From ab660c991a164e3309088081851cd191c7e61af7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pepe=20M=C3=A1rquez=20Romero?= Date: Wed, 31 May 2023 13:57:12 +0200 Subject: [PATCH] subiendo docs de omop --- Data Models Service.html | 6631 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 6631 insertions(+) create mode 100644 Data Models Service.html diff --git a/Data Models Service.html b/Data Models Service.html new file mode 100644 index 0000000..fcfff3a --- /dev/null +++ b/Data Models Service.html @@ -0,0 +1,6631 @@ + + + + + + Data Models Service + + + + + + + + + +
+

OMOP v5.1

+ + + +

Tables

+ + + +

attribute_definition

+ +

The ATTRIBUTE_DEFINITION table contains records to define each attribute through an associated description syntax.

+ +

Fields

+ + + +

attribute_definition_id

+ +

A unique identifier for each attribute.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 1

+ + + + + + + + + + + + + + + + + +
TableFieldName
cohort_attributeattribute_definition_idfpk_ca_attribute_definition
+ +

attribute_description

+ +

A complete description of the attribute definition.

+ +
Schema
+ + + +

attribute_name

+ +

A short description of the attribute.

+ +
Schema
+ + + +

attribute_syntax

+ +

Syntax to operationalize the attribute definition.

+ +
Schema
+ + + +

attribute_type_concept_id

+ +

Type to define what kind of attribute definition the record represents and how the syntax may be executed.

+ +
Schema
+ + + +

care_site

+ +

Information about the site of care

+ +

Fields

+ + + +

care_site_id

+ +

A system-generated unique identifier for each care site. A care site +is the place where the provider delivered the healthcare to the person.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 3

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TableFieldName
personcare_site_idfpk_person_care_site
providercare_site_idfpk_provider_care_site
visit_occurrencecare_site_idfpk_visit_care_site
+ +

care_site_name

+ +

The description of the care site.

+ +
Schema
+ + + +

care_site_source_value

+ +

The identifier for the care site as it appears in the source data, stored here for reference.

+ +
Schema
+ + + +

location_id

+ +

Refers to: location / location_id

+ +

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

+ +
Schema
+ + + +

place_of_service_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to the predefined concept identifier in the vocabulary reflecting the place of service.

+ +
Schema
+ + + +

place_of_service_source_value

+ +

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

+ +
Schema
+ + + +

cdm_source

+ +

The CDM_SOURCE table contains detail about the source database and +the process used to transform the data into the OMOP common data model.

+ +

Fields

+ + + +

cdm_etl_reference

+ +

URL or other external reference to location of ETL specification documentation and ETL source code

+ +
Schema
+ + + +

cdm_holder

+ +

The name of the organization responsible for the development of the CDM instance

+ +
Schema
+ + + +

cdm_release_date

+ +

The date when the CDM was instantiated

+ +
Schema
+ + + +

cdm_source_abbreviation

+ +

An abbreviation of the name

+ +
Schema
+ + + +

cdm_source_name

+ +

The full name of the source.

+ +
Schema
+ + + +

cdm_version

+ +

The version of CDM used

+ +
Schema
+ + + +

source_description

+ +

A 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.

+ +
Schema
+ + + +

source_documentation_reference

+ +

URL or other external reference to location of source documentation

+ +
Schema
+ + + +

source_release_date

+ +

The date for which the source data is most current, such as the last day of data capture

+ +
Schema
+ + + +

vocabulary_version

+ +

The version of the vocabulary used

+ +
Schema
+ + + +

cohort

+ +

The COHORT table contains records derived as a set of subjects that +satisfy a given set of inclusion criteria for a duration of time.

+ +

Fields

+ + + +

cohort_definition_id

+ +

Refers to: cohort_definition / cohort_definition_id

+ +

A foreign key to a record in the COHORT_DEFINITION table containing relevant Cohort definition information.

+ +
Schema
+ + + +

cohort_end_date

+ +

The date when the cohort definition criteria for the person, provider + or visit no longer match or the cohort membership was terminated.

+ +
Schema
+ + + +

cohort_start_date

+ +

The date when the cohort definition criteria for the person, provider or visit first match.

+ +
Schema
+ + + +

subject_id

+ +

A foreign key to the subject in the cohort. These could be referring to records in the Person, Provider, Visit Occurrence table.

+ +
Schema
+ + + +

cohort_attribute

+ +

The 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

+ + + +

attribute_definition_id

+ +

Refers to: attribute_definition / attribute_definition_id

+ +

A foreign key to a record in the ATTRIBUTE_DEFINITION table containing relevant attribute definition information.

+ +
Schema
+ + + +

cohort_definition_id

+ +

Refers to: cohort_definition / cohort_definition_id

+ +

A foreign key to a record in the COHORT_DEFINITION table containing relevant Cohort definition information.

+ +
Schema
+ + + +

cohort_end_date

+ +

The date when the cohort definition criteria for the person, provider + or visit no longer match or the cohort membership was terminated.

+ +
Schema
+ + + +

cohort_start_date

+ +

The date when the cohort definition criteria for the person, provider or visit first match.

+ +
Schema
+ + + +

subject_id

+ +

A foreign key to the subject in the cohort. These could be referring +to records in the PERSON, PROVIDER, or VISIT_OCCURRENCE table.

+ +
Schema
+ + + +

value_as_concept_id

+ +

Refers 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.

+ +
Schema
+ + + +

value_as_number

+ +

The 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).

+ +
Schema
+ + + +

