Why Automated Clinical Data is the Key to Surviving the Next Wave of CMS Regulations

Short answer: Healthcare interoperability is no longer a back-office IT project; it’s the operational backbone that determines whether a health plan can meet CMS’s tightening compliance deadlines, defend its Star Ratings, and keep pace with FHIR-based clinical data exchange requirements. 

Plans that automate clinical data exchange can turn compliance from a cost center into a competitive advantage. Plans that don’t are already falling behind.

The regulatory reality health plans are facing in 2026

If you lead compliance, quality, or IT strategy at a health plan, you’ve felt the pace of change accelerate. Three overlapping regulatory tracks are converging on payers at once:

• CMS-0057-F (the 2024 Interoperability and Prior Authorization Final Rule) required Medicare Advantage organizations, Medicaid and CHIP managed care plans, and Qualified Health Plan issuers on the federal exchanges to stand up FHIR-based Patient Access, Provider Access, Provider Directory, and Prior Authorization APIs, with prior authorization operational requirements taking effect January 1, 2026.
• CMS-0062-P: The 2026 proposed rule was released in April extending those same interoperability standards to prior authorization for drugs, tightens decision timeframes, and adds new payer reporting requirements, including publishing API endpoints and FHIR capability statements directly to CMS.
• ONC’s HTI-1 rule: Made USCDI v3 data classes (including health insurance information, clinical tests, diagnostic imaging, and care team members) mandatory for certified health IT as of January 2026, changing what data payers can expect to receive electronically from provider systems.

None of these rules exist in isolation. Each one assumes health plans can reliably send, receive, and act on structured clinical data in near real time. That assumption is where most plans’ legacy data infrastructure starts to break down.

The other shoe: Star ratings are getting harder, not easier

While the interoperability rules are tightening, CMS also overhauled the Medicare Advantage and Part D Star Ratings methodology for 2026 and the changes cut in two directions at once.

On one hand, CMS eliminated roughly a dozen administrative measures and walked back the planned Health Equity Index reward, which sent billions of dollars in projected bonus payments back toward plan sponsors. On the other hand, CMS explicitly reweighted the system to reduce the influence of patient experience and access measures (dropping from a 4x to a 2x weight) and increase reliance on measurable clinical outcomes: chronic disease control, medication adherence, and new measures like Kidney Health Evaluation for Patients with Diabetes and an upcoming Depression Screening and Follow-Up measure.

That shift has a direct data consequence: outcome measures can’t be attested to or estimated. They have to be proven with clinical data, such as lab values, diagnoses, care gaps closed, medications reconciled, that is pulled from the provider systems where care actually happens, not just from claims.

At the same time, cut points have tightened. Only 18 contracts earned 5 stars in the 2026 ratings cycle, up slightly from 7 the year before but still far below the 38 contracts that hit 5 stars in 2024. More than a third of MA members are currently enrolled in plans rated below 4 stars, the threshold that unlocks meaningful Quality Bonus Payments. In a market where average ratings have declined from roughly 4.37 stars in 2022 to under 4.0 today, the margin for error has essentially disappeared.

Put simply: the same clinical data pipelines that CMS now requires for interoperability compliance are the pipelines health plans need to defend their Star Ratings. Regulatory reporting and quality performance have quietly become the same problem.

Why manual and semi-automated data exchange can’t keep up

Most health plans didn’t build their data infrastructure for this moment. Clinical data often arrives as:

• Faxed or scanned records that require manual abstraction
• Point-to-point HL7v2 feeds that vary by hospital system and rarely map cleanly to current standards
• Batch files that update days or weeks after a care event
• Claims-only views that miss lab results, imaging findings, or care team changes entirely

Every one of those gaps now shows up somewhere CMS is watching: a missed prior authorization turnaround (72 hours for expedited, seven calendar days for standard non-drug requests under CMS-0057-F), a Patient Access API metric that looks stale, or a HEDIS/DQM measure that can’t be substantiated with timely clinical evidence.

Manual reconciliation might have been passable when there were fewer measures and softer deadlines. It isn’t anymore. CMS is explicitly steering the entire ecosystem toward electronic clinical quality measures and standardized FHIR-based exchange. Which means plans relying on manual data wrangling aren’t just slower, they’re structurally out of step with where the regulatory floor is heading.

What automated clinical data exchange actually looks like

