Glossary

This list includes terms commonly used in Network. Can't find what you're looking for? Send us your Feedback.

    A
  • A custom relationship object that connects HCPs and HCOs to a health system for a specific product and therapeutic area. It is supported for the Affiliation widget only and is automatically created when the widget is enabled in your Network instance.
  • A high confidence match between two records. ACT matches result in a merge without any human review.
  • A user-initiated match of a user-supplied file against Network data that typically results in high confidence matches.
  • Controls (similar to SQL queries) for using available keywords, tables, fields, and operators to analyze data in a Network instance.
  • 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.
  • The process of validating address information automatically during data load, change requests, and updates submitted through the Network UI, or manually from a Profile page.
  • An address management tool that applies the address of a parent HCO to its child HCP or HCO addresses, using customer-specific criteria.
  • A feature that recalculates cleansed addresses to ensure that street name and number are in the address_line_1__v field to support downstream systems.
  • The process of validating address information automatically during data load, change requests, and updates submitted through the Network UI, or manually from a Profile page.
  • The view in Network that enables administrators to add and update user profiles, system information, subscriptions, general settings, and manage the data model.
  • A Network user who can access some data steward functionality as well as system configuration and user management functionality.
  • A relationship between an HCO or HCP and another HCO.
  • A Veeva standard relationship object that identifies HCP to HCP affiliations. It is supported for the Affiliation widget only and is automatically created when the widget is enabled in your Network instance.
  • A Network integration pattern for understanding influencers between HCPs and identifying key players in a health system.
  • Influence Maps that users can create and customize for specific business purposes. Multiple views can be created for each health system.
  • A unique key used to represent a Network record across multiple systems.
  • A unique key used to represent a Network record across multiple systems.
  • A single incoming record matches multiple incoming or Network records without one clear "best" match. Ambiguous matches typically require human review.
  • A single incoming record matches multiple incoming or Network records without one clear "best" match. Ambiguous matches typically require human review.
  • An administrator log containing significant events and configuration changes in Network.
  • B
  • A component of the match process that groups data into blocks to reduce the overall amount of data to compare.
  • C
  • A temporary record created to enable data stewards to verify data quality before promoting the record as valid. Candidate records are not pushed to downstream systems.
  • A request to change data from Veeva CRM, the Network API, or from within the Network user interface. Change requests are processed by either customer or Veeva data stewards, depending on ownership of the data being changed.
  • A relationship from a specific parent HCO to an HCP or HCO.
  • A read-only CRM data subscription for a country that is managed by its associated multi-country Network Bridge.
  • This term is no longer used. It has been replaced by sub-object.
  • This term is no longer used. It has been replaced by sub-object.
  • A component of the match process that combines features and uses them to compare records and determine matches.
  • A read-only field that is automatically generated for configurations. The field is used for exporting and importing configurations.
  • An online business and travel expense system that can be integrated with Veeva Network.
  • A Concur instance that is configured in the Network Concur Connector. Mutliple Concur environments are supported for each Network instance.
  • The degree to which a record comparison is considered a potential or true match.
  • Immediately create records (in an unverified state) when new HCPs or HCOs are submitted as requests in your Network instance. This enables users to immediately make changes to unverified records.
  • Customer relationship management
  • Customer-specific information (such as unique identifiers) from downstream systems that are stored in Network.
  • Change set export from Veeva OpenData.
  • Import of the change set update from Veeva OpenData to a customer instance.
  • Fields that are added to an entity in the Network data model. This data is customer-maintained.
  • A cross-reference between an identifier from an external system and a Network ID.
  • Field-level logic to ensure that specific field values are retained when two records are merged together.
  • A root entity that is provisioned for a unique use and is specific to your Network instance.
  • A relationship between a HCP or HCO and a parent HCO that is managed by a customer.
  • An object that depends on the existence of a root entity. Custom sub-objects are provisioned for a unique use and are specific to your Network instance.
  • User groups that are created and managed by Network users to provide access to specific Network features.
  • A data steward that manages updates to customer-owned data.
  • A customer instance of Veeva Network that contains both Veeva OpenData data (if subscribed) as well as customer-owned records and data.
  • A customer instance of Veeva Network that contains both Veeva OpenData data (if subscribed) as well as customer-owned records and data.
  • A customer instance of Veeva Network that contains both Veeva OpenData data (if subscribed) as well as customer-owned records and data.
  • D
  • A data visualization that instantly displays important information to administrators and data managers on their home dashboard.
  • A request to change data from Veeva CRM, the Network API, or from within the Network user interface. Change requests are processed by either customer or Veeva data stewards, depending on ownership of the data being changed.
  • A tool that can be customized to display external data related to HCOs HCPs, and custom objects in Network.
  • A data maintenance job that identifies duplicate records by comparing specific records in your Network instance against all other records in your instance using match rules and data groups.
  • A logical grouping of objects for a specific theme or purpose. All objects must belong to a data domain.
  • Writing data from a Network instance to a file. This can include HCP and HCO information as well as address, licenses and affiliations.
  • The inbound integration configuration that allows you to load data into Network and that includes file preparation, data modelling, field mapping, and data standardization and cleansing.
  • The series of operations that occurs every time information is added, updated, matched and merged from files, change requests, or data steward updates.
  • A component of the match process that groups data into blocks to reduce the overall amount of data to compare.
  • The inbound integration configuration that allows you to load data into Network and that includes file preparation, data modelling, field mapping, and data standardization and cleansing.
  • A detailed view of the current record, including all sources that contributed to it and survivorship results at the field level.
  • The inbound integration configuration that allows you to load data into Network and that includes file preparation, data modelling, field mapping, and data standardization and cleansing.
  • User directed automated jobs that improve data quality by targeting specific data quality issues like sub-object inactivation and data deduplication detection.
  • A Network user that can perform all data steward tasks, as well as some administrator tasks; for example, managing subscription jobs and data model tasks. This user cannot manage users, access audit logs, or configure admin settings.
  • The organization of Network data, including objects, individual fields, field attributes, and data relationships.
  • A suite of tests that quantify and summarize potential issues in customer master data.
  • A system that provides customer data for mastering in Network.
  • A Network user who can manage data change requests and suspect matches, add records, and merge records.
  • A feature for making simple updates to records by uploading a file.
  • See profile validation rules
  • A user-assigned profile that contains permissions and the profile layouts that are used when viewing HCP or HCO records.
  • An Inbox feature to help users reject or cancel add requests and change requests in bulk.
  • The process of merging duplicate records.
  • The process of changing a record state to invalid, making the record unavailable for search and match.
  • A number assigned to a record that is incremented every time that a record is updated in any way.
  • A system that consumes data exported from Network.
  • A record that is generally deemed to be a copy of an existing record in Network.
  • Permissions that provide more granular access control to custom objects by using rules that are assigned to specific users.
  • Permission criteria that uses a Network field to determine access to a custom object.
  • E
  • A high-level record attribute; in general, an HCO or HCP.
  • An alternate name for a Network entity, used to simplify a subscription configuration.
  • Characteristics or individual fields of an HCP or HCO, such as corporate name or last name.
  • Specific information about an HCP or HCO, including attributes for the entity.
  • A way to group results (similar to HCPs or HCOs) for data quality analysis; for example, hospitals in France, Nurses in Germany, or MDs in the EU.
  • A unique record identifier across all Network customers and instances. Also referred to as a VID.
  • Used to define how winning attributes will overwrite losing attributes resulting in a single customer record.
  • Writing data from a Network instance to a file. This can include HCP and HCO information as well as address, licenses and affiliations.
  • A downstream system from which Network loads data.
  • F
  • Selectable attributes within the Search filter that enable you to narrow search results.
  • A component of the match process that identifies fields to use when comparing records and determining matches.
  • A component of the match process that combines features and uses them to compare records and determine matches.
  • A version number applied to Network features to ensure that they are compatible for importing configurations to target environments. Feature versions increment each time a major enhancement of the feature is released.
  • A collection of files within a folder or archive that are processed during data load using a source subscription. They reside on the FTP site for the Network instance in which the source subscription is configured.
  • Specific information within an entity (for example, the last name of an HCP). Field types include text, numeric, reference, and date.
  • Specific information within an entity (for example, the last name of an HCP). Field types include text, numeric, reference, and date.
  • The process of creating mappings between elements of two distinct data models.
  • A read-only or edit permission assigned to specific users or user groups to provide access to a field by country.
  • The ability for users to see and manage their Network file system (FTP) from within Network.
  • In Search, a list of facets used to refine search results. Elsewhere in the Network user interface, filters enable a user to refine views and limit import or export data.
  • The primary key field from a main object that is used to reference a main object on a sub-object or relationship object. Relationship objects contain two foreign keys; one for the owner object and one for the related object in the relationship.
  • Summarized address data for entities.
  • Matching that is not exact; a comparison of similar values (for example Smith/Smyth) depending on match rules set by the customer administrator.
  • G
  • The first Concur environment created in the Concur Connector. It is automatically linked to the concur__v system.
  • H
  • Tags that are applied to profiles to help users find and summarize records.
  • Health care organization. An organization that provides health care services in a systematic way to individuals, families, or communities.
  • A classification of HCO, such as a pharmacy or hospital. HCOs are grouped into similar categories.
  • Health care provider, including (but not limited to) individuals who are authorized by their governing body to practice medicine and prescribe drugs within the scope of their defined practice.
  • Health care organization. An organization that provides health care services in a systematic way to individuals, families, or communities.
  • Health care provider, including (but not limited to) individuals who are authorized by their governing body to practice medicine and prescribe drugs within the scope of their defined practice.
  • A tiered tree of relationships between HCOs and child HCPs.
  • An integration pattern that enables users to traverse the hierarchy of a top-level HCO from a top-down approach.
  • A default view for administrators and data managers. The view contains customizable widgets that provide instant access to important data.
  • I
  • The process of changing a record state to invalid, making the record unavailable for search and match.
  • A record that has been flagged as deactivated, making it unavailable for search and match. See deactivate.
  • A page within Network that enables data stewards to find and identify tasks for review or re-assignment. The Inbox displays tasks such as change requests, suspect matches, and job notifications. Available for data steward and administrator users.
  • Custom inbox filter and column configurations that can be saved by data stewards, data managers, and administrators.
  • The process of loading, matching, and merging an external data source into Network for the first time.
  • A Network user who can only access Network functionality using the Network API; API users cannot access the Network UI. Also used for users who only need access to specific FTP directories.
  • A record that is effectively soft deleted from Network. Invalid records are not visible in Network and are not editable.
  • J
  • A user-defined event to import, export, or update data.
  • A scheduled event that can invoke actions after a job runs. A job trigger can send an email based on job outcomes or start a subsequent job when the original job successfully completes.
  • A defined set of rules ensuring that critical value changes do not occur on a large number of existing records.
  • K
  • Matching records with identical custom keys, alternate keys, or Network IDs on data load.
  • L
  • License-related information for an HCO or HCP. Granted by a recognized state or federal entity, allowing an HCP or HCO the ability to store and/or prescribe prescription pharmaceutical products.
  • Relationship objects that can have no more than one relationship per owner object.
  • An entity that is flagged as a duplicate of another entity by the match engine or a data steward.
  • For Network address inheritance in data change requests, the parent HCO that is affiliated to the entity.
  • A code or value that represents a user's geographic region or language.
  • A multi-value reference file that you can import into your Network instance and use to perform operations and validate data.
  • M
  • A subscription that defines the schedule and filters for incoming Veeva OpenData data.
  • The process of identifying records that are similar or the same.
  • A definition that determines which fields in a record are a possible match and when a record comparison is considered a suspect match. See features and feature sets.
  • The process of combining successfully matched records, or those manually identified as the same.
  • Data that provides information about data set content. In Network, this can include reference data, field mappings, and subscription configurations.
  • A link that identifies health care providers that have records in more than one country. The link displays on the record profile.
  • A Network to CRM integration that manages and maintains the CRM data subscription process for multiple countries.
  • A customer instance can subscribe to more than one master for a specific country (for example, Veeva OpenData and a third party master), which allows routing of DCRs to the appropriate master data stewards.
  • N
  • The Network application programming interface that enables developers to access Network functionality programmatically.
  • The configuration for a primary type custom field where Network determines the primary for each object. This configuration applies to address and Parent HCO objects only.
  • A customer instance of Veeva Network that contains both Veeva OpenData data (if subscribed) as well as customer-owned records and data.
  • The view in Network that graphically displays HCO and HCP affiliations.
  • A user-defined rule applied to Network data loads which can be used to apply transformations to the data during the load.
  • A customer instance of Veeva Network that contains both Veeva OpenData data (if subscribed) as well as customer-owned records and data.
  • A customer instance of Veeva Network that contains both Veeva OpenData data (if subscribed) as well as customer-owned records and data.
  • An easy and intuitive user interface for accessing Network data through predefined and custom applications.
  • A component that displays Network widgets in the Network Portal.
  • A user-defined rule applied to Network data loads which can be used to apply transformations to the data during the load.
  • O
  • A high-level record attribute; in general, an HCO or HCP.
  • Implied consent from HCPs who have not requested to opt out from Veeva Open Data. See also opt-out.
  • Direction from an HCP that their personal attributes should not be visible to those who use Veeva OpenData. Capture of opt-out requests is required by law in some countries.
  • The main object that owns the relationship between two connected main objects. Relationship records can be created on owner objects only; not the related object. Previously called "controlling object".
  • P
  • An HCO that has a relationship to a specific child HCO or HCP.
  • A custom domain for storing records such as payers, plans, and formulary. The domain can be created from your own payer/plan data model or you can quick-start from a Network template. The data model is customer-managed and be configured according to your needs.
  • The ability to provide granular application-level access to Network features for individual users or user groups.
  • Labels created for the main objects in a relationship object. The labels are used on the record profile to refer to the other object in the relationship.
  • A Network user type that has access only to the Network Portal and Network Widgets; this user type has no access to the Network application.
  • The primary affiliation of an HCP or HCO.
  • The data model field that uniquely identifies an object and that is used to associate a main object to sub-objects and relationship objects.
  • A custom domain for storing records such as brands, products, and market basket definiitions. The domain can be created from your own product data model or you can quick-start from a Network template. The data model is customer-managed and can be configured according to your needs. Search tip: Use double quotes (") to find relevant product master topics; for example: "product master".
  • The view in Network that displays all information for a particular HCP, HCO, or custom object record.
  • Specifies the arrangement of the included fields on the Profile page for each entity type by specific region.
  • A section on the Profile page that displays the notes that users can add to records so other users can see that information.
  • A defined set of rules ensuring that data is complete and accurate before DCRs can be processed. Previously called data validation rules.
  • An integration pattern that enables business users to view and update real-time data about a record from a web-based application without logging directly into the Network instance.
  • Q
  • Filters that enable a user to narrow entity search results based on values for particular fields. See facet.
  • R
  • An attribute in the data model that tracks the general state of a record, for example UNDER REVIEW, VALID, INVALID, MERGED.
  • Indicates the working status of an individual HCP or HCO; for example, Active (working) or Inactive (not working).
  • Data steward review of a record to ensure that it is up to date, complete, and correct.
  • A mapping between a Network reference code and the reference code of an external system.
  • A code used in reference data that uniquely identifies an entry in a reference code list. For example, the code A represents Active.
  • The data model and related functionality in Veeva OpenData and customer data that stores the values that appear in dropdown fields (such as specialty, country, or gender) throughout Network.
  • A mapping between a Network reference code and the reference code of an external system.
  • A collection of reference codes associated with reference fields that defines the values allowed for a field.
  • Fields for which multiple predefined values exist, in the form of reference codes.
  • A collection of reference codes associated with reference fields that defines the values allowed for a field.
  • The value assigned to an entry in a reference code list.
  • A scheduled maintenance job for Network Address Inheritance that identifies and updates out-of-sync child addresses.
  • A relationship between an HCO or HCP and another HCO.
  • A field for which the user must provide a value.
  • Comments that can be used by data stewards to explain the rejection or approval of a data change request.
  • A function to receive a record from a third party data feed again. Resubscribing to a record creates a new record in your Network instance; it does not restore the original unsubscribed record.
  • A history of changes for a record, including the time, system, and task performed on the record.
  • An object that is not dependent on another object. Root entities can be Veeva standard objects or custom objects.
  • A user-defined rule applied to Network data loads which can be used to apply transformations to the data during the load.
  • S
  • An integration pattern that enables business users to search for and view real-time data from Network and OpenData from al web-based application without logging directly into the Network instance. Records can also be added using the search widget.
  • A network protocol used for secure file transfer. Network supports this protocol for accessing folders on your FTP server
  • A user-assigned configuration that defines Network permissions and security-related preferences.
  • A time value in the Inbox to indicate how long a task has been in the Inbox.
  • A network protocol used for secure file transfer. Network supports this protocol for accessing folders on your FTP server
  • A feature that recalculates US address lines that are longer than 35 characters to ensure that the entire address is in a legiible format for delivery.
  • The process of identifying and merging duplicate records that are loaded to Network through a source subscription job.
  • A field from which a target field is mapped in a reference data mapping.
  • A file provided by an external system to load data into Network.
  • A field from which a target field is mapped in a reference data mapping.
  • A ranked list of systems in order of decreasing "trust" level.
  • An external source of data, such as Concur or SAP. A source subscription defines the data model, job scheduling, and other configuration for the data import.
  • A downstream system from which Network loads data.
  • A user who can search for, view, and submit change requests for HCPs and HCOs in Network.
  • A profile that has has been starred or favorited for quick retrieval.
  • A high confidence match between two records. Also called ACT match. ACT matches result in a merge without any human review.
  • (previously called child object) An object that depends on the existence of a root entity. Sub-objects can be Veeva standard sub-objects (addresses and licenses) or custom sub-objects.
  • A data maintenance job for finding and automatically inactivating active address, license, and Parent HCO sub-objects on inactive entities. (Previously called child object inactivation).
  • A configuration that defines data loads and exports to or from Network.
  • The process by which the final record is determined as duplicate records are merged, resulting in winning and losing values.
  • The identification of multiple records that are suspected to be duplicates of one another, but without high enough confidence for automatic resolution.
  • A system that provides customer data for mastering in Network.
  • A Network user who can access some inbox functionality as well as system configuration and user management functionality.
  • A Network user that has the combined capabilities of the data steward and system administrator users. This user has complete access to the features and functions of the Network user interface.
  • Predefined user groups that are read-only and dynamically managed by Network based on user type, status, and security policy.
  • The view in Network that displays change request and usage statistics.
  • T
  • A field to which a source field is mapped in a reference data mapping.
  • A field to which a source field is mapped in a reference data mapping.
  • Configurations that define timing and filters for data exports to downstream systems.
  • A data change or add request, suspect match, or job notification that appears in the Network Inbox.
  • A date value displayed in the Inbox to indicate when a task was created.
  • Custom fields that are created specifically to use for data stewardship purposes. The fields display on data change requests if data stewards and data managers have access to the fields.
  • A quality report that identifies a single problem or symptom of poor data quality; for example, a list of active HCPs without active addresses.
  • Data that a customer purchases 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.
  • For Network address inheritance in data change requests, the parent address at the top of the hierarchy that is affiliated to the entity.
  • The ability to use SQL queries to post-process data during the subscription process within Network.
  • U
  • A record that has not yet been validated by a data steward.
  • The configuration for a primary type custom field where users manage the primary for each object. Multiple primary fields can be configured using this configuration. It can be applied to address, license, and Parent HCO objects.
  • Relationship objects that have no limit to the number of relationships per owner object.
  • An option in target subscriptions to reveal fields for opted-out HCPs so that identifying information about the record is visible to users in downstream systems.
  • A function to remove records from a data feed so you no longer receive updates. Typically used to support GDPR or records that are no longer used.
  • An HCP or HCO record that has not yet been reviewed by a data steward and has not completed the add request process.
  • A user-assigned profile that defines the user role, data visibility profile, security profile, locale, and permissions.
  • V
  • Data steward review of a record to ensure that it is up to date, complete, and correct.
  • Veeva Connector is the feature that allows the system administrator to configure integrations between Network and other Veeva applications, such as Veeva CRM and Veeva Vault.
  • A Veeva customer relationship management product used in Life Sciences.
  • A data steward that manages updates to Veeva OpenData data.
  • A unique record identifier across all Network customers and instances. Also referred to as a VID.
  • Veeva-owned data that is shared with Network instances by subscription only.
  • Veeva-owned data that is shared with Network instances by subscription only.
  • An object that depends on the existence of an HCP or HCO that is managed by Veeva data stewards.
  • W
  • An integration pattern to embed a Network component into the Network Portal or any internal web-based application.
  • A list of Veeva IDs (VIDs) in a file that determines the initial data set to download from a Veeva OpenData instance to a customer instance.