The Palantir Federated Data Platform is a data analytics and visualization system deployed across NHS organisations in England, designed to join up patient care and accelerate diagnosis. Yet NHS staff who use it daily are calling it overpriced, poorly designed, and inferior to the systems it is meant to replace. With MPs, trade unions, and patient advocacy groups now pushing for the contract to end early, Palantir’s position in the NHS is becoming untenable.
Key Takeaways
- NHS staff describe the Palantir Federated Data Platform as “not very good” and “awful to use” for data querying and analytics.
- 150 NHS organisations are already live on the platform; 50+ more are set to start soon.
- The initial contract is worth £330 million over three years, expiring February 2027.
- A coalition of healthcare, union, and patient rights groups urges NHS organisations to resist rollout and prioritise open-source alternatives.
- NHS England expects full adoption across all providers and ICBs by 2028/29.
Why NHS Staff Reject the Palantir Federated Data Platform
The core complaint is blunt: the Palantir Federated Data Platform does not work as well as the software it is replacing. According to NHS staff who have used both systems, the platform’s functionality for data querying, pipelining, analytics, and visualisation is significantly weaker than existing NHS solutions. One NHS staff member described it as “really a very overpriced data warehouse,” producing outputs that fall short of what clinicians and managers expect. The user interface itself is another flashpoint—staff report it is “not pleasant” to navigate, and accessibility features for visual impairments and mobile compatibility are missing.
What makes this worse is that hospitals and GP surgeries are being pressured from above to adopt the platform. Trusts and Integrated Care Boards (ICBs) are mandating rollout, a pattern NHS staff call “mission creep.” Teams are losing access to familiar, functional tools and being forced onto a system many view as a step backward. This is not a gradual, voluntary migration—it is a top-down mandate that is creating friction at every level.
Political and Union Pressure Threatens the Palantir Federated Data Platform Contract
The backlash has moved beyond staff complaints into formal political opposition. A coalition including Medact (a health union), patient advocacy groups, and consumer rights organisations has issued a direct call for NHS hospitals, Trusts, ICBs, and Health Scrutiny Committees to resist the Palantir Federated Data Platform rollout entirely. They are urging organisations to refuse implementation and instead prioritise in-house and open-source alternatives. This is not a marginal critique—it represents a coordinated push from unions, clinicians, and patient advocates to block what NHS England sees as a strategic priority.
The timing is significant. The UK government is requiring hospitals to sign a memorandum of understanding for Palantir Federated Data Platform elements starting next month, formalising the rollout commitment. At the same time, regional systems like Greater Manchester’s existing data-sharing infrastructure are resisting dismantling their pre-existing solutions in favour of the Palantir platform. These local systems work, staff know them, and there is no appetite to replace them with something staff describe as inferior.
The Contract Timeline and Palantir Federated Data Platform Expansion
The Palantir Federated Data Platform contract is worth £330 million for the initial three years, with the agreement expiring in February 2027. This gives NHS England a decision point—extend the contract or terminate it. Currently, 150 NHS organisations are live on the platform, with 50 or more set to begin implementation in coming months. NHS England is pushing for universal adoption across all providers and ICBs by 2028/29, which would lock the platform in place before the contract review date arrives.
This expansion strategy may backfire. The more organisations that are forced onto a system staff already dislike, the louder the resistance becomes. Every hospital that goes live and discovers the platform underperforms adds another voice to the chorus calling for alternatives. By the time February 2027 arrives, NHS England may face a choice between defending an unpopular system or admitting the rollout was a mistake.
Palantir’s Claims vs. Staff Reality
Palantir and NHS England claim the Palantir Federated Data Platform is delivering transformative benefits: joining up care, speeding cancer diagnosis, and treating thousands of additional patients each month. Palantir specifically highlights claims of 100,000 additional operations, a 12% reduction in discharge delays, and 675,000 patients removed from waiting lists. Yet these figures are unattributed promotional claims with no independent verification, and they sit in sharp contrast to staff reports of a system that is difficult to use and produces inferior outputs.
This credibility gap is the real problem. When frontline staff say a system is “awful to use” and produces worse results than what it replaced, and leadership simultaneously claims it is delivering massive clinical benefits, one side is not telling the truth. Staff have no reason to lie—they are the ones struggling with the interface daily. The claims of transformed outcomes, by contrast, come from the organisations promoting the contract and the vendor itself.
Open-source and in-house alternatives remain viable
The coalition pushing back against the Palantir Federated Data Platform explicitly recommends that NHS organisations prioritise in-house development and open-source software as first options for data solutions. This is not a call for the NHS to abandon data analytics—it is a call to build or adopt systems that NHS staff actually want to use, that integrate with existing workflows, and that do not impose a commercial vendor’s design choices on clinicians and managers.
Several NHS regions already have functional data-sharing systems in place. Rather than dismantling these and forcing adoption of a platform staff describe as inferior, the recommendation is to strengthen what works locally. This approach is cheaper, faster, and avoids the mission creep that comes with a national mandate from a single vendor.
Will the Palantir Federated Data Platform survive to 2027?
The contract expires in February 2027, giving NHS England roughly two years to decide whether to extend. If the current trajectory of staff complaints, union opposition, and regional resistance continues, the political cost of renewal will be substantial. NHS leadership may find it easier to walk away than to defend a system that frontline staff actively dislike. The question is not whether the Palantir Federated Data Platform is good—staff have already answered that. The question is whether NHS England will listen.
What makes the Palantir Federated Data Platform different from NHS legacy systems?
The Palantir Federated Data Platform is a centralised, commercial data analytics platform designed to standardise data across the entire NHS. Existing NHS solutions are often fragmented, locally managed systems that evolved to fit specific hospital or trust workflows. The Palantir approach promises interoperability and scale; the legacy systems offer familiarity and staff comfort. Staff are reporting that the trade-off—losing a system they know for one that is harder to use—is not worth the promised benefits.
Can NHS organisations opt out of the Palantir Federated Data Platform?
Technically, individual NHS organisations can resist or delay adoption, as Greater Manchester has done. However, NHS England is mandating rollout via memoranda of understanding, and the expectation is that all providers will be on the platform by 2028/29. Opting out requires either refusing to sign the MoU or explicitly pushing back against regional ICB pressure—a politically costly move for trust leadership.
What happens if the Palantir Federated Data Platform contract is not renewed in 2027?
If NHS England chooses not to extend the contract in February 2027, the platform would need to be decommissioned or replaced. This would require migration of data and workflows back to existing systems or to alternative platforms. The cost and disruption would be significant, which is why early termination is unlikely unless political pressure becomes overwhelming. However, if staff resistance continues to mount and public scrutiny increases, the reputational cost of renewal could exceed the cost of exit.
The Palantir Federated Data Platform is now at a crossroads. Staff have rejected it, unions are organising against it, and MPs are questioning the contract. NHS England is committed to rolling it out, but the momentum is shifting. By 2027, when the contract comes up for renewal, the political landscape may look very different from today.
This article was written with AI assistance and editorially reviewed.
Source: TechRadar
