OMOP/docs/inst/csv/OMOP_CDMv5.3.1_Field_Level.csv

1	cdmTableName	cdmFieldName	isRequired	isRequiredThreshold	cdmDatatype	cdmDatatypeThreshold	userGuidance	etlConventions	isPrimaryKey	isPrimaryKeyThreshold	isForeignKey	isForeignKeyThreshold	fkTableName	fkFieldName	fkDomain	fkDomainThreshold	fkClass	fkClassThreshold	isStandardValidConcept	isStandardValidConceptThreshold	measureValueCompleteness	measureValueCompletenessThreshold	standardConceptRecordCompleteness	standardConceptRecordCompletenessThreshold	sourceConceptRecordCompleteness	sourceConceptRecordCompletenessThreshold	sourceValueCompleteness	sourceValueCompletenessThreshold	standardConceptFieldName	plausibleValueLow	plausibleValueLowThreshold	plausibleValueHigh	plausibleValueHighThreshold	plausibleTemporalAfterTableName	plausibleTemporalAfterFieldName	plausibleTemporalAfterThreshold	plausibleDuringLife	plausibleDuringLifeThreshold
2	PERSON	person_id	Yes	0	integer	0	It 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 identify unique persons should be done prior to ETL.	Yes	0	No								No		Yes	100	No		No		No										No
3	PERSON	gender_concept_id	Yes	0	integer	0	This 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 table.	No		Yes	0	CONCEPT	CONCEPT_ID	Gender	0			Yes	0	Yes	100	Yes	0	No		No										No
4	PERSON	year_of_birth	Yes	0	integer	0		For data sources with date of birth, the year is extracted. For data sources where the year of birth is not available, the approximate year of birth is derived based on any age group categorization available.	No		No								No		Yes	100	No		No		No			1850	0	YEAR(GETDATE())+1	0				No
5	PERSON	month_of_birth	No		integer	0		For data sources that provide the precise date of birth, the month is extracted and stored in this field.	No		No								No		Yes	100	No		No		No			1	0	12	0				No
6	PERSON	day_of_birth	No		integer	0		For data sources that provide the precise date of birth, the day is extracted and stored in this field.	No		No								No		Yes	100	No		No		No			1	0	31	0				No
7	PERSON	birth_datetime	No		datetime	0	Compute age using birth_datetime.	For data sources that provide the precise datetime of birth, store that value 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 month/1/year. If month_of_birth is null then use 1/day/year, if day_of_birth is null and month_of_birth is null then 1/1/year. If time of birth is not given use midnight (00:00:0000).	No		No								No		Yes	100	No		No		No			'1850-01-01'	0	DATEADD(dd,1,GETDATE())	0				No
8	PERSON	race_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Race	0			Yes	0	Yes	100	Yes	0	No		No										No
9	PERSON	ethnicity_concept_id	Yes	0	integer	0	Ethnic backgrounds as subsets of race. The OMOP CDM adheres to the OMB standards so only Concepts that represent "Hispanic" and "Not Hispanic" are stored here. If a source has more granular ethnicity information it can be found in the field ethnicity_source_value.	Ethnicity in the OMOP CDM follows the OMB Standards for Data on Race and Ethnicity: Only distinctions between Hispanics and Non-Hispanics are made. If a source provides more granular ethnicity information it should be stored in the field ethnicity_source_value.	No		Yes	0	CONCEPT	CONCEPT_ID	Ethnicity	0			Yes	0	Yes	100	Yes	0	No		No										No
10	PERSON	location_id	No		integer	0	The location refers to the physical address of the person.	Put the location_id from the LOCATION table here that represents the most granular location information for the person. This could be zip code, state, or county for example.	No		Yes	0	LOCATION	LOCATION_ID					No		Yes	100	No		No		No										No
11	PERSON	provider_id	No		integer	0	The Provider refers to the last known primary care provider (General Practitioner).	Put the provider_id from the PROVIDER table of the last known general practitioner of the person.	No		Yes	0	PROVIDER	PROVIDER_ID					No		Yes	100	No		No		No										No
12	PERSON	care_site_id	No		integer	0	The Care Site refers to where the Provider typically provides the primary care.		No		Yes	0	CARE_SITE	CARE_SITE_ID					No		Yes	100	No		No		No										No
13	PERSON	person_source_value	No		varchar(50)	0	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.	No		No								No		Yes	100	No		No		No										No
14	PERSON	gender_source_value	No		varchar(50)	0	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.	No		No								No		Yes	100	No		No		Yes	0	GENDER_CONCEPT_ID								No
15	PERSON	gender_source_concept_id	No		Integer	0		If the source data codes biological sex in a non-standard vocabulary, store the concept_id here.	No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		Yes	0	No										No
16	PERSON	race_source_value	No		varchar(50)	0	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.	No		No								No		Yes	100	No		No		Yes	0	RACE_CONCEPT_ID								No
17	PERSON	race_source_concept_id	No		Integer	0		If the source data codes race in an OMOP supported vocabulary store the concept_id here.	No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		Yes	0	No										No
18	PERSON	ethnicity_source_value	No		varchar(50)	0	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.	No		No								No		Yes	100	No		No		Yes	0	ETHNICITY_CONCEPT_ID								No
19	PERSON	ethnicity_source_concept_id	No		Integer	0		If the source data codes ethnicity in an OMOP supported vocabulary, store the concept_id here.	No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		Yes	0	No										No
20	OBSERVATION_PERIOD	observation_period_id	Yes	0	integer	0	A Person can have multiple discrete observations periods which are identified by the Observation_Period_Id. It is assumed that the observation period covers the period of time for which we know events occurred for the Person. In the context of the Common Data Model the absence of events during an observation period implies that the event did not occur.	Assign a unique observation_period_id to each discrete observation period for a Person. An observation period should the length of time for which we know events occurred for the Person. It may take some logic to define an observation period, especially when working with EHR or registry data. Often if no enrollment or coverage information is given an observation period is defined as the time between the earliest record and the latest record available for a person.	Yes	0	No								No		Yes	100	No		No		No										No
21	OBSERVATION_PERIOD	person_id	Yes	0	integer	0			No		Yes	0	PERSON	PERSON_ID					No		Yes	100	No		No		No										No
22	OBSERVATION_PERIOD	observation_period_start_date	Yes	0	date	0	Use this date to determine the start date of the period for which we can assume that all events for a Person are recorded and any absense of records indicates an absence of events.	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 US claims, the observation period can be considered as the time period the person is enrolled with an insurer. If a Person switches plans but stays with the same insurer, that change would be captured in payer_plan_period.	No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
23	OBSERVATION_PERIOD	observation_period_end_date	Yes	0	date	0	Use this date to determine the end date of the period for which we can assume that all events for a Person are recorded and any absense of records indicates an absence of events.	It is often the case that the idea of observation periods does not exist in source data. In those cases the observation_period_start_end_date can be inferred as the latest event date available for the Person. The event dates include insurance enrollment dates.	No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	OBSERVATION_PERIOD	OBSERVATION_PERIOD_START_DATE	0	Yes	0
24	OBSERVATION_PERIOD	period_type_concept_id	Yes	0	Integer	0	This field can be used to determine the provenance of the observation period as in whether the period was determined from an insurance enrollment file or if it was determined from EHR healthcare encounters.	Choose the observation_period_type_concept_id that best represents how the period was determined.	No		Yes	0	CONCEPT	CONCEPT_ID	Type Concept	0			Yes	0	Yes	100	Yes	0	No		No										No
25	VISIT_OCCURRENCE	visit_occurrence_id	Yes	0	integer	0	Use 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.	Yes	0	No								No		Yes	100	No		No		No										No
26	VISIT_OCCURRENCE	person_id	Yes	0	integer	0			No		Yes	0	PERSON	PERSON_ID					No		Yes	100	No		No		No										No
27	VISIT_OCCURRENCE	visit_concept_id	Yes	0	integer	0	This field contains a concept id representing the kind of visit, like inpatient or outpatient.	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. It is often the case that some logic should be written for how to define visits and how to assign Visit_Concept_Id. In US claims outpatient visits that appear to occur within the time period of an inpatient visit can be rolled into one with the same Visit_Occurrence_Id. In EHR data inpatient visits that are within one day of each other may be strung together to create one visit. It will all depend on the source data and how encounter records should be translated to visit occurrences.	No		Yes	0	CONCEPT	CONCEPT_ID	Visit	0			Yes	0	Yes	100	Yes	0	No		No										No
28	VISIT_OCCURRENCE	visit_start_date	Yes	0	date	0	For 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 will first have to make decisions on how to define visits. In some cases visits in the source data can be strung together if there are one or fewer days between them.	No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
29	VISIT_OCCURRENCE	visit_start_datetime	No		datetime	0		If no time is given for the start date of a visit, set it to midnight (00:00:0000).	No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
30	VISIT_OCCURRENCE	visit_end_date	Yes	0	date	0	For 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.	No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	VISIT_OCCURRENCE	VISIT_START_DATE	0	Yes	0
31	VISIT_OCCURRENCE	visit_end_datetime	No		datetime	0		If no time is given for the end date of a visit, set it to midnight (00:00:0000).	No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	VISIT_OCCURRENCE	VISIT_START_DATETIME	0	Yes	0
32	VISIT_OCCURRENCE	visit_type_concept_id	Yes	0	Integer	0	Use 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.	No		Yes	0	CONCEPT	CONCEPT_ID	Type Concept	0			Yes	0	Yes	100	Yes	0	No		No										No
33	VISIT_OCCURRENCE	provider_id	No		integer	0	There will only be one provider per visit. If multiple providers are associated with a visit that information can be found 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 table.	No		No		PROVIDER	PROVIDER_ID					No		Yes	100	No		No		No										No
34	VISIT_OCCURRENCE	care_site_id	No		integer	0	This field provides information about the care site where the visit took place.	There should only be one care site associated with a visit.	No		No		CARE_SITE	CARE_SITE_ID					No		Yes	100	No		No		No										No
35	VISIT_OCCURRENCE	visit_source_value	No		varchar(50)	0	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.	No		No								No		Yes	100	No		No		Yes	0	VISIT_CONCEPT_ID								No
36	VISIT_OCCURRENCE	visit_source_concept_id	No		integer	0		If the visit source value is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.	No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		Yes	0	No										No
37	VISIT_OCCURRENCE	admitting_source_concept_id	No		integer	0	Use 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.	No		Yes	0	CONCEPT	CONCEPT_ID	Visit	0			Yes	0	Yes	100	Yes	0	No		No										No
38	VISIT_OCCURRENCE	admitting_source_value	No		varchar(50)	0		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.	No		No								No		Yes	100	No		No		Yes	0	ADMITTING_SOURCE_CONCEPT_ID								No
39	VISIT_OCCURRENCE	discharge_to_concept_id	No		integer	0	Use 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.	No		Yes	0	CONCEPT	CONCEPT_ID	Visit	0			Yes	0	Yes	100	Yes	0	No		No										No
40	VISIT_OCCURRENCE	discharge_to_source_value	No		varchar(50)	0		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.	No		No								No		Yes	100	No		No		Yes	0	DISCHARGE_TO_CONCEPT_ID								No
41	VISIT_OCCURRENCE	preceding_visit_occurrence_id	No		integer	0	Use this field to find the visit that occured for the person prior to the given visit. There could be a few days or a few years in between.	The preceding_visit_id 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".	No		Yes	0	VISIT_OCCURRENCE	VISIT_OCCURRENCE_ID					No		Yes	100	No		No		No										No
42	CONDITION_OCCURRENCE	condition_occurrence_id	Yes	0	bigint	0			Yes	0	No								No		Yes	100	No		No		No										No
43	CONDITION_OCCURRENCE	person_id	Yes	0	bigint	0			No		Yes	0	PERSON	PERSON_ID					No		Yes	100	No		No		No										No
44	CONDITION_OCCURRENCE	condition_concept_id	Yes	0	integer	0	The CONDITION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies		No		Yes	0	CONCEPT	CONCEPT_ID	Condition	0			Yes	0	Yes	100	Yes	0	No		No										No
45	CONDITION_OCCURRENCE	condition_start_date	Yes	0	date	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
46	CONDITION_OCCURRENCE	condition_start_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
47	CONDITION_OCCURRENCE	condition_end_date	No		date	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	CONDITION_OCCURRENCE	CONDITION_START_DATE	0	Yes	0
48	CONDITION_OCCURRENCE	condition_end_datetime	No		datetime	0		should not be inferred	No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	CONDITION_OCCURRENCE	CONDITION_START_DATETIME	0	Yes	0
49	CONDITION_OCCURRENCE	condition_type_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Type Concept	0			Yes	0	Yes	100	Yes	0	No		No										No
50	CONDITION_OCCURRENCE	condition_status_concept_id	No		integer	0		Presently, there is no designated vocabulary, domain, or class that represents condition status. The following concepts from SNOMED are recommended: Admitting diagnosis: 4203942 Final diagnosis: 4230359 (should also be used for discharge diagnosis Preliminary diagnosis: 4033240	No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	Yes	0	No		No										No
51	CONDITION_OCCURRENCE	stop_reason	No		varchar(20)	0	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.		No		No								No		Yes	100	No		No		No										No
52	CONDITION_OCCURRENCE	provider_id	No		integer	0			No		Yes	0	PROVIDER	PROVIDER_ID					No		Yes	100	No		No		No										No
53	CONDITION_OCCURRENCE	visit_occurrence_id	No		integer	0			No		Yes	0	VISIT_OCCURRENCE	VISIT_OCCURRENCE_ID					No		Yes	100	No		No		No										No
54	CONDITION_OCCURRENCE	visit_detail_id	No		integer	0			No		Yes	0	VISIT_DETAIL	VISIT_DETAIL_ID					No		Yes	100	No		No		No										No
55	CONDITION_OCCURRENCE	condition_source_value	No		varchar(50)	0	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.	This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.	No		No								No		Yes	100	No		No		Yes	0	CONDITION_CONCEPT_ID								No
56	CONDITION_OCCURRENCE	condition_source_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		Yes	0	No										No
57	CONDITION_OCCURRENCE	condition_status_source_value	No		varchar(50)	0		This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference.	No		No								No		Yes	100	No		No		Yes	0	CONDITION_STATUS_CONCEPT_ID								No
58	DRUG_EXPOSURE	drug_exposure_id	Yes	0	bigint	0			Yes		No								No		Yes	100	No		No		No										No
59	DRUG_EXPOSURE	person_id	Yes	0	bigint	0			No		Yes		PERSON	PERSON_ID					No		Yes	100	No		No		No										No
60	DRUG_EXPOSURE	drug_concept_id	Yes	0	integer	0			No		Yes		CONCEPT	CONCEPT_ID	Drug				Yes		Yes	100	Yes	0	No		No										No
61	DRUG_EXPOSURE	drug_exposure_start_date	Yes	0	date	0		Valid entries include a start date of a prescription, the date a prescription was filled, or the date on which a Drug administration procedure was recorded.	No		No								No		Yes	100	No		No		No			'1950-01-01'		DATEADD(dd,1,GETDATE())		PERSON	BIRTH_DATETIME		Yes	0
62	DRUG_EXPOSURE	drug_exposure_start_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No			'1950-01-01'		DATEADD(dd,1,GETDATE())		PERSON	BIRTH_DATETIME		Yes	0
63	DRUG_EXPOSURE	drug_exposure_end_date	Yes	0	date	0		The DRUG_EXPOSURE_END_DATE denotes the day the drug exposure ended for the patient. This could be that the duration of DRUG_SUPPLY was reached (in which case DRUG_EXPOSURE_END_DATETIME = DRUG_EXPOSURE_START_DATETIME + DAYS_SUPPLY -1 day), or because the exposure was stopped (medication changed, medication discontinued, etc.) When the native data suggests a drug exposure has a days supply less than 0, drop the record as unknown if a person has received the drug or not (THEMIS issue #24). If a patient has multiple records on the same day for the same drug or procedures the ETL should not de-dupe them unless there is probable reason to believe the item is a true data duplicate (THEMIS issue #14). Depending on different sources, it could be a known or an inferred date and denotes the last day at which the patient was still exposed to Drug.	No		No								No		Yes	100	No		No		No			'1950-01-01'		DATEADD(dd,1,GETDATE())		DRUG_EXPOSURE	DRUG_EXPOSURE_START_DATE		Yes	0
64	DRUG_EXPOSURE	drug_exposure_end_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No			'1950-01-01'		DATEADD(dd,1,GETDATE())		DRUG_EXPOSURE	DRUG_EXPOSURE_START_DATETIME		Yes	0
65	DRUG_EXPOSURE	verbatim_end_date	No		date	0	You can use the TYPE_CONCEPT_ID to delineate between prescriptions written vs. prescriptions dispensed vs. medication history vs. patient-reported exposure		No		No								No		Yes	100	No		No		No			'1950-01-01'		DATEADD(dd,1,GETDATE())		DRUG_EXPOSURE	DRUG_EXPOSURE_START_DATE		Yes	0
66	DRUG_EXPOSURE	drug_type_concept_id	Yes	0	integer	0			No		Yes		CONCEPT	CONCEPT_ID	Type Concept				Yes		Yes	100	Yes	0	No		No										No
67	DRUG_EXPOSURE	stop_reason	No		varchar(20)	0		Reasons include regimen completed, changed, removed, etc.	No		No								No		Yes	100	No		No		No										No
68	DRUG_EXPOSURE	refills	No		integer	0	The content of the refills field determines the current number of refills, not the number of remaining refills. For example, for a drug prescription with 2 refills, the content of this field for the 3 Drug Exposure events are null, 1 and 2.		No		No								No		Yes	100	No		No		No			0		12					No
69	DRUG_EXPOSURE	quantity	No		float	0			No		No								No		Yes	100	No		No		No			0		1095					No
70	DRUG_EXPOSURE	days_supply	No		integer	0			No		No								No		Yes	100	No		No		No			0		365					No
71	DRUG_EXPOSURE	sig	No		varchar(MAX)	0	(and printed on the container)		No		No								No		Yes	100	No		No		No										No
72	DRUG_EXPOSURE	route_concept_id	No		integer	0	Route information can also be inferred from the Drug product itself by determining the Drug Form of the Concept, creating some partial overlap of the same type of information. Therefore, route information should be stored in DRUG_CONCEPT_ID (as a drug with corresponding Dose Form). The ROUTE_CONCEPT_ID could be used for storing more granular forms e.g. 'Intraventricular cardiac'.		No		Yes		CONCEPT	CONCEPT_ID	Route				Yes		Yes	100	Yes	0	No		No										No
73	DRUG_EXPOSURE	lot_number	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
74	DRUG_EXPOSURE	provider_id	No		integer	0			No		Yes		PROVIDER	PROVIDER_ID					No		Yes	100	No		No		No										No
75	DRUG_EXPOSURE	visit_occurrence_id	No		integer	0			No		Yes		VISIT_OCCURRENCE	VISIT_OCCURRENCE_ID					No		Yes	100	No		No		No										No
76	DRUG_EXPOSURE	visit_detail_id	No		integer	0			No		Yes		VISIT_DETAIL	VISIT_DETAIL_ID					No		Yes	100	No		No		No										No
77	DRUG_EXPOSURE	drug_source_value	No		varchar(50)	0		This code is mapped to a Standard Drug concept in the Standardized Vocabularies and the original code is, stored here for reference.	No		No								No		Yes	100	No		No		Yes		DRUG_CONCEPT_ID								No
78	DRUG_EXPOSURE	drug_source_concept_id	No		integer	0			No		Yes		CONCEPT	CONCEPT_ID					No		Yes	100	No		Yes		No										No
79	DRUG_EXPOSURE	route_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes		ROUTE_CONCEPT_ID								No
80	DRUG_EXPOSURE	dose_unit_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
81	PROCEDURE_OCCURRENCE	procedure_occurrence_id	Yes	0	integer	0			Yes	0	No								No		Yes	100	No		No		No										No
82	PROCEDURE_OCCURRENCE	person_id	Yes	0	integer	0			No		Yes	0	PERSON	PERSON_ID					No		Yes	100	No		No		No										No
83	PROCEDURE_OCCURRENCE	procedure_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Procedure	0			Yes	0	Yes	100	Yes	0	No		No										No
84	PROCEDURE_OCCURRENCE	procedure_date	Yes	0	date	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
85	PROCEDURE_OCCURRENCE	procedure_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
86	PROCEDURE_OCCURRENCE	procedure_type_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Type Concept	0			Yes	0	Yes	100	Yes	0	No		No										No
87	PROCEDURE_OCCURRENCE	modifier_concept_id	No		integer	0	These concepts are typically distinguished by 'Modifier' concept classes (e.g., 'CPT4 Modifier' as part of the 'CPT4' vocabulary).		No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	Yes	0	No		No										No
88	PROCEDURE_OCCURRENCE	quantity	No		integer	0	If 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 once (THEMIS issue #26).	No		No								No		Yes	100	No		No		No			1	0						No
89	PROCEDURE_OCCURRENCE	provider_id	No		integer	0			No		No		PROVIDER	PROVIDER_ID					No		Yes	100	No		No		No										No
90	PROCEDURE_OCCURRENCE	visit_occurrence_id	No		integer	0			No		No		VISIT_OCCURRENCE	VISIT_OCCURRENCE_ID					No		Yes	100	No		No		No										No
91	PROCEDURE_OCCURRENCE	visit_detail_id	No		integer	0			No		No		VISIT_DETAIL	VISIT_DETAIL_ID					No		Yes	100	No		No		No										No
92	PROCEDURE_OCCURRENCE	procedure_source_value	No		varchar(50)	0		This code is mapped to a standard procedure Concept in the Standardized Vocabularies and the original code is, stored here for reference. Procedure source codes are typically ICD-9-Proc, CPT-4, HCPCS or OPCS-4 codes.	No		No								No		Yes	100	No		No		Yes	0	PROCEDURE_CONCEPT_ID								No
93	PROCEDURE_OCCURRENCE	procedure_source_concept_id	No		integer	0			No		No		CONCEPT	CONCEPT_ID					No		Yes	100	No		Yes	0	No										No
94	PROCEDURE_OCCURRENCE	modifier_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	MODIFIER_CONCEPT_ID								No
95	DEVICE_EXPOSURE	device_exposure_id	Yes	0	bigint	0			Yes	0	No								No		Yes	100	No		No		No										No
96	DEVICE_EXPOSURE	person_id	Yes	0	bigint	0			No		Yes	0	PERSON	PERSON_ID					No		Yes	100	No		No		No										No
97	DEVICE_EXPOSURE	device_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Device	0			Yes	0	Yes	100	Yes	0	No		No										No
98	DEVICE_EXPOSURE	device_exposure_start_date	Yes	0	date	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
99	DEVICE_EXPOSURE	device_exposure_start_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
100	DEVICE_EXPOSURE	device_exposure_end_date	No		date	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	DEVICE_EXPOSURE	DEVICE_EXPOSURE_START_DATE	0	Yes	0
101	DEVICE_EXPOSURE	device_exposure_end_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	DEVICE_EXPOSURE	DEVICE_EXPOSURE_START_DATETIME	0	Yes	0
102	DEVICE_EXPOSURE	device_type_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Type Concept	0			Yes	0	Yes	100	Yes	0	No		No										No
103	DEVICE_EXPOSURE	unique_device_id	No		varchar(50)	0		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.	No		No								No		Yes	100	No		No		No										No
104	DEVICE_EXPOSURE	quantity	No		integer	0			No		No								No		Yes	100	No		No		No			1	0						No
105	DEVICE_EXPOSURE	provider_id	No		integer	0			No		Yes	0	PROVIDER	PROVIDER_ID					No		Yes	100	No		No		No										No
106	DEVICE_EXPOSURE	visit_occurrence_id	No		integer	0			No		Yes	0	VISIT_OCCURRENCE	VISIT_OCCURRENCE_ID					No		Yes	100	No		No		No										No
107	DEVICE_EXPOSURE	visit_detail_id	No		integer	0			No		Yes	0	VISIT_DETAIL	VISIT_DETAIL_ID					No		Yes	100	No		No		No										No
108	DEVICE_EXPOSURE	device_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	DEVICE_CONCEPT_ID								No
109	DEVICE_EXPOSURE	device_source_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		Yes	0	No										No
110	MEASUREMENT	measurement_id	Yes	0	integer	0			Yes	0	No								No		Yes	100	No		No		No										No
111	MEASUREMENT	person_id	Yes	0	integer	0			No		Yes	0	PERSON	PERSON_ID					No		Yes	100	No		No		No										No
112	MEASUREMENT	measurement_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Measurement	0			Yes	0	Yes	100	Yes	0	No		No										No
113	MEASUREMENT	measurement_date	Yes	0	date	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	No
114	MEASUREMENT	measurement_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No										No
115	MEASUREMENT	measurement_time	No		varchar(10)	0	This is present for backwards compatibility and will be deprecated in an upcoming version		No		No								No		Yes	100	No		No		No										No
116	MEASUREMENT	measurement_type_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Type Concept	0			Yes	0	Yes	100	Yes	0	No		No										No
117	MEASUREMENT	operator_concept_id	No		integer	0	The meaning of Concept 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 =.	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): 1925-7 Base excess in Arterial blood by calculation 1927-3 Base excess in Venous blood by calculation Operators are <, <=, =, >=, > and these concepts belong to the 'Meas Value Operator' domain. 8632-2 QRS-Axis 11555-0 Base excess in Blood by calculation 1926-5 Base excess in Capillary blood by calculation 28638-5 Base excess in Arterial cord blood by calculation 28639-3 Base excess in Venous cord blood by calculation THEMIS issue #16	No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	No		No		No										No
118	MEASUREMENT	value_as_number	No		float	0			No		No								No		Yes	100	No		No		No										No
119	MEASUREMENT	value_as_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
120	MEASUREMENT	unit_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Unit	0			Yes	0	Yes	100	Yes	0	No		No										No
121	MEASUREMENT	range_low	No		float	0	Ranges have the same unit as the VALUE_AS_NUMBER.	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. Ranges have the same unit as the VALUE_AS_NUMBER.	No		No								No		Yes	100	No		No		No										No
122	MEASUREMENT	range_high	No		float	0	Ranges have the same unit as the VALUE_AS_NUMBER.		No		No								No		Yes	100	No		No		No										No
123	MEASUREMENT	provider_id	No		integer	0			No		Yes	0	PROVIDER	PROVIDER_ID					No		Yes	100	No		No		No										No
124	MEASUREMENT	visit_occurrence_id	No		integer	0			No		Yes	0	VISIT_OCCURRENCE	VISIT_OCCURRENCE_ID					No		Yes	100	No		No		No										No
125	MEASUREMENT	visit_detail_id	No		integer	0			No		Yes	0	VISIT_DETAIL	VISIT_DETAIL_ID					No		Yes	100	No		No		No										No
126	MEASUREMENT	measurement_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	MEASUREMENT_CONCEPT_ID								No
127	MEASUREMENT	measurement_source_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		Yes	0	No										No
128	MEASUREMENT	unit_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	UNIT_CONCEPT_ID								No
129	MEASUREMENT	value_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
130	VISIT_DETAIL	visit_detail_id	Yes	0	integer	0			Yes	0	No								No		Yes	100	No		No		No										No
131	VISIT_DETAIL	person_id	Yes	0	integer	0			No		Yes	0	PERSON	PERSON_ID					No		Yes	100	No		No		No										No
132	VISIT_DETAIL	visit_detail_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Visit	0			Yes	0	Yes	100	Yes	0	No		No										No
133	VISIT_DETAIL	visit_detail_start_date	Yes	0	date	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
134	VISIT_DETAIL	visit_detail_start_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
135	VISIT_DETAIL	visit_detail_end_date	Yes	0	date	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	VISIT_OCCURRENCE	VISIT_DETAIL_START_DATE	0	Yes	0
136	VISIT_DETAIL	visit_detail_end_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	VISIT_OCCURRENCE	VISIT_DETAIL_START_DATETIME	0	Yes	0
137	VISIT_DETAIL	visit_detail_type_concept_id	Yes	0	Integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Type Concept	0			Yes	0	Yes	100	Yes	0	No		No										No
138	VISIT_DETAIL	provider_id	No		integer	0			No		Yes	0	PROVIDER	PROVIDER_ID					No		Yes	100	No		No		No										No
139	VISIT_DETAIL	care_site_id	No		integer	0			No		Yes	0	CARE_SITE	CARE_SITE_ID					No		Yes	100	No		No		No										No
140	VISIT_DETAIL	visit_detail_source_value	No		string(50)	0			No		No								No		Yes	100	No		No		Yes	0	VISIT_DETAIL_CONCEPT_ID								No
141	VISIT_DETAIL	visit_detail_source_concept_id	No		Integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		Yes	0	No										No
142	VISIT_DETAIL	admitting_source_value	No		Varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	ADMITTING_SOURCE_CONCEPT_ID								No
143	VISIT_DETAIL	admitting_source_concept_id	No		Integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	Yes	0	Yes	0	No										No
144	VISIT_DETAIL	discharge_to_source_value	No		Varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	DISCHARGE_TO_CONCEPT_ID								No
145	VISIT_DETAIL	discharge_to_concept_id	No		Integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	Yes	0	No		No										No
146	VISIT_DETAIL	preceding_visit_detail_id	No		Integer	0			No		Yes	0	VISIT_DETAIL	VISIT_DETAIL_ID					No		Yes	100	No		No		No										No
147	VISIT_DETAIL	visit_detail_parent_id	No		Integer	0			No		Yes	0	VISIT_DETAIL	VISIT_DETAIL_ID					No		Yes	100	No		No		No										No
148	VISIT_DETAIL	visit_occurrence_id	Yes	0	Integer	0			No		Yes	0	VISIT_OCCURRENCE	VISIT_OCCURRENCE_ID					No		Yes	100	No		No		No										No
149	NOTE	note_id	Yes	0	integer	0			Yes	0	No								No		Yes	100	No		No		No										No
150	NOTE	person_id	Yes	0	integer	0			No		Yes	0	PERSON	PERSON_ID					No		Yes	100	No		No		No										No
151	NOTE	note_date	Yes	0	date	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	No
152	NOTE	note_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	No
153	NOTE	note_type_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Type Concept	0			Yes	0	Yes	100	No		No		No										No
154	NOTE	note_class_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	No		No		No										No
155	NOTE	note_title	No		varchar(250)	0			No		No								No		Yes	100	No		No		No										No
156	NOTE	note_text	Yes	0	varchar(MAX)	0			No		No								No		Yes	100	No		No		No										No
157	NOTE	encoding_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	No		No		No										No
158	NOTE	language_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	No		No		No										No
159	NOTE	provider_id	No		integer	0			No		Yes	0	PROVIDER	PROVIDER_ID					No		Yes	100	No		No		No										No
160	NOTE	visit_occurrence_id	No		integer	0			No		Yes	0	VISIT_OCCURRENCE	VISIT_OCCURRENCE_ID					No		Yes	100	No		No		No										No
161	NOTE	visit_detail_id	No		integer	0			No		Yes	0	VISIT_DETAIL	VISIT_DETAIL_ID					No		Yes	100	No		No		No										No
162	NOTE	note_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
163	NOTE_NLP	note_nlp_id	Yes	0	integer	0			Yes	0	No								No		Yes	100	No		No		No										No
164	NOTE_NLP	note_id	Yes	0	integer	0			No		No								No		Yes	100	No		No		No										No
165	NOTE_NLP	section_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	No		No		No										No
166	NOTE_NLP	snippet	No		varchar(250)	0			No		No								No		Yes	100	No		No		No										No
167	NOTE_NLP	offset	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
168	NOTE_NLP	lexical_variant	Yes	0	varchar(250)	0			No		No								No		Yes	100	No		No		No										No
169	NOTE_NLP	note_nlp_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	No		No		No										No
170	NOTE_NLP	note_nlp_source_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
171	NOTE_NLP	nlp_system	No		varchar(250)	0			No		No								No		Yes	100	No		No		No										No
172	NOTE_NLP	nlp_date	Yes	0	date	0			No		No								No		Yes	100	No		No		No										No
173	NOTE_NLP	nlp_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0				No
174	NOTE_NLP	term_exists	No		varchar(1)	0		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.	No		No								No		Yes	100	No		No		No										No
175	NOTE_NLP	term_temporal	No		varchar(50)	0		Term_temporal is to indicate if a condition is <20>present<6E> or just in the <20>past<73>. The following would be past: History = true Concept_date = anything before the time of the report	No		No								No		Yes	100	No		No		No										No
176	NOTE_NLP	term_modifiers	No		varchar(2000)	0		For the modifiers that are there, they would have to have these values: 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. A list of allowable modifiers (e.g., signature for medications) and their possible values will be standardized later.	No		No								No		Yes	100	No		No		No										No
177	OBSERVATION	observation_id	Yes	0	integer	0			Yes	0	No								No		Yes	100	No		No		No										No
178	OBSERVATION	person_id	Yes	0	integer	0			No		Yes	0	PERSON	PERSON_ID					No		Yes	100	No		No		No										No
179	OBSERVATION	observation_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	Yes	0	No		No										No
180	OBSERVATION	observation_date	Yes	0	date	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	No
181	OBSERVATION	observation_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	No
182	OBSERVATION	observation_type_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Type Concept	0			Yes	0	Yes	100	Yes	0	No		No										No
183	OBSERVATION	value_as_number	No		float	0			No		No								No		Yes	100	No		No		No										No
184	OBSERVATION	value_as_string	No		varchar(60)	0			No		No								No		Yes	100	No		No		No										No
185	OBSERVATION	value_as_concept_id	No		Integer	0		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, ICD9CM V17.5 concept_id 44828510 'Family history of asthma' has a 'Maps to' relationship to 4167217 'Family history of clinical finding' as well as a 'Maps to value' record to 317009 'Asthma'.	No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
186	OBSERVATION	qualifier_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	No		No		No										No
187	OBSERVATION	unit_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Unit	0			Yes	0	Yes	100	Yes	0	No		No										No
188	OBSERVATION	provider_id	No		integer	0			No		Yes	0	PROVIDER	PROVIDER_ID					No		Yes	100	No		No		No										No
189	OBSERVATION	visit_occurrence_id	No		integer	0			No		Yes	0	VISIT_OCCURRENCE	VISIT_OCCURRENCE_ID					No		Yes	100	No		No		No										No
190	OBSERVATION	visit_detail_id	No		integer	0			No		Yes	0	VISIT_DETAIL	VISIT_DETAIL_ID					No		Yes	100	No		No		No										No
191	OBSERVATION	observation_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	OBSERVATION_CONCEPT_ID								No
192	OBSERVATION	observation_source_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		Yes	0	No										No
193	OBSERVATION	unit_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	UNIT_CONCEPT_ID								No
194	OBSERVATION	qualifier_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	QUALIFIER_CONCEPT_ID								No
195	SPECIMEN	specimen_id	Yes	0	integer	0			Yes	0	No								No		Yes	100	No		No		No										No
196	SPECIMEN	person_id	Yes	0	integer	0			No		Yes	0	PERSON	PERSON_ID					No		Yes	100	No		No		No										No
197	SPECIMEN	specimen_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	Yes	0	No		No										No
198	SPECIMEN	specimen_type_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Type Concept	0			Yes	0	Yes	100	Yes	0	No		No										No
199	SPECIMEN	specimen_date	Yes	0	date	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	No
200	SPECIMEN	specimen_datetime	No		datetime	0			No		No								No		Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	No
201	SPECIMEN	quantity	No		float	0			No		No								No		Yes	100	No		No		No			1	0						No
202	SPECIMEN	unit_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	Yes	0	No		No										No
203	SPECIMEN	anatomic_site_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	No		No		No										No
204	SPECIMEN	disease_status_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	No		No		No										No
205	SPECIMEN	specimen_source_id	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
206	SPECIMEN	specimen_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	SPECIMEN_CONCEPT_ID								No
207	SPECIMEN	unit_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	UNIT_CONCEPT_ID								No
208	SPECIMEN	anatomic_site_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	ANATOMIC_SITE_CONCEPT_ID								No
209	SPECIMEN	disease_status_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	DISEASE_STATUS_CONCEPT_ID								No
210	FACT_RELATIONSHIP	domain_concept_id_1	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	Yes	0	No		No										No
211	FACT_RELATIONSHIP	fact_id_1	Yes	0	integer	0			No		No								No		Yes	100	No		No		No										No
212	FACT_RELATIONSHIP	domain_concept_id_2	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	Yes	0	No		No										No
213	FACT_RELATIONSHIP	fact_id_2	Yes	0	integer	0			No		No								No		Yes	100	No		No		No										No
214	FACT_RELATIONSHIP	relationship_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	Yes	0	No		No										No
215	LOCATION	location_id	Yes	0	integer	0			Yes	0	No								No		Yes	100	No		No		No										No
216	LOCATION	address_1	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
217	LOCATION	address_2	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
218	LOCATION	city	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
219	LOCATION	state	No		varchar(2)	0			No		No								No		Yes	100	No		No		No										No
220	LOCATION	zip	No		varchar(9)	0		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.	No		No								No		Yes	100	No		No		No										No
221	LOCATION	county	No		varchar(20)	0			No		No								No		Yes	100	No		No		No										No
222	LOCATION	location_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
223	CARE_SITE	care_site_id	Yes	0	integer	0			Yes	0	No								No		Yes	100	No		No		No										No
224	CARE_SITE	care_site_name	No		varchar(255)	0			No		No								No		Yes	100	No		No		No										No
225	CARE_SITE	place_of_service_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	Yes	0	No		No										No
226	CARE_SITE	location_id	No		integer	0			No		No								No		Yes	100	No		No		No										No
227	CARE_SITE	care_site_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
228	CARE_SITE	place_of_service_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
229	PROVIDER	provider_id	Yes	0	integer	0			Yes	0	No								No		Yes	100	No		No		No										No
230	PROVIDER	provider_name	No		varchar(255)	0			No		No								No		Yes	100	No		No		No										No
231	PROVIDER	npi	No		varchar(20)	0			No		No								No		Yes	100	No		No		No										No
232	PROVIDER	dea	No		varchar(20)	0			No		No								No		Yes	100	No		No		No										No
233	PROVIDER	specialty_concept_id	No		integer	0		If a Provider has more than one Specialty, the main or most often exerted specialty should be recorded.	No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	Yes	0	No		No										No
234	PROVIDER	care_site_id	No		integer	0			No		Yes	0	CARE_SITE	CARE_SITE_ID					No		Yes	100	No		No		No										No
235	PROVIDER	year_of_birth	No		integer	0			No		No								No		Yes	100	No		No		No										No
236	PROVIDER	gender_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Gender	0			Yes	0	Yes	100	Yes	0	No		No										No
237	PROVIDER	provider_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		No										No
238	PROVIDER	specialty_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	SPECIALTY_CONCEPT_ID								No
239	PROVIDER	specialty_source_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		Yes	0	No										No
240	PROVIDER	gender_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	GENDER_CONCEPT_ID								No
241	PROVIDER	gender_source_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
242	PAYER_PLAN_PERIOD	payer_plan_period_id	Yes	0	integer	0			Yes	0	Yes	0	PERSON	PERSON_ID					No		Yes	100	No		No		No										No
243	PAYER_PLAN_PERIOD	person_id	Yes	0	integer	0			No		Yes	0	PERSON	PERSON_ID					No		Yes	100	No		No		No										No
244	PAYER_PLAN_PERIOD	payer_plan_period_start_date	Yes	0	date	0			No		No								No		Yes	100	No		No		No										No
245	PAYER_PLAN_PERIOD	payer_plan_period_end_date	Yes	0	date	0			No		No								No		Yes	100	No		No		No							PAYER_PLAN_PERIOD	PAYER_PLAN_PERIOD_START_DATE	0	No
246	PAYER_PLAN_PERIOD	payer_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
247	PAYER_PLAN_PERIOD	payer_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	PAYER_CONCEPT_ID								No
248	PAYER_PLAN_PERIOD	payer_source_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
249	PAYER_PLAN_PERIOD	plan_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
250	PAYER_PLAN_PERIOD	plan_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	PLAN_CONCEPT_ID								No
251	PAYER_PLAN_PERIOD	plan_source_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
252	PAYER_PLAN_PERIOD	sponsor_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
253	PAYER_PLAN_PERIOD	sponsor_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	SPONSOR_CONCEPT_ID								No
254	PAYER_PLAN_PERIOD	sponsor_source_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
255	PAYER_PLAN_PERIOD	family_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		No	0									No
256	PAYER_PLAN_PERIOD	stop_reason_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
257	PAYER_PLAN_PERIOD	stop_reason_source_value	No		varchar(50)	0			No		No								No		Yes	100	No		No		Yes	0	STOP_REASON_CONCEPT_ID								No
258	PAYER_PLAN_PERIOD	stop_reason_source_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
259	COST	cost_id	Yes	0	INTEGER	0			Yes	0	No								No		Yes	100	No		No		No										No
260	COST	cost_event_id	Yes	0	INTEGER	0			No		No								No		Yes	100	No		No		No										No
261	COST	cost_domain_id	Yes	0	VARCHAR(20)	0			No		Yes	0	DOMAIN	DOMAIN_ID					No		Yes	100	No		No		No										No
262	COST	cost_type_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					Yes	0	Yes	100	Yes	0	No		No										No
263	COST	currency_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
264	COST	total_charge	No		FLOAT	0			No		No								No		Yes	100	No		No		No										No
265	COST	total_cost	No		FLOAT	0			No		No								No		Yes	100	No		No		No										No
266	COST	total_paid	No		FLOAT	0			No		No								No		Yes	100	No		No		No										No
267	COST	paid_by_payer	No		FLOAT	0			No		No								No		Yes	100	No		No		No										No
268	COST	paid_by_patient	No		FLOAT	0			No		No								No		Yes	100	No		No		No										No
269	COST	paid_patient_copay	No		FLOAT	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
270	COST	paid_patient_coinsurance	No		FLOAT	0			No		No								No		Yes	100	No		No		No										No
271	COST	paid_patient_deductible	No		FLOAT	0			No		No								No		Yes	100	No		No		No										No
272	COST	paid_by_primary	No		FLOAT	0			No		No								No		Yes	100	No		No		No										No
273	COST	paid_ingredient_cost	No		FLOAT	0			No		No								No		Yes	100	No		No		No										No
274	COST	paid_dispensing_fee	No		FLOAT	0			No		No								No		Yes	100	No		No		No										No
275	COST	payer_plan_period_id	No		INTEGER	0			No		No								No		Yes	100	No		No		No										No
276	COST	amount_allowed	No		FLOAT	0			No		No								No		Yes	100	No		No		No										No
277	COST	revenue_code_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
278	COST	revenue_code_source_value	No		VARCHAR(50)	0	Revenue codes are a method to charge for a class of procedures and conditions in the U.S. hospital system.		No		No								No		Yes	100	No		No		No										No
279	COST	drg_concept_id	No		integer	0			No		Yes	0	CONCEPT	CONCEPT_ID					No		Yes	100	No		No		No										No
280	COST	drg_source_value	No		VARCHAR(3)	0	Diagnosis Related Groups are US codes used to classify hospital cases into one of approximately 500 groups.		No		No								No		Yes	100	No		No		No										No
281	DRUG_ERA	drug_era_id	Yes	0	integer	0			Yes	0	No										Yes	100	No		No		No										No
282	DRUG_ERA	person_id	Yes	0	integer	0			No		Yes	0	PERSON	PERSON_ID							Yes	100	No		No		No										No
283	DRUG_ERA	drug_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Drug	0	Ingredient	0	Yes	0	Yes	100	Yes	0	No		No										No
284	DRUG_ERA	drug_era_start_date	Yes	0	datetime	0		The Drug Era Start Date is the start date of the first Drug Exposure for a given ingredient. (NOT RIGHT)	No		No										Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
285	DRUG_ERA	drug_era_end_date	Yes	0	datetime	0		The 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. (ARENT WE REQUIRING TO USE DRUG_EXPOSURE_END_DATE NOW????)	No		No										Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	DRUG_ERA	DRUG_ERA_START_DATE	0	No
286	DRUG_ERA	drug_exposure_count	No		integer	0			No		No										Yes	100	No		No		No			1	0						No
287	DRUG_ERA	gap_days	No		integer	0		The 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.	No		No										Yes	100	No		No		No			0	0						No
288	DOSE_ERA	dose_era_id	Yes	0	integer	0			Yes	0	No										Yes	100	No		No		No										No
289	DOSE_ERA	person_id	Yes	0	integer	0			No		Yes	0	PERSON	PERSON_ID							Yes	100	No		No		No										No
290	DOSE_ERA	drug_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Drug	0	Ingredient	0	Yes	0	Yes	100	Yes	0	No		No										No
291	DOSE_ERA	unit_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Unit	0			Yes	0	Yes	100	Yes	0	No		No										No
292	DOSE_ERA	dose_value	Yes	0	float	0			No		No										Yes	100	No		No		No			0	0						No
293	DOSE_ERA	dose_era_start_date	Yes	0	datetime	0			No		No										Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
294	DOSE_ERA	dose_era_end_date	Yes	0	datetime	0			No		No										Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	No
295	CONDITION_ERA	condition_era_id	Yes	0	integer	0			Yes	0	No										Yes	100	No		No		No										No
296	CONDITION_ERA	person_id	Yes	0	integer	0			No		No		PERSON	PERSON_ID							Yes	100	No		No		No										No
297	CONDITION_ERA	condition_concept_id	Yes	0	integer	0			No		Yes	0	CONCEPT	CONCEPT_ID	Condition	0			Yes	0	Yes	100	Yes	0	No		No										No
298	CONDITION_ERA	condition_era_start_date	Yes	0	datetime	0			No		No										Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	Yes	0
299	CONDITION_ERA	condition_era_end_date	Yes	0	datetime	0			No		No										Yes	100	No		No		No			'1950-01-01'	0	DATEADD(dd,1,GETDATE())	0	PERSON	BIRTH_DATETIME	0	No
300	CONDITION_ERA	condition_occurrence_count	No		integer	0			No		No										Yes	100	No		No		No			1	0						No