A group of professionals seated at a table, reviewing documents related to Stark Law exceptions.

A Practical Guide to Stark Law Exceptions for Medical Group Practices

Stark Law exceptions are the narrow legal pathways that let your medical group make physician referrals for designated health services without violating the federal self-referral ban. If your practice owns ancillaries, uses in-house imaging or lab services, or pays physicians through bonuses and medical director arrangements, you need to understand exactly where the line sits.

What Stark Law Exceptions Mean for Medical Group Practices

Stark Law exceptions are technical safe pathways, not flexible business judgments. If your arrangement meets every required element, the referral is permitted. If one element fails, the exception fails with it, even when the service is legitimate, the price is fair, and the clinical need is obvious.

For medical group practices, that matters because Stark reaches the ordinary parts of practice operations. A referral from a physician to a practice-owned MRI suite, a therapy department, a lab, or a home health entity all trigger the same basic question: does a financial relationship exist, and if so, does a valid exception cover it? The answer has to be yes before the referral starts, not after an audit begins.

Why Exceptions Matter to Group Practices

Exceptions determine whether your group can lawfully keep ancillaries in-house, compensate physicians in a way that rewards productivity, and hold ownership interests in related entities. A missed technical requirement can turn a standard operating model into a prohibited referral relationship.

That risk is not theoretical. A bonus plan tied to the wrong measure, a lease that fails commercial reasonableness, or an ancillary service furnished from the wrong location can break the exception. If your practice runs multiple service lines, the compliance burden grows quickly, which is why a disciplined Healthcare Compliance Program belongs at the center of the business structure, not on the side of it.

Stark Law vs. Anti-Kickback Law

Stark and anti-kickback are related, but they are not the same law. Stark focuses on physician referrals and financial relationships. Anti-kickback focuses on whether something of value is offered or received to induce referrals. In practice, your arrangement often has to satisfy both frameworks at once.

That distinction matters because a deal can be perfectly structured under one law and still fail under the other. Stark is strict liability, so intent does not rescue a bad structure. Anti-kickback analysis adds a separate layer, especially for referral agreements, medical directorships, and ownership interests. For that reason, any physician compensation or ancillary-service arrangement deserves review under Anti-Kickback Statute Compliance at the same time you test Stark.

How Stark Law Works Before Any Exception Applies

Before any exception applies, Stark starts with a ban. A physician may not refer Medicare or Medicaid patients for designated health services to an entity with which the physician, or an immediate family member, has a financial relationship unless a valid exception covers the arrangement. That is the baseline rule, and every exception is built on top of it.

You should think of the statute like a locked door with very specific keys. The relationship may be commercial and ordinary, but if the key does not match the lock exactly, the door stays closed.

Financial Relationships That Trigger Risk

Stark reaches ownership or investment interests and compensation relationships. Ownership is the most obvious form, but compensation is often where practices get trapped. A lease payment, a profit-sharing formula, a medical directorship, or a productivity bonus can all create a financial relationship.

Indirect arrangements matter too. A physician may not hold formal equity in the billing entity, yet still have an economic interest through a layered ownership structure, management company, or distribution vehicle. Regulators look at substance, not labels. If money moves in a way that links referrals and compensation, you need an exception analysis before the arrangement goes live.

Designated Health Services You Must Track

The common designated health services relevant to medical groups include clinical lab services, imaging and radiology, physical and occupational therapy, durable medical equipment, home health services, prescription drugs, and hospital services. If your practice touches any of those service lines, your referrals and billing workflows need clear Stark review.

That list matters because a practice often assumes only major hospital referrals create exposure. They do not. A physician group with in-office lab testing or imaging carries direct Stark risk every time a patient is ordered into that service line.

What Counts as a Referral

A referral is broader than a formal written send-out. Ordering a designated health service from an entity in which a financial relationship exists is the core trigger. In a group practice, that covers employed physicians, partners, and physicians acting under medical director or co-management arrangements.

The practical question is simple: does a physician use clinical authority to direct a patient to an affiliated DHS entity, and does the physician or family member have a financial relationship with that entity? If yes, Stark applies unless an exception fits exactly. That is why referral workflows and contract reviews should sit beside your Physician Employment Contract Review process, not after it.

The Group Practice Requirement You Must Satisfy First

The most useful Stark protections for medical groups depend on qualifying as a bona fide group practice. If the practice fails that threshold, the in-office ancillary services exception and several compensation protections become unavailable or severely limited.

