If your instrument isn’t listed, send the model number and interface manual. Most new integrations take two to four weeks including on-site validation.
Send your instrument list
Protocol, port, encoding and verification policy are configuration per instrument — visible to your engineer, changeable without a release, with the raw message log one tab away.
Results stream in as the analyser produces them, matched to the accession barcode. Anything that arrives without an order is held and flagged rather than silently filed.
Every instrument listed with model, firmware and port availability.
Interface manual mapped to our driver layer and unit tested.
Sample runs against known controls, in our lab or yours.
Live alongside the existing process until results match.
Validation document handed to your quality team.
Protocols, timelines and validation for laboratory machine integration.
Send the model number and the interface manual. Most new instruments take two to four weeks to build, bench test and validate on site, and the driver becomes part of the platform for every lab after that.
HL7 v2.x ORM and ORU messaging, ASTM E1394 record transfer, ASTM E1381 link layer, CLSI LIS2-A2, direct RS-232 and TCP instrument links, and CSV, XML or shared-folder polling where a machine offers nothing better.
Where the analyser supports it, yes — worklist and order download to the instrument, result upload back to the case record, with flags preserved for out-of-range values.
No. We write the protocol-level driver ourselves, so when an analyser behaves oddly at 2am the person who wrote the interface is reachable.
Site audit of every instrument with model, firmware and port availability; driver build and bench test against known controls; a parallel run alongside your existing process; and a validation document handed to your quality team at sign-off.
A 30-minute call with an engineer, not a salesperson. Tell us the problem and we’ll tell you what’s possible.