Moderate evidence
Published recordHealthProblem Space
More
Assessment of Vestibular Schwannoma Growth After Radiosurgery: Variability in Clinical Decision Thresholds and the Role of Artificial Intelligence
- Truvace record
- TRV-2026-2898raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- 6fc1d8ab2846…check it
To quantify expert interobserver variability in longitudinal vestibular schwannoma growth assessment after radiosurgery and evaluate AI segmentation performance relative to human variability. Retrospective review of patients with sporadic unilateral VS treated with stereotactic radiosurgery (2001-2023). Manual and AI segmentations were compared across the cohort. A growth-enriched subset of 24 tumors underwent additional expert assessment. Agreement was evaluated using intraclass correlation coefficients (ICC),…
The problem
In a retrospective study of 85 radiosurgery patients (170 MRI exams), AI segmentation reached only 83.5% binary agreement with experts on tumor growth (Cohen κ 0.47), with limits of agreement from -53.33 to 66.60 percentage points.
What this doesn’t fix
Growth classification was assessed by multiple experts only on a growth-enriched subset of 24 tumors, and the study was a retrospective review.
Sources
1 on file- Journal of Imaging Informatics in Medicinedoi:10.1007/s10278-026-02516-8
Cite this record
v1Truvace Impact Record TRV-2026-2898, v1: “Assessment of Vestibular Schwannoma Growth After Radiosurgery: Variability in Clinical Decision Thresholds and the Role of Artificial Intelligence.” Truvace, 2026-11-14. /record/TRV-2026-2898 (accessed on the day you copy it). sha256 6fc1d8ab28467b63…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2898 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.
ace