Transformations between DICOM and other Representations

Download

PS3.21

DICOM PS3.21 2024d - Transformations between DICOM and other Representations

DICOM Standards Committee

A DICOM® publication

Table of Contents

Notice and Disclaimer

Foreword

1. Scope and Field of Application

2. Normative and Informative References

Bibliography

3. Definitions

Glossary

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.3.1. Header

A.3.2. Document Body

A.3.2.1. DICOM SR "Measurement Report" Template Structure
A.3.2.2. Mapping Considerations
A.3.2.3. DICOM Composite Object References

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.7.1. Source AIM v4 Instance
A.7.2. Target DICOM SR "Measurement Report" (TID 1500)

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

Notice and Disclaimer

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.

Foreword

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].

1 Scope and Field of Application

This Part of the DICOM Standard specifies the transformations between DICOM and other representations of the same information.

Currently, this Part addresses:

compatible components of the NCI Annotation and Image Markup (AIM) to and from DICOM SR Measurement Templates, applicable to quantitative and categorical description of regions of interest in images

Transformation of diagnostic imaging reports between DICOM SR and HL7 CDA representations is addressed in PS3.20.

2 Normative and Informative References

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] ISO/IEC. 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 .

[IEEE 754] IEEE. 1985. 32-bit and 64-bit Floating Point Number Representations.

[ISO 21090] ISO. 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] HL7. 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] W3C. 2006/09/29. Extensible Markup Language (XML) 1.1. http://www.w3.org/TR/2006/REC-xml11-20060816/ .

[XSD Datatypes] W3C. 2004/10/28. XML Schema Part 2: Datatypes. http://www.w3.org/TR/xmlschema-2/ .

[AIM v3 v4 changes] NCI. 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.2] NCI. 2018/02. Annotation and Image Markup model version 4.2. https://wiki.nci.nih.gov/display/AIM/Annotation+and+Image+Markup+-+AIM#AnnotationandImageMarkup-AIM-AIMModel .

[Extending AIM] NCI. 2014/12/03. Extending the AIM Model. https://wiki.nci.nih.gov/display/AIM/Extending+the+AIM+Model .

[caBIG™ AIM] J Digit Imaging. Channin, David S, Mongkolwat, Pattanasak, Kleper, Vladimir, Sepukar, Kastubh, and Rubin, Daniel L. 2010/04. 23. 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. Mongkolwat, Pattanasak, Channin, David S, Kleper, Vladimir, and Rubin, Daniel. 2012/07. 32. 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. Mongkolwat, Pattanasak, Kleper, Vladimir, Talbot, Skip, and Rubin, Daniel. 2014/12. 27. 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/ .

3 Definitions

For the purposes of this Standard the following definitions apply.

3.1 Codes and Controlled Terminology Definitions:

This Part of the Standard makes use of the following terms defined in PS3.16:

Coding Scheme: See Coding Scheme in PS3.16 .
Context Group: See Context Group in PS3.16 .
Context ID (CID): See Context ID in PS3.16 .
Template: See Template in PS3.16 .
Template ID (TID): See Template ID in PS3.16 .

3.2 DICOM Introduction and Overview Definitions:

This Part of the Standard makes use of the following terms defined in PS3.1:

Attribute: See Attribute in PS3.1 .
Service-Object Pair Class (SOP Class): See Service-Object Pair Class in PS3.1 .

3.3 DICOM Service Class Definitions:

This Part of the Standard makes use of the following terms defined in PS3.4:

Service-Object Pair Instance (SOP Instance): See Service-Object Pair Instance in PS3.4 .

3.4 DICOM Information Object Definitions:

This Part of the Standard makes use of the following terms defined in PS3.3:

Attribute Macro: See Attribute Macro in PS3.3 .
Content Item: See Content Item in PS3.3 .
Content Tree: See Content Tree in PS3.3 .
Module: See Module in PS3.3 .

3.5 DICOM Data Structures and Encoding

This Part of the Standard makes use of the following terms defined in PS3.5:

Data Set: See Data Set in PS3.5 .
Value Multiplicity (VM): See Value Multiplicity in PS3.5 .
Value Representation (VR): See Value Representation in PS3.5 .

4 Symbols and Abbreviations

The following symbols and abbreviations are used in this Part of the Standard.

AIM: Annotation and Image Markup
DICOM: Digital Imaging and Communications in Medicine
IOD: Information Object Definition
ISO: International Standards Organization
NCI: National Cancer Institute
NEMA: National Electrical Manufacturers Association
OID: Object Identifier (ISO 8824)
SR: Structured Reporting
UCUM: Unified Code for Units of Measure
UID: Unique Identifier
XML: Extensible Markup Language
XSLT: Extensible Stylesheet Language Transformations

5 Conventions

Terms listed in Section 3 Definitions are capitalized throughout the document.

A Transformation Between AIM and DICOM SR

A.1 Scope and Field of Application

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.

A.2 Use Cases

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.

Figure A.2-1. Annotation Creation and Transformation

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.2 model allows for the encoding of multiple marked up regions and multiple measurements in a single annotation instance, and unlike earlier AIM model versions provides mechanisms for identifying which markup is associated with which measurement using AIM statements; otherwise it is 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, it is not only possible to encode in AIM (and map to TID 1500) the boundaries of and the area measurements derived from a planar volumetric ROI, it is also possible to encode the endpoints of the measured axes of the pair of linear measurements and their derived values.

A.3 Structure of DICOM SR Documents

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.

Figure A.3-1. SR Document Structure

A.3.1 Header

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

IE	Module	Reference	Usage	Transformation
Patient	Patient	C.7.1.1	M	Section A.6.1.1.1
Patient	Clinical Trial Subject	C.7.1.3	U	Section A.6.1.1.2
Study	General Study	C.7.2.1	M	Section A.6.1.1.3
	Patient Study	C.7.2.2	U	Section A.6.1.1.4
	Clinical Trial Study	C.7.2.3	U	Section A.6.1.1.5
Series	SR Document Series	C.17.1	M	Section A.6.1.1.6
Series	Clinical Trial Series	C.7.3.2	U	Section A.6.1.1.7
Equipment	General Equipment	C.7.5.1	M	Section A.6.1.1.8
Document	SR Document General	C.17.2	M	Section A.6.1.1.9
	SR Document Content	C.17.3	M	Section A.6.1.1.10
	SOP Common	C.12.1	M	Section A.6.1.1.11

Patient Module

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.

Clinical Trial Subject Module

The Clinical Trial Subject Module contains Attributes that identify a Patient as a clinical trial Subject.

General Study Module

The General Study Module specifies the Attributes that describe and identify the Study performed upon the Patient.

Patient Study Module

The Patient Study Module defines the Attributes that provide information about the Patient at the time the Study was performed.

Clinical Trial Study Module

The Clinical Trial Study Module contains Attributes that identify a Study in the context of a clinical trial.

SR Document Series Module

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.

Clinical Trial Series Module

The Clinical Trial Series Module contains Attributes that identify a Series in the context of a clinical trial.

General Equipment Module

The General Equipment Module specifies the Attributes that identify and describe the piece of equipment that produced a Series of Composite Instances.

SR Document General Module

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.

SOP Common Module

The SOP Common Module defines the Attributes that are required for proper functioning and identification of the associated SOP Instances.

SR Document Content Module

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).

A.3.2 Document Body

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.

A.3.2.1 DICOM SR "Measurement Report" Template Structure

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.

Figure A.3.2.1-1. Template Structure Summarized from PS 3.16

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.

A.3.2.2 Mapping Considerations

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.

A.3.2.3 DICOM Composite Object References

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.

A.4 Structure of AIM Version 4 Instances

AIM instances are encoded in XML according to a schema generated from the AIM Model [AIM Model v4.2], 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.

Figure A.4-1. AIM v4 Instance Structure

A.5 AIM v4 Structure

Version 4 of AIM makes use of [ISO 21090] data types. See Section A.8 “Overview of Data Types”.

A.6 AIM v4 to DICOM TID 1500 Mapping

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 Attribute 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.

A.6.1 Mapping of Constrained AIM v4

A.6.1.1 Header

General Remarks on the mapping of DICOM header Module Attributes:

SR Document General Module

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".

SOP Common Module

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.

A.6.1.1.1 Mapping of DICOM Patient Module

Table A.6.1.1.1-1. Mapping of DICOM Patient Module

DICOM Attribute	DICOM VR	DICOM VM	DICOM Usage Type	AIM Element or Attribute	AIM Data Type	AIM Multiplicity
PatientName	PN	1	2	ImageAnnotationCollection/person/name/@value	ST	0..1
PatientID	LO	1	2	ImageAnnotationCollection/person/id/@value	ST	0..1
PatientBirthDate	DA	1	2	ImageAnnotationCollection/person/birthDate/@value	TS	0..1
PatientSex	CS	1	2	ImageAnnotationCollection/person/sex/@value	ST	0..1
EthnicGroup	SH	1	3	ImageAnnotationCollection/person/ethnicGroup/@value	ST	0..1
SourcePatientGroupIdentificationSequence>PatientID	SQ	1	3	ImageAnnotationCollection/person/sourcePatientGroupId	ST	0..1

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. The AIM 4.2 model can optionally identify the group of animals imaged at the same time that corresponds to the DICOM SourcePatientGroupIdentificationSequence.

A.6.1.1.2 Mapping of DICOM Clinical Trial Subject Module

No mapping of the DICOM Clinical Trial Subject Module is described since no corresponding content is present in the AIM model.

A.6.1.1.3 Mapping of DICOM General Study Module

The AIM 4.2 model provides optional Study identification information. If available, this information shall be used during transformation from AIM to SR, otherwise 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.

If there is more than one DICOM Study referenced by the AIM object and explicit Study identification information (ImageAnnotationCollection/studyInstanceUid) is absent, 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 Section C.17.2.2 “Identical Documents Sequence” in PS3.3 .

Table A.6.1.1.3-1. Mapping of DICOM General Study Module

DICOM Attribute	DICOM VR	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	Data Type	Multiplicity	Comment
StudyInstanceUID	UI	1	1	New or derived from referenced image if not in source	ImageAnnotationCollection/studyInstanceUid/@root	II	0..1
StudyDate	UI	1	2	Empty if not in source	ImageAnnotationCollection/imageAnnotations/ImageAnnotation[1]/imageReferenceEntityCollection/ImageReferenceEntity[1]/imageStudy[1]/startDate/@value	TS	0..1
StudyTime	UI	1	2	Empty if not in source	ImageAnnotationCollection/imageAnnotations/ImageAnnotation[1]/imageReferenceEntityCollection/ImageReferenceEntity[1]/imageStudy[1]/startTime/@value	TS	0..1
ReferringPhysicianName	PN	1	2	Empty				Not in AIM.
StudyID	SH	1	2	Empty				Not in AIM.
AccessionNumber	SH	1	2	Empty if not in source				ImageAnnotationCollection/accessionNumber/@value.

A.6.1.1.4 Mapping of DICOM Patient Study Module

No mapping of the DICOM Patient Study Module is described since no corresponding content is present in the AIM model.

A.6.1.1.5 Mapping of DICOM Clinical Trial Study Module

No mapping of the DICOM Clinical Trial Study Module is described since no corresponding content is present in the AIM model.

A.6.1.1.6 Mapping of DICOM SR Document Series Module

The AIM 4.2 model optionally supports the concept that an annotation itself is part of a Series. If available, this information shall be used, otherwise a new Series shall be generated since a converted instance 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

DICOM Attribute	DICOM VR	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
Modality	CS	1	1	"SR"
SeriesInstanceUID	UI	1	1	New if not in source.	ImageAnnotationCollection/seriesInstanceUid/@root	II	0..1	Using a generated value means that multiple round-trips may produce different values. When mapping multiple AIM instances related to the same study, if the same SeriesInstanceUID is used they will appear in the same Series.
SeriesNumber	IS	1	1	7291				A well-known value means that multiple round-trips will use the same value.
ReferencedPerformedProcedureStepSequence	SQ	1	2	Empty

A.6.1.1.7 Mapping of DICOM Clinical Trial Series Module

No mapping of the DICOM Clinical Trial Series Module is described since no corresponding content is present in the AIM model.

A.6.1.1.8 Mapping of DICOM General Equipment Module

Table A.6.1.1.8-1. Mapping of DICOM General Equipment Module

DICOM Attribute	DICOM VR	DICOM VM	DICOM Usage Type	AIM Element or Attribute	AIM Data Type	AIM Multiplicity
Manufacturer	LO	1	2	ImageAnnotationCollection/equipment/manufacturer/@value	ST	0..1
ManufacturerModelName	LO	1	3	ImageAnnotationCollection/equipment/manufacturerModelName/@value	ST	0..1
SoftwareVersions	LO	1-n	3	ImageAnnotationCollection/equipment/softwareVersion/@value	ST	0..1

