Migrate from Epic Ehr to Suki.
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.
Suki and Epic both capture the visit ambiently and draft the structured note. A practice on Epic can retire the standalone Suki contract by turning the same workflow on inside the chart: enable Epic's in-app ambient documentation — Epic's native 'Art' / AI Charting, or the embedded partner ambient (DAX Copilot in Epic). Clinicians launch it from the Epic Notes activity and record the encounter via the Epic mobile apps (Haiku/Canto); the draft writes straight into the encounter for sign-off, and because it lands on the same chart it is immediately available to ordering and to Epic's level-of-service/coding — no separate Suki login or paste-back. Keep Epic as the system of record; cut the standalone Suki.
- Warning: Epic's ambient is a licensed add-on (Epic 'Art'/AI Charting, or DAX Copilot in Epic) and partner ambient vendors may carry their own per-clinician fee — confirm it is enabled and provisioned for the clinicians before cancelling Suki.
- Warning: Re-validate Suki's specialty note types and custom sections against Epic's SmartSection/SmartPhrase layout; the section mapping and any personalization must be rebuilt on the Epic side.
- Warning: Suki also runs natively inside Epic (Haiku/Hyperspace), so confirm you are cancelling the standalone Suki subscription and not an Epic-side entitlement before flipping the workflow to Epic's own ambient.
- Warning: Patient consent for ambient recording still applies — keep the consent step in the Epic-app workflow.
- Warning: Output is a draft, not auto-filed: clinician review and sign-off in Epic is required before the note enters the record.
Suki suggests visit codes (ICD-10, HCC, CPT, E/M) from the documented encounter; Epic does the same natively. A practice on Epic can drop Suki's coding by relying on Epic's own AI-for-operations coding (branded 'Penny'): Epic's Coding Assistance tees up diagnosis and procedure codes from each visit's clinical content, recommends Level of Service from the data entered during the visit (including free-text notes), and surfaces CDI query opportunities — and because it reads the encounter it will bill against, the codes attach straight to that chart's claim in Resolute. Let Epic generate and attach the codes during charting instead of pulling them from Suki. Keep Epic; cut the standalone Suki.
- Warning: Epic's revenue-cycle/coding AI ('Penny' / Coding Assistance) rides on the Epic revenue-cycle license — confirm Coding Assistance and Level-of-Service suggestions are enabled for the clinics before relying on them in place of Suki.
- Warning: Suki and Epic may suggest different codes; re-validate against Epic's NoteReader/coding output and have coders spot-check the first encounters after cutover to avoid amended encounters or denials.
- Warning: Autonomous ('no-touch') Epic coding via Penny is rolling out by specialty (e.g. ED, Radiology) — do not assume fully automated coding for every department on day one; clinician/coder review still applies.
- Warning: Suki's coding surfaces inside the documentation workflow (including its Epic integration), so confirm you are retiring the standalone Suki subscription, not an Epic-side entitlement.