Practical guide · November 17, 2026
Your vendor signed a BAA. What HIPAA work still belongs to you?
A signed business associate agreement helps define how a vendor handles protected health information. It does not complete your practice's risk analysis or decide how your staff should use the service. For a HIPAA-regulated practice adopting a cloud platform, the next task is to connect the agreement to the way information and responsibilities move through the practice.
That means examining both sides. The vendor has obligations of its own; your team still needs to understand the service, make operating decisions and carry out the work assigned to it.
What the agreement establishes
HHS describes a business associate contract as establishing permitted uses and disclosures of PHI and requiring safeguards, reporting and other provisions. A business associate can also have direct obligations under HIPAA. It is inaccurate to treat the agreement as merely a promise about the vendor's servers—or as a transfer of all responsibility away from the practice. See HHS's business associate contract guidance.
Read the executed agreement alongside the services actually purchased. Identify which organization is contracting, what service is covered and which obligations the documents assign. A general statement that a company “signs BAAs” does not explain your particular arrangement.
For cloud services, HHS explicitly says the customer should understand the solution so it can conduct its own risk analysis and establish risk-management policies. It also discusses service-level agreements covering matters such as availability, recovery, data return and security responsibilities. Those terms should be consistent with the BAA and HIPAA rules. HHS cloud guidance
Follow a patient workflow beyond the platform
Hypothetical example: a practice adopts a telehealth service. An administrator creates staff accounts. A clinician downloads a visit summary to send through another approved system. A temporary staff member leaves at the end of the month.
The vendor agreement alone does not tell the practice manager whether that downloaded file remains on a laptop, who approved the temporary account or whether somebody removed it. Those are questions about how the practice operates the service.
Start with one workflow rather than a list of software features. Who enters information? Who can see it? Where does an export go? Who knows that a worker has left, and who acts on that information? Use a test record for the walkthrough so the exercise does not create unnecessary patient-data copies.
Our ePHI inventory guide helps trace those locations and transfers. Here, the point is to attach responsibility to the path: a known destination is useful, but someone must also decide how it is used and maintained.
Separate the feature from the decision to use it
A feature list describes what a service offers. Your implementation establishes which capabilities are enabled, who administers them and whether they support your intended workflow.
For the hypothetical practice, consider three questions:
- If the application offers different staff roles, who chooses the appropriate role for each person and handles changes?
- If it provides activity records, who determines what review is needed, obtains access and investigates an unexplained event?
- If it supports exports, who decides which destinations are appropriate and what happens to those copies?
These are implementation questions, not a claim that every platform must use an identical configuration or review schedule. HHS's Security Rule summary describes administrative, physical and technical safeguards, workforce compliance and a risk-based approach appropriate to the regulated entity. A vendor capability and an operating control are different things to demonstrate.
Put operating responsibilities beside the contract
Take one task that crosses the boundary between practice and vendor. If a staff member loses access during a patient session, for example, who checks the account, who contacts support and what information can be shared to resolve the issue? If the practice ends the service, who initiates the agreed data-return process and confirms that the returned information is usable?
Write down the handoff in terms the people doing the work can follow. Where the contract and operating expectation differ, resolve the difference with the appropriate vendor contact and your legal or compliance adviser. Do not quietly assign work to the vendor because your team lacks someone to do it.
You may delegate implementation to an IT provider. That creates another relationship to understand: what the provider does, what your practice authorizes and what evidence returns to you. It should not leave a task unowned between two suppliers.
Treat the signature as a starting point
Before relying on the new service, connect three things: what the agreement says, how the product works and how your practice will use it. A gap between them is a specific issue to resolve, not a reason to declare the entire platform compliant or noncompliant from a checklist.
The useful question after “Do we have a BAA?” is “Can we explain who does the work that this arrangement depends on?”
Research basis: HHS guidance inspected November 17, 2026; public practitioner questions informed the angle. This is an operating explanation for HIPAA-regulated practices, not a review of your contract or a complete legal compliance assessment.