HIPAA-grade scheduling for a multi-clinic network in 19 days

Multi-clinic specialist group, USA/Canada

HIPAA + PHIPA audit passed with zero findings across 14 clinics.

14

Clinics migrated

23

PHI fields encrypted

7-year

Audit log retention

The situation

  • The CTO of a Toronto-based specialist network built a working scheduling tool on Replit during a hackathon, then quietly rolled it out to all 14 clinics. It saved hours per week, the doctors loved it, and then their compliance officer found out.
  • PHI stored in plaintext columns. No audit log.
  • Auth based on shared passwords. A scheduled HIPAA + PHIPA review was 4 weeks away.

What we did

  • Column-level PHI encryption with AWS KMS-managed keys
  • Azure AD SSO with enforced MFA and group-based access
  • Immutable audit log with 7-year S3 Object Lock retention
  • Role hierarchy: clinic admin, clinician, front desk, auditor, break-glass
  • Encrypted attachment storage for clinical notes and referrals
  • Audit-ready exports for HIPAA + PHIPA reviewer requests

The result

  • The HIPAA + PHIPA audit completed with zero findings.
  • The clinic network has since added 6 more clinics without any architectural changes. The CTO uses the audit log dashboard as a recurring board agenda item, auditability has become a selling point when recruiting new specialists.

Timeline

How it unfolded

  1. Day 1

    Compliance gap analysis

  2. Days 2-4

    Encryption + KMS integration

  3. Days 4-7

    Auth rebuild + Azure AD SSO

  4. Days 7-11

    Audit log + reads

  5. Days 11-14

    Break-glass + emergency access

  6. Days 14-17

    Audit dry run

  7. Days 17-19

    Cutover + clinic migration

Our compliance officer signed off on the dry run with no findings. I have literally never seen that happen in 12 years of healthcare IT.

CTO · Specialist Clinic Network · Toronto, Canada

Stack

SupabaseAWS KMSAzure AD SSOSupabase StorageLogflare + S3Vercel Edge Functions

Want to be the next case study?

Book a call →