Updated on 22 June 2026

Hospital laboratory information system (LIS) — NABL compliance and what Indian hospitals need

A detailed guide to hospital laboratory information systems in India — NABL ISO 15189:2022 requirements, sample lifecycle management, two-step result validation, QC with Westgard rules, analyser interfacing, critical value alerts, turnaround time monitoring, ABDM DiagnosticReport generation, and vendor evaluation criteria.

By L.K. Monu Borkala, Founder & CEO, OneCity Technologies Pvt Ltd  ·  17 min read

The hospital laboratory generates more structured, time-sensitive, regulatory-audited data per day than any other department. Every sample collected, every test ordered, every QC run, every result validated, every critical value communicated, every reagent lot consumed — each creates a data point that must be traceable, timestamped, attributed to a specific operator, and available for audit at any point in the future. A 100-bed hospital with a moderately busy lab processes 300–800 samples per day across chemistry, haematology, microbiology, and serology. Each sample may have 5–15 tests ordered. That is 1,500 to 12,000 individual test results per day — each requiring validation before release to the clinician.

In India, laboratory quality is governed by NABL (National Accreditation Board for Testing and Calibration Laboratories) accreditation under ISO 15189:2022 — the international standard for medical laboratory quality and competence. NABL accreditation is not universally mandatory by law, but it is increasingly required for NABH hospital accreditation, insurance empanelment, referral credibility, and participation in government health schemes. The 2022 revision of ISO 15189 (replacing the 2012 edition) tightened requirements around information system management, making the choice of LIS directly relevant to accreditation outcomes.

This guide covers what an Indian hospital LIS must do — the NABL requirements, the clinical workflow from order to report, quality control management, analyser interfacing, integration with the hospital ERP, and the questions to ask during vendor evaluation.

What NABL ISO 15189:2022 requires from a LIS

ISO 15189:2022 has several clauses that directly constrain LIS selection and configuration. These are not optional features — they are accreditation requirements.

Clause 7.3 — Pre-examination processes. The LIS must capture at the point of sample collection: patient identification linked to the hospital's UHID and, where available, the ABHA ID; the specific tests ordered; the sample type (serum, plasma, whole blood, urine, CSF, etc.); the collection date and time; the collector's identity; and any relevant clinical information that affects test interpretation (e.g., fasting status for glucose, last dose timing for drug levels). The system must prevent sample misidentification — barcoded sample tracking from collection point to result release is the practical minimum that satisfies this clause. Manual sample labelling with handwritten patient names does not meet the traceability standard.

