# Manage Derived Fields

Derived fields are standardized definitions in Workbench to simplify filtering for _Cases_ in reports (including aggregate reports) and displaying fields. Workbench provisions standardized definitions of derived fields. To customize derived fields according to your business needs, contact your Veeva Representative.

## Standardized Derived Fields

The following table describes some standard derived fields and the Workbench aggregate report in which they are applied:

<table>
    <thead>
        <tr>
            <th>Derived Field</th>
            <th>Definition</th>
            <th>Workbench Aggregate Report</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td><em>Case Category</em></td>
            <td><em>Cases</em> can be categorized as one (1) of the following:
                <ul>
                    <li><em>Spontaneous</em>: <em>Cases</em> with a <em>Report Type</em> of <em>Spontaneous</em> (E2B code=<code>1</code>), <em>Other</em> (E2B code=<code>2</code>), or <em>Not Available</em> (E2B code=<code>3</code>)</li>
                    <li><em>Interventional</em>: <em>Cases</em> that meet criteria for one (1) of the following:
                        <ul>
                            <li>Contains a <em>Report Type</em> of <em>Study</em> (E2B code=<code>2</code>) and a <em>Study Type</em> of <em>Clinical Trial</em> (E2B code=<code>1</code>)</li>
                            <li>Contains a <em>Report Type</em> of <em>Study</em> (E2B code=<code>2</code>), a <em>Study Type</em> with a blank value or an invalid E2B code, and where <em>Literature</em> is not set to <em>Yes</em></li>
                        </ul>
                    </li>
                    <li><em>Non-Interventional</em>: <em>Cases</em> that do not meet any of the above criteria</li>
                </ul>
            </td>
            <td><ul>
                    <li>DSUR</li>
                    <li>PBRER</li>
                    <li>PADER</li>
                    <li>SAR</li>
                </ul>
            </td>
        </tr>
        <tr>
            <td><em>Case Completed</em></td>
            <td>This field simplifies <em>Case</em> lifecycle states to determine whether a <em>Case</em> is completed or open. Vault uses the following criteria to determine a <em>Case</em> lifecycle state:
                <ul>
                    <li>Completed: <em>Cases</em> in one of the following lifecycle states: 
                        <ul>
                            <li><em>Approved</em> (<code>approved_state__v</code>)</li>
                            <li><em>Closed</em> (<code>closed_state__v</code>)</li>
                            <li><em>Superseded</em> (<code>superseded_state__v</code>)</li>
                            <li><em>Voided</em> (<code>voided_state__v</code>)</li>
                            <li><em>Nullified</em> (<code>nullified_state__v</code>)</li>
                        </ul>
                    </li>
                    <li>Open: <em>Cases</em> that do not meet any of the above criteria, including <em>Cases</em> in custom lifecycle states</li>
                </ul>
                <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>: Depending on report criteria, voided and nullified <em>Cases</em> may be automatically excluded.</p>
    </div>
  </div>
</div>


            </td>
            <td><ul>
                    <li>DSUR</li>
                    <li>PBRER</li>
                </ul>
            </td>
        </tr>
<tr>
            <td><em>Is Case Nullified / Voided</em></td>
            <td>This field determines whether a <em>Case</em> is nullified or voided and should not be included in latest <em>Case</em> version reports using the following criteria:
                <ul>
                    <li>Voided: <em>Cases</em> in the <em>Voided</em> (<code>voided_state__v</code>) lifecycle state</li>
                    <li>Nullified: <em>Cases</em> in the <em>Nullified</em> (<code>nullified_state__v</code>) lifecycle state</li>
                </ul>
            </td>
            <td><ul>
                    <li>DSUR</li>
                    <li>PBRER</li>
                </ul>
            </td>
        </tr>
        <tr>
            <td><em>Masking</em></td>
            <td>Vault determines whether the <em>Case</em> data is eligible for masked, unmasked, or both reports using the following criteria:
                <ul>
                    <li>Masked: <a href="/en/gr/691317/#overview"><em>Case</em> records</a> with a <em>Blinding Type</em> of <em>Blinded</em></li>
                    <li>Unmasked: <em>Case</em> records with a <em>Blinding Type</em> of <em>Unblinded</em></li>
                    <li>Both: <em>Case</em> records with a <em>Blinding Type</em> of <em>Open</em></li>
                </ul>
            </td>
            <td><ul>
                    <li>DSUR</li>
                    <li>PBRER</li>
                    <li>PADER</li>
                    <li>SAR</li>
                </ul>
            </td>
        </tr>
        <tr>
            <td><em>Receipt/New Info Date</em></td>
            <td>This field provides the following mapping logic:
                <ol>
                    <li>Vault maps this value from the <em>New Info Date</em> on the <em>Case</em>.</li>
                    <li>If the <em>New Info Date</em> on the <em>Case</em> is blank, Vault maps the value from the <em>Receipt Date</em> on the <em>Case</em>.</li>
                </ol>
            </td>
            <td><ul>
                    <li>DSUR</li>
                    <li>PBRER</li>
                    <li>PADER</li>
                    <li>SAR</li>
                </ul>
            </td>
        </tr>
    </tbody>
</table>