Migrate from Oracle Health to Ohmd.
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.
OhMD lets patients self-schedule through its AI (Nia) conversation, and Oracle Health lets patients self-schedule through the Patient Portal Cloud Service — the same capability on both sides. A practice already on Oracle Health can cut OhMD's scheduling automation and move booking into the portal. Keep Oracle Health, cut OhMD. Operationally: enable the portal's self-service online scheduling so patients find and book their own appointments against real provider availability, plus reschedule, cancel, and 'Book again' from past appointments and favorites with add-to-calendar. Because bookings write into the same scheduling and patient record the EHR uses, a self-booked slot becomes a real encounter that flows straight into pre-registration, intake, and check-in — not a request a separate tool has to hand back. Use 'Ask Oracle' natural-language scheduling and confirmation links via the patient's preferred contact method to keep the conversational feel OhMD offered, and redirect OhMD's scheduling prompts to the portal.
- Warning: Oracle portal self-scheduling requires patient enrollment/login; OhMD books patients inside a no-login text/voice conversation. Confirm portal adoption before retiring OhMD or a slice of patients loses self-serve booking.
- Warning: Self-service scheduling only surfaces correct slots if provider availability, visit types, and scheduling rules are configured in Oracle Health; build these before directing patients to it.
- Warning: OhMD resolves scheduling conversationally over voice via Nia for callers who phone in; the Oracle portal flow is screen-based (with 'Ask Oracle' text), so practices relying on OhMD's phone-call deflection should pair the portal with a separate call-handling plan.
- Warning: Verify OhMD-originated future appointments and pending scheduling requests are migrated or re-booked in Oracle Health before cancelling, so nothing is stranded in OhMD.
OhMD and Oracle Health both provide two-way secure patient messaging, so a practice already running Oracle Health can retire the standalone OhMD contract and move messaging into the EHR's own patient portal. Keep Oracle Health, cut OhMD. Operationally: route patients to message the care team from the Oracle Health Patient Portal Cloud Service (the EHR's digital front door, successor to HealtheLife) instead of OhMD. Using the portal's Conversational Messaging / 'Manage messages', inbound messages route to the matching provider or message pool based on encounter relationships and are handled in the staff message workflow inside the EHR, so a reply or refill request can be reconciled into the chart and trigger orders or scheduling — rather than carried in a separate app and synced back. Lean on rich-text composing, attachments, conversation search, and send/receipt indicators so staff keep the responsiveness they had in OhMD, and repoint published 'text us' entry points to portal enrollment.
- Warning: OhMD messages patients over plain SMS with no app, login, or portal account; the Oracle Health Patient Portal requires patient enrollment/login. Expect to re-onboard the un-enrolled patient base and confirm portal adoption before cancelling OhMD.
- Warning: OhMD can text-enable the practice landline and convert inbound phone calls into text threads; the Oracle portal has no native phone-to-text bridge, so phone-origin contacts return to the call queue unless a separate SMS tool is retained.
- Warning: Confirm the org is on the current Oracle Health Patient Portal Cloud Service (not only legacy HealtheLife) and that Conversational Messaging features from the March 2026 release are enabled before retiring OhMD.
- Export and archive open OhMD conversation threads before closing the account — the Oracle portal will not back-fill historical OhMD message history into the chart.