Learn how to configure coding verification for Company Product matching upon E2B and API import.
About Company Product Match Verification
In 23R2, Vault Safety now supports a more advanced Product match coding verification. When an intake user imports an E2B or JSON file to Inbox Item, Vault Safety performs Product matching using certain criteria.
This feature allows you to configure Product coding criteria to consider additional Product matching scenarios. Vault Safety verifies whether the imported Inbox Item meets the Product coding criteria and determines whether to proceed with Product matching.
For more information, see Inbox Item Study and Product Matching: Company Product Match Verification.
Prerequisites
You must first enable this feature in the Intake Settings.
Must Match and Should Match Confidence Outcomes
When importing an E2B or JSON file to Inbox Item, Vault checks the Inbox Item’s primary Company Product information with that on the library Product’s Registrations. This data includes the fields you set in the Must Match and Should Match picklists (Country, Route of Administration, and Dose Form). If the product’s Country Obtained is not provided, Vault attempts to match the Country using the primary reporter’s Country.
The following table displays the possible Product match outcomes and their Product Match Coding criteria:
| IMPORTED INBOX ITEM PRIMARY PRODUCT <> LIBRARY PRODUCT MATCHING | PRODUCT MATCH CONFIDENCE |
|---|---|
One of the following fields matches between the Inbox Item primary Product Registration and the library Product's Registration:
|
1 - Exact Match |
| All Must Match fields and Should Match fields exist on the Inbox Item and match a single Product Registration. | 2 - Confident Match |
| All Must Match fields exist on the Inbox Item and match a single Product Registration, but a Should Match field does not exist on the Inbox Item. | 3 - Likely Match |
| All Must Match and Should Match fields exist on the Inbox Item, but at least one (1) Should Match field does not match the Product Registration common to the Must Match fields. | 4 - Unlikely Match |
| At least one (1) Must Match field is missing or doesn't match the same Product Registration. | 4 - Unlikely Match |
| On the Intake Settings page, both the Must Match and Should Match fields are not configured. | 5 - Unknown |
| The Inbox Item does not contain an MPID, PHPID, or Registration Number. Or, the Inbox Item primary Product Name did not match to a library Product. | 6 - No ID or Name Match |
Product Match Verification Diagrams
The diagrams in this section illustrate how Vault Safety determines whether to auto-code the Inbox Item Company Product. Review the sections below to learn about successful and unsuccessful Company Product matches.
Successful Match
The following diagram illustrates a successful Company Product match:
Import the E2B or JSON file from an external system to Vault Safety.
On the Admin > Intake Settings page, the Product Coding criteria are as follows:
- Must Match: Country
- Should Match: Dose Form and Route of Administration
- Auto code min Product Confidence level: 2 - Confident Match
From the Must Match and Should Match Confidence Outcomes, achieving a 2 - Confident Match requires that all Must Match fields and Should Match fields exist on the Inbox Item and match a single Product Registration.
Vault Safety attempts to match the Inbox Item primary Company Product with a library Product by comparing the Registration information.
Vault determines the Must Match and Should Match fields exist on the Inbox Item and these fields match a Product Registration in the Product library. The resulting Product Match Confidence is therefore 2 - Confident Match.
On the Intake Settings page, the Auto code min Product Confidence level was set to 2 - Confident Match.
Since the Vault-determined Product Match Confidence met the confidence level threshold set by your Admin, the Inbox Item Company Product can be auto-coded to the library Product.
Unsuccessful Match
The following diagram illustrates an unsuccessful Company Product match:
Import the E2B or JSON file from an external system to Vault Safety.
On the Admin > Intake Settings page, the Product Coding criteria are as follows:
- Must Match: Country
- Should Match: Dose Form and Route of Administration
- Auto code min Product Confidence level: 2 - Confident Match
From the Must Match and Should Match Confidence Outcomes, achieving a 2 - Confident Match requires that all Must Match fields and Should Match fields exist on the Inbox Item and match a single Product Registration.
Vault Safety attempts to match the Inbox Item primary Company Product with a library Product by comparing the Registration information.
Vault determines the Must Match fields (Country) exist on the Inbox Item and match a library Product Registration. However, although all the Should Match fields (Dose Form and RoA) exist on the Inbox Item, one (1) of them (RoA) does not match that on the library Product Registration. The resulting Product Match Confidence is therefore 4 - Unlikely Match.
On the Intake Settings page, the Auto code min Product Confidence level was set to 2 - Confident Match.
Since the Vault-determined Product Match Confidence did not meet the confidence level threshold set by your Admin, the Inbox Item Company Product field is left blank.