Lab and imaging interfaces are among the highest-value integrations in any practice — and among the most common sources of support tickets. Done well, results flow directly into the chart, discrete and routed to the right provider. Done poorly, staff are faxing requisitions and manually scanning PDFs, and clinicians lose trust in whether the chart is complete. Because these feeds touch patient safety directly, they deserve more rigor than almost any other interface you manage. Here's how to get them right.
Understand the order-to-result flow
A bidirectional lab interface typically runs on HL7 v2. The EMR sends an order message (often ORM) to the lab; the lab returns results (ORU) that post back to the chart. Imaging follows a similar pattern, and reports may route through the same kind of result interface. A unidirectional (results-only) interface is simpler but pushes order entry back onto paper or a separate portal, so understand which model you are buying before you scope the build.
| Direction | Message | Carries |
|---|---|---|
| EMR → Lab | Order (ORM/OMG) | Patient, ordering provider, tests, diagnosis |
| Lab → EMR | Result (ORU) | Discrete results, reference ranges, flags |
Compendium mapping is the hard part
Mapping is tedious, detailed work, and it is tempting to rush it or accept the lab's defaults wholesale. Resist that. A panel that splits into the wrong component results, or a value that posts as free text instead of a trendable number, will not throw an error — it will simply produce a chart that looks fine but quietly loses its analytic value. Budget real time for a clinician or experienced analyst to review the mapping rather than treating it as a clerical task.
Set up result routing carefully
- Route results to the ordering provider's in-basket, with backup coverage rules for time off.
- Define how abnormal and critical results are flagged and escalated.
- Decide how unsolicited results (no matching order) are handled so they don't fall into a void.
- Confirm patient matching is reliable to prevent results posting to the wrong chart.
Test thoroughly before go-live
- Send test orders for a representative range of tests, including panels and reflex tests.
- Verify results post to the right patient, the right test, and as discrete data where expected.
- Confirm reference ranges, units, and abnormal flags display correctly.
- Test the failure cases: rejected orders, corrections, and canceled tests.
Don't skip the corrected-result case
A result that the lab later revises is one of the most dangerous edge cases. If a corrected ORU does not clearly replace the original in the chart — or worse, appears as a second result alongside the first — a clinician may act on outdated information. Make corrected and canceled results an explicit part of your test plan, and confirm the provider can tell at a glance which value is current.
Plan for ongoing maintenance
Compendiums change — labs add tests, retire others, and update codes. Establish a process with each lab to receive compendium updates and apply them under change control. An interface that's perfect at go-live drifts out of date without maintenance, and the drift is invisible until a clinician reports that a newly offered test cannot be ordered electronically.
Troubleshooting basics
When a result doesn't appear, check the interface engine logs first: did the message arrive, was it well-formed, did it match a patient and an order? Most "the EMR lost my result" tickets resolve to a mapping gap, a patient-match failure, or a routing rule — all of which you can diagnose with interface logs and a clear inventory of how each feed is configured. Keeping that inventory current is what turns a frantic outage call into a methodical ten-minute check.