What Hospital General Counsels Won't Tell You About Your Consulting Indemnity Clause

You're tired after clinic. Your inbox is full. Then a "great opportunity" lands: advise a hospital, health tech startup, device company, or payer on a part-time basis. Good money. Flexible hours. A nice line on the CV. You skim the agreement, see boilerplate, and tell yourself you'll circle back later.

That's how people get burned.

I've seen physicians spend months building a consulting side gig, only to realize they signed an indemnity clause that shifted ugly legal risk onto them. Not theoretical risk. Real risk. The kind that turns one harmless-seeming advisory call into demands for defense costs, reimbursement, or liability for problems you didn't create and couldn't control.

Indemnity language is where contracts stop being friendly. It's where smiles, "partnership," and talk about innovation get replaced by a very simple question: if something goes wrong, whose wallet is on the hook?

If you do consulting on the side, this matters to your medical career for three reasons:

• It can wipe out the economics of the deal. A side gig isn't a side gig if one claim creates five-figure or worse headaches in legal fees.
• It can spill into your day job. A badly drafted clause can trigger disclosure issues, insurance problems, and reputation damage.
• It exposes a blind spot many physicians have. We're trained to read studies and spot clinical risk. Contract risk? Different battlefield.

The mistake is assuming indemnity is routine boilerplate you can safely ignore. It isn't. It's one of the most dangerous paragraphs in the whole agreement.

This article is for educational purposes only. It is not financial advice, not legal advice, and not tax advice. Figures vary, and you should consult a qualified professional.

Introduction

Physicians are often flattered into bad contracts. That's the truth. A hospital or company says they value your expertise, sends over an agreement, and wraps the risky parts in polished language: "customary," "standard," "mutual protection," "market." Those words mean nothing if the indemnity clause is lopsided.

Here's what hospital general counsels usually won't say plainly: their job is to protect the institution, not you. That's not evil. It's their job. But your mistake is expecting them to point out where the contract quietly makes you responsible for losses tied to the hospital's own conduct, third-party claims, broad allegations, regulatory issues, or work product used in ways you never approved.

And yes, this comes up often in physician side hustles. Medical advisory work. Chart review. Protocol design. Expert input on workflow. Speaking or education tied to operational changes. Even "just a few calls a quarter." I've seen indemnity traps buried in all of it.

The language is often sneaky in one of two ways:

• It's absurdly broad. You indemnify them for "any and all claims arising out of or related to" your services.
• It sounds balanced but isn't. There's "mutual indemnification," but their obligation is narrow and yours is expansive.

If you remember one thing, remember this: indemnity is not just about who was actually wrong. It's about who has to step in, pay, defend, and fight. Huge difference.

The Core Challenge

The core challenge is simple: physicians underestimate how broad indemnity clauses can become once lawyers and insurers start reading them aggressively.

A lot of doctors glance at the clause and think, "Well, I won't do anything negligent, so I'm fine." Wrong. That's the first mistake. Some indemnity clauses aren't limited to your negligence. They're triggered by claims merely "arising from" your services. That phrase is a legal swamp.

Here are the most common pitfalls I see.

1. Agreeing to indemnify for more than your own negligence

This is the classic bad clause. It may say you indemnify the hospital for claims, damages, losses, penalties, and attorney fees "arising out of or relating to" your consulting.

That's too broad.

Why? Because it can reach:

• Alleged errors made by others after relying on your advice
• Operational decisions you didn't control
• Regulatory fallout from how the hospital implemented your recommendations
• Claims that name everyone in sight, whether or not you actually caused the harm

If the clause isn't limited to your negligent acts, willful misconduct, or breach of contract, you're standing in a dangerous place.

2. Missing the duty to defend

Indemnify is bad enough. Defend can be worse.

Some clauses require you not only to reimburse losses later, but to step in and pay for legal defense from the beginning. That means paying lawyers before liability is even established. Before facts are sorted out. Before fault is clear.

Don't miss this mistake. A duty to defend can turn a small consulting deal into an immediate financial drain.

3. Ignoring uncapped liability

Many side-gig agreements pay modestly but impose uncapped indemnity exposure. That's nonsense, and yet physicians sign it all the time.

If you're being paid modest consulting fees, your exposure should not be limitless. Period.

Watch for:

• No cap on liability
• Cap that excludes indemnity, making the cap meaningless
• Language that includes indirect, consequential, special, or punitive damages

That's contract poison unless heavily negotiated.

4. Assuming malpractice insurance covers consulting indemnity

Usually, physicians assume, "My malpractice policy will handle it." Dangerous assumption.

Your clinical malpractice policy may not cover:

• Non-clinical consulting work
• Contractual indemnity obligations
• Regulatory investigations
• Intellectual property claims
• Business losses tied to your recommendations

I've seen doctors discover this only after the problem started. Terrible time to learn.

5. Overlooking who controls the defense and settlement

If a claim comes in, who picks the lawyer? Who decides whether to settle? Can the hospital settle in a way that harms your reputation or licensing position, then send the bill your way?

These details matter. A lot.

You want clarity on:

• Who controls defense
• Whether your consent is required for settlements affecting you
• Whether separate counsel is allowed if interests diverge

Without that, you can get dragged behind decisions made for the institution's convenience, not your protection.

6. Letting "mutual indemnity" fool you

I'm skeptical every time I hear "don't worry, it's mutual."

