How to use MedITEX DICOM Application

From MedITEX - Wiki

(Difference between revisions)
Jump to: navigation, search
Line 8: Line 8:
 
<p>MedITEX DICOM Server can be run as a service (hidden) or as a normal application with a user interface.</p>
 
<p>MedITEX DICOM Server can be run as a service (hidden) or as a normal application with a user interface.</p>
 
<p>This is a description of its general workflow:</p>
 
<p>This is a description of its general workflow:</p>
−
<p>-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A DCM message comes in<br /> - in case of a worklist request, MDS sends back the daily task list<br /> - in case of any measurement, MDS saves a DCM file in a so called SPOOL folder</p>
+
<ul>
−
<p>-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DCM files are scanned, analyzed and processed (one after the other)</p>
+
<li>A DCM message comes in:<br />
−
<p>-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Each single step is recorded in a protocol file<br /> - communications in a monthly created log file<br /> - DCM processing in a protocol file that keeps the last 50 records</p>
+
<ul>
−
<p>-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If a DCM file is successfully processed it <em>can be saved</em> in a so called ARCHIVE folder,<br /> in case of errors it <em>will be saved</em> in a FAILED folder for a later manual re-work</p>
+
<li>In case of a <strong>worklist</strong> request, MDS sends back the daily task list.</li>
−
<p>The following pictures are screenshots of each form of the MDS application:</p>
+
<li>In case of any measurement, MDS saves a DCM file in a so called <strong>SPOOL</strong> folder.</li>
 +
</ul>
 +
</li>
 +
</ul>
 +
<ul>
 +
<li>DCM files are scanned, analyzed and processed (one after the other).</li>
 +
<li>Each single step is recorded in a protocol file:<br />
 +
<ul>
 +
<li>Communications in a monthly created log file.</li>
 +
<li>DCM processing in a protocol keeping the last 50 records.</li>
 +
</ul>
 +
</li>
 +
</ul>
 +
<ul>
 +
<li>If a DCM file is successfully processed it will be saved in a so called <strong>ARCHIVE</strong> folder, in case of errors it will be saved in a <strong>FAILED </strong>folder where it can be used later for manual re-work.</li>
 +
</ul>
 +
<p>The following screenshots describe each form of the MedITEX DICOM Server Application:</p>
 
<table style="margin-left: auto; margin-right: auto;" border="0" width="10" height="44">
 
<table style="margin-left: auto; margin-right: auto;" border="0" width="10" height="44">
 
<tbody>
 
<tbody>
Line 20: Line 36:
 
</td>
 
</td>
 
</tr>
 
</tr>
−
</tbody>
 
−
</table>
 
−
<p>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 so called SOP Class defines the so called Modality which informs the MDS application which kind of information is in the DCM file and how it should be processed. Drag any DCM file from you 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 picture above shows a typical US (ultrasound image), the two pictures below a typical SR (structured report) and how the relevant follicle measurement is extracted and prepared for database insert or update.</p>
 
−
<table style="margin-left: auto; margin-right: auto;" border="0" width="10" height="44">
 
−
<tbody>
 
 
<tr>
 
<tr>
−
<td>
+
<td>[[Image:2_DICOM_SR_ListView.png|none|740px|thumb|left|link=http://wiki.meditex-software.com/images/2_DICOM_SR_ListView.png|  ]]</td>
−
<p>[[Image:2_DICOM_SR_ListView.png|none|740px|thumb|left|link=http://wiki.meditex-software.com/images/2_DICOM_SR_ListView.png|  ]]</p>
+
−
</td>
+
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 35: Line 44:
 
</tbody>
 
</tbody>
 
</table>
 
</table>
 +
<p>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).</p>
 +
<p>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.</p>
 +
<p>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.</p>
 +
<p>The DCM file is immediately analyzed and processed if possible.</p>
 +
<p>The above screenshot shows 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.</p>
 +
<p>&nbsp;</p>
 
<p>The 3<sup>rd</sup> picture shows (for the sake of completeness) 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.</p>
 
<p>The 3<sup>rd</sup> picture shows (for the sake of completeness) 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.</p>
 
<table style="margin-left: auto; margin-right: auto;" border="0" width="10" height="44">
 
<table style="margin-left: auto; margin-right: auto;" border="0" width="10" height="44">
Line 68: Line 83:
 
</tbody>
 
</tbody>
 
</table>
 
</table>
−
<p>&nbsp;</p>
 

Revision as of 11:47, 22 September 2017

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 following screenshots describe each form of the MedITEX DICOM Server Application:

<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 above screenshot shows 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.

 

The 3rd picture shows (for the sake of completeness) 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 you can 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.

<tbody> </tbody>

5 DICOM Rework Analyse.png

6 DICOM Rewok Assign.png

Last not least a screenshot of a typical protocol. Two records are displayed: one successfully imported ultrasound image, and one failed because of unmapped patient ID.

<tbody> </tbody>

7 DICOM Protocol.png