DICOM PS3.3 2020a - Information Object Definitions |
Page 331 |
Note
1.The HAS CONCEPT MOD relationship is used to modify the meaning of the concept name of a parent node (or Source Content Item), with a modifier or qualifier in a child (target node) to provide a more descriptive explanation, a different coded language translation, or to define a post-coordinated concept.
A.35.20 Performed Imaging Agent Administration SR IOD
A.35.20.1 Performed Imaging Agent Administration SR IOD Description
The Performed Imaging Agent Administration SR IOD describes the imaging agent delivery whether manual methods or automated power-injector devices were used. It includes a reference to the Planned Imaging Agent Administration Procedure SR SOP instance if based on a plan.
A.35.20.2 Performed Imaging Agent Administration SR IOD Entity-Relationship Model
This IOD uses the E-R Model in Section A.1.2, with only the SR Document IE below the Series IE.
A.35.20.3 Performed Imaging Agent Administration SR IOD Module Table
Table A.35.20-1. Performed Imaging Agent Administration SR IOD Modules
IE |
Module |
Reference |
Usage |
Patient |
Patient |
C.7.1.1 |
M |
|
Clinical Trial Subject |
C.7.1.3 |
U |
Study |
General Study |
C.7.2.1 |
M |
|
Patient Study |
C.7.2.2 |
U |
|
Clinical Trial Study |
C.7.2.3 |
U |
Series |
SR Document Series |
C.17.1 |
M |
|
Clinical Trial Series |
C.7.3.2 |
U |
Frame of ReferenceSynchronization |
C.7.4.2 |
M |
|
Equipment |
General Equipment |
C.7.5.1 |
M |
|
Enhanced General Equipment |
C.7.5.2 |
M |
Document |
SR Document General |
C.17.2 |
M |
|
SR Document Content |
C.17.3 |
M |
|
SOP Common |
C.12.1 |
M |
A.35.20.3.1 Performed Imaging Agent Administration SR IOD Content Constraints
A.35.20.3.1.1 Template
The document shall be constructed from TID 11020 “Performed Imaging Agent Administration” invoked at the root node.
A.35.20.3.1.2 Value Type
Value Type (0040,A040) in the Content Sequence (0040,A730) of the SR Document Content Module is constrained to the following Enumerated Values (see Table C.17.3-7 for Value Type definitions):
Enumerated Values:
TEXT
CODE
NUM
DATETIME
DATE
- Standard -
Page 332 |
DICOM PS3.3 2020a - Information Object Definitions |
UIDREF
PNAME
COMPOSITE
IMAGE
WAVEFORM
CONTAINER
A.35.20.3.1.3 Relationship Constraints
RelationshipsbetweenContentItemsinthecontentofthisIODshallbeconveyedby-value.TableA.35.20-2specifiestherelationship constraints of this IOD. See Table C.17.3-8 for Relationship Type definitions.
Table A.35.20-2. Relationship Content Constraints for Performed Imaging Agent Administration SR IOD
Source Value Type |
Relationship Type (Enumerated |
Target Value Type |
|
|
Values) |
|
|
CONTAINER |
CONTAINS |
TEXT, CODE, NUM, DATETIME, DATE, UIDREF, PNAME, |
|
|
|
COMPOSITE1, IMAGE1, WAVEFORM1, CONTAINER |
|
TEXT, CODE, NUM, CONTAINERHAS OBS CONTEXT
CONTAINER, IMAGE1, |
HAS ACQ CONTEXT |
WAVEFORM1, COMPOSITE1, |
|
NUM |
|
TEXT, CODE, NUM, DATETIME, DATE, UIDREF, PNAME,
COMPOSITE1
TEXT, CODE, NUM, DATETIME, DATE, UIDREF, PNAME, CONTAINER
any type |
HAS CONCEPT MOD |
TEXT, CODE2 |
TEXT, CODE, NUM |
HAS PROPERTIES |
TEXT, CODE, NUM, DATETIME, DATE, UIDREF, PNAME, |
|
|
IMAGE1, WAVEFORM1, COMPOSITE1, CONTAINER |
PNAME |
HAS PROPERTIES |
TEXT, CODE, DATETIME, DATE, UIDREF, PNAME |
TEXT, CODE, NUM |
INFERRED FROM |
TEXT, CODE, NUM, DATETIME, DATE, UIDREF, PNAME, |
|
|
IMAGE1, WAVEFORM1, COMPOSITE1, CONTAINER |
Note |
|
|
1.The SOP Classes to which an IMAGE or WAVEFORM or COMPOSITE Value Type may refer, is documented in the Conformance Statement for an application (see PS3.2 and PS3.4).
2.The HAS CONCEPT MOD relationship is used to modify the meaning of the concept name of a parent node (or Source Content Item), with a modifier or qualifier in a child (target node) to provide a more descriptive explanation, a different coded language translation, or to define a post-coordinated concept.
A.35.21 Rendition Selection Document IOD
A.35.21.1 Rendition Selection Document IOD Description
The Rendition Selection Document IOD associates a group of time-synchronized Flows produced for a simultaneous presentation, transported using DICOM-RTV.
A.35.21.2 Rendition Selection Document IOD Entity-Relationship Model
This IOD uses the E-R Model in Section A.1.2, with only the SR Document IE below the Series IE.
A.35.21.3 Rendition Selection Document IOD Module Table
Table A.35.21-1 specifies the Modules of the Rendition Selection Document IOD.
- Standard -
DICOM PS3.3 2020a - Information Object Definitions Page 333
Table A.35.21-1. Rendition Selection Document IOD Modules
IE |
Module |
Reference |
Usage |
Patient |
Patient |
C.7.1.1 |
M |
|
Clinical Trial Subject |
C.7.1.3 |
U |
Study |
General Study |
C.7.2.1 |
M |
|
Patient Study |
C.7.2.2 |
U |
|
Clinical Trial Study |
C.7.2.3 |
U |
Series |
Key Object Document Series |
C.17.6.1 |
M |
|
Clinical Trial Series |
C.7.3.2 |
U |
Equipment |
General Equipment |
C.7.5.1 |
M |
|
Enhanced General Equipment |
C.7.5.2 |
M |
FrameOfReferenceSynchronization |
C.7.4.2 |
M |
|
Document |
Key Object Document |
C.17.6.2 |
M |
|
SR Document Content |
C.17.3 |
M |
|
SOP Common |
C.12.1 |
M |
A.35.21.3.1 Rendition Selection Document IOD Content Constraints
A.35.21.3.1.1 Value Type
Value Type (0040,A040) in Content Sequence (0040,A730) of the SR Document Content Module is constrained to the following Enumerated Values (see Table C.17.3-7 for Value Type definitions):
Enumerated Values:
TEXT
CODE
UIDREF
PNAME
COMPOSITE
IMAGE
WAVEFORM
CONTAINER
The IMAGE and WAVEFORM Content Items shall only include references to SOP Instance UIDs of DICOM-RTV Metadata Flows.
A.35.21.3.1.2 Relationship Constraints
Relationships between Content Items in the content of this IOD shall be conveyed in the by-value mode. See Table C.17.3-8 for Re- lationship Type definitions.
Note
Relationships by-reference are forbidden. Therefore, Referenced Content Item Identifier (0040,DB73) is not present in any of the Content Items within the SR Document Content Module.
Table A.35.21-2 specifies the relationship constraints of this IOD.
Table A.35.21-2. Relationship Content Constraints for Rendition Selection Document IOD
Source Value Type |
Relationship Type (Enumerated Values) |
Target Value Type |
CONTAINER |
CONTAINS |
TEXT, IMAGE, WAVEFORM, COMPOSITE |
CONTAINER |
HAS OBS CONTEXT |
TEXT, CODE, UIDREF, PNAME |
CONTAINER |
HAS CONCEPT MOD |
CODE |
- Standard -
Page 334 |
DICOM PS3.3 2020a - Information Object Definitions |
A.35.21.3.1.3 Template Constraints
The document shall be constructed from TID 2010 “Key Object Selection” invoked at the root node.
A.36 Enhanced MR Information Object Definitions
A.36.1 Relationship Between Enhanced MR IODs
Figure A.36-1 illustrates the relationships between the Enhanced MR IODs described in Section A.36.
Source Image Sequence (0008,2112), Referenced Image Sequence (0008,1140) and Referenced Raw Data Sequence (0008,9121) provide references between SOP Instances.
Note
Many Attributes have names and descriptions that include the terms "pixel" and "image". Although MR spectroscopy is not pixel based, some of these "pixel" and "image" Attributes encode concepts that are still relevant for this technique. Where such Attributes appear in the MR Spectroscopy IOD, it may be helpful to consider the term "pixel" to be equivalent to a spectroscopy "voxel", and the term "image" to be equivalent to "MR Spectroscopy SOP Instance".
Image
References Image Sequence |
|
0-n |
|
|
|
|
|
|
|
|
Spectroscopy |
||||||||||||
only if image type is METABOLITE MAP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
References Raw Data Sequence 0-n |
|
|
|
|
|
|
|
|
0-n |
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
References Raw Data Sequence |
|
|
|
||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Raw Data |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
Sequence |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
References Image Sequence 0-n |
References Image Sequence |
|
0-n |
|
|
References Image Sequence |
|
||||||||||||||||
required if planned on |
required if planned on |
|
|
|
|
|
required if planned on |
|
|
||||||||||||||
prior image |
prior image |
|
|
|
|
|
prior image |
|
|||||||||||||||
|
|
|
|
|
|
0-n |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
References Source Image Sequence 0-n |
|
|
|
|
|
|
|
|
0-n References Source Image Sequence |
|
|||||||||||||
for derived images |
|
|
|
|
|
|
|
|
|
|
|
|
|
for derived spectroscopy data |
|
|
|||||||
|
|
|
|
|
|
|
|
|
|
|
0-n |
|
|
References Image Sequence |
|
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
required if planned on |
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
prior spectroscopy data |
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
Prior Image |
|
|
|
|
Prior |
|
|
|
|
|
|
|
|
||||||
|
|
|
|
|
|
Spectroscopy |
|
|
|
|
|
|
|
|
|||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||
Figure A.36-1. Relationships between Enhanced MR IODs
A.36.2 Enhanced MR Image IOD
A.36.2.1 Enhanced MR Image IOD Description
The Enhanced Magnetic Resonance (MR) Image Information Object Definition (IOD) specifies an image, which has been created by a magnetic resonance device.
A.36.2.2 Enhanced MR Image Entity-Relationship Model
This IOD uses the E-R Model in Section A.1.2, with only the Image IE below the Series IE.
A.36.2.3 Enhanced MR Image IOD Module Table
Table A.36-1 specifies the Modules of the Enhanced MR Image IOD.
- Standard -
DICOM PS3.3 2020a - Information Object Definitions |
Page 335 |
Table A.36-1. Enhanced MR Image IOD Modules
IE |
Module |
Reference |
Patient |
Patient |
C.7.1.1 |
|
Clinical Trial Subject |
C.7.1.3 |
Study |
General Study |
C.7.2.1 |
|
Patient Study |
C.7.2.2 |
|
Clinical Trial Study |
C.7.2.3 |
Series |
General Series |
C.7.3.1 |
|
Clinical Trial Series |
C.7.3.2 |
|
MR Series |
C.8.13.6 |
Frame of Frame of Reference |
C.7.4.1 |
|
ReferenceSynchronization |
C.7.4.2 |
|
EquipmentGeneral Equipment |
C.7.5.1 |
|
|
Enhanced General Equipment |
C.7.5.2 |
Image |
Image Pixel |
C.7.6.3 |
|
Enhanced Contrast/Bolus |
C.7.6.4b |
|
Multi-frame Functional Groups |
C.7.6.16 |
|
Multi-frame Dimension |
C.7.6.17 |
|
Cardiac Synchronization |
C.7.6.18.1 |
|
Respiratory Synchronization |
C.7.6.18.2 |
|
Bulk Motion Synchronization |
C.7.6.18.3 |
|
Supplemental Palette Color Lookup TableC.7.6.19 |
|
|
Acquisition Context |
C.7.6.14 |
|
Device |
C.7.6.12 |
|
Specimen |
C.7.6.22 |
|
Enhanced MR Image |
C.8.13.1 |
|
MR Pulse Sequence |
C.8.13.4 |
|
ICC Profile |
C.11.15 |
|
SOP Common |
C.12.1 |
|
Common Instance Reference |
C.12.2 |
|
Frame Extraction |
C.12.3 |
Usage
M
U
M
U
U
M
U
M
M
C - Required if time synchronization was applied.
M
M
M
C - Required if contrast media were applied.
M M
C - Required if cardiac synchronization was applied.
C - Required if respiratory synchronization was applied.
C - Required if bulk motion synchronization was applied.
C - Required if Pixel Presentation (0008,9205) in the Enhanced MR Image Module equals COLOR or MIXED.
M
U
U M
C - Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.
U
M
U
C - Required if the SOP Instance was created in response to a Frame-Level retrieve request
A.36.2.3.1 Enhanced MR Image IOD Content Constraints
The General Image Module, Overlay Plane Module and VOI LUT Module shall not be used in a Standard Extended SOP Class of the Enhanced MR Image.
- Standard -