Table of Contents

If your practice is in Arizona, New Jersey, Ohio, Oklahoma, Texas, or Washington, one case can now trigger two separate prior auth requests from the same payer. Most billing teams have not mapped this yet. 

The gap between your WISeR procedure Prior-Auth and your CMS drug PA is where denials are being built. Your revenue cycle management software needs to handle both together. A workflow that tracks procedure PA and drug PA separately will miss timing mismatches. By the time the gap is visible, the denial is already posted. 

What the Two-Layer Problem Actually Looks Like

WISeR requires prior auth for covered procedures. These include epidural steroid injections, nerve blocks, and pain management work. Each PA has its own documents, criteria, and timeline.

CMS drug policy adds a second PA on top of that. It covers the injectable corticosteroid itself. Same payer. Same case. But a totally separate auth pathway. Different review criteria. Different approval windows.

Here is where the risk builds. When a pain management or ortho ASC bills a corticosteroid injection with a WISeR-covered procedure, both parts face their own independent review. If either auth is missing, incomplete, or off in timing, the whole case can be denied. Not just the drug line.

Where Billing Workflows Break Down

The real failure here is sequencing. Most billing teams treat PA as one pre-service checkpoint. They get auth for the procedure, document it, and move on. The drug PA gets handled separately by someone else – or it gets missed entirely. It was never part of the traditional pre-auth workflow, so no one built a step for it.

That fragmentation creates three specific failure points.

First, the procedure PA and drug PA may go to the same payer portal through different queues. Staff often do not know both are required until a claim comes back denied. Second, the supporting documents for each PA can differ. The procedure PA usually needs imaging and functional status notes. The drug PA may need medication history, dosage justification, or step therapy records. Gathering both at the same time is a coordination task, not just a filing task.

Third, approval timelines may not line up. A procedure PA approved for a specific date of service can expire or fall out of the valid window if the drug PA takes longer to process.

Practices that rely on disconnected tools will miss timing mismatches. Denials pile up fast and turn into a long appeals backlog. See how integrated billing and RCM operations close that gap before it grows.

Why This Scales Badly Without a Coordinated System

A single-provider pain practice billing ten WISeR-eligible cases per month can manage this manually. An ortho ASC running 30 to 50 cases per week cannot. Each case now requires two intake checks, two documentation pulls, and two timeline monitors. None of those are connected by default. Staff time increases. Denial rates climb. Reimbursement cycles slow down.

The first sign of trouble is usually a cluster of denials, not a workflow audit. By that point, the appeals backlog is already growing. Staff are reacting to problems instead of managing pre-service compliance.

This is the gap that good revenue cycle management software is built to close. It does not just automate PA submissions on their own. It connects the procedure PA and drug PA into one case-level workflow. Documents are shared. Timelines are tracked together. And the billing team gets a clear, joined-up view of status for both auths at once.

What Coordinated PA Management Requires at the Case Level

Fixing this operationally means treating the two-authorization requirement as a single case compliance event, not two parallel tasks.

At intake, your billing team needs to flag every WISeR-eligible case that includes an injectable drug. That flag should trigger a dual-PA checklist inside the same case record — one path for the procedure, one for the drug. Pull the documentation requirements for both at the same time, not one after the other. Track the drug PA timeline against the scheduled date of service from the moment the case is opened.

This is exactly what CERTIFY Pay is built to handle. It links procedure-level and drug-level PA workflows inside a single case view. Billing managers can see where each auth stands, what documents are still missing, and whether the timelines line up — all before the case moves to claim.

What Your Workflow Needs to Handle Before the Next Case

WISeR is active in six states. CMS drug PA rules apply everywhere. That overlap is live now.

Auditing your PA process for dual-auth gaps is no longer optional. For most ortho and pain ASCs in these states, the double PA review is not a future risk. It is already here.

The real question is simple: does your workflow track both auths at the same time?

If your team handles WISeR procedure PAs and drug PAs as two separate tasks, every affected case carries denial risk. Auth gaps early in the process hurt you later. Delayed or denied claims push costs back into the patient payment resolution cycle – and that creates a second problem on top of the first.

Map Your PA Overlap Before the Next Denial Cycle

Start by pulling your last 60 days of WISeR-eligible cases. Identify which ones included an injectable corticosteroid or a drug subject to CMS PA requirements. For each case, check three things: whether both a procedure PA and a drug PA were obtained, whether the documents met each payer’s criteria, and whether the approval dates lined up with the date of service.

That audit will show you exactly where your workflow is exposed. The fix requires a structural change to your pre-service process – not a workaround. You need case-level tracking, joint documentation checklists, and timeline monitoring that treats both auths as one compliance requirement.

Talk to our team about coordinated billing workflows and map your WISeR and drug PA overlap before it becomes a denial pattern.