Job Types for Study Administrators

Learn how to schedule jobs here.

Audit Trail Export

The Audit Trail Export job generates a CSV file containing the audit trail for each Casebook in a Study, including any deleted records, such as those removed by a retrospective amendment. This job also generates an additional CSV file to track deleted Subjects.

Job Options

The following configuration options are available for the Audit Trail Export job:

  • Date Range: You can choose to apply a date range to your Audit Trail Export.

  • User: You can choose to filter your exported audit trail to only include actions performed by a specific user.

Output

When the Audit Trail Export job finishes, you can download a ZIP file containing CSVs for each Casebook and the CSV for deleted Subjects. Extract the ZIP files contents and review the CSVs in your preferred editor.

Code Request Export

The Code Request Export job generates a CSV file that details all Code Requests for a Study. Organizations that use the Data Export job can combine this job’s output and a Data Export job’s SAS output to review study execution and coding data together. These files can be joined using key value pairs for Subject ID and Form Sequence or Item Group Sequence.

Job Options

The following configuration options are available for the Code Request Export job:

  • External Connection: You can choose to export your data to a configured FTP location, instead of downloading the files. To use this option, you must first create an FTP connection from EDC Tools > FTPs.

Output

When the Code Request Export job finishes, you can download a CSV file listing all Code Requests for a Study, including Study, Site, Form, and Code information for each Code Request.

Data Export

The Data Export job exports study execution data as a series of either CSV or SAS files, in a format determined in your study’s design.

Job Options

The following configuration options are available for the Data Export job:

  • View Set: Select a View Set to base your export on. View set availability depends on your vault’s configuration and your study design. Contact your Veeva Services representative for details.

  • Export File Type: You can export data as CSVs or as SAS files. Choose one.

  • External Connection: You can choose to export your data to a configured FTP location, instead of downloading the files. To use this option, you must first create an FTP connection from EDC Tools > FTPs.

Output

When the Data Export job is complete, you can download a ZIP file containing either CSVs or SAS files, depending on your selections. Extract the contents and view the exported data in your preferred file viewer.

Core Listing

The Core Listing job generates a simplified CSV for each Form included, listing the data collected for that Form.

Job Options

The following configuration options are available for the Core Listing job:

  • Forms: In the Forms tab, use the Arrow buttons to move Forms from Available Forms to Selected Forms. Forms in the Selected Forms section are included in the export. You must select at least one Form.

  • Sites: In the Sites tab, use the Arrow buttons to move Sites from Available Sites to Selected Sites. Sites in the Selected Sites section are included in the export. You must select at least one Site.

Output

When the Core Listing job finishes, you can download a ZIP file containing CSV files for each selected Form. Each form’s CSV lists data for each Subject in the selected Sites. The following information is included (as columns):

  • Study
  • Study Country
  • Site
  • Subject
  • Event Group
  • Event Group Sequence Number
  • Event
  • Form Casebook Version
  • Form
  • Form Sequence Number
  • Form Status
  • Form Creation Date
  • Form Submission Date
  • Form ILB Status*
  • Form ILB Reason
  • Item Group Sequence Number
  • DateTime of Last Data Change
  • Open Queries
  • Closed Queries
  • Form SDV Status
  • Form SDV DateTime
  • Form DMR Status
  • Form DMR DateTime
  • Form Frozen Status*
  • Form Frozen DateTime*
  • Form Locked Status*
  • Form Locked DateTime*
  • Form Signed Status*
  • Form Signed DateTime*
  • Core Listing as of {DateTime when the job was run}

Form CSVs also include a column for each Item on the Form, which lists the entered value, labeled with the item’s Label, Name, and the item’s Item Group. For example, an Item labeled “Procedure Time” (named PROC_TIME) in an Item Group named IG_PROC has the column header “Procedure Time (IG_PROC.PROC_TIME)”. For unit-type Items, Vault includes additional columns for the Value, Unit, Value Translated, and Unit Translated.

For repeating Forms and Item Groups, the CSV includes a row for each sequence of repetition.

