Unique identifier for the call record within the Veeva Vault system. This is typically used as the primary key for referencing individual call entries.

Indicates the Vault object type associated with this call record. This usually reflects the metadata structure or template used to define the record.

System-generated globally unique identifier (GUID) for the call record. Ensures uniqueness across environments and supports integrations.

Internal system link or reference to the full Vault record. Often used in integrations or UI redirections.

The descriptive name assigned to the call. This value can be manually set by users or generated based on a template.

Current status of the call, such as Planned, Completed, or Cancelled. This is used to track the call's lifecycle.

Username or identifier of the Vault user who initially created the call record.

Timestamp capturing when the call record was first created in the system.

Username or identifier of the user who last modified the call record. Helps with auditing and traceability.

Timestamp for the most recent update to the call record. This is useful for synchronization and audit purposes.

Field specific to Puerto Rico's ASSMCA reporting requirements. This is used to indicate call compliance with regulatory tracking.

Specifies the nature of the interaction conducted during the call, such as detailing, sampling, or discussion.

Indicates whether additional product details were provided during the call. This is typically a flag or status field.

Indicates whether key marketing or medical messages were presented during the call interaction.

First line of the address where the call took place. May contain street address or facility name.

Second line of the address for supplementary location details, such as suite number or building.

Full formatted address string combining all available address components. This is useful for display or reporting.

List of products that are authorized or permitted to be discussed or used during the call. Values are typically separated by commas.

Date and time when the call was assigned to a user or representative. Supports workload tracking and call scheduling.

Represents the status assigned to an attendee after the call, indicating follow-up actions or acknowledgments specific to their role or response.

Specifies the role or category of each attendee in the call, such as healthcare professional (HCP), sales representative, or support staff, used for classification and reporting purposes.

A comma-separated list of names or identifiers for attendees who are not healthcare professionals, such as office staff or administrative personnel, captured during the call.

Indicates the total number of attendees present at the call, including both HCPs and non-HCP participants, used for engagement tracking and compliance validation.

The expiration date of the Controlled Document Set (CDS) that was referenced or presented during the call, ensuring up-to-date materials are used in interactions.

A unique identifier or reference number assigned to the Controlled Document Set (CDS), enabling traceability and version control for materials shared during the call.

A free-text summary of any chat messages exchanged during or in relation to the call, providing context or follow-up notes about the interaction.

Represents the latitude coordinate where Closed Loop Marketing (CLM) content was launched, used for geolocation and activity auditing.

Represents the longitude coordinate where CLM content was launched, enabling precise geospatial tracking of CLM usage.

Indicates whether location services were enabled when CLM content was accessed, with values such as Enabled, Disabled, or Unavailable for audit purposes.

A boolean flag indicating whether CLM content was launched during the call, helping measure digital content engagement.

Describes the communication medium used for the call, such as In Person, Phone, Email, or Virtual, used for segmentation and analytics.

Free-text notes added by the user to provide context, observations, or remarks about the call, often used for internal reference or compliance documentation.

The date on which the call occurred, used for chronological reporting, scheduling analysis, and regulatory tracking.

The precise timestamp capturing both date and time of when the call was conducted, supporting chronological audits and activity sequencing.

Classifies the nature of the call, such as Detail, Sample Drop, or Medical Inquiry, based on predefined business rules or user input.

Represents the latitude coordinate where the user checked in for the call, supporting compliance with location-based activity tracking.

Indicates whether location services were active at the time of check-in, providing insight into data accuracy and user permissions.

Geographical longitude recorded at the time of check-in, typically captured via the device's GPS during a call event.

Status indicating whether the check-in for the call was successfully completed, pending, or failed. This is used to track user activity compliance.

Precise timestamp denoting when the check-in occurred, stored in UNIX or epoch format for accurate time-based queries.

Identifier for the subordinate or related account associated with the primary account on the call record. This is used in account hierarchies.

City associated with the call location, typically derived from the address of the facility or account visited.

Session ID for the co-browsing interaction that took place during the call. Supports remote engagement scenarios with healthcare professionals.

URL used by the participant to join a co-browse session, enabling synchronized navigation and screen sharing.

URL used by the presenter to initiate and control a co-browse session during a remote call.

Color value used to visually represent the call or its category in user interfaces such as calendars or dashboards.

Name of the Concur expense report associated with the call, linking expense data to Veeva activity.

Professional credentials of the attendee or user involved in the call, such as MD, NP, or PharmD. This is used for compliance and targeting.

Platform or system through which the call record was created, such as iPad, web, or integration API.

Primary street address where the DEA-registered activities took place, used in validation of controlled substance interactions.

Secondary address field for DEA registration, capturing additional location information if needed.

City portion of the address associated with the DEA-registered facility or professional.

Expiration date of the DEA registration, used to verify whether prescribers are authorized at the time of call.

State code from the address of the DEA-registered site, used for jurisdictional validation.

The extended ZIP code (ZIP+4) for the DEA address, improving postal accuracy and regional tracking.

Base ZIP code of the DEA-registered address, used in location-based reporting and filtering.

Represents the Drug Enforcement Administration (DEA) registration number associated with the healthcare provider involved in the call. This number is used to uniquely identify entities authorized to prescribe or handle controlled substances.

List of all individual products discussed or promoted in detail during the call, as recorded in the call entry.

Name or identifier of the recipient to whom the disbursement was made during or as part of the call activity.

Indicates whether a disbursement order was successfully created in association with this call record (true or false).

Text of any legal or compliance disclaimers associated with the call, which can be required for regulatory or promotional purposes.

Length of the call in minutes, capturing the total time spent in the interaction from start to finish.

System-generated or external reference identifier that uniquely links this call to another business entity or external system.

Total cost of the call-related expenses incurred, recorded in the user's default currency or the organization's primary reporting currency.

Corporate-recorded amount of call-related expenses used for internal financial reporting and audit tracking, stored in the system currency.

The currency code (such as USD, EUR, JPY) used locally at the time of expense entry or disbursement.

Categorization of the attendee in relation to the expense, such as 'employee', 'healthcare professional', or 'other external participant'.

Status of the expense posting workflow, indicating whether the expense is pending, posted, rejected, or processed in the finance system.

Indicates the current receipt status for the associated expense, such as 'required', 'received', or 'not required'.

Unique identifier for the call-related expense as registered in an external financial or accounting system.

Specifies whether an actual cost was incurred during the call (true), or if the entry is informational only (false).

Indicates whether this call involved the distribution of product samples, typically for compliance tracking and reporting (true or false).

URL link provided to participants to access remote CLM sessions or presentations during the call.

URL used by the presenter to initiate or manage a remote CLM session during the call.

Universally unique identifier assigned to the remote CLM session, ensuring traceability across devices and platforms.

System-generated identifier for the remote Closed Loop Marketing session linked to the call record.

Identifier or name of the last known device used to log, edit, or submit the call record, used for audit and tracking purposes.

Name of the platform or application (such as iPad, CRM UI, or integration system) used to last modify this call record.

The expiration date of the license associated with the user or product for this call, which can affect sample eligibility or activity permissions.

Indicates the current licensing status of the user or healthcare provider at the time of the call, such as Active, Suspended, or Expired. This status can be used to validate compliance or restrict certain call actions.

Represents the license number of the professional, typically a physician or medical representative, involved in the call. This value is used to verify credentials and regulatory compliance.

A unique identifier linking this call record to an external system or integration, enabling cross-system traceability of activities or communications.

Email address of the originator or sender associated with the call entry, typically used in integrations or audit tracking involving email-based workflows.

System-generated or externally assigned identifier that denotes the origin entity or user initiating the call record. This is useful for tracing data lineage.

A unique internal identifier representing the physical or virtual location where the call took place. This can relate to specific offices, hospitals, or remote settings.

Reflects the operational status of location services at the time of the call, indicating whether geolocation tracking was enabled, disabled, or unavailable.

Textual representation of the location where the call occurred, such as a clinic name, city, or address. This field complements the Location Id field for display purposes.

System reference field storing the location metadata in raw or internal format. May be used in system integrations or rule-based processing.

Describes the topics or products discussed during the call that are classified under medical or scientific content. This can include therapeutic areas, treatments, or medical inquiries.

Timestamp indicating when the call record was originally created on the mobile device, providing traceability for offline or field activity logging.

Unique identifier assigned to the call record by the mobile application. Often used to reconcile mobile-generated data with centralized Veeva Vault records.

Indicates the most recent time the call record was edited or updated from the mobile device, allowing tracking of field activity updates.

Free-form text entered by the representative summarizing plans, expectations, or action items for the next scheduled call. Often reviewed in follow-up engagements.

