Most laboratories do not start with software. They start with a register, a set of printed request forms, and a WhatsApp group. That works — until roughly the point where you cannot answer "where is Mrs. Bibi's CBC?" without walking to the bench and asking someone.
A laboratory information system (LIS) is the software that removes that question. It records every sample, tracks its state, holds the results against the correct reference ranges, enforces who is allowed to approve them, and produces the report. Everything else an LIS does is built on top of that spine.
What an LIS actually does
It is easy to be sold a feature list. It is more useful to think about the four jobs an LIS has to do well, because a system that is weak at any one of them creates manual work everywhere else.
1. Identify the sample, unambiguously
Every downstream problem in a lab traces back to sample identity. The LIS assigns an accession or lab number at registration, ties it to the patient and the requested tests, and — ideally — prints it as a barcode. Once a tube carries a barcode, "which sample is this?" stops being a question anyone has to answer from memory.
2. Track state over time
At any moment a sample is registered, collected, received, in progress, resulted, verified, or dispatched. An LIS that records those transitions with timestamps gives you two things at once: an answer for the patient at the counter, and turnaround-time data you can actually act on.
3. Hold results against the right reference ranges
A haemoglobin of 11.5 g/dL means different things for an adult man, a pregnant woman, and a six-year-old. A competent LIS stores reference ranges by test, and varies them by age and sex where clinically appropriate, then flags values that fall outside. That flag is not a diagnosis — it is a prompt for a human to look.
4. Enforce verification before release
The step that separates a lab system from a spreadsheet is that a result cannot reach a patient until a qualified person has released it. The LIS should record who verified what, and when, and should make it impossible to skip that step by accident.
LIS vs LIMS — is there a difference?
The terms are used interchangeably in day-to-day conversation, and vendors are not consistent. There is a rough distinction worth knowing:
| LIS | LIMS | |
|---|---|---|
| Typical setting | Clinical / diagnostic labs | Research, industrial, QC, environmental labs |
| Organised around | The patient and their report | The sample, batch or experiment |
| Core output | A clinical report for a patient or doctor | Analytical data, batch records, compliance evidence |
| Usually needs | Billing, referring doctors, report delivery | Protocol versioning, chain of custody, instrument runs |
If you run a pathology or diagnostic lab and someone offers you a "LIMS", it may still be the right product — but check that it does patient-facing reporting and billing properly, because those are often thin in systems designed for research.
The modules that matter in a clinical lab
- Registration and billing — patient details, test selection, price, discount, and what was actually collected. If billing lives in a separate system, reconciliation becomes a daily chore.
- Test catalogue — your own list of tests with parameters, units, reference ranges and prices. You should be able to edit this yourself without calling the vendor.
- Sample tracking — barcodes and state transitions, as above.
- Result entry — structured fields for numeric results, free text for narrative reports such as histopathology or radiology, and calculated fields for panels that derive values.
- Verification and e-sign — with the pathologist's name and credentials appearing on the released report.
- Report delivery — a branded PDF, and a way to get it to the patient without them coming back to the counter.
- Reporting on the business — daily collection, test volumes, referring doctor share, turnaround times.
Turnaround time is the metric worth watching
If you measure one thing, measure turnaround time (TAT) — the interval from collection to verified report, broken down by test.
TAT is useful because it is a symptom rather than a cause. When it drifts, the reason is usually specific and fixable: samples waiting for a batch to fill, a single analyser as a bottleneck, or results sitting entered-but-unverified because the pathologist only reviews in the evening. You cannot see any of that from a register, and you can see all of it from an LIS that timestamps its transitions.
A lab that knows its median TAT per test can make a promise to a referring doctor and keep it. That is a commercial advantage, not just an operational one.
How to tell you have outgrown paper
You probably need an LIS when more than one of these is true:
- Someone regularly has to physically look for a sample or a result.
- You cannot say what yesterday's total collection was without adding it up by hand.
- Reports are re-typed from a bench sheet into a template — a step that quietly introduces transcription errors.
- Patients or doctors phone to ask whether a report is ready.
- You have opened, or want to open, a second collection point.
- You cannot show who approved a given report six months ago.
That last one matters more than it seems. The day a result is questioned, an audit trail is the difference between a clear answer and an argument.
What to check before you buy
- Can you edit your own test catalogue? If adding a test means raising a support ticket, you will stop adding tests.
- Can you get your data out? Ask specifically for an export of patients and results in a standard format. A vendor who cannot answer this quickly is a vendor who is planning on lock-in.
- What happens when the internet drops? For a cloud system, ask what the lab does during an outage. There should be an answer, even if it is a manual one.
- Who can release a report? Check that roles are enforced server-side, not just hidden in the interface.
- Where does the data physically live, and who else can read it? Patient data has legal weight in most jurisdictions.
- What does year two cost? Licences, per-user fees, support contracts and paid add-ons frequently exceed the first-year price.
See a working LIS instead of a feature list
PathLab is our pathology lab system — registration, billing, result entry against reference ranges, pathologist verification, and branded PDF reports over WhatsApp and SMS. The software is free; you pay only for hosting. The demo is the real product with a live login, no sales call.
Read about PathLab See our LIS → Open the live demo →A note on scope creep
The most common mistake we see is buying a system sized for a lab three times larger, on the theory that you will grow into it. In practice, complexity has a running cost: more configuration, more training, more ways for staff to do the wrong thing. A smaller system your team actually uses correctly beats a comprehensive one they route around.
Start with the four jobs at the top of this article. If a system does those cleanly and lets you export your data, it will serve you for years.