Some healthcare laws kick down the door. The Stark Law is not one of them. It does not usually arrive with a dramatic raid scene, a television-ready slogan, or a trending hashtag. It is quieter than that. It lives in contract files, compensation models, lease terms, board approvals, and the kind of spreadsheet tabs that make compliance officers reach for coffee before 9 a.m.
That quiet can be deceptive. Because the Stark Law is no longer the shiny object of every conference panel, some organizations treat it like yesterday’s problem. That is risky. The law still governs physician referrals for designated health services, still carries strict consequences, and still shows up in False Claims Act cases, self-disclosures, internal audits, and transaction diligence. In other words, Stark may not be loud, but it is absolutely still on the payroll.
For hospitals, physician groups, ambulatory platforms, compliance leaders, private equity-backed practices, and health systems trying to modernize care, the real question is not whether Stark is exciting. It is whether it is still operationally dangerous. The answer is yes. Quietly, persistently, and sometimes expensively, yes.
What the Stark Law Actually Does
At its core, the Stark Law, also called the federal physician self-referral law, prohibits a physician from referring Medicare patients for certain designated health services to an entity with which the physician, or an immediate family member, has a financial relationship unless an exception applies. It also bars the entity from billing for services that result from a prohibited referral. That basic framework sounds simple enough, right up until someone says, “We thought the agreement was in the shared drive.”
The law covers a defined list of designated health services, including common areas where referral patterns matter a lot: clinical laboratory services, imaging, radiation therapy, durable medical equipment, home health services, outpatient prescription drugs, and inpatient and outpatient hospital services. That means Stark is not some exotic museum piece for rare fact patterns. It applies in places where healthcare organizations do business every single day.
Another reason Stark still matters: it is a strict liability statute. You do not need proof of evil intent, cartoon villain laughter, or a secret email saying, “Let us monetize referrals.” If the arrangement fails to meet an exception, the referral can be prohibited even without bad intent. Compare that with the Anti-Kickback Statute, which is intent-based and criminal. The two laws often travel together, but they are not twins. Passing Stark does not automatically mean you pass AKS, and vice versa.
Why It Feels So Quiet Right Now
The healthcare industry has spent the last several years juggling telehealth rules, AI governance, price transparency, reimbursement pressure, cybersecurity, workforce shortages, Medicare Advantage disputes, and aggressive deal scrutiny. Against that backdrop, Stark has become the compliance equivalent of the smoke detector you stop noticing until it chirps at 2:17 a.m.
There is also a practical reason for the lower noise level. CMS modernized the Stark regulations in 2020, adding new value-based exceptions and clarifying key concepts like fair market value, commercial reasonableness, and the volume-or-value standard. Those reforms made the rules more navigable in some areas, especially for care coordination and value-based structures. In plain English: CMS cleaned up part of the map, so some people assumed the mountain had disappeared. It did not.
In fact, the modernization may have made Stark less theatrical but more technical. Instead of endless industry debate over whether the regulations fit modern care delivery, the conversation has shifted to harder operational questions: Does this compensation formula really work under the revised rule? Is this arrangement commercially reasonable even if it loses money? Is the math tied to referrals in a way that crosses the line? Have we documented the services clearly enough? Are we still relying on pandemic-era habits after the COVID blanket waivers ended?
That is not a quieter risk environment. It is just a more grown-up one.
Why the Law Has Not Gone Away
1. Enforcement has not stopped
If anyone thought Stark quietly retired to a beach condo in Florida, recent enforcement says otherwise. DOJ settlements and complaints in 2024, 2025, and 2026 show the government is still pursuing physician self-referral theories tied to office leases, above-market compensation, spouse employment relationships, and benefits given to referral sources. Stark claims also continue to appear alongside Anti-Kickback Statute and False Claims Act allegations, which is where things can get painfully expensive in a hurry.
That matters because Stark problems are rarely just “technical” once the government starts calculating tainted claims. A sloppy compensation structure can turn into an FCA exposure story. A bad lease can become a repayment problem. A cozy referral relationship can become the kind of sentence no CFO wants to hear: “We may need to quantify the entire lookback period.”
2. Strict liability is still unforgiving
Healthcare leaders often focus on intent because it feels morally intuitive. Stark does not care that much about your vibe. It cares whether the arrangement fits an exception. If a contract expired and kept operating on autopilot, if a signature was missing, if compensation drifted above supportable fair market value, or if an internal formula rewarded referral generation in substance even if not in name, the analysis can turn ugly fast.
This is why Stark remains such a favorite topic in diligence and internal audits. It is less about “Did someone mean to do wrong?” and more about “Can we defend this arrangement line by line, date by date, and formula by formula?”
3. Compensation is getting more complex, not less
Physician compensation is under pressure from every direction. Health systems want access, coverage, quality metrics, retention, productivity, recruitment support, and service-line growth. Physicians want compensation models that reflect actual workload, market scarcity, call burden, and strategic value. Add wRVUs, collections, co-management payments, medical directorships, quality incentives, relocation support, technology support, and management layers, and you have a recipe for complexity wearing a nice blazer.
Complexity is where Stark thrives. Recent compliance guidance and industry programming keep returning to the same hot spots: outlier wRVU compensation, high-dollar call pay, fair market value support, commercial reasonableness, and the need to audit arrangements before they become headlines. That is not the behavior of an irrelevant statute. That is the behavior of a law sitting quietly in the corner, sharpening pencils.
The Compliance Traps That Keep Showing Up
Fair market value is necessary, but not magic
One of the most common Stark mistakes is treating a valuation report like a legal force field. Fair market value matters, but it is not the whole test. CMS has made clear that fair market value is distinct from the separate requirement that compensation not take into account the volume or value of referrals. Translation: a number can look polished and still fail if the underlying structure rewards referrals.
There is another trap here. Compensation surveys are useful, but they are not self-executing truth machines. A high percentile salary is not automatically illegal, but neither is it automatically safe. If an arrangement pays far above peers, organizations need a defensible explanation tied to actual services, market need, burden, specialty characteristics, access goals, or other legitimate business purposes. “We really wanted to keep the doctor happy” is not a legal doctrine.
Commercial reasonableness is not the same as profitability
CMS’s 2020 rule was helpful on this point. An arrangement can be commercially reasonable even if it does not generate profit for one or more parties. That was an important clarification for legitimate service lines, rural coverage models, trauma call, and access-driven strategies that make clinical sense even when the spreadsheet frowns at them.
But the key word is legitimate. Commercial reasonableness is about whether the arrangement furthers a real business purpose and makes sense given the parties and circumstances. A losing arrangement can be lawful. A senseless arrangement cannot be rescued by saying, “Well, hospitals lose money on important things all the time.” True statement, weak defense.
The volume-or-value analysis is still a minefield
CMS also clarified that compensation is considered to take into account the volume or value of referrals when the mathematical formula includes referrals as a variable and compensation correlates with them. That bright-line framing helped, but only up to a point. Real-world compensation models are rarely simple. Bonus pools, split formulas, indirect collections, service-line incentives, and internal allocations can make a model look innocent from 30,000 feet and suspicious from three feet.
If the formula rises because designated health services ordered by the physician feed the physician’s pay, compliance teams should not shrug and assume the lawyers will sort it out later. Later is where the invoice lives.
Group practice rules are still a sleeper issue
Some physician organizations have become so familiar with the in-office ancillary services exception that they treat it like background wallpaper. That is dangerous. Group practice standards remain detailed and technical, and they need to be satisfied on an ongoing basis, not just when the structure chart first looked pretty in a PowerPoint. If a group’s compensation model, distribution methodology, or operational setup drifts, the exception can become fragile.
This is one reason Stark still appears in 2026 compliance forecasting. Group practice issues can hide in plain sight. Everyone assumes the organization “has always been structured that way,” until someone asks for the documentation and the room suddenly gets very interested in the ceiling tiles.
Leases, perks, and side benefits still matter
Do not underestimate the humble office lease. Recent DOJ matters show that rent arrangements remain fertile ground for Stark scrutiny, especially where terms are not squarely within an exception or where economics look more generous than justified. The same goes for benefits that are not labeled as compensation but function like it: subsidized staff, technology support, favorable space use, excessive administrative help, or goodies dressed up as “relationship building.” Compliance people know this category well. It is technically called things that become exhibits later.
What Changed in the Modernized Ruleand What Did Not
The 2020 CMS final rule was a real update, not a decorative repaint. It created three new permanent exceptions for certain value-based arrangements, added an exception for limited remuneration to a physician, and added protection for donations of cybersecurity technology and services. It also clarified core definitions that had caused years of anxiety.
Those reforms were significant because healthcare had long argued that Stark, built for a fee-for-service world, made modern care coordination harder than it needed to be. AAMC and other stakeholders have continued to press for additional changes, which tells you something important: even after modernization, Stark still shapes how organizations design beneficial arrangements.
At the same time, the reforms did not repeal the law’s central logic. Stark still exists to prevent financial relationships from distorting medical judgment and increasing cost or utilization in ways that are not in the patient’s interest. The modernization gave the industry better tools. It did not grant a compliance hall pass.
And organizations should remember that pandemic flexibility is not permanent flexibility. CMS’s COVID-19 blanket waivers expired on May 11, 2023. Since then, parties must comply with the regular Stark framework unless a specific waiver applies. Any organization still behaving like it is April 2020 should update the playlist.
What Smart Organizations Are Doing Now
The better-run systems are not waiting for a subpoena to rediscover Stark. They are doing unglamorous, highly effective work:
- reviewing physician compensation annually rather than admiring it from a distance,
- testing formulas for hidden referral variables,
- refreshing fair market value support when duties or market conditions change,
- documenting legitimate business purpose and access rationale,
- cleaning up expired agreements and unsigned amendments,
- checking family relationships and employment ties,
- auditing group practice compliance on a continuing basis, and
- using the Self-Referral Disclosure Protocol when an issue is real and needs structured resolution.
That last point matters. CMS still maintains the SRDP as the formal route for self-disclosing actual or potential Stark violations. The existence of an active disclosure pathway is another reminder that Stark is not a historical artifact. Regulators still expect people to use it because people still need it.
So, Is the Stark Law Still a Big Deal?
Yes, but not because it is trendy. It is a big deal because it sits at the intersection of money, referrals, documentation, and federal reimbursement. It matters because modern compensation models are complicated. It matters because healthcare transactions keep getting more sophisticated. It matters because the government still brings cases. And it matters because some of the riskiest arrangements are not dramatic schemes at all; they are ordinary deals that drifted out of compliance one amendment, one lease term, or one bonus metric at a time.
The Stark Law is quiet in the way a pressure gauge is quiet. It does not need to shout. It just needs to be right.
Field Notes: What the Stark Law Feels Like in Real Life
Talk to people who actually live with Stark compliance, and you hear less legal poetry and more operational realism. For many healthcare organizations, Stark is not experienced as a courtroom doctrine. It is experienced as friction. It is the awkward pause before a compensation committee approves a new package. It is the email chain about whether the medical director agreement was signed before services started. It is the moment a valuation consultant says, “We can support most of this, but not that piece.”
In hospitals, the experience often starts with access needs. Leadership needs trauma coverage, obstetrics coverage, call coverage, service-line stability, or a specialist in a market where recruiting is somewhere between hard and mythological. The clinical case is obvious. The business case may also be obvious. The Stark case is where the room gets quieter. People start asking whether the payment is really tied to work performed, whether the arrangement is defensible if it loses money, and whether anyone can explain the formula without using three whiteboards and a support animal.
In physician groups, the lived experience is different but just as real. The challenge is often internal fairness mixed with external risk. High-performing physicians want to be paid for being high-performing. That is understandable. But once ancillary revenue, designated health services, or internal productivity pools become part of the design, leaders have to test whether the model rewards professional effort or accidentally rewards referrals. The emotional temperature can rise quickly. Physicians hear “compliance review” and sometimes think “someone is trying to cut my pay.” Compliance hears “market realities” and sometimes thinks “someone is trying to make a bad fact pattern sound inevitable.” Both sides are usually partly right and fully stressed.
Transaction teams feel Stark in another way: surprise. A target company may look polished from the outside, only for diligence to uncover unsigned renewals, expired leases rolling month to month, referral relationships involving family members, or compensation plans that were built for growth and never re-tested for legal durability. Nothing kills deal momentum quite like discovering that a “legacy arrangement” is legal code for “we have all been hoping nobody asks.”
Compliance officers, meanwhile, often describe Stark as a law of small misalignments. Rarely is the problem a giant neon sign that says FRAUD THIS WAY. More often it is the accumulation of little mismatches: duties changed but pay did not; terms changed but the amendment did not; a subsidy continued after the rationale faded; a formula kept running after the exception no longer fit. The experience is less detective novel and more plumbing leak. Ignore it long enough, and suddenly the wall is soft.
That is why the organizations that handle Stark best are rarely the flashiest. They are the ones with disciplined contract management, careful compensation governance, recurring audits, and the cultural maturity to treat compliance as infrastructure rather than theater. They know the law is quiet. They also know that quiet is not the same thing as gone.
