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

Why Did Medicare Start Denying CO-109 on a Patient Who Recently Elected Hospice?

The patient has been yours for months. The visits look exactly like the ones you billed all year, the coding is right, and then out of nowhere Medicare denies CO-109: this claim is not covered by this payer or contractor.

Trusted 800+ Providers MGMA 2026 Corporate Member HIPAA-Compliant SOC 2 Type II BAA Signed $5M E&O and Cyber
BEST Hospice Billing Outsourcing PartnerRecognized by our customers as a leading healthcare outsourcing partner, based on Google reviews and direct client feedback.
All Pain Points
SOLUTIONThe fix is to read hospice election status on every eligibility response, decide whether each service is terminal-related, apply the correct hospice rules and modifiers, and route each claim to the right entity before submission.
Written for Front Office Managers, Billing Directors, and Practice Administrators evaluating eligibility and benefits verification support.

Medicare started denying CO-109 on your recently-hospice patient because electing the Medicare hospice benefit changes who pays for care related to the terminal condition: the hospice becomes responsible for that care under its per diem, and Part B claims for terminal-related services sent to the regular Medicare contractor come back not covered by this payer or contractor. It is not that the visit was wrong; it is that the payer behind the terminal condition changed the moment hospice was elected, and your eligibility workflow never surfaced it. The fix has four moves: check hospice election status on every Medicare eligibility response, decide whether each service is related to the terminal condition, apply the correct hospice billing rules and modifiers before submission, and route or bill each claim to the right entity instead of reworking CO-109 after the fact. We run those moves inside the systems you already use, so a hospice election stops turning your supportive-care claims into denials. The table of contents maps the whole method; the moves after it are the detail.

How to Bill a Hospice Patient's Part B Claims Without a CO-109

The goal is simple: catch the hospice election before you bill, decide what is terminal-related, and send each claim to the right payer the first time. Here is what does that, move by move.

1. Check Hospice Election Status on Every Eligibility Response

The denial starts with a hospice election your workflow never saw, so surfacing it is the first move. A Medicare eligibility response can show that a patient has elected hospice and the effective date, and that single field changes how everything for that patient bills. Make reading hospice status a standing part of eligibility, not an afterthought, so the election is caught before the claim drops. You cannot bill a hospice patient correctly if you do not know they are on hospice.

2. Decide Whether Each Service Is Related to the Terminal Condition

Hospice does not swallow every claim; it changes who pays for care related to the terminal illness. So the next move is a clinical read: is this visit for the terminal condition, or is it clearly unrelated. That distinction drives everything downstream, because related and unrelated services bill differently once hospice is elected. Getting this call right, service by service, is what separates a clean claim from a CO-109, and it is a judgment that belongs with someone who understands the chart.

3. Apply the Correct Hospice Billing Rules and Modifiers

Medicare has specific rules for physician services furnished to hospice patients, including modifiers that signal whether a service is related to or unrelated to the terminal condition. An attending service related to the terminal illness is handled one way; a service unrelated to it is billed another, and Medicare's processing system expects the right modifier to be present. Submitting a terminal-related Part B service to the regular contractor without accounting for hospice is exactly what produces the CO-109. Apply the rules before submission, not after the denial.

4. Route Each Claim to the Right Entity Before Submission

With the terminal-versus-unrelated call made and the correct modifier applied, each claim goes where it actually belongs: terminal-related care handled per the hospice rules, unrelated care billed to Medicare with the appropriate modifier. The point is to bill it right the first time rather than send everything to the usual contractor and rework the CO-109s. Tracking hospice-elected patients in one place, with their election dates and terminal diagnosis, is what keeps the next supportive-care visit from bouncing the same way.

5. Hand Hospice Coordination Billing to a Dedicated Team

Practices that stop losing hospice-patient claims to CO-109 do it by handing this to a dedicated team: remote specialists who catch the hospice election on eligibility, make the terminal-related call with clinical judgment, apply the right modifiers, and bill each claim to the correct entity, live in 1 to 2 weeks. The physicians go back to caring for patients in a fragile stretch instead of untangling denials, a trained backup covers every gap, and hospice billing stops being the thing nobody owns. Below is what it sounds like when nobody owns it yet, in providers' own words.

