Pain Point, Solved 4.9 ★★★★★ Google Rating

How Do I Stop CO-197 Denials When Patients Reschedule Procedures Past the Auth Expiration Date?

All Pain Points

Ask AI about this page

CO-197 fires on rescheduled procedures because every authorization approval carries a validity window with a start and end date, and the reschedule workflow rebooks the patient without checking the new date against that window; when the surgery lands even a day past the expiration, the auth is dead and the payer denies precertification absent. Because CO-197 is a contractual-obligation code, you eat the write-off and cannot bill the patient. It is almost never a missing auth; it is an expired one that nobody re-checked when the date moved. The fix has four moves: build an auth-date check into the reschedule step so any new date outside the window is caught before rebooking, request an extension the moment a date slips instead of after the fact, track every auth expiration in a dated work queue so nothing ages out silently, and when a denial does land, work the retro-auth or appeal path before timely filing closes. We run those moves inside the systems you already use, so a postponed surgery stops meaning a lost claim. The table of contents maps the whole method; the moves after it are the detail.

What Actually Stops the Expired-Auth Write-Off on Rescheduled Cases
Key Pain Points and Discussions by Providers
Why This Keeps Happening
The Solution
How We Permanently Fix the Process
The Whole Thing in Four Sentences
Frequently Asked Questions
Where the Claims on This Page Come From

What Actually Stops the Expired-Auth Write-Off on Rescheduled Cases

The goal is simple: no procedure ever reaches the OR on a date the auth does not cover, and any date that slips triggers an extension before the patient is rebooked. Here is what does that, move by move.

1. Put an Auth-Date Check Inside the Reschedule Step

The denial starts the moment someone rebooks a surgery without looking at the auth window. So the check has to live inside the reschedule action itself: before a new date is confirmed, the approved start and end dates are pulled and compared to it. If the new date falls inside the window, the rebooking goes through. If it falls outside, the case stops and routes to an extension request before the patient is ever given the new date. You cannot rely on memory for a window that was approved weeks ago and buried in a chart; the check has to be a step, not a habit.

2. Request the Auth Extension Before the Date Slips, Not After

Once a new date lands outside the window, the request goes to the payer for an extended or updated authorization while there is still time to get it approved. That is a completely different conversation than a retro request after the surgery already happened. Payers grant extensions on documented rescheduling far more readily before the fact than after, and getting the updated dates on file before the patient walks into the OR is what keeps the claim clean instead of turning it into an appeal.

3. Track Every Expiration in a Dated Work Queue

Auth windows do not announce themselves; they age out in silence. A dated work queue lists every open surgical auth by its expiration date, so the ones about to lapse surface before they do. A case that has been postponed twice shows up on the queue days ahead of its expiration, not the morning of surgery. That single view is what turns a landmine into a scheduled task, because you are working the calendar instead of discovering the problem in the remit.

4. Work the Retro-Auth or Appeal Before Timely Filing Closes

When a CO-197 does land, the clock that matters is timely filing. Some payers allow a retroactive authorization for documented scheduling changes, and where they do, that request goes out immediately with the reschedule history attached. Where they do not, the appeal makes the medical-necessity case and documents that a valid auth existed and only lapsed because the patient postponed. Either way it gets worked the day it lands, because a CO-197 that sits is a CO write-off you can never bill the patient for.

5. Hand Expiring-Auth Tracking to a Dedicated Team

Practices that stop losing rescheduled cases to CO-197 do it by handing auth-window tracking to a dedicated team: remote specialists who run the date check on every reschedule, request extensions before the fact, and work the dated queue so nothing lapses, live in 1 to 2 weeks. The surgeons and schedulers go back to running the OR, a trained backup covers every gap, and the expiring-auth queue stops being the thing nobody owns until it denies. Below is what it sounds like when nobody owns it yet, in providers’ own words.

Key Pain Points and Discussions by Providers

real reports from practice staff, lightly edited

“We had a clean auth for the arthroscopy, the patient pushed the date twice, and by the time we operated the window had closed. CO-197, and because it is a CO code I cannot even bill the patient. The auth was never the problem. Nobody re-checked the dates when the surgery moved.” – billing lead, orthopedic practice

“The reschedule happens at the front desk and the auth expiration lives in the billing system, and those two never talk. A patient postpones, we rebook, and nobody realizes the approval expired in between until the denial shows up weeks later.” – practice administrator, surgical group

“I found out the hard way that a 60-day auth means 60 days, not whenever the patient feels like coming in. We lost a full knee case to nine days over the window. There was no way to bill the patient and no retro option with that payer.” – office manager, orthopedic practice

“Every postponed surgery is a small bomb waiting in the schedule. We do not have anything that flags an auth about to expire, so we find out when the remit comes back CO-197 and it is already too late to extend.” – revenue cycle lead, orthopedic group

“When I finally started asking for extensions before the new surgery date instead of after, the denials mostly stopped. The payers were fine granting it up front. The problem was we were always asking after the case had already slipped past the window.” – billing manager, surgical practice

Our Answer

Here is what we actually do. A dedicated remote specialist builds an auth-date check into your reschedule workflow, so before any surgery is rebooked, the new date is compared to the approved start and end dates. If it falls outside the window, the case stops and an extension request goes to the payer before the patient is given a new date, with the reschedule history attached. Every open surgical auth sits in a dated work queue tracked by expiration, so nothing ages out in silence, and when a CO-197 does land, the specialist works the retro-auth or appeal the same day, before timely filing closes. Our specialists are credentialed professionals, overseas-trained physicians and US-licensed nurses and pharmacists, working inside your scheduling and billing systems, with AI drafting the first pass and a human verifying every submission. This is our prior authorization support paired with an AI-first workflow, in one paragraph.

Why This Keeps Happening

If the auth was valid when you got it, why does the surgery still deny? Because an authorization is not open-ended; it is approved for a specific date range, and the reschedule workflow at most practices simply never checks the new date against that range. The auth number sits in the chart looking valid, but the window quietly closed while the patient was postponing. CO-197 means precertification or authorization was absent at the time of service, and an expired auth is, to the payer’s adjudication system, exactly the same as no auth at all. The order was right and the approval was real; the calendar just moved out from under it.

The volume is what makes this hurt at scale. The American Medical Association’s 2024 prior authorization survey reports that practices complete an average of 39 authorization requests per physician every week and spend about 13 hours per physician doing it. When a surgical case gets rescheduled, its auth is one of dozens moving through that workload, and re-verifying the window on a moved date is exactly the kind of step that falls off a plate that is already full. The auth does not get re-checked because there is no room in the day to re-check it, and closing that gap is what an AI prior authorization workflow with human oversight is built to do.

And the cost of a CO-197 is uniquely bad. Because it is a contractual-obligation code, the payer’s ruling is that the missing authorization was the provider’s responsibility, so you absorb the entire charge and are barred from billing the patient for it. A denied claim you can rebill is a nuisance; a CO-197 write-off on a full surgical case is revenue that is simply gone. One knee arthroscopy lost to an expired window is not a coding cleanup, it is a five-figure procedure billed at zero, and it happened because a date moved and nobody caught it in time.

⚠️ The quiet one that hurts most: The quiet one that hurts most: the auth looks valid right up until the moment it is not. A number sitting in the chart gives everyone false confidence, so a rescheduled case sails through booking as if it is covered, and the expiration is invisible until the remit comes back CO-197. By then the surgery has already happened, the window has already closed, and because it is a CO code there is no patient to bill. Unless someone checks the actual date range every time a surgery moves, the most expensive denials are the ones that were fully authorized when they were booked and silently expired before they happened.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

What you tried	What actually happened	Who ended up doing the work
Trusted the auth number already in the chart	The number looked valid but the window had expired while the patient postponed, and the claim denied CO-197	Whoever rebooked the surgery
Asked for a retro authorization after the denial	The payer would not grant retro for a scheduling change, and there was no patient to bill on a CO code	The billing team, after the fact
Reminded schedulers to watch auth dates	It worked until the desk got busy; a postponed case slipped past the window again the next month	Whoever remembered that day
Gave expiring-auth tracking to a dedicated specialist	Date checked on every reschedule, extension requested before the slip, dated queue worked so nothing ages out	Someone whose whole job it is

The Solution

