MHV account creation API error messages

[laurwill]

Your team

• Product name: MHV Account Creation API, FE user alerts in My HealtheVet on VA.gov
• Team name: Cartography Team
• OCTO product owner: Robyn Singleton
• Product manager: Wes Rowe
• Designer(s): Sara Sterkenburg, Florence McCafferty

• Slack channel: mhv-on-va-gov-cartography-team

  Description:

This is a cross-team initiative. The MHV Portals + Access team (OCC) is creating an Account Creation API that is being implemented by Identity team (Joe Niquette, Trevor Boshaw) on VA.gov to eliminate the need for users who interact with My HealtheVet for the first time to manually register on the MHV Classic website.

However, if this API fails or encounters any issues, we need to surface alerts to users on the FE in multiple locations that help them understand those issues & give them steps to a resolution.

Content help needed

1. Content edits/approval for the alert / MHV landing page design we've drafted in Figma here
2. Alert content plan for side-door alerts in the apps themselves. Since users may not come to My HealtheVet through the landing page, we also need to make sure these alerts live on the affected applications (tools the user cannot access without an MHV UUID): Medications, Medical records, and Secure Messages.
   • I am going to draw up options and socialize those with the POs of those teams, but would love your opinion re:
   • do we want to generically say everywhere that "you can't access these 3 tools until you call the helpdesk"; or
   • specify the specific tool they're on? e.g. "You can't access medications because there is an issue connecting your account. Please call the helpdesk"

Pros of using one alert: easier to manage - Cartography team can build this and offer it to other teams as a shared component that they insert in their code.

Cons: potentially more confusing for user? Would love your opinion.

3. I think we will need to also ask VAHB to implement these alerts, but since they do not support MR on the app, you may need to work with that team and have them modify the alert content. Their architecture is also different, so may need to pull in Holly Collier to speak to where these need to live.

Images

Extremely draft concept that will probably change:

Error codes we need to include in alert body (will probably conditionally reveal?)

Resources

• Mural
• Figma file

Timeline

• as of 10/30/2024 we are still working with the other teams to get the data locked down & there could be some churn. Let's regroup when you're back from PTO, second week of November?

[laurwill]

@sterkenburgsara I made a stub, want to fill in whatever info here and I'll take a pass when you say it's ready?

[sterkenburgsara]

@laurwill thank you! updated, I'll poke you about this when you're back from PTO.