Customer Portal Help Desk: 1-800-834-8618
LIMS IQ Integrations DOC INTEGRATIONS
REV 2026-08

LIS Integrations — Where LIMS IQ Connects

LIS and LIMS integration hub for EMR/EHR, HL7 and FHIR messaging, instruments, billing, ELR, and reference labs — see what LIMS IQ supports and how it connects.

Request a demo Read the guide

Quick answer: LIS integrations are the connections between the laboratory information system and external systems — EMRs and reference labs via HL7 v2.x and FHIR R4, analyzers via ASTM and vendor protocols, billing via ANSI 837, ELR to public health agencies, and SSO via SAML/OIDC. Each integration is configured, monitored, and validated by the vendor.

A clinical LIS lives or dies by its integrations. Orders enter from EMRs and portals, results flow back to clinicians, instruments send raw values, billing systems consume charges, public-health agencies require electronic laboratory reporting (ELR), and reference labs need bidirectional message exchange. LIMS IQ is built so all of this runs as a managed cloud service, not a lab-IT science project.

Searching for LIMS integration? You are in the right place. In patient-testing labs the system of record is conventionally called an LIS, while “LIMS” usually refers to research and industrial sample management — the clinical LIS vs research LIMS comparison unpacks the terminology. In a clinical laboratory, LIMS integration means exactly the connections on this page: instruments, EMR/EHR ordering and resulting, billing, and public-health reporting.

What LIMS IQ connects to

Category Examples Standards & transports
EMR / EHR Hospital and clinic EMRs, ambulatory products, specialty practice systems HL7 v2 (ORM, ORU, ADT), FHIR R4, MLLP, HTTPS, SFTP
Instruments Chemistry, hematology, immunoassay, coagulation, molecular, NGS, toxicology, urinalysis, microbiology ASTM, HL7 v2, vendor-proprietary, file-based
Reference labs Send-out routing and result return HL7 v2 ORM/ORU, secure file transfer
Public health ELR for reportable conditions, COVID, sexually transmitted infections, etc. HL7 v2.5.1 / 2.6, jurisdiction-specific rules
Billing / RCM Direct partner billing, clearinghouse claim submission ANSI 837P / 837I, eligibility 270/271, ERA 835
Document & notification Result PDFs, fax, secure email, portal links PDF, sFTP, signed URLs
Identity SSO and federated login SAML 2.0, OIDC

EMR & EHR integration

EMR integration is the highest-impact connection in the system. LIMS IQ supports the full clinical loop:

  • ORM (orders) — orderable mapping, specimen requirements, container/collection routing, and rejection handling.
  • ORU (results) — patient-friendly and structured result delivery, reflex testing, amendment messaging, abnormal flags.
  • ADT (demographics) — patient merge handling, MRN reconciliation, and insurance/encounter context.
  • MDM (documents) — signed PDF reports back to the EMR document store.
  • DFT (charges) — charge capture into the hospital’s billing system where LIMS IQ is not handling RCM directly.

The HL7 LIS integration feature page and the HL7 practical guide cover the deeper mechanics — message types, ack patterns, Z-segments, mapping pitfalls, and validation strategy. The EMR/EHR integration page covers the EMR-specific side.

FHIR for modern endpoints

Where partners support FHIR R4, LIMS IQ exchanges:

  • ServiceRequest ↔ HL7 ORM
  • Observation ↔ HL7 ORU
  • Patient / Encounter ↔ HL7 ADT
  • DiagnosticReport for full result documents
  • Coverage / ChargeItem for billing-context exchange

FHIR is layered alongside HL7 v2 — labs do not need to choose. Most clinical exchange remains HL7 v2.x today, with FHIR adopted incrementally as partners enable it. The FHIR for clinical labs guide walks through each resource in detail and shows how a FHIR-based lab interface flow lines up against the equivalent HL7 v2 message set.

Instrument integration

Bench instruments are the second-largest integration footprint. LIMS IQ runs analyzer interfaces through a managed engine that bridges bench protocols (often ASTM or proprietary) to the cloud LIS. Coverage spans:

  • Chemistry & immunoassay — common high-throughput analyzers across the major vendors. See the chemistry LIS guide for how bidirectional analyzer interfacing drives autoverification, delta and critical checks, and Levey-Jennings QC gating before result release.
  • Hematology & coagulation — bidirectional CBC and coag connections, including reflex from hematology rules. See the hematology LIS guide for how analyzer integration drives autoverification, delta checks, and reflex slide review.
  • Molecular & NGS — instrument output capture, plate-map round-trip, library-prep tracking. See the molecular LIS guide for the full PCR / NGS / bioinformatics integration workflow.
  • Toxicology — LC-MS/MS, GC-MS, and immunoassay screen/confirm workflows.
  • Microbiology — identification, susceptibility, and culture systems. See the microbiology LIS guide for how ID/AST and blood-culture instrument results drive the bench workcard, automated CLSI/EUCAST interpretation, and cumulative antibiograms.
  • Urinalysis — strip readers and microscopy systems.

The instrument integrations feature page lists current coverage; less-common analyzers are added via a defined interface-build process during implementation.

Billing & revenue-cycle integration

The LIS is where charges originate. LIMS IQ supports two patterns:

  1. Integrated billing — LIMS IQ captures charges, runs eligibility, applies payer rules and modifiers, attaches ICD-10, and posts to a billing partner or clearinghouse. See billing & revenue cycle and LIS billing integration.
  2. External billing — LIMS IQ exports clean ANSI 837 claims (or DFT messages to a hospital billing system) for an external billing service to file. The lab still gets denial-reducing edits at order time. See the LIS billing integration and claim-denial playbook for how those order-time edits map to the clean-claim lifecycle that keeps denials down.

