Skip to main content
Contact

By Sakshi Shah · 18 November 2026 · 10 min read

Lab Instrument Integration: Getting Analyser Results Into Your LIS Reliably

Lab instrument integration explained: ASTM and HL7 interfaces, host query, code mapping, autoverification and validating results before go-live.

Introduction

In many diagnostic laboratories, at least some results still travel from analyser to report by hand. A technician reads values off an instrument screen or printout and types them into the laboratory information system (LIS). Orders are keyed into the analyser one sample at a time. It is slow, it ties up skilled staff, and every manual transcription is a chance for a wrong value, a swapped sample or a missed flag to reach a patient report.

Most modern analysers can send results to an LIS automatically, and many can receive orders from it too. Yet connecting them reliably is harder than a vendor brochure suggests: instruments speak older protocols over serial cables, every lab codes its tests differently, quality control results must be kept apart from patient results, and every link must be validated before a single patient result passes through it. This guide explains how lab instrument integration works, the decisions involved, the rules worth automating, and how to validate and run interfaces safely.

How Analysers Talk to an LIS

Instrument interfacing has its own set of established standards, and knowing which ones your analysers support is the first practical step.

The physical connection is either a serial cable (RS-232) on older instruments or a network (TCP/IP) connection on newer ones. Serial connections often need a small converter or a dedicated interface PC to reach the network.

ASTM protocols are the long-standing standard for clinical laboratory instruments. One standard defines how data is transmitted reliably at a low level (originally ASTM E1381), and another defines the content of the messages — header, patient, order, result and terminator records (originally ASTM E1394). These are now maintained by CLSI as LIS01 and LIS02, and many instrument manuals still refer to the ASTM names.

HL7 version 2 is common on newer instruments and middleware, using order messages to send requests and result messages (ORU) to return values — the same family of standards used elsewhere in hospitals, as covered in EMR Integration: Connecting Clinical Systems Without Replacing Them.

Point-of-care devices often use their own standard, POCT1-A, usually through a vendor's device management system rather than directly.

File exports — CSV or vendor-specific files written to a folder — are the fallback for instruments without a live interface.

Unidirectional or Bidirectional?

A unidirectional interface sends results from the analyser to the LIS; tests are still selected on the analyser by hand. A bidirectional interface also sends orders from the LIS to the analyser, which removes manual test selection and its errors entirely. The most common bidirectional pattern is the host query.

LISorder + sample ID(barcode label)Analyserreads barcode,runs tests1. host query: "which tests for sample 2041?"2. test list returnedInterface / middlewareseparate QC from patient resultsmap test codes and unitsdelta check vs previous resultcritical value alertsapproved autoverification rules3. results + flagsLIS: auto-releasedpasses all rulesScientist reviewanything flagged
With a host query, the analyser asks the LIS what to run, so nobody selects tests by hand. Results pass through rules that release routine values and send anything unusual to a scientist.

Bidirectional interfaces depend on reliable sample identification: barcode labels printed from the LIS at collection or reception, readable by every analyser. Getting labelling right — label size, barcode type, placement on tubes of different sizes — is often a bigger practical task than the software interface itself.

Mapping: Where Most Problems Hide

Each analyser has its own codes for tests, units, flags and sample types, and each LIS has its own. The interface must translate between them exactly. This mapping is where most errors occur, and where careful work pays off most.

Item to mapWhat can go wrongWhat to check
Test codesResult filed under the wrong test, or not filed at allEvery instrument code maps to exactly one LIS test; unmapped codes raise an error, never disappear
UnitsA value reported in different units from the LIS's reference rangeUnits match or are converted explicitly; reference ranges align
FlagsHigh, low, critical or instrument error flags lost in transferAll instrument flags carried through and visible to reviewers
Quality controlQC material results mistaken for patient results, or vice versaQC identified and routed to QC records only
Reruns and dilutionsA rerun result overwriting the original without trace, or a dilution factor not appliedReruns recorded with history; dilution handling defined per test
Sample identificationMisread or unrecognised barcodeUnrecognised IDs held for manual resolution, never guessed

Automating Rules — Carefully

