TRV-2026-2298Certified recordPeer-reviewed

Artificial intelligence–based tumor detection using stimulated Raman histology in patients undergoing neurosurgical biopsies

OBJECTIVE Intraoperative confirmation of diagnostic tumor tissue is critical in neurosurgical biopsies, particularly in stereotactic procedures, in which sampling error remains a major limitation. Stimulated Raman histology (SRH) enables rapid, label-free tissue imaging directly in the operating room. This study aimed to evaluate the performance of intraoperative SRH combined with artificial intelligence (AI)–based tumor detection using a CE (Conformité Européenne)–certified algorithm under routine clinical cond…

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

Current reading — gain

In 204 scans from 89 biopsy patients, the Glioma Reveal algorithm detected tumor tissue with 80.9% initial accuracy, rising to 94.1% after expert review, giving rapid intraoperative confirmation of tumor tissue.

Current reading — problem

The algorithm reached only 62.5% accuracy on nonneoplastic lesions because of reactive mimics, and sensitivity for gliomas and lymphomas was 78.8%, with false negatives driven by tissue heterogeneity.

What this doesn’t fix

This was a retrospective single-center study, and the higher accuracy figures relied on expert re-review of discordant cases rather than the algorithm alone; heterogeneity and sampling differences affected metrics.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2298, v1: “Artificial intelligence–based tumor detection using stimulated Raman histology in patients undergoing neurosurgical biopsies.” Truvace, 2026-10-28. /record/TRV-2026-2298 (accessed at citation time). sha256 cfb0cbd9d75a7f09…

Calibration history

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

  1. Certifiedv1cfb0cbd9d75a…

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