Practice Operations
Spine Surgery Prior Authorization on a Predictable Cadence
Spine surgery prior authorization runs on three clocks at once. Here is how AI keeps submissions, statuses and expirations moving inside athenaOne daily.
Spine surgery prior authorization is not a task, it is a cadence. Requests go out, statuses come back, approvals expire, and cases move. Run that rhythm every day and the surgical calendar holds. Run it whenever the authorization coordinator has an hour free and you get a queue that is always three days stale, which is exactly long enough for a case to be scheduled against an approval nobody checked.
A neurosurgical practice with a procedure-heavy mix carries more pending authorizations than it can hold in anyone’s head. Each one has a submission date, a status that changes without notice, and an expiration that arrives whether or not the case has been done.
The usual failure is not a denial. It is silence. A request sits at the plan, nobody calls to check, and the case comes up on the schedule with a status that was accurate two weeks ago. Somebody spends the afternoon on hold to find out what a portal could have told them, and the case moves anyway.
That backlog is not an administrative problem in a practice owner’s head. It is revenue already earned and not yet collectable. An MGMA Stat poll found the biggest revenue cycle leaks are denials and appeals (48%), followed by front end issues (23%), and both of those are decided in the weeks before a claim exists.
Every request runs on three clocks
Authorization work feels chaotic because three separate timers run on every request and only one of them shows up on the calendar.
The first is the submission clock, which starts when someone actually sends the request rather than when the surgeon decides to operate. The second is the decision clock at the plan. The third is the expiration clock on the approval itself, which is the one that quietly ruins a case that got pushed twice.
athenaOne holds the second and third of those as data. Authorization records carry status and validity dates, and benefit details carry what the plan requires. The automation reads them daily, groups the queue by which clock is closest to running out, and works the list in that order rather than in the order the requests were created.
Medicare is adding review where neurosurgery lives
Review requirements for procedures are moving, and a neurosurgical practice should plan for more of them rather than fewer. CMS is running the WISeR (Wasteful and Inappropriate Service Reduction) Model for six performance years, from January 1, 2026 to December 31, 2031, in New Jersey, Ohio, Oklahoma, Texas, Arizona and Washington.
The model focuses on a specific set of items and services, and one of them is electrical nerve stimulator implants. CMS frames the underlying problem plainly: waste contributes up to 25% of health care spending in the United States.
Whatever your view of the policy, the operational consequence is the same. More of your procedure mix will carry a review step, in more places, with more paperwork attached to it. A practice already running authorization on a daily cadence absorbs that. A practice running it in bursts does not.
Build the cadence on the published decision window
Under the CMS Interoperability and Prior Authorization Final Rule, impacted payers must send prior authorization decisions within 72 hours for expedited requests and seven calendar days for standard requests, with operational provisions generally beginning January 1, 2026 and a specific denial reason required beginning January 1, 2027.
That gives you an actual schedule to build against. A standard request submitted Tuesday has a decision due the following Tuesday, so the first status check belongs on the calendar rather than in someone’s intentions. A request that has heard nothing by then is a phone call, not a shrug.
The AI makes those calls and reads those statuses on the schedule the rule implies. Approvals get written back to the authorization record with their validity dates. Anything still silent past the window gets escalated with the full submission history attached, which is the difference between a productive call to the plan and a twenty-minute reconstruction.
The expiration nobody is watching
Approvals expire. A case that got moved for a facility conflict and then moved again for a patient conflict can land past the validity date on its own approval, and nothing on the schedule says so.
The same reschedule also breaks the link between the appointment and the authorization, so the case now looks unauthorized in one system and approved in another. And an appointment whose authorization has not returned can be pushed later safely but must never be pulled earlier into an open date, which is precisely what a scheduler filling a cancellation will try to do.
Automating this means every schedule change is re-checked against the authorization record. Cases that drift past their validity window surface before the week of, not during it. That is the same mechanic behind authorization timing in thoracic surgery, running against a larger and faster-moving queue.
Where the queue hands back to people
The AI does not argue medical necessity, write appeal language about why a procedure is warranted, or decide what a patient should have. It submits, checks, records, escalates, and keeps the queue current.
Denials go to your authorization coordinator with the plan’s stated reason and the full history. Requests for additional records go to the person who can pull them. A peer conversation goes on a surgeon’s calendar with the case packet already assembled. Those are the tasks worth a trained person’s day, and they are the ones that currently get squeezed by status checks.
No tool eliminates authorization work. What changes is that the repetitive part stops competing with the part that needs a trained person, so your coordinator is not choosing between them every afternoon.
Key Takeaways
- Work the authorization queue by which clock is closest to expiring, not by the order requests were created.
- Put the first status check on the calendar against the published decision window instead of waiting for the plan to volunteer an update.
- Write approvals and their validity dates back to the athenaOne authorization record so the schedule and the paperwork stay attached.
- Re-check every reschedule against the authorization, and never pull a case with a pending request into an earlier date.
- Plan for more review steps across your procedure mix, and build a daily cadence that can absorb them without new headcount.
Authorization backlog in a spine practice is revenue you have already earned sitting in a queue nobody has hours for. Run the queue daily against three clocks, check status when the published window closes rather than when someone remembers, keep validity dates attached to booked dates, and hand your coordinator the denials and the peer calls. The surgical calendar stops being a guess about paperwork you cannot see.
Sources
Ready to See It in Action?
See how PGA runs your authorization queue on a cadence inside athenaOne
Schedule a Demo →Written by Kevin Henrikson