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 SR Document Root invoked at the root node.

Note: All Template and Context Group definitions are located in PS 3.16, DICOM Content Mapping Resource, in the Annexes titled DCMR Templates and DCMR Context Groups, respectively.

A.35.12.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):

TEXT

CODE

NUM

UIDREF

COMPOSITE

IMAGE

CONTAINER

DATE

PNAME

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

Notes: 1. Which SOP Classes the IMAGE or COMPOSITE Value Type may refer to is documented in the Conformance Statement for an application (see PS 3.2 and PS 3.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.