A.6.1.1.9 Mapping of DICOM SR Document General Module

Table A.6.1.1.9-1. Mapping of DICOM SR Document General Module

DICOM Attribute	DICOM VR	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	Data Type	Multiplicity	Comment
InstanceNumber	IS	1	1	New
CompletionFlag	CS	1	1	"COMPLETE"
VerificationFlag	CS	1	1	"UNVERIFIED"				Sending a value of "VERIFIED" would trigger the need to send the Verifying Observer Sequence, which is not described in this mapping.
ContentDate	DA	1	1		ImageAnnotationCollection/dateTime/@value	TS	1..1
ContentTime	TM	1	1		ImageAnnotationCollection/dateTime/@value	TS	1..1
AuthorObserverSequence	SQ	1-n	3					Don't send sequence at all if observer is a device rather than a human since the device is described in the General Equipment Module.
AuthorObserverSequence > ObserverType	CS	1	1	PSN				DICOM allows PSN or DEV.
AuthorObserverSequence > PersonName	PN	1	1C		ImageAnnotationCollection/user/name/@value	ST	1..1	If PSN.
AuthorObserverSequence > PersonIdentificationCodeSequence	SQ	1	2C	Empty				If PSN. Not in AIM.
AuthorObserverSequence > InstitutionName	SQ	1	2	Empty				Not in AIM.
AuthorObserverSequence > InstitutionCodeSequence	SQ	1	2	Empty				Not in AIM.
IdenticalDocumentsSequence	SQ	1	1C	UIDs of other identical converted instances.				Required if this document is stored with different SOP Instance UIDs in one or more other Studies
CurrentRequestedProcedureEvidenceSequence	SQ	1	1
CurrentRequestedProcedureEvidenceSequence>StudyInstanceUID	UI	1	1		ImageAnnotationCollection/imageAnnotations/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/instanceUid/@root ImageAnnotationCollection/imageAnnotations/ImageAnnotation/segmentationEntityCollection/SegmentationEntity/studyInstanceUid/@root	II, II	1..1, 0..1
CurrentRequestedProcedureEvidenceSequence>ReferencedSeriesSequence	SQ	1	1
CurrentRequestedProcedureEvidenceSequence>ReferencedSeriesSequence>SeriesInstanceUID	UI	1	1		ImageAnnotationCollection/imageAnnotations/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/imageSeries/instanceUid/@root ImageAnnotationCollection/imageAnnotations/ImageAnnotation/segmentationEntityCollection/SegmentationEntity/seriesInstanceUid/@root	II, II	1..1, 0..1
CurrentRequestedProcedureEvidenceSequence>ReferencedSeriesSequence>ReferencedSOPSequence	SQ	1	1
CurrentRequestedProcedureEvidenceSequence>ReferencedSeriesSequence>ReferencedSOPSequence>ReferencedSOPClassUID	UI	1	1		ImageAnnotationCollection/imageAnnotations/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/imageSeries/imageCollection/Image/sopClassUid/@root ImageAnnotationCollection/imageAnnotations/ImageAnnotation/segmentationEntityCollection/SegmentationEntity/sopClassUid/@root	II, II	1..1, 0..1	If the studyInstanceUid or seriesInstanceUid of a SegmentationEntity are absent, this reference cannot be included for that instance.
CurrentRequestedProcedureEvidenceSequence>ReferencedSeriesSequence>ReferencedSOPSequence>ReferencedSOPInstanceUID	UI	1	1		ImageAnnotationCollection/imageAnnotations/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/imageSeries/imageCollection/Image/sopInstanceUid/@root ImageAnnotationCollection/imageAnnotations/ImageAnnotation/segmentationEntityCollection/SegmentationEntity/sopInstanceUid/@root	II, II	1..1, 0..1	If the studyInstanceUid or seriesInstanceUid of a SegmentationEntity are absent, this reference cannot be included for that instance.
PerformedProcedureCodeSequence	SQ	1	2	Empty				Not in AIM.

A.6.1.1.10 Mapping of DICOM SR Document Content 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:

ValueType
ConceptNameCodeSequence
ObservationUID
ContentSequence

Each child Content Item with a "by-value" relationship with its parent also contains:

RelationshipType

The additional required Attributes in each Content Item depend on the ValueType:

TEXT - TextValue
DATETIME - DateTime
DATE - Date
TIME - Time
PNAME - PersonName
UIDREF - UID
NUM - MeasuredValueSequence, MeasuredValueSequence>NumericValue, MeasuredValueSequence>MeasurementUnitsCodeSequence
CODE - ConceptCodeSequence
COMPOSITE - ReferencedSOPSequence, ReferencedSOPSequence>ReferencedSOPClassUID, ReferencedSOPSequence>ReferencedSOPInstanceUID
IMAGE - ReferencedSOPSequence, ReferencedSOPSequence>ReferencedSOPClassUID, ReferencedSOPSequence>ReferencedSOPInstanceUID, ReferencedSOPSequence>ReferencedFrameNumber, ReferencedSOPSequence>ReferencedSegmentNumber
SCOORD - GraphicData, GraphicType
SCOORD3D - ReferencedFrameOfReferenceUID, GraphicData, GraphicType
CONTAINER - ContinuityOfContent, ContentTemplateSequence, ContentTemplateSequence>MappingResource, ContentTemplateSequence>TemplateIdentifier

ObservationUID is required for the following Content Items in order to propagate the aim:uniqueIdentifer information:

IMAGE - for (121191, DCM, "Referenced Segment") Content Item corresponding to aim:SegmentationEntity
CONTAINER - for (126200, DCM, "Image Library Group") Content Item corresponding to aim:ImageReferenceEntity
CONTAINER - for (125007, DCM, "Measurement Group") Content Item corresponding to aim:ImageAnnotation
NUM - for any Content Item corresponding to aim:CalculationEntity
SCOORD - for any Content Item corresponding to aim:MarkupEntity

ObservationDateTime is required for the following Content Items in order to propagate the aim:dateTime information:

CONTAINER - for (125007, DCM, "Measurement Group") Content Item corresponding to aim:ImageAnnotation

A.6.1.1.11 Mapping of DICOM SOP Common Module

Table A.6.1.1.11-1. Mapping of DICOM SOP Common Module

DICOM Attribute	DICOM VR	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
SOPClassUID	UI	1	1	"1.2.840.10008.5.1.4.1.1.88.22"				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".
SOPInstanceUID	UI	1	1	Generated if more than one converted instance in separate studies.	ImageAnnotationCollection>uniqueIdentifier/@root	II	1..1
SpecificCharacterSet	CS	1	1	"ISO_IR 192"				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.

A.6.1.2 Content Tree

TID 1500 Mapping of Measurement Report

This section describes the mapping of TID 1500 “Measurement Report” in PS3.16 .

Table TID 1500. Mapping of Measurement Report

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report")	CONTAINER	1	M					The fixed Concept Name code is an appropriate choice selected from CID 7021 “Measurement Report Document Title” in the absence of a "document title" concept in AIM. If out of band information is available, a more appropriate code can be used.
(126000, DCM, "Imaging Measurement Report") >	INCLUDE	1	M	TID 1204 “Mapping of Language of Content Item and Descendants”
(126000, DCM, "Imaging Measurement Report") >	INCLUDE	1	M	TID 1001 “Mapping of Observation Context”
(126000, DCM, "Imaging Measurement Report") > (121058, DCM, "Procedure reported")	CODE	1-n	M	(363679005, SCT, "Imaging procedure")				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 Procedure” cannot be used. If out of band information is available, a more appropriate code can be used.
(126000, DCM, "Imaging Measurement Report") >	INCLUDE	1	M	TID 1600 “Mapping of Image Library”
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements")	CONTAINER	1	C					IFF measurements are present in the source AIM object
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") >	INCLUDE	1-n	U	TID 1410 “Mapping of Planar ROI Measurements”
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") >	INCLUDE	1-n	U	TID 1411 “Mapping of Volumetric ROI Measurements”
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") >	INCLUDE	1-n	U	TID 1501 “Mapping of Measurement Group”
(126000, DCM, "Imaging Measurement Report") > (126011, DCM, "Derived Imaging Measurements")	CONTAINER	1	C					Not applicable to current use cases
(126000, DCM, "Imaging Measurement Report") > (126011, DCM, "Derived Imaging Measurements") >	INCLUDE	1-n	U	TID 1420 “Mapping of Measurements Derived From Multiple ROI Measurements”
(126000, DCM, "Imaging Measurement Report") > (C0034375, UMLS, "Qualitative Evaluations")	CONTAINER	1	C					IFF ImagingObservationEntity elements are present in the source AIM object
(126000, DCM, "Imaging Measurement Report") > (C0034375, UMLS, "Qualitative Evaluations") > CODE	CODE	1-n	U		NAME = ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imagingObservationEntityCollection/ImagingObservationEntity/imagingObservationCharacteristicCollection/ImagingObservationCharacteristic/questionTypeCode or NAME = ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imagingObservationEntityCollection/ImagingObservationEntity/typeCode VALUE = ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imagingObservationEntityCollection/ImagingObservationEntity/imagingObservationCharacteristicCollection/ImagingObservationCharacteristic/typeCode	CD, CD	1, 0..1	The concept name may be encoded as a specific questionTypeCode for the ImagingObservationCharacteristic or inherited from the typeCode of the parent ImagingObservationEntity.
(126000, DCM, "Imaging Measurement Report") > (C0034375, UMLS, "Qualitative Evaluations") > TEXT	TEXT	1-n	U					Not used in AIM

TID 1501 Mapping of Measurement Group

This section describes the mapping of TID 1501 “Measurement and Qualitative Evaluation Group” in PS3.16 .

Table TID 1501. Mapping of Measurement Group

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group")	CONTAINER	1	M		ImageAnnotationCollection/imageAnnotations/ImageAnnotation			The value of aim:uniqueIdentifier/@root is mapped to the ObservationUID Attribute of the CONTAINER. The value of aim:dateTime/@root is mapped to the ObservationDateTimeAttribute of the CONTAINER.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (C67447, NCIt, "Activity Session")	TEXT	1	U					Not present in AIM. 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")	TEXT	1	M		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/name/@value	ST	1
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (112040, DCM, "Tracking Unique Identifier")	UIDREF	1	M		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/trackingUniqueIdentifier/@root	II	1	If trackingUniqueIdentifier is absent, then ImageAnnotation/uniqueIdentifier may be used as a proxy for Tracking Unique Identifier, but this does not allow longitudinal identification of the same lesion because ImageAnnotation/uniqueIdentifier must be unique to each AIM annotation file, in which case 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")	CODE	1	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/typeCode	CD	1..n	Only a single aim:typeCode value can be mapped.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") >	INCLUDE	1	U	TID 1502 “Mapping of Time Point Context”				Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (370129005, SCT, "Measurement Method")	CODE	1	U					Not used in AIM at this level.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (363698007, SCT, "Finding Site")	CODE	1-n	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imagingPhysicalEntityCollection/ImagingPhysicalEntity[label/@value='Location' or label/@value='Lobar Location' or label/@value='Segmental Location' or label/@value='Organ Type']/typeCode	CD	1..n	If a paired structure in AIM, this entry will pre-coordinate the laterality with the site.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (363698007, SCT, "Finding Site") > (272741003, SCT, "Laterality")	CODE	1	U					CID 244 “Laterality” Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (363698007, SCT, "Finding Site") > (106233006, SCT, "Topographical modifier")	CODE	1	U					Not used since AIM does not have a mechanism for post-coordinating the location.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (126100, DCM, "Real World Value Map used for measurement")	COMPOSITE	1	U					Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") >	INCLUDE	1-n	M	TID 300 “Mapping of Measurement”
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $QualitativeEvaluations	CODE	1-n	U					Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121106, DCM, "Comment")	TEXT	1-n	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/comment/@value			The parameter $QualitativeEvaluations is not used in AIM, but this TEXT content item is used to map the AIM comment as if it were a Qualitative Evaluation.

TID 1502 Mapping of Time Point Context

This section describes the mapping of TID 1502 “Time Point Context” in PS3.16 .

Table TID 1502. Mapping of Time Point Context

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Comment
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (126070, DCM, "Subject Time Point Identifier")	TEXT	1	U	Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (126071, DCM, "Protocol Time Point Identifier")	TEXT	1	U	Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (C2348792, UMLS, "Time Point")	TEXT	1	M	Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (126072, DCM, "Time Point Type")	CODE	1-n	U	BCID 6146 “Time Point Type” Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (126073, DCM, "Time Point Order")	NUM	1	U	Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (128740, DCM, "Longitudinal Temporal Offset from Event")	NUM	1	U	Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (128740, DCM, "Longitudinal Temporal Offset from Event") > (128741, DCM, "Longitudinal Temporal Event Type")	CODE	1	U	Not used in AIM.

TID 1410 Mapping of Planar ROI Measurements

This section describes the mapping of TID 1410 “Planar ROI Measurements and Qualitative Evaluations” in PS3.16 .

Table TID 1410. Mapping of Planar ROI Measurements

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group")	CONTAINER	1	M		ImageAnnotationCollection/imageAnnotations/ImageAnnotation			The value of aim:uniqueIdentifier/@root is mapped to the ObservationUID Attribute of the CONTAINER. The value of aim:dateTime/@root is mapped to the ObservationDateTimeAttribute of the CONTAINER.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (C67447, NCIt, "Activity Session")	TEXT	1	U					Not present in AIM. 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")	TEXT	1	M		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/name/@value	ST	1
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (112040, DCM, "Tracking Unique Identifier")	UIDREF	1	M		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/trackingUniqueIdentifier/@root	II	1	If trackingUniqueIdentifier is absent, then ImageAnnotation/uniqueIdentifier may be used as a proxy for Tracking Unique Identifier, but this does not allow longitudinal identification of the same lesion because ImageAnnotation/uniqueIdentifier must be unique to each AIM annotation file, in which case 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")	CODE	1	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/typeCode	CD	1..n	Only a single aim:typeCode value can be mapped.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") >	INCLUDE	1	U	TID 1502 “Mapping of Time Point Context”				Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (111030, DCM, "Image Region")	SCOORD	1	MC		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/twoDimensionSpatialCoordinateCollection/TwoDimensionSpatialCoordinate			A Graphic Type of MULTIPOINT is not permitted in the DICOM template. One or more MarkupEntity instances within an ImageAnnotation instance may be constrained to be associated with particular NUM measurement(s) in the included TID 1419 by a CalculationEntityReferencesMarkupEntityStatement.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (111030, DCM, "Image Region") > IMAGE	IMAGE	1	M		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/imageReferenceUid/@root, referencedFrameNumber/@value	II, INT	1, 0..1	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")	IMAGE	1	MC		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. The value of aim:uniqueIdentifier/@root is mapped to the ObservationUID Attribute of the IMAGE. One or more Segmentation references within an ImageAnnotation instance may be constrained to be associated with particular NUM measurement(s) in the included TID 1419 by a CalculationEntityReferencesSegmentationEntityStatement.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121233, DCM, "Source image for segmentation")	IMAGE	1	MC		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")	IMAGE	1	U					Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (126100, DCM, "Real World Value Map used for measurement")	COMPOSITE	1	U					Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") >	INCLUDE	1	M	TID 1419 “Mapping of ROI Measurements”
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $QualitativeEvaluations	CODE	1-n	U					Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121106, DCM, "Comment")	TEXT	1-n	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/comment/@value			The parameter $QualitativeEvaluations is not used in AIM, but this TEXT content item is used to map the AIM comment as if it were a Qualitative Evaluation

TID 1411 Mapping of Volumetric ROI Measurements

This section describes the mapping of TID 1411 “Volumetric ROI Measurements and Qualitative Evaluations” in PS3.16 .

Table TID 1411. Mapping of Volumetric ROI Measurements

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group")	CONTAINER	1	M		ImageAnnotationCollection/imageAnnotations/ImageAnnotation			The value of aim:uniqueIdentifier/@root is mapped to the ObservationUID Attribute of the CONTAINER. The value of aim:dateTime/@root is mapped to the ObservationDateTimeAttribute of the CONTAINER.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (C67447, NCIt, "Activity Session")	TEXT	1	U					Not present in AIM. 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")	TEXT	1	M		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/name/@value	ST	1
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (112040, DCM, "Tracking Unique Identifier")	UIDREF	1	M		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/trackingUniqueIdentifier/@root	II	1	If trackingUniqueIdentifier is absent, then ImageAnnotation/uniqueIdentifier may be used as a proxy for Tracking Unique Identifier, but this does not allow longitudinal identification of the same lesion because ImageAnnotation/uniqueIdentifier must be unique to each AIM annotation file, in which case 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")	CODE	1	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/typeCode	CD	1..n	Only a single aim:typeCode value can be mapped.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") >	INCLUDE	1	U	TID 1502 “Mapping of Time Point Context”				Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (111030, DCM, "Image Region")	SCOORD	1-n	MC		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/twoDimensionSpatialCoordinateCollection/TwoDimensionSpatialCoordinate	REAL	1..n	A Graphic Type of MULTIPOINT is not permitted in the DICOM template. The value of aim:MarkupEntity/aim:uniqueIdentifier/@root is mapped to the ObservationUID Attribute of the SCOORD. One or more MarkupEntity instances within an ImageAnnotation instance may be constrained to be associated with particular NUM measurement(s) in the included TID 1419 by a CalculationEntityReferencesMarkupEntityStatement.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (111030, DCM, "Image Region") > IMAGE	IMAGE	1	M		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/imageReferenceUid/@root, referencedFrameNumber/@value	II, INT	1, 0..1	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")	IMAGE	1	MC		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/segmentationEntityCollection/SegmentationEntity	INT	0..1	Reference shall be to a Segmentation Image or Surface Segmentation object, with a single value specified in Referenced Segment Number. One or more Segmentation references within an ImageAnnotation instance may be constrained to be associated with particular NUM measurement(s) in the included TID 1419 by a CalculationEntityReferencesSegmentationEntityStatement
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121231, DCM, "Volume Surface")	SCOORD3D	1	MC					Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121233, DCM, "Source image for segmentation")	IMAGE	1-n	MC		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")	UIDREF	1	MC					Not used in AIM
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121200, DCM, "Illustration of ROI")	IMAGE	1-n	U					Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (126100, DCM, "Real World Value Map used for measurement")	COMPOSITE	1	U					Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") >	INCLUDE	1	M	TID 1419 “Mapping of ROI Measurements”
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $QualitativeEvaluations	CODE	1-n	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imagingObservationEntityCollection/ImagingObservationEntity/imagingObservationCharacteristicCollection/ImagingObservationCharacteristic/questionTypeCode,typeCode	CD, CD	1, 0..1
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (121106, DCM, "Comment")	TEXT	1-n	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/comment/@value			The parameter $QualitativeEvaluations is not used in AIM, but this TEXT content item is used to map the AIM comment as if it were a Qualitative Evaluation.

TID 1419 Mapping of ROI Measurements

This section describes the mapping of TID 1419 “ROI Measurements” in PS3.16 .

Table TID 1419. Mapping of ROI Measurements

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (370129005, SCT, "Measurement Method")	CODE	1	U					Not encoded in AIM at this level.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (363698007, SCT, "Finding Site")	CODE	1-n	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imagingPhysicalEntityCollection/ImagingPhysicalEntity[label/@value='Location' or label/@value='Lobar Location' or label/@value='Segmental Location' or label/@value='Organ Type']/typeCode	CD	1..n	The finding site is factored out since it is common to all measurements in this group. If a paired structure in AIM, this entry will pre-coordinate the laterality with the site.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (363698007, SCT, "Finding Site") > (272741003, SCT, "Laterality")	CODE	1	U					Not used since AIM does not have a mechanism for post-coordinating the location.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > (363698007, SCT, "Finding Site") > (106233006, SCT, "Topographical modifier")	CODE	1	U					Not used since AIM does not have a mechanism for post-coordinating the location.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement	NUM	1-n	M		NAME = ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/typeCode[1] VALUE = ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/calculationResultCollection/CalculationResult/@value, calculationDataCollection/CalculationData/@value UNITS = ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/calculationResultCollection/CalculationResult/unitOfMeasure	CD, ST, CD	1..n, 0..n, 1	The first typeCode entry is assumed to be the primary concept. Other typeCode entries may be considered as modifiers. Value may be found in either CompactCalculationResult (i.e., value child of CalculationResult) or first value of ExtendedCalculationResult (i.e., nested within calculationResultCollection). Only mapping of a single value from ExtendedCalculationResult is supported. If no measurement is present in AIM (0..n) then do not include the template in the first place. The value of aim:uniqueIdentifier/@root is mapped to the ObservationUID Attribute of the NUM Content Item.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > $ModType	CODE	1-n	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/typeCode[position() != 1]	CD	1..n	The first typeCode entry is assumed to be the primary concept. This row can be used if successive typeCode entries are recognized, and not a method or derivation, and a name-value pair can be constructed from the typeCode entry (which is a single code).
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (370129005, SCT, "Measurement Method")	CODE	1	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/typeCode[position() != 1]	CD	1..n	The first typeCode entry is assumed to be the primary concept. Other typeCode entries may be considered as modifiers, but there is no standard order, so recognition as a "method" depends on recognition of specific codes.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (121401, DCM, "Derivation")	CODE	1	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/typeCode[position() != 1]	CD	1..n	The first typeCode entry is assumed to be the primary concept. Other typeCode entries may be considered as modifiers, but there is no standard order, so recognition as a "derivation" depends on recognition of specific codes.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (363698007, SCT, "Finding Site")	CODE	1-n	U					Not used, since is sent at measurement group level since common to all measurements in annotation. If a paired structure in AIM, this entry will pre-coordinate the laterality with the site.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (363698007, SCT, "Finding Site") > (272741003, SCT, "Laterality")	CODE	1	U					CID 244 “Laterality”
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (363698007, SCT, "Finding Site") > (106233006, SCT, "Topographical modifier")	CODE	1	U					Not used since AIM does not have a mechanism for post-coordinating the location.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement >	INCLUDE	1	U	TID 310 “Measurement Properties” in PS3.16				Statistical and normal range properties are not used in AIM use cases for this mapping.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > $DerivationParameter	NUM	1-n	UC					Not used in AIM
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > $DerivationParameter	NUM	1-n	UC					Not used in AIM
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement >	INCLUDE	1	UC	TID 315 “Equation or Table” in PS3.16				Not used in AIM
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > TEXT	TEXT	1	UC					CID 228 “Equation or Table” Not used in AIM
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement >	INCLUDE	1	U	TID 1000 “Quotation” in PS3.16				Quotations are not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (121050, DCM, "Equivalent Meaning of Concept Name")	TEXT	1	U					Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (126100, DCM, "Real World Value Map used for measurement")	COMPOSITE	1	U					Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement >	INCLUDE	1	U	TID 4019 “Mapping of Algorithm Identification”

TID 1420 Mapping of Measurements Derived From Multiple 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

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	Comment
(126000, DCM, "Imaging Measurement Report") > (126011, DCM, "Derived Imaging Measurements") > NUM	NUM	1-n	M		CID 7465 “Measurement Derived From Multiple ROI Measurements”
(126000, DCM, "Imaging Measurement Report") > (126011, DCM, "Derived Imaging Measurements") > NUM >	INCLUDE	1-n	MC	TID 1410 “Mapping of Planar ROI Measurements”
(126000, DCM, "Imaging Measurement Report") > (126011, DCM, "Derived Imaging Measurements") > NUM >	INCLUDE	1-n	MC	TID 1411 “Mapping of Volumetric ROI Measurements”
(126000, DCM, "Imaging Measurement Report") > (126011, DCM, "Derived Imaging Measurements") > NUM >	INCLUDE	1	U	TID 310 “Measurement Properties” in PS3.16	Statistical and normal range properties are not used in AIM use cases for this mapping.

TID 300 Mapping of Measurement

This section describes the mapping of TID 300 “Measurement” in PS3.16 .

