Move your team from Epic to Relatient.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Relatient — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in Epic is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
Relatient Dash Intake and Epic both let patients complete pre-appointment intake from their own device - appointment-specific questionnaires, consent e-signatures, demographic and insurance updates, insurance-card/ID capture, and copay payment - and write the answers back into the chart. A practice already on Epic can retire the standalone Dash Intake contract and move registration into MyChart eCheck-in plus Epic Welcome / Hello Patient: assigned Epic Questionnaires file directly into the visit encounter, patients e-sign consents, verify or update demographics and insurance, photograph insurance cards and IDs, and pay copays before arrival, with an in-office kiosk covering on-site arrivals. Because eCheck-in writes into the same Epic record and Prelude registration used for clinical documentation and billing, the intake data is structured and reused downstream with no separate Relatient forms integration to maintain and no Relatient login. Keep Epic as the system of record; cut Relatient.
- Warning: Map every active Dash Intake form (including its specialty-specific questionnaires such as orthopedic or OBGYN) to an Epic Questionnaire and confirm which ones can be completed in eCheck-in vs still require in-person signature before cutover - Epic notes some forms/questionnaires are not available via eCheck-in and need in-person verification, so a blind cut could drop a required form.
- Warning: Confirm the practice's MyChart activation rate is high enough to carry intake volume before retiring Relatient - Dash Intake collects forms from patients with no portal account or app, whereas Epic eCheck-in is gated behind an active MyChart login (kiosk/Hello Patient covers on-site arrivals but not pre-visit-at-home for non-MyChart patients).
- Warning: Dash Intake auto-extracts demographics/insurance from card scans and verifies insurance up front; validate that Epic's eCheck-in card capture and any coverage/eligibility verification reproduce that front-desk-time savings before cutover, since losing the OCR/auto-extract step can shift work back to staff.
- Warning: Re-point copay collection at intake from Relatient's payment capture to Epic's eCheck-in copay/payment workflow, and confirm card-on-file handling is acceptable, so pre-visit payment collection does not lapse when Relatient is cut.
Relatient Dash Patient Self-Scheduling and Epic both let patients book, reschedule, or cancel online against real provider availability, both use rules/decision logic to route the patient to the right provider by appointment type, and both offer earlier-slot waitlisting (Relatient waitlist/recall vs Epic Fast Pass). A practice already on Epic can retire the standalone Relatient Dash contract and move the same workflow into Epic itself: turn on MyChart Open Scheduling (for not-yet-registered patients off the website, referral links, or Google) and Direct Scheduling (for logged-in patients) running on the Cadence scheduling module, and build Epic Decision Trees so patients are matched to the correct provider, specialty, visit type, and length exactly as Dash's rules engine did. Because it runs on Cadence, every booking writes straight to the same Epic patient record, registration (Prelude), and billing (Resolute) the practice already uses, so there is no Relatient-to-Epic HL7/FHIR bidirectional writeback integration to maintain and no separate Relatient login. Keep Epic as the system of record; cut Relatient.
- Warning: Open/Direct Scheduling and the Cadence decision-tree build are a configuration project, not a flip-the-switch toggle - budget Epic analyst time to rebuild Dash's appointment-type-to-provider routing (including its distinct new-patient, returning-patient, and referral workflows) as Epic Decision Trees before cancelling Relatient, or new-patient and referral self-booking quality will regress at cutover.
- Warning: Relatient self-scheduling needs no patient login and was Best in KLAS 2024 partly on new-patient capture (it cites ~70% of online bookings from new patients); Epic Direct Scheduling is gated behind an active MyChart account, so confirm MyChart Open Scheduling adequately covers the unauthenticated new-patient and referral-link path before retiring Relatient or new-patient volume can drop.
- Relatient also drives self-scheduling from referral links, SMS, chat, and Voice AI on a single shared rules engine; Epic's equivalent front doors are MyChart and the public Open Scheduling web link - if a meaningful share of Dash bookings came from referral links, text, or the voice agent, confirm those channels are acceptably replaced before cutover.