TRV-2026-2304Version 1 · Certified

Written 2026-10-29 06:45:50 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-2304
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-29T06:45:50.078746Z
status: published
lens: p_space
sector: health
headline: Performance of Large Language Models in Image-Based Evaluation of Dupuytren Contracture
dek: Background Artificial intelligence (AI) has been utilized as a supplemental tool by patients and providers in the evaluation of common hand pathology. This study evaluated the ability of 3 large language model (LLM)-based AI systems (ChatGPT, Gemini, and Claude) to characterize Dupuytren's contracture involvement and recommend treatment based solely on patient images. Methods A heterogeneous set of publicly available images was obtained from open-access databases and literature sources. Images were evaluated by…
gain_title: (none)
problem_title: Three AI chatbots characterized Dupuytren's contracture from photos with limited accuracy, and their treatment recommendations agreed with hand surgeons no more than chance would.
trace_subject: (none)
gain_reading: (none)
gain_evidence: (none)
problem_reading: Three AI chatbots characterized Dupuytren's contracture from photos with limited accuracy, and their treatment recommendations agreed with hand surgeons no more than chance would.
problem_evidence: Large language models demonstrated limited accuracy in characterizing Dupuytren's contracture involvement from patient images. | agreement with surgeons was no greater than chance
quick_read: Researchers gave images of Dupuytren's contracture, a hand condition, to three AI chatbots: ChatGPT, Gemini and Claude. Each model worked in an independent session with a standardized prompt and was asked to describe the contracture and recommend treatment. Their answers were checked against the consensus of three board-certified hand surgeons.

The results suggest that patients who upload a photo to a chatbot may receive unreliable guidance about this hand condition. The authors say it is not yet known whether adding standardized clinical information would make the recommendations more dependable, so the study does not show how chatbots perform in realistic care settings.
limitation: The assessment relied on single images alone, and the authors say further research is needed to determine whether adding standardized clinical information could improve reliability.
tag: Evidence-backed problem
key_points: The chatbots tested were ChatGPT, Gemini and Claude. | Images came from open-access databases and literature sources rather than real patients seen in clinic. | Treatment recommendations were often within one ordinal tier of surgeon consensus. | Agreement with surgeons was no greater than chance, and no consistent differences appeared among the models.
rundown: The study used a heterogeneous set of publicly available images from open-access databases and literature. Each image was evaluated in an independent stateless session with a standardized prompt, so earlier answers could not influence later ones.

Model outputs were compared with consensus assessments from three board-certified hand surgeons. The models were weak at characterizing the extent of contracture involvement, and their treatment suggestions were often close to the surgeons' tier but did not agree beyond chance.

The authors describe a gap between current model performance and surgeon consensus when judging from single patient-submitted images, and call for further research on whether adding clinical information would improve reliability.
sources:
- peer_reviewed | HAND | https://doi.org/10.1177/15589447261495085 | 2026-10-27
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
6bca88aa6f94c1c6916d2b15ff99198a8fade2c850b1f2359f3969a63cba18f5
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

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