OpenData 2.0 fields
The OpenData 2.0 data model contains the following components:
| Object | Attributes | Reference Types |
|---|---|---|
| HCP | 52 fields | 21 reference types Multivalued reference fields are supported. |
| HCO | 34 fields | 4 reference types Multivalued reference fields are supported. |
| Address | 17 fields | 4 reference types |
| Parent HCO | 8 fields | 4 reference types |
This includes fields from the following data model schemas:
-
a subset of OpenData 1.0 fields
-
a subset of Common Data Architecture (CDA) fields
-
several new fields
Field details
-
List of all OpenData 2.0 fields - For the complete list of fields, follow the OpenData communities on Veeva Connect.
Tip: To quickly identify OpenData 2.0 fields in the Customer Master domain (Data Model), filter each object using the OpenData 2.0 data model schema tag or export the data model and filter the file using the tags column.
-
Updates to OpenData 1.0 and CDA fields - For changes to existing fields included in the OpenData 2.0 data model, see the Veeva Network MDM 26R1.0 Data Governance document.
Changes to fields can include support for additional objects, updates to labels, additional country support, and more.
New fields
The following list of new fields have been added to Network MDM.
| Field Name | Field Label (EN) | Field Type | Description | Object | Managed |
|---|---|---|---|---|---|
| all_spec_local__v | All Specialties Local | Multivalued Reference Type (SpecialtyLocal) | All locally recognized medical fields or expertise areas for the healthcare professional or organization. | HCP, HCO | Veeva |
| child_entity_type__v | Child Entity Type |
Reference Type (ObjectEntityType) |
Type of the source entity (HCO or HCP). | ParentHCO | Veeva |
| child_veevaid__v | Child Entity Veeva ID |
Text |
Veeva ID of the child entity in the affiliation relationship. | ParentHCO | Veeva |
| city_intl__v | City International |
Text | The English exonym of the city or municipality (e.g., "Munich" for München). If none exists, the transliterated local name (e.g., "Tokyo" for 東京). | Address | Veeva |
| count_hcp__v | Number of Total Affiliated HCPs |
Reference Type (CountRange) |
Total number of HCPs affiliated to the HCO. | HCO | Veeva |
| count_prescriber__v | Number of Affiliated Prescribers |
Reference Type (CountRange) |
Number of HCPs with prescriptive authority affiliated to the HCO. | HCO | Veeva |
| entity_object_type__v | Entity Object Type | Reference Type (ObjectEntityType) | Veeva ID of the HCP or HCO associated with this address or license. | Address | Veeva |
| entity_veevaid__v | Entity Object Veeva ID | Text | Type of the source entity (HCO or HCP). | Address | Veeva |
| first_name_intl__v | International First Name | Text | The HCP's first name, converted to Latin script via transliteration. Used globally for searching, data matching, international correspondence, and reading by non-local staff. | HCP | Veeva |
| grad_institution__v | Graduation Institution | Text | Name of the graduation institution. | HCP | Veeva |
| hco_name_english__v
(not available for the US) |
English Name | Text | English organization name where relevant. | HCO | Veeva |
| hco_name_intl__v | International HCO Name | Text | The HCO's registered local name, converted to Latin script via transliteration. Used globally for cross-border searching, entity resolution, international reporting, and accessibility for non-local staff. | HCO | Veeva |
| hco_name_short__v | Short Name | Text | Short organization name where relevant. | HCO | Veeva |
| hco_ownership__v | Ownership | Reference Type (HCOOwnership) | Defines the ownership body of an HCO private or public. | HCO | Veeva |
| hcp_reason_status__v | Status Reason | Reference Type (HCPStatusReason) | Specifies the reason for the healthcare professional’s current status, describing their level and type of engagement in the healthcare system and distinguishing between active practitioners, contributors, and those retired or no longer involved. | HCP | Veeva |
| hcp_type_local__v | HCP Type Local | Reference Type (HCPTypeLocal) | The primary, most granular role of the HCP as it is recognized within the local healthcare system. This role spans from the development and commercialization of life science products to their delivery and administration in healthcare settings. | HCP | Veeva |
| hospital_campus_name__v
(US only) |
Hospital Campus Name | Text | Name of the hospital on whose campus this HCO is located. | Address | Veeva |
| hospital_campus_veevaid__v
(US only) |
Hospital Campus Veeva ID | Text | Veeva ID of the hospital on whose campus this HCO is located. | Address | Veeva |
| job_title__v | Job Title | Text | The job title of the source HCP associated with this affiliation. | ParentHCO | Veeva |
| last_name_intl__v | International Last Name | Text | The HCP's last name, family name or surname. Converted to Latin script via transliteration. Used globally for searching, data matching, international correspondence, and reading by non-local staff. | HCP | Veeva |
| main_org_name__v | Main Org Name | Text | Primary institution-level facility name (e.g., hospital/clinic). Acts as an HCP's main workplace or the overarching institution for a smaller HCO (e.g., 'Seattle General' for an 'Oncology Lab'). Excludes corporate parents and internal sub-units | HCO, HCP | Veeva |
| main_org_veevaid__v | Main Org Veeva ID | Text | Primary institution-level facility Veeva ID (e.g., hospital/clinic). Acts as an HCP's main workplace or the overarching institution for a smaller HCO (e.g., 'Seattle General' for an 'Oncology Lab'). Excludes corporate parents and internal sub-units | HCO, HCP | Veeva |
| middle_name_intl__v | International Middle Name | Text | The HCP’s middle or secondary given name, including patronymics or equivalent naming elements, converted to Latin script via transliteration. Used globally for searching, data matching, international correspondence, and readability by non-local staff. | HCP | Veeva |
| nhid_2__v | National Healthcare ID 2 | Text | Unique secondary national identifier assigned to healthcare professionals within a country's healthcare system. | HCP | Veeva |
| parent_veevaid__v | Parent Entity Veeva ID | Text | Veeva ID of the parent entity in the affiliation relationship. | ParentHCO | Veeva |
| postal_code_full_us__v
(US only) |
Postal Code Full US |
Text | This field is only relevant for U.S. addresses. It contains the complete, nine-digit postal code, including both the five-digit ZIP Code and the four-digit ZIP+4 Code. For example, this field would contain "90210-1234". | Address |
Veeva |
| postal_code_intl__v | Postal Code International |
Text | The extended postal format required for international correspondence, ensuring correct routing from outside the destination country. | Address |
Veeva |
| primary_affl_name__v | Primary Affiliation Name | Text | The Name of the primary, direct parent affiliation for the child HCP/HCO. | HCP | Veeva |
| primary_affl_veevaid__v | Primary Affiliation Veeva ID | Text | The Veeva ID of the corresponding to the primary, direct parent affiliation for the child HCP/HCO. | HCP | Veeva |
| spec_1_local__v | Specialty Local | Reference Type (SpecialtyLocal) | Primary, locally recognized medical field or expertise area for the healthcare professional or organization. Values are drawn from the list of local specialties. | HCO, HCP | Veeva |
| spec_2_local__v | Specialty Local 2 | Reference Type (SpecialtyLocal) | Secondary, locally recognized medical field or expertise area for the healthcare professional or organization. Values are drawn from the list of local specialties. | HCO, HCP | Veeva |
| street_address_1__v | Street Address 1 | Text | Residential or business street address information including house number and street name written in local language. Originates from primary address. | HCO, HCP | Local |
| street_address_1_intl__v | Street Address 1 International | Text | Residential or business street address information, including house number and street name, written in English. Used for international correspondence, validation, and readability by non-local staff. | Address | Veeva |
| street_address_2__v | Street Address 2 | Text | Additional address details, such as apartment, suite, or building number written in local language. Originates from primary address. | HCO, HCP | Local |
| street_address_2_intl__v | Street Address 2 International | Text | Additional address details, such as apartment, suite, or building number written in English. | Address | Veeva |
| sub_state_admin_unit__v
(available for APAC, LATAM, US & Greece) |
Region/County | Text | In the hierarchy where Country is Level 0 and State is Level 1, this defines Administrative Level 2. Examples: US County, German Kreis, UK District/Borough, Australian LGA, or Mexican Municipality. | Address | Veeva |
| top_org_name__v | Top Org Name | Text | The name of the ultimate parent organization (e.g., Global Headquarters, Health System) of the HCP's or HCO's primary affiliation. | HCO, HCP | Veeva |
| top_org_veevaid__v | Top Org Veeva ID | Text | The Veeva ID of the ultimate parent organization (e.g., Global Headquarters, Health System) of the HCP's or HCO's primary affiliation. | HCO, HCP | Veeva |
| type_of_hierarchy__v | Type of Hierarchy | Reference Type (HCOHierarchyType) | Describes the structure of the hierarchy the HCO is in (e.g. Multi-Level healthcare network or Independent Physician Association). | HCO | Veeva |
| type_of_relationship__v | Type of Relationship | Reference Type (RelationshipType) | Type of relationship between the source and the target. | ParentHCO | Veeva |
Reference types for OpenData 2.0 fields
Several of the new fields are reference type fields. New reference types and codes are added for these fields.
There are two types of reference types.
Unrestricted reference types
Custom codes can be added to these reference types. Veeva codes and custom codes can also be inactivated.
| Reference Type | Field | Object |
|---|---|---|
| HCOTypeLocal | hco_type_local__v | HCO |
| HCPTypeLocal | hcp_type_local__v | HCP |
Restricted reference types
The restricted reference types in OpenData 2.0 are read-only. Reference codes cannot be added, changed, or removed.
| Reference Type | Field | Object |
|---|---|---|
| CountRange | count_prescriber__v count_hcp__v |
HCO |
| HCOHierarchyType | type_of_hierarchy__v | HCO |
| HCOOwnership | hco_ownership__v | HCO |
| HCPStatusReason | hcp_reason_status__v | HCP |
| SpecialtyLocal | spec_1_local__v spec_2_local__v |
HCO, HCP |
Reference codes
Administrators and Data Managers can view the reference codes in the Network MDM UI (Data Model > Reference Data).