Introduction
This post compares the two federal laws most central to physician arrangement compliance: the Physician Self-Referral Law, commonly called the Stark Law (42 U.S.C. § 1395nn), and the federal Anti-Kickback Statute (42 U.S.C. § 1320a-7b(b)). It is written for compliance officers, healthcare counsel, and others who need a precise, citation-grounded reference rather than a summary.
The two laws are frequently discussed together because most physician arrangements implicate both. They are nonetheless distinct instruments: they have different scopes, different intent requirements, different penalty structures, and — following the OIG's April 2026 guidance — different roles in a defensible compliance program. Conflating them is a common source of compliance error, because an arrangement can satisfy one law and violate the other.
The post is organized definitional first, comparative second, and practical last: what each law is, how they differ, where they overlap, how to analyze an arrangement under both, the misconceptions that recur in practice, and what recent enforcement and guidance indicate for compliance program design.
What is the Stark Law?
The Stark Law, formally the Physician Self-Referral Law, is codified at 42 U.S.C. § 1395nn, with implementing regulations at 42 C.F.R. §§ 411.350–411.389. It prohibits a physician from making referrals for certain "designated health services" (DHS) payable by Medicare to an entity with which the physician (or an immediate family member) has a financial relationship, unless the arrangement satisfies a statutory or regulatory exception.
The Stark Law operates as a strict-liability statute, meaning intent is not required to establish a violation. If a financial relationship exists and no exception is fully satisfied, the referral is prohibited and the resulting claims are not payable — regardless of whether the parties intended any wrongdoing. This is the single most consequential structural feature of the statute: a good-faith arrangement that simply fails to meet every element of an exception is still a violation.
Exceptions are the mechanism by which otherwise-prohibited financial relationships become permissible. The personal services arrangements exception (42 C.F.R. § 411.357(d)), the fair market value exception, the rental-of-office-space and rental-of-equipment exceptions, and the bona fide employment exception are among those most relevant to physician arrangements. Each exception specifies elements — a writing, a term, set-in- advance compensation, fair market value, commercial reasonableness, and compensation not determined by the volume or value of referrals, depending on the exception — all of which must be satisfied.
A "financial relationship" is defined broadly to include ownership and investment interests as well as compensation arrangements, which is why most physician compensation, lease, and services agreements fall within the statute's reach.
Designated health services are enumerated by regulation and include, among other categories, clinical laboratory services, imaging, physical and occupational therapy, durable medical equipment, and outpatient prescription drugs. Some integrated arrangements rely on the in-office ancillary services exception (42 C.F.R. § 411.355(b)), which permits certain referrals within a practice; others rely on the compensation-arrangement exceptions noted above. The breadth of the DHS definition is part of why the statute reaches so much of routine practice operations.
What is the Anti-Kickback Statute?
The federal Anti-Kickback Statute (AKS) is codified at 42 U.S.C. § 1320a-7b(b), with voluntary safe harbor regulations at 42 C.F.R. § 1001.952. It prohibits knowingly and willfully offering, paying, soliciting, or receiving remuneration to induce or reward referrals of items or services reimbursable by a federal healthcare program.
Unlike the Stark Law, the AKS contains an intent requirement: the conduct must be "knowing and willful." Courts have construed this requirement through the "one purpose" rule, under which the statute is violated if even one purpose of the remuneration is to induce referrals, even where the payment also serves legitimate purposes and reflects fair market value. The inquiry is directed at why a payment was made, not merely at its amount.
The AKS is a criminal statute. A violation is a felony punishable by fines, imprisonment of up to ten years, and exclusion from federal healthcare programs; it can also support civil liability under the False Claims Act and civil monetary penalties. "Remuneration" is construed broadly to mean anything of value, in cash or in kind, whether provided directly or indirectly.
Safe harbors describe categories of arrangements that, if every condition is met, are protected from prosecution. A critical and frequently misunderstood feature is that safe harbors are voluntary: failure to fit within a safe harbor does not, by itself, establish a violation. It means only that the arrangement is evaluated under the general intent standard.
The reach of the Anti-Kickback Statute is amplified by its relationship to the False Claims Act (31 U.S.C. § 3729). Under a provision added by the Affordable Care Act in 2010, a claim that includes items or services resulting from an Anti-Kickback Statute violation constitutes a false or fraudulent claim for False Claims Act purposes. This linkage is why many of the largest healthcare settlements pair Anti-Kickback allegations with False Claims Act liability, and why whistleblower (qui tam) actions frequently frame physician arrangement matters under both.
Key differences
The two statutes are most usefully understood side by side. The table below summarizes the dimensions that most affect compliance program design.
| Dimension | Stark Law | Anti-Kickback Statute |
|---|---|---|
| Statute | 42 U.S.C. § 1395nn | 42 U.S.C. § 1320a-7b(b) |
| Type of liability | Civil; strict liability | Criminal and civil; intent required |
| Intent requirement | None (strict liability) | "Knowingly and willfully"; one-purpose rule |
| Who it covers | Physicians (and immediate family) | Anyone — broad applicability |
| What it prohibits | Self-referral for DHS to an entity with a financial relationship | Remuneration to induce federal-program referrals |
| Program scope | Medicare (limited Medicaid implications) | All federal healthcare programs |
| Exception / safe harbor | Exceptions must be fully satisfied (mandatory) | Safe harbors are voluntary; non-compliance ≠ violation |
| Penalties | Denied payment, refunds, CMPs, FCA exposure | Up to 10 years' imprisonment, fines, exclusion, civil liability |
| Role of fair market value | Central to most exceptions | Necessary but not sufficient (OIG, April 2026) |
The most consequential difference is the contrast between strict liability and intent. Because the Stark Law imposes liability without regard to intent, the compliance task it creates is essentially documentary: confirm that an exception applies and that every element is satisfied and recorded. The Anti-Kickback Statute creates a different task, because intent cannot be reduced to a checklist; it must be assessed from the structure and operation of the arrangement. A program optimized only for Stark exception fit will tend to under-examine the question the AKS actually asks.
The second-most consequential difference is the voluntary nature of AKS safe harbors. Because a safe harbor is not the only path to compliance, the absence of safe harbor protection is a prompt for analysis, not a conclusion of liability — the inverse of how Stark exceptions function.
Where they overlap
In practice, most physician arrangements implicate both statutes at once. A medical directorship, a professional services agreement, a space or equipment lease, or an employment arrangement typically creates a financial relationship that the Stark Law reaches and a flow of remuneration that the Anti-Kickback Statute reaches.
The overlap is not symmetrical, and that is the point most relevant to compliance officers. An arrangement that satisfies a Stark Law exception may still violate the AKS if intent to induce referrals is present. Conversely, an arrangement structured to fit an AKS safe harbor may still violate the Stark Law if an exception element is missing, because Stark exceptions are mandatory and strict. Neither analysis substitutes for the other.
Because the two analyses ask different questions, they can reach different conclusions on the same facts. An arrangement may satisfy every Stark exception element and still present meaningful Anti-Kickback exposure where its structure or operation suggests a referral-inducement purpose; the reverse is also possible where a safe-harbored arrangement omits a required Stark element. Treating the two statutes as a single inquiry is precisely the error the April 2026 guidance is directed against.
This is the explicit message of the OIG's April 23, 2026 FAQ updates (revised FAQ 4 and new FAQ 17): Stark compliance and fair market value do not, by themselves, provide Anti-Kickback Statute protection, and AKS exposure turns on intent. The working assumption a defensible program adopts is therefore that both analyses are required for every physician arrangement. The intent dimension is treated at greater length in FMV Alone Won't Save You.
How to analyze a physician arrangement under both
A dual-statute analysis can be approached as an ordered sequence. The steps below are a working framework, not a substitute for counsel.
1. Determine whether the Stark Law applies. Is a physician referring designated health services payable by Medicare, and is there a financial relationship between the physician (or an immediate family member) and the entity furnishing the DHS? If so, the Stark Law is in scope.
2. Identify the applicable Stark exception. Common candidates include personal services (42 C.F.R. § 411.357(d)), fair market value, rental of office space, rental of equipment, and bona fide employment.
3. Verify each element of the exception. Confirm, element by element and with documentation, that the exception is fully satisfied. Because Stark is strict liability, a single unmet element defeats the exception.
4. Independently analyze Anti-Kickback Statute exposure. Separately assess the intent surrounding the remuneration. Is any purpose of the payment to induce or reward referrals? Consider whether compensation tracks the volume or value of referrals, whether any remuneration travels outside the written agreement, and whether the arrangement is commercially reasonable apart from referrals.
5. Identify a relevant safe harbor, if available. Determine whether the arrangement fits an AKS safe harbor — personal services and management contracts, space rental, equipment rental, or employment, among others. Fitting a safe harbor strengthens the posture; failing to fit one returns the arrangement to the general intent standard.
6. Document both analyses contemporaneously. Record the Stark exception elements and the Anti-Kickback intent analysis at the time the arrangement is active, not retrospectively. The reasons documentation must be contemporaneous are treated in The Spreadsheet Gap.
Common misconceptions
Several recurring misunderstandings are worth stating precisely.
"Fair market value is enough to defend an arrangement." Incorrect as to the Anti-Kickback Statute. Per the OIG's April 2026 FAQ update, fair market value is necessary but not dispositive; an at-market payment can still be unlawful if intent to induce referrals is present.
"The Stark Law applies only to Medicare." Largely accurate as to designated health services, with limited Medicaid implications. The Anti-Kickback Statute, by contrast, reaches all federal healthcare programs.
"An arrangement at fair market value cannot violate the AKS." Incorrect. The "one purpose" rule means an FMV payment violates the statute if even one purpose is to induce referrals.
"Failing to meet a safe harbor means an AKS violation." Incorrect. Safe harbors are voluntary; non-compliance returns the arrangement to the general intent analysis rather than establishing liability.
"The Stark Law requires intent." Incorrect. The Stark Law is strict liability; intent is not an element of a violation.
Recent enforcement patterns
Enforcement illustrates how the two statutes operate, separately and together. The Tuomey Healthcare matter ($72.4M, on a 21,730 false-claims jury finding) centered on compensation that the government argued tracked the volume or value of referrals — the intersection of Stark exception elements and Anti-Kickback intent. Community Health Network ($345M, the largest Stark settlement in ArrowISE's enforcement library) involved alleged failures of exception compliance and documentation integrity. Fresno Community Health reflects Anti-Kickback Statute exposure arising from physician remuneration arrangements.
Taken together, these matters reflect a consistent enforcement interest in physician financial relationships and a willingness to pursue both statutes where the facts support it. Additional matters are catalogued in the ArrowISE enforcement library.
What this means for compliance programs
The post-April 2026 guidance does not change the law, but it removes a common shortcut. A compliance program can no longer treat a current fair market value opinion and a satisfied Stark exception as a complete defense; the OIG has stated that the Anti-Kickback analysis is independent and intent-driven.
Three implications follow for program design. First, documentation must be contemporaneous, so that the evidence of compliance demonstrably existed while the arrangement was active. Second, fair market value documentation must be paired with an explicit intent analysis, as discussed in FMV Alone Won't Save You. Third, the program's workflow and its audit-ready evidence packets should surface both analyses for every arrangement, on a recurring cadence rather than only at execution — an operational point developed in The Compliance Officer's Quarterly Audit. How ArrowISE structures this dual-statute methodology is described on the methodology page.
Where to go next
For a fuller treatment of how compliance programs operationalize the dual-analysis requirement, see the ArrowISE methodology. For examples of where physician arrangement compliance has failed under one or both statutes, see the enforcement library. For the operational cadence implications, see The Compliance Officer's Quarterly Audit; and for the documentation-integrity controls behind a defensible evidence trail, see the security overview.