UiPath Documentation
activities
latest
false
Integration Service activities

Filters and search parameters

Filters available on Epic FHIR List activities, why a supported parameter can still return nothing, and the STU3 parameters with no R4 effect.

Every search parameter Epic declares for a resource in R4 is available as a filter on that resource's List activity. An empty result does not always mean there is no data, because Epic declares more search parameters than any individual organization honors.

A parameter can return zero results and no error for any of these reasons:

  • Epic marks it unsupported for that resource, so it is accepted and then ignored.
  • It is valid only in combination with another parameter.
  • Your organization's Epic build disables or restricts it.

When a search returns nothing and you expected results, the filter is the first thing to check, before concluding the data is missing.

Note:

Epic's specification for a specific resource at fhir.epic.com is the authoritative answer to whether a parameter is supported. Your Epic team can confirm how your build is configured.

Date parameters use FHIR prefixes such as ge2024-01-01, le2024-12-31, gt, lt and eq. See Epic's Search Parameters documentation for details.

Parameters with no effect in R4​

Four parameters appear on R4 connections but apply only to STU3 and have no effect:

ResourceParameterR4 equivalent
DocumentReferenceclass, createdNone
DocumentReferenceindexeddate
Immunizationnotgivenstatus
  • Parameters with no effect in R4​

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated