Top

PEDSnet v2.1

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
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_name

The description of the care site

Schema

care_site_source_value

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

Schema

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

place_of_service_concept_id

Refers to: concept / concept_id

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

Schema

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

specialty_concept_id

Refers to: concept / concept_id

The specialty of the department linked to a standard specialty concept as it appears in the Vocabulary

Schema

specialty_source_value

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

Schema

concept

The CONCEPT table contains records that uniquely identify each fundamental unit of meaning used to express clinical information. Concepts are derived from source vocabularies, which represent clinical information across different domains (e.g. conditions, drugs, procedures) through the use of source codes and associated descriptions. Some concepts are designated as standard concepts, meaning these concepts can be used within the OMOP Common Data Model and within standardized analytics. Each standard concept has a primary domain, which defines the location where the concept would be expected to be observed within OMOP Common Data Model.

Fields

concept_class_id

Refers to: concept_class / concept_class_id

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

concept_id

A unique identifier for each concept across all domains.

Schema
Inbound References

Total: 66

Table Field Name
care_site place_of_service_concept_id fpk_care_site_place
care_site specialty_concept_id fpk_care_site_specialty
concept_ancestor ancestor_concept_id fpk_concept_ancestor_concept_1
concept_ancestor descendant_concept_id fpk_concept_ancestor_concept_2
concept_class concept_class_concept_id fpk_concept_class_concept
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
concept_synonym language_concept_id fpk_concept_synonym_language
condition_occurrence condition_concept_id fpk_condition_concept
condition_occurrence condition_source_concept_id fpk_condition_concept_s
condition_occurrence condition_type_concept_id fpk_condition_type_concept
death cause_concept_id fpk_death_cause_concept
death cause_source_concept_id fpk_death_cause_concept_s
death death_type_concept_id fpk_death_type_concept
death death_impute_concept_id fpk_death_impute_concept
domain domain_concept_id fpk_domain_concept
drug_exposure dose_unit_concept_id fpk_drug_dose_unit_concept
drug_exposure drug_concept_id fpk_drug_concept
drug_exposure drug_source_concept_id fpk_drug_concept_s
drug_exposure drug_type_concept_id fpk_drug_type_concept
drug_exposure route_concept_id fpk_drug_route_concept
drug_strength drug_concept_id fpk_drug_strength_concept_1
drug_strength ingredient_concept_id fpk_drug_strength_concept_2
drug_strength amount_unit_concept_id fpk_drug_strength_unit_1
drug_strength numerator_unit_concept_id fpk_drug_strength_unit_2
drug_strength denominator_unit_concept_id fpk_drug_strength_unit_3
fact_relationship domain_concept_id_1 fpk_fact_domain_1
fact_relationship domain_concept_id_2 fpk_fact_domain_2
fact_relationship relationship_concept_id fpk_fact_relationship
measurement measurement_concept_id fpk_measurement_concept
measurement measurement_source_concept_id fpk_measurement_concept_s
measurement measurement_type_concept_id fpk_measurement_type_concept
measurement operator_concept_id fpk_measurement_operator
measurement unit_concept_id fpk_measurement_unit
measurement value_as_concept_id fpk_measurement_value
measurement range_low_operator_concept_id fpk_measurement_range_low_operator
measurement range_high_operator_concept_id fpk_measurement_range_high_operator
observation observation_concept_id fpk_observation_concept
observation observation_source_concept_id fpk_observation_concept_s
observation observation_type_concept_id fpk_observation_type_concept
observation qualifier_concept_id fpk_observation_qualifier
observation unit_concept_id fpk_observation_unit
observation value_as_concept_id fpk_observation_value
observation_period period_type_concept_id fpk_observation_period_concept
person ethnicity_concept_id fpk_person_ethnicity_concept
person ethnicity_source_concept_id fpk_person_ethnicity_concept_s
person gender_concept_id fpk_person_gender_concept
person gender_source_concept_id fpk_person_gender_concept_s
person race_concept_id fpk_person_race_concept
person race_source_concept_id fpk_person_race_concept_s
procedure_occurrence modifier_concept_id fpk_procedure_modifier
procedure_occurrence procedure_concept_id fpk_procedure_concept
procedure_occurrence procedure_source_concept_id fpk_procedure_concept_s
procedure_occurrence procedure_type_concept_id fpk_procedure_type_concept
provider gender_concept_id fpk_provider_gender
provider gender_source_concept_id fpk_provider_gender_s
provider specialty_concept_id fpk_provider_specialty
provider specialty_source_concept_id fpk_provider_specialty_s
relationship relationship_concept_id fpk_relationship_concept
source_to_concept_map source_concept_id fpk_source_to_concept_map_src
source_to_concept_map target_concept_id fpk_source_to_concept_map_c_1
visit_occurrence visit_concept_id fpk_visit_concept
visit_occurrence visit_source_concept_id fpk_visit_concept_s
visit_occurrence visit_type_concept_id fpk_visit_type_concept
vocabulary vocabulary_concept_id fpk_vocabulary_concept

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

