The short version

A mobile IV business has three distinct layers of exposure: the medicine (professional liability), the place — which is somebody's living room (general liability), and the road (commercial auto, and your personal policy almost certainly won't cover it). Two things quietly bite operators: your policy covers the procedures the carrier knows about — add NAD+ or peptides without telling them and you may have no coverage on your best-selling drip — and your medical director's malpractice policy does not cover your business. Get a broker who has actually written a mobile IV account before.

Read this before you Google anything else

Search "IV therapy insurance" and nearly every result you'll get is an insurance broker selling insurance. That's not a conspiracy — it's just how that search term monetizes. But it does mean the internet's answer to "what do I need?" is written almost entirely by people whose answer to every question is "a policy from us."

So we've deliberately sourced this guide from places that aren't selling you a policy: the Small Business Administration, the National Association of Insurance Commissioners (the association of state insurance regulators), and health care counsel. Use a broker — you'll need one — but go in knowing what you're looking for first.

The three layers of a mobile IV exposure

A clinic has patients come to it. You go to them. That single fact reshapes your risk profile, and it's why a policy designed for a med spa suite doesn't map cleanly onto a van. Your exposure sits in three places: the medicine, the place, and the road.

1. The medicine — professional liability

The anchor policy, and the one to get right first. Professional liability (malpractice) responds to claims arising from the care itself: a bad stick, infiltration or extravasation, phlebitis, an adverse reaction, a missed contraindication, inadequate screening, a documentation failure, failure to monitor. If you carry one policy, it's this one — and your medical director will very likely require it before putting their license behind your protocols.

Your medical director's policy does not cover your business

This one catches people, and it's worth stating flatly. A physician's individual malpractice policy covers them — their personal liability, for their own acts and supervisory decisions. It does not cover your company as an entity, it does not cover your techs, and it does not cover a procedure they didn't personally perform. Two different insureds, two different policies. Don't sign a medical director agreement assuming otherwise, and don't let them assume it either.

Claims-made vs. occurrence — ask which one you're buying

An occurrence policy covers incidents that happened during the policy period, whenever the claim eventually lands. A claims-made policy only responds if the policy is active when the claim is filed — which means if you switch carriers or close the business, claims from your covered years can arrive with nothing behind them. That's what tail coverage is for, and it costs money. Ask which type you're being sold, and ask what the tail would cost, before you need it.

The gap that catches growing operators

A professional liability policy covers the procedures the carrier knows about. You applied, you described what you do, and they priced and wrote a policy against that description. It is not a blank cheque for whatever you might add later.

Picture the ordinary arc of a growing IV business. You open with hydration, immunity, and a Myers. A year in, you add NAD+ because everyone's asking for it. Then peptides. Your menu grew — and nobody told the carrier.

Now a patient has an adverse reaction to a drip that wasn't on your application. The question the carrier asks isn't "were you insured?" It's "was this insured?" Insurance professionals describe exactly this as a routine path to an uncovered claim: a practice adds a service, doesn't update the policy, and the insurer denies coverage because the procedure was never scheduled.

What we can tell you, and what we can't

What we can't: tell you whether your carrier covers NAD+, high-dose vitamin C, ketamine, or peptides. You'll read confident statements online that "most carriers exclude NAD+" — and they may well be right. But the sources making that claim are, almost without exception, brokers who also sell coverage for those treatments. We're not saying they're wrong; we're saying we can't independently verify it, so we won't state it as fact. Neither should you take it as one. Verify anything you read about what is and isn't covered — including this guide — against your own policy and your own broker.

What we can: specialty insurance programs exist that market themselves specifically around these treatments. That tells you something real on its own — the market treats these infusions as non-standard. And non-standard means "ask," not "assume."

What to do: read your service menu to your broker line by line and get written confirmation for each one. Do it again every time you add a drip. "I have malpractice insurance" and "my NAD+ infusions are covered" are two different sentences, and only one of them is on your policy.

2. The place — general liability

The coverage operators skip, and the one that being mobile makes more relevant rather than less.

Malpractice covers what happens during the treatment. General liability covers the rest of your operations. As the National Association of Insurance Commissioners — the body of state insurance regulators, not a company selling you anything — describes it, commercial general liability responds to third-party bodily injury and property damage.

