Policy

CMS Proposes Electronic Prior Authorization in MA Contracts

A new Medicare Advantage proposal would require network providers to use plans' electronic prior-authorization connections from January 2028. OT clinics have preparation questions to raise.

Medicare AdvantagePrior authorizationProposed rulePractice management
Conceptual illustration of a clinician and an older adult reviewing information on a laptop at a clinic reception desk
Conceptual illustration of a clinic conversation; the screen does not depict a prior-authorization system.

CMS's November 20 Medicare Advantage proposal, fact sheet, and public-inspection rule text

An occupational therapy evaluation can be ready while the request for permission to treat still needs another attachment. A new Medicare Advantage proposal would make the electronic route for that request part of a clinic's network contract, giving practice owners a reason to examine how their software communicates with each plan.

In brief

  • CMS proposes a January 1, 2028 start for contract requirements to use plans' FHIR-based prior-authorization APIs.
  • The proposal covers in-network providers furnishing non-drug items or services that require prior authorization, with annual connection testing.
  • Small practices can document software, staffing, and cost barriers for CMS; the requirements remain proposed.

A connection becomes a contract term

CMS released the proposal November 20 as part of its contract year 2028 Medicare Advantage and Part D rulemaking. Its fact sheet describes a requirement for network contracts to direct providers to submit authorization requests and supporting documentation through the plan's FHIR-based Prior Authorization API. An API is a connection through which software systems exchange information.

The public-inspection text puts the proposed start at January 1, 2028. As drafted, the provision applies to in-network providers furnishing non-drug items or services for which the plan requires authorization. An OT clinic in that position would need to examine how its submission workflow meets the contract term.

Plans would also have to include annual testing in provider contracts. The test would check that a request can travel from the provider to the plan and a response can return. For a clinic, that makes a successful round trip a useful question to put to its software vendor.

Start with one ordinary request

Practice owners could take a recent, de-identified OT authorization through the existing workflow. Record who prepares it, where the evaluation and plan of care are attached, how receipt is confirmed, and where the decision appears. Count staff time spent moving the same information between systems.

Then ask the vendor and the plan which connection would handle that request, whether attachments and responses arrive in the clinical record, who would arrange annual testing, and what implementation would cost. A general assurance that software supports electronic authorization leaves those operational details unanswered.

Small-practice constraints belong in the record

CMS explicitly seeks input on the barriers facing rural providers, small groups, and individual practices. Its questions include infrastructure, staffing, financial support, extra implementation time, and possible hardship exceptions. These are matters for comment; the questions do not establish an exemption.

A small OT practice can make that feedback concrete with upgrade estimates, available technical support, and the time needed to test connections across its plans. The rule remains proposed. The Federal Register lists November 25 as its scheduled publication date; consult the rule record for the final comment instructions and deadline.

Decision use

How to use this analysis

Read the source documents and linked resources to check which findings apply to your situation.

Compare OT documentation tools1

Use the tool comparison as a starting point, then verify each vendor's authorization connections directly.

Open next step