TRV-2026-2394Published recordJournalism

UK government to extend controversial Palantir NHS contract as it draws up plan for British alternative – UK politics live

Palantir’s controversial £330m health contract is to be extended before ministers draw up plans to replace it with a British alternative, the FT has reported. Health secretary Yvette Cooper has faced calls from MPs and campaigners to axe the US tech firm’s contract to deliver the flagship government AI system. The system aims to connect scattered medical files, speed up hospital discharges and improve surgery scheduling among other potentially life-saving improvements. But a review has concluded that removing Pa…

Labor · Problem Space (a documented problem) · first published 2026-11-06 · v1 · read the full story · raw data (JSON)

The problem

The government plans to keep Palantir's £330m NHS AI system running despite calls from MPs and campaigners to axe it, while NHS staff contest evidence of patient benefit and many trusts have rejected the platform.

What this doesn’t fix

The extension and replacement plan comes from an FT report relayed by the Guardian, and the plan is only expected to be signed off soon, so details and timing are not final.

Sources

Your take

What do you make of this one?

Cite this record

Truvace Impact Record TRV-2026-2394, v1: “UK government to extend controversial Palantir NHS contract as it draws up plan for British alternative – UK politics live.” Truvace, 2026-11-06. /record/TRV-2026-2394 (accessed on the day you copy it). sha256 edc98c05257a1789…

Change history

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1edc98c05257a…

    Certified into the record

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2394 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.