Table of Contents

  1. What Flexbone does
  2. How the agents work
  3. The CMS 2026 electronic PA rule
  4. Implementation: a 4-week path
  5. What to ask any PA vendor
24/7PA submission across portals, ePA, and phone lines
4 weekforward-deployed implementation, not a 9-month rollout
Shadow first30-day parallel run on your actual PA mix before agents submit in production

What Flexbone does

Flexbone runs prior authorization as a single workflow. Our AI agents pull the order from your EHR, check payer rules, assemble clinical documentation, submit the request, track status, handle appeals, and write the determination back to the chart. No staff member sitting at a keyboard for any of it.

We handle three channels in one system. Browser agents operate payer portals (Availity, CoverMyMeds, Surescripts, and direct payer portals). Voice agents call payers for peer-to-peer or when the portal fails. Electronic PA rails (X12 278, HL7 Da Vinci PAS) are used wherever payers support them. Most vendors do one channel well. We do all three.

How the agents work

A Flexbone deployment runs as four steps. Each one is supervised in week one, then operates on exception review.

Step 1. Order capture

The system pulls the order, CPT/ICD codes, scheduled date, and ordering provider from your EHR via FHIR, a direct API, or a browser agent when no API exists. For ASCs on HST Pathways, the agent reads directly from HST and Casetabs.

Step 2. Eligibility and documentation

The AI runs real-time insurance eligibility verification to confirm the PA is actually required for this payer and plan. Then it pulls clinical notes, imaging, and prior treatment history from the chart and matches them against the payer's medical policy. Gaps get surfaced before submission, not discovered as denials.

Step 3. Submission across any channel

If the payer supports the HL7 Da Vinci PAS FHIR endpoint or X12 278, we submit electronically. If not, a browser agent logs in and submits through the portal. If both fail, an AI voice agent calls the payer PA line. One workflow, three channels.

Step 4. Status tracking, appeals, and writeback

The system polls status on a cadence set by procedure urgency. Denials flow into Flexbone's AI denials management workflow for auto-appeal or human routing. Every outcome writes back to the EHR with a full audit trail.

The CMS 2026 electronic PA rule

CMS finalized the Interoperability and Prior Authorization Final Rule (CMS-0057-F) in January 2024. It applies to Medicare Advantage, Medicaid, CHIP, and QHP issuers on the federal exchange. Starting in 2026, these payers must respond to urgent PA requests within 72 hours and standard requests within seven calendar days. By January 2027 they must expose a FHIR-based Prior Authorization API.

Commercial payers aren't covered by the rule, so portal and phone workflows won't disappear. Stacks that only speak FHIR will strand a chunk of your volume. Stacks that only operate portals will miss the efficiency gains the rule unlocks. A system that handles all three channels is the only safe bet.

Implementation: a 4-week path

Enterprise healthcare software usually ships on a 9-month timeline. PA automation doesn't work that way. Every week the workflow stays manual is a week of ROI on the floor. Flexbone deploys in four weeks, forward-deployed with your team.

  • Week 1. Discovery and workflow mapping. Our engineers sit with your PA coordinators and document the 10-20 payer and procedure combinations that cover 80% of volume.
  • Week 2. Build and integration. EHR connection (FHIR API where available, browser agent where not), payer portal training on your highest-volume payers, and clinical-policy ingestion.
  • Week 3. Supervised go-live. The system starts submitting real PAs for a single payer and procedure cohort. A Flexbone engineer pair-reviews every submission for three days, then shifts to exception-only review.
  • Week 4. Expansion and optimization. Coverage expands across your full payer mix, with tuning for the edge cases your team handles every day.

The success factor isn't the model. It's workflow fidelity. The AI has to understand your specific payer mix, documentation patterns, and edge cases. That's why we run forward-deployed instead of handing you a config screen.

What to ask any PA vendor

If you're evaluating vendors, these are the questions that separate real automation from demo-ware:

  • What percentage of PAs go out with zero human touch? Some vendors count a human-reviewed draft as "automated." Ask for the number on real customer volume.
  • Can you submit PAs by phone? Phone-only PA is still a meaningful share of volume for most practices. Vendors without voice leave your staff running the hardest part of the workflow.
  • What happens when a payer portal changes? RPA and scripted automation break on UI updates. Ask for portal-resilience proof, not promises.
  • Can I export the full audit trail? HIPAA and payer audits require a complete log of every AI action. If you can't export it, the automation is a liability.
  • How does the system back off on errors? Automation that floods a payer with malformed submissions will get your TIN flagged. Good systems throttle, escalate, and communicate.
  • What's the time to first live PA? Anything over a few months means the ROI clock doesn't start this quarter.

Prior authorization guides by specialty, facility, EHR, and payer

The PA workflow is not one problem. It is dozens, and each one has its own clinical criteria, payer rules, and EHR quirks. The guides below each go deep on a cluster of related PA workflows so you can jump to the one that matches your setting, book of business, or system of record.

By specialty

By facility type

By EHR and PA portal

  • ASC EHRs — HST Pathways, Casetabs, SIS, AmkAI, Provation, Advantx, SourceMedical, Picis, Simplify ASC, Nextech ASC.
  • Outpatient & specialty EHRs — athenahealth, eCW, NextGen, Allscripts/Veradigm, ModMed, Greenway, DrChrono, AdvancedMD, Tebra, and more.
  • Post-acute EHRs — PointClickCare, MatrixCare, Netsmart myUnity, WellSky, Homecare Homebase, and more.
  • Therapy & behavioral EHRs — WebPT, Raintree, Prompt, Valant, TherapyNotes, SimplePractice, Qualifacts.
  • PA portals & clearinghouses — CoverMyMeds, Availity, Waystar, Change/Optum, eviCore, NIA, Carelon.

By payer

  • Commercial payers — UHC, Aetna, Cigna, Humana, Anthem/Elevance, Kaiser, Molina, Oscar.
  • BCBS plans — HCSC, Highmark, BCBSM, Florida Blue, Regence, Premera, Independence, Wellmark, Anthem BCBS states.
  • Medicare, Medicaid & government — Traditional Medicare, MA, Managed Medicaid, CHIP, TRICARE, VA CCN, FEHB, CMS-0057-F.

By workflow step