Brief Description of Measure:

Multiple EC eCQMs

Description of Issue:

During this CRP cycle, measure developers explored the potential inclusion and feasibility of incorporating a new Quality Data Model (QDM) v5.6 Encounter.class attribute into eligible encounter logic across eCQMs to indicate if the measure is to address specific settings. 
 
We received feedback in prior CRP tickets CQM-4822 Use of Encounter.class attribute across EC eCQMs and CQM-4807 Use of Encounter.class attribute across EH eCQMs - Office of the National Coordinator for Health Information Technology (healthit.gov) that instituting the Encounter.class attribute across all eCQMs is feasible but may add complexity without perceived value.
 
We did however receive support in CQM-4823 Use of Encounter.class attribute to capture non-telehealth eligible encounters for using the Encounter.class attribute for the purposes of excluding telehealth eligible encounters.
 
We would like to circle back on this issue once more, and see if there is any perceived value or support in using the Encounter.class attribute to also identify encounters for inclusion that are telehealth eligible within measure logic.

Proposed Solution:

​Measure developers would implement the Quality Data model (QDM) v5.6 Encounter.class attribute in the eCQM logic for all telehealth eligible encounters, using the 'virtual' code from the value set (http://terminology.hl7.org/ValueSet/v3-ActEncounterCode) as defined as part of HL7 v3. This will provide a mechanism to represent the telehealth eligible encounters across applicable eCQMs.
 
Example logic excerpt:
   where FaceToFaceEncounter.relevantPeriod during "Measurement Period"
       and FaceToFaceEncounter.class = "virtual"
 
Please see the HL7 terminology description of virtual encounter (based onhttp://terminology.hl7.org/ValueSet/v3-ActEncounterCode) and provide feedback. A 'VR' or 'virtual' for Encounter.class attribute is defined as a patient encounter where the patient and the practitioner(s) are not in the same physical location. Examples include telephone conference, email exchange, robotic surgery, and televideo conference.

Rationale for Change:

​Provide a mechanism, using the QDM encounter. Class attribute, to distinguish which measures contain telehealth eligible encounters.