AI Governance

WISeR AI Prior Authorization: What Go-Live Readiness Requires

CMS WISeR records and FOIA reporting highlight a broader AI governance issue: whether the full prior-authorization workflow is operationally ready before it affects consequential healthcare decisions.

💡

TL;DR:
WISeR shows why AI-assisted prior authorization requires more than model validation. Healthcare leaders should assess workflow readiness, connectivity, human review, turnaround times, and documented go-live decisions.

What you need to know

The change: Wasteful and Inappropriate Service Reduction (WISeR) began January 1, 2026, in six states and uses enhanced technology with human clinical review for selected Original Medicare prior-authorization and pre-payment reviews. Participants and Medicare Administrative Contractors (MACs) began accepting prior-authorization requests January 5 for services rendered on or after January 15. (Centers for Medicare & Medicaid Services)
Who is affected: Healthcare compliance and risk leaders, utilization-management teams, providers, clinical operations leaders, health-technology vendors and executives responsible for AI-assisted consequential workflows.
Why it matters: WISeR depends on more than AI. Requests may move through participant portals or Medicare Administrative Contractors, non-affirmations require clinician review, and CMS monitors portal readiness and turnaround times. (Centers for Medicare & Medicaid Services)
What to do first: Review whether your production-readiness process covers end-to-end workflow dependencies, unresolved defects, human-review capacity and escalation—not just model validation.
Key date or trigger: CMS began WISeR on January 1, 2026. In April, CMS delayed two services to allow additional time for operational readiness. (Federal Register Public Inspection)

This analysis continues in the PolicyEdge AI Intelligence Terminal, where members receive decision-grade intelligence on AI, regulation, and policy risk.

Founding Member access

Abstract signal pathways converge through a verification layer, representing Medicare AI policy provenance and governance.

Medicare AI Policy: What CMS’s Health-Tech Slack Means for Compliance

KFF’s CMS Slack investigation highlights a practical compliance issue: distinguish published Medicare AI requirements from developing workgroup specifications, official comments, and vendor interpretations.

IEEPA tariff refunds shown as branching data paths moving through regulatory gates toward different financial outcomes.

IEEPA Tariff Refunds: What Class Certification Means for Companies

A federal court certified an IEEPA tariff refund class, but certification is not a final payment order. Public filings show that accounting treatment and customer refund liabilities can affect what companies ultimately retain.

AI incident reporting visualized as blue data flows moving through controlled review points and connected external systems.

White House AI Incident Reporting: New Disclosure Expectations and Unanswered Questions

The White House has declared immediate AI incident reporting mandatory, but key implementation details remain unclear. Examine the September 29 AI accord, Anthropic's unintended model actions, and what compliance and security leaders should review.

FDA FY2027 AI device guidance visualized as converging data flows, checkpoints, and traceable lifecycle pathways.

FDA FY2027 AI Device Guidance Puts Lifecycle Evidence in Focus

FDA’s FY2027 priorities put AI device lifecycle management, change control, robotic surgery, and real-world performance in focus for manufacturers and healthcare organizations.