Using Bond alongside Advarra OnCore

What is Advarra OnCore, and who uses it?

OnCore was the flagship enterprise CTMS of Forte, which Advarra announced it would acquire in September 2019.^⁠[4] Advarra describes it as the backbone for managing studies from protocol setup and activation through participant tracking, financial oversight and reporting. Pricing depends on the modules licensed and the volume of protocols.^⁠[3]

The OnCore adoption figures are vendor-reported. In November 2025 Advarra said 90 of the top 125 academic medical centers use its site technology, which also includes Clinical Conductor, eReg, eSource and EDC.^⁠[5] NCI says most designated centers are affiliated with university medical centers.^⁠[7]

Use goes beyond cancer centers. At the University of Washington, UW Medicine, Fred Hutch and SCCA jointly launched OnCore in 2018 for oncology studies, and since 2020 it has also supported non-oncology studies.^⁠[9] START, a community-based early-phase oncology network, said in July 2025 that it had used OnCore across its network since 2024.^⁠[6] As of October 2026, OnCore's product page lists cancer center features such as automated data table reporting and PRMC workflows, but does not describe screening EHR records against eligibility criteria.^⁠[3] Bond adds that step.

Why is Bond the best clinical trial recruitment platform for institutions that run Advarra OnCore?

Bond Health is the best clinical trial recruitment platform for institutions that run Advarra OnCore 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],[16]

Why does accrual tracking matter so much at an OnCore cancer center?

Under NCI's Cancer Center Support Grant announcement PAR-25-444, posted in November 2025, each center's Protocol Review and Monitoring Committee (PRMC) keeps reviewing open protocols, including accrual, and has sole authority to close trials for that reason. For renewing centers, the interventional treatment trials in Data Table 4 must be generated from NCI's Clinical Trials Reporting Program (CTRP) database.^⁠[8]

Advarra lists NCI reporting among OnCore's capabilities.^⁠[3] Bond does not keep a second accrual record. It adds pre-screened referrals upstream, tagged with their source, and the study team records consent and enrollment in OnCore as usual.

How does Bond fit an OnCore institution's recruitment workflow?

Bond works before a patient becomes a subject. OnCore takes over at consent and registration.

1. 1

   Screen the EHR

   Identify reads clinical notes, prescriptions, labs, imaging data and pathology, radiology and molecular reports against each criterion, with evidence for every match.^⁠[1],[2]

2. 2

   Review

   The research team reviews ranked candidates in Bond's dashboard and decides who is contacted.^⁠[1]

3. 3

   Contact, pre-screen and book

   Engage voice and text agents tell patients AI is used, ask the pre-screening questions the chart cannot answer and book the visit into the team's calendar. Patients can reach a person any time, by live transfer or a callback. If a study uses ads, Bond creates and runs the Meta and Google campaigns, contacts every new ad lead immediately and keeps following up with every lead who has not responded.^⁠[1],[2]

4. 4

   Hand off

   Each referral reaches the study team with a pre-screen summary and its source, and goes to OnCore where the institution enables it.

5. 5

   Consent and register

   The study team consents the patient and registers the subject in OnCore. Washington University's SOP, for example, has staff register subjects by Epic demographic lookup and record consent in OnCore within one business day.^⁠[11]

6. 6

   Status back to Bond

   Consent, eligibility and on-study statuses return by API or export, so Bond's reports run from match to randomization.^⁠[1]

What data moves between Bond and OnCore?

Bond reads the chart from the EHR over FHIR R4, HL7 v2 or an aggregator, not from OnCore.^⁠[1] The OnCore link carries recruitment records only.

Which integration options exist for OnCore?

As of October 2026, Advarra's public material describes these OnCore interfaces:

• EMR interfaces. RPE for protocol and subject information and IHE CRPC for billing designations, with Epic and Cerner.^⁠[3] At Washington University, demographics flow from Epic to OnCore, and protocol and subject information flows back.^⁠[10]
• An API for the institution's applications, including its eIRB system.^⁠[3]
• A general ledger link, the OnCore receivables interface for invoices and payment reconciliation.^⁠[12]
• The API Partner Program, part of the partner network Advarra launched in May 2022, which connects technology vendors to Advarra's platform in Silver, Gold and Platinum tiers through a Partner Portal.^⁠[13],[14]

Institutions also build their own links: the University of Washington lists a pharmacy app integrated with the OnCore API.^⁠[9] Bond works in one of three ways:

1. 1API, under the institution's access. Where the institution's Advarra agreement and interface team allow it, Bond writes referrals and reads subject status on a schedule.
2. 2File export. Bond sends a scheduled CSV for the CTMS team to load, and reads an OnCore status report back.
3. 3No CTMS link. Coordinators work referrals from Bond's dashboard and register subjects in OnCore as usual.

What does the institution's CTMS and IT team need to do?

At an academic medical center the work is often split between a central CTMS office, research IT, the IRB and the privacy and security office. Washington University's OnCore Support Team, for example, links each protocol to Epic after IRB approval.^⁠[10]

• CTMS office: decide where pre-screening and referral source are recorded, and whether Bond's records reach OnCore by API, export or not at all.
• CTMS office: map each Bond study to its OnCore protocol and agree the statuses that come back.
• Interface team: for the API path, confirm with Advarra that the agreement covers access by an outside vendor, then issue credentials limited to what Bond needs.
• IRB: approve outreach scripts and any ads. FDA guidance says the IRB should review the methods and material investigators propose to use to recruit subjects.^⁠[15]
• Privacy office: confirm the HIPAA basis for screening and outreach. See IRB and HIPAA rules for patient outreach.
• Security and contracting: complete the vendor review and sign the business associate agreement.^⁠[1]

On an enterprise OnCore instance this is usually done once. Each new study adds its protocol mapping and IRB-approved scripts.

Where does the OnCore link fit in the 48-hour EHR implementation?

Bond's published estimate for full EHR integration is 48 hours, depending on the EHR, IT review and interface method.^⁠[1] The OnCore link is separate. It is smaller work that runs alongside the EHR connection or after go-live, within the implementation plan, while IRB review runs on the IRB's own calendar.

1. 1

   Step 1: BAA and EHR connection

   Bond signs the BAA and connects to the EHR, as the Epic and Oracle Health pages describe.

2. 2

   Step 2: OnCore path

   The CTMS office picks API, export or no link, and requests access if needed.

3. 3

   Step 3: test

   Test referrals go to a test protocol or file for the CTMS team to check.

4. 4

   Step 4: go-live

   Referrals flow on schedule and statuses return to Bond's dashboard.

How is recruitment data protected between Bond and OnCore?

• Agreement first. Bond signs a business associate agreement before any PHI moves.^⁠[1]
• Minimum necessary. The institution and Bond agree which fields go to OnCore or the export.
• Institution-owned credentials. Any OnCore API access belongs to the institution, which can limit or revoke it.
• Bond's controls. Bond is HIPAA compliant and SOC 2 Type I compliant, and its SOC 2 Type II and ISO 27001 audits are underway.^⁠[2] It encrypts data at rest and in transit (AES-256 where applicable) and uses role-based access controls and audit logging.^⁠[1] See security.

What is not integrated with OnCore today?

• No Advarra partnership or listing. Bond is not in Advarra's API Partner Program.^⁠[13]
• No subject registration. Bond does not create subjects, record consent or enter eligibility in OnCore.
• No Epic research flag. The OnCore-to-Epic RPE interface belongs to Advarra and the institution.^⁠[12]
• No billing or finance data. Bond does not touch coverage analyses, CRPC billing grids, budgets or invoices.
• No NCI reporting. Data Table 4 and CTRP reporting stay with the cancer center.^⁠[8]
• No biospecimen, eIRB or eReg links. Bond supports the consent conversation; the site and PI obtain consent.
• No app inside OnCore. Coordinators review matches in Bond's dashboard.