TruaceTracing the truth around AIMonday, September 14, 2026
TRV-2026-1088Certified recordPeer-reviewed

Comprehension of an AI-generated discharge letter versus a traditional discharge letter: two controlled quasi-experimental parallel-group studies

Background Discharge letters are essential for continuity of care, yet patients often misunderstand their content. Poor discharge communication is associated with medication errors, inappropriate healthcare use, and hospital readmissions. Artificial intelligence (AI) language models may improve discharge documentation clarity and accessibility. This study aimed to compare a GPT-4-generated, accessibility-optimised discharge letter with a conventional discharge letter regarding comprehension of key discharge info…

Health · G Space — documented gain · certified 2026-09-14 · v1 · article view · machine-readable

Current reading — gain

GPT-4-generated, accessibility-optimised discharge letters increased comprehension of diagnosis, treatment, investigations and follow-up compared with conventional letters.

What this doesn’t fix

Findings were based on simulated letters and specific samples, requiring further validation with real clinical letters and more diverse patients.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1088, v1: “Comprehension of an AI-generated discharge letter versus a traditional discharge letter: two controlled quasi-experimental parallel-group studies.” Truvace, 2026-09-14. /record/TRV-2026-1088 (accessed at citation time). sha256 c1a1721ddfcdd875

Calibration history

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

  1. Certifiedv1c1a1721ddfcd

    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-1088 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.