Top

PEDSnet v1

Tables

care_site

Information about the site of care

Fields

care_site_id

A unique identifier for each defined location of care within an organization. Here, an organization is defined as a collection of one or more care sites that share a single EHR database.

Schema
Mappings
Model Table Field Comment
OMOP v4 care_site care_site_id
Inbound References

Total: 3

Table Field Name
person care_site_id fpk_person_care_site
provider care_site_id fpk_provider_care_site
visit_occurrence care_site_id fpk_visit_care_site

care_site_source_value

The identifier for the organization in the source data, stored here for reference.

Schema
Mappings
Model Table Field Comment
OMOP v4 care_site care_site_source_value

location_id

Refers to: location / location_id

A foreign key to the geographic location of the administrative offices of the organization in the location table, where the detailed address information is stored.

Schema
Mappings
Model Table Field Comment
OMOP v4 care_site location_id

organization_id

Refers to: organization / organization_id

A foreign key to the organization record.

Schema
Mappings
Model Table Field Comment
OMOP v4 care_site organization_id

place_of_service_concept_id

A foreign key that refers to a place of service concept identifier in the Vocabulary

Schema
Mappings
Model Table Field Comment
OMOP v4 care_site place_of_service_concept_id

place_of_service_source_value

The source code for the place of service as it appears in the source data, stored here for reference.

Schema
Mappings
Model Table Field Comment
OMOP v4 care_site place_of_service_source_value

concept

Contains all Concepts across domains, including the name (description), their source (called Concept Type), their identifier in the source (called Source Code), their level in the hierarchy and their class.

Fields

concept_class

The category or class of the concept along both the hierarchical tree as well as different domains within a vocabulary. Examples are “Clinical Drug”, “Ingredient”, “Clinical Finding” etc.

Schema

concept_code

The concept code represents the identifier of the concept in the source data it originates from, such as SNOMED-CT concept IDs, RxNorm RXCUIs etc. Note that concept codes are not unique across vocabularies.

Schema
Mappings
Model Table Field Comment
PCORnet v1 encounter drg Explicitly maps to concept_id 3040646.

concept_id

A system-generated unique identifier for each concept across all domains.

Schema
Inbound References

Total: 6

Table Field Name
concept_ancestor ancestor_concept_id fpk_concept_ancestor_concept_1
concept_ancestor descendant_concept_id fpk_concept_ancestor_concept_2
concept_relationship concept_id_1 fpk_concept_relationship_c_1
concept_relationship concept_id_2 fpk_concept_relationship_c_2
concept_synonym concept_id fpk_concept_synonym_concept
source_to_concept_map target_concept_id fpk_source_to_concept_map_c_1

concept_level

The level of hierarchy associated with the concept. Different concept levels are assigned to concepts to depict their seniority in a clearly defined hierarchy, such as drugs, conditions, etc. A concept level of 0 is assigned to concepts that are not part of a standard vocabulary, but are part of the vocabulary for reference purposes (e.g. drug form).

Schema

concept_name

An unambiguous, meaningful and descriptive name for the concept.

Schema

invalid_reason

Reason the concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.

Schema

valid_end_date

The date when the concept became invalid because it was deleted or superseded (updated) by a new concept. The default value is 31-Dec-2099.

Schema

valid_start_date

The date when the concept was first recorded.

Schema

vocabulary_id

Refers to: vocabulary / vocabulary_id

A foreign key to the vocabulary table indicating from which source the concept has been adapted.

Schema

concept_ancestor

Contains the ancestry relationship of Concepts that have one or several hierarchical Relationships among them for fast lookup of hierarchical tree information, such as drug classes.

Fields

ancestor_concept_id

Refers to: concept / concept_id

A foreign key to the concept code in the concept table for the higher-level concept that forms the ancestor in the relationship.

Schema

descendant_concept_id

Refers to: concept / concept_id

A foreign key to the concept code in the concept table for the lower-level concept that forms the descendant in the relationship.

Schema

max_levels_of_separation

