Error message - OAuth2 error {org name} patient. Invalid-request. {'error". "invalid_request","error_description", null }
Translation - VisuWell is getting an OAuth error from Epic. Customer should check "interconnect" and see the reason for the error on their side. Something is probably configured wrong in Epic separate from VisuWell.
-------
-------
Error Message - Epic is not authorized to authenticate account {visuwell ID}
Translation - something is wrong with the user they are trying to join the video visit as. the number in that error is the VisuWell patient ID, so you can look them up in VisuWell and see their account and user type. This issue is probably happening because there is already a user with the same email address in Visuwell. You'll have to change that person's email address for this other user to be able to get in. This is okay because we don't send the email notifications and Epic will still authenticate the user who's email we changed, since they use a special ID to connect the account from Epic to Visuwell.
This issue will be fixed when we switch from email as the unique identifier to username.
-------
Error Message - Patient launch failed with missing redirect path.
That means something is going wrong when we're trying to read patient info from the Epic API. It's supposed to supply the redirect URL (back to their API, for authentication) but it's not. So the problem is in Epic; Epic didn't give Visuwell a redirect path.
-------
Issue - Video visit icon doesn't turn green in Hyperspace when patient joins the visit
Translation - This usually means we're getting a 400 for setconnectionstatus and the customer or Epic needs to look on their end to find why. This may be an issue with rewrite rules in Epic, so you can suggest they look at that.
Comments
0 comments
Please sign in to leave a comment.