HL7 for imaging result documents and narrative reports

The report is not just text; it is status, identity, payload, and clinical timing.

Imaging reports can arrive as ORU_R01, MDM_T02, or local variants. The payload may be plain text, formatted text, a PDF, a reference, or structured observations. The right interface design starts by asking what the receiver must do with the report: display it, file it, update order status, trigger critical-results follow-up, or feed analytics.

IHE Radiology Results Distribution uses HL7 v2.5.1 ORU messaging for imaging-result reports and separates report metadata from the payload format. That is a useful mental model even when your local interface is not formally claiming the profile.

MSH|^~\&|RIS|CITYHOSP|EHR|CITYHOSP|20260715172000||ORU^R01^ORU_R01|IMG000501|P|2.5.1 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F ORC|RE|RAD4488^EHR|ACC778899^RIS OBR|1|RAD4488^EHR|ACC778899^RIS|24627-2^CT Abdomen and Pelvis W contrast^LN|||20260715140000|||||||||67890^Radiologist^Riley^^^^^^NPI||||ACC778899||20260715171500|||F OBX|1|TX|18748-4^Diagnostic imaging study report^LN||No acute intra-abdominal abnormality.||||||F|||20260715171000 OBX|2|ED|PDF^Report PDF^LOCAL||^application^pdf^Base64^JVBERi0xLjQKJcTl8uXrCg==||||||F|||20260715171000

This is synthetic sample data for learning and testing. Open it in HL7 Soup Web before mapping it so the segment groups, repeated fields, and coded values are visible.

Status And Identity Come Before Display

A report should carry enough identity to link to patient, encounter, order, accession, report/document ID, author/interpreter, result status, and report time. Without that, even a perfect PDF can be filed in the wrong place or fail to replace the preliminary version.

Report status is not a style preference. Preliminary, final, corrected, amended, and cancelled reports should drive different receiver behavior.

  • Keep accession/order identifiers from ORC and OBR.
  • Preserve report status and observation status.
  • Store payload type and encoding when using ED values.

ORU Or MDM?

ORU is often easier when the report belongs to an order/result workflow. MDM is often natural when the receiver treats the report as a managed document with TXA metadata. Neither is automatically better; the receiving system's filing model decides.

If the sender provides both narrative text and a PDF, agree which copy is authoritative and how amendments replace or supplement the earlier version. If the message carries DICOM SR-derived measurements as well, treat that as a mapping design: the structured values usually belong in repeated OBX rows, while the human-readable report or PDF has its own display and filing behavior.

A Practical Integration Soup Workflow

In Integration Soup, route imaging reports by status, destination, accession, and payload type. If the message contains a PDF, use the PDF/binary HL7 tutorial to extract or create ED payloads safely. If converting structured reports, use the DICOM SR to HL7 tutorial pattern.

The Test Pack I Would Ask For

Ask for preliminary, final, amended, cancelled, critical-result, text-only, PDF, large PDF, missing accession, and duplicate report messages.