DICOM PS3.21 2018c - Transformations between DICOM and other Representations
Copyright © 2018 NEMA
Table of Contents
- Notice and Disclaimer
- Foreword
- 1. Scope and Field of Application
- 2. Normative and Informative References
- 3. Definitions
- 4. Symbols and Abbreviations
- 5. Conventions
- A. Transformation Between AIM and DICOM SR
-
- A.1. Scope and Field of Application
- A.2. Use Cases
- A.3. Structure of DICOM SR Documents
- A.4. Structure of AIM Version 4 Instances
- A.5. AIM v4 Structure
- A.6. AIM v4 to DICOM TID 1500 Mapping
-
- A.6.1. Mapping of Constrained AIM v4
-
- A.6.1.1. Header
-
- A.6.1.1.1. Mapping of DICOM Patient Module
- A.6.1.1.2. Mapping of DICOM Clinical Trial Subject Module
- A.6.1.1.3. Mapping of DICOM General Study Module
- A.6.1.1.4. Mapping of DICOM Patient Study Module
- A.6.1.1.5. Mapping of DICOM Clinical Trial Study Module
- A.6.1.1.6. Mapping of DICOM SR Document Series Module
- A.6.1.1.7. Mapping of DICOM Clinical Trial Series Module
- A.6.1.1.8. Mapping of DICOM General Equipment Module
- A.6.1.1.9. Mapping of DICOM SR Document General Module
- A.6.1.1.10. Mapping of DICOM SR Document Content Module
- A.6.1.1.11. Mapping of DICOM SOP Common Module
- A.6.1.2. Content Tree
-
- TID 1500. Mapping of Measurement Report
- TID 1501. Mapping of Measurement Group
- TID 1502. Mapping of Time Point Context
- TID 1410. Mapping of Planar ROI Measurements
- TID 1411. Mapping of Volumetric ROI Measurements
- TID 1419. Mapping of ROI Measurements
- TID 1420. Mapping of Measurements Derived From Multiple ROI Measurements
- TID 300. Mapping of Measurement
- TID 320. Mapping of Image or Spatial Coordinates
- TID 4019. Mapping of Algorithm Identification
- TID 4108. Mapping of Tracking Identifier
- TID 1204. Mapping of Language of Content Item and Descendants
- TID 1001. Mapping of Observation Context
- TID 1002. Mapping of Observer Context
- TID 1003. Mapping of Person Observer Identifying Attributes
- TID 1600. Mapping of Image Library
- TID 1601. Mapping of Image Library Entry
- TID 1602. Mapping of Image Library Entry Descriptors
- A.7. Sample Documents
- A.8. Overview of Data Types
List of Figures
- A.2-1. Annotation Creation and Transformation
- A.3-1. SR Document Structure
- A.3.2.1-1. Template Structure Summarized from PS 3.16
- A.4-1. AIM v4 Instance Structure
List of Tables
- A.3.1-1. Transformation of DICOM SR IOD Modules
- A.6.1.1.1-1. Mapping of DICOM Patient Module
- A.6.1.1.3-1. Mapping of DICOM General Study Module
- A.6.1.1.6-1. Mapping of DICOM SR Document Series Module
- A.6.1.1.8-1. Mapping of DICOM General Equipment Module
- A.6.1.1.9-1. Mapping of DICOM SR Document General Module
- A.6.1.1.11-1. Mapping of DICOM SOP Common Module
- TID 1500. Mapping of Measurement Report
- TID 1501. Mapping of Measurement Group
- TID 1502. Mapping of Time Point Context
- TID 1410. Mapping of Planar ROI Measurements
- TID 1411. Mapping of Volumetric ROI Measurements
- TID 1419. Mapping of ROI Measurements
- TID 1420. Mapping of Measurements Derived From Multiple ROI Measurements
- TID 300. Mapping of Measurement
- TID 320. Mapping of Image or Spatial Coordinates
- TID 4019. Mapping of Algorithm Identification
- TID 4108. Mapping of Tracking Identifier
- TID 1204. Mapping of Language of Content Item and Descendants
- TID 1001. Mapping of Observation Context
- TID 1002. Mapping of Observer Context
- TID 1003. Mapping of Person Observer Identifying Attributes
- TID 1600. Mapping of Image Library
- TID 1601. Mapping of Image Library Entry
- TID 1602. Mapping of Image Library Entry Descriptors
- A.7.2-1. Transformed SR document encoding at the Attribute level
- A.8-1. ISO 21090 Data Types used in AIM V4
- A.8-2. Mapping between DICOM Basic Code Attributes and AIM ISO 21090 Code Data Types (CD)
- A.8-3. Mapping between DICOM Person Name (PN) ans ISO 21090 Data Type Person Name (PN)
- A.8-4. Mapping between DICOM Numeric Measurement Value Types and ISO 21090 Data Types
- A.8-5. Mapping between DICOM Numeric Value Qualifier Code Sequence and AIM ST
- A.8-6. DICOM Image references to AIM Path
- A.8-7. DICOM Segmentation references to AIM Path
List of Examples
- A.8-1. Person Name Example
- A.8-2. HL7 V3 Multi-Part Person Name Example
The information in this publication was considered technically sound by the consensus of persons engaged in the development and approval of the document at the time it was developed. Consensus does not necessarily mean that there is unanimous agreement among every person participating in the development of this document.
NEMA standards and guideline publications, of which the document contained herein is one, are developed through a voluntary consensus standards development process. This process brings together volunteers and/or seeks out the views of persons who have an interest in the topic covered by this publication. While NEMA administers the process and establishes rules to promote fairness in the development of consensus, it does not write the document and it does not independently test, evaluate, or verify the accuracy or completeness of any information or the soundness of any judgments contained in its standards and guideline publications.
NEMA disclaims liability for any personal injury, property, or other damages of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, application, or reliance on this document. NEMA disclaims and makes no guaranty or warranty, expressed or implied, as to the accuracy or completeness of any information published herein, and disclaims and makes no warranty that the information in this document will fulfill any of your particular purposes or needs. NEMA does not undertake to guarantee the performance of any individual manufacturer or seller's products or services by virtue of this standard or guide.
In publishing and making this document available, NEMA is not undertaking to render professional or other services for or on behalf of any person or entity, nor is NEMA undertaking to perform any duty owed by any person or entity to someone else. Anyone using this document should rely on his or her own independent judgment or, as appropriate, seek the advice of a competent professional in determining the exercise of reasonable care in any given circumstances. Information and other standards on the topic covered by this publication may be available from other sources, which the user may wish to consult for additional views or information not covered by this publication.
NEMA has no power, nor does it undertake to police or enforce compliance with the contents of this document. NEMA does not certify, test, or inspect products, designs, or installations for safety or health purposes. Any certification or other statement of compliance with any health or safety-related information in this document shall not be attributable to NEMA and is solely the responsibility of the certifier or maker of the statement.
This DICOM Standard was developed according to the procedures of the DICOM Standards Committee.
The DICOM Standard is structured as a multi-part document using the guidelines established in [ISO/IEC Directives, Part 2].
This part of the DICOM Standard specifies the transformations between DICOM and other representations of the same information.
Currently, this Part addresses:
Transformation of diagnostic imaging reports between DICOM SR and HL7 CDA representations is addressed in PS3.20.
The following standards contain provisions that, through reference in this text, constitute provisions of this Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibilities of applying the most recent editions of the standards indicated below.
[ISO/IEC Directives, Part 2] 2016/05. 7.0. Rules for the structure and drafting of International Standards. http://www.iec.ch/members_experts/refdocs/iec/isoiecdir-2%7Bed7.0%7Den.pdf .
[ISO 21090] 2011. Health informatics -- Harmonized data types for information interchange. http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=35646 .
[V3 DT R1] 2004. HL7 Version 3 Standard: XML Implementation Technology Specification - Wire Format Compatible Release 1 Data Types, Release 1. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=357 .
[XML] 2006/09/29. Extensible Markup Language (XML) 1.1. http://www.w3.org/TR/2006/REC-xml11-20060816/ .
[XSD Datatypes] 2004/10/28. XML Schema Part 2: Datatypes. http://www.w3.org/TR/xmlschema-2/ .
[AIM v3 v4 changes] 2014/04/10. Changes from AIM 3.0, Revision 11 to AIM Foundation - Summary of Changes Between AIM 3.0 and 4.0 Models. https://wiki.nci.nih.gov/display/AIM/Changes+from+AIM+3.0%2C+Revision+11+to+AIM+Foundation#ChangesfromAIM3.0,Revision11toAIMFoundation-ISO21090DataTypes .
[AIM Model v4 rv48] 2013/03. Annotation and Image Markup model version 4. https://wiki.nci.nih.gov/display/AIM/Annotation+and+Image+Markup+-+AIM#AnnotationandImageMarkup-AIM-AIMModel .
[Extending AIM] 2014/12/03. Extending the AIM Model. https://wiki.nci.nih.gov/display/AIM/Extending+the+AIM+Model .
[caBIG™ AIM] J Digit Imaging. 2010/04. 2. 217–225. “The caBIG™ Annotation and Image Markup Project”. doi:10.1007/s10278-009-9193-9 http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2837161/ .
[AIM Template Builder] Radiographics. 2012/07. 4. 1223–1232. “An Open-Source and Open-Access Cancer Biomedical Informatics Grid Annotation and Image Markup Template Builder”. doi:10.1148/rg.324115080 http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3393884/ .
[AIM Foundation Model] J Digit Imaging. 2014/12. 6. 692–701. “The National Cancer Informatics Program (NCIP) Annotation and Image Markup (AIM) Foundation Model”. doi:10.1007/s10278-014-9710-3 http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4391072/ .
For the purposes of this Standard the following definitions apply.
The following definitions are commonly used in this Part of the DICOM Standard:
- Coding Schemes
-
Dictionaries (lexicons) of concepts (terms) with assigned codes and well defined meanings.
See Section 3.1 "Codes and Controlled Terminology Definitions" in “Codes and Controlled Terminology Definitions:” in PS3.16 .
- Content Item
-
A node in the Content Tree of a DICOM SR document, consisting of either a container with a coded Concept Name, or a name-value pair with a coded Concept Name and a Concept Value.
- Content Tree
- Context Group
-
A set of coded concepts defined by a Mapping Resource forming a set appropriate to use in a particular context.
See Section 3.1 "Codes and Controlled Terminology Definitions" in “Codes and Controlled Terminology Definitions:” in PS3.16 .
- Context ID (CID)
-
Identifier of a Context Group.
See Section 3.1 "Codes and Controlled Terminology Definitions" in “Codes and Controlled Terminology Definitions:” in PS3.16 .
- Template
-
A pattern that describes the Content Items, Value Types, Relationship Types and Value Sets that may be used in part of a Structured Report Content Tree, or in other Content Item constructs, such as Acquisition Context or Protocol Context. Analogous to a Module of an Information Object Definition.
See Section 3.1 "Codes and Controlled Terminology Definitions" in “Codes and Controlled Terminology Definitions:” in PS3.16 .
- Template ID (TID)
-
See Section 3.1 "Codes and Controlled Terminology Definitions" in “Codes and Controlled Terminology Definitions:” in PS3.16 .
The following symbols and abbreviations are used in this Part of the Standard.
- AIM
- DICOM
- IOD
- ISO
- NCI
- NEMA
- OID
- SR
- UCUM
- UID
- XML
- XSLT
Terms listed in Section 3 Definitions are capitalized throughout the document.
NCI AIM objects that are constrained to specific use cases can be transformed to DICOM SR documents that are based on TID 1500.
NCI AIM specifies a generic model for encoding structured information about medical images. The AIM model and its XML encoding are version specific. The version transformed in this document is Version 4 [Extending AIM]. Though AIM instances can be generated according to application-specific templates [ref. AIM template builder], such templates are too use-case specific to be detailed in the transformation described in this Part. Rather, common patterns of use implemented by well known implementations (ref. CC, ref ePAD) have been abstracted and are mapped as described in this document.
DICOM SR specifies a generic model for encoding structured information about DICOM instances. DICOM TID 1500 Measurement Report specifies a basic DICOM SR report template for quantitative measurements and categorical statements for single identifiable patient subjects including regions of interest defined by spatial coordinates or segmentations.
The basic use case for the transformation from AIM to DICOM SR is exchange of quantitative and categorical information about DICOM images and regions of interest in DICOM images.
AIM and DICOM SR instances both contain references to DICOM images, and both make use of references to other types of DICOM instances such as segmentations. The flow of information between systems that might make use of a conversion between AIM and DICOM SR instances is considered in Figure A.2-1.
Various different transformation scenarios should be considered:
-
Transformation of a complete AIM instance to a complete DICOM SR Measurement Report. The receiver optionally selects relevant parts of the transformed document for further processing or static or interactive visualization by the user.
-
Transformation of a subset of a AIM instance to a DICOM SR Measurement Report. This subset comprises the relevant information for a specific use-case.
-
Transformation of multiple related AIM instances to a single DICOM SR Measurement Report. The selected related AIM instances comprise the relevant information for a specific use-case.
This part of the Standard does not mandate any particular transformation scenario. Transformations of various compatible components of AIM and DICOM SR TID 1500 are described, allowing each of these scenarios to be implemented as appropriate. This part of the Standard enables a deterministic transformation of the first scenario (complete mapping of an AIM instance to DICOM).
The primary use-case for the transformation is that of:
-
taking an existing AIM instance containing one or more annotations, converting it into DICOM SR, storing it in a DICOM storage system, possibly displaying it with a DICOM SR aware application, transforming it back into an AIM instance after retrieval from the DICOM storage system, and reusing it in an AIM-aware application
An important secondary use-case is transformation of annotation information in different formats into a single format for data aggregation (e.g., "analytics", "data mining", "big data", "machine learning", and "deep learning"). The conversion described here is intended to allow preservation of semantics sufficient for such purposes, regardless of the source format.
It should be understood that DICOM SR created by transforming an AIM object will not necessarily be identical in structure and content to a DICOM SR that might have been created de novo by a similar application. For instance, there are various encoding choices that an application implementer may make, especially with respect to the degree of post-coordination of ROI and measurement descriptions, which might result in different structures. It may not be possible to transform a DICOM SR TID 1500 instance into AIM and retain all of its content. Post-coordinated concepts, such as measurement and derivation methods, may be preserved by using multiple CalculationEntity/typeCode entries or by pre-coordinating into a single concept during the transformation.
Multiple regions of interest, or multiple measurements and categorical statements about a single region of interest, or about the same real world entity (e.g., lesion) identified with different regions of interest (e.g., at different time points or with different modalities), may be encoded in single or multiple AIM or DICOM SR instances. Whether or not a source AIM or DICOM SR implementation encodes more than one region of interest (and their accompanying measurements and categorical statements) in a single instance or in separate instances, and whether the conversion from one form to the other "bundles" multiple instances into a single instance, or "unbundles" a single instance into multiple instances, is not prescribed. The AIM 4.0 model allows for the encoding of multiple marked up regions and multiple measurements in a single annotation instance, but does not provide a mechanism for identifying which markup is associated with which measurement; it is therefore necessary to assume that all markup applies to all measurements and vice versa.
-
For example, for RECIST measurements that involve the long and short axis of a lesion, though it is currently possible to encode in AIM (and map to TID 1500) the measurements as derived from a planar volumetric ROI, and recognize them by their concept name code, it is not also possible to encode the endpoints of the measured axes of the pair of linear measurements. Nor is a reverse mapping of such information encoded in TID 1500 into AIM possible. Some current AIM implementations use private extensions to address this use case, but mapping these is beyond the scope of the Standard.
-
It is expected that a future revision of the AIM 4.0 model will allow for explicit linkage of markup and measurements, probably using statements, e.g., CalculationEntityReferencesMarkupEntityStatement and CalculationEntityReferencesSegmentationEntityStatement, at which time the appropriate mappings will be added.
DICOM SR documents can be thought of as consisting of a document header and a document body. The header metadata attribute values are grouped into modules such as "Patient", "General Study" in PS3.3.
The SR Document Content Module (Section C.17.3 in PS3.3 ) contains the attributes for the root Content Item, which includes the coded report title. The Content Tree (structured content) of the document body is contained in the nested Content Sequence Items of that module. "Container" Content Items are part of the Content Sequence. They are structural elements of the SR document body structure. Content items are DICOM SR document nodes within the Content Tree that are connected through "by-value" relationships (for Enhanced SR IODs). The transformations defined in this Part do not support the use of "by-reference" relationships between Content Items.
The Modules used in a DICOM SR are defined by the Information Object Definition (IOD). A particular DICOM SR template may be encoded using a variety of DICOM SR IODs, depending on the features supported by the template and used by a particular instance. Each SR IOD constrains the Value Types and Relationship Types that are permitted. The Enhanced SR IOD is sufficient to encode TID 1500 instances unless 3D patient-relative coordinates (rather than 2D image-relative coordinates or segmentations) are used to define regions of interest on images, in which case use of the Comprehensive 3D SR IOD or Extensible SR IOD would be required.
Table A.3.1-1 summarizes the modules common to the SR IODs that can encode the TID 1500 as specified in PS3.3.
Table A.3.1-1. Transformation of DICOM SR IOD Modules
The Patient Module specifies the Attributes of the Patient that describe and identify the Patient who is the subject of a Study. This Module contains Attributes of the patient that are needed for interpretation of the Image and are common for all studies performed on the patient.
The Clinical Trial Subject Module contains attributes that identify a Patient as a clinical trial Subject.
The General Study Module specifies the Attributes that describe and identify the Study performed upon the Patient.
The Patient Study Module defines the attributes that provide information about the Patient at the time the Study was performed.
The Clinical Trial Study Module contains attributes that identify a Study in the context of a clinical trial.
The SR Document Series Module defines the Attributes of the SR Document Series. A Series of SR Documents may contain any number of SR Documents.
The Clinical Trial Series Module contains attributes that identify a Series in the context of a clinical trial.
The General Equipment Module specifies the Attributes that identify and describe the piece of equipment that produced a Series of Composite Instances.
The SR Document General Module defines the general Attributes of an SR Document Instance. These Attributes identify the SR Document and provide context for the entire document.
The SOP Common Module defines the Attributes that are required for proper functioning and identification of the associated SOP Instances.
The Attributes in this Module convey the content of an SR Document. It specifies the root Content Item and the Content Tree (refer to Figure A.3-1).
The document body is the information that is stored in the DICOM SR Content Tree. The Content Tree is encoded in the SR Document Content Module.
TID 1500 is the top-level template of the DICOM SR Measurement Report (PS3.16). It includes sub-templates as shown in Figure A.3.2.1-1.
Note
-
The use of TID 1001 Observation Context within TID 1000 Quotation is not shown because it is not relevant to the mapping use cases.
-
The use of TID 311 Measurement Statistical Properties and TID 312 Normal Range Properties within TID 310 Measurement Properties is not shown because it is not relevant to the mapping use cases.
-
The use of TID 1410 Planar ROI Measurements, TID 1411 Volumetric ROI Measurements, and TID 310 Measurement Properties within TID 1420 is not shown because it is not relevant to the mapping use cases.
The goal of this document is to specify a mapping between constrained AIM v4 instances and TID 1500 Measurement Report DICOM SR documents. The following limitations apply to AIM instances that are mapped to DICOM SR Measurement Reports:
-
Subject Context: The DICOM SR TID 1500 Measurement Report is restricted to cover exactly one patient subject; the mapping of subject context of fetuses, specimens or devices as subjects is out of scope. Small or large animal identifiers and descriptors (beyond reuse of the normal patient identifiers) are not specifically addressed since no such identifiers are present in the AIM model (e.g., multiple animals imaged as one, and strain descriptions are out of scope).
-
The mapping of DICOM SR clinical trial header data (Clinical Trial Subject Module, Clinical Trial Study Module, Clinical Trial Series Module) is not described since no such identifiers are present in the AIM model.
-
The transformation of de-identified objects is not specifically addressed in this mapping, since AIM does not address encoding of the history of de-identification explicitly. I.e., identifiers will be converted unchanged and whether they have been de-identified will not be explicitly signaled.
-
A subset of spatial coordinate types are mapped, to the extent that both AIM and DICOM SR support the same graphic concepts.
The hierarchical attributes describing DICOM composite object references are used whenever DICOM composite objects are referenced in the Content Tree and are also described in the Image Library templates and the Current Requested Procedure Evidence Sequence (0040,A375) or Pertinent Other Evidence Sequence (0040,A385). Information on relevant DICOM objects referenced within the AIM instance are included in the AIM DicomImageReferenceEntity class.
AIM instances are encoded in XML according to a schema generated from the AIM Model [AIM Model v4 rv48], which is defined in UML. Figure A.4-1 is a simplified view rather than the entire model, showing only those UML classes and attributes relevant to the transformations described in this part.
Version 4 of AIM makes use of [ISO 21090] data types. See Section A.8 “Overview of Data Types”.
The transformation is described in one direction, by enumerating the structures in the target (DICOM SR TID 1500) and describing where in the source (AIM v4) the corresponding information may be obtained. The information is tabulated in a manner that can be implemented as an automated "pull" conversion of an AIM instance into a DICOM SR instance, such as might be described using a transformation language such as XSLT. The transformation is intended to be reversible, i.e., by inverting the target and the source, even though round-trip full fidelity will not be achieved in some cases. Gaps that exist in the information required in the target to create a compliant object, which need to be filled by information from an out of band source or generated de novo , are highlighted. Information in the source that is not "pulled" into the DICOM encoding will be lost; these omissions are deemed to be harmless from the perspective of the relevant use cases.
The tabular representations make use of the following conventions in order to simplify the automatic extraction and use as a formal syntax to drive implementations:
-
DICOM attributes are represented by keywords defined in PS3.6, rather than specifying the data element group and element tags.
-
DICOM attributes that are nested within sequences are shown as a path from the top level data set separated by a ">" symbol.
-
AIM classes, attributes and associations are represented using their XPath representation as encoded in XML instances.
-
DICOM Code Sequence attributes are mapped from AIM CD data type attributes without fully enumerating the corresponding subordinate DICOM attributes and XML elements and attributes.
-
Other DICOM Sequences are listed, without a mapping on the same row, but with the following rows describing the individual DICOM Attributes nested within that Sequence.
-
All source and target paths are fully qualified relative to the root of the instance in order to make the transformation reversible. I.e., it would be possible to describe some transformations using the descendant-or-self axis XSLT operator ("//") if the source were unambiguous but that would not specify the location reversibly as a target. Accordingly, some of the explicit paths are quite long.
-
The requirement type for DICOM Attributes is as defined in PS3.3 for Attributes in Modules and Macros, except that if the containing Module in the IOD is not required, e.g., is U rather than M, then a mandatory (Type 1 or 2) Attribute in a user optional (type U) Module is shown as optional (Type 3).
-
The data type and cardinality are specified for both the source and the target, to highlight potential mismatches that may occur during transformation. For nested elements and attributes, the multiplicity is expressed as the combination of the multiplicity along the entire path. For example, the aim:name attribute has a multiplicity of 1:1 in an aim:Person class but is associated with the aim:ImageAnnotationClass with a multiplicity of 1 -> 0:1, so the multiplicity is indicated as 0:1, not 1:1, since that is the net effect. The DICOM multiplicity is either the VM for the data element or the number of Sequence Items if the data element is a Sequence.
The XML representation of the AIM UML collapses some associations and classes such that they are encoded as a single element, and this is reflected in the mapping paths. For example, the aim:Person class has an aim:person association from the aim:ImageAnnotationCollection class, so the path to the aim:name attribute is expressed as /ImageAnnotationCollection/person/name, as it appears in the XML instance.
-
Data type transformations are assumed and are not described further unless there is a specific requirement. For example, conversion from DICOM DA, TM and DT VR Attributes to AIM TS Data Type values is implicit, including extraction/population of the appropriate sub-fields (i.e., only the date portion of a TS is used when creating a DICOM DA value).
-
If value sets are defined for both AIM and DICOM, then value mappings are described. In some cases, explicit value sets are not defined. For example, aim:Person/sex has no explicitly defined value set but maps to DICOM PatientSex, which does; so if AIM implementations use the DICOM values, and the values are copied, then the transformation without value mapping will be successful, but not otherwise.
-
When a mapping is defined but no transformation source is available but a value is required, a Generated Value is indicated, which may be a fixed constant (e.g., a Modality value of "SR"), an indication that an empty (zero length) value or sequence is required, or an indication that a new value of the appropriate VR needs to be generated (e.g., a new UID for a UI VR, a new integer for an IS VR, etc.). The need to generate new values will not produce a deterministic result without a memory of previous conversions.
-
Optional content in the target that has no defined source is not described (e.g., DICOM SeriesDescription in the General Series Module has no correlate in AIM, though it would be useful to populate with a generated value).
-
When the same DICOM Attribute is described in two different Modules, the more specialized (restrictive) use is described in the mapping tables. E.g., InstanceNumber is Type 3 in the SOP Common Module but Type 1 in the SR Document General Module, so it is only described in the latter.
-
Capitalization and punctuation of DICOM keywords and AIM class, attribute and association names are significant.
General Remarks on the mapping of DICOM header module attributes:
-
Mapped AIM objects are considered "unverified", so there is no requirement to record the identity of the Verifying Observer; if the "recording" observer identity is required (aim:user class attributes) it may be mapped to Author Observer Sequence (0040,A078) in the SR Document General Module (and entries in Observation Context in the Content Tree are not needed).
-
Attributes of the Predecessor Documents Sequence (0040,A360) and Identical Documents Sequence (0040,A525) are not described in this transformation since they are relevant only in the context of a managed DICOM SR document environment and have no correlate in AIM.
-
Attributes of the Current Requested Procedure Evidence Sequence (0040,A375) and Pertinent Other Evidence Sequence (0040,A385) are described in the transformation and provide the information described in the Hierarchical SOP Instance Reference Macro used to match composite instance references with their Study and Series context; the AIM DicomImageReferenceEntity class performs a similar function.
-
Attributes of the Equivalent Document Sequence (0040,A090) are not described in the transformation since they are relevant only in the context of the original DICOM SR document.
The name space of the AIM elements is elided, and is implied to be "gme://caCORE.caCORE/4.4/edu.northwestern.radiology.AIM".
-
Timezone Offset From UTC (0008,0201) shall be considered for attributes of the DICOM SR document that are based on the DA or TM data type (PS3.5). AIM date and time attributes may or may not contain explicit timezone information that may be extracted to populate Timezone Offset From UTC (0008,0201).
-
The Specific Character Set (0008,0005) is required (Type 1C), if the Basic Graphic Set is expanded or replaced. This is the basis for mapping DICOM character sets to AIM XML Unicode (<?xml version="1.0" encoding="UTF-8"?>).
Note
Ambiguities exist for mapping individual characters to Unicode (e.g., for Japanese characters). Resolution of those issues is beyond the scope of this document. Please refer to Section A.8 for further details on data types and character sets.
Note
If the annotation concerns a small animal that has been imaged as part of a group of animals in the same image, then the PatientID and other Attributes of this Module will be those of that individual animal, not the group. Currently there is no AIM mechanism to identify the group of animals imaged at the same time that corresponds to the DICOM SourcePatientGroupIdentificationSequence.
No mapping of the DICOM Clinical Trial Subject Module is described since no corresponding content is present in the AIM model.
The AIM 4.0 model does not provide Study information per se (i.e., conceptually an AIM instance may exist independent of a Study, but DICOM requires that SR instances be part of a Study). Accordingly, during transformation from AIM to SR either a new Study may be generated, or the SR instance derived from the AIM object could be placed in (one of) the Study(ies) referenced by the AIM instance, assuming there are any, which produces a predictable transformation, and is described here.
If there is more than one DICOM Study referenced by the AIM object, duplicates of the converted AIM SR instance may be placed in each of the referenced studies (with different SOP Instance UIDs), in which case the IdenticalDocumentsSequence is required in the SR Document General Module; see PS3.3 C.17.2.2 Identical Documents Sequence.
Table A.6.1.1.3-1. Mapping of DICOM General Study Module
No mapping of the DICOM Patient Study Module is described since no corresponding content is present in the AIM model.
No mapping of the DICOM Clinical Trial Study Module is described since no corresponding content is present in the AIM model.
The AIM 4.0 model does not support the concept that an annotation itself is part of a series, and it cannot be made part of a referenced image series, if any, because of the rule that all instances of a series are generated on the same equipment.
Table A.6.1.1.6-1. Mapping of DICOM SR Document Series Module
No mapping of the DICOM Clinical Trial Series Module is described since no corresponding content is present in the AIM model.
Table A.6.1.1.8-1. Mapping of DICOM General Equipment Module
Table A.6.1.1.9-1. Mapping of DICOM SR Document General Module
All the Attributes in the SR Document Content Module are transformed by processing the DICOM SR Content Tree, and accordingly are not described in the same tabular manner as the "header" Attributes, since the mapping depends on the DICOM SR template structure. The Attributes common to each Content Item of the Content Tree are:
Each child Content Item with a "by-value" relationship with its parent also contains:
The additional required Attributes in each Content Item depend on the ValueType:
-
NUM - MeasuredValueSequence, MeasuredValueSequence>NumericValue, MeasuredValueSequence>MeasurementUnitsCodeSequence
-
COMPOSITE - ReferencedSOPSequence, ReferencedSOPSequence>ReferencedSOPClassUID, ReferencedSOPSequence>ReferencedSOPInstanceUID
-
IMAGE - ReferencedSOPSequence, ReferencedSOPSequence>ReferencedSOPClassUID, ReferencedSOPSequence>ReferencedSOPInstanceUID, ReferencedSOPSequence>ReferencedFrameNumber, ReferencedSOPSequence>ReferencedSegmentNumber
-
SCOORD3D - ReferencedFrameOfReferenceUID, GraphicData, GraphicType
-
CONTAINER - ContinuityOfContent, ContentTemplateSequence, ContentTemplateSequence>MappingResource, ContentTemplateSequence>TemplateIdentifier
Table A.6.1.1.11-1. Mapping of DICOM SOP Common Module
|
The fixed value is the SOP Class UID of the Enhanced SR Storage SOP Class, which is sufficient unless SCOORD3D are used, in which case the Comprehensive 3D SR Storage SOP Class is required, which has a UID of "1.2.840.10008.5.1.4.1.1.88.34". |
||||||||
|
Generated if more than one converted instance in separate studies. |
||||||||
|
The fixed generated value corresponds to the normal UTF-8 specified in the XMLDecl of the XML prolog [XML] in the AIM instance. Other values may be used if they are sufficient to describe all the encoded characters in the transformed instance. E.g., it may be omitted entirely if all the characters are US-ASCII. |
This section describes the mapping of TID 1500 “Measurement Report” in PS3.16 .
Table TID 1500. Mapping of Measurement Report
|
The fixed Concept Name code is an appropriate choice selected from CID 7021 “Measurement Report Document Titles” in the absence of a "document title" concept in AIM. If out of band information is available, a more appropriate code can be used. |
||||||||
|
TID 1204 “Mapping of Language of Content Item and Descendants” |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (121058, DCM, "Procedure reported") |
The fixed generic code value is suggested in lieu of AIM containing any information about the imaging procedure, so more specific procedure codes such as those from CID 100 “Quantitative Diagnostic Imaging Procedures” cannot be used. If out of band information is available, a more appropriate code can be used. |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126011, DCM, "Derived Imaging Measurements") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126011, DCM, "Derived Imaging Measurements") > |
TID 1420 “Mapping of Measurements Derived From Multiple ROI Measurements” |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (C0034375, UMLS, "Qualitative Evaluations") |
IFF ImagingObservationEntity elements are present in the source AIM object |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (C0034375, UMLS, "Qualitative Evaluations") > CODE |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imagingObservationEntityCollection/ImagingObservationEntity/questionTypeCode,typeCode |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (C0034375, UMLS, "Qualitative Evaluations") > TEXT |
||||||||
This section describes the mapping of TID 1501 “Measurement Group” in PS3.16 .
Table TID 1501. Mapping of Measurement Group
This section describes the mapping of TID 1502 “Time Point Context” in PS3.16 .
Table TID 1502. Mapping of Time Point Context
This section describes the mapping of TID 1410 “Planar ROI Measurements” in PS3.16 .
Table TID 1410. Mapping of Planar ROI Measurements
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (C67447, NCIt, "Activity Session") |
Identifies the session during which the measurements were made. The NCI Thesaurus definition is "time, period, or term devoted to some activity". |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (112039, DCM, "Tracking Identifier") |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/name/@value |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (112040, DCM, "Tracking Unique Identifier") |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/uniqueIdentifier/@root |
Using ImageAnnotation/uniqueIdentifier as a proxy for Tracking Unique Identifier does not allow longitudinal identification of the same lesion because ImageAnnotation/uniqueIdentifier must be unique to each AIM annotation file; only ImageAnnotation/name can be used to recognize commonality. |
||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121071, DCM, "Finding") |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/typeCode |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (111030, DCM, "Image Region") |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/twoDimensionSpatialCoordinateCollection/TwoDimensionSpatialCoordinate |
A Graphic Type of MULTIPOINT is not permitted in the DICOM template. |
||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (111030, DCM, "Image Region") > IMAGE |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/imageReferenceUid/@root, referencedFrameNumber/@value |
The Referenced SOP Class UID is obtained from imageReferenceEntityCollection; see Table A.8-5 |
||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121214, DCM, "Referenced Segmentation Frame") |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/segmentationEntityCollection/SegmentationEntity |
Reference shall be to a Segmentation Image, with a single value specified in Referenced Frame Number, and with a single value specified in Referenced Segment Number |
||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121233, DCM, "Source image for segmentation") |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/segmentationEntityCollection/SegmentationEntity/referencedSopInstanceUid/@root |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121200, DCM, "Illustration of ROI") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (126100, DCM, "Real World Value Map used for measurement") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $QualitativeEvaluations |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $QualitativeEvaluations |
||||||||
This section describes the mapping of TID 1411 “Volumetric ROI Measurements” in PS3.16 .
Table TID 1411. Mapping of Volumetric ROI Measurements
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (C67447, NCIt, "Activity Session") |
Identifies the session during which the measurements were made. The NCI Thesaurus definition is "time, period, or term devoted to some activity". |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (112039, DCM, "Tracking Identifier") |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/name/@value |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (112040, DCM, "Tracking Unique Identifier") |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/uniqueIdentifier/@root |
Using ImageAnnotation/uniqueIdentifier as a proxy for Tracking Unique Identifier does not allow longitudinal identification of the same lesion because ImageAnnotation/uniqueIdentifier must be unique to each AIM annotation file; only ImageAnnotation/name can be used to recognize commonality. |
||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121071, DCM, "Finding") |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/typeCode |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (111030, DCM, "Image Region") |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/twoDimensionSpatialCoordinateCollection/TwoDimensionSpatialCoordinate |
A Graphic Type of MULTIPOINT is not permitted in the DICOM template. |
||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (111030, DCM, "Image Region") > IMAGE |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/imageReferenceUid/@root, referencedFrameNumber/@value |
The Referenced SOP Class UID is obtained from imageReferenceEntityCollection; see Table A.8-5 |
||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121191, DCM, "Referenced Segment") |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/segmentationEntityCollection/SegmentationEntity |
Reference shall be to a Segmentation Image or Surface Segmentation object, with a single value specified in Referenced Segment Number |
||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121231, DCM, "Volume Surface") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121233, DCM, "Source image for segmentation") |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/segmentationEntityCollection/SegmentationEntity/referencedSopInstanceUid/@root |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121232, DCM, "Source series for segmentation") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121200, DCM, "Illustration of ROI") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (126100, DCM, "Real World Value Map used for measurement") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $QualitativeEvaluations |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imagingObservationEntityCollection/ImagingObservationEntity/imagingObservationCharacteristicCollection/ImagingObservationCharacteristic/questionTypeCode,typeCode |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $QualitativeEvaluations |
||||||||
This section describes the mapping of TID 1419 “ROI Measurements” in PS3.16 .
Table TID 1419. Mapping of ROI Measurements
This section describes the mapping of TID 1420 “Measurements Derived From Multiple ROI Measurements” in PS3.16 .
Table TID 1420. Mapping of Measurements Derived From Multiple ROI Measurements
|
(126000, DCM, "Imaging Measurement Report") > (126011, DCM, "Derived Imaging Measurements") > NUM |
CID 7465 “Measurements Derived From Multiple ROI Measurements” |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (126011, DCM, "Derived Imaging Measurements") > NUM > |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126011, DCM, "Derived Imaging Measurements") > NUM > |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (126011, DCM, "Derived Imaging Measurements") > NUM > |
Statistical and normal range properties are not used in AIM use cases for this mapping. |
|||||||
This section describes the mapping of TID 300 “Measurement” in PS3.16 .
Table TID 300. Mapping of Measurement
This section describes the mapping of TID 320 “Image or Spatial Coordinates” in PS3.16 .
Table TID 320. Mapping of Image or Spatial Coordinates
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Purpose |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/imageReferenceUid/@root, referencedFrameNumber/@value |
An entire image reference without spatial coordinates The Referenced SOP Class UID is obtained from imageReferenceEntityCollection; see Table A.8-5 Only the by-value (SELECTED FROM) relationship is used, not the by-reference (R-SELECTED FROM) relationship. |
||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Purpose |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/twoDimensionSpatialCoordinateCollection/TwoDimensionSpatialCoordinate |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Purpose > IMAGE |
ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/imageReferenceUid/@root, referencedFrameNumber/@value |
The Referenced SOP Class UID is obtained from imageReferenceEntityCollection; see Table A.8-5 Only the by-value (SELECTED FROM) relationship is used, not the by-reference (R-SELECTED FROM) relationship. |
This section describes the mapping of PS3.16 TID 4019 “Algorithm Identification” in PS3.16 .
Table TID 4019. Mapping of Algorithm Identification
This section describes the mapping of TID 4108 “Tracking Identifier” in PS3.16 .
For the purpose of this mapping, this template is not used to track individual measurements; rather, the corresponding content items defined in Section TID 1501 “Mapping of Measurement Group” are mapped at the Measurement Group level instead.
Table TID 4108. Mapping of Tracking Identifier
This section describes the mapping of TID 1204 “Language of Content Item and Descendants” in PS3.16 .
Table TID 1204. Mapping of Language of Content Item and Descendants
|
(126000, DCM, "Imaging Measurement Report") > (121049, DCM, "Language of Content Item and Descendants") |
Not used in AIM; discarded if present in DICOM SR. CID 5000 “Languages” |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (121049, DCM, "Language of Content Item and Descendants") > (121046, DCM, "Country of Language") |
Not used in AIM; discarded if present in DICOM SR. CID 5001 “Countries” |
This section describes the mapping of TID 1001 “Observation Context” in PS3.16 .
Table TID 1001. Mapping of Observation Context
This section describes the mapping of TID 1002 “Observer Context” in PS3.16 .
Table TID 1002. Mapping of Observer Context
|
(126000, DCM, "Imaging Measurement Report") > (121005, DCM, "Observer Type") |
Since this template is only used for AIM for person observers, which is the default, it may be omitted or explicitly sent as (121006, DCM, "Person"); see also CID 270 “Observer Type” |
|||||||
|
TID 1003 “Mapping of Person Observer Identifying Attributes” |
IFF Row 1 value = (121006, DCM, "Person") or Row 1 is absent |
|||||||
This section describes the mapping of TID 1003 “Person Observer Identifying Attributes” in PS3.16 .
Table TID 1003. Mapping of Person Observer Identifying Attributes
This section describes the mapping of TID 1600 “Image Library” in PS3.16 .
Table TID 1600. Mapping of Image Library
This section describes the mapping of TID 1601 “Image Library Entry” in PS3.16 .
Table TID 1601. Mapping of Image Library Entry
This section describes the mapping of TID 1602 “Image Library Entry Descriptors” in PS3.16 .
Table TID 1602. Mapping of Image Library Entry Descriptors
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (121139, DCM, "Modality") |
/ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/imageSeries/modality/@code |
AIM does not formally define a value set but common usage is the set of code strings defined for the image Modality Attribute, and these have a 1:1 correspondence with the code values of CID 29 “Acquisition Modality”. |
||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (123014, DCM, "Target Region") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (111027, DCM, "Image Laterality") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (111060, DCM, "Study Date") |
/ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/startDate/@value |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (111061, DCM, "Study Time") |
/ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/startTime/@value |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (111018, DCM, "Content Date") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (111019, DCM, "Content Time") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (126201, DCM, "Acquisition Date") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (126202, DCM, "Acquisition Time") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (112227, DCM, "Frame of Reference UID") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (110910, DCM, "Pixel Data Rows") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (110911, DCM, "Pixel Data Columns") |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > |
TID 1603 "Image Library Entry Descriptors for Projection Radiography" |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > |
TID 1604 "Image Library Entry Descriptors for Cross-Sectional Modalities" |
|||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > |
||||||||
|
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > |
||||||||
This section describes a sample AIM v4 instance and the same content transformed into a DICOM SR TID 1500 instance.
<?xml version="1.0" encoding="UTF-8"?>
<ImageAnnotationCollection xmlns="gme://caCORE.caCORE/4.4/edu.northwestern.radiology.AIM" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" aimVersion="AIMv4_0" xsi:schemaLocation="gme://caCORE.caCORE/4.4/edu.northwestern.radiology.AIM AIM_v4_rv44_XML.xsd">
<uniqueIdentifier root="2.25.224793923339609181243139195858254344686"/>
<dateTime value="20170201180043"/>
<user>
<name value="Doe^Jane"/>
<loginName value="jdoe"/>
<roleInTrial/>
</user>
<equipment>
<manufacturerName value="Acme Medical Systems"/>
<manufacturerModelName value=""/>
<softwareVersion value="36.00"/>
</equipment>
<person>
<name value="CM-1-111-000000"/>
<id value="293761767066931586407385203810190772174"/>
<birthDate value="19600101000000"/>
<sex value="M"/>
<ethnicGroup/>
</person>
<imageAnnotations>
<ImageAnnotation>
<uniqueIdentifier root="2.25.56002466128627498886935079903172938041"/>
<typeCode code="M-01100" codeSystemName="SRT">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Lesion"/>
</typeCode>
<dateTime value="20170201180043"/>
<name value="Lesion1"/>
<comment value="PT / WB NAC P600 / 0"/>
<calculationEntityCollection>
<CalculationEntity>
<uniqueIdentifier root="0"/>
<typeCode code="126401" codeSystemName="DCM">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="SUVbw"/>
</typeCode>
<typeCode code="R-404FB" codeSystemName="SRT">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Minimum"/>
</typeCode>
<description value="SUVbw Minimum"/>
<mathML/>
<calculationResultCollection>
<CalculationResult type="Scalar" xsi:type="CompactCalculationResult">
<unitOfMeasure value="g/ml{SUVbw}"/>
<dataType code="C48870" codeSystemName="NCI">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Double"/>
</dataType>
<dimensionCollection>
<Dimension>
<index value="0"/>
<size value="1"/>
<label value="Minimum"/>
</Dimension>
</dimensionCollection>
<value value="1.98024"/>
</CalculationResult>
</calculationResultCollection>
<algorithm>
<name value="Descriptive Statistics Calculator"/>
<type code="RID12780" codeSystemName="RadLex" codeSystemVersion="3.2">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Calculation"/>
</type>
<version value="1.0"/>
</algorithm>
</CalculationEntity>
<CalculationEntity>
<uniqueIdentifier root="0"/>
<typeCode code="126401" codeSystemName="DCM">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="SUVbw"/>
</typeCode>
<typeCode code="G-A437" codeSystemName="SRT">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Maximum"/>
</typeCode>
<description value="SUVbw Maximum"/>
<mathML/>
<calculationResultCollection>
<CalculationResult type="Scalar" xsi:type="CompactCalculationResult">
<unitOfMeasure value="g/ml{SUVbw}"/>
<dataType code="C48870" codeSystemName="NCI">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Double"/>
</dataType>
<dimensionCollection>
<Dimension>
<index value="0"/>
<size value="1"/>
<label value="Maximum"/>
</Dimension>
</dimensionCollection>
<value value="5.68816"/>
</CalculationResult>
</calculationResultCollection>
<algorithm>
<name value="Descriptive Statistics Calculator"/>
<type code="RID12780" codeSystemName="RadLex" codeSystemVersion="3.2">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Calculation"/>
</type>
<version value="1.0"/>
</algorithm>
</CalculationEntity>
<CalculationEntity>
<uniqueIdentifier root="0"/>
<typeCode code="126401" codeSystemName="DCM">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="SUVbw"/>
</typeCode>
<typeCode code="R-00317" codeSystemName="SRT">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Mean"/>
</typeCode>
<description value="SUVbw Mean"/>
<mathML/>
<calculationResultCollection>
<CalculationResult type="Scalar" xsi:type="CompactCalculationResult">
<unitOfMeasure value="g/ml{SUVbw}"/>
<dataType code="C48870" codeSystemName="NCI">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Double"/>
</dataType>
<dimensionCollection>
<Dimension>
<index value="0"/>
<size value="1"/>
<label value="Mean"/>
</Dimension>
</dimensionCollection>
<value value="2.329186593407"/>
</CalculationResult>
</calculationResultCollection>
<algorithm>
<name value="Descriptive Statistics Calculator"/>
<type code="RID12780" codeSystemName="RadLex" codeSystemVersion="3.2">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Calculation"/>
</type>
<version value="1.0"/>
</algorithm>
</CalculationEntity>
<CalculationEntity>
<uniqueIdentifier root="0"/>
<typeCode code="126401" codeSystemName="DCM">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="SUVbw"/>
</typeCode>
<typeCode code="R-10047" codeSystemName="SRT">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Standard Deviation"/>
</typeCode>
<description value="SUVbw Standard Deviation"/>
<mathML/>
<calculationResultCollection>
<CalculationResult type="Scalar" xsi:type="CompactCalculationResult">
<unitOfMeasure value="g/ml{SUVbw}"/>
<dataType code="C48870" codeSystemName="NCI">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Double"/>
</dataType>
<dimensionCollection>
<Dimension>
<index value="0"/>
<size value="1"/>
<label value="Standard Deviation"/>
</Dimension>
</dimensionCollection>
<value value="1.8828952323684"/>
</CalculationResult>
</calculationResultCollection>
<algorithm>
<name value="Descriptive Statistics Calculator"/>
<type code="RID12780" codeSystemName="RadLex" codeSystemVersion="3.2">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Calculation"/>
</type>
<version value="1.0"/>
</algorithm>
</CalculationEntity>
</calculationEntityCollection>
<segmentationEntityCollection>
<SegmentationEntity xsi:type="DicomSegmentationEntity">
<uniqueIdentifier root="2.25.318310842062810077214341266367812728264"/>
<sopInstanceUid root="2.25.134884066033959077306435705240550195701"/>
<sopClassUid root="1.2.840.10008.5.1.4.1.1.66.4"/>
<referencedSopInstanceUid root="2.25.319214308104243787945491694789635628411"/>
<segmentNumber value="1"/>
</SegmentationEntity>
</segmentationEntityCollection>
<imageReferenceEntityCollection>
<ImageReferenceEntity xsi:type="DicomImageReferenceEntity">
<uniqueIdentifier root="2.25.239108061065263370785162033783811931375"/>
<imageStudy>
<instanceUid root="2.25.52186905385055707830834793159643714079"/>
<startDate value="20170113"/>
<startTime value="070844"/>
<imageSeries>
<instanceUid root="2.25.263500776851326986665835510707132143772"/>
<modality code="PT" codeSystemName="DCM" codeSystemVersion="20121129">
<iso:displayName xmlns:iso="uri:iso.org:21090" value="Positron emission tomography"/>
</modality>
<imageCollection>
<Image>
<sopClassUid root="1.2.840.10008.5.1.4.1.1.128"/>
<sopInstanceUid root="2.25.319214308104243787945491694789635628411"/>
</Image>
</imageCollection>
</imageSeries>
</imageStudy>
</ImageReferenceEntity>
</imageReferenceEntityCollection>
</ImageAnnotation>
</imageAnnotations>
</ImageAnnotationCollection>
A compact representation of the semantic content of the transformed DICOM SR tree is shown here:
1: : CONTAINER: (126000,DCM,"Imaging Measurement Report") [SEPARATE] (DCMR,1500)
>1.1: HAS CONCEPT MOD: CODE: (121049,DCM,"Language of Content Item and Descendants") = (eng,RFC5646,"English")
>>1.1.1: HAS CONCEPT MOD: CODE: (121046,DCM,"Country of Language") = (US,ISO3166_1,"United States")
>1.2: HAS OBS CONTEXT: PNAME: (121008,DCM,"Person Observer Name") = "Doe^Jane"
>1.3: HAS OBS CONTEXT: TEXT: (128774,DCM,"Person Observer's Login Name") = "jdoe"
>1.4: HAS CONCEPT MOD: CODE: (121058,DCM,"Procedure reported") = (44139-4,LN,"PET whole body")
>1.5: CONTAINS: CONTAINER: (111028,DCM,"Image Library") [SEPARATE]
>>1.5.1: CONTAINS: CONTAINER: (126200,DCM,"Image Library Group") [SEPARATE]
>>>1.5.1.1: CONTAINS: IMAGE: = (1.2.840.10008.5.1.4.1.1.128,2.25.319214308104243787945491694789635628411)
>>>1.5.1.2: HAS ACQ CONTEXT: CODE: (121139,DCM,"Modality") = (PT,DCM,"Positron emission tomography")
>>>1.5.1.3: HAS ACQ CONTEXT: DATE: (111060,DCM,"Study Date") = "20170113"
>>>1.5.1.4: HAS ACQ CONTEXT: TIME: (111061,DCM,"Study Time") = "070844"
>1.6: CONTAINS: CONTAINER: (126010,DCM,"Imaging Measurements") [SEPARATE]
>>1.6.1: CONTAINS: CONTAINER: (125007,DCM,"Measurement Group") [SEPARATE]
>>>1.6.1.1: HAS OBS CONTEXT: TEXT: (112039,DCM,"Tracking Identifier") = "Lesion1"
>>>1.6.1.2: HAS OBS CONTEXT: UIDREF: (112040,DCM,"Tracking Unique Identifier") = "2.25.56002466128627498886935079903172938041"
>>>1.6.1.3: CONTAINS: CODE: (121071,DCM,"Finding") = (M-01100,SRT,"Lesion")
>>>1.6.1.4: CONTAINS: IMAGE: (121191,DCM,"Referenced Segment") = (1.2.840.10008.5.1.4.1.1.66.4,2.25.134884066033959077306435705240550195701) [Segment 1]
>>>1.6.1.5: CONTAINS: NUM: (126401,DCM,"SUVbw") = 1.98024 (g/ml{SUVbw},UCUM,"Standardized Uptake Value body weight")
>>>>1.6.1.5.1: HAS CONCEPT MOD: CODE: (121401,DCM,"Derivation") = (R-404FB,SRT,"Minimum")
>>>>1.6.1.5.2: HAS CONCEPT MOD: TEXT: (111001,DCM,"Algorithm Name") = "Descriptive Statistics Calculator"
>>>>1.6.1.5.3: HAS CONCEPT MOD: TEXT: (111003,DCM,"Algorithm Version") = "1.0"
>>>1.6.1.6: CONTAINS: NUM: (126401,DCM,"SUVbw") = 5.68816 (g/ml{SUVbw},UCUM,"Standardized Uptake Value body weight")
>>>>1.6.1.6.1: HAS CONCEPT MOD: CODE: (121401,DCM,"Derivation") = (G-A437,SRT,"Maximum")
>>>>1.6.1.6.2: HAS CONCEPT MOD: TEXT: (111001,DCM,"Algorithm Name") = "Descriptive Statistics Calculator"
>>>>1.6.1.6.3: HAS CONCEPT MOD: TEXT: (111003,DCM,"Algorithm Version") = "1.0"
>>>1.6.1.7: CONTAINS: NUM: (126401,DCM,"SUVbw") = 2.329186593407 (g/ml{SUVbw},UCUM,"Standardized Uptake Value body weight")
>>>>1.6.1.7.1: HAS CONCEPT MOD: CODE: (121401,DCM,"Derivation") = (R-00317,SRT,"Mean")
>>>>1.6.1.7.2: HAS CONCEPT MOD: TEXT: (111001,DCM,"Algorithm Name") = "Descriptive Statistics Calculator"
>>>>1.6.1.7.3: HAS CONCEPT MOD: TEXT: (111003,DCM,"Algorithm Version") = "1.0"
>>>1.6.1.8: CONTAINS: NUM: (126401,DCM,"SUVbw") = 1.8828952323684 (g/ml{SUVbw},UCUM,"Standardized Uptake Value body weight")
>>>>1.6.1.8.1: HAS CONCEPT MOD: CODE: (121401,DCM,"Derivation") = (R-10047,SRT,"Standard Deviation")
>>>>1.6.1.8.2: HAS CONCEPT MOD: TEXT: (111001,DCM,"Algorithm Name") = "Descriptive Statistics Calculator"
>>>>1.6.1.8.3: HAS CONCEPT MOD: TEXT: (111003,DCM,"Algorithm Version") = "1.0"
The AIM sample transformed into SR illustrated at the Attribute encoding level shown in Table A.7.2-1 includes information on the SR document body tree depth (column 1: SR Tree Depth), nesting level for nested artifacts such as sequences and sequence items (column 2: Nesting), DICOM attribute names (column 3: Attribute), DICOM tag (column 4: Tag), the DICOM attribute value representation (Column 5: VR as specified in PS3.5), the hexadecimal value of value length (column 6: VL (hex)) and the sample document attribute values (column 7: Value).