Veteran playbook for hospice referral-marketing compliance — the Anti-Kickback Statute and its hospice-relevant safe harbors, Stark, the beneficiary-inducement CMP, the gift/meal nominal-value discipline, OIG hospice risk areas, truthful-marketing rules, and HIPAA for a liaison. Consulted by hospice-sales-compliance-advisor. Frames the question and names the rule and safe harbor; routes the RULING to the compliance officer / counsel.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hospice-referral-sales:hospice-sales-complianceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** help `hospice-sales-compliance-advisor` frame the compliance question correctly — name the rule, flag the risk, give the safe-harbor structure — and route the **ruling** to the agency compliance officer and counsel.
Purpose: help hospice-sales-compliance-advisor frame the compliance question correctly — name the rule, flag the risk, give the safe-harbor structure — and route the ruling to the agency compliance officer and counsel.
Frame the question; never issue the ruling. The correct output is "here is the rule, here is the line, here is the safe-harbor structure, here is the question to put to your compliance officer" — not "yes, that's fine." Hospice is high-enforcement (OIG work plans, False Claims Act settlements); when in doubt, stop and ask the compliance officer. Every threshold here is [example — confirm against the current rule / your compliance officer]. (../CLAUDE.md §3 #2, §5, §10.)
The federal criminal prohibition on knowingly offering/paying/soliciting/receiving remuneration to induce referrals of items or services payable by a federal healthcare program. Intent-based and broad — "remuneration" includes anything of value. Hospice referral-source relationships are squarely in scope. Safe harbors protect specific structures only if every element is met — see resources/aks-safe-harbors.md. The relevant ones for a liaison's world:
A strict-liability civil law: a physician may not refer designated health services to an entity with which the physician (or an immediate family member) has a financial relationship, unless an exception is met. Where a referral source is a physician, Stark applies in addition to AKS — and Stark has no intent requirement, so a technical violation is still a violation. Route physician arrangements to counsel.
Prohibits offering remuneration to a Medicare/Medicaid beneficiary that is likely to influence their choice of provider. Gifts to patients/families must fit the nominal-value exception (small per-item and annual caps — [example — confirm the current CMS figures]) and never be cash or cash-equivalents.
"Small and infrequent" is a documented structure, not a feeling:
[example — confirm].No eligibility or coverage guarantee, no misleading or unsubstantiated claim, no competitor disparagement with unverified facts, no pressure on a vulnerable family. Read every piece for those four failures.
The published enforcement themes that make referral-source arrangements high-scrutiny: ineligible patients / inappropriately long lengths of stay, improper financial relationships with nursing facilities and physicians, and GIP (general inpatient) misuse. These are why the default posture is caution.
A liaison handles real patient data. Minimum-necessary, a HIPAA-safe boundary, and nothing patient-identifying in a CRM note shared out, an email, an example, or a scenario. Route any PHI question beyond minimum-necessary framing to the privacy officer.
For any ask: name the rule → locate the line → give the safe-harbor structure (if any) → state the specific question to put to the compliance officer → never green-light. Run the ## Decision Tree: Gift / meal / arrangement anti-kickback gate in the knowledge bank; it ends at "route to compliance officer."
ravenclaude-core deep-researcher.ravenclaude-core security-reviewer + the privacy officer.hospice-eligibility-criteria skill / hospice-eligibility-educator.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.