When an Authorization Expires Before the Appointment Does

Most pain practices treat approval as the finish line. Somebody submits, somebody waits, the answer comes back yes, and the file closes. Then the patient reschedules twice, the surgery center moves a block, and the authorization expires four days before the procedure finally happens.

Nobody in the building did anything wrong. The paperwork was correct, the answer was favorable, and the visit still got billed against an approval that had run out.

The reason is structural. An approval is a dated object with a start and an end, and the appointment is a separate dated object that moves whenever a patient’s life moves. Almost no front office holds those two dates in the same view.

So the failure shows up at checkout, weeks after anybody could have fixed it cheaply. The work was already done. It just aged out.

The approval is a dated object now, not a filed answer

Review requirements are expanding, and the newer ones come with explicit windows attached. CMS is running the WISeR (Wasteful and Inappropriate Service Reduction) Model for six performance years, from January 1, 2026 to December 31, 2031, in six states: New Jersey, Ohio, Oklahoma, Texas, Arizona, and Washington. CMS frames the problem it is aimed at plainly, saying waste contributes up to 25% of health care spending in the United States.

For a pain practice the policy debate is beside the point. The operational consequence is that more of your procedure mix carries a review step, in more places, and the answer you get back has a life span.

That changes what the front office has to hold. Not a yes or a no, but a yes with a date on it, attached to a patient who has not been scheduled yet.

The window is measured in months, and the schedule moves in weeks

Under the WISeR model, once a prior authorization request is approved, the unique tracking number associated with it is valid for 120 calendar days starting from the decision date. CMS gives the worked version in its own guide: a request affirmed on January 5, 2026 is valid for dates of service through May 4, 2026, and after that the practice has to submit a new request and obtain a new tracking number. Determinations are typically issued within 3 calendar days of receipt, with an expedited path for cases where a delay would put the patient at risk.

Four months sounds generous until you put a real pain patient’s calendar next to it. An approval issued in early January against a procedure block that is full until late March leaves a few weeks of margin. One reschedule eats it.

And the arithmetic gets sharper with partial answers. Some codes on a single request can be approved while others are not, which means the visit is half covered and somebody has to notice before the patient is in the building.

So the practical unit of work is not the authorization and it is not the appointment. It is the pair, and it needs a single owner.

Two places the pair comes apart

The first is booking. At one multi-site pain practice, between six and eight in every hundred procedures were being scheduled outside the authorization window by human schedulers. Not through carelessness. The scheduler is looking at open slots and a patient who wants the earliest one, and the window lives in a different system entirely.

The second is rescheduling, and it is quieter. Moving an appointment silently breaks the link to the authorization. The new booking is not attached to the existing approval, and an appointment whose authorization has not come back can only be pushed later, never pulled earlier. A front desk that reschedules a patient to help them has just created a claim problem nobody will see for a month.

Both of these are fixable at the moment they happen, and only at that moment. Once the visit is done, the options are an appeal or a write-off.

What the automation does here is narrow and specific. Before offering a slot for a procedure that requires review, it reads the current authorization record for that patient in athenaOne, checks the validity window against the open slots it is about to offer, and does not offer a date the approval will not reach. When a booked appointment moves, it re-checks the pair and flags the ones that have come apart.

What the front office should be able to see every morning

Most of the money in revenue cycle is lost before anyone sends a statement. A January 6, 2026, MGMA Stat poll found the biggest revenue cycle leaks for practices today are denials and appeals at 48%, followed by front end issues at 23%, billing and collections at 14%, coding at 13%, and charge posting at 2%.

The expiry problem is a front end issue that reports as a denial, which is part of why it stays invisible. It gets counted in the 48% and fixed in the appeals queue, months downstream of the desk that could have prevented it.

A working view has four lists on it. Approvals granted with no appointment attached. Appointments booked with no approval attached. Pairs where the appointment sits outside the validity window. And approvals inside their last thirty days with the procedure still unscheduled.

None of that requires new data. All four come from records athenaOne already holds, joined on the patient and read on a daily cadence rather than when somebody remembers. The list is short enough to work before the first patient arrives.

Where the automation stops, on purpose

This is the part worth being precise about, because the review programs are medical necessity reviews and the line matters.

PGA does not decide whether a service is appropriate, does not assemble or judge the supporting documentation, and does not take a position on what the patient needs. Those belong to the clinician requesting the service, full stop.

What is in scope is everything around that. Knowing which encounters carry a review requirement. Tracking status and validity dates. Chasing the paperwork that has not come back. Getting the appointment inside the window. Telling the patient what is happening and when.

When a case needs a human, the handoff has to be specific rather than an alert. The item that lands with your authorization coordinator says which patient, which approval, which date it runs out, which slot is currently attached, and what the next available in-window slot would be. That is a decision they can make in thirty seconds. A notification that says review authorizations is a task they have to rebuild from scratch.

Ask a vendor to show you the expiry list

Front-office automation is easy to demo and hard to grade. If you are evaluating anything that claims to work authorizations on athenaOne, the useful request is not a call recording.

Ask to see the list of authorizations expiring in the next thirty days with no appointment attached, generated live from a real athenaOne connection. It is a boring screen. It is also the one that proves the tool reads authorization records and appointment records together, which is the only thing that makes any of the rest work.

Then ask what happens when the patient reschedules. If the answer involves a person noticing, you have bought a report rather than a process.

PGA works these lists across 440+ of athenahealth’s roughly 800 endpoints, which is the reason the pairing is available at all. Depth of access is what separates a tool that can tell you an authorization exists from one that can tell you it will not survive the appointment.

Key Takeaways

Treat the approval and the procedure slot as one object with one owner, because the failure is always the gap between two dates nobody holds together.
Check the validity window before offering a slot, not after the patient picks one, since an approval that cannot reach the date is not an approval.
Re-check the pair every time an appointment moves, because rescheduling breaks the link to the authorization silently.
Work a daily list of approvals with no appointment, appointments with no approval, out-of-window pairs, and approvals in their last thirty days.
Watch for partial answers, where some codes on a request are approved and others are not, and route those to a person before the patient arrives.
Keep the automation on tracking, chasing, and booking, and leave the necessity question with the clinician requesting the service.

An expired authorization is not a paperwork failure, it is a calendar failure that shows up as a paperwork failure sixty days later. Hold the approval and the slot in the same view, block the bookings that fall outside the window, re-check the pair on every reschedule, and hand your coordinator a list short enough to clear before the first patient walks in.

Sources