Migrate from Nabla to Oracle Health.
1 documentation-derived translation pattern — what carries over and what to watch for. Cited to the Feature Parity Map; the audit tells you whether the move is worth it.
Nabla Copilot and the Oracle Health Clinical AI Agent both listen to the consultation ambiently and draft the structured note for clinician review. A practice on Oracle Health (Cerner Millennium) runs Nabla as a separate paid contract that pushes its note back into the chart; to retire it, enable the Oracle Health Clinical AI Agent, which is embedded in the EHR and uses ambient voice plus a multimodal voice UI to write the draft note straight into the same encounter used for results, orders and billing. Capture happens inside the Oracle Health workflow rather than the Nabla app, and because it lives in the system of record the Clinical AI Agent can also draft orders (labs, imaging, meds, follow-ups) from the conversation — a step Nabla can only paste back as text. Keep Oracle Health, cut Nabla.
- Warning: The Oracle Health Clinical AI Agent is licensed as part of the Oracle Health clinical suite — confirm it is provisioned and enabled for your specialties before cancelling Nabla (it is documented across 30+ specialties, but verify yours is live).
- Warning: Re-create Nabla's note templates (SOAP/APSO/WCC) in the Clinical AI Agent's note configuration; section structure and formatting will differ and need clinician sign-off.
- Warning: Validate the Clinical AI Agent's drafted orders before trusting them in place of Nabla's note-only output — order creation infers dosage/frequency/pharmacy and must be reviewed, and this is a newer capability than the note drafting.
- Warning: Reconcile or export any Nabla note history you must keep before the contract lapses; Nabla retains no audio by default.