Unable to launch standalone as provider

[michaelgriffithus]

I am building a standalone application that will be an external provider launch. I am able to launch the application using the following launch scope:

online_access openid profile offline_access launch/patient user/*.* patient/*.*

I am routed to the EPIC login, but it appears that the only users you have provisioned are patients.

I would expect that I could launch the EHR as a provider, get an authentication token and then be able to produce a list of patients that I am authorized to see Patient/*

It appears that you provide the following user id and password to test patient launch: Username: fhirjason Password: epicepic1

Is there an equivalent for an external provider launch? Please advise?

[radamson]

Hi @michaelgriffithus sorry for not getting back to you sooner.

It sounds like you're trying to test against the Epic sandbox based on the documentation provided in the wiki. We do not control that sandbox and do not provision the data or users on it.

If you take a look on the open.epic.com documentation (Step 2 specifically) for the server it does look like there is another user fhirjessica that you could try, but it looks like that user is still a patient.

There are a few other patient contexts listed on the epic launchpad, but I think you might have to reach out to Epics support to get what you need.

We'd love to hear back if you make any headway on this! Let me know if you have any other issues or if we can provide further clarification.