# CHORUS Dataset Documentation

Datasheet for Dataset - Human Readable Format

🎯

## Motivation

Why was the dataset created?

Purposes

Description | ID | Name
--- | --- | ---
Answer the grand challenge of improving recovery from acute illness by developing high-resolution multi-center datasets as a critical first step towards actionable and trustworthy AI in critical care. Address the urgent need for infrastructure to support artificial intelligence and machine learning (AI/ML) in critical care settings. | chorus:purpose:1 | Improve recovery from acute illness
Develop a publicly available, AI-ready critical care dataset from more than 100,000 critically ill patients while ensuring methods promote privacy, accountability, and clinical benefit. Generate the most diverse, high-resolution, ethically sourced dataset for AI/ML applications in acute and critical care, expanding AI and Machine Learning to improve recovery from acute illness. | chorus:purpose:2 | Create AI-ready critical care dataset
Unify standards to harmonize multi-modal EHR, waveform, imaging, and text data. Develop software and tooling to interact with and extract insight from clinical data in diverse formats. Create validated semantic mappings for connecting clinical data in various source formats to international standards (OMOP Common Data Model, DICOM, WFDB, OHNLP). | chorus:purpose:3 | Establish data standards and tools
Ensure comprehensive sets of patient conditions and clinical treatment strategies with appropriate contextual factors such as geographic distance to nearest hospital and Social Determinants of Health. Develop the skills and workforce for a next generation of diverse academic and community AI scientists through comprehensive training and education programs in partnership with AIM-AHEAD. | chorus:purpose:4 | Promote diversity and health equity

Funders

- ID
    chorus:funder:1
  Name
    NIH Common Fund Bridge2AI Program
  Description
    Funded through National Institutes of Health grant OT2OD032701 (project number 1OT2OD032701-01), administered by NIH Office of the Director. Opportunity Number: OTA-21-008. Study Section: Data Coordination, Mapping, and Modeling (DCMM). Fiscal Year 2022. Total funding in 2022: $5,880,300 (all direct costs). Project dates: September 1, 2022 to November 30, 2026 (with approved no-cost extension). Award notice date: September 1, 2022. Assistance Listing Number: 93.310.

📊

## Composition

What do the instances represent?

Instances

1. ID
     chorus:instance:1
   Name
     Critically ill patients in ICU settings
   Description
     Individual critically ill patients requiring acute or critical care admitted to intensive care units (ICU), pediatric intensive care units (PICU), or neonatal intensive care units (NICU) across 14 data acquisition centers. As of August 2025, the dataset covers 14 different hospitals with over 45,000 unique admissions, with 50,000 patient admissions from ICU, PICU, and NICU currently released. Target enrollment exceeds 100,000 critically ill patients. Retrospective data collection from patients with acute or critical illness.
   Instance Type
     Human subjects - critically ill patients admitted to participating hospitals (retrospective data collection, ongoing collection through November 2026).

Subpopulations

Description | ID | Name
--- | --- | ---
Patients distributed across 14 different hospitals within the CHoRUS network spanning 20 academic centers in the United States, ensuring geographic and institutional diversity in critical care settings. | chorus:subpop:1 | Critically ill patients by hospital
Patients admitted to intensive care units (ICU), pediatric intensive care units (PICU), and neonatal intensive care units (NICU) across contributing hospitals, with 50,000 patient admissions in the current released dataset. | chorus:subpop:2 | ICU, PICU, and NICU patients

Distribution Formats

Access Urls | Description | ID | Name
--- | --- | --- | ---
https://chorus4ai.org/ | Structured electronic health record data distributed in OMOP Common Data Model format enabling use of OHDSI tool stack for analysis. Contains 1.6 billion rows. Available in secure enclave with controlled access. Published OMOP schema metadata available. | chorus:format:1 | OMOP Common Data Model (structured EHR data)
https://chorus4ai.org/ | Waveform telemetry data (23 TB) distributed in WFDB (WaveForm DataBase) format following extended PhysioNet schema. Available in secure enclave with controlled access. Published PhysioNet schema (extended) metadata available. | chorus:format:2 | WFDB waveform format (bedside monitor telemetry)
https://chorus4ai.org/ | Medical imaging data (7,642 admissions with radiology; 1,000 images currently available) distributed in DICOM format with comprehensive metadata following DICOM schema. De-identification in process for larger cohort. Planned controlled access. | chorus:format:3 | DICOM format (medical imaging)
https://chorus4ai.org/ | Clinical notes distributed as OHNLP-tokenized text following open source OHNLP schema. Stored locally at contributing sites (except tokens). Controlled access planned. | chorus:format:4 | OHNLP tokenized format (clinical notes)
https://chorus4ai.org/ | EEG waveform data distributed in EDF+ (European Data Format) and Persyst formats following open source schemas. Extraction in process, planned for controlled access. | chorus:format:5 | EDF+ and Persyst formats (EEG waveforms)

