Connecting Bond to CRIO

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.