Technology

The Patient Portal Playbook: What to Build, What to Skip, and What Actually Drives Repeat Orders

Most clinic patient portals are built for the clinic's benefit, not the patient's. The ones that actually drive repeat orders and long-term retention are built around a much shorter list of features — and they get those features exactly right.

Dom PaulDom Paul·20 May 2026·8 min read

A patient portal sounds like an obvious investment. Patients can log in, view their records, reorder their medication, and track their progress. You reduce inbound calls, improve retention, and give your clinic a professional digital presence.

The reality is that most patient portals fail to deliver on that promise. Patients register, log in once or twice, and then abandon the portal entirely. Repeat orders still come in by phone. Progress tracking goes unused. The clinic ends up maintaining two parallel workflows: the portal for patients who remember to use it, and manual processes for everyone else.

The difference between a portal that patients actually use and one that sits idle is not the number of features. It is whether the right features work well enough to be worth the friction of logging in at all.

Table of Contents

  1. Start With the Job the Portal Needs to Do
  2. Repeat Ordering: The Feature That Justifies Everything Else
  3. Login Friction: The Silent Killer of Portal Adoption
  4. Progress Tracking: What to Surface and What to Skip
  5. Assessment Editing: Why This Matters More Than Most Clinics Realise
  6. What to Skip
  7. The Features That Actually Drive Retention
  8. How to Roll Out a Portal That Gets Used

Start With the Job the Portal Needs to Do

Before you build anything, define what the portal is actually for. Not in general terms, but specifically for your patient mix and your service model.

For a weight loss clinic running GLP-1 prescriptions, the portal's primary job is to make it easy for patients to continue their treatment month after month with minimal friction. That means ordering their next supply, updating their health information if anything has changed, and seeing enough of their own progress data to stay motivated.

For a travel health clinic, the portal's primary job is different. It needs to surface upcoming vaccination schedules, allow patients to book follow-up appointments, and store their vaccination history in a format they can share with a travel insurance provider or border control.

The features you build should follow directly from that primary job. Every feature that does not serve it directly is noise that makes the portal harder to navigate, slower to load, and less likely to be used.


Repeat Ordering: The Feature That Justifies Everything Else

For any clinic running a subscription-based or recurring treatment service, repeat ordering is the one feature that has to work perfectly. It is the reason most patients would log in at all.

A repeat ordering flow that works has three characteristics. It is fast (the patient can complete the order in under three minutes). It is clinically safe (the patient is prompted to update any health information that might affect their prescription before the order is processed). And it is transparent (the patient can see the status of their order from submission through to despatch).

A repeat ordering flow that fails typically fails in one of two ways. Either it requires the patient to complete a full assessment form every time they order, even when nothing has changed, which makes ordering by phone feel easier. Or it asks no clinical questions at all, which creates a prescribing risk if a patient's health status has changed since their last order.

The right approach is conditional re-assessment. The patient is asked a short set of screening questions: has their weight changed significantly, are they experiencing any side effects, have they started any new medications. If all answers indicate no change, the order proceeds. If any answer indicates a change, the patient is routed into a fuller clinical review before the order is processed.

This approach reduces the friction for the majority of straightforward repeat orders while maintaining the clinical safeguard for the minority where something has changed.


Login Friction: The Silent Killer of Portal Adoption

Login friction is the most common reason that portals go unused, and it is almost always underestimated by the team that built the portal.

The problem is not that patients find it hard to log in once they have an account. The problem is the sequence of events that happens before they get there. A patient who cannot remember their password and is asked to retrieve it by email has to:

  1. Navigate away from the portal to their email client
  2. Find the reset email (or not find it, if it went to spam)
  3. Click the link, set a new password, and navigate back
  4. Log in again

For a patient who wanted to place a quick repeat order before they ran out of medication, that sequence is enough to make them call the clinic instead. And once they have called once and found it easier, the portal adoption rate for that patient drops to near zero.

The solutions are well established. Magic link login (where a patient receives a one-click login link by email or SMS) eliminates the password problem entirely. Persistent sessions on trusted devices mean a patient who logs in on their phone does not need to log in again next month. Biometric authentication on mobile (Face ID or fingerprint) reduces the login step to a fraction of a second.

The implementation choice depends on your portal platform, but the principle is the same: every additional step between a patient deciding to log in and reaching their dashboard is a dropout opportunity. Measure your login completion rate. If it is below 80%, the authentication flow is losing you patients before they reach the features you built.


Progress Tracking: What to Surface and What to Skip

Weight loss and chronic condition management clinics are often tempted to build comprehensive progress dashboards. The vision is a patient who logs in regularly, tracks their metrics, feels engaged with their treatment, and therefore continues it.

The reality is more nuanced. Patients engage with progress data when it is simple, positive, and meaningful to them. They disengage when it is complex, data-heavy, or hard to interpret.

