wesrowe
commented
9 months ago refinement notes:
- left as both dev & ux for now, may need to split
- do we need to log anything to datadog? probably not
- size: small
Closed radavis closed 6 months ago
wesrowe
commented
9 months ago refinement notes:
jzucadi
commented
7 months ago
User story
As a Cartographers team member, I want to make sure that users with a facility registration but no MHV account have no unnecessary API calls that would result in console errors, to reduce noise and make errors that actually impact user experience easier to notice.
As a user with a facility registration but no MHV account, I would like if possible to not have a confusing experience if I click a tool link on the MHV landing page, so that I'm not confused.
Notes
Details of UX (not part of this ticket)
- Both are for a subtle use case I don't think we've really looked at: a user who: (1) has a medical record at a facility; and (2) does not have an MHV account. Today we are showing them the full landing page with tool links. However, if/when they click through to an MHV National Portal tool, they will be asked to register for an MHV account – that UX where they are dropped without explanation into a very long form. - The potentially-confusing experience (getting sent to the MHV account creation form without explanation) is a temporary situation. Once the account creation API is launched, MHV accounts will be created in the background before the user has a confusing experience. ETA on that: Spring 2024. - We still need to figure out if these 403 errors will persist beyond the launch of the account-creation API (in mid-2024) - Consider the case for Oracle-only users – should there be a different experience for them? - Sara/IA rec: don't ever link Oracle-only users to MHV NPPossible tasks:
Acceptance Criteria