DICOM PS3.3 2018a - Information Object Definitions

A.35.12.3 Implantation Plan SR Document IOD Module Table
Prev | A.35.12 Implantation Plan SR Document IOD | Next

#### A.35.12.3 Implantation Plan SR Document IOD Module Table

Table A.35.12-1 specifies the Modules of the Implantation Plan SR Document IOD.

Table A.35.12-1. Implantation Plan SR 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 | SR Document Series | C.17.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
Document | SR Document General | C.17.2 | M
SR Document Content | C.17.3 | M
SOP Common | C.12.1 | M

##### A.35.12.3.1 Implantation Plan SR Document IOD Content Constraints

###### A.35.12.3.1.1 Template Constraints

The document shall be constructed from TID 7000 “Implantation Plan” invoked at the root node.

### Note

All Template and Context Group definitions are located in Annex A “Structured Reporting Templates (Normative)” in PS3.16 and Annex B “DCMR Context Groups (Normative)” in PS3.16, respectively.

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

DATE

UIDREF

PNAME

COMPOSITE

IMAGE

CONTAINER

###### A.35.12.3.1.3 Relationship Constraints

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

Table A.35.12-2. Relationship Content Constraints for Implantation Plan SR Document IOD

Source Value Type | Relationship Type (Enumerated Values) | Target Value Type
--- | --- | ---
CONTAINER | CONTAINS | TEXT, CODE, NUM, UIDREF, COMPOSITE1, IMAGE1, CONTAINER
CONTAINER | HAS OBS CONTEXT | TEXT, CODE, NUM, DATE, UIDREF, PNAME, COMPOSITE1
any type | HAS CONCEPT MOD | TEXT, CODE2
TEXT, CODE, NUM, IMAGE, UIDREF, COMPOSITE | HAS PROPERTIES | TEXT, CODE, NUM, UIDREF, IMAGE1, COMPOSITE1

### Note

1. Which SOP Classes the IMAGE 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.12.2 Implantation Plan SR Document IOD Entity-Relationship Model | Home | A.35.13 Comprehensive 3D SR IOD

DICOM PS3.3 2018a - Information Object Definitions