Back to top
Top
CMS Measure ID: CMS529v1    Performance/Reporting Period: 2021    Version: 1    NQF Number: 02879e
Description:

This logic is intended to extract electronic clinical data. This is not an electronic clinical quality measure and this logic will not produce measure results. Instead, it will produce a file containing the data that CMS will link with administrative claims to risk adjust the Hybrid HWR outcome measure. It is designed to extract the first resulted set of vital signs and basic laboratory results obtained from encounters for adult Medicare Fee-For-Service patients admitted to acute care short stay hospitals.

Data Elements and coded QDM Attributes contained within the eCQM

+ Expand all

Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent procedures representing an emergency department encounter.
Data Element Scope: This value set may use the Quality Data Model (QDM) category related to Encounter. The intent of this data element is to identify patients who have had an emergency department encounter.
Inclusion Criteria: Includes only relevant concepts associated with an emergency department visit encounter using the SNOMED CT code system.
Exclusion Criteria: No exclusions.

Constrained to codes in the Encounter, Performed: Emergency Department Visit value set (2.16.840.1.113883.3.117.1.7.1.292)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Encounter, Performed"

Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.5 addresses that concept using the diagnosis rank=1.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here

Timing:

  • The relevantPeriod addresses:
    • startTime - The time the encounter began (admission time).
    • stopTime - The time the encounter ended (discharge time).
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • The locationPeriod is an attribute of the attribute facility location that addresses:
    • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
    • stopTime - the time the patient departed from the location.
Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent the most common inpatient encounter types.
Data Element Scope: This value set may use the Quality Data Model (QDM) category related to Encounter. The intent of this data element is to identify patients who have had an inpatient encounter.
Inclusion Criteria: Includes only relevant concepts associated with SNOMED CT codes representing inpatient encounter.
Exclusion Criteria: No exclusions.

Constrained to codes in the Encounter, Performed: Encounter Inpatient value set (2.16.840.1.113883.3.666.5.307)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Encounter, Performed"

Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.5 addresses that concept using the diagnosis rank=1.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here

Timing:

  • The relevantPeriod addresses:
    • startTime - The time the encounter began (admission time).
    • stopTime - The time the encounter ended (discharge time).
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • The locationPeriod is an attribute of the attribute facility location that addresses:
    • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
    • stopTime - the time the patient departed from the location.
Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent observation encounter types.
Data Element Scope: This value set may use the Quality Data Model (QDM) category related to Encounter. The intent of this data element is to identify patients who have had an observation encounter.
Inclusion Criteria: Includes only relevant concepts associated with SNOMED CT codes representing inpatient encounter.
Exclusion Criteria: No exclusions.

Constrained to codes in the Encounter, Performed: Observation Services value set (2.16.840.1.113762.1.4.1111.143)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Encounter, Performed"

Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.5 addresses that concept using the diagnosis rank=1.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here

Timing:

  • The relevantPeriod addresses:
    • startTime - The time the encounter began (admission time).
    • stopTime - The time the encounter ended (discharge time).
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • The locationPeriod is an attribute of the attribute facility location that addresses:
    • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
    • stopTime - the time the patient departed from the location.
Value Set Description from VSAC
Clinical Focus: This value set contains codes for lab tests commonly used for a blood/serum/plasma bicarbonate lab test.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype Laboratory Test, Performed. The intent of this data element is to identify patients who had a Bicarbonate lab test on a specimen source of blood/serum/plasma.
Inclusion Criteria: Includes only codes that represent bicarbonate lab test using the specimen source of blood/serum/plasma. Includes codes that represent both bicarbonate and carbon dioxide lab tests.
Exclusion Criteria: Excludes any codes which do not represent bicarbonate lab tests using a non-blood/serum/plasma source of blood.

Constrained to codes in the Laboratory Test, Performed: Bicarbonate lab test value set (2.16.840.1.113762.1.4.1045.139)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Laboratory Test, Performed"

Data elements that meet criteria using this datatype should document the laboratory test indicated by the QDM category and its corresponding value set was performed.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here.    

Timing:

  • relevant dateTime references the time the laboratory test is performed when the laboratory test occurs at a single point in time.
  • relevantPeriod references a start and stop time for a laboratory test that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the laboratory test begins.
    • stopTime - The time the laboratory test ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Examples:

  • Initiation of a venipuncture for a fasting blood glucose to the time venipuncture for the fasting blood glucose is completed – use relevant dateTime to reference this single point in time for many specimen collections
  • Initiation of a 24-hour urine collection for measured creatinine clearance until completion of the 24-hour urine collection – use relevantPeriod to reference the start to stop time for this event.

Notes:

  • The time that the result report is available is a separate attribute than the time of the study (specimen collection).
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Value Set Description from VSAC
Clinical Focus: This value set contains codes used for a blood/serum/plasma creatinine test.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype Laboratory Test, Performed. The intent of this data element is to identify patients with a lab test performed on a source of blood/serum/plasma for creatinine.
Inclusion Criteria: Includes only codes that represent creatinine lab test using the source of blood/serum/plasma.
Exclusion Criteria: Excludes any codes which do not represent creatinine lab test using a non-blood/serum/plasma source of blood.

Constrained to codes in the Laboratory Test, Performed: Creatinine lab test value set (2.16.840.1.113883.3.666.5.2363)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Laboratory Test, Performed"

Data elements that meet criteria using this datatype should document the laboratory test indicated by the QDM category and its corresponding value set was performed.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here.    

Timing:

  • relevant dateTime references the time the laboratory test is performed when the laboratory test occurs at a single point in time.
  • relevantPeriod references a start and stop time for a laboratory test that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the laboratory test begins.
    • stopTime - The time the laboratory test ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Examples:

  • Initiation of a venipuncture for a fasting blood glucose to the time venipuncture for the fasting blood glucose is completed – use relevant dateTime to reference this single point in time for many specimen collections
  • Initiation of a 24-hour urine collection for measured creatinine clearance until completion of the 24-hour urine collection – use relevantPeriod to reference the start to stop time for this event.

Notes:

  • The time that the result report is available is a separate attribute than the time of the study (specimen collection).
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Value Set Description from VSAC
Clinical Focus: This value set contains codes for lab tests commonly used for a glucose lab test.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype Laboratory Test, Performed. The intent of this data element is to identify patients who had a glucose lab test.
Inclusion Criteria: Includes only codes that represent a glucose lab test using the specimen source of blood/serum/plasma. Point of Care (POC) testing sources are included.
Exclusion Criteria: Excludes any codes representing a glucose lab test using any other specimen source.

Constrained to codes in the Laboratory Test, Performed: Glucose lab test value set (2.16.840.1.113762.1.4.1045.134)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Laboratory Test, Performed"

Data elements that meet criteria using this datatype should document the laboratory test indicated by the QDM category and its corresponding value set was performed.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here.    

Timing:

  • relevant dateTime references the time the laboratory test is performed when the laboratory test occurs at a single point in time.
  • relevantPeriod references a start and stop time for a laboratory test that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the laboratory test begins.
    • stopTime - The time the laboratory test ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Examples:

  • Initiation of a venipuncture for a fasting blood glucose to the time venipuncture for the fasting blood glucose is completed – use relevant dateTime to reference this single point in time for many specimen collections
  • Initiation of a 24-hour urine collection for measured creatinine clearance until completion of the 24-hour urine collection – use relevantPeriod to reference the start to stop time for this event.

Notes:

  • The time that the result report is available is a separate attribute than the time of the study (specimen collection).
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Value Set Description from VSAC
Clinical Focus: This value set contains codes for hematocrit laboratory testing performed using a source of blood/serum/plasma.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype Laboratory Test, Performed. The intent of this data element is to identify patients with a lab test performed on a source of blood/serum/plasma for hematocrit.
Inclusion Criteria: Includes only codes that represent hematocrit lab test using the source of blood/serum/plasma with a reporting scale of volume fraction-% represented using LOINC codes.
Exclusion Criteria: Excludes any codes which do not represent hematocrit lab tests using a non-blood/serum/plasma source of blood.

Constrained to codes in the Laboratory Test, Performed: Hematocrit lab test value set (2.16.840.1.113762.1.4.1045.114)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Laboratory Test, Performed"

Data elements that meet criteria using this datatype should document the laboratory test indicated by the QDM category and its corresponding value set was performed.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here.    

Timing:

  • relevant dateTime references the time the laboratory test is performed when the laboratory test occurs at a single point in time.
  • relevantPeriod references a start and stop time for a laboratory test that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the laboratory test begins.
    • stopTime - The time the laboratory test ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Examples:

  • Initiation of a venipuncture for a fasting blood glucose to the time venipuncture for the fasting blood glucose is completed – use relevant dateTime to reference this single point in time for many specimen collections
  • Initiation of a 24-hour urine collection for measured creatinine clearance until completion of the 24-hour urine collection – use relevantPeriod to reference the start to stop time for this event.

Notes:

  • The time that the result report is available is a separate attribute than the time of the study (specimen collection).
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Value Set Description from VSAC
Clinical Focus: This value set contains codes for lab tests commonly used for a blood/serum/plasma potassium lab test.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype Laboratory Test, Performed. The intent of this data element is to identify patients who had a potassium lab test on a specimen source of blood/serum/plasma.
Inclusion Criteria: Includes only codes that represent a potassium lab test using the specimen source of blood/serum/plasma.
Exclusion Criteria: Excludes any codes which do not represent a potassium lab tests using a non-blood/serum/plasma source of blood.

