Patient Journey as seen by the Browser

From IDESG Wiki
Jump to navigation Jump to search

Full Title

How the Patient journey is seen by the user agent (browser) on a user device.

Context

Patient journey, writing a proposal to present to BlinkDev, browser render engine people.

Journey

  1. User navigates to Relying Party Web site, for this journey a patient viewing a patient portal. The patient portal may receive a cookie from a prior visit
  2. RP displays one or more sign in options for the user (note that the patient view may be determined by the existence of a valid cookie)
  3. The user clicks on one sign in option . A his point there is a fork in the journey based on the cookie.

Fork one: User is apparently new as there is no existing cookie

  1. Legacy journey would have the user sign into the portal using a local user name and password. That would be and and to the user journey.

Fork two the user device is recognized by the appearance of a cookie

References

Retrieved from "https://wiki.idesg.org/index.php?title=Patient_Journey_as_seen_by_the_Browser&oldid=15851"