HL7 + DICOM
One platform for DICOM routing and HL7 order workflows
RadFuzion brings DICOM routing, HL7 order workflows, automated prior retrieval, cloud image management and on-site downtime reading into one platform. HL7 orders fill the worklist, start prior retrieval and release held images; reports go back to the RIS as ORU results.
The basics
What HL7 orders add to DICOM routing
A DICOM study carries images and a header. What it often lacks is the context of the order behind it: the accession the RIS will report against, the patient as registered, the procedure that was ordered, its priority, the reason for the exam and the patient’s allergies. That context lives in the HL7 order the RIS sends when the exam is scheduled.
When the router has the order, it can do more than move images. It can give the scanner a worklist so the technologist doesn’t retype demographics, fetch the patient’s priors before the exam is read, keep images back until their order has arrived, so systems downstream that need the order first get it before the images, and send the finished report back to the RIS against the right accession.
RadFuzion does this on the same server that routes your DICOM. One distinction matters: routing rules decide where images go based on DICOM data (tags and the calling and called AE title), not on HL7 fields. HL7 orders drive the workflow around routing.
How it fits together
Orders in, workflow in the middle, results out
Three jobs, all on the RadFuzion server.
Orders in, over MLLP
RadFuzion listens for HL7 v2 orders on a port you choose, reads the fields you map, stores each order by accession number and acknowledges it once it is stored.
Orders drive the workflow
Each order can fill the modality worklist, start prior retrieval, appear in the RadRead reading list and release images held until it arrives. Routing itself stays rule-based on DICOM data.
Results back to the RIS
Final reports that arrive as DICOM Basic Text SR, RadRead preliminary reports and RadSR measurements go back out as HL7, with retries and a resend button where the workflow needs one.
Architecture
Where RadFuzion sits between the RIS and imaging
RadFuzion connects to the RIS or EHR over MLLP and to modalities, PACS and cloud stores over DICOM, DICOMweb and cloud storage APIs. RadEngine7 is optional, for feeds that need changing before RadFuzion reads them.
RIS / EHR
Sends orders, receives results
RadEngine7 (optional)
Changes HL7 between systems: mappings, lookups, filters
Orders (MLLP)
ACK
ORU results
RadFuzion server
HL7 listener
Port 2575 by default. Field mapping, AA / AE ACK
then the order store, keyed by accession
Orders drive
DICOM receiver and routing rules
Rules match DICOM tags and AE titles
Results out
SR to ORU, RadRead prelims, RadSR results
Worklist C-FIND
C-STORE
Query / retrieve
Modalities
Query the worklist, send images
PACS and cloud
DICOM C-STORE or DICOMweb STOW-RS; prior archives
Orders in
How RadFuzion receives HL7 orders
RadFuzion receives HL7 v2 orders over MLLP on a port you choose, 2575 by default, and can also listen for MLLP over TLS on a second port (2580 by default). It reads fields by position and doesn’t depend on a particular v2 version. You choose which HL7 fields hold the accession, MRN, patient name, birth date, sex, modality, exam, schedule, station, priority, reason for exam, allergies and medical alerts.
Each order is stored by accession number before RadFuzion answers. The sender gets AA once the order is stored, or AE when it can’t be, for example when the accession field is empty. The full raw message is kept by accession too, so results and RadSR can build on the original order after the exam has left the worklist.
An order cancel (ORC-1 = CA) removes the order from the worklist and stops its prior fetch. A repeat order for the same accession updates the stored order.
Default field mapping
Where RadFuzion looks out of the box, and where each value lands on the worklist. Every row can be changed.
| Value | Default HL7 field | Worklist attribute |
|---|---|---|
| Accession number | OBR-3.1 | Accession Number |
| Patient ID (MRN) | PID-3.1 | Patient ID |
| Patient name | PID-5 | Patient Name |
| Birth date / sex | PID-7 / PID-8 | Patient Birth Date / Sex |
| Modality | OBR-24 | Modality (scheduled step) |
| Exam description | OBR-4.2 | Requested Procedure / Study Description |
| Requested procedure ID | OBR-4.1 | Requested Procedure ID |
| Scheduled date and time | OBR-7 | Scheduled Step Start Date / Time |
| Referring physician | OBR-16 | Referring / Requesting Physician |
| Station AE / station name | OBR-21 / OBR-20 | Scheduled Station AE Title / Name |
| Priority | OBR-27.6 | Requested Procedure Priority |
| Reason for exam | OBR-31.1 | Reason for the Requested Procedure |
| Allergies | AL1-3.2 (every AL1) | Allergies |
| Medical alerts | None until you set one | Medical Alerts |
Workflow
What an HL7 order drives in RadFuzion
An HL7 order can fill the modality worklist, start prior fetching, appear in RadRead and release images held for it. Each of these is turned on separately.
A modality worklist from your orders (RadList)
RadList answers DICOM Modality Worklist (C-FIND) queries from your HL7 orders. Scanners get the accession, patient ID, name, birth date and sex, the requested procedure, referring physician, priority, reason for exam, allergies, medical alerts and the scheduled procedure step. You can limit each modality to its own AE title, modalities and station, and choose whether unmapped scanners see everything or nothing. By default, when an exam’s images arrive its order leaves the worklist (not while Hold for ORM is on); the order record stays for reporting and results. More on RadList
Prior retrieval when the order lands (RadFetch)
Each order can start a RadFetch job. RadFetch searches your archives for the patient’s relevant priors using rules you set, retrieves them, and passes them through your routing rules to the reading destination. STAT orders go first, a duplicate order within a minute (by default) doesn’t start a second job, and a cancel stops the job. More on RadFetch
The RadRead reading list
Orders feed RadRead, the on-site reading module used for downtime. Radiologists see the ordered exams, open the images and send preliminary reports back to the RIS. When an HL7 order arrives for an exam RadRead had built from images alone, the HL7 order replaces it. PACS downtime with RadRead
Hold images until the order arrives
Some PACS and cloud stores need the order before the images. Hold for ORM keeps incoming images until the matching order arrives, matched by accession number, with a timeout you set (15 minutes by default) and an optional delay after the order lands. If no order arrives before the timeout, the exam waits in Needs attention with its images kept, and staff send it without the order or delete it; an order that arrives late still releases it. A setting sends these exams on without the order instead. Set the timeout to fit how quickly your RIS sends orders. Holds are off by default.
No order feed
Image-first sites: build the order from the images
Not every site has a RIS feed. Where exams start at the scanner, there is no order to work from. For the exams a routing rule picks, RadDicom7 builds an HL7 ORM^O01 from the DICOM and sends it ahead of the images, by MLLP, HTTP(S) or Amazon S3. It can generate an accession when the images have none, skips exams that already have an order, and by default waits 30 seconds before forwarding the images, to give the receiving system time to take in the order first. More on RadDicom7
RadGen7 does the reverse. From each HL7 order sent to its own port (2577 by default) it makes a placeholder DICOM study and sends it to the destination named in a field of the order, for systems that expect a study to exist before the real images arrive. More on RadGen7
RadDicom7 and RadGen7 are included with every RadFuzion license.
Results out
Getting reports and results back to the RIS
Final reports from DICOM SR
Some reporting systems return final reports as DICOM Basic Text SR. RadFuzion turns them into HL7 ORU^R01 results, built from the SR alone, with preliminary, final and corrected status (P, F, C). A report that was already sent unchanged is skipped. Results go to MLLP, Amazon S3 or Mirth REST, are retried automatically, and can be previewed and resent from the send log.
RadRead preliminary reports
RadRead preliminary reports go out as HL7 v2.5.1 ORU^R01 over MLLP, or by fax. Each one waits 30 seconds by default after the radiologist completes it, so it can be recalled, and failed sends are retried.
RadSR measurements
RadSR adds measurements to the exam’s HL7 order as OBX segments and sends it by MLLP, Mirth REST or Amazon S3, or posts the values as JSON, including FHIR R4 Observations, to a REST endpoint. More on RadSR
Change HL7 fields without scripts
A routing rule can change any field of the HL7 order RadDicom7 builds for its exams, and each SR-to-ORU profile has the same field mappings. Name the field as SEG.field.component (for example OBR.4.2) and fill it from text that can include DICOM tag values, from a DICOM tag, or from another field. Each edit can overwrite, append, prepend or fill only when empty, and can apply to every exam, only to priors RadFetch retrieved, or only to the rest.
Matching
How images are matched to orders
RadFuzion matches images to orders by accession number, and only by accession number. The order’s accession, read from OBR-3.1 unless you map another field, must equal the DICOM Accession Number in the images. RadFuzion doesn’t match on MRN, issuer of patient ID or patient name.
In practice this works well when scanners use the worklist, because the accession comes from the order. Where technologists key the accession by hand, a typo means the images don’t find their order. If holds are on, that exam waits until the timeout, then shows in Needs attention for staff to send without the order or delete.
RadEngine7
RadEngine7 for the HL7 work around imaging
RadEngine7 is a no-code HL7 v2 interface engine that comes with every RadFuzion license. It runs as a separate service (installed as a Windows service) with its own web interface, and pairs with RadFuzion. Use it when a feed needs changing before RadFuzion reads it, or when you need to move HL7 between other systems: reformat a RIS feed, look up codes in a table, split one feed to several receivers, or write report text out as a PDF.
Channels are built from steps rather than code. Each message is stored before it is acknowledged, each outbound has its own queue and retries, and the message log lets you find and replay messages. MLLP inbounds and outbounds can use TLS, and HTTP listeners and RadEngine7’s own web page can run over HTTPS. Alerts tell you when a channel stops, an outbound can’t deliver, or messages pile up. If you use the AI assistant, RadEngine7 can rebuild a Mirth channel export as builder steps for you to review and test before you add it.
- In: MLLP, HTTP, folder, Amazon S3, SFTP, FTP/FTPS, another channel
- Out: MLLP, HTTP, folder, Amazon S3, SFTP, FTP/FTPS, PDF
- Set, copy, lookup tables, dates, regex, segments, if/else
- Sandboxed JavaScript for what the steps can’t do
- A queue and retries for each outbound
- Message log with replay
- Alerts to email, Teams, Slack, Google Chat or a webhook
- ACK on receipt, after delivery, or none
- MLLP over TLS both ways; HTTPS listeners
- Mirth channel import with the AI assistant
Monitoring
Seeing what HL7 did, and fixing it
- HL7 Messages page. A searchable list of recent orders received, failed or canceled, with the extracted fields and the raw message where it could be read. Filter by accession, MRN, patient, birth date, modality, exam and date.
- Listener health. A banner in the web interface warns when the HL7 receiver isn’t running.
- Audit trail. Order received, failed and canceled events are written to the audit log.
- Test sends. Send a test ORU to the RadRead delivery target, a test order to RadDicom7 and RadMatch targets, and a test SR-to-ORU result before going live.
- Resend. SR-to-ORU results and RadSR HL7 can be sent again from the web interface. Inbound orders can’t be replayed from RadFuzion; RadEngine7 can replay what passes through it.
Examples
Three workflows, step by step
1. Order-first outpatient MRI
- 1The RIS schedules a brain MRI and sends an ORM^O01 over MLLP. RadFuzion stores it by accession and answers AA.
- 2The order goes on the worklist, and RadFetch starts pulling the patient’s prior brain MRI from the archive.
- 3The MRI queries the worklist, picks the patient and scans. The images carry the order’s accession.
- 4Routing rules send the study to the PACS. By default, the order then leaves the worklist.
- 5The final report comes back as a Basic Text SR, and RadFuzion sends it to the RIS as an ORU^R01.
2. Image-first site with no RIS feed
- 1A technologist scans a walk-in patient. The images arrive at RadFuzion with no order behind them.
- 2A routing rule turns on RadDicom7 for the exam. RadDicom7 builds an ORM^O01 from the DICOM, generating an accession if needed, and sends it to the receiving system.
- 3RadFuzion waits 30 seconds by default before routing rules forward the images, to give the receiving system time to take in the order.
3. A downtime preliminary back to the RIS
- 1The cloud PACS is unreachable. HL7 orders keep arriving and keep the RadRead list current.
- 2New exams wait on the RadFuzion server for the PACS, and RadRead opens them from there, read-only.
- 3The radiologist dictates a preliminary report. After the 30-second recall window it goes to the RIS as an ORU^R01 over MLLP, or by fax.
- 4When the PACS is back, exams held for it are forwarded.
Downtime reads are preliminary. The built-in viewer is non-diagnostic and is not FDA cleared for primary diagnostic interpretation.
Scope
What’s supported, and what isn’t
The HL7 side of RadFuzion is built for imaging orders and results. This is the plain list, so you can plan around the gaps.
| Capability | Status | Notes |
|---|---|---|
| HL7 v2.x order messages in (ORM^O01 and similar) | Supported | Over MLLP. Any message with an accession in the mapped field is stored as an order, so send this port order traffic only. |
| Order cancel | Supported | ORC-1 or ORC-5 = CA, DC or OC removes the order and stops its prior fetch. |
| HL7 ORU^R01 results out | Supported | Final reports from Basic Text SR, and RadRead preliminary reports. |
| HL7 ORU^R01 results in | Supported | Optional second listener (port 2576 by default), used by RadRead. |
| ORM^O01 built from DICOM | Supported | RadDicom7, for sites with no order feed. |
| ADT patient updates and merges (A08, A47, A40) | Supported | From RadFuzion 6.8.5. ADT patient updates (A01, A04, A05, A08, A28, A31) and ID changes and merges with MRG (A47, A46, A40, A34, A18, A30) correct exams RadFuzion has not sent yet; exams already sent are noted, not re-sent. An ADT with no MRG never changes an MRN. |
| Order updates that change the patient | Supported | From RadFuzion 6.8.5. A new order for the same accession with a different MRN, name, birth date or sex corrects the exam before it is sent. |
| SIU scheduling, MDM documents | Not supported | Not processed. |
| HL7 over TLS (encrypted MLLP) | Supported | The order and ORU receivers can each open a TLS port beside the plain one, with optional client certificates, and every HL7 sender can use TLS. RadEngine7 does both ways. Not on the RadGen7 order port. |
| FHIR | Limited | Output only: RadSR can post results as FHIR R4 Observations to a REST endpoint. No FHIR orders, no FHIR server. |
| MPPS (Modality Performed Procedure Step) | Supported | From RadFuzion 6.8.7, with RadList. Modalities report on the worklist AE (or the receiver); RadFuzion keeps each step, can mark the order started and take it off the worklist when completed, and passes every message on, in order, to your RIS or PACS. |
| Matching images to orders | Limited | By accession number only. No MRN, issuer or name matching. |
| Worklist character set | Limited | The worklist answers in ISO_IR 100 (Latin-1). |
Planning
When you still want an enterprise interface engine
RadFuzion and RadEngine7 cover these imaging HL7 jobs: orders in, worklist, priors, holds and results out. Keep or add an enterprise interface engine if you need any of these:
- Patient identity across many systems: a master patient index, or matching patients by demographics.
- FHIR APIs, or X12 and other non-HL7 v2 formats.
- Clustering, failover or high availability for the interface layer.
- Database or email connectors, or dozens of systems with their own feeds.
In that setup the enterprise engine stays the hub, sends imaging orders on to RadFuzion, and receives the ORU results RadFuzion sends back. If you are moving channels off Mirth, RadEngine7 can import them with its AI assistant.
Under the hood
HL7 and DICOM capabilities at a glance
- HL7 v2 orders over MLLP (2575), or MLLP over TLS
- AA / AE acknowledgment after the order is stored
- Field mapping for accession, MRN, exam, station and more
- Order cancel (ORC-1 = CA) clears worklist and prior fetch
- Modality Worklist C-FIND from HL7 orders
- Per-station worklist filtering by AE, modality, station
- Prior retrieval (RadFetch) started by each order
- Hold images until their order arrives
- ORM^O01 built from DICOM for image-first sites
- Basic Text SR to ORU^R01 (P / F / C)
- RadRead preliminary ORU^R01 over MLLP, or fax
- Searchable HL7 Messages page with the raw message
This is the short list. See every RadFuzion feature
FAQ
HL7 and DICOM questions
Can a DICOM router process HL7 messages?
Yes, when it includes an HL7 listener. RadFuzion, a DICOM router, receives HL7 v2 order messages over MLLP, stores each order by accession number and acknowledges it. The orders fill the modality worklist, start prior retrieval, appear in the RadRead reading list and can release images held until their order arrives. RadFuzion also sends results back to the RIS as HL7 ORU^R01 messages.
How can HL7 orders trigger DICOM workflows?
In RadFuzion, an HL7 order arriving over MLLP becomes a modality worklist entry that scanners query with DICOM C-FIND, starts a prior search that pulls relevant older studies by DICOM query/retrieve, and appears in the RadRead reading list. With Hold for ORM turned on, images wait until the order with the same accession number arrives. Routing rules still decide where images go, based on DICOM tags and AE titles.
Which HL7 message types does RadFuzion support?
RadFuzion takes in HL7 v2 order messages (typically ORM^O01) on its order port, and ORU^R01 results on an optional second port used by RadRead. It sends ORU^R01 results for final reports that arrive as DICOM Basic Text SR and for RadRead preliminary reports, ORM^O01 orders that RadDicom7 builds from images, and orders with RadSR measurement OBX segments added. From 6.8.5 the order port also takes ADT messages: patient updates and ID changes or merges correct exams RadFuzion has not sent yet. SIU and MDM messages are not processed.
Does RadFuzion need a separate HL7 interface engine?
Not for its own imaging workflow: RadFuzion reads HL7 orders directly once you map which fields hold the accession, MRN and exam. If a feed needs changing first, RadEngine7, a no-code HL7 v2 interface engine that comes with every RadFuzion license, can sit in front. Sites that need patient identity reconciliation across many systems (a master patient index), FHIR APIs, X12 or high availability should keep an enterprise interface engine and send the imaging feeds on to RadFuzion.
How does RadFuzion match images to HL7 orders?
RadFuzion matches images to HL7 orders by accession number only. The order’s accession, read from OBR-3.1 by default, must equal the DICOM Accession Number in the images. Scanners that use the RadFuzion modality worklist get the accession from the order, which keeps the two in step. RadFuzion does not match on MRN, issuer or patient name.
Can RadFuzion create a modality worklist from HL7 orders?
Yes. RadList, a RadFuzion module, answers DICOM Modality Worklist C-FIND queries from HL7 orders, with patient demographics, accession, procedure, priority, reason for exam, allergies and medical alerts. Each modality can be limited to its own AE title, modalities and station, and by default an order leaves the worklist when its images arrive (not while Hold for ORM is on). An order cancel (ORC-1 = CA) removes it.
How do radiology reports get back to the RIS from RadFuzion?
As HL7 ORU^R01 messages. Final reports that arrive at RadFuzion as DICOM Basic Text SR become ORU^R01 results with preliminary, final or corrected status, sent by MLLP, Amazon S3 or Mirth REST, retried automatically and resendable. RadRead preliminary reports go out as HL7 v2.5.1 ORU^R01 over MLLP, or by fax. RadSR measurements are added to the order message as OBX segments.
Does RadFuzion support FHIR?
Only as an output. RadSR can post measurement results to a REST endpoint as FHIR R4 Observations. RadFuzion has no FHIR server and does not accept orders over FHIR; orders arrive as HL7 v2 over MLLP, and reports go out as HL7 v2 ORU^R01.
What happens if the HL7 order never arrives?
With Hold for ORM turned on, RadFuzion keeps an exam’s images until the order with the same accession number arrives, up to a timeout you set (15 minutes by default). If no order arrives in time, the exam waits in Needs attention as Waiting for order, timed out, with its images kept: send it without the order or delete it, and an order that arrives late still releases it. To send these exams on automatically instead, set When the Hold Times Out to Send it without the order. With holds off, images route as soon as they finish arriving.
Is HL7 traffic to RadFuzion encrypted?
It can be. RadFuzion’s HL7 order receiver and ORU receiver can each listen on a TLS port beside the plain one (2580 and 2581 by default), optionally requiring client certificates, and every HL7 sender in RadFuzion can send over TLS, checking the receiver by system trust or a pinned certificate. RadEngine7 does MLLP over TLS in both directions. Plain MLLP stays available for systems that don’t support TLS; keep those links on a private network or a VPN.
See the worklist and routing on sample data
Open the live preview to look at the modality worklist and routing on sample data. No PHI, no signup.