PEDSnet Common Data Model - ETL Conventions
| dc.contributor.author | PEDSnet Data Coordinating Center |
| dc.date.accessioned | 2026-11-04T17:55:40Z |
| dc.date.created | 2026-07 |
| dc.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. <br><br> #### **** NEW in PEDSnet CDM v6.3 **** ##### 1. condition_type_concept_id — [CONDITION_OCCURRENCE](https://github.com/PEDSnet/Data_Models_Public/blob/master/PEDSnet/docs/v6.3_PEDSnet_CDM_ETL_Conventions.md#12-condition_occurrence-1) 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_id` field - In analytics, will be obtained using linkage to visit_occurrence/visit_detail through `visit_(detail)_concept_id` - **Priority** - Should now be contained in `condition_status_concept_id` - The full list of potential values for `condition_status_concept_id` can be found in the vocabulary **`where 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 - **Type of Diagnosis** - Should remain in `condition_type_concept_id` - The full list of potential `condition_type_concept_ids` can be found in the vocabulary table **`where 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 > 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](https://github.com/PEDSnet/Data_Models_Public/blob/master/PEDSnet/docs/v6.3_PEDSnet_CDM_ETL_Conventions.md#112-measurement-1) 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](https://github.com/PEDSnet/Data_Models_Public/blob/master/PEDSnet/docs/v6.3_PEDSnet_CDM_ETL_Conventions.md#112-measurement-1) 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](https://github.com/PEDSnet/Data_Models_Public/blob/master/PEDSnet/docs/v6.3_PEDSnet_CDM_ETL_Conventions.md#121-specialty-1) and [location_history](https://github.com/PEDSnet/Data_Models_Public/blob/master/PEDSnet/docs/v6.3_PEDSnet_CDM_ETL_Conventions.md#119-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](https://github.com/PEDSnet/Data_Models_Public/blob/master/PEDSnet/docs/v6.3_PEDSnet_CDM_ETL_Conventions.md#111-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 |
| dc.description.abstract | 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. |
| dc.identifier.uri | https://hdl.handle.net/20.500.14642/749.14 |
| dc.publisher | PEDSnet |
| dc.relation.uri | https://github.com/PEDSnet/Data_Models_Public |
| dc.rights | a CC-BY Attribution 4.0 License. |
| dc.rights.uri | http://creativecommons.org/licenses/by/4.0 |
| dc.subject | ETL Specifications |
| dc.subject | Database Access |
| dc.title | PEDSnet Common Data Model - ETL Conventions |
| dc.type | Other |
| dspace.entity.type | Documentation |
| local.code.github | https://github.com/PEDSnet/Data_Models_Public/blob/master/PEDSnet/docs/Conventions%20Docs/v6.2_PEDSnet_CDM_ETL_Conventions.md |
| relation.isDocumentationOfDocumentation | 676a790b-cf6a-4a68-afc3-95f8cdfccc8c |
| relation.isDocumentationOfDocumentation.latestForDiscovery | b305fdbf-6f8d-4ba6-af9c-7cd29f9ad26d |
| relation.isOrgUnitOfDocumentation | a118440c-013c-4d44-b7ce-19a9b1441304 |
| relation.isOrgUnitOfDocumentation | cdb3cef9-ebdd-4ca8-9000-14573ba301bf |
| relation.isOrgUnitOfDocumentation | c8e42b1c-6ffb-4b73-b893-ae4b5fe07dfa |
| relation.isOrgUnitOfDocumentation | cc4d0004-ec82-4d55-8a8d-61a3b0e7a09a |
| relation.isOrgUnitOfDocumentation | da598fc2-bed7-4a0d-92d7-fc2517b715de |
| relation.isOrgUnitOfDocumentation | 32f633d4-ee75-467f-a1a2-24c207244346 |
| relation.isOrgUnitOfDocumentation | 751635c0-bac7-47e0-95ea-c78f3cb31390 |
| relation.isOrgUnitOfDocumentation | f17f740b-c35e-4a0e-9d83-7e051d0c64c5 |
| relation.isOrgUnitOfDocumentation | ff3cd76b-cf4c-44c1-84a6-368cfd0e9123 |
| relation.isOrgUnitOfDocumentation | 4a9c59a3-af72-449e-b5c0-2db953ff475a |
| relation.isOrgUnitOfDocumentation.latestForDiscovery | a118440c-013c-4d44-b7ce-19a9b1441304 |
Files
Domains
Version History
You are currently viewing version 14 of the item.
1 - 10 of 12
| 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 |
* Selected version
