- Getting started
- Notifications
- Licensing
- Troubleshooting
- Coding agents
- Connector Builder
- Act! 365
- ActiveCampaign
- Active Directory - Preview
- Adobe Acrobat Sign
- Adobe PDF Services
- Amazon Bedrock
- Amazon Connect
- Amazon Polly
- Amazon SES
- Amazon Transcribe
- Amazon Web Services
- Anthropic Claude
- Asana
- AWeber
- Azure AI Document Intelligence
- Azure Defender for Cloud
- Azure Maps
- BambooHR
- Box
- Brevo
- Calendly
- Campaign Monitor
- Cisco Webex Teams
- Citrix Hypervisor
- Citrix ShareFile
- Clearbit
- Confluence Cloud
- Constant Contact
- Coupa
- CrewAI – Preview
- Customer.io
- Database Hub
- Databricks Agent
- Datadog
- DeepSeek
- Deputy
- Discord - Preview
- DocuSign
- Drip
- Dropbox
- Dropbox Business
- Egnyte
- Epic FHIR - Preview
- About the Epic FHIR connector
- Epic FHIR authentication
- Eventbrite
- Exchangerates
- Exchange Server - Preview
- Expensify
- Facebook
- Freshbooks
- Freshdesk
- Freshsales
- Freshservice
- GetResponse
- GitHub
- Gmail
- Google Cloud Platform
- Google Docs
- Google Drive
- Google Forms - Preview
- Google Maps
- Google Sheets
- Google Speech-to-Text
- Google Text-to-Speech
- Google Tasks - Preview
- Google Vertex
- Google Vision
- Google Workspace
- GoToWebinar
- Greenhouse
- Hootsuite
- HTTP
- HTTP Webhook
- Hubspot CRM
- HubSpot Marketing
- HyperV - Preview
- Icertis
- iContact
- Insightly CRM
- Intercom
- Jina.ai
- Jira
- Keap
- Klaviyo
- LinkedIn
- Mail
- Mailchimp
- Mailgun
- Mailjet
- MailerLite
- Marketo
- MCP
- Microsoft 365
- Microsoft Azure
- Microsoft Azure Active Directory
- Microsoft Azure AI Foundry
- Microsoft Azure OpenAI
- Microsoft Azure Sentinel
- Microsoft Dynamics 365 CRM
- Microsoft OneDrive & Sharepoint
- Microsoft Outlook 365
- Microsoft Power Automate – Preview
- Microsoft Sentiment
- Microsoft Sentinel Threat Intelligence
- Microsoft Teams
- Microsoft Translator
- Microsoft Vision
- Miro
- NetIQ eDirectory
- Nvidia NIM
- Okta
- OpenAI
- OpenAI V1 Compliant LLM
- Oracle Eloqua
- Oracle NetSuite
- PagerDuty
- PayPal
- PDFMonkey
- Perplexity
- Pinecone
- Pipedrive
- QuickBooksOnline
- Quip
- Salesforce
- Salesforce Agentforce & Flows
- Salesforce Marketing Cloud
- SAP BAPI
- SAP Cloud for Customer
- SAP Concur
- SAP OData
- SendGrid
- ServiceNow
- Shopify
- Slack
- SmartRecruiters
- Smartsheet
- Snowflake
- Snowflake Cortex
- Stripe
- Sugar Enterprise
- Sugar Professional
- Sugar Sell
- Sugar Serve
- System Center - Preview
- TangoCard
- Todoist
- Trello
- Twilio
- UiPath Apps - Preview
- UiPath Data Fabric
- UiPath Test Manager
- UiPath GenAI Activities
- UiPath Orchestrator
- X (formerly Twitter)
- Xero
- watsonx.ai
- WhatsApp Business
- WooCommerce
- Workable
- Workday
- Workday REST
- VMware ESXi vSphere
- YouTube
- Zendesk
- Zoho Campaigns
- Zoho Desk
- Zoho Mail
- Zoom
- ZoomInfo
About the Epic FHIR connector
Integration Service connector for the Epic FHIR API in Automation Cloud, providing read access to clinical, administrative, and financial data from an Epic instance.
The Epic FHIR connector lets your organization read clinical, administrative and financial data from your own Epic instance through Epic's Fast Healthcare Interoperability Resources (FHIR) R4 APIs, and use that data in UiPath automations.
The connector authenticates as a SMART on FHIR Backend Services client, using OAuth 2.0 client credentials with an RS384-signed JSON Web Token (JWT) assertion. There is no user login and no browser step, so automations can run unattended.
This guide is written for health systems connecting UiPath Integration Service to their own Epic environment. It covers:
- What your Epic team needs to do in Epic.
- Which values you need to collect from them.
- How to configure the connection in Integration Service.
Your Epic technical contact carries out the environment-side parts of the setup. How the activities behave once you start building automations is covered in the Epic FHIR activities documentation.
Authentication
Setting up a connection involves both your Epic team and your UiPath organization administrator. A connection authenticates as one of UiPath's two registered Epic apps, Production or Non-Production, rather than one your organization registers itself. The following four stages happen in order, and the first two take the longest because they depend on your Epic release schedule.
- Your Epic team downloads the UiPath app.
- Your Epic team registers your public key and confirms API access.
- You collect the Epic instance URLs.
- You create the connection in Integration Service.
Step-by-step instructions, the Client IDs, and how to find the Epic instance URLs are on the Epic FHIR authentication page.
Events
The Epic FHIR connector does not support events. There is no polling or webhook mechanism to react to changes in your Epic instance, and all activities run on demand. For general information about how events and triggers work in Integration Service, refer to the Triggers page.
Activity package
You can use the connection to enable the Epic FHIR activities in UiPath® Studio and build automations that read data from your Epic instance. Two generic activities, Get Record and List Records, work against 26 FHIR resources, and Patient adds Patient.$match and Patient.$summary.
Provider documentation
Epic's constraints vary by release and by organization. Epic's own documentation and your own Epic build are the authoritative sources, rather than a copy.
| Link | Why it matters |
|---|---|
| App Creation & Request Process | How an Epic community member requests and downloads a registered app. See the Requesting An App and Downloading Client Records sections. |
| Epic Showroom | Epic's marketplace, where the connector is listed. |
| API specifications and sandbox | The index of every API Epic publishes, by resource and FHIR version. This is the authoritative answer to whether a filter is supported for a given resource. |
| Backend Services OAuth 2.0 guide | The authentication flow this connector uses, including the token endpoint and the JWT assertion. |
| Search Parameters | How Epic handles search parameters in general, including formats, prefixes and which parameters are honored. |
| ID Types for APIs | Epic's identifier types, and the warning that identifier systems differ between customers. |
| Endpoint directory | Where to find your organization's FHIR base URL. |
| Patient Searching and Matching | Epic's guidance on choosing between search and match. |
| Patient.Search (Demographics) (R4) | Search parameters and the minimum data set. |
| Patient.$match (R4) | The match operation and its outcome codes. |
| Patient.$summary (IPS) (R4) | The International Patient Summary returned for one patient, including the standard IPS section set. |