Key Pain Points and Discussions by Providers

representative composite examples based on common workflow discussions

“A patient I had treated for a long time elected hospice, and I did not find out until Medicare denied CO-109 on the next visit. The care was the same as always, but the payer behind the terminal condition had changed and nothing in our system flagged it.” composite example: physician, oncology practice

“Our eligibility check shows all kinds of things, but nobody was reading the line about hospice election. So we kept billing the contractor we always bill, the claims kept coming back CO-109, and every one of them was a patient in a really hard moment.” composite example: billing lead, specialty practice

“The hard part is deciding what is related to the terminal condition and what is not. That is a clinical call, and my front-office biller cannot make it. When we get it wrong, the claim denies, and when we do not even try, everything denies.” composite example: practice administrator, oncology group

“Nobody in our office knew the modifier rules for services on a hospice patient. We just billed normally, and Medicare treated the terminal-related visits as already covered by the hospice per diem, so they came back denied.” composite example: coder, specialty practice

“Once a patient is on hospice, I have learned every one of their claims needs a second look before it goes out. But we do not have the bandwidth to give every hospice patient that attention, so the CO-109s pile up on exactly the patients who need us focused on care.” composite example: office manager, oncology practice

Our Answer

Here is what we actually do. A dedicated remote specialist reads hospice election status off every Medicare eligibility response, so a recently-elected patient is caught before the claim drops. For each service, they make the terminal-related call with clinical judgment, apply the correct hospice billing rules and modifiers, and route each claim to the right entity: terminal-related care handled per the hospice rules, unrelated care billed to Medicare with the appropriate modifier. For claims that already denied CO-109, they rework each with the right status and modifier so it lands the first time on resubmission. Our teams include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, working inside your EMR, eligibility, and billing tools, with approved AI tools assisting with first-pass and a human verifying every terminal-related determination. This is our denial management support paired with an AI-first workflow, in one paragraph.

Why This Keeps Happening

If the visit looked like every other one you billed, why does it suddenly deny CO-109? Because the patient elected the Medicare hospice benefit, and that election changes who is responsible for care related to the terminal condition. Once hospice is elected, the hospice is paid a per diem that covers care for the terminal illness, so a Part B claim for terminal-related services sent to the regular Medicare contractor comes back as not covered by this payer or contractor. The care did not change; the payer behind the terminal condition did, on the effective date of the election.

The reason it blindsides a practice is that the election is invisible unless someone reads for it. Hospice status can appear on a Medicare eligibility response, but if the workflow does not check that field, the claim keeps routing to the contractor you always bill. Surfacing the election at the point of eligibility is exactly the front-office catch an insurance eligibility verification workflow is built to make, and without it the first sign of a hospice election is often a CO-109 on a patient in a fragile stretch of care.

And the second half of the problem is the clinical judgment underneath it. Hospice election does not turn every claim into a denial; it changes billing only for care related to the terminal condition, while unrelated care can still be billed to Medicare with the right modifier. Making that terminal-versus-unrelated call, service by service, and applying the correct hospice modifier is not a front-office data-entry task; it needs someone who can read the chart. When a practice cannot give every hospice patient that attention, the CO-109s land on precisely the patients whose care should have the team's full focus, and the denials become a distraction from the moment that matters most.

⚠️ The quiet one that hurts most: The quiet one that hurts most: the hospice election nobody saw. A patient can elect hospice between visits, and unless someone reads the election status on the eligibility response, the practice keeps billing the same contractor and keeps getting CO-109, claim after claim, on a patient in their final stretch of care. It reads on paper like an ordinary denial to rework, but it is really a signal that the coverage moved and the workflow missed it. Every terminal-related claim after that election will deny the same way until someone catches the status and starts making the terminal-related call. The most painful CO-109s here are the ones stacking up on the patients who most deserve the team's attention on care, not on paperwork.

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
Kept billing the usual Medicare contractor Every terminal-related claim after the hospice election denied CO-109, because the payer behind it had changed The workflow that never read hospice status
Assumed the front-office biller could sort it out The terminal-versus-unrelated call is clinical, so it got guessed or skipped and the claims denied A biller without the chart context to decide
Billed hospice-patient visits with no modifiers Medicare treated terminal-related services as covered by the hospice per diem and denied them Nobody who knew the modifier rules
Gave hospice billing to a dedicated remote specialist Election caught on eligibility, terminal-related call made, right modifier applied, each claim routed to the correct entity Someone whose whole job it is

