Migrate from Klara to Oracle Health.
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.
Klara Self-Scheduling and Oracle Health both let patients book or reschedule their own appointments online, so a practice on Oracle Health can drop Klara's self-scheduling and move it into the Oracle Health Patient Portal. Keep Oracle Health, cut Klara. Turn on the portal's self-service online scheduling so patients book against real provider availability, plus Book again from past appointments/favorites and portal-based cancel/reschedule (Conversational Scheduling via Ask Oracle also handles book/cancel/reschedule in natural language). Because scheduling is one module of the system of record, a self-booked slot becomes a real encounter that flows straight into pre-registration, intake, and check-in — not a request a separate booking tool has to hand back. Point the practice's 'request an appointment' links and reminder texts at the Oracle Health Patient Portal instead of Klara's text/automated flow.
- Warning: Klara lets patients self-schedule by text with no portal login; Oracle Health self-scheduling runs through the Patient Portal (enrollment + login) — confirm the un-enrolled base can still book and which visit types are exposed before cutting Klara.
- Warning: Self-service scheduling, Book again, and Conversational Scheduling are part of the March 2026 portal release; verify the org's portal version includes them and that schedulable visit types/availability rules are configured.
- Warning: Klara positions scheduling as the entry point into pre-visit instructions and reminders; rebuild that downstream automation in the Oracle Health portal (appointment notifications, pre-registration, intake) so the journey is not lost when Klara is removed.
Klara and Oracle Health both run two-way secure patient messaging, so a practice already on Oracle Health can retire the standalone Klara/ModMed Patient Engagement contract and move messaging into the Oracle Health Patient Portal (the EHR's digital front door, successor to HealtheLife). Keep Oracle Health, cut Klara. Have patients message the care team from the Oracle Health Patient Portal instead of Klara; with the March 2026 portal release, Conversational Messaging and Message Routing send each message to the right provider or message pool based on encounter relationships, support attachments up to 50 MB, conversation search, and send/receipt status, and inbound messages route into the staff message workflow inside the EHR. Because it is one module of the system of record, a reply or refill is reconciled into the chart and can trigger orders or scheduling — not a thread to copy back. Redirect the practice's 'message us' entry points and patient onboarding to Patient Portal enrollment so there is one secure inbox.
- Warning: Klara's signature 'call-to-text' (turning an inbound phone call into a text thread) has no native Oracle Health Patient Portal equivalent — if the practice relies on it, keep a separate SMS/voice front door or accept phone-origin contacts returning to the phone queue.
- Warning: The Oracle Health portal needs patient enrollment and login, whereas Klara texts patients on plain SMS — plan to re-onboard the un-enrolled base and confirm portal adoption before cancelling Klara.
- Warning: Conversational Messaging / Message Routing arrived in the March 2026 portal release; confirm the org is on a portal version that includes it (and that provider/pool routing is configured) before relying on it.