LIS Instrument Integration Guide: Plan, Test, Stabilize

Key takeaways

Start with the analyzers that produce the most results each day. That is where integration saves the most typing and errors.

Know whether each analyzer supports unidirectional or bidirectional interfacing before planning the workflow.

Map every parameter and unit, then validate with real samples before going live.

Plan for failure: when an interface stops, staff need a clear fallback so reporting continues.

What analyzer integration does

Analyzer integration (also called interfacing) sends results from the instrument straight into the LIS, so nobody has to read a printout and type values into a report. It removes transcription errors and saves technician time, which matters most on high-volume analyzers such as haematology cell counters and biochemistry analyzers.

Unidirectional vs bidirectional

There are two common setups, and the analyzer's capabilities decide which you can use.

Type	How it works	Best for
Unidirectional	Analyzer sends results to the LIS; tests are selected on the analyzer	Simpler setups and analyzers without host query support
Bidirectional	LIS sends the test order to the analyzer by barcode; analyzer returns results	High-volume labs that want to remove manual test selection too

Plan before connecting

Collect these details for each analyzer before any technical work starts. Missing information is the most common cause of integration delays.

Analyzer make, model, and software version
Supported protocol (commonly ASTM or HL7) and connection type (serial/RS-232 or network/TCP-IP)
Whether host query (bidirectional) is supported and licensed
The analyzer's interface manual or protocol document
The computer or device that will connect to the analyzer, and its location
The analyzer service engineer's contact, in case settings must be changed

Map and validate before go-live

Every analyzer parameter code must be mapped to the right test parameter in the LIS, with matching units and decimal places. Then validate with real samples: run them through the interface, compare the LIS values against the analyzer printout for every parameter, and check flags and reruns behave as expected. Keep the validation records; accreditation assessors may ask for them.

Plan for interface failures

Interfaces can stop because of a loose cable, a network change, or an analyzer software update. Decide in advance how staff will know results have stopped arriving, who checks the connection, and how results are entered manually, with a second-person check, until the interface is restored.

Monitor after go-live

In the first weeks, compare a sample of interfaced results against the analyzer every day. After that, a weekly spot check and a review of any results that failed to transfer keep the interface reliable. Re-validate after any analyzer software update or parameter change.

Frequently asked questions

What is LIS analyzer interfacing?

A connection that sends results from a lab analyzer directly into the laboratory information system, so results don't have to be typed in by hand.

What is the difference between unidirectional and bidirectional interfacing?

In unidirectional interfacing the analyzer only sends results to the LIS. In bidirectional interfacing the LIS also sends test orders to the analyzer, usually by sample barcode, so tests don't have to be selected on the analyzer.

Which analyzers should a lab integrate first?

Start with the analyzers that produce the most results per day, typically the haematology cell counter and the biochemistry analyzer, because that is where manual entry costs the most time and causes the most errors.