Guide · Published Nov 18, 2026
Airtable for a Medical Practice: HIPAA, BAA and Setup
For managers and owners who want Airtable for the trackers a practice runs on: Airtable's own HIPAA terms, where patient data can never go, and a base you can build this week.
Airtable for a medical practice works best as an operations database: licenses, compliance tasks, equipment, vendors and staff access. Airtable offers a business associate agreement only on Enterprise Scale, and only Airtable can switch HIPAA on (Airtable, Nov 2026). On Free, Team or Business, keep every patient detail out.
Key takeaways
- The BAA and HIPAA safeguards come only with Enterprise Scale, switched on by Airtable after signing (Airtable support, Nov 2026).
- Even then, ePHI may sit only in records: never in base names, descriptions or automated emails (Airtable datasheet, Jul 23, 2026).
- Chart numbers are not a safe stand-in: medical record numbers are a HIPAA identifier (45 CFR 164.514).
- Free holds 1,000 records per base and Team 50,000 (Airtable, Nov 2026); an operations base needs about 250.
- Five tables and one weekly digest cover most small-practice operations.
Free download: the Airtable Medical Practice Base Template (Excel). Five ready tables with Airtable field types and formulas, an automation map checked against your plan's run limit, a 13-case playbook, and a 20-question check that scores your patient-data risk from 0 to 100.
Get the free base templateThe license tracker lives in a spreadsheet three people edit, and someone just sorted one column and not the others. Airtable fixes that. The catch is HIPAA: Airtable limits its safeguards to Enterprise Scale, and most small practices start on Free or Team.
What Airtable is good for
Airtable is best at things linked to other things: a provider to each license, a device to its service vendor, a vendor to its agreement. In a spreadsheet those links live in someone's head; in Airtable they are fields, so one filter answers "what expires in 60 days?" It is weaker at task comments and workloads, so keep patient-level work in the EHR.
| Table | One record is | Watch out for |
|---|---|---|
| Licenses and registrations | A state license, DEA registration, board certificate or BLS card | Store the last four digits, not the full number |
| Compliance calendar | One recurring duty, such as bloodborne pathogens training | Evidence stays in your files; the base holds the date |
| Equipment | One device, linked to its vendor | Service intervals come from the manufacturer |
| Vendors and agreements | One vendor, with its BAA status | Signed PDFs belong in restricted storage |
| Staff access | One person and every system they can open | Review quarterly and on the last day of work |
Two rows run on federal clocks. A DEA practitioner registration lasts 3 years, and you may apply to renew no more than 60 days before it expires (21 CFR 1301.13). OSHA requires bloodborne pathogens training and an exposure control plan review at least annually (29 CFR 1910.1030). The full lists are in the license renewal tracker and the compliance calendar.
Airtable and HIPAA, from its own pages
Airtable signs a business associate agreement only for Enterprise Scale customers, inside its Health Information Exhibit. HIPAA requires one before any vendor "creates, receives, maintains, or transmits protected health information" for you (45 CFR 160.103), documented "through a written contract" (45 CFR 164.502(e)).
| Question | What Airtable's pages say |
|---|---|
| Which plan? | Enterprise Scale only, with the Health Information Exhibit |
| Who turns HIPAA on? | Airtable, after the agreement is processed; admins cannot |
| Which apps? | Web, Mac and Windows apps are listed; mobile apps are not |
| Moving a base in later? | No defined migration path from a non-HIPAA environment |
| Patient portal? | "Do not use Airtable as a patient portal at this time." |
The migration line matters most: if you build on Team now and need patient data later, Airtable has no specific path to move that work into a HIPAA-enabled environment (Airtable support, Nov 2026). Decide the patient-data question first. The agreement also hands you duties: review access, download usage reports, approve or disable integrations, turn on single sign-on. Log it, or your written "no patient data, no BAA" decision, in the business associate agreement tracker.
Where ePHI cannot go, even under the BAA
With the exhibit signed, Airtable's datasheet still allows ePHI only in "records within Airtable bases or interfaces" (Airtable datasheet, Jul 23, 2026).
| Place or feature | Rule |
|---|---|
| Base, table, interface and workspace names; base descriptions | No ePHI or medical information |
| Automated emails | Not in the subject or the body |
| Send record | Not on records that hold ePHI |
| Airtable AI | No ePHI unless the health information AI terms are accepted |
| Support tickets and screenshots | No ePHI, by any channel |
| Integrations | Airtable is not responsible once data leaves Airtable |
Two more lines change habits: Enterprise audit logs are kept 180 days, so export them to keep longer; and if you downgrade from Enterprise Scale, protection ends and all ePHI must come out first.
Free, Team or Business with no patient data
Without an agreement the rule is short: no patient information anywhere. No names, birth dates, phone numbers, diagnoses, images, notes or chart numbers, in any field, attachment, comment or base name. HIPAA lists "medical record numbers" among the 18 identifiers that must go before data counts as de-identified (45 CFR 164.514(b)(2)(i)(H)), so a chart-number base holds identifiers on a plan with no agreement.
A three-physician practice with 40 licenses and cards, 60 compliance duties, 80 devices, 50 vendors and 20 staff has 250 records, a quarter of Free's 1,000. The limits that bite are history and people: Free keeps 2 weeks of revision and snapshot history against 1 year on Team and Business, and allows 5 editors (Airtable plans overview, Nov 2026). Read-only collaborators, form submissions and share links are not billed (Airtable pricing, Nov 2026).
| What staff type | Write this instead |
|---|---|
| "Call back J.S. about the MRI" | Nothing: callbacks stay in the EHR task queue |
| A chart number in a task title | The room, device or process the work is about |
| Doses affected when the vaccine fridge ran warm | Device ID, time out of range, "doses listed in the EHR" |
| A screenshot of the day's schedule | Open slots, as a number |
Building the base, step by step
Every table answers one question and every view serves one person. These steps take about two hours over a week; the template's Blueprint tab lists every field, type and formula.
| Step | Owner | How often | Where it breaks |
|---|---|---|---|
| 1. Write the rule: no patient data, or only under a signed BAA | Owner, privacy officer | Once | Unwritten, so the first form asks for a name |
| 2. Create the workspace on a practice-owned account | Manager | Once | A personal account leaves with the person |
| 3. Build the five tables from the Blueprint | Manager | Once, 90 minutes | Free text where a single select belongs |
| 4. Add "next due" and "days left" formulas | Manager | Once | Hand-typed due dates go stale |
| 5. Give each role one view | Manager | Once | Everyone resorts the main grid |
| 6. Add the Monday digest automation | Manager | Weekly | The email pastes record details |
| 7. Close the side doors | Manager | Monthly | A vendor's share link stays open for a year |
| 8. Review access, export the base | Manager and backup | Quarterly; monthly | A former employee still has edit access |
Step 8 is HIPAA's access rule in daily form: "establish, document, review, and modify a user's right of access," and end it when someone leaves (45 CFR 164.308(a)(3) and (a)(4)). The formulas are short: "Days left" is DATETIME_DIFF({Expires}, TODAY(), 'days') and "Next due" is DATEADD({Last done}, {Every (months)}, 'months'). Schedule the digest every Monday to email each owner a link to the "due in 60 days" view, never the contents. It uses 4 or 5 runs a month, against 100 on Free and 25,000 on Team.
ClinicOps Practice Controls builds the license and compliance calendars, the recurring task board and the access reviews inside your own tools, then hands them over. See what an operations consultant costs.
Start with the free templateForms, share links, automations and AI
Patient data rarely enters through the grid. It comes through side doors someone opened and forgot. Run this check first.
- Does it identify a patient: a name, a chart number, initials plus a service, a photo?No: it can go in. Yes: step 2.
- Is the workspace on Enterprise Scale, exhibit signed, HIPAA enabled by Airtable?No: stop; it stays in the EHR. Yes: step 3.
- Will it live only in a record field, never a name, email, AI field or ticket?No: redesign first. Yes: step 4.
- Are every person and integration that can reach it approved, and is the base in your risk analysis?No: fix access first. Yes: it can go in.
Decision flow: ClinicOps summary of Airtable's datasheet (Jul 23, 2026) and 45 CFR 164.502, 164.514 and 164.308.
| Door | What to do |
|---|---|
| Forms | No patient fields on any form outside an agreement; review questions monthly |
| Shared view links | Password or email-domain restriction; turn off links nobody can explain |
| Automation emails | Send a link to the view, never the data |
| Integrations and sync | List each one and approve it in writing, or switch it off |
| Airtable AI | Off in any workspace that could hold patient data |
| Accounts | Named logins, two owners, and two-factor authentication, which every plan offers (Airtable, Nov 2026) |
Automating between tools? The rules in the Zapier guide for medical offices apply, and the BAA route or reference codes guide covers the same trap in project tools.
Worked example: what the current way costs
Worked example, not a client: a three-physician family practice where the manager spends 4 hours a week chasing license dates, service visits, vendor agreements and logins across spreadsheets and an inbox, and the front-desk lead spends 3.
| Input | Value | Basis |
|---|---|---|
| Manager hours a week | 4 | Assumption |
| Median wage, medical and health services managers, physician offices | $50.85 an hour | BLS OEWS, May 2025 |
| Front-desk lead hours a week | 3 | Assumption |
| Median wage, medical secretaries and administrative assistants, physician offices | $21.45 an hour | BLS OEWS, May 2025 |
| Yearly cost | $13,923 | (4 x $50.85 + 3 x $21.45) x 52 |
That is wages only, before one missed renewal. The template's Score tab runs this on your own hours, plus the share you expect the base to save: your estimate to test, not a promise.
Airtable, Notion, ClickUp or a spreadsheet?
Pick the tool your team already opens every day; add Airtable only if your trackers are truly relational.
| Option | Best when | Our verdict |
|---|---|---|
| Airtable | Licenses, devices and vendors linked, with dates driving alerts | Good for an operations base with no patient data |
| Notion | SOPs and policies are the bigger gap | See Notion for a medical office |
| ClickUp | Assignments, recurring checklists and comments matter most | See whether ClickUp is HIPAA compliant |
| Excel or Google Sheets | One person keeps a short list | Fine to start; see Google Workspace and HIPAA |
Mistakes to avoid
- Building first, deciding the patient-data rule later. There is no defined path to move a non-HIPAA base into a HIPAA environment.
- Leaving Airtable out of the risk analysis. HIPAA requires "an accurate and thorough assessment" of risks to ePHI (45 CFR 164.308(a)(1)); record the base and its decision. The HHS risk assessment tool guide shows how.
- Search every base for names, birth dates, phone numbers and chart numbers.
- Turn off every share link and form nobody can explain.
- Record "BAA signed" or "no patient data, no BAA" for each workspace in your agreement register.
- Run the template's 20-question check and fix the three highest-weight gaps.
Frequently asked questions
Is Airtable HIPAA compliant?
Airtable offers HIPAA safeguards and a business associate agreement only on Enterprise Scale, per its support article checked in November 2026. No tool is compliant on its own: the agreement, the configuration and how your team uses it decide that.
Does Airtable sign a BAA?
Yes, for Enterprise Scale customers, inside its Health Information Exhibit. Airtable enables HIPAA internally after the agreement is signed and processed; admins cannot switch it on.
Can a medical practice use Airtable without a BAA?
Yes, for operations with no patient information: licenses, compliance tasks, equipment, vendors and staff access. Keep out names, birth dates, contact and clinical details, and chart numbers.
Are Airtable forms safe for patient intake?
Not on a plan without an agreement, and Airtable's datasheet says not to use it as a patient portal. Intake belongs in your EHR or a patient communication tool covered by a BAA.
Can Airtable AI be used with patient information?
Only after the Airtable AI Terms and the Supplemental AI Terms for Health Information are accepted. Until then, the datasheet says to keep ePHI out of AI-enabled workspaces.
What happens to our base if the person who built it leaves?
If it sits in their personal account, it can leave with them. Build in a practice-owned workspace, keep two owners, and remove access on the last day of work.
Next steps
- The medical practice operations library
Every system a small practice runs, and where Airtable fits.
- The business associate agreement tracker
Record the Airtable decision and every vendor that touches patient data.
- Notion for a medical office
The same questions, answered for SOPs and policies.
- What a practice operations consultant costs
If you would rather have the base built and handed over.
Build the base without the patient-data risk
The free template gives you the five tables, the formulas, the automations and a score for your current setup. Want a second pair of eyes first? The 20-minute Chaos Audit walks back the last thing that slipped and names the first fix.