Under HIPAA, a business associate is a person or company that handles protected health information (PHI) for a covered entity, such as a provider, health plan, or clearinghouse. The definition in 45 CFR 160.103 names claims processing, data analysis, billing, and quality assurance as examples, along with legal, accounting, and consulting services that involve PHI. Subcontractors of a business associate are business associates too. A covered entity may share PHI with a business associate only after getting satisfactory assurance, in writing, that the data will be safeguarded. The BAA is that assurance.
What a BAA has to contain
The required contents are set out in 45 CFR 164.504(e). A compliant agreement must:
- State the permitted and required uses and disclosures of PHI, and bar the vendor from using it any other way.
- Require appropriate safeguards, including compliance with the Security Rule for electronic PHI.
- Require the vendor to report any use or disclosure the contract does not allow, including breaches of unsecured PHI.
- Require the vendor's subcontractors to agree to the same restrictions.
- Support patients' rights of access, amendment, and accounting of disclosures where the vendor holds the records.
- Make the vendor's books and records available to HHS for compliance reviews.
- Require the vendor to return or destroy the PHI at termination, or keep protecting it if that is not feasible.
- Let the covered entity terminate the contract if the vendor violates a material term.
Why it matters when you buy or build software
Most software vendors that touch patient data are business associates: the hosting provider, the development team with production access, the analytics tool, the SMS gateway that sends appointment reminders. Each link in that chain needs its own agreement, because a business associate may pass PHI to a subcontractor only on the same kind of written assurance. Breach timing is fixed by regulation: a business associate must notify the covered entity without unreasonable delay and no later than 60 calendar days after discovering a breach of unsecured PHI. The agreement has to be in place before the vendor gets any PHI, so it cannot wait until go-live. If a covered entity knows of a pattern of material violations by its vendor and does not act to cure or end it, the covered entity is itself out of compliance.
Example
A clinic hires a team to rebuild its patient portal. During migration the engineers will query the old database, which holds names, appointments, and lab results. That makes the team a business associate, so the clinic and the team sign a BAA first. The team runs the new portal on a cloud platform, which makes the cloud provider a subcontractor, so the team signs a BAA with it too. When the engagement ends, the team returns or destroys every copy of the migration data. At Onix Health we sign a BAA before anyone on our side sees PHI.