What is LIS middleware?

What is LIS middleware?

LIS middleware is software that sits between laboratory instruments and the laboratory information system (LIS). It translates each instrument’s communication protocol, sends orders to the right analyzer, and returns results to the LIS, so instruments and the LIS can exchange data without manual entry.

Every analyzer speaks its own dialect. Some use ASTM over a serial cable, some use HL7 over the network, and some only export files. Middleware handles those differences in one place, so the LIS sees one consistent stream of orders and results.

What middleware does

• Protocol translation. Converts ASTM, HL7, serial output, and flat files into the format the LIS expects, and back again.
• Order routing. Sends each test to the correct instrument, either by download or by answering an instrument’s query when it scans a barcode.
• Result capture. Collects results, flags, and instrument messages and returns them to the LIS.
• Monitoring. Shows which instruments are connected, what traffic is moving, and where a message failed.
• Rules, in some products. Many middleware products can also apply review rules, reruns, or QC checks before results reach the LIS. Capabilities vary widely, so ask each vendor exactly what theirs does.

When does a lab need middleware?

Middleware earns its place when one or more of these is true:

• You run many instruments, or add new ones often.
• You have older analyzers that only offer an RS-232 serial port.
• Your LIS vendor charges for, or is slow to build, each new instrument interface.
• You want to change LIS without reconnecting and revalidating every instrument from scratch.
• You operate more than one site and want a single view of instrument connectivity.

Middleware vs. direct instrument interfaces

A direct interface connects one instrument straight to the LIS. That works well for a small number of modern analyzers your LIS already supports. Middleware adds a layer, but it centralizes every connection, makes instruments independent of the LIS, and usually makes adding or replacing an instrument faster. Many labs use both: direct interfaces where the LIS handles them well, middleware for everything else.

Cloud vs. on-site middleware

Traditional middleware runs on a server at the lab. Cloud middleware runs in a hosted environment, with a small local agent at the lab that connects to instruments and carries their traffic securely to the cloud.

Cloud deployment removes the on-site server your team would otherwise buy, patch, and back up. Self-hosted deployment, for example in Docker containers on your own infrastructure, keeps everything on your network. Either way, the instruments connect locally. Only the place where translation and routing happen changes.

What to look for in LIS middleware

1. Support for the protocols your instruments actually use: ASTM, HL7, RS-232 serial, TCP/IP, and flat files.
2. Compatibility with your current LIS, and with the next one.
3. Deployment options that fit your IT policy, hosted or self-hosted.
4. Message-level monitoring, so you can see and resolve failures quickly.
5. Who builds and supports each instrument connection.
6. Security: encrypted transport, access controls, and audit trails.

Where Lab Dynamo fits

SparkRelay is Lab Dynamo’s custom-built middleware. It sits between your instruments and your LIS, translating, routing, and monitoring orders and results, and it works with SparkLIS, PathArray, or nearly any other LIS. Run it in the Lab Dynamo cloud with local relay agents, or in your own environment with Docker. SparkRelay focuses on instrument-to-LIS traffic; connections to EHRs, reference labs, and billing go through the LIS’s own interfaces.