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 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.
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.
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.
- Hematology & coagulation — bidirectional CBC and coag connections, including reflex from hematology rules.
- Molecular & NGS — instrument output capture, plate-map round-trip, library-prep tracking.
- Toxicology — LC-MS/MS, GC-MS, and immunoassay screen/confirm workflows.
- Microbiology — identification, susceptibility, and culture systems.
- 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:
- 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.
- 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.
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 Public Health LIMS for how this fits into the full public-health workflow.
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.
- 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:
- Discovery — capture sample messages, list orderables/codes, agree on transport (MLLP, HTTPS, SFTP).
- Mapping — orderable map, demographics map, units, abnormal-flag conventions, Z-segment use.
- Build — interface configuration in a non-production tenant; LIMS IQ team owns this.
- Validation — end-to-end test cases, ack-pattern verification, rule-edge cases, replay testing.
- Cutover — supervised go-live, message-log monitoring, fast-path defect handling.
- Hypercare — first 1–2 weeks of monitored exchange; promotion to standard support.
A single EMR connection typically runs 3–8 weeks once the EMR counterpart is engaged. Instrument interfaces with pre-validated drivers run in 1–3 weeks. ELR per agency runs 2–4 weeks. Multi-interface projects parallelize during the implementation window — see the LIS implementation timeline guide.
Where to next
- Building an EMR or HL7 connection: HL7 LIS integration and the practical HL7 guide.
- Standing up instrument interfaces: instrument integrations.
- Connecting billing or RCM: billing & revenue cycle and LIS billing integration.
- Reporting to public-health agencies: Public Health LIMS.
- Talk through your specific partner mix: request a demo.