Great write-up @Tani Frankel !
We see FHIR lists used across clinical datasets, workflows, devices and can be applied to anything else in a health system. Good timing on this article as we have some additional samples available on github modelling current remote devices and current allergies for a set of patients:
Follow Link to Github.
Hi @Dmitrii Baranov, for M2M flows, I don't think the openid scope has any meaning. Openid should only be granted to human end users authenticating and receiving ID tokens at the identity layer.
The IRIS for Health FHIR Server does not require openid scopes for this reason and system access is based only on OAuth access tokens and SMART scopes (system/*.read, etc.). You might need to verify whether your 3rd-party server can support M2M since OIDC is defined on authorization code, implicit, and hybrid grant types.
@Hassan Mirza , 4101 is a response code used by Epic to mean "no results found", the Patient.$match API spec and codes can be found here: https://fhir.epic.com/Specifications?api=10423
If you think this is being returned incorrectly, definitely reach out to Epic directly for support!