Patient Scheduling

Schedule patient visits with provider availability, visit type, location, waitlist, and follow-up needs visible in the same weekly view. The screen connects Schedule and Patients so care teams can find the “Book visit” action while checking appointments and open slots.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Ava Carter · Follow-up and Marcus Lee · New patient, rather than an empty visual shell.

Patient Scheduling
Use this template in Figr

Template facts

Screen

Calendar

Primary action

Book visit

Pattern

Calendar

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Care teams need a clear “Book visit” action without losing sight of appointments, open slots and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Book visit is clearly available where the task happens.
  • Main view: Schedule keeps the starting point obvious.
  • Connected view: Patients supplies nearby context.
  • Metric: Appointments is visible with a meaningful value.
  • Another signal: Open slots helps people judge what to do next.
  • Representative record: Ava Carter · Follow-up makes the example specific.
  • Second record: Marcus Lee · New patient shows the pattern works beyond one item.

States worth designing

  • No availability in selected range; show what people can do instead of leaving a blank panel.
  • Loading schedule without changing the layout unexpectedly.
  • Slot conflict or reschedule; explain the problem and preserve work.
  • Permission denied for patients; clarify who can continue.
  • Success after choosing Book visit; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Schedule → Patients → Book visit → Review outcome

Patterns used

Calendar, Schedule, Patients, Providers, accessible states, contextual actions

Why these choices work

Show timezone, time range and conflicts before a user commits. Offer a clear path back to available slots.

In this design, people should be able to compare Ava Carter · Follow-up with Marcus Lee · New patient. Make appointments clear, then use open slots to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Book visit” action. The happy path alone is not enough.

Related UI examples: Care Plan, Clinical Inbox, Provider Roster.

Start from this in Figr

Design a patient scheduling screen for our existing software product. Use our real design-system tokens, components and product language. Show Schedule and Patients, include believable records such as Ava Carter · Follow-up, and make book visit easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr