TRV-2026-2288Certified recordPeer-reviewed

OpenEvidence versus Six Leading Large Language Models in Refractive Surgery: Does Curated Medical Evidence Confer an Advantage?

Purpose To assess the accuracy of OpenEvidence relative to six leading large language models (LLMs) in answering refractive surgery multiple-choice questions, and to compare their performance with users of the American Academy of Ophthalmology (AAO) Basic and Clinical Science Course (BCSC) Self-Assessment Program. Setting Not applicable. Design Randomized questionnaire-based study using 225 questions from the refractive surgery section of the AAO BCSC Program. Methods OpenEvidence and 6 LLMs (ChatGPT-4o, ChatGPT…

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

Current reading — problem

The medical-evidence tool OpenEvidence had the lowest accuracy (76%) on 225 refractive surgery questions, below six general-purpose chatbots and the human benchmark of ophthalmology trainees and users.

What this doesn’t fix

The authors state the task-specific result should not be interpreted as direct evidence of globally inferior medical knowledge or of performance in open-ended clinical applications.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2288, v1: “OpenEvidence versus Six Leading Large Language Models in Refractive Surgery: Does Curated Medical Evidence Confer an Advantage?.” Truvace, 2026-10-27. /record/TRV-2026-2288 (accessed at citation time). sha256 08f70fce384cda28…

Calibration history

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

  1. Certifiedv108f70fce384c…

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