Business Associate Agreement (BAA) for Healthtech SaaS: What US Customers Will Ask You to Sign

By Prakhar Rai, Founder, My Legal Pal. Advocate, Bar Council of India. LL.B, NLSIU Bangalore. Master of Business Laws.

Quick answer: Yes, if your software creates, receives, maintains or transmits protected health information (PHI) for a US healthcare provider, health plan or clearinghouse, you are a business associate under HIPAA, and the customer must have a written Business Associate Agreement (BAA) with you before you handle that data. HHS lists cloud providers, software vendors and app developers working for covered entities as examples. Encryption without a key does not take you out of scope. The BAA must contain the terms in 45 CFR 164.504(e). Everything else in the document, including breach timing, liability, audit rights and what you may do with de-identified data, is negotiable.

Key takeaways

  • Who needs one: a SaaS vendor that handles PHI on behalf of a covered entity, and any subcontractor of that vendor that touches the PHI.
  • What the law fixes: the BAA must set permitted uses, bar other uses, require safeguards, require reporting of breaches, flow terms down to subcontractors, support access and amendment rights, open your records to HHS, return or destroy PHI at the end, and let the customer terminate for a material violation.
  • What the law leaves open: most of what buyers actually push on, such as 24-hour breach notice, uncapped liability, audit rights and de-identification.
  • No “HIPAA certified” badge: HHS says its Office for Civil Rights does not endorse, certify or recommend technology or products.
  • You are directly liable: business associates answer to HHS for impermissible uses, Security Rule failures, missing breach notices and missing subcontractor BAAs.
  • The chain matters: if you pass PHI to your cloud host, support desk or an AI model provider, you need a BAA with each before you do it.
  • Not every health app is covered: an app a consumer picks for themselves is usually outside HIPAA, though other rules may apply.

If you build software for hospitals, clinics, insurers or digital health companies in the United States, the first enterprise contract you receive will often arrive with a BAA attached and a deadline. This guide explains what the document has to say, what buyers usually add, and where a SaaS vendor can push back. It is based on the HIPAA Rules and HHS guidance as they stand in November 2026.

My Legal Pal is an international team of contract lawyers with US law experience. We are not a US law firm. This guide is general information, and a US-qualified lawyer should review your actual BAA, particularly if your product handles clinical data or you operate in states with stricter health privacy laws.

The first request usually comes late in the sales cycle, from the customer’s procurement or security team, with a form BAA that was written for a hospital’s other vendors. The useful habit is to read it against your actual product before the call, not after.

Do I need a Business Associate Agreement (BAA) for Healthtech SaaS customers?

Yes, if you handle PHI for a covered entity or for another business associate. No, if you never touch PHI.

HIPAA’s Privacy and Security Rules apply to covered entities (most health care providers, health plans and health care clearinghouses) and to their business associates. HHS describes a business associate as a person who performs regulated functions or services for a covered entity that involve PHI. Its examples include a cloud service provider that creates, receives, maintains or transmits electronic PHI, an IT or software vendor such as an EHR vendor, and a health care app developer that handles patient PHI for patient management services on behalf of a covered entity.

A covered entity may disclose PHI to a business associate only after getting satisfactory assurances, in the form of a written contract. That contract is the BAA. If your customer is a covered entity and your product holds, processes or moves its patient data, the BAA is not optional for either of you.

Is data safe from HIPAA if it is encrypted and I hold no key?

No. HHS’s cloud computing guidance says a cloud provider that stores only encrypted ePHI, with no decryption key, is still a business associate. In HHS’s words, lacking a key does not exempt a provider from business associate status and obligations, because encryption alone does not maintain the integrity and availability of the data.

The “conduit” exception is narrow. HHS limits it to transmission-only services. If your service stores ePHI, even if you never look at it, you are a business associate and not a conduit.

Does HIPAA cover my health app?

Only if you work on behalf of a covered entity or another business associate. OCR’s health app scenarios turn on who hired you and who pays you.

Situation Business associate?
A consumer downloads your app and enters their own data, with no provider involved No
A provider recommends your app, and the patient chooses to send data to the provider No, by itself
A provider contracts you to manage patients, and data flows into the provider’s EHR Yes
A health plan offers your app to its members under a contract Yes, for that version of the product
You also sell a separate direct-to-consumer version Not for that version, if the data stays separate

If you are not a business associate, other rules can still apply. The FTC’s Health Breach Notification Rule covers many health apps and similar technologies that are outside HIPAA, and the FTC says it does not apply to organisations covered by HIPAA. Our guide to privacy policy drafting covers the consumer-facing side.

What must a BAA contain?

The Privacy Rule, at 45 CFR 164.504(e), lists what the contract must do. HHS’s own sample provisions follow the same list. This table puts each requirement in product terms.

