This section provides an overview of the types of testing needed to assess measure evaluation criteria and outlines the process for development, implementation, and reporting of test plans, results, and associated artifacts. The content in this section is not meant to be prescriptive or exhaustive. Measure developers can use testing approaches other than what this section describes. Measure developers should always select the best method(s) for the measure under development and provide empirical evidence for the importance, feasibility, scientific acceptability, and usability and use. Measure developers should ensure they report their findings and rationales in their documentation, such as the Measure Information and Justification Form and Instructions.

Measure testing is an iterative process conducted concurrently with measure specification. Iterative testing provides measure developers an opportunity to refine draft specifications before finalization; augment or reevaluate earlier judgments about the measure’s importance; and assess feasibility, usability, and scientific acceptability of the measure.

Measure testing enables a measure developer to assess suitability of the quality measure’s technical specifications and acquire empirical evidence to help assess strengths and weaknesses of a measure with respect to the CMS consensus-based entity, Partnership for Quality Measurement Endorsement and Maintenance. To evaluate a measure, the measure developer should use information gathered through measure testing in conjunction with expert judgment. Measure testing refers to evaluating the draft specifications of quality measures, including components of the quality measures, such as the data elements, instruments, and performance score.