HTSH-2000 LIS Integration: Bidirectional Biochemistry Over HL7

The HTSH-2000 is a biochemistry analyzer that will happily talk to your LIS, but only if the other end follows its rules exactly. It opens every transmission with a handshake, expects an answer within seconds, and labels every message as a patient sample, a calibration, or a QC run. Most generic interfaces get one or two of those right. Getting all of them right is what separates a link that looks alive from a link that delivers results.

LISBridge supports the HTSH-2000 natively, in both directions. This post walks through what the analyzer sends, how ordering works, and the details that tend to cause trouble on a real lab floor.

What the HTSH-2000 Is, and How It Identifies Itself

The HTSH-2000 is a biochemistry analyzer whose vendor application is called Bio200. For integration purposes the important facts are these: it sends results as HL7 v2.3.1 ORU^R01 messages, it can do so over TCP or serial, and it supports a host-query channel so it can ask the LIS what to run on a given sample.

That makes it one of the 17 bidirectional instruments LISBridge supports out of the box, alongside analyzers such as the Mindray BS-430 and the Abbott i800. If your lab runs it, you do not need custom programming to connect it. You can read the broader picture on the HL7 and ASTM support page and see the instrument itself at /instruments/htsh-2000.

ENQ, Then Wait for a Real ACK

This is the detail that trips up the most connections. The HTSH-2000 family opens every transmission with an ENQ byte and then sends nothing until it sees a genuine 0x06 ACK byte come back.

A listener that does not know this behaves badly in a very specific way. It waits for data, hits an idle timer, and eventually answers with the three printable characters "A", "C", "K". To a person reading a log, that looks like an acknowledgement. To the analyzer, it is not one. The port appears open, the cable is fine, the analyzer is plainly connected, and no result ever arrives.

LISBridge answers the ENQ immediately with the real ACK byte. Bare ENQ and EOT control bytes are no longer stored as junk rows, and HL7 wrapped inside that handshake is recognised only when an MSH| segment actually follows the start-of-block byte. The result is a link that starts delivering on the first transmission rather than the first timeout.

Results: HL7 v2.3.1 ORU^R01 and the Missing OBX Set ID

Once the handshake is done, results arrive as ORU^R01 messages. One quirk is worth knowing about: the analyzer omits the OBX Set ID. In a standard OBX segment, the first field after the segment name is a sequence number. When it is simply absent, every following field shifts one position to the left. A parser written strictly from the HL7 specification will read the observation identifier as the value type, the value as the identifier, and so on, without raising a single error.

LISBridge's parser for this analyzer accounts for the shifted layout, so test codes, values, units and reference ranges land in the right fields. If you want the broader context on this kind of vendor variation, our post on analyzers that speak neither pure HL7 nor ASTM covers the pattern in more depth.

Bidirectional Ordering: QRY^Q02 In, DSR^Q03 Out

The analyzer does not wait to be told what to run. When a sample barcode is read, the HTSH-2000 asks the LIS what tests are ordered, using a QRY^Q02 query. LISBridge looks up the sample and replies with a DSR^Q03 message carrying the ordered tests. The analyzer then sends an ACK^Q03 to close the exchange.

For the lab, this removes the step where a technician keys the worklist into the analyzer by hand. Orders flow from the HIS or LIS, through LISBridge, to the instrument, and results flow back along the same path. If you want the general mechanics of this pattern, see how host-query worklists work.

What Happens When There Is No Sample on File

Host-query analyzers give the LIS a short window to reply. On the HTSH-2000 that window is about six seconds. If nothing comes back, the analyzer times out and may hold the sample, raise an error, or simply stall the rack.

The common case where this matters is a sample with no matching order: a walk-in, an add-on, a barcode typo. LISBridge answers these with an MSA|NF (no data found) reply, so the query window closes cleanly instead of timing out. The analyzer gets a definite "nothing here" and carries on, which is far better than a six-second stall on every unmatched tube.

Patient, Calibration, or QC: Read From MSH-16

The analyzer tags each transmission in MSH-16 as a patient sample, a calibration, or a QC run. That tag is easy to ignore and expensive to ignore. If calibrator and control results land in the patient result table, they end up on patient reports or pollute trend data.

LISBridge reads the tag and routes calibration and QC transmissions away from the patient pipeline automatically. Nobody has to remember to filter them out. They are kept, they are traceable, and they never appear as a patient result.

Setting It Up

1. Choose the connection. Use TCP/IP if your unit has a network interface, or an RS-232 serial cable if not. LISBridge supports both on this analyzer.
2. Add the instrument. Select the HTSH-2000 from the instrument list in LISBridge and set the port or IP and port number.
3. Configure the analyzer side. Point the analyzer's host settings at the machine running LISBridge and enable host query if you want orders to flow downstream.
4. Run a test sample. Send one patient sample and one control. Confirm the patient result appears and the control is held out of the patient pipeline.
5. Test a query with no order. Scan a barcode that has no order on file and confirm the analyzer moves on without a timeout.

Raw protocol data is stored alongside every parsed result, so if anything looks off on day one you can compare exactly what the analyzer sent against what was recorded. And if a link drops, LISBridge reconnects with exponential backoff and jitter, with crash-safe local storage so nothing is lost mid-run.

Why This Analyzer Rewards a Purpose-Built Parser

None of the HTSH-2000's quirks is exotic on its own. The handshake, the shifted field positions, the short query window and the transmission tag are each manageable once you know about them. The trouble is that they stack. A generic HL7 listener might handle the ORU message but fail the handshake. Another might handle the handshake but mis-assign the fields. A third might do both and then store the QC run as a patient.

The practical risk for a lab is not a dramatic failure on day one. It is a quiet, partial one: most results arrive, a few are wrong, and nobody notices until a clinician queries a value. Because LISBridge keeps the raw protocol data next to every parsed result, you can always go back to the exact bytes the analyzer sent and see how they were interpreted. For a biochemistry analyzer producing a high volume of results per day, that traceability is worth having from the start.

Where It Fits in a Larger Lab

Many labs run the HTSH-2000 beside a haematology analyzer and an immunoassay system. LISBridge handles all of them in one application, whether they connect by serial cable, TCP/IP or a file server, and shows them on one real-time monitoring dashboard. The device connectivity overview explains how multiple instruments share one installation.

Frequently Asked Questions

Does the HTSH-2000 support bidirectional communication with LISBridge?

Yes. It is one of 17 bidirectional instruments. It queries for orders with QRY^Q02 and LISBridge answers with DSR^Q03.

Which transports are supported?

HL7 v2.3.1 over TCP or serial, behind the ENQ/ACK handshake.

Why does the connection look open but no results arrive?

The analyzer sends ENQ and waits for a real 0x06 ACK byte. An interface that replies with the text "ACK", or only after a timeout, will look connected and receive nothing.

What happens to QC and calibration results?

The analyzer marks them in MSH-16 and LISBridge routes them away from the patient pipeline automatically.

What if the analyzer asks about a sample with no order?

LISBridge replies with MSA|NF so the analyzer's six-second query window closes cleanly.

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