What the BAA must do In practice for a SaaS vendor
Set the permitted and required uses and disclosures of PHI Your use must be limited to providing the service. The contract may also allow use for your proper management and administration, and data aggregation for the customer’s health care operations
Bar any other use or disclosure You cannot use the data for your own product analytics, marketing or model training unless the BAA allows it and the law permits
Require appropriate safeguards, including the Security Rule for ePHI You need real administrative, physical and technical safeguards, not just a promise
Require reporting of unauthorised uses or disclosures, including breaches of unsecured PHI You need an incident process that can meet the contract’s deadline
Flow the same restrictions to subcontractors Your hosting, support and tooling vendors must sign matching terms
Support access, amendment and accounting of disclosures Your product must be able to give the customer what it needs to answer patient requests
Make internal practices, books and records available to HHS You must be willing to open records to regulators
Return or destroy PHI at the end, where feasible You need a deletion process and a rule for what happens when deletion is not feasible
Allow the customer to terminate for a material violation The customer can leave if you breach a material term

The BAA can also let you use PHI for your proper management and administration, and disclose it for those purposes if the disclosure is required by law, or if the recipient gives reasonable confidentiality assurances and agrees to report known breaches.

Is the HHS sample BAA enough?

No, and it is not required. The HHS sample provisions say they are only sample language, that using them is not required for HIPAA compliance, that they may not be enough on their own to make a binding contract under state law, and that using them does not replace consulting a lawyer. Treat them as a checklist, not as your contract.

Is a BAA the same as a DPA?

No. A BAA is a HIPAA contract for PHI. A data processing agreement is the contract GDPR and similar laws require between a controller and a processor. A healthtech SaaS company selling to both US and EU customers may need both, covering different data and different law. See our guide to data processing agreement drafting for the GDPR side.

What will US customers ask you to sign beyond the legal minimum?

The required terms are short. Most negotiation happens on the points the rules leave open. These are the requests we expect from healthcare procurement and security teams, and a sensible position for a SaaS vendor on each. They are practice points, not legal requirements.

Customer request What the law says A reasonable vendor position
Breach notice within 24 or 48 hours A business associate must notify the covered entity without unreasonable delay and no later than 60 calendar days after discovery. A breach is treated as discovered when it is known, or would have been known with reasonable diligence Accept a shorter window you can actually meet, with a clear start point (“confirmed breach”), and a separate lighter duty for suspected incidents
Report every “security incident” The Security Rule defines a security incident to include attempted as well as successful unauthorised access Agree that unsuccessful attempts such as pings and failed logins are reported in aggregate, on request, not one by one
Uncapped liability and indemnity for breach HIPAA does not set how losses are shared between the two companies Seek a cap tied to fees or a higher “super cap” for data breach, with a clear list of reimbursable breach costs. See our notes on indemnity and limitation of liability
Right to audit your systems The BAA must make your books and records available to HHS. It does not give each customer an audit right Offer an independent report or questionnaire once a year, with an on-site audit only after an incident
Approval of every subcontractor You must have a BAA with each subcontractor before disclosing PHI Offer a current list with notice and a right to object, rather than prior approval of each change
Data stays in the US HHS says storing ePHI overseas may raise risks that should be part of a risk analysis Say where data is hosted, and agree what notice you give before moving it
Return and deletion at the end The BAA must require return or destruction where feasible Set a time limit, a format, and a clear rule for backups that cannot be wiped at once
BAA overrides the main contract Not a legal rule Accept that the BAA governs PHI, but make sure the liability cap and dispute terms in your SaaS agreement and MSA are not silently overridden
Insurance Not a legal rule State what cover you hold, and ask for the minimum limit to be written in

Can I use customer PHI to train or improve my product, including AI?

Only if the BAA allows it, and in practice usually only after de-identification. HHS treats de-identification as a use of PHI. Its FAQ says a business associate may de-identify PHI only to the extent its BAA authorises it. Once PHI is de-identified under the Privacy Rule, it stops being PHI and can be used for other purposes, subject to other laws.

So the clause to look for is whether the BAA, or the main contract, says you may de-identify the data and what you may do with the result. Many buyer forms are silent or forbid it. If your product depends on learning from customer data, raise this at the start of the negotiation, not after signing. Training a model on identifiable PHI is a use beyond providing the service, and would need clear authority in the BAA and a basis under the Privacy Rule.

Do I need BAAs with my own vendors?

Yes, if they create, receive, maintain or transmit PHI for you. HHS says a business associate must have a BAA with its subcontractor before disclosing PHI to it, and that a subcontractor handling PHI for a business associate is itself a business associate. The customer does not have to sign a contract directly with your subcontractor.

List every vendor that could touch PHI: cloud hosting, backup, email, customer support desks, logging and monitoring tools, analytics, and any AI model provider your product calls. Each needs a BAA that matches the terms you gave your customer. If a vendor will not sign one, keep PHI away from it. Our guide to AI vendor contracts covers the model provider side.

One further caution on tracking tools: HHS’s online tracking guidance was vacated in part by a federal court in June 2024, and HHS said it was evaluating next steps. The sensible habit has not changed. Do not send PHI to analytics or advertising tools that have not signed a BAA.

Am I directly liable, or only through my customer?

Directly. HHS’s fact sheet lists what OCR can enforce against a business associate. It includes failing to comply with the Security Rule, failing to give breach notice to a covered entity or another business associate, making impermissible uses and disclosures, failing to limit PHI to the minimum necessary, failing to enter BAAs with subcontractors, and failing to take reasonable steps to address a subcontractor’s material breach. HHS also notes that OCR has no authority to enforce the “reasonable, cost-based fee” limit for access requests against business associates. That duty stays with the covered entity.

Penalties depend on how much the violator knew and how it responded, and the dollar amounts are adjusted over time. Check the current figures in the HHS penalty rules (45 CFR 160.404 and 45 CFR 102.3) at the time you rely on them.

Is there a “HIPAA certification” I can show customers?

No. HHS’s cloud guidance says OCR does not endorse, certify or recommend specific technology or products. A badge from a vendor or a consultant is not a legal status. What customers can fairly ask for is evidence that you carry out a risk analysis, apply Security Rule safeguards, train staff, and can respond to an incident. Independent security reports can help in a sales discussion, but they do not replace the BAA.

Avoid marketing claims such as “HIPAA certified” or “HIPAA approved”. Say “we sign BAAs” and describe your safeguards instead. Our guide to legal documents every SaaS startup needs in the USA sets out the wider paper trail.

What happens when a breach occurs?

When you discover a breach of unsecured PHI, you notify the covered entity. The Breach Notification Rule gives a ceiling of 60 calendar days from discovery, and your contract may set something shorter. The notice must identify, as far as possible, each person affected, and give the other information the covered entity needs for its own notice to individuals. You may send that further information after the first notice, as it becomes available.

Prepare before a customer asks. Decide who confirms a breach, who talks to customers, what your first notice contains, and how you track the clock. Our data breach response playbook walks through the steps. Your uptime and recovery commitments also matter, since HHS says a cloud agreement can address availability and backup, so read our guide to a service level agreement alongside the BAA.

Is the HIPAA Security Rule changing?

HHS issued a proposed rule on 27 December 2024 to strengthen cybersecurity protections for ePHI, including for business associates. HHS’s page says that while it works on the rulemaking, the current Security Rule remains in effect. Plan for the existing rule today, and watch for a final rule, because a stricter rule would flow into customer BAAs and security schedules.

Pre-signing checklist for a SaaS vendor

  1. Confirm that your product actually handles PHI for a covered entity. If not, say so in writing and do not sign a BAA you do not need.
  2. Map where PHI goes: your app, databases, logs, support tickets, backups, test environments and every vendor.
  3. Check you can sign a BAA with each vendor on that map, before PHI goes to it.
  4. Compare the customer’s draft with the required terms in 45 CFR 164.504(e), then with your product.
  5. Negotiate the breach window, the definition of a security incident, liability, audits and subcontractor approval.
  6. Settle de-identification and any use of data to improve your product.
  7. Fix the deletion and return process, and the treatment of backups.
  8. Make sure the BAA and the main agreement do not conflict on liability or term.
  9. Check state health privacy laws that may apply to your customer or its patients.
  10. Keep a signed copy, and a register of every BAA you have signed and received.

Get a lawyer to review your BAA

If a customer has sent you a BAA and you need a lawyer to compare it against your product, negotiate the open terms, and line it up with your SaaS and vendor contracts, our technology lawyers for tech startups, SaaS and AI platforms can help.

Quick answers

Do I need a BAA to sell software to a US hospital? Yes, if your software handles PHI for the hospital. HHS treats cloud, software and app vendors working for covered entities as business associates, and the hospital must have a BAA with you first.

Is a SaaS company that never views the data still a business associate? Yes. HHS says a cloud provider with only encrypted ePHI and no key is still a business associate, and the conduit exception covers only transmission-only services.

Who signs a BAA, the customer or the vendor? Both. The covered entity and the business associate sign. A business associate also signs BAAs with its own subcontractors that handle PHI.

How long do I have to report a breach to my customer? The rule sets an outer limit of 60 calendar days from discovery. Many customer contracts require less, so check the BAA.

Can I use customer data to train AI models? Only if the BAA allows it and the Privacy Rule permits it. HHS says a business associate may de-identify PHI only as its BAA authorises.

Is there a HIPAA certificate for SaaS? No. HHS says OCR does not endorse, certify or recommend specific technology or products.

Does HIPAA apply to a consumer health app? Not if the consumer chose the app and no provider or plan hired you. It applies if you work on behalf of a covered entity. Other rules, such as the FTC’s Health Breach Notification Rule, may still apply.

Is the HHS sample BAA enough? No. HHS says its sample language is not required, may not be enough for a binding contract under state law, and does not replace advice from a lawyer.

A note on who we are

My Legal Pal is an international team of contract lawyers with US law experience. We aren’t a US law firm, and we aren’t a local firm in every country mentioned above. This article is general information and not legal advice on your facts. Have a lawyer qualified in the governing jurisdiction check the details before you act.


About the author. Prakhar Rai is an advocate enrolled with the Bar Council of India and the founder of My Legal Pal. He holds an LL.B from NLSIU Bangalore and a Master of Business Laws, and works on contract drafting, review and disputes for founders and businesses across borders. Full profile

Leave a Reply

Your email address will not be published. Required fields are marked *

Are you human? Please solve:Captcha