RX: List & Detail View Enhancements - build

[bischoffa]

Project Status Overview

In Q2 23' the mobile team conducted a usability research study to

• Engage with Veterans who use the Prescriptions feature recently launched in the VA: Health and Benefits Mobile app
• Surface any usability issues or points of confusion along the way in relation to prescriptions statuses and dates
• Understand their current experience refilling a prescription.

As part of this research a key finding that we would like to address

1. All participants were able to successfully refill a prescription during the session. However, participants struggled to review their full list of prescriptions in order to identify the correct prescription they were looking to refill.

Veteran Job to be done:

Veterans use the VA: Health and Benefits mobile app, Prescriptions feature to get two jobs done:

1 job: request and track refills. 2 job: view list of medications and details of a medication.

Problems to solve

• Problem A: Veterans struggle to review their full list of prescriptions to identify the correct prescription they were looking to refill.
  • Veterans struggle to review their full list of prescriptions to identify the correct prescription they were looking to refill. Participants did not use any other prescription status besides Active to determine what to refill. When prompted to define them, participants provided their own interpretation when scanning the list and the Filter options. Veterans view a list of “actionable” scripts, defined as medications they currently take or are looking to refill, without having to use “Filter by.”
• Problem B: When a filter is on, header 1 and header 2 counts are unequal.
• Problem C: Need to remove to Prescription/Refill statuses: Active: Suspended and Non-Verified as they are not used
• Problem D Help Veterans understand the app’s usage of “VA prescriptions"

Current Dependencies / Blockers

Blockers

|Blocker | Team / Owner | Est to Resolution | |-------|---------|-------| | Dr. Spahn approval of Mobile' RX design | Kay & Coulton leading discussions; Go / No Go determined by Dr. Spahn | No ETA |

Project Timeline

Milestones

