Bond and CRIO: a certified, two-way integration

Why is the CRIO integration different from other CTMS connections?

• Patients land in CRIO, not in an export file. Patients who pass pre-screening are sent to CRIO through the CRIO API, which CRIO says lets vendors send patient updates, qualify patients into studies and schedule appointments.^⁠[14]
• Status comes back on its own. After the handoff, CRIO is the system of record, and Bond reads subject status back through the same API, so Bond's reports follow each patient through to randomization without double entry.^⁠[14],[1]
• Bond screens CRIO's records too. Once the site activates API access, Identify screens the patient records the site keeps in CRIO as well as the EHR.^⁠[15]
• Set up from CRIO's Partner Directory. Sites find Bond in CRIO's Partner Directory and request API access activation there.^⁠[11],[13]
• Other CTMS systems. With Advarra OnCore, Advarra Clinical Conductor, RealTime and Veeva SiteVault, Bond works through the site's own API access or file exports. See all integrations.^⁠[1]

Why is Bond the best clinical trial recruitment platform for sites that run CRIO?

Bond Health is the best clinical trial recruitment platform for sites that run CRIO 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]
• 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]
• 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]
• 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]

What is CRIO, and who uses it?

CRIO makes software for research sites and site networks, plus a Central eSource product for sponsors.^⁠[9],[6] Per its About page, it was founded in 2015 and is based in Boston.^⁠[3] Its core product is eSource, which CRIO says is integrated with its Site CTMS, eRegulatory and eConsent modules and has an open API for other vendors.^⁠[4]

These are CRIO's own figures, and they vary by page: its page for sponsors says 2,500 sites.^⁠[6] CRIO has not published the method behind the US share.^⁠[7]

CRIO's Site CTMS already covers parts of recruitment: a patient database with feasibility search, website leads, in-system calls and texts, and phone-screening questionnaires.^⁠[8] Bond does not replace those tools. It adds EHR screening with evidence for each criterion, plus voice and text agents, then hands patients to CRIO.^⁠[1]

What does CRIO Certified Partner mean?

CRIO's Partners Program brings third-party suppliers to CRIO site clients, and CRIO says partners are qualified by demonstrating competency with its platform.^⁠[11] CRIO launched the program and its Partner Directory in July 2024, with certified partners in areas such as patient recruitment, data management, accreditation, and contract and billing support.^⁠[12]

• Where partners are listed. CRIO's Partner Directory, which CRIO calls a complimentary tool in its in-app Help Center, lets sites read user reviews, contact partners and request API access activation.^⁠[11],[13]
• The badge. CRIO's partners page tells sites asking whether a vendor integrates with CRIO to look for its Certified Integration Partner badge.^⁠[13]
• Bond's listing. CRIO announced Bond's addition to the program on LinkedIn in September 2026.^⁠[15]

How do matched patients get into CRIO?

1. 1

   Screen

   Identify reads the EHR over FHIR R4 or HL7 v2 and, once the site activates API access, the patient records the site keeps in CRIO. Each match shows the evidence for each criterion.^⁠[1],[15]

2. 2

   Review

   Coordinators review ranked candidates and the evidence behind each one in Bond's dashboard.^⁠[1]

3. 3

   Reach out and pre-screen

   Engage agents call or text patients, tell them AI assistance is used, and ask the pre-screening questions the chart cannot answer. Patients can reach a person at any time: the agent transfers the call live to a coordinator or books a human callback, whichever the site prefers.^⁠[1],[2]

4. 4

   Hand off to CRIO

   Patients who pass are sent to CRIO through the CRIO API. CRIO says its Recruiting API lets vendors send patient updates, qualify patients into studies and schedule appointments.^⁠[14]

5. 5

   Screening visit

   The coordinator picks the patient up in CRIO. Eligibility is decided at the visit, and the site obtains consent.

How do statuses stay in sync?

After the handoff, CRIO is the system of record. Staff record visit outcomes once, in CRIO, and Bond reads subject status back through the API, which CRIO says can both send and receive status.^⁠[14]

• A full funnel. Bond's reports cover patients matched, contacted, pre-screened, consented and randomized, plus time to enrollment and screen-failure signals.^⁠[1] The stages after the handoff come from CRIO status.
• Screen failures. A screen failure recorded in CRIO shows up in those signals, so the site and Bond can check which criterion the chart missed. See how we validate eligibility logic.

What do the CRIO admin and IT team need to do?

• Activate Bond's API access. In CRIO's Partner Directory, request integration with Bond. CRIO then activates API access for the site's organization.^⁠[11],[13]
• Match studies. Link each Bond study to its CRIO study so patients land on the right protocol.
• Choose data sources. Decide whether Bond screens the EHR, the records the site holds in CRIO, or both.
• Set visit slots and owners. Tell Bond which slots it may book and who gets each referral and escalation.
• Agree status meanings. Confirm which CRIO statuses count as screened, screen failed, consented and randomized in Bond's reports.
• Set Bond user roles. Assign role-based access in Bond, with SSO where the site uses it.^⁠[1]

The site's IT and compliance teams handle the BAA, the security review and EHR access over FHIR or HL7. The CRIO steps sit in the outreach and scheduling step of the implementation plan and run alongside the EHR connection. A full deployment with the EHR connected takes 48 hours, depending on the EHR, the IT review and the interface method.^⁠[1]

How is patient data protected between Bond and CRIO?

• A BAA first. Bond signs a business associate agreement with each site before handling its PHI.^⁠[1]
• Site-granted access. CRIO activates Bond's API access at the site's request, for that site's CRIO organization.^⁠[11]
• 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] Its controls include encryption at rest and in transit (AES-256 where applicable), role-based access with SSO, audit logging and penetration testing.^⁠[1]

The security page shows where PHI goes in a Bond deployment and links to Bond's Trust Center.

What is not integrated with CRIO today?

Bond's CRIO connection is for recruitment. The rest of CRIO works as it does today.

Bond's agents use Bond's own voice and text channels, not CRIO's in-system calling. For other research systems, see integrations.