Does Nexus replace any of these systems?

No. Each system keeps its own records. Nexus runs the process between them and records each decision.

What if a step is not covered by a pre-built action?

It runs through an API, protocol or database call, or as Rules + Code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the same approvals and audit.

Healthcare use case · Oracle Health + SAP + ServiceNow

Charge and invoice exception workflow

Charge and invoice mismatches between clinical administration and finance are resolved by email. Administrative charge and invoice mismatches are resolved with approval before finance records change.

Discuss this use case Healthcare overview

Systems involved

What each system contributes

Oracle Health

13 actions

Charge Items5

SAP

97 actions

Invoice10
Finance20

ServiceNow

55 actions

Tickets10

Trigger source: ServiceNow

Architecture

One governed run

Trigger: scheduleIntegration: Oracle Health + SAPRules + CodeHuman ApprovalSystem Action: SAPAudit

How it starts: A scheduled check starts the run.

Step by step

How the process runs

01
Read
Oracle Health charge items are read.
02
Compare
SAP invoice and finance records are compared by Rules + Code.
03
Exception
Mismatches open a ServiceNow ticket.
04
Correct
Approved SAP corrections run.

Control

Human decision and exception path

Human decision

A finance owner approves every SAP correction.

Exception path

Unmatched items route to billing staff.
SAP rejections keep the ticket open.
Read failures are retried.

Evidence

What gets audited

Charge items read.
Comparison.
Approval.
SAP response.

Nexus runs on premises, in private or sovereign cloud, or air-gapped. Credentials stay in the vault, roles decide who can approve, and the execution record stays inside your deployment boundary.

Sovereignty and deployment

SAP-ServiceNow integration
Integration pattern · ERP exceptions reach service operations, and approved changes reach SAP.
Oracle Health connector
13 pre-built actions
SAP connector
97 pre-built actions
ServiceNow connector
55 pre-built actions
Compliance evidence
Evidence produced by the work itself.
Appointment administration and service follow-up
Another healthcare use case.

FAQ

Questions about this use case

Does Nexus replace any of these systems?: No. Each system keeps its own records. Nexus runs the process between them and records each decision.
How does the run start?: A scheduled check starts the run.
What if a step is not covered by a pre-built action?: It runs through an API, protocol or database call, or as Rules + Code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the same approvals and audit.

Use case review

Discuss this use case

Bring your version of the process. We will map the systems, approvals and evidence it needs.

Discuss this use case Book a demo