CMS treats group status as an operational reality, not a paperwork label. A shared tax ID does not make you a group practice. Integrated clinical and financial operations do.

The 75% “Substantially All” Test

A group practice must satisfy the “substantially all” test, meaning at least 75% of patient-care services are personally furnished by group physicians. That requirement shows the practice functions as a real clinical enterprise, not a loose collection of independent doctors under one roof.

This test is often misunderstood because it is easy to focus on ownership or branding. Those things do not matter enough. What matters is how the physicians actually deliver care and whether the practice truly operates as one integrated unit.

Single Legal Entity and Integrated Operations

The group practice must be a single legal entity with coordinated clinical and financial operations. CMS has also recognized that a wholly owned subsidiary can fit within a single-entity structure when the practice remains integrated, as reflected in CMS Advisory Opinion 2021-01. The point is not whether the structure is tidy on paper. The point is whether it functions as one enterprise.

If your practice has multiple entities, shared ancillary companies, or related management structures, the entity chart is only the starting point. Your compliance team has to trace who bills, who owns the assets, who supervises the service, and how profits move through the structure.

Why Group Structure Drives Exception Eligibility

Group status drives eligibility for the in-office ancillary services exception, affects profit allocation, and shapes compensation design. If the group structure is defective, downstream exceptions collapse with it. A practice cannot fix a bad structure by drafting a clever compensation clause.

This is where structural diligence pays off. A practice that understands its entity map, physician rosters, and service lines can align arrangements correctly from the beginning. A practice that guesses usually ends up revisiting the file under pressure, which is the wrong time to discover that the structure never supported the exception.

The In-Office Ancillary Services Exception

The in-office ancillary services exception is the most important Stark Law exception for medical group practices. It allows referrals for certain ancillary services furnished within the practice, but only if the supervision, location, and billing rules are satisfied exactly.

Used properly, IOAS supports efficient patient care. Used loosely, it becomes one of the most common sources of Stark exposure.

The Three Core IOAS Requirements

IOAS stands on three requirements: supervision, location, and billing. Fail any one of them and the exception fails, even if the service is common, useful, and fully documented clinically.

That is why an in-office lab or imaging suite is not automatically compliant simply because it sits near the exam rooms. The service must be supervised at the required level, furnished from a qualifying location, and billed in the required manner. The compliance analysis has to follow the service from order to claim.

Supervision Rules

The supervising physician must satisfy the applicable supervision standard for the service, and that standard must align with the relevant DHS and billing rules. Internal policy alone is not enough. If the service requires direct or general supervision under the applicable framework, your staffing model has to match that requirement.

A common failure point is assuming credentialed staff can run the ancillary department without a clear supervision structure. That assumption creates risk immediately. Supervision should be written, operationalized, and auditable.

Location Rules

IOAS also depends on where the service is furnished. The “same building” and centralized building rules control whether the ancillary service sits close enough to the referring practice to qualify. Satellite offices and shared spaces deserve special scrutiny because a physically convenient location does not necessarily satisfy the rule.

The mistake here is treating the building test as informal. It is not. Your lease map, suite layout, signage, and patient flow all matter because they prove where the service is actually furnished.

Billing Rules

The referring group must bill the DHS claims in the manner required by the exception. Billing by the wrong entity or through the wrong reassignment structure can break IOAS. The billing process should track who furnished the service, who supervised it, and which legal entity submitted the claim.

If your practice outsources billing, the vendor still needs precise instructions. Outsourcing does not outsource Stark liability. Your billing controls should be reviewed the same way you would review Medicare Billing Audit readiness, because the claim mechanics are part of the exception itself.

Common IOAS Uses in Medical Group Practices

IOAS is commonly used for lab testing, imaging, and therapy. Those services create clear clinical value, reduce patient friction, and keep care coordinated. They also draw regulatory attention because they generate independent revenue streams tied directly to physician referrals.

That combination is exactly why your compliance file needs to be clean. If your practice keeps these services in house, document the group-practice analysis, supervision model, building analysis, and billing workflow before the first claim goes out.

Where Practices Commonly Fail IOAS

The recurring failures are predictable. Supervision is wrong. The building analysis is stale. The ancillary asset sits in a separate ownership vehicle without proper analysis. Billing is performed by an entity that does not match the exception structure. The practice assumes convenience equals compliance, and it does not.

The safest approach is to review IOAS as a working system, not a legal slogan. If your facts change, your exception analysis changes too.

Compensation Exceptions for Physician Arrangements

Compensation exceptions matter because most physician group practices pay doctors in ways that would otherwise create Stark risk. Employment agreements, medical director contracts, call coverage, and professional services all need a valid compensation exception.

The same rule applies across each structure: written terms, fair market value support, commercial reasonableness, and no referral-based compensation.

Personal Service Arrangements

The personal service arrangements exception covers written service contracts with specific terms, a set duration, defined services, commercially reasonable terms, and compensation that does not vary with referrals. It is a workhorse exception for specialty practices, administrative duties, and part-time physician service roles.

The contract has to exist before the services begin. You cannot patch the record later and expect the exception to hold. If the arrangement changes, amend it prospectively and document the business reason.

Employment Relationships

Employment compensation can fit the employment exception, but the compensation structure still matters. Salary, bonus, and productivity formulas must be designed so they do not reward referrals. Work relative value units and other legitimate productivity metrics are common tools, but they must be applied carefully.

The practical question is whether the compensation reflects bona fide services or hides a referral incentive inside the pay plan. If your physician payroll depends on downstream DHS volume, the review should be treated as part of your broader Medical Director Agreement Compliance and employment oversight process.

Fair Market Value Compensation

Fair market value, or FMV, means compensation consistent with arm’s-length market terms for the actual services or assets involved. FMV helps support leases, medical directorships, call coverage, and other physician arrangements. It does not save a bad structure by itself.

That distinction matters. A payment can be FMV and still fail Stark if the arrangement does not fit the right exception or if the compensation varies with referrals. FMV is necessary in many cases, but it is not a complete defense.

Payments by a Physician

The payments by a physician exception gets less attention than it deserves. It can support arrangements where the physician pays the entity, including certain timeshare-style structures. For groups that need temporary office access, equipment access, or defined use of space, this exception can be useful if structured correctly.

The catch is precision. You need clear payment mechanics, real use rights, and documentation that matches the actual relationship. A sloppy timeshare arrangement creates the same Stark problems as a poorly drafted lease.

Group Practice Profit Distribution After the 2020 CMS Rule

CMS tightened the group practice compensation rules in the 2020 final rule published at 85 FR 77492 on December 2, 2020. Most of the rule became effective January 19, 2021, and the amendment affecting group-practice compensation methodology became effective January 1, 2022. The key change is simple: group practices must allocate profits, not revenues, from DHS.

That change matters because it closed a common workaround. Practices can no longer slice service-line revenue in a way that masks referral-driven economics.

Why CMS Changed the Profit Allocation Framework

CMS changed the framework to reduce manipulation of service-line profits and align allocations with real economic performance. The rule reflects a straightforward policy choice, if a practice earns DHS profits, those profits need to be allocated in a way that fits the current Stark structure.

The regulatory message is clear. Creative labeling does not change economic reality. If your profit-sharing plan was built on older flexibility, it needs to be reviewed now, not later.

The “Overall Profits” Rule

If your practice wants to use the “overall profits” concept, it must aggregate all DHS profits from the group or from a component of at least five physicians. That means you cannot isolate one service line and distribute it differently if that service line sits inside the relevant profit pool.

For smaller groups, the analysis is still possible, but it has to be done through a compliant methodology. The size of the group does not eliminate the rule. It only changes how you evaluate the pool.

Components of at Least Five Physicians

CMS allows separate components of at least five physicians, and each component can use a different allocation methodology. That flexibility is useful for larger groups with distinct clinical divisions. It is not a license to vary methodology inside the same component.

This is where many practices get into trouble. Once the component is defined, the allocation method has to stay consistent within that component. Service-line-by-service-line tinkering inside the pool does not pass muster.

Prohibited Allocation Methods

A group may not distribute profits from different DHS service lines using different methodologies inside the same relevant group or component. CMS also prohibits using ordering patterns for non-Medicare DHS patients to allocate Medicare DHS profits. That rule shuts down a common attempt to disguise referral-based distribution under a mixed-payer analysis.

If your finance team uses multiple compensation formulas, the formulas need Stark review before implementation. A clean paper trail is not optional, and the methodology must match the current rule, not the one your predecessor used.

Practical Compensation Review Questions

Before approving any compensation plan, ask a few hard questions. What profits are being allocated? Who is in the relevant pool? Is the methodology set in advance? Does the structure reflect the post-2020 CMS rule?