**Identity Timeline:** Feb 24' - All tickets completed and merged -changes to be released on 3/12 Sept 23' - Complete Design, Content, & Data discovery/analysis & recommendations - Remove status codes Non-Verified & Active: Suspended target app release 10/10/23 Oct 23' - Mobile to provide design recommendation to Kay and Coulton no later than the end of Sprint 83 (11/7) - Rachel & Matt agreed that Mobile will only work on RX into Sprint 83 and be on hold for Q1 Nov '23 - Mobile Design recommendation delivered to Kay and Coulton for review via va-mobile-app-design [slack thread ](https://dsva.slack.com/archives/C02M11AKKNU/p1698849712471259) - Kay and Coulton to provide feedback to Mobile Team - Kay and Coulton to coordinate review with Dr. Spahn with Mobile supporting - Kay and Coulton to get Dr. Spahn's Go/No go with design and implementation

Monthly Update

Updates

|Month| Project Health | Progress & Key Accomplishments| Issues/Risks/Blockers| |-------| ---------|--------|---------| |Feb '24| Green| Work has been completed and merged and will be released on 3/12| N/A |Sep '23| Green| Team is currently exploring opportunities to solve problems identified. Problem C: Dev complete remove non used status codes Non-verified & Active: Suspended App. Planned release store release 10/10/23| N/A |Oct '23| Green | Finalizing design recommendations based on feedback received on sort/filter and number of RXs. This will be reviewed by Kay and Coulton with intent that design proposal is done early November then Kay and Coluton can share it with Dr. Spahn. After passing it off, Mobile will be on a holding until we get feedback / decision from Dr. Spahn | |Nov '23| Green | Mobile shared clickable Figma prototype of our design recommendation to Kay and Coulton |

Detailed Project Scope

• Product Brief
• Decision Log
• RX Filter/Sort Prototype

Definition of Done

Following needs to be true

Epic is currently in exploratory phase and making recommendation.

Supporting Team

Name	Role
Rachel Han	Product Owner, VA
Ryan Thurlwell	Design Lead, VA
Alayna	Sr. Product Manager, Ad Hoc
Lauren Russell	Sr. UX Designer, Ad Hoc
Misty Milliron-Grant	Sr. Content Designer, Ad Hoc
Kay Lawyer	Octo VA PO

Checklist

Toggle Product Checklist

**Project Kickoff & Requirements Gathering** - [ ] Project Kickoff session - [ ] Initiative Scope finalized - [ ] Link Product Brief - [Sprint 0 ](https://docs.google.com/document/d/1WHDJ1iCt9J-acLx8_DSL4tkRKoVYqJGaRUqXuFf7ceg/edit# ) - [ ] Link to Implementation Strategy - Implementation Plan - UAT Plan - Release Plan - Metrics Identified (what metrics are we capturing, how do they tie into stakeholder OKRs, etc) **Pre-Production Readiness** - [ ] Associate Readiness - [ ] Update product guide - [ ] Coordinate with contact center support teams - [ ] What’s New Content - [ ] App Store/In App messaging (if applicable) - [ ] Coordinate with Release coordinator - [ ] App store Content changes required? Y/N - [ ] App store images needed? Y/N - [ ] QA Signed off - [ ] UAT complete - [ ] Obtain Go/No Go decision **Feature Go Live** - [ ] Ensure Waygate/Feature toggle release ticket submitted w/engineering & QA - **Template: Turn on Waygate/Turn off feature flag** - [ ] Coordinate with content & release coordinator if what’s new in app is required

Toggle Team Collaboration Checklist

- [ ] Design Intent & Feasibility discussions - [X] Research needed? No - [ ] UAT Needed? Yes/No - [ ] Ticket creation - [ ] Demo feature (mid check, end of development)

Toggle Design/UX Checklist

- [ ] Review problem/opportunity statement - [ ] Add questions and assumptions to product brief - [ ] Add research links to product brief - [ ] Document high-level research/design plans - [ ] Create lo/hi fi wireframes & user flows if applicable - [ ] Add links to Epic & applicable GitHub folders - [ ] Socialize designs - [ ] Sign off received - [ ] Complete Design QA - [ ] Does it require component review? - [ ] Accessibility review needed?

Toggle Content Checklist

- [ ] Review product brief and surface any questions, assumptions & risks - [ ] Participate in project discovery and kickoff activities/ceremonies - [ ] Complete comparative analysis/content research activities for net-new content - [ ] Review current content and determine where app may need to differ and potential improvements to share with web - [ ] Review past VA research and decisions documentation - [ ] Support Research & UX Design in research sessions and synthesis - [ ] Make content recommendations for lo-/hi-fi wireframes in collaboration with UX Design - [ ] Collaborate with Sitewide Content team for alignment, improvements, and sign-off - [ ] Participate in FE hand off - [ ] Complete content QA - [ ] Write copy for What's New In App - [ ] Write copy for app stores' What's New sections. - [ ] Write copy for updated screenshots in app stores

Toggle Engineering Checklist

- [ ] Are UI designs/ specs available/ready? If yes, they should be attached to attach specs. (We are assuming the design specs have been approved) - [ ] Are there any deadlines that need to be met? - [ ] What is the roll out plan? (Do we need a feature toggle? is this going to be available to every user immediately or do we want to roll out to a few users first) - [ ] Does this project require api integration? if yes, what api endpoint are we integrating with and what is the expected response body? - [ ] Do we want to capture analytics for this projects (i.e. update GA, add logs to grafana/datadog etc)?If yes, what metrics would we like to capture?

Toggle QA Checklist

- [ ] Create test plan - **Template: QA Test Plan** - [ ] Identify test data needs - [ ] Gotten & incorporated test plan review - [ ] QA Complete - [ ] Waygate tasks complete - [ ] Added new feature cases to the RC in TestRail - [ ] Added feature cases to appropriate section of active cases in TestRail - [ ] Spun up a (future) UI automation ticket for new feature

[kfink24]

Approved by OCTO Rx Product and Design Leads. Improvements look great and approved on our side. Changes were shared with Dr. Spahn back in November and we noted his feedback and documented how we will proceed in prioritizing if we get large amounts of veteran feedback.