ps3 - dicomdicom.nema.org/medical/dicom/2018b/output/pdf/part21... · 2018. 4. 12. · ps3.21 dicom...

PS3.21DICOM PS3.21 2018a2018b - Transformations between

DICOM and other Representations

PS3.21: DICOM PS3.21 2018a2018b - Transformations between DICOM andother RepresentationsCopyright © 2018 NEMA

- Standard -

Page 2

Table of ContentsNotice and Disclaimer ............................................................................................................................................. 9Foreword ............................................................................................................................................................ 111. Scope and Field of Application ............................................................................................................................. 132. Normative and Informative References .................................................................................................................. 153. Definitions ....................................................................................................................................................... 17

3.1. Codes and Controlled Terminology Definitions: ................................................................................................. 174. Symbols and Abbreviations ................................................................................................................................. 195. Conventions ..................................................................................................................................................... 21A. Transformation Between AIM and DICOM SR ........................................................................................................ 23

A.1. Scope and Field of Application ...................................................................................................................... 23A.2. Use Cases ................................................................................................................................................ 23A.3. Structure of DICOM SR Documents ............................................................................................................... 24

A.3.1. Header .............................................................................................................................................. 25A.3.2. Document Body ................................................................................................................................... 26

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

A.4. Structure of AIM Version 4 Instances .............................................................................................................. 28A.5. AIM v4 Structure ........................................................................................................................................ 29A.6. AIM v4 to DICOM TID 1500 Mapping ............................................................................................................. 29

A.6.1. Mapping of Constrained AIM v4 .............................................................................................................. 30A.6.1.1. Header ........................................................................................................................................ 30

A.6.1.1.1. Mapping of DICOM Patient Module ............................................................................................ 31A.6.1.1.2. Mapping of DICOM Clinical Trial Subject Module ........................................................................... 31A.6.1.1.3. Mapping of DICOM General Study Module ................................................................................... 31A.6.1.1.4. Mapping of DICOM Patient Study Module .................................................................................... 32A.6.1.1.5. Mapping of DICOM Clinical Trial Study Module ............................................................................. 32A.6.1.1.6. Mapping of DICOM SR Document Series Module .......................................................................... 32A.6.1.1.7. Mapping of DICOM Clinical Trial Series Module ............................................................................ 33A.6.1.1.8. Mapping of DICOM General Equipment Module ............................................................................ 33A.6.1.1.9. Mapping of DICOM SR Document General Module ........................................................................ 33A.6.1.1.10. Mapping of DICOM SR Document Content Module ...................................................................... 35A.6.1.1.11. Mapping of DICOM SOP Common Module ................................................................................. 36

A.6.1.2. Content Tree ................................................................................................................................ 37TID 1500. Mapping of Measurement Report ............................................................................................... 37TID 1501. Mapping of Measurement Group ............................................................................................... 39TID 1502. Mapping of Time Point Context ................................................................................................. 42TID 1410. Mapping of Planar ROI Measurements ....................................................................................... 43TID 1411. Mapping of Volumetric ROI Measurements .................................................................................. 46TID 1419. Mapping of ROI Measurements ................................................................................................. 50TID 1420. Mapping of Measurements Derived From Multiple ROI Measurements .............................................. 55TID 300. Mapping of Measurement .......................................................................................................... 56TID 320. Mapping of Image or Spatial Coordinates ...................................................................................... 60TID 4019. Mapping of Algorithm Identification ............................................................................................. 61TID 4108. Mapping of Tracking Identifier ................................................................................................... 62TID 1204. Mapping of Language of Content Item and Descendants ................................................................ 63TID 1001. Mapping of Observation Context ................................................................................................ 63TID 1002. Mapping of Observer Context ................................................................................................... 64TID 1003. Mapping of Person Observer Identifying Attributes ........................................................................ 64TID 1600. Mapping of Image Library ......................................................................................................... 66TID 1601. Mapping of Image Library Entry ................................................................................................. 66TID 1602. Mapping of Image Library Entry Descriptors ................................................................................. 66

A.7. Sample Documents .................................................................................................................................... 70A.7.1. Source AIM v4 Instance ........................................................................................................................ 70A.7.2. Target DICOM SR "Measurement Report" (TID 1500) ................................................................................. 74

A.8. Overview of Data Types .............................................................................................................................. 91

- Standard -

Page 3DICOM PS3.21 2018a2018b - Transformations between DICOM and other Representations

- Standard -

DICOM PS3.21 2018a2018b - Transformations between DICOM and other RepresentationsPage 4

List of FiguresA.2-1. Annotation Creation and Transformation .......................................................................................................... 23A.3-1. SR Document Structure ................................................................................................................................ 25A.3.2.1-1. Template Structure Summarized from PS 3.16 ............................................................................................. 27A.4-1. AIM v4 Instance Structure ............................................................................................................................. 29

- Standard -


- Standard -


List of TablesA.3.1-1. Transformation of DICOM SR IOD Modules .................................................................................................... 25A.6.1.1.1-1. Mapping of DICOM Patient Module .......................................................................................................... 31A.6.1.1.3-1. Mapping of DICOM General Study Module ................................................................................................ 32A.6.1.1.6-1. Mapping of DICOM SR Document Series Module ....................................................................................... 32A.6.1.1.8-1. Mapping of DICOM General Equipment Module ......................................................................................... 33A.6.1.1.9-1. Mapping of DICOM SR Document General Module ..................................................................................... 33A.6.1.1.11-1. Mapping of DICOM SOP Common Module .............................................................................................. 36TID 1500. Mapping of Measurement Report ............................................................................................................... 37TID 1501. Mapping of Measurement Group ............................................................................................................... 39TID 1502. Mapping of Time Point Context ................................................................................................................. 42TID 1410. Mapping of Planar ROI Measurements ....................................................................................................... 43TID 1411. Mapping of Volumetric ROI Measurements .................................................................................................. 47TID 1419. Mapping of ROI Measurements ................................................................................................................. 50TID 1420. Mapping of Measurements Derived From Multiple ROI Measurements .............................................................. 55TID 300. Mapping of Measurement .......................................................................................................................... 57TID 320. Mapping of Image or Spatial Coordinates ...................................................................................................... 61TID 4019. Mapping of Algorithm Identification ............................................................................................................. 62TID 4108. Mapping of Tracking Identifier ................................................................................................................... 63TID 1204. Mapping of Language of Content Item and Descendants ................................................................................ 63TID 1001. Mapping of Observation Context ................................................................................................................ 64TID 1002. Mapping of Observer Context ................................................................................................................... 64TID 1003. Mapping of Person Observer Identifying Attributes ........................................................................................ 65TID 1600. Mapping of Image Library ......................................................................................................................... 66TID 1601. Mapping of Image Library Entry ................................................................................................................. 66TID 1602. Mapping of Image Library Entry Descriptors ................................................................................................. 67A.7.2-1. Transformed SR document encoding at the Attribute level ................................................................................. 74A.8-1. ISO 21090 Data Types used in AIM V4 ............................................................................................................ 92A.8-2. Mapping between DICOM Basic Code Attributes and AIM ISO 21090 Code Data Types (CD) ..................................... 93A.8-3. Mapping between DICOM Person Name (PN) ans ISO 21090 Data Type Person Name (PN) ..................................... 93A.8-4. Mapping between DICOM Numeric Measurement Value Types and ISO 21090 Data Types ....................................... 94A.8-5. Mapping between DICOM Numeric Value Qualifier Code Sequence and AIM ST ...................................................... 95A.8-6. DICOM Image references to AIM Path ............................................................................................................. 96A.8-7. DICOM Segmentation references to AIM Path ................................................................................................... 96

