DICOM PS3.3 2016e - Information Object Definitions

A.35 Structured Report Document Information Object Definitions
Prev | A Composite Information Object Definitions (Normative) | Next

## A.35 Structured Report Document Information Object Definitions

### A.35.1 Basic Text SR IOD

#### A.35.1.1 Basic Text SR IOD Description

The Basic Text Structured Report (SR) IOD is intended for the representation of reports with minimal usage of coded entries (typically used in Document Title and headings) and a hierarchical tree of headings under which may appear text and subheadings. Reference to SOP Instances (e.g., images or waveforms or other SR Documents) is restricted to appear at the level of the leaves of this primarily textual tree. This structure simplifies the encoding of conventional textual reports as SR Documents, as well as their rendering.

#### A.35.1.2 Basic Text SR IOD Entity-Relationship Model

This IOD uses the E-R Model in Section A.1.2, with only the SR Document IE below the Series IE. The Frame of Reference IE is not a component of this IOD.

#### A.35.1.3 Basic Text SR IOD Module Table

Table A.35.1-1 specifies the Modules of the Basic Text SR IOD.

Table A.35.1-1. Basic Text 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
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.1.3.1 Basic Text SR IOD Content Constraints

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

DATETIME

DATE

TIME

UIDREF

PNAME

COMPOSITE

IMAGE

WAVEFORM

CONTAINER

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

Table A.35.1-2. Relationship Content Constraints for Basic Text SR IOD

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

### 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.34.10.4.6 Waveform Sample Interpretation | Home | A.35.2 Enhanced SR IOD

DICOM PS3.3 2016e - Information Object Definitions