TruaceTracing the truth around AIWednesday, August 5, 2026
TRV-2026-0572Certified recordPeer-reviewed

Early Identification of Recovery Potential After Acute Brain Injury Using Functional Near-Infrared Spectroscopy

Background Accurate early prognostication in patients with acute brain injury remains a major challenge in neurocritical care. Conventional bedside assessments provide limited insight into long-term outcomes and may not fully capture preserved brain function that supports recovery. Functional neuroimaging can detect brain activity not evident at the bedside, but its use in intensive care remains constrained by cost, logistics, and the need for stronger evidence supporting its value. Functional near-infrared spec…

Health · G Space — documented gain · certified 2026-07-26 · v1 · article view · machine-readable

Current reading — gain

A machine learning model using bedside fNIRS functional connectivity during audio movie clips predicted 6-month functional outcome in ICU patients with acute brain injury with 81.3% balanced accuracy, outperforming clinical models.

What this doesn’t fix

Small single-center cohort of 33 patients with imbalanced outcomes limits generalizability and requires larger multicenter validation before clinical use.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0572, v1: “Early Identification of Recovery Potential After Acute Brain Injury Using Functional Near-Infrared Spectroscopy.” Truvace, 2026-07-26. /record/TRV-2026-0572 (accessed at citation time). sha256 062538012db179ab

Calibration history

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

  1. Certifiedv1062538012db1

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