Table TID 300. Mapping of Measurement

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement	NUM	1	M		NAME = ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/typeCode[1] VALUE = ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/calculationResultCollection/CalculationResult/@value, calculationDataCollection/CalculationData/@value UNITS = ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/calculationResultCollection/CalculationResult/unitOfMeasure	CD, ST, CD	1..n, 0..n, 1	The first typeCode entry is assumed to be the primary concept. Other typeCode entries may be considered as modifiers. Value may be found in either CompactCalculationResult (i.e., value child of CalculationResult) or first value of ExtendedCalculationResult (i.e., nested within calculationResultCollection). Only mapping of a single value from ExtendedCalculationResult is supported. The value of aim:uniqueIdentifier/@root is mapped to the ObservationUID Attribute of the NUM Content Item.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > $ModType	CODE	1-n	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/typeCode[position() != 1]	CD	1..n	The first typeCode entry is assumed to be the primary concept. This row can be used if successive typeCode entries are recognized, and not a method or derivation, and a name-value pair can be constructed from the typeCode entry (which is a single code).
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (370129005, SCT, "Measurement Method")	CODE	1	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/typeCode[position() != 1]	CD	1..n	The first typeCode entry is assumed to be the primary concept. Other typeCode entries may be considered as modifiers, but there is no standard order, so recognition as a "method" depends on recognition of specific codes.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (121401, DCM, "Derivation")	CODE	1	U		ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/typeCode[position() != 1]	CD	1..n	The first typeCode entry is assumed to be the primary concept. Other typeCode entries may be considered as modifiers, but there is no standard order, so recognition as a "derivation" depends on recognition of specific codes.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (363698007, SCT, "Finding Site")	CODE	1-n	U					Not used in AIM, since it is sent at measurement group level because it is common to all measurements in annotation.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (363698007, SCT, "Finding Site") > (272741003, SCT, "Laterality")	CODE	1	U		CID 244 “Laterality”			Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (363698007, SCT, "Finding Site") > (106233006, SCT, "Topographical modifier")	CODE	1	U		$TargetSiteMod			Not used since AIM does not have a mechanism for post-coordinating the location.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement >	INCLUDE	1	U	TID 310 “Measurement Properties” in PS3.16				Statistical and normal range properties are not used in AIM use cases for this mapping.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > $DerivationParameter	NUM	1-n	UC					Not used in AIM for our use cases.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > $DerivationParameter	NUM	1-n	UC					Not used in AIM for our use cases.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement >	INCLUDE	1	UC	TID 315 “Equation or Table” in PS3.16				Beyond the scope of our use cases to map.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > TEXT	TEXT	1	UC					CID 228 “Equation or Table” in PS3.16 Beyond the scope of our use cases to map.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > $ImagePurpose	INCLUDE	1-n	U	TID 320 “Mapping of Image or Spatial Coordinates”
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > $WavePurpose	INCLUDE	1-n	U	TID 321 “Waveform or Temporal Coordinates” in PS3.16				Not used in our AIM use cases.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement >	INCLUDE	1	U	TID 1000 “Quotation” in PS3.16				Not used in our AIM use cases.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (121050, DCM, "Equivalent Meaning of Concept Name")	TEXT	1	U					Not used in AIM
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement >	INCLUDE	1	U	TID 4108 “Mapping of Tracking Identifier”				Not mapped at this level for TID 1500, but rather at the Measurement Group level in TID 1501.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (126100, DCM, "Real World Value Map used for measurement")	COMPOSITE	1	U					Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement >	INCLUDE	1	U	TID 4019 “Mapping of Algorithm Identification”

TID 320 Mapping of Image or Spatial Coordinates

This section describes the mapping of TID 320 “Image or Spatial Coordinates” in PS3.16 .

Table TID 320. Mapping of Image or Spatial Coordinates

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Purpose	IMAGE	1	MC	ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/imageReferenceUid/@root, referencedFrameNumber/@value	II, INT	1, 0..1	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	SCOORD	1	MC	ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/twoDimensionSpatialCoordinateCollection/TwoDimensionSpatialCoordinate	REAL	1..n	A reference to coordinates on an image. The value of aim:MarkupEntity/aim:uniqueIdentifier/@root is mapped to the ObservationUID Attribute of the SCOORD. One or more MarkupEntity instances within an ImageAnnotation instance may be constrained to be associated with particular NUM measurement(s) in the included TID 1419 by a CalculationEntityReferencesMarkupEntityStatement.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Purpose > IMAGE	IMAGE	1	M	ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/imageReferenceUid/@root, referencedFrameNumber/@value	II, INT	1, 0..1	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.

DICOM SR Path

DICOM VT

DICOM VM

DICOM Usage Type

Generated Value

AIM Element or Attribute

AIM Data Type

AIM Multiplicity

Comment

