The operating system for integrated care

Care happens in real time. Why does the data arrive weeks late?

What commvita is

One platform for a whole health system.

LIVE · updated now LEGACY · 19 days old
commvita™ Flow©

The system as one managed flow.

Front gate
λ 142/d
ED
WIP 38
AMU
WIP 24
Ward
WIP 61
D2A
constraint
Home
μ 118/d
← back-pressure: the binding constraint is Discharge to Assess
Ward to board

From incident to board assurance.

Event
incident
Theme
clustered
Systemic
issue
Risk
register
BAF
objective
evidence carried at every step · counts reconcile · de-escalation needs abating signal
LeftShift Intelligence©

Digital maturity, measured live.

Analogue → Digital
Hospital → Community
Sickness → Prevention
ImmatureEmergingDevelopingEstablishedLeading
▲ your system · Established, and moving
The path

Start where you’re. Grow when you’re ready.

Health, connected.
One record · one chain from ward to board · one platform
Commvita Flow EditionGovernance & AssurancePopulation Platform
0:00 / 1:20

A shared care record. An operations platform. One place for board oversight. Every health system needs all three — and buys dozens of products to get them, with procurement after procurement, integration after integration, and people whose job is keeping them in step. This is one platform that is all three, which is why the incident recorded on a ward becomes the risk on the board’s register without anyone re-keying it. openEHR-aligned, so it’s your data, not ours.

The problem

The system moves continuously. The data stands still.

The most expensive integration engine in any care provider is its own people — clinicians and administrators re-keying between systems and reading one screen at a time to assemble a picture that should already exist. Managers then make strategic decisions on data that was out of date before the pack was printed.

01 · FRAGMENTATION

Dozens of silos

Primary care, community, mental health, social care and acute each run separate systems. The person is scattered across all of them and whole in none.

02 · POINT SOLUTIONS

A tool for every task

Board management here, a risk register there, incidents somewhere else — each bought, integrated and maintained on its own, none of them speaking.

03 · PEOPLE AS GLUE

Staff as the middleware

When systems don’t connect, humans carry the data between them — the most costly, error-prone and demoralising integration layer there is.

Design for flows, not queues. People are never the workaround.

The proposal

Stop buying systems. Run one.

One open record — openEHR, FHIR, SNOMED — carrying clinical, operational and governance in a single platform you host yourself. Start at £1 an instance, prove it on your own estate, expand when you choose. The data stays in an open standard, so leaving is always possible: we want you to stay because you want to, and not because you can’t get out.

01 · OUTCOMES

Decided on everything that’s known

The whole person in one record, in real time — so the intervention is chosen on all of it, not on the fragment the system in front of you happens to hold.

02 · ACCESS & EQUALITY

Routed on need

Need visible by cohort and deprivation, so access and waiting are managed on who needs care most, not on who is best at navigating the system.

03 · VALUE FOR MONEY

An ambition of 80% off

One platform in place of a stack of point systems, their integrations, their infrastructure and their assurance overhead. The ambition is an 80% reduction in total cost of ownership.

04 · WORKFORCE

Shorter, simpler, safer days

One record, one login, one worklist. The people currently employed to move data between systems get to do the job they trained for.

Judged the way you’re judged — on outcomes, access, cost and staff experience, not a feature list.

Before you ask

We aren’t an AI company with a health product.

The order matters. Every platform now claims to be AI-first; most are a proprietary database with a model on top. commvita is a record and a platform first, and the intelligence sits on it — governed, human-in-the-loop and switchable off.

01 · THE RECORD IS THE PRODUCT

Open from the first entry

A real-time whole-person record built to openEHR’s record shapes, with FHIR and SNOMED at the edges. A model can read that record. It’s no substitute for having one.

02 · AI IS A COMPONENT

Yours to choose, or to switch off

Configure Claude, Microsoft Copilot or OpenAI — or none at all. Keys stay server-side, the provider is swappable, and with the AI off every module still runs.

03 · NOT A MEDICAL DEVICE

It drafts. A person signs.

It helps organise the work. It doesn’t diagnose. Every AI output is review-gated — the board narrative is drafted and held for approval, and the override log is on the record.

Judge it the other way round: take the AI out and ask what is left standing.

The proof

It’s built. It’s running. You can see it.

