Measure Lifecycle
Measure specification follows the conceptualization stage, when the measure developer determines the initial intent of the measure based on clinical practice guidelines or a patient-reported outcome measure, and evidence from the environmental scan. Development of measure specifications is an iterative process throughout the Measure Lifecycle, with specifications informing and being informed by later stages of the measure development process, particularly measure testing.
Measure Specification & Measure Testing
As a measure developer moves from alpha (formative) testing to beta (field) testing, the specification becomes more fully developed. As a result of testing, specifications continue to evolve, becoming more detailed and precise.
- For measures based on electronic, administrative, or claims-based data, the measure developer may provide draft specifications to the programming staff responsible for data retrieval and for developing programming logic necessary to produce the measure. Programmers will assess feasibility of the specifications as written and may provide feedback.
- For measures based on chart abstraction, the measure developer develops and tests data collection tools.
Paperwork Reduction Act Guidance for CMS Measure Developers
Though most measure development activities are exempt from the Paperwork Reduction Act (PRA) due to the Medicare Access and Children's Health Insurance Program Reauthorization Act (MACRA), some CMS developers may be required to prepare a PRA package. CMS measure developers should discuss this requirement with their Contracting Officer's Representative. The Blueprint Contractual Guidance and Considerations —located in the password-protected Measure & Instrument Development and Support (MIDS) Library—has additional details for CMS MIDS contractors. Users must have an invitation to view the MIDS Library.
