Skip to main content

Prior Authorization Automation: From Request to Approval

Duration: 60 min · Level: Intermediate · Module: 2. Eligibility & Prior Auth Agents · Focus: prior-authorization, CMS-rule, FHIR-PA, CoverMyMeds, automation

Learning objectives

By the end of this lesson you will be able to explain and apply:

  • CMS Interoperability and Prior Authorization Final Rule (January 2024)
  • PA request components
  • X-FHIR-PA API
  • Gold carding
  • PA agent design

Why this matters​

Prior authorization is where healthcare administrative waste is most visible and most painful.

Overview​

Prior authorization is where healthcare administrative waste is most visible and most painful. CoverMyMeds (now RxBenefits), Surescripts, and payer portals each handle different authorization types. CMS finalized rules in 2024 requiring payers to support FHIR-based PA APIs — a landmark shift that makes prior auth automation dramatically more feasible.

Key concepts​

Key idea

CMS Interoperability and Prior Authorization Final Rule (January 2024): requires Medicare Advantage, Medicaid, and CHIP plans to implement FHIR-based PA APIs by January 2027; must respond within 72 hours (standard) and 24 hours (urgent)

  • PA request components: requesting provider NPI + contact, patient demographics + insurance ID, diagnosis codes (ICD-10), procedure/drug codes (CPT/HCPCS/NDC), clinical documentation (clinical notes, labs, prior treatments tried)
  • X-FHIR-PA API: the FHIR-based PA standard emerging from CMS rules; uses FHIR R4 Claim resources for submission and ClaimResponse for decisions; integrates directly with EHR via SMART on FHIR
  • Gold carding: some payers grant "gold card" status to physicians with high PA approval rates — exempting them from PA requirements; track approval rates by payer to identify gold card opportunities
  • PA agent design: (1) detect services requiring PA from the order (CPT + diagnosis + payer lookup), (2) gather clinical documentation from EHR, (3) submit via API or portal, (4) poll for determination, (5) alert on approval/denial/additional info request, (6) auto-escalate to human if peer-to-peer needed
  • CoverMyMeds/RxBenefits API: largest pharmacy PA clearinghouse; REST API for drug PAs; covers 95% of commercially insured lives; significant pharmacy PA automation through this single integration

Check your understanding​

Try to recall each answer before expanding it.

Q1. What do you know about CMS Interoperability and Prior Authorization Final Rule (January 2024)?

requires Medicare Advantage, Medicaid, and CHIP plans to implement FHIR-based PA APIs by January 2027; must respond within 72 hours (standard) and 24 hours (urgent)

Q2. What do you know about PA request components?

requesting provider NPI + contact, patient demographics + insurance ID, diagnosis codes (ICD-10), procedure/drug codes (CPT/HCPCS/NDC), clinical documentation (clinical notes, labs, prior treatments tried)

Q3. What do you know about X-FHIR-PA API?

the FHIR-based PA standard emerging from CMS rules; uses FHIR R4 Claim resources for submission and ClaimResponse for decisions; integrates directly with EHR via SMART on FHIR

Q4. What do you know about Gold carding?

some payers grant "gold card" status to physicians with high PA approval rates — exempting them from PA requirements; track approval rates by payer to identify gold card opportunities

Q5. What do you know about PA agent design?

(1) detect services requiring PA from the order (CPT + diagnosis + payer lookup), (2) gather clinical documentation from EHR, (3) submit via API or portal, (4) poll for determination, (5) alert on approval/denial/additional info request, (6) auto-escalate to human if peer-to-peer needed

← Previous: H2.1 Real-Time Eligibility: The 270/271 EDI Transaction · Next: H2.3 Portal Scraping & Browser Automation as Fallback →

Part of Module 2: Eligibility & Prior Auth Agents.