CMS Interoperability & Prior Authorization Final Rule

The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) is a federal regulation published in February 2024 that builds on earlier CMS interoperability requirements. It creates new mandates for how health plans exchange data with providers and patients — specifically through standardized, FHIR-based APIs.

This is not a suggestion or a guideline. It is a final rule with enforcement dates. CMS is requiring that Medicare Advantage organizations, Medicaid managed care plans, CHIP managed care entities, and Qualified Health Plan issuers on the federal exchanges all comply.

The rule has several interconnected requirements, but three are most relevant to home health operations:

• Prior Authorization API (PARDD): Payers must build a FHIR-based API that lets providers submit prior authorization requests electronically, check status in real time, and receive decisions faster. For urgent requests, payers must respond within 72 hours. For standard requests, 7 calendar days. This replaces the current black-box process of portal submissions and phone follow-ups.
• Payer-to-Payer Data Exchange: When a patient switches health plans, the old plan must transfer up to 5 years of claims and clinical data to the new plan via API. This means the new payer has full context on prior authorizations, treatment history, and utilization — reducing re-authorization burden on providers.
• Patient Access API Enhancements: Payers must include prior authorization decisions, pending requests, and denial reasons in the data available to patients through their Patient Access API. Patients will have real visibility into their own authorization status.

The rule directly regulates payers, not providers. But the operational impact flows directly to home health agencies.

When payers implement Prior Authorization APIs, agencies that can connect to those APIs will submit authorizations electronically, check status in real time, and receive faster decisions. Agencies that cannot connect will continue using the old process — faxes, portals, and phone calls — while their competitors move faster.

The rule affects Medicare Advantage, Medicaid managed care, CHIP, and federal exchange plans. Traditional Medicare fee-for-service is not subject to this specific rule, though CMS has signaled broader interoperability requirements are coming.

Prior authorization is one of the biggest operational pain points in home health. The current process is slow, opaque, and labor-intensive. The average prior auth takes 11 business days to resolve. Roughly 30% of initial requests are denied. Coordinators spend hours each week on phone holds and portal logins just to check status.

This rule doesn't fix all of that overnight — but it creates the infrastructure for a fundamentally different workflow. Agencies with software that can connect to payer APIs will:

• Submit prior auth requests electronically in minutes instead of hours
• Track authorization status in real time instead of calling payers
• Receive decisions in 72 hours (urgent) or 7 days (standard) instead of weeks
• Build an audit trail automatically instead of reconstructing it from email threads
• Reduce denial rates through pre-submission validation against payer rules

The deadline is January 1, 2027. That sounds far off, but the operational changes agencies need to make take time. Here is what forward-thinking agencies are doing now:

• Audit your current prior auth workflow: How many hours per week does your team spend on authorizations? What is your denial rate? What is your average time-to-decision? These numbers are your baseline.
• Ask your software vendor about FHIR support: Can your current system connect to payer Prior Authorization APIs? If the answer is vague, that is your answer.
• Evaluate your tech stack for interoperability readiness: The prior auth API is just the beginning. CMS is moving toward a fully API-driven healthcare ecosystem. Systems built on FHIR R4 from the ground up will adapt. Systems that bolt on FHIR as an afterthought will struggle.
• Start the conversation with your payer partners: Which of your top payers are building their Prior Authorization APIs now? What format will they expect? Early coordination reduces friction at go-live.

This rule is part of a broader federal push toward healthcare interoperability. ONC's HTI-1 rule is already updating certification criteria. HTI-4 will add TEFCA requirements and e-prescribing standards through 2027-2028. The direction is unmistakable: healthcare is moving from fax-and-phone coordination to API-driven data exchange.

Agencies that treat January 2027 as just another compliance checkbox will miss the strategic opportunity. The real advantage goes to agencies that use this transition to modernize their operations — not just their prior auth workflow, but their entire approach to intake, scheduling, clinical documentation, and care coordination.

2027 is not a threat. It is a line in the sand. The question is whether your agency will be ready to operate on the other side of it.