Home / Insights / Connectivity

How a lab orders and results interface works (HL7 ORM and ORU)

ConnectivityPublished 2026-11-1810 min readInternational

When a clinician orders a test in the EHR and the result appears in the chart a few hours later without anyone typing, an orders and results interface is doing the work. This guide explains how that interface works, the messages involved, the details that cause most go-live problems, and how to plan the project with your EHR vendor.

Written and reviewed by the Catenix team. How these guides are written and checked.

In brief

  • Orders usually travel from the EHR to the lab system as HL7 v2 ORM^O01 (or OML^O21) messages; results come back as ORU^R01.
  • More EHRs now also offer FHIR APIs: ServiceRequest for orders, DiagnosticReport and Observation for results.
  • The specimen ID on the tube barcode links the order, the analyser run and the result, so agree its format first.
  • Every message should be acknowledged, logged and retried on failure; corrected results need their own tested path.
  • Catenix receives orders and sends results to athenahealth, eClinicalWorks and Epic over interfaces built to each vendor's published specification, and any record system that accepts a standard HL7 v2 or FHIR result. A result without a single clear patient match waits for a person; it is never guessed.

Take it with you: POCT connectivity buyer's guide · POCT readiness checklist (PDF, no form).

The end-to-end flow

  1. A clinician orders tests in the EHR for a patient.
  2. The EHR sends an order message to the lab system with the patient, the ordering clinician, the tests and an order number.
  3. The lab collects the sample and labels it with a specimen ID, either printed by the EHR or by the lab system at accession.
  4. The analyser reads the barcode and asks the lab system which tests to run (host query), or receives a worklist.
  5. The analyser runs the tests and sends results to the lab system.
  6. The lab system matches results to the order, applies QC and review rules, and a scientist or the rules release them.
  7. The lab system sends a result message back to the EHR, which files it in the chart against the original order.
  8. If a result is later corrected, a corrected result message replaces the earlier value.

The HL7 v2 messages

MessageDirectionKey segmentsPurpose
ORM^O01 or OML^O21EHR to labMSH, PID, PV1, ORC, OBRNew order, change or cancellation
ACKBothMSH, MSAConfirms a message was received and accepted or rejected
ORU^R01Lab to EHRMSH, PID, ORC, OBR, OBX, NTEResults, one OBX per result
ADTEHR to labMSH, PID, PV1Patient demographics updates, where used

Messages usually travel over TCP using MLLP framing on a private network or a VPN, or are wrapped in HTTPS by cloud systems. Our HL7 field guide shows real segments, and our LIS and EHR outbound guide covers the result side in detail.

A worked example: one TSH order and its result

A clinician orders a TSH in the EHR. The EHR sends an order message to the lab system:

MSH|^~\&|EHR|CLINIC|LABSYS|LAB|20261118090200||ORM^O01|ORD000913|P|2.5.1
PID|1||MRN12345^^^CLINIC^MR||TEST^PATIENT||19850214|F
PV1|1|O
ORC|NW|ORD7781|||||||20261118090200|||1234567890^EXAMPLE^PROVIDER
OBR|1|ORD7781||3016-3^TSH^LN|||20261118090000

ORC-1 NW means a new order. ORD7781 in ORC-2 and OBR-2 is the EHR's placer order number, and ORC-12 names the ordering provider. The lab system replies with an acknowledgement:

MSH|^~\&|LABSYS|LAB|EHR|CLINIC|20261118090201||ACK^O01|ACK000913|P|2.5.1
MSA|AA|ORD000913

MSA-1 AA means accepted; AE or AR would mean an error or a rejection, and the EHR should alert someone. The sample is drawn and labelled with specimen ID 2611180042, the analyser runs it, and the lab system returns the result:

MSH|^~\&|MIDDLEWARE|LAB|EHR|CLINIC|20261118101530||ORU^R01|MSG000417|P|2.5.1
PID|1||MRN12345^^^CLINIC^MR||TEST^PATIENT||19850214|F
ORC|RE|ORD7781|2611180042
OBR|1|ORD7781|2611180042|3016-3^TSH^LN|||20261118094500|||||||||||||||20261118101530|||F
OBX|1|NM|3016-3^TSH^LN||2.15|mIU/L|0.27-4.20|N|||F|||20261118101500

The result carries ORD7781 back in ORC-2 and OBR-2 and the specimen ID as the filler number, which is how the EHR files the value against the original order instead of creating an unsolicited result. The EHR then sends its own ACK, and the lab system records it. All identifiers and names here are invented for the example; real interfaces follow each EHR's own specification for field use.

The FHIR alternative

Many cloud EHRs expose FHIR APIs. An order is a ServiceRequest; the lab system can read it, or receive a notification. Results are written back as a DiagnosticReport with one Observation per result, linked to the ServiceRequest. FHIR is easier to build on with modern tools, but each EHR implements it differently, with its own app registration, permissions and review process. See HL7 v2 vs FHIR for lab results.

The details that cause go-live problems

Specimen ID format. If the EHR prints labels, the analyser must be able to read that barcode symbology and length. If the lab prints labels, the EHR must accept the lab's specimen ID on the result. Decide early.

