Measurement
type: StructureDefinition
node role: treeRoot
id:
  v: Measurement
language:
  v: en
text:
  status:
    v: extensions
  div:
    v: Generated Narrative: StructureDefinition Measurement Language: en Name Flags Card. Type Description & Constraints<img src="[binary]" alt="doco" style="background-color: inherit"/> <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 integer 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/ter…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-type-characteristics
    l: structuredefinition-type-characteristics
  value: Code
    v: can-be-target
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: brr
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 1
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/omop/ImplementationGuide/hl7.fhir.uv.omop
        l: hl7.fhir.uv.omop
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: informative
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/omop/ImplementationGuide/hl7.fhir.uv.omop
        l: hl7.fhir.uv.omop
url:
  v: http://hl7.org/fhir/uv/omop/StructureDefinition/Measurement
  l: Measurement
version:
  v: 1.0.0
name:
  v: Measurement
title:
  v: Measurement OMOP Table
status:
  v: active
date:
  v: 2026-04-02T22:51:15+00:00
publisher:
  v: HL7 International / Biomedical Research and Regulation
contact:
  name:
    v: HL7 International / Biomedical Research and Regulation
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/rcrim
description:
  v: 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.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
fhir version:
  v: 5.0.0
mapping:
  identity:
    v: rim
  uri:
    v: http://hl7.org/v3
    l: v3
  name:
    v: RIM Mapping
kind:
  v: logical
abstract:
  v: false
type:
  v: http://hl7.org/fhir/uv/omop/StructureDefinition/Measurement
  l: Measurement
base definition:
  v: http://hl7.org/fhir/StructureDefinition/Base
  l: Base
derivation:
  v: specialization
snapshot:
  extension:
    url:
      v: http://hl7.org/fhir/tools/StructureDefinition/snapshot-base-version
      l: snapshot-base-version
    value: String
      v: 5.0.0
  element:
    id:
      v: Measurement
    path:
      v: Measurement
    short:
      v: Measurement OMOP Table
    definition:
      v: 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.
    min:
      v: 0
    max:
      v: *
    base:
      path:
        v: Base
      min:
        v: 0
      max:
        v: *
    is modifier:
      v: false
    mapping:
      identity:
        v: rim
      map:
        v: n/a
  element:
    id:
      v: Measurement.measurement-id
    path:
      v: Measurement.measurement_id
    short:
      v: Measurement Identifier
    definition:
      v: Measurement Identifier
    min:
      v: 1
    max:
      v: 1
    base:
      path:
        v: Measurement.measurement_id
      min:
        v: 1
      max:
        v: 1
    type:
      code:
        v: code
        l: code
  element:
    id:
      v: Measurement.person-id
    path:
      v: Measurement.person_id
    short:
      v: Person
    definition:
      v: The PERSON_ID of the Person for whom the Measurement is recorded. This may be a system generated code.
    min:
      v: 1
    max:
      v: 1
    base:
      path:
        v: Measurement.person_id
      min:
        v: 1
      max:
        v: 1
    type:
      code:
        v: integer
        l: integer
  element:
    id:
      v: Measurement.measurement-concept-id
    path:
      v: Measurement.measurement_concept_id
    short:
      v: Measurement
    definition:
      v: The MEASUREMENT_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies.
    min:
      v: 1
    max:
      v: 1
    base:
      path:
        v: Measurement.measurement_concept_id

v: 1

v: 1

code:
  v: code
  l: code

id:
  v: Measurement.measurement-date
path:
  v: Measurement.measurement_date
short:
  v: Measurement Date
definition:
  v: Use this date to determine the date of the measurement.
min:
  v: 1
max:
  v: 1
base:
  path:
    v: Measurement.measurement_date
  min:
    v: 1
  max:
    v: 1
type:
  code:
    v: date
    l: date

id:
  v: Measurement.measurement-datetime
path:
  v: Measurement.measurement_datetime
short:
  v: Measurement Datetime
definition:
  v: Measurement Datetime
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.measurement_datetime
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: dateTime
    l: dateTime

id:
  v: Measurement.measurement-time
path:
  v: Measurement.measurement_time
short:
  v: Measurement Time
definition:
  v: Measurement Time
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.measurement_time
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string
    l: string

id:
  v: Measurement.measurement-type-concept-id
path:
  v: Measurement.measurement_type_concept_id
short:
  v: Measurement Type
definition:
  v: 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.
min:
  v: 1
max:
  v: 1
base:
  path:
    v: Measurement.measurement_type_concept_id
  min:
    v: 1
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: Measurement.operator-concept-id
path:
  v: Measurement.operator_concept_id
short:
  v: Operator
definition:
  v: 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 =.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.operator_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: Measurement.value-as-number
path:
  v: Measurement.value_as_number
short:
  v: Value as Number
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.value_as_number
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: integer
    l: integer

id:
  v: Measurement.value-as-concept-id
path:
  v: Measurement.value_as_concept_id
short:
  v: Value as Concept
definition:
  v: If the raw data gives a categorial result for measurements those values are captured and mapped to standard concepts in the 'Meas Value' domain.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.value_as_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: Measurement.unit-concept-id
path:
  v: Measurement.unit_concept_id
short:
  v: Unit
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.unit_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: Measurement.range-low
path:
  v: Measurement.range_low
short:
  v: Range Low
definition:
  v: Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.range_low
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: integer
    l: integer

id:
  v: Measurement.range-high
path:
  v: Measurement.range_high
short:
  v: Range High
definition:
  v: Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.range_high
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: integer
    l: integer

id:
  v: Measurement.provider-id
path:
  v: Measurement.provider_id
short:
  v: Provider
definition:
  v: The provider associated with measurement record, e.g. the provider who ordered the test or the provider who recorded the result.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.provider_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: integer
    l: integer

id:
  v: Measurement.visit-occurrence-id
path:
  v: Measurement.visit_occurrence_id
short:
  v: Visit Occurence
definition:
  v: The visit during which the Measurement occurred.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.visit_occurrence_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: integer
    l: integer

id:
  v: Measurement.visit-detail-id
path:
  v: Measurement.visit_detail_id
short:
  v: Visit Detail
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.visit_detail_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: integer
    l: integer

id:
  v: Measurement.measurement-source-value
path:
  v: Measurement.measurement_source_value
short:
  v: Measurement Source Value
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.measurement_source_value
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string
    l: string

id:
  v: Measurement.measurement-source-concept-id
path:
  v: Measurement.measurement_source_concept_id
short:
  v: Measurement Source
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.measurement_source_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: Measurement.unit-source-value
path:
  v: Measurement.unit_source_value
short:
  v: Unit Source Value
definition:
  v: This field houses the verbatim value from the source data representing the unit of the Measurement that occurred.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.unit_source_value
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string
    l: string

id:
  v: Measurement.unit-source-concept-id
path:
  v: Measurement.unit_source_concept_id
short:
  v: Unit Source
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.unit_source_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: Measurement.value-source-value
path:
  v: Measurement.value_source_value
short:
  v: Value Source Value
definition:
  v: This field houses the verbatim result value of the Measurement from the source data .
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.value_source_value
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string
    l: string

id:
  v: Measurement.measurement-event-id
path:
  v: Measurement.measurement_event_id
short:
  v: Measurement Event
definition:
  v: If the Measurement record is related to another record in the database, this field is the primary key of the linked record.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.measurement_event_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string
    l: string

id:
  v: Measurement.meas-event-field-concept-id
path:
  v: Measurement.meas_event_field_concept_id
short:
  v: Measurement Event Field
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: Measurement.meas_event_field_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: code
    l: code

element:
  id:
    v: Measurement
  path:
    v: Measurement
  short:
    v: Measurement OMOP Table
  definition:
    v: 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.
element:
  id:
    v: Measurement.measurement-id
  path:
    v: Measurement.measurement_id
  short:
    v: Measurement Identifier
  definition:
    v: Measurement Identifier
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: code
      l: code
element:
  id:
    v: Measurement.person-id
  path:
    v: Measurement.person_id
  short:
    v: Person
  definition:
    v: The PERSON_ID of the Person for whom the Measurement is recorded. This may be a system generated code.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: integer
      l: integer
