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

How Should a Practice Bill Part B When a Patient Has an Active Hospice Election It Did Not Know About?

All Pain Points

Ask AI about this page

A practice bills Part B around an unknown hospice election by proving relatedness, not by writing off the claim. When a patient elects the Medicare hospice benefit, the hospice files a Notice of Election that updates Medicare’s eligibility file, and any unrelated provider that did not know finds out when the claim denies B9 for hospice overlap. The fix has four moves: read the hospice occurrence data in the eligibility response before you ever bill a Medicare patient, on any B9 denial confirm with the hospice agency whether your service was related to the terminal diagnosis, rebill unrelated services with the GW modifier and attending-physician services with GV, and route the truly related ones to the hospice instead of appealing a claim that will never pay. We run those moves inside the systems you already use, so an unrelated service you documented actually gets reimbursed instead of aging out. The table of contents maps the whole method; the moves after it are the detail.

What Actually Clears a Hospice-Overlap B9 Denial
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 Clears a Hospice-Overlap B9 Denial

The goal is a documented, unrelated Part B service paid the first time you rebill it, without a coder losing an afternoon to a denial nobody saw coming. Here is what does that, move by move.

1. Read the Hospice Occurrence Data on Every Medicare Eligibility Check

The election is not hidden; it is in the eligibility response if someone looks. Before you bill any Medicare patient, check the hospice occurrence data returned in the eligibility file: the election date, the hospice provider, and the active period. When that flag is there, you know before you submit that any claim may hit a B9 edit, and you can decide up front whether your service is related or unrelated. You cannot bill correctly around an election you never checked for, and the check takes seconds when it is built into the workflow.

2. Confirm Relatedness With the Hospice Agency, Not With a Guess

B9 is not a verdict that your service was wrong; it is a flag that the patient is under an active election. The real question is whether what you did was related to the terminal diagnosis. Contact the hospice agency, confirm the terminal condition and the plan of care, and get relatedness settled on the record. An unrelated service is yours to rebill and collect. A related service belongs to the hospice’s per-diem, and appealing it to Medicare only ages the claim. Settle which one it is before you touch the rebill.

3. Rebill Unrelated Services With GW, Attending Services With GV

Once relatedness is confirmed, the modifier does the work. Services unrelated to the terminal condition get the GW modifier, which tells Medicare the care sits outside the hospice benefit and should pay under Part B. Services furnished by the designated attending physician get the GV modifier when that physician is not employed by the hospice. Medicare’s contractors have denied unrelated claims submitted without GW since 2019, so the modifier is not optional; it is the difference between a paid claim and a repeat denial.

4. Route Related Services to the Hospice and Stop Appealing Them

Not every B9 denial is yours to overturn, and chasing the ones that are not is how the queue clogs. When the service truly was related to the terminal diagnosis, it is covered under the hospice’s per-diem payment, and the right move is to bill or coordinate with the hospice, not to appeal Medicare. Sorting related from unrelated at the front keeps your appeals focused on the claims that will actually pay and stops the write-offs that should have been hospice’s to reimburse.

5. Hand Medicare Eligibility and B9 Rework to a Dedicated Team

Practices that stop getting blindsided by hospice elections do it by handing Medicare eligibility and hospice-overlap denials to a dedicated team: remote specialists who read the occurrence data up front, confirm relatedness, rebill with the right modifier, and route the rest, live in 1 to 2 weeks. The billing team goes back to the rest of the queue, a trained backup covers every gap, and the B9 pile stops being the denial nobody catches until it is three weeks old. Below is what it sounds like when nobody owns this yet, in providers’ own words.

Key Pain Points and Discussions by Providers

real reports from practice staff, lightly edited

“The lesion removal denied B9 and I had no idea the patient was even on hospice. The condition had nothing to do with their terminal diagnosis, but I lost three weeks figuring that out and rebilling with GW before it finally paid.” – billing lead, dermatology practice

“Nobody tells us when a patient elects hospice. The Notice of Election goes to Medicare, the eligibility file flips, and the first we hear of it is a denial code on a claim we already worked.” – practice administrator, multi-specialty group

