How Should a Practice Bill Part B When a Patient Has an Active Hospice Election It Did Not Know About?
You saw the patient, you documented the visit, and the service had nothing to do with why they are on hospice.
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
representative composite examples based on common workflow discussions
“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.” composite example: 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.” composite example: 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.” composite example: 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.” composite example: 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.” composite example: 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 teams include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, working inside your practice management system and the Medicare eligibility portals you already use, with approved AI tools assisting with 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.
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, Approved AI tools may assist with the first pass and a trained human reviewer 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 include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, 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+ 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.
Ready to Stop Losing Claims to Hidden Hospice Elections?
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 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 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 claims to hidden hospice elections? Start with a Two-Week Free Trial: 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.
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.
One dedicated remote specialist owning Medicare eligibility checks and hospice-overlap denials end to end, single-site specialty or primary care practice
5+ remote specialists covering eligibility verification and B9 rework across a multi-provider group and several sites
10+ remote specialists, multi-location group, MSO, or PE-backed platform running Medicare eligibility and hospice-overlap denial work across many providers
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.
Clear Your Hospice-Overlap Denials This Month
You have seen the whole method. The trial lets you test it on your own Medicare denial queue, with a tracker your team can watch every day.
Start My Two-Week Free TrialWant Us to Stop Losing Claims to Hidden Hospice Elections?
Tell us your situation and we will map your Medicare denial reasons and the eligibility workflow behind them. A team member will follow up with next steps.
Frequently Asked Questions
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
- 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