CDA data model fields

HCP, HCO, and Address fields are currently supported for CDA.

The naming convention for the fields contain the _cda__v suffix. The ID field (veevaid__v) is the exception to the naming convention.

List of fields

Field details

A list of the fields with high-level details is provided in the sections below.

Download the following files for more information about the fields:

Calculation of CDA Fields 24R3 November 29th 2024.xlsx

  • Field ownership

  • Field calculation rules for each country / region

Network CDA - Data dictionary 24R3 November 29th 2024.xlsx

  • Network > CDA language mappings

  • Network > CDA reference code mappings

Field ownership

Most CDA fields are managed by Veeva OpenData for OpenData records. The remaining fields are locally managed.

OpenData-managed CDA fields

Veeva managed CDA field values will be pushed to your Network instance through your OpenData subscriptions or ad hoc downloads as usual.

Note: The CDA Sync setting does not need to be enabled in our Network instance to receive OpenData in these CDA fields.

Populate CDA fields on OpenData records

After you enable at least one CDA field in your Network instance, run a full OpenData country subscription to update all records that are downloaded in your Network instance.

To run a full update:

  1. Open an OpenData country subscription (System Interfaces > OpenData Subscriptions).

  2. In the Updates to OpenData records section, select Update all records.

  3. Save your changes.

The next time the subscription runs, you will receive updates for all the OpenData managed CDA fields that you have enabled.

Locally managed CDA fields

These CDA fields and their values are managed in your Network instance. These are custom fields, but they have the __v suffix.

Calculated fields

Some locally managed fields are calculated fields. This means that the field values are populated by the CDA Sync process in your Network instance. CDA Sync applies to locally managed records only.

CDA Sync runs when data is updated in your Network instance, for example, through source subscriptions, data updater, DCRs, and merges. The process calculates the CDA field values using internal country-based rules or by mapping the corresponding legacy field value.

Note: CDA Sync must be enabled so calculated fields values can be populated.

Populate calculated fields

Calculated CDA fields are populated by the CDA Sync process.

CDA Sync automatically runs in your Network instance during data update jobs, for example, source subscriptions, data updater, DCRs, and merges.

To update calculated fields:

  • Load data into the mapped legacy fields

    The CDA Sync process will map the legacy field values to the calculated CDA fields.

    Important: If calculated CDA fields are included in the import files, the data will be overwritten when CDA Sync runs.

  • Submit data change requests on calculated CDA fields

    The CDA Sync process will map the values to the legacy fields for Data Stewards to process.

For more details, see CDA Sync and CDA DCRs.

Non-calculated fields

The local CDA fields that are not calculated are managed just like legacy fields.

Populate non-calculated fields

The fields can be updated in the following ways:

  • Submit data change requests on the non-calculated fields.

  • Load the data into your Network instance

    Include non-calculated fields in the import files.