TRV-2026-1594Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1594 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-16T18:13:07.151107Z status: published lens: g_space sector: health headline: An artificial intelligence framework for end-to-end rare disease phenotyping from clinical notes using large language models dek: Phenotyping is fundamental to rare disease diagnosis, but manually curating structured phenotypes from clinical notes is labor intensive and difficult to scale. Existing artificial intelligence (AI) approaches optimize individual components of phenotyping but generally do not operationalize the full workflow of extracting features from clinical text, standardizing them to Human Phenotype Ontology (HPO) terms, and prioritizing rare disease-relevant HPO terms. We developed RARE-PHENIX, an end-to-end AI framework f… gain_title: RARE-PHENIX automates extraction, HPO standardization and ranking of phenotypes from clinical notes, producing terms highly concordant with clinician curation and reducing reliance on labor-intensive manual curation. problem_title: (none) trace_subject: (none) gain_reading: RARE-PHENIX automates extraction, HPO standardization and ranking of phenotypes from clinical notes, producing terms highly concordant with clinician curation and reducing reliance on labor-intensive manual curation. gain_evidence: generates structured, prioritized HPO terms highly concordant with clinician curation problem_reading: (none) problem_evidence: (none) quick_read: Researchers built RARE-PHENIX, a framework that chains together three steps of rare disease phenotyping: large language model extraction of features from clinical text, mapping of those features to Human Phenotype Ontology terms, and supervised ranking of the terms most relevant to rare disease. Phenotyping underpins rare disease diagnosis, yet manual curation is slow and hard to scale, so automating the whole workflow could matter for clinical genetics. The authors describe their results as suggestive and as supporting human review rather than replacing it, and the disease-prioritization signal is described only as potential. limitation: The authors frame the findings cautiously, describing only potential downstream disease-prioritization signal and possible support for human-in-the-loop use rather than demonstrated autonomous diagnostic benefit. tag: Evidence-backed gain key_points: The framework combines LLM-based phenotype extraction, ontology-grounded HPO standardization, and supervised ranking of HPO terms. | Training used data from 2671 patients across 11 Undiagnosed Diseases Network clinical sites. | External validation used 16,357 real-world clinical notes from 143 patients at Vanderbilt University Medical Center. | Output was highly concordant with clinician curation and showed potential downstream disease-prioritization signal. rundown: The study starts from a bottleneck: manually curating structured phenotypes from clinical notes is labor intensive and difficult to scale, even though phenotyping is fundamental to diagnosing rare diseases. Earlier AI approaches tended to optimize individual components and did not operationalize the full workflow from clinical text to standardized, prioritized HPO terms. RARE-PHENIX is presented as an end-to-end alternative that covers that whole workflow. Testing moved from the multi-site Undiagnosed Diseases Network training cohort to a separate external set of notes at Vanderbilt University Medical Center. The authors conclude it may support human-in-the-loop phenotyping in real-world settings. sources: - peer_reviewed | npj Digital Medicine | https://doi.org/10.1038/s41746-026-03275-0 | 2026-10-15 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- cd37f86d39b7ef6387f8c6d1a3eba1d7135f4d673b0c6283f4be093d27c69e89
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1594 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