Laboratory (LIS) Integration Diagram
Laboratory integration has two halves: instrument connectivity inside the lab, and order and result messaging with the rest of the hospital. This diagram shows both. Analyzers connect to lab middleware using ASTM (CLSI LIS2-A2) or HL7, point-of-care devices report through POCT middleware, the LIS manages orders and results, and the EHR and blood bank exchange HL7 messages with the LIS.
Free, no sign-up. The builder runs in your browser; nothing is uploaded.
What this diagram shows
Use it to plan an LIS replacement, document instrument connectivity, or explain the lab’s place in the hospital’s integration landscape.
Components
Analyzers
Chemistry, hematology and other instruments. Many speak ASTM E1394 (now CLSI LIS2-A2); newer ones support HL7 v2 under the IHE LAW profile.
Lab middleware
Connects instruments, applies autoverification rules, manages reruns and passes verified results to the LIS.
POCT devices
Glucose meters, blood gas analyzers and other bedside devices.
POCT middleware
Collects results from devices using POCT1-A, manages operator certification and device QC, and sends results to the LIS.
LIS
Laboratory information system — accessioning, worklists, result validation and reporting.
EHR / EMR
Places lab orders and displays results.
Blood bank
Transfusion system — blood type, antibody history and product issue — integrated with the LIS.
How the data flows
Order
The EHR sends a lab order to the LIS as HL7 OML^O21 (or ORM^O01 on older interfaces).
Download to instruments
The LIS or middleware sends the test request to the analyzer when the specimen barcode is scanned (host query) or in advance (broadcast).
Results from instruments
Analyzers send results to the middleware — as ASTM records or HL7 OUL messages — where autoverification rules release normal results.
Point of care
Bedside devices dock or connect to the POCT middleware (POCT1-A), which forwards results to the LIS as HL7 ORU^R30 or ORU^R01.
Results to the EHR
The LIS sends verified results to the EHR as ORU^R01.
Blood bank
Orders and results for type & screen and crossmatch flow between the LIS and the blood bank system.
Interfaces in this diagram
Every connection in the diagram, ready to copy into an interface register or test plan.
| # | From | To | Protocol | Detail |
|---|---|---|---|---|
| 1 | Analyzer (Chemistry) | →Lab Middleware (Autoverification) | TCP/IP | LIS2-A2 |
| 2 | Analyzer (Hematology) | →Lab Middleware (Autoverification) | HL7 | LAW |
| 3 | Lab Middleware (Autoverification) | ↔LIS (Lab Information) | HL7 | OML · OUL |
| 4 | POCT Devices (Glucose · Blood gas) | →POCT Middleware (POCT1-A Hub) | TCP/IP | POCT1-A |
| 5 | POCT Middleware (POCT1-A Hub) | →LIS (Lab Information) | HL7 | ORU^R30 |
| 6 | LIS (Lab Information) | ↔EHR / EMR (Orders & Results) | HL7 | OML · ORU |
| 7 | LIS (Lab Information) | ↔Blood Bank (Transfusion) | HL7 | OML · ORU |
Design considerations
- Inventory every instrument with its protocol, connection type (serial or TCP/IP) and middleware driver before an LIS change.
- Validate units, reference ranges and LOINC codes end to end — a mapping error here reaches the patient chart.
- Document autoverification rules alongside the diagram; they are part of the clinical safety case.
- POCT results need a reliable patient ID at the bedside — scanning the wristband is the control that matters.
Related reference
- POCT Data Management: Integrating POCT with LIS →
- HL7 OML^O21 — Laboratory Order →
- HL7 ORU^R30 — POCT Observation →
- HL7 OBX Segment →
- HL7 Interface Engine: 10 Best Practices →
- LIS — Lab Diagnostics →
- POCT Middleware — Lab Diagnostics →
- Lab Automation Interfaces — Lab Diagnostics →
- Blood Bank — Lab Diagnostics →
Frequently asked questions
What is LIS integration?
LIS integration connects the laboratory information system to instruments (analyzers and POCT devices) and to hospital systems (EHR, billing, blood bank), so orders flow in and verified results flow out without manual transcription.
What protocols do lab analyzers use?
Many analyzers use the ASTM E1394 message format (now CLSI LIS2-A2) over serial or TCP/IP, with low-level framing from ASTM E1381 / CLSI LIS1-A. Newer instruments increasingly support HL7 v2 messages defined by the IHE Laboratory Analytical Workflow (LAW) profile.
What is lab middleware?
Lab middleware sits between the instruments and the LIS. It normalises instrument protocols, applies autoverification and rerun rules, and gives the lab one workstation for result review.
What is POCT1-A?
POCT1-A (CLSI POCT01) is the connectivity standard for point-of-care testing devices. It defines how devices send results, QC data and operator information to POCT data management software.
Make it match your site
Rename systems, add your AE titles and message types, then export PNG, SVG or PDF — or send a colleague a share link.