TRV-2026-1856Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1856 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-18T22:01:15.148487Z status: published lens: p_space sector: health headline: Readability, reliability, and quality of AI-Generated responses on pelvic congestion syndrome: A comparative analysis of ChatGPT, gemini, and perplexity dek: ObjectivePelvic congestion syndrome (PCS) is a vascular cause of chronic pelvic pain arising from ovarian and pelvic venous insufficiency, typically presenting as dull, aching pelvic pain that worsens with prolonged standing, physical activity, and the premenstrual period, and is particularly common among multiparous women of reproductive age. Online health information on this condition is frequently accessed by both patients and healthcare professionals. This study aimed to evaluate the readability, quality, an… gain_title: (none) problem_title: Responses from ChatGPT-4o, Gemini and Perplexity to common pelvic congestion syndrome questions were too complex for the recommended sixth-grade level, and overall quality scores were suboptimal. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: Responses from ChatGPT-4o, Gemini and Perplexity to common pelvic congestion syndrome questions were too complex for the recommended sixth-grade level, and overall quality scores were suboptimal. problem_evidence: all chatbot responses significantly exceeded the sixth-grade level recommended by the AMA and NIH | overall quality scores are suboptimal quick_read: Researchers took 18 commonly searched keywords on pelvic congestion syndrome, a vascular cause of chronic pelvic pain, and submitted them to ChatGPT-4o, Gemini and Perplexity. They then scored the responses with several readability, quality and reliability instruments. Patients and clinicians often look for health information online, so the readability and quality of chatbot answers affect how usable that information is. The authors describe chatbots as promising but found the content too complex and of suboptimal quality. The study covers only three freely accessible platforms and does not measure patient outcomes. limitation: The study evaluated only three freely accessible chatbots on 18 keyword queries, and the authors judge overall quality scores suboptimal, so the results do not show how patients actually use or are affected by the answers. tag: Evidence-backed problem key_points: All chatbot responses significantly exceeded the sixth-grade reading level recommended by the AMA and NIH (p < .001). | Perplexity produced the most complex responses but scored highest on JAMA, DISCERN and GQS. | Gemini scored best on EQIP and on most readability indices, while ChatGPT-4o did best on CLI and ARI. | The 18 keywords were derived from 25 Google Trends terms after removing duplicates and irrelevant ones. rundown: The study began with 25 PCS-related keywords from Google Trends. After duplicates and irrelevant terms were removed, 18 remained and were submitted separately to each of the three chatbots. Readability was calculated with indices including Gunning Fog, SMOG and Flesch Reading Ease, using two independent tools. Quality was measured with the Global Quality Score and the EQIP tool, and reliability with the JAMA benchmark criteria and modified DISCERN. Platform results differed by measure. ChatGPT-4o led on CLI and ARI readability, Gemini on the remaining readability indices, and Perplexity gave the most complex text yet led on several quality and reliability scores. The authors conclude that clearer, more balanced and more reliable content could improve these tools' contribution to public health. sources: - peer_reviewed | Phlebology: The Journal of Venous Disease | https://doi.org/10.1177/02683555261499766 | 2026-10-18 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 8f7e54599e2b528583380da1d4990a6c451ce3525175f2f94f745291a4de4655
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1856 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.
ace