What Is a Laboratory Information System?
A Laboratory Information System (LIS) is a software platform that manages the operational and informational workflows of a clinical laboratory. It handles everything from the moment a test is ordered through specimen collection, processing, analysis, quality control, and result reporting. In a busy hospital laboratory, the LIS is the command centre — tracking thousands of specimens simultaneously, managing instrument interfaces, enforcing quality rules, and ensuring results reach clinicians rapidly and accurately.
The clinical laboratory is one of the most information-intensive environments in a hospital. A single patient admission may generate dozens of laboratory requests. Each request triggers a cascade of events: specimen labelling, collection, transport, receipt, processing, analysis on one or more instruments, quality control checks, result verification, and reporting. Without a well-configured LIS managing this process, the risks of error — misidentification, lost specimens, delayed results, transcription mistakes — are substantial.
Modern LIS platforms are highly integrated systems with bidirectional connections to the hospital information system, clinical analysers, blood bank systems, and increasingly to AI-powered interpretation tools.
Core Modules of an LIS
Specimen Management
Specimen management is the physical tracking layer of the LIS. When a test is ordered (via the HIS/EHR or directly in the LIS), the system generates labels — typically barcoded or using RFID — that are applied to collection tubes at the point of collection. The barcode encodes the patient identity, the specimen type, and the tests required.
At every subsequent step — collection, transport, laboratory receipt, centrifugation, aliquoting, analysis — the specimen is scanned and its location and status updated in the LIS. This chain of custody documentation is essential for both patient safety and medicolegal purposes. A misidentified specimen is a potentially catastrophic patient safety event; barcode-based specimen management significantly reduces this risk compared to manual labelling.
Test Ordering and Requisition
In an integrated environment, test orders arrive in the LIS from the HIS via HL7 ORM messages. Clinicians place orders in the EHR/HIS, which transmits them electronically to the LIS. This eliminates handwritten request forms and the transcription errors they introduce.
For urgent requests — such as an emergency department STAT order — the LIS must support prioritisation rules that flag the specimen for immediate processing and establish turnaround time targets. Many LIS platforms include turnaround time monitoring with alerts when targets are at risk of being missed.
Instrument Interfacing
A clinical laboratory contains numerous automated analysers — haematology counters, chemistry platforms, coagulation analysers, immunoassay systems, microbiology processors, and molecular diagnostic instruments. The LIS must interface with all of these, typically using the ASTM E1394 standard or HL7 v2.5.1 LIS2-A2 protocol for bidirectional communication.
With a bidirectional interface, the analyser receives a worklist of pending tests from the LIS when a specimen is loaded. After analysis, results are transmitted back to the LIS automatically rather than being manually entered. This automation is critical for throughput, accuracy, and turnaround time.
Result Reporting and Verification
When results arrive from instruments, they pass through the LIS validation workflow. Automated validation rules — defined by the laboratory's quality team — flag results that fall outside reference ranges, critical values, or delta check thresholds (where the current result differs substantially from the patient's previous result).
Results that pass automated rules are auto-verified and available for reporting immediately. Results that trigger flags require manual review and verification by a laboratory scientist or pathologist. This review layer is essential for catching instrument errors, contaminated specimens, and clinically implausible results.
Verified results are transmitted to the HIS/EHR via HL7 ORU messages. Critical values — for example, a potassium of 6.8 mmol/L or a positive blood culture — must also trigger an active notification to the clinical team, typically via phone call from the laboratory or an automated alert in the clinical system.
Quality Control
Laboratory quality control is a rigorous scientific discipline. The LIS supports QC by managing the analysis of reference materials at defined intervals, applying Westgard rules or equivalent statistical criteria to identify when an instrument has drifted out of calibration, and generating QC reports for accreditation purposes.
Accreditation by bodies such as ISO 15189 (the international standard for medical laboratory quality) requires systematic documentation of QC processes. The LIS is the system of record for this documentation.
Integration with HIS and EHR via HL7
The LIS sits at the centre of a web of HL7 interfaces:
- Inbound ORM messages from the HIS carry test orders with patient demographics and clinical context
- Inbound ADT messages from the HIS update patient demographic information when patients are admitted, discharged, or their details change
- Outbound ORU messages carry completed results back to the HIS for display in the patient's record
- FHIR DiagnosticReport resources are increasingly used in modern environments where the LIS connects to FHIR-enabled EHR platforms or national health exchanges
Patient matching — ensuring that the patient in the LIS record corresponds to the correct patient in the HIS — is a critical integration challenge. Master Patient Index (MPI) synchronisation between the LIS and HIS is essential to prevent results being reported to the wrong patient record.
Barcode and RFID in Laboratory Workflows
Barcode scanning is now universal in clinical laboratories worldwide. Linear barcodes (Code 128 is the most common) and 2D barcodes (Data Matrix and QR codes) are used on specimen labels, reagent kits, and consumables.
RFID is less universally deployed but is used in some environments for specimen tracking where scanning is inconvenient — for example, tracking specimens in a refrigerator or transport box without needing line-of-sight scanning. RFID is also used in blood bank management to track blood products from component preparation through to transfusion.
Automated specimen processing lines — robotics systems from vendors such as Roche, Siemens, and Abbott that automate centrifugation, aliquoting, and specimen routing — depend on barcoding and LIS integration for their operation. These systems represent the leading edge of laboratory automation in high-volume settings.
Standalone LIS vs Integrated HIS Module
One of the key strategic decisions in laboratory IT is whether to deploy a standalone specialist LIS or to use the laboratory module built into the hospital's HIS.
Standalone LIS products (such as MEDITECH LIS, Sunquest, DI-LIS, or CliniSys) offer deep laboratory functionality, mature instrument interfaces, and specialist support. They are the right choice for high-volume laboratories with complex workflows, a wide range of analytical disciplines, or research functions.
Integrated HIS modules are simpler to manage (single vendor, tighter integration with clinical workflows) but often lack the depth of specialist LIS products. They may be adequate for smaller laboratories with straightforward workflows and a limited range of disciplines.
The decision should be driven by the volume and complexity of the laboratory's work, the number and types of instruments that need to be interfaced, and the organisation's overall IT architecture strategy.
Implementation Steps
A successful LIS implementation follows a structured process:
- Requirements gathering: Document all laboratory disciplines, test menus, instrument types, and reporting requirements
- Interface design: Map all HL7 interfaces required with the HIS and with each laboratory instrument
- System configuration: Build test profiles, reference ranges, QC rules, and report templates
- Instrument interface testing: Test each instrument interface in isolation before connecting to the live environment
- End-to-end workflow testing: Simulate complete order-to-result workflows with test specimens
- Staff training: Role-specific training for laboratory scientists, phlebotomists, and administrative staff
- Parallel running: Operate the new LIS alongside the legacy system for a defined period to validate result accuracy
- Go-live and stabilisation: Go live on a defined date with intensive support coverage
The parallel running phase — often underestimated — is essential for identifying discrepancies before they become patient safety incidents.
FZ Consulting LLP supports clinical laboratories with LIS selection, HL7 interface design, instrument interfacing, and implementation project management. Contact our team to discuss your laboratory IT requirements.