Plug in via RS-232 or point it at LISBridge over TCP/IP. Auto-detection identifies the instrument and loads the correct parser — no manual selection.
LISBridge reads the HL7 v2.3.1 (ORU^R01 / QRY^Q02) stream in real time. Every result message is decoded — field by field — into structured data.
Each result is checked for completeness. Duplicates caught. Malformed messages flagged. Only clean data moves forward.
Validated results reach your HIS automatically — as HL7 or direct format. Stored locally too. No manual entry required.
HL7 v2.3.1 over TCP or serial (9600 8N1). Results are ORU^R01 messages sent after an ENQ/ACK handshake, framed in MLLP with an additional EOT byte the standard does not describe. LISBridge's HTSH-2000 parser is built for that framing, so the message is read rather than dropped.
No — it is host-query only. The analyser initiates the exchange by sending a QRY^Q02 asking what to run on a sample, and LISBridge replies with a DSR^Q03 carrying the order. Orders are not pushed at the analyser; they are held until it asks.
LISBridge replies MSA|NF — no sample matched, nothing to run — with no DSP segments. That matters because the analyser holds its query window open for roughly six seconds. An explicit no-order reply closes the window cleanly; silence leaves it to time out and retry.
Yes. The HTSH-2000 tags every transmission in MSH-16 as patient sample, calibration, or quality control. LISBridge reads that field and routes calibration and QC traffic away from the patient pipeline before it can reach your LIS.
Two reasons. The vendor EOT on the end of the MLLP frame breaks strict framing, and the analyser omits the OBX Set ID, which shifts every later field one position left. A generic parser reads that message without error and puts the values in the wrong places — the failure is silent, which is the worst kind in a lab.
LISBridge supports 37 instruments. See also:
Start your free 7-day trial — no credit card required. Full HL7 v2.3.1 (ORU^R01 / QRY^Q02) support from day one.