Data model

Common Data Architecture (CDA)

The Veeva ID CDA field (veevaid__v) is now enabled by default in all Network instances. This field is the global identifier from Veeva data products and is used in the CDA data model.

This system field is enabled, even if the CDA data model is not enabled, so all customers and downstream systems have access to this Veeva-wide ID.

Supported countries

The Veeva ID is enabled for OpenData countries where CDA is supported. CDA is not supported for China, Hong Kong, Japan, and Macao.

For more information, see Common Data Architecture (CDA).

Veeva ID and VID fields

The Veeva ID and VID fields are both ID fields used in Network, but they have differences.

Comparison

ID Definition Supported records Supported entities Format
Veeva ID The global identifier used across Veeva data products. Veeva OpenData records HCP, HCO 21-character string
HCP: V+01+VID
HCO: V+02+VID
VID Unique ID assigned by Veeva Network. Local records
Veeva OpenData records
Third party records
HCP, HCO,
Address, License, Parent HCO,
custom objects
18-digits

Example ID field formats

Entity VID

Veeva ID

HCP 243205709943014403 V01243205709943014403
HCO 242976940179325951 V02242976940179325951

View Veeva ID on record profiles

The Veeva ID displays in the Primary Information section on standard profile layouts.

If you have created custom profile layouts for a country, add the field to the layout.

Veeva ID field updates

The field is populated when the record is updated by Veeva OpenData (any field) and then is downloaded to your Network instance.

Cluster codes for Germany

Updated cluster codes from IQVIA™ are available for Germany.

New cluster version

  • Version 7.0.

The new cluster version is available by default if you have the Germany and IQVIA country/provider combination enabled in your Network instance.

Update addresses

To update addresses with the latest cluster codes:

  1. In the Admin console, click Data Model > Cluster Management.

  2. Select the Germany / IQVIA cluster configuration.

  3. In the Cluster Management Details section, expand the Cluster Version field and choose Version 7.

  4. Save your changes.

  5. Click Refresh Addresses to run a data maintenance job to ensure that all German addresses have the latest cluster codes.