"Third-party property damage" sounds abstract until you picture the job. You are a service business, working inside somebody's home, surrounded by their possessions. That isn't an exotic risk profile — it is the textbook general liability scenario. The examples carriers themselves reach for are exactly this shape: a cleaner knocks over a lamp in a client's living room; a residential service breaks a window on the job; an employee damages a customer's home while working in it.

Swap the props for yours:

  • Your tech catches a bag on the coffee table and a laptop goes to the floor
  • An IV pole tips into a lamp — or into something the patient tells you was their grandmother's
  • Blood or saline goes onto a white couch, or a rug worth more than your van
  • The patient trips over your line and breaks a wrist

None of that is malpractice, and a professional liability policy is not written to answer for it.

The question to ask, not the answer to assume

Knowing what general liability is for is not the same as knowing what your policy does. Only your policy says that. So ask directly: "Does my general liability respond to property damage inside a patient's home, or only at a fixed premises?"

A great many general business policies are written with a storefront in mind. Your storefront is somebody's living room.

3. The road — commercial auto

Your business is mobile. Your techs drive to calls. And most of them drive their own cars.

A personal auto policy generally excludes business use. The SBA's guidance is blunt: if a vehicle is used primarily for business — driving to customers, hauling equipment, or being driven by employees — you belong on a commercial policy, even though it costs more. Read their overview of business insurance directly.

And it isn't only about vehicles you own. The NAIC notes that commercial auto policies carry far higher liability limits than personal ones and may cover non-owned vehicles — including employees' own cars driven for company business. That coverage has a name: non-owned auto, and a great many mobile IV operators have never heard it.

"But it's their car — am I even liable?"

Probably, and whose name is on the title matters less than you'd think. Nearly every state recognizes respondeat superior — an employer is responsible for an employee's negligence within the scope of employment — and as the legal publisher Wolters Kluwer explains in its overview of employee vehicle use, that liability reaches accidents even when employees are driving their own vehicles. The car is theirs. The errand is yours.

Operators sometimes reach for the "going and coming" rule — employers generally aren't liable for an ordinary commute. Don't lean on it. A tech driving to a patient's home isn't commuting. They're performing the work, at an address you assigned, at a time you set, with your supplies in the trunk. (Scope-of-employment rules are fact-specific and vary by state, so how a particular drive gets characterised is a question for your attorney — but a mobile visit is not a close call.)

Where this collides with worker classification

Counsel analysing the employer's non-owned auto liability endorsement describe courts asking two things: whether the vehicle was used in the course and scope of the business, and how much control the company exerted over the vehicle and its driver — with an alternative formulation turning on whether the driver was an independent contractor. (The same firm notes jurisdictions differ on how the endorsement is read.)

Control over the driver is the same question that decides employee versus contractor. Your protocols. Your dispatch. You assigning that call, at that address, at that time. Those facts do double duty — they're the classification evidence and the control-over-the-driver evidence.

So your worker classification doesn't only decide whether you owed workers' comp. It can shape whether you're liable for the crash and whether your policy responds. One question, three consequences — and it's why the classification guide isn't a separate topic from this one. (Even a genuine contractor doesn't fully close the door: negligent hiring, supervision, and entrustment are direct-liability theories that can still reach the company, depending on the state.)

The practical move: collect proof of insurance from everyone who drives to your calls — employee or contractor, annually — and ask your broker point-blank whether you carry non-owned auto and at what limits.

Legally required vs. contractually required vs. merely wise

Brokers tend to present every coverage as essential. It's more useful to sort them by who is actually making you buy it.

Legally required

  • Workers' compensation — once you have employees. The SBA notes that the federal government requires businesses with employees to carry workers' comp, unemployment, and disability insurance, and that state requirements vary on top of that. This one is not optional, and it interacts with a much bigger question — see below.
  • Commercial auto — where state law requires it for business vehicle use.

Contractually required

  • Malpractice — often not legally mandated as such, but your medical director will very likely require it before putting their license behind your protocols. So will many venues and corporate clients.
  • General liability with additional-insured language — the moment you do an event, a corporate wellness day, or a hotel visit, someone is going to ask for a certificate naming them.

Merely wise (but genuinely wise)

  • Cyber liability — you hold PHI. You run intake, scheduling, and payments through software. A breach is a HIPAA problem before it's an IT problem.
  • Umbrella/excess — sits above your other limits.

