Migrate from Luma Health 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.
Luma Digital Forms and eClinicalWorks healow CHECK-IN both let patients complete pre-visit intake from their phone - questionnaires, consents, demographic/insurance review - and write the answers into the chart. A practice already on eClinicalWorks can retire Luma's standalone Digital Forms (and the dedicated Luma EHR Integration for Forms) and move intake into healow CHECK-IN: the day before the visit it texts the patient a secure healow link where they confirm the appointment, review and update demographics, confirm insurance, e-sign consents, complete customizable (state- or clinic-specific) questionnaires, and review meds/allergies/history. Because CHECK-IN runs on the eClinicalWorks/healow stack, the captured demographics, consents, and questionnaire data import directly into the same chart - eClinicalWorks states customizable form and questionnaire data imports into Progress and SOAP notes - so there is no Luma forms integration to maintain and no separate Luma login. Keep eClinicalWorks; cut Luma.
- Warning: Rebuild every active Luma form as a healow CHECK-IN customizable questionnaire and verify each maps to the right Progress/SOAP note section before cutover - field-to-chart mapping that Luma's EHR Integration for Forms handled will not carry over automatically.
- Warning: healow CHECK-IN sends its secure link by text the day before the visit; Luma can prompt forms via SMS, website, LumaBot, and the Voice Navigator across a wider window - confirm the single day-before text cadence still yields acceptable completion, and that the practice's appointments are in eCW so CHECK-IN can target them.
- Warning: Copay collection at intake moves from Luma's payment capture to healow Payment Services - confirm healow Payments is enabled and configured so pre-visit copay collection does not lapse when Luma is cut.
Luma Patient Scheduling+ and eClinicalWorks both let patients view real provider availability and self-book, reschedule, or request an appointment online around the clock. A practice already on eClinicalWorks can retire the standalone Luma Scheduling+ contract and move the workflow into healow Open Access: patients book from the practice website, the Patient Portal, or the healow app, seeing each provider's real open slots, and the practice can let patients either book directly or only request a slot for staff to confirm. Because Open Access reads and writes against the eClinicalWorks practice schedule, the booked slot lands directly on the same provider calendar eCW uses for clinical documentation, orders, and billing - so there is no Luma-to-EHR bidirectional writeback integration to maintain and no separate Luma login. Keep eClinicalWorks; cut Luma.
- Warning: Open Access publishes whatever slice of each provider's schedule the practice chooses and supports a book-vs-request-only mode per provider - rebuild Luma's appointment-type rules and provider guardrails as Open Access settings before cutover, or self-booking accuracy will regress.
- Warning: Luma's questionnaire-driven matching steers a patient to the right provider/visit type/length; healow Open Access leans on published-slot and visit-type setup rather than a Luma-style guided questionnaire - confirm the practice's visit-type configuration reproduces that routing so patients do not book the wrong slot once Luma is gone.
- Warning: Luma also drives bookings from SMS, Google Search, and its AI Voice Navigator; the healow front doors are the website widget, Patient Portal, and healow app - if a meaningful share of Luma volume came from text or the voice agent, confirm those channels are acceptably replaced before retiring Luma.