PEDSnet Common Data Model - ETL Conventions


Simple item page
dc.contributor.authorPEDSnet
dc.date.accessioned2026-05-12T15:12:50Z
dc.date.created2026-04
dc.descriptionThe 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> ### **** Updated in PEDSnet CDM v6.2 **** #### No DDL Changes There are no DDL or structural schema changes between PEDSnet version 6.1 and 6.2. #### Updated Conventions ##### 1. IMO Term Mapping [CONDITION_OCCURRENCE](https://github.com/PEDSnet/Data_Models/blob/master/PEDSnet/docs/PEDSnet_CDM_ETL_Conventions.md#12-condition_occurrence-1) A clarification has been added for sites that use IMO (Intelligent Medical Objects) terminology in their source systems: - Sites should map IMO terms to the current ICD-9-CM or ICD-10-CM code(s) that were in use at the time of the `visit_start_date` for that encounter. - The original IMO term (or code) should be retained in `condition_source_value`. - **Mapping to historical ICD codes is not a site responsibility.** Study teams requiring historical code mappings may perform that mapping on demand — sites are not expected to supply it. This is a convention clarification only; no vocabulary or schema changes are required. ##### 2. New Cohort Definition [COHORT_DEFINITION](https://github.com/PEDSnet/Data_Models/blob/master/PEDSnet/docs/PEDSnet_CDM_ETL_Conventions.md#124-cohort_definition) A new cohort definition has been added to the DCC-maintained `cohort_definition` table: | cohort_definition_id | cohort_definition_name | cohort_definition_description | definition_type_concept_id | cohort_initiation_date | |---|---|---|---|---| | 2000001561 | USDHub v1 | Meets inclusion criteria for v1 USDHub cohort | 44807982 (Cohort) | 9/1/2025 | ##### 3. Pain Scale Inclusion [MEASUREMENT](https://github.com/PEDSnet/Data_Models/blob/master/PEDSnet/docs/PEDSnet_CDM_ETL_Conventions.md#112-measurement-1) Starting in v6.2, sites will pilot the inclusion of pain scales in the measurement table with intent to refine in the following cycles. 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 - FLACC (Face, Legs, Activity, Cry, Consolability) total score - FLACC component scores, if available - (Wong-Baker) FACES pain scale For v6.2, we are only requesting the scales listed above for all visits where available. As this is a pilot and to simplify ETL, we are not asking that sites standardize result values unless the numeric score is easily extractable. 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/blob/master/PEDSnet/docs/PEDSnet_CDM_ETL_Conventions.md#112-measurement-1) table for specific guidance on how to populate the Measurement table with pain scale data. --- ### **** Reminders **** #### Drug Metadata — Priority Fields for v6.2 Submission For the v6.2 submission cycle, sites are asked to prioritize completeness for the following fields in [DRUG_EXPOSURE](https://github.com/PEDSnet/Data_Models/blob/master/PEDSnet/docs/PEDSnet_CDM_ETL_Conventions.md#111-drug-exposure) where source data is available: ##### 1. Dose Unit (`dose_unit_concept_id` / `dose_unit_source_value`) - Populate `dose_unit_concept_id` with the appropriate UCUM concept for the unit of the administered or prescribed dose. - Retain the original source unit string in `dose_unit_source_value`. ##### 2. End Dates and Duration (`drug_exposure_end_date` / `days_supply`) - Populate `drug_exposure_end_date` when an end date is available in the source system. - Populate `days_supply` when a days-supply value is available (particularly for outpatient prescriptions). - When only a start date is available, calculate `drug_exposure_end_date` as `drug_exposure_start_date + days_supply - 1` where possible.
dc.description.abstractThis 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.2 or PEDSnet Database 2026-07.
dc.identifier.urihttps://hdl.handle.net/20.500.14642/749.13
dc.publisherPEDSnet
dc.relation.urihttps://github.com/PEDSnet/Data_Models_Public/blob/master/PEDSnet/docs/Conventions%20Docs/v6.2_PEDSnet_CDM_ETL_Conventions.md
dc.rightsa CC-BY Attribution 4.0 License.
dc.rights.urihttp://creativecommons.org/licenses/by/4.0
dc.subjectPEDSnet Data Source
dc.subjectETL Specifications
dc.titlePEDSnet Common Data Model - ETL Conventions
dc.typeOther
dspace.entity.typeDocumentation
relation.isDocumentationOfDocumentationb305fdbf-6f8d-4ba6-af9c-7cd29f9ad26d
relation.isDocumentationOfDocumentationd0698db8-b7bd-4fa1-b9be-fb45d0098f52
relation.isDocumentationOfDocumentation.latestForDiscoveryb305fdbf-6f8d-4ba6-af9c-7cd29f9ad26d
relation.isOrgUnitOfDocumentationa118440c-013c-4d44-b7ce-19a9b1441304
relation.isOrgUnitOfDocumentationcdb3cef9-ebdd-4ca8-9000-14573ba301bf
relation.isOrgUnitOfDocumentationc8e42b1c-6ffb-4b73-b893-ae4b5fe07dfa
relation.isOrgUnitOfDocumentationcc4d0004-ec82-4d55-8a8d-61a3b0e7a09a
relation.isOrgUnitOfDocumentationda598fc2-bed7-4a0d-92d7-fc2517b715de
relation.isOrgUnitOfDocumentation32f633d4-ee75-467f-a1a2-24c207244346
relation.isOrgUnitOfDocumentation751635c0-bac7-47e0-95ea-c78f3cb31390
relation.isOrgUnitOfDocumentationf17f740b-c35e-4a0e-9d83-7e051d0c64c5
relation.isOrgUnitOfDocumentationff3cd76b-cf4c-44c1-84a6-368cfd0e9123
relation.isOrgUnitOfDocumentation4a9c59a3-af72-449e-b5c0-2db953ff475a
relation.isOrgUnitOfDocumentation.latestForDiscoverya118440c-013c-4d44-b7ce-19a9b1441304

Files

Original bundle

Now showing 1 - 1 of 1
Thumbnail Image
Name:
ETL Conventions for use with PEDSnet CDM v6.2 OMOP V5.4.pdf
Size:
2.85 MB
Format:
Adobe Portable Document Format
Download

License bundle

Now showing 1 - 1 of 1
Thumbnail Image
Name:
license.txt
Size:
1.71 KB
Format:
Item-specific license agreed to upon submission
Description:
Download

Domains

Data Architecture

Version History

Now showing 1 - 10 of 11
VersionDateSummary
13*
 2026-05-12 11:09:07
Version 6.2 of the PEDSnet CDM ETL Conventions
12
 2026-02-02 16:00:01
Version 6.1 of the PEDSnet CDM ETL Conventions
11
 2026-02-02 15:37:26
Version 6.0 of the PEDSnet CDM ETL Conventions
9
 2025-07-16 12:29:21
Version 5.9 of the PEDSnet CDM ETL Conventions
8
 2025-07-16 12:22:41
Version 5.8 of the PEDSnet CDM ETL Conventions
7
 2025-03-11 10:39:21
Version 5.7 of the PEDSnet CDM ETL Conventions
6
 2024-11-15 10:52:12
Version 5.6 of the PEDSnet CDM ETL Conventions
5
 2024-08-13 15:01:37
Version 5.5 of the PEDSnet CDM ETL Conventions
4
 2024-08-13 14:58:18
Version 5.4 of the PEDSnet CDM ETL Conventions
3
 2024-08-13 14:53:47
Version 5.3 of the PEDSnet CDM ETL Conventions
* Selected version