Guide · Published Nov 18, 2026
Automation for a Medical Office: Zapier, Keragon and HIPAA
For practice managers who want the copy-paste work gone without sending patient data where it cannot go: what Zapier may run, what needs a tool that signs a BAA, and 28 recipes with the hours they save.
The free Automation Recipe List (Excel)
28 recipes sorted by what is allowed (any tool, BAA-covered tool only, or do not automate), each with its trigger, action, owner, failure point and weekly check; a calculator that turns your volumes into hours and dollars a year; a PHI check that routes any automation you propose; and a 12-case playbook. Filled with a worked example.
Get the free recipe listAutomation for a medical office is safe when you split it in two: anything with no patient data can run in Zapier, and anything that touches patient data runs only in a tool that signs a business associate agreement. Zapier says it "can't sign business associate agreements" (Zapier, 2026). Keragon and Microsoft Power Automate can.
Key takeaways
- Zapier states that protected health information under HIPAA "isn't supported" and that it cannot sign BAAs (Zapier data privacy page).
- Keragon includes a BAA on all plans, from $99 a month billed annually for 200 workflow runs, as of Nov 17, 2026 (Keragon).
- Microsoft lists Power Automate among the cloud services covered by its BAA, which comes by default in its Data Protection Addendum (Microsoft Learn, updated Sep 11, 2026).
- A practice may let a vendor handle patient data only after getting "satisfactory assurances" in a business associate agreement (45 CFR 164.308(b)(1)).
- In our worked example, nine automations return about 430 staff hours a year, worth about $8,170 at the $19.00 BLS healthcare median receptionist wage (BLS, May 2025).
What's allowed, tool by tool
The rule is simple to state and easy to break: patient data may move only through tools whose vendor has signed a BAA with you (45 CFR 164.502(e) and 164.504(e)). Everything below comes from each vendor's own page on Nov 17, 2026.
| Tool | BAA | Patient data allowed? | Plans and list price |
|---|---|---|---|
| Zapier | No: "can't sign business associate agreements" | No. Office work only | Free $0 (100 tasks a month); Professional $19.99 a month billed annually (750 tasks); Team $69 (2,000 tasks) |
| Keragon | Yes: "BAA included on all plans" | Yes, under the BAA | Starter $99 a month billed annually ($149 monthly), 200 runs; Professional $269 ($399), 2,000 runs; Scale Up $995 ($1,499), 20,000 runs |
| Microsoft Power Automate | Yes, in scope of Microsoft's BAA "as a standalone service or as included in an Office 365 or Dynamics 365 branded plan" | Yes, under the BAA, once your Microsoft 365 is set up for it | Comes with many Microsoft 365 business plans; check your plan |
| Your EHR's own automations | Usually covered by your EHR contract's BAA | Yes, inside the EHR | Part of the EHR subscription |
| Make | No BAA statement found on Make's own site | Treat as no | Not compared |
A chart number does not make data safe for Zapier. Tied to an appointment date or a health detail it is protected health information, so it stays out. For Microsoft, start with the Microsoft 365 HIPAA setup guide, and keep every signed BAA in your BAA tracker.
The recipes, sorted by route
The full list in the download has 28 recipes. These are the ones most small practices start with. Each has one owner and one check, because an automation nobody watches fails quietly.
| Recipe | Route | Minutes per run | Where it breaks |
|---|---|---|---|
| Job applicant form to hiring board, manager alerted | Any tool | 4 | Form field renamed; the zap stops mapping |
| Supply reorder form to purchase list and vendor email | Any tool | 10 | Vendor email changes |
| License and DEA expiry 90 days out to a task for the owner | Any tool | 20 a week | New provider never added to the sheet |
| Weekly KPI snapshot (counts only) emailed to the owner | Any tool | 45 a week | Someone adds a patient-level column |
| Staff offboarding checklist when HR sets an end date | Any tool | 15 | End date entered late |
| New patient web booking to EHR and intake packet | BAA tool only | 6 | Duplicate patients from typos |
| Intake form to the patient's chart folder | BAA tool only | 4 | Files the PDF to the wrong chart |
| Records request to a tracking row with a 30-day due date (15 days from July 17, 2027) | BAA tool only | 5 | Clock starts on the wrong date |
| No-show to the waitlist and recall list | BAA tool only | 3 | Patient who rescheduled is still listed |
| Clinical advice by auto-reply | Do not automate | 0 | A clinician decides; never a rule |
Two of these sit next to other guides: records requests run on the 30-day rule (15 days from July 17, 2027) in the medical records request process, and the license reminders feed the recurring tasks board.
Type in how often each task happens and how long it takes; the workbook returns hours a week, hours a year and dollars a year, and flags any patient-data recipe you cannot run until you have a BAA-covered tool.
Get the free recipe listSet it up: the steps
The finished system: a register of every automation with its owner, route and weekly check; patient-data automations only in a BAA-covered tool; and a monthly review. Build it in this order.
- List the copy-paste work (practice manager, one week). Each person logs every task they retype from one screen to another. Breaks when only the manager's own tasks get listed.
- Route each task (manager, one hour). Run each through the PHI check: does it touch patient data, does every tool in the chain have a BAA, is it a clinical decision? Breaks when "just a first name" is treated as safe.
- Get the BAAs first (owner). Signed BAA in the tracker before the first patient-data run. Breaks when a trial account goes live with real patients.
- Build in practice accounts, never personal ones (manager). Breaks when the builder leaves and the automations leave with them.
- Trim the data (manager). Send only the fields the next step needs (45 CFR 164.502(b)). Breaks when a whole intake form is copied "to be safe".
- Name an owner and a weekly check for each (manager). Look at run history every Monday. Breaks when a failed run sends no alert.
- Review monthly (compliance contact, 20 minutes). Any automation not in the register gets switched off.
Worked example: a 3-physician practice
Worked example, not a client. A 3-physician family practice turns on nine recipes. Front desk time is valued at $19.00 an hour, the BLS median for receptionists in healthcare and social assistance in May 2025 (BLS); wages only, before other payroll costs.
| Recipe | Runs a week | Minutes per run | Hours a week |
|---|---|---|---|
| New patient booking to EHR and intake packet (BAA tool) | 25 | 6 | 2.50 |
| Intake form to chart folder (BAA tool) | 25 | 4 | 1.67 |
| Referral fax to coordinator task (BAA tool) | 15 | 3 | 0.75 |
| No-show to waitlist and recall (BAA tool) | 12 | 3 | 0.60 |
| Records request tracking (BAA tool) | 6 | 5 | 0.50 |
| Supply reorder (any tool) | 5 | 10 | 0.83 |
| Weekly KPI snapshot (any tool) | 1 | 45 | 0.75 |
| Applicant to hiring board (any tool) | 10 | 4 | 0.67 |
| License and DEA alerts (any tool) | 1 | 20 | 0.33 |
| Total | 100 | 8.60 |
At 50 working weeks, 8.6 hours a week is 430 hours a year, worth about $8,170 at $19.00 an hour. The tools cost far less. The five patient-data recipes run about 83 times a week, roughly 360 a month: Keragon's Starter plan includes 200 runs and charges $0.15 for each extra run, so about $99 + $24 = $123 a month. The four office recipes run about 17 times a week, about 74 a month; at two actions per run that is roughly 150 Zapier tasks, above the free plan's 100, so budget $19.99 a month for Professional. Together, about $143 a month, or $1,716 a year, against $8,170 of staff time.
Which route for your automation
| Situation | Best route | Cost | Risk |
|---|---|---|---|
| No patient data anywhere in the chain | Zapier or any tool | From $0 (Zapier Free) | Someone adds a patient field later: review monthly |
| Patient data, and you already run Microsoft 365 under its BAA | Power Automate | Usually inside your plan | Settings and connectors must stay inside Microsoft's BAA scope |
| Patient data across several vendors' apps | Keragon | From $99 a month billed annually | Run limits and overage: watch the monthly count |
| The step happens inside one system | That system's own automation (often the EHR) | Usually included | Vendor features change with upgrades |
| The step makes a clinical judgment | Do not automate | None | A clinician decides |
When patient data ends up in the wrong tool
It will happen once: someone pastes a patient's name into a Zapier form or a spreadsheet. Treat it as a possible breach. Stop the automation, delete the data from the tool's history, and run the four-factor risk assessment in 45 CFR 164.402. If it is a breach, patients are told without unreasonable delay and within 60 calendar days of discovery (164.404(b)). Automations that text patients also fall under the FCC limit of one healthcare text a day and three a week, covered in the HIPAA texting guide. If you would rather have the register, the routing and the weekly checks built inside your tools, that is part of our Practice Controls engagement.
Mistakes to avoid
- "It's only a first name." A name tied to an appointment is patient data. Fix: route it through the PHI check every time.
- Automations in personal accounts. Fix: practice accounts only, listed in the register, removed at offboarding.
- No owner, no check. Zaps fail quietly when a form field changes. Fix: a Monday run-history check per automation.
- Copying the whole record. Fix: send only the fields the next step needs.
- Counting saved minutes nobody measured. Fix: time each task for a week before you build.
By the numbers
| Figure | What it measures | Source and date |
|---|---|---|
| $0; $19.99; $69 | Zapier Free, Professional, Team per month, billed annually | Zapier, Nov 17, 2026 |
| 100; 750; 2,000 | Zapier tasks a month included on those plans | Zapier, Nov 17, 2026 |
| $99; $269; $995 | Keragon Starter, Professional, Scale Up per month, billed annually | Keragon, Nov 17, 2026 |
| 200; 2,000; 20,000 | Keragon workflow runs a month included | Keragon, Nov 17, 2026 |
| $0.15; $0.07; $0.02 | Keragon overage per extra run | Keragon, Nov 17, 2026 |
| $18.27; $19.00 | Receptionist median hourly wage; in healthcare and social assistance | BLS, May 2025 |
| 60 days | Latest patient notice after discovering a breach | 45 CFR 164.404 |
| 8.6 hours; 430 hours; $8,170 | Worked example: weekly hours, yearly hours, yearly value | ClinicOps calculation |
- Ask each staff member to list every task they retype from one screen to another.
- Mark each task: patient data or not.
- Move any automation that touches patient data out of Zapier, or switch it off.
- Check whether your Microsoft 365 or EHR already gives you a BAA-covered automation tool.
- Start a register: automation, owner, route, weekly check.
Frequently asked questions
Is Zapier HIPAA compliant?
No. Zapier's data privacy page says the use of protected health information under HIPAA is not supported and that Zapier cannot sign business associate agreements. A practice can still use Zapier for automations that never touch patient data, such as hiring, supplies, staff scheduling and internal reports.
What is a HIPAA-compliant alternative to Zapier?
Use a tool that signs a BAA. As of Nov 17, 2026, Keragon includes a BAA on all plans, from $99 a month billed annually, and Microsoft lists Power Automate among the services covered by its BAA. Your EHR's built-in automations are usually covered by the BAA you already have with the EHR vendor.
Does a chart number make data safe for Zapier?
No. A chart number is a HIPAA identifier, and tied to an appointment date or a health detail it is protected health information. Keep chart numbers, dates of service, phone numbers and any health detail out of Zapier entirely, and run those automations in a BAA-covered tool.
What happens if patient data ends up in Zapier by mistake?
Treat it as a possible breach. Stop the automation, delete the data from the tool's history, and run the four-factor risk assessment in 45 CFR 164.402. If it is a breach, patients must be notified without unreasonable delay and within 60 calendar days of discovery.
How much time can automation save a small practice?
It depends on your volumes. In our worked example, nine automations save a 3-physician practice about 8.6 staff hours a week, or about 430 hours a year, worth about $8,170 at the BLS healthcare median receptionist wage of $19.00 an hour. The recipe list recalculates this from your own counts and timings.
Who should own the practice's automations?
One named person, usually the practice manager, with every automation listed in a register: what it does, which tools it touches, whether it carries patient data, and who checks it each week. Automations built in a staff member's personal account should be moved to a practice account or switched off.
Next steps
- Back to the system library: medical practice operations for 1 to 10 physicians.
- Set up the Microsoft side safely: Microsoft 365 HIPAA setup.
- Track every vendor's signed BAA: the business associate agreement tracker.
- Building on a database instead? Read Airtable for a medical practice.
- Price outside help: what a medical practice operations consultant costs.
- Download the Automation Recipe List.
Find the hours hiding in your copy-paste work
The recipe list turns your own volumes into hours and dollars a year and routes every automation to a tool that is allowed to run it. If you would rather have it built and watched for you, start with a 20-minute Chaos Audit.