🔍

## Collection Process

How was the data acquired?

ID
https://chorus4ai.org/
Name
CHoRUS
Title
Patient-Focused Collaborative Hospital Repository Uniting Standards (CHoRUS) for Equitable AI
Description
CHoRUS for Equitable AI is a Bridge2AI data generation project developing the most diverse, high-resolution, ethically sourced, AI-ready critical care dataset to answer the grand challenge of improving recovery from acute illness. The project spans 20 academic centers (14 data acquisition centers) and is building a publicly available dataset targeting over 100,000 critically ill patients with multi-modal data including structured EHR, waveform telemetry, medical imaging, EEG, and clinical notes. All structured data is standardized to the OMOP Common Data Model with additional formats (DICOM, WFDB, OHNLP tokenization) and comprehensive metadata schemas. Patient-focused efforts determine ethical and legal approaches to manage privacy and bias while accounting for Social Determinants of Health. A visualization and annotation environment labels data with targets important for prediction. The project emphasizes skills and workforce development for a next generation of diverse academic and community AI scientists through training programs and partnerships with AIM-AHEAD. As of August 2025, the dataset covers 14 different hospitals with over 45,000 unique admissions and includes 50,000 patient admissions from ICU, PICU, and NICU, 1.6 billion rows of EHR OMOP data, 7,642 admissions with radiology data, and 23 TB of waveform data.
Page
https://chorus4ai.org/
Language
en
Keywords

- CHoRUS
- Bridge2AI
- critical care
- acute illness
- AI-ready dataset
- OMOP Common Data Model
- electronic health records
- EHR
- waveform telemetry
- medical imaging
- DICOM
- EEG
- clinical notes
- OHNLP
- health equity
- social determinants of health
- federated access
- multi-modal data
- high-resolution data
- ethical AI
- trustworthy AI
- workforce development
- data standardization
- privacy preservation
- bias mitigation
- ICU
- intensive care

Research Gaps Addressed

Description | ID | Name
--- | --- | ---
Address the absence of large-scale, diverse, high-resolution multi-center datasets for critical care AI/ML by creating a dataset spanning 20 academic centers with 100,000+ critically ill patients and ensuring balanced, diverse cohorts through federated access and sampling methods across 14 data acquisition centers. | chorus:gap:1 | Lack of diverse multi-center critical care datasets
Overcome the lack of unified standards in critical care data by harmonizing multi-modal EHR, waveform, imaging, and text data to OMOP Common Data Model and other international standards (DICOM, WFDB, OHNLP). | chorus:gap:2 | Insufficient data standardization in critical care
Address ethical and legal challenges in AI through patient-focused efforts that determine approaches to manage privacy and bias while accounting for Social Determinants of Health and performing community-facing ethics focus groups to determine what data is appropriate for public sharing. | chorus:gap:3 | Privacy and bias concerns in clinical AI
Bridge the gap in diverse AI/ML workforce through comprehensive educational approaches, training programs (including AIM-AHEAD partnership), and cultivation of expertise in lay and scientific communities to improve AI literacy and utilization. | chorus:gap:4 | Limited diversity in AI/ML workforce

Creators