cohort_definition

+ +

The cohort definition table contains records to define each derived cohort through an associated description and syntax.

+ +

Fields

+ + + +

cohort_definition_description

+ +

A complete description of the cohort definition.

+ +
Schema
+ + + +

cohort_definition_id

+ +

A unique identifier for each cohort.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 2

+ + + + + + + + + + + + + + + + + + + + + + + +
TableFieldName
cohortcohort_definition_idfpk_cohort_definition
cohort_attributecohort_definition_idfpk_ca_cohort_definition
+ +

cohort_definition_name

+ +

A short description of the cohort.

+ +
Schema
+ + + +

cohort_definition_syntax

+ +

Syntax to operationalize the cohort definition.

+ +
Schema
+ + + +

cohort_initiation_date

+ +

A date to indicate when the cohort was instantiated in the COHORT table.

+ +
Schema
+ + + +

definition_type_concept_id

+ +

Refers to: concept / concept_id

+ +

Type to define what kind of cohort definition the record represents and how the syntax may be executed.

+ +
Schema
+ + + +

subject_concept_id

+ +

A foreign key to the concept to which defines the domain of subjects +that are members of the cohort (e.g., person, provider, visit).

+ +
Schema
+ + + +

concept

+ +

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

+ +

Fields

+ + + +

concept_class_id

+ +

Refers to: concept_class / concept_class_id

+ +

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

+ +
Schema
+ + + +

concept_code

+ +

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

+ +
Schema
+ + + +

concept_id

+ +

A unique identifier for each concept across all domains.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 86

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TableFieldName
care_siteplace_of_service_concept_idfpk_care_site_place
cohort_attributevalue_as_concept_idfpk_ca_value
cohort_definitiondefinition_type_concept_idfpk_cohort_definition_concept
concept_ancestorancestor_concept_idfpk_concept_ancestor_concept_1
concept_ancestordescendant_concept_idfpk_concept_ancestor_concept_2
concept_classconcept_class_concept_idfpk_concept_class_concept
concept_relationshipconcept_id_1fpk_concept_relationship_c_1
concept_relationshipconcept_id_2fpk_concept_relationship_c_2
concept_synonymconcept_idfpk_concept_synonym_concept
condition_eracondition_concept_idfpk_condition_era_concept
condition_occurrencecondition_concept_idfpk_condition_concept
condition_occurrencecondition_source_concept_idfpk_condition_concept_s
condition_occurrencecondition_type_concept_idfpk_condition_type_concept
condition_occurrencecondition_status_concept_idfpk_condition_status_concept
deathcause_concept_idfpk_death_cause_concept
deathcause_source_concept_idfpk_death_cause_concept_s
deathdeath_type_concept_idfpk_death_type_concept
device_exposuredevice_concept_idfpk_device_concept
device_exposuredevice_source_concept_idfpk_device_concept_s
device_exposuredevice_type_concept_idfpk_device_type_concept
domaindomain_concept_idfpk_domain_concept
dose_eradrug_concept_idfpk_dose_era_concept
dose_eraunit_concept_idfpk_dose_era_unit_concept
drug_eradrug_concept_idfpk_drug_era_concept
drug_exposuredose_unit_concept_idfpk_drug_dose_unit_concept
drug_exposuredrug_concept_idfpk_drug_concept
drug_exposuredrug_source_concept_idfpk_drug_concept_s
drug_exposuredrug_type_concept_idfpk_drug_type_concept
drug_exposureroute_concept_idfpk_drug_route_concept
drug_strengthamount_unit_concept_idfpk_drug_strength_unit_1
drug_strengthdenominator_unit_concept_idfpk_drug_strength_unit_3
drug_strengthdrug_concept_idfpk_drug_strength_concept_1
drug_strengthingredient_concept_idfpk_drug_strength_concept_2
drug_strengthnumerator_unit_concept_idfpk_drug_strength_unit_2
fact_relationshipdomain_concept_id_1fpk_fact_domain_1
fact_relationshipdomain_concept_id_2fpk_fact_domain_2
fact_relationshiprelationship_concept_idfpk_fact_relationship
measurementmeasurement_concept_idfpk_measurement_concept
measurementmeasurement_source_concept_idfpk_measurement_concept_s
measurementmeasurement_type_concept_idfpk_measurement_type_concept
measurementoperator_concept_idfpk_measurement_operator
measurementunit_concept_idfpk_measurement_unit
measurementvalue_as_concept_idfpk_measurement_value
notenote_type_concept_idfpk_note_type_concept
notenote_class_concept_idfpk_note_class_concept
noteencoding_concept_idfpk_note_encoding_concept
notelanguage_concept_idfpk_note_language_concept
observationobservation_concept_idfpk_observation_concept
observationobservation_source_concept_idfpk_observation_concept_s
observationobservation_type_concept_idfpk_observation_type_concept
observationqualifier_concept_idfpk_observation_qualifier
observationunit_concept_idfpk_observation_unit
observationvalue_as_concept_idfpk_observation_value
observation_periodperiod_type_concept_idfpk_observation_period_concept
personethnicity_concept_idfpk_person_ethnicity_concept
personethnicity_source_concept_idfpk_person_ethnicity_concept_s
persongender_concept_idfpk_person_gender_concept
persongender_source_concept_idfpk_person_gender_concept_s
personrace_concept_idfpk_person_race_concept
personrace_source_concept_idfpk_person_race_concept_s
procedure_occurrencemodifier_concept_idfpk_procedure_modifier
procedure_occurrenceprocedure_concept_idfpk_procedure_concept
procedure_occurrenceprocedure_source_concept_idfpk_procedure_concept_s
procedure_occurrenceprocedure_type_concept_idfpk_procedure_type_concept
providergender_concept_idfpk_provider_gender
providergender_source_concept_idfpk_provider_gender_s
providerspecialty_concept_idfpk_provider_specialty
providerspecialty_source_concept_idfpk_provider_specialty_s
relationshiprelationship_concept_idfpk_relationship_concept
source_to_concept_maptarget_concept_idfpk_source_to_concept_map_c_1
specimenanatomic_site_concept_idfpk_specimen_site_concept
specimendisease_status_concept_idfpk_specimen_status_concept
specimenspecimen_concept_idfpk_specimen_concept
specimenspecimen_type_concept_idfpk_specimen_type_concept
specimenunit_concept_idfpk_specimen_unit_concept
costcurrency_concept_idfpk_visit_cost_currency
costcost_type_concept_idfpk_concept_type_cost_id
costcost_domain_idfpk_domain_cost_id
costrevenue_code_concept_idfpk_rev_code_cost_id
costdrg_concept_idfpk_drg_cost_id
visit_occurrencevisit_concept_idfpk_visit_concept
visit_occurrencevisit_source_concept_idfpk_visit_concept_s
visit_occurrencevisit_type_concept_idfpk_visit_type_concept
visit_occurrenceadmitting_source_concept_idfpk_visit_adm_src_concept
visit_occurrencedischarge_to_concept_idfpk_visit_disch_concept
vocabularyvocabulary_concept_idfpk_vocabulary_concept
+ +