The Solution

So what does "someone whose whole job it is" look like on a hospice-elected patient? The specialist reads the hospice election status off the eligibility response before anything bills, catching the election your workflow used to miss entirely. Then, service by service, they make the terminal-related call with clinical judgment, because that distinction decides how the claim bills once hospice is in the picture. Surfacing the election at the point of eligibility is exactly what dedicated insurance eligibility verification is built to do, before a supportive-care visit ever routes to a contractor that no longer holds responsibility for terminal-related care.

Then comes the part a front-office biller cannot do alone: applying the correct hospice billing rules and modifiers and sending each claim where it belongs. Terminal-related care is handled per the hospice rules; unrelated care is billed to Medicare with the appropriate modifier so it is not mistaken for something the per diem already covers. For the CO-109s already on the aging report, the specialist reworks each with the right status and modifier so it lands cleanly on resubmission. The hospice patients who used to generate a stream of denials get billed correctly, the same way every time.

Behind all of it, Approved AI tools may assist with the first pass and a trained human reviewer verifies. The workflow flags the hospice election, drafts the modifier and routing, and queues the claim; a person with clinical context confirms the terminal-related determination and owns the submission. Every security control that protects the chart and coverage data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving clinical documentation through a billing workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team bill your hospice patients better than your own staff? Because the terminal-related determination and the hospice modifier rules take clinical understanding, not just data entry, and reading charts is what our people do all day. The specialists working your hospice claims include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, all trained in US billing and hospice coordination workflows. They know how a hospice election changes responsibility for terminal-related care, how to read election status off an eligibility response, and how to apply the right modifier so a Part B claim for a hospice patient does not bounce CO-109. That is not a task for whoever is free at the front desk; it needs someone who can read the chart.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ team members, 24/7 coverage, and the AI-assisted plus human-verified workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at approximately 68% below equivalent in-house staffing costs. Trained backup coverage is included in the managed-service model.

And the security piece your compliance officer will ask about: Staffingly maintains active ISO/IEC 27001:2022 certification and operates under HIPAA-compliant controls and signed BAAs. SOC 2 Type II reporting and security controls apply according to the relevant entity, client environment, facility, device, and workflow. Venn Blue Border and related workstation restrictions are used where applicable. Staffingly maintains $5M in professional liability (E&O) and cyber insurance as part of its enterprise risk-management program; 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 this workflow is designed to reduce: What this workflow is designed to reduce: the CO-109 denials that land on a patient right after they elect hospice. The hospice election nobody read on the eligibility response. The terminal-related call guessed by a biller without the chart. The hospice-patient visits billed with no modifiers and treated as covered by the per diem. The stream of denials piling up on exactly the patients whose care should have the team's full attention.
Two-Week Free Trial

Ready to Stop Losing Hospice-Patient Claims to CO-109?

Evaluating the best insurance eligibility verification services? See how a dedicated remote team compares, then browse every pain point we solve.

How We Build a More Durable Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented hospice-coordination workflow: how to read hospice election status on eligibility, how to make the terminal-related call service by service, which modifiers apply to related and unrelated care, and where each claim gets routed. Before we take a single claim for a new practice, we chart your hospice-patient denials so we can see exactly where the CO-109s are coming from, and we build the workflow against that, not against a generic template.

From there the workflow becomes a living playbook rather than knowledge in one biller's head. It records how to surface a hospice election, the criteria for calling a service terminal-related, the correct modifier for each situation, and the routing for related versus unrelated care. It is written down, kept current as Medicare updates its hospice rules, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so a hospice patient's claims never wait for one person to come back.

That is the difference between reworking this month's hospice denials and fixing the process for good, and it is what a dedicated revenue cycle management partner actually buys you. A biller leaving used to mean the hospice patients started denying again. Under this model the workflow keeps running, the playbook stays, the backup steps in, and a hospice election stops being the thing that quietly turns your supportive-care claims into CO-109s.

The Whole Thing in Four Sentences

