User Tools

Site Tools


documentation:cdm:observation

Differences

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

Link to this comparison view

Next revision
Previous revision
documentation:cdm:observation [2014/12/05 20:44]
cgreich created
documentation:cdm:observation [2017/09/25 15:02] (current)
clairblacketer
Line 1: Line 1:
 ===== OBSERVATION table ===== ===== OBSERVATION table =====
-The Observation ​table captures clinical facts about a Person obtained in the context of examination,​ questioning or a procedure. Any data that cannot be represented by any other domains, such as social and lifestyle facts, medical history, family history, etc. are recorded here.+**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** 
 + 
 +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,​ questioning or a procedure. Any data that cannot be represented by any other domains, such as social and lifestyle facts, medical history, family history, etc. are recorded here.
 ^Field^Required^Type^Description^ ^Field^Required^Type^Description^
 |observation_id|Yes|integer|A unique identifier for each observation.| |observation_id|Yes|integer|A unique identifier for each 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.| |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_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,​ lifestyle choices, healthcare utilization patterns, etc. If the generation clinical facts requires a standardized testing such as lab testing or imaging and leeds to a standardized result, the data item is recorded in the MEASUREMENT table. If the clinical fact observed determines a sign, symptom, diagnosis of a disease or other medical condition, it is recorded in the CONDITION_OCCURRENCE table. +  * 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,​ lifestyle choices, healthcare utilization patterns, etc. If the generation clinical facts requires a standardized testing such as lab testing or imaging and leads to a standardized result, the data item is recorded in the MEASUREMENT table. If the clinical fact observed determines a sign, symptom, diagnosis of a disease or other medical condition, it is recorded in the CONDITION_OCCURRENCE table. 
-  * Valid Observation Concepts are not enforced to be from any domain. They still should be Standard Concepts ​(Concepts allowed to be recorded in any field called <​entity>​_concept_id)but they might well be from the Observation domain+  * Valid Observation Concepts are not enforced to be from any domain. They still should be Standard Concepts, ​and they typically belong to the "Observation" or sometimes "​Measurement" ​domain. 
-  * Even though Observations do not have a result, the clinical fact can be stated separately from the type of Observation in the value_as_number and value_as_concept_id fields+  * 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),​ a numerical value (value_as_number) or a verbatim string (value_as_string). Even though Observations do not have an explicit result, the clinical fact can be stated separately from the type of Observation in the value_as_ fields. 
-  * 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),​ a numerical value (value_as_number) or a verbatim string (value_as_string) ​+  * It is recommended for observations that are suggestive statements of positive assertion should have a value of "​Yes"​ (concept_id=4188539),​ recorded, even though the null value is the equivalent.  
 +  * Valid Concepts of the value_as_concept field are not enforced, but typically belong to the "Meas Value" domain.
   * 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. 
-  * Observations ​which appear ​to be suggestive statements ​of positive assertion might have recorded value_as_concept ​of ‘Yes’ (concept_id=),​ such as . This is equivalent ​to an empty valid_as_concept field+  * 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 "Maps to" relationship to 4167217 "​Family history ​of clinical finding" ​as well as a "Maps to value" record ​to 317009 "​Asthma"​.
   * 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.1417812261.txt.gz · Last modified: 2014/12/05 20:44 by cgreich