# Setting Up CRF & Dataset Import (RIM)

Many organizations use outside systems to collect clinical data, and then assemble subject case report forms (CRFs) and datasets. Using the CRF and dataset import feature, users can quickly and easily file all final subject CRFs and datasets into Vault. Vault automatically assigns the imported documents to the correct study and site, and sets them to _Approved_ status and major version 1.0.

<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 is only available on RIM Submissions and RIM Submissions Publishing Vaults.</p>
    </div>
  </div>
</div>



## Granting Permissions

To <a href="/en/gr/24707/">import CRFs and datasets</a>, a user must have at least read-only access to the _Clinical Studies_ listing (generally through **Admin > Business Admin**) and **Create Document** permission on the document types, subtypes, and classifications selected for CRFs and datasets.

To import a new version of an existing CRF or dataset, a user must have **Edit Document** permission on _Approved_ state documents in the _Batch Import_ lifecycle.

## How to Enable Batch Import

To enable the **Import CRFs** action:

  1. Navigate to **Admin > Settings > Application Settings**.
  2. Select the checkbox for **Allow batch import of CRFs**.
  3. Select a document type, subtype, or classification to apply to imported CRFs.

To enable the **Import Datasets** action:

  1. Navigate to **Admin > Settings > Application Settings**.
  2. Select the checkbox for **Allow batch import of datasets**.
  3. Select a document type, subtype, or classification to apply to imported datasets.

Once you enable Batch Import settings, you cannot disable them.

## Batch Import Configuration

For CRF and dataset import to work correctly, you must complete the following configurations:

  * Assign the _Batch Import_ lifecycle to the CRF and dataset document types. Vault automatically creates and activates this lifecycle after enablement. The lifecycle has a simple configuration with a single state (_Approved_), no workflows, and no expiration. Imported documents must use this lifecycle.
  * Ensure that the required fields (_Clinical Study_, _Site_) are on the CRF and dataset document types.

## About Required Fields & Batch Import

When enabling CRF and dataset imports, verify that there are no required fields which apply to the selected CRF and dataset document types that do not have default values. Vault cannot populate document fields during imports unless they have default values, so required fields can prevent Vault from successfully creating documents.

## About Approved State

By default, the _Batch Import_ lifecycle only has a single state: _Approved_. This state is assigned as the **Starting State** for the lifecycle. Vault does not automatically assign a **Steady State**, but you can modify this configuration to make _Approved_ the **Steady State**.