| DICOM PS3.16 2024e - Content Mapping Resource |
|---|
Table 8-1 lists the coding schemes (and their designators) defined for use in DICOM; Table 8-2 lists the HL7v3 coding schemes referenced for use in DICOM. Additionally, any coding scheme may be used that has an entry in the HL7 Registry of Coding Schemes (HL7 v2 Table 0396, or the equivalent online registry), in which case the HL7 Symbolic Name shall be used as the value for the Coding Scheme Designator in DICOM, as long as it does not conflict with an entry Table 8-1 and fits within the Value Representation of the DICOM Coding Scheme Designator (0008,0102) Attribute. As specified in the HL7 v2 Table 0396, local or private coding schemes shall be identified by an alphanumeric identifier beginning with the characters "99".
An earlier version of this table was formerly contained in Annex D of PS3.3.
See Section 8.2 “Coding Scheme Designator and Coding Scheme Version” in PS3.3 for further description.
The Coding Scheme UIDs are provided for reference only; the normative specification of UIDs and their associated meaning is the responsibility of the coding scheme developer and/or HL7.
The current version of HL7 v2 Table 0396 is available at http://www.hl7.org/special/committees/vocab/table_0396/index.cfm.
The HL7 registration of Coding Schemes is available at http://www.hl7.org/oid/index.cfm.
Publication of codes or references to coding schemes within DICOM does not constitute a grant of intellectual property rights to implementers. Use of some Coding Schemes may require a license, or purchase of the relevant coding scheme publication. Implementers should consult the relevant coding scheme publisher; see also Section 2.
The values of Coding Scheme Name (0008,0115), Coding Scheme Responsible Organization (0008,0116) and Coding Scheme Resources Sequence (0008,0109), if available, may be used to fill the corresponding optional Attributes of the Coding Scheme Identification Sequence (0008,0110) in the Section C.12.1 “SOP Common Module” in PS3.3 .
Table 8-1. Coding Schemes
|
ACR Index for Radiological Diagnosis Revised, 3rd Edition 1986 |
|||||
|
[ASTM E 2084-00] Signature Purpose codes (see Annex A1 of ASTM E 2084), ASTM Subcommittee E 31.20 Data and System Security for Health Information |
|||||
|
Bypass Angioplasty Revascularization Investigation[Alderman 1992]; endorsed by ACC/AHA Guidelines for Coronary Angiography[Scanlon 1999]. |
|||||
|
ACR Breast Imaging Reporting and Data System [BI-RADS®], Coding Scheme Version (0008,0103) is required; Code Values are section and paragraph identifiers within the publication where the code meaning is defined (e.g., "I.D.1", where I = Breast Imaging Lexicon, D = Special Cases, 1 = Tubular Density, as the Code Value for "Tubular Density"). |
|||||
|
American Medical Association's Current Procedure Terminology 4 (CPT-4) |
|||||
|
American Medical Association's Current Procedure Terminology 5 (CPT-5) |
|||||
|
The Public ID is used as the Code Value. These can be looked up as in the following example (the version is required): http://cdebrowser.nci.nih.gov/CDEBrowser/search?dataElementDetails=9/&cdeId=2178693&version=2.1&PageId=DataElementsGroup |
|||||
|
American Dental Association's (ADA) Current Dental Terminology 2 (CDT-2) |
|||||
|
Dublin Code Metadata for Resource Discovery. The Code Value is the Label field, e.g., "Creator" (capitalization significant). |
|||||
|
DOC: http://dicom.nema.org/medical/dicom/current/output/chtml/part16/chapter_D.html OWL: ftp://medical.nema.org/MEDICAL/Dicom/Resources/Ontology/DCM/dcm.owl.zip |
PS3.16 Content Mapping Resource, Annex D (Note that HL7 also specifies an OID of 2.16.840.1.113883.6.31, but deprecates it in favor of 1.2.840.10008.2.16.4). |
||||
|
DOC: http://dicom.nema.org/medical/dicom/current/output/chtml/part06/chapter_A.html |
|||||
|
DOC: http://sig.biostr.washington.edu/projects/fm/AboutFM.html OWL: http://sig.biostr.washington.edu/share/downloads/fma/release/latest/fma.zip |
|||||
|
Healthcare Financing Administration (HCFA) Common Procedure Coding System (HCPCS) |
|||||
|
International Classification of Diseases revision 10 (ICD-10) |
|||||
|
International Classification of Diseases, Tenth Revision, Clinical Modification |
|||||
|
International Classification of Diseases revision 11 (ICD-11) |
|||||
|
International Classification of Diseases revision 9, with Clinical Modifications (ICD-9-CM) |
|||||
|
DOC: http://www.who.int/standards/classifications/other-classifications/international-classification-of-diseases-for-oncology |
International Classification of Diseases for Oncology, 3rd Edition NoteICD-O-3 version 3.2 is described at http://www.iacr.com.fr/index.php?option=com_content&view=article&id=149. |
||||
|
[RFC 4646], Tags for Identifying Languages, The Internet Society (2005) [RFC 4646] has been superceded by [RFC 5646]. |
|||||
|
[ISO 639-1] Two-letter language codes |
|||||
|
[ISO 639-2] Three-letter language codes |
|||||
|
[ISO 3166-1] alpha-2 Country Codes |
|||||
|
Representation of Human Sexes (not used) ISO5218_1, which uses numeric codes, was improperly specified in CID 7455 Sex in earlier editions of the Standard. The alphabetic codes improperly attributed to that coding scheme have been added to the DICOM Controlled Terminology, and thus all references to coding scheme ISO5218_1 should be considered equivalent to coding scheme DCM. |
|||||
|
[ISO 8824-1] ISO/IEC 8824-1- Information Technology - Abstract Syntax 1 (ASN.1): Specification of Basic Notation, and [ISO 9834-1] - Information technology - Open Systems Interconnection - Procedures for the operation of OSI Registration Authorities: General procedures and top arcs of the ASN.1 Object Identifier tree |
|||||
|
A Taxonomic Serial Number (TSN) is a unique, persistent, non-intelligent identifier for a scientific name in the context of the Integrated Taxonomic Information System (ITIS). |
|||||
|
DOC: http://loinc.org/ FHIR: http://loinc.org |
[LOINC] Logical Observation Identifier Names and Codes |
||||
|
DOC: http://www.informatics.jax.org/searches/AMA.cgi?id=MA:0002405 |
Hayamizu TF, Mangan M, Corradi JP, Kadin JA, Ringwald M. The Adult Mouse Anatomical Dictionary: a tool for annotating and integrating data. Genome Biology 2005;6(3):R29. doi:10.1186/gb-2005-6-3-r29. http://www.ncbi.nlm.nih.gov/pmc/articles/PMC1088948/ |
||||
|
Mayo Clinic Non-radiological Images Specific Body Structure Anatomical Surface Region Guide |
The numeric code of entries in the Mayo Clinic Non-radiological Images Specific Body Structure Anatomical Surface Region Guide. |
||||
|
ISO/IEEE 11073 Medical Device Nomenclature, including all its subsections ([ISO/IEEE 11073-10101], [ISO/IEEE 11073-10101a], [ISO/IEEE 11073-10102], etc.), encoded as decimal strings <partition>:<element> |
|||||
|
The MGI ID from the Mouse Genome Initiative (MGI) nomenclature. |
|||||
|
US National Library of Medicine (NLM) Medical Subject Headings (MeSH) |
|||||
|
Bernstein AD, et al."The NASPE/BPEG Defibrillator Code" PACE, 16:1776-1780, 1993 |
|||||
|
DOC: http://www.hrsonline.org/Practice-Guidance/Clinical-Guidelines-Documents/2002-The-Revised-NASPE-BPEG-Generic-Code-for-Antibradycardia-AdaptiveRate-and-Multisite-Pacing |
NASPE/BPEG Generic Pacemaker Code (2000) Bernstein AD, et al."The Revised NASPE/BPEG Generic Code for antibradycardia, adaptive-rate, and multisite pacing." Pacing Clin Electrophysiol., 25:260-264, 2002 See http://www.hrsonline.org/Practice-Guidance/Clinical-Guidelines-Documents/2002-The-Revised-NASPE-BPEG-Generic-Code-for-Antibradycardia-AdaptiveRate-and-Multisite-Pacing. |
||||
|
American College of Cardiology National Cardiovascular Data Registry™ Cath Lab Module Version 1.1, 1997; Version 2.0b, 1999 |
|||||
|
DOC: http://www.fda.gov/Drugs/InformationOnDrugs/ucm142438.htm |
The Code Value is the 10 digit 3 segment NDC code with "-" between segments included and no asterisk (leading zero placeholder). |
||||
|
DOC: http://braininfo.rprc.washington.edu/aboutBrainInfo.aspx#NeuroNames |
|||||
|
DOC: http://digital.nhs.uk/article/1108/National-Interim-Clinical-Imaging-Procedure-NICIP-Code-Set |
UK National Health Service National Interim Clinical Imaging Procedures (NICIP) Short Code (e.g., "CCHAPC" for CT Thorax abdomen pelvis with contrast) |
||||
|
The numeric code of entries in the New York University Melanoma Clinical Cooperative Group's numbering system. |
|||||
|
DOC: http://www.ihe.net/Technical_Framework/upload/IHE_PAT_Suppl_APSR_Appendix_Value_Sets_2011_03_31.xls |
|||||
|
US National Center for Biotechnology Information (NCBI) PubChem Compound CID. |
|||||
|
FHIR: http://www.radlex.org |
|||||
|
[RFC 3066], Tags for the Identification of Languages, Internet Engineering Task Force NoteHL7 uses "IETF3066" for the symbolic name. [RFC 3066] has been superseded by [RFC 4646], which in turn has been superceded by [RFC 5646]. |
|||||
|
[RFC 3881], Security Audit and Access Accountability Message - XML Data Definitions for Healthcare Applications |
|||||
|
[RFC 5646], Tags for Identifying Languages, The Internet Society (2009) NoteThe HL7 OID Registry specifies "rfc5646", not "ietf5646", as the Desired Symbolic Name (inconsistent with the pattern used for [RFC 4646]). [RFC 5646] constitutes one part of IETF Best Current Practice BCP 47 Tags for Identifying Languages, which also includes [RFC 4647] Matching of Language Tags; [RFC 4647] is not relevant in this context. |
|||||
|
RxNorm provides normalized names for clinical drugs and links its names to many of the drug vocabularies commonly used in pharmacy management and drug interaction software. |
|||||
|
SNOMED DICOM Microglossary (Retired) (see Section 8.1) |
|||||
|
Standard Communications Protocol for Computer-Assisted Electrocardiography, Draft proposal for ISO Standard, AAMI, Revision 1.3 |
|||||
|
SNOMED International Version 3 (see Section 8.1) |
|||||
|
FHIR: http://snomed.info/sct |
[SNOMED], using the CT Code Values |
||||
|
[SNOMED], using the "SNOMED-RT style" Code Values (see Section 8.1) |
|||||
|
DOC: http://uberon.org/ |
The Uberon ID from the Uberon integrated cross-species ontology covering anatomical structures in animals. |
||||
|
[UCUM] Unified Code for Units of Measure |
|||||
|
Unified numbering system (UNS) for metals and alloys [J1086_201210] |
|||||
SNOMED (the Systematized Nomenclature of Medicine) Clinical Terms (CT) is the preferred coding system within DICOM for anatomy, clinical findings, procedures, pharmaceutical/biologic products (including contrast agents), and other clinical terms.
SNOMED has had various versions, including SNOMED International (Version 3), which was issued in 1993 and revised through 1998, SNOMED Reference Terminology, the successor to SNOMED 3 that was published between 1999 and 2001, and SNOMED Clinical Terms, which has been the name since 2002. The coding scheme is fully backward-compatible across SNOMED 3, SNOMED-RT, and SNOMED CT. SNOMED CT introduced a solely numeric set of codes (ConceptID) in addition to the former alphanumeric codes (SnomedID), but all SNOMED terminology concepts have both a numeric and an alphanumeric code.
In previous editions of the DICOM Standard, the following Coding Scheme Designators were used for SNOMED codes in DICOM:
All uses of SNOMED CT coded terms in DICOM are now indicated by the Coding Scheme Designator "SCT", identifying them as SNOMED CT numeric Concept IDs as Code Values.
When a Coding Scheme Designator of "99SDM", "SNM3" or "SRT" is encountered by a receiving system, the "SNOMED-RT style" alphanumeric Code Value needs to be mapped to the corresponding concept designated by the SNOMED CT Concept IDs assigned to the same concept.
"SRT" as a coding scheme designator was used only in the DICOM Standard. HL7v2 did not standardize a coding scheme designator for SNOMED-RT.
When interoperating with systems that use SNOMED CT codes, Application Entities may receive and are expected to send Code Sequences with a numeric ConceptID code. It is the responsibility of such Application Entities to convert any alphanumeric SnomedID with Coding Scheme Designator "SRT" used in old DICOM objects and services to the corresponding numeric ConceptID code.
Some non-DICOM systems may use a Coding Scheme Designator of "SNOMED-CT" rather than "SCT" as is used in DICOM.
The SNOMED organization's policy on the use of "antecedent versions", including the continued use of "SNOMED-RT style" alphanumeric Code Values is described at: http://www.snomed.org/news-articles/timetable-for-the-withdrawal-of-legacy-snomed-codes.
Since the SNOMED organization no longer distributes a reference set that includes a mapping of "SNOMED-RT style" SNOMED IDs to SNOMED Concept IDs a complete mapping of those used in DICOM is provided in Annex O to allow implementers to process legacy objects from legacy devices and archives.
In general, DICOM uses the anatomic concepts with the term "structure", rather than with the term "entire". This is an important distinction in SNOMED. "Entire" is a child concept to "structure", has a more restricted meaning, and typically is used in conjunction with treatments (e.g., "excision of entire right kidney"). It is used in distinction to other sibling children of the parent concept that may identify parts of the parent anatomic feature. Since imaging typically targets both the anatomic feature and the area around it, or sometimes just part of the anatomic feature, DICOM usually uses "structure" concepts that are more inclusive than the "entire" concepts.
| DICOM PS3.16 2024e - Content Mapping Resource |
|---|