Clincapture Training - Deploy And Manage

1. Testing should be performed in @Build prior to moving study definition to Production.

True

False

The statement suggests that testing should be conducted in the "Build" phase before moving the study definition to the "Production" phase. This implies that it is important to ensure that the study definition is thoroughly tested and any issues or bugs are identified and resolved before it is deployed in a live production environment. By conducting testing in the build phase, potential issues can be detected early on and addressed, reducing the likelihood of problems occurring in the production phase. Therefore, the answer "True" indicates that testing should indeed be performed in the build phase prior to moving the study definition to production.

Explanation

The statement suggests that testing should be conducted in the "Build" phase before moving the study definition to the "Production" phase. This implies that it is important to ensure that the study definition is thoroughly tested and any issues or bugs are identified and resolved before it is deployed in a live production environment. By conducting testing in the build phase, potential issues can be detected early on and addressed, reducing the likelihood of problems occurring in the production phase. Therefore, the answer "True" indicates that testing should indeed be performed in the build phase prior to moving the study definition to production.

2. Select the supported data extract file formats. (mark all that apply)

Microsoft Excel

R

SAS Transport

CDISC ODM XML

Microsoft Access

DB2 Transfer

ClinCapture supports a number of data export formats including: Excel, Delimited (CSV, Tab), SAS, SPSS, CDISC ODM XML, and HTML.

Explanation

ClinCapture supports a number of data export formats including: Excel, Delimited (CSV, Tab), SAS, SPSS, CDISC ODM XML, and HTML.

Submit

3. Rules are moved to production by:

Creating new rules in Rules Studio specific to Production

Exporting using XML and importing rules under Tasks -> Build Study -> Rules

ClinCapture Support must move your rules for you using DB scripts

Rules should never be moved to production

Rules are created and changed with Rule Studio but must be moved from @Build to Production using the XML export and import. Rules can be moved to production individually or all at once.

Explanation

Rules are created and changed with Rule Studio but must be moved from @Build to Production using the XML export and import. Rules can be moved to production individually or all at once.

4. To hide a CRF from a specified CRC User, which ClinCapture feature may be used?

Hidden CRFs

Override CRFs

CRF Masking

CRC Hiding

CRF Masking allows you to hide specific CRFs from users with the Clinical Research Coordinator role. Investigators will see all CRFs in the subject casebook.

Explanation

CRF Masking allows you to hide specific CRFs from users with the Clinical Research Coordinator role. Investigators will see all CRFs in the subject casebook.

5. When exporting data from ClinCapture, the following is allowed:

Extracting data for specified subjects

Extracting data for all CRFs or specified CRFs

Extracting data for only CRFs marked SDV Complete

Extracting data for specified Groups

Data extracts allow users to export data based on specific CRFs, time range, and data completion status. Exporting subject groups, specific subjects, and by SDV status are not currently supported.

Explanation

Data extracts allow users to export data based on specific CRFs, time range, and data completion status. Exporting subject groups, specific subjects, and by SDV status are not currently supported.

6. A dataset export definition may be changed after creation

True

False

Datasets can be created and edited as necessary over the life of the study.

Explanation

Datasets can be created and edited as necessary over the life of the study.

7. The audit trail related to subject data can be (check all that apply):

Exported with Subject casebooks

Viewed on the Discrepancy Note

Accessed from the Subject Record

Downloaded in MS Excel format

The audit trail related to subject data can be exported with Subject casebooks, viewed on the Discrepancy Note, accessed from the Subject Record, and downloaded in MS Excel format.

Explanation

The audit trail related to subject data can be exported with Subject casebooks, viewed on the Discrepancy Note, accessed from the Subject Record, and downloaded in MS Excel format.

Submit

8. A User may only execute data exports for dataset definitions that they create:

True

False

A user can export any dataset which is visible to them. Site users can only see data extracts created at their site while study users can see data extracts across the study including all sites.

Explanation

A user can export any dataset which is visible to them. Site users can only see data extracts created at their site while study users can see data extracts across the study including all sites.

9. Exports may be schedule to occur at defined time points, and are called:

Schedule Exports

Export Jobs

Data Extracts

Casebooks

Users can schedule data exports to occur at specific time points by going to Tasks -> Jobs and selecting Export Jobs.

Explanation

Users can schedule data exports to occur at specific time points by going to Tasks -> Jobs and selecting Export Jobs.

10. To move a study into Production, the recommended order of the tasks is:

1

2

3

4

5

6

Many of the configuration settings are inherited from the Study down to the User so the steps for promotion to Production should be done in order: 1. Study Parameters, 2. Events, 3. Groups, 4. Rules, 5. Sites, 6. Users.

Explanation

Many of the configuration settings are inherited from the Study down to the User so the steps for promotion to Production should be done in order: 1. Study Parameters, 2. Events, 3. Groups, 4. Rules, 5. Sites, 6. Users.

Submit