Migrate from Oracle Health to Luma 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.
Luma Digital Forms and the Oracle Health Patient Portal both let patients complete pre-visit intake from their own device - questionnaires, consents, demographic/insurance details - and reconcile the answers into the chart. A practice already on Oracle Health can retire Luma's standalone Digital Forms (and the dedicated Luma EHR Integration for Forms) and move intake into the portal's 'Get Ready' and Arrival workflows: per the 2026.Q1 portal release patients upload their ID, sign consent forms, submit pre-visit details, answer custom health-related registration questionnaires, request updates to health/social/family history, and confirm arrival from their own device. Because Get Ready is one module of the system of record, the questionnaire responses and history updates are ones 'providers can access, view, and reconcile' directly into the same Oracle patient record used for documentation, orders, and billing - so there is no Luma forms integration to maintain and no separate Luma login. Keep Oracle Health; cut Luma.
- Warning: The Get Ready pre-visit workflow, Custom Questionnaires, and Update History features cited here are the March 2026 (2026.Q1 MR1) portal release - confirm the org's portal version has them enabled before cancelling Luma.
- Warning: Oracle history updates are a patient-requested change a provider must reconcile, not a silent overwrite of the chart; rebuild Luma's forms as Oracle custom registration questionnaires and confirm staff own the reconcile step so no intake data is silently dropped at cutover.
- Warning: Luma prompts form completion via SMS, website, LumaBot, and the Voice Navigator and can collect from patients with no portal account; Oracle Get Ready is completed inside the patient portal - verify portal adoption and the practice's reminder cadence carry intake completion before retiring Luma's multi-channel nudges.
Luma Patient Scheduling+ and the Oracle Health Patient Portal both let patients find and book their own appointments against real provider availability and reschedule or cancel without phoning the office. A practice already on Oracle Health can retire the standalone Luma Scheduling+ contract and move the workflow into the Oracle Health Patient Portal Cloud Service: per the 2026.Q1 portal release patients self-schedule online, use 'Book again' to rebook a past appointment or a favorite (with add-to-calendar), get notifications for scheduled/rescheduled/canceled visits and pre-registration, confirm via their preferred contact method, and navigate scheduling questions through 'Ask Oracle'. Because the portal writes the booking into the same scheduling and patient record Oracle's EHR uses for documentation and billing, a self-booked slot becomes a real encounter that flows on into pre-registration and check-in - so there is no Luma-to-EHR bidirectional writeback integration to maintain and no separate Luma login. Keep Oracle Health; cut Luma.
- Warning: The portal self-scheduling feature set referenced here is the March 2026 (2026.Q1 MR1) release - confirm the organization is on a portal version that has online self-scheduling, Book again, and Ask Oracle scheduling navigation enabled before cancelling Luma, since older portal builds may lack them.
- Warning: Luma's questionnaire-driven routing matches a patient to a specific provider/visit type/length; verify Oracle's scheduling rules and visit-type configuration reproduce that guardrail logic so patients do not book into the wrong slot once Luma's questionnaires are gone.
- Warning: Luma also drives bookings from SMS, Google Search, and its AI Voice Navigator, while the Oracle path is portal-centric (with Ask Oracle natural-language navigation) - if a large share of Luma volume came from text or the voice agent, confirm the portal channel and notifications acceptably replace those front doors before cutover.