A patient portal is used by someone who is worried, often in a hurry, and frequently not the patient at all but a family member acting for them. Design decisions that are merely inconvenient elsewhere become genuinely harmful here.
Say what you know, and say what you do not
The most important rule in a clinical interface is that uncertainty must be visible. A result that has not been reviewed by a clinician should not look identical to one that has. A confident presentation of an unconfirmed value is worse than showing nothing, because the reader will act on it.
The same applies to gaps. If a record is incomplete, saying so builds more trust than a clean-looking screen that quietly omits it.
The edges are where these systems fail
Appointment flows work fine in the demonstration path and break at the situations that occur every day.
- A cancellation close to the appointment, where the rules differ from a normal cancellation.
- A reschedule that is really a cancellation and a new booking, with different consequences depending on which the system thinks it is.
- A caregiver booking for someone else, which means the account holder and the patient are different people and every screen has to know which it is showing.
- A patient who is also a caregiver for a parent, which is the same problem plus switching between them.
None of these are exotic. Designing for them from the start costs a fraction of retrofitting them.
Plain language is a safety feature
Clinical vocabulary in a patient-facing screen forces the reader to guess, and an anxious reader guesses badly. Write the label the way a person would say it, and keep the clinical term alongside it where it matters for continuity of care.
This extends to time and dates. “Tomorrow, 10:30 am” is understood instantly. An ISO timestamp is not.
Accessibility is not optional in this sector
The audience skews older and includes people managing conditions that affect vision, dexterity and attention. Text size, contrast, tap target size and keyboard operation are not compliance boxes here, they are the difference between a portal that works and one that gets phoned in instead.
Privacy shows up in the interface, not just the database
What appears in a notification preview on a lock screen, what is visible over a shoulder in a waiting room, how long a session stays open on a shared device. These are interface decisions with real consequences, and they are usually decided by default rather than deliberately.
We hold no healthcare compliance certification and do not present ourselves as a regulated vendor. What we can do is build to the requirements your clinical and compliance teams set, and our healthcare page is explicit about that boundary.