Moderate evidence
Published recordHealthGood Space
More
Large Language Model-Assisted Discharge Instructions for Diabetic Kidney Disease: Comparative Evaluation Study
- Truvace record
- TRV-2026-2908raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 6279bb4d790a…check it
Background: Discharge instructions are an important component of the transition from hospital to home for patients with diabetic kidney disease (DKD), whose care often involves multiple comorbidities, medications, and stage-specific management needs. However, producing complete, accurate, clear, and personalized instructions can be challenging for junior physicians. Objective: This study aimed to evaluate whether large language model (LLM) assistance improves the quality of DKD discharge instructions produced by…
The gain
In a comparative study of 101 hospitalized diabetic kidney disease patients, four clinical experts rated discharge instructions written by junior residents with DeepSeek-V3.2 higher than resident-only versions on all five dimensions, with 100 of 101 cases improving by at least one point overall.
What this doesn’t fix
The comparison used two separate groups of residents who wrote instructions for the same 101 patients, rather than the same residents with and without AI, and quality was scored by four experts rather than measured in patient outcomes.
Sources
1 on file- JMIR Medical Informaticsdoi:10.2196/100792
Cite this record
v1Truvace Impact Record TRV-2026-2908, v1: “Large Language Model-Assisted Discharge Instructions for Diabetic Kidney Disease: Comparative Evaluation Study.” Truvace, 2026-11-14. /record/TRV-2026-2908 (accessed on the day you copy it). sha256 6279bb4d790a989c…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
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-2908 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.
ace