search

chronic-care / mcc-project

MCC eCare Plan project planning and documentation
Apache License 2.0
0 stars 1 forks source link

Caching issue with MyCarePlanner #405

Open MichelleBobo opened 1 month ago

MichelleBobo commented 1 month ago

There is an issue with trying to access MyCarePlanner with external data multiple times in sequence. If you come back to it after a previous login, the app either fails with an error message, or it defaults to the login for the external site before it even properly loads the home page. On the user end, the issue can be fixed by clearing the browser cache, but that's not something that we want to be trying to talk our patients through. Is there a way to configure this so that it loads properly from scratch, every time?

kbertodatti commented 1 month ago

  1. Need to be clear on what is the expected behavior when you close it and reload within an hour of the first login. Document from user perspective.

  2. Need to spend some time to reproduce. @drdavec to take first stab.

mattStorer commented 1 month ago

I confirm this is a problem, I have experienced this myself. Steps to reproduce:

  1. log into MyCarePlanner via OHSU MyChart
  2. connect to a third-party provider (e.g., Providence Oregon/Washington)
  3. DO NOT COMPLETE THE AUTHENTICATION PROCESS! Instead, repeat steps 1 and 2.
  4. as soon as MyCarePlanner begins to load, control will redirect to the third-party provider's authentication endpoint selected in step 2.
  5. The only way to resolve this is to wipe your browser's cache and data, OR to complete the third-party provider's authentication handshake. Doing this will permit MyCarePlanner to load, with both OHSU's data and data from the third-party provider.

Completing the third-party endpoint authentication is the easiest workaround, if it can be done. However, if a user selects the wrong third-party endpoint, or for some reason cannot complete the third-party endpoint authentication, they will be stuck until they clear their browser's cache and data.

MyCarePlanner needs to wipe cached credentials on startup.

kbertodatti commented 4 weeks ago

EMI to try logging in different EHRs using invalid password to see if the loop happens. @drdavec @savanahmueller @kbertodatti

Document all failed paths.