Role | Name | ORCID | Affiliation
--- | --- | --- | ---
Contributor | Eric S. Rosenthal | chorus:creator:1 | -
Contributor | Azra Bihorac | chorus:creator:2 | -
Contributor | Ashley Cordes | chorus:creator:3 | -
Contributor | Gilles Clermont | chorus:creator:4 | -
Contributor | Gari David Clifford | chorus:creator:5 | -
Contributor | Barbara J. Evans | chorus:creator:6 | -
Contributor | Xiao Hu | chorus:creator:7 | -
Contributor | Rishikesan Kamaleswaran | chorus:creator:8 | -
Contributor | Yulia A. Levites Strekalova | chorus:creator:9 | -
Contributor | Parisa Rashidi | chorus:creator:10 | -
Contributor | Cynthia Rudin | chorus:creator:11 | -
Contributor | Ishan Canty Williams | chorus:creator:12 | -
Contributor | Andrew Ewing Williams | chorus:creator:13 | -
Contributor | Xiaoqian Jiang | chorus:creator:14 | -
Contributor | Morteza Zabihi | chorus:creator:15 | -
Contributor | Zhenhong Hu | chorus:creator:16 | -
Contributor | Debora Simmons | chorus:creator:17 | -
Contributor | Aliyah Geer | chorus:creator:18 | -
Contributor | Ciera McCrary | chorus:creator:19 | -

Subsets

Description | ID | Name
--- | --- | ---
Primary dataset with controlled access requiring data use agreement and licensing. Includes OMOP-standardized structured EHR data comprising demographics, medication administration (dosing time-stamped upon each infusion change or dose administration), procedures, nursing flowsheets (high-frequency documentation), and diagnoses. Available in secure enclave. As of August 2025, contains 1.6 billion rows of EHR OMOP data. Registration required with institutional email; all participants must sign licensing agreement. | chorus:subset:1 | Controlled Access Structured EHR Dataset (OMOP)
Waveform telemetry data from bedside monitors (gateway/middleware) standardized to WFDB (WaveForm DataBase) format following extended PhysioNet schema. Available in secure enclave with controlled access. As of August 2025, contains 23 TB of waveform data. Published metadata schema: PhysioNet schema (extended). | chorus:subset:2 | Waveform Telemetry Dataset (WFDB)
Imaging data from hospital PACS (Picture Archiving and Communication System) in DICOM format with comprehensive metadata following DICOM schema. As of August 2025, 1,000 images are available with de-identification in process for the larger cohort. 7,642 admissions have radiology data. Controlled access planned. | chorus:subset:3 | Medical Imaging Dataset (DICOM)
Clinical notes extracted and tokenized using OHNLP (Open Health Natural Language Processing) toolkit following open source OHNLP schema. Stored locally at contributing sites (except tokens). Controlled access planned. De-identification achieved through tokenization approach. | chorus:subset:4 | Clinical Notes Dataset (OHNLP Tokenized)
Electroencephalography (EEG) waveform data from hospital databases in EDF+ (European Data Format) and Persyst formats. Open source EDF+ and Persyst schema metadata available. Extraction in process, planned for controlled access. | chorus:subset:5 | EEG Waveform Dataset (EDF+ and Persyst)
Subsets of the dataset currently being used for training activities (AIM-AHEAD Bridge2AI for Clinical Care Training Program) and publications as the dataset undergoes expansion and quality assurance processes. | chorus:subset:6 | Training and Publication Subset

Sampling Strategies

1. ID
     chorus:sampling:1
   Name
     Multi-center federated sampling
   Description
     Federated access enables sampling methods to ensure a balanced and diverse cohort across 20 academic centers (14 data acquisition centers). Legal framework established for collecting data at scale with sampling to ensure comprehensive sets of patient conditions and clinical treatment strategies. Community-facing ethics focus groups conducted to determine what data is appropriate for public sharing.
   Sample
     True
   Random Sampling
     False
   Representative Sample
     True
   Source Data
     - Critically ill patients in ICU, PICU, and NICU settings at 14 data acquisition centers across 20 academic centers in the United States
   Representative Verification
     - Federated multi-center data collection across 14 hospitals ensures geographic and institutional diversity; sampling for balanced and diverse patient populations; inclusion of Social Determinants of Health contextual factors

Sensitive Elements

