Network MDM data model FAQs

Review the following frequently asked questions (FAQs) for the Network MDM data model.

General

What is the Veeva Network MDM Data Model?

It's the underlying structure that defines how data is organized and related within Veeva Network MDM.

What is CDA in Veeva Network MDM?

CDA stands for Customer Data Architecture. It's an industry standard (developed by Veeva) for operational data in life science companies. It is a simple set of data structures (kernels) that are small, easy to understand, and easy to implement.

How does CDA relate to the overall data model?

CDA is a key part of the data model, specifically focused on organizing data for a unified view.

Why is understanding the data model important?

It's crucial for effectively importing, exporting, reporting on, and integrating data with Veeva Network MDM.

Customizing the data model

What is the difference between a main object and a sub-object?

A main object is independent and directly associated with a data domain, such as HCPs and HCOs. A sub-object, like Addresses or Licenses, cannot exist on its own and must be associated with a main object. Custom objects can be created as either type based on your business needs.

Can I extend the data model with my own custom objects?

Yes. You can create custom domains to store data not included in the standard Veeva model, such as Product or Payer Masters. Within these domains, you can define custom main objects, sub-objects, and relationship objects to represent many-to-many connections between records.

Where can I find more details about specific data objects and fields?

The full Veeva Network MDM Data Model documentation would provide comprehensive details.

Fields and reference data

What are "grouped fields" and how do they work?

Grouped fields are sets of related standard fields, such as All Specialties (specialties 1 through 10) or All Phones. Instead of filtering individual fields, you can use the group name to query the entire set at once. These fields are typically enabled or disabled as a single unit.

How do lookup tables differ from reference data?

Reference data provides simple picklist values for a single field. Lookup tables are multi-column reference files (supporting up to 5 million rows) used for complex operations. They allow you to cross-reference data across multiple columns to calculate values, validate addresses, or cleanse data using Network Expressions (NEX).

Advanced data relationships

What is Network Address Inheritance?

Address inheritance allows a "child" record, such as an HCP, to inherit address information from a "parent" record, such as an HCO. This ensures data consistency and reduces manual entry; updates made to the parent address can automatically propagate to all associated child records.