TRV-2026-2075Certified recordPeer-reviewed

MRI-Based Machine Learning to Differentiate True Progression from Pseudoprogression in Glioblastoma: An Updated Systematic Review and Meta-Analysis

Background Differentiating true progression (TP) from pseudoprogression (PsP) after chemoradiation for glioblastoma remains clinically difficult. We evaluated externally validated diagnostic performance of magnetic resonance imaging (MRI)-based machine learning models and appraised study quality and transparency. Methods PubMed, Embase, MEDLINE, and Cochrane Library were searched through October 1, 2025 (PROSPERO registration CRD420251144894). Eligible adult glioblastoma studies used MRI-based machine learning t…

Health · The Trace — both readings · certified 2026-10-21 · v1 · article view · machine-readable

Current reading — gain

In external test cohorts, MRI-based machine learning models distinguished true glioblastoma progression from pseudoprogression with pooled sensitivity of 0.78 and specificity of 0.75.

Current reading — problem

The supporting evidence is weak: external cohorts were small, risk of bias was often high or unclear, and reporting was incomplete, so the models are not ready for routine clinical use.

What this doesn’t fix

The external evidence base is small and often biased or incompletely reported, so the pooled accuracy may not hold up in routine care; larger transparent multicenter validations are still needed.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2075, v1: “MRI-Based Machine Learning to Differentiate True Progression from Pseudoprogression in Glioblastoma: An Updated Systematic Review and Meta-Analysis.” Truvace, 2026-10-21. /record/TRV-2026-2075 (accessed at citation time). sha256 397ce5b5386e037d…

Calibration history

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

  1. Certifiedv1397ce5b5386e…

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