OMOP/OMOP_CDM_v6_0.csv

66 KiB
Raw Blame History

1fieldrequiredtypedescriptiontable
2cohort_definition_idYesINTEGERA foreign key to a record in the COHORT_DEFINITION table containing relevant Cohort Definition information.cohort
3subject_idYesINTEGERA foreign key to the subject in the cohort. These could be referring to records in the PERSON, PROVIDER, VISIT_OCCURRENCE table.cohort
4cohort_start_dateYesDATEThe date when the Cohort Definition criteria for the Person, Provider or Visit first match.cohort
5cohort_end_dateYesDATEThe date when the Cohort Definition criteria for the Person, Provider or Visit no longer match or the Cohort membership was terminated.cohort
6cohort_definition_idYesINTEGERA unique identifier for each Cohort.cohort_definition
7cohort_definition_nameYesVARCHAR(255)A short description of the Cohort.cohort_definition
8cohort_definition_descriptionNoVARCHAR(MAX)A complete description of the Cohort definitioncohort_definition
9definition_type_concept_idYesINTEGERType defining what kind of Cohort Definition the record represents and how the syntax may be executedcohort_definition
10cohort_definition_syntaxNoVARCHAR(MAX)Syntax or code to operationalize the Cohort definitioncohort_definition
11subject_concept_idYesINTEGERA 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
12cohort_initiation_dateNoDATEA date to indicate when the Cohort was initiated in the COHORT tablecohort_definition
13condition_occurrence_idYesBIGINTA unique identifier for each Condition Occurrence event.condition_occurrence
14person_idYesBIGINTA 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
15condition_concept_idYesINTEGERA foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the 'Condition' domain.condition_occurrence
16condition_start_dateNoDATEThe date when the instance of the Condition is recorded.condition_occurrence
17condition_start_datetimeYesDATETIMEThe date and time when the instance of the Condition is recorded.condition_occurrence
18condition_end_dateNoDATEThe date when the instance of the Condition is considered to have ended.condition_occurrence
19condition_end_datetimeNoDATETIMEThe date when the instance of the Condition is considered to have ended.condition_occurrence
20condition_type_concept_idYesINTEGERA 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' vocabularycondition_occurrence
21condition_status_concept_idYesINTEGERA 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
22stop_reasonNoVARCHAR(20)The reason that the Condition was no longer present, as indicated in the source data.condition_occurrence
23provider_idNoINTEGERA foreign key to the Provider in the PROVIDER table who was responsible for capturing (diagnosing) the Condition.condition_occurrence
24visit_occurrence_idNoINTEGERA foreign key to the visit in the VISIT_OCCURRENCE table during which the Condition was determined (diagnosed).condition_occurrence
25visit_detail_idNoINTEGERA foreign key to the visit in the VISIT_DETAIL table during which the Condition was determined (diagnosed).condition_occurrence
26condition_source_valueNoVARCHAR(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
27condition_source_concept_idYesINTEGERA foreign key to a Condition Concept that refers to the code used in the source.condition_occurrence
28condition_status_source_valueNoVARCHAR(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
29device_exposure_idYesBIGINTA system-generated unique identifier for each Device Exposure.device_exposure
30person_idYesBIGINTA 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
31device_concept_idYesINTEGERA foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the 'Device' domain.device_exposure
32device_exposure_start_dateNoDATEThe date the Device or supply was applied or used.device_exposure
33device_exposure_start_datetimeYesDATETIMEThe date and time the Device or supply was applied or used.device_exposure
34device_exposure_end_dateNoDATEThe date use of the Device or supply was ceased.device_exposure
35device_exposure_end_datetimeNoDATETIMEThe date and time use of the Device or supply was ceased.device_exposure
36device_type_concept_idYesINTEGERA 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
37unique_device_idNoVARCHAR(50)A UDI or equivalent identifying the instance of the Device used in the Person.device_exposure
38quantityNoINTEGERThe number of individual Devices used in the exposure.device_exposure
39provider_idNoINTEGERA foreign key to the provider in the PROVIDER table who initiated or administered the Device.device_exposure
40visit_occurrence_idNoINTEGERA foreign key to the visit in the VISIT_OCCURRENCE table during which the Device was used.device_exposure
41visit_detail_idNoINTEGERA foreign key to the visit detail record in the VISIT_DETAIL table during which the Device was used.device_exposure
42device_source_valueNoVARCHAR(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
43device_source_concept_idYesINTEGERA foreign key to a Device Concept that refers to the code used in the source.device_exposure
44drug_exposure_idYesBIGINTA system-generated unique identifier for each Drug utilization event.drug_exposure
45person_idYesBIGINTA 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
46drug_concept_idYesINTEGERA foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the 'Drug' domain.drug_exposure
47drug_exposure_start_dateNoDATEThe 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
48drug_exposure_start_datetimeYesDATETIMEThe 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
49drug_exposure_end_dateNoDATEThe 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
50drug_exposure_end_datetimeNoDATETIMEThe 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
51verbatim_end_dateNoDATEThe known end date of a drug_exposure as provided by the source.drug_exposure
52drug_type_concept_idYesINTEGERA 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
53stop_reasonNoVARCHAR(20)The reason the Drug was stopped. Reasons include regimen completed, changed, removed, etc.drug_exposure
54refillsNoINTEGERThe number of refills after the initial prescription. The initial prescription is not counted, values start with null.drug_exposure
55quantityNoFLOATThe quantity of drug as recorded in the original prescription or dispensing record.drug_exposure
56days_supplyNoINTEGERThe number of days of supply of the medication as prescribed. This reflects the intention of the provider for the length of exposure.drug_exposure
57sigNoVARCHAR(MAX)The directions ('signetur') on the Drug prescription as recorded in the original prescription (and printed on the container) or dispensing record.drug_exposure
58route_concept_idYesINTEGERA 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
59lot_numberNoVARCHAR(50)An identifier assigned to a particular quantity or lot of Drug product from the manufacturer.drug_exposure
60provider_idNoINTEGERA foreign key to the provider in the PROVIDER table who initiated (prescribed or administered) the Drug Exposure.drug_exposure
61visit_occurrence_idNoINTEGERA foreign key to the Visit in the VISIT_OCCURRENCE table during which the Drug Exposure was initiated.drug_exposure
62visit_detail_idNoINTEGERA foreign key to the Visit Detail in the VISIT_DETAIL table during which the Drug Exposure was initiated.drug_exposure
63drug_source_valueNoVARCHAR(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
64drug_source_concept_idYesINTEGERA foreign key to a Drug Concept that refers to the code used in the source.drug_exposure
65route_source_valueNoVARCHAR(50)The information about the route of administration as detailed in the source.drug_exposure
66dose_unit_source_valueNoVARCHAR(50)The information about the dose unit as detailed in the source.drug_exposure
67domain_concept_id_1YesINTEGERThe concept representing the domain of fact one, from which the corresponding table can be inferred.fact_relationship
68fact_id_1YesINTEGERThe unique identifier in the table corresponding to the domain of fact one.fact_relationship
69domain_concept_id_2YesINTEGERThe concept representing the domain of fact two, from which the corresponding table can be inferred.fact_relationship
70fact_id_2YesINTEGERThe unique identifier in the table corresponding to the domain of fact two.fact_relationship
71relationship_concept_idYesINTEGERA foreign key to a Standard Concept ID of relationship in the Standardized Vocabularies.fact_relationship
72measurement_idYesINTEGERA unique identifier for each Measurement.measurement
73person_idYesINTEGERA 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
74measurement_concept_idYesINTEGERA 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
75measurement_dateNoDATEThe date of the Measurement.measurement
76measurement_datetimeYesDATETIMEThe 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
77measurement_timeNoVARCHAR(10)The time of the Measurement. This is present for backwards compatibility and will be deprecated in an upcoming versionmeasurement
78measurement_type_concept_idYesINTEGERA 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' vocabularymeasurement
79operator_concept_idNoINTEGERA 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
80value_as_numberNoFLOATA Measurement result where the result is expressed as a numeric value.measurement
81value_as_concept_idNoINTEGERA 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' domainmeasurement
82unit_concept_idNoINTEGERA foreign key to a Standard Concept ID of Measurement Units in the Standardized Vocabularies that belong to the 'Unit' domain.measurement
83range_lowNoFLOATThe 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
84range_highNoFLOATThe 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
85provider_idNoINTEGERA foreign key to the provider in the PROVIDER table who was responsible for initiating or obtaining the measurement.measurement
86visit_occurrence_idNoINTEGERA foreign key to the Visit in the VISIT_OCCURRENCE table during which the Measurement was recorded.measurement
87visit_detail_idNoINTEGERA foreign key to the Visit Detail in the VISIT_DETAIL table during which the Measurement was recorded.measurement
88measurement_source_valueNoVARCHAR(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
89measurement_source_concept_idYesINTEGERA foreign key to a Concept in the Standard Vocabularies that refers to the code used in the source.measurement
90unit_source_valueNoVARCHAR(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
91value_source_valueNoVARCHAR(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
92note_idYesINTEGERA unique identifier for each note.note
93person_idYesINTEGERA 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
94note_event_idNoINTEGERA foreign key identifier to the event (e.g. Measurement, Procedure, Visit, Drug Exposure, etc) record during which the note was recorded.note
95note_event_field_concept_idNoINTEGERA foreign key to the predefined Concept in the Standardized Vocabularies reflecting the field to which the note_event_id is referring.note
96note_dateNoDATEThe date the note was recorded.note
97note_datetimeYesDATETIMEThe date and time the note was recorded.note
98note_type_concept_idYesINTEGERA 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' vocabularynote
99note_class_concept_idYesINTEGERA foreign key to the predefined Concept in the Standardized Vocabularies reflecting the HL7 LOINC Document Type Vocabulary classification of the note.note
100note_titleNoVARCHAR(250)The title of the Note as it appears in the source.note
101note_textYesVARCHAR(MAX)The content of the Note.note
102encoding_concept_idYesINTEGERA foreign key to the predefined Concept in the Standardized Vocabularies reflecting the note character encoding typenote
103language_concept_idYesINTEGERA foreign key to the predefined Concept in the Standardized Vocabularies reflecting the language of the notenote
104provider_idNoINTEGERA foreign key to the Provider in the PROVIDER table who took the Note.note
105visit_occurrence_idNoINTEGERA foreign key to the Visit in the VISIT_OCCURRENCE table when the Note was taken.note
106visit_detail_idNoINTEGERA foreign key to the Visit in the VISIT_DETAIL table when the Note was taken.note
107note_source_valueNoVARCHAR(50)The source value associated with the origin of the Notenote
108note_nlp_idYesINTEGERA unique identifier for each term extracted from a note.note_nlp
109note_idYesINTEGERA foreign key to the Note table note the term wasnote_nlp
110section_concept_idYesINTEGERA foreign key to the predefined Concept in the Standardized Vocabularies representing the section of the extracted term.note_nlp
111snippetNoVARCHAR(250)A small window of text surrounding the term.note_nlp
112offsetNoVARCHAR(50)Character offset of the extracted term in the input note.note_nlp
113lexical_variantYesVARCHAR(250)Raw text extracted from the NLP tool.note_nlp
114note_nlp_concept_idYesINTEGERA 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
115note_nlp_source_concept_idYesINTEGERA foreign key to a Concept that refers to the code in the source vocabulary used by the NLP systemnote_nlp
116nlp_systemNoVARCHAR(250)Name and version of the NLP system that extracted the term.Useful for data provenance.note_nlp
117nlp_dateYesDATEThe date of the note processing.Useful for data provenance.note_nlp
118nlp_datetimeNoDATETIMEThe date and time of the note processing. Useful for data provenance.note_nlp
119term_existsNoVARCHAR(1)A summary modifier that signifies presence or absence of the term for a given patient. Useful for quick querying.note_nlp
120term_temporalNoVARCHAR(50)An optional time modifier associated with the extracted term. (for now “past” or “present” only). Standardize it later.note_nlp
121term_modifiersNoVARCHAR(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
122observation_idYesINTEGERA unique identifier for each observation.observation
123person_idYesINTEGERA 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
124observation_concept_idYesINTEGERA foreign key to the standard observation concept identifier in the Standardized Vocabularies.observation
125observation_dateNoDATEThe date of the observation.observation
126observation_datetimeYesDATETIMEThe date and time of the observation.observation
127observation_type_concept_idYesINTEGERA foreign key to the predefined concept identifier in the Standardized Vocabularies reflecting the type of the observation.observation
128value_as_numberNoFLOATThe observation result stored as a number. This is applicable to observations where the result is expressed as a numeric value.observation
129value_as_stringNoVARCHAR(60)The observation result stored as a string. This is applicable to observations where the result is expressed as verbatim text.observation
130value_as_concept_idNoINTEGERA 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
131qualifier_concept_idNoINTEGERA foreign key to a Standard Concept ID for a qualifier (e.g., severity of drug-drug interaction alert)observation
132unit_concept_idNoINTEGERA foreign key to a Standard Concept ID of measurement units in the Standardized Vocabularies.observation
133provider_idNoINTEGERA foreign key to the provider in the PROVIDER table who was responsible for making the observation.observation
134visit_occurrence_idNoINTEGERA foreign key to the visit in the VISIT_OCCURRENCE table during which the observation was recorded.observation
135visit_detail_idNoINTEGERA foreign key to the visit in the VISIT_DETAIL table during which the observation was recorded.observation
136observation_source_valueNoVARCHAR(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
137observation_source_concept_idYesINTEGERA foreign key to a Concept that refers to the code used in the source.observation
138unit_source_valueNoVARCHAR(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
139qualifier_source_valueNoVARCHAR(50)The source value associated with a qualifier to characterize the observationobservation
140observation_event_idNoINTEGERA foreign key to an event table (e.g., PROCEDURE_OCCURRENCE_ID).observation
141obs_event_field_concept_idYesINTEGERA foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies referring to the field represented in the OBSERVATION_EVENT_ID.observation
142value_as_datetimeNoINTEGERThe observation result stored as a datetime value. This is applicable to observations where the result is expressed as a point in time.observation
143observation_period_idYesINTEGERA unique identifier for each observation period.observation_period
144person_idYesINTEGERA 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
145observation_period_start_dateYesDATEThe start date of the observation period for which data are available from the data source.observation_period
146observation_period_end_dateYesDATEThe end date of the observation period for which data are available from the data source.observation_period
147period_type_concept_idYesINTEGERA 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' vocabularyobservation_period
148person_idYesINTEGERA unique identifier for each person.person
149gender_concept_idYesINTEGERA foreign key that refers to an identifier in the CONCEPT table for the unique gender of the person.person
150year_of_birthYesINTEGERThe 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
151month_of_birthNoINTEGERThe 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
152day_of_birthNoINTEGERThe 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
153birth_datetimeNoDATETIMEThe date and time of birth of the person.person
154death_datetimeNoDATETIMEThe date and time of death of the person.person
155race_concept_idYesINTEGERA foreign key that refers to an identifier in the CONCEPT table for the unique race of the person, belonging to the 'Race' vocabulary.person
156ethnicity_concept_idYesINTEGERA 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
157location_idNoINTEGERA foreign key to the place of residency for the person in the location table, where the detailed address information is stored.person
158provider_idNoINTEGERA foreign key to the primary care provider the person is seeing in the provider table.person
159care_site_idNoINTEGERA foreign key to the site of primary care in the care_site table, where the details of the care site are stored.person
160person_source_valueNoVARCHAR(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
161gender_source_valueNoVARCHAR(50)The source code for the gender of the person as it appears in the source data. The persons gender is mapped to a standard gender concept in the Standardized Vocabularies; the original value is stored here for reference.person
162gender_source_concept_idYesINTEGERA foreign key to the gender concept that refers to the code used in the source.person
163race_source_valueNoVARCHAR(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
164race_source_concept_idYesINTEGERA foreign key to the race concept that refers to the code used in the source.person
165ethnicity_source_valueNoVARCHAR(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
166ethnicity_source_concept_idYesINTEGERA foreign key to the ethnicity concept that refers to the code used in the source.person
167procedure_occurrence_idYesINTEGERA system-generated unique identifier for each Procedure Occurrence.procedure_occurrence
168person_idYesINTEGERA 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
169procedure_concept_idYesINTEGERA foreign key that refers to a standard procedure Concept identifier in the Standardized Vocabularies.procedure_occurrence
170procedure_dateNoDATEThe date on which the Procedure was performed.procedure_occurrence
171procedure_datetimeYesDATETIMEThe date and time on which the Procedure was performed.procedure_occurrence
172procedure_type_concept_idYesINTEGERA 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
173modifier_concept_idYesINTEGERA 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
174quantityNoINTEGERThe quantity of procedures ordered or administered.procedure_occurrence
175provider_idNoINTEGERA foreign key to the provider in the PROVIDER table who was responsible for carrying out the procedure.procedure_occurrence
176visit_occurrence_idNoINTEGERA foreign key to the Visit in the VISIT_OCCURRENCE table during which the Procedure was carried out.procedure_occurrence
177visit_detail_idNoINTEGERA foreign key to the Visit Detail in the VISIT_DETAIL table during which the Procedure was carried out.procedure_occurrence
178procedure_source_valueNoVARCHAR(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
179procedure_source_concept_idYesINTEGERA foreign key to a Procedure Concept that refers to the code used in the source.procedure_occurrence
180modifier_source_valueNoVARCHAR(50)The source code for the qualifier as it appears in the source data.procedure_occurrence
181specimen_idYesINTEGERA unique identifier for each specimen.specimen
182person_idYesINTEGERA foreign key identifier to the Person for whom the Specimen is recorded.specimen
183specimen_concept_idYesINTEGERA foreign key referring to a Standard Concept identifier in the Standardized Vocabularies for the Specimen.specimen
184specimen_type_concept_idYesINTEGERA 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
185specimen_dateNoDATEThe date the specimen was obtained from the Person.specimen
186specimen_datetimeYesDATETIMEThe date and time on the date when the Specimen was obtained from the person.specimen
187quantityNoFLOATThe amount of specimen collection from the person during the sampling procedure.specimen
188unit_concept_idNoINTEGERA foreign key to a Standard Concept identifier for the Unit associated with the numeric quantity of the Specimen collection.specimen
189anatomic_site_concept_idYesINTEGERA foreign key to a Standard Concept identifier for the anatomic location of specimen collection.specimen
190disease_status_concept_idYesINTEGERA foreign key to a Standard Concept identifier for the Disease Status of specimen collection.specimen
191specimen_source_idNoVARCHAR(50)The Specimen identifier as it appears in the source data.specimen
192specimen_source_valueNoVARCHAR(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
193unit_source_valueNoVARCHAR(50)The information about the Unit as detailed in the source.specimen
194anatomic_site_source_valueNoVARCHAR(50)The information about the anatomic site as detailed in the source.specimen
195disease_status_source_valueNoVARCHAR(50)The information about the disease status as detailed in the source.specimen
196survey_conduct_idYesINTEGERUnique identifier for each completed survey.survey_conduct
197person_idYesINTEGERA foreign key identifier to the Person in the PERSON table about whom the survey was completed.survey_conduct
198survey_concept_idYesINTEGERA foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the name and identity of the survey.survey_conduct
199survey_start_dateNoDATEDate on which the survey was started.survey_conduct
200survey_start_datetimeNoDATETIMEDate and time the survey was started.survey_conduct
201survey_end_dateYesDATEDate on which the survey was completed.survey_conduct
202survey_end_datetimeNoDATETIMEDate and time the survey was completed.survey_conduct
203provider_idNo<C2>INTEGER<C2>A foreign key to the provider in the provider table who was associated with the survey completion.survey_conduct
204assisted_concept_idYesINTEGERA foreign key to the predefined Concept identifier in the Standardized Vocabularies indicating whether the survey was completed with assistance.survey_conduct
205respondent_type_concept_idYesINTEGERA foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the respondent type. Example: Research Associate, Patient.survey_conduct
206timing_concept_idYesINTEGERA 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
207collection_method_concept_idYesINTEGERA foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the data collection method (e.g. Paper, Telephone, Electronic Questionnaire).survey_conduct
208assisted_source_valueNoVARCHAR(50)Source value representing whether patient required assistance to complete the survey. Example: “Completed without assistance”, ”Completed with assistance”.survey_conduct
209respondent_type_source_valueNoVARCHAR(100)Source code representing role of person who completed the survey.survey_conduct
210timing_source_valueNoVARCHAR(100)Text string representing the timing of the survey. Example: Baseline, 6-month follow-up.survey_conduct
211collection_method_source_valueNoVARCHAR(100)The collection method as it appears in the source data.survey_conduct
212survey_source_valueNoVARCHAR(100)The survey name/title as it appears in the source data.survey_conduct
213survey_source_concept_idYesINTEGERA foreign key to a predefined Concept that refers to the code for the survey name/title used in the source.survey_conduct
214survey_source_identifierNoVARCHAR(100)Unique identifier for each completed survey in source system.survey_conduct
215validated_survey_concept_idYesINTEGERA foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the validation status of the survey.survey_conduct
216validated_survey_source_valueNoINTEGERSource value representing the validation status of the survey.survey_conduct
217survey_version_numberNoVARCHAR(20)Version number of the questionnaire or survey used.survey_conduct
218visit_occurrence_idNoINTEGERA foreign key to the VISIT_OCCURRENCE table during which the survey was completedsurvey_conduct
219response_visit_occurrence_idNoINTEGER<C2>A foreign key to the visit in the VISIT_OCCURRENCE table during which treatment was carried out that relates to this survey.survey_conduct
220visit_detail_idYesINTEGERA unique identifier for each Person's visit or encounter at a healthcare provider.visit_detail
221person_idYesINTEGERA 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
222visit_detail_concept_idYesINTEGERA foreign key that refers to a visit Concept identifier in the Standardized Vocabularies belonging to the 'Visit' Vocabulary.visit_detail
223visit_detail_start_dateNoDATEThe start date of the visit.visit_detail
224visit_detail_start_datetimeYesDATETIMEThe date and time of the visit started.visit_detail
225visit_detail_end_dateNoDATEThe end date of the visit. If this is a one-day visit the end date should match the start date.visit_detail
226visit_detail_end_datetimeYesDATETIMEThe date and time of the visit end.visit_detail
227visit_detail_type_concept_idYesINTEGERA 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
228provider_idNoINTEGERA foreign key to the provider in the provider table who was associated with the visit.visit_detail
229care_site_idNoINTEGERA foreign key to the care site in the care site table that was visited.visit_detail
230visit_detail_source_valueNoSTRING(50)The source code for the visit as it appears in the source data.visit_detail
231visit_detail_source_concept_idYesINTEGERA foreign key to a Concept that refers to the code used in the source.visit_detail
232admitted_from_source_valueNoVARCHAR(50)The source code for the admitting source as it appears in the source data.visit_detail
233admitted_from_concept_idYesINTEGERA foreign key to the predefined concept in the 'Place of Service' Vocabulary reflecting the admitting source for a visit.visit_detail
234discharge_to_source_valueNoVARCHAR(50)The source code for the discharge disposition as it appears in the source data.visit_detail
235discharge_to_concept_idYesINTEGERA foreign key to the predefined concept in the 'Place of Service' Vocabulary reflecting the discharge disposition for a visit.visit_detail
236preceding_visit_detail_idNoINTEGERA foreign key to the VISIT_DETAIL table of the visit immediately preceding this visitvisit_detail
237visit_detail_parent_idNoINTEGERA foreign key to the VISIT_DETAIL table record to represent the immediate parent visit-detail record.visit_detail
238visit_occurrence_idYesINTEGERA 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
239visit_occurrence_idYesINTEGERA unique identifier for each Person's visit or encounter at a healthcare provider.visit_occurrence
240person_idYesINTEGERA 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
241visit_concept_idYesINTEGERA foreign key that refers to a visit Concept identifier in the Standardized Vocabularies belonging to the 'Visit' Vocabulary.visit_occurrence
242visit_start_dateNoDATEThe start date of the visit.visit_occurrence
243visit_start_datetimeYesDATETIMEThe date and time of the visit started.visit_occurrence
244visit_end_dateNoDATEThe end date of the visit. If this is a one-day visit the end date should match the start date.visit_occurrence
245visit_end_datetimeYesDATETIMEThe date and time of the visit end.visit_occurrence
246visit_type_concept_idYesINTEGERA 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
247provider_idNoINTEGERA foreign key to the provider in the provider table who was associated with the visit.visit_occurrence
248care_site_idNoINTEGERA foreign key to the care site in the care site table that was visited.visit_occurrence
249visit_source_valueNoVARCHAR(50)The source code for the visit as it appears in the source data.visit_occurrence
250visit_source_concept_idYesINTEGERA foreign key to a Concept that refers to the code used in the source.visit_occurrence
251admitting_source_concept_idYesINTEGERA foreign key to the predefined concept in the Place of Service Vocabulary reflecting the admitting source for a visit.visit_occurrence
252admitting_source_valueNoVARCHAR(50)The source code for the admitting source as it appears in the source data.visit_occurrence
253discharge_to_concept_idYesINTEGERA foreign key to the predefined concept in the Place of Service Vocabulary reflecting the discharge disposition for a visit.visit_occurrence
254discharge_to_source_valueNoVARCHAR(50)The source code for the discharge disposition as it appears in the source data.visit_occurrence
255preceding_visit_occurrence_idNoINTEGERA foreign key to the VISIT_OCCURRENCE table of the visit immediately preceding this visitvisit_occurrence
256condition_era_idYesINTEGERA unique identifier for each Condition Era.condition_era
257person_idYesINTEGERA 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
258condition_concept_idYesINTEGERA foreign key that refers to a standard Condition Concept identifier in the Standardized Vocabularies.condition_era
259condition_era_start_datetimeYesDATEThe 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
260condition_era_end_datetimeYesDATEThe 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
261condition_occurrence_countNoINTEGERThe number of individual Condition Occurrences used to construct the condition era.condition_era
262dose_era_idYesINTEGERA unique identifier for each Dose Era.dose_era
263person_idYesINTEGERA 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
264drug_concept_idYesINTEGERA foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the active Ingredient Concept.dose_era
265unit_concept_idYesINTEGERA foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the unit concept.dose_era
266dose_valueYesFLOATThe numeric value of the dose.dose_era
267dose_era_start_datetimeYesDATEThe 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
268dose_era_end_datetimeYesDATEThe 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
269drug_era_idYesINTEGERA unique identifier for each Drug Era.drug_era
270person_idYesINTEGERA 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
271drug_concept_idYesINTEGERA foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the Ingredient Concept.drug_era
272drug_era_start_datetimeYesDATEThe 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
273drug_era_end_datetimeYesDATEThe 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
274drug_exposure_countNoINTEGERThe number of individual Drug Exposure occurrences used to construct the Drug Era.drug_era
275gap_daysNoINTEGERThe number of days that are not covered by DRUG_EXPOSURE records that were used to make up the era record.drug_era
276cost_idYesINTEGERA unique identifier for each COST record.cost
277person_idYesINTEGERA unique identifier for each PERSON.cost
278cost_event_idYesINTEGERA foreign key identifier to the event (e.g. Measurement, Procedure, Visit, Drug Exposure, etc) record for which cost data are recorded.cost
279cost_event_field_concept_idYesINTEGERA foreign key identifier to a concept in the CONCEPT table representing the identity of the field represented by COST_EVENT_IDcost
280cost_concept_idYesINTEGERA foreign key that refers to a Standard Cost Concept identifier in the Standardized Vocabularies belonging to the 'Cost' vocabulary.cost
281cost_type_concept_idYesINTEGERA 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' vocabularycost
282cost_source_concept_idYesINTEGERA foreign key to a Cost Concept that refers to the code used in the source.cost
283cost_source_valueNoVARCHAR(50)The source value for the cost as it appears in the source datacost
284currency_concept_idYesINTEGERA 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' vocabularycost
285costYesFLOATThe actual financial cost amountcost
286incurred_dateYesDATEThe 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
287billed_dateNoDATEThe date a bill was generated for a service or encountercost
288paid_dateNoDATEThe date payment was received for a service or encountercost
289revenue_code_concept_idYesINTEGERA foreign key referring to a Standard Concept ID in the Standardized Vocabularies for Revenue codes belonging to the 'Revenue Code' vocabulary.cost
290drg_concept_idYesINTEGERA foreign key referring to a Standard Concept ID in the Standardized Vocabularies for DRG codes belonging to the 'DRG' vocabulary.cost
291revenue_code_source_valueNoVARCHAR(50)The source value for the Revenue code as it appears in the source data, stored here for reference.cost
292drg_source_valueNoVARCHAR(50)The source value for the 3-digit DRG source code as it appears in the source data, stored here for reference.cost
293payer_plan_period_idNoINTEGERA 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
294payer_plan_period_idYesINTEGERA identifier for each unique combination of payer, plan, family code and time span.payer_plan_period
295person_idYesINTEGERA 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
296contract_person_idNoINTEGERA 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
297payer_plan_period_start_dateYesDATEThe start date of the payer plan period.payer_plan_period
298payer_plan_period_end_dateYesDATEThe end date of the payer plan period.payer_plan_period
299payer_concept_idYesINTEGERA foreign key that refers to a standard Payer concept identifier in the Standarized Vocabulariespayer_plan_period
300payer_source_valueNoVARCHAR(50)The source code for the payer as it appears in the source data.payer_plan_period
301payer_source_concept_idYesINTEGERA foreign key to a payer concept that refers to the code used in the source.payer_plan_period
302plan_concept_idYesINTEGERA foreign key that refers to a standard plan concept identifier that represents the health benefit plan in the Standardized Vocabularies.payer_plan_period
303plan_source_valueNoVARCHAR(50)The source code for the Person's health benefit plan as it appears in the source data.payer_plan_period
304plan_source_concept_idYesINTEGERA foreign key to a plan concept that refers to the plan code used in the source data.payer_plan_period
305contract_concept_idYesINTEGERA foreign key to a standard concept representing the reason justifying the contract between person_id and contract_person_id.payer_plan_period
306contract_source_valueNoINTEGERThe source code representing the reason justifying the contract. Usually it is family relationship like a spouse, domestic partner, child etc.payer_plan_period
307contract_source_concept_idYesINTEGERA foreign key to a concept that refers to the code used in the source as the reason justifying the contract.payer_plan_period
308sponsor_concept_idYesINTEGERA foreign key that refers to a concept identifier that represents the sponsor in the Standardized Vocabularies.payer_plan_period
309sponsor_source_valueNoVARCHAR(50)The source code for the Person's sponsor of the health plan as it appears in the source data.payer_plan_period
310sponsor_source_concept_idYesINTEGERA foreign key to a sponsor concept that refers to the sponsor code used in the source data.payer_plan_period
311family_source_valueNoVARCHAR(50)The source code for the Person's family as it appears in the source data.payer_plan_period
312stop_reason_concept_idYesINTEGERA foreign key that refers to a standard termination reason that represents the reason for the termination in the Standardized Vocabularies.payer_plan_period
313stop_reason_source_valueNoVARCHAR(50)The reason for stop-coverage as it appears in the source data.payer_plan_period
314stop_reason_source_concept_idYesINTEGERA foreign key to a stop-coverage concept that refers to the code used in the source.payer_plan_period
315care_site_idYesINTEGERA unique identifier for each Care Site.care_site
316care_site_nameNoVARCHAR(255)The verbatim description or name of the Care Site as in data sourcecare_site
317place_of_service_concept_idYesINTEGERA foreign key that refers to a Place of Service Concept ID in the Standardized Vocabularies.care_site
318location_idNoINTEGERA foreign key to the geographic Location in the LOCATION table, where the detailed address information is stored.care_site
319care_site_source_valueNoVARCHAR(50)The identifier for the Care Site in the source data, stored here for reference.care_site
320place_of_service_source_valueNoVARCHAR(50)The source code for the Place of Service as it appears in the source data, stored here for reference.care_site
321location_idYesINTEGERA unique identifier for each geographic location.location
322address_1NoVARCHAR(50)The address field 1, typically used for the street address, as it appears in the source data.location
323address_2NoVARCHAR(50)The address field 2, typically used for additional detail such as buildings, suites, floors, as it appears in the source data.location
324cityNoVARCHAR(50)The city field as it appears in the source data.location
325stateNoVARCHAR(2)The state field as it appears in the source data.location
326zipNoVARCHAR(9)The zip or postal code.location
327countyNoVARCHAR(20)The county.location
328countryNoVARCHAR(100)The countrylocation
329location_source_valueNoVARCHAR(50)The verbatim information that is used to uniquely identify the location as it appears in the source data.location
330latitudeNoFLOATThe geocoded latitudelocation
331longitudeNoFLOATThe geocoded longitudelocation
332location_idYesINTEGERA foreign key to the location table.location_history
333relationship_type_concept_idYesVARCHAR(50)The type of relationship between location and entity.location_history
334domain_idYesVARCHAR(50)The domain of the entity that is related to the location. Either PERSON, PROVIDER, or CARE_SITE.location_history
335entity_idYesINTEGERThe unique identifier for the entity. References either person_id, provider_id, or care_site_id, depending on domain_id.location_history
336start_dateYesDATEThe date the relationship started.location_history
337end_dateNoDATEThe date the relationship ended.location_history
338provider_idYesINTEGERA unique identifier for each Provider.provider
339provider_nameNoVARCHAR(255)A description of the Provider.provider
340npiNoVARCHAR(20)The National Provider Identifier (NPI) of the provider.provider
341deaNoVARCHAR(20)The Drug Enforcement Administration (DEA) number of the provider.provider
342specialty_concept_idYesINTEGERA foreign key to a Standard Specialty Concept ID in the Standardized Vocabularies.provider
343care_site_idNoINTEGERA foreign key to the main Care Site where the provider is practicing.provider
344year_of_birthNoINTEGERThe year of birth of the Provider.provider
345gender_concept_idYesINTEGERThe gender of the Provider.provider
346provider_source_valueNoVARCHAR(50)The identifier used for the Provider in the source data, stored here for reference.provider
347specialty_source_valueNoVARCHAR(50)The source code for the Provider specialty as it appears in the source data, stored here for reference.provider
348specialty_source_concept_idYesINTEGERA foreign key to a Concept that refers to the code used in the source.provider
349gender_source_valueNoVARCHAR(50)The gender code for the Provider as it appears in the source data, stored here for reference.provider
350gender_source_concept_idYesINTEGERA foreign key to a Concept that refers to the code used in the source.provider
351cdm_source_nameYesVARCHAR(255)The full name of the sourcecdm_source
352cdm_source_abbreviationNoVARCHAR(25)An abbreviation of the namecdm_source
353cdm_holderNoVARCHAR(255)The name of the organization responsible for the development of the CDM instancecdm_source
354source_descriptionNoCLOBA 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
355source_documentation_referenceNoVARCHAR(255)URL or other external reference to location of source documentationcdm_source
356cdm_etl_referenceNoVARCHAR(255)URL or other external reference to location of ETL specification documentation and ETL source codecdm_source
357source_release_dateNoDATEThe date for which the source data are most current, such as the last day of data capturecdm_source
358cdm_release_dateNoDATEThe date when the CDM was instantiatedcdm_source
359cdm_versionNoVARCHAR(10)The version of CDM usedcdm_source
360vocabulary_versionNoVARCHAR(20)The version of the vocabulary usedcdm_source
361metadata_concept_idYesINTEGERA foreign key that refers to a Standard Metadata Concept identifier in the Standardized Vocabularies.metadata
362metadata_type_concept_idYesINTEGERA foreign key that refers to a Standard Type Concept identifier in the Standardized Vocabularies.metadata
363nameYesVARCHAR(250)The name of the Concept stored in metadata_concept_id or a description of the data being stored.metadata
364value_as_stringNoNVARCHARThe metadata value stored as a string.metadata
365value_as_concept_idNoINTEGERA foreign key to a metadata value stored as a Concept ID.metadata
366metadata dateNoDATEThe date associated with the metadatametadata
367metadata_datetimeNoDATETIMEThe date and time associated with the metadatametadata
368concept_idYesINTEGERA unique identifier for each Concept across all domains.concept
369concept_nameYesVARCHAR(255)An unambiguous, meaningful and descriptive name for the Concept.concept
370domain_idYesVARCHAR(20)A foreign key to the [DOMAIN](https://github.com/OHDSI/CommonDataModel/wiki/DOMAIN) table the Concept belongs to.concept
371vocabulary_idYesVARCHAR(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
372concept_class_idYesVARCHAR(20)The attribute or concept class of the Concept. Examples are 'Clinical Drug', 'Ingredient', 'Clinical Finding' etc.concept
373standard_conceptNoVARCHAR(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
374concept_codeYesVARCHAR(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
375valid_start_dateYesDATEThe date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.concept
376valid_end_dateYesDATEThe 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
377invalid_reasonNoVARCHAR(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
378ancestor_concept_idYesINTEGERA foreign key to the concept in the concept table for the higher-level concept that forms the ancestor in the relationship.concept_ancestor
379descendant_concept_idYesINTEGERA foreign key to the concept in the concept table for the lower-level concept that forms the descendant in the relationship.concept_ancestor
380min_levels_of_separationYesINTEGERThe 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
381max_levels_of_separationYesINTEGERThe 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
382concept_class_idYesVARCHAR(20)A unique key for each class.concept_class
383concept_class_nameYesVARCHAR(255)The name describing the Concept Class, e.g. "Clinical Finding", "Ingredient", etc.concept_class
384concept_class_concept_idYesINTEGERA 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
385concept_id_1YesINTEGERA 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
386concept_id_2YesINTEGERA 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
387relationship_idYesVARCHAR(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
388valid_start_dateYesDATEThe date when the instance of the Concept Relationship is first recorded.concept_relationship
389valid_end_dateYesDATEThe 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
390invalid_reasonNoVARCHAR(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
391concept_idYesINTEGERA foreign key to the Concept in the CONCEPT table.concept_synonym
392concept_synonym_nameYesVARCHAR(1000)The alternative name for the Concept.concept_synonym
393language_concept_idYesINTEGERA foreign key to a Concept representing the language.concept_synonym
394domain_idYesVARCHAR(20)A unique key for each domain.domain
395domain_nameYesVARCHAR(255)The name describing the Domain, e.g. "Condition", "Procedure", "Measurement" etc.domain
396domain_concept_idYesINTEGERA 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
397drug_concept_idYesINTEGERA foreign key to the Concept in the CONCEPT table representing the identifier for Branded Drug or Clinical Drug Concept.drug_strength
398ingredient_concept_idYesINTEGERA foreign key to the Concept in the CONCEPT table, representing the identifier for drug Ingredient Concept contained within the drug product.drug_strength
399amount_valueNoFLOATThe numeric value associated with the amount of active ingredient contained within the product.drug_strength
400amount_unit_concept_idNoINTEGERA foreign key to the Concept in the CONCEPT table representing the identifier for the Unit for the absolute amount of active ingredient.drug_strength
401numerator_valueNoFLOATThe numeric value associated with the concentration of the active ingredient contained in the productdrug_strength
402numerator_unit_concept_idNoINTEGERA foreign key to the Concept in the CONCEPT table representing the identifier for the numerator Unit for the concentration of active ingredient.drug_strength
403denominator_valueNoFLOATThe amount of total liquid (or other divisible product, such as ointment, gel, spray, etc.).drug_strength
404denominator_unit_concept_idNoINTEGERA foreign key to the Concept in the CONCEPT table representing the identifier for the denominator Unit for the concentration of active ingredient.drug_strength
405box_sizeNoINTEGERThe number of units of Clinical of Branded Drug, or Quantified Clinical or Branded Drug contained in a box as dispensed to the patientdrug_strength
406valid_start_dateYesDATEThe date when the Concept was first recorded. The default value is 1-Jan-1970.drug_strength
407valid_end_dateYesDATEThe 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
408invalid_reasonNoVARCHAR(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
409relationship_idYesVARCHAR(20)The type of relationship captured by the relationship record.relationship
410relationship_nameYesVARCHAR(255)The text that describes the relationship type.relationship
411is_hierarchicalYesVARCHAR(1)Defines whether a relationship defines concepts into classes or hierarchies. Values are 1 for hierarchical relationship or 0 if not.relationship
412defines_ancestryYesVARCHAR(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
413reverse_relationship_idYesVARCHAR(20)The identifier for the relationship used to define the reverse relationship between two concepts.relationship
414relationship_concept_idYesINTEGERA foreign key that refers to an identifier in the CONCEPT table for the unique relationship concept.relationship
415source_codeYesVARCHAR(50)The source code being translated into a Standard Concept.source_to_concept_map
416source_concept_idYesINTEGERA foreign key to the Source Concept that is being translated into a Standard Concept.source_to_concept_map
417source_vocabulary_idYesVARCHAR(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
418source_code_descriptionNoVARCHAR(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
419target_concept_idYesINTEGERA foreign key to the target Concept to which the source code is being mapped.source_to_concept_map
420target_vocabulary_idYesVARCHAR(20)A foreign key to the VOCABULARY table defining the vocabulary of the target Concept.source_to_concept_map
421valid_start_dateYesDATEThe date when the mapping instance was first recorded.source_to_concept_map
422valid_end_dateYesDATEThe 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
423invalid_reasonNoVARCHAR(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
424vocabulary_idYesVARCHAR(20)A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit.vocabulary
425vocabulary_nameYesVARCHAR(255)The name describing the vocabulary, for example "International Classification of Diseases, Ninth Revision, Clinical Modification, Volume 1 and 2 (NCHS)" etc.vocabulary
426vocabulary_referenceYesVARCHAR(255)External reference to documentation or available download of the about the vocabulary.vocabulary
427vocabulary_versionNoVARCHAR(255)Version of the Vocabulary as indicated in the source.vocabulary
428vocabulary_concept_idYesINTEGERA foreign key that refers to a standard concept identifier in the CONCEPT table for the Vocabulary the VOCABULARY record belongs to.vocabulary