Move your team from Abridge to Nabla.

Both Abridge and Nabla Copilot capture the patient-clinician conversation and produce a structured clinical note without manual typing. To migrate from Abridge to Nabla: provision Nabla Copilot accounts for each clinician (web app, iOS/Android, or Chrome extension) and connect to the EHR via Nabla Connect (iFrame embed); clinicians should start recording encounters using Nabla the same way they did in Abridge — begin recording at encounter start, end it when finished, and review the generated note before filing. To move the other direction (Nabla → Abridge): request an Abridge enterprise deployment through your health system's IT or the Abridge team, then install the Abridge tab inside Epic (Haiku on mobile, Hyperdrive/Hyperspace on desktop); workflow is the same — tap Start in Haiku at encounter start, review in the Abridge tab. Neither platform automatically migrates historical note drafts; past notes already filed in the EHR remain there and require no migration. Clinicians may notice slight differences in default note structure — Abridge outputs are aligned to assessment & plan sections typical in Epic, while Nabla defaults to configurable SOAP/APSO/WCC templates; both allow customization.

Abridge Inside embeds natively within Epic via Epic's Workshop co-development program, giving clinicians a dedicated Abridge tab in Haiku (mobile) and Hyperdrive/Hyperspace (desktop) without any context switching. Nabla Connect embeds via iFrame into any of 16+ supported EHRs and goes live in days rather than months. Migrating from Abridge → Nabla: have your EHR administrator work with Nabla's onboarding team to activate Nabla Connect for your EHR; for Epic shops, configure the iFrame embed in Epic's App Orchard or via Nabla Connect's plug-and-play module; set up SSO/SAML/SCIM for single sign-on; validate that structured note export and chart push (vital signs, diagnoses, flowsheets) map correctly to your EHR templates before rollout. Migrating from Nabla → Abridge: Abridge Inside requires a formal co-development partnership with Epic; contact Abridge enterprise sales to begin the procurement and Epic coordination process — plan for a longer implementation timeline. In both directions, end-user training will be needed since the recording interface location changes (iFrame panel vs dedicated Epic Abridge tab).

Both platforms surface ICD-10 and HCC codes from the documented encounter. Abridge's revenue-cycle product is a dedicated product line with automatic E&M level calculation, real-time inpatient CDI, and a Care Signals risk-adjustment tool; all codes are anchored by Linked Evidence tracing each code back to the patient conversation. Nabla's medical coding surfaces ICD-10, HCC, and MCC suggestions alongside the generated note for clinician review, exposed in Copilot and via the Core API. Migrating from Abridge → Nabla: engage Nabla's Proactive Coding Agent (in-progress as of 2026-06-14) for CDI nudges; confirm with Nabla which coding features are GA versus roadmap before committing revenue-cycle workflows; code suggestions are clinician-reviewed rather than auto-submitted on both platforms. Migrating from Nabla → Abridge: contact Abridge enterprise sales to activate the revenue-cycle product line separately from the documentation product (it is a distinct offering); set up Linked Evidence so revenue-cycle codes can be audited back to the conversation; configure the Care Signals gap-identification workflow before visits if risk adjustment is a priority.

Both platforms handle multilingual encounters: Abridge officially supports 28 languages (including the 16 most-spoken U.S. languages such as Spanish, Tagalog, Vietnamese, Arabic, Korean, and Haitian Creole) and always outputs the note in English. Nabla supports 35+ languages and can output the note and patient summary in the patient's language rather than forcing English output. No data migration is needed between the two — multilingual support is configuration-free on both sides; clinicians simply speak in their patient's language and the note generates automatically. Migrating from Abridge → Nabla: verify your key languages appear in Nabla's language list before go-live; if your practice uses Nabla for non-English patient summaries, activate the patient-summary output and select the target language in Nabla Copilot settings. Migrating from Nabla → Abridge: confirm your required languages appear in Abridge's published 28-language list; note that Abridge's note output is English-only, so any workflows relying on non-English note output must be redesigned.

Both platforms let clinicians refine an AI-drafted note using plain-language instructions instead of manual text editing. In Abridge, Prompt Editing accepts free-form instructions such as 'Make the assessment more concise and make the differential explicit' or 'Add a Next Steps section below the A/P'; it can also fold in evidence-based reasoning from external sources like UpToDate using the same prompt-style workflow. In Nabla, Magic Edit accepts a typed direction or a preset option (e.g. correct the patient's gender, make a section more verbose/concise, or highlight specific encounter details) and regenerates the note section accordingly; it is also available via the Core API for developers. No migration of past refinement history is needed — each note's edit instructions are single-session and not persisted as saved prompts in either product. Teams switching directions should expect a different instruction vocabulary: Abridge prompts tend to be clinical-reasoning-framed (add a section, reference a guideline), while Nabla Magic Edit emphasizes tone/verbosity and field correction; train clinicians on the appropriate phrasing conventions for the target platform.

Both platforms auto-generate patient-facing documents from the encounter without separate clinician effort. Abridge produces a Patient Visit Summary (PVS) at roughly an 8th-grade reading level, generated in real time during the visit and accessible in a dedicated PVS tab at notes.abridge.com; the clinician copies it into the EMR to share with the patient. Nabla Copilot generates a plain-language patient summary and, additionally, a referral/addressing letter from the same encounter; both are selectable document outputs in the Copilot interface and can be translated into the patient's language. Migrating from Abridge → Nabla: no configuration is needed — select 'Patient Summary' and/or 'Referral Letter' as document outputs after recording; enable language translation in Copilot settings if non-English summaries are needed for your population. Migrating from Nabla → Abridge: the PVS appears automatically in the notes.abridge.com PVS tab during the encounter; train clinicians to copy/paste the PVS content into the patient portal or after-visit summary field in the EMR since Abridge does not auto-push the PVS to the chart.