TruaceTracing the truth around AITuesday, September 15, 2026
TRV-2026-1095Certified recordPeer-reviewed

Clinical usability of an explainable AI decision support tool and evaluation of multimodal models in NSCLC

Despite a decade in, immunotherapy (IO) treatment selection in non-small cell lung cancer (NSCLC) remains largely guided by subgroup analyses and imperfect programmed death ligand 1 (PD-L1) and clinical scores. To our knowledge, I 3 LUNG ( NCT05537922 ) is currently the largest international, real-world, multimodal, artificial intelligence (AI)-based study, enrolling 2,396 patients. We integrated real-world clinical and blood (CB) data, computed tomography (CT) images, digital pathology (DP), and genomics into m…

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

Current reading — gain

In NSCLC immunotherapy selection, CB-only AI models outperformed PD-L1 and clinical scores in the independent test set, and both expert and nonexpert physicians improved their predictions when using the explainable AI decision support tool.

Current reading — problem

AI model performance dropped in external validation to AUC 0.55-0.72, and multimodal integration did not show translated incremental benefit in TEST and EXVAL sets.

What this doesn’t fix

External generalizability is limited by performance drop in external validation and uncertain incremental benefit of multimodal fusion, which did not translate in TEST and EXVAL.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1095, v1: “Clinical usability of an explainable AI decision support tool and evaluation of multimodal models in NSCLC.” Truvace, 2026-09-15. /record/TRV-2026-1095 (accessed at citation time). sha256 439de0637552e79c

Calibration history

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

  1. Certifiedv1439de0637552

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