domain_id

Refers to: domain / domain_id

The domain a concept belongs to.

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

standard_concept

This flag determines where a concept is a Standard Concept, i.e. is used in the data, a class concept, or a non-standard concept. The allowables values for standard_concept are: ’S’ for Standard Concept, ‘C’ for a Class Concept, otherwise the content is null for non-standard concepts, including source concepts. Standard Concepts (S) may appear in CDM tables in CONCEPT_ID fields, whereas Class concepts © should not appear in the CDM data, but participate in the CONCEPT_ANCESTOR and can be used to identify descendants that may appear in the data. Non-standard concepts can only appear in SOURCE_CONCEPT_ID fields and are not used in CONCEPT_ANCESTOR.

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

The CONCEPT_ANCESTOR table contains records that define the inferred hierarchical relationships between all standard concepts. The concept ancestor table is fully derived from the concept, CONCEPT_RELATIONSHIP, and relationship tables, whereby all ancestor-descendant relationships can be inferred from traversing all parent-child relationships between standard concepts. The concept ancestor table includes records for all parent-child relationships, as well as grandparent-grandchild relationships and additional levels of lineage. The concept ancestor table enables efficient identification of multi-step hierarchical relationships, such as branded drugs that fall within a therapeutic class or specific diagnosis that are classified within a particular system organ class.

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_class

The CONCEPT_CLASS table includes a list of the classifications used to differentiate concepts within a given vocabulary. This reference table is populated with a single record for each concept class and includes a descriptive name for the concept class.

Fields

concept_class_concept_id

Refers to: concept / concept_id

A foreign key that refers to a standard concept identifier in the Standardized Vocabularies for the Class the record belongs to.

Schema

concept_class_id

A unique key for each class.

Schema
Inbound References

Total: 1

Table Field Name
concept concept_class_id fpk_concept_class

concept_class_name

The name describing the Concept Class, e.g. “Clinical Finding”, “Ingredient”, etc.

Schema

concept_relationship

The CONCEPT_RELATIONSHIP table contains records that define direct relationships between any two concepts and the nature of the relationship. The type of relationship is defined in the Relationship table, and is generally classified as hierarchical (parent-child) or non-hierarchical (lateral). All relationships are directional, and each concept relationship is represented twice symmetrically within the concept relationship table. For example, the two SNOMED concepts of ‘Acute myocardial infarction of the anterior wall’ and ‘Acute myocardial infarction’ have two concept relationships: 1- ‘Acute myocardial infarction of the anterior wall’ ‘is a’ ‘Acute myocardial infarction’, and 2- ‘Acute myocardial infarction’ ‘subsumes’ ‘Acute myocardial infarction of the anterior wall’.

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

The CONCEPT_SYNONYM table is used to store alternate names and descriptions for a concept. Each synonym is assigned its own unique identifier and contains the text of a description and the identifier of the concept that it represents.

Fields

concept_id

Refers to: concept / concept_id

A foreign key to the concept in the concept table.

Schema

concept_synonym_name

The alternative name for the concept.

Schema

language_concept_id

Refers to: concept / concept_id

A foreign key to a concept representing the language.

Schema

condition_occurrence

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

Fields

condition_concept_id

Refers to: concept / concept_id

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

Schema

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

condition_end_time

The date and time when the instance of the condition is considered to have ended

Schema

condition_occurrence_id

A unique identifier for each condition occurrence event.

Schema

condition_source_concept_id

Refers to: concept / concept_id

A foreign key to a condition concept that refers to the code used in the source

Schema

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

condition_start_date

