55/100

Moderate evidence

ProblemPublished recordHealthProblem Space

Revealed: Palantir lobbied minister to stretch AI tools’ reach to NHS GP records

Truvace record
TRV-2026-2440raw data (JSON)
Version
v1Published
First published
Evidence type
Investigative reporting
Sources
1 sourceJournalism
sha256
0253fa393414…check it

Palantir lobbied a health minister to consider extending its AI technology into GP records, stretching its reach into the NHS in a way doctors fear could undermine trust with patients. The US company, co-founded by the Trump-supporting billionaire Peter Thiel, used a direct WhatsApp channel to argue that “the logic of joining up primary and secondary [care] data is unarguable” and said its software was “ideal” for the job. The push came in February this year despite GP data being expressly ruled out of scope of…

The problem

Messages released under freedom of information law show Palantir privately urged a health minister to extend its software to GP records that its £330m NHS England contract excludes, and doctors say this could damage patient trust.

What this doesn’t fix

The Palantir executive's name is redacted in the released documents, though Palantir did not deny it was Mosley, and Palantir says it is for the government to decide how the software is rolled out.

Sources

1 on file
  1. The Guardiantheguardian.com
    Journalism2026-11-09

Cite this record

v1

Truvace Impact Record TRV-2026-2440, v1: “Revealed: Palantir lobbied minister to stretch AI tools’ reach to NHS GP records.” Truvace, 2026-11-09. /record/TRV-2026-2440 (accessed on the day you copy it). sha256 0253fa3934146280…

Change history

1 version

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

  1. Publishedv10253fa393414…

    Certified into the record

Check this record hasn’t been altered

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

Download any version from /api/record/TRV-2026-2440 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.