This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
documentation:cdm:cohort_attribute [2015/01/05 16:39] cgreich |
documentation:cdm:cohort_attribute [2015/01/05 16:45] 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 ==== | ||
- | * Like with Cohorts, the unifying definition or feature of any Cohort Attribute is captured in the cohort_definition_id. | + | * Each record in the COHORT_ATTRIBUTE table is linked to a specific record in the COHORT table, identified by matching cohort_definition_id, subject_id, cohort_start_date and cohort_end_date fields. |
- | * Cohort Attribute records must have a Start Date | + | * It addes to the records additional information, such as co-variates, scores of disease assessment indices, etc. |
- | * 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. | + | * The unifying definition or feature of the Cohort Attribute is captured in the attribute_definition_id referring to a record in the ATTRIBUTE_DEFINITION table. |
- | * 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. | + | * The actual result or value of the Cohort Attribute (co-variate, index value) is captured in the value_as_number (if the value is numberic) or the value_as_concept_id (if the value is a concept) fields. |