documentation:cdm:observation
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| documentation:cdm:observation [2016/06/04 06:05] – cgreich | documentation:cdm:observation [2017/09/25 15:02] (current) – clairblacketer | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== OBSERVATION table ===== | ===== OBSERVATION table ===== | ||
| + | **THIS IS OUTDATED. All documentation is now on the [[https:// | ||
| + | |||
| + | This table changed in version 5.1 of the OMOP CDM. The field observation_datetime was added. | ||
| + | |||
| + | ----- | ||
| + | |||
| The OBSERVATION table captures clinical facts about a Person obtained in the context of examination, | The OBSERVATION table captures clinical facts about a Person obtained in the context of examination, | ||
| ^Field^Required^Type^Description^ | ^Field^Required^Type^Description^ | ||
| Line 6: | Line 12: | ||
| |observation_concept_id|Yes|integer|A foreign key to the standard observation concept identifier in the Standardized Vocabularies.| | |observation_concept_id|Yes|integer|A foreign key to the standard observation concept identifier in the Standardized Vocabularies.| | ||
| |observation_date|Yes|date|The date of the observation.| | |observation_date|Yes|date|The date of the observation.| | ||
| - | |observation_time|No|time|The time of the observation.| | + | |observation_datetime|No|datetime|The date and time of the 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_type_concept_id|Yes|integer|A foreign key to the predefined concept identifier in the Standardized Vocabularies reflecting the type of the 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.| | |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.| | ||
| Line 20: | Line 26: | ||
| |qualifier_source_value|No|varchar(50)|The source value associated with a qualifier to characterize the observation| | |qualifier_source_value|No|varchar(50)|The source value associated with a qualifier to characterize the observation| | ||
| ==== Conventions ==== | ==== Conventions ==== | ||
| - | * Observations differ from Measurements in that they do not require a standardized test or some other activity to generate clinical fact. Typical observations are medical history, family history, the stated need for certain treatment, social circumstances, | + | * Observations differ from Measurements in that they do not require a standardized test or some other activity to generate clinical fact. Typical observations are medical history, family history, the stated need for certain treatment, social circumstances, |
| - | * Valid Observation Concepts are not enforced to be from any domain. They still should be Standard Concepts, and they typically belong to the 'Observation' | + | * Valid Observation Concepts are not enforced to be from any domain. They still should be Standard Concepts, and they typically belong to the "Observation" |
| * Observation can be stored as attribute value pairs, with the attribute as the Observation Concept and the value representing the clinical fact. This fact can be a Concept (stored in value_as_concept), | * Observation can be stored as attribute value pairs, with the attribute as the Observation Concept and the value representing the clinical fact. This fact can be a Concept (stored in value_as_concept), | ||
| - | * It is recommended for observations that are suggestive statements of positive assertion should have a value of 'Yes' | + | * It is recommended for observations that are suggestive statements of positive assertion should have a value of "Yes" |
| - | * Valid Concepts of the value_as_concept field are not enforced, but typically belong to the 'Meas Value' | + | * Valid Concepts of the value_as_concept field are not enforced, but typically belong to the "Meas Value" |
| * For numerical facts a Unit can be provided in the unit_concept_id. | * For numerical facts a Unit can be provided in the unit_concept_id. | ||
| * For facts represented as Concepts no domain membership is enforced. | * For facts represented as Concepts no domain membership is enforced. | ||
| - | * 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 | + | * 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" |
| * The qualifier_concept_id field contains all attributes specifying the clinical fact further, such as as degrees, severities, drug-drug interaction alerts etc. | * The qualifier_concept_id field contains all attributes specifying the clinical fact further, such as as degrees, severities, drug-drug interaction alerts etc. | ||
| * The Visit during which the observation was made is recorded through a reference to the VISIT_OCCURRENCE table. This information is not always available. | * The Visit during which the observation was made is recorded through a reference to the VISIT_OCCURRENCE table. This information is not always available. | ||
| * The Provider making the observation is recorded through a reference to the PROVIDER table. This information is not always available. | * The Provider making the observation is recorded through a reference to the PROVIDER table. This information is not always available. | ||
| - | |||
documentation/cdm/observation.1465020331.txt.gz · Last modified: by cgreich
