commvita™ — NHS FDP vs Commvita Flow Edition

A direct, product-by-product comparison so a buyer who knows the NHS England Federated Data Platform (FDP) can see exactly what the Flow Edition delivers against it. The mapping below is the same canonical mapping the product itself uses, so what is claimed here is what ships.

Key. ● Live = real API-backed logic wired end-to-end today. ◍ Demonstrated = representative control surface with seeded data or an illustrative UI. Every row below is one of the two — nothing here is a roadmap item.

The headline difference

NHS England FDP

A national data platform delivered on a proprietary commercial stack under a national contract.
Data is lifted into the platform's own environment and model.
Capability arrives through national product releases and the Solution Exchange.
Integration is a programme; value follows the programme.
Exit means rebuilding on a different platform.

Flow Edition

The equivalent capability, self-hosted, at £1 per instance (perpetual, optional support).
Data stays on your infrastructure, in openEHR and FHIR R4 — portable by right.
Capability is switched on locally, at your pace, not a national release cycle.
Connects over open standards to what you already run — nothing is ripped out.
Exit is an export, not a rebuild. Partners integrate with no access toll.

Product-by-product mapping

Domain	NHS FDP product / use-case	commvita Flow Edition module	What the Flow Edition module delivers
Data platform	Canonical Data Model (DAPB4121) — the FDP data layer	FDP CDM — Trust Data Console /fdp-cdm	Open, self-hostable store for acute NHS data in the FDP Canonical Data Model — canonical schema · DQ tests · FHIR read API (UK Core) · governance/RLS. Logical/data-spec interoperability, not Foundry physical parity.
Data platform	Foundry data integration & pipeline monitoring	PulseGrid — Integration Assurance /connector-dashboard	Dual-endpoint (source/target) integration monitoring over 12 EPR connectors with protocol-native probes (MLLP/FHIR/REST) — open, self-hosted.
Urgent & emergency care	UEC demand & capacity forecasting	A&E Demand Forecasting /ae-demand-forecast	ML 7-day A&E demand forecast, hourly profiles, surge prediction and OPEL bed-demand — MHRA-AIaMD non-SaMD governance built in.
Urgent & emergency care	Care coordination — patient flow / OPEL	CommVita Flow /flow	ICS operational control centre: OPEL, Little's-Law flow canvas, constraint detection, ambulance front door and D2A pipeline — decision-support, not just a dashboard.
Urgent & emergency care	Care coordination — care transfer hubs / discharge	Discharge Hub /discharge-hub	SAFER-bundle discharge coordination, D2A pathways, delayed-discharge reason coding, cross-setting onward capacity and closed-loop discharge actions.
Urgent & emergency care	Winter / UEC pressures	Winter Pressures Forecast /winter-pressures	6-week forward OPEL projection with flu/RSV modelling, scenario planning, mutual-aid cascade and UKHSA surveillance.
Elective recovery	Elective care coordination (Waiting List Management / RTT)	RTT PTL Dashboard /rtt-ptl	Patient-level PTL with RTT clock RAG, breach prevention, IS capacity and GIRFT benchmarking — plus IMD/CORE20PLUS5 inequality-weighted list ranking.
Elective recovery	Theatre scheduling & utilisation	Theatre Productivity /theatre-productivity	Utilisation/on-time-start analytics, case-mix, ODP staffing and GIRFT benchmarking — plus carbon-aware Greener-NHS scheduling.
Diagnostics	Diagnostics capacity & imaging waits	Diagnostics Capacity /diagnostics-capacity	DM01 6-week standard tracking, modality demand-vs-capacity, report turnaround and Community Diagnostic Centre utilisation.
Population health	Population Health Management	Population Health + Open Phenotypes /population-health	Risk stratification, NLP cohort builder and portable openEHR/OMOP+AQL phenotypes with cohort-to-action (recall / social prescribing / CDSS).
Community & remote	Virtual wards / acute-at-home	Virtual Ward Hub /virtual-ward	Live bed board, NEWS2 obs, step-up alerts, MDT review and cost-vs-physical-bed outcomes for the acute-at-home mandate.
Supply chain	Inventory management / supply chain	NHS Supply Chain /nhs-supply-chain	GS1-coded catalogue, PO lifecycle, ward-level inventory, supplier scorecards and autonomous par-level reordering on open feeds — no national platform contract required.
Research & secondary use	Secondary use / SDE-adjacent analytics	OMOP Transformation / Clinical Studies /omop-cdm	Real OMOP CDM v5.4 ETL (CSV/Parquet) with DQD, k≥5 suppression and an OHDSI network node — portable, open, no vendor lock-in.

Where the Flow Edition goes further

Inequalities as a first-class lens. IMD / CORE20PLUS5 weighting is built into waiting-list ranking and population analytics, not a separate report — so long waits and care gaps can be targeted where need is greatest.
Decision-support, not dashboards. Flow applies Little's Law and Theory of Constraints to name the binding constraint; tiles drill through to the people behind the number, and counts reconcile.
Open research path. Cohorts export natively to OMOP CDM v5.4 with a tokenised extract ledger and a data-quality report — no separate analytics stack to licence.
Governed AI. Model cards, human-in-the-loop gates and a tamper-evident prompt audit ship with the platform.

Where the FDP is ahead, and what that means

Stated plainly, because a comparison that concedes nothing is not credible: national scale and mandate — the FDP is a national programme with central funding, national data flows and centrally-negotiated information governance; national datasets — access to central flows that a self-hosted instance must be granted separately; and an established national assurance route. The FDP is not itself a national data flow, and the distinction matters here: it is Palantir Foundry deployed into trust and integrated-care-board tenancies, so a trust's FDP tenancy is a local platform consuming the national datasets exactly as any local platform must. What the FDP has that the Flow Edition does not is the programme around it — central funding, centrally-negotiated information governance and a granted route to the central datasets. That is a real advantage and it is not a technical one. The Flow Edition can run alongside an FDP tenancy or in place of it: alongside, because the Trust Data Console emits extracts validated against the published FDP Canonical Data Model; in place of, because the operational products in this comparison are the FDP's own use cases.

What the Flow Edition does not do today, stated because the sentence above used to imply otherwise. It does not ingest the central flows. Measured in this build: the SUS/HES and GPES surfaces register five and four endpoints between them and make zero database queries — they are demonstration surfaces, not pipelines, and /national-audit-feeds and /cqrs-reporting register no endpoints at all. A deployment that needs those feeds needs them built and granted, and the grant is the longer half. The one national return that is genuinely wired is MHSDS, and that is an outbound submission rather than consumption.

Data model alignment

The Flow Edition includes a Trust Data Console implementing the NHS FDP Canonical Data Model (DAPB4121), with schema-validated extracts emitted against the published CDM object schemas. The honest ceiling is stated in-product: this is logical / data-specification interoperability with the FDP CDM — it is not physical parity with the FDP's underlying commercial platform, and it is not an organisation-level DAPB4121 certification.

commvita™ — NHS FDP vs Flow Edition v1.0 · July 2026. FDP product names follow the NHS England FDP national products and Solution Exchange catalogue; verify against the live catalogue before external use. Comparison is of delivery models and shipped capability. © 2026 commvita™. All rights reserved. Errors & Omissions Excepted (E&OE).