What is Dr. Zubair Khalid's research focus?

Dr. Zubair Khalid specializes in molecular virology, mRNA vaccine development, and computational biology, with a focus on avian pathogens like IBDV and Avian Reovirus.

Where is Dr. Zubair Khalid currently working?

Dr. Zubair Khalid is a Postdoctoral Research Associate at the University of Maryland (UMD), specifically within the Department of Animal and Avian Sciences.

LIMS Explained: Lab Information Management Systems

By Dr. Zubair Khalid, DVM, MS, PhD · 2026-09-20

A laboratory information management system (LIMS) is software that tracks a physical sample from the moment it arrives at a laboratory until its result is authorized and reported. It is the operational backbone of a testing lab: it assigns identifiers, records who handled what and when, schedules tests, captures instrument output, applies quality rules, and stores an immutable audit trail.

The term gets used loosely. People say "LIMS" when they mean a spreadsheet, a clinical results viewer, or an electronic notebook. Those are different tools with different jobs. This guide defines LIMS precisely, separates it from the electronic laboratory notebook (ELN) and the laboratory information system (LIS), walks through the core modules, and follows one sample through a complete workflow.

What Is a Laboratory Information Management System?

The LIMS system definition is narrow and operational. A LIMS is a database-backed application whose primary object is the sample, not the experiment and not the patient result. Every record in a LIMS is anchored to a specimen, an aliquot, or a batch of specimens, and every action on that specimen is time-stamped and attributed to a user or an instrument.

That anchoring is what separates a real LIMS from a folder of CSV files. When a veterinary diagnostic laboratory receives 400 oral fluid tubes in a single morning during a disease outbreak, the LIMS is the only system that can answer three questions at once: where is tube 217 right now, what has been done to it, and who signed off on the result. The New South Wales Department of Primary Industries used exactly this capability during the 2007 equine influenza emergency response in Australia, where the LIMS database structure and configuration were tailored to handle a surge in sample throughput and to feed information to field and planning staff controlling the outbreak [1].

The LIMS system meaning in practice is "the system of record for specimens." If a piece of software cannot tell you the custody history of a specific tube, it is not a LIMS.

The Three Systems People Confuse

Three acronyms get mixed up constantly: LIMS, LIS, and ELN. They overlap in function but differ in their central object and their regulatory posture.

A LIS (laboratory information system) is the clinical sibling of the LIMS. Its central object is the patient result. LIS platforms in hospital laboratories handle test ordering, result reporting, and increasingly autoverification, where rules encoded in the LIS release results without manual review. A 2026 review in Lab Med describes LIS-based autoverification as a way to improve turnaround time and consistency, and argues that those rules must be governed as controlled, versioned, risk-scored assets because they drift as methods, reagent lots, reference ranges, and interfaces change [2]. That governance framing is the clearest functional difference: an LIS is built around releasing a clinical result to a clinician, so its validation and change-control features are tuned to patient safety.

An ELN (electronic laboratory notebook) is experiment-centric and largely unstructured. Its central object is the experiment or the researcher's daily record. A 2026 study of eLabFTW deployment at University Medicine Halle found that most respondents (78%) had extensive documentation experience, yet 67% cited time burden, 63% cited inefficient organization, and 63% cited difficulty retrieving information, with spreadsheets (87%) and paper notebooks (85%) still dominating daily practice [3]. That is the ELN problem space: capturing narrative methods and observations in a searchable, FAIR-aligned form. An ELN does not normally track chain of custody for a specimen, and it does not enforce accessioning barcodes.

Feature	LIMS	LIS	ELN
Central object	Sample or aliquot	Patient result	Experiment or notebook entry
Primary users	Analytical, veterinary, environmental, food, pharma labs	Hospital and reference clinical labs	Research and academic labs
Sample accessioning with barcodes	Core function	Core function	Rare
Chain of custody	Core function	Present but lighter	Not typically supported
Instrument interfacing	ASTM, HL7, CSV, serial	ASTM, HL7	Manual import or API
QC rules such as Westgard	Built in	Built in	Not typically supported
Result validation and release	Configurable, often multi-level	Central function, autoverification common	Not applicable
Audit trail	Full, tamper-evident	Full, tamper-evident	Version history of notes
Typical regulatory frame	ISO 17025, 21 CFR Part 11, CLIA, CAP	CLIA, CAP, ISO 15189	Institutional data policy, FAIR principles
Structured data model	Highly structured	Highly structured	Semi-structured to free text