The SBA's governing principle is the cleanest rule of thumb anyone gives on this: insure against the things you couldn't pay for out of your own pocket. Everything else is a judgment call.

The workers' comp question is really a classification question

Most mobile IV operators run their techs as 1099 contractors, and true independent contractors are generally exempt from workers' compensation coverage. So the operator doesn't carry it, and the box appears to be ticked.

Here's why that's the single most dangerous assumption in this guide: whether your techs are actually contractors is not a decision you get to make by writing "1099" on an agreement. It's a legal test, applied after the fact — often on the worst possible day, when a tech is injured on a call and files a claim.

If they're reclassified as employees, you were required to carry workers' comp and didn't. The medical bills and lost wages land on the business. And an employer who failed to carry required coverage typically loses the exclusive-remedy protection that workers' comp normally provides — meaning the worker can sue you directly, uncapped, with your general liability policy standing to one side saying "employee injuries are excluded, that's what comp is for."

This deserves its own guide, and it has one

"They set their own hours, so they're 1099" is not the test, and mobile IV is a genuinely hard case — because a tech who relies on your medical director for supply access and protocols may be structurally incapable of being an independent business. We wrote the whole thing up separately: employee or independent contractor?

Read it before you decide you don't need workers' comp.

Who buys the insurance — you, or your tech?

This one comes up constantly, and there's a lot of confusion out there. The answer is actually clean, and it follows the same line as everything else in this guide: it depends on whether they're an employee or a contractor.

If they're your employee (including per diem) — you cover them

Your professional liability policy is the primary coverage for your employees. That's what it's for. A per-diem tech picking up calls is your employee, and they're covered under your policy for the work they do for you. They don't need to go buy their own to be protected on your calls.

So if a company is telling its W-2 techs to go get their own malpractice insurance as a condition of working — that's worth a second look. Either the company is confused about how its own coverage works, or it's quietly pushing a cost onto the tech that it ought to be carrying itself. Neither is a good sign.

If they're a genuine independent contractor — they carry their own, and you carry yours

A true contractor isn't your employee, which means your policy doesn't reach them. They need their own. And you should be collecting a certificate of insurance from them, naming your business as an additional insured, before they run a single call. Not after. Before.

But here's the part operators get wrong: "they carry their own" does not mean you don't need coverage. When something goes wrong, the patient's attorney doesn't pick one defendant — they sue the tech who placed the line and the company that took the booking, set the price, and sent them to the door. If your only plan is "the contractor's policy will handle it," your business is standing there with nothing.

The right posture is both: your company-level professional and general liability, and a current COI from every contractor.

And you can't have it both ways

Telling your 1099 techs to carry their own insurance is perfectly consistent with a real contractor relationship. But it doesn't buy you anything if you're controlling everything else — their supplies, their protocols, their prices, whether they can work for anyone else.

You don't get to take the contractor obligations (buy your own insurance, no benefits, no workers' comp) while exercising employer control. That's exactly the mismatch a plaintiff's attorney is looking for, and it's the subject of the classification guide.

"But my nurse has her own policy anyway" — and why that's a good thing

Plenty of experienced nurses carry personal malpractice coverage even when they're W-2 employees with perfectly good employer coverage. Operators sometimes read that as distrust. It isn't. It's experience.

Here's what a personal policy is really for, and it isn't mainly "in case I make a mistake":

  • Defending their license. This is the big one. If a complaint goes to the State Board of Nursing, an employer's malpractice policy generally won't pay to defend it — and a board investigation is the thing that can end a nursing career. The board can suspend a license while it investigates, which means the nurse loses their income at the exact moment they need to hire an attorney.
  • Whose lawyer is it, really? Your insurer is defending your company's interests. If the company's best defense ever becomes "the tech went off protocol," the tech is not the client in that room. Nurses know this.
  • The employer can decline to defend them. If a company believes the tech violated its policies, it may refuse to defend — and in some cases employers have gone further and pursued the nurse to recoup their own losses.
  • Anything outside the job. Moonlighting, volunteering, helping a neighbour — none of that is covered by your policy, because none of it is your work.
  • After they leave. Your coverage generally doesn't follow them out the door.

