...
| Page Tree | ||||||
|---|---|---|---|---|---|---|
|
Save and Mark Complete Button Missing
There was an upgrade to REDCap in the summer of 2023 that caused a major modification to how the original e-consent process worked. The major issue was that a Save & Mark Complete button no longer functioned as it had previously.
...
...
REDCap e-Consent
...
Short term solution: Watch video Save_Mark_Survey_Complete_Workaround.mp4 to show how to manually trigger the delivery of the fully executed consent form.
...
Long term solution: Use file SOP Automating Delivery of Fully Executed Consent on Current Project v1.02.pdf and watch video Automating Delivery of Fully Executed Consent on Current Project v1.02.mp4 to set up an external module that will automate the delivery.
Modifying a REDCap e-Consent
Open the WashU REDCap e-Consent Procedures Box folder.
Use file SOP WUSTL REDCap eConsent Modification v1.01.pdf to modify the e-consent survey to match the modified Informed Consent Form.
The IRB will not ask to review the modified e-consent survey. It is the responsibility of the research team to ensure the text in the e-consent survey matches exactly the text in the modified Informed Consent Form approved by the IRB.
REDCap e-Consent with multiple signatures
There currently is no SOP for projects that need multiple signatures on the consent. Adding multiple signatures is complex There are new tools coming to REDCap in late 2024 to help reduce the complexity of REDCap e-consent requiring more than one signature or a consent and assent. For now:
Use file SOP WUSTL REDCap Academic eConsent v1.04.1pdf to create a project. Manually add the additional signature fields required to the e-consent survey. If signatures needed varies across participants, for example due to age or cognitive ability, use branching logic to make the correct signatures appear on the e-consent survey. For example, if only a participant signature is required for participants 18 and older, but participant and parent or legal guardian signature is required for participants under 18, create an [age] field on a screening form. The [age] field can then be used to create branching logic for the parent or legal guardian signature fields, e.g. [parent_lg_signature] only appears if [age] < 18.
...