Manage Multi-Case Tabular Data Import

Configure field mapping from the multi-Case CSV or multi-CSV ZIP file to the target fields.

About Multi-Case Tabular Data Import

Intake users can import a multi-Case tabular CSV file or a multi-CSV ZIP file to Inbox Items, which includes up to 1,000 Cases, using pre-defined mapping. For more information, see Import an Inbox Item: About Multi-Case Tabular Data Import.

This article demonstrates how to configure Tabular Data Formats, Import Field Mappings, and Import Code Mappings to map the imported data to a target Vault Safety field.

Prerequisites

Your Admin must enable Multi-Case Tabular Data Import.

Create Tabular Data Formats

Tabular Data Formats include the type of field mapping the system uses to import multi-Case data to Vault Safety fields and the list of source files being imported.

  1. Go to Business Admin > Objects > Tabular Data Formats.
  2. Select Create.
  3. Complete the following information:
    • Format: Enter a name for this Tabular Data Format.
    • Encoding: Select an encoding type for the Tabular Data Format. If creating a Tabular Data Format for VAERS, select ISO-8859-1.
    • Country: Select a country for the Tabular Data Format.
  4. Save the page.

Create Tabular Source Files

Tabular Source Files specify the files being imported during multi-CSV ZIP import. You can create and update these files on the Tabular Data Format object.

  1. Create Tabular Source Files by expanding the section on the respective Tabular Data Format record or by going to Business Admin > Objects > Tabular Source Files and selecting Create.
  2. Complete the following information:
    • Name: Enter the name of the source file including the format extension. Ensure your entry is case-sensitive.
    • Standard Format: If importing VAERS Symptoms, select the option. Otherwise, leave this field blank.
    • Target Object Name: Enter the name of the object to which the source file is mapping. For example, case_product__v.
  3. Save the page.

Create Field Import Mappings

Field Import Mappings specify how imported tabular data maps to field and object records in Vault Safety. Vaults created in 23R3 or later already have some pre-defined field mapping for standard Tabular Data Formats. If your Vault was provisioned before 23R3, you can contact your Veeva Representative to obtain pre-defined field mappings. You can also create and update Field Import Mappings on the Tabular Data Format object:

  1. Create Import Field Mappings by expanding the section on the respective Tabular Data Format record and selecting Create.
  2. Complete the following information:
    • Source Column Header: Enter the name of the column header in the CSV file. You cannot enter a separator (for example, a comma or semicolon).
    • Tabular Data Format: Select the Tabular Data Format this field mapping belongs to. If you created this Import Field Mapping record directly from a Tabular Data Format, this field is automatically populated.
    • Target Field Name: Enter the field name of the Vault Safety field. For example, event_reported__v.
    • Target Object Name: Enter the name of the object to which the target field belongs. For example, case_adverse_event__v.
  3. Save the page.
  4. Repeat these steps for as many column headers as needed.

Certain fields are not supported, for example, auto-calculated fields. If data is received for unsupported fields, Vault will ignore and not process that data. To see the list of unsupported fields, download this XLS file.

ID Field Mappings

If your Vault contains pre-defined mapping already, you will see some source column headers mapping to the Target Field Name, id. For multi-case CSV import, Vault uses the id field mapping to reference a record in another row for a given source column header. For multi-CSV ZIP import, Vault uses the id field mapping to reference a record in another CSV file for a given source column header. For example, the following field mapping allows Vault to reference an Adverse Event record on another Case for a given Case Assessment record:

Source Column Header Target Object Name Target Field Name
Event ID case_adverse_event__v id

For applicable source column headers, create field import mappings to reference a record in another row (if multi-case CSV import) or file (if multi-CSV ZIP import).

About Import Code Mappings

Import Code Mappings map source values to Vault-coded values for a given Import Field Mapping. Each Import Code Mapping requires a Code Mapping Type, an expected source value, and a value Vault will map from your library. Code Mapping Types indicate which object type each mapping is based on. Available types are:

  • Controlled Vocabulary
  • Dose Form
  • Route of Administration
  • Unit of Measurement
  • Reason Omitted
  • Seriousness

Source values may be case-sensitive text or codes. For the Vault value, you must populate the field corresponding to the Code Mapping Type. For example, if you want to create an Import Code Mapping for the value Spontaneous within the Report Type controlled vocabulary, you will:

  • Select Controlled Vocabulary in the Code Mapping Type field.
  • Enter any of the following in the Source Value field:
    • 1
    • SPT
    • Spontaneous
  • Select Spontaneous in the Controlled Vocabulary field.

Create Import Code Mappings

To create Import Code Mappings:

  1. Navigate to Business Admin > Objects > Import Field Mappings.
  2. Select an Import Field Mapping.
  3. Expand the Code Mapping section and select Create.
  4. In the Code Mapping Type field, select an object type on which to base the field mapping.
  5. In the Source Value field, enter the code or text value that would appear on source files.
  6. Based on your Code Mapping Type selection, in the corresponding field select a value from the drop-down list or, when available in the field, select the Advanced Search (Binoculars Icon) icon to find the value using the Search dialog.
  7. Select Save.

Consider the following system validations:

  • The Source Value must be mapped to only one (1) object field. In other words, only one (1) of the object fields should be populated on the Import Code Mapping page, for example, Dose Form.
  • The Source Value cannot be mapped to multiple target object values for a given Import Field Mapping.