LIMS integration with a hospital EHR is not a single interface but a set of coordinated decisions about workflow direction, message standards, terminology, and validation. The Association of Public Health Laboratories (APHL) describes the core exchange as a clinician working in the EHR seeing available tests, placing an electronic order, and the laboratory returning a result that lands in the patient record [1]. The same guide distinguishes two transport patterns: the EHR pushes orders to the LIS and the LIS pushes results back, or the EHR pulls results from the LIS on request [1]. A practical integration therefore requires agreeing on identifiers, data elements, and communication conventions before configuration begins [1]. This article explains those decision points, documents what published sources establish, and identifies where evidence remains thin.
The Named Workflow: Order, Accession, Result, and Referral
The APHL guide frames the LIS–EMR connection as one of the most logical and important system interactions related to laboratory work. A clinician working on a patient record in the EMR can see exactly which tests the laboratory offers and request them directly. The collection facility and laboratory then receive a precise specimen list and an electronic list of tests to perform [1]. If the local laboratory cannot perform a test at that time, the specimen can be referred to another laboratory with that capability, and the data are transmitted electronically to that laboratory's LIS [1].
Specimen tracking becomes essential when the hospital information system and LIS are integrated. The laboratory can know what specimens the hospital has collected, when they were collected, and when they were shipped. The hospital can track delivery, testing status, and whether results have been approved and released [1]. This bidirectional visibility is the operational reason many hospitals treat integration as a specimen logistics problem rather than only a messaging problem. The workflow therefore spans ordering, accessioning, testing, result release, and referral loops, each with its own data elements and failure modes.
Push and Pull Models Are a Design Choice, Not a Default
APHL's integration guide presents two communication models. In the push model, the EMR pushes a test order request to the LIS, the laboratory conducts testing, and the LIS pushes results back into the EMR. In the pull model, the EMR sends a test results request and the LIS responds with the laboratory test results [1]. The distinction matters because it changes where the initiative for a transaction originates and which system must be available at a given moment. A pull model can suit an EMR that needs on-demand result retrieval, while a push model fits a laboratory that finalizes results and expects them to arrive in the chart without a separate request.
Vendor documentation adds a practical layer. LIMS IQ states that most production interfaces are bidirectional: HL7 ORM messages flow from the EHR into accessioning, and ORU messages return finalized and corrected results to the ordering provider. Unidirectional setups, such as results only or orders only, are supported when the EHR side cannot accept inbound traffic or when the lab is read-only [2]. This is a vendor claim about its own product, not an industry statistic. It does, however, illustrate that the push/pull decision is often constrained by what the EHR side can technically accept, not only by laboratory preference.
A Suggested Evaluation Scenario for a Hospital Reference Lab
A hospital laboratory could evaluate an integration by scripting a single high-priority test order through the full loop. The suggested scenario: create a patient record in a non-production EHR, send an HL7 v2 ORM order for a quantitative chemistry test, confirm the LIS accessions the specimen with the correct facility and patient identifiers, then return an ORU result with a corrected value and verify the audit trail records both the original and corrected result. This mirrors the build and test cycle LIMS IQ describes, which includes scripted scenarios for reflex orders and corrected results before production cutover [2].
The evaluation should also test terminology consistency. The JAMIA Open case report found inconsistent LOINC code use and different HL7 v2 versions at the same institution [7], so a hospital should ask the vendor to demonstrate how the interface handles a mismatched LOINC code or a legacy HL7 version. APHL's guidance to collect current standards and define how systems communicate before installation [1] supports making this a written acceptance criterion rather than a post-go-live discovery. This scenario is a suggestion for evaluation design, not a report of testing performed.
HL7 v2 and FHIR: Two Standards with Different Operating Assumptions
The dominant clinical interface messages remain HL7 v2 ORM for orders and ORU for results. LIMS IQ describes these as the workhorse messages for most clinical interfaces, while also supporting FHIR resources such as ServiceRequest, Specimen, and DiagnosticReport for partners that prefer a REST-based exchange. The vendor states that the right choice depends on what the EHR side supports and the throughput requirements [2]. This is a product-level statement, but it reflects a broader pattern: HL7 v2 is entrenched in hospital EHRs, while FHIR offers a resource-based alternative that some implementers adopt when the EHR can consume it.
The OpenMRS implementer guide describes a FHIR-based Lab Order and Results workflow using the FHIR Workflow Module and suggested communication patterns. It notes that some contexts may still rely on older messaging standards in local systems [3]. The guide recommends LOINC as the international standard for the shared terminology set of orders and results needed for a given context [3]. A documented case report from two healthcare institutions found inconsistent LOINC code use and different HL7 v2 versions being used at the same institution for ordering and resulting [7]. That finding underscores a practical risk: selecting a standard is not the same as enforcing consistent use of it across interfaces.
Terminology, Identifiers, and the Hidden Cost of Local Conventions
APHL advises implementers to coordinate lists of standardized values and terminology within their country, in addition to general international standards for specific data elements. These include healthcare facility identification codes, laboratory identification codes, unique patient identifiers, and specimen identifications. The guide warns that unless otherwise specified, a system provider will likely use its own naming conventions during installation, which can create confusion later when trying to exchange, centralize, or analyze data [1]. Both sides must review all data elements being exchanged and discuss standard conventions during the definition of communication between two systems [1].
The OpenMRS guide makes terminology mapping an explicit implementation step: map all relevant concepts and identifiers needed between EMR and LIS, then identify the data exchange method based on the health information exchange and infrastructure context [3]. The case report from the University of Nebraska Medical Center and Children's Health in Dallas examined HL7 v2 messages between the EHR and LIS and analyzer messages between the LIS and IVD analyzers for nine laboratory tests. Review identified inconsistent LOINC code use and different HL7 v2 versions at the same institution [7]. The authors concluded that consistent test identification and result value transmission would require enhanced EHR functionality and adherence to SHIELD (Systemic Harmonization and Interoperability Enhancement for Laboratory Data) recommendations [7].
What the Evidence Does and Does Not Establish
The CDC's Public Health Electronic Test Orders and Results (ETOR) initiative provides one of the few documented outcome examples. The CDC states that manual or paper-based test ordering and result delivery can introduce transcription errors and delay time-sensitive results, and that ETOR solutions address these problems by streamlining data exchange [6]. For newborn screening, the CDC reports that nine states, eight public labs, and 97 healthcare organizations were involved, with a 42% faster results figure and a 93% public health laboratory reduction figure [6]. The source does not define the exact denominator or measurement period for those percentages, so they should be treated as program-reported impacts rather than controlled study findings.
A separate CDC example describes Fairbanks Memorial Hospital in Alaska, where newborn screening previously relied on manual data entry and mailed paperwork to the Iowa Public Health Laboratory, taking on average 12 days to receive results. After electronically transmitting laboratory information between the EHR and LIMS using the Detor solution, turnaround time was reduced to six days [6]. This is a single documented implementation, not a generalizable market result. The JAMIA Open case report is similarly bounded: it examined nine low-complexity, FDA-cleared assays that do not require pathologist interpretation, and the authors explicitly list this as a limitation [7]. Neither source supports broad claims about clinical efficacy or universal integration benefits.
Sources & references
- LIS Integration Guide · aphl.org
- EMR/EHR Interfaces for Clinical Labs | LIMS IQ · limsiq.com
- Integration with LIS: Implementer's Guide - Documentation - OpenMRS Wiki · openmrs.atlassian.net
- LIMS and EHR Integration with QCI Interpret | Unify molecular data · digitalinsights.qiagen.com
- E1578 Standard Guide for Laboratory Informatics - ASTM · store.astm.org
- About Public Health Electronic Test Orders and Results Initiative | Division of Laboratory Systems (DLS) | CDC · www.cdc.gov
- Analysis of laboratory data transmission between two healthcare institutions using a widely used point-to-point health information exchange platform: a case report - PMC · pmc.ncbi.nlm.nih.gov
- Public Health Electronic Test Orders and Results (ETOR) Initiative · cdc.gov