Humana takes electronic prior auth to 180,000 athenahealth clinicians, two months before the CMS API deadline

More than seven in ten. That's the share of Humana prior auth requests that athenahealth practices completed in September without staff having to add anything, chase anyone or pick up a phone. On 3 November the two companies said they are taking that set-up nationwide, across athenahealth's network of more than 180,000 physicians and clinicians.

What's new

The expansion runs on three FHIR standards from the Da Vinci Project: Coverage Requirements Discovery (CRD), Documentation Templates and Rules (DTR) and Prior Authorization Support (PAS). Between them they tell a clinician whether an authorization is needed, what documentation the plan wants, and then carry the request and the answer, all inside the EHR.

Get Digital Health every TuesdayThree-minute read. Free. One-click unsubscribe.

The connection runs through athenaPayer, athenahealth's payer link. Humana plugs into it once and reaches every practice on athenaOne, rather than building a separate interface for each practice or health system, which is how most payer-provider integrations still work.

"Prior authorization shouldn't require care teams to navigate a different process for every health plan." Paul Brient, Chief Product and Operations Officer, athenahealth

The numbers

In September, more than 6,000 providers sent nearly 35,000 electronic prior auth transactions to Humana. More than 70% were completed without extra input from practice staff. Read the footnote, though: that figure comes from athenahealth's internal data and counts determinations that no authorization was needed, as well as electronic approvals and denials. RevCycleAI points out that the companies didn't share decision-time or denial-rate comparisons, so this is a measure of touchless processing, not of faster or more favourable decisions.

Why the timing matters

The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) requires impacted payers, including Medicare Advantage plans, Medicaid and CHIP programmes and qualified health plans on the federal exchanges, to run a Prior Authorization API from 1 January 2027, according to RevCycleAI's summary. CRD, DTR and PAS are the standards that API work leans on.

Both companies were already named early adopters in CMS's Electronic Prior Authorization Acceleration Initiative in May 2026, and the work builds on an earlier Humana, athenahealth and Availity project. HIT Consultant's write-up frames it as replacing faxes, repeat phone calls and separate payer portals.

The bigger picture

Most of the prior auth news in recent issues has been about AI deciding cases. This is the less glamorous layer underneath: standard pipes between payer and EHR. Our read is that it's good news for the AI vendors too. Once requests arrive as structured FHIR data rather than faxed PDFs, there's far more for automation on both sides to work with, and the 2027 deadline gives every other large plan a reason to move.

What it means for hiring

FHIR and Da Vinci implementation experience is about to be in demand across payers, EHR vendors and the prior auth start-ups that plug into them. People who have shipped CRD, DTR or PAS in production are a small pool.
Network-style payer connections change the sale. We'd expect EHR and interoperability vendors to want payer partnership leads who can sign one health plan and light up thousands of practices.
With a hard regulatory date in January, payer-side programme managers and compliance-minded product leads look like the near-term hires, ahead of pure sales growth.

Share Ask Issy about this →