CMS WISeR Model 2026: What You Must Know About Prior Authorization Changes

Medicare is not standing still. In January 2026, CMS launched one of the most operationally disruptive prior authorization experiments in recent memory. It is called the WISeR Model (Wasteful and Inappropriate Service Reduction). Six states. Six years. One clear objective: eliminate unnecessary Medicare spending on select high-cost services, using AI-assisted prior authorization reviews.

If your practice operates in Arizona, New Jersey, Ohio, Oklahoma, Texas, or Washington, and treats Medicare fee-for-service patients, this model is not optional reading. It is a live operational requirement that affects how you schedule services, submit authorization requests, and file claims starting now.

And if you think prior authorization complexity was already a burden, wait until you understand what FHIR-based APIs, Unique Tracking Numbers, and pre-payment claim holds actually mean for your revenue cycle. For a broader look at how CMS redesigns payment at scale, start with our Medicare Advantage and Part D payment update for 2026.

What Is the CMS WISeR Model and Why Does It Exist

CMS introduced WISeR as a mandatory six-year Medicare pilot (2026 through 2031) built specifically to reduce what federal analysts describe as low-value care. This is not a voluntary quality improvement program. Every eligible provider in the six pilot states must comply.

The model targets services that research has flagged as frequently overutilized without proportional clinical benefit. Current examples include:

•       Skin substitute products used in wound care

•       Peripheral nerve stimulators

•       Certain spinal intervention procedures

CMS partners with one technology vendor per state. These vendors, referred to as WISeR participants, handle the prior authorization review process using data analytics and clinical algorithms. Their job is to assess each request and determine whether CMS should affirm or deny coverage before the service is performed.

For practices already navigating MIPS eligibility, deadlines, and reporting, adding a mandatory prior authorization layer with new technology requirements is a significant operational lift.

Key Fact: WISeR launched on January 1, 2026. PA submissions opened January 5, 2026. Six states are live: AZ, NJ, OH, OK, TX, and WA.

The 2024 to 2026 Policy Changes That Paved the Way for WISeR

WISeR does not exist in a policy vacuum. It sits inside a broader CMS interoperability push that has been building momentum since 2021. The most consequential regulatory development is the CMS-0057-F final rule, published in February 2024.

That rule requires all payers operating under Medicare Advantage, Medicaid, and CHIP to implement FHIR-based prior authorization APIs by January 2027. The implication is significant: the infrastructure WISeR requires is the same infrastructure that will eventually govern prior authorization across nearly every major payer category in the US healthcare system.

What this means in practical terms:

•       Payers must support electronic PA requests through standardized FHIR APIs

•       The old fax-it-and-wait workflow is being systematically replaced

•       Practices that build FHIR connectivity now are building infrastructure that survives beyond WISeR

CMS is also exercising enforcement discretion to allow FHIR-based submissions in place of X12 278 transactions during the WISeR pilot. This is a temporary accommodation, not a permanent waiver. Understanding the distinction matters for your compliance team. For context on how regulatory coding accuracy intersects with audit risk, review how CMS Medically Unlikely Edits (MUEs) work and how edit failures can surface downstream billing problems.

Technical Requirements: FHIR Standards, APIs, and Security Protocols

This is where WISeR becomes genuinely complex for practices without dedicated IT resources. To fully participate in the electronic PA workflow, providers and their EHR vendors must support the following standards:

•       HL7 FHIR Release 4.0.1 as the base data exchange standard

•       US Core Implementation Guide for patient and clinical data

•       SMART on FHIR for secure application authorization

•       Da Vinci Coverage Requirements Discovery (CRD) to identify whether a service needs PA in real time

•       Da Vinci Documentation Templates and Rules (DTR) to pull and populate required clinical forms

•       Da Vinci Prior Auth Support (PAS) to submit the actual authorization request

Security requirements include mutual TLS (mTLS) or UDAP protocols to authenticate connections between provider systems and payer APIs. This is not a plug-and-play situation. Your EHR vendor needs to certify compatibility or you need an intermediary solution.

Simpler Path: If your EHR is not yet FHIR-ready, CMS's Provider Compliance Group (PCG-FHIR) offers a platform that bridges X12 ESA submissions into the FHIR workflow. Vendor portals and fax submission through the MAC are also accepted during the pilot.

The technical barrier to API connectivity is real, but manageable. Practices already working through medical billing and coding audit services should use that workflow as a baseline to identify documentation gaps before WISeR reviews expose them.

The WISeR Prior Authorization Workflow Step by Step

Understanding the process flow is the fastest way to prevent submission errors, missed UTNs, and denied claims. Here is how the workflow operates from end to end.

