About the Veeva Vault CTMS Connection
With the Veeva Vault CTMS Connection, you can easily leverage operational data from your EDC vault for operational reporting within your CTMS vault. CTMS users can then report on subject statuses and status dates captured in Vault EDC, as well as navigate from a Subject within Vault CTMS to a subject’s Casebook in Vault EDC. Once configured, you can share data between Vault EDC and CTMS automatically, instead of manually exporting and importing data.
You can define subject milestone exports in Vault EDC that update subject information in your CTMS Vault. This export contains the following: Study, Country, Site, Subject ID, Subject Status, Screened Date, Screen Failed Date, Randomized Date, Enrolled Date, Withdrawn Date, End of Treatment Date, End of Study Date. With this feature, you can easily keep concurrent data for your subjects in both your EDC and CTMS vaults.
Connect via FTP or Spark
Depending on your vault’s configuration, you can connect your CTMS vault to your CDMS vault using FTP and the Clinical Loader, or via a Spark connection. To integrate using a Spark connection, the CDMS to CTMS Spark Integration feature must be enabled in your CDMS vault.
How the Connection Works via Spark Connection
When you use a spark connection to integrate with Vault CTMS, Vault EDC and Vault CTMS can automatically exchange record data in near-real time.
For example, whenever a data entry user creates a new Subject in EDC (by creating a new Casebook in the Data Entry tab), CTMS automatically creates a new, matching Subject in the CTMS vault.
The EDC/CTMS Spark connection exchanges the following data:
From Vault CTMS to Vault EDC:
- Studies (updates only, Studies must still be manually created and linked in Vault EDC)
- Study Countries
- Study Sites
From Vault EDC to Vault CTMS:
- Event Definitions (into the Visit Definitions object in Vault CTMS)
- Events (into the Subject Visits object in Vault CTMS)
The EDC/CTMS Spark connection enables Vault to create and update records in a connected vault after a user makes a change to an affected record in the source vault. Once an Admin activates the connection between EDC and CTMS, record data begins flowing between the vaults based on the Connect to Vault CDMS and Connect to Clinical Operations fields on the Study object:
- For Studies _in CTMS that have this field set to _Yes, Vault creates or updates Studies*, Study Countries, and Sites in EDC as you create or update those records in CTMS.
- For Studies _in EDC that have the _Connect to Vault Clinical Operations field set to Yes, Vault creates or updates Subjects, Subject Visits (Events), and Visit Definitions (Event Definitions) in CTMS as you create or update those records in EDC.
*The connection only updates Studies. Vault cannot create Study records.
See Configuration for the EDC/CTMS Spark Connection for configuration instructions.
How the Connection Works via FTP
With this connection, Vault EDC exports subject data in a CSV-formatted View Set to an FTP server as part of a scheduled, recurring job. Vault CTMS then ingests that data from the FTP server with Clinical Vault Loader into the CTMS vault, and creates new Subject records or updates existing Subject records accordingly.
See Configuration for the EDC/CTMS FTP Connection for configuration instructions.
Subject (CTMS) Object Fields
Data from Vault EDC populates the following fields on the Vault CTMS Subject (
- Subject ID
- Subject Status
- Screened Date
- Screen Failed Date
- Enrolled Date
- Randomized Date
- Withdrawn Date
- End of Treatment Date
- End of Study Date
- EDC ID
Actions within Vault CTMS
When configured, users with access to both EDC and CTMS vaults can open a Subject’s casebook in EDC directly from their CTMS vaults. What actions those CTMS users can perform in EDC depends on their permissions. For example, a CRA could navigate to a casebook and perform source data verification (SDV) in their EDC vault, while a data manager might open a casebook to create a query.