REDCap 14.5 LTS New Features
Version | Release Date | Version Type | Log Type | Descriptions |
14.5.4 | 7/30/2024 | Standard | Improvement | Improvement: Multi-Language Management can now be utilized by MyCap. Users will see a new "MyCap" tab on the MLM setup page, which will allow them to translate their custom MyCap elements that will appear to participants in the MyCap Mobile App. Participants will be given the choice to use any of the project's MLM languages after opening and viewing the MyCap Mobile App. |
14.5.4 | 7/30/2024 | Standard | Improvement | Improvement: REDCap now supports the "s" HTML tag for strikethrough (note: the "strike" HTML tag was already supported). |
14.5.4 | 7/30/2024 | Standard | Improvement | Improvement: The "Help & FAQ" page has been updated with new content (thanks to the FAQ Committee). |
14.5.4 | 7/30/2024 | Standard | Improvement | Improvement: The "strikethrough" styling button has been added to the toolbar in the rich text editor in all the places where the editor is used. |
14.5.4 | 7/30/2024 | Standard | Improvement | Improvement: When using MyCap in a project, users can now customize the notification time (default 8:00AM) for MyCap notifications to participants using the MyCap mobile app. |
14.5.4 | 7/30/2024 | Standard | Change | Change/improvement: If a custom primary key field has been added to any given REDCap database table that does not have an auto-incrementing field that serves as the primary key, the "database structure is incorrect" warning in the Control Center will no longer recommend that this extra field (and its key) be deleted. This should help institutions where their local IT support is recommending or forcing them to add primary keys to all REDCap database tables (for various reasons). |
14.5.5 | 7/30/2024 | Long Term Support (LTS) | New Feature | New LTS branch based off of REDCap 14.5.4 (Standard) Note: Please see the Standard Release ChangeLog for the full list of new features and changes released between the previous LTS and this new LTS branch. |
14.5.3 | 7/25/2024 | Standard | Improvement | Improvement: More user experience improvements for the Online Designer, including a new dismissible popup that alerts the user about the new "drag-n-drop" behavior for moving fields in the Online Designer. Additionally, users can now limit the deactivation/reactivation to certain action tags in the Quick Modify Field(s) popup. In previous versions, users could only deactivate/reactivate all action tags for the selected fields, but now users may provide specific actions tags that will be deactivated/reactivated. |
14.5.3 | 7/25/2024 | Standard | Change | Change/improvement: The internal service check on the Configuration Check page that checks the main REDCap survey end-point now works even when the REDCap system is set as "Offline". |
14.5.3 | 7/25/2024 | Standard | Change | Change: REDCap has been verified to be fully compatible with PHP 8.3. |
14.5.2 | 7/18/2024 | Standard | Change | Change/improvement: Small change in JavaScript to improve loading speed and calculation speed on data entry forms and survey pages. (Ticket #235138) |
14.5.2 | 7/18/2024 | Standard | Change | Change/improvement: Small change in JavaScript to improve loading speed slightly on data entry forms and survey pages in specific situations. (Ticket #235136) |
14.5.2 | 7/18/2024 | Standard | Change | Change/improvement: When a user moves a project to production and they opt to delete all records during the process, this is now specifically denoted on the Logging page, which will now list the logged event as "Move project to Production status (delete all records)". |
14.5.1 | 7/15/2024 | Standard | Improvement | Improvement: In the "Move Field" dialog in the Online Designer, the user may now choose "Insert at top of this form" or (if the field is part of a matrix) "Insert at the top of the matrix group" from the field drop-down. |
14.5.1 | 7/15/2024 | Standard | Change | Change: Added 2 new data tables and 3 new log_event tables to help long-term performance going forward. |
14.5.0 | 7/11/2024 | Standard | New Feature | New features: Enhanced e-Consent Framework and PDF Snapshot Functionality |
| ||||
Overview - A new page named "Settings for e-Consent & PDF Snapshots" (linked from the Online Designer) serves as the new location where users can enable and set up the e-Consent Framework for a given survey and also set up triggers for storing PDF Snapshots. In previous versions, the e-Consent Framework and PDF Snapshot settings all existed on the Survey Settings page as several disparate options, but now they have been consolidated on this new page as two separate tabs. While these two exist as separate features, there is some overlap of functionality since the e-Consent Framework does ultimately store a copy of the PDF Snapshot for the e-Consent response. In addition to moving these features to the new page, both have been given enhancements, which are detailed below. View a 5-minute overview video of the new features: https://redcap.link/econsent2vid | ||||
| ||||
Overall Benefits of the New Features - Streamlined Consent Process: Simplify and enhance the electronic consent process for both researchers and participants. Improved Data Integrity: Ensure secure and organized storage of consent forms and survey responses. Enhanced Compliance: Meet regulatory standards such as ICH and FDA requirements with robust version control and audit trails. | ||||
14.5.0 | 7/11/2024 | Standard | Improvement | Improved PDF Snapshot Functionality: Audit Trails: Improved, detailed audit trails for consent form completions and PDF snapshot generations. |
14.5.0 | 7/11/2024 | Standard | Improvement | Improved PDF Snapshot Functionality: Automatic Saving: Save PDF copies of survey responses (i.e., snapshots) to the project's File Repository or to specified File Upload fields. In previous versions, this would have been set up using separate features on the Survey Settings page, but now they can be set up as specific settings of a PDF Snapshot trigger. |
14.5.0 | 7/11/2024 | Standard | Improvement | Improved PDF Snapshot Functionality: Custom Logic-based Triggers: Create custom triggers for generating PDF snapshots based on specific conditions using conditional logic. Whenever data is being saved for a record (on a survey, form, API, data import, etc.), if the logic of the snapshot trigger evaluates as True, then a PDF snapshot will be saved to whatever location is specified. Note: Logic-based triggers can only be triggered once per record, whereas survey-completion-based triggers (including e-Consent surveys) will store a new snapshot every time the survey is completed (because surveys may possibly be completed multiple times if certain Survey Settings are defined). |
14.5.0 | 7/11/2024 | Standard | Improvement | Improved PDF Snapshot Functionality: File Naming Customization: Customize the file names of PDF snapshots using static text or piping, appended with date-time stamps. |
14.5.0 | 7/11/2024 | Standard | Improvement | Improved PDF Snapshot Functionality: Note: Non-e-Consent PDF Snapshot triggers will always store the PDF in the default MLM language, but an e-Consent PDF Snapshot trigger will always store the snapshot in the participant's chosen language. |
14.5.0 | 7/11/2024 | Standard | Improvement | Improved PDF Snapshot Functionality: Snapshot Re-triggering: Perform re-triggering of PDF Snapshots while on a data entry form. If the user has "View & Edit" Data View privileges on the current instrument, they will see a "Trigger Snapshots'' link in the button box at the top-left of the page. This will allow them to trigger or re-trigger any given PDF snapshot (although "survey completion" snapshot triggers specifically require that the survey be completed first). Additionally, for logic-based triggers, the logic does not have to currently be True in order to trigger/re-trigger it. |
14.5.0 | 7/11/2024 | Standard | Improvement | Improved PDF Snapshot Functionality: Snapshot Scope: The "scope" of the snapshot must be defined when creating a new snapshot trigger. The scope refers to the data content inside the PDF, i.e., which instruments are included in the snapshot (a single instrument, multiple instruments, or all instruments/events). Note: The PDF snapshot created by completing an e-Consent survey will only ever include just that single survey response. But for non-e-Consent snapshots, users may define the scope of the snapshot. |
14.5.0 | 7/11/2024 | Standard | Improvement | Improved PDF Snapshot Functionality: Support for Multi-Form Consents: Combine multiple forms and/or signatures into a single PDF snapshot. Define a PDF snapshot that contains multiple instruments in order to potentially capture multiple signatures, and then store the snapshot in the File Repository or a File Upload field. |
14.5.0 | 7/11/2024 | Standard | Improvement | Improved PDF Snapshot Functionality: Vault Storage Integration: If using the system-level feature "e-Consent Framework: PDF External Storage Settings (for all projects)", all PDF snapshots generated via completed e-Consent surveys will automatically be stored on the external server (i.e., "The Vault"). This feature existed in previous versions and continues to function in the same way. Noted new feature: If a multi-instrument PDF snapshot is being stored in the File Repository, in which it contains at least one completed e-Consent survey response, that snapshot will automatically be stored in the Vault. However, a project-level setting named "Store non-e-Consent governed PDF Snapshots on the External Storage server if the snapshot contains a completed e-Consent response" exists on the "Edit Project Settings" page that is set to Yes/Enabled by default, in which it can be disabled if the REDCap administrator wants only e-Consent governed PDF snapshots to be stored in the Vault and thus not store multi-instrument snapshots that happen to contain an e-Consent response in the Vault. |
14.5.0 | 7/11/2024 | Standard | Improvement | Improvement/bug fix: A new project-level setting "Hide closed/verified data queries from Data Quality results" has been added that can be used with the Data Resolution Workflow. This setting defaults to an Enabled/Checked value, and it can be changed in the DRW/Field Comment Log section of the Additional Customizations dialog on the Project Setup page. If users prefer for closed and/or verified data queries in the DRW to always be visible in results on the Data Quality page, they can uncheck this new setting in the project. NOTE: Beginning in 14.3.13 through (and including) 14.4.1, a mistake was introduced regarding a change in the behavior of closed/verified data queries, in which they were no longer automatically hidden from Data Quality results (whereas in previous versions they were always hidden). That change was a mistake and thus was a bug, which is now fixed here by reverting the default behavior back to its pre-14.3.13 behavior and also by the addition of this new setting that allows users to have both behaviors (i.e., to either hide or show closed/verified data queries from Data Quality results). The default behavior of this setting is the same as the behavior prior to REDCap 14.3.13. |
14.5.0 | 7/11/2024 | Standard | Improvement | Improvement: The "Help & FAQ" page has been updated with new content (thanks to the FAQ Committee). |
14.5.0 | 7/11/2024 | Standard | Improvement | Improvements to the Online Designer General user interface improvement that utilizes newer icons. New "Go to field" feature (invoked via Ctrl-G or Cmd-G) allows users to search for a variable by name and then navigate directly to its location in the Online Designer, even if the field is on a different instrument than the current one. Improved and expanded "Quick modify field(s)" popup will appear when users Ctrl-click (or Cmd-click) one or more fields or check the new checkboxes located on the far right of each field. Additions to this popup include the ability to edit the following for multiple fields: branching logic, action tags/field annotation, custom alignment, required status, identifier status, and multiple choice options (including the ability to copy choices - with new choice of location for copied fields, import choices from an existing field, convert a field to a different multiple choice field, and also append new choices using a full-blown choice editor). NOTE: When updating actions tags for one or more fields via the "Quick modify field(s)" popup, there is a new action tag named @DEACTIVATED-ACTION-TAGS that is only used in the Online Designer for the purpose of deactivating (and thus possibly reactivating) action tags. The difference between deactivating action tags and removing action tags from fields is that deactivating them leaves the action tags in a state/format so that they can be easily reactivated later, whereas removing action tags would make it very difficult to restore the action tags of many fields having many different action tags. For example, if a field has the @HIDDEN action tag and is then deactivated, its field annotation will then appear as the following: @DEACTIVATED-ACTION-TAGS @.OFF.HIDDEN, and if reactivated, it will go back to @HIDDEN again. The "Quick modify field(s)" popup also includes an additional, large selector popup to allow users to select many fields on the current instrument that match certain criteria by clicking one or more icons (e.g., clicking the slider icon and then clicking the "add new selections" button will automatically select all slider fields on the page to use for the "Quick modify field(s)" popup). This makes it easy to select many fields on the page very quickly when they all match a certain criteria (i.e., field type, field validation). Change: The drag-field feature to "drag-n-drop" a field to a new location on the instrument now operates differently. Inside of clicking and holding anywhere on a field, the user must now click and hold specifically on the Move icon for the given field in order to ready the field for being moved. |
14.5.0 | 7/11/2024 | Standard | Change | Change/improvement: The Configuration Check page now checks to ensure that the MySQL-specific setting "Generated Invisible Primary Key" (GIPK) is disabled. GIPK was introduced in MySQL 8.0.30. If enabled on the MySQL server, a warning will appear on the page telling the admin how to disable it since GIPK is not compatible with REDCap. |
14.5.0 | 7/11/2024 | Standard | Change | Change: In a MyCap-enabled project, if users switch from classic mode (i.e., non-longitudinal) to longitudinal data collection mode or from longitudinal to classic (via the setting at the top of the Project Setup page), the MyCap task settings and Active task formats will no longer be erased in the project when changing that setting. In previous versions, all MyCap task settings and Active task formats would be completely erased in the project when moving to/from longitudinal mode. |
14.5.0 | 7/11/2024 | Standard | Change | Enhanced e-Consent Framework: Audit Trails: Improved, detailed audit trails for consent form completions and PDF snapshot generations. |
14.5.0 | 7/11/2024 | Standard | Change | Enhanced e-Consent Framework: Change/improvement: When a user views a completed/signed e-Consent response on a data entry form, in which a consent form was used on the survey, near the top of the page will be displayed the version of the consent form that was used. Also, the consent form itself (i.e., the inline PDF or rich text) displayed on the page will always be the consent form under which the participant originally consented. For example, if a participant consented using consent form v2.0, then even though a new consent form (v3.0) has been added to the project at some point afterward, the data entry form for that participant's response will always display consent form v2.0 so that the user will always see the survey response and its consent form exactly as the participant originally viewed it. |
14.5.0 | 7/11/2024 | Standard | Change | Enhanced e-Consent Framework: Change/improvement: When reviewing draft mode changes, if a consent form's anchor Descriptive field is deleted or moved to another instrument, it now gets listed as a critical issue in the list of drafted changes. |
14.5.0 | 7/11/2024 | Standard | Change | Enhanced e-Consent Framework: Change/improvement: When using MLM together with the e-Consent Framework, downloading an instrument PDF of a completed e-Consent survey response (or if the e-Consent survey response is included in a generated PDF that contains non-e-Consent instruments), the e-Consent survey response itself in the PDF will always be rendered in the language in which the participant originally consented. |
14.5.0 | 7/11/2024 | Standard | Change | Enhanced e-Consent Framework: Custom Headers and Footers: Add custom headers and footers to PDF snapshots created via the e-Consent Framework, including the use of text fields, smart variables, and piping. |
14.5.0 | 7/11/2024 | Standard | Change | Enhanced e-Consent Framework: Custom Notes: An optional custom notes field can be utilized for each e-Consent survey for bookkeeping purposes. The custom notes are neither displayed on the survey nor anywhere else in the application. |
14.5.0 | 7/11/2024 | Standard | Change | Enhanced e-Consent Framework: Customizable Consent Forms with Version Control: Design consent forms and manage new versions of consent forms while maintaining historical versions for audit purposes. During the setup process for consent forms, their location can be set in relation to a single Descriptive field on the survey. A consent form can exist as an inline PDF or as rich text. A consent form can be associated with a specific MLM language and/or a Data Access Group if the project users wish to have the consent form be used for a specific language (chosen by the participant) and/or DAG (to which the record has been assigned). This allows for language-specific consent forms and DAG-specific consent forms, if needed. |
14.5.0 | 7/11/2024 | Standard | Change | Enhanced e-Consent Framework: File Naming Customization: Customize the file names of PDF snapshots for e-Consent responses using static text or piping, appended with date-time stamps. |
14.4.1 | 7/3/2024 | Standard | Change | Change/improvement: Stats for Mobile Toolbox (MTB) tasks and MyCap tasks created from PROMIS measures were added to the System Statistics page in the Control Center. |
14.4.0 | 6/27/2024 | Standard | New Feature | New feature: Background Data Import option for the API - Similar to using the Background Data Import on the Data Import Tool page, users may now utilize the feature when making a call to the Import Records API method. They can simply pass the API parameter "backgroundProcess" with a value of 1 (for Yes) or 0 (for No, which is the default) to invoke this option. The API will return a "success" message with "true" or "false" regarding if the data was successfully accepted. Note: This option works with any data format: CSV, JSON, or XML. |
14.4.0 | 6/27/2024 | Standard | Improvement | Improvement: "Survey Notifications" and "Survey Confirmation Emails" were added as new filter options to the "Type" drop-down filter on the Email Logging page. Note: This change is not retroactive, meaning that any survey notification emails or confirmation emails that were sent prior to the upgrade to REDCap 14.4.0 will not show up when filtering by these new options but will instead only show up when Type is set to "all types". |
14.4.0 | 6/27/2024 | Standard | Improvement | Improvement: The Email Logging page now has its own separate user privilege. Previously, only users with "User Rights" privileges could access the Email Logging page. Now, users must explicitly be given "Email Logging" privileges in order to access the Email Logging page. Note: During the upgrade to REDCap 14.4.0 or higher, any users with "User Rights" privileges will automatically be given "Email Logging" privileges in order to keep continuity with their current access to the Email Logging page. |
14.4.0 | 6/27/2024 | Standard | Improvement | Improvement: When using Multi-Language Management, the Twilio/Mosio text messaging text ("To begin the survey, visit [link]" and voice call text ("To begin the phone survey, call [phone]" are now available for translation on the MLM setup page. (Ticket #233030) |
14.4.0 | 6/27/2024 | Standard | Change | Change/improvement: The Data Access Group page in a project might be very slow to load in certain circumstances where many records exist in the project. (Ticket #233650) |
14.4.0 | 6/27/2024 | Standard | Change | Change/improvement: The email that administrators receive when a user submits an API token request now contains the user's email address in the email body. Previously, the email body only contained the username and first/last name of the requestor. (Ticket #233507) |
14.4.0 | 6/27/2024 | Standard | Change | Change: The button text was changed from "Cancel import" to "Halt import" for greater clarity for Background Data Imports that are still processing on the Data Import Tool page. |
14.3.13 | 5/30/2024 | Standard | Improvement | Improvement: Ability to import clinical notes via CDIS - Users may now import clinical note documents for patients using Clinical Data Pull or Clinical Data Mart. Note: If using Epic, the institution will be required to upgrade to v4 of the REDCap app in the Epic "Show Room" (formerly known as "App Orchard"). |
14.3.13 | 5/30/2024 | Standard | Improvement | Improvement: For users that are not assigned to a Data Access Group, the Data Quality page will now display a DAG drop-down filter (next to the record drop-down filter) to allow them to apply any Data Quality rule only to records assigned to the selected DAG. |
14.3.13 | 5/30/2024 | Standard | Improvement | Improvement: IP exceptions for the Rate Limiter - On the General Configuration page in the Control Center, you may now set IP address or IP range exceptions for the Rate Limiter (if enabled) so that specific IP addresses will not be banned. This will be useful if performing security scans on your server, in which you can add the IP address of the scanning tool so that it does not get banned while performing scans. (Ticket #119954) |
14.3.13 | 5/30/2024 | Standard | Improvement | Improvement: In the Online Designer when Ctrl-clicking multiple checkbox or radio fields to display the "Modify multiple fields" options, a new option to "Convert to matrix group" will appear, thus allowing users to merge the selected fields into a matrix. When merging fields into a matrix, the confirmation dialog will note that only the choices for the first field selected will be preserved (in case the selected fields have different choices). Additionally, the action will remove all field notes from the fields and will also remove all section headers (except for the first field's section header, if it exists). (Ticket #230591) |
14.3.13 | 5/30/2024 | Standard | Improvement | Improvement: In the Online Designer when editing a matrix of fields, a new button will appear at the bottom left of the "Edit Matrix of Fields" dialog that says "Save & split matrix into separate fields". When clicked, it will convert the matrix into separate fields. (Ticket #230591) |
14.3.13 | 5/30/2024 | Standard | Improvement | Improvement: New "Top Usage Report" page in the Control Center - This page displays the most active projects, users, pages, specific URLs, External Modules, cron jobs, etc. within a given period of time. It can be used to quickly identify where server resources are being spent under periods of high load. |
14.3.13 | 5/30/2024 | Standard | Change | Change: When using the Data Resolution Workflow in a project, it has always been the case that the results of data quality rules would automatically "exclude" fields that have a data query with "closed" status. Many users have complained about this behavior and have stated that the discrepancies should still be displayed in the data quality rule results regardless of the field's data query status. From now on, such fields will no longer be automatically "excluded" simply because they have a data query with "closed" status. |
14.3.12 | 5/23/2024 | Standard | Improvement | Improvement: "Phone (France)" was added as a new field validation. After upgrading, an administrator will need to enable it on the Field Validation Types page in the Control Center. |
14.3.12 | 5/23/2024 | Standard | Improvement | Improvement: "Phone (France)" was added as a new field validation. After upgrading, an administrator will need to enable it on the Field Validation Types page in the Control Center. |
14.3.12 | 5/23/2024 | Standard | Improvement | Improvement: A new system-level setting "Total maximum cron instances" was added, which allows one to control the maximum number of concurrent cron processes for the REDCap cron job. The setting defaults to the value "20". Increasing this value will allow more cron processes to be spawned concurrently, which may be useful if you are using system-intensive External Modules such as API Sync or Flight Tracker. It is generally advised to leave this setting at its default value unless the cron job is either causing server performance issues (because too many jobs are running simultaneously) or if certain cron jobs aren't running often enough to get everything done that they need to get done. |
14.3.12 | 5/23/2024 | Standard | Improvement | Improvement: A new system-level setting "Total maximum cron instances" was added, which allows one to control the maximum number of concurrent cron processes for the REDCap cron job. The setting defaults to the value "20". Increasing this value will allow more cron processes to be spawned concurrently, which may be useful if you are using system-intensive External Modules such as API Sync or Flight Tracker. It is generally advised to leave this setting at its default value unless the cron job is either causing server performance issues (because too many jobs are running simultaneously) or if certain cron jobs aren't running often enough to get everything done that they need to get done. |
14.3.11 | 5/16/2024 | Standard | Improvement | Improvement: Administrators will now see an icon/link in the User Actions popup when clicking a username on a project's User Rights page, in which the icon/link will take the admin to view the user's account on the Browse Users page in the Control Center. (Ticket #230772) |
14.3.11 | 5/16/2024 | Standard | Improvement | Improvement: In a MyCap-enabled project, all MyCap tasks can now be manually set as Active or Not Active at any time on the MyCap settings page in the Online Designer. Setting a MyCap task as "not active" will prevent the task from appearing in the MyCap mobile app for participants. Note: The previous release enabled this feature specifically for MyCap active tasks, while this change makes this feature available to all MyCap tasks (not just active tasks). |
14.3.11 | 5/16/2024 | Standard | Change | Change/improvement: The accuracy of the External Service Checks on the Configuration Check page was improved and are now able to better exclude false positive results. |
14.3.10 |