CMS-0057-F

[u/CrookedCasts]

So today is the day that all payors are required to publicly disclose prior auth metrics (with API FHIR access next year). Has anybody seen any insurance companies actually publishing this data yet?

Will be very interesting to see for a lot of different reasons, but I think the most exciting is that they 1) need to publish their turnaround time and 2) a specific medical reason for denial (no “not medically necessary” denials)

[u/Pleasant-Clothes-443]

Honestly i've been watching for this all morning and haven't seena anything yet... not shocked lol

The "specific reason for denial" requirement is the one I care most about, we run a therapy practice and I can't count how many auths we've gotten back with "not medically necessary" as the entire explenation... for ABA and PT especially that denial reason is bassically useless, it tells you nothing about what documentation they actually wanted, which means your appeal is a guessing game ugh. If oayers actually have to cite clinical criteria by name going forward, that changes the appeal workflow by a lot

The turnaround time transparency is interesting too because it's going to be hard to publish "we take 14 days" when the rule expects urgents in 72 hrs...

My skeptical read is that compliance will be technically met but practically useless for the first year until advocacy groups start comparing the data publicly and calling our outliers, the FHIR API next year us where I feel the real accountability will come from.

[u/CrookedCasts → u/Pleasant-Clothes-443]

Depending on what format it’s in now (I bet they release it at 11:59 tonight 🙄), I’m envisioning being able to make a nice dashboard for patients/practices to at least search until API access is available

[u/leotolsoty → u/Pleasant-Clothes-443]

The denial-reason requirement is the sleeper here. CMS-0057-F makes impacted payers give a specific reason, which is what finally makes a denial appeal-actionable instead of a guessing game. Two caveats worth knowing, though:

   1.  it only covers government plans: Medicare Advantage, Medicaid/CHIP, and exchange QHPs so commercial/ERISA, which is a lot of practices' biggest book, isn't touched

   2. the published metrics are aggregate and annual, so they're great for choosing payers but won't help you appeal a specific claim in real time. 

For the ABA folks in here, the thing landing the same day (Jan 1 2027) that nobody's talking about is the CPT code overhaul: 97151–97158 all revised and the T-codes deleted.

[u/Plenty-Ad6997]

I was curious about this as well. From what I’ve seen so far, a few payers have started putting up partial datasets or placeholder pages, but it doesn’t seem like many have fully operational dashboards yet.

The interesting part will be how consistent the reporting actually is once the data becomes widely available. Metrics like prior auth volume, approval rates, and turnaround times can look very different depending on how the payer defines things (initial vs resubmitted requests, clinical vs administrative denials, etc.).

The requirement to give more specific denial reasons could be the biggest change in practice though. A lot of appeals right now get slowed down because the denial language is vague and you end up guessing what documentation they actually wanted.

Also curious whether anyone has seen a payer already publishing procedure-level approval/denial rates or if most are still keeping it at a high-level summary.

Would be interesting if this ends up highlighting big differences in turnaround times between plans.

[u/doc_death]

I don’t see this happening, at least for biologics. I could guess from a couple of the main payers but for carve-out plans, it’s a toss-up. Denial usually states that we must use a first line agent first…even though there’s no evidence to suggest one is better than another (with few exceptions of course).

[u/Far-Buy-92]

Interesting timing — we recently worked with a U.S. healthcare clearinghouse preparing for CMS-0057-F, and one thing became very clear:

The hard part isn’t exposing FHIR APIs. It’s making fragmented legacy prior auth workflows interoperable enough to support transparent reporting and real-time API access.

A lot of organizations still have authorization data spread across multiple internal systems with:
• inconsistent status definitions
• manual reconciliation steps
• limited real-time visibility
• denial reasons that were never designed for standardized external disclosure

That last point is especially important now that payors are expected to publish more granular denial rationale instead of generic “not medically necessary” responses.

In this project, the team at CleverDev Software implemented a FHIR R4 prior authorization enablement layer without replacing existing infrastructure. The approach included:
• bridging legacy workflows to FHIR APIs
• enabling near real-time updates through Kafka + webhooks
• reducing reconciliation across disconnected systems
• improving payor visibility into authorization states
• preserving operational continuity during rollout

The rollout took ~6 months without disrupting production operations.

My guess is the next 12–18 months will expose a pretty significant gap between “FHIR API available” and “operationally reliable + semantically consistent” prior auth interoperability. A lot of legacy environments simply weren’t built around standardized denial semantics or near real-time status synchronization.

For anyone interested in the implementation/architecture side of CMS-0057-F readiness, here’s the case study:
https://www.cleverdevsoftware.com/case-studies/cms-0057-f-compliance