The date when the instance of the condition is recorded.

Schema

condition_start_time

The date and time when the instance of the condition is recorded.

Schema

condition_type_concept_id

Refers to: concept / 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

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

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

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

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

death

Time and cause of death of the Person

Fields

cause_concept_id

Refers to: concept / concept_id

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

Schema

cause_source_concept_id

Refers to: concept / concept_id

A foreign key to the vocbaulary concept that refers to the code used in the source.

Schema

cause_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

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

death_impute_concept_id

Refers to: concept / concept_id

A foreign key referring to a standard concept identifier in the vocabulary for death imputation.

Schema

death_time

The date the person was deceased.

Schema

death_type_concept_id

Refers to: concept / 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

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

domain

The DOMAIN table includes a list of the domains of data elements that are contained within the OMOP common data model. A domain defines the set of allowable concepts for each standardized field. This reference table is populated with a single record for each domain and includes a descriptive name for the Domain.

Fields

domain_concept_id

Refers to: concept / concept_id

A foreign key that refers to a standard concept identifier in the Standardized Vocabularies for the Domain the Domain record belongs to.

Schema

domain_id

A unique key for each domain.

Schema
Inbound References

Total: 1

Table Field Name
concept domain_id fpk_concept_domain

domain_name

The name describing the Domain, e.g. “Condition”, “Procedure”, “Measurement” etc.

Schema

drug_exposure

The drug exposure domain captures any biochemical substance that is introduced in any way to a patient.

Fields

days_supply

The number of days of supply the medication as recorded in the original prescription or dispensing record.

Schema

dose_unit_concept_id

Refers to: concept / concept_id

A foreign key to a predefined concept in the Standard Vocabularies reflecting the unit the effective drug_dose value is expressed

Schema

dose_unit_source_value

The information about the dose unit as detailed in the source

Schema

drug_concept_id

Refers to: concept / concept_id

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

Schema

drug_exposure_end_date

The end date for the current instance of drug utilization. It is not available from all sources.

Schema

drug_exposure_end_time

The end date and time of the utilization of the drug

Schema

drug_exposure_id

A system-generated unique identifier for each drug utilization event.

Schema

drug_exposure_order_date

The order date of the drug

Schema

drug_exposure_order_time

The order date and time of the drug

Schema

drug_exposure_start_date

The start date for the current instance of drug utilization. Valid entries include a start date of a prescription, the date a prescription was filled, or the date on which a drug administration procedure was recorded.

Schema

drug_exposure_start_time

The start date and time of the utilization of the drug. The start date of the prescription, the date the prescription was filled, the date a drug was dispensed or the date on which a drug administration procedure was recorded are acceptable.

Schema

drug_source_concept_id

Refers to: concept / concept_id

A foreign key to a drug concept that refers to the code used in the source

Schema

drug_source_value

The source drug value as it appears in the source data. The source is mapped to a standard RxNorm concept and the original code is stored here for reference.

Schema

drug_type_concept_id

Refers to: concept / concept_id

A foreign key to a standard concept identifier of the type of drug exposure in the Vocabulary as represented in the source data.

Schema

effective_drug_dose

Numerical value of drug dose for this drug_exposure record

Schema

effective_drug_dose_source_value

The drug dose for this drug_exposure record as it appears in the source

Schema

frequency

The discrete frequency information as available from the source

Schema

lot_number

An identifier to determine where the product originated

Schema

person_id

Refers to: person / person_id

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

Schema

provider_id

Refers to: provider / provider_id

A foreign key to the provider in the provider table who initiated (prescribed) the drug exposure

Schema

quantity

The quantity of the drugs as recorded in the original prescription or dispensing record.

Schema

refills

The number of refills after the initial prescrition.

Schema

route_concept_id

Refers to: concept / concept_id

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

Schema

route_source_value

The information about the route of administration as detailed in the source

Schema

sig

The directions on the drug prescription as recorded in the original prescription (and printed on the container) or the dispensing record

Schema

stop_reason

The reason, if available, where the medication was stopped, as indicated in the source data.

Schema

visit_occurrence_id

Refers to: visit_occurrence / visit_occurrence_id

A foreign key to the visit in the visit table during which the drug exposure initiated.

Schema

drug_strength