Boolean flag indicating whether no disbursement of materials, samples, or other items took place during the call. This is used for compliance and audit controls.

Specifies whether a user manually bypassed a locking mechanism on the call record, typically due to an approved exception or administrative override.

Identifier linking the call record to the parent address record, such as the primary clinic or physician office location. This is used for hierarchy navigation.

Phone number associated with the call, often the recipient's office or mobile contact. This is used for reference and follow-up validation.

Mobile identifier of the parent call if the current entry is part of a multi-call sequence or follow-up chain. Supports data lineage and grouping.

Narrative notes entered prior to the call, typically outlining objectives, topics to be discussed, or prior engagement context. Aids in call preparation.

Comma-separated list of presentation identifiers or names shown during the call, typically referencing approved marketing or scientific content shared with the attendee.

Numerical field capturing an additional attribute or calculated metric related to the call. This can represent a configurable score, rating, or financial metric depending on organizational use.

Specifies the email address designated to receive a digital receipt following the completion of the call. This is typically used to confirm transactions or interactions with healthcare professionals.

Captures the full name of the attendee who provided a signature remotely. This is relevant for virtual meetings where electronic signatures are collected for compliance or verification.

Indicates whether a signature was successfully captured using a QR code-based method during the call. True if captured, false otherwise.

Indicates whether the user requested a receipt to be generated and sent for the interaction. A value of true reflects a positive request.

Represents the formal title or greeting associated with the attendee, such as Mr., Mrs., Dr., or other culturally appropriate honorifics.

Provides the rationale or justification for issuing a physical or digital sample card during the call, which can be required for auditing or regulatory compliance.

Contains the unique identifier or number associated with the issued sample card. This is used for tracking and validation purposes.

Indicates whether a transaction was automatically created due to sample limit thresholds being met or exceeded during the call. Helps ensure sample compliance.

Specifies the identifier for the sample send card, which is used to facilitate sample shipments or transfers as part of the call.

