TRV-2026-1487Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1487 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-15T22:01:23.493248Z status: published lens: p_space sector: health headline: Cognition, oversight, and the safety case for documentation AI dek: Large language models (LLMs) can now draft hospital discharge summaries. Reported hallucination rates vary by measurement context, from about 1%-2% in structured summarisation to over 60% under provocation testing. The common argument that LLMs outperform a tired resident treats a high-stakes clinical and legal document as a text-quality problem. We argue that a potentially underappreciated concern is the weakening of clinician oversight when reviewing fluent machine-generated text, and that the joint clinician-… gain_title: (none) problem_title: When clinicians review fluent machine-generated discharge summaries, their oversight may weaken, and hallucination rates range from about 1%-2% in structured summarisation to over 60% under provocation testing. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: When clinicians review fluent machine-generated discharge summaries, their oversight may weaken, and hallucination rates range from about 1%-2% in structured summarisation to over 60% under provocation testing. problem_evidence: a potentially underappreciated concern is the weakening of clinician oversight when reviewing fluent machine-generated text | Reported hallucination rates vary by measurement context, from about 1%-2% in structured summarisation to over 60% under provocation testing quick_read: A journal article examines the use of large language models to draft hospital discharge summaries. It notes that reported hallucination rates differ widely by how they are measured, from roughly 1%-2% in structured summarisation to above 60% when models are deliberately provoked. The authors argue that the safety question is not only text quality, because a discharge summary is a high-stakes clinical and legal document. Their concern is that fluent output may weaken clinician oversight, so safety depends on the joint clinician-AI system. The proposed oversight model is a framework, and the excerpt gives no outcome data showing it works. limitation: The authors describe the oversight weakening as a potentially underappreciated concern, and the excerpt gives no empirical evidence that the proposed safeguards work. tag: Evidence-backed problem key_points: LLMs can now draft hospital discharge summaries, according to the article. | Hallucination rates range from about 1%-2% in structured summarisation to over 60% under provocation testing. | The authors say that arguing LLMs outperform a tired resident treats a high-stakes clinical and legal document as only a text-quality problem. | They propose a Clinician-AI Oversight Model with four safeguards. rundown: The article challenges the common claim that LLMs outperform a tired resident. It says this framing reduces a high-stakes clinical and legal document to a question of text quality. Its central worry is a cognitive one: reviewing fluent machine-generated text may weaken clinician oversight. The authors therefore treat the joint clinician-AI system as central to safety rather than the model alone. The proposed Clinician-AI Oversight Model has four safeguards: bounded autonomy, structured verification, error-signal monitoring, and longitudinal evaluation of cognitive effects. sources: - peer_reviewed | Journal of Hospital Medicine | https://doi.org/10.1002/jhm.70513 | 2026-10-15 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- e4d163aad6a7ebb656c28f0fc8a642cfd92a70d704e3b83433819844275f3abd
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1487 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.
ace