64/100

Moderate evidence

GainPublished recordHealthGood Space

Commercially available multimodal LLMs for EEG-based prognostication after cardiac arrest

Truvace record
TRV-2026-3020raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
ba473e53cfbe…check it

Objectives: Machine-learning and deep-learning approaches have been successfully applied to EEG-based prognostication in comatose patients after cardiac arrest (CA), but typically rely on task-specific signal processing, feature extraction, and model development. Here, we investigated whether two commercially available multimodal large language models (LLMs) could predict neurological outcome directly from EEG images. Methods: Thirty-three comatose patients on the first day after CA from a prospective cohort wer…

The gain

In an exploratory study of 33 comatose cardiac arrest patients, ChatGPT 5.4 and Claude Opus 4.7 each reached 93.9% accuracy at predicting favorable neurological outcome from a single 10-second EEG image using few-shot prompting.

What this doesn’t fix

The study was exploratory and used only 33 patients, performance depended substantially on prompt design, and the authors say the findings require confirmation in a larger cohort.

Sources

1 on file
  1. Resuscitationdoi:10.1016/j.resuscitation.2026.111398
    Peer-reviewed2026-11-17

Cite this record

v1

Truvace Impact Record TRV-2026-3020, v1: “Commercially available multimodal LLMs for EEG-based prognostication after cardiac arrest.” Truvace, 2026-11-18. /record/TRV-2026-3020 (accessed on the day you copy it). sha256 ba473e53cfbee478…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1ba473e53cfbe…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-3020 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.