Integrating with third-party masters

Data from third party providers can be loaded into your Network instance. Data that is externally managed and stewarded by the third party data provider is considered third party master data. This data displays as blue records and fields in your instance.

Master data comparison

Third party master data can be used as an alternative to Veeva OpenData in some countries.

The Network features that are available for these masters can differ.

	Veeva OpenData	Third Party Master Data
Loading data	OpenData subscriptions	Create a source subscription that will be used as the third party master feed
Search and download records that are not in your Network instance	Yes	No
Match against existing records in the OpenData instance	Yes	No
Data stewardship	DCRs are routed to Veeva OpenData data stewards in real-time	DCRs must be extracted, exported, and provided to third party data stewards using files or the API. The DCR response is imported back into Network with the master feed or using the API.
Reporting against records in the OpenData instance	Yes	No
Integration with Veeva CRM and Vault CRM	Yes	Yes
Match and merge	Local records can be matched and merged to OpenData records.	Local records can be matched and merged to third-party master records.
Unsubscribe to master records	Yes - Using a data maintenance job	Yes - Advise the third party and then use a NEX function to unsubscribe the third party records.

Key details for third party masters

Third party master systems are created in Network to identify record ownership and stewardship.
Third party data can be loaded into Network and provisioned to Veeva CRM or Vault CRM using the Network Bridge.
DCRs for third party records must be exported from Network and sent to third party master data stewards to be processed.
Third party records never interact with OpenData records or are sent to Veeva OpenData.

Creating a third party master system

Before loading any data from a third party master into Network, create a system.

Purpose

Record ownership - Data that is loaded into Network with that system is identified as a third-party master data. The source subscription that you set up for that system will function as your third-party master feed.
Field ownership - In the DCR routing section, you define which fields will be externally mastered by third-party data stewards. Any fields not defined as externally mastered will be managed locally.

DCR processing - The DCRs on the entities and fields that you have defined in this third party system must be processed by the third party master for the specified country.

Loading third party master data

Third-party master feed

Load the data into your Network instance using a dedicated source subscription that is assigned to the third-party master system. This source system is essentially the third-party master feed; the equivalent of an OpenData subscription. Use this master feed as the only method for updating third-party records and fields.

Important: Administrators and Data Managers are responsible for ensuring that TPAs with third party providers are either in place or are not required before loading data into Network.

Custom keys

When the data is loaded into your Network instance using this master feed, custom keys will be created to identify the record as a third-party record owned by that system.

These master keys are the primary key that the third party uses to identify a record. They are critical for the DCR process. When you export DCRs for third party records, the keys are included in the DCR export file. After the third party data stewards have processed the changes, the DCR response file that is imported back into Network must include these master keys.

Matching and merging

For data deduplication, locally managed records can be matched and merged into third-party master records. Third party master records are never merged into locally managed records.

Third party records are never matched (or merged) with Veeva OpenData records.

Viewing data

Third party master HCPs and HCOs are identified in Network using blue object icons and fields..

Data change requests

DCRs for third party data are externally processed by third party data stewards.

Processing the DCRs requires the following updates:

Updating the DCRs
Updating the data (new or changed)

When users create new records or submit changes to third party master data in Network, the DCRs are assigned to the third party master system.

The DCRs must be exported to the third party master using one of the following methods:

Files - Export the DCRs so the third party can accept or reject the changes and then re-import the DCR outcome.
- Export DCR files - Use a target subscription to create files containing DCRs for the third party system.
- Import DCR response - The third party can use the exported file to record their response and then import the file back into Network to update the DCR.
The data that was added or changed from the DCRs is also included in the third party master feed.
Network API - Use Network API calls to forward DCRs to the third party master so they know what DCRs to process.

Use the API endpoint to retrieve (single or bulk) DCRs that are assigned to the third party master system and that are not yet processed.

After the DCRs have been processed, use the API endpoint to update the DCRs as being processed.

For details, see the Third-party integration topic in the Veeva Network Developers Online Help.

Workflow settings

Administrators can enable the option to create local records from add requests that are rejected by third party data providers.

User activities

The following activities are available depending on the user type:

The System and Data Admin user role combines the full capabilities of Data Stewards and Administrators.
Activity	Standard User	Data Steward	Data Manager	Administrator
Create a third-party system
Define DCR routing for third-party records
Load third-party data
View third-party records
Export DCRs for third-party systems
Import DCRs from third-party systems
Configure workflow settings for rejected third-party records