The problem

What the customer was up against.

  • Prior authorization took an average of 7 days, with 11% of requests denied on technicalities that could have been corrected upfront.
  • Physicians spent 14 hours per week on PA paperwork instead of patient care — a leading cause of clinician burnout.
  • Each payer (Anthem, UHC, Aetna, BCBS) used different forms, criteria, and submission portals, requiring a 9-person dedicated PA team.
  • Denials created downstream revenue-cycle losses of $46M/year and care delays that hurt patient outcomes.
The solution

What xyner built.

  • Deployed HIPAA-aligned xyner agents inside the health system's Epic environment using SMART-on-FHIR.
  • Agents read the clinical chart, identify the required CPT codes and medical-necessity criteria, then complete and submit each payer's exact form with all needed documentation.
  • Integrated to Epic, all 8 major payer portals, and CMS coverage databases. Real-time policy lookup ensures requests match each payer's published medical-necessity rules.
  • Built-in human approval gate for any oncology or transplant request; routine PAs auto-submit. All decisions explainable with cited clinical-policy bulletins.
The outcomes

Measured impact.

12 min
median time-to-decision
was 7 days
96%
first-pass approval rate
was 89%
14 hrs/week
returned to physicians
per provider
$46M
annual revenue recovery
downstream cycle
HIPAA + SOC 2
audited & live
across 14 hospitals
Executive summary

At a glance.

Situation

A top-20 US health system was running a 320-FTE prior-authorization operation with average turnaround of 6 business days, a 28% initial-denial rate, and rising clinical-team frustration as physicians spent unbillable time on PA workflows.

Intervention

Deployed a Prior-Authorization Agent connected to the EHR (Epic), payer portals, formulary database and the clinical documentation system, with HIPAA-grade audit and PHI redaction enforced on every outbound payer call.

Outcome

PA turnaround cut from 6 days to under 2; initial-denial rate down from 28% to 17%; approximately 40% of physician PA-related effort eliminated; appeals workload reduced by 35%.

Industry

Healthcare

A top-20 US integrated health system

Scope

United States (multi-state)

Prior authorization across all commercial payers

Duration

10 weeks pilot, 7 months full rollout

From contract signature to full rollout.

Architecture

What the deployment actually looks like.

The deployment runs in the health system's HIPAA-aligned private cloud with a single-tenant data plane; PHI never leaves the system's perimeter, and all model calls go to HIPAA-eligible model endpoints in the same region.

Prior-Authorization Agent

Reads the clinical note, identifies the proposed service/medication, looks up the relevant payer's PA requirements, assembles clinical evidence from the EHR, and drafts the submission.

Payer connector layer

First-class connectors to the major US commercial payers' PA APIs and portals, with fallback to fax-based PA where APIs aren't available.

Formulary & medical-policy RAG

Policy-aware RAG indexed on each payer's medical policy, formulary and PA criteria — retrieval bounded by payer and date.

Clinical reviewer hand-off

Cases requiring clinical judgment route to the system's clinical-review nurses with the assembled evidence and proposed submission for approval.

Appeals agent

On initial denial, an appeals agent assembles additional evidence, drafts the appeal letter citing the relevant policy clause, and routes for clinical sign-off.

HIPAA-grade audit

Every PHI touchpoint is captured; every payer interaction is logged; PHI is redacted on any model call that doesn't require it.

Implementation timeline

How the rollout sequenced.

A 10-week pilot focused on three high-volume service lines (cardiology, oncology, advanced imaging) before scaling to the full PA portfolio.

Weeks 1-3

HIPAA foundations

Deploy in HIPAA private cloud; configure HIPAA-eligible model endpoints; complete BAA paperwork with relevant providers; deploy single-tenant data plane.

Weeks 4-5

Integration

Integrate Epic, major payer portals, the formulary database, and the appeals workflow system; configure RBAC inheritance from the system's identity provider.

Weeks 6-7

Agent & RAG configuration

Configure the PA agent against the three pilot service lines; load payer medical policies and PA criteria into the RAG layer; complete first round of clinical-safety testing.

Weeks 8-10

Shadow mode + go-live

Agents run alongside the PA team for two weeks; go live with clinical approval on all submissions for the three pilot service lines.

Months 3-5

Service-line expansion

Add service lines incrementally; expand to more payers; introduce the appeals agent.

Months 6-7

Full portfolio + autonomy calibration

Full PA portfolio coverage; autonomy thresholds calibrated for low-complexity routine PAs; humans focus on high-complexity and appeals.

Governance & controls

How the deployment is governed.

Healthcare AI is under intense scrutiny — HIPAA, HITECH, the HHS AI strategy, payer-readiness requirements. Every component was designed for the audit conversation.

HIPAA-grade handling

PHI tagged at write-time; access-checked at read-time; redacted on any outbound call that doesn't require it; minimum-necessary enforced at retrieval.

Clinical safety

Every clinical recommendation requires a citation chain to the clinical guideline, formulary or evidence base. No ungrounded clinical reasoning ever ships.

Clinician oversight

All PA submissions and appeals are reviewed by a licensed clinical reviewer before submission for the first 90 days; thresholds recalibrate based on demonstrated quality.

Audit-grade trail

Every PHI touchpoint and every payer interaction is captured with timestamp, requester, payload hash and outcome. Audit packs export on demand for HIPAA reviews.

Payer-relationship discipline

Payer interactions are rate-limited and respectful of payer-side terms; flagged or rejected submissions trigger root-cause analysis, not retry-loops.

What other enterprises can learn

Three transferable lessons.

Three lessons for other health systems considering agentic AI in revenue-cycle and clinical-administrative workflows.

1

Pick a workflow where the unit economics are obvious

Prior auth was a clear case: high volume, well-defined success criteria (approval/denial), measurable cycle time. Choose workflows where 'better' is obviously definable.

2

Bring clinical leadership in as design partners

Clinical and operational leadership co-designed the agent behaviour and the hand-off thresholds. The deployment ran into zero clinical-safety pushback because the clinicians had built it.

3

Treat PHI redaction as platform-level, not app-level

Every model call goes through a redaction layer at the platform — not in app code. This is the single biggest derisking decision for a healthcare AI deployment.

We stopped having the AI-in-healthcare conversation. We started having the prior-authorization conversation, and the AI just happens to be how we solve it.
Chief Medical Information Officer, top-20 US health system

Reference call available through your xyner account team; the deployment has been presented at HIMSS and is featured in upcoming AMA workflow-modernization materials.

Talk to a partner

Could the same outcome work in your environment?

Tell us your sector. A senior xyner partner will walk you through a tailored plan.