Few technology programmes in Britain attract as much attention as the NHS Federated Data Platform. Most of that attention focuses on the supplier. This piece deliberately does not.
Instead, it looks at what the programme's numbers tell us about something every large organisation struggles with: building a business case for a data platform, and then making it come true.
What has been reported
In August, Computing, citing Financial Times reporting, set out the latest position (Computing). The National Infrastructure and Service Transformation Authority (NISTA) has raised its whole-life cost estimate to £1.1 billion, while forecast benefits have been reduced to £808 million. NISTA says the revised figures reflect a better understanding of performance, usage and adoption during rollout, and continues to rate the project green on delivery.
Other findings have added to the scrutiny. In July the Office for Statistics Regulation told NHS England to strengthen caveats on benefit claims, saying they risked confusing correlation with causation. The Health Foundation found "no noticeable improvement" in delayed discharge performance among trusts using one discharge tool built on the platform. Two parliamentary committees have urged ministers to consider a break clause in the contract in 2027. NHS England maintains that wider benefits will be realised as rollout continues.
Reasonable people disagree about what this all means. But several lessons apply to any organisation, public or private, planning a major data platform.
Lesson 1: Signing up is not adopting
A platform delivers nothing until people use it in their daily work. Programmes often measure progress by how many sites have "gone live" or "signed up". Those are activity measures. What matters is whether clinicians, operators or analysts actually change how they work.
Every data platform business case should define adoption in terms of real use, such as active users, decisions made using the platform and processes switched off, and report on it from the start.
Lesson 2: Benefits need a causal story
The statistics regulator's warning about correlation and causation is a lesson for every benefits case. If performance improves at sites using a new platform, was it the platform, or were those sites already improving, better resourced or more motivated to adopt?
Strong business cases set out, before rollout, how benefits will be measured and how they will be separated from everything else that is changing. That might mean comparison groups, staggered rollouts or clear baselines. Without that, benefit claims become arguments rather than evidence.
Lesson 3: Re-forecast early and openly
Costs going up and benefits coming down during delivery is common. What matters is that forecasts are updated as evidence arrives, as NISTA has done, and that decisions follow from them. A business case should be a living document, revisited at every major stage, not a one-off approval artefact.
Lesson 4: Design the exit before you need it
The prominence of the 2027 break clause shows why exit terms matter. For any strategic platform, organisations should know before signing how they would leave: who owns the data models, pipelines and products built on the platform, how data would be extracted, and what a migration would cost. Platforms that make leaving expensive also weaken your negotiating position every year you stay.
Open standards, documented data models and portable pipelines are the insurance policy.
Lesson 5: Trust is part of the benefits case
The programme has faced sustained public concern about privacy and data access, and NHS England apologised in August after admitting that an earlier Data Protection Impact Assessment had wrongly suggested only NHS staff could access identifiable data (Computing).
In health, and increasingly elsewhere, public and staff trust is not a communications task layered on afterwards. It directly affects adoption. Clear, accurate transparency about who can see what data, and why, belongs in the business case alongside the cost and benefit numbers.
What this means for your next data platform
Whether you run a hospital trust, a retail chain or a logistics network, the core questions are the same. What decisions will this platform change? How will we know it was the platform that changed them? How will we measure real adoption? How would we leave? And have we earned the trust of the people whose data it holds?
Answer those well and a data platform can transform how an organisation runs. Skip them and you risk paying for a platform that is technically live but practically unused.
At Vitalos we help Health & Care organisations and others build data platform business cases that survive contact with reality, and then engineer the platforms to deliver them. If you are planning a major data investment, let's talk. You may also find our briefing on preparing for the NHS single patient record useful.
Frequently asked questions
What is the NHS Federated Data Platform?
It is a national data platform programme that connects data across NHS trusts and integrated care boards to support operational uses such as elective recovery, discharge and care coordination.
How much does the NHS Federated Data Platform cost?
As reported in August 2026, NISTA's whole-life cost estimate is £1.1 billion, with forecast benefits of £808 million.
What makes a good data platform business case?
Clear adoption measures based on real use, a method for attributing benefits to the platform, regular honest re-forecasting, defined exit terms and a credible approach to data trust and transparency.