Integrate Epic EHR with any application
Flows360 provides a robust integration platform to connect your Epic Electronic Health Record (EHR) system with any other application in your technology stack. Move beyond data silos by synchronizing patient demographics, appointments, clinical summaries, billing information, and more. Automate patient intake processes, streamline referral management, and connect clinical data with research, analytics, or patient engagement platforms. Our Epic connector allows you to build custom, bidirectional workflows that reduce manual data entry, minimize errors, and provide a unified view of patient information across your organization. Securely and reliably extend the capabilities of your Epic system to enhance interoperability and support modern healthcare delivery.
Common use cases
- Automated Patient Intake: Sync patient registration data from online forms or patient portals directly into Epic.
- Referral Management Automation: Connect Epic with other providers or CRMs to streamline the patient referral process.
- Clinical Data Warehousing: Aggregate Epic data with other clinical and operational data sources for advanced analytics and reporting.
- Telehealth Platform Integration: Synchronize appointment and patient data between Epic and third-party telehealth solutions.
Sync scenarios
- Patient demographics
- Appointments and scheduling
- Clinical documents (CCDAs)
- Billing and insurance data
- Lab results and orders
- Medication information
Objects supported
- Patients
- Encounters
- Orders
- Results
- Practitioners
- Appointments
- Observations
- Medication Requests
- Conditions
- Allergies
- Diagnostic Reports
- Document References
Actions
- get_patient_admissions
- create_new_order
- update_patient_demographics
- new_patient_encounter
- create_appointment
- upload_document_reference
- post_vital_signs
- record_allergy_intolerance
- add_condition
- new_lab_result
- appointment_scheduled
- patient_discharged
- medication_prescribed
Frequently asked questions
What kind of data can I sync with the Epic integration?
You can sync a wide range of data, including patient demographics, appointments, clinical documents like CCDAs, billing information, lab results, orders, and medications.
How does integrating Epic improve clinical workflows?
By connecting Epic to other systems, you can automate manual processes like patient registration and referral management. This reduces data entry errors, saves clinician time, and ensures data is consistent across all platforms.
Can I build two-way integrations with Epic?
Yes, our platform supports bidirectional data flows. You can both pull data from Epic to use in other applications and push data from external systems into Epic, enabling real-time, two-way synchronization.
- Auth method: OAuth 2.0
- Required scopes: 6
- Supported objects: 4
- Supported actions: 4
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.
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
1. Log in to the Epic on FHIR developer portal.
2. Navigate to the application registration section and create a new application.
3. During setup, specify the required FHIR resource scopes (e.g., `Patient.read`, `Encounter.write`).
4. Configure the Redirect URI to the Flows360 callback URL: `https://platform.flows360.app/oauth/callback`.
5. Save the application and securely record the Client ID and Private Key.
2. Configure the Connection in Flows360
1. In the Flows360 platform, navigate to Connections and click Add Connection.
2. Select Epic.
3. Enter the Client ID and Private Key obtained from the Epic developer portal.
4. Provide your organization's Epic FHIR Base URL.
5. Click Connect. You will be redirected to your Epic instance to authorize the connection.
6. Log in and grant the requested permissions to complete the setup.
Required scopes
patient/Patient.readpatient/Patient.writeEncounter.readEncounter.writeServiceRequest.writeDiagnosticReport.read
Supported objects
- Patient
- Encounter
- Order
- Result
Supported actions
- 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.
Use cases
- Customer 360
- Data Warehousing
- Finance & Billing
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.