Dependent Appointment Rescheduling
Design a healthcare rescheduling flow that protects linked appointments, preparation steps, and transport arrangements.
The brief
Understand the problem
Background
A specialist visit may depend on lab work, imaging, fasting, an interpreter, or arranged transport. Moving one appointment without checking those dependencies can delay care or create duplicate work.
User context
Rosa needs to move her cardiology review because of a work conflict. Her blood test must happen within seven days beforehand, and hospital transport is already reserved.
Product problem
Patients need to see the consequences of a schedule change before committing, while clinics need to preserve clinical timing and limited support resources.
Objective
Create a rescheduling journey that identifies linked care, offers viable alternatives, and confirms every affected service.
What to design
Define the experience
Required experience
- Open an appointment and inspect its dependencies
- Compare replacement slots by clinical and practical fit
- Review changes to linked services
- Confirm the new care plan and receive updated instructions
Screens and states
- Appointment detail
- Replacement slot search
- Dependency review
- Updated care plan
Core user flow
Follow the critical path
- 01
Rosa selects her cardiology visit and chooses to reschedule
- 02
The service explains that the blood test and transport are linked
- 03
She selects a later visit with a compatible lab window
- 04
She confirms all three changes and receives revised preparation details
Product rules
Requirements and constraints
Requirements
- Show hard clinical dependencies separately from optional conveniences
- Reserve a proposed slot long enough to review linked changes
- Require confirmation for each canceled or rebooked service
- Provide a clinic contact route when no safe combination exists
Constraints
- Clinical timing rules cannot be overridden by the patient interface
- A support service cannot be assumed available until confirmed
- Cancellation fees and deadlines must appear before commitment
Reality check
States worth considering
Finish line
What to deliver
- Four responsive screens showing a successful linked reschedule and one blocked combination
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.