Laboratory Information System for Hospitals: Barcodes, Analysers, NABL

A laboratory information system (LIS) manages everything that happens to a lab test after a doctor orders it: sample collection, barcoding, transport, processing on analysers, result entry, validation, reporting and billing. In a hospital, the LIS is also the link that sends results back to the doctor's screen and the patient's record without anyone carrying paper.

Many hospital labs in India still run a hybrid: orders on paper slips, sample tubes labelled by hand, results typed from analyser printouts, and reports printed for the ward to collect. Each manual step adds delay and a chance of error. Transcription mistakes and mislabelled samples are among the most serious risks in any lab.

This guide covers how a hospital LIS should work end to end, why sample barcoding and analyser interfacing matter most, what to track for turnaround time, and what NABL assessors expect your system to show.

The hospital lab workflow, step by step

Before you evaluate any laboratory information system, map how a test moves through your lab today. A typical connected flow looks like this.

1. The doctor orders a test or panel in OPD, IPD or casualty.
2. The order reaches the lab and billing at the same time.
3. At collection, the system prints barcode labels for each tube based on test and container type.
4. The sample is collected, and the collector, time and site are recorded.
5. The sample is received in the lab and scanned, so its location is known.
6. The analyser reads the barcode, runs the tests and sends results back to the LIS.
7. A technologist reviews results, applying quality control and flag rules.
8. A pathologist or authorised signatory validates and releases the report.
9. The report appears on the doctor's screen, in the patient record and, where enabled, on the patient's phone.

Every step should be timestamped. That is what makes turnaround time measurable and errors traceable.

Sample barcoding: the single biggest safety gain

If a lab can make only one improvement, it should be barcoding. A barcode ties the physical tube to the patient, the order and the test, so the sample can be identified without reading handwriting.

What good barcoding includes:

• Labels printed at the point of collection, not in advance in bulk.
• One barcode per container, with the system deciding how many tubes a set of tests needs.
• Patient name, ID, age, sex, test codes and collection time on the label.
• Scan at collection, at lab receipt and on the analyser, so every hand-off is recorded.
• Rejection workflow for haemolysed, clotted, insufficient or mislabelled samples, with a reason and a recollection request.

Analyser interfacing: removing transcription

Analyser interfacing means the LIS and the lab machines talk directly. The analyser reads the barcode, asks the LIS which tests to run (or receives a worklist), and sends results back automatically. No one types numbers from a printout.

Most analysers communicate using the ASTM protocol over serial or network connections, and some use HL7 v2 messages. Each machine has its own interface specification, so interfacing is done machine by machine. Budget time for it, and ask your analyser vendor for the interface document early.

Interfacing lab equipment is part of our healthcare integration work, and our HL7 and FHIR integration guide explains the message standards in more depth.

Result validation and reporting

Getting a number from an analyser is not the same as releasing a report. A laboratory information system should support a clear validation chain.

• Reference ranges by age, sex and, where relevant, pregnancy, with abnormal values flagged.
• Critical values that trigger an immediate alert to the ordering doctor or ward, with the call documented.
• Delta checks that flag a result very different from the patient's previous value.
• Technical validation by the technologist, then medical validation by the pathologist or authorised signatory.
• Amended reports with the original preserved and the reason recorded.
• Report formats per department: tabular for biochemistry, narrative for histopathology, culture and sensitivity for microbiology.

Released reports should reach the doctor in the OPD or ward screen automatically. In our OPD management system guide we describe how a ready result moves the patient back into the doctor's review queue.

Turnaround time: what to measure

Turnaround time (TAT) is the metric doctors notice most. The LIS should break it down so you can see which step is slow.

Track TAT separately for routine, urgent and STAT tests, and by department. Often the analytical step is fast and the delays are in sample transport from wards or in waiting for validation. Those are process fixes that only become visible when each step is timestamped.

NABL and the LIS

NABL accredits medical laboratories in India against ISO 15189, the international standard for quality and competence in medical labs. Accreditation is about the lab's whole quality system, not the software. But a good LIS makes much of the required evidence part of daily work instead of a separate paper exercise.

What assessors typically look for that the LIS can support:

• Unique sample identification and traceability from collection to report.
• Records of who collected, received, processed, validated and released each sample.
• Internal quality control results recorded and reviewed, with action on failures.
• Participation in external quality assessment, with results tracked.
• Documented critical value communication.
• Controlled report formats and amendment records.
• Access control so only authorised staff validate reports.

Integration with billing, ABDM and patients

A hospital LIS sits in the middle of several systems.

• Billing: tests are charged when ordered or when the sample is collected, depending on your policy, so nothing is processed unbilled.
• IPD and nursing: collection lists for each ward round, and results on the nurse's view.
• ABDM: lab reports can be linked to the patient's ABHA and shared with consent where the hospital is ABDM-integrated. See our ABDM integration guide.
• Patients: reports shared on WhatsApp or a patient portal once released.
• Outsourced tests: samples sent to a reference lab tracked, with results imported or attached.

For standalone diagnostic centres rather than hospital labs, the priorities are different (home collection, B2B clients, franchise centres). Our guide to diagnostic centre management software covers that case.

Laboratory information system checklist

Use this when evaluating an LIS or scoping a build.

• Electronic orders from OPD, IPD and casualty linked to billing
• Barcode labels at collection, by container type
• Scan points at collection, receipt and analyser
• Sample rejection with reasons and recollection requests
• Bidirectional interfaces for your main analysers
• Age and sex reference ranges, critical values and delta checks
• Two-step validation with role-based signatories
• Department-specific report formats, including microbiology and histopathology
• TAT reports by segment, priority and department
• QC records, audit trail and amended report history
• Report delivery to doctors, records and patients

Common mistakes in LIS projects

Leaving analyser interfacing to the end. Interfaces depend on the analyser vendor's documentation, cables, network access and sometimes a vendor engineer's visit. Start this work in the first week, not after the screens are built.

Printing barcodes in advance. Pre-printed label sheets defeat the purpose. If a label exists before the patient is in front of the collector, it can end up on the wrong tube.

Ignoring manual departments. Microbiology, histopathology, cytology and some serology are partly or wholly manual. If the LIS only handles analyser-driven tests well, these departments stay on paper and their TAT stays invisible.

Copying old report formats blindly. Report formats are often years old and cluttered. Review them with your pathologists before go-live; it is the cheapest moment to fix them.

No plan for downtime. Analysers and networks fail. Agree how samples will be labelled and results recorded when the LIS is unavailable, and how that data will be entered afterwards.

Not training ward staff. Sample collection often happens in the ward, not the lab. If nurses do not scan at collection, traceability breaks before the sample even reaches the lab.

Building or connecting an LIS

Some hospitals already have a lab system that works well inside the lab but is disconnected from the rest of the hospital. In that case, connecting it is usually cheaper than replacing it. Others run the lab on a module that cannot interface with their analysers, and replacement is the only way to stop manual transcription.

At Algon we build the lab module as part of a connected hospital management system, or connect an existing LIS to it, depending on what the hospital already has. The starting point is the analyser list and a trace of a few real samples from order to report.

Conclusion

A laboratory information system earns its value in two places: barcoding that ties every tube to the right patient, and analyser interfacing that removes manual transcription. Add a clear validation chain, segment-wise turnaround tracking and connections to billing and the doctor's screen, and the lab becomes faster and safer. NABL accreditation still depends on your quality system, but a good LIS makes the evidence part of everyday work.