Stream: Touchstone
Topic: open.epic.com Patient resource errors in WildFHIR
Abbie Watson (Apr 11 2017 at 20:49):
Hi!
So, at the Chicago MiniConnectathon #VBConFHIR, we were trying to connect to open.epic.com, with the following URL (which worked!).
curl "https://open-ic.epic.com/FHIR/api/FHIR/DSTU2/Patient/Tbt3KuCY0B5PSrJvCu2j-PlK.aiHsu2xUjUM8bWpetXoB"
The documentation says that it should have returned a JSON object, but we received an XML content, and when we tried to validate with WildFHIR, we got an error when creating a new record. Any thoughts?
https://open.epic.com/Clinical/FHIR?whereTo=patient
Richard Ettema (Apr 11 2017 at 20:55):
@Abigail Watson I just retrieved that Patient resource using the Epic url (above). Yes, I can see why WildFHIR would reject it. The problem is that the extensions (as well as a number of other elements) are not in the correct position in the Patient structure for the XML format. The JSON format is more forgiving.
Richard Ettema (Apr 11 2017 at 21:08):
Another issue I see is that this Patient appears to be a DSTU2 version. The <careProvider> element is now <generalPractitioner> in STU3.
Richard Ettema (Apr 11 2017 at 21:08):
You can also see that the <careProvider> reference points to the Epic DSTU2 base url.
Abbie Watson (Apr 11 2017 at 21:18):
Oooh, thank you Richard! That totally helps! Added the xml2js library, and we have it dropping to the database, relaying to the client, and displaying in our UI! We just got Read access to the Epic FHIR server!!!
Richard Ettema (Apr 11 2017 at 21:31):
FYI - I cleaned up that Patient resource and successfully created in WildFHIR for FHIR Release 3. You can read it here:
http://wildfhir.aegis.net/fhir3-0-0/Patient/Tbt3KuCY0B5PSrJvCu2j-PlK.aiHsu2xUjUM8bWpetXoB
Note: The <generalPractitioner> reference was modified to remove the Epic reference so it doesn't point to a valid Practitioner right now.
Richard Ettema (Apr 11 2017 at 21:32):
I'm dropping offline now. Hope your day has been fun.
Last updated: Apr 12 2022 at 19:14 UTC
