Ask KJ · Healthcare cybersecurity
Business Associate Agreements, EHRs, and Healthcare Vendors
Review who touches PHI, vendor contracts, and controls before connecting software or services.

By Kimm C. King Jr. · Reviewed
Determine who is a business associate
Evaluate the function performed and whether a vendor creates, receives, maintains, or transmits PHI on behalf of the practice. Common candidates include EHR, billing, backup, transcription, managed IT, and managed messaging vendors. HHS explains that a cloud provider that maintains ePHI can be a business associate even when it cannot decrypt or view the data.
Review the exact workflow and service plan
Confirm the covered service, signed BAA where applicable, permitted uses, subcontractors, access controls, incident notice responsibilities, data return, and deletion or transition. Verify whether the product tier, integrations, and support channels used by the practice fall within the scope. A vendor agreement and the deployed configuration both need review.
Scenario involving a billing contractor
Trace the vendor’s access to claims, receipts, and support tickets. List staff and vendor accounts by role. Require a named contact for a security incident and confirm how the practice receives exports during transition. Check whether partner services also receive information.
Keep a decision record
Maintain a vendor inventory, agreement and renewal dates, approved workflows, access evidence, and named owner. Remove access and confirm data return or handling according to the agreement when a vendor leaves.
My answers to related practice questions
Official sources
Apply this to your practice
Confirm requirements for your organization, services, and jurisdiction with your privacy or legal lead. Use fictional or approved de-identified examples when testing. Keep PHI out of public forms.
Find healthcare resources by state or city · All healthcare cybersecurity guides
Explore cybersecurity consulting · Read the website’s healthcare data notice