If those answers are not documented, the plan is not ready. A practice that wants to avoid overpayment disputes and referral scrutiny should treat compensation review like a formal control, not a finance shortcut.

Referrals, Ownership, and Investment Interests

Ownership interests are a major Stark trigger because they connect physician referrals to the economics of the entity receiving the referral. If a physician owns part of the lab, imaging entity, therapy company, or DME supplier, that ownership has to be analyzed before any referrals begin.

The same is true for indirect interests. Layering does not erase Stark exposure.

Direct Ownership Interests

Direct ownership means equity, partnership, or membership in the entity furnishing DHS. If your physicians own the ancillary provider directly, every referral to that entity needs a valid exception. The investment cannot sit on autopilot.

The safe course is to review ownership documents before the first distribution, not after claims are submitted. That review should cover buy-ins, capital calls, exit rights, and distribution formulas.

Indirect Ownership Interests

Indirect ownership can arise through management companies, holding entities, distribution waterfalls, or layered affiliates. Stark analysis follows the economic path. If the physician benefits financially from referrals through a chain of entities, the interest still matters.

This is where entity charts can mislead. A formal structure may look disconnected, but the money flow often tells a different story. Regulators care about that second story.

Why Ownership Structures Need Advance Review

Ownership changes need review before implementation. Recapitalizations, new investor entries, and phantom equity arrangements all alter the Stark analysis. If you wait until after the deal closes, the problem becomes harder and more expensive to fix.

Advance review is the only practical method. Once claims are submitted under a bad structure, the exposure spreads quickly.

Exceptions Commonly Used Outside the Core Medical Group Model

Not every physician relationship lives inside the in-office ancillary model. Practices also rely on lease arrangements, recruitment support, incidental benefits, and charitable or community-based relationships. These are common, but each one has its own narrow exception.

Rental of Office Space and Equipment

The lease exceptions require a written agreement, set term, FMV, commercial reasonableness, and rent that does not vary with referrals or DHS profitability. The arrangement must exist because it makes business sense, not because the landlord expects downstream referrals.

A lease that is below market, indefinite, or routinely amended without review creates immediate exposure. Use the same discipline you would apply to any regulated contract, because the statute treats it that way.

Medical Staff Incidental Benefits and Non-Monetary Compensation

Incidental benefits and non-monetary compensation exceptions protect narrow, low-value items, such as modest meals or limited perks in provider settings. The dollar limits and tracking rules are strict. If you exceed the cap or fail to record the benefit, the protection disappears.

That sounds small, but these exceptions matter because small items often accumulate unnoticed. A practice that wants to stay clean needs a system for tracking them.

Recruitment and Physician Loan Support

Recruitment arrangements support physician placement in a service area, but they need careful drafting, geographic analysis, and repayment terms. Loan support and income guarantees are common, yet they must fit the exception exactly.

These deals are often negotiated under pressure to fill coverage gaps. Pressure is not a compliance defense. The paperwork has to lead the business decision, not follow it.

Charitable Donations and Community-Based Arrangements

Charitable support needs special scrutiny when physicians influence placement, funding, or beneficiary selection. A donation can become a problem if it operates like a quid pro quo for referrals or access. Keep the charitable purpose distinct from any referral relationship.

If the structure starts to resemble a backdoor business benefit, stop and review it. Regulators will not treat it as charity if the economics say otherwise.

Why Stark Exceptions Fail in Real Practices

Most Stark failures are not caused by bad intentions. They are caused by missing elements, stale documents, or compensation plans that drift away from the paper file.

Missing or Improper Written Agreements

Unsigned agreements, expired terms, backdated paperwork, and incomplete service descriptions break exception protection. If the contract does not accurately reflect the actual deal, your file is vulnerable.

You need contemporaneous documentation. If the relationship changes, update the agreement before the change takes effect.

Compensation That Varies With Referrals

Compensation tied to referrals, volume, or downstream DHS profitability usually fails Stark. That includes obvious formulas and disguised ones. If a bonus structure rewards a doctor for steering patients into an ancillary service line, the exception problem is immediate.

A compliant pay plan rewards legitimate work, not referral leverage.

Lack of Commercial Reasonableness

Commercial reasonableness means the arrangement makes business sense even without referrals. If you would not keep the lease, medical director role, or staffing arrangement except for the referral stream, your structure is vulnerable.

