Resources
Everything you need to form your own view
The public material below explains the position and the standards it rests on. The build artefacts are released to named evaluators.
Open material
Released to authorised evaluators
Available after your access request is approved.
Canonical schema DDL
The full generated 72-table model with keys, constraints and value sets.
dbt transformation project
Source-to-canonical models plus the generated test suite.
FHIR UK Core service
Read API implementation and OAuth2 configuration.
IG starter pack
Draft DPIA, data flow map and retention positions.
Exit & cutover runbook
The 90-day plan with reconciliation gates.
Deployment templates
Docker Compose and the AWS / Terraform target.
Standards this is built on
NHS Canonical Data Model
The published model the schema is generated from.
FHIR UK Core
The profiles the read API conforms to.
NHS Data Dictionary
Value sets used in the accepted-values tests.
Open Government Licence
The licence covering the published NHS model.
Business Source License 1.1
The licence CDP itself is released under.
Frequently asked questions
Is this a replacement for the national platform?
No. It is a repository that sits in your own estate. A Trust can run it alongside any national or commercial platform — the point is that the canonical copy of your data no longer depends on one.
Can it hold data from our existing FDP instance?
Yes. CDP is built on the same NHS Canonical Data Model, so data exported from an existing FDP instance can be loaded into its canonical tables and reconciled. It is designed to be a repository you own, not a competing platform.
Is it compatible with the national FDP instance?
It is aligned by design. CDP uses the published NHS Canonical Data Model and FHIR UK Core — the same standards that underpin the national FDP programme — so the data shape and API surface are structurally compatible.
Has it been used with real patient data?
No. It has been exercised against synthetic data only. That is the single biggest limitation of v0.1 and the main reason we are looking for a design-partner Trust.
What does it cost?
Evaluating, testing and non-production use are free. A production instance holding live Trust data needs an annual instance licence, which includes model currency, support and IG evidence. Every release converts to Apache-2.0 four years after publication.
Who owns changes we make?
You do. The licence lets a Trust fork and modify freely, and keep those changes private. We would like improvements offered back, but nothing obliges you to.
Why can't we download the code from this site?
Access is individually authorised at this stage so we know who is evaluating it and can support them properly. It is a release process, not a licence restriction.
What happens if VUIT Data Labs stops working on it?
The repository stays where it is: in your tenancy, with readable SQL, and with a Change Date that converts it to Apache-2.0 regardless of what happens to us. That is the entire argument for building it this way.
Next step
See it before you commit to anything
Open the synthetic sandbox to see the canonical model, the FHIR API and the pathway analytics working — or request evaluation access to the reference build itself.