TRV-2026-1856Certified recordPeer-reviewed

Readability, reliability, and quality of AI-Generated responses on pelvic congestion syndrome: A comparative analysis of ChatGPT, gemini, and perplexity

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…

Health · Problem Space — documented harm · certified 2026-10-18 · v1 · article view · machine-readable

Current reading — problem

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.

What this doesn’t fix

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.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1856, v1: “Readability, reliability, and quality of AI-Generated responses on pelvic congestion syndrome: A comparative analysis of ChatGPT, gemini, and perplexity.” Truvace, 2026-10-18. /record/TRV-2026-1856 (accessed at citation time). sha256 8f7e54599e2b5285…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv18f7e54599e2b…

    Certified into the record

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.