Epic systems

Epic systems + Konnectify

Epic systems Integration with Konnectify

Connect Epic systems with Konnectify to automate interoperable workflows across clinics and health systems—sync patients, appointments, encounters, observations, and document references with your downstream tools.

Appointments Document References Encounters Observations Patients 10 Triggers 10 Actions

ON THIS PAGE

→ What is Epic systems? → API & Authentication → How to connect → Triggers (10) → Actions (10) → Popular automations → FAQ

What is Epic systems?

Epic is a leading electronic health record (EHR) platform used by hospitals, clinics, and health systems worldwide. Through Epic’s FHIR interfaces, you can securely exchange clinical and administrative data such as patients, appointments, encounters, observations, and clinical documents.

Integrating Epic systems with Konnectify helps you orchestrate workflows across your care operations—keeping connected systems in sync, automating notifications, and improving data flow between Epic and your downstream applications.

New to Epic systems?

Review Epic’s developer resources and FHIR documentation to get your OAuth client and test environment ready.

Visit Epic on FHIR →

New to Konnectify?

Konnectify is an iPaaS that lets you build, test, and run secure automations between Epic and your other tools.

Create a Konnectify account →

What you can automate

• Sync new patient records into downstream systems

• Route updated patient demographics to connected apps

• Monitor appointment creation for reminders and scheduling workflows

• React to appointment changes (reschedules/cancellations)

• Track encounters and trigger post-visit workflows

• Capture observations and new documents for analytics or archival

API & Authentication

Authentication: OAuth 2.0 authorization

Konnectify connects to Epic using OAuth 2.0. During authorization, you’ll be redirected to Epic to approve access; Konnectify stores only the encrypted access credentials needed to run your workflows and never stores your Epic password.

API capabilities in this connector:

Read and detect changes for Patients, Appointments, Encounters, Observations, and Document References (via polling triggers).
Create and find core FHIR resources: Patient, Appointment, Encounter, Observation, and DocumentReference.
Support for incremental sync using cursor-based polling where available.

Important: rate limits & environment constraints

Epic environments may enforce rate limits, app approval requirements, and scope restrictions (especially in sandbox vs. production). If you see authorization errors or inconsistent reads, verify your Epic app registration, allowed redirect URIs, and granted scopes.

Before you start
When creating your app to get the Client ID and Client Secret, you'll be asked to add a Redirect URI. Make sure to add the URI below:
https://app.us.konnectifyapp.co/ipaas/api/oauth/callback

Official documentation: Epic on FHIR Documentation

How to connect Epic systems to Konnectify

Prerequisites

An Epic OAuth 2.0 client (Client ID and Client Secret) provisioned for your environment.
Access to Epic’s FHIR endpoint(s) and approval to use required FHIR resources.
A Konnectify workspace with permission to create Connections and Workflows.

Add Epic systems to a Workflow

Create a new Workflow in Konnectify.
Select Epic systems as your trigger app or action app.

Authorize via OAuth 2.0

Click Connect to create a new Epic systems Connection.
Enter your Client ID and Client Secret when prompted.
Complete the OAuth consent/authorization flow in Epic.

Configure the Trigger or Action

Choose the exact trigger (e.g., Patient created) or action (e.g., Create appointment).
Map fields from previous steps into your Epic systems step.
Set any required identifiers (e.g., patient IDs) consistently across steps.

Warning

Healthcare integrations often require strict identifier and scope alignment. If a create/find step fails, confirm that your Epic app is approved for the target FHIR resource type and that you’re using the correct environment endpoint.

Test the Workflow

Run a test to verify authentication and field mappings.
For polling triggers, ensure there is new/updated data in Epic to detect.

Activate the Workflow

Turn the Workflow on.
Monitor initial runs and adjust polling intervals and mappings as needed.

Triggers 10

This connector provides 10 triggers. All triggers are polling-based—Konnectify periodically checks Epic systems for new or updated records and triggers your workflow when changes are detected.

