Champ AI
November 20, 2026

CMS-0057-F for Billing Companies: What Changes in 2026 and 2027, and What Doesn't

CMS-0057-F covers Medicare Advantage, Medicaid, CHIP and exchange plans. Here is what changed in 2026, what arrives in 2027, and what billing teams still handle by portal and phone.

Trevor Tang
Trevor TangFounding GTM/Solutions Engineer

Updated November 19, 2026, based on CMS, HHS, the Federal Register, the eCFR and CAQH as of that date.

CMS-0057-F, the CMS Interoperability and Prior Authorization final rule, changes how a defined group of payers handles prior authorization. In 2026 those payers had to start meeting decision deadlines, giving specific denial reasons and posting prior authorization metrics. In 2027 they must open new APIs, including a Prior Authorization API that can take a request and return a decision.

The rule covers Medicare Advantage, Medicaid and CHIP (fee-for-service and managed care) and Qualified Health Plans on the federal exchanges. It doesn't cover employer plans, traditional Medicare or drugs, and it doesn't touch claim status, remittances or claim attachments. For a billing company, that means the rule improves part of the prior auth workload and leaves the rest of the payer-facing work where it is today: portals, phone and fax.

If you're new to how a clearinghouse fits into this work, start with our guide to what a medical billing clearinghouse handles and what still needs a portal.

The rule applies to five payer types, not to every plan

CMS's fact sheet on CMS-0057-F names the "impacted payers": Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities, and QHP issuers on the federally facilitated exchanges.

Commercial employer plans are not on that list. In the final rule in the Federal Register, CMS answered commenters who asked it to include them. It said its authority here reaches issuers on the exchanges it runs, not health insurers and group health plans outside them. It added that nothing stops those payers from adopting the rule voluntarily, and it encouraged them to. Traditional Medicare fee-for-service isn't an impacted payer either. The rule says its requirements "do not directly pertain to Medicare FFS," though CMS said it intends Medicare FFS to lead on the same kinds of data exchange.

The rule applies by line of business. One carrier can run Medicare Advantage, Medicaid managed care and employer plans, and only some of those lines are covered. When you sort a client's payer mix, sort it by plan type.

What changed in 2026: deadlines, denial reasons and public metrics

The first set of requirements took effect in 2026. CMS calls them operational provisions, and they don't depend on the new APIs.

Impacted payers, except QHP issuers on the exchanges, must decide expedited requests within 72 hours and standard requests within seven calendar days. The details, extensions and drug rules are in our guide to prior authorization turnaround times.

Starting in 2026, impacted payers must give a specific reason when they deny a prior authorization, "regardless of the method used to send the prior authorization request." The fact sheet says the decision may come by portal, fax, email, mail or phone. For Medicare Advantage the requirement is in 42 CFR 422.122(a). If an impacted payer's denial gives no specific reason, ask for one before you appeal.

Impacted payers must also post prior authorization data on their websites each year. The first set was due March 31, 2026. It includes the list of items and services that need prior authorization, approval and denial rates, and average and median decision times. These pages are a free way to see which plans in your book approve slowly or deny often.

What arrives in 2027: the Prior Authorization API and provider data access

The rule's API requirements start "in 2027," but the exact date depends on the payer type. Per the final rule:

  • Medicare Advantage organizations and state Medicaid and CHIP fee-for-service programs: by January 1, 2027.
  • Medicaid managed care plans and CHIP managed care entities: by the rating period beginning on or after January 1, 2027.
  • QHP issuers on the federally facilitated exchanges: for plan years beginning on or after January 1, 2027.

Under 42 CFR 431.80(c), a state can apply for a one-time, one-year extension for its Medicaid fee-for-service program. A state with at least 90 percent of its Medicaid beneficiaries in managed care can request an exemption for its fee-for-service program. QHP issuers have an exceptions process.

The Prior Authorization API must list the items and services (excluding drugs) that need prior authorization, identify the documentation the payer requires, and support a request and response. The response must say whether the payer approved the request (and when the authorization ends), denied it with a specific reason, or needs more information.

The Provider Access API lets in-network providers pull a patient's claims and encounter data, clinical data and prior authorization information from the payer. The payer must attribute the patient to the provider, and patients can opt out. Under the Medicare Advantage rule, the payer must make the data available no later than one business day after the provider's request.

The rule also added an "Electronic Prior Authorization" measure for MIPS eligible clinicians. The CY 2027 Physician Fee Schedule final rule made it optional for the 2027 performance period, worth 10 bonus points for a "yes," and required starting in 2028. A "yes" means requesting at least one prior authorization through a Prior Authorization API using certified EHR technology. If you handle MIPS reporting for clients, plan for it as optional in 2027 and required in 2028.

The API reaches you through the provider's systems

