skills/legal/incident-to-billing-policy/SKILL.md
Drafts Medicare incident-to billing compliance policies for healthcare practices. Covers eligibility criteria, direct supervision, documentation standards, audit programs, and FCA risk mitigation under 42 CFR 410.26, Medicare Benefit Policy Manual Ch. 15 §60.1, and 42 U.S.C. §1395x(s)(2)(A). Use when creating or updating incident-to policies, responding to OIG scrutiny, or establishing NPP billing compliance programs.
npx skillsauth add casemark/skills incident-to-billing-policyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Drafts a compliance policy governing Medicare incident-to billing — NPP services billed under the supervising physician's NPI at the physician rate. Improper use creates False Claims Act liability, civil monetary penalties, and program exclusion risk.
Gather before drafting:
Core question for every encounter: Does this visit meet all nine eligibility criteria? If any criterion fails, bill under the NPP's own NPI.
Include: effective date, annual review cycle, scope (all clinical/billing staff), and governing authority (42 CFR 410.26; Medicare Benefit Policy Manual Ch. 15 §60.1; 42 U.S.C. §1395x(s)(2)(A)). State that incident-to is a conditional billing privilege with FCA consequences for misuse.
| Term | Definition | |---|---| | Incident-To Billing | Billing NPP services under supervising physician's NPI at physician rate | | Direct Supervision | Physician physically present in office suite and immediately available — phone/telehealth does NOT qualify | | NPP | Non-physician practitioner (NP, PA, CNS, CNM) per Medicare definition | | Initial Service | First physician evaluation establishing diagnosis and treatment plan |
Must bill under NPP's NPI instead when:
Scheduling — Flag appointments for billing path; confirm physician is on-site that date. Decision flow: treatment plan exists? → physician on-site? → follow-up (not new problem)?
Day-of supervision — Physician signs daily attestation log (name, date, location, hours). Retain with billing records.
Encounter documentation (each incident-to note must include):
Billing controls — Verify supervision log before submitting under physician NPI. EHR/PM system flags: physician not scheduled, new diagnosis code, NPP not credentialed.
Retain all records (physician notes, NPP notes, supervision logs, schedules, billing data) for 10 years from service or final payment, whichever is later. Training records: employment duration + 6 years. All records retrievable within 48 hours of audit request.
Governing authorities:
Audit program:
Error correction:
Physicians and NPPs: trained before incident-to participation, annual refresher. Clinical and billing staff: within 30 days of hire, annual refresher. Cover eligibility criteria, supervision definition, documentation requirements, non-compliance consequences.
Governance roles: Compliance Officer (policy owner, audit, disclosures), Medical Director (supervision standards), Billing Director (claims controls), Practice Administrator (training, retention). Review policy annually; update within 30 days of regulatory change.
Include in final document:
[VERIFY] if regulatory currency is uncertain.Key changes from original:
tags from frontmatter — not part of the Agent Skills specdevelopment
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
tools
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
development
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
testing
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.