TRV-2026-2299Certified recordPeer-reviewed

Intraoperative artificial intelligence for brain tumor surgery: from tissue diagnosis to real-time surgical guidance

The 2021 WHO CNS tumor classification marked a fundamental shift in neuro-oncology: molecular markers rather than histological appearance now define glioma diagnosis and guide treatment. Yet, in clinical practice the molecular information that matters most to a surgeon—IDH status, 1p/19q codeletion, and methylation class—typically arrives days to weeks after the operation it was meant to inform. Artificial intelligence (AI) is beginning to close that gap. Over the past several years, a growing body of work has d…

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

Current reading — gain

AI models can give surgeons molecular tumor information during the operation, for example ROBIN nanopore classification reached 90% concordance with the final diagnosis in under 2 hours, rather than days to weeks later.

Current reading — problem

Widespread clinical adoption of intraoperative AI is held back because no randomized clinical trials yet show that these tools benefit patients.

What this doesn’t fix

The review says adoption is limited by the absence of randomized clinical trials showing patient-level benefit, so improved patient outcomes are not established.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2299, v1: “Intraoperative artificial intelligence for brain tumor surgery: from tissue diagnosis to real-time surgical guidance.” Truvace, 2026-10-28. /record/TRV-2026-2299 (accessed at citation time). sha256 5c96085c86c04c4b…

Calibration history

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

  1. Certifiedv15c96085c86c0…

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