70/100

Moderate evidence

GainPublished recordHealthGood Space

Decoding Complications: Large Language Model-Based Classification of Free-Text Entries in Clinical Stroke Registries

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

Clinical registries capture adverse events (AEs) in free-text fields that are rarely analyzed. We developed a reproducible large language model (LLM)-assisted workflow using 11,216 free-text entries from 18,069 patients in the German Stroke Registry; 9,146 informative entries were retained after filtering. Embedding-based clustering showed poor separation, whereas an LLM-guided taxonomy identified 89 leaf labels. On the model-assisted 1,000-entry development set used for model and prompt selection, GPT-5.4 reach…

The gain

In a German Stroke Registry study, GPT-5.4 labelled 300 held-out free-text entries at 96.5% weighted F1 against clinician consensus, and the free text documented 1,345 more adverse-event instances (+19.6%) than the structured field for comparable concepts.

What this doesn’t fix

Gains in outcome prediction were minimal once the discharge NIHSS score was included, and the test on a second corpus only showed the software ran end to end rather than validating accuracy.

Sources

1 on file
  1. Journal of Medical Systemsdoi:10.1007/s10916-026-02486-y
    Peer-reviewed2026-11-16

Cite this record

v1

Truvace Impact Record TRV-2026-2994, v1: “Decoding Complications: Large Language Model-Based Classification of Free-Text Entries in Clinical Stroke Registries.” Truvace, 2026-11-17. /record/TRV-2026-2994 (accessed on the day you copy it). sha256 f4a4aebc31475b7d…

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. Publishedv1f4a4aebc3147…

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