eCarePlanner 3.2.0 - not all "OHSU - POC" Goals are showing

[mattStorer]

Loaded MyCarePlanner 2.4.1 for "Andrew Fhir" OHSU POC patient, and loaded Epic third party endpoint data for "fhirderrick" sandbox user.

Goals brought in. There are 6 goals from "OHSU - POC" and 2 goals from "Test Data: Epic sandbox".

Shared data to SDS. I can see in the SDS these goals are represented:

However, when loading eCarePlanner for Andrew Fhir, we only see one "OHSU - POC" Goal. Both Goals from "Test Data: Epic sandbox" are represented:

Where are these other 5 "OHSU - POC" Goals?

[mattStorer]

these are the Goal queries executed by eCarePlanner :

It looks like it's only pulling Goals from the SDS for the Local Patient resource (those Goals created by the user through MyCarePlanner), and those for the "fhirderrick" user, from fhir.epic.com. So that explains why the 6 Goals aren't coming through for the OHSU POC user from the SDS, they're not being queried.

Those OHSU - POC Goals are being queried against epicmobile.ohsu.edu, though. But what's weird is that those calls are only bringing back one Goal -

Which is the 130/80 BP goal that is being displayed.

I see in MyCarePlanner, the Goal query being executed is this:

Whereas in eCarePlanner, it's this:

I've just examined the bodies of the responses, and it seems that MyCarePlanner is including Inpatient Care Plan Goals, as each of the missing Goals in eCarePlanner are those. The Blood Pressure Goal is the only one having a different Category.

See attached for the Goals returned by MyCarePlanner:
MyCarePlanner Goals from OHSU POC.json

And those returned by eCarePlanner:
eCarePlanner Goals from OHSU POC.json

Anyone have any idea why these would be different?

[xmlmodeling]

Matt, I would look at your Epic app configurations for MyCarePlanner vs eCarePlanner. These are different app configs, right? The resources returned (or not returned) by a query are determined by the read & search privileges. My guess is you've select in-patient Goals for MyCarePlanner, but not selected these for eCarePlanner. Dave

…

On Thu, Sep 26, 2024 at 3:21 PM Matt Storer ***@***.***> wrote: these are the Goal queries executed by eCarePlanner : image.png (view on web) <https://github.com/user-attachments/assets/b8258a4b-5e3d-43dc-8b72-f20290d41b96> It looks like it's only pulling Goals from the SDS for the Local Patient resource (those Goals created by the user through MyCarePlanner), and those for the "fhirderrick" user, from *fhir.epic.com <http://fhir.epic.com>*. So that explains why the 6 Goals aren't coming through for the OHSU POC user from the SDS, they're not being queried. Those OHSU - POC Goals are being queried against *epicmobile.ohsu.edu <http://epicmobile.ohsu.edu>*, though. But what's weird is that those calls are only bringing back one Goal - image.png (view on web) <https://github.com/user-attachments/assets/39d35c91-e143-4bcf-b622-6aaf336278c8> Which is the 130/80 BP goal that is being displayed. I see in MyCarePlanner, the *Goal* query being executed is this: image.png (view on web) <https://github.com/user-attachments/assets/d2a99f34-5089-4a4c-84d3-9cd0783ab097> Whereas in eCarePlanner, it's this: image.png (view on web) <https://github.com/user-attachments/assets/9604d271-59ee-49ad-912e-49966daa0a29> I've just examined the bodies of the responses, and it seems that MyCarePlanner is including Inpatient Care Plan Goals, as each of the missing Goals in eCarePlanner are those. The Blood Pressure Goal is the only one having a different Category. See attached for the Goals returned by MyCarePlanner: MyCarePlanner Goals from OHSU POC.json <https://github.com/user-attachments/files/17156147/MyCarePlanner.Goals.from.OHSU.POC.json> And those returned by eCarePlanner: eCarePlanner Goals from OHSU POC.json <https://github.com/user-attachments/files/17156153/eCarePlanner.Goals.from.OHSU.POC.json> Anyone have any idea why these would be different? — Reply to this email directly, view it on GitHub <#477 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPT6NZISL42XP53TIUGSH3ZYR3EBAVCNFSM6AAAAABO52RC62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXHE2TSNZUG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mattStorer]

@xmlmodeling ah that could be it. good thought! will check and get back.