Healthcare · 13 pre-built actions
Oracle Health integration with Nexus
Connect Oracle Health to administrative operations. Appointment, charge item, insurance plan, patient card and medication request actions let administrative steps run with approval and a record.
Nexus orchestrates administrative and operational steps around the clinical system. Clinical decisions stay with clinicians and the system of record.
Pre-built actions
What you can automate
13 pre-built Oracle Health actions, grouped by what they work on.
13
PRE-BUILT ACTIONS
- 01Millennium Appointment actions work with scheduling.
- 02Charge Items and Insurance Plan actions support billing administration.
- 03Patient Card and Medication Request actions read the records a step needs.
Workflow
How it fits into a Nexus workflow
Oracle Health steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Oracle Health API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Charge review
Charge items outside policy go to billing staff for review.
Insurance check before scheduling
Insurance plan data is checked before an appointment is confirmed.
Appointment changes
Changes notify the patient through approved channels.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Industry use cases
Processes that use Oracle Health
FAQ
Oracle Health connector questions
- Which Oracle Health actions are pre-built?
- Nexus includes 13 pre-built Oracle Health actions across Millennium Appointment (4), Charge Items (5), Insurance Plan (2), Patient Card (1) and Medication Request (1).
- Can Oracle Health start a workflow?
- Runs that use Oracle Health start from a webhook, a schedule or another trigger source. Oracle Health steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Oracle Health API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- Healthcare
Governed automation for healthcare operations.
- Epic connector
Appointments and service requests.
- Human-in-the-loop
Where approval belongs in a running workflow.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Oracle Health fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.