DICOM PS3.3 2020b - Information Object Definitions

A.35.2.3 Enhanced SR IOD Module Table (Current)
Prev | A.35.2 Enhanced SR IOD | Next

#### A.35.2.3 Enhanced SR IOD Module Table

Table A.35.2-1 specifies the Modules of the Enhanced SR IOD.

Table A.35.2-1. Enhanced 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 | U
Equipment | General Equipment | C.7.5.1 | M
Document | SR Document General | C.17.2 | M
SR Document Content | C.17.3 | M
SOP Common | C.12.1 | M

### Note

The Specimen Identification Module was previously included in this IOD but has been retired. See PS3.3-2008.

##### A.35.2.3.1 Enhanced SR IOD Content Constraints

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

NUM

DATETIME

DATE

TIME

UIDREF

PNAME

SCOORD

TCOORD

COMPOSITE

IMAGE

WAVEFORM

CONTAINER

###### A.35.2.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 Relationship 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.2-2 specifies the relationship constraints of this IOD.

Table A.35.2-2. Relationship Content Constraints for Enhanced SR IOD

Source Value Type | Relationship Type (Enumerated Values) | Target Value Type
--- | --- | ---
CONTAINER | CONTAINS | TEXT, CODE, NUM, DATETIME, DATE, TIME, UIDREF, PNAME, SCOORD, TCOORD, COMPOSITE1, IMAGE1, WAVEFORM1, CONTAINER
CONTAINER | HAS OBS CONTEXT | TEXT, CODE, NUM, DATETIME, DATE, TIME, UIDREF, PNAME, COMPOSITE1
CONTAINER, IMAGE1, WAVEFORM1, COMPOSITE1, NUM | HAS ACQ CONTEXT | TEXT, CODE, NUM, DATETIME, DATE, TIME, UIDREF, PNAME
any type | HAS CONCEPT MOD | TEXT, CODE2
TEXT, CODE, NUM | HAS PROPERTIES | TEXT, CODE, NUM, DATETIME, DATE, TIME, UIDREF, PNAME, IMAGE1, WAVEFORM1, COMPOSITE1, SCOORD, TCOORD
PNAME | HAS PROPERTIES | TEXT, CODE, DATETIME, DATE, TIME, UIDREF, PNAME
TEXT, CODE, NUM | INFERRED FROM | TEXT, CODE, NUM, DATETIME, DATE, TIME, UIDREF, PNAME, IMAGE1, WAVEFORM1, COMPOSITE1, SCOORD, TCOORD
SCOORD | SELECTED FROM | IMAGE1
TCOORD | SELECTED FROM | SCOORD, IMAGE1, WAVEFORM1

### Note

1. Which SOP Classes the IMAGE, WAVEFORM or COMPOSITE Value Type may refer to, 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 Source Content Item, for example to provide a more descriptive explanation, a different language translation, or to define a post-coordinated concept.

Prev | Up | Next
A.35.2.2 Enhanced SR IOD Entity-Relationship Model | Home | A.35.3 Comprehensive SR IOD

DICOM PS3.3 2020b - Information Object Definitions