TRV-2026-2427Published recordPeer-reviewed

Patient-Friendly Simplifications of Outpatient Reports Using Large Language Models via Few-Shot Prompting: Blinded Comparative Evaluation

Background: Effective communication between clinicians and patients plays an important role in the successful delivery of health care. In geriatric medicine, where multimorbidity, polypharmacy, and functional limitations often make treatment plans complex, AI simplifications of clinical reports into patient-friendly language offer a promising way to improve communication. Objective: This study investigated whether AI could generate patient-friendly simplifications of outpatient reports that were comparable to th…

Health · The Trace (a gain and a problem) · first published 2026-11-08 · v1 · read the full story · raw data (JSON)

The gain

In a blinded evaluation of 64 German geriatric outpatient reports, patient representatives (P<.001) and one expert reviewer (P=.001) preferred Gemma-3 simplifications over those written by geriatricians.

The problem

In the same study, expert reviewers rated physician-written simplifications as more complete than the AI versions (P<.001), a gap that tracked with text length.

What this doesn’t fix

The study measured perceived comprehension and preference, not objective health outcomes, adherence or patient engagement, which the authors say prospective studies must still examine.

Sources

Your take

What do you make of this one?

Cite this record

Truvace Impact Record TRV-2026-2427, v1: “Patient-Friendly Simplifications of Outpatient Reports Using Large Language Models via Few-Shot Prompting: Blinded Comparative Evaluation.” Truvace, 2026-11-08. /record/TRV-2026-2427 (accessed on the day you copy it). sha256 0855a15551e27d7c…

Change history

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

  1. Publishedv10855a15551e2…

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