So the honest way to think about it: a personal policy isn't a substitute for yours, and it doesn't mean the tech thinks you're going to hang them out to dry. It's there for the day your lawyer isn't their lawyer.

And frankly, you want that. A tech with license-defense coverage is a tech who won't be financially ruined by a board complaint, won't panic, and won't spend a claim quietly wondering whose side you're on. It costs them very little and it takes nothing away from you.

What a COI actually is (and why it lapses on you)

A certificate of insurance is a one-page summary proving a policy exists: carrier, coverage types, limits, effective dates, and who's named. It isn't the policy — it's the receipt.

You'll be asked for one constantly: by a hotel before an event, by a corporate client before a wellness day, by a landlord, by a venue, by a partner platform, sometimes by a medical director. And you'll ask for them too, from every contractor you use.

The part that catches people is the expiry date. A COI is a snapshot. The policy behind it can lapse, get cancelled for non-payment, or simply expire — and the certificate in your file still looks perfectly valid. Operators discover this at the exact moment they need it not to be true.

Why we ask for one

This is exactly why an active certificate of insurance is one of the requirements for a Verified badge on Infuse Pro, and why the platform tracks the expiry date and warns you before it lapses. It isn't a hoop — it's the one document that proves, to a patient who has never met you, that there's something behind you if a visit goes wrong. A company that lets its COI quietly expire is a company that has stopped being insurable, and neither its patients nor its operators should find that out the hard way.

What to ask a broker

Bring this list. A broker who has written mobile IV before will have crisp answers; one who hasn't will improvise, and you'll hear the difference.

Bring this list
  • Have you written a mobile IV therapy account before — not a med spa, not a clinic?
  • Here is my full service menu. Confirm in writing which of these are covered and which need an endorsement — including NAD+, high-dose vitamin C, and peptides if I offer them.
  • If I add a new drip next year, what exactly do I have to do to make sure it's covered?
  • Is my professional liability claims-made or occurrence? If claims-made, what does tail coverage cost when I switch or close?
  • Does my general liability respond to property damage inside a patient's home, or only at a fixed premises?
  • My techs drive their own cars to calls. Do I have non-owned auto coverage, and what are the limits?
  • Are my 1099 techs covered under my policy, or do they need their own — and should I be collecting COIs naming my business as additional insured?
  • Will you issue certificates with additional-insured language for hotels and event venues, and how quickly?
  • Does my medical director need to be named on anything — and to be clear, their malpractice policy does not cover my business, correct?
  • What are the exclusions? Read them to me.

The quick version

  • Three layers of exposure: the medicine (professional liability), the patient's home (general liability), and the road (commercial auto)
  • General liability is the one operators skip — a service business damaging a client's property inside their home is the textbook GL scenario, and malpractice will not answer for it
  • The commercial auto gap is real: personal policies exclude business use, and most techs drive their own cars — ask about non-owned auto
  • "It's their car" is not a defense. Respondeat superior reaches employees' own vehicles, and driving to a call is the job, not a commute — though scope-of-employment rules vary by state
  • Classification shapes auto liability too — courts look at "control over the driver," the same question that decides employee vs. contractor. It's one question with three consequences
  • Your policy covers the procedures the carrier knows about. Add NAD+ or peptides to the menu and don't tell them, and you may have no coverage on the drip you sell most of
  • Specialty programs market themselves around NAD+, ketamine, and peptides — which tells you the market treats them as non-standard. Read your menu to your broker line by line and get it in writing
  • Your medical director's malpractice does not cover your business
  • Workers' comp turns on worker classification — and "they set their own hours, so they're 1099" is not the test
  • Employees (including per diem) are covered by your policy — if a company is telling W-2 techs to buy their own, ask why
  • True contractors carry their own — and you still carry yours. A plaintiff sues the tech and the company. Collect their COI, naming your business, before they run a call
  • Nurses often carry personal coverage anyway — mostly to defend their license, which your policy won't do. That's a good thing, not distrust
  • A COI is a snapshot. Policies lapse. Track the expiry date
  • Nearly every source ranking for "IV therapy insurance" is a broker selling insurance. Use one — but know what you're asking for first
Built for mobile IV therapy

Compliance you can prove, not just claim

Infuse Pro tracks your certificate of insurance and your medical director agreement, warns you before they expire, and shows patients you're verified — because the paperwork only protects you if it's current.

See how it works →