The rule is written around providers and their technology, not billing companies. The Federal Register describes providers querying a payer's documentation requirements "directly from the provider's system." The MIPS measure counts requests made using certified EHR technology. The Provider Access API goes to in-network providers the payer can authenticate and attribute patients to.

So whether your team can use these APIs depends on your clients' EHR and practice management vendors, and on how those vendors grant access to an outside billing team. Ask each vendor three questions: which payers' APIs it will connect to and when, whether billing staff working under the provider's account can use the connection, and how status and denial reasons will show up in the work queue.

The X12 278 doesn't go away. HHS announced enforcement discretion for covered entities that build an all-FHIR Prior Authorization API without the 278. The fact sheet says payers can offer FHIR only, FHIR and X12 together, or an X12-only transaction. In April 2026 CMS also proposed a rule that would adopt FHIR standards for HIPAA prior authorization transactions. It isn't final as of this update. Expect a mix, and confirm with each payer which route it supports before you change how your team submits.

What doesn't change for billing companies

  • Commercial employer plans aren't impacted payers. Their prior auth runs through whatever channels each plan offers: portal, phone, fax or a 278 where supported.
  • The rule excludes drugs from the API, the denial reason requirement and the metrics. Pharmacy and medical-benefit drug requests keep their own processes. The April 2026 proposed rule would extend many of these requirements to drugs, but it isn't final.
  • The rule creates four APIs: Patient Access, Provider Access, Payer-to-Payer and Prior Authorization. None of them is a claim status API, and the Provider Access API leaves out remittances. Claim follow-up stays on the 276/277, the portal and the phone. Our guide to payers without an API covers that fallback order.
  • CMS-0057-F doesn't set an attachment standard. A separate rule, CMS-0053-F, adopts the X12 275 for claims attachments, with compliance due May 26, 2028. CMS dropped prior authorization attachments from that rule. Until then, supporting documents go however each payer accepts them.

Payer readiness is uneven. The 2025 CAQH Index reports that 40% of medical plan prior authorizations were fully electronic. In a CAQH FHIR pilot survey, 63 percent of medical plans were still developing their electronic prior authorization FHIR APIs, and only 20 percent of providers had begun implementation.

How to plan for CMS-0057-F

  1. Tag each client's payers by line of business: Medicare Advantage, Medicaid fee-for-service, Medicaid managed care, exchange QHP, employer plan, traditional Medicare.
  2. For each impacted payer, pull its posted prior authorization metrics and its list of services that need authorization.
  3. Track denial reasons from impacted payers, and flag any denial that arrives without a specific reason.
  4. Confirm each payer's API go-live date. Medicaid managed care dates follow the plan's rating period, and a state's fee-for-service program may have an extension or exemption.
  5. Ask your clients' EHR and practice management vendors how and when they'll connect to these APIs, and whether your staff can use the connection.
  6. Keep portal, phone and fax capacity for employer plans, drugs, claim status and attachments. Those volumes don't shrink because of this rule.

Frequently asked questions

Does CMS-0057-F apply to commercial insurance?

Not to employer group plans or commercial plans sold off the federal exchanges. It applies to Medicare Advantage, Medicaid and CHIP, and QHP issuers on the federally facilitated exchanges. CMS encouraged other payers to adopt it voluntarily, so ask each commercial plan what it plans to offer.

Does it apply to traditional Medicare?

No. CMS says the requirements "do not directly pertain to Medicare FFS." Watch for separate announcements from CMS and your Medicare Administrative Contractor.

When is the Prior Authorization API required?

January 1, 2027, for Medicare Advantage and Medicaid and CHIP fee-for-service programs. For Medicaid managed care and CHIP managed care, it's the rating period beginning on or after that date. For exchange QHPs, it's plan years beginning on or after that date. Extensions, exemptions and exceptions can push some payers later.

Will payers stop taking prior auths by portal or fax?

The rule doesn't require that. The denial reason requirement applies however the request was sent, and CMS lists portal, fax, email, mail and phone as ways a decision can be communicated. Check each payer's provider manual for its own channel rules.

Can a billing company use the Provider Access API?

It's for in-network providers the payer authenticates and attributes patients to. A billing company would usually reach it through the provider's systems. Confirm access with the client's EHR vendor and the payer.

Working prior auths across portals and phone for most of your payers?

Champ automates payer portal work like authorizations and eligibility checks, and it can handle the document and phone work around them. We set it up and run it, so your team sees only the finished results. If 2027 still leaves most of your prior auth volume in portals, learn more here.

This post is general information, not legal, compliance or billing advice. Rules vary by payer, plan type and state and change often, so confirm with each payer, your state Medicaid agency or CMS before acting. Champ is not affiliated with or endorsed by CMS, HHS or CAQH.

Continue reading

See all

Do the work of fifty
without hiring one more.

Eligibility
Verification
Claims
Payroll
Carrier check-in
Patient intake
Benefits
Credentialing
Credentialing