TRV-2026-2209Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-2209 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-23T06:46:21.257189Z status: published lens: g_space sector: health headline: AI-Powered Structuring of Clinical Information in Parkinson's Disease: An Approach Based on Large Language Models dek: Advanced Parkinson's Disease (APD) is clinically heterogeneous, and many APD-defining features are recorded predominantly in unstructured neurology narratives, limiting scalable phenotyping and longitudinal analyses. An approach based on large language models (LLMs) was designed to transform free text from electronic health records (EHRs) into an APD-oriented dataset aligned with Questionnaire for the Evaluation of Advanced Parkinson's Disease (CDEPA)-derived domains. A retrospective EHR cohort identified betwee… gain_title: A schema-guided LLM pipeline with vote-based aggregation extracted 22 advanced Parkinson's indicators from 1,201 patients' records, with 85.4% sensitivity and 94.6% NPV against neurologist annotation. problem_title: (none) trace_subject: (none) gain_reading: A schema-guided LLM pipeline with vote-based aggregation extracted 22 advanced Parkinson's indicators from 1,201 patients' records, with 85.4% sensitivity and 94.6% NPV against neurologist annotation. gain_evidence: accuracy was 83.3%, precision 61.4%, sensitivity 85.4%, specificity 82.7%, negative predictive value (NPV) 94.6%, and F1-score 71.4% problem_reading: (none) problem_evidence: (none) quick_read: Researchers built a pipeline in which GPT-4o reads de-identified free-text neurology records from a tertiary service and fills a structured schema of 22 binary indicators of advanced Parkinson's disease, plus the diagnosis date. The records covered 1,201 confirmed patients identified between 2018 and 2023. The work matters because many features that define advanced Parkinson's disease sit in narrative notes, which limits large-scale phenotyping and longitudinal analysis. The study reports that structured output can support research and modeling, but precision was modest, diagnosis dates were weak, and the authors call for targeted clinical review of critical fields. limitation: Diagnosis-date extraction remained the main limitation, and the authors recommend targeted clinical review for critical fields; precision was also only 61.4%. tag: Evidence-backed gain key_points: The retrospective cohort comprised 1,201 confirmed Parkinson's patients from a tertiary neurology service, identified between January 2018 and January 2023. | The schema aligned with domains derived from the CDEPA questionnaire and used 22 binary indicators plus the diagnosis date. | Repeated sampling with vote-based aggregation, recursive routing, and deterministic temporal normalization were used to reduce variability. | Four neurologists annotated 120 cases as the reference standard, covering 2,760 variable instances. | Precision was 61.4%, well below the 94.6% negative predictive value. rundown: The pipeline has four functional blocks: presence, absence, or unknown classification; controlled-option selection; temporal-period extraction; and date extraction. Records were de-identified with a privacy-preserving step before GPT-4o processed them. Against the expert reference, the method outperformed zero-shot biomedical and clinical baselines and direct GPT-4o. Paired patient-level analyses showed significant improvements over GPT-4o and the no-voting ablation on all six metrics after Holm correction. The authors say diagnosis-date extraction remained the main limitation. They propose using the workflow with targeted clinical review for critical fields rather than as a fully autonomous tool. sources: - peer_reviewed | IEEE Journal of Biomedical and Health Informatics | https://doi.org/10.1109/jbhi.2026.3746031 | 2026-10-21 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 506989f3d2cd761fb9da421600b021262f23b035dced78cba7bfd3431df2d6ae
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-2209 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.
ace