Back to all articles
Patient Experience

Designing patient portals for services that need discretion

6 min read

Most patient portal design assumes a baseline: patients are comfortable with clinic names appearing in emails, results being sent by default, and household members occasionally seeing a notification on a shared device. Sexual health services can't assume any of that, and designing for the exception turned out to make the whole portal better, not just the sensitive parts of it.

Notifications are where privacy actually breaks

The record itself can be perfectly secure and still leak sensitive information through a badly worded push notification or email subject line visible on a lock screen. "Your appointment at [Clinic Name] is tomorrow" can say more than a patient wants shared with whoever glances at their phone. Configurable notification wording, generic enough to be safe by default but specific enough to be useful, turned out to be one of the highest-value, least glamorous features we built.

Consent has to be a first-class object, not a checkbox

Proxy access for a partner or family member, communication preferences, and visibility of specific record sections all needed to be genuinely configurable per patient, not a single global setting. Building consent as a structured, queryable part of the record, rather than a static form filled in once, meant it could actually be enforced consistently across the patient portal, notifications, and staff-facing systems.

  • Default settings should protect the most vulnerable use case, not the average one.
  • Every communication channel needs its own privacy review. Email, SMS and push notifications all leak differently.
  • Consent changes should be as easy to make as the original consent was to give.

Why this benefits every specialty, not just sexual health

Mental health, HIV care, safeguarding-sensitive community care: the list of services where discretion matters is longer than it first appears. Building the pattern once, thoroughly, for the service that needed it most meant every other specialty on the platform inherited a stronger default than it would have gotten if privacy had been treated as an edge case.

Want this applied to your service?

Book a demo and let's talk about what's relevant to your specialty.