Third-Party Risk Management in Healthcare: A Guide

Third-party risk management (TPRM) in healthcare means knowing every vendor that touches patient data or critical systems, ranking them by risk, putting HIPAA business associate agreements and security requirements in contract, and monitoring them over time. The hardest parts are usually an incomplete vendor inventory, limited staff and vendors that are too critical to replace.

Key takeaways

  • You cannot manage vendors you have not inventoried, so start with a complete list.
  • Tier vendors by data access and operational impact, then scale the review effort.
  • HIPAA requires business associate agreements before PHI is shared with most vendors.
  • Monitoring and offboarding matter as much as the initial assessment.

Why is third-party risk harder in healthcare?

Hospitals and health systems rely on a long chain of outside parties: electronic health record vendors, billing and claims processors, cloud hosts, medical device makers, staffing agencies, transcription services and software add-ons bought by individual departments. Many of them handle protected health information (PHI), and some keep clinical operations running. When one fails or is breached, care can be disrupted, not just data exposed.

Common challenges include:

  • Shadow procurement. Departments buy tools with a credit card, bypassing security review.
  • Fourth parties. Your vendor's subcontractors may also handle PHI.
  • Concentration risk. A few vendors support many critical workflows and have no quick substitute.
  • Thin teams. Smaller hospitals may have one or two people covering all of security.
  • Questionnaire fatigue. Long, generic questionnaires produce long, generic answers.

What does HIPAA require for vendors?

Under HIPAA, a business associate is a person or organization that performs functions or services for a covered entity involving PHI. HHS lists examples such as cloud providers, EHR vendors, IT contractors, billing companies and claims administrators. Before sharing PHI, the covered entity needs satisfactory assurances, usually a business associate agreement (BAA). HHS explains that the BAA must describe permitted uses and disclosures, require compliance with applicable Security Rule standards and require reporting of security incidents, including breaches of unsecured PHI. Business associates also need BAAs with their own subcontractors, and they are directly liable for certain HIPAA provisions.

A BAA is a legal floor, not a risk assessment. Our article on EHR data security and HIPAA compliance covers the patient privacy side in more detail.

How to build a practical TPRM program

1. Build the inventory

Pull vendor lists from accounts payable, contract management, IT asset records and single sign-on logs. Note for each vendor what data it accesses, which systems it connects to and who owns the relationship internally.

2. Tier by risk

TierTypical profileReview approach
CriticalLarge volumes of PHI or supports clinical operationsFull assessment, evidence review, annual reassessment, exit plan
HighSome PHI or network accessStandard questionnaire, BAA, review of independent audit reports
ModerateBusiness data, no PHIShort questionnaire, contract security clauses
LowNo sensitive data or system accessBasic due diligence at onboarding

3. Assess with a shared standard

Align questions to a recognized framework so answers can be compared. The NIST Cybersecurity Framework is widely used, and the HHS 405(d) program publishes Health Industry Cybersecurity Practices tailored to the sector. Ask for evidence, not just yes or no answers.

4. Put requirements in the contract

Include breach notification timelines, right to audit, security controls, subcontractor disclosure, data return or destruction at termination and cyber insurance expectations.

5. Monitor and offboard

Reassess on a schedule tied to tier, watch for changes such as acquisitions or new subcontractors, and confirm access removal and data destruction when a contract ends.

Purchasing decisions are where most of this starts, so connect TPRM to the process described in our guide on healthcare IT purchasing decisions.

Who should own vendor risk?

TPRM fails when it belongs to nobody. A workable split is: procurement triggers the review, security assesses, compliance and legal handle the BAA and contract terms, and the business owner stays accountable for the relationship. HR has a role too, because staffing agencies, benefits administrators and payroll providers handle sensitive employee data, a point covered in our piece on HR's role in cybersecurity and risk management.

Frequently Asked Questions

Is every healthcare vendor a business associate?

No. A vendor is a business associate when it creates, receives, maintains or transmits PHI on behalf of a covered entity. A furniture supplier is not one. Some relationships are excluded, such as disclosures between providers for treatment. When in doubt, have counsel review the data flows rather than relying on the vendor's own label.

How often should vendors be reassessed?

Base frequency on tier. Critical vendors are commonly reviewed every year, with interim checks after a major incident, acquisition or change in services. Lower-tier vendors can be reviewed less often or at renewal. Whatever schedule you set, document it in policy and follow it, because an unapplied schedule is a finding in itself.

What if a critical vendor fails our assessment?

Few hospitals can switch a critical vendor quickly. Agree on a remediation plan with dates, add compensating controls such as tighter access or extra monitoring, document the accepted risk with an executive sign-off and start building an exit or backup plan in case remediation stalls.

Next steps

Start by reconciling your vendor list against accounts payable and single sign-on data. Tier the top fifty vendors, confirm a current BAA exists for every one that touches PHI and set reassessment dates for the critical tier. Then pick one recognized framework for all future questionnaires.

Last reviewed: October 2026.

Sources

Comments

Popular Posts

Why Workday Onboarding Breaks Down for Frontline Employees

How to Improve the Customer Experience (CX)

How Do I Log In and Sign In to Workday HCM

UKG Union Contract and Overtime Rules for Multi-Site Food Plants

Infor HCM Software Engineer Jobs: Salary Factors and Skills

How to Search in Workday: Find Reqs, Reports, People and Tasks

ERP Solution Guide: How to Choose the Best ERP for You

The End of Remote Work: Why Companies Want You Back

The Future of Employee Healthcare Key Concerns and Strategies for 2024

How Digital Marketing Helps Your Business Grow: A Practical Plan