element:
  id:
    v: Measurement.measurement-concept-id
  path:
    v: Measurement.measurement_concept_id
  short:
    v: Measurement
  definition:
    v: The MEASUREMENT_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: code
      l: code
element:
  id:
    v: Measurement.measurement-date
  path:
    v: Measurement.measurement_date
  short:
    v: Measurement Date
  definition:
    v: Use this date to determine the date of the measurement.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: date
      l: date
element:
  id:
    v: Measurement.measurement-datetime
  path:
    v: Measurement.measurement_datetime
  short:
    v: Measurement Datetime
  definition:
    v: Measurement Datetime
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: dateTime
      l: dateTime
element:
  id:
    v: Measurement.measurement-time
  path:
    v: Measurement.measurement_time
  short:
    v: Measurement Time
  definition:
    v: Measurement Time
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: string
      l: string
element:
  id:
    v: Measurement.measurement-type-concept-id
  path:
    v: Measurement.measurement_type_concept_id
  short:
    v: Measurement Type
  definition:
    v: 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.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: code
      l: code
element:
  id:
    v: Measurement.operator-concept-id
  path:
    v: Measurement.operator_concept_id
  short:
    v: Operator
  definition:
    v: 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 =.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: code
      l: code
element:
  id:
    v: Measurement.value-as-number
  path:
    v: Measurement.value_as_number
  short:
    v: Value as Number
  definition:
    v: 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.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: integer
      l: integer
element:
  id:
    v: Measurement.value-as-concept-id
  path:
    v: Measurement.value_as_concept_id
  short:
    v: Value as Concept
  definition:
    v: If the raw data gives a categorial result for measurements those values are captured and mapped to standard concepts in the 'Meas Value' domain.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: code
      l: code
element:
  id:
    v: Measurement.unit-concept-id
  path:
    v: Measurement.unit_concept_id
  short:
    v: Unit
  definition:
    v: 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.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: code
      l: code
element:
  id:
    v: Measurement.range-low
  path:
    v: Measurement.range_low

v: Range Low

v: Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.

v: 0

v: 1

code:
  v: integer
  l: integer

id:
  v: Measurement.range-high
path:
  v: Measurement.range_high
short:
  v: Range High
definition:
  v: Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: integer
    l: integer

id:
  v: Measurement.provider-id
path:
  v: Measurement.provider_id
short:
  v: Provider
definition:
  v: The provider associated with measurement record, e.g. the provider who ordered the test or the provider who recorded the result.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: integer
    l: integer

id:
  v: Measurement.visit-occurrence-id
path:
  v: Measurement.visit_occurrence_id
short:
  v: Visit Occurence
definition:
  v: The visit during which the Measurement occurred.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: integer
    l: integer

id:
  v: Measurement.visit-detail-id
path:
  v: Measurement.visit_detail_id
short:
  v: Visit Detail
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: integer
    l: integer

id:
  v: Measurement.measurement-source-value
path:
  v: Measurement.measurement_source_value
short:
  v: Measurement Source Value
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: string
    l: string

id:
  v: Measurement.measurement-source-concept-id
path:
  v: Measurement.measurement_source_concept_id
short:
  v: Measurement Source
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: code
    l: code

id:
  v: Measurement.unit-source-value
path:
  v: Measurement.unit_source_value
short:
  v: Unit Source Value
definition:
  v: This field houses the verbatim value from the source data representing the unit of the Measurement that occurred.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: string
    l: string

id:
  v: Measurement.unit-source-concept-id
path:
  v: Measurement.unit_source_concept_id
short:
  v: Unit Source
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: code
    l: code

id:
  v: Measurement.value-source-value
path:
  v: Measurement.value_source_value
short:
  v: Value Source Value
definition:
  v: This field houses the verbatim result value of the Measurement from the source data .
min:
  v: 0
max:
  v: 1
type:
  code:
    v: string
    l: string

id:
  v: Measurement.measurement-event-id
path:
  v: Measurement.measurement_event_id
short:
  v: Measurement Event
definition:
  v: If the Measurement record is related to another record in the database, this field is the primary key of the linked record.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: string
    l: string

id:
  v: Measurement.meas-event-field-concept-id
path:
  v: Measurement.meas_event_field_concept_id
short:
  v: Measurement Event Field
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: code
    l: code