User Tools

Site Tools


documentation:cdm:cohort_attribute

Differences

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

Link to this comparison view

Next revision Both sides next revision
documentation:cdm:cohort_attribute [2014/12/05 21:08]
cgreich created
documentation:cdm:cohort_attribute [2015/01/05 16:39]
cgreich
Line 10: Line 10:
 |value_as_concept_id|No|integer|The attribute result stored as a Concept ID. This is applicable to attributes where the result is expressed as a categorical value.| |value_as_concept_id|No|integer|The attribute result stored as a Concept ID. This is applicable to attributes where the result is expressed as a categorical value.|
 ==== Conventions ==== ==== Conventions ====
-  * The core of a Cohort Attribute is the unifying definition or feature of the Cohort. This is captured in the cohort_definition_id. ​+  * Like with Cohorts, ​the unifying definition or feature of any Cohort ​Attribute ​is captured in the cohort_definition_id. ​
   * Cohort Attribute records must have a Start Date   * Cohort Attribute records must have a Start Date
   * Cohort Attribute records must have an End Date, but may be set to Start Date or could apply a censored date using the Observation Period Start Date.   * Cohort Attribute records must have an End Date, but may be set to Start Date or could apply a censored date using the Observation Period Start Date.
   * Cohort Attribute records must contain a Subject ID, which can refer to a Person, Provider, or Visit record. The cohort definition will define the type of subject through the subject concept id.   * Cohort Attribute records must contain a Subject ID, which can refer to a Person, Provider, or Visit record. The cohort definition will define the type of subject through the subject concept id.
  
documentation/cdm/cohort_attribute.txt ยท Last modified: 2017/09/25 15:09 by clairblacketer