C.17.2 SR Document General Module
Prev | C.17 SR Document Modules | Next

### C.17.2 SR Document General Module

Table C.17-2 defines the general Attributes of an SR Document Instance. These Attributes identify the SR Document and provide context for the entire document.

Table C.17-2. SR Document General Module Attributes

Attribute Name | Tag | Type | Attribute Description
--- | --- | --- | ---
Instance Number | (0020,0013) | 1 | A number that identifies the SR Document.
Preliminary Flag | (0040,A496) | 3 | Indicates whether this SR Document is intended to be regarded as a preliminary or final report. Enumerated Values: PRELIMINARY This report precedes the final report and may contain limited information; it may be time sensitive, and it is not expected to contain all the reportable findings. FINAL This report is the definitive means of communicating the results of a procedure. ### Note The definitions of the Enumerated Values are derived from the ACR Practice Guideline for Communication of Diagnostic Imaging Findings, Revised 2005.
Completion Flag | (0040,A491) | 1 | The estimated degree of completeness of this SR Document. See Section C.17.2.7. Enumerated Values: PARTIAL Partial content. COMPLETE Complete content.
Completion Flag Description | (0040,A492) | 3 | Explanation of the value sent in Completion Flag (0040,A491).
Verification Flag | (0040,A493) | 1 | Indicates whether this SR Document is Verified. Enumerated Values: UNVERIFIED Not attested to. VERIFIED Attested to by a Verifying Observer Name (0040,A075) who is accountable for its content. A value of "VERIFIED" shall be used only when the value of Completion Flag (0040,A491) is "COMPLETE". ### Note The intent of this specification is that the "prevailing final version" of an SR Document is the version having the most recent Verification DateTime (0040,A030), Verification Flag (0040,A493) of VERIFIED and Preliminary Flag (0040,A496) of FINAL.
Content Date | (0008,0023) | 1 | The date the document content creation started.
Content Time | (0008,0033) | 1 | The time the document content creation started.
Verifying Observer Sequence | (0040,A073) | 1C | The person or persons authorized to verify documents of this type and accept responsibility for the content of this document. One or more Items shall be included in this sequence. Required if Verification Flag (0040,A493) is VERIFIED. ### Note In HL7 Structured Documents, the comparable attribute is the "legalAuthenticator".
>Verifying Observer Name | (0040,A075) | 1 | The person authorized by the Verifying Organization (0040,A027) to verify documents of this type and who accepts responsibility for the content of this document.
>Verifying Observer Identification Code Sequence | (0040,A088) | 2 | Coded identifier of Verifying Observer. Zero or one Item shall be included in this sequence.
>>Include Table 8.8-1 “Code Sequence Macro Attributes” | No Baseline CID is defined.
>Verifying Organization | (0040,A027) | 1 | Organization to which the Verifying Observer Name (0040,A075) is accountable in the current interpretation procedure.
>Verification DateTime | (0040,A030) | 1 | Date and Time of verification by the Verifying Observer Name (0040,A075).
Author Observer Sequence | (0040,A078) | 3 | The person or device that created the clinical content of this document. This attribute sets the default Observer Context for the root of the content tree. One or more Items are permitted in this sequence.
>Include Table C.17-3b “Identified Person or Device Macro Attributes” |
Participant Sequence | (0040,A07A) | 3 | Persons or devices related to the clinical content of this document. One or more Items are permitted in this sequence.
>Participation Type | (0040,A080) | 1 | Participant's role with respect to the clinical content of this document. See Section C.17.2.5. Defined Terms: SOURCE Equipment that contributed to the content ENT Data enterer (e.g., transcriptionist) ATTEST Attestor ### Note In HL7 Structured Documents, the participation comparable to Attestor is the "Authenticator".
>Participation DateTime | (0040,A082) | 2 | DateTime of participation with respect to the clinical content of this document.
>Include Table C.17-3b “Identified Person or Device Macro Attributes” |
Custodial Organization Sequence | (0040,A07C) | 3 | Custodial organization for this SR Document instance. Represents the organization from which the document originates and that is in charge of maintaining the document, i.e., the steward of the original source document. ### Note This may or may not be identical to the Institution identified in the Equipment Module. Only a single item is permitted in this sequence.
>Institution Name | (0008,0080) | 2 | Name of Custodial Institution or Organization.
>Institution Code Sequence | (0008,0082) | 2 | Coded identifier of Custodial Institution or Organization. Zero or one Item shall be included in this sequence.
>>Include Table 8.8-1 “Code Sequence Macro Attributes” | No Baseline CID is defined.
Predecessor Documents Sequence | (0040,A360) | 1C | Shall refer to SR SOP Instances (e.g., prior or preliminary reports) whose content has been wholly or partially included in this document with or without modification. One or more Items shall be included in this sequence. Required if this document includes content from other documents. ### Note The amendment process of an existing SR Document may be described using the Purpose of Reference Code Sequence.
>Include Table C.17-3 “Hierarchical SOP Instance Reference Macro Attributes” | Defined CID for the Purpose of Reference Code Sequence in the Hierarchical SOP Instance Reference Macro is CID 7009 “Purpose of Reference to Predecessor Report”.
Identical Documents Sequence | (0040,A525) | 1C | Duplicates of this document, stored with different SOP Instance UIDs. One or more Items shall be included in this sequence. Required if this document is stored with different SOP Instance UIDs in one or more other Studies. See Section C.17.2.2 for further explanation.
>Include Table C.17-3 “Hierarchical SOP Instance Reference Macro Attributes” |
Referenced Request Sequence | (0040,A370) | 1C | Identifies Requested Procedures that are being fulfilled (completely or partially) by creation of this Document. One or more Items shall be included in this sequence. Required if this Document fulfills at least one Requested Procedure. May be present otherwise.
>Study Instance UID | (0020,000D) | 1 | Unique identifier for the Study.
>Referenced Study Sequence | (0008,1110) | 2 | Uniquely identifies the Study SOP Instance. Zero or one Item shall be included in this sequence. See Section 10.6.1.
>>Include Table 10-11 “SOP Instance Reference Macro Attributes” |
>Accession Number | (0008,0050) | 2 | A departmental IS generated number that identifies the order for the Study.
>Issuer of Accession Number Sequence | (0008,0051) | 3 | Identifier of the Assigning Authority that issued the Accession Number. Only a single Item is permitted in this sequence.
>>Include Table 10-17 “HL7v2 Hierarchic Designator Macro Attributes” |
>Placer Order Number/Imaging Service Request | (0040,2016) | 2 | The order number assigned to the Imaging Service Request by the party placing the order.
>Order Placer Identifier Sequence | (0040,0026) | 3 | Identifier of the Assigning Authority that issued the Placer Order Number. Only a single Item is permitted in this sequence.
>>Include Table 10-17 “HL7v2 Hierarchic Designator Macro Attributes” |
>Filler Order Number/Imaging Service Request | (0040,2017) | 2 | The order number assigned to the Imaging Service Request by the party filling the order.
>Order Filler Identifier Sequence | (0040,0027) | 3 | Identifier of the Assigning Authority that issued the Filler Order Number. Only a single Item is permitted in this sequence.
>>Include Table 10-17 “HL7v2 Hierarchic Designator Macro Attributes” |
>Requested Procedure ID | (0040,1001) | 2 | Identifier of the related Requested Procedure
>Requested Procedure Description | (0032,1060) | 2 | Institution-generated administrative description or classification of Requested Procedure.
>Requested Procedure Code Sequence | (0032,1064) | 2 | A sequence that conveys the requested procedure. Zero or one Item shall be included in this sequence.
>>Include Table 8.8-1 “Code Sequence Macro Attributes” | No Baseline CID is defined.
>Reason for the Requested Procedure | (0040,1002) | 3 | Reason for requesting this procedure.
>Reason for Requested Procedure Code Sequence | (0040,100A) | 3 | Coded Reason for requesting this procedure. One or more Items are permitted in this sequence.
>>Include Table 8.8-1 “Code Sequence Macro Attributes” | No Baseline CID is defined.
Performed Procedure Code Sequence | (0040,A372) | 2 | A Sequence that conveys the codes of the performed procedures pertaining to this SOP Instance. Zero or more Items shall be included in this sequence.
>Include Table 8.8-1 “Code Sequence Macro Attributes” | No Baseline CID is defined.
Current Requested Procedure Evidence Sequence | (0040,A375) | 1C | Full set of Composite SOP Instances, of which the creator is aware, which were created to satisfy the current Requested Procedure(s) for which this SR Document is generated or that are referenced in the content tree. One or more Items shall be included in this sequence. Required if the creator is aware of Composite Objects acquired in order to satisfy the Requested Procedure(s) for which the SR Document is or if instances are referenced in the content tree. May be present otherwise. See Section C.17.2.3 for further explanation.
>Include Table C.17-3 “Hierarchical SOP Instance Reference Macro Attributes” |
Pertinent Other Evidence Sequence | (0040,A385) | 1C | Other Composite SOP Instances that are considered to be pertinent evidence by the creator of this SR Document. This evidence must have been acquired in order to satisfy Requested Procedures other than the one(s) for which this SR Document is generated. One or more Items shall be included in this sequence. Required if pertinent evidence from other Requested Procedures needs to be recorded. See Section C.17.2.3 for further explanation.
>Include Table C.17-3 “Hierarchical SOP Instance Reference Macro Attributes” |
Referenced Instance Sequence | (0008,114A) | 1C | Sequence specifying SOP Instances significantly related to the current SOP Instance. Such referenced Instances may include equivalent documents or renderings of this document. One or more Items shall be included in this sequence. Required if the identity of a CDA Document equivalent to the current SOP Instance is known at the time of creation of this SOP Instance (see Section C.17.2.6). May be present otherwise.
>Include Table 10-11 “SOP Instance Reference Macro Attributes” |
>Purpose of Reference Code Sequence | (0040,A170) | 1 | Code describing the purpose of the reference to the Instance(s). Only a single Item shall be included in this sequence.
>>Include Table 8.8-1 “Code Sequence Macro Attributes” | Defined CID 7006 “SR Document Purposes of Reference”.

