Do you mean pulling data offline, like when the patient/provider is not actually present at a website? You’ll need at some point in the process to obtain an auth token to make FHIR requests --- this can be done by the provider or patient using a flow similar to the one in that tutorial. If you request “offline” access you’ll also get a “refresh token” that will enable to you to obtain new tokens without user interaction once the original one expires. One caveat --- I don’t know the status of Epic giving long-lived tokens these days, you may find that you’ll have to interrupt the user every once in awhile to re-obtain auth, which is a big pain. But with that token, you can just make FHIR requests as usual. There is no FHIR-based trigger to let you know when new data is available, so you’ll have to implement polling of some type.
There is a separate backend auth flow (https://build.fhir.org/ig/HL7/smart-app-launch/backend-services.html) --- but I don’t know what the support levels are for this in Epic, or how challenging it is to set up --- just haven’t done it.
Hope that at least gets you started! ---S
--
You received this message because you are subscribed to a topic in the Google Groups "SMART on FHIR" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/smart-on-fhir/q_Nn5tyX_1k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
smart-on-fhi...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/smart-on-fhir/97d8f28e-2c1b-4ad4-a60d-8e76bb5c57e4n%40googlegroups.com.