- Standard -


- Standard -


Notice and DisclaimerThe information in this publication was considered technically sound by the consensus of persons engaged in the development andapproval of the document at the time it was developed. Consensus does not necessarily mean that there is unanimous agreementamong 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 voluntaryconsensus standards development process. This process brings together volunteers and/or seeks out the views of persons who havean interest in the topic covered by this publication. While NEMA administers the process and establishes rules to promote fairnessin the development of consensus, it does not write the document and it does not independently test, evaluate, or verify the accuracyor 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 informationpublished herein, and disclaims and makes no warranty that the information in this document will fulfill any of your particular purposesor needs. NEMA does not undertake to guarantee the performance of any individual manufacturer or seller's products or services byvirtue 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 behalfof any person or entity, nor is NEMA undertaking to perform any duty owed by any person or entity to someone else. Anyone usingthis document should rely on his or her own independent judgment or, as appropriate, seek the advice of a competent professionalin determining the exercise of reasonable care in any given circumstances. Information and other standards on the topic covered bythis publication may be available from other sources, which the user may wish to consult for additional views or information not coveredby this publication.

NEMA has no power, nor does it undertake to police or enforce compliance with the contents of this document. NEMA does not cer-tify, test, or inspect products, designs, or installations for safety or health purposes. Any certification or other statement of compliancewith any health or safety-related information in this document shall not be attributable to NEMA and is solely the responsibility of thecertifier or maker of the statement.

- Standard -


- Standard -


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

- Standard -


- Standard -


1 Scope and Field of ApplicationThis 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, applicableto 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.

- Standard -


- Standard -


2 Normative and Informative ReferencesThe following standards contain provisions that, through reference in this text, constitute provisions of this Standard. At the time ofpublication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standardare 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 Release1 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 AIM3.0 and 4.0 Models. https://wiki.nci.nih.gov/display/AIM/Changes+from+AIM+3.0%2C+Revision+11+to+AIM+Foundation#ChangesfromAIM3.0,Revision11toAIMFoundation-ISO21090DataTypes .

[AIM Model v4 rv48] NCI. 2013/03. Annotation and Image Markup model version 4. https://wiki.nci.nih.gov/display/AIM/Annotation+and+Image+Markup+-+AIM#AnnotationandImageMarkup-AIM-AIMModel .

[Extending AIM] 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, DanielL. 2010/04. 23. 2. 217–225. “The caBIG™ Annotation and Image Markup Project”. 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 MarkupTemplate Builder”. 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”.10.1007/s10278-014-9710-3. http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4391072/ .

- Standard -


http://www.iec.ch/members_experts/refdocs/iec/isoiecdir-2%7Bed7.0%7Den.pdfhttp://www.iec.ch/members_experts/refdocs/iec/isoiecdir-2%7Bed7.0%7Den.pdfhttp://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=35646http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=35646http://www.hl7.org/implement/standards/product_brief.cfm?product_id=357http://www.w3.org/TR/2006/REC-xml11-20060816/http://www.w3.org/TR/xmlschema-2/https://wiki.nci.nih.gov/display/AIM/Changes+from+AIM+3.0%2C+Revision+11+to+AIM+Foundation#ChangesfromAIM3.0,Revision11toAIMFoundation-ISO21090DataTypeshttps://wiki.nci.nih.gov/display/AIM/Changes+from+AIM+3.0%2C+Revision+11+to+AIM+Foundation#ChangesfromAIM3.0,Revision11toAIMFoundation-ISO21090DataTypeshttps://wiki.nci.nih.gov/display/AIM/Annotation+and+Image+Markup+-+AIM#AnnotationandImageMarkup-AIM-AIMModelhttps://wiki.nci.nih.gov/display/AIM/Annotation+and+Image+Markup+-+AIM#AnnotationandImageMarkup-AIM-AIMModelhttps://wiki.nci.nih.gov/display/AIM/Extending+the+AIM+Modelhttp://www.ncbi.nlm.nih.gov/pmc/articles/PMC2837161/http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2837161/http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3393884/http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4391072/

- Standard -


3 DefinitionsFor the purposes of this Standard the following definitions apply.

3.1 Codes and Controlled Terminology Definitions:The following definitions are commonly used in this Part of the DICOM Standard:

Coding Schemes Dictionaries (lexicons) of concepts (terms) with assigned codes and well defined meanings.

See Section 3.1 "Codes and Controlled Terminology Definitions" in “Codes and Controlled TerminologyDefinitions:” in PS3.16.

Content Item A node in the Content Tree of a DICOM SR document, consisting of either a container with a coded ConceptName, or a name-value pair with a coded Concept Name and a Concept Value.

Content Tree The tree of Content Items of a DICOM SR document.

Context Group A set of coded concepts defined by a Mapping Resource forming a set appropriate to use in a particularcontext.


Context ID (CID) Identifier of a Context Group.


Template A pattern that describes the Content Items, Value Types, Relationship Types and Value Sets that may beused in part of a Structured Report Content Tree, or in other Content Item constructs, such as AcquisitionContext or Protocol Context. Analogous to a Module of an Information Object Definition.


Template ID (TID) Identifier of a Template.


- Standard -


part16.pdf#sect_3.1part16.pdf#sect_3.1part16.pdf#sect_3.1part16.pdf#sect_3.1part16.pdf#sect_3.1part16.pdf#sect_3.1part16.pdf#sect_3.1part16.pdf#sect_3.1part16.pdf#sect_3.1part16.pdf#sect_3.1

- Standard -


4 Symbols and AbbreviationsThe 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

- Standard -


- Standard -


5 ConventionsTerms listed in Section 3 Definitions are capitalized throughout the document.

- Standard -


- Standard -


