Back to blog

    LIS EMR Integration: How Lab Orders and Results Connect

    Technologist reviewing laboratory order and result data

    LIS EMR integration connects the laboratory’s information system (LIS) to your electronic medical record (EMR), so a test ordered in the chart reaches the lab without re-keying and the approved result returns to the same patient record. For a practice, a long-term care facility or a research site, the integration works when the lab is chosen for it, the data is mapped to shared standards, and the interface is tested and watched after go-live. At KoHealth Labs, LIS and EHR integration is one of the services we provide alongside specimen pickup, electronic results reporting and dedicated onboarding and training.

    This guide explains what each system does, how an order travels, which standards matter, how to test before go-live and how to keep the interface healthy afterward.

    Kohealth Labs
    kohealthlabs.com
    Connect Lab Orders and Results
    KoHealth Labs provides LIS and EHR integration alongside electronic results reporting, specimen services and dedicated onboarding and training.
    Visit

    TL;DR

    • The EMR holds the patient chart and places the order. The LIS tracks that order inside the lab and releases the result.
    • A typical electronic lab flow runs through ten steps, from intake in the EHR to result sharing with the provider, the patient and, at times, public health agencies.
    • Shared vocabularies such as LOINC and message formats such as HL7 v2 keep a result from being misread on arrival.
    • Test examples from every discipline before go-live, then keep monitoring interface error logs afterward.
    • Choose a lab that treats integration, onboarding and training as part of the service, not an extra project.

    What LIS and EMR each do

    An EMR is the clinic’s digital chart: demographics, history, orders, notes and results. An LIS is software built for the laboratory itself. APHL’s integration guide describes it as a system created for laboratories to support workflow and track data from the start to the end of testing. The same guide says the LIS must receive test requests and return results to the care provider’s system.

    The split matters because an EMR cannot follow an order through the lab. A University of Washington health information systems module notes that an EMR can generate a lab order but will not track it as it is processed, so the lab tracks the order on its own with an LIS. If you want a plain picture of what happens to a specimen once it leaves your office, what happens to a specimen at the lab walks through the accessioning and testing stages that an LIS records.

    Integration is the bridge between the two. Without it, someone prints or faxes requisitions, someone else types results into the chart, and every hand-off is a place for a transcription error or a delay.

    What LIS and EMR each do

    How an order travels from chart to result

    The U.S. Office of the National Coordinator for Health IT (ONC, now part of ASTP) describes the flow in a Report to Congress on electronic ordering and reporting of lab results. It runs ten steps. In plain terms:

    1. Patient information is recorded in the EHR.
    2. The provider decides on testing and, where possible, orders electronically.
    3. The specimen is collected and reaches the lab.
    4. The LIS receives the order information.
    5. The lab analyzes the specimen.
    6. Results are transferred into the LIS.
    7. Results are reviewed and approved there.
    8. The approved result goes to the ordering provider.
    9. The patient can receive it.
    10. Public health agencies and health information networks receive it when required.

    Two practical points follow. First, the physical steps, collection and transport, sit between the electronic ones. A clean interface does not help if the specimen arrives late or unlabeled, so pickup logistics belong in the same conversation as the interface. Second, the same report states that there is no federal requirement that a lab order be received electronically or follow one specific national standard. Your interface is therefore something you agree with your lab, not something you can assume the law has settled for you.

    The standards behind a clean connection

    Two systems can exchange data only if they agree on the format of the message and the meaning of each field. The ASTP report says that LOINC (the code set that names each lab test and observation) and UCUM (the standard for units of measure) are widely adopted by providers and laboratories. It also says HL7 v2 messages and C-CDA documents are used extensively, and that EHRs moderately implement the HL7 v2.5.1 Laboratory Results Interface (LRI) and Electronic Laboratory Reporting (ELR) guides from the ONC Certification Program.

    Roles of key laboratory data exchange standards

    The VA’s technology reference page for the HL7 V2 Laboratory Results Interface explains what the LRI guide covers: communicating lab results from a reference laboratory’s LIS to an EHR, a public health system or another lab, including microbiology and clinical genomics. For you, that translates into a simple expectation: results should arrive as structured, coded data, not as a PDF someone must read and re-enter.

    Why LOINC mapping comes first

    One test can carry different local names in the lab and in your EMR. Mapping both to a LOINC code is what lets a result land in the correct field and trend over time. Mapping every test at once is rarely realistic, so start with the highest-volume tests. We cover this in our guide to LOINC mapping for labs, which explains why the high-volume tests go first.

    What the rules say about certification and information blocking

    The EHR vendor’s side of the connection sits under ONC’s certification program. ONC’s program overview states that certified health IT developers may not engage in information blocking, as defined in 45 CFR 171.103, and that violations can lead to certification termination, a certification ban and civil monetary penalties. The structure of those certification criteria and maintenance conditions is laid out in 45 CFR Part 170. In practice, a vendor cannot reasonably refuse to let you exchange lab data, though building the interface still takes planning. ONC has also been weighing lab-specific criteria: its HTI-1 task force slides record that the ordering and results implementation guides were proposed earlier but not adopted in the 2015 Final Rule. Ask your EHR vendor for its current certified capabilities, since they change with each rule.

    Planning an integration that works at go-live

    A good project follows a sequence. Our own walkthrough, standards-first EMR lab integration in seven stages, covers it in detail. The shape is:

    • Define scope. List the test menu, the order sources (each provider, each site, each mobile team) and who receives results.
    • Confirm the EMR’s interface options. Find out which message types your EMR vendor supports for orders and results, and who on their side owns the build.
    • Map the data. Agree on test codes, units, reference ranges and abnormal flags.
    • Build and test in a non-production environment. Run real-looking orders through the entire loop.
    • Train staff. Front desk, medical assistants and providers each use a different part of the order screen.
    • Go live with a small pilot. We describe a ten-order pilot approach for clinics, which finds mapping mistakes while the volume is still small.

    Test examples from every discipline

    Testing is where integrations are won. The Indian Health Service’s laboratory training materials, based on CAP checklist requirement GEN.48500, call for verifying that patient results are transmitted accurately from data entry to the patient report before go-live and every two years afterward. At implementation they require at least two example reports from each applicable discipline. Later checks need at least two examples from at least four disciplines. The examples should include individual results, panels, abnormal flags, comments and footnotes, and corrected results.

    That last item is the one teams forget. A corrected result must replace the original in the receiving system and be visible as a correction, not appear as a second, conflicting value. Include a corrected result in your test script on day one.

    A simple acceptance checklist for a practice:

    • Order placed in the EMR appears in the lab’s system with the right patient, test and collection date.
    • Panels arrive with every component, not just the headline value.
    • Units and reference ranges match what the lab reports.
    • Abnormal flags show in the chart.
    • A corrected result replaces the earlier one.
    • Results route to the right ordering provider, including for covering clinicians.

    Keeping the interface healthy after launch

    An interface is not finished at go-live. ONC’s SAFER guide on system management recommends that interface error logs be monitored and errors investigated and fixed promptly. It also advises monitoring interfaces for usage, designing them for expected data volumes and documenting performance requirements. It recommends keeping a data dictionary and an interface data map, and using automated monitoring of key settings where possible.

    For a clinic manager, that becomes a short routine:

    • Assign one named person to review the interface error queue each working day.
    • Keep the data map current whenever a test is added or renamed.
    • Agree with the lab on how failed, delayed or corrected messages are reported to you.
    • Recheck sample results on a schedule, and again after any EMR or LIS upgrade.

    As a general rule, most integration trouble comes from the same few places: patient identifiers that do not match between systems, test codes that were never mapped, and updates on one side that nobody told the other side about. A named contact at the lab who answers quickly shortens the time from “result missing” to “result fixed.”

    What changes by type of organization

    Independent practices and multi-physician groups. The aim is fewer manual steps for front-desk and clinical staff. Start with your top ten ordered tests, then expand.

    Urgent care and specialty clinics. Speed of result return is what the provider feels. Make sure results route to whoever sees the patient, not only the original ordering provider.

    Skilled nursing, assisted living and home health. Orders come from many prescribers and specimens are often collected away from a clinic. The interface, the courier and mobile collection need to work as one chain.

    CROs, sponsors and research sites. Study data needs consistent coding and clean delivery to the study’s data systems. Our ePRO and lab data integration guide covers the standards-first approach for clinicians and sponsors.

    Public health reporting. APHL’s guide frames electronic exchange as a benefit for public health as well as care, because in outbreak management lab results must exist before public health can act, and electronic transfer avoids manual transcription delays.

    Our perspective

    Most integration projects we hear about stall for the same reason: the lab is treated as a vendor at the end of the project, when it should be a partner at the start. The interface is only one part. Courier pickup, mobile phlebotomy, result delivery and training for your staff decide whether a connected lab actually feels faster on a Tuesday morning.

    That is why we offer LIS and EHR integration together with specimen pickup, electronic results reporting, a provider portal and dedicated onboarding and training. We work as a primary lab or as an additional resource for specialized testing, and we prioritize direct communication, fast results and solutions tailored to each provider or research organization.

    If you are choosing between a big national lab and a smaller partner, ask who will answer when a result does not show up in your chart. Our aim is that the answer is a person who already knows your setup.

    Kohealth Labs

    Connecting with KoHealth Labs

    If you run a practice, a facility or a study and want laboratory testing connected to your records, KoHealth Labs offers laboratory diagnostics with LIS and EHR integration, specimen pickup and electronic results reporting, backed by onboarding and training for your team. We serve healthcare practices, telehealth and wellness programs, and clinical research organizations, with a presence in Dallas, Plano and across Texas.

    Kohealth Labs

    Research teams can see how we support study protocols and specimen logistics on our clinical trials laboratory page. Practices and facilities can start from our main site. For patients who cannot travel to a draw site, our mobile phlebotomy request page is the place to begin.

    FAQ

    What does LIS EMR integration mean?

    It means the laboratory’s information system and your electronic medical record exchange orders and results automatically. The provider orders in the chart, the lab receives the order in its LIS, and the approved result returns to the patient record. It removes re-typing and paper hand-offs.

    What is the difference between an LIS and an EMR?

    The EMR is the patient’s clinical chart, used by providers and clinic staff. The LIS is the laboratory’s own system for tracking each order and specimen through testing and releasing the result. The EMR can create an order, but the LIS follows it inside the lab.

    Which standards are used to connect them?

    HL7 v2 messages are used extensively, and LOINC and UCUM are widely adopted for naming tests and units, according to ASTP’s 2024 report to Congress. The HL7 v2.5.1 results interface guide describes how lab results flow from the lab’s LIS to an EHR. Your EMR vendor and lab agree on the exact specification for your interface.

    How should we test before go-live?

    Run example reports from every discipline you will use, including panels, abnormal flags, comments and a corrected result. The Indian Health Service materials based on the CAP checklist call for at least two examples per applicable discipline at implementation and repeat checks every two years. A small pilot of live orders afterward catches mapping gaps early.

    Who should watch the interface after launch?

    Name one person in your organization to review interface error logs on working days, and agree with your lab on how failed or delayed messages are reported. ONC’s SAFER guide recommends prompt investigation and correction of interface errors.

    Sources

    For more information about our diagnostic testing, clinical research laboratory services, or partnership opportunities, visit https://kohealthlabs.com or contact KoHealth Labs at (469) 792-8439 and ask for Amy Patterson.