Contains the ASSMCA number (from Puerto Rico's mental health and addiction services administration) associated with the shipping destination, if applicable.

Represents the first line of the street address where the materials or samples are to be shipped. This is typically the primary delivery location.

Optional second line of the shipping address, used for additional location details such as suite number, floor, or building name.

Specifies the expiration date of the Controlled Dangerous Substances (CDS) license for the shipping destination. Ensures compliance with controlled substance regulations.

Holds the CDS license number for the recipient address. This number is used to validate the shipment of controlled substances.

Indicates the name of the city where the shipping destination is located.

Specifies the name of the country for the shipping address. Required for international shipping and regulatory purposes.

Denotes the expiration date of the DEA (Drug Enforcement Administration) license associated with the shipment recipient. This is used to verify authorization to receive regulated products.

Contains the DEA registration number of the shipping recipient. This number is required for shipments involving controlled substances in the United States.

Indicates the date on which the recipient's professional or facility license expires. This is used to confirm that the recipient is currently authorized to receive shipments.

Describes the current status of the recipient's license, such as Active, Suspended, or Expired, to determine eligibility for shipments.

Provides the license number associated with the shipping recipient, which can be required for validation and auditing.

Stores a unique identifier for the shipping location, typically used internally to reference a validated address or site.

Gives the full name or description of the location where the shipment is being sent, such as a clinic name or practice site.

Shows the expiration date of the recipient's state-level distributor license, which can be required for legal distribution within certain states.

Contains the name or identifier of the state distributor license holder at the shipping location. Required for state-specific regulatory tracking.

Identifies the U.S. state or equivalent regional authority for the shipping address.

Holds the 4-digit ZIP code extension (ZIP+4) that provides more precise delivery location information within the ZIP code area.

Represents the 5-digit ZIP code for the shipping address, used for standard postal delivery.

Indicates whether the signature was obtained remotely using a compliant virtual signing method, such as via remote detail or tele-detail call functionality.

Specifies whether the signature was collected through a secure shared link, allowing the recipient to sign externally without direct login to the system.

The date and time when the signature was officially recorded in the system. This value is captured in the local time of the signing device or environment.

Latitude coordinate of the location where the signature was captured, typically using the device's GPS for geolocation logging.

Longitude coordinate corresponding to the geographic location of the signature event, supporting audit trail and compliance tracking.

The display-friendly name of the page on which the signature appears, typically shown in the user interface or reports for clarity.

A reference or path to the stored image of the page containing the captured signature, which can be stored as a document or binary blob.

A precise timestamp (usually in milliseconds since epoch) denoting when the signature action was executed, used for synchronization and audit purposes.

The electronic representation or encoded value of the signature captured, which can include metadata, hash, or a base64-encoded image string.

Indicates whether the interaction qualifies as a significant event under compliance or regulatory standards, such as a major milestone or agreement.

Unique identifier associated with the state distributor's address record within the Vault system, used for linking and integration.

Primary address line for the state distributor location, typically includes street name and number.

Secondary address line for additional location details such as suite, building, or floor, if applicable.

Name of the city where the state distributor is located, used for geographic reporting and routing.

The expiration date of the distributor's license or authorization to operate within the respective state, used for compliance validation.

Two-character state abbreviation or full name representing the U.S. state in which the distributor is registered.

The extended ZIP code (ZIP+4 format) for the distributor's address, enhancing location precision for delivery and reporting.

The standard 5-digit ZIP code of the state distributor's registered address.

The official name or code representing the authorized distributor within a specific U.S. state jurisdiction.

Represents the U.S. state or Canadian province in which the activity or entity is located, used for regional reporting and jurisdictional compliance.

Current status of the call record such as Completed, Cancelled, In Progress, or Planned, used for workflow tracking and operational reporting.

The primary topic, agenda, or purpose of the call, often aligned with the visit objective or discussion focus.

Latitude coordinate where the call submission occurred, typically collected from the mobile device during finalization.

Longitude coordinate associated with the physical location where the call was submitted to the Vault platform.

Indicates whether device location services were enabled or disabled at the time of call submission, used to validate geolocation accuracy.

High-precision timestamp capturing the exact moment the call data was submitted to Vault. This can be used for ordering and tracking submissions.

Boolean flag that indicates whether the call record was submitted using a mobile device rather than through the web interface.

The rationale or justification behind the submitted suggestion, typically provided by the user to support process improvements or feedback.

A concise title or summary for the suggestion provided, aiding in categorization and follow-up analysis.

Credentials or qualification identifiers for the supervising physician associated with the call, such as MD, DO, or NP.

License number or registration identifier of the supervising physician overseeing the call or associated medical activity, used for compliance tracking and credential verification.

Full name of the supervising physician associated with the call, typically used for documentation, reporting, and medical oversight purposes.

Sales or operational territory in which the call occurred, mapped to regional assignments for performance analysis and coverage tracking.

Total number of individuals who attended the call, including HCPs and internal participants, used for calculating engagement levels and compliance with regulations.

Indicates whether the call record is currently unlocked and available for editing by users with the appropriate permissions.

External system identifier used to link the Veeva Vault record with a corresponding entry in an external clinical system or integration platform.

Represents the source or initiating location of the call, often referring to an originating user, team, or virtual location.

Boolean flag that determines whether the call data should be transmitted to Vault Clinical for integration with clinical trials or study data.

Unique identifier for the Veeva-hosted remote meeting session associated with this call, used for linking virtual call metadata such as duration and participants.

Extended 4-digit ZIP code suffix that provides more granular postal information for the call location, typically used for address validation and targeting.

Primary 5-digit ZIP code representing the geographic location where the call occurred or was logged.

Reference to the strategic account plan associated with this call, used to align the call objectives with broader commercial or clinical goals.

Primary account or healthcare provider organization involved in the call, used for attribution, Customer Relationship Management (CRM) reporting, and engagement history.

User or system entity that assigned the call to a field rep or user, typically used for workload distribution and ownership tracking.

Sub-account or affiliated healthcare provider under the main account hierarchy, relevant for complex account structures and field activity segmentation.

Indicates the co-browsing interaction performed during the call, capturing shared digital interactions such as product detailing or information display.

Name or identifier of the visual or digital presentation shared during a co-browse session or remote meeting.

Represents a linked Event Management (EM) event, if the call is associated with an organized activity such as a speaker program or congress.

Identifier of another call record referenced due to an error or correction in data entry, supporting audit trails and data integrity.

Descriptive name of the physical or virtual location where the call was held, useful for reporting and logistical insights.

Refers to a medical event (such as an adverse event or product complaint) logged during or related to the call, for pharmacovigilance or compliance.

Indicates whether a medical inquiry was made during the call, typically linked to Medical Information Requests (MIRs).

Flag or reference indicating whether the call originated from a formal meeting request by the HCP or other stakeholders.

Parent account entity that controls or oversees the current account, providing context for enterprise-level account management.

Mailing or physical address of the parent account, used for correspondence and hierarchical reporting.

Identifier of the parent call, if this record represents a follow-up or child interaction under a larger call engagement.

Primary product prioritized for discussion or detailing during the call, typically ranked based on marketing strategy or HCP interest.

Second-tier product prioritized for inclusion in the call agenda or promotional discussion.

Third-ranked product considered for discussion during the call, based on rep planning or previous engagement data.

Fourth-ranked product listed for potential coverage during the call, often optional depending on time or interest.

Indicates the fifth level of product prioritization for the call, typically used to rank detailing order when multiple products are discussed.

Specifies whether the call was conducted remotely, and can include details such as platform or method of virtual communication.

References the primary account responsible for the shipment destination, typically used in tracking controlled product distribution.

Captures the designated shipping address where materials or samples associated with the call are sent.

Represents a specific internal or external location identifier associated with the ship-to address, often used for inventory and compliance tracking.

Contains recommendations or feedback generated during the call, either from the attendee or representative, for future engagement or action.

Identifies the supervising physician associated with the call, relevant for tracking medical oversight and regulatory compliance.

Refers to the internal Veeva user or representative who conducted or recorded the call activity.

Holds the unique identifier of the user or team who owns or is responsible for managing the call record.

Specifies whether and when a reminder was set for the call, which can aid in scheduling follow-up activities or tasks.

Stores the attendee's preferred name for personalization in communication and documentation.

Contains the credentials or professional titles of the call attendee, such as MD, DO, PharmD, relevant for reporting and compliance.

Displays a formatted name for the primary entity associated with the call, used in user interfaces or reports.

Indicates whether this call record serves as a parent in a hierarchical call structure, typically used in group call scenarios.

Stores an alternative or formatted version of the shipping address for enhanced display or postal compliance.

Specifies whether a signature was captured and synchronized from a remote session or device, important for digital consent tracking.

Represents the overall lifecycle phase of the call record, such as Planned, Submitted, or Approved.

Defines the current state within the call lifecycle, used to control visibility, workflow, and permissions.

Holds the internal identifier for the lifecycle stage of the record, used by system workflows and transitions.

Indicates the display label of the current stage in the record lifecycle, which helps users understand progress visually.

Boolean flag that indicates whether the call involves a unique group activity, typically used to prevent duplicate reporting in group settings.

Stores a universally unique identifier for the signature request, enabling secure tracking and validation across systems.

Holds the original identifier from a legacy CRM system, allowing for historical data reference and migration tracing.

Contains metadata or tags related to specific detail sections within the call, used to drive conditional logic or analytics.

Specifies the category of remote meeting, such as Webex, Zoom, or other virtual platforms, to support meeting type analytics.

Indicates the recommended communication channel for the call, such as Face-to-Face, Phone, or Email, typically suggested by the system or rep.

Stores the system- or user-suggested date and time for the next call, based on rules, preferences, or prior interactions.

Captures the system- or user-suggested date for a follow-up or future call, often based on past engagement or targeting logic.

Indicates whether Microsoft Teams was used as the remote meeting platform, often relevant for compliance, reporting, or integrations.

Specifies the address associated with the prescriber's DEA (Drug Enforcement Administration) registration, used for compliance tracking and regulatory reporting.

Represents the unique identifier of the account associated with the call, typically used for linking call records to account master data.

Indicates the top-level parent account or organization associated with the call, used to group calls under a common corporate or hierarchical structure.

Indicates whether the target person or account was unavailable for scheduling at the time of the call attempt. A value of true prevents future call scheduling until availability is updated.

Specifies the country where the user who logged the call is located. This is used for localization, reporting, and compliance with country-specific regulations.

Represents the country where the associated account resides, which can influence call eligibility, product restrictions, or regulatory compliance.

Identifies the individual (for example healthcare provider or contact) targeted in the call record. This value links the interaction to a person-level entity within Veeva Vault.

Captures the exact date and time when a system or user action triggered the creation or update of the call record, typically used for auditing and time-based reporting.

Records any specific interest expressed by the target during the call, such as interest in a product, service, or follow-up, allowing for personalized engagement planning.

Represents a derived field that calculates the communication channel (for example face-to-face, phone, video) used during the call, based on a combination of input data and predefined business logic.