The maximum separation in number of levels of hierarchy between ancestor and descendant concepts. This is an optional attribute that is used to simplify hierarchic analysis.

Schema

min_levels_of_separation

The minimum separation in number of levels of hierarchy between ancestor and descendant concepts. This is an optional attribute that is used to simplify hierarchic analysis.

Schema

concept_relationship

Contains the Relationship between any two Concepts and the type of the Relationship.

Fields

concept_id_1

Refers to: concept / concept_id

A foreign key to the concept in the concept table associated with the relationship. Relationships are directional, and this field represents the source concept designation.

Schema

concept_id_2

Refers to: concept / concept_id

A foreign key to the concept in the concept table associated with the relationship. Relationships are directional, and this field represents the destination concept designation.

Schema

invalid_reason

Reason the relationship was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.

Schema

relationship_id

Refers to: relationship / relationship_id

The type of relationship as defined in the relationship table.

Schema

valid_end_date

The date when the relationship became invalid because it was deleted or superseded (updated) by a new relationship. Default value is 31-Dec-2099.

Schema

valid_start_date

The date when the instance of the relationship is first recorded.

Schema

concept_synonym

Contains any number of synonymous names (descriptions) for the Concepts.

Fields

concept_id

Refers to: concept / concept_id

A foreign key to the concept in the concept table.

Schema

concept_synonym_id

A system-generated unique identifier for each concept synonym.

Schema

concept_synonym_name

The alternative name for the concept.

Schema

condition_occurrence

A diagnosis or condition that has been recorded about a person at a certain time

Fields

associated_provider_id

Refers to: provider / provider_id

A foreign key to the provider in the provider table who was responsible for determining (diagnosing) the condition.

Schema
Mappings
Model Table Field Comment
OMOP v4 condition_occurrence associated_provider_id

condition_concept_id

A foreign key that refers to a standard condition concept identifier in the Vocabulary.

Schema
Mappings
Model Table Field Comment
PCORnet v1 diagnosis dx
OMOP v4 condition_occurrence condition_concept_id

condition_end_date

The date when the instance of the condition is considered to have ended. If this information is not available, set to NULL.

Schema
Mappings
Model Table Field Comment
OMOP v4 condition_occurrence condition_end_date

condition_occurrence_id

A unique identifier for each condition occurrence event.

Schema
Mappings
Model Table Field Comment
OMOP v4 condition_occurrence condition_occurrence_id

condition_source_value

The source code for the condition as it appears in the source data. This code is mapped to a standard condition concept in the Vocabulary and the original code is, stored here for reference. Condition source codes are typically ICD-9-CM diagnosis codes from medical claims or discharge status/visit diagnosis codes from EHRs.

Schema
Mappings
Model Table Field Comment
OMOP v4 condition_occurrence condition_source_value

condition_start_date

The date when the instance of the condition is recorded.

Schema
Mappings
Model Table Field Comment
OMOP v4 condition_occurrence condition_start_date

condition_type_concept_id

A foreign key to the predefined concept identifier in the Vocabulary reflecting the source data from which the condition was recorded, the level of standardization, and the type of occurrence. For example, conditions may be defined as primary or secondary diagnoses, problem lists and person statuses.

Schema
Mappings
Model Table Field Comment
OMOP v4 condition_occurrence condition_type_concept_id

person_id

Refers to: person / person_id

A foreign key identifier to the person who is experiencing the condition. The demographic details of that person are stored in the person table.

Schema
Mappings
Model Table Field Comment
PCORnet v1 diagnosis patid
OMOP v4 condition_occurrence person_id

stop_reason

The reason, if available, that the condition was no longer recorded, as indicated in the source data. Valid values include discharged, resolved, etc. Note that a stop_reason does not necessarily imply that the condition is no longer occurring.

Schema
Mappings
Model Table Field Comment
OMOP v4 condition_occurrence stop_reason

visit_occurrence_id

Refers to: visit_occurrence / visit_occurrence_id

