Closed laurenernest closed 3 years ago
Given the various logic a user has to pass through to make an appointment, every path in the VA request flow needs to appropriately account for the proper context and consistency
Ideally this documentation would include:
Data presented with each page
Screenshots of an example state for each
[ ] Document current VA request pages in flow
[ ] Document states of each page
Types of care with VA requests available:
See #16917 for a similar example
@outerpress Documented here: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/appointments/va-online-scheduling/design/request_flow.md
Thanks Jeff! This looks great. The different error states are especially helpful.
Description
Given the various logic a user has to pass through to make an appointment, every path in the VA request flow needs to appropriately account for the proper context and consistency
Ideally this documentation would include:
Data presented with each page
Screenshots of an example state for each
Tasks
[ ] Document current VA request pages in flow
[ ] Document states of each page
Additional Notes
Types of care with VA requests available:
See #16917 for a similar example