The site, end to end — programs, intake, consent, booking.
TL;DR — A SCREENER CAN STOP HERE
Forma Medical Wellness is a live telehealth platform for a New York practice — treatment programs, a rule-based eligibility questionnaire, clinical intake, two-document e-sign consent, and an in-app scheduler that creates the Zoom visit — plus an in-app patient CRM the clinician runs the practice from: a self-populating directory, per-patient records, follow-ups, and a contact log. Built 0 → 1, solo, self-hosted on AWS where the HIPAA BAA is free. Live at formamedicalwellness.com.
A real telehealth front door, without enterprise SaaS prices
The client is an ER doctor whose hours change weekly, and his practice needed intake, consent, payment, and scheduling without living inside a clunky EHR — or paying enterprise prices for a “HIPAA-eligible” stack. The app handles PHI, so the host needs a signed BAA: enterprise-only at Vercel and Render, free and self-serve at AWS.
✦ NORTH STAR
“The compliance-and-cost problem was really a hosting problem.”
Treatment programs up front — GLP-1 weight care by generic name, per the client's compliance call.
02 — SOLUTION
Ship fast, then replace the rented parts with owned ones
A visitor browses programs, passes the eligibility questionnaire, completes intake, e-signs two consents, and books a Zoom visit. The clinician's side grew into a full workspace: a dashboard for intakes and visits, and an in-app CRM — every patient's whole history in one record, with follow-ups and a contact log so nobody slips through the cracks.
The rule-based eligibility questionnaire, start to finish — no AI, just honest rules.
The patient CRM in one take — the directory, a record, a follow-up scheduled, and the dashboard showing it due.
The same homepage, cookie-switched — tap a language.
The clinician dashboard — upcoming visits and follow-ups due, soonest first.
INSIGHTThe two retention toolsNo Salesforce clone — the CRM adds exactly what a small practice needs to keep patients: follow-ups that surface as due and overdue, and a contact log of every call, text, and email.
INSIGHTBMI is clinician-onlyHeight and weight are collected in intake, but the computed BMI shows only in the admin view — no discouraging on-screen number for the patient.
03 — UNDER THE HOOD
The same screens, flipped over
No AI at runtime — the questionnaire is rule-based and every flow deterministic, which is what a medical intake should be. Even the CRM has no patients table: a patient is an aggregation over the tables the funnel already fills, keyed by email. Toggle any screen below to see the code behind it.
FRONTENDNext.js 15 · React 19 · Tailwind 4
BACKENDSupabase Postgres · Drizzle ORM · Auth.js
INTEGRATIONSZoom S2S OAuth · SendGrid
HOSTINGAWS Amplify SSR — free HIPAA BAA
KEY SCREEN A · PATIENT DIRECTORY
UNDER THE HOOD · THIS EXACT SCREEN
const map = new Map<string, PatientSummary>();
for (const pv of core.preVisits) {
const p = get(pv.email); // merge by normalized email
if (!p.name) p.name = `${pv.firstName} ${pv.lastName}`.trim();
if (pv.slug) p._cond.add(conditionLabel(pv.slug));
p.intakeCount += 1;
if (!pv.paid) p.unpaid = true;
p.lastActivity = maxIso(p.lastActivity, iso(pv.createdAt));
}
There is no patients table — a patient is an aggregation keyed by email over the funnel's own tables, so the directory populates itself with zero data entry.
Same screen, both faces — every patient, no data entry.
KEY SCREEN B · PATIENT RECORD
UNDER THE HOOD · THIS EXACT SCREEN
CREATE TYPE "follow_up_status" AS ENUM('open', 'done');
CREATE TABLE "follow_ups" (
"id" uuid PRIMARY KEY DEFAULT gen_random_uuid() NOT NULL,
"patient_email" text NOT NULL,
"due_date" text NOT NULL,
"reason" text NOT NULL,
"status" "follow_up_status" DEFAULT 'open' NOT NULL,
"completed_at" timestamp with time zone
);
Follow-ups and the contact log hang off the patient's email — migration 0007 added the only two tables the CRM needed.
Same screen, both faces — the practice's memory of one person.
04 — DECISIONS
What I said no to
✕ REJECTEDVercel / Render hostingPHI needs a signed BAA — Enterprise-only there, free and self-serve on AWS via Artifact.
✕ REJECTEDThe embedded EHR calendarCharmHealth's flow was painful for weekly-changing hours — replaced by the in-app scheduler.
✕ REJECTEDDocuSignA timestamped typed-name signature stored in the DB is ESIGN-valid, free, and self-contained — no extra vendor, no extra BAA.
✕ REJECTEDA third-party CRMPiping PHI into HubSpot or Salesforce means another BAA and a data-egress review each — building on the practice's own Postgres keeps the compliance surface small.
A NOTE ON HONESTY
“Every screenshot and recording here uses test accounts only — patient-facing software means real people's health data, and none of it belongs in a portfolio.”
05 — REFLECTION
The expensive bugs live in the boundaries
The expensive bugs lived in the boundaries, not the product code — Amplify quietly withholding env vars from the SSR runtime, a day lost to Wix squatting a DNS record until one “Unassign” click freed it. On a regulated, self-hosted stack: verify the deployed thing, not the local one. And the platform's second act was reorganization, not addition — the CRM is the same funnel data, turned around to face the person.