Integrations / Cerner
Cerner
Cerner is an electronic health records (EHR) system providing healthcare IT solutions
OAuth 2.0
Indexes
Actions
What Telara does
Capability matrix
Before you connect
Prerequisites
A Cerner (Oracle Health) FHIR tenant your organization has provisioned.
An administrator who can register a SMART app or issue client credentials for that tenant.
Vendor setup
Get the credential
1
Open the Cerner code console
In the Oracle Health / Cerner code portal, open your tenant’s SMART application registration.
2
Register Telara’s client
Create (or reuse) the confidential client Telara’s Connect form describes. Note the tenant id, FHIR base URL, client id, and client secret. Grant the permissions this page lists from the catalog — do not invent extra clinical scopes.
3
Paste in Telara
Settings → Integrations → Cerner. Enter tenant, base URL, client id, and secret. Patient-context vs user-context is whatever the catalog lists for this connector.
Permissions Telara requests
- patient/Patient.readOAuth 2.0
- patient/Observation.readOAuth 2.0
- patient/Encounter.readOAuth 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
- 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
- Tenant Id
- 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
Sandbox and production FHIR endpoints are different tenants. A sandbox client id will not open production charts.
This connector only reads what the registered client is allowed. Missing encounters are usually a scope or patient-compartment issue on the Cerner side.