Migrate from Epic Ehr to Fathom Health.
1 documentation-derived translation pattern — what carries over and what to watch for. Cited to the Feature Parity Map; the audit tells you whether the move is worth it.
Fathom and Epic both read the encounter documentation and produce the diagnosis/procedure codes. A practice already on Epic can retire the standalone Fathom contract and move coding into Epic's own revenue-cycle AI: turn on Epic's Coding Assistance, which 'tees up diagnosis and procedure codes based on clinical content for each visit', auto-suggests Level of Service from data entered during the visit (including free-text notes), and surfaces CDI query opportunities — all branded under Penny (AI and automation for the revenue cycle). Because Epic codes the same chart it will bill against and writes the codes straight onto the Resolute claim, there is no export-out/post-back loop the way a third-party engine like Fathom needs. For the high-volume service lines where Fathom delivered direct-to-bill automation, adopt Epic's autonomous ('no-touch') coding via Penny as it rolls out (announced beginning with Emergency Department and Radiology). Keep Epic (the system of record); cut Fathom.
- Warning: Epic autonomous / no-touch coding (Penny) was announced beginning with Emergency Department and Radiology and is launching in November 2026 — confirm it is live and licensed for the specific service lines before cancelling Fathom, otherwise Epic's built-in Coding Assistance only proposes codes for human coders rather than billing direct-to-bill the way Fathom did.
- Warning: Epic's Coding Assistance / Penny is part of the Epic revenue-cycle (AI for Operations) license — verify the org has it enabled rather than assuming it ships with the base EHR.
- Warning: Re-validate automation/accuracy on a sample before cutover: Fathom published encounter-level automation (~93%+ direct-to-bill, client case studies up to ~95.5% at ~98.3% accuracy); Epic's native coverage and accuracy on your specialties may differ, so do not assume parity on every chart type.
- Warning: Fathom also runs retrospective risk-adjustment (HCC/RAF) coding (node:fathom-health/risk-adjustment-coding); confirm Epic's coding/HCC workflows cover that retrospective use case before dropping Fathom if the practice relies on it.