DICOM

I have dabbled wtih DICOM, and loaded some FreeWare tools to my PC so I can open up DICOM files and modify patient header information for testing (in essence turning my PC into a modality).  The software is freeware by Offis (http://dicom.offis.de/dcmtk.php.en).

A DICOM file (*.dcm) is a file that contains both the image and patient/image/order information which is encrypted.  These are all stored in pre-defined data elements (you would need to get your hands on the DICOM standard).  Myself, I just look at the data I get, and Google for more information.

Using these tools, I have converted the image file from the .dcm format to txt format.  From there I have parsed out or even modified the information.  If I have made changes (say for testing an upgrade and I need a particular test patient), I then package the information back up to the DICOM format and send it onto the PACS.  The tools allow you go get images from and store images to other DICOM SCUs (modality, PACS, etc.).

Since they have Windows and UNIX versions, I don’t see why one couldn’t just load this on their Cloverleaf box, and run the command line stuff via some script, e.g., TCL, and create a Clovelreaf UPoc interface to accept/send DICOM information.  However, there are a lot of products out there that already do this, e.g., Conquest, so this work may already be done for you.  In fact, we have an MD here who downloaded Conquest and is using it as a DICOM engine to integrate the University Student Health clinic’s X-rays into the hospital PACs.

My biggest advice is to start Googling and expect to spend hours gathering information, downloading freeware, andplaying around with it.

Hope this helps,