Emerging evidence
Published recordHealthGood Space
More
Guideline Concordance, Information Quality, and Readability of Large Language Model Responses to Female Urethral Stricture Questions: A Comparative Cross-sectional Study
- Truvace record
- TRV-2026-3051raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Benchmark or lab evaluation
- Sources
- 1 sourcePeer-reviewed
- sha256
- de46c07cbe54…check it
Aim Large language models (LLMs) are increasingly employed to acquire medical information. However, their reliability in addressing rare and technically intricate conditions, such as female urethral stricture disease (FUSD), remains uncertain. This study evaluated the guideline concordance, information quality, reliability, and readability of responses generated by three widely accessible LLMs in response to clinical questions related to FUSD. Methods This comparative cross-sectional study was conducted in Janua…
The gain
In a January 2026 test of 30 guideline-based questions on female urethral stricture, three blinded urologists gave Gemini 3.0 a mean accuracy of 4.80 out of 5, the highest of three chatbots.
What this doesn’t fix
The study tested three chatbots on 30 questions in a single month, January 2026, and the authors advise that the output be verified against current clinical guidance before use in clinical or patient education.
Sources
1 on file- Medical Bulletin of Hasekidoi:10.4274/haseki.galenos.2026.93585
Cite this record
v1Truvace Impact Record TRV-2026-3051, v1: “Guideline Concordance, Information Quality, and Readability of Large Language Model Responses to Female Urethral Stricture Questions: A Comparative Cross-sectional Study.” Truvace, 2026-11-19. /record/TRV-2026-3051 (accessed on the day you copy it). sha256 de46c07cbe546194…
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-3051 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