Oracle Cerner

Oracle Cerner + Konnectify

Oracle Cerner Integration with Konnectify

Securely connect Oracle Cerner EHR to Konnectify using SMART on FHIR protocols to automate healthcare workflows across clinical, scheduling, financial, document, and patient data.

Patients Appointments Clinical Records Medications Documents Organizations 31 Triggers 81 Actions

ON THIS PAGE

→ What is Oracle Cerner? → API & authentication → How to connect → Triggers (31) → Actions (81) → Popular automations → FAQ

What is Oracle Cerner?

Oracle Cerner is an electronic health record (EHR) platform used by healthcare organizations to manage patient, clinical, scheduling, care coordination, and operational data. This Konnectify integration connects to Oracle Cerner through SMART on FHIR so teams can build secure automations around FHIR resources without writing custom integration code.

Use it to sync patient updates, retrieve clinical resources, power downstream analytics, coordinate care workflows, or connect Oracle Cerner data with other business and healthcare systems in your stack.

New to Oracle Cerner?

Explore Oracle Health solutions and SMART on FHIR capabilities for connected healthcare data.

Visit Oracle Health →

New to Konnectify?

Create connected workflows across healthcare, business, and operational apps with no-code automation.

What you can automate

• Monitor new and updated patient records

• Retrieve appointment, slot, and schedule data

• Fetch observations, conditions, procedures, and reports

• Access medications, immunizations, and nutrition orders

• Retrieve documents, Binary resources, CCDs, and media

• Sync organizations, practitioners, related persons, and care teams

API & Authentication

OAuth 2.0 authorization with SMART on FHIR

Oracle Cerner uses OAuth 2.0 through SMART on FHIR. When you connect the app, Konnectify redirects you to Oracle Cerner authorization, where an authorized provider or administrator grants access. Konnectify stores authorization tokens securely and does not store your Oracle Cerner user password.

Required connection fields include Client ID, Client Secret, Tenant ID, and Hostname.

Based on the configured SMART scopes and available resources, this connector supports read access across major FHIR modules, including:

Patient, Person, Practitioner, RelatedPerson, Organization, and CareTeam resources
Appointment, Schedule, Slot, Encounter, Location, and ServiceRequest resources
AllergyIntolerance, Condition, Observation, Procedure, DiagnosticReport, Specimen, and FamilyMemberHistory resources
MedicationRequest, MedicationAdministration, MedicationDispense, Immunization, NutritionOrder, and Goal resources
DocumentReference, Binary, Media, Questionnaire, QuestionnaireResponse, Provenance, StructureDefinition, and OperationDefinition resources
Account, ChargeItem, Coverage, InsurancePlan, Consent, Device, and Communication resources

Important: Available resources, scopes, patient context, launch context, rate limits, and write permissions can vary by Oracle Cerner tenant, SMART app registration, organization policy, and FHIR endpoint configuration.

Official API documentation: Oracle Cerner FHIR documentation.

How to Connect Oracle Cerner to Konnectify

Prerequisites

An active Konnectify account.
An Oracle Cerner SMART app registration with Client ID and Client Secret.
Your Oracle Cerner Tenant ID and Hostname.
Required FHIR scopes approved for the resources you want to access.
Authorization from a user or administrator permitted to connect the EHR tenant.

Add Oracle Cerner to a Workflow

Open Konnectify and create or edit a workflow.
Choose Oracle Cerner as the trigger or action app.

Authorize via OAuth 2.0

Enter your Client ID, Client Secret, Tenant ID, and Hostname.
Click authorize and approve the SMART on FHIR permission request in Oracle Cerner.

Configure the Trigger or Action

Select the FHIR resource operation, such as Patient Created or Updated, Get Observation, or List DocumentReference.
Map IDs, patient references, encounter references, date ranges, and search parameters as needed.

Tip: FHIR search parameter availability can vary by resource and tenant. Test each operation with a known patient, encounter, or resource ID.

Test the Workflow

Run a test to confirm Konnectify can retrieve the expected FHIR bundle or resource.
Review returned fields and map them to downstream apps.

Activate the Workflow

Turn on the workflow when testing is complete.
Monitor workflow runs and error logs for authorization, scope, or rate-limit issues.

Triggers 31

Oracle Cerner includes 31 polling triggers. These triggers periodically check the FHIR API for new or recently updated resources.

