diff --git a/docs/NAMESPACE b/docs/NAMESPACE index c31a890..4b433a2 100644 --- a/docs/NAMESPACE +++ b/docs/NAMESPACE @@ -1,5 +1,6 @@ # Generated by roxygen2: do not edit by hand +export(createDdlFromFile) export(downloadCurrentDdl) export(parseWiki) export(writeConstraints) diff --git a/docs/R/createDdlFromFile.R b/docs/R/createDdlFromFile.R new file mode 100644 index 0000000..2126b64 --- /dev/null +++ b/docs/R/createDdlFromFile.R @@ -0,0 +1,70 @@ + +# Copyright 2019 Observational Health Data Sciences and Informatics +# +# This file is part of DDLGeneratr +# +# Licensed under the Apache License, Version 2.0 (the "License"); +# you may not use this file except in compliance with the License. +# You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +#' Create a DDL script from a two csv files that detail the OMOP CDM Specifications. These files also form the basis of the CDM documentation and the Data Quality +#' Dashboard. +#' +#' @param cdmTableCsvLoc The location of the csv file with the high-level CDM table information. This is defaulted to "inst/csv/OMOP_CDMv5.3.1_Table_Level.csv". +#' If a new version of this file was committed to the CDM repository the package automatically will grab it and place it in "inst/csv/". +#' @param cdmVersion The location of the csv file with the CDM field information. This is defaulted to "inst/csv/OMOP_CDMv5.3.1_Field_Level.csv". +#' If a new version of this file was committed to the CDM repository the package automatically will grab it and place it in "inst/csv/". +#' @export + +createDdlFromFile <- function(cdmTableCsvLoc = "inst/csv/OMOP_CDMv5.3.1_Table_Level.csv", + cdmFieldCsvLoc = "inst/csv/OMOP_CDMv5.3.1_Field_Level.csv"){ + + tableSpecs <- read.csv(cdmTableCsvLoc, stringsAsFactors = FALSE) + cdmSpecs <- read.csv(cdmFieldCsvLoc, stringsAsFactors = FALSE) + + tableList <- tableSpecs$cdmTableName + + s <- c() + for (t in tableList){ + table <- subset(cdmSpecs, cdmTableName == t) + fields <- table$cdmFieldName + + if ('person_id' %in% fields){ + q <- "--HINT DISTRIBUTE ON KEY (person_id)" + } else { + q <- "--HINT DISTRIBUTE ON RANDOM" + } + + s <- c(s, q, paste0("CREATE TABLE ", t, " (")) + + end <- length(fields) + a <- c() + + for(f in fields) { + + if (subset(table, cdmFieldName == f, isRequired) == "Yes") { + r <- (" NOT NULL") + } else { + r <- (" NULL") + } + + if (f == fields[[end]]) { + e <- (" );") + } else { + e <- (",") + } + + a <- c(a, paste0(f," ",subset(table, cdmFieldName == f, cdmDatatype),r,e)) + } + s <- c(s, a, "") + } + return(s) +} diff --git a/docs/R/writeDDL.R b/docs/R/writeDDL.R index 63f8163..b31f1b7 100644 --- a/docs/R/writeDDL.R +++ b/docs/R/writeDDL.R @@ -1,4 +1,4 @@ -# Copyright 2017 Observational Health Data Sciences and Informatics +# Copyright 2019 Observational Health Data Sciences and Informatics # # This file is part of DDLGeneratr # diff --git a/docs/README.html b/docs/README.html index 9a0a1c9..56cc4a5 100644 --- a/docs/README.html +++ b/docs/README.html @@ -384,6 +384,13 @@ div.tocify { +
  • + + + + Background + +
  • @@ -408,6 +415,34 @@ div.tocify {
    • +
  • + + +
  • @@ -424,7 +459,12 @@ div.tocify {
    • diff --git a/docs/background.html b/docs/background.html new file mode 100644 index 0000000..bba9890 --- /dev/null +++ b/docs/background.html @@ -0,0 +1,553 @@ + + + + + + + + + + + + + +background.utf8 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + + + + + + + + + + + + + + + + +
    +
    +
    +
    +
    + +
    + + + + + + + + + +
    +

    Background

    +

    The Observational Medical Outcomes Partnership (OMOP) was a public-private partnership established to inform the appropriate use of observational healthcare databases for studying the effects of medical products. Over the course of the 5-year project and through its community of researchers from industry, government, and academia, OMOP successfully achieved its aims to:

    +
      +
    • Conduct methodological research to empirically evaluate the performance of various analytical methods on their ability to identify true associations and avoid false findings
      • +
    • Develop tools and capabilities for transforming, characterizing, and analysing disparate data sources across the health care delivery spectrum
      • +
    • Establish a shared resource so that the broader research community can collaboratively advance the science
      • +
    +

    The results of OMOP’s research has been widely published and presented at scientific conferences, including annual symposia.

    +

    The OMOP Legacy continues…

    +

    The community is actively using the OMOP Common Data Model for their various research purposes. Those tools will continue to be maintained and supported, and information about this work is available in the public domain.

    +

    The OMOP Common Data Model will continue to be an open-source community standard for observational healthcare data. The model specifications and associated work products will be placed in the public domain, and the entire research community is encouraged to use these tools to support everybody’s own research activities.

    +
    +
    +

    The Role of the Common Data Model

    +

    No single observational data source provides a comprehensive view of the clinical data a patient accumulates while receiving healthcare, and therefore none can be sufficient to meet all expected outcome analysis needs. This explains the need for assessing and analyzing multiple data sources concurrently using a common data standard. This standard is provided by the OMOP Common Data Model (CDM).

    +

    The CDM is designed to support the conduct of research to identify and evaluate associations between interventions (drug exposure, procedures, healthcare policy changes etc.) and outcomes caused by these interventions (condition occurrences, procedures, drug exposure etc.). Outcomes can be efficacious (benefit) or adverse (safety risk). Often times, specific patient cohorts (e.g., those taking a certain drug or suffering from a certain disease) may be defined for treatments or outcomes, using clinical events (diagnoses, observations, procedures, etc.) that occur in predefined temporal relationships to each other. The CDM, combined with its standardized content (via the Standardized Vocabularies), will ensure that research methods can be systematically applied to produce meaningfully comparable and reproducible results.

    +
    +
    +

    Design Principles

    +

    The CDM is designed to include all observational health data elements (experiences of the patient receiving health care) that are relevant for analytic use cases to support the generation of reliable scientific evidence about disease natural history, healthcare delivery, effects of medical interventions, the identification of demographic information, health care interventions and outcomes.

    +

    Therefore, the CDM is designed to store observational data to allow for research, under the following principles:

    +
      +
    • Suitability for purpose: The CDM aims to provide data organized in a way optimal for analysis, rather than for the purpose of addressing the operational needs of health care providers or payers.
      • +
    • Data protection: All data that might jeopardize the identity and protection of patients, such as names, precise birthdays etc. are limited. Exceptions are possible where the research expressly requires more detailed information, such as precise birth dates for the study of infants.
      • +
    • Design of domains: The domains are modeled in a person-centric relational data model, where for each record the identity of the person and a date is captured as a minimum.
      • +
    • Rationale for domains: Domains are identified and separately defined in an entity-relationship model if they have an analysis use case and the domain has specific attributes that are not otherwise applicable. All other data can be preserved as an observation in an entity-attribute-value structure.
      • +
    • Standardized Vocabularies: To standardize the content of those records, the CDM relies on the Standardized Vocabularies containing all necessary and appropriate corresponding standard healthcare concepts.
      • +
    • Reuse of existing vocabularies: If possible, these concepts are leveraged from national or industry standardization or vocabulary definition organizations or initiatives, such as the National Library of Medicine, the Department of Veterans’ Affairs, the Center of Disease Control and Prevention, etc.
      • +
    • Maintaining source codes: Even though all codes are mapped to the Standardized Vocabularies, the model also stores the original source code to ensure no information is lost.
      • +
    • Technology neutrality: The CDM does not require a specific technology. It can be realized in any relational database, such as Oracle, SQL Server etc., or as SAS analytical datasets.
      • +
    • Scalability: The CDM is optimized for data processing and computational analysis to accommodate data sources that vary in size, including databases with up to hundreds of millions of persons and billions of clinical observations.
      • +
    • Backwards compatibility: All changes from previous CDMs are clearly delineated in the github repository. Older versions of the CDM can be easily created from the CDMv5, and no information is lost that was present previously.
      • +
    +
    + + + +
    +
    + +
    + + + + + + + + diff --git a/docs/cdm531.html b/docs/cdm531.html index 211e0dd..8eae79b 100644 --- a/docs/cdm531.html +++ b/docs/cdm531.html @@ -386,6 +386,13 @@ div.tocify { +
  • + + + + Background + +
  • @@ -410,6 +417,34 @@ div.tocify {
    • +
  • + + +
  • @@ -426,7 +461,12 @@ div.tocify {
    • @@ -446,6 +486,7 @@ div.tocify {

    CDM v5.3.1

    +

    Documentation still in development

    PERSON

    @@ -515,7 +556,7 @@ No @@ -574,7 +615,7 @@ No @@ -602,7 +643,7 @@ No @@ -630,7 +671,7 @@ No @@ -688,7 +729,7 @@ Race @@ -895,7 +936,7 @@ CONCEPT @@ -953,7 +994,7 @@ CONCEPT @@ -1052,7 +1093,7 @@ FK Class @@ -1384,7 +1425,7 @@ No @@ -1441,7 +1482,7 @@ No @@ -1590,7 +1631,7 @@ CONCEPT @@ -1649,7 +1690,7 @@ No @@ -1708,7 +1749,7 @@ No
    -gender _concept_id +gender_concept_id 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. @@ -546,7 +587,7 @@ Gender
    -year _of_birth +year_of_birth
    -month _of_birth +month_of_birth
    -day _of_birth +day_of_birth
    -birth _datetime +birth_datetime Compute age using birth_datetime. @@ -659,7 +700,7 @@ No
    -race_ concept_id +race_concept_id
    -ethnicity _concept_id +ethnicity_concept_id 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. @@ -808,7 +849,7 @@ CARE_SITE
    -person _source_value +person_source_value Use this field to link back to persons in the source data. This is typically used for error checking of ETL logic. @@ -837,7 +878,7 @@ No
    -gender _source_value +gender_source_value 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. @@ -866,7 +907,7 @@ No
    -gender_source _concept_id +gender_source_concept_id
    -race_ source_value +race_source_value 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. @@ -924,7 +965,7 @@ No
    -race_ source_concept_id +race_source_concept_id
    -ethnicity_ source_value +ethnicity_source_value 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. @@ -982,7 +1023,7 @@ No
    -ethnicity_source _concept_id +ethnicity_source_concept_id
    -observation _period_id +observation_period_id 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. @@ -1109,7 +1150,7 @@ PERSON
    -observation_period _start_date +observation_period_start_date 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. @@ -1138,7 +1179,7 @@ No
    -observation_period _end_date +observation_period_end_date 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. @@ -1167,7 +1208,7 @@ No
    -period_type _concept_id +period_type_concept_id 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. @@ -1239,7 +1280,7 @@ FK Class
    -visit _occurrence_id +visit_occurrence_id 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. @@ -1296,7 +1337,7 @@ PERSON
    -visit _concept_id +visit_concept_id This field contains a concept id representing the kind of visit, like inpatient or outpatient. @@ -1327,7 +1368,7 @@ Visit
    -visit _start_date +visit_start_date For inpatient visits, the start date is typically the admission date. For outpatient visits the start date and end date will be the same. @@ -1356,7 +1397,7 @@ No
    -visit_start _datetime +visit_start_datetime
    -visit _end_date +visit_end_date For inpatient visits the end date is typically the discharge date. @@ -1413,7 +1454,7 @@ No
    -visit_end _datetime +visit_end_datetime
    -visit_type _concept_id +visit_type_concept_id Use this field to understand the provenance of the visit record, or where the record comes from. @@ -1532,7 +1573,7 @@ CARE_SITE
    -visit _source_value +visit_source_value This field houses the verbatim value from the source data representing the kind of visit that took place (inpatient, outpatient, emergency, etc.) @@ -1561,7 +1602,7 @@ No
    -visit_source _concept_id +visit_source_concept_id
    -admitting_source _concept_id +admitting_source_concept_id 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. @@ -1621,7 +1662,7 @@ Visit
    -admitting _source_value +admitting_source_value
    -discharge_to _concept_id +discharge_to_concept_id 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. @@ -1680,7 +1721,7 @@ Visit
    -discharge_to _source_value +discharge_to_source_value
    -preceding_visit _occurrence_id +preceding_visit_occurrence_id 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. @@ -1739,6 +1780,7951 @@ VISIT_OCCURRENCE
    +
    +

    CONDITION_OCCURRENCE

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +condition_occurrence_id + + + +bigint + +Yes + +Yes + +No + + + +
    +person_id + + + +bigint + +Yes + +No + +Yes + +PERSON + + +
    +condition_concept_id + +The CONDITION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies + + +integer + +Yes + +No + +Yes + +CONCEPT + +Condition + +
    +condition_start_date + + + +date + +Yes + +No + +No + + + +
    +condition_start_datetime + + + +datetime + +No + +No + +No + + + +
    +condition_end_date + + + +date + +No + +No + +No + + + +
    +condition_end_datetime + + +should not be inferred + +datetime + +No + +No + +No + + + +
    +condition_type_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Type Concept + +
    +condition_status_concept_id + + +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 + +integer + +No + +No + +Yes + +CONCEPT + + +
    +stop_reason + +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. + + +varchar(20) + +No + +No + +No + + + +
    +provider_id + + + +integer + +No + +No + +Yes + +PROVIDER + + +
    +visit_occurrence_id + + + +integer + +No + +No + +Yes + +VISIT_OCCURRENCE + + +
    +visit_detail_id + + + +integer + +No + +No + +Yes + +VISIT_DETAIL + + +
    +condition_source_value + +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. + +varchar(50) + +No + +No + +No + + + +
    +condition_source_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +condition_status_source_value + + +This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference. + +varchar(50) + +No + +No + +No + + + +
    +
    +
    +

    DRUG_EXPOSURE

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +drug_exposure_id + + + +bigint + +Yes + +Yes + +No + + + +
    +person_id + + + +bigint + +Yes + +No + +Yes + +PERSON + + +
    +drug_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Drug + +
    +drug_exposure_start_date + + +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. + +date + +Yes + +No + +No + + + +
    +drug_exposure_start_datetime + + + +datetime + +No + +No + +No + + + +
    +drug_exposure_end_date + + +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. + +date + +Yes + +No + +No + + + +
    +drug_exposure_end_datetime + + + +datetime + +No + +No + +No + + + +
    +verbatim_end_date + +You can use the TYPE_CONCEPT_ID to delineate between prescriptions written vs. prescriptions dispensed vs. medication history vs. patient-reported exposure + + +date + +No + +No + +No + + + +
    +drug_type_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Type Concept + +
    +stop_reason + + +Reasons include regimen completed, changed, removed, etc. + +varchar(20) + +No + +No + +No + + + +
    +refills + +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. + + +integer + +No + +No + +No + + + +
    +quantity + + + +float + +No + +No + +No + + + +
    +days_supply + + + +integer + +No + +No + +No + + + +
    +sig + +(and printed on the container) + + +varchar(MAX) + +No + +No + +No + + + +
    +route_concept_id + +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’. + + +integer + +No + +No + +Yes + +CONCEPT + +Route + +
    +lot_number + + + +varchar(50) + +No + +No + +No + + + +
    +provider_id + + + +integer + +No + +No + +Yes + +PROVIDER + + +
    +visit_occurrence_id + + + +integer + +No + +No + +Yes + +VISIT_OCCURRENCE + + +
    +visit_detail_id + + + +integer + +No + +No + +Yes + +VISIT_DETAIL + + +
    +drug_source_value + + +This code is mapped to a Standard Drug concept in the Standardized Vocabularies and the original code is, stored here for reference. + +varchar(50) + +No + +No + +No + + + +
    +drug_source_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +route_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +dose_unit_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +
    +
    +

    PROCEDURE_OCCURRENCE

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +procedure_occurrence_id + + + +integer + +Yes + +Yes + +No + + + +
    +person_id + + + +integer + +Yes + +No + +Yes + +PERSON + + +
    +procedure_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Procedure + +
    +procedure_date + + + +date + +Yes + +No + +No + + + +
    +procedure_datetime + + + +datetime + +No + +No + +No + + + +
    +procedure_type_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Type Concept + +
    +modifier_concept_id + +These concepts are typically distinguished by ‘Modifier’ concept classes (e.g., ‘CPT4 Modifier’ as part of the ‘CPT4’ vocabulary). + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +quantity + +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). + +integer + +No + +No + +No + + + +
    +provider_id + + + +integer + +No + +No + +No + +PROVIDER + + +
    +visit_occurrence_id + + + +integer + +No + +No + +No + +VISIT_OCCURRENCE + + +
    +visit_detail_id + + + +integer + +No + +No + +No + +VISIT_DETAIL + + +
    +procedure_source_value + + +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. + +varchar(50) + +No + +No + +No + + + +
    +procedure_source_concept_id + + + +integer + +No + +No + +No + +CONCEPT + + +
    +modifier_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +
    +
    +

    DEVICE_EXPOSURE

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +device_exposure_id + + + +bigint + +Yes + +Yes + +No + + + +
    +person_id + + + +bigint + +Yes + +No + +Yes + +PERSON + + +
    +device_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Device + +
    +device_exposure_start_date + + + +date + +Yes + +No + +No + + + +
    +device_exposure_start_datetime + + + +datetime + +No + +No + +No + + + +
    +device_exposure_end_date + + + +date + +No + +No + +No + + + +
    +device_exposure_end_datetime + + + +datetime + +No + +No + +No + + + +
    +device_type_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Type Concept + +
    +unique_device_id + + +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. + +varchar(50) + +No + +No + +No + + + +
    +quantity + + + +integer + +No + +No + +No + + + +
    +provider_id + + + +integer + +No + +No + +Yes + +PROVIDER + + +
    +visit_occurrence_id + + + +integer + +No + +No + +Yes + +VISIT_OCCURRENCE + + +
    +visit_detail_id + + + +integer + +No + +No + +Yes + +VISIT_DETAIL + + +
    +device_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +device_source_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +
    +
    +

    MEASUREMENT

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +measurement_id + + + +integer + +Yes + +Yes + +No + + + +
    +person_id + + + +integer + +Yes + +No + +Yes + +PERSON + + +
    +measurement_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Measurement + +
    +measurement_date + + + +date + +Yes + +No + +No + + + +
    +measurement_datetime + + + +datetime + +No + +No + +No + + + +
    +measurement_time + +This is present for backwards compatibility and will be deprecated in an upcoming version + + +varchar(10) + +No + +No + +No + + + +
    +measurement_type_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Type Concept + +
    +operator_concept_id + +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 + +integer + +No + +No + +Yes + +CONCEPT + + +
    +value_as_number + + + +float + +No + +No + +No + + + +
    +value_as_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +unit_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + +Unit + +
    +range_low + +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. + +float + +No + +No + +No + + + +
    +range_high + +Ranges have the same unit as the VALUE_AS_NUMBER. + + +float + +No + +No + +No + + + +
    +provider_id + + + +integer + +No + +No + +Yes + +PROVIDER + + +
    +visit_occurrence_id + + + +integer + +No + +No + +Yes + +VISIT_OCCURRENCE + + +
    +visit_detail_id + + + +integer + +No + +No + +Yes + +VISIT_DETAIL + + +
    +measurement_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +measurement_source_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +unit_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +value_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +
    +
    +

    VISIT_DETAIL

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +visit_detail_id + + + +integer + +Yes + +Yes + +No + + + +
    +person_id + + + +integer + +Yes + +No + +Yes + +PERSON + + +
    +visit_detail_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Visit + +
    +visit_detail_start_date + + + +date + +Yes + +No + +No + + + +
    +visit_detail_start_datetime + + + +datetime + +No + +No + +No + + + +
    +visit_detail_end_date + + + +date + +Yes + +No + +No + + + +
    +visit_detail_end_datetime + + + +datetime + +No + +No + +No + + + +
    +visit_detail_type_concept_id + + + +Integer + +Yes + +No + +Yes + +CONCEPT + +Type Concept + +
    +provider_id + + + +integer + +No + +No + +Yes + +PROVIDER + + +
    +care_site_id + + + +integer + +No + +No + +Yes + +CARE_SITE + + +
    +visit_detail_source_value + + + +string(50) + +No + +No + +No + + + +
    +visit_detail_source_concept_id + + + +Integer + +No + +No + +Yes + +CONCEPT + + +
    +admitting_source_value + + + +Varchar(50) + +No + +No + +No + + + +
    +admitting_source_concept_id + + + +Integer + +No + +No + +Yes + +CONCEPT + + +
    +discharge_to_source_value + + + +Varchar(50) + +No + +No + +No + + + +
    +discharge_to_concept_id + + + +Integer + +No + +No + +Yes + +CONCEPT + + +
    +preceding_visit_detail_id + + + +Integer + +No + +No + +Yes + +VISIT_DETAIL + + +
    +visit_detail_parent_id + + + +Integer + +No + +No + +Yes + +VISIT_DETAIL + + +
    +visit_occurrence_id + + + +Integer + +Yes + +No + +Yes + +VISIT_OCCURRENCE + + +
    +
    +
    +

    NOTE

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +note_id + + + +integer + +Yes + +Yes + +No + + + +
    +person_id + + + +integer + +Yes + +No + +Yes + +PERSON + + +
    +note_date + + + +date + +Yes + +No + +No + + + +
    +note_datetime + + + +datetime + +No + +No + +No + + + +
    +note_type_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Type Concept + +
    +note_class_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + + +
    +note_title + + + +varchar(250) + +No + +No + +No + + + +
    +note_text + + + +varchar(MAX) + +Yes + +No + +No + + + +
    +encoding_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + + +
    +language_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + + +
    +provider_id + + + +integer + +No + +No + +Yes + +PROVIDER + + +
    +visit_occurrence_id + + + +integer + +No + +No + +Yes + +VISIT_OCCURRENCE + + +
    +visit_detail_id + + + +integer + +No + +No + +Yes + +VISIT_DETAIL + + +
    +note_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +
    +
    +

    NOTE_NLP

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +note_nlp_id + + + +integer + +Yes + +Yes + +No + + + +
    +note_id + + + +integer + +Yes + +No + +No + + + +
    +section_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +snippet + + + +varchar(250) + +No + +No + +No + + + +
    +offset + + + +varchar(50) + +No + +No + +No + + + +
    +lexical_variant + + + +varchar(250) + +Yes + +No + +No + + + +
    +note_nlp_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +note_nlp_source_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +nlp_system + + + +varchar(250) + +No + +No + +No + + + +
    +nlp_date + + + +date + +Yes + +No + +No + + + +
    +nlp_datetime + + + +datetime + +No + +No + +No + + + +
    +term_exists + + +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. + +varchar(1) + +No + +No + +No + + + +
    +term_temporal + + +Term_temporal is to indicate if a condition is �present� or just in the �past�. The following would be past: History = true Concept_date = anything before the time of the report + +varchar(50) + +No + +No + +No + + + +
    +term_modifiers + + +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. + +varchar(2000) + +No + +No + +No + + + +
    +
    +
    +

    OBSERVATION

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +observation_id + + + +integer + +Yes + +Yes + +No + + + +
    +person_id + + + +integer + +Yes + +No + +Yes + +PERSON + + +
    +observation_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + + +
    +observation_date + + + +date + +Yes + +No + +No + + + +
    +observation_datetime + + + +datetime + +No + +No + +No + + + +
    +observation_type_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Type Concept + +
    +value_as_number + + + +float + +No + +No + +No + + + +
    +value_as_string + + + +varchar(60) + +No + +No + +No + + + +
    +value_as_concept_id + + +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’. + +Integer + +No + +No + +Yes + +CONCEPT + + +
    +qualifier_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +unit_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + +Unit + +
    +provider_id + + + +integer + +No + +No + +Yes + +PROVIDER + + +
    +visit_occurrence_id + + + +integer + +No + +No + +Yes + +VISIT_OCCURRENCE + + +
    +visit_detail_id + + + +integer + +No + +No + +Yes + +VISIT_DETAIL + + +
    +observation_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +observation_source_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +unit_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +qualifier_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +
    +
    +

    SPECIMEN

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +specimen_id + + + +integer + +Yes + +Yes + +No + + + +
    +person_id + + + +integer + +Yes + +No + +Yes + +PERSON + + +
    +specimen_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + + +
    +specimen_type_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Type Concept + +
    +specimen_date + + + +date + +Yes + +No + +No + + + +
    +specimen_datetime + + + +datetime + +No + +No + +No + + + +
    +quantity + + + +float + +No + +No + +No + + + +
    +unit_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +anatomic_site_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +disease_status_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +specimen_source_id + + + +varchar(50) + +No + +No + +No + + + +
    +specimen_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +unit_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +anatomic_site_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +disease_status_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +
    +
    +

    FACT_RELATIONSHIP

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +domain_concept_id_1 + + + +integer + +Yes + +No + +Yes + +CONCEPT + + +
    +fact_id_1 + + + +integer + +Yes + +No + +No + + + +
    +domain_concept_id_2 + + + +integer + +Yes + +No + +Yes + +CONCEPT + + +
    +fact_id_2 + + + +integer + +Yes + +No + +No + + + +
    +relationship_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + + +
    +
    +
    +

    LOCATION

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +location_id + + + +integer + +Yes + +Yes + +No + + + +
    +address_1 + + + +varchar(50) + +No + +No + +No + + + +
    +address_2 + + + +varchar(50) + +No + +No + +No + + + +
    +city + + + +varchar(50) + +No + +No + +No + + + +
    +state + + + +varchar(2) + +No + +No + +No + + + +
    +zip + + +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. + +varchar(9) + +No + +No + +No + + + +
    +county + + + +varchar(20) + +No + +No + +No + + + +
    +location_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +
    +
    +

    CARE_SITE

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +care_site_id + + + +integer + +Yes + +Yes + +No + + + +
    +care_site_name + + + +varchar(255) + +No + +No + +No + + + +
    +place_of_service_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +location_id + + + +integer + +No + +No + +No + + + +
    +care_site_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +place_of_service_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +
    +
    +

    PROVIDER

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +provider_id + + + +integer + +Yes + +Yes + +No + + + +
    +provider_name + + + +varchar(255) + +No + +No + +No + + + +
    +npi + + + +varchar(20) + +No + +No + +No + + + +
    +dea + + + +varchar(20) + +No + +No + +No + + + +
    +specialty_concept_id + + +If a Provider has more than one Specialty, the main or most often exerted specialty should be recorded. + +integer + +No + +No + +Yes + +CONCEPT + + +
    +care_site_id + + + +integer + +No + +No + +Yes + +CARE_SITE + + +
    +year_of_birth + + + +integer + +No + +No + +No + + + +
    +gender_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + +Gender + +
    +provider_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +specialty_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +specialty_source_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +gender_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +gender_source_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +
    +
    +

    PAYER_PLAN_PERIOD

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +payer_plan_period_id + + + +integer + +Yes + +Yes + +Yes + +PERSON + + +
    +person_id + + + +integer + +Yes + +No + +Yes + +PERSON + + +
    +payer_plan_period_start_date + + + +date + +Yes + +No + +No + + + +
    +payer_plan_period_end_date + + + +date + +Yes + +No + +No + + + +
    +payer_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +payer_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +payer_source_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +plan_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +plan_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +plan_source_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +sponsor_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +sponsor_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +sponsor_source_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +family_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +stop_reason_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +stop_reason_source_value + + + +varchar(50) + +No + +No + +No + + + +
    +stop_reason_source_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +
    +
    +

    COST

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +cost_id + + + +INTEGER + +Yes + +Yes + +No + + + +
    +cost_event_id + + + +INTEGER + +Yes + +No + +No + + + +
    +cost_domain_id + + + +VARCHAR(20) + +Yes + +No + +Yes + +DOMAIN + + +
    +cost_type_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + + +
    +currency_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +total_charge + + + +FLOAT + +No + +No + +No + + + +
    +total_cost + + + +FLOAT + +No + +No + +No + + + +
    +total_paid + + + +FLOAT + +No + +No + +No + + + +
    +paid_by_payer + + + +FLOAT + +No + +No + +No + + + +
    +paid_by_patient + + + +FLOAT + +No + +No + +No + + + +
    +paid_patient_copay + + + +FLOAT + +No + +No + +Yes + +CONCEPT + + +
    +paid_patient_coinsurance + + + +FLOAT + +No + +No + +No + + + +
    +paid_patient_deductible + + + +FLOAT + +No + +No + +No + + + +
    +paid_by_primary + + + +FLOAT + +No + +No + +No + + + +
    +paid_ingredient_cost + + + +FLOAT + +No + +No + +No + + + +
    +paid_dispensing_fee + + + +FLOAT + +No + +No + +No + + + +
    +payer_plan_period_id + + + +INTEGER + +No + +No + +No + + + +
    +amount_allowed + + + +FLOAT + +No + +No + +No + + + +
    +revenue_code_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +revenue_code_source_value + +Revenue codes are a method to charge for a class of procedures and conditions in the U.S. hospital system. + + +VARCHAR(50) + +No + +No + +No + + + +
    +drg_concept_id + + + +integer + +No + +No + +Yes + +CONCEPT + + +
    +drg_source_value + +Diagnosis Related Groups are US codes used to classify hospital cases into one of approximately 500 groups. + + +VARCHAR(3) + +No + +No + +No + + + +
    +
    +
    +

    DRUG_ERA

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +drug_era_id + + + +integer + +Yes + +Yes + +No + + + +
    +person_id + + + +integer + +Yes + +No + +Yes + +PERSON + + +
    +drug_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Drug + +Ingredient +
    +drug_era_start_date + + +The Drug Era Start Date is the start date of the first Drug Exposure for a given ingredient. (NOT RIGHT) + +datetime + +Yes + +No + +No + + + +
    +drug_era_end_date + + +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????) + +datetime + +Yes + +No + +No + + + +
    +drug_exposure_count + + + +integer + +No + +No + +No + + + +
    +gap_days + + +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. + +integer + +No + +No + +No + + + +
    +
    +
    +

    DOSE_ERA

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +dose_era_id + + + +integer + +Yes + +Yes + +No + + + +
    +person_id + + + +integer + +Yes + +No + +Yes + +PERSON + + +
    +drug_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Drug + +Ingredient +
    +unit_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Unit + +
    +dose_value + + + +float + +Yes + +No + +No + + + +
    +dose_era_start_date + + + +datetime + +Yes + +No + +No + + + +
    +dose_era_end_date + + + +datetime + +Yes + +No + +No + + + +
    +
    +
    +

    CONDITION_ERA

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +CDM Field + +User Guide + +ETL Conventions + +Datatype + +Required + +Primary Key + +Foreign Key + +FK Table + +FK Domain + +FK Class +
    +condition_era_id + + + +integer + +Yes + +Yes + +No + + + +
    +person_id + + + +integer + +Yes + +No + +No + +PERSON + + +
    +condition_concept_id + + + +integer + +Yes + +No + +Yes + +CONCEPT + +Condition + +
    +condition_era_start_date + + + +datetime + +Yes + +No + +No + + + +
    +condition_era_end_date + + + +datetime + +Yes + +No + +No + + + +
    +condition_occurrence_count + + + +integer + +No + +No + +No + + + +
    +
    diff --git a/docs/cdm60.html b/docs/cdm60.html index 248f106..e3c5d89 100644 --- a/docs/cdm60.html +++ b/docs/cdm60.html @@ -386,6 +386,13 @@ div.tocify { +
  • + + + + Background + +
  • @@ -410,6 +417,34 @@ div.tocify {
    • +
  • + + +
  • @@ -426,7 +461,12 @@ div.tocify {
    • @@ -443,6 +483,7 @@ div.tocify {

    CDM v6.0

    +

    Documentation still in development

    PERSON

    @@ -461,13 +502,13 @@ ETL Conventions Datatype @@ -521,7 +558,6 @@ gender_concept_id A foreign key that refers to an identifier in the CONCEPT table for the unique gender of the person. @@ -553,7 +588,6 @@ year_of_birth The year of birth of the person. For data sources with date of birth, the year is extracted. For data sources where the year of birth is not available, the approximate year of birth is derived based on any age group categorization available. @@ -585,7 +616,6 @@ month_of_birth The month of birth of the person. For data sources that provide the precise date of birth, the month is extracted and stored in this field. @@ -617,7 +644,6 @@ day_of_birth The day of the month of birth of the person. For data sources that provide the precise date of birth, the day is extracted and stored in this field. @@ -649,7 +672,6 @@ birth_datetime The date and time of birth of the person. @@ -681,7 +700,6 @@ death_datetime The date and time of death of the person. @@ -713,7 +728,6 @@ race_concept_id A foreign key that refers to an identifier in the CONCEPT table for the unique race of the person, belonging to the ‘’Race’’ vocabulary. @@ -745,7 +758,6 @@ ethnicity_concept_id A foreign key that refers to the standard concept identifier in the Standardized Vocabularies for the ethnicity of the person, belonging to the ‘’Ethnicity’’ vocabulary. @@ -777,7 +788,6 @@ location_id A foreign key to the place of residency for the person in the location table, where the detailed address information is stored. @@ -809,7 +817,6 @@ provider_id A foreign key to the primary care provider the person is seeing in the provider table. @@ -841,7 +846,6 @@ care_site_id A foreign key to the site of primary care in the care_site table, where the details of the care site are stored. @@ -873,7 +875,6 @@ person_source_value An (encrypted) key derived from the person identifier in the source data. This is necessary when a use case requires a link back to the person data at the source dataset. @@ -905,7 +903,6 @@ gender_source_value The source code for the gender of the person as it appears in the source data. The person’s gender is mapped to a standard gender concept in the Standardized Vocabularies; the original value is stored here for reference. @@ -937,7 +931,6 @@ gender_source_concept_id A foreign key to the gender concept that refers to the code used in the source. @@ -969,7 +960,6 @@ race_source_value The source code for the race of the person as it appears in the source data. The person race is mapped to a standard race concept in the Standardized Vocabularies and the original value is stored here for reference. @@ -1001,7 +988,6 @@ race_source_concept_id A foreign key to the race concept that refers to the code used in the source. @@ -1033,7 +1017,6 @@ ethnicity_source_value The source code for the ethnicity of the person as it appears in the source data. The person ethnicity is mapped to a standard ethnicity concept in the Standardized Vocabularies and the original code is, stored here for reference. @@ -1065,7 +1045,6 @@ ethnicity_source_concept_id A foreign key to the ethnicity concept that refers to the code used in the source. @@ -1110,13 +1087,13 @@ ETL Conventions Datatype @@ -1170,7 +1143,6 @@ person_id A foreign key identifier to the person for whom the observation period is defined. The demographic details of that person are stored in the person table. @@ -1202,7 +1172,6 @@ observation_period_start_date The start date of the observation period for which data are available from the data source. @@ -1234,7 +1200,6 @@ observation_period_end_date The end date of the observation period for which data are available from the data source. @@ -1266,7 +1228,6 @@ period_type_concept_id A foreign key identifier to the predefined concept in the Standardized Vocabularies reflecting the source of the observation period information, belonging to the ‘’Obs Period Type’’ vocabulary @@ -1311,13 +1271,13 @@ ETL Conventions Datatype @@ -1371,7 +1327,6 @@ person_id A foreign key identifier to the Person for whom the visit is recorded. The demographic details of that Person are stored in the PERSON table. @@ -1403,7 +1356,6 @@ visit_concept_id A foreign key that refers to a visit Concept identifier in the Standardized Vocabularies belonging to the ‘’Visit’’ Vocabulary. @@ -1435,7 +1386,6 @@ visit_start_date The start date of the visit. @@ -1467,7 +1414,6 @@ visit_start_datetime The date and time of the visit started. @@ -1499,7 +1442,6 @@ visit_end_date The end date of the visit. If this is a one-day visit the end date should match the start date. @@ -1531,7 +1470,6 @@ visit_end_datetime The date and time of the visit end. @@ -1563,7 +1498,6 @@ visit_type_concept_id A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of source data from which the visit record is derived belonging to the ‘’Visit Type’’ vocabulary. @@ -1595,7 +1528,6 @@ provider_id A foreign key to the provider in the provider table who was associated with the visit. @@ -1627,7 +1557,6 @@ care_site_id A foreign key to the care site in the care site table that was visited. @@ -1659,7 +1586,6 @@ visit_source_value The source code for the visit as it appears in the source data. @@ -1691,7 +1614,6 @@ visit_source_concept_id A foreign key to a Concept that refers to the code used in the source. @@ -1723,7 +1643,6 @@ admitted_from_concept_id A foreign key to the predefined concept in the Place of Service Vocabulary reflecting where the patient was admitted from. @@ -1755,7 +1672,6 @@ admitted_from_source_value The source code for where the patient was admitted from as it appears in the source data. @@ -1787,7 +1700,6 @@ discharge_to_concept_id A foreign key to the predefined concept in the Place of Service Vocabulary reflecting the discharge disposition for a visit. @@ -1819,7 +1729,6 @@ discharge_to_source_value The source code for the discharge disposition as it appears in the source data. @@ -1851,7 +1757,6 @@ preceding_visit_occurrence_id A foreign key to the VISIT_OCCURRENCE table of the visit immediately preceding this visit @@ -1896,13 +1799,13 @@ ETL Conventions Datatype @@ -1956,7 +1855,6 @@ person_id A foreign key identifier to the Person who is experiencing the condition. The demographic details of that Person are stored in the PERSON table. @@ -1988,7 +1884,6 @@ condition_concept_id A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the ‘’Condition’’ domain. @@ -2020,7 +1914,6 @@ condition_start_date The date when the instance of the Condition is recorded. @@ -2052,7 +1942,6 @@ condition_start_datetime The date and time when the instance of the Condition is recorded. @@ -2084,7 +1970,6 @@ condition_end_date The date when the instance of the Condition is considered to have ended. @@ -2116,7 +1998,6 @@ condition_end_datetime The date when the instance of the Condition is considered to have ended. @@ -2148,7 +2026,6 @@ condition_type_concept_id A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the source data from which the Condition was recorded, the level of standardization, and the type of occurrence. These belong to the ‘’Condition Type’’ vocabulary @@ -2180,7 +2056,6 @@ condition_status_concept_id A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies reflecting the point of care at which the Condition was diagnosed. @@ -2212,7 +2085,6 @@ stop_reason The reason that the Condition was no longer present, as indicated in the source data. @@ -2244,7 +2113,6 @@ provider_id A foreign key to the Provider in the PROVIDER table who was responsible for capturing (diagnosing) the Condition. @@ -2276,7 +2142,6 @@ visit_occurrence_id A foreign key to the visit in the VISIT_OCCURRENCE table during which the Condition was determined (diagnosed). @@ -2308,7 +2171,6 @@ visit_detail_id A foreign key to the visit in the VISIT_DETAIL table during which the Condition was determined (diagnosed). @@ -2340,7 +2200,6 @@ condition_source_value The source code for the Condition as it appears in the source data. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference. @@ -2372,7 +2228,6 @@ condition_source_concept_id A foreign key to a Condition Concept that refers to the code used in the source. @@ -2404,7 +2257,6 @@ condition_status_source_value The source code for the condition status as it appears in the source data. This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference. @@ -2449,13 +2298,13 @@ ETL Conventions Datatype @@ -2509,7 +2354,6 @@ person_id A foreign key identifier to the Person who is subjected to the Drug. The demographic details of that Person are stored in the PERSON table. @@ -2541,7 +2383,6 @@ drug_concept_id A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the ‘’Drug’’ domain. @@ -2573,7 +2413,6 @@ drug_exposure_start_date The start date for the current instance of Drug utilization. Valid entries include a start date of a prescription, the date a prescription was filled, or the date on which a Drug administration procedure was recorded. @@ -2605,7 +2441,6 @@ drug_exposure_start_datetime The start date and time for the current instance of Drug utilization. Valid entries include a start datetime of a prescription, the date and time a prescription was filled, or the date and time on which a Drug administration procedure was recorded. @@ -2637,7 +2469,6 @@ drug_exposure_end_date The end date for the current instance of Drug utilization. Depending on different sources, it could be a known or an inferred date and denotes the last day at which the patient was still exposed to Drug. @@ -2669,7 +2497,6 @@ drug_exposure_end_datetime The end date and time for the current instance of Drug utilization. Depending on different sources, it could be a known or an inferred date and time and denotes the last day at which the patient was still exposed to Drug. @@ -2701,7 +2525,6 @@ verbatim_end_date The known end date of a drug_exposure as provided by the source. @@ -2733,7 +2553,6 @@ drug_type_concept_id A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of Drug Exposure recorded. It indicates how the Drug Exposure was represented in the source data and belongs to the ‘’Drug Type’’ vocabulary. @@ -2765,7 +2583,6 @@ stop_reason The reason the Drug was stopped. Reasons include regimen completed, changed, removed, etc. @@ -2797,7 +2611,6 @@ refills The number of refills after the initial prescription. The initial prescription is not counted, values start with null. @@ -2829,7 +2639,6 @@ quantity The quantity of drug as recorded in the original prescription or dispensing record. @@ -2861,7 +2667,6 @@ days_supply The number of days of supply of the medication as prescribed. This reflects the intention of the provider for the length of exposure. @@ -2893,7 +2695,6 @@ sig The directions (‘’signetur’’) on the Drug prescription as recorded in the original prescription (and printed on the container) or dispensing record. @@ -2925,7 +2723,6 @@ route_concept_id A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies reflecting the route of administration and belonging to the ‘’Route’’ domain. @@ -2957,7 +2752,6 @@ lot_number An identifier assigned to a particular quantity or lot of Drug product from the manufacturer. @@ -2989,7 +2780,6 @@ provider_id A foreign key to the provider in the PROVIDER table who initiated (prescribed or administered) the Drug Exposure. @@ -3021,7 +2809,6 @@ visit_occurrence_id A foreign key to the Visit in the VISIT_OCCURRENCE table during which the Drug Exposure was initiated. @@ -3053,7 +2838,6 @@ visit_detail_id A foreign key to the Visit Detail in the VISIT_DETAIL table during which the Drug Exposure was initiated. @@ -3085,7 +2867,6 @@ drug_source_value The source code for the Drug as it appears in the source data. This code is mapped to a Standard Drug concept in the Standardized Vocabularies and the original code is, stored here for reference. @@ -3117,7 +2895,6 @@ drug_source_concept_id A foreign key to a Drug Concept that refers to the code used in the source. @@ -3149,7 +2924,6 @@ route_source_value The information about the route of administration as detailed in the source. @@ -3181,7 +2952,6 @@ dose_unit_source_value The information about the dose unit as detailed in the source. @@ -3226,13 +2993,13 @@ ETL Conventions Datatype @@ -3286,7 +3049,6 @@ person_id A foreign key identifier to the Person who is subjected to the Procedure. The demographic details of that Person are stored in the PERSON table. @@ -3318,7 +3078,6 @@ procedure_concept_id A foreign key that refers to a standard procedure Concept identifier in the Standardized Vocabularies. @@ -3350,7 +3108,6 @@ procedure_date The date on which the Procedure was performed. @@ -3382,7 +3136,6 @@ procedure_datetime The date and time on which the Procedure was performed. @@ -3414,7 +3164,6 @@ procedure_type_concept_id A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of source data from which the procedure record is derived, belonging to the ‘Procedure Type’ vocabulary. @@ -3446,7 +3194,6 @@ modifier_concept_id A foreign key to a Standard Concept identifier for a modifier to the Procedure (e.g. bilateral). These concepts are typically distinguished by ‘Modifier’ concept classes (e.g., ‘CPT4 Modifier’ as part of the ‘CPT4’ vocabulary). @@ -3478,7 +3223,6 @@ quantity The quantity of procedures ordered or administered. @@ -3510,7 +3251,6 @@ provider_id A foreign key to the provider in the PROVIDER table who was responsible for carrying out the procedure. @@ -3542,7 +3280,6 @@ visit_occurrence_id A foreign key to the Visit in the VISIT_OCCURRENCE table during which the Procedure was carried out. @@ -3574,7 +3309,6 @@ visit_detail_id A foreign key to the Visit Detail in the VISIT_DETAIL table during which the Procedure was carried out. @@ -3606,7 +3338,6 @@ procedure_source_value The source code for the Procedure as it appears in the source data. This code is mapped to a standard procedure Concept in the Standardized Vocabularies and the original code is, stored here for reference. Procedure source codes are typically ICD-9-Proc, CPT-4, HCPCS or OPCS-4 codes. @@ -3638,7 +3366,6 @@ procedure_source_concept_id A foreign key to a Procedure Concept that refers to the code used in the source. @@ -3670,7 +3395,6 @@ modifier_source_value The source code for the qualifier as it appears in the source data. @@ -3715,13 +3436,13 @@ ETL Conventions Datatype @@ -3775,7 +3492,6 @@ person_id A foreign key identifier to the Person who is subjected to the Device. The demographic details of that Person are stored in the PERSON table. @@ -3807,7 +3521,6 @@ device_concept_id A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the ‘Device’ domain. @@ -3839,7 +3551,6 @@ device_exposure_start_date The date the Device or supply was applied or used. @@ -3871,7 +3579,6 @@ device_exposure_start_datetime The date and time the Device or supply was applied or used. @@ -3903,7 +3607,6 @@ device_exposure_end_date The date use of the Device or supply was ceased. @@ -3935,7 +3635,6 @@ device_exposure_end_datetime The date and time use of the Device or supply was ceased. @@ -3967,7 +3663,6 @@ device_type_concept_id A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of Device Exposure recorded. It indicates how the Device Exposure was represented in the source data and belongs to the ‘Device Type’ domain. @@ -3999,7 +3693,6 @@ unique_device_id A UDI or equivalent identifying the instance of the Device used in the Person. @@ -4031,7 +3721,6 @@ quantity The number of individual Devices used in the exposure. @@ -4063,7 +3749,6 @@ provider_id A foreign key to the provider in the PROVIDER table who initiated or administered the Device. @@ -4095,7 +3778,6 @@ visit_occurrence_id A foreign key to the visit in the VISIT_OCCURRENCE table during which the Device was used. @@ -4127,7 +3807,6 @@ visit_detail_id A foreign key to the visit detail record in the VISIT_DETAIL table during which the Device was used. @@ -4159,7 +3836,6 @@ device_source_value The source code for the Device as it appears in the source data. This code is mapped to a Standard Device Concept in the Standardized Vocabularies and the original code is stored here for reference. @@ -4191,7 +3864,6 @@ device_source_concept_id A foreign key to a Device Concept that refers to the code used in the source. @@ -4236,13 +3906,13 @@ ETL Conventions Datatype @@ -4296,7 +3962,6 @@ person_id A foreign key identifier to the Person about whom the measurement was recorded. The demographic details of that Person are stored in the PERSON table. @@ -4328,7 +3991,6 @@ measurement_concept_id A foreign key to the standard measurement concept identifier in the Standardized Vocabularies. These belong to the ‘Measurement’ domain, but could overlap with the ‘Observation’ domain (see #3 below). @@ -4360,7 +4021,6 @@ measurement_date The date of the Measurement. @@ -4392,7 +4049,6 @@ measurement_datetime The date and time of the Measurement. Some database systems don’t have a datatype of time. To accommodate all temporal analyses, datatype datetime can be used (combining measurement_date and measurement_time forum discussion) @@ -4424,7 +4077,6 @@ measurement_time The time of the Measurement. This is present for backwards compatibility and will be deprecated in an upcoming version @@ -4456,7 +4105,6 @@ measurement_type_concept_id A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the provenance from where the Measurement record was recorded. These belong to the ‘Meas Type’ vocabulary @@ -4488,7 +4135,6 @@ operator_concept_id A foreign key identifier to the predefined Concept in the Standardized Vocabularies reflecting the mathematical operator that is applied to the value_as_number. Operators are <, <=, =, >=, > and these concepts belong to the ‘Meas Value Operator’ domain. @@ -4520,7 +4164,6 @@ value_as_number A Measurement result where the result is expressed as a numeric value. @@ -4552,7 +4192,6 @@ value_as_concept_id A foreign key to a Measurement result represented as a Concept from the Standardized Vocabularies (e.g., positive/negative, present/absent, low/high, etc.). These belong to the ‘Meas Value’ domain @@ -4584,7 +4221,6 @@ unit_concept_id A foreign key to a Standard Concept ID of Measurement Units in the Standardized Vocabularies that belong to the ‘Unit’ domain. @@ -4616,7 +4251,6 @@ range_low The lower limit of the normal range of the Measurement result. The lower range is assumed to be of the same unit of measure as the Measurement value. @@ -4648,7 +4279,6 @@ range_high The upper limit of the normal range of the Measurement. The upper range is assumed to be of the same unit of measure as the Measurement value. @@ -4680,7 +4307,6 @@ provider_id A foreign key to the provider in the PROVIDER table who was responsible for initiating or obtaining the measurement. @@ -4712,7 +4336,6 @@ visit_occurrence_id A foreign key to the Visit in the VISIT_OCCURRENCE table during which the Measurement was recorded. @@ -4744,7 +4365,6 @@ visit_detail_id A foreign key to the Visit Detail in the VISIT_DETAIL table during which the Measurement was recorded. @@ -4776,7 +4394,6 @@ measurement_source_value The Measurement name as it appears in the source data. This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference. @@ -4808,7 +4422,6 @@ measurement_source_concept_id A foreign key to a Concept in the Standard Vocabularies that refers to the code used in the source. @@ -4840,7 +4451,6 @@ unit_source_value The source code for the unit as it appears in the source data. This code is mapped to a standard unit concept in the Standardized Vocabularies and the original code is stored here for reference. @@ -4872,7 +4479,6 @@ value_source_value The source value associated with the content of the value_as_number or value_as_concept_id as stored in the source data. @@ -4917,13 +4520,13 @@ ETL Conventions Datatype @@ -4977,7 +4576,6 @@ person_id A foreign key identifier to the Person for whom the visit is recorded. The demographic details of that Person are stored in the PERSON table. @@ -5009,7 +4605,6 @@ visit_detail_concept_id A foreign key that refers to a visit Concept identifier in the Standardized Vocabularies belonging to the ‘Visit’ Vocabulary. @@ -5041,7 +4635,6 @@ visit_detail_start_date The start date of the visit. @@ -5073,7 +4663,6 @@ visit_detail_start_datetime The date and time of the visit started. @@ -5105,7 +4691,6 @@ visit_detail_end_date The end date of the visit. If this is a one-day visit the end date should match the start date. @@ -5137,7 +4719,6 @@ visit_detail_end_datetime The date and time of the visit end. @@ -5169,7 +4747,6 @@ visit_detail_type_concept_id A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of source data from which the visit record is derived belonging to the ‘Visit Type’ vocabulary. @@ -5201,7 +4775,6 @@ provider_id A foreign key to the provider in the provider table who was associated with the visit. @@ -5233,7 +4804,6 @@ care_site_id A foreign key to the care site in the care site table that was visited. @@ -5265,7 +4833,6 @@ visit_detail_source_value The source code for the visit as it appears in the source data. @@ -5297,7 +4861,6 @@ visit_detail_source_concept_id A foreign key to a Concept that refers to the code used in the source. @@ -5329,7 +4890,6 @@ admitted_from_source_value The source code for the admitting source as it appears in the source data. @@ -5361,7 +4918,6 @@ admitted_from_concept_id A foreign key to the predefined concept in the ‘Place of Service’ Vocabulary reflecting the admitting source for a visit. @@ -5393,7 +4947,6 @@ discharge_to_source_value The source code for the discharge disposition as it appears in the source data. @@ -5425,7 +4975,6 @@ discharge_to_concept_id A foreign key to the predefined concept in the ‘Place of Service’ Vocabulary reflecting the discharge disposition for a visit. @@ -5457,7 +5004,6 @@ preceding_visit_detail_id A foreign key to the VISIT_DETAIL table of the visit immediately preceding this visit @@ -5489,7 +5033,6 @@ visit_detail_parent_id A foreign key to the VISIT_DETAIL table record to represent the immediate parent visit-detail record. @@ -5521,7 +5062,6 @@ visit_occurrence_id A foreign key that refers to the record in the VISIT_OCCURRENCE table. This is a required field, because for every visit_detail is a child of visit_occurrence and cannot exist without a corresponding parent record in visit_occurrence. @@ -5566,13 +5104,13 @@ ETL Conventions Datatype @@ -5626,7 +5160,6 @@ person_id A foreign key identifier to the Person about whom the Note was recorded. The demographic details of that Person are stored in the PERSON table. @@ -5658,7 +5189,6 @@ note_event_id A foreign key identifier to the event (e.g. Measurement, Procedure, Visit, Drug Exposure, etc) record during which the note was recorded. @@ -5690,7 +5217,6 @@ note_event_field_concept_id A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the field to which the note_event_id is referring. @@ -5722,7 +5246,6 @@ note_date The date the note was recorded. @@ -5754,7 +5274,6 @@ note_datetime The date and time the note was recorded. @@ -5786,7 +5302,6 @@ note_type_concept_id A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the type, origin or provenance of the Note. These belong to the ‘Note Type’ vocabulary @@ -5818,7 +5332,6 @@ note_class_concept_id A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the HL7 LOINC Document Type Vocabulary classification of the note. @@ -5850,7 +5361,6 @@ note_title The title of the Note as it appears in the source. @@ -5882,7 +5389,6 @@ note_text The content of the Note. @@ -5914,7 +5417,6 @@ encoding_concept_id A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the note character encoding type @@ -5946,7 +5446,6 @@ language_concept_id A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the language of the note @@ -5978,7 +5475,6 @@ provider_id A foreign key to the Provider in the PROVIDER table who took the Note. @@ -6010,7 +5503,6 @@ visit_occurrence_id A foreign key to the Visit in the VISIT_OCCURRENCE table when the Note was taken. @@ -6042,7 +5532,6 @@ visit_detail_id A foreign key to the Visit in the VISIT_DETAIL table when the Note was taken. @@ -6074,7 +5561,6 @@ note_source_value The source value associated with the origin of the Note @@ -6119,13 +5602,13 @@ ETL Conventions Datatype @@ -6179,7 +5658,6 @@ note_id A foreign key to the Note table note the term was @@ -6211,7 +5686,6 @@ section_concept_id A foreign key to the predefined Concept in the Standardized Vocabularies representing the section of the extracted term. @@ -6243,7 +5715,6 @@ snippet A small window of text surrounding the term. @@ -6275,7 +5743,6 @@ offset Character offset of the extracted term in the input note. @@ -6307,7 +5771,6 @@ lexical_variant Raw text extracted from the NLP tool. @@ -6339,7 +5799,6 @@ note_nlp_concept_id A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the normalized concept for the extracted term. Domain of the term is represented as part of the Concept table. @@ -6371,7 +5828,6 @@ note_nlp_source_concept_id A foreign key to a Concept that refers to the code in the source vocabulary used by the NLP system @@ -6403,7 +5857,6 @@ nlp_system Name and version of the NLP system that extracted the term.Useful for data provenance. @@ -6435,7 +5885,6 @@ nlp_date The date of the note processing.Useful for data provenance. @@ -6467,7 +5913,6 @@ nlp_datetime The date and time of the note processing. Useful for data provenance. @@ -6499,7 +5941,6 @@ term_exists A summary modifier that signifies presence or absence of the term for a given patient. Useful for quick querying. @@ -6531,7 +5969,6 @@ term_temporal An optional time modifier associated with the extracted term. (for now “past” or “present” only). Standardize it later. @@ -6563,7 +5997,6 @@ term_modifiers A compact description of all the modifiers of the specific term extracted by the NLP system. (e.g. “son has rash” ? “negated=no,subject=family, certainty=undef,conditional=false,general=false”). @@ -6608,13 +6038,13 @@ ETL Conventions Datatype @@ -6668,7 +6094,6 @@ PERSON_ID A foreign key identifier to the Person in the PERSON table about whom the survey was completed. @@ -6700,7 +6123,6 @@ SURVEY_CONCEPT_ID A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the name and identity of the survey. @@ -6732,7 +6152,6 @@ SURVEY_START_DATE Date on which the survey was started. @@ -6764,7 +6180,6 @@ SURVEY_START_DATETIME Date and time the survey was started. @@ -6796,7 +6208,6 @@ SURVEY_END_DATE Date on which the survey was completed. @@ -6828,7 +6236,6 @@ SURVEY_END_DATETIME Date and time the survey was completed. @@ -6860,7 +6264,6 @@ PROVIDER_ID A foreign key to the provider in the provider table who was associated with the survey completion. @@ -6892,7 +6293,6 @@ ASSISTED_CONCEPT_ID A foreign key to the predefined Concept identifier in the Standardized Vocabularies indicating whether the survey was completed with assistance. @@ -6924,7 +6321,6 @@ RESPONDENT_TYPE_CONCEPT_ID A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the respondent type. Example: Research Associate, Patient. @@ -6956,7 +6350,6 @@ TIMING_CONCEPT_ID A foreign key to the predefined Concept identifier in the Standardized Vocabularies that refers to a certain timing. Example: 3 month follow-up, 6 month follow-up. @@ -6988,7 +6378,6 @@ COLLECTION_METHOD_CONCEPT_ID A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the data collection method (e.g. Paper, Telephone, Electronic Questionnaire). @@ -7020,7 +6407,6 @@ ASSISTED_SOURCE_VALUE Source value representing whether patient required assistance to complete the survey. Example: “Completed without assistance”, ”Completed with assistance”. @@ -7052,7 +6435,6 @@ RESPONDENT_TYPE_SOURCE_VALUE Source code representing role of person who completed the survey. @@ -7084,7 +6463,6 @@ TIMING_SOURCE_VALUE Text string representing the timing of the survey. Example: Baseline, 6-month follow-up. @@ -7116,7 +6491,6 @@ COLLECTION_METHOD_SOURCE_VALUE The collection method as it appears in the source data. @@ -7148,7 +6519,6 @@ SURVEY_SOURCE_VALUE The survey name/title as it appears in the source data. @@ -7180,7 +6547,6 @@ SURVEY_SOURCE_CONCEPT_ID A foreign key to a predefined Concept that refers to the code for the survey name/title used in the source. @@ -7212,7 +6576,6 @@ SURVEY_SOURCE_IDENTIFIER Unique identifier for each completed survey in source system. @@ -7244,7 +6604,6 @@ VALIDATED_SURVEY_CONCEPT_ID A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the validation status of the survey. @@ -7276,7 +6633,6 @@ VALIDATED_SURVEY_SOURCE_VALUE Source value representing the validation status of the survey. @@ -7308,7 +6661,6 @@ SURVEY_VERSION_NUMBER Version number of the questionnaire or survey used. @@ -7340,7 +6689,6 @@ VISIT_OCCURRENCE_ID A foreign key to the VISIT_OCCURRENCE table during which the survey was completed @@ -7372,7 +6718,6 @@ RESPONSE_VISIT_OCCURRENCE_ID A foreign key to the visit in the VISIT_OCCURRENCE table during which treatment was carried out that relates to this survey. @@ -7417,13 +6760,13 @@ ETL Conventions Datatype @@ -7477,7 +6816,6 @@ person_id A foreign key identifier to the Person about whom the observation was recorded. The demographic details of that Person are stored in the PERSON table. @@ -7509,7 +6845,6 @@ observation_concept_id A foreign key to the standard observation concept identifier in the Standardized Vocabularies. @@ -7541,7 +6874,6 @@ observation_date The date of the observation. @@ -7573,7 +6902,6 @@ observation_datetime The date and time of the observation. @@ -7605,7 +6930,6 @@ observation_type_concept_id A foreign key to the predefined concept identifier in the Standardized Vocabularies reflecting the type of the observation. @@ -7637,7 +6960,6 @@ value_as_number The observation result stored as a number. This is applicable to observations where the result is expressed as a numeric value. @@ -7669,7 +6988,6 @@ value_as_string The observation result stored as a string. This is applicable to observations where the result is expressed as verbatim text. @@ -7701,7 +7016,6 @@ value_as_concept_id A foreign key to an observation result stored as a Concept ID. This is applicable to observations where the result can be expressed as a Standard Concept from the Standardized Vocabularies (e.g., positive/negative, present/absent, low/high, etc.). @@ -7733,7 +7045,6 @@ qualifier_concept_id A foreign key to a Standard Concept ID for a qualifier (e.g., severity of drug-drug interaction alert) @@ -7765,7 +7074,6 @@ unit_concept_id A foreign key to a Standard Concept ID of measurement units in the Standardized Vocabularies. @@ -7797,7 +7104,6 @@ provider_id A foreign key to the provider in the PROVIDER table who was responsible for making the observation. @@ -7829,7 +7133,6 @@ visit_occurrence_id A foreign key to the visit in the VISIT_OCCURRENCE table during which the observation was recorded. @@ -7861,7 +7162,6 @@ visit_detail_id A foreign key to the visit in the VISIT_DETAIL table during which the observation was recorded. @@ -7893,7 +7191,6 @@ observation_source_value The observation code as it appears in the source data. This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is, stored here for reference. @@ -7925,7 +7219,6 @@ observation_source_concept_id A foreign key to a Concept that refers to the code used in the source. @@ -7957,7 +7248,6 @@ unit_source_value The source code for the unit as it appears in the source data. This code is mapped to a standard unit concept in the Standardized Vocabularies and the original code is, stored here for reference. @@ -7989,7 +7276,6 @@ qualifier_source_value The source value associated with a qualifier to characterize the observation @@ -8021,7 +7304,6 @@ observation_event_id A foreign key to an event table (e.g., PROCEDURE_OCCURRENCE_ID). @@ -8053,7 +7332,6 @@ obs_event_field_concept_id A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies referring to the field represented in the OBSERVATION_EVENT_ID. @@ -8085,7 +7361,6 @@ value_as_datetime The observation result stored as a datetime value. This is applicable to observations where the result is expressed as a point in time. @@ -8130,13 +7402,13 @@ ETL Conventions Datatype @@ -8190,7 +7458,6 @@ person_id A foreign key identifier to the Person for whom the Specimen is recorded. @@ -8222,7 +7487,6 @@ specimen_concept_id A foreign key referring to a Standard Concept identifier in the Standardized Vocabularies for the Specimen. @@ -8254,7 +7516,6 @@ specimen_type_concept_id A foreign key referring to the Concept identifier in the Standardized Vocabularies reflecting the system of record from which the Specimen was represented in the source data. @@ -8286,7 +7546,6 @@ specimen_date The date the specimen was obtained from the Person. @@ -8318,7 +7574,6 @@ specimen_datetime The date and time on the date when the Specimen was obtained from the person. @@ -8350,7 +7602,6 @@ quantity The amount of specimen collection from the person during the sampling procedure. @@ -8382,7 +7630,6 @@ unit_concept_id A foreign key to a Standard Concept identifier for the Unit associated with the numeric quantity of the Specimen collection. @@ -8414,7 +7659,6 @@ anatomic_site_concept_id A foreign key to a Standard Concept identifier for the anatomic location of specimen collection. @@ -8446,7 +7688,6 @@ disease_status_concept_id A foreign key to a Standard Concept identifier for the Disease Status of specimen collection. @@ -8478,7 +7717,6 @@ specimen_source_id The Specimen identifier as it appears in the source data. @@ -8510,7 +7745,6 @@ specimen_source_value The Specimen value as it appears in the source data. This value is mapped to a Standard Concept in the Standardized Vocabularies and the original code is, stored here for reference. @@ -8542,7 +7773,6 @@ unit_source_value The information about the Unit as detailed in the source. @@ -8574,7 +7801,6 @@ anatomic_site_source_value The information about the anatomic site as detailed in the source. @@ -8606,7 +7829,6 @@ disease_status_source_value The information about the disease status as detailed in the source. @@ -8651,13 +7870,13 @@ ETL Conventions Datatype @@ -8711,7 +7927,6 @@ fact_id_1 The unique identifier in the table corresponding to the domain of fact one. @@ -8743,7 +7955,6 @@ domain_concept_id_2 The concept representing the domain of fact two, from which the corresponding table can be inferred. @@ -8775,7 +7984,6 @@ fact_id_2 The unique identifier in the table corresponding to the domain of fact two. @@ -8807,7 +8012,6 @@ relationship_concept_id A foreign key to a Standard Concept ID of relationship in the Standardized Vocabularies. @@ -8852,13 +8054,13 @@ ETL Conventions Datatype @@ -8912,7 +8110,6 @@ address_1 The address field 1, typically used for the street address, as it appears in the source data. @@ -8944,7 +8138,6 @@ address_2 The address field 2, typically used for additional detail such as buildings, suites, floors, as it appears in the source data. @@ -8976,7 +8166,6 @@ city The city field as it appears in the source data. @@ -9008,7 +8194,6 @@ state The state field as it appears in the source data. @@ -9040,7 +8222,6 @@ zip The zip or postal code. @@ -9072,7 +8250,6 @@ county The county. @@ -9104,7 +8278,6 @@ country The country @@ -9136,7 +8306,6 @@ location_source_value The verbatim information that is used to uniquely identify the location as it appears in the source data. @@ -9168,7 +8334,6 @@ latitude The geocoded latitude @@ -9200,7 +8362,6 @@ longitude The geocoded longitude @@ -9245,13 +8403,13 @@ ETL Conventions Datatype @@ -9305,7 +8460,6 @@ relationship_type_concept_id The type of relationship between location and entity. @@ -9337,7 +8489,6 @@ domain_id The domain of the entity that is related to the location. Either PERSON, PROVIDER, or CARE_SITE. @@ -9369,7 +8517,6 @@ entity_id The unique identifier for the entity. References either person_id, provider_id, or care_site_id, depending on domain_id. @@ -9401,7 +8545,6 @@ start_date The date the relationship started. @@ -9433,7 +8573,6 @@ end_date The date the relationship ended. @@ -9478,13 +8614,13 @@ ETL Conventions Datatype @@ -9538,7 +8670,6 @@ care_site_name The verbatim description or name of the Care Site as in data source @@ -9570,7 +8698,6 @@ place_of_service_concept_id A foreign key that refers to a Place of Service Concept ID in the Standardized Vocabularies. @@ -9602,7 +8727,6 @@ location_id A foreign key to the geographic Location in the LOCATION table, where the detailed address information is stored. @@ -9634,7 +8755,6 @@ care_site_source_value The identifier for the Care Site in the source data, stored here for reference. @@ -9666,7 +8783,6 @@ place_of_service_source_value The source code for the Place of Service as it appears in the source data, stored here for reference. @@ -9711,13 +8824,13 @@ ETL Conventions Datatype @@ -9771,7 +8880,6 @@ provider_name A description of the Provider. @@ -9803,7 +8908,6 @@ npi The National Provider Identifier (NPI) of the provider. @@ -9835,7 +8936,6 @@ dea The Drug Enforcement Administration (DEA) number of the provider. @@ -9867,7 +8964,6 @@ specialty_concept_id A foreign key to a Standard Specialty Concept ID in the Standardized Vocabularies. @@ -9899,7 +8993,6 @@ care_site_id A foreign key to the main Care Site where the provider is practicing. @@ -9931,7 +9022,6 @@ year_of_birth The year of birth of the Provider. @@ -9963,7 +9050,6 @@ gender_concept_id The gender of the Provider. @@ -9995,7 +9080,6 @@ provider_source_value The identifier used for the Provider in the source data, stored here for reference. @@ -10027,7 +9108,6 @@ specialty_source_value The source code for the Provider specialty as it appears in the source data, stored here for reference. @@ -10059,7 +9136,6 @@ specialty_source_concept_id A foreign key to a Concept that refers to the code used in the source. @@ -10091,7 +9165,6 @@ gender_source_value The gender code for the Provider as it appears in the source data, stored here for reference. @@ -10123,7 +9193,6 @@ gender_source_concept_id A foreign key to a Concept that refers to the code used in the source. @@ -10168,13 +9235,13 @@ ETL Conventions Datatype @@ -10228,7 +9292,6 @@ person_id A foreign key identifier to the Person covered by the payer. The demographic details of that Person are stored in the PERSON table. @@ -10260,7 +9321,6 @@ contract_person_id A foreign key identifier to the person_id in person table, for the person who is the primary subscriber/contract owner for the record in the payer_plan_period table. Maybe the same person or different person, depending on who is the primary subscriber/contract owner. @@ -10292,7 +9349,6 @@ payer_plan_period_start_date The start date of the payer plan period. @@ -10324,7 +9377,6 @@ payer_plan_period_end_date The end date of the payer plan period. @@ -10356,7 +9405,6 @@ payer_concept_id A foreign key that refers to a standard Payer concept identifier in the Standarized Vocabularies @@ -10388,7 +9434,6 @@ payer_source_value The source code for the payer as it appears in the source data. @@ -10420,7 +9462,6 @@ payer_source_concept_id A foreign key to a payer concept that refers to the code used in the source. @@ -10452,7 +9491,6 @@ plan_concept_id A foreign key that refers to a standard plan concept identifier that represents the health benefit plan in the Standardized Vocabularies. @@ -10484,7 +9520,6 @@ plan_source_value The source code for the Person’s health benefit plan as it appears in the source data. @@ -10516,7 +9548,6 @@ plan_source_concept_id A foreign key to a plan concept that refers to the plan code used in the source data. @@ -10548,7 +9577,6 @@ contract_concept_id A foreign key to a standard concept representing the reason justifying the contract between person_id and contract_person_id. @@ -10580,7 +9606,6 @@ contract_source_value The source code representing the reason justifying the contract. Usually it is family relationship like a spouse, domestic partner, child etc. @@ -10612,7 +9634,6 @@ contract_source_concept_id A foreign key to a concept that refers to the code used in the source as the reason justifying the contract. @@ -10644,7 +9663,6 @@ sponsor_concept_id A foreign key that refers to a concept identifier that represents the sponsor in the Standardized Vocabularies. @@ -10676,7 +9692,6 @@ sponsor_source_value The source code for the Person’s sponsor of the health plan as it appears in the source data. @@ -10708,7 +9720,6 @@ sponsor_source_concept_id A foreign key to a sponsor concept that refers to the sponsor code used in the source data. @@ -10740,7 +9749,6 @@ family_source_value The source code for the Person’s family as it appears in the source data. @@ -10772,7 +9777,6 @@ stop_reason_concept_id A foreign key that refers to a standard termination reason that represents the reason for the termination in the Standardized Vocabularies. @@ -10804,7 +9806,6 @@ stop_reason_source_value The reason for stop-coverage as it appears in the source data. @@ -10836,7 +9834,6 @@ stop_reason_source_concept_id A foreign key to a stop-coverage concept that refers to the code used in the source. @@ -10881,13 +9876,13 @@ ETL Conventions Datatype @@ -10941,7 +9932,6 @@ person_id A unique identifier for each PERSON. @@ -10973,7 +9961,6 @@ cost_event_id A foreign key identifier to the event (e.g. Measurement, Procedure, Visit, Drug Exposure, etc) record for which cost data are recorded. @@ -11005,7 +9989,6 @@ cost_event_field_concept_id A foreign key identifier to a concept in the CONCEPT table representing the identity of the field represented by COST_EVENT_ID @@ -11037,7 +10018,6 @@ cost_concept_id A foreign key that refers to a Standard Cost Concept identifier in the Standardized Vocabularies belonging to the ‘Cost’ vocabulary. @@ -11069,7 +10047,6 @@ cost_type_concept_id A foreign key identifier to a concept in the CONCEPT table for the provenance or the source of the COST data and belonging to the ‘Cost Type’ vocabulary @@ -11101,7 +10076,6 @@ cost_source_concept_id A foreign key to a Cost Concept that refers to the code used in the source. @@ -11133,7 +10105,6 @@ cost_source_value The source value for the cost as it appears in the source data @@ -11165,7 +10133,6 @@ currency_concept_id A foreign key identifier to the concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar. These belong to the ‘Currency’ vocabulary @@ -11197,7 +10162,6 @@ cost The actual financial cost amount @@ -11229,7 +10190,6 @@ incurred_date The first date of service of the clinical event corresponding to the cost as in table capturing the information (e.g. date of visit, date of procedure, date of condition, date of drug etc). @@ -11261,7 +10218,6 @@ billed_date The date a bill was generated for a service or encounter @@ -11293,7 +10246,6 @@ paid_date The date payment was received for a service or encounter @@ -11325,7 +10274,6 @@ revenue_code_concept_id A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for Revenue codes belonging to the ‘Revenue Code’ vocabulary. @@ -11357,7 +10303,6 @@ drg_concept_id A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for DRG codes belonging to the ‘DRG’ vocabulary. @@ -11389,7 +10331,6 @@ revenue_code_source_value The source value for the Revenue code as it appears in the source data, stored here for reference. @@ -11421,7 +10359,6 @@ drg_source_value The source value for the 3-digit DRG source code as it appears in the source data, stored here for reference. @@ -11453,7 +10387,6 @@ payer_plan_period_id A foreign key to the PAYER_PLAN_PERIOD table, where the details of the Payer, Plan and Family are stored. Record the payer_plan_id that relates to the payer who contributed to the paid_by_payer field. @@ -11498,13 +10428,13 @@ ETL Conventions Datatype @@ -11558,7 +10484,6 @@ person_id A foreign key identifier to the Person who is subjected to the Drug during the fDrug Era. The demographic details of that Person are stored in the PERSON table. @@ -11590,7 +10513,6 @@ drug_concept_id A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the Ingredient Concept. @@ -11654,7 +10572,6 @@ drug_era_end_datetime The end date for the drug era constructed from the individual instance of drug exposures. It is the end date of the final continuously recorded instance of utilization of a drug. @@ -11686,7 +10600,6 @@ drug_exposure_count The number of individual Drug Exposure occurrences used to construct the Drug Era. @@ -11718,7 +10628,6 @@ gap_days The number of days that are not covered by DRUG_EXPOSURE records that wer @@ -11763,13 +10669,13 @@ ETL Conventions Datatype @@ -11823,7 +10725,6 @@ person_id A foreign key identifier to the Person who is subjected to the drug during the drug era. The demographic details of that Person are stored in the PERSON table. @@ -11855,7 +10754,6 @@ drug_concept_id A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the active Ingredient Concept. @@ -11919,7 +10815,6 @@ dose_value The numeric value of the dose. @@ -11951,7 +10843,6 @@ dose_era_start_datetime The start date for the drug era constructed from the individual instances of drug exposures. It is the start date of the very first chronologically recorded instance of utilization of a drug. @@ -11983,7 +10871,6 @@ dose_era_end_datetime The end date for the drug era constructed from the individual instance of drug exposures. It is the end date of the final continuously recorded instance of utilization of a drug. @@ -12028,13 +10912,13 @@ ETL Conventions Datatype @@ -12088,7 +10968,6 @@ person_id A foreign key identifier to the Person who is experiencing the Condition during the Condition Era. The demographic details of that Person are stored in the PERSON table. @@ -12120,7 +10997,6 @@ condition_concept_id A foreign key that refers to a standard Condition Concept identifier in the Standardized Vocabularies. @@ -12152,7 +11027,6 @@ condition_era_start_datetime The start date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the start date of the very first chronologically recorded instance of the condition. @@ -12184,7 +11055,6 @@ condition_era_end_datetime The end date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the end date of the final continuously recorded instance of the Condition. @@ -12216,7 +11083,6 @@ condition_occurrence_count The number of individual Condition Occurrences used to construct the condition era. diff --git a/docs/contribute.html b/docs/contribute.html index c708752..29cd18c 100644 --- a/docs/contribute.html +++ b/docs/contribute.html @@ -386,6 +386,13 @@ div.tocify { +
  • + + + + Background + +
  • @@ -410,6 +417,34 @@ div.tocify {
    • +
  • + + +
  • @@ -426,7 +461,12 @@ div.tocify {
    • @@ -441,32 +481,13 @@ div.tocify { -

    ##TODO for CDM # File bug reports

    -

    If you’ve found a bug you can help out by filing a bug report. Each package has an issue tracker where you can create a new issue. Try and be as specific as possible. What error message occurs? Can you provide a simple example to reproduce the problem? What versions of the various packages are you running?

    -
    -

    Write help files

    -

    If you’re a bit more experienced with the Methods Library and are looking to improve your open source development skills, the next step up is to contribute a pull request to a Methods Library package. The most important thing to know is that Methods Library packages use roxygen2: this means that documentation is found in the R code close to the source of each function.

    +
    +

    File bug reports

    +

    If you’ve found a bug you can help out by filing a bug report. Try and be as specific as possible. What error message occurs? Can you provide a simple example to reproduce the problem? What versions of the various packages are you running?

    -
    -

    Write unit tests

    -

    An important part of validating the methods in the library is unit testing. A unit test is a small program that tests a specific function in the library. For example, there are several unit tests that make sure the propensity score matching works correctly. We can never have enough unit tests, and writing unit tests is an excellent way to learn how the Methods Library packages work under the hood.

    -
    -
    -

    Add methods

    -

    We are always looking for new methods and packages to add to the Methods Libary. However, in order to qualify for inclusion a package must meet the following requirements:

    -
      -
    • Pass R check without warnings or notes.
      • -
    • Adhere to OHDSI’s code style guidelines and overall development practices.
      • -
    • Have unit tests that test the package’s most important routines.
      • -
    • For population-level estimation methods: be evaluated using the OHDSI Methods Benchmark.
      • -
    -
    -
    -

    Code style guidelines

    - +
    +

    Join meetings

    +

    Please come to meetings and contribute to the discussion! All details can be found our home page.

    diff --git a/docs/dataModelConventions.html b/docs/dataModelConventions.html index 366ec35..c10acee 100644 --- a/docs/dataModelConventions.html +++ b/docs/dataModelConventions.html @@ -386,6 +386,13 @@ div.tocify { +
  • + + + + Background + +
  • @@ -410,6 +417,34 @@ div.tocify {
    • +
  • + + +
  • @@ -426,7 +461,12 @@ div.tocify {
    • diff --git a/docs/faq.html b/docs/faq.html index 1654975..42a1ada 100644 --- a/docs/faq.html +++ b/docs/faq.html @@ -288,6 +288,13 @@ $(document).ready(function () { +
  • + + + + Background + +
  • @@ -312,6 +319,34 @@ $(document).ready(function () {
    • +
  • + + +
  • @@ -328,7 +363,12 @@ $(document).ready(function () {
    • diff --git a/docs/index.html b/docs/index.html index c7b03d1..16b6259 100644 --- a/docs/index.html +++ b/docs/index.html @@ -19,9 +19,6 @@ - - - @@ -271,101 +268,6 @@ $(document).ready(function () { - - - - - -
    -
    -
    -
    -
    - -
    - -
    @@ -443,46 +385,35 @@ div.tocify {
    -
    -

    Background

    -

    The Observational Medical Outcomes Partnership (OMOP) was a public-private partnership established to inform the appropriate use of observational healthcare databases for studying the effects of medical products. Over the course of the 5-year project and through its community of researchers from industry, government, and academia, OMOP successfully achieved its aims to:

    -
      -
    • Conduct methodological research to empirically evaluate the performance of various analytical methods on their ability to identify true associations and avoid false findings
      • -
    • Develop tools and capabilities for transforming, characterizing, and analysing disparate data sources across the health care delivery spectrum
      • -
    • Establish a shared resource so that the broader research community can collaboratively advance the science
      • -
    -

    The results of OMOP’s research has been widely published and presented at scientific conferences, including annual symposia.

    -

    The OMOP Legacy continues…

    -

    The community is actively using the OMOP Common Data Model for their various research purposes. Those tools will continue to be maintained and supported, and information about this work is available in the public domain.

    -

    The OMOP Common Data Model will continue to be an open-source community standard for observational healthcare data. The model specifications and associated work products will be placed in the public domain, and the entire research community is encouraged to use these tools to support everybody’s own research activities.

    +

    The OMOP Common Data Model is managed by the OHDSI CDM Working Group. Through the end of 2019 and into 2020 our goal is to fully update the documentation in an effort to facilitate greater understanding of the model. Almost every forum post relating to a question on how to map data into the CDM inevitably references the technical and difficult-to-understand explanations of the tables and fields currently on the wiki. To remedy this each month we are focusing on one or two tables, diving fully into the user guidance and ETL specifications. We meet twice a month, on the first Tuesday at 1pm est and on the 3rd Tuesday at 9am est (meeting details below).

    +

    In addition to documentation the formal remit of the CDM Working Group is to hear proposals for change, ratifying only those with valid use cases and data to support them. This process will be slower through 2020 though proposals related to existing CDM tables will be considered during the months those tables are being updated. For example November 2019 will be focused on the PERSON and OBSERVATION_PERIOD tables so any proposals related to those two tables will be evaluated during November 2019. Once proposals are accepted they are listed as such and will be integrated in an upcoming version of the OMOP CDM. Currently accepted proposals can be found under the “Proposals” drop down across the top.

    +
    +

    CDM WG Meeting Information

    +

    Every first Tuesday of the month at 1pm est
    +Skype Meeting
    +Join by phone
    +US toll-free: +1 (908) 316-2436
    +Attendee access code: 215874708#
    +Global Numbers

    +

    Every third Tuesday of the month at 9am est
    +Skype Meeting
    +Join by phone
    +US toll-free: +1 (908) 316-2436
    +Attendee access code: 180836323#
    +Global Numbers

    -
    -

    The Role of the Common Data Model

    -

    No single observational data source provides a comprehensive view of the clinical data a patient accumulates while receiving healthcare, and therefore none can be sufficient to meet all expected outcome analysis needs. This explains the need for assessing and analyzing multiple data sources concurrently using a common data standard. This standard is provided by the OMOP Common Data Model (CDM).

    -

    The CDM is designed to support the conduct of research to identify and evaluate associations between interventions (drug exposure, procedures, healthcare policy changes etc.) and outcomes caused by these interventions (condition occurrences, procedures, drug exposure etc.). Outcomes can be efficacious (benefit) or adverse (safety risk). Often times, specific patient cohorts (e.g., those taking a certain drug or suffering from a certain disease) may be defined for treatments or outcomes, using clinical events (diagnoses, observations, procedures, etc.) that occur in predefined temporal relationships to each other. The CDM, combined with its standardized content (via the Standardized Vocabularies), will ensure that research methods can be systematically applied to produce meaningfully comparable and reproducible results.

    -
    -
    -

    Design Principles

    -

    The CDM is designed to include all observational health data elements (experiences of the patient receiving health care) that are relevant for analytic use cases to support the generation of reliable scientific evidence about disease natural history, healthcare delivery, effects of medical interventions, the identification of demographic information, health care interventions and outcomes.

    -

    Therefore, the CDM is designed to store observational data to allow for research, under the following principles:

    + -
    -
    diff --git a/docs/inst/csv/OMOP_CDMv5.3.1_Concept_Level.csv b/docs/inst/csv/OMOP_CDMv5.3.1_Concept_Level.csv new file mode 100644 index 0000000..479def4 --- /dev/null +++ b/docs/inst/csv/OMOP_CDMv5.3.1_Concept_Level.csv @@ -0,0 +1,342 @@ +cdmTableName,cdmFieldName,conceptId,conceptName,unitConceptId,unitConceptName,plausibleValueLow,plausibleValueHigh,plausibleGender,isTemporallyConstant,validPrevalenceLow,validPrevalenceHigh +MEASUREMENT,MEASUREMENT_CONCEPT_ID,3004410,Hemoglobin A1c/Hemoglobin.total in Blood,8554,percent,4,15,,Yes,, +MEASUREMENT,MEASUREMENT_CONCEPT_ID,3036277,Body height,8582,centimeter,1,272,,Yes,, +MEASUREMENT,MEASUREMENT_CONCEPT_ID,3016723,Creatinine [Mass/volume] in Serum or Plasma,8840,milligram per deciliter,0.1,10,,Yes,, +MEASUREMENT,MEASUREMENT_CONCEPT_ID,3004249,Systolic blood pressure,8876,millimeter mercury column,60,300,,Yes,, +MEASUREMENT,MEASUREMENT_CONCEPT_ID,3012888,Diastolic blood pressure,8876,millimeter mercury column,30,200,,Yes,, +MEASUREMENT,MEASUREMENT_CONCEPT_ID,3025315,Body weight,9529,kilogram,1,635,,Yes,, +MEASUREMENT,MEASUREMENT_CONCEPT_ID,3038553,Body mass index (BMI) [Ratio],9531,kilogram per square meter,10,80,,Yes,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,26662,Testicular hypofunction,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,26935,Disorder of endocrine testis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,30969,Testicular hyperfunction,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,73801,Scrotal varices,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,74322,Benign neoplasm of scrotum,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,78193,Orchitis and epididymitis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,79758,Primary malignant neoplasm of scrotum,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,141917,Balanitis xerotica obliterans,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,192367,Dysplasia of cervix,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,192676,Cervical intraepithelial neoplasia grade 1,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,192683,Uterovaginal prolapse,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,192854,Intramural leiomyoma of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,192858,Ovarian hyperfunction,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,193254,Disorder of vagina,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,193261,Vaginospasm,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,193262,Inflammatory disorder of penis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,193277,Deliveries by cesarean,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,193437,Neoplasm of uncertain behavior of female genital organ,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,193439,Benign neoplasm of body of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,193522,Acute prostatitis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,193530,Follicular cyst of ovary,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,193739,Ovarian failure,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,193818,Calculus of prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,194092,Uterine prolapse without vaginal wall prolapse,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,194286,"Malignant neoplasm of corpus uteri, excluding isthmus",,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,194412,Dysplasia of vagina,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,194420,Endometriosis of fallopian tube,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,194611,Carcinoma in situ of uterine cervix,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,194696,Dysmenorrhea,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,194871,Trichomonal vulvovaginitis,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,194997,Prostatitis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195009,Leukoplakia of penis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195012,Intermenstrual bleeding - irregular,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195197,Primary malignant neoplasm of vulva,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195316,Atypical endometrial hyperplasia,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195321,Postmenopausal bleeding,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195483,Primary malignant neoplasm of penis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195500,Benign neoplasm of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195501,Polycystic ovaries,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195683,Open wound of penis without complication,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195769,Submucous leiomyoma of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195770,Subserous leiomyoma of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195793,Neoplasm of uncertain behavior of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195867,Noninflammatory disorder of the vagina,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,195873,Leukorrhea,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196048,Primary malignant neoplasm of vagina,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196051,Overlapping malignant neoplasm of female genital organs,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196068,Carcinoma in situ of male genital organ,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196157,Induratio penis plastica,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196158,Disorder of penis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196163,Cervicitis and endocervicitis,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196165,Cervical intraepithelial neoplasia grade 2,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196168,Irregular periods,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196359,Primary malignant neoplasm of uterine cervix,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196364,Benign neoplasm of uterine cervix,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196473,Hypertrophy of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196734,Disorder of prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196738,Disorder of male genital organ,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,196758,Tumor of body of uterus affecting pregnancy,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197032,Hyperplasia of prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197039,Male genital organ vascular diseases,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197044,Female infertility associated with anovulation,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197236,Uterine leiomyoma,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197237,Benign neoplasm of prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197507,Primary malignant neoplasm of male genital organ,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197601,Spermatocele,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197605,Inflammatory disorder of male genital organ,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197606,Female infertility of tubal origin,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197607,Excessive and frequent menstruation,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197609,"Cervical, vaginal and vulval inflammatory diseases",,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197610,Cyst of ovary,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,197938,Uterine inertia,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,198082,Overlapping malignant neoplasm of body of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,198108,Benign neoplasm of fallopian tubes and uterine ligaments,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,198194,Female genital organ symptoms,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,198197,Male infertility,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,198198,Polyp of vagina,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,198202,Cystocele,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,198212,Spotting per vagina in pregnancy,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,198363,Candidiasis of vagina,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,198471,Complex endometrial hyperplasia,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,198483,Stricture or atresia of the vagina,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,198803,Benign prostatic hyperplasia,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,198806,Abscess of prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,199067,Female pelvic inflammatory disease,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,199078,Vaginal wall prolapse,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,199752,Secondary malignant neoplasm of ovary,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,199764,Benign neoplasm of ovary,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,199876,Prolapse of female genital organs,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,199877,Mucous polyp of cervix,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,199878,Light and infrequent menstruation,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,199881,Endometriosis of ovary,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200051,Primary malignant neoplasm of ovary,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200052,Primary malignant neoplasm of uterine adnexa,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200147,Atrophy of prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200445,Chronic prostatitis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200452,Disorder of female genital organs,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200461,Endometriosis of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200670,Benign neoplasm of male genital organ,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200675,Neoplasm of uncertain behavior of ovary,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200775,Endometrial hyperplasia,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200779,Polyp of corpus uteri,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200780,Disorder of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200962,Primary malignant neoplasm of prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,200970,Carcinoma in situ of prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201072,Benign prostatic hypertrophy without outflow obstruction,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201078,Atrophic vaginitis,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201211,Herpetic vulvovaginitis,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201238,Primary malignant neoplasm of female genital organ,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201244,Benign neoplasm of vagina,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201257,Disorder of endocrine ovary,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201346,Edema of penis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201355,Erosion and ectropion of the cervix,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201527,Neoplasm of uncertain behavior of prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201617,Prostatic cyst,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201625,Malposition of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201801,Primary malignant neoplasm of fallopian tube,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201817,Benign neoplasm of female genital organ,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201823,Benign neoplasm of penis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201907,Edema of male genital organs,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201909,Female infertility,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,201913,"Torsion of the ovary, ovarian pedicle or fallopian tube",,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,314409,Vascular disorder of penis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,315586,Priapism,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,433716,Primary malignant neoplasm of testis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,434251,Injury of male external genital organs,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,435315,Torsion of testis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,435648,Retractile testis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,436155,Redundant prepuce and phimosis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,436358,Primary malignant neoplasm of exocervix,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,436366,Benign neoplasm of testis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,436466,Balanoposthitis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,437501,Primary malignant neoplasm of labia majora,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,437655,Undescended testicle,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,438477,Atrophy of testis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,439871,Hemospermia,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,440971,Neoplasm of uncertain behavior of testis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,441068,Torsion of appendix of testis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,441077,Stenosis of cervix,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,441805,Primary malignant neoplasm of endocervix,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,442781,Disorder of uterine cervix,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,443211,Benign prostatic hypertrophy with outflow obstruction,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,443435,Primary uterine inertia,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,443800,Amenorrhea,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,444078,Inflammation of cervix,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,444106,Candidiasis of vulva,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2003947,Closed [percutaneous] [needle] biopsy of prostate,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2003966,Other transurethral prostatectomy,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2003983,Other prostatectomy,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2004031,Other repair of scrotum and tunica vaginalis,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2004063,Unilateral orchiectomy,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2004070,Other repair of testis,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2004090,Excision of varicocele and hydrocele of spermatic cord,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2004164,Local excision or destruction of lesion of penis,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2004263,Other removal of both ovaries and tubes at same operative episode,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2004329,Other bilateral destruction or occlusion of fallopian tubes,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2004342,Removal of both fallopian tubes at same operative episode,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2004443,Closed biopsy of uterus,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2004627,Vaginal suspension and fixation,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2109825,"Transurethral electrosurgical resection of prostate, including control of postoperative bleeding, complete (vasectomy, meatotomy, cystourethroscopy, urethral calibration and/or dilation, and internal urethrotomy are included)",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2109833,"Laser vaporization of prostate, including control of postoperative bleeding, complete (vasectomy, meatotomy, cystourethroscopy, urethral calibration and/or dilation, internal urethrotomy and transurethral resection of prostate are included if performed)",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2109900,"Destruction of lesion(s), penis (eg, condyloma, papilloma, molluscum contagiosum, herpetic vesicle), simple; chemical",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2109902,"Destruction of lesion(s), penis (eg, condyloma, papilloma, molluscum contagiosum, herpetic vesicle), simple; cryosurgery",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2109905,"Destruction of lesion(s), penis (eg, condyloma, papilloma, molluscum contagiosum, herpetic vesicle), extensive (eg, laser surgery, electrosurgery, cryosurgery, chemosurgery)",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2109906,Biopsy of penis, (separate procedure),,,,,Male,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2109916,"Circumcision, using clamp or other device with regional dorsal penile or ring block",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2109968,Foreskin manipulation including lysis of preputial adhesions and stretching,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2109973,"Orchiectomy, simple (including subcapsular), with or without testicular prosthesis, scrotal or inguinal approach",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2109981,"Orchiopexy, inguinal approach, with or without hernia repair",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110004,Drainage of scrotal wall abscess,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110011,"Vasectomy, unilateral or bilateral (separate procedure), including postoperative semen examination(s)",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110026,"Biopsy, prostate; needle or punch, single or multiple, any approach",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110039,"Prostatectomy, retropubic radical, with or without nerve sparing; with bilateral pelvic lymphadenectomy, including external iliac, hypogastric, and obturator nodes",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110044,"Laparoscopy, surgical prostatectomy, retropubic radical, including nerve sparing, includes robotic assistance, when performed",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110078,Colposcopy of the vulva,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110116,"Colpopexy, vaginal; extra-peritoneal approach (sacrospinous, iliococcygeus)",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110142,"Laparoscopy, surgical, colpopexy (suspension of vaginal apex)",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110144,Colposcopy of the cervix including upper/adjacent vagina, with biopsy(s) of the cervix and endocervical curettage,,,,,Female,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110169,"Endometrial sampling (biopsy) with or without endocervical sampling (biopsy), without cervical dilation, any method (separate procedure)",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110175,"Total abdominal hysterectomy (corpus and cervix), with or without removal of tube(s), with or without removal of ovary(s)",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110194,Insertion of intrauterine device (IUD),,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110195,Removal of intrauterine device (IUD),,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110203,"Endometrial ablation, thermal, without hysteroscopic guidance",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110222,"Hysteroscopy, surgical; with sampling (biopsy) of endometrium and/or polypectomy, with or without D & C",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110227,"Hysteroscopy, surgical; with endometrial ablation (eg, endometrial resection, electrosurgical ablation, thermoablation)",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110230,"Laparoscopy, surgical, with total hysterectomy, for uterus 250 g or less; with removal of tube(s) and/or ovary(s)",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110307,"Routine obstetric care including antepartum care, vaginal delivery (with or without episiotomy, and/or forceps) and postpartum care",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110315,"Routine obstetric care including antepartum care, cesarean delivery, and postpartum care",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110316,Cesarean delivery only,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110317,Cesarean delivery only, including postpartum care,,,,,Female,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2110326,"Treatment of missed abortion, completed surgically; first trimester",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2211747,"Ultrasound, pregnant uterus, real time with image documentation, fetal and maternal evaluation, first trimester (< 14 weeks 0 days), transabdominal approach; single or first gestation",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2211749,"Ultrasound, pregnant uterus, real time with image documentation, fetal and maternal evaluation, after first trimester (> or = 14 weeks 0 days), transabdominal approach; single or first gestation",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2211751,"Ultrasound, pregnant uterus, real time with image documentation, fetal and maternal evaluation plus detailed fetal anatomic examination, transabdominal approach; single or first gestation",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2211753,"Ultrasound, pregnant uterus, real time with image documentation, first trimester fetal nuchal translucency measurement, transabdominal or transvaginal approach; single or first gestation",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2211755,"Ultrasound, pregnant uterus, real time with image documentation, limited (eg, fetal heart beat, placental location, fetal position and/or qualitative amniotic fluid volume), 1 or more fetuses",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2211756,"Ultrasound, pregnant uterus, real time with image documentation, follow-up (eg, re-evaluation of fetal size by measuring standard growth parameters and amniotic fluid volume, re-evaluation of organ system(s) suspected or confirmed to be abnormal on a prev",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2211757,"Ultrasound, pregnant uterus, real time with image documentation, transvaginal",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2211765,"Ultrasound, transvaginal",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2211769,"Ultrasound, scrotum and contents",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2617204,Cervical or vaginal cancer screening, pelvic and clinical breast examination,,,,,Female,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2721063,"Annual gynecological examination, new patient",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2721064,"Annual gynecological examination, established patient",,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2780478,"Resection of Prostate, Percutaneous Endoscopic Approach",,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,2780523,"Resection of Prepuce, External Approach",,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4005743,Female sterility,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4005933,"Hypospadias, penile",,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4012343,Vaginal discharge symptom,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4016155,Prostatism,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4021531,Total abdominal hysterectomy,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4032594,Inflammation of scrotum,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4032622,Laparoscopic supracervical hysterectomy,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4038747,Obstetric examination,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4048225,Neoplasm of endometrium,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4050091,Open wound of penis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4051956,Vulvovaginal disease,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4052532,Hysteroscopy,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4054550,Open wound of scrotum and testes,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4056903,Vaginitis associated with another disorder,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4058792,Douche of vagina,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4060207,Vulval irritation,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4060556,"Uterine scar from previous surgery in pregnancy, childbirth and the puerperium",,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4060558,"Uterine scar from previous surgery in pregnancy, childbirth and the puerperium - delivered",,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4060559,"Uterine scar from previous surgery in pregnancy, childbirth and the puerperium with antenatal problem",,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4061050,Subacute and chronic vaginitis,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4071874,Pain in scrotum,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4073700,Transurethral laser prostatectomy,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4081648,Acute vaginitis,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4083772,Echography of scrotum and contents,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4090039,Penile arterial insufficiency,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4092515,"Malignant neoplasm, overlapping lesion of cervix uteri",,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4093346,Large prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4095940,Finding of pattern of menstrual cycle,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4096783,Radical prostatectomy,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4109081,Pain in penis,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4127886,Hysterectomy,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4128329,Menopause present,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4129155,Vaginal bleeding,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4138738,Vaginal hysterectomy,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4140828,Acute vulvitis,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4141940,Endometrial ablation,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4143116,Azoospermia,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4146777,Radical abdominal hysterectomy,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4147021,"Contusion, scrotum or testis",,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4149084,Vaginitis,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4150042,Vaginal ulcer,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4150816,Bicornuate uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4155529,Mechanical complication of intrauterine contraceptive device,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4156113,Malignant neoplasm of body of uterus,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4161944,Low cervical cesarean section,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4162860,Primary malignant neoplasm of body of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4163261,Malignant tumor of prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4171394,Abnormal menstrual cycle,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4171915,Orchitis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4180978,Vulvovaginitis,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4181912,Cone biopsy of cervix,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4194652,Pruritus of vulva,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4199600,Candidal balanitis,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4234536,Transurethral prostatectomy,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4235215,Swelling of testicle,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4238715,Removal of intrauterine device,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4243919,Incision of ovary,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4260520,Balanitis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4270932,Pain in testicle,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4275113,Insertion of intrauterine contraceptive device,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4279913,Primary ovarian failure,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4281030,Secondary malignant neoplasm of right ovary,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4294393,Ulcer of penis,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4294805,Laparoscopic-assisted vaginal hysterectomy,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4295261,Postmenopausal state,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4303258,Bacterial vaginosis,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4306780,Gynecologic examination,,,,,Female,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4310552,Orchidopexy,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4320332,Hydrocele of tunica vaginalis,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4321575,Lysis of penile adhesions,,,,,Male,,, +PROCEDURE_OCCURRENCE,PROCEDURE_CONCEPT_ID,4330583,Vasectomy,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,4339088,Testicular mass,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,40481080,Benign localized hyperplasia of prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,40482030,Dysplasia of prostate,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,40482406,Low lying placenta,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,40483613,Inflammatory disease of female genital structure,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,40490888,Herniation of rectum into vagina,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,42709954,Phimosis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,45757415,Benign endometrial hyperplasia,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,45766654,Disorder of skin of penis,,,,,Male,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,45770892,Primary malignant neoplasm of uterus,,,,,Female,,, +CONDITION_OCCURRENCE,CONDITION_CONCEPT_ID,45772671,Nodular prostate without urinary obstruction,,,,,Male,,, +CONDITION,CONDITION_CONCEPT_ID,4006969,Acute respiratory disease,,,,,,Yes,0.1703,1 +CONDITION,CONDITION_CONCEPT_ID,4134440,Visual system disorder,,,,,,Yes,0.1181,1 +CONDITION,CONDITION_CONCEPT_ID,316866,Hypertensive disorder,,,,,,Yes,0.0913,0.8215 +CONDITION,CONDITION_CONCEPT_ID,432867,Hyperlipidemia,,,,,,Yes,0.0712,0.6412 +CONDITION,CONDITION_CONCEPT_ID,321588,Heart disease,,,,,,Yes,0.061,0.5491 +CONDITION,CONDITION_CONCEPT_ID,80180,Osteoarthritis,,,,,,Yes,0.0584,0.5252 +CONDITION,CONDITION_CONCEPT_ID,321052,Peripheral vascular disease,,,,,,Yes,0.0426,0.3832 +CONDITION,CONDITION_CONCEPT_ID,81902,Urinary tract infectious disease,,,,,,Yes,0.0412,0.371 +CONDITION,CONDITION_CONCEPT_ID,440383,Depressive disorder,,,,,,Yes,0.0392,0.3531 +CONDITION,CONDITION_CONCEPT_ID,201820,Diabetes mellitus,,,,,,Yes,0.039,0.3514 +CONDITION,CONDITION_CONCEPT_ID,433736,Obesity,,,,,,Yes,0.038,0.3422 +CONDITION,CONDITION_CONCEPT_ID,318800,Gastroesophageal reflux disease,,,,,,Yes,0.0337,0.3033 +CONDITION,CONDITION_CONCEPT_ID,443392,Malignant neoplastic disease,,,,,,Yes,0.0326,0.2932 +CONDITION,CONDITION_CONCEPT_ID,255848,Pneumonia,,,,,,Yes,0.0218,0.1966 +CONDITION,CONDITION_CONCEPT_ID,317576,Coronary arteriosclerosis,,,,,,Yes,0.0206,0.1852 +CONDITION,CONDITION_CONCEPT_ID,4185932,Ischemic heart disease,,,,,,Yes,0.0201,0.1813 +CONDITION,CONDITION_CONCEPT_ID,255573,Chronic obstructive lung disease,,,,,,Yes,0.0194,0.1742 +CONDITION,CONDITION_CONCEPT_ID,4030518,Renal impairment,,,,,,Yes,0.0174,0.1568 +CONDITION,CONDITION_CONCEPT_ID,316139,Heart failure,,,,,,Yes,0.0161,0.1452 +CONDITION,CONDITION_CONCEPT_ID,381591,Cerebrovascular disease,,,,,,Yes,0.0142,0.1274 +CONDITION,CONDITION_CONCEPT_ID,192671,Gastrointestinal hemorrhage,,,,,,Yes,0.0135,0.1219 +CONDITION,CONDITION_CONCEPT_ID,313217,Atrial fibrillation,,,,,,Yes,0.0128,0.1155 +CONDITION,CONDITION_CONCEPT_ID,4182210,Dementia,,,,,,Yes,0.0086,0.0773 +CONDITION,CONDITION_CONCEPT_ID,444247,Venous thrombosis,,,,,,Yes,0.0082,0.0737 +CONDITION,CONDITION_CONCEPT_ID,438409,Attention deficit hyperactivity disorder,,,,,,Yes,0.0078,0.0706 +CONDITION,CONDITION_CONCEPT_ID,4279309,Substance abuse,,,,,,Yes,0.0063,0.0568 +CONDITION,CONDITION_CONCEPT_ID,140168,Psoriasis,,,,,,Yes,0.0055,0.0494 +CONDITION,CONDITION_CONCEPT_ID,4212540,Chronic liver disease,,,,,,Yes,0.0053,0.0476 +CONDITION,CONDITION_CONCEPT_ID,200962,Primary malignant neoplasm of prostate,,,,,,Yes,0.0052,0.0471 +CONDITION,CONDITION_CONCEPT_ID,4112853,Malignant tumor of breast,,,,,,Yes,0.0047,0.0421 +CONDITION,CONDITION_CONCEPT_ID,80809,Rheumatoid arthritis,,,,,,Yes,0.0045,0.0405 +CONDITION,CONDITION_CONCEPT_ID,4044013,Hematologic neoplasm,,,,,,Yes,0.0037,0.0331 +CONDITION,CONDITION_CONCEPT_ID,4104000,Lesion of liver,,,,,,Yes,0.0029,0.0265 +CONDITION,CONDITION_CONCEPT_ID,440417,Pulmonary embolism,,,,,,Yes,0.0024,0.022 +CONDITION,CONDITION_CONCEPT_ID,435783,Schizophrenia,,,,,,Yes,0.0021,0.0186 +CONDITION,CONDITION_CONCEPT_ID,443388,Malignant tumor of lung,,,,,,Yes,0.0021,0.0185 +CONDITION,CONDITION_CONCEPT_ID,4180790,Malignant tumor of colon,,,,,,Yes,0.0019,0.0173 +CONDITION,CONDITION_CONCEPT_ID,197494,Viral hepatitis C,,,,,,Yes,0.0017,0.0155 +CONDITION,CONDITION_CONCEPT_ID,432571,Malignant lymphoma,,,,,,Yes,0.0016,0.0143 +CONDITION,CONDITION_CONCEPT_ID,81893,Ulcerative colitis,,,,,,Yes,0.0014,0.0128 +CONDITION,CONDITION_CONCEPT_ID,197508,Malignant tumor of urinary bladder,,,,,,Yes,0.0013,0.0113 +CONDITION,CONDITION_CONCEPT_ID,201606,Crohn's disease,,,,,,Yes,0.0012,0.0112 +CONDITION,CONDITION_CONCEPT_ID,40481902,Malignant neoplasm of anorectum,,,,,,Yes,0.001,0.0089 +CONDITION,CONDITION_CONCEPT_ID,439727,Human immunodeficiency virus infection,,,,,,Yes,0.0006,0.0057 +CONDITION,CONDITION_CONCEPT_ID,9201,Inpatient visit,,,,,,Yes,, +CONDITION,CONDITION_CONCEPT_ID,9202,Outpatient visit,,,,,,Yes,, +CONDITION,CONDITION_CONCEPT_ID,9203,ER visit,,,,,,Yes,, diff --git a/docs/inst/csv/OMOP_CDMv5.3.1_Field_Level.csv b/docs/inst/csv/OMOP_CDMv5.3.1_Field_Level.csv new file mode 100644 index 0000000..796cc34 --- /dev/null +++ b/docs/inst/csv/OMOP_CDMv5.3.1_Field_Level.csv @@ -0,0 +1,334 @@ +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 +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, +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, +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, +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, +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, +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, +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, +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, +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, +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, +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, +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, +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, +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, +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, +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, +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, +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, +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, +OBSERVATION_PERIOD,person_id,Yes,0,integer,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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 +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 +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, +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, +VISIT_OCCURRENCE,person_id,Yes,0,integer,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +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 +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 +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 +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 +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, +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, +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, +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, +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, +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, +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, +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, +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, +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, +CONDITION_OCCURRENCE,condition_occurrence_id,Yes,0,bigint,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +CONDITION_OCCURRENCE,person_id,Yes,0,bigint,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +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 +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 +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 +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 +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, +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, +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, +CONDITION_OCCURRENCE,provider_id,No,,integer,0,,,No,,Yes,0,PROVIDER,PROVIDER_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +CONDITION_OCCURRENCE,visit_occurrence_id,No,,integer,0,,,No,,Yes,0,VISIT_OCCURRENCE,VISIT_OCCURRENCE_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +CONDITION_OCCURRENCE,visit_detail_id,No,,integer,0,,,No,,Yes,0,VISIT_DETAIL,VISIT_DETAIL_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +CONDITION_OCCURRENCE,condition_source_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,Yes,0,No,,,,,,,,,,No, +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, +DRUG_EXPOSURE,drug_exposure_id,Yes,0,bigint,0,,,Yes,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +DRUG_EXPOSURE,person_id,Yes,0,bigint,0,,,No,,Yes,,PERSON,PERSON_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +DRUG_EXPOSURE,drug_concept_id,Yes,0,integer,0,,,No,,Yes,,CONCEPT,CONCEPT_ID,Drug,,,,Yes,,Yes,100,Yes,0,No,,No,,,,,,,,,,No, +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 +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 +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 +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 +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 +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, +DRUG_EXPOSURE,stop_reason,No,,varchar(20),0,," Reasons include regimen completed, changed, removed, etc.",No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +DRUG_EXPOSURE,quantity,No,,float,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,0,,1095,,,,,No, +DRUG_EXPOSURE,days_supply,No,,integer,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,0,,365,,,,,No, +DRUG_EXPOSURE,sig,No,,varchar(MAX),0,(and printed on the container),,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +DRUG_EXPOSURE,lot_number,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +DRUG_EXPOSURE,provider_id,No,,integer,0,,,No,,Yes,,PROVIDER,PROVIDER_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +DRUG_EXPOSURE,visit_occurrence_id,No,,integer,0,,,No,,Yes,,VISIT_OCCURRENCE,VISIT_OCCURRENCE_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +DRUG_EXPOSURE,visit_detail_id,No,,integer,0,,,No,,Yes,,VISIT_DETAIL,VISIT_DETAIL_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +DRUG_EXPOSURE,drug_source_concept_id,No,,integer,0,,,No,,Yes,,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,Yes,,No,,,,,,,,,,No, +DRUG_EXPOSURE,route_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,,ROUTE_CONCEPT_ID,,,,,,,,No, +DRUG_EXPOSURE,dose_unit_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PROCEDURE_OCCURRENCE,procedure_occurrence_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PROCEDURE_OCCURRENCE,person_id,Yes,0,integer,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +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 +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 +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, +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, +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, +PROCEDURE_OCCURRENCE,provider_id,No,,integer,0,,,No,,No,,PROVIDER,PROVIDER_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PROCEDURE_OCCURRENCE,visit_occurrence_id,No,,integer,0,,,No,,No,,VISIT_OCCURRENCE,VISIT_OCCURRENCE_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PROCEDURE_OCCURRENCE,visit_detail_id,No,,integer,0,,,No,,No,,VISIT_DETAIL,VISIT_DETAIL_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +PROCEDURE_OCCURRENCE,procedure_source_concept_id,No,,integer,0,,,No,,No,,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,Yes,0,No,,,,,,,,,,No, +PROCEDURE_OCCURRENCE,modifier_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,MODIFIER_CONCEPT_ID,,,,,,,,No, +DEVICE_EXPOSURE,device_exposure_id,Yes,0,bigint,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +DEVICE_EXPOSURE,person_id,Yes,0,bigint,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +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 +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 +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 +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 +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, +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, +DEVICE_EXPOSURE,quantity,No,,integer,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,1,0,,,,,,No, +DEVICE_EXPOSURE,provider_id,No,,integer,0,,,No,,Yes,0,PROVIDER,PROVIDER_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +DEVICE_EXPOSURE,visit_occurrence_id,No,,integer,0,,,No,,Yes,0,VISIT_OCCURRENCE,VISIT_OCCURRENCE_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +DEVICE_EXPOSURE,visit_detail_id,No,,integer,0,,,No,,Yes,0,VISIT_DETAIL,VISIT_DETAIL_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +DEVICE_EXPOSURE,device_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,DEVICE_CONCEPT_ID,,,,,,,,No, +DEVICE_EXPOSURE,device_source_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,Yes,0,No,,,,,,,,,,No, +MEASUREMENT,measurement_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +MEASUREMENT,person_id,Yes,0,integer,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +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, +MEASUREMENT,measurement_datetime,No,,datetime,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +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, +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, +MEASUREMENT,value_as_number,No,,float,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +MEASUREMENT,value_as_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +MEASUREMENT,unit_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,Unit,0,,,Yes,0,Yes,100,Yes,0,No,,No,,,,,,,,,,No, +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, +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, +MEASUREMENT,provider_id,No,,integer,0,,,No,,Yes,0,PROVIDER,PROVIDER_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +MEASUREMENT,visit_occurrence_id,No,,integer,0,,,No,,Yes,0,VISIT_OCCURRENCE,VISIT_OCCURRENCE_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +MEASUREMENT,visit_detail_id,No,,integer,0,,,No,,Yes,0,VISIT_DETAIL,VISIT_DETAIL_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +MEASUREMENT,measurement_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,MEASUREMENT_CONCEPT_ID,,,,,,,,No, +MEASUREMENT,measurement_source_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,Yes,0,No,,,,,,,,,,No, +MEASUREMENT,unit_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,UNIT_CONCEPT_ID,,,,,,,,No, +MEASUREMENT,value_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +VISIT_DETAIL,visit_detail_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +VISIT_DETAIL,person_id,Yes,0,integer,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +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 +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 +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 +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 +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, +VISIT_DETAIL,provider_id,No,,integer,0,,,No,,Yes,0,PROVIDER,PROVIDER_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +VISIT_DETAIL,care_site_id,No,,integer,0,,,No,,Yes,0,CARE_SITE,CARE_SITE_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +VISIT_DETAIL,visit_detail_source_value,No,,string(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,VISIT_DETAIL_CONCEPT_ID,,,,,,,,No, +VISIT_DETAIL,visit_detail_source_concept_id,No,,Integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,Yes,0,No,,,,,,,,,,No, +VISIT_DETAIL,admitting_source_value,No,,Varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,ADMITTING_SOURCE_CONCEPT_ID,,,,,,,,No, +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, +VISIT_DETAIL,discharge_to_source_value,No,,Varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,DISCHARGE_TO_CONCEPT_ID,,,,,,,,No, +VISIT_DETAIL,discharge_to_concept_id,No,,Integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,Yes,0,No,,No,,,,,,,,,,No, +VISIT_DETAIL,preceding_visit_detail_id,No,,Integer,0,,,No,,Yes,0,VISIT_DETAIL,VISIT_DETAIL_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +VISIT_DETAIL,visit_detail_parent_id,No,,Integer,0,,,No,,Yes,0,VISIT_DETAIL,VISIT_DETAIL_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +VISIT_DETAIL,visit_occurrence_id,Yes,0,Integer,0,,,No,,Yes,0,VISIT_OCCURRENCE,VISIT_OCCURRENCE_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE,note_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE,person_id,Yes,0,integer,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +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, +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, +NOTE,note_class_concept_id,Yes,0,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE,note_title,No,,varchar(250),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE,note_text,Yes,0,varchar(MAX),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE,encoding_concept_id,Yes,0,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE,language_concept_id,Yes,0,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE,provider_id,No,,integer,0,,,No,,Yes,0,PROVIDER,PROVIDER_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE,visit_occurrence_id,No,,integer,0,,,No,,Yes,0,VISIT_OCCURRENCE,VISIT_OCCURRENCE_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE,visit_detail_id,No,,integer,0,,,No,,Yes,0,VISIT_DETAIL,VISIT_DETAIL_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE,note_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE_NLP,note_nlp_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE_NLP,note_id,Yes,0,integer,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE_NLP,section_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE_NLP,snippet,No,,varchar(250),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE_NLP,offset,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE_NLP,lexical_variant,Yes,0,varchar(250),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE_NLP,note_nlp_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE_NLP,note_nlp_source_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE_NLP,nlp_system,No,,varchar(250),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +NOTE_NLP,nlp_date,Yes,0,date,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +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, +NOTE_NLP,term_temporal,No,,varchar(50),0,,"Term_temporal is to indicate if a condition is �present� or just in the �past�. 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, +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, +OBSERVATION,observation_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +OBSERVATION,person_id,Yes,0,integer,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +OBSERVATION,observation_concept_id,Yes,0,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,Yes,0,No,,No,,,,,,,,,,No, +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, +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, +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, +OBSERVATION,value_as_number,No,,float,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +OBSERVATION,value_as_string,No,,varchar(60),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +OBSERVATION,qualifier_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,No,,No,,No,,,,,,,,,,No, +OBSERVATION,unit_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,Unit,0,,,Yes,0,Yes,100,Yes,0,No,,No,,,,,,,,,,No, +OBSERVATION,provider_id,No,,integer,0,,,No,,Yes,0,PROVIDER,PROVIDER_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +OBSERVATION,visit_occurrence_id,No,,integer,0,,,No,,Yes,0,VISIT_OCCURRENCE,VISIT_OCCURRENCE_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +OBSERVATION,visit_detail_id,No,,integer,0,,,No,,Yes,0,VISIT_DETAIL,VISIT_DETAIL_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +OBSERVATION,observation_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,OBSERVATION_CONCEPT_ID,,,,,,,,No, +OBSERVATION,observation_source_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,Yes,0,No,,,,,,,,,,No, +OBSERVATION,unit_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,UNIT_CONCEPT_ID,,,,,,,,No, +OBSERVATION,qualifier_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,QUALIFIER_CONCEPT_ID,,,,,,,,No, +SPECIMEN,specimen_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +SPECIMEN,person_id,Yes,0,integer,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +SPECIMEN,specimen_concept_id,Yes,0,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,Yes,0,No,,No,,,,,,,,,,No, +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, +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, +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, +SPECIMEN,quantity,No,,float,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,1,0,,,,,,No, +SPECIMEN,unit_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,Yes,0,No,,No,,,,,,,,,,No, +SPECIMEN,anatomic_site_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,No,,No,,No,,,,,,,,,,No, +SPECIMEN,disease_status_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,No,,No,,No,,,,,,,,,,No, +SPECIMEN,specimen_source_id,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +SPECIMEN,specimen_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,SPECIMEN_CONCEPT_ID,,,,,,,,No, +SPECIMEN,unit_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,UNIT_CONCEPT_ID,,,,,,,,No, +SPECIMEN,anatomic_site_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,ANATOMIC_SITE_CONCEPT_ID,,,,,,,,No, +SPECIMEN,disease_status_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,DISEASE_STATUS_CONCEPT_ID,,,,,,,,No, +FACT_RELATIONSHIP,domain_concept_id_1,Yes,0,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,Yes,0,No,,No,,,,,,,,,,No, +FACT_RELATIONSHIP,fact_id_1,Yes,0,integer,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +FACT_RELATIONSHIP,domain_concept_id_2,Yes,0,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,Yes,0,No,,No,,,,,,,,,,No, +FACT_RELATIONSHIP,fact_id_2,Yes,0,integer,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +FACT_RELATIONSHIP,relationship_concept_id,Yes,0,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,Yes,0,No,,No,,,,,,,,,,No, +LOCATION,location_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +LOCATION,address_1,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +LOCATION,address_2,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +LOCATION,city,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +LOCATION,state,No,,varchar(2),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +LOCATION,county,No,,varchar(20),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +LOCATION,location_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +CARE_SITE,care_site_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +CARE_SITE,care_site_name,No,,varchar(255),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +CARE_SITE,location_id,No,,integer,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +CARE_SITE,care_site_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +CARE_SITE,place_of_service_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PROVIDER,provider_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PROVIDER,provider_name,No,,varchar(255),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PROVIDER,npi,No,,varchar(20),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PROVIDER,dea,No,,varchar(20),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +PROVIDER,care_site_id,No,,integer,0,,,No,,Yes,0,CARE_SITE,CARE_SITE_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PROVIDER,year_of_birth,No,,integer,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PROVIDER,gender_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,Gender,0,,,Yes,0,Yes,100,Yes,0,No,,No,,,,,,,,,,No, +PROVIDER,provider_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PROVIDER,specialty_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,SPECIALTY_CONCEPT_ID,,,,,,,,No, +PROVIDER,specialty_source_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,Yes,0,No,,,,,,,,,,No, +PROVIDER,gender_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,GENDER_CONCEPT_ID,,,,,,,,No, +PROVIDER,gender_source_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +PAYER_PLAN_PERIOD,person_id,Yes,0,integer,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PAYER_PLAN_PERIOD,payer_plan_period_start_date,Yes,0,date,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +PAYER_PLAN_PERIOD,payer_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PAYER_PLAN_PERIOD,payer_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,PAYER_CONCEPT_ID,,,,,,,,No, +PAYER_PLAN_PERIOD,payer_source_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PAYER_PLAN_PERIOD,plan_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PAYER_PLAN_PERIOD,plan_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,PLAN_CONCEPT_ID,,,,,,,,No, +PAYER_PLAN_PERIOD,plan_source_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PAYER_PLAN_PERIOD,sponsor_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PAYER_PLAN_PERIOD,sponsor_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,Yes,0,SPONSOR_CONCEPT_ID,,,,,,,,No, +PAYER_PLAN_PERIOD,sponsor_source_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +PAYER_PLAN_PERIOD,family_source_value,No,,varchar(50),0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,0,,,,,,,,,No, +PAYER_PLAN_PERIOD,stop_reason_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +PAYER_PLAN_PERIOD,stop_reason_source_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,cost_id,Yes,0,INTEGER,0,,,Yes,0,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,cost_event_id,Yes,0,INTEGER,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,cost_domain_id,Yes,0,VARCHAR(20),0,,,No,,Yes,0,DOMAIN,DOMAIN_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,cost_type_concept_id,Yes,0,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,Yes,0,Yes,100,Yes,0,No,,No,,,,,,,,,,No, +COST,currency_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,total_charge,No,,FLOAT,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,total_cost,No,,FLOAT,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,total_paid,No,,FLOAT,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,paid_by_payer,No,,FLOAT,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,paid_by_patient,No,,FLOAT,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,paid_patient_copay,No,,FLOAT,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,paid_patient_coinsurance,No,,FLOAT,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,paid_patient_deductible,No,,FLOAT,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,paid_by_primary,No,,FLOAT,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,paid_ingredient_cost,No,,FLOAT,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,paid_dispensing_fee,No,,FLOAT,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,payer_plan_period_id,No,,INTEGER,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,amount_allowed,No,,FLOAT,0,,,No,,No,,,,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +COST,revenue_code_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +COST,drg_concept_id,No,,integer,0,,,No,,Yes,0,CONCEPT,CONCEPT_ID,,,,,No,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +DRUG_ERA,drug_era_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,,,Yes,100,No,,No,,No,,,,,,,,,,No, +DRUG_ERA,person_id,Yes,0,integer,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +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 +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, +DRUG_ERA,drug_exposure_count,No,,integer,0,,,No,,No,,,,,,,,,,Yes,100,No,,No,,No,,,1,0,,,,,,No, +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, +DOSE_ERA,dose_era_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,,,Yes,100,No,,No,,No,,,,,,,,,,No, +DOSE_ERA,person_id,Yes,0,integer,0,,,No,,Yes,0,PERSON,PERSON_ID,,,,,,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +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, +DOSE_ERA,dose_value,Yes,0,float,0,,,No,,No,,,,,,,,,,Yes,100,No,,No,,No,,,0,0,,,,,,No, +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 +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, +CONDITION_ERA,condition_era_id,Yes,0,integer,0,,,Yes,0,No,,,,,,,,,,Yes,100,No,,No,,No,,,,,,,,,,No, +CONDITION_ERA,person_id,Yes,0,integer,0,,,No,,No,,PERSON,PERSON_ID,,,,,,,Yes,100,No,,No,,No,,,,,,,,,,No, +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, +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 +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, +CONDITION_ERA,condition_occurrence_count,No,,integer,0,,,No,,No,,,,,,,,,,Yes,100,No,,No,,No,,,1,0,,,,,,No, diff --git a/docs/inst/csv/OMOP_CDMv5.3.1_Table_Level.csv b/docs/inst/csv/OMOP_CDMv5.3.1_Table_Level.csv new file mode 100644 index 0000000..b3f58c9 --- /dev/null +++ b/docs/inst/csv/OMOP_CDMv5.3.1_Table_Level.csv @@ -0,0 +1,23 @@ +cdmTableName,schema,isRequired,conceptPrefix,measurePersonCompleteness,measurePersonCompletenessThreshold,validation,tableDescription,userGuidance,etlConventions +PERSON,CDM,Yes,,No,,,,, +OBSERVATION_PERIOD,CDM,Yes,,Yes,0,,,, +VISIT_OCCURRENCE,CDM,No,VISIT_,Yes,0,,,, +CONDITION_OCCURRENCE,CDM,No,CONDITION_,Yes,0,,,, +DRUG_EXPOSURE,CDM,No,DRUG_,Yes,0,,,, +PROCEDURE_OCCURRENCE,CDM,No,PROCEDURE_,Yes,0,,,, +DEVICE_EXPOSURE,CDM,No,DEVICE_,Yes,0,,,, +MEASUREMENT,CDM,No,MEASUREMENT_,Yes,0,,,, +VISIT_DETAIL,CDM,No,VISIT_DETAIL_,Yes,0,,,, +NOTE,CDM,No,,Yes,0,,,, +NOTE_NLP,CDM,No,,No,,,,, +OBSERVATION,CDM,No,OBSERVATION_,Yes,0,,,, +SPECIMEN,CDM,No,SPECIMEN_,Yes,0,,,, +FACT_RELATIONSHIP,CDM,No,,No,,,,, +LOCATION,CDM,No,,No,,,,, +CARE_SITE,CDM,No,,No,,,,, +PROVIDER,CDM,No,,No,,,,, +PAYER_PLAN_PERIOD,CDM,No,,Yes,0,,,, +COST,CDM,No,,No,,,,, +DRUG_ERA,CDM,No,,Yes,0,,,, +DOSE_ERA,CDM,No,,Yes,0,,,, +CONDITION_ERA,CDM,No,,Yes,0,,,, diff --git a/docs/inst/sql/sql_server/OMOP CDM ddl v5_3_1 2019-08-28.sql b/docs/inst/sql/sql_server/OMOP CDM ddl v5_3_1 2019-08-28.sql new file mode 100644 index 0000000..50baabd Binary files /dev/null and b/docs/inst/sql/sql_server/OMOP CDM ddl v5_3_1 2019-08-28.sql differ diff --git a/docs/inst/sql/sql_server/OMOP CDM ddl v5_3_1 2019-08-29.txt b/docs/inst/sql/sql_server/OMOP CDM ddl v5_3_1 2019-08-29.txt new file mode 100644 index 0000000..50baabd Binary files /dev/null and b/docs/inst/sql/sql_server/OMOP CDM ddl v5_3_1 2019-08-29.txt differ diff --git a/docs/man/createDdlFromFile.Rd b/docs/man/createDdlFromFile.Rd new file mode 100644 index 0000000..9afbb9a --- /dev/null +++ b/docs/man/createDdlFromFile.Rd @@ -0,0 +1,22 @@ +% Generated by roxygen2: do not edit by hand +% Please edit documentation in R/createDdlFromFile.R +\name{createDdlFromFile} +\alias{createDdlFromFile} +\title{Create a DDL script from a two csv files that detail the OMOP CDM Specifications. These files also form the basis of the CDM documentation and the Data Quality +Dashboard.} +\usage{ + + createDdlFromFile(cdmTableCsvLoc = "inst/csv/OMOP_CDMv5.3.1_Table_Level.csv", + cdmFieldCsvLoc = "inst/csv/OMOP_CDMv5.3.1_Field_Level.csv") +} +\arguments{ +\item{cdmTableCsvLoc}{The location of the csv file with the high-level CDM table information. This is defaulted to "inst/csv/OMOP_CDMv5.3.1_Table_Level.csv". +If a new version of this file was committed to the CDM repository the package automatically will grab it and place it in "inst/csv/".} + +\item{cdmVersion}{The location of the csv file with the CDM field information. This is defaulted to "inst/csv/OMOP_CDMv5.3.1_Field_Level.csv". +If a new version of this file was committed to the CDM repository the package automatically will grab it and place it in "inst/csv/".} +} +\description{ +Create a DDL script from a two csv files that detail the OMOP CDM Specifications. These files also form the basis of the CDM documentation and the Data Quality +Dashboard. +} diff --git a/docs/output/OMOP_CDM_v6_0.csv b/docs/output/OMOP_CDM_v6_0.csv deleted file mode 100644 index 5b1cd27..0000000 --- a/docs/output/OMOP_CDM_v6_0.csv +++ /dev/null @@ -1,428 +0,0 @@ -"field","required","type","description","table" -"cohort_definition_id","Yes","INTEGER","A foreign key to a record in the COHORT_DEFINITION table containing relevant Cohort Definition information.","cohort" -"subject_id","Yes","INTEGER","A foreign key to the subject in the cohort. These could be referring to records in the PERSON, PROVIDER, VISIT_OCCURRENCE table.","cohort" -"cohort_start_date","Yes","DATE","The date when the Cohort Definition criteria for the Person, Provider or Visit first match.","cohort" -"cohort_end_date","Yes","DATE","The date when the Cohort Definition criteria for the Person, Provider or Visit no longer match or the Cohort membership was terminated.","cohort" -"cohort_definition_id","Yes","INTEGER","A unique identifier for each Cohort.","cohort_definition" -"cohort_definition_name","Yes","VARCHAR(255)","A short description of the Cohort.","cohort_definition" -"cohort_definition_description","No","VARCHAR(MAX)","A complete description of the Cohort definition","cohort_definition" -"definition_type_concept_id","Yes","INTEGER","Type defining what kind of Cohort Definition the record represents and how the syntax may be executed","cohort_definition" -"cohort_definition_syntax","No","VARCHAR(MAX)","Syntax or code to operationalize the Cohort definition","cohort_definition" -"subject_concept_id","Yes","INTEGER","A foreign key to the Concept to which defines the domain of subjects that are members of the cohort (e.g., Person, Provider, Visit).","cohort_definition" -"cohort_initiation_date","No","DATE","A date to indicate when the Cohort was initiated in the COHORT table","cohort_definition" -"condition_occurrence_id","Yes","BIGINT","A unique identifier for each Condition Occurrence event.","condition_occurrence" -"person_id","Yes","BIGINT","A foreign key identifier to the Person who is experiencing the condition. The demographic details of that Person are stored in the PERSON table.","condition_occurrence" -"condition_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the 'Condition' domain.","condition_occurrence" -"condition_start_date","No","DATE","The date when the instance of the Condition is recorded.","condition_occurrence" -"condition_start_datetime","Yes","DATETIME","The date and time when the instance of the Condition is recorded.","condition_occurrence" -"condition_end_date","No","DATE","The date when the instance of the Condition is considered to have ended.","condition_occurrence" -"condition_end_datetime","No","DATETIME","The date when the instance of the Condition is considered to have ended.","condition_occurrence" -"condition_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the source data from which the Condition was recorded, the level of standardization, and the type of occurrence. These belong to the 'Condition Type' vocabulary","condition_occurrence" -"condition_status_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies reflecting the point of care at which the Condition was diagnosed.","condition_occurrence" -"stop_reason","No","VARCHAR(20)","The reason that the Condition was no longer present, as indicated in the source data.","condition_occurrence" -"provider_id","No","INTEGER","A foreign key to the Provider in the PROVIDER table who was responsible for capturing (diagnosing) the Condition.","condition_occurrence" -"visit_occurrence_id","No","INTEGER","A foreign key to the visit in the VISIT_OCCURRENCE table during which the Condition was determined (diagnosed).","condition_occurrence" -"visit_detail_id","No","INTEGER","A foreign key to the visit in the VISIT_DETAIL table during which the Condition was determined (diagnosed).","condition_occurrence" -"condition_source_value","No","VARCHAR(50)","The source code for the Condition as it appears in the source data. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.","condition_occurrence" -"condition_source_concept_id","Yes","INTEGER","A foreign key to a Condition Concept that refers to the code used in the source.","condition_occurrence" -"condition_status_source_value","No","VARCHAR(50)","The source code for the condition status as it appears in the source data. This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference.","condition_occurrence" -"device_exposure_id","Yes","BIGINT","A system-generated unique identifier for each Device Exposure.","device_exposure" -"person_id","Yes","BIGINT","A foreign key identifier to the Person who is subjected to the Device. The demographic details of that Person are stored in the PERSON table.","device_exposure" -"device_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the 'Device' domain.","device_exposure" -"device_exposure_start_date","No","DATE","The date the Device or supply was applied or used.","device_exposure" -"device_exposure_start_datetime","Yes","DATETIME","The date and time the Device or supply was applied or used.","device_exposure" -"device_exposure_end_date","No","DATE","The date use of the Device or supply was ceased.","device_exposure" -"device_exposure_end_datetime","No","DATETIME","The date and time use of the Device or supply was ceased.","device_exposure" -"device_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of Device Exposure recorded. It indicates how the Device Exposure was represented in the source data and belongs to the 'Device Type' domain.","device_exposure" -"unique_device_id","No","VARCHAR(50)","A UDI or equivalent identifying the instance of the Device used in the Person.","device_exposure" -"quantity","No","INTEGER","The number of individual Devices used in the exposure.","device_exposure" -"provider_id","No","INTEGER","A foreign key to the provider in the PROVIDER table who initiated or administered the Device.","device_exposure" -"visit_occurrence_id","No","INTEGER","A foreign key to the visit in the VISIT_OCCURRENCE table during which the Device was used.","device_exposure" -"visit_detail_id","No","INTEGER","A foreign key to the visit detail record in the VISIT_DETAIL table during which the Device was used.","device_exposure" -"device_source_value","No","VARCHAR(50)","The source code for the Device as it appears in the source data. This code is mapped to a Standard Device Concept in the Standardized Vocabularies and the original code is stored here for reference.","device_exposure" -"device_source_concept_id","Yes","INTEGER","A foreign key to a Device Concept that refers to the code used in the source.","device_exposure" -"drug_exposure_id","Yes","BIGINT","A system-generated unique identifier for each Drug utilization event.","drug_exposure" -"person_id","Yes","BIGINT","A foreign key identifier to the Person who is subjected to the Drug. The demographic details of that Person are stored in the PERSON table.","drug_exposure" -"drug_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies belonging to the 'Drug' domain.","drug_exposure" -"drug_exposure_start_date","No","DATE","The start date for the current instance of Drug utilization. Valid entries include a start date of a prescription, the date a prescription was filled, or the date on which a Drug administration procedure was recorded.","drug_exposure" -"drug_exposure_start_datetime","Yes","DATETIME","The start date and time for the current instance of Drug utilization. Valid entries include a start datetime of a prescription, the date and time a prescription was filled, or the date and time on which a Drug administration procedure was recorded.","drug_exposure" -"drug_exposure_end_date","No","DATE","The end date for the current instance of Drug utilization. Depending on different sources, it could be a known or an inferred date and denotes the last day at which the patient was still exposed to Drug.","drug_exposure" -"drug_exposure_end_datetime","No","DATETIME","The end date and time for the current instance of Drug utilization. Depending on different sources, it could be a known or an inferred date and time and denotes the last day at which the patient was still exposed to Drug.","drug_exposure" -"verbatim_end_date","No","DATE","The known end date of a drug_exposure as provided by the source.","drug_exposure" -"drug_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of Drug Exposure recorded. It indicates how the Drug Exposure was represented in the source data and belongs to the 'Drug Type' vocabulary.","drug_exposure" -"stop_reason","No","VARCHAR(20)","The reason the Drug was stopped. Reasons include regimen completed, changed, removed, etc.","drug_exposure" -"refills","No","INTEGER","The number of refills after the initial prescription. The initial prescription is not counted, values start with null.","drug_exposure" -"quantity","No","FLOAT","The quantity of drug as recorded in the original prescription or dispensing record.","drug_exposure" -"days_supply","No","INTEGER","The number of days of supply of the medication as prescribed. This reflects the intention of the provider for the length of exposure.","drug_exposure" -"sig","No","VARCHAR(MAX)","The directions ('signetur') on the Drug prescription as recorded in the original prescription (and printed on the container) or dispensing record.","drug_exposure" -"route_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies reflecting the route of administration and belonging to the 'Route' domain.","drug_exposure" -"lot_number","No","VARCHAR(50)","An identifier assigned to a particular quantity or lot of Drug product from the manufacturer.","drug_exposure" -"provider_id","No","INTEGER","A foreign key to the provider in the PROVIDER table who initiated (prescribed or administered) the Drug Exposure.","drug_exposure" -"visit_occurrence_id","No","INTEGER","A foreign key to the Visit in the VISIT_OCCURRENCE table during which the Drug Exposure was initiated.","drug_exposure" -"visit_detail_id","No","INTEGER","A foreign key to the Visit Detail in the VISIT_DETAIL table during which the Drug Exposure was initiated.","drug_exposure" -"drug_source_value","No","VARCHAR(50)","The source code for the Drug as it appears in the source data. This code is mapped to a Standard Drug concept in the Standardized Vocabularies and the original code is, stored here for reference.","drug_exposure" -"drug_source_concept_id","Yes","INTEGER","A foreign key to a Drug Concept that refers to the code used in the source.","drug_exposure" -"route_source_value","No","VARCHAR(50)","The information about the route of administration as detailed in the source.","drug_exposure" -"dose_unit_source_value","No","VARCHAR(50)","The information about the dose unit as detailed in the source.","drug_exposure" -"domain_concept_id_1","Yes","INTEGER","The concept representing the domain of fact one, from which the corresponding table can be inferred.","fact_relationship" -"fact_id_1","Yes","INTEGER","The unique identifier in the table corresponding to the domain of fact one.","fact_relationship" -"domain_concept_id_2","Yes","INTEGER","The concept representing the domain of fact two, from which the corresponding table can be inferred.","fact_relationship" -"fact_id_2","Yes","INTEGER","The unique identifier in the table corresponding to the domain of fact two.","fact_relationship" -"relationship_concept_id","Yes","INTEGER","A foreign key to a Standard Concept ID of relationship in the Standardized Vocabularies.","fact_relationship" -"measurement_id","Yes","INTEGER","A unique identifier for each Measurement.","measurement" -"person_id","Yes","INTEGER","A foreign key identifier to the Person about whom the measurement was recorded. The demographic details of that Person are stored in the PERSON table.","measurement" -"measurement_concept_id","Yes","INTEGER","A foreign key to the standard measurement concept identifier in the Standardized Vocabularies. These belong to the 'Measurement' domain, but could overlap with the 'Observation' domain (see #3 below).","measurement" -"measurement_date","No","DATE","The date of the Measurement.","measurement" -"measurement_datetime","Yes","DATETIME","The date and time of the Measurement. Some database systems don't have a datatype of time. To accommodate all temporal analyses, datatype datetime can be used (combining measurement_date and measurement_time [forum discussion](http://forums.ohdsi.org/t/date-time-and-datetime-problem-and-the-world-of-hours-and-1day/314))","measurement" -"measurement_time","No","VARCHAR(10)","The time of the Measurement. This is present for backwards compatibility and will be deprecated in an upcoming version","measurement" -"measurement_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the provenance from where the Measurement record was recorded. These belong to the 'Meas Type' vocabulary","measurement" -"operator_concept_id","No","INTEGER","A foreign key identifier to the predefined Concept in the Standardized Vocabularies reflecting the mathematical operator that is applied to the value_as_number. Operators are <, <=, =, >=, > and these concepts belong to the 'Meas Value Operator' domain.","measurement" -"value_as_number","No","FLOAT","A Measurement result where the result is expressed as a numeric value.","measurement" -"value_as_concept_id","No","INTEGER","A foreign key to a Measurement result represented as a Concept from the Standardized Vocabularies (e.g., positive/negative, present/absent, low/high, etc.). These belong to the 'Meas Value' domain","measurement" -"unit_concept_id","No","INTEGER","A foreign key to a Standard Concept ID of Measurement Units in the Standardized Vocabularies that belong to the 'Unit' domain.","measurement" -"range_low","No","FLOAT","The lower limit of the normal range of the Measurement result. The lower range is assumed to be of the same unit of measure as the Measurement value.","measurement" -"range_high","No","FLOAT","The upper limit of the normal range of the Measurement. The upper range is assumed to be of the same unit of measure as the Measurement value.","measurement" -"provider_id","No","INTEGER","A foreign key to the provider in the PROVIDER table who was responsible for initiating or obtaining the measurement.","measurement" -"visit_occurrence_id","No","INTEGER","A foreign key to the Visit in the VISIT_OCCURRENCE table during which the Measurement was recorded.","measurement" -"visit_detail_id","No","INTEGER","A foreign key to the Visit Detail in the VISIT_DETAIL table during which the Measurement was recorded.","measurement" -"measurement_source_value","No","VARCHAR(50)","The Measurement name as it appears in the source data. This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference.","measurement" -"measurement_source_concept_id","Yes","INTEGER","A foreign key to a Concept in the Standard Vocabularies that refers to the code used in the source.","measurement" -"unit_source_value","No","VARCHAR(50)","The source code for the unit as it appears in the source data. This code is mapped to a standard unit concept in the Standardized Vocabularies and the original code is stored here for reference.","measurement" -"value_source_value","No","VARCHAR(50)","The source value associated with the content of the value_as_number or value_as_concept_id as stored in the source data.","measurement" -"note_id","Yes","INTEGER","A unique identifier for each note.","note" -"person_id","Yes","INTEGER","A foreign key identifier to the Person about whom the Note was recorded. The demographic details of that Person are stored in the PERSON table.","note" -"note_event_id","No","INTEGER","A foreign key identifier to the event (e.g. Measurement, Procedure, Visit, Drug Exposure, etc) record during which the note was recorded.","note" -"note_event_field_concept_id","No","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the field to which the note_event_id is referring.","note" -"note_date","No","DATE","The date the note was recorded.","note" -"note_datetime","Yes","DATETIME","The date and time the note was recorded.","note" -"note_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the type, origin or provenance of the Note. These belong to the 'Note Type' vocabulary","note" -"note_class_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the HL7 LOINC Document Type Vocabulary classification of the note.","note" -"note_title","No","VARCHAR(250)","The title of the Note as it appears in the source.","note" -"note_text","Yes","VARCHAR(MAX)","The content of the Note.","note" -"encoding_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the note character encoding type","note" -"language_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the language of the note","note" -"provider_id","No","INTEGER","A foreign key to the Provider in the PROVIDER table who took the Note.","note" -"visit_occurrence_id","No","INTEGER","A foreign key to the Visit in the VISIT_OCCURRENCE table when the Note was taken.","note" -"visit_detail_id","No","INTEGER","A foreign key to the Visit in the VISIT_DETAIL table when the Note was taken.","note" -"note_source_value","No","VARCHAR(50)","The source value associated with the origin of the Note","note" -"note_nlp_id","Yes","INTEGER","A unique identifier for each term extracted from a note.","note_nlp" -"note_id","Yes","INTEGER","A foreign key to the Note table note the term was","note_nlp" -"section_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies representing the section of the extracted term.","note_nlp" -"snippet","No","VARCHAR(250)","A small window of text surrounding the term.","note_nlp" -"offset","No","VARCHAR(50)","Character offset of the extracted term in the input note.","note_nlp" -"lexical_variant","Yes","VARCHAR(250)","Raw text extracted from the NLP tool.","note_nlp" -"note_nlp_concept_id","Yes","INTEGER","A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the normalized concept for the extracted term. Domain of the term is represented as part of the Concept table.","note_nlp" -"note_nlp_source_concept_id","Yes","INTEGER","A foreign key to a Concept that refers to the code in the source vocabulary used by the NLP system","note_nlp" -"nlp_system","No","VARCHAR(250)","Name and version of the NLP system that extracted the term.Useful for data provenance.","note_nlp" -"nlp_date","Yes","DATE","The date of the note processing.Useful for data provenance.","note_nlp" -"nlp_datetime","No","DATETIME","The date and time of the note processing. Useful for data provenance.","note_nlp" -"term_exists","No","VARCHAR(1)","A summary modifier that signifies presence or absence of the term for a given patient. Useful for quick querying.","note_nlp" -"term_temporal","No","VARCHAR(50)","An optional time modifier associated with the extracted term. (for now “past” or “present” only). Standardize it later.","note_nlp" -"term_modifiers","No","VARCHAR(2000)","A compact description of all the modifiers of the specific term extracted by the NLP system. (e.g. “son has rash” ? “negated=no,subject=family, certainty=undef,conditional=false,general=false”).","note_nlp" -"observation_id","Yes","INTEGER","A unique identifier for each observation.","observation" -"person_id","Yes","INTEGER","A foreign key identifier to the Person about whom the observation was recorded. The demographic details of that Person are stored in the PERSON table.","observation" -"observation_concept_id","Yes","INTEGER","A foreign key to the standard observation concept identifier in the Standardized Vocabularies.","observation" -"observation_date","No","DATE","The date of the observation.","observation" -"observation_datetime","Yes","DATETIME","The date and time of the observation.","observation" -"observation_type_concept_id","Yes","INTEGER","A foreign key to the predefined concept identifier in the Standardized Vocabularies reflecting the type of the observation.","observation" -"value_as_number","No","FLOAT","The observation result stored as a number. This is applicable to observations where the result is expressed as a numeric value.","observation" -"value_as_string","No","VARCHAR(60)","The observation result stored as a string. This is applicable to observations where the result is expressed as verbatim text.","observation" -"value_as_concept_id","No","INTEGER","A foreign key to an observation result stored as a Concept ID. This is applicable to observations where the result can be expressed as a Standard Concept from the Standardized Vocabularies (e.g., positive/negative, present/absent, low/high, etc.).","observation" -"qualifier_concept_id","No","INTEGER","A foreign key to a Standard Concept ID for a qualifier (e.g., severity of drug-drug interaction alert)","observation" -"unit_concept_id","No","INTEGER","A foreign key to a Standard Concept ID of measurement units in the Standardized Vocabularies.","observation" -"provider_id","No","INTEGER","A foreign key to the provider in the PROVIDER table who was responsible for making the observation.","observation" -"visit_occurrence_id","No","INTEGER","A foreign key to the visit in the VISIT_OCCURRENCE table during which the observation was recorded.","observation" -"visit_detail_id","No","INTEGER","A foreign key to the visit in the VISIT_DETAIL table during which the observation was recorded.","observation" -"observation_source_value","No","VARCHAR(50)","The observation code as it appears in the source data. This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is, stored here for reference.","observation" -"observation_source_concept_id","Yes","INTEGER","A foreign key to a Concept that refers to the code used in the source.","observation" -"unit_source_value","No","VARCHAR(50)","The source code for the unit as it appears in the source data. This code is mapped to a standard unit concept in the Standardized Vocabularies and the original code is, stored here for reference.","observation" -"qualifier_source_value","No","VARCHAR(50)","The source value associated with a qualifier to characterize the observation","observation" -"observation_event_id","No","INTEGER","A foreign key to an event table (e.g., PROCEDURE_OCCURRENCE_ID).","observation" -"obs_event_field_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies referring to the field represented in the OBSERVATION_EVENT_ID.","observation" -"value_as_datetime","No","INTEGER","The observation result stored as a datetime value. This is applicable to observations where the result is expressed as a point in time.","observation" -"observation_period_id","Yes","INTEGER","A unique identifier for each observation period.","observation_period" -"person_id","Yes","INTEGER","A foreign key identifier to the person for whom the observation period is defined. The demographic details of that person are stored in the person table.","observation_period" -"observation_period_start_date","Yes","DATE","The start date of the observation period for which data are available from the data source.","observation_period" -"observation_period_end_date","Yes","DATE","The end date of the observation period for which data are available from the data source.","observation_period" -"period_type_concept_id","Yes","INTEGER","A foreign key identifier to the predefined concept in the Standardized Vocabularies reflecting the source of the observation period information, belonging to the 'Obs Period Type' vocabulary","observation_period" -"person_id","Yes","INTEGER","A unique identifier for each person.","person" -"gender_concept_id","Yes","INTEGER","A foreign key that refers to an identifier in the CONCEPT table for the unique gender of the person.","person" -"year_of_birth","Yes","INTEGER","The year of birth of the person. For data sources with date of birth, the year is extracted. For data sources where the year of birth is not available, the approximate year of birth is derived based on any age group categorization available.","person" -"month_of_birth","No","INTEGER","The month of birth of the person. For data sources that provide the precise date of birth, the month is extracted and stored in this field.","person" -"day_of_birth","No","INTEGER","The day of the month of birth of the person. For data sources that provide the precise date of birth, the day is extracted and stored in this field.","person" -"birth_datetime","No","DATETIME","The date and time of birth of the person.","person" -"death_datetime","No","DATETIME","The date and time of death of the person.","person" -"race_concept_id","Yes","INTEGER","A foreign key that refers to an identifier in the CONCEPT table for the unique race of the person, belonging to the 'Race' vocabulary.","person" -"ethnicity_concept_id","Yes","INTEGER","A foreign key that refers to the standard concept identifier in the Standardized Vocabularies for the ethnicity of the person, belonging to the 'Ethnicity' vocabulary.","person" -"location_id","No","INTEGER","A foreign key to the place of residency for the person in the location table, where the detailed address information is stored.","person" -"provider_id","No","INTEGER","A foreign key to the primary care provider the person is seeing in the provider table.","person" -"care_site_id","No","INTEGER","A foreign key to the site of primary care in the care_site table, where the details of the care site are stored.","person" -"person_source_value","No","VARCHAR(50)","An (encrypted) key derived from the person identifier in the source data. This is necessary when a use case requires a link back to the person data at the source dataset.","person" -"gender_source_value","No","VARCHAR(50)","The source code for the gender of the person as it appears in the source data. The person’s gender is mapped to a standard gender concept in the Standardized Vocabularies; the original value is stored here for reference.","person" -"gender_source_concept_id","Yes","INTEGER","A foreign key to the gender concept that refers to the code used in the source.","person" -"race_source_value","No","VARCHAR(50)","The source code for the race of the person as it appears in the source data. The person race is mapped to a standard race concept in the Standardized Vocabularies and the original value is stored here for reference.","person" -"race_source_concept_id","Yes","INTEGER","A foreign key to the race concept that refers to the code used in the source.","person" -"ethnicity_source_value","No","VARCHAR(50)","The source code for the ethnicity of the person as it appears in the source data. The person ethnicity is mapped to a standard ethnicity concept in the Standardized Vocabularies and the original code is, stored here for reference.","person" -"ethnicity_source_concept_id","Yes","INTEGER","A foreign key to the ethnicity concept that refers to the code used in the source.","person" -"procedure_occurrence_id","Yes","INTEGER","A system-generated unique identifier for each Procedure Occurrence.","procedure_occurrence" -"person_id","Yes","INTEGER","A foreign key identifier to the Person who is subjected to the Procedure. The demographic details of that Person are stored in the PERSON table.","procedure_occurrence" -"procedure_concept_id","Yes","INTEGER","A foreign key that refers to a standard procedure Concept identifier in the Standardized Vocabularies.","procedure_occurrence" -"procedure_date","No","DATE","The date on which the Procedure was performed.","procedure_occurrence" -"procedure_datetime","Yes","DATETIME","The date and time on which the Procedure was performed.","procedure_occurrence" -"procedure_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of source data from which the procedure record is derived, belonging to the 'Procedure Type' vocabulary.","procedure_occurrence" -"modifier_concept_id","Yes","INTEGER","A foreign key to a Standard Concept identifier for a modifier to the Procedure (e.g. bilateral). These concepts are typically distinguished by 'Modifier' concept classes (e.g., 'CPT4 Modifier' as part of the 'CPT4' vocabulary).","procedure_occurrence" -"quantity","No","INTEGER","The quantity of procedures ordered or administered.","procedure_occurrence" -"provider_id","No","INTEGER","A foreign key to the provider in the PROVIDER table who was responsible for carrying out the procedure.","procedure_occurrence" -"visit_occurrence_id","No","INTEGER","A foreign key to the Visit in the VISIT_OCCURRENCE table during which the Procedure was carried out.","procedure_occurrence" -"visit_detail_id","No","INTEGER","A foreign key to the Visit Detail in the VISIT_DETAIL table during which the Procedure was carried out.","procedure_occurrence" -"procedure_source_value","No","VARCHAR(50)","The source code for the Procedure as it appears in the source data. This code is mapped to a standard procedure Concept in the Standardized Vocabularies and the original code is, stored here for reference. Procedure source codes are typically ICD-9-Proc, CPT-4, HCPCS or OPCS-4 codes.","procedure_occurrence" -"procedure_source_concept_id","Yes","INTEGER","A foreign key to a Procedure Concept that refers to the code used in the source.","procedure_occurrence" -"modifier_source_value","No","VARCHAR(50)","The source code for the qualifier as it appears in the source data.","procedure_occurrence" -"specimen_id","Yes","INTEGER","A unique identifier for each specimen.","specimen" -"person_id","Yes","INTEGER","A foreign key identifier to the Person for whom the Specimen is recorded.","specimen" -"specimen_concept_id","Yes","INTEGER","A foreign key referring to a Standard Concept identifier in the Standardized Vocabularies for the Specimen.","specimen" -"specimen_type_concept_id","Yes","INTEGER","A foreign key referring to the Concept identifier in the Standardized Vocabularies reflecting the system of record from which the Specimen was represented in the source data.","specimen" -"specimen_date","No","DATE","The date the specimen was obtained from the Person.","specimen" -"specimen_datetime","Yes","DATETIME","The date and time on the date when the Specimen was obtained from the person.","specimen" -"quantity","No","FLOAT","The amount of specimen collection from the person during the sampling procedure.","specimen" -"unit_concept_id","No","INTEGER","A foreign key to a Standard Concept identifier for the Unit associated with the numeric quantity of the Specimen collection.","specimen" -"anatomic_site_concept_id","Yes","INTEGER","A foreign key to a Standard Concept identifier for the anatomic location of specimen collection.","specimen" -"disease_status_concept_id","Yes","INTEGER","A foreign key to a Standard Concept identifier for the Disease Status of specimen collection.","specimen" -"specimen_source_id","No","VARCHAR(50)","The Specimen identifier as it appears in the source data.","specimen" -"specimen_source_value","No","VARCHAR(50)","The Specimen value as it appears in the source data. This value is mapped to a Standard Concept in the Standardized Vocabularies and the original code is, stored here for reference.","specimen" -"unit_source_value","No","VARCHAR(50)","The information about the Unit as detailed in the source.","specimen" -"anatomic_site_source_value","No","VARCHAR(50)","The information about the anatomic site as detailed in the source.","specimen" -"disease_status_source_value","No","VARCHAR(50)","The information about the disease status as detailed in the source.","specimen" -"survey_conduct_id","Yes","INTEGER","Unique identifier for each completed survey.","survey_conduct" -"person_id","Yes","INTEGER","A foreign key identifier to the Person in the PERSON table about whom the survey was completed.","survey_conduct" -"survey_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the name and identity of the survey.","survey_conduct" -"survey_start_date","No","DATE","Date on which the survey was started.","survey_conduct" -"survey_start_datetime","No","DATETIME","Date and time the survey was started.","survey_conduct" -"survey_end_date","Yes","DATE","Date on which the survey was completed.","survey_conduct" -"survey_end_datetime","No","DATETIME","Date and time the survey was completed.","survey_conduct" -"provider_id","No","INTEGER","A foreign key to the provider in the provider table who was associated with the survey completion.","survey_conduct" -"assisted_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies indicating whether the survey was completed with assistance.","survey_conduct" -"respondent_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the respondent type. Example: Research Associate, Patient.","survey_conduct" -"timing_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies that refers to a certain timing. Example: 3 month follow-up, 6 month follow-up.","survey_conduct" -"collection_method_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the data collection method (e.g. Paper, Telephone, Electronic Questionnaire).","survey_conduct" -"assisted_source_value","No","VARCHAR(50)","Source value representing whether patient required assistance to complete the survey. Example: “Completed without assistance”, ”Completed with assistance”.","survey_conduct" -"respondent_type_source_value","No","VARCHAR(100)","Source code representing role of person who completed the survey.","survey_conduct" -"timing_source_value","No","VARCHAR(100)","Text string representing the timing of the survey. Example: Baseline, 6-month follow-up.","survey_conduct" -"collection_method_source_value","No","VARCHAR(100)","The collection method as it appears in the source data.","survey_conduct" -"survey_source_value","No","VARCHAR(100)","The survey name/title as it appears in the source data.","survey_conduct" -"survey_source_concept_id","Yes","INTEGER","A foreign key to a predefined Concept that refers to the code for the survey name/title used in the source.","survey_conduct" -"survey_source_identifier","No","VARCHAR(100)","Unique identifier for each completed survey in source system.","survey_conduct" -"validated_survey_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the validation status of the survey.","survey_conduct" -"validated_survey_source_value","No","INTEGER","Source value representing the validation status of the survey.","survey_conduct" -"survey_version_number","No","VARCHAR(20)","Version number of the questionnaire or survey used.","survey_conduct" -"visit_occurrence_id","No","INTEGER","A foreign key to the VISIT_OCCURRENCE table during which the survey was completed","survey_conduct" -"response_visit_occurrence_id","No","INTEGER","A foreign key to the visit in the VISIT_OCCURRENCE table during which treatment was carried out that relates to this survey.","survey_conduct" -"visit_detail_id","Yes","INTEGER","A unique identifier for each Person's visit or encounter at a healthcare provider.","visit_detail" -"person_id","Yes","INTEGER","A foreign key identifier to the Person for whom the visit is recorded. The demographic details of that Person are stored in the PERSON table.","visit_detail" -"visit_detail_concept_id","Yes","INTEGER","A foreign key that refers to a visit Concept identifier in the Standardized Vocabularies belonging to the 'Visit' Vocabulary.","visit_detail" -"visit_detail_start_date","No","DATE","The start date of the visit.","visit_detail" -"visit_detail_start_datetime","Yes","DATETIME","The date and time of the visit started.","visit_detail" -"visit_detail_end_date","No","DATE","The end date of the visit. If this is a one-day visit the end date should match the start date.","visit_detail" -"visit_detail_end_datetime","Yes","DATETIME","The date and time of the visit end.","visit_detail" -"visit_detail_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of source data from which the visit record is derived belonging to the 'Visit Type' vocabulary.","visit_detail" -"provider_id","No","INTEGER","A foreign key to the provider in the provider table who was associated with the visit.","visit_detail" -"care_site_id","No","INTEGER","A foreign key to the care site in the care site table that was visited.","visit_detail" -"visit_detail_source_value","No","STRING(50)","The source code for the visit as it appears in the source data.","visit_detail" -"visit_detail_source_concept_id","Yes","INTEGER","A foreign key to a Concept that refers to the code used in the source.","visit_detail" -"admitted_from_source_value","No","VARCHAR(50)","The source code for the admitting source as it appears in the source data.","visit_detail" -"admitted_from_concept_id","Yes","INTEGER","A foreign key to the predefined concept in the 'Place of Service' Vocabulary reflecting the admitting source for a visit.","visit_detail" -"discharge_to_source_value","No","VARCHAR(50)","The source code for the discharge disposition as it appears in the source data.","visit_detail" -"discharge_to_concept_id","Yes","INTEGER","A foreign key to the predefined concept in the 'Place of Service' Vocabulary reflecting the discharge disposition for a visit.","visit_detail" -"preceding_visit_detail_id","No","INTEGER","A foreign key to the VISIT_DETAIL table of the visit immediately preceding this visit","visit_detail" -"visit_detail_parent_id","No","INTEGER","A foreign key to the VISIT_DETAIL table record to represent the immediate parent visit-detail record.","visit_detail" -"visit_occurrence_id","Yes","INTEGER","A foreign key that refers to the record in the VISIT_OCCURRENCE table. This is a required field, because for every visit_detail is a child of visit_occurrence and cannot exist without a corresponding parent record in visit_occurrence.","visit_detail" -"visit_occurrence_id","Yes","INTEGER","A unique identifier for each Person's visit or encounter at a healthcare provider.","visit_occurrence" -"person_id","Yes","INTEGER","A foreign key identifier to the Person for whom the visit is recorded. The demographic details of that Person are stored in the PERSON table.","visit_occurrence" -"visit_concept_id","Yes","INTEGER","A foreign key that refers to a visit Concept identifier in the Standardized Vocabularies belonging to the 'Visit' Vocabulary.","visit_occurrence" -"visit_start_date","No","DATE","The start date of the visit.","visit_occurrence" -"visit_start_datetime","Yes","DATETIME","The date and time of the visit started.","visit_occurrence" -"visit_end_date","No","DATE","The end date of the visit. If this is a one-day visit the end date should match the start date.","visit_occurrence" -"visit_end_datetime","Yes","DATETIME","The date and time of the visit end.","visit_occurrence" -"visit_type_concept_id","Yes","INTEGER","A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of source data from which the visit record is derived belonging to the 'Visit Type' vocabulary.","visit_occurrence" -"provider_id","No","INTEGER","A foreign key to the provider in the provider table who was associated with the visit.","visit_occurrence" -"care_site_id","No","INTEGER","A foreign key to the care site in the care site table that was visited.","visit_occurrence" -"visit_source_value","No","VARCHAR(50)","The source code for the visit as it appears in the source data.","visit_occurrence" -"visit_source_concept_id","Yes","INTEGER","A foreign key to a Concept that refers to the code used in the source.","visit_occurrence" -"admitting_source_concept_id","Yes","INTEGER","A foreign key to the predefined concept in the Place of Service Vocabulary reflecting the admitting source for a visit.","visit_occurrence" -"admitting_source_value","No","VARCHAR(50)","The source code for the admitting source as it appears in the source data.","visit_occurrence" -"discharge_to_concept_id","Yes","INTEGER","A foreign key to the predefined concept in the Place of Service Vocabulary reflecting the discharge disposition for a visit.","visit_occurrence" -"discharge_to_source_value","No","VARCHAR(50)","The source code for the discharge disposition as it appears in the source data.","visit_occurrence" -"preceding_visit_occurrence_id","No","INTEGER","A foreign key to the VISIT_OCCURRENCE table of the visit immediately preceding this visit","visit_occurrence" -"condition_era_id","Yes","INTEGER","A unique identifier for each Condition Era.","condition_era" -"person_id","Yes","INTEGER","A foreign key identifier to the Person who is experiencing the Condition during the Condition Era. The demographic details of that Person are stored in the PERSON table.","condition_era" -"condition_concept_id","Yes","INTEGER","A foreign key that refers to a standard Condition Concept identifier in the Standardized Vocabularies.","condition_era" -"condition_era_start_datetime","Yes","DATE","The start date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the start date of the very first chronologically recorded instance of the condition.","condition_era" -"condition_era_end_datetime","Yes","DATE","The end date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the end date of the final continuously recorded instance of the Condition.","condition_era" -"condition_occurrence_count","No","INTEGER","The number of individual Condition Occurrences used to construct the condition era.","condition_era" -"dose_era_id","Yes","INTEGER","A unique identifier for each Dose Era.","dose_era" -"person_id","Yes","INTEGER","A foreign key identifier to the Person who is subjected to the drug during the drug era. The demographic details of that Person are stored in the PERSON table.","dose_era" -"drug_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the active Ingredient Concept.","dose_era" -"unit_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the unit concept.","dose_era" -"dose_value","Yes","FLOAT","The numeric value of the dose.","dose_era" -"dose_era_start_datetime","Yes","DATE","The start date for the drug era constructed from the individual instances of drug exposures. It is the start date of the very first chronologically recorded instance of utilization of a drug.","dose_era" -"dose_era_end_datetime","Yes","DATE","The end date for the drug era constructed from the individual instance of drug exposures. It is the end date of the final continuously recorded instance of utilization of a drug.","dose_era" -"drug_era_id","Yes","INTEGER","A unique identifier for each Drug Era.","drug_era" -"person_id","Yes","INTEGER","A foreign key identifier to the Person who is subjected to the Drug during the fDrug Era. The demographic details of that Person are stored in the PERSON table.","drug_era" -"drug_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the Ingredient Concept.","drug_era" -"drug_era_start_datetime","Yes","DATE","The start date for the Drug Era constructed from the individual instances of Drug Exposures. It is the start date of the very first chronologically recorded instance of conutilization of a Drug.","drug_era" -"drug_era_end_datetime","Yes","DATE","The end date for the drug era constructed from the individual instance of drug exposures. It is the end date of the final continuously recorded instance of utilization of a drug.","drug_era" -"drug_exposure_count","No","INTEGER","The number of individual Drug Exposure occurrences used to construct the Drug Era.","drug_era" -"gap_days","No","INTEGER","The number of days that are not covered by DRUG_EXPOSURE records that were used to make up the era record.","drug_era" -"cost_id","Yes","INTEGER","A unique identifier for each COST record.","cost" -"person_id","Yes","INTEGER","A unique identifier for each PERSON.","cost" -"cost_event_id","Yes","INTEGER","A foreign key identifier to the event (e.g. Measurement, Procedure, Visit, Drug Exposure, etc) record for which cost data are recorded.","cost" -"cost_event_field_concept_id","Yes","INTEGER","A foreign key identifier to a concept in the CONCEPT table representing the identity of the field represented by COST_EVENT_ID","cost" -"cost_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Cost Concept identifier in the Standardized Vocabularies belonging to the 'Cost' vocabulary.","cost" -"cost_type_concept_id","Yes","INTEGER","A foreign key identifier to a concept in the CONCEPT table for the provenance or the source of the COST data and belonging to the 'Cost Type' vocabulary","cost" -"cost_source_concept_id","Yes","INTEGER","A foreign key to a Cost Concept that refers to the code used in the source.","cost" -"cost_source_value","No","VARCHAR(50)","The source value for the cost as it appears in the source data","cost" -"currency_concept_id","Yes","INTEGER","A foreign key identifier to the concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar. These belong to the 'Currency' vocabulary","cost" -"cost","Yes","FLOAT","The actual financial cost amount","cost" -"incurred_date","Yes","DATE","The first date of service of the clinical event corresponding to the cost as in table capturing the information (e.g. date of visit, date of procedure, date of condition, date of drug etc).","cost" -"billed_date","No","DATE","The date a bill was generated for a service or encounter","cost" -"paid_date","No","DATE","The date payment was received for a service or encounter","cost" -"revenue_code_concept_id","Yes","INTEGER","A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for Revenue codes belonging to the 'Revenue Code' vocabulary.","cost" -"drg_concept_id","Yes","INTEGER","A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for DRG codes belonging to the 'DRG' vocabulary.","cost" -"revenue_code_source_value","No","VARCHAR(50)","The source value for the Revenue code as it appears in the source data, stored here for reference.","cost" -"drg_source_value","No","VARCHAR(50)","The source value for the 3-digit DRG source code as it appears in the source data, stored here for reference.","cost" -"payer_plan_period_id","No","INTEGER","A foreign key to the PAYER_PLAN_PERIOD table, where the details of the Payer, Plan and Family are stored. Record the payer_plan_id that relates to the payer who contributed to the paid_by_payer field.","cost" -"payer_plan_period_id","Yes","INTEGER","A identifier for each unique combination of payer, plan, family code and time span.","payer_plan_period" -"person_id","Yes","INTEGER","A foreign key identifier to the Person covered by the payer. The demographic details of that Person are stored in the PERSON table.","payer_plan_period" -"contract_person_id","No","INTEGER","A foreign key identifier to the person_id in person table, for the person who is the primary subscriber/contract owner for the record in the payer_plan_period table. Maybe the same person or different person, depending on who is the primary subscriber/contract owner.","payer_plan_period" -"payer_plan_period_start_date","Yes","DATE","The start date of the payer plan period.","payer_plan_period" -"payer_plan_period_end_date","Yes","DATE","The end date of the payer plan period.","payer_plan_period" -"payer_concept_id","Yes","INTEGER","A foreign key that refers to a standard Payer concept identifier in the Standarized Vocabularies","payer_plan_period" -"payer_source_value","No","VARCHAR(50)","The source code for the payer as it appears in the source data.","payer_plan_period" -"payer_source_concept_id","Yes","INTEGER","A foreign key to a payer concept that refers to the code used in the source.","payer_plan_period" -"plan_concept_id","Yes","INTEGER","A foreign key that refers to a standard plan concept identifier that represents the health benefit plan in the Standardized Vocabularies.","payer_plan_period" -"plan_source_value","No","VARCHAR(50)","The source code for the Person's health benefit plan as it appears in the source data.","payer_plan_period" -"plan_source_concept_id","Yes","INTEGER","A foreign key to a plan concept that refers to the plan code used in the source data.","payer_plan_period" -"contract_concept_id","Yes","INTEGER","A foreign key to a standard concept representing the reason justifying the contract between person_id and contract_person_id.","payer_plan_period" -"contract_source_value","No","INTEGER","The source code representing the reason justifying the contract. Usually it is family relationship like a spouse, domestic partner, child etc.","payer_plan_period" -"contract_source_concept_id","Yes","INTEGER","A foreign key to a concept that refers to the code used in the source as the reason justifying the contract.","payer_plan_period" -"sponsor_concept_id","Yes","INTEGER","A foreign key that refers to a concept identifier that represents the sponsor in the Standardized Vocabularies.","payer_plan_period" -"sponsor_source_value","No","VARCHAR(50)","The source code for the Person's sponsor of the health plan as it appears in the source data.","payer_plan_period" -"sponsor_source_concept_id","Yes","INTEGER","A foreign key to a sponsor concept that refers to the sponsor code used in the source data.","payer_plan_period" -"family_source_value","No","VARCHAR(50)","The source code for the Person's family as it appears in the source data.","payer_plan_period" -"stop_reason_concept_id","Yes","INTEGER","A foreign key that refers to a standard termination reason that represents the reason for the termination in the Standardized Vocabularies.","payer_plan_period" -"stop_reason_source_value","No","VARCHAR(50)","The reason for stop-coverage as it appears in the source data.","payer_plan_period" -"stop_reason_source_concept_id","Yes","INTEGER","A foreign key to a stop-coverage concept that refers to the code used in the source.","payer_plan_period" -"care_site_id","Yes","INTEGER","A unique identifier for each Care Site.","care_site" -"care_site_name","No","VARCHAR(255)","The verbatim description or name of the Care Site as in data source","care_site" -"place_of_service_concept_id","Yes","INTEGER","A foreign key that refers to a Place of Service Concept ID in the Standardized Vocabularies.","care_site" -"location_id","No","INTEGER","A foreign key to the geographic Location in the LOCATION table, where the detailed address information is stored.","care_site" -"care_site_source_value","No","VARCHAR(50)","The identifier for the Care Site in the source data, stored here for reference.","care_site" -"place_of_service_source_value","No","VARCHAR(50)","The source code for the Place of Service as it appears in the source data, stored here for reference.","care_site" -"location_id","Yes","INTEGER","A unique identifier for each geographic location.","location" -"address_1","No","VARCHAR(50)","The address field 1, typically used for the street address, as it appears in the source data.","location" -"address_2","No","VARCHAR(50)","The address field 2, typically used for additional detail such as buildings, suites, floors, as it appears in the source data.","location" -"city","No","VARCHAR(50)","The city field as it appears in the source data.","location" -"state","No","VARCHAR(2)","The state field as it appears in the source data.","location" -"zip","No","VARCHAR(9)","The zip or postal code.","location" -"county","No","VARCHAR(20)","The county.","location" -"country","No","VARCHAR(100)","The country","location" -"location_source_value","No","VARCHAR(50)","The verbatim information that is used to uniquely identify the location as it appears in the source data.","location" -"latitude","No","FLOAT","The geocoded latitude","location" -"longitude","No","FLOAT","The geocoded longitude","location" -"location_id","Yes","INTEGER","A foreign key to the location table.","location_history" -"relationship_type_concept_id","Yes","VARCHAR(50)","The type of relationship between location and entity.","location_history" -"domain_id","Yes","VARCHAR(50)","The domain of the entity that is related to the location. Either PERSON, PROVIDER, or CARE_SITE.","location_history" -"entity_id","Yes","INTEGER","The unique identifier for the entity. References either person_id, provider_id, or care_site_id, depending on domain_id.","location_history" -"start_date","Yes","DATE","The date the relationship started.","location_history" -"end_date","No","DATE","The date the relationship ended.","location_history" -"provider_id","Yes","INTEGER","A unique identifier for each Provider.","provider" -"provider_name","No","VARCHAR(255)","A description of the Provider.","provider" -"npi","No","VARCHAR(20)","The National Provider Identifier (NPI) of the provider.","provider" -"dea","No","VARCHAR(20)","The Drug Enforcement Administration (DEA) number of the provider.","provider" -"specialty_concept_id","Yes","INTEGER","A foreign key to a Standard Specialty Concept ID in the Standardized Vocabularies.","provider" -"care_site_id","No","INTEGER","A foreign key to the main Care Site where the provider is practicing.","provider" -"year_of_birth","No","INTEGER","The year of birth of the Provider.","provider" -"gender_concept_id","Yes","INTEGER","The gender of the Provider.","provider" -"provider_source_value","No","VARCHAR(50)","The identifier used for the Provider in the source data, stored here for reference.","provider" -"specialty_source_value","No","VARCHAR(50)","The source code for the Provider specialty as it appears in the source data, stored here for reference.","provider" -"specialty_source_concept_id","Yes","INTEGER","A foreign key to a Concept that refers to the code used in the source.","provider" -"gender_source_value","No","VARCHAR(50)","The gender code for the Provider as it appears in the source data, stored here for reference.","provider" -"gender_source_concept_id","Yes","INTEGER","A foreign key to a Concept that refers to the code used in the source.","provider" -"cdm_source_name","Yes","VARCHAR(255)","The full name of the source","cdm_source" -"cdm_source_abbreviation","No","VARCHAR(25)","An abbreviation of the name","cdm_source" -"cdm_holder","No","VARCHAR(255)","The name of the organization responsible for the development of the CDM instance","cdm_source" -"source_description","No","CLOB","A description of the source data origin and purpose for collection. The description may contain a summary of the period of time that is expected to be covered by this dataset.","cdm_source" -"source_documentation_reference","No","VARCHAR(255)","URL or other external reference to location of source documentation","cdm_source" -"cdm_etl_reference","No","VARCHAR(255)","URL or other external reference to location of ETL specification documentation and ETL source code","cdm_source" -"source_release_date","No","DATE","The date for which the source data are most current, such as the last day of data capture","cdm_source" -"cdm_release_date","No","DATE","The date when the CDM was instantiated","cdm_source" -"cdm_version","No","VARCHAR(10)","The version of CDM used","cdm_source" -"vocabulary_version","No","VARCHAR(20)","The version of the vocabulary used","cdm_source" -"metadata_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Metadata Concept identifier in the Standardized Vocabularies.","metadata" -"metadata_type_concept_id","Yes","INTEGER","A foreign key that refers to a Standard Type Concept identifier in the Standardized Vocabularies.","metadata" -"name","Yes","VARCHAR(250)","The name of the Concept stored in metadata_concept_id or a description of the data being stored.","metadata" -"value_as_string","No","NVARCHAR","The metadata value stored as a string.","metadata" -"value_as_concept_id","No","INTEGER","A foreign key to a metadata value stored as a Concept ID.","metadata" -"metadata date","No","DATE","The date associated with the metadata","metadata" -"metadata_datetime","No","DATETIME","The date and time associated with the metadata","metadata" -"concept_id","Yes","INTEGER","A unique identifier for each Concept across all domains.","concept" -"concept_name","Yes","VARCHAR(255)","An unambiguous, meaningful and descriptive name for the Concept.","concept" -"domain_id","Yes","VARCHAR(20)","A foreign key to the [DOMAIN](https://github.com/OHDSI/CommonDataModel/wiki/DOMAIN) table the Concept belongs to.","concept" -"vocabulary_id","Yes","VARCHAR(20)","A foreign key to the [VOCABULARY](https://github.com/OHDSI/CommonDataModel/wiki/VOCABULARY) table indicating from which source the Concept has been adapted.","concept" -"concept_class_id","Yes","VARCHAR(20)","The attribute or concept class of the Concept. Examples are 'Clinical Drug', 'Ingredient', 'Clinical Finding' etc.","concept" -"standard_concept","No","VARCHAR(1)","This flag determines where a Concept is a Standard Concept, i.e. is used in the data, a Classification Concept, or a non-standard Source Concept. The allowables values are 'S' (Standard Concept) and 'C' (Classification Concept), otherwise the content is NULL.","concept" -"concept_code","Yes","VARCHAR(50)","The concept code represents the identifier of the Concept in the source vocabulary, such as SNOMED-CT concept IDs, RxNorm RXCUIs etc. Note that concept codes are not unique across vocabularies.","concept" -"valid_start_date","Yes","DATE","The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.","concept" -"valid_end_date","Yes","DATE","The date when the Concept became invalid because it was deleted or superseded (updated) by a new concept. The default value is 31-Dec-2099, meaning, the Concept is valid until it becomes deprecated.","concept" -"invalid_reason","No","VARCHAR(1)","Reason the Concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.","concept" -"ancestor_concept_id","Yes","INTEGER","A foreign key to the concept in the concept table for the higher-level concept that forms the ancestor in the relationship.","concept_ancestor" -"descendant_concept_id","Yes","INTEGER","A foreign key to the concept in the concept table for the lower-level concept that forms the descendant in the relationship.","concept_ancestor" -"min_levels_of_separation","Yes","INTEGER","The minimum separation in number of levels of hierarchy between ancestor and descendant concepts. This is an attribute that is used to simplify hierarchic analysis.","concept_ancestor" -"max_levels_of_separation","Yes","INTEGER","The maximum separation in number of levels of hierarchy between ancestor and descendant concepts. This is an attribute that is used to simplify hierarchic analysis.","concept_ancestor" -"concept_class_id","Yes","VARCHAR(20)","A unique key for each class.","concept_class" -"concept_class_name","Yes","VARCHAR(255)","The name describing the Concept Class, e.g. ""Clinical Finding"", ""Ingredient"", etc.","concept_class" -"concept_class_concept_id","Yes","INTEGER","A foreign key that refers to an identifier in the [CONCEPT](https://github.com/OHDSI/CommonDataModel/wiki/CONCEPT) table for the unique Concept Class the record belongs to.","concept_class" -"concept_id_1","Yes","INTEGER","A foreign key to a Concept in the [CONCEPT](https://github.com/OHDSI/CommonDataModel/wiki/CONCEPT) table associated with the relationship. Relationships are directional, and this field represents the source concept designation.","concept_relationship" -"concept_id_2","Yes","INTEGER","A foreign key to a Concept in the [CONCEPT](https://github.com/OHDSI/CommonDataModel/wiki/CONCEPT) table associated with the relationship. Relationships are directional, and this field represents the destination concept designation.","concept_relationship" -"relationship_id","Yes","VARCHAR(20)","A unique identifier to the type or nature of the Relationship as defined in the [RELATIONSHIP](https://github.com/OHDSI/CommonDataModel/wiki/RELATIONSHIP) table.","concept_relationship" -"valid_start_date","Yes","DATE","The date when the instance of the Concept Relationship is first recorded.","concept_relationship" -"valid_end_date","Yes","DATE","The date when the Concept Relationship became invalid because it was deleted or superseded (updated) by a new relationship. Default value is 31-Dec-2099.","concept_relationship" -"invalid_reason","No","VARCHAR(1)","Reason the relationship was invalidated. Possible values are 'D' (deleted), 'U' (replaced with an update) or NULL when valid_end_date has the default value.","concept_relationship" -"concept_id","Yes","INTEGER","A foreign key to the Concept in the CONCEPT table.","concept_synonym" -"concept_synonym_name","Yes","VARCHAR(1000)","The alternative name for the Concept.","concept_synonym" -"language_concept_id","Yes","INTEGER","A foreign key to a Concept representing the language.","concept_synonym" -"domain_id","Yes","VARCHAR(20)","A unique key for each domain.","domain" -"domain_name","Yes","VARCHAR(255)","The name describing the Domain, e.g. ""Condition"", ""Procedure"", ""Measurement"" etc.","domain" -"domain_concept_id","Yes","INTEGER","A foreign key that refers to an identifier in the [CONCEPT](https://github.com/OHDSI/CommonDataModel/wiki/CONCEPT) table for the unique Domain Concept the Domain record belongs to.","domain" -"drug_concept_id","Yes","INTEGER","A foreign key to the Concept in the CONCEPT table representing the identifier for Branded Drug or Clinical Drug Concept.","drug_strength" -"ingredient_concept_id","Yes","INTEGER","A foreign key to the Concept in the CONCEPT table, representing the identifier for drug Ingredient Concept contained within the drug product.","drug_strength" -"amount_value","No","FLOAT","The numeric value associated with the amount of active ingredient contained within the product.","drug_strength" -"amount_unit_concept_id","No","INTEGER","A foreign key to the Concept in the CONCEPT table representing the identifier for the Unit for the absolute amount of active ingredient.","drug_strength" -"numerator_value","No","FLOAT","The numeric value associated with the concentration of the active ingredient contained in the product","drug_strength" -"numerator_unit_concept_id","No","INTEGER","A foreign key to the Concept in the CONCEPT table representing the identifier for the numerator Unit for the concentration of active ingredient.","drug_strength" -"denominator_value","No","FLOAT","The amount of total liquid (or other divisible product, such as ointment, gel, spray, etc.).","drug_strength" -"denominator_unit_concept_id","No","INTEGER","A foreign key to the Concept in the CONCEPT table representing the identifier for the denominator Unit for the concentration of active ingredient.","drug_strength" -"box_size","No","INTEGER","The number of units of Clinical of Branded Drug, or Quantified Clinical or Branded Drug contained in a box as dispensed to the patient","drug_strength" -"valid_start_date","Yes","DATE","The date when the Concept was first recorded. The default value is 1-Jan-1970.","drug_strength" -"valid_end_date","Yes","DATE","The date when the concept became invalid because it was deleted or superseded (updated) by a new Concept. The default value is 31-Dec-2099.","drug_strength" -"invalid_reason","No","VARCHAR(1)","Reason the concept was invalidated. Possible values are 'D' (deleted), 'U' (replaced with an update) or NULL when valid_end_date has the default value.","drug_strength" -"relationship_id","Yes","VARCHAR(20)","The type of relationship captured by the relationship record.","relationship" -"relationship_name","Yes","VARCHAR(255)","The text that describes the relationship type.","relationship" -"is_hierarchical","Yes","VARCHAR(1)","Defines whether a relationship defines concepts into classes or hierarchies. Values are 1 for hierarchical relationship or 0 if not.","relationship" -"defines_ancestry","Yes","VARCHAR(1)","Defines whether a hierarchical relationship contributes to the concept_ancestor table. These are subsets of the hierarchical relationships. Valid values are 1 or 0.","relationship" -"reverse_relationship_id","Yes","VARCHAR(20)","The identifier for the relationship used to define the reverse relationship between two concepts.","relationship" -"relationship_concept_id","Yes","INTEGER","A foreign key that refers to an identifier in the CONCEPT table for the unique relationship concept.","relationship" -"source_code","Yes","VARCHAR(50)","The source code being translated into a Standard Concept.","source_to_concept_map" -"source_concept_id","Yes","INTEGER","A foreign key to the Source Concept that is being translated into a Standard Concept.","source_to_concept_map" -"source_vocabulary_id","Yes","VARCHAR(20)","A foreign key to the VOCABULARY table defining the vocabulary of the source code that is being translated to a Standard Concept.","source_to_concept_map" -"source_code_description","No","VARCHAR(255)","An optional description for the source code. This is included as a convenience to compare the description of the source code to the name of the concept.","source_to_concept_map" -"target_concept_id","Yes","INTEGER","A foreign key to the target Concept to which the source code is being mapped.","source_to_concept_map" -"target_vocabulary_id","Yes","VARCHAR(20)","A foreign key to the VOCABULARY table defining the vocabulary of the target Concept.","source_to_concept_map" -"valid_start_date","Yes","DATE","The date when the mapping instance was first recorded.","source_to_concept_map" -"valid_end_date","Yes","DATE","The date when the mapping instance became invalid because it was deleted or superseded (updated) by a new relationship. Default value is 31-Dec-2099.","source_to_concept_map" -"invalid_reason","No","VARCHAR(1)","Reason the mapping instance was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.","source_to_concept_map" -"vocabulary_id","Yes","VARCHAR(20)","A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit.","vocabulary" -"vocabulary_name","Yes","VARCHAR(255)","The name describing the vocabulary, for example ""International Classification of Diseases, Ninth Revision, Clinical Modification, Volume 1 and 2 (NCHS)"" etc.","vocabulary" -"vocabulary_reference","Yes","VARCHAR(255)","External reference to documentation or available download of the about the vocabulary.","vocabulary" -"vocabulary_version","No","VARCHAR(255)","Version of the Vocabulary as indicated in the source.","vocabulary" -"vocabulary_concept_id","Yes","INTEGER","A foreign key that refers to a standard concept identifier in the CONCEPT table for the Vocabulary the VOCABULARY record belongs to.","vocabulary" diff --git a/docs/reviewProposals.html b/docs/reviewProposals.html new file mode 100644 index 0000000..b2e64f7 --- /dev/null +++ b/docs/reviewProposals.html @@ -0,0 +1,417 @@ + + + + + + + + + + + + + +CDM Proposals Under Review + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + + + + + + + + + + + + + + + + + + +

    This page is still in development. For a list of all proposals currently under review please see the github issue log.

    + + + + +
    + + + + + + + +
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -489,7 +530,6 @@ person_id A unique identifier for each person. -NA integer @@ -504,13 +544,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -542,7 +578,6 @@ CONCEPT Gender -NA
    -NA integer @@ -568,13 +602,10 @@ No No -NA -NA -NA
    -NA integer @@ -600,13 +630,10 @@ No No -NA -NA -NA
    -NA integer @@ -632,13 +658,10 @@ No No -NA -NA -NA
    -NA datetime @@ -664,13 +686,10 @@ No No -NA -NA -NA
    -NA datetime @@ -696,13 +714,10 @@ No No -NA -NA -NA
    -NA integer @@ -734,7 +748,6 @@ CONCEPT Race -NA
    -NA integer @@ -766,7 +778,6 @@ CONCEPT Ethnicity -NA
    -NA integer @@ -795,10 +805,8 @@ Yes LOCATION -NA -NA
    -NA integer @@ -827,10 +834,8 @@ Yes PROVIDER -NA -NA
    -NA integer @@ -859,10 +863,8 @@ Yes CARE_SITE -NA -NA
    -NA varchar(50) @@ -888,13 +889,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -920,13 +917,10 @@ No No -NA -NA -NA
    -NA Integer @@ -955,10 +948,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -984,13 +974,10 @@ No No -NA -NA -NA
    -NA Integer @@ -1019,10 +1005,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -1048,13 +1031,10 @@ No No -NA -NA -NA
    -NA Integer @@ -1083,10 +1062,8 @@ Yes CONCEPT -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -1138,7 +1115,6 @@ observation_period_id A unique identifier for each observation period. -NA integer @@ -1153,13 +1129,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -1188,10 +1160,8 @@ Yes PERSON -NA -NA
    -NA date @@ -1217,13 +1186,10 @@ No No -NA -NA -NA
    -NA date @@ -1249,13 +1214,10 @@ No No -NA -NA -NA
    -NA Integer @@ -1287,7 +1248,6 @@ CONCEPT Type Concept -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -1339,7 +1299,6 @@ visit_occurrence_id A unique identifier for each Person’’s visit or encounter at a healthcare provider. -NA integer @@ -1354,13 +1313,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -1389,10 +1344,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -1424,7 +1376,6 @@ CONCEPT Visit -NA
    -NA date @@ -1450,13 +1400,10 @@ No No -NA -NA -NA
    -NA datetime @@ -1482,13 +1428,10 @@ No No -NA -NA -NA
    -NA date @@ -1514,13 +1456,10 @@ No No -NA -NA -NA
    -NA datetime @@ -1546,13 +1484,10 @@ No No -NA -NA -NA
    -NA Integer @@ -1584,7 +1518,6 @@ CONCEPT Type Concept -NA
    -NA integer @@ -1613,10 +1545,8 @@ No PROVIDER -NA -NA
    -NA integer @@ -1645,10 +1574,8 @@ No CARE_SITE -NA -NA
    -NA varchar(50) @@ -1674,13 +1600,10 @@ No No -NA -NA -NA
    -NA integer @@ -1709,10 +1631,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -1741,10 +1660,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -1770,13 +1686,10 @@ No No -NA -NA -NA
    -NA integer @@ -1805,10 +1717,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -1834,13 +1743,10 @@ No No -NA -NA -NA
    -NA integer @@ -1869,10 +1774,8 @@ Yes VISIT_OCCURRENCE -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -1924,7 +1827,6 @@ condition_occurrence_id A unique identifier for each Condition Occurrence event. -NA bigint @@ -1939,13 +1841,10 @@ Yes No -NA -NA -NA
    -NA bigint @@ -1974,10 +1872,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -2009,7 +1904,6 @@ CONCEPT Condition -NA
    -NA date @@ -2035,13 +1928,10 @@ No No -NA -NA -NA
    -NA datetime @@ -2067,13 +1956,10 @@ No No -NA -NA -NA
    -NA date @@ -2099,13 +1984,10 @@ No No -NA -NA -NA
    -NA datetime @@ -2131,13 +2012,10 @@ No No -NA -NA -NA
    -NA integer @@ -2169,7 +2046,6 @@ CONCEPT Type Concept -NA
    -NA integer @@ -2198,10 +2073,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(20) @@ -2227,13 +2099,10 @@ No No -NA -NA -NA
    -NA integer @@ -2262,10 +2130,8 @@ Yes PROVIDER -NA -NA
    -NA integer @@ -2294,10 +2159,8 @@ Yes VISIT_OCCURRENCE -NA -NA
    -NA integer @@ -2326,10 +2188,8 @@ Yes VISIT_DETAIL -NA -NA
    -NA varchar(50) @@ -2355,13 +2214,10 @@ No No -NA -NA -NA
    -NA integer @@ -2390,10 +2245,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -2419,13 +2271,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -2477,7 +2326,6 @@ drug_exposure_id A system-generated unique identifier for each Drug utilization event. -NA bigint @@ -2492,13 +2340,10 @@ Yes No -NA -NA -NA
    -NA bigint @@ -2527,10 +2371,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -2562,7 +2403,6 @@ CONCEPT Drug -NA
    -NA date @@ -2588,13 +2427,10 @@ No No -NA -NA -NA
    -NA datetime @@ -2620,13 +2455,10 @@ No No -NA -NA -NA
    -NA date @@ -2652,13 +2483,10 @@ No No -NA -NA -NA
    -NA datetime @@ -2684,13 +2511,10 @@ No No -NA -NA -NA
    -NA date @@ -2716,13 +2539,10 @@ No No -NA -NA -NA
    -NA integer @@ -2754,7 +2573,6 @@ CONCEPT Type Concept -NA
    -NA varchar(20) @@ -2780,13 +2597,10 @@ No No -NA -NA -NA
    -NA integer @@ -2812,13 +2625,10 @@ No No -NA -NA -NA
    -NA float @@ -2844,13 +2653,10 @@ No No -NA -NA -NA
    -NA integer @@ -2876,13 +2681,10 @@ No No -NA -NA -NA
    -NA varchar(MAX) @@ -2908,13 +2709,10 @@ No No -NA -NA -NA
    -NA integer @@ -2943,10 +2740,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -2972,13 +2766,10 @@ No No -NA -NA -NA
    -NA integer @@ -3007,10 +2797,8 @@ Yes PROVIDER -NA -NA
    -NA integer @@ -3039,10 +2826,8 @@ Yes VISIT_OCCURRENCE -NA -NA
    -NA integer @@ -3071,10 +2855,8 @@ Yes VISIT_DETAIL -NA -NA
    -NA varchar(50) @@ -3100,13 +2881,10 @@ No No -NA -NA -NA
    -NA integer @@ -3135,10 +2912,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -3164,13 +2938,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -3196,13 +2966,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -3254,7 +3021,6 @@ procedure_occurrence_id A system-generated unique identifier for each Procedure Occurrence. -NA integer @@ -3269,13 +3035,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -3304,10 +3066,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -3339,7 +3098,6 @@ CONCEPT Procedure -NA
    -NA date @@ -3365,13 +3122,10 @@ No No -NA -NA -NA
    -NA datetime @@ -3397,13 +3150,10 @@ No No -NA -NA -NA
    -NA integer @@ -3435,7 +3184,6 @@ CONCEPT Type Concept -NA
    -NA integer @@ -3464,10 +3211,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -3493,13 +3237,10 @@ No No -NA -NA -NA
    -NA integer @@ -3528,10 +3268,8 @@ No PROVIDER -NA -NA
    -NA integer @@ -3560,10 +3297,8 @@ No VISIT_OCCURRENCE -NA -NA
    -NA integer @@ -3592,10 +3326,8 @@ No VISIT_DETAIL -NA -NA
    -NA varchar(50) @@ -3621,13 +3352,10 @@ No No -NA -NA -NA
    -NA integer @@ -3656,10 +3383,8 @@ No CONCEPT -NA -NA
    -NA varchar(50) @@ -3685,13 +3409,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -3743,7 +3464,6 @@ device_exposure_id A system-generated unique identifier for each Device Exposure. -NA bigint @@ -3758,13 +3478,10 @@ Yes No -NA -NA -NA
    -NA bigint @@ -3793,10 +3509,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -3828,7 +3541,6 @@ CONCEPT Device -NA
    -NA date @@ -3854,13 +3565,10 @@ No No -NA -NA -NA
    -NA datetime @@ -3886,13 +3593,10 @@ No No -NA -NA -NA
    -NA date @@ -3918,13 +3621,10 @@ No No -NA -NA -NA
    -NA datetime @@ -3950,13 +3649,10 @@ No No -NA -NA -NA
    -NA integer @@ -3988,7 +3683,6 @@ CONCEPT Type Concept -NA
    -NA varchar(50) @@ -4014,13 +3707,10 @@ No No -NA -NA -NA
    -NA integer @@ -4046,13 +3735,10 @@ No No -NA -NA -NA
    -NA integer @@ -4081,10 +3766,8 @@ Yes PROVIDER -NA -NA
    -NA integer @@ -4113,10 +3795,8 @@ Yes VISIT_OCCURRENCE -NA -NA
    -NA integer @@ -4145,10 +3824,8 @@ Yes VISIT_DETAIL -NA -NA
    -NA varchar(50) @@ -4174,13 +3850,10 @@ No No -NA -NA -NA
    -NA integer @@ -4209,10 +3881,8 @@ Yes CONCEPT -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -4264,7 +3934,6 @@ measurement_id A unique identifier for each Measurement. -NA integer @@ -4279,13 +3948,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -4314,10 +3979,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -4349,7 +4011,6 @@ CONCEPT Measurement -NA
    -NA date @@ -4375,13 +4035,10 @@ No No -NA -NA -NA
    -NA datetime @@ -4407,13 +4063,10 @@ No No -NA -NA -NA
    -NA varchar(10) @@ -4439,13 +4091,10 @@ No No -NA -NA -NA
    -NA integer @@ -4477,7 +4125,6 @@ CONCEPT Type Concept -NA
    -NA integer @@ -4506,10 +4152,8 @@ Yes CONCEPT -NA -NA
    -NA float @@ -4535,13 +4178,10 @@ No No -NA -NA -NA
    -NA integer @@ -4570,10 +4209,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -4605,7 +4241,6 @@ CONCEPT Unit -NA
    -NA float @@ -4631,13 +4265,10 @@ No No -NA -NA -NA
    -NA float @@ -4663,13 +4293,10 @@ No No -NA -NA -NA
    -NA integer @@ -4698,10 +4324,8 @@ Yes PROVIDER -NA -NA
    -NA integer @@ -4730,10 +4353,8 @@ Yes VISIT_OCCURRENCE -NA -NA
    -NA integer @@ -4762,10 +4382,8 @@ Yes VISIT_DETAIL -NA -NA
    -NA varchar(50) @@ -4791,13 +4408,10 @@ No No -NA -NA -NA
    -NA integer @@ -4826,10 +4439,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -4855,13 +4465,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -4887,13 +4493,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -4945,7 +4548,6 @@ visit_detail_id A unique identifier for each Person’s visit or encounter at a healthcare provider. -NA integer @@ -4960,13 +4562,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -4995,10 +4593,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -5030,7 +4625,6 @@ CONCEPT Visit -NA
    -NA date @@ -5056,13 +4649,10 @@ No No -NA -NA -NA
    -NA datetime @@ -5088,13 +4677,10 @@ No No -NA -NA -NA
    -NA date @@ -5120,13 +4705,10 @@ No No -NA -NA -NA
    -NA datetime @@ -5152,13 +4733,10 @@ No No -NA -NA -NA
    -NA Integer @@ -5184,13 +4761,10 @@ No Yes -NA -NA -NA
    -NA integer @@ -5219,10 +4792,8 @@ Yes PROVIDER -NA -NA
    -NA integer @@ -5251,10 +4821,8 @@ Yes CARE_SITE -NA -NA
    -NA string(50) @@ -5280,13 +4847,10 @@ No No -NA -NA -NA
    -NA Integer @@ -5315,10 +4878,8 @@ Yes CONCEPT -NA -NA
    -NA Varchar(50) @@ -5344,13 +4904,10 @@ No No -NA -NA -NA
    -NA Integer @@ -5379,10 +4935,8 @@ Yes CONCEPT -NA -NA
    -NA Varchar(50) @@ -5408,13 +4961,10 @@ No No -NA -NA -NA
    -NA Integer @@ -5443,10 +4992,8 @@ Yes CONCEPT -NA -NA
    -NA Integer @@ -5475,10 +5021,8 @@ Yes VISIT_DETAIL -NA -NA
    -NA Integer @@ -5507,10 +5050,8 @@ Yes VISIT_DETAIL -NA -NA
    -NA Integer @@ -5539,10 +5079,8 @@ Yes VISIT_OCCURRENCE -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -5594,7 +5132,6 @@ note_id A unique identifier for each note. -NA integer @@ -5609,13 +5146,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -5644,10 +5177,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -5673,13 +5203,10 @@ No No -NA -NA -NA
    -NA integer @@ -5708,10 +5234,8 @@ No CONCEPT -NA -NA
    -NA date @@ -5737,13 +5260,10 @@ No No -NA -NA -NA
    -NA datetime @@ -5769,13 +5288,10 @@ No No -NA -NA -NA
    -NA integer @@ -5807,7 +5322,6 @@ CONCEPT Type Concept -NA
    -NA integer @@ -5836,10 +5349,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(250) @@ -5865,13 +5375,10 @@ No No -NA -NA -NA
    -NA varchar(MAX) @@ -5897,13 +5403,10 @@ No No -NA -NA -NA
    -NA integer @@ -5932,10 +5434,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -5964,10 +5463,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -5993,13 +5489,10 @@ No Yes -NA -NA -NA
    -NA integer @@ -6028,10 +5520,8 @@ Yes VISIT_OCCURRENCE -NA -NA
    -NA integer @@ -6060,10 +5549,8 @@ Yes VISIT_DETAIL -NA -NA
    -NA varchar(50) @@ -6089,13 +5575,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -6147,7 +5630,6 @@ note_nlp_id A unique identifier for each term extracted from a note. -NA integer @@ -6162,13 +5644,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -6194,13 +5672,10 @@ No No -NA -NA -NA
    -NA integer @@ -6229,10 +5703,8 @@ Yes NOTE -NA -NA
    -NA varchar(250) @@ -6258,13 +5729,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -6290,13 +5757,10 @@ No No -NA -NA -NA
    -NA varchar(250) @@ -6322,13 +5785,10 @@ No No -NA -NA -NA
    -NA integer @@ -6357,10 +5816,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -6389,10 +5845,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(250) @@ -6418,13 +5871,10 @@ No No -NA -NA -NA
    -NA date @@ -6450,13 +5899,10 @@ No No -NA -NA -NA
    -NA datetime @@ -6482,13 +5927,10 @@ No No -NA -NA -NA
    -NA varchar(1) @@ -6514,13 +5955,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -6546,13 +5983,10 @@ No No -NA -NA -NA
    -NA varchar(2000) @@ -6578,13 +6011,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -6636,7 +6066,6 @@ SURVEY_CONDUCT_ID Unique identifier for each completed survey. -NA integer @@ -6651,13 +6080,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -6686,10 +6111,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -6718,10 +6140,8 @@ Yes CONCEPT -NA -NA
    -NA date @@ -6747,13 +6166,10 @@ No No -NA -NA -NA
    -NA datetime @@ -6779,13 +6194,10 @@ No No -NA -NA -NA
    -NA date @@ -6811,13 +6222,10 @@ No No -NA -NA -NA
    -NA datetime @@ -6843,13 +6250,10 @@ No No -NA -NA -NA
    -NA integer @@ -6878,10 +6281,8 @@ Yes PROVIDER -NA -NA
    -NA integer @@ -6907,13 +6307,10 @@ No Yes -NA -NA -NA
    -NA integer @@ -6942,10 +6338,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -6971,13 +6364,10 @@ No Yes -NA -NA -NA
    -NA integer @@ -7006,10 +6395,8 @@ No CONCEPT -NA -NA
    -NA varchar(50) @@ -7035,13 +6421,10 @@ No No -NA -NA -NA
    -NA varchar(100) @@ -7067,13 +6449,10 @@ No No -NA -NA -NA
    -NA varchar(100) @@ -7099,13 +6477,10 @@ No No -NA -NA -NA
    -NA varchar(100) @@ -7131,13 +6505,10 @@ No No -NA -NA -NA
    -NA varchar(100) @@ -7163,13 +6533,10 @@ No No -NA -NA -NA
    -NA integer @@ -7198,10 +6564,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(100) @@ -7227,13 +6590,10 @@ No No -NA -NA -NA
    -NA integer @@ -7262,10 +6621,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -7291,13 +6647,10 @@ No No -NA -NA -NA
    -NA varchar(20) @@ -7323,13 +6675,10 @@ No No -NA -NA -NA
    -NA integer @@ -7358,10 +6706,8 @@ Yes VISIT_OCCURRENCE -NA -NA
    -NA integer @@ -7390,10 +6735,8 @@ Yes VISIT_OCCURRENCE -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -7445,7 +6788,6 @@ observation_id A unique identifier for each observation. -NA integer @@ -7460,13 +6802,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -7495,10 +6833,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -7527,10 +6862,8 @@ Yes CONCEPT -NA -NA
    -NA date @@ -7556,13 +6888,10 @@ No No -NA -NA -NA
    -NA datetime @@ -7588,13 +6916,10 @@ No No -NA -NA -NA
    -NA integer @@ -7626,7 +6950,6 @@ CONCEPT Type Concept -NA
    -NA float @@ -7652,13 +6974,10 @@ No No -NA -NA -NA
    -NA varchar(60) @@ -7684,13 +7002,10 @@ No No -NA -NA -NA
    -NA Integer @@ -7719,10 +7033,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -7751,10 +7062,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -7786,7 +7094,6 @@ CONCEPT Unit -NA
    -NA integer @@ -7815,10 +7121,8 @@ Yes PROVIDER -NA -NA
    -NA integer @@ -7847,10 +7150,8 @@ Yes VISIT_OCCURRENCE -NA -NA
    -NA integer @@ -7879,10 +7179,8 @@ Yes VISIT_DETAIL -NA -NA
    -NA varchar(50) @@ -7908,13 +7205,10 @@ No No -NA -NA -NA
    -NA integer @@ -7943,10 +7236,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -7972,13 +7262,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -8004,13 +7290,10 @@ No No -NA -NA -NA
    -NA integer @@ -8036,13 +7318,10 @@ No No -NA -NA -NA
    -NA integer @@ -8071,10 +7349,8 @@ Yes CONCEPT -NA -NA
    -NA datetime @@ -8100,13 +7375,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -8158,7 +7430,6 @@ specimen_id A unique identifier for each specimen. -NA integer @@ -8173,13 +7444,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -8208,10 +7475,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -8240,10 +7504,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -8275,7 +7536,6 @@ CONCEPT Type Concept -NA
    -NA date @@ -8301,13 +7560,10 @@ No No -NA -NA -NA
    -NA datetime @@ -8333,13 +7588,10 @@ No No -NA -NA -NA
    -NA float @@ -8365,13 +7616,10 @@ No No -NA -NA -NA
    -NA integer @@ -8400,10 +7647,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -8432,10 +7676,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -8464,10 +7705,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -8493,13 +7731,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -8525,13 +7759,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -8557,13 +7787,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -8589,13 +7815,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -8621,13 +7843,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -8679,7 +7898,6 @@ domain_concept_id_1 The concept representing the domain of fact one, from which the corresponding table can be inferred. -NA integer @@ -8697,10 +7915,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -8726,13 +7941,10 @@ No No -NA -NA -NA
    -NA integer @@ -8761,10 +7972,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -8790,13 +7998,10 @@ No No -NA -NA -NA
    -NA integer @@ -8825,10 +8029,8 @@ Yes CONCEPT -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -8880,7 +8082,6 @@ location_id A unique identifier for each geographic location. -NA integer @@ -8895,13 +8096,10 @@ Yes No -NA -NA -NA
    -NA varchar(50) @@ -8927,13 +8124,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -8959,13 +8152,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -8991,13 +8180,10 @@ No No -NA -NA -NA
    -NA varchar(2) @@ -9023,13 +8208,10 @@ No No -NA -NA -NA
    -NA varchar(9) @@ -9055,13 +8236,10 @@ No No -NA -NA -NA
    -NA varchar(20) @@ -9087,13 +8264,10 @@ No No -NA -NA -NA
    -NA varchar(100) @@ -9119,13 +8292,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -9151,13 +8320,10 @@ No No -NA -NA -NA
    -NA float @@ -9183,13 +8348,10 @@ No No -NA -NA -NA
    -NA float @@ -9215,13 +8376,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -9273,7 +8431,6 @@ location_id A foreign key to the location table. -NA integer @@ -9291,10 +8448,8 @@ Yes LOCATION -NA -NA
    -NA varchar(50) @@ -9323,10 +8477,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -9352,13 +8503,10 @@ No No -NA -NA -NA
    -NA integer @@ -9384,13 +8531,10 @@ No No -NA -NA -NA
    -NA date @@ -9416,13 +8559,10 @@ No No -NA -NA -NA
    -NA date @@ -9448,13 +8587,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -9506,7 +8642,6 @@ care_site_id A unique identifier for each Care Site. -NA integer @@ -9521,13 +8656,10 @@ Yes No -NA -NA -NA
    -NA varchar(255) @@ -9553,13 +8684,10 @@ No No -NA -NA -NA
    -NA integer @@ -9588,10 +8715,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -9617,13 +8741,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -9649,13 +8769,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -9681,13 +8797,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -9739,7 +8852,6 @@ provider_id A unique identifier for each Provider. -NA integer @@ -9754,13 +8866,10 @@ Yes No -NA -NA -NA
    -NA varchar(255) @@ -9786,13 +8894,10 @@ No No -NA -NA -NA
    -NA varchar(20) @@ -9818,13 +8922,10 @@ No No -NA -NA -NA
    -NA varchar(20) @@ -9850,13 +8950,10 @@ No No -NA -NA -NA
    -NA integer @@ -9885,10 +8981,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -9917,10 +9010,8 @@ Yes CARE_SITE -NA -NA
    -NA integer @@ -9946,13 +9036,10 @@ No No -NA -NA -NA
    -NA integer @@ -9984,7 +9070,6 @@ CONCEPT Gender -NA
    -NA varchar(50) @@ -10010,13 +9094,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -10042,13 +9122,10 @@ No No -NA -NA -NA
    -NA integer @@ -10077,10 +9153,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -10106,13 +9179,10 @@ No No -NA -NA -NA
    -NA integer @@ -10141,10 +9210,8 @@ Yes CONCEPT -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -10196,7 +9263,6 @@ payer_plan_period_id A identifier for each unique combination of payer, plan, family code and time span. -NA integer @@ -10214,10 +9280,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -10246,10 +9309,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -10275,13 +9335,10 @@ No No -NA -NA -NA
    -NA date @@ -10307,13 +9363,10 @@ No No -NA -NA -NA
    -NA date @@ -10339,13 +9391,10 @@ No No -NA -NA -NA
    -NA integer @@ -10374,10 +9422,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -10403,13 +9448,10 @@ No No -NA -NA -NA
    -NA integer @@ -10438,10 +9479,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -10470,10 +9508,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -10499,13 +9534,10 @@ No No -NA -NA -NA
    -NA integer @@ -10534,10 +9565,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -10566,10 +9594,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -10595,13 +9620,10 @@ No No -NA -NA -NA
    -NA integer @@ -10630,10 +9651,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -10662,10 +9680,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -10691,13 +9706,10 @@ No No -NA -NA -NA
    -NA integer @@ -10726,10 +9737,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -10755,13 +9763,10 @@ No No -NA -NA -NA
    -NA integer @@ -10790,10 +9794,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -10819,13 +9820,10 @@ No No -NA -NA -NA
    -NA integer @@ -10854,10 +9851,8 @@ Yes CONCEPT -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -10909,7 +9904,6 @@ cost_id A unique identifier for each COST record. -NA integer @@ -10924,13 +9918,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -10959,10 +9949,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -10988,13 +9975,10 @@ No No -NA -NA -NA
    -NA integer @@ -11023,10 +10006,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -11055,10 +10035,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -11087,10 +10064,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -11119,10 +10093,8 @@ Yes CONCEPT -NA -NA
    -NA varchar(50) @@ -11148,13 +10119,10 @@ No No -NA -NA -NA
    -NA integer @@ -11183,10 +10150,8 @@ Yes CONCEPT -NA -NA
    -NA float @@ -11212,13 +10176,10 @@ No No -NA -NA -NA
    -NA date @@ -11244,13 +10204,10 @@ No No -NA -NA -NA
    -NA date @@ -11276,13 +10232,10 @@ No No -NA -NA -NA
    -NA date @@ -11308,13 +10260,10 @@ No No -NA -NA -NA
    -NA integer @@ -11343,10 +10291,8 @@ Yes CONCEPT -NA -NA
    -NA integer @@ -11372,13 +10317,10 @@ No Yes -NA -NA -NA
    -NA varchar(50) @@ -11404,13 +10345,10 @@ No No -NA -NA -NA
    -NA varchar(50) @@ -11436,13 +10373,10 @@ No No -NA -NA -NA
    -NA integer @@ -11468,13 +10401,10 @@ No Yes -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -11526,7 +10456,6 @@ drug_era_id A unique identifier for each Drug Era. -NA integer @@ -11541,13 +10470,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -11576,10 +10501,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -11622,7 +10544,6 @@ drug_era_start_datetime The start date for the Drug Era constructed from the individual instances of Drug Exposures. It is the start date of the very first chronologically recorded instance of conutilization of a Drug. -NA datetime @@ -11637,13 +10558,10 @@ No No -NA -NA -NA
    -NA datetime @@ -11669,13 +10586,10 @@ No No -NA -NA -NA
    -NA integer @@ -11701,13 +10614,10 @@ No No -NA -NA -NA
    -NA integer @@ -11733,13 +10642,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -11791,7 +10697,6 @@ dose_era_id A unique identifier for each Dose Era. -NA integer @@ -11806,13 +10711,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -11841,10 +10742,8 @@ Yes PERSON -NA -NA
    -NA integer @@ -11887,7 +10785,6 @@ unit_concept_id A foreign key that refers to a Standard Concept identifier in the Standardized Vocabularies for the unit concept. -NA integer @@ -11908,7 +10805,6 @@ CONCEPT Unit -NA
    -NA float @@ -11934,13 +10829,10 @@ No No -NA -NA -NA
    -NA datetime @@ -11966,13 +10857,10 @@ No No -NA -NA -NA
    -NA datetime @@ -11998,13 +10885,10 @@ No No -NA -NA -NA
    -Is Required +Required -Is Primary Key +Primary Key -Is Foreign Key (FK) +Foreign Key (FK) FK Table @@ -12056,7 +10940,6 @@ condition_era_id A unique identifier for each Condition Era. -NA integer @@ -12071,13 +10954,10 @@ Yes No -NA -NA -NA
    -NA integer @@ -12106,10 +10985,8 @@ No PERSON -NA -NA
    -NA integer @@ -12141,7 +11017,6 @@ CONCEPT Condition -NA
    -NA datetime @@ -12167,13 +11041,10 @@ No No -NA -NA -NA
    -NA datetime @@ -12199,13 +11069,10 @@ No No -NA -NA -NA
    -NA integer @@ -12231,13 +11097,10 @@ No No -NA -NA -NA