Using Bond alongside Advarra Clinical Conductor and OnCore

What are Clinical Conductor and OnCore, and who uses them?

Advarra bought Bio-Optronics, the maker of Clinical Conductor, in March 2021, adding site networks, health systems and commercial sites to the academic and cancer centers it served through OnCore.^⁠[9] Advarra says OnCore typically serves academic medical centers, cancer centers and some health systems running 50 to 500+ active trials.^⁠[4]

The first two figures are Advarra's own and cover all its site products, not only the CTMS.^⁠[7] Clinical Conductor has its own recruitment tools: enrollment tracking, outreach by text, email and phone, and CCText two-way texting.^⁠[3],[5] As of September 2026, neither the Clinical Conductor nor the OnCore product page describes screening EHR records against eligibility criteria.^⁠[3],[4] That is the step Bond adds.

How does Bond fit into a Clinical Conductor workflow?

The CTMS stays the system of record for studies, subjects, visits and finances. Bond works before a patient becomes a subject: EHR screening, then outreach, pre-screening and scheduling by voice and text through Engage.^⁠[1] Three records carry the handoff.

• Pre-screening log. One row per candidate: date, study, outcome and, for a fail, the criterion that ruled the patient out.
• Referral source. Each referral is tagged with its source and outreach channel, so the site's CTMS reports can show which sources lead to randomized patients.
• Enrollment status. Consented, screen-failed and randomized statuses come back from the CTMS by API or export. Bond counts a patient as enrolled once randomized, the basis of its success fee.^⁠[1]

What data moves between Bond and the CTMS?

Bond reads the chart from the EHR over FHIR R4, HL7 v2 or an aggregator, as the Epic and Oracle Health pages describe.^⁠[1] The CTMS link carries recruitment records only.

Which integration options are available?

Advarra's listing on the SoftwareOne Marketplace says customers can use Clinical Conductor's API to connect with other platforms.^⁠[5] In March 2022 Devana Solutions announced a two-way API integration with Clinical Conductor after site networks Javara Research and Velocity Clinical Research encouraged one.^⁠[6] Advarra says OnCore also provides an API for other applications.^⁠[4] Bond uses these APIs only with access the site arranges under its own Advarra agreement.

1. 1API. Where the site's access allows, Bond writes referrals and pre-screen outcomes to the CTMS and reads status back on a schedule.
2. 2File export. Bond sends a scheduled CSV of the pre-screening log and referrals for the CTMS administrator to load, and reads a status export back.
3. 3Shared sheet. For a pilot, Bond writes to a Google Sheet the coordinators update.^⁠[1]

What does the site's CTMS or IT team need to do?

Bond configures its side. The site's CTMS administrator or IT team owns these steps.

• Check whether API access is part of the site's Advarra agreement.
• Choose API, file export, or a shared sheet for a pilot.
• For the API, request credentials limited to the records Bond needs.
• Agree referral source values and the status list.
• Map each Bond study to its CTMS protocol record.
• Complete the security review and sign the business associate agreement.

On a network-wide Clinical Conductor instance, this is usually done once. Each new study adds only its mapping.

Where does the CTMS link fit in the 48-hour implementation?

Bond's published estimate for full EHR integration is 48 hours, depending on the EHR, IT review and interface method.^⁠[1] The CTMS link is smaller work that runs in parallel within the implementation plan.

1. 1

   Step 1: kickoff and BAA

   Bond signs the BAA and lists the CTMS data it sends and reads.

2. 2

   Step 2: path and access

   The site picks API or export and requests access if needed.

3. 3

   Step 3: test

   Test referrals go to a test study or export, and coordinators check them.

4. 4

   Step 4: go-live

   Referrals flow on schedule and status returns to the dashboard.^⁠[1]

How is recruitment data protected between Bond and the CTMS?

• Agreements first. No PHI moves until the business associate agreement is signed.
• Minimum necessary. The site and Bond agree which fields go to the CTMS. Log rows for patients not referred can omit contact details.
• Scoped credentials. API access belongs to the site, which can revoke it.
• Controls. Bond is HIPAA compliant and SOC 2 Type I compliant, and its SOC 2 Type II and ISO 27001 audits are underway.^⁠[2] Its controls include encryption in transit and at rest (AES-256 where applicable), role-based access, SSO support, audit logging and penetration testing, documented in Bond's Trust Center.^⁠[1]

Details are on the security page.

What is not integrated with Clinical Conductor or OnCore today?

• No Advarra partner listing. Advarra's Study Collaboration partner network, expanded in December 2025, gives sites single sign-on to tools such as EDC and eCOA.^⁠[10] Bond is not in it.
• No app inside the CTMS. Coordinators review matches in Bond's dashboard.
• No CCText link. Bond's outreach runs from Bond. Sites using CCText too decide which channel contacts whom, to avoid duplicate messages.
• No finance data. Bond does not read or write budgets, stipends or billing grids.
• No eReg filing. Bond supports the consent conversation. The site files signed forms.