So what does “someone whose whole job it is” look like on a rescheduled surgery? The specialist runs the date check before the case is rebooked, not after. When the patient calls to postpone, the new date is compared to the approved window before it is confirmed, and if it falls outside, the case stops and an extension request goes to the payer with the reschedule history attached. The patient gets a date the auth actually covers. Most CO-197 denials on moved surgeries are a date-tracking problem, and that is exactly what dedicated prior authorization support is built to solve, before it ever becomes a write-off.

Behind the reschedule check sits the dated work queue. Every open surgical auth is tracked by its expiration date, so a case that has been postponed twice surfaces days before its window closes, not the morning of surgery. The specialist works that queue every day, requesting extensions on the ones about to lapse and confirming the ones already inside their window are still clean. When a CO-197 does land despite everything, they work the retro-auth or appeal immediately, because timely filing is the only clock that can turn a workable denial into a permanent loss.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow flags the expiring auths, drafts the extension request, and tracks the deadline; a person confirms the dates are right and owns the payer conversation and the appeal. Every security control that protects the chart and scheduling data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving clinical and scheduling data through an auth workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team catch your expiring auths better than your own staff? Because tracking authorization windows and working extensions is their entire day, not the thing they squeeze between check-ins and OR turnover. The people working your auths are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US prior authorization and surgical scheduling workflows. They know what a validity window is, how to read a reschedule against it, and how to word an extension request so the payer grants it before the case slips. That is not a task for whoever is closest to the phone; it is a specialty.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so a rescheduled surgery never slips past its window because the one person who tracks auths is on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

✓ What stops happening: What stops happening: the CO-197 write-off on a surgery that was fully authorized when it was booked. The knee case lost to nine days past the window. The retro request the payer refuses to grant after the fact. The scheduler rebooking a patient onto a date the auth never covered. The expiring-auth queue nobody owns until it shows up in the remit as a five-figure procedure billed at zero.

2-Week Free Trial

Ready to Stop Losing Rescheduled Cases to CO-197?

Book A Strategy Call Request Information

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented auth-window workflow: which payers grant extensions and on what terms, how each one wants a rescheduled date documented, the retro-authorization rules per plan, and the timely-filing deadlines, all written down and worked the same way every time. Before we take a single auth for a new practice, we chart your rescheduled-case denials by payer so we can see where surgeries are actually being lost to expired windows, and we build the workflow against that, not against a generic template.

From there the workflow becomes a living playbook rather than one coordinator’s memory. It records every payer’s validity-window rules, how to request an extension before a case slips, which plans allow retro authorization for scheduling changes, and the escalation path when a CO-197 lands. It is written down, kept current as payers change their rules, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so a postponed surgery never ages out because one person was away the week it slipped.

That is the difference between writing off this month’s expired auths and fixing the process for good, and it is what a dedicated prior authorization partner actually buys you. A coordinator leaving used to mean the expiring-auth queue fell apart and rescheduled cases started denying again. Under this model the workflow keeps running, the playbook stays, the backup steps in, and a moved surgery stops being the thing that quietly writes off a full procedure.

The Whole Thing in Four Sentences

CO-197 fires on rescheduled procedures because the authorization was approved for a date range, the patient postponed past it, and the reschedule workflow never checked the new date against the window, so a valid auth quietly expired before the surgery happened. Trusting the number in the chart, asking for retro after the fact, or reminding schedulers to watch dates all fail the same way. The fix is an auth-date check inside the reschedule step, an extension request before the slip, a dated queue so nothing ages out, and the retro or appeal worked before timely filing closes. An orthopedic and surgical group runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to stop losing rescheduled cases to CO-197? Try us risk free: two weeks, your real expiring-auth queue, dedicated specialists running the date checks and working the extensions, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Transparent Weekly Pricing

One Flat Weekly Rate. 45 Hours of Coverage.

No hourly meters, no setup fees, no long-term contracts. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.

Single

$399/ week

One dedicated remote specialist tracking auth expiration windows and extension requests across your surgical schedule, single-site orthopedic practice or ASC

Stop the CO-197 Write-Offs This Month

You have seen the whole method. The pilot proves it on your own rescheduled-case queue, with a tracker your team can watch every day.

Start My 2-Week Free Trial

Request Information or call directly: (800) 489-5877

Request Information

Single specialty or multi-site? One payer or many? Tell us your situation and we will map the right coverage within 24 hours.

Frequently Asked Questions

Why did my claim deny CO-197 when I had a valid authorization on file?

