Connecting Bond to eClinicalWorks

What is eClinicalWorks, and who uses it?

eClinicalWorks is a privately held health IT company founded in 1999. It sells EHR software to ambulatory practices, urgent care centers, health centers and hospitals, along with patient engagement, population health and revenue cycle tools.^⁠[8]

Its footprint is largest in community health. Health centers served 32.4 million patients in 2024, and 64% of them were people of color.^⁠[7] If the vendor's share holds, many of those charts are in eClinicalWorks, which matters to FQHCs and to sponsors with a diversity action plan.

What data does Bond read, and which FHIR resources carry it?

eClinicalWorks holds ONC certification for the standardized API for patient and population services, § 170.315(g)(10).^⁠[10] As of September 2026, its production FHIR server runs version 4.0.1, declares the US Core server and Bulk Data capability statements, and lists 36 resource types. All of them are read and search only, except QuestionnaireResponse, which also accepts create.^⁠[9]

How are clinical notes handled?

Many criteria live in free text, such as symptom history or response to a prior therapy. Identify reads the notes eClinicalWorks returns through DocumentReference and Binary alongside coded fields, and links each criterion to the passage that supports it.^⁠[9]

• Scope. DocumentReference can be searched by category, type and date, so a query can be limited to the note types and look-back window a protocol needs.^⁠[9]
• Scribe-drafted notes. Some practices draft notes with Sunoh.ai, an ambient AI scribe eClinicalWorks says is fully integrated with its EHR.^⁠[15] Bond does not connect to Sunoh; in the test connection, check that these notes appear in DocumentReference like other progress notes.
• Scanned and outside records. Faxes, scans and records from other networks may not arrive as readable text. If not, criteria that depend on them move to the pre-screening call.
• Wording. A note can name the same condition many ways. Bond's terminology graph maps phrases, codes and drug names to one concept before a criterion is checked.^⁠[3]

What does the practice need to do?

The practice-side work sits mostly with your eClinicalWorks administrator. Third-party developers connect through eClinicalWorks' Platform for Open Development, which has one developer portal for patient-facing apps and another for provider-facing and backend (bulk) FHIR APIs.^⁠[11],[10] A tool that screens a whole panel uses the second.

1. 1

   Sign the business associate agreement

   No PHI moves until the BAA with Bond is in place.

2. 2

   Turn on FHIR access

   An administrator enables FHIR APIs through the On-Demand Activation feature inside the eClinicalWorks application.^⁠[10] A third-party API directory reports that each practice activates separately, so a network running several eClinicalWorks practices may repeat this step for each.^⁠[13]

3. 3

   Authorize the backend connection

   An independent API catalog lists support for SMART Backend Services with private_key_jwt authentication, so no staff login is shared.^⁠[12]

4. 4

   Agree on the export population

   The practice and Bond agree on which patients the Bulk Data export covers.

5. 5

   Name a validation reviewer

   Before go-live, a PI or coordinator adjudicates a sample of Bond's criteria checks on real records. See how we validate eligibility logic.

Where does this sit in the 48-hour implementation?

Bond's published estimate for a full EHR integration is 48 hours, depending on the EHR, the IT review and the interface method.^⁠[1] In the implementation plan, the security review and the eClinicalWorks connection come first, while criteria and outreach scripts are set up alongside.^⁠[1]

The first screen runs across the agreed population. As of September 2026, a third-party API directory reports a limit of 250 calls per minute per practice code, which makes chart-by-chart queries across a large panel slow.^⁠[13] A Bulk Data export fetches the population as one job, which is why the population is agreed early.

How is patient data protected?

• Scoped access. Bond requests read access to the resources in the table above, and your security review approves that list.
• 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 signs BAAs and uses encryption in transit and at rest (AES-256 where applicable), role-based access, SSO support, audit logging and penetration testing.^⁠[1]
• People decide. Bond ranks candidates with the evidence for each criterion; coordinators review them, and the screening visit confirms eligibility.

See security for where PHI goes and what your security reviewer should ask for.

How does Bond relate to eClinicalWorks' own tools?

eClinicalWorks does not present these tools as trial recruitment products; the difference is scope.

What is not integrated with eClinicalWorks today?

• Certification or partner status. Bond works alongside eClinicalWorks and connects via its FHIR APIs, but holds no eClinicalWorks certification or partner listing. Its only vendor certification is CRIO Certified Partner.^⁠[1]
• Writing to the chart. The FHIR server is read-only apart from QuestionnaireResponse, and a third-party directory reports that write APIs need a separate contract with eClinicalWorks.^⁠[9],[13] Bond does not file notes, orders or research status in eClinicalWorks.
• The eClinicalWorks schedule. Bond does not read or book eClinicalWorks appointments. It books visits on the calendar the site connects, and status goes to Bond's dashboard, the CTMS or a Google Sheet.^⁠[1]
• Portal messaging. Bond does not send patient portal messages. Its outreach is voice and text through Engage.

Paths for other EHRs and research systems are on the integrations page.