The DRUG_STRENGTH table contains structured content about the amount or concentration and associated units of a specific ingredient within a particular drug product. The drug strength table is a supplemental file to support standardized analysis of drug utilization using concepts from the RxNorm vocabulary. A clinical drug concept which contains multiple active ingredients will result in one drug strength record for each active ingredient.

Fields

amount_unit_concept_id

Refers to: concept / concept_id

The unit corresponding to the numeric value of the amount of the active ingredient contained within the product.

Schema

amount_value

The numeric value associated with the amount of active ingredient contained within the product, in situations when the ingredient is contained within a solid formulation.

Schema

denominator_unit_concept_id

Refers to: concept / concept_id

The denominator unit corresponding to the numeric value of the concentration of the active ingredient contained within the product.

Schema

drug_concept_id

Refers to: concept / concept_id

A foreign key to the concept in the concept table, representing the identifier for an RxNorm branded drug or clinical drug concept.

Schema

ingredient_concept_id

Refers to: concept / concept_id

A foreign key to the concept in the concept table, representing the identifier for an RxNorm ingredient concept contained within the drug product.

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

numerator_unit_concept_id

Refers to: concept / concept_id

The numerator unit corresponding to the numeric value of the concentration of the active ingredient contained within the product.

Schema

numerator_value

The numeric value associated with the concentration of the active ingredient contained within the product, in situations when the ingredient is contained within a non-solid formulation.

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. The default value is 1-Jan-1970.

Schema

fact_relationship

The fact relationship domain contains details of the relationships between facts within one domain or across two domains, and the nature of the relationship.

Fields

domain_concept_id_1

Refers to: concept / concept_id

The concept representing the domain of fact one, from which the corresponding table can be inferred.

Schema

domain_concept_id_2

Refers to: concept / concept_id

The concept representing the domain of fact two, from which the corresponding table can be inferred.

Schema

fact_id_1

The unique identifier in the table corresponding to the domain of fact one.

Schema

fact_id_2

The unique identifier in the table corresponding to the domain of fact two.

Schema

relationship_concept_id

Refers to: concept / concept_id

A foreign key to a standard concept identifier of relationship in the Standardized Vocabularies.

Schema

location

Physical addresses of patients, organizations and care sites

Fields

address_1

Optional - Do not transmit to DCC

Schema

address_2

Optional - Do not transmit to DCC

Schema

city

Optional - Do not transmit to DCC

Schema

county

Optional - Do not transmit to DCC

Schema

location_id

A unique identifier for each geographic location.

Schema
Inbound References

Total: 2

Table Field Name
care_site location_id fpk_care_site_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

state

The state field as it appears in the source data.

Schema

zip

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

Schema

measurement

The measurement domain captures measurement orders and measurement results. The measurement domain can contain laboratory results and vital signs.

Fields

measurement_concept_id

Refers to: concept / concept_id

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

Schema

measurement_date

The date of the measurement.

Schema

measurement_id

A system-generated unique identifier for each measurement

Schema

measurement_order_date

This field applies to Lab Orders only. This is the date the lab was ordered in the source.

Schema

measurement_order_time

This field applies to Lab Orders only. This is the time the lab was ordered in the source.

Schema

measurement_result_date

This field applies to Lab Orders only. This is the date the lab resulted in the source.

Schema

measurement_result_time

This field applies to Lab Orders only. This is the time the lab resulted in the source.

Schema

measurement_source_concept_id

Refers to: concept / concept_id

A foreign key to a concept that refers to the code used in the source.

Schema

measurement_source_value

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

Schema

measurement_time

The time of the measurement.

Schema

measurement_type_concept_id

Refers to: concept / concept_id

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

Schema

operator_concept_id

Refers to: concept / concept_id

A foreign key identifier to the mathematical operator that is applied to the value_as_number.Operators are <, ≤, =, ≥, >

Schema

person_id

Refers to: person / person_id

A foreign key identifier to the person who the measurement is being documented for. The demographic details of that person are stored in the person table.

Schema

provider_id

Refers to: provider / provider_id

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

Schema

range_high

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

Schema

range_high_operator_concept_id

Refers to: concept / concept_id

A forign key to the modifier of higher limit of the normal range of the measurement as it appears in the source as a concept identifer.

Schema

range_high_source_value

The higher limit of the normal range of the measurement as it appears in the source.

Schema

range_low

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

Schema

