Integration
Veeva SiteVault and Bond: what connects and what is manual
Veeva SiteVault is the eISF, CTMS and eConsent system many research sites use as their regulatory binder.[3],[5] Bond Health works at the recruitment step, before a patient becomes a participant, and produces records the binder may need.
What is Veeva SiteVault, and who uses it?
SiteVault eISF is an electronic investigator site file that replaces paper regulatory binders and gives study teams and monitors self-serve access to documents.[3] Veeva launched SiteVault as a free eRegulatory product in January 2020.[6] As of September 2026, the free edition includes CTMS, eISF and eConsent for sites with 20 or fewer concurrent active studies, which Veeva says is over 90% of research sites globally.[5] Larger sites move to SiteVault Enterprise, which has tiered pricing.[3],[5]
Site staff file essential documents in SiteVault, and monitors assigned to a study review them there.[3],[11] The figures below are Veeva's, as of September 2026.
Where does Bond sit next to SiteVault?
Bond covers recruitment. Identify screens EHR records against the protocol and shows the evidence for each criterion. Engage contacts candidates by voice or text, pre-screens them and books a screening visit. Consent support answers patients' questions in plain language, and the site still obtains consent.[1] SiteVault holds the regulatory record that follows: approved recruitment materials, logs, signed consent forms and staff records.[11]
Which Bond records belong in the SiteVault binder?
SiteVault's eBinder uses a fixed folder structure based on the eISF Reference Model, and sites cannot change it.[7] So each Bond record goes under one of Veeva's standard document types.[11] The site's SOPs and the sponsor decide what is filed.
| Data element | FHIR resource or interface | SiteVault document type | Notes |
|---|---|---|---|
| Chart data for screening | EHR over FHIR R4 (Patient, Condition, MedicationRequest, Observation, DocumentReference), HL7 v2 or an integration partner | None | Read from the EHR under the BAA with Bond and never filed in SiteVault.[1] See integrations. |
| Recruitment approach | Written description of the study's Bond configuration | Recruitment Plan, in Key Study Materials > Manuals & Procedures | The plan can name EHR screening and AI outreach as methods and say how referrals are tracked. |
| Voice and text outreach scripts | Script text exported as a document | Advertisement for Recruitment, in Participant Facing > Recruiting & Consenting | Veeva defines this type as IRB-approved recruitment material. The IRB's decision files as IRB/IEC Response. |
| Pre-screening log | Report exported from Bond's dashboard, coded by the site before filing | Participant Screening Log, in Participants > Logs | Veeva's log lists participants by code. Whether pre-screens belong here is the site's and sponsor's call. |
| Consent support record | Report from Bond's audit trail | Source, in Participants > Source | Only if the site's SOP treats it as documentation of the consent process. The signed ICF files as Informed Consent Form (signed). |
| Bond user access | User list from Bond's role-based access settings | System User Access, in PI Oversight | Which staff hold Bond accounts, and when access ends. |
| Dashboard training | The site's training sign-in sheet | Training Evidence (study-specific), in Study Training | Bond trains coordinators just before go-live, as part of the typical implementation plan.[1] |
Document types and eBinder locations are from Veeva's SiteVault document type list, updated August 7, 2026.[11]
How do records move from Bond into SiteVault?
It depends on the edition. As of September 2026, Veeva's FAQ says the free version integrates with other Veeva applications but does not currently integrate with third-party systems, and that the Enterprise package enables integration.[7] On Veeva's plans page, Open API and single sign-on are Enterprise features.[8]
| SiteVault edition | How Bond records get in | Who finalizes them |
|---|---|---|
| SiteVault Free (up to 20 active studies)[3] | Staff export the reports above from Bond and upload them like any other document. | Site staff |
| SiteVault Enterprise | Enterprise adds API access.[5] The Vault API lets an external application read and write to Vault.[9] Bond has no prebuilt upload, so one is scoped per site with the Vault administrator. | Uploads start in Draft, the first lifecycle state for these document types. Staff review and finalize them.[11] |
For API loads, Veeva's general Vault guidance recommends storing the external system's document ID in the external_id__v field so each document links back to its source.[10] For Bond, that is the report ID.
What does the site's regulatory or IT team need to do?
- 1
Confirm the edition
Free sites use file upload. Enterprise sites can also use the API.
- 2
Agree on the mapping
Check each document type above against site SOPs and sponsor expectations.
- 3
Set the coding rule
Decide how patients are coded in logs, so names stay out of shared logs. The key linking codes to names files as a Participant ID Code List.[11]
- 4
Issue API access (Enterprise only)
With the site's Vault administrator, set up credentials for the upload and limit its access to the agreed studies.
- 5
Test on one study
File one study's first reports, have the regulatory lead check them, then extend.
Where does this fit in the 48-hour implementation?
A full Bond deployment with the EHR connected typically takes 48 hours, depending on the EHR, the IT review and the interface method.[1] SiteVault work does not gate go-live, because Bond never reads from it. In the typical implementation plan, scripts go to the IRB before outreach starts, and the pre-screening log starts when outreach begins. Training and access setup just before go-live produce the training and user access records.[1]
How is patient data protected between Bond and SiteVault?
- Agreements first. The business associate agreement with Bond is signed at kickoff, before any PHI moves.[1]
- Coded logs. Veeva's screening log type lists participants by code, and monitors on the study can view it once final.[11]
- The site decides what is shared. In SiteVault the site owns its data and chooses which documents to share and with whom.[7]
- 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. See security.[1]
What is not integrated with SiteVault today?
- No prebuilt connector, and no reads. Bond works alongside SiteVault by file upload, or an API upload scoped with an Enterprise site. It pulls nothing out of SiteVault.
- No CTMS sync. Bond does not create participants or set their status in SiteVault CTMS. Staff do that on the participant's Screening & Enrollment Details tab, as for any referral.[12]
- No sponsor feed. For sponsors on Veeva's Clinical Platform, SiteVault CTMS can share recruitment status.[5] That status comes from what staff enter, not from Bond.
- No eConsent writes. SiteVault eConsent runs in-person or remote consent.[14] Bond supports the conversation before it and does not write to eConsent records.
Bring one protocol and your regulatory lead. We will map Bond's records to your binder.
Frequently asked questions
Is Bond a Veeva partner?
Do we need SiteVault Enterprise to use Bond?
How is Bond different from Veeva AI in SiteVault?
Sources
- 1.Bond Health: platform overview, FAQ and pricing · Bond Health, 2026
- 2.Bond Health product information · Bond Health, 2026Capabilities, pricing and compliance status described by Bond Health, September 2026.
- 3.eISF Software for Clinical Trial Sites | Veeva SiteVault · Veeva Systems, 2026Vendor page, accessed September 2026. Quote: "SiteVault eISF is an electronic investigator site file (eISF) that reduces the administrative burden of managing paper binders so research teams can focus on what matters most." Also: "SiteVault is free for sites with up to 20 active studies, and available with tiered pricing options for larger sites." Also: "Join over 8,000 sites across more than 80 countries."
- 4.Veeva SiteVault: One place to manage your studies · Veeva Systems, 2026Vendor homepage, accessed September 2026. Quote: "2000 + Monthly Active Sites Use SiteVault"
- 5.CTMS General FAQs | SiteVault Help · Veeva Systems, 2026Quote: "The 'SiteVault Free' edition (which now includes CTMS, eISF, and eConsent) is available to any site managing 20 or fewer concurrent active studies. This is over 90% of research sites, globally." Also: "The Enterprise tier provides the same core CTMS capabilities but includes additional features like Single Sign-On (SSO), API access for custom integrations, and dedicated account management." Also: "For sponsors and CROs using Veeva's Clinical Platform, SiteVault CTMS allows for bidirectional data flow. This streamlines the exchange of information, such as recruitment status and milestone completions."
- 6.Veeva SiteVault Now Available to Simplify Study Execution at Clinical Research Sites · Veeva Systems, 2020Press release dated January 8, 2020. Quote: "Veeva Systems (NYSE:VEEV) today introduced the availability of Veeva SiteVault, a free eRegulatory solution for clinical research sites."
- 7.SiteVault FAQ · Veeva Systems, 2026Accessed September 22, 2026. Quote: "The free version of SiteVault integrates with other Veeva applications but does not currently integrate with third-party systems." Also: "The SiteVault Enterprise Package enables integration." Also: "The SiteVault eBinder structure is based on the eISF Reference Model and is an intentional product design choice." Also: "The sites decide what documents to share and with whom to share them."
- 8.Plans | Veeva SiteVault · Veeva Systems, 2026Feature table, SiteVault Free then SiteVault Enterprise. Quote: "Connection to sponsor systems from Veeva ✓ ✓ One login across Veeva applications ✓ ✓ Open API – ✓ Single sign-on (SSO) – ✓"
- 9.Vault API | Vault Developer Portal (SiteVault) · Veeva Systems, 2026Quote: "Vault API allows you to read and write to Vault [...], allowing your application to integrate directly with Vault."
- 10.Integration Types | Vault Developer Portal · Veeva Systems, 2026General Vault Platform guidance. Quote: "When loading documents from an external system into Vault, it's recommended to store the external document's identifier in the Vault external_id__v field or any other unique field, to be able to easily link the documents."
- 11.SiteVault Document Types (SiteVault-DocumentTypes.xlsx) · Veeva Systems, 2026Spreadsheet downloaded and read September 22, 2026 ("Current" sheet; the Updates sheet is dated August 7, 2026). Quote: "Participant Screening Log | Subject Screening Log -- Lists all study participants screened at the site. Participants are coded to respect personal identification. | Draft to Current | ... | Participants > Logs" Also: "Advertisement for Recruitment | Recruiting Ad -- Materials used in study recruitment campaigns; approved by the IRB/IEC to ensure recruitment measures are appropriate and not coercive." (Participant Facing > Recruiting & Consenting). Also: "Recruitment Plan | To describe the planned participant enrollment/recruitment goals for the study, and the methods by which those goals will be tracked and achieved." (Key Study Materials > Manuals & Procedures). Also: "System User Access | ... Identifies which site staff have received accounts for a third party system (such as randomization or ePRO) used for the study. May also identify revocation of access." (PI Oversight). Also: Source "May include medical treatment and history, concomitant medication (con med) records, documentation of the consent process" (Participants > Source). Also: "Training Evidence (study-specific) | Verifies completion of study-specific training. Often in form of a Sign-in Sheet." (Study Training). Also: "IRB/IEC Response | Ethics Committee Approval, Decision, Acknowledgement" (IRB/IEC > Submissions). Also: "Participant ID Code List | Subject Identification Code List, Subject ID List -- Fully identifies all participants for the study at the site, with unique identifiers/codes where relevant." (Participants > Logs). Can Monitors View: "Yes, if steady state and monitor is on the study."
- 12.Create Participant | SiteVault Help · Veeva Systems, 2026Quote: "Once created, you can select the current status for the participant and complete any relevant date fields on the Screening & Enrollment Details tab."
- 13.Veeva AI in SiteVault · Veeva Systems, 2026Accessed September 22, 2026. Quote: "Not permitted. Only Veeva-governed agents operate on SiteVault data." (row: third-party AI apps reaching into your data). Also: "SiteVault's first production ready AI agent is live in CTMS, built to eliminate the manual overhead of study setup." Also: "The agent reads the schedule of assessments the way an experienced study manager would, automatically generating the visit schedule directly in CTMS."
- 14.eConsent in Clinical Trials | Veeva SiteVault · Veeva Systems, 2026Accessed September 2026. Quote: "SiteVault eConsent provides a digital way to consent clinical trial participants in-person or remotely."
Related pages
Consent
How Bond supports the consent conversation and what the site still owns.
ReadImplementation
The 48-hour plan, step by step, with site and Bond tasks.
ReadIntegrations
EHR and research-system connections, and what each requires.
ReadIdentify: LLM-based EHR screening
How Bond screens the EHR and explains each match.
ReadSecurity
BAAs, encryption, access control and audit logging.
ReadeRegulatory and eISF
What an electronic regulatory binder holds.
Read