Calibrated Triage, Not Autonomy: Confidence Estimation for Medical Vision-Language Models

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2606.15910v2 Announce Type: replace Abstract: A vision-language model can answer a question about a chest radiograph or a pathology slide fluently and confidently while barely using the image, relying instead on language priors. In medicine this is the failure that matters most: the answer looks trustworthy and is not, and the natural safeguard is a confidence score reliable enough to say when the model should abstain. We ask a deployment question rather than an accuracy one: how much medical imaging work a vision-language model can safely defer on its own, and which confidence signal makes that possible. We evaluate nine confidence estimators, spanning training-free logit baselines, prompt-based self-reports, and trained internal probes, across five open-weight LVLMs and three medical VQA datasets covering broad clinical imaging, radiology, and pathology, every probe trained only on natural images and applied to medicine without adaptation. Recast as bounded selective prediction, the comparison is cautionary. Standard metrics mislead: discrimination barely separates the estimators, and a fixed high-confidence cutoff separates them far less than it appears, because their scores sit on incomparable scales; no estimator is reliably best across domains or models. What can be safely deferred is set at two levels: base-model competence fixes a ceiling, and the confidence layer determines how much of it is reachable. At a 20% error tolerance the strongest estimator defers about a quarter of radiology cases under a distribution-free guarantee and a third under a held-out …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2606.15910
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.