“I used to just write B9 denials off, assuming Medicare would never pay them. Then I learned half of them were unrelated services I could have collected on with the right modifier. That was real money we were leaving on the table.” – coder, primary care practice

“The hard part is proving relatedness. Was the visit related to the terminal condition or not? You have to actually call the hospice agency and confirm, and until you do, you cannot tell whether to rebill it or hand it to them.” – billing manager, specialty practice

“We started checking the hospice occurrence data on every Medicare eligibility response instead of finding out at the denial. Catching the election before we bill changed the whole thing from a rework problem to a front-end one.” – office manager, family medicine group

Our Answer

Here is what we actually do. A dedicated remote specialist reads the hospice occurrence data in the eligibility response before your Medicare claim ever goes out, so an active election is caught up front instead of at the denial. On any B9 that lands, they confirm relatedness with the hospice agency, then rebill unrelated services with the GW modifier and attending-physician services with GV so the claim pays under Part B, and route the genuinely related ones to the hospice instead of appealing them into the ground. Our specialists are credentialed professionals, overseas-trained physicians and US-licensed nurses and pharmacists, working inside your practice management system and the Medicare eligibility portals you already use, with AI drafting the first pass and a human verifying every rebill. This is our insurance eligibility verification paired with an AI-first workflow, in one paragraph.

Why This Keeps Happening

If the service was unrelated and documented, why does it deny in the first place? Because the hospice election updates Medicare’s eligibility file the moment the hospice files its Notice of Election, and unrelated providers are not on that notice. Medicare’s contractors, including Noridian and Palmetto, describe B9 as a hospice-overlap edit: when a patient has an active election on the date of service, the claim is flagged, and unrelated services submitted without the GW modifier are denied. The denial is a coordination gap, not a clinical judgment about your care. The election was real and silent, and your claim was the first thing to run into it.

The second half of the problem is timing. Your office does not learn about the election until the claim comes back, which by then is often weeks after the visit. That is weeks of a claim sitting, then a rework cycle to determine relatedness, contact the hospice, add the modifier, and resubmit. Medicare has required the GW modifier on unrelated hospice-overlap claims since January 2019, so a claim billed without it does not just wait; it denies outright and starts the clock over. Catching the election on the front end, in the eligibility response, is exactly what an eligibility verification workflow is built to do before the claim ever goes out.

And the cost is quiet but real. A B9 denial that gets written off as uncollectable is often an unrelated service that would have paid with the right modifier, so the write-off is lost revenue on care you actually delivered. The reverse mistake costs too: appealing a genuinely related service that belongs to the hospice’s per-diem only ages a claim that will never pay. Getting relatedness right, then rebilling or rerouting accordingly, is the difference between collecting on the unrelated care and burying it in a write-off pile nobody revisits.

⚠️ The quiet one that hurts most: The quiet one that hurts most: the B9 you write off without checking relatedness. A denial on an unrelated service looks identical to a denial on a related one, and the easy move is to assume Medicare will never pay and clear it off the aging report. But unrelated services are collectable with the GW modifier, and every one written off blind is revenue on care you already delivered. Unless someone confirms relatedness with the hospice before deciding, the most expensive B9 denials are the ones that quietly become write-offs when they should have been paid claims.

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
Wrote off every B9 denial as uncollectable	Buried real revenue; many were unrelated services that would have paid with a modifier	Whoever cleared the aging report
Resubmitted the same claim without a modifier	Denied B9 again, because Medicare requires GW on unrelated hospice-overlap claims	The billing queue, on repeat
Appealed the denial straight to Medicare	Wasted the appeal on related services that belong to the hospice’s per-diem	Whoever had a free minute
Gave Medicare eligibility and B9 rework to a dedicated specialist	Election caught in the eligibility file up front, relatedness confirmed, unrelated services rebilled with GW and paid	Someone whose whole job it is

The Solution

