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 aiMessage / lisMessage XML (BCI Connect) 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.
Over the bioMérieux BCI Connect file server, using FTP, FTPS, or SFTP. LISBridge polls the configured directory for new aiMessage XML result documents and writes lisMessage XML order documents in return. No socket connection to the analyser is required.
Most middleware assumes an instrument streams data over a serial port or a TCP socket. The VIDAS KUBE writes and reads XML files instead. Generic integration engines built around message streams have no natural place to put that, which is why the KUBE is often left as the one analyser still handled by hand.
Yes. LISBridge writes lisMessage XML order documents to the BCI Connect file server, so test orders reach the analyser from your LIS. The VIDAS KUBE is one of LISBridge's 16 order-capable instruments.
FTPS and SFTP are both supported, so the exchange can be encrypted in transit. Parsed results and the raw XML documents are stored locally on the LISBridge machine — nothing is sent to a cloud service.
Yes. The classic VIDAS and MiniVIDAS instruments are supported separately through their own serial protocol. The VIDAS KUBE is a distinct connection profile because it uses the BCI Connect file transport instead.
LISBridge supports 35 instruments. See also:
Start your free 7-day trial — no credit card required. Full aiMessage / lisMessage XML (BCI Connect) support from day one.