REDCap upgrade March 22 adds new features; expect downtime from 8 p.m. to 10 p.m.
On the evening of Tuesday, March 22, 2018 the CTS-IT will upgrade REDCap from version 8.2.0 to 8.3.0. You can expect a downtime for REDCap from 8:00 pm to 10:00 pm while we complete the upgrade.
The new version of REDCap, scheduled for release on March 22, 2018, has some new features and several improvements to existing features, including:
New features: PDF Auto-Archiver and eConsent Framework
- Upon survey completion, a compact PDF copy of the survey response can be automatically stored in the project’s File Repository, from which the archived PDFs can be downloaded at any time.
- This setting is located on the Survey Settings page in the Online Designer; thus, it can be enabled for any given survey in a project.
- This feature, which works together with the PDF Auto-Archiver, provides functionality for users to implement electronic consent (e-Consent) using a survey as the consent form, such as for capturing the consent of a research study participant.
- The e-Consent Framework option adds two things to the typical survey-taking process. 1) Before a participant completes the survey, an extra certification page is added to end of the survey that displays an in-line PDF copy of their survey responses in which they will be asked to confirm that all information in the document is correct. Once they confirm all is correct, the survey will then be marked as complete. The survey will not be considered complete until they fulfill the certification step. 2) Upon completion of the survey, a static copy of their responses in the form of a consent-specific PDF will be stored in the project’s File Repository. The consent-specific PDF will have the values of the e-Consent Framework Options inserted at the bottom of each page in the PDF. These values (i.e., name, date of birth, etc.) are added to the PDF as extra documentation of the identity of the person who is consenting.
Improved Logging for Automated Survey Invitations
- The project Logging page now provides useful contextual information for the Automated Survey Invitations (ASI) logged event “Automatically schedule survey invitation”, in which it will display the record name, survey title, and event name (if longitudinal).
- The project Logging page now logs when a survey invitation that was scheduled via ASI gets deleted due to the ASI option “Ensure logic is still true before sending invitation?”, in which the logged event will display useful contextual information, such as the record name, survey title, and event name (if longitudinal).
- The project Logging page now logs when a survey invitation is deleted or when its send-time is modified on the Survey Invitation Log, in which the logged event will display useful contextual information, such as the record name, survey title, and event name (if longitudinal).
Survey Invitation Log
- Added new “Record ID” column in the Survey Invitation Log table to allow users to find specific invitations more efficiently. Note: If the record name should not be displayed in order to preserve the anonymity of a response (e.g., participant identifier is not used, designated email field is not used), it will instead display an icon indicating that the record name cannot be displayed.
- Added new filter on the Survey Invitation Log table to allow users to filter the invitations by record ID.
- The Survey Invitation Log now contains an extra column on the right-hand side to allow users to delete many scheduled invitations at once (rather than having to delete them one at a time).
Added new “Record ID” column in the Participant List table
- In previous versions, the record ID was appended to the email address in the “Email” column. Having its own column will allow users to find specific participants more efficiently.
- When performing an API export in JSON format for the API methods Export Users, Export Project Info, Export Survey Participants, and Export Events, while the values in the API response were all correct, some API scripts were having trouble with the fact that some integers were returned in string format (surrounded in quotes) rather than as literal integers in the JSON response. Now they should all be returned as literal integers.
Add/Edit Branching Logic” popup in the Online Designer
- When opening the “Add/Edit Branching Logic” popup in the Online Designer, it could sometimes be very slow to open if the project contains many fields, especially many multiple-choice fields. The popup could even be slow when the selected field does not even have branching logic yet. To improve this, it now defaults to selecting the “Advanced” option first when the popup opens and only attempts to load the “Drag-N-Drop” draggable field choices when that option has been selected by a user. While this won’t completely alleviate the issue of the “Drag-N-Drop” option being slow when there are many fields, this will make it much more palatable in a majority of situations when branching logic is being added/edited in the Online Designer.
Branching logic in the Online Designer
- If a field has branching logic, the Online Designer now displays the logic (up to the first 65 characters) on the field so that the user can view it easily without having to open the Add/Edit Branching Logic popup.