Not a roadmap and not a prototype. The platform is complete across primary care, community, mental health, social care, acute and governance — on one record, in one codebase, deployable on infrastructure you own.

618
modules in the registry — one platform, not a suite of acquisitions
567
live today — 39 built and 12 stubbed, nothing in the backlog
13
national data platform products with a mapped equivalent running here
16
jurisdictions configured from one codebase

That proves the platform exists and runs. It doesn’t yet prove outcomes at scale in your organisation, and we won’t claim it does — which is exactly what a first deployment is for.

See it

One record in the middle. Everything else binds to it.

The whole platform on one page, in five layers — from the surfaces people touch, down to the services every module shares. The band across the centre is the point of the design: one person and record spine, one interoperability layer, and every theme above and below reading and writing that same record. Integration happens once, at the edge, and not between the themes.

The person

One record that follows someone across primary care, community, hospital and social care.

The flow

Demand and capacity as one line, with the real bottleneck named instead of assumed.

The oversight

One chain from a ward incident to the board’s risk register, carrying its evidence.

The escalation

Breaches and entry points, marked where they happen and counted where they land.

Colour does one job on this site and only one. It’s the same meaning in the mark, on the page and inside the platform — so the plate below can be read not decoded.

commvita — Module Linkage & Product-Theme MapA representative system map of modules grouped by product theme, with the documented cross-cutting architectural spines. Modules shown are exemplars of each theme.01PEOPLE-FACING— how a person, carer or clinician reaches the servicePatient PortalPortal · nudges · feedback · NHS AppReferrals & Accesse-RS · triage · waiting list · RTTAmbulance & Pre-HospitalCrew app · JRCALC · handoverFront Door & AssistMyDay · Concierge · Ask commvita02CARE DELIVERY— where care is actually recorded, across every settingClinical CoreConsults · meds · CDSSRemote & CommunityVirtual ward · RPMMental Health & SocialMH · IAPT · social careAllied HealthPhysio · OT · SLTCondition ProgrammesDiabetes · stroke · MSK03THE SPINE— one open record and one way in. Everything above and below binds herePERSON & RECORD SPINEEMPI Hub · Whole Person Record · Care Journey · Neighbourhood Health RecordopenEHR · FHIR R4 · SNOMED CT · dm+d — your data, in an open standardINTEROPERABILITY & EPR LAYERPulseGrid · HL7 Engine · EPR Hub · GP Connect · NRL · FHIR BulkThe only place integration work is needed — at the edge, not between themes04RUN THE ORGANISATION— operations, assurance and money, computed from the same recordFlow & OperationsFlow · OPEL · beds · dischargeGovernance, Safety & RiskIncidents · PSIRF · IG · AIBoard & AssuranceBoard · BAF · EPRR · HIMSSWorkforce & L&DRostering · staffing · LearnAnalytics & PopulationCohorts · PROMs · inequalitiesUS Care ManagementCCM · RAF · STAR · payerFinance & CommissioningTariff · ICB · Care Act05SHARED SERVICES— one of each, used by every theme above. Config-driven, not rebuiltPlatform & AIAI Hub · commvita Sign · flagsCommunications CRMCRM · telephony · SMS · NotifyJurisdiction & ConfigProfiles · packs · RBAC · policyWhat the lines meanPerson binding — every care surface reads and writes one record — no orphaned copiesPerson entry — portal, referral and front-door contact lands on the same recordFlow orchestration — ambulance → flow → bed → discharge; OPEL → on-call → EPRRFrom ward to board — event → theme → systemic issue → risk → board objectiveCohort to action — population analysis becomes recall, prescribing or a care planShared services — one AI hub, one e-signature, one CRM, one jurisdiction profileBackbone = person and record spine + interoperability layer. Non-SaMD. 622 modules, 565 live — boxes above name exemplars, not the full inventory.

See every module in the registry →

622 modules, 565 live. The boxes name exemplars of each theme, not the full inventory. On a narrow screen the plate scrolls sideways.

Why we started

We have been on both sides of this.

commvita didn’t start with a technology. It started with a frustration anyone who has both sold into public health systems and worked inside them will recognise. The integration never quite arrives. The data is never quite current. And the contract is always harder to leave than it was to sign.

Portrait of Martin Carpenter
Founder & Chief Strategy Officer

