Click on the magnifying glass to the right. Starting typing a topic you wish to learn about

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

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

Never delete (old) consent instruments, this will result in lost data!

Instead, you can ‘deactivate’ the old survey instrument which will keep you data intact, but ensures said survey is no longer accessible to participants. This is completed using ‘survey settings’, view the below process for details.

Initial Considerations
Design changes after the Production phase are discouraged but sometimes needed. If a new version of the consent is needed, it is critical to modify the project in such a way as to not lose existing data nor compromise the audit trail of the REDCap e-Consent.

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

  1. Creation of new instruments

  2. Branching Logic

Expand the process you wish to review below

The Process

Updating E-Consent using new instrument creation:

 Click here to 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

  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 expiration 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)

Adjust your operational processes or survey settings to send the new e-consent to the participant & retire the old:

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

Updating E-Consent using Branching Logic:

 Click here to expand...

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 expiration 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

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?
A. Use a two-part system.

  1. E-consent Survey: consent is signed, reviewed, and submitted within the e-consent framework.

  2. Documentation of Informed Consent /Attestation data form (for staff) can have the participant's information piped in and includes a date & signature field for the PI.



  • No labels