24/7 live agents 800-677-7406

What Is a Business Associate Agreement? A BAA Guide for Practices Using an Answering Service

Nurse in a hospital room checking a secure messaging app on her phone

If your practice hands its phones to an outside company after hours, that company will hear patient names, symptoms, medication questions, and callback numbers. Before that happens, HIPAA expects a specific document to be in place. So what is a business associate agreement, what has to be in it, and what should you ask an answering service before you sign one?

This guide walks through the basics in plain language. It’s general information, not legal advice. Your compliance officer or attorney should review any agreement before you sign it. (For how we set up medical accounts, see our medical answering service page.)

What is a business associate agreement?

A business associate agreement (BAA) is a written contract between a HIPAA covered entity, such as a physician practice, clinic, or health plan, and a vendor that creates, receives, maintains, or transmits protected health information (PHI) on the covered entity’s behalf. HIPAA calls that vendor a “business associate.”

The agreement does two jobs. It sets limits on what the vendor may do with your patients’ information, and it obligates the vendor to protect that information and tell you when something goes wrong. Without a BAA, a covered entity generally may not share PHI with a business associate at all.

Who counts as a business associate?

The definition in the HIPAA regulations (45 CFR 160.103) is broad. Common examples include billing companies, IT and cloud hosting providers, transcription services, shredding companies, outside consultants, and answering services. If a vendor’s work for you involves handling PHI, it is likely a business associate.

There is a narrow exception for “conduits,” such as a phone carrier or the postal service, that only transmit information and don’t store it beyond what transmission requires. An answering service doesn’t fit that exception. Its agents listen to callers, write down health details, store messages, and deliver them to your providers, so it needs a BAA.

Who needs a business associate agreement?

The covered entity is responsible for having one in place with each business associate. Business associates must also have BAAs with their own subcontractors that handle PHI. If your answering service uses an outside messaging platform or hosting provider that stores your patients’ messages, that vendor should be covered by a subcontractor agreement on the answering service’s side.

Practice administrators talking in a clinic hallway beside a signed agreement

Business associate agreement requirements: what must be in a BAA

The required contents are set out in the HIPAA Privacy Rule at 45 CFR 164.504(e) and, for electronic PHI, the Security Rule at 45 CFR 164.314(a). HHS publishes sample business associate agreement provisions on its website that many organizations use as a starting point. At a minimum, a BAA should:

  • Describe the permitted and required uses and disclosures of PHI, and bar the vendor from using or disclosing it in any other way except as the law requires.
  • Require appropriate safeguards, including compliance with the HIPAA Security Rule for electronic PHI.
  • Require the vendor to report any use or disclosure not allowed by the contract, including breaches of unsecured PHI and security incidents.
  • Require the vendor to ensure that any subcontractors that handle PHI agree to the same restrictions and conditions.
  • Require the vendor to help you meet patients’ rights to access and amend their information and to receive an accounting of disclosures, where those apply.
  • Require the vendor to make its internal practices, books, and records about PHI available to HHS when HHS is determining compliance.
  • Require the vendor to return or destroy PHI when the contract ends, if feasible, and to keep protecting anything it can’t return or destroy.
  • Allow you to terminate the contract if the vendor violates a material term.

On breach timing, the HIPAA Breach Notification Rule requires a business associate to notify the covered entity without unreasonable delay and no later than 60 calendar days after discovering a breach of unsecured PHI. Many BAAs set a shorter window. That’s a point worth negotiating, since your own notification clock depends on how fast you find out.

What a BAA does and doesn’t do

A signed BAA is necessary, but it isn’t proof that a vendor protects PHI well. It’s a set of promises. What matters is whether the vendor’s day-to-day process keeps those promises.

It also doesn’t shift your obligations away from you. Your practice still decides what information the service should collect, who should receive messages, and how urgent calls should be handled. Since the 2013 HIPAA Omnibus Rule, business associates are directly liable for certain HIPAA violations, but a covered entity that knows a business associate is violating the agreement and does nothing can still be on the hook.

