Migrate from Oracle Health to Suki.
2 documentation-derived translation patterns — what carries over and what to watch for. Cited to the Feature Parity Map; the audit tells you whether the move is worth it.
Suki and Oracle Health both listen to the visit ambiently and draft the structured note. A practice on Oracle Health (Cerner Millennium) can drop the standalone Suki contract by using the EHR's own ambient module: enable the Oracle Health Clinical AI Agent, a voice-first ambient assistant embedded directly in the chart. It converts the conversation into a draft note (multilingual) on the same encounter used for results review, orders, and billing, and — beyond what a paste-back scribe does — drafts clinical orders (labs, imaging, new/refill medications, follow-up appointments) into the live order workflow. Clinicians edit and sign in Oracle Health rather than logging into Suki. Keep the Oracle Health EHR; cut the standalone Suki.
- Warning: The Clinical AI Agent is licensed as part of the Oracle Health clinical suite, not free — confirm it is contracted and enabled for your clinicians (and that automated order creation is turned on) before cancelling Suki.
- Warning: Re-validate Suki's specialty note types and customized sections against the Clinical AI Agent's note structure, and verify your specialties are among the supported set before the cutover.
- Warning: Suki also offers a native Oracle Health integration, so confirm you are retiring the standalone Suki subscription rather than an Oracle-side entitlement before flipping the workflow to Oracle's own ambient.
- Warning: Auto-drafted orders (meds/labs/imaging/follow-ups) and the drafted note must be clinician-reviewed and signed in Oracle Health — treat them as drafts, not auto-filed.
- Warning: Patient consent for ambient recording still applies in the Oracle workflow.
Suki lets clinicians ask natural-language questions about a patient's chart and generates concise patient summaries; Oracle Health offers the same through the Oracle Clinical Digital Assistant, the conversational companion inside the Clinical AI Agent. A practice on Oracle Health can retire Suki's chart Q&A by using the Clinical Digital Assistant: clinicians ask by voice or text — e.g. 'show me the patient's latest MRI results' or for current meds/allergies — and it retrieves the information and surfaces pre-visit insights and visual summaries against the live chart, then can launch the next clinical action in the same system of record. Use the Oracle assistant for chart questions and summaries instead of Suki. Keep Oracle Health; cut the standalone Suki.
- Warning: The Clinical Digital Assistant is part of the Oracle Health Clinical AI Agent / clinical-suite license, not a free add-on — confirm it is contracted and enabled for your clinicians before dropping Suki's chart-Q&A workflow.
- Warning: Validate that the question types and pre-visit summaries clinicians rely on in Suki are actually supported by the Clinical Digital Assistant for your specialties and chart data before the cutover.
- Warning: Both tools generate AI summaries from the chart — keep clinicians reviewing the source data in the record; summaries are decision support, not a substitute for the underlying chart.
- Warning: If clinicians used Suki Q&A across multiple EHRs, note the Oracle assistant only answers against Oracle Health data — non-Oracle charts are out of scope.