That test is practical, not abstract. Ask whether the arrangement stands on its own operationally. If it does not, rewrite it.

Inadequate FMV Support

FMV support should include market data, valuation methodology, and approval records. A bare assertion that the payment is “fair” does not satisfy the file requirement.

Without support, both Stark and broader fraud-and-abuse scrutiny intensify. If a compensation arrangement appears generous without documentation, regulators assume the worst.

Structuring Around the Rule

Layering entities, using shell companies, or redefining service lines does not avoid Stark. Regulators look at the economic reality. If the arrangement still connects physician referrals to financial gain, the labels do not matter.

That is the practical lesson here. Compliance is not about cleverness. It is about alignment.

Documentation and Audit Controls Your Practice Needs

If you want Stark exceptions to hold up, document the entire analysis. That means contracts, valuation support, billing rules, supervision logs, and the internal approvals that show how the deal was built.

A strong compliance file is not defensive theater. It is the evidence that your practice planned correctly from the start.

Core Documents to Retain

Retain signed contracts, amendments, valuation reports, board or committee approvals, referral analyses, billing policies, and supervision logs. Each record supports a different exception element, and together they show that the structure was deliberate.

You should also keep entity charts and service-line maps. When a regulator asks how the arrangement worked, those documents shorten the answer and reduce confusion.

Monitoring Compensation and Referral Patterns

Compensation and referral patterns need routine review. Look for unexpected productivity spikes, year-end true-ups that create referral sensitivity, and service-line changes that alter the underlying economics.

This is a good place to align Stark monitoring with False Claims Act Defense efforts. Once compensation and billing distort each other, overpayment and false claim exposure often travel together.

Policy Controls for Multi-Site Practices

Multi-site practices need location-specific controls. Each site should be analyzed separately for IOAS location rules, staffing, and billing mechanics. Satellite offices and shared suites create recurring confusion, so you need clear site-level records.

Do not assume a compliant main office automatically covers every affiliated location. It does not.

Internal Escalation and Corrective Action

If you spot a suspected exception failure, freeze the arrangement, preserve records, and escalate it to legal and compliance review. Then determine whether repayment, contract correction, or voluntary disclosure is required.

If the issue touches federal reimbursement, consider the Voluntary Self-Disclosure Protocol before the problem expands. Early containment is always cheaper than late repair.

Enforcement Risks and Financial Consequences

Stark noncompliance carries real financial exposure. The statute is strict liability, so a mistake does not become harmless just because no one intended to break the rule.

Payment Denial and Refund Exposure

Claims tied to prohibited referrals can be denied or require repayment. The OIG position is harsh, claims submitted in violation of Stark can require repayment of the entire claim amount, even if the service was medically necessary.

That means a bad referral relationship can taint the claim itself, not just the excess profit. The exposure is larger than most practice owners expect.

Civil Monetary Penalties and Exclusion

Stark violations can trigger civil monetary penalties of up to $15,000 per service, plus $100,000 fines for circumvention schemes. Serious conduct can also lead to Medicare and Medicaid exclusion.

Those penalties are why quick internal review matters. Once the file becomes an enforcement matter, the cost of delay rises fast.

State Law and Payer Contract Consequences

State self-referral laws can impose separate restrictions, and commercial payers often reserve audit and recoupment rights in contract language. Even if the federal issue looks limited, the broader reimbursement impact is not.

If your practice receives a demand letter, the response should treat federal, state, and payer exposure as connected issues. That is where a Healthcare Regulatory Attorney becomes valuable, because the response strategy has to match the full legal picture.

How to Build a Stark Compliance Program for Your Practice

A Stark compliance program starts with structure, not reaction. Your goal is to identify every financial relationship, match it to the correct exception, and keep the documentation current as the practice changes.

Step 1: Map Every Financial Relationship

Inventory ownership interests, compensation plans, leases, medical directorships, call coverage, and ancillary service lines. If you cannot see the relationship map, you cannot assess the exception.

This inventory should include physicians, immediate family members, related entities, and any service company that participates in referrals or payments. No blind spots.

Step 2: Match Each Arrangement to the Correct Exception

Every arrangement needs a specific exception analysis before launch or renewal. Do not rely on habit or past practice. The exception must fit the facts, not the other way around.

Use a consistent review checklist so finance, compliance, and legal teams are applying the same standard every time.

Step 3: Standardize Contract Review

Centralize contract review with legal, compliance, and finance sign-off. Template language should reflect current CMS rules, especially for compensation methodology and profit allocation.

This is also where a Healthcare Regulatory Attorney can help you stop outdated forms from staying in circulation after the law has changed.

Step 4: Reassess Annually and on Material Change

Annual review is not enough by itself, but it is the minimum baseline. Reassess after ownership transfers, compensation changes, new ancillary lines, new locations, or practice acquisitions.

Material change creates new Stark facts. When the facts change, the analysis changes.

Practical Questions Medical Group Practices Should Ask

Before you sign a deal or bill a DHS claim, ask the hard questions. If the answer is not documented, your compliance posture is weak.

Does Your Practice Qualify as a Group Practice?

Check the 75% test, entity structure, and operational integration. If group status is shaky, do not assume IOAS or profit-allocation protections apply.

Does the Arrangement Fit a Specific Exception?

Identify the exact exception and verify every element. “Almost compliant” is not a category in Stark.

Can You Prove FMV and Commercial Reasonableness?

Ask whether the arrangement survives without referral volume. If it does not, the structure needs revision.

Are Your Billing and Supervision Practices Consistent With the Paperwork?

Match real-world operations to the contract. If the paperwork says one thing and the workroom says another, the problem is already live.

Common FAQs About Stark Law Exceptions

Is IOAS always available to a medical group?

No. IOAS applies only when the practice qualifies as a group practice and satisfies the supervision, location, and billing rules. If one element is missing, the exception fails.

Can you split DHS profits by service line?

Not within the same relevant group or component under the current CMS framework. DHS profits must be allocated using a compliant methodology that follows the post-2020 rule.

Does a fair market value opinion guarantee compliance?

No. FMV support helps, but it does not replace the need to fit a specific Stark exception. The arrangement still has to avoid referral-based compensation and satisfy all required elements.

What happens if you find a problem after implementation?

Stop the arrangement if needed, preserve the record, quantify the exposure, and obtain legal review immediately. Then decide whether repayment, contract correction, or disclosure is required.

Does Stark apply if services are medically necessary?

Yes. Medical necessity does not cure a prohibited referral relationship. If the financial structure fails, the claim remains exposed.

Do state laws matter if you are already reviewing Stark?

Yes. State self-referral laws, payer contracts, and fraud rules can create separate liability even when the federal analysis is only part of the problem.

What a Compliant Stark Review Looks Like in Practice

A compliant Stark review is prospective, documented, and tied to actual operations. You do not wait for an audit to decide whether the structure works.

Before Signing

Select the exception, confirm FMV, document commercial reasonableness, and obtain legal approval before execution. The agreement should match the business model on day one.

After Signing

Monitor billing, supervision, and compensation reconciliation. If the actual operation drifts from the contract, correct it immediately.

Before Expansion or Acquisition

Any new location, service line, or acquisition needs a fresh Stark analysis. Historical compliance does not automatically carry forward into a new entity or market.

Frequently Asked Questions

What is the most important Stark Law exception for medical groups?

For most physician groups, the in-office ancillary services exception is the most important because it supports in-house lab, imaging, and therapy referrals. It only works if the practice satisfies every technical requirement.

Can a medical group rely on verbal agreements for Stark purposes?

No. Stark exceptions that depend on compensation, leases, or personal services require written documentation. Verbal terms do not protect the arrangement.

Why does group practice status matter so much?

Because many Stark protections, especially IOAS and group compensation rules, depend on the practice qualifying as a real group practice under CMS rules. If group status fails, the exception analysis changes immediately.

Is fair market value enough to satisfy Stark?

No. FMV is one part of the analysis, not the whole defense. The arrangement still has to fit a specific exception and avoid compensation tied to referrals.

What is the biggest compliance mistake practices make?

Treating Stark as a contract formality instead of an operational rule. The actual supervision, billing, ownership, and compensation structure must match the paper file.

How often should your practice review Stark arrangements?

Review them before execution, after any material change, and on a scheduled annual basis. If the business model changes, the Stark analysis changes with it.

Understanding the Rule Before You Expand

Stark Law exceptions are narrow on purpose. That is the point. If your medical group wants to keep ancillaries in-house, pay physicians correctly, and avoid referral-related exposure, your structure has to fit the exception first and the business preference second.

Once you understand that, the compliance question becomes much clearer. You are not looking for a loophole. You are confirming that your practice’s financial relationships match the exact legal pathway that makes the referrals lawful.

References

Scroll to Top