Migrate from Epic Ehr to Nym 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.
Nym and Epic both read the finished chart and assign the billing/diagnosis codes; Nym does it as a standalone first-pass engine that posts codes back, while Epic does it natively on the system of record. A practice on Epic can retire the standalone Nym contract: turn on Epic's revenue-cycle coding (branded 'Penny' — AI for Operations). Penny's Coding Assistance tees up CPT/ICD-10 and recommends Level of Service from the same encounter documentation, and Epic's autonomous ('no-touch') coding completes straightforward sessions inside org-set guardrails and writes the codes straight onto the Resolute claim — no Nym export or post-back. Keep Epic (the system of record); cut Nym.
- Warning: Coverage parity is the real gate: Nym auto-codes many service lines (ED, urgent care, radiology, outpatient surgery, inpatient pro-fee, EM), but Epic's autonomous 'no-touch' coding launches first on Emergency Department and Radiology and expands by specialty over time — confirm Penny autonomous coverage matches Nym's live specialty mix before cancelling, or you re-create a manual backlog on the uncovered lines.
- Warning: Nym is itself an Epic Toolbox / Showroom app (Fully Autonomous Coding category) and connects to Epic via FHIR — the practice may be running Nym *through* Epic today, so disconnect the Nym FHIR/Toolbox integration and stop the data feed when you cancel.
- Warning: Penny autonomous coding is a licensed/enabled revenue-cycle capability — confirm it is turned on for the org (not just the assistive Coding Assistance) before retiring Nym.
- Warning: Re-validate any in-flight Nym coding suggestions against Epic's NoteReader / Penny output during cutover so encounters are not double-coded or dropped between the two engines.