Episode 212 ·
Isolated Transaction Exception under the Stark Law: “All by Myself”
Send us Fan Mail There are some uses of the isolated transaction exception that are prohibited under the Stark Law. In this episode, Captain Integrity Bob Wade dives into that isolated transaction exception. Hear why the isolated transaction exception has been expanded, the times when it can be used for service arrangements, how it can be used for settlement of a bona fide dispute, the nuances of the isolated transaction exception, and the history of the famous song, “All by Myself.” Learn more at CaptainIntegrity.com
- Stark Law
Listen to the episode
Companion article
Isolated Transaction Exception Under the Stark Law: “All by Myself”
Episode Date: April 15, 2026
In this episode of Stark Integrity, Bob Wade (Captain Integrity) explores an important and nuanced concept under the Stark Law:
The isolated transaction exception—and when a one-time financial arrangement may qualify for protection.
The episode emphasizes a key point:
Not all financial relationships are ongoing—and the Stark Law provides a pathway for certain one-time transactions to remain compliant.
Understanding the Isolated Transaction Exception
A central theme of the episode is:
What qualifies as an isolated transaction under the Stark Law.
An isolated transaction generally refers to:
- A one-time financial arrangement
- A transaction that is not recurring or ongoing
- A discrete event, such as a sale or transfer
The takeaway:
This exception is designed for limited, one-off arrangements—not continuous relationships.
Why the Exception Exists
The Stark Law recognizes that:
Not every transaction involves an ongoing financial relationship or referral concern.
The isolated transaction exception allows for:
- Certain one-time deals
- Non-recurring transfers of value
- Limited financial interactions
The key point:
The exception provides flexibility—but only within strict boundaries.
Common Examples
Typical examples of isolated transactions may include:
- The sale of a medical practice
- The purchase or transfer of equipment
- A one-time asset transaction
These situations:
- Do not involve repeated payments
- Do not create ongoing financial ties
- Are limited in scope and duration
The takeaway:
The exception applies best to clearly defined, one-time events.
Requirements for the Exception
To qualify for the isolated transaction exception, arrangements must:
- Be commercially reasonable
- Be consistent with fair market value
- Not take into account the volume or value of referrals
The key point:
Even one-time transactions must meet core Stark Law requirements.
What Does Not Qualify
A major focus of the episode is:
What falls outside the isolated transaction exception.
Arrangements that may not qualify include:
- Installment payments that resemble ongoing compensation
- Repeated or structured transactions over time
- Arrangements that effectively create a continuing relationship
The takeaway:
Calling something “isolated” does not make it so—structure matters.
Substance Over Form
As emphasized throughout the episode:
Regulators look at the substance of the arrangement—not just how it is labeled.
This means:
- A transaction labeled as “one-time” may not qualify if payments are spread out improperly
- The overall structure must align with the purpose of the exception
- Economic reality determines compliance
The key point:
Labels do not control—the facts do.
Risks of Misuse
Misapplying the isolated transaction exception can create:
- Improper referral relationships
- Failure to meet a Stark Law exception
- Compliance and enforcement risk
The takeaway:
Overreliance on this exception without proper analysis can lead to exposure.
Documentation Is Critical
As with other Stark Law exceptions:
Documentation plays a key role in defensibility.
Organizations should ensure:
- Clear description of the transaction
- Defined terms and pricing
- Support for fair market value
- Evidence that the arrangement is truly one-time
Because:
Strong documentation supports the position that the exception applies.
Avoiding Common Pitfalls
The episode highlights several common mistakes:
Treating Installments as Isolated
Spreading payments over time without proper structure.
Repeating “One-Time” Transactions
Engaging in similar transactions that create a pattern.
Weak Documentation
Failing to clearly define the transaction terms.
Ignoring FMV Requirements
Not supporting the value exchanged.
The key point:
Improper structuring can invalidate the exception.
Practical Considerations
To properly apply the isolated transaction exception, organizations should:
- Evaluate whether the transaction is truly one-time
- Ensure compliance with fair market value standards
- Structure payments appropriately
- Document the arrangement clearly
- Avoid creating patterns of repeated transactions
Because:
Careful planning is essential to qualify for the exception.
Key Takeaways
- The isolated transaction exception applies to one-time arrangements
- It does not apply to ongoing or repeated relationships
- Fair market value and commercial reasonableness are still required
- Substance matters more than labels
- Improper structuring can invalidate the exception
- Documentation is critical for defensibility
- Each transaction must be evaluated individually
Final Thoughts
This episode reinforces an important compliance principle:
Not all financial relationships are ongoing—but even one-time transactions require careful analysis.
The isolated transaction exception offers flexibility, but:
- It is narrowly defined
- It must be applied correctly
- It depends on structure and substance
Ultimately:
A one-time transaction must truly stand alone to qualify.
Because in healthcare compliance:
Even a single transaction can carry significant regulatory implications.
Click here to listen to this Stark Integrity Podcast Episode:
https://podcasts.apple.com/us/podcast/isolated-transaction-exception-under-the-stark-law/id1588939373?i=1000761443646&l=fr-FR
