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 can include up to 1,000 Cases, using pre-defined mapping. For more information about multi-Case tabular data import, see Import an Inbox Item.

To set up your Vault to import data to targeted fields, you must create the appropriate mappings for each applicable health authority or partner. Your Vault includes standard records for Health Canada, which you can customize as needed and use instead of creating mappings.

Prerequisite

Your Admin must enable Multi-Case Tabular Data Import.

Create Mappings

You must create mappings for each applicable health authority or partner to define how Vault imports multi-Case data from that source. Veeva provides standard mappings for certain authorities, which you can use as a starting point by activating and then customizing as needed for your business process. For all other formats, you must create the applicable mappings, including a Tabular Data Format with the appropriate Tabular Source Files, Import Field Mappings, and Import Code Mappings.

Standard Mappings for Health Canada

Veeva provides standard mappings for Health Canada. We recommend activating this standard record and updating it as needed, along with all related records. Alternatively, you can create new records. To use standard mappings:

1. Navigate to Business Admin > Objects > Tabular Data Formats > Health Canada English (Standard).
2. Select Edit.
3. Update the Status to Active.
4. Select Save.

Review the Tabular Source Files, Import Field Mappings, and Import Code Mappings in the standard record and update them as needed for your business processes.

Create & Update Tabular Data Formats

Tabular Data Formats include the type of field mapping Vault uses to import multi-Case data to Vault fields and the list of source files being imported. To create or update a Tabular Data Format:

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

Create & Update Tabular Source Files

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

1. Create and update records by doing either of the following:
   • Expand the section on the applicable Tabular Data Format.
   • Navigate to Business Admin > Objects > Tabular Source Files and select Create to create a new record or open an existing record to review and update.
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. Select Save.

Create & Update Import Field Mappings

Import Field Mappings specify how imported tabular data maps to field and object records in Vault. To create or update an Import Field Mapping:

1. Expand the section on the applicable Tabular Data Format and select Create to create a new record or open an existing record to review and update.
2. Complete the following information:
   • Source Column Header: Enter the name of the column header in the CSV file. Do not enter separators such as commas (,) or semicolons (;).
   • Tabular Data Format: Select the Tabular Data Format this field mapping belongs to. If you created this Import Field Mapping directly from a Tabular Data Format, Vault populates this field.
   • Target Field Name: Enter the field name of the Vault 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. Select Save.
4. Repeat these steps for as many column headers as needed.

Vault does not support certain fields, such as auto-calculated fields. Vault ignores unsupported fields 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 Import Field Mappings to reference a record in another row (if multi-Case CSV import) or file (if multi-CSV ZIP import).

Create 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, such as:

• 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.

How to Create Import Code Mappings

To create or update an Import Code Mapping:

1. Navigate to Business Admin > Objects > Import Field Mappings.
2. Select an Import Field Mapping.
3. In the Code Mapping section, select Create to create a new record or open an existing record to review and update.
4. For Code Mapping Type, select an object type on which to base the field mapping.
5. For Source Value, 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 () icon to find the value using the Search dialog.
7. Select Save.

Consider the following system validations:

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