Home / Insights / Connectivity
How to connect a lab analyzer to a cloud EHR in a small CLIA lab
What sits between a benchtop immunoassay, chemistry or hematology analyzer and a cloud EHR, how orders and results move, where QC and the audit trail fit, what to ask a vendor, and a realistic plan for going live.
Written and reviewed by the Catenix team. How these guides are written and checked.
In brief
- Most benchtop analyzers, including the Tosoh AIA-900 and AIA-360, talk to a host computer over ASTM E1381/E1394 or HL7 v2 on a serial or network port, and a cloud EHR cannot listen on that port, so a piece of middleware has to sit in between.
- A serial device server can put an RS-232 analyzer on the network, but only one host can hold that connection at a time, so the old LIS PC, a test laptop and the new middleware cannot all be connected at once.
- Orders come from the EHR as HL7 ORM messages or through a REST or FHIR ServiceRequest, and the specimen ID printed on the tube barcode is the single link between the order, the analyzer run and the result.
- Results go back as HL7 ORU messages or through the EHR's results API, and corrected results need their own tested path; whether results auto-release or wait for review is a lab director decision that must be validated before go-live.
- QC runs must be identified and filed as QC, never as patient results, with Levey-Jennings charts and Westgard rules, and the whole chain should carry an audit trail and sit under a HIPAA business associate agreement.
Take it with you: POCT connectivity buyer's guide · POCT readiness checklist (PDF, no form).
Why the analyzer and the EHR cannot talk directly
A small CLIA lab, for example a physician office laboratory, a fertility or endocrinology practice, or an urgent care group with its own testing room, often runs one or two benchtop analyzers: an immunoassay system such as the Tosoh AIA-900 or AIA-360, a chemistry analyzer, a hematology counter. The electronic health record (EHR) is usually cloud hosted. The question that follows is simple: how do the tests ordered in the EHR reach the analyzer, and how do the results get back into the chart without someone typing them?
The analyzer was built to talk to a host computer sitting next to it. Most benchtop systems use one of two families of standards:
- ASTM E1381 and E1394, now maintained by the Clinical and Laboratory Standards Institute (CLSI) as LIS1 and LIS2. E1381 defines the low-level link (how bytes are framed, acknowledged and checked), and E1394 defines the records: header, patient, order, result, comment and terminator. Our ASTM E1381/E1394 guide walks through a real message.
- HL7 v2 (Health Level Seven, version 2), the common language of clinical systems, usually carried over TCP/IP using MLLP (Minimal Lower Layer Protocol) framing.
These run over an RS-232 serial cable or a TCP connection on the local network. A cloud EHR lives in a data center elsewhere. It does not open a serial port in your lab, it will not accept an inbound ASTM session from your analyzer, and many cloud EHRs do not offer an HL7 lab interface at all, or offer one only at extra cost through a third-party interface engine. What they more often expose is a REST API (an application programming interface reached over HTTPS), sometimes built on FHIR (Fast Healthcare Interoperability Resources).
So something has to sit in the lab, speak the analyzer's protocol on one side and the EHR's interface on the other, and keep a record of everything that passed through. That something is middleware, sometimes called an instrument interface or a lightweight LIS (laboratory information system). For a lab that does not need a full LIS, middleware alone is often enough.
The physical connection: serial ports, device servers and one host at a time
Many benchtop analyzers still have only an RS-232 serial port for host communication. The AIA-900 is one of them. There are two common ways to reach it:
- A PC in the lab with a serial port (or a USB-to-serial adapter) running the middleware's local gateway.
- A serial device server, a small box of the Lantronix type that takes the serial cable on one side and presents it as a TCP port on the network. The gateway then connects to that TCP port from anywhere on the local network.
Whichever you use, remember one rule: only one host can hold the connection at a time. A serial port has one other end. A device server usually accepts a single TCP client per serial port, and the analyzer itself expects one host. If the old LIS PC, a vendor service laptop or a test tool is still connected, the new middleware will connect and receive nothing, or messages will be split between two hosts with neither getting a complete picture. Before go-live, list every system that currently talks to the analyzer and decide which one will stop.
Get the serial settings right on both ends: baud rate, data bits, parity, stop bits and flow control must match exactly. A mismatch usually shows up as garbled characters or as an analyzer that sends one frame and then waits forever for an acknowledgment. Analyzers with a native network port avoid the device server, but the same one-host rule usually applies to their host connection.
The local gateway should also store and forward: if the internet link drops, results are held on site and sent when the connection returns, in order, without duplicates. A cloud EHR outage should never turn into a lost result.
Getting orders from the EHR to the analyzer
Sending results is half the job. The other half is making sure the analyzer runs the tests the provider ordered, without a technologist selecting them by hand on the analyzer screen. That is where most transcription and wrong-test errors start.
How the order leaves the EHR
EHRs that support an HL7 lab interface send an ORM message (order message; some newer interfaces use OML) when a lab test is ordered. Cloud EHRs without an HL7 feed may instead let the middleware read orders through their API, for example as FHIR ServiceRequest resources or the vendor's own order endpoint. Either way, the middleware needs the patient identity, the specimen ID, the ordered tests and the ordering provider.
How the analyzer gets its work
There are two patterns:
- Host query. The analyzer reads the tube barcode and asks the host what to run for that specimen ID. The middleware looks up the order and answers with the test codes. The AIA-900 supports this when query to the host is enabled and tubes are loaded in barcode mode; see our Tosoh AIA-900 connection page for the settings that matter.
- Worklist download (broadcast). The middleware pushes orders to the analyzer in advance, and the analyzer matches them when the tube is loaded.
Host query is usually more robust for small labs, because the analyzer always asks for the current order, including late additions and cancellations.
The barcode is the link
The specimen ID printed on the tube label is what joins the EHR order, the analyzer run and the result. Decide early where that ID comes from: the EHR's accession number, a label printed by the middleware, or a pre-printed label scanned at collection. Then check what each analyzer can read. Some analyzers accept only a limited number of characters in the sample ID field, or only certain barcode symbologies, so a long EHR accession number may be truncated or rejected. Test real labels from your printer on every analyzer before go-live, including the shortest and longest IDs your EHR will produce.
Test code mapping
The analyzer knows tests by its own codes (on the AIA-900, the site's test file numbers). The EHR has its own order codes, and may use LOINC (Logical Observation Identifiers Names and Codes) for results. Someone has to build and sign off the map between them, test by test, including units.
Getting results back into the chart, including corrections
When the run finishes, the analyzer sends the result to the host. The middleware matches it to the order by specimen ID, checks that the patient and test agree, applies the release rules, and files it in the EHR.
- HL7 ORU (observation result) messages are the standard route where the EHR has an HL7 results interface. Each result carries the value, units, reference range, abnormal flag, result status, the performing lab and the time.
- The EHR's REST or FHIR API is the route for cloud EHRs without an HL7 feed. Results may be posted as FHIR Observation and DiagnosticReport resources, or through a vendor-specific lab results endpoint. Find out early whether results land as structured discrete values (which can be trended and alerted on) or only as a document attached to the chart.
Corrected results
Corrections happen: a hemolyzed sample is rerun, a calibration problem is found after release, a result was filed to the wrong order. CLIA expects the lab to notify the ordering provider promptly of a corrected report and to keep both the original and the corrected result (42 CFR 493.1291(k)). Your interface must send a correction that the EHR displays as a correction, for example an ORU with a corrected result status in HL7, or an amended Observation in FHIR, and not as a second, separate result that a provider might miss. Test this path before go-live with your EHR, not just the normal one.
Unmatched and pending results
Every interface produces some results that cannot be matched: a mislabeled tube, an order cancelled after collection, a rerun with a typed ID. The middleware should hold these in a visible queue for a person to resolve, never drop them and never guess. Results the analyzer flags as pending or incomplete should be held or sent according to a written lab policy.
Release rules, QC and what CLIA expects
Manual review or auto-release
The middleware can hold every result for a technologist to review and release, or release results automatically when defined conditions are met: QC in, no analyzer error flags, value inside a defined range, no delta check failure. Which tests can auto-release, and under what conditions, is a decision for the laboratory director, written into the procedure and validated before use. Validation means running known cases through the rules, including ones that should be held, and keeping the record. Software can apply the rules consistently; it should not decide what they are.
QC filed as QC
Control samples run on the analyzer must be identified as QC and filed against the control lot and level, never sent to the EHR as patient results. On many analyzers that means a distinct sample ID range or a control flag in the message, and on some it means a setting so controls are uploaded to the host at all. Once QC arrives electronically, the middleware can plot Levey-Jennings charts and apply Westgard multi-rules automatically, and hold patient results for a test when its QC fails. Our Levey-Jennings and Westgard guide explains the rules.
CLIA moderate and high complexity, at a high level
Most benchtop immunoassay, chemistry and hematology testing is categorized by the FDA as moderate or high complexity, so the lab holds a CLIA Certificate of Compliance or Certificate of Accreditation, not a Certificate of Waiver. The rules at 42 CFR Part 493 then apply in full. Those most relevant to an interface are:
- Quality control (493.1256): for most quantitative tests, at least two levels of control each day of testing unless the lab uses an approved individualized quality control plan (IQCP), with results reviewed and acted on before patient results are reported.
- Test reports (493.1291): reports must carry the required elements and go to the right person, and the lab must verify that results transmitted to the EHR arrive accurately and completely.
- Records (493.1105): QC, test and report records kept for at least two years, longer for some record types and under some state rules.
- Verification: the interface itself is part of the reporting system and should be validated, with evidence that what the analyzer produced is what appears in the chart.
Accrediting organizations such as CAP and COLA have checklist items on interface validation and periodic checks of transmitted results. Confirm the current wording with your accreditor.
Audit trail and HIPAA
Every step in the chain should leave a record: order received, specimen ID matched, query answered, result received, QC applied, result held or released and by whom, result sent, EHR acknowledgment, correction issued. That audit trail is how you answer an inspector, a provider asking why a result is late, or your own investigation after an error. It should be tamper-evident and keep the raw messages, not just a summary.
Any vendor whose system stores or transmits protected health information on your behalf is a business associate under the HIPAA Privacy and Security Rules, and needs a signed business associate agreement (BAA) before live data flows (45 CFR 164.502(e) and 164.504(e)). Ask where data is hosted, how it is encrypted in transit and at rest, who at the vendor can access it, how access is logged, and what happens to your data if you leave. The HIPAA Security Rule's audit control standard (45 CFR 164.312(b)) is a useful reference for what logging to expect.
What to ask a vendor, and a realistic go-live plan
| Ask | Why it matters |
|---|---|
| Have you connected this analyzer model before, with host query, and can you show a sample message? | A driver that only receives results will leave staff typing orders at the analyzer. |
| How do you exchange orders and results with our EHR: HL7, FHIR or its REST API? | Some cloud EHRs have no HL7 lab interface; you need a route the EHR actually offers you. |
| How are corrected results sent and displayed? | A correction that looks like a new result is a patient safety risk. |
| How is QC identified, charted and used to hold results? | QC must never reach a chart and must stop release when it fails. |
| What happens when the internet or the EHR is down? | Results should queue on site and send later, in order, without duplicates. |
| Will you sign a BAA, and where is data hosted? | Required under HIPAA before live data flows. |
| What does validation evidence look like, and who produces it? | Your lab director signs it; the vendor should make it easy. |
A realistic plan for one or two analyzers and one cloud EHR is 4 to 8 weeks, most of it waiting on EHR interface access and validation, not software:
- Weeks 1 to 2: discovery. Analyzer models and software versions, current host connections, EHR interface options and credentials, specimen ID and label format, test list, BAA signed.
- Weeks 2 to 3: physical and analyzer setup. Gateway PC or device server installed, serial settings matched, host query and QC upload enabled, old host disconnected.
- Weeks 3 to 5: build. Test code and units mapping, EHR order and result routes in a test environment, QC rules and release rules drafted by the lab director.
- Weeks 5 to 7: validation. Run real samples and controls, compare analyzer printouts with what lands in the EHR, test corrections, unmatched specimens, long and short barcodes, and an internet outage. Record everything.
- Weeks 7 to 8: go-live. Director sign-off, staff trained, parallel checks for the first days, a named person watching the unmatched queue.
Where software helps
The middleware is the piece that makes the rest of this manageable: one place where orders, analyzer traffic, QC, release decisions and the EHR acknowledgment are tied together by specimen ID and recorded. Look for a local gateway with store and forward, real host query support for your analyzer, QC with Levey-Jennings and Westgard, configurable release rules, an unmatched results queue and a complete audit trail.
Catenix is connectivity and quality software built for this job. It is designed and ready to connect over open standards, ASTM E1381/E1394, HL7 v2, FHIR and REST, to EHRs that accept them or offer a results API, and it runs a local gateway that answers analyzer host queries with the EHR's orders. See how it works for small labs connecting analyzers to an EHR. Catenix records and routes results; it does not interpret them.
Questions people ask
What middleware connects a benchtop immunoassay or chemistry analyzer to a cloud EMR for a small CLIA lab?
You need middleware with a local gateway that speaks the analyzer's protocol, usually ASTM E1381/E1394 or HL7 v2 over serial or TCP, and the EHR's interface, usually HL7 or a REST or FHIR API. For a small CLIA lab it should also answer host queries with EHR orders, file QC separately with Westgard rules, hold results that fail release rules, and keep an audit trail under a HIPAA business associate agreement.
We have a Tosoh AIA-900 and a cloud EHR. How do we get the analyzer to pick up the tests ordered?
Enable query to the host on the AIA-900, load tubes in barcode mode, and put middleware between the analyzer and the EHR. When a tube is read, the AIA-900 asks the host what to run for that specimen ID, and the middleware answers with the tests ordered in the EHR. The AIA-900 uses RS-232 serial, so a lab PC or a serial device server provides the connection.
Our cloud EHR doesn't have an HL7 lab interface. Can we still send analyzer results into it?
Often yes. Many cloud EHRs expose a REST API, sometimes based on FHIR, that can accept lab orders and results. Middleware can read orders and post results through that API instead of HL7. Check with the EHR whether results land as discrete values or as an attached document, whether API access carries a fee, and how corrected results are shown before you commit.
Can two computers connect to the same analyzer through a Lantronix serial server?
Usually not usefully. A serial port has one other end, most serial device servers accept a single client per port, and the analyzer expects one host. If an old LIS PC and new middleware both try to connect, one gets nothing or messages are split between them. Decide which host owns the analyzer and disconnect the other before testing.
Should analyzer results auto-release to the EHR or wait for a technologist to review them?
That is the laboratory director's decision. Many labs start with manual review for every result, then allow auto-release for selected tests when QC is in, no instrument flags are present and values fall inside defined limits. Whatever rules you choose must be written into the procedure and validated with known cases, including ones that should be held, before they are used on patient results.
How long does it take to connect a lab analyzer to an EHR?
For one or two analyzers and one cloud EHR, plan on roughly 4 to 8 weeks. The software setup is quick; the time goes on getting EHR interface access, matching analyzer settings, mapping test codes, and validating orders, results, corrections and QC handling with real samples. Anyone promising a few days is usually leaving out validation, which CLIA and your accreditor will expect to see.
Sources and further reading
- 42 CFR Part 493, Laboratory Requirements (CLIA)
- CMS, Clinical Laboratory Improvement Amendments (CLIA)
- CLSI LIS1 (formerly ASTM E1381) and LIS2 (formerly ASTM E1394), laboratory instrument to computer communication
- HL7 Version 2 messaging standard, ORM and ORU messages
- 45 CFR Parts 160 and 164, HIPAA Privacy and Security Rules, including business associate requirements
- CAP, Laboratory Accreditation Program
Read next
More for coordinators.
Connecting a Tosoh AIA-900 to your LIS or EHR
Connect a Tosoh AIA-900 to your LIS or EHR: ASTM host query so barcoded tubes pick their tests from the order, QC filed separately, results matched...
Read →Lab analyzer to EHR for small labs
Connect benchtop chemistry and immunoassay analyzers to your EHR: orders select the tests, failed QC holds results, every step is audited. Set up...
Read →Catenix in the United States
Point-of-care connectivity for US urgent care, physician offices and multi-site clinics: analyzer results into athenahealth, eClinicalWorks, Epic and...
Read →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.
See it done in software.
A 30-minute walkthrough on a live tenant, with your analysers and your allowable-error limits.