Does Nabla Work With NextGen?

Two architectures, and you should know which one you are being quoted.

The bundled route is NextGen Ambient Assist. NextGen's June 2024 release describes capture through the NextGen Mobile application, a note produced within about 30 seconds of the visit ending, provider review and approval on the phone, and the approved note integrating into NextGen Enterprise. The same release describes Spanish language capture, specialty models for psychiatry, cardiology, paediatrics and primary care, and support for diagnostic and order codes inside the note. NextGen Office Ambient Assist is the equivalent for the cloud product aimed at smaller practices. In this model the integration is NextGen's problem, not yours: there is no API application to onboard because the vendor of the EHR is the vendor of the scribe.

The direct route is a Nabla integration built on NextGen's published interfaces. NextGen runs an API Developer Program with three tracks. Patient Access APIs are free to develop against, the Open Access track covers a client building for its own use with no fee stated, and the API Distributor Program is the commercial track with sandboxes and a statement that fees "may have associated fees based on the scope of data needs and/or other requirements". NextGen documents FHIR R4 and SMART App Launch for certified access, and NextGen Connect, the engine formerly called Mirth, for HL7 v2 and document interfaces. Nabla's site also promotes Nabla Connect, launched in late 2025, as a way for an EHR vendor to embed Nabla rather than a way for a practice to connect it, so do not mistake that for a self service integration you can switch on.

Which route applies is a commercial decision and a technical one at once. The bundled product is NextGen's to configure and support. A direct Nabla deployment on NextGen needs Nabla to hold a place in the Distributor Program or to have built for your organisation under Open Access, and either way you should get the track and the fee position in writing. Our EHR integration questions list is built for exactly this conversation.

On the bundled route, the clinician opens the encounter in NextGen Mobile, records the conversation, reviews a drafted note on the phone, edits it and approves it. The approved note then lands in the NextGen Enterprise encounter. NextGen states that the product supports diagnostic and order codes, which means the note is not just prose: parts of it are intended to populate structured elements. That is useful and it is also where your compliance review should focus, because suggested codes touch billing.

On the direct route, Nabla's public material describes structured note export into EHR fields and templates rather than a single text block, plus pre visit chart context. What that means on NextGen specifically, field by field, is not published. Not published. Checked September 2026. Ask for a field map: which NextGen template sections receive text, whether the note lands as a signed document or a draft, and whether problems, medications and orders are written discretely or left for the clinician to enter.

The time saving figures are vendor supplied and they disagree with each other. NextGen's 2024 release says up to two hours of documentation time per day; other NextGen pages have said two and a half; press coverage has quoted lower. Treat all of them as ceilings and measure your own baseline first. The ROI calculator exposes its assumptions so you can substitute your own encounter counts and your own pre pilot documentation time.

Different things depending on the route, and this is the point at which bundled and direct stop being interchangeable.

• Business associate agreement. On the bundled route your BAA is with NextGen, and NextGen holds the subcontractor relationship with Nabla. Ask NextGen to name Nabla as a subcontractor in writing and to state where audio and transcripts are stored and for how long. On the direct route the BAA is with Nabla and NextGen is not a party to the AI question at all.
• Device policy. Capture is on the clinician's phone through NextGen Mobile. Your mobile device management, screen lock and lost device procedures now cover an audio recording workflow, whether or not you had thought of them that way.
• Access path. On the direct route, ask which NextGen developer track Nabla is on, whether the integration uses FHIR R4 with SMART launch, and whether any part of it depends on a NextGen Connect interface that somebody in your organisation has to maintain.
• Model training and retention. Ask both parties whether your data trains shared models and what is deleted at termination. The HIPAA and AI compliance page sets out the questions in order.
• Coding oversight. If diagnostic and order codes are suggested, your compliance officer needs a documented human review step before anything reaches a claim.

The HTI-1 rule adds a further item on the bundled route. Predictive decision support shipped inside certified health IT carries transparency obligations on the developer, so NextGen should be able to hand your governance committee the source attribute information for Ambient Assist's coding suggestions. Ask for it before go live rather than after an audit query.

The first gap is feature lag between the two routes. Nabla ships to its direct customers on its own cadence. NextGen ships Ambient Assist on NextGen's cadence. Nobody publishes how far apart those are, and a feature you saw on a Nabla demo may not be in the bundled product for months. Ask NextGen for the release notes of the last four Ambient Assist updates and compare them with Nabla's changelog.

The second is the field map on the direct route, discussed above. The third is developer track and fees: NextGen's own wording leaves room for a charge to appear on the Distributor track, and it is reasonable to ask both NextGen and Nabla who pays it and whether it is in your quote.

The fourth is marketplace presence. A direct Nabla integration is not listed on the NextGen API Marketplace as of September 2026, so you are relying on Nabla's statement and on reference customers rather than on a NextGen validated listing. Ask for two named NextGen practices running the direct integration in your specialty and your NextGen product, Enterprise or Office, and call them.

The fifth is specialty coverage. NextGen sells into specialty groups, and NextGen names four specialty models for Ambient Assist. If yours is not one of them, ask what a note looks like in your specialty before the pilot, and read our scribe comparison for how other vendors cover it.

Ask both NextGen and Nabla for a quote, and ask each of them the same list.

• Which route are you quoting, bundled Ambient Assist or direct Nabla, and which NextGen product, Enterprise or Office?
• On the direct route, which NextGen developer track is the integration on, and who pays any NextGen fee?
• Which NextGen template sections and discrete fields does the note populate, and is it saved as draft or signed?
• What happens to audio and transcript after the note is approved, and how long is it retained?
• Who do we call when a note is wrong, and what is the response commitment?
• What is the renewal uplift cap, and can we move from bundled to direct, or back, without a data migration?
• Which of the specialty models cover our specialties, with a sample note for each?

For the money question, Nabla pricing sets out what is published and what is not, and the small practice buying guide covers the contract terms that matter more than the monthly rate.

A NextGen group choosing Nabla is really choosing between two sellers of one engine, and neither seller has an incentive to lay the two routes side by side. NextGen would rather you take the bundle. Nabla would rather you sign direct. Both are reasonable products; the question is which contract, which support path and which integration architecture fits a multi site specialty group with your interface estate.

Our vendor selection engagement runs both quotes through the same scorecard, checks the field map and the developer track in writing, calls the references, and gives your partners or your board a one page recommendation with the trade offs stated. If you already know the route and want the rollout sequenced across sites and specialties, the deployment roadmap is the right service. We take no commission from Nabla, NextGen or anyone else. Book a call to talk it through.