On this page

A BAA is required whenever a HIPAA covered entity, or one of its business associates, lets a vendor create, receive, maintain or transmit protected health information (PHI) on its behalf. The covered entity may do that if it “obtains satisfactory assurance that the business associate will appropriately safeguard the information,” and those assurances must be in a written contract or other written agreement (45 CFR 164.502(e)). No BAA is needed when a provider sends PHI to another provider for treatment, or when a carrier such as the postal service only transports it. Curve Compliance signs a BAA on every plan and strips PHI before data reaches an ad platform.

Book a call. Running ads for a clinic or telehealth practice? Curve signs a BAA on every plan and sends each ad platform only a fixed list of fields, server-side. Book a call with Curve.

When is a BAA required?

The test is what the vendor does with PHI, not what it calls itself. Under 45 CFR 160.103, a business associate is a person or company that, other than as a member of your workforce, “creates, receives, maintains, or transmits protected health information” for a function or activity HIPAA regulates on a covered entity's behalf, or that provides services such as legal or accounting work involving PHI. HHS gives examples: “Some examples of activities performed on behalf of a covered entity by a business associate include claims processing or administration, data analysis, billing, and practice management” (HHS business associates guidance).

Once a vendor meets that definition, the BAA isn't optional. HIPAA requires the satisfactory assurances to “be documented through a written contract or other written agreement or arrangement with the business associate” (45 CFR 164.502(e)), and 45 CFR 164.504(e) lists what that contract must contain, from the permitted uses of PHI to returning or destroying it at the end. The Security Rule repeats it for electronic PHI (45 CFR 164.308(b)). HHS's current list of business associates includes cloud and IT vendors (such as EHR vendors and managed service providers) that handle ePHI for a covered entity, health app developers under contract to serve its patients, and transcription services (HHS business associates guidance).

When is a BAA not required?

In a short list of cases, HHS says, “a covered entity is not required to have a BAA in place before PHI may be disclosed to the person” (HHS business associates guidance). One is treatment: “A hospital is not required to have a BAA with the specialist to whom it refers a patient and transmits the patient’s medical chart for treatment purposes.” Another is the conduit, a carrier that moves PHI without using it. HHS says “The conduit exception is limited to entities that only provide transmission services for PHI (whether in electronic or paper form), including any temporary storage of PHI,” and “Entities that access PHI on a regular or frequent basis to perform a service on behalf of a covered entity are not conduits.”

Vendor or relationshipBAA required?Why
Telehealth video or messaging platformYesProviders must use vendors that will sign one (HHS telehealth guidance)
Phone carrier that only connects the callNoA conduit with transient access (HHS audio-only guidance)
Phone or telehealth app that stores recordings or transcriptsYesMore than a conduit (HHS audio-only guidance)
EHR, scheduling or intake software the vendor hostsYesIt hosts patient information (HHS software FAQ)
Software you install, where the vendor never sees PHINoNo access to PHI (HHS software FAQ)
Cloud host that stores encrypted PHI without the keyYesHHS treats it as a business associate anyway (HHS cloud guidance)
Ad or analytics tracking vendor that receives PHIYesHHS online tracking bulletin
Specialist or lab you send a patient to for treatmentNoTreatment exception in 45 CFR 160.103
Health plan you bill for paymentNoEach acts for itself as a covered entity (HHS)
Cleaning service or electricianNoAny contact with PHI is incidental (HHS)
Bank or card processor taking patient paymentsNoNormal payment services are not on your behalf (HHS)
Your vendor's own subcontractor that handles your PHIYes, with your vendorSubcontractors are business associates too (45 CFR 160.103)

Edge cases turn on facts, such as how often a vendor sees PHI and whether it stores any, so talk to your counsel before you rely on an exception.

Is a BAA required for telemedicine?

Yes, for most of the technology a telehealth practice runs on. HHS's telehealth guidance says “Covered health care providers and health plans must use technology vendors that comply with the HIPAA Rules and will enter into HIPAA business associate agreements in connection with the provision of their video communication products or other remote communication technologies for telehealth” (HHS telehealth guidance). That covers the video platform and patient messaging; the EHR, intake and scheduling tools need one too when the vendor hosts patient information (HHS FAQ on software vendors).

The line HHS draws is between a carrier and a vendor that keeps PHI. A provider using an ordinary phone for an audio visit needs no BAA with the phone company when it “is only connecting the call,” but “a covered entity must enter into a BAA with a vendor that is more than a mere conduit for PHI,” such as an app that stores recordings or transcripts in its own cloud (HHS audio-only telehealth guidance). The pandemic-era leniency is over: the COVID-19 enforcement discretion notices “expire at 11:59 p.m. on May 11, 2023,” and the transition period for telehealth tools ended at 11:59 p.m. on August 9, 2023 (Federal Register, April 13, 2023).

For a cash-pay telehealth company, the first question is whether HIPAA applies at all. A provider is a covered entity if it is “A health care provider who transmits any health information in electronic form in connection with a transaction covered by this subchapter” (45 CFR 160.103), such as an electronic insurance claim. See does HIPAA apply to cash-pay telehealth for how that test plays out, and HIPAA compliant telehealth platforms for which video tools sign a BAA.

Do ad and tracking vendors need a BAA?

