Identify Issues In Stark Law Compliance Program

---
name: hls-identify-stark-compliance-program-issues
task_id: healthcare-life-sciences/identify-issues-in-stark-law-compliance-program
description: Reviews a Stark Law compliance program, physician arrangement documents, and internal audit materials to identify exception-citation deficiencies, in-office ancillary services same-building issues, holdover-arrangement issues, and compliance-officer reporting-independence gaps.
activates_for: [planner, solver, checker]
---

# Skill: Identify Issues in Stark Law Compliance Program

## 1. Subject-matter triage
- Treat the source set as a Stark Law compliance-gap review across physician compensation and referral arrangements, not a generic policy audit.
- First inventory the physician arrangements, compliance-program documents, audit findings, and governance materials; then analyze each arrangement and control point against the relevant Stark framework.
- If the documents span multiple arrangements, periods, or entities, enumerate them before analysis and keep the review itemized by arrangement and issue.
- If only one arrangement or one governance structure is in scope, state that explicitly and explain why.

## 2. Failure modes the skill is correcting
- Exception citations are given only at a broad exception-family level, leaving the analysis too vague for defense, remediation, or disclosure.
- Holdover eligibility is assessed without tracing the full expiration / renewal history, so a later holdover period is missed.
- In-office ancillary services are assumed compliant without checking whether DHS performance occurs in the same building or an approved centralized building.
- Compliance-officer independence is assumed from title alone, without testing reporting lines to the board or audit committee.
- Findings are described without linking the issue to a specific legal authority, the interacting document or arrangement, and the practical consequence.
- Remediation is implied but not stated as concrete next steps with responsibility and timing.

## 3. Legal frameworks / domain conventions that apply
- Stark Law: apply the physician self-referral statute, 42 U.S.C. § 1395nn, and the relevant implementing regulations in 42 C.F.R. Part 411.
- Exception analysis: cite the specific exception and subsection or comparable granular authority, not just the exception family.
- Limited holdover exception: trace the arrangement’s expiration, any renewal or termination, and any later holdover period that may affect eligibility.
- In-office ancillary services: test the same-building requirement and any centralized-building concept against the physical location where DHS is furnished.
- Compliance-program governance: assess whether the compliance officer reports independently to the board or audit committee, rather than through operational management.
- Use the source documents’ terminology where helpful, but anchor every legal proposition to a controlling statute, regulation, or other recognized authority.
- Severity should be stated on a uniform ordinal scale defined once at the top of the memo.

## 4. Analytical scaffolds
1. Build an arrangement-by-arrangement inventory: identify the parties, term, compensation or services structure, governing exception, and any renewal / holdover history.
2. For each arrangement, test each exception element in sequence; do not skip from a general conclusion to the end result.
3. When a citation is too broad, narrow it to the specific subsection, clause, or regulatory prong that actually governs the issue.
4. For holdover issues, trace the timeline from initial expiration through any later holdover or renewal periods and identify where eligibility may break.
5. For IOAS issues, compare the place of service for DHS against the physician office location and any centralized-building arrangement reflected in the documents.
6. For governance issues, map the compliance officer’s reporting line and escalation path, then test independence from the CEO / COO / operational chain.
7. Close each issue with: the legal authority, the document intersection, the operational or regulatory consequence, the severity, and a concrete remediation recommendation.
8. When source documents include amounts, terms, dates, or thresholds, use them to scale the issue; do not invent figures or perform hidden arithmetic.

## 5. Vertical / structural / temporal relationships
- Treat arrangement history as time-sensitive: expiration, amendment, renewal, and holdover dates can change the Stark analysis.
- Treat related documents as cross-referencing controls: an agreement, amendment, policy, audit memo, or board charter may cure or worsen the same issue.
- Treat governance and operational controls as vertically related: board oversight, compliance reporting, and day-to-day operations should be analyzed as separate layers.
- If a later document changes an earlier assumption, prioritize the later controlling document and explain the shift.

## 6. Output structure conventions
- Write a memo-style gap analysis organized by arrangement first, then by issue category or exception element.
- Open with a concise executive summary stating the overall risk picture and the highest-severity findings.
- Define the severity scale once near the front and apply it consistently to every finding.
- For each finding, use a compact issue format: arrangement / control at issue → governing authority → what fails → why it matters → severity → recommendation.
- Include the specific Stark authority for each proposition; do not rely on conclusory statements without citing the rule.
- Distinguish between a documentation gap, a substantive compliance gap, and a governance gap.
- End with a Recommended Actions section that assigns each action to a responsible role and gives a timing anchor tied to the remediation cadence or regulatory milestone.
- Keep the memo substantive and remediation-oriented; do not use a checklist-only format or a narrative that omits issue-level conclusions.