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.
The E-R Model in Section A.1.2 of this Part applies to the Basic Text SR IOD. The Frame of Reference IE, and the IEs at the level of the Image IE in Section A.1.2 are not components of the Basic Text SR IOD. Table A.35.1-1 specifies the Modules of the Basic Text SR IOD.
Table A.35.1-1 specifies the Modules of the Basic Text SR IOD.
Table A.35.1-1BASIC TEXT SR IOD MODULES
|Clinical Trial Subject||C.7.1.3||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|
|Document||SR Document General||C.17.2||M|
|SR Document Content||C.17.3||M|
Note: The Specimen Identification Module was previously included in this IOD but has been retired. See PS 3.3-2008.
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):
PNAME COMPOSITE IMAGE WAVEFORM CONTAINER
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-2RELATIONSHIP 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 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.