Healthcare use case · Epic + Oracle Health + Microsoft 365
Appointment administration and service follow-up
Scheduling staff copy appointment and service request details between systems and chase follow-up by email. Appointment changes and service requests reach the right administrative staff and calendars.
Systems involved
What each system contributes
10 actions
- Appointments6
- Service Request4
13 actions
- Millennium Appointment4
Architecture
One governed run
How it starts: A scheduled check of Epic and Oracle Health starts the run.
Step by step
How the process runs
- 01
Read
Epic appointments and service requests and Oracle Health appointments are read.
- 02
Check
Rules + Code finds conflicts and missing administrative information.
- 03
Route
Administrative staff are notified in Teams or email.
- 04
Schedule
Calendar holds are created for follow-up.
Control
Human decision and exception path
Human decision
Scheduling staff confirm changes before any appointment is updated.
Exception path
- Conflicts route to scheduling staff.
- Read failures are retried.
- Unmatched records go to review.
Evidence
What gets audited
- Records read.
- Checks applied.
- Staff decisions.
- Notifications sent.
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 deploymentRelated
Patterns, connectors and next steps
- Epic connector
10 pre-built actions
- Oracle Health connector
13 pre-built actions
- Microsoft 365 connector
45 pre-built actions
- Enterprise automation
Governed processes across the systems you already run.
- Healthcare employee onboarding
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 of Epic and Oracle Health 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.
- Does this make clinical decisions?
- No. It handles administrative scheduling and follow-up. Clinical decisions stay with clinicians.
Use case review
Discuss this use case
Bring your version of the process. We will map the systems, approvals and evidence it needs.