The practical rule: if the lab's output is a measurement on a specimen, you want a LIMS or LIS. If the output is a narrative record of what a scientist did, you want an ELN. Many modern research cores run both, with the LIMS handling accessioning and the ELN handling method development notes.

Core Modules of a LIMS

A production LIMS is a stack of modules, and a lab that skips any of them ends up patching the gap with manual work. The modules below are the standard set.

Sample Accessioning and Barcoding

Accessioning is the act of receiving a specimen and creating its permanent record. The LIMS assigns a unique accession number, prints a barcode label, and links the specimen to a submitting client, a patient or animal identifier, a test panel, and a received date and time.

Barcodes matter because they remove transcription as a failure mode. A 2026 postimplementation study of a cytopathology service after an enterprise LIS migration found that amendment rates peaked at 0.47% in the first full operational month and declined to 0.14% by month six, with one wrong-patient misassignment among the reviewed amendments [4]. The authors attribute part of the early spike to altered workflows, unfamiliar templates, and reconfigured terminology during go-live. Barcode-driven accessioning is the standard control against that class of error, because the identifier is scanned rather than typed.

Common symbologies are Code 128 for linear labels and Data Matrix or QR for two-dimensional labels that carry more characters in less space. The LIMS should store the barcode value as the primary key and treat the human-readable number as a secondary convenience.

Chain of Custody

Chain of custody is the unbroken record of who had physical control of a specimen and when. Each transfer is an event: received by, aliquoted by, moved to storage at a recorded temperature, retrieved, consumed, or destroyed.

For forensic, anti-doping, and regulatory residue testing, chain of custody is the legal product of the LIMS. For veterinary and clinical labs it is a quality requirement rather than a courtroom requirement, but the data model is the same. A custody record needs at minimum a timestamp, an actor identity, a location, and a reason code. Free-text custody notes are a red flag in any audit.

Test Ordering and Panel Configuration

Test ordering maps a specimen to the analytical work to be performed. In a mature LIMS, orders are built from panels and profiles rather than entered line by line, so that a single order for a respiratory panel expands into the correct set of individual assays, each with its own method, instrument, and reference interval.

This is where the LIMS encodes laboratory policy. Reflex rules, add-on tests, and cancellation logic all live here. A reflex rule says that if result A crosses a threshold, order test B automatically on the stored aliquot. That logic must be versioned, because changing it changes what the laboratory reports.

Instrument Interfacing

Instrument interfacing is the automated transfer of results from an analyzer to the LIMS. Without it, a technologist retypes every value, which is slow and error-prone.

Two messaging standards dominate. ASTM (historically ASTM E1381 for the low-level protocol and ASTM E1394 for the message content) is the long-standing standard for clinical analyzers and remains common on benchtop chemistry and hematology instruments. HL7 version 2.x, particularly the ORU^R01 observation result message, is used where results must flow into a hospital information system or a public health repository. In veterinary diagnostics, the National Animal Health Laboratory Network built an electronic messaging system that lets participating LIMS automatically send standardized data streams for select agents to a national repository, which is how the U.S. Department of Agriculture tracks high-consequence animal disease outbreaks such as highly pathogenic avian influenza [5].

Interfacing is also where LIMS implementations fail most often. Interface engines, serial settings, character encodings, and unit conventions all have to be validated per instrument, and every method change can invalidate the mapping.

Quality Control and Westgard Rules

QC rules decide whether a run is acceptable before patient or animal results are released. The Westgard multirule framework is the standard approach in clinical and veterinary laboratories: 1-2s as a warning rule, 1-3s and 2-2s as rejection rules, R-4s for range violations, and 4-1s or 10x for trend and shift detection.

A LIMS implements these as configurable rules tied to control material lots. When a rule fires, the run is held and the affected results cannot be released until a supervisor documents the investigation. The same governance logic applies to autoverification rules. The 2026 Lab Med framework recommends treating rule changes as controlled events with a life cycle model, a taxonomy of change triggers, a risk assessment, proportionate verification or revalidation, version control, and monitoring indicators including false-pass and false-hold rates [2]. Any LIMS that lets a user edit a release rule without a version record is not fit for accredited work.

Result Validation and Release

Validation is the human or rule-based decision that a result is fit to report. Most LIMS support multi-level release: a technologist reviews the raw data, a supervisor or pathologist authorizes the final report, and the system records both actions.

Expert rules can be embedded at this stage. A 2026 review in Clin Biochem proposes implementing compensatory-response formulas for acid-base analysis as expert rules inside laboratory information systems or clinical decision support tools, so that the calculated expected compensation is presented alongside the measured blood gas values [6]. That is a clean example of the LIMS doing interpretive work rather than just storage.

