TRV-2026-2372Certified recordPeer-reviewed

Evaluation of large language models for clinical decision support in renal cell carcinoma: a multidisciplinary Delphi study

Aim: Large language models (LLMs) may facilitate the interpretation of clinical guideline information, but their performance in renal cell carcinoma (RCC) remains insufficiently characterized. We evaluated agreement between a multidisciplinary expert panel and the responses generated by Claude, Gemini and ChatGPT to RCC guideline-based questions. Materials & methods: A multidisciplinary tumor board developed 25 clinical questions based on the 2025 European Association of Urology RCC guidelines. Guideline figures…

Health · The Trace — both readings · certified 2026-11-05 · v1 · article view · machine-readable

Current reading — gain

When given structured guideline summaries, Gemini won expert consensus agreement on 24 of 25 kidney cancer questions (96%), while Claude and ChatGPT each won it on 23 of 25 (92%).

Current reading — problem

Panelists found occasional factual inaccuracies, omitted options and limited clinical nuance, and responses that failed consensus mostly involved clinically uncertain or individualized scenarios.

What this doesn’t fix

The models answered only 25 questions from structured guideline summaries, so the results do not demonstrate independent clinical reasoning or real-world decision-making performance.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2372, v1: “Evaluation of large language models for clinical decision support in renal cell carcinoma: a multidisciplinary Delphi study.” Truvace, 2026-11-05. /record/TRV-2026-2372 (accessed at citation time). sha256 70a0250cf2217f6e…

Calibration history

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

  1. Certifiedv170a0250cf221…

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