Laboratory interfaces: instrument, LIS, and analyzer connectivity
TransLABtor is on-premise lab software — a lab system layer that provides an interface with LIS and bidirectional analyzer links. Analyzer interfaces route orders and results securely across the hospital and laboratory intranet.
Last updated 8 September 2026
How it works
Three steps from LIS order to validated result — all on your hospital or laboratory intranet.
- 1
LIS sends orders
Your Laboratory Information System transmits orders to TransLABtor over the LIS interface — HL7 v2.4 (MLLP or File I/O) or ASTM LIS2-A2. One message can carry multiple tests per specimen.
LIS interface specifications → - 2
TransLABtor maps and routes
Middleware translates protocols, maps LIS test codes to instrument test codes, routes each order line to the target analyzer, and applies validation rules. Traffic and raw frames are logged on your intranet.
Core capabilities → - 3
Results return to LIS
Results flow from analyzers to TransLABtor for validation and logic processing. Operators review and release via the TransLABtor workstation, and validated results are transmitted back to the LIS. PHI stays entirely on-premise.
HL7 result message format →
Choosing an integration approach
Hospitals and clinical labs typically evaluate direct LIS links, instrument-vendor middleware, or independent laboratory middleware. Use this table to align stakeholders before scoping.
| Criteria | Direct LIS integration | Instrument vendor middleware | TransLABtor |
|---|---|---|---|
| Typical scope | Direct link between the LIS and each analyzer or instrument middleware box | Vendor-supplied software for that manufacturer's analyzers | Independent laboratory middleware between the LIS and analyzers |
| Multi-vendor analyzer support | One custom project per LIS × analyzer pair; development cost scales with instrument count | Strong when analyzers sit under one IVD family; additional fees/adapters often required for third-party instruments | Growing driver library across major IVD brands; new driver development based on specifications under active maintenance contract |
| LIS connectivity | Native LIS interface module, built and maintained by the LIS vendor or systems integrator | Typically via a vendor-specific LIS interface protocol or professional services engagement | Standard LIS interfaces (HL7 v2.4 and ASTM LIS2-A2) with published developer specs, or custom mapping on request |
| Workflow rules & audit | Depends on LIS vendor scope; often limited reflex or cross-instrument logic | Built-in rules engine tailored to vendor hardware; vendor-supported rules development available | GUI-based, no-code rules engine for cross-analyzer logic; optional professional rules development |
| Deployment & PHI | Varies by LIS product and site architecture | Mix of on-premise, cloud appliances, and vendor-hosted options | On-premise, web-based on the hospital or laboratory intranet; application-layer PHI encryption |
| Best fit when | The LIS team has in-house capacity to build, validate, and maintain analyzer interfaces | Labs standardized on a single manufacturer's ecosystem, requiring deep integration with proprietary hardware and tracks | Mixed-vendor environments seeking vendor independence, unified validation workflows, and minimal disruption during hardware refresh cycles |
What is a laboratory interface?
A laboratory interface is software that connects a Laboratory Information System (LIS) to clinical analyzers, translating orders and results over protocols such as HL7 and ASTM. TransLABtor is a laboratory interface vendor providing on-premise laboratory instrument interfaces for hospitals and clinical labs worldwide.
Laboratory instrument interface
A laboratory instrument interface is the analyzer-side link in that stack — bidirectional ASTM or HL7 traffic between middleware and each instrument. The library below lists pre-built drivers; additional laboratory interfaces are mapped from manufacturer host-interface specifications on request.
LIS interface
The LIS interface is the upstream channel for orders, results, and status between your LIS and TransLABtor. Standard interfaces are published as developer specifications — HL7 v2.4 (TCP/MLLP and File I/O) and ASTM LIS2-A2 (E1381 framing). Analyzer-side protocols vary by vendor and model (see host protocols and the driver library).
Specifications last updated 8 September 2026
Analyzer and LIS library
Pre-built laboratory instrument interfaces in our driver library, plus models we can deliver on request from manufacturer host-interface specifications (built on our existing ASTM and HL7 base drivers — typically within 14 working days under an active maintenance contract, depending on protocol complexity). LIS connectivity uses the standard interfaces in the Laboratory Information System section below — each links to a full developer specification.
Abbott
Instrument| Interface | Protocol | Notes |
|---|---|---|
| Alinity ci-series | ASTM LIS01 / LIS2-A2 | Chemistry / immunoassay host interface |
| Alinity ci-series HL7 | HL7 2.5.1 / IHE LAW / MLLP | Bidirectional query and order channels |
| AlinIQ AMS | ASTM | Vendor middleware — available on request |
| AlinIQ AMS HL7 | HL7 | Vendor middleware — available on request |
| Architect c16000 / i1000SR / ci16200 | ASTM | Chemistry / immunochemistry — available on request |
| Architect HL7 | HL7 | Chemistry / immunochemistry — available on request |
| CELL-DYN Ruby | ASTM | Hematology — available on request |
Roche
Instrument| Interface | Protocol | Notes |
|---|---|---|
| Cobas 4800 | HL7 MLLP + ASTM | Molecular / host protocol selectable |
| Cobas 5800 | HL7 | Molecular — available on request |
| Cobas 6800 / 8800 | HL7 | Molecular — available on request |
| Cobas pro | HL7 2.5.1 / MLLP | Integrated serum work area |
| Cobas pure | HL7 2.5.1 / MLLP | Integrated chemistry / immunoassay |
| Cobas b 221 | ASTM | Blood gas — available on request |
| Cobas Infinity | HL7 | Vendor middleware — available on request |
| Cobas u 411 | ASTM | Urinalysis — available on request |
Sysmex
Instrument| Interface | Protocol | Notes |
|---|---|---|
| XN Series | ASTM E1394 | XN-10 / 20 / 1000 / 1500 / 2000 / 3000 / 3100 |
| XN-V Series | ASTM | Veterinary / species-aware hematology |
| CS Series | ASTM | CS-1600, CS-2000i coagulation |
| U-WAM | ASTM LIS2-A2 | Urinalysis work-area manager |
Bruker
Instrument| Interface | Protocol | Notes |
|---|---|---|
| MALDI Biotyper | ASTM v4.3 | Microbiology identification |
Laboratory Information System
Connectivity to LIS| Interface | Protocol | Notes |
|---|---|---|
| Standard HL7 v2.4 LIS | HL7 v2.4 TCP/MLLP + File I/O | Interface specification |
| Standard ASTM LIS | ASTM LIS2-A2 / E1381 | Interface specification |
Host protocols
ASTM E1394 / LIS01-A2
Analyzer host interfaces
HL7 v2.x + MLLP
Connectivity to LIS and HL7 instruments
File I/O
Drop-folder HL7 or ASTM
TCP Server / Client
Hospital LAN connectivity
Not listed?
We keep developing drivers on customer request. Send the manufacturer interface manual or a de-identified hex/HL7 trace. Under a valid maintenance contract, new drivers are included; a beta pack is typically ready for site validation within 14 working days, depending on protocol complexity.
Formal site validation of each interface remains the responsibility of the deploying laboratory.
Lab Systems FAQ
Laboratory interface vendor
TransLABtor ships laboratory interface software with pre-built laboratory instrument interfaces. Custom ASTM/HL7 mappings are available on request.
Lab middleware in Hong Kong & worldwide
KW Informatics Limited is based in Lai Chi Kok, Hong Kong. Deployments run on-premise globally — patient data stays on your intranet.
Need connectivity to a LIS or analyzer that is not listed?
Send the manufacturer interface specification or a de-identified sample trace. We map a driver for your laboratory system and keep the library growing for every site.