Compass
Compass provides claims data at the patient, prescriber, procedure, and diagnosis level. The Compass connector data model supports the updated data model in the Compass 22R1 release.
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.
| Column Name | Type | Description |
|---|---|---|
| query_id__v | numeric(10) | ID generated for each scheduled data pull. This is ID indicating the overall ongoing, scheduled data pull. Scheduled monthly jobs will have the same Query ID, different Job IDs. One-time pulls will have one Query ID to one Job ID. |
| job_id__v | numeric(10) | ID generated for each job run |
| record_id__v | varchar(38) | Unique ID for each record |
| record_type__v | varchar(3) | Indicates whether the transaction is a Prescription or Medical Claim. This field can be used to filter to RX or MX records. Data attributes are expected to be populated based on Record Type (Column B) column in this Data Dictionary. |
| prescription_num__v | varchar(18) | Hashed identifier for the original prescription number generated by the pharmacy for each prescription. A prescription filled more than once will have the same Prescription Number. In these cases, Fill Number should be used to differentiate the dispenses. |
| claim_id__v | varchar(32) | Identifier for the medical claim. This identifier is hashed to ensure HIPAA compliance. A medical claim contains unique medical codes detailing the care administered during a patient visit. The medical codes describe any service that a provider used to render care, including, a diagnosis, procedure, medical supplies, medical devices, and medical transportation.A group of medical claims may have the same Claim ID when it has multiple procedures and diagnosis. In these cases, Charge Line Number should be used to differentiate the service lines. |
| charge_line_number__v | bigint | Identifier for each line of the claim, unique within each Claim ID |
| transaction_date__v | date | Date the prescription is dispensed or the service was provided |
| transaction_day__v | varchar(2) | Day the prescription is dispensed or the service was provided |
| transaction_month__v | varchar(2) | Month the prescription is dispensed or the service was provided |
| transaction_year__v | varchar(4) | Year the prescription is dispensed or the service was provided |
| patient_id__v | varchar(20) | Unique patient ID, persistent across data pulls |
| age__v | varchar(5) | Age of patient at the time of transaction in 5-year age brackets |
| year_of_birth__v | varchar(4) | Year of birth of the patient |
| gender__v | varchar(1) | Gender of the patient |
| zip3__v | varchar(3) | ZIP3 (first 3 digits of ZIP code) of the patient |
| state__v | varchar(2) | State of patient based on patient’s ZIP3 |
| product_id__v | varchar(19) | National Drug Codes (NDC) of the product or medical supply product ID associated with the claim |
| product_name__v | varchar(100) | Product name given to the group of Product IDs, managed by Veeva Data Cloud.For branded products, product name represents the brand name given by the manufacturer.For generic products, product name is the generic name of the product. |
| product_desc__v | varchar(100) | More descriptive product name |
| product_category__v | varchar(50) | Categorizes whether the product is generic or branded |
| compound_name__v | varchar(100) | Generic product name, representing the way that physicians typically refer to generic products, including active ingredients without salt/chemical/ester forms and product label names |
| ta1__v | varchar(100) | Primary, broadest, therapeutic area of the product. Therapeutic areas were created by Data Cloud to help facilitate research and analytics objectives. |
| ta2__v | varchar(200) | Secondary therapeutic area of the product. Therapeutic areas were created by Data Cloud to help facilitate research and analytics objectives. |
| ta3__v | varchar(255) | Tertiary, most granular, therapeutic area of the product. Therapeutic areas were created by Data Cloud to help facilitate research and analytics objectives. |
| otc__v | varchar(1) | Flags whether the product 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 product |
| company_name__v | varchar(255) | Company responsible for packaging of the product |
| route__v | varchar(50) | Description of route of administration, indicating how the product is received by the patient |
| dose_form__v | varchar(100) | The physical form of a dose of the product |
| product_j_code__v | varchar(6) | J-code related to the product. Product J-Code is not sourced from claims data and is enriched by Data Cloud based on the Product |
| obsolete_datetime__v | date | This field contains data only if a 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 |
| num_authorized_refills__v | numeric(2) | The number of refills provided in the prescription authorized by the provider |
| days_supply__v | numeric(3) | Number of days the product was supplied to the patient in the prescription |
| 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) | Number of days or units associated with the medical services, e.g. the number of hospital days, miles, pints of blood, kidney dialysis treatments. |
| unit_of_measure__v | varchar(2) | Provides the measurement for the Quantity Dispensed on the products dispensed, or Units of Service for service provided |
| unit_of_measure_desc__v | varchar(20) | Description of Unit of Measure |
| line_charges__v | numeric(18,2) | The amount submitted by the provider for payment for each line of service |
| place_of_service__v | varchar(2) | Two-digit codes indicating the setting where a service was provided or a product was dispensed |
| place_of_service_desc__v | varchar(1023) | Description of Place of Service |
| telehealth__v | varchar(1) | Flags whether the visit is conducted remotely |
| hcp_id__v | varchar(35) | Rendering Provider NPI. Represents the HCP that wrote the prescription on Prescription Claims. Represents the HCP that performed the treatment and/or made the diagnoses on Medical Claims. |
| hcp_vid__v | varchar(18) | Rendering HCP Veeva ID. It can be used to integrate with all Veeva systems, including CRM, Link, and OpenData. |
| hcp_specialty_1__v | varchar(200) | Primary Specialty for the Rendering HCP, provided by Veeva OpenData |
| hcp_specialty_2__v | varchar(200) | Secondary Specialty for the Rendering HCP, provided by Veeva OpenData |
| referring_hcp_npi__v | varchar(15) | NPI of the HCP who directed the patient for care to the HCP rendering the services being reportedThe attribute is enriched using OpenData. |
| referring_hcp_vid__v | varchar(18) | Veeva ID for the referring HCPVeeva 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 Link. |
| referring_hcp_specialty_1__v | varchar(200) | Primary Specialty for the Referring HCP, provided by Veeva OpenData |
| referring_hcp_specialty_2__v | varchar(200) | Secondary Specialty for the Referring HCP, provided by Veeva OpenData |
| facility_npi__v | varchar(15) | The NPI of the site where the patient was diagnosed and/or treated |
| facility_vid__v | varchar(18) | The Veeva ID of the site where the patient was diagnosed and/or treated |
| billing_provider_npi__v | varchar(15) | The NPI of the billing entity responsible for billing a patient for healthcare services |
| billing_provider_vid__v | varchar(18) | The Veeva ID of the billing entity responsible for billing a patient for healthcare services |
| procedure_code__v | varchar(5) | Code of the procedure performed. Codes may be any of the 3 terminologies: Current Procedural Terminology (CPT), Healthcare Common Procedure Coding System (HCPCS), or Health Insurance Prospective Payment System (HIPPS) codes. |
| procedure_code_desc__v | varchar(300) | Procedure Code Description |
| 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 description |
| diagnosis_code_2_desc__v | varchar(255) | Diagnosis code 2 description |
| diagnosis_code_3_desc__v | varchar(255) | Diagnosis code 3 description |
| diagnosis_code_4_desc__v | varchar(255) | Diagnosis code 4 description |
| diagnosis1_class1__v | varchar(255) | Primary, broadest, category of diagnosis for diagnosis_code_1 |
| diagnosis1_class2__v | varchar(255) | Secondary, more granular, category of diagnosis for diagnosis_code_1 |
| diagnosis2_class1__v | varchar(255) | Primary, broadest, category of diagnosis for diagnosis_code_2 |
| diagnosis2_class2__v | varchar(255) | Secondary, more granular, category of diagnosis for diagnosis_code_2 |
| diagnosis3_class1__v | varchar(255) | Primary, broadest, category of diagnosis for diagnosis_code_3 |
| diagnosis3_class2__v | varchar(255) | Secondary, more granular, category of diagnosis for diagnosis_code_3 |
| diagnosis4_class1__v | varchar(255) | Primary, broadest, category of diagnosis for diagnosis_code_4 |
| diagnosis4_class2__v | varchar(255) | Secondary, more granular, category of diagnosis for diagnosis_code_4 |
| diagnosis_icdtype__v | varchar(5) | Type of ICD code corresponding to Diagnosis Code 1 (Primary Diagnosis) |
| payer_name_primary__v | varchar(100) | Name of the primary payer. A primary payer is the insurer that pays a healthcare bill first. |
| payer_name_secondary__v | varchar(100) | Name of the secondary payer. A secondary payer covers remaining costs not covered by primary payer. |
| payment_type_primary__v | varchar(30) | Description of payment type for the primary payer. This attribute is available for both RX and MX records. |
| payment_type_secondary__v | varchar(30) | Description of payment type for the secondary payer |
| payment_subtype_primary__v | varchar(75) | Description of payment subtype for the primary payer, more granular than Primary Payment Type |
| payment_subtype_secondary__v | varchar(75) | Description of payment subtype for the secondary payer, more granular than Secondary Payment Type |
| payer_amount_paid_primary__v | numeric(13,2) | Total amount to be paid by the primary payer |
| payer_amount_paid_secondary__v | numeric(13,2) | Total amount to be paid by the secondary payer |
| patient_pay_amount__v | numeric(13,2) | The amount the patient paid out of pocket |
| num_payers__v | numeric(10) | Number of payers that covered the claim. Multiple payers can contribute to covering the cost of the product or service provided, e.g. a claim can be covered by two payers, first Medicare, then a commercial payer covers the remaining cost. |
| diagnosis_composite__v | varchar(100) | Concatenation of the four diagnosis codes for easier searching |
| patient_claim__v | varchar(100) | Unique patient claim identifier |
| pateint_presc_num__v | varchar(100) | Unique patient prescription identifier |
| raw_filename__v | varchar(100) | Filename |