A Transformation Between AIM and DICOMSRA.1 Scope and Field of ApplicationNCI 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 encodingare version specific. The version transformed in this document is Version 4 [Extending AIM]. Though AIM instances can be generatedaccording to application-specific templates [ref. AIM template builder], such templates are too use-case specific to be detailed in thetransformation described in this Part. Rather, common patterns of use implemented by well known implementations (ref. CC, refePAD) 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 MeasurementReport specifies a basic DICOM SR report template for quantitative measurements and categorical statements for single identifiablepatient subjects including regions of interest defined by spatial coordinates or segmentations.

A.2 Use CasesThe basic use case for the transformation from AIM to DICOM SR is exchange of quantitative and categorical information aboutDICOM 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 DICOMinstances such as segmentations. The flow of information between systems that might make use of a conversion between AIM andDICOM SR instances is considered in Figure A.2-1.

DICOM SR

AIM Annotations

Voice RecognitionReporting System

DICOM Image

DICOM Segmentation

Convert AIM ↔ SR

Legend: Convert

Send

Reference

AIMWorkstation

DICOM SRWorkstation

PACS Store,Distribute,

Review

Figure A.2-1. Annotation Creation and Transformation

Various different transformation scenarios should be considered:

a. Transformation of a complete AIM instance to a complete DICOM SR Measurement Report. The receiver optionally selects rel-evant parts of the transformed document for further processing or static or interactive visualization by the user.

- Standard -


part16.pdf#sect_TID_1500part16.pdf#sect_TID_1500part16.pdf#sect_TID_1500

b. Transformation of a subset of a AIM instance to a DICOM SR Measurement Report. This subset comprises the relevant inform-ation for a specific use-case.

c. Transformation of multiple related AIM instances to a single DICOM SR Measurement Report. The selected related AIM instancescomprise the relevant information for a specific use-case.

This part of the Standard does not mandate any particular transformation scenario. Transformations of various compatible componentsof AIM and DICOM SR TID 1500 are described, allowing each of these scenarios to be implemented as appropriate. This part of theStandard 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 storagesystem, possibly displaying it with a DICOM SR aware application, transforming it back into an AIM instance after retrieval fromthe 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 aggreg-ation (e.g., "analytics", "data mining", "big data", "machine learning", and "deep learning"). The conversion described here is intendedto 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 contentto a DICOM SR that might have been created de novo by a similar application. For instance, there are various encoding choices thatan 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 allof its content. Post-coordinated concepts, such as measurement and derivation methods, may be preserved by using multiple Calcu-lationEntity/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 samereal world entity (e.g., lesion) identified with different regions of interest (e.g., at different time points or with different modalities), maybe encoded in single or multiple AIM or DICOM SR instances. Whether or not a source AIM or DICOM SR implementation encodesmore than one region of interest (and their accompanying measurements and categorical statements) in a single instance or in sep-arate instances, and whether the conversion from one form to the other "bundles" multiple instances into a single instance, or "unbundles"a single instance into multiple instances, is not prescribed. The AIM 4.0 model allows for the encoding of multiple marked up regionsand multiple measurements in a single annotation instance, but does not provide a mechanism for identifying which markup is asso-ciated with which measurement; it is therefore necessary to assume that all markup applies to all measurements and vice versa.

1. For example, for RECIST measurements that involve the long and short axis of a lesion, though it is currently possible to encodein AIM (and map to TID 1500) the measurements as derived from a planar volumetric ROI, and recognize them by their conceptname code, it is not also possible to encode the endpoints of the measured axes of the pair of linear measurements. Nor is areverse mapping of such information encoded in TID 1500 into AIM possible. Some current AIM implementations use privateextensions to address this use case, but mapping these is beyond the scope of the Standard.

2. It is expected that a future revision of the AIM 4.0 model will allow for explicit linkage of markup and measurements, probablyusing statements, e.g., CalculationEntityReferencesMarkupEntityStatement and CalculationEntityReferencesSegmentationEntityS-tatement, at which time the appropriate mappings will be added.

A.3 Structure of DICOM SR DocumentsDICOM SR documents can be thought of as consisting of a document header and a document body. The header metadata attributevalues 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 thecoded report title. The Content Tree (structured content) of the document body is contained in the nested Content Sequence Itemsof that module. "Container" Content Items are part of the Content Sequence. They are structural elements of the SR document bodystructure. 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 betweenContent Items.

- Standard -


part16.pdf#sect_TID_1500part03.pdf#PS3.3part03.pdf#sect_C.17.3

Header

Content Tree

Root Content Itemincl. Report Title

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 beencoded 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 encodeTID 1500 instances unless 3D patient-relative coordinates (rather than 2D image-relative coordinates or segmentations) are used todefine 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

TransformationUsageReferenceModuleIESection A.6.1.1.1MC.7.1.1PatientPatientSection A.6.1.1.2UC.7.1.3Clinical Trial SubjectSection A.6.1.1.3MC.7.2.1General StudyStudySection A.6.1.1.4UC.7.2.2Patient StudySection A.6.1.1.5UC.7.2.3Clinical Trial StudySection A.6.1.1.6MC.17.1SR Document SeriesSeriesSection A.6.1.1.7UC.7.3.2Clinical Trial SeriesSection A.6.1.1.8MC.7.5.1General EquipmentEquipmentSection A.6.1.1.9MC.17.2SR Document GeneralDocumentSection A.6.1.1.10MC.17.3SR Document ContentSection A.6.1.1.11MC.12.1SOP Common

Patient Module

The Patient Module specifies the Attributes of the Patient that describe and identify the Patient who is the subject of a Study. ThisModule contains Attributes of the patient that are needed for interpretation of the Image and are common for all studies performedon 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

- Standard -


part16.pdf#sect_TID_1500part03.pdf#PS3.3part03.pdf#sect_C.7.1.1part03.pdf#sect_C.7.1.3part03.pdf#sect_C.7.2.1part03.pdf#sect_C.7.2.2part03.pdf#sect_C.7.2.3part03.pdf#sect_C.17.1part03.pdf#sect_C.7.3.2part03.pdf#sect_C.7.5.1part03.pdf#sect_C.17.2part03.pdf#sect_C.17.3part03.pdf#sect_C.12.1

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 anynumber 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 ofComposite Instances.

SR Document General Module