Once results arrive electronically, rules can do much of the routine checking that scientists currently do by eye. Common examples include holding results when QC for that run has failed, flagging a result that differs sharply from the patient's previous result for the same test (a delta check), raising immediate alerts for critical values, and autoverification — automatically releasing results that meet strict, predefined criteria.

Autoverification can make a substantial difference to turnaround time and workload, letting scientists focus on the results that genuinely need judgement. But every rule is a clinical decision about which results can be released without a person looking at them.

Autoverification rules belong to the laboratory, not the software. Criteria should be defined and approved by laboratory leadership, validated against real results before use, documented for accreditation (such as ISO 15189 through NABL in India or UKAS in the UK), and reviewed whenever methods, analysers or reference ranges change.

Validating Before Go-Live

No patient result should pass through a new interface until it has been validated. A thorough validation typically includes:

  • every mapped test sent through the interface and compared with the analyser's own record — value, units, flags and sample ID;
  • a parallel run in which results are both interfaced and recorded manually, with every difference investigated;
  • deliberate edge cases: unknown barcodes, missing orders, reruns, dilutions, results above or below measuring range, instrument error flags;
  • failure scenarios: the cable unplugged or the network dropped mid-transmission, the LIS unavailable, duplicate transmissions;
  • a signed validation record, kept for accreditation and audit.
1

Inventory instruments

For each analyser: protocol, connection type, uni- or bidirectional support, interface manual and vendor contact.

2

Build and map

Connect one analyser, map every test, unit, flag and QC code, and agree the rules with lab leadership.

3

Validate

Test every code, edge case and failure scenario, run in parallel with manual entry, and sign off the record.

4

Go live and monitor

Watch connection status and message queues, keep a written downtime procedure, then move to the next analyser.

Running Interfaces Day to Day

Once live, an instrument interface is part of the laboratory's critical path and needs watching like one. Monitor whether each analyser is connected and sending, alert staff when results queue up or an analyser goes quiet unexpectedly, and keep a clear record of every message received and sent. Keep a written downtime procedure so that, if an interface fails, staff know exactly how to switch to manual entry with a second-person check — and how to reconcile once the interface returns.

This is the same discipline that applies to any device integration, whether laboratory analysers or factory machines, described in Getting Data Out of Old Factory Machines. The protocols differ; the principles of reading reliably, translating carefully, never losing data and monitoring constantly are the same.

Conclusion

Lab instrument integration removes manual transcription, shortens turnaround and frees skilled staff for the results that need them — but only if it is done with clinical care. Know which protocols each analyser supports, prefer bidirectional host query where possible and get barcode labelling right, map every test, unit, flag and QC code exactly, and treat autoverification rules as laboratory decisions that are approved, validated and documented. Validate thoroughly before go-live, then monitor every interface and keep a downtime procedure ready.

Results still re-typed from analysers into your LIS?

We will check what each of your instruments can send, and plan interfaces with mapping and validation built in. See our Device & Protocol Integration work or start the conversation.

Frequently Asked Questions

What is the difference between ASTM and HL7 for lab instruments?

ASTM protocols, now maintained by CLSI as LIS01 and LIS02, are the long-standing standard specifically for laboratory instruments. HL7 v2 is a broader healthcare messaging standard used by many newer instruments and middleware. Many labs use both, translating between them in an interface layer.

Can older analysers with only serial ports be connected?

Usually, yes. A serial-to-network converter or a dedicated interface PC can connect RS-232 instruments to the LIS, using the instrument's ASTM or vendor protocol.

What is a host query?

In a host query, the analyser reads a sample's barcode and asks the LIS which tests to run. The LIS replies with the test list, so tests do not need to be selected manually on the analyser.

Is autoverification safe?

It can be, when criteria are strict, defined and approved by laboratory leadership, validated against real results, documented for accreditation and reviewed whenever methods change. Results that do not meet every criterion should always go to a scientist.

How long does it take to interface an analyser?

It depends on the instrument, the protocol, vendor support and the number of tests. Mapping and validation usually take longer than the connection itself, and should never be rushed.

Further Reading