Business associates are not a single industry. The category includes accounting and law firms, management consultants, answering services, document shredding and storage vendors, transcription services, marketing agencies, actuaries, data analytics firms and many more. What they share is a relationship: they perform a function or service for a covered entity, or for another business associate, that involves PHI.
Before the HITECH Act and the 2013 Omnibus Rule, business associates were bound mainly by contract. Today they are directly liable for certain HIPAA requirements, and OCR can investigate and penalize them independently of their clients. Many organizations that became business associates through one client contract have not fully absorbed what that means.
Key points
- Business associate status comes from the function you perform with PHI, not from signing a BAA.
- Business associates are directly liable under the Security Rule and specific Privacy and Breach Notification provisions.
- Your subcontractors that handle PHI are business associates too and need BAAs with you.
- You must notify your client of breaches of unsecured PHI within the deadlines in §164.410 and your BAA.
Are you a business associate?
Under §160.103, a business associate creates, receives, maintains or transmits PHI on behalf of a covered entity or another business associate, or provides certain services — legal, actuarial, accounting, consulting, data aggregation, management, administrative, accreditation or financial — that involve disclosure of PHI. Some relationships fall outside the definition.
| Usually a business associate | Usually not a business associate |
|---|---|
| A law firm reviewing patient records to defend a malpractice claim | A member of the covered entity’s own workforce, including employees and volunteers |
| A document storage or shredding company handling patient files | A provider receiving PHI to treat the patient |
| An answering service taking patient messages after hours | A courier or internet service provider acting only as a conduit for transmission |
| A consultant performing a risk analysis with access to ePHI systems | A janitorial service whose staff might incidentally see PHI while cleaning |
What you are directly liable for
HHS has described the requirements for which business associates can be held directly liable. They include:
- Complying with the Security Rule — administrative, physical and technical safeguards, policies and documentation.
- Notifying the covered entity (or upstream business associate) of breaches of unsecured PHI.
- Avoiding uses and disclosures of PHI that the BAA or the Privacy Rule does not permit.
- Making reasonable efforts to limit uses, disclosures and requests to the minimum necessary.
- Entering into BAAs with subcontractors that handle PHI, and taking reasonable steps to address a known material breach by a subcontractor.
- Providing an electronic copy of ePHI as the BAA specifies to satisfy an individual’s access request, and providing an accounting of disclosures in certain circumstances.
- Cooperating with HHS investigations and compliance reviews and not retaliating against anyone who files a complaint.
The subcontractor chain
If you give PHI to a vendor so it can help you serve your client — a cloud host, an IT provider, an offshore team, a transcription subcontractor — that vendor is a business associate of yours. §164.502(e)(1)(ii) and §164.308(b)(2) require satisfactory assurances, documented in a BAA meeting §164.504(e) and §164.314(a), that the subcontractor will safeguard the information. Those agreements should be at least as protective as the one you signed with your client. Gaps in this chain are among the most common findings in business associate assessments.
Challenges business associates commonly face
- The organization’s main business is not health care, so no one internally owns HIPAA compliance.
- PHI arrives through informal channels — email attachments, file-sharing links, USB drives — and spreads across personal folders.
- Client BAAs accumulate with different terms, and no one tracks the obligations they impose.
- A Security Rule risk analysis has never been done because the firm assumed the client’s compliance covered it.
- PHI is retained long after the engagement ends, despite BAA return-or-destroy terms.
How we tailor engagements for business associates
Business associate engagements usually start with a scoped HIPAA gap analysis that identifies which requirements apply to your role and where your current practices fall short. From there, a HIPAA risk assessment of the systems and channels through which PHI reaches you addresses the Security Rule requirement directly.
Our business associate compliance service organizes client and subcontractor BAAs and aligns your processes with them, and HIPAA policies and procedures are drafted for an organization whose main line of business may not be health care. Our HIPAA business associate agreement resource explains the required contract elements.
What your clients will expect to see
Covered entities are expected to obtain satisfactory assurances from their business associates, and many now go beyond the contract with vendor risk questionnaires, evidence requests and periodic reviews. For a business associate, this means compliance is also a commercial issue: a slow or vague response to a client questionnaire can delay renewals or new work.
The most useful evidence is usually straightforward: a dated risk analysis covering the systems where client PHI lives, a risk management plan showing progress, current policies, training records, a subcontractor list with BAA status and an incident response procedure that includes client notification. Building that package once, and keeping it current, is far less effort than rebuilding answers for every request.
BAA terms worth reading closely
- Notification deadlines for security incidents and breaches, which are often much shorter than 60 days.
- Whether you must notify of unsuccessful security incidents, and how.
- Restrictions on offshore access, de-identification or aggregation of client data.
- Return-or-destroy obligations and what happens when return or destruction is infeasible.
- Indemnification, insurance and audit rights that create obligations beyond the regulation.
A starting checklist for business associates
- List every client relationship that involves PHI and confirm a signed BAA for each.
- Map how PHI arrives, where it is stored and who can access it.
- Identify subcontractors that touch PHI and put BAAs in place with each.
- Complete and document a Security Rule risk analysis for the systems involved.
- Designate a security official, as §164.308(a)(2) requires.
- Set up a process to notify clients of breaches within the shortest deadline in your BAAs.
- Return or destroy PHI at the end of each engagement as your BAAs require, and document it.
Frequently asked questions
If we haven’t signed a BAA, are we still a business associate?
Yes, if you perform a business associate function involving PHI. The status comes from the activity. Failing to have a BAA is itself a compliance problem for both you and the covered entity.
Does the Privacy Rule apply to business associates in full?
Not in full. Business associates are directly liable for specific Privacy Rule provisions, such as impermissible uses and disclosures and minimum necessary, and are bound contractually by the rest of their BAA. The Security Rule applies to them directly.
Who notifies patients if we have a breach?
The covered entity is responsible for notifying individuals, though it may delegate that task to you by contract. Your direct obligation is to notify the covered entity without unreasonable delay and no later than 60 days after discovery, or sooner if your BAA requires.
Do our subcontractors need to sign BAAs with us?
Yes, if they create, receive, maintain or transmit PHI on your behalf. The BAA requirement flows down the chain to every subcontractor that handles PHI.
Authoritative sources
- HHS — Sample Business Associate Agreement Provisions
- HHS — HIPAA Compliance and Enforcement
- eCFR — 45 CFR Part 164
This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.