Which solutions can connect multiple laboratory instruments to an LIS?

A growing lab rarely has one machine. A typical diagnostic centre runs a haematology analyser, a chemistry analyser, an immunoassay analyser for hormones, an electrolyte analyser and perhaps a urine analyser, often from four different makers. Typing every result from all of them into the report is slow and error-prone, so the question becomes: what can connect them all to one laboratory information system (LIS)?

There are five kinds of solution. They all depend on the same two things: each analyser’s host interface (usually ASTM or HL7) and barcoded samples, so a result can be matched to the right patient. If those terms are new, start with our guide to lab analyser integration.

1. An LIS with built-in instrument drivers

Some laboratory systems ship with their own drivers for common analysers. You connect each machine directly to the LIS (or to a small service the LIS runs on a lab PC), map the test codes, and results flow into the report.

• Suits: diagnostic centres and hospital labs with a handful to a dozen machines.
• Strengths: one system, one vendor to call, no middleware licence.
• Watch for: the driver list. Ask for every one of your models by name and software version, and how long a new driver takes.

2. Middleware from the analyser maker

Large analyser makers sell middleware that sits between their machines and the LIS. It handles their instruments very well, including automation lines, reruns and auto-verification rules, then sends finished results to the LIS.

• Suits: large labs with many machines from one maker, or a sample automation line.
• Strengths: deep control of that maker’s instruments.
• Watch for: cost, and machines from other brands, which may still need a separate connection.

3. Independent instrument middleware

Independent middleware products connect many brands of analyser and pass results to any LIS. They often add quality-control tracking and rules for auto-verification.

• Suits: big or reference labs with mixed brands and an LIS that lacks drivers.
• Strengths: one hub for many brands.
• Watch for: another system to license, maintain and support, plus the LIS interface on top.

4. A general HL7/ASTM integration engine

Large hospitals often run an integration engine that moves HL7 messages between all their systems. It can also route lab orders and results between analysers or middleware and the LIS.

• Suits: hospitals with an IT team and many systems to join.
• Strengths: flexible, handles far more than the lab.
• Watch for: it is a toolkit, not a ready lab solution. Someone has to build and maintain every interface.

5. A lab connector for a cloud LIS

Analysers talk to a computer beside them, not to the internet. A cloud LIS therefore uses a small lab connector app on a PC in the lab. The connector talks ASTM or HL7 with each analyser and passes results securely to the cloud LIS:

Analysers ⇄ (serial or network) ⇄ Lab connector PC ⇄ (secure internet) ⇄ Cloud LIS

• Suits: diagnostic centres, clinics and hospital labs using cloud software, with mixed brands.
• Strengths: one PC serves several analysers; code mapping and logs in one place; no middleware licence.
• Watch for: the PC needs a UPS, and someone should glance at the connector status each shift.

Comparing the options

Option	Typical lab	Mixed brands	Extra system to run	Relative cost
LIS with built-in drivers	Small to medium	Yes, if drivers exist	No	Low
Vendor middleware	Large, one maker	Limited	Yes	High
Independent middleware	Large, many brands	Yes	Yes	Medium to high
Integration engine	Large hospital	Yes, with build work	Yes	High (staff time)
Lab connector + cloud LIS	Small to large	Yes, if drivers exist	A small app	Low

Questions to ask any vendor

• Which of my analysers (brand, model, software version) do you support today?
• One-way or two-way for each? Two-way lets the analyser fetch tests by barcode.
• How long does a new driver take if a model is missing?
• Who does the test-code and unit mapping, and how is it checked?
• Do analyser flags and comments come through to the technologist?
• Are results held as pending verification until a pathologist or authorised technologist signs off?
• How is a missing result traced? Is every message logged?
• What is the price per analyser, and are there setup fees?

How Hospify Pro connects several analysers

Hospify Pro uses option 5. The Hospify Pro Lab Connector runs on a Windows PC in your lab and connects your analysers over serial or network, using ASTM or HL7. One PC can serve several machines.

• Results arrive matched by the sample barcode printed at billing.
• Each machine’s codes are mapped to your report parameters and units.
• Results wait as pending verification; nothing reaches a patient until it is verified and the report is locked.
• Every message is logged, so a missing result can be traced.
• Support for each model is confirmed during onboarding, and new drivers can be added on request.

The Lab Connector is Tk 2,000 a month$49 a month per connected analyser, on top of the Diagnostic plan or Hospital plan. See laboratory features, or book a demo and send us your analyser list.

Checklist

• List every analyser: brand, model, software version, serial or network port.
• Confirm each has a host interface and that it is enabled.
• Barcode labels from your LIS that every analyser can read.
• Choose the option that fits your size and brands.
• Plan a few days of parallel testing per machine before going live.