HL7 for radiology orders and results

Radiology HL7 sits between clinical orders, RIS scheduling, PACS identity, and report distribution.

Radiology uses HL7 for several different conversations: the EHR places an order, the RIS schedules and manages the study, PACS and modalities need patient and accession context, and the final report returns to the clinical record. In older feeds that often means ORM_O01 orders and ORU_R01 reports. Newer profiles may use imaging-specific OMI_O23 orders.

The order/result relationship is the thing to protect. ORC carries order control and placer/filler identifiers; OBR carries the ordered procedure, timing, status, accession, and result/report context. If those identifiers drift, images and reports can be clinically correct but filed to the wrong order.

MSH|^~\&|EHR|CITYHOSP|RIS|IMAGING|20260715121500||ORM^O01^ORM_O01|RAD000501|P|2.5.1 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F PV1|1|O|RAD^WAIT^1^CITYHOSP||||12345^Careful^Clara^^^^^^NPI ORC|NW|RAD4488^EHR||RADGRP22^EHR|||^^^20260715140000^^R|||20260715121500|||12345^Careful^Clara^^^^^^NPI OBR|1|RAD4488^EHR||24627-2^CT Abdomen and Pelvis W contrast^LN|||20260715140000|||||||||12345^Careful^Clara^^^^^^NPI||||ACC778899|||20260715121500|||O

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.

Orders And Results Are Different Contracts

An order tells the imaging department what is requested. A result tells the clinical system what was found or what report is available. Keep those workflows separate even if the same accession number appears in both. Order messages need control-code behavior such as new, cancel, discontinue, change, and status. Results need final/preliminary/amended behavior and a reliable report payload.

IHE Radiology profiles are useful here because they describe how HL7 and DICOM workflow fit together. In practice, your HL7 work needs to preserve enough data for DICOM Modality Worklist, PACS reconciliation, report status, and downstream clinical display.

  • Use ORC-1 for order intent, not just routing.
  • Protect accession numbers in OBR fields and local profile fields.
  • Treat patient merges from ADT_A40 as radiology safety events.

Radiology Reports Can Be Text, Structured Data, Or Documents

Many radiology result interfaces use ORU_R01 with narrative report text in OBX. Some send preliminary and final reports as separate events. Some send PDF or formatted content using the ED datatype. IHE Results Distribution describes HL7 v2.5.1 ORU messaging for imaging results and specifically distinguishes the metadata from the payload format.

Do not design the receiver as if every report is a single plain-text OBX forever. Keep room for corrected reports, critical-result flags, addenda, document identifiers, and payload format differences.

Receiver Capability Beats Syntax

A valid HL7 document payload is not the same thing as a supported receiving workflow. A RIS, PACS-adjacent system, or ultrasound reporting product may accept the ORM or ORU structure but still be unable to process an embedded Base64 PDF in OBX-5. Before you build the payload, ask the receiver to choose the actual contract: embedded ED value, URL/reference, separate file drop, managed document message, or no document transfer at all.

For referral-to-order workflows, map the order first: procedure requested, urgency, destination, clinical details, referrer, provider identifiers, and accession/order identifiers. Then handle the attachment as a separate capability question. The documents and PDFs article and the Integration Soup PDF/binary tutorial are the right next stops when the receiver really does support payload transfer.

A Practical Integration Soup Workflow

In Integration Soup, route radiology orders by message type, order control, facility, modality/procedure code, and destination RIS or modality workflow. Keep order identifiers and accession values visible in logs. For results, route preliminary, final, amended, and cancelled report behavior explicitly.

When radiology sends DICOM Structured Reports and you need HL7 output, the DICOM SR to HL7 ORU tutorial is directly relevant. For PDF reports, pair this with the PDF/binary in HL7 tutorial.

The Test Pack I Would Ask For

Ask for a new order, changed order, cancelled order, scheduled order, final report, amended report, report with a critical finding, a patient merge affecting a study, and a report payload in every format the sender claims to support. Then open each sample in HL7 Soup Web before you wire it into production routing.