Designing Intake That Protects Patients
Telehealth intake is a clinical instrument and a patient experience at the same time. Here's how we design it to do both jobs honestly.
Intake is the single most important screen in telehealth. It's where commerce meets clinical: a patient is describing their situation, and a clinician is gathering the evidence they'll later use to prescribe. Treating intake as either a sales step or a medical form alone produces bad outcomes. The right design respects both.
Structured data, not free text
Every answer should be a discrete, queryable field. Free-text inputs feel friendly but make clinical review slow and rules engines impossible. We use structured questions with controlled vocabularies, then offer free-text only as a follow-up for nuance.
Branching that respects time
Long flat questionnaires exhaust patients. Clinically-justified flows are easier to complete because every question is relevant. We branch aggressively on prior answers so each patient sees the shortest path through the questions that actually apply to them.
Red flags are the point
Some answers should stop the flow — contraindications, age limits, state restrictions, drug interactions. Intake should surface these clearly to both the patient and the clinical reviewer, never bury them.
Save state and let people come back
Patients leave intake to grab a list of their medications or check a dose. Saving progress and letting them resume on another device is a meaningful UX improvement — and it doubles as a clinical safety feature.
Auditability built in
Every answer, every change, every device and timestamp is part of the medical record. Intake should produce a complete, immutable record of what the patient shared and when — both for clinical quality and for regulatory defensibility.