Emerging evidence
Published recordHealthProblem Space
More
Hallucinated Evidence and Real-World Risk-Physicians' Intent to Act on AI-Generated Abstracts in Emergency Medicine and Trauma Surgery: Cross-Sectional, Vignette-Based Diagnostic Accuracy Study
- Truvace record
- TRV-2026-2904raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Survey
- Sources
- 1 sourcePeer-reviewed
- sha256
- d9ef7a7eb618…check it
Background: Large language models (LLMs) are increasingly used in academic writing and can generate linguistically polished but factually incorrect scientific content. Such misinformation may distort evidence appraisal and, if translated into clinical practice, compromise patient care. Objective: This study aimed to estimate physicians' likelihood of misperceiving false information embedded in LLM-generated abstracts as true and reporting an intent to use that information in future practice. We also explored whi…
The problem
In a vignette survey of 20 emergency and trauma physicians at 4 German hospitals, doctors said they would act on 57% (31/54) of the abstracts they chose to act on that were GPT-5-generated fakes, and rated true and false abstracts similarly for accuracy.
What this doesn’t fix
The study involved only 20 physicians from 4 hospitals in Germany, used vignettes, and measured reported intent to act rather than real clinical decisions.
Sources
1 on file- Journal of Medical Internet Researchdoi:10.2196/91095
Cite this record
v1Truvace Impact Record TRV-2026-2904, v1: “Hallucinated Evidence and Real-World Risk-Physicians' Intent to Act on AI-Generated Abstracts in Emergency Medicine and Trauma Surgery: Cross-Sectional, Vignette-Based Diagnostic Accuracy Study.” Truvace, 2026-11-14. /record/TRV-2026-2904 (accessed on the day you copy it). sha256 d9ef7a7eb618f8e5…
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-2904 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