63/100

Moderate evidence

Published recordHealthGeneral

Longitudinal symptom severity tracking in vagus nerve stimulation patients: a 2-stage LLM-based pipeline with explainable AI

Truvace record
TRV-2026-1260raw data (JSON)
Version
v2Revised
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
f1047ec61cde…check it

Objectives To produce the first structured longitudinal dataset of symptom severity trajectories in vagus nerve stimulation (VNS) patients using a 2-stage large language model pipeline for automated symptom severity extraction from clinical notes, as part of the NIH-funded research evaluating vagal excitations and anatomical linkages (U54AT012307). Materials and methods We analyzed 1427 annotated clinical notes from 95 patients across 5 corpora. LLaMA models (3.2-1B, 3.2-3B, and 3.3-70B) were fine-tuned to class…

The gain

Fine-tuned LLaMA models extracted symptom presence and severity from free-text notes with high F1 scores, enabling the first structured quarterly trajectories for VNS patients.

Sources

1 on file
  1. JAMIA Opendoi:10.1093/jamiaopen/ooag195
    Peer-reviewed2026-10-01

Cite this record

v2

Truvace Impact Record TRV-2026-1260, v2: “Longitudinal symptom severity tracking in vagus nerve stimulation patients: a 2-stage LLM-based pipeline with explainable AI.” Truvace, 2026-11-04. /record/TRV-2026-1260 (accessed on the day you copy it). sha256 f1047ec61cdec6b4…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv2f1047ec61cde…

    Editorial pass: sharper headline; filed as context: no real AI gain or problem (gain activity_only, problem absent).

  2. Publishedv1fda06cf647b9…

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