Test codes. The EHR's orderable codes and result codes must map to the lab's tests. In the US, results are commonly coded with LOINC; in the NHS, SNOMED CT is used for pathology. See LOINC and SNOMED coding for lab results.

Panels. A panel ordered as one code may produce many results. Agree whether the EHR expects one OBR with many OBX segments or one OBR per test.

Patient matching. The result must carry the patient and order identifiers exactly as the EHR sent them. Never let the analyser's patient fields overwrite them. In Catenix, a result without a single clear match waits for a person; it is never guessed onto a patient.

Corrected results. The EHR must replace, not duplicate, a corrected value. Test it.

Cancellations and add-on tests. An order cancelled after collection, or a test added to an existing sample, needs a defined path.

Acknowledgements and retries. If the EHR rejects a message, the lab system must alert someone and hold the result, not drop it.

Time zones and timestamps. Collection, receipt and result times must be sent in the format and time zone the EHR expects, or results can appear out of order in the chart. Check this in the test environment, especially around daylight saving changes.

Unsolicited results. A result that arrives without an order the EHR recognises may land in a separate inbox or be rejected. Agree how the EHR handles it, and who checks that inbox.

Who builds what, and who pays

An interface has two ends. Your lab system vendor configures its side: mappings, message formats, connection and monitoring. Your EHR vendor configures its side: the orderable catalogue, result filing, the connection and, often, an approval or certification process. Some EHR vendors charge for this; some include it. Ask both vendors for their process, timeline and fees in writing before you sign, and start the EHR request early, because it is usually the slowest step.

Questions to ask your EHR vendor

  1. Which routes do you support for an outside lab system: HL7 v2, FHIR, your own API or file transfer?
  2. Is there an interface fee, and who signs off the interface?
  3. Do you send orders electronically, and in which message type?
  4. Which code system do you expect on results: LOINC, SNOMED CT or your own codes?
  5. How are corrected results filed, and what happens to a result that does not match an order?
  6. Is there a test environment, and how long does approval take?

Then check the analyser side: our analyser connection guides and the open connectivity dataset list protocols and order support for 130 analysers, and you can ask whether a given analyser connects to your EHR inside ChatGPT or Claude through our AI assistant connector.

Testing the interface

Run a structured test plan with real but test-patient data: a single test, a panel, an abnormal result, a critical result, a corrected result, a cancelled order, an add-on test, an order with no sample, a sample with no order, and a network outage. Record each outcome as validation evidence for your quality system.

Where Catenix fits

Catenix receives orders from the EHR, prints or accepts specimen IDs, sends worklists or answers host queries from analysers, applies QC and competency rules, and returns results to the EHR as HL7 v2 or through FHIR and vendor APIs, with acknowledgements, retries and a full audit trail. Its interfaces are built to each vendor's published specification for athenahealth (API, HL7 or athena-hosted SFTP), eClinicalWorks and Epic, and it works with any system that accepts a standard HL7 v2 or FHIR result, including Oracle Health, NextGen, SystmOne and EMIS Web. See all integrations. Catenix is connectivity, workflow and record-keeping software; it does not interpret results and is not marketed as a medical device.

Questions people ask

What is the difference between ORM and ORU?

ORM messages carry orders from the EHR to the lab. ORU messages carry results from the lab back to the EHR.

Do all EHRs accept HL7 v2 lab results?

Most hospital and ambulatory EHRs do, sometimes as a paid interface. Some cloud EHRs prefer their own API or FHIR. Ask your EHR vendor which routes they support for an outside lab system.

How long does a lab interface take?

The lab side can be configured in days for a supported EHR. The EHR vendor's process often takes several weeks, so start that request first.

Can results go to the EHR without electronic orders?

Yes, results can be sent against patient identifiers alone, but matching is safer with an electronic order and a specimen ID.

Does Catenix support bidirectional interfaces?

Yes. Catenix receives orders and returns results, and supports analyser host query where the analyser offers it.

What does an HL7 ACK message do?

It confirms that the receiving system got a message and accepted or rejected it. MSA-1 carries AA for accepted, AE for an error or AR for a rejection, and the sender should retry or alert a person on anything other than AA.

Which identifiers link a lab order to its result?

The placer order number from the EHR, the filler or accession number from the lab, and the specimen ID on the barcode. The result message must carry them back exactly as received.

What is an unsolicited result in HL7?

A result sent to the EHR without a matching electronic order, for example a walk-in test. Many EHRs accept them into a separate inbox for a person to file; agree with your EHR vendor how they are handled.

Sources and further reading

Take it with you

The buyer's guide, in your inbox.

Nine pages on what POCT connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier.

Get the POCT connectivity buyer's guide

Nine pages, vendor-neutral: what connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier. The PDF also opens directly from the downloads page; leave an email only if you want it in your inbox.

We use your email only to send the guide and, if you ask, to follow up once. No newsletter unless you tick the box. See our privacy notice.

Thank you. The guide is on its way. You can also open it now.
That did not send. Open the guide directly or email contact@catenix.com.

See it done in software.

A 30-minute walkthrough on a live tenant, with your analysers and your allowable-error limits.