68/100

Moderate evidence

GainPublished recordHealthGood Space

Multicenter evaluation of radiomics and multimodal artificial intelligence for colorectal cancer diagnosis and survival prediction

Truvace record
TRV-2026-3065raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
7daa54e0f80f…check it

Abstract Reliable preoperative classification and outcome prediction could improve management of locally advanced colorectal cancer. We retrospectively studied 879 participants from two centers, including 741 patients with locally advanced colorectal cancer and 138 with benign colorectal lesions. Clinical, radiomics, deep learning, and early fusion models were trained at center A ( n = 615) and independently tested at center B ( n = 264) using pretreatment contrast-enhanced computed tomography and clinical data.…

The gain

In a retrospective study of 879 patients at two centres, a clinical-radiomics model trained at one centre separated malignant from benign colorectal lesions with a test AUC of 0.957 at the second centre.

What this doesn’t fix

The study was retrospective, and the early deep learning fusion approach offered limited incremental value over an optimized radiomics baseline.

Sources

1 on file
  1. npj Digital Medicinedoi:10.1038/s41746-026-03434-3
    Peer-reviewed2026-11-19

Cite this record

v1

Truvace Impact Record TRV-2026-3065, v1: “Multicenter evaluation of radiomics and multimodal artificial intelligence for colorectal cancer diagnosis and survival prediction.” Truvace, 2026-11-20. /record/TRV-2026-3065 (accessed on the day you copy it). sha256 7daa54e0f80ff745…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv17daa54e0f80f…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-3065 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.