Stark Law and Anti-Kickback Statute Compliance Training for Healthcare Providers

Two federal fraud and abuse laws sit behind more healthcare compliance investigations than almost any other statute on the books: the Stark Law and the federal Anti-Kickback Statute (AKS). Both aim at the same underlying problem — financial relationships that could influence a clinical referral — but they work in very different ways, carry very different penalties, and require different things from a training program. Getting the distinction right matters, because a well-meaning employment contract, a discounted equipment lease, or a "thank you" payment to a referring physician can turn into a six- or seven-figure liability if nobody in the organization was trained to spot it.

This guide breaks down what each law actually prohibits, who it applies to, the exceptions and safe harbors that keep legitimate arrangements out of trouble, and what a compliance training program needs to cover. It pairs well with a broader look at Medicare Conditions of Participation for hospitals, since Stark and AKS exposure often surfaces during the same billing and contracting reviews.

What the Stark Law Prohibits

The Stark Law, formally the physician self-referral law (42 U.S.C. § 1395nn), prohibits a physician from referring Medicare patients for certain "designated health services" (DHS) to an entity with which the physician — or an immediate family member — has a financial relationship, unless the arrangement fits squarely within a regulatory exception. Designated health services include clinical laboratory services, physical and occupational therapy, radiology and imaging, radiation therapy, durable medical equipment, home health services, outpatient prescription drugs, and inpatient and outpatient hospital services.

The defining feature of Stark is that it is a strict liability statute. There is no requirement to prove intent to defraud. A physician doesn't need to have meant to profit from referrals for a violation to occur — an expired lease, a compensation formula that happens to track referral volume, or a missing signature on a service agreement can be enough. That is exactly why so many Stark problems are discovered by compliance audits rather than whistleblowers: the underlying arrangement often looks completely ordinary on paper.

What the Anti-Kickback Statute Prohibits

The Anti-Kickback Statute (42 U.S.C. § 1320a-7b(b)) is a criminal statute that prohibits knowingly and willfully offering, paying, soliciting, or receiving any form of remuneration — cash, free services, below-market rent, excessive compensation, gifts, and more — to induce or reward referrals of items or services reimbursable by a federal healthcare program.

Unlike Stark, the AKS is not limited to physicians or to a defined list of services. It reaches anyone in the referral chain: hospitals, physician practices, laboratories, home health and hospice agencies, durable medical equipment suppliers, pharmaceutical and device manufacturers, and the marketing and consulting firms that work with them. It also requires proof that the remuneration was offered or accepted with intent to induce referrals — though courts have interpreted "one purpose" of a payment being to induce referrals as enough to trigger liability, even if there were other legitimate reasons for the arrangement.

Stark vs. AKS: The Core Differences

Exceptions and Safe Harbors

Both laws recognize that plenty of financial relationships between referring parties are completely legitimate — a hospital employing a physician, a practice leasing office space, a specialist covering call for the emergency department. The two frameworks protect these relationships differently.

Common Stark Law exceptions include bona fide employment relationships, fair market value compensation arrangements, the in-office ancillary services exception, physician recruitment arrangements, personal service arrangements, and space or equipment rental — provided the arrangement is in writing, set in advance, for a term of at least one year, and priced at fair market value without regard to the volume or value of referrals.

AKS safe harbors cover similar ground — space and equipment rental, personal services and management contracts, bona fide employee relationships, investment interests, discounts, warranties, and group purchasing organization arrangements — plus provisions for electronic health record items and services. In 2021, CMS and the HHS Office of Inspector General finalized coordinated updates to both frameworks (the "Regulatory Sprint to Coordinated Care") that added new exceptions and safe harbors for value-based arrangements, recognizing that coordinated, outcomes-based care models don't always fit neatly into older fee-for-service rules.

Penalties

The Anti-Kickback Statute carries criminal exposure: a felony conviction can result in up to ten years in prison and fines of up to $100,000 per violation, alongside mandatory exclusion from Medicare, Medicaid, and all other federal healthcare programs for a minimum of five years. Civil monetary penalties and administrative sanctions can apply on top of that.

