A lab lives or dies on whether the right result reaches the right clinician at the right time. Here is what a Laboratory Information System does, the workflow it runs, and why it should not sit apart from the hospital record.
A Laboratory Information System, or LIS, is the software that runs a clinical laboratory. It takes a test from the moment it is ordered to the moment a verified result is delivered, and it keeps track of every step in between: the sample, the analyser, the quality control, and the report. Without it, a lab runs on register books, handwritten worksheets, and results read out over the phone, where a single transposed digit can change a clinical decision.
The LIS is one of the most operationally demanding parts of a hospital system, because a lab is a small factory. Samples flow in, machines process them, results flow out, and accuracy is not negotiable. This guide explains what an LIS actually does, the workflow it manages, and why the most important question is not what the LIS does on its own but how it connects to the rest of the facility.
An LIS exists to manage the lifecycle of a test. Follow one specimen and the stages become clear.
Around that core, an LIS also handles the things that keep a lab honest and running: reagent and consumable stock, turnaround time tracking, and an audit trail showing who did what and when. The acronym LIMS is sometimes used as well, and the two are not the same thing. We explain the distinction in LIS vs LIMS.
One detail surprises facilities buying their first LIS. Laboratory analysers do not speak the same language as hospital systems. Where the hospital side trades in standards like HL7 and FHIR, the instruments themselves typically communicate using laboratory protocols such as ASTM and LIS2-A2. An LIS has to handle these instrument protocols directly to pull results off the machines, and getting that connection right is much of the real engineering in a lab system.
A result that has to be read off a machine and typed into a system by hand is a result waiting to be entered wrong.
This matters when you evaluate products. A demo can show a tidy results screen while quietly assuming someone keys the numbers in. The question to ask is whether the LIS connects to your specific analysers and pulls results automatically, because that connection is where accuracy and speed are won or lost. For the wider standards picture, see our guide to FHIR and HL7.
Here is the most consequential question about any LIS: does it share the patient record with the hospital, or is it a separate system that has to be wired to one? Many labs run an LIS that is entirely separate from the hospital software. The result is a seam, and seams cost.
When the LIS is separate, an order placed by a doctor has to cross from the hospital system into the lab system, and the result has to cross back. That crossing is either a fragile integration that breaks, or a human re-typing the order and reading the result back over the phone. Either way, the doctor often ends up looking at a result on a different screen from the chart, or waiting while someone bridges the gap. When the LIS is one module of the same platform, the order and the result live on the same record, and the seam disappears. We make the full case in one platform versus separate hospital and lab systems.
For facilities across the continent, two requirements sit on top of the standard ones. The first is offline operation. A lab cannot stop accessioning samples or recording results because the network dropped, so the LIS has to keep working locally and sync when connectivity returns. The second is reporting. Lab data feeds disease surveillance and statutory returns, including to national platforms like DHIS2, so coded, structured results are far more useful than free text. We cover both in why offline-first matters and understanding DHIS2 reporting.
Veona includes a full laboratory as part of the platform rather than selling it as a separate system to integrate. The order and the result live on the same patient record the clinician already uses, so there is no seam between the consulting room and the lab. Analysers connect through the instrument protocols they actually speak, results come back without re-typing, and the platform is built offline-first so the lab keeps running through an outage. Results are coded and structured so they feed reporting cleanly. You can see how it works in our labs overview and how it sits in the wider platform in our platform overview.
The takeaway: an LIS is the system that carries a test from order to verified result, and its hardest jobs are connecting to analysers and not losing the result on the way back. The single biggest decision is whether it shares the hospital record or sits apart from it, because that seam is where labs lose time and trust.
We will walk a test through Veona, from order to verified result, with no seam between the clinic and the lab.