Compliance: Know the Difference Between Fraud and Abuse

Subscribe or sign in to view the full article.

Note:  The following article synopsis was NOT provided by AAPC. It was created by Find-A-Code/innoviHealth.

Article Overview

This compliance-focused article reviews how Medicare fraud differs from Medicare abuse and why the distinction matters for providers, billing staff, and compliance teams. It summarizes broad categories of problematic conduct discussed by a Medicare Administrative Contractor and CMS-related educational material, including documentation, claims submission, payer order, beneficiary issues, supplier standards, and other improper practices. The piece is designed to help readers recognize the scope of Medicare enforcement concerns without serving as a substitute for the full guidance.

Why This Topic Matters

Understanding the difference between fraud and abuse helps organizations strengthen compliance programs, reduce payment risk, and recognize issues that can trigger audits, repayment demands, or enforcement action.

Article Sections

  1. What Constitutes Medicare Fraud?

    Defines fraud at a high level and discusses broad examples of intentional deception in the Medicare program. It also notes that fraudulent activity can involve multiple types of individuals and organized schemes.

  2. Fraud varieties

    Summarizes several broad categories of fraudulent conduct described in the source material. The section focuses on general patterns of misconduct and enforcement concerns.

  3. Gang visits

    Describes a form of abusive or fraudulent behavior involving group billing in long-term care settings. The discussion frames the compliance concern in a general way.

  4. Here’s How Abuse Is Different Than Fraud

    Explains abuse as a separate Medicare compliance issue that is more closely tied to claims, billing, and coding practices. It highlights the risk that improper practices can escalate.

  5. Top abuse scenarios

    Outlines broad examples of abusive billing and coding behaviors identified by the source. The section also includes payer-order and patient-charge concerns, along with related compliance topics.

  6. Example: Unbundling

    Provides a general illustration of unbundling in a laboratory billing context. The example is presented to show why the practice is a compliance concern.

  7. Resource

    Points readers to CMS educational material for additional background on fraud and abuse. It serves as a reference and follow-up section.

What You Will Learn

  • How Medicare fraud and abuse are distinguished at a broad level
  • What kinds of compliance issues are commonly associated with fraud and abuse
  • Why billing, documentation, payer-order, and supplier-standard issues matter
  • How Medicare contractors and CMS-related resources frame enforcement concerns
  • Why some improper practices may escalate from abuse into fraud

Who Should Read This

  • Medical coders
  • Billing staff
  • Compliance officers
  • Revenue cycle managers
  • Healthcare providers
  • Practice administrators

Subscribe or sign in to view the full article.

Keep pace with evolving Medicare regulations — and onboard your team — with timely analysis of critical updates interpreted in an easy-to-follow, easy-to-apply format. Your subscription to TCI's Medicare Compliance & Reimbursement Alert will equip you to navigate code and guideline changes, CCI edits, and revisions to modifiers, payer policies, the fee schedule, OIG target areas, and more.

  • Current newsletters added each month
  • Fully searchable archives - over 4200 articles
  • ALL years/issues back to 2003 organized by year and issue
  • Codes mentioned in articles are linked to Code Information pages
  • Code Information pages link back to related articles

This feature is currently unavailable for online purchase. For more information, please call 801-770-4203 or Contact Us.

Thank you for choosing Find-A-Code, please Sign In to remove ads.

Aimee- AI -powered coding assistant - Try it now for Free Would you like Aimee - AI
to help you with this?