Versions Compared

Version Old Version 15 New Version 16
Changes made by

Alyssa Hill

Alyssa Hill

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

NOTE: This article should only be used to modify your E-Consent survey in Production in order to apply version updates as necessary. If you are looking to create a e-consent survey for the first time, see: E-Consent Initial Setup

...

There are two ways to implement new versions of e-consent:

  1. Creation of new instruments

  2. Branching Logic

If you are using a public survey as your e-consent you must use the branching logic methodology provided Expand the process you wish to review below

...

The ProcessThe

optimal way to add a new version to an existing E-consent Public Survey project is to modify the current instrument Updating E-Consent using Branching Logic:

Expand

using branching logic:

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

...

  1. Image Added

  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)

...

    1. Image Added

...

    1. Image Added

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

...

  1. Image Added

  2. 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)

      Image Modified

       

    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)
         

...

      1. Image Added

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

Image Added

Updating E-Consent using new instrument creation:

Expand

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

    Image Added

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

    Image Added

  3. Move the E-consent (version

...

  1. 2) instrument under the now expired (version 1) instrument

    Image Added

     

  2. 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

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

  4. STOP HERE UNTIL YOUR CHANGE REQUEST HAS BEEN APPROVED

  5. Once the requested changes have been implemented…

    1. Enable E-Consent Version 2 as a survey

  6. Open E-Consent Version 2 survey settings to preform the below:

    1. Setup the E-consent Framework

    2. 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)

      Image Added

       

    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. Signautre (v2)

        Image Added

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 switch from active > ‘Survey Offline’ in survey settings, which ensure respondents will not be able to take the survey, even if mistakenly triggered!

    Image Added

...

Additional Considerations

Q. What is the optimal way to handle multiple signatures? For instance, the parent or participant consents and then our PI would need to sign the consent. Usually this is all done in person, however, with e-Consent what is the best workflow? I know the records are locked, so what is the best way to have that signed?
A. Use a two-part system.

Anchor
_GoBack
_GoBack

  1. Survey 1 – e-Consent, signed, reviewed, and submitted within the e-consent framework.Survey 2 – is triggered by submission of survey 1 and is emailed to the study coordinator or PI. The survey is an attestation that has

  2. Data entry attestation form for staff – form which can have the participant's information piped in and can be signed by the PI, reviewed, and also submitted within the e-consent framework.

...

  1. includes a date & signature field for the PI.