TRV-2026-2384Version 1 · Published

Saved · see the current record

Why this version exists

Certified into the record

The exact text we saved

This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.

TRUVACE RECORD VERSION
record: TRV-2026-2384
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-11-05T18:01:46.862701Z
status: published
lens: trace
sector: health
headline: Large language model chatbots for patient-facing erectile dysfunction information: a cross-sectional evaluation of safety, accuracy, empathy, information quality and readability
dek: 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…
gain_title: 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.
problem_title: 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.
trace_subject: AI chatbot answers to erectile dysfunction questions
gain_reading: 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.
gain_evidence: Accuracy was generally high (median 4.00/5 for all interfaces)
problem_reading: 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.
problem_evidence: Twenty-six responses (11.4%) were safety-flagged.
quick_read: Researchers submitted 38 standardized erectile dysfunction questions once to each of six large language model chatbot interfaces, producing 228 responses. Five independent raters scored them, and 26 responses (11.4%) were safety-flagged.

Accuracy was generally high, with a median of 4.00 out of 5 for every interface, though scores differed slightly overall. Empathy, DISCERN, Ensuring Quality Information for Patients and Journal of the American Medical Association benchmark scores all differed significantly between chatbots, while Global Quality Score did not.

The authors conclude the chatbots may support information seeking but should not replace individualized clinical assessment. Safety-flag frequency differed across interfaces, but the effect size was small and no pairwise difference held after multiplicity correction.
limitation: 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.
tag: Dual reading
key_points: Thirty-eight standardized questions were each submitted once to six chatbot interfaces, yielding 228 responses. | Twenty-six responses (11.4%) were safety-flagged by the raters. | Safety-flag frequency differed across interfaces (P = 0.038) with a small effect size of 0.062, and no pairwise difference remained significant after correction. | Accuracy had a median of 4.00 out of 5 for all interfaces, with a slight overall difference (P = 0.010, Kendall's W = 0.080). | The JAMA benchmark showed the largest spread between chatbots (W = 0.888), followed by Ensuring Quality Information for Patients (W = 0.576) and DISCERN (W = 0.508). | Global Quality Score did not differ significantly across interfaces (P = 0.146). | Readability and response length differed between interfaces (all P < 0.001).
rundown: The study was a cross-sectional evaluation of six large language model chatbot interfaces answering patient-facing questions on erectile dysfunction, a sensitive condition for which people increasingly turn to generative AI. Each of 38 standardized questions was submitted once, giving 228 responses.

Five independent raters scored responses on Safety, Accuracy and Empathy, plus four information-quality tools: DISCERN, Ensuring Quality Information for Patients, the JAMA benchmark and Global Quality Score. Readability and response length were also measured, and differences between interfaces were tested with Cochran's Q or Friedman tests.

Results showed 11.4% of responses were safety-flagged. Differences in flag frequency across interfaces were statistically detectable (Q = 11.765, P = 0.038) but small, and none survived multiplicity correction in pairwise comparisons. Accuracy stayed high across interfaces, while empathy, source-related transparency and information quality scores varied more.

The authors conclude the chatbots generally gave accurate information and may help people seek it, but performance varied on clinically relevant dimensions and the tools should not replace individualized clinical assessment.
sources:
- peer_reviewed | Sexual Health | https://doi.org/10.1071/sh26186 | 2026-12-17
prev: 0000000000000000000000000000000000000000000000000000000000000000
SHA-256 hash
1f7a0c4c6e1e1fe074cbb2c2168749fe9f9cd16f81f4834ac1f9ce68635bdfb5
Previous version’s hash
0000000000000000000000000000000000000000000000000000000000000000
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.