- If a vendor handles patient information for you, you need a business associate agreement.
- Send each step only the data it needs.
- Know where data is stored, who can see it and how long it is kept.
- Self-hosting keeps data in your environment, and makes you responsible for securing it.
Please note: this guide is general information for US practices, not legal advice. Confirm your obligations with your compliance officer or legal counsel.
Automation can take a great deal of administrative work off a practice, and much of that work involves protected health information (PHI). The rules don’t forbid automating it. They require you to know where the information goes and to protect it along the way. The questions below are the ones to answer before connecting anything.
1. Does this workflow touch PHI at all?
Not every workflow in a practice does. Posting a job advert or reconciling a supplier invoice involves no patient data. Many workflows can also be redesigned so that they don’t need it: a staff alert can say “a new intake form has arrived” and link to the secure system, without repeating the patient’s details in a chat message. Start by asking whether PHI needs to be in the flow.
2. Is there a business associate agreement with every vendor involved?
When a vendor creates, receives, stores or transmits PHI on your behalf, HIPAA treats it as a business associate, and you need a signed business associate agreement (BAA) before any data flows. That applies to every link in the chain: the form tool, the automation platform, the messaging service and the storage behind them.
Many software companies sign BAAs only on certain plans, and some don’t offer them at all. Check before you build. A tool that is perfect in every other way cannot be used for PHI without one.
3. Is each step receiving only what it needs?
The minimum necessary principle applies to automated steps as much as to people. A reminder message needs a name, a time and a contact number. It doesn’t need a diagnosis. Map which fields each step uses and remove the rest from what you pass along. This also limits the damage if something goes wrong.
4. Where is data stored, and for how long?
Automation platforms keep run histories so that failures can be investigated. Those logs can contain the data that passed through. Find out what is retained, for how long and who can view it, then shorten retention or switch off detailed logging where the platform allows. The same applies to spreadsheets and inboxes used as stepping stones: if PHI lands there, they are in scope.
5. Who can get in?
- Individual logins, never shared accounts
- Multi-factor authentication on every tool in the chain
- Access limited to the people who maintain the workflow
- Accounts removed promptly when someone leaves
6. Is there a record of what happened?
You should be able to show what an automation did with a patient’s information and when. Keep an audit log of actions, without copying the PHI itself into the log, and review failed runs routinely. A workflow that fails silently is both an operational and a compliance problem.
Cloud or self-hosted?
There are two sound approaches. One is to use cloud tools that sign a BAA and configure them carefully. The other is to run the automation layer on infrastructure you control, for example a self-hosted n8n instance, so that data stays inside your environment.
Self-hosting reduces the number of outside parties handling PHI. It doesn’t make you compliant automatically. Encryption, patching, backups and access control become your responsibility, or your partner’s, and should be written down. Our comparison of Make, n8n and Zapier covers the hosting differences.
A checklist to keep
- Data flow diagram for each workflow that touches PHI
- BAA on file for every vendor in that flow
- Fields limited to the minimum each step needs
- Log retention reviewed and reduced
- Individual accounts with multi-factor authentication
- Audit log of automated actions
- A named owner and a documented process for failures
- Workflows included in your regular risk assessment
With these in place, the workflows that save a practice the most time, such as reminders and intake or prior authorisation tracking, can be automated with confidence.