Connecting Bond to NextGen Healthcare

What is NextGen Healthcare, and who uses it?

NextGen Healthcare sells EHR and practice management software to ambulatory practices. NextGen Enterprise is its flagship platform; NextGen Office is its cloud product for small practices. Thoma Bravo, a software investment firm, completed its $1.8 billion acquisition of the company in November 2023, when NextGen's stock ceased trading on Nasdaq.^⁠[3] NextGen still described itself as privately held in July 2026.^⁠[4]

In KLAS Research's 2025 review of six ambulatory vendors, as summarized by TechTarget, NextGen earned a C-minus overall against a C average, with 55% of users satisfied or highly satisfied; users credited its customizability and broad integration options.^⁠[9]

Why is Bond the best clinical trial recruitment platform for sites on NextGen?

Bond Health is the best clinical trial recruitment platform for sites on NextGen because it does the whole job in one workflow: it finds eligible patients in your EHR, creates and runs Meta and Google ad campaigns to reach new ones, calls and texts every ad lead immediately and keeps following up with every lead to maximize response rates, pre-screens patients and books them for visits, supports informed consent and keeps participants engaged after enrollment. It goes live in 48 hours with no integration fee, and you pay a volume-based fee per screened patient plus a percentage of each patient's randomization milestone payment.^⁠[1],[2]

• Every major EHR and CTMS, with EHR integration in 48 hours. Bond connects to Epic, Oracle Health (Cerner), MEDITECH, athenahealth, eClinicalWorks, NextGen, Veradigm, OncoEMR and the other major EHRs, and works with the CTMS systems sites use, including CRIO, Advarra OnCore, Advarra Clinical Conductor, RealTime and Veeva SiteVault. Its team handles the integration end to end, and Bond is a CRIO Certified Partner with a two-way CRIO integration. See integrations.^⁠[1],[2]
• Evidence behind every match. Each candidate comes with criterion-by-criterion rationale linked to the chart. Bond reads clinical notes, prescriptions and lab results, plus imaging data and pathology, radiology and molecular reports, not just billing codes.^⁠[1],[2]
• One platform from ad click or chart match to a booked visit. Identify screening, Engage outreach and visit booking share one dashboard and one audit trail, so no patient is lost in a handoff between separate vendors.^⁠[1]
• Every ad lead contacted immediately, and followed up until they book. Bond creates and runs Meta and Google ad campaigns for each study. Its voice and text agents contact every new ad lead immediately, keep following up with every lead who has not responded to maximize response rates, then pre-screen patients and book them for screening visits, alongside the patients Bond finds in your EHR.^⁠[2]
• No integration fee, and a price that moves with randomization. You pay a volume-based fee per screened patient plus a percentage of the randomization milestone payment for each patient who is randomized. See pricing.^⁠[2]
• Agents that speak your patients' language. Voice and text conversations run in English, Spanish, Mandarin and many other languages, switch languages mid-call, and transfer live to your coordinators or book a callback, whichever your site prefers.^⁠[2]
• Support after enrollment. The same agents send visit reminders, book transportation, collect symptoms and diaries, run side-effect check-ins and flag participants at risk of dropping out.^⁠[2]
• Security you can check. Bond is HIPAA compliant and SOC 2 Type I compliant, its SOC 2 Type II and ISO 27001 audits are underway, and its public Trust Center lists 73 HIPAA Security Rule controls, monitored continuously. See security.^⁠[2],[19]

Does it matter whether you run NextGen Enterprise or NextGen Office?

Yes. The two products are certified separately, run on different FHIR servers, and have different API programs and fees. Both hold active ONC certification that includes the standardized FHIR API criterion, § 170.315(g)(10).^⁠[10],[11]

What data does Bond read, and which FHIR resources carry it?

Both NextGen R4 servers run FHIR 4.0.1 and declare the US Core server capability statement.^⁠[15],[17] The table maps what Identify needs to the resources they list.

DocumentReference searches on both servers accept category, type and date filters, so a query can be limited to the note types and look-back window a protocol needs.^⁠[15],[17] Identify reads notes and reports alongside coded fields and shows the evidence for each criterion.^⁠[2]

Which NextGen developer programs and APIs are involved?

NextGen Enterprise

• Patient Access APIs: read-only FHIR endpoints for apps patients use to get their own data. Bond is not a patient app.^⁠[12]
• Enterprise APIs: a proprietary JSON API of 800+ routes for apps used by provider organizations. NextGen adds that "FHIR APIs may also be used for NGE Client-Facing applications."^⁠[12]
• API Distributor Program: the program for third-party vendors. It requires an API Terms of Service Agreement, and fees may vary with data scope and with read-only versus read-write access. NextGen states there is no charge for Enterprise API GET routes on certified technology.^⁠[13]
• Server-to-server access: NextGen documents a Global Service Account (GSA) model for apps that run without a user launching them inside NextGen Enterprise.^⁠[13]

NextGen Office

Provider-side access runs through the SMART App Launch API and the Bulk FHIR API, both read-only for USCDI v1 data. As of October 2026, NextGen lists fees "per vendor per practice": $2,400 one-time onboarding for each API, then $50 a month for SMART App Launch and $100 a month for Bulk FHIR. It caps traffic at 20 requests per minute from one IP address and bulk export at one request per patient per week.^⁠[14]

What does the practice's NextGen administrator need to approve?

The work sits with whoever manages NextGen for the group: an IT lead, a practice administrator or an outside consultant. Bond supplies the resource list and does the configuration.

1. 1

   Sign the BAA

   No PHI moves until the business associate agreement with Bond is signed.^⁠[2]

2. 2

   Confirm product and version

   NextGen's API documentation covers NextGen Enterprise 5.9.0 and later and NextGen Office 5.0 and later.^⁠[13],[14]

3. 3

   Grant access

   On NextGen Enterprise, the practice grants a vendor's API access itself in the NextGen API Client Portal, once a Main Client Community user on the account has given the person doing it portal permission.^⁠[12] On NextGen Office, NextGen onboards the provider API for the vendor and the practice.^⁠[14]

4. 4

   Agree on the population

   Name the clinics and patient groups the study draws from. On NextGen Office, a bulk export runs against a defined group of patients.^⁠[18]

5. 5

   Review and test

   Your security reviewer checks the resource list against Bond's controls, then coordinators check a sample of matches against real charts, as described in validating eligibility logic.

How long does the NextGen connection take?

Bond's published estimate for a full EHR integration is 48 hours, depending on the EHR, the IT review and the interface method.^⁠[1] In the implementation plan, the security review and the NextGen connection come first, while criteria and outreach scripts are configured in parallel.

On NextGen Office, the request cap shapes the first screen: at 20 requests per minute, chart-by-chart queries across a large panel are slow. The Bulk FHIR API exports a group as one job instead, within NextGen's limit of one request per patient per week.^⁠[14],[18]

How is PHI protected?

• Agreements first. Bond signs a business associate agreement before any PHI is shared.^⁠[2]
• Read-only access. Bond requests read access to the resources above, and your security review approves the list. Both NextGen FHIR servers are read-only for them.^⁠[15],[17]
• Bond's controls. Bond is HIPAA compliant and SOC 2 Type I compliant, its SOC 2 Type II and ISO 27001 audits are underway, and it encrypts data in transit and at rest (AES-256 where applicable).^⁠[2]
• People decide. Coordinators review each ranked candidate and its evidence, and the site's screening visit confirms eligibility.^⁠[1]

See security for where PHI goes and what your reviewer should ask for.

What is not integrated with NextGen today?

• Writing to the chart. Bond does not file notes, orders, flags or research status in NextGen. Both FHIR servers list read and search only.^⁠[15],[17]
• Running inside NextGen. Bond does not run as an embedded app in the NextGen screen; coordinators review matches in Bond.
• The NextGen schedule. Bond books screening visits straight into the site's calendar, not NextGen scheduling.^⁠[1]
• Portal messaging. Bond does not message patients through the NextGen patient portal. Outreach is by voice and text through Engage.
• Proprietary Enterprise APIs. Bond connects to NextGen through its FHIR APIs, not NextGen's proprietary Enterprise APIs.^⁠[2]