Information about the site of care
Fields
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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | care_site | care_site_name |
The identifier for the organization in the source data, stored here for reference.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | care_site | care_site_source_value |
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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | care_site | location_id |
Refers to: concept / concept_id
A foreign key that refers to a place of service concept identifier in the Vocabulary
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | care_site | place_of_service_source_value |
Refers to: concept / concept_id
The specialty of the department linked to a standard specialty concept as it appears in the Vocabulary
integerThe source code for the specialty as it appears in the source data, stored here for reference.
stringThe 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: 63
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).
integerAn 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.
stringRefers to: concept / concept_id
A foreign key to a concept representing the language.
integerA diagnosis or condition that has been recorded about a person at a certain time
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 |
|---|---|---|---|
| OMOP v5 | condition_occurrence | condition_concept_id |
The date when the instance of the condition is considered to have ended. If this information is not available, set to NULL.
datetime| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | condition_occurrence | condition_end_date |
The date and time when the instance of the condition is considered to have ended
datetimeA unique identifier for each condition occurrence event.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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/visit diagnosis codes from EHRs.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | condition_occurrence | condition_source_value |
The date when the instance of the condition is recorded.
datetime| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | condition_occurrence | condition_start_date |
The date and time when the instance of the condition is recorded.
datetimeRefers 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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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. Note that a stop_reason does not necessarily imply that the condition is no longer occurring.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | condition_occurrence | visit_occurrence_id |
Time and cause of death of the Person
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 vocbaulary concept that refers to the code used in the source.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 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.
date| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | death | death_date |
The date the person was deceased.
datetimeRefers 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | death | person_id |
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
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.
stringThe drug exposure domain captures any biochemical substance that is introduced in any way to a patient.
Fields
The number of days of supply the medication as recorded in the original prescription or dispensing record.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | drug_exposure | days_supply |
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
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | drug_exposure | dose_unit_concept_id |
The information about the dose unit as detailed in the source
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | drug_exposure | dose_unit_source_value |
Refers to: concept / concept_id
A foreign key that refers to a standard drug concept identifier in the Vocabulary.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | drug_exposure | drug_exposure_end_date |
The end date and time of the utilization of the drug
datetimeA system-generated unique identifier for each drug utilization event.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | drug_exposure | drug_exposure_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 |
|---|---|---|---|
| OMOP v5 | drug_exposure | drug_exposure_start_date |
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.
datetimeRefers 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 |
|---|---|---|---|
| OMOP v5 | drug_exposure | drug_source_concept_id |
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.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | drug_exposure | drug_source_value |
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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | drug_exposure | drug_type_concept_id |
Numerical value of drug dose for this drug_exposure record
number| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | drug_exposure | effective_drug_dose |
An identifier to determine where the product originated
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | drug_exposure | provider_id |
The quantity of the drugs as recorded in the original prescription or dispensing record.
number| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | drug_exposure | quantity |
The number of refills after the initial prescrition.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | drug_exposure | refills |
Refers to: concept / concept_id
A foreign key that refers to a standard administration route concept identifier in the Vocabulary.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | drug_exposure | route_concept_id |
The information about the route of administration as detailed in the source
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | drug_exposure | route_source_value |
The directions on the drug prescription as recorded in the original prescription (and printed on the container) or the dispensing record
clob| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | drug_exposure | sig |
The reason, if available, where the medication was stopped, as indicated in the source data.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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.
integerRefers 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 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 domain contains details of the relationships between facts within one domain or across two domains, and the nature of the relationship.
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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | fact_relationship | domain_concept_id_2 |
The unique identifier in the table corresponding to the domain of fact one.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | fact_relationship | fact_id_1 |
The unique identifier in the table corresponding to the domain of fact two.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | fact_relationship | relationship_concept_id |
Physical addresses of patients, organizations and care sites
Fields
Optional - Do not transmit to DCC
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | location | address_1 |
Optional - Do not transmit to DCC
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | location | address_2 |
Optional - Do not transmit to DCC
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | location | city |
Optional - Do not transmit to DCC
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | location | county |
A unique identifier for each geographic location.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | location | location_source_value |
The state field as it appears in the source data.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | location | zip |
The measurement domain captures measurement orders and measurement results. The measurement domain can contain laboratory results and vital signs.
Fields
Refers to: concept / concept_id
A foreign key to the standard measurement concept identifier in the Vocabulary.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | measurement | measurement_concept_id |
The date of the measurement.
date| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | measurement | measurement_date |
A system-generated unique identifier for each measurement
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | measurement | measurement_source_value |
The time of the measurement.
datetime| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | measurement | measurement_time |
Refers to: concept / concept_id
A foreign key to the predefined concept identifier in the Vocabulary reflecting the type of the measurement.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | measurement | operator_concept_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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | measurement | provider_id |
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.
number| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | measurement | range_high |
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.
number| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | measurement | range_low |
Refers to: concept / concept_id
A foreign key to a standard concept identifier of measurement units in the Vocabulary.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | measurement | 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 |
|---|---|---|---|
| OMOP v5 | measurement | value_as_concept_id |
The measurement result stored as a number. This is applicable to measurements where the result is expressed as a numeric value.
number| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | measurement | value_source_value |
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 |
|---|---|---|---|
| OMOP v5 | measurement | visit_occurrence_id |
Observations are clinical facts, such as laboratory tests, signs/symptoms, which are not captured within other CDM tables
Fields
Refers to: concept / concept_id
A foreign key to the standard observation concept identifier in the Vocabulary.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | observation | observation_concept_id |
The date of the observation.
date| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | observation | observation_date |
A unique identifier for each observation.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | observation | observation_source_value |
The time of the observation.
datetime| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | observation | provider_id |
Refers to: concept / concept_id
A foreign key to standard concept identifier for a qualifier (e.g severity of drug-drug interaction alert)
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | observation | qualifier_concept_id |
The source value associated with a qualifier to characterize the observation
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | observation | value_as_number |
The observation result stored as a string. This is applicable to observations where the result is expressed as verbatim text.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | observation | visit_occurrence_id |
Time intervals during which health care information, such as drugs, conditions, and other clinical observations, may be available
Fields
The end date of the observation period for which data are available from the source.
date| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | observation_period | observation_period_end_date |
The end date of the observation period for which data are available from the source.
datetimeA system-generate unique identifier for each observation period
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | observation_period | observation_period_start_date |
The start date of the observation period for which data are available from the data source
datetimeRefers 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 who is experiencing the condition. The demographic details of that person are stored in the person table.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | observation_period | person_id |
Demographic information about a Person
Fields
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
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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’s gender is mapped to a standard gender concept in the Vocabulary; the original value is stored here for reference.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | person | gender_source_value |
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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | person | month_of_birth |
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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | person | person_id |
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 |
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.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | person | person_source_value |
The post-menstrual age in weeks of the person at birth, if known.
numberRefers to: provider / provider_id
Foreign key to the primary care provider – the person is seeing in the provider table.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 value is stored here for reference.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | person | race_source_value |
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.
datetime| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | person | year_of_birth |
Procedures carried out on the Person
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 |
|---|---|---|---|
| OMOP v5 | procedure_occurrence | modifier_concept_id |
The source code for the modifier as it appears in the source data.
stringA 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | procedure_occurrence | procedure_concept_id |
The date on which the procedure was performed.
date| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | procedure_occurrence | procedure_date |
A system-generated unique identifier for each procedure occurrence. Sites can use any integer- DCC will do a substitution.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | procedure_occurrence | procedure_occurrence_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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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, ICD-10-Proc, CPT-4, HCPCS or OPCS-4 codes.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | procedure_occurrence | procedure_source_value |
The date and time on which the procedure was performed. If there is no time associated with the date assert midnight.
datetimeRefers 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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | procedure_occurrence | visit_occurrence_id |
Information about health care providers
Fields
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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | provider | care_site_id |
The Drug Enforcement Administration (DEA) number of the provider. Optional – Do not transmit to DCC.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | provider | dea |
Refers to: concept / concept_id
The gender of the provider
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | provider | gender_concept_id |
Refers to: concept / concept_id
A foreign key to a concept that refers to the code used in the source.
integerThe source value for the provider gender.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | provider | gender_source_value |
The National Provider Identifier (NPI) of the provider. Optional – Do not transmit to DCC.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | provider | npi |
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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | provider | provider_id |
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 |
A description of the provider.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | provider | provider_name |
The identifier used for the provider in the source data, stored here for reference. Sites should create a random ID, but keep the mapping.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | provider | provider_source_value |
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.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 |
|---|---|---|---|
| OMOP v5 | provider | specialty_source_value |
The year of birth of the provider
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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.
stringRefers to: concept / concept_id
A 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.
dateVisits for health care services of the Person
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 |
|---|---|---|---|
| OMOP v5 | 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. 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).
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | visit_occurrence | provider_id |
Refers to: concept / concept_id
A foreign key that refers to a place of service concept identifier in the vocabulary.
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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. If the encounter is on-going at the time of ETL, this should be null.
date| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | visit_occurrence | visit_end_date |
The end time of the visit.
datetime| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | visit_occurrence | visit_end_time |
A unique identifier for each person’s visits or encounter at a healthcare provider. Sites can provide whatever integers (DCC will replace the value).
integer| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | visit_occurrence | visit_occurrence_id |
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 |
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 |
|---|---|---|---|
| OMOP v5 | visit_occurrence | visit_source_concept_id |
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.
string| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | visit_occurrence | visit_source_value |
The start date of the visit.
date| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | visit_occurrence | visit_start_date |
The start time of the visit.
datetime| Model | Table | Field | Comment |
|---|---|---|---|
| OMOP v5 | 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 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
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
stringThe untransformed payer/plan name from the source data
stringA standardized interpretation of the plan structure; proposed value set would be HMO, PPO, POS, Fee for service, Other/unknown
stringRefers to: visit_occurrence / visit_occurrence_id
A foreign key to the visit in the visit table where the payer was billed for the visit.
integerA system-generated unique identifier for each visit payer relationship.
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