Unidirectional vs Bidirectional Analyzer Interface

When a vendor says an analyzer is "integrated", they are usually describing one of two very different arrangements — and the gap between them is several hours of technologist time a week. It is worth ten minutes to understand which one you are being sold.

The quick answer

A unidirectional interface is one-way: the analyzer finishes a sample and pushes results into the lab software. A bidirectional interface adds the return path — the software sends the worklist to the analyzer, telling it which tests to run on which sample. Unidirectional removes typing. Bidirectional removes typing and programming.

What each one actually changes at the bench

With no interface at all, a technologist reads twenty-odd CBC parameters off a screen and types them into the software. That is where transposed differentials come from, and it is the single most common source of a corrected report in a small lab.

With a unidirectional interface, results arrive on their own, matched to the order by the barcode already on the tube. But someone still has to tell the analyzer what to run — selecting the profile on the instrument keypad for each sample. On a machine doing 150 samples a day, that is the remaining manual step.

With a bidirectional interface, the analyzer queries the software when it reads a barcode: "what am I running on this tube?" The software answers from the order. Nobody programs anything. This matters most where the test menu varies sample to sample — biochemistry with per-patient profiles rather than a fixed panel.

The part vendors gloss over: it is the machine that decides

Whether you can have a bidirectional interface is a property of your analyzer, not of your software. Many bench instruments — particularly older haematology and electrolyte analyzers — only broadcast results. They have no host-query mode. No LIS can add one, and a vendor promising bidirectional operation on an instrument that does not support it is promising something nobody can deliver.

So the question to ask is not "does your software do bidirectional?" It is "does MY analyzer support host query, and can you show me?" The answer is in the instrument manual, usually in a section called Host Interface, LIS Interface or Serial Communication.

How to check before you buy anything

• Find the analyzer manual and locate the interface section. Note the protocol it names — ASTM E1381/E1394 (often written LIS2-A2) or HL7.
• Note the transport: an RS-232 serial port, or Ethernet/TCP. Serial is still the commonest on bench analyzers and is not a problem.
• Look for the words "host query", "query mode" or "bidirectional". Their absence usually means the instrument only broadcasts.
• Check whether the machine reads barcodes itself. Bidirectional operation is far less useful if a human still identifies each tube.
• Ask any prospective vendor to confirm against that specific model — not the brand.

That last point is worth insisting on. Analyzer support is model-specific because the test-code map differs between models of the same brand, so a claim of "we support Mindray" is not really a claim about your machine. Our integration pages state a status per integration for exactly this reason, and the analyzer interfacing page explains how the interface is put together.

Is bidirectional worth paying extra for?

Often, no. If your analyzer runs a fixed panel — a haematology machine doing CBCs all day — the test selection step barely exists, and a unidirectional interface captures nearly all the available benefit. The case for bidirectional is strongest on biochemistry and immunoassay instruments with a variable menu, and in labs running enough volume that instrument-side programming has become a bottleneck.

Be especially wary of paying a large premium for bidirectional on a machine that cannot do it. That upgrade quote should name your model.

Red flags

• A vendor quoting analyzer integration without asking for your make and model.
• A published list of "500+ supported analyzers" with no way to check yours.
• "Bidirectional" offered on an instrument whose manual has no host-query section.
• An interface that requires the vendor's own middleware licence on top.
• No mention of what happens to results when the internet drops — a local interface should not care.

On that last point: an analyzer link runs between the instrument and the lab PC over a cable. It has no business depending on your broadband, and if a vendor's architecture makes it depend on their server, results stop when the line does. Our view on where lab data should live is set out on the security and data page.

Where SamLab fits

SamLab speaks ASTM (E1381/E1394) and HL7 over serial or TCP, using one generic driver plus a small parser file per analyzer model that carries the test-code map. Bidirectional operation is configured where the instrument supports host query. We confirm per model rather than per brand, because that is the only honest unit of the claim — bring the model number and the interface page of the manual to a demo.