Taction Software®
Healthcare IT Glossary

What is LIS?
Laboratory Information System

Behind every lab result that appears in a patient’s chart — every blood count, every metabolic panel, every culture and sensitivity — there’s a system that received the order, tracked the specimen, managed the analyzer workflow, validated the result, and transmitted it back to the ordering provider. That system is the LIS. It’s the operational backbone of every clinical laboratory.

Certifications

Tell Us Your Requirements

Our experts are ready to understand your business goals.

What is 1 + 1 ?

100% confidential & no spam

Definition of LISHow LIS Works in HealthcareKey LIS Standards and SpecificationsImplementation ConsiderationsHow Taction Helps with LIS

Definition of LIS

LIS, which stands for Laboratory Information System, is a software system that manages the complete workflow of a clinical laboratory — from test ordering and specimen accessioning through result entry, validation, reporting, and archiving. It serves as the central operational and data management platform for pathology, clinical chemistry, hematology, microbiology, blood bank, and molecular diagnostics laboratories.

An LIS handles both the analytical workflow (managing instruments, quality control, and result validation) and the administrative workflow (order management, billing, turnaround time tracking, and regulatory compliance). Modern LIS platforms also support interfacing with external systems — receiving orders from EHR systems and transmitting results back using standardized messaging.

It’s worth distinguishing LIS from LIMS (Laboratory Information Management System). While the terms are sometimes used interchangeably, LIMS typically refers to systems used in research, pharmaceutical, and industrial laboratories focused on sample tracking and data management. LIS specifically refers to clinical laboratory systems operating within healthcare, subject to CLIA, CAP, and HIPAA regulations.

In simple terms: LIS is the operating system of the clinical lab — managing every specimen, every test, and every result from the moment an order arrives until the report reaches the provider.

How LIS Works in Healthcare

The LIS workflow mirrors the physical flow of a specimen through the laboratory — from order receipt to result delivery.

Order receipt
Clinical orders originate in the EHR or a hospital information system. The order — containing patient demographics, ordering provider, requested tests, clinical indication, and priority — arrives at the LIS via an HL7v2 ORM (Order) message. The LIS validates the order, checks for duplicate orders, and assigns it to the appropriate laboratory section.
Specimen accessioning
When the physical specimen arrives in the lab, a technologist accessions it — scanning the barcode label to link the specimen to the electronic order in the LIS. The LIS verifies specimen type, collection time, and adequacy. If the specimen doesn’t match the order requirements (wrong tube type, insufficient volume, hemolyzed sample), the LIS flags it for resolution.
Worklist generation and instrument interfacing
The LIS generates worklists for each analyzer and testing station. For automated chemistry and hematology analyzers, the LIS sends the test requests to the instrument via a bidirectional interface. The instrument runs the tests and sends results back to the LIS automatically — no manual transcription required.
Result entry and validation
Results flow into the LIS either from instrument interfaces (automated) or manual entry (for manual test methods). The LIS applies auto-verification rules — checking results against reference ranges, delta checks (comparison to prior results), critical value thresholds, and quality control status. Results that pass all rules are auto-verified and released. Results that trigger flags require manual review by a medical technologist or pathologist.
Result reporting
Once validated, results are transmitted from the LIS to the ordering provider’s EHR via an HL7v2 ORU (Observation Result) message. Each result carries a LOINC code identifying the test and a SNOMED CT code or text value for the result. Critical values trigger immediate notification to the ordering provider per laboratory protocol.
Public health reporting
For reportable conditions (infectious diseases, certain cancers), the LIS generates electronic laboratory reports (ELRs) for state and federal health departments. These reports use LOINC-coded test identifiers and SNOMED CT-coded results, transmitted via the public health surveillance infrastructure.
Billing integration
The LIS feeds billing systems with completed test data — test codes, performing laboratory, ordering provider — which is then translated into CPT codes for claims submission through the revenue cycle.

Key LIS Standards and Specifications

