Published

14 August 2026 · 2 min read

Most telemedicine work we see starts from the patient's side, and that side is genuinely easier: someone who wants a doctor will tolerate a clumsy booking flow to get one. The clinician has no such patience. They are between appointments, the previous consultation ran over, and your interface is one of six they are expected to keep open.

The consultation is not the product

A video call is a solved problem. What is not solved is everything wrapped around it — arriving at the call already knowing who the patient is, what they came for, and what happened last time; leaving it with notes filed and a prescription sent without retyping anything.

When we designed the consultation screen for a telemedicine startup, the video window ended up smaller than the client first expected. The space went to the patient's history, visible without a click, because that is what clinicians reached for in every session we watched.

Consultation screen: patient history alongside the video window
The video window gave up space to the patient's history — the thing clinicians reached for in every session.

Three things that decide whether it gets used

  • Time to context. How many seconds between opening a consultation and knowing why this person is here. If it is more than a few, clinicians open the old system in another tab and yours becomes the video widget.
  • Where the notes go. If notes have to be re-entered anywhere else, they will be entered badly, late, or not at all.
  • What happens when the connection drops. It will. Whether the consultation survives it is a design decision, not a networking one.

Privacy is an interface problem too

Health data rules shape more of the UI than teams expect. Who can see a record, for how long, and what gets logged are not settings buried in an admin panel — they show up as what a screen dares to display by default, what stays behind a deliberate action, and how a shared-device session ends.

The version that passes review and the version clinicians like are usually the same version. Both come from asking, for every field on screen, whether this person needs it right now.

Start by watching a real day

Before wireframes, sit with two clinicians through a full clinic. Not a scripted usability session — an ordinary morning, with the interruptions. Whatever they do to work around their current system is your specification.