Why Are Post-Op Office Visits Denying CO-97 and Which Modifier Fixes It?

How to Clear a Post-Op CO-97 and See the Global Window First

The goal is simple: every visit inside a global window flagged before it bills, the right modifier applied, and the separately payable services paid instead of bundled. Here is what does that, move by move.

1. See the Global Window Before You Bill the Visit

The root of a post-op CO-97 is visibility, not coding. A surgeon’s patient can be inside a 0, 10, or 90-day global period from an earlier procedure, and if the schedule and the charge do not flag it, the visit bills as if there were no window, and the payer bundles it. Track the global period on every surgical patient so any visit that falls inside a window is flagged the moment it is scheduled. You cannot append the right modifier to a window you cannot see, and the window is where every one of these denials starts.

2. Apply Modifier 24 for an Unrelated E/M Visit

When the patient is inside a global window but comes in for an evaluation and management visit unrelated to the surgery, modifier 24 tells the payer the service is separate. The key is the diagnosis: the unrelated E/M has to carry a distinct diagnosis that shows it is not follow-up for the operation. A knee-replacement patient seen for a shoulder problem is a classic case. Modifier 24 with the shoulder diagnosis is what turns a bundled denial into a paid visit.

3. Use Modifier 79 or 78 for Procedures in the Window

Not every in-window service is an office visit. When the surgeon performs an unrelated procedure during the postoperative period, modifier 79 marks it as separate. When the patient returns to the operating room for a related complication of the original surgery, modifier 78 applies. Choosing between 24, 79, and 78 depends on whether the service is an E/M or a procedure and whether it is related or unrelated to the original surgery, and getting that choice right is what makes the service payable instead of bundled.

4. Appeal Misapplied Global Denials With the Documentation

Some CO-97 global denials are simply wrong: the payer bundled a service that was genuinely separate, or the modifier was applied correctly and the claim still denied. Those get appealed, not written off. The appeal packet pairs the operative note that defines the original global period with the visit documentation that shows the new service was unrelated or a separate procedure. Tracking which post-op denials are winnable appeals versus which need a corrected modifier is what keeps separately payable revenue from quietly disappearing into the surgical package.

5. Hand Global-Period Work to a Dedicated Team

Practices that stop losing post-op visits to bundling do it by handing global-period tracking and modifiers to a dedicated team: remote specialists who flag every window, apply the right modifier, and appeal the misapplied denials, live in 1 to 2 weeks. The surgeon and the coder go back to the work only they can do, a trained backup covers every gap, and the post-op denial queue stops being the thing nobody has visibility into. Below is what it sounds like when nobody owns it yet, in providers’ own words.

Why This Keeps Happening

If the visit was separately payable, why does it bundle? Because the global surgical package is designed to include related follow-up care for a set window, and Medicare defines three of them: a 0-day period for endoscopies and minor procedures, a 10-day period for other minor procedures, and a 90-day period for major surgery. Inside that window, the payer assumes any related service is already paid for in the surgical fee. The system does exactly what it is built to do. The failure is that a separately payable service, an unrelated visit or procedure, went out without the modifier that tells the payer it does not belong to the package.

The reason the modifier goes missing is visibility, not knowledge. Most schedulers and coders have no built-in view of which patients are inside a global window on any given day, so a visit gets booked and charged as if the earlier surgery never happened. By the time the CO-97 comes back, the practice is reworking a claim that should have carried modifier 24, 79, or 78 from the start. Closing that visibility gap, seeing the window before the claim goes out, is exactly the kind of tracking a dedicated revenue cycle management workflow is built to provide.

And the cost hides in plain sight. A bundled post-op visit does not look like a denial to fight; it looks like a service that was correctly included, so it gets written off without a second look. Multiply that across a busy surgical schedule, where patients cycle through 90-day windows constantly, and separately payable revenue leaks out steadily. AAPC and MGMA both flag global-period modifier errors as a common and recoverable source of surgical denials, precisely because so many of them are winnable visits that were simply never flagged as in-window. The visit was payable. The window was invisible.

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:

The Solution

So what does “someone whose whole job it is” look like on a post-op CO-97? The specialist starts where the practice usually cannot: they track the global period on every surgical patient, so any visit inside a 0, 10, or 90-day window is flagged before it bills. Then they make the modifier call the visit needs, 24 for an unrelated E/M with a distinct diagnosis, 79 for an unrelated procedure in the postoperative period, 78 for a related return to the operating room, and apply it with the supporting documentation. Most post-op bundling loss is a visibility-and-modifier problem, and that is exactly what dedicated denials and appeals management is built to solve before a payable visit ever gets written off.

When a genuinely separate service is bundled anyway, the specialist appeals it rather than eating it. The appeal packet pairs the operative note that defines the original global period with the visit documentation that shows the new service was unrelated or a distinct procedure, so the payer has to unbundle what it wrongly included. Every post-op denial is sorted into the ones that need a corrected modifier and the ones that need an appeal, so separately payable revenue stops disappearing into the surgical package.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow flags the global window, proposes the modifier, and assembles the appeal packet; a person confirms the service is genuinely separate and owns the modifier choice and the appeal. Every security control that protects the chart data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving operative and visit documentation through a coding and appeals workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team handle your global-period modifiers better than your own coders? Because tracking windows and making the 24-79-78 call all day is their entire job, not the thing they squeeze between other charges. The people working your denials are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US surgical coding, global-period rules, and denial management workflows. They know which visits fall inside which window, which modifier a separately payable service needs, and how to read an operative note to prove a service was unrelated. That is not a generalist task handed to whoever is free; 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 separately payable visit never bundles because the one coder who tracks global windows 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.

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented global-period workflow: every surgical patient’s window tracked on the schedule, the rule for when a visit is separately payable, the modifier choice among 24, 79, and 78 spelled out for each situation, and the appeal path for misapplied bundling denials written down and worked the same way every time. Before we take a single claim for a new practice, we chart your post-op CO-97 volume by procedure and window so we can see where payable visits are being lost, and we build the workflow against that, not against a generic template.

From there the workflow becomes a living playbook rather than tribal knowledge in one coder’s head. It records which procedures carry which global periods, how to flag a visit that falls inside a window, when each of the three modifiers applies, and the exact documentation that wins an unbundling appeal. It is written down, kept current, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so a separately payable visit never bundles because one person was away that day.

That is the difference between reworking this month’s post-op denials and fixing the process for good, and it is what a dedicated revenue cycle management partner actually buys you. A coder leaving used to mean the team went blind to global windows again and payable visits started bundling. Under this model the workflow keeps running, the playbook stays, the backup steps in, and a post-op CO-97 stops being the denial nobody saw coming.

The Whole Thing in Four Sentences

Post-op office visits deny CO-97 because the global surgical package bundles related follow-up care for 0, 10, or 90 days, and a separately payable visit that falls inside that window without the right modifier gets treated as included. The fix is the correct modifier, 24 for an unrelated E/M visit with a distinct diagnosis, 79 for an unrelated procedure in the postoperative period, and 78 for a related return to the operating room, but the modifier only gets applied if someone can see the window first. Billing blind to the window, writing off post-op denials as correctly bundled, or guessing the modifier all fail the same way. The fix is to track every global period so visits get flagged, apply the right modifier, and appeal misapplied denials with the documentation. An orthopedic surgery practice 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 post-op visits to bundling? Try us risk free: two weeks, your real post-op denial queue, dedicated specialists tracking every window and applying the right modifier, 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.

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