CDA data model fields

CDA supports HCP, HCO, and Address fields.

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 25R1 April 11th 2025.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

OpenData managed CDA fields

All CDA fields have the __v suffix. Most of the fields are managed by Veeva OpenData for OpenData records.

Updates to OpenData CDA fields

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

For details see Populate CDA fields on OpenData records.

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

Locally managed CDA fields

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

Tip: Field labels can be added, edited, and removed for any language for these fields. If you customize a label, any changes that Veeva makes to the label will not overwrite your changes.

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.

Update calculated fields

CDA Sync automatically runs in your Network instance during data update jobs, for example, 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.

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

Updating fields

The local CDA fields that are not calculated can be updated the same way that legacy fields are updated:

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

  • Load the data into your Network instance

    Include non-calculated fields in the import files.