The SR Document General Module defines the general Attributes of an SR Document Instance. These Attributes identify the SRDocument 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 SOPInstances.

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 (referto 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 DocumentContent Module.

A.3.2.1 DICOM SR "Measurement Report" Template StructureTID 1500 is the top-level template of the DICOM SR Measurement Report (PS3.16). It includes sub-templates as shown in Fig-ure A.3.2.1-1.

- Standard -


part16.pdf#sect_TID_1500part16.pdf#PS3.16

TID 1204

Language ofContent Item andDescendants

MeasurementReport

TID 1500

Observer Context

TID 1001

Procedure Context

TID 1005

Subject Context

TID 1006

Subject Context,Device

TID 1010

Subject Context,Fetus

TID 1008

Subject Context,Patient

TID 1007

Subject Context,Specimen

TID 1009

Subject Context,Patient

TID 1007

AlgorithmIdentification

TID 4019

Equation or Table

TID 315

MeasurementProperties

TID 310

Quotation

TID 1000

ROIMeasurements

TID 1419

Image Library

TID 1600

Image Library EntryDescriptors

TID 1602

Image Library EntryDescriptors

TID 1602

Image Library EntryDescriptors fo MR

TID 1606

Image Library EntryDescriptors for Cross-Sectional Modalities

TID 1604

Image Library EntryDescriptors for Projection Radiography

TID 1603

Image Library EntryDescriptors for CT

TID 1605

Image Library EntryDescriptors fo PET

TID 1607

Image Library Entry

TID 1601

Image Library EntryDescriptors fo MR

TID 1606

Image Library EntryDescriptors for Cross-Sectional Modalities

TID 1604

Image Library EntryDescriptors for Projection Radiography

TID 1603

Image Library EntryDescriptors for CT

TID 1605

Image Library EntryDescriptors fo PET

TID 1607

Planar ROIMeasurements

TID 1410

Time PointContext

TID 1502


TID 4019

Equation or Table

TID 315


TID 310

Quotation

TID 1000


TID 4019

Quotation

TID 1000

Tracking Identifier

TID 4108

ROIMeasurements

TID 1419

Volumetric ROIMeasurements

TID 1411

Time PointContext

TID 1502

Waveform or TemporalCoordinates

TID 321

Equation or Table

TID 315


TID 310

Image or SpatialCoordinates

TID 320

Measurement

TID 300

MeasurementGroup

TID 1501

Time PointContext

TID 1502

Measurements Derived fromMultiple ROI Measurements

TID 1420

Device ObserverIdentifying Attributes

TID 1004

Person ObserverIdentifying AttributesObserver Context

TID 1002 TID 1003

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

Note

1. The use of TID 1001 Observation Context within TID 1000 Quotation is not shown because it is not relevant to themapping use cases.

- Standard -


2. The use of TID 311 Measurement Statistical Properties and TID 312 Normal Range Properties within TID 310 Measure-ment Properties is not shown because it is not relevant to the mapping use cases.

3. The use of TID 1410 Planar ROI Measurements, TID 1411 Volumetric ROI Measurements, and TID 310 MeasurementProperties within TID 1420 is not shown because it is not relevant to the mapping use cases.

A.3.2.2 Mapping ConsiderationsThe goal of this document is to specify a mapping between constrained AIM v4 instances and TID 1500 Measurement Report DICOMSR 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 ofsubject 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 AIMmodel (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 SeriesModule) 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 ofthe history of de-identification explicitly. I.e., identifiers will be converted unchanged and whether they have been de-identified willnot 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 ReferencesThe hierarchical attributes describing DICOM composite object references are used whenever DICOM composite objects are referencedin 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 AIMinstance are included in the AIM DicomImageReferenceEntity class.

A.4 Structure of AIM Version 4 InstancesAIM instances are encoded in XML according to a schema generated from the AIM Model [AIM Model v4 rv48], which is defined inUML. Figure A.4-1 is a simplified view rather than the entire model, showing only those UML classes and attributes relevant to thetransformations described in this part.

- Standard -


part16.pdf#sect_TID_1500

AIM:: Entity

- uniqueIdentifier: II

AIM:: ImagingObservationEntity

- comment: ST [0..1]- isPresent: BL [0..1]- label: ST [0..1]- questionIndex: INT [0..1]- questionTypeCode: CD [0..n] {ordered}- typeCode: CD [1..n] {ordered}::Entity- uniqueIdentifier: II

AIM:: ImagingPhysicalEntity

- label: ST [0..1]- typeCode: CD [1..n] {ordered}::Entity- uniqueIdentifier: II

AIM:: InferenceEntity

- comment: ST [0..1]- imageEvidence: BL- isPresent: BL [0..1]- label: ST [0..1]- questionIndex: INT [0..1]- questionTypeCode: CD [0..n] {ordered}- typeCode: CD [1..n] {ordered}::Entity- uniqueIdentifier: II

AIM:: AnnotationEntity

- comment: ST [0..1]- dateTime: TS- name: ST- templateUid: II [0..1]- typeCode: CD [1..n] {ordered}::Entity- uniqueIdentifier: II

AIM:: ImageAnnotation

::AnnotationEntity- comment: ST [0..1]- dateTime: TS- name: ST- precedentReferencedAnnotationUid: II [0..1]- templateUid: II [0..1]- typeCode: CD [1..n] {ordered}::Entity- uniqueIdentifier: II

AIM:: ImageAnnotationStatement

AIM:: SegmentationEntity

-imageAnnotations

-imageAnnotationCollection

1..*

1-imageReferenceEntityCollection

-imageAnnotation

1

0..* -segmentationEntityCollection

-imageAnnotation

1

0..*

1

-markupEntityCollection

-imageAnnotation

1

0..*

-inferenceEntityCollection

-annotationEntity

1

-calculationResultEntity

1

-annotationEntity

0..*-calculationEntityCollection

1-calculationEntity

-calculationEntity

10..1-algorithm

0..*-calculationResultCollection

1-extendedCalculationResultEntity

0..*-calculationDataCollection

1-calculationDataEntity

1..*-coordinateCollection

1..*-dimensionCollection

0..*-imagingPhysicalEntityCollection

-annotationEntity

1

0..*-imagingObservationEntityCollection

-annotationEntity

1

0..*

-imagingObservationEntity 1

-imagingObservationCharacteristicCollection 0..*

-imagingPhysicalEntity 1

-imagingPhysicaEntityCharacteristicCollection 0..*

-annotationCollection

-equipment

1

0..1

-annotationCollection

-user

1

0..1

-twoDimensionGeometricShapeEntity

-twoDimensionSpatialCoordinateCollection

1

0..1

-imageAnnotationCollection

-person

1

0..1

AIM:: ImageReferenceEntity

AIM:: DICOMImageReferenceEntity

- instanceUid: II- startDate: TS- startTime: TS

AIM:: ImageStudy

- instanceUid: II- modality: CD

AIM:: ImageSeries

- sopClassUid: II- sopInstanceUid: II

AIM:: Image

-imageSeries

-imageCollection

1

1..*

-imageStudy

-imageSeries

1

1

-dicomImageReferenceEntity

-imageStudy

1

1

AIM:: ImageAnnotationCollection

::AnnotationCollection- aimVersion: AimVersion- dateTime: TS- description: ST [0..1]- uniqueIdentifier: II

AIM:: Person

- birthDate: TS [0..1]- ethnicGroup: ST [0..1]- id: ST- name: ST- sex: ST [0..1]

AIM:: AnnotationCollection

- aimVersion: AimVersion- dateTime: TS- description: ST [0..1]- uniqueIdentifier: II

AIM:: User

- loginName: ST- name: ST- numberWithinRoleOfClinicalTrial: INT [0..1]- roleInTrial: ST [0..1]

AIM:: Equipment

- manufacturerModelName: ST [0..1]- manufacturerName: ST- softwareVersion: ST [0..1]

AIM:: DicomSegmentationEntity

- referencedSopInstanceUid: II- segmentNumber: INT- sopClassUid: II*- sopInstanceUid: II

::Entity- uniqueIdentifier: II

AIM:: MarkupEntity

AIM:: GeometricShapeEntity

- comment: ST [0..1]- includeFlag: BL- label: ST [0..1]- questionIndex: INT [0..1]- questionTypeCode: CD [0..n]- shapeIdentifier: INT::Entity- uniqueIdentifier: II

AIM:: TwoDimensionPolyline

- coordinateIndex: INT- x: REAL- y: REAL

AIM:: TwoDimensionSpatialCoordinate

- imageReferenceUid: II [0..1]- referencedFrameNumber: INT [0..1]

AIM:: TwoDimensionGeometricShapeEntity

AIM:: CalculationEntity

- description: ST- typeCode: CD [1..n] {ordered}::Entity- uniqueIdentifier: II

AIM:: ExtendedCalculationResult

- dataType: CD- type: CalculationResultIdentifier- unitOfMeasure: ST

AIM:: CalculationResult

- compression: CD [0..1]- encoding: CD [0..1]- value: ST

AIM:: CompactCalculationResult

- index: INT- label: ST- size: ST

AIM:: Dimension

- name: ST- type: CD [1..n] {ordered}- version: ST [0..1]

AIM:: Algorithm

- value: ST

AIM:: CalculationData

- dimensionIndex: INT- position: INT

AIM:: Coordinate

AIM:: ImagingPhysicalEntityCharacteristic

- annotatorConfidence: REAL [0..1]- comment: ST [0..1]- label: ST [0..1]- questionIndex: INT [0..1]- questionTypeCode: CD [1..n] {ordered}- typeCode: CD [1..n] {ordered}

- label: ST [0..1]- typeCode: CD [1..n] {ordered}

AIM:: ImagingObservationCharacteristic

Figure A.4-1. AIM v4 Instance Structure

A.5 AIM v4 StructureVersion 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 MappingThe transformation is described in one direction, by enumerating the structures in the target (DICOM SR TID 1500) and describingwhere in the source (AIM v4) the corresponding information may be obtained. The information is tabulated in a manner that can beimplemented as an automated "pull" conversion of an AIM instance into a DICOM SR instance, such as might be described using atransformation 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 createa compliant object, which need to be filled by information from an out of band source or generated de novo, are highlighted. Informationin the source that is not "pulled" into the DICOM encoding will be lost; these omissions are deemed to be harmless from the perspectiveof the relevant use cases.

The tabular representations make use of the following conventions in order to simplify the automatic extraction and use as a formalsyntax 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 correspondingsubordinate 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 individualDICOM 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 wereunambiguous but that would not specify the location reversibly as a target. Accordingly, some of the explicit paths are quite long.

- Standard -


• The requirement type for DICOM Attributes is as defined in PS3.3 for Attributes in Modules and Macros, except that if the containingModule 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 occurduring transformation. For nested elements and attributes, the multiplicity is expressed as the combination of the multiplicity alongthe entire path. For example, the aim:name attribute has a multiplicity of 1:1 in an aim:Person class but is associated with theaim: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 itappears in the XML instance.

• Data type transformations are assumed and are not described further unless there is a specific requirement. For example, conversionfrom DICOM DA, TM and DT VR Attributes to AIM TS Data Type values is implicit, including extraction/population of the appropriatesub-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 notdefined. For example, aim:Person/sex has no explicitly defined value set but maps to DICOM PatientSex, which does; so if AIMimplementations 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, whichmay 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 anIS 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 SeriesModule 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 themapping 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 HeaderGeneral 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 describedin this transformation since they are relevant only in the context of a managed DICOM SR document environment and have nocorrelate 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 usedto match composite instance references with their Study and Series context; the AIM DicomImageReferenceEntity class performsa similar function.

• Attributes of the Equivalent Document Sequence (0040,A090) are not described in the transformation since they are relevant onlyin the context of the original DICOM SR document.

- Standard -


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 DAor TM data type (PS3.5). AIM date and time attributes may or may not contain explicit timezone information that may be extractedto 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 basisfor mapping DICOM character sets to AIM XML Unicode ().

Note

Ambiguities exist for mapping individual characters to Unicode (e.g., for Japanese characters). Resolution of those issuesis 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

CommentAIMMultiplicity

AIM DataType

AIM Element or AttributeGeneratedValue

DICOMUsageType

DICOMVM

DICOMVR

DICOM Attribute

0..1STImageAnnotationCollection/person/name/@value

21PNPatientName

0..1STImageAnnotationCollection/person/id/@value

21LOPatientID

0..1TSImageAnnotationCollection/person/birthDate/@value

21DAPatientBirthDate

0..1STImageAnnotationCollection/person/sex/@value

21CSPatientSex

0..1STImageAnnotationCollection/person/ethnicGroup/@value

31SHEthnicGroup

Note

If the annotation concerns a small animal that has been imaged as part of a group of animals in the same image, then thePatientID and other Attributes of this Module will be those of that individual animal, not the group. Currently there is no AIMmechanism to identify the group of animals imaged at the same time that corresponds to the DICOM SourcePatientGrou-pIdentificationSequence.

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.0 model does not provide Study information per se (i.e., conceptually an AIM instance may exist independent of a Study,but DICOM requires that SR instances be part of a Study). Accordingly, during transformation from AIM to SR either a new Studymay be generated, or the SR instance derived from the AIM object could be placed in (one of) the Study(ies) referenced by the AIMinstance, assuming there are any, which produces a predictable transformation, and is described here.

If there is more than one DICOM Study referenced by the AIM object, duplicates of the converted AIM SR instance may be placed ineach of the referenced studies (with different SOP Instance UIDs), in which case the IdenticalDocumentsSequence is required in theSR Document General Module; see PS3.3 C.17.2.2 Identical Documents Sequence.

- Standard -


part05.pdf#PS3.5

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

CommentMultiplicityDataType


DICOMUsageType

DICOMVM

DICOMVR

DICOM Attribute

0..1IIImageAnnotationCollection/imageAnnotations/ImageAnnotation[1]/imageReferenceEntityCollection/ImageReferenceEntity[1]/imageStudy[1]/instanceUid/@root

New if not insource

11UIStudyInstanceUID

0..1TSImageAnnotationCollection/imageAnnotations/ImageAnnotation[1]/imageReferenceEntityCollection/ImageReferenceEntity[1]/imageStudy[1]/startDate/@value

Empty if not insource

21UIStudyDate

0..1TSImageAnnotationCollection/imageAnnotations/ImageAnnotation[1]/imageReferenceEntityCollection/ImageReferenceEntity[1]/imageStudy[1]/startTime/@value

Empty if not insource

21UIStudyTime

Not inAIM.

Empty21PNReferringPhysicianName

Not inAIM.

Empty21SHStudyID

Not inAIM.

Empty21SHAccessionNumber

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.0 model does not support the concept that an annotation itself is part of a series, and it cannot be made part of a referencedimage 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


AIMDataType

AIMElement

orAttribute

GeneratedValue

DICOMUsageType

DICOMVM

DICOMVR

DICOM Attribute

"SR"11CSModalityUsing a generated value meansthat multiple round-trips mayproduce different values.

When mapping multiple AIMinstances related to the samestudy, if the sameSeriesInstanceUID is used theywill appear in the same Series.

New11UISeriesInstanceUID

- Standard -



AIMDataType

AIMElement

orAttribute

GeneratedValue

DICOMUsageType

DICOMVM

DICOMVR

DICOM Attribute

A well-known value means thatmultiple round-trips will use thesame value.

729111ISSeriesNumber

Empty21SQReferencedPerformedProcedureStepSequence

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


AIM DataType


DICOMUsageType

DICOMVM

DICOMVR

DICOM Attribute

0..1STImageAnnotationCollection/equipment/manufacturer/@value

21LOManufacturer

0..1STImageAnnotationCollection/equipment/manufacturerModelName/@value

31LOManufacturerModelName

0..1STImageAnnotationCollection/equipment/softwareVersion/@value

31-nLOSoftwareVersions

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


AIM Element orAttribute

GeneratedValue

DICOMUsageType

DICOMVM

DICOMVR

DICOM Attribute

New11ISInstanceNumber"COMPLETE"11CSCompletionFlag

Sending avalue of"VERIFIED"would triggerthe need tosend theVerifyingObserverSequence,which is notdescribed inthis mapping.

"UNVERIFIED"11CSVerificationFlag

- Standard -




GeneratedValue

DICOMUsageType

DICOMVM

DICOMVR

DICOM Attribute

1..1TSImageAnnotationCollection/dateTime/@value

11DAContentDate

1..1TSImageAnnotationCollection/dateTime/@value

11TMContentTime

Don't sendsequence atall if observeris a devicerather than ahuman sincethe device isdescribed inthe GeneralEquipmentModule.

31-nSQAuthorObserverSequence

DICOM allowsPSN or DEV.

PSN11CSAuthorObserverSequence >ObserverType

If PSN.1..1STImageAnnotationCollection/user/name/@value

1C1PNAuthorObserverSequence >PersonName

If PSN.

Not in AIM.

Empty2C1SQAuthorObserverSequence >PersonIdentificationCodeSequence

Not in AIM.Empty21SQAuthorObserverSequence >InstitutionName

Not in AIM.Empty21SQAuthorObserverSequence >InstitutionCodeSequence

Required ifthis documentis stored withdifferent SOPInstance UIDsin one or moreother Studies

UIDs of otheridenticalconvertedinstances.

1C1SQIdenticalDocumentsSequence

11SQCurrentRequestedProcedureEvidenceSequence

1..1IIImageAnnotationCollection/imageAnnotations/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/instanceUid/@root

11UICurrentRequestedProcedureEvidenceSequence>StudyInstanceUID

11SQCurrentRequestedProcedureEvidenceSequence>ReferencedSeriesSequence

- Standard -




GeneratedValue

DICOMUsageType

DICOMVM

DICOMVR

DICOM Attribute

1..1IIImageAnnotationCollection/imageAnnotations/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/imageSeries/instanceUid/@root

11UICurrentRequestedProcedureEvidenceSequence>ReferencedSeriesSequence>SeriesInstanceUID

11SQCurrentRequestedProcedureEvidenceSequence>ReferencedSeriesSequence>ReferencedSOPSequence

1..1IIImageAnnotationCollection/imageAnnotations/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/imageSeries/imageCollection/Image/sopClassUid/@root

11UICurrentRequestedProcedureEvidenceSequence>ReferencedSeriesSequence>ReferencedSOPSequence>ReferencedSOPClassUID

1..1IIImageAnnotationCollection/imageAnnotations/imageReferenceEntityCollection/ImageReferenceEntity/imageStudy/imageSeries/imageCollection/Image/sopInstanceUid/@root

11UICurrentRequestedProcedureEvidenceSequence>ReferencedSeriesSequence>ReferencedSOPSequence>ReferencedSOPInstanceUID

Not in AIM.Empty21SQPerformedProcedureCodeSequence

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 accordinglyare not described in the same tabular manner as the "header" Attributes, since the mapping depends on the DICOM SR templatestructure. 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:

- Standard -


• TEXT - TextValue

• DATETIME - DateTime

• DATE - Date

• TIME - Time

• PNAME - PersonName

• UIDREF - UID

• NUM - MeasuredValueSequence, MeasuredValueSequence>NumericValue, MeasuredValueSequence>MeasurementUn-itsCodeSequence

• CODE - ConceptCodeSequence

• COMPOSITE - ReferencedSOPSequence, ReferencedSOPSequence>ReferencedSOPClassUID, ReferencedSOPSequence>Ref-erencedSOPInstanceUID

• IMAGE - ReferencedSOPSequence, ReferencedSOPSequence>ReferencedSOPClassUID, ReferencedSOPSequence>Refer-encedSOPInstanceUID, ReferencedSOPSequence>ReferencedFrameNumber, ReferencedSOPSequence>ReferencedSegment-Number

• SCOORD - GraphicData, GraphicType

• SCOORD3D - ReferencedFrameOfReferenceUID, GraphicData, GraphicType

• CONTAINER - ContinuityOfContent, ContentTemplateSequence, ContentTemplateSequence>MappingResource, ContentTem-plateSequence>TemplateIdentifier

A.6.1.1.11 Mapping of DICOM SOP Common Module

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


AIMDataType


DICOMUsageType

DICOMVM

DICOMVR

DICOM Attribute

The fixed value isthe SOP ClassUID of theEnhanced SRStorage SOPClass, which issufficient unlessSCOORD3D areused, in whichcase theComprehensive3D SR StorageSOP Class isrequired, whichhas a UID of"1.2.840.10008.5.1.4.1.1.88.34".

"1.2.840.10008.5.1.4.1.1.88.22"

11UISOPClassUID

- Standard -



AIMDataType


DICOMUsageType

DICOMVM

DICOMVR

DICOM Attribute

1..1IIImageAnnotationCollection>uniqueIdentifier/@root

Generated ifmore than oneconvertedinstance inseparatestudies.

11UISOPInstanceUID

The fixedgenerated valuecorresponds tothe normal UTF-8specified in theXMLDecl of theXML prolog [XML]in the AIMinstance. Othervalues may beused if they aresufficient todescribe all theencodedcharacters in thetransformedinstance. E.g., itmay be omittedentirely if all thecharacters areUS-ASCII.

"ISO_IR 192"11CSSpecificCharacterSet

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


AIMDataType

AIM Elementor Attribute

GeneratedValue

DICOMUsageType

DICOMVM

DICOM VTDICOM SR Path

The fixed ConceptName code is anappropriate choiceselected from CID7021 “MeasurementReport DocumentTitles” in the absenceof a "document title"concept in AIM.

If out of bandinformation isavailable, a moreappropriate code canbe used.

M1CONTAINER(126000, DCM, "ImagingMeasurement Report")

- Standard -


part16.pdf#sect_TID_1500part16.pdf#sect_CID_7021part16.pdf#sect_CID_7021part16.pdf#sect_CID_7021part16.pdf#sect_CID_7021


AIMDataType


GeneratedValue

DICOMUsageType

DICOMVM


TID 1204 “Mapping of Language of Content Item and Descendants”M1INCLUDE(126000, DCM, "ImagingMeasurement Report") >

TID 1001 “Mapping of Observation Context”M1INCLUDE(126000, DCM, "ImagingMeasurement Report") >

The fixed generic codevalue is suggested inlieu of AIM containingany information aboutthe imaging procedure,so more specificprocedure codes suchas those from CID 100“QuantitativeDiagnostic ImagingProcedures” cannot beused.

If out of bandinformation isavailable, a moreappropriate code canbe used.

(P0-0099A,SRT,"Imagingprocedure")

M1-nCODE(126000, DCM, "ImagingMeasurement Report") >(121058, DCM, "Procedurereported")

TID 1600 “Mapping of Image Library”M1INCLUDE(126000, DCM, "ImagingMeasurement Report") >

IFF measurements arepresent in the sourceAIM object

C1CONTAINER(126000, DCM, "ImagingMeasurement Report") >(126010, DCM, "ImagingMeasurements")

TID 1410 “Mapping of Planar ROI Measurements”U1-nINCLUDE(126000, DCM, "ImagingMeasurement Report") >(126010, DCM, "ImagingMeasurements") >

TID 1411 “Mapping of Volumetric ROI Measurements”U1-nINCLUDE(126000, DCM, "ImagingMeasurement Report") >(126010, DCM, "ImagingMeasurements") >

TID 1501 “Mapping of Measurement Group”U1-nINCLUDE(126000, DCM, "ImagingMeasurement Report") >(126010, DCM, "ImagingMeasurements") >

Not applicable tocurrent use cases

C1CONTAINER(126000, DCM, "ImagingMeasurement Report") >(126011, DCM, "DerivedImaging Measurements")

TID 1420 “Mapping of Measurements Derived From Multiple ROIMeasurements”

U1-nINCLUDE(126000, DCM, "ImagingMeasurement Report") >(126011, DCM, "DerivedImaging Measurements") >

- Standard -


part16.pdf#sect_CID_100part16.pdf#sect_CID_100part16.pdf#sect_CID_100part16.pdf#sect_CID_100


AIMDataType


GeneratedValue

DICOMUsageType

DICOMVM


IFF ImagingObservationEntityelements are presentin the source AIMobject

C1CONTAINER(126000, DCM, "ImagingMeasurement Report") >(C0034375, UMLS,"Qualitative Evaluations")

1, 0..1CD,CD

ImageAnnotationCollection/imageAnnotations/ImageAnnotation/imagingObservationEntityCollection/ImagingObservationEntity/questionTypeCode,typeCode

U1-nCODE(126000, DCM, "ImagingMeasurement Report") >(C0034375, UMLS,"Qualitative Evaluations")> CODE

Not used in AIMU1-nTEXT(126000, DCM, "ImagingMeasurement Report") >(C0034375, UMLS,"Qualitative Evaluations")> TEXT

TID 1501 Mapping of Measurement Group

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

Table TID 1501. Mapping of Measurement Group


AIMDataType


DICOMUsageType

DICOMVM


M1CONTAINER(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")

- Standard -




AIMDataType


DICOMUsageType

DICOMVM


Not present inAIM.

Identifies thesession duringwhich themeasurementswere made. TheNCI Thesaurusdefinition is "time,period, or termdevoted to someactivity".

U1TEXT(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (C67447, NCIt,"Activity Session")

1STImageAnnotationCollection/imageAnnotations/ImageAnnotation/name/@value

M1TEXT(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (112039, DCM,"Tracking Identifier")

Using ImageAnnotation/uniqueIdentifieras a proxy forTracking UniqueIdentifier does notallow longitudinalidentification ofthe same lesionbecause ImageAnnotation/uniqueIdentifiermust be unique toeach AIMannotation file;only ImageAnnotation/namecan be used torecognizecommonality.

1IIImageAnnotationCollection/imageAnnotations/ImageAnnotation/uniqueIdentifier/@root

M1UIDREF(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (112040, DCM,"Tracking UniqueIdentifier")

Only a singleaim:typeCodevalue can bemapped.

1..nCDImageAnnotationCollection/imageAnnotations/ImageAnnotation/typeCode

U1CODE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (121071, DCM,"Finding")

- Standard -



AIMDataType


DICOMUsageType

DICOMVM


Not used in AIM.TID 1502 “Mapping of Time Point Context”U1INCLUDE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")>

Not used in AIMat this level.

U1CODE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (G-C036, SRT,"Measurement Method")

If a pairedstructure in AIM,this entry willpre-coordinatethe laterality withthe site.

1..nCDImageAnnotationCollection/imageAnnotations/ImageAnnotation/imagingPhysicalEntityCollection/ImagingPhysicalEntity[label/@value='Location' or label/@value='Lobar Location' orlabel/@value='SegmentalLocation' or label/@value='OrganType']/typeCode

U1-nCODE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (G-C0E3, SRT,"Finding Site")

CID 244“Laterality”

Not used in AIM.

U1CODE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (G-C0E3, SRT,"Finding Site") >(G-C171, SRT,"Laterality")

Not used sinceAIM does nothave amechanism forpost-coordinatingthe location.

U1CODE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (G-C0E3, SRT,"Finding Site") >(G-A1F8, SRT,"Topographicalmodifier")

- Standard -


part16.pdf#sect_CID_244part16.pdf#sect_CID_244


AIMDataType


DICOMUsageType

DICOMVM


Not used in AIM.U1COMPOSITE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (126100, DCM, "RealWorld Value Map usedfor measurement")

TID 300 “Mapping of Measurement”M1-nINCLUDE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")>

Not used in AIM.U1-nCODE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")>$QualitativeEvaluations

Not used in AIM.U1-nTEXT(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")>$QualitativeEvaluations

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


AIMDataType

AIMElement

orAttribute

GeneratedValue

DICOMUsageType

DICOMVM

DICOMVT

DICOM SR Path

Not used inAIM.

U1TEXT(126000, DCM, "Imaging MeasurementReport") > (126010, DCM, "ImagingMeasurements") > (125007, DCM,"Measurement Group") > (126070, DCM,"Subject Time Point Identifier")

- Standard -




AIMDataType

AIMElement

orAttribute

GeneratedValue

DICOMUsageType

DICOMVM

DICOMVT

DICOM SR Path

Not used inAIM.

U1TEXT(126000, DCM, "Imaging MeasurementReport") > (126010, DCM, "ImagingMeasurements") > (125007, DCM,"Measurement Group") > (126071, DCM,"Protocol Time Point Identifier")

Not used inAIM.

M1TEXT(126000, DCM, "Imaging MeasurementReport") > (126010, DCM, "ImagingMeasurements") > (125007, DCM,"Measurement Group") > (C2348792, UMLS,"Time Point")

BCID 6146“Time PointTypes”

Not used inAIM.

U1-nCODE(126000, DCM, "Imaging MeasurementReport") > (126010, DCM, "ImagingMeasurements") > (125007, DCM,"Measurement Group") > (126072, DCM,"Time Point Type")

Not used inAIM.

U1NUM(126000, DCM, "Imaging MeasurementReport") > (126010, DCM, "ImagingMeasurements") > (125007, DCM,"Measurement Group") > (126073, DCM,"Time Point Order")

Not used inAIM.

U1NUM(126000, DCM, "Imaging MeasurementReport") > (126010, DCM, "ImagingMeasurements") > (125007, DCM,"Measurement Group") > (128740, DCM,"Longitudinal Temporal Offset from Event")

Not used inAIM.

U1CODE(126000, DCM, "Imaging MeasurementReport") > (126010, DCM, "ImagingMeasurements") > (125007, DCM,"Measurement Group") > (128740, DCM,"Longitudinal Temporal Offset from Event") >(128741, DCM, "Longitudinal Temporal EventType")

TID 1410 Mapping of Planar ROI Measurements

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

Table TID 1410. Mapping of Planar ROI Measurements


AIMDataType


DICOMUsageType

DICOMVM



- Standard -


part16.pdf#sect_CID_6146part16.pdf#sect_CID_6146part16.pdf#sect_CID_6146part16.pdf#sect_TID_1410


AIMDataType


DICOMUsageType

DICOMVM


Not present inAIM.

Identifies thesession duringwhich themeasurementswere made. TheNCI Thesaurusdefinition is"time, period, orterm devoted tosome activity".




Using ImageAnnotation/uniqueIdentifieras a proxy forTracking UniqueIdentifier doesnot allowlongitudinalidentification ofthe same lesionbecause ImageAnnotation/uniqueIdentifiermust be uniqueto each AIMannotation file;only ImageAnnotation/namecan be used torecognizecommonality.



Only a singleaim:typeCodevalue can bemapped.

1..nCDImageAnnotationCollection/imageAnnotations/ImageAnnotation/typeCode

U1CODE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (121071, DCM,"Finding")

- Standard -



AIMDataType


DICOMUsageType

DICOMVM


Not used in AIM.TID 1502 “Mapping of Time Point Context”U1INCLUDE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")>

A Graphic Typeof MULTIPOINTis not permittedin the DICOMtemplate.

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

MC1SCOORD(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (111030, DCM,"Image Region")

The ReferencedSOP Class UIDis obtained fromimageReferenceEntityCollection;see Table A.8-5

1, 0..1II,INT

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

M1IMAGE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (111030, DCM,"Image Region") >IMAGE

Reference shallbe to aSegmentationImage, with asingle valuespecified inReferencedFrame Number,and with a singlevalue specified inReferencedSegmentNumber

ImageAnnotationCollection/imageAnnotations/ImageAnnotation/segmentationEntityCollection/SegmentationEntity

MC1IMAGE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (121214, DCM,"ReferencedSegmentation Frame")

ImageAnnotationCollection/imageAnnotations/ImageAnnotation/segmentationEntityCollection/SegmentationEntity/referencedSopInstanceUid/@root

MC1IMAGE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (121233, DCM,"Source image forsegmentation")

- Standard -



AIMDataType


DICOMUsageType

DICOMVM


Not used in AIM.U1IMAGE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (121200, DCM,"Illustration of ROI")

Not used in AIM.U1COMPOSITE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")> (126100, DCM, "RealWorld Value Map usedfor measurement")

Not used in AIM.TID 1419 “Mapping of ROI Measurements”M1INCLUDE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")>

Not used in AIM.U1-nCODE(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")>$QualitativeEvaluations

Not used in AIM.U1-nTEXT(126000, DCM, "ImagingMeasurement Report")> (126010, DCM,"ImagingMeasurements") >(125007, DCM,"Measurement Group")>$QualitativeEvaluations

TID 1411 Mapping of Volumetric ROI Measurements

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

- Standard -



Table TID 1411. Mapping of Volumetric ROI Measurements


AIMDataType


DICOMUsageType

DICOMVM



Not present inAIM.

Identifies thesession duringwhich themeasurementswere made. TheNCI Thesaurusdefinition is"time, period, orterm devoted tosome activity".




Using ImageAnnotation/uniqueIdentifieras a proxy forTracking UniqueIdentifier doesnot allowlongitudinalidentification ofthe same lesionbecause ImageAnnotation/uniqueIdentifiermust be uniqueto each AIMannotation file;only ImageAnnotation/namecan be used torecognizecommonality.



- Standard -



AIMDataType


DICOMUsageType

DICOMVM

D