Certificate of Insurance for MedTech Vendors: Coverage You Actually Need
Which COI coverages hospitals commonly require, how to spot gaps, and how to request clean endorsements.
Article content
Hospitals often require a certificate of insurance before purchasing or legal will move. Checking it against their list early prevents a delay.
Common coverage elements
- General liability, often $1 million per occurrence and $2 million aggregate
- Professional liability or errors and omissions, limits vary
- Workers' compensation and employer's liability
- Auto liability if vehicles are used on site
- Additional insured and primary, non-contributory endorsements
Worked example
Your certificate shows general liability of $1 million and $2 million, but no additional-insured endorsement and no errors and omissions. The hospital requires both. You request an updated certificate with those endorsements and the stated errors-and-omissions limit, instead of finding out at the last review.
Common mistakes
- Sending an expired certificate.
- Limits that look fine while the additional-insured language is missing.
- The insured legal name not matching the contracting party.
Try the tool
Run the details through the COI coverage checker before you send the paperwork.
Context for MedTech teams
This topic shows up every week in vendor management and perioperative coordination. The short version: make it easy for qualified reps to support cases while maintaining airtight compliance and safety guardrails. Align hospital policy with your credentialing workflow, keep training and immunization evidence current, and close the last‑mile gap between your credentialing system and the OR desk.
If you are rolling out updates across facilities, standardize the “source of truth” for rep status, implement pragmatic exception handling, and partner early with IT and legal on privacy and device security. Those moves reduce day‑of‑surgery friction and help you demonstrate audit‑ready controls.
Further reading
For deeper context on credentialing, OR access, and validation, explore these resources: