BAA Questions to Ask a Vendor Before You Sign

HIPAA fixes the required terms of a business associate agreement and leaves several practical points open: which services are covered, how fast you hear about a breach, who the subcontractors are and what happens to the data at the end. Twelve questions to ask, with the regulation behind each one.

In short

  • HIPAA requires a written business associate agreement before a vendor creates, receives, maintains or transmits PHI for you, and 45 CFR 164.504(e) and 164.314(a) list what it must contain, from permitted uses to return or destruction of PHI at termination.
  • The rule sets only the minimum: a business associate must report a breach without unreasonable delay and no later than 60 calendar days after discovery, but the contract can set a shorter deadline, the content of the notice and the people to call.
  • Before signing, check which of the vendor's services the agreement covers, whether it is the vendor's standard paper, how it binds subcontractors, which incidents it reports and how your data comes back or is destroyed when the contract ends.

Before you sign a business associate agreement, ask the vendor what exactly it covers, how fast and how it will tell you about incidents and breaches, which subcontractors will touch PHI and on what terms, and what happens to the data when the contract ends. HIPAA fixes the minimum content of a BAA in 45 CFR 164.504(e) and 164.314(a). It leaves the details open, and vendors differ on those details.

When do you need a BAA?

Under 45 CFR 160.103, a business associate is a person who, on behalf of a covered entity and other than as a member of its workforce, creates, receives, maintains or transmits PHI for a regulated function or activity, such as claims processing, data analysis, utilization review, quality assurance, billing, benefit management or practice management. It also includes those who provide legal, actuarial, accounting, consulting, data aggregation, management, administrative, accreditation or financial services that involve PHI. The definition names health information organizations and other data transmission services with routine access to PHI, vendors offering a personal health record on behalf of a covered entity, and subcontractors that handle PHI for a business associate.

Under 45 CFR 164.308(b), a covered entity may let a business associate handle electronic PHI only after obtaining satisfactory assurances, documented in a written contract or other arrangement that meets 164.314(a). A business associate needs the same from its own subcontractors. If you are a health tech company, you are often on both sides: you sign a BAA with your customer and you need BAAs with the cloud, messaging and AI vendors underneath you.

What must every BAA contain?

Under 164.504(e)(2), the agreement must set out the business associate's permitted and required uses and disclosures of PHI. It may not allow uses the covered entity itself could not make, with two exceptions: the business associate's own management and administration, and data aggregation for the covered entity's health care operations. It must require the business associate to:

  • Use or disclose PHI only as the contract or the law permits.
  • Use appropriate safeguards and comply with the Security Rule for electronic PHI.
  • Report any use or disclosure not provided for by the contract, including breaches of unsecured PHI.
  • Make sure subcontractors that handle PHI agree to the same restrictions and conditions.
  • Make PHI available for individuals' access and amendment requests and provide the information needed for an accounting of disclosures.
  • Follow the Privacy Rule when carrying out an obligation of the covered entity under it.
  • Make its internal practices, books and records available to HHS.
  • Return or destroy all PHI at termination, if feasible, and keep no copies, or extend the contract's protections to anything that cannot be returned or destroyed.

The agreement must also let the covered entity terminate it if the business associate violates a material term. Section 164.314(a)(2)(i) adds the Security Rule's version: comply with the applicable security requirements, bind subcontractors that handle electronic PHI, and report any security incident the business associate becomes aware of, including breaches of unsecured PHI.

Twelve questions to ask before you sign

Scope

  • Which of your services does the BAA cover, and which are excluded? Large platforms publish lists. AWS says customers should process, store and transmit PHI only in its HIPAA-eligible services. Microsoft lists the cloud services in scope of its BAA. A feature outside the list is outside the agreement, even if it runs in the same account.
  • Is this your standard BAA, and can any of it change? AWS presents a standard addendum that customers review and accept through AWS Artifact. Microsoft offers its BAA by default through its Data Protection Addendum and says it cannot use a customer's BAA, because its services are standardized. With platforms like these, you check fit rather than negotiate. Smaller vendors may accept your paper.
  • What uses of PHI does the agreement permit? The rule only allows uses you could make yourself, plus the vendor's own management and administration and data aggregation for your operations. Ask directly whether the vendor uses PHI, or data derived from it, for product analytics or for training models, and get the answer into the contract.

Incidents and breaches

  • How quickly will you notify us of a breach? Under 45 CFR 164.410, a business associate must notify the covered entity without unreasonable delay and no later than 60 calendar days after discovery. A breach counts as discovered on the first day it is known, or would have been known with reasonable diligence, to the business associate, and knowledge of its employees and agents counts. You have your own deadlines for notifying patients, so ask for a contractual deadline well inside 60 days.
  • What will the notice contain? The rule requires the identity of each individual affected, to the extent possible, and any other available information you need for your own notice to individuals, given at first notice or as it becomes available. Ask for a named contact, a channel and a template.
  • Which security incidents will you report? The Security Rule requires a business associate to report any security incident it becomes aware of. Ask how the agreement handles routine unsuccessful attempts, such as blocked scans, so that the clause is something both sides can actually follow.

Subcontractors and safeguards

  • Which subcontractors will handle our PHI, and do they sign equivalent terms? The rule requires the flow-down. Ask for the current list and for notice before a new subcontractor gets access.
  • What safeguards do you run, and what can you show us? A vendor's risk analysis and risk management are required by 45 CFR 164.308(a)(1) whether or not anyone asks. Ask for a summary of how they are done and when they were last updated.
  • Where does your responsibility end and ours begin? Microsoft states that having its BAA does not by itself make a customer compliant, and AWS ties its BAA to its shared responsibility model. Write down which controls the vendor runs and which you configure.

End of the contract

  • How do we get our data back, and how do you destroy it? The BAA must provide for return or destruction at termination, if feasible, with no copies retained. Ask for the export format, the timeline and written confirmation of destruction, and for how backups are handled.
  • Can we terminate for a material violation, and what happens if one occurs? The agreement must allow it. Under 164.504(e)(1)(ii), a covered entity that knows of a pattern of activity or practice by its business associate that is a material breach is not compliant unless it takes reasonable steps to cure the breach or end the violation and, if those fail, terminates the arrangement where feasible.

What might change for BAAs?

HHS proposed an update to the Security Rule on January 6, 2025. According to a summary by the law firm Bradley, it would have covered entities rely on written verification from business associates, validated by a cybersecurity expert and certified by a person of authority at the business associate, and it would require business associates and subcontractors to notify covered entities within 24 hours of activating a contingency plan. These are proposals, not current law, but asking a vendor today whether it could provide such a verification tells you a lot about its security program.

What does the rule leave to the business negotiation?

The required terms in 164.504(e) do not cover indemnification, limits of liability, insurance or audit rights. Those are business terms between you and the vendor, and they decide who pays when something goes wrong. Bring counsel in for them, and keep the HIPAA terms and the commercial terms consistent, especially around breach costs and cooperation.

How we handle it

We sign a BAA before anyone on our team sees PHI. When a product we build includes an AI assistant, it cites its sources and runs on Claude via AWS Bedrock or Anthropic directly, so the model provider is a known link in the chain that the BAA review has to cover. Onix Systems has built software since 2000 and has 370+ engineers. If you are reviewing the vendor chain behind a health product, talk to one of our engineers. Our free five-day technical audit ends with a written report that maps where PHI goes and which agreements cover each step.