How to Choose Lab Middleware: 7 Questions to Ask Before You Buy

Choosing lab middleware is harder than it looks. On the surface, every vendor claims to support your instruments, handle your protocols, and integrate with your HIS. The differences — the ones that will matter at 2 AM when a connection drops — are buried in the details.

This guide cuts through the marketing. Here are the seven questions that separate middleware that works from middleware that creates new problems.

Why Middleware Evaluation Is Harder Than It Looks

Lab middleware sits between two environments that were never designed to talk to each other: the instrument manufacturer's world (ASTM E1394, RS-232 serial, proprietary protocols) and the hospital IT world (HL7, TCP/IP, modern databases). The middleware has to fluently speak both languages, handle every edge case, and never drop a result.

Most labs discover the real limitations of their middleware only after deployment — when a new instrument gets added, when the internet goes down, or when a parser fails to handle a non-standard result format. Asking the right questions upfront prevents those discoveries from becoming patient safety incidents.

Q1: What Protocols Does It Support — Really?

Every middleware vendor will say "yes" to ASTM E1394 and HL7. That's not enough information. What you need to know:

• Which version of ASTM? ASTM E1394-97 is common. Some analyzers use older variants with non-standard record structures.
• Which HL7 version? HL7 v2.x (2.3, 2.4, 2.5) is still dominant in labs. HL7 FHIR is a different protocol entirely — a "yes to HL7" answer doesn't tell you much.
• Can it handle custom protocols? Some instruments — especially older or regional ones — use proprietary formats. If your analyzer isn't on the vendor's supported list, ask exactly what "custom protocol support" means. Is it configurable by you, or does it require a paid development engagement?
• Does it support bidirectional communication? One-way (instrument → middleware → HIS) is common. Bidirectional (HIS → middleware → instrument, to send orders) is harder and requires specific implementation. If you want to send test orders to instruments automatically, confirm this is supported.

LISBridge supports ASTM E1394, HL7 v2.x, and custom protocols through a WASM-based parser that can be updated without downtime. You can verify protocol support for your specific instruments at lisbridge.com/solutions/data-parsing.

Q2: What Happens When the Internet Goes Down?

This question eliminates a large portion of the market immediately.

Cloud-based middleware depends on a server connection to function. If your internet goes down — or if the vendor's servers go down — your lab goes dark. In a hospital setting, that's not an acceptable failure mode.

Ask directly: "Does the middleware run locally on-premise, or does it require cloud connectivity to function?" Follow-up: "If your servers go offline, what happens to instrument communication?"

Local-first middleware (software that installs and runs on your hardware, like LISBridge) is immune to internet outages because there's no cloud dependency. The instrument connection, parsing, and delivery all happen on the device. Offline licensing means the software continues to operate even without any external validation.

For labs in areas with unreliable connectivity — or for any hospital that takes uptime seriously — local-first architecture is a hard requirement. Learn more about how offline-capable middleware works at lisbridge.com/how-it-works.

Q3: How Does It Handle New Instruments?

The instrument fleet in a clinical lab doesn't stay static. New analyzers get added. Old ones get replaced. The middleware needs to grow with you.

The key question is: what does adding a new instrument actually require? In the worst case, adding an instrument means submitting a support ticket, waiting weeks, and paying a one-time development fee. In the best case, it means selecting the instrument from a dropdown and connecting a cable.

Ask the vendor:

• Is there a supported instrument list, and is my analyzer on it?
• What's the process for adding an unsupported instrument?
• How long does it typically take?
• Is there a cost per new instrument?

LISBridge supports 25+ instruments out of the box, including Sysmex, Mindray, COBAS, Horiba, Abbott, and more. New instruments can be connected in minutes using the existing parser framework — no development engagement required for supported models.

Q4: Is It One-Way or Bidirectional?

This distinction matters more than most labs realize at the point of purchase.

One-way middleware receives results from instruments and delivers them to your LIS or HIS. This is sufficient for many labs that don't need to send orders back to analyzers.

Bidirectional middleware also sends test orders from the HIS to the instrument, so the analyzer knows what tests to run before a sample is processed. This eliminates a second manual step (entering orders at the instrument) and is required for most accreditation workflows.

If bidirectional communication is important to your workflow, confirm it explicitly — and ask which instruments support it. Not every analyzer supports bidirectional communication, and not every middleware implements it for every supported instrument.

