6.1 Template Table field definition

SR Templates are described using tables of the following form:

TID #Template NameType: (Non-)Extensible Order: (Non-)Significant

NL Rel with Parent VT Concept Name VM Req Type Condition Value Set Constraint
1
2
3

Acquisition Context Templates are described using tables of the following form:

TID # Template NameType: (Non-)Extensible Order: (Non-)Significant

VT Concept Name VM Req Type Condition Value Set Constraint
1
2
3

Protocol Context Templates are described using tables of the following form:

TID # Template NameType: (Non-)Extensible Order: (Non-)Significant

NL VT Concept Name VM Req Type Condition Value Set Constraint
1
2
3

The semantics of the fields (columns) of Template tables are defined by subsections of this Section. A row of a Template table specifies either one Content Item or inclusion of another Template that may specify any number of Content Items (see Section 6.2.3 for definition of Included Templates). Each Template table is named by a title, identified by a TID number and further explained by a description such as explanation of Template contents, purpose and use cases.

The folllowing conventions are defined for the form of references to coded concepts, Context Groups and Templates.

Code Meanings are enclosed in quotation marks (for example “cm”). Code Values and Coding Scheme Designators are not enclosed in quotation marks unless a comma occurs in the string.

References to coded concepts take the following form:

EV or DT (CV, CSD, “CM”)

e.g. an Enumerated Value with only CV, CSD, and CM defined is represented as follows: EV (CV, CSD, “CM”), for example EV (T-04000, SNM3, “Breast”).

MemberOf { BCID or DCID (CID) CNAME } MemberOf selects one term from the specified context group.

If reference to a specific coding scheme version is required, it takes the following form:

EV or DT (CV, CSD [CSV] , “CM”)

e.g., DT (D3-81922, SRT [V1], “Aortic fistula”).

References to Context Groups take the following form:

BCID or DCID (CID) CNAME

e.g. Defined Context Group 5000 is represented as follows: DCID (5000) Language.

References to Templates take the following form:

BTID or DTID (TID) TNAME

e.g. Baseline Template 1000 is represented as follows: BTID (1000) Quotation.

6.1.1 Row Number

Each row of a Template Table is denoted by a row number. The first row is numbered 1 and subsequent rows are numbered in ascending order with increments of 1. This number denotes a row for convenient description as well as reference in conditions. The Row Number of a Content Item in a Template may or may not be the same as the ordinal position of the corresponding Sequence Item (representing the Content Item) in a Content Sequence (0040,A730), depending on the number of times the Content Item is repeated.

The Content Item specified in the first row of a Template table may be of any Value Type. Specifically, it is not constrained to be a CONTAINER.

6.1.2 Nesting Level (NL)

The nesting level of Content Items is denoted by “>” symbols, one per level of nesting below the initial Source Content Item (of the Template) in a manner similar to the depiction of nested Sequences of Items in Modules Tables in PS 3.3. When it is necessary to specify the Target Content Item(s) of a relationship, they are specified in the row(s) immediately following the corresponding Source Content Item. The Nesting Level of a Target Content Item is one greater than the Nesting Level of the corresponding (parent) Source Content Item. The Content Item specified in row 1 of a Template Table is at the top level (i.e. no “>” symbol is ever present in the NL field for the first Content Item in the table).

Acquisition context templates have no Nesting Level field. Protocol Context templates allow a single Nesting Level implemented through the Content Item Modifier Sequence (see PS3.3).

6.1.3 Relationship with Source Content Item (Parent)

Relationship Type and Relationship Mode (i.e. By-value or By-reference) constraints, if defined, are specified in this field, as described in Table 6.1.3-1.

Relationship Type and Mode are specified for each row that specifies a target content item.

Relationship Type and Mode may also be specified when another Template is included, either “top-down” or “bottom-up” or both (i.e. in the “INCLUDE Template” row of the calling Template, or in all rows of the included Template, or in both places). There shall be no conflict between the Relationship Type and Mode of a row that includes another Template and the Relationship Type and Mode of the rows of the included Template.

Note: SR IODs specify Enumerated Values for Relationship Types. If a Relationship Type other than one of the Defined Terms for Relationship Type (0040,A010) is specified in a Private SOP Class, there is a significant risk to interoperability. Documentation accompanying Templates for Private SOP Classes should define any Relationship-type extensions in the manner that the Standard Relationship Types are defined in PS 3.3.

Acquisition context and Protocol Context templates have no Relationship field.

Table 6.1.3-1Syntax of Relationship Constraints

