Start Walk-In Flow
Use Start Walk-In Flow to create an appointment without a prior booking.
The doctor selects coverage and visit location, and the app validates eligibility for the selected combination.
When supported, the app displays a scannable QR code for payment.
This screen includes:
- A list of eligible insurers based on platform configuration and eligibility rules.
- A required location selector with options such as Home and Clinic.
- An optional partner selector that depends on the selected insurer.
- Eligibility validation for each insurer and location combination.
- A QR code view when the selected option qualifies. See Generate QR Code for Walk-In.
Workflow
Start a Walk-In Appointment
Select an insurer before you select a location.
- On the Appointment screen, select Walk-In.
- Select an insurer from the list.
- Select a location.
The app runs eligibility checks after insurer and location selection.
- If the app displays a QR code, continue with Generate QR Code for Walk-In.
- If the app does not display a QR code, follow the manual payment instructions shown on screen.
Validations
These scenarios describe how the app validates the Start Walk-In Flow screen and what the integrator can expect.
| Scenario | App Behavior | SDK Output | Example |
|---|---|---|---|
| No insurer is selected. | The app blocks progression and keeps the user on insurer selection. | Validation error; no eligibility check. | — |
| No location is selected. | The app blocks eligibility evaluation that requires location. | Validation error; no QR evaluation. | — |
| The insurer requires a partner. | The app displays the partner selector. | UI state includes partner field. | — |
| The insurer and location combination is eligible for QR. | The app displays a scannable QR code. | Response includes QR state and payload. | — |
| The QR code is expired. | The app displays a QR_EXPIRED error. | Error state in response. | — |
| The insurer configuration is invalid. | The app disables or hides dependent controls and displays guidance. | Error state or missing UI elements. | — |
Actions
These scenarios describe how the app responds to actions on the Start Walk-In Flow screen and what the SDK returns.
| Scenario | App Behavior | SDK Output | Example |
|---|---|---|---|
| The doctor opens Walk-In. | The app displays the coverage selection screen. | Page response for walk-in coverage. | — |
| The doctor selects an insurer. | The app updates available options and eligibility state. | Update set for insurer selection. | — |
| The doctor selects a location. | The app evaluates eligibility for the combination. | Update set for location selection. | — |
| The selection qualifies for QR. | The app displays the QR code. | Response includes QR data. | — |
| The selection does not qualify for QR. | The app displays manual payment instructions. | Response includes non-QR state. | — |
Endpoint Resources
Select Coverage
PUT
/profile/walk-in/coverage
Displays the insurer selection step for the walk-in flow..
UI Element Types
| Level | Reference | Type | Value |
|---|---|---|---|
| 1 | change-language | Toolbar | [Language] |
| 1 | subtitle | Subtitle | Select the patient's coverage |
| 1 | company a | Secondary | Company A's name |
| 1 | ... | Secondary | ... |
| 1 | company b | Secondary | Company B's name |
Change Doctor
PATCH
/profile/walk-in/change-profile
Updates the walk-in flow after doctor selection.
Change Location
PATCH
/profile/walk-in/change-location
Updates the walk-in flow after location selection.
