How to use MedITEX DICOM Application

From MedITEX - Wiki

(Difference between revisions)
Jump to: navigation, search
Line 92: Line 92:
 
<p>&nbsp;</p>
 
<p>&nbsp;</p>
 
<h2>MedITEX DICOM Server Configuration</h2>
 
<h2>MedITEX DICOM Server Configuration</h2>
 +
<p><strong>DICOM-SERVER</strong></p>
 +
<p>The communication between ultrasound devices and MDS is done via TCP/IP. The IP address is the address of that computer where the MDS is running. The default port is 108 but you can assign any other port if 108 is in use. The so called AE-Title only matters if different database applications in your network provide different worklists. In case of many ultrasound devices in combination with MDS (and no other application that listens on the defined port), the AE-Title is just nice to have.</p>
 +
<table style="margin-left: auto; margin-right: auto;" border="0" width="10" height="44">
 +
<tbody>
 +
<tr>
 +
<td>
 +
<p>[[Image:8_DICOM_Connection.png|none|740px|thumb|left|link=http://wiki.meditex-software.com/images/8_DICOM_Connection.png|  ]]</p>
 +
</td>
 +
</tr>
 +
</tbody>
 +
</table>

Revision as of 12:59, 22 September 2017

MedITEX DICOM Server Application

MedITEX DICOM Server (MDS) has 2 main tasks:

  • Communication with ultrasound devices to retrieve DICOM measurements ("ultrasound" or "structured report") and provide worklists.
  • Processing the DICOM measurements, extracting header information and perform a database insert or update for the associated patient.

MedITEX DICOM Server can be run as a service (hidden) or as a normal application with a user interface.

This is a description of its general workflow:

- A DCM message comes in:

  • In case of a worklist request, MDS sends back the daily task list.
  • In case of any measurement, MDS saves a DCM file in a so called SPOOL folder.

- DCM files are scanned, analyzed and processed (one after the other).

- Each single step is recorded in a protocol file:

  • Communications in a monthly created log file.
  • DCM processing in a protocol keeping the last 50 records.

- If a DCM file is successfully processed it will be saved in a so called ARCHIVE folder, in case of errors it will be saved in a FAILED folder where it can be used later for manual re-work.

The below screenshots show a typical US (ultrasound image), a typical SR (structured report) and how the relevant follicle measurement is extracted and prepared for database insert or update.

<tbody> </tbody>

1 MedITEX DICOM US.png

2 DICOM SR ListView.png
3 DICOM SR Dataset.png

Patient ID, Patient Name, DOB (Date of Birth), Sex, Study Date / Time and SOP Class are extracted from the DCM header (no manual interaction is possible here).

The SOP Class defines the Modality that informs the MDS Application which kind of information is in the DCM file and how it should be processed.

  • Drag any DCM file from explorer and drop it into the MDS form or click on the upper right button to open a file dialog.
  • The DCM file is immediately analyzed and processed if possible.

 

The following screenshot shows a typical header information. If no header can be extracted or the internal SOPClassUID is not mapped to a modality, the whole DCM file cannot be processed and is immediately moved into the FAILED folder.

<tbody> </tbody>

4 DICOM DCM Header.png

The normal situation where it is possible to interact with the MDS application is called RE-WORK.

Here you can manually work on a DCM file, associate the correct patient and run the import again.

  • Click on Analyse CDM-File (1) and the patient records of the selected DCM file will be displayed.
  • When clicking on Assign Patient (2) then, a list of all your patients will open.
  • Choose from this list the patient to whom the DCM file should be assigned and click on Assign Patient (3) symbol next to the patient ID.
  • Once the new patient is assigned to the DCM file, click on Import (4) and the file will be processed.
<tbody> </tbody>

5 DICOM Rework Analyse.png

6 DICOM Rewok Assign.png

This is an example of a typical protocol displaying one successfully imported ultrasound image and another failed one.

<tbody> </tbody>

7 DICOM Protocol.png

 

MedITEX DICOM Server Configuration

DICOM-SERVER

The communication between ultrasound devices and MDS is done via TCP/IP. The IP address is the address of that computer where the MDS is running. The default port is 108 but you can assign any other port if 108 is in use. The so called AE-Title only matters if different database applications in your network provide different worklists. In case of many ultrasound devices in combination with MDS (and no other application that listens on the defined port), the AE-Title is just nice to have.

<tbody> </tbody>

8 DICOM Connection.png