Notification MVP (Texting for Medical Appointments)

[lkoenigsberg]

Launch the notification MVP, allowing users to start/stop receiving text message reminder of upcoming medical appointments. This is the first step towards an overall strategy to build a unified notification engine that business lines to send effective digital notifications.

This project will leverage the existing VetText product which already delivers text notifications (via Twillio) to Veterans for medical appointments to all but 1 of the VA's locations. The VetText and Vet360 teams are partnering to store and expose this user preference.

Or primary goal is to give Veterans greater access to managing and controlling their existing VA settings and preferences.

Initial Invision mocks show the basic user experience, further outlined below.

Target Completion: End August

Requirements

Data

• Endpoint is textMessagePermInd and will have one of three values:
  • True = text notification is enabled
  • False = text notification is disabled
  • Null = text notification is unknown and should be considered disabled

User Navigation Menu

• Add an item between Account and Sign Out which reads "Notifications"
• This new item will only be present if the logged in user is identified as having Health Care benefits
• Clicking on "Notifications" from the user menu will take users to the Notifications landing page

Notifications Landing Page

• Breadcrumb = Home (link to VA.gov) --> Notifications
• Content of page TBD, use mocks as starting point. Do need to add an "edit" next to the mobile phone number shown. This takes users to their profile contact information to edit.
• URL = va.gov/notifications (verify with IA folks on VSP)

Considerations/Open Items

• What displays on the notification page if the user has healthcare but does not have a mobile phone number as part of their contact information?
• What error considerations do we need to account for at the save point?
• What Is the overall UX upon save, error or not? (Profile shows an in progress msg and then confirm/error)
• Review and update launch checklist so that it includes only what is needed
• Define launch marketing/promotion plan

Launch Checklist

List of tasks that will need to take place in order to go live. No particular order and some might not be necessary for this effort.

• [ ] Usability testing complete
• [ ] Staging QA
• [ ] 508 audit complete
• [ ] Unit tests complete
• [ ] e2e manual testing complete, and bugs fixed
• [ ] UAT complete and successful
• [ ] Security expert review
• [ ] Content expert review
• [ ] IA expert review
• [ ] Load testing complete
• [ ] Rate limit set
• [ ] Downtime notification rules and messaging set
• [ ] Analytics setup (#747)
• [ ] Monitoring setup
• [ ] Error logging configured
• [ ] Call centers are ready (Product Outline and Demo Video)
• [ ] Platform is prepared to disable via feature flag
• [ ] Brief stakeholders
• [ ] Go/No-go complete and successful
• [ ] Product launched!

[elwoodva]

This is the latest mockup: https://adhoc.invisionapp.com/share/FSTDOO0WUHC#/screens/378179664