Job Types for Study Administrators
Learn how to schedule jobs here.
Autocoding and Suggestions
When a Code Request is created or updated, it is evaluated for Autocoding and Suggestions from the assigned Synonym List. If the Code Request is not autocoded and the Study Setting “Autocode from Dictionary” is set to Yes, Vault will attempt to autocode it from the dictionary. Anytime a Synonym List is approved or is imported in the Active State, Vault will attempt to Autocode and generate Suggestions from this Synonym List to all of the assigned forms. If you need to uncode a large and diverse set of Code Requests and want them to be evaluated for Autocoding from the Synonym List and Dictionary (if the applicable Study Setting is enabled), you can run the Autocoding and Suggestions job from EDC Tools. This job will evaluate all pending Coding Requests for Autocoding from the Synonym List and Dictionary and reevaluate Suggestions.
Job Options
There are no special configuration options for the Autocoding and Suggestions job.
Output
This job does not generate any output file.
Audit Trail Export by Study
The Audit Trail Export by Study 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 by Study job:
-
Date Range: You can choose to apply a date range to your Audit Trail Export by Study job.
-
User: You can choose to filter your exported audit trail to only include actions performed by a specific user.
-
Include Definition, Relationship, and Facade Audit Changes: This option displays a checkbox so that you can exclude (unchecked) or include (checked) extraneous change records that were suppressed in a 24R1 enhancement. This option will only display if configured by Veeva Support.
Audit Trail Export by Site
The Audit Trail Export by Site job generates a CSV file containing the audit trail for each Subject in a selected Site or Sites.
Job Options
The following configuration options are available for the Audit Trail Export by Site job:
-
Date Range: You can choose to apply a date range to your Audit Trail Export by Site job.
-
User: You can choose to filter your exported audit trail to only include actions performed by a specific user.
-
Site: You can select up to ten sites to export audit trail data from.
-
Include Definition, Relationship, and Facade Audit Changes: This option displays a checkbox so that you can exclude (unchecked) or include (checked) extraneous change records that were suppressed in a 24R1 enhancement. This option will only display if configured by Veeva Support.
Audit Trail Export by Subject
The Audit Trail Export by Subject job generates a CSV file containing the audit trail for each selected subject.
Job Options
The following configuration options are available for the Audit Trail Export by Subject job:
-
Date Range: You can choose to apply a date range to your Audit Trail Export by Subject job.
-
User: You can choose to filter your exported audit trail to only include actions performed by a specific user.
-
Subject: You can select up to 20 current or deleted subjects to export audit trail data for.
-
Include Definition, Relationship, and Facade Audit Changes: This option displays a checkbox so that you can exclude (unchecked) or include (checked) extraneous change records that were suppressed in a 24R1 enhancement. This option will only display if configured by Veeva Support.
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.
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. You must have the View Code permission to view these columns.
- 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).
Data and Definition Export (Deprecated)
The Data and Definition Export job (formerly known as the JReview job) exports a ZIP file of CSVs representing collected data in your Study.
The Data and Definition Export (DDE) job is retired. The Study Data Extract (SDE) job has been enhanced to replace the functionality previously provided by the DDE.
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.
Data Change Extract
The Data Change Extract exports a ZIP file of CSVs that show changes made to Item and Event Date data during a specific time period.
Job Options
The following configuration options are available for the Data Change Extract job:
-
File Type: Choose whether to export data changes as a CSV or an Excel™ file.
-
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.
-
Forms: You can choose whether to include all forms in the extract or specific forms.
-
Include Restricted Data: If you have the Restricted Data Access permission, you can select this checkbox to include data from restricted forms in your extract.
-
Frequency: You can choose how often you want the job to run and schedule future jobs. If scheduling, you must provide a unique Name for your job to display in the Job Name column of the Job Schedule tab. You must also specify how often you’d like the job to run.
-
Date Range: You can choose the date range of data that you would like the extract to capture (up to 90 days).
Output
When the Data Change Extract is complete, you can download as a ZIP file containing the Data Change Extract Summary and Data Change Extract CSVs or as an Excel™ file, depending on your chosen File Type.
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.
Delete Inactive Coding Requests
The Delete Inactive Coding Requests job deletes coding requests that belong to inactive coding forms.
Job Options
There are no special configuration options for the Delete Inactive Coding Requests job.
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.
Event Progress Listing
The Event Progress Listing job generates a list of all Events in the Study, with status details and operational data, as a CSV file or report. The Event Progress Listing job is versionless.
Job Options
The following configuration options are available for the Event Progress Listing job:
-
Include Review Data: Users with the View SDV or View DMR permissions can choose to include SDV/DMR data in the listing.
-
Include Restricted Data: When this checkbox is selected, Vault includes events from restricted Forms if the job is initiated by a user with the Restricted Data Access permission. An event becomes Restricted when the data that triggers a dynamic event contains a Restricted form and is updated by a user without Restricted permission and the Restricted form is included in the submitted event. A user with Restricted permission must perform an action to clear the newly unneeded form.
Output
The Event Progress Listing job CSV export and report include the columns listed below. If your Study is using Data Model V1, the Event Signature Date, Freeze Date, and Lock Date columns will be blank in the CSV and report output.
Column Header | Description |
---|---|
Study | Study Name |
Country | Study Country Name |
Site | Site number |
Subject | Subject number |
Subject Status | Current Subject status |
Event Group Label | Event Group Label |
Event Label | Event Label |
Event Group Sequence Number | Event Group Sequence Number |
Event Type | Event Type |
Event Date | Event Date entered |
Visit Method | Visit Method selected |
Event Status | Event status (Planned, Blank, In Progress, Submitted, Did Not Occur) |
Event Did Not Occur | Indicates if the event was marked as Did Not Occur (Yes/No value) |
Event Did Not Occur Reason | Change Reason entered if the event was marked as Did Not Occur |
Restricted Event | Shows if the event is restricted or not (Yes/No value) |
Early Planned Date | The low date relative to study design plan and not considered out of window |
Planned Date | The date from study design the event was planned for |
Late Planned Date | The high date relative to study design plan and not considered out of window |
Event Out of Window | If the event is out of window (below Early, above Late), or if missing (and past late grace) |
Days Out of Window | If Out of Window, display the number of days out of window |
SDV Plan | The SDV plan assigned to subject at time of generation |
Event SDV Required | Shows if SDV was required for the Event (Required, Optional, Not Required, Blank) |
Event SDV Complete | Shows whether the Event completed SDV (Yes/No value) |
% Event SDV Complete | Shows the percentage of SDV completion for the Event |
Event First SDV Completion Date | Shows the date that SDV for all forms in the event, and for Event Date and Visit Method if required, was first completed. This value will be cleared if the form or event is reset. |
Forms SDV Completion Date | Shows the date when the forms in the Event underwent SDV |
Visit Method SDV Required | Shows if SDV was required for the Visit Method (Required, Optional, Not Required, Blank) |
Visit Method SDV Complete | Shows whether the Visit Method completed SDV (Yes/No value) |
Visit Method SDV Complete Date | Shows the date when the Visit Method underwent SDV |
Total Forms SDV Required | Total number of forms completed for this event, where at least one field is SDV required |
Submitted Forms SDV Required | Number of submitted forms where SDV is required at the event |
Total Forms SDV Complete | Shows the total number of forms that completed SDV |
% Forms SDV | Percentage of forms that underwent SDV at this event |
Event SDV Completion Date | The date on which all forms at this event completed SDV for this subject |
DMR Plan | The DMR plan assigned to subject at time of generation |
Event DMR Required | Shows if DMR was required for the Event (Required, Optional, Not Required, Blank) |
Event DMR Complete | Shows whether the Event completed DMR (Yes/No value) |
% Event DMR Complete | Shows the percentage of DMR completion for the Event |
Event First DMR Completion Date | Shows the date that DMR for all forms in the event, and for Event Date and Visit Method if required, was first completed. This value will be cleared if the form or event is reset. |
Forms DMR Completion Date | Shows the date when the forms in the Event underwent DMR |
Visit Method DMR Required | Shows if DMR was required for the Visit Method (Required, Optional, Not Required, Blank) |
Visit Method DMR Complete | Shows whether the Visit Method completed DMR (Yes/No value) |
Visit Method DMR Complete Date | Shows the date when the Visit Method underwent DMR |
Event Date DMR Date | Shows the date when the Event Date underwent DMR |
Total Forms DMR Required | Total number of forms completed for this event, where at least one field is DMR required |
Submitted Forms DMR Required | Number of submitted forms where DMR is required at the event |
Total Forms DMR Complete | Shows the total number of forms that completed DMR |
% Forms DMR | Percentage of forms that underwent DMR at this event |
Event DMR Completion Date | The date on which all forms at this event completed DMR for this subject |
Event Date Frozen | Shows if the Event Date was frozen (Yes/No value) |
Event Date Frozen Date | The date that the Event Date was frozen |
Event Date Locked | Shows if the Event Date was locked (Yes/No value) |
Event Date Locked Date | The date that the Event Date was locked |
Event Signed | Shows if event is signed (Yes/No value) |
Event Date Signature Date | The date when the event was signed |
Visit Method Frozen | Shows if the Visit Method was frozen (Yes/No value) |
Visit Method Frozen Date | The date that the Visit Method was frozen |
Visit Method Locked | Shows if the Visit Method was locked (Yes/No value) |
Visit Method Locked Date | The date that the Visit Method was locked |
Visit Method Signed | Shows if the Visit Method was signed (Yes/No value) |
Visit Method Signature Date | The date that the Visit Method was signed |
Event Frozen | Shows if the event is frozen (Yes/No value) |
Freeze Date | The date when the event was frozen |
Event Locked | Shows if the event is locked (Yes/No value) |
Lock Date | The date when the event was locked |
Event ID | Vof ID of the event |
Last Run of Listing | Datetime when the listing was last run |
Form Progress Listing
The Form Progress Listing job generates a list of all Forms in the Study, with status details and operational data, as a CSV file. The Form Progress Listing job is versionless.
Job Options
The following configuration options are available for the Form Progress Listing job:
-
Include Restricted Data: When this checkbox is selected, Vault includes data from restricted Forms if the job is initiated by a user with the Restricted Data Access permission.
-
Include Item Counts: When this checkbox is selected, Vault includes item counts for All Items, Items with Values, Items with Value Change, Items SDV Required Completed, Items SDV Required, Items DMR Required Completed, and Items DMR Required.
Output
The Form Progress Listing job CSV export and report include the columns listed below. If your Study is using Data Model V1, the SDV Required, Items SDV Required Completed, Items SDV Required, SDV %, SDV Age, DMR Required, Items DMR Required Completed, Items DMR Required, DMR %, and DMR Age columns will be blank in the job export and report output.
Requires Re-SDV and Requires Re-DMR in the Form Progress Listing: For studies created after 23R3, ‘Requires Re-SDV’ and ‘Requires Re-DMR’ are recorded in the Form Progress Listing. These columns will be blank for studies created before 23R3 or for studies where the First Review Date is not enabled. We only recommend enabling the First Review Date flag for existing studies if there is no review data.
Column Header | Description |
---|---|
Study | Study Name |
Country | Study Country Name |
Site | Site Number |
Subject | Subject Number |
Subject Status | Current Subject Status |
Event Group Label | Event Group Label of the Event Group where the Form is |
Event Label | Event Label of the Event where the Query is |
Event Group Sequence Number | Event Group Sequence Number |
Event Date | Event Date entered |
Form Label | Form Label |
Form Sequence Number | Form Sequence Number |
Form Status | Form Status (Planned, Blank, In Progress, Submitted, In Progress Post Submit) |
First Submission Date | Datetime when the Form was first submitted |
Latest Submission Date | Datetime when the Form was last submitted |
Number of Submits | Total number of Form submissions |
Restricted Form | Shows if the Form is Restricted or not (Yes/No value) |
Complete | Shows if the Form is complete/submitted, including ILB forms (Yes/No value) |
Intentionally Left Blank | Shows if the Form was Intentionally Left Blank (Yes/No value) |
Intentionally Left Blank Reason | The reason the Form was marked as Intentionally Left Blank |
Marked for Removal | Shows whether the Form is no longer needed |
Late | Shows if the Form is late based on the Event Date and the number of overdue days allowed (Yes/No value) |
Days Overdue | Shows the number of days beyond the overdue date |
All Items | Calculates the total number of items on the form |
Items with Values | Calculates the number of items on the form with a saved value |
Items with Value Change | Calculates the number of items on the form with at least one data value change |
SDV Plan | SDV Review Plan assigned to the Subject |
SDV Override Plan | SDV Review Plan override for the Form (from an override rule) |
SDV Required | Shows whether SDV is required for the Form |
Requires Re-SDV | Shows whether SDV needs to be completed again after being cleared due to updates by the site |
SDV Complete | Shows whether SDV was completed for the Form |
Items SDV Required | Number of items on the Form where SDV is required |
Items SDV Required Completed | Number of items on the Form where SDV is required and completed |
SDV % | Percentage of required SDV complete for the Form |
SDV Age | How long the Form has been submitted without SDV |
SDV Date | Date the Form was marked SDV |
DMR Plan | DMR Review Plan assigned to the Subject |
DMR Override Plan | DMR Review Plan override for the Form (from an override rule) |
DMR Required | Shows whether DMR is required for the Form |
Requires Re-DMR | Shows whether DMR needs to be completed again after being cleared due to updates by the site |
DMR Complete | Shows whether DMR was completed for the Form |
Items DMR Required | Number of items on the Form where DMR is required |
Items DMR Required Completed | Number of items on the Form where DMR is required and completed |
DMR % | Percentage of DMR complete for the Form |
DMR Age | How long the Form has been submitted without DMR |
DMR Date | Date the Form was marked DMR |
Frozen | Whether or not the Form is frozen (Yes/No value) |
Freeze Date | Date the Form was frozen |
Locked | Whether or not the Form is locked (Yes/No value) |
Lock Date | Date the Form was locked |
Signed | Whether or not the Form is signed |
Sign Date | Date the Form was signed |
Last Signed Date | Date the Form was last signed |
Total Queries | Total number of queries on the Form |
Open Queries | Total number of open queries on the Form |
Answered Queries | Total number of answered queries on the Form |
Closed Queries | Total number of closed queries on the Form |
Form Vault ID | Vof ID of the Form |
Last Run of Listing | Datetime when the listing was last run |
Query Detail Listing
The Query Detail Listing job generates a list of all Queries in the Study, with status details and operational data, as a CSV file. Users can filter this listing by Query Status, Query Team, Site, and Form. The output only includes Queries from restricted Forms if the user selected the Include Restricted Data checkbox and has the Restricted Data Access permission. The Query Progress Listing job is versionless. Note that if you have the Show Queries in the User Language setting configured, queries will display in the user’s language, not the vault language.
Enabling Team Query Restrictions and the Query Detail Listing: When the Team Query Restrictions study setting is not enabled, the Role column in the Query Detail Listing is populated with the user’s current role at the time of job generation. This information is not recorded in the query record. When the Team Query Restrictions setting is enabled in an ongoing study, the user’s role and team are stored on the query record at the time of the query action for queries moving forward and will populate in the Roles and Teams columns in the Query Detail Listing. Queries that were created prior to the Team Query Restrictions setting being enabled are not assigned a query team. If you want to keep the current roles for existing queries in the Query Detail Listing, we do not recommend that you enable Query Teams in an ongoing study.
Job Options
The following configuration options are available for the Query Detail Listing job:
- Include Restricted Data: When this checkbox is selected, Vault includes queries from restricted Forms if the job is initiated by a user with the Restricted Data Access permission.
Output
The Query Detail Listing job CSV export and report include the columns listed below. If your Study isn’t using Query Teams, the Query Team, Created by Query Team, Answered by Query Team, Closed by Query Team, Created by Role, Answered by Role, and Closed by Role columns will be blank in the CSV and report output.
Column Header | Description |
---|---|
Study | Study Name |
Country | Study Country Name |
Site | Site Number |
Subject | Subject Number |
Subject Status | Current Subject Status |
Event Group Label | Event Group Label of the Event Group where the query is |
Event Label | Event Label of the Event where the query is |
Event Group Sequence Number | Event Group Sequence Number |
Event Date | Event Date entered |
Visit Method | Visit method selected |
Form Label | Form Label of the Form where the query is |
Form Sequence Number | Form Sequence Number |
Form Status | Form Status |
Item Group Label | Item Group Label of the Item Group where the query is |
Item Group Sequence Number | Item Group Sequence Number |
Item OID (External ID) | External ID (OID) of the item that the query is attached to |
Item Label | Label of the item that the query is attached to |
Query ID | The query name (VV-XXXXX) (not the internal vault ID) |
Query Status | Current Status of the query |
Restricted Query | Shows if the query is Restricted or not (Yes/No value) |
Query Team | Query Team assigned to the query |
Source Type | Source type of the query |
Source System Name | Value optionally set by an API query addition, describing the name of the query source system |
Source User | Value optionally set by an API query addition, describing the user who opened the query |
Source ID | Unique identifier from the source of the query |
Days Unresolved | Days the query has been unresolved |
Manual Query | Shows if the query was manually created (Yes/No value) |
Query Rule | If a query rule, the rule that originates the query |
Original Query Text | First message text of the query |
Original Query Text in User's Language | Original text of the query in the User’s language |
Original Query Text in English | Original text of the query in English |
Latest Query Comment | Latest query message |
Latest Query Answer Text | Last answer of the query |
Number of Query Messages | The number of query messages on a query |
Item Value Before Query | Value of the item the query is attached to before query creation |
Item Value Now | Value of the item the query is attached to at the time of run |
Item Value Changed | Shows whether the value of the queried item changed (Yes/No value) |
Query Caused Data Change | Shows whether the data changed after query creation (Yes/No value). This field is determined by checking if the item value was modified between creation and closing of the query (by dates). |
Query Created Date | Datetime of the creation of the query |
Query Created By | User that created the query (or System) |
Created By Role | Role name of the user that created the query (or System) |
Created by Query Team | Query Team of the user that created the query |
Answered Date | Datetime of last answer of the query |
Answered By | User that last answered the query |
Answered by Role | Role name of the user that last answered the query |
Answered by Query Team | Query Team of the user that last answered the query |
Closed Date | Datetime of last closing of the query |
Closed By | User that last closed the query (or System) |
Closed By Role | Role name of the user that last closed the query (or System) |
Closed by Query Team | Query Team of the user that last closed the query |
Query Vault ID | Vault Query Object |
Last Run of Listing | Datetime when the listing was last run |
Form Progress Versioned Extract
The Form Progress Versioned Extract generates a list of all Forms in the Study, with status details and operational data, as a CSV file and according to the selected version.
Job Options
The following configuration options are available for the Form Progress Versioned Extract job:
-
Include Restricted Data: When this checkbox is selected, Vault includes data from restricted Forms if the job is initiated by a user with the Restricted Data Access permission.
-
Version: You can choose which release version of the Form Progress Listing job to run.
Event Progress Versioned Extract
The Event Progress Versioned Extract generates a list of all Events in the Study, with status details and operational data, as a CSV file or report and according to the selected version.
Job Options
The following configuration options are available for the Event Progress Versioned Extract job:
-
Include Restricted Data: When this checkbox is selected, Vault includes data from restricted Forms if the job is initiated by a user with the Restricted Data Access permission.
-
Version: You can choose which release version of the Event Progress Listing job to run.
Subject Progress Versioned Extract
The Subject Progress Versioned Extract generates a list of all Subjects in the Study, with status details and operational data, as a CSV file and according to the selected version.
Job Options
The following configuration options are available for the Subject Progress Versioned Extract job:
-
Include Restricted Data: When this checkbox is selected, Vault includes data from restricted Forms if the job is initiated by a user with the Restricted Data Access permission.
-
Version: You can choose which release version of the Subject Progress Listing job to run.
Query Detail Versioned Extract
The Query Detail Versioned Extract generates a list of all Queries in the Study, with status details and operational data, as a CSV file and according to the selected version.
Job Options
The following configuration options are available for the Query Detail Versioned Extract job:
-
Include Restricted Data: When this checkbox is selected, Vault includes data from restricted Forms if the job is initiated by a user with the Restricted Data Access permission.
-
Version: You can choose which release version of the Query Progress Listing job to run.
For more information about Study Progress Versioned Extracts jobs, see Study Progress Versioned Extracts.
Recalculate Normalized DateTime Values
After a site’s timezone is changed, this job recalculates all normalized datetime values (for datetime-type Items) to reference the new timezone.
Job Options
The following configuration options are available for the Recalculate Normalized DateTime Values job:
- Sites: Select Execute for All Sites to run this job in all Sites in your Study. Otherwise, use Select Sites to select specific Sites in which to run the job.
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
The following configuration options are available for the Reconstitute Code Requests job:
- Select Forms: You can choose to run this job on all coding forms in a Study or on select forms.
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
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: When this checkbox is selected, Vault includes data from restricted Forms if the job is initiated by a user with the Restricted Data Access permission.
-
Include Randomization Treatment: When this checkbox is selected, Vault includes randomized treatment information in the SYS_RAND dataset if the job is initiated by a user with Randomization enabled.
-
SDE Version: You can choose which version of the SDE to run. Columns may be added, removed, or changed between versions.
-
Clinical Data Options: You can select from a number of options to determine how Vault handles clinical data formatting in your extract.
-
Datasets to Export: You can choose which specific datasets to include in your extract.
-
External Connection: You can select an External Connection to receive the output file. Vault will send you a link to download the output when the job finishes if an External Connection isn’t selected.
-
Include Study Design (only available for 22R3 version): When this checkbox is selected, Vault includes a Definitions folder containing study design information in your extract.
-
Send Data to CDB (Version 23R2 and later): If you have CDB enabled, you can send SDE datasets to CDB.
Output
When the Study Data Extract job is completed, you can download a SAS or CSV file for each selected Study.
For more information about the Study Data Extract job, see Study Data Extracts.
Subject Progress Listing
The Subject Progress Listing job generates a list of all Subjects in the Study, with status details and operational data, as a CSV file. The Subject Progress Listing job is versionless.
Job Options
The following configuration options are available for the Subject Progress Listing job:
- Include Restricted Data: When this checkbox is selected, Vault includes data from restricted Forms if the job is initiated by a user with the Restricted Data Access permission.
Output
The Subject Progress Listing job CSV export and report include the following columns:
Column Header | Description |
---|---|
Study | Study Name |
Country | Study Country Name |
Site | Site Number |
Subject | Subject Number |
Subject Status | Current Subject status |
Restricted Subject | Shows if the Subject is Restricted (Yes/No value) |
Most Recent Visit | Event Label of the last visit/event |
Date of Most Recent Visit | Event Date of the last visit/event |
Method of Most Recent Visit | Visit Method of the last visit/event |
Next Event | Event Label of the next scheduled visit/event |
Entry Complete | Shows if all forms expected for a Subject have been submitted (Yes/No value) |
SDV Plan | SDV Plan assigned to the Subject |
Subject SDV Required | Shows whether SDV is required for the Subject |
Subject SDV Complete | Shows if all forms and all event dates that require SDV have been marked SDV for the Subject |
Subject SDV Completion Date | The date that SDV was completed for the Subject |
Forms SDV Completion Date | The date that SDV was completed on all forms for the Subject |
DMR Plan | DMR plan assigned to the Subject |
Subject DMR Required | Shows whether DMR is required for the Subject |
Subject DMR Complete | Shows if all forms and all event dates that require DMR have been marked DMR for the Subject |
Subject DMR Completion Date | The date that DMR was completed for the Subject |
Forms DMR Completion Date | The date that DMR was completed on all forms for the Subject |
Frozen | Shows if all forms, event dates, and visit methods have been frozen for the Subject |
Locked | Shows if all forms, event dates, and visit methods have been locked for the Subject |
Signed | Shows if all forms, event dates, and visit methods have been signed for the Subject |
All Queries Closed | Shows if all queries for the Subject have been closed |
Clean | Shows if a Subject is "clean," meaning that all forms, event dates, and visit methods are submitted, signed, and locked and all queries are closed. SDV and DMR should also be completed (Yes/No value) |
Forms | Total number of forms for Subject |
Forms Complete | Number of forms submitted |
Forms Incomplete | Number of forms that are blank or in progress (e.g. forms that are not submitted yet) |
Forms SDV Required | Number of forms that are SDV required for the subject |
Submitted Forms SDV Required | Number of submitted forms that are SDV required for the subject |
Forms SDV Complete | Number of forms that were marked as SDV reviewed for the subject |
% Forms SDV Complete | Percentage of forms that were marked as SDV reviewed for the subject compared to the number of forms marked SDV required |
Forms Not SDV | Number of forms submitted that require SDV based on the review plan but have not been marked for SDV |
Event Dates Not SDV | Number of event dates that require SDV that have not been marked SDV for the Subject |
Visit Methods Not SDV | Number of visit methods that require SDV that have not been marked SDV for the Subject |
Forms DMR Required | Number of forms that are DMR required for the subject |
Forms DMR Complete | Number of forms that were marked as DMR reviewed for the Subject |
Submitted Forms DMR Required | Number of submitted forms that are DMR required for the subject |
% Forms DMR Complete | Percentage of forms that were marked as DMR reviewed for the subject compared to the number of forms marked DMR required |
Forms Not DMR | Number of forms submitted that require DMR based on the review plan but have not been marked for DMR |
Event Dates Not DMR | Number of event dates that require DMR that have not been marked DMR for the Subject |
Visit Methods Not DMR | Number of visit methods that require DMR that have not been marked DMR for the Subject |
Forms Not Frozen | Total number of submitted forms that are not frozen |
Event Dates Not Frozen | Total number of event dates that are not frozen |
Visit Methods Not Frozen | Total number of visit methods that are not frozen |
Forms Not Locked | Total number of submitted forms that are not locked |
Event Dates Not Locked | Total number of event dates that are not locked |
Visit Methods Not Locked | Total number of visit methods that are not locked |
Forms Not Signed | Total number of submitted forms that are not signed |
Event Dates Not Signed | Total number of event dates that are not signed |
Visit Methods Not Signed | Total number of event dates that are not signed |
Total MC | Total Medical Coding Requests for the Subject |
MedDRA MC | Total MedDRA Medical Coding Requests |
WHODrug MC | Total WHODrug Medical Coding Requests |
MedDRA MC Need Coding | MedDRA Medical Coding Requests that are not yet coded |
WHODrug MC Need Coding | WHODrug Medical Coding Requests that are not yet coded |
Total Queries | Total number of queries |
Open Queries | Total number of open queries |
Answered Queries | Total number of answered queries |
Closed Queries | Total number of closed queries |
Subject Vault ID | Vof ID of the Subject |
Last Run of Listing | Datetime when the listing was last run |
Workbench Export
The Workbench Export job exports study data in Vault EDC and Vault Coder, and then sends the export package to CDB Workbench. CDB Workbench 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 CDB Workbench. You can download and view the output from EDC Tools > Jobs or from Workbench > Import.