Get Started with eCQMs

Many different organizations may participate in the development and maintenance of electronic clinical quality measures (eCQMs). The Centers for Medicare & Medicaid Services (CMS) Measures Management System is a standardized system providing details on the process for developing and maintaining the quality measures used in CMS's various quality reporting and incentive programs. Information on the clinical quality measure and eCQM lifecycle is available in the Blueprint content on the CMS Measures Management System Hub and on the eCQM Lifecycle webpages. CMS's Quality Data Model (QDM)-based Clinical Quality Language (CQL) Style Guide is for measure developers; it provides examples to standardize the expression of measure concepts across eCQMs and define a uniform look and feel to eCQM logic using CQL. The Guide also provides a set of common best practices for implementation across CQL-based eCQMs used in CMS quality reporting and incentive programs. 

eCQM Lifecycle

The eCQM Lifecycle is a series of stages eCQMs progress through development (conceptualization, specification, and testing), implementation, and maintenance. CMS and measure developers provide several opportunities for stakeholders to engage throughout the Measure Lifecycle. 

Endorsement of eCQMs  

The CMS Consensus-Based Entity (CBE) endorses quality measures through a transparent, consensus-based process to evaluate the extent to which measures are safe and effective. CMS uses CBE-endorsed measures in some of their quality reporting and value-based purchasing programs. Note, not all CBE-endorsed measures are used in CMS programs and all CMS measures are not CBE-endorsed. The CMS CBE has posted their inventory, the Submission Tool and Repository (STAR), with CBE numbers replacing the National Quality Foundation (NQF) numbers. The numbers did not change. 

Updates to eCQMs  

CMS requires eCQMs adopted by CMS programs to be updated annually to reflect changes in evidence-based medicine, code sets, and measure logic. CMS works with measure stewards, measure developers, and eCQMs users to ensure necessary changes are reflected in the Annual Update. 

Structure of eCQMs

To facilitate reporting from an electronic health record (EHR) and/or other health information technology, eCQMs are made of electronic specifications. Health Quality Measure Format (HQMF), CQL, Expression Logical Model (ELM), and other Health Level Seven International® (HL7) standards, are used for electronically documenting eCQM content. 

Coding of information for eCQMs consists of

• Computable representations of the eCQM contain important details about the measure, the definition of the data elements, and the underlying logic of the measure calculation. The files include
  • HQMF XML syntax (.xml). The HQMF includes a header and a body. The header identifies and classifies the document and provides important metadata about the measure. The HQMF body contains eCQM sections (e.g., definitions, population criteria, supplemental data elements).
  • Shared CQL libraries (.cql, .xml, and .json). The shared libraries are the basic units of sharing CQL. They consist of a foundation of CQL statements used within a measure. Every measure has at least one main CQL library referenced from HQMF.
    • CQL file (.cql). The CQL file provides the expression logic for data criteria, population criteria, and supplemental data elements. It provides a formal description of the computable content in the measure and organized into libraries for reusing or sharing between measures and other artifacts.
    • Expression Logical Model (ELM) XML document (.xml). ELM provides a machine-readable representation of the measure’s logic in XML. The intent of the ELM file is for machine processing and provides the information needed to retrieve data from an EHR automatically.
    • ELM JavaScript Object Notation (JSON) file (.json). The JSON file is the ELM file in JavaScript Notation, as opposed to XML.
• Human-readable representation of the eCQM displays the eCQM content in a human-readable format directly in a web browser, Hypertext Markup Language (HTML) file (.html). This file does not include the underlying HQMF syntax, but the narrative content at the top of the HTML is an extraction from the HQMF header.
• Value sets and direct reference codes (DRCs) convey specific coded value(s) allowed for the data elements within the eCQM. Identification of value sets is via an object identifier (OID) and each value set includes several metadata elements describing the inclusion and exclusion criteria for the codes in the set. The value set includes a list of codes (i.e., the value set expansion code set) acceptable or valid for a specific data element in the measure, descriptors of those codes, the code system from which the codes are derived, and the version of the code system. DRCs are specific codes referenced directly in the eCQM logic to describe a data element or one of its attributes. Find value sets and DRCs in the Value Set Authority Center (VSAC).

Naming eCQMs

CMS created a unique “CMS eCQM Identifier” to name eCQM files. The naming convention adds the eCQM identifier assigned to the eCQM in the Measure Authoring Development Integrated Environment (MADiE) with the “eCQM Version Number.” “CMS” is in front of the number. The eCQM Version Number indicates the published version of the eCQM. For example, based on this naming convention, eligible clinician measure (Diabetes: Eye Exam) would be CMS131v9 for the ninth version of the measure. Use the eCQM Naming and Terminology Guide for guidance regarding common words, phrases, and technical terms used in conjunction with eCQMs.