History and Evolution of DICOM

Section 2 of 27
7% complete

History and Evolution

Understanding DICOM’s history helps appreciate its current capabilities and future direction.

Timeline

1985: The Beginning

The American College of Radiology (ACR) and National Electrical Manufacturers Association (NEMA) formed a joint committee to develop a standard for medical imaging communications.

The initial goal was simple but ambitious: create a way for medical imaging devices from different manufacturers to share images and related information.

1993: DICOM 3.0 - The Foundation

DICOM 3.0 was released as the first comprehensive version, establishing the foundation that continues to this day:

  • Introduced network protocol - Enabled direct communication between devices over TCP/IP networks
  • Defined service classes - Established the operations that DICOM devices can perform (storage, query, retrieve, print)
  • Established conformance requirements - Created a framework for vendors to declare what their products support

This version transformed DICOM from a simple file format into a complete communication standard.

2000s: Major Expansions

The 2000s saw DICOM grow to address more complex healthcare needs:

  • Structured Reporting (SR) - Machine-readable encoding of radiological findings
  • Encapsulation of non-image data - Support for PDFs, videos, and other media
  • Security enhancements - TLS support for encrypted communications
  • Enhanced compression - Support for JPEG 2000 and other modern codecs

2010s: Web-Based Standards

The web era brought significant changes:

  • DICOMweb (RESTful services) - HTTP-based APIs for DICOM operations
    • QIDO-RS: Query
    • WADO-RS: Retrieve
    • STOW-RS: Store
  • Integration with IHE profiles - Standardized workflows for healthcare integration
  • Enhanced compression support - Modern codecs for efficient storage and transmission

2015+: Modern Healthcare Integration

Recent developments focus on interoperability with the broader healthcare ecosystem:

  • FHIR ImagingStudy resources - Integration with HL7 FHIR for modern healthcare APIs
  • Cloud-native implementations - Support for cloud storage and processing
  • AI/ML integration standards - Frameworks for incorporating artificial intelligence in imaging workflows

DICOM Versions

Unlike traditional software, DICOM uses continuous updates rather than major version numbers:

DICOM Version Strategysaravanansubramanian.comone evergreen standard, extended by supplements instead of major version bumpsNot this: sequential major versionsDICOM 3.01993DICOM 4.0never happenedDICOM 5.0never happenedInstead: one root, continuous supplementsDICOM 3.0the evergreen root (1993 to today)Sup 1 and 21994early refinementsSup 231998Structured ReportingSup 1452011DICOMwebSup 1832015FHIR integrationSup 2192020AI AnnotationsAnnual Publication: 21 PartsPS3.1IntroPS3.2Conform.PS3.3IODsPS3.10File FmtPS3.18Web SvcPS3.21Xformsyearly

The standard is published annually with supplements added regularly. Each supplement addresses specific needs, from new modalities to enhanced security features.

Key Milestones Summary

YearMilestoneImpact
1985ACR-NEMA Committee formedFoundation established
1993DICOM 3.0 releasedNetwork protocol, service classes
1998Structured ReportingMachine-readable findings
2004Security supplementsTLS, digital signatures
2011DICOMweb (Supplement 145)RESTful web services
2015FHIR integrationModern healthcare APIs
2018AI/ML supplementsAI workflow integration

This evolution demonstrates DICOM’s ability to adapt to changing healthcare needs while maintaining backward compatibility with existing systems.

Quiz: History and Evolution of DICOM

Question 1 of 4

When was DICOM 3.0, the first comprehensive version, released?