NHS Trusts Turn Away Palantir's Patient Data Platform in Favor of Older Systems
Several English NHS trusts are rejecting Palantir's £330m federated data platform, saying existing systems perform as well or better, according to freedom of information responses.
The Guardian reports that a number of National Health Service organizations in England are declining to adopt Palantir's patient data technology. The findings come from freedom of information responses, which the paper says show that health leaders in many cases believe they can find alternatives that are as good as, or better than, the US company's platform.
According to the Guardian, the federated data platform, a £330m system run by the controversial American firm, has been credited by some health bodies with making waiting lists easier to manage and improving how surgeries are scheduled. Other trusts took a different path. The paper names Gateshead and Truro among organizations that have said they will not use the platform.
The report also describes trusts that tested the system and then went back to the tools they already used. One Suffolk trust is quoted in the report, though the summary available to this outlet does not include the full statement, so its complete position is not clear here.
The picture that emerges is mixed rather than uniformly negative. Some trusts report practical gains, while others conclude that the platform offers little beyond what they already have. The Guardian's exclusive frames the issue as a gap between national ambition and local judgment about what works.
Background
The federated data platform is part of a broader effort to connect information held across England's health service. The idea behind a federated approach is that patient records and operational data remain spread across many local organizations, while a shared software layer lets staff see and act on that information without everything being moved into one central store. Supporters argue this can speed up decisions on bed use, theatre scheduling and waiting lists, which are pressure points for hospitals that have struggled with backlogs for years.
Health data projects in the United Kingdom have a long and often difficult history. Earlier attempts to create large national records systems ran into concerns about cost, technical complexity and public trust, and some were scaled back or abandoned. Hospitals also tend to have a patchwork of older systems, many built at different times by different suppliers, which makes any new platform hard to introduce and harder to integrate.
Choosing a technology supplier for public health care involves more than comparing features. Procurement rules, contract length, data protection duties and the need to avoid dependence on a single vendor all shape decisions. Trusts are semi-independent bodies, which means national programs can encounter resistance when local leaders do not feel a tool meets their needs. Freedom of information requests are one way outside observers can see how these choices are being made, since they can reveal decisions that are not always announced publicly.
Concern about American technology firms holding sensitive public data is also a recurring theme in European debates. Questions about where data is stored, who can access it and how well it is protected tend to surface whenever a foreign provider is involved in health services. These concerns exist independently of whether any particular system performs well, and they shape how the public and policymakers judge such deals.
Why it matters
Patient data sits at the center of how a health service runs. Waiting lists, cancellations and surgery timetables all depend on accurate, timely information, so the tools used to manage them affect patients directly, even if most never see the software. When trusts decide a system does not add value, that judgment matters for patients who are waiting and for staff who must work with whatever is in place.
The story also highlights a tension in public procurement. National programs are often designed to create consistency, but local organizations must live with the results. If trusts that test a platform find existing systems equally capable, questions arise about whether a central mandate can be justified, and what evidence should be required before public money is spent on a single supplier.
There is a wider point about trust. Health data is among the most sensitive information people share, and any system that handles it must earn confidence from patients and clinicians alike. Disputes over vendors can therefore affect public faith in the broader program, regardless of the technical merits of a given product.
Finally, the report is a reminder of how much these decisions depend on transparency. Freedom of information responses allow reporting that might otherwise stay hidden, and they give the public a clearer view of what local organizations actually think.
What to watch
Watch for official responses from the bodies involved, including any statement that explains how the platform was assessed and why certain trusts decided against it. Clarity about the trial results would help readers judge the claims on both sides.
Look for whether national health authorities respond to the findings and whether they signal any change in how the platform is rolled out or required. Any move toward making adoption optional, or toward publishing performance comparisons, would be significant.
Pay attention to further freedom of information disclosures, which could show how many trusts have adopted the system, how many have declined it, and what they cite as their reasons.
Finally, watch for scrutiny of the contract terms and data protection arrangements, since questions about cost, vendor dependence and data handling tend to follow the platform wherever it is used.
Viewpoints
Commentary from our columns: three angles on this story.
The Skeptic open questions and weak points
The most important question in this story is not whether Palantir's platform works in some places. Several trusts say it does. The harder question is why so many others, after trying it, concluded that the systems they already had were just as good. When an organization that has tested a tool walks away, that deserves more than a shrug from the vendor or the program's backers.
Claims that a platform made waiting lists easier to manage are meaningful, but they need context. Easier compared to what, measured how, and over what period? A trust that reverted to older systems after a trial may have had a different set of problems, a different staffing picture, or different expectations. Without a clear, shared yardstick, both the praise and the rejections are hard to weigh.
There is also a pattern worth noticing. Large national technology rollouts often promise consistency and savings, yet local teams are the ones who live with the results every day. If the people closest to the work are unconvinced, the burden of proof falls on the program to show what it delivers beyond the promise. Readers should ask for the trial data, not just the verdicts.
The Rulebook privacy, safety and regulation
Patient records are about as sensitive as data gets, which is why any platform handling them deserves close scrutiny. This story raises questions that go beyond performance. Where the data lives, who can see it, how access is logged, and what happens if the contract ends are all matters that the public has a right to understand clearly, not as an afterthought.
Freedom of information responses are a useful tool here, because they show how decisions are being made behind closed doors. Trusts that decline a system are, in effect, making a judgment about risk as well as function. Their reasoning, where it is shared, should be read as part of the privacy conversation, not separate from it.
Regulators and oversight bodies should be asking the same questions. Public confidence in health data depends on being able to see the safeguards, not only to hear that they exist. Any move toward wider adoption should come with published, accessible information about protections, governance and accountability.
The Ledger the business angle
Public procurement of software is a business story as much as a technology one. A platform costing several hundred million pounds carries an obvious question: what is the return, and for whom? When trusts decide that existing systems are good enough, the financial logic of a central purchase starts to look less certain, and the cost of the contract becomes a more pressing subject.
Vendor dependence is another factor. Once a national health system builds its workflows around one supplier's platform, switching later becomes expensive and slow. That lock-in gives the provider leverage, which is one reason public bodies try to keep multiple options open. Trusts that resist adoption may be protecting that flexibility, even if it complicates the national picture.
The practical lesson for other public buyers is to insist on measured results before scaling up. Pilots should have clear success criteria, and comparisons with incumbent tools should be published. A contract is only good value if it delivers, and the evidence so far suggests that answer is still being argued over.