Clause 7.4 — Examination processes. The LIS must record for each test result: the analytical method used, the specific analyser on which the test was run, the reagent lot number, the calibration status of the analyser at the time of the run, and the internal QC results for the analytical batch. If QC results are out of range (based on the laboratory's defined QC rules — typically Westgard multi-rule), the system must block patient result release for that analytical batch until corrective action is documented and a repeat QC run is acceptable.

Clause 7.5 — Post-examination processes. Result validation must follow a two-step workflow: technical validation by the laboratory technician (checking against QC status, delta check against the patient's previous result, panic value thresholds, and biological plausibility) followed by medical validation by the pathologist (clinical interpretation, addition of interpretive comments, and authorisation for release). The LIS must enforce this sequence — a result must not reach the ordering clinician before both validation steps are complete. For critical values, the system must generate an immediate alert and track the communication pathway: when was the clinician notified, who acknowledged, and what was the response time.

Clause 8.5 — Management of information. This clause directly addresses the LIS as a system: data integrity (protection against unauthorised modification), access control (role-based — technicians can enter results, only pathologists can medically validate, administrators can configure), audit trails for all data changes (who changed what, when, from what value to what value), backup and disaster recovery procedures with defined RPO and RTO, and validation of the LIS after any software upgrade or configuration change.

The sample lifecycle

A complete LIS manages eight distinct stages of the sample lifecycle. Each stage must be tracked with a timestamp and operator identity.

Stage 1 — Test order. The doctor orders tests from the OPD or IPD module. The order flows to the laboratory electronically — no paper test request form. The LIS generates barcode labels for each sample tube, indicating the patient ID, the tests ordered, the required sample type, and the collection instructions (e.g., fasting, specific tube colour, special handling). For in-patients, the order also generates a phlebotomy task assigned to the ward nurse or phlebotomist.

Stage 2 — Sample collection. The phlebotomist scans the patient's wristband (IPD) or verifies identity against two identifiers (OPD — name and UHID), collects the sample in the correct tube, and scans the barcode label to link the physical tube to the electronic order. The collection timestamp is recorded. If the wrong tube type is used for a test (e.g., EDTA tube for a coagulation test that requires citrate), the system should flag the mismatch.

Stage 3 — Sample receipt. The lab reception scans each barcode at receipt. The system checks: is the sample type correct? Is the volume adequate? Was the transport time within acceptable limits (e.g., blood gas samples must be processed within 30 minutes of collection)? Is the sample haemolysed, lipemic, or icteric (which affects certain assays)? Any rejection is documented with a reason code, and a recollection request is auto-generated and sent to the ordering location.

Stage 4 — Analysis. For automated analysers (chemistry, haematology, immunoassay), the LIS interfaces directly with the instrument. The sample ID and ordered tests are transmitted to the analyser (query message). The analyser processes the sample and transmits the results back to the LIS (result message). No manual data entry. For manual tests (certain microbiology, cytology, special stains), the technician enters results directly into the LIS with the test method recorded.

Stage 5 — Technical validation. The technician reviews each result against: QC status (were the QC samples in the same batch acceptable?), delta check (is this result significantly different from the patient's previous result for the same test? A haemoglobin that drops from 12 to 6 in 24 hours needs investigation before release), panic/critical value thresholds, and biological plausibility (is a potassium of 9.8 real or a lab error?). Results that fail any check are flagged for review before release.

Stage 6 — Medical validation. The pathologist reviews flagged results and, depending on lab policy, all results. The pathologist can add interpretive comments (e.g., "peripheral smear shows hypersegmented neutrophils — suggest B12 and folate levels"), suggest additional tests, or request a repeat. Medical validation is the release gate — only after the pathologist signs off does the result become visible to the ordering clinician.

Stage 7 — Result delivery. The validated result appears on the doctor's dashboard in real time. A formatted report is generated with the laboratory header, patient demographics, test results with reference ranges, flags for out-of-range values, interpretive comments, and the pathologist's digital signature. For ABDM-linked patients, the result can be generated as a FHIR DiagnosticReport resource and made available through the ABDM Health Information Exchange with the patient's consent.

Stage 8 — Turnaround time measurement. The system calculates TAT per test at two levels: order-to-result (from when the doctor placed the order to when the result was released — this is the clinician's TAT) and receipt-to-result (from when the lab received the sample to when the result was released — this is the lab's operational TAT). Both are NABH quality indicators. The LIS should generate monthly TAT reports segmented by test, by shift, by department of origin, and by urgency (routine vs stat).

Quality control management

Internal quality control (IQC) and external quality assessment (EQAS) tracking are non-negotiable for NABL accreditation. The LIS must support both.

Internal QC (IQC). Before each analytical run (or at defined intervals per the lab's QC policy), the technician runs QC materials — commercially purchased control samples with known target values and acceptable ranges. The LIS must store QC results per analytical run, generate Levey-Jennings charts (plotting QC values over time against the mean, ±1SD, ±2SD, and ±3SD lines), and apply Westgard multi-rules to detect systematic errors. The standard Westgard rules — 1-2s (warning), 1-3s (reject), 2-2s (reject), R-4s (reject), 4-1s (reject), 10x (reject) — should be configurable per test and per QC material. When a Westgard rule is violated, the LIS must block release of patient results from that analytical batch until corrective action is documented and a repeat QC run is acceptable.

External QA (EQAS). The lab participates in external quality assessment schemes (e.g., CMC Vellore, AIIMS, BioRad EQAS) where blind samples are tested and results are compared against the scheme's consensus values. The LIS should record: scheme name, survey round, expected result, lab's reported result, performance score (SDI or z-score), and any non-conformance action taken. Performance trends over multiple rounds should be visible.

Calibration tracking. Each analyser has a calibration schedule, calibration results, and calibration verification records. The LIS should alert when calibration is due, block analysis on an analyser with overdue calibration (or at minimum flag the results), and maintain the calibration history for audit.

Analyser interfacing

Manual result entry is the single largest source of laboratory errors. A technician reading a number from an analyser screen and typing it into a computer transposes digits, misreads decimal points, and enters results against the wrong patient. Direct interfacing between the LIS and the analyser eliminates all three error categories.

The LIS must support standard instrument communication protocols: ASTM E1381/1394 (the most common protocol for clinical chemistry, haematology, immunoassay and coagulation analysers), HL7 v2.x for newer-generation instruments, and serial (RS-232) or TCP/IP communication for older equipment. The interface should be bi-directional: the LIS transmits the sample barcode and ordered tests to the analyser (host query), and receives the results back (result upload). Unidirectional interfaces (results only, no query) are acceptable but less efficient — the technician must still manually select the test panel on the analyser.

In Indian tier-2/3 hospitals, the analyser fleet is typically heterogeneous: a Beckman or Roche for chemistry, a Sysmex or Beckman for haematology, a BioMerieux for microbiology identification and sensitivity, a Siemens or Abbott for immunoassay, and several manual tests. The LIS must handle this mix of brands and protocols without requiring separate middleware for each analyser. Middleware adds cost, maintenance burden, and an additional failure point between the instrument and the database.

Specialised workflows

Microbiology and culture sensitivity

Microbiology differs fundamentally from chemistry or haematology. A blood culture may take 24–72 hours for growth detection. Sensitivity testing adds another 18–24 hours. Interim results — Gram stain (available in 1 hour), preliminary organism identification (24 hours) — must be reportable before the final culture and sensitivity report. The LIS must support multi-step result entry with interim reporting: preliminary → intermediate → final, each step separately visible to the clinician.

Antibiogram generation is a critical function. The LIS should auto-generate cumulative antibiograms — quarterly reports showing resistance percentages per organism-antibiotic combination — for the hospital's infection control committee and antibiotic stewardship programme. ICMR's Antimicrobial Resistance Surveillance Network mandates AMR reporting from sentinel sites. Even for non-sentinel hospitals, cumulative antibiograms are a NABH quality indicator and an essential tool for empiric antibiotic prescribing policy.

Histopathology

Histopathology has its own distinct workflow: specimen receipt → gross examination (macroscopic description, measurements, section selection) → tissue processing → paraffin embedding → microtomy (sectioning) → staining → microscopic examination → pathologist report. The LIS must track the specimen through each stage with timestamps. Gross description templates, microscopic description with ICD-O (International Classification of Diseases for Oncology) coding for cancer specimens, synoptic reporting for cancer (following CAP — College of American Pathologists — protocol), and image attachment for photomicrographs should be supported. TAT tracking for histopathology operates in days, not hours — the system must handle both timescales.

Blood bank integration

If the hospital operates a blood bank (licensed under Drugs and Cosmetics Act 1940, Rule 122-I), the LIS must integrate with blood bank operations. Cross-match requests originate from the clinical team. The blood bank performs grouping and cross-matching. Issue tracking must capture: donor unit number, blood group (ABO + Rh), cross-match result, issue time, and any adverse transfusion reaction. Haemovigilance reporting per National Blood Transfusion Council (NBTC) guidelines requires structured data that only an integrated system can produce efficiently.

Integration with the hospital ERP

Lab ↔ Billing: Every test performed becomes a billing line item. In-patient lab charges accumulate on the running bill. Outpatient lab charges generate an immediate bill or add to a health check-up package.

Lab ↔ EMR: Results become part of the patient's electronic medical record. Historical trends — HbA1c over 12 months, creatinine over 6 months, PSA over 2 years — should be visualisable as time-series charts by the clinician, not just as a list of numbers.

Lab ↔ Pharmacy: Drug monitoring tests (INR for warfarin, creatinine and GFR for nephrotoxic drugs, LFT for methotrexate, TSH for amiodarone) should trigger alerts if results are outside the therapeutic range. The alert goes to both the prescribing doctor and the pharmacist.

Lab ↔ ABDM: FHIR R4 DiagnosticReport resource generation for ABDM health record sharing. When the patient consents, the validated lab result is pushed to the ABDM Health Information Exchange as a structured document.

Lab ↔ Inventory: Reagent consumption per test drives the auto-reorder system. The LIS tracks reagent lot usage, expiry dates, and wastage volumes.

What to ask a LIS vendor

These questions should be asked during a live demonstration with your lab manager and pathologist present.

Walk me through the complete sample lifecycle — from a doctor ordering a CBC to the pathologist-validated result appearing on the clinician's screen. Every step must be visible, timestamped, and barcoded.

Show me a QC violation blocking patient result release. Trigger a 1-3s Westgard rule violation and demonstrate that results from that batch cannot be released until corrective action is documented and a repeat QC passes.

Show me a Levey-Jennings chart for a QC material over 30 days. The chart should clearly show the mean, ±1SD, ±2SD, ±3SD lines, and any Westgard rule violations marked.

Generate a critical value alert and show me the acknowledgement tracking. When was the clinician notified? Who acknowledged? What was the turnaround time from result to acknowledgement?

Demonstrate analyser interfacing. Which analyser brands and protocols are supported? Is the interface bi-directional (host query + result upload) or unidirectional (result upload only)?

Generate a TAT report by test and by shift for the last month. Can I see the percentage of tests meeting the defined TAT target?

Show me the audit trail. If a technician changes a result after technical validation, is the original value, the new value, the reason for change, and the operator identity all recorded and visible?

OneCity's laboratory information system covers the complete sample lifecycle with barcoded tracking, analyser interfacing (ASTM, HL7, serial), two-step validation, QC with Westgard multi-rules, critical value alerting, TAT monitoring, cumulative antibiogram generation, and ABDM DiagnosticReport — all integrated with billing, EMR, pharmacy and accounts in the same database. See it in a walkthrough →