Solutions for Epic FHIR activity errors, including empty results, withheld access, and the status codes Epic returns.

The following causes are listed from most to least frequent:

When the app is not authorized for a resource in your environment, Epic responds with HTTP 200, an empty result, and a warning embedded in the response body. To an automation, this is indistinguishable from a patient who has no records of that type.

The connector detects this case and fails the activity with a 403 that names the cause, instead of returning an empty list. To resolve it:

For failures that occur while creating the connection rather than while running activities, see Connection failures.