Capture
AGIMINION records the room
AGIMINION captures the visit audio in the exam room and sends it to the appliance on your network. The audio and transcript stay local, with no cloud account and no internet round trip to transcribe.
All integrationsOracle Health
EHR integration
Send the signed note and codes back to Oracle Health Millennium
AGIMAN captures the visit on an appliance inside your network, drafts the chart note in the clinician's style, and suggests ICD and CPT codes. After the clinician reviews and signs, the approved note and codes map to your Oracle Health Millennium chart over FHIR R4.
- HIPAA compliant
- Runs on your network
- Clinician signs every note
- System
- Oracle Health
- Category
- EHR
- Used by
- Hospitals and large health systems
- Connects over
- Oracle Health Ignite APIs, code console
The connection
How AGIMAN connects to Oracle Health.
What Oracle Health is
Oracle Health is the electronic health record formerly known as Cerner Millennium, which Oracle acquired in 2022. It runs the inpatient and ambulatory record for many large hospitals and academic health systems, and it is one of the two largest EHRs in the United States by hospital share. Clinicians document encounters, orders, and results in Millennium, and the system exposes data through Oracle Health's Ignite APIs.
Who runs it
Hospitals and large health systems
The access path
FHIR R4SMART on FHIROAuth 2.0HL7v2
AGIMAN connects to Millennium through Oracle Health's Ignite APIs on FHIR R4, registered in the code console under your health system's CernerCare account. The app authenticates with SMART on FHIR and OAuth 2.0, and it requests only the scopes your team approves, such as reading the encounter and writing the document and coded entries. Oracle Health provisions apps per site, so the export path is scoped and tested against your own Millennium instance before it is turned on at go-live. Where you need real-time event data that FHIR does not yet carry, AGIMAN can take HL7v2 over your interface engine.
The Oracle Health export path is scoped and tested against your own Millennium instance before it is turned on at go-live.
The workflow
From the exam room to Oracle Health, with you in control.
Draft
AGIMAN drafts the note and codes
AGIMAN drafts the chart note in the clinician's style and suggests ICD and CPT codes for the encounter, plus any referral letter, patient handout, or visit form the visit calls for.
Review and sign
The clinician reviews and signs
The clinician reads the draft, edits anything, and signs. Nothing leaves the appliance for Millennium until a human has approved it.
Sync
Map to Millennium over FHIR R4
The signed note and approved codes map to your Millennium chart through the Ignite APIs, written to the encounter and document fields your scopes allow, with a review log of what was sent.
After sign-off
What AGIMAN hands back to Oracle Health.
The chart note
The reviewed and signed note maps to the matching document and encounter fields in Millennium through the Ignite FHIR R4 endpoints, in the clinician's own wording.
Codes for the encounter
The ICD and CPT codes the clinician approved attach to the encounter as coded entries, ready for the coder and billing team to confirm in Millennium.
Referrals and documents
Referral letters, patient handouts, and visit forms are prepared as documents for the clinician to attach or send, never filed to the chart on their own.
On your network
Local first, before any export.
- Room audio and transcripts stay on the appliance on your network.
- Transcription and note drafting run on site, with no internet connection required.
- Nothing reaches Oracle Health until the clinician reviews and signs.
- Exports use the access path your practice approves, with a BAA available.
Questions
Oracle Health, answered.
Where do the visit audio and drafts live?
On the AGIMAN appliance inside your practice network. Room audio, transcripts, and drafts stay local, and no internet connection is needed to transcribe or draft. A BAA is available and AGIMAN is HIPAA compliant.
How does AGIMAN reach our Millennium instance?
Through Oracle Health's Ignite APIs on FHIR R4, registered in the code console and authenticated with SMART on FHIR and OAuth 2.0. Oracle Health provisions apps per site, so the path is enabled in your own environment with the scopes your team approves.
Does AGIMAN write to the chart on its own?
No. A clinician reviews and signs every note and every code before anything maps to Millennium. AGIMAN automates the drafting and the mapping, not the clinical judgment, and it keeps a review log of what was sent.
Other EHR integrations
See all integrations
Get started
Run AGIMAN alongside Oracle Health.
Buy the appliance and room devices, then scope the Oracle Health export path with us. We test it against your instance before it is turned on.