Part 2: Examples of Interplay between Peer Review and Compliance, False Claims Act, and Stark Law

Episode Date: September 28, 2022

In this episode of Stark Integrity, Bob Wade (“Captain Integrity”) continues his discussion on the interplay between peer review and compliance, focusing on practical, real-world examples that illustrate how these functions overlap—particularly in the context of the False Claims Act (FCA) and the Stark Law.

Building on Part 1, Bob moves from theory to application, helping organizations better understand who should review specific issues and how to respond appropriately.

Moving from Theory to Practice

Bob emphasizes that while it is important to understand the conceptual differences between peer review and compliance, the real challenge is determining:

• Where a specific issue should be reviewed
• Which department should take the lead
• When escalation is required

He notes that this decision-making process is often fact-specific and nuanced.

When Quality Becomes A Compliance Issue

A key takeaway from this episode is that quality issues can also be compliance issues—depending on severity.

Bob explains:

• Some clinical issues remain within peer review (quality-focused)
• Others cross into compliance territory when they impact billing, documentation, or regulatory requirements

In many cases, the same issue can be both a peer review and compliance matter simultaneously.

Fraud and Billing Issues: A Clear Line

Bob highlights an important distinction:

• Fraud and billing-related issues typically fall within compliance

These include:

• Improper coding or billing practices
• Documentation that does not support claims
• Potential FCA exposure

He makes clear that once an issue involves payment or reimbursement, it generally becomes the responsibility of the compliance function.

Determining Who Reviews an Issue

One of the most practical lessons from this episode is the need for a structured decision-making process.

Bob explains that organizations should:

• Assess the nature and severity of the issue
• Determine whether it is primarily:
  • Clinical (peer review)
  • Financial/regulatory (compliance)
  • Or both
• Assign responsibility accordingly

He stresses that someone must take ownership to ensure issues do not fall through the cracks.

Real-World Examples

Bob walks through various scenarios to help illustrate how these decisions are made.

These examples demonstrate:

• Situations where peer review alone is sufficient
• Cases where compliance must be involved
• Instances requiring joint review and coordination

He also highlights that some physician conduct can be surprising or unexpected—reinforcing the importance of having strong review processes in place.

Avoiding Silos

A major theme carried over from Part 1 is the danger of organizational silos.

Bob cautions that:

• Peer review teams cannot operate in isolation
• Compliance teams must be aware of clinical findings
• Lack of coordination increases risk

Organizations that fail to integrate these functions may miss early warning signs of FCA exposure or Stark Law violations.

Building Effective Processes

Bob emphasizes that organizations should establish:

• Clear protocols for issue identification and routing
• Defined roles for peer review and compliance teams
• Escalation pathways for high-risk concerns
• Documentation standards for both functions

These processes help ensure that issues are handled consistently and efficiently.

Practical Takeaways

The key takeaway from this episode is that determining who reviews an issue is just as important as identifying the issue itself. Organizations should:

• Evaluate each issue based on facts and risk level
• Recognize when quality concerns evolve into compliance risks
• Ensure collaboration between departments
• Assign clear responsibility for follow-up
• Develop structured workflows for decision-making

Final Thoughts

Bob Wade’s Part 2 discussion reinforces a critical point: there is no one-size-fits-all answer when it comes to peer review versus compliance.

Instead, organizations must rely on:

• Sound judgment
• Clear processes
• Strong communication

By using real-world examples, this episode provides a practical roadmap for navigating the complex intersection of clinical quality, billing compliance, and regulatory risk.

Click here to listen to this Stark Integrity Podcast Episode:
https://podcasts.apple.com/us/podcast/part-2-examples-of-interplay-between-peer-review/id1588939373?i=1000580865844&l=fr-FR