In both models, eligibility (270/271) is checked before the specimen is processed where possible, and ERA (835) is consumed back into the LIS for posting and reporting.

Public-health ELR

Reportable testing has to flow to public-health agencies in a structured format. LIMS IQ generates ELR messages in the HL7 v2.5.1 / 2.6 formats agencies require, with:

  • Reportable-condition rules per agency and per jurisdiction.
  • Address geocoding and patient demographics conformance.
  • Message replay and re-send for partial outages.
  • Onboarding by agency as the lab adds reportable testing.

See the public health LIMS solution for the broader public health workflow and product surface, and the public health LIMS ELR workflow guide for the end-to-end reportable-condition lifecycle (rule evaluation, message generation, jurisdiction routing, and ACK/NAK reconciliation).

Client and patient connectivity

Not every ordering source is an EMR. LIMS IQ provides:

  • Client portal — for ordering clients without an integrated EMR: order entry, results, eligibility, history. It is the self-service counterpart to the HL7 channel — the same orders and results an integrated clinic exchanges over ORM/ORU, delivered through a browser to clinics that have no interface, while deflecting the result-status and resend calls those clinics would otherwise place.
  • Patient portal — for direct-to-consumer and patient-facing programs.
  • Mobile phlebotomy tracker — for in-home and mobile draw programs.

These run on the same LIMS IQ tenant — no separate sub-product, no separate login.

Identity & SSO

LIMS IQ supports SAML 2.0 and OIDC federated login so labs can plug the platform into their identity provider — Okta, Azure AD, Google Workspace, and other IdPs. Roles map from IdP groups; offboarding is immediate when a user is disabled in the IdP.

How an integration project actually runs

Every integration follows roughly the same shape, sized to the partner:

  1. Discovery — capture sample messages, list orderables/codes, agree on transport (MLLP, HTTPS, SFTP).
  2. Mapping — orderable map, demographics map, units, abnormal-flag conventions, Z-segment use.
  3. Build — interface configuration in a non-production tenant; LIMS IQ team owns this.
  4. Validation — end-to-end test cases, ack-pattern verification, rule-edge cases, replay testing.
  5. Cutover — supervised go-live, message-log monitoring, fast-path defect handling.
  6. Hypercare — monitored exchange after cutover; promotion to standard support once the connection is stable.

Delivery timing is scoped during discovery rather than promised per interface. Complete message samples, available transports, code mappings, validation cases, and a ready partner test environment reduce uncertainty; unusual formats, incomplete mappings, or external scheduling dependencies add work. Multiple connections can proceed in parallel within the broader project — see the LIS implementation timeline guide for the phased implementation plan.

Where to next

Frequently asked

Is LIMS integration the same as LIS integration?
In a clinical laboratory, yes — the terms describe the same work. LIS is the conventional name for the system of record in patient-testing labs, while LIMS usually refers to research and industrial sample management, but searchers and vendors use the terms interchangeably. LIMS integration for a clinical lab covers instrument interfaces, EMR/EHR ordering and resulting over HL7 or FHIR, billing and claim export, and electronic laboratory reporting to public-health agencies — all of which LIMS IQ delivers as a managed service.
What integration standards does LIMS IQ support?
LIMS IQ supports HL7 v2 (ORM, ORU, ADT, DFT, MDM, ELR), FHIR R4 for modern EMR endpoints, ASTM and proprietary instrument protocols via a managed interface engine, ANSI 837P/837I billing export, and SFTP/HTTPS/MLLP transport. Connections are configured by the LIMS IQ team, not left to lab IT.
How are EMR/EHR integrations built?
Each EMR connection follows the same pattern: discovery (message samples, code mapping, transport), interface build (mapping, ack handling, retries), validation (round-trip ORM → ORU testing in a non-production environment), and go-live with monitored cutover. We support the major hospital and clinic EMRs as well as smaller ambulatory products.
Which instruments does LIMS IQ connect to?
LIMS IQ supports bidirectional interfaces across chemistry, hematology, immunoassay, coagulation, urinalysis, microbiology, molecular, NGS, and toxicology analyzers via a managed interface engine. Common drivers are pre-validated; less-common analyzers are added through a defined interface-build process. See the instrument integrations feature page for current coverage.
How does LIS billing integration work?
LIMS IQ captures charges at order time with payer, eligibility, ABN, modifiers, and ICD-10 codes. The system can post charges directly to a partner billing/RCM system, export ANSI 837P/837I claims to a clearinghouse, or feed a hospital’s GL — depending on the lab’s revenue model. Eligibility checks and clean-claim validation reduce denials before the claim is filed.
Can LIMS IQ send ELR to public-health agencies?
Yes. LIMS IQ generates ELR (electronic laboratory reporting) messages in the HL7 v2.5.1 / 2.6 formats most state and CDC programs require, with reportable-condition rules, jurisdiction routing, and message replay. Agencies can be onboarded individually as the lab adds reportable testing.
What determines how long an integration takes?
Integration timing is scoped during discovery because it depends on the partner’s message samples and test environment, transport setup, code mapping, validation cases, and responsiveness. Reusable connection patterns and existing instrument parsers can reduce configuration work; unusual formats or incomplete mappings add it. Multiple connections can proceed in parallel within the broader implementation plan.