DICOM PS3.3 2020d - Information Object Definitions

A.35.20.3 Performed Imaging Agent Administration SR IOD Module Table (Current)
Prev | A.35.20 Performed Imaging Agent Administration SR IOD | Next

#### 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 Reference | Synchronization | 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

UIDREF

PNAME

COMPOSITE

IMAGE

WAVEFORM

CONTAINER

###### A.35.20.3.1.3 Relationship Constraints

Relationships between Content Items in the content of this IOD shall be conveyed by-value. Table A.35.20-2 specifies the relationship 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 Values) | Target Value Type
--- | --- | ---
CONTAINER | CONTAINS | TEXT, CODE, NUM, DATETIME, DATE, UIDREF, PNAME, COMPOSITE1, IMAGE1, WAVEFORM1, CONTAINER
TEXT, CODE, NUM, CONTAINER | HAS OBS CONTEXT | TEXT, CODE, NUM, DATETIME, DATE, UIDREF, PNAME, COMPOSITE1
CONTAINER, IMAGE1, WAVEFORM1, COMPOSITE1, NUM | HAS ACQ CONTEXT | 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.

Prev | Up | Next
A.35.20.2 Performed Imaging Agent Administration SR IOD Entity-Relationship Model | Home | A.35.21 Rendition Selection Document IOD

DICOM PS3.3 2020d - Information Object Definitions