So what does “someone whose whole job it is” look like on a B9 denial? The specialist starts where most practices cannot: on the front end, reading the hospice occurrence data in the eligibility response before the Medicare claim goes out, so an active election is a known fact rather than a surprise. When a B9 does land, they do not guess at relatedness; they contact the hospice agency, confirm the terminal diagnosis and plan of care, and settle whether the service sits inside or outside the hospice benefit. That front-end catch and relatedness call is exactly what dedicated insurance eligibility verification is built to do before a denial ever becomes a write-off.

Then the rebill goes out correctly the first time. Unrelated services get the GW modifier so they pay under Part B, attending-physician services get GV where it applies, and the genuinely related services get routed to the hospice instead of appealed into an aging report. The specialist owns that sort every time, so your billing team stops toggling between write-off and appeal and stops losing three weeks per claim to a denial they never saw coming. The unrelated care you delivered gets collected, and the related care goes to the party that actually owes it.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow reads the eligibility file, flags the election, and drafts the modifier-corrected rebill; a person confirms relatedness with the hospice and owns the resubmission. Every security control that protects the eligibility and claim data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving Medicare eligibility and clinical data through a denial workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team handle your hospice-overlap denials better than your own staff? Because reading eligibility occurrence data, confirming relatedness with a hospice agency, and applying the right modifier is their whole day, not the thing they squeeze between the rest of the aging report. The people working your denials are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US Medicare billing and eligibility workflows. They know what B9 actually means, when GW applies versus GV, and how to settle relatedness on the record so the rebill pays the first time. 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 B9 denial never sits three weeks because the one person who handles it 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 B9 denial nobody saw coming until the claim was three weeks old. The unrelated service written off as uncollectable when it would have paid with a modifier. The appeal wasted on a related service that belonged to the hospice. The claim resubmitted without GW that just denies again. The Medicare eligibility check that skips the hospice occurrence data and finds out about the election the hard way.

2-Week Free Trial

Ready to Stop Losing Claims to Hidden Hospice Elections?

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 eligibility-and-denial workflow: check the hospice occurrence data on every Medicare eligibility response, a written rule for confirming relatedness with the hospice, the exact modifier logic for GW versus GV, and a routing path for the related services that belong to the hospice. Before we take a single claim for a new practice, we chart where your Medicare denials are actually coming from, so we can see whether hospice overlap is a recurring leak and build the front-end check against it, not against a generic template.

From there the workflow becomes a living playbook rather than tribal knowledge in one coder’s head. It records how to read the eligibility file for an active election, who to call at which hospice agency to settle relatedness, when GW applies and when GV does, and the escalation path when a service is truly related and belongs to the hospice’s per-diem. It is written down, kept current as Medicare guidance changes, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so a B9 denial never waits for one person to come back.

That is the difference between reworking this month’s B9 pile and fixing the process for good, and it is what a dedicated eligibility verification partner actually buys you. A coder leaving used to mean hospice denials piled up unnoticed and got written off blind. Under this model the front-end check keeps running, the playbook stays, the backup steps in, and a hidden hospice election stops being the thing that quietly costs you paid claims.

The Whole Thing in Four Sentences

A practice bills Part B around an unknown hospice election by catching it up front and proving relatedness, not by writing the claim off. The hospice files a Notice of Election that flips Medicare’s eligibility file, and unrelated providers only find out at the B9 denial. Writing every B9 off, resubmitting without a modifier, or appealing a related service to Medicare all fail the same way. The fix is to read the hospice occurrence data on every Medicare eligibility check, confirm relatedness with the hospice, rebill unrelated services with GW and attending services with GV, and route the related ones to the hospice. A multi-specialty 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 claims to hidden hospice elections? Try us risk free: two weeks, your real Medicare denial queue, dedicated specialists reading the eligibility file and reworking the B9 denials, 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 owning Medicare eligibility checks and hospice-overlap denials end to end, single-site specialty or primary care practice

Clear Your Hospice-Overlap Denials This Month

You have seen the whole method. The pilot proves it on your own Medicare denial 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 Medicare Part B claim deny B9 for a patient I did not know was on hospice?

