Veeva Data Cloud

Veeva Data Cloud provides claims data at the patient, prescriber, procedure, and diagnosis level.

Table name: vdc_longitudinal_patient__v

A vdc-landing-zone directory is available in the Nitro primary S3 bucket where VDC data can be loaded for all customers who use Nitro as their data access location.

Field Field Type Description
instance_id__v numeric(10) Identifier for the customer instance ID that was used for the job.
license_id__v numeric(10) Identifier that indicates the unique (per instance) license ID that was used for the job. There can be multiple License IDs under a single Instance ID across pulls.
query_plan_id__v numeric(10) Identifier that indicates the unique (per instance) query ID that was used for the job. There can be multiple Query IDs under a single License ID across pulls.
job_id__v numeric(10) Identifier that indicates a unique (per instance) job number given to the data request. There can be multiple Job IDs under a single Query ID across pulls.
query_record_id__v varchar(38) Crossix generated unique ID per record
record_type__v varchar(3) Indicates whether the patient transaction is an Rx (Rx) or Medical Claims (MC) record
prescription_num__v varchar(18) Hashed prescription number
transaction_date__v Date (YYYY-MM-DD) Date the Rx is dispensed or the service was provided (YYYY-MM-DD)
transaction_day__v varchar(2) Day the Rx is dispensed or the service was provided
transaction_month__v varchar(2) Month the Rx is dispensed or the service was provided
transaction_year__v varchar(4) Year the Rx is dispensed or the service was provided
patient_id__v varchar(20) Unique patient identifier
age__v varchar(5) Age of patient at the time of data pull in age brackets, e.g.0-5,…80-84,85+
gender__v varchar(1) Gender of patient, i.e.'F' - Female'M' - Male
zip3__v varchar(3) ZIP3 of patient
state__v varchar(2) State of patient. Mapped from patient’s ZIP3
claim_id__v varchar(18) Hashed ID for the medical claim
product_id__v varchar(19) ID identifying the product. Most of the IDs are National Drug Codes (NDC). Other values include Universal Product Codes (UPC) and Healthcare Common Procedure Coding System (HCPCS)
product_desc__v varchar(100) Drug names as they appear on labels of drug products
compound_name__v varchar(100) Generic drug name, representing the way that physicians typically refer to generic drugs, including active ingredients without salt/chemical/ester forms and drug label names
product_name__v varchar(200) Name of the Brand family as organized by Crossix.If the brand is branded, then Brand Name is the same as Brand Description, e.g. HumiraIf the brand is generic, then Brand Name is the brand description and drug name (compound description), e.g. Lipitor (atorvastatin)
ta1__v varchar(100) Primary, broadest, therapeutic area of the drug corresponding to the product_id.Therapeutic areas were created in-house to help facilitate research and analytics objectives.
ta2__v varchar(200) Secondary therapeutic area of the drug associated with the product_id.Therapeutic areas were created in-house to help facilitate research and analytics objectives.
ta3__v varchar(255) Tertiary, most granular, therapeutic area of the drug associated with the product_id.Therapeutic areas were created in-house to help facilitate research and analytics objectives.
branded_generic__v varchar(1) Flags whether the NDC is generic or branded
otc__v varchar(1) Flags whether the NDC is over the counter
strength__v varchar(255) Strength of the product including unit of measure
active_ingredient__v varchar(255) The full salt/chemical name of all active ingredients of the drug product
source_desc__v varchar(255) Drug labeler. A labeler may be either a manufacturer, including a repackager or relabeler, or, for drugs subject to private labeling arrangements, the entity under whose own label or trade name the product will be distributed.
route_desc__v varchar(100) Path by which a drug, fluid, poison, or other substance is taken into the body, e.g. oral, injectable, implant
dose_form_desc__v varchar(100) Form in which they are marketed for use
product_j_code__v varchar(6) J-code related to the product based on reference data on the drugs. The J-code does not come in from the claims data, and does not indicate that this is a medical claims record.
obsolete_datetime__v Date (YYYY-MM-DD) This field contains data only if a drug product is no longer manufactured. It will contain the date when the product became obsolete
fill_number__v numeric(2) Number of times a patient has filled this prescription associated with this claim, e.g. 0 = NRx, 1 = 1st time refill
num_authorized_refills__v numeric(2) The number of refills provided in the prescription
days_supply__v numeric(3) Number of days the product was supplied to the patient in the prescription i.e. 30
qty_dispensed__v numeric(10,3) Describes the amount of product dispensed in the transaction or the amount of service provided
units_of_service__v numeric(10,3) Related to a drug administered, e.g. Number of injections
unit_of_measure__v varchar(2) Unit of measure for the drug dispensed or service provided
unit_of_measure_desc__v varchar(20) Description of unit of measure
patient_opc__v numeric(13,2) The amount the patient paid out of pocket
total_payment__v numeric(13,2) Total amount to be paid by the claims processor (i.e. pharmacy receivable).
charge_line_number__v bigint A sequential line number to distinguish distinct services that are submitted on the same claim
line_charges__v numeric(18,2) The amount submitted for the line of service, not necessarily the amount paid
place_of_service__v varchar(2) Code that identifies categories of entity where the service(s) were provided.The code is mapped to Place of Service Description.
place_of_service_desc__v varchar(1023) Describes the categories of entity where the service was provided, e.g. “Pharmacy”, “Group Home”, “In Patient hospital”.Mapped from Place of Service.
hcp_id__v varchar(35) Rendering Provider ID, i.e. prescription written, procedure performed, diagnosis made. Most IDs are NPI numbers, but could also be state licenses and DEA numbers. Most Rendering Providers are HCPs, but can also be HCOs such as group practice.Note: If user is an OpenData customer, this attribute will be 0 across all records. Please use HCP ID OpenData instead.
hcp_vid__v varchar(18) Veeva ID for rendering HCP.Veeva ID is the unique ID created and maintained by Veeva to identify individual HCPs. It can be used to integrate with all Veeva systems, including CRM, Vault, and OpenData.Note: If user is an OpenData customer, this attribute will be 0 across all records. Please use HCP VID OpenData instead.
hcp_specialty_1__v varchar(200) Rendering HCP primary specialtySource: OpenDataNote: If user is not an OpenData customer, this attribute will be 0 across all records. Please use HCP Specialty 1 Classification and HCP Specialty 1 Specialization instead.
hcp_specialty_2__v varchar(200) Rendering HCP secondary specialtySource: OpenDataNote: If user is not an OpenData customer, this attribute will be 0 across all records. Please use HCP Specialty 1 Classification and HCP Specialty 1 Specialization instead.
hcp_specialty_1_classification__v varchar(200) Rendering HCP primary specialty classification, broader than specializationSources: CMS/Center for Medicare, National Uniform Claim CommitteeNote: If user is an OpenData customer, this attribute will be 0 across all records. Please use HCP Specialty 1 OpenData instead.
hcp_specialty_1_specialization__v varchar(200) Rendering HCP primary specialty specialization, narrower than classificationSources: CMS/Center for Medicare, National Uniform Claim CommitteeNote: If user is an OpenData customer, this attribute will be 0 across all records. Please use HCP Specialty 1 OpenData instead.
hcp_specialty_2_classification__v varchar(200) Rendering HCP secondary specialty classification, broader than specializationSources: CMS/Center for Medicare, National Uniform Claim CommitteeNote: If user is an OpenData customer, this attribute will be 0 across all records. Please use HCP Specialty 2 OpenData instead.
hcp_specialty_2_specialization__v varchar(200) Rendering HCP secondary specialty specialization, narrower than classificationSources: CMS/Center for Medicare, National Uniform Claim CommitteeNote: If user is an OpenData customer, this attribute will be 0 across all records. Please use HCP Specialty 2 OpenData instead.
referring_hcp_npi__v varchar(15) NPI of the HCP who directed the patient for care to the HCP rendering the services being reported
referring_hcp_vid__v varchar(18) Veeva ID for the referring HCP.Veeva ID is the unique ID created and maintained by Veeva to identify individual HCPs. It can be used to integrate with all Veeva systems, including OpenData, CRM, and Vault.
referring_hcp_specialty_1__v varchar(200) Referring HCP primary specialtySource: OpenDataNote: If user is not an OpenData customer, this attribute will be 0 across all records. Please use Referring HCP Specialty 1 Classification and Referring HCP Specialty 1 Specialization instead.
referring_hcp_specialty_2__v varchar(200) Referring HCP secondary specialtySource: OpenDataNote: If user is not an OpenData customer, this attribute will be 0 across all records. Please use Referring HCP Specialty 2 Classification and Referring HCP Specialty 2 Specialization instead.
referring_hcp_specialty_1_classification__v varchar(200) Referring HCP primary specialty classification, broader than specializationSources: CMS/Center for Medicare, National Uniform Claim CommitteeNote: If user is an OpenData customer, this attribute will be 0 across all records. Please use Referring HCP Specialty 1 OpenData instead.
referring_hcp_specialty_1_specialization__v varchar(200) Referring HCP primary specialty specialization, narrower than classificationSources: CMS/Center for Medicare, National Uniform Claim CommitteeNote: If user is an OpenData customer, this attribute will be 0 across all records. Please use Referring HCP Specialty 1 OpenData instead.
referring_hcp_specialty_2_classification__v varchar(200) Referring HCP secondary specialty classification, broader than specializationSources: CMS/Center for Medicare, National Uniform Claim CommitteeNote: If user is an OpenData customer, this attribute will be 0 across all records. Please use Referring HCP Specialty 2 OpenData instead.
referring_hcp_specialty_2_specialization__v varchar(200) Referring HCP secondary specialty specialization, narrower than classificationSources: CMS/Center for Medicare, National Uniform Claim CommitteeNote: If user is an OpenData customer, this attribute will be 0 across all records. Please use Referring HCP Specialty 2 OpenData instead.
facility_npi__v varchar(15) The NPI of the site where the service was performedNote: If user is an OpenData customer, this attribute will be 0 across all records. Please use Facility NPI OpenData instead.
facility_vid__v varchar(18) Veeva ID for the Facility, including Healthcare OrganizationNote: If user is an OpenData customer, this attribute will be 0 across all records. Please use Facility VID OpenData instead.
billing_provider_npi__v varchar(15) Veeva ID of the billing entity responsible for billing a patient for healthcare services. The billing provider can also be servicing, referring, or prescribing provider.Note: If user is not an OpenData customer, this attribute will be 0 across all MX records. Please use Billing Provider VID instead.
billing_provider_vid__v varchar(18) Veeva ID of the billing entity responsible for billing a patient for healthcare services. The billing provider can also be servicing, referring, or prescribing provider.Note: If user is an OpenData customer, this attribute will be 0 across all MX records. Please use Billing Provider VID OpenData instead.
procedure_code__v varchar(5) CPT or HCPCS code of procedure performed.
procedure_code_desc__v varchar(100) Procedure Code Description.Only HCPCS codes have descriptions. Source: CMS/Center for Medicare.
procedure_code_modifier1__v varchar(2) Used to supplement information or provide care descriptions for procedure codes to provide extra details concerning a procedure or service provided by a physician, without changing the definition
diagnosis_code_1__v varchar(15) ICD-9/ICD-10 code for primary diagnosis
diagnosis_code_2__v varchar(15) ICD-9/ICD-10 code for secondary diagnosis
diagnosis_code_3__v varchar(15) ICD-9/ICD-10 code for tertiary diagnosis
diagnosis_code_4__v varchar(15) ICD-9/ICD-10 code for fourth diagnosis
diagnosis_code_1_desc__v varchar(255) Diagnosis code 1 descriptionSource: CMS/Center for Medicare
diagnosis_code_2_desc__v varchar(255) Diagnosis code 2 descriptionSource: CMS/Center for Medicare
diagnosis_code_3_desc__v varchar(255) Diagnosis code 3 descriptionSource: CMS/Center for Medicare
diagnosis_code_4_desc__v varchar(255) Diagnosis code 4 descriptionSource: CMS/Center for Medicare
diagnosis1_class1__v varchar(255) Primary, broadest, category of diagnosis for diagnosis_code_1.The class category is sourced from CMS/Center for Medicare based on Crossix defined logic.Class 1 is the diagnosis description of the first 3 digits of the diagnosis code.
diagnosis1_class2__v varchar(255) Secondary, more granular, category of diagnosis for diagnosis_code_1.The class category is sourced from CMS/Center for Medicare based on Crossix defined logic.Class 2 is the diagnosis description of the first 4 digits of the diagnosis code.
diagnosis2_class1__v varchar(255) Primary, broadest, category of diagnosis for diagnosis_code_2.The class category is sourced from CMS/Center for Medicare based on Crossix defined logic.Class 1 is the diagnosis description of the first 3 digits of the diagnosis code.
diagnosis2_class2__v varchar(255) Secondary, more granular, category of diagnosis for diagnosis_code_2.The class category is sourced from CMS/Center for Medicare based on Crossix defined logic.Class 2 is the diagnosis description of the first 4 digits of the diagnosis code.
diagnosis3_class1__v varchar(255) Primary, broadest, category of diagnosis for diagnosis_code_3.The class category is sourced from CMS/Center for Medicare based on Crossix defined logic.Class 1 is the diagnosis description of the first 3 digits of the diagnosis code.
diagnosis3_class2__v varchar(255) Secondary, more granular, category of diagnosis for diagnosis_code_3.The class category is sourced from CMS/Center for Medicare based on Crossix defined logic.Class 2 is the diagnosis description of the first 4 digits of the diagnosis code.
diagnosis4_class1__v varchar(255) Primary, broadest, category of diagnosis for diagnosis_code_4.The class category is sourced from CMS/Center for Medicare based on Crossix defined logic.Class 1 is the diagnosis description of the first 3 digits of the diagnosis code.
diagnosis4_class2__v varchar(255) Secondary, more granular, category of diagnosis for diagnosis_code_4.The class category is sourced from CMS/Center for Medicare based on Crossix defined logic.Class 2 is the diagnosis description of the first 4 digits of the diagnosis code.
diagnosis_icdtype__v varcahr (25) Type of ICD code corresponding to Diagnosis Codes, i.e. whether the code is ICD-9 or ICD-10 code
payment_type__v numeric(2) Method of payment code. Used to map to Payment Type Description. Specifically,1 - Cash - Money or an equivalent, as a check, paid at the time of making a purchase2 - Medicare - The federal program providing health insurance for people aged 65 and older and for disabled people of all ages3 - Medicaid - A program, financed jointly by the federal government and the states, that provides health coverage for mostly low-income women and children as well as nursing-home care for low-income elderly4 - Manufacturer program - Rebate programs and drug company patient assistance programs, such as Vouchers, Coupons, Patient Assistance and Discount Cards5 - Commercial/other - Prescription health insurance program provided by a for-profit, private insurance agency or companynull - Unknown
payment_type_desc__v varchar(20) Description of payment type. Values include, Cash, Medicare, Medicaid, Manufacturer program, Commercial/other
num_payers__v numeric(10) Number of payers in the transaction
raw_filename__v varchar(100) The name of the file which contained this record when it was loaded into Nitro