TRV-2026-1830Certified recordPeer-reviewed

A focused PubMed artificial intelligence search program creates better literature reviews than general purpose artificial intelligence and is comparable to trainees in shoulder and elbow surgery

Background: As the use of artificial intelligence (AI) expands into orthopedic surgery, the potential to use AI for review and summation of literature leaves researchers and clinicians questioning the quality of AI-driven literature reviews. This study aims to compare AI-generated literature reviews to those done by orthopedic surgery trainees. Methods: ChatGPT-4o and The-Literature, a directed AI platform, were asked to produce a literature review on 5 shoulder and elbow-related research topics. The primary out…

Science · The Trace — both readings · certified 2026-10-18 · v1 · article view · machine-readable

Current reading — gain

A directed AI search platform produced shoulder and elbow literature reviews rated comparably to orthopedic trainees and better than a general-purpose chatbot.

Current reading — problem

A general-purpose large language model produced weaker reviews, with most of its cited references fabricated.

What this doesn’t fix

The comparison rests on five topics, a small number of human reviewers, and two graders, and tested ChatGPT-4 rather than other models, which limits generalization.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1830, v1: “A focused PubMed artificial intelligence search program creates better literature reviews than general purpose artificial intelligence and is comparable to trainees in shoulder and elbow surgery.” Truvace, 2026-10-18. /record/TRV-2026-1830 (accessed at citation time). sha256 04cb82f48f171c60…

Calibration history

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

  1. Certifiedv104cb82f48f17…

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