01	Provider Identifies WISeR Service Before scheduling, confirm the service falls under the WISeR list (skin substitutes, nerve stimulators, certain spinal procedures).
02	Submit PA Request Send the request to the state-assigned tech vendor portal or API, or submit to your MAC who will forward it to the participant.
03	Tech Participant Reviews The vendor uses clinical analytics and clinician review to evaluate the request within 3 calendar days (2 days for expedited).
04	Decision Issued If affirmed, the MAC issues a Unique Tracking Number (UTN) valid for 120 days. If denied, a non-affirmation notice is sent.
05	Claim Submitted with UTN Include the UTN in the claim remark field. Claims without a valid UTN are held for pre-payment review and may be denied.
06	Resubmission if Denied Providers may resubmit unlimited times with additional documentation using the same original UTN to pursue approval.

One critical nuance: if a provider submits the PA request directly to the MAC (rather than to the tech participant), the MAC will forward it. Either path is valid. The UTN still comes from the MAC regardless of submission route.

Providers managing high-volume Medicare patient panels will feel this most acutely in scheduling and pre-authorization workflows. The principles of patient scheduling strategies that boost practice revenue become especially relevant when PA timelines are now a rate-limiting step before services can be performed.

 Billing and Coding Implications Under WISeR

The billing rule change that will impact your revenue cycle most directly is the Unique Tracking Number requirement. Every claim for a WISeR-covered service must include the UTN issued by the MAC. Without it, your claim will be held and routed for pre-payment review.

UTN Rules at a Glance

•       UTNs are valid for 120 days from the date of issuance

•       The UTN must appear in the appropriate remark field on both paper and electronic claims

•       If a service is performed without an affirmed UTN, the claim will not be automatically denied but will be flagged for additional review

•       No new HCPCS modifier has been announced specifically for WISeR claims

•       Advance Beneficiary Notices (ABNs) apply only when a denial is issued and the provider believes Medicare will not cover the service after review

The resubmission rules are more provider-friendly than typical PA frameworks. There is no cap on the number of times a denied PA can be resubmitted with additional clinical documentation. Peer-to-peer review with the participant's clinical team is also available, though not mandatory.

For practices that have already refined their claim accuracy workflows, the UTN requirement adds a trackable data element rather than a fundamental process overhaul. See how Medicare NCCI edits affect claim accuracy to understand how layered claim edits interact with newer administrative requirements like UTN validation.

Important: Existing CMS prior authorization coding rules apply. No WISeR-specific modifier has been released. Billers should document UTN issuance dates and attach them to patient records for audit readiness.

Compliance and Audit Risks

WISeR creates new audit exposure at two distinct points in the revenue cycle: before the service (if PA was not properly obtained) and after the claim is submitted (if the UTN is missing or expired).

CMS has made clear that claims for WISeR services submitted without a valid UTN on file will be held for pre-payment review. If a MAC suspends a claim and the participant cannot verify an affirmed PA exists, the claim faces denial with no automatic payment pathway.

From a HIPAA compliance perspective, CMS is currently allowing FHIR-based data exchange to satisfy the PA submission requirement in place of the standard X12 278 transaction. However, this enforcement discretion does not extend to the PHI security standards that govern data transmission. All WISeR-related data exchanges must still comply with HIPAA privacy and security requirements.

Audit readiness under WISeR means maintaining PA submission records, UTN issuance logs, denial notices, and any resubmission documentation in an organized, retrievable format. The same discipline that protects practices during NCCI or MUE audits applies here. Review our overview of medical billing and coding audit services to assess whether your current audit infrastructure is ready for WISeR-level scrutiny.

Payer vs Provider Responsibilities Under WISeR

Understanding who owns what part of the WISeR workflow eliminates the most common source of PA bottlenecks. The following table breaks down responsibilities by role.

Aspect	Payer (MAC) Responsibilities	Provider Responsibilities
Prior Authorization	Accept PA requests via FHIR API or portal and fax. Forward MAC requests to the tech participant. Issue UTN on all affirmed decisions.	Identify WISeR services before scheduling. Submit PA to the model participant or MAC. Include urgency flag when medically needed.
Turnaround Times	Process PA requests within 3 calendar days. 2 days for expedited cases. Issue UTN and communicate decision immediately.	Submit requests well before planned service. Track PA timelines against patient schedules to prevent care delays.
Claims and UTN Handling	Provide a UTN for each affirmed PA. Monitor claims and suspend WISeR claims missing UTNs. Route flagged claims for pre-payment review.	Always include the UTN on WISeR claims. Bill within the 120-day UTN validity window. Expect hold or denial without a UTN.
Denials and Appeals	Send formal non-affirmation notices. Allow unlimited resubmissions. Handle appeals via standard Medicare processes.	Resubmit with additional clinical documentation. Use the original UTN on resubmissions. Educate staff on appeal rights and timelines.
Compliance and Security	Comply with HIPAA standards. CMS is exercising enforcement discretion to allow FHIR in place of X12 278 for PA. Report suspicious activity.	Protect patient consent and PHI when exchanging data via API tools. Maintain current provider credentials. Participate in audits.

WISeR Participants by State: Who Is Handling Your Reviews

CMS has assigned one technology vendor per pilot state. Knowing which participant serves your geography determines where PA requests should be submitted directly, which portal to access, and which contact to escalate to if issues arise.