Legacy
HL7v2 Lab Messaging
LIS systems communicate with EHRs and hospital systems using HL7v2 messages — ORM (orders), ORU (results), and ORL (order response/acknowledgment). The HL7 2.5.1 Implementation Guide for Lab Orders and Results is the reference specification for clinical lab interfaces in the U.S.
Legacy
LOINC
LOINC is the standard vocabulary for identifying laboratory tests and observations in LIS-to-EHR result messages. Every result transmitted from the LIS must carry the appropriate LOINC code in the OBX-3 field to enable interoperability — the receiving EHR uses the LOINC code to identify what was tested and display results in the correct clinical context.
Legacy
CLIA and CAP Compliance
Clinical laboratories in the U.S. must comply with CLIA (Clinical Laboratory Improvement Amendments) regulations, which govern laboratory testing quality, personnel qualifications, and proficiency testing. Many laboratories also pursue CAP (College of American Pathologists) accreditation. The LIS must support these compliance requirements — maintaining audit trails, QC documentation, proficiency testing records, and personnel competency tracking.
Legacy
IHE Laboratory Profiles
The IHE Laboratory domain publishes integration profiles including Laboratory Testing Workflow (LTW) for order-to-result workflow management and Laboratory Analytical Workflow (LAW) for instrument-level work management. These profiles standardize how LIS platforms interact with ordering systems, analyzers, and reporting infrastructure.
Legacy
FHIR for Lab Data
FHIR is increasingly used for lab data exchange beyond traditional HL7v2 messaging. The FHIR Observation resource represents lab results, DiagnosticReport bundles results into interpretive reports, and ServiceRequest handles lab orders. Organizations building new lab connectivity should plan for FHIR-based interfaces alongside HL7v2 support.
Building an LIS integration? Let’s talk.
Book a free call

Implementation Considerations

LIS implementation involves instrument interfacing, workflow configuration, vocabulary management, and compliance setup.

Interoperability with the EHR is non-negotiable. The HL7v2 ORM/ORU interface between the LIS and EHR is one of the most critical integrations in a hospital. Order flows, result delivery, critical value notifications, and add-on test handling must all work reliably. Use a dedicated integration engine for message routing, transformation, and error management between the LIS and EHR.

Instrument interfacing is the critical path
A clinical lab may have dozens of analyzers — chemistry, hematology, coagulation, urinalysis, immunoassay, blood gas, microbiology identification systems. Each instrument requires a bidirectional interface with the LIS. Interface protocols vary by vendor — some use HL7, some use ASTM/CLSI LIS2-A2, some use proprietary protocols. Budget significant time for instrument interface development and testing.
Auto-verification rules require clinical validation
Auto-verification dramatically improves turnaround time by releasing normal results without manual review. But the rules must be clinically validated — incorrect auto-verification can release erroneous results to patient charts. Pathologists and lab directors must define and approve all auto-verification criteria before go-live.
LOINC mapping requires laboratory expertise
Mapping your lab’s internal test catalog to LOINC codes requires understanding the six LOINC axes — component, property, time, specimen, scale, and method. Incorrect mappings compromise downstream analytics, quality reporting, and clinical decision support. Use laboratory professionals — not just IT staff — for LOINC mapping validation.
Specimen tracking and chain of custody
For forensic, drug testing, and certain reference lab workflows, the LIS must maintain a complete chain of custody — documenting every handoff from collection through testing and reporting. This requires barcode-driven tracking at every step.
Data migration from legacy LIS
Replacing an existing LIS requires migrating historical patient results, reference ranges, test catalogs, and instrument configurations. Historical results must be accurately mapped and accessible in the new system for delta checking and trend analysis.

How Taction Helps with LIS

At Taction, our healthcare integration team builds LIS interfaces, lab connectivity solutions, and custom laboratory applications for hospitals, reference labs, and health IT vendors.

What we do:

Whether you’re implementing a new LIS, connecting lab systems to an EHR, or building lab data APIs, our healthcare engineering team delivers the interface precision and clinical workflow understanding laboratory integrations demand.

LIS-to-EHR interface development
We build HL7v2 ORM/ORU interfaces connecting LIS platforms to EHR systems — handling order routing, result delivery, critical value alerts, and add-on test workflows.
Instrument interfacing
We build bidirectional interfaces between LIS platforms and laboratory analyzers — supporting HL7, ASTM, and vendor-specific protocols across chemistry, hematology, microbiology, and specialty testing instruments.
LOINC mapping and terminology services
We map laboratory test catalogs to LOINC codes with clinical validation, and deploy terminology services that support ongoing code maintenance as LOINC releases new versions.
Public health reporting
We build automated electronic laboratory reporting (ELR) pipelines that generate LOINC-coded, SNOMED CT-coded reportable condition messages for state and federal public health agencies.
FHIR lab APIs
We build FHIR-based lab data services exposing Observation and DiagnosticReport resources for patient portals, mobile apps, and third-party clinical applications.

Explore Related Terms

What is RIS?What is PACS?What is ADT?What is HIE?What is EHR Migration?

Ready to discuss your LIS project?

Schedule a free call

Ready to Discuss Your Project With Us?

Your email address will not be published. Required fields are marked *

What is 1 + 1 ?

What's Next?

Our expert reaches out shortly after receiving your request and analyzing your requirements.

If needed, we sign an NDA to protect your privacy.

We request additional information to better understand and analyze your project.

We schedule a call to discuss your project, goals. and priorities, and provide preliminary feedback.

If you're satisfied, we finalize the agreement and start your project.