Description | ID | Name | Sensitive Elements Present | Sensitivity Details
--- | --- | --- | --- | ---
Complete electronic health records including demographics, diagnoses, procedures, medications, nursing documentation, and clinical notes for critically ill patients. Contains protected health information subject to HIPAA and institutional privacy requirements. De-identified before release through OMOP transformation and privacy scanning tools. | chorus:sensitive:1 | Protected health information - clinical EHR data | True | Demographics and patient identifiers (de-identified before controlled access release), Diagnoses and medical conditions (OMOP standardized), Medication administration records with dosing timestamps (OMOP standardized), Procedures and clinical interventions documented by providers (OMOP standardized), Clinical notes (tokenized using OHNLP toolkit for privacy protection), Nursing flowsheet documentation at high frequency (OMOP with extensions)
Continuous waveform telemetry from bedside monitors and EEG recordings capturing detailed physiological states of critically ill patients. May reveal sensitive health conditions and treatment responses. Stored in WFDB format (telemetry) and EDF+/Persyst formats (EEG) with controlled access. | chorus:sensitive:2 | Physiological monitoring and EEG waveform data | True | Continuous cardiac waveforms from bedside monitors (WFDB format, 23 TB), Respiratory monitoring and hemodynamic measurement data, Electroencephalography (EEG) recordings from hospital databases, High-frequency physiological parameters
Diagnostic imaging studies in DICOM format from hospital PACS systems. De-identification in process to remove embedded patient information while preserving clinical utility. As of August 2025, 1,000 images available with de-id in process for larger cohort (7,642 admissions with radiology data total). | chorus:sensitive:3 | Medical imaging data | True | Radiology images (CT scans, X-rays, MRI and other modalities) in DICOM format, DICOM metadata (de-identification in process), Embedded patient information being removed through de-identification pipeline
Contextual factors including geographic information (distance to hospital) and social determinants of health data. Collected to support health equity research while maintaining patient privacy through privacy-preserving transformations. | chorus:sensitive:4 | Social Determinants of Health data | True | Geographic location information (distance to nearest hospital), Social determinants of health variables, Contextual equity factors with privacy-preserving transformations applied

Collection Mechanisms

Description | ID | Name
--- | --- | ---
Retrospective data collection from electronic health record systems at 14 data acquisition centers. Data extracted includes demographics, medication administration (dosing time-stamped upon each infusion change or dose administration), procedures, nursing flowsheets (high-frequency documentation), diagnoses, and clinical notes. Standardized to OMOP Common Data Model. | chorus:collection:1 | Retrospective EHR extraction
Continuous waveform telemetry data captured from bedside monitors through gateway and middleware systems at each contributing hospital. Stored in WFDB (WaveForm DataBase) format following extended PhysioNet schema. Contains 23 TB of waveform data as of August 2025. | chorus:collection:2 | Waveform telemetry capture
Medical imaging data acquired from hospital Picture Archiving and Communication Systems (PACS) and stored in DICOM format with comprehensive metadata following DICOM schema. 7,642 admissions have radiology data; 1,000 images currently available. | chorus:collection:3 | Medical imaging acquisition from PACS
Electroencephalography recordings extracted from hospital EEG databases in EDF+ (European Data Format) and Persyst formats with metadata following open source schemas. Extraction in process as of August 2025. | chorus:collection:4 | EEG recording extraction

Acquisition Methods

Description | ID | Name
--- | --- | ---
Demographics, medication administration (dosing time-stamped upon each infusion change or dose administration), procedures, nursing flowsheets (high-frequency documentation), and diagnoses acquired from electronic health records and standardized to OMOP Common Data Model. Controlled access with published OMOP schema metadata. Contains 1.6 billion rows of OMOP data as of August 2025. | chorus:acquisition:1 | Structured EHR data via OMOP transformation
Clinical notes extracted from EHR systems and tokenized using OHNLP (Open Health Natural Language Processing) toolkit. Stored locally at sites except for tokens. Controlled access planned with OHNLP open source schema metadata. | chorus:acquisition:2 | Clinical notes via OHNLP tokenization
Imaging data acquired from hospital PACS systems in DICOM format. De-identification in process. Planned controlled access with published DICOM schema metadata. | chorus:acquisition:3 | Medical imaging via DICOM from PACS
Bedside monitor waveform data acquired through gateway and middleware systems. Stored in WFDB format with controlled access and published PhysioNet schema (extended) metadata. 23 TB available as of August 2025. | chorus:acquisition:4 | Waveform telemetry via WFDB from bedside monitors
EEG recordings from hospital databases in EDF+ and Persyst formats. Extraction in process. Planned controlled access with open source EDF+ and Persyst schema metadata. | chorus:acquisition:5 | EEG waveforms from hospital databases

Preprocessing Strategies

