Migrate from Nabla 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.
Nabla Copilot and Epic both listen to the visit ambiently and draft the structured note; a practice on Epic runs Nabla as a separate paid contract (~$119/provider/month) whose notes are pushed back into Epic via Epic's Ambient APIs. To retire that contract, turn on Epic's own in-chart ambient documentation — 'Art for Clinicians' / AI Charting, which uses Microsoft Dragon (DAX/Dragon Copilot) ambient capture and Epic Cosmos context to pre-populate the note directly in the encounter — and capture via Haiku/the Epic mobile app instead of the Nabla app. The draft lands in the same Epic note the clinician signs, so there is no separate Nabla login, transcript window, or export step. Keep Epic (the system of record); cut Nabla.
- Warning: Epic ambient ('Art' / AI Charting via Dragon Copilot/DAX) is a licensed AI add-on and the partner ambient vendor may carry its own per-clinician fee — confirm it is enabled and provisioned for your org before cancelling the Nabla subscription.
- Warning: Re-create Nabla's specialty templates (SOAP/APSO/WCC) as Epic note templates/SmartPhrases; Epic's draft styling and section structure will differ from Nabla's and needs clinician validation before go-live.
- Warning: Nabla also auto-suggests problems, diagnoses and vitals for Epic export — verify Epic's AI Charting plus NoteReader/coding cover those chart-update steps so nothing is lost when Nabla is removed.
- Warning: Export or settle any Nabla note history you must retain before the contract ends; Nabla retains no audio by default, so anything not already filed to Epic should be reconciled first.
Nabla surfaces real-time coding suggestions (ICD-10, HCC, MCC, with E/M and CDI nudges via its Proactive Coding Agent) alongside the generated note. Epic delivers the equivalent natively: its Coding Assistance / AI for Operations ('Penny') reads the same encounter documentation, tees up diagnosis and procedure codes, recommends the Level of Service from data entered during the visit (including free-text notes), and surfaces CDI query opportunities — then writes the codes straight onto that chart's Resolute claim. Because Epic codes off the note it will bill against, a practice can drop Nabla's coding layer: let clinicians document in Epic ambient and review Epic's code/LOS suggestions in-chart rather than reconciling a separate Nabla code list. Keep Epic, cut Nabla.
- Warning: Epic Coding Assistance / Penny is part of the Epic revenue-cycle license — confirm the coding and CDI modules are turned on for your org before relying on them in place of Nabla.
- Warning: Nabla's coding is partly roadmap (E/M and CDI compliance are stated as expanding); do a side-by-side period where Epic's NoteReader/Penny output is checked against the prior Nabla suggestions so coders trust the new source before Nabla is removed.
- Warning: If any downstream system consumed Nabla's FHIR-normalized ICD-10/LOINC export, re-point it to Epic's coded encounter data; the field shapes and code sets will not match Nabla's API one-to-one.