Health plans face three converging regulatory shifts: dual Medicare Physician Fee Schedule conversion factors, evolving maternity billing methodologies, and interoperability requirements under CMS-0057-F. Meeting compliance deadlines alone won’t prepare organizations for these changes. Readiness requires evaluating data, workflows, and cross-functional alignment well before implementation dates arrive.
Key Takeaways
- Two Medicare Physician Fee Schedule (PFS) conversion factors now apply based on Qualifying Alternative Payment Model (APM) Participant (QP) status, and the Centers for Medicare & Medicaid Services’ (CMS) CY 2027 proposed rule widens the gap between QP and non-QP payment rates.
- Maternity billing methodologies are shifting away from traditional global billing models, with potential effects across claims, payment, and care management workflows.
- The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) sets implementation deadlines of January 1, 2026, and January 1, 2027, for data exchange and application programming interface (API) requirements.
- Readiness depends on alignment across compliance, operations, technology, and business teams, not just meeting individual deadlines in isolation.
- Health plans that begin readiness assessments now reduce implementation risk later.
Three Regulatory Developments Reshaping Health Plan Operations
In September, HealthEdge® held its monthly Regulatory Compliance User Group discussion, bringing together health plan compliance and operations leaders to examine what these changes require in practice. Three topics anchored the conversation:
- Dual fee schedule implementation
- Maternity billing, and
- CMS Interoperability and Prior Authorization Final Rule
Health plans are managing a regulatory calendar that doesn’t pause for operational convenience. Reimbursement methodologies are splitting into separate payment tracks. Maternity billing approaches are under active reconsideration. Interoperability and prior authorization requirements carry firm federal deadlines. And each of these developments demands more than a compliance checklist.
A health plan can update a system to satisfy a new rule and still face claims errors, provider confusion, or reporting gaps months later. True readiness means the organization has tested the downstream effects of a change before it takes effect, not after.
This article examines three regulatory developments reshaping health plan operations and outlines what proactive preparation looks like for each.
What Does Dual Conversion Factor Readiness Mean for Health Plans?
Since CY 2026, Medicare has applied two separate conversion factors under the Physician Fee Schedule: one for Qualifying APM Participants (QPs) and one for physicians and practitioners who don’t meet QP thresholds. This split is a statutory requirement, and the gap between the two rates is growing.
The CY 2027 Medicare Physician Fee Schedule proposed rule outlines the following proposed updates:
- CMS proposed a QP conversion factor update of +0.75%, compared to +0.25% for non-QPs.
- The proposed CY 2027 QP conversion factor of $33.17 reflects a projected decrease of $0.40, or 1.19%, from the current rate of $33.57.
- The proposed non-QP conversion factor of $32.84 reflects a larger projected decrease of $0.56, or 1.68%, from $33.40.
Beginning with Payment Year 2026, QPs also receive the following, according to CMS Quality Payment Program guidance:
- A higher conversion factor applied directly to claims.
- The lump-sum APM Incentive Payment, available for 2017 through 2024 QP performance periods.
For health plans, this isn’t a single configuration update. Provider qualification status must be managed accurately and kept current. Systems need updated support for CMS file formats. Annual provider participation data has to load correctly, and claims adjudication workflows have to apply the correct conversion factor to every claim without exception. Including Medicare payment adjustment logic adds yet another layer of complexity.
Health plans that review pricing and claims processes well ahead of implementation deadlines reduce the risk of misapplied rates and downstream payment disputes.
How Are Maternity Billing Methodologies Evolving?
The industry continues to evaluate new approaches to maternity billing, with movement away from traditional global maternity billing toward phased billing models that reflect care delivered at distinct points in the pregnancy and postpartum period. Guidance in this area is still evolving, which makes early assessment more valuable than ever.
A shift of this kind doesn’t stay contained to claims operations. Payment models, provider workflows, reporting structures, authorization processes, and care management activities can all be affected. A health plan that waits until a final methodology is published to begin mapping these dependencies will have less time to test changes before they reach production.
Understanding operational dependencies early, even while guidance is still forming, gives compliance, claims, and care management teams a head start on identifying where phased billing would intersect with existing workflows. That assessment work doesn’t require a finalized rule to begin.
Why Is Interoperability a Readiness Initiative, Not Just a Compliance Deadline?
The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F), finalized January 17, 2024, expands on the 2020 CMS Interoperability and Patient Access rule and adds new requirements for data exchange and prior authorization. Impacted organizations must implement most provisions by January 1, 2026, with API requirements due primarily by January 1, 2027.
Health plans are approaching these requirements from different starting points. Some have mature data exchange infrastructure already in place. Others are building prior authorization automation largely from scratch. That variation in maturity makes testing and planning essential, not optional. A health plan that waits to test API connections until close to the deadline risks discovering integration issues with little time left to resolve them.
Interoperability readiness also depends on people, not just systems. Claims, IT, compliance, and provider relations teams all touch some part of the prior authorization and data exchange process. Early, cross-functional planning surfaces conflicts in ownership and process before they become implementation blockers.
What Does Readiness Beyond Compliance Look Like?
Each of these regulatory developments touches more than one function inside a health plan. Dual conversion factors affect claims and provider data management. Maternity billing changes touch claims, authorization, and care management. Interoperability requirements span IT, compliance, and operations. Treating any of these as a single-department compliance project limits an organization’s ability to see the full operational picture.
Readiness means compliance, operations, technology, and business teams work from the same timeline and the same understanding of impact. It means testing workflows before a deadline forces the issue. And it means building the internal muscle to repeat this process for the next regulatory change, because another one is already on the way.
Health plans that build this kind of cross-functional discipline don’t just avoid penalties. They reduce the operational disruption that follows a rushed implementation, and they strengthen their ability to respond to whatever regulatory change comes next.
Building Readiness for What Comes Next
Dual conversion factors, maternity billing changes, and interoperability requirements each carry their own deadlines and their own operational demands. Taken together, they represent a broader pattern: regulatory change in healthcare is constant, and compliance alone doesn’t prepare an organization for it.
Health plans that assess provider data practices, map workflow dependencies, and align compliance, operations, and technology teams now will face each of these transitions with less risk and more control. The work doesn’t wait for a final rule to be worth starting.
Is your health plan ready for the January 1, 2027 regulatory deadlines? Make sure your teams are well prepared for the new prior authorization and interoperability APIs. Read the article from our regulatory experts: Six Regulatory Developments Health Plans Can’t Afford to Miss Before January 1, 2027.
Frequently Asked Questions about Dual Medicare Physician Fee Schedules, Maternity Billing, and CMS Interoperability Requirements
What is the difference between QP and non-QP conversion factors?
Qualifying APM Participants (QPs) meet statutory thresholds for participation in an Advanced Alternative Payment Model (APM) and receive a separate, generally higher, Medicare Physician Fee Schedule conversion factor than non-QPs. The gap between the two rates has widened under the CY 2027 proposed rule.
When do health plans need to comply with CMS-0057-F?
Most provisions of the CMS Interoperability and Prior Authorization Final Rule took effect January 1, 2026. API-specific requirements are due by January 1, 2027.
Why is maternity billing methodology changing?
The industry is reconsidering traditional global maternity billing in favor of phased billing models that reflect care delivered at distinct points during pregnancy and postpartum care. Regulatory guidance in this area continues to evolve.
What’s the biggest risk of treating these changes as compliance-only projects?
Addressing a regulatory change within a single department, without testing downstream effects on claims, operations, and provider workflows, increases the likelihood of errors, delays, and rework after the deadline passes.
How can health plans start preparing now?
Begin by reviewing provider data management practices, mapping where a given regulatory change intersects with existing workflows, and bringing compliance, operations, technology, and business stakeholders into the same planning process before implementation deadlines arrive.