Moderate evidence
Published recordHealthGood Space
More
InterGenEHR$^+$: An Interactive Framework for Natural Language-Conditioned Generation of Longitudinal Patient Trajectories
- Truvace record
- TRV-2026-3067raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 358352bdafbb…check it
Objective: To develop and validate InterGenEHR+, an interactive framework for natural language-conditioned generation of synthetic tabular data and longitudinal EHR trajectories for critically ill patients requiring mechanical ventilation and venovenous extracorporeal membrane oxygenation (VV-ECMO), enabling scenario-based evaluation of machine learning models in high-risk cohorts. Methods: InterGenEHR+ uses an optional large language model (LLM) parser for text-driven input. For single-time-point generation, we…
The gain
In a study of a multi-institutional cohort of 874 VV-ECMO patients, mortality models trained on InterGenEHR+ synthetic records kept predictive utility on real test data, and clinicians rated the generated trajectories clinically plausible.
What this doesn’t fix
The framework was evaluated in a single VV-ECMO cohort of 874 patients, and extension to other clinical settings is stated as a possibility rather than shown.
Sources
1 on file- IEEE Transactions on Biomedical Engineeringdoi:10.1109/tbme.2026.3753060
Cite this record
v1Truvace Impact Record TRV-2026-3067, v1: “InterGenEHR$^+$: An Interactive Framework for Natural Language-Conditioned Generation of Longitudinal Patient Trajectories.” Truvace, 2026-11-20. /record/TRV-2026-3067 (accessed on the day you copy it). sha256 358352bdafbb0788…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-3067 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.
ace