concept_name

+ +

An unambiguous, meaningful and descriptive name for the concept.

+ +
Schema
+ + + +

domain_id

+ +

Refers to: domain / domain_id

+ +

The domain a concept belongs to.

+ +
Schema
+ + + +

invalid_reason

+ +

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

+ +
Schema
+ + + +

standard_concept

+ +

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

+ +
Schema
+ + + +

valid_end_date

+ +

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

+ +
Schema
+ + + +

valid_start_date

+ +

The date when the concept was first recorded.

+ +
Schema
+ + + +

vocabulary_id

+ +

Refers to: vocabulary / vocabulary_id

+ +

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

+ +
Schema
+ + + +

concept_ancestor

+ +

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

+ +

Fields

+ + + +

ancestor_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

descendant_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

max_levels_of_separation

+ +

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

+ +
Schema
+ + + +

min_levels_of_separation

+ +

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

+ +
Schema
+ + + +

concept_class

+ +

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

+ +

Fields

+ + + +

concept_class_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

concept_class_id

+ +

A unique key for each class.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 1

+ + + + + + + + + + + + + + + + + +
TableFieldName
conceptconcept_class_idfpk_concept_class
+ +

concept_class_name

+ +

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

+ +
Schema
+ + + +

concept_relationship

+ +

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

+ +

Fields

+ + + +

concept_id_1

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

concept_id_2

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

invalid_reason

+ +

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

+ +
Schema
+ + + +

relationship_id

+ +

Refers to: relationship / relationship_id

+ +

The type of relationship as defined in the relationship table.

+ +
Schema
+ + + +

valid_end_date

+ +

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

+ +
Schema
+ + + +

valid_start_date

+ +

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

+ +
Schema
+ + + +

concept_synonym

+ +

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

+ +

Fields

+ + + +

concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to the concept in the concept table.

+ +
Schema
+ + + +

concept_synonym_name

+ +

The alternative name for the concept.

+ +
Schema
+ + + +

language_concept_id

+ +

A foreign key to a concept representing the language.

+ +
Schema
+ + + +

condition_era

+ +

A Condition Era is defined as a span of time when the Person is assumed to have a given condition.

+ +

Fields

+ + + +

condition_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

condition_era_end_date

+ +

The 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.

+ +
Schema
+ + + +

condition_era_id

+ +

A system-generated unique identifier for each condition era.

+ +
Schema
+ + + +

condition_era_start_date

+ +

The 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.

+ +
Schema
+ + + +

condition_occurrence_count

+ +

The number of individual condition occurrences used to construct the condition era.

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

A 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.

+ +
Schema
+ + + +

condition_occurrence

+ +

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

+ +

Fields

+ + + +

condition_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

condition_end_date

+ +

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

+ +
Schema
+ + + +

condition_end_datetime

+ +

The date when the instance of the Condition is considered to have ended.

+ +
Schema
+ + + +

condition_occurrence_id

+ +

A system-generated unique identifier for each condition occurrence event.

+ +
Schema
+ + + +

condition_source_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

condition_source_value

+ +

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

+ +
Schema
+ + + +

condition_start_date

+ +

The date when the instance of the condition is recorded.

+ +
Schema
+ + + +

condition_start_datetime

+ +

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

+ +
Schema
+ + + +

condition_status_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to the predefined concept in the standard vocabulary reflecting the condition status.

+ +
Schema
+ + + +

condition_status_source_value

+ +

The source code for condition status as it appears in the source data.

+ +
Schema
+ + + +

condition_type_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to the predefined concept identifier in the vocabulary +reflecting the source data from which the condition was recorded, the +level of standardization, and the type of occurrence. Conditions are +defined as primary or secondary diagnoses, problem lists and person +statuses.

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

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

+ +
Schema
+ + + +

provider_id

+ +

