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

Radiomics and dosiomics in radionecrosis prediction in brain metastasis treated with Stereotactic Radiation Therapy: a machine learning approach

Introduction Stereotactic Radiotherapy plays a main role in Brain Metastases treatment. Radiomics and Dosiomics, coupled with Machine Learning approaches are emerging in radiation oncology as support in clinical decision-making workflow. In this study a machine learning approach was used to predict the late toxicities induced by Stereotactic Radiotherapy including clinical, radiomics and dosiomics features extracted from patients. Materials and methods Lesions contribution, concomitant and/or sequential treatmen…

Health · G Space — documented gain · certified 2026-09-15 · v1 · article view · machine-readable

Current reading — gain

Machine learning models trained on clinical, radiomics and dosiomics features predicted radionecrosis after stereotactic radiotherapy for brain metastases with ROC-AUC up to 80%, offering decision support that may improve patient-specific treatment and reduce radiotherapy-induced toxicity severity.

What this doesn’t fix

Findings are based on a small single-cohort sample of 37 patients / 113 lesions with wide confidence intervals, limiting generalizability and precision of performance estimates.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1098, v1: “Radiomics and dosiomics in radionecrosis prediction in brain metastasis treated with Stereotactic Radiation Therapy: a machine learning approach.” Truvace, 2026-09-15. /record/TRV-2026-1098 (accessed at citation time). sha256 773942fd7fa92269

Calibration history

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

  1. Certifiedv1773942fd7fa9

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