Clinical Records7 triggers

New or Updated AllergyIntolerance

Polls the FHIR API for new or recently updated AllergyIntolerance records.

Condition Created or Updated

Polls the FHIR API for new or recently updated Condition records.

FamilyMemberHistory Created or Updated

Polls the FHIR API for new or recently updated FamilyMemberHistory records.

Observation Created or Updated

Polls the FHIR API for new or recently updated Observation records.

Procedure Created or Updated

Polls the FHIR API for new or recently updated Procedure records.

Specimen Created or Updated

Polls the FHIR API for new or recently updated Specimen records.

DiagnosticReport Created or Updated

Polls the FHIR API for new or recently updated DiagnosticReport records.

Scheduling & Locations4 triggers

Appointment Created or Updated

Polls the FHIR API for new or recently updated Appointment records.

Location Created or Updated

Polls the FHIR API for new or recently updated Location records.

Slot Created or Updated

Polls the FHIR API for new or recently updated Slot records.

Schedule Created or Updated

Polls the FHIR API for new or recently updated Schedule records.

Care Management5 triggers

CarePlan Created or Updated

Polls the FHIR API for new or recently updated CarePlan records.

Communication Created or Updated

Polls the FHIR API for new or recently updated Communication records.

Consent Created or Updated

Polls the FHIR API for new or recently updated Consent records.

Goal Created or Updated

Polls the FHIR API for new or recently updated Goal records.

ServiceRequest Created or Updated

Polls the FHIR API for new or recently updated ServiceRequest records.

Financial & Coverage2 triggers

ChargeItem Created or Updated

Polls the FHIR API for new or recently updated ChargeItem records.

Coverage Created or Updated

Polls the FHIR API for new or recently updated Coverage records.

Devices & Documents2 triggers

Device Created or Updated

Polls the FHIR API for new or recently updated Device records.

DocumentReference Created or Updated

Polls the FHIR API for new or recently updated DocumentReference records.

Medications & Nutrition5 triggers

Immunization Created or Updated

Polls the FHIR API for new or recently updated Immunization records.

MedicationAdministration Created or Updated

Polls the FHIR API for new or recently updated MedicationAdministration records.

MedicationDispense Created or Updated

Polls the FHIR API for new or recently updated MedicationDispense records.

MedicationRequest Created or Updated

Polls the FHIR API for new or recently updated MedicationRequest records.

NutritionOrder Created or Updated

Polls the FHIR API for new or recently updated NutritionOrder records.

Organizations & People6 triggers

Encounter Created or Updated

Polls the FHIR API for new or recently updated Encounter records.

Caregiver Organization Created or Updated

Polls the FHIR API for new or recently updated Organization (caregiver) records.

Organization Created or Updated

Polls the FHIR API for new or recently updated Organization records.

Patient Created or Updated

Polls the FHIR API for new or recently updated Patient records.

Practitioner Created or Updated

Polls the FHIR API for new or recently updated Practitioner records.

RelatedPerson Created or Updated

Polls the FHIR API for new or recently updated RelatedPerson records.

Actions 81

Use actions to retrieve individual FHIR resources or search for bundles of records from Oracle Cerner.

Administrative & Financial8 actions

List Account

Fetch a bundle of Account resources based on search parameters.

Get Account

Fetch a specific Account resource by its unique ID.

List ChargeItem

Fetch a bundle of ChargeItem resources based on search parameters.

Get ChargeItem

Fetch a specific ChargeItem resource by its unique ID.

List Coverage

Fetch a bundle of Coverage (insurance) resources based on search parameters.

Get Coverage

Fetch a specific Coverage (insurance) resource by its unique ID.

List InsurancePlan

Fetch a bundle of InsurancePlan resources based on search parameters.

Get InsurancePlan

Fetch a specific InsurancePlan resource by its unique ID.

Allergies & Clinical Conditions8 actions

List AllergyIntolerance

Fetch a bundle of AllergyIntolerance resources based on search parameters.

Get AllergyIntolerance

Fetch a specific AllergyIntolerance resource by its unique ID.

List Condition

Fetch a bundle of Condition resources based on search parameters.

Get Condition

Fetch a specific Condition resource by its unique ID.

List FamilyMemberHistory

Fetch a bundle of FamilyMemberHistory resources based on search parameters.

Get FamilyMemberHistory

