Differences

This shows you the differences between two versions of the page.

--- documentation:cdm:cohort_definition [2014/11/17 18:40] – created cgreich
+++ documentation:cdm:cohort_definition [2017/09/25 14:59] (current) – clairblacketer
@@ Line 1: / Line 1: @@
 ===== COHORT_DEFINITION table =====
+**THIS IS OUTDATED. All documentation is now on the [[https://github.com/OHDSI/CommonDataModel/wiki|github wiki]]. Please refer there or to the [[projects:workgroups:cdm-wg|CDM working group]] for more information**
 The COHORT_DEFINITION table contains records defining a Cohort derived from the data through the associated description and syntax and upon instantiation (execution of the algorithm) placed into the COHORT table. Cohorts are a set of subjects that satisfy a given combination of inclusion criteria for a duration of time. The COHORT_DEFINITION table provides a standardized structure for maintaining the rules governing the inclusion of a subject into a cohort, and can store operational programming code to instantiate the cohort within the OMOP Common Data Model.
 ^Field^Required^Type^Description^
-^cohort_definition_id^Yes^integer^A unique identifier for each Cohort.^
+|cohort_definition_id|Yes|integer|A unique identifier for each Cohort.|
-^cohort_definition_name^Yes^varchar(255)^A short description of the Cohort.^
+|cohort_definition_name|Yes|varchar(255)|A short description of the Cohort.|
-^cohort_definition_description^No^CLOB^A complete description of the Cohort definition^
+|cohort_definition_description|No|CLOB|A complete description of the Cohort definition|
-^definition_type_concept_id^Yes^integer^Type to define what kind of Cohort definition the record represents and how the syntax may be executed^
+|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_syntax^No^CLOB^Syntax to operationalize the Cohort definition^
+|cohort_definition_syntax|No|CLOB|Syntax or code to operationalize the 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).^
+|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_instantiation_date^No^Date^A date to indicate when the Cohort was instantiated in the COHORT table^
+|cohort_instantiation_date|No|Date|A date to indicate when the Cohort was instantiated in the COHORT table|
 ==== Conventions ====
-  * The cohort_definition_syntax does not define the used syntax. It can be SQL, a cohort definition language, or a free-text description of the algorithm.
+  * The cohort_definition_syntax does not prescribe any specific syntax or programming language. Typically, it would be any flavor SQL, a cohort definition language, or a free-text description of the algorithm.
-  * The subject_cocnept_id determines what the individual subjects or entities of the cohort consists of. In most cases, that would be a person (patient). But cohorts could be constructed for providers, visits and any other domain. Note that the domain is not codified using the alphanumerical domain_id like in the CONCEPT table. Instead, the corresponding Concept is used. The Concepts for each domain can be obtained from the DOMAIN table in the domain_concept_id.
+  * The subject_concept_id determines what the individual subjects or entities of the Cohort consists of. In most cases, that would be a Person (patient). But cohorts could also be constructed for Providers, Visits or any other Domain. Note that the Domain is not codified using the alphanumerical domain_id like in the CONCEPT table. Instead, the corresponding Concept is used. The Concepts for each domain can be obtained from the DOMAIN table in the domain_concept_id.
-~~DISQUS~~