What to surface:

  • Weight at starting date versus current weight, as a single number and a trend line
  • Duration of treatment (patients who have been on a programme for six months feel invested)
  • Next appointment or next order date
  • Any unread messages from the clinical team

What to skip:

  • BMI charts with multiple lines and categories
  • Detailed pharmacokinetic information about their medication
  • Long lists of historical entries without a visual trend
  • Percentage calculations that require the patient to do mental arithmetic

The goal of progress tracking is not to give patients more data. It is to give them a reason to feel that the treatment is working and that continuing makes sense. A simple visual showing 8 kg lost over 12 weeks achieves that goal. A table of weekly weights with BMI calculations alongside them does not.


Assessment Editing: Why This Matters More Than Most Clinics Realise

Most portal builds focus on the patient-facing features and treat the clinical assessment as a fixed input. The patient fills in the assessment at the start of treatment, and that is that.

The problem is that a patient's health status changes over time. They start a new medication that interacts with their GLP-1. Their blood pressure moves into a range that affects their prescribing. They develop a new condition that was not present at the time of their original assessment.

If a patient cannot update their clinical information between appointments, two things happen. Some patients will update it voluntarily when prompted during a repeat order flow, which is good. But others will have changed circumstances that they do not connect to their treatment, and those changes will not be captured until a scheduled review.

Allowing patients to edit their own assessment, within limits, solves part of this problem. The design should allow patients to update key fields (current medications, recent diagnoses, changes in chronic conditions) with those changes flagged to the clinical team for review before the next supply is issued. This is not an open editing system. It is a structured update mechanism with clinical oversight.

The benefit is twofold: you catch clinically relevant changes earlier, and patients feel that their ongoing health is being monitored rather than that they are on autopilot between appointments.


What to Skip

The following features appear regularly in patient portal specifications and rarely justify the development time:

Document upload. Patients rarely upload documents unless they are required to complete a specific process. A document upload feature that is optional will be used by fewer than 5% of patients and creates a document management overhead for the clinical team.

In-portal messaging with a full inbox. A messaging system that patients have to log in to check is worse than SMS or email for most interactions. Patients do not check their portal inbox unprompted. If you need to communicate with a patient, send them a notification to a channel they already use.

Health goal setting. Patients who want to set health goals use the apps they already have on their phones. A goal-setting feature in a pharmacy portal competes with Apple Health, MyFitnessPal, and half a dozen other tools that do it better with more data.

Referral programmes. Referral features built into portals consistently underperform referral links sent at the right moment in a patient's journey (typically just after a positive result). A portal is not where patients go to think about recommending your clinic to a friend.


The Features That Actually Drive Retention

Across weight loss and chronic condition management portals, the features most strongly correlated with patient retention are not the most complex ones. They are the ones that remove uncertainty.

Order status notifications. A patient who knows their order has been received, approved by the prescriber, and despatched does not call the clinic to ask. More importantly, a patient who has clear visibility of their order timeline feels looked after, which is a driver of continued treatment.

Automated recall prompts. A message sent two weeks before a patient's supply is due to run out, with a direct link to the repeat ordering flow, converts at significantly higher rates than any portal feature the patient has to discover themselves.

Follow-up outcome collection. A short check-in question sent four weeks after starting treatment ("How are you finding the medication so far?") does two things. It gives the clinical team early signal on tolerability. And it makes the patient feel that someone is paying attention, which is one of the strongest retention drivers in private healthcare.

These three features require less development time than a document upload system or a goal-setting tool, and they have a direct measurable impact on repeat order rates and patient lifetime value.


How to Roll Out a Portal That Gets Used

The decision to build a patient portal is not the hard part. Getting patients to use it consistently is.

The highest-adoption portals are ones where the portal is the path of least resistance from day one. That means registering patients on the portal before or during their first appointment, not after. It means making the repeat order flow faster than calling the clinic, not the same speed. And it means using the portal proactively (sending messages through it, logging clinical notes in it, sending appointment reminders from it) so that patients have a reason to log in even when they are not placing an order.

The second factor is expectation-setting at registration. A patient who is told "we will send your monthly order reminders through the portal and you can track your progress there" is more likely to return to the portal than one who is told "you can log in if you ever need anything." Give patients a specific, concrete reason to use it.

Finally, measure usage and act on the data. Track monthly active users as a percentage of your active patient list. Track login completion rate. Track the proportion of repeat orders placed through the portal versus by phone. If those numbers are low, the portal is not doing its job and you need to understand why before adding more features.


Book a Free Discovery Call

If you are building or rebuilding a patient portal and want to understand what works in practice rather than in theory, book a free 20-minute discovery call with the Clinic Pro team.

We have designed and built patient portals for weight loss clinics, travel health services, and complex multi-service pharmacies, and we can help you get the architecture right before you commit to a build.

Book your free call below.

Next Step

Want this implemented in your clinic?

Free 30-minute strategy call. No pitch — just practical next steps.

Book a free call

More articles