Configuring Statement Validation (Veeva Claims)

Certain words or phrases are “high risk” when used in product claim 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. When creating claims statements in Veeva Claims, this feature provides users with an automated way to check the full text content of a claim statement against a list of flagged words and phrases. This feature runs on either the Statement object or the Claim object, but not both. If your Vault’s configuration includes a statement library, text is validated on Statements only because Claims are created from Statements.

Statement validation is available in all Veeva Claims Vaults, but you must define records for the Flagged Words or Phrases object. Before defining words and phrases, there are no terms for statement validation to check.

Each organization can maintain its own list of flagged or prohibited words. Organizations can also use entry criteria to enforce policies around limitations of use of such language in the claim statements.

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:

Defining flagged words and phrases
Enforcing statement validation
Configuring 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 that Veeva Claims should use for statement validation, you create a new record in the Flagged Words or Phrases object.

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 Veeva Claims 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 will appear later for users who are validating statements. This field is limited to 1,500 characters.
Enter Alternative Suggestions. These suggestions will appear later for users who are 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. In Veeva Claims, you can ensure that claims with high-risk statements are not approved using entry criteria.

As an example, you could create an entry criteria on the Approved state (in 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 a record from entering a 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.

See Configuring Entry Criteria for details about how to set up entry criteria.

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: