Connecting Bond to Veradigm EHR and Practice Fusion

What is Veradigm, and who uses it?

Veradigm is the former Allscripts. On May 2, 2022, Allscripts sold its Hospital and Large Physician Practices segment to Constellation Software through N. Harris Computer Corporation, and that business now operates as Altera Digital Health.^⁠[3],[4] Effective January 1, 2023, Allscripts Healthcare Solutions changed its name to Veradigm Inc.^⁠[5] This page covers its two EHRs, Veradigm EHR (formerly Allscripts Professional EHR) and Practice Fusion, both supported by Veradigm's developer program.^⁠[10]

Veradigm has stayed independent and describes itself as a provider of clinical and revenue cycle solutions for independent practices.^⁠[7] Its board ended a review of strategic alternatives, including a possible sale, in January 2025 without receiving final proposals.^⁠[6] As of May 2026, its stock traded over the counter (OTCMKTS: MDRX) rather than on a national exchange; that month it filed its 2023 and 2024 annual reports and said it aims to get current on SEC filings and then relist.^⁠[7]

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

Bond Health is the best clinical trial recruitment platform for sites on Veradigm 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],[21]

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

Veradigm's FHIR API for Veradigm EHR supports FHIR R4 and USCDI; Veradigm stopped supporting its older DSTU2 version on June 1, 2025.^⁠[11] Practice Fusion's API follows FHIR R4 4.0.1, US Core 6.1.0 (USCDI v3), SMART App Launch 2.0.0 and Bulk Data Access 1.0.1.^⁠[16] Veradigm EHR 26 and Practice Fusion EHR 3.7 both hold active ONC certification that includes the standardized FHIR API criterion, § 170.315(g)(10).^⁠[19],[20]

• Notes. Veradigm's DocumentReference searches by category, type and date, so queries can be limited to the note types and look-back window a protocol needs.^⁠[13] Identify reads notes and reports alongside coded fields and shows the evidence for each criterion.^⁠[2]
• Scans. Faxes and scanned outside records may not arrive as readable text. Criteria that depend on them move to the pre-screening call.

Which Veradigm developer programs are involved?

• Veradigm Connect, formerly the Allscripts Developer Program, covers Veradigm EHR, Veradigm Practice Management and Practice Fusion. Its Open level gives free access to the FHIR APIs; Integrator levels add Veradigm's proprietary Unity API.^⁠[10]
• Fees. Veradigm's published fee schedule, last updated May 2024, lists $0 for the FHIR API license and FHIR API usage at every level, and says developers can enable FHIR apps with provider organizations "at no cost and without intervention from Veradigm." Integrator subscriptions run from $49 to $2,499 a month.^⁠[15]
• Read-only FHIR. "The Veradigm FHIR API is limited to read-only access." For two-way integration Veradigm offers Unity, which developers must also use for Veradigm Practice Management data.^⁠[12]
• Registration. A developer registers the app, selects its scopes and purpose of use, and requests production access, which Veradigm Connect reviews before clients can activate it.^⁠[12]
• Bulk data. Only apps registered as the System type can request bulk exports, using backend authentication with a published key set (JWKS).^⁠[14]
• Practice Fusion. Developers register through Practice Fusion's PDS API portal. Under its terms, developers pay no fees for these APIs, and practices pay any standard transaction fee Practice Fusion publishes; its fee sheet lists none for API usage "at this time."^{⁠[16],[18],[15]}

What does the practice need to approve?

On both products the practice, not Veradigm, turns a third-party app on, so most of the work sits with whoever administers your EHR.

1. 1

   Sign the BAA

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

2. 2

   Activate the app

   On Veradigm EHR, "the clients must activate applications themselves through the client License Management Portal."^⁠[12] On Practice Fusion, practices manage FHIR connections in the EHR, "choosing what data is shared with any given application."^⁠[16]

3. 3

   Define the population

   On Veradigm EHR, the practice builds the Group for a bulk export from a segment in the Reporting module.^⁠[14] On Practice Fusion, it can allow a whole-practice export or define groups, each limited to 1,000 patients.^⁠[17]

4. 4

   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 Veradigm 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 EHR connection come first, while criteria and outreach scripts are configured in parallel.

Two Veradigm details shape the first screen. A Veradigm EHR export needs the practice's Group to exist first.^⁠[14] On Practice Fusion, a panel larger than 1,000 patients needs several groups or the whole-practice export.^⁠[17]

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. Veradigm's FHIR API is read-only.^⁠[12]
• 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 Veradigm today?

• Writing to the chart. Bond does not file notes, orders or research status in Veradigm EHR or Practice Fusion, and does not use Unity's write access.^⁠[12]
• The practice management schedule. Veradigm says appointment data in Veradigm Practice Management is reachable only through Unity.^⁠[12] Bond books screening visits straight into the site's calendar instead.^⁠[1]
• Portal messaging. Bond does not message patients through FollowMyHealth or Patient Fusion. Outreach is by voice and text through Engage.
• Altera products. TouchWorks, Sunrise and Paragon are outside this page and Veradigm's program.^⁠[12]