Q5: How Is the Parser Updated?

Instrument firmware updates and HIS version upgrades can change the data format an analyzer sends. When that happens, the middleware parser needs to be updated to match.

Ask how parser updates are delivered:

• Does updating the parser require restarting the middleware service?
• Does it require an IT ticket or vendor involvement?
• Can updates be applied during lab hours, or do they require downtime?

LISBridge uses a WebAssembly (WASM) parser architecture that updates silently in the background — no restart, no downtime, no IT call required. When a parser is updated, it loads automatically the next time a connection is initialized. Learn more at lisbridge.com/solutions/data-parsing.

Q6: What Does the Licensing Model Actually Cost?

Middleware pricing is often structured to look affordable upfront and become expensive over time. Common patterns to watch for:

• Per-instrument fees: Some vendors charge a separate license fee for each instrument you connect. A lab with 8 analyzers can quickly find itself paying 8x the base price.
• Annual support contracts: Required for access to updates, bug fixes, or new instrument support.
• Per-site or per-user fees: Less common in middleware but present in some enterprise products.
• Professional services: Some vendors build implementation fees, training fees, and parser customization costs into the engagement, but not the headline price.

Ask for total cost of ownership over 3 years, not just the monthly subscription price. Include implementation, training, and projected costs for adding 2–3 new instruments during that period.

LISBridge uses a transparent subscription model scaled by the number of devices and instruments, with no hidden per-instrument fees for supported analyzers. Regional pricing is available — visit lisbridge.com/pricing for details.

Q7: Is There a Free Trial?

This is a signal, not just a convenience feature.

Vendors who offer a free trial are confident their software works as described. They're willing to let you test it against your actual instruments, with your actual data formats, before you commit. Vendors who don't offer a trial — or who offer only a "demo environment" with synthetic data — are asking you to take the integration on faith.

For lab middleware specifically, the free trial period should be long enough to:

• Connect at least one real instrument
• Confirm your HIS accepts the output format
• Test the behavior during a simulated connectivity failure
• Evaluate the parser's handling of your actual result types

LISBridge offers a full free trial with no credit card required. You can start connecting instruments within minutes of installation.

A Scoring Rubric for Your Evaluation

Use this as a quick comparison framework when evaluating multiple vendors:

• Protocol support: Does it support your exact instruments and your HIS format? (5 points)
• Offline capability: Does it run locally without cloud dependency? (5 points)
• Instrument onboarding: Can you add new instruments without vendor involvement? (4 points)
• Bidirectional support: If you need it, is it implemented for your instruments? (3 points)
• Parser updates: Are updates zero-downtime? (3 points)
• Total cost transparency: Is 3-year TCO clearly stated? (4 points)
• Free trial: Can you test against real instruments before buying? (3 points)

A vendor scoring below 20/27 on this rubric deserves harder scrutiny before you sign anything.

FAQ

What is lab middleware?

Lab middleware is software that sits between laboratory instruments (analyzers, centrifuges, point-of-care devices) and hospital information systems or LIMS. It handles the protocol translation, data validation, and delivery that makes instrument data usable in clinical workflows. See our full explanation at lisbridge.com/how-it-works.

How long does lab middleware implementation take?

With LISBridge, initial installation and connecting a first instrument typically takes under 30 minutes. Full deployment across a multi-analyzer lab — including HIS output configuration — usually takes 1–2 days. Compare this to custom integration projects, which can take 3–6 months.

Do I need middleware if my HIS vendor says they can connect to instruments directly?

Some HIS vendors offer native instrument connections, but these are typically limited to a small set of supported instruments and require the HIS to be online to function. Middleware provides vendor-neutral instrument support, offline resilience, and the ability to connect any instrument regardless of HIS vendor. Evaluate the specific instruments your HIS claims to support before assuming native connectivity meets your needs.

What's the difference between middleware and a LIS?

A Laboratory Information System (LIS) is the core system labs use to manage test orders, results, and patient records. Middleware sits between instruments and the LIS, translating raw instrument output into formats the LIS can accept. They serve different functions and most labs need both. See our full comparison at lisbridge.com/solutions/laboratory-integration.

Start your free trial — no credit card required. lisbridge.com/pricing