Skip to main content
LIMS IQ LIS knowledge library DOC LAB-INFORMATICS
REV 2026-11

What Is Clinical Laboratory Informatics? Guides

Clinical laboratory informatics explained: scope, roles, the LOINC, HL7 and FHIR standards, and practical guides to QC, coding, critical values, ELR and KPIs.

Clinical laboratory informatics is the discipline of managing a clinical laboratory’s data: how orders, specimens, results and reports are coded, validated, released, exchanged and measured. It is distinct from the bench work that produces a result and from the general hospital IT that keeps networks and workstations running; informatics sits between the two and decides whether an accurate measurement becomes an accurate, traceable, billable and reportable result.

The distinction matters because informatics failures rarely show up at the bench. A result that is coded to the wrong LOINC, released past a failed control, or never called to the ordering provider is still a failed result, and the failure surfaces later: at inspection, in a denied claim, or in a public health agency’s rejection queue, long after the specimen is gone. This guide defines the field, its scope, who owns it, the standards you will meet and an implementation order, grounded in CLIA-regulated practice; the articles in this section go deeper on individual decisions. For an overview of the system informatics runs on, start with the clinical LIS guide.

What laboratory informatics covers

The scope follows the specimen through the three phases of testing; informatics owns the data generated in each phase, not the collection or analytic work itself.

Pre-analytic data. Order entry and requisitions, whether keyed from a paper form, received as an HL7 ORM message from an EMR, or placed through a provider portal. Patient and ordering-provider identification. Specimen identification and tracking: barcode labels, accession numbers, collection time, container and transport conditions, aliquots and storage locations. The test catalog itself: which orderable maps to which result components, specimen requirements, reference ranges by age and sex, and the reflex rules that add tests automatically.

Analytic data. Instrument data capture through ASTM or HL7 interfaces, including the flags and comments the analyzer attaches to each value. Quality control: control lot definitions, target means and standard deviations, Levey-Jennings charts, and the Westgard multirule evaluation that decides whether a run is accepted or held. Autoverification rules, which release routine results without technologist review when the value is within range, QC passed, no instrument flag fired and the delta check against the patient’s prior result is clean.

Post-analytic data. Result coding to national vocabularies: LOINC for what was measured, SNOMED CT for organisms and findings, CPT for the billable procedure and ICD-10 for the diagnosis that supports it. Result release, with the audit trail of who verified what and when. Critical value handling: the list, the time-to-call window, the read-back confirmation and the escalation path when the first call fails. Reporting and exchange: HL7 ORU results to the EMR, FHIR resources for newer integrations, PDF reports to portals and fax. Electronic laboratory reporting of reportable conditions to public health. Billing data quality, so the claim leaving the lab carries validated codes and a documented order. And finally measurement: turnaround time, QC failure rates, autoverification rate, critical value call compliance and denial rates, surfaced in dashboards the lab reviews on a schedule.

An integrated lab informatics approach treats all of this as one connected dataset rather than a set of unrelated modules: the catalog decision that assigns a LOINC code is the same decision that makes the ELR message valid and the claim payable.

Laboratory informatics vs the LIS vs bioinformatics vs lab IT

The terms get used interchangeably, and they should not be.

Discipline Core question Typical work Who usually owns it
Laboratory informatics Is the lab’s data correct, complete, coded, released and reported the way regulators and clinicians require? Catalog governance, QC and autoverification rules, LOINC and SNOMED CT maps, critical value policy, ELR, billing edits, KPIs Lab director with an LIS analyst or informatics lead
The LIS Which system records and executes those decisions? Configuring and operating the laboratory information system: accessioning, interfaces, worklists, result entry, reporting LIS administrator and the vendor
Bioinformatics What do sequencing and other high-dimensional data mean biologically? Pipelines, variant calling, annotation, genomic databases Bioinformaticians in molecular or research labs
Lab IT (hospital IT) Is the infrastructure available, secure and supported? Networks, servers or cloud tenancy, workstations, identity, backups, patching Hospital or enterprise IT

Laboratory informatics is the set of decisions; the LIS is where most of them are implemented. Bioinformatics overlaps only in molecular labs, where sequencing output has to flow back into the LIS as a coded, reportable result. Lab IT keeps the platform running but does not decide which Westgard rules hold a run.

Who owns informatics in a clinical lab

No single title owns it; the work is split across a few roles, and the gaps between them are where problems hide.

  • The laboratory director is accountable under CLIA for the quality of results and for the policies that govern release, critical values and reporting. Informatics decisions are quality decisions, so they end at the director’s signature.
  • The LIS administrator or analyst builds and maintains the configuration: the test catalog, interface mappings, rule sets, report templates and user roles.
  • The QC officer or quality manager owns the control rules, the failed-QC review process, proficiency testing records and the evidence an inspector will ask for.
  • Informatics-trained medical laboratory scientists bridge the bench and the configuration: they know what an analyzer flag means and whether an autoverification rule is safe for a given analyte.
  • The vendor’s implementation team carries the configuration know-how during a go-live and should hand it over documented and version controlled, in a form the lab can maintain afterward.

