The ATTRIBUTE_DEFINITION table contains records to define each attribute through an associated description syntax.
- -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.
- -integerInformation about the site of care
- -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.
- -integerTotal: 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.
- -stringThe identifier for the care site as it appears in the source data, stored here for reference.
- -stringRefers to: location / location_id
- -A foreign key to the geographic location in the location table, where the detailed address information is stored.
- -integerRefers to: concept / concept_id
- -A foreign key to the predefined concept identifier in the vocabulary reflecting the place of service.
- -integerThe source code for the place of service as it appears in the source data, stored here for reference.
- -stringThe CDM_SOURCE table contains detail about the source database and -the process used to transform the data into the OMOP common data model.
- -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.
- -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 assoicated with each -subject within a cohort, as defined by a given set of inclusion criteria - for a duration of time.
- -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.
- -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: 86
- -| Table | -Field | -Name | -
|---|---|---|
| care_site | -place_of_service_concept_id | -fpk_care_site_place | -
| cohort_attribute | -value_as_concept_id | -fpk_ca_value | -
| cohort_definition | -definition_type_concept_id | -fpk_cohort_definition_concept | -
| concept_ancestor | -ancestor_concept_id | -fpk_concept_ancestor_concept_1 | -
| concept_ancestor | -descendant_concept_id | -fpk_concept_ancestor_concept_2 | -
| concept_class | -concept_class_concept_id | -fpk_concept_class_concept | -
| concept_relationship | -concept_id_1 | -fpk_concept_relationship_c_1 | -
| concept_relationship | -concept_id_2 | -fpk_concept_relationship_c_2 | -
| concept_synonym | -concept_id | -fpk_concept_synonym_concept | -
| condition_era | -condition_concept_id | -fpk_condition_era_concept | -
| condition_occurrence | -condition_concept_id | -fpk_condition_concept | -
| condition_occurrence | -condition_source_concept_id | -fpk_condition_concept_s | -
| condition_occurrence | -condition_type_concept_id | -fpk_condition_type_concept | -
| condition_occurrence | -condition_status_concept_id | -fpk_condition_status_concept | -
| death | -cause_concept_id | -fpk_death_cause_concept | -
| death | -cause_source_concept_id | -fpk_death_cause_concept_s | -
| death | -death_type_concept_id | -fpk_death_type_concept | -
| device_exposure | -device_concept_id | -fpk_device_concept | -
| device_exposure | -device_source_concept_id | -fpk_device_concept_s | -
| device_exposure | -device_type_concept_id | -fpk_device_type_concept | -
| domain | -domain_concept_id | -fpk_domain_concept | -
| dose_era | -drug_concept_id | -fpk_dose_era_concept | -
| dose_era | -unit_concept_id | -fpk_dose_era_unit_concept | -
| drug_era | -drug_concept_id | -fpk_drug_era_concept | -
| drug_exposure | -dose_unit_concept_id | -fpk_drug_dose_unit_concept | -
| drug_exposure | -drug_concept_id | -fpk_drug_concept | -
| drug_exposure | -drug_source_concept_id | -fpk_drug_concept_s | -
| drug_exposure | -drug_type_concept_id | -fpk_drug_type_concept | -
| drug_exposure | -route_concept_id | -fpk_drug_route_concept | -
| drug_strength | -amount_unit_concept_id | -fpk_drug_strength_unit_1 | -
| drug_strength | -denominator_unit_concept_id | -fpk_drug_strength_unit_3 | -
| drug_strength | -drug_concept_id | -fpk_drug_strength_concept_1 | -
| drug_strength | -ingredient_concept_id | -fpk_drug_strength_concept_2 | -
| drug_strength | -numerator_unit_concept_id | -fpk_drug_strength_unit_2 | -
| fact_relationship | -domain_concept_id_1 | -fpk_fact_domain_1 | -
| fact_relationship | -domain_concept_id_2 | -fpk_fact_domain_2 | -
| fact_relationship | -relationship_concept_id | -fpk_fact_relationship | -
| measurement | -measurement_concept_id | -fpk_measurement_concept | -
| measurement | -measurement_source_concept_id | -fpk_measurement_concept_s | -
| measurement | -measurement_type_concept_id | -fpk_measurement_type_concept | -
| measurement | -operator_concept_id | -fpk_measurement_operator | -
| measurement | -unit_concept_id | -fpk_measurement_unit | -
| measurement | -value_as_concept_id | -fpk_measurement_value | -
| note | -note_type_concept_id | -fpk_note_type_concept | -
| note | -note_class_concept_id | -fpk_note_class_concept | -
| note | -encoding_concept_id | -fpk_note_encoding_concept | -
| note | -language_concept_id | -fpk_note_language_concept | -
| observation | -observation_concept_id | -fpk_observation_concept | -
| observation | -observation_source_concept_id | -fpk_observation_concept_s | -
| observation | -observation_type_concept_id | -fpk_observation_type_concept | -
| observation | -qualifier_concept_id | -fpk_observation_qualifier | -
| observation | -unit_concept_id | -fpk_observation_unit | -
| observation | -value_as_concept_id | -fpk_observation_value | -
| observation_period | -period_type_concept_id | -fpk_observation_period_concept | -
| person | -ethnicity_concept_id | -fpk_person_ethnicity_concept | -
| person | -ethnicity_source_concept_id | -fpk_person_ethnicity_concept_s | -
| person | -gender_concept_id | -fpk_person_gender_concept | -
| person | -gender_source_concept_id | -fpk_person_gender_concept_s | -
| person | -race_concept_id | -fpk_person_race_concept | -
| person | -race_source_concept_id | -fpk_person_race_concept_s | -
| procedure_occurrence | -modifier_concept_id | -fpk_procedure_modifier | -
| procedure_occurrence | -procedure_concept_id | -fpk_procedure_concept | -
| procedure_occurrence | -procedure_source_concept_id | -fpk_procedure_concept_s | -
| procedure_occurrence | -procedure_type_concept_id | -fpk_procedure_type_concept | -
| provider | -gender_concept_id | -fpk_provider_gender | -
| provider | -gender_source_concept_id | -fpk_provider_gender_s | -
| provider | -specialty_concept_id | -fpk_provider_specialty | -
| provider | -specialty_source_concept_id | -fpk_provider_specialty_s | -
| relationship | -relationship_concept_id | -fpk_relationship_concept | -
| source_to_concept_map | -target_concept_id | -fpk_source_to_concept_map_c_1 | -
| specimen | -anatomic_site_concept_id | -fpk_specimen_site_concept | -
| specimen | -disease_status_concept_id | -fpk_specimen_status_concept | -
| specimen | -specimen_concept_id | -fpk_specimen_concept | -
| specimen | -specimen_type_concept_id | -fpk_specimen_type_concept | -
| specimen | -unit_concept_id | -fpk_specimen_unit_concept | -
| cost | -currency_concept_id | -fpk_visit_cost_currency | -
| cost | -cost_type_concept_id | -fpk_concept_type_cost_id | -
| cost | -cost_domain_id | -fpk_domain_cost_id | -
| cost | -revenue_code_concept_id | -fpk_rev_code_cost_id | -
| cost | -drg_concept_id | -fpk_drg_cost_id | -
| visit_occurrence | -visit_concept_id | -fpk_visit_concept | -
| visit_occurrence | -visit_source_concept_id | -fpk_visit_concept_s | -
| visit_occurrence | -visit_type_concept_id | -fpk_visit_type_concept | -
| visit_occurrence | -admitting_source_concept_id | -fpk_visit_adm_src_concept | -
| visit_occurrence | -discharge_to_concept_id | -fpk_visit_disch_concept | -
| vocabulary | -vocabulary_concept_id | -fpk_vocabulary_concept | -
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. ‘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.
- -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.
- -integerThe date when the instance of the condition is considered to have ended.
- -dateThe date when the instance of the Condition is considered to have ended.
- -datetimeA system-generated unique identifier for each condition occurrence event.
- -integerRefers to: concept / concept_id
- -A foreign key to a condition concept that refers to the code used in the source.
- -integerThe 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.
- -stringThe date when the instance of the condition is recorded.
- -dateThe date and time when the instance of the Condition is recorded.
- -datetimeRefers to: concept / concept_id
- -A foreign key to the predefined concept in the standard vocabulary reflecting the condition status.
- -integerThe source code for condition status as it appears in the source data.
- -stringRefers 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.
- -integerA foreign key identifier to the person who is experiencing the -condition. 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 determining (diagnosing) the condition.
- -integerThe reason, if available, that the condition was no longer recorded, -as indicated in the source data. Valid values include discharged, -resolved, etc.
- -stringRefers to: visit_occurrence / visit_occurrence_id
- -A foreign key to the visit in the visit table during which the condition was determined (diagnosed).
- -integerThe COST table captures records containing the cost of any medical -entity recorded in one of the DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, -VISIT_OCCURRENCE or DEVICE_OCCURRENCE tables.
- -Fields
- -The contracted amount agreed between the payer and provider.
- -integerRefers to: concept / concept_id
- -The concept representing the domain of the cost event, from which the - corresponding table can be inferred that contains the entity for which -cost information is recorded.
- -integerA foreign key identifier to the event (e.g. Measurement, Procedure, -Visit, Drug Exposure, etc) record for which cost data are recorded.
- -integerA unique identifier for each procedure cost record.
- -integerRefers to: concept / concept_id
- -A foreign key identifier to a concept in the CONCEPT table for the -provenance or the source of the COST data: Calculated from insurance -claim information, provider revenue, calculated from cost-to-charge -ratio, reported from accounting database, etc.
- -integerRefers to: concept / concept_id
- -A concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar.
- -integerRefers to: concept / concept_id
- -A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for DRG codes.
- -integerThe source code for the 3-digit DRG source code as it appears in the source data, stored here for reference.
- -integerThe total amount paid by the Person as a share of the expenses.
- -integerThe amount paid by the payer (insurer). If there is more than one payer, several cost records indicate that fact.
- -integerThe amount paid by a primary Payer through the coordination of benefits.
- -integerThe amount paid by the Payer to a pharmacy for dispensing a drug, -excluding the amount paid for the drug ingredient. paid_dispensing_fee -contributes to the paid_by_payer field if this field is populated with a - nonzero value.
- -integerThe amount paid by the Payer to a pharmacy for the drug, excluding -the amount paid for dispensing the drug. paid_ingredient_cost -contributes to the paid_by_payer field if this field is populated with a - nonzero value.
- -integerThe 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.
- -integerThe amount paid by the person as a fixed contribution to the expenses. Copay does not contribute to the out_of_pocket expenses.
- -integerThe amount paid by the person that is counted toward the deductible defined by the payer plan (policy).
- -integerRefers 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.
- -integerRefers to: concept / concept_id
- -A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for Revenue codes.
- -integerThe source code for the Revenue code as it appears in the source data, stored here for reference.
- -stringThe total amount charged by some provider of goods or services (e.g. -hospital, physician pharmacy, dme provider) to payers (insurance -companies, the patient).
- -integerThe cost incurred by the provider of goods or services.
- -integerThe total amount paid for the expenses of the procedure.
- -integerTime 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 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.
- -integerThe 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.
- -dateThe date and time 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.
- -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.
- -integerA foreign key identifier to the deceased person. The demographic details of that person are stored in the person table.
- -integerThe device exposure domain captures records about a person�s inferred - exposure to a foreign physical object or instrument that which is used -for diagnostic or therapeutic purposes through a mechanism beyond -chemical action.
- -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.
- -dateThe date and time the Device or supply was removed from use.
- -datetimeA system-generated unique identifier for each device exposure.
- -integerThe date the device or supply was applied or used.
- -dateThe date and time the Device or supply was applied or used.
- -datetimeRefers 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.
- -integerA Drug Era is defined as a span of time when the Person is assumed to be exposed to a particular active ingredient.
- -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 domain captures any biochemical substance that is introduced in any way to a patient.
- -Fields
- -The number of days of supply of the medication as recorded in the original prescription or dispensing record.
- -integerRefers 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.
- -integerThe information about the dose unit as detailed in the source.
- -stringRefers 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 current instance of drug utilization. It is not available from all sources.
- -dateThe end date and time for the current instance of Drug utilization. It is not available from all sources.
- -datetimeA system-generated unique identifier for each drug utilization event.
- -integerThe 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.
- -dateThe start date and time 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.
- -datetimeRefers to: concept / concept_id
- -A foreign key to a drug concept that refers to the code used in the source.
- -integerThe 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.
- -stringRefers 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.
- -integerNumerical value of drug dose for this drug_exposure record.
- -numberAn identifier to determine where the product originated
- -stringA foreign key identifier to the person who is subjected to the drug. -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 initiated (prescribed) the drug exposure.
- -integerThe quantity of drug as recorded in the original prescription or dispensing record.
- -numberThe number of refills after the initial prescription. The initial prescription is not counted, values start with 0.
- -integerRefers to: concept / concept_id
- -A foreign key to a predefined concept in the Standardized Vocabularies reflecting the route of administration.
- -integerThe information about the route of administration as detailed in the source.
- -stringThe directions (“signetur”) on the drug prescription as recorded in -the original prescription (and printed on the container) or dispensing -record.
- -clobThe reason the medication was stopped, where available. Reasons include regimen completed, changed, removed, etc.
- -stringRefers to: visit_occurrence / visit_occurrence_id
- -A foreign key to the visit in the visit table during which the drug exposure initiated.
- -integerThe 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 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.
- -integerRefers to: concept / concept_id
- -The concept representing the domain of fact two, from which the corresponding table can be inferred.
- -integerThe unique identifier in the table corresponding to the domain of fact one.
- -integerThe unique identifier in the table corresponding to the domain of fact two.
- -integerRefers to: concept / concept_id
- -A foreign key to a standard concept identifier of relationship in the Standardized Vocabularies.
- -integerPhysical addresses of patients, organizations and care sites
- -Fields
- -The address field 1, typically used for the street address, as it appears in the source data.
- -stringThe address field 2, typically used for additional detail such as buildings, suites, floors, as it appears in the source data.
- -stringThe city field as it appears in the source data.
- -stringThe county. The county information is necessary because not all zip codes fall into one and the same county.
- -stringA system-generated unique identifier for each geographic location.
- -integerTotal: 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.
- -stringThe state field as it appears in the source data.
- -stringThe zip code. For US addresses, valid zip codes can be 3, 5 or 9 digits long, depending on the source data.
- -stringThe 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 Standardized Vocabularies.
- -integerThe date of the Measurement.
- -dateThe date and time of the Measurement.
- -datetimeA unique identifier for each measurement.
- -integerRefers to: concept / concept_id
- -A foreign key to a concept that refers to the code used in the source.
- -integerThe 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.
- -stringRefers 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.
- -integerRefers to: concept / concept_id
- -A foreign key identifier to the mathematical operator that is applied to the value_as_number. Operators are <, ≤, =, ≥, >
- -integerA foreign key identifier to the person about whom the measurement 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 making the measurement.
- -integerThe 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.
- -numberThe 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.
- -numberRefers to: concept / concept_id
- -A foreign key to a standard concept identifier of measurement units in the Standardized Vocabularies.
- -integerThe 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.
- -stringRefers 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.).
- -integerA measurement stored as a number. This is applicable to measurement where the result is expressed as a numeric value.
- -numberThe 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.
- -stringRefers to: visit_occurrence / visit_occurrence_id
- -A foreign key to the visit in the visit table during which the measurement was recorded.
- -integerThe NOTE table captures unstructured information that was recorded by - a provider or a patient in free text notes on a given date.
- -Fields
- -Refers to: concept / concept_id
- -A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the note character encoding type.
- -integerRefers to: concept / concept_id
- -A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the language of the note.
- -integerRefers to: concept / concept_id
- -A foreign key to the predefined Concept in the Standardized -Vocabularies reflecting the HL7 LOINC Document Type Vocabulary -classification of the note.
- -integerThe date the note was recorded.
- -dateThe time the note was recorded.
- -datetimeA unique identifier for each note.
- -integerThe content of the note.
- -clobThe title of the Note as it appears in the source.
- -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
- -integerObservations 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.
- -integerThe date of the observation.
- -dateThe time of the observation.
- -datetimeA system-generated unique identifier for each observation.
- -integerRefers to: concept / concept_id
- -A foreign key to a concept that refers to the code used in the source.
- -integerThe 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.
- -stringRefers to: concept / concept_id
- -A foreign key to the predefined concept identifier in the vocabulary reflecting the type of the observation.
- -integerA foreign key identifier to the person about whom the observation 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 making the observation.
- -integerRefers to: concept / concept_id
- -A foreign key to a standard concept identifier for a qualifier (e.g., severity of drug-drug interaction alert)
- -integerThe source value associated with a qualifier to characterize the observation
- -stringRefers to: concept / concept_id
- -A foreign key to a standard concept identifier of measurement units in the vocabulary.
- -integerThe 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.
- -stringRefers 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.).
- -integerThe observation result stored as a number. This is applicable to observations where the result is expressed as a numeric value.
- -numberThe 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.
- -stringRefers to: visit_occurrence / visit_occurrence_id
- -A foreign key to the visit in the visit table during which the observation was recorded.
- -integerTime 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 data source.
- -dateA system-generated unique identifier for each observation period.
- -integerThe start date of the observation period for which data are available from the data source.
- -dateRefers 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.
- -integerThe 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.
- -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: 1
- -| Table | -Field | -Name | -
|---|---|---|
| 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.
- -stringDemographic information about a Person
- -Fields
- -The time of birth at the birth day
- -datetimeRefers 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.
- -integerThe 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.
- -integerRefers to: concept / concept_id
- -A foreign key that refers to the standard concept identifier in the vocabulary for the ethnicity of the person.
- -integerRefers 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.
- -stringRefers to: concept / concept_id
- -A foreign key that refers to a standard concept identifier in the vocabulary for the gender of the person.
- -integerRefers 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.
- -stringRefers 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.
- -integerThe 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.
- -integerA system-generated unique identifier for each person.
- -integerTotal: 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.
- -stringRefers to: provider / provider_id
- -A foreign key to the primary care provider the person is seeing in the provider table.
- -integerRefers to: concept / concept_id
- -A foreign key that refers to a standard concept identifier in the vocabulary for the race of the person.
- -integerRefers 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.
- -stringThe 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.
- -integerProcedures 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)
- -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: concept / concept_id
- -A foreign key that refers to a standard procedure concept identifier in the vocabulary.
- -integerThe date on which the procedure was performed.
- -dateThe date and time on which the Procedure was performed.
- -datetimeA system-generated unique identifier for each procedure occurrence.
- -integerRefers to: concept / concept_id
- -A foreign key to a procedure concept that refers to the code used in the source.
- -integerThe 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.
- -stringRefers to: concept / concept_id
- -The date on which the procedure was performed.
- -integerRefers to: provider / provider_id
- -A foreign key to the provider in the provider table who was responsible for carrying out the procedure.
- -integerThe source code for the qualifier as it appears in the source data.
- -stringThe quantity of procedures ordered or administered.
- -integerRefers to: visit_occurrence / visit_occurrence_id
- -A foreign key to the visit in the visit table during which the procedure was carried out.
- -integerInformation 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.
- -integerThe Drug Enforcement Administration (DEA) number of the provider.
- -stringRefers to: concept / concept_id
- -integerRefers to: concept / concept_id
- -A foreign key to a concept that refers to the code used in the source.
- -integerstringThe National Provider Identifier (NPI) of the provider.
- -stringA system-generated unique identifier for each provider.
- -integerTotal: 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
- -stringThe identifier used for the provider in the source data, stored here for reference.
- -stringRefers to: concept / concept_id
- -A foreign key to a standard provider’s specialty concept identifier in the vocabulary.
- -integerRefers 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.
- -stringintegerThe 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 domain 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.
- -dateThe time on the date when the specimen was obtained from the person.
- -datetimeA 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.
- -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.
- -stringVisits for health care services of the Person
- -Fields
- -Refers to: concept / concept_id
- -A foreign key to the predefined concept in the Place of Service Vocabulary reflecting the admitting source for a visit.
- -integerRefers to: care_site / care_site_id
- -A foreign key to the care site in the care site table that was visited.
- -integerRefers to: concept / concept_id
- -A foreign key to the predefined concept in the Place of Service -Vocabulary reflecting the discharge disposition (destination) for a -visit.
- -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.
- -integerRefers to: visit_occurrence / visit_occurrence_id
- -A foreign key to the VISIT_OCCURRENCE table record of the visit -immediately preceding this visit. -omop,v5.1,visit_occurrence,admitting_source_value,No,,,,The source code -for the admitting source as it appears in the source data. -omop,v5.1,visit_occurrence,discharge_to_source_value,No,,,,The source -code for the discharge disposition as it appears in the source data.
- -integerRefers to: provider / provider_id
- -A foreign key to the provider in the provider table who was associated with the visit.
- -integerRefers to: concept / concept_id
- -A foreign key that refers to a visit concept identifier in the Standardized Vocabularies.
- -integerThe end date of the visit. If this is a one-day visit the end date should match the start date.
- -dateThe time the visit ended.
- -datetimeA system-generated unique identifier for each person’s visit or encounter at a healthcare provider.
- -integerTotal: 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_occurrence | -preceding_visit_occurrence_id | -fpk_visit_preceding_visit | -
Refers to: concept / concept_id
- -A foreign key to a concept that refers to the code used in the source.
- -integerThe source code used to reflect the type or source of the visit in the source data.
- -stringThe start date of the visit.
- -dateThe time the visit started.
- -datetimeRefers 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