Medicare denies CO-109 on a recently-hospice patient because electing the hospice benefit moves responsibility for care related to the terminal condition to the hospice under its per diem, so Part B claims for terminal-related services sent to the regular contractor come back not covered by this payer or contractor, and the eligibility workflow never surfaced the election. Billing the usual contractor, guessing the terminal-related call, or billing with no modifiers all fail the same way. The fix is to read hospice election status on every eligibility response, decide whether each service is terminal-related, apply the correct hospice rules and modifiers, and route each claim to the right entity before submission. An oncology and specialty group can use this workflow without exposing patient information or naming client organizations.

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 hospice-patient claims to CO-109? Start with a Two-Week Free Trial: your real hospice-patient denial queue, dedicated specialists reading eligibility and billing each claim to the right entity, 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 security deposits, no long-term contracts. Two-Week Free Trial. 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 owning your hospice-status checks and Part B billing for hospice patients end to end, single-site oncology or specialty practice

Department
$299/ week

10+ remote specialists, multi-location specialty network, MSO, or PE-backed platform running hospice-status verification and Part B billing across many providers

  How Pricing Works

45 hours of coverage at one flat weekly rate.

For a simple annual comparison, 40 hrs x 52 weeks = 2,080 hours. A Staffingly plan: 45 hrs x 52 weeks = 2,340 hours a year, that is 260 additional hours included in your flat rate. $399/week x 52 = $20,748 a year / 2,340 hours = $8.87 per hour.

Trained backup VA Dedicated success manager Monthly training updates HIPAA-trained staff $5M E&O and cyber liability

Bill Your Hospice Patients Right This Month

You have seen the whole method. The trial lets you test it on your own hospice-patient claims, with a tracker your team can watch every day.

Start My Two-Week Free Trial

Want Us to Stop Losing Hospice-Patient Claims to CO-109?

Tell us your situation and we will map your hospice-status checks and the Part B billing behind them. A team member will follow up with next steps.

Frequently Asked Questions

Because electing the Medicare hospice benefit changes who pays for care related to the terminal condition. The hospice is paid a per diem that covers terminal-related care, so a Part B claim for those services sent to the regular Medicare contractor comes back CO-109: not covered by this payer or contractor. The care did not change; the payer responsible for the terminal condition changed on the effective date of the hospice election.
No. Hospice election changes billing only for care related to the terminal condition. Care that is clearly unrelated to the terminal illness can still be billed to Medicare with the appropriate modifier. That is why the terminal-versus-unrelated determination matters so much: getting it right, service by service, is what keeps the unrelated care payable and routes the terminal-related care correctly.
Hospice election status can appear on a Medicare eligibility response, along with the effective date. The problem is usually that no one is reading that field. Making hospice status a standing part of your eligibility check, rather than an afterthought, surfaces the election before you bill, so the first sign of it is not a CO-109 on the next visit.
Medicare has specific rules and modifiers that signal whether a physician service is related to or unrelated to the patient's terminal condition. An attending service related to the terminal illness is handled one way; a service unrelated to it is billed with the modifier that tells Medicare it is not covered by the hospice per diem. The exact modifier depends on the situation, and applying the right one before submission is what prevents the terminal-related services from denying as already covered.
Staffingly charges $399 per week for one dedicated team member, $349 per week each at 5 or more, and $299 per week each at 10 or more. The dedicated-team model includes 45 hours of weekly coverage where applicable to the service schedule, with trained backup coverage included. There are no setup fees, no security deposits, no long-term contracts, and no percentage of collections. Every engagement starts with a Two-Week Free Trial.
No. Approved AI tools may assist with the first pass, flagging the hospice election and drafting the modifier and routing, and a trained human reviewer with clinical context makes the terminal-related determination and owns the submission. The clinical judgment stays with people. Automation removes the repetitive flagging and assembly so the specialist spends their time on the calls that need a human, not on rechecking every eligibility response by hand.
No. Our specialists work inside the EMR, eligibility, and billing tools you already use, so there is no migration and no new platform for your staff to learn. They read hospice status, make the terminal-related call, and submit each claim where your accounts already live, which is why a typical practice is live in 1 to 2 weeks rather than months.
Usually within the first weeks. Once a dedicated specialist is reading hospice election status on eligibility and billing each claim to the right entity with the correct modifier, the terminal-related claims stop routing to the wrong contractor and the CO-109s stop generating at the source. The denials already on the aging report get reworked in parallel, so the pile shrinks from both ends.
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, compared with 2,080 hours from a simple 40-hours x 52-weeks annual calculation. That is how $399 per week works out to $8.87 per hour.
Dan Nandan, Founder and CEO of Staffingly, Inc.

