Travel Dates
Use the Travel Dates screen to add or update travel periods for a selected coverage.
This screen includes:
- A selected coverage context for the active policy.
- Date pickers for Travel start date and Travel end date.
- Inline validation for missing or invalid date ranges.
- A primary action that submits the travel-date range.
- A Stored dates section that lists existing travel periods.
- Grouping for stored entries by Upcoming, Ongoing, and Past status, when applicable.
Workflow 1 – Create coverage with travel dates
-
Open the coverage creation flow.
-
Collect the required coverage and patient data.
-
Enter the travel start date and travel end date.
-
Submit the coverage request.
-
The platform validates:
- coverage data,
- required identifiers,
- travel date range.
Success: If validation succeeds, the platform creates the coverage and stores the submitted travel dates.
Failure: - If validation fails, the platform returns validation errors and the UI remains editable.
Workflow 2 – Add or update travel dates for an existing coverage
- Open My Coverage.
- Select Travel dates for the relevant coverage.
- Enter the travel start date and travel end date.
- Submit the travel-date request.
- The platform validates the submitted date range against:
- coverage validity,
- existing travel periods,
- date-order rules.
- If validation succeeds, the platform stores the new travel-date entry and returns the updated list.
- The client updates the Stored dates section and groups entries by Upcoming, Ongoing, and Past.
Failure: - If validation fails, the platform returns validation errors and the UI remains editable.
Validations
These rules define travel-date validation behavior for coverage-linked travel periods.
| Condition | App behavior | SDK output |
|---|---|---|
| Travel start date is empty. | Block submission and highlight the field. | Validation error indicating missing start date. |
| Travel end date is empty. | Block submission and highlight the field. | Validation error indicating missing end date. |
| Start date is later than end date. | Display error and block submission. | Validation error indicating invalid date range. |
| Entered dates fall outside the coverage validity period. | Display error and block submission. | Validation error indicating dates outside coverage validity. |
| New dates overlap with an existing travel period. | Display error and block submission. | Validation error indicating overlapping date range. |
Actions
These actions define runtime behavior for travel-date creation and update.
| Condition | App behavior | SDK output |
|---|---|---|
| Coverage is created with travel dates. | Proceed in the flow and display updated coverage data. | Response includes the created coverage and stored travel-date entries. |
| A new travel-date range is added. | Update the stored dates view. | Response includes the updated travel-date entries. |
| Stored dates section expands. | Display existing travel periods grouped by status. | Previously returned date ranges remain available in client state, or are re-requested based on implementation. |
| Dialog closes without submission. | Return to the previous screen without changes. | No update returned. |
Endpoint Resources
Travel Dates
PUT
v3/travel-dates
Show Travel Date Details
Add Travel Dates Form
PUT
v3/travel-dates/add
Open form to add travel date.
Add Draft Travel Date
PATCH
v3/travel-dates/add
Validate Add form and add draft row to main screen via patch replace.
Save Travel Dates
POST
v3/travel-dates/create
Save travel dates and close.