Home / Devices / Connecting the SD Biosensor STANDARD M10 to your LIS or EHR
Connecting the SD Biosensor STANDARD M10 to your LIS or EHR
If your clinic runs a SD Biosensor STANDARD M10, you already know the routine: the analyser shows or prints a result, and someone types those values into the patient record or the practice system by hand. That copying takes time, it is easy to transpose a value, and it leaves no clean record of who moved what and when.
Catenix removes that manual step. We can connect to the STANDARD M10 through a small gateway that sits on your own network, capture each result as it is produced, keep quality-control runs separate from patient results, and forward the finished results to the systems your site already uses. The STANDARD M10 is not a stock driver today, but because it reports over HL7 version 2 result messaging, an open standard, Catenix can build the connection for it. Send us the make and model and we will confirm what is possible and scope it with you.
Quick answer
Yes, a STANDARD M10 can be connected to your LIS or EHR. It supports an HL7 v2 result interface, and Catenix builds the connection through an on-site gateway, capturing each cartridge result, keeping quality-control runs separate, and forwarding validated results onward. Catenix keeps an audit trail of what arrived and where it was sent.
| Aspect | What Catenix supports |
|---|---|
| Manufacturer | SD Biosensor |
| Interface family | HL7 version 2 result messaging |
| Transport | Network connection over your local network |
| Direction | Results in (analyser to Catenix), forwarded onward to a LIS or EHR |
| Quality-control data | QC runs identified and stored separately from patient results |
| On-site component | Catenix gateway on your own network |
What the STANDARD M10 measures
The SD Biosensor STANDARD M10 is a portable molecular platform running rapid PCR cartridges for respiratory and other targets, sized for decentralised and near-patient testing.
Catenix does not change how the analyser runs a test or what it reports. Our role begins once a result exists: we take what the STANDARD M10 has produced and move it into your workspace and onward systems reliably, so the same values reach the patient record without anyone re-typing them. We make no claims about the device's clinical performance or its suitability for any diagnosis; our scope is connectivity and the handling of the data.
How it connects
The STANDARD M10 reports over HL7 version 2 result messaging, a long-established way for an instrument to send structured results to the systems that record them. In practical terms, the analyser can send each completed result as a message rather than only showing it on screen or printing it.
Catenix builds the connection to the STANDARD M10 through a small gateway that sits on your own network. The gateway listens for the results the STANDARD M10 sends, acknowledges them, and passes them securely up to your Catenix workspace. Keeping this component on site means the analyser talks to something local and predictable on the same network, which suits clinics that do not want the instrument itself reaching out to the internet.
Results and quality control in Catenix
Once the gateway is receiving the STANDARD M10 feed, every result is captured automatically as it is produced. Patient results appear in your Catenix workspace ready for review, with the values and the time recorded, so your team can check and release them instead of transcribing them.
Quality-control runs are handled separately. When a run is a QC sample rather than a patient sample, Catenix recognises it and keeps it out of the patient results, filing it against your quality-control records instead. Keeping the two streams apart from the moment of capture means your patient data stays clean and your QC history stays complete. From there, validated patient results can be forwarded to a LIS or EHR, so the systems your clinic already relies on receive the same numbers automatically. You can read more on our platform pages and about data handling on our security page.
Getting connected
A site needs the analyser reachable on its local network, a place on that network for the Catenix gateway, and agreement on where results should be delivered. If you plan to push results into another system, it helps to know which system and how it expects to receive results, so delivery can be mapped correctly. If you would like to check whether your specific setup is supported, get in touch. For commercial detail see pricing.
Questions clinics ask
Can I connect a SD Biosensor STANDARD M10 to my LIS?
Yes. The STANDARD M10 reports over HL7 version 2 result messaging, and Catenix reads that feed through an on-site gateway. Validated patient results are then forwarded to your LIS or EHR, so the same values reach your record system without anyone re-typing them.
Do we still have to type results in by hand?
No. Once the gateway is receiving the STANDARD M10 feed, each result is captured automatically and appears in your Catenix workspace for review. Your team checks and releases results rather than transcribing them, which removes a common source of copying errors.
How are quality-control runs handled?
Catenix recognises quality-control runs and keeps them separate from patient results, filing them against your QC records instead of a patient's chart. This keeps patient data clean and preserves a complete QC history for your quality processes.
Does the analyser need to be connected to the internet?
No. The STANDARD M10 talks to the Catenix gateway on your own local network, and the gateway handles secure delivery upward. The analyser itself does not need to reach the wider internet.
How long does it take to connect a STANDARD M10?
Most analysers that speak an open standard connect within days once the instrument is reachable on your network and the destination for results is agreed. If a bespoke driver is needed, we scope that with you first.
Will connecting the STANDARD M10 change how it runs tests?
No. Catenix does not alter how the analyser performs a test or what it reports. We only capture the results it produces and move them into your workspace and onward systems, with an audit trail of what was captured and where it was sent.
Product and company names mentioned are the trademarks of their respective owners. Reference to them is for identification only and does not imply any affiliation with, endorsement by, or certification from those owners. This page describes connectivity and data handling only and is not clinical advice.
Reviewed July 2026. Back to integrations. Going deeper on the standard: our HL7 v2 field guide.
Running something we have not listed?
We build analyser drivers to order, including for niche, regional and discontinued instruments. Tell us the make and model and we will tell you what is possible. Custom integrations or request a quote.