Migrate from Epic Ehr to Spruce 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.
Spruce and Epic both run HIPAA-compliant two-way secure messaging between the practice and its patients. A practice already on Epic can retire the standalone Spruce contract and move the messaging workflow into the chart: have patients message through MyChart instead of the Spruce app, and triage inbound messages in the clinician's Epic In Basket on the same patient record. Because the thread lands on the system of record Epic already uses for notes, orders, and billing, a reply, a resulting order, or documentation all attach to the one chart - no separate Spruce login or copy-back. Turn on MyChart In Basket Augmented Response Technology (ART) to draft replies the clinician reviews, mirroring Spruce's saved-template/auto-reply speed-ups. Keep Epic as the system of record; cut Spruce.
- Warning: Patient adoption is the real switch cost: every patient who messaged via the Spruce app must be activated on MyChart and told to use it - migrate the practice's Spruce contact/patient list into MyChart enrollment before cancelling.
- Warning: ART (the AI draft) is a licensed/enabled Epic capability, not on by default - confirm it is provisioned for the messaging clinicians if you are replacing Spruce's templates and automated replies.
- Warning: Export and archive open Spruce conversation history before the contract ends; Spruce threads live outside the chart and will not auto-import into MyChart/In Basket.
- Warning: Rebuild Spruce's saved message templates, scheduled (delayed-delivery) messages, and auto-replies as Epic SmartPhrases / In Basket QuickActions / automated MyChart messaging - the 1:1 equivalents are not carried over.
- Warning: Spruce also carries SMS texting, e-fax, and a phone system; MyChart messaging only replaces the patient-messaging slice, so confirm those other Spruce channels are re-homed (or intentionally dropped) before cancelling.
Spruce and Epic both run live HIPAA-compliant video visits the patient joins from a link on their own device. A practice already on Epic can retire Spruce's standalone telemedicine and run the visit inside the chart instead: schedule the encounter in Epic and use Epic Video Visits, where the patient joins from MyChart and the clinician launches from Hyperdrive/Hyperspace, with the session tied to the scheduled encounter. Route the patient through MyChart eCheck-in first to sign the telehealth consent, so the visit, consent, documentation, orders, and charge all attach to the one system-of-record - versus Spruce's video, which produces nothing in the chart. Keep Epic as the system of record; cut Spruce.
- Warning: The video transport may carry a vendor cost: Epic supports its native client and launches integrated third-party platforms (e.g. Zoom for Telehealth, Pexip) natively from MyChart - confirm one is licensed/configured before cancelling Spruce.
- Warning: The Epic path assumes patients are activated on MyChart; Spruce needs no patient app-store download for web join, so validate that your patient population can onboard to MyChart before cutting over.
- Warning: Patients must complete MyChart eCheck-in (consent/documents) before joining - rebuild any pre-visit consent step Spruce handled into the eCheck-in flow.
- Warning: Spruce sends pre-visit clinical questionnaires alongside the video; if you relied on that, move those into Epic questionnaires / eCheck-in so the screening still reaches the encounter.