TRV-2026-1380Version 1 · Certified

Written 2026-10-14 22:03:02 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1380
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-14T22:03:02.566874Z
status: published
lens: p_space
sector: health
headline: Evaluation and Comparison of Large Language Models in Answering Frequently Asked Patient Questions on Glaucoma
dek: Prcis: ChatGPT-o1 and DeepSeek-R1 demonstrated similar performance in answering frequently asked patient questions. However, limitations in reliability and high reading levels underscore the need for greater oversight and refinement to improve their role in patient education.
Purpose: This study evaluated and compared the reliability and readability of responses generated by ChatGPT-o1 and DeepSeek-R1 to frequently asked patient questions (FAQs) on glaucoma. The findings aim to elucidate the utility of each mode…
gain_title: (none)
problem_title: ChatGPT-o1 and DeepSeek-R1 gave glaucoma patient answers with notable accuracy errors, including false claims about tunnel vision and unsubstantiated lifestyle advice, written at 8th-12th grade reading levels.
trace_subject: (none)
gain_reading: (none)
gain_evidence: (none)
problem_reading: ChatGPT-o1 and DeepSeek-R1 gave glaucoma patient answers with notable accuracy errors, including false claims about tunnel vision and unsubstantiated lifestyle advice, written at 8th-12th grade reading levels.
problem_evidence: falsely suggesting that glaucoma may cause tunnel vision | Responses generated by both models were presented at the 8th-12th grade reading level.
quick_read: Researchers took the first 10 glaucoma questions from Google's People Also Ask section and put them to two chatbots, ChatGPT-o1 and DeepSeek-R1. Two glaucoma specialists graded each answer on a 4-point reliability scale, and the top two Google webpages for the same queries were graded in the same way. Readability was measured with validated metrics.

Patients increasingly look for health information online, so errors or hard-to-read answers from chatbots could affect how well they understand a chronic eye disease. The authors call for oversight and refinement of these models. The study covers only 10 questions and two models, so how far the findings extend is unclear.
limitation: The study evaluated only the first 10 Google People Also Ask questions and two chatbot models, which limits how broadly the results apply.
tag: Evidence-backed problem
key_points: Median reliability scores were 2.3 for ChatGPT-o1 and 2.8 for DeepSeek-R1, with no significant difference (P=0.08). | Top Google webpages scored 2.3, similar to the chatbots (P=0.18). | Both chatbots struggled with foundational knowledge and lifestyle questions. | Chatbot responses were written at the 8th-12th grade reading level, above average U.S. adult literacy.
rundown: The questions covered foundational knowledge, treatment description, lifestyle, and prognosis. Each was entered into both models, and two glaucoma specialists independently graded the responses, where 1 meant excellent with no clarification needed and 4 meant unsatisfactory.

The chatbots made specific errors: they falsely suggested glaucoma may cause tunnel vision, and they offered unsubstantiated advice on chugging water, diet, and screen time.

The authors conclude that the two models performed comparably and that their reading levels exceed average U.S. adult literacy, which poses challenges for patient comprehension. They say rigorous oversight and targeted refinement are needed before these tools are relied on for patient education.
sources:
- peer_reviewed | Journal of Glaucoma | https://doi.org/10.1097/ijg.0000000000002794 | 2026-10-12
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
0ded77124b3cfa53113cb7efd3816bd13dbb00b3f6b1add04f8874180c89f66a
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1380 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.