Radiology image exchange

February 13, 2012 by MassDevice

By John D. Halamka, MD

Dr. John Halamka

In my recent blog about the Standards Work Ahead in 2012, I called DICOM a non-standard standard.

This generated numerous email messages, phone calls, and blog comments.

Let me clarify what I meant.

Sign up to get our free newsletters delivered straight to your inbox

DICOM is a great standard that has unified many processes within organizations, linking radiology modalities and PACS systems.

Why do I believe additional work is needed?

In December, my wife visited a hospital near our home for a diagnostic mammogram. It was clear she needed followup care with a cancer care team. We decided that Beth Israel Deaconess would be ideal because of its electronic health records and personal health records that would help Kathy coordinate her care. We asked for the images to be transmitted to BIDMC and we were told that we needed to visit the radiology department Monday-Friday 9am-5pm for a CD to be created so that Kathy could drive is 20 miles to BIDMC. The CD contained a proprietary viewer that required Windows and hence was not visible on our home computers (all Mac OSX).

What would have happened in an ideal world?

1. An implementation guide for DICOM would specify required vendor neutral content - a basic set of metadata (patient identifiers, name of the radiology study, imaging techniques used etc.) that would work with any viewer - Siemens, Agfa, Philips, GE, Kodak, etc. Any vendor specific/proprietary metadata would be stored separately from the required basic content, so that extensions do not impact generic viewers. CDs with proprietary viewers and media formats should become a thing of the past.