The ATTRIBUTE_DEFINITION table contains records to define each attribute through an associated description and syntax. Attributes are derived elements that can be selected or calculated for a subject within a cohort. The ATTRIBUTE_DEFINITION table provides a standardized structure for maintaining the rules governing the calculation of covariates for a subject in a cohort, and can store operational programming code to instantiate the attributes for a given cohort within the OMOP Common Data Model.
Fields
A unique identifier for each attribute.
integerTotal: 1
| Table | Field | Name |
|---|---|---|
| cohort_attribute | attribute_definition_id | fpk_ca_attribute_definition |
A complete description of the attribute definition.
clobA short description of the attribute.
stringSyntax to operationalize the attribute definition.
clobType to define what kind of attribute definition the record represents and how the syntax may be executed.
integerThe CARE_SITE table contains a list of uniquely identified physical or organizational units where healthcare delivery is practiced (offices, wards, hospitals, clinics, etc.).
Fields
A system-generated unique identifier for each care site. A care site is the place where the provider delivered the healthcare to the person.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | care_site | care_site_id |
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 |
The description of the care site.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | care_site | care_site_name |
The identifier for the care site as it appears in the source data, stored here for reference.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | care_site | care_site_source_value |
Refers to: location / location_id
A foreign key to the geographic location in the location table, where the detailed address information is stored.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | care_site | location_id |
Refers to: concept / concept_id
A foreign key to the predefined concept identifier in the vocabulary reflecting the place of service.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | care_site | place_of_service_concept_id |
The source code for the place of service as it appears in the source data, stored here for reference.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | care_site | place_of_service_source_value |
The CDM_SOURCE table contains detail about the source database and the process used to transform the data into the OMOP common data model. If a source database is derived from multiple data feeds, the integration of those disparate sources is expected to be documented in the ETL specifications.
Fields
URL or other external reference to location of ETL specification documentation and ETL source code
stringThe name of the organization responsible for the development of the CDM instance
stringThe date when the CDM was instantiated
dateAn abbreviation of the name
stringThe full name of the source.
stringThe version of CDM used
stringA description of the source data origin and purpose for collection. The description may contain a summary of the period of time that is expected to be covered by this dataset.
clobURL or other external reference to location of source documentation
stringThe date for which the source data is most current, such as the last day of data capture
dateThe version of the vocabulary used
stringThe COHORT table contains records derived as a set of subjects that satisfy a given set of inclusion criteria for a duration of time. The definition of the cohort is contained within the COHORT_DEFINITION table. Example cohorts can include patients diagnosed with a specific condition, patients exposed to a particular drug, or providers who have performed a specific procedure.
Fields
Refers to: cohort_definition / cohort_definition_id
A foreign key to a record in the COHORT_DEFINITION table containing relevant Cohort definition information.
integerThe date when the cohort definition criteria for the person, provider or visit no longer match or the cohort membership was terminated.
dateThe date when the cohort definition criteria for the person, provider or visit first match.
dateA foreign key to the subject in the cohort. These could be referring to records in the Person, Provider, Visit Occurrence table.
integerThe COHORT_ATTRIBUTE table contains attributes associated with each subject within a cohort, as defined by a given set of inclusion criteria for a duration of time. The definition of the cohort attribute is contained within the ATTRIBUTE_DEFINITION table. Example cohort attributes can be age, BMI or comorbidity score.
Fields
Refers to: attribute_definition / attribute_definition_id
A foreign key to a record in the ATTRIBUTE_DEFINITION table containing relevant attribute definition information.
integerRefers to: cohort_definition / cohort_definition_id
A foreign key to a record in the COHORT_DEFINITION table containing relevant Cohort definition information.
integerThe date when the cohort definition criteria for the person, provider or visit no longer match or the cohort membership was terminated.
dateThe date when the cohort definition criteria for the person, provider or visit first match.
dateA foreign key to the subject in the cohort. These could be referring to records in the PERSON, PROVIDER, or VISIT_OCCURRENCE table.
integerRefers to: concept / concept_id
The attribute result stored as a concept id. This is applicable to attributes where the result is expressed as a categorical value.
integerThe attribute result stored as a number. This is applicable to attributes where the result is expressed as a numeric value, such as calculated entities (e.g. age, BMI) or composite scales (e.g. Charlson index).
numberThe COHORT_DEFINITION table contains records to define each derived cohort through an associated description and syntax. Cohorts are derived elements of a set of subjects that satisfy a given set of inclusion criteria for a duration of time. The COHORT_DEFINITION table provides a standardized structure for maintaining the rules governing the inclusion of a subject into a cohort, and can store operational programming code to instantiate the cohort within a OMOP common data model.
Fields
A complete description of the cohort definition.
clobA unique identifier for each cohort.
integerTotal: 2
| Table | Field | Name |
|---|---|---|
| cohort | cohort_definition_id | fpk_cohort_definition |
| cohort_attribute | cohort_definition_id | fpk_ca_cohort_definition |
A short description of the cohort.
stringSyntax to operationalize the cohort definition.
clobA date to indicate when the cohort was instantiated in the COHORT table.
dateRefers to: concept / concept_id
Type to define what kind of cohort definition the record represents and how the syntax may be executed.
integerA foreign key to the concept to which defines the domain of subjects that are members of the cohort (e.g., person, provider, visit).
integerThe 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
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.
stringThe 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.
stringA unique identifier for each concept across all domains.
integerTotal: 80
An unambiguous, meaningful and descriptive name for the concept.
stringThe domain a concept belongs to.
stringReason the concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.
stringThis 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.
stringThe date when the concept became invalid because it was deleted or superseded (updated) by a new concept. The default value is 31-Dec-2099.
dateThe date when the concept was first recorded.
dateRefers to: vocabulary / vocabulary_id
A foreign key to the vocabulary table indicating from which source the concept has been adapted.
stringThe 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
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.
integerRefers 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.
integerThe 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.
integerThe 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.
integerThe 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
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.
integerA unique key for each class.
stringTotal: 1
| Table | Field | Name |
|---|---|---|
| concept | concept_class_id | fpk_concept_class |
The name describing the Concept Class, e.g. “Clinical Finding”, “Ingredient”, etc.
stringThe 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
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.
integerRefers 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.
integerReason the relationship was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.
stringRefers to: relationship / relationship_id
The type of relationship as defined in the relationship table.
stringThe date when the relationship became invalid because it was deleted or superseded (updated) by a new relationship. Default value is 31-Dec-2099.
dateThe date when the instance of the relationship is first recorded.
dateThe 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
Refers to: concept / concept_id
A foreign key to the concept in the concept table.
integerThe alternative name for the concept.
stringA foreign key to a concept representing the language.
integerA Condition Era is defined as a span of time when the Person is assumed to have a given condition.
Fields
Refers to: concept / concept_id
A foreign key that refers to a standard condition concept identifier in the vocabulary.
integerThe end date for the condition era constructed from the individual instances of condition occurrences. It is the end date of the final continuously recorded instance of the condition.
dateA system-generated unique identifier for each condition era.
integerThe start date for the condition era constructed from the individual instances of condition occurrences. It is the start date of the very first chronologically recorded instance of the condition.
dateThe number of individual condition occurrences used to construct the condition era.
integerA foreign key identifier to the person who is experiencing the condition during the condition era. The demographic details of that person are stored in the person table.
integerThe CONDITION_OCCURRENCE table captures records of a disease or a medical condition based on evaluation by a provider or reported by a patient.
Fields
Refers to: concept / concept_id
A foreign key that refers to a standard condition concept identifier in the vocabulary.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | condition_occurrence | condition_concept_id |
The date when the instance of the condition is considered to have ended. This is not typically recorded.
date| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | condition_occurrence | condition_end_date |
A system-generated unique identifier for each condition occurrence event.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | condition_occurrence | condition_occurrence_id |
Refers to: concept / concept_id
A foreign key to a condition concept that refers to the code used in the source.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | condition_occurrence | condition_source_concept_id |
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/disposition codes from EHRs.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | condition_occurrence | condition_source_value |
The date when the instance of the condition is recorded.
date| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | condition_occurrence | condition_start_date |
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. Conditions are defined as primary or secondary diagnoses, problem lists and person statuses.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | condition_occurrence | condition_type_concept_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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | condition_occurrence | person_id |
Refers to: provider / provider_id
A foreign key to the provider in the provider table who was responsible for determining (diagnosing) the condition.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | condition_occurrence | provider_id |
The reason, if available, that the condition was no longer recorded, as indicated in the source data. Valid values include discharged, resolved, etc.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | condition_occurrence | stop_reason |
Refers to: visit_occurrence / visit_occurrence_id
A foreign key to the visit in the visit table during which the condition was determined (diagnosed).
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | condition_occurrence | visit_occurrence_id |
The DEATH table contains the clinical event for how and when a person dies. A person can have up to one record if the source systems contain evidence that s/he is deceased. All persons who were alive during all observation periods should not contain any information in the death table.
Fields
Refers to: concept / concept_id
A foreign key referring to a standard concept identifier in the vocabulary for conditions.
integerRefers to: concept / concept_id
A foreign key to the concept that refers to the code used in the source. Note, this variable name is abbreviated to ensure it will be allowable across database platforms.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | death | cause_source_concept_id |
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.
stringThe date the person 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.
date| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | death | death_date |
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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | death | death_type_concept_id |
A foreign key identifier to the deceased person. The demographic details of that person are stored in the person table.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | death | person_id |
The DEVICE_COST table captures the cost of a medical device or supply used on a Person. The information about the cost is only derived from the amounts paid for the device.
Fields
Refers to: concept / concept_id
A concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar.
integerA unique identifier for each procedure cost record.
integerRefers to: device_exposure / device_exposure_id
A foreign key identifier to the procedure record for which cost data are recorded.
integerThe amount paid by a secondary payer through the coordination of benefits.
numberThe amount paid by the payer (insurer). If there is more than one payer, several procedure_cost records indicate that fact.
numberThe amount paid by the person as a joint assumption of risk. Typically, this is a percentage of the expenses defined by the payer plan (policy) after the person’s deductible is exceeded.
numberThe amount paid by the person as a fixed contribution to the expenses. Copay does not contribute to the out_of_pocket expenses.
numberThe amount paid by the person that is counted toward the deductible defined by the payer plan (policy).
numberRefers to: payer_plan_period / payer_plan_period_id
A foreign key to the payer_plan_period table, where the details of the payer, plan and family are stored.
integerThe total amount paid by the person as a share of the expenses, excluding the copay.
numberThe total amount paid for the expenses of the procedure.
numberThe DEVICE_EXPOSURE table captures records about a person’s inferred exposure to a foreign physical object or instrument that is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), durable medical equipment and supplies (e.g. bandages, crutches, syringes), and other instruments used in medical procedures (e.g. sutures, defibrillators).
Fields
Refers to: concept / concept_id
Only the DI portion of the UDI would be captured as a Concept in the Standardized Vocabularies.
integerThe date the device or supply was removed from use.
dateA system-generated unique identifier for each device exposure.
integerTotal: 1
| Table | Field | Name |
|---|---|---|
| device_cost | device_exposure_id | fpk_device_cost_id |
The date the device or supply was applied or used.
dateRefers to: concept / concept_id
A foreign key to a device concept that refers to the code used in the source.
integerThe source code for the device as it appears in the source data. This code is mapped to a standard device concept in the Standardized Vocabularies and the original code is stored here for reference.
stringRefers to: concept / concept_id
Provenance for the data, e.g. procedure device, from registry, etc.
integerA foreign key identifier to the person who is subjected to the procedure. The demographic details of that person are stored in the person table.
integerRefers to: provider / provider_id
A foreign key to the provider in the provider table who was responsible for using the device.
integerThe number of individual devices used for the exposure
integerThe entire UDI or equivalent.
stringRefers to: visit_occurrence / visit_occurrence_id
A foreign key to the visit in the visit table during which the device was used.
integerThe 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
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.
integerA unique key for each domain.
stringTotal: 1
| Table | Field | Name |
|---|---|---|
| concept | domain_id | fpk_concept_domain |
The name describing the Domain, e.g. “Condition”, “Procedure”, “Measurement” etc.
stringA Dose Era is defined as a span of time when the Person is assumed to be exposed to a constant dose of a specific active ingredient.
Fields
The end date for the drug era constructed from the individual instance of drug exposures. It is the end date of the final continuously recorded instance of utilization of a drug.
dateA unique identifier for each drug era.
integerThe start date for the drug era constructed from the individual instances of drug exposures. It is the start date of the very first chronologically recorded instance of utilization of a drug.
dateThe numeric value of the dose
numberRefers to: concept / concept_id
A foreign key that refers to a standard concept identifier in the Standardized Vocabularies for the active ingredient drug concept.
integerA foreign key identifier to the person who is subjected to the drug during the drug era. The demographic details of that person are stored in the person table.
integerRefers to: concept / concept_id
A foreign key that refers to a standard concept identifier in the Standardized Vocabularies for the unit concept.
integerThe DRUG_COST table captures records indicating the cost of a Drug Exposure. The information about the cost is defined by the amount of money paid by the person and payer for the drug, as well as the charged cost of the drug.
Fields
List price of a drug set by the manufacturer.
numberRefers to: concept / concept_id
A concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar.
integerThe portion of the drug expenses due to the dispensing fee charged by the pharmacy, typically a fixed amount.
numberA system-generated unique identifier for each drug cost record.
integerRefers to: drug_exposure / drug_exposure_id
A foreign key identifier to the drug record for which cost data are recorded.
integerThe portion of the drug expenses due to the cost charged by the manufacturer for the drug, typically a percentage of the Average Wholesale Price.
numberThe amount paid by a secondary payer through the coordination of benefits.
numberThe amount paid by the payer (insurer). If there is more than one payer, several drug_cost records indicate that fact.
numberThe amount paid by the person as a joint assumption of risk. Typically, this is a percentage of the expenses defined by the payer plan (policy) after the person’s deductible is exceeded.
numberThe amount paid by the person as a fixed contribution to the expenses. Copay does not contribute to the out of pocket expenses.
numberThe amount paid by the person that is counted toward the deductible defined by the payer plan (policy).
numberRefers to: payer_plan_period / payer_plan_period_id
A foreign key to the payer_plan_period table, where the details of the payer, plan and family are stored.
integerThe total amount paid by the person as a share of the expenses, excluding the copay.
numberThe total amount paid for the expenses of drug exposure.
numberA Drug Era is defined as a span of time when the Person is assumed to be exposed to a particular active ingredient. A Drug Era is not the same as a Drug Exposure: Exposures are individual records corresponding to the source when drug was delivered to the Person, while successive periods of Drug Exposures are combined under certain rules to produce continuous Drug Eras.
Fields
Refers to: concept / concept_id
A foreign key that refers to a standard concept identifier in the vocabulary for the drug concept.
integerThe end date for the drug era constructed from the individual instance of drug exposures. It is the end date of the final continuously recorded instance of utilization of a drug.
dateA system-generated unique identifier for each drug era.
integerThe start date for the drug era constructed from the individual instances of drug exposures. It is the start date of the very first chronologically recorded instance of utilization of a drug.
dateThe number of individual drug exposure occurrences used to construct the drug era.
integerThe number of observed days of gap between drug exposure records which was tolerated in the building of the drug era record.
integerA foreign key identifier to the person who is subjected to the drug during the drug era. The demographic details of that person are stored in the person table.
integerThe DRUG_EXPOSURE table captures records about the inferred utilization of a biochemical substance with a physiological therapeutic effect when ingested or otherwise introduced into the body. Drugs include prescription and over-the- counter medicines, vaccines, and large-molecule biologic therapies. Drug exposure is inferred from clinical events associated with orders, prescriptions written, pharmacy dispensings, procedural administrations, and other patient- reported information.
Fields
The number of days of supply of the medication as recorded in the original prescription or dispensing record.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | days_supply |
Refers to: concept / concept_id
A foreign key to a predefined concept in the Standardized Vocabularies reflecting the unit the effective_drug_dose value is expressed.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | dose_unit_concept_id |
The information about the dose unit as detailed in the source.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | dose_unit_source_value |
Refers to: concept / concept_id
A foreign key that refers to a standard concept identifier in the vocabulary for the drug concept.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | drug_concept_id |
The end date for the current instance of drug utilization. It is not available from all sources.
date| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | drug_exposure_end_date |
A system-generated unique identifier for each drug utilization event.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | drug_exposure_id |
Total: 1
| Table | Field | Name |
|---|---|---|
| drug_cost | drug_exposure_id | fpk_drug_cost_id |
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.
date| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | drug_exposure_start_date |
Refers to: concept / concept_id
A foreign key to a drug concept that refers to the code used in the source.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | drug_source_concept_id |
The source code for the drug as it appears in the source data. This code is mapped to a standard drug concept in the vocabulary and the original code is, stored here for reference.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | drug_source_value |
Refers to: concept / concept_id
A foreign key to the predefined concept identifier in the vocabulary reflecting the type of drug exposure recorded. It indicates how the drug exposure was represented in the source data: as medication history, filled prescriptions, etc.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | drug_type_concept_id |
Numerical value of drug dose for this drug_exposure record.
number| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | effective_drug_dose |
An identifier to determine where the product originated
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | lot_number |
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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | person_id |
Refers to: provider / provider_id
A foreign key to the provider in the provider table who initiated (prescribed) the drug exposure.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | provider_id |
The quantity of drug as recorded in the original prescription or dispensing record.
number| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | quantity |
The number of refills after the initial prescription. The initial prescription is not counted, values start with 0.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | refills |
Refers to: concept / concept_id
A foreign key to a predefined concept in the Standardized Vocabularies reflecting the route of administration.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | route_concept_id |
The information about the route of administration as detailed in the source.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | route_source_value |
The directions (“signetur”) on the drug prescription as recorded in the original prescription (and printed on the container) or dispensing record.
clob| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | sig |
The reason the medication was stopped, where available. Reasons include regimen completed, changed, removed, etc.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | stop_reason |
Refers to: visit_occurrence / visit_occurrence_id
A foreign key to the visit in the visit table during which the drug exposure initiated.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | drug_exposure | visit_occurrence_id |
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
Refers to: concept / concept_id
The unit corresponding to the numeric value of the amount of the active ingredient contained within the product.
integerThe numeric value associated with the amount of active ingredient contained within the product, in situations when the ingredient is contained within a solid formulation.
numberRefers to: concept / concept_id
The denominator unit corresponding to the numeric value of the concentration of the active ingredient contained within the product.
integerThe denominator of 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.
numberRefers 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.
integerRefers 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.
integerReason the concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.
stringRefers to: concept / concept_id
The numerator unit corresponding to the numeric value of the concentration of the active ingredient contained within the product.
integerThe numerator of 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.
numberThe date when the concept became invalid because it was deleted or superseded (updated) by a new concept. The default value is 31-Dec-2099.
dateThe date when the concept was first recorded. The default value is 1-Jan-1970.
dateThe FACT_RELATIONSHIP table contains records to detail the relationships between facts within one domain or across two domains, and the nature of the relationship. Examples of types of fact relationships include: person relationships (mother-child linkage), care site relationships (representing the hierarchical organization structure of facilities within health systems), drug exposures provided due to associated indicated condition, devices used during the course of an associated procedure, and measurements derived from an associated specimen. All relationships are directional, and each relationship is represented twice symmetrically within the fact relationship table. For example, two persons (PERSON_ID = 1 is the mother of PERSON_ID = 2) have two fact relationships: 1- ‘PERSON_ID 1’ ‘parent of’ ‘PERSON_ID 2’, and 2- ‘PERSON_ID 2’ ‘child of’ ‘PERSON_ID 1’.
Fields
Refers to: concept / concept_id
The concept representing the domain of fact one, from which the corresponding table can be inferred.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | fact_relationship | domain_concept_id_1 |
Refers to: concept / concept_id
The concept representing the domain of fact two, from which the corresponding table can be inferred.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | fact_relationship | domain_concept_id_2 |
The unique identifier in the table corresponding to the domain of fact one.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | fact_relationship | fact_id_1 |
The unique identifier in the table corresponding to the domain of fact two.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | fact_relationship | fact_id_2 |
Refers to: concept / concept_id
A foreign key to a standard concept identifier of relationship in the Standardized Vocabularies.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | fact_relationship | relationship_concept_id |
The LOCATION table represents a generic way to capture physical location or address information. Locations are used to define the addresses for Persons and Care Sites.
Fields
The address field 1, typically used for the street address, as it appears in the source data.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | location | address_1 |
The address field 2, typically used for additional detail such as buildings, suites, floors, as it appears in the source data.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | location | address_2 |
The city field as it appears in the source data.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | location | city |
The county. The county information is necessary because not all zip codes fall into one and the same county.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | location | county |
A system-generated unique identifier for each geographic location.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | location | location_id |
Total: 2
| Table | Field | Name |
|---|---|---|
| care_site | location_id | fpk_care_site_location |
| person | location_id | fpk_person_location |
The verbatim information that is used to uniquely identify the location as it appears in the source data.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | location | location_source_value |
The state field as it appears in the source data.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | location | state |
The zip code. For US addresses, valid zip codes can be 3, 5 or 9 digits long, depending on the source data.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | location | zip |
A measurement is the capture of a structured value (numerical or categorical) obtained through systematic examination of a person or sample. The MEASUREMENT table captures measurement orders and measurement results. The measurement domain can contain laboratory results, vital signs, or quantitative findings from pathology reports.
Fields
Refers to: concept / concept_id
A foreign key to the standard measurement concept identifier in the Standardized Vocabularies.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | measurement_concept_id |
The date of the Measurement.
date| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | measurement_date |
A unique identifier for each measurement.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | measurement_id |
Refers to: concept / concept_id
A foreign key to a concept that refers to the code used in the source.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | measurement_source_concept_id |
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.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | measurement_source_value |
The time of the Measurement
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | measurement_time |
Refers to: concept / concept_id
A foreign key to the predefined concept identifier in the Standardized Vocabularies reflecting the type of data on which the measurement record is based.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | measurement_type_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 <, ≤, =, ≥, >
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | operator_concept_id |
A foreign key identifier to the person about whom the measurement was recorded. The demographic details of that person are stored in the person table.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | person_id |
Refers to: provider / provider_id
A foreign key to the provider in the provider table who was responsible for making the measurement.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | provider_id |
The upper limit of the normal range of the measurement. The lower range is assumed to be in the same units of measure as the measurement value.
number| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | range_high |
The lower limit of the normal range of the measurement. The lower range is assumed to be in the same units of measure as the measurement value.
number| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | range_low |
Refers to: concept / concept_id
A foreign key to a standard concept identifier of measurement units in the Standardized Vocabularies.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | unit_concept_id |
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.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | unit_source_value |
Refers to: concept / concept_id
A foreign key to a measurement stored as a concept identifier. This is applicable to measurements where the result can be expressed as a standard concept from the Standardized Vocabularies (e.g., positive/negative, present/absent, low/high, etc.).
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | value_as_concept_id |
A measurement stored as a number. This is applicable to measurement where the result is expressed as a numeric value.
number| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | value_as_number |
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 to produce the structured value.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | value_source_value |
Refers to: visit_occurrence / visit_occurrence_id
A foreign key to the visit in the visit table during which the measurement was recorded.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | measurement | visit_occurrence_id |
The NOTE table captures unstructured information that was recorded by a provider or a patient in free text notes on a given date.
Fields
The date the note was recorded.
dateA unique identifier for each note.
integerThe source value associated with the origin of the note, as standardized using the note_concept_id
stringThe content of the note.
clobThe time the note was recorded.
stringRefers to: concept / concept_id
A foreign key to the predefined concept identifier in the Standardized Vocabularies reflecting the type data from which the note.
integerA foreign key identifier to the person about whom the note was recorded. The demographic details of that person are stored in the person table.
integerRefers to: provider / provider_id
A foreign key to the provider in the provider table who was responsible for taking the note.
integerRefers to: visit_occurrence / visit_occurrence_id
Foreign key to visit
integerThe OBSERVATION table captures any clinical facts about a patient obtained in the context of examination, questioning or a procedure. The observation domain supports capture of data not represented by other domains, including unstructured measurements, medical history and family history.
Fields
Refers to: concept / concept_id
A foreign key to the standard observation concept identifier in the vocabulary.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | observation_concept_id |
The date of the observation.
date| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | observation_date |
A system-generated unique identifier for each observation.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | observation_id |
Refers to: concept / concept_id
A foreign key to a concept that refers to the code used in the source.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | observation_source_concept_id |
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.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | observation_source_value |
The time of the observation.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | observation_time |
Refers to: concept / concept_id
A foreign key to the predefined concept identifier in the vocabulary reflecting the type of the observation.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | observation_type_concept_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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | person_id |
Refers to: provider / provider_id
A foreign key to the provider in the provider table who was responsible for making the observation.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | provider_id |
Refers to: concept / concept_id
A foreign key to a standard concept identifier for a qualifier (e.g., severity of drug-drug interaction alert)
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | qualifier_concept_id |
The source value associated with a qualifier to characterize the observation
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | qualifier_source_value |
Refers to: concept / concept_id
A foreign key to a standard concept identifier of measurement units in the vocabulary.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | unit_concept_id |
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.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | unit_source_value |
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.).
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | value_as_concept_id |
The observation result stored as a number. This is applicable to observations where the result is expressed as a numeric value.
number| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | value_as_number |
The observation result stored as a varchar. This is applicable to observations where the result is expressed as verbatim text, such as in radiology or pathology reports.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | value_as_string |
Refers to: visit_occurrence / visit_occurrence_id
A foreign key to the visit in the visit table during which the observation was recorded.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation | visit_occurrence_id |
The OBSERVATION_PERIOD table contains records which uniquely define the spans of time for which a person is at-risk to have clinical events recorded within the source systems. One person may have one or more disjoint observation periods, during which times analyses may assume that clinical events would be captured if observed, and outside of which no clinical events may be recorded.
Fields
The end date of the observation period for which data are available from the data source.
date| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation_period | observation_period_end_date |
A system-generated unique identifier for each observation period.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation_period | observation_period_id |
The start date of the observation period for which data are available from the data source.
date| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation_period | observation_period_start_date |
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
integerA foreign key identifier to the person for whom the observation period is defined. The demographic details of that person are stored in the person table.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | observation_period | person_id |
The PAYER_PLAN_PERIOD table captures records that detail the period of time that a person is continuously enrolled under a specific health plan benefit structure from a given payer. Each Person receiving health care and covered by a health benefits is subject to a Plan defined by the Payer for the Person or her family. For a given benefit policy, there may be one or more Plans that are active for certain periods of time (e.g. before and after the deductible is reached), determining the cost of health services provided.
Fields
The source code for the person’s family as it appears in the source data.
stringThe end date of the payer plan period.
dateAn identifier for each unique combination of payer, plan, family code and time span.
integerTotal: 4
| Table | Field | Name |
|---|---|---|
| device_cost | payer_plan_period_id | fpk_device_cost_period |
| drug_cost | payer_plan_period_id | fpk_drug_cost_period |
| procedure_cost | payer_plan_period_id | fpk_procedure_cost_period |
| visit_cost | payer_plan_period_id | fpk_visit_cost_period |
The start date of the payer plan period.
dateThe source code for the payer as it appears in the source data.
stringA foreign key identifier to the person covered by the payer. The demographic details of that person are stored in the person table.
integerThe source code for the person’s coverage plan as it appears in the source data.
stringThe PERSON table contains records that uniquely identify each patient in the source data who has time at-risk to have clinical events recorded within the source systems. A person must have at least one observation period to defined the time-at-risk but may or may not have any clinical events recorded in the other data domains. Each person record has associated demographic attributes which are assumed to be constant for the patient throughout the course of their periods of observation. All other patient-level data domains have a foreign-key reference to the person domain.
Fields
Refers to: care_site / care_site_id
A foreign key to the primary care site in the care site table, where the details of the care site are stored.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | care_site_id |
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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | day_of_birth |
Refers to: concept / concept_id
A foreign key that refers to the standard concept identifier in the vocabulary for the ethnicity of the person.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | ethnicity_concept_id |
Refers to: concept / concept_id
A foreign key to the ethnicity concept that refers to the code used in the source.
integerThe 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.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | ethnicity_source_value |
Refers to: concept / concept_id
A foreign key that refers to a standard concept identifier in the vocabulary for the gender of the person.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | gender_concept_id |
Refers to: concept / concept_id
A foreign key to the gender concept that refers to the code used in the source.
integerThe source code for the gender of the person as it appears in the source data. The person gender is mapped to a standard gender concept in the vocabulary and the corresponding concept identifier is, stored here for reference.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | gender_source_value |
Refers to: location / location_id
A foreign key to the place of residency for the person in the location table, where the detailed address information is stored.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | location_id |
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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | month_of_birth |
A system-generated unique identifier for each person.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | person_id |
Total: 15
| Table | Field | Name |
|---|---|---|
| condition_era | person_id | fpk_condition_era_person |
| condition_occurrence | person_id | fpk_condition_person |
| death | person_id | fpk_death_person |
| device_exposure | person_id | fpk_device_person |
| dose_era | person_id | fpk_dose_era_person |
| drug_era | person_id | fpk_drug_era_person |
| drug_exposure | person_id | fpk_drug_person |
| measurement | person_id | fpk_measurement_person |
| note | person_id | fpk_note_person |
| observation | person_id | fpk_observation_person |
| observation_period | person_id | fpk_observation_period_person |
| payer_plan_period | person_id | fpk_payer_plan_period |
| procedure_occurrence | person_id | fpk_procedure_person |
| specimen | person_id | fpk_specimen_person |
| visit_occurrence | person_id | fpk_visit_person |
An encrypted key derived from the person identifier in the source data. This is necessary when a drug safety issue requires a link back to the person data at the source dataset. No value with any medical or demographic significance must be stored.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | person_source_value |
Refers to: provider / provider_id
A foreign key to the primary care provider the person is seeing in the provider table.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | provider_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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | race_concept_id |
Refers to: concept / concept_id
A foreign key to the race concept that refers to the code used in the source.
integerThe 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 code is, stored here for reference.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | race_source_value |
The time of birth at the birth day
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | time_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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | person | year_of_birth |
The PROCEDURE_COST table captures the cost of a Procedure performed on a Person. The information about the cost is only derived from the amounts paid for the Procedure.
Fields
Refers to: concept / concept_id
A concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar.
integerThe amount paid by a secondary payer through the coordination of benefits.
numberThe amount paid by the payer (insurer). If there is more than one payer, several procedure_cost records indicate that fact.
numberThe amount paid by the person as a joint assumption of risk. Typically, this is a percentage of the expenses defined by the payer plan (policy) after the person’s deductible is exceeded.
numberThe amount paid by the person as a fixed contribution to the expenses. Copay does not contribute to the out_of_pocket expenses.
numberThe amount paid by the person that is counted toward the deductible defined by the payer plan (policy).
numberRefers to: payer_plan_period / payer_plan_period_id
A foreign key to the payer_plan_period table, where the details of the payer, plan and family are stored.
integerA system-generated unique identifier for each procedure cost record.
integerRefers to: procedure_occurrence / procedure_occurrence_id
A foreign key identifier to the procedure record for which cost data are recorded.
integerRefers to: concept / concept_id
A foreign key referring to a standard concept identifier in the vocabulary for revenue codes.
integerThe source code for the revenue code as it appears in the source data, stored here for reference.
stringThe total amount paid by the person as a share of the expenses, excluding the copay.
numberThe total amount paid for the expenses of the procedure.
numberThe PROCEDURE_OCCURRENCE table contains records of activities or processes ordered by and/or carried out by a healthcare provider on the patient to have a diagnostic and/or therapeutic purpose.
Fields
Refers to: concept / concept_id
A foreign key to a standard concept identifier for a modifier to the procedure (e.g. bilateral)
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | procedure_occurrence | modifier_concept_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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | procedure_occurrence | person_id |
Refers to: concept / concept_id
A foreign key that refers to a standard procedure concept identifier in the vocabulary.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | procedure_occurrence | procedure_concept_id |
The date on which the procedure was performed.
date| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | procedure_occurrence | procedure_date |
A system-generated unique identifier for each procedure occurrence.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | procedure_occurrence | procedure_occurrence_id |
Total: 1
| Table | Field | Name |
|---|---|---|
| procedure_cost | procedure_occurrence_id | fpk_procedure_cost_id |
Refers to: concept / concept_id
A foreign key to a procedure concept that refers to the code used in the source.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | procedure_occurrence | procedure_source_concept_id |
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, CPT-4 or HCPCS codes.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | procedure_occurrence | procedure_source_value |
Refers to: concept / concept_id
The date on which the procedure was performed.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | procedure_occurrence | procedure_type_concept_id |
Refers to: provider / provider_id
A foreign key to the provider in the provider table who was responsible for carrying out the procedure.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | procedure_occurrence | provider_id |
The source code for the qualifier as it appears in the source data.
stringThe quantity of procedures ordered or administered.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | procedure_occurrence | quantity |
Refers to: visit_occurrence / visit_occurrence_id
A foreign key to the visit in the visit table during which the procedure was carried out.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | procedure_occurrence | visit_occurrence_id |
The PROVIDER table contains a list of uniquely identified health care providers. These are typically physicians and nurses.
Fields
Refers to: care_site / care_site_id
A foreign key to the main care site where the provider is practicing.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | provider | care_site_id |
The Drug Enforcement Administration (DEA) number of the provider.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | provider | dea |
Refers to: concept / concept_id
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | provider | gender_concept_id |
Refers to: concept / concept_id
A foreign key to a concept that refers to the code used in the source.
integerstring| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | provider | gender_source_value |
The National Provider Identifier (NPI) of the provider.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | provider | npi |
A system-generated unique identifier for each provider.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | provider | provider_id |
Total: 9
| Table | Field | Name |
|---|---|---|
| condition_occurrence | provider_id | fpk_condition_provider |
| device_exposure | provider_id | fpk_device_provider |
| drug_exposure | provider_id | fpk_drug_provider |
| measurement | provider_id | fpk_measurement_provider |
| note | provider_id | fpk_note_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 |
A description of the provider
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | provider | provider_name |
The identifier used for the provider in the source data, stored here for reference.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | provider | provider_source_value |
Refers to: concept / concept_id
A foreign key to a standard provider’s specialty concept identifier in the vocabulary.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | provider | specialty_concept_id |
Refers to: concept / concept_id
A foreign key to a concept that refers to the code used in the source.
integerThe source code for the provider specialty as it appears in the source data, stored here for reference.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | provider | specialty_source_value |
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | provider | year_of_birth |
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 whether a hierarchical relationship contributes to the concept_ancestor table. These are subsets of the hierarchical relationships. Valid values are 1 or 0.
stringDefines whether a relationship defines concepts into classes or hierarchies. Values are 1 for hierarchical relationship or 0 if not.
stringRefers to: concept / concept_id
A foreign key that refers to a standard concept identifier in the Standardized Vocabularies for the relationship concept.
integerThe type of relationship captured by the relationship record.
stringTotal: 2
| Table | Field | Name |
|---|---|---|
| concept_relationship | relationship_id | fpk_concept_relationship_id |
| relationship | reverse_relationship_id | fpk_relationship_reverse |
The text that describes the relationship type.
stringRefers to: relationship / relationship_id
The identifier for the relationship used to define the reverse relationship between two concepts.
stringThe 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
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.
stringThe source code being translated into a standard concept.
stringAn 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.
stringA foreign key to the source concept to which the source code is being mapped.
integerRefers 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.
stringRefers to: concept / concept_id
A foreign key to the concept to which the source code is being mapped.
integerRefers to: vocabulary / vocabulary_id
A foreign key to the vocabulary table defining the vocabulary of the target concept.
stringThe date when the mapping instance became invalid because it was deleted or superseded (updated) by a new relationship. Default value is 31-Dec-2099.
dateThe date when the mapping instance was first recorded.
dateThe SPECIMEN table contains the records identifying each biological sample from a person.
Fields
Refers to: concept / concept_id
A foreign key to a standard concept identifier for the anatomic location of specimen collection.
integerThe information about the anatomic site as detailed in the source.
stringRefers to: concept / concept_id
A foreign key to a standard concept identifier for the disease status of specimen collection.
integerThe information about the disease status as detailed in the source.
stringA foreign key identifier to the person for whom the specimen is recorded.
integerThe amount of specimen collection from the person during the sampling procedure
numberRefers to: concept / concept_id
A foreign key referring to a standard concept identifier in the Standardized Vocabularies for the specimen.
integerThe date the specimen was obtained from the person.
dateA unique identifier for each specimen.
integerThe specimen identifier as it appears in the source data.
stringThe specimen value as it appears in the source data. This value is mapped to a standard concept in the Standardized Vocabularies and the original code is, stored here for reference.
stringThe time on the date when the specimen was obtained from the person.
stringRefers to: concept / concept_id
A foreign key referring to the predefined concept identifier in the Standardized Vocabularies reflecting the system of record from which the specimen was represented in the source data.
integerRefers to: concept / concept_id
A foreign key to a standard concept identifier for the unit associated with the numeric quantity of the specimen collection.
integerThe information about the unit as detailed in the source.
stringThe VISIT_COST table captures the costs of health visit of a patient which are not itemized to specific procedures, drugs, or devices used within the encounter.
Fields
Refers to: concept / concept_id
A concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar.
integerThe amount paid by a secondary payer through the coordination of benefits.
numberThe amount paid by the payer (insurer). If there is more than one payer, several visit_cost records indicate that fact.
numberThe amount paid by the person as a joint assumption of risk. Typically, this is a percentage of the expenses defined by the payer plan (policy) after the person’s deductible is exceeded.
numberThe amount paid by the person as a fixed contribution to the expenses. Copay does not contribute to the out_of_pocket expenses.
numberThe amount paid by the person that is counted toward the deductible defined by the payer plan (policy).
numberRefers to: payer_plan_period / payer_plan_period_id
A foreign key to the payer_plan_period table, where the details of the payer, plan and family are stored.
integerThe total amount paid by the person as a share of the expenses, excluding the copay.
numberThe total amount paid for the expenses of the procedure.
numberA unique identifier for each procedure cost record.
integerRefers to: visit_occurrence / visit_occurrence_id
A foreign key identifier to the procedure record for which cost data are recorded.
integerThe VISIT_OCCURRENCE table contains the spans of time a person continuously receives medical services from one or more providers at a facility in a given setting within the health care system. Visits are classified into 4 settings: outpatient care, inpatient confinement, emergency room, and long- term care. Persons may transition between these settings over the course of an episode of care. Inpatient visits are defined by the span of time between admission and discharge from a specific hospital facility. Outpatient visits are defined as span of time within a specific provider’s office, which is expected to less than 1 day. Long-term care visits are defined as the span of time a person is treated within a specific long-term care facility.
Fields
Refers to: care_site / care_site_id
A foreign key to the care site in the care site table that was visited.
integerA foreign key identifier to the person for whom the visit is recorded. The demographic details of that person are stored in the person table.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | visit_occurrence | person_id |
Refers to: provider / provider_id
A foreign key to the provider in the provider table who was associated with the visit.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | visit_occurrence | provider_id |
Refers to: concept / concept_id
A foreign key that refers to a visit concept identifier in the Standardized Vocabularies.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | visit_occurrence | visit_concept_id |
The end date of the visit. If this is a one-day visit the end date should match the start date.
date| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | visit_occurrence | visit_end_date |
The time the visit ended.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | visit_occurrence | visit_end_time |
A system-generated unique identifier for each person’s visit or encounter at a healthcare provider.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | visit_occurrence | visit_occurrence_id |
Total: 8
| Table | Field | Name |
|---|---|---|
| condition_occurrence | visit_occurrence_id | fpk_condition_visit |
| device_exposure | visit_occurrence_id | fpk_device_visit |
| drug_exposure | visit_occurrence_id | fpk_drug_visit |
| measurement | visit_occurrence_id | fpk_measurement_visit |
| note | visit_occurrence_id | fpk_note_visit |
| observation | visit_occurrence_id | fpk_observation_visit |
| procedure_occurrence | visit_occurrence_id | fpk_procedure_visit |
| visit_cost | visit_occurrence_id | fpk_visit_cost_id |
Refers to: concept / concept_id
A foreign key to a concept that refers to the code used in the source.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | visit_occurrence | visit_source_concept_id |
The source code used to reflect the type or source of the visit in the source data.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | visit_occurrence | visit_source_value |
The start date of the visit.
date| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | visit_occurrence | visit_start_date |
The time the visit started.
string| Model | Table | Field | Comment |
|---|---|---|---|
| PEDSnet v2 | visit_occurrence | visit_start_time |
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.
integerThe 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
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.
integerA unique identifier for each vocabulary.
stringTotal: 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 |
The name describing the vocabulary, for example “SNOMED-CT”, “ICD-9”, “Visit”, etc.
stringThe name describing the vocabulary, for example “SNOMED-CT”, “ICD-9”, “Visit”, etc.
stringExternal reference to documentation or available download of the about the vocabulary.
string