Note: This feature is only available on RIM Registrations Vaults.
There are two types of Impact Assessment Reports: standard and configurable. You can tell whether your Vault uses standard Impact Assessment Reports or configurable Impact Assessment Reports based on the fields available in the dialog when you launch the report.
## Standard Impact Assessment Reports
The below standard one-click reports are available in RIM Registrations Vaults:
Product Impact Assessment Report (RIM Registrations)
: Lists all registrations related to the _Product_ (`drug_product__v`) or _Manufacturer_ records described in the _Event_ record. [Learn more][2].
Active Substance Impact Assessment Report (RIM Registrations)
: Lists all registrations related to the _Active Substance_ or _Manufacturer_ described in the _Event_ record.
Packaging Impact Assessment Report (RIM Registrations)
: Lists all registrations related to the _Packaging_, _Packaging Site_, or _Shelf Life_ changes described in the _Event_ record.
Inactive Ingredient Impact Assessment Report (RIM Registrations)
: Lists all registrations related to the _Inactive Ingredient_ or _Manufacturer_ described in the _Event_ record.
Indication Impact Assessment Report (RIM Registrations)
: Lists all registrations related to the _Indication_ changes described in the _Event_ record.
Clinical Study Assessment Report (RIM Registrations)
: Lists all registrations related to the _Clinical Study_ or _Study Site_ changes described in the _Event_ record.
### Viewing Standard Reports
To open a standard impact assessment report for a specific event:
1. Navigate to the _Event_ record.
2. From the **Actions** menu, choose **Impact Assessment Report**. You'll only see this option if the _Event_ record has at least one related join record, for example, an _Event_ _Packaging_ record.
3. In the dialog, choose the data you want to include. The _Event_ record needs to be associated with the appropriate records, for example, opening the _Inactive Ingredient Impact Assessment_ requires that the event is associated with at least one _Inactive Ingredient_ record.
4. Click **Run**.
## Viewing Configurable Impact Assessment Reports {#configurable-reports}
Your Admin defines the report types that are available for configurable Impact Assessment Reports in your Vault.
To open a configurable impact assessment report for a specific event:
1. Navigate to the _Event_ record.
2. From the **Actions** menu, choose **Impact Assessment Report**. This option is available for all _Event_ records, regardless of related join records.
3. In the dialog, select the **Report Type** and the **Report Template** to use. The options you see are defined by your Admin.
4. Populate any [**Report Prompts**][1]. Vault may populate some values automatically based on the records associated with the _Event_ record.
5. Click **Continue**.
### Working with Reports
Vault creates a copy of the report template that you selected in the dialog, saves any values you entered in the _Impact Report Options_ dialog as filters, and assigns you the _Viewer_ role. The copied report's name is based on the _Event_ record from which you initiated the Impact Assessment Report, and the report description includes the _Event_ record ID. After you've made any changes, click **Save.**
If you re-run the report from the same _Event_ record using the same report template, Vault overwrites the saved report based on the input from the _Event_ record, rather than creating a duplicate report. You can still access the report from the **Reports** tab.
## About Report Prompts {#report-prompts}
Your Admin may include **Report Prompt** selections within the **Impact Assessment Report Options** dialog, allowing you to narrow the scope of records in the resulting report. Impact Assessment Reports allow you to select up to 100 values within a given prompt.
The options available to you are based on the report set-up, in addition to the report's included records. Report prompt options include:
* Optional prompts, where you can select the **Skip** checkbox.
* Pre-populated prompts, based on metadata available across relationship objects. For example, Vault can default the **Registration > Country** prompt to the *Country* value on each related *Event Country* record. See additional details about field mapping across relationship objects.
Additionally, Vault supports selecting **All** in-scope *Product Variant*, *Product*, and *Country* records for certain prompts. This option can be useful when running a report with more than 100 records requiring assessment.
* To use this feature, the report must use Advanced Logic, and filters must be configured with the IN operator.
* Selecting **All** includes up to 10,000 records, however Vault only displays the first 100. As a result, you cannot select a custom amount between 100 and the total record count.
* When the total record count is more than 10,000, Vault automatically splits the filters into batches of 100 and updates the Advanced Logic syntax to accommodate each batch. See additional details on how Vault handles more than 10,000 records.
## Creating Related Records
After you save the report, you can select **Create Related Records** from the report's **Actions** menu. When you start the Create Related Records wizard from the report, Vault populates the _Event_ field in the wizard with the _Event_ record ID from which you started the Impact Assessment Report.
When you run the Create Related Records wizard from this report, Vault only carries forward data related to the _Event_ record to any _Regulatory Objective_ or _Submission_ records created from the wizard. If you change the filters in your report copy to include data that is not related to the event, Vault will not carry this data forward.
## Objects & Medical Device Support {#footnote}
In Vaults created after the 19R1 release, the following objects are relabeled to support medical devices. For Vaults created prior to 19R1, Admins must update the standard objects to support medical devices.
* The **Product** (`product__v`) object is **Product Family**.
* The **Drug Product** (`drug_product__v`) object is **Product**.
* The **Product Detail** (`product_detail__v`) object is **Product Variant**.
[1]: #report-prompts
[2]: #footnote