Life SciencesLiability
Get a quote

TL;DR

Salt Lake City sits at the center of an established Utah medical device corridor spanning cardiovascular, interventional, and general devices. Coverage here turns on products liability sized to device class, IDE clinical trial exposure, and the additional-insured obligations buried in GPO and hospital supply contracts. The recurring gap is a blanket additional-insured endorsement that quietly excludes products and completed operations.

Salt Lake City medical device

Medical device insurance for Salt Lake City and Utah's device corridor.

Salt Lake City anchors one of the country's more mature medical device corridors, with operators along the Wasatch Front building cardiovascular, interventional, and general medical devices alongside the broader Silicon Slopes technology ecosystem. Utah's cluster includes large operators such as Becton Dickinson (BD) operations, Merit Medical Systems headquartered in South Jordan, and Edwards Lifesciences operations, plus device-testing labs and a deep base of contract manufacturers and component suppliers. That mix produces insurance exposures distinct from the region's biotech and therapeutics companies, which carry their own coverage architecture.

For a device operator, the policy has to be engineered around the physical product, the clinical pathway that cleared it, and the commercial contracts that move it into hospitals. Products liability, IDE clinical trial coverage, and the additional-insured and recall obligations embedded in GPO agreements do the real work here. A generic small-business package rarely reflects device-class risk, and the mismatch usually surfaces at the worst possible moment, when a hospital customer or a supply contract demands proof of coverage the policy does not actually provide.

Get a quoteRun the Free Analyzer

Last updated 2026-07-13

Cluster shape

The Salt Lake City and Utah device cluster

The Utah device corridor is concentrated along the Salt Lake City metro and the surrounding Wasatch Front communities, where established manufacturers and a supporting supplier base cluster near research talent and a skilled production workforce. Merit Medical Systems is headquartered in South Jordan, and the region hosts Becton Dickinson (BD) operations and Edwards Lifesciences operations, giving the area unusual depth in cardiovascular and interventional device design and manufacturing. This anchor base pulls in contract manufacturers, component suppliers, and specialized device-testing labs that serve both local operators and national customers.

That concentration matters for insurance because the corridor skews toward higher-acuity products. Cardiovascular and interventional devices frequently fall into Class II and Class III, where a failure reaches a patient directly and the resulting liability tower has to be sized accordingly. General medical devices and Class I products round out the cluster, but the presence of implantable and interventional technology raises the ceiling on what an appropriate program looks like across the region.

The corridor also overlaps with the Silicon Slopes technology ecosystem, which brings software, connectivity, and data into modern devices. That convergence is why a Salt Lake City device program often has to consider software-driven functionality and connected-device exposure in addition to the traditional hardware product risk. This page addresses the device manufacturing cluster specifically and is distinct from Salt Lake City's biotech cluster, which is covered on its own page.

Coverage architecture

How coverage is built for a device operator

The foundation is products liability, and the tower should be sized to the device class rather than to headcount or revenue. Class I devices carry comparatively modest exposure, while Class II and especially Class III cardiovascular and interventional devices justify materially higher limits, with market-typical products towers for device manufacturers commonly running in the $5M-$25M range and higher for implantable or life-sustaining technology. Clinical-stage operators also need IDE clinical trial coverage that responds to investigational device exposure during studies, since a standard products form may not contemplate pre-market use in human subjects.

Commercial contracts drive much of the remaining structure. Hospital purchase contracts and GPO supplier agreements with organizations such as Vizient, Premier, and HealthTrust routinely require additional-insured status for both products and completed operations, primary and non-contributory wording, and specified minimum limits. Product recall belongs in the program as a separate first-party trigger, because the cost to retrieve, replace, or rework a defective device is an expense that liability coverage does not pay. Operators that supply components or manufacture under an OEM arrangement also carry contractual obligations flowing from the finished-device maker, and the policy has to honor those indemnity and insurance terms.

The most common and most damaging gap is a blanket additional-insured endorsement that grants status to customers but excludes products and completed operations, which is precisely the exposure a hospital or GPO cares about. Reading the endorsement language, not the certificate, is the only way to confirm the coverage actually matches the contract. Aligning limits, additional-insured scope, primary and non-contributory wording, and recall to each supply agreement is the practical difference between a certificate that satisfies a customer and one that quietly leaves the operator exposed.

Regulatory + market context

Regulatory and contractual context

Device risk is organized around the FDA classification system, and the class of a given product should drive both the underwriting conversation and the size of the liability tower. Class I, Class II, and Class III carry escalating regulatory scrutiny and escalating potential for patient harm, and cardiovascular and interventional devices concentrated in the Utah corridor frequently sit at the higher end of that scale. Investigational use under an IDE adds a distinct clinical exposure that a purely commercial products form may not address.

On the commercial side, GPO and hospital supply agreements function as their own compliance regime, dictating insurance terms that carry real contractual consequences if unmet. A device operator that supplies to national systems through Vizient, Premier, or HealthTrust is agreeing to specific additional-insured, primary and non-contributory, and limit requirements, and non-compliance can jeopardize the supply relationship itself. Matching the insurance program to these contractual and regulatory realities, rather than to a generic template, is what keeps a Utah device operator both covered and contract-eligible.

Frequently asked

Common questions from Salt Lake City medical device operators

What makes medical device insurance in Salt Lake City different?

The Utah corridor is unusually weighted toward cardiovascular and interventional devices, which often fall into higher FDA classes and demand larger products liability towers than general device work. With anchor operators, contract manufacturers, and device-testing labs concentrated along the Wasatch Front, many local companies also carry supplier and OEM obligations to larger finished-device makers. A program built here has to reflect device class, clinical-trial exposure, and the additional-insured demands of hospital and GPO contracts, not a generic small-business template.

How should a cardiovascular or interventional device company size its products liability tower?

The tower should follow the device class, not headcount or revenue. Class II and Class III cardiovascular and interventional devices reach patients directly, so market-typical products limits for these operators commonly run higher than for Class I products, often in the $5M-$25M range and above for implantable or life-sustaining technology. Clinical-stage operators should confirm the program includes IDE coverage that responds during investigational use, since a standard products form may not contemplate pre-market use in human subjects.

What do GPO and hospital contracts require for additional-insured status?

Hospital purchase contracts and GPO agreements with groups such as Vizient, Premier, and HealthTrust typically require additional-insured status covering both products and completed operations, primary and non-contributory wording, and specified minimum limits. The common trap is a blanket additional-insured endorsement that excludes products and completed operations, which is exactly the exposure the customer cares about. The endorsement language itself, not the certificate, has to be reviewed against each supply agreement.

What insurance obligations does a component or OEM supplier carry?

An operator that supplies components or manufactures under an OEM arrangement inherits contractual insurance and indemnity terms from the finished-device maker, and the policy has to honor them. That usually means carrying products and completed operations coverage, extending additional-insured status upstream, and meeting specified limits tied to the finished device's risk profile rather than the component's standalone value. Product recall should be addressed as a separate first-party trigger, because the cost of retrieving or reworking a supplied part is an expense liability coverage does not pay.

Medical device insurance practice →Device products liability →Salt Lake City biotech →Device umbrella limits →

Free coverage review

A specialist will reach out by end of business day.

Programs placed through A-rated specialty markets. Send your contract, insurance schedule, or current COI - a specialist returns a clause-by-clause read by end of business day.

Get my quote

Specifically for Salt Lake City medical device operators.

Programs placed through A-rated specialty markets. Your specialist handles unlimited certificates of insurance, annual coverage reviews, and claims advocacy.