Migrate from Oracle Health to Relatient.
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.
Relatient Dash Intake and the Oracle Health Patient Portal both let patients complete pre-visit intake from their own device - health questionnaires, consent e-signatures, ID and insurance upload, demographic/history updates, and check-in - and reconcile the answers into the chart. A practice already on Oracle Health can retire the standalone Dash Intake contract and move registration 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, and receive confirmation when they arrive', complete custom registration health questionnaires inline, and request updates to health, social, and family history that 'providers can access, view, and reconcile' into the chart, with arrival/check-in done from the home page. Because intake is one module of the system of record, the answers reconcile directly into the same patient record Oracle's EHR uses for documentation, orders, and billing - so there is no Relatient forms integration to maintain and no separate Relatient login. Keep Oracle Health; cut Relatient.
- Warning: The Get Ready / Arrival intake feature set referenced here is the March 2026 (2026.Q1 MR1) portal release - confirm the organization's portal version has the custom registration questionnaires, ID/consent upload, and history-reconciliation workflow enabled before cancelling Relatient, since older builds may lack them.
- Warning: Rebuild every active Dash Intake form (including specialty-specific questionnaires such as orthopedic or OBGYN) as Oracle portal registration questionnaires and confirm each reconciles into the right chart location before cutover - the field-to-chart mapping Relatient's EHR integration handled will not carry over automatically.
- Warning: Dash Intake auto-extracts demographics/insurance from card scans and verifies insurance up front; the Oracle portal path centers on patient-entered details plus ID/insurance upload and provider reconciliation, so confirm the loss of OCR auto-extract and front-desk insurance verification is acceptable, or work shifts back to staff.
- Warning: Confirm copay/payment collection at intake is covered by the Oracle Health portal/billing workflow before retiring Relatient, since Dash Intake collected payments (stored cards/digital wallets) and that step must not lapse at cutover.
Relatient Dash Patient Self-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 Relatient Dash 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 Relatient-to-EHR HL7/FHIR bidirectional writeback integration to maintain and no separate Relatient login. Keep Oracle Health; cut Relatient.
- 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 Relatient, since older portal builds may lack them.
- Warning: Relatient's rules engine matches a patient to a specific provider/visit type/length and runs distinct new-patient, returning-patient, and referral workflows; verify Oracle's scheduling rules and visit-type configuration reproduce that guardrail logic so patients do not book into the wrong slot once Dash's rules are gone.
- Warning: Relatient self-scheduling needs no login and skews to new-patient capture (~70% of online bookings from new patients) and referral-link booking; confirm the Oracle portal path acceptably covers unauthenticated new-patient and referral self-scheduling, since a portal-account requirement can suppress new-patient volume.