From the Health & Human Services edition of November 5, 2026
CMS WISeR Medicare AI prior-authorization pilot: FOIA records show four of six vendors flagged for delays, questionable denials and portal gaps
Centers for Medicare & Medicaid Services (WISeR model), reported by Nextgov/FCW · Public health coverage determination / prior authorization (traditional Medicare) · New Jersey, Ohio, Oklahoma, Texas, Arizona, and Washington, United States
- Publisher
- Nextgov/FCW
- Original publication
- 2026-11-02
- Source retrieved
- 2026-11-06
- Event date
- 2026-11-02
What happened
FOIA documents released by EFF and reported by Nextgov show CMS sent RFIs or corrective-action requests to four of six WISeR AI prior-authorization vendors early in 2026 over slow determinations, questionable or blank denials, missing electronic portals and weak provider communication. Named vendors include Genzeon (New Jersey), Virtix Health (Washington), Zyter (Arizona) and Innovaccer (Ohio). CMS later said no CAPs are active and vendors are compliant, with a six-month performance report forthcoming. CMS deputy administrator Kimberly Brandt publicly acknowledged many things about WISeR are not working; House Appropriations advanced an amendment to suspend WISeR funding.
Why it matters
A large federal AI-assisted coverage-review experiment in six states with documented early vendor noncompliance and congressional scrutiny—directly instructive for state Medicaid and public-hospital prior-auth AI programs considering similar vendors and human-in-the-loop claims.
Evidence and measured results
Nextgov synthesis of EFF FOIA RFIs/CAPs, vendor response letters, CMS spokesperson comments and public remarks by CMS leadership. Early-period performance; later improvements claimed by vendors/CMS without independent audit in this article.
Limitations and uncertainty
Federal Medicare WISeR, not Medicaid; documents describe early-2026 problems and CMS asserts current compliance. Choose Nextgov over MedCity/EFF as the Nov. 2 independent-reporting synthesis.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-05; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Coverage programs want AI to cut wasteful spend without delaying care or generating indefensible denials.
- Stakeholders
- Medicaid/Medicare coverage leads
- Hospital association and specialty providers
- Legislative oversight staff
- Discovery questions
- What go-live readiness gates exist for the provider portal?
- How are denial-accuracy samples reported publicly?
- Can clinicians override without quota pressure?
- Value hypothesis
- Bounded: AI-assisted review may speed routine affirms if portals and SLAs work; early WISeR evidence shows the opposite risk when rushed.
- Potential engagement
- Prior-auth AI readiness and denial-quality assessment for a state coverage program.
- Unsupported claims
- That WISeR currently meets all SLAs
- That human review fully prevents improper denials
- Net savings after access harms
Pre-sales engineering
Role takeaway
- Fit
- AI-assisted prior authorization with mandatory licensed-clinician review for non-affirmations.
- Architecture and integration
- Provider portal, case tracking IDs, AI recommendation, clinician review, determination letters and claims integration.
- Prerequisites
- Portal ready before launch
- Turnaround SLO monitoring
- Denial rationale templates tied to coverage criteria
- Constraints
- Compressed implementation timelines
- Vendor incentive to maximize prevented spend
- Opaque model features
- Security
- Secure provider authentication, PHI minimization in vendor environments, and immutable determination audit logs.
- Proof of value
- Share of determinations within SLA
- Clinician override rate
- Provider resubmission/affirmation rates after education
Delivery
Role takeaway
- Work
- Phased service list, portal UAT, clinician reviewer staffing, provider education, public performance reporting.
- Dependencies
- CMS/state model rules
- Vendor portal delivery
- Clinical reviewer capacity
- Ownership
- Coverage operations with compliance and IT.
- Skills and adoption
- Train clinicians to challenge AI recommendations and document independent rationales.
- Governance checkpoints
- Pre-launch readiness review
- Weekly CAP-style exception review
- Public six-month performance report
- Acceptance criteria
- Proposed: zero go-live without functioning electronic submission
- Proposed: determination SLA met for ≥95% of cases
- Risks
- Care delays and patient harm
- Congressional or CMS suspension
- Provider abrasion and resubmission churn
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Vendor AI plus licensed clinician review for selected Medicare services, with provider portals and determination-letter workflows; Zyter noted as using Palantir infrastructure in related EFF material cited by secondary coverage. Technical details of models are not in the Nextgov piece.
Governance
Who approves, reviews and stays accountable for outcomes?
Rushed six-month launch, active CAP/RFI oversight, congressional funding threat and limited public transparency on whether human reviewers meaningfully override AI recommendations.
Security and privacy
What data, permissions and controls need testing?
Coverage requests include clinical detail; article focuses on operational failures more than cybersecurity, but portal readiness failures are themselves access-control risks.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Provider burden and patient delays (e.g., reported bedside distress waiting on kyphoplasty auth) show workforce and access harms when AI prior-auth underperforms.
Procurement
What should contracts, pricing and exit terms secure?
Payment structure sharing savings from prevented 'wasteful' care creates denial-incentive concerns; readiness gates and enforceable SLAs should precede go-live.
Operating model
Which teams own the service once it runs?
Human-in-the-loop non-affirmation review is required by CMS FAQ, yet early letters suggest turnaround and denial-quality failures—operating model depends on reviewer capacity and authority, not slogans.
Publication history
- 2026-11-05Health & Human Services · Issue 084 resources
Stable resource ID: cms-wiser-medicare-ai-prior-auth-vendor-flags-eff-foia-20261102