OMOP/inst/csv/OMOP_CDMv5.3_Field_Level.csv

106 KiB

1cdmTableNamecdmFieldNameisRequiredcdmDatatypeuserGuidanceetlConventionsisPrimaryKeyisForeignKeyfkTableNamefkFieldNamefkDomainfkClassunique DQ identifiers
2PERSONperson_idYesintegerIt is assumed that every person with a different unique identifier is in fact a different person and should be treated independently.Any person linkage that needs to occur to uniquely identify Persons ought to be done prior to writing this table. This identifier can be the original id from the source data provided if it is an integer, otherwise it can be an autogenerated number.YesNo
3PERSONgender_concept_idYesintegerThis field is meant to capture the biological sex at birth of the Person. This field should not be used to study gender identity issues.Use the gender or sex value present in the data under the assumption that it is the biological sex at birth. If the source data captures gender identity it should be stored in the [OBSERVATION](https://ohdsi.github.io/CommonDataModel/cdm531.html#observation) table. [Accepted gender concepts](http://athena.ohdsi.org/search-terms/terms?domain=Gender&standardConcept=Standard&page=1&pageSize=15&query=)NoYesCONCEPTCONCEPT_IDGender
4PERSONyear_of_birthYesintegerCompute age using year_of_birth.For data sources with date of birth, the year should be extracted. For data sources where the year of birth is not available, the approximate year of birth could be derived based on age group categorization, if available.NoNo
5PERSONmonth_of_birthNointegerFor data sources that provide the precise date of birth, the month should be extracted and stored in this field.NoNo
6PERSONday_of_birthNointegerFor data sources that provide the precise date of birth, the day should be extracted and stored in this field.NoNo
7PERSONbirth_datetimeNodatetimeThis field is not required but highly encouraged. For data sources that provide the precise datetime of birth, that value should be stored in this field. If birth_datetime is not provided in the source, use the following logic to infer the date: If day_of_birth is null and month_of_birth is not null then use the first of the month in that year. If month_of_birth is null or if day_of_birth AND month_of_birth are both null and the person has records during their year of birth then use the date of the earliest record, otherwise use the 15th of June of that year. If time of birth is not given use midnight (00:00:0000).NoNo
8PERSONrace_concept_idYesintegerThis field captures race or ethnic background of the person.Only use this field if you have information about race or ethnic background. The Vocabulary contains Concepts about the main races and ethnic backgrounds in a hierarchical system. Due to the imprecise nature of human races and ethnic backgrounds, this is not a perfect system. Mixed races are not supported. If a clear race or ethnic background cannot be established, use Concept_Id 0. [Accepted Race Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Race&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDRace
9PERSONethnicity_concept_idYesintegerThis field captures Ethnicity as defined by the Office of Management and Budget (OMB) of the US Government: it distinguishes only between "Hispanic" and "Not Hispanic". Races and ethnic backgrounds are not stored here.Only use this field if you have US-based data and a source of this information. Do not attempt to infer Ethnicity from the race or ethnic background of the Person. [Accepted ethnicity concepts](http://athena.ohdsi.org/search-terms/terms?domain=Ethnicity&standardConcept=Standard&page=1&pageSize=15&query=)NoYesCONCEPTCONCEPT_IDEthnicity
10PERSONlocation_idNointegerThe location refers to the physical address of the person. This field should capture the last known location of the person. Put the location_id from the [LOCATION](https://ohdsi.github.io/CommonDataModel/cdm531.html#location) table here that represents the most granular location information for the person. This could represent anything from postal code or parts thereof, state, or county for example. Since many databases contain deidentified data, it is common that the precision of the location is reduced to prevent re-identification. This field should capture the last known location. NoYesLOCATIONLOCATION_ID
11PERSONprovider_idNointegerThe Provider refers to the last known primary care provider (General Practitioner).Put the provider_id from the [PROVIDER](https://ohdsi.github.io/CommonDataModel/cdm531.html#provider) table of the last known general practitioner of the person. If there are multiple providers, it is up to the ETL to decide which to put here.NoYesPROVIDERPROVIDER_ID
12PERSONcare_site_idNointegerThe Care Site refers to where the Provider typically provides the primary care.NoYesCARE_SITECARE_SITE_ID
13PERSONperson_source_valueNovarchar(50)Use this field to link back to persons in the source data. This is typically used for error checking of ETL logic.Some use cases require the ability to link back to persons in the source data. This field allows for the storing of the person value as it appears in the source. This field is not required but strongly recommended.NoNo
14PERSONgender_source_valueNovarchar(50)This field is used to store the biological sex of the person from the source data. It is not intended for use in standard analytics but for reference only.Put the biological sex of the person as it appears in the source data.NoNo
15PERSONgender_source_concept_idNointegerDue to the small number of options, this tends to be zero.If the source data codes biological sex in a non-standard vocabulary, store the concept_id here.NoYesCONCEPTCONCEPT_ID
16PERSONrace_source_valueNovarchar(50)This field is used to store the race of the person from the source data. It is not intended for use in standard analytics but for reference only.Put the race of the person as it appears in the source data.NoNo
17PERSONrace_source_concept_idNointegerDue to the small number of options, this tends to be zero.If the source data codes race in an OMOP supported vocabulary store the concept_id here.NoYesCONCEPTCONCEPT_ID
18PERSONethnicity_source_valueNovarchar(50)This field is used to store the ethnicity of the person from the source data. It is not intended for use in standard analytics but for reference only.If the person has an ethnicity other than the OMB standard of "Hispanic" or "Not Hispanic" store that value from the source data here.NoNo
19PERSONethnicity_source_concept_idNointegerDue to the small number of options, this tends to be zero.If the source data codes ethnicity in an OMOP supported vocabulary, store the concept_id here.NoYesCONCEPTCONCEPT_ID
20OBSERVATION_PERIODobservation_period_idYesintegerA Person can have multiple discrete Observation Periods which are identified by the Observation_Period_Id.Assign a unique observation_period_id to each discrete Observation Period for a Person.YesNo
21OBSERVATION_PERIODperson_idYesintegerThe Person ID of the PERSON record for which the Observation Period is recorded.NoYesPERSONPERSON_ID
22OBSERVATION_PERIODobservation_period_start_dateYesdateUse this date to determine the start date of the Observation Period.It is often the case that the idea of Observation Periods does not exist in source data. In those cases, the observation_period_start_date can be inferred as the earliest Event date available for the Person. In insurance claim data, the Observation Period can be considered as the time period the Person is enrolled with a payer. If a Person switches plans but stays with the same payer, and therefore capturing of data continues, that change would be captured in [PAYER_PLAN_PERIOD](https://ohdsi.github.io/CommonDataModel/cdm531.html#payer_plan_period).NoNo
23OBSERVATION_PERIODobservation_period_end_dateYesdateUse this date to determine the end date of the period for which we can assume that all events for a Person are recorded.It is often the case that the idea of Observation Periods does not exist in source data. In those cases, the observation_period_end_date can be inferred as the last Event date available for the Person. In insurance claim data, the Observation Period can be considered as the time period the Person is enrolled with a payer.NoNo
24OBSERVATION_PERIODperiod_type_concept_idYesintegerThis field can be used to determine the provenance of the Observation Period as in whether the period was determined from an insurance enrollment file, EHR healthcare encounters, or other sources.Choose the observation_period_type_concept_id that best represents how the period was determined. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDType Concept
25VISIT_OCCURRENCEvisit_occurrence_idYesintegerUse this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit.This should be populated by creating a unique identifier for each unique interaction between a person and the healthcare system where the person receives a medical good or service over a span of time.YesNo
26VISIT_OCCURRENCEperson_idYesintegerNoYesPERSONPERSON_ID
27VISIT_OCCURRENCEvisit_concept_idYesintegerThis field contains a concept id representing the kind of visit, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain.Populate this field based on the kind of visit that took place for the person. For example this could be "Inpatient Visit", "Outpatient Visit", "Ambulatory Visit", etc. This table will contain standard concepts in the Visit domain. These concepts are arranged in a hierarchical structure to facilitate cohort definitions by rolling up to generally familiar Visits adopted in most healthcare systems worldwide. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDVisit
28VISIT_OCCURRENCEvisit_start_dateYesdateFor inpatient visits, the start date is typically the admission date. For outpatient visits the start date and end date will be the same.When populating VISIT_START_DATE, you should think about the patient experience to make decisions on how to define visits. In the case of an inpatient visit this should be the date the patient was admitted to the hospital or institution. In all other cases this should be the date of the patient-provider interaction.NoNo
29VISIT_OCCURRENCEvisit_start_datetimeNodatetimeIf no time is given for the start date of a visit, set it to midnight (00:00:0000).NoNo
30VISIT_OCCURRENCEvisit_end_dateYesdateFor inpatient visits the end date is typically the discharge date.Visit end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them: - Outpatient Visit: visit_end_datetime = visit_start_datetime - Emergency Room Visit: visit_end_datetime = visit_start_datetime - Inpatient Visit: Usually there is information about discharge. If not, you should be able to derive the end date from the sudden decline of activity or from the absence of inpatient procedures/drugs. - Non-hospital institution Visits: Particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs. For Inpatient Visits ongoing at the date of ETL, put date of processing the data into visit_end_datetime and visit_type_concept_id with 32220 "Still patient" to identify the visit as incomplete. - All other Visits: visit_end_datetime = visit_start_datetime. If this is a one-day visit the end date should match the start date.NoNo
31VISIT_OCCURRENCEvisit_end_datetimeNodatetimeIf no time is given for the end date of a visit, set it to midnight (00:00:0000).NoNo
32VISIT_OCCURRENCEvisit_type_concept_idYesIntegerUse this field to understand the provenance of the visit record, or where the record comes from.Populate this field based on the provenance of the visit record, as in whether it came from an EHR record or billing claim. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDType Concept
33VISIT_OCCURRENCEprovider_idNointegerThere will only be one provider per visit record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). If there are multiple providers associated with a visit in the source, this can be reflected in the event tables (CONDITION_OCCURRENCE, PROCEDURE_OCCURRENCE, etc.) or in the VISIT_DETAIL table.If there are multiple providers associated with a visit, you will need to choose which one to put here. The additional providers can be stored in the [VISIT_DETAIL](https://ohdsi.github.io/CommonDataModel/cdm531.html#visit_detail) table.NoYesPROVIDERPROVIDER_ID
34VISIT_OCCURRENCEcare_site_idNointegerThis field provides information about the Care Site where the Visit took place.There should only be one Care Site associated with a Visit.NoYesCARE_SITECARE_SITE_ID
35VISIT_OCCURRENCEvisit_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the kind of visit that took place (inpatient, outpatient, emergency, etc.)If there is information about the kind of visit in the source data that value should be stored here. If a visit is an amalgamation of visits from the source then use a hierarchy to choose the visit source value, such as IP -> ER-> OP. This should line up with the logic chosen to determine how visits are created.NoNo
36VISIT_OCCURRENCEvisit_source_concept_idNointegerIf the visit source value is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.NoYesCONCEPTCONCEPT_ID
37VISIT_OCCURRENCEadmitting_source_concept_idNointegerUse this field to determine where the patient was admitted from. This concept is part of the visit domain and can indicate if a patient was admitted to the hospital from a long-term care facility, for example.If available, map the admitted_from_source_value to a standard concept in the visit domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDVisit
38VISIT_OCCURRENCEadmitting_source_valueNovarchar(50)This information may be called something different in the source data but the field is meant to contain a value indicating where a person was admitted from. Typically this applies only to visits that have a length of stay, like inpatient visits or long-term care visits.NoNo
39VISIT_OCCURRENCEdischarge_to_concept_idNointegerUse this field to determine where the patient was discharged to after a visit. This concept is part of the visit domain and can indicate if a patient was discharged to home or sent to a long-term care facility, for example.If available, map the discharge_to_source_value to a standard concept in the visit domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDVisit
40VISIT_OCCURRENCEdischarge_to_source_valueNovarchar(50)This information may be called something different in the source data but the field is meant to contain a value indicating where a person was discharged to after a visit, as in they went home or were moved to long-term care. Typically this applies only to visits that have a length of stay of a day or more.NoNo
41VISIT_OCCURRENCEpreceding_visit_occurrence_idNointegerUse this field to find the visit that occurred for the person prior to the given visit. There could be a few days or a few years in between.This field can be used to link a visit immediately preceding the current visit. Note this is not symmetrical, and there is no such thing as a "following_visit_id".NoYesVISIT_OCCURRENCEVISIT_OCCURRENCE_ID
42VISIT_DETAILvisit_detail_idYesintegerUse this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit detail.This should be populated by creating a unique identifier for each unique interaction between a person and the healthcare system where the person receives a medical good or service over a span of time.YesNo
43VISIT_DETAILperson_idYesintegerNoYesPERSONPERSON_ID
44VISIT_DETAILvisit_detail_concept_idYesintegerThis field contains a concept id representing the kind of visit detail, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain.Populate this field based on the kind of visit that took place for the person. For example this could be "Inpatient Visit", "Outpatient Visit", "Ambulatory Visit", etc. This table will contain standard concepts in the Visit domain. These concepts are arranged in a hierarchical structure to facilitate cohort definitions by rolling up to generally familiar Visits adopted in most healthcare systems worldwide. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDVisit
45VISIT_DETAILvisit_detail_start_dateYesdateThis is the date of the start of the encounter. This may or may not be equal to the date of the Visit the Visit Detail is associated with.When populating VISIT_DETAIL_START_DATE, you should think about the patient experience to make decisions on how to define visits. Most likely this should be the date of the patient-provider interaction.NoNo
46VISIT_DETAILvisit_detail_start_datetimeNodatetimeIf no time is given for the start date of a visit, set it to midnight (00:00:0000).NoNo
47VISIT_DETAILvisit_detail_end_dateYesdateThis the end date of the patient-provider interaction.Visit Detail end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them:<br> - Outpatient Visit Detail: visit_detail_end_datetime = visit_detail_start_datetime - Emergency Room Visit Detail: visit_detail_end_datetime = visit_detail_start_datetime - Inpatient Visit Detail: Usually there is information about discharge. If not, you should be able to derive the end date from the sudden decline of activity or from the absence of inpatient procedures/drugs. - Non-hospital institution Visit Details: Particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs.<br> For Inpatient Visit Details ongoing at the date of ETL, put date of processing the data into visit_detai_end_datetime and visit_detail_type_concept_id with 32220 "Still patient" to identify the visit as incomplete. All other Visits Details: visit_detail_end_datetime = visit_detail_start_datetime. NoNo
48VISIT_DETAILvisit_detail_end_datetimeNodatetimeIf no time is given for the end date of a visit, set it to midnight (00:00:0000).NoNo
49VISIT_DETAILvisit_detail_type_concept_idYesintegerUse this field to understand the provenance of the visit detail record, or where the record comes from.Populate this field based on the provenance of the visit detail record, as in whether it came from an EHR record or billing claim. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDType Concept
50VISIT_DETAILprovider_idNointegerThere will only be one provider per **visit** record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). This is a typical reason for leveraging the VISIT_DETAIL table as even though each VISIT_DETAIL record can only have one provider, there is no limit to the number of VISIT_DETAIL records that can be associated to a VISIT_OCCURRENCE record.The additional providers associated to a Visit can be stored in this table where each VISIT_DETAIL record represents a different provider.NoYesPROVIDERPROVIDER_ID
51VISIT_DETAILcare_site_idNointegerThis field provides information about the Care Site where the Visit Detail took place.There should only be one Care Site associated with a Visit Detail.NoYesCARE_SITECARE_SITE_ID
52VISIT_DETAILvisit_detail_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the kind of visit detail that took place (inpatient, outpatient, emergency, etc.)If there is information about the kind of visit detail in the source data that value should be stored here. If a visit is an amalgamation of visits from the source then use a hierarchy to choose the VISIT_DETAIL_SOURCE_VALUE, such as IP -> ER-> OP. This should line up with the logic chosen to determine how visits are created.NoNo
53VISIT_DETAILvisit_detail_source_concept_idNoIntegerIf the VISIT_DETAIL_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.NoYesCONCEPTCONCEPT_ID
54VISIT_DETAILadmitting_source_valueNoVarchar(50)This information may be called something different in the source data but the field is meant to contain a value indicating where a person was admitted from. Typically this applies only to visits that have a length of stay, like inpatient visits or long-term care visits.NoNo
55VISIT_DETAILadmitting_source_concept_idNoIntegerUse this field to determine where the patient was admitted from. This concept is part of the visit domain and can indicate if a patient was admitted to the hospital from a long-term care facility, for example.If available, map the admitted_from_source_value to a standard concept in the visit domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDVisit
56VISIT_DETAILdischarge_to_source_valueNoVarchar(50)This information may be called something different in the source data but the field is meant to contain a value indicating where a person was discharged to after a visit, as in they went home or were moved to long-term care. Typically this applies only to visits that have a length of stay of a day or more.NoNo
57VISIT_DETAILdischarge_to_concept_idNointegerUse this field to determine where the patient was discharged to after a visit detail record. This concept is part of the visit domain and can indicate if a patient was discharged to home or sent to a long-term care facility, for example.If available, map the DISCHARGE_TO_SOURCE_VALUE to a Standard Concept in the Visit domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDVisit
58VISIT_DETAILpreceding_visit_detail_idNointegerUse this field to find the visit detail that occurred for the person prior to the given visit detail record. There could be a few days or a few years in between.The PRECEDING_VISIT_DETAIL_ID can be used to link a visit immediately preceding the current Visit Detail. Note this is not symmetrical, and there is no such thing as a "following_visit_id".NoYesVISIT_DETAILVISIT_DETAIL_ID
59VISIT_DETAILvisit_detail_parent_idNointegerUse this field to find the visit detail that subsumes the given visit detail record. This is used in the case that a visit detail record needs to be nested beyond the VISIT_OCCURRENCE/VISIT_DETAIL relationship.If there are multiple nested levels to how Visits are represented in the source, the VISIT_DETAIL_PARENT_ID can be used to record this relationship. NoYesVISIT_DETAILVISIT_DETAIL_ID
60VISIT_DETAILvisit_occurrence_idYesintegerUse this field to link the VISIT_DETAIL record to its VISIT_OCCURRENCE.Put the VISIT_OCCURRENCE_ID that subsumes the VISIT_DETAIL record here.NoYesVISIT_OCCURRENCEVISIT_OCCURRENCE_ID
61CONDITION_OCCURRENCEcondition_occurrence_idYesintegerThe unique key given to a condition record for a person. Refer to the ETL for how duplicate conditions during the same visit were handled.Each instance of a condition present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same condition within the same visit. It is valid to keep these duplicates and assign them individual, unique, CONDITION_OCCURRENCE_IDs, though it is up to the ETL how they should be handled.YesNo
62CONDITION_OCCURRENCEperson_idYesintegerThe PERSON_ID of the PERSON for whom the condition is recorded.NoYesPERSONPERSON_ID
63CONDITION_OCCURRENCEcondition_concept_idYesintegerThe CONDITION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a conditionThe CONCEPT_ID that the CONDITION_SOURCE_VALUE maps to. Only records whose source values map to concepts with a domain of "Condition" should go in this table. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Condition&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDCondition
64CONDITION_OCCURRENCEcondition_start_dateYesdateUse this date to determine the start date of the conditionMost often data sources do not have the idea of a start date for a condition. Rather, if a source only has one date associated with a condition record it is acceptable to use that date for both the CONDITION_START_DATE and the CONDITION_END_DATE.NoNo
65CONDITION_OCCURRENCEcondition_start_datetimeNodatetimeIf a source does not specify datetime the convention is to set the time to midnight (00:00:0000)NoNo
66CONDITION_OCCURRENCEcondition_end_dateNodateUse this date to determine the end date of the conditionMost often data sources do not have the idea of a start date for a condition. Rather, if a source only has one date associated with a condition record it is acceptable to use that date for both the CONDITION_START_DATE and the CONDITION_END_DATE.NoNo
67CONDITION_OCCURRENCEcondition_end_datetimeNodatetimeIf a source does not specify datetime the convention is to set the time to midnight (00:00:0000)NoNo
68CONDITION_OCCURRENCEcondition_type_concept_idYesintegerThis field can be used to determine the provenance of the Condition record, as in whether the condition was from an EHR system, insurance claim, registry, or other sources.Choose the CONDITION_TYPE_CONCEPT_ID that best represents the provenance of the record. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDType Concept
69CONDITION_OCCURRENCEcondition_status_concept_idNointegerThis concept represents the point during the visit the diagnosis was given (admitting diagnosis, final diagnosis), whether the diagnosis was determined due to laboratory findings, if the diagnosis was exclusionary, or if it was a preliminary diagnosis, among others. Choose the Concept in the Condition Status domain that best represents the point during the visit when the diagnosis was given. These can include admitting diagnosis, principal diagnosis, and secondary diagnosis. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Condition+Status&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDCondition Status
70CONDITION_OCCURRENCEstop_reasonNovarchar(20)The Stop Reason indicates why a Condition is no longer valid with respect to the purpose within the source data. Note that a Stop Reason does not necessarily imply that the condition is no longer occurring.This information is often not populated in source data and it is a valid etl choice to leave it blank if the information does not exist.NoNo
71CONDITION_OCCURRENCEprovider_idNointegerThe provider associated with condition record, e.g. the provider who made the diagnosis or the provider who recorded the symptom.The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the admitting vs attending physician on an EHR record.NoYesPROVIDERPROVIDER_ID
72CONDITION_OCCURRENCEvisit_occurrence_idNointegerThe visit during which the condition occurred.Depending on the structure of the source data, this may have to be determined based on dates. If a CONDITION_START_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the Visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the CONDITION_OCCURRENCE record.NoYesVISIT_OCCURRENCEVISIT_OCCURRENCE_ID
73CONDITION_OCCURRENCEvisit_detail_idNointegerThe VISIT_DETAIL record during which the condition occurred. For example, if the person was in the ICU at the time of the diagnosis the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.Same rules apply as for the VISIT_OCCURRENCE_ID.NoYesVISIT_DETAILVISIT_DETAIL_ID
74CONDITION_OCCURRENCEcondition_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the condition that occurred. For example, this could be an ICD10 or Read code.This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.NoNo
75CONDITION_OCCURRENCEcondition_source_concept_idNointegerThis is the concept representing the condition source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Condition necessary for a given analytic use case. Consider using CONDITION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.If the CONDITION_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.NoYesCONCEPTCONCEPT_ID
76CONDITION_OCCURRENCEcondition_status_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the condition status.This information may be called something different in the source data but the field is meant to contain a value indicating when and how a diagnosis was given to a patient. This source value is mapped to a standard concept which is stored in the CONDITION_STATUS_CONCEPT_ID field.NoNo
77DRUG_EXPOSUREdrug_exposure_idYesintegerThe unique key given to records of drug dispensings or administrations for a person. Refer to the ETL for how duplicate drugs during the same visit were handled.Each instance of a drug dispensing or administration present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same drug within the same visit. It is valid to keep these duplicates and assign them individual, unique, DRUG_EXPOSURE_IDs, though it is up to the ETL how they should be handled.YesNo
78DRUG_EXPOSUREperson_idYesintegerThe PERSON_ID of the PERSON for whom the drug dispensing or administration is recorded. This may be a system generated code.NoYesPERSONPERSON_ID
79DRUG_EXPOSUREdrug_concept_idYesintegerThe DRUG_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a drug product or molecule otherwise introduced to the body. The drug concepts can have a varying degree of information about drug strength and dose. This information is relevant in the context of quantity and administration information in the subsequent fields plus strength information from the DRUG_STRENGTH table, provided as part of the standard vocabulary download.The CONCEPT_ID that the DRUG_SOURCE_VALUE maps to. The concept id should be derived either from mapping from the source concept id or by picking the drug concept representing the most amount of detail you have. Records whose source values map to standard concepts with a domain of Drug should go in this table. When the Drug Source Value of the code cannot be translated into Standard Drug Concept IDs, a Drug exposure entry is stored with only the corresponding SOURCE_CONCEPT_ID and DRUG_SOURCE_VALUE and a DRUG_CONCEPT_ID of 0. The Drug Concept with the most detailed content of information is preferred during the mapping process. These are indicated in the CONCEPT_CLASS_ID field of the Concept and are recorded in the following order of precedence: 'Branded Pack', 'Clinical Pack', 'Branded Drug', 'Clinical Drug', 'Branded Drug Component', 'Clinical Drug Component', 'Branded Drug Form', 'Clinical Drug Form', and only if no other information is available 'Ingredient'. Note: If only the drug class is known, the DRUG_CONCEPT_ID field should contain 0. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Drug&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDDrug
80DRUG_EXPOSUREdrug_exposure_start_dateYesdateUse this date to determine the start date of the drug record.Valid entries include a start date of a prescription, the date a prescription was filled, or the date on which a Drug administration was recorded. It is a valid ETL choice to use the date the drug was ordered as the DRUG_EXPOSURE_START_DATE.NoNo
81DRUG_EXPOSUREdrug_exposure_start_datetimeNodatetimeThis is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)NoNo
82DRUG_EXPOSUREdrug_exposure_end_dateYesdateThe DRUG_EXPOSURE_END_DATE denotes the day the drug exposure ended for the patient.If this information is not explicitly available in the data, infer the end date using the following methods:<br><br> 1. Start first with duration or days supply using the calculation drug start date + days supply -1 day. 2. Use quantity divided by daily dose that you may obtain from the sig or a source field (or assumed daily dose of 1) for solid, indivisibile, drug products. If quantity represents ingredient amount, quantity divided by daily dose * concentration (from drug_strength) drug concept id tells you the dose form. 3. If it is an administration record, set drug end date equal to drug start date. If the record is a written prescription then set end date to start date + 29. If the record is a mail-order prescription set end date to start date + 89. The end date must be equal to or greater than the start date. Ibuprofen 20mg/mL oral solution concept tells us this is oral solution. Calculate duration as quantity (200 example) * daily dose (5mL) /concentration (20mg/mL) 200*5/20 = 50 days. [Examples by dose form](https://ohdsi.github.io/CommonDataModel/drug_dose.html)NoNo
83DRUG_EXPOSUREdrug_exposure_end_datetimeNodatetimeThis is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)NoNo
84DRUG_EXPOSUREverbatim_end_dateNodateThis is the end date of the drug exposure as it appears in the source data, if it is givenPut the end date or discontinuation date as it appears from the source data or leave blank if unavailable.NoNo
85DRUG_EXPOSUREdrug_type_concept_idYesintegerYou can use the TYPE_CONCEPT_ID to delineate between prescriptions written vs. prescriptions dispensed vs. medication history vs. patient-reported exposure, etc.Choose the drug_type_concept_id that best represents the provenance of the record, for example whether it came from a record of a prescription written or physician administered drug. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDType Concept
86DRUG_EXPOSUREstop_reasonNovarchar(20)The reason a person stopped a medication as it is represented in the source. Reasons include regimen completed, changed, removed, etc. This field will be retired in v6.0.This information is often not populated in source data and it is a valid etl choice to leave it blank if the information does not exist.NoNo
87DRUG_EXPOSURErefillsNointegerThis is only filled in when the record is coming from a prescription written this field is meant to represent intended refills at time of the prescription.NoNo
88DRUG_EXPOSUREquantityNofloatTo find the dose form of a drug the RELATIONSHIP table can be used where the relationship_id is 'Has dose form'. If liquid, quantity stands for the total amount dispensed or ordered of ingredient in the units given by the drug_strength table. If the unit from the source data does not align with the unit in the DRUG_STRENGTH table the quantity should be converted to the correct unit given in DRUG_STRENGTH. For clinical drugs with fixed dose forms (tablets etc.) the quantity is the number of units/tablets/capsules prescribed or dispensed (can be partial, but then only 1/2 or 1/3, not 0.01). Clinical drugs with divisible dose forms (injections) the quantity is the amount of ingredient the patient got. For example, if the injection is 2mg/mL but the patient got 80mL then quantity is reported as 160. Quantified clinical drugs with divisible dose forms (prefilled syringes), the quantity is the amount of ingredient similar to clinical drugs. Please see [how to calculate drug dose](https://ohdsi.github.io/CommonDataModel/drug_dose.html) for more information. NoNo
89DRUG_EXPOSUREdays_supplyNointegerDays supply of the drug. This should be the verbatim days_supply as given on the prescription. If the drug is physician administered use duration end date if given or set to 1 as default if duration is not available.NoNo
90DRUG_EXPOSUREsigNovarchar(MAX)This is the verbatim instruction for the drug as written by the provider.Put the written out instructions for the drug as it is verbatim in the source, if available.NoNo
91DRUG_EXPOSUREroute_concept_idNointegerThe standard CONCEPT_ID that the ROUTE_SOURCE_VALUE maps to in the route domain.NoYesCONCEPTCONCEPT_IDRoute
92DRUG_EXPOSURElot_numberNovarchar(50)NoNo
93DRUG_EXPOSUREprovider_idNointegerThe Provider associated with drug record, e.g. the provider who wrote the prescription or the provider who administered the drug.The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the ordering vs administering physician on an EHR record.NoYesPROVIDERPROVIDER_ID
94DRUG_EXPOSUREvisit_occurrence_idNointegerThe Visit during which the drug was prescribed, administered or dispensed.To populate this field drug exposures must be explicitly initiated in the visit.NoYesVISIT_OCCURRENCEVISIT_OCCURRENCE_ID
95DRUG_EXPOSUREvisit_detail_idNointegerThe VISIT_DETAIL record during which the drug exposure occurred. For example, if the person was in the ICU at the time of the drug administration the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.Same rules apply as for the VISIT_OCCURRENCE_ID.NoYesVISIT_DETAILVISIT_DETAIL_ID
96DRUG_EXPOSUREdrug_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the drug exposure that occurred. For example, this could be an NDC or Gemscript code.This code is mapped to a Standard Drug Concept in the Standardized Vocabularies and the original code is stored here for reference.NoNo
97DRUG_EXPOSUREdrug_source_concept_idNointegerThis is the concept representing the drug source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Drug necessary for a given analytic use case. Consider using DRUG_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.If the DRUG_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.NoYesCONCEPTCONCEPT_ID
98DRUG_EXPOSUREroute_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the drug route.This information may be called something different in the source data but the field is meant to contain a value indicating when and how a drug was given to a patient. This source value is mapped to a standard concept which is stored in the ROUTE_CONCEPT_ID field.NoNo
99DRUG_EXPOSUREdose_unit_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the dose unit of the drug given.This information may be called something different in the source data but the field is meant to contain a value indicating the unit of dosage of drug given to the patient. This is an older column and will be deprecated in an upcoming version.NoNo
100PROCEDURE_OCCURRENCEprocedure_occurrence_idYesintegerThe unique key given to a procedure record for a person. Refer to the ETL for how duplicate procedures during the same visit were handled.Each instance of a procedure occurrence in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same procedure within the same visit. It is valid to keep these duplicates and assign them individual, unique, PROCEDURE_OCCURRENCE_IDs, though it is up to the ETL how they should be handled.YesNo
101PROCEDURE_OCCURRENCEperson_idYesintegerThe PERSON_ID of the PERSON for whom the procedure is recorded. This may be a system generated code.NoYesPERSONPERSON_ID
102PROCEDURE_OCCURRENCEprocedure_concept_idYesintegerThe PROCEDURE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a procedureThe CONCEPT_ID that the PROCEDURE_SOURCE_VALUE maps to. Only records whose source values map to standard concepts with a domain of "Procedure" should go in this table. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Procedure&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDProcedure
103PROCEDURE_OCCURRENCEprocedure_dateYesdateUse this date to determine the date the procedure occurred.If a procedure lasts more than a day, then it should be recorded as a separate record for each day the procedure occurred, this logic is in lieu of the procedure_end_date, which will be added in a future version of the CDM.NoNo
104PROCEDURE_OCCURRENCEprocedure_datetimeNodatetimeThis is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)NoNo
105PROCEDURE_OCCURRENCEprocedure_type_concept_idYesintegerThis field can be used to determine the provenance of the Procedure record, as in whether the procedure was from an EHR system, insurance claim, registry, or other sources.Choose the PROCEDURE_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. If a procedure is recorded as an EHR encounter, the PROCEDURE_TYPE_CONCEPT would be 'EHR encounter record'. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDType Concept
106PROCEDURE_OCCURRENCEmodifier_concept_idNointegerThe modifiers are intended to give additional information about the procedure but as of now the vocabulary is under review.It is up to the ETL to choose how to map modifiers if they exist in source data. These concepts are typically distinguished by 'Modifier' concept classes (e.g., 'CPT4 Modifier' as part of the 'CPT4' vocabulary). If there is more than one modifier on a record, one should be chosen that pertains to the procedure rather than provider. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?conceptClass=CPT4+Modifier&conceptClass=HCPCS+Modifier&vocabulary=CPT4&vocabulary=HCPCS&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_ID
107PROCEDURE_OCCURRENCEquantityNointegerIf the quantity value is omitted, a single procedure is assumed.If a Procedure has a quantity of '0' in the source, this should default to '1' in the ETL. If there is a record in the source it can be assumed the exposure occurred at least onceNoNo
108PROCEDURE_OCCURRENCEprovider_idNointegerThe provider associated with the procedure record, e.g. the provider who performed the Procedure.The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the admitting vs attending physician on an EHR record.NoNoPROVIDERPROVIDER_ID
109PROCEDURE_OCCURRENCEvisit_occurrence_idNointegerThe visit during which the procedure occurred.Depending on the structure of the source data, this may have to be determined based on dates. If a PROCEDURE_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the Visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the PROCEDURE_OCCURRENCE record.NoNoVISIT_OCCURRENCEVISIT_OCCURRENCE_ID
110PROCEDURE_OCCURRENCEvisit_detail_idNointegerThe VISIT_DETAIL record during which the Procedure occurred. For example, if the Person was in the ICU at the time of the Procedure the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.Same rules apply as for the VISIT_OCCURRENCE_ID.NoNoVISIT_DETAILVISIT_DETAIL_ID
111PROCEDURE_OCCURRENCEprocedure_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the procedure that occurred. For example, this could be an CPT4 or OPCS4 code.Use this value to look up the source concept id and then map the source concept id to a standard concept id.NoNo
112PROCEDURE_OCCURRENCEprocedure_source_concept_idNointegerThis is the concept representing the procedure source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Procedure necessary for a given analytic use case. Consider using PROCEDURE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.If the PROCEDURE_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.NoNoCONCEPTCONCEPT_ID
113PROCEDURE_OCCURRENCEmodifier_source_valueNovarchar(50)The original modifier code from the source is stored here for reference.NoNo
114DEVICE_EXPOSUREdevice_exposure_idYesintegerThe unique key given to records a person's exposure to a foreign physical object or instrument.Each instance of an exposure to a foreign object or device present in the source data should be assigned this unique key. YesNo
115DEVICE_EXPOSUREperson_idYesintegerNoYesPERSONPERSON_ID
116DEVICE_EXPOSUREdevice_concept_idYesintegerThe DEVICE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a foreign object or instrument the person was exposed to. The CONCEPT_ID that the DEVICE_SOURCE_VALUE maps to. NoYesCONCEPTCONCEPT_IDDevice
117DEVICE_EXPOSUREdevice_exposure_start_dateYesdateUse this date to determine the start date of the device record.Valid entries include a start date of a procedure to implant a device, the date of a prescription for a device, or the date of device administration. NoNo
118DEVICE_EXPOSUREdevice_exposure_start_datetimeNodatetimeThis is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)NoNo
119DEVICE_EXPOSUREdevice_exposure_end_dateNodateThe DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given.Put the end date or discontinuation date as it appears from the source data or leave blank if unavailable.NoNo
120DEVICE_EXPOSUREdevice_exposure_end_datetimeNodatetimeIf a source does not specify datetime the convention is to set the time to midnight (00:00:0000)NoNo
121DEVICE_EXPOSUREdevice_type_concept_idYesintegerYou can use the TYPE_CONCEPT_ID to denote the provenance of the record, as in whether the record is from administrative claims or EHR. Choose the drug_type_concept_id that best represents the provenance of the record, for example whether it came from a record of a prescription written or physician administered drug. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDType Concept
122DEVICE_EXPOSUREunique_device_idNovarchar(50)This is the Unique Device Identification number for devices regulated by the FDA, if given.For medical devices that are regulated by the FDA, a Unique Device Identification (UDI) is provided if available in the data source and is recorded in the UNIQUE_DEVICE_ID field.NoNo
123DEVICE_EXPOSUREquantityNointegerNoNo
124DEVICE_EXPOSUREprovider_idNointegerThe Provider associated with device record, e.g. the provider who wrote the prescription or the provider who implanted the device.The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record.NoYesPROVIDERPROVIDER_ID
125DEVICE_EXPOSUREvisit_occurrence_idNointegerThe Visit during which the device was prescribed or given.To populate this field device exposures must be explicitly initiated in the visit.NoYesVISIT_OCCURRENCEVISIT_OCCURRENCE_ID
126DEVICE_EXPOSUREvisit_detail_idNointegerThe Visit Detail during which the device was prescribed or given.To populate this field device exposures must be explicitly initiated in the visit detail record.NoYesVISIT_DETAILVISIT_DETAIL_ID
127DEVICE_EXPOSUREdevice_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the device exposure that occurred. For example, this could be an NDC or Gemscript code.This code is mapped to a Standard Device Concept in the Standardized Vocabularies and the original code is stored here for reference.NoNo
128DEVICE_EXPOSUREdevice_source_concept_idNointegerThis is the concept representing the device source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Device necessary for a given analytic use case. Consider using DEVICE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.If the DEVICE_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.NoYesCONCEPTCONCEPT_ID
129MEASUREMENTmeasurement_idYesintegerThe unique key given to a Measurement record for a Person. Refer to the ETL for how duplicate Measurements during the same Visit were handled.Each instance of a measurement present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same measurement within the same visit. It is valid to keep these duplicates and assign them individual, unique, MEASUREMENT_IDs, though it is up to the ETL how they should be handled.YesNo
130MEASUREMENTperson_idYesintegerThe PERSON_ID of the Person for whom the Measurement is recorded. This may be a system generated code.NoYesPERSONPERSON_ID
131MEASUREMENTmeasurement_concept_idYesintegerThe MEASUREMENT_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies.The CONCEPT_ID that the MEASUREMENT_SOURCE_CONCEPT_ID maps to. Only records whose SOURCE_CONCEPT_IDs map to Standard Concepts with a domain of "Measurement" should go in this table.NoYesCONCEPTCONCEPT_IDMeasurement
132MEASUREMENTmeasurement_dateYesdateUse this date to determine the date of the measurement.If there are multiple dates in the source data associated with a record such as order_date, draw_date, and result_date, choose the one that is closest to the date the sample was drawn from the patient.NoNo
133MEASUREMENTmeasurement_datetimeNodatetimeThis is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)NoNo
134MEASUREMENTmeasurement_timeNovarchar(10)This is present for backwards compatibility and will be deprecated in an upcoming version.NoNo
135MEASUREMENTmeasurement_type_concept_idYesintegerThis field can be used to determine the provenance of the Measurement record, as in whether the measurement was from an EHR system, insurance claim, registry, or other sources.Choose the MEASUREMENT_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDType Concept
136MEASUREMENToperator_concept_idNointegerThe meaning of Concept [4172703](https://athena.ohdsi.org/search-terms/terms/4172703) for '=' is identical to omission of a OPERATOR_CONCEPT_ID value. Since the use of this field is rare, it's important when devising analyses to not to forget testing for the content of this field for values different from =.Operators are <, <=, =, >=, > and these concepts belong to the 'Meas Value Operator' domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Meas+Value+Operator&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_ID
137MEASUREMENTvalue_as_numberNofloatThis is the numerical value of the Result of the Measurement, if available. Note that measurements such as blood pressures will be split into their component parts i.e. one record for systolic, one record for diastolic.If there is a negative value coming from the source, set the VALUE_AS_NUMBER to NULL, with the exception of the following Measurements (listed as LOINC codes):<br>- [1925-7](https://athena.ohdsi.org/search-terms/terms/3003396) Base excess in Arterial blood by calculation - [1927-3](https://athena.ohdsi.org/search-terms/terms/3002032) Base excess in Venous blood by calculation - [8632-2](https://athena.ohdsi.org/search-terms/terms/3006277) QRS-Axis - [11555-0](https://athena.ohdsi.org/search-terms/terms/3012501) Base excess in Blood by calculation - [1926-5](https://athena.ohdsi.org/search-terms/terms/3003129) Base excess in Capillary blood by calculation - [28638-5](https://athena.ohdsi.org/search-terms/terms/3004959) Base excess in Arterial cord blood by calculation [28639-3](https://athena.ohdsi.org/search-terms/terms/3007435) Base excess in Venous cord blood by calculationNoNo
138MEASUREMENTvalue_as_concept_idNointegerIf the raw data gives a categorial result for measurements those values are captured and mapped to standard concepts in the 'Meas Value' domain.If the raw data provides categorial results as well as continuous results for measurements, it is a valid ETL choice to preserve both values. The continuous value should go in the VALUE_AS_NUMBER field and the categorical value should be mapped to a standard concept in the 'Meas Value' domain and put in the VALUE_AS_CONCEPT_ID field. This is also the destination for the 'Maps to value' relationship.NoYesCONCEPTCONCEPT_ID
139MEASUREMENTunit_concept_idNointegerThere is currently no recommended unit for individual measurements, i.e. it is not mandatory to represent Hemoglobin a1C measurements as a percentage. UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.There is no standardization requirement for units associated with MEASUREMENT_CONCEPT_IDs, however, it is the responsibility of the ETL to choose the most plausible unit.NoYesCONCEPTCONCEPT_IDUnit
140MEASUREMENTrange_lowNofloatRanges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.If reference ranges for upper and lower limit of normal as provided (typically by a laboratory) these are stored in the RANGE_HIGH and RANGE_LOW fields. This should be set to NULL if not provided.NoNo
141MEASUREMENTrange_highNofloatRanges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.If reference ranges for upper and lower limit of normal as provided (typically by a laboratory) these are stored in the RANGE_HIGH and RANGE_LOW fields. This should be set to NULL if not provided.NoNo
142MEASUREMENTprovider_idNointegerThe provider associated with measurement record, e.g. the provider who ordered the test or the provider who recorded the result.The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record. For example the admitting vs attending physician on an EHR record.NoYesPROVIDERPROVIDER_ID
143MEASUREMENTvisit_occurrence_idNointegerThe visit during which the Measurement occurred.Depending on the structure of the source data, this may have to be determined based on dates. If a MEASUREMENT_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the measurement record. If a measurement is related to a visit explicitly in the source data, it is possible that the result date of the Measurement falls outside of the bounds of the Visit dates.NoYesVISIT_OCCURRENCEVISIT_OCCURRENCE_ID
144MEASUREMENTvisit_detail_idNointegerThe VISIT_DETAIL record during which the Measurement occurred. For example, if the Person was in the ICU at the time the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.Same rules apply as for the VISIT_OCCURRENCE_ID.NoYesVISIT_DETAILVISIT_DETAIL_ID
145MEASUREMENTmeasurement_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the Measurement that occurred. For example, this could be an ICD10 or Read code.This code is mapped to a Standard Measurement Concept in the Standardized Vocabularies and the original code is stored here for reference.NoNo
146MEASUREMENTmeasurement_source_concept_idNointegerThis is the concept representing the MEASUREMENT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Measurement necessary for a given analytic use case. Consider using MEASUREMENT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.If the MEASUREMENT_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.NoYesCONCEPTCONCEPT_ID
147MEASUREMENTunit_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the unit of the Measurement that occurred. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.NoNo
148MEASUREMENTvalue_source_valueNovarchar(50)This field houses the verbatim result value of the Measurement from the source data . If both a continuous and categorical result are given in the source data such that both VALUE_AS_NUMBER and VALUE_AS_CONCEPT_ID are both included, store the verbatim value that was mapped to VALUE_AS_CONCEPT_ID here.NoNo
149OBSERVATIONobservation_idYesintegerThe unique key given to an Observation record for a Person. Refer to the ETL for how duplicate Observations during the same Visit were handled.Each instance of an observation present in the source data should be assigned this unique key. YesNo
150OBSERVATIONperson_idYesintegerThe PERSON_ID of the Person for whom the Observation is recorded. This may be a system generated code.NoYesPERSONPERSON_ID
151OBSERVATIONobservation_concept_idYesintegerThe OBSERVATION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies.The CONCEPT_ID that the OBSERVATION_SOURCE_CONCEPT_ID maps to. There is no specified domain that the Concepts in this table must adhere to. The only rule is that records with Concepts in the Condition, Procedure, Drug, Measurement, or Device domains MUST go to the corresponding table. NoYesCONCEPTCONCEPT_ID
152OBSERVATIONobservation_dateYesdateThe date of the Observation. Depending on what the Observation represents this could be the date of a lab test, the date of a survey, or the date a patient's family history was taken. For some observations the ETL may need to make a choice as to which date to choose.NoNo
153OBSERVATIONobservation_datetimeNodatetimeIf no time is given set to midnight (00:00:00).NoNo
154OBSERVATIONobservation_type_concept_idYesintegerThis field can be used to determine the provenance of the Observation record, as in whether the measurement was from an EHR system, insurance claim, registry, or other sources.Choose the OBSERVATION_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDType Concept
155OBSERVATIONvalue_as_numberNofloatThis is the numerical value of the Result of the Observation, if applicable and available. It is not expected that all Observations will have numeric results, rather, this field is here to house values should they exist. NoNo
156OBSERVATIONvalue_as_stringNovarchar(60)This is the categorical value of the Result of the Observation, if applicable and available. NoNo
157OBSERVATIONvalue_as_concept_idNoIntegerIt is possible that some records destined for the Observation table have two clinical ideas represented in one source code. This is common with ICD10 codes that describe a family history of some Condition, for example. In OMOP the Vocabulary breaks these two clinical ideas into two codes; one becomes the OBSERVATION_CONCEPT_ID and the other becomes the VALUE_AS_CONCEPT_ID. It is important when using the Observation table to keep this possibility in mind and to examine the VALUE_AS_CONCEPT_ID field for relevant information. Note that the value of VALUE_AS_CONCEPT_ID may be provided through mapping from a source Concept which contains the content of the Observation. In those situations, the CONCEPT_RELATIONSHIP table in addition to the 'Maps to' record contains a second record with the relationship_id set to 'Maps to value'. For example, ICD10 [Z82.4](https://athena.ohdsi.org/search-terms/terms/45581076) 'Family history of ischaemic heart disease and other diseases of the circulatory system' has a 'Maps to' relationship to [4167217](https://athena.ohdsi.org/search-terms/terms/4167217) 'Family history of clinical finding' as well as a 'Maps to value' record to [134057](https://athena.ohdsi.org/search-terms/terms/134057) 'Disorder of cardiovascular system'.NoYesCONCEPTCONCEPT_ID
158OBSERVATIONqualifier_concept_idNointegerThis field contains all attributes specifying the clinical fact further, such as as degrees, severities, drug-drug interaction alerts etc.Use your best judgement as to what Concepts to use here and if they are necessary to accurately represent the clinical record. There is no restriction on the domain of these Concepts, they just need to be Standard.NoYesCONCEPTCONCEPT_ID
159OBSERVATIONunit_concept_idNointegerThere is currently no recommended unit for individual observation concepts. UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.There is no standardization requirement for units associated with OBSERVATION_CONCEPT_IDs, however, it is the responsibility of the ETL to choose the most plausible unit.NoYesCONCEPTCONCEPT_IDUnit
160OBSERVATIONprovider_idNointegerThe provider associated with the observation record, e.g. the provider who ordered the test or the provider who recorded the result.The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record. For example the admitting vs attending physician on an EHR record.NoYesPROVIDERPROVIDER_ID
161OBSERVATIONvisit_occurrence_idNointegerThe visit during which the Observation occurred.Depending on the structure of the source data, this may have to be determined based on dates. If an OBSERVATION_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the observation record. If an observation is related to a visit explicitly in the source data, it is possible that the result date of the Observation falls outside of the bounds of the Visit dates.NoYesVISIT_OCCURRENCEVISIT_OCCURRENCE_ID
162OBSERVATIONvisit_detail_idNointegerThe VISIT_DETAIL record during which the Observation occurred. For example, if the Person was in the ICU at the time the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.Same rules apply as for the VISIT_OCCURRENCE_ID.NoYesVISIT_DETAILVISIT_DETAIL_ID
163OBSERVATIONobservation_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the Observation that occurred. For example, this could be an ICD10 or Read code.This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference.NoNo
164OBSERVATIONobservation_source_concept_idNointegerThis is the concept representing the OBSERVATION_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Observation necessary for a given analytic use case. Consider using OBSERVATION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.If the OBSERVATION_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.NoYesCONCEPTCONCEPT_ID
165OBSERVATIONunit_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the unit of the Observation that occurred. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.NoNo
166OBSERVATIONqualifier_source_valueNovarchar(50)This field houses the verbatim value from the source data representing the qualifier of the Observation that occurred. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.NoNo
167DEATHperson_idYesintegerNoYesPERSONPERSON_ID
168DEATHdeath_dateYesdateThe date the person was deceased.If the precise date include 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.NoNo
169DEATHdeath_datetimeNodatetimeIf not available set time to midnight (00:00:00)NoNo
170DEATHdeath_type_concept_idNointegerThis is the provenance of the death record, i.e., where it came from. It is possible that an administrative claims database would source death information from a government file so do not assume the Death Type is the same as the Visit Type, etc.Use the type concept that be reflects the source of the death record. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDType Concept
171DEATHcause_concept_idNointegerThis is the Standard Concept representing the Person's cause of death, if available.There is no specified domain for this concept, just choose the Standard Concept Id that best represents the person's cause of death.NoYesCONCEPTCONCEPT_ID
172DEATHcause_source_valueNovarchar(50)If available, put the source code representing the cause of death here. NoNo
173DEATHcause_source_concept_idNointegerIf the cause of death was coded using a Vocabulary present in the OMOP Vocabularies put the CONCEPT_ID representing the cause of death here.NoYesCONCEPTCONCEPT_ID
174NOTEnote_idYesintegerA unique identifier for each note.YesNo
175NOTEperson_idYesintegerNoYesPERSONPERSON_ID
176NOTEnote_dateYesdateThe date the note was recorded.NoNo
177NOTEnote_datetimeNodatetimeIf time is not given set the time to midnight.NoNo
178NOTEnote_type_concept_idYesintegerThe provenance of the note. Most likely this will be EHR. Put the source system of the note, as in EHR record. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&domain=Type+Concept&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDType Concept
179NOTEnote_class_concept_idYesintegerA Standard Concept Id representing the HL7 LOINC Document Type Vocabulary classification of the note.Map the note classification to a Standard Concept. For more information see the ETL Conventions in the description of the NOTE table. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&conceptClass=Doc+Kind&conceptClass=Doc+Role&conceptClass=Doc+Setting&conceptClass=Doc+Subject+Matter&conceptClass=Doc+Type+of+Service&domain=Meas+Value&page=1&pageSize=15&query=). This Concept can alternatively be represented by concepts with the relationship 'Kind of (LOINC)' to [706391](https://athena.ohdsi.org/search-terms/terms/706391) (Note).NoYesCONCEPTCONCEPT_ID
180NOTEnote_titleNovarchar(250)The title of the note.NoNo
181NOTEnote_textYesvarchar(MAX)The content of the note.NoNo
182NOTEencoding_concept_idYesintegerThis is the Concept representing the character encoding type. Put the Concept Id that represents the encoding character type here. Currently the only option is UTF-8 ([32678](https://athena.ohdsi.org/search-terms/terms/32678)). It the note is encoded in any other type, like ASCII then put 0. NoYesCONCEPTCONCEPT_ID
183NOTElanguage_concept_idYesintegerThe language of the note. Use Concepts that are descendants of the concept [4182347](https://athena.ohdsi.org/search-terms/terms/4182347) (World Languages).NoYesCONCEPTCONCEPT_ID
184NOTEprovider_idNointegerThe Provider who wrote the note.The ETL may need to make a determination on which provider to put here.NoYesPROVIDERPROVIDER_ID
185NOTEvisit_occurrence_idNointegerThe Visit during which the note was written. NoYesVISIT_OCCURRENCEVISIT_OCCURRENCE_ID
186NOTEvisit_detail_idNointegerThe Visit Detail during which the note was written.NoYesVISIT_DETAILVISIT_DETAIL_ID
187NOTEnote_source_valueNovarchar(50)The source value mapped to the NOTE_CLASS_CONCEPT_ID.NoNo
188NOTE_NLPnote_nlp_idYesintegerA unique identifier for the NLP record.YesNo
189NOTE_NLPnote_idYesintegerThis is the NOTE_ID for the NOTE record the NLP record is associated to.NoNo
190NOTE_NLPsection_concept_idNointegerThe SECTION_CONCEPT_ID should be used to represent the note section contained in the NOTE_NLP record. These concepts can be found as parts of document panels and are based on the type of note written, i.e. a discharge summary. These panels can be found as concepts with the relationship 'Subsumes' to CONCEPT_ID [45875957](https://athena.ohdsi.org/search-terms/terms/45875957).NoYesCONCEPTCONCEPT_ID
191NOTE_NLPsnippetNovarchar(250)A small window of text surrounding the termNoNo
192NOTE_NLPoffsetNovarchar(50)Character offset of the extracted term in the input noteNoNo
193NOTE_NLPlexical_variantYesvarchar(250)Raw text extracted from the NLP tool.NoNo
194NOTE_NLPnote_nlp_concept_idNointegerNoYesCONCEPTCONCEPT_ID
195NOTE_NLPnote_nlp_source_concept_idNointegerNoYesCONCEPTCONCEPT_ID
196NOTE_NLPnlp_systemNovarchar(250)Name and version of the NLP system that extracted the term. Useful for data provenance.NoNo
197NOTE_NLPnlp_dateYesdateThe date of the note processing.NoNo
198NOTE_NLPnlp_datetimeNodatetimeThe date and time of the note processing.NoNo
199NOTE_NLPterm_existsNovarchar(1)Term_exists is defined as a flag that indicates if the patient actually has or had the condition. Any of the following modifiers would make Term_exists false: Negation = true Subject = [anything other than the patient] Conditional = true/li> Rule_out = true Uncertain = very low certainty or any lower certainties A complete lack of modifiers would make Term_exists true. NoNo
200NOTE_NLPterm_temporalNovarchar(50)Term_temporal is to indicate if a condition is present or just in the past. The following would be past:<br><br> - History = true - Concept_date = anything before the time of the reportNoNo
201NOTE_NLPterm_modifiersNovarchar(2000)For the modifiers that are there, they would have to have these values:<br><br> - Negation = false - Subject = patient - Conditional = false - Rule_out = false - Uncertain = true or high or moderate or even low (could argue about low). Term_modifiers will concatenate all modifiers for different types of entities (conditions, drugs, labs etc) into one string. Lab values will be saved as one of the modifiers. NoNo
202SPECIMENspecimen_idYesintegerUnique identifier for each specimen.YesNo
203SPECIMENperson_idYesintegerThe person from whom the specimen is collected.NoYesPERSONPERSON_ID
204SPECIMENspecimen_concept_idYesintegerThe standard CONCEPT_ID that the SPECIMEN_SOURCE_VALUE maps to in the specimen domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Specimen&standardConcept=Standard&page=1&pageSize=15&query=)NoYesCONCEPTCONCEPT_ID
205SPECIMENspecimen_type_concept_idYesintegerPut the source of the specimen record, as in an EHR system. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&domain=Type+Concept&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDType Concept
206SPECIMENspecimen_dateYesdateThe date the specimen was collected.NoNo
207SPECIMENspecimen_datetimeNodatetimeNoNo
208SPECIMENquantityNofloatThe amount of specimen collected from the person.NoNo
209SPECIMENunit_concept_idNointegerThe unit for the quantity of the specimen.Map the UNIT_SOURCE_VALUE to a Standard Concept in the Unit domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Unit&standardConcept=Standard&page=1&pageSize=15&query=)NoYesCONCEPTCONCEPT_ID
210SPECIMENanatomic_site_concept_idNointegerThis is the site on the body where the specimen is from.Map the ANATOMIC_SITE_SOURCE_VALUE to a Standard Concept in the Spec Anatomic Site domain. This should be coded at the lowest level of granularity [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&domain=Spec+Anatomic+Site&conceptClass=Body+Structure&page=4&pageSize=15&query=)NoYesCONCEPTCONCEPT_ID
211SPECIMENdisease_status_concept_idNointegerNoYesCONCEPTCONCEPT_ID
212SPECIMENspecimen_source_idNovarchar(50)This is the identifier for the specimen from the source system. NoNo
213SPECIMENspecimen_source_valueNovarchar(50)NoNo
214SPECIMENunit_source_valueNovarchar(50)This unit for the quantity of the specimen, as represented in the source.NoNo
215SPECIMENanatomic_site_source_valueNovarchar(50)This is the site on the body where the specimen was taken from, as represented in the source.NoNo
216SPECIMENdisease_status_source_valueNovarchar(50)NoNo
217FACT_RELATIONSHIPdomain_concept_id_1YesintegerNoYesCONCEPTCONCEPT_ID
218FACT_RELATIONSHIPfact_id_1YesintegerNoNo
219FACT_RELATIONSHIPdomain_concept_id_2YesintegerNoYesCONCEPTCONCEPT_ID
220FACT_RELATIONSHIPfact_id_2YesintegerNoNo
221FACT_RELATIONSHIPrelationship_concept_idYesintegerNoYesCONCEPTCONCEPT_ID
222LOCATIONlocation_idYesintegerThe unique key given to a unique Location.Each instance of a Location in the source data should be assigned this unique key.YesNo
223LOCATIONaddress_1Novarchar(50)This is the first line of the address.NoNo
224LOCATIONaddress_2Novarchar(50)This is the second line of the addressNoNo
225LOCATIONcityNovarchar(50)NoNo
226LOCATIONstateNovarchar(2)NoNo
227LOCATIONzipNovarchar(9)Zip codes are handled as strings of up to 9 characters length. For US addresses, these represent either a 3-digit abbreviated Zip code as provided by many sources for patient protection reasons, the full 5-digit Zip or the 9-digit (ZIP + 4) codes. Unless for specific reasons analytical methods should expect and utilize only the first 3 digits. For international addresses, different rules apply.NoNo
228LOCATIONcountyNovarchar(20)NoNo
229LOCATIONlocation_source_valueNovarchar(50)Put the verbatim value for the location here, as it shows up in the source. NoNo
230CARE_SITEcare_site_idYesintegerAssign an id to each unique combination of location_id and place_of_service_source_valueYesNo
231CARE_SITEcare_site_nameNovarchar(255)The name of the care_site as it appears in the source dataNoNo
232CARE_SITEplace_of_service_concept_idNointegerThis is a high-level way of characterizing a Care Site. Typically, however, Care Sites can provide care in multiple settings (inpatient, outpatient, etc.) and this granularity should be reflected in the visit.Choose the concept in the visit domain that best represents the setting in which healthcare is provided in the Care Site. If most visits in a Care Site are Inpatient, then the place_of_service_concept_id should represent Inpatient. If information is present about a unique Care Site (e.g. Pharmacy) then a Care Site record should be created. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=2&pageSize=15&query=).NoYesCONCEPTCONCEPT_ID
233CARE_SITElocation_idNointegerThe location_id from the LOCATION table representing the physical location of the care_site.NoYesLOCATIONLOCATION_ID
234CARE_SITEcare_site_source_valueNovarchar(50)The identifier of the care_site as it appears in the source data. This could be an identifier separate from the name of the care_site.NoNo
235CARE_SITEplace_of_service_source_valueNovarchar(50)Put the place of service of the care_site as it appears in the source data.NoNo
236PROVIDERprovider_idYesintegerIt is assumed that every provider with a different unique identifier is in fact a different person and should be treated independently.This identifier can be the original id from the source data provided it is an integer, otherwise it can be an autogenerated number.YesNo
237PROVIDERprovider_nameNovarchar(255)This field is not necessary as it is not necessary to have the actual identity of the Provider. Rather, the idea is to uniquely and anonymously identify providers of care across the database.NoNo
238PROVIDERnpiNovarchar(20)This is the National Provider Number issued to health care providers in the US by the Centers for Medicare and Medicaid Services (CMS).NoNo
239PROVIDERdeaNovarchar(20)This is the identifier issued by the DEA, a US federal agency, that allows a provider to write prescriptions for controlled substances.NoNo
240PROVIDERspecialty_concept_idNointegerThis field either represents the most common specialty that occurs in the data or the most specific concept that represents all specialties listed, should the provider have more than one. This includes physician specialties such as internal medicine, emergency medicine, etc. and allied health professionals such as nurses, midwives, and pharmacists.If a Provider has more than one Specialty, there are two options: 1. Choose a concept_id which is a common ancestor to the multiple specialties, or, 2. Choose the specialty that occurs most often for the provider. Concepts in this field should be Standard with a domain of Provider. [Accepted Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Provider&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_ID
241PROVIDERcare_site_idNointegerThis is the CARE_SITE_ID for the location that the provider primarily practices in.If a Provider has more than one Care Site, the main or most often exerted CARE_SITE_ID should be recorded.NoYesCARE_SITECARE_SITE_ID
242PROVIDERyear_of_birthNointegerNoNo
243PROVIDERgender_concept_idNointegerThis field represents the recorded gender of the provider in the source data.If given, put a concept from the gender domain representing the recorded gender of the provider. [Accepted Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Gender&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_IDGender
244PROVIDERprovider_source_valueNovarchar(50)Use this field to link back to providers in the source data. This is typically used for error checking of ETL logic.Some use cases require the ability to link back to providers in the source data. This field allows for the storing of the provider identifier as it appears in the source.NoNo
245PROVIDERspecialty_source_valueNovarchar(50)This is the kind of provider or specialty as it appears in the source data. This includes physician specialties such as internal medicine, emergency medicine, etc. and allied health professionals such as nurses, midwives, and pharmacists.Put the kind of provider as it appears in the source data. This field is up to the discretion of the ETL-er as to whether this should be the coded value from the source or the text description of the lookup value.NoNo
246PROVIDERspecialty_source_concept_idNointegerThis is often zero as many sites use proprietary codes to store physician speciality.If the source data codes provider specialty in an OMOP supported vocabulary store the concept_id here.NoYesCONCEPTCONCEPT_ID
247PROVIDERgender_source_valueNovarchar(50)This is provider's gender as it appears in the source data.Put the provider's gender as it appears in the source data. This field is up to the discretion of the ETL-er as to whether this should be the coded value from the source or the text description of the lookup value.NoNo
248PROVIDERgender_source_concept_idNointegerThis is often zero as many sites use proprietary codes to store provider gender.If the source data codes provider gender in an OMOP supported vocabulary store the concept_id here.NoYesCONCEPTCONCEPT_ID
249PAYER_PLAN_PERIODpayer_plan_period_idYesintegerA unique identifier for each unique combination of a Person, Payer, Plan, and Period of time.YesYesPERSONPERSON_ID
250PAYER_PLAN_PERIODperson_idYesintegerThe Person covered by the Plan.A single Person can have multiple, overlapping, PAYER_PLAN_PERIOD recordsNoYesPERSONPERSON_ID
251PAYER_PLAN_PERIODpayer_plan_period_start_dateYesdateStart date of Plan coverage.NoNo
252PAYER_PLAN_PERIODpayer_plan_period_end_dateYesdateEnd date of Plan coverage.NoNo
253PAYER_PLAN_PERIODpayer_concept_idNointegerThis field represents the organization who reimburses the provider which administers care to the Person.Map the Payer directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same payer, though the name of the Payer is not necessary. [Accepted Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Payer&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_ID
254PAYER_PLAN_PERIODpayer_source_valueNovarchar(50)This is the Payer as it appears in the source data.NoNo
255PAYER_PLAN_PERIODpayer_source_concept_idNointegerIf the source data codes the Payer in an OMOP supported vocabulary store the concept_id here.NoYesCONCEPTCONCEPT_ID
256PAYER_PLAN_PERIODplan_concept_idNointegerThis field represents the specific health benefit Plan the Person is enrolled in.Map the Plan directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same health benefit Plan though the name of the Plan is not necessary. [Accepted Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Plan&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_ID
257PAYER_PLAN_PERIODplan_source_valueNovarchar(50)This is the health benefit Plan of the Person as it appears in the source data.NoNo
258PAYER_PLAN_PERIODplan_source_concept_idNointegerIf the source data codes the Plan in an OMOP supported vocabulary store the concept_id here.NoYesCONCEPTCONCEPT_ID
259PAYER_PLAN_PERIODsponsor_concept_idNointegerThis field represents the sponsor of the Plan who finances the Plan. This includes self-insured, small group health plan and large group health plan.Map the sponsor directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same sponsor though the name of the sponsor is not necessary. [Accepted Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Sponsor&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_ID
260PAYER_PLAN_PERIODsponsor_source_valueNovarchar(50)The Plan sponsor as it appears in the source data.NoNo
261PAYER_PLAN_PERIODsponsor_source_concept_idNointegerIf the source data codes the sponsor in an OMOP supported vocabulary store the concept_id here.NoYesCONCEPTCONCEPT_ID
262PAYER_PLAN_PERIODfamily_source_valueNovarchar(50)The common identifier for all people (often a family) that covered by the same policy.Often these are the common digits of the enrollment id of the policy members.NoNo
263PAYER_PLAN_PERIODstop_reason_concept_idNointegerThis field represents the reason the Person left the Plan, if known.Map the stop reason directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. [Accepted Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Plan+Stop+Reason&standardConcept=Standard&page=1&pageSize=15&query=).NoYesCONCEPTCONCEPT_ID
264PAYER_PLAN_PERIODstop_reason_source_valueNovarchar(50)The Plan stop reason as it appears in the source data.NoNo
265PAYER_PLAN_PERIODstop_reason_source_concept_idNointegerIf the source data codes the stop reason in an OMOP supported vocabulary store the concept_id here.NoYesCONCEPTCONCEPT_ID
266COSTcost_idYesintegerYesNo
267COSTcost_event_idYesintegerNoNo
268COSTcost_domain_idYesvarchar(20)NoYesDOMAINDOMAIN_ID
269COSTcost_type_concept_idYesintegerNoYesCONCEPTCONCEPT_ID
270COSTcurrency_concept_idNointegerNoYesCONCEPTCONCEPT_ID
271COSTtotal_chargeNofloatNoNo
272COSTtotal_costNofloatNoNo
273COSTtotal_paidNofloatNoNo
274COSTpaid_by_payerNofloatNoNo
275COSTpaid_by_patientNofloatNoNo
276COSTpaid_patient_copayNofloatNoNo
277COSTpaid_patient_coinsuranceNofloatNoNo
278COSTpaid_patient_deductibleNofloatNoNo
279COSTpaid_by_primaryNofloatNoNo
280COSTpaid_ingredient_costNofloatNoNo
281COSTpaid_dispensing_feeNofloatNoNo
282COSTpayer_plan_period_idNointegerNoNo
283COSTamount_allowedNofloatNoNo
284COSTrevenue_code_concept_idNointegerNoYesCONCEPTCONCEPT_ID
285COSTrevenue_code_source_valueNovarchar(50)Revenue codes are a method to charge for a class of procedures and conditions in the U.S. hospital system.NoNo
286COSTdrg_concept_idNointegerNoYesCONCEPTCONCEPT_ID
287COSTdrg_source_valueNovarchar(3)Diagnosis Related Groups are US codes used to classify hospital cases into one of approximately 500 groups. NoNo
288DRUG_ERAdrug_era_idYesintegerYesNo
289DRUG_ERAperson_idYesintegerNoYesPERSONPERSON_ID
290DRUG_ERAdrug_concept_idYesintegerThe Concept Id representing the specific drug ingredient.NoYesCONCEPTCONCEPT_IDDrugIngredient
291DRUG_ERAdrug_era_start_dateYesdatetimeThe Drug Era Start Date is the start date of the first Drug Exposure for a given ingredient, with at least 31 days since the previous exposure. NoNo
292DRUG_ERAdrug_era_end_dateYesdatetimeThe Drug Era End Date is the end date of the last Drug Exposure. The End Date of each Drug Exposure is either taken from the field drug_exposure_end_date or, as it is typically not available, inferred using the following rules: For pharmacy prescription data, the date when the drug was dispensed plus the number of days of supply are used to extrapolate the End Date for the Drug Exposure. Depending on the country-specific healthcare system, this supply information is either explicitly provided in the day_supply field or inferred from package size or similar information. For Procedure Drugs, usually the drug is administered on a single date (i.e., the administration date). A standard Persistence Window of 30 days (gap, slack) is permitted between two subsequent such extrapolated DRUG_EXPOSURE records to be considered to be merged into a single Drug Era.NoNo
293DRUG_ERAdrug_exposure_countNointegerNoNo
294DRUG_ERAgap_daysNointegerThe Gap Days determine how many total drug-free days are observed between all Drug Exposure events that contribute to a DRUG_ERA record. It is assumed that the drugs are "not stockpiled" by the patient, i.e. that if a new drug prescription or refill is observed (a new DRUG_EXPOSURE record is written), the remaining supply from the previous events is abandoned. The difference between Persistence Window and Gap Days is that the former is the maximum drug-free time allowed between two subsequent DRUG_EXPOSURE records, while the latter is the sum of actual drug-free days for the given Drug Era under the above assumption of non-stockpiling.NoNo
295DOSE_ERAdose_era_idYesintegerYesNo
296DOSE_ERAperson_idYesintegerNoYesPERSONPERSON_ID
297DOSE_ERAdrug_concept_idYesintegerThe Concept Id representing the specific drug ingredient.NoYesCONCEPTCONCEPT_IDDrugIngredient
298DOSE_ERAunit_concept_idYesintegerThe Concept Id representing the unit of the specific drug ingredient.NoYesCONCEPTCONCEPT_IDUnit
299DOSE_ERAdose_valueYesfloatThe numeric value of the dosage of the drug_ingredient.NoNo
300DOSE_ERAdose_era_start_dateYesdatetimeThe date the Person started on the specific dosage, with at least 31 days since any prior exposure.NoNo
301DOSE_ERAdose_era_end_dateYesdatetimeThe date the Person was no longer exposed to the dosage of the specific drug ingredient. An era is ended if there are 31 days or more between dosage records.NoNo
302CONDITION_ERAcondition_era_idYesintegerYesNo
303CONDITION_ERAperson_idYesintegerNoNoPERSONPERSON_ID
304CONDITION_ERAcondition_concept_idYesintegerThe Concept Id representing the Condition.NoYesCONCEPTCONCEPT_IDCondition
305CONDITION_ERAcondition_era_start_dateYesdatetimeThe 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 with at least 31 days since any prior record of the same Condition. NoNo
306CONDITION_ERAcondition_era_end_dateYesdatetimeThe 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.NoNo
307CONDITION_ERAcondition_occurrence_countNointegerThe number of individual Condition Occurrences used to construct the condition era.NoNo
308METADATAmetadata_concept_idYesintegerNoYesCONCEPTCONCEPT_ID
309METADATAmetadata_type_concept_idYesintegerNoYesCONCEPTCONCEPT_ID
310METADATAnameYesvarchar(250)NoNo
311METADATAvalue_as_stringNovarchar(250)NoNo
312METADATAvalue_as_concept_idNointegerNoYesCONCEPTCONCEPT_ID
313METADATAmetadata_dateNodateNoNo
314METADATAmetadata_datetimeNodatetimeNoNo
315CDM_SOURCEcdm_source_nameYesvarchar(255)The name of the CDM instance.NoNo
316CDM_SOURCEcdm_source_abbreviationNovarchar(25)The abbreviation of the CDM instance.NoNo
317CDM_SOURCEcdm_holderNovarchar(255)The holder of the CDM instance.NoNo
318CDM_SOURCEsource_descriptionNovarchar(MAX)The description of the CDM instance.NoNo
319CDM_SOURCEsource_documentation_referenceNovarchar(255)NoNo
320CDM_SOURCEcdm_etl_referenceNovarchar(255)Put the link to the CDM version used.NoNo
321CDM_SOURCEsource_release_dateNodateThe release date of the source data.NoNo
322CDM_SOURCEcdm_release_dateNodateThe release data of the CDM instance.NoNo
323CDM_SOURCEcdm_versionNovarchar(10)NoNo
324CDM_SOURCEvocabulary_versionNovarchar(20)NoNo
325CONCEPTconcept_idYesintegerA unique identifier for each Concept across all domains.YesNo
326CONCEPTconcept_nameYesvarchar(255)An unambiguous, meaningful and descriptive name for the Concept.NoNo
327CONCEPTdomain_idYesvarchar(20)A foreign key to the [DOMAIN](https://ohdsi.github.io/CommonDataModel/cdm531.html#domain) table the Concept belongs to.NoYesDOMAINDOMAIN_ID
328CONCEPTvocabulary_idYesvarchar(20)A foreign key to the [VOCABULARY](https://ohdsi.github.io/CommonDataModel/cdm531.html#vocabulary) table indicating from which source the Concept has been adapted.NoYesVOCABULARYVOCABULARY_ID
329CONCEPTconcept_class_idYesvarchar(20)The attribute or concept class of the Concept. Examples are 'Clinical Drug', 'Ingredient', 'Clinical Finding' etc.NoYesCONCEPT_CLASSCONCEPT_CLASS_ID
330CONCEPTstandard_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 allowable values are 'S' (Standard Concept) and 'C' (Classification Concept), otherwise the content is NULL.NoNo
331CONCEPTconcept_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.NoNo
332CONCEPTvalid_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.NoNo
333CONCEPTvalid_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.NoNo
334CONCEPTinvalid_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.NoNo
335VOCABULARYvocabulary_idYesvarchar(20)A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit.YesNo
336VOCABULARYvocabulary_nameYesvarchar(255)The name describing the vocabulary, for example, International Classification of Diseases, Ninth Revision, Clinical Modification, Volume 1 and 2 (NCHS) etc.NoNo
337VOCABULARYvocabulary_referenceYesvarchar(255)External reference to documentation or available download of the about the vocabulary.NoNo
338VOCABULARYvocabulary_versionNovarchar(255)Version of the Vocabulary as indicated in the source.NoNo
339VOCABULARYvocabulary_concept_idYesintegerA Concept that represents the Vocabulary the VOCABULARY record belongs to.NoYesCONCEPTCONCEPT_ID
340DOMAINdomain_idYesvarchar(20)A unique key for each domain.YesNo
341DOMAINdomain_nameYesvarchar(255)The name describing the Domain, e.g. Condition, Procedure, Measurement etc.NoNo
342DOMAINdomain_concept_idYesintegerA Concept representing the Domain Concept the DOMAIN record belongs to.NoYesCONCEPTCONCEPT_ID
343CONCEPT_CLASSconcept_class_idYesvarchar(20)A unique key for each class.YesNo
344CONCEPT_CLASSconcept_class_nameYesvarchar(255)The name describing the Concept Class, e.g. Clinical Finding, Ingredient, etc.NoNo
345CONCEPT_CLASSconcept_class_concept_idYesintegerA Concept that represents the Concept Class.NoYesCONCEPTCONCEPT_ID
346CONCEPT_RELATIONSHIPconcept_id_1YesintegerNoYesCONCEPTCONCEPT_ID
347CONCEPT_RELATIONSHIPconcept_id_2YesintegerNoYesCONCEPTCONCEPT_ID
348CONCEPT_RELATIONSHIPrelationship_idYesvarchar(20)The relationship between CONCEPT_ID_1 and CONCEPT_ID_2. Please see the [Vocabulary Conventions](https://ohdsi.github.io/CommonDataModel/dataModelConventions.html#concept_relationships). for more information. NoYesRELATIONSHIPRELATIONSHIP_ID
349CONCEPT_RELATIONSHIPvalid_start_dateYesdateThe date when the relationship is first recorded.NoNo
350CONCEPT_RELATIONSHIPvalid_end_dateYesdateThe date when the relationship is invalidated.NoNo
351CONCEPT_RELATIONSHIPinvalid_reasonNovarchar(1)Reason the relationship was invalidated. Possible values are 'D' (deleted), 'U' (updated) or NULL. NoNo
352RELATIONSHIPrelationship_idYesvarchar(20)The type of relationship captured by the relationship record.YesNo
353RELATIONSHIPrelationship_nameYesvarchar(255)NoNo
354RELATIONSHIPis_hierarchicalYesvarchar(1)Defines whether a relationship defines concepts into classes or hierarchies. Values are 1 for hierarchical relationship or 0 if not.NoNo
355RELATIONSHIPdefines_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.NoNo
356RELATIONSHIPreverse_relationship_idYesvarchar(20)The identifier for the relationship used to define the reverse relationship between two concepts.NoNo
357RELATIONSHIPrelationship_concept_idYesintegerA foreign key that refers to an identifier in the [CONCEPT](https://ohdsi.github.io/CommonDataModel/cdm531.html#concept) table for the unique relationship concept.NoYesCONCEPTCONCEPT_ID
358CONCEPT_SYNONYMconcept_idYesintegerNoYesCONCEPTCONCEPT_ID
359CONCEPT_SYNONYMconcept_synonym_nameYesvarchar(1000)NoNo
360CONCEPT_SYNONYMlanguage_concept_idYesintegerNoYesCONCEPTCONCEPT_ID
361CONCEPT_ANCESTORancestor_concept_idYesintegerThe Concept Id for the higher-level concept that forms the ancestor in the relationship.NoYesCONCEPTCONCEPT_ID
362CONCEPT_ANCESTORdescendant_concept_idYesintegerThe Concept Id for the lower-level concept that forms the descendant in the relationship.NoYesCONCEPTCONCEPT_ID
363CONCEPT_ANCESTORmin_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.NoNo
364CONCEPT_ANCESTORmax_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.NoNo
365SOURCE_TO_CONCEPT_MAPsource_codeYesvarchar(50)The source code being translated into a Standard Concept.NoNo
366SOURCE_TO_CONCEPT_MAPsource_concept_idYesintegerA foreign key to the Source Concept that is being translated into a Standard Concept.This is either 0 or should be a number above 2 billion, which are the Concepts reserved for site-specific codes and mappings. NoYesCONCEPTCONCEPT_ID
367SOURCE_TO_CONCEPT_MAPsource_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.NoNo
368SOURCE_TO_CONCEPT_MAPsource_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.NoNo
369SOURCE_TO_CONCEPT_MAPtarget_concept_idYesintegerThe target Concept to which the source code is being mapped.NoYesCONCEPTCONCEPT_ID
370SOURCE_TO_CONCEPT_MAPtarget_vocabulary_idYesvarchar(20)The Vocabulary of the target Concept.NoYesVOCABULARYVOCABULARY_ID
371SOURCE_TO_CONCEPT_MAPvalid_start_dateYesdateThe date when the mapping instance was first recorded.NoNo
372SOURCE_TO_CONCEPT_MAPvalid_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.NoNo
373SOURCE_TO_CONCEPT_MAPinvalid_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.NoNo
374DRUG_STRENGTHdrug_concept_idYesintegerThe Concept representing the Branded Drug or Clinical Drug Product.NoYesCONCEPTCONCEPT_ID
375DRUG_STRENGTHingredient_concept_idYesintegerThe Concept representing the active ingredient contained within the drug product.Combination Drugs will have more than one record in this table, one for each active Ingredient.NoYesCONCEPTCONCEPT_ID
376DRUG_STRENGTHamount_valueNofloatThe numeric value or the amount of active ingredient contained within the drug product.NoNo
377DRUG_STRENGTHamount_unit_concept_idNointegerThe Concept representing the Unit of measure for the amount of active ingredient contained within the drug product. NoYesCONCEPTCONCEPT_ID
378DRUG_STRENGTHnumerator_valueNofloatThe concentration of the active ingredient contained within the drug product.NoNo
379DRUG_STRENGTHnumerator_unit_concept_idNointegerThe Concept representing the Unit of measure for the concentration of active ingredient.NoYesCONCEPTCONCEPT_ID
380DRUG_STRENGTHdenominator_valueNofloatThe amount of total liquid (or other divisible product, such as ointment, gel, spray, etc.).NoNo
381DRUG_STRENGTHdenominator_unit_concept_idNointegerThe Concept representing the denominator unit for the concentration of active ingredient.NoYesCONCEPTCONCEPT_ID
382DRUG_STRENGTHbox_sizeNointegerThe number of units of Clinical Branded Drug or Quantified Clinical or Branded Drug contained in a box as dispensed to the patient.NoNo
383DRUG_STRENGTHvalid_start_dateYesdateThe date when the Concept was first recorded. The default value is <<<<<<< HEAD:inst/csv/OMOP_CDMv5.3_Field_Level.csv 1-Jan-1970.NoNo
384DRUG_STRENGTHvalid_end_dateYesdateThe date when then Concept became invalid.NoNo
385DRUG_STRENGTHinvalid_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.NoNo
386COHORT_DEFINITIONcohort_definition_idYesintegerThis is the identifier given to the cohort, usually by the ATLAS applicationNoNo
387COHORT_DEFINITIONcohort_definition_nameYesvarchar(255)A short description of the cohortNoNo
388COHORT_DEFINITIONcohort_definition_descriptionNovarchar(MAX)A complete description of the cohort.NoNo
389COHORT_DEFINITIONdefinition_type_concept_idYesintegerType defining what kind of Cohort Definition the record represents and how the syntax may be executed.NoYesCONCEPTCONCEPT_ID
390COHORT_DEFINITIONcohort_definition_syntaxNovarchar(MAX)Syntax or code to operationalize the Cohort Definition.NoNo
391COHORT_DEFINITIONsubject_concept_idYesintegerThis field contains a Concept that represents the domain of the subjects that are members of the cohort (e.g., Person, Provider, Visit).NoYesCONCEPTCONCEPT_ID
392COHORT_DEFINITIONcohort_initiation_dateNodateA date to indicate when the Cohort was initiated in the COHORT table.NoNo
393ATTRIBUTE_DEFINITIONattribute_definition_idYesintegerNoNo
394ATTRIBUTE_DEFINITIONattribute_nameYesvarchar(255)NoNo
395ATTRIBUTE_DEFINITIONattribute_descriptionNovarchar(MAX)NoNo
396ATTRIBUTE_DEFINITIONattribute_type_concept_idYesintegerNoYesCONCEPTCONCEPT_ID
397ATTRIBUTE_DEFINITIONattribute_syntaxNovarchar(MAX)NoNo