WashU REDCap e-Consent Standard Operating Procedures

All procedures for the WashU REDCap e-Consent can be found in this WUSTL Box folder:

Standard Operating Procedures - Using the REDCap Template to Create an eConsent

Creating a new REDCap e-consent project?

1. Use file SOP WUSTL REDCap Academic eConsent v1.04.1.pdf to create, edit, and test the project.

2. Watch REDCap Workshop – The WUSTL REDCap E-Consent Template to guide you through this process.

Already have a REDCap e-consent project and modifying your Informed Consent Form?

1. Use file SOP WUSTL REDCap eConsent Modification v1.01.pdf to modify the e-consent survey to match the modified Informed Consent Form.

a.     The IRB will not ask to review the modified e-consent survey.  It is the responsibility of the research team to ensure the text in the e-consent survey matches exactly the text in the modified Informed Consent Form approved by the IRB 

Already have a project in production but can’t find the “Save & Mark Survey as Complete” button?

1. Short term solution: Watch video Save_Mark_Survey_Complete_Workaround.mp4 to show how to manually trigger the delivery of the fully executed consent form.

2. Long term solution: Use file SOP Automating Delivery of Fully Executed Consent on Current Project v1.02.pdf and watch video Automating Delivery of Fully Executed Consent on Current Project v1.02.mp4 to set up an external module that will automate the delivery.

Creating a REDCap e-consent that needs multiple signatures on the consent?

There is no SOP for projects than need multiple signatures on the consent.

Use file SOP WUSTL REDCap Academic eConsent v1.04.pdf to create a project. Manually add the additional signature fields required to the e-consent survey.  If signatures needed varies across participants, for example due to age or cognitive ability, use branching logic to make the correct signatures appear on the e-consent survey.  For example, if only a participant signature is required for participants 18 and older, but participant and parent or legal guardian signature is required for participants under 18, create an [age] field on a screening form.  The [age] field can then be used to create branching logic for the parent or legal guardian signature fields, e.g. [parent_lg_signature] only appears if [age] < 18.