Sold digital health into public systems, then worked inside them. Frustrated by the integration that never arrived, by an industry competing on how hard it’s to leave instead of on total cost, and by a sprawl of separate products no other real-time industry would put up with.

"No airline, bank or logistics operator would run on data that’s weeks old. Health shouldn’t have to either."
Portrait of Hassan Chaudhury
Co-founder & Chief Commercial Officer

Sees digital health companies globally making the same mistake — solving a department’s problem instead of a system’s. Digital health should be an enabler of better care, not an end in itself.

"Digital health can do considerably more than it currently does."
Portrait of Marc Farr
Co-founder & Chief Data & Analytics Officer

Here for three reasons: openEHR at the heart instead of bolted on; system flow data brought together in a way not previously seen in health; and health inequalities made actionable rather than merely reported.

"Flow data and an open record in the same place changes what analytics can answer."
What only we can say

Five decisions a competitor can’t retro-fit.

Not features, which anyone can ship next quarter, but choices made years ago that everything since has been built on. Each one would cost a rival a rewrite instead of a release.

openEHR at the heart, not as a wrapper
Clinical data is written to an open, vendor-neutral repository from the first entry. Portability is a property of the design, not an export button bolted on for procurement questions.
Flow data and the clinical record in one place
Operational flow modelled as a production line — constraint, WIP, failure demand — alongside the person’s record. Analytics platforms have one; EPRs have the other. Almost nobody has both.
One thread from a frontline incident to a board objective
Not four products and a manual board pack. Evidence is carried, counts reconcile, and assurance de-escalates on abating signal instead of on a calendar date.
Jurisdiction is configuration, and it fails safe
Identifiers, terminology, funding rules and regulators resolve from a governed profile. Where a rule is missing the platform refuses to guess — it never borrows another country’s.
We don’t charge partners to integrate
No access toll, no certification tax to connect. The ecosystem grows because it’s open — and you stay because you want to, not because leaving is expensive.
Why commvita is different

Not another electronic patient record. One system for joined-up care.

Most platforms sell you a better silo. commvita removes the silos — five commitments the incumbents structurally can’t make.

01 · REAL TIME

Not overnight

The record updates as care is delivered. The number on the board is the number on the ward, right now.

02 · openEHR

Your data, not ours

An open, vendor-neutral record. Portable by design — you own it and can leave with it.

03 · ONE PLATFORM

Not many

The whole care journey on one record and one chain from ward to board, instead of a dozen contracts to integrate.

04 · JURISDICTION

By configuration

ID numbers, clinical terms, funding rules and regulators are settings, never written into the code. If one is missing, the system stops and not guesses.

05 · NO LOCK-IN

Stay by choice

Renewal earned on value, not on the cost of leaving. Partners integrate without paying a toll.

Built for health systems · judged on the four things you’re

Everything we build, judged on the four things you’re.

Point solutions each optimise their own box, then leave your people to carry the data between them. A system-level platform optimises the whole journey — so a gain anywhere flows to everywhere downstream. We measure the difference the way you’re measured — the Quadruple Aim: patient and population health outcomes, access and equality, value for money, and workforce experience and productivity.

Outcomes
Patient & population health — proof the intervention changed the trajectory
Access
Access & equality — routed on need, not on who can navigate the system
Equity
Inequality measurable and actionable, by cohort and deprivation
Value
Value for money — outcome per pound and per staff-hour

Staff experience and efficiency — one record, one login, one worklist. Less re-typing, less chasing, fewer duplicate assessments. The workarounds people rely on are brought into the open and reduced, not hidden.

Scenario 01 · frailty in winter

The deterioration nobody saw until the ambulance came.

An 82-year-old with COPD and moderate frailty lives alone. Her carer notices she is quieter than usual; her home monitor shows oxygen drifting down. Today those two facts sit in two systems that never meet.

Today

Two signals, two silos

The carer’s note goes to the agency system; the reading sits with the monitoring supplier. The GP sees neither. Nine days later she arrives by ambulance and is admitted for eleven days.

With commvita

Signals fuse on one record

Mood and observation land on the same whole-person record. The deterioration engine fuses carer-reported change, falling oxygen and frailty score into one amber flag — visible to the community team the same day.

Result

Treated at home

