Cerner FHIR R4 Coverage Resource is not appearing in the scope list

[Francisco Gaytan]

Hello,

I have completed an integration with our application using DSTU2 resources. We are interested in getting coverage data, so I created an additional application targeting R4. When I created the new R4 application I made user I requested access to user/Coverage.read, but when I receive the access token I am not seeing Coverage.read in the list of scopes. I made sure that I am requesting it during the authentication flow, but it is not coming across after a successful authentication. Is granting this scope something that has to be done manually from your end?

Thank you.

[Benjamin Eichhorn (Cerner)]

Hi Francisco,

Could you provide us with a correlation ID for your authorization request?

Thanks,

Ben (Cerner)

[Benjamin Eichhorn (Cerner)]

Hi Francisco,

I had to delete your post as per our group guidelines do not post authorization tokens. The correlation ID is located within the headers of the response. It should be the "X-Request-Id" or "Cerner-Correlation-Id" header.

Thanks,

Ben (Cerner)

[Edwin Perez]

Hello Benjamin

I'm working with Francisco in this issue, I found this Correlation-ID: 

Cerner-Correlation-ID:

29705085-c29f-4cb3-94c2-13acacf10cbd

Let me know if you need more information.

thanks

[Francisco Gaytan]

Hi Benjamin,

I just wanted to follow up on this. Edwin went ahead an posted the correlation-id. Any updates?

--
You received this message because you are subscribed to a topic in the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/cerner-fhir-developers/sGFkMyjMXvA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to cerner-fhir-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/918b88ca-3719-4d1e-ae1a-0f4f7b619318%40googlegroups.com.

[Matt Randall (Cerner)]

Francisco,

Can you post the URL being generated by your client for your authorization grant request?  We're not seeing the actual request contain that scope.  Trying to determine the source of the disparity, here.

Regards,

- Matt Randall

[Francisco Gaytan]

Hi Matt,

Here is some of the data I collected from a single launch:

launch: 9ddea245-eeb3-4d2a-822d-84a27443565d

url user to request the authorization code:

https://authorization.sandboxcerner.com/tenants/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/protocols/oauth2/profiles/smart-v1/personas/provider/authorize?client_id=f599a003-eb80-446c-ae83-ad45de72b198&response_type=code&redirect_uri=https://localhost:8051/sso/cerner&scope=launch%20openid%20profile%20user%2FPractitioner.read%20user%2FPatient.read%20user%2FEncounter.read%20user%2FCoverage.read&launch=9ddea245-eeb3-4d2a-822d-84a27443565d&contract_id=4&state=1430d06f-fe12-4f16-888c-d65491ff4ba2&aud=https%3A%2F%2Ffhir-ehr.sandboxcerner.com%2Fr4%2F0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca

url used to request the access_token: https://authorization.sandboxcerner.com/tenants/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/protocols/oauth2/profiles/smart-v1/token

[Jenni Syed (Cerner)]

Hi,

It looks like you may be authorizing with the older DSTU 2 client application (which won't have access to Coverage) that was created instead of the newer R4 client application - can you check your client id in the authorization request and compare it to the the client id shown in the code portal on the registration page for the app built for r4? It will need to be updated in the code doing the authorization request.

Regards,

Jenni

[Francisco Gaytan]

Hi Jenni,

That was the issue. I have two applications in the sandbox one is targetting DSTU2 and the other R4. I forgot to change the client id when testing with the R4 application.

Thanks a lot.