search

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

Patient Check-in #4315

Open kellylein opened 1 year ago

kellylein commented 1 year ago

Project Status Overview

Project Objective:

Provide veterans the ability to check in the day of for a VA In Person appt using the VA Health & Benefits Mobile app

Product Outline

Dependencies / Blockers

Blockers |Blocker | Team / Owner | Est to Resolution | |-------|---------|-------| | Test Patient account for staging needed. Details [here](https://github.com/orgs/department-of-veterans-affairs/projects/984/views/1?pane=issue&itemId=33330662) | Appointments team (Kay Lawyer assisting)| TBD

Project Timeline

Milestones Step | Timing | |-------| ---------| |Sprint 0 - Discovery | Complete | |Step 1 - Strategy | Complete | |Step 2 - Design | Complete | |Step 3 - Building / Implementing | On Hold | | 100% Release | | |Step 4 - Post Verification| |

Monthly Update

|Month| Project Health|Progress & Key Accomplishments| Issues/Risks/Blockers |-------| ---------|--------|---------| |July '23| At Risk| Mobile & Check in team working closely to finalize check in api design/intent |Mobile has dependency on Check in team's finalized API designs, 2 data fields (IEN & check in flag) to be exposed by Appt's team, and staging test user availability configuration needed by Appts team| |Aug '23| At Risk| BE engineering started work to integrate with check in APIs. | Open dependencies remain| |Sept '23| At Risk| Development on hold| Tracking dependencies|

Detailed Project Scope

Veteran's have the ability to use their VA Health & Benefits app to check-in for a VA In person appt

User Story:

As a veteran, with internet connectivity, who has a scheduled in person appt at a VA facility that offers echeck-in I want to have the ability to check in for my appt using my own mobile phone via the Health & Benefits mobile app.

MVP Scope

Check-in w/pre-registration tasks

The scope of this initiatives provides veterans the ability to check in the day of for a VA In Person appt. The workflow may include 3 demographic Y/N questions if the Veteran has not reviewed within the last 7 days

Is this your current contact info correct? Is this your current next of kin info Is this your emergency contact?

If a Veteran answers No to any of the above questions they are not able to check in via the app and advised to see front desk

If a Veteran answers Yes to all the questions then they can be checked in and should be provided confirmation that they are checked in

This workflow would display a Check in button only (placement tbd) when the veteran is within the check in window (45 min prior to appt or 15 min after appt time) and meets the following criteria

Not in Scope

Assumption/Risks

Risks

Assumptions

OKR and Analytic Metrics

Metrics
What we are measuring Why Event Name

Definition of Done

Project Links

Supporting Team

- **OCTO Product Leads:** Rachel Han and Ryan Thurlwell - **PM:** Rachel Han - **Ad Hoc PM:** Meko Hong - **Engineering:** Jayson Perkins and Jon Bindbeutel - **Design:** Lauren Russell

Checklist

Toggle Product Checklist **Project Kickoff & Requirements Gathering** - [X] Project Kickoff session - [ ] Initiative Scope finalized - [X] 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
Hallm13 commented 1 year ago

Need deeper understanding of technical lift. This is maybe more of a medium effort. Could be form heavy. Focus on lighter lift V1 of this. Looking for use cases that require fewer questions. Step 1 should determine if pre-check and travel should be separate projects.

bischoffa commented 1 year ago

Per PO request during 7/11 SoS the release estimate has been updated to match the SoS doc - it could only be added in the 100% release as there is no other option. Date pulled from Q3 planning. Date to be updated if it moves / changes.

bischoffa commented 11 months ago

2 Blocker removed - 1 remaining
Add Check in e-flag to appts service. Details [here](https://github.com/orgs/department-of-veterans-affairs/projects/984/views/1?pane=issue&itemId=33311547)  
Surface IEN data field to appts service. Details [here](https://github.com/orgs/department-of-veterans-affairs/projects/984/views/1?pane=issue&itemId=33311621)

Hallm13 commented 10 months ago

Excluding from Q1 24' plan until blocker is removed.