A lab informatics implementation goes better when these roles meet regularly over a shared change log. Every catalog edit, rule change and interface map is recorded, reviewed and, where it affects patient results, validated before it goes live.

Standards and vocabularies you will meet

  • HL7 v2 is the production protocol for moving structured data between healthcare systems. In the lab it carries orders (ORM), results (ORU), patient demographics (ADT), documents (MDM) and billing transactions (DFT) between the EMR, the LIS, reference labs and public health agencies. See the HL7 LIS integration page.
  • FHIR R4 is the REST and JSON standard that newer integrations use. Lab work maps onto a small set of resources: Patient, ServiceRequest, Specimen, Observation and DiagnosticReport. See the FHIR for clinical labs guide.
  • LOINC (Logical Observation Identifiers Names and Codes) identifies what was measured independently of who ran the test. It is the standard result code in EMR interfaces, ELR and FHIR Observation resources, and mapping it correctly is the most consequential catalog task.
  • SNOMED CT is the clinical terminology for organisms, findings and specimen types. ELR and structured microbiology reporting rely on it alongside LOINC.
  • CPT and ICD-10 carry the billing side: the procedure performed and the diagnosis that supports medical necessity.
  • ASTM E1394 is the older analyzer-to-LIS interface standard that many chemistry, hematology and immunology instruments still speak.
  • CLIA and CAP do not prescribe a particular system, but both expect the lab to validate its information system, control who can change test definitions and rules, keep audit trails of result changes, retain records for the required period, and demonstrate that the result reported to the clinician matches what the instrument produced. The LIS glossary defines these terms in one place.

Implementing informatics controls: where to start

The order reflects dependency, not importance: each step produces something the next one needs.

  1. Test catalog and LOINC map. Clean the orderables, result components, units and reference ranges first, then assign LOINC codes. Everything downstream, from interfaces to ELR to claims, inherits this map.
  2. QC rules. Define control lots, targets and the Westgard rule set per analyte, and decide how a failed run is documented and how held samples are released under the SOP.
  3. Autoverification. Write and validate the release rules analyte by analyte, starting with high-volume chemistry and hematology, and keep the validation evidence.
  4. Critical values. Fix the list and thresholds, configure the alert, capture read-back and escalation, and report on time to acknowledgment.
  5. Electronic laboratory reporting. Flag reportable results from the catalog, map jurisdiction routing and reconcile acknowledgments so nothing fails silently.
  6. Billing edits. Validate CPT and ICD-10 at accessioning, check eligibility before the specimen is run, and stop incomplete orders from reaching the claim.
  7. Dashboards. Once the data is coded and the rules are live, measure turnaround, QC performance, autoverification rate, callback compliance and denials, and review them on a schedule.

Where to start in this section

The topics above map onto specific parts of the platform: QC in the LIS, analytics for clinical labs, specimen tracking, LIS billing integration, and public health LIMS reporting. For evaluation-stage reading, see the lab analytics dashboard guide.

To see how these controls would be configured against your own test catalog, control rules, and interfaces, request a demo.

  1. FISH Probe Lot Tracking and QC in the LIS

    How a cytogenetics LIS turns FISH probe lot tracking, validation, and case-to-probe traceability into QC that gates FISH result release.

    Read article: FISH Probe Lot Tracking and QC in the LIS
  2. Westgard Rules & Failed-QC Review

    How a clinical LIS evaluates Westgard rules, charts QC trends, alerts reviewers to failures, and documents SOP-controlled sample holds.

    Read article: Westgard Rules & Failed-QC Review
  3. LIS Billing Integration: Cutting Claim Denials

    How LIS billing integration reduces avoidable lab claim denials: eligibility at accessioning, charge capture, ICD-10/CPT validation, and clean 837 claims.

    Read article: LIS Billing Integration: Cutting Claim Denials
  4. Critical Value Reporting Workflow in an LIS

    See how clinical labs define critical values, route provider callbacks, document read-back, and measure acknowledgment time in the LIS.

    Read article: Critical Value Reporting Workflow in an LIS
  5. LOINC Mapping for Clinical Labs: Practical Guide

    How clinical labs approach LOINC mapping in practice: six-part axis structure, where mappings break, RELMA, LIVD, ELR/FHIR requirements, and governance.

    Read article: LOINC Mapping for Clinical Labs: Practical Guide
  6. Clinical Lab KPIs and the Lab Analytics Dashboard

    Clinical lab KPI guidance, plus how LIMS IQ separates a live requisition view from administrator-refreshed analytics dashboards.

    Read article: Clinical Lab KPIs and the Lab Analytics Dashboard
  7. Lab Chain of Custody: Barcode Workflow

    How barcode chain of custody records collection, accessioning, aliquoting, storage, and disposition across regulated laboratory workflows.

    Read article: Lab Chain of Custody: Barcode Workflow