A virtual-ward review, a rescue pack and daily monitoring. No admission. The GP, carer and family all see the same plan; the outcome is recorded against her care goals, not just the contact.

Outcomes
Deterioration caught days earlier; admission avoided and independence retained.
Access & equality
Proactive contact reaches a housebound patient who wouldn’t have presented.
Value for money
An avoided admission and eleven bed-days released for someone who needs them.
Workforce
One record, one plan — no chasing three organisations for the same facts.
Scenario 02 · incident to board assurance

The fourth time was the first time anyone joined the dots.

An infusion pump is programmed incorrectly on a ward. It’s reported, investigated locally and closed. It happens three more times across two sites over five months — each time as a fresh, unconnected form.

Today

Four forms, four dead ends

Incidents live in one system, risks in another, the board pack in a third. Nobody sees the pattern; the board is assured a control is working because a form was completed last quarter.

With commvita

The thread promotes itself

The second event clusters into a theme; the third triggers a systemic issue carrying its evidence. It is promoted to one risk, linked to the board objective it threatens — no re-keying, evidence attached.

Result

Assurance that’s actually assured

The board sees the gap in control, the action, and the signal abating in live data. De-escalation happens on evidence, not on a calendar date — and every number drills back to the four events behind it.

Outcomes
A recurring harm stopped at event four instead of event fourteen.
Access & equality
Learning applied across both sites at once, not just where it was reported.
Value for money
One governance platform instead of four contracts and a manual board pack.
Workforce
The governance team stops re-keying and starts investigating.
Scenario 03 · the long wait nobody validated

Waiting longest, living in the most deprived postcode.

A patient in the most deprived decile has waited 41 weeks. He has missed two appointments — both booked on days he couldn’t get childcare or time off — and each miss pushed him further down the list.

Today

The list punishes the people it should protect

Non-attendance is recorded as a patient failure. Nobody sees that long waits cluster by deprivation, so the list is managed first-in-first-out and the gap quietly widens.

With commvita

An equity lens on the same list

The waiting list is ranked with an inequalities weighting alongside clinical priority. His communication needs are on the record, so contact goes out in the format and channel he can actually use.

Result

Contacted, prepared, treated — and the gap measured

Kept in touch while waiting, offered prehabilitation, and given an appointment he can attend. The inequality gap is measured before and after — so the board can see whether it actually closed.

Outcomes
Better-prepared patients, better surgical outcomes, fewer cancellations.
Access & equality
The access gap by deprivation is measured and narrowed, not just reported.
Value for money
Fewer wasted slots and less re-referral churn from avoidable non-attendance.
Workforce
Admin teams stop chasing non-attenders and start preventing them.
Three editions, one platform

Start where you’re. Grow when you’re ready.

Every edition is the same connected platform on the same open record — you switch capability on, you don’t replace systems. Own your platform, then govern your organisation, then run your health economy. No migration, no re-integration between the steps.

01 · START HERE

Flow

Own your platform

It’s the hub you host yourself. It carries the operational analytics of the NHS Federated Data Platform (FDP) and the insight commissioners need, on open standards — openEHR, FHIR and OMOP — with the core platform, the shared tools and a developer toolkit. A hub, not an electronic patient record system: no primary care, no clinical record.

Base edition
03 · FULL PLATFORM

Population Platform

Run your health economy

The clinical record and care delivery, day-to-day operations, patient flow and capacity, population health, and analytics and AI — everything, with governance built in.

Everything in Governance & Assurance
Flow · own your platform

See the whole system — and get it flowing — before you change a thing.

Most organisations begin here. Flow is self-hosted and joins the data you already hold, turning it into the FDP operational analytics and strategic-commissioning insight on open standards (openEHR / FHIR / OMOP) — without touching your clinical systems. Its first job is to make the system visible and get it flowing.

01 · THE CORE PLATFORM

A platform you own

A record built on openEHR, FHIR interfaces, logins and permissions, audit trails, integration, workflow, forms and reporting.

02 · FDP OPERATIONAL ANALYTICS

The system as one flow

Elective and RTT waits, diagnostics, theatres, winter and demand — plus the binding constraint and failure demand made visible in real time. The FDP operational analytics stay here, in Flow.

03 · BUILD ON IT

Utilities & toolkit

Dashboards, case management, and queries that return answers without copying your data. Plus data loading, document management, and a toolkit for partners to build on.

A hub, not an electronic patient record No clinical record at this edition Deploy on-premises or your own sovereign cloud Open exit, by right
A lower-risk alternative

The same national data ambition — without the integration and operating risk.

Organisations are being asked to hand their data to a single supplier’s analytics platform, on a contract that’s hard to leave, after an integration programme measured in years. There’s a safer route to the same result: run the same thing yourself, on open standards, on hardware you already control.

Risk
The proprietary route
commvita
Integration
A multi-year programme to lift data into someone else’s platform before value appears.
Connects over open FHIR and HL7 to the systems you already run; the hub sits over them, nothing is ripped out.
Where data lives
Your population’s data held in a vendor-operated environment.
On-premises or in your own sovereign tenancy. It never has to leave your control.
Operating model
Capability delivered through the vendor’s specialists; your team stays dependent.
Your team operates it; open standards mean the skills are transferable, not proprietary.
Exit
Data in a proprietary model — leaving means rebuilding.
An openEHR-aligned record and FHIR interfaces. Portable from day one; the exit is a right, not a negotiation.
Time to first value
Value arrives at the end of the programme.
Start as a reporting and flow hub, prove it, then switch on more. Each step is reversible.

We compare ways of delivering, not named suppliers. Judged on the risk of joining systems up, running them, and leaving.

Why lower risk matters

Risk removed is benefit delivered — measured the way you’re measured.

A lower-risk route isn’t a procurement technicality. Every year of integration programme is a year of outcomes not improved, and every pound of lock-in premium is a pound not spent on care. The four aims are how that difference shows up.

Outcomes
Capability lands in months, so proactive care starts years earlier.
Access & equality
You can target the neighbourhoods that need it without waiting for a national release cycle.
Value for money
No lock-in premium, no vendor-operated hosting, no rebuild to leave.
Workforce
Your people operate the platform with transferable open-standard skills.

And it composes. The same hub that replaces the analytics contract becomes the place you track risk and assurance, and then the clinical record — one platform, three steps, each one proven before the next.

Governance & Assurance · govern your organisation

Govern the organisation. Land clinical later.

The quickest way to see value, and the reason boards start here. Governance in one place, on an audit trail that shows if anyone tampers with it. The evidence comes from live data instead of being stitched together from separate tools. And there are no individual clinical records, so there’s no clinical certification to clear first.

01 · BOARD & RISK

Assurance that reconciles

Board portal, papers, committees, action tracking, decision logging and the Board Assurance Framework. Plus strategic and operational risk, a library of controls, a map of what your assurance actually covers, and how much risk you’re willing to carry.

02 · INFORMATION GOVERNANCE

FOI, DSAR & records

Freedom of information and subject access requests, with deadlines, redaction, review and drafted replies. Plus schedules for how long records are kept and when they’re destroyed, and a live register of the data you hold.

03 · AI GOVERNANCE

A headline, not an add-on

Every AI system, what it is used for and who owns it, on one register. With risk assessments, approvals, monitoring evidence, data protection impact assessments, and equality and safety checks.

04 · INCIDENTS & LEARNING

Incidents that become learning

Reporting, investigations, corrective actions, near misses, complaints and duty of candour — joined up with the rest of your assurance work instead of sitting on its own.

05 · AUDIT & COMPLIANCE

The organisational memory system

Internal and external audit, compliance, and evidence for inspections — all drawn from the same live record, so the evidence assembles itself.

Population Platform · run your health economy

A complete community health system. Every setting, one record.

Where you end up: the clinical record and care delivery across the whole community health system, plus day-to-day operations, patient flow and capacity, population health and analytics — with governance built in.

Primary careCommunity nursingMental health Social careCommunity ophthalmologyCommunity dentistry Ambulance & pre-hospitalSpecialist & AHPStaff portal Patient & carer portals
01 · GENOMICS

Embedded referral

Genomic testing referrals coded to clinical indication, consent-gated and routed to the laboratory — part of the record and the chain from ward to board.

02 · COHORTS · OMOP

Native OMOP export

Build research groups from the live record and export them in OMOP, the common format health researchers use — with traceable extracts and a tamper-evident log of where each one came from.

03 · EHDS · WHO

Aligned by design

We remove names from data, and hide numbers small enough to identify someone. This follows European Health Data Space and WHO standards.

commvita™ Flow©Seeded demo

The whole system as one managed flow — and the one thing holding it up.

Most dashboards show you twenty numbers. Flow shows you the production line — where work enters, where it queues, and which single station is setting the pace for everything behind it. Bound by Little’s Law, so the maths is honest: reduce demand or relieve the constraint, nothing else moves the queue.

← back-pressure: 24 patients are held upstream because D2A can’t pull. Every extra ward day is created here, not on the ward.
Little’s Law · L = λW λ in 142/d · μ out 118/d WIP 152 Flow efficiency 41% Pressure index OPEL 3
Demand classification — only the first band is value-creating

Seeded demonstration data — not a live system feed. The station volumes, constraint and demand split above are illustrative. In a deployed instance the commvita™ Flow Canvas© is computed from your own live ward, OPEL and discharge state, and the chip reads Live · API.

Outcomes
Shorter stays and fewer deconditioning harms when the constraint is relieved, not the ward pressured.
Access & equality
Front-door queues fall for everyone, not just those who escalate loudest.
Value for money
Bed-days released at the real bottleneck — 15% failure demand designed out, not absorbed.
Workforce
Teams stop firefighting the symptom ward and fix the station actually setting the pace.
The product, not the pitch

Every number on every screen drills to the people behind it.

A house rule, enforced in the build: no dead-end numbers. Every tile is a named query, every count reconciles with the list it opens, and every operational drill-down ends at the people composing it — within the professional’s lawful access.

Board Assurance Framework
Principal risks12
Red (≥15)3
Gaps in assurance5
Controls evidenced live78%
BAF-002 → 4 linked events
Click any risk to reach the events behind it — counts reconcile.
Whole Person Record
Frailty (CFS)6
Deterioration signalAmber
Settings contributing5
Medications · interactions9 · 1
Care-plan goals on track3 / 4
One record across primary, community, mental health, social care and acute.
commvita™ Flow Canvas©
Binding constraintD2A
WIP in system152
Held upstream24
Flow efficiency41%
Failure demand15%
The station setting the pace — and what it costs upstream.

These screens show how the platform really works. The numbers are examples — a live system works them out from your own data.

Digital maturity, in real time

Manage the journey to a modern care model — as it happens.

Digital maturity isn’t a form you file annually. It’s a live property of your system that moves every day. LeftShift Intelligence© measures it continuously and tells you the next move: are you genuinely shifting the model of care, and where should you push next?

SHIFT 01

Analogue → Digital

From paper and disconnected systems to a real-time structured record — the foundation everything else shifts on.

SHIFT 02

Hospital → Community

Care closer to home — neighbourhood teams, virtual wards and community response, tracked as a measurable shift.

SHIFT 03

Sickness → Prevention

Proactive population-level care that heads off crises, with evidence that demand is moving upstream.

LeftShift Index© · live composite maturity (0–100)
your system · Established, and moving

A steering wheel, not a snapshot — per-axis gauges, surfaced signals, a tracked action plan with owners, and a board narrative that assembles itself.

One chain, ward to board

Why buy Board, Risk, Incident and a Clinical Risk Register separately?

In most organisations these are four contracts, four logins and four disconnected datasets — and your team is paid to piece them together. A frontline incident never reaches the board risk that should have caught it. commvita makes it one continuous, traceable chain.

Incident Reporting · INC-4471
Infusion pump — wrong rateModerate
WardAMU
Reported byBand 5 RN
Duty of candourAuto
Similar events, 90 days7
Captured once, at the bedside. Nothing re-keyed after this point.
Corporate Risk Register · RSK-118
Infusion device competence12
Promoted from theme7 events
Controls3
AssuranceGap
Evidence carried7/7
The events came with it. The score is derived, not typed.
Board Assurance Framework · BAF-002
Objective: safe, effective care
Principal riskRSK-118
Gap in assuranceOpen
Signal, last 8 weeksAbating
Drill to source events7
The board sees the ward. De-escalation needs abating signal, not a date.

One chain, three surfaces — INC-4471 → RSK-118 → BAF-002. Representative data on the live product.

Underneath, the same chain as a model:

