Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Conducting Stark Law Analysis

ASecurity

Evaluates physician self-referral arrangements against Stark Law exceptions with documentation. Use when analyzing Stark compliance, evaluating referral arrangements, or documenting exception applicability.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
documentationgosecuritydocumentation

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill conducting-stark-law-analysis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Conducting Stark Law Analysis?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Conducting Stark Law Analysis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-conducting-stark-law-analysis/badge)](https://www.skillsdirectory.com/skills/lev-os-conducting-stark-law-analysis)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: conducting-stark-law-analysis
description: Evaluates physician self-referral arrangements against Stark Law exceptions with documentation. Use when analyzing Stark compliance, evaluating referral arrangements, or documenting exception applicability.
tags:
  - process
  - healthcare-compliance
  - compliance
metadata:
  author: casemark
  practice_areas:
    - Healthcare Compliance
    - HIPAA
    - Healthcare Regulation
  document_types:
    - Process Documentation
  skill_modes:
    - Process Management
---

# Conducting Stark Law Analysis

A systematic methodology for evaluating physician compensation and referral arrangements against the Physician Self-Referral Law (42 U.S.C. § 1395nn) and its regulatory exceptions under 42 CFR § 411.350–411.389.

## Why This Skill Exists

The Stark Law is a strict liability statute—no intent to violate is required. A single non-compliant referral arrangement can trigger False Claims Act liability for every claim submitted during the non-compliant period, with treble damages and per-claim penalties. CMS's 2020 and 2021 regulatory modernization updates added new exceptions (e.g., value-based arrangements) and modified existing ones, but the complexity of fitting real-world arrangements into narrow exception requirements remains a leading source of healthcare compliance risk. Self-disclosure to CMS under the SRDP (Self-Referral Disclosure Protocol) can reduce liability, but only if the violation is identified and documented with precision. This skill provides the structured analysis needed to evaluate arrangements proactively and document exception applicability with the rigor required for regulatory defense.

---

## Checkpoint A — Intake and Arrangement Identification

### Intake Questions

1. What is the financial arrangement under review—employment, personal services, lease, equipment purchase, recruitment, group practice distribution?
2. Does the arrangement involve a "referring physician" as defined under § 411.351 (or immediate family member)?
3. What "designated health services" (DHS) does the entity furnish that the physician (or family member) refers patients for?
4. What are the specific DHS categories at issue—clinical lab, radiology/imaging, PT/OT, DME, home health, outpatient prescription drugs, inpatient/outpatient hospital services?
5. Is the referring physician (or family member) an owner or investor in the entity furnishing DHS?
6. What is the compensation methodology—fixed salary, productivity-based (wRVUs, collections), percentage-based, per-click, time-based?
7. Is the arrangement documented in a written agreement signed by both parties?
8. What is the term of the arrangement, and when was it last renewed or amended?
9. Has a fair market value (FMV) opinion been obtained, and if so, who prepared it and when?
10. Does the entity participate in any value-based arrangements as defined under the 2021 Final Rule?

### Required Documents

- Written agreement(s) for the financial arrangement
- Compensation schedules, amendments, and addenda
- Fair market value appraisal or opinion
- Commercial reasonableness assessment
- Physician referral volume data for DHS
- Entity ownership/investment records
- Group practice documentation (if group practice exception claimed)
- Board meeting minutes approving the arrangement
- Prior Stark analysis or legal opinions on the arrangement
- CMS Provider Enrollment documentation confirming DHS categories furnished

---

## Step 1 — Identify the Financial Relationship

Determine whether a "financial relationship" exists between the referring physician (or immediate family member) and the entity furnishing DHS:

- **Ownership/Investment Interest** (§ 411.354(b)): Any equity, debt, or other investment interest in the entity, whether through direct ownership, investment securities, or loans/guarantees. Applies to both publicly traded and non-publicly traded entities (with different exception requirements).
- **Compensation Arrangement** (§ 411.354(c)): Any arrangement involving remuneration between the physician (or family member) and the entity. Includes direct compensation (entity-to-physician) and indirect compensation (through one or more intermediary entities).
- **Indirect Financial Relationships**: Trace the chain of financial relationships between the physician and the DHS entity. An indirect compensation arrangement exists if the physician receives aggregate compensation that varies with or takes into account the volume or value of referrals, unless an exception applies at each link.

If no financial relationship exists, the Stark Law does not apply and the analysis concludes.

---

## Step 2 — Confirm Referrals for Designated Health Services

- Verify that the physician makes or influences "referrals" as defined in § 411.351—any request for, or ordering of, an item or service payable by Medicare.
- Identify all DHS categories that the entity furnishes to Medicare beneficiaries referred by the physician.
- Note that the Stark prohibition applies only to referrals for DHS payable by Medicare (or Medicaid by operation of § 1903(s) of the Social Security Act).
- Document the volume and value of referrals over the relevant period—this data informs both the exception analysis and potential FCA exposure if non-compliance is found.

---

## Step 3 — Exception Analysis

Map the arrangement to one or more Stark exceptions and evaluate whether every element of the exception is satisfied:

**Compensation Exceptions (§ 411.357)**:
- **Employment (§ 411.357(c))**: Verify bona fide employment relationship, compensation consistent with FMV, not determined by volume/value of referrals (except productivity bonuses based on personally performed services).
- **Personal Service Arrangements (§ 411.357(d))**: Written agreement signed by parties, specifying services, for a term of at least one year (or holdover provisions), with aggregate compensation set in advance, consistent with FMV, and not varying with volume/value of referrals.
- **Fair Market Value (§ 411.357(l))**: Written arrangement, compensation consistent with FMV, arrangement commercially reasonable, not determined by volume/value of referrals.
- **Indirect Compensation (§ 411.357(p))**: Compensation received by physician does not vary with volume/value of referrals; arrangement is commercially reasonable and FMV.
- **Value-Based Arrangements (§ 411.357(aa))**: Verify arrangement meets the 2021 Final Rule value-based purpose, target patient population, and monitoring requirements.

**Ownership Exceptions (§ 411.356)**:
- **Physician Services** (§ 411.355(a)): Services personally performed or supervised by the referring physician.
- **In-Office Ancillary Services** (§ 411.355(b)): Verify same building or centralized building location test, supervision requirement, and billing requirement. Apply the "group practice" definition strictly per § 411.352.
- **Publicly Traded Securities** (§ 411.356(a)): Ownership in an entity whose securities are traded on a recognized exchange.
- **Rural Provider** (§ 411.356(c)(1)): Entity located in a rural area and substantially all DHS are furnished to rural area residents.
- **Hospital Ownership** (§ 411.356(c)(3)): Grandfather provisions for physician-owned hospitals per ACA § 6001 restrictions.

For each claimed exception, document satisfaction of every element with specific evidence references.

---

## Step 4 — Fair Market Value and Commercial Reasonableness

- **FMV Assessment**: Verify FMV was determined using a recognized valuation methodology (income approach, market approach, cost approach) as of the effective date of the arrangement. FMV means the value in arm's-length transactions consistent with the general market value per § 411.351.
- **FMV Benchmarks**: Compare physician compensation to published survey data (MGMA, AMGA, SullivanCotter, Gallagher) at the specialty and geographic market level. Significant deviations (above 75th percentile) require enhanced documentation.
- **Commercial Reasonableness**: The arrangement must make business sense independent of referrals—would the entity enter into this arrangement with a physician who made no referrals? Document the business purpose, community need, and operational rationale.
- **Volume/Value Standard**: Verify compensation does not vary with, and is not determined by, the volume or value of referrals, except where specifically permitted (e.g., productivity for personally performed services under the employment exception).

---

## Step 5 — Gap Remediation and Self-Disclosure Assessment

If the analysis identifies non-compliance:

- **Assess FCA Exposure**: Calculate the number and value of Medicare claims submitted for DHS referrals during the non-compliant period. FCA damages are treble the overpayment amount plus per-claim penalties.
- **Evaluate SRDP Self-Disclosure**: CMS's Self-Referral Disclosure Protocol allows entities to disclose actual or potential Stark violations and negotiate reduced settlements (typically 1.0x–1.5x the overpayment vs. 3x under FCA).
- **Restructure the Arrangement**: Draft corrective amendments to bring the arrangement into compliance with a specific exception, ensuring all elements are met prospectively.
- **Document Remediation**: Create a file documenting the violation period, corrective actions taken, and prospective compliance measures.
- **Consider the 90-Day Window**: 42 U.S.C. § 1320a-7b(g) requires return of identified overpayments within 60 days of identification; failure creates additional FCA liability.

---

## Checkpoint B — Analysis Validation

1. Confirm the financial relationship is correctly characterized as direct/indirect ownership or direct/indirect compensation.
2. Verify all DHS categories referred by the physician are identified and analyzed.
3. For each claimed exception, confirm every element is satisfied with documentary evidence—partial satisfaction is complete non-compliance under Stark's strict liability framework.
4. Validate FMV opinions are current (within 2 years), performed by a qualified independent appraiser, and consistent with recognized valuation methodology.
5. Confirm commercial reasonableness is documented independently from FMV.
6. Verify that "volume or value" analysis accounts for both direct and indirect correlation with referrals.
7. If non-compliance is found, confirm FCA exposure calculation and SRDP considerations are documented.
8. Review against CMS's published Stark advisory opinions for analogous arrangements.

---

## Quality Audit

- [ ] Financial relationship type (ownership/compensation, direct/indirect) correctly identified
- [ ] All DHS categories identified with supporting Medicare billing data
- [ ] Specific exception(s) cited with regulatory section references
- [ ] Every element of each claimed exception analyzed individually
- [ ] FMV opinion obtained from qualified independent appraiser and is current
- [ ] Commercial reasonableness documented with business justification independent of referrals
- [ ] Volume/value analysis addresses both direct and indirect compensation pathways
- [ ] Written agreement reviewed for completeness (signatures, term, services specification)
- [ ] Group practice requirements verified if in-office ancillary exception claimed
- [ ] Non-compliance exposure quantified with claims data if gap identified
- [ ] SRDP self-disclosure evaluated where non-compliance is identified

---

## Guidelines

- Stark Law is strict liability—there is no "intent" element. Even inadvertent technical non-compliance triggers the prohibition on referrals and claims submission.
- An arrangement must fit entirely within an exception; partial compliance is complete non-compliance. There is no de minimis exception.
- The "volume or value" prohibition applies to both direct and indirect compensation pathways. Compensation that correlates with referral volume, even if not explicitly tied to referrals, may fail this test.
- FMV and commercial reasonableness are separate requirements—an arrangement can be at FMV but not commercially reasonable (and vice versa).
- The 2021 Final Rule modernization added value-based exceptions but did not eliminate the traditional exception structure. Legacy arrangements must still satisfy legacy exception requirements.
- Group practice requirements under § 411.352 are highly technical—verify the "substantially all" test (75% of services through the group), unified business requirement, and distribution formula restrictions.
- Indirect compensation arrangements require tracing the full chain and analyzing each link. A single non-qualifying intermediate entity can disrupt the exception chain.
- Always consider parallel Anti-Kickback Statute analysis—an arrangement may satisfy a Stark exception but violate AKS, and vice versa.
- This skill produces regulatory compliance analysis, not legal advice. All Stark analyses should be reviewed by qualified healthcare regulatory counsel before reliance.

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Caveman Help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

1023330 votes

How It Works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

929660 votes
View all in documentation →