Intent under the Stark Law: "But I Thought Stark Was Civil, Not Criminal"

Episode Date: June 15, 2022

In this episode of Stark Integrity, host Bob Wade (“Captain Integrity”) tackles a common misconception in healthcare compliance: if the Stark Law is a strict liability statute, does intent matter at all?

While Stark is often described as a “no intent required” law, this episode explains that the reality is more nuanced—and understanding that nuance is critical for compliance.

Stark Law and Strict Liability

At its core, the Stark Law is a strict liability statute, meaning that a violation can occur regardless of intent. If a financial relationship exists and referrals occur without meeting an applicable exception, the law is violated—even if no one intended to do anything wrong.

This is what makes Stark uniquely unforgiving compared to other healthcare laws like the Anti-Kickback Statute (AKS), which requires proof of intent.

So…Where Does Intent Come In?

This episode clarifies a key distinction: while intent is not required to prove a violation, certain elements of a Stark arrangement still involve intentional actions by the parties.

For example:

• The parties must intend to enter into a financial arrangement
• The arrangement must involve an exchange of remuneration or benefit
• There must be a knowing relationship between the parties, even if they don’t intend to violate the law

In other words, intent is not relevant to liability—but it is relevant to understanding whether an arrangement exists in the first place.

Bob’s “Three Buckets” of Intent

Bob introduces a practical framework for thinking about intent under Stark: dividing it into “buckets.”

While Stark does not require intent to violate the law, organizations should still evaluate:

• Whether the parties intended to create the arrangement
• Whether value was actually exchanged
• Whether payments or benefits were received

This framework helps clarify when Stark is implicated—and when it is not.

Overpayments vs. Stark Violations

Another key takeaway from this episode is that not every payment issue equals a Stark violation.

Bob emphasizes that:

• Mere overpayments or accounting errors do not automatically trigger Stark
• There must be an actual financial relationship tied to referrals
• The arrangement must fail to meet an applicable exception

This distinction is important, as organizations often overreact to payment issues without analyzing whether Stark truly applies.

Interaction with the Anti-Kickback Statute

As in many episodes, Bob highlights the relationship between Stark and the AKS.

While Stark focuses on structure and technical compliance:

• AKS focuses on intent to induce referrals
• The same arrangement may be evaluated under both laws
• An arrangement that passes Stark could still raise AKS concerns

Understanding this interplay is critical for a complete compliance analysis.

Practical Takeaways

The central takeaway from this episode is that “strict liability” does not mean “intent is irrelevant in all contexts.” Healthcare organizations should:

• Understand that Stark violations do not require proof of intent
• Recognize that intent still plays a role in forming arrangements
• Distinguish between technical errors and actual Stark violations
• Analyze both Stark (structure) and AKS (intent) together

Final Thoughts

This episode tackles one of the most misunderstood aspects of the Stark Law. While the statute is strictly applied, the concept of intent still has a practical role in determining whether a financial relationship exists.

By breaking down this nuance, Bob provides a clearer framework for evaluating arrangements—helping organizations avoid both unintentional violations and unnecessary overcorrections.

Click here to listen to this Stark Integrity Podcast Episode:
https://podcasts.apple.com/us/podcast/intent-under-the-stark-law-but-i-thought-stark-was/id1588939373?i=1000564767986&l=fr-FR