Back to top
Top

Encounter, Performed: Office Visit 1

eCQM Data Element

Performance/Reporting Period
2020
Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent patients who have had an office or other outpatient visit.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype related to Encounter, Performed.
Inclusion Criteria: Includes only relevant concepts associated with comprehensive history, evaluation, and management of a patient in an office or outpatient facility. Patient can be presenting with problems that are minor to high severity. This is a grouping value set of CPT codes.
Exclusion Criteria: Excludes non-office visits, including telehealth services.

Constrained to codes in the Encounter, Performed: Office Visit 1 value set (2.16.840.1.113883.3.464.1003.101.12.1001)

QDM Datatype and Definition (QDM Version 5.4)

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.

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

Timing: The Relevant Period addresses:

  • startTime – the time the encounter began (admission time)
  • stopTime – the time the encounter ended (discharge time)

The Author dateTime addresses when an Encounter is documented. Documentation can occur at the beginning, during, at the end or subsequent to the end of an Encounter. The Author dateTime should be used only if the Relevant Period cannot be obtained.

The Location Period is an attribute of the attribute facility location addresses:

  • startTime -the time the patient arrived at the location;
  • stopTime -the time the patient departed from the location
eCQMs using this data element:
QDM Attributes

Author dateTime

The time the data element was entered into the clinical software. Note, some datatypes include both Relevant Time and Author dateTime attributes. The purpose is to accommodate Author dateTime if the actual start and stop times are not available when evaluating for feasibility, and also to allow specification of a time for Negation Rationale.

Diagnoses

Coded diagnoses/problems addressed during the encounter. The diagnoses attribute is intended to capture ALL diagnoses, including principal diagnosis. Use of the Encounter, Performed: diagnoses attribute and the Diagnosis datatype is redundant for relating the diagnosis to the Encounter, Performed. The Encounter, Performed: diagnoses syntax is preferred. Referencing the same diagnosis using Encounter, Performed (diagnoses attribute) and Diagnosis (datatype) should only occur if the measure must define a specified length of a prevalence period, e.g., the measure must assure that the diagnoses have been present for at least some defined time period before the encounter, and were addressed during the Encounter.

Relevant Period

Relevant Period addresses the time between the start of an action to the end of an action. Each datatype using relevant period defines specific definitions for the start and stop time for the action listed.
Last Updated: Oct 17, 2019