Refers to: provider / provider_id

+ +

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

+ +
Schema
+ + + +

stop_reason

+ +

The reason, if available, that the condition was no longer recorded, +as indicated in the source data. Valid values include discharged, +resolved, etc.

+ +
Schema
+ + + +

visit_occurrence_id

+ +

Refers to: visit_occurrence / visit_occurrence_id

+ +

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

+ +
Schema
+ + + +

cost

+ +

The 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

+ + + +

amount_allowed

+ +

The contracted amount agreed between the payer and provider.

+ +
Schema
+ + + +

cost_domain_id

+ +

Refers 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.

+ +
Schema
+ + + +

cost_event_id

+ +

A foreign key identifier to the event (e.g. Measurement, Procedure, +Visit, Drug Exposure, etc) record for which cost data are recorded.

+ +
Schema
+ + + +

cost_id

+ +

A unique identifier for each procedure cost record.

+ +
Schema
+ + + +

cost_type_concept_id

+ +

Refers 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.

+ +
Schema
+ + + +

currency_concept_id

+ +

Refers to: concept / concept_id

+ +

A concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar.

+ +
Schema
+ + + +

drg_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for DRG codes.

+ +
Schema
+ + + +

drg_source_value

+ +

The source code for the 3-digit DRG source code as it appears in the source data, stored here for reference.

+ +
Schema
+ + + +

paid_by_patient

+ +

The total amount paid by the Person as a share of the expenses.

+ +
Schema
+ + + +

paid_by_payer

+ +

The amount paid by the payer (insurer). If there is more than one payer, several cost records indicate that fact.

+ +
Schema
+ + + +

paid_by_primary

+ +

The amount paid by a primary Payer through the coordination of benefits.

+ +
Schema
+ + + +

paid_dispensing_fee

+ +

The 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.

+ +
Schema
+ + + +

paid_ingredient_cost

+ +

The 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.

+ +
Schema
+ + + +

paid_patient_coinsurance

+ +

The 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.

+ +
Schema
+ + + +

paid_patient_copay

+ +

The amount paid by the person as a fixed contribution to the expenses. Copay does not contribute to the out_of_pocket expenses.

+ +
Schema
+ + + +

paid_patient_deductible

+ +

The amount paid by the person that is counted toward the deductible defined by the payer plan (policy).

+ +
Schema
+ + + +

payer_plan_period_id

+ +

Refers 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.

+ +
Schema
+ + + +

revenue_code_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for Revenue codes.

+ +
Schema
+ + + +

revenue_code_source_value

+ +

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

+ +
Schema
+ + + +

total_charge

+ +

The total amount charged by some provider of goods or services (e.g. +hospital, physician pharmacy, dme provider) to payers (insurance +companies, the patient).

+ +
Schema
+ + + +

total_cost

+ +

The cost incurred by the provider of goods or services.

+ +
Schema
+ + + +

total_paid

+ +

The total amount paid for the expenses of the procedure.

+ +
Schema
+ + + +

death

+ +

Time and cause of death of the Person

+ +

Fields

+ + + +

cause_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

cause_source_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to the 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.

+ +
Schema
+ + + +

cause_source_value

+ +

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

+ +
Schema
+ + + +

death_date

+ +

The date the person 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.

+ +
Schema
+ + + +

death_datetime

+ +

The 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.

+ +
Schema
+ + + +

death_type_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

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

+ +
Schema
+ + + +

device_exposure

+ +

The 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

+ + + +

device_concept_id

+ +

Refers to: concept / concept_id

+ +

Only the DI portion of the UDI would be captured as a Concept in the Standardized Vocabularies.

+ +
Schema
+ + + +

device_exposure_end_date

+ +

The date the device or supply was removed from use.

+ +
Schema
+ + + +

device_exposure_end_datetime

+ +

The date and time the Device or supply was removed from use.

+ +
Schema
+ + + +

device_exposure_id

+ +

A system-generated unique identifier for each device exposure.

+ +
Schema
+ + + +

device_exposure_start_date

+ +

The date the device or supply was applied or used.

+ +
Schema
+ + + +

device_exposure_start_datetime

+ +

The date and time the Device or supply was applied or used.

+ +
Schema
+ + + +

device_source_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

device_source_value

+ +

The 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.

+ +
Schema
+ + + +

device_type_concept_id

+ +

Refers to: concept / concept_id

+ +

Provenance for the data, e.g. procedure device, from registry, etc.

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

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

+ +
Schema
+ + + +

provider_id

+ +

Refers to: provider / provider_id

+ +

A foreign key to the provider in the provider table who was responsible for using the device.

+ +
Schema
+ + + +

quantity

+ +

The number of individual devices used for the exposure

+ +
Schema
+ + + +

unique_device_id

+ +

The entire UDI or equivalent.

+ +
Schema
+ + + +

visit_occurrence_id

+ +

Refers to: visit_occurrence / visit_occurrence_id

+ +

A foreign key to the visit in the visit table during which the device was used.

+ +
Schema
+ + + +

domain

+ +

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

+ +

Fields

+ + + +

domain_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

domain_id

+ +

A unique key for each domain.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 1

+ + + + + + + + + + + + + + + + + +
TableFieldName
conceptdomain_idfpk_concept_domain
+ +

domain_name

+ +

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

+ +
Schema
+ + + +

dose_era

+ +

A 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

+ + + +

dose_era_end_date

+ +

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.

+ +
Schema
+ + + +

dose_era_id

+ +

