In DICOM, the process of choosing a code, and a coding scheme, depends on the context. In the following, we will discuss some of the guidelines that can be used to choose suitable codes for the tasks of segmentation, measurements and parametric map conversion supported by dcmqi.
While converting segmentations, you will need to define the following coded entities in the JSON file:
SegmentedPropertyCategoryCodeSequence
SegmentedPropertyTypeCodeSequence
SegmentedPropertyTypeModifierCodeSequence (when applicable)
AnatomicRegionSequence (when applicable)
This looks overwhelming indeed! That's why we developed to help you interactively choose the codes for each of those items. If you want to know the details, read on!
For each of these attributes, DICOM provides guidance on the selection of the suitable codes.
SegmentedPropertyCategoryCodeSequence codes are listed in context group ID (CID) (extensible, i.e., you are not forced to use only the codes from this selection)
SegmentedPropertyTypeCodeSequence codes are defined in , which points to the application-specific CIDs that you can follow for the lists of codes
SegmentedPropertyTypeModifierCodeSequence is an optional attribute that augments segmented property type code. As an example, if SegmentedPropertyTypeModifier is "Kidney", SegmentedPropertyTypeModifier can be "Left" to specify laterality. More modifier codes are available in , as an example see .
AnatomicRegionSequence and its modifier do not always have to be specified. In some situations, information contained in SegmentedPropertyType is sufficient. E.g., if one is creating an atlas, where the properties are purely anatomical, and there is no more to say about them than the anatomy, then the anatomy goes in the Segmented Property Type Code Sequence. If one has different types of properties (e.g., necrosis, enhancing rim, gross tumor volume), but one wants to say something about the anatomy (e.g., where the tumor is at), then the property goes in Segmented Property Type Code Sequence and the anatomy goes in Anatomic Region Sequence. When you do want to specify AnatomicRegion, you can consult for the list of codes. Modifier for this code is specified as needed, following the same approach as discussed for SegmentedPropertyTypeModifierCodeSequence.
we mentioned earlier provides an interactive interface to somewhat simplify the task of populating the codes discussed above.
Most, if not all codes listed in the contexts referenced earlier are from SNOMED CT, and have DICOM CodingSchemeDesignator SRT. The reason for this is that coding scheme is the preferred controlled terminology used by DICOM . Most, if not all, of the codes used to define the entities above are from SNOMED CT. SNOMED CT maintains a systematically organized computer processable collection of medical terms providing codes, terms, synonyms and definitions used in clinical documentation and reporting. SNOMED CT maintains the hierarchy of relationships among the codes, which can be used for semantic reasoning on the data. As an example, see .
Note that SNOMED CT codes included in the DICOM standard are exempt from . The details are discussed in . In short:
Users and commercial and open source DICOM developers can be reassured that they may continue to use the subset of SNOMED concepts in the DICOM standard in their products and software, globally and without a fee or individual license.
TBD - work in progress
The following codes can be passed to describe the parametric map you are converting using :
QuantityValueCode: Quantity being measured at each pixel - select code from , or introduce a .
MeasurementUnitsCode: Units of measurement. DICOM uses code system (CodingSchemeDesignator UCUM) to describe units. Some of the commonly used unit codes are listed in , but as discussed in , any of the UCUM codes can be used in DICOM.
DerivationCode: select code from , or introduce a .
In the future we plan to provide specific recipes that describe the sets of codes suitable for specific use-cases (e.g., estimating Apparent Diffusion Coefficient (ADC) from Diffusion-Weighted MRI, or performing pharmacokinetic modeling of the Dynamic Contrast-Enhanced MRI).
Relevant development of the codes related to ADC calculation can be found in DICOM Correction Proposal (CP). These codes are expected to become part of the standard in Spring 2017.
For now, the best place to start is (select pm-schema in the Validation schema selector) that you can use to choose an existing example and modify it to tailor to your use case.
AnatomicRegionModifierSequence (when applicable)
AnatomicRegionSequence and Modifier (optional): follow the same guidelines as discussed for Segmentation
anatomic codes selection.
MeasurementMethodCode (optional): code describing the model used for deriving the quantity.
ModelFittingMethodCode (optional): code describing the model fitting method.