User flow diagram for integration

[wesrowe]

Description

User story

As a Cartography team member, I want to document the UX flow of the integrated portal, so that teams have a single source of truth for the intended experience.

Notes

• Design portal-wide sitemap that communicates current state and the impending future state (point of integration)
• Create user flow w/ branching logic and routing info annotations where possible
• Surface jobs to be done
• Show concerns for Vista v. Cerner/OH users
• Come up with QA use cases
  • VistA only user
  • Hybrid user
  • Cerner/OH only user
  • Unauth user
  • Mobile user
  • AT user
  • User who is shadow banned from some tools
• Run by Wes, Mikki and Kaitlin
• Determine how to get tool teams aligned around flow – possibly a meeting like Bryan organized for downtime alerts?

Possible tasks:

• Create high-level sitemap diagram
• Create user flow diagram for various test scenarios (above) that illustrates jobs to be done for tool teams

Acceptance criteria

• [x] Current + future state sitemaps documented
• [x] User flows documented - updated Phased UX Mural
• [x] Iterated with feedback from Wes, Kaitlin
• [x] Determined a way (meeting?) to circulate to tool teams

[sterkenburgsara]

Sitemap schematic in MURAL here

[sterkenburgsara]

Per Kaitlin:

• We may not need a diagram, but just a clear to-do list for health tool teams (via Slack is okay) where POs are cc'ed for visibility. From there, Kaitlin & POs will ensure that jobs to be done for integration are ticketed during PI planning

Does that sound right, @wesrowe? Do you still want this missing artifact that creates user flows for the test user cases that can inform QA?

[wesrowe]

I think this is a compelling document, but I'll let @allanto-ah answer whether it meets his needs for identifying test cases. I feel we don't need to QA every link within tools ourselves, that should fall to tool teams. But we have a strong point of view on how some flows work. Maybe we could talk in 16th minute one day about what a reasonable heuristic is for determining if Cartographers QA a particular bit of functionality.

[sterkenburgsara]

Other task (capturing User flows) I completed by updating the existing Phased UX diagram to reflect the integration. See that here.