← Back to episodes

Episode 94 ·

Master List Requirement under the Stark Law Explained

Send us Fan Mail A master list reference is sometimes necessary under the Stark Law. In this episode - suggested by a Stark Integrity listener - Captain Integrity Bob Wade explains when and why that’s the case. Hear why creating a master list is just good practice, why it’s a legal requirement to cross-reference it, why you need to dedicate resources to maintain a master list, some interesting numbers tied to master lists, and what The Sound of Music has to do with them. Learn more at CaptainIntegrity.com

  • Stark Law

Listen to the episode

Audio

Ready to play. Audio loads only after you press Play.

0:000:00

Prefer Buzzsprout? Listen on Buzzsprout.

Companion article

Master List Requirement Under the Stark Law Explained

Episode Date: October 25, 2023

In this episode of Stark Integrity, Bob Wade (“Captain Integrity”) tackles a practical—but often overlooked—compliance tool under the Stark Law: the master list requirement for physician financial arrangements.

While it may sound administrative, the master list plays a critical role in organizing, tracking, and proving compliance—and in some cases, it is effectively required to meet a Stark Law exception.

What Is a Master List?

A master list is a centralized inventory of:

  • All physician financial arrangements
  • Key contract terms (parties, services, compensation, term)
  • Cross-references to underlying agreements

It acts as a single source of truth for physician relationships across the organization.

Why It Matters Under the Personal Services Exception

A key point from this episode is that the master list is not just a best practice—it can be necessary to satisfy the Personal Services Arrangements Exception.

Under this exception, compensation arrangements must be:

  • Documented in writing
  • Clearly define the services and compensation
  • Meet all required elements of the exception

Bob Wade emphasizes an important nuance:

  • If you have multiple arrangements with the same referring physician or group,
  • And your individual agreements do not explicitly cross-reference one another,

then you must maintain a centralized system (i.e., a master list) that ties all of those arrangements together.

Without that:

  • You may not be able to demonstrate that the arrangements collectively meet Stark requirements
  • Documentation may appear incomplete or fragmented
  • Compliance with the exception could be challenged

In other words:
If your contracts don’t connect the dots, your master list must.

The Compliance Function

From a legal and audit perspective, the master list allows organizations to:

  • Identify all arrangements with a single physician or group
  • Demonstrate that compensation is consistent with applicable exceptions
  • Show regulators a complete and organized compliance framework

This is critical because Stark Law compliance is:

  • Technical
  • Documentation-driven
  • Evaluated based on what you can produce and prove

Operational Value

Beyond legal compliance, the master list supports day-to-day operations by helping organizations:

  • Track contract terms and expiration dates
  • Prevent payments under expired agreements
  • Ensure services align with contractual requirements
  • Coordinate across legal, compliance, and finance teams

It directly addresses a recurring theme:
Most Stark issues arise from operational gaps—not from poor contract drafting.

Common Pitfalls

Without a functioning master list, organizations often face:

  • Disconnected agreements across departments
  • Inability to track all arrangements with a single physician
  • Payments that cannot be tied back to valid contracts
  • Overlapping or inconsistent compensation structures

These issues can create unnecessary compliance exposure, even when each individual agreement appears compliant on its own.

Practical Takeaways

This episode reinforces a clear and actionable message:

  • A master list is often essential—not optional
  • It becomes critical when agreements do not cross-reference each other
  • It serves as both a compliance safeguard and operational control tool

Organizations should ensure their master list:

  • Is complete and regularly updated
  • Clearly ties together all arrangements with each physician or group
  • Links directly to supporting documentation
  • Is accessible for audit and compliance review

Final Thoughts

The master list may seem like an administrative detail—but under the Stark Law, details matter.

As Bob Wade highlights, the ability to connect, track, and produce all physician arrangements is fundamental to satisfying key exceptions like the Personal Services Arrangements Exception.

In practice, this often comes down to a simple principle:
If your contracts don’t cross-reference each other, your master list must do it for them.

Click here to listen to this Stark Integrity Podcast Episode:
https://podcasts.apple.com/us/podcast/master-list-requirement-under-the-stark-law-explained/id1588939373?i=1000632524324&l=fr-FR