Skip to main content
bLIS Gateway is a lightweight service that sits between your laboratory instruments and bLIS. It receives data from analyzers — hematology, chemistry, immunoassay, coagulation, and more — translates their communication protocols, and delivers results directly into bLIS. No manual transcription required.

Why use bLIS Gateway?

Most laboratory instruments output results using specialized protocols (such as ASTM or HL7) over serial or network connections. Without middleware, someone would need to read values from the instrument and type them into the LIS by hand — a slow, error-prone process. bLIS Gateway automates this entirely. Once configured, results flow from the instrument into bLIS in seconds, matched to the correct accession and test order automatically.

How it works

The gateway supports two primary workflows: Order download — When a sample is loaded, the instrument queries bLIS for pending test orders. The gateway translates the query, forwards it to bLIS, and returns the order list back to the instrument in its native format. Result upload — After testing completes, the instrument sends results through the gateway to bLIS. Results are matched to the correct accession and test order automatically. In both directions, the gateway translates between the instrument’s native protocol and a standardized format that bLIS understands. This means bLIS receives a consistent message structure regardless of the instrument manufacturer or protocol.

Key features

  • Bidirectional communication — Supports both order download (instrument queries bLIS for pending tests) and result upload (instrument sends completed results to bLIS).
  • Multi-instrument support — Connect as many instruments as you need, each on its own port with its own configuration.
  • Protocol translation — Supports ASTM E1394, Siemens EXL, Clinitek, and more. Each instrument can speak its native protocol.
  • Web dashboard — A built-in management console lets you monitor connections, view message history, and stream logs in real time.
  • Message persistence — Optionally store all instrument messages in a local database for auditing and troubleshooting.
  • Reliable delivery — Automatic retries and error handling ensure results reach bLIS even during brief network interruptions.
  • Self-updating — The gateway can update itself to the latest version with a single command.
  • Flexible deployment — Run it as a system service on a VM, or as a Docker container. A single compiled binary with no external dependencies.

Supported protocols

bLIS Gateway includes drivers for the following communication protocols:
  • ASTM E1394 — The most widely used LIS protocol. Supports the majority of laboratory analyzers including Abbott, Beckman Coulter, Roche, Sysmex, and others.
  • HL7 — Health Level Seven messaging standard used by many clinical systems.
  • Siemens EXL — Proprietary protocol for Siemens EXL analyzers.
  • Siemens Clinitek CSV — CSV-based output from Siemens Clinitek urinalysis systems.
If your instrument uses one of these protocols, it can be connected to bLIS through the gateway.

Next steps

Deployment

Install bLIS Gateway on a VM or run it with Docker.

Configuration

Set up your instruments, LIS connection, and other options.

Integration

How order download and result upload work end to end.