Veteran playbook for EDUCATING referral sources on hospice eligibility — the Medicare Hospice Benefit structure, the non-disease-specific decline guidelines, the diagnosis-specific LCD criteria, and the PPS/FAST/NYHA scales. Teaches recognition, never certification. Consulted by hospice-eligibility-educator. Every output ends with 'the attending physician and medical director certify eligibility.'
How this skill is triggered — by the user, by Claude, or both
Slash command
/hospice-referral-sales:hospice-eligibility-criteriaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** help `hospice-eligibility-educator` teach a referral source to _recognize_ a potentially hospice-eligible patient. This skill is **education**, not a certification or determination tool.
Purpose: help hospice-eligibility-educator teach a referral source to recognize a potentially hospice-eligible patient. This skill is education, not a certification or determination tool.
The representative educates; the physician certifies. Hospice eligibility — a prognosis of six months or less if the disease runs its normal course — is certified by the attending physician and the hospice medical director on clinical judgment. Nothing in this skill, and nothing the agent produces from it, tells anyone that a specific patient "qualifies," "is eligible," or "is covered." Every deliverable ends with the physician-certifies line. (../CLAUDE.md §3 #1, §5.)
[example — verify].)The most useful teaching tool, because it catches the multi-morbidity and failure-to-thrive patients that single-diagnosis LCDs miss. The decline picture:
Teach the clinician to see the trajectory, not a single number.
| Scale | Measures | Hospice-relevant signal |
|---|---|---|
| PPS (Palliative Performance Scale) | Functional status 0–100% | Lower PPS (often ≤ 40–50%) supports a decline picture — [example — confirm against the LCD] |
| FAST (Functional Assessment Staging) | Dementia progression | FAST stage 7 (plus a recent complication) is the dementia LCD anchor |
| NYHA (New York Heart Association) | Heart-failure functional class | Class IV (symptoms at rest), optimally treated, anchors the cardiac LCD |
The detailed per-diagnosis decline indicators live in resources/lcd-quick-reference.md and ../../knowledge/hospice-eligibility-lcd-reference.md. Covered: heart disease, pulmonary, dementia, renal, liver, stroke/coma, ALS/neuromuscular, cancer, HIV, and adult failure-to-thrive. Each is dated and sourced to the published LCD, and each is teaching content — the recognition picture, not a checklist that certifies.
| Myth | The accurate framing |
|---|---|
| "You need a DNR for hospice." | False — a DNR is not required to elect hospice. |
| "Hospice is cancer-only." | False — the majority of hospice patients have non-cancer diagnoses (cardiac, dementia, pulmonary, etc.). |
| "You have to stop all treatment." | The patient forgoes curative treatment for the terminal illness; comfort and symptom treatment continue, and unrelated conditions are still treated. |
| "Hospice is the last 48 hours." | Hospice is for a six-month-or-less prognosis — earlier election gives the full benefit. |
When reading a de-identified profile, list which decline indicators are present, what is missing to know, and recommend routing to the attending physician for the clinical conversation. The output is "these published indicators are present; this warrants a physician discussion," never "this patient is eligible." The eligibility-indicators subcommand of scripts/hospice_calc.py tallies indicators with the same discipline.
goals-of-care-conversations skill / goals-of-care-conversation-coach.referral-territory-development skill / referral-development-strategist.ravenclaude-core deep-researcher.npx claudepluginhub mcorbett51090/ravenclaude --plugin hospice-referral-salesGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.