Images are referenced using hypertext links in the narrative text. These links in CDA are not considered part of the attested content.
Notes: 1. The primary use case for this Annex is the dictation/transcription reporting model. In the historical context of that model, the images (film sheets) are usually not considered part of the attested content of the report, although they are part of the complete exam record. I.e., the report is clinically complete without the images, and the referenced images are not formally part of the report. Therefore, this Annex discusses only the use of image references, not images embedded in the report.
2. Being part of the attested content would require the images to be displayed every time the report is displayed – i.e., they are integral to understanding the report. If the images are attested, they must also be encapsulated with the CDA package. I.e., the CDA document itself is only one part of the interchanged package; the referenced images must also always be sent with the CDA document. If the images are for reference only and not attested, the Image Content Item may be transformed to a simple hypertext link; it is then the responsibility of CDA document receiver to follow or not follow the hyperlink. Moreover, as the industry moves toward ubiquitous network access to a distributed electronic healthcare record, there will be less need to prepackage the referenced images with the report.
In the current use case, there will be one or more KO instances with image references. Each KO instance can be transformed to a Section in the CDA document with a Section.Title “Key Images”, and a Section.Code of 121180 from the DICOM Controlled Terminology (see PS3.16). If the KO includes a TEXT content item, it can be transformed to <paragraph> data in that Section.Text of the CDA document. Each IMAGE content item can be transformed to a link item using the <linkHtml> markup.
Within the <linkHtml> markup, the value of the href attribute is the DICOM object reference as a Web Access to Persistent DICOM Objects (WADO) specified URI (see Table X.3-1).
Notes: 1. When a DICOM object reference is included in an HL7 CDA document, it is presumed the recipient would not be a DICOM application; it would have access only to general Internet network protocols (and not the DICOM upper layer protocol), and would not be configured with the means to display a native DICOM image. Therefore, the recommended encoding of a DICOM Object Reference in the CDA narrative block <linkHtml> uses WADO for access by the HTTP/HTTPS network protocol (see PS3.18), using one of the formats broadly supported in Web browsers (image/jpeg or video/mpeg) as the requested content type.
2. In CDA Release 1, the markup tag for hyperlinks is <link_html> within the scope of a <link> tag.
Table X.3-1 WADO Reference in an HL7 CDA <linkHtml>
|<scheme>://<authority>/<path>||Configuration setting, used by the conversion process, identifying the WADO server|
|&studyUID=<uid>||Study Instance UID for referenced image obtained from the Current Requested Procedure Evidence Sequence or the Pertinent Other Evidence Sequence in the KO Instance|
|&seriesUID=<uid>||Series Instance UID for referenced image obtained from the Current Requested Procedure Evidence Sequence or the Pertinent Other Evidence Sequence in the KO Instance|
|&objectUID=<uid>||Referenced SOP Instance UID from IMAGE content item|
|&frameNumber=<list>||Referenced Frame Number from IMAGE content item (if present)|
|&presentationUID=<uid>||Referenced SOP Instance UID from Referenced SOP Sequence within IMAGE content item|
|&presentationSeriesUID=<uid>||Series Instance UID for referenced presentation state obtained from the Current Requested Procedure Evidence Sequence or the Pertinent Other Evidence Sequence in the KO Instance|
|&contentType=video/mpeg||Present if Referenced SOP Class UID from IMAGE content item is for a multi-frame image IOD|
Notes: 1. Literal strings are in normal typeface, while <italic typeface within angle brackets> indicates values to be copied from the identified source.
2. The default contentType for single frame images is image/jpeg, which does not need to be specified as a WADO component. However, the default contentType for multiple frame images is application/dicom, which needs to be overridden with the specific request for video/mpeg.
3. There is not yet a standard mechanism for minimizing the potential for staleness of the <scheme> :// <authority> / <path> component.