State	Assigned WISeR Tech Participant
Arizona (AZ)	Cohere Health
New Jersey (NJ)	Genzeon
Ohio (OH)	Innovaccer
Oklahoma (OK)	Humata Health
Texas (TX)	VirTix
Washington (WA)	Zyter

Providers in these states have two submission options. They can submit directly to the state-assigned participant through that vendor's web portal or API endpoint. Or they can submit through the MAC, which will route the request to the participant on the provider's behalf. Either path works. The UTN still comes from the MAC regardless.

For practices managing multi-state provider networks or those working across state lines, understanding which participant governs which geography is non-negotiable. The same logic applies when managing medical billing services across different payer environments.

Implementation Challenges and How to Get Ahead of Them

Every major CMS operational change creates friction during implementation. WISeR is no different. The most pressing challenges practices are encountering fall into three categories.

EHR and API Integration

Most practices are not yet running FHIR-native workflows. If your EHR does not support the Da Vinci IGs natively, you need either a vendor upgrade or an intermediary platform like PCG-FHIR. Delaying this decision has a direct revenue impact because claims submitted without proper UTN documentation get held.

Staff Training and Workflow Updates

Front desk and billing staff need to understand which services fall under WISeR coverage, when to initiate PA before scheduling, and how to track UTN issuance and expiration dates. This is especially important for practices where front office management and billing functions overlap. Creating a WISeR-specific pre-service checklist dramatically reduces downstream claim errors.

Coordinating with MACs and Participants

Practices submitting through the MAC need to verify that the MAC is properly routing requests to the state participant. Early in the pilot, routing delays created PA limbo situations where requests were technically submitted but not yet received by the participant within the decision window.

For practices already working with HMS on revenue cycle management, these workflow integrations are being built into our standard client support framework. Explore how our medical billing services handle prior authorization coordination as part of a complete RCM solution.

Frequently Asked Questions About WISeR

Which services require prior authorization under WISeR?

CMS designed WISeR to target services that federal spending data identifies as overutilized. Current covered services include skin substitute products, peripheral nerve stimulators, and certain spinal procedures. The full list is defined in the WISeR RFA documentation and may expand as the pilot progresses through 2031.

What happens if a provider performs a WISeR service without prior authorization?

The claim will not be automatically denied, but it will be held for pre-payment review by the MAC. The MAC routes it to the WISeR participant for evaluation. If the participant cannot verify an affirmed PA exists, the claim faces denial. Providers can still submit documentation post-service, but payment will be delayed.

How long does a UTN remain valid?

UTNs issued by the MAC are valid for 120 days from the issuance date. If a planned service is delayed beyond that window, a new PA request must be submitted and a new UTN obtained before the claim can be filed.

Can a WISeR denial be appealed?

Yes. Providers can resubmit a denied PA request an unlimited number of times with additional clinical documentation. Peer-to-peer review with the participant's clinical team is also available. If a claim is formally denied after PA review, standard Medicare appeals processes apply.

Does WISeR apply to Medicare Advantage patients?

No. WISeR applies specifically to Original Medicare (Medicare fee-for-service) patients. Medicare Advantage plans operate under separate prior authorization frameworks governed by plan-level rules and the CMS-0057-F interoperability mandate.

Future Outlook: What Happens After 2026

WISeR is a pilot. That means CMS is watching it carefully to decide whether mandatory prior authorization should expand to additional services, additional states, or eventually become a permanent Medicare program feature. The data collected through 2031 will directly inform those decisions.

Several trends worth tracking through 2028:

•       FHIR IG versions are actively evolving. Post-2026 updates to the Da Vinci IGs may require payer and provider system updates

•       CMS may add services to the WISeR coverage list based on spending analysis

•       Other regional MACs may adopt WISeR-style PA models even outside the six pilot states

•       The January 2027 deadline for payer FHIR API compliance under CMS-0057-F will pressure the entire industry toward standardized electronic PA

Practices that treat this pilot as a temporary inconvenience will face a harder transition if WISeR expands. The smarter move is to build FHIR-capable workflows now, train billing teams on UTN tracking, and establish PA documentation standards that hold up under audit scrutiny. For practices that want guidance navigating both the current WISeR requirements and the broader Medicare policy landscape, our medical billing services and provider quality payment program support are designed to carry that operational weight.

Final Word

WISeR is not a bureaucratic detour. It is a direct line between PA compliance and your claim payment timeline. Every WISeR service that hits a claim hold, a missing UTN flag, or a pre-payment review is revenue that is delayed or at risk. The practices that come out of this pilot in the strongest position will be those that treated January 2026 as a deadline, not a warning.

The checklist is not long. Confirm which services fall under WISeR. Identify your state participant. Get your EHR or portal submission workflow functional. Train your front office to initiate PA before scheduling. Track UTN issuance dates like you track everything else in your revenue cycle.

That is the work. And for practices that want a partner in carrying it, HMS USA LLC is built for exactly this moment.