A foreign key to the visit in the visit table during which the condition was determined (diagnosed).

Schema
Mappings
Model Table Field Comment
PCORnet v1 diagnosis encounterid
OMOP v4 condition_occurrence visit_occurrence_id

death

Time and cause of death of the Person

Fields

cause_of_death_concept_id

A foreign key referring to a standard concept identifier in the Vocabulary for conditions.

Schema
Mappings
Model Table Field Comment
OMOP v4 death cause_of_death_concept_id

cause_of_death_source_value

The source code for the cause of death as it appears in the source data. This code is mapped to a standard concept in the Vocabulary and the original code is, stored here for reference.

Schema
Mappings
Model Table Field Comment
OMOP v4 death cause_of_death_source_value

death_date

The date the person was deceased. If the precise date including day or month is not known or not allowed, December is used as the default month, and the last day of the month the default day. If no date available, use date recorded as deceased.

Schema
Mappings
Model Table Field Comment
OMOP v4 death death_date

death_type_concept_id

A foreign key referring to the predefined concept identifier in the Vocabulary reflecting how the death was represented in the source data.

Schema
Mappings
Model Table Field Comment
OMOP v4 death death_type_concept_id

person_id

Refers to: person / person_id

A foreign key identifier to the deceased person. The demographic details of that person are stored in the person table.

Schema
Mappings
Model Table Field Comment
OMOP v4 death person_id

drug_approval

Fields

approval_date

Schema

approved_by

Schema

ingredient_concept_id

Schema

drug_strength

Fields

amount_unit

Schema

amount_value

Schema

concentration_denom_unit

Schema

concentration_enum_unit

Schema

concentration_value

Schema

drug_concept_id

Schema

ingredient_concept_id

Schema

invalid_reason

Schema

valid_end_date

Schema

valid_start_date

Schema

location

Physical addresses of patients, organizations and care sites

Fields

address_1

Optional - Do not transmit to DCC

Schema
Mappings
Model Table Field Comment
OMOP v4 location address_1

address_2

Optional - Do not transmit to DCC

Schema
Mappings
Model Table Field Comment
OMOP v4 location address_2

city

Optional - Do not transmit to DCC

Schema
Mappings
Model Table Field Comment
OMOP v4 location city

county

Optional - Do not transmit to DCC

Schema
Mappings
Model Table Field Comment
OMOP v4 location county

location_id

A unique identifier for each geographic location.

Schema
Mappings
Model Table Field Comment
OMOP v4 location location_id
Inbound References

Total: 3

Table Field Name
care_site location_id fpk_care_site_location
organization location_id fpk_organization_location
person location_id fpk_person_location

location_source_value

The verbatim information that is used to uniquely identify the location as it appears in the source data.

Schema
Mappings
Model Table Field Comment
OMOP v4 location location_source_value

state

The state field as it appears in the source data.

Schema
Mappings
Model Table Field Comment
OMOP v4 location state

zip

The zip code. For US addresses, valid zip codes can be 3, 5 or 9 digits long, depending on the source data.

Schema
Mappings
Model Table Field Comment
PCORnet v1 encounter facility_location
OMOP v4 location zip

observation

Observations are clinical facts, such as laboratory tests, signs/symptoms, which are not captured within other CDM tables

Fields

associated_provider_id

Refers to: provider / provider_id

A foreign key to the provider in the provider table who was responsible for making the observation.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation associated_provider_id

observation_concept_id

A foreign key to the standard observation concept identifier in the Vocabulary.

Schema
Mappings
Model Table Field Comment
PCORnet v1 vital bp_position Maps to the concept_id values under the ���BP Position�۝ concept class.
OMOP v4 observation observation_concept_id

observation_date

The date of the observation. In order to reduce ambiguity around timezone shifts, this field is stored and transmitted as a full date and time. Enter as much information as is available.

Schema
Mappings
Model Table Field Comment
PCORnet v1 vital measure_date
OMOP v4 observation observation_date

observation_id

A unique identifier for each observation.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation observation_id

observation_source_value

