UiPath Documentation
activities
latest
false
Integration Service activities

Known limitations

Scope boundaries of the Epic FHIR activities, covering write operations, FHIR version support, scheduling, bulk export, and complex field binding.

The following limitations apply to the Epic FHIR activities. For limitations that apply to the connection itself, see Epic FHIR authentication.

  • Write activities are only available through HTTP Request. Create, Update and Delete are not exposed as activities, although the Client Id carries the write scopes.
  • R4 only. This is a deliberate scope decision. Patient/$match is declared only in R4, seven of the resources modelled here do not exist in STU3, and R4 returns relative reference URLs where earlier versions return absolute ones, so reference fields would not bind consistently across versions.
  • No open-slot search or booking. Epic publishes Schedule, Slot, Appointment.$find and Appointment.$book for STU3 only. In R4 the only scheduling resource is Appointment, supporting read and search, which this connector provides.
  • No bulk export. Group/$export is not modelled. It is the appropriate tool for whole-population extracts, and polling this connector for a large cohort is not a suitable substitute.
  • Complex FHIR fields do not bind. Fields typed as standard FHIR datatypes appear as a single untyped object with no child fields. This affects Reference, CodeableConcept, Coding, Identifier, Quantity and Period. Epic's specifications describe these by datatype without expanding their contents, so the data is present in the response but must be read from the activity's raw JSON output until the schemas expand these types.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated