# Configure Inbox Item Significance Criteria

Learn how to create custom significance rules to define how Vault identifies significant and urgent _Inbox Items_ generated by the Safety-EDC Connection. These rules  alert users about possible changes to the reporting requirements for a _Case_. 

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: This feature applies only to <em>Inbox Items</em> generated by the Safety-EDC Connection.</p>
    </div>
  </div>
</div>



## About Significance Criteria {#about}

Your Vault includes standard _Significance Criteria_, which Vault uses to determine the _Significance_ value for _Inbox Items_ generated from serious adverse events (SAEs) transferred by the <a href="/en/lr/679352/">Safety-EDC Connection</a>. You can use these [standard rules][6] or [define new rules][7] to support the unique requirements of your organization's business processes. 

For _Inbox Items_ generated by the connection, Vault calculates the _Significance_ value based on which active _Significance Criteria_ return true and, when applicable, generates a follow-up _Case_. When multiple criteria return true, Vault assigns the highest level of significance met:

* _Initial Case_
* _Non-Significant Follow-Up_
* _Significant Follow-Up_
* _Urgent Significant Follow-Up_

Users can review which _Significance Criteria_ Vault evaluated to determine _Significance_ in the _Significance Results_ section of an _Inbox Item_. Vault recalculates _Significance_ every time it detects an associated follow-up _Inbox Item_. Users can also manually recalculate _Significance_ using the <a href="/en/lr/725776/#rerun-action">_Rerun Significance Criteria_ action</a>.

### Standard Significance Criteria Records {#standard}

Safety Vaults include the following standard _Significance Criteria_ records:

* _Case Adverse Event Event Reported Changed_
* _Case Adverse Event Meddra Coding Changed_
* _Case Adverse Event Onset Changed_
* _Case Adverse Event Outcome = Fatal_
* _Case Adverse Event Outcome Changed_
* _Case Adverse Event Reported = Death_
* _Case Adverse Event Seriousness = Results in Death or Life Threatening_
* _Case Adverse Event Seriousness Changed_
* _Case Age Changed_
* _Case Assessment Result Changed_
* _Case Cause of Death Changed_
* _Case Cause of Death Reported Changed_
* _Case Date of Death Changed_
* _Case Gender Changed_
* _Case Product Indication Meddra Changed_
* _Case Product Indication Name Reported Changed_
* _Case Product MPID Changed_
* _Case Product Product Reported Changed_
* _Case Site Narrative Changed_
* _Case Tags Susar_

## Prerequisite

Before configuring this feature, you must <a href="/en/lr/725776/">enable Automated Classification of Inbox Item Significance</a>.

## Define Significance Criteria {#define}

You can create new rules that are customized to fit your business needs. You can review the _Descriptions_ of all [standard rules][6] to understand the criteria by navigating to **Business Admin > Objects >  Significance Criteria**. To create custom rules, you can <a href="/en/lr/32218/">copy</a> the standard record, then update the custom records as needed, or create new records from scratch:

1. Navigate to **Business Admin > Objects >  Significance Criteria**.
2. Create the new record as applicable:
   * To create a new rule, select **Create**.
   *  To modify a standard rule, copy the existing record:
      1. From the record's **Action** menu, select **Change State to Inactive**.
      2. From the record's **Action** menu, select **Copy Record**.
3. Enter or update the **Name**.
4. Optional: Enter or update the **Description**.
5. Use the [**Significance Criteria Builder**][1] to define when Vault applies the specified _Significance_ value.
6.  Select a **Significance** value to apply when the _Rule Formula_ returns true.
7.  Enter or update an **API Name**. For example, `case_state_change__c`.
8.  Select **Save**.

### Significance Criteria Builder {#criteria}

Use the _Significance Criteria Builder_ to build a formula expression. When a formula returns true, Vault applies the _Significance Criteria's_ specified _Significance_ value to the generated _Inbox Item_. The builder supports <a href="/en/lr/1037069/">VQL</a>, the operators and functions in the <a href="/en/lr/52324/">Vault Formula Reference Guide</a>, certain Safety-specific functions detailed in <a href="/en/lr/861364/">Create Formula Expressions</a>, and the following Safety significance functions:

* [`VS_SIG_CASE_VALUE`][2]
* [`VS_SIG_CHANGED`][3]
* [`VS_SIG_CHANGED_RECORD`][4]
* [`VS_SIG_NEW`][5]


<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: You cannot use significance functions in conjunction with the <a href="/en/lr/861364/#vs_anyof"><code class="language-plaintext highlighter-rouge">VS_ANYOF</code></a> or <a href="/en/lr/861364/#vs_let"><code class="language-plaintext highlighter-rouge">VS_LET</code></a> functions.</p>
    </div>
  </div>
</div>



The _Significance Criteria Builder_ supports composite checks, allowing you to identify data that meets all specified conditions. You can use the OR `(||)` and AND `(&&)` operators to evaluate multiple _Inbox Item_ or _Case_ values at once and to evaluate _Inbox Item_ field values relative to the underlying _Case_. For more details about creating formulas, see <a href="/en/lr/42857/">Creating Formulas in Vault</a>.

#### VS_SIG_CASE_VALUE {#vs_sig_case_value}

`VS_SIG_CASE_VALUE(object_name.field_name, "string_value")`

This function returns true if there is a particular value of the specified _Case_ field value. This function includes the following inputs:

* `object_name.field_name`: Specifies a _Case_ field.
* `string_value`: Specifies the _Case_ field's value. This can be a display value (to evaluate a specific field value) or an _ID_ (to evaluate a specific record).

##### Example

The following example returns true if there are multiple _Cases_ with an _Organization_ value of _Vault Customer_:

`VS_SIG_CASE_VALUE(case_version__v.organization__v, "Vault Customer")`

#### VS_SIG_CHANGED {#vs_sig_changed}

`VS_SIG_CASE_VALUE(object_name.field_name)`

This function returns true if the values of the specified _Inbox Item_ fields do not match the values of the corresponding _Case_ fields, allowing you to evaluate a change on a new _Inbox Item_ against the existing _Case_. This function includes the following input:

* `object_name.field_name`: Specifies a _Case_ field.

##### Example

The following example returns true if the _Event Reported_ value of the follow-up _Case Adverse Event_ differs from the corresponding field on the related _Case_:

`VS_SIG_CHANGED(case_adverse_event__v.event_reported__v)`

#### VS_SIG_CHANGED_RECORD {#vs_sig_changed_record}

`VS_SIG_CHANGED_RECORD(object_name)`

This function returns true if any non-system field values displayed on the <a href="/en/lr/01196/#customize-the-inbox-item-follow-up-case-compare-layout">_Case Compare Followup_ layout</a> for the specified object do not match the values of the corresponding _Case_, allowing you to evaluate changes from a new _Inbox Item_ against the existing _Case_. This function includes the following input:

* `object_name`: Specifies a _Case_-related object.

##### Example

The following example returns true if any values of the follow-up _Case Adverse Event_ differs from the corresponding fields on the related _Case_:

`VS_SIG_CHANGED_RECORD(case_adverse_event__v)`

#### VS_SIG_NEW {#vs_sig_new}

`VS_SIG_NEW(object_name)`

This function returns true if the specified record is new. This function includes the following input:

* `object_name`: Specifies a _Case_-related object.

##### Example

The following example returns true if there is no existing _Case Adverse Event_ for the _Case_:

`VS_SIG_NEW(case_adverse_event__v)`


[1]: #criteria
[2]: #vs_sig_case_value
[3]: #vs_sig_changed
[4]: #vs_sig_changed_record
[5]: #vs_sig_new
[6]: #standard
[7]: #define