HL7 ASTM lab analyzer integration, explained plainly

What HL7 and ASTM actually are

HL7 (Health Level Seven) and ASTM (from ASTM International, the standards body that originally published it for laboratory instruments) are both message formats: agreed structures for describing "here is a sample, here is the test to run on it" and "here is the result for that sample and that test." Neither one is a piece of software you buy. They are a shared vocabulary that lets an analyzer built by one manufacturer and an LIS built by a completely different company understand each other without a person typing the number in between.

ASTM E1394 (and its newer relative, LIS2) is the format most laboratory analyzers have spoken for decades: chemistry analyzers, haematology counters, coagulation analyzers and similar bench equipment. HL7 is broader and more common in hospital and radiology systems, and increasingly appears on newer lab instruments too. Neither format is objectively "better." What matters for a buyer is simply which one a given analyzer actually speaks, and whether the LIS on the other end speaks it back.

Connecting analyzers to LIS: how the interface actually works

At a basic level, connecting analyzers to LIS is a conversation with two directions, and it is worth knowing both, because vendors sometimes deliver only one and still call it "integration."

1. LIS sends order (host query)
2. Analyzer runs the sample
3. Analyzer sends result message
4. Result lands on the patient record

A "host query" interface is the fuller version: the analyzer asks the LIS which test to run for a given sample barcode, and the LIS answers automatically, so the technician never has to key the order into the analyzer by hand. A "results-only" interface is more limited: the technician still enters the order on the analyzer itself, but the finished result flows back into the LIS automatically instead of being retyped. Both remove manual result entry. Only host query also removes manual order entry on the analyzer side, which is where a busy lab actually loses time and makes transcription mistakes on a high-volume shift.

The point of any interface is a number that never gets typed twice.

Underneath either pattern sits a piece of software often called a "driver" or "middleware": code written for that specific analyzer model that translates its particular dialect of HL7 or ASTM into whatever the LIS expects, and back again. This is the part vendors sometimes skip past in a sales conversation. A driver is usually built and priced per analyzer model, not delivered as one generic "HL7 support" checkbox that instantly works with every machine in your lab.

HL7 vs ASTM vs RS232: the interfacing standards, compared

These three terms get used almost interchangeably in sales conversations. They are not the same kind of thing, and knowing the difference is what lets you ask a sharper question.

A practical consequence: an older analyzer connected by RS232 usually needs a physical serial cable run to wherever the LIS server or interface box sits, while a networked instrument just needs to be on the same network as the software. Ask which connection your specific analyzer models use before assuming either is possible without extra cabling or hardware.

Why HL7 ASTM lab analyzer integration matters for a lab

The case for it is straightforward and worth stating without exaggeration. Manual result entry, someone reading a number off an analyzer's screen or printout and typing it into the LIS, is slow at volume and is exactly where transcription errors creep in: a digit transposed, a decimal point missed, a result attached to the wrong patient in a busy batch. A working interface removes that step for the tests it covers, which usually means faster turnaround time and one less place for a wrong number to enter a report.

It is not, on its own, a substitute for the rest of what an LIS needs to do correctly with that result once it arrives: applying the right age- and gender-specific reference range, flagging it Low, Normal or High, routing it through approval, and getting it to the patient. Analyzer integration solves one specific problem (getting the number in without retyping it). The result-handling logic around it is a separate thing to evaluate, covered in our LIS features checklist.

What to demand from any LIS before you buy

Whether or not analyzer interfacing is on your list today, these are the questions that separate a real interface from a marketing checkbox, for any vendor you talk to:

• Bidirectional or results-only? Ask explicitly whether the order goes to the analyzer automatically (host query) or whether staff still key it in on the machine and only the result comes back.
• Which exact analyzer models are supported today? "HL7 support" is not a yes/no feature. Get the specific make and model list, not a general capability claim.
• Who builds and maintains the driver, and what does it cost? Per-analyzer interface work is usually a separate, priced project. Ask for that number before comparing headline software prices across vendors.
• What happens when the interface goes down mid-shift? Every interface can fail. Ask what the fallback is: manual entry as a backstop, or a full stop until it's fixed.
• Who owns the mapping between analyzer test codes and your LIS test catalogue? A mismatch here is a common, quiet source of a result landing against the wrong test name.
• Does the LIS run on the cloud or on-premise, and does that change what analyzer connections are possible? A cloud LIS can usually still take a network (TCP/IP) analyzer feed through a local interface box; a purely serial (RS232) analyzer may need extra hardware either way. See our comparison of cloud vs on-premise lab software for how that choice plays out beyond just analyzer connections.

These questions apply whether you are evaluating a large multi-analyzer reference lab setup or a small lab with one or two instruments. The scale changes; the questions don't.

Where analyzer interfacing fits in choosing an LIS overall

Analyzer connectivity is one line item in a much longer evaluation, and it should not crowd out the rest of it. Reference ranges, result flagging, report approval, billing, WhatsApp delivery and referral commissions are all things a lab uses every single day, on every test, whether or not that test came off an interfaced analyzer. Our lab information system page covers what a modern LIS should handle end to end, and our pillar guide on choosing a laboratory information system walks through the fuller evaluation, of which analyzer interfacing is one part, not the whole decision.

Browse more guides for running a diagnostic lab in India →

Frequently asked questions

Related

• Choosing a laboratory information system: the pillar guide
• LIS features checklist: what to evaluate before you buy
• Cloud vs on-premise lab software
• HealthFlow's lab information system