The Problem
US healthcare loses 200. A five-provider practice running at the average 19% no-show rate bleeds roughly $192,000 annually — not from bad doctors, but from patients who don't show up.
The common explanation is scheduling friction. The real explanation is trust.
Patients who don't understand why their doctor recommended a treatment are more likely to skip the appointment. If a cardiologist prescribes statins and the patient spent the weekend reading about how statins are "over-prescribed," they'll rationalize not going. If a diabetic patient doesn't understand why an A1C check matters, it becomes easy to push it off one more week.
The deeper issue: evidence-based medicine is losing a trust war against unverified online content. The volume of evidence behind a therapy has, counterintuitively, become inversely correlated with public trust in it. Patients prefer unproven peptide protocols over generic statins that have 30 years of data. Not because they're irrational — but because no one gave them a clear, human explanation of why the evidence-backed path is right for them.
Sources:
- r/medicine — "Why do patients distrust evidence-based medicine?" — 1,021 upvotes, 215 comments
- r/nursing — burnout from repetitive patient explanations — 6,066 upvotes, 278 comments
- No-show cost data: Prospyrmed, Curogram, Clearwave
Existing patient communication tools — Podium, Curogram, Demandforce — focus on reminders and scheduling. None of them address the root problem: patients who don't trust the care plan don't show up. There's no product that owns pre-visit education as a trust-building mechanism.
The Insight
The problem isn't the reminder. It's the explanation.
Duolingo made language learning work by breaking it into bite-sized, visual, addictive daily content. Headspace made meditation accessible by stripping away complexity. Neither of those markets had an engagement problem before — they had a presentation problem.
The same reframe applies here. Medical education for patients doesn't have to be a dense PDF from the patient portal. It can be five cards on their phone, each taking under a minute to read, written in plain language, delivered in the days before the appointment. Not "Here is information about your condition." But "Here's why your doctor recommended this, what to expect, and how to prepare."
Patients who arrive informed are more likely to trust the provider, ask better questions, and follow through on the care plan.
What We Built
TrustBase is a web app for small-to-medium medical practices. A provider adds a patient and their upcoming visit type. TrustBase uses Claude to generate five personalized education cards tailored to that visit. The provider sends the content to the patient — who gets a link to a clean, mobile-first card reader — and can see in the dashboard who engaged before the appointment.
The provider flow:
- Sign up and complete onboarding (specialty selection)
- Add a patient — name, visit type, appointment date
- Click "Send Content" — Claude generates 5 education cards specific to the visit type
- Patient receives a link via email
- Dashboard shows who opened it, who completed it
The patient experience:
- A clean card reader, mobile-first
- Progress bar ("Step 2 of 5")
- One card at a time: emoji icon + headline + 2–3 sentences in plain English
- Final card confirms the appointment details and closes with encouragement
Visit types in the MVP: Cholesterol Management, Diabetes Check-in, Preventive Care, Annual Physical, Follow-up Visit.
Product Decisions
Demo mode, no real patient PHI. For the MVP, providers manually enter a patient's first name and visit type. No EHR integration, no patient login, no real health records. This keeps us entirely outside HIPAA territory for launch. The value prop is demonstrable without touching sensitive data, and real EHR integration is a post-validation problem.
Email delivery to provider, not patient. In the MVP, the content link goes to the provider's email, who can then forward or share it. This sidesteps the patient identity and communication compliance questions. It's a demo-first decision: prove the content is worth sharing before building the delivery infrastructure around it.
Bite-sized over comprehensive. Medical patient education resources are almost always too long. A 20-page pamphlet about managing type 2 diabetes doesn't get read. Five cards with clear headlines and 2–3 conversational sentences each have a real chance of being absorbed in the parking lot before the appointment. Content length was constrained deliberately.
Warm aesthetic, not clinical. Every healthcare product defaults to blue, white, and Times New Roman. TrustBase uses a warm teal and sage green palette on a warm off-white background. The goal is to feel like a modern health startup — approachable and trustworthy — not like a hospital portal that hasn't been redesigned since 2009.
Try It
Sign up as a provider, add a test patient, and send content. The patient viewer link will show you what patients see. No real Supabase or email configured in the public demo yet — that's coming once the validation round completes.
What's Next
The MVP validates the content model. A real product would need:
- EHR integration — auto-trigger content when an appointment is booked in Epic, Cerner, or Athenahealth; no manual entry
- Patient accounts and direct delivery — SMS/email directly to the patient, with tracking that doesn't require provider forwarding
- HIPAA compliance — BAA, encryption at rest, audit logging; the architecture is clean but the legal layer needs to be added
- Content quality layer — medical review workflow before content ships; Claude is good but a human review process matters when the subject is health
- Longitudinal engagement — content sequences across multiple appointments, not just one-time sends; building a patient education relationship over time