Migrate from Ohmd to Eclinicalworks.
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.
OhMD lets patients self-schedule through its AI (Nia) conversation, and eClinicalWorks lets patients self-schedule through healow Open Access — the same capability on both sides. A practice already on eClinicalWorks can cut OhMD's scheduling automation and move booking into healow. Keep eClinicalWorks, cut OhMD. Operationally: enable healow Open Access so patients book from the practice website, the Patient Portal, or the healow app, viewing providers' real schedules and open slots and booking the one that fits. Because Open Access reads and writes against the eClinicalWorks practice schedule, a self-booked slot lands directly on the same provider calendar used for documentation and billing, with no double-entry or external sync. Redirect OhMD's scheduling links and prompts to the Open Access booking entry points so patients have one self-serve path.
- Warning: healow Open Access self-scheduling runs through the website widget, Patient Portal, or healow app; OhMD books patients inside a no-login text/voice conversation. Confirm Portal/healow adoption and the public booking page before retiring OhMD or some patients lose self-serve booking.
- Warning: Open Access only surfaces slots correctly if provider schedules, visit types, and open-slot rules are configured in eClinicalWorks; build these before pointing patients at it.
- Warning: OhMD also resolves scheduling conversationally over voice via Nia (callers who phone in); Open Access is screen-based, so practices leaning on OhMD's phone-call deflection should pair it with a separate call-handling plan.
- Warning: Verify OhMD-originated future appointments and pending scheduling requests are migrated or re-booked on the eClinicalWorks schedule before cancelling, so nothing is stranded in OhMD.
OhMD and eClinicalWorks both provide two-way secure patient messaging, so a practice already running eClinicalWorks can retire the standalone OhMD contract and move messaging into the EHR's own patient-engagement stack. Keep eClinicalWorks, cut OhMD. Operationally: route patients to the eClinicalWorks Patient Portal and the healow app instead of OhMD; secure messages link to the patient's record inside eClinicalWorks so a reply or refill request is documented in the chart rather than carried in a separate app and synced back, and staff triage them in the EHR message workflow off the phone. Use healow appointment reminders and broadcast/outreach messaging to keep the proactive-text feel patients had in OhMD. Repoint published 'text us' entry points and reminder flows to Portal/healow enrollment. Notably OhMD already lists eClinicalWorks as a sync target, so the chart data the practice valued from OhMD is native once messaging lives in healow.
- Warning: OhMD messages patients over plain SMS with no app, login, or portal account; the eClinicalWorks Patient Portal and healow require patient enrollment/login. Expect to re-onboard the un-enrolled patient base and confirm Portal/healow adoption before cancelling OhMD.
- Warning: OhMD can text-enable the practice landline and convert inbound calls into text threads; healow/Portal messaging has no native phone-to-text bridge, so phone-origin contacts return to the call queue unless a separate SMS tool is kept.
- Warning: Confirm the practice's healow/Patient Portal patient-engagement modules are licensed and live (messaging is part of the deployed stack, but enable Conversational/secure messaging and reminders) before retiring OhMD.
- Export and archive open OhMD conversation threads before closing the account — eClinicalWorks will not back-fill historical OhMD message history into the chart.