TruaceTracing the truth around AIWednesday, July 22, 2026
TRV-2026-0402Certified recordPeer-reviewed

Artificial intelligence and radiologists in prostate cancer detection on MRI (PI-CAI): an international, paired, non-inferiority, confirmatory study

BACKGROUND: Artificial intelligence (AI) systems can potentially aid the diagnostic pathway of prostate cancer by alleviating the increasing workload, preventing overdiagnosis, and reducing the dependence on experienced radiologists. We aimed to investigate the performance of AI systems at detecting clinically significant prostate cancer on MRI in comparison with radiologists using the Prostate Imaging-Reporting and Data System version 2.1 (PI-RADS 2.1) and the standard of care in multidisciplinary routine pract…

Health · P Space — documented harm · certified 2026-07-20 · v1 · article view · machine-readable

Current reading — problem

When compared to historical multidisciplinary routine practice readings in 1000 testing cases, the AI system did not demonstrate confirmed non-inferiority and showed slightly lower specificity at matched sensitivity.

What this doesn’t fix

Retrospective design and need for prospective testing; authors note clinical applicability not yet established.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0402, v1: “Artificial intelligence and radiologists in prostate cancer detection on MRI (PI-CAI): an international, paired, non-inferiority, confirmatory study.” Truvace, 2026-07-20. /record/TRV-2026-0402 (accessed at citation time). sha256 2e2a27b44c9339bc

Calibration history

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

  1. Certifiedv12e2a27b44c93

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