RealTime CTMS and Bond: how they work together

What is RealTime, and who uses it?

RealTime eClinical Solutions, formerly RealTime Software Solutions,^⁠[16] makes software for running clinical research sites. Its founder began building it in 2013 to meet the needs of the large research site he owned.^⁠[3] RealTime-CTMS tracks recruitment, subjects, visits, finances and reporting; per RealTime's website, it can centrally manage an unlimited number of sites and studies in over 30 countries.^⁠[7] RealTime also sells eSource, eReg/eISF, SitePay participant payments and Engage!, a participant portal with remote eConsent.^{⁠[13],[12],[14],[11]}

As of September 2026, RealTime's CTMS page lists recruitment integrations for websites, Facebook ads and SubjectWell, plus visit scheduling with window calculations and text reminders.^⁠[7] The figures below are RealTime's own; it does not name the customers or its ranking basis.

How does Bond work alongside RealTime?

Bond works before a patient becomes a subject. RealTime-CTMS is where the site tracks the patient from referral onward. The referral is the handoff.

1. 1Identify screens EHR records against the study's inclusion and exclusion criteria and shows the evidence for each criterion.
2. 2A coordinator reviews the ranked list and accepts or rejects each match.
3. 3Bond's voice and text agents contact accepted patients, tell them AI assistance is used, pre-screen and book a visit. 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. 4Bond passes the referral to RealTime, by API or through a shared sheet, with the study, the referral source and a pre-screen summary.
5. 5The coordinator works the subject in RealTime as usual. Screening and randomization outcomes come back to Bond for reporting.

What data moves, and how is it carried?

Per RealTime's website, its API is an OData-enabled REST API, built for connecting RealTime data to CRM, ERP, EMR, analytics and BI systems.^⁠[8] A 2022 RealTime post says lead-generation campaigns connected to RealTime deliver leads directly into studies,^⁠[9] so RealTime already has a path for leads that start outside it. Which fields Bond can read or write at your site is confirmed with your RealTime administrator during scoping.

What do the site's RealTime administrator and IT team need to do?

Most of the work is decisions, not code. The RealTime administrator owns the steps below with Bond. The site's IT team handles the EHR connection and security review separately; the integrations page covers each EHR.

1. 1

   Choose the handoff method

   API, shared sheet, or Bond's dashboard only. A site can start with a sheet for the first study and add the API once the workflow is settled.

2. 2

   Confirm API access

   Check that the site's RealTime agreement covers API use, issue a credential for Bond, and limit it to the studies and fields the connection needs.

3. 3

   Map statuses and sources

   Match Bond's statuses to the subject statuses and referral sources the site already uses, so RealTime reports keep working.

4. 4

   Test on one study

   Send test referrals to one study, have a coordinator check each record, then switch on the rest.

5. 5

   Bring in RealTime if needed

   Per its website, RealTime's professional services include Integration Services with custom API development and configuration.^⁠[15] A site that wants RealTime's team involved scopes that with RealTime directly.

Where does this fit in the 48-hour implementation?

Bond's estimate for a full deployment with the EHR connected is 48 hours, depending on the EHR, the IT review and the interface method.^⁠[1] In the implementation plan, the CTMS or sheet connection is set up alongside outreach scripts and calendar scheduling. Most of the elapsed time goes to approvals: the BAA, the security review and EHR access.

How is patient data protected between Bond and RealTime?

• Agreement first. Bond signs a business associate agreement before any PHI moves.^⁠[1]
• Only referrals cross over. RealTime receives records only for patients Bond refers. The site decides whether declines and pre-screen failures are also logged there.
• 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 in transit and at rest (AES-256 where applicable), role-based access, SSO, audit logging and penetration testing.^⁠[1]
• Your risk analysis. Data synced to RealTime or a shared sheet falls under that system's access controls, so list each connection. The security page maps where PHI goes in a Bond deployment.

What is not integrated with RealTime today?

• No certified or native integration. Bond connects via RealTime's API or a file export under the site's own account.
• eSource and eReg/eISF. Bond does not write visit data to RealTime eSource or file documents in eReg/eISF.
• Payments. Bond does not trigger SitePay stipends or reimbursements.
• Messaging. Bond sends its own voice and text outreach, not through RealTime Text, which per RealTime uses a US short code for recruitment messages.^⁠[10]
• eConsent signatures. Bond supports the consent conversation. Signatures are captured in the site's eConsent tool, such as RealTime's remote eConsent, or on paper.^⁠[11]
• Screening from RealTime data. Bond screens from the EHR, not from eSource forms or subject histories in RealTime.