Back to top

Physical Exam, Performed: Height

eCQM Data Element

Performance/Reporting Period
Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent a patient's height has been measured or observed.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype related to Physical Exam, Performed.
Inclusion Criteria: Includes only relevant concepts associated with identifying if a patient's height has been measured or observed. This is a grouping of LOINC codes.
Exclusion Criteria: Excludes codes that are expressed as a percentile, stated by a patient, post-partum or estimated.

Constrained to codes in the Physical Exam, Performed: Height value set (2.16.840.1.113883.3.464.1003.121.12.1014)

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.


  • 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.


  • 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.
QDM Attributes

Relevant dateTime

Relevant dateTime addresses the time an activity occurs as a single point in time. If the activity occurs over a period of time, use Relevant Period.


The final consequences or data collected from the datatype. results can be used in four ways to express:

  • That a result is present in the electronic record but any entry is acceptable
  • A numerical result is reported directly as a value. Values may be integers or decimal numbers without units, or as a quantity with a value and units - examples:
    • 100mg/dL for a lab test
    • 140 mmHg for blood pressure
    • as a percentage (actually as a quantity with % as units)
    • as a titer or ratio (e.g., 1:4, 1:80)
  • A result that matches one of a specific set of coded concepts in a value set or a code that matches a direct reference code
  • A result as a dateTime ("Assessment, Performed" and components)
Last Updated: Jun 08, 2020