Yes, when they receive PHI. HHS's bulletin on online tracking says “Regulated entities must ensure that all tracking technology vendors have signed a BAA and that there is an applicable permission prior to a disclosure of PHI” (HHS online tracking bulletin). In its example, a clinic's booking page sends appointment details and the visitor's IP address to a tracking vendor, and “the tracking technology vendor is a business associate, and a BAA is required.” In June 2024 a federal court vacated one part of the bulletin, on tracking that only links a visitor's IP address with a visit to an unauthenticated public page about specific health conditions or providers; the rest is still posted on HHS's site.

For an ad platform that won't sign a BAA (see which ad platforms sign a BAA), HHS describes another route: a clinic can “establish a BAA with another vendor, for example a Customer Data Platform vendor, that will enter into a BAA with the regulated entity to de-identify online tracking information that includes PHI,” which then passes only de-identified information to the platforms (HHS online tracking bulletin). Curve Compliance signs a BAA on every plan and strips PHI before data reaches an ad platform.

Do a vendor's subcontractors need a BAA?

Yes, with the vendor. 45 CFR 160.103 counts as a business associate “A subcontractor that creates, receives, maintains, or transmits protected health information on behalf of the business associate,” and HHS says “A business associate must establish a BAA with its subcontractor before disclosing PHI to the subcontractor for work to be done for a covered entity” (HHS business associates guidance). You don't sign those agreements yourself: “A covered entity is not required to establish a BAA directly with a subcontractor of its business associate.” 45 CFR 164.504(e) makes binding subcontractors to the same restrictions a required term; see our BAA template guide for the full clause list.

What if a vendor stores only encrypted data?

It still needs a BAA. HHS says a cloud service provider that stores electronic PHI is a business associate, and “This is true even if the CSP processes or stores only encrypted ePHI and lacks an encryption key for the data” (HHS cloud computing guidance). Skipping the agreement is itself a violation: when a covered entity uses a cloud provider to maintain ePHI without a BAA, HHS says it “is in violation of the HIPAA Rules” (HHS FAQ on cloud providers without a BAA). For the storage vendors that sign one, see HIPAA compliant cloud storage.

How Curve Compliance helps

Curve Compliance replaces browser ad pixels with one script and sends conversions server-side from Curve's servers to Meta Conversions API, Google Ads, TikTok, Microsoft Advertising and LinkedIn. Each platform receives only a fixed list of fields, and Curve detects PHI-like patterns, such as condition names, form answers and emails in URLs, before data reaches an ad platform and flags them so they can be stopped at the source. Event Logs show what Curve sent to each platform and what the platform accepted.

Curve signs a BAA on every plan and is SOC 2 Type II. It keeps ad attribution when a patient leaves your site to book in tools such as IntakeQ, Calendly, Acuity and Jane App, and Curve Forms are intake and lead forms hosted by Curve under the BAA Curve signs on every plan, with the ad and campaign that brought each person attached to the lead. Curve's team does the setup, typically live in about a week. See the BAA Directory for where other vendors stand, then book a call to review what your site sends today.

Sources, checked November 20, 2026: 45 CFR 160.103; 45 CFR 164.502(e); 45 CFR 164.504(e); 45 CFR 164.308(b); HHS business associates guidance; HHS cloud computing guidance; HHS FAQ on cloud providers without a BAA; HHS FAQ on software vendors; HHS FAQ on providers as business associates; HHS FAQ on self-certification; HHS online tracking bulletin; HHS telehealth guidance; HHS audio-only telehealth guidance; Federal Register, April 13, 2023.

Frequently Asked Questions

When is a BAA required?

A BAA is required whenever a vendor creates, receives, maintains or transmits PHI on behalf of a covered entity or another business associate. It is not required for disclosures to another provider for treatment, for pure conduits such as the postal service, or for services where any contact with PHI is incidental.

Is a BAA required for telemedicine?

Yes: HHS says telehealth providers must use technology vendors that “will enter into HIPAA business associate agreements” for their video and other remote communication tools (HHS telehealth guidance), and hosted EHR and scheduling vendors that hold PHI need one too. The COVID-19 leniency for telehealth tools without a BAA ended in 2023.

Do we need a BAA with our phone provider?

Not if the carrier only connects calls: HHS treats a phone company with transient access as a conduit. You do need one with a phone or telehealth app that stores recordings or transcripts (HHS audio-only telehealth guidance).

Is a BAA required between two providers?

Not for treatment: “any covered health care provider (or other covered entity) may share protected health information with a health care provider for treatment purposes without a business associate contract.” A BAA is needed before one provider gives another access to PHI to do other work for it, such as training medical students (HHS FAQ on providers as business associates).

Is a BAA required with my website host?

Yes, if the host stores or processes PHI, such as form submissions or a patient portal, because HHS treats a software company that hosts patient information on its own server as a business associate (HHS FAQ on software vendors). See HIPAA compliant website hosting.

Can a vendor's HIPAA certification replace a BAA?

No. Asked whether business associates can self-certify instead, HHS answers that a covered entity “is required to enter into a contract or other written arrangement with a business associate that meets the requirements at 45 CFR 164.504” (HHS FAQ on self-certification).

Does an email provider need a BAA?

Generally yes, if it stores messages with PHI for you. The closest HHS text, its cloud guidance, counts email message storage as a cloud service and says “a CSP that maintains ePHI for the purpose of storing it will qualify as a business associate, and not a conduit” (HHS cloud computing guidance). See HIPAA compliant email providers for who signs one.

Talk to Curve Compliance

Book a call. Want ad tracking that keeps PHI away from ad platforms, under a BAA signed on every plan? Curve's team does the setup, typically live in about a week. Book a call with Curve.