C.17.3 SR Document Content Module
Prev | C.17 SR Document Modules | Next

### C.17.3 SR Document Content Module

This section specifies the Attributes contained in the SR Document Content Module. The Attributes in this Module convey the content of an SR Document.

Table C.17-4. SR Document Content Module Attributes

Attribute Name | Tag | Type | Attribute Description
--- | --- | --- | ---
Include Table C.17-5 “Document Content Macro Attributes” | With a Value Type (0040,A040) of CONTAINER
Include Table C.17-6 “Document Relationship Macro Attributes” |

Table C.17-5. Document Content Macro Attributes

Attribute Name | Tag | Type | Attribute Description
--- | --- | --- | ---
Value Type | (0040,A040) | 1 | The type of the value encoded in this Content Item. Defined Terms: TEXT NUM CODE DATE TIME DATETIME UIDREF PNAME COMPOSITE IMAGE WAVEFORM SCOORD SCOORD3D TCOORD CONTAINER See Section C.17.3.2.1 for further explanation.
Concept Name Code Sequence | (0040,A043) | 1C | Code describing the concept represented by this Content Item. Also conveys the value of Document Title and section headings in documents. Only a single Item shall be included in this sequence. Required if Value Type (0040,A040) is TEXT, NUM, CODE, DATETIME, DATE, TIME, UIDREF or PNAME. Required if Value Type (0040,A040) is CONTAINER and a heading is present, or this is the Root Content Item. ### Note That is, containers without headings do not require Concept Name Code Sequence Required if Value Type (0040,A040) is COMPOSITE, IMAGE, WAVEFORM, SCOORD, SCOORD3D or TCOORD, and the Purpose of Reference is conveyed in the Concept Name. See Section C.17.3.2.2 for further explanation.
>Include Table 8.8-1 “Code Sequence Macro Attributes” | No Baseline CID is defined.
Text Value | (0040,A160) | 1C | This is the value of the Content Item. Required if Value Type (0040,A040) is TEXT. Text data that is unformatted and whose manner of display is implementation dependent. The text value may contain spaces, as well as multiple lines separated by CR LF, but otherwise no format control characters (such as horizontal or vertical tab and form feed) shall be present, even if permitted by the Value Representation of UT. The text shall be interpreted as specified by Specific Character Set (0008,0005) if present in the SOP Common Module. ### Note The text may contain single or multi-byte characters and use code extension techniques as described in PS3.5 if permitted by the values of Specific Character Set (0008,0005).
DateTime | (0040,A120) | 1C | This is the value of the Content Item. Required if Value Type (0040,A040) is DATETIME.
Date | (0040,A121) | 1C | This is the value of the Content Item. Required if Value Type (0040,A040) is DATE.
Time | (0040,A122) | 1C | This is the value of the Content Item. Required if Value Type (0040,A040) is TIME.
Person Name | (0040,A123) | 1C | This is the value of the Content Item. Required if Value Type (0040,A040) is PNAME.
UID | (0040,A124) | 1C | This is the value of the Content Item. Required if Value Type (0040,A040) is UIDREF.
Include Table C.18.1-1 “Numeric Measurement Macro Attributes” if and only if Value Type (0040,A040) is NUM. |
Include Table C.18.2-1 “Code Macro Attributes” if and only if Value Type (0040,A040) is CODE. |
Include Table C.18.3-1 “Composite Object Reference Macro Attributes” if and only if Value Type (0040,A040) is COMPOSITE. |
Include Table C.18.4-1 “Image Reference Macro Attributes” if and only if Value Type (0040,A040) is IMAGE. |
Include Table C.18.5-1 “Waveform Reference Macro Attributes” if and only if Value Type (0040,A040) is WAVEFORM. |
Include Table C.18.6-1 “Spatial Coordinates Macro Attributes” if and only if Value Type (0040,A040) is SCOORD. |
Include Table C.18.9-1 “3D Spatial Coordinates Macro Attributes” if and only if Value Type (0040,A040) is SCOORD3D. |
Include Table C.18.7-1 “Temporal Coordinates Macro Attributes” if and only if Value Type (0040,A040) is TCOORD. |
Include Table C.18.8-1 “Container Macro Attributes” if and only if Value Type (0040,A040) is CONTAINER. |

