Before (1.0 e-consent)
Required continual updating of the consent instrument (or new consent as a whole) was needed everytime a new consent version was needed
Multiple, different consent instruments and fields were needed to accommodate different languages, DAGs, etc.
After (2.0 e-consent)
A single instrument and single descriptive field is continually used for all versions of a single consent document.
The single descriptive field can host multiple, different consent forms based on…
Participants language (if using MLM)
1 active form for english
1 active form for spanish
Both tied to the same field and instrument!
Data Access group
Example of how 2.0 it works:
Before e-consent 2.0 is released study teams should:
Ensure the ‘version’ number in your framework settings is correct, as when 2.0 framework is rolled out whatever number you have listed here will be what is used by default in the new setting.
e-Consent 2.0 will be release on xxxxx
The below update steps are provided to ensure you don’t have duplicate consent images/fields displayed in your consent.
After e-consent 2.0 is released updates to your instrument and settings must be made:
Plan a time to update your project when participants will not be completing consent
Mark you Consent survey as ‘Inactive’ via ‘survey settings’
Review you current consent instrument to verify if your consent hosts your consent pages in a single descriptive field or multiple separate descriptive fields?
If single, you’ll need to remove the (in-line text) or remove the attached document. Why? The e-consent document is now uploaded via the framework settings and NOT in the instrument itself.
If multiple, you’ll need to remove or hide the all but 1 descriptive field. Why? The e-consent document is now uploaded via the framework settings and NOT in the instrument itself.
Add your version settings & consent form following: (link)
Once the new settings & form is setup is complete, 're-activate' your survey! (via survey settings)