Integration Engineer (EPR & NHS App)

About Cerina Health Cerina Health builds an Agentic AI platform for digital mental health, live in NHS Integrated Care Boards and trusts today. We sit upstream of the NHS clinical record — structuring demand before it enters formal clinical pathways, and generating the pre-clinical and social data that no Electronic Patient Record (EPR) system holds. Data is the core of what we do, and this role sits at the centre of that strategy. The Role We are hiring an Integration Engineer to own Cerina’s integration strategy and execution into the NHS — Electronic Patient Record (EPR) systems and the NHS App ecosystem. Every integration we build is a data-accumulation event: a reusable asset that travels to every future deployment. You won’t just maintain connections — you’ll design the architecture that determines how much of the NHS Cerina can reach, and how predictive our dataset becomes over time. You’ll work closely with the UK leadership team and have visibility at board and investor level from day one. Integrations follow confirmed commercial need — each one is built in response to a signed or named opportunity, not speculatively — so your work is always tied to a real deployment. What You Will Build ·

GP Connect via FHIR — a single build across EMIS Web and SystmOne (over 90% of GP records, ~62M registered patients), with SNOMED-coded write-back to the GP record. Travels to every subsequent deployment without rebuilding. ·

NHS App ecosystem — 15M+ monthly active users, with a Single Patient Record accessible through the App from 2028. Being inside this ecosystem matters more than any single EPR partnership. ·

SystmOne direct partnership — community, mental health and GP practices across multiple ICBs in one partnership. ·

Rio (Access Group) — used by over half of NHS mental health trusts. ·

Local-authority systems (Mosaic, LiquidLogic) — connecting housing, benefits, employment and care-package data with pre-clinical health data; a combination no EPR vendor can offer. ·

Epic and Oracle Health (Cerner) — acute-trust integration (longer-term; architecture decided now shapes how fast it can be delivered later). ·

SNOMED CT write-back — design the data model now so the write-back layer can be added cleanly, not retrofitted. Key Responsibilities · Own the integration architecture and roadmap across EPRs, the NHS App, and local-authority systems — sequenced against confirmed commercial need. · Design and build production integrations: read access (demographics, clinical history) and structured SNOMED-coded write-back. · Own the cross-system data and identity model — NHS Number linkage, demographic feed, proxy/edge cases, and pseudonymisation. · Treat governance as first-class delivery work — DPIAs, Information Sharing Agreements, clinical safety sign-off (DCB0129 / DCB0160) — not an afterthought. · Build robust, observable, well-documented APIs and integration services (REST, FHIR, modern auth), with sensible versioning and partner change-management. · Navigate EPR partner programmes and approval processes, and work directly with partner engineering teams. What We Are Looking For · Hands-on experience building

healthcare integrations in production . NHS experience is a strong advantage;

equivalent FHIR R4 / HL7 / clinical-data-standards experience in any regulated health market is highly relevant — including

ABDM under the Ayushman Bharat Digital Mission , or US healthcare interoperability (Epic / Cerner, HL7). · Strong back-end engineering: RESTful APIs, authentication models, and integration architecture designed to scale and be reused, not rebuilt. · Deep understanding of

clinical data standards — SNOMED CT, FHIR resource modelling, coded outputs. You understand what writing structured data back into a clinical record means in practice. ·

Governance as first-class work: DPIAs, Information Sharing Agreements, clinical safety sign-off. · A

data mindset — you think about what each integration accumulates, not only what it connects. · Comfortable in a fast-moving, early-stage company where integrations follow confirmed sales and every build has a commercial purpose. Nice to Have EMIS / SystmOne API · GP Connect · Rio / Access Group · Epic or Oracle Health · Mosaic or LiquidLogic · NHS App developer ecosystem · DCB0129 / DCB0160 · ABDM FHIR · IAPT dataset Why This Role Matters The integrations built in year one become the foundation of a data asset that compounds over time. The person in this role shapes that architecture, works directly with the UK leadership team, and has board- and investor-level visibility. If you want to build something that matters inside a company still small enough for your decisions to define it, this is that role. Our Process 1.

Application via the form below. 2.

Design exercise (your choice): a 1-page written approach

or a 45-min design discussion on a real Cerina integration problem — e.g. “how would you architect GP Connect (FHIR) read access plus SNOMED write-back across EMIS and SystmOne as a single build, and how would you sequence it against the NHS App?” 3.

Final conversation with the team and UK leadership, plus references.