Appointments 2 triggers

Appointment created

Polls appointments and triggers for each new appointment detected.

Appointment updated

Polls appointments and triggers when appointment is updated.

Document References 2 triggers

Document reference created

Polls document references and triggers for each new document reference detected.

Document reference updated

Polls document references and triggers when document reference is updated.

Encounters 2 triggers

Encounter created

Polls encounter and triggers for each new encounter detected.

Encounter updated

Polls encounter and triggers when an encounter is updated.

Observations 2 triggers

Observation created

Polls observation and triggers for each new observation detected.

Observation updated

Polls observation and triggers for when an observation is updated.

Patients 2 triggers

Patient created

Polls patient and triggers for each new patient detected.

Patient updated

Polls patient and triggers when a patient is updated.

Actions 10

Use actions to create and look up key Epic systems FHIR resources from your workflows.

Appointments 2 actions

Create appointment

Creates a new appointment in Epic System

Find appointment

Finds an appointment in Epic System

Document References 2 actions

Create document reference

Creates a document reference in Epic System

Find document reference

Finds a document reference in Epic System

Encounters 2 actions

Create encounter

Creates a encounter in Epic System

Find encounter

Finds a encounter in Epic System

Observations 2 actions

Create observation

Creates an observation in Epic System

Find observation

Finds an observation in Epic System

Patients 2 actions

Create patient

Creates a patient in Epic System

Find patient

Finds a patient in Epic System

Popular automations

Examples of real-world Epic systems workflows you can build with Konnectify using the available triggers and actions.

Create follow-up appointment records after new scheduling events

When a new appointment is created, look it up to confirm identifiers and downstream mappings before continuing the workflow.

Appointment created → Find appointment

Create a patient record when a new patient appears in your feed

Use new patient detection to drive downstream onboarding, then write back or mirror the record as needed.

Patient created → Create patient

Validate encounter details when an encounter is updated

Trigger on encounter updates and fetch the encounter to ensure you have the latest version before routing to analytics or care ops.

Encounter updated → Find encounter

Track clinical documents and resolve to a specific document reference

When a document reference is created, immediately locate it via a find step to capture identifiers for storage, indexing, or audit workflows.

Document reference created → Find document reference

FAQ

How does authentication work for Epic systems in Konnectify?

Epic systems uses OAuth 2.0. You authenticate by providing your Client ID and Client Secret and completing Epic’s authorization flow. Konnectify does not store your Epic password.

Which Epic environments or plans are supported?

Support depends on your Epic configuration and whether your organization has enabled the relevant FHIR APIs and granted the necessary scopes for your registered app. Many teams start in Epic’s sandbox and then move to a production tenant after approval.

Are triggers real-time or polling?

All triggers in this connector are polling triggers. Konnectify checks Epic systems at an interval and triggers when it finds new or updated resources (for example, a newly created appointment).

How do I prevent duplicates?

This connector does not expose an explicit “upsert” action. To avoid duplicates, use a Find action first (e.g., Find patient / Find appointment) and then conditionally run the corresponding Create action only when a match is not found.

How does Konnectify handle rate limits and retries?

If Epic returns throttling or transient errors, Konnectify may retry requests based on platform safeguards. For high-volume use cases, reduce polling frequency, add filtering where possible, and prefer “updated” triggers only when needed.

Can I connect multiple Epic tenants or accounts?

Yes. Create a separate Konnectify Connection for each Epic environment/tenant (for example, sandbox vs. production) and select the appropriate connection in each workflow step.

Do I need special permissions for healthcare data (PHI/PII)?

Often, yes. Access to FHIR resources in Epic can be gated by organizational policy, app review, scopes, and user context. Ensure your organization’s compliance requirements are met (including PHI handling), and validate that your Epic app is approved for the required resource types such as Patient and DocumentReference.

Ready to automate your Epic systems workflows?

Connect Epic systems to Konnectify and start building reliable patient, scheduling, and clinical data automations.

Get started free →