Overview
The Flows360 Epic connector provides robust, bidirectional integration by leveraging the HL7 FHIR (Fast Healthcare Interoperability Resources) R4 standard. This allows for secure, programmatic access to your Epic Electronic Health Record (EHR) system, enabling seamless data exchange with other applications.
Key Capabilities
- Patient Data Management: Synchronize patient demographics for a consistent, up-to-date view across all connected systems.
- Clinical Workflow Automation: Automate critical processes including patient intake, appointment scheduling, and referral management.
- Clinical Data Exchange: Access clinical summaries, lab results (via DiagnosticReport resources), and medication orders (via ServiceRequest resources) to support analytics, research, or patient engagement platforms.
- Unified Patient View: Build a comprehensive, 360-degree view of patient information by integrating clinical data with operational and financial systems.
Capability summary
Authentication
Auth method: OAuth 2.0
Required scopes
patient/Patient.read
patient/Patient.write
Encounter.read
Encounter.write
ServiceRequest.write
DiagnosticReport.read
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Patient | Yes | Yes | Represents patient demographic and administrative data (FHIR Patient resource). |
| Encounter | Yes | Yes | Represents a patient's visit or interaction with a healthcare provider (FHIR Encounter resource). |
| Order | Yes | Yes | Represents a request for a service or procedure (FHIR ServiceRequest resource). |
| Result | Yes | No | Represents the findings of a diagnostic service (FHIR DiagnosticReport resource). Read-only. |
Supported actions
| Action | Description |
|---|---|
| Get Patient Admissions | Retrieves a list of patient encounters, typically filtered by admission or visit status. |
| Create New Order | Creates a new clinical order (FHIR ServiceRequest) for a specified patient. |
| Update Patient Demographics | Updates demographic or administrative information for an existing patient record. |
| New Patient Encounter | Creates a new encounter record for a patient visit, admission, or other interaction. |
Setup steps
Prerequisites
- Administrator access to your Epic on FHIR instance.
- An active account on the Epic developer portal (open.epic).
1. Register a New Application in Epic
- Log in to the Epic on FHIR developer portal.
- Navigate to the application registration section and create a new application.
- During setup, specify the required FHIR resource scopes (e.g.,
Patient.read,Encounter.write). - Configure the Redirect URI to the Flows360 callback URL:
https://platform.flows360.app/oauth/callback. - Save the application and securely record the Client ID and Private Key.
2. Configure the Connection in Flows360
- In the Flows360 platform, navigate to Connections and click Add Connection.
- Select Epic.
- Enter the Client ID and Private Key obtained from the Epic developer portal.
- Provide your organization's Epic FHIR Base URL.
- Click Connect. You will be redirected to your Epic instance to authorize the connection.
- Log in and grant the requested permissions to complete the setup.
Limitations
- This connector interacts exclusively through the Epic FHIR R4 API. Access to data is strictly limited by the specific FHIR resources implemented and permissions configured by your organization's Epic instance.
- API requests are subject to rate limits imposed by Epic's infrastructure.
- Custom fields or proprietary Epic modules not exposed via the standard FHIR API are not accessible through this connector.
- The connector's functionality depends on the successful completion and maintenance of the OAuth 2.0 authorization flow. Any token expiration or revocation will disrupt integration.
Troubleshooting
I am receiving a 401 Unauthorized or 403 Forbidden error.
A 401 or 403 error indicates a problem with authentication or authorization. nnSteps to resolve:n1. Verify that the Client ID and Private Key are correctly entered in the Flows360 connection settings.n2. Confirm that the required scopes were requested when the application was registered in Epic.n3. The OAuth tokens may have expired or been revoked. Re-authorize the connection from the Flows360 connection settings page to generate a new set of tokens.
My workflow is failing with an error about missing data or an inability to find a resource.
This occurs when the user account that authorized the connection does not have sufficient permissions within Epic to access the requested data, or the required FHIR scopes were not granted.nnSteps to resolve:n1. Check the permissions of the authorizing user account within Epic's administrative settings.n2. Ensure that all required scopes (e.g., Patient.read, Encounter.read) are enabled for the connected application in the Epic developer portal.