You can manually add records to your local data. The new record is added or merged The process of combining successfully matched records, or those manually identified as the same. with existing data pending further review. If a new HCP or HCO record meets the criteria for Veeva OpenData or a third-party master source, the add request A request to add a new HCP or HCO profile to a customer instance. Add requests are matched against existing data before routing to customer data stewards for review. is sent to that system. You can also add custom object records to your local data.
Tip: Before you add a record, search for it to see if it already exists or if it can be downloaded from OpenData.
To add a record:
Records can be added from the following pages:
- Inbox - At the top-right of the page, click the Gear icon and select Add Record.
- My Requests page - Click + Add Record.
- Search results - From the search results page, click Add Record.
In the Add Record dialog box, select a Record Type and Primary Country for the record and click the Next button.
The primary country cannot be changed after the record is submitted.
Custom objects are available in the Record Type list if
Add record information
The Add New Profile page displays. The summary header section includes a blank header with a generic title and the primary country.
Recommended details for add requests
When records are added, they are routed to data stewards to process. Including the following details helps to ensure that data stewards can validate the information and accept the record.
Address - Provide at least one address (ideally with a suite number and phone number).
The following address types are available:
Professional and Preferred (B) - A business address to which the provider has indicated they want their mail delivered. B refers to “both.”
- Mail Only (M) - Where the HCP wants material to be mailed. This can also be a residential (home) address.
- Professional (P) - A business address.
- Address (U) - An address that cannot be confirmed as any of the above. U refers to “unknown.”
- Specialty or Degree
- Phone number - Particularly for HCPs, include a phone number in your comments so data stewards can easily complete a call verification.
- License or NPI number
- Custom key - In the event that this record is merged with another in future, add a custom key A cross-reference between an identifier from an external system and a Network ID. to ensure it can be subsequently unmerged if necessary.
Tip: Administrators can configure field and object settings on custom profile layouts to simplify add and change requests submitted through Network widgets. For example, you can indicate required fields, or limit the values that are available for specific fields. For details, see Widget profile layouts.
Expand or collapse profile sections
By default, profiles are fully expanded so you can view all sections within a profile. You can collapse sections to view sections on the screen more easily.
To collapse or expand one section:
- Click the triangle to the left of the section.
To collapse or expand all sections:
- Click the Options menu. Choose Expand all page sections or Collapse all page sections.
Submit a record
After you apply your changes to the new record, the request is routed to the appropriate Data Stewards for review and you can see the request on your My Requests page.
If a Data Steward or System and Data Admin user submits a local record, it is automatically accepted. Requests that are routed to Veeva OpenData but are rejected, can also be automatically accepted as a local record if the workflow settings are configured to review rejections.
When the new record is processed and accepted, the profile page contains the preview boxes; for example, Find Suspect Match, Data Lineage, and Revision History. The Record Information section is populated with the latest data and the External Identifiers section includes any keys generated by Network during the add request process.
Default field values
When you add a new record, save a record, or during data load, specific fields are pre-filled with default values if no value is provided otherwise. When you add records, you do not have to specify values for default fields unless you want to change the default value. During a data load, A record that has not yet been validated by a data steward. if a source does not have a value for a field with a default value, the default value is used.
The default behavior for these fields is determined by
Survivorship The process by which the final record is determined as duplicate records are merged, resulting in winning and losing values. for fields with default values does not change; field values are overridden using the usual field survivorship process. Data Stewards do not need to edit the default values for fields unless they want to change the value.
The following apply for default values:
- They can be set by country.
- They are applicable to custom fields.
- When used in the UI, data stewards do not need to process these fields unless they want to change the default value.
- They can be set for any type of field.
- Upon implementation, they will be set for all identified fields, however existing values will not be overwritten.
- They cannot be blank.
DCRs with too many sub-objects
The number of sub-objects that can be submitted in a DCR is restricted to 100. DCRs that contain more than 100 sub-objects are automatically rejected to ensure that memory issues do not occur when the task is processed.
When you save the DCR, an error message in the Network UI or the API explains why the DCR cannot be saved:
Requests cannot have more than 100 objects.
If an entity has more than 100 sub-objects, Network users can submit a DCR and include only some of the sub-objects. Additional DCRs can be submitted to include more sub-objects.
Reserved Network entity ID
When an add request is submitted, the Task ID is immediately returned to the user. The Network entity ID (VID) for the record is returned when the request is approved.
However, if an add request is created using the API, Network can provide a Network entity ID (VID) for a new record as soon as it is created. This enables customers to use the VID as an identifier in their downstream system.
Enable receiving reserved Network entity IDs
This feature is only supported in Network instances that have the Create Unverified option enabled in the Workflow Settings.
To enable this feature, a Network integration user must set the value for the reserve_vid parameter in the change request API to true. For more information, see the Change request API documentation.
If the user tries to search for an entity using the reserved VID before the record is created, an error message displays:
Reserved VID cannot be found. Please try again later.
No matching occurs within your Network instance on records before the task is created. If the entity type of the record is managed by OpenData, the add request is routed directly to OpenData. If the entity type is managed locally, the add request is immediately routed to local data stewards. This behavior enables you to get the Network entity ID immediately for an unverified record.
When data stewards open the task in their inbox, matching will occur if there is a local match in the Network instance. If the record matches with an existing record, a change request is created and it can be merged when data stewards process the task. If no match is found, the request remains an add request.
If you do not use the reserve VID feature, add requests go through the ACT matching process before the task and the unverified record is created, but the Network entity ID is not available until the task is created.
The reserved VID is logged in the Task Audit History in the Message column.