Added v6.0 pdf

This commit is contained in:
Clair Blacketer 2018-10-10 15:04:27 -04:00
parent fe581d8d5e
commit cc5e8f7f28
3 changed files with 429 additions and 1 deletions

View File

@ -18,5 +18,5 @@
These tables contain the core information about the clinical events that occurred longitudinally during valid Observation Periods for each Person, as well as demographic information for the Person. These tables contain the core information about the clinical events that occurred longitudinally during valid Observation Periods for each Person, as well as demographic information for the Person.
Below provides an entity-relationship diagram highlighting the tables within the Standardized Clinical Data portion of the OMOP Common Data Model: Below provides an entity-relationship diagram highlighting the tables within the Standardized Clinical Data portion of the OMOP Common Data Model:
![](http://www.ohdsi.org/web/wiki/lib/exe/fetch.php?media=entity_diagram.png) ![](S:/Git/GitHub/CommonDataModel_v6/Documentation/CommonDataModel_Wiki_Files/images/entity_diagram.png)

428
OMOP_CDM_v6_0.csv Normal file
View File

@ -0,0 +1,428 @@
"field","required","type","description","table"
"cohort_definition_id","Yes","INTEGER","A foreign key to a record in the COHORT_DEFINITION table containing relevant Cohort Definition information.","cohort"
"subject_id","Yes","INTEGER","A foreign key to the subject in the cohort. These could be referring to records in the PERSON, PROVIDER, VISIT_OCCURRENCE table.","cohort"
"cohort_start_date","Yes","DATE","The date when the Cohort Definition criteria for the Person, Provider or Visit first match.","cohort"
"cohort_end_date","Yes","DATE","The date when the Cohort Definition criteria for the Person, Provider or Visit no longer match or the Cohort membership was terminated.","cohort"
"cohort_definition_id","Yes","INTEGER","A unique identifier for each Cohort.","cohort_definition"
"cohort_definition_name","Yes","VARCHAR(255)","A short description of the Cohort.","cohort_definition"
"cohort_definition_description","No","VARCHAR(MAX)","A complete description of the Cohort definition","cohort_definition"
"definition_type_concept_id","Yes","INTEGER","Type defining what kind of Cohort Definition the record represents and how the syntax may be executed","cohort_definition"
"cohort_definition_syntax","No","VARCHAR(MAX)","Syntax or code to operationalize the Cohort definition","cohort_definition"
"subject_concept_id","Yes","INTEGER","A foreign key to the Concept to which defines the domain of subjects that are members of the cohort (e.g., Person, Provider, Visit).","cohort_definition"
"cohort_initiation_date","No","DATE","A date to indicate when the Cohort was initiated in the COHORT table","cohort_definition"
"condition_occurrence_id","Yes","BIGINT","A unique identifier for each Condition Occurrence event.","condition_occurrence"
"person_id","Yes","BIGINT","A foreign key identifier to the Person who is experiencing the condition. The demographic details of that Person are stored in the PERSON table.","condition_occurrence"
"condition_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the 'Condition' domain.","condition_occurrence"
"condition_start_date","No","DATE","The date when the instance of the Condition is recorded.","condition_occurrence"
"condition_start_datetime","Yes","DATETIME","The date and time when the instance of the Condition is recorded.","condition_occurrence"
"condition_end_date","No","DATE","The date when the instance of the Condition is considered to have ended.","condition_occurrence"
"condition_end_datetime","No","DATETIME","The date when the instance of the Condition is considered to have ended.","condition_occurrence"
"condition_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the source data from which the Condition was recorded, the level of standardization, and the type of occurrence. These belong to the 'Condition Type' vocabulary","condition_occurrence"
"condition_status_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies reflecting the point of care at which the Condition was diagnosed.","condition_occurrence"
"stop_reason","No","VARCHAR(20)","The reason that the Condition was no longer present, as indicated in the source data.","condition_occurrence"
"provider_id","No","INTEGER","A foreign key to the Provider in the PROVIDER table who was responsible for capturing (diagnosing) the Condition.","condition_occurrence"
"visit_occurrence_id","No","INTEGER","A foreign key to the visit in the VISIT_OCCURRENCE table during which the Condition was determined (diagnosed).","condition_occurrence"
"visit_detail_id","No","INTEGER","A foreign key to the visit in the VISIT_DETAIL table during which the Condition was determined (diagnosed).","condition_occurrence"
"condition_source_value","No","VARCHAR(50)","The source code for the Condition as it appears in the source data. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.","condition_occurrence"
"condition_source_concept_id","Yes","INTEGER","A foreign key to a Condition Concept that refers to the code used in the source.","condition_occurrence"
"condition_status_source_value","No","VARCHAR(50)","The source code for the condition status 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.","condition_occurrence"
"device_exposure_id","Yes","BIGINT","A system-generated unique identifier for each Device Exposure.","device_exposure"
"person_id","Yes","BIGINT","A foreign key identifier to the Person who is subjected to the Device. The demographic details of that Person are stored in the PERSON table.","device_exposure"
"device_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the 'Device' domain.","device_exposure"
"device_exposure_start_date","No","DATE","The date the Device or supply was applied or used.","device_exposure"
"device_exposure_start_datetime","Yes","DATETIME","The date and time the Device or supply was applied or used.","device_exposure"
"device_exposure_end_date","No","DATE","The date use of the Device or supply was ceased.","device_exposure"
"device_exposure_end_datetime","No","DATETIME","The date and time use of the Device or supply was ceased.","device_exposure"
"device_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of Device Exposure recorded. It indicates how the Device Exposure was represented in the source data and belongs to the 'Device Type' domain.","device_exposure"
"unique_device_id","No","VARCHAR(50)","A UDI or equivalent identifying the instance of the Device used in the Person.","device_exposure"
"quantity","No","INTEGER","The number of individual Devices used in the exposure.","device_exposure"
"provider_id","No","INTEGER","A foreign key to the provider in the PROVIDER table who initiated or administered the Device.","device_exposure"
"visit_occurrence_id","No","INTEGER","A foreign key to the visit in the VISIT_OCCURRENCE table during which the Device was used.","device_exposure"
"visit_detail_id","No","INTEGER","A foreign key to the visit detail record in the VISIT_DETAIL table during which the Device was used.","device_exposure"
"device_source_value","No","VARCHAR(50)","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.","device_exposure"
"device_source_concept_id","Yes","INTEGER","A foreign key to a Device Concept that refers to the code used in the source.","device_exposure"
"drug_exposure_id","Yes","BIGINT","A system-generated unique identifier for each Drug utilization event.","drug_exposure"
"person_id","Yes","BIGINT","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.","drug_exposure"
"drug_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the 'Drug' domain.","drug_exposure"
"drug_exposure_start_date","No","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.","drug_exposure"
"drug_exposure_start_datetime","Yes","DATETIME","The start date and time for the current instance of Drug utilization. Valid entries include a start datetime of a prescription, the date and time a prescription was filled, or the date and time on which a Drug administration procedure was recorded.","drug_exposure"
"drug_exposure_end_date","No","DATE","The end date for the current instance of Drug utilization. Depending on different sources, it could be a known or an inferred date and denotes the last day at which the patient was still exposed to Drug.","drug_exposure"
"drug_exposure_end_datetime","No","DATETIME","The end date and time for the current instance of Drug utilization. Depending on different sources, it could be a known or an inferred date and time and denotes the last day at which the patient was still exposed to Drug.","drug_exposure"
"verbatim_end_date","No","DATE","The known end date of a drug_exposure as provided by the source.","drug_exposure"
"drug_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of Drug Exposure recorded. It indicates how the Drug Exposure was represented in the source data and belongs to the 'Drug Type' vocabulary.","drug_exposure"
"stop_reason","No","VARCHAR(20)","The reason the Drug was stopped. Reasons include regimen completed, changed, removed, etc.","drug_exposure"
"refills","No","INTEGER","The number of refills after the initial prescription. The initial prescription is not counted, values start with null.","drug_exposure"
"quantity","No","FLOAT","The quantity of drug as recorded in the original prescription or dispensing record.","drug_exposure"
"days_supply","No","INTEGER","The number of days of supply of the medication as prescribed. This reflects the intention of the provider for the length of exposure.","drug_exposure"
"sig","No","VARCHAR(MAX)","The directions ('signetur') on the Drug prescription as recorded in the original prescription (and printed on the container) or dispensing record.","drug_exposure"
"route_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies reflecting the route of administration and belonging to the 'Route' domain.","drug_exposure"
"lot_number","No","VARCHAR(50)","An identifier assigned to a particular quantity or lot of Drug product from the manufacturer.","drug_exposure"
"provider_id","No","INTEGER","A foreign key to the provider in the PROVIDER table who initiated (prescribed or administered) the Drug Exposure.","drug_exposure"
"visit_occurrence_id","No","INTEGER","A foreign key to the Visit in the VISIT_OCCURRENCE table during which the Drug Exposure was initiated.","drug_exposure"
"visit_detail_id","No","INTEGER","A foreign key to the Visit Detail in the VISIT_DETAIL table during which the Drug Exposure was initiated.","drug_exposure"
"drug_source_value","No","VARCHAR(50)","The source code for the Drug as it appears in the source data. This code is mapped to a Standard Drug concept in the Standardized Vocabularies and the original code is, stored here for reference.","drug_exposure"
"drug_source_concept_id","Yes","INTEGER","A foreign key to a Drug Concept that refers to the code used in the source.","drug_exposure"
"route_source_value","No","VARCHAR(50)","The information about the route of administration as detailed in the source.","drug_exposure"
"dose_unit_source_value","No","VARCHAR(50)","The information about the dose unit as detailed in the source.","drug_exposure"
"domain_concept_id_1","Yes","INTEGER","The concept representing the domain of fact one, from which the corresponding table can be inferred.","fact_relationship"
"fact_id_1","Yes","INTEGER","The unique identifier in the table corresponding to the domain of fact one.","fact_relationship"
"domain_concept_id_2","Yes","INTEGER","The concept representing the domain of fact two, from which the corresponding table can be inferred.","fact_relationship"
"fact_id_2","Yes","INTEGER","The unique identifier in the table corresponding to the domain of fact two.","fact_relationship"
"relationship_concept_id","Yes","INTEGER","A foreign key to a Standard Concept ID of relationship in the Standardized Vocabularies.","fact_relationship"
"measurement_id","Yes","INTEGER","A unique identifier for each Measurement.","measurement"
"person_id","Yes","INTEGER","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.","measurement"
"measurement_concept_id","Yes","INTEGER","A foreign key to the standard measurement concept identifier in the Standardized Vocabularies. These belong to the 'Measurement' domain, but could overlap with the 'Observation' domain (see #3 below).","measurement"
"measurement_date","No","DATE","The date of the Measurement.","measurement"
"measurement_datetime","Yes","DATETIME","The date and time of the Measurement. Some database systems don't have a datatype of time. To accommodate all temporal analyses, datatype datetime can be used (combining measurement_date and measurement_time [forum discussion](http://forums.ohdsi.org/t/date-time-and-datetime-problem-and-the-world-of-hours-and-1day/314))","measurement"
"measurement_time","No","VARCHAR(10)","The time of the Measurement. This is present for backwards compatibility and will be deprecated in an upcoming version","measurement"
"measurement_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the provenance from where the Measurement record was recorded. These belong to the 'Meas Type' vocabulary","measurement"
"operator_concept_id","No","INTEGER","A foreign key identifier to the predefined Concept in the Standardized Vocabularies reflecting the mathematical operator that is applied to the value_as_number. Operators are <, <=, =, >=, > and these concepts belong to the 'Meas Value Operator' domain.","measurement"
"value_as_number","No","FLOAT","A Measurement result where the result is expressed as a numeric value.","measurement"
"value_as_concept_id","No","INTEGER","A foreign key to a Measurement result represented as a Concept from the Standardized Vocabularies (e.g., positive/negative, present/absent, low/high, etc.). These belong to the 'Meas Value' domain","measurement"
"unit_concept_id","No","INTEGER","A foreign key to a Standard Concept ID of Measurement Units in the Standardized Vocabularies that belong to the 'Unit' domain.","measurement"
"range_low","No","FLOAT","The lower limit of the normal range of the Measurement result. The lower range is assumed to be of the same unit of measure as the Measurement value.","measurement"
"range_high","No","FLOAT","The upper limit of the normal range of the Measurement. The upper range is assumed to be of the same unit of measure as the Measurement value.","measurement"
"provider_id","No","INTEGER","A foreign key to the provider in the PROVIDER table who was responsible for initiating or obtaining the measurement.","measurement"
"visit_occurrence_id","No","INTEGER","A foreign key to the Visit in the VISIT_OCCURRENCE table during which the Measurement was recorded.","measurement"
"visit_detail_id","No","INTEGER","A foreign key to the Visit Detail in the VISIT_DETAIL table during which the Measurement was recorded.","measurement"
"measurement_source_value","No","VARCHAR(50)","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.","measurement"
"measurement_source_concept_id","Yes","INTEGER","A foreign key to a Concept in the Standard Vocabularies that refers to the code used in the source.","measurement"
"unit_source_value","No","VARCHAR(50)","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.","measurement"
"value_source_value","No","VARCHAR(50)","The source value associated with the content of the value_as_number or value_as_concept_id as stored in the source data.","measurement"
"note_id","Yes","INTEGER","A unique identifier for each note.","note"
"person_id","Yes","INTEGER","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.","note"
"note_event_id","No","INTEGER","A foreign key identifier to the event (e.g. Measurement, Procedure, Visit, Drug Exposure, etc) record during which the note was recorded.","note"
"note_event_field_concept_id","No","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the field to which the note_event_id is referring.","note"
"note_date","No","DATE","The date the note was recorded.","note"
"note_datetime","Yes","DATETIME","The date and time the note was recorded.","note"
"note_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the type, origin or provenance of the Note. These belong to the 'Note Type' vocabulary","note"
"note_class_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the HL7 LOINC Document Type Vocabulary classification of the note.","note"
"note_title","No","VARCHAR(250)","The title of the Note as it appears in the source.","note"
"note_text","Yes","VARCHAR(MAX)","The content of the Note.","note"
"encoding_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the note character encoding type","note"
"language_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the language of the note","note"
"provider_id","No","INTEGER","A foreign key to the Provider in the PROVIDER table who took the Note.","note"
"visit_occurrence_id","No","INTEGER","A foreign key to the Visit in the VISIT_OCCURRENCE table when the Note was taken.","note"
"visit_detail_id","No","INTEGER","A foreign key to the Visit in the VISIT_DETAIL table when the Note was taken.","note"
"note_source_value","No","VARCHAR(50)","The source value associated with the origin of the Note","note"
"note_nlp_id","Yes","INTEGER","A unique identifier for each term extracted from a note.","note_nlp"
"note_id","Yes","INTEGER","A foreign key to the Note table note the term was","note_nlp"
"section_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies representing the section of the extracted term.","note_nlp"
"snippet","No","VARCHAR(250)","A small window of text surrounding the term.","note_nlp"
"offset","No","VARCHAR(50)","Character offset of the extracted term in the input note.","note_nlp"
"lexical_variant","Yes","VARCHAR(250)","Raw text extracted from the NLP tool.","note_nlp"
"note_nlp_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the normalized concept for the extracted term. Domain of the term is represented as part of the Concept table.","note_nlp"
"note_nlp_source_concept_id","Yes","INTEGER","A foreign key to a Concept that refers to the code in the source vocabulary used by the NLP system","note_nlp"
"nlp_system","No","VARCHAR(250)","Name and version of the NLP system that extracted the term.Useful for data provenance.","note_nlp"
"nlp_date","Yes","DATE","The date of the note processing.Useful for data provenance.","note_nlp"
"nlp_datetime","No","DATETIME","The date and time of the note processing. Useful for data provenance.","note_nlp"
"term_exists","No","VARCHAR(1)","A summary modifier that signifies presence or absence of the term for a given patient. Useful for quick querying.","note_nlp"
"term_temporal","No","VARCHAR(50)","An optional time modifier associated with the extracted term. (for now “pastâ€<C3A2> or “presentâ€<C3A2> only). Standardize it later.","note_nlp"
"term_modifiers","No","VARCHAR(2000)","A compact description of all the modifiers of the specific term extracted by the NLP system. (e.g. “son has rashâ€<C3A2> ? “negated=no,subject=family, certainty=undef,conditional=false,general=falseâ€<C3A2>).","note_nlp"
"observation_id","Yes","INTEGER","A unique identifier for each observation.","observation"
"person_id","Yes","INTEGER","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.","observation"
"observation_concept_id","Yes","INTEGER","A foreign key to the standard observation concept identifier in the Standardized Vocabularies.","observation"
"observation_date","No","DATE","The date of the observation.","observation"
"observation_datetime","Yes","DATETIME","The date and time of the observation.","observation"
"observation_type_concept_id","Yes","INTEGER","A foreign key to the predefined concept identifier in the Standardized Vocabularies reflecting the type of the observation.","observation"
"value_as_number","No","FLOAT","The observation result stored as a number. This is applicable to observations where the result is expressed as a numeric value.","observation"
"value_as_string","No","VARCHAR(60)","The observation result stored as a string. This is applicable to observations where the result is expressed as verbatim text.","observation"
"value_as_concept_id","No","INTEGER","A foreign key to an observation result stored as a Concept ID. This is applicable to observations where the result can be expressed as a Standard Concept from the Standardized Vocabularies (e.g., positive/negative, present/absent, low/high, etc.).","observation"
"qualifier_concept_id","No","INTEGER","A foreign key to a Standard Concept ID for a qualifier (e.g., severity of drug-drug interaction alert)","observation"
"unit_concept_id","No","INTEGER","A foreign key to a Standard Concept ID of measurement units in the Standardized Vocabularies.","observation"
"provider_id","No","INTEGER","A foreign key to the provider in the PROVIDER table who was responsible for making the observation.","observation"
"visit_occurrence_id","No","INTEGER","A foreign key to the visit in the VISIT_OCCURRENCE table during which the observation was recorded.","observation"
"visit_detail_id","No","INTEGER","A foreign key to the visit in the VISIT_DETAIL table during which the observation was recorded.","observation"
"observation_source_value","No","VARCHAR(50)","The observation code 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.","observation"
"observation_source_concept_id","Yes","INTEGER","A foreign key to a Concept that refers to the code used in the source.","observation"
"unit_source_value","No","VARCHAR(50)","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.","observation"
"qualifier_source_value","No","VARCHAR(50)","The source value associated with a qualifier to characterize the observation","observation"
"observation_event_id","No","INTEGER","A foreign key to an event table (e.g., PROCEDURE_OCCURRENCE_ID).","observation"
"obs_event_field_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies referring to the field represented in the OBSERVATION_EVENT_ID.","observation"
"value_as_datetime","No","INTEGER","The observation result stored as a datetime value. This is applicable to observations where the result is expressed as a point in time.","observation"
"observation_period_id","Yes","INTEGER","A unique identifier for each observation period.","observation_period"
"person_id","Yes","INTEGER","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.","observation_period"
"observation_period_start_date","Yes","DATE","The start date of the observation period for which data are available from the data source.","observation_period"
"observation_period_end_date","Yes","DATE","The end date of the observation period for which data are available from the data source.","observation_period"
"period_type_concept_id","Yes","INTEGER","A foreign key identifier to the predefined concept in the Standardized Vocabularies reflecting the source of the observation period information, belonging to the 'Obs Period Type' vocabulary","observation_period"
"person_id","Yes","INTEGER","A unique identifier for each person.","person"
"gender_concept_id","Yes","INTEGER","A foreign key that refers to an identifier in the CONCEPT table for the unique gender of the person.","person"
"year_of_birth","Yes","INTEGER","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.","person"
"month_of_birth","No","INTEGER","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.","person"
"day_of_birth","No","INTEGER","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.","person"
"birth_datetime","No","DATETIME","The date and time of birth of the person.","person"
"death_datetime","No","DATETIME","The date and time of death of the person.","person"
"race_concept_id","Yes","INTEGER","A foreign key that refers to an identifier in the CONCEPT table for the unique race of the person, belonging to the 'Race' vocabulary.","person"
"ethnicity_concept_id","Yes","INTEGER","A foreign key that refers to the standard concept identifier in the Standardized Vocabularies for the ethnicity of the person, belonging to the 'Ethnicity' vocabulary.","person"
"location_id","No","INTEGER","A foreign key to the place of residency for the person in the location table, where the detailed address information is stored.","person"
"provider_id","No","INTEGER","A foreign key to the primary care provider the person is seeing in the provider table.","person"
"care_site_id","No","INTEGER","A foreign key to the site of primary care in the care_site table, where the details of the care site are stored.","person"
"person_source_value","No","VARCHAR(50)","An (encrypted) key derived from the person identifier in the source data. This is necessary when a use case requires a link back to the person data at the source dataset.","person"
"gender_source_value","No","VARCHAR(50)","The source code for the gender of the person as it appears in the source data. The person’s gender is mapped to a standard gender concept in the Standardized Vocabularies; the original value is stored here for reference.","person"
"gender_source_concept_id","Yes","INTEGER","A foreign key to the gender concept that refers to the code used in the source.","person"
"race_source_value","No","VARCHAR(50)","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 Standardized Vocabularies and the original value is stored here for reference.","person"
"race_source_concept_id","Yes","INTEGER","A foreign key to the race concept that refers to the code used in the source.","person"
"ethnicity_source_value","No","VARCHAR(50)","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 Standardized Vocabularies and the original code is, stored here for reference.","person"
"ethnicity_source_concept_id","Yes","INTEGER","A foreign key to the ethnicity concept that refers to the code used in the source.","person"
"procedure_occurrence_id","Yes","INTEGER","A system-generated unique identifier for each Procedure Occurrence.","procedure_occurrence"
"person_id","Yes","INTEGER","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.","procedure_occurrence"
"procedure_concept_id","Yes","INTEGER","A foreign key that refers to a standard procedure Concept identifier in the Standardized Vocabularies.","procedure_occurrence"
"procedure_date","No","DATE","The date on which the Procedure was performed.","procedure_occurrence"
"procedure_datetime","Yes","DATETIME","The date and time on which the Procedure was performed.","procedure_occurrence"
"procedure_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of source data from which the procedure record is derived, belonging to the 'Procedure Type' vocabulary.","procedure_occurrence"
"modifier_concept_id","Yes","INTEGER","A foreign key to a Standard Concept identifier for a modifier to the Procedure (e.g. bilateral). These concepts are typically distinguished by 'Modifier' concept classes (e.g., 'CPT4 Modifier' as part of the 'CPT4' vocabulary).","procedure_occurrence"
"quantity","No","INTEGER","The quantity of procedures ordered or administered.","procedure_occurrence"
"provider_id","No","INTEGER","A foreign key to the provider in the PROVIDER table who was responsible for carrying out the procedure.","procedure_occurrence"
"visit_occurrence_id","No","INTEGER","A foreign key to the Visit in the VISIT_OCCURRENCE table during which the Procedure was carried out.","procedure_occurrence"
"visit_detail_id","No","INTEGER","A foreign key to the Visit Detail in the VISIT_DETAIL table during which the Procedure was carried out.","procedure_occurrence"
"procedure_source_value","No","VARCHAR(50)","The source code for the Procedure as it appears in the source data. This code is mapped to a standard procedure Concept in the Standardized Vocabularies and the original code is, stored here for reference. Procedure source codes are typically ICD-9-Proc, CPT-4, HCPCS or OPCS-4 codes.","procedure_occurrence"
"procedure_source_concept_id","Yes","INTEGER","A foreign key to a Procedure Concept that refers to the code used in the source.","procedure_occurrence"
"modifier_source_value","No","VARCHAR(50)","The source code for the qualifier as it appears in the source data.","procedure_occurrence"
"specimen_id","Yes","INTEGER","A unique identifier for each specimen.","specimen"
"person_id","Yes","INTEGER","A foreign key identifier to the Person for whom the Specimen is recorded.","specimen"
"specimen_concept_id","Yes","INTEGER","A foreign key referring to a Standard Concept identifier in the Standardized Vocabularies for the Specimen.","specimen"
"specimen_type_concept_id","Yes","INTEGER","A foreign key referring to the Concept identifier in the Standardized Vocabularies reflecting the system of record from which the Specimen was represented in the source data.","specimen"
"specimen_date","No","DATE","The date the specimen was obtained from the Person.","specimen"
"specimen_datetime","Yes","DATETIME","The date and time on the date when the Specimen was obtained from the person.","specimen"
"quantity","No","FLOAT","The amount of specimen collection from the person during the sampling procedure.","specimen"
"unit_concept_id","No","INTEGER","A foreign key to a Standard Concept identifier for the Unit associated with the numeric quantity of the Specimen collection.","specimen"
"anatomic_site_concept_id","Yes","INTEGER","A foreign key to a Standard Concept identifier for the anatomic location of specimen collection.","specimen"
"disease_status_concept_id","Yes","INTEGER","A foreign key to a Standard Concept identifier for the Disease Status of specimen collection.","specimen"
"specimen_source_id","No","VARCHAR(50)","The Specimen identifier as it appears in the source data.","specimen"
"specimen_source_value","No","VARCHAR(50)","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.","specimen"
"unit_source_value","No","VARCHAR(50)","The information about the Unit as detailed in the source.","specimen"
"anatomic_site_source_value","No","VARCHAR(50)","The information about the anatomic site as detailed in the source.","specimen"
"disease_status_source_value","No","VARCHAR(50)","The information about the disease status as detailed in the source.","specimen"
"survey_conduct_id","Yes","INTEGER","Unique identifier for each completed survey.","survey_conduct"
"person_id","Yes","INTEGER","A foreign key identifier to the Person in the PERSON table about whom the survey was completed.","survey_conduct"
"survey_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the name and identity of the survey.","survey_conduct"
"survey_start_date","No","DATE","Date on which the survey was started.","survey_conduct"
"survey_start_datetime","No","DATETIME","Date and time the survey was started.","survey_conduct"
"survey_end_date","Yes","DATE","Date on which the survey was completed.","survey_conduct"
"survey_end_datetime","No","DATETIME","Date and time the survey was completed.","survey_conduct"
"provider_id","NoÂ","INTEGERÂ","A foreign key to the provider in the provider table who was associated with the survey completion.","survey_conduct"
"assisted_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies indicating whether the survey was completed with assistance.","survey_conduct"
"respondent_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the respondent type. Example: Research Associate, Patient.","survey_conduct"
"timing_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies that refers to a certain timing. Example: 3 month follow-up, 6 month follow-up.","survey_conduct"
"collection_method_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the data collection method (e.g. Paper, Telephone, Electronic Questionnaire).","survey_conduct"
"assisted_source_value","No","VARCHAR(50)","Source value representing whether patient required assistance to complete the survey. Example: “Completed without assistanceâ€<C3A2>, â€<C3A2>Completed with assistanceâ€<C3A2>.","survey_conduct"
"respondent_type_source_value","No","VARCHAR(100)","Source code representing role of person who completed the survey.","survey_conduct"
"timing_source_value","No","VARCHAR(100)","Text string representing the timing of the survey. Example: Baseline, 6-month follow-up.","survey_conduct"
"collection_method_source_value","No","VARCHAR(100)","The collection method as it appears in the source data.","survey_conduct"
"survey_source_value","No","VARCHAR(100)","The survey name/title as it appears in the source data.","survey_conduct"
"survey_source_concept_id","Yes","INTEGER","A foreign key to a predefined Concept that refers to the code for the survey name/title used in the source.","survey_conduct"
"survey_source_identifier","No","VARCHAR(100)","Unique identifier for each completed survey in source system.","survey_conduct"
"validated_survey_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the validation status of the survey.","survey_conduct"
"validated_survey_source_value","No","INTEGER","Source value representing the validation status of the survey.","survey_conduct"
"survey_version_number","No","VARCHAR(20)","Version number of the questionnaire or survey used.","survey_conduct"
"visit_occurrence_id","No","INTEGER","A foreign key to the VISIT_OCCURRENCE table during which the survey was completed","survey_conduct"
"response_visit_occurrence_id","No","INTEGERÂ","A foreign key to the visit in the VISIT_OCCURRENCE table during which treatment was carried out that relates to this survey.","survey_conduct"
"visit_detail_id","Yes","INTEGER","A unique identifier for each Person's visit or encounter at a healthcare provider.","visit_detail"
"person_id","Yes","INTEGER","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.","visit_detail"
"visit_detail_concept_id","Yes","INTEGER","A foreign key that refers to a visit Concept identifier in the Standardized Vocabularies belonging to the 'Visit' Vocabulary.","visit_detail"
"visit_detail_start_date","No","DATE","The start date of the visit.","visit_detail"
"visit_detail_start_datetime","Yes","DATETIME","The date and time of the visit started.","visit_detail"
"visit_detail_end_date","No","DATE","The end date of the visit. If this is a one-day visit the end date should match the start date.","visit_detail"
"visit_detail_end_datetime","Yes","DATETIME","The date and time of the visit end.","visit_detail"
"visit_detail_type_concept_id","Yes","INTEGER","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 belonging to the 'Visit Type' vocabulary.","visit_detail"
"provider_id","No","INTEGER","A foreign key to the provider in the provider table who was associated with the visit.","visit_detail"
"care_site_id","No","INTEGER","A foreign key to the care site in the care site table that was visited.","visit_detail"
"visit_detail_source_value","No","STRING(50)","The source code for the visit as it appears in the source data.","visit_detail"
"visit_detail_source_concept_id","Yes","INTEGER","A foreign key to a Concept that refers to the code used in the source.","visit_detail"
"admitted_from_source_value","No","VARCHAR(50)","The source code for the admitting source as it appears in the source data.","visit_detail"
"admitted_from_concept_id","Yes","INTEGER","A foreign key to the predefined concept in the 'Place of Service' Vocabulary reflecting the admitting source for a visit.","visit_detail"
"discharge_to_source_value","No","VARCHAR(50)","The source code for the discharge disposition as it appears in the source data.","visit_detail"
"discharge_to_concept_id","Yes","INTEGER","A foreign key to the predefined concept in the 'Place of Service' Vocabulary reflecting the discharge disposition for a visit.","visit_detail"
"preceding_visit_detail_id","No","INTEGER","A foreign key to the VISIT_DETAIL table of the visit immediately preceding this visit","visit_detail"
"visit_detail_parent_id","No","INTEGER","A foreign key to the VISIT_DETAIL table record to represent the immediate parent visit-detail record.","visit_detail"
"visit_occurrence_id","Yes","INTEGER","A foreign key that refers to the record in the VISIT_OCCURRENCE table. This is a required field, because for every visit_detail is a child of visit_occurrence and cannot exist without a corresponding parent record in visit_occurrence.","visit_detail"
"visit_occurrence_id","Yes","INTEGER","A unique identifier for each Person's visit or encounter at a healthcare provider.","visit_occurrence"
"person_id","Yes","INTEGER","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.","visit_occurrence"
"visit_concept_id","Yes","INTEGER","A foreign key that refers to a visit Concept identifier in the Standardized Vocabularies belonging to the 'Visit' Vocabulary.","visit_occurrence"
"visit_start_date","No","DATE","The start date of the visit.","visit_occurrence"
"visit_start_datetime","Yes","DATETIME","The date and time of the visit started.","visit_occurrence"
"visit_end_date","No","DATE","The end date of the visit. If this is a one-day visit the end date should match the start date.","visit_occurrence"
"visit_end_datetime","Yes","DATETIME","The date and time of the visit end.","visit_occurrence"
"visit_type_concept_id","Yes","INTEGER","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 belonging to the 'Visit Type' vocabulary.","visit_occurrence"
"provider_id","No","INTEGER","A foreign key to the provider in the provider table who was associated with the visit.","visit_occurrence"
"care_site_id","No","INTEGER","A foreign key to the care site in the care site table that was visited.","visit_occurrence"
"visit_source_value","No","VARCHAR(50)","The source code for the visit as it appears in the source data.","visit_occurrence"
"visit_source_concept_id","Yes","INTEGER","A foreign key to a Concept that refers to the code used in the source.","visit_occurrence"
"admitting_source_concept_id","Yes","INTEGER","A foreign key to the predefined concept in the Place of Service Vocabulary reflecting the admitting source for a visit.","visit_occurrence"
"admitting_source_value","No","VARCHAR(50)","The source code for the admitting source as it appears in the source data.","visit_occurrence"
"discharge_to_concept_id","Yes","INTEGER","A foreign key to the predefined concept in the Place of Service Vocabulary reflecting the discharge disposition for a visit.","visit_occurrence"
"discharge_to_source_value","No","VARCHAR(50)","The source code for the discharge disposition as it appears in the source data.","visit_occurrence"
"preceding_visit_occurrence_id","No","INTEGER","A foreign key to the VISIT_OCCURRENCE table of the visit immediately preceding this visit","visit_occurrence"
"condition_era_id","Yes","INTEGER","A unique identifier for each Condition Era.","condition_era"
"person_id","Yes","INTEGER","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.","condition_era"
"condition_concept_id","Yes","INTEGER","A foreign key that refers to a standard Condition Concept identifier in the Standardized Vocabularies.","condition_era"
"condition_era_start_datetime","Yes","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.","condition_era"
"condition_era_end_datetime","Yes","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.","condition_era"
"condition_occurrence_count","No","INTEGER","The number of individual Condition Occurrences used to construct the condition era.","condition_era"
"dose_era_id","Yes","INTEGER","A unique identifier for each Dose Era.","dose_era"
"person_id","Yes","INTEGER","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.","dose_era"
"drug_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the active Ingredient Concept.","dose_era"
"unit_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the unit concept.","dose_era"
"dose_value","Yes","FLOAT","The numeric value of the dose.","dose_era"
"dose_era_start_datetime","Yes","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.","dose_era"
"dose_era_end_datetime","Yes","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.","dose_era"
"drug_era_id","Yes","INTEGER","A unique identifier for each Drug Era.","drug_era"
"person_id","Yes","INTEGER","A foreign key identifier to the Person who is subjected to the Drug during the fDrug Era. The demographic details of that Person are stored in the PERSON table.","drug_era"
"drug_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the Ingredient Concept.","drug_era"
"drug_era_start_datetime","Yes","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 conutilization of a Drug.","drug_era"
"drug_era_end_datetime","Yes","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.","drug_era"
"drug_exposure_count","No","INTEGER","The number of individual Drug Exposure occurrences used to construct the Drug Era.","drug_era"
"gap_days","No","INTEGER","The number of days that are not covered by DRUG_EXPOSURE records that were used to make up the era record.","drug_era"
"cost_id","Yes","INTEGER","A unique identifier for each COST record.","cost"
"person_id","Yes","INTEGER","A unique identifier for each PERSON.","cost"
"cost_event_id","Yes","INTEGER","A foreign key identifier to the event (e.g. Measurement, Procedure, Visit, Drug Exposure, etc) record for which cost data are recorded.","cost"
"cost_event_field_concept_id","Yes","INTEGER","A foreign key identifier to a concept in the CONCEPT table representing the identity of the field represented by COST_EVENT_ID","cost"
"cost_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Cost Concept identifier in the Standardized Vocabularies belonging to the 'Cost' vocabulary.","cost"
"cost_type_concept_id","Yes","INTEGER","A foreign key identifier to a concept in the CONCEPT table for the provenance or the source of the COST data and belonging to the 'Cost Type' vocabulary","cost"
"cost_source_concept_id","Yes","INTEGER","A foreign key to a Cost Concept that refers to the code used in the source.","cost"
"cost_source_value","No","VARCHAR(50)","The source value for the cost as it appears in the source data","cost"
"currency_concept_id","Yes","INTEGER","A foreign key identifier to the concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar. These belong to the 'Currency' vocabulary","cost"
"cost","Yes","FLOAT","The actual financial cost amount","cost"
"incurred_date","Yes","DATE","The first date of service of the clinical event corresponding to the cost as in table capturing the information (e.g. date of visit, date of procedure, date of condition, date of drug etc).","cost"
"billed_date","No","DATE","The date a bill was generated for a service or encounter","cost"
"paid_date","No","DATE","The date payment was received for a service or encounter","cost"
"revenue_code_concept_id","Yes","INTEGER","A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for Revenue codes belonging to the 'Revenue Code' vocabulary.","cost"
"drg_concept_id","Yes","INTEGER","A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for DRG codes belonging to the 'DRG' vocabulary.","cost"
"revenue_code_source_value","No","VARCHAR(50)","The source value for the Revenue code as it appears in the source data, stored here for reference.","cost"
"drg_source_value","No","VARCHAR(50)","The source value for the 3-digit DRG source code as it appears in the source data, stored here for reference.","cost"
"payer_plan_period_id","No","INTEGER","A foreign key to the PAYER_PLAN_PERIOD table, where the details of the Payer, Plan and Family are stored. Record the payer_plan_id that relates to the payer who contributed to the paid_by_payer field.","cost"
"payer_plan_period_id","Yes","INTEGER","A identifier for each unique combination of payer, plan, family code and time span.","payer_plan_period"
"person_id","Yes","INTEGER","A foreign key identifier to the Person covered by the payer. The demographic details of that Person are stored in the PERSON table.","payer_plan_period"
"contract_person_id","No","INTEGER","A foreign key identifier to the person_id in person table, for the person who is the primary subscriber/contract owner for the record in the payer_plan_period table. Maybe the same person or different person, depending on who is the primary subscriber/contract owner.","payer_plan_period"
"payer_plan_period_start_date","Yes","DATE","The start date of the payer plan period.","payer_plan_period"
"payer_plan_period_end_date","Yes","DATE","The end date of the payer plan period.","payer_plan_period"
"payer_concept_id","Yes","INTEGER","A foreign key that refers to a standard Payer concept identifier in the Standarized Vocabularies","payer_plan_period"
"payer_source_value","No","VARCHAR(50)","The source code for the payer as it appears in the source data.","payer_plan_period"
"payer_source_concept_id","Yes","INTEGER","A foreign key to a payer concept that refers to the code used in the source.","payer_plan_period"
"plan_concept_id","Yes","INTEGER","A foreign key that refers to a standard plan concept identifier that represents the health benefit plan in the Standardized Vocabularies.","payer_plan_period"
"plan_source_value","No","VARCHAR(50)","The source code for the Person's health benefit plan as it appears in the source data.","payer_plan_period"
"plan_source_concept_id","Yes","INTEGER","A foreign key to a plan concept that refers to the plan code used in the source data.","payer_plan_period"
"contract_concept_id","Yes","INTEGER","A foreign key to a standard concept representing the reason justifying the contract between person_id and contract_person_id.","payer_plan_period"
"contract_source_value","No","INTEGER","The source code representing the reason justifying the contract. Usually it is family relationship like a spouse, domestic partner, child etc.","payer_plan_period"
"contract_source_concept_id","Yes","INTEGER","A foreign key to a concept that refers to the code used in the source as the reason justifying the contract.","payer_plan_period"
"sponsor_concept_id","Yes","INTEGER","A foreign key that refers to a concept identifier that represents the sponsor in the Standardized Vocabularies.","payer_plan_period"
"sponsor_source_value","No","VARCHAR(50)","The source code for the Person's sponsor of the health plan as it appears in the source data.","payer_plan_period"
"sponsor_source_concept_id","Yes","INTEGER","A foreign key to a sponsor concept that refers to the sponsor code used in the source data.","payer_plan_period"
"family_source_value","No","VARCHAR(50)","The source code for the Person's family as it appears in the source data.","payer_plan_period"
"stop_reason_concept_id","Yes","INTEGER","A foreign key that refers to a standard termination reason that represents the reason for the termination in the Standardized Vocabularies.","payer_plan_period"
"stop_reason_source_value","No","VARCHAR(50)","The reason for stop-coverage as it appears in the source data.","payer_plan_period"
"stop_reason_source_concept_id","Yes","INTEGER","A foreign key to a stop-coverage concept that refers to the code used in the source.","payer_plan_period"
"care_site_id","Yes","INTEGER","A unique identifier for each Care Site.","care_site"
"care_site_name","No","VARCHAR(255)","The verbatim description or name of the Care Site as in data source","care_site"
"place_of_service_concept_id","Yes","INTEGER","A foreign key that refers to a Place of Service Concept ID in the Standardized Vocabularies.","care_site"
"location_id","No","INTEGER","A foreign key to the geographic Location in the LOCATION table, where the detailed address information is stored.","care_site"
"care_site_source_value","No","VARCHAR(50)","The identifier for the Care Site in the source data, stored here for reference.","care_site"
"place_of_service_source_value","No","VARCHAR(50)","The source code for the Place of Service as it appears in the source data, stored here for reference.","care_site"
"location_id","Yes","INTEGER","A unique identifier for each geographic location.","location"
"address_1","No","VARCHAR(50)","The address field 1, typically used for the street address, as it appears in the source data.","location"
"address_2","No","VARCHAR(50)","The address field 2, typically used for additional detail such as buildings, suites, floors, as it appears in the source data.","location"
"city","No","VARCHAR(50)","The city field as it appears in the source data.","location"
"state","No","VARCHAR(2)","The state field as it appears in the source data.","location"
"zip","No","VARCHAR(9)","The zip or postal code.","location"
"county","No","VARCHAR(20)","The county.","location"
"country","No","VARCHAR(100)","The country","location"
"location_source_value","No","VARCHAR(50)","The verbatim information that is used to uniquely identify the location as it appears in the source data.","location"
"latitude","No","FLOAT","The geocoded latitude","location"
"longitude","No","FLOAT","The geocoded longitude","location"
"location_id","Yes","INTEGER","A foreign key to the location table.","location_history"
"relationship_type_concept_id","Yes","VARCHAR(50)","The type of relationship between location and entity.","location_history"
"domain_id","Yes","VARCHAR(50)","The domain of the entity that is related to the location. Either PERSON, PROVIDER, or CARE_SITE.","location_history"
"entity_id","Yes","INTEGER","The unique identifier for the entity. References either person_id, provider_id, or care_site_id, depending on domain_id.","location_history"
"start_date","Yes","DATE","The date the relationship started.","location_history"
"end_date","No","DATE","The date the relationship ended.","location_history"
"provider_id","Yes","INTEGER","A unique identifier for each Provider.","provider"
"provider_name","No","VARCHAR(255)","A description of the Provider.","provider"
"npi","No","VARCHAR(20)","The National Provider Identifier (NPI) of the provider.","provider"
"dea","No","VARCHAR(20)","The Drug Enforcement Administration (DEA) number of the provider.","provider"
"specialty_concept_id","Yes","INTEGER","A foreign key to a Standard Specialty Concept ID in the Standardized Vocabularies.","provider"
"care_site_id","No","INTEGER","A foreign key to the main Care Site where the provider is practicing.","provider"
"year_of_birth","No","INTEGER","The year of birth of the Provider.","provider"
"gender_concept_id","Yes","INTEGER","The gender of the Provider.","provider"
"provider_source_value","No","VARCHAR(50)","The identifier used for the Provider in the source data, stored here for reference.","provider"
"specialty_source_value","No","VARCHAR(50)","The source code for the Provider specialty as it appears in the source data, stored here for reference.","provider"
"specialty_source_concept_id","Yes","INTEGER","A foreign key to a Concept that refers to the code used in the source.","provider"
"gender_source_value","No","VARCHAR(50)","The gender code for the Provider as it appears in the source data, stored here for reference.","provider"
"gender_source_concept_id","Yes","INTEGER","A foreign key to a Concept that refers to the code used in the source.","provider"
"cdm_source_name","Yes","VARCHAR(255)","The full name of the source","cdm_source"
"cdm_source_abbreviation","No","VARCHAR(25)","An abbreviation of the name","cdm_source"
"cdm_holder","No","VARCHAR(255)","The name of the organization responsible for the development of the CDM instance","cdm_source"
"source_description","No","CLOB","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.","cdm_source"
"source_documentation_reference","No","VARCHAR(255)","URL or other external reference to location of source documentation","cdm_source"
"cdm_etl_reference","No","VARCHAR(255)","URL or other external reference to location of ETL specification documentation and ETL source code","cdm_source"
"source_release_date","No","DATE","The date for which the source data are most current, such as the last day of data capture","cdm_source"
"cdm_release_date","No","DATE","The date when the CDM was instantiated","cdm_source"
"cdm_version","No","VARCHAR(10)","The version of CDM used","cdm_source"
"vocabulary_version","No","VARCHAR(20)","The version of the vocabulary used","cdm_source"
"metadata_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Metadata Concept identifier in the Standardized Vocabularies.","metadata"
"metadata_type_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Type Concept identifier in the Standardized Vocabularies.","metadata"
"name","Yes","VARCHAR(250)","The name of the Concept stored in metadata_concept_id or a description of the data being stored.","metadata"
"value_as_string","No","NVARCHAR","The metadata value stored as a string.","metadata"
"value_as_concept_id","No","INTEGER","A foreign key to a metadata value stored as a Concept ID.","metadata"
"metadata date","No","DATE","The date associated with the metadata","metadata"
"metadata_datetime","No","DATETIME","The date and time associated with the metadata","metadata"
"concept_id","Yes","INTEGER","A unique identifier for each Concept across all domains.","concept"
"concept_name","Yes","VARCHAR(255)","An unambiguous, meaningful and descriptive name for the Concept.","concept"
"domain_id","Yes","VARCHAR(20)","A foreign key to the [DOMAIN](https://github.com/OHDSI/CommonDataModel/wiki/DOMAIN) table the Concept belongs to.","concept"
"vocabulary_id","Yes","VARCHAR(20)","A foreign key to the [VOCABULARY](https://github.com/OHDSI/CommonDataModel/wiki/VOCABULARY) table indicating from which source the Concept has been adapted.","concept"
"concept_class_id","Yes","VARCHAR(20)","The attribute or concept class of the Concept. Examples are 'Clinical Drug', 'Ingredient', 'Clinical Finding' etc.","concept"
"standard_concept","No","VARCHAR(1)","This flag determines where a Concept is a Standard Concept, i.e. is used in the data, a Classification Concept, or a non-standard Source Concept. The allowables values are 'S' (Standard Concept) and 'C' (Classification Concept), otherwise the content is NULL.","concept"
"concept_code","Yes","VARCHAR(50)","The concept code represents the identifier of the Concept in the source vocabulary, such as SNOMED-CT concept IDs, RxNorm RXCUIs etc. Note that concept codes are not unique across vocabularies.","concept"
"valid_start_date","Yes","DATE","The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.","concept"
"valid_end_date","Yes","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, meaning, the Concept is valid until it becomes deprecated.","concept"
"invalid_reason","No","VARCHAR(1)","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.","concept"
"ancestor_concept_id","Yes","INTEGER","A foreign key to the concept in the concept table for the higher-level concept that forms the ancestor in the relationship.","concept_ancestor"
"descendant_concept_id","Yes","INTEGER","A foreign key to the concept in the concept table for the lower-level concept that forms the descendant in the relationship.","concept_ancestor"
"min_levels_of_separation","Yes","INTEGER","The minimum separation in number of levels of hierarchy between ancestor and descendant concepts. This is an attribute that is used to simplify hierarchic analysis.","concept_ancestor"
"max_levels_of_separation","Yes","INTEGER","The maximum separation in number of levels of hierarchy between ancestor and descendant concepts. This is an attribute that is used to simplify hierarchic analysis.","concept_ancestor"
"concept_class_id","Yes","VARCHAR(20)","A unique key for each class.","concept_class"
"concept_class_name","Yes","VARCHAR(255)","The name describing the Concept Class, e.g. ""Clinical Finding"", ""Ingredient"", etc.","concept_class"
"concept_class_concept_id","Yes","INTEGER","A foreign key that refers to an identifier in the [CONCEPT](https://github.com/OHDSI/CommonDataModel/wiki/CONCEPT) table for the unique Concept Class the record belongs to.","concept_class"
"concept_id_1","Yes","INTEGER","A foreign key to a Concept in the [CONCEPT](https://github.com/OHDSI/CommonDataModel/wiki/CONCEPT) table associated with the relationship. Relationships are directional, and this field represents the source concept designation.","concept_relationship"
"concept_id_2","Yes","INTEGER","A foreign key to a Concept in the [CONCEPT](https://github.com/OHDSI/CommonDataModel/wiki/CONCEPT) table associated with the relationship. Relationships are directional, and this field represents the destination concept designation.","concept_relationship"
"relationship_id","Yes","VARCHAR(20)","A unique identifier to the type or nature of the Relationship as defined in the [RELATIONSHIP](https://github.com/OHDSI/CommonDataModel/wiki/RELATIONSHIP) table.","concept_relationship"
"valid_start_date","Yes","DATE","The date when the instance of the Concept Relationship is first recorded.","concept_relationship"
"valid_end_date","Yes","DATE","The date when the Concept Relationship became invalid because it was deleted or superseded (updated) by a new relationship. Default value is 31-Dec-2099.","concept_relationship"
"invalid_reason","No","VARCHAR(1)","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.","concept_relationship"
"concept_id","Yes","INTEGER","A foreign key to the Concept in the CONCEPT table.","concept_synonym"
"concept_synonym_name","Yes","VARCHAR(1000)","The alternative name for the Concept.","concept_synonym"
"language_concept_id","Yes","INTEGER","A foreign key to a Concept representing the language.","concept_synonym"
"domain_id","Yes","VARCHAR(20)","A unique key for each domain.","domain"
"domain_name","Yes","VARCHAR(255)","The name describing the Domain, e.g. ""Condition"", ""Procedure"", ""Measurement"" etc.","domain"
"domain_concept_id","Yes","INTEGER","A foreign key that refers to an identifier in the [CONCEPT](https://github.com/OHDSI/CommonDataModel/wiki/CONCEPT) table for the unique Domain Concept the Domain record belongs to.","domain"
"drug_concept_id","Yes","INTEGER","A foreign key to the Concept in the CONCEPT table representing the identifier for Branded Drug or Clinical Drug Concept.","drug_strength"
"ingredient_concept_id","Yes","INTEGER","A foreign key to the Concept in the CONCEPT table, representing the identifier for drug Ingredient Concept contained within the drug product.","drug_strength"
"amount_value","No","FLOAT","The numeric value associated with the amount of active ingredient contained within the product.","drug_strength"
"amount_unit_concept_id","No","INTEGER","A foreign key to the Concept in the CONCEPT table representing the identifier for the Unit for the absolute amount of active ingredient.","drug_strength"
"numerator_value","No","FLOAT","The numeric value associated with the concentration of the active ingredient contained in the product","drug_strength"
"numerator_unit_concept_id","No","INTEGER","A foreign key to the Concept in the CONCEPT table representing the identifier for the numerator Unit for the concentration of active ingredient.","drug_strength"
"denominator_value","No","FLOAT","The amount of total liquid (or other divisible product, such as ointment, gel, spray, etc.).","drug_strength"
"denominator_unit_concept_id","No","INTEGER","A foreign key to the Concept in the CONCEPT table representing the identifier for the denominator Unit for the concentration of active ingredient.","drug_strength"
"box_size","No","INTEGER","The number of units of Clinical of Branded Drug, or Quantified Clinical or Branded Drug contained in a box as dispensed to the patient","drug_strength"
"valid_start_date","Yes","DATE","The date when the Concept was first recorded. The default value is 1-Jan-1970.","drug_strength"
"valid_end_date","Yes","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.","drug_strength"
"invalid_reason","No","VARCHAR(1)","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.","drug_strength"
"relationship_id","Yes","VARCHAR(20)","The type of relationship captured by the relationship record.","relationship"
"relationship_name","Yes","VARCHAR(255)","The text that describes the relationship type.","relationship"
"is_hierarchical","Yes","VARCHAR(1)","Defines whether a relationship defines concepts into classes or hierarchies. Values are 1 for hierarchical relationship or 0 if not.","relationship"
"defines_ancestry","Yes","VARCHAR(1)","Defines whether a hierarchical relationship contributes to the concept_ancestor table. These are subsets of the hierarchical relationships. Valid values are 1 or 0.","relationship"
"reverse_relationship_id","Yes","VARCHAR(20)","The identifier for the relationship used to define the reverse relationship between two concepts.","relationship"
"relationship_concept_id","Yes","INTEGER","A foreign key that refers to an identifier in the CONCEPT table for the unique relationship concept.","relationship"
"source_code","Yes","VARCHAR(50)","The source code being translated into a Standard Concept.","source_to_concept_map"
"source_concept_id","Yes","INTEGER","A foreign key to the Source Concept that is being translated into a Standard Concept.","source_to_concept_map"
"source_vocabulary_id","Yes","VARCHAR(20)","A foreign key to the VOCABULARY table defining the vocabulary of the source code that is being translated to a Standard Concept.","source_to_concept_map"
"source_code_description","No","VARCHAR(255)","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.","source_to_concept_map"
"target_concept_id","Yes","INTEGER","A foreign key to the target Concept to which the source code is being mapped.","source_to_concept_map"
"target_vocabulary_id","Yes","VARCHAR(20)","A foreign key to the VOCABULARY table defining the vocabulary of the target Concept.","source_to_concept_map"
"valid_start_date","Yes","DATE","The date when the mapping instance was first recorded.","source_to_concept_map"
"valid_end_date","Yes","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.","source_to_concept_map"
"invalid_reason","No","VARCHAR(1)","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.","source_to_concept_map"
"vocabulary_id","Yes","VARCHAR(20)","A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit.","vocabulary"
"vocabulary_name","Yes","VARCHAR(255)","The name describing the vocabulary, for example ""International Classification of Diseases, Ninth Revision, Clinical Modification, Volume 1 and 2 (NCHS)"" etc.","vocabulary"
"vocabulary_reference","Yes","VARCHAR(255)","External reference to documentation or available download of the about the vocabulary.","vocabulary"
"vocabulary_version","No","VARCHAR(255)","Version of the Vocabulary as indicated in the source.","vocabulary"
"vocabulary_concept_id","Yes","INTEGER","A foreign key that refers to a standard concept identifier in the CONCEPT table for the Vocabulary the VOCABULARY record belongs to.","vocabulary"
1 field required type description table
2 cohort_definition_id Yes INTEGER A foreign key to a record in the COHORT_DEFINITION table containing relevant Cohort Definition information. cohort
3 subject_id Yes INTEGER A foreign key to the subject in the cohort. These could be referring to records in the PERSON, PROVIDER, VISIT_OCCURRENCE table. cohort
4 cohort_start_date Yes DATE The date when the Cohort Definition criteria for the Person, Provider or Visit first match. cohort
5 cohort_end_date Yes DATE The date when the Cohort Definition criteria for the Person, Provider or Visit no longer match or the Cohort membership was terminated. cohort
6 cohort_definition_id Yes INTEGER A unique identifier for each Cohort. cohort_definition
7 cohort_definition_name Yes VARCHAR(255) A short description of the Cohort. cohort_definition
8 cohort_definition_description No VARCHAR(MAX) A complete description of the Cohort definition cohort_definition
9 definition_type_concept_id Yes INTEGER Type defining what kind of Cohort Definition the record represents and how the syntax may be executed cohort_definition
10 cohort_definition_syntax No VARCHAR(MAX) Syntax or code to operationalize the Cohort definition cohort_definition
11 subject_concept_id Yes INTEGER A foreign key to the Concept to which defines the domain of subjects that are members of the cohort (e.g., Person, Provider, Visit). cohort_definition
12 cohort_initiation_date No DATE A date to indicate when the Cohort was initiated in the COHORT table cohort_definition
13 condition_occurrence_id Yes BIGINT A unique identifier for each Condition Occurrence event. condition_occurrence
14 person_id Yes BIGINT A foreign key identifier to the Person who is experiencing the condition. The demographic details of that Person are stored in the PERSON table. condition_occurrence
15 condition_concept_id Yes INTEGER A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the 'Condition' domain. condition_occurrence
16 condition_start_date No DATE The date when the instance of the Condition is recorded. condition_occurrence
17 condition_start_datetime Yes DATETIME The date and time when the instance of the Condition is recorded. condition_occurrence
18 condition_end_date No DATE The date when the instance of the Condition is considered to have ended. condition_occurrence
19 condition_end_datetime No DATETIME The date when the instance of the Condition is considered to have ended. condition_occurrence
20 condition_type_concept_id Yes INTEGER A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the source data from which the Condition was recorded, the level of standardization, and the type of occurrence. These belong to the 'Condition Type' vocabulary condition_occurrence
21 condition_status_concept_id Yes INTEGER A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies reflecting the point of care at which the Condition was diagnosed. condition_occurrence
22 stop_reason No VARCHAR(20) The reason that the Condition was no longer present, as indicated in the source data. condition_occurrence
23 provider_id No INTEGER A foreign key to the Provider in the PROVIDER table who was responsible for capturing (diagnosing) the Condition. condition_occurrence
24 visit_occurrence_id No INTEGER A foreign key to the visit in the VISIT_OCCURRENCE table during which the Condition was determined (diagnosed). condition_occurrence
25 visit_detail_id No INTEGER A foreign key to the visit in the VISIT_DETAIL table during which the Condition was determined (diagnosed). condition_occurrence
26 condition_source_value No VARCHAR(50) The source code for the Condition as it appears in the source data. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference. condition_occurrence
27 condition_source_concept_id Yes INTEGER A foreign key to a Condition Concept that refers to the code used in the source. condition_occurrence
28 condition_status_source_value No VARCHAR(50) The source code for the condition status 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. condition_occurrence
29 device_exposure_id Yes BIGINT A system-generated unique identifier for each Device Exposure. device_exposure
30 person_id Yes BIGINT A foreign key identifier to the Person who is subjected to the Device. The demographic details of that Person are stored in the PERSON table. device_exposure
31 device_concept_id Yes INTEGER A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the 'Device' domain. device_exposure
32 device_exposure_start_date No DATE The date the Device or supply was applied or used. device_exposure
33 device_exposure_start_datetime Yes DATETIME The date and time the Device or supply was applied or used. device_exposure
34 device_exposure_end_date No DATE The date use of the Device or supply was ceased. device_exposure
35 device_exposure_end_datetime No DATETIME The date and time use of the Device or supply was ceased. device_exposure
36 device_type_concept_id Yes INTEGER A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of Device Exposure recorded. It indicates how the Device Exposure was represented in the source data and belongs to the 'Device Type' domain. device_exposure
37 unique_device_id No VARCHAR(50) A UDI or equivalent identifying the instance of the Device used in the Person. device_exposure
38 quantity No INTEGER The number of individual Devices used in the exposure. device_exposure
39 provider_id No INTEGER A foreign key to the provider in the PROVIDER table who initiated or administered the Device. device_exposure
40 visit_occurrence_id No INTEGER A foreign key to the visit in the VISIT_OCCURRENCE table during which the Device was used. device_exposure
41 visit_detail_id No INTEGER A foreign key to the visit detail record in the VISIT_DETAIL table during which the Device was used. device_exposure
42 device_source_value No VARCHAR(50) 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. device_exposure
43 device_source_concept_id Yes INTEGER A foreign key to a Device Concept that refers to the code used in the source. device_exposure
44 drug_exposure_id Yes BIGINT A system-generated unique identifier for each Drug utilization event. drug_exposure
45 person_id Yes BIGINT 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. drug_exposure
46 drug_concept_id Yes INTEGER A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the 'Drug' domain. drug_exposure
47 drug_exposure_start_date No 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. drug_exposure
48 drug_exposure_start_datetime Yes DATETIME The start date and time for the current instance of Drug utilization. Valid entries include a start datetime of a prescription, the date and time a prescription was filled, or the date and time on which a Drug administration procedure was recorded. drug_exposure
49 drug_exposure_end_date No DATE The end date for the current instance of Drug utilization. Depending on different sources, it could be a known or an inferred date and denotes the last day at which the patient was still exposed to Drug. drug_exposure
50 drug_exposure_end_datetime No DATETIME The end date and time for the current instance of Drug utilization. Depending on different sources, it could be a known or an inferred date and time and denotes the last day at which the patient was still exposed to Drug. drug_exposure
51 verbatim_end_date No DATE The known end date of a drug_exposure as provided by the source. drug_exposure
52 drug_type_concept_id Yes INTEGER A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of Drug Exposure recorded. It indicates how the Drug Exposure was represented in the source data and belongs to the 'Drug Type' vocabulary. drug_exposure
53 stop_reason No VARCHAR(20) The reason the Drug was stopped. Reasons include regimen completed, changed, removed, etc. drug_exposure
54 refills No INTEGER The number of refills after the initial prescription. The initial prescription is not counted, values start with null. drug_exposure
55 quantity No FLOAT The quantity of drug as recorded in the original prescription or dispensing record. drug_exposure
56 days_supply No INTEGER The number of days of supply of the medication as prescribed. This reflects the intention of the provider for the length of exposure. drug_exposure
57 sig No VARCHAR(MAX) The directions ('signetur') on the Drug prescription as recorded in the original prescription (and printed on the container) or dispensing record. drug_exposure
58 route_concept_id Yes INTEGER A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies reflecting the route of administration and belonging to the 'Route' domain. drug_exposure
59 lot_number No VARCHAR(50) An identifier assigned to a particular quantity or lot of Drug product from the manufacturer. drug_exposure
60 provider_id No INTEGER A foreign key to the provider in the PROVIDER table who initiated (prescribed or administered) the Drug Exposure. drug_exposure
61 visit_occurrence_id No INTEGER A foreign key to the Visit in the VISIT_OCCURRENCE table during which the Drug Exposure was initiated. drug_exposure
62 visit_detail_id No INTEGER A foreign key to the Visit Detail in the VISIT_DETAIL table during which the Drug Exposure was initiated. drug_exposure
63 drug_source_value No VARCHAR(50) The source code for the Drug as it appears in the source data. This code is mapped to a Standard Drug concept in the Standardized Vocabularies and the original code is, stored here for reference. drug_exposure
64 drug_source_concept_id Yes INTEGER A foreign key to a Drug Concept that refers to the code used in the source. drug_exposure
65 route_source_value No VARCHAR(50) The information about the route of administration as detailed in the source. drug_exposure
66 dose_unit_source_value No VARCHAR(50) The information about the dose unit as detailed in the source. drug_exposure
67 domain_concept_id_1 Yes INTEGER The concept representing the domain of fact one, from which the corresponding table can be inferred. fact_relationship
68 fact_id_1 Yes INTEGER The unique identifier in the table corresponding to the domain of fact one. fact_relationship
69 domain_concept_id_2 Yes INTEGER The concept representing the domain of fact two, from which the corresponding table can be inferred. fact_relationship
70 fact_id_2 Yes INTEGER The unique identifier in the table corresponding to the domain of fact two. fact_relationship
71 relationship_concept_id Yes INTEGER A foreign key to a Standard Concept ID of relationship in the Standardized Vocabularies. fact_relationship
72 measurement_id Yes INTEGER A unique identifier for each Measurement. measurement
73 person_id Yes INTEGER 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. measurement
74 measurement_concept_id Yes INTEGER A foreign key to the standard measurement concept identifier in the Standardized Vocabularies. These belong to the 'Measurement' domain, but could overlap with the 'Observation' domain (see #3 below). measurement
75 measurement_date No DATE The date of the Measurement. measurement
76 measurement_datetime Yes DATETIME The date and time of the Measurement. Some database systems don't have a datatype of time. To accommodate all temporal analyses, datatype datetime can be used (combining measurement_date and measurement_time [forum discussion](http://forums.ohdsi.org/t/date-time-and-datetime-problem-and-the-world-of-hours-and-1day/314)) measurement
77 measurement_time No VARCHAR(10) The time of the Measurement. This is present for backwards compatibility and will be deprecated in an upcoming version measurement
78 measurement_type_concept_id Yes INTEGER A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the provenance from where the Measurement record was recorded. These belong to the 'Meas Type' vocabulary measurement
79 operator_concept_id No INTEGER A foreign key identifier to the predefined Concept in the Standardized Vocabularies reflecting the mathematical operator that is applied to the value_as_number. Operators are <, <=, =, >=, > and these concepts belong to the 'Meas Value Operator' domain. measurement
80 value_as_number No FLOAT A Measurement result where the result is expressed as a numeric value. measurement
81 value_as_concept_id No INTEGER A foreign key to a Measurement result represented as a Concept from the Standardized Vocabularies (e.g., positive/negative, present/absent, low/high, etc.). These belong to the 'Meas Value' domain measurement
82 unit_concept_id No INTEGER A foreign key to a Standard Concept ID of Measurement Units in the Standardized Vocabularies that belong to the 'Unit' domain. measurement
83 range_low No FLOAT The lower limit of the normal range of the Measurement result. The lower range is assumed to be of the same unit of measure as the Measurement value. measurement
84 range_high No FLOAT The upper limit of the normal range of the Measurement. The upper range is assumed to be of the same unit of measure as the Measurement value. measurement
85 provider_id No INTEGER A foreign key to the provider in the PROVIDER table who was responsible for initiating or obtaining the measurement. measurement
86 visit_occurrence_id No INTEGER A foreign key to the Visit in the VISIT_OCCURRENCE table during which the Measurement was recorded. measurement
87 visit_detail_id No INTEGER A foreign key to the Visit Detail in the VISIT_DETAIL table during which the Measurement was recorded. measurement
88 measurement_source_value No VARCHAR(50) 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. measurement
89 measurement_source_concept_id Yes INTEGER A foreign key to a Concept in the Standard Vocabularies that refers to the code used in the source. measurement
90 unit_source_value No VARCHAR(50) 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. measurement
91 value_source_value No VARCHAR(50) The source value associated with the content of the value_as_number or value_as_concept_id as stored in the source data. measurement
92 note_id Yes INTEGER A unique identifier for each note. note
93 person_id Yes INTEGER 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. note
94 note_event_id No INTEGER A foreign key identifier to the event (e.g. Measurement, Procedure, Visit, Drug Exposure, etc) record during which the note was recorded. note
95 note_event_field_concept_id No INTEGER A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the field to which the note_event_id is referring. note
96 note_date No DATE The date the note was recorded. note
97 note_datetime Yes DATETIME The date and time the note was recorded. note
98 note_type_concept_id Yes INTEGER A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the type, origin or provenance of the Note. These belong to the 'Note Type' vocabulary note
99 note_class_concept_id Yes INTEGER A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the HL7 LOINC Document Type Vocabulary classification of the note. note
100 note_title No VARCHAR(250) The title of the Note as it appears in the source. note
101 note_text Yes VARCHAR(MAX) The content of the Note. note
102 encoding_concept_id Yes INTEGER A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the note character encoding type note
103 language_concept_id Yes INTEGER A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the language of the note note
104 provider_id No INTEGER A foreign key to the Provider in the PROVIDER table who took the Note. note
105 visit_occurrence_id No INTEGER A foreign key to the Visit in the VISIT_OCCURRENCE table when the Note was taken. note
106 visit_detail_id No INTEGER A foreign key to the Visit in the VISIT_DETAIL table when the Note was taken. note
107 note_source_value No VARCHAR(50) The source value associated with the origin of the Note note
108 note_nlp_id Yes INTEGER A unique identifier for each term extracted from a note. note_nlp
109 note_id Yes INTEGER A foreign key to the Note table note the term was note_nlp
110 section_concept_id Yes INTEGER A foreign key to the predefined Concept in the Standardized Vocabularies representing the section of the extracted term. note_nlp
111 snippet No VARCHAR(250) A small window of text surrounding the term. note_nlp
112 offset No VARCHAR(50) Character offset of the extracted term in the input note. note_nlp
113 lexical_variant Yes VARCHAR(250) Raw text extracted from the NLP tool. note_nlp
114 note_nlp_concept_id Yes INTEGER A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the normalized concept for the extracted term. Domain of the term is represented as part of the Concept table. note_nlp
115 note_nlp_source_concept_id Yes INTEGER A foreign key to a Concept that refers to the code in the source vocabulary used by the NLP system note_nlp
116 nlp_system No VARCHAR(250) Name and version of the NLP system that extracted the term.Useful for data provenance. note_nlp
117 nlp_date Yes DATE The date of the note processing.Useful for data provenance. note_nlp
118 nlp_datetime No DATETIME The date and time of the note processing. Useful for data provenance. note_nlp
119 term_exists No VARCHAR(1) A summary modifier that signifies presence or absence of the term for a given patient. Useful for quick querying. note_nlp
120 term_temporal No VARCHAR(50) An optional time modifier associated with the extracted term. (for now “past” or “present” only). Standardize it later. note_nlp
121 term_modifiers No VARCHAR(2000) A compact description of all the modifiers of the specific term extracted by the NLP system. (e.g. “son has rash” ? “negated=no,subject=family, certainty=undef,conditional=false,general=false”). note_nlp
122 observation_id Yes INTEGER A unique identifier for each observation. observation
123 person_id Yes INTEGER 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. observation
124 observation_concept_id Yes INTEGER A foreign key to the standard observation concept identifier in the Standardized Vocabularies. observation
125 observation_date No DATE The date of the observation. observation
126 observation_datetime Yes DATETIME The date and time of the observation. observation
127 observation_type_concept_id Yes INTEGER A foreign key to the predefined concept identifier in the Standardized Vocabularies reflecting the type of the observation. observation
128 value_as_number No FLOAT The observation result stored as a number. This is applicable to observations where the result is expressed as a numeric value. observation
129 value_as_string No VARCHAR(60) The observation result stored as a string. This is applicable to observations where the result is expressed as verbatim text. observation
130 value_as_concept_id No INTEGER A foreign key to an observation result stored as a Concept ID. This is applicable to observations where the result can be expressed as a Standard Concept from the Standardized Vocabularies (e.g., positive/negative, present/absent, low/high, etc.). observation
131 qualifier_concept_id No INTEGER A foreign key to a Standard Concept ID for a qualifier (e.g., severity of drug-drug interaction alert) observation
132 unit_concept_id No INTEGER A foreign key to a Standard Concept ID of measurement units in the Standardized Vocabularies. observation
133 provider_id No INTEGER A foreign key to the provider in the PROVIDER table who was responsible for making the observation. observation
134 visit_occurrence_id No INTEGER A foreign key to the visit in the VISIT_OCCURRENCE table during which the observation was recorded. observation
135 visit_detail_id No INTEGER A foreign key to the visit in the VISIT_DETAIL table during which the observation was recorded. observation
136 observation_source_value No VARCHAR(50) The observation code 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. observation
137 observation_source_concept_id Yes INTEGER A foreign key to a Concept that refers to the code used in the source. observation
138 unit_source_value No VARCHAR(50) 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. observation
139 qualifier_source_value No VARCHAR(50) The source value associated with a qualifier to characterize the observation observation
140 observation_event_id No INTEGER A foreign key to an event table (e.g., PROCEDURE_OCCURRENCE_ID). observation
141 obs_event_field_concept_id Yes INTEGER A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies referring to the field represented in the OBSERVATION_EVENT_ID. observation
142 value_as_datetime No INTEGER The observation result stored as a datetime value. This is applicable to observations where the result is expressed as a point in time. observation
143 observation_period_id Yes INTEGER A unique identifier for each observation period. observation_period
144 person_id Yes INTEGER 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. observation_period
145 observation_period_start_date Yes DATE The start date of the observation period for which data are available from the data source. observation_period
146 observation_period_end_date Yes DATE The end date of the observation period for which data are available from the data source. observation_period
147 period_type_concept_id Yes INTEGER A foreign key identifier to the predefined concept in the Standardized Vocabularies reflecting the source of the observation period information, belonging to the 'Obs Period Type' vocabulary observation_period
148 person_id Yes INTEGER A unique identifier for each person. person
149 gender_concept_id Yes INTEGER A foreign key that refers to an identifier in the CONCEPT table for the unique gender of the person. person
150 year_of_birth Yes INTEGER 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. person
151 month_of_birth No INTEGER 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. person
152 day_of_birth No INTEGER 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. person
153 birth_datetime No DATETIME The date and time of birth of the person. person
154 death_datetime No DATETIME The date and time of death of the person. person
155 race_concept_id Yes INTEGER A foreign key that refers to an identifier in the CONCEPT table for the unique race of the person, belonging to the 'Race' vocabulary. person
156 ethnicity_concept_id Yes INTEGER A foreign key that refers to the standard concept identifier in the Standardized Vocabularies for the ethnicity of the person, belonging to the 'Ethnicity' vocabulary. person
157 location_id No INTEGER A foreign key to the place of residency for the person in the location table, where the detailed address information is stored. person
158 provider_id No INTEGER A foreign key to the primary care provider the person is seeing in the provider table. person
159 care_site_id No INTEGER A foreign key to the site of primary care in the care_site table, where the details of the care site are stored. person
160 person_source_value No VARCHAR(50) An (encrypted) key derived from the person identifier in the source data. This is necessary when a use case requires a link back to the person data at the source dataset. person
161 gender_source_value No VARCHAR(50) The source code for the gender of the person as it appears in the source data. The person’s gender is mapped to a standard gender concept in the Standardized Vocabularies; the original value is stored here for reference. person
162 gender_source_concept_id Yes INTEGER A foreign key to the gender concept that refers to the code used in the source. person
163 race_source_value No VARCHAR(50) 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 Standardized Vocabularies and the original value is stored here for reference. person
164 race_source_concept_id Yes INTEGER A foreign key to the race concept that refers to the code used in the source. person
165 ethnicity_source_value No VARCHAR(50) 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 Standardized Vocabularies and the original code is, stored here for reference. person
166 ethnicity_source_concept_id Yes INTEGER A foreign key to the ethnicity concept that refers to the code used in the source. person
167 procedure_occurrence_id Yes INTEGER A system-generated unique identifier for each Procedure Occurrence. procedure_occurrence
168 person_id Yes INTEGER 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. procedure_occurrence
169 procedure_concept_id Yes INTEGER A foreign key that refers to a standard procedure Concept identifier in the Standardized Vocabularies. procedure_occurrence
170 procedure_date No DATE The date on which the Procedure was performed. procedure_occurrence
171 procedure_datetime Yes DATETIME The date and time on which the Procedure was performed. procedure_occurrence
172 procedure_type_concept_id Yes INTEGER A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of source data from which the procedure record is derived, belonging to the 'Procedure Type' vocabulary. procedure_occurrence
173 modifier_concept_id Yes INTEGER A foreign key to a Standard Concept identifier for a modifier to the Procedure (e.g. bilateral). These concepts are typically distinguished by 'Modifier' concept classes (e.g., 'CPT4 Modifier' as part of the 'CPT4' vocabulary). procedure_occurrence
174 quantity No INTEGER The quantity of procedures ordered or administered. procedure_occurrence
175 provider_id No INTEGER A foreign key to the provider in the PROVIDER table who was responsible for carrying out the procedure. procedure_occurrence
176 visit_occurrence_id No INTEGER A foreign key to the Visit in the VISIT_OCCURRENCE table during which the Procedure was carried out. procedure_occurrence
177 visit_detail_id No INTEGER A foreign key to the Visit Detail in the VISIT_DETAIL table during which the Procedure was carried out. procedure_occurrence
178 procedure_source_value No VARCHAR(50) The source code for the Procedure as it appears in the source data. This code is mapped to a standard procedure Concept in the Standardized Vocabularies and the original code is, stored here for reference. Procedure source codes are typically ICD-9-Proc, CPT-4, HCPCS or OPCS-4 codes. procedure_occurrence
179 procedure_source_concept_id Yes INTEGER A foreign key to a Procedure Concept that refers to the code used in the source. procedure_occurrence
180 modifier_source_value No VARCHAR(50) The source code for the qualifier as it appears in the source data. procedure_occurrence
181 specimen_id Yes INTEGER A unique identifier for each specimen. specimen
182 person_id Yes INTEGER A foreign key identifier to the Person for whom the Specimen is recorded. specimen
183 specimen_concept_id Yes INTEGER A foreign key referring to a Standard Concept identifier in the Standardized Vocabularies for the Specimen. specimen
184 specimen_type_concept_id Yes INTEGER A foreign key referring to the Concept identifier in the Standardized Vocabularies reflecting the system of record from which the Specimen was represented in the source data. specimen
185 specimen_date No DATE The date the specimen was obtained from the Person. specimen
186 specimen_datetime Yes DATETIME The date and time on the date when the Specimen was obtained from the person. specimen
187 quantity No FLOAT The amount of specimen collection from the person during the sampling procedure. specimen
188 unit_concept_id No INTEGER A foreign key to a Standard Concept identifier for the Unit associated with the numeric quantity of the Specimen collection. specimen
189 anatomic_site_concept_id Yes INTEGER A foreign key to a Standard Concept identifier for the anatomic location of specimen collection. specimen
190 disease_status_concept_id Yes INTEGER A foreign key to a Standard Concept identifier for the Disease Status of specimen collection. specimen
191 specimen_source_id No VARCHAR(50) The Specimen identifier as it appears in the source data. specimen
192 specimen_source_value No VARCHAR(50) 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. specimen
193 unit_source_value No VARCHAR(50) The information about the Unit as detailed in the source. specimen
194 anatomic_site_source_value No VARCHAR(50) The information about the anatomic site as detailed in the source. specimen
195 disease_status_source_value No VARCHAR(50) The information about the disease status as detailed in the source. specimen
196 survey_conduct_id Yes INTEGER Unique identifier for each completed survey. survey_conduct
197 person_id Yes INTEGER A foreign key identifier to the Person in the PERSON table about whom the survey was completed. survey_conduct
198 survey_concept_id Yes INTEGER A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the name and identity of the survey. survey_conduct
199 survey_start_date No DATE Date on which the survey was started. survey_conduct
200 survey_start_datetime No DATETIME Date and time the survey was started. survey_conduct
201 survey_end_date Yes DATE Date on which the survey was completed. survey_conduct
202 survey_end_datetime No DATETIME Date and time the survey was completed. survey_conduct
203 provider_id No INTEGER A foreign key to the provider in the provider table who was associated with the survey completion. survey_conduct
204 assisted_concept_id Yes INTEGER A foreign key to the predefined Concept identifier in the Standardized Vocabularies indicating whether the survey was completed with assistance. survey_conduct
205 respondent_type_concept_id Yes INTEGER A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the respondent type. Example: Research Associate, Patient. survey_conduct
206 timing_concept_id Yes INTEGER A foreign key to the predefined Concept identifier in the Standardized Vocabularies that refers to a certain timing. Example: 3 month follow-up, 6 month follow-up. survey_conduct
207 collection_method_concept_id Yes INTEGER A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the data collection method (e.g. Paper, Telephone, Electronic Questionnaire). survey_conduct
208 assisted_source_value No VARCHAR(50) Source value representing whether patient required assistance to complete the survey. Example: “Completed without assistance”, ”Completed with assistance”. survey_conduct
209 respondent_type_source_value No VARCHAR(100) Source code representing role of person who completed the survey. survey_conduct
210 timing_source_value No VARCHAR(100) Text string representing the timing of the survey. Example: Baseline, 6-month follow-up. survey_conduct
211 collection_method_source_value No VARCHAR(100) The collection method as it appears in the source data. survey_conduct
212 survey_source_value No VARCHAR(100) The survey name/title as it appears in the source data. survey_conduct
213 survey_source_concept_id Yes INTEGER A foreign key to a predefined Concept that refers to the code for the survey name/title used in the source. survey_conduct
214 survey_source_identifier No VARCHAR(100) Unique identifier for each completed survey in source system. survey_conduct
215 validated_survey_concept_id Yes INTEGER A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the validation status of the survey. survey_conduct
216 validated_survey_source_value No INTEGER Source value representing the validation status of the survey. survey_conduct
217 survey_version_number No VARCHAR(20) Version number of the questionnaire or survey used. survey_conduct
218 visit_occurrence_id No INTEGER A foreign key to the VISIT_OCCURRENCE table during which the survey was completed survey_conduct
219 response_visit_occurrence_id No INTEGER A foreign key to the visit in the VISIT_OCCURRENCE table during which treatment was carried out that relates to this survey. survey_conduct
220 visit_detail_id Yes INTEGER A unique identifier for each Person's visit or encounter at a healthcare provider. visit_detail
221 person_id Yes INTEGER 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. visit_detail
222 visit_detail_concept_id Yes INTEGER A foreign key that refers to a visit Concept identifier in the Standardized Vocabularies belonging to the 'Visit' Vocabulary. visit_detail
223 visit_detail_start_date No DATE The start date of the visit. visit_detail
224 visit_detail_start_datetime Yes DATETIME The date and time of the visit started. visit_detail
225 visit_detail_end_date No DATE The end date of the visit. If this is a one-day visit the end date should match the start date. visit_detail
226 visit_detail_end_datetime Yes DATETIME The date and time of the visit end. visit_detail
227 visit_detail_type_concept_id Yes INTEGER 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 belonging to the 'Visit Type' vocabulary. visit_detail
228 provider_id No INTEGER A foreign key to the provider in the provider table who was associated with the visit. visit_detail
229 care_site_id No INTEGER A foreign key to the care site in the care site table that was visited. visit_detail
230 visit_detail_source_value No STRING(50) The source code for the visit as it appears in the source data. visit_detail
231 visit_detail_source_concept_id Yes INTEGER A foreign key to a Concept that refers to the code used in the source. visit_detail
232 admitted_from_source_value No VARCHAR(50) The source code for the admitting source as it appears in the source data. visit_detail
233 admitted_from_concept_id Yes INTEGER A foreign key to the predefined concept in the 'Place of Service' Vocabulary reflecting the admitting source for a visit. visit_detail
234 discharge_to_source_value No VARCHAR(50) The source code for the discharge disposition as it appears in the source data. visit_detail
235 discharge_to_concept_id Yes INTEGER A foreign key to the predefined concept in the 'Place of Service' Vocabulary reflecting the discharge disposition for a visit. visit_detail
236 preceding_visit_detail_id No INTEGER A foreign key to the VISIT_DETAIL table of the visit immediately preceding this visit visit_detail
237 visit_detail_parent_id No INTEGER A foreign key to the VISIT_DETAIL table record to represent the immediate parent visit-detail record. visit_detail
238 visit_occurrence_id Yes INTEGER A foreign key that refers to the record in the VISIT_OCCURRENCE table. This is a required field, because for every visit_detail is a child of visit_occurrence and cannot exist without a corresponding parent record in visit_occurrence. visit_detail
239 visit_occurrence_id Yes INTEGER A unique identifier for each Person's visit or encounter at a healthcare provider. visit_occurrence
240 person_id Yes INTEGER 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. visit_occurrence
241 visit_concept_id Yes INTEGER A foreign key that refers to a visit Concept identifier in the Standardized Vocabularies belonging to the 'Visit' Vocabulary. visit_occurrence
242 visit_start_date No DATE The start date of the visit. visit_occurrence
243 visit_start_datetime Yes DATETIME The date and time of the visit started. visit_occurrence
244 visit_end_date No DATE The end date of the visit. If this is a one-day visit the end date should match the start date. visit_occurrence
245 visit_end_datetime Yes DATETIME The date and time of the visit end. visit_occurrence
246 visit_type_concept_id Yes INTEGER 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 belonging to the 'Visit Type' vocabulary. visit_occurrence
247 provider_id No INTEGER A foreign key to the provider in the provider table who was associated with the visit. visit_occurrence
248 care_site_id No INTEGER A foreign key to the care site in the care site table that was visited. visit_occurrence
249 visit_source_value No VARCHAR(50) The source code for the visit as it appears in the source data. visit_occurrence
250 visit_source_concept_id Yes INTEGER A foreign key to a Concept that refers to the code used in the source. visit_occurrence
251 admitting_source_concept_id Yes INTEGER A foreign key to the predefined concept in the Place of Service Vocabulary reflecting the admitting source for a visit. visit_occurrence
252 admitting_source_value No VARCHAR(50) The source code for the admitting source as it appears in the source data. visit_occurrence
253 discharge_to_concept_id Yes INTEGER A foreign key to the predefined concept in the Place of Service Vocabulary reflecting the discharge disposition for a visit. visit_occurrence
254 discharge_to_source_value No VARCHAR(50) The source code for the discharge disposition as it appears in the source data. visit_occurrence
255 preceding_visit_occurrence_id No INTEGER A foreign key to the VISIT_OCCURRENCE table of the visit immediately preceding this visit visit_occurrence
256 condition_era_id Yes INTEGER A unique identifier for each Condition Era. condition_era
257 person_id Yes INTEGER 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. condition_era
258 condition_concept_id Yes INTEGER A foreign key that refers to a standard Condition Concept identifier in the Standardized Vocabularies. condition_era
259 condition_era_start_datetime Yes 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. condition_era
260 condition_era_end_datetime Yes 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. condition_era
261 condition_occurrence_count No INTEGER The number of individual Condition Occurrences used to construct the condition era. condition_era
262 dose_era_id Yes INTEGER A unique identifier for each Dose Era. dose_era
263 person_id Yes INTEGER 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. dose_era
264 drug_concept_id Yes INTEGER A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the active Ingredient Concept. dose_era
265 unit_concept_id Yes INTEGER A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the unit concept. dose_era
266 dose_value Yes FLOAT The numeric value of the dose. dose_era
267 dose_era_start_datetime Yes 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. dose_era
268 dose_era_end_datetime Yes 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. dose_era
269 drug_era_id Yes INTEGER A unique identifier for each Drug Era. drug_era
270 person_id Yes INTEGER A foreign key identifier to the Person who is subjected to the Drug during the fDrug Era. The demographic details of that Person are stored in the PERSON table. drug_era
271 drug_concept_id Yes INTEGER A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the Ingredient Concept. drug_era
272 drug_era_start_datetime Yes 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 conutilization of a Drug. drug_era
273 drug_era_end_datetime Yes 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. drug_era
274 drug_exposure_count No INTEGER The number of individual Drug Exposure occurrences used to construct the Drug Era. drug_era
275 gap_days No INTEGER The number of days that are not covered by DRUG_EXPOSURE records that were used to make up the era record. drug_era
276 cost_id Yes INTEGER A unique identifier for each COST record. cost
277 person_id Yes INTEGER A unique identifier for each PERSON. cost
278 cost_event_id Yes INTEGER A foreign key identifier to the event (e.g. Measurement, Procedure, Visit, Drug Exposure, etc) record for which cost data are recorded. cost
279 cost_event_field_concept_id Yes INTEGER A foreign key identifier to a concept in the CONCEPT table representing the identity of the field represented by COST_EVENT_ID cost
280 cost_concept_id Yes INTEGER A foreign key that refers to a Standard Cost Concept identifier in the Standardized Vocabularies belonging to the 'Cost' vocabulary. cost
281 cost_type_concept_id Yes INTEGER A foreign key identifier to a concept in the CONCEPT table for the provenance or the source of the COST data and belonging to the 'Cost Type' vocabulary cost
282 cost_source_concept_id Yes INTEGER A foreign key to a Cost Concept that refers to the code used in the source. cost
283 cost_source_value No VARCHAR(50) The source value for the cost as it appears in the source data cost
284 currency_concept_id Yes INTEGER A foreign key identifier to the concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar. These belong to the 'Currency' vocabulary cost
285 cost Yes FLOAT The actual financial cost amount cost
286 incurred_date Yes DATE The first date of service of the clinical event corresponding to the cost as in table capturing the information (e.g. date of visit, date of procedure, date of condition, date of drug etc). cost
287 billed_date No DATE The date a bill was generated for a service or encounter cost
288 paid_date No DATE The date payment was received for a service or encounter cost
289 revenue_code_concept_id Yes INTEGER A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for Revenue codes belonging to the 'Revenue Code' vocabulary. cost
290 drg_concept_id Yes INTEGER A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for DRG codes belonging to the 'DRG' vocabulary. cost
291 revenue_code_source_value No VARCHAR(50) The source value for the Revenue code as it appears in the source data, stored here for reference. cost
292 drg_source_value No VARCHAR(50) The source value for the 3-digit DRG source code as it appears in the source data, stored here for reference. cost
293 payer_plan_period_id No INTEGER A foreign key to the PAYER_PLAN_PERIOD table, where the details of the Payer, Plan and Family are stored. Record the payer_plan_id that relates to the payer who contributed to the paid_by_payer field. cost
294 payer_plan_period_id Yes INTEGER A identifier for each unique combination of payer, plan, family code and time span. payer_plan_period
295 person_id Yes INTEGER A foreign key identifier to the Person covered by the payer. The demographic details of that Person are stored in the PERSON table. payer_plan_period
296 contract_person_id No INTEGER A foreign key identifier to the person_id in person table, for the person who is the primary subscriber/contract owner for the record in the payer_plan_period table. Maybe the same person or different person, depending on who is the primary subscriber/contract owner. payer_plan_period
297 payer_plan_period_start_date Yes DATE The start date of the payer plan period. payer_plan_period
298 payer_plan_period_end_date Yes DATE The end date of the payer plan period. payer_plan_period
299 payer_concept_id Yes INTEGER A foreign key that refers to a standard Payer concept identifier in the Standarized Vocabularies payer_plan_period
300 payer_source_value No VARCHAR(50) The source code for the payer as it appears in the source data. payer_plan_period
301 payer_source_concept_id Yes INTEGER A foreign key to a payer concept that refers to the code used in the source. payer_plan_period
302 plan_concept_id Yes INTEGER A foreign key that refers to a standard plan concept identifier that represents the health benefit plan in the Standardized Vocabularies. payer_plan_period
303 plan_source_value No VARCHAR(50) The source code for the Person's health benefit plan as it appears in the source data. payer_plan_period
304 plan_source_concept_id Yes INTEGER A foreign key to a plan concept that refers to the plan code used in the source data. payer_plan_period
305 contract_concept_id Yes INTEGER A foreign key to a standard concept representing the reason justifying the contract between person_id and contract_person_id. payer_plan_period
306 contract_source_value No INTEGER The source code representing the reason justifying the contract. Usually it is family relationship like a spouse, domestic partner, child etc. payer_plan_period
307 contract_source_concept_id Yes INTEGER A foreign key to a concept that refers to the code used in the source as the reason justifying the contract. payer_plan_period
308 sponsor_concept_id Yes INTEGER A foreign key that refers to a concept identifier that represents the sponsor in the Standardized Vocabularies. payer_plan_period
309 sponsor_source_value No VARCHAR(50) The source code for the Person's sponsor of the health plan as it appears in the source data. payer_plan_period
310 sponsor_source_concept_id Yes INTEGER A foreign key to a sponsor concept that refers to the sponsor code used in the source data. payer_plan_period
311 family_source_value No VARCHAR(50) The source code for the Person's family as it appears in the source data. payer_plan_period
312 stop_reason_concept_id Yes INTEGER A foreign key that refers to a standard termination reason that represents the reason for the termination in the Standardized Vocabularies. payer_plan_period
313 stop_reason_source_value No VARCHAR(50) The reason for stop-coverage as it appears in the source data. payer_plan_period
314 stop_reason_source_concept_id Yes INTEGER A foreign key to a stop-coverage concept that refers to the code used in the source. payer_plan_period
315 care_site_id Yes INTEGER A unique identifier for each Care Site. care_site
316 care_site_name No VARCHAR(255) The verbatim description or name of the Care Site as in data source care_site
317 place_of_service_concept_id Yes INTEGER A foreign key that refers to a Place of Service Concept ID in the Standardized Vocabularies. care_site
318 location_id No INTEGER A foreign key to the geographic Location in the LOCATION table, where the detailed address information is stored. care_site
319 care_site_source_value No VARCHAR(50) The identifier for the Care Site in the source data, stored here for reference. care_site
320 place_of_service_source_value No VARCHAR(50) The source code for the Place of Service as it appears in the source data, stored here for reference. care_site
321 location_id Yes INTEGER A unique identifier for each geographic location. location
322 address_1 No VARCHAR(50) The address field 1, typically used for the street address, as it appears in the source data. location
323 address_2 No VARCHAR(50) The address field 2, typically used for additional detail such as buildings, suites, floors, as it appears in the source data. location
324 city No VARCHAR(50) The city field as it appears in the source data. location
325 state No VARCHAR(2) The state field as it appears in the source data. location
326 zip No VARCHAR(9) The zip or postal code. location
327 county No VARCHAR(20) The county. location
328 country No VARCHAR(100) The country location
329 location_source_value No VARCHAR(50) The verbatim information that is used to uniquely identify the location as it appears in the source data. location
330 latitude No FLOAT The geocoded latitude location
331 longitude No FLOAT The geocoded longitude location
332 location_id Yes INTEGER A foreign key to the location table. location_history
333 relationship_type_concept_id Yes VARCHAR(50) The type of relationship between location and entity. location_history
334 domain_id Yes VARCHAR(50) The domain of the entity that is related to the location. Either PERSON, PROVIDER, or CARE_SITE. location_history
335 entity_id Yes INTEGER The unique identifier for the entity. References either person_id, provider_id, or care_site_id, depending on domain_id. location_history
336 start_date Yes DATE The date the relationship started. location_history
337 end_date No DATE The date the relationship ended. location_history
338 provider_id Yes INTEGER A unique identifier for each Provider. provider
339 provider_name No VARCHAR(255) A description of the Provider. provider
340 npi No VARCHAR(20) The National Provider Identifier (NPI) of the provider. provider
341 dea No VARCHAR(20) The Drug Enforcement Administration (DEA) number of the provider. provider
342 specialty_concept_id Yes INTEGER A foreign key to a Standard Specialty Concept ID in the Standardized Vocabularies. provider
343 care_site_id No INTEGER A foreign key to the main Care Site where the provider is practicing. provider
344 year_of_birth No INTEGER The year of birth of the Provider. provider
345 gender_concept_id Yes INTEGER The gender of the Provider. provider
346 provider_source_value No VARCHAR(50) The identifier used for the Provider in the source data, stored here for reference. provider
347 specialty_source_value No VARCHAR(50) The source code for the Provider specialty as it appears in the source data, stored here for reference. provider
348 specialty_source_concept_id Yes INTEGER A foreign key to a Concept that refers to the code used in the source. provider
349 gender_source_value No VARCHAR(50) The gender code for the Provider as it appears in the source data, stored here for reference. provider
350 gender_source_concept_id Yes INTEGER A foreign key to a Concept that refers to the code used in the source. provider
351 cdm_source_name Yes VARCHAR(255) The full name of the source cdm_source
352 cdm_source_abbreviation No VARCHAR(25) An abbreviation of the name cdm_source
353 cdm_holder No VARCHAR(255) The name of the organization responsible for the development of the CDM instance cdm_source
354 source_description No CLOB 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. cdm_source
355 source_documentation_reference No VARCHAR(255) URL or other external reference to location of source documentation cdm_source
356 cdm_etl_reference No VARCHAR(255) URL or other external reference to location of ETL specification documentation and ETL source code cdm_source
357 source_release_date No DATE The date for which the source data are most current, such as the last day of data capture cdm_source
358 cdm_release_date No DATE The date when the CDM was instantiated cdm_source
359 cdm_version No VARCHAR(10) The version of CDM used cdm_source
360 vocabulary_version No VARCHAR(20) The version of the vocabulary used cdm_source
361 metadata_concept_id Yes INTEGER A foreign key that refers to a Standard Metadata Concept identifier in the Standardized Vocabularies. metadata
362 metadata_type_concept_id Yes INTEGER A foreign key that refers to a Standard Type Concept identifier in the Standardized Vocabularies. metadata
363 name Yes VARCHAR(250) The name of the Concept stored in metadata_concept_id or a description of the data being stored. metadata
364 value_as_string No NVARCHAR The metadata value stored as a string. metadata
365 value_as_concept_id No INTEGER A foreign key to a metadata value stored as a Concept ID. metadata
366 metadata date No DATE The date associated with the metadata metadata
367 metadata_datetime No DATETIME The date and time associated with the metadata metadata
368 concept_id Yes INTEGER A unique identifier for each Concept across all domains. concept
369 concept_name Yes VARCHAR(255) An unambiguous, meaningful and descriptive name for the Concept. concept
370 domain_id Yes VARCHAR(20) A foreign key to the [DOMAIN](https://github.com/OHDSI/CommonDataModel/wiki/DOMAIN) table the Concept belongs to. concept
371 vocabulary_id Yes VARCHAR(20) A foreign key to the [VOCABULARY](https://github.com/OHDSI/CommonDataModel/wiki/VOCABULARY) table indicating from which source the Concept has been adapted. concept
372 concept_class_id Yes VARCHAR(20) The attribute or concept class of the Concept. Examples are 'Clinical Drug', 'Ingredient', 'Clinical Finding' etc. concept
373 standard_concept No VARCHAR(1) This flag determines where a Concept is a Standard Concept, i.e. is used in the data, a Classification Concept, or a non-standard Source Concept. The allowables values are 'S' (Standard Concept) and 'C' (Classification Concept), otherwise the content is NULL. concept
374 concept_code Yes VARCHAR(50) The concept code represents the identifier of the Concept in the source vocabulary, such as SNOMED-CT concept IDs, RxNorm RXCUIs etc. Note that concept codes are not unique across vocabularies. concept
375 valid_start_date Yes DATE The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception. concept
376 valid_end_date Yes 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, meaning, the Concept is valid until it becomes deprecated. concept
377 invalid_reason No VARCHAR(1) 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. concept
378 ancestor_concept_id Yes INTEGER A foreign key to the concept in the concept table for the higher-level concept that forms the ancestor in the relationship. concept_ancestor
379 descendant_concept_id Yes INTEGER A foreign key to the concept in the concept table for the lower-level concept that forms the descendant in the relationship. concept_ancestor
380 min_levels_of_separation Yes INTEGER The minimum separation in number of levels of hierarchy between ancestor and descendant concepts. This is an attribute that is used to simplify hierarchic analysis. concept_ancestor
381 max_levels_of_separation Yes INTEGER The maximum separation in number of levels of hierarchy between ancestor and descendant concepts. This is an attribute that is used to simplify hierarchic analysis. concept_ancestor
382 concept_class_id Yes VARCHAR(20) A unique key for each class. concept_class
383 concept_class_name Yes VARCHAR(255) The name describing the Concept Class, e.g. "Clinical Finding", "Ingredient", etc. concept_class
384 concept_class_concept_id Yes INTEGER A foreign key that refers to an identifier in the [CONCEPT](https://github.com/OHDSI/CommonDataModel/wiki/CONCEPT) table for the unique Concept Class the record belongs to. concept_class
385 concept_id_1 Yes INTEGER A foreign key to a Concept in the [CONCEPT](https://github.com/OHDSI/CommonDataModel/wiki/CONCEPT) table associated with the relationship. Relationships are directional, and this field represents the source concept designation. concept_relationship
386 concept_id_2 Yes INTEGER A foreign key to a Concept in the [CONCEPT](https://github.com/OHDSI/CommonDataModel/wiki/CONCEPT) table associated with the relationship. Relationships are directional, and this field represents the destination concept designation. concept_relationship
387 relationship_id Yes VARCHAR(20) A unique identifier to the type or nature of the Relationship as defined in the [RELATIONSHIP](https://github.com/OHDSI/CommonDataModel/wiki/RELATIONSHIP) table. concept_relationship
388 valid_start_date Yes DATE The date when the instance of the Concept Relationship is first recorded. concept_relationship
389 valid_end_date Yes DATE The date when the Concept Relationship became invalid because it was deleted or superseded (updated) by a new relationship. Default value is 31-Dec-2099. concept_relationship
390 invalid_reason No VARCHAR(1) 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. concept_relationship
391 concept_id Yes INTEGER A foreign key to the Concept in the CONCEPT table. concept_synonym
392 concept_synonym_name Yes VARCHAR(1000) The alternative name for the Concept. concept_synonym
393 language_concept_id Yes INTEGER A foreign key to a Concept representing the language. concept_synonym
394 domain_id Yes VARCHAR(20) A unique key for each domain. domain
395 domain_name Yes VARCHAR(255) The name describing the Domain, e.g. "Condition", "Procedure", "Measurement" etc. domain
396 domain_concept_id Yes INTEGER A foreign key that refers to an identifier in the [CONCEPT](https://github.com/OHDSI/CommonDataModel/wiki/CONCEPT) table for the unique Domain Concept the Domain record belongs to. domain
397 drug_concept_id Yes INTEGER A foreign key to the Concept in the CONCEPT table representing the identifier for Branded Drug or Clinical Drug Concept. drug_strength
398 ingredient_concept_id Yes INTEGER A foreign key to the Concept in the CONCEPT table, representing the identifier for drug Ingredient Concept contained within the drug product. drug_strength
399 amount_value No FLOAT The numeric value associated with the amount of active ingredient contained within the product. drug_strength
400 amount_unit_concept_id No INTEGER A foreign key to the Concept in the CONCEPT table representing the identifier for the Unit for the absolute amount of active ingredient. drug_strength
401 numerator_value No FLOAT The numeric value associated with the concentration of the active ingredient contained in the product drug_strength
402 numerator_unit_concept_id No INTEGER A foreign key to the Concept in the CONCEPT table representing the identifier for the numerator Unit for the concentration of active ingredient. drug_strength
403 denominator_value No FLOAT The amount of total liquid (or other divisible product, such as ointment, gel, spray, etc.). drug_strength
404 denominator_unit_concept_id No INTEGER A foreign key to the Concept in the CONCEPT table representing the identifier for the denominator Unit for the concentration of active ingredient. drug_strength
405 box_size No INTEGER The number of units of Clinical of Branded Drug, or Quantified Clinical or Branded Drug contained in a box as dispensed to the patient drug_strength
406 valid_start_date Yes DATE The date when the Concept was first recorded. The default value is 1-Jan-1970. drug_strength
407 valid_end_date Yes 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. drug_strength
408 invalid_reason No VARCHAR(1) 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. drug_strength
409 relationship_id Yes VARCHAR(20) The type of relationship captured by the relationship record. relationship
410 relationship_name Yes VARCHAR(255) The text that describes the relationship type. relationship
411 is_hierarchical Yes VARCHAR(1) Defines whether a relationship defines concepts into classes or hierarchies. Values are 1 for hierarchical relationship or 0 if not. relationship
412 defines_ancestry Yes VARCHAR(1) Defines whether a hierarchical relationship contributes to the concept_ancestor table. These are subsets of the hierarchical relationships. Valid values are 1 or 0. relationship
413 reverse_relationship_id Yes VARCHAR(20) The identifier for the relationship used to define the reverse relationship between two concepts. relationship
414 relationship_concept_id Yes INTEGER A foreign key that refers to an identifier in the CONCEPT table for the unique relationship concept. relationship
415 source_code Yes VARCHAR(50) The source code being translated into a Standard Concept. source_to_concept_map
416 source_concept_id Yes INTEGER A foreign key to the Source Concept that is being translated into a Standard Concept. source_to_concept_map
417 source_vocabulary_id Yes VARCHAR(20) A foreign key to the VOCABULARY table defining the vocabulary of the source code that is being translated to a Standard Concept. source_to_concept_map
418 source_code_description No VARCHAR(255) 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. source_to_concept_map
419 target_concept_id Yes INTEGER A foreign key to the target Concept to which the source code is being mapped. source_to_concept_map
420 target_vocabulary_id Yes VARCHAR(20) A foreign key to the VOCABULARY table defining the vocabulary of the target Concept. source_to_concept_map
421 valid_start_date Yes DATE The date when the mapping instance was first recorded. source_to_concept_map
422 valid_end_date Yes 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. source_to_concept_map
423 invalid_reason No VARCHAR(1) 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. source_to_concept_map
424 vocabulary_id Yes VARCHAR(20) A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit. vocabulary
425 vocabulary_name Yes VARCHAR(255) The name describing the vocabulary, for example "International Classification of Diseases, Ninth Revision, Clinical Modification, Volume 1 and 2 (NCHS)" etc. vocabulary
426 vocabulary_reference Yes VARCHAR(255) External reference to documentation or available download of the about the vocabulary. vocabulary
427 vocabulary_version No VARCHAR(255) Version of the Vocabulary as indicated in the source. vocabulary
428 vocabulary_concept_id Yes INTEGER A foreign key that refers to a standard concept identifier in the CONCEPT table for the Vocabulary the VOCABULARY record belongs to. vocabulary

BIN
OMOP_CDM_v6_0.pdf Normal file

Binary file not shown.