A unique identifier for each drug era.

+ +
Schema
+ + + +

dose_era_start_date

+ +

The 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.

+ +
Schema
+ + + +

dose_value

+ +

The numeric value of the dose

+ +
Schema
+ + + +

drug_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key that refers to a standard concept identifier in the +Standardized Vocabularies for the active ingredient drug concept.

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

A 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.

+ +
Schema
+ + + +

unit_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

drug_era

+ +

A Drug Era is defined as a span of time when the Person is assumed to be exposed to a particular active ingredient.

+ +

Fields

+ + + +

drug_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

drug_era_end_date

+ +

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.

+ +
Schema
+ + + +

drug_era_id

+ +

A system-generated unique identifier for each drug era.

+ +
Schema
+ + + +

drug_era_start_date

+ +

The 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.

+ +
Schema
+ + + +

drug_exposure_count

+ +

The number of individual drug exposure occurrences used to construct the drug era.

+ +
Schema
+ + + +

gap_days

+ +

The number of observed days of gap between drug exposure records which was tolerated in the building of the drug era record.

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

A 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.

+ +
Schema
+ + + +

drug_exposure

+ +

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

+ +

Fields

+ + + +

days_supply

+ +

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

+ +
Schema
+ + + +

dose_unit_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to a predefined concept in the Standardized +Vocabularies reflecting the unit the effective_drug_dose value is +expressed.

+ +
Schema
+ + + +

dose_unit_source_value

+ +

The information about the dose unit as detailed in the source.

+ +
Schema
+ + + +

drug_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

drug_exposure_end_date

+ +

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

+ +
Schema
+ + + +

drug_exposure_end_datetime

+ +

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

+ +
Schema
+ + + +

drug_exposure_id

+ +

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

+ +
Schema
+ + + +

drug_exposure_start_date

+ +

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

+ +
Schema
+ + + +

drug_exposure_start_datetime

+ +

The 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.

+ +
Schema
+ + + +

drug_source_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

drug_source_value

+ +

The source 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.

+ +
Schema
+ + + +

drug_type_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to the predefined concept identifier in the vocabulary +reflecting the type of drug exposure recorded. It indicates how the drug + exposure was represented in the source data: as medication history, +filled prescriptions, etc.

+ +
Schema
+ + + +

effective_drug_dose

+ +

Numerical value of drug dose for this drug_exposure record.

+ +
Schema
+ + + +

lot_number

+ +

An identifier to determine where the product originated

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

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

+ +
Schema
+ + + +

provider_id

+ +

Refers to: provider / provider_id

+ +

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

+ +
Schema
+ + + +

quantity

+ +

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

+ +
Schema
+ + + +

refills

+ +

The number of refills after the initial prescription. The initial prescription is not counted, values start with 0.

+ +
Schema
+ + + +

route_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to a predefined concept in the Standardized Vocabularies reflecting the route of administration.

+ +
Schema
+ + + +

route_source_value

+ +

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

+ +
Schema
+ + + +

sig

+ +

The directions (“signetur”) on the drug prescription as recorded in +the original prescription (and printed on the container) or dispensing +record.

+ +
Schema
+ + + +

stop_reason

+ +

The reason the medication was stopped, where available. Reasons include regimen completed, changed, removed, etc.

+ +
Schema
+ + + +

visit_occurrence_id

+ +

Refers to: visit_occurrence / visit_occurrence_id

+ +

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

+ +
Schema
+ + + +

drug_strength

+ +

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

+ +

Fields

+ + + +

amount_unit_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

amount_value

+ +

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

+ +
Schema
+ + + +

denominator_unit_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

denominator_value

+ +

The 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.

+ +
Schema
+ + + +

drug_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

ingredient_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

invalid_reason

+ +

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

+ +
Schema
+ + + +

numerator_unit_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

numerator_value

+ +

The 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.

+ +
Schema
+ + + +

valid_end_date

+ +

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

+ +
Schema
+ + + +

valid_start_date

+ +

The date when the concept was first recorded. The default value is 1-Jan-1970.

+ +
Schema
+ + + +

fact_relationship

+ +

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

+ +

Fields

+ + + +

domain_concept_id_1

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

domain_concept_id_2

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

fact_id_1

+ +

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

+ +
Schema
+ + + +

fact_id_2

+ +

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

+ +
Schema
+ + + +

relationship_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

location

+ +

Physical addresses of patients, organizations and care sites

+ +

Fields

+ + + +

address_1

+ +

The address field 1, typically used for the street address, as it appears in the source data.

+ +
Schema
+ + + +

address_2

+ +

The address field 2, typically used for additional detail such as buildings, suites, floors, as it appears in the source data.

+ +
Schema
+ + + +

city

+ +

The city field as it appears in the source data.

+ +
Schema
+ + + +

county

+ +

The county. The county information is necessary because not all zip codes fall into one and the same county.

+ +
Schema
+ + + +

location_id

+ +

A system-generated unique identifier for each geographic location.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 2

+ + + + + + + + + + + + + + + + + + + + + + + +
TableFieldName
care_sitelocation_idfpk_care_site_location
personlocation_idfpk_person_location
+ +

location_source_value

+ +

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

+ +
Schema
+ + + +

state

+ +

The state field as it appears in the source data.

+ +
Schema
+ + + +

zip

+ +

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

+ +
Schema
+ + + +

measurement

+ +

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

+ +

Fields

+ + + +

measurement_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to the standard measurement concept identifier in the Standardized Vocabularies.

