DICOM PS3.3 2020b - Information Object Definitions

A.35.18.3 Patient Radiation Dose SR IOD Module Table (Current)
Prev | A.35.18 Patient Radiation Dose SR IOD | Next

#### A.35.18.3 Patient Radiation Dose SR IOD Module Table

Table A.35.18-1. Patient Radiation Dose Structured Report 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 | C - shall be present if system time is synchronized to an external reference. May be present otherwise.
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.18.3.1 Patient Radiation Dose SR IOD Content Constraints

###### A.35.18.3.1.1 Template

The document shall be constructed from Baseline TID 10030 “Patient Radiation Dose” invoked at the root node.

###### A.35.18.3.1.2 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

NUM

DATETIME

UIDREF

PNAME

COMPOSITE

IMAGE

CONTAINER

###### A.35.18.3.1.3 Relationship Constraints

Relationships between Content Items in the content of this IOD shall be conveyed by-value. Table A.35.18-2 specifies the relationship constraints of this IOD. See Table C.17.3-8 for Relationship Type definitions.

Table A.35.18-2. Relationship Content Constraints for Patient Radiation Dose SR IOD

Source Value Type | Relationship Type (Enumerated Values) | Target Value Type
--- | --- | ---
CONTAINER | CONTAINS | TEXT, CODE, NUM, DATETIME, UIDREF, PNAME, IMAGE, COMPOSITE, CONTAINER
CONTAINER | HAS OBS CONTEXT | DATETIME, CODE, TEXT, UIDREF, PNAME
TEXT, CODE, NUM, COMPOSITE | HAS OBS CONTEXT | TEXT, CODE, NUM, DATETIME, UIDREF, PNAME, COMPOSITE
CONTAINER, IMAGE, COMPOSITE | HAS ACQ CONTEXT | TEXT, CODE, NUM, DATETIME, UIDREF, PNAME, CONTAINER
any type | HAS CONCEPT MOD | TEXT, CODE
TEXT, CODE, NUM, COMPOSITE | HAS PROPERTIES | TEXT, CODE, NUM, DATETIME, UIDREF, PNAME, IMAGE, COMPOSITE, CONTAINER
PNAME | HAS PROPERTIES | TEXT, CODE, DATETIME, UIDREF, PNAME
TEXT, CODE, NUM | INFERRED FROM | TEXT, CODE, NUM, DATETIME, UIDREF, IMAGE, COMPOSITE, CONTAINER

### Note

The SOP Classes to which an IMAGE or COMPOSITE Value Type may refer are documented in the Conformance Statement for an application (see PS3.2 and PS3.4).

Prev | Up | Next
A.35.18.2 Patient Radiation Dose SR IOD Entity-Relationship Model | Home | A.35.19 Planned Imaging Agent Administration SR IOD

DICOM PS3.3 2020b - Information Object Definitions