documentation:cdm:measurement
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
documentation:cdm:measurement [2014/12/05 20:43] cgreich created |
documentation:cdm:measurement [2017/09/25 15:02] (current) clairblacketer |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== MEASUREMENT table ===== | ===== MEASUREMENT table ===== | ||
| - | A Measurement is a structured value (numerical or categorical) obtained through systematic and standardized examination or testing of a Person or Person's sample. The Measurement table contains measurement contains both orders and results of such Measurements as laboratory tests, vital signs, quantitative findings from pathology reports, etc. | + | **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 measurement_datetime was added. | ||
| + | |||
| + | ----- | ||
| + | |||
| + | The MEASUREMENT table contains records of Measurement, i.e. structured values (numerical or categorical) obtained through systematic and standardized examination or testing of a Person or Person's sample. The MEASUREMENT table contains both orders and results of such Measurements as laboratory tests, vital signs, quantitative findings from pathology reports, etc. | ||
| ^Field^Required^Type^Description^ | ^Field^Required^Type^Description^ | ||
| |measurement_id|Yes|integer|A unique identifier for each Measurement.| | |measurement_id|Yes|integer|A unique identifier for each Measurement.| | ||
| Line 6: | Line 12: | ||
| |measurement_concept_id|Yes|integer|A foreign key to the standard measurement concept identifier in the Standardized Vocabularies.| | |measurement_concept_id|Yes|integer|A foreign key to the standard measurement concept identifier in the Standardized Vocabularies.| | ||
| |measurement_date|Yes|date|The date of the Measurement.| | |measurement_date|Yes|date|The date of the Measurement.| | ||
| - | |measurement_time|No|time|The time of the Measurement.| | + | |measurement_datetime|No|datetime|The date and time of the Measurement. (Some database systems don't have a datatype of time. To accomodate all temporal analyses, datatype datetime can be used (combining measurement_date and measurement_time)[[http://forums.ohdsi.org/t/date-time-and-datetime-problem-and-the-world-of-hours-and-1day/314|Relevant Forum Discussion]]| |
| |measurement_type_concept_id|Yes|integer|A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the provenance from where the Measurement record was recorded.| | |measurement_type_concept_id|Yes|integer|A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the provenance from where the Measurement record was recorded.| | ||
| |operator_concept_id|No|integer|A foreign key identifier to the predefined Concept in the Standardized Vocabularies reflecting the mathematical operator that is applied to the value_as_number. Operators are <, ≤, =, ≥, >.| | |operator_concept_id|No|integer|A foreign key identifier to the predefined Concept in the Standardized Vocabularies reflecting the mathematical operator that is applied to the value_as_number. Operators are <, ≤, =, ≥, >.| | ||
| Line 19: | Line 25: | ||
| |measurement_source_concept_id|No|integer|A foreign key to a Concept in the Standard Vocabularies that refers to the code used in the source.| | |measurement_source_concept_id|No|integer|A foreign key to a Concept in the Standard Vocabularies that refers to the code used in the source.| | ||
| |unit_source_value|No|varchar(50)|The source code for the unit as it appears in the source data. This code is mapped to a standard unit concept in the Standardized Vocabularies and the original code is stored here for reference.| | |unit_source_value|No|varchar(50)|The source code for the unit as it appears in the source data. This code is mapped to a standard unit concept in the Standardized Vocabularies and the original code is stored here for reference.| | ||
| - | |value_source_value|No|varchar(50)|The source value associated with the content of the value_as_number or value_as_concept as stored in the source data.| | + | |value_source_value|No|varchar(50)|The source value associated with the content of the value_as_number or value_as_concept_id as stored in the source data.| |
| ==== Conventions ==== | ==== Conventions ==== | ||
| - | * Measurements differ from Observations in that they require a standardized test or some other activity to generate a quantitative or qualitative result. For example, However, even though each Measurement requires to have a result, the fields value_as_number and value_as_concept_id are not mandatory. When the result is missing, the Measurement record might represent an order or the result was not captured in the source data (missing data). | + | * Measurements differ from Observations in that they require a standardized test or some other activity to generate a quantitative or qualitative result. For example, LOINC 1755-8 concept_id 3027035 'Albumin [Mass/time] in 24 hour Urine' is the lab test to measure a certain chemical in a urine sample. |
| - | * Valid Measurement Concepts (measurement_concept_id) belong to the 'Measurement' domain, but could overlap with the 'Observation' domain. This is due to the fact that there is a continuum between systematic examination or testing (Measurement) and a simple determination of fact (Observation). | + | * Even though each Measurement always have a result, the fields value_as_number and value_as_concept_id are not mandatory. When the result is not known, the Measurement record represents just the fact that the corresponding Measurement was carried out, which in itself is already useful information for some use cases. |
| + | * Valid Measurement Concepts (measurement_concept_id) belong to the 'Measurement' domain, but could overlap with the 'Observation' domain. This is due to the fact that there is a continuum between systematic examination or testing (Measurement) and a simple determination of fact (Observation). When the Measurement Source Value of the code cannot be translated into a standard Measurement Concept ID, a Measurement entry is stored with only the corresponding source_concept_id and measurement_source_value and a measurement_concept_id of 0. | ||
| * Measurements are stored as attribute value pairs, with the attribute as the Measurement Concept and the value representing the result. The value can be a Concept (stored in value_as_concept), or a numerical value (value_as_number) with a Unit (unit_concept_id). | * Measurements are stored as attribute value pairs, with the attribute as the Measurement Concept and the value representing the result. The value can be a Concept (stored in value_as_concept), or a numerical value (value_as_number) with a Unit (unit_concept_id). | ||
| + | * Valid Concepts for the value_as_concept field belong to the 'Meas Value' domain. | ||
| + | * For some Measurement Concepts, the result is included in the test. For example, ICD10 concept_id 45595451 "Presence of alcohol in blood, level not specified" indicates a Measurement and the result (present). 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”. In this example, the “Maps to” relationship directs to 4041715 "Blood ethanol measurement" as well as a “Maps to value” record to 4181412 "Present". | ||
| + | * The operator_concept_id is optionally given for relative Measurements where the precise value is not available but its relation to a certain benchmarking value is. For example, this can be used for minimal detection thresholds of a test. | ||
| + | * The meaning of Concept 4172703 for '=' is identical to omission of a operator_concept_id value. Since the use of this field is rare, it's important when devising analyses to not to forget testing for the content of this field for values different from =. | ||
| + | * Valid Concepts for the operator_concept_id field belong to the 'Meas Value Operator' domain. | ||
| * The Unit is optional even if a value_as_number is provided. | * The Unit is optional even if a value_as_number is provided. | ||
| - | * Measurement results represented as Concepts belong to the 'Measurement Result' domain. | ||
| - | * The operator_concept_id is optionally given for relative Measurements where the precise value is not available but it's relation to a certain benchmarking value is. For example, this can be used for minimal detection thresholds of a test. The meaning of Concept XXX for '=' is identical to omission of a operator_concept_id value. Since the use of this field is rare, it's important when devising analyses to not to forget testing for the content of this field. | ||
| * If reference ranges for upper and lower limit of normal as provided (typically by a laboratory) these are stored in the range_high and range_low fields. Ranges have the same unit as the value_as_number. | * If reference ranges for upper and lower limit of normal as provided (typically by a laboratory) these are stored in the range_high and range_low fields. Ranges have the same unit as the value_as_number. | ||
| * 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/measurement.1417812196.txt.gz · Last modified: 2014/12/05 20:43 by cgreich
Page Tools