range_low_operator_concept_id

Refers to: concept / concept_id

A forign key to the modifier of lower limit of the normal range of the measurement as it appears in the source as a concept identifer.

Schema

range_low_source_value

The lower limit of the normal range of the measurement as it appears in the source.

Schema

specimen_source_value

This field is applicable for lab values only. This source value for the specimen source as it appears in the source

Schema

unit_concept_id

Refers to: concept / concept_id

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

Schema

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 Standardized Vocabularies and the original code is, stored here for reference.

Schema

value_as_concept_id

Refers to: concept / 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

value_as_number

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

Schema

value_source_value

The source value associated with the structured value stored as numeric or concept. This field can be used in instances where the source data are transformed

Schema

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

observation

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

Fields

observation_concept_id

Refers to: concept / concept_id

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

Schema

observation_date

The date of the observation.

Schema

observation_id

A unique identifier for each observation.

Schema

observation_source_concept_id

Refers to: concept / concept_id

A foreign key to a concept that refers to the code used in the source.

Schema

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

observation_time

The time of the observation.

Schema

observation_type_concept_id

Refers to: concept / concept_id

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

Schema

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

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

qualifier_concept_id

Refers to: concept / concept_id

A foreign key to standard concept identifier for a qualifier (e.g severity of drug-drug interaction alert)

Schema

qualifier_source_value

The source value associated with a qualifier to characterize the observation

Schema

unit_concept_id

Refers to: concept / concept_id

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

Schema

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

value_as_concept_id

Refers to: concept / 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

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

value_as_string

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

Schema

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

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

observation_period_end_time

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

Schema

observation_period_id

A system-generate unique identifier for each observation period

Schema

observation_period_start_date

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

Schema

observation_period_start_time

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

Schema

period_type_concept_id

Refers to: concept / concept_id

A foreign key identifier to the predefined concept in the Standardized Vocabularies reflecting the source of the observation period information

Schema

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

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

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

ethnicity_concept_id

Refers to: concept / concept_id

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

Schema

ethnicity_source_concept_id

Refers to: concept / concept_id

A foreign key to the ethnicity concept that refers to the code used in the source.

Schema

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

gender_concept_id

Refers to: concept / concept_id

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

Schema

gender_source_concept_id

Refers to: concept / concept_id

A foreign key to the gender concept that refers to the code used in the source.

Schema

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

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

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

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
Inbound References

Total: 8

Table Field Name
condition_occurrence person_id fpk_condition_person
death person_id fpk_death_person
drug_exposure person_id fpk_drug_person
measurement person_id fpk_measurement_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

provider_id

Refers to: provider / provider_id

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

Schema

race_concept_id

Refers to: concept / concept_id

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

Schema

race_source_concept_id

Refers to: concept / concept_id

A foreign key to the race concept that refers to the code used in the source.

Schema

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

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

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

procedure_occurrence

Procedures carried out on the Person

Fields

modifier_concept_id

Refers to: concept / concept_id

A foreign key to a standard concept identifier for a modifier to the procedure (e.g. bilateral)

Schema

modifier_source_value

The source code for the modifier as it appears in the source data.

Schema

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

procedure_concept_id

Refers to: concept / concept_id

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

Schema

procedure_date

The date on which the procedure was performed.

Schema

procedure_occurrence_id

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

Schema

procedure_source_concept_id

Refers to: concept / concept_id

A foreign key to a procedure concept that refers to the code used in the source. For example, if the procedure is “Anesthesia for procedures on eye; lens surgery” in the source which has a concept code in the vocabulary that is 2100658. The procedure source concept id will be 2100658.

Schema

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

procedure_time

The date and time on which the procedure was performed. If there is no time associated with the date assert midnight.

Schema

procedure_type_concept_id

Refers to: concept / 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

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

qualifier_source_value

The source code for the qualifier as it appears in the source data.

Schema

quantity

The quantity of procedures ordered or administered.

Schema

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

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

dea

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

Schema

gender_concept_id

Refers to: concept / concept_id

The gender of the provider

Schema

gender_source_concept_id

Refers to: concept / concept_id

A foreign key to a concept that refers to the code used in the source.

Schema

gender_source_value

The source value for the provider gender.

Schema

npi

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

Schema

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
Inbound References

Total: 7

