TRV-2026-2089Certified recordJournalism

New study reveals AI chatbots recognize unnecessary medical tests, but stumble where human doctors disagree

In an era where patients and clinicians increasingly turn to artificial intelligence for medical advice, a critical question emerges: Does AI know when not to test or treat? A new joint study from Ben-Gurion University of the Negev (BGU) and Clalit Health Services reveals that leading large language models (LLMs) successfully identify when medical interventions are redundant in the vast majority of cases, stumbling primarily in gray areas where medical consensus itself is divided.

Health · The Trace — both readings · certified 2026-10-21 · v1 · article view · machine-readable

Current reading — gain

In the study, leading language models correctly recognized redundant medical interventions in most cases, suggesting they can help spot low-value testing or treatment.

Current reading — problem

The models' errors clustered in ambiguous clinical situations where medical consensus is itself divided, so their guidance is least reliable in contested cases.

What this doesn’t fix

The models struggled mainly in gray areas where medical consensus is itself divided, so their reliability in contested clinical decisions remains unresolved.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2089, v1: “New study reveals AI chatbots recognize unnecessary medical tests, but stumble where human doctors disagree.” Truvace, 2026-10-21. /record/TRV-2026-2089 (accessed at citation time). sha256 0ecdd71b82cc2f51…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv10ecdd71b82cc…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-2089 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.