Description | ID | Name | Preprocessing Details
--- | --- | --- | ---
All structured electronic health record data standardized to the OMOP (Observational Medical Outcomes Partnership) Common Data Model. Ensures interoperability and enables use of OHDSI (Observational Health Data Sciences and Informatics) tool stack for analysis. Data from all 14 acquisition centers unified through this transformation. | chorus:preproc:1 | OMOP Common Data Model transformation | Transformation of source EHR data from diverse institutional formats to OMOP CDM, Standardization of terminology and clinical codes to OMOP vocabulary standards, Mapping to OMOP vocabulary standards using validated semantic mappings, Quality assurance of transformed data against OMOP schema specifications, Integration with OHDSI tools for downstream analysis and characterization, Generation of characterization reports returned to contributing sites via CHoRUSReports
Clinical notes processed using OHNLP (Open Health Natural Language Processing) toolkit for extraction and tokenization. Protects patient privacy while enabling natural language processing and analysis of clinical text data. | chorus:preproc:2 | Clinical note tokenization via OHNLP | Text extraction from clinical notes in source EHR systems, OHNLP tokenization pipeline applied to free-text clinical documentation, De-identification of sensitive information through tokenization approach, Standardization to OHNLP open source schema, Local storage of full notes at sites; only tokens available in enclave
Waveform telemetry data from diverse bedside monitoring systems standardized to WFDB (WaveForm DataBase) format following extended PhysioNet schema. Scripts available in chorus_waveform repository. | chorus:preproc:3 | Waveform standardization to WFDB format | Conversion from proprietary bedside monitor formats using gateway/middleware systems, Standardization to WFDB format per extended PhysioNet schema, Metadata extraction and schema compliance verification, Quality checks for waveform integrity and completeness, Synchronization with clinical events from OMOP EHR data
DICOM imaging data undergoing de-identification process to remove patient identifiable information from image metadata while preserving clinical utility and image quality. | chorus:preproc:4 | Medical imaging de-identification | DICOM header de-identification to remove embedded patient information, Preservation of clinically relevant imaging metadata, DICOM schema compliance verification after de-identification, Quality assurance of de-identified images for clinical utility, Privacy scan tool (privacy_scan_tool) used for medical records privacy scanning
Data transformed using approaches that limit re-identification while maintaining analytical utility. Multiple preprocessing strategies employed to protect patient privacy across all data modalities per HIPAA and institutional requirements. | chorus:preproc:5 | Re-identification limitation transformations | Application of de-identification algorithms across all data modalities, Privacy-preserving transformations for EHR and imaging data, Geocoding via DeGauss (UF-Geocoding tool) for OMOP Location entities, Risk assessment and compliance with ethical and legal requirements, Community ethics focus group input on appropriate data for public sharing

Cleaning Strategies

Cleaning Details | Description | ID | Name
--- | --- | --- | ---
Semantic mapping validation by clinical experts using chorus-mapping repository, Standard operating protocol (SOP) implementation per Chorus_SOP documentation, Cross-site data quality checks through CHoRUSReports characterization reports, Resolution of institutional variations in coding and clinical terminology, Clinical validation SOP for contributing to mapping efforts, Site status tracking via GitHub interface and Google Form submissions | Data from 14 acquisition centers harmonized through validated semantic mappings and standard operating protocols (SOPs). Ensures consistency and interoperability across diverse institutional EHR systems and clinical practices. Mappings maintained in chorus-mapping repository with clinical validation SOP. | chorus:cleaning:1 | Multi-center data harmonization with validated semantic mappings
Schema compliance verification against OMOP CDM specifications, DICOM schema metadata validation for imaging data, WFDB/PhysioNet schema validation for waveform data, OHNLP open source schema validation for tokenized clinical notes, EDF+ and Persyst schema validation for EEG data, Documentation of schema extensions for OMOP high-frequency nursing flowsheets | All data modalities validated against published metadata schemas (OMOP, DICOM, WFDB, OHNLP, EDF+, Persyst) to ensure compliance and data quality across the multi-modal dataset. | chorus:cleaning:2 | Schema compliance validation across all modalities

Labeling Strategies

1. ID
     chorus:labeling:1
   Name
     Visualization and annotation environment for prediction targets
   Description
     Custom visualization and annotation environment developed to label data with targets important for prediction tasks in critical care AI applications. Supports labeling for characterizing acute illness, predicting complications, and measuring treatment response.
   Data Annotation Protocol
     - Interactive visualization tools for clinical data exploration
     - Annotation interface for clinical expert labeling of prediction targets
     - Labeling of targets for characterization, prediction, and treatment response tasks
     - Quality control of annotations through review processes
     - Documentation of labeling protocols per Chorus_SOP standard operating procedures

Maintainers

Description | ID | Maintainer Details | Name
--- | --- | --- | ---
Multi-institutional consortium managing dataset maintenance including 14 data acquisition centers, coordinating teams at Massachusetts General Hospital (lead), University of Florida, UT Health Science Center, and Tufts Medicine, plus infrastructure development team. Standards, Data Acquisition, and Tooling sub-teams manage ongoing data delivery and quality. Contact: cmccrary@mgh.harvard.edu (Ciera McCrary, Program Manager, MGH). | chorus:maintainer:1 | Massachusetts General Hospital (lead institution, Contact PI Eric S. Rosenthal), University of Florida (data acquisition and coordination, Azra Bihorac, Parisa Rashidi, Yulia Strekalova), UT Health Science Center / UTHealth Houston (Xiaoqian Jiang), Tufts Medicine (Andrew Ewing Williams, Manlik Kwong, Jared Houghtaling), 14 data acquisition centers across United States contributing clinical data extracts, Standards team (semantic mappings and validation via chorus-mapping repository), Data Acquisition team (extraction and contribution per Chorus_SOP), Tooling team (software development across chorus-ai GitHub organization), Project management via GitHub organization (chorus-ai) with 28 active repositories | CHoRUS Consortium
Active GitHub organization housing repositories for software, semantic mappings, standard operating protocols, and project management. 28 repositories with comprehensive documentation and community support. Licensed under MIT License (GitHub organization). | chorus:maintainer:2 | GitHub organization at https://github.com/chorus-ai, Chorus_SOP repository - centralized SOP documentation site (Apache-2.0 license), chorus-container-apps - Azure deployment infrastructure (JavaScript), chorus-mapping - semantic mappings repository, chorus_waveform - waveform documentation and conversion scripts (MIT license), privacy_scan_tool - privacy scan tool for medical records (Python), CHoRUSReports - characterization reports returned to contributing sites (R), chorus-extract-upload - tools to create and upload CHoRUS data extract (MIT license), UF-Geocoding - open source code to geocode OMOP Location entities via DeGauss, Community discussions and issue tracking for Standards and Data Acquisition teams | CHoRUS GitHub Organization (chorus-ai)

Retention Limit

ID
  chorus:retention:1
Name
  Long-term dataset retention per NIH data sharing policies
Description
  Digital data maintained according to NIH data sharing policies and institutional requirements at participating centers. Controlled access model ensures long-term availability for research while protecting patient privacy. Funded under NIH award OT2OD032701 with project end date of November 30, 2026.
Retention Details
  - NIH data sharing policies govern long-term retention requirements
  - Institutional requirements at 14 participating data acquisition centers apply
  - Controlled access model via secure enclave for ongoing privacy protection
  - Long-term maintenance through CHoRUS Consortium and associated institutions

External Resources

Description | External Resources | ID | Name
--- | --- | --- | ---
Official project website with dataset overview, team information, project components, and access instructions | https://chorus4ai.org/ | chorus:resource:1 | CHoRUS Project Website
Comprehensive GitHub organization with 28 repositories including software, documentation, SOPs, and tooling | https://github.com/chorus-ai | chorus:resource:2 | CHoRUS GitHub Organization
Centralized standard operating protocol documentation with interactive workflow diagrams for data extraction and contribution | https://github.com/chorus-ai/Chorus_SOP | chorus:resource:3 | Chorus_SOP Documentation Site
Federal grant information and project details from NIH Research Portfolio Online Reporting Tools for grant 1OT2OD032701-01 | https://reporter.nih.gov/project-details/10472824 | chorus:resource:4 | NIH RePORTER Project Details
Parent NIH Common Fund program supporting AI-ready biomedical datasets across four data generation projects | https://bridge2ai.org/, https://bridge2ai.org/chorus | chorus:resource:5 | Bridge2AI Program
Partnership with AIM-AHEAD for Bridge2AI Clinical Care Training Program (Cohort 1 and Cohort 2) providing AI/ML training for underrepresented trainees | https://aim-ahead.net/ | chorus:resource:6 | AIM-AHEAD Bridge2AI Training Program
Observational Health Data Sciences and Informatics community supporting OMOP Common Data Model used for CHoRUS structured EHR data | https://www.ohdsi.org/ | chorus:resource:7 | OHDSI Community and OMOP CDM
Peer-reviewed publication documenting CHoRUS dataset methodology and design in Neurocritical Care journal | https://doi.org/10.1007/s12028-024-02007 | chorus:resource:8 | Published Research (Neurocritical Care)

