Common Data Architecture for Life Sciences (CDA)
The Common Data Architecture for Life Sciences (CDA) is a new industry standard for referring to HCPs, HCOs, clinical operations, and products and diseases.
All life sciences organizations can use CDA to communicate and collaborate more effectively with each other using these universal data components.
The HCP Kernel is currently supported.
For more information about this open standard, see veeva.com/cda/.
Key highlights
-
CDA is freely available for all life sciences organizations to implement and use.
-
Vault CRM, Network, and OpenData are adopting the CDA HCP Kernel at the same time.
-
The CDA HCP Kernel will contain the following components: entities (HCPs, Addresses), attributes, and picklists.
Note: The Segment object from the HCP CDA Kernel is not currently added to Network.
-
For existing customers that integrate with Veeva CRM, there are no changes; CDA fields will be off by default.
-
OpenData will provide values for most CDA fields on the HCP and Address objects on OpenData records.
-
For locally managed (gray) records and third party managed records, Network provides the ability to calculate CDA fields based on the legacy fields.
-
Data change requests can be submitted for CDA fields.
About the CDA in Network
In Network, the CDA HCP Kernel supports the following components:
-
Entity - HCP
-
Attributes - 50 new fields (HCP, Address). All fields contain the
_cda__vsuffix. -
Picklists - New reference types and reference codes. Multivalued reference fields are supported.
CDA fields
There are 50 CDA fields for the HCP kernel.
The CDA fields do not impact the legacy fields. Many CDA field values may be calculated based on the existing legacy fields.
| Field Name | Field Label | Field Type | Description |
|---|---|---|---|
| Veeva ID | veevaid__v | Text | Global identifier from Veeva data products |
| First Name (CDA) | first_name_cda__v | Text | Given name as officially recorded in professional or legal documents. |
| Last Name (CDA) | last_name_cda__v | Text | Family or surname as officially recorded in professional or legal documents. |
| Middle Name (CDA) | middle_name_cda__v | Text | Secondary given name or initial as officially recorded in professional or legal documents. |
| Prefix (CDA) | prefix_cda__v | Text | Salutation or title used before a person's name, such as Mr., Mrs., Dr., etc. |
| Suffix (CDA) | suffix__cda__v | Text | Includes professional credentials or generational titles such as I, II, III, IV, but excludes medical degrees. |
| Primary Language (CDA) | language_cda__v | Reference Type | Primary spoken and written language. |
| Primary Email (CDA) | email_cda__v | Text | Primary email address. |
| Mobile Phone (CDA) | mobile_phone_cda__v | Text | Primary mobile phone number. May include country code including non-alphanumeric characters. e.g. +, - |
| Office Phone (CDA) | office_phone_cda__v | Text | Primary office phone number. May include country code including non-alphanumeric characters. e.g. +, - |
| Fax (CDA) | fax_cda__v | Text | Primary fax. May include country code including non-alphanumeric characters. e.g. +, - |
| Country (CDA) | country_cda__v | Reference Type | Country from primary address. |
|
State (CDA)
(HCP field) |
state_cda__v | Reference Type | State, province, or regional area from primary address. |
| City (CDA)
(HCP field) |
city_cda__v | Text | City or municipality from primary address. |
| Postal Code (CDA)
(HCP field) |
postal_code_cda__v | Text | Postal code from primary address. May include non-alphanumeric characters. e.g. - |
| Type (CDA) | hcp_type_cda__v | Reference Type | The role an individual plays in the life sciences industry, spanning from the development and commercialization of life science products to their delivery and administration in healthcare settings. |
| National Healthcare ID (CDA) | nhid_cda__v | Text | Unique identifier assigned to healthcare professionals within a country's healthcare system. |
| Primary Specialty (CDA) | spec_1_cda__v | Reference Type | The primary medical field or expertise area to which the healthcare professional belongs. Uses the list of specialties. |
| All Specialties (CDA) | all_spec_cda__v | Multivalued Reference Type | All medical fields and expertise areas to which the healthcare provider belongs. Uses the list of specialties. |
| Primary Specialty Group (CDA) | spec_group_1_cda__v | Reference Type | The primary overarching medical field or expertise area to which the healthcare provider belongs. Uses the list of global specialties. |
| All Specialty Groups (CDA) | all_spec_group_cda__v | Multivalued Reference Type | All overarching medical fields and expertise areas to which the healthcare provider belongs. Uses the list of global specialties. |
| Prescriber (CDA) | prescriber_cda__v | Boolean | Indicates whether the individual is authorized to prescribe medications. |
| Primary Medical Degree (CDA) | degree_1_cda__v | Reference Type | The primary medical qualification or degree obtained. |
| All Medical Degrees (CDA) | all_degree_cda__v | Multivalued Reference Type | Additional medical qualification or degree obtained. |
| Status (CDA) | status_cda__v | Reference Type | Indicates whether the healthcare professional is currently active and working or not. |
| Level | level_cda__v | Reference Type | Indicates the level of importance of this individual to the company, where level 5 indicates the highest level of importance. Can be used to drive business rules. For example: You may want to limit personalized promotions to levels 3 and below. You may also require a single relationship owner for level 5. |
| Adopter Type | adopter_type_cda__v | Reference Type | A categorization of the individual based on their willingness and speed to adopt new medical technologies, treatments, practices, or products. |
| Key Opinion Leader | kol_cda__v | Boolean | Recognized as a key opinion leader in the industry. |
| Investigator | investigator_cda__v | Boolean | Indicates whether the individual is involved in running clinical research studies. |
| Speaker | speaker_cda__v | Boolean | Indicates whether the individual is engaged in speaking roles at professional gatherings or educational events for the company. |
| Target | target_cda__v | Boolean | Indicates whether the individual is a target for one or more brands of the company. |
| Year of Birth (CDA) | year_of_birth_cda__v | Number | Birth year of the HCP. |
| Age Range (CDA) | age_range_cda__v | Reference Type | Age range of the HCP. |
| Street Address 1 (CDA) | street_address_1_cda__v | Text | Residential or business street address information including house number and street name. |
| Street Address 2 (CDA) | street_address_2_cda__v | Text | Additional address details, such as apartment, suite, or building number. |
| Country (CDA) | country_cda__v | Reference Type | Name of country. |
| State (CA)
(Address field) |
state_cda__v | Reference Type | Name of state, province, or regional area. |
| City (CDA)
(Address field) |
city_cda__v | Text | Name of city or municipality. |
| Postal Code (CDA)
(Address field) |
postal_code_cda__v | Text | May include non-alphanumeric characters. |
| Latitude (CDA) | latitude_cda__v | Number | Geographic coordinate specifying north-south position. |
| Longitude (CDA) | longitude_cda__v | Number | Geographic coordinate indicating east-west position. |
| Phone (CDA) | phone_cda__v | Text | Phone number. May include country code including non-alphanumeric characters. e.g. +, - |
| Fax (CDA) | fax_cda__v | Text | Fax number. May include country code including non-alphanumeric characters. e.g. +, - |
| Status (CDA) | status_cda__v | Indicates whether this address is currently usable for contact purposes. | |
| Business (CDA) | business_cda__v | Boolean | Indicates whether this represents a business address. |
| Home | home_cda__v | Boolean | Indicates whether this represents a home address. |
| Billing | billing_cda__v | Boolean | Indicates whether this represents a billing address. |
| Shipping | shipping_cda__v | Boolean | Indicates whether this represents a shipping address. |
| Sample Shipping | sample_shipping_cda__v | Boolean | Indicates whether this represents a shipping address that can accept medical shipments. |
| Primary (CDA) | primary_cda__v | Boolean | Indicates whether this represents the individual's primary address. Only one address can be marked as Primary. |
For more details, see CDA fields.
CDA Sync Calculation
Network will continue to support the existing data model and the new CDA data model. CDA Sync is a process that runs in the backend on your Network instance to calculate the values from the Veeva fields to the CDA fields.
For more details, see CDA Sync.
Vault CRM - Network integration.
Vault CRM, Network, and OpenData are supporting the CDA HCP Kernel at the same time, so you can view and manage CDA fields between these applications.
Supported integration features
-
Network Account Search
-
Vault CRM Bridge
-
Data change requests
For information about CDA and Vault CRM, see the Data Model Updates for the Common Data Architecture for Life Sciences topic in the Vault CRM Online Help.
Enable CDA in Network
New customers
CDA fields are enabled and implemented by default in new Network instances so new customers can use the standardized data structure for these applications from the start.
Existing customers
CDA fields will be available in existing instances, but they will not be enabled by default.
Administrators can enable CDA fields for their Network instance when they are ready to begin adopting this new standard.
To enable CDA for your existing Network instance:
-
In the Admin console, click Settings > General Settings.
-
Click Edit.
-
In the Common Data Architecture (CDA) Data Model section enable the following settings:
-
Enable CDA Sync - Sync calculated CDA fields with legacy fields in your Network instance.
This setting enables the CDA Sync Calculation and turns on the workflow process for the CDA data model.
Only impacts enabled CDA fields that are locally managed.
Note: This setting does not need to be enabled in your instance to get data from OpenData in CDA fields.
-
Enable CDA Data Model - Enable all CDA data model fields.
This setting cannot be turned off after it has been enabled. Individual fields can be turned off in the data model.
-
-
Save your changes.