63/100

Moderate evidence

GainPublished recordHealthGood Space

Clinician Acceptance of Large Language Model–Generated Discharge Summaries

Truvace record
TRV-2026-3039raw data (JSON)
Version
v1Published
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
036768ed0f19…check it

Importance Hospital discharge summaries are essential for continuity of care, but fragmented electronic health record (EHR) data can compromise their quality and safety. Large language models (LLMs) are increasingly proposed for clinical documentation tasks despite limited evidence regarding their performance in health care settings compared with the current standard of care. Objective To evaluate clinician acceptability of LLM-generated discharge summaries derived from EHRs compared with routine clinician-writt…

The gain

In a retrospective study of 1,294 discharge summaries from 5 London hospitals, 12 physicians were 22.2 percentage points more likely to sign off GPT-4o mini summaries with no or minor edits than clinician-written ones.

What this doesn’t fix

The study was retrospective and reviewers judged summaries against records; the authors frame the finding as an early use case needing close clinician oversight.

Sources

1 on file
  1. JAMA Network Opendoi:10.1001/jamanetworkopen.2026.44496
    Peer-reviewed2026-11-17

Cite this record

v1

Truvace Impact Record TRV-2026-3039, v1: “Clinician Acceptance of Large Language Model–Generated Discharge Summaries.” Truvace, 2026-11-19. /record/TRV-2026-3039 (accessed on the day you copy it). sha256 036768ed0f192505…

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. Publishedv1036768ed0f19…

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