Why WISeR providers should keep their own record while Congress argues

The Senate’s July vote left Medicare’s AI-assisted prior authorization model running in six states, its future still contested. Providers bound by it now need their own record of decisions, documentation and appeals, because that record serves both daily operations and the policy fight.

Looking Back revisits one week at a time, from January 2020 to today, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

The week

The Wasteful and Inappropriate Service Reduction model, known as WISeR, started in January 2026 and is scheduled to run through 2031 in Arizona, New Jersey, Ohio, Oklahoma, Texas and Washington. For selected services, providers in traditional Medicare must request prior authorization or face prepayment review. Technology companies review requests with tools that include artificial intelligence. They are paid a share of the spending their reviews avert, and a licensed clinician must review any denial. The model’s footing was contested all summer. On May 12, GAO concluded that the CMS notice implementing it is a rule under the Congressional Review Act. On June 9, the House Appropriations Committee adopted language barring fiscal 2027 funds for it. On July 16, the Senate voted 46 to 50, falling short of taking up a resolution to overturn it. Providers entered August still bound by the model.

For a hospital or physician group in the six states, the politics left an awkward position. The model might be defunded in a later spending bill, or it might run to 2031. Either way, it decides claims today. A revenue cycle cannot wait for Washington to settle the question. The more useful response is for each organization to build its own record of how WISeR works in practice. That record does two jobs at once. It lets the organization manage the model day to day, and it gives the organization evidence to bring to its medical society, its hospital association, CMS or Congress. The record has three parts, which follow the life of a request: the decision, the documentation behind it, and what happens after a denial.

The decision record

The first part is a log of every WISeR request. It should capture the service, the ordering clinician, the site, the dates submitted and decided, the outcome, the stated reason for any denial, and whether the organization chose prior authorization or prepayment review. Most of these data exist already, spread across the authorization work queue, the scheduling system and the billing system. They are rarely joined, and for traditional Medicare they may not be tracked at all, because these services never needed authorization before.

A joined log turns anecdotes into measures. It shows turnaround by service and by month, so a slipping reviewer is visible early. Turnaround is not a theoretical concern. By early July, CMS had directed Virtix Health, the reviewer for Washington, to submit a corrective action plan after it missed required response times. A provider with its own timestamps could see that delay in its schedule before CMS acted, and could document how many procedures it pushed back.

The log also shows whether outcomes differ by clinician or site, which separates documentation habits from reviewer behavior. It can track the gap between first-pass and final decisions. Early Texas figures, as reported by the Washington Post, showed roughly 62 percent of requests approved on first submission and about 84 percent after physician review. A provider that can set its own numbers beside published ones is in a stronger position than one relying on press reports.

The documentation record

The second part is a copy of exactly what was submitted with each request. Technology-assisted review reads the record against coverage criteria. When a request is denied for insufficient documentation, the question is whether the clinical facts were missing or only hard to find. Those problems need different fixes.

Tagging each denial by the criterion cited lets clinical documentation teams find patterns. A spine practice may find that conservative therapy history sits in referral letters that are never attached. A pain clinic may find that imaging results are summarized in notes but not included. Each pattern can be fixed with a template change, an order-entry prompt or a checklist at scheduling. That is cheaper than appealing the same denial repeatedly. Where services are ordered in the EHR, a pre-submission check for required elements catches the problem at source.

Scope changes matter here too. In April, CMS delayed two of the listed services, deep brain stimulation and a lumbar decompression procedure, to allow more operational readiness. A documentation library keyed to each service’s current status stops staff from sending requests that are no longer required, or skipping ones that are.

This record also feeds the wider argument about AI in utilization review. If reviews track the published criteria, a provider’s files will show it. If they do not, specific examples tied to cited criteria will carry more weight with CMS and lawmakers than general complaints.

The record after a denial

The third part covers what happens next. A denied request can be resubmitted with more documentation. A provider can also deliver the service and bill it, accepting prepayment review and the normal Medicare claims and appeals process. Each path has a cost. Resubmission takes staff time and delays care. Proceeding without an affirmed request risks nonpayment and adds work for patient financial services.

Tracking every denial to final payment shows which path works for which service. The log should record resubmissions and their results, claims sent through prepayment review, appeal levels reached, final payment and the staff hours spent. Over a few months, the overturn rate becomes one of the most telling measures available. A high rate suggests first-pass reviews are missing something. It is also the figure most likely to matter in an evaluation or an oversight hearing.

Beneficiary effects belong in this record as well. Patients who cancel, travel to another state or switch to a Medicare Advantage plan leave a trace in scheduling and registration data. Counting them is harder than counting dollars, and it is the concern critics of the model raise most often.

The three parts work best under one owner, usually a utilization management or revenue cycle lead. That person reports monthly to clinical leadership and to the compliance office, and keeps a short version ready for the state hospital association. Organizations should confirm current resubmission and appeal rules with their Medicare Administrative Contractor and with counsel, because program details have changed during the year.

With hindsight

As of October 2026, WISeR is still running. The House committee’s funding bar has not become law. Fiscal 2027 began under a continuing resolution that runs into December and generally carries forward 2026 terms, so the fight moves to the full-year bill. CMS has adjusted the model during its first year, delaying two services and pressing a reviewer on turnaround, which shows that the details remain open even if the model survives. No formal CMS evaluation has been published, and conclusions about accuracy or effects on care would be premature. Public numbers so far come from press reports and individual reviewers rather than from CMS. That makes provider-side measurement more valuable, not less. Organizations that log decisions, documentation and outcomes consistently can describe their own experience with evidence, whatever Congress decides.

  • WISeR
  • prior authorization
  • Medicare
  • Congressional Review Act
  • revenue cycle