Most healthcare practices live with operational pain that has nothing to do with medicine. The clinical work happens; the operational work around it is held together by paper, fax, sticky notes, and Excel spreadsheets that nobody quite trusts. The EMR handles clinical data well but everything around it — intake, referrals, compliance, reporting — is somebody's job that they're squeezing in between patients.
We build the operational layer that makes a small or mid-sized practice run cleanly. Built on Airtable and Make, with HIPAA handled on Airtable's Enterprise Scale plan and a signed Business Associate Addendum. Patient-facing portal functionality (which Airtable does not currently support) is delivered through a HIPAA-certified portal product or your EMR. The result is the same kind of practice management visibility that hospital systems pay six figures for — at a fraction of the cost and built around your specific workflows.
What a Modern Practice Operations System Looks Like
Digital Patient Intake
Paper intake is a tax on every new patient. A patient fills in 6 pages by hand, the front desk retypes 4 of them into the EMR, errors get introduced, and the patient is already irritated before the clinician walks in.
For the clinical intake itself — PHI, medical history, insurance details — use a HIPAA-certified intake product (your EMR's intake module, or a tool like Phreesia, Klara, Mend) that signs its own BAA covering patient-portal use. That data flows into your EMR.
For the operational intake — appointment scheduling preferences, transport needs, language/accessibility flags, marketing source — we build a non-PHI intake form fronting Airtable. The form collects only the operational data needed to prep for the visit. Conditional logic shows only relevant questions. The data lands in Airtable structured and validated.
By the time the patient arrives, the operational record is populated. Front desk verifies identity, the EMR has the clinical intake from the certified portal, and the patient is in a room rather than at a clipboard.
Referral Tracking That Doesn't Lose Patients
Referrals arrive through every channel — fax, secure email, portal, phone. In most practices, the front desk juggles a hard-copy folder, a shared Outlook inbox, and a calendar to track which referrals are open. Patients call asking about their referral and the answer is "let me check and call you back."
A referral tracking hub centralizes all of it. Every incoming referral becomes an Airtable record with a status, an owner, a target schedule date, and a contact log. Outgoing referrals work the same way — when you send a patient to a specialist, the referral is tracked until the patient is seen and the report is back.
A daily summary alert surfaces:
- Referrals awaiting initial outreach (older than 1 day)
- Referrals with scheduled appointments that haven't been confirmed
- Outgoing referrals where no consult report has arrived after 30 days
No more "let me check and call you back." The status is on screen.
Appointment Operations Around Your EMR
Your EMR's calendar is the source of truth for appointment times. What it does badly: querying patterns across appointments, tracking no-show rates by provider/payer/day-of-week, surfacing patients who need follow-up but haven't been scheduled.
We build the operational layer that sits next to the EMR, ingesting appointments through API or daily sync. The team gets:
- A no-show rate dashboard with cause categorization (forgot, transport, cancelled day-of, reschedule)
- Automated appointment reminder workflows (SMS at 48hrs, 24hrs, and 1hr) — content is PHI-free by design (e.g. "You have an appointment tomorrow at 9am — reply Y to confirm"), never including diagnosis, provider name, or anything identifiable beyond appointment time
- A follow-up queue showing patients due for routine check-ups, lab follow-ups, or referral confirmations
- Post-visit survey automation with results landing in Airtable for review
The EMR keeps doing what it does well. The operations layer answers the questions the EMR can't.
Compliance Documentation as a System
Audits happen. When they do, having documentation organized and current is worth weeks of relief. Most practices' compliance docs live in a shared drive that's accreted over years, with no system for tracking expirations or covered employees.
We build a structured compliance database:
- Employees table with each role, hire date, license info, and credentialing status
- Training records linked to employees, with expiration dates and renewal automation
- Policies and consents with version tracking
- BAAs and vendor contracts with renewal reminders
- OSHA logs with the required incident details
A monthly compliance report surfaces anything within 60 days of expiration. An audit-ready export is one click.
For more on the documentation patterns underneath, see our linked records guide and collaboration features overview.
Practice Performance Dashboards
Most practice managers don't have a dashboard. They have a series of monthly reports, none of which agree with each other, and they spend a half-day a month assembling slides for the partners' meeting.
A real operations dashboard pulls from EMR, billing, and the Airtable operations layer to surface:
- Patient volume by provider, by day, by month
- No-show rate with trending
- Referral funnel — incoming, scheduled, completed, with conversion percentages
- Payer mix and reimbursement aging
- Average wait time from check-in to clinician contact
- Practice growth — new vs returning patients
Refreshed daily, accessible to the partners and managers in their own interface. The monthly review meeting becomes a discussion of the numbers rather than a manual reporting exercise.
HIPAA, BAAs, and What Airtable Specifically Restricts
We won't go a step further on patient data than the legal coverage allows. The compliance chain for an Airtable-based healthcare workflow:
- Airtable Enterprise Scale plan — the only Airtable tier on which HIPAA support is offered. Requires a signed Business Associate Addendum and a Health Information Exhibit.
- Make Enterprise plan with BAA — required if PHI flows through any Make scenario.
- Any other tool in the stack — must also sign a BAA before patient data touches it.
Airtable's own published restrictions for handling PHI (which we enforce in every build):
- No PHI in email subject lines or bodies — Airtable can't guarantee TLS encryption between Airtable's mail servers and the recipient. Any PHI in automation-generated email is non-compliant.
- PHI only in records — never in base names, table names, view names, or workspace identifiers.
- No "send record" feature with PHI — those emails route through unsecured paths.
- No Airtable AI in workspaces with PHI — AI features must be disabled for these workspaces.
- No patient portal use — Airtable's documentation states "Do not use Airtable as a patient portal at this time." Patient-facing PHI portals must use a certified third-party product.
- No PHI shared with Airtable support — screenshots, tickets, and support calls cannot include PHI.
- Third-party integrations require careful review — every integration that touches PHI needs its own BAA chain.
Beyond Airtable's specific rules:
- Field-level permissions restrict PHI to clinical staff only
- Audit logging captures all record access
- Encryption at rest and in transit at the BAA tier
- Multi-factor authentication for every user
- Forms collecting PHI live on a certified portal tool, not on Airtable
For practices subject to state-specific rules (controlled substance registries, telehealth licensure, breach notification timelines), we add validations and report templates to match.
The Tools We Use and Why
Airtable Enterprise Scale is the structured database for the operational data — appointments, referrals, compliance docs, scheduling. Enterprise Scale is the only tier where HIPAA BAA support is offered, with the required field-level permissions and audit logging.
Make Enterprise (with BAA) handles automation — operational intake → record creation, appointment reminder dispatch (PHI-free content), daily report generation, referral status transitions.
A HIPAA-certified intake/portal tool (Phreesia, Klara, Mend, Athena's patient portal, or your EMR's intake module) handles the patient-facing PHI side. Airtable explicitly cannot fill this role.
Twilio for SMS reminders configured with HIPAA-compliant settings, with reminder content designed to be PHI-free.
Real Results from Healthcare Practices
Our healthcare automation clients typically see:
- 70-80% reduction in front desk time spent on data entry — intake comes in pre-structured
- 15-30% drop in no-show rates — automated reminders catch patients who would have forgotten
- 50% faster referral processing — referrals don't sit in an inbox waiting for someone to act
- Audit-ready compliance documentation instead of an annual scramble
For a 10-provider practice, this typically pays back the implementation within 3-6 months.
Who This Is For
This solution works best for outpatient practices of 5-50 staff that:
- Have an EMR they're keeping but find operational tasks live outside it
- Need HIPAA-aware automation but can't justify enterprise practice management software ($50k-200k/year)
- Have grown beyond what spreadsheets and paper can handle
- Value flexibility and want a system that adapts to their workflow rather than the other way around
- Have ownership or management willing to lead the change
If your practice has an EMR doing 100% of operational work effectively, you don't need us. If your practice has clinical staff doing significant operational work that automation could absorb, you do.
Where to Go Next
For the underlying automation patterns, see our Airtable automation guide and Make automation guide. For the form-and-portal layer, the Softr client portal tutorial covers what the patient-facing side typically looks like.
To discuss a specific practice setup, get in touch and we'll walk through your workflows.