The observation code as it appears in the source data. This code is mapped to a standard concept in the Vocabulary and the original code is, stored here for reference.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation observation_source_value

observation_time

The time of the observation. In order to reduce ambiguity around timezone shifts, this field is stored and transmitted as a full date and time. Enter as much information as is available.

Schema
Mappings
Model Table Field Comment
PCORnet v1 vital measure_time
OMOP v4 observation observation_time

observation_type_concept_id

A foreign key to the predefined concept identifier in the Vocabulary reflecting the type of the observation.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation observation_type_concept_id

person_id

Refers to: person / person_id

A foreign key identifier to the person about whom the observation was recorded. The demographic details of that person are stored in the person table.

Schema
Mappings
Model Table Field Comment
PCORnet v1 vital patid
OMOP v4 observation person_id

range_high

The upper limit of the normal range of the observation. It is not applicable if the observation results are non-numeric or categorical, and must be in the same units of measure as the observation value. Optional - Do not transmit to DCC.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation range_high

range_low

The lower limit of the normal range of the observation. It is not applicable if the observation results are non-numeric or categorical, and must be in the same units of measure as the observation value. Optional - Do not transmit to DCC.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation range_low

relevant_condition_concept_id

A foreign key to the condition concept related to this observation, if this relationship exists in the source data (e.g. indication for a diagnostic test).

Schema
Mappings
Model Table Field Comment
OMOP v4 observation relevant_condition_concept_id

unit_concept_id

A foreign key to a standard concept identifier of measurement units in the Vocabulary.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation unit_concept_id

unit_source_value

The source code for the unit as it appears in the source data. This code is mapped to a standard unit concept in the Vocabulary and the original code is, stored here for reference.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation unit_source_value

value_as_concept_id

A foreign key to an observation result stored as a concept identifier. This is applicable to observations where the result can be expressed as a standard concept from the Vocabulary (e.g., positive/negative, present/absent, low/high, etc.).

Schema
Mappings
Model Table Field Comment
PCORnet v1 demographic biobank_flag Explicitly maps to concept_id 4001345 in the ���Biobank_flag�۝ concept class.
PCORnet v1 encounter discharge_disposition Explicitly maps to concept_id 44813951 in the ���Discharge Disposition�۝ concept class.
PCORnet v1 encounter discharge_status Explicitly maps to concept_id 4137274 in the ���Discharge Status�۝ concept class.
PCORnet v1 encounter admitting_source Explicitly maps to concept_id 4145666 in the ���Admitting Source�۝ concept class.
PCORnet v1 encounter raw_discharge_disposition
PCORnet v1 encounter raw_discharge_status
PCORnet v1 encounter raw_admitting_source
PCORnet v1 enrollment chart Explicitly maps to concept_id 4030450 in the ���Chart Availability�۝ concept class.
OMOP v4 observation value_as_concept_id

value_as_number

The observation result stored as a number. This is applicable to observations where the result is expressed as a numeric value.

Schema
Mappings
Model Table Field Comment
PCORnet v1 vital ht Explicitly maps to concept_id 3036277.
PCORnet v1 vital wt Explicitly maps to concept_id 3025315.
PCORnet v1 vital original_bmi Explicitly maps to concept_id 3038553.
PCORnet v1 vital diastolic Explicitly maps to concept_id 3012888.
PCORnet v1 vital systolic Explicitly maps to concept_id 3004249.
OMOP v4 observation value_as_number

value_as_string

The observation result stored as a string. This is applicable to observations where the result is expressed as verbatim text.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_string

visit_occurrence_id

Refers to: visit_occurrence / visit_occurrence_id

A foreign key to the visit in the visit table during which the observation was recorded.

Schema
Mappings
Model Table Field Comment
PCORnet v1 vital encounterid
OMOP v4 observation visit_occurrence_id

observation_period

Time intervals during which health care information, such as drugs, conditions, and other clinical observations, may be available

Fields

observation_period_end_date

The end date of the observation period for which data are available from the source.

