Appointment Request

Use the Appointment Request page to review provider details and enter request information.

important

This screen can vary depending on the user coverage type. Private-pay users and insured users can see different fields, labels, or sections.

This screen includes

Doctor summary header with name, specialty, date, time, coverage status, and visit type.
Coverage section that displays the selected insurance or travel policy.
Patient details selector with a required patient name field.
Contact information form with required contact name, email address, and phone number, including country code selection and label.
Medical issue field with required text input for the doctor.
Document upload action for photos or medical files.
Primary action button that continues to the next step.
Privacy notice that states data sharing with the listed provider.

Workflow

From the Home screen, the app collects:
- Coverage type.
- Patient profile.
- Location.
- Medical need or specialty.
The app displays a provider results list based on the selected criteria.
The user selects:
- A doctor.
- A visit type (for example, Home or Video).
- An available date > time
The app opens the Appointment Request screen.

These scenarios describe how the app validates the Appointment Request screen.

Scenario	App Behavior	SDK Output	Example
Required fields remain empty.	The app blocks progression and highlights missing fields.	Validation errors for required fields.	—
Email or phone number format is invalid.	The app displays inline format errors.	Validation error with field identifier.	—
Selected patient lacks mandatory data.	The app displays patient-related errors.	Validation error for patient object.	—
Coverage selection invalidates patient eligibility.	The app blocks progression and displays a generic error.	Eligibility validation error.	—
Inactivity exceeds the expiration timeout.	The app sets the request state to `expired` and disables actions.	Update set with state `expired`.	—

These scenarios describe how the app responds to actions on the Appointment Request screen.

Scenario	App Behavior	SDK Output	Example
The user selects Next with valid input.	The app proceeds to confirmation.	Update set that creates a pending request.	—
The user uploads documents.	The app attaches files to the request.	Update set with document references.	—
The user changes patient or coverage details.	The app revalidates eligibility.	Updated validation result.	—
The user leaves the screen without submission.	The app preserves the request until expiration.	No-op update set.	—
The request expires before submission.	The app disables actions and locks the request.	Update set with state `expired`.	—