X.4 Simultaneous SR and CDA Instance Creation
Prev | X Dictation-based Reporting With Image References (Informative) | Next

## X.4 Simultaneous SR and CDA Instance Creation

The report may be created as both an SR instance and a CDA instance. In this case, the two instances are equivalent, and can cross-reference each other.

### X.4.1 Equivalence

The CDA Document shall contain clinical content equivalent to the SR Document.

### Note

The HL7 CDA standard specifically addresses transformation of documents from a non-CDA format. The requirement in the CDA specification is: "A proper transformation must ensure that the human readable clinical content of the report is not impacted."

There is no requirement that the transform or transcoding between DICOM SR and HL7 CDA be reversible. In particular, some attributes of the DICOM Patient, Study, and Series IEs have no corresponding standard encoding in the HL7 CDA Header, and vice versa. Such data elements, if transcoded, may need to be encoded in "local markup" (in HL7 CDA) or private data elements (in DICOM SR) in an implementation-dependent manner; and some such data elements may not be transcoded at all. It is a responsibility of the transforming application to ensure clinical equivalence.

Many attributes of the SR Document General Module can be transcoded to CDA Header participations or related acts.

### X.4.2 Document Cross-reference

Due to the inherent differences between DICOM SR and HL7 CDA, a transcoded document will have a different UID than the source document. However, the SR Document may reference the CDA Document as equivalent using the Equivalent CDA Document Sequence (0040,A090) attribute, and the CDA Document may reference the SR Document with a relatedDocument act relationship.

Since the ParentDocument target of the relatedDocument relationship is constrained to be a simple DOCCLIN act, it is recommended that the reference to the DICOM SR be encoded per Table X.3-4, without explicit identification of the Study and Series Instance UIDs, and with classCode DOCCLIN (rather than DGIMG).

### Note

1. The Study and Series Instance UIDs would be encoded in the WADO reference in the Act.Text ED data type.

2. CDA Release 1 does not provide a standard for the relatedDocument relationship to another document.

Prev | Up | Next
X.3 Transcribed Diagnostic Imaging CDA Instance Content | Home | Y VOI LUT Functions (Informative)