Lab interface volume: HL7 v2 traffic and the interfaces we build
A lab interface must carry every order, result, correction and ACK, and the busiest hour sets the size of the engine, the connections and the archive. Agnotic Technologies builds HL7 v2 lab interfaces to your requirements, sized from your own volumes.
Last reviewed by the Agnotic Technologies engineering team
How many HL7 v2 messages will a lab interface carry?
A lab interface carries an order and a result message for each order or each test, an ACK for every message, and an extra result message for each correction. Message grouping, corrections and the busiest hour decide the real load. Agnotic Technologies builds HL7 v2 lab interfaces sized from your LIS reports and interface engine logs.
Where do lab interfaces break?
Most lab interface trouble is a sizing or mapping gap that only shows up under real traffic.
Sized for the daily average
Results cluster at certain hours. An engine and MLLP connection sized for the average backs up in the busiest hour.
Slow ACKs that stall the feed
In HL7 v2 over MLLP, each message waits for its ACK. A slow receiver slows every result queued behind it.
Grouping mismatches
Some systems send one order message with several OBR segments; others send one message per test. A mismatch changes message and ACK counts and breaks parsing.
Corrected results shown twice
Corrected and amended results arrive as new result messages. A receiving system that does not recognise them can show two answers for one test.
Local test codes
Without a mapping to LOINC, each OBX carries a code only the sending lab understands, which blocks reporting and reuse.
Archives that outgrow the plan
CLIA requires test reports kept for at least 2 years and pathology reports for at least 10, so result rows build up for years.
What do we build for lab traffic?
Agnotic Technologies builds lab interfaces to your requirements, on the interface engine you run or on a new one. These are the features we typically build.
MLLP channels per connection
One channel per ordering system or lab, with ACK timeouts and resend rules sized from the busiest hour.
Order and result message mapping
Order and ORU result messages mapped to the agreed profile, such as the HL7 LRI guide for results sent to ambulatory EHRs.
LOINC mapping
Local test codes mapped to LOINC, so every OBX carries a standard observation identifier.
Corrected result handling
Result status tracked, so corrected and amended results replace the earlier value instead of appearing as a second result.
Backlog replay
Message history kept in the engine, so a feed can be replayed after an outage, with load tests that include a replay.
Result archive with retention rules
Storage sized from the OBX rows kept per day, with older results moved to cheaper storage after the agreed period.
Per-connection monitoring
Queue depth, ACK latency and rejected messages per connection, with alert thresholds for each sending system.
What does each count decide?
Each count answers a sizing question for the interface engine, the network or the database.
Messages per day
Interface engine capacity, log volume and how much message history the engine can keep for replay.
Busiest hour
Throughput per MLLP connection and how quickly a backlog drains after a connection drops and comes back.
ACKs
Acknowledgment timeouts and resend rules. Every message waits for its ACK, so slow ACKs slow the whole feed.
Per ordering system
Which connection gets its own monitoring and alert thresholds, starting with the system that sends the most.
OBX segments
The result rows your database writes each day, and the parsing load on every system that receives them.
Rows kept
Database and archive size over the retention period, and when older results can move to cheaper storage.
Order or test: why does message grouping matter?
Some interfaces send one order message with several OBR segments, one per test. Others send one message per test. The choice changes the message and ACK counts, but not the number of OBX result values.
Check the grouping in your interface specification before you size anything. The laboratory information system guide shows which HL7 v2 message carries each lab handoff.
Corrected and amended results are sent again as new result messages, so they add to the count. Lab integration services explains how receiving systems handle them.
How long must lab results be kept?
Under CLIA, a laboratory keeps or can retrieve a copy of each original report, including preliminary and corrected reports, for at least 2 years after reporting. Pathology reports are kept for at least 10 years (42 CFR 493.1105).
State law, accreditation and your own record policy may require longer. Size the archive for the longest period that applies, since it must hold every row for that long.
How does Agnotic build the interface?
See our HL7 v2 integration services for the engine and channel work.
Confirm the message profile with the lab and each ordering system, for example the HL7 LRI guide for results to ambulatory EHRs.
Map local test codes to LOINC so every OBX carries a standard observation identifier.
Set up one MLLP channel per connection, with ACK timeouts and resend rules sized from the busiest-hour count.
Load test above the busiest-hour figure, including a backlog replay after a simulated outage.
Monitor queue depth, ACK latency and rejected messages per connection after go-live.
Traffic beyond orders and results
Count these separately when you size a shared connection or the engine.
- Preliminary results sent before the final result.
- Reflex tests, add-on orders and cancellations.
- ADT feeds and patient queries that share the connection.
- Instrument traffic between analyzers and the LIS, which runs on separate interfaces.
- FHIR APIs that expose the same results to apps.
Which standards and rules apply to lab interfaces?
Each fact links to the HL7, LOINC or eCFR page it comes from.
HL7 describes its Version 2.x messaging standard as the workhorse of electronic data exchange in the clinical domain, built to move clinical data between a central patient care system and departmental systems.
Source: HL7 International, HL7 Version 2 product briefHL7 publishes the Laboratory Results Interface (LRI) as an HL7 Version 2.5.1 implementation guide for the US Realm, now in Edition 5.
Source: HL7 International, LRI implementation guide product briefLOINC provides a set of universal names and ID codes for identifying laboratory and clinical test results in HL7 observation report messages.
Source: Regenstrief Institute, LOINC FAQA CLIA laboratory must retain or be able to retrieve a copy of each original test report, including final, preliminary and corrected reports, for at least 2 years after the date of reporting (42 CFR 493.1105(a)(6)).
Source: 42 CFR 493.1105 (eCFR)
Trusted by global innovators
Which standards does Agnotic build healthcare software against?
HIPAA
Health Insurance Portability and Accountability Act
Protect PHI with privacy-first architecture, encrypted storage and transmission, strict access controls, and traceable audit logs.
GDPR
General Data Protection Regulation
Implement lawful consent flows, data minimization, retention controls, and secure processing for sensitive health data.
FHIR
Fast Healthcare Interoperability Resources
Enable standardized health data exchange across apps, care teams, and systems through standards-based FHIR APIs.
HL7
Health Level Seven International
Support enterprise-grade interoperability with HL7-based integrations for records, events, and clinical messaging workflows.
HITRUST
Health Information Trust Alliance
Align security programs to healthcare-specific control and risk management practices trusted by providers and ecosystem partners.
HITECH
Health Information Technology for Economic and Clinical Health Act
Design with breach notification readiness, digital record safeguards, and operational controls that support regulated care programs.
SaMD
FDA Software as a Medical Device
Plan software quality, traceability, and documentation pathways for products that may require SaMD review and submission.
MDR (EU)
Medical Device Regulation (European Union)
Prepare EU market-ready processes for risk classification, evidence tracking, and lifecycle governance under MDR expectations.
SAMHSA
Substance Abuse and Mental Health Services Administration
Apply confidentiality controls and consent-aware sharing models for behavioral and mental health data experiences.
Where should you go next?
- Laboratory information system developmentLIS software and the HL7 v2 messages behind each lab handoff.
- Medical laboratory instrument integrationAnalyzer and instrument connections to the LIS.
- Lab integration servicesOrder and result interfaces with reference labs, including corrected results.
- HL7 v2 integration servicesADT, ORM, ORU and MLLP interfaces on an interface engine.
- Laboratory management softwareSoftware for lab operations, quality and reporting.