Oracle Health AI Integration
Oracle Health AI agents in Bonfire Terminal assist clinical and administrative work using your own EHR context and credentials. They draft summaries and organize records from a local-first desktop app, keeping sensitive health data on your machine rather than a cloud service.
What Bonfire can do in Oracle Health
Real actions from the Oracle Health API that a Bonfire agent can run on your behalf, on-device.
| Action | Resource | Method · Endpoint |
|---|---|---|
| Search patients | Patient | GET /Patient |
| Create patient | Patient | POST /Patient |
| Search appointments | Appointment | GET /Appointment |
| Book appointment | Appointment | POST /Appointment |
| Search encounters | Encounter | GET /Encounter |
| Create observation | Observation | POST /Observation |
| Search conditions | Condition | GET /Condition |
| Create medication order | MedicationRequest | POST /MedicationRequest |
Oracle Health agents in action
On your machine, not a SaaS
Bonfire Terminal
- Your keys & data stay on your device
- Perpetual license — no per-seat SaaS fee
- Any connected model — Claude, GPT, Gemini or Grok
- Offline Llama for local, private reasoning
- Driven from chat you already use
Cloud AI middleman
- Keys & data pass through a third-party server
- Recurring subscription, usage caps
- Model locked to the vendor
- Yet another dashboard to log into
Oracle Health — questions
Can Bonfire automate Oracle Health?
Yes. Bonfire runs on your machine, holds your Oracle Health credentials locally, and a connected model (Claude, GPT, Gemini or Grok) drives the Oracle Health API to run the actions you ask for in chat.
Does my Oracle Health data go to the cloud?
Bonfire runs on your desktop and keeps your keys local — it isn't a SaaS holding your data. Only the specific request you approve is sent to your chosen AI model.
Which AI models can I use?
Any connected model — Claude, GPT, Gemini or Grok. A fully offline Llama model runs locally for private reasoning but can't reach live APIs.