Referral interoperability still spans both legacy and modern contracts
Most production environments still bridge multiple interoperability styles at once. Legacy HL7 v2 messages may place or result orders, FHIR resources may expose modern APIs, and DICOM or departmental workflows may carry execution context for imaging.
Representative HL7 v2 referral order
A simplified ORM-style order showing how patient identity, control state, and requested service are carried in a traditional interface.
Click on a segment above to highlight its fields
Hover or click any field value for detailed explanation
How common referral events map across standards
| Business event | Legacy pattern | Modern pattern |
|---|---|---|
| Place referral or order | HL7 v2 ORM with ORC and OBR | FHIR ServiceRequest |
| Track operational work | Status codes or local work queues | FHIR Task or workflow profile |
| Book appointment | Local scheduler or HL7 SIU patterns | FHIR Appointment and Slot |
| Return results | HL7 v2 ORU | FHIR DiagnosticReport plus linked observations |
HL7 v2.4 Chapter 4: Order Entry
Reference chapter for HL7 v2 order messages, including ORC and OBR semantics used in many referral interfaces.
Read HL7 Chapter 4ServiceRequest - FHIR v4.0.1
Official modern order resource for requests to perform diagnostics, procedures, or other healthcare services.
Read the FHIR order resourceClosed-loop interoperability needs state visibility after transmission
Modern referral design is about what happens after the receiving organization gets the request. Systems need a durable way to represent acceptance, triage, booking, inability to perform, and final closure without pretending one transport message covers every step.
Closed-loop referral state propagation
Loading diagram...
XDW is useful when the referral must remain visible after the original message leaves the sender. Instead of pretending one interface event tells the whole story, the participants share an evolving workflow document whose task list and status can be updated over time.
That is the core closed-loop lesson: the transport may be HL7 v2, FHIR APIs, or local messaging, but the business workflow still needs a durable shared representation of acceptance, booking, fulfillment, and final closure.
The workflow-document view matters because it captures more than the latest status label. It preserves the completed step, inputs, outputs, timestamps, and task-event history that later teams need when they reconcile what really happened to the referral.
Transmission is not completion
A robust referral platform proves that the downstream team accepted the work, not just that an interface engine delivered bytes successfully.
IHE Scheduling profile
IHE guidance for appointment discovery and scheduling workflows between organizations.
Read the scheduling workflow profileCross-Enterprise Document Workflow (XDW)
IHE workflow profile for a shared, versioned workflow document that tracks tasks and status changes across organizations, including simple referral processes.
Read the XDW profileTask - FHIR v4.0.1
FHIR workflow resource for operational tracking when a referral turns into actionable tasks.
Read the Task specificationFHIR APIs make the referral lifecycle queryable step by step
A modern referral API should expose more than the initial order. Teams often need to query the current operational task, confirm whether a booking exists, and later retrieve the resulting report without parsing a stream of flat messages.
Representative FHIR referral lifecycle endpoints
Example endpoints showing how a sender or downstream application can place a referral, inspect operational status, and later fetch the diagnostic result.
Request
POSTANNOTATIONS
Response
Appointment - FHIR v4.0.1
Official booking resource used when a referral becomes a scheduled healthcare event.
Read the Appointment resourceDiagnosticReport - FHIR v4.0.1
Official result resource used when the service completes and the receiving organization returns a report.
Read the DiagnosticReport resourceKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.