Sections in This Article
- About Case Promotion
- Prerequisites
- Valid Case Criteria
- Promote an Inbox Item or AER to a Case
- Overview of Duplicate Detection Options
- Duplicate Case Detection (Option 1)
- Deep Duplicate Detection (Option 2 and 3)
- Complete the Potential Matches Page for Duplicate Detection Option 1 and 2
- Excluded Case States
- Considerations When Promoting an AER to a Follow-Up Case
About Case Promotion
To create a new Vault Safety Case, you can promote an existing AER or Inbox Item using the Promote to Case action.
When you initiate the Case promotion process, Vault Safety duplicate detection compares the current record against all other Cases in the system. The check is useful in the following scenarios:
- Preventing duplicate Case creation
- Creating follow-up Cases
- Copying patient information to a new Case
Note Once a Case has been created with at least one Case Adverse Event, Case Product, or Case Reporter, you cannot delete the Case record from your vault. Furthermore, you cannot delete the following primary Case child records, which the system automatically creates upon Case promotion:
- Primary Case Adverse Event
- Primary Case Reporter
- Primary Case Product
Another Case promotion method is available for Inbox Items received through an AS2 gateway Transmission, Intake API, or created from an E2B file. See Automated Case Promotion for more detail.
Prerequisites
The following checklists outline the prerequisites for promoting an Inbox Item or AER to a Case.
Inbox Item Promotion Prerequisites
- The Organization must be specified on the Inbox Item.
The Organization is required to ensure only users with permissions in that Organization can view the Inbox Item and the resulting Case. - Your vault may be configured to hide the Promote to Case action until the Inbox Item is in the Verified state.
- Your vault may be configured to hide the Promote to Case action until the following minimum case criteria fields are set:
- Identifiable Patient
- Identifiable Reporter
- One of the following:
- Country of the Primary Reporter
- Country of the Adverse Event
- Adverse Event
- One of the following:
- Study
- Company Product
AER Promotion Prerequisites
- The Organization must be specified on the AER.
The Organization is required to ensure only users with permissions in that Organization can view the AER and the resulting Case. - The following minimum case criteria fields must be set to Yes:
- Identifiable Reported Event
- Identifiable Patient
- Identifiable Reporter
- Identifiable Country
- Identifiable Company Product
Valid Case Criteria
An AER or Inbox Item should have enough information to qualify as a valid case before you promote to Case.
There are fields on the AER and Inbox Item objects to help you check whether a record has the required information to qualify as a valid case.
The following images show these fields, which are automatically populated based on the data entered on the record:
-
Note For AERs, an Administrator can configure your environment to require additional custom valid case criteria using Vault formulas.
AER Case Validity Fields -
Inbox Item Case Validity Fields
Promote an Inbox Item or AER to a Case
Once you’ve verified that an AER or Inbox Item has all the data required for a valid ICSR, you can access the Promote to Case action from the All Actions (
) menu on the record or by selecting 
.
Once you initiate the Promote to Case action, duplicate detection runs automatically.
If any information in the record matches an existing Case, the Potential Matches page appears.
If the record does not match any existing Cases, Vault Safety creates the Case and an Inbound Transmission record.
Note Your Administrator can configure your vault to display user actions to promote Inbox Items at any given lifecycle state. For example, a configuration might only allow you to promote the Inbox Item after completing the verification process, or it may allow you to promote when the Inbox Item is still in the Triage state. Refer to your standard operating procedures for more information.
Learn how Case intake and Case promotion consider Inbox Items with Combination Products.
Overview of Duplicate Detection Options
The following table provides an overview and comparison of the three duplicate search options.
| BASIC DUPLICATE DETECTION (OPTION 1) | 22R1 DEEP DUPLICATE DETECTION (OPTION 2) | 22R3 DEEP DUPLICATE DETECTION (OPTION 3) | |
|---|---|---|---|
| Search Criteria | Considers:
|
Considers:
Stricter likely and possible match tagging criteria. |
Considers:
Less strict likely and possible match tagging criteria, which provides more matching results. |
| Ranking | Potential match results are ranked from most similar to least. | Potential match results are ranked from most similar to least. | Potential match results are ranked using matching:
|
| Duplicate Actions (New Case, Copy Patient Info, Duplicate, Follow-Up, Mark as Follow-Up) | Available on Potential Matches page. | Available on Potential Matches page. | Available on Case Compare page. |
| Inbox Item Consideration | Does not look at Inbox Items for search. | Does not look at Inbox Items for search. | Considers Inbox Items if setting is enabled by an Admin. |
| AER Consideration | Considers AERs in search automatically. | Considers AERs in search automatically. | Does not look at AERs and Cases created from AERs for search. |
| AER Promotion | Supported for AER promotion. | Not supported for AER promotion. | Not supported for AER promotion. |
| Enablement | Auto-On. | Auto-On for Limited Release (the default option). Requires Veeva Support for General Release. |
Requires Veeva Support and Admin configuration. |
Note that you can only use one duplicate detection option at a time, but you may switch between all three options by contacting Veeva Support.
Duplicate Case Detection (Option 1)
During duplicate detection, Vault Safety compares the current record against all other Cases and AERs in the system to find potential matches and prevent duplicates. You’ll see the following screen while the system performs duplicate detection:
If the system detects matching information, the Potential Matches page appears.
The left pane lists all potential match Cases with similar or matching information. The returned results are ranked from the most similar (top) to least similar (bottom) match. The Comparison table lists the information for the current record side-by-side with the Case that is a potential match.
The following indicators assist with comparing information:
represents an exact match.
represents a partial match or similar information.
Review and complete the Potential Matches page to continue.
-
How Basic Duplicate Detection Works: Fields
The system looks at certain data points on each Case to determine potential matches.
When searching for duplicate Cases, the system compares information entered or received in the following fields:
Primary Product
The system compares values entered in the following fields for the primary Case Product:
- Product
- Study
- Study Product
- Study Arm
Note Note When a study Case is blinded, the system cannot compare the Study Product with other Cases.
Primary Events
The system compares values entered in the following fields for the primary Case Adverse Event:
- Event Country
- Event (Reported)
- Event (MedDRA)
- Event Onset
Patient
The system compares values entered in the following Case Patient fields:
- Patient Initials/ID
- Gender
- Date of Birth
- Age at Onset
- Gestation
- Age Group
- GP MRN
- Hospital MRN
- Investigation MRN
- Specialist MRN
Primary Reporter
The system compares values entered in the following fields for the primary Reporter Case Contact:
- Reporter First Name
- Reporter Last Name
- Reporter Country
- Reporter Qualification
Note Note When a study Case is blinded, the system cannot compare the Study Product with other Cases.
See the section below to learn more about alternative duplicate search options.
Deep Duplicate Detection (Option 2 and 3)
Deep duplicate detection considers more field values in the search than basic duplicate detection.
There are two deep duplicate search methods:
- 22R1 Deep Duplicate Detection (Option 2)
This method looks at primary and non-primary information to obtain likely and possible matches. - 22R3 Deep Duplicate Detection (Option 3)
This method uses partial matching and considers more field values in the search, providing more potential match results.
Note The 22R1 and 22R3 deep duplicate detection options are only supported for Inbox Item promotion and are not supported when promoting an AER.
22R1 Deep Duplicate Detection (Option 2)
You must contact Veeva Support to request this deep duplicate option be made available in your vault.
Deep duplicate search compares primary as well as non-primary records. For example, the system compares case information including Patient, primary and non-primary Adverse Events, Study, primary and non-primary Products, and Primary Reporter information.
Deep duplicate search can be used to determine whether each potential match is a likely match or a possible match:
if all the following are a match:
- Primary Company/Study Product
- Patient MRN OR 2 other Patient fields
- Any 2 Event fields
Note If the UID (UID, WWUID, External UID, or Case Identifiers) match, the system automatically determines the Case is a likely match. A cross compare match (for example, a WWUID matching an External UID) also results in a likely match. This cross-comparison only occurs when deep duplicate detection is enabled.
if all the following are a match:
- 2 out of the 3 likely match criteria are met
- 1 Patient field OR 1 Primary Event field OR 3 Primary Reporter fields
The returned results are ranked from the most similar (top) to least similar (bottom) match.
Review and complete the Potential Matches page to continue.
If deep duplicate search is enabled in your vault and the record does not match any existing Cases, a “No Match Found” page appears. You can select one of the following options:
- Cancel: Cancel the process and return to the Inbox Item. You can then go to the Case tab to perform a manual search for a match.
- Continue: Create a new Case and an Inbound Transmission.
-
How 22R1 Deep Duplicate Detection Works: Fields
The system looks at certain data points on each Case to determine potential matches.
When searching for duplicate Cases, the system compares information entered or received in the following fields:
Details
The system compares any AER or Inbox Item UID (WWUID, UID, External System UID and Case Identifiers) with any Case UID (WWUID, UID, External System UID and Case Identifiers).
Primary Product
The system compares values entered in the following fields for the primary Case Product:
- Product
- Study
- Study Product
- Study Arm
Note Note When a study Case is blinded, the system cannot compare the Study Product with other Cases.
Non-Primary Product
The system compares the above Product field values for up to 10 non-primary Case Products.
Primary Events
The system compares values entered in the following fields for the primary Case Adverse Event:
- Event Country
- Event (Reported)
- Event (MedDRA)
- Event Onset
Non-Primary Events
The system compares the above Event field values for up to 10 non-primary Case Adverse Events.
Patient
The system compares values entered in the following Case Patient fields:
- Patient Initials/ID
- Gender
- Date of Birth
- Age at Onset
- Gestation
- Age Group
- GP MRN
- Hospital MRN
- Investigation MRN
- Specialist MRN
Primary Reporter
The system compares values entered in the following fields for the primary Reporter Case Contact:
- Reporter First Name
- Reporter Last Name
- Reporter Country
- Reporter Qualification
Note Note When a study Case is blinded, the system cannot compare the Study Product with other Cases.
22R3 Deep Duplicate Detection (Option 3)
You must contact veeva support to request this deep duplicate option be made available in your vault. An administrator must also ensure Duplicate Search Options are enabled in your vault.
Note 22R3 deep duplicate detection does not consider AERs when searching for potential matches but can optionally consider Inbox Items, if enabled.
This duplicate search option considers more field values than option 1 and 2 in the search. This provides a more extensive list of potential matches. Records with sparse information could be considered as matching.
This method employs the Likely and Possible Match tags, but with different criteria than option 2:
A search result is tagged with when there is an ID match. For example:
- UID, WWUID, External UID, Case Identifiers
Note A cross compare match (for example, a WWUID matching an External UID) also results in a likely match. This cross-comparison only occurs when deep duplicate detection is enabled.
- Patient MRN
- Study Name
A search result is tagged with if any field value matches.
Potential match results are ranked in the following order:
- Matching Patient
- Matching Reporter
- Matching Product
- Matching Event
If enabled, you can also compare open Inbox Items to your current record on the Potential Matches page. This is a 22R3 duplicate search capability.
-
How 22R3 Deep Duplicate Detection Works: Fields
The system looks at certain data points on each Case to determine potential matches.
The 22R3 deep duplicate search considers many field values when searching for potential matches. As long as there is one field match, the Case or Inbox Item (if enabled) will be returned as a potential match. Note that AERs are not considered in this option.
The following table lists the fields considered in the 22R3 deep duplicate search:
Object Field Case Identifier ( case_identifier__v)- Case Identifier (
name__v)
Case ( case_version__v)- WWUID (
worldwide_uid__v) - UID (
uid__v) - External System UID (
external_system_uid__v) - Receipt Date (
receiptdate_date__v) - Study Number (
study_number__v) - MRN - Investigation (
mrn_investigation_value__v) - MRN - Specialist (
mrn_specialist_value__v) - MRN - Hospital (
mrn_hospital_value__v) - MRN - GP (
mrn_gp_value__v) - Patient Date of Birth (
dob_idate__v) - Patient Age Group (
age_group__v) - Patient Gender (
gender_value__v) - Patient ID (
patient_id_value__v) - Patient First Name (
patient_first_name__v) - Patient Last Name (
patient_last_name__v) - Reporter First Name (
reporter_first_name__v) - Reporter Last Name (
reporter_first_name__v) - Reporter Qualification (
reporter_qualification__v) - Reporter Country (
reporter_country__v) - Report Type (
report_type__v) - Study Type (
study__v)
Case Product ( case_product__v)- Product Reported (
product_reported__v)
Case Contact ( case_contact__v)- Reporter First Name (
firstname_value__v) - Reporter Last Name (
lastname_value__v)
Product ( product__v)- Product ID (
id)
Case Adverse Event ( case_adverse_event__v)- Event Reported (
event_reported__v)
MedDRA ( meddra__v)- MedDRA PT Codes (
pt_code__v)
Controlled Vocabulary ( controlled_vocabulary__v)- Report Type (
case_version__v.report_type__v.api_name__v) - Study Type (
case_version__v.study__v.study_type__v.api_name__v)
- Case Identifier (
The system compares any Inbox Item UID (WWUID, UID, External System UID and Case Identifiers) with any Case UID (WWUID, UID, External System UID and Case Identifiers).
Note When a study Case is blinded, the system cannot compare the Study Product with other Cases.
Complete the Potential Matches Page for 22R3 Deep Duplicate Detection
The Potential Matches page for the deep duplicate detection released in 22R3 contains different actions than for the 22R1 deep duplicate detection (option 2) and the basic duplicate detection (option 1).
The following images illustrate the Potential Matches page when comparing the current record to a Case and Inbox Item, respectively.
- In the left pane, select a Case or Inbox Item (if enabled) to compare it with the current record.
- If you selected a Case, review the details listed in the comparison table to determine whether the current record is a new Case, or a new Case with existing patient details, a duplicate of an existing Case, or a follow-up Case.
If you selected an Inbox Item, you can choose to create a new Case or mark the current record as a duplicate. - Select one of the following options after reviewing the details:
Option Description Cancel Select this option to exit the Potential Matches page and be redirected back to the current Inbox Item record. Compare Details This button is displayed when you are comparing a Case to your current record. The system directs you to the Inbox Item to Case Compare page. You can perform additional actions on this page such as: - Mark as a duplicate
- Create a new Case with existing Patient information
- Mark as Follow-Up
- Merge to Current
Note Note This option is not available for Inbox Items that are found to match a Case in the Void, Nullified, Voiding, or Nullifying lifecycle state or a Case in the lifecycle state with the Deleted state type. The Deleted state type can only be mapped to one lifecycle state.
Mark as Duplicate This button is displayed when you are comparing an Inbox Item to your current record.
Select this option if an Inbox Item is an exact match to the current record. If you select this option, the system marks the record as Duplicate and does not create a Case.Create New Case Select this option if the current record is not a duplicate of any potential matches.
If you select this option, the system creates the Case and an Inbound Transmission record.
A link to the matching record is also provided under the Likely Match or Possible Match heading. You can select the link to access the matching record for more information.
Complete the Potential Matches Page for Duplicate Detection Option 1 and 2
- In the left pane, select a Case to compare it with the current record.
- Review each Case listed in the Comparison table to determine whether the record is a new Case, a new Case with existing patient details, a duplicate of an existing Case, or a follow-up Case.
- From the drop-down list beside Possible Duplicate, select one of the following options:
Option Description New Case Select this option if the current record is not a duplicate of any potential matches.
If you select this option, the system creates the Case and an Inbound Transmission record.New Case - Copy Patient Info If the current Inbox Item includes a patient with an existing Case, select the Case, and then select New Case - Copy Patient Info.
If you select this option, in addition to creating a Case that includes the patient details, you can specify other information to copy, including the following:- Medical History
- Drug History
- Case Contacts
- Test Results
- Suspect/Interacting Products
- Concomitant Products
- Narrative
- Adverse Events to Medical History
- Concomitant Products to Drug History
See Copy Patient Information from Existing Case for more detail.Note The new Case is not linked to the original Case. However, the audit trail records which information was copied.
Duplicate If a Case is an exact match to the current record, select the Case, and then select Duplicate.
If you select this option, the system marks the record as Duplicate and does not create a Case. The system links the duplicate record to the matching Case in the Initial Case field.Follow-Up If an AER or Inbox Item is a follow-up to an existing Case, select the Case, and then select Follow-Up.
If you select this option on an Inbox Item, the system directs you to the Case Compare page. See Inbox Item Follow-Up for more detail.
If you select this option, the system promotes the AER to a Follow-Up Case. For more information, see Considerations for Follow-Up Promotion on an AER.Note This option is not available for Inbox Items that are found to match a Case in the Void, Nullified, Voiding, or Nullifying lifecycle state or a Case in the lifecycle state with the Deleted state type. The Deleted state type can only be mapped to one lifecycle state.
Mark as Follow-Up Select this option to link the Inbox Item to an In-Flight Case An open Case that has not completed case processing (generally in any state before Approved, Closed, or Superseded).
and indicate it should be merged with the Case. In order for the action to be successful, the Case must not have completed processing and can not be in a prohibited state.If you select this option, the state changes to Marked as Follow-up and a new section, Inbox Item has been marked as a follow-up, appears on the Inbox Item with a link to the associated Case. Note that an administrator must configure the Inbox Item page layout in order for this section to appear. This lets the Case Processor know there is new information on the Inbox Item that should be merged with the In-Flight Case.
If you do not see this option, an administrator must enable the Mark as Follow-up option in the Case Promotion settings.
You can undo this action by navigating back to the Inbox Item and selecting Unmark Follow-Up in the All Actions (
) menu.Note Promoted Inbox Items cannot be unlinked from the Case.
- Select Complete.
Excluded Case States
Vault Safety compares the current Inbox Item or AER with all Cases and Inbox Items or AERs linked to the same Organization, except those in the following states:
| Excluded State | Description |
|---|---|
| Superseded Cases | The system looks at the latest Case version rather than Superseded versions. |
| Promoted Inbox Items or AERs | The system looks at the promoted Case rather than the original Inbox Item or AER. |
| Duplicate Inbox Items or AERs | The system does not look at Duplicate Inbox Items or AERs because they cannot be promoted to Cases. |
| Rejected Inbox Items or AERs | The system does not look at Rejected Inbox Items or AERs because they cannot be promoted to Cases. |
Note Inbox Items are not included in the search for duplicates, unless your vault uses 22R3 Deep Duplicate Detection and has enabled this setting.
Considerations When Promoting an AER to a Follow-Up Case
The following sections describe important information to consider when you promote an AER to a Follow-Up Case, depending on how you created the follow-up AER. This section does not apply to Inbox Items.
For information on creating a Follow-Up Case from an initial Case in the Closed state, see Add a Follow-Up Case.
Promote an E2B Imported AER to a Follow-Up Case
When you promote a Follow-Up Case from an E2B-imported AER, the resulting Follow-Up Case contains only data from the E2B source file.
You must update the Follow-Up Case to add any information from the previous Case version that the E2B source file omits.
Promote a Manually Entered AER to a Follow-Up Case
When you promote a Follow-Up Case from an AER created through manual data entry, the resulting Follow-Up Case contains all data from the initial case and any additional information from the follow-up AER. You may need to correct duplicate information in the resulting Follow-Up Case.
When the Follow-Up AER contains conflicting data from the initial Case, the system reconciles certain information during case promotion.
The following list describes how Vault Safety reconciles certain fields when you promote an AER to a Follow-Up Case:
- Masked Fields: For fields with a Reason Omitted masking option, the information entered in the AER being promoted to a Follow-Up takes precedence. For example, if the initial Case specified a field value, but the follow-up masked the same field with a Reason Omitted option, the resulting Follow-Up Case blanks the field but maintains the Reason Omitted option.
- Value and Unit Fields: For the following fields, the latest data in the follow-up overwrites the value from the initial case, including null values:
- Age
- Gestation
- Height
- Weight
- Age-Related Fields: The follow-up information takes precedence over the initial case for all age-related fields, including Date of Birth, Age at Onset, and Age Group.
- Receipt Date: The receipt date remains constant across both the initial and follow-up case versions. The follow-up receipt date is recorded in the New Info Date field.
