) icon in the filter's header.
Note: Contact your Admin for more information about the standard fields on the Inbox Item object to better understand which fields you can search and filter by on the Inbox tab.
) menus. Some of the default _Inbox Item_ lifecycle states include:
* **New**: _Inbox Item_ is not yet promoted to a _Case_.
* **Import Error**: _Inbox Item_ import has failed. The user who initiated the import can view the error message in the import notification.
* **Rejected**: _Inbox Item_ rejected during intake. In this state, the _Inbox Item_ is closed to prevent further processing or _Case_ promotion.
* **Marked as Follow-Up**: _Inbox Item_ is associated with a _Case_ but is not included in that version. You can merge it into the active version or promote it to a new version.
* **Marked as Follow-Up (Not Current)**: _Inbox Item_ generated by the Safety-EDC Connection is associated with a _Case_ that is also associated with a more recent _Inbox Item_.
* **Superseded**: _Inbox Item_ is associated with a _Case_ that is also associated with a more recent _Inbox Item_, which Vault promoted instead of the superseded record.
* **Verification**: _Inbox Item_ is ready for verification.
* **Processing**: _Inbox Item_ is in the process of being automatically promoted to an initial or follow-up _Case_.
* **Missing Information**: _Inbox Item_ is missing information and cannot be promoted to a _Case_.
* **Duplicate**: _Inbox Item_ detected as a duplicate prior to _Case_ promotion. In this state, the _Inbox Item_ is closed to prevent further processing or _Case_ promotion.
* **Promoted**: _Inbox Item_ successfully promoted to a _Case_. Vault archives promoted _Inbox Items_ 180 days after the last record update. You cannot modify archived records.
* **Promotion Failed**: _Inbox Item_ failed automated _Case_ promotion due to not meeting the conditions for being marked as a follow-up _Case_ or created as a follow-up _Case_.
## Data Validation {#validation}
Vault validates _Inbox Item_ field values during data entry. When you save a record, Vault displays messages so you can correct any missing or invalid data. Additional validations may occur during _Case_ promotion according to your Vault's configuration. You cannot save _Inbox Items_ or verify _Inbox Item_ sections that do not meet all of the applicable criteria, including values for all required fields and the following:
* **Dates**: The following rules apply to all date fields:
* Cannot be more than one day in the future. This rule supports data entry in different timezones.
* Must be later than `1800/01/01`.
* The _Date of Death_ must be later than the _First Admin Date_, _Last Admin Date_, _Adverse Event Onset_ and _Cessation_ dates, as well as all dosage administration dates.
* The _Last Admin Date_ must be later than the _First Admin Date_.
* The _Cessation_ date must be later than the _Onset_ date.
* Minimum precision required for _New Info Date_ is the day.
* **Ranks**: Only one entry per section can be assigned a _Rank_ of _1_ (primary), including _Products_, _Events_, and _Reporter_ types of _Case Contacts_.
* The primary _Product_ must have a value specified in the _Product_ field, as reported by the source.
* **Unit Fields**: All numeric unit fields must specify both a value and unit, or neither.
* **Awareness Details Section**: Each _Inbox Item_ must specify _New Info Date_ and _Report Type_.
* **Events Section**: Each _Event_ must specify a _Type_.
* **Contacts Section**: Each _Inbox Item_ can have only one _Patient_ type of _Case Contact_. If needed, you can include additional details in the _Patient_ section.
## Seriousness and Priority Calculation {#seriousness}
_Cases_ should be processed in a timely manner based on their priority. When there is a high volume of _Cases_, it is crucial to determine _Case_ priority quickly. Vault calculates the _Priority_ and _Seriousness_ of an _Inbox Item_ based on the top-ranked adverse event according to the following order, which you can edit as needed:
| Order | Priority | Seriousness |
| --- | --- | --- |
| 1 | _P1_ | _Results in death_ |
| 2 | _P1_ | _Life threatening_ |
| 3 | _P2_ | _Caused / prolonged hospitalisation_ |
| 4 | _P2_ | _Disabling / incapacitating_ |
| 5 | _P2_ | _Congenital anomaly / birth defect_ |
| 6 | _P2_ | _Other medically important condition_ |
| 7 | _P3_ | Blank |
Vault considers the following when calculating priority and seriousness:
* Vault assigns _P3_ priority to _Inbox Items_ without seriousness criteria and one or more associated adverse events.
* Depending on your Admin's configuration, _Required Intervention to Prevent Permanent Impairment/Damage (Devices)_ may be an available _Seriousness_ value on _Cases_ with _Devices_ and _Combination Products_. Vault excludes this value when calculating _Seriousness_ and _Priority_ on _Inbox Items_ and _Overall Case Seriousness_ on _Cases_. When automatically ranking _Case Adverse Events_, Vault considers this value to be less serious than _Other medically important condition_, but more serious than a blank _Seriousness_ value.
* When you update the _Priority_ value without changing any other adverse event information, Vault retains the manually updated _Priority_ value. However, if you update, add, or delete the _Event_, Vault recalculates the _Priority_ upon saving the _Inbox Item_.
## Import Suggestions {#import-suggestions}
For imported _Inbox Items_, Vault generates suggestions to assist with processing and verification. Vault identifies suggestions with a lightbulb () icon, along with a confidence calculation and rationale, which you can edit as needed. Vault generates the following suggestions:
* [_Priority_][1] of _Inbox Item_
* _Drug Role_ and [_Rank_][2] for _Products_
* _Event Country_ for _Events_
### Product Rank Calculation {#product-rank}
Vault calculates and suggests _Product_ rank for imported _Inbox Items_ based on the following:
* **Rank 1**: Assigned to the first imported _Product_ with a _Drug Role_ of _Suspect_, _Interacting_, or _Drug Not Administered_ that matches to a product. If there is no _Suspect_ drug, Vault assigns this rank to the first imported _Product_ with a matching product. Vault assigns this rank to a single record and checks for a product match in the following sequential order:
1. _Study Product_
2. _Study Product Placeholder_
3. _Company Product_
* **Rank 2**: Assigned to all other _Products_ with matching _Study Products_, _Study Product Placeholders_, or _Company Products_.
* **Rank 3**: Assigned to all other _Products_.
## Localization {#localization}
Depending on your Admin's configuration, Vault may populate the _Localization_ field based on reporter locale:
* If you populate the _Site Reporter_ field of the _Inbox Item_, Vault populates the _Localization_ based on the reporter's _Country_ and _Reporter Language_.
* If your Admin has configured the _Enable auto-set Inbox Item Localization by Reporter Country_ setting, Vault may populate the _Localization_ based on the primary reporter's locale. Vault references the _Reporter_ type of _Case Contact_ with a _Rank_ of _1_:
* If the _Country_ has a related _Localization_, Vault populates the _Localization_ field based on the _Language_ of the reporter's _Country_.
* If the _Country_ has multiple associated _Languages_, Vault populates the _Localization_ field based on the _Reporter Language_ field of the _Case Contact_.
* If no match exists, Vault checks for an _English_ record.
* If no _English_ record exists, Vault applies the first _Localization_ record in alphabetical order for that country.
* If configured by your Admin, Vault may populate the _Localization_ based on the the [primary reporter's locale and the report type][5] of the _Inbox Item_.
When you promote the _Inbox Item_, Vault processes the _Case_ as domestic or global based on the _Localization Type_ of the matching _Localization_.
#### Reporter Locale and Report Type Localization {#report-localization}
When configured by your Admin, Vault populates the _Localization_ field on imported _Inbox Items_ based on the primrary reporter's locale and the report type of the _Inbox Item_. Vault references the _Reporter_ type of _Case Contact_ with a _Rank_ of _1_ and the _Report Type_ of the _Inbox Item_. When the _Report Type_ is _Study_, Vault also references the _Study Type_ of the associated _Study_. Vault matches _Localization_ based on its _Case Type_ values as follows:
* **Blank**: Matches regardless of the _Report Type_ of the _Inbox Item_.
* **Investigational**: Matches if the _Report Type_ of the _Inbox Item_ maps to E2B code `2` (Report in Clinical Trial) and the _Study Type_ of the _Study_ maps to E2B code `1` (Clinical Trial), or _Study Type_ is blank. For example, the _Study Type_ is _Clinical Trial_.
* **Marketing**: Matches if either of the following conditions are true:
* The _Report Type_ of the _Inbox Item_ maps to any E2B code except `2` (Report in Clinical Trial). For example, when the _Report Type_ is any value other than _Study_.
* The _Report Type_ of the _Inbox Item_ maps to E2B code `2` (Report in Clinical Trial) and the _Study Type_ of the _Study_ maps to any E2B code except `1`. For example, when the _Study Type_ is any value other than _Clinical Trial_.
Vault then populates the _Localization_ field based on the matching _Localization_ record:
* If one match for the primary reporter's _Country_ and _Report Type_ exists, Vault populates the field with the corresponding _Localization_ value.
* If multiple matches for the primary reporter's _Country_ and _Report Type_ exist, Vault references the _Reporter Language_ field of the _Case Contact_.
* If _Reporter Language_ is blank, Vault checks for an _English_ record.
* If there are still multiple matches, Vault applies the first _Localization_ record for that _Country_ or _Report Type_.
* If zero matches for the primary reporter's _Country_ and _Report Type_ exist, Vault does not populate the field.
[1]: #seriousness
[2]: #product-rank
[3]: #library
[4]: #aer
[5]: #report-localization