TRV-2026-1394Certified recordPeer-reviewed

Reliable Detection, Unreliable Clinical Decision-making: Artificial Intelligence Models in Burn Assessment

Background: Multimodal artificial intelligence (AI) systems are increasingly used for visual interpretation tasks. Whether commercially available models can be applied to burn surgery, and to what extent, remains unclear. We evaluated a clinical chain from visual recognition (distinguishing burns from nonburned skin) to treatment decision-making (debridement versus immediate skin grafting), including accuracy, output consistency, and skin tone subgroup performance. Methods: Four multimodal large language models…

Health · The Trace — both readings · certified 2026-10-15 · v1 · article view · machine-readable

Current reading — gain

Four multimodal models distinguished burns from nonburned skin with 97.2%-100% accuracy, with equivalent performance across Fitzpatrick skin tone strata.

Current reading — problem

The same models gave unreliable treatment recommendations for burns (debridement versus immediate skin grafting), with accuracy of 24.8% to 72.8% and inconsistent outputs for identical images.

What this doesn’t fix

The study tested a small set of 50 cropped photographs and concluded that current applicability in burn surgery is limited, so results do not establish performance in real-world clinical decision-making.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1394, v1: “Reliable Detection, Unreliable Clinical Decision-making: Artificial Intelligence Models in Burn Assessment.” Truvace, 2026-10-15. /record/TRV-2026-1394 (accessed at citation time). sha256 758dba5df4034da7…

Calibration history

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

  1. Certifiedv1758dba5df403…

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