Fetch a specific FamilyMemberHistory resource by its unique ID.

List Goal

Fetch a bundle of Goal resources based on search parameters.

Get Goal

Fetch a specific Goal resource by its unique ID.

Scheduling & Locations8 actions

List Appointment

Fetch a bundle of Appointment resources based on search parameters.

Get Appointment

Fetch a specific Appointment resource by its unique ID.

List Location

Fetch a bundle of Location resources based on search parameters.

Get Location

Fetch a specific Location resource by its unique ID.

List Schedule

Fetch a bundle of Schedule resources based on search parameters.

Get Schedule

Fetch a specific Schedule resource by its unique ID.

List Slot

Fetch a bundle of Slot resources based on search parameters.

Get Slot

Fetch a specific Slot resource by its unique ID.

Documents, Binary, Devices & Media8 actions

Get Binary CCD

Fetch a Continuity of Care Document (CCD) in Binary format based on patient and encounter parameters.

Get Binary

Fetch a specific Binary resource document by its unique ID.

List Device

Fetch a bundle of Device resources based on search parameters.

Get Device

Fetch a specific Device resource by its unique ID.

List DocumentReference

Fetch a bundle of DocumentReference resources based on search parameters.

List DocumentReference with $docref

Fetch a bundle of DocumentReference resources using the specialized Cerner $docref operation.

Get DocumentReference

Fetch a specific DocumentReference resource by its unique ID.

Get Media

Fetch a specific Media resource by its unique ID.

Care Coordination10 actions

List CarePlan

Fetch a bundle of CarePlan resources based on search parameters.

Get CarePlan

Fetch a specific CarePlan resource by its unique ID.

List CareTeam

Fetch a bundle of CareTeam resources based on search parameters.

Get CareTeam

Fetch a specific CareTeam resource by its unique ID.

List Communication

Fetch a bundle of Communication resources based on search parameters.

Get Communication

Fetch a specific Communication resource by its unique ID.

List Consent

Fetch a bundle of Consent resources based on search parameters.

Get Consent

Fetch a specific Consent resource by its unique ID.

List ServiceRequest

Fetch a bundle of ServiceRequest resources based on search parameters.

Get ServiceRequest

Fetch a specific ServiceRequest resource by its unique ID.

Encounters, Procedures & Diagnostics8 actions

List Encounter

Fetch a bundle of Encounter resources based on search parameters.

Get Encounter

Fetch a specific Encounter resource by its unique ID.

List Procedure

Fetch a bundle of Procedure resources based on search parameters.

Get Procedure

Fetch a specific Procedure resource by its unique ID.

List Specimen

Fetch a bundle of Specimen resources based on search parameters.

Get Specimen

Fetch a specific Specimen resource by its unique ID.

List DiagnosticReport

Fetch a bundle of DiagnosticReport resources based on search parameters.

Get DiagnosticReport

Fetch a specific DiagnosticReport resource by its unique ID.

Medications & Nutrition10 actions

List Immunization

Fetch a bundle of Immunization resources based on search parameters.

Get Immunization

Fetch a specific Immunization resource by its unique ID.

List MedicationAdministration

Fetch a bundle of MedicationAdministration resources based on search parameters.

Get MedicationAdministration

Fetch a specific MedicationAdministration resource by its unique ID.

List MedicationDispense

Fetch a bundle of MedicationDispense resources based on search parameters.

Get MedicationDispense

Fetch a specific MedicationDispense resource by its unique ID.

List MedicationRequest

Fetch a bundle of MedicationRequest resources based on search parameters.

Get MedicationRequest

Fetch a specific MedicationRequest resource by its unique ID.

List NutritionOrder

Fetch a bundle of NutritionOrder resources based on search parameters.

Get NutritionOrder

Fetch a specific NutritionOrder resource by its unique ID.

Observations & Questionnaires6 actions

List Observation

Fetch a bundle of Observation resources based on search parameters.

Get Observation

Fetch a specific Observation resource by its unique ID.

List Questionnaire

Fetch a bundle of Questionnaire resources based on search parameters.

Get Questionnaire

Fetch a specific Questionnaire resource by its unique ID.

List QuestionnaireResponse

Fetch a bundle of QuestionnaireResponse resources based on search parameters.

Get QuestionnaireResponse

Fetch a specific QuestionnaireResponse resource by its unique ID.

