Medical Professional Liability

Group Practices & Clinics

Entity and provider coverage for multi-provider practices — structured so a single claim does not take the whole organization’s limit with it.

The problem

A practice is not a group of individual policies stapled together.

Once a practice has more than a handful of providers, the interesting questions stop being about any one physician's limit. They become structural: does the entity carry its own coverage, or is it riding on the providers' limits? Do providers share an aggregate? What happens when a partner leaves, a locum covers for six weeks, or a new associate starts before the paperwork clears?

These are the places where practices discover gaps — usually during a claim, occasionally during a credentialing audit, and almost always in a way that costs more than getting it right would have.

RiskLinx places entity and provider professional liability for group practices and clinics, and structures the program so that adding and removing providers is a routine administrative step rather than a coverage event.

Coverage highlights we push for

  • Entity coverage in the practice’s own name, distinct from individual provider limits
  • Separate provider limits where a shared aggregate would put the group at risk
  • Slot positions so provider turnover does not require re-underwriting the program
  • Locum tenens and per-diem coverage arranged in advance rather than retroactively
  • Separate limits for supervised advanced practice providers
  • Clean prior acts continuity when partners join or depart
  • Cyber liability sized to the actual patient record count, not a default sub-limit
  • Employment practices liability and employee benefits liability coordinated with the program

Structure

Structural decisions worth getting right once

Entity versus provider limits
If the practice entity is named in a suit but carries no limit of its own, it defends out of the providers' coverage. Separate entity limits keep the organization's exposure from consuming the clinicians' protection.
Shared versus separate aggregates
A shared aggregate is cheaper and creates a queue: the first severe claim can exhaust the pool for everyone. Separate limits cost more and remove that dependency. Which is right depends on provider count, specialty mix and claims history — and it should be a decision, not a default.
Slot positions
Coverage attached to a role rather than a named individual. For practices with regular turnover, slots dramatically reduce the administrative friction and the gap risk of every hire and departure.
Locum tenens and per-diem providers
Temporary coverage providers are a routine exposure and a routine omission. Whether the locum carries their own policy, and whether it names the practice, should be confirmed before the first shift.
Partner additions and departures
Every arrival is a prior acts question and every departure is a tail question. Handled at the time, both are administrative. Handled afterwards, both are expensive.
Supervised APP limits
Nurse practitioners and physician assistants sharing a supervising physician's limit concentrate risk in exactly the wrong place. Separate limits are usually the better structure at scale.
Cyber and regulatory exposure
A practice holds a patient record count that makes breach notification costs scale quickly. The embedded cyber sub-limit on a malpractice policy rarely reflects that. This is one of the most common under-insured exposures we find in group practices.
Employment practices liability
As headcount grows, employment claims — discrimination, harassment, wrongful termination, wage and hour — become a more frequent source of loss than clinical claims. EPLI belongs in the conversation.

What the engagement includes

How we run a group program

Full program assessment

Every policy the practice holds, read together rather than in isolation, so we can see where two forms overlap and where neither one responds.

Structure recommendation in writing

Entity limits, shared versus separate aggregates, slot design and retention level, with the cost of each option and the reasoning behind our recommendation.

Benchmarking against comparable practices

What similarly sized practices in your specialty mix and state carry, and what they pay for it.

Provider onboarding and offboarding

A repeatable process for adding and removing providers so nobody practices uninsured for three weeks while paperwork moves.

Claims advocacy for the entity and the providers

Including the situations where the practice's interests and an individual provider's interests are not identical.

Cyber sized to the record count

Modeled against notification, forensics, restoration and downtime at your actual scale rather than a round number.

Working with RiskLinx

Administrators should not have to be insurance experts.

Most of the practice managers we work with inherited an insurance program nobody fully documented. Our first deliverable is usually just a clear map of what exists — which policies, which providers, which limits, which dates.

From there, changing it is straightforward. Without it, every renewal is a guess.

Start here

A thirty-minute strategy call, then a written assessment of what you have now. No application required to begin.

Book a Strategy Call

Common questions

Group Practices & Clinics: straight answers

Should our practice carry entity coverage separate from provider limits?
In most multi-provider practices, yes. The entity can be named in a claim independently of any individual provider, and if it has no limit of its own, it defends out of the providers' coverage. Separate entity limits keep those exposures from competing.
What is a slot position and do we need one?
A slot attaches coverage to a role rather than a named person, so a departing provider can be replaced without re-underwriting. Practices with regular turnover, residents, or rotating coverage usually benefit. Stable practices with long-tenured providers often do not need them.
How do we handle coverage when a partner leaves?
The departing provider needs their past care covered, which means either tail coverage or acceptance of their prior acts date by a new carrier. The practice needs to confirm the departure does not disturb entity coverage or the remaining providers' limits. Both are simple if handled before the departure date.
Is our cyber sub-limit enough for a practice our size?
Frequently not. Breach notification, forensics, credit monitoring, regulatory defense and downtime scale with patient record count, and embedded sub-limits on malpractice policies are typically set well below that. We model the number for your record count and show you the gap.
Do we need EPLI as well?
Once a practice has meaningful headcount, employment claims tend to become more frequent than clinical claims. General liability and malpractice policies do not respond to them. EPLI is the policy that does.

Next step

Let's look at what you have now.

Send us your current declarations page and we will tell you what it does, what it does not, and how it compares to the market.