Payers face Jan. 1 prior authorization API deadline as automation money flows

CMS-regulated payers, including Medicare Advantage, Medicaid and marketplace plans, face a Jan. 1 deadline to implement three prior authorization APIs under a federal interoperability rule, Healthcare Dive reports. The APIs let providers check whether a service needs prior authorization, pull documentation requirements from the patient's EHR, and submit requests that payers answer electronically. MedCity News notes the rule, CMS-0057-F, also sets decision timeframes of 72 hours for expedited requests and seven days for standard ones.

Epic, which holds roughly 42% of the acute care EHR market according to Healthcare Dive, shipped API-based prior authorization in its February release. Ryan Bohochik, Epic's vice president of value-based care, describes payer readiness as a spectrum: large national payers are ready or testing, UnitedHealthcare is live with health systems, and Network Health in Wisconsin supports all three APIs, while some smaller regional plans are still digitizing policies that once lived in binders. He reports early adopters seeing fewer canceled appointments. His field lesson matters for workflow design: coverage checks built for the point of care often need rechecking at scheduling, because data the payer needs is not yet known when the order is placed.

Capital is following the mandate. ClarityCare raised a $16.5 million Series A led by Headline, bringing total funding to $19.8 million, per MedCity News. The company says its AI agent, Electra, approves and escalates but never denies, keeps a clinician in the loop, and cut waits for one of its seven customers from 12 days to two. That is a single company-reported result, not independent data. The AMA, cited by MedCity, reports staff spend up to two business days per week, per clinic, on prior authorization.

What the evidence does not show is overall payer readiness. Bohochik's account is a vendor's view, and no independent tally is given. For revenue cycle leaders, readiness varies by payer, so denial and cancellation risk will too. For CIOs, each live payer connection is a new data exchange that warrants the same security and access review as any external interface.

The move: ask your top five payers this week for their API readiness status and test dates, confirm your EHR release supports all three APIs, and route coverage checks to scheduling as well as ordering. The return is fewer canceled visits and fewer hours staff spend chasing approvals.

You are a revenue cycle and interoperability advisor to the executive team of [your organization], a [type of organization].

Context: Healthcare Dive reports that CMS-regulated payers, including Medicare Advantage, Medicaid and marketplace plans, face a Jan. 1 deadline to implement three prior authorization APIs under a federal interoperability rule. The APIs let providers check whether a service needs prior authorization, pull documentation requirements from the EHR, and submit requests that payers answer electronically. MedCity News notes the rule, CMS-0057-F, sets decision timeframes of 72 hours for expedited requests and seven days for standard ones. Epic's Ryan Bohochik, speaking to Healthcare Dive, describes payer readiness as a spectrum and says coverage checks built for the point of care often need rechecking at scheduling. His account is a vendor's view. No independent data on payer readiness is given. MedCity News cites the AMA: staff spend up to two business days per week, per clinic, on prior authorization.

Task: Help me ask our top five payers this week for their prior authorization API readiness status and test dates, and confirm whether our EHR release supports all three APIs.

Output: First, a question list to send to each payer, covering readiness for each of the three APIs, test dates, decision timeframes, and the security and access review an external interface requires. Second, a one-page memo for the executive team with these sections: Why this matters by Jan. 1, Payer readiness tracker, EHR readiness, Scheduling workflow change, Open questions.

My details: [your top five payers by volume], [your EHR and current release], [your weekly staff hours on prior authorization], [your monthly visits canceled for pending authorization], [the owner for payer outreach].

Guardrails: Use only the facts above and the details I fill in. Cite Healthcare Dive and MedCity News by name. Flag anything uncertain or that needs verifying, including every vendor claim. Do not request or include patient data. Nothing here is medical advice. Label the result a draft for the team to check.