Integrations / Epic
Epic
Epic is an electronic health records (EHR) system used by healthcare organizations
OAuth 2.0
Indexes
Actions
What Telara does
Capability matrix
Before you connect
Prerequisites
An Epic on FHIR (or customer-hosted Epic) environment your organization has provisioned.
An administrator who can register a SMART on FHIR app for that environment.
Vendor setup
Get the credential
1
Open the Epic app registration
In open.epic.com (or your health system’s app orchard), open the FHIR app registration for this environment.
2
Register the client
Create a confidential client. Note client id, secret, FHIR base URL, and tenant. Grant the permissions this page lists from the catalog.
3
Paste in Telara
Settings → Integrations → Epic. Enter the base URL, client id, secret, and tenant Telara asks for.
Permissions Telara requests
- patient/Patient.readOAuth 2.0
- patient/Patient.writeOAuth 2.0
- patient/Observation.readOAuth 2.0
- patient/Observation.writeOAuth 2.0
- patient/Encounter.readOAuth 2.0
- patient/Encounter.writeOAuth 2.0
- patient/MedicationRequest.readOAuth 2.0
- patient/AllergyIntolerance.readOAuth 2.0
- patient/Procedure.readOAuth 2.0
- patient/Condition.readOAuth 2.0
- patient/Appointment.readOAuth 2.0
- patient/Appointment.writeOAuth 2.0
- user/Patient.readOAuth 2.0
- user/Practitioner.readOAuth 2.0
- user/Organization.readOAuth 2.0
In Telara
Connect in Telara
OAuth 2.0
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
Fields Telara asks for
- Base Url
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Encounter metadata | Partial — not every record the vendor holds is synced |
| Problem list | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Encounter metadata | Up to 1 day | Removed records disappear on the next full sync |
| Problem list | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.
Excluded from semantic search: Encounter metadata, Problem list.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty
Known limitations
Non-prod and production Epic environments are different registrations. A non-prod client id will not open production charts.
Patient-compartment rules on the Epic side hide resources even when Connect succeeds.