Migrate from Freed to Epic Ehr.
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.
Freed and Epic both capture the visit ambiently and draft a structured SOAP note for the clinician to review. A practice already on Epic can retire the standalone Freed subscription and document inside the chart instead: turn on Epic's in-app ambient documentation - either Epic's native clinician AI 'Art' / AI Charting, or an embedded partner (DAX Copilot in Epic, Abridge in Epic) - which records in the Epic Haiku/mobile app, pulls live chart context, and writes the draft straight into the Epic encounter for sign-off. Because the note lands in the same record Epic already uses for orders, coding, and billing, there is no second login and no copy-paste from Freed's 'push to EHR' step. Keep Epic as the system of record; cut Freed.
- Warning: Epic ambient is a licensed/enabled capability: native Art (AI Charting) must be turned on for the org, and partner ambient (DAX Copilot / Abridge in Epic) typically carries its own per-clinician fee - confirm one is live before cancelling Freed.
- Warning: Freed works offline and as a fully standalone app; the Epic-embedded path assumes the clinician is working in Epic (Haiku/mobile or desktop), so validate coverage for low-connectivity or non-Epic settings before cutting over.
- Warning: Re-validate specialty note templates and SOAP formatting in Epic - Freed's specialty-tuned output will not map 1:1 to Epic's note types, so rebuild any custom templates the practice relied on.
Freed surfaces inline ICD-10 / CPT / E&M code suggestions on the generated note; Epic produces the same suggestions natively from the visit documentation. A practice on Epic can drop Freed's coding step and rely on Epic's Coding Assistance, which 'tees up diagnosis and procedure codes based on clinical content for each visit' and automatically suggests a Level of Service from the data entered during the visit (including free-text notes), feeding straight into Resolute billing on that same chart. Because Epic codes the encounter it already documented, there is no export/paste-back of Freed's codes. Keep Epic for coding and billing; cut Freed.
- Warning: Epic Coding Assistance / Level of Service and the autonomous revenue-cycle automation are part of Epic's AI for Operations ('Penny') and the Resolute/revenue-cycle license - confirm the coding modules are enabled for the org before relying on them in place of Freed.
- Warning: Freed's CPT suggestions were historically flagged as beta; do not assume parity - re-validate that Epic's code and E&M / Level-of-Service output matches the practice's prior billing before cutting Freed.
- Warning: Coding quality in Epic depends on the documentation reaching the chart; if the note is still drafted in a standalone scribe, codes may differ - pair this with moving documentation into Epic (see the ambient-clinical-documentation pattern).