How to Use a Free BAA Template to Vet a Vendor’s Agreement Before PHI Is Shared

Start With the Vendor’s Own BAA

Before a vendor creates, receives, maintains, or transmits protected health information for your practice, you need to know whether the vendor is a business associate and whether the agreement in front of you covers what HIPAA requires. An EHR, cloud storage provider, email service, billing company, or IT support firm with access to patient data is the usual example. A vendor that handles no PHI does not need a BAA, and a conduit that carries PHI only on a transient basis does not either. A vendor that stores encrypted PHI is still a business associate even if it cannot view the data or does not hold the key. Sharing information with another provider to treat a patient is also outside this vendor-BAA exercise.

Once you have decided the vendor needs a BAA, check the vendor’s own agreement first. Large cloud, email, and EHR vendors usually insist on their own form, and that is fine if it contains every provision HIPAA requires. The free business associate agreement template on hipaa.systems is useful here as a comparison document, not as a replacement for the vendor’s paper. It is an editable two-page Word BAA written from the practice’s side, and it contains the provisions required by 45 CFR 164.504(e) and 164.314(a). Read it beside the vendor’s BAA and mark every required clause the vendor’s version does or does not contain.

Compare the Core Required Provisions

The template gives you a structured way to read the vendor’s BAA. Start with permitted and required uses and disclosures. The vendor should be allowed to use or disclose PHI only as the agreement permits and as HIPAA requires, with no other use. Next, check safeguards. The vendor’s BAA should commit the vendor to appropriate safeguards and to its Security Rule duties. Then look at subcontractors: the vendor must get the same restrictions in writing from any subcontractor that handles your PHI. You do not sign with those subcontractors yourself, but the vendor’s BAA should make the chain of written obligations clear.

Move on to reporting. The vendor’s BAA should require the vendor to report improper uses, security incidents, and breaches. It should also cover patients’ rights: access, amendment, accounting, Privacy Rule duties, and HHS access. Finally, check the end of the relationship. The BAA should require return or destruction of PHI and should address termination for a material violation. These are not decorative clauses. They map to the required provisions in 45 CFR 164.504(e)(2)(ii)(A) through (J), 164.504(e)(2)(iii), 164.314(a)(2)(i)(A) through (C), and 164.410. If the vendor’s BAA omits one, ask for an addendum or use a separate agreement as a starting point for both sides to adapt and sign. The template can serve that purpose, but it does not make the vendor safe for patient information, and the vendor still has to agree to it.

Check the Reporting Clock and the Optional Uses

Reporting deadlines deserve a close read. HIPAA requires a business associate to report a breach without unreasonable delay and no later than 60 calendar days after discovery. The template sets a shorter contractual deadline of 10 business days. A shorter deadline leaves the practice time to meet its own breach notification duties. When you review the vendor’s BAA, find the deadline and compare it with your own process. Also check whether the vendor’s BAA describes the services you actually use and covers the product and plan in question. A BAA for one service tier does not automatically answer the question for another.

The template also asks you to decide whether to allow optional uses: the vendor’s own management and administration, and data aggregation. The vendor’s BAA may permit broader uses than your practice intends. Mark those provisions and decide whether they fit the service. Then check operational details that sit beside the BAA. Turn on the settings the vendor requires, confirm that the BAA and your services agreement do not conflict, and remember that state contract law or the services agreement may need more terms or formalities. The template covers the terms HIPAA requires, not prices, liability, or other commercial terms.

Use a Provision-by-Provision Checklist

A single pass through a vendor’s BAA can miss a clause buried in an attachment. Use the template as a checklist and record a result for each item:

  • Permitted and required uses and disclosures, plus the prohibition on other uses.
  • Safeguards and the vendor’s Security Rule duties.
  • Written subcontractor assurances with the same restrictions.
  • Reporting of improper uses, security incidents, and breaches.
  • Patient access, amendment, accounting, Privacy Rule duties, and HHS access.
  • Return or destruction of PHI and termination for a material violation.
  • The breach reporting deadline and any optional management, administration, or data aggregation uses.
  • The product and plan covered, and the settings the vendor requires.

If the vendor’s BAA contains every required provision and covers the service you use, the vendor’s form may be acceptable. If it is missing a provision, do not rely on the template itself to fix the problem. Use it to show the vendor exactly what is missing, or adapt it as a separate agreement for both sides to sign. Keep the comparison notes with the signed BAA so the decision is easy to explain later.

Document the Check and Keep the Signed BAA

Sign the BAA before the vendor creates, receives, maintains, or transmits PHI for you. After signing, record the vendor, the plan, and the date in your vendor register. Keep the signed BAA for six years from signing or from when it was last in effect, whichever is later. Review the agreement when the service or plan changes, and when it ends, get the PHI returned or destroyed. If you accepted the vendor’s own BAA, keep your checklist and note where each required provision appears. If you used the template as a separate agreement, keep the final signed version and any addendum together.

The free BAA template is a practical comparison tool because it is built around the provisions HIPAA requires. It helps you ask better questions before PHI is shared, but it does not transfer your HIPAA duties to the vendor. You still check the plan and settings, and your own compliance work stays with you. Treat the template as a reference point, read the vendor’s BAA against it, and document the result before the first record leaves your practice.

Lagos-born, Berlin-educated electrical engineer who blogs about AI fairness, Bundesliga tactics, and jollof-rice chemistry with the same infectious enthusiasm. Felix moonlights as a spoken-word performer and volunteers at a local makerspace teaching kids to solder recycled electronics into art.