Initial Considerations:
Ensure the ‘version’ number in your current framework settings is correct, whatever number you have listed here, by default will be used in the 2.0 framework as well.
Your current e-consent survey will continue to function with success and save to your file repository with the already configured settings when the system is updated to the 2.0 framework. However, the NEXT time you go to add a new version, you will need to take the below steps to ensure success.
Before (1.0)
How to access the framework:
Survey settings > framework settings
Required continual updating of the consent instrument, logic, etc, everytime a new consent version was applied
Multiple, different consent instruments and fields were needed to accommodate different languages, DAGs, etc.
E-consent framework was hosted in ‘survey settings’
After (2.0)
How to access the framework:
Online Designer < ‘e-consent framework and PDF snapshot’
A single instrument and single descriptive field is continually used for all versions of a single consent.
The single descriptive field can host multiple, different consent forms based on…
Data Access group
Participants language (if using MLM)
1 active form for english
1 active form for spanish
The correct consent form will be dynamically displayed based on the participants language selection/ DAG group.
E-consent framework is now hosted in the designer page
| Info |
|---|
Once you need to upload a NEW version of your consent document, the below actions must be taken!
|
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 your Consent survey as ‘Inactive’ via ‘survey settings’
Review & update you current consent instrument so that only the below fields are left:
Reduce ‘descriptive’ fields so that only a single, empty descriptive exists
Keep existing data capture fields as is (discrete fields, name, date, signature)
You’ll need to remove or hide the all but 1 descriptive field.
If your descriptive field host hosts an image, remove the file
If your descriptive field host in-line text, remove the text
Delete or use the @HIDDEN action tag to hide any (old) additional ‘descriptive’ fields (excluding the now blank field.) The single, blank, descriptive field should not be hidden as this is needed for step 5b)
is now all this is needed. If your previous econsent surveys were set up accurately, the previous records files are already saved to your file repo and will not be affected when you delete old fields.
If you don't feel comfortable deleting your old fields, use both @HIDDEN-PDF and @HIDDEN action tags to ensure the invalid, old fields aren’t in new records PDF file.
Why delete? The e-consent document is now uploaded via the framework settings and NOT in the instrument itself. If you don’t clean up your instrument, you will have duplicated and/or invalid consent images displayed. !
Version settings will be automatically mapped
Setup your new consent form via ‘+ Add Consent Form’ feature
.png?version=1&modificationDate=1735585006671&cacheVersion=1&api=v2&width=512)
Update version number if applicable
Only applicable if you are uploaded a new version of what was previously in place
Select your empty ‘descriptive’ field for the ‘Placement of consent form’
Select ‘Consent Form (Inline PDF)’ to upload your consent PDF document
Click ‘Add new consent form’ to finalize
.png?version=1&modificationDate=1735585014025&cacheVersion=1&api=v2&width=512)
Once the new settings & form is setup is complete, 're-activate' your survey! (via survey settings)