Written By

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

Dan Nandan is the Founder and CEO of Staffingly, Inc., based in Piscataway, New Jersey. He has 25+ years in IT consulting and IT staffing, with the last decade focused on healthcare outsourcing. He was among the first to establish an RPO operation in India more than 20 years ago and has been featured in Computerworld. He leads Staffingly's U.S. clients and delivery teams behind the workflows described on this page.

Connect on LinkedIn
This page is general educational information for healthcare operations teams. It is not legal, medical, billing, coding, or compliance advice, and it does not create any professional or advisory relationship. Payer rules, codes, forms, and regulations change and vary by plan and region, so confirm every requirement with the applicable payer or authority before acting. Staffingly, Inc. makes no warranty as to accuracy or completeness and accepts no liability for decisions made based on this content.

Where the Claims on This Page Come From

Sources & References

  • Palmetto GBA Jurisdiction M Part B, Modifiers GV and GW: Medicare Part B Services Provided to Hospice Patients. Medicare Administrative Contractor guidance on billing physician services for hospice-elected patients and the modifiers that signal terminal-related versus unrelated care. palmettogba.com
  • Centers for Medicare and Medicaid Services, Medicare Hospice Benefit. Official CMS guidance on the hospice benefit, the per diem, and how responsibility for care related to the terminal condition shifts to the hospice on election. cms.gov
  • AMA Practice Management and Administrative Simplification Resources. Physician-practice guidance on coverage verification and reducing the administrative burden of denial rework. ama-assn.org

Key highlights of every Staffingly engagement

You pay for the resource. Everything else is included.

Your flat weekly rate covers one dedicated specialist. The management layer around them, backup coverage, quality reviews, training, escalation, reporting, and custom automation comes standard at no added cost. Here is what every Staffingly account includes.

See the 8 things every account includesHide the 8 inclusions
  • Who manages my account day to day?

    An account manager plus a customer success manager. Two named people own your account: the account manager runs daily operations and quality, the customer success manager handles onboarding and communication tools like ClickUp or Teams, so your team never chases an answer.

  • What if something needs to go higher?

    VP-level escalation, US and offshore. A direct path above your account manager to Vice President level leadership on both sides, US-based and at our offshore delivery centers. You are never stuck in a ticket queue waiting for someone with authority.

  • What happens when my specialist is out or leaves?

    Backup coverage and same-week replacement. A cross-trained backup covers absences so your work never sits idle. If a specialist leaves or underperforms, we replace them the same week, trained on your workflows before the handoff.

  • How are holidays and leave handled?

    Planned in advance. Specialists receive approved US holidays and two weeks of paid leave per year. Coverage for those dates is arranged with you ahead of time, so continuity is planned, not improvised.

  • How do I know the work is getting done?

    Daily quality stand-up plus daily and weekly reports. Every account starts the day with a stand-up: what came in, what went out, what is stuck, and who is fixing it. You get a daily activity report and a weekly performance report, so nothing slips for a month before you hear about it.

  • How are specialists trained before they touch my account?

    AI-enabled, HIPAA-controlled training. Specialists train in simulations of your EMR and workflows inside our secured environment, with quizzes requiring an 80 percent passing score and AI-moderated final assessments. See how our training works.

  • Do I pay extra for automation?

    No. Custom AI and automation workflows are free. We build automation around your account at no charge: document intake, EMR data entry assistance, and status tracking, always with human review. Faster turnaround and fewer errors reaching the payer, without an extra software bill.

  • Will my rate change, and how do I add people?

    12-month price lock, easy scaling. Your rate is fixed for twelve months from your start date. Need more agents later? An email from your authorized representative is enough. Once confirmed in writing, new agents fall under your existing agreement. No new contract, no work order.

Dedicated specialists, never shared, working inside your EMR and payer portals under a signed BAA. One flat weekly price per operator covers all of the above.Book a Strategy Call