Guide · Published Nov 18, 2026
Notion for a Medical Office: HIPAA, the BAA and a Safe Setup
For the practice manager who wants every SOP and policy in one searchable place: what Notion's own pages say, what a Business workspace cannot lock down, and a workspace you can import this week.
Notion works in a medical office as the operations wiki: SOPs, policies, onboarding and checklists, with no patient information. Notion signs a business associate agreement only on its Enterprise plan (Notion Help Center, 2026). On Free, Plus or Business, keep every patient detail out, and run a quarterly sweep to prove it.
Key takeaways
- Notion signs its BAA only for Enterprise Plan subscribers, and HIPAA configuration costs nothing extra there (Notion Help Center, 2026).
- Even under the BAA, patient information may not go in workspace or teamspace names, file names, profiles, user group names or support requests, and beta features are not covered.
- On Free, Plus and Business, Notion's AI providers keep data for 30 days or fewer; zero data retention is an Enterprise feature, and a few models lack it (Notion AI security page, 2026).
- Below Enterprise you cannot switch off publishing, export or guest invites for the whole workspace: Notion lists those as Enterprise-only settings (Notion Help Center, 2026).
- Page history lasts 7, 30 or 90 days on Free, Plus and Business, but HIPAA policies must be kept 6 years (45 CFR 164.316), so export every retired version.
Free download: the Notion Medical Office Workspace Template (Excel). Four databases you import into Notion by CSV (SOP library, compliance calendar, access roster, vendor and BAA register), a 20-question safeguard check that scores your patient-data exposure from 0 to 100, and a 12-case playbook for the day something goes wrong.
Get the free Notion workspace templateA new front desk hire asks where the cash drawer SOP lives. One person says the shared drive, another says the binder, and the honest answer is the manager who has been there nine years. Notion fixes that well. The catch is the plan: Notion's help center says only Enterprise subscribers can sign its business associate agreement, and most small practices start on Plus or Business. That is fine for a wiki. It is not fine for a patient's name.
The short answer, from Notion's own pages
Notion can hold patient information only on Enterprise, with the BAA accepted and the safeguards configured. A business associate is anyone who "creates, receives, maintains, or transmits" protected health information for a practice (45 CFR 160.103), and a cloud workspace that stores it maintains it. The practice needs that assurance in a written agreement (45 CFR 164.502(e)). On every other plan, the only safe amount of patient information is none.
| Question | Free, Plus, Business | Enterprise |
|---|---|---|
| Business associate agreement | Not available | Available: Settings, Workspace settings, HIPAA compliance, Activate, then accept |
| Cost of the HIPAA configuration | Not applicable | No extra charge |
| Patient information allowed | No | Only inside the BAA and Notion's configuration guide |
| AI provider data retention | 30 days or fewer | Zero retention on most models; a few models are off unless the owner opts in |
| Page history | 7 days (Free), 30 (Plus), 90 (Business) | Custom |
| SAML single sign-on | Business only | Yes |
| SCIM provisioning and audit log | No | Yes |
Sources: Notion HIPAA configuration, Notion AI security and privacy practices, Notion pricing, all opened Nov 17, 2026. Prices are left out on purpose: they change.
Notion's security page says the same thing in one line: Business Associate Agreement (BAA) available to Enterprise customers
(Notion security, 2026). No software is HIPAA compliant on its own: the signed agreement, the configuration and how your team uses the tool decide it. Even with the BAA, Notion bars patient information from workspace and teamspace names, file names, account profiles, user group names and support requests, says beta services are not covered, and does not allow the workspace to be used to communicate with patients.
What a Business workspace cannot lock down
On Free, Plus and Business, a workspace owner cannot turn off publishing, export or guest invitations for everyone. Notion's settings page lists those controls under "Security settings available on Enterprise Plans only" (Notion Help Center, 2026). Any member can still publish a page to the web or invite an outside guest by mistake, so the protection below Enterprise is a written rule, training, and a check that proves the rule held.
| Setting | Free, Plus, Business | Enterprise | What the practice does instead |
|---|---|---|---|
| Disable publishing sites and forms | Not available | Available | Rule: nothing goes to the web. Check Settings, Public pages every month |
| Disable export | Not available | Available | Remove access the day someone leaves; nothing patient-related exists to export |
| Control who can invite guests | Not available | Available | Rule: no guests. Compare the member list with the staff list monthly |
| Disable duplicating pages to other workspaces | Not available | Available | Rule: practice pages stay in the practice workspace, never a personal one |
| Trash deletion and retention timing | Not available | Available | Export retired policies to the practice's secure drive |
The check is easier than it sounds. Settings, then Public pages, lists every published site, public form and page "that anyone with a link can access", and every workspace member can see it (Notion Help Center, 2026). An empty list is the result you want each month.
Where Notion fits a medical office
Notion is pages plus databases, which makes it very good at the practice's written memory and only fair at deadline work with alarms. Match the job to the tool before you move anything.
| Job | Fit | Patient information needed? |
|---|---|---|
| SOP and policy library | Strong: searchable, linked, one owner per page | None |
| New-hire onboarding pages | Strong: checklists, links, short videos | None |
| Huddle agendas and meeting notes | Good, if written by role and time slot | None |
| Vendor and BAA register | Good as a database | None |
| Compliance calendar (OSHA, HIPAA training) | Good, though reminders are weaker than a task tool | None |
| Schedules, results, referrals, patient messages | No | Belongs in the EHR |
For queues where a missed date costs money, a task tool with automations usually fits better; the trade-offs are in project management for medical practices and the BAA-or-reference-codes choice in the HIPAA project tool guide. If your team lives in spreadsheets more than documents, compare Airtable for a medical practice.
Notion AI, Mail, Calendar and connections
Notion AI is the door most practices forget. On Free, Plus and Business, Notion says its AI provider "retains your data for 30 days or fewer, then deletes it." On Enterprise, most models offer zero data retention, but "a small number of models don't offer zero data retention", and those stay off unless the workspace owner opts in (Notion AI security page, 2026). Notion's wording on HIPAA is narrow: For workspaces with zero data retention in effect, our providers' zero-retention APIs support HIPAA-compliant workflows.
| Door | What Notion's pages say | What to do |
|---|---|---|
| Notion AI, lower plans | Providers keep data 30 days or fewer | No patient details in prompts, or on any page the AI can read |
| Notion AI, Enterprise | Zero retention on most models; the rest need an owner opt-in | Leave those models off. Ask Notion in writing which AI features your BAA covers |
| Notion Mail and Calendar | HIPAA goes through Google Workspace's own setup | Keep patient details out of subjects and invites unless your Google agreement covers them |
| Connections (apps) | Apps enabled before HIPAA activation stay enabled | Remove unused apps; list the rest on your BAA register |
| Beta features | Not covered by the BAA | Leave them off in any workspace that holds patient information |
If the practice runs Gmail and Google Calendar, that agreement is a separate decision, covered in the Google Workspace HIPAA guide. Record every agreement you hold, and every vendor you decided needs none, in the business associate agreement tracker.
Page history and the six-year rule
HIPAA policies and procedures must be kept 6 years "from the date of its creation or the date when it last was in effect, whichever is later" (45 CFR 164.316(b)(2)(i); the Privacy Rule says the same in 164.530(j)(2)). Notion's page history covers 7 days on Free, 30 on Plus and 90 on Business (Notion pricing, 2026). Edit your privacy policy page in January on Business, and by May the old wording is gone from Notion.
The fix takes two minutes per change. Before you replace a policy, export the current page as a PDF, name it with the policy ID and its effective dates, and save it to the practice's secure drive. Then tick "Archived copy saved" on the SOP Library row. The template's SOP Library flags every retired version without an archived copy.
Why your risk analysis should name Notion
A HIPAA risk analysis is required, not optional: "an accurate and thorough assessment of the potential risks and vulnerabilities" to electronic protected health information (45 CFR 164.308(a)(1)(ii)(A)). If Notion holds patient information, it must be assessed. If it holds none, write that down with the controls that keep it that way, so the decision is on paper when someone asks.
The numbers under the chart: 19 penalties listed for 2020 (4 citing a risk analysis failure), 14 for 2021 (1), 22 for 2022 (1), 13 for 2023 (6), 15 for 2024 (8), 20 for 2025 (15) and 12 so far in 2026 (10). The smallest 2025 entry was a $5,000 settlement with a single imaging practice (HIPAA Journal, 2026), so size is no shield. The free HHS tool and how to run it are in the HIPAA security risk assessment guide.
The template's Safeguard Check asks 20 yes-or-no questions drawn from Notion's settings and the HIPAA rules above, then gives you a 0 to 100 exposure score, the gaps ranked, and the hours it takes to close them.
Get the free Notion workspace templateThe practice workspace, database by database
Start with five teamspaces and four databases. Five well-kept pages beat fifty abandoned ones, and the first page should be the SOP the practice can least afford to lose.
- Opening and closing checklist
- Phone scripts
- Cash drawer and payment at time of service
- Room turnover
- Vaccine refrigerator excursion steps
- Policy manual (SOP Library database)
- Vendor and BAA Register (database)
- Compliance Calendar (database)
- Quarterly sweep log
- Week one checklist
- Access Roster (database)
| Database | Key properties | Owner | Review |
|---|---|---|---|
| SOP Library | SOP ID, title, teamspace, owner role, status, version, effective date, last reviewed, review every (months), archived copy saved | Practice manager | Monthly |
| Compliance Calendar | Task, rule, interval in months, owner, last done, fixed due date, next due, evidence location | Privacy official | Weekly |
| Access Roster | Person (staff ID), member or guest, date added, HIPAA training date, rule acknowledged, date left, date removed | Practice manager | Monthly |
| Vendor and BAA Register | Vendor, what it does, touches patient information, BAA status, plan, review date | Privacy official | Quarterly |
Building them takes about an hour. Notion turns a CSV file into a database, but it cannot create formulas or relations during the import, and it reads dates as MM/DD/YYYY (Notion Help Center, 2026).
- Fill in one import tab in the workbook and delete the sample rows.
- Save that tab alone as CSV (File, Save As, CSV), one tab at a time.
- In Notion, open Settings, then Import, then CSV, or type /csv on a page. Each file becomes a database.
- Set the property types: select for status and owner, date for dates, checkbox for yes-or-no columns.
- Add the formulas after the import. The workbook prints each one, for example
dateAdd(prop("Last reviewed"), prop("Review months"), "months")for the next review date.
Worked example. A three-physician family practice with 14 staff runs Notion Business as its wiki. It imports 32 SOPs, gives each an owner role and a 12-month review, and lists 9 vendors. The first Dashboard read shows 6 SOPs past review, 2 former staff still in the workspace and one public page left over from a holiday schedule. Fixing all three takes one afternoon. No patient record is involved at any step. Start from the free SOP templates so you are editing, not writing from scratch.
How patient data sneaks in, and the sweep
Drift, not hackers, is how patient information usually enters a wiki. Someone pastes a schedule screenshot into the huddle page, or names a page after a patient to find it later. A chart number counts too: medical record numbers are one of the 18 identifiers HIPAA lists (45 CFR 164.514(b)(2)(i)(H)), so a chart number is minimized data, not de-identified data. A 15-minute sweep every quarter catches the drift.
| Check | Owner | Last run | Findings | Next due |
|---|---|---|---|---|
| Settings, Public pages is empty | Practice manager | Oct 6 | 1 (removed) | Jan 5 |
| Search: DOB, MRN, chart, patient, Dx, Rx | Practice manager | Oct 6 | 0 | Jan 5 |
| Uploads and images, last 90 days | Front desk lead | Oct 6 | 2 (deleted) | Jan 5 |
| Members and guests vs staff list | Practice manager | Oct 6 | 1 (removed) | Jan 5 |
| Connections and AI use reviewed | Privacy official | Oct 6 | 0 | Jan 5 |
Delete what you find and retrain on the rule. If the sweep finds patient information in a workspace without a BAA, tell your privacy official the same day and follow your incident policy; the breach response checklist walks the steps. Remove a departing employee the day they leave, since HIPAA expects procedures for ending access when employment ends (45 CFR 164.308(a)(3)(ii)(C)), and give each person their own login: unique user identification is a required safeguard (45 CFR 164.312(a)(2)(i)).
Which path fits your practice
| Question | Free, Plus or Business, no patient information | Enterprise with the BAA |
|---|---|---|
| Patient information | None, including chart numbers | Only inside the BAA and Notion's configuration guide |
| Main risk | Drift: someone pastes a name or publishes a page | Settings left open, and features outside the BAA |
| Controls you rely on | Written rule, training, quarterly sweep, same-day offboarding | SAML SSO, SCIM, audit log, publishing and export off, plus the same sweep |
| Best for | SOP wiki, policies, onboarding, vendor register | A compliance-approved reason to keep patient information in Notion |
My view: for most practices with 1 to 10 physicians, run Notion as the SOP and policy wiki with no patient information and no patient details in AI prompts, and keep patient work in the EHR. Move to Enterprise only when your compliance advisor confirms a real need, then configure every safeguard on Notion's list before the first record goes in.
Mistakes to avoid. Calling chart numbers de-identified. Assuming Business can switch off publishing or guest invites. Treating page history as your policy archive. Letting Notion AI read pages that might hold patient details. Leaving former staff in the member list because "they never log in".
- Open Settings, then Public pages, and unpublish anything about the practice's operations.
- Search the workspace for DOB, MRN, chart, patient and Dx; delete anything patient-related and log the count.
- Compare the member and guest list with today's staff list; remove anyone who has left.
- Pin a "Read first" page: no names, birth dates, chart numbers, photos or clinical details, and none in AI prompts.
- Export the current version of every policy page to the practice drive before the next edit.
The rest of the system library is in the medical practice operations hub. If you would rather have the SOP library, compliance calendar and access controls built and handed over, our Practice Controls work does exactly that, and what an operations consultant costs lays out the options against hiring.
Get the workspace, or get it built
The template gives you four import-ready databases and a score that shows how exposed your current setup is. If you want a second pair of eyes first, the free 20-minute Chaos Audit walks back the last thing that slipped and names the first fix.
Frequently asked questions
Is Notion HIPAA compliant?
Only on its Enterprise plan, with the business associate agreement accepted and the safeguards configured, per Notion's help center in Nov 2026. Free, Plus and Business cannot sign the agreement, so they should hold no patient information.
Does Notion sign a BAA?
Yes, for Enterprise Plan subscribers only. A workspace owner activates HIPAA compliance in Settings, Workspace settings, HIPAA compliance, and accepts the agreement. Notion says the HIPAA configuration costs nothing extra on Enterprise.
Is Notion AI covered by the BAA?
Notion says zero-retention APIs support HIPAA-compliant workflows where zero data retention is in effect, an Enterprise feature that a few models lack. On Free, Plus and Business, AI providers keep data for 30 days or fewer. Get Notion's answer in writing before AI goes near patient information.
Can a medical office use Notion without a BAA?
Yes, as an SOP, policy and onboarding wiki that holds no patient information at all: no names, birth dates, contact details, chart numbers, photos or clinical details. A chart number is one of the 18 HIPAA identifiers.
Where can PHI not go in Notion, even with a BAA?
Notion's help center bars protected health information from workspace and teamspace names, file names, account profiles, user group names and support requests. Beta services are not covered by the agreement, and the workspace may not be used to communicate with patients.
How long does Notion keep old versions of a page?
Page history covers 7 days on Free, 30 days on Plus and 90 days on Business, and is custom on Enterprise, per Notion's pricing page in Nov 2026. HIPAA policies must be kept 6 years, so export each retired version to the practice's secure drive.