Data Model
User Roles
| Activity | ST | DS | DM | AD |
|---|---|---|---|---|
| View the data model |
|
|
||
| Enable or disable Veeva-owned fields |
|
|
||
| Create custom domains and objects |
|
|
||
| Create custom fields |
|
|
||
| Manage custom reference data and descriptions |
|
|
Key Concepts
The Network MDM data model
The organization of Network data, including objects, individual fields, field attributes, and data relationships. consists of primary entities A high-level record attribute; in general, an HCO or HCP., their corresponding fields, and their relationship with one another. The data model is unique to each supported country. These fields are used for all Veeva OpenData or third-party mastered Data that customers purchase from an independent data provider that can be used as the master data in the customer's own Network instance. This data is never shared with Veeva OpenData. data, and have the "__v" suffix.
You can extend the Network MDM data model by creating custom domains, objects, and custom fields Fields that are added to an entity in the Network data model. This data is customer-maintained. ("__c"), and by loading customer data into Veeva-owned fields for fields that aren't in use for a particular country.
Reference data types A collection of reference codes associated with reference fields that defines the values allowed for a field. use a list of values so users can choose a field value from a predefined list. The values in this list are called reference codes. Network includes code values The value assigned to an entry in a reference code list. and descriptions for reference data fields Fields for which multiple predefined values exist, in the form of reference codes., localized for supported regions. You can also add custom values to the reference list for a field, with your own localized description.