Healthcare third-party risk is usually filed under HIPAA, and HIPAA is the right statute for a large part of it. It is a poor sorting rule for the whole portfolio. A covered entity's vendors include business associates, other covered entities, and suppliers that never see protected health information (PHI). Treating all three as a business associate problem produces agreements that should not exist, and misses relationships that can stop claims, or stop a device, without fitting the definition at 45 CFR 160.103. The legal mechanics of the business associate agreement are on HIPAA and third-party risk. This page is the operating question that comes before that document: which relationship is this, and what does that change about assessment, contract, and monitoring? For the general method, start with what TPRM is.
Three populations, one inventory
HHS's business associate guidance is more useful as a sorting tool than as a definition to memorize. Read against a real health-system inventory, it separates three populations.
Business associates
A business associate is a person, other than a workforce member, that performs certain functions or services for a covered entity, or for another business associate, involving PHI. The HHS examples that show up constantly in a health system are a clearinghouse translating claims, an EHR vendor or managed service provider whose support requires access to electronic PHI, a cloud service provider that stores or processes electronic PHI, an app developer contracted to provide a patient app that handles PHI, a transcription vendor, a pharmacy benefit manager for a health plan, and a technician servicing a device that stores PHI where the service itself involves disclosure of that PHI to the technician. A third-party chatbot on a patient portal that uses PHI for symptom assessment, reminders, or scheduling is on the same list. A subcontractor that creates, receives, maintains, or transmits PHI for a business associate is itself a business associate. A covered entity can be a business associate of another covered entity when it is acting on that entity's behalf rather than on its own.
Other covered entities, where a business associate agreement is the wrong artifact
HHS is explicit that many ordinary exchanges of PHI do not make the recipient a business associate, because neither party is acting on the other's behalf. A hospital does not need a business associate agreement with the specialist it refers a patient to, or with a clinical laboratory, when the disclosure is for treatment. A provider submitting a claim and a health plan paying it are each acting as a covered entity, not as the other's business associate. A researcher receiving PHI for research, with authorization, a waiver, or as a limited data set, is not a business associate for that research; the same researcher can become one if engaged to de-identify or aggregate data for the covered entity. A financial institution processing a card payment or an electronic funds transfer is providing its own banking service, not a business associate function. A pure conduit, such as the postal service and electronic equivalents that only transmit PHI, including temporary storage, sits outside the definition. HHS reads that exception narrowly: a vendor that accesses PHI on a regular basis to perform a service is not a conduit. HHS's cloud computing guidance applies the same reading to storage: a cloud provider that maintains ePHI is a business associate, not a conduit, even if the data is encrypted and the provider holds no key.
None of that means these parties drop out of third-party risk management. A reference laboratory and a payer are dependencies. They are not dependencies you control with a business associate agreement. The contract, the assessment, and the incident path are different, and forcing that agreement onto a treatment relationship does not create a business associate where the regulation does not.
Suppliers with incidental or no PHI access
HHS also carves out a person whose function does not involve PHI and whose access would be only incidental, if reasonable safeguards are in place. The example is a janitorial service or an electrician. That is a safeguards question, not a business associate question, and it is easy to over-read. A facilities vendor with a badge and no records access is in this bucket. A facilities vendor whose building-automation access rides the same network as clinical systems, or a device manufacturer with a standing remote path, is not incidental just because the statement of work never says PHI. Ask what the access can reach, not what the vendor calls itself. See vendor tiering for how access and data, rather than spend, should drive the tier.
The business associate agreement is a gate
Where the relationship is a business associate relationship, PHI should not flow until the agreement is in place. What that agreement has to contain, across 45 CFR 164.504(e) and the Security Rule's parallel at 45 CFR 164.314(a), is covered on the HIPAA page, including subcontractor flow-down and direct liability since the 2013 Omnibus Rule. Two operating points are easy to lose once the signed file is in the folder.
- Knowing about a material failure is its own duty. Under 45 CFR 164.504(e)(1)(ii), a covered entity that knows of a pattern of activity or practice by the business associate that is a material breach or violation of the agreement is not in compliance unless it takes reasonable steps to cure the breach or end the violation and, if those steps fail, terminates the contract if feasible. The same structure applies to a business associate that knows of such a pattern by its subcontractor. A single disappointing questionnaire answer is not automatically that pattern. A repeated failure to notify, a practice of using PHI outside the agreement, or a control failure the vendor will not correct, can be. The program needs an owner for that judgment, and a path that is not "wait for renewal."
- The Security Rule still has to be implemented, not only promised. NIST SP 800-66 Rev. 2 (February 2024) is NIST's guide for regulated entities safeguarding electronic PHI under the Security Rule. It does not replace the agreement, and an agreement that recites safeguards does not tell you the safeguards are in place this quarter. Certifications and audit reports are evidence about a stated scope and period. Scope match is the whole question: a report for a different service line is not evidence for the service that holds your PHI.
One proposed change is worth tracking, and it is not in force. In January 2025 HHS published a notice of proposed rulemaking to amend the HIPAA Security Rule (90 FR 898, January 6, 2025). As proposed, a business associate would have to give the covered entity written verification of its technical safeguards at least every 12 months, supported by a written analysis from a subject matter expert and a certification, and would have to notify the covered entity within 24 hours of activating its contingency plan. HHS has not finalized the proposal, and the current Security Rule remains in effect. Treat these as proposed terms, not requirements. If the evidence is useful to you, you can ask for it in the agreement today.
What Change Healthcare showed
The practical lesson is concentration, not a new definition of business associate. Change Healthcare, a UnitedHealth Group unit, suffered a ransomware attack that resulted in a breach of PHI. OCR's Change Healthcare cybersecurity incident FAQ (updated as of March 14, 2025; the page was last reviewed August 13, 2025) calls the impact unprecedented for patients and for health care providers nationwide. The points that belong in a TPRM program:
- OCR prioritized investigations of Change Healthcare and UnitedHealth Group, focused on whether a breach of unsecured PHI occurred and on their compliance with the HIPAA Rules. OCR described its interest in partner covered entities and business associates as secondary, and still reminded those entities that business associate agreements have to be in place and that breach notification has to be timely.
- Change Healthcare filed a breach report with OCR on July 19, 2024. The report identified 500 individuals as the approximate number affected. OCR notes that 500 is the minimum that results in a posting on the HHS Breach Portal, that Change Healthcare was still determining the number, and that a posted report can be amended. Portal posting is not same-day: OCR verifies the report first, a step it describes as generally completed within 14 days, longer when the circumstances require it. A portal row is a verified filing, not a live incident feed, and the first number on it can be a placeholder.
- FAQ item 11 records what Change Healthcare later told OCR about individual notice: approximately 100 million individual notices sent as of October 22, 2024; Change Healthcare told OCR on January 24, 2025 that approximately 130 million notices had been sent and approximately 190 million individuals were impacted; and it told OCR on July 31, 2025 that approximately 192.7 million individuals were impacted. Treat those as OCR's record of Change Healthcare's own reports.
- The covered entity remains responsible for ensuring notification of affected individuals, the Secretary, and, where required, the media. It may delegate the task to the business associate. Only one of them needs to complete each required notice. For this incident, OCR said it would not treat the covered entity's 60-calendar-day period as starting until the covered entity had received the information it needed from Change Healthcare or UnitedHealth Group. That is OCR's stated position on this breach. It is not a general rewrite of 45 CFR 164.410, which still requires a business associate to notify the covered entity without unreasonable delay and no later than 60 calendar days after the business associate discovers a breach of unsecured PHI. Do not draft ordinary contracts to that incident-specific position.
OCR's FAQ addresses two sets of other parties, and both matter for a program that thinks its only business associate is the vendor it pays. One set is covered entities that have a business associate relationship with Change Healthcare or UnitedHealth Group. The other is organizations that are themselves business associates to Change Healthcare or UnitedHealth Group. A clearinghouse sits in the transaction path. The covered entity's agreement with its own vendor does not name that clearinghouse unless someone asked the vendor who actually processes the claim. HHS does not require the covered entity to sign an agreement with its business associate's subcontractor. The business associate has to have that agreement before it discloses PHI. You still need the name. That is how concentration becomes visible: many covered entities, one pipe for claims. See fourth-party risk and concentration risk.
Clinical technology is a second assessment
A medical device vendor can be a business associate, a product supplier, or both, depending on whether anyone there receives PHI. The HHS technician example is the boundary: servicing a device that stores PHI is a business associate relationship when the service involves disclosure of PHI to the technician. Selling a device, and never receiving PHI, is not. Patient safety does not wait on that distinction. A vulnerable infusion pump or patient monitor is a third-party risk whether or not a business associate agreement exists.
FDA's authority over that product risk is separate from HIPAA. Section 524B of the Federal Food, Drug, and Cosmetic Act took effect on March 29, 2023. It requires a cyber device's premarket submission to include information showing a reasonable assurance that the device and related systems are cybersecure. FDA's manufacturer cybersecurity page describes the statutory contents as a plan to address postmarket cybersecurity vulnerabilities and exploits, including coordinated vulnerability disclosure; processes and procedures that provide a reasonable assurance of cybersecurity, including updates and patches; and a software bill of materials. FDA's medical device cybersecurity page lists a February 2, 2026 final guidance on premarket submissions, revising the June 27, 2025 guidance that added the section 524B discussion. That file tells you what the manufacturer had to show FDA about the product. It does not tell you whether remote service into your hospital is brokered and logged, whether the device sits on a segmented network, or whether the field engineer is a business associate.
Outside-in monitoring of the manufacturer's internet footprint answers a third question, and only that one. It will not see a device that is deliberately not reachable from the internet. For the highest-impact clinical suppliers, keep three lines rather than one score: the product record (vulnerability disclosure, patch qualification, and a software bill of materials where the user can actually obtain it), the service record (remote access, who holds it, how it is revoked), and the PHI question. Replacement is often unrealistic for the life of the installed base, so compensating controls and leverage at renewal matter more than a terminate-and-replace habit. The same constraint shows up with operational technology suppliers; third-party risk in critical infrastructure covers that pattern, and healthcare adds the PHI question those regimes do not.
Substance use disorder records are a second regime
If the organization is a Part 2 program, or it receives substance use disorder records from one, HIPAA is not the only rule on the vendor. 42 CFR Part 2 protects records of federally assisted programs that diagnose, treat, or refer for treatment of a substance use disorder. HHS states that some Part 2 requirements also apply to people and organizations that receive those records, including other health care providers, qualified service organizations, HIPAA covered entities and business associates, intermediaries, and investigative agencies. The 2024 final rule has been effective since April 16, 2024, and compliance was required by February 16, 2026. OCR enforces Part 2 using the HIPAA Enforcement Rule at 45 CFR Part 160, subparts C, D, and E. A patient may give a single consent for future treatment, payment, and health care operations uses. A HIPAA covered provider or health plan that receives the record under that consent may redisclose it as HIPAA permits, except for use in a legal proceeding against the patient.
One timing trap is easy to miss. The final rule's accounting-of-disclosures provision at 42 CFR 2.25 is tolled until HHS revises the HIPAA accounting standard at 45 CFR 164.528. The Federal Register text of the 2024 final rule says so. A program building an accounting workflow for Part 2 should not assume that particular section is already in force. What is in force is enough to change vendor intake: a business associate agreement does not, by itself, answer whether the vendor will receive Part 2 records, whether it is a qualified service organization, or which Part 2 limits travel with the records. Ask that before the data moves.
A program that fits the portfolio
- Sort before you tier. Tag each relationship as business associate, other covered entity, Part 2 recipient, clinical supplier, or incidental-access supplier. One vendor can carry more than one tag. Tiering then follows data and consequence, not the label on the contract.
- Map the transactions that hurt when they stop. Claims, eligibility, remittance, e-prescribing, and pharmacy switches are where clearinghouse concentration hides. Record the actual processor, including the one behind your direct vendor.
- Get the agreement before PHI moves, and keep a cure path. Use the HIPAA page for the clause list. Assign an owner for 45 CFR 164.504(e)(1)(ii) once you know of a material pattern, including the decision to terminate if a cure fails and termination is feasible.
- Collect downstream names for critical business associates. Hosting, transcription, ambient documentation, patient-portal tools, and claims intermediaries. You will not sign those agreements. You do need to know they exist before an incident tells you. See fourth-party risk.
- Write the notice clock inside the 60-day ceiling. 45 CFR 164.410 requires the business associate to notify without unreasonable delay and no later than 60 calendar days after it discovers a breach of unsecured PHI. Sixty days is an outer limit, not a safe harbor. If the business associate is your agent under the federal common law of agency, 45 CFR 164.404(a)(2) treats its discovery as yours, so your 60 days start the same day and a contract that allows the full 60 leaves you none. If it is an independent contractor, your clock starts when it tells you. A law enforcement request can delay notification under 45 CFR 164.412, but that is an exception to plan around, not a term to negotiate. Either way, put a short, fixed number of days in the agreement. How to run the first hours after a vendor calls is in the vendor breach playbook.
- Split clinical suppliers into product, access, and PHI. Ask for the vulnerability-disclosure practice and, for a cyber device, whether a software bill of materials is available to you as a user and not only filed with FDA. Inventory remote access per vendor and revoke it when the contract ends. PHI return or destruction is the other half of offboarding. Under 45 CFR 164.504(e)(2)(ii)(J) the agreement must provide for return or destruction at termination if feasible and, where it is not, extend its protections to what the business associate keeps and limit further use to the reasons return is infeasible. Ask for written confirmation that covers its subcontractors, and record what was kept and why. See vendor offboarding.
- Plan the response side of clearinghouse concentration. Pre-contract an alternate clearinghouse and learn the payer enrollment lead time before you need it. Write down the criteria for disconnecting from a vendor and for reconnecting, including the evidence you require before reconnecting. Plan for cash flow while claims are delayed.
- Watch between annual reviews, and read the breach portal with the Change Healthcare caveat. Continuous monitoring of what a vendor exposes on the internet covers that slice of the relationship and not the clinical network. The breach portal is a backstop for large filings. It is useful, it is late, and the first posted count can be the minimum of 500 individuals while the real number is still unknown.
Where tools fit, and where they do not
No single product covers this portfolio. Workflow and GRC platforms such as OneTrust and ProcessUnity are built to hold the business associate agreement library, the downstream list, and the evidence request. That is where the gate lives. Security-rating providers such as BitSight and SecurityScorecard add an outside-in view of internet-visible posture, which helps triage a long list and spot change between assessments. Rescana focuses on continuous, evidence-based assessment of that externally observable footprint (see vendor attack surface monitoring). It does not hold the signed agreement, see a device on a segmented clinical network, or decide to terminate a business associate. Those decisions stay under your approval. Most programs will run more than one of these, because a current agreement and a current external signal answer different questions.
Frequently asked questions
What is third-party risk management in healthcare?
Healthcare third-party risk management is the work of finding the outside parties a covered entity depends on and controlling the risk they create. That includes privacy risk under HIPAA and operational and patient-safety risk that HIPAA does not cover. The portfolio mixes business associates that handle protected health information, other covered entities such as treating providers and health plans, clinical technology suppliers, and ordinary vendors whose access to PHI is only incidental. A business associate agreement is the right control for the first group only.
Which healthcare vendors need a business associate agreement?
A vendor needs a business associate agreement when it creates, receives, maintains, or transmits protected health information on behalf of a covered entity or another business associate. HHS examples include claims clearinghouses, EHR vendors and managed service providers with access to electronic PHI, cloud providers that store electronic PHI, transcription vendors, and a technician who receives PHI while servicing a device that stores it. A business associate agreement is not required for a disclosure to another provider for treatment, for a provider and a health plan each acting on its own behalf in payment, for a pure conduit, or for a vendor whose access to PHI would be only incidental and is covered by reasonable safeguards.
Does a business associate agreement replace a vendor security assessment?
No. The agreement is the legal gate and the promise. It does not show that safeguards are operating, that an audit report's scope matches the service you use, or that a subcontractor chain exists. Under 45 CFR 164.504(e)(1)(ii), a covered entity that knows of a pattern of activity or practice that is a material breach of the agreement has to take reasonable steps to cure or end it and, if that fails, terminate if feasible. Assessment and monitoring are how you learn whether that pattern exists. NIST SP 800-66 Rev. 2 is a guide to the Security Rule for regulated entities. It is not a substitute for the agreement.
What did the Change Healthcare cyberattack show about third-party risk in healthcare?
OCR's FAQ on the incident describes a clearinghouse ransomware breach whose effects ran well beyond a single contract. Change Healthcare's July 19, 2024 breach report to OCR listed 500 individuals, the minimum that places a report on the HHS Breach Portal, while the number of people affected was still being determined. Change Healthcare later told OCR on January 24, 2025 that approximately 190 million individuals were impacted, and on July 31, 2025 that approximately 192.7 million were. Covered entities stay responsible for notification and may delegate it to Change Healthcare. The operating lesson is to map who actually processes claims and related transactions, including the party behind the vendor you pay, because that agreement does not name the clearinghouse unless you asked.
Are medical device manufacturers business associates under HIPAA?
Only when they create, receive, maintain, or transmit protected health information on a covered entity's behalf. HHS's example is a technician servicing a device that stores PHI, where the service involves disclosure of that PHI to the technician. A manufacturer that never receives PHI is not a business associate for that supply relationship, and it can still be a serious third-party risk because of patient safety and remote access. FDA section 524B, in effect since March 29, 2023, requires a cyber device premarket submission to include a postmarket vulnerability plan, cybersecurity processes including updates and patches, and a software bill of materials. That product file does not answer the business associate question, and it does not describe your network.