Patient portal adoption in US healthcare runs 30-40% by most industry benchmarks. The portals we've shipped tend to land in the 60-80% range. The teams hitting those numbers are not building better software than their peers. They're measuring four specific things that most healthcare product teams don't bother measuring at all.
What most teams measure (and why it doesn't help)
Walk into any patient portal team's QBR and you'll see the same metrics: registered users, monthly active users, total logins. These tell you nothing about whether the portal is doing its job.
Registered users is supply (patients with accounts), not demand (patients getting value). MAU is too lagging. Total logins counts power users many times and disengaged patients zero.
What you actually need is funnel data on what patients try to do, where they drop off, and what they come back for.
Metric 1: Activation rate by intent
Patients sign up for portals for specific reasons: a test result, a bill, an appointment, a message from a provider. Activation rate by intent measures, for each entry reason, what percentage of patients who arrived for that reason actually completed it.
Example: of patients who arrive intending to view a lab result, what percentage view it within their first session? A portal that's 90% on "view lab result" but 30% on "pay a bill" is telling you the bill-pay flow is broken, regardless of overall MAU.
Most teams can't compute this because they don't capture intent. Capture it: a one-question modal on first login ("What brings you here today?") and you suddenly have segmented adoption data.
Metric 2: 7-day return rate
30-day retention is the industry default. It's the wrong horizon for patient portals.
Healthcare interactions are episodic. A patient might sign up after a visit, come back twice in the next week, then not return for three months — and that's the right pattern. Tracking 30-day return rate punishes that pattern artificially.
7-day return rate, in our experience, correlates much better with longer-term engagement. A patient who came back within 7 days found enough value to come back. The 30-day window includes too many patients who returned by accident or because they got an email.
Benchmark: portals with 7-day return rates above 35% tend to land in the 60-80% adoption tier over 12 months. Portals below 25% rarely get there, regardless of what's built on top.
Metric 3: Task completion vs. session count
Two patient journeys produce the same MAU number but tell very different stories.
Journey A: a patient logs in, finds what they need in 90 seconds, logs out. They return three weeks later for the next thing.
Journey B: a patient logs in, doesn't find what they need, logs in again the next day, asks a family member to help, logs in a third time, gives up and calls the front desk.
Both patients counted toward MAU three times. Journey A is success. Journey B is failure in slow motion.
The metric that separates them: tasks completed per session. If a portal's tasks-per-session is trending up, that's good. If sessions-per-task is trending up, that's bad — patients are working harder for the same outcome.
Metric 4: Off-ramp tracking
Every patient portal has off-ramps: phone calls to the front desk, walk-ins, faxes, secure messages with simple questions, third-party booking tools. These are the things the portal was meant to replace — and they're the actual measure of the portal's success.
If your patient portal MAU doubled but front-desk call volume stayed flat, the portal didn't replace the phone. It added to it. That's a different kind of failure than "low adoption."
Tracking off-ramps requires cooperation with operational teams (and sometimes a small change to their phone or scheduling systems to capture reason codes). The teams that do this get unmistakable signal about what the portal isn't doing for patients yet.
The portal is winning when the phone is quieter. Not when MAU goes up.
The conversion funnel that matters
When we work on portal adoption, we instrument this funnel explicitly:
- Notified — patient received the signup invitation (email, text, post-visit handout).
- Started — clicked through to begin signup.
- Verified — completed identity verification.
- First task — completed the first action they came to do.
- Returning — came back within 7 days for any reason.
- Repeat task — completed a second meaningful task.
The biggest drop-off is usually Notified → Started (typically 70-85% loss). The second biggest is Verified → First task (typically 30-50% loss). If you can fix either of these, adoption moves a lot.
What to fix first
If we had to recommend one thing to fix in a typical portal: redesign the post-verification landing page around intent. Most portals dump verified patients onto a generic dashboard with 12 menu items. They should land on the thing they came to do.
If we had to recommend a second thing: shorten identity verification. Every additional question loses 5-15% of patients. Most portals over-collect during verification because the EHR team wanted the data — not because the security model required it. Push back hard on this.
If we had to recommend a third thing: instrument the off-ramps. You can't fix what you can't see, and most teams are flying blind on this dimension.
Closing
Patient portal adoption isn't a UI problem. It's an instrumentation problem. The teams that get to 60-80% know exactly what their patients are trying to do, where they drop off, and what they fall back to when the portal fails them. The teams stuck at 30-40% have a generic adoption funnel and a vague sense that "engagement is lower than we'd like."
Measure the four things in this article and you'll move adoption regardless of what else you do.