Generated Narrative: StructureDefinition Measurement Language: en Name Flags Card. Type Description & Constraints <a href="StructureDefinition-Measurement-definitions.html#Measurement" title="The MEASUREMENT table contains records of Measurements, 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. 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). The Procedure for obtaining the sample is housed in the PROCEDURE_OCCURRENCE table, though it is unnecessary to create a PROCEDURE_OCCURRENCE record for each measurement if one does not exist in the source data. Measurements differ from Observations in that they require a standardized test or some other activity to generate a quantitative or qualitative result. If there is no result, it is assumed that the lab test was conducted but the result was not captured.">Measurement 0..* Base Measurement OMOP Table Instances of this logical model can be the target of a Reference #xD; measurement_id 1..1 code Measurement Identifier #xD; person_id 1..1 Reference(Person OMOP Table) Person #xD; measurement_concept_id 1..1 code Measurement #xD; measurement_date 1..1 date Measurement Date #xD; measurement_datetime 0..1 dateTime Measurement Datetime #xD; measurement_time 0..1 string Measurement Time #xD; measurement_type_concept_id 1..1 code Measurement Type #xD; <a href="StructureDefinition-Measurement-definitions.html#Measurement.operator-concept-id" title="The meaning of Concept [4172703](https://athena.ohdsi.org/search-terms/terms/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 =.">operator_concept_id 0..1 code Operator #xD; value_as_number 0..1 integer Value as Number #xD; value_as_concept_id 0..1 code Value as Concept #xD; unit_concept_id 0..1 code Unit #xD; range_low 0..1 integer Range Low #xD; range_high 0..1 integer Range High #xD; provider_id 0..1 Reference(Provider OMOP Table) Provider #xD; visit_occurrence_id 0..1 Reference(Visit Occurrence OMOP Table) Visit Occurence #xD; visit_detail_id 0..1 Reference(Visit Detail OMOP Table) Visit Detail #xD; measurement_source_value 0..1 string Measurement Source Value #xD; <a href="StructureDefinition-Measurement-definitions.html#Measurement.measurement-source-concept-id" title="This is the concept representing the MEASUREMENT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Measurement necessary for a given analytic use case. Consider using MEASUREMENT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.">measurement_source_concept_id 0..1 code Measurement Source #xD; unit_source_value 0..1 string Unit Source Value #xD; <a href="StructureDefinition-Measurement-definitions.html#Measurement.unit-source-concept-id" title="This is the concept representing the UNIT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Measurement necessary for a given analytic use case. Consider using UNIT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.">unit_source_concept_id 0..1 code Unit Source #xD; value_source_value 0..1 string Value Source Value #xD; measurement_event_id 0..1 string Measurement Event #xD; meas_event_field_concept_id 0..1 code Measurement Event Field #xD; Documentation for this format
HL7 International / Biomedical Research and Regulation
The MEASUREMENT table contains records of Measurements, 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. 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). The Procedure for obtaining the sample is housed in the PROCEDURE_OCCURRENCE table, though it is unnecessary to create a PROCEDURE_OCCURRENCE record for each measurement if one does not exist in the source data. Measurements differ from Observations in that they require a standardized test or some other activity to generate a quantitative or qualitative result. If there is no result, it is assumed that the lab test was conducted but the result was not captured.
The PERSON_ID of the Person for whom the Measurement is recorded. This may be a system generated code.
The MEASUREMENT_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies.
Use this date to determine the date of the measurement.
This field can be used to determine the provenance of the Measurement record, as in whether the measurement was from an EHR system, insurance claim, registry, or other sources.
The meaning of Concept [4172703](https://athena.ohdsi.org/search-terms/terms/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 =.
This is the numerical value of the Result of the Measurement, if available. Note that measurements such as blood pressures will be split into their component parts i.e. one record for systolic, one record for diastolic.
If the raw data gives a categorial result for measurements those values are captured and mapped to standard concepts in the 'Meas Value' domain.
There is currently no recommended unit for individual measurements, i.e. it is not mandatory to represent Hemoglobin a1C measurements as a percentage. UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.
The provider associated with measurement record, e.g. the provider who ordered the test or the provider who recorded the result.
The visit during which the Measurement occurred.
The VISIT_DETAIL record during which the Measurement occurred. For example, if the Person was in the ICU at the time the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
This field houses the verbatim value from the source data representing the Measurement that occurred. For example, this could be an ICD10 or Read code.
This is the concept representing the MEASUREMENT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Measurement necessary for a given analytic use case. Consider using MEASUREMENT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
This field houses the verbatim value from the source data representing the unit of the Measurement that occurred.
This is the concept representing the UNIT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Measurement necessary for a given analytic use case. Consider using UNIT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
This field houses the verbatim result value of the Measurement from the source data .
If the Measurement record is related to another record in the database, this field is the primary key of the linked record.
If the Measurement record is related to another record in the database, this field is the CONCEPT_ID that identifies which table the primary key of the linked record came from.