LLMpediaThe first transparent, open encyclopedia generated by LLMs

Digital Imaging and Communications in Medicine (DICOM)

⚠Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: The Cancer Imaging Archive Hop 6 terminal

This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.

Digital Imaging and Communications in Medicine (DICOM)
NameDigital Imaging and Communications in Medicine
AbbreviationDICOM
Initial release1985
DeveloperAmerican College of Radiology; National Electrical Manufacturers Association
Latest release(varies)
Website(see governing bodies)

Digital Imaging and Communications in Medicine (DICOM) Digital Imaging and Communications in Medicine is a standards framework for handling, storing, printing and transmitting medical imaging information, developed by the American College of Radiology, the National Electrical Manufacturers Association, and adopted by diverse institutions such as World Health Organization, Food and Drug Administration, European Commission, and International Organization for Standardization. The standard underpins interoperability among vendors including GE Healthcare, Siemens Healthineers, Philips Healthcare, Canon Medical Systems, and supports clinical systems like PACS used in hospitals such as Mayo Clinic and Johns Hopkins Hospital. DICOM interacts with related standards and initiatives from organizations such as IHE, HL7, SNOMED International, and LOINC to enable integrated imaging workflows across providers including Kaiser Permanente and NHS England.

History

DICOM emerged in the mid-1980s following interoperability challenges identified by institutions including Massachusetts General Hospital and vendors like Eastman Kodak Company and Hitachi, building on earlier efforts exemplified by projects at Stanford University and standards work at National Institute of Standards and Technology. Early milestones involved collaboration between the American College of Radiology and the National Electrical Manufacturers Association culminating in initial releases that influenced regulatory dialogues at the Food and Drug Administration and procurement standards used by health systems such as Veterans Health Administration. Subsequent revisions were informed by input from academic centers including Harvard Medical School and University of California, San Francisco as well as industry consortia like RSNA and SIIM.

Standard and Organization

The standard is maintained through committees and working groups involving stakeholders such as IHE, HL7 International, ISO/TC 215 and vendor consortia including MITRE Corporation and GE Healthcare, with governance models comparable to processes at IEEE and ANSI. Technical content is produced by expert panels reflecting clinical sites like Cleveland Clinic and manufacturers including Siemens Healthineers and Philips Healthcare, and coordinated via meetings hosted by organizations such as RSNA and SIIM. DICOM’s evolution aligns with policy frameworks at European Medicines Agency and interoperability roadmaps from Centers for Medicare & Medicaid Services and is referenced in procurement by networks such as Truven Health Analytics.

File Format and Data Model

DICOM specifies a binary file format and an information object model influenced by data modeling practices used at National Library of Medicine and HL7 International, defining attributes such as patient identifiers used by Centers for Disease Control and Prevention and study metadata interoperable with terminologies from SNOMED International and LOINC. The object model supports modalities produced by manufacturers like GE Healthcare and Philips Healthcare including Computed Tomography scanners by Siemens Healthineers and Magnetic Resonance Imaging systems from Canon Medical Systems, encoding pixel data alongside structured metadata used in archives at institutions such as Memorial Sloan Kettering Cancer Center and MD Anderson Cancer Center. File structure variants include encapsulated formats that enable embedding of derived images and reports similar to practices in archives at National Institutes of Health and libraries at Library of Congress.

Network Services and Protocols

DICOM defines network services and protocols for query/retrieve, storage, print and worklist management which interoperate with systems from vendors like Fujifilm and Agfa-Gevaert and integrate with hospital systems such as Epic Systems Corporation and Cerner Corporation. Services use TCP/IP and application layer conventions comparable to those standardized by IETF and are often deployed alongside messaging standards from HL7 International and directory services like those used by Microsoft enterprise solutions. Implementation profiles and testing events organized by IHE and demonstrations at conferences like RSNA Annual Meeting validate conformance across research centers such as Massachusetts Institute of Technology and national laboratories like Lawrence Berkeley National Laboratory.

Security and Privacy

Security extensions to the standard accommodate encryption, authentication and audit trails aligning with regulatory regimes such as Health Insurance Portability and Accountability Act enforcement by U.S. Department of Health and Human Services and privacy frameworks from European Data Protection Board informed by General Data Protection Regulation. Implementations incorporate cryptographic suites endorsed by bodies like NIST and integrate identity management solutions from vendors including Okta and directory services used by Microsoft Azure in cloud deployments with governance considerations similar to those at National Cyber Security Centre (UK). Clinical sites including Royal Free Hospital and research networks like All of Us Research Program implement policy controls to balance access, secondary use and data-sharing agreements exemplified by frameworks at Wellcome Trust and Bill & Melinda Gates Foundation.

Implementations and Software

A broad ecosystem of commercial and open-source software implements the standard, from vendor platforms by GE Healthcare, Siemens Healthineers, Philips Healthcare to open projects like Orthanc, DCMTK, dcm4che and archival solutions used by centers such as Stanford Health Care and Beth Israel Deaconess Medical Center. Cloud services from Amazon Web Services, Google Cloud Platform, and Microsoft Azure provide managed DICOM APIs used by research consortia including UK Biobank and academic collaborations at Johns Hopkins University and University of Oxford. Conformance testing, certification and academic evaluations are conducted at events and programs run by RSNA, IHE, and standards bodies like NEMA.

Adoption and Impact in Clinical Practice

DICOM’s adoption enabled integrated imaging workflows across hospitals including Mayo Clinic, Cleveland Clinic, and national health services like NHS Scotland, facilitating teleradiology networks linking providers such as Teladoc Health and specialty centers like MD Anderson Cancer Center. The standard supported advances in multimodality imaging used in clinical trials by organizations like National Cancer Institute and multicenter studies coordinated by World Health Organization, improving diagnostic workflows in departments at Johns Hopkins Hospital and enabling AI pipelines developed by research labs at MIT and Stanford University. Its interoperability model influenced procurement, regulatory guidance from FDA and clinical IT strategies at health systems including Kaiser Permanente and global initiatives supported by WHO.

Category:Medical imaging standards