HIPAA and Compliance

Business Associate Agreements: When You Need One

Which vendors count as HIPAA business associates, what a BAA must contain, and how a small practice can audit its agreements in an afternoon.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. The one-question test
  2. Vendors that usually need one
  3. What the agreement must say
  4. Breach clocks to write into the contract
  5. What a missing agreement can cost
  6. Red flags in vendor templates
  7. AI tools are the new blind spot
  8. Audit your agreements in one afternoon
  9. Example: a three-physician practice finds two gaps
  10. Frequently asked questions
  11. References
HIPAA and Compliance: Business Associate Agreements: When You Need OneArticle coverHIPAA AND COMPLIANCEBusiness AssociateAgreements: When YouNeed OneAva Medical IntakeInsightsHIPAA and Compliance: Business Associate Agreements: When You Need OneArticle coverHIPAA AND COMPLIANCEBusiness AssociateAgreements: When YouNeed OneAva Medical Intake

Key takeaways

  • A vendor is a business associate when it creates, receives, maintains or transmits patient information to do a job for your practice.
  • Other providers you send patients to for treatment, and your own employees, are not business associates.
  • The agreement has required contents, including breach reporting, subcontractor flow-down and return or destruction of data at the end.
  • AI tools are the fastest-growing gap: most medical groups still have no formal AI-use policy to catch them.

The one-question test

Ask one question about every outside company your practice pays or uses: does it create, receive, maintain or transmit protected health information so it can perform a service for us? If the answer is yes, HIPAA treats that company as a business associate[1]. The label covers far more than billing companies. The regulation names claims processing, billing and data analysis, plus legal, accounting, consulting, management and administrative services when the work involves your patient information[1].

The definition also reaches down the chain. A subcontractor that handles patient information for your vendor is itself a business associate, and so are data transmission services that routinely access that information, such as e-prescribing gateways and health information organizations[1].

Two groups are outside the definition and cause the most confusion at the front desk. First, a health care provider who receives information to treat the patient is not your business associate, so you do not need a BAA with the cardiologist you refer to or the lab that runs a test. Second, members of your own workforce are covered by your policies and training, not by a contract[1].

Vendors that usually need one

Most practices have more business associates than their files show. The table below sorts common vendors by what they actually touch. Use it as a starting list, then check each contract against the test above.

Common practice vendors and whether a business associate agreement is usually needed. Confirm each case against the definition.
Vendor typeWhat they typically touchBAA usually needed?
EHR or practice management system (cloud hosted)Charts, schedules, demographicsYes
Billing or revenue cycle companyClaims, diagnoses, insurance dataYes
Answering service or call centerCaller names, reasons for calling, callbacksYes
Phone system that stores voicemail, recordings or transcriptsMessages that name patients and symptomsYes
Appointment reminder or texting platformNames, numbers, appointment detailsYes
Managed IT support with system accessAnything on your networkYes
Document shredding companyPaper records before destructionYes
Specialist or hospital receiving a referralRecords needed for treatmentNo (treatment)
Office cleaning crew with no job need for recordsIncidental exposure at mostUsually no, limit access instead

Phone and messaging vendors are the ones practices miss most often. A voicemail that says a patient called about a positive pregnancy test is patient information, and the company storing that audio is maintaining it on your behalf. The same goes for call transcripts and text message logs. Before you sign with any communication vendor, run through our vendor BAA checklist to see where that information hides.

What the agreement must say

Before a vendor touches patient information, the practice must obtain satisfactory assurance, in writing, that the vendor will safeguard it[2]. The regulation spells out what that written contract has to contain[3]. Check any vendor template against this list rather than trusting a heading that says HIPAA.

  1. The uses and disclosures the vendor is permitted and required to make, which cannot exceed what your practice itself could do.
  2. A promise not to use or disclose the information beyond the contract or what law requires.
  3. Appropriate safeguards, including Security Rule compliance for electronic information.
  4. Reporting of any use or disclosure the contract does not allow, including breaches of unsecured information.
  5. Flow-down: subcontractors must agree to the same restrictions and conditions.
  6. Help with patient rights: making information available for access, amendment and an accounting of disclosures.
  7. Privacy Rule compliance when the vendor carries out one of your obligations for you.
  8. Access for HHS to the vendor's internal practices, books and records.
  9. Return or destruction of the information when the contract ends, or continued protection if that is not feasible.
  10. Your right to terminate if the vendor violates a material term.

If you learn that a vendor has a pattern of activity that materially breaches the agreement, you must take reasonable steps to cure it, and terminate the arrangement where feasible if those steps fail. Ignoring a known problem puts the practice itself out of compliance[3].

Breach clocks to write into the contract

The law gives a business associate up to 60 calendar days after discovery to tell you about a breach, and it must identify each affected individual where possible[4]. Your own deadline to notify patients is also measured in days from discovery, with the same 60-day outer limit[5]. If the vendor uses its full allowance, you can be left with almost no time to investigate, draft letters and set up a call line.

That is why many practices negotiate a shorter reporting window, such as a few business days, plus a duty to cooperate with the investigation and to share logs. These terms are not mandatory, but they are reasonable asks, and a vendor that refuses them is telling you something about how it will behave during an incident.

  • Reporting window: a fixed number of business days after discovery, not just the legal maximum.
  • Content: who was affected, what data, how it happened, what has been done to contain it.
  • Cooperation: access to logs and a named contact during the investigation.
  • Costs: who pays for patient letters and any call center if the vendor caused the breach.

What a missing agreement can cost