Expression Definition
RTYPE Relationship Mode is By-value and Relationship Type is RTYPE. For example, “INFERRED FROM”.
R-RTYPE Relationship Mode is By-reference and Relationship Type is RTYPE. For example, “R-INFERRED FROM”.

6.1.4 Value Type (VT)

The Value Type field specifies the SR Value Type of the Content Item or conveys the word “INCLUDE” to indicate that another Template is to be included (substituted for the row). See Section 6.2.3 for further description of “Included Templates”.

6.1.5 Concept Name

Any constraints on Concept Name are specified in this field as defined or enumerated coded entries, or as baseline or defined context groups. Alternatively, when the VT field is “INCLUDE”, the Concept Name field specifies the template to be included.

6.1.6 Value Multiplicity (VM)

The VM field indicates the number of times that either a Content Item of the specified pattern or an included Template may appear in this position. Table 6.1.6-1 specifies the values that are permitted in this field.

Table 6.1.6-1Permitted Values for VM

Expression Definition
i (where ‘i’ represents an integer) Exactly i occurrences, where i>=1. E.g. when i=1 there shall be one occurrence of the Content Item in this position.
i-j From i to j occurrences, where i and j are >=1 and j>i.
1-n One or more occurrences

6.1.7 Requirement Type

The Requirement Type field specifies the requirements on the presence or absence of the Content Item or included Template.

Note: There is typically no need to specify Requirement Type separately for SCU and SCP of the Basic SR SOP Classes, because the SCP is required to support the entire content of any SR Document it receives. Therefore, for Basic SR SOP Classes, Requirement Type effectively only applies to the SCU.

The following symbols are used:

M – Mandatory. Shall be present.

MC – Mandatory Conditional. Shall be present if the specified condition is satisfied.

U – User Option. May or may not be present.

UC – User Option Conditional. May not be present. May be present according to the specified condition.

Note: There is an interaction between the VM and the Requirement Type with respect to the number of times that a content item (or included Template) may actually be present, as follows:

Req Type VM Actual number of occurences in the content tree

M 1 1

M 1-n 1 to n

U 1 0 or 1

U 1-n 0 to n

6.1.8 Condition

The Condition field specifies any conditions upon which presence or absence of the Content Item or its values depends. This field specifies any Concept Name(s) or Values upon which there are dependencies.

References in Condition statements to coded concepts or values, whether to select a content item to test or to specify a value to test against, are of the form (CV, CSD, “CM”). As is always the case for coded entries, the matching is performed against CV and CSD, irrespective of the string value of CM.

References may also be made to row numbers (e.g. to specify exclusive OR conditions that span multiple rows of a Template table) .

The following abbreviations are used:

XOR = Exclusive OR. One and only one row shall be selected from mutually-exclusive options.

Note: For example, if one of rows 1, 2, 3 or 4 may be included, then for row 2, the abbreviation “XOR rows 1,3,4” is specified for the condition.

IF = Shall be present if the condition is TRUE; may be present otherwise.

IFF = If and only if . Shall be present if the condition is TRUE; shall not be present otherwise.

6.1.9 Value Set Constraint

Value Set Constraints, if any, are specified in this field as defined or enumerated coded entries, or as baseline or defined context groups.

The Value Set Constraint column may specify a default value for the Content Item if the Content Item is not present, either as a fixed value, or by reference to another Content Item, or by reference to an Attribute from the dataset other than within the Content Sequence (0040,A730).

6.1.9.1 NUM Units Constraint

Constraints on units of measurement, if any, are specified in the Value Set Constraint field if and only if the Value Type is NUM. The constraints are specified either as defined or enumerated coded entries, or as baseline or defined context groups.

6.1.9.2 CONTAINER Continuation Flag Constraint

The value of the Continuity of Content Flag (0040,A050) may be specified in the Value Set Constraint field if and only if the Value Type is CONTAINER.

Note: The SR Document Content Module specifies “SEPARATE” and “CONTINUOUS” as the Enumerated Values for Continuity of Content Flag (0040,A050).

6.1.9.3 SCOORD Graphic Type Constraint

Constraints on the value of the Graphic Type (0070,0023) may be specified in the Value Set Constraint field if and only if the Value Type is SCOORD. The constraint may specify a set of allowed values, or a set of disallowed values. For example:

GRAPHIC TYPE = {POINT}

GRAPHIC TYPE = {CIRCLE, ELLIPSE}

GRAPHIC TYPE = not {MULTIPOINT}