Table C.17-6. Document Relationship Macro Attributes

Attribute Name | Tag | Type | Attribute Description
--- | --- | --- | ---
Observation DateTime | (0040,A032) | 1C | The date and time on which this Content Item was completed. For the purpose of recording measurements or logging events, completion time is defined as the time of data acquisition of the measurement, or the time of occurrence of the event. Required if the date and time are different from Content Date (0008,0023) and Content Time (0008,0033) or Observation DateTime (0040,A032) defined in higher items. May be present otherwise. ### Note When Content Items are copied into successor reports, Content Date (0008,0023) and Content Time (0008,0033) of the new report are likely to be different than the date and time of the original observation. Therefore this attribute may need to be included in any copied Content Items to satisfy the condition.
Observation UID | (0040,A171) | 3 | Unique identifier for the observation Content Item (and its subsidiary Content Items, if any). The UID represents the semantic content of the observation; an encoding of the same observation with the same context into another representation (e.g., a CDA Entry) may use the same UID.
Content Sequence | (0040,A730) | 1C | A potentially recursively nested Sequence of Items that conveys content that is the Target of Relationships with the enclosing Source Content Item. One or more Items shall be included in this sequence. Required if the enclosing Content Item has relationships. ### Note If this Attribute is not present then the enclosing Item is a leaf. The order of Items within this Sequence is semantically significant for presentation. See Section C.17.3.2.4 for further explanation.
>Relationship Type | (0040,A010) | 1 | The type of relationship between the (enclosing) Source Content Item and the Target Content Item. IODs specify additional constraints on Relationships (including lists of Enumerated Values). Defined Terms: CONTAINS HAS PROPERTIES HAS OBS CONTEXT HAS ACQ CONTEXT INFERRED FROM SELECTED FROM HAS CONCEPT MOD See Section C.17.3.2.4 for further explanation.
>Include Table C.17-6 “Document Relationship Macro Attributes” if the Target Content Item is included by-value in the Source Content Item. The Macro shall not be present if the relationship is by-reference. |
>Include Table C.17-5 “Document Content Macro Attributes” if the Target Content Item is included by-value in the Source Content Item. The Macro shall not be present if the relationship is by-reference. |
>Referenced Content Item Identifier | (0040,DB73) | 1C | An ordered set of one or more integers that uniquely identifies the Target Content Item of the relationship. The root Content Item is referenced by a single value of 1. Each subsequent integer represents an ordinal position of a Content Item in the Content Sequence (0040,A730) in which it belongs. The Referenced Content Item Identifier is the set of these ordinal positions along the by-value relationship path. The number of values in this Multi-Value Attribute is exactly the number of relationships traversed in the SR content tree plus one. ### Note See Section C.17.3.2.5. Content Items are ordered in a Content Sequence starting from 1 as defined in VR of SQ (see PS3.5). Required if the Target Content Item is denoted by-reference, i.e., the Document Relationship Macro and Document Content Macro are not included.

#### C.17.3.1 SR Document Content Tree

The Module consists of a single root Content Item that is the root of the SR Document tree. The root Content Item is of type CONTAINER, and its Content Sequence conveys either directly or indirectly through further nested Content Sequences, all of the other Content Items in the document. This root Content Item shall have a heading in the Concept Name Code Sequence (0040,A043) that conveys the title of the SR Document, i.e., the Document Title.

Figure C.17.3-1 depicts the relationship of SR Documents to Content Items and the relationships of Content Items to other Content Items and to Observation Context.

Figure C.17.3-1. SR Information Model

### Note

Whether or not relationships by-reference are allowed to ancestor Content Items, is specified in the IOD.

Figure C.17.3-2. Example of an SR Content Tree (Informative)

Prev | Up | Next
C.17.2.7 Completion Flag | Home | C.17.3.2 Content Item Attributes