🎉 Now from ₹299/month — full LIS, analyser integration and WhatsApp reports. See plans

How analyser–LIS integration works

Integration means the numbers a machine produces write themselves into the right report against the right patient, so staff verify results instead of re-typing them. Here is what sits between the test order and the signed report.

“Analyser integration” or “instrument interfacing” is the link between a laboratory analyser — a haematology counter, a biochemistry system, an immunoassay analyser — and the laboratory information system. Done well, a technician loads the sample, the machine runs it, and the result appears in the patient’s report ready for a pathologist to review. No USB stick, no manual entry, no transcription error.

The pieces involved

  • The LIS, which holds the order: which tests are pending for which sample.
  • A connector — a small piece of software (sometimes called a driver, an agent or middleware) that speaks the analyser’s protocol on one side and the LIS on the other. It usually runs on a PC next to the machine.
  • The analyser itself, configured to send results to a host.
  • A transport: either a serial cable (RS-232) for older instruments or a network connection (TCP/IP) for newer ones.

The flow, step by step

  • Order and accession. The test is booked in the LIS. The sample gets an accession number and, usually, a barcode label.
  • The worklist. The pending tests for that analyser become a worklist. In a host-query (bidirectional) setup, the analyser scans the tube barcode and asks the LIS “what do I run on this sample?”; the LIS answers with the test list. In a simpler unidirectional setup, someone selects the tests on the analyser and it just sends results back.
  • The run. The analyser processes the sample and produces results.
  • The result message. The analyser sends a message back — in HL7 or ASTM — carrying the sample ID, each analyte, its value, units and any instrument flags.
  • The match. The connector matches the message’s sample ID to the open accession in the LIS and writes each value into the right test.
  • Ranges and flags. The LIS applies reference ranges for the patient’s age and sex, marks high / low / critical, and can run delta checks against the patient’s previous results.
  • Validation. A technologist does the technical review; a pathologist or authorised scientist does the medical review and releases the report. Only then does it go to the patient.

What happens when a result has no match

A well-built integration holds an unmatched result rather than guessing. If the machine reports a sample ID the LIS does not recognise — a mislabelled tube, a sample registered on the wrong day, a typo in a manual entry on the analyser — the value sits in a review queue for a human to resolve. Nothing is written against a patient the machine did not clearly identify.

Where a person still signs

Integration removes the typing, not the judgement. Instrument flags, a haemolysed sample, a result that contradicts the patient’s history, a QC failure earlier in the run — these are why a qualified person reviews and signs every report. The value of integration is that the reviewer is checking numbers, not re-keying them.

For how Raydian LIS does this in an Indian lab — including on an unreliable connection — see the analyser integration page.

Seeing how a modern LIS handles this?

Raydian LIS is an analytics-led laboratory information system for Indian pathology and diagnostic labs — billing, analyser integration, signed reports, WhatsApp delivery and owner dashboards in one system, from ₹299 a month.

See what it does · Book a demo · Compare the options