Migrate from Oracle Health to Weave.
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.
Weave and Oracle Health both let patients book appointments online, so a practice on Oracle Health can retire Weave Scheduling and move booking into the Oracle Health Patient Portal Cloud Service: patients self-schedule against real provider availability, use 'Book again' from past appointments/favorites with add-to-calendar, get scheduled/rescheduled/canceled notifications and confirmation links via their preferred contact method, and can navigate scheduling by natural language through 'Ask Oracle'. Keep Oracle Health (the system of record where a self-booked slot becomes a real encounter flowing straight into pre-registration, intake, and check-in); cut Weave. The portal's confirmation links and appointment notifications replace the confirmations/reminders Weave fired around each booking.
- Warning: Weave can run 'with or without an integrated PMS' and posts an appointment request staff approve; the Oracle Health portal writes the booking into the EHR schedule, so confirm provider availability/templates are built so self-scheduling has real bookable slots before cutting Weave.
- Warning: Weave bundles scheduling with reminders and its VoIP phone line — confirm Oracle Health portal notifications and confirmation links cover the reminder cadence Weave sent before turning Weave off.
- Warning: Self-service online scheduling, 'Book again', and Ask Oracle scheduling navigation are 2026.Q1 portal features — verify the org is on (or scheduled for) the March 2026 portal release and that scheduling is enabled before cancelling Weave.
- Warning: If the practice adopted Weave because its prior system was not portal-integrated, validate that Oracle Health scheduling rules and visit types are configured so the right patients reach the right slot.
Weave and Oracle Health both run two-way patient messaging, so a practice on Oracle Health can retire the standalone Weave contract and move the conversation into the Oracle Health Patient Portal Cloud Service: patients message from the portal/app and, via Conversational Messaging, the thread routes to the right provider or message pool based on encounter relationships and is handled in the staff message workflow inside the EHR — covering the scheduling, intake, and billing conversations Weave carried over SMS. Keep Oracle Health (the system of record where an inbound message can be reconciled into the chart and trigger orders or scheduling); cut Weave. The March 2026 portal release adds attachments up to 50 MB, conversation search, a rich-text editor, send/receipt status, and secure-message notifications so the portal inbox replaces Weave's shared inbox feature-for-feature.
- Warning: Weave texts from the practice's own phone/VoIP line and reaches patients who never enroll in a portal; Oracle Health messaging is portal-first, so confirm portal activation/adoption and keep an SMS notification fallback before cutting Weave or unportaled patients lose the channel.
- Warning: Weave bundles texting with VoIP phone, reminders, reviews, and payments under one login — cutting Weave for messaging alone can strand those adjacent workflows, so scope what else the practice runs on Weave first.
- Warning: Conversational Messaging routing, pools, and the 2026.Q1 messaging features must be configured/enabled on the org's portal release before cancelling Weave; verify the practice is on (or scheduled for) the March 2026 portal version.
- Re-point any reminder/confirmation/recall texts Weave automated onto Oracle Health portal notifications so nothing silently stops sending when Weave is turned off.