Move your team from NexHealth to Oracle Health (Cerner).
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Oracle Health (Cerner) — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in NexHealth is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
NexHealth digital forms and the Oracle Health Patient Portal both run pre-visit intake — consent signatures, demographics/insurance, health questionnaires, and medication/allergy/history review — before the patient arrives, so a practice on Oracle Health can drop the standalone NexHealth Forms add-on and move intake into the portal. Keep Oracle Health (intake answers reconcile directly into the same patient record used for clinical documentation, orders, and billing); cut NexHealth. Operationally: use the Oracle Health Patient Portal 'Get Ready' and Arrival workflows — patients upload ID, sign consent forms, submit pre-visit details, answer custom registration questionnaires, and request updates to health/social/family history that providers access, view, and reconcile into the chart, then complete Arrival/check-in from a personal device. This replaces NexHealth's text/email form delivery and its Synchronizer-based push of demographics, medications, allergies, and conditions back to the chart.
- Warning: NexHealth forms reach patients on plain text/email with no portal or app; Oracle's Get Ready/Arrival intake runs inside the Patient Portal, so confirm patients are enrolled/active in the portal before cutting NexHealth or the un-enrolled lose the intake channel.
- Warning: Get Ready custom questionnaires, ID upload, consent signing, and history-update workflows are governed by the March 2026 Patient Portal release — verify your org is on a portal version that includes them before retiring NexHealth.
- Warning: History updates in Oracle are submitted by the patient and must be reconciled by a provider before they land in the chart; this is a review step NexHealth's auto-sync-to-chart model did not impose — adjust staff workflow accordingly.
- Warning: Rebuild NexHealth's conditional-logic forms and any appointment-type / procedure-code / new-vs-returning targeting as Oracle registration questionnaires; that template logic does not migrate automatically.
NexHealth and the Oracle Health Patient Portal both let patients self-book online against real provider availability and get confirmations, so a practice running Oracle Health can retire the standalone NexHealth scheduling add-on and move booking into the portal. Keep Oracle Health (the booked slot becomes a real encounter in the same scheduling and patient record the EHR uses for documentation and billing); cut NexHealth. Operationally: enable self-service online scheduling in the Oracle Health Patient Portal Cloud Service, with 'Book again' from past appointments/favorites, add-to-calendar, scheduled/rescheduled/canceled notifications, and confirmation links to the patient's preferred contact method — replacing NexHealth's 'Book Now' widget and shared links. Because scheduling is one module of the system of record, the booked visit flows straight into pre-registration, intake, and check-in, so the NexHealth Synchronizer write-back layer is no longer needed.
- Warning: Oracle Health self-service scheduling is governed by the March 2026 Patient Portal release — confirm your org is on a portal version that includes self-service online scheduling and confirmation links before cancelling NexHealth, since availability of these items is version-gated.
- Warning: The Oracle portal books against the EHR's own scheduling logic; rebuild NexHealth's appointment-type, provider/location, custom-duration, rotating-schedule, and new-vs-existing rules (which NexHealth's team configured for you) inside Oracle scheduling so open slots surface correctly.
- Warning: Re-point NexHealth's external booking entry points — website 'Book Now' widget, Reserve-with-Google button, and text/email/QR/social links — to the Oracle Health Patient Portal scheduling URL so external scheduling traffic is not stranded.