Constrained to codes in the Laboratory Test, Performed: Potassium lab test value set (2.16.840.1.113762.1.4.1045.117)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Laboratory Test, Performed"

Data elements that meet criteria using this datatype should document the laboratory test indicated by the QDM category and its corresponding value set was performed.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here.    

Timing:

  • relevant dateTime references the time the laboratory test is performed when the laboratory test occurs at a single point in time.
  • relevantPeriod references a start and stop time for a laboratory test that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the laboratory test begins.
    • stopTime - The time the laboratory test ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Examples:

  • Initiation of a venipuncture for a fasting blood glucose to the time venipuncture for the fasting blood glucose is completed – use relevant dateTime to reference this single point in time for many specimen collections
  • Initiation of a 24-hour urine collection for measured creatinine clearance until completion of the 24-hour urine collection – use relevantPeriod to reference the start to stop time for this event.

Notes:

  • The time that the result report is available is a separate attribute than the time of the study (specimen collection).
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Value Set Description from VSAC
Clinical Focus: This value set contains lab tests commonly used for a blood/serum/plasma sodium test.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype Laboratory Test, Result or Laboratory Test, Order. The intent of this data element is to identify patients with a lab test performed on a source of blood/serum/plasma for sodium.
Inclusion Criteria: Includes only sodium lab test using the source of blood/serum/plasma.
Exclusion Criteria: Excludes codes for sodium lab test using the source of capillary blood.

Constrained to codes in the Laboratory Test, Performed: Sodium lab test value set (2.16.840.1.113762.1.4.1045.119)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Laboratory Test, Performed"

Data elements that meet criteria using this datatype should document the laboratory test indicated by the QDM category and its corresponding value set was performed.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here.    

Timing:

  • relevant dateTime references the time the laboratory test is performed when the laboratory test occurs at a single point in time.
  • relevantPeriod references a start and stop time for a laboratory test that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the laboratory test begins.
    • stopTime - The time the laboratory test ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Examples:

  • Initiation of a venipuncture for a fasting blood glucose to the time venipuncture for the fasting blood glucose is completed – use relevant dateTime to reference this single point in time for many specimen collections
  • Initiation of a 24-hour urine collection for measured creatinine clearance until completion of the 24-hour urine collection – use relevantPeriod to reference the start to stop time for this event.

Notes:

  • The time that the result report is available is a separate attribute than the time of the study (specimen collection).
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Value Set Description from VSAC
Clinical Focus: This value set contains codes for lab tests commonly used for a blood/serum/plasma white blood cells count lab test.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype Laboratory Test, Performed. The intent of this data element is to identify patients who had a white blood cells lab test on a specimen source of blood/serum/plasma.
Inclusion Criteria: Includes only codes that represent white blood cells count lab test using the specimen source of blood/serum/plasma.
Exclusion Criteria: Excludes any codes which do not represent white blood cells count lab tests using a non-blood/serum/plasma source of blood.

Constrained to codes in the Laboratory Test, Performed: White blood cells count lab test value set (2.16.840.1.113762.1.4.1045.129)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Laboratory Test, Performed"

Data elements that meet criteria using this datatype should document the laboratory test indicated by the QDM category and its corresponding value set was performed.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here.    

Timing:

  • relevant dateTime references the time the laboratory test is performed when the laboratory test occurs at a single point in time.
  • relevantPeriod references a start and stop time for a laboratory test that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the laboratory test begins.
    • stopTime - The time the laboratory test ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Examples:

  • Initiation of a venipuncture for a fasting blood glucose to the time venipuncture for the fasting blood glucose is completed – use relevant dateTime to reference this single point in time for many specimen collections
  • Initiation of a 24-hour urine collection for measured creatinine clearance until completion of the 24-hour urine collection – use relevantPeriod to reference the start to stop time for this event.

Notes:

  • The time that the result report is available is a separate attribute than the time of the study (specimen collection).
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Value Set Description from VSAC
Clinical Focus: This value set contains codes for Medicare payer types.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype Participant. The intent of this data element is to identify patients with Medicare Fee-For-Service as a payer source.
Inclusion Criteria: Includes only codes that identify Medicare Fee-For-Service as a payer source.
Exclusion Criteria: Excludes codes which do not represent Medicare Fee-For-Service as a payer source.

Constrained to codes in the Participation: Medicare payer value set (2.16.840.1.113762.1.4.1104.10)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Participation"

Data elements that meet criteria using this datatype should document the type of plan or program in which the patient is expected to be enrolled. The program is identified as the Issuer (e.g., Aetna, Blue Cross Blue Shield Association, Cigna). The code attribute indicates the coverage type indicating the program in which the subject of record participates (e.g., health insurance plan policy, disease specific policy, health maintenance organization policy)

Timing:

participationPeriod addresses:

  • enrollmentStartdate - The time the patient enrolled in the program.
  • enrollmentEnddate - The time the patient’s enrollment in the program ends.
Direct Reference Code

Constrained to 'Birth date' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Patient Characteristic, Birthdate"

The "Patient Characteristic Birthdate" should document the patient’s date of birth.

Timing: The "Patient Characteristic, Birthdate" is a single point in time representing the date and time of birth. It does not have a start and stop time.

Note: "Patient Characteristic Birthdate" is fixed to LOINC code 21112-8 (Birth date) and therefore cannot be further qualified with a value set.

Value Set Description from VSAC
Clinical Focus: This value set contains codes which represent the observation or measurement of a patient's body temperature.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype Physical exam, finding. The intent of this data element is to identify an observation or measurement of a patient's body temperature using LOINC code system.
Inclusion Criteria: Includes only those LOINC codes which represent an observation or measurement of a body temperature.
Exclusion Criteria: Excludes any codes which do not represent an observation or measurement of a body temperature in LOINC code system.

Constrained to codes in the Physical Exam, Performed: Body temperature value set (2.16.840.1.113762.1.4.1045.152)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Physical Exam, Performed"

Data elements that meet criteria using this datatype should document the completion of the physical exam indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references the time the physical exam is performed when the physical exam occurs at a single point in time.
  • relevantPeriod references a start and stop time for a physical exam that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the physical exam begins.
    • stopTime - The time the physical exam ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • Timing refers to a single instance of a physical examination activity. If a measure seeks to evaluate multiple physical examination activities over a period of time, the measure developer should use CQL logic to represent the query request.
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Value Set Description from VSAC
Clinical Focus: This value set contains codes for lab tests that represent the result of measurement or observation of body weight.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype Physical Exam, Finding. The intent of this data element is to identify patients who have had an observation or measurement of their body weight.
Inclusion Criteria: Includes only codes that represent a measurement or observation of a person's body weight in LOINC.
Exclusion Criteria: Excludes any codes or concepts which do not represent body weight as defined in the inclusion criteria.

Constrained to codes in the Physical Exam, Performed: Body weight value set (2.16.840.1.113762.1.4.1045.159)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Physical Exam, Performed"

Data elements that meet criteria using this datatype should document the completion of the physical exam indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references the time the physical exam is performed when the physical exam occurs at a single point in time.
  • relevantPeriod references a start and stop time for a physical exam that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the physical exam begins.
    • stopTime - The time the physical exam ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • Timing refers to a single instance of a physical examination activity. If a measure seeks to evaluate multiple physical examination activities over a period of time, the measure developer should use CQL logic to represent the query request.
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Direct Reference Code

Constrained to 'Heart rate' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Physical Exam, Performed"

Data elements that meet criteria using this datatype should document the completion of the physical exam indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references the time the physical exam is performed when the physical exam occurs at a single point in time.
  • relevantPeriod references a start and stop time for a physical exam that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the physical exam begins.
    • stopTime - The time the physical exam ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • Timing refers to a single instance of a physical examination activity. If a measure seeks to evaluate multiple physical examination activities over a period of time, the measure developer should use CQL logic to represent the query request.
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Direct Reference Code

Constrained to 'Oxygen saturation in Arterial blood by Pulse oximetry' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Physical Exam, Performed"

Data elements that meet criteria using this datatype should document the completion of the physical exam indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references the time the physical exam is performed when the physical exam occurs at a single point in time.
  • relevantPeriod references a start and stop time for a physical exam that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the physical exam begins.
    • stopTime - The time the physical exam ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • Timing refers to a single instance of a physical examination activity. If a measure seeks to evaluate multiple physical examination activities over a period of time, the measure developer should use CQL logic to represent the query request.
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Direct Reference Code

Constrained to 'Respiratory rate' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Physical Exam, Performed"

Data elements that meet criteria using this datatype should document the completion of the physical exam indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references the time the physical exam is performed when the physical exam occurs at a single point in time.
  • relevantPeriod references a start and stop time for a physical exam that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the physical exam begins.
    • stopTime - The time the physical exam ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • Timing refers to a single instance of a physical examination activity. If a measure seeks to evaluate multiple physical examination activities over a period of time, the measure developer should use CQL logic to represent the query request.
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Direct Reference Code

Constrained to 'Systolic blood pressure' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Physical Exam, Performed"

Data elements that meet criteria using this datatype should document the completion of the physical exam indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references the time the physical exam is performed when the physical exam occurs at a single point in time.
  • relevantPeriod references a start and stop time for a physical exam that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the physical exam begins.
    • stopTime - The time the physical exam ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • Timing refers to a single instance of a physical examination activity. If a measure seeks to evaluate multiple physical examination activities over a period of time, the measure developer should use CQL logic to represent the query request.
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.