Organizations & People11 actions

List Caregiver Organization

Fetch a bundle of caregiver-related Organization resources.

List Organization

Fetch a bundle of Organization resources based on search parameters.

Get Organization

Fetch a specific Organization resource by its unique ID.

List Patient

Fetch a bundle of Patient resources based on search parameters.

Get Patient

Fetch a specific Patient resource by its unique ID.

List Person

Fetch a bundle of Person resources based on search parameters.

Get Person

Fetch a specific Person resource by its unique ID.

List Practitioner

Fetch a bundle of Practitioner resources based on search parameters.

Get Practitioner

Fetch a specific Practitioner resource by its unique ID.

List RelatedPerson

Fetch a bundle of RelatedPerson resources based on search parameters.

Get RelatedPerson

Fetch a specific RelatedPerson resource by its unique ID.

System Metadata4 actions

Get OperationDefinition

Fetch a specific OperationDefinition resource by its unique ID.

List Provenance

Fetch a bundle of Provenance resources based on search parameters.

Get Provenance

Fetch a specific Provenance resource by its unique ID.

Get StructureDefinition

Fetch a specific StructureDefinition resource by its unique ID.

Popular Automations

Here are common workflow patterns you can build with Oracle Cerner and Konnectify.

Sync newly updated patients to downstream systems

When patient records change in Oracle Cerner, retrieve the full patient resource and send normalized demographics to your CRM, data warehouse, or care coordination tool.

Patient Created or Updated→Get Patient

Notify teams about appointment changes

Detect new or updated appointments, retrieve appointment details, and enrich them with patient or location data for scheduling notifications.

Appointment Created or Updated→Get Appointment→Get Patient

Archive clinical documents and CCDs

Watch for DocumentReference updates, retrieve document metadata, and fetch Binary or CCD content for compliant document workflows.

DocumentReference Created or Updated→Get DocumentReference→Get Binary

Monitor lab results and diagnostic updates

Trigger when observations or diagnostic reports update, then fetch related DiagnosticReport, Specimen, or Encounter resources for review queues and analytics.

Observation Created or Updated→Get Observation→List DiagnosticReport

FAQ

How does Oracle Cerner authentication work in Konnectify?

This integration uses OAuth 2.0 through SMART on FHIR. You provide the Client ID, Client Secret, Tenant ID, and Hostname from your Oracle Cerner SMART app configuration, then authorize access through Oracle Cerner. Konnectify stores tokens securely and does not store your Oracle Cerner password.

Which Oracle Cerner plans or tenants are supported?

Supported access depends on your Oracle Cerner tenant, the SMART on FHIR app registration, enabled FHIR endpoints, and approved scopes. If a resource is not available in your tenant or your app lacks the required scope, that trigger or action may return an authorization or unsupported-resource error.

How do Oracle Cerner triggers work?

All triggers in this connector are polling triggers. Konnectify periodically queries the relevant FHIR resource endpoint and checks for new or recently updated records. Polling frequency may vary based on your Konnectify plan and workflow settings.

How does Konnectify prevent duplicate records?

This connector provides read and list operations rather than upsert actions. For polling triggers, Konnectify tracks previously processed records where supported by the workflow runtime and uses resource IDs and timestamps to reduce repeat processing. For downstream systems, map the FHIR resource ID as the external identifier whenever possible.

How are rate limits handled?

Oracle Cerner API rate limits and throttling policies can vary by tenant and endpoint. If a workflow receives a rate-limit response, Konnectify surfaces the error in workflow history. Use narrower search parameters, reduce polling scope, and avoid unnecessary high-frequency list operations when working with large clinical datasets.

Can I connect multiple Oracle Cerner accounts or tenants?

Yes. You can create separate Oracle Cerner connections in Konnectify for different tenants, hostnames, environments, or app registrations. Name each connection clearly so workflow builders can select the correct EHR environment.

What is the difference between DocumentReference, Binary, CCD, and $docref?

DocumentReference usually contains document metadata and links, while Binary stores the actual document payload. CCD refers to a Continuity of Care Document, often retrieved as a Binary document. The specialized Cerner $docref operation returns DocumentReference resources based on Cerner-supported document search behavior.

Ready to automate your Oracle Cerner workflows?

Connect Oracle Cerner to Konnectify and build secure SMART on FHIR automations across your healthcare stack.

Get started free →