Configuring Statement Validation (Veeva Claims)

Veeva Claims provides users with the abilty to automatically check the full text content of a claim statement against a list of flagged words and phrases when you create claims statements. Certain words or phrases are “high risk” when used in product statements and need to be “flagged”. Usage of such words or phrases in statements may leave consumer goods organizations exposed to legal and regulatory risks.

Depending on your configuration, Vault checks either the Statement in each Statement or Claim record against the list of Admin-defined Flagged Words or Phrases, but the process will not check both objects. Based on the results, Vault automatically populates the Statement Validation Status field on each applicable record. Vault also creates relationships between the Flagged Words or Phrases records and the matching Statement or Claim records. These relationships allow you to see which problematic words or phrases are found in each claim. If your Vault includes a statement library, Vault validates text on Statements only because Claims are created from Statements.

Your organization can maintain its own list of flagged or prohibited words. You can also use entry criteria to enforce policies around limitations of use of such language in the claim statements. Statement validation is available in all Veeva Claims Vaults, but you must define Flagged Words or Phrases records so that Vault knows which terms to check for statement validation.

Statement Validation Objects

Veeva Claims uses the following core objects to support Statement Validation:

Flagged Words or Phrases (prohibit__v): This object represents defined words or phrases that need to be flagged and includes information about reasons and suggestions for avoiding the risky phrase. Each word or phrase is an object record.
Statement (statement__v): This object represents the standalone desired messaging.
Statement Prohibit Join (statement_prohibit_join__v): This object joins the Statement and Flagged Words or Phrases objects. The object is not editable, and you won’t interact with it, or its records, directly. All users, even Admins, have only Read access to this object.
Claim (claim__v): This object represents an individual claim and includes information about the statement, the footnote (fine print), and which product uses the claim.
Claim Prohibit Join (claim_prohibit__v): This object joins the Claim and Flagged Words or Phrases objects. The object is not editable, and you won’t interact with it, or its records, directly.
Claim Validation Stats (claim_validation_stats__v): This object represents statistics on the affected Statement or Claim records. Vault uses these records to track each time you create, edit, or delete Flagged Words or Phrases records. This object is not editable, and you won’t interact with it, or its records, directly.

Statement Validation Object Fields

The Statement and Claim objects include the following fields to support Statement Validation:

Statement Validation Required? (validation_required__v): This field controls whether or not Vault will validate the claim statement.
Statement Validation Status (validate__v): This field indicates the result of validation. See the list of statuses. This field is not editable.

Configuration Overview

Configuring your Vault to use Statement Validation involves the following steps:

Define flagged words and phrases
Enforce statement validation
Configure user permissions

Note: Depending on your Vault’s creation date and which features are currently enabled and configured, some of the steps described in this article may be unavailable or already complete in your Vault.

Defining Flagged Words & Phrases

To define a word or phrase for statement validation, you must create the applicable Flagged Words or Phrases records. To do this:

Navigate to Business Admin > Objects > Flagged Words or Phrases.
Click Create.
Enter the Flagged Word or Phrase, for example, “treat” or “cure”. This is the value that Vault will match within statements on Statement or Claim records. This field is limited to 1,500 characters and is not case-sensitive.
Enter a Reason why this word or phrase is flagged. This reason appear to users when validating statements. This field is limited to 1,500 characters.
Enter Alternative Suggestions. These suggestions appear to users when validating statements.
Optional: Set the Status to Inactive. By default, new records are active. If you do not want it to become effective immediately, you can make it inactive.
Click Save. To create another flagged word or phrase, click Save + Create.

Enforcing Statement Validation on Statements or Claims

When your lifecycle configuration includes entry criteria, Vault automatically checks a record before allowing it to enter a specific state. You can ensure that claims with high-risk statements are not approved using entry criteria. For example, you can create an entry criteria on the Approved state of the Claims Lifecycle to check that Statement Validation Status equals Validated. No Prohibited Word Found before allowing a record to enter Approved state. For Vaults using a statement library, you can enforce the same entry criteria in the Statement Lifecycle.

Note: Entry criteria prevent records from entering a specific lifecycle state. They have no effect on records that are already in a given state. In the above example, no invalid records could enter Approved state, but there may already be records in that state.

Configuring User Permissions

You must ensure users have the appropriate read and create permissions to access the appropriate objects and object fields in addition to the permissions outlined below:

Read permission on the Claim Prohibit Join, Flagged Words or Phrases, and Statement Prohibit Join objects.
Create and Edit permission on the Claim and Statement objects.

You can complete all the steps in this article with the standard System Administrator or Vault Owner security profile. If your Vault uses custom security profiles, your profile must grant the following permissions: