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

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.

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

2026 is the year the pieces line up.

The problem above isn’t new. What’s new is that five things have arrived at the same time, and together they change what a health system can sensibly buy.

Each of these is a reason to look again. Together they’re the reason to look now.

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.

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

Meaning, movement and adaptation. Three ontologies, one platform.

commvita isn’t an openEHR system with screens on top. It holds three kinds of knowledge about a health system and keeps them in one place, so each one acts on the others. That way of describing a platform is used well beyond health, and we don’t claim to have invented it. What’s different here is where it sits: on the live record, on your estate, with the rules inside the system people use.

The layers in more detail are on the Approach page, and a measured account of what is built, partly built and absent is in the architecture explainer.

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.

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.

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.

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."

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."

Professor 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."

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.

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.

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.

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.

Start where you are. 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.

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.

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.

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

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.

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.

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.

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.

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.

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

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?

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

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.

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

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.

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

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.

commvita is a platform for running services and supporting decisions. It doesn’t diagnose. A person always reviews what the AI drafts, and it never makes clinical or funding decisions on its own. How it behaves in each country is set up and signed off before it goes live. Cost figures are planning estimates. They depend on which systems you replace and how much integration work you remove.