Skip to Main Content

API, CLI, SDK & Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Application Provisioning Process

James TidwellFeb 24 2026

Workflow or API calls:

Reminder: If this is referring to a client domain or EHR activity—not the public sandbox—do not include API request data or live patient data.

Background Information:

Failure to provide answers will impact our ability to respond in a timely and effective manner
Developer questions:

Are you an OPN Member? No
Have you signed up to be in the Healthcare Developer Track? No
Are you a registered Code Program member? No
Does your App have a presence on the Oracle Healthcare App Marketplace? No

Are you developing on behalf of an Oracle Health client? Yes and No
If so, which client:

We are implementing an integration that will be used by multiple Oracle Health customers. We do not know exactly which customers yet.

Question:

We are implementing an integration which will send appointment reminders via our phone system to patients with upcoming appointments. In the future, we also plan to add the capability of creating a call record or something similar in customers' Oracle Health app.

What I want to confirm is how will customers be able to provision our app in their tenant. From what I understand, we can create a system application. This will provide us a client ID and secret we need to use to call your APIs. For us to be able to call APIs against customer tenants, they will have to do the self provisioning described here. Is my understanding correct? Also, I wonder if it is a one to one relationship between a system app and a tenant or multiple customers would be able to provision our app on their tenant?

Thank you

Comments
Post Details
Added on Feb 24 2026
0 comments
70 views