Home / Integrations / CareFlow EPR
Integration guide · United Kingdom
Point-of-care results, filed in CareFlow EPR.
Run the test on the ward, in the emergency department or in clinic and the result lands in CareFlow EPR as a structured value against the right patient. Nothing read off a screen, nothing typed twice, no printout walked to a terminal.
CareFlow EPR is System C's patient administration system and electronic patient record (EPR), used by NHS trusts in England. System C lists it as open and interoperable via HL7, FHIR and APIs, with a toolset called CareFlow Connect that lets local digital teams build and manage APIs against NHS England's Interoperability Standards Directory. Where CareFlow is the chart, a point-of-care result that never reaches it might as well not exist. The gap is rarely the analyser and rarely CareFlow. It is the manual step in between.
Two things push a trust on CareFlow to connect its analysers. The first is volume: blood gas, glucose, ketones and INR run on many devices across wards, theatres, the emergency department (ED) and outpatients, and each result is a value someone would otherwise type in later. The second is governance: ISO 15189:2022 and Medicines and Healthcare products Regulatory Agency (MHRA) guidance on point-of-care devices expect every result to carry the operator, the device, the lot and the quality-control status, and the point-of-care testing (POCT) coordinator has to evidence that across every site. Connect the analysers and both problems shrink.
Catenix sits between your analysers and CareFlow EPR. A small gateway on site captures each result electronically the moment it is produced, over HL7, POCT1-A2, ASTM or the device's own format. The result is matched to the right patient and operator, kept separate from quality-control runs, and forwarded to CareFlow EPR through an HL7 v2 results interface, which System C states CareFlow supports alongside FHIR, usually routed through the trust integration engine, or an API made available through CareFlow Connect where the trust has enabled it. The trust's integration team configures the CareFlow side.
How it works
From bench to filed result.
More than the pipe
Connectivity is the start, not the whole product.
QC captured as it happens, Westgard rules on failures, Levey-Jennings charts drawn for you, competency against the operator who ran the test. Every analyser, one system
Chemistry, immunoassay, blood gas, haematology, molecular and urinalysis on one platform instead of one middleware per manufacturer. Pocket Gateway
A phone becomes the gateway, so testing connects even in settings without fixed network infrastructure. Built for networks
One coordinator can oversee devices, QC and operators across every site from a single screen.
Modules switch on per clinic, so you take the connectivity and governance you need now and add the rest if it earns its place. There are no per-test fees.
Questions, answered
Before you ask.
How do point-of-care results reach CareFlow EPR?
A result captured at the bench is turned into a structured message and delivered to CareFlow EPR through an HL7 v2 results interface or, where the trust has enabled it, an API. System C states that CareFlow supports both HL7 v2 and FHIR interfaces and describes CareFlow Connect as the toolset for building and managing APIs. Catenix is designed to connect over those open standards, so the value that was measured is the value filed against the right patient, with the operator and device attached.
Is Catenix integrated with CareFlow EPR?
Catenix is designed and ready to connect to CareFlow EPR over the standards it accepts. That describes connectivity built to open standards, not an affiliation with or endorsement by System C. Exactly what flows, and how, is confirmed with your trust during implementation.
Does the result go through the trust integration engine?
Usually, yes. Most trusts route inbound clinical messages through a trust integration engine that validates them and passes them to CareFlow EPR, and that is where patient identifiers, test codes and result locations are mapped. Catenix presents a standard HL7 v2 result message and works with the trust's integration team on that mapping. Where the trust prefers point-of-care results to pass through its laboratory system first, so they sit alongside laboratory results and reach CareFlow through the existing results reporting, Catenix can deliver there instead, or to both.
Catenix is designed and ready to connect to the systems named on this page over open standards. That wording is deliberate: it describes connectivity built to published interfaces, not a claim of affiliation with, endorsement by, or certification from any named vendor. Product and company names are the trademarks of their respective owners and are used for identification only. What connects in your setting is confirmed during implementation. This page describes connectivity and data handling only and is not clinical advice.
See a result land in CareFlow EPR.
Bring your analyser list. We'll show the journey from bench to record, live, and start with a 15-minute call if you prefer.