About Coder Jobs


From the EDC Tools area, you can manage jobs occurring in your Study. By interacting with these jobs in EDC Tools, you can save time by reviewing and initiating jobs in from a single location. A job represents a bulk evaluation or action upon collected study data. For example, an Autocoding and Suggestions job evaluates Code Requests to determine if they can be autocoded and to provide coding suggestions.

Coder Job Summary

Job Description Added When
Autocoding and Suggestions

Run the autocoding and suggestions algorithms, attempting to autocode any pending Code Requests and creating suggestions

An EDC Tools user initiates an Autocoding and Suggestions job from EDC Tools > Jobs

Code Request Export

Export a CSV file of all Code Requests for a Study, including details about each Code Request and what each request was coded to.

An EDC Tools user initiates a Code Request Export job from EDC Tools > Jobs

Reconstitute Code Requests

Updates existing Code Requests to use updated form configuration, and, if applicable, recreates previously deleted Code Requests to reference the updated configuration

An EDC Tools user initiates a Reconstitute Code Requests job from EDC Tools > Jobs

Autocoding and Suggestions

The Autocoding and Suggestions job runs the autocoding and suggestions algorithms on a scheduled basis. This job analyzes all Code Requests that are pending coding and attempts to autocode them and generate suggestions. The Autocoding and Suggestions job is helpful if you are new to using Vault Coder, and you have just begun building a Synonym List, but you want to autocode and provide suggestions for older Code Requests that were created before the matching patterns were available in your Synonym List.

Job Options

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

Output

This job does not generate any output file.

Veeva recommends that you schedule an Autocoding and Suggestions job once daily at midnight or another time when no one is using Vault Coder.

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 recreates previously deleted Code Requests after your organization finishes mid-stream configuration changes. It also updates existing Code Requests to reflect any configuration changes.

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