Modify E-Consent: (version control)

using branching logic:

1. Keep the existing public survey instrument as the first instrument in the project

   

2. Create new fields for each updated section of the consent.

   1. Updated fields should sit directly under the original field

3. Create a field in the public survey to denote Consent Version.

   1. Use Action tags to ensure that only the current version of the e-consent is selected.

   2. Use the @Default to ensure only the most current version is presented and @HIDDEN SURVEY)
      

      
      

4. Use of branching logic makes the new fields visible only when the appropriate current version of the e-consent is selected.

   

5. Open survey settings to preform the below updates:

   1. Update version number from 1 > 2 (you do not have to use the number 2, but the value listed MUST be different from the first version). Best practice would include version number and IRB approval date.

      

       

   2. Below is an example of the issue that occurs if you do NOT update your version number:

      1. participant #3 actually filled out Version 2 but because the survey settings were not updated, the accurate version is not shown in the PDF file display. (However if you open the PDF it will be second version signed by the participant)
          

         

6. After saving your survey settings, the next participant consented will accurately reflect consent version

Modifying the e-consent via new instrument:

1. Since your project is in Production, you’ll need navigate to your online designer and enter Draft Mode

   

2. Copy your existing E-consent form to quickly copy over the bulk of your E-Consent

   

3. Move the E-consent (version 2) instrument under the now expired (version 1) instrument

   

    

4. Apply needed updates to new version (2) such as…

   1. Upload IRB stamp with new expiration date

   2. Apply any consent field/verbiage updates required

   3. All Consent component should be included in your new version

5. Submit your drafted changes for review to a REDCap Administrator

6. STOP HERE UNTIL YOUR CHANGE REQUEST HAS BEEN APPROVED

7. Once the requested changes have been implemented…

   1. Enable E-Consent Version 2 as a survey

8. Open E-Consent Version 2 survey settings to perform the below:

   1. Update the copied Survey Title:

      1. This is what will appear at the top of the participants survey page, edit as needed.

      2. Note, the survey title (red) and the instrument name (blue) can be different.

         

   2. Setup the E-consent Framework

      1. Update version number from 1 > 2 (you do not have to use the number 2, but the value listed MUST be different from the first version). Best practice would include version number and IRB approval date.

         

          

   3. CRITICAL STEP: in addition to updating the version number, you also must ensure the framework is pulling data from the new fields in the new consent version (2) for the below inputs:

      1. First name (v2)

      2. Last Name (v2)

      3. DOB (v2)

      4. Signature (v2)

         

9. Adjust your operational processes or survey settings to send the new e-consent to the participant & retire the old. How this is done depends on your project operational flow and how surveys are sent to participants.

Suggested steps:

1. Limit user access to the original e-consent survey through ‘User settings’, however this will not limit ASI’s/Form display logic. If your project uses either of these functionalities, further steps are required to ensure the old consent is no longer used or triggered.

2. Hide the instrument using Form Display logic or by making the survey ASI ‘Not Active’.

3. The survey itself can be switched from active > ‘Survey Offline’ in survey settings, which ensure respondents will not be able to take the survey, even if mistakenly triggered!