A common longitudinal intensive care unit data format (CLIF) for critical illness research

Juan C. Rojas, Patrick G. Lyons, Kaveri Chhikara, Vaishvik Chaudhari, Sivasubramanium V. Bhavani, Muna Nour, Kevin G. Buell, Kevin D. Smith, Catherine A. Gao, Saki Amagai, Chengsheng Mao, Yuan Luo, Anna K. Barker, Mark Nuppnau, Michael Hermsen, Jay L. Koyner, Haley Beck, Rachel Baccile, Zewei Liao, Kyle A. CareyBrenna Park-Egan, Xuan Han, Alexander C. Ortiz, Benjamin E. Schmid, Gary E. Weissman, Chad H. Hochberg, Nicholas E. Ingraham, William F. Parker*

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

1 Scopus citations

Abstract

Rationale: Critical illness threatens millions of lives annually. Electronic health record (EHR) data are a source of granular information that could generate crucial insights into the nature and optimal treatment of critical illness. Objectives: Overcome the data management, security, and standardization barriers to large-scale critical illness EHR studies. Methods: We developed a Common Longitudinal Intensive Care Unit (ICU) data Format (CLIF), an open-source database format to harmonize EHR data necessary to study critical illness. We conducted proof-of-concept studies with a federated research architecture: (1) an external validation of an in-hospital mortality prediction model for critically ill patients and (2) an assessment of 72-h temperature trajectories and their association with mechanical ventilation and in-hospital mortality using group-based trajectory models. Measurements and main results: We converted longitudinal data from 111,440 critically ill patient admissions from 2020 to 2021 (mean age 60.7 years [standard deviation 17.1], 28% Black, 7% Hispanic, 44% female) across 9 health systems and 39 hospitals into CLIF databases. The in-hospital mortality prediction model had varying performance across CLIF consortium sites (AUCs: 0.73–0.81, Brier scores: 0.06–0.10) with degradation in performance relative to the derivation site. Temperature trajectories were similar across health systems. Hypothermic and hyperthermic-slow-resolver patients consistently had the highest mortality. Conclusions: CLIF enables transparent, efficient, and reproducible critical care research across diverse health systems. Our federated case studies showcase CLIF’s potential for disease sub-phenotyping and clinical decision-support evaluation. Future applications include pragmatic EHR-based trials, target trial emulations, foundational artificial intelligence (AI) models of critical illness, and real-time critical care quality dashboards.

Original languageEnglish (US)
Article number160035
Pages (from-to)556-569
Number of pages14
JournalIntensive Care Medicine
Volume51
Issue number3
DOIs
StatePublished - Mar 2025

Funding

Dr. Lyons is supported by NIH/NCI K08CA270383. Dr. Rojas is supported by NIH/NIDA R01DA051464 and the Robert Wood Johnson Foundation and has received consulting fees from Truveta. Dr. Bhavani is supported by NIH/NIGMS K23GM144867. Dr. Buell is supported by an institutional research training grant (NIH/NHLBI T32 HL007605). Dr. Gao is supported by NIH/NHLBI K23HL169815, a Parker B. Francis Opportunity Award, and an American Thoracic Society Unrestricted Grant. Dr. Luo is supported in part by NIH U01TR003528 and R01LM013337. Dr. Hochberg is supported by NIH/NHLBI K23HL169743. Dr. Ingraham is supported by NIH/NHLBI K23HL166783. Dr. Ortiz is supported by an institutional research training grant (NIH/NHLBI T32 HL007891). Dr. Weissman is supported by NIH/NIGMS R35GM155262. Dr. Parker is supported by NIH K08HL150291, R01LM014263, and the Greenwall Foundation. The other authors have no conflicts of interest to disclose.

Keywords

  • Critical care data
  • Machine learning
  • Temperature trajectory modeling

ASJC Scopus subject areas

  • Critical Care and Intensive Care Medicine

Fingerprint

Dive into the research topics of 'A common longitudinal intensive care unit data format (CLIF) for critical illness research'. Together they form a unique fingerprint.

Cite this