Schema
Mappings
Model Table Field Comment
PCORnet v1 enrollment enr_end_date
OMOP v4 observation_period observation_period_end_date

observation_period_id

A system-generate unique identifier for each observation period

Schema
Mappings
Model Table Field Comment
OMOP v4 observation_period observation_period_id

observation_period_start_date

The start date of the observation period for which data are available from the data source

Schema
Mappings
Model Table Field Comment
PCORnet v1 enrollment enr_start_date
OMOP v4 observation_period observation_period_start_date

person_id

Refers to: person / person_id

A foreign key identifier to the person who is experiencing the condition. The demographic details of that person are stored in the person table.

Schema
Mappings
Model Table Field Comment
PCORnet v1 enrollment patid
OMOP v4 observation_period person_id

organization

Information about health care organizations

Fields

location_id

Refers to: location / location_id

A foreign key to the geographic location of the administrative offices of the organization in the location table, where the detailed address information is stored.

Schema
Mappings
Model Table Field Comment
OMOP v4 organization location_id

organization_id

A unique identifier for each defined location of care within an organization. Here, an organization is defined as a collection of one or more care sites that share a single EHR database.

Schema
Mappings
Model Table Field Comment
OMOP v4 organization organization_id
Inbound References

Total: 1

Table Field Name
care_site organization_id fpk_care_site_organization

organization_source_value

The identifier for the organization in the source data, stored here for reference

Schema
Mappings
Model Table Field Comment
OMOP v4 organization organization_source_value

place_of_service_concept_id

A foreign key that refers to a place of service concept identifier in the Vocabulary

Schema
Mappings
Model Table Field Comment
OMOP v4 organization place_of_service_concept_id

place_of_service_source_value

The source code for the place of service as it appears in the source data, stored here for reference.

Schema
Mappings
Model Table Field Comment
OMOP v4 organization place_of_service_source_value

person

Demographic information about a Person

Fields

care_site_id

Refers to: care_site / care_site_id

A foreign key to the site of primary care in the care_site table, where the details of the care site are stored

Schema
Mappings
Model Table Field Comment
OMOP v4 person care_site_id

day_of_birth

The day of the month of birth of the person. For data sources that provide the precise date of birth, the day is extracted and stored in this field.

Schema
Mappings
Model Table Field Comment
PCORnet v1 demographic birth_date
OMOP v4 person day_of_birth

ethnicity_concept_id

A foreign key that refers to the standard concept identifier in the Vocabulary for the ethnicity of the person.

Schema
Mappings
Model Table Field Comment
PCORnet v1 demographic hispanic Limited to the concept_id values under the ���Hispanic�۝ concept class.
OMOP v4 person ethnicity_concept_id

ethnicity_source_value

The source code for the ethnicity of the person as it appears in the source data. The person ethnicity is mapped to a standard ethnicity concept in the Vocabulary and the original code is, stored here for reference.

Schema
Mappings
Model Table Field Comment
PCORnet v1 demographic raw_hispanic
OMOP v4 person ethnicity_source_value

gender_concept_id

A foreign key that refers to a standard concept identifier in the Vocabulary for the gender of the person.

Schema
Mappings
Model Table Field Comment
PCORnet v1 demographic sex Maps to the concept_id values under the ���Gender�۝ concept class.
OMOP v4 person gender_concept_id

gender_source_value

The source code for the gender of the person as it appears in the source data. The person’s gender is mapped to a standard gender concept in the Vocabulary; the original value is stored here for reference.

Schema
Mappings
Model Table Field Comment
PCORnet v1 demographic raw_sex
OMOP v4 person gender_source_value

location_id

Refers to: location / location_id

A foreign key to the place of residency (ZIP code) for the person in the location table, where the detailed address information is stored.

Schema
Mappings
Model Table Field Comment
OMOP v4 person location_id

month_of_birth

The month of birth of the person. For data sources that provide the precise date of birth, the month is extracted and stored in this field.

