Patient Journey as seen by the Browser: Difference between revisions

From IDESG Wiki
Jump to navigation Jump to search
Line 7: Line 7:
# User navigates to Relying Party Web site, for example to a patient view a  patient portal, the patient portal may receive a cookie from a prior visit
# User navigates to Relying Party Web site, for example to a patient view a  patient portal, the patient portal may receive a cookie from a prior visit
# 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)
# 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)
# The user clicks on one sign in option at his point there is a fork in the journey based on the cookie.
# 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
Fork one: User is apparently new as there is no existing cookie

Revision as of 15:44, 31 March 2021

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 example to a patient view 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

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

References