Emerging evidence
Published recordHealthProblem Space
More
Quality, readability, and potential safety risks of epididymitis information generated by six artificial intelligence chatbots: a cross-sectional comparative study
- Truvace record
- TRV-2026-2932raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Benchmark or lab evaluation
- Sources
- 1 sourcePeer-reviewed
- sha256
- 52a442c80856…check it
Background AI chatbots are increasingly used for medical information, but the quality, readability, and safety of disease-specific responses remain uncertain. We compared epididymitis information generated by six widely accessible AI chatbots. Methods Nine of 25 Google Trends queries identified worldwide from August 2021 to August 2026 were each submitted once to ChatGPT, Gemini, Perplexity, Copilot, Kimi, and DeepSeek. Responses were assessed with DISCERN, EQIP, JAMA, GQS, and six readability indices. Between-m…
The problem
In a cross-sectional test of six AI chatbots answering nine epididymitis queries (54 responses), 4 responses (7.4%) contained potentially harmful information, all on antimicrobial recommendations, and none met sixth-grade readability benchmarks.
What this doesn’t fix
The authors describe the work as an exploratory cross-sectional snapshot, with each of nine queries submitted once per chatbot and potentially harmful misinformation assessed exploratorily.
Sources
1 on file- Frontiers in Medicinedoi:10.3389/fmed.2026.1991323
Cite this record
v1Truvace Impact Record TRV-2026-2932, v1: “Quality, readability, and potential safety risks of epididymitis information generated by six artificial intelligence chatbots: a cross-sectional comparative study.” Truvace, 2026-11-15. /record/TRV-2026-2932 (accessed on the day you copy it). sha256 52a442c80856f803…
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-2932 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