Table Field Name
condition_occurrence provider_id fpk_condition_provider
drug_exposure provider_id fpk_drug_provider
measurement provider_id fpk_measurement_provider
observation provider_id fpk_observation_provider
person provider_id fpk_person_provider
procedure_occurrence provider_id fpk_procedure_provider
visit_occurrence provider_id fpk_visit_provider

provider_name

A description of the provider.

Schema

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

specialty_concept_id

Refers to: concept / 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

specialty_source_concept_id

Refers to: concept / concept_id

A foreign key to a concept that refers to the code used in the source

Schema

specialty_source_value

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

Schema

year_of_birth

The year of birth of the provider

Schema

relationship

The RELATIONSHIP table provides a reference list of all allowable types of relationships that can be used to associate any two concepts in the concept relationship table. Relationships are classified as hierarchical (parent-child) or non-hierarchical, and are used to determine which concept relationship records should be included in the computation of the concept ancestor table.

Fields

defines_ancestry

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

Schema

is_hierarchical

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

Schema

relationship_concept_id

Refers to: concept / concept_id

A foreign key that refers to a standard concept identifier in the Standardized Vocabularies for the relationship concept.

Schema

relationship_id

The type of relationship captured by the relationship record.

Schema
Inbound References

Total: 2

Table Field Name
concept_relationship relationship_id fpk_concept_relationship_id
relationship reverse_relationship_id fpk_relationship_reverse

relationship_name

The text that describes the relationship type.

Schema

reverse_relationship_id

Refers to: relationship / relationship_id

The identifier for the relationship used to define the reverse relationship between two concepts.

Schema

source_to_concept_map

The SOURCE_TO_CONCEPT_MAP table is a legacy data structure within the OMOP Common Data Model, recommended for use in extract, transform, and load (ETL) processes to maintain local source codes which are not available as concepts in the Standardized Vocabularies, and to establish mappings for each source code into a standard concept that can be used to populate the Common Data Model tables. The source to concept map table is no longer populated with content within the Standardized Vocabularies published to the OMOP community.

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

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_concept_id

Refers to: concept / concept_id

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

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

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

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_concept_id

Refers to: concept / concept_id

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

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

visit_end_time

The end time of the visit.

Schema

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
Inbound References

Total: 6

Table Field Name
condition_occurrence visit_occurrence_id fpk_condition_visit
drug_exposure visit_occurrence_id fpk_drug_visit
measurement visit_occurrence_id fpk_measurement_visit
observation visit_occurrence_id fpk_observation_visit
procedure_occurrence visit_occurrence_id fpk_procedure_visit
visit_payer visit_occurrence_id fpk_visit_payer_visit

visit_source_concept_id

Refers to: concept / concept_id

A foreign key to a concept that refers to the code used in the source.

Schema

visit_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

visit_start_date

The start date of the visit.

Schema

visit_start_time

The start time of the visit.

Schema

visit_type_concept_id

Refers to: concept / concept_id

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

Schema

visit_payer

The visit payer table documents insurance information as it relates to a visit in visit_occurrence. For this reason the key of this table will be visit_occurrence_id and visit_payer_id.

Fields

plan_class

A list of the “payment sources” most often used in demographic analyses; proposed value would be Private/commercial, Medicaid/sCHIP, Medicare, Other public, Self-pay, Other/unknown

Schema

plan_name

The untransformed payer/plan name from the source data

Schema

plan_type

A standardized interpretation of the plan structure; proposed value set would be HMO, PPO, POS, Fee for service, Other/unknown

Schema

visit_occurrence_id

Refers to: visit_occurrence / visit_occurrence_id

A foreign key to the visit in the visit table where the payer was billed for the visit.

Schema

visit_payer_id

A system-generated unique identifier for each visit payer relationship.

Schema

vocabulary

The VOCABULARY table includes a list of the vocabularies collected from various sources or created de novo by the OMOP community. This reference table is populated with a single record for each vocabulary source and includes a descriptive name and other associated attributes for the vocabulary.

Fields

vocabulary_concept_id

Refers to: concept / concept_id

A foreign key that refers to a standard concept identifier in the Standardized Vocabularies for the vocabulary the Vocabulary record belongs to.

Schema

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

vocabulary_reference

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

Schema

vocabulary_version

External reference to documentation or available download of the about the vocabulary.

Schema