#### C.17.2.1 Hierarchical SOP Instance Reference Macro

Table C.17-3 specifies the Attributes that reference a list of SOP Instances.

Table C.17-3. Hierarchical SOP Instance Reference Macro Attributes

Attribute Name | Tag | Type | Attribute Description
--- | --- | --- | ---
Study Instance UID | (0020,000D) | 1 | Unique identifier for the Study
Referenced Series Sequence | (0008,1115) | 1 | Sequence of Items where each Item includes the Attributes of a Series containing referenced Composite Object(s). One or more Items shall be included in this sequence
>Include Table C.17-3a “Hierarchical Series Reference Macro Attributes” |

Table C.17-3a specifies the Attributes that reference a Series of SOP Instances.

Table C.17-3a. Hierarchical Series Reference Macro Attributes

Attribute Name | Tag | Type | Attribute Description
--- | --- | --- | ---
Series Instance UID | (0020,000E) | 1 | Unique identifier of a Series that is part of this Study and contains the referenced Composite Object(s).
Retrieve AE Title | (0008,0054) | 3 | Title of the DICOM Application Entity where the Composite Object(s) may be retrieved on the network.
Retrieve Location UID | (0040,E011) | 3 | Unique identifier of the system where the Composite Object(s) may be retrieved on the network.
Retrieve URL | (0008,1190) | 3 | URI/URL specifying the location of the referenced instance(s).
Storage Media File-Set ID | (0088,0130) | 3 | The user or implementation specific human readable identifier that identifies the Storage Media on which the Composite Object (s) reside.
Storage Media File-Set UID | (0088,0140) | 3 | Uniquely identifies the Storage Media on which the Composite Object(s) reside.
Referenced SOP Sequence | (0008,1199) | 1 | References to Composite Object SOP Class/SOP Instance pairs that are part of the Study defined by Study Instance UID and the Series defined by Series Instance UID (0020,000E). One or more Items shall be included in this sequence.
>Include Table 10-11 “SOP Instance Reference Macro Attributes” |
>Purpose of Reference Code Sequence | (0040,A170) | 3 | Describes the purpose for which the reference is made. One or more Items are permitted in this sequence.
>>Include Table 8.8-1 “Code Sequence Macro Attributes” | Baseline CID may be specified in Macro invocation.
>Referenced Digital Signature Sequence | (0400,0402) | 3 | Sequence of references to Digital Signatures in the referenced SOP Instance. One or more Items are permitted in this sequence. ### Note The Attributes in this sequence can be used to detect if the referenced SOP Instance has been altered.
>>Digital Signature UID | (0400,0100) | 1 | The Unique Identifier of a Digital Signature held in the referenced SOP Instance.
>>Signature | (0400,0120) | 1 | The Signature Value identified by the Digital Signature UID within the Referenced SOP Instance UID.
>Referenced SOP Instance MAC Sequence | (0400,0403) | 3 | A MAC Calculation from data in the referenced SOP Instance that can be used as a data integrity check. Only a single Item is permitted in this Sequence. ### Note This Attribute may be used in place of Referenced Digital Signature Sequence (0400,0402), particularly if the SOP Instance does not have appropriate Digital Signatures that can be referenced.
>>MAC Calculation Transfer Syntax UID | (0400,0010) | 1 | The Transfer Syntax UID used to encode the values of the Data Elements included in the MAC calculation. When computing the MAC, only Transfer Syntaxes that explicitly include the VR and use Little Endian encoding shall be used. ### Note Certain Transfer Syntaxes, particularly those that are used with compressed data, allow the fragmentation of the pixel data to change. If such fragmentation changes, Digital Signatures generated with such Transfer Syntaxes could become invalid. This does not constrain the transfer syntax used to transmit the object.
>>MAC Algorithm | (0400,0015) | 1 | The algorithm used in generating the MAC. Defined Terms: RIPEMD160 MD5 SHA1 SHA256 SHA384 SHA512 ### Note Digital Signature Security Profiles (see PS3.15) may require the use of a restricted subset of these terms.
>>Data Elements Signed | (0400,0020) | 1 | A list of Data Element Tags in the order they appear at the top level of the referenced SOP Instance that identify the Data Elements used in creating the MAC. See Section C.12.1.1.3.1.1.
>>MAC | (0400,0404) | 1 | The MAC generated as described in Section C.12.1.1.3, but unencrypted and without inclusion of fields from the Digital Signatures Sequence. See Section C.12.1.1.3.1.2.

Prev | Up | Next
C.17 SR Document Modules | Home | C.17.2.2 Identical Documents Sequence