+ +
Schema
+ + + +

measurement_date

+ +

The date of the Measurement.

+ +
Schema
+ + + +

measurement_datetime

+ +

The date and time of the Measurement.

+ +
Schema
+ + + +

measurement_id

+ +

A unique identifier for each measurement.

+ +
Schema
+ + + +

measurement_source_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

measurement_source_value

+ +

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

+ +
Schema
+ + + +

measurement_type_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to the predefined concept identifier in the +Standardized Vocabularies reflecting the type of data on which the +measurement record is based.

+ +
Schema
+ + + +

operator_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

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

+ +
Schema
+ + + +

provider_id

+ +

Refers to: provider / provider_id

+ +

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

+ +
Schema
+ + + +

range_high

+ +

The upper limit of the normal range of the measurement. The lower +range is assumed to be in the same units of measure as the measurement +value.

+ +
Schema
+ + + +

range_low

+ +

The lower limit of the normal range of the measurement. The lower +range is assumed to be in the same units of measure as the measurement +value.

+ +
Schema
+ + + +

unit_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

unit_source_value

+ +

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

+ +
Schema
+ + + +

value_as_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to 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.).

+ +
Schema
+ + + +

value_as_number

+ +

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

+ +
Schema
+ + + +

value_source_value

+ +

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

+ +
Schema
+ + + +

visit_occurrence_id

+ +

Refers to: visit_occurrence / visit_occurrence_id

+ +

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

+ +
Schema
+ + + +

note

+ +

The NOTE table captures unstructured information that was recorded by + a provider or a patient in free text notes on a given date.

+ +

Fields

+ + + +

encoding_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the note character encoding type.

+ +
Schema
+ + + +

language_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the language of the note.

+ +
Schema
+ + + +

note_class_concept_id

+ +

Refers 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.

+ +
Schema
+ + + +

note_date

+ +

The date the note was recorded.

+ +
Schema
+ + + +

note_datetime

+ +

The time the note was recorded.

+ +
Schema
+ + + +

note_id

+ +

A unique identifier for each note.

+ +
Schema
+ + + +

note_text

+ +

The content of the note.

+ +
Schema
+ + + +

note_title

+ +

The title of the Note as it appears in the source.

+ +
Schema
+ + + +

note_type_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to the predefined concept identifier in the +Standardized Vocabularies reflecting the type data from which the note.

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

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

+ +
Schema
+ + + +

provider_id

+ +

Refers to: provider / provider_id

+ +

A foreign key to the provider in the provider table who was responsible for taking the note.

+ +
Schema
+ + + +

visit_occurrence_id

+ +

Refers to: visit_occurrence / visit_occurrence_id

+ +

Foreign key to visit

+ +
Schema
+ + + +

observation

+ +

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

+ +

Fields

+ + + +

observation_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

observation_date

+ +

The date of the observation.

+ +
Schema
+ + + +

observation_datetime

+ +

The time of the observation.

+ +
Schema
+ + + +

observation_id

+ +

A system-generated unique identifier for each observation.

+ +
Schema
+ + + +

observation_source_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

observation_source_value

+ +

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

+ +
Schema
+ + + +

observation_type_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

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

+ +
Schema
+ + + +

provider_id

+ +

Refers to: provider / provider_id

+ +

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

+ +
Schema
+ + + +

qualifier_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

qualifier_source_value

+ +

The source value associated with a qualifier to characterize the observation

+ +
Schema
+ + + +

unit_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

unit_source_value

+ +

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

+ +
Schema
+ + + +

value_as_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

value_as_number

+ +

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

+ +
Schema
+ + + +

value_as_string

+ +

The observation result stored as a varchar. This is applicable to +observations where the result is expressed as verbatim text, such as in +radiology or pathology reports.

+ +
Schema
+ + + +

visit_occurrence_id

+ +

Refers to: visit_occurrence / visit_occurrence_id

+ +

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

+ +
Schema
+ + + +

observation_period

+ +

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

+ +

Fields

+ + + +

observation_period_end_date

+ +

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

+ +
Schema
+ + + +

observation_period_id

+ +

A system-generated unique identifier for each observation period.

+ +
Schema
+ + + +

observation_period_start_date

+ +

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

+ +
Schema
+ + + +

period_type_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

A foreign key identifier to the person for whom the observation +period is defined. The demographic details of that person are stored in +the person table.

+ +
Schema
+ + + +

payer_plan_period

+ +

The PAYER_PLAN_PERIOD table captures records that detail the period +of time that a person is continuously enrolled under a specific health +plan benefit structure from a given payer.

+ +

Fields

+ + + +

family_source_value

+ +

The source code for the person’s family as it appears in the source data.

+ +
Schema
+ + + +

payer_plan_period_end_date

+ +

The end date of the payer plan period.

+ +
Schema
+ + + +

payer_plan_period_id

+ +

An identifier for each unique combination of payer, plan, family code and time span.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 1

+ + + + + + + + + + + + + + + + + +
TableFieldName
costpayer_plan_period_idfpk_visit_cost_period
+ +

payer_plan_period_start_date

+ +

The start date of the payer plan period.

+ +
Schema
+ + + +

payer_source_value

+ +

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

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

A foreign key identifier to the person covered by the payer. The +demographic details of that person are stored in the person table.

+ +
Schema
+ + + +

plan_source_value

+ +

The source code for the person’s coverage plan as it appears in the source data.

+ +
Schema
+ + + +

person

+ +

Demographic information about a Person

+ +