Schema
Mappings
Model Table Field Comment
PCORnet v1 demographic birth_date
OMOP v4 person month_of_birth

person_id

A unique identifier for each person; this is created by each contributing site. Note: This is not a value found in the EHR. However, a map to patient ID or MRN from the EHR must be kept at the site and not shared with the data coordinating center for re-identification in the future.

Schema
Mappings
Model Table Field Comment
PCORnet v1 demographic patid
OMOP v4 person person_id
Inbound References

Total: 6

Table Field Name
condition_occurrence person_id fpk_condition_person
death person_id fpk_death_person
observation person_id fpk_observation_person
observation_period person_id fpk_observation_period_person
procedure_occurrence person_id fpk_procedure_person
visit_occurrence person_id fpk_visit_person

person_source_value

An encrypted key derived from the person identifier in the source data. For site-specific data extracts, this may be identical to the person_id.

Schema

pn_gestational_age

The post-menstrual age in weeks of the person at birth, if known.

Schema

pn_time_of_birth

The time of birth at the birthday. In order to reduce ambiguity around timezone shifts, this field is stored and transmitted as a full date and time without timezone information or conversion. Enter as much information as is available.

Schema

provider_id

Refers to: provider / provider_id

Foreign key to the primary care provider – the person is seeing in the provider table.

Schema
Mappings
Model Table Field Comment
OMOP v4 person provider_id

race_concept_id

A foreign key that refers to a standard concept identifier in the Vocabulary for the race of the person.

Schema
Mappings
Model Table Field Comment
PCORnet v1 demographic race Limited to the concept_id values under the ���Race�۝ concept class.
OMOP v4 person race_concept_id

race_source_value

The source code for the race of the person as it appears in the source data. The person race is mapped to a standard race concept in the Vocabulary and the original value is stored here for reference.

Schema
Mappings
Model Table Field Comment
PCORnet v1 demographic raw_race
OMOP v4 person race_source_value

year_of_birth

The year of birth of the person. For data sources with date of birth, the year is extracted. For data sources where the year of birth is not available, the approximate year of birth is derived based on any age group categorization available.

Schema
Mappings
Model Table Field Comment
PCORnet v1 demographic birth_date
OMOP v4 person year_of_birth

procedure_occurrence

Procedures carried out on the Person

Fields

associated_provider_id

Refers to: provider / provider_id

A foreign key to the provider in the provider table who was responsible for carrying out the procedure.

Schema
Mappings
Model Table Field Comment
OMOP v4 procedure_occurrence associated_provider_id

person_id

Refers to: person / person_id

A foreign key identifier to the person who is subjected to the procedure. The demographic details of that person are stored in the person table.

Schema
Mappings
Model Table Field Comment
PCORnet v1 procedure patid
OMOP v4 procedure_occurrence person_id

procedure_concept_id

A foreign key that refers to a standard procedure concept identifier in the Vocabulary.

Schema
Mappings
Model Table Field Comment
PCORnet v1 procedure px
OMOP v4 procedure_occurrence procedure_concept_id

procedure_date

The date on which the procedure was performed.

Schema
Mappings
Model Table Field Comment
OMOP v4 procedure_occurrence procedure_date

procedure_occurrence_id

A system-generated unique identifier for each procedure occurrence. Sites can use any integer- DCC will do a substitution.

Schema
Mappings
Model Table Field Comment
OMOP v4 procedure_occurrence procedure_occurrence_id

procedure_source_value

The source code for the procedure as it appears in the source data. This code is mapped to a standard procedure concept in the Vocabulary and the original code is, stored here for reference. Procedure source codes are typically ICD-9-Proc, ICD-10-Proc, CPT-4, HCPCS or OPCS-4 codes.

Schema
Mappings
Model Table Field Comment
OMOP v4 procedure_occurrence procedure_source_value

procedure_type_concept_id

A foreign key to the predefined concept identifier in the Vocabulary reflecting the type of source data from which the procedure record is derived.

Schema
Mappings
Model Table Field Comment
OMOP v4 procedure_occurrence procedure_type_concept_id