Because the authorization was valid for a specific date range, and the surgery landed past the end of that window after the patient rescheduled. CO-197 means precertification or authorization was absent at the time of service, and to the payer’s system an expired auth is the same as no auth. The number in the chart looked valid, but the validity window had closed, so a fully approved case denied the moment it was rebooked onto a date the auth no longer covered.

Can I bill the patient when a rescheduled surgery denies CO-197?

No. CO-197 is a contractual-obligation code, which means the payer has ruled the missing authorization was the provider’s responsibility, so you absorb the charge and are barred from billing the patient. That is what makes an expired-auth denial so costly: it is not a claim you can rebill or shift to the patient, it is a write-off. The only paths are a retro authorization where the payer allows it or a formal appeal, both worked before timely filing closes.

How do I stop authorizations from expiring when patients reschedule?

Put an auth-date check inside the reschedule step itself. Before any new surgery date is confirmed, compare it to the approved start and end dates; if it falls outside the window, stop the rebooking and request an extension before the patient is given the date. Track every open auth in a dated work queue by expiration so postponed cases surface days ahead, not the morning of surgery. The fix is catching the slip before the case is rebooked, not after the remit comes back.

Will a payer grant an authorization extension for a rescheduled procedure?

Often yes, if you ask before the case slips past the window and document the reschedule. Payers grant extensions on documented scheduling changes far more readily up front than as a retro request after the surgery already happened. The key is requesting the updated dates while there is still time to get them on file, with the reschedule history attached, so the auth covers the actual date the patient walks into the OR.

How much does outsourced prior authorization for surgical scheduling cost?

Staffingly charges a flat weekly rate per dedicated remote specialist, with lower per-person rates for teams of 5 or more and 10 or more. Every plan covers 45 hours of coverage per week with a trained backup included, and there is no percentage of your reimbursement. The pricing section on this page shows how the flat rate compares with typical US market rates for this work.

Will AI be making decisions on my authorizations?

No. AI drafts the first pass, flagging the expiring auths, drafting the extension request, and tracking the deadline, and a credentialed human verifies every submission and owns the payer conversation and the appeal. The judgment stays with people. Automation removes the repetitive tracking work so the specialist spends their time on the cases that need a human, not on scanning a schedule for dates about to lapse.

Do we have to change our scheduling system or EMR?

No. Our specialists work inside the scheduling and billing systems you already use, so there is no migration and no new platform for your staff to learn. They read your auths and reschedules where they already live and submit through the payer portals you already have, which is why a typical practice is live in 1 to 2 weeks rather than months.

How fast will we see fewer rescheduled cases denying CO-197?

Usually within the first two weeks. Once a dedicated specialist is running the date check on every reschedule, requesting extensions before cases slip, and working a dated queue so nothing ages out, the surgeries that used to expire silently start reaching the OR on dates the auth actually covers, and the CO-197 write-offs stop appearing in the remit.

How does one flat weekly rate cover 45 hours every week?

Your dedicated specialist works a 9-hour day, Monday to Friday, which is 45 hours of coverage each week. The ninth hour is part of the flat weekly rate, not billed as overtime. Over a year that is 2,340 hours of coverage, against the standard US full-time work year of 2,080 hours (40 hours x 52 weeks, the same basis the U.S. Office of Personnel Management uses to compute hourly rates of pay). That is how $399 per week works out to $8.87 per hour.

Written By

Dan Nandan

Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From

Sources & References

American Medical Association Prior Authorization Physician Survey. Physician-reported data on authorization volume and burden, including that practices average roughly 39 authorization requests per physician per week and about 13 hours per physician processing them. ama-assn.org
CMS Claim Adjustment Reason Codes. Official reference for adjustment codes including CO-197, precertification/authorization/notification absent, and the contractual-obligation group code that bars billing the patient. cms.gov
MGMA Practice Operations and Prior Authorization Resources. Benchmarks and guidance on authorization workload, surgical scheduling, and patient access for medical group practices. mgma.com
HFMA Revenue Cycle and Denials Management Resources. Guidance on authorization-related denials, appeals workflow, and the revenue impact of expired or lapsed authorizations. hfma.org
American Academy of Orthopaedic Surgeons Practice Management Resources. Guidance on authorization and scheduling workflow for orthopedic surgical practices. aaos.org