OMOP/OMOP_CDM_v5_3.csv

63 KiB
Raw Permalink Blame History

1fieldrequiredtypedescriptiontable
2condition_occurrence_idYesINTEGERA unique identifier for each Condition Occurrence event.condition_occurrence
3person_idYesINTEGERA 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
4condition_concept_idYesINTEGERA foreign key that refers to a Standard Condition Concept identifier in the Standardized Vocabularies.condition_occurrence
5condition_start_dateYesDATEThe date when the instance of the Condition is recorded.condition_occurrence
6condition_start_datetimeNoDATETIMEThe date and time when the instance of the Condition is recorded.condition_occurrence
7condition_end_dateNoDATEThe date when the instance of the Condition is considered to have ended.condition_occurrence
8condition_end_datetimeNoDATEThe date when the instance of the Condition is considered to have ended.condition_occurrence
9condition_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.condition_occurrence
10stop_reasonNoVARCHAR(20)The reason that the condition was no longer present, as indicated in the source data.condition_occurrence
11provider_idNoINTEGERA foreign key to the Provider in the PROVIDER table who was responsible for capturing (diagnosing) the Condition.condition_occurrence
12visit_occurrence_idNoINTEGERA foreign key to the visit in the VISIT_OCCURRENCE table during which the Condition was determined (diagnosed).condition_occurrence
13visit_detail_idNoINTEGERA foreign key to the visit in the VISIT_DETAIL table during which the Condition was determined (diagnosed).condition_occurrence
14condition_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
15condition_source_concept_idNoINTEGERA foreign key to a Condition Concept that refers to the code used in the source.condition_occurrence
16condition_status_source_valueNoVARCHAR(50)The source code for the condition status as it appears in the source data.condition_occurrence
17condition_status_concept_idNoINTEGERA foreign key to the predefined Concept in the Standard Vocabulary reflecting the condition statuscondition_occurrence
18person_idYesINTEGERA foreign key identifier to the deceased person. The demographic details of that person are stored in the person table.death
19death_dateYesDATEThe date the person was deceased. If the precise date including day or month is not known or not allowed, December is used as the default month, and the last day of the month the default day.death
20death_datetimeNoDATETIMEThe date and time the person was deceased. If the precise date including day or month is not known or not allowed, December is used as the default month, and the last day of the month the default day.death
21death_type_concept_idYesINTEGERA foreign key referring to the predefined concept identifier in the Standardized Vocabularies reflecting how the death was represented in the source data.death
22cause_concept_idNoINTEGERA foreign key referring to a standard concept identifier in the Standardized Vocabularies for conditions.death
23cause_source_valueNoVARCHAR(50)The source code for the cause of death as it appears in the source data. This code is mapped to a standard concept in the Standardized Vocabularies and the original code is, stored here for reference.death
24cause_source_concept_idNoINTEGERA foreign key to the concept that refers to the code used in the source. Note, this variable name is abbreviated to ensure it will be allowable across database platforms.death
25device_exposure_idYesINTEGERA system-generated unique identifier for each Device Exposure.device_exposure
26person_idYesINTEGERA 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
27device_concept_idYesINTEGERA foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the Device concept.device_exposure
28device_exposure_start_dateYesDATEThe date the Device or supply was applied or used.device_exposure
29device_exposure_start_datetimeNoDATETIMEThe date and time the Device or supply was applied or used.device_exposure
30device_exposure_end_dateNoDATEThe date the Device or supply was removed from use.device_exposure
31device_exposure_end_datetimeNoDATETIMEThe date and time the Device or supply was removed from use.device_exposure
32device_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.device_exposure
33unique_device_idNoVARCHAR(50)A UDI or equivalent identifying the instance of the Device used in the Person.device_exposure
34quantityNoINTEGERThe number of individual Devices used for the exposure.device_exposure
35provider_idNoINTEGERA foreign key to the provider in the PROVIDER table who initiated of administered the Device.device_exposure
36visit_occurrence_idNoINTEGERA foreign key to the visit in the VISIT_OCCURRENCE table during which the device was used.device_exposure
37visit_detail_idNoINTEGERA foreign key to the visit detail in the VISIT_DETAIL table during which the Drug Exposure was initiated.device_exposure
38device_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
39device_source_ concept_idNoINTEGERA foreign key to a Device Concept that refers to the code used in the source.device_exposure
40drug_exposure_idYesINTEGERA system-generated unique identifier for each Drug utilization event.drug_exposure
41person_idYesINTEGERA 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
42drug_concept_idYesINTEGERA foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the Drug concept.drug_exposure
43drug_exposure_start_dateYesDATEThe 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
44drug_exposure_start_datetimeNoDATETIMEThe start date and time for the current instance of Drug utilization. Valid entries include a start date of a prescription, the date a prescription was filled, or the date on which a Drug administration procedure was recorded.drug_exposure
45drug_exposure_end_dateYesDATEThe end date for the current instance of Drug utilization. It is not available from all sources.drug_exposure
46drug_exposure_end_datetimeNoDATETIMEThe end date and time for the current instance of Drug utilization. It is not available from all sources.drug_exposure
47verbatim_end_dateNoDATEThe known end date of a drug_exposure as provided by the sourcedrug_exposure
48drug_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.drug_exposure
49stop_reasonNoVARCHAR(20)The reason the Drug was stopped. Reasons include regimen completed, changed, removed, etc.drug_exposure
50refillsNoINTEGERThe number of refills after the initial prescription. The initial prescription is not counted, values start with 0.drug_exposure
51quantityNoFLOATThe quantity of drug as recorded in the original prescription or dispensing record.drug_exposure
52days_supplyNoINTEGERThe number of days of supply of the medication as recorded in the original prescription or dispensing record.drug_exposure
53sigNoVARCHAR(MAX)The directions ("signetur") on the Drug prescription as recorded in the original prescription (and printed on the container) or dispensing record.drug_exposure
54route_concept_idNoINTEGERA foreign key to a predefined concept in the Standardized Vocabularies reflecting the route of administration.drug_exposure
55lot_numberNoVARCHAR(50)An identifier assigned to a particular quantity or lot of Drug product from the manufacturer.drug_exposure
56provider_idNoINTEGERA foreign key to the provider in the PROVIDER table who initiated (prescribed or administered) the Drug Exposure.drug_exposure
57visit_occurrence_idNoINTEGERA foreign key to the Visit in the VISIT_OCCURRENCE table during which the Drug Exposure was initiated.drug_exposure
58visit_detail_idNoINTEGERA foreign key to the Visit Detail in the VISIT_DETAIL table during which the Drug Exposure was initiated.drug_exposure
59drug_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
60drug_source_concept_idNoINTEGERA foreign key to a Drug Concept that refers to the code used in the source.drug_exposure
61route_source_valueNoVARCHAR(50)The information about the route of administration as detailed in the source.drug_exposure
62dose_unit_source_valueNoVARCHAR(50)The information about the dose unit as detailed in the source.drug_exposure
63domain_concept_id_1YesINTEGERThe concept representing the domain of fact one, from which the corresponding table can be inferred.fact_relationship
64fact_id_1YesINTEGERThe unique identifier in the table corresponding to the domain of fact one.fact_relationship
65domain_concept_id_2YesINTEGERThe concept representing the domain of fact two, from which the corresponding table can be inferred.fact_relationship
66fact_id_2YesINTEGERThe unique identifier in the table corresponding to the domain of fact two.fact_relationship
67relationship_concept_idYesINTEGERA foreign key to a Standard Concept ID of relationship in the Standardized Vocabularies.fact_relationship
68measurement_idYesINTEGERA unique identifier for each Measurement.measurement
69person_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
70measurement_concept_idYesINTEGERA foreign key to the standard measurement concept identifier in the Standardized Vocabularies.measurement
71measurement_dateYesDATEThe date of the Measurement.measurement
72measurement_datetimeNoDATETIMEThe date and time of the Measurement. Some database systems don't have a datatype of time. To accomodate 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
73measurement_type_concept_idYesINTEGERA foreign key to the predefined Concept in the Standardized Vocabularies reflecting the provenance from where the Measurement record was recorded.measurement
74operator_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 <, <=, =, >=, >.measurement
75value_as_numberNoFLOATA Measurement result where the result is expressed as a numeric value.measurement
76value_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.).measurement
77unit_concept_idNoINTEGERA foreign key to a Standard Concept ID of Measurement Units in the Standardized Vocabularies.measurement
78range_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
79range_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
80provider_idNoINTEGERA foreign key to the provider in the PROVIDER table who was responsible for initiating or obtaining the measurement.measurement
81visit_occurrence_idNoINTEGERA foreign key to the Visit in the VISIT_OCCURRENCE table during which the Measurement was recorded.measurement
82visit_detail_idNoINTEGERA foreign key to the Visit Detail in the VISIT_DETAIL table during which the Measurement was recorded.measurement
83measurement_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
84measurement_source_concept_idNoINTEGERA foreign key to a Concept in the Standard Vocabularies that refers to the code used in the source.measurement
85unit_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
86value_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
87note_idYesINTEGERA unique identifier for each note.note
88person_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
89note_dateYesDATEThe date the note was recorded.note
90note_datetimeNoDATETIMEThe date and time the note was recorded.note
91note_type_concept_idYesINTEGERA foreign key to the predefined Concept in the Standardized Vocabularies reflecting the type, origin or provenance of the Note.note
92note_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
93note_titleNoVARCHAR(250)The title of the Note as it appears in the source.note
94note_textYesVARCHAR(MAX)The content of the Note.note
95encoding_concept_idYesINTEGERA foreign key to the predefined Concept in the Standardized Vocabularies reflecting the note character encoding typenote
96language_concept_idYesINTEGERA foreign key to the predefined Concept in the Standardized Vocabularies reflecting the language of the notenote
97provider_idNoINTEGERA foreign key to the Provider in the PROVIDER table who took the Note.note
98visit_occurrence_idNoINTEGERA foreign key to the Visit in the VISIT_OCCURRENCE table when the Note was taken.note
99visit_detail_idNoINTEGERA foreign key to the Visit in the VISIT_DETAIL table when the Note was taken.note
100note_source_valueNoVARCHAR(50)The source value associated with the origin of the Notenote
101note_nlp_idYesINTEGERA unique identifier for each term extracted from a note.note_nlp
102note_idYesINTEGERA foreign key to the Note table note the term was extracted from.note_nlp
103section_concept_idNoINTEGERA foreign key to the predefined Concept in the Standardized Vocabularies representing the section of the extracted term.note_nlp
104snippetNoVARCHAR(250)A small window of text surrounding the term.note_nlp
105offsetNoVARCHAR(50)Character offset of the extracted term in the input note.note_nlp
106lexical_variantYesVARCHAR(250)Raw text extracted from the NLP tool.note_nlp
107note_nlp_concept_idNoINTEGERA 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
108note_nlp_source_concept_idNoINTEGERA foreign key to a Concept that refers to the code in the source vocabulary used by the NLP systemnote_nlp
109nlp_systemNoVARCHAR(250)Name and version of the NLP system that extracted the term.Useful for data provenance.note_nlp
110nlp_dateYesDATEThe date of the note processing.Useful for data provenance.note_nlp
111nlp_date_timeNoDATETIMEThe date and time of the note processing. Useful for data provenance.note_nlp
112term_existsNoVARCHAR(1)A summary modifier that signifies presence or absence of the term for a given patient. Useful for quick querying. *note_nlp
113term_temporalNoVARCHAR(50)An optional time modifier associated with the extracted term. (for now <20>past<73> or <20>present<6E> only). Standardize it later.note_nlp
114term_modifiersNoVARCHAR(2000)A compact description of all the modifiers of the specific term extracted by the NLP system. (e.g. <20>son has rash<73> ? <20>negated=no,subject=family, certainty=undef,conditional=false,general=false<73>).note_nlp
115observation_idYesINTEGERA unique identifier for each observation.observation
116person_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
117observation_concept_idYesINTEGERA foreign key to the standard observation concept identifier in the Standardized Vocabularies.observation
118observation_dateYesDATEThe date of the observation.observation
119observation_datetimeNoDATETIMEThe date and time of the observation.observation
120observation_type_concept_idYesINTEGERA foreign key to the predefined concept identifier in the Standardized Vocabularies reflecting the type of the observation.observation
121value_as_numberNoFLOATThe observation result stored as a number. This is applicable to observations where the result is expressed as a numeric value.observation
122value_as_stringNoVARCHAR(60)The observation result stored as a string. This is applicable to observations where the result is expressed as verbatim text.observation
123value_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
124qualifier_concept_idNoINTEGERA foreign key to a Standard Concept ID for a qualifier (e.g., severity of drug-drug interaction alert)observation
125unit_concept_idNoINTEGERA foreign key to a Standard Concept ID of measurement units in the Standardized Vocabularies.observation
126provider_idNoINTEGERA foreign key to the provider in the PROVIDER table who was responsible for making the observation.observation
127visit_occurrence_idNoINTEGERA foreign key to the visit in the VISIT_OCCURRENCE table during which the observation was recorded.observation
128visit_detail_idNoINTEGERA foreign key to the visit in the VISIT_DETAIL table during which the observation was recorded.observation
129observation_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
130observation_source_concept_idNoINTEGERA foreign key to a Concept that refers to the code used in the source.observation
131unit_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
132qualifier_source_valueNoVARCHAR(50)The source value associated with a qualifier to characterize the observationobservation
133observation_period_idYesINTEGERA unique identifier for each observation period.observation_period
134person_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
135observation_period_start_dateYesDATEThe start date of the observation period for which data are available from the data source.observation_period
136observation_period_end_dateYesDATEThe end date of the observation period for which data are available from the data source.observation_period
137period_type_concept_idYesINTEGERA foreign key identifier to the predefined concept in the Standardized Vocabularies reflecting the source of the observation period informationobservation_period
138person_idYesINTEGERA unique identifier for each person.person
139gender_concept_idYesINTEGERA foreign key that refers to an identifier in the CONCEPT table for the unique gender of the person.person
140year_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
141month_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
142day_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
143birth_datetimeNoDATETIMEThe date and time of birth of the person.person
144race_concept_idYesINTEGERA foreign key that refers to an identifier in the CONCEPT table for the unique race of the person.person
145ethnicity_concept_idYesINTEGERA foreign key that refers to the standard concept identifier in the Standardized Vocabularies for the ethnicity of the person.person
146location_idNoINTEGERA foreign key to the place of residency for the person in the location table, where the detailed address information is stored.person
147provider_idNoINTEGERA foreign key to the primary care provider the person is seeing in the provider table.person
148care_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
149person_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
150gender_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
151gender_source_concept_idNoINTEGERA foreign key to the gender concept that refers to the code used in the source.person
152race_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
153race_source_concept_idNoINTEGERA foreign key to the race concept that refers to the code used in the source.person
154ethnicity_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
155ethnicity_source_concept_idNoINTEGERA foreign key to the ethnicity concept that refers to the code used in the source.person
156procedure_occurrence_idYesINTEGERA system-generated unique identifier for each Procedure Occurrence.procedure_occurrence
157person_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
158procedure_concept_idYesINTEGERA foreign key that refers to a standard procedure Concept identifier in the Standardized Vocabularies.procedure_occurrence
159procedure_dateYesDATEThe date on which the Procedure was performed.procedure_occurrence
160procedure_datetimeNoDATETIMEThe date and time on which the Procedure was performed.procedure_occurrence
161procedure_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.procedure_occurrence
162modifier_concept_idNoINTEGERA foreign key to a Standard Concept identifier for a modifier to the Procedure (e.g. bilateral)procedure_occurrence
163quantityNoINTEGERThe quantity of procedures ordered or administered.procedure_occurrence
164provider_idNoINTEGERA foreign key to the provider in the PROVIDER table who was responsible for carrying out the procedure.procedure_occurrence
165visit_occurrence_idNoINTEGERA foreign key to the Visit in the VISIT_OCCURRENCE table during which the Procedure was carried out.procedure_occurrence
166visit_detail_idNoINTEGERA foreign key to the Visit Detail in the VISIT_DETAIL table during which the Procedure was carried out.procedure_occurrence
167procedure_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
168procedure_source_concept_idNoINTEGERA foreign key to a Procedure Concept that refers to the code used in the source.procedure_occurrence
169modifier_source_valueNoVARCHAR(50)The source code for the qualifier as it appears in the source data.procedure_occurrence
170specimen_idYesINTEGERA unique identifier for each specimen.specimen
171person_idYesINTEGERA foreign key identifier to the Person for whom the Specimen is recorded.specimen
172specimen_concept_idYesINTEGERA foreign key referring to a Standard Concept identifier in the Standardized Vocabularies for the Specimen.specimen
173specimen_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
174specimen_dateYesDATEThe date the specimen was obtained from the Person.specimen
175specimen_datetimeNoDATETIMEThe date and time on the date when the Specimen was obtained from the person.specimen
176quantityNoFLOATThe amount of specimen collection from the person during the sampling procedure.specimen
177unit_concept_idNoINTEGERA foreign key to a Standard Concept identifier for the Unit associated with the numeric quantity of the Specimen collection.specimen
178anatomic_site_concept_idNoINTEGERA foreign key to a Standard Concept identifier for the anatomic location of specimen collection.specimen
179disease_status_concept_idNoINTEGERA foreign key to a Standard Concept identifier for the Disease Status of specimen collection.specimen
180specimen_source_idNoVARCHAR(50)The Specimen identifier as it appears in the source data.specimen
181specimen_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
182unit_source_valueNoVARCHAR(50)The information about the Unit as detailed in the source.specimen
183anatomic_site_source_valueNoVARCHAR(50)The information about the anatomic site as detailed in the source.specimen
184disease_status_source_valueNoVARCHAR(50)The information about the disease status as detailed in the source.specimen
185visit_detail_idYesINTEGERA unique identifier for each Person's visit or encounter at a healthcare provider.visit_detail
186person_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
187visit_concept_idYesINTEGERA foreign key that refers to a visit Concept identifier in the Standardized Vocabularies.visit_detail
188visit_start_dateYesDATEThe start date of the visit.visit_detail
189visit_start_datetimeNoDATETIMEThe date and time of the visit started.visit_detail
190visit_end_dateYesDATEThe end date of the visit. If this is a one-day visit the end date should match the start date.visit_detail
191visit_end_datetimeNoDATETIMEThe date and time of the visit end.visit_detail
192visit_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.visit_detail
193provider_idNoINTEGERA foreign key to the provider in the provider table who was associated with the visit.visit_detail
194care_site_idNoINTEGERA foreign key to the care site in the care site table that was visited.visit_detail
195visit_source_valueNoSTRING(50)The source code for the visit as it appears in the source data.visit_detail
196visit_source_concept_idNoINTEGERA foreign key to a Concept that refers to the code used in the source.visit_detail
197admitting_source_valueVarchar(50)NOThe source code for the admitting source as it appears in the source data.visit_detail
198admitting_source_concept_idIntegerNOA foreign key to the predefined concept in the Place of Service Vocabulary reflecting the admitting source for a visit.visit_detail
199discharge_to_source_valueVarchar(50)NOThe source code for the discharge disposition as it appears in the source data.visit_detail
200discharge_to_concept_idIntegerNOA foreign key to the predefined concept in the Place of Service Vocabulary reflecting the discharge disposition for a visit.visit_detail
201preceding_visit_detail_idIntegerNOA foreign key to the VISIT_DETAIL table of the visit immediately preceding this visitvisit_detail
202visit_detail_parent_idIntegerNOA foreign key to the VISIT_DETAIL table record to represent the immediate parent visit-detail record.visit_detail
203visit_occurrence_idIntegerYESA 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
204visit_occurrence_idYesINTEGERA unique identifier for each Person's visit or encounter at a healthcare provider.visit_occurrence
205person_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
206visit_concept_idYesINTEGERA foreign key that refers to a visit Concept identifier in the Standardized Vocabularies.visit_occurrence
207visit_start_dateYesDATEThe start date of the visit.visit_occurrence
208visit_start_datetimeNoDATETIMEThe date and time of the visit started.visit_occurrence
209visit_end_dateYesDATEThe end date of the visit. If this is a one-day visit the end date should match the start date.visit_occurrence
210visit_end_datetimeNoDATETIMEThe date and time of the visit end.visit_occurrence
211visit_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.visit_occurrence
212provider_idNoINTEGERA foreign key to the provider in the provider table who was associated with the visit.visit_occurrence
213care_site_idNoINTEGERA foreign key to the care site in the care site table that was visited.visit_occurrence
214visit_source_valueNoVARCHAR(50)The source code for the visit as it appears in the source data.visit_occurrence
215visit_source_concept_idNoINTEGERA foreign key to a Concept that refers to the code used in the source.visit_occurrence
216admitting_source_concept_idintegerNOA foreign key to the predefined concept in the Place of Service Vocabulary reflecting the admitting source for a visit.visit_occurrence
217admitting_source_valuevarchar(50)NOThe source code for the admitting source as it appears in the source data.visit_occurrence
218discharge_to_concept_idintegerNOA foreign key to the predefined concept in the Place of Service Vocabulary reflecting the discharge disposition for a visit.visit_occurrence
219discharge_to_source_valuevarchar(50)NOThe source code for the discharge disposition as it appears in the source data.visit_occurrence
220preceding_visit_occurrence_idintegerNOA foreign key to the VISIT_OCCURRENCE table of the visit immediately preceding this visitvisit_occurrence
221cohort_definition_idYesINTEGERA foreign key to a record in the COHORT_DEFINITION table containing relevant Cohort Definition information.cohort
222subject_idYesINTEGERA foreign key to the subject in the cohort. These could be referring to records in the PERSON, PROVIDER, VISIT_OCCURRENCE table.cohort
223cohort_start_dateYesDATEThe date when the Cohort Definition criteria for the Person, Provider or Visit first match.cohort
224cohort_end_dateYesDATEThe date when the Cohort Definition criteria for the Person, Provider or Visit no longer match or the Cohort membership was terminated.cohort
225cohort_definition_idYesINTEGERA foreign key to a record in the [COHORT_DEFINITION](https://github.com/OHDSI/CommonDataModel/wiki/COHORT_DEFINITION) table containing relevant Cohort Definition information.cohort_attribute
226subject_idYesINTEGERA foreign key to the subject in the Cohort. These could be referring to records in the PERSON, PROVIDER, VISIT_OCCURRENCE table.cohort_attribute
227cohort_start_dateYesDATEThe date when the Cohort Definition criteria for the Person, Provider or Visit first match.cohort_attribute
228cohort_end_dateYesDATEThe date when the Cohort Definition criteria for the Person, Provider or Visit no longer match or the Cohort membership was terminated.cohort_attribute
229attribute_definition_idYesINTEGERA foreign key to a record in the [ATTRIBUTE_DEFINITION](https://github.com/OHDSI/CommonDataModel/wiki/ATTRIBUTE_DEFINITION) table containing relevant Attribute Definition information.cohort_attribute
230value_as_numberNoFLOATThe attribute result stored as a number. This is applicable to attributes where the result is expressed as a numeric value.cohort_attribute
231value_as_concept_idNoINTEGERThe attribute result stored as a Concept ID. This is applicable to attributes where the result is expressed as a categorical value.cohort_attribute
232condition_era_idYesINTEGERA unique identifier for each Condition Era.condition_era
233person_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
234condition_concept_idYesINTEGERA foreign key that refers to a standard Condition Concept identifier in the Standardized Vocabularies.condition_era
235condition_era_start_dateYesDATEThe 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
236condition_era_end_dateYesDATEThe 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
237condition_occurrence_countNoINTEGERThe number of individual Condition Occurrences used to construct the condition era.condition_era
238dose_era_idYesINTEGERA unique identifier for each Dose Era.dose_era
239person_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
240drug_concept_idYesINTEGERA foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the active Ingredient Concept.dose_era
241unit_concept_idYesINTEGERA foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the unit concept.dose_era
242dose_valueYesFLOATThe numeric value of the dose.dose_era
243dose_era_start_dateYesDATEThe 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
244dose_era_end_dateYesDATEThe 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
245drug_era_idYesINTEGERA unique identifier for each Drug Era.drug_era
246person_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
247drug_concept_idYesINTEGERA foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the Ingredient Concept.drug_era
248drug_era_start_dateYesDATEThe 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
249drug_era_end_dateYesDATEThe 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
250drug_exposure_countNoINTEGERThe number of individual Drug Exposure occurrences used to construct the Drug Era.drug_era
251gap_daysNoINTEGERThe number of days that are not covered by DRUG_EXPOSURE records that were used to make up the era record.drug_era
252cost_idYesINTEGERA unique identifier for each COST record.cost
253cost_event_idYesINTEGERA foreign key identifier to the event (e.g. Measurement, Procedure, Visit, Drug Exposure, etc) record for which cost data are recorded.cost
254cost_domain_idYesVARCHAR(20)The concept representing the domain of the cost event, from which the corresponding table can be inferred that contains the entity for which cost information is recorded.cost
255cost_type_concept_idYesINTEGERA foreign key identifier to a concept in the CONCEPT table for the provenance or the source of the COST data: Calculated from insurance claim information, provider revenue, calculated from cost-to-charge ratio, reported from accounting database, etc.cost
256currency_concept_idNoINTEGERA foreign key identifier to the concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar.cost
257total_chargeNoFLOATThe total amount charged by some provider of goods or services (e.g. hospital, physician pharmacy, dme provider) to payers (insurance companies, the patient).cost
258total_costNoFLOATThe cost incurred by the provider of goods or services.cost
259total_paidNoFLOATThe total amount actually paid from all payers for goods or services of the provider.cost
260paid_by_payerNoFLOATThe amount paid by the Payer for the goods or services.cost
261paid_by_patientNoFLOATThe total amount paid by the Person as a share of the expenses.cost
262paid_patient_copayNoFLOATThe amount paid by the Person as a fixed contribution to the expenses.cost
263paid_patient_coinsuranceNoFLOATThe amount paid by the Person as a joint assumption of risk. Typically, this is a percentage of the expenses defined by the Payer Plan after the Person's deductible is exceeded.cost
264paid_patient_deductibleNoFLOATThe amount paid by the Person that is counted toward the deductible defined by the Payer Plan. paid_patient_deductible does contribute to the paid_by_patient variable.cost
265paid_by_primaryNoFLOATThe amount paid by a primary Payer through the coordination of benefits.cost
266paid_ingredient_costNoFLOATThe amount paid by the Payer to a pharmacy for the drug, excluding the amount paid for dispensing the drug. paid_ingredient_cost contributes to the paid_by_payer field if this field is populated with a nonzero value.cost
267paid_dispensing_feeNoFLOATThe amount paid by the Payer to a pharmacy for dispensing a drug, excluding the amount paid for the drug ingredient. paid_dispensing_fee contributes to the paid_by_payer field if this field is populated with a nonzero value.cost
268payer_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
269amount_allowedNoFLOATThe contracted amount agreed between the payer and provider.cost
270revenue_code_concept_idNoINTEGERA foreign key referring to a Standard Concept ID in the Standardized Vocabularies for Revenue codes.cost
271revenue_code_source_valueNoVARCHAR(50)The source code for the Revenue code as it appears in the source data, stored here for reference.cost
272drg_concept_idNoINTEGERA foreign key to the predefined concept in the DRG Vocabulary reflecting the DRG for a visit.cost
273drg_source_valueNoVARCHAR(3)The 3-digit DRG source code as it appears in the source data.cost
274payer_plan_period_idYesINTEGERA identifier for each unique combination of payer, plan, family code and time span.payer_plan_period
275person_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
276payer_plan_period_start_dateYesDATEThe start date of the payer plan period.payer_plan_period
277payer_plan_period_end_dateYesDATEThe end date of the payer plan period.payer_plan_period
278payer_concept_idNoINTEGERA foreign key that refers to a standard Payer concept identifier in the Standarized Vocabulariespayer_plan_period
279payer_source_valueNoVARCHAR(50)The source code for the payer as it appears in the source data.payer_plan_period
280payer_source_concept_idNoINTEGERA foreign key to a payer concept that refers to the code used in the source.payer_plan_period
281plan_concept_idNoINTEGERA foreign key that refers to a standard plan concept identifier that represents the health benefit plan in the Standardized Vocabulariespayer_plan_period
282plan_source_valueNoVARCHAR(50)The source code for the Person's health benefit plan as it appears in the source data.payer_plan_period
283plan_source_concept_idNoINTEGERA foreign key to a plan concept that refers to the plan code used in the source data.payer_plan_period
284sponsor_concept_idNoINTEGERA foreign key that refers to a concept identifier that represents the sponsor in the Standardized Vocabularies.payer_plan_period
285sponsor_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
286sponsor_source_concept_idNoINTEGERA foreign key to a sponsor concept that refers to the sponsor code used in the source data.payer_plan_period
287family_source_valueNoVARCHAR(50)The source code for the Person's family as it appears in the source data.payer_plan_period
288stop_reason_concept_idNoINTEGERA foreign key that refers to a standard termination reason that represents the reason for the termination in the Standardized Vocabularies.payer_plan_period
289stop_reason_source_valueNoVARCHAR(50)The reason for stop-coverage as it appears in the source data.payer_plan_period
290stop_reason_source_concept_idNoINTEGERA foreign key to a stop-coverage concept that refers to the code used in the source.payer_plan_period
291care_site_idYesINTEGERA unique identifier for each Care Site.care_site
292care_site_nameNoVARCHAR(255)The verbatim description or name of the Care Site as in data sourcecare_site
293place_of_service_concept_idNoINTEGERA foreign key that refers to a Place of Service Concept ID in the Standardized Vocabularies.care_site
294location_idNoINTEGERA foreign key to the geographic Location in the LOCATION table, where the detailed address information is stored.care_site
295care_site_source_valueNoVARCHAR(50)The identifier for the Care Site in the source data, stored here for reference.care_site
296place_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
297location_idYesINTEGERA unique identifier for each geographic location.location
298address_1NoVARCHAR(50)The address field 1, typically used for the street address, as it appears in the source data.location
299address_2NoVARCHAR(50)The address field 2, typically used for additional detail such as buildings, suites, floors, as it appears in the source data.location
300cityNoVARCHAR(50)The city field as it appears in the source data.location
301stateNoVARCHAR(2)The state field as it appears in the source data.location
302zipNoVARCHAR(9)The zip or postal code.location
303countyNoVARCHAR(20)The county.location
304location_source_valueNoVARCHAR(50)The verbatim information that is used to uniquely identify the location as it appears in the source data.location
305provider_idYesINTEGERA unique identifier for each Provider.provider
306provider_nameNoVARCHAR(255)A description of the Provider.provider
307npiNoVARCHAR(20)The National Provider Identifier (NPI) of the provider.provider
308deaNoVARCHAR(20)The Drug Enforcement Administration (DEA) number of the provider.provider
309specialty_concept_idNoINTEGERA foreign key to a Standard Specialty Concept ID in the Standardized Vocabularies.provider
310care_site_idNoINTEGERA foreign key to the main Care Site where the provider is practicing.provider
311year_of_birthNoINTEGERThe year of birth of the Provider.provider
312gender_concept_idNoINTEGERThe gender of the Provider.provider
313provider_source_valueNoVARCHAR(50)The identifier used for the Provider in the source data, stored here for reference.provider
314specialty_source_valueNoVARCHAR(50)The source code for the Provider specialty as it appears in the source data, stored here for reference.provider
315specialty_source_concept_idNoINTEGERA foreign key to a Concept that refers to the code used in the source.provider
316gender_source_valueNoVARCHAR(50)The gender code for the Provider as it appears in the source data, stored here for reference.provider
317gender_source_concept_idNoINTEGERA foreign key to a Concept that refers to the code used in the source.provider
318cdm_source_nameYesVARCHAR(255)The full name of the sourcecdm_source
319cdm_source_abbreviationNoVARCHAR(25)An abbreviation of the namecdm_source
320cdm_holderNoVARCHAR(255)The name of the organization responsible for the development of the CDM instancecdm_source
321source_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
322source_documentation_referenceNoVARCHAR(255)URL or other external reference to location of source documentationcdm_source
323cdm_etl _referenceNoVARCHAR(255)URL or other external reference to location of ETL specification documentation and ETL source codecdm_source
324source_release_dateNoDATEThe date for which the source data are most current, such as the last day of data capturecdm_source
325cdm_release_dateNoDATEThe date when the CDM was instantiatedcdm_source
326cdm_versionNoVARCHAR(10)The version of CDM usedcdm_source
327vocabulary_versionNoVARCHAR(20)The version of the vocabulary usedcdm_source
328metadata_concept_idYesINTEGERA foreign key that refers to a Standard Metadata Concept identifier in the Standardized Vocabularies.metadata
329metadata_type_concept_idYesINTEGERA foreign key that refers to a Standard Type Concept identifier in the Standardized Vocabularies.metadata
330nameYesVARCHAR(250)The name of the Concept stored in metadata_concept_id or a description of the data being stored.metadata
331value_as_stringNoNVARCHARThe metadata value stored as a string.metadata
332value_as_concept_idNoINTEGERA foreign key to a metadata value stored as a Concept ID.metadata
333metadata dateNoDATEThe date associated with the metadatametadata
334metadata_datetimeNoDATETIMEThe date and time associated with the metadatametadata
335attribute_definition_idYesINTEGERA unique identifier for each Attribute.attribute_definition
336attribute_nameYesVARCHAR(255)A short description of the Attribute.attribute_definition
337attribute_descriptionNoVARCHAR(MAX)A complete description of the Attribute definitionattribute_definition
338attribute_type_concept_idYesINTEGERType defining what kind of Attribute Definition the record represents and how the syntax may be executedattribute_definition
339attribute_syntaxNoVARCHAR(MAX)Syntax or code to operationalize the Attribute definitionattribute_definition
340cohort_definition_idYesINTEGERA unique identifier for each Cohort.cohort_definition
341cohort_definition_nameYesVARCHAR(255)A short description of the Cohort.cohort_definition
342cohort_definition_descriptionNoVARCHAR(MAX)A complete description of the Cohort definitioncohort_definition
343definition_type_concept_idYesINTEGERType defining what kind of Cohort Definition the record represents and how the syntax may be executedcohort_definition
344cohort_definition_syntaxNoVARCHAR(MAX)Syntax or code to operationalize the Cohort definitioncohort_definition
345subject_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
346cohort_instantiation_dateNoDATEA date to indicate when the Cohort was instantiated in the COHORT tablecohort_definition
347concept_idYesINTEGERA unique identifier for each Concept across all domains.concept
348concept_nameYesVARCHAR(255)An unambiguous, meaningful and descriptive name for the Concept.concept
349domain_idYesVARCHAR(20)A foreign key to the [DOMAIN](https://github.com/OHDSI/CommonDataModel/wiki/DOMAIN) table the Concept belongs to.concept
350vocabulary_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
351concept_class_idYesVARCHAR(20)The attribute or concept class of the Concept. Examples are 'Clinical Drug', 'Ingredient', 'Clinical Finding' etc.concept
352standard_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
353concept_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
354valid_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
355valid_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
356invalid_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
357ancestor_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
358descendant_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
359min_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
360max_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
361concept_class_idYesVARCHAR(20)A unique key for each class.concept_class
362concept_class_nameYesVARCHAR(255)The name describing the Concept Class, e.g. "Clinical Finding", "Ingredient", etc.concept_class
363concept_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
364concept_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
365concept_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
366relationship_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
367valid_start_dateYesDATEThe date when the instance of the Concept Relationship is first recorded.concept_relationship
368valid_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
369invalid_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
370concept_idYesINTEGERA foreign key to the Concept in the CONCEPT table.concept_synonym
371concept_synonym_nameYesVARCHAR(1000)The alternative name for the Concept.concept_synonym
372language_concept_idYesINTEGERA foreign key to a Concept representing the language.concept_synonym
373domain_idYesVARCHAR(20)A unique key for each domain.domain
374domain_nameYesVARCHAR(255)The name describing the Domain, e.g. "Condition", "Procedure", "Measurement" etc.domain
375domain_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
376drug_concept_idYesINTEGERA foreign key to the Concept in the CONCEPT table representing the identifier for Branded Drug or Clinical Drug Concept.drug_strength
377ingredient_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
378amount_valueNoFLOATThe numeric value associated with the amount of active ingredient contained within the product.drug_strength
379amount_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
380numerator_valueNoFLOATThe numeric value associated with the concentration of the active ingredient contained in the productdrug_strength
381numerator_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
382denominator_valueNoFLOATThe amount of total liquid (or other divisible product, such as ointment, gel, spray, etc.).drug_strength
383denominator_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
384box_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
385valid_start_dateYesDATEThe date when the Concept was first recorded. The default value is 1-Jan-1970.drug_strength
386valid_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
387invalid_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
388relationship_idYesVARCHAR(20)The type of relationship captured by the relationship record.relationship
389relationship_nameYesVARCHAR(255)The text that describes the relationship type.relationship
390is_hierarchicalYesVARCHAR(1)Defines whether a relationship defines concepts into classes or hierarchies. Values are 1 for hierarchical relationship or 0 if not.relationship
391defines_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
392reverse_relationship_idYesVARCHAR(20)The identifier for the relationship used to define the reverse relationship between two concepts.relationship
393relationship_concept_idYesINTEGERA foreign key that refers to an identifier in the CONCEPT table for the unique relationship concept.relationship
394source_codeYesVARCHAR(50)The source code being translated into a Standard Concept.source_to_concept_map
395source_concept_idYesINTEGERA foreign key to the Source Concept that is being translated into a Standard Concept.source_to_concept_map
396source_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
397source_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
398target_concept_idYesINTEGERA foreign key to the target Concept to which the source code is being mapped.source_to_concept_map
399target_vocabulary_idYesVARCHAR(20)A foreign key to the VOCABULARY table defining the vocabulary of the target Concept.source_to_concept_map
400valid_start_dateYesDATEThe date when the mapping instance was first recorded.source_to_concept_map
401valid_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
402invalid_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
403vocabulary_idYesVARCHAR(20)A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit.vocabulary
404vocabulary_nameYesVARCHAR(255)The name describing the vocabulary, for example "International Classification of Diseases, Ninth Revision, Clinical Modification, Volume 1 and 2 (NCHS)" etc.vocabulary
405vocabulary_referenceYesVARCHAR(255)External reference to documentation or available download of the about the vocabulary.vocabulary
406vocabulary_versionYesVARCHAR(255)Version of the Vocabulary as indicated in the source.vocabulary
407vocabulary_concept_idYesINTEGERA foreign key that refers to a standard concept identifier in the CONCEPT table for the Vocabulary the VOCABULARY record belongs to.vocabulary