Audit Trails

An audit trail is an append-only log of every create, read, update, and delete action on a record, with the user identity, timestamp, and reason for change where required. The critical property is that the trail cannot be edited or deleted by ordinary users, including administrators.

Audit trails are the reason regulated labs cannot run on spreadsheets. A spreadsheet can be changed silently. A compliant LIMS records the before and after value of every field edit.

A Sample-Tracking Workflow

Here is the path a single specimen takes through a LIMS, from arrival to authorized report.

flowchart TD
    A[Specimen arrives] --> B[Accession and barcode]
    B --> C[Chain of custody logged]
    C --> D[Test order created]
    D --> E[Aliquot and route]
    E --> F[Instrument run]
    F --> G[QC rules evaluated]
    G --> H{Run acceptable}
    H -->|No| I[Hold and investigate]
    I --> F
    H -->|Yes| J[Result validation]
    J --> K[Authorized report]
    K --> L[Audit trail sealed]

Step by step:

Arrival. The courier delivers a cooler. The receiving tech opens the manifest in the LIMS.
Accessioning. The LIMS creates an accession number, prints a barcode, and links the specimen to the submitting clinic and animal or patient ID.
Custody. The receiving tech scans the barcode into the custody log. Time and identity are recorded automatically.
Ordering. The LIMS expands the requested panel into individual assays with methods and reference intervals attached.
Aliquoting. If the panel needs serum, EDTA whole blood, and a swab, the LIMS prints child barcodes for each aliquot and records the parent-child relationship.
Analysis. The analyzer runs the batch and transmits results over ASTM or HL7. The LIMS parses the message and maps each analyte to the ordered test.
QC. Control values are evaluated against Westgard rules. A 1-3s violation holds the run.
Validation. The technologist reviews flagged results. The supervisor authorizes release.
Reporting. The LIMS generates the report in the client's required format and transmits it.
Audit. Every action above is written to the audit trail with a timestamp.

The whole sequence is designed so that any single result can be reconstructed months later, including which reagent lot was in use and which analyst was on shift.

Regulatory Drivers

Regulation is the main reason labs buy LIMS software rather than building something in-house. The relevant frameworks differ by sector.

CLIA (Clinical Laboratory Improvement Amendments) governs human clinical testing in the United States. It sets requirements for personnel, proficiency testing, quality control, and result reporting. A clinical LIS must support these, which is why clinical systems emphasize autoverification governance and result release controls [2].

CAP (College of American Pathologists) accreditation adds checklist-driven requirements for document control, method validation, and competency. Digital pathology workflows, for example, must integrate the image management system with the laboratory information system and satisfy CAP and CLIA requirements alongside FDA device rules [7].

ISO 17025 is the general competence standard for testing and calibration laboratories. It is the usual accreditation target for veterinary, environmental, food, and materials testing labs. Its requirements for traceability, method validation, and records map directly onto LIMS modules.

ISO 15189 is the medical laboratory equivalent. The 2026 autoverification framework explicitly integrates ISO 15189:2022 requirements with ISO 22367 and CLSI guidance, and notes that rules must be re-examined as methods, reagent lots, reference ranges, and interfaces change [2].

21 CFR Part 11 is the FDA rule on electronic records and electronic signatures. It requires validated systems, secure audit trails, and controls over who can sign electronically. Any LIMS used to generate data for a regulatory submission in the United States must satisfy it.

GDPR applies when a LIMS holds data from which a living person can be identified. Human clinical and research specimens fall in scope. Veterinary LIMS data usually does not, unless animal identifiers can be linked back to an owner who is a natural person. The practical implication is that data minimization, retention limits, and subject access requests have to be designed into the schema, not bolted on later.

Veterinary Diagnostic Labs Are Not Small Clinical Labs

A veterinary diagnostic laboratory handles problems that a human clinical LIS was never designed for. The 2021 review of AAVLD member laboratories notes that test data from roughly 60 accredited member laboratories are captured by one of 13 LIMS products developed specifically for veterinary diagnostic laboratories [5]. That specialization exists for concrete reasons.

First, species. A single accessioning screen has to accept bovine, equine, porcine, canine, feline, avian, and wildlife identifiers, with species-specific reference intervals attached to the same analyte code. A human LIS assumes one species.