If a Form is configured for coding, Vault includes additional columns detailing the coding status and any assigned code.

  • For WHODrug forms, Vault includes: Coding Status, Drug Code, Drug Name, Preferred Code, Preferred Name, ATC4 Code, ATC4, ATC3 Code, ATC3, ATC2 Code, AC2, ATC1 Code, ATC`, Dictionary Release, and Last Coded Date.
  • For MedDRA forms, Vault includes: Coding Status, LLT Code, LLT, PT Code, PT, HLT Code, HLT, HLGT Code, HLGT, SOC Code, SOC, Dictionary Release, and Last Coded Date.

*ILB is an abbreviation for Intentionally Left Blank.

*Vault only includes these Form status columns for Studies created prior to the 19R3 release (December 2019).

Detail PDFs

The Detail PDFs job exports subject Casebooks as PDFs, including any entered data within those Casebooks. Optionally, this export can include query and audit trail information.

Job Options

The following configuration options are available for the Detail PDFs job:

  • Include Queries: Select this checkbox to include queries in your PDF.

  • Include Audit Trail: Select this checkbox to include the related audit trails in your PDF.

  • Scope: Select Export all sites to include all Sites for the Study, generating a closeout PDF. Select Select Sites to choose which Sites to include. If you chose Select sites, use the Arrow buttons to move Sites from Available to Selected. Sites in Selected are included in the PDF export.

Output

When the Detail PDFs job finishes, you can download a ZIP file containing a folder for each Site. Each of those site folders contains a Detail PDF for each subject Casebook at that Site.

Data and Definition Export

The Data and Definition Export job (formerly known as the JReview job) exports a ZIP file of CSVs representing collected data in your Study.

Job Options

The following configuration options are available for the Data and Definition Export job:

  • Include Restricted Data: If you have the Restricted Data Access permission, you can select this checkbox to include data from restricted forms in your export.

Output

When the Data and Definition Export job is complete, you can download the ZIP file containing all Form CSVs. Extract the contents and view the exported data in your preferred file viewer.

Study Data Extract

The Study Data Extract job allows Lead Data Managers to extract and download study execution data.

Job Options

The following configuration options are available for the Study Data Extract job:

  • Include Restricted Data: If you have the Restricted Data Access permission, you can select this checkbox to include data from restricted forms in your export.

Output

When the Study Data Extract job is completed, you can download a SAS or CSV file for each selected Study. System Datasets include Sites (SYS_SITE), Subjects (SYS_SUB), Events (SYS_EVT), Forms (SYS_FORM), Queries (SYS_Q), Query Status (SYS_QT), Intentionally Left Blank fields (SYS_ILB), and Links (SYS_LINKS).

For more information about the Study Data Extract job, see Study Data Extracts.

Workbench Export

The Workbench Export job exports study data in Vault EDC and Vault Coder, and then sends the export package to Vault CDB. Vault CDB imports the data and creates a Core Listing for each form.

Job Options

There are no special configuration options for the Workbench Export job.

Output

Vault automatically sends the output file to Vault CDB. You can download and view the output from EDC Tools > Jobs or from Workbench > Import.

Autocoding and Suggestions

Vault Coder runs the Autocoding and Suggestions job automatically. This job analyzes all Code Requests that are pending coding and attempts to autocode them and generate suggestions. The Autocoding and Suggestions job allows you to autocode a coding request or generate a suggestion if Vault has not already done so.

Job Options

There are no special configuration options for the Autocoding and Suggestions job.

Output

This job does not generate any output file.

Code Request Export

The Code Request Export job generates a CSV file that details all Code Requests for a Study. Organizations that use the Data Export job can combine this job’s output and a Data Export job’s SAS output to review study execution and coding data together. These files can be joined using key value pairs for Subject ID and Form Sequence or Item Group Sequence.

Job Options

The following configuration options are available for the Code Request Export job:

  • External Connection: You can choose to export your data to a configured FTP location, instead of downloading the files. To use this option, you must first create an FTP connection from EDC Tools > FTPs.

Output

When the Code Request Export job finishes, you can download a CSV file listing all Code Requests for a Study, including Study, Site, Form, and Code information for each Code Request.

Reconstitute Code Requests

The Reconstitute Code Requests job updates existing Code Requests to reflect any configuration changes. This job can be useful if you’ve added Coding Configurations after a Study is live and Forms that require coding have been previously submitted.

Job Options

There are no special configuration options for the Reconstitute Code Requests job.

Note: Frequency is disabled for this job. You can only run this job on an ad hoc basis.

Output

The job output for the Reconstitute Code Requests job includes four CSV files detailing record creation and updates for Code Requests during this job:

  • Code Requests Created
  • Code Requests Updated
  • Code Requests Failed to Create
  • Code Requests Failed to Update