“Automation” doesn’t mean replacing your compliance and quality teams; it means giving them clinical data they can trust, as close to real time as possible, without a small army re-keying PDFs. 

In practice, a modern automated data exchange platform operates through five core capabilities: 

1. FHIR-native ingestion, not FHIR wrappers. It consumes USCDI v3 data classes, health insurance information, clinical tests, diagnostic imaging reports, care team members, directly through US Core FHIR profiles rather than screen-scraping legacy formats and bolting a FHIR shape onto them after the fact.
2. Bidirectional, standards-based APIs. It supports the full interoperability API stack CMS expects: Patient Access, Provider Access, Provider Directory, and Prior Authorization APIs built on the relevant Da Vinci implementation guides (PAS for prior auth, CRD for coverage requirements, DTR for documentation templates, PDex for care data exchange between payers).
3. Continuous data validation, not point-in-time submission. It normalizes and validates clinical and claims data on an ongoing basis so that care gaps, adherence issues, and quality measure evidence are visible before a reporting deadline, not discovered during it.
4. Bulk data capability for population health. It leverages FHIR bulk data access so population-level clinical data, (the kind needed for HEDIS abstraction, risk stratification, and equity-related analysis) doesn’t require manual chart pulls at scale.
5. Payer-to-payer continuity. It automates the Payer-to-Payer Data Exchange API so that when members switch plans, clinical history follows them. Reducing duplicate testing, care gaps at enrollment, and the data blind spots that hurt both quality scores and member experience.

Turning compliance infrastructure into a Star Ratings advantage

The plans that will come out ahead in this environment aren’t necessarily the ones spending the most on compliance, they’re the ones treating clinical data exchange as shared infrastructure rather than a series of separate regulatory checkboxes. A single, automated, standards-based data layer can simultaneously:

• Satisfy CMS-0057-F and CMS-0062-P reporting obligations
• Feed real-time care gap and adherence data to quality teams for Star Ratings measures
• Reduce prior authorization turnaround time, which increasingly shows up in both regulatory metrics and member-experience outcomes
• Support Health Equity-related stratification even as CMS’s own equity reward mechanisms remain in flux
• Shorten the lag between a clinical event and its appearance in analytics, risk adjustment, and reporting systems

That’s the strategic case for automated clinical data exchange: it’s not a separate line item next to Star Ratings strategy, it’s the foundation that Star Ratings strategy now depends on.

Frequently asked questions

What is healthcare interoperability? Healthcare interoperability is the ability of different health IT systems (EHRs, payer platforms, health information exchanges, and patient-facing apps) to exchange, interpret, and use clinical and administrative data without manual intervention, typically through standards like HL7 FHIR.

What is clinical data exchange? Clinical data exchange refers to the transmission of patient health information (diagnoses, lab results, medications, care plans, imaging reports) between healthcare organizations, payers, and patients in a structured, standardized format so the receiving system can use it directly.

How does interoperability affect Medicare Advantage Star Ratings? CMS has shifted Star Ratings weighting toward clinical outcome measures and away from administrative and experience measures, which means plans need timely, standardized clinical data (not just claims) to demonstrate performance. Automated, FHIR-based data exchange is what makes that possible at scale.

What are the main CMS interoperability rules health plans need to track? The two most relevant are CMS-0057-F (the 2024 Interoperability and Prior Authorization Final Rule, largely effective January 1, 2026) and CMS-0062-P (the 2026 proposed rule extending similar requirements to drug prior authorizations, with most provisions targeted for October 1, 2027 if finalized). ONC’s HTI-1 rule, which mandates USCDI v3 data classes in certified health IT, also shapes what data payers can expect to receive.

Do these rules apply to all health plans? The CMS interoperability rules apply to Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities, and Qualified Health Plan issuers on the federally facilitated exchanges. Requirements and timelines vary by payer type, and small health plans often receive extended compliance windows.

See what Best in KLAS payer-provider data exchange looks like

Building this kind of infrastructure in-house is a multi-year undertaking and CMS’s timelines don’t leave that much room. That’s why more health plans are turning to partners who have already solved the hard parts of automated, standards-based clinical data exchange.

Moxe Health was named #1 Best in KLAS for Payer-Provider Data Exchange in 2026, recognized for the reliability and clinical accuracy of its EHR-agnostic exchange network. 

See how we help leading health plans automate clinical data exchange.