Second, pooled and herd samples. Veterinary submissions frequently arrive as pooled oral fluids, pooled fecal swabs, or bulk tank milk, where one result represents a group rather than an individual. A 2021 study of porcine enteric coronavirus surveillance across multiple veterinary diagnostic laboratories used oral fluids, feces, and fecal swabs as the most frequently submitted specimen types, and applied statistical algorithms to scan the percentage of positive submissions over time, detecting a recurring seasonal peak from December through February for porcine epidemic diarrhea virus, porcine deltacoronavirus, and transmissible gastroenteritis virus [8]. That kind of aggregate surveillance is built on pooled-sample semantics that a clinical LIS does not model.

Third, data sharing. The same review notes that because of the lack of standardized data collection across the LIMS products in use at veterinary diagnostic laboratories, there was no means of summarizing their large data streams for multi-state and national animal health studies, or for near-real-time tracking of the hundreds of other important animal diseases detected routinely [5]. Standardization efforts such as the enteric coronavirus aggregation project exist precisely to bridge that gap [8].

The takeaway for anyone specifying a system: veterinary LIMS selection is driven by species flexibility, pooled-sample support, and outbound messaging to animal health networks, not by the clinical result-release features that dominate human LIS procurement.

Common Mistakes and Limitations

Buying an ELN and calling it a LIMS. If the system cannot record chain of custody for a tube, it will not pass an ISO 17025 or CLIA audit. The documentation burden that ELN users report, including time cost and retrieval difficulty [3], is real but it is a different problem from specimen traceability.

Underestimating go-live disruption. The cytopathology amendment study found amendment rates peaking at 0.47% in the first full operational month after an LIS migration and falling to 0.14% by month six, with nondiagnostic amendments predominating and one wrong-patient misassignment identified [4]. Transitions introduce altered workflows and unfamiliar templates. Plan for a monitored postimplementation period rather than assuming day-one stability.

Treating autoverification rules as set-and-forget. Rules drift as methods, reagent lots, reference ranges, and interfaces change. The recommended control is a life cycle model with version control, risk scoring, and monitoring of false-pass and false-hold rates [2]. A rule that was validated two years ago is not automatically valid today.

Ignoring interface validation. Every instrument connection has to be validated independently, and every method change can break the mapping. Budget engineering time for interfaces, not just for licenses.

Assuming pooled-sample logic is free. If your laboratory tests herd-level specimens, confirm that the LIMS supports pool-level results and pool-to-individual traceability before purchase.

Confusing data aggregation with data standardization. Sending results to a national repository requires agreed vocabularies and message formats, not just an export button. The veterinary experience shows that a dozen LIMS products can each hold excellent data and still be unable to answer a national question without deliberate standardization work [5][8].

Forgetting retention and deletion. GDPR and institutional policy both impose retention limits. A LIMS that can only append and never archive will eventually become a compliance problem.

Overlooking the human factor. The eLabFTW survey found that 90% of respondents emphasized user-friendliness as a key requirement for adoption [3]. The same applies to LIMS. A technically complete system that analysts route around with paper will not produce reliable data.

Frequently Asked Questions

What is a LIMS system in simple terms?

A LIMS is software that tracks laboratory samples and their test results from arrival to final report. It records who handled each specimen, what tests were run, what the instruments returned, and who authorized the result.

What is the difference between a LIMS and a LIS?

A LIMS is sample-centric and serves analytical, veterinary, environmental, and industrial labs. A LIS is result-centric and serves clinical laboratories that report patient results to clinicians, with autoverification and result release as central functions [2].

What is the difference between a LIMS and an ELN?

A LIMS tracks specimens, custody, tests, and results in a structured database. An ELN captures narrative experimental records, methods, and observations, and is typically semi-structured or free text [3].

Do I need a LIMS if I already use a spreadsheet?

If your laboratory is accredited or regulated, yes. Spreadsheets cannot provide tamper-evident audit trails, versioned QC rules, or chain of custody, all of which are required by frameworks such as ISO 17025, CLIA, and 21 CFR Part 11.

What is instrument interfacing in a LIMS?

It is the automated transfer of analyzer results into the LIMS using messaging standards such as ASTM or HL7. It removes manual transcription, which is a major source of result errors.

What are Westgard rules?

Westgard rules are statistical QC acceptance rules applied to control material measurements. Common rules include 1-3s and 2-2s for rejection and 4-1s or 10x for detecting trends and shifts. A LIMS enforces them automatically.

Why do veterinary labs need different LIMS features than human clinical labs?

Veterinary laboratories handle multiple species with different reference intervals and frequently process pooled herd samples. AAVLD member laboratories use LIMS products built specifically for these requirements [5][8].

What is an audit trail in a LIMS?

It is an append-only log of every action taken on a record, including the user, timestamp, and changed values. Regulators require it because it makes data modification visible and attributable.