Send add requests to Veeva OpenData
Data stewards and data managers can route qualified local records to Veeva OpenData as add requests so OpenData takes ownership of the records. Sending the records to OpenData for ownership reduces stewardship cost for customers and improves data quality. Previously, if locally managed records were loaded into their Network instance and matches with Veeva OpenData records were not found, customer data stewards would need to manually copy the information into an add request and send it to OpenData. Now, data stewards can click a button on local record profiles to quickly send the record as an add request to OpenData.
Add requests cannot be sent to third party providers using this feature.
The feature is not enabled by default. Contact Veeva Support to enable it for your Network instance.
Set user permissions
When the feature is enabled, administrators can determine which group of users have access to the Send to OpenData button by assigning the permission on the data visibility profile.
To specify the users who can access this feature:
- In the Admin console, click Users > Data Visibility Profile.
- Select a data visibility profile and click Edit.
- In the Permissions section, set the Send to OpenData option to True.
- Save your changes.
The data stewards and data managers assigned to this data visibility profile will have access to the Send to OpenData button on locally managed records.
Data stewards can route locally managed records to Veeva OpenData using the Send to OpenData button on the record profile.
The primary country of the record determines which Veeva OpenData master the add request is sent to. Address countries are not considered for add request routing.
The Send to OpenData button displays only if the following criteria are met:
- The record state is valid. The button is hidden if the record is in any of the following states: Under Review, Invalid, Merged_into, or Deleted.
- The user is a data steward or a data manager.
- The HCP type (for example, prescriber, nurse) or HCO type (for example, clinic, organization) is managed by Veeva OpenData (defined in the Veeva OpenData subscription).
- The record is locally managed.
- The record does not contain proprietary, restricted data, or third party system contributions - sub-objects or attributes cannot be from a proprietary system. Source systems can be marked as proprietary or restricted in System Interfaces > Systems. Data from a proprietary system is never shared with Veeva OpenData or a third party master.
- The record does not have local pending tasks (DCRs or suspect matches).
- The record has not already been sent to Veeva OpenData with pending master tasks.
After the button is clicked, a dialog displays to confirm that the record is not managed by a third party data provider:
You are sending a request for this record to be added to Veeva OpenData and to be maintained by Veeva. Was this record obtained from the data of another third party data provider other than Veeva (e.g, data from IMS / IQVIA)?
If you answer No, the add request is sent to Veeva OpenData. If you answer Yes, the add request is canceled and the record cannot be sent to Veeva OpenData.
If the Send to OpenData button displays on the profile but the button is dimmed, the record contains proprietary data, has pending local tasks, or has already been sent to Veeva OpenData. For each of these reasons, a tooltip message displays when data stewards hover over the dimmed Send to OpenData button.
Records that are routed using the Send to OpenData button display as add requests on the data steward's or data manager's My Requests page.
Data stewards and data managers can track the add requests that they send from the My Requests page.
When add requests are sent to Veeva OpenData, any further updates made to the pending master record in your customer instance will be automatically rejected. Change requests can be made to this record after the add request has been processed by Veeva OpenData.
Add requests that are routed using Send to OpenData do not include the following information:
- Custom reference types for sub-objects (addresses, parent HCOs, and licenses). The values are removed.
- Inactive sub-objects
- Locally managed parent affiliations. If the record has a parent HCO relationship to an HCO from a proprietary source, the HCP record is sent to OpenData without the parent HCO relationship and HCO. Only Parent HCOs that are managed by Veeva OpenData are included in the add request.
Custom keys and sources are retained on the record if Veeva OpenData accepts the add request and assumes ownership of the record.
When the add request has been submitted, the following behavior occurs for the local record in the Network user interface:
- The record profile becomes locked; edits cannot be made. Incoming change requests are automatically rejected by Network with the following message: "System Rejected - You cannot update a record that has been sent to OpenData. The record is currently Pending Master."
- The record cannot be merged into another record; the Find Suspect Match option on the profile page is not available.
- For candidate records, the Resolve button on the record profile is disabled so data stewards or data managers do not accidentally resolve the candidate.
- When the Create Verified option is enabled in your Network instance (Workflow Settings), another unverified record will not be created. Network recognizes that the local record already exists, so a new unverified record will be prevented from being created.
If the add request is rejected by Veeva OpenData, the local record state does not become invalid. The record remains a valid local record that can be edited and the Send to OpenData button displays on the record's profile page.
Reporting on DCRs
Users with access to advanced ad hoc reporting can run a query to report on the change requests that have been sent to Veeva OpenData. For more information see DCRs sent to Veeva OpenData.