Organizer View from PowerChart

[Quang Nguyen]

Hi,
We are building a provider facing Smart app and have been able to launch our app successfully with patient chart view in PowerChart. 
We are also given a new launch point within PowerChart to launch Organization view. Do we need to make any change in the scopes from patient scopes to be user scopes? We're currently experience access_denied error.

Below are our current scopes:

App Type: provider

FHIR Spec: r4 - "https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d"

Authorized: true

Standard Scopes: launch, profile, openid, online_access

Patient Scopes: 

• patient/AllergyIntolerance.read
• patient/Condition.read
• patient/Device.read
• patient/DocumentReference.read
• patient/Encounter.read
• patient/Observation.read
• patient/Patient.read
• patient/Procedure.read
• patient/DocumentReference.write

Thanks,
Quang

[Aaron McGinn (Cerner)]

Per our group guidelines, can you please provide the X-Request-Id of the error you are receiving? This is in the response headers.

In general, if you are accessing a resource that is specific to a single patient, you should use the 'patient/<Resource>' scope. If you are doing a search across patients, you should be using the 'user/<Resource>' scope.

-Aaron (Cerner)

[Quang Nguyen]

Hi Aaron,
Appreciate your response. Do you have a suggestion on how to collect X-Request-Id from the app in PowerChart?  Is there a way we can test Organizer view from the sandbox environment?  It would be easier to collect response headers there. 
Here is our Client and App Id if it helps.

Client Id: 9fea3154-6e4a-4448-ad40-92d5f20ed8e5

App Id: b0e29c28-53e2-40fd-83f4-9d4518339951

We are using fhir-client.js library on our app. Bellow is the error trying to initiate the call  FHIR.oauth2.ready()  

{

"description": "access_denied",

"stack": "Error: access_denied\n 

at _callee2$ (https://cdn.jsdelivr.net/npm/fhirclient/build/fhir-client.js:13841:13)\n

at tryCatch (https://cdn.jsdelivr.net/npm/fhirclient/build/fhir-client.js:429:7)\n

at invoke (https://cdn.jsdelivr.net/npm/fhirclient/build/fhir-client.js:659:9)\n

at Anonymous function (https://cdn.jsdelivr.net/npm/fhirclient/build/fhir-client.js:484:9)\n

at asyncGeneratorStep (https://cdn.jsdelivr.net/npm/fhirclient/build/fhir-client.js:99:5)\n

at _next (https://cdn.jsdelivr.net/npm/fhirclient/build/fhir-client.js:121:9)\n

at Anonymous function (https://cdn.jsdelivr.net/npm/fhirclient/build/fhir-client.js:128:7)\n

at N (https://pocedocdev.z13.web.core.windows.net/js/chunk-vendors.a83d92ef.js:500:66739)\n

at Anonymous function (https://cdn.jsdelivr.net/npm/fhirclient/build/fhir-client.js:117:5)\n

at _completeAuth (https://cdn.jsdelivr.net/npm/fhirclient/build/fhir-client.js:14023:3)"

}

For Organizer view workflow, we don't need to access any Fhir resources. We only need SSO feature for users to launch our app from PowerChart. All the requirements to read/write Fhir resources are on the Patient Chart View workflow, which we don't have any issue with.
We are having trouble finding documentation regarding Organizer view. Wonder what minimum scopes would need for our app to just use SSO feature.

Thank you!

Quang

[Aaron McGinn (Cerner)]

The Organizer view is tested as an app with no patient context, but the Cerner client experience will have to be tested through an instance of PowerChart. As a program member, we will work with you on that. It looks like the launch is already set up for your user. If you have questions about your testing or login, you can post to your uCern group so we can get it worked out!

-Aaron (Cerner)