(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Purpose

IMAGE

ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/imageReferenceUid/@root, referencedFrameNumber/@value

II, INT

1, 0..1

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

SCOORD

ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/twoDimensionSpatialCoordinateCollection/TwoDimensionSpatialCoordinate

REAL

1..n

A reference to coordinates on an image.

The value of aim:MarkupEntity/aim:uniqueIdentifier/@root is mapped to the ObservationUID Attribute of the SCOORD.

One or more MarkupEntity instances within an ImageAnnotation instance may be constrained to be associated with particular NUM measurement(s) in the included TID 1419 by a CalculationEntityReferencesMarkupEntityStatement.

(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Purpose > IMAGE

IMAGE

ImageAnnotationCollection/imageAnnotations/ImageAnnotation/markupEntityCollection/MarkupEntity/imageReferenceUid/@root, referencedFrameNumber/@value

II, INT

1, 0..1

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.

TID 4019 Mapping of Algorithm Identification

This section describes the mapping of PS3.16 TID 4019 “Algorithm Identification” in PS3.16 .

Table TID 4019. Mapping of Algorithm Identification

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (111001, DCM, "Algorithm Name")	TEXT	1	U	ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/algorithm/name/@value	ST	1	The type attribute (CD 1..n) is not supported by CID 4019
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (111003, DCM, "Algorithm Version")	TEXT	1	U	ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/algorithm/version/@value	ST	0..1
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (111002, DCM, "Algorithm Parameters")	TEXT	1-n	U	ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/algorithm/parameter/@dataType,@name,@value	CD,ST,ST	0..n	Separate mapping of dataType, name and value attributes is not supported by CID 4019
				ImageAnnotationCollection/imageAnnotations/ImageAnnotation/calculationEntityCollection/CalculationEntity/algorithm/type	CD	1..n	No corresponding mapping in DICOM SR template at this time.

TID 4108 Mapping of Tracking Identifier

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

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (112039, DCM, "Tracking Identifier")	TEXT	1	U					MC but U in parent TID 300. Not mapped at this level for TID 1500, but rather at the Measurement Group level in TID 1501.
(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (112040, DCM, "Tracking Unique Identifier")	UIDREF	1	U					MC but U in parent TID 300. Not mapped at this level for TID 1500, but rather at the Measurement Group level in TID 1501.

DICOM SR Path

DICOM VT

DICOM VM

DICOM Usage Type

Generated Value

AIM Element or Attribute

AIM Data Type

AIM Multiplicity

Comment

(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (112039, DCM, "Tracking Identifier")

TEXT

MC but U in parent TID 300.

Not mapped at this level for TID 1500, but rather at the Measurement Group level in TID 1501.

(126000, DCM, "Imaging Measurement Report") > (126010, DCM, "Imaging Measurements") > (125007, DCM, "Measurement Group") > $Measurement > (112040, DCM, "Tracking Unique Identifier")

UIDREF

MC but U in parent TID 300.

Not mapped at this level for TID 1500, but rather at the Measurement Group level in TID 1501.

TID 1204 Mapping of Language of Content Item and Descendants

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

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report") > (121049, DCM, "Language of Content Item and Descendants")	CODE	1	M	(eng,RFC5646,"English")				Not used in AIM; discarded if present in DICOM SR. CID 5000 “Language”
(126000, DCM, "Imaging Measurement Report") > (121049, DCM, "Language of Content Item and Descendants") > (121046, DCM, "Country of Language")	CODE	1	U	(US,ISO3166_1,"United States")				Not used in AIM; discarded if present in DICOM SR. CID 5001 “Country”

TID 1001 Mapping of Observation Context

This section describes the mapping of TID 1001 “Observation Context” in PS3.16 .

Table TID 1001. Mapping of Observation Context

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	Comment
(126000, DCM, "Imaging Measurement Report") >	INCLUDE	1-n	MC	TID 1002 “Mapping of Observer Context”	Only required for AIM if Attributes of the Author Observer Sequence (0040,A078) are insufficient to describe the person observer; not used for a device observer.
(126000, DCM, "Imaging Measurement Report") >	INCLUDE	1	MC	TID 1005 "Procedure Context"	Not used in AIM since redundant with header information; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") >	INCLUDE	1	MC	TID 1006 "Subject Context"	Not used in AIM since redundant with header information; discarded if present in DICOM SR.

TID 1002 Mapping of Observer Context

This section describes the mapping of TID 1002 “Observer Context” in PS3.16 .

Table TID 1002. Mapping of Observer Context

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	Comment
(126000, DCM, "Imaging Measurement Report") > (121005, DCM, "Observer Type")	CODE	1	MC		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”
(126000, DCM, "Imaging Measurement Report") >	INCLUDE	1	MC	TID 1003 “Mapping of Person Observer Identifying Attributes”	IFF Row 1 value = (121006, DCM, "Person") or Row 1 is absent
(126000, DCM, "Imaging Measurement Report") >	INCLUDE	1	MC	TID 1004 "Device Observer Identifying Attributes"	Not used in AIM; IFF Row 1 value = (121007, DCM, "Device")

TID 1003 Mapping of Person Observer Identifying Attributes

This section describes the mapping of TID 1003 “Person Observer Identifying Attributes” in PS3.16 .

Table TID 1003. Mapping of Person Observer Identifying Attributes

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report") > (121008, DCM, "Person Observer Name")	PNAME	1	M	ImageAnnotationCollection/user/name/@value	ST	1..1
(126000, DCM, "Imaging Measurement Report") > (128774, DCM, "Person Observer's Login Name")	PNAME	1	M	ImageAnnotationCollection/user/loginName/@value	ST	1..1
(126000, DCM, "Imaging Measurement Report") > (121009, DCM, "Person Observer's Organization Name")	TEXT	1	U				Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (121010, DCM, "Person Observer's Role in the Organization")	CODE	1	U				Not used in AIM.
(126000, DCM, "Imaging Measurement Report") > (121011, DCM, "Person Observer's Role in this Procedure")	CODE	1	U	ImageAnnotationCollection/user/roleInTrial/@value	ST	0..1	BCID 7453 “Performing Role” Values mapped are amended in CP 1734. AIM does not define a value set for the roles, so no standard mapping to the DICOM codes is defined.
(126000, DCM, "Imaging Measurement Report") > (121011, DCM, "Person Observer's Role in this Procedure") > (128775, DCM, "Identifier within Person Observer's Role")	TEXT	1	U	ImageAnnotationCollection/user/numberWithinRoleOfClinicalTrial/@value	INT	0..1	DICOM allows for alphanumeric, whereas AIM is INT only.

TID 1600 Mapping of Image Library

This section describes the mapping of TID 1600 “Image Library” in PS3.16 .

Table TID 1600. Mapping of Image Library

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	Comment
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library")	CONTAINER	1	M
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group")	CONTAINER	1-n	U		/ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imageReferenceEntityCollection/ImageReferenceEntity	The value of aim:uniqueIdentifier/@root is mapped to the ObservationUID Attribute of the CONTAINER.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") >	INCLUDE	1	U	TID 1602 “Mapping of Image Library Entry Descriptors”
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") >	INCLUDE	1-n	U	TID 1601 “Mapping of Image Library Entry”

TID 1601 Mapping of Image Library Entry

This section describes the mapping of TID 1601 “Image Library Entry” in PS3.16 .

Table TID 1601. Mapping of Image Library Entry

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > IMAGE	IMAGE	1	M		/ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/imageSeries/imageCollection/Image/sopInstanceUid/@root, sopClassUid/@root	II, II	1, 1
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > IMAGE >	INCLUDE	1	U	TID 1602 “Mapping of Image Library Entry Descriptors”

TID 1602 Mapping of Image Library Entry Descriptors

This section describes the mapping of TID 1602 “Image Library Entry Descriptors” in PS3.16 .

Table TID 1602. Mapping of Image Library Entry Descriptors

DICOM SR Path	DICOM VT	DICOM VM	DICOM Usage Type	Generated Value	AIM Element or Attribute	AIM Data Type	AIM Multiplicity	Comment
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (121139, DCM, "Modality")	CODE	1	U		/ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/imageSeries/modality/@code	CD	1..1	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")	CODE	1	U					Not used in AIM; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (111027, DCM, "Image Laterality")	CODE	1	U					Not used in AIM; discarded if present in DICOM SR.
126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") >(121022, DCM, "Accession Number")	TEXT	1	U		/ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/accessionNumber/@value	ST	0..1
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (111060, DCM, "Study Date")	DATE	1	U		/ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/startDate/@value	TS	1..1
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (111061, DCM, "Study Time")	TIME	1	U		/ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/startTime/@value	TS	1..1
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (111018, DCM, "Content Date")	DATE	1	U					Not used in AIM; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (111019, DCM, "Content Time")	TIME	1	U					Not used in AIM; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (126201, DCM, "Acquisition Date")	DATE	1	U					Not used in AIM; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (126202, DCM, "Acquisition Time")	TIME	1	U					Not used in AIM; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (112227, DCM, "Frame of Reference UID")	UIDREF	1	U					Not used in AIM; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (110910, DCM, "Pixel Data Rows")	NUM	1	U					Not used in AIM; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") > (110911, DCM, "Pixel Data Columns")	NUM	1	U					Not used in AIM; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") >	INCLUDE	1	U	TID 1603 "Image Library Entry Descriptors for Projection Radiography"				Not used in AIM; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") >	INCLUDE	1	U	TID 1604 "Image Library Entry Descriptors for Cross-Sectional Modalities"				Not used in AIM; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") >	INCLUDE	1	U	TID 1605 "Image Library Entry Descriptors for CT"				Not used in AIM; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") >	INCLUDE	1	U	TID 1606 "Image Library Entry Descriptors for MR"				Not used in AIM; discarded if present in DICOM SR.
(126000, DCM, "Imaging Measurement Report") > (111028, DCM, "Image Library") > (126200, DCM, "Image Library Group") >	INCLUDE	1	U	TID 1607 "Image Library Entry Descriptors for PET"				Not used in AIM; discarded if present in DICOM SR.

A.7 Sample Documents

This section describes a sample AIM v4.2 instance and the same content transformed into a DICOM SR TID 1500 instance.

A.7.1 Source AIM v4 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_2" xsi:schemaLocation="gme://caCORE.caCORE/4.4/edu.northwestern.radiology.AIM AIM_v4.2_rv2_XML.xsd">
    <uniqueIdentifier root="2.25.224793923339609181243139195858254344686"/>
    <studyInstanceUid root="2.25.80159168229010751652502576830057032194"/>
    <seriesInstanceUid root="2.25.323817225444021135415209334192751441320"/>
    <accessionNumber value="AN5678AIM"/>
    <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="52988006" codeSystemName="SCT">
                <iso:displayName xmlns:iso="uri:iso.org:21090" value="Lesion"/>
            </typeCode>
            <dateTime value="20170201180043"/>
            <name value="Lesion1"/>
            <comment value="PT / WB NAC P600 / 0"/>
            <trackingUniqueIdentifier root="2.25.165294254063588909770717555738008800301"/>
            <calculationEntityCollection>
                <CalculationEntity>
                    <uniqueIdentifier root="2.25.51420968257530981243824658943871973198"/>
                    <typeCode code="126401" codeSystemName="DCM">
                        <iso:displayName xmlns:iso="uri:iso.org:21090" value="SUVbw"/>
                    </typeCode>
                    <typeCode code="255605001" codeSystemName="SCT">
                        <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>
                    
                </CalculationEntity>
                <CalculationEntity>
                    <uniqueIdentifier root="2.25.205292243885258032428819330909580896146"/>
                    <typeCode code="126401" codeSystemName="DCM">
                        <iso:displayName xmlns:iso="uri:iso.org:21090" value="SUVbw"/>
                    </typeCode>
                    <typeCode code="56851009" codeSystemName="SCT">
                        <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>
                    
                </CalculationEntity>
                <CalculationEntity>
                    <uniqueIdentifier root="2.25.70160252080234577167847509948368893276"/>
                    <typeCode code="126401" codeSystemName="DCM">
                        <iso:displayName xmlns:iso="uri:iso.org:21090" value="SUVbw"/>
                    </typeCode>
                    <typeCode code="373098007" codeSystemName="SCT">
                        <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>
                    
                </CalculationEntity>
                <CalculationEntity>
                    <uniqueIdentifier root="2.25.140657026119469861895824082767088344984"/>
                    <typeCode code="126401" codeSystemName="DCM">
                        <iso:displayName xmlns:iso="uri:iso.org:21090" value="SUVbw"/>
                    </typeCode>
                    <typeCode code="386136009" codeSystemName="SCT">
                        <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>
                    
                </CalculationEntity>
            </calculationEntityCollection>
            <segmentationEntityCollection>
                <SegmentationEntity xsi:type="DicomSegmentationEntity">
                    <uniqueIdentifier root="2.25.318310842062810077214341266367812728264"/>
                    <sopInstanceUid root="2.25.134884066033959077306435705240550195701"/>
                    <studyInstanceUid root="2.25.19202292006231006756726546749423641172"/>
                    <seriesInstanceUid root="2.25.225493840038502954753967211679094249480"/>
                    <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"/>
                        <accessionNumber value="AN1234IMG"/>
                        <imageSeries>
                            <instanceUid root="2.25.263500776851326986665835510707132143772"/>
                            <modality code="PT" codeSystemName="DCM">
                                <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.7.2 Target DICOM SR "Measurement Report" (TID 1500)

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")  = (44136-0,LN,"PET unspecified body region")
	>1.5: CONTAINS: CONTAINER: (111028,DCM,"Image Library")  [SEPARATE]
		>>1.5.1: CONTAINS: CONTAINER: (126200,DCM,"Image Library Group")  [SEPARATE] (,2.25.239108061065263370785162033783811931375)
			>>>1.5.1.1: CONTAINS: IMAGE:  = (1.2.840.10008.5.1.4.1.1.128,2.25.319214308104243787945491694789635628411)
				>>>>1.5.1.1.1: HAS ACQ CONTEXT: CODE: (121139,DCM,"Modality")  = (PT,DCM,"Positron emission tomography")
				>>>>1.5.1.1.2: HAS ACQ CONTEXT: TEXT: (121022,DCM,"Accession Number")  = "AN1234IMG"
				>>>>1.5.1.1.3: HAS ACQ CONTEXT: DATE: (111060,DCM,"Study Date")  = "20170113"
				>>>>1.5.1.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] (20170201180043,2.25.56002466128627498886935079903172938041)
			>>>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.165294254063588909770717555738008800301"
			>>>1.6.1.3: CONTAINS: CODE: (121071,DCM,"Finding")  = (52988006,SCT,"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] (,2.25.318310842062810077214341266367812728264)
			>>>1.6.1.5: CONTAINS: IMAGE: (121233,DCM,"Source image for segmentation")  = (1.2.840.10008.5.1.4.1.1.128,2.25.319214308104243787945491694789635628411)
			>>>1.6.1.6: CONTAINS: NUM: (126401,DCM,"SUVbw")  = 1.98024 (g/ml{SUVbw},UCUM,"g/ml{SUVbw}") (,2.25.51420968257530981243824658943871973198)
				>>>>1.6.1.6.1: HAS CONCEPT MOD: CODE: (121401,DCM,"Derivation")  = (255605001,SCT,"Minimum")
			>>>1.6.1.7: CONTAINS: NUM: (126401,DCM,"SUVbw")  = 5.68816 (g/ml{SUVbw},UCUM,"g/ml{SUVbw}") (,2.25.205292243885258032428819330909580896146)
				>>>>1.6.1.7.1: HAS CONCEPT MOD: CODE: (121401,DCM,"Derivation")  = (56851009,SCT,"Maximum")
			>>>1.6.1.8: CONTAINS: NUM: (126401,DCM,"SUVbw")  = 2.329186593407 (g/ml{SUVbw},UCUM,"g/ml{SUVbw}") (,2.25.70160252080234577167847509948368893276)
				>>>>1.6.1.8.1: HAS CONCEPT MOD: CODE: (121401,DCM,"Derivation")  = (373098007,SCT,"Mean")
			>>>1.6.1.9: CONTAINS: NUM: (126401,DCM,"SUVbw")  = 1.8828952323684 (g/ml{SUVbw},UCUM,"g/ml{SUVbw}") (,2.25.140657026119469861895824082767088344984)
				>>>>1.6.1.9.1: HAS CONCEPT MOD: CODE: (121401,DCM,"Derivation")  = (386136009,SCT,"Standard Deviation")
			>>>1.6.1.10: CONTAINS: TEXT: (121106,DCM,"Comment")  = "PT / WB NAC P600 / 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).

Table A.7.2-1. Transformed SR document encoding at the Attribute level

SR Tree Depth	Nesting	Attribute	Tag	VR	VL (hex)	Value
		File Meta Information Group Length	(0002,0000)	UL	0004	0x000000ba
		File Meta Information Version	(0002,0001)	OB	0002	0x00,0x01
		Media Storage SOP Class UID	(0002,0002)	UI	001e	1.2.840.10008.5.1.4.1.1.88.22
		Media Storage SOP Instance UID	(0002,0003)	UI	002c	2.25.224793923339609181243139195858254344686
		Transfer Syntax UID	(0002,0010)	UI	0014	1.2.840.10008.1.2.1
		Implementation Class UID	(0002,0012)	UI	0016	1.3.6.1.4.1.5962.99.2
		Implementation Version Name	(0002,0013)	SH	0010	PIXELMEDJAVA001
		SOP Class UID	(0008,0016)	UI	001e	1.2.840.10008.5.1.4.1.1.88.22
		SOP Instance UID	(0008,0018)	UI	002c	2.25.224793923339609181243139195858254344686
		Study Date	(0008,0020)	DA	0000
		Content Date	(0008,0023)	DA	0008	20170201
		Study Time	(0008,0030)	TM	0000
		Content Time	(0008,0033)	TM	0006	180043
		Accession Number	(0008,0050)	SH	000a	AN5678AIM
		Modality	(0008,0060)	CS	0002	SR
		Manufacturer	(0008,0070)	LO	0014	Acme Medical Systems
		Referring Physician's Name	(0008,0090)	PN	0000
		Manufacturer's Model Name	(0008,1090)	LO	0000
		Referenced Performed Procedure Step Sequence	(0008,1111)	SQ	ffffffff
	%endseq
		Patient's Name	(0010,0010)	PN	0010	CM-1-111-000000
		Patient ID	(0010,0020)	LO	0028	293761767066931586407385203810190772174
		Patient's Birth Date	(0010,0030)	DA	0008	19601000
		Patient's Sex	(0010,0040)	CS	0002	M
		Ethnic Group	(0010,2160)	SH	0000
		Software Versions	(0018,1020)	LO	0006	36.00
		Study Instance UID	(0020,000d)	UI	002c	2.25.80159168229010751652502576830057032194
		Series Instance UID	(0020,000e)	UI	002c	2.25.323817225444021135415209334192751441320
		Study ID	(0020,0010)	SH	0000
		Series Number	(0020,0011)	IS	0004	7291
		Instance Number	(0020,0013)	IS	0002	1
1		Value Type	(0040,a040)	CS	000a	CONTAINER
1		Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
	>	Code Value	(0008,0100)	SH	0006	126000
	>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
	>	Code Meaning	(0008,0104)	LO	001a	Imaging Measurement Report
	%enditem
	%endseq
1		Continuity Of Content	(0040,a050)	CS	0008	SEPARATE
		Author Observer Sequence	(0040,a078)	SQ	ffffffff
	%item
	>	Institution Name	(0008,0080)	LO	0000
	>	Institution Code Sequence	(0008,0082)	SQ	ffffffff
	%endseq
	>	Person Identification Code Sequence	(0040,1101)	SQ	ffffffff
	%endseq
	>	Observer Type	(0040,a084)	CS	0004	PSN
	>	Person Name	(0040,a123)	PN	0008	Doe^Jane
	%enditem
	%endseq
		Performed Procedure Code Sequence	(0040,a372)	SQ	ffffffff
	%endseq
		Current Requested Procedure Evidence Sequence	(0040,a375)	SQ	ffffffff
	%item
	>	Referenced Series Sequence	(0008,1115)	SQ	ffffffff
	%item
	>>	Referenced SOP Sequence	(0008,1199)	SQ	ffffffff
	%item
	>>>	Referenced SOP Class UID	(0008,1150)	UI	001c	1.2.840.10008.5.1.4.1.1.128
	>>>	Referenced SOP Instance UID	(0008,1155)	UI	002c	2.25.319214308104243787945491694789635628411
	%enditem
	%endseq
	>>	Series Instance UID	(0020,000e)	UI	002c	2.25.263500776851326986665835510707132143772
	%enditem
	%endseq
	>	Study Instance UID	(0020,000d)	UI	002c	2.25.52186905385055707830834793159643714079
	%enditem
	%item
	>	Referenced Series Sequence	(0008,1115)	SQ	ffffffff
	%item
	>>	Referenced SOP Sequence	(0008,1199)	SQ	ffffffff
	%item
	>>>	Referenced SOP Class UID	(0008,1150)	UI	001c	1.2.840.10008.5.1.4.1.1.66.4
	>>>	Referenced SOP Instance UID	(0008,1155)	UI	002c	2.25.134884066033959077306435705240550195701
	%enditem
	%endseq
	>>	Series Instance UID	(0020,000e)	UI	002c	2.25.225493840038502954753967211679094249480
	%enditem
	%endseq
	>	Study Instance UID	(0020,000d)	UI	002c	2.25.19202292006231006756726546749423641172
	%enditem
	%endseq
		Completion Flag	(0040,a491)	CS	0008	COMPLETE
		Verification Flag	(0040,a493)	CS	000a	UNVERIFIED
		Content Template Sequence	(0040,a504)	SQ	ffffffff
	%item
	>	Mapping Resource	(0008,0105)	CS	0004	DCMR
	>	Template Identifier	(0040,db00)	CS	0004	1500
	%enditem
	%endseq
1		Content Sequence	(0040,a730)	SQ	ffffffff
	%item
1.1	>	Relationship Type	(0040,a010)	CS	0010	HAS CONCEPT MOD
1.1	>	Value Type	(0040,a040)	CS	0004	CODE
1.1	>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.1	>>	Code Value	(0008,0100)	SH	0006	121049
1.1	>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.1	>>	Code Meaning	(0008,0104)	LO	0028	Language of Content Item and Descendants
	%enditem
	%endseq
1.1	>	Concept Code Sequence	(0040,a168)	SQ	ffffffff
	%item
1.1	>>	Code Value	(0008,0100)	SH	0004	eng
1.1	>>	Coding Scheme Designator	(0008,0102)	SH	0008	RFC5646
1.1	>>	Code Meaning	(0008,0104)	LO	0008	English
	%enditem
	%endseq
1.1	>	Content Sequence	(0040,a730)	SQ	ffffffff
	%item
1.1.1	>>	Relationship Type	(0040,a010)	CS	0010	HAS CONCEPT MOD
1.1.1	>>	Value Type	(0040,a040)	CS	0004	CODE
1.1.1	>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.1.1	>>>	Code Value	(0008,0100)	SH	0006	121046
1.1.1	>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.1.1	>>>	Code Meaning	(0008,0104)	LO	0014	Country of Language
	%enditem
	%endseq
1.1.1	>>	Concept Code Sequence	(0040,a168)	SQ	ffffffff
	%item
1.1.1	>>>	Code Value	(0008,0100)	SH	0002	US
1.1.1	>>>	Coding Scheme Designator	(0008,0102)	SH	000a	ISO3166_1
1.1.1	>>>	Code Meaning	(0008,0104)	LO	000e	United States
	%enditem
	%endseq
	%enditem
	%endseq
	%enditem
	%item
1.2	>	Relationship Type	(0040,a010)	CS	0010	HAS OBS CONTEXT
1.2	>	Value Type	(0040,a040)	CS	0006	PNAME
1.2	>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.2	>>	Code Value	(0008,0100)	SH	0006	121008
1.2	>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.2	>>	Code Meaning	(0008,0104)	LO	0014	Person Observer Name
	%enditem
	%endseq
1.2	>	Person Name	(0040,a123)	PN	0008	Doe^Jane
	%enditem
	%item
1.3	>	Relationship Type	(0040,a010)	CS	0010	HAS OBS CONTEXT
1.3	>	Value Type	(0040,a040)	CS	0004	TEXT
1.3	>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.3	>>	Code Value	(0008,0100)	SH	0006	128774
1.3	>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.3	>>	Code Meaning	(0008,0104)	LO	001c	Person Observer's Login Name
	%enditem
	%endseq
1.3	>	Text Value	(0040,a160)	UT	0004	jdoe
	%enditem
	%item
1.4	>	Relationship Type	(0040,a010)	CS	0010	HAS CONCEPT MOD
1.4	>	Value Type	(0040,a040)	CS	0004	CODE
1.4	>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.4	>>	Code Value	(0008,0100)	SH	0006	121058
1.4	>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.4	>>	Code Meaning	(0008,0104)	LO	0012	Procedure reported
	%enditem
	%endseq
1.4	>	Concept Code Sequence	(0040,a168)	SQ	ffffffff
	%item
1.4	>>	Code Value	(0008,0100)	SH	0008	44136-0
1.4	>>	Coding Scheme Designator	(0008,0102)	SH	0002	LN
1.4	>>	Code Meaning	(0008,0104)	LO	001c	PET unspecified body region
	%enditem
	%endseq
	%enditem
	%item
1.5	>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.5	>	Value Type	(0040,a040)	CS	000a	CONTAINER
1.5	>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.5	>>	Code Value	(0008,0100)	SH	0006	111028
1.5	>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.5	>>	Code Meaning	(0008,0104)	LO	000e	Image Library
	%enditem
	%endseq
1.5	>	Continuity Of Content	(0040,a050)	CS	0008	SEPARATE
1.5	>	Content Sequence	(0040,a730)	SQ	ffffffff
	%item
1.5.1	>>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.5.1	>>	Value Type	(0040,a040)	CS	000a	CONTAINER
1.5.1	>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.5.1	>>>	Code Value	(0008,0100)	SH	0006	126200
1.5.1	>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.5.1	>>>	Code Meaning	(0008,0104)	LO	0014	Image Library Group
	%enditem
	%endseq
1.5.1	>>	Continuity Of Content	(0040,a050)	CS	0008	SEPARATE
1.5.1	>>	Observation UID	(0040,a171)	UI	002c	2.25.239108061065263370785162033783811931375
1.5.1	>>	Content Sequence	(0040,a730)	SQ	ffffffff
	%item
1.5.1.1	>>>	Referenced SOP Sequence	(0008,1199)	SQ	ffffffff
	%item
1.5.1.1	>>>>	Referenced SOP Class UID	(0008,1150)	UI	001c	1.2.840.10008.5.1.4.1.1.128
1.5.1.1	>>>>	Referenced SOP Instance UID	(0008,1155)	UI	002c	2.25.319214308104243787945491694789635628411
	%enditem
	%endseq
1.5.1.1	>>>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.5.1.1	>>>	Value Type	(0040,a040)	CS	0006	IMAGE
1.5.1.1	>>>	Content Sequence	(0040,a730)	SQ	ffffffff
	%item
1.5.1.1.1	>>>>	Relationship Type	(0040,a010)	CS	0010	HAS ACQ CONTEXT
1.5.1.1.1	>>>>	Value Type	(0040,a040)	CS	0004	CODE
1.5.1.1.1	>>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.5.1.1.1	>>>>>	Code Value	(0008,0100)	SH	0006	121139
1.5.1.1.1	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.5.1.1.1	>>>>>	Code Meaning	(0008,0104)	LO	0008	Modality
	%enditem
	%endseq
1.5.1.1.1	>>>>	Concept Code Sequence	(0040,a168)	SQ	ffffffff
	%item
1.5.1.1.1	>>>>>	Code Value	(0008,0100)	SH	0002	PT
1.5.1.1.1	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.5.1.1.1	>>>>>	Code Meaning	(0008,0104)	LO	001c	Positron emission tomography
	%enditem
	%endseq
	%enditem
	%item
1.5.1.1.2	>>>>	Relationship Type	(0040,a010)	CS	0010	HAS ACQ CONTEXT
1.5.1.1.2	>>>>	Value Type	(0040,a040)	CS	0004	TEXT
1.5.1.1.2	>>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.5.1.1.2	>>>>>	Code Value	(0008,0100)	SH	0006	121022
1.5.1.1.2	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.5.1.1.2	>>>>>	Code Meaning	(0008,0104)	LO	0010	Accession Number
	%enditem
	%endseq
1.5.1.1.2	>>>>	Text Value	(0040,a160)	UT	000a	AN1234IMG
	%enditem
	%item
1.5.1.1.3	>>>>	Relationship Type	(0040,a010)	CS	0010	HAS ACQ CONTEXT
1.5.1.1.3	>>>>	Value Type	(0040,a040)	CS	0004	DATE
1.5.1.1.3	>>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.5.1.1.3	>>>>>	Code Value	(0008,0100)	SH	0006	111060
1.5.1.1.3	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.5.1.1.3	>>>>>	Code Meaning	(0008,0104)	LO	000a	Study Date
	%enditem
	%endseq
1.5.1.1.3	>>>>	Date	(0040,a121)	DA	0008	20170113
	%enditem
	%item
1.5.1.1.4	>>>>	Relationship Type	(0040,a010)	CS	0010	HAS ACQ CONTEXT
1.5.1.1.4	>>>>	Value Type	(0040,a040)	CS	0004	TIME
1.5.1.1.4	>>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.5.1.1.4	>>>>>	Code Value	(0008,0100)	SH	0006	111061
1.5.1.1.4	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.5.1.1.4	>>>>>	Code Meaning	(0008,0104)	LO	000a	Study Time
	%enditem
	%endseq
1.5.1.1.4	>>>>	Time	(0040,a122)	TM	0006	070844
	%enditem
	%endseq
	%enditem
	%endseq
	%enditem
	%endseq
	%enditem
	%item
1.6	>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.6	>	Value Type	(0040,a040)	CS	000a	CONTAINER
1.6	>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6	>>	Code Value	(0008,0100)	SH	0006	126010
1.6	>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6	>>	Code Meaning	(0008,0104)	LO	0014	Imaging Measurements
	%enditem
	%endseq
1.6	>	Continuity Of Content	(0040,a050)	CS	0008	SEPARATE
1.6	>	Content Sequence	(0040,a730)	SQ	ffffffff
	%item
1.6.1	>>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.6.1	>>	Observation DateTime	(0040,a032)	DT	000e	20170201180043
1.6.1	>>	Value Type	(0040,a040)	CS	000a	CONTAINER
1.6.1	>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1	>>>	Code Value	(0008,0100)	SH	0006	125007
1.6.1	>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1	>>>	Code Meaning	(0008,0104)	LO	0012	Measurement Group
	%enditem
	%endseq
1.6.1	>>	Continuity Of Content	(0040,a050)	CS	0008	SEPARATE
1.6.1	>>	Observation UID	(0040,a171)	UI	002c	2.25.56002466128627498886935079903172938041
1.6.1	>>	Content Sequence	(0040,a730)	SQ	ffffffff
	%item
1.6.1.1	>>>	Relationship Type	(0040,a010)	CS	0010	HAS OBS CONTEXT
1.6.1.1	>>>	Value Type	(0040,a040)	CS	0004	TEXT
1.6.1.1	>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.1	>>>>	Code Value	(0008,0100)	SH	0006	112039
1.6.1.1	>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.1	>>>>	Code Meaning	(0008,0104)	LO	0014	Tracking Identifier
	%enditem
	%endseq
1.6.1.1	>>>	Text Value	(0040,a160)	UT	0008	Lesion1
	%enditem
	%item
1.6.1.2	>>>	Relationship Type	(0040,a010)	CS	0010	HAS OBS CONTEXT
1.6.1.2	>>>	Value Type	(0040,a040)	CS	0006	UIDREF
1.6.1.2	>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.2	>>>>	Code Value	(0008,0100)	SH	0006	112040
1.6.1.2	>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.2	>>>>	Code Meaning	(0008,0104)	LO	001a	Tracking Unique Identifier
	%enditem
	%endseq
1.6.1.2	>>>	UID	(0040,a124)	UI	002c	2.25.165294254063588909770717555738008800301
	%enditem
	%item
1.6.1.3	>>>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.6.1.3	>>>	Value Type	(0040,a040)	CS	0004	CODE
1.6.1.3	>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.3	>>>>	Code Value	(0008,0100)	SH	0006	121071
1.6.1.3	>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.3	>>>>	Code Meaning	(0008,0104)	LO	0008	Finding
	%enditem
	%endseq
1.6.1.3	>>>	Concept Code Sequence	(0040,a168)	SQ	ffffffff
	%item
1.6.1.3	>>>>	Code Value	(0008,0100)	SH	0008	52988006
1.6.1.3	>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	SCT
1.6.1.3	>>>>	Code Meaning	(0008,0104)	LO	0006	Lesion
	%enditem
	%endseq
	%enditem
	%item
1.6.1.4	>>>	Referenced SOP Sequence	(0008,1199)	SQ	ffffffff
	%item
1.6.1.4	>>>>	Referenced SOP Class UID	(0008,1150)	UI	001c	1.2.840.10008.5.1.4.1.1.66.4
1.6.1.4	>>>>	Referenced SOP Instance UID	(0008,1155)	UI	002c	2.25.134884066033959077306435705240550195701
1.6.1.4	>>>>	Referenced Segment Number	(0062,000b)	US	0002	0x0001
	%enditem
	%endseq
1.6.1.4	>>>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.6.1.4	>>>	Value Type	(0040,a040)	CS	0006	IMAGE
1.6.1.4	>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.4	>>>>	Code Value	(0008,0100)	SH	0006	121191
1.6.1.4	>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.4	>>>>	Code Meaning	(0008,0104)	LO	0012	Referenced Segment
	%enditem
	%endseq
1.6.1.4	>>>	Observation UID	(0040,a171)	UI	002c	2.25.318310842062810077214341266367812728264
	%enditem
	%item
1.6.1.5	>>>	Referenced SOP Sequence	(0008,1199)	SQ	ffffffff
	%item
1.6.1.5	>>>>	Referenced SOP Class UID	(0008,1150)	UI	001c	1.2.840.10008.5.1.4.1.1.128
1.6.1.5	>>>>	Referenced SOP Instance UID	(0008,1155)	UI	002c	2.25.319214308104243787945491694789635628411
	%enditem
	%endseq
1.6.1.5	>>>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.6.1.5	>>>	Value Type	(0040,a040)	CS	0006	IMAGE
1.6.1.5	>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.5	>>>>	Code Value	(0008,0100)	SH	0006	121233
1.6.1.5	>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.5	>>>>	Code Meaning	(0008,0104)	LO	001e	Source image for segmentation
	%enditem
	%endseq
	%enditem
	%item
1.6.1.6	>>>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.6.1.6	>>>	Value Type	(0040,a040)	CS	0004	NUM
1.6.1.6	>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.6	>>>>	Code Value	(0008,0100)	SH	0006	126401
1.6.1.6	>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.6	>>>>	Code Meaning	(0008,0104)	LO	0006	SUVbw
	%enditem
	%endseq
1.6.1.6	>>>	Observation UID	(0040,a171)	UI	002c	2.25.51420968257530981243824658943871973198
1.6.1.6	>>>	Measured Value Sequence	(0040,a300)	SQ	ffffffff
	%item
1.6.1.6	>>>>	Measurement Units Code Sequence	(0040,08ea)	SQ	ffffffff
	%item
1.6.1.6	>>>>>	Code Value	(0008,0100)	SH	000c	g/ml{SUVbw}
1.6.1.6	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	UCUM
1.6.1.6	>>>>>	Code Meaning	(0008,0104)	LO	000c	g/ml{SUVbw}
	%enditem
	%endseq
1.6.1.6	>>>>	Numeric Value	(0040,a30a)	DS	0008	1.98024
	%enditem
	%endseq
1.6.1.6	>>>	Content Sequence	(0040,a730)	SQ	ffffffff
	%item
1.6.1.6.1	>>>>	Relationship Type	(0040,a010)	CS	0010	HAS CONCEPT MOD
1.6.1.6.1	>>>>	Value Type	(0040,a040)	CS	0004	CODE
1.6.1.6.1	>>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.6.1	>>>>>	Code Value	(0008,0100)	SH	0006	121401
1.6.1.6.1	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.6.1	>>>>>	Code Meaning	(0008,0104)	LO	000a	Derivation
	%enditem
	%endseq
1.6.1.6.1	>>>>	Concept Code Sequence	(0040,a168)	SQ	ffffffff
	%item
1.6.1.6.1	>>>>>	Code Value	(0008,0100)	SH	000a	255605001
1.6.1.6.1	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	SCT
1.6.1.6.1	>>>>>	Code Meaning	(0008,0104)	LO	0008	Minimum
	%enditem
	%endseq
	%enditem
	%endseq
	%enditem
	%item
1.6.1.7	>>>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.6.1.7	>>>	Value Type	(0040,a040)	CS	0004	NUM
1.6.1.7	>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.7	>>>>	Code Value	(0008,0100)	SH	0006	126401
1.6.1.7	>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.7	>>>>	Code Meaning	(0008,0104)	LO	0006	SUVbw
	%enditem
	%endseq
1.6.1.7	>>>	Observation UID	(0040,a171)	UI	002c	2.25.205292243885258032428819330909580896146
1.6.1.7	>>>	Measured Value Sequence	(0040,a300)	SQ	ffffffff
	%item
1.6.1.7	>>>>	Measurement Units Code Sequence	(0040,08ea)	SQ	ffffffff
	%item
1.6.1.7	>>>>>	Code Value	(0008,0100)	SH	000c	g/ml{SUVbw}
1.6.1.7	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	UCUM
1.6.1.7	>>>>>	Code Meaning	(0008,0104)	LO	000c	g/ml{SUVbw}
	%enditem
	%endseq
1.6.1.7	>>>>	Numeric Value	(0040,a30a)	DS	0008	5.68816
	%enditem
	%endseq
1.6.1.7	>>>	Content Sequence	(0040,a730)	SQ	ffffffff
	%item
1.6.1.7.1	>>>>	Relationship Type	(0040,a010)	CS	0010	HAS CONCEPT MOD
1.6.1.7.1	>>>>	Value Type	(0040,a040)	CS	0004	CODE
1.6.1.7.1	>>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.7.1	>>>>>	Code Value	(0008,0100)	SH	0006	121401
1.6.1.7.1	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.7.1	>>>>>	Code Meaning	(0008,0104)	LO	000a	Derivation
	%enditem
	%endseq
1.6.1.7.1	>>>>	Concept Code Sequence	(0040,a168)	SQ	ffffffff
	%item
1.6.1.7.1	>>>>>	Code Value	(0008,0100)	SH	0008	56851009
1.6.1.7.1	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	SCT
1.6.1.7.1	>>>>>	Code Meaning	(0008,0104)	LO	0008	Maximum
	%enditem
	%endseq
	%enditem
	%endseq
	%enditem
	%item
1.6.1.8	>>>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.6.1.8	>>>	Value Type	(0040,a040)	CS	0004	NUM
1.6.1.8	>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.8	>>>>	Code Value	(0008,0100)	SH	0006	126401
1.6.1.8	>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.8	>>>>	Code Meaning	(0008,0104)	LO	0006	SUVbw
	%enditem
	%endseq
1.6.1.8	>>>	Observation UID	(0040,a171)	UI	002c	2.25.70160252080234577167847509948368893276
1.6.1.8	>>>	Measured Value Sequence	(0040,a300)	SQ	ffffffff
	%item
1.6.1.8	>>>>	Measurement Units Code Sequence	(0040,08ea)	SQ	ffffffff
	%item
1.6.1.8	>>>>>	Code Value	(0008,0100)	SH	000c	g/ml{SUVbw}
1.6.1.8	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	UCUM
1.6.1.8	>>>>>	Code Meaning	(0008,0104)	LO	000c	g/ml{SUVbw}
	%enditem
	%endseq
1.6.1.8	>>>>	Numeric Value	(0040,a30a)	DS	000e	2.329186593407
	%enditem
	%endseq
1.6.1.8	>>>	Content Sequence	(0040,a730)	SQ	ffffffff
	%item
1.6.1.8.1	>>>>	Relationship Type	(0040,a010)	CS	0010	HAS CONCEPT MOD
1.6.1.8.1	>>>>	Value Type	(0040,a040)	CS	0004	CODE
1.6.1.8.1	>>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.8.1	>>>>>	Code Value	(0008,0100)	SH	0006	121401
1.6.1.8.1	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.8.1	>>>>>	Code Meaning	(0008,0104)	LO	000a	Derivation
	%enditem
	%endseq
1.6.1.8.1	>>>>	Concept Code Sequence	(0040,a168)	SQ	ffffffff
	%item
1.6.1.8.1	>>>>>	Code Value	(0008,0100)	SH	000a	373098007
1.6.1.8.1	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	SCT
1.6.1.8.1	>>>>>	Code Meaning	(0008,0104)	LO	0004	Mean
	%enditem
	%endseq
	%enditem
	%endseq
	%enditem
	%item
1.6.1.9	>>>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.6.1.9	>>>	Value Type	(0040,a040)	CS	0004	NUM
1.6.1.9	>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.9	>>>>	Code Value	(0008,0100)	SH	0006	126401
1.6.1.9	>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.9	>>>>	Code Meaning	(0008,0104)	LO	0006	SUVbw
	%enditem
	%endseq
1.6.1.9	>>>	Observation UID	(0040,a171)	UI	002c	2.25.140657026119469861895824082767088344984
1.6.1.9	>>>	Measured Value Sequence	(0040,a300)	SQ	ffffffff
	%item
1.6.1.9	>>>>	Measurement Units Code Sequence	(0040,08ea)	SQ	ffffffff
	%item
1.6.1.9	>>>>>	Code Value	(0008,0100)	SH	000c	g/ml{SUVbw}
1.6.1.9	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	UCUM
1.6.1.9	>>>>>	Code Meaning	(0008,0104)	LO	000c	g/ml{SUVbw}
	%enditem
	%endseq
1.6.1.9	>>>>	Numeric Value	(0040,a30a)	DS	0010	1.8828952323684
	%enditem
	%endseq
1.6.1.9	>>>	Content Sequence	(0040,a730)	SQ	ffffffff
	%item
1.6.1.9.1	>>>>	Relationship Type	(0040,a010)	CS	0010	HAS CONCEPT MOD
1.6.1.9.1	>>>>	Value Type	(0040,a040)	CS	0004	CODE
1.6.1.9.1	>>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.9.1	>>>>>	Code Value	(0008,0100)	SH	0006	121401
1.6.1.9.1	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.9.1	>>>>>	Code Meaning	(0008,0104)	LO	000a	Derivation
	%enditem
	%endseq
1.6.1.9.1	>>>>	Concept Code Sequence	(0040,a168)	SQ	ffffffff
	%item
1.6.1.9.1	>>>>>	Code Value	(0008,0100)	SH	000a	386136009
1.6.1.9.1	>>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	SCT
1.6.1.9.1	>>>>>	Code Meaning	(0008,0104)	LO	0012	Standard Deviation
	%enditem
	%endseq
	%enditem
	%endseq
	%enditem
	%item
1.6.1.10	>>>	Relationship Type	(0040,a010)	CS	0008	CONTAINS
1.6.1.10	>>>	Value Type	(0040,a040)	CS	0004	TEXT
1.6.1.10	>>>	Concept Name Code Sequence	(0040,a043)	SQ	ffffffff
	%item
1.6.1.10	>>>>	Code Value	(0008,0100)	SH	0006	121106
1.6.1.10	>>>>	Coding Scheme Designator	(0008,0102)	SH	0004	DCM
1.6.1.10	>>>>	Code Meaning	(0008,0104)	LO	0008	Comment
	%enditem
	%endseq
1.6.1.10	>>>	Text Value	(0040,a160)	UT	0014	PT / WB NAC P600 / 0
	%enditem
	%endseq
	%enditem
	%endseq
	%enditem
	%endseq

A.8 Overview of Data Types

DICOM data types are specified in PS3.5 of the Standard (PS3.5).

The AIM V4 data types are a subset of [ISO 21090], which are in turn based on [V3 DT R1]. The AIM V4 data types used are documented in [AIM v3 v4 changes] and [Extending AIM].

While a complete comparison of DICOM and [ISO 21090] data types, cardinality and optionality is beyond the scope of this mapping guide, some hints are given on topics that are relevant for transforming AIM instances and DICOM SR Measurement Reports.

The AIM V4 model uses the data types as specified in Table A.8-2 from [ISO 21090], of which only a subset are encountered in use cases described by this mapping. In XML encoded AIM instances, the data type is not explicitly encoded, though it is defined in the UML model.

Table A.8-1. ISO 21090 Data Types used in AIM V4

ISO 21090 Data Types	Description
BL	Boolean (two-valued logic). A BL value can be either true or false, or may have a nullFlavor.
CD	Concept Descriptor. A reference to a concept defined in an external code system, terminology or ontology, or an expression in some syntax defined by the referenced code system.
II	Instance Identifier. An identifier that uniquely identifies a thing or object. Instance identifiers are usually defined based on ISO object identifiers.
INT	Integer. No arbitrary limit is imposed on the range of integer numbers.
REAL	Fractional numbers. The typical representation is decimal.
ST	Character string. Shall have at least one character or else have a nullFlavor.
TS	Point in time. A quantity specifying a point on the axis of natural time. Most often represented as a calendar expression.

Additional data type mapping considerations include:

Optionality and nullFlavor

If the original AIM instance does not include values that are required or mandatory in DICOM SR TID 1500, fixed values are specified since empty values are not permitted in DICOM SR TEXT and CODE entries and omitting the Content Item would violate the template constraints. All nullFlavor values are treated as empty, except for numeric values.
Character Sets

DICOM provides information on the interpretation of text data types by specifying a default character set (ISO-IR 6) and "Specific Character Set" (0008,0005) values that are used if the Basic Graphic Set is expanded or replaced. For AIM, the XML declaration attribute "encoding" (overall document) and the attribute "charset" (for ST data type values) may be used to provide information on character sets. See the description of Specific Character Set in Section A.6.1.1.11 “Mapping of DICOM SOP Common Module”.
Character strings

In general, ST text value attributes in AIM XML elements are mapped to DICOM Text Value (0040,A160) of value type TEXT (with a VR of Unlimited Text (UT)) in the SR Content Tree. No maximum length is specified for AIM elements and attributes.

Some text value attributes in AIM XML elements are mapped to Attributes in the DICOM header, and DICOM length limits may apply to character strings such as Long String (LO), e.g., Patient ID.
Identifiers

Unique identifiers in AIM V4 are encoded as the root attribute of an XML element (aim:uniqueIdentifier/@root), which has an II data type, and are mapped to the DICOM UI VR, which is limited to 64 bytes.

Codes

Codes in AIM V4 are encoded as attributes of the aim:typeCode XML element and are mapped as specified in Table A.8-2 below for the [ISO 21090] code data type (CD). The code and codeSystemName attributes are encountered as attributes of the aim:typeCode XML element, but the displayName is the value attribute of a child element, aim:typeCode/iso:displayName/@value. Note that codeSystem (Coding Scheme UID) is usually not sent, even though it is required by [ISO 21090]. DICOM also supports other Attributes for encoding code values that exceed 16 characters in length.

Table A.8-2. Mapping between DICOM Basic Code Attributes and AIM ISO 21090 Code Data Types (CD)

DICOM Attribute and VR		AIM Element and Attribute and ISO 21090 Data Type
Code Value (0008,0100)	SH	aim:typeCode/@code	CD.characterstring
Coding Scheme UID (0008,0x010C)	UI	aim:typeCode/@codeSystem	CD.characterstring
Coding Scheme Designator (0008,0102)	SH	aim:typeCode/@codeSystemName	CD.characterstring
Coding Scheme Version (0008,0103)	SH	aim:typeCode/@codeSystemVersion	CD.characterstring
Code Meaning (0008,0104)	LO	aim:typeCode/iso:displayName/@value	CD.ST

Date and Time
- The AIM V4 XML element aim:dateTime/@value attribute corresponds to the ISO 21090 TS data type, and is mapped to the DICOM DateTime (DT) VR, or the combination of separate Date (DA) and Time (TM) Attributes.
- DICOM DT matches TS except for the number of decimal places of fractional seconds (6 for DT versus 4 for TS).
- DICOM DA matches the TS part YYYYMMDD (Y=Year, M=Month, D=Day), except that TS may be missing DD or MMDD.
- DICOM TM matches the TS part HHMMSS.UUUUUU (H=Hour, M=Minute, S=Second, U=Fractional Second) except for the number of decimal places of fractional seconds (6 for DT versus 4 for TS).
- If available, the DICOM Timezone Offset From UTC (0008,0201) used for DA or TM data types may be populated using time zone offset values from the ISO 21090 TS value.
- ISO TS allows for separators; these need to be removed for conversion to DT, DA and TM.

Person Names

DICOM Person Name (PN) shall be mapped from [ISO 21090] data type Person Name (PN) as described in Table A.8-3.

Table A.8-3. Mapping between DICOM Person Name (PN) ans ISO 21090 Data Type Person Name (PN)

DICOM Person Name (PN)	ISO 21090 Data Type: Person Name (PN)
<family_name_complex>	Family Part type
<given_name_complex>	Given Part type
<middle_name>	Given Part type - order of parts matters
<name_suffix>	Suffix Part type
<name_prefix>	Prefix Part type

[ISO 21090] PN may contain multiple given names. DICOM PN Middle Name shall be mapped to [ISO 21090] PN Given Name Part type.
Example A.8-1. Person Name Example
John Robert Morrison, Ph.D. "Morrison^John Robert^^^Ph.D." [One family name; two given names; no middle name; no prefix; one suffix] can be represented as a [ISO 21090] Person Name (PN) in the following way:
```
<name>
   		<given>John</given>
   		<given>Robert</given>
		<family>Morrison</family>
 		<suffix>Ph.D.</suffix>
	</name>
```

The following [ISO 21090] PN use codes may be used to represent multi-part DICOM person names: ABC (Alphabetic), IDE (Ideographic), SYL (Phonetic).

Example A.8-2. HL7 V3 Multi-Part Person Name Example

<name use="ABC">
   		<family>KIMURA</family>
   		<given>MICHIO</given>
	</name>
	<name use='IDE'>
   		<family>木村</family>
   		<given>道男</given>
	</name>
	<name use="SYL">
   		<family>きむら</family>
   		<given>みちお</given>
	</name>

Numeric Measurements

DICOM Numeric Measurement value types shall be mapped from the [ISO 21090] data types as specified in Table A.8-4.

Table A.8-4. Mapping between DICOM Numeric Measurement Value Types and ISO 21090 Data Types

DICOM PS3.3, PS3.5 and PS3.16: Numeric Measurement (NUM) Value Type		AIM Path and ISO 21090 Data Type
Measured Value Sequence (0040,A300) > Concept Name Code Sequence (0040,A043)	Code Sequence Macro	CalculationEntity/typeCode[1]	CD
Measured Value Sequence (0040,A300) > Numeric Value (0040,A30A)	DS	CalculationEntity/calculationResultCollection/CalculationResult/@value CalculationEntity/calculationResultCollection/CalculationResult/calculationDataCollection/CalculationData/@value	ST
Measured Value Sequence (0040,A300) > Measurement Units Code Sequence (0040,08EA)	Code Sequence Macro	CalculationEntity/calculationResultCollection/CalculationResult/unitOfMeasure	ST
Numeric Value Qualifier Code Sequence (0040,A301)	Code Sequence Macro	CalculationEntity/calculationResultCollection/CalculationResult/calculationDataCollection/CalculationData/@value	ST

The [ISO 21090] PQ data type is not used in AIM.

The Concept Name of the measurement is usually pre-coordinated in a single CalculationEntity/typeCode entry. If there is more than one CalculationEntity/typeCode, the first is assumed to be the primary concept and the others may be modifiers that, if recognized as such, may be mapped to method and derivation, or if otherwise recognized and name-value pair of concepts can be constructed can be encoded as generic modifiers, but otherwise have to be ignored.

The Numeric Value may be found as the single value of a CompactCalculationResult (i.e., value child of CalculationResult) or the first value of an ExtendedCalculationResult (i.e., nested within calculationResultCollection). This can give rise to a difference in representation in a round trip conversion.

Units of measurement shall be converted from a text string (ST) to a Coded Sequence entry using the UCUM Code Values and "UCUM" as the Coding Scheme Designator (in AIM, CalculationResult/unitOfMeasure is defined as "A string representation of UCUM unit for the value of the calculation").

The AIM CalculationData/@value shall be assumed to be in the US English locale (i.e., periods are used as the decimal point, not commas, etc.).

The length of the AIM CalculationData/@value ST is not limited, but the DICOM DS value representation is limited to 16 characters. Values of CalculationData/@value that are too long shall be truncated or rounded to fit in an implementation-dependent manner.

The CalculationResult/dataType (e.g., Double, Integer) is not encoded in the DICOM mapping, since all DICOM SR numeric values are encoded as a Decimal String (DS), so in a round trip from AIM to DICOM and back to AIM will not be recovered (i.e., will always be encoded as Double). For the use cases for this mapping, it is likely that all measurements will be Double anyway.

DICOM allows the Measured Value Sequence (0040,A300) to be sent zero length (empty) if there is no value. In such cases the Numeric Value Qualifier Code Sequence (0040,A301) may be used in DICOM to send a code indicating why, either because of an invalid floating point result (e.g., (114000, DCM, "Not a number") corresponding to [IEEE 754] NaN), or for more general reasons (e.g., (114006, DCM, "Measurement failure")). See CID 42 “Numeric Value Qualifier”. Table A.8-4 indicates that a non-numeric CalculationData/@value may be mapped to Numeric Value Qualifier Code Sequence (0040,A301). Various possible mappings of AIM string values to a subset of DICOM codes corresponding to [IEEE 754] are defined in Table A.8-5. These are based on the:

Java Double.toString(double) definition (see https://docs.oracle.com/javase/8/docs/api/java/lang/Double.html#toString-double-)
[XSD Datatypes]
[ISO 21090]

No similar standard C or C++ mapping is known to exist (e.g., for libc dtostr() or sprintf()). Other languages offer some flexibility (e.g., Python supports case insensitive variants of "NaN" and "Infinity", the latter with or without a sign; see http://docs.python.org/3/library/functions.html#float). For JavaScript, see https://tc39.github.io/ecma262/#sec-tostring-applied-to-the-number-type, https://tc39.github.io/ecma262/#sec-parsefloat-string and https://tc39.github.io/ecma262/#sec-number.parsefloat. The table describes a subset of possible values, the mapping may not be exact (e.g., the definitions of NaN may differ), the mapping is ambiguous (since AIM does not define which string source to use), and the mapping of other values is undefined.

Table A.8-5. Mapping between DICOM Numeric Value Qualifier Code Sequence and AIM ST

DICOM Code	Java String	XML Schema	ISO 21090 Null Flavor
(114000, DCM, "Not a number")	NaN	NaN
(114001, DCM, "Negative Infinity")	-Infinity	-INF	NINF
(114002, DCM, "Positive Infinity")	Infinity	INF	PINF

Image and segmentation references

DICOM image references may be mapped as specified in Table A.8-6.

Table A.8-6. DICOM Image references to AIM Path

DICOM PS3.3, PS3.5 and PS3.16: Image Reference (IMAGE) Value Type		AIM Path and ISO 21090 Data Type
Referenced SOP Sequence > Referenced SOP Class UID	UI	/ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/imageSeries/imageCollection/Image[sopInstanceUid/@root=imageReferenceUid/@root]/sopClassUid/@root	II
Referenced SOP Sequence > Referenced SOP Instance UID	UI	imageReferenceUid/@root	II
Referenced SOP Sequence > Referenced Frame Number	IS	referencedFrameNumber/@value	INT

An image reference in the AIM tree locally consists of the SOP Instance UID only, without SOP Class, which is described elsewhere in the tree in the imageReferenceEntityCollection (which, similar to the DICOM Current Requested Procedure Evidence Sequence or Pertinent Other Evidence Sequence, also contains the Study and Series level information). Hence the use of the predicate "sopInstanceUid/@root=$sopInstanceUID" in the path in the table.

The AIM version 4.2 model includes an optional AccessionNumber in the imageStudy class used in the imageReferenceEntityCollection. This may be preserved in a DICOM SR instance in the ImageLibrary.

DICOM segmentation references may be mapped as specified in Table A.8-7.

Table A.8-7. DICOM Segmentation references to AIM Path

DICOM PS3.3, PS3.5 and PS3.16: Image Reference (IMAGE) Value Type		AIM Path and ISO 21090 Data Type
Referenced SOP Sequence > Referenced SOP Class UID	UI	SegmentationEntity/sopClassUid/@root	II
Referenced SOP Sequence > Referenced SOP Instance UID	UI	SegmentationEntity/sopInstanceUid/@root	II
Referenced SOP Sequence > Referenced Segment Number	US	SegmentationEntity/segmentNumber/@value	INT

The SOP Class UID is included locally in the AIM tree with the reference, rather than being factored out into the imageReferenceEntityCollection, in which it is not present.

Ideally, all segmentation references would be included in either Current Requested Procedure Evidence Sequence or Pertinent Other Evidence Sequence as appropriate. There is optional information in the AIM 4.2 model to identify the Study and Series, but if the Study and Series Instance UIDs are absent, they cannot be assumed to be those of any related images.

The reference to the original image that was segmented or a representative image on which the segmentation may be displayed, which may be present in SegmentationEntity/referencedSopInstanceUid/@root, may be encoded in a separate Content Item if supported by the template (e.g., TID 1410, TID 1411) in (121233, DCM, "Source image for segmentation").

Data saved successfully.

Data saved successfully.

Categories

Transformations between DICOM and other Representations

PS3.21

DICOM PS3.21 2024d - Transformations between DICOM and other Representations

DICOM Standards Committee

Notice and Disclaimer

Foreword

1 Scope and Field of Application

2 Normative and Informative References

3 Definitions

3.1 Codes and Controlled Terminology Definitions:

3.2 DICOM Introduction and Overview Definitions:

3.3 DICOM Service Class Definitions:

3.4 DICOM Information Object Definitions:

3.5 DICOM Data Structures and Encoding

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.3.1 Header

A.3.2 Document Body

A.3.2.1 DICOM SR "Measurement Report" Template Structure

Note

A.3.2.2 Mapping Considerations

A.3.2.3 DICOM Composite Object References

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

Note

A.6.1.1.1 Mapping of DICOM Patient Module

Note

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.7.1 Source AIM v4 Instance

A.7.2 Target DICOM SR "Measurement Report" (TID 1500)

A.8 Overview of Data Types