Move your team from eClinicalWorks to Freed.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Freed — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in eClinicalWorks is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
Freed and eClinicalWorks both capture the patient conversation ambiently and draft a structured note. A practice on eClinicalWorks can retire the standalone Freed subscription and document with Sunoh.ai, the ambient AI scribe natively wired into the eCW Progress Note: Sunoh listens to the visit, generates a SOAP note plus labs, orders, and follow-up appointments, and the provider edits and imports it directly into the Progress Note inside the eClinicalWorks EHR (desktop, eClinicalTouch on iPad, or eClinicalMobile). Because the draft lands in the same chart eCW already uses for orders, coding, and billing, there is no separate Freed login and no paste-back. Keep eClinicalWorks; cut Freed.
- Warning: Sunoh.ai is a paid add-on to the eClinicalWorks license (publicly listed around $149/user/month, with possible additional monthly charges) - price the Sunoh seats against the Freed contract being cancelled, not assume it is free.
- Warning: Sunoh markets itself as EHR-agnostic but the deep one-click import-to-Progress-Note path is the eCW-native integration; confirm the practice is using the eCW-integrated Sunoh, not a generic deployment, before cutting Freed.
- Warning: Re-validate specialty templates and SOAP section mapping - Freed's specialty-tuned output will not map 1:1 to how Sunoh categorizes content into eCW Progress Note sections; rebuild templates and check offline/low-connectivity coverage that Freed supported.
Freed surfaces inline ICD-10 / CPT / E&M code suggestions on the note. eClinicalWorks already supports coding natively: its Clinical Rules Engine automatically drops/suggests the appropriate codes based on the documentation as the encounter is completed and feeds them into the integrated charge/claim workflow in the same EHR, and the embedded eva assistant can be invoked in-context during documentation. A practice on eCW can drop Freed's coding step and let the codes attach directly to the encounter it already documented, rather than exporting Freed's codes back. Keep eClinicalWorks for coding and billing; cut Freed.
- Warning: The native eCW capability is rules-based / E&M coding via the Clinical Rules Engine (plus eva); deep autonomous GenAI chart coding for eClinicalWorks is largely offered by third-party add-ons - do not assume the built-in engine matches a standalone AI coder before relying on it in place of Freed.
- Warning: Freed's CPT suggestions were historically flagged as beta; re-validate that eCW's suggested codes and E&M levels match the practice's prior billing, and confirm the CRE rules are configured for the specialty.
- Warning: Coding accuracy depends on the documentation reaching the chart - pair this with moving documentation into eCW via Sunoh.ai (see the ambient-clinical-documentation pattern) so the codes are derived from the same note.