LISBridge connects to lab instruments over RS-232 serial or TCP/IP — at the same time, on the same installation. Legacy equipment works alongside your newest analyzers without replacing a single cable.
No IT project. No configuration file. Three steps and your instrument is live.
Connect the serial cable to your instrument's RS-232 port, or enter the IP address and port for a network-connected analyzer. That is all the setup required.
The first message from the instrument tells LISBridge what it is. The correct parser and settings load automatically — no dropdown, no profile selection.
From this point, every result the instrument produces is received, parsed, and forwarded to your HIS or LIMS automatically. Nothing else to do.
Hospital IT asks a fair question before any middleware goes in: does putting another piece of software between the analyser and the LIS make our security position worse? For a device that cannot be upgraded, the recognised answer is the opposite — put a secure gateway in front of it, keep it segmented, and log what it does. That is a description of what LISBridge already is.
A bench analyser bought in 2011 is not going to learn modern cryptography, and replacing it is rarely a real option. LISBridge speaks to it exactly as it is — RS-232, TCP/IP or file transport, in its own native dialect — so the device stays on its original firmware while the rest of the path around it is modernised.
LISBridge is a native desktop application, not a cloud service. Results are written to encrypted local storage on a machine you already control. Patient data does not leave the site in order to be parsed, and an internet outage does not put results at risk.
Orders are pulled from your HIS or HMS over an outbound connection and results are pushed back the same way. There is no inbound firewall rule to justify, no static IP to reserve, and no DMZ slot to negotiate for the HIS side of the integration.
Every parsed result keeps the raw ASTM or HL7 frame that produced it. Liveness and panic logging record what the software was doing when it stopped. If someone asks what a given analyser sent at 02:14 last Tuesday, the answer is on disk.
LISBridge is written in Rust, which rules out entire classes of memory-safety vulnerability at compile time — the same classes that dominate advisories for long-lived connected medical equipment.
Doing a security review? Our full data-handling and retention position is written up on the data security page, and the parsing and raw-frame retention detail is on data parsing.