department-of-veterans-affairs / va-mobile-app

"If VA were a company, it would have a flagship mobile app."
https://department-of-veterans-affairs.github.io/va-mobile-app/
17 stars 2 forks source link

Implement Type of Care & SubType screen transition logic - Audiology & speech #3421

Closed MekoHong closed 1 year ago

MekoHong commented 2 years ago

Description

As a Veteran, I want to schedule an appt for audiology & speech using the mobile app

Audiology subtype screen only comes into play if the user is CC eligible.

As part of this story we want to: • Implement screen transition rules when a user selects service Audiology and speech

Acceptance Criteria

**Type of Care Screen (Start)** 1. - [ ] Update Type of Care Screen to ALWAYS display Audiology & speech (including hearing aid support) care type 2. - [ ] Verify when a user selects Audiology & speech and upon continue make Get request `GET v0/appointments/community_care/eligibility/{service_type}` 3. - [ ] If `v0/appointments/community_care/eligibility/{service_type}` is still loading, display loading modal with no text (we will work with design for content message and include in future ticket) 4. - [ ] If `v0/appointments/community_care/eligibility/{service_type}` service fails, display common app not working component message see screen shot below 5. - [ ] Once API call has completed, show the next screen based on the following criteria using responses from `/v0/appointments/va/eligibility` and `/v0/appointments/community_care/eligibility/{service_type}` - If `requestEligibleFacilities` or `directEligibleFacilities` facility IDs are listed for service type `audiology` from the VA eligibility call AND CC `eligible` = true than show Facility Type screen - If `requestEligibleFacilities` or `directEligibleFacilities` facility IDs are listed for service type `audiology` from the VA eligibility call AND CC `eligible` = False than show Facilities Reason for Care Screen - If `requestEligibleFacilities` or `directEligibleFacilities` is `null` for service type `audiology` from the VA eligibility call AND CC `eligible` = `False` than show the scheduling help modal - - If `requestEligibleFacilities` or `directEligibleFacilities` is `null` for service type `audiology` from the VA eligibility call AND CC `eligible` = `True` than show the Audiology Subtype screen **Facility Type Screen** 6. If user lands on the Facility type screen implement the following logic (when service type = Audiology & speech) - If user selects VA Medical Center or Clinic than direct user to facilities reason for visit screen - If user selects Community Care than direct user to Audiology SubType screen **Audiology Subtype Screen** 7. - [ ] Verify both 'Routine hearing exam' and Hearing aid support radio options are enabled if a user lands on this screen 8. - [ ] Verify when selecting either option and upon selecting Continue the user is directed to the CC Reason for appointment screen 9. - [ ] Verify if user selects continue without choosing care type in line message Please choose type of [type of care] 10. - [ ] Verify if user selects Need help choosing link they are shown the SubType Help Modal (ticket #3188) 11. - [ ] Verify if user selects the Back button they are directed back to the previous screen (Facility type screen) 12. - [ ] Verify when selecting Cancel the user is shown the Cancel snack bar 13. - [ ] Verify when selecting the '?' help icon the user is shown the appointments general help modal User Flow: https://www.figma.com/file/MKa88criOi0hLEVXjqjjcL/Appointment-Scheduling?node-id=1382%3A2989 **Accessibility Requirements** N/A **Test Account(s)** judy.morrison (CC/VA eligible) vets.gov.user+41 (VA eligible) patient998@id.me (VA eligible/CC eligible for Primary Care only) confirm should go through VA flow for this use case App not working message: ![Screen Shot 2022-06-30 at 3 11 10 PM](https://user-images.githubusercontent.com/90273080/176758921-fd815cc4-1bce-4b51-ac47-81d301739a43.png) ## Notes & Open Questions - Dependencies/Roadblocks: - Any internal/external dependencies? - Test accounts needed? - Does this require QA? - Dev Notes: ## Ticket Checklist - [X] Acceptance criteria defined - [X] Labels added (front-end, back-end, feature) - [X] Linked to an Epic
MekoHong commented 1 year ago

Closing ticket, feature not being currently worked and due to lapse in time it was decided to close all scheduling tickets. No testing of tickets and will revisit in future