Created
Submission Date
Data Collection
Files
Tags
This document provides the ETL processing assumptions and conventions developed by the PEDSnet data partners that a data partner should use to ensure common ETL business rules. This record documents the changes for v6.3 or PEDSnet Database 2026-10.
Creator
Affiliation(s)
Provenance
Description
The PEDSnet Common Data Model is an evolving specification, based in structure on the OMOP Common Data Model, but expanded to accommodate requirements of both the PCORnet® Common Data Model and the primary research cohorts established in PEDSnet. This version of the PEDSnet CDM reflects the ETL processes developed after several iterations of network development. As such, it proposes to align with the current version of the PCORnet® CDM.
This document provides the ETL processing assumptions and conventions developed by the PEDSnet data partners that a data partner should use to ensure common ETL business rules. This document will be modified as new situations are identified, incorrect business rules are identified and replaced, as new analytic use cases impose new/different ETL rules, and as the PEDSnet CDM continues to evolve.
**** NEW in PEDSnet CDM v6.3 ****
1. condition_type_concept_id — CONDITION_OCCURRENCE
In PEDSnet v6.2 and prior, the condition_type_concept_id holds 3 dimensions: care setting, priority, and type of diagnosis.
Starting in v6.3, care setting should be removed from condition_type_concept_id and priority should be moved to condition_status_concept_id. This change impacts the expected value sets for both the condition_type_concept_id and condition_status_concept_id fields, as detailed below:
- Care Setting
- No longer to be contained in the
condition_type_concept_idfield - In analytics, will be obtained using linkage to visit_occurrence/visit_detail through
visit_(detail)_concept_id
- No longer to be contained in the
- Priority
- Should now be contained in
condition_status_concept_id - The full list of potential values for
condition_status_concept_idcan be found in the vocabularywhere vocabulary_id = 'Condition Status' - Prioritize mapping to a concept differentiating between primary/secondary for final diagnosis, admitting diagnoses are optional but a concept ID is provided below if you wish to include these:
- 32890 = Admission diagnosis
- 32902 = Primary Diagnosis *
- 32908 = Secondary Diagnosis *
* For outpatient or discharge diagnoses
- Should now be contained in
- Type of Diagnosis
- Should remain in
condition_type_concept_id - The full list of potential
condition_type_concept_idscan be found in the vocabulary tablewhere domain_id = 'Type Concept' and vocabulary_id = 'Type Concept' and standard_concept = 'S' - Prioritize differentiating between provider and hospital billing, clinician ordered, and problem list diagnoses:
- 32874 = Provider billing
- 32852 = Facility/hospital billing
- 32833 = Clinician order
- 32840 = EHR Problem List Entry
- Should remain in
The DCC will add a step to standardize this in the pipeline in the event sites are unable to make this change in their ETL process.
2. Pain Scale Inclusion — MEASUREMENT
Starting in v6.3, all sites are expected to include pain scales in the measurement table. This request is driven by the INSPIRE study, which is focused on identifying patients with pediatric chronic primary pain.
The study team is interested in the following pain scales:
- Numeric pain score (Identified as a priority for the study)
- FLACC (Face, Legs, Activity, Cry, Consolability) total score
- FLACC component scores, if available
- (Wong-Baker) FACES pain scale
- Other pain scores (not listed above)
All pain scores are expected to have something in value_source_value, which could be a numeric value (even if the value is 0), a numeric value with an operator, and/or a string.
Please see Note 8 under the Measurement table for specific guidance on how to populate the Measurement table with pain scale data.
**** Convention Clarifications/Reminders ****
1. All date/datetime fields should be reported using the site’s local time without attributing a timezone
Datetime fields in particular have a datatype of ‘TIMESTAMP WITHOUT TIME ZONE’, please ensure you are not including a time zone in your data submission and use the local time of your site (not UTC or similar).
2. Domain_id fields should contain a string in sentence case
The domain_id field in the specialty and location_history tables should be a string value, not numeric. We are also requesting that sites use sentence case (first letter capitalized only) to better align with OMOP. For example: ‘Person’, ‘Provider’, ‘Care site’
The DCC will add a step to standardize this in the pipeline in the event sites are unable to make this change in their ETL process.
3. Drug Metadata Priorities — DRUG_EXPOSURE
Sites should continue to prioritize the following drug metadata fields for the v6.3 submission cycle if not yet fully implemented:
- Dose Unit (
dose_unit_concept_id/dose_unit_source_value) - End dates / Duration (
drug_exposure_end_date/days_supply/frequency)
No new fields have been added; this is a priority callout to improve data completeness across the network.
4. Mental and Behavioral Health Data
There is no expectation of any changes being made for this version, but sites should begin investigating the following items relating to mental and behavioral heath (MBH) data:
- Begin to look into how MBH services are recorded
- What visit types, what providers, etc., and how to get those in the PEDSnet data
- Investigate the governance of sensitive MBH data, and whether our existing desensitization process covers your site’s needs
Related Resources
Vocabulary
Creative Commons license
Version History
| Version | Date | Summary |
|---|---|---|
14* | 2026-11-04 12:49:13 | Version 6.3 of the PEDSnet CDM ETL Conventions |
| 2026-05-12 11:09:07 | Version 6.2 of the PEDSnet CDM ETL Conventions | |
| 2026-02-02 16:00:01 | Version 6.1 of the PEDSnet CDM ETL Conventions | |
| 2026-02-02 15:37:26 | Version 6.0 of the PEDSnet CDM ETL Conventions | |
| 2025-07-16 12:29:21 | Version 5.9 of the PEDSnet CDM ETL Conventions | |
| 2025-07-16 12:22:41 | Version 5.8 of the PEDSnet CDM ETL Conventions | |
| 2025-03-11 10:39:21 | Version 5.7 of the PEDSnet CDM ETL Conventions | |
| 2024-11-15 10:52:12 | Version 5.6 of the PEDSnet CDM ETL Conventions | |
| 2024-08-13 15:01:37 | Version 5.5 of the PEDSnet CDM ETL Conventions | |
| 2024-08-13 14:58:18 | Version 5.4 of the PEDSnet CDM ETL Conventions |