And a BAA doesn’t make anyone “HIPAA certified.” HHS doesn’t recognize or endorse private HIPAA certifications. When you evaluate a vendor, look at the agreement and the practices behind it, not a badge. Our guide to what a HIPAA compliant answering service means covers that in more depth.

Why an answering service needs a BAA

Think about a single after-hours call. A parent calls about a child’s fever. The agent records the child’s name, date of birth, symptoms, the parent’s phone number, and the name of the provider the family sees. That message is PHI. It’s stored in the answering service’s system, sent to your on-call provider, and kept in a log your office reviews in the morning.

Every step of that path is something the BAA should govern: what the agent may collect, how the message is sent, who inside the vendor can see it, how long it’s kept, and what happens if it’s sent to the wrong person. The phone side of this has its own rules, which we cover in HIPAA rules for phone calls and voicemail.

Team reviewing a HIPAA risk assessment on a screen in a meeting room

Questions to ask an answering service about its BAA

Use these before you sign. A vendor that handles medical calls every day should answer them without hesitation.

  1. Will you sign a BAA, and whose form do we use? Some vendors sign the practice’s agreement; others have their own. Either can work if it contains the required provisions. Have counsel compare it against the HHS sample provisions.
  2. How are messages delivered to our providers? Ask whether PHI ever goes out by ordinary SMS or unencrypted email, and what secure options exist, such as a secure texting app or a client portal.
  3. Who can see our patients’ information? Ask how access is limited to staff who need it, and whether agents who log in to your EMR or scheduling system are handled differently.
  4. How are agents trained on privacy? Ask what HIPAA training covers and how often it’s repeated.
  5. Are calls recorded, and how long are messages kept? Recordings and message logs are both PHI. Know what exists, where it lives, and what happens to it when the contract ends.
  6. Which subcontractors touch our data? Messaging platforms and hosting providers should be covered by subcontractor agreements.
  7. How fast will you tell us about a breach or a misdirected message? Compare the answer with the BAA’s reporting clause.

Our guide on how to choose a medical answering service covers the rest of the evaluation: greetings, escalation, and on-call routing.

How Southern Voices handles BAAs

We sign BAAs with our healthcare clients. Our agents are HIPAA-trained. Messages reach your team by secure texting or through our client portal, both included, and urgent calls can be patched live to your on-call provider. We don’t record calls. When agents need direct access to a client’s EMR or scheduling system, or when a client asks for it, the account is staffed by US-only personnel. For hospitals, home health, and larger groups, our healthcare call center page explains how that scales.

Frequently asked questions

What is a business associate agreement in simple terms?

It’s a contract between a healthcare provider or health plan and a vendor that handles patients’ protected health information for it. The contract limits how the vendor may use that information, requires safeguards, and requires the vendor to report breaches.

Does an answering service need to sign a BAA?

Generally, yes. An answering service that takes and stores messages containing patient information is acting as a business associate, not a conduit, so the practice should have a BAA in place before the service handles calls. Confirm the details with your compliance advisor.

What happens if we don’t have a BAA with a vendor that handles PHI?

Sharing PHI with a business associate without a BAA can be a HIPAA violation for the covered entity, and HHS has issued penalties in cases where a required agreement was missing. If you find a gap, talk to counsel and get an agreement in place.

Is a BAA the same as HIPAA certification?

No. A BAA is a contract. There is no official HIPAA certification for vendors, and HHS doesn’t recognize private certifications. Judge a vendor by its agreement and the safeguards it actually uses.

Can we use our own BAA form instead of the vendor’s?

Often, yes. Many vendors will review and sign the practice’s form. What matters is that the final agreement contains the provisions HIPAA requires and that both sides understand the reporting timelines.

Share this article

Related articles

Talk to a live agent, 24/7/365

Live, bilingual agents answering calls since 1995. Tell us how your calls work and we’ll quote a plan around them.

800-677-7406