Read the actual words. Their indemnity might cover only bodily injury caused by the hospital's gross negligence. Yours might cover all claims related to your services, breach, statements, deliverables, or even alleged noncompliance with law.

That's not mutual. That's cosmetic symmetry hiding a bad deal.

7. Forgetting downstream use of your advice

This one is common in innovation work. You provide limited strategic input. Then the organization scales, modifies, or operationalizes your suggestions in ways you never reviewed. Months later, there's a problem. Guess whose name is in the file.

Your contract should make clear:

• Your advice is limited to the scope of engagement
• Final operational decisions are theirs
• They remain responsible for implementation, compliance, supervision, and patient care

If that's not spelled out, don't act surprised when blame expands.

How to handle this correctly

Here's the cleaner approach. Not perfect. But far safer.

Push for indemnity language that is:

• Narrowly triggered
  • Only by your negligence, willful misconduct, or material breach
• Not a duty to defend
  • Reimbursement after final determination is safer than front-end defense duty
• Mutual in a real way
  • If they want your indemnity, they should indemnify you for their negligence, implementation choices, and legal violations
• Capped
  • Ideally tied to fees paid under the agreement or another negotiated limit
• Paired with insurance review
  • Never assume coverage
• Clear on control
  • No settlement affecting you without your written consent

Here's the decision logic I tell physicians to use:

Actionable Next Steps

Don't just "be careful." That advice is useless. Use a process.

Step 1: Find the clause and isolate the trigger words

Search the contract for:

• indemnify
• defend
• hold harmless
• arising out of
• relating to
• claims
• losses
• attorney fees

Then mark every trigger phrase. If the clause reaches beyond your own negligence or breach, it needs work.

Step 2: Check if the obligation is one-way or fake-mutual

Ask:

• Do both sides indemnify?
• Are the triggers equally broad?
• Are the types of covered losses similar?
• Is one side's obligation effectively unlimited?

Don't be fooled by formatting. Two paragraphs can still be wildly unfair.

Step 3: Compare indemnity to the liability cap

This is where many physicians get trapped.

Look for a limitation-of-liability section and ask:

• Is there a cap?
• Does the cap apply to indemnity?
• Are defense costs included or excluded?
• Are consequential damages waived?

If indemnity is excluded from the cap, the cap may be mostly decorative.

Step 4: Verify insurance before you sign

Not after. Before.

Ask your insurance broker or coverage counsel:

• Does my current policy cover this consulting work?
• Does it cover contractual indemnity?
• Does it cover defense obligations?
• Are regulatory or privacy-related claims excluded?
• Do I need a rider or separate policy?

I've seen physicians assume they were covered because the work "used medical knowledge." That's not how insurers think.

Step 5: Clarify scope and implementation responsibility

Your agreement should say what you are and are not doing.

Good protective language usually separates:

• advisory input from clinical decision-making
• recommendations from implementation
• educational services from operational control

This matters because vague scope expands blame.

Step 6: Use a lawyer who does physician-side contract review

Not your cousin who handles real estate closings. Not a general business lawyer who dabbles. Use someone who understands physician consulting, healthcare contracts, and liability allocation.

You want someone who knows the difference between:

• clinical exposure
• business risk
• healthcare regulatory spillover
• institution-drafted "standard" tricks

And yes, I'm opinionated here: this is money well spent. Far better than pretending you saved money by signing blind.

Step 7: Ask for concrete revisions

Don't send vague pushback. Give exact asks:

1. Limit indemnity to your negligence, willful misconduct, or material breach.
2. Remove any duty to defend.
3. Add a mutual indemnity from the company or hospital for its own acts, omissions, and implementation decisions.
4. Apply the liability cap to indemnity.
5. Exclude consequential, special, and punitive damages where possible.
6. Require your written consent before any settlement that admits fault on your behalf or affects licensure, reputation, or reporting obligations.

That's the adult version of contract review. Specific, calm, and firm.

Step 8: Know when to walk away

This is the part physicians hate. But it matters.

Walk if:

• They insist on broad one-way indemnity
• They refuse to narrow "arising out of" language
• They demand a duty to defend
• They offer small compensation with massive exposure
• They brush off your concerns with "everyone signs this"

"Everyone signs this" is a sales tactic, not a legal argument.

Useful resources

Use these intelligently:

• A healthcare attorney who routinely represents physicians
• Your malpractice carrier or broker
• Professional association contract review resources
• Your state medical society's legal referral network
• A plain-language checklist you keep for every side gig

Here's a simple checklist format worth saving:

• Scope of work defined?
• Indemnity narrow?
• No duty to defend?
• Real mutuality?
• Liability cap applies?
• Insurance confirmed?
• Settlement consent protected?
• Lawyer reviewed final version?

Summary

The consulting indemnity clause is where "nice opportunity" turns into hidden liability. Don't make the classic physician mistake of treating it like harmless boilerplate. It's not boilerplate. It's the paragraph that decides who bleeds when something goes wrong.

Be prepared. Focus on the high-yield areas. That means reading for trigger language, spotting the duty to defend, checking whether indemnity blows past the liability cap, and confirming insurance with an actual professional before you sign.

My position is simple: if a hospital or company wants your expertise, they don't get to offload open-ended legal risk onto you as the price of admission. Bad contracts count on physician fatigue, ego, and haste. Don't hand them that advantage.

Slow down. Redline the clause. Get real review. And if the indemnity language stays ugly, walk. That's not paranoia. That's how you protect your career.