Telehealth Visit

Prepare for a virtual visit with identity, device check, consent, symptoms, care-team context, and a clear handoff into the live consultation. This example brings Check in and Devices together so patients and care teams can find the next task without losing context.

It includes representative records such as Confirm identity and Check camera and microphone. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Telehealth Visit
Use this template in Figr

Template facts

Screen

Onboarding

Primary action

Join visit

Pattern

Onboarding

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Care team members need to join visit while keeping visit, provider and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Check in gives users an obvious place to start.
  • Supporting view: Devices keeps the related context close.
  • Primary action: Join visit stays visible when people need it.
  • First signal: Visit shows a useful value (3:30 PM).
  • Second signal: Provider gives additional context (Dr. Chen).
  • Sample record: Confirm identity.
  • Next record: Check camera and microphone.

States worth designing

  • No setup steps complete: say what changed, protect progress, and offer a clear next step.
  • Step in progress: say what changed, protect progress, and offer a clear next step.
  • Identity check failed: say what changed, protect progress, and offer a clear next step.
  • Invite sent: say what changed, protect progress, and offer a clear next step.
  • Access denied: say what changed, protect progress, and offer a clear next step.
  • Setup complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Check in → Devices → Join visit → Review outcome

Patterns used

Onboarding, Check in, Devices, contextual actions, error recovery

Why these choices work

Make each setup step and completion state clear. Allow admins to resume without repeating the work they finished.

Pay attention to check in and devices. People need to distinguish Confirm identity from Check camera and microphone. Keep visit visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Join visit”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Referral Management, Wellness Progress, Insurance Verification.

Start from this in Figr

Design a telehealth visit screen inside our existing product. Use our current components, tokens and content language. Include Check in and Devices views, credible records like Confirm identity, and a clear “Join visit” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr