Home / Integrations / Epic
Integration guide · United Kingdom
Point-of-care results, filed in Epic.
Run the test on the ward, in the emergency department or in clinic and the result lands in Epic as a structured value against the right patient. Nothing read off a screen, nothing typed twice, no printout walked to a terminal.
Epic is the electronic patient record (EPR) at a growing number of NHS trusts, including several of the largest teaching and specialist trusts in England. A contract announcement in March 2026 put the count at 18 trusts. Once a trust is on Epic, most clinical work happens inside it, so a point-of-care result that never reaches it might as well not exist. The gap is rarely the analyser and rarely Epic. It is the manual step in between.
Two things push an acute trust 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, produce a steady stream of results that someone would otherwise have to transcribe. 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 Epic. 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 Epic through an HL7 v2 results interface of the kind Epic documents on open.epic, its Incoming Ancillary Results and Incoming Results from Lab Instruments interfaces among them. Epic also publishes FHIR R4 APIs, but which inbound route applies to point-of-care results is confirmed with the trust's integration team, which configures the Epic 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 Epic?
A result captured at the bench is turned into a structured message and delivered to Epic through an HL7 v2 results interface or, where the trust has enabled it, a FHIR R4 API. Epic documents its inbound results interfaces on open.epic, including one it names as the route for point-of-care testing results into Beaker, its laboratory module. 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 Epic?
Catenix is designed and ready to connect to Epic over the standards it accepts. That describes connectivity built to open standards, not an affiliation with or endorsement by Epic. Exactly what flows, and how, is confirmed with your trust during implementation.
Does our trust's IT team need to enable an interface in Epic?
Yes. Inbound interfaces on the Epic side are set up by the trust's Epic and integration teams, usually through the trust integration engine. Catenix presents a standard HL7 v2 result message and works with those teams on patient identifiers, test codes and where each result files. Where a trust runs Beaker, Epic names its Incoming Results from Lab Instruments interface as the route for point-of-care testing results, and results from an external system can also file through the Incoming Ancillary Results interface. Where the trust prefers point-of-care results to pass through its laboratory system first, 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 Epic.
Bring your analyser list. We'll show the journey from bench to record, live, and start with a 15-minute call if you prefer.