🚀

## Uses

What (other) tasks could the dataset be used for?

Tasks

Description | ID | Name
--- | --- | ---
Generate data for ML/AI applications aimed at characterizing acute and critical care illness patterns, progression, and outcomes across diverse patient populations and hospital settings. | chorus:task:1 | Characterize acute and critical care illness
Enable prediction of complications among patients with acute or critical illness using multi-modal data including structured EHR, waveforms, imaging, and clinical notes. | chorus:task:2 | Predict complications in critically ill patients
Support measurement and analysis of treatment response among critically ill patients through high-frequency documentation, medication administration records, and clinical outcomes data. | chorus:task:3 | Measure treatment response
Provision a holdout test set accessible for model external validation to aid marketplace adoption of AI-developed models for implementation in acute and critical care settings. | chorus:task:4 | External validation for AI model marketplace adoption
Utilize visualization and annotation environment to label data with targets important for prediction tasks in critical care AI applications. | chorus:task:5 | Label data for prediction targets

Intended Uses

Description | Examples | ID | Name
--- | --- | --- | ---
Primary intended use is development and training of artificial intelligence and machine learning models to characterize acute and critical care illness, predict complications, and measure treatment response in critically ill patients across diverse hospital settings. | Characterizing acute and critical care illness patterns using multi-modal data, Predicting complications (e.g., sepsis, respiratory failure) in critically ill patients, Measuring treatment response in ICU patients using medication and waveform data, Developing clinical deep learning models for critical care AI applications | chorus:use:1 | AI/ML model development for critical care
Provision of holdout test set accessible for model external validation to aid marketplace adoption of AI-developed models for implementation in acute and critical care settings. | External validation of sepsis prediction models developed at other institutions, Benchmarking AI algorithms for critical care across diverse patient populations | chorus:use:2 | External validation of AI models
Studies examining health equity, social determinants of health, and disparities in critical care outcomes across diverse patient populations and hospital settings. Dataset includes contextual factors such as geographic distance to nearest hospital. | Analysis of disparities in critical care outcomes by race, ethnicity, and geography, Research on social determinants of health in ICU patient populations | chorus:use:3 | Health equity and disparities research
Training and education of next generation of diverse academic and community AI scientists through hands-on experience with real-world critical care datasets. Integrated with AIM-AHEAD Bridge2AI for Clinical Care Training Program (Cohorts 1 and 2). | AIM-AHEAD training program for underrepresented trainees (Cohort 1: 2024-2025, Cohort 2: 2025-2026), Foundational hands-on training using Jupyter Notebooks with Bridge2AI CHoRUS ecosystem, Workshops on OHDSI/OMOP common data model and clinical AI, Development of practical use cases for AI/ML in clinical care | chorus:use:4 | Educational and training purposes for AI scientists

Discouraged Uses

Description | Discouragement Details | ID | Name
--- | --- | --- | ---
Dataset is for research purposes only. AI/ML models developed should undergo appropriate clinical validation, regulatory approval, and institutional review before use in patient care or clinical decision-making. | Models trained on CHoRUS data must undergo independent clinical validation, Regulatory approval processes (e.g., FDA clearance) required for clinical use, Institutional review board approval needed for clinical deployment | chorus:discouraged:1 | Clinical decision-making without proper validation and regulatory approval
Attempts to re-identify patients from de-identified data violate ethical principles, data use agreements, and legal frameworks established for privacy protection under HIPAA and institutional requirements. | Re-identification attempts violate the signed data use agreement, Prohibited under HIPAA and applicable institutional data privacy regulations, Data use agreement explicitly prohibits re-identification efforts | chorus:discouraged:2 | Re-identification attempts
As data collection continues through November 2026 and quality assurance processes are ongoing, early dataset versions should be used with awareness of completeness limitations and ongoing expansion (from 45K to target 100K+ admissions). | Dataset is actively growing; cohort coverage varies by data modality, EEG extraction and full imaging de-identification still in process as of 2025, Clinical notes stored locally at sites; only tokens available in enclave | chorus:discouraged:3 | Use without awareness of ongoing data collection limitations

