How to get Encounter Participants if not passed in the Encounter resource?

[Odalys Jordan]

Our SMART App receives the Encounter ID from the launch context. 

We need to retrieve the participants for this Encounter, but the Participants list is not always passed in the Encounter resource. In this case, is there any other way of retrieving the Participants related to the Encounter?

Thanks!

[Jenni Syed (Cerner)]

Hi Odalys,

You could try to query the CarePlan resource by encounter (looking for care team: http://fhir.cerner.com/millennium/dstu2/care-provision/care-plan/#care-teams). The "context" parameter is where you would provide encounter.

Regards,

Jenni 

[Odalys Jordan]

Thank you! I will try that.

[Odalys Jordan]

Hi,

I tried querying CarePlan resource. I added parameters patient(ID) and context(encounter ID), and I only got results from category: assess-plan

Then I added the category parameter equals careteam, and I got a 403 Forbidden. "Forbidden resource". Does this mean the data resulted this parameters combination is not accessible?

Thank you,

Odalys

On Tuesday, February 20, 2018 at 12:23:57 PM UTC-5, Jenni Syed (Cerner) wrote:

[Odalys Jordan]

Any answer on this please?

[Madhur Rajendran (Cerner)]

Hi Odalys,

Would you be able to provide a correlation id? Also can you double check that your authorization includes the CareTeam.read scope?

Thanks,

Madhur

[Joshua Fisk (Cerner)]

Hi Jordan,

Sorry for the lack of response! Currently to use the careteam category in sandbox you will have to provide a CareTeam scope in addition to the CarePlan scope that you are already providing. This was a defect in our handling of the scopes and there is a change that will pushed out to sandbox soon that will correct this.

Thank you,

Josh Fisk

On Friday, July 13, 2018 at 3:45:08 PM UTC-5, Odalys Jordan wrote:

[Odalys Jordan]

Hi!

Yes, the App is authorized for the scope patient/CarePlan.read

What do you call "correlation" ID ?

[Odalys Jordan]

Hi Josh,

Thank you for your response. To summarize, I need to wait until that change is pushed to test the request for CareTeam, since there's no "CareTeam" available to be selected in the Patient Scopes. Correct?

Thank you!

[Madhur Rajendran (Cerner)]

Hi Odalys,

Sorry for the confusion there. You will have to wait to test the CareTeam request, unfortunately. I'll check back with the team and give an update tomorrow.

In response to your other question, the correlation Id is the 'X-Request-Id' header that we return with the response.

Thanks,

Madhur

[Madhur Rajendran (Cerner)]

Hi Odalys,

We did relate this back to a known issue. We have engaged with the team that owns the concept, and will provide further updates early next week.

Thanks,

Madhur

[Odalys Jordan]

Hi!

Any updates on this issue? 

Thank you.

[Joshua Fisk (Cerner)]

Hi Odalys,

Due to some delays with the team responsible for the care team concept this was unfortunately side tracked. They are currently close to a fix for this issue and we will make sure to update you once this is ready :)

Thanks,

Josh

[Odalys Jordan]

Hi Josh,

Thank you for the update. I will appreciate that you let me know once the fix is published. 

Thanks again!

Odalys

[Denis Mulder]

Same issue with not being able to read CareTeam (Participants) from CarePlan with "Forbidden" error. Any updates?

[Joshua Fisk (Cerner)]

I was able to get in touch with the team responsible for care team today. They are looking to release their update to the care team service soon. I can't comment on our specific roadmap but once that is available we will be able to adjust our server and will post an update here for you.

[Joshua Fisk (Cerner)]

Good news! The fix for this issue is now live in our sandbox. If you experience any further errors attempting to call CareTeam (CarePlan with Participants) please let us know :)

Thank you for being patient while we worked through this.

- Josh

[Odalys Jordan]

Thanks for the update. I'll give it a try and let you know the results.

Thank you!

[Odalys Jordan]

I tried the API call but no luck so far. I'm still getting error 403, but now with the message "insufficient_scope". See the details below:

REQUEST HEADERS: 

GET /dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/CarePlan?patient=4342012&context=4027930&category=careteam HTTP/1.1

User-Agent: GuzzleHttp/6.3.3 curl/7.38.0 PHP/7.2.4

Host: fhir-ehr.sandboxcerner.com

Authorization: Bearer SENSITIVE-DATA-REMOVED

Accept: application/json+fhir 

REQUEST BODY: 

 

RESPONSE CODE: 403 

RESPONSE HEADERS: 

HTTP/1.1 403 Forbidden

Date: Fri, 18 Jan 2019 15:59:16 GMT

Cache-Control: no-cache

Vary: Origin,User-Agent,Accept-Encoding

Server-Response-Time: 22.453745

WWW-Authenticate: Bearer realm="fhir-ehr.sandboxcerner.com", error="insufficient_scope"

X-Request-Id: 7472c67f8970f4d6dde08fce7a53b01f

Status: 403 Forbidden

Content-Length: 0

Content-Type: text/html 

RESPONSE BODY:

 

Let me know if I'm missing something.

Thanks!

[Joshua Fisk (Cerner)]

Thanks for providing the request id. I took a look at the token you used and there is no CarePlan scope included in it so that is why you are seeing the errors now. You will have to add back the CarePlan scope that you were originally using.

[Odalys Jordan]

Yep, I was missing the fact that I have removed the patient/CarePlan.read scope from the App weeks ago. I'll update that and try again. 

Thanks

[Odalys Jordan]

I was able to get results for the request specified. Question, is this working in the Cerner Production environment? 

[Joshua Fisk (Cerner)]

Great! This should be deployed to our Production environments this next Tuesday, the 22nd.

[Odalys Jordan]

Awesome! 

Thank you all for all your hard work and support!