Sharing patient information with a vendor without an agreement is an impermissible disclosure in its own right, before anything else goes wrong. Civil money penalties are tiered by culpability, starting at a minimum per violation for the did-not-know tier and rising to a calendar-year cap for each identical provision violated[6].

$2,190,294

Calendar-year cap on HIPAA civil money penalties for violations of an identical provision, after inflation adjustment[6]

A missing BAA is also hard to explain away. It is a document you either have or do not have, and it is one of the first things an investigator asks for after a vendor incident.

Red flags in vendor templates

Most vendors will hand you their own BAA template. That is normal and often fine, but read it with the required elements beside you. These are the clauses that most often cause trouble later.

  • Breach reporting tied only to the legal maximum, or limited to incidents the vendor itself decides are significant.
  • A clause letting the vendor use your patient information to train or improve its products without saying whether it is de-identified first.
  • No mention of subcontractors, or a statement that subcontractors are bound only by the vendor's general privacy policy.
  • Return or destruction terms that let the vendor keep copies indefinitely with no limit on further use.
  • Liability caps so low that they would not cover the cost of mailing breach notices.
  • An agreement signed by a reseller rather than the company that actually stores the data.

None of these automatically makes an agreement invalid, but each one shifts risk onto your practice. Ask for changes in writing and keep the email trail with the signed copy, so the next practice manager can see why a clause reads the way it does.

AI tools are the new blind spot

Scribes, chat assistants, transcription tools and phone agents are arriving through individual clinicians and staff, often on a free trial. Each one that processes patient information on your behalf needs the same agreement as any other vendor. Yet most medical groups have no formal policy that would route a new AI tool through a BAA review in the first place[7].

US medical groups with a formal AI governance or AI-use policyMGMA Stat poll, January 2026, 328 responses
US medical groups with a formal AI governance or AI-use policyStacked bar chart. Have a policy: 20%; Developing one: 22%; No policy: 56%.Have a policy: 20% (20%)Developing one: 22% (22%)No policy: 56% (57%)US medical groups with a formal AI governance or AI-use policyStacked bar chart. Have a policy: 20%; Developing one: 22%; No policy: 56%.Have a policy: 20% (20%)Developing one: 22% (22%)No policy: 56% (57%)
  • Have a policy 20%
  • Developing one 22%
  • No policy 56%

Source: Medical Group Management Association (MGMA), 2026[7]

Show the data
ItemValue
Have a policy20%
Developing one22%
No policy56%

The fix is a simple rule written into your policy: no tool may receive patient information until the practice manager has a signed agreement on file. Pair it with a list of approved tools so staff know what they can use today.

Audit your agreements in one afternoon

  1. Pull the vendor list from accounts payable

    Every recurring payment is a candidate. Add free tools staff use, which will not appear in the books.

  2. Apply the one-question test

    Mark each vendor yes, no or unsure. Treat unsure as yes until you have confirmed what the vendor can see.

  3. Match each yes to a signed agreement

    Look for a signed BAA, not just a privacy policy or terms of service page that mentions HIPAA.

  4. Check the contents

    Compare each agreement with the required elements above. Note missing breach reporting or subcontractor terms.

  5. Request or renegotiate

    Send missing agreements to vendors with a deadline. Stop sending patient information to any vendor that will not sign.

  6. File and diary

    Keep agreements and your audit notes for at least six years, the retention period HIPAA sets for required documentation[8]. Set a yearly review date.

Example: a three-physician practice finds two gaps

Example (fictional): Lakeside Family Medicine runs the audit and finds 14 recurring vendors. Nine pass the one-question test. Seven have signed agreements. The two gaps are a texting platform a medical assistant set up for recall messages and an after-hours answering service whose contract predates the current owner.

The practice manager pauses recall texts until the platform signs, asks the answering service for its current BAA template, and finds it lacks any breach reporting timeline. She negotiates a short reporting window, files both agreements with the audit notes, and adds the rule that new tools need sign-off before use. Total time: one afternoon plus two follow-up emails.

Frequently asked questions

Do we need a BAA with a hospital or specialist we refer patients to?

No. A health care provider that receives information to treat the patient is excluded from the business associate definition. You still share only what the referral needs.

Is a vendor's online terms of service enough?

Only if it actually contains the required BAA terms and your practice has accepted it. A privacy page that says the vendor is HIPAA compliant does not create an agreement.

Do our own employees sign a BAA?

No. Workforce members are covered by your policies, training and sanctions, not by a business associate agreement.

How long do we keep old BAAs?

Keep them, and records of your reviews, for at least six years from creation or from when they were last in effect.

References

  1. Legal Information Institute, Cornell Law School (current). 45 CFR § 160.103 - Definitions (business associate) (opens in a new tab) ↑

  2. Legal Information Institute, Cornell Law School (current). 45 CFR § 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) ↑

  3. Legal Information Institute, Cornell Law School (current). 45 CFR § 164.504 - Uses and disclosures: Organizational requirements (opens in a new tab) ↑

  4. Legal Information Institute, Cornell Law School (current). 45 CFR § 164.410 - Notification by a business associate (opens in a new tab) ↑

  5. Legal Information Institute, Cornell Law School (current). 45 CFR § 164.404 - Notification to individuals (opens in a new tab) ↑

  6. Legal Information Institute, Cornell Law School (current). 45 CFR § 102.3 - Penalty adjustment and table (opens in a new tab) ↑

  7. Medical Group Management Association (MGMA) (2026). AI governance in medical group practices: Rules for the humans in the loop (opens in a new tab) ↑

  8. Legal Information Institute, Cornell Law School (current). 45 CFR § 164.530 - Administrative requirements (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo