Recent and Future developments of the DICOM standard
Publication date: Mar 06, 2014
Harry Solomon, DICOM chair, discusses some of the new/recent changes to the DICOM standard, inclusive of the publication
of DICOM in an XML format, FHIR and RESTful DICOM, as well as Patient Safety issues.
I recently held a video interview with Harry Solomon, who works for GE and has been chair of the ACR/NEMA DICOM
committee since the fall of 2013. During the interview, which focused on new and/or future developments in
the DICOM standard, three notable topics came up:
DICOM publication in an XML format
"The publication of the DICOM standard in an XML format will prbably have the most visible impact" according to Harry.
DICOM has been wordking on this for over 10 years. The idea is that by having the specification in XML developers will be
able to access all of the tables, all of the information object definitions, and the vocabulary, and use this in
This would enable thinks like test tools, code generators, documentation generators - there's wide variety of things that
they expect to facilitate by creating an XML specification.
FHIR and RESTful DICOM
"It's the model for what we want to do when accessing DICOM objects", says Harry when asked about FHIR,
"as we're developing DICOM webservices we're very much looking at how that would integrate with the FHIR resources.
We don't want to reinvent the wheel, so we've already made the decision that any
'general' resources are all going to be FHIR resources,
and DICOM will focus on the definition of any 'imaging' resources."
DICOM has been working on webservices (mainly for access to images) for over a decade.
Initially WADO (a URL based mechanism),
subsequently Webservices, and currently REST. New users with new use cases want to leverage the technology
they have - so if mobile devices support
REST, DICOM has to create a RESTful protocol to allow for access to imaging objects by such devices.
"At the same time we want to preserve the investment that has been made
in imaging systems, and the value of the data that has been collected.
So we want to create RESTful services that integrate well with existing production systems."
DICOM tries to ensure that the evolutionary trends still maintain the value of any existing
images in the radiology department. As such these new protocols are viewed as layers on top of DICOM.
There'll be a mixture of the DICOM native protocol and webservices for some of these new use cases.
Radiation dosage monitoring
DICOM also has relationships with the IEC related to the issue of radiation safety. Regulatory agencies have an interest
in collecting information related to radiation/patient safety issues. Jointly with the IEC DICOM has created the information stuctures
to capture patient radiation dose information, initially for simple X-Rays, for CT, and currently they're working on collecting
radiation data for radiopharmaceuticals. This is tricky, because the radiopharmaceutical dose is not produced by the imaging
equipment, but by the radiopharmaceutical agent. The dosage has to be collected in a system that's ancilary to the
Future of DICOM
DICOM will be with us for years to come, and it's my impression that the level of
coordination between DICOM and other standards organizations has increased, and I'm sure it will increase, over time.
The core value of DICOM (according to the DICOM standardization community) lies in its object definitions, and in the
existing clinical information archived according to those definitions. As such new 'transport protocols' like REST
can be easily embraced.
PermaLink to this page: http://www.ringholm.com/column/Recent_Future_Developments_in_DICOM_Harry_Solomon.htm
Index of columns:
- De Algemene Verordening Gegevensbescherming (AVG) in de zorg (Dutch, Sep 19, 2017)
- Impact of the GDPR on the use of interoperability standards (Jun 27, 2017)
- News from the FHIR DevDays in Amsterdam (Dec 15, 2016)
- Next XDS Release (Oct 27, 2016)
- Five years of FHIR (Aug 11, 2016)
- Interoperability projects in Ireland - FHIReland (Mar 14, 2016)
- 2016 FHIR Jedi Calendar (Jan 06, 2016)
- Top 10 HL7 videos watched in 2015 (Dec 24, 2015)
- Update from the trenches on CDA R2.1/R3 and HL7v2. (Oct 15, 2015)
- FHIR DevDays - UK GP System APIs (Sep 16, 2015)
- IHE XDS - testing and implementation tools (Aug 25, 2015)
- Most often implemented IHE Profiles (Jun 08, 2015)
- Why we sponsor the HL7 WGM (May 10, 2015)
- FHIR in Paris (Apr 21, 2015)
- Mapping HL7v2 messages to FHIR. (Apr 13, 2015)
- Analysis of CDA R2 testing tools - most requirements are neither tested nor respected. (Feb 13, 2015)
- HL7 and IHE in Sweden (Feb 08, 2015)
- 2015 FHIR Chiefs Calendar (Jan 07, 2015)
- The Merry FHIR Choir caroling the 12 Days of Christmas (Dec 09, 2014)
- Chicago FHIR Update (Oct 13, 2014)
- Internationalization of HL7 (Sep 25, 2014)
- New XDS Advanced training course on offer by IHE Services and IHE Academy (Jul 14, 2014)
- Recent and Future developments of the DICOM standard (Mar 06, 2014)
- Top 10 HL7 videos watched in 2013 (Jan 02, 2014)
- Report from the HL7 WGM in Cambridge (Oct 16, 2013)
- Documenting the history of HL7 (Sep 03, 2013)
- Histology Lab Device Automation using HL7 version 2 (Jul 23, 2013)
- HL7 FHIR Elevator Pitch (Jul 15, 2013)
- Interoperability Standards - the no-sales pitch (Jul 09, 2013)
- HL7 UK - new landscape, new opportunities (Jun 26, 2013)
- Validation and error correction at the IHE Connectathon (Apr 25, 2013)
- CDA Implementation Guides - (not) invented here (Apr 17, 2013)
- Usage of IHE Profiles (Feb 25, 2013)
- 10 year anniversary - Dutch Ringholm HL7 v2 training courses. (Feb 19, 2013)
- About IHE Academy and new IHE training courses (Jan 12, 2013)
- CDA implementation experiences in the UK (Dec 04, 2012)
- Musings on free HL7 IP (Oct 01, 2012)
- HL7 Connectathons (Sep 09, 2012)
- Renovate HL7 version 3 (Aug 03, 2012)
- Frequency of use of HL7 message types (Jul 24, 2012)
- Lighting the FHIR, HL7s new major interoperability standard (Jun 15, 2012)
- Reflections on the HL7 membership model - the affiliate life cycle (Dec 28, 2011)
- Thinking like an OWL reasoner (Sep 17, 2011)
- RFH (Resources for Health): HL7 version 3 taken to the next step (Aug 18, 2011)
- What's so great about the HL7 organization? (Aug 04, 2011)
- Kerndossier: een Nederlandse versie van CCD (Dutch, May 03, 2011)
- A HL7 RIMBAA update (Apr 21, 2011)
- Timezone Hotel (Mar 29, 2011)
- HL7 and openEHR are cooperating (finally) (Jan 21, 2011)
- Increasing demand for IHE training courses (Dec 18, 2010)
- Context issues with the IHE QED profile (Dec 15, 2010)
- The changing role of HL7 country organizations (Jul 16, 2010)
- Implementing HL7 version 3 - the book (May 06, 2010)
- Adding openness to a closed world (Feb 09, 2010)
- How to lower the hurdle for HL7 v3 implementers (Jan 21, 2010)
- HL7 v3 deployment statistics (Dec 17, 2009)
- There's Trouble in Paradigm (Sep 25, 2009)
- Internationalization of HL7 (Sep 24, 2009)
- HL7 UK signs deal with Ringholm to deliver HL7 v2/v3 training courses in London (Sep 17, 2009)
- The use of HL7 in South Africa (Aug 20, 2009)
- The Next Web Conference in Amsterdam (Apr 17, 2009)
- The HL7 UK AGM and RIMBAA (Apr 16, 2009)
- The HL7 Wiki reaches 2000 pages (Mar 02, 2009)
- The HL7 roadmap for CDA R3 and the CCD (Jan 17, 2009)
- HL7 Affiliates Meeting in Orlando (Jan 11, 2009)
- Swiss and Dutch HL7 News (Dec 31, 2008)
- Devices and Prizes (Nov 22, 2008)
- HL7 in Norway: a situation report (Sep 02, 2008)
- Russian whitepaper (Jul 09, 2008)
- The HL7 Interoperability Conference - IHIC 2008 (May 30, 2008)
- HL7 creates a RIM Based Application Architecture (RIMBAA) group (May 18, 2008)
- Notes from the HL7 WGM in Phoenix (May 08, 2008)
- Germany embraces CDA eReferral document specification (May 02, 2008)
- HL7 v3 RIM based applications: an unintended side effect (Jan 19, 2008)
- Collaborative Tools (Jun 21, 2007)
- HL7 ist Pflicht in der deutschen Telematikinfrastruktur (German, Mar 16, 2007)
- HL7 based Tree inventory system (Jan 30, 2007)
- The link between HL7 and Open Source Software (Jan 06, 2007)
- Workflow Bribery (Sep 15, 2006)
- Timezones in HL7 (Jan 23, 2004)
- Controlled vocabularies: "@*%!!!" ? (Sep 01, 2003)
- Trusting the other Party (Nov 01, 2002)
About Ringholm bv
Ringholm bv is a group of European experts in the field of messaging standards and systems integration in healthcare IT.
We provide the industry's most advanced training courses and consulting on healthcare information exchange standards.
See http://www.ringholm.com or call +31 33 7 630 636 for additional information.
Rene is the Tutor-in-chief of Ringholm.