Help NHS digital programmes
actually succeed.
Every major NHS EPR go-live, PAS upgrade, and ICS shared-care-record stand-up fails at the same point — the moment systems flip live and clinicians can't find what the SOP says to do. WYRM Healthcare ships a three-product trinity that addresses the operational reality, not the slide deck.
Vendor-neutral. Works on Epic, Cerner / Oracle Health, EMIS, TPP, Vision, System C, IMS Maxims, or our own substrate.
The problem
NHS go-lives bleed at the human-system interface, not the system itself
The EPR you picked is fine. The migration plan is fine. The training was fine. What breaks is procedural recall under pressure at 2am of week two, when the super-user is asleep and the SOP is on a SharePoint folder nobody can find.
Procedural recall fails under pressure
At 2am during stabilisation, the clinician on shift is the clinician least likely to remember which screen captures the allergy in the new system. The SOP exists. It is on the intranet. It is not where the clinician is looking. Compass is in Teams where they already are.
Super-users get overwhelmed
A typical EPR go-live runs ten to thirty super-users for a trust of 2,500 clinicians. Routine procedural questions consume all of their time. The judgement calls that actually need them queue up. Compass answers the routine; the super-users handle what only they can.
Incidents lag by days
Datix reports lag the actual incident by 48 to 72 hours during go-live. The programme team learns about an emerging cluster after the fourth or fifth instance. Compass classifies questions live and surfaces clusters within the hour.
| Downtime risk | 48-72h target cutover |
| Retraining | ~60h per clinician |
| Lock-in | Vendor-controlled exit · 5y+ to amortise |
| Reversibility | Effectively none post-cutover |
| Downtime risk | Zero downtime · per-cohort cutover |
| Retraining | ~4h per clinician (Compass surface only) |
| Lock-in | None · reverse manifest preserved throughout |
| Reversibility | Send-Document back to incumbent at any time |
The trinity
Three products. One substrate. Land any of them first.
Compass earns the relationship at go-live. Migrate sells at the next contract renewal. Manage compounds over years. Any single pillar is a viable standalone business; together they are a category.
WYRM Compass
Vendor-neutral clinical operational assistant
A clinical-safety-cased AI assistant trained on your trust's own SOPs, runbooks, escalation matrices, and architecture documents. Clinicians ask procedural questions during go-live and beyond. Compass cites the source SOP, surfaces the escalation path, refuses clinical-advice questions, and routes low-confidence answers to a named human. Works on Epic, Cerner, EMIS, TPP, Oracle Health, or our own substrate.
- Lands first — sells into competitor go-lives
- Per-trust DCB0129 Safety Case
- Microsoft Teams, web, mobile
- Immutable audit log, no hard usage caps
WYRM Migrate
Migration-by-replay via GP Connect Access Record
EMIS, TPP, Vision, Cerner, and Oracle Health will not voluntarily export their patient records. They do not have to. NHS England has already mandated the channel. Migrate pulls each patient's consolidated record over GP Connect Access Record: Structured, normalises STU3 to FHIR UK Core R4, maps terminology via the NHS Terminology Server, reconciles identity against PDS, and cuts over atomically per patient with a Send Document reverse manifest. Dual-run reconciler and exit-ramp snapshot guarantee no data is locked in.
- No incumbent vendor cooperation needed
- STU3 to FHIR UK Core R4 normalisation
- Atomic per-patient cutover + reverse manifest
- Destination-agnostic — including away from us
WYRM Manage
Compounding operational memory
After stabilisation, Compass does not go away. It ages into the trust's permanent operational memory — new starters onboard through it, SOPs auto-ingest from the intranet, incident classification feeds continuous improvement. Booking optimisation, no-show prediction, NHS Notify wrapped patient comms, population-health analytics, SNOMED CT enrichment for QOF and IIF, and regional shared-care-record participation all layer in on the same substrate.
- Permanent institutional memory
- Booking + no-show optimisation
- QOF / IIF SNOMED CT enrichment
- Regional ShCR participation
- Datix payload (anonymised) into the WORM audit log
- Narrative tokenised + theme-tagged (verbal-prescription · handover · medication)
- Cross-references existing SOPs touching those themes
- Flags the cluster to Patient Safety committee queue
See the trinity in action
Interactive demos. Real inputs. Fictional trust.
Three working demos for the three pillars. Compass takes typed questions and runs a real lookup over the trust's SOP corpus. Migrate runs a dry-run pipeline over a chosen source EPR + cohort. Manage drives a live booking optimiser and operational-memory query surface. All data fictional; production deployments are gated by a per-trust DCB0129 Safety Case.
Tap a preset or type a procedural question — try one about an allergy or downtime SOP.
Interactive demonstration. All trust documents, EPR data, and operational metrics shown are fictional. Production deployments are gated by a per-trust DCB0129 Safety Case.
Vendor-neutral
Works on whatever EPR you actually have
Compass is trained on your trust's own documents, not on a particular EPR's data model. It reads SOPs, runbooks, escalation matrices, and architecture specs — and answers questions about whichever system those documents describe.
Inclusion is a statement of intent, not a partnership claim. WYRM Healthcare is an independent UK supplier with no contractual relationships with the EPR vendors named.
Clinical safety + compliance
The substrate the LLM-RAG entrants can't match
Anyone can spin up a RAG over your SOPs in a week. The clinical-safety substrate — DCB0129 Safety Case, DSPT v8 with CAF-aligned independent audit, DTAC v2, a named Clinical Safety Officer on retainer — takes twelve months and is gate-kept by senior clinician availability. WYRM Healthcare carries that posture so individual NHS deployments don't have to.
DCB0129 Safety Case
Per-trust safety case with named hazards, controls, and a hazard log maintained across deployment versions. Reviewed by your CSO and ours every quarter.
DSPT v8 + CAF-aligned audit
Standards-met with the 2025/26 CAF-aligned independent-audit requirement that now applies to in-scope IT suppliers.
DTAC v2 pack
Full DTAC v2 (mandatory from 6 April 2026) coverage across clinical safety, data protection, technical security, interoperability, and usability.
Named Clinical Safety Officer
A senior clinician on retainer with current GMC or NMC registration and clinical-safety training. Available to your CSO for joint safety reviews.
Cyber Essentials Plus
Independently audited annually. UK-only data residency on AWS London or Azure UK South.
Immutable audit log
Every Q/A persisted to a WORM store with 25-year retention. Every refusal carries reason, escalation path, model version, and audit ID. Surfaced for incident review without ceremony.
- ·PAT-001 v2.3 (rank 1, score 0.92)
- ·PAT-001 v2.2 (superseded, rank 2, 0.78)
- ·DOWN-001 v1.7 (rank 3, 0.41)
Returned PAT-001 §3.1 v2.3 procedure with PDS-trace cross-reference. 178 tokens · 412 ms.
Usage-based, no hard caps
A clinician is never denied at the moment they need help
WYRM Healthcare bills usage-based — customers pay for their own LLM usage with our margin on top. Soft thresholds at 80%, 100%, 150%, 200% trigger finance emails, CIO notifications, and admin warnings. Service continues at every threshold. Our customer contract carries an explicit operational-emergency clause: during incidents we serve over-budget and bill afterwards. It is the commercial expression of the clinical-safety principle.
How we price
Every WYRM Healthcare engagement is bespoke to the trust — scoped per contract, with a dedicated go-live director who owns delivery end to end. Compass, Migrate and Manage are sized to your estate, corpus and clinician count rather than a list price. Usage is billed transparently — you pay for your own LLM usage, with our margin — under soft thresholds that never interrupt clinical service. Talk to us for a scoped proposal.
Honest answers
Frequently asked
Does WYRM Compass replace our EPR?
No. Compass is vendor-neutral. It sits alongside your existing Epic, Cerner, EMIS, TPP, Oracle Health, or other EPR and helps your clinicians use it. WYRM Healthcare does have an EPR substrate of its own for trusts who want to migrate, but Compass works regardless of what you run today.
Is Compass clinically safe?
Production deployments carry a per-trust DCB0129 Clinical Safety Case, named Clinical Safety Officer, and DSPT v8 alignment. Compass refuses clinical-advice questions outright and routes to a named human; every refusal is logged. It only answers procedural questions, grounded in the trust's own SOPs, with citation enforced server-side — no answer is permitted without source references. Low-confidence answers escalate to a named super-user with rota awareness. Every Q/A is retained in an immutable audit log per NHS retention policy.
How does WYRM Migrate work without cooperation from our incumbent EPR vendor?
It uses GP Connect Access Record: Structured — the FHIR STU3 channel NHS England has mandated every conformant GP system serve. We pull each patient's consolidated record (problems, medications, allergies, immunisations, observations, encounters) over that channel without needing the incumbent vendor to do anything. The record normalises to FHIR UK Core R4, terminology maps via the NHS Terminology Server, identity reconciles against PDS, and cutover is atomic per patient with a Send Document reverse manifest that lets the incumbent record retain a pointer.
What about free-text consultation notes and attachments?
GP Connect Access Record: Structured deliberately excludes free-text consultation bodies. For primary care, community, mental health, and outpatient work this is acceptable and well-precedented. We supplement with MESH inbox sweeps for lab and discharge documents, and with any contractually-available document-store dumps. We are explicit with prospective customers: we deliver structured-record migration plus linked-document retention, not a complete consultation-history migration. For acute trusts, the migration scope is materially different and we will say so.
How does usage-based billing work? Won't a busy go-live week bankrupt us?
Billing is usage-based and scoped per contract — customers pay per answer with a per-clinician seat fee, sized to your trust rather than a list price. Your monthly budget has soft thresholds at 80%, 100%, 150%, and 200% — finance gets emails, the CIO gets a notification, and admin gets an over-budget approval flow. Service continues at every threshold. We have an explicit operational-emergency clause in the contract: during incidents we will continue to serve over-budget and bill the customer after the fact. No clinician is denied at the moment they need help. This is the commercial expression of the clinical-safety principle.
Is WYRM Healthcare available now?
Pre-pilot. We are pre-recruiting our Clinical Safety Officer, completing Cyber Essentials Plus and DSPT v8 standards-met submission, preparing the DCB0129 v1 Safety Case for our first deployment, and building out the production substrate. We are taking pilot conversations now and aim to be in our first trust deployment in 2027.
Do you support NHS Wales, Scotland, or Northern Ireland?
v1 targets NHS England providers because the GP Connect, PDS FHIR, NHS login, CIS2, and NHS Notify integrations we depend on are NHS England programmes. Compass itself is portable to the devolved-administration estates because it does not depend on the integration layer. We are happy to scope devolved-administration engagements case by case.
Where is data hosted?
UK-only data residency on AWS London (eu-west-2) or Azure UK South, your choice. Per-tenant isolation. The customer corpus never leaves the customer tenant. LLM calls are stateless under no-retention contracts. The audit log is WORM-stored with 25-year retention per NHS policy. Production deployments are gated by DSPT v8 with CAF-aligned independent audit per the 2025/26 requirement.
Bring us in early.
We are pre-recruiting our Clinical Safety Officer, drafting the v1 DCB0129 Safety Case, and taking design-partner conversations with NHS trusts and ICSs that are 6-12 months out from a major EPR programme or stabilisation cycle. Early design partners get substantially reduced commercials and direct influence on the v1 build.
Status — Pre-pilot. WYRM Healthcare is in build. No clinical data, no NHS integrations live, no DCB0129 Safety Case yet on file. The Compass demo conversation rendered above is a static illustration of intended behaviour using a fictional trust (Ashmere Vale NHS Foundation Trust) and a fictional EPR (Aurora EPR). Any resemblance to a real organisation is unintentional. Production deployments are gated on Clinical Safety Officer appointment, DSPT v8 with CAF-aligned independent audit, DTAC v2 pack, and a per-trust DCB0129 Safety Case File.
Vendor neutrality — WYRM Healthcare is independent of Epic Systems, Oracle Health, EMIS Health, TPP, Vision Healthcare, System C, IMS Maxims, and Allscripts. EPR product names appear here as a statement of WYRM Compass's technical compatibility scope only. No partnership or endorsement is claimed by either party.