License and Use Terms

ID
  chorus:license:1
Name
  CHoRUS Controlled Access License with Data Use Agreement
Description
  Dataset distributed under controlled access requiring institutional email registration and signed licensing agreement. Access granted after review and approval process. Participants must complete registration form with name, institutional email (not personal), and institution. Once approved, users receive email with access instructions to CHoRUS secure enclave. For training program access, program administrators assist with licensing.
License Terms
  - Institutional (.edu) email required for registration
  - All participants must sign a licensing agreement before gaining access to the dataset
  - Controlled access through secure enclave (Azure-based infrastructure)
  - Data use agreement specifies permitted research uses and prohibits re-identification
  - Access request contacts - dbold@emory.edu or jared.houghtaling@tuftsmedicine.org
  - Funded under NIH award OT2OD032701; content is solely responsibility of authors

📤

## Distribution

How will the dataset be distributed?

License
Controlled Access - Data Use Agreement Required (OT2OD032701)
🔄

## Maintenance

How will the dataset be maintained?

Updates

ID
  chorus:updates:1
Name
  Ongoing data collection and continuous expansion
Description
  Dataset updated continuously as data collection progresses at 14 acquisition centers. As of August 2025, covers 14 hospitals with over 45,000 unique admissions; current released dataset includes 50,000 patient admissions (ICU, PICU, NICU) and 1.6 billion rows of EHR OMOP data. Target exceeds 100,000 critically ill patients. Project timeline extends through November 30, 2026 (approved no-cost extension). Regular status updates tracked through GitHub project management system via GitHub interface or Google Form submissions. Sites statuses tracked in Standards Project and Data Acquisition Project.
Frequency
  Continuous updates through November 30, 2026
Update Details
  - Ongoing retrospective data collection at 14 sites through project end date
  - Current status (August 2025) - 45K+ unique admissions; 50K released (ICU, PICU, NICU)
  - Target - 100,000+ critically ill patients across 9 data modalities
  - Regular site status updates via GitHub interface or Google Form submissions
  - GitHub project tracking for deliverables and task dependencies
  - Documentation updates maintained in Chorus_SOP repository
  - Software and tooling continuous development across chorus-ai GitHub organization
  - Semantic mapping validation and expansion via chorus-mapping repository
  - EEG extraction and full imaging de-identification in progress

👥

## Human Subjects

Does the dataset relate to people?

Human Subject Research

ID
  chorus:hsr:1
Name
  CHoRUS Human Subjects Research
Description
  Retrospective data collection from critically ill patients (ICU, PICU, NICU) approved through institutional review processes at 14 data acquisition centers. Community-facing ethics focus groups conducted to determine what data is appropriate for public sharing. Legal framework established for collecting data at scale. Patient-focused efforts determine ethical and legal approaches to manage privacy and bias while accounting for Social Determinants of Health. Project includes expertise from law, ethics, health services, biomedical science, engineering, and scientific journal publications disciplines. Ethics of AI component addressed through AIM-AHEAD training curriculum (safety, risk, and legal considerations; IRB, HIPAA/GDPR compliance for OMOP/FHIR data).
Involves Human Subjects
  True
Ethics Review Board
  - Institutional review boards at 14 data acquisition centers across United States
  - Community-facing ethics focus groups determining appropriate data for public sharing
  - Legal and ethical advisory teams including law and ethics discipline experts
  - Privacy and accountability review processes per project three-pillar structure (Data, Ethics, People)
Regulatory Compliance
  - HIPAA (Health Insurance Portability and Accountability Act) compliance for protected health information
  - 45 CFR 46 (Common Rule) for human subjects research protections
  - Institutional data privacy regulations at each of the 14 contributing sites
  - NIH Common Fund Bridge2AI program ethical and trustworthy AI requirements
  - IRB protocol drafting and HIPAA/GDPR compliance guidance provided in training curriculum

Generated on 2026-04-21 15:34:01 using Bridge2AI Data Sheets Schema