56/100

Moderate evidence

GainPublished recordHealthGood Space

Can radiomics outperform radiologists in predicting Ewing sarcoma response to neoadjuvant chemotherapy from longitudinal MRI?

Truvace record
TRV-2026-2893raw data (JSON)
Version
v1Published
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
1b71cfcba5b2…check it

This retrospective, multicenter study evaluated whether MRI-based radiomics can predict the histological response to neoadjuvant chemotherapy in Ewing sarcoma patients and compared their performance to that of radiological findings. Definitive histological assessment is only possible during surgery, potentially delaying therapy changes and increasing metastatic risk; therefore, a positive outcome would enable early adaptations. Radiomics features were extracted from pre- and post-neoadjuvant (after first chemoth…

The gain

In a retrospective study of 96 Ewing sarcoma patients, MRI radiomics models identified chemotherapy responders with an AUROC of 0.62, above 0.58 for the best model built on radiologist readings and 0.53 for a clinical baseline.

What this doesn’t fix

The study was retrospective and exploratory, the identification of responders was only moderate, and the authors say larger prospective trials are needed to validate the findings.

Sources

1 on file
  1. BMC Cancerdoi:10.1186/s12885-026-17332-0
    Peer-reviewed2026-11-12

Cite this record

v1

Truvace Impact Record TRV-2026-2893, v1: “Can radiomics outperform radiologists in predicting Ewing sarcoma response to neoadjuvant chemotherapy from longitudinal MRI?.” Truvace, 2026-11-13. /record/TRV-2026-2893 (accessed on the day you copy it). sha256 1b71cfcba5b2ea91…

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. Publishedv11b71cfcba5b2…

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