Adoption
A path where the first step costs almost nothing
No Trust should bet a reporting function on an early reference build. So the path is staged deliberately: each stage is independently useful, and stopping after any of them leaves you better off than not starting.
Four stages, four defined stop points
Technical evaluation
A named team reviews the schema, transformation logic and API against your own PAS shape. Nothing is deployed and no data moves.
- Duration
- 2–4 weeks
- Commitment
- A few analyst days
- You end up with
- A written technical opinion your Board can read.
Synthetic pilot
The stack is deployed into your tenancy and loaded with synthetic data. Access controls, audit and reconciliation are tested against your own IG expectations.
- Duration
- 4–6 weeks
- Commitment
- One environment, no patient data
- You end up with
- A working environment plus a completed draft DPIA.
Single-domain proving ground
One real domain — typically RTT or diagnostics — is loaded and reconciled against existing reporting until the numbers agree line by line.
- Duration
- 8–12 weeks
- Commitment
- One domain, one reporting line
- You end up with
- A production-grade domain your reporting team trusts.
Phased extension
Further domains are added at whatever pace the Trust chooses, with each one reconciled before it is relied upon.
- Duration
- Ongoing
- Commitment
- Domain by domain
- You end up with
- A canonical repository the Trust owns outright.
What we would ask of a design partner
- A named technical sponsor and a route into your IG function.
- Access to your PAS data dictionary — structure, not data.
- Honest feedback when the model does not fit your reality.
- Agreement that improvements return to the open repository.
What a design partner gets
- Direct influence over the canonical model and the roadmap.
- Hands-on support through evaluation and pilot at no licence cost.
- An asset the Trust holds permanently, source available and Apache-2.0 on its Change Date.
- A credible, documented exit position for any future platform decision.
The Board ask
Nothing on this page requires a procurement decision. The ask is a technical evaluation by a named team, and permission to bring the findings back to the Board. If the evaluation is negative, the Trust has spent a few analyst days and learned something useful about its own data estate.
Next step
Start with an evaluation, not a commitment
Open the sandbox to see the substance first, then request access if your team wants to look under the bonnet.