Skip to content
The Algorithm
The Algorithm/Knowledge Base/CMS Star Ratings
Healthcare Quality

CMS Star Ratings

The CMS quality measurement programs that tie Medicare Advantage and Part D plan payments to performance — and the data pipelines that determine whether a plan earns 4 stars or 2.

What You Need to Know

The CMS Star Ratings program evaluates Medicare Advantage (MA) and Part D prescription drug plans on a 1-to-5-star scale across multiple quality domains. For MA plans, the 2024 measurement year evaluates on measures grouped into domains including Staying Healthy (screenings, tests, vaccines), Managing Chronic Conditions, Member Experience (CAHPS), Member Complaints and Access, and Drug Plan Quality. Ratings directly affect plan payment: plans achieving 4+ stars receive quality bonus payments (QBPs) — a 5% payment increase applied to the plan's benchmark — and 5-star plans receive continuous enrollment periods. CMS introduced the Health Equity Index (HEI) for 2027 as a new star rating measure rewarding plans that reduce disparities in care for dual-eligible and low-income subsidy beneficiaries. The HEDIS (Healthcare Effectiveness Data and Information Set) measures, CAHPS survey data, HOS (Health Outcomes Survey), and administrative claims data are the primary inputs. Plans submit HEDIS data via NCQA's Interim Data Submission (IDS) system in hybrid and administrative methodologies.

The engineering reality of Star Ratings is that it is a data quality and analytics problem at scale. Administrative measure calculation requires joining claims data across multiple sources (medical claims, pharmacy claims, lab results, enrollment files) with specific measure logic defined in NCQA's HEDIS Technical Specifications — specifications that change annually and include intricate denominator/numerator exclusion logic. CAHPS survey data requires survey vendor integration and statistically valid sampling. Medical record review for hybrid measures requires abstraction workflows with inter-rater reliability monitoring. A common failure pattern: plan analytics teams running measure calculations on incomplete or delayed claims data, discovering Star Rating gaps too late in the measurement year to remediate through member outreach. Effective Star Ratings engineering requires near-real-time gap closure pipelines that identify care gap opportunities at the member level and route them to care management workflows with enough lead time to close gaps before the measurement year ends.

The Star Ratings program has undergone significant methodology changes that create year-over-year engineering instability. CMS introduced the Tukey outlier deletion method for setting cut points and the "guardrails" methodology to limit year-over-year rating changes — both of which make it impossible to calculate final ratings without CMS's cut point values, which are not released until after the measurement year. The transition to the HEI creates new data requirements around stratified measure performance by dual-eligible status. The Part D Star Ratings measures include medication adherence measures (PDC — Proportion of Days Covered) that require pharmacy claims timeliness standards the industry has struggled to meet. For plans using delegated provider groups for data submission, the Technical Performance Standards (TPS) require data submission infrastructure that can validate and ingest provider-submitted supplemental data.

How We Handle It

We build Star Ratings analytics platforms with HEDIS measure logic implemented as versioned, auditable calculation engines — updated annually with NCQA Technical Specification changes — deployed against real-time claims feeds to provide continuous gap closure intelligence rather than year-end snapshots. Our member outreach integration layer connects gap identification to care management workflows with priority scoring that accounts for measure weight, member accessibility, and remaining measurement year days. We maintain HEDIS measure audit trails that support NCQA IDSS submission validation and audit defense.

Services
Service
Healthcare Technology
Service
Data Engineering & Analytics
Service
Compliance Infrastructure
Related Frameworks
HEDIS Technical Specifications
NCQA Accreditation
CAHPS Survey Protocols
CMS Medicare Advantage Final Rule
DECISION GUIDE

Compliance-Native Architecture Guide

Design principles and a structured checklist for building software that is compliant by default — not compliant by retrofit. Covers data architecture, access controls, audit trails, and vendor due diligence.

§

Compliance built at the architecture level.

Deploy a team that knows your regulatory landscape before they write their first line of code.

Start the conversation
Related
Service
Healthcare Technology
Service
Data Engineering & Analytics
Service
Compliance Infrastructure
Related Framework
HEDIS Technical Specifications
Related Framework
NCQA Accreditation
Related Framework
CAHPS Survey Protocols
Platform
ALICE Compliance Engine
Service
Compliance Infrastructure
Engagement
Surgical Strike (Tier I)
Why Switch
vs. Accenture
Get Started
Start a Conversation
Engage Us