Security and privacy
The Business Associate Agreement, explained
We sign one with every practice before any patient data moves. Here is what HIPAA requires every Business Associate Agreement (BAA) to say, with the rule behind each line.
| Term | In plain words | Rule |
|---|---|---|
| Permitted uses | The business associate uses and shares patient information only as the BAA allows or the law requires. The BAA cannot allow anything the practice could not do itself, apart from the business associate's own management and administration and combining data for the practice's operations. | 45 CFR 164.504(e)(2)(i) and (ii)(A) |
| Safeguards | It protects the information with appropriate safeguards and follows the HIPAA Security Rule for electronic records. | 45 CFR 164.504(e)(2)(ii)(B); 164.314(a)(2)(i)(A) |
| Reporting | It tells the practice about any use or disclosure the BAA does not allow, any security incident, and any breach of unsecured patient information. | 45 CFR 164.504(e)(2)(ii)(C); 164.314(a)(2)(i)(C) |
| Vendors | Every vendor it uses that handles the information agrees to the same restrictions, in writing. | 45 CFR 164.504(e)(2)(ii)(D); 164.314(a)(2)(i)(B) |
| Patients' rights | It makes the information available so the practice can answer patients who ask to see or correct their records, or ask who their information was shared with. | 45 CFR 164.504(e)(2)(ii)(E) to (G) |
| The practice's own duties | It follows the Privacy Rule when it does a task that is the practice's own obligation. | 45 CFR 164.504(e)(2)(ii)(H) |
| Access for HHS | It opens its books and records about the information to HHS. | 45 CFR 164.504(e)(2)(ii)(I) |
| At the end | It returns or destroys all of the information and keeps no copies. If that is not feasible, it keeps protecting what is left and uses it only for the reason it could not be returned or destroyed. | 45 CFR 164.504(e)(2)(ii)(J) |
| Ending the agreement | The practice can end the agreement if the business associate breaks a material term. | 45 CFR 164.504(e)(2)(iii) |
HHS publishes example BAA provisions and says using them is optional; the parties can add stricter terms, such as a shorter window to report a breach.
Why the BAA comes first
A billing service is a business associate
A billing service that handles patient information for a practice is a HIPAA business associate.
The BAA comes before any patient data
A practice may share patient information with a business associate only after a written BAA is in place.
Our vendors sign the same terms; you do not sign with them
You do not sign with a business associate's vendors; the business associate must have a written BAA with each vendor that handles patient information.
HHS can enforce many duties against us directly
HHS can enforce many HIPAA duties against a business associate directly, not only through the BAA.
A BAA is not a certification
There is no official HIPAA certification. HHS does not issue one and does not recognize private ones. We sign a BAA before any patient data moves, and we follow the HIPAA Privacy, Security and Breach Notification Rules.
At the end, data is returned or destroyed
When the BAA ends, a business associate must return or destroy the practice's patient information and keep no copies; if that is not feasible, it must keep protecting it.
Next question: how do your systems protect our data?
Encryption, role-based access and a log of every access, built to HIPAA standards.