TRV-2026-2384Published recordPeer-reviewed

Large language model chatbots for patient-facing erectile dysfunction information: a cross-sectional evaluation of safety, accuracy, empathy, information quality and readability

Background: Generative artificial intelligence chatbots are increasingly used for health information, including sensitive conditions, such as erectile dysfunction (ED), but their safety and quality remain uncertain. To compare six large language model chatbot interfaces for ED information across safety, accuracy, empathy, information quality, source-related transparency, readability and response length. Methods: Thirty-eight standardized ED questions were submitted once to six chatbot interfaces, yielding 228 re…

Health · The Trace (a gain and a problem) · first published 2026-11-05 · v1 · read the full story · raw data (JSON)

The gain

In a test of six chatbot interfaces answering 38 erectile dysfunction questions, accuracy was generally high, with a median of 4.00 out of 5 for every interface.

The problem

In a test of six chatbot interfaces answering 38 erectile dysfunction questions, raters safety-flagged 26 of 228 responses (11.4%), and empathy, information quality and readability differed across the chatbots.

What this doesn’t fix

Each question was submitted only once to each chatbot interface, so the results capture a single response per question rather than repeated or varied answers.

Sources

Your take

What do you make of this one?

Cite this record

Truvace Impact Record TRV-2026-2384, v1: “Large language model chatbots for patient-facing erectile dysfunction information: a cross-sectional evaluation of safety, accuracy, empathy, information quality and readability.” Truvace, 2026-11-05. /record/TRV-2026-2384 (accessed on the day you copy it). sha256 1f7a0c4c6e1e1fe0…

Change history

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv11f7a0c4c6e1e…

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