Does General Liability Cover a Patient Injury at Your Digital Health Company?

Not the kind of patient injury a digital health company is most likely to face. General liability covers third-party bodily injury on your premises or arising from your operations, someone hurt at your office, a physical accident tied to your activities. A patient harmed by a clinical decision made through your platform is a different claim entirely. That is professional liability and technology errors and omissions territory, and most digital health founders do not understand the distinction until a claim arrives.

What General Liability Actually Covers

General liability responds to third-party bodily injury and property damage from your premises and operations: a visitor slips in your office, a contractor is hurt on site. It is real and necessary coverage, but the injury it contemplates is physical and tied to a place or a physical activity. A digital health company’s defining exposure is not someone tripping in the lobby. It is the harm that flows when a user relies on what the software did, or failed to do, and a patient is worse off for it. That harm reaches the patient through a clinical decision, not through a premises accident, and general liability was not built to answer it.

The confusion comes from the word “injury.” A patient harmed after acting on a flawed output is, in a plain sense, injured, so founders assume the liability policy that mentions bodily injury responds. The policy’s bodily-injury grant is about premises and operations, not about the consequences of a clinical recommendation delivered through software.

Where the Real Exposure Sits

When a digital health product influences care and a patient is harmed, the claim is about the quality of what the product delivered. That is the reliance-on-the-output trigger behind a digital health professional liability claim: a symptom checker that misguides, a monitoring tool that misses an alert, a decision-support feature that recommends the wrong step. Professional liability answers the judgment side of that, and technology errors and omissions answers the software-function side, which is why a platform usually needs both, coordinated, as covered in technology errors and omissions for a digital health company.

There is a further trap specific to software that can cause physical harm. Many technology policies carry a bodily injury exclusion that makes sense for ordinary software but fails a health platform, where a software failure can lead to patient harm. So the exposure has to be matched deliberately: professional liability and tech E&O written to respond where the product influences care, with the bodily injury question addressed rather than left to a default exclusion. General liability sits beside those for the premises and operations risks it was actually built for, not as the answer to a clinical-harm claim.

Why the Distinction Matters Before a Claim

A digital health company that carries general liability and assumes it covers patient harm has insured the least likely injury and left the most likely one open. The premises accident GL answers is rare for a software company; the clinical-reliance claim is the one that fits the business. When that claim arrives, the GL policy does not respond, and if there is no professional liability or tech E&O in force, or if a bodily injury exclusion knocks out the tech policy, the company is exposed on its signature risk. Drawing the line in advance, before an incident forces it, is what keeps the claim from landing in an uncovered gap.

What to Do Now

Map each way your product could harm a user and ask which policy answers it. A physical accident at your premises is general liability. A patient harmed by a clinical decision the platform influenced is professional liability and tech E&O, and the bodily injury wording on the tech policy has to be confirmed rather than assumed. Make sure the lines are coordinated so a mixed claim does not fall between them, and revisit as the product takes on more clinical function, because the exposure grows faster than the policy renews.

Before your next renewal, separate the premises question from the clinical-harm question and confirm a policy answers each. A specialty review through Tower Street Insurance can confirm your digital health company is covered for the patient-harm claim it is actually most likely to face.