The Stark Law carries no criminal penalty, but the civil exposure is still serious. Violations can trigger civil monetary penalties per prohibited billed service, along with repayment of amounts improperly received, and penalties that scale up further for arrangements found to be a "circumvention scheme" designed to get around the law. Because Stark is strict liability, providers who identify a violation are expected to repay any resulting overpayment within 60 days of discovery to limit further exposure.

The connection that makes both laws so financially dangerous is the False Claims Act. Claims submitted for services referred in violation of Stark, or generated through a kickback arrangement, can be treated as false claims — exposing the organization to treble damages, a per-claim penalty that can run into the tens of thousands of dollars, and qui tam lawsuits brought by whistleblowers who share in any recovery.

Who Needs to Be Trained

• Physicians and advanced practice providers who make or influence referrals
• Practice administrators and managers who negotiate leases, medical director agreements, and call-coverage pay
• Compliance officers and legal or contracts staff who draft and review financial arrangements
• Hospital executives, department chairs, and boards who approve physician compensation
• Billing and coding staff who need to recognize red flags in claims tied to referral relationships

What a Compliance Training Program Should Cover

Effective training goes well beyond a one-hour annual video. It should give staff the vocabulary and judgment to flag a problem before a contract is signed, not after a claim has already been submitted. At minimum, a program should cover:

• Clear definitions of designated health services, financial relationships, remuneration, and referral
• A practical process for vetting any new financial arrangement before it is executed
• Fair market value documentation practices and how to obtain a defensible valuation
• A red-flag checklist: compensation tied to referral volume or value, below-market or free rent, equipment, or staff time, unusually generous terms, and exclusivity clauses linked to referral commitments
• Exception and safe harbor checklists mapped to common arrangement types (employment, leases, medical directorships, call coverage)
• Self-disclosure options — the CMS Voluntary Self-Referral Disclosure Protocol for Stark issues and the OIG Self-Disclosure Protocol for kickback concerns — and when to use them
• A schedule for periodically re-reviewing existing arrangements, since an agreement that was compliant at signing can drift out of compliance as terms, staffing, or referral patterns change

Building this kind of judgment across an organization is part of a wider effort described in our piece on building a culture of compliance in healthcare — rules alone don't prevent violations; people who understand why the rules exist do. Structured, role-specific CPD courses are one of the most reliable ways to build and document that understanding across physicians, administrators, and compliance staff alike.

FAQ

Does the Stark Law apply to Medicaid claims?

Stark is a Medicare statute, but many states have adopted parallel self-referral restrictions for their Medicaid programs, and some state Medicaid rules cross-reference the federal Stark framework directly. Providers billing Medicaid should check their state's specific requirements rather than assuming Stark doesn't apply at all.

Can a hospital be held liable for a physician's Stark violation?

Yes. Because Stark is strict liability, a hospital that submits a claim for a designated health service referred in violation of the law can face liability even if it did not intend to violate the statute and even if the referring physician was unaware of the problem.

What's the practical difference between an exception and a safe harbor?

A Stark exception is mandatory: if an arrangement involves a financial relationship and a DHS referral, it must fit within an exception or it is a per se violation. An AKS safe harbor is voluntary protection: falling outside a safe harbor does not automatically mean an arrangement is illegal, but it does mean the arrangement will be judged on the facts, including intent.

How often should existing financial arrangements be reviewed?

At least annually, and immediately whenever compensation terms, staffing, space, or referral patterns change. Many organizations build this into their annual compliance work plan alongside contract renewal dates.

Stark and AKS violations rarely start as deliberate fraud — they start as an overlooked lease renewal, an informal handshake deal, or a compensation formula nobody re-checked after a service line changed. A training program that gives physicians, administrators, and compliance staff a shared vocabulary and a clear escalation path is the most effective safeguard an organization has against both laws.