JupiteX Get the app
Politics & Governance21 Nov 2026 · about 7 min

Will replacing Palantir solve the NHS’s fragmented governance problem?

The brief

The NHS Federated Data Platform, or FDP, is a network of connected platforms rather than a single system. It was designed to let NHS trusts and integrated care boards operate local instances, alongside a national instance run by NHS England. That structure matters because data stays local by design, with responsibility and control held by the relevant data controllers. Palantir is the supplier involved in the FDP contract. The article frames the government’s possible use of a break clause in February 2027 as a point when Palantir could leave and a replacement supplier could take over. The Department of Health and Social Care has confirmed the contract will be reviewed before that clause. The platform is already operating across a substantial network: by the end of May 2026, 139 trusts and 35 integrated care boards were live on it. The article argues that replacing Palantir would not remove the local data controllers, legacy systems or technical dependencies. Any future platform should also demonstrate ongoing visibility and accountability across the wider NHS estate.

01

What is the NHS Federated Data Platform, and what role does Palantir play in it?

The NHS Federated Data Platform, or FDP, is a network of connected platforms rather than a single system. It was designed to let NHS trusts and integrated care boards operate local instances, alongside a national instance run by NHS England. That structure matters because data stays local by design, with responsibility and control held by the relevant data controllers.

Palantir is the supplier involved in the FDP contract. The article frames the government’s possible use of a break clause in February 2027 as a point when Palantir could leave and a replacement supplier could take over. The Department of Health and Social Care has confirmed the contract will be reviewed before that clause.

The platform is already operating across a substantial network: by the end of May 2026, 139 trusts and 35 integrated care boards were live on it. The article argues that replacing Palantir would not remove the local data controllers, legacy systems or technical dependencies. Any future platform should also demonstrate ongoing visibility and accountability across the wider NHS estate.

02

How do the platform’s projected lifetime costs compare with its projected benefits?

The latest projected lifetime cost of the Federated Data Platform is £1.1 billion. Its projected benefits are £808 million. That comparison matters because it places the estimated cost above the estimated benefits, sharpening questions about whether the programme’s business case offers value for money.

The National Infrastructure and Service Transformation Authority revised the programme’s projected lifetime cost. The article reports both figures but does not give a breakdown of what makes up the cost or how the projected benefits were calculated. It says the widening gap between costs and benefits has intensified scrutiny of the business case.

The figures are part of the context for reviewing the contract with Palantir, not proof that a supplier change would resolve the concern. The Department of Health and Social Care has confirmed a review before the break clause. The article argues that any decision should consider value and supplier dependency, while also addressing governance across the connected NHS estate.

03

Why is the NHS reviewing the Palantir contract before its break clause?

The NHS is reviewing the Palantir contract because the programme’s financial case is under scrutiny and broader questions remain about the supplier relationship. The National Infrastructure and Service Transformation Authority revised the FDP’s projected lifetime cost to £1.1 billion, while projected benefits stand at £808 million. The Department of Health and Social Care has confirmed the contract will be reviewed before its break clause.

The review is not limited to the difference between those figures. The article says concerns about value, sovereignty and supplier dependency deserve serious attention. In its opening scenario, the government could trigger the break clause in February 2027, bring in a new supplier and begin migration. That would change who supplies the platform, but it would not itself change the NHS’s wider technical estate.

The article therefore separates the contract decision from the underlying governance problem. It argues that local data controllers, legacy systems and technical dependencies would remain after a supplier change. The review is a chance to assess the contract, but future platforms should also prove they can support ongoing visibility and accountability across the estate.

04

If the NHS chose a new supplier, what would change—and what underlying problems would remain?

If the NHS chose a new supplier, the immediate change would be who provides the platform and how the migration is carried out. The article imagines a break clause in February 2027, followed by Palantir leaving and a replacement supplier arriving. But a different supplier would not automatically make the NHS’s wider systems or governance simpler.

The FDP is a federation of local and national instances, not a single platform isolated from the rest of the health service. Trusts and integrated care boards remain data controllers, and the article says legacy systems and technical dependencies would remain too. It notes that staff still move between multiple systems to complete one task, while data sharing between organizations is inconsistent.

That is why the article calls the deeper issue a governance problem. Existing assurance processes were designed for a more static technology environment, while connections and risks need continuous attention. By the end of May 2026, 139 trusts and 35 integrated care boards were live on the FDP. Any replacement should therefore be judged on visibility and accountability across the wider estate, not only price or supplier location.

05

How does a federated data platform connect organizations while leaving data control with local bodies?

A federated data platform connects organizations through linked local and national systems rather than placing everything in one centrally controlled platform. In the NHS design, trusts and integrated care boards operate local instances, while NHS England operates the national instance. The model is intended to keep data local by design.

That arrangement leaves responsibility and control with the relevant data controllers at each level. It can strengthen accountability because local organizations retain ownership of their data and decisions about it. The connection between instances still creates dependencies, however. Those links must be mapped, risk-assessed and managed across systems and organizations.

The scale makes that ongoing work important. By the end of May 2026, 139 trusts and 35 integrated care boards were live on the FDP. The article says this is a network of local and national instances, not one platform or one supplier. Its central challenge is to maintain clear accountability and visibility across that network as systems and connections evolve.

06

How do legacy systems and technical dependencies make it harder to share data safely across the NHS?

The NHS’s technology estate was already complex before the FDP. The article says three-quarters of providers have identified investments needed to address technical debt. Staff still move between multiple systems to complete a single task, and data sharing across organizational boundaries remains inconsistent. These conditions make it harder to understand how information moves and which systems rely on one another.

A federation adds connections across local and national instances, so technical dependencies must be continuously mapped, risk-assessed and managed. When systems are old or fragmented, those links can be harder to see and coordinate. The article does not say that every dependency causes a security incident; its point is that the network creates ongoing work for governance and assurance.

Changing the FDP supplier would leave the legacy systems and dependencies in place. Existing NHS safeguards include the Data Security and Protection Toolkit, the Cyber Assessment Framework, impact assessments and named governance roles. But the article says many mechanisms assume a point-in-time assessment remains reliable, an assumption challenged by a changing technology estate.

07

Why can AI agents be harder to govern than fixed software when their access and actions can change over time?

Fixed software can be assessed at a particular point, but AI systems and agents may connect to applications, datasets and third parties, and their access or behavior can change at runtime. That makes governance harder because the risk is not confined to the AI tool itself. Security teams need to know who owns each system and what it is permitted to reach and do.

For example, an agent’s permissions or connected data may change after an assessment. The article says periodic reviews cannot by themselves govern an agent whose access or behavior changes at runtime. Teams need to reassess risk when models, data or permissions change, and to establish quickly what the system could access, what changed and who is accountable.

This is already relevant across the FDP network. By the end of May 2026, 139 trusts and 35 integrated care boards were live. The article calls for an inventory of AI systems, owners, data sources and approvals, along with real-time evidence and audit trails. It also recommends controls suited to each use case and monitoring for drift and bias.

This brief was written by AI from the original reporting and checked by other models. Names, figures and quotes come from the source; read it for full context.

Read more in the JupiteX app

Pulse is free. New stories every 4 hours, each one broken into the questions that explain it.

Or read more news on the web