Because the patient elected the Medicare hospice benefit and the hospice filed a Notice of Election that updated Medicare’s eligibility file. B9 is a hospice-overlap edit: when an active election exists on the date of service, the claim is flagged. Unrelated providers are not on that notice, so the first they hear of the election is the denial. The service is often perfectly appropriate; it just collided with a coverage change your office never saw.

How do I get paid for a service that was unrelated to the terminal diagnosis?

Confirm relatedness with the hospice agency, then rebill the unrelated service with the GW modifier, which tells Medicare the care sits outside the hospice benefit and should pay under Part B. Medicare’s contractors have required GW on unrelated hospice-overlap claims since January 2019, so a rebill without it denies again. Once the modifier is on and relatedness is settled, the unrelated service pays under Part B like any other.

What is the difference between the GW and GV modifiers?

GW indicates the service is unrelated to the patient’s terminal condition and should be paid under Part B outside the hospice benefit. GV indicates the service was furnished by the patient’s designated attending physician who is not employed by the hospice. They answer different questions: GW is about relatedness to the terminal diagnosis, GV is about who the physician is. Applying the wrong one, or neither, is a common reason these claims deny a second time.

Should I appeal every B9 denial to Medicare?

No. If the service was genuinely related to the terminal diagnosis, it is covered under the hospice’s per-diem payment, and appealing it to Medicare only ages a claim that will never pay; that one belongs to the hospice. Reserve rebilling for the unrelated services that pay with GW or GV. Sorting related from unrelated first is what keeps your appeals focused on the claims that will actually collect.

How do I catch a hospice election before the claim denies?

Read the hospice occurrence data in the Medicare eligibility response before you bill. An active election shows up there with the election date and the hospice provider, so you can decide up front whether your service is related or unrelated and bill accordingly. Building that check into every Medicare eligibility verification turns hospice overlap from a rework problem you discover at the denial into a front-end catch.

Do we have to change our practice management system or clearinghouse?

No. Our specialists work inside the practice management system, clearinghouse, and Medicare eligibility portals you already use, so there is no migration and no new platform for your staff to learn. They read your eligibility responses and denials where they already live and submit rebills through the systems you already have, which is why a typical practice is live in 1 to 2 weeks rather than months.

Will AI decide whether a service was related to the terminal diagnosis?

No. AI drafts the first pass, reading the eligibility file, flagging the election, and drafting the modifier-corrected rebill, and a credentialed human confirms relatedness with the hospice and owns every resubmission. The judgment about relatedness stays with people, because it depends on the terminal diagnosis and the plan of care. Automation removes the repetitive assembly so the specialist spends time on the calls that need a human.

How fast will we see fewer hospice-overlap write-offs?

Usually within the first two weeks. Once a dedicated specialist is reading the hospice occurrence data up front and reworking B9 denials with the right modifier, the unrelated services that used to get written off blind start getting rebilled and paid, and the related ones get routed to the hospice instead of aging in an appeal queue. The catch moves to the front end, where it costs the least.

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

Noridian Medicare, Patient Enrolled in Hospice (Reason Code B9) Guidance. Contractor guidance on hospice-overlap denials and the use of GV and GW modifiers for services unrelated to the terminal diagnosis. med.noridianmedicare.com
Novitas Solutions, Coding Guidelines: Hospice Modifiers GV and GW. Medicare contractor guidance defining when GV and GW apply to Part B services for patients with an active hospice election. novitas-solutions.com
CMS Medicare Claims Processing Manual, Hospice Services. Federal guidance on hospice election, the Notice of Election, and Part B coverage of services unrelated to the terminal condition. cms.gov
MGMA Practice Operations and Revenue Cycle Resources. Benchmarks and guidance on Medicare eligibility, denial management, and front-office verification for medical group practices. mgma.com
HFMA Revenue Cycle and Denials Management Resources. Guidance on eligibility-related denials, appeals workflow, and the revenue impact of avoidable write-offs. hfma.org