OpenEDC: Third Party EDC Studies

CDB supports the use of CDB for data from third party EDC applications, without data collection or study design occurring in Vault EDC. CDB still uses Vault EDC for user management.


Contact your Veeva representative to enable the OpenEDC feature for your vault.

You must create a Study record in Vault EDC, using the External study type. Then, your organization must create users and assign them roles from within Vault CDMS to allow them access to CDB.

Users with the CDMS Lead Data Manager or CDMS Super User standard study roles can perform the actions described below by default. If your organization uses custom roles, your role must grant the following permissions:

Type Permission Label Controls
Functional Permission Workbench Tab

Ability to access and use the Data Workbench application, via the Workbench tab

Functional Permission API Access

Ability to access and use the Vault CDMS API. (This permission is also required to use CDB.)

Functional Permission View Import

Ability to access the Import page

Functional Permission Approve Import

Ability to approve or reject an import package that contains configuration changes

Functional Permission Download Import Package

Ability to download import packages

Functional Permission Manage Sources

Abiltiy to view and manage Sources from the import of third party data in CDB

If your Study contains restricted data, you must have the Restricted Data Access permission to view it.

Learn more about Study Roles.

Configuration in Vault EDC

You must first create your Study record in EDC Studio. The creation of an external EDC study in Studio creates the Study on the EDC side, so that you can use CDMS’s System Tools to manage permissions and data access. CDB makes API calls to check that your Study exists and to check if a user has permission to a Study as needed. There is no information that is sent from Vault EDC to CDB (for example, there is no Workbench Export job).

Sites & Subjects

CDB uses the Site and Subject columns in your import CSVs to create Sites. Because CDB only has the data in these files to create Sites from, only @HDR.Site.Name and @HDR.Subject.Name are available for @HDR context.

How to Import

Importing data for OpenEDC works in the same way as importing any third party data into CDB. You will need to specify that you’re using OpenEDC with the “primary_source” property in your manifest.json file. Setting “primary_source” to true indicates that the import package is the primary data source for the Study.

Use the following in your manifest.json file:

  "study": "studyName",
  "source": "External_EDC",
  "primary_source": true,

To do this in the CDB Manifest Builder, select the Primary Source checkbox.

Learn how to:

What Isn’t Included

In the current release, the following functionality isn’t supported in OpenEDC studies:

  • Import Queries: CDB doesn’t support the import of third party queries into an OpenEDC study. The creation and automation of queries within CDB is supported after the study has been imported.
  • Codelists & Unit Codelists: CDB doesn’t support Codelists or Unit Codelists. If you want to show coded and decoded values, you will need to include them in separate data columns.
  • Labels: The import of Labels isn’t supported. If you want to see Labels for an Event, Form, Item Group, or Item, you will need to include them in separate data columns.
  • Deployments: CDB doesn’t support the deployment of listings, views, or checks from one environment to another for OpenEDC studies.
  • Key Mappings: CDB doesn’t support the import of key mappings for OpenEDC studies.
  • Clean Patient Tracker: CDB doesn’t offer the Clean Patient Tracker in an OpenEDC study.