relevant_condition_concept_id

A foreign key to the predefined concept identifier in the vocabulary reflecting the condition that was the cause for initiation of the procedure. Note that this is not a direct reference to a specific condition record in the condition table, but rather a condition concept in the vocabulary.

Schema
Mappings
Model Table Field Comment
OMOP v4 procedure_occurrence relevant_condition_concept_id

visit_occurrence_id

Refers to: visit_occurrence / visit_occurrence_id

A foreign key to the visit in the visit table during which the procedure was carried out.

Schema
Mappings
Model Table Field Comment
PCORnet v1 procedure encounterid
OMOP v4 procedure_occurrence visit_occurrence_id

provider

Information about health care providers

Fields

care_site_id

Refers to: care_site / care_site_id

A foreign key to the main care site where the provider is practicing. This field is required in PEDSnet, which is a deviation from OMOP CDM V4.

Schema
Mappings
Model Table Field Comment
OMOP v4 provider care_site_id

dea

The Drug Enforcement Administration (DEA) number of the provider. Optional – Do not transmit to DCC.

Schema
Mappings
Model Table Field Comment
OMOP v4 provider dea

npi

The National Provider Identifier (NPI) of the provider. Optional – Do not transmit to DCC.

Schema
Mappings
Model Table Field Comment
OMOP v4 provider npi

provider_id

A unique identifier for each provider. Each site must maintain a map from this value to the identifier used for the provider in the source data.

Schema
Mappings
Model Table Field Comment
OMOP v4 provider provider_id
Inbound References

Total: 5

Table Field Name
condition_occurrence associated_provider_id fpk_condition_provider
observation associated_provider_id fpk_observation_provider
person provider_id fpk_person_provider
procedure_occurrence associated_provider_id fpk_procedure_provider
visit_occurrence provider_id fpk_visit_provider

provider_source_value

The identifier used for the provider in the source data, stored here for reference. Sites should create a random ID, but keep the mapping.

Schema
Mappings
Model Table Field Comment
OMOP v4 provider provider_source_value

specialty_concept_id

A foreign key to a standard provider’s specialty concept identifier in the Vocabulary. This is an optional field. PEDSnet has not yet defined an ETL convention for selecting one specialty code for providers who have multiple specialties.

Schema
Mappings
Model Table Field Comment
OMOP v4 provider specialty_concept_id

specialty_source_value

The source code for the provider specialty as it appears in the source data, stored here for reference.

Schema
Mappings
Model Table Field Comment
OMOP v4 provider specialty_source_value

relationship

List of all types of Relationships in the Concept Relationship Table and their names (descriptions).

Fields

defines_ancestry

Defines whether a hierarchical relationship contributes to the concept_ancestor table. These are subsets of the hierarchical relationships. Valid values are Y or NULL.

Schema

is_hierarchical

Defines whether a relationship defines concepts into classes or hierarchies. Values are Y for hierarchical relationship or NULL if not.

Schema

relationship_id

The type of relationship captured by the relationship record.

Schema
Inbound References

Total: 1

Table Field Name
concept_relationship relationship_id fpk_concept_relationship_id

relationship_name

The text that describes the relationship type.

Schema

source_to_concept_map

Mapping between codes used in source data and Concepts in the Standard Vocabulary.

Fields

invalid_reason

Reason the mapping instance was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.

Schema

mapping_type

A string identifying the observational data element being translated. Examples include ‘DRUG’, ‘CONDITION’, ‘PROCEDURE’, ‘PROCEDURE DRUG’ etc. It is important to pick the appropriate mapping record when the same source code is being mapped to different concepts in different contexts. As an example a procedure code for drug administration can be mapped to a procedure concept or a drug concept or both.

Schema

primary_map

A boolean value identifying the primary mapping relationship for those sets where the source_code, the source_vocabulary_id and the mapping type is identical (one-to-many mappings). The ETL will only consider the primary map. Permitted values are Y and NULL.

Schema

