Move your team from Oracle Health (Cerner) to Phreesia.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Phreesia — 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.
Phreesia and Oracle Health both run self-service, pre-visit intake. A practice already on Oracle Health can retire the standalone Phreesia intake contract and move the workflow into the Oracle Health Patient Portal Cloud Service: the 'Get Ready' / Pre-visit Workflows and Arrival flows let patients upload ID, sign consent forms, submit pre-visit details, complete custom registration questionnaires, request updates to health/social/family history, and confirm arrival from their own device — and because intake is one module of the system of record, the answers reconcile straight into the same chart used for documentation, orders, and billing rather than a PDF/export staff re-key. Keep Oracle Health as the system of record; cut Phreesia.
- Warning: The 'Get Ready' pre-visit, custom-questionnaire, and Arrival-in-portal capabilities arrived in the Oracle Health Patient Portal March 2026 (2026.Q1 MR1) release — confirm the org is on a portal version that includes them and that they are turned on before cancelling Phreesia.
- Warning: Phreesia ships pre-built specialty-specific intake logic and validated screeners/PROs; in Oracle Health the equivalent custom questionnaires must be authored and tested first, so rebuild the question sets before cutover.
- Warning: History updates patients submit are reconciled by providers (access/view/reconcile), not auto-merged — set the staff reconciliation workflow before relying on it.
- Warning: If Phreesia collected copays at intake, confirm Oracle Health patient-payment/registration collection is configured so point-of-service payment does not regress.
Phreesia and Oracle Health both let patients self-book online against real availability. A practice already on Oracle Health can drop Phreesia self-scheduling and run booking through the Oracle Health Patient Portal Cloud Service: self-service online scheduling, 'Book again' from past appointments/favorites with add-to-calendar, self-reschedule and self-cancel, confirmation links via the patient's preferred contact method, and natural-language 'Ask Oracle' scheduling navigation. Because the portal writes bookings into the same scheduling and patient record the EHR uses for documentation and billing, a self-booked slot becomes a real encounter that flows straight into pre-registration, intake, and check-in — no separate booking tool handing the appointment back. Keep Oracle Health as the system of record; cut Phreesia.
- Warning: Several of these scheduling features (Ask Oracle scheduling, Book again/add-to-calendar, expanded notifications) landed in the Oracle Health Patient Portal March 2026 (2026.Q1 MR1) release — confirm the org's portal version includes them before cancelling Phreesia.
- Warning: Online self-scheduling depends on correctly configured scheduling rules/templates and visit types in Oracle Health; rebuild and test the booking logic to match Phreesia's specialty routing before cutover.
- Warning: Phreesia's VoiceAI phone self-scheduling and Appointment Accelerator waitlist/no-show auto-backfill have no exact native equivalent; if telephone self-booking or automated cancellation backfill is relied on, plan a replacement before cancelling Phreesia.
- Warning: Re-point website 'Book appointment' and outreach links from the Phreesia self-scheduling URL to the Oracle Health portal scheduling entry point.