STEP 1
Event
An incident, complaint or near-miss, captured once.
STEP 2
Theme
Signals cluster — evidence carried, not re-typed.
STEP 3
Systemic issue
Recurring themes promoted with their evidence.
STEP 4
Risk
One risk record — operational, corporate and BAF lenses.
STEP 5
Board objective
Linked to the objective it threatens, with live assurance.
Mitigation spine: Risk → Control → Assurance, closed-loop. De-escalation requires assurance and abating signal from live event data — never a calendar date. Every risk drills back to the exact events that compose it, with counts that reconcile.
What we do better

Six systems, six invoices, one integration headache — or one platform.

Board Management platform + licence
Risk Management system + licence
Incident Management tool + licence
Clinical Risk Register + licence
Complaints & Duty of Candour + licence
CAPA & action tracking + integration
Governance & Assurance edition

Risk and assurance in one place

Board, risk, incidents, clinical safety, complaints, corrective actions and the Board Assurance Framework — plus the workforce side that usually sits in separate systems: mandatory and information-governance training, appraisal, rostering, safe staffing, job planning, bank and agency, and freedom to speak up. On one record and one chain from ward to board. Nothing to integrate, nothing to reconcile, nothing lost between suppliers.

  • Board & BAF
  • Risk
  • Incidents
  • IG · FOI · DSAR
  • AI governance
  • Training & CPD
  • Workforce & rostering
  • Audit & evidence
  • EPRR & on-call
Total cost of ownership

A target of up to 80% off software and total cost of ownership.

Total cost of ownership isn’t just licences. It’s the integrations, the infrastructure, the assurance overhead — and above all the people paid to move data between systems that should have been one. Collapse the stack and you collapse all four.

Traditional stack100
commvita — one platform≈ 20
LicencesIntegration InfrastructureStaff time to integrate commvita
TARGET REDUCTION
80%

off software and total cost of ownership when the stack — and the human integration layer it depends on — is replaced by one real-time platform.

Illustrative model. Actual savings depend on the systems replaced and integration burden removed — a planning target, not a guarantee.

Open by design

Your data. Your standards. Your freedom to leave.

Lock-in is the incumbent’s business model. It isn’t ours. commvita follows openEHR, an open standard no single supplier controls. Your record stays portable from the first day. We earn renewal on what the platform is worth to you, not on how expensive we have made it to leave.

01 · openEHR CDR

A vendor-neutral record

Clinical data is written to an open, vendor-neutral repository — not a proprietary schema only we can read. Structured, portable, exportable.

02 · FHIR · SNOMED · OMOP

Standards, not walls

FHIR R4 interfaces, SNOMED CT clinical terms and research extracts in the OMOP standard — the platform speaks the language every other system does.

03 · NO ACCESS TOLL

Partners plug in free

Third parties integrate through open interfaces without paying us a toll to connect — an ecosystem that grows because it’s open, not taxed.

You stay because you want to — not because you have to.

Multi-jurisdiction, by configuration

One platform that speaks every system’s rules — without a rebuild.

Countries, Crown Dependencies and international health systems use different ID numbers, clinical terms, funding rules, regulators and ways of working. None of that’s written into commvita’s code. Each value is a dated, sourced entry in a country profile, and the most local setting wins. If a rule hasn’t been set, the platform stops in a neutral state not quietly borrowing another country’s.

01 · CONFIGURED

Configuration, not code

Patient ID numbers, clinical terms, regulators, background checks, funding and eligibility rules, residency and legal requirements — all read from one profile. Opening in a new country means signing off a configuration, not writing new software.

02 · FAIL-SAFE

Fail-safe, never assumed

A country can’t go live until its required settings are signed off and up to date. Missing or expired values never fall back to another country’s rule. Safety and sovereignty come first.

Nations & regionsCrown DependenciesInternational systems Most local setting winsSourced & effective-datedSigned off before go-live

Stop integrating systems. Start connecting care.

See the real-time record, the chain that runs from a ward incident to board assurance, and the full cost case — mapped to your organisation in a single walkthrough.

info@commvita.com
Registered office: 20 Wenlock Road, London, England, N1 7GU · Company number 17404587
© 2026 commvita™. All rights reserved.
● Real-time record on openEHR ◍ Illustrative cost model — planning target, not a guarantee