source_code

The source code being translated into a standard concept.

Schema

source_code_description

An optional description for the source code. This is included as a convenience to compare the description of the source code to the name of the concept.

Schema

source_vocabulary_id

Refers to: vocabulary / vocabulary_id

A foreign key to the vocabulary table defining the vocabulary of the source code that is being mapped to the standard vocabulary.

Schema

target_concept_id

Refers to: concept / concept_id

A foreign key to the concept to which the source code is being mapped.

Schema

target_vocabulary_id

Refers to: vocabulary / vocabulary_id

A foreign key to the vocabulary table defining the vocabulary of the target concept.

Schema

valid_end_date

The date when the mapping instance became invalid because it was deleted or superseded (updated) by a new relationship. Default value is 31-Dec-2099.

Schema

valid_start_date

The date when the mapping instance was first recorded.

Schema

visit_occurrence

Visits for health care services of the Person

Fields

care_site_id

Refers to: care_site / care_site_id

A foreign key to the care site in the care site table that was visited.

Schema
Mappings
Model Table Field Comment
PCORnet v1 encounter facilityid
OMOP v4 visit_occurrence care_site_id

person_id

Refers to: person / person_id

A foreign key identifier to the person for whom the visit is recorded. The demographic details of that person are stored in the person table.

Schema
Mappings
Model Table Field Comment
PCORnet v1 encounter patid
OMOP v4 visit_occurrence person_id

place_of_service_concept_id

A foreign key that refers to a place of service concept identifier in the vocabulary.

Schema
Mappings
Model Table Field Comment
PCORnet v1 encounter enc_type Limited to concept_id values under the ���Encounter Type�۝ concept class.
PCORnet v1 encounter raw_enc_type
OMOP v4 visit_occurrence place_of_service_concept_id

place_of_service_source_value

The source code used to reflect the type or source of the visit in the source data. Valid entries include office visits, hospital admissions, etc. These source codes can also be type-of service codes and activity type codes.

Schema
Mappings
Model Table Field Comment
OMOP v4 visit_occurrence place_of_service_source_value

provider_id

Refers to: provider / provider_id

A foreign key to the provider in the provider table who was associated with the visit. NOTE: this is NOT in OMOP CDM v4, but appears in OMOP CDMv5. PEDSnet is including the field at this time due to an existing use case (Obesity cohort).

Schema

visit_end_date

The end date of the visit. If this is a one-day visit the end date should match the start date. If the encounter is on-going at the time of ETL, this should be null.

Schema
Mappings
Model Table Field Comment
PCORnet v1 encounter discharge_date
OMOP v4 visit_occurrence visit_end_date

visit_occurrence_id

A unique identifier for each person’s visits or encounter at a healthcare provider. Sites can provide whatever integers (DCC will replace the value).

Schema
Mappings
Model Table Field Comment
PCORnet v1 encounter encounterid
OMOP v4 visit_occurrence visit_occurrence_id
Inbound References

Total: 3

Table Field Name
condition_occurrence visit_occurrence_id fpk_condition_visit
observation visit_occurrence_id fpk_observation_visit
procedure_occurrence visit_occurrence_id fpk_procedure_visit

visit_start_date

The start date of the visit.

Schema
Mappings
Model Table Field Comment
PCORnet v1 encounter admit_date
OMOP v4 visit_occurrence visit_start_date

vocabulary

Contains a list of sources for the various Concepts. Many Concepts are derived from national or industry initiatives, such as the ICD diagnostic codes. Others are created by OMOP.

Fields

vocabulary_id

A unique identifier for each vocabulary.

Schema
Inbound References

Total: 3

Table Field Name
concept vocabulary_id fpk_concept_vocabulary
source_to_concept_map source_vocabulary_id fpk_source_to_concept_map_v_1
source_to_concept_map target_vocabulary_id fpk_source_to_concept_map_v_2

vocabulary_name

The name describing the vocabulary, for example “SNOMED-CT”, “ICD-9”, “Visit”, etc.

Schema