Move your team from Oracle Health (Cerner) to Spruce Health.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Spruce Health — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in Oracle Health (Cerner) is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
Spruce and Oracle Health both run two-way secure patient-practice messaging. A practice already on Oracle Health can retire the standalone Spruce contract and move messaging into the EHR's patient portal: have patients message through the Oracle Health Patient Portal Cloud Service (the digital front door, successor to HealtheLife) instead of the Spruce app, and handle replies in the staff message workflow inside the EHR. Per the March 2026 portal release, Conversational/Manage Messaging routes a message to the specific provider or message pool based on encounter relationships, supports file attachments up to 50 MB, conversation search, a rich-text editor, and send/receipt indicators - so the thread runs against the same patient identity used for documentation and orders, and an inbound message can be reconciled into the chart and trigger orders or scheduling. That is the gap Spruce can't close: its threads carry only text and live outside the chart. Keep Oracle Health as the system of record; cut Spruce.
- Warning: Patient adoption is the switch cost: patients who messaged via the Spruce app must be enrolled and active on the Oracle Health Patient Portal - migrate the practice's Spruce patient/contact list into portal enrollment before cancelling.
- Warning: Confirm the org is on the current Oracle Health Patient Portal Cloud Service (not legacy HealtheLife) and that the messaging release features are enabled, since routing/attachments shipped in the 2026.Q1 portal release.
- Warning: Export and archive open Spruce conversation history before the contract ends; Spruce threads will not import into the Oracle portal inbox.
- Warning: Rebuild Spruce's saved templates, scheduled messages, and auto-replies on the Oracle side - the portal's rich-text editor and pool routing are not a 1:1 carryover of Spruce automations.
- Warning: Spruce also bundles SMS texting, e-fax, and a phone system; the portal only replaces the patient-messaging slice, so re-home (or intentionally drop) those other channels before cancelling.
Spruce and Oracle Health both run live HIPAA-compliant video visits for virtual appointments. A practice already on Oracle Health can retire Spruce's standalone telemedicine and run the visit inside the EHR: use Oracle Health Scheduled Video Visits, the native solution where patients schedule, register for, and join the video visit from the same Oracle Health Patient Portal they already use. Because the visit is created as a real encounter on the system of record, it writes back to the same chart used for documentation, orders, and billing - delivering longitudinal, hybrid in-person-plus-virtual care rather than the episodic, disconnected encounter a standalone tool like Spruce leaves behind. Keep Oracle Health as the system of record; cut Spruce.
- Warning: Use the native Scheduled Video Visits path: a prior Microsoft Teams EHR-connector virtual-appointment integration into Oracle Health has been discontinued by Microsoft ('This EHR integration is no longer supported'), so do not plan the cutover around Teams.
- Warning: Confirm Scheduled Video Visits is provisioned/enabled in your Oracle Health portal stack before cancelling Spruce; it is part of the EHR/portal stack rather than a separately priced add-on, but availability still depends on your deployment.
- Warning: The Oracle path assumes patients are enrolled on the Oracle Health Patient Portal; Spruce needs no patient app-store download for web join, so validate patient onboarding to the portal before cutting over.
- Warning: Spruce sends pre-visit clinical questionnaires with the visit; move that screening into the portal's Get Ready / pre-visit workflow so it still reaches the encounter.