Typeost

Tech news in plain type

Latest / Policy

Policy

Should the NHS Loosen Its Reliance on Palantir for Patient Data?

A Labour MP argues that the NHS in England should end its Palantir contract next spring and move patient data control back to the health service.

According to a column in The Guardian, ministers in England face a decision by Christmas on whether to extend the NHS contract with the US software company Palantir. The deal, worth £330 million, covers running the federated data platform, a system meant to connect information across NHS England. The contract is due to end next March.

Writing in the paper, Ben Coleman, Labour MP for Chelsea and Fulham and a member of the health and social care committee, urges ministers not to extend it. He argues that the NHS should move to new suppliers that would give the health service full control over its technology and patient data. He says the committee recommended in June against an extension, citing public distrust of the company, contested claims about the platform's benefits, and the availability of other tools.

Coleman presents the issue as one of reversing a dependence that has built up over time. He acknowledges that the transition will not be easy but says the work should begin next spring. Because this is an opinion piece, its conclusions reflect the author's position rather than independent reporting.

The column does not set out the government's current stance on an extension, the expected cost of changing suppliers, or which replacement providers might be considered. Those questions remain open in the reporting so far.

Background

The federated data platform is part of a broader effort to make health information easier to share across NHS England's hospitals, community services and local organizations. Supporters of such systems argue that clinicians need a joined-up view of patients to reduce duplicated tests, speed up discharges and plan services. Critics often focus on who holds the data, who runs the software and how easily an organization can leave a supplier once a system is built around it.

That last concern has a name in procurement circles: vendor lock-in. When a public body relies on one company's proprietary software, switching providers can involve rewriting integrations, migrating large volumes of records and retraining staff. Contracts may limit what the buyer can do with the code or data, and the cost of exit can be high even when the original price looked reasonable. Governments in several countries have faced this problem with large technology projects and have responded by seeking open standards, shorter contract terms and clearer rights over data.

Health data is especially sensitive. In the United Kingdom, it falls under data protection law, and patients have a legitimate interest in knowing how their information is used, who can access it and whether it is ever processed outside the country. Debates about public trust in NHS data initiatives have run for years, and previous projects that sought to share records more widely have prompted strong public reaction. Any large platform therefore has to balance technical ambition with transparency, consent and accountability.

The question of foreign suppliers also arises. Many public agencies rely on large American technology firms because those companies offer mature tools and scale. Some policymakers see that reliance as a practical necessity, while others see it as a strategic risk that should be reduced over time.

Why it matters

The decision on this contract is about more than one supplier. It tests whether the NHS can build digital infrastructure that clinicians and patients trust, and whether the health service has the internal skills to run complex systems without depending on a single outside firm. If ministers extend the deal, they will need to explain how they will address concerns about trust and transparency. If they end it, the NHS will have to plan a transition that protects patient safety and keeps services running.

The debate also reflects a wider policy question across the public sector: who controls the data that governments collect, and on what terms. Decisions made now about contract length, data ownership and exit rights could shape how future digital projects are procured. For patients, the outcome may determine how their records are handled and who is accountable when something goes wrong. For the technology industry, it signals how seriously public bodies are willing to press for control over their systems. Even a narrow contract dispute can set expectations for other departments and suppliers.

What to watch

The first signal will be the government's response before Christmas. A clear statement on whether the contract will be extended, and on what terms, would indicate how seriously ministers are weighing the committee's concerns. Any published reasoning would also help the public understand the trade-offs.

Watch for details on a transition plan, including timelines, costs and how patient data would be moved safely. Independent scrutiny from parliamentary committees and data protection regulators will also matter. Finally, pay attention to whether alternative suppliers or in-house options are named, since that will show how realistic a move away from the current arrangement may be.

Viewpoints

Commentary from our columns: three angles on this story.

The Rulebook privacy, safety and regulation

The debate over this contract is ultimately about who is accountable for patient records, and that question deserves a direct answer before any renewal is signed. Health data carries some of the most personal information a person can have, and the rules that govern it should be clear to everyone involved. Patients should be able to ask who can see their information, where it is processed and what happens if something goes wrong. A contract that leaves those answers buried in technical terms makes that harder.

Coleman's call for full NHS control is a useful test for any renewal. Ministers should ask whether the contract includes clear data protection terms, audit rights, independent oversight and a practical exit path. If those safeguards cannot be demonstrated in plain language, the public has reason to remain skeptical. Trust is not a side issue here. It is a precondition for systems that depend on people sharing sensitive information honestly.

The Skeptic open questions and weak points

Before the NHS commits to either extending or ending this contract, it is worth asking what the evidence actually shows. The column says the benefits are contested, which is a reminder that a large platform can look impressive in a presentation and still fail to deliver measurable improvements for clinicians and patients. Officials should be able to explain what the platform does, what it has achieved and what remains unfinished, without relying on broad claims.

The argument for moving to new suppliers also needs a sharper test. Changing providers is not automatically an improvement. It can be expensive, slow and risky, and the replacement may carry its own weaknesses. The useful question is not simply whether Palantir is the right partner, but whether any option, including keeping the current arrangement, can be shown to serve patients better. Open questions about cost, performance and transition should be answered before the December decision, not after it.

The User what changes for people who use it

For most people, the most important question is simple: will the care they receive become more joined up and safer, and will their information be handled with care? A patient rarely sees the contract behind a hospital system. They notice whether a referral arrives on time, whether a doctor has the full history and whether a letter about their care is accurate. Any change in supplier should be judged by those everyday experiences.

For NHS staff, the practical effects could be even larger. Clinicians and administrators already juggle many systems, and a switch in platform would require training, testing and patience. A transition that is poorly planned could disrupt the very services it is meant to improve. That is why the next spring should be treated as a serious project, with clear communication to staff and the public about what will change, when and why.

More in Policy