Fields

+ + + +

birth_datetime

+ +

The time of birth at the birth day

+ +
Schema
+ + + +

care_site_id

+ +

Refers to: care_site / care_site_id

+ +

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

+ +
Schema
+ + + +

day_of_birth

+ +

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

+ +
Schema
+ + + +

ethnicity_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

ethnicity_source_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

ethnicity_source_value

+ +

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

+ +
Schema
+ + + +

gender_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

gender_source_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

gender_source_value

+ +

The source code for the gender of the person as it appears in the +source data. The person gender is mapped to a standard gender concept in + the vocabulary and the corresponding concept identifier is, stored here + for reference.

+ +
Schema
+ + + +

location_id

+ +

Refers to: location / location_id

+ +

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

+ +
Schema
+ + + +

month_of_birth

+ +

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

+ +
Schema
+ + + +

person_id

+ +

A system-generated unique identifier for each person.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 15

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TableFieldName
condition_eraperson_idfpk_condition_era_person
condition_occurrenceperson_idfpk_condition_person
deathperson_idfpk_death_person
device_exposureperson_idfpk_device_person
dose_eraperson_idfpk_dose_era_person
drug_eraperson_idfpk_drug_era_person
drug_exposureperson_idfpk_drug_person
measurementperson_idfpk_measurement_person
noteperson_idfpk_note_person
observationperson_idfpk_observation_person
observation_periodperson_idfpk_observation_period_person
payer_plan_periodperson_idfpk_payer_plan_period
procedure_occurrenceperson_idfpk_procedure_person
specimenperson_idfpk_specimen_person
visit_occurrenceperson_idfpk_visit_person
+ +

person_source_value

+ +

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.

+ +
Schema
+ + + +

provider_id

+ +

Refers to: provider / provider_id

+ +

A foreign key to the primary care provider the person is seeing in the provider table.

+ +
Schema
+ + + +

race_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

race_source_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

race_source_value

+ +

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

+ +
Schema
+ + + +

year_of_birth

+ +

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

+ +
Schema
+ + + +

procedure_occurrence

+ +

Procedures carried out on the Person

+ +

Fields

+ + + +

modifier_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

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

+ +
Schema
+ + + +

procedure_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

procedure_date

+ +

The date on which the procedure was performed.

+ +
Schema
+ + + +

procedure_datetime

+ +

The date and time on which the Procedure was performed.

+ +
Schema
+ + + +

procedure_occurrence_id

+ +

A system-generated unique identifier for each procedure occurrence.

+ +
Schema
+ + + +

procedure_source_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

procedure_source_value

+ +

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

+ +
Schema
+ + + +

procedure_type_concept_id

+ +

Refers to: concept / concept_id

+ +

The date on which the procedure was performed.

+ +
Schema
+ + + +

provider_id

+ +

Refers to: provider / provider_id

+ +

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

+ +
Schema
+ + + +

qualifier_source_value

+ +

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

+ +
Schema
+ + + +

quantity

+ +

The quantity of procedures ordered or administered.

+ +
Schema
+ + + +

visit_occurrence_id

+ +

Refers to: visit_occurrence / visit_occurrence_id

+ +

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

+ +
Schema
+ + + +

provider

+ +

Information about health care providers

+ +

Fields

+ + + +

care_site_id

+ +

Refers to: care_site / care_site_id

+ +

A foreign key to the main care site where the provider is practicing.

+ +
Schema
+ + + +

dea

+ +

The Drug Enforcement Administration (DEA) number of the provider.

+ +
Schema
+ + + +

gender_concept_id

+ +

Refers to: concept / concept_id

+ +
Schema
+ + + +

gender_source_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

gender_source_value

+ +
Schema
+ + + +

npi

+ +

The National Provider Identifier (NPI) of the provider.

+ +
Schema
+ + + +

provider_id

+ +

A system-generated unique identifier for each provider.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 9

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TableFieldName
condition_occurrenceprovider_idfpk_condition_provider
device_exposureprovider_idfpk_device_provider
drug_exposureprovider_idfpk_drug_provider
measurementprovider_idfpk_measurement_provider
noteprovider_idfpk_note_provider
observationprovider_idfpk_observation_provider
personprovider_idfpk_person_provider
procedure_occurrenceprovider_idfpk_procedure_provider
visit_occurrenceprovider_idfpk_visit_provider
+ +

provider_name

+ +

A description of the provider

+ +
Schema
+ + + +

provider_source_value

+ +

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

+ +
Schema
+ + + +

specialty_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to a standard provider’s specialty concept identifier in the vocabulary.

+ +
Schema
+ + + +

specialty_source_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

specialty_source_value

+ +

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

+ +
Schema
+ + + +

year_of_birth

+ +
Schema
+ + + +

relationship

+ +

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

+ +

Fields

+ + + +

defines_ancestry

+ +

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

+ +
Schema
+ + + +

is_hierarchical

+ +

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

+ +
Schema
+ + + +

relationship_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

relationship_id

+ +

The type of relationship captured by the relationship record.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 2

+ + + + + + + + + + + + + + + + + + + + + + + +
TableFieldName
concept_relationshiprelationship_idfpk_concept_relationship_id
relationshipreverse_relationship_idfpk_relationship_reverse
+ +

relationship_name

+ +

The text that describes the relationship type.

+ +
Schema
+ + + +

reverse_relationship_id

+ +

Refers to: relationship / relationship_id

+ +

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

+ +
Schema
+ + + +

source_to_concept_map

+ +

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

+ +

Fields

+ + + +

invalid_reason

+ +

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

+ +
Schema
+ + + +

source_code

+ +

The source code being translated into a standard concept.

+ +
Schema
+ + + +

source_code_description

+ +

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

+ +
Schema
+ + + +

source_concept_id

+ +

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

+ +
Schema
+ + + +

source_vocabulary_id

+ +

Refers to: vocabulary / vocabulary_id

+ +

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

+ +
Schema
+ + + +

target_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

target_vocabulary_id

+ +

Refers to: vocabulary / vocabulary_id

+ +

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

+ +
Schema
+ + + +

valid_end_date

+ +

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

+ +
Schema
+ + + +

valid_start_date

+ +

The date when the mapping instance was first recorded.

+ +
Schema
+ + + +

specimen

+ +

The specimen domain contains the records identifying each biological sample from a person.

+ +

Fields

+ + + +

anatomic_site_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to a standard concept identifier for the anatomic location of specimen collection.

+ +
Schema
+ + + +

anatomic_site_source_value

+ +

The information about the anatomic site as detailed in the source.

+ +
Schema
+ + + +

disease_status_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to a standard concept identifier for the disease status of specimen collection.

+ +
Schema
+ + + +

disease_status_source_value

+ +

The information about the disease status as detailed in the source.

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

A foreign key identifier to the person for whom the specimen is recorded.

+ +
Schema
+ + + +

quantity

+ +

The amount of specimen collection from the person during the sampling procedure

+ +
Schema
+ + + +

specimen_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key referring to a standard concept identifier in the Standardized Vocabularies for the specimen.

+ +
Schema
+ + + +

specimen_date

+ +

The date the specimen was obtained from the person.

+ +
Schema
+ + + +

specimen_datetime

+ +

The time on the date when the specimen was obtained from the person.

+ +
Schema
+ + + +

specimen_id

+ +

A unique identifier for each specimen.

+ +
Schema
+ + + +

specimen_source_id

+ +

The specimen identifier as it appears in the source data.

+ +
Schema
+ + + +

specimen_source_value

+ +

The 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.

+ +
Schema
+ + + +

specimen_type_concept_id

+ +

Refers 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.

+ +
Schema
+ + + +

unit_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key to a standard concept identifier for the unit associated with the numeric quantity of the specimen collection.

+ +
Schema
+ + + +

unit_source_value

+ +

The information about the unit as detailed in the source.

+ +
Schema
+ + + +

visit_occurrence

+ +

Visits for health care services of the Person

+ +

Fields

+ + + +

admitting_source_concept_id

+ +

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.

+ +
Schema
+ + + +

care_site_id

+ +

Refers to: care_site / care_site_id

+ +

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

+ +
Schema
+ + + +

discharge_to_concept_id

+ +

Refers 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.

+ +
Schema
+ + + +

person_id

+ +

Refers to: person / person_id

+ +

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

+ +
Schema
+ + + +

preceding_visit_occurrence_id

+ +

Refers 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.

+ +
Schema
+ + + +

provider_id

+ +

Refers to: provider / provider_id

+ +

A foreign key to the provider in the provider table who was associated with the visit.

+ +
Schema
+ + + +

visit_concept_id

+ +

Refers to: concept / concept_id

+ +

A foreign key that refers to a visit concept identifier in the Standardized Vocabularies.

+ +
Schema
+ + + +

visit_end_date

+ +

The end date of the visit. If this is a one-day visit the end date should match the start date.

+ +
Schema
+ + + +

visit_end_datetime

+ +

The time the visit ended.

+ +
Schema
+ + + +

visit_occurrence_id

+ +

A system-generated unique identifier for each person’s visit or encounter at a healthcare provider.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 8

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TableFieldName
condition_occurrencevisit_occurrence_idfpk_condition_visit
device_exposurevisit_occurrence_idfpk_device_visit
drug_exposurevisit_occurrence_idfpk_drug_visit
measurementvisit_occurrence_idfpk_measurement_visit
notevisit_occurrence_idfpk_note_visit
observationvisit_occurrence_idfpk_observation_visit
procedure_occurrencevisit_occurrence_idfpk_procedure_visit
visit_occurrencepreceding_visit_occurrence_idfpk_visit_preceding_visit
+ +

visit_source_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

visit_source_value

+ +

The source code used to reflect the type or source of the visit in the source data.

+ +
Schema
+ + + +

visit_start_date

+ +

The start date of the visit.

+ +
Schema
+ + + +

visit_start_datetime

+ +

The time the visit started.

+ +
Schema
+ + + +

visit_type_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

vocabulary

+ +

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

+ +

Fields

+ + + +

vocabulary_concept_id

+ +

Refers to: concept / concept_id

+ +

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

+ +
Schema
+ + + +

vocabulary_id

+ +

A unique identifier for each vocabulary.

+ +
Schema
+ + + +
Inbound References
+ +

Total: 3

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TableFieldName
conceptvocabulary_idfpk_concept_vocabulary
source_to_concept_mapsource_vocabulary_idfpk_source_to_concept_map_v_1
source_to_concept_maptarget_vocabulary_idfpk_source_to_concept_map_v_2
+ +

vocabulary_name

+ +

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

+ +
Schema
+ + + +

vocabulary_reference

+ +

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

+ +
Schema
+ + + +

vocabulary_version

+ +

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

+ +
Schema
+ + + +
+ + + + + + + \ No newline at end of file -- 2.24.1