Version | Release Date | Version Type | Log Type | Descriptions |
14.5. |
...
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.4.0 2024-06-27
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.3.1 2024-03-28
New hook: redcap_project_delete_after - Allows custom actions to be performed after a delete action has been initiated. This allows for close control of the delete operation on a project.
14.3.1 2024-03-28
New hook: redcap_project_save_after - Allows custom actions to be performed after a project has been saved from a newly created, copied, or modified project. This allows for close control of the create, copy, and modify operations on a project.
14.3.0 2024-03-21
New action tags: @MC-PARTICIPANT-JOINDATE-UTC and @MC-PARTICIPANT-TIMEZONE - These action tags will capture the MyCap participant's timezone and also the install date/time (in UTC time) of the MyCap participant whenever the participant joins a project via the MyCap mobile app. NOTE: This is used only for the MyCap mobile app. The fields' values are not generated when viewing the data entry form but only when the MyCap app is making a call to REDCap when the participant joins the project. Additionally, while these action tags can be added to a new field in already-existing MyCap projects, a field with this action tag will be auto-added to any projects where MyCap is enabled in the project after the fact and for any new projects created using the MyCap project template.
14.3.0 2024-03-21
New feature: Custom Query Folders - For improved organization, Custom Queries on the Database Query Tool page can now be organized into folders. Additionally, custom queries can be exported and imported using a CSV file.
14.2.0 2024-02-22
New feature: Account Expiration Email Templates - At the bottom of the User Settings page in the Control Center, administrators may optionally customize the email text of the account expiration emails that are sent to users prior to the users' impending expiration. Two text editors exist on the page, in which admins may define text for users with sponsors and also for users without sponsors. If no custom text is provided, stock text will be utilized in the outgoing emails to users. (Ticket #58767)
14.2.0 2024-02-22
New feature: Project Dashboard Folders - Project Dashboards in a project can now be organized into folders. If a user has Project Setup & Design privileges, they will see an "Organize" link on the left-hand project menu above the Project Dashboards panel. They will be able to create folders and then assign their Project Dashboards to a folder, after which the Project Dashboards will be displayed in collapsible groups on the left-hand menu. (Ticket #137183)
14.1.0 2024-01-04
...
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 | 5/9/2024 | Standard | Improvement | Improvement: In a MyCap-enabled project, active tasks can now be set as Active or Not Active at any time on the MyCap settings page in the Online Designer. Setting an active task as "not active" will prevent the task from appearing in the MyCap mobile app for participants. Note: This is not for all MyCap tasks but only for MyCap active tasks. |
14.3.10 | 5/9/2024 | Standard | Improvement | Improvement: In the Online Designer when viewing the fields of a specific instrument, a yellow star is now displayed to the right of the variable name for identifier fields to denote to users which fields are identifiers. |
14.3.10 | 5/9/2024 | Standard | Improvement | Improvement: When clicking on a user's username in the user table on the User Rights page, in which the user is assigned to a user role, a "Remove from project" button was added inside the "User actions" popup that allows the user to be removed from a project directly without having to un-assign them from the role first. |
14.3.10 | 5/9/2024 | Standard | Change | Change: The text in the help dialog for the option "Rename records?" on the Data Import Tool has been changed slightly for improved clarity and to reduce confusion. (Ticket #228096b) |
14.3.9 | 5/3/2024 | Standard | Change | Change: The text for the option "Rename records?" on the Data Import Tool has been changed slightly for improved clarity and to reduce confusion. (Ticket #228096) |
14.3.8 | 5/2/2024 | Standard | Improvement | Improvement: Mobile Toolbox measures have been added for use in the MyCap mobile app. The Mobile Toolbox (MTB) is a research platform that includes a library of cognitive and other tests that can be administered remotely on a smartphone. The MTB's measures include smartphone versions of assessments from the NIH Toolbox, the International Cognitive Ability Resource, and the Patient Reported Outcomes Measurement Information System. A list of all available MTB tasks in REDCap can be viewed via the "Import Active Task" button in the Online Designer for any MyCap-enabled project. |
14.3.8 | 5/2/2024 | Standard | Improvement | Improvement: New "Download SQL" button was added to the REDCap install page to make it easier to fetch the generated install SQL as a file rather than obtaining it from the webpage via copy-and-pasting. (Ticket #229260) |
14.3.8 | 5/2/2024 | Standard | Improvement | Improvement: The Codebook page now has checkboxes that can be toggled by the user to remember the collapsed state of the tables on the page on a per-project basis for the user. (Ticket #229673) |
14.3.8 | 5/2/2024 | Standard | Change | Change: Small changes to the redcap_log_view_requests database table to improve general application performance. |
14.3.7 | 4/29/2024 | Standard | Change | Change: The video "Full Project Build" was added as a new video on the project left-hand menu and on the Training Videos page. |
14.3.5 | 4/25/2024 | Standard | Improvement | Improvement: The Database Query Tool in the Control Center now has the ability to utilize "Smart Variables Context", which can be enabled on the page via checkbox option on the DQT menu so that administrators may provide the literal values of certain Smart Variables that can be piped into the query from text boxes on the page. Also, a link or button to navigate directly to the Database Query Tool has been added to several project pages, such data entry forms, survey pages, the Edit Field dialog in the Online Designer, etc. to allow admins to open the DQT directly with the current context values (e.g., project-id, record-name, event-id) already pre-filled on the page. This will make it much, much easier to execute queries on a specific project and/or record with less copy-and-pasting. Note: This feature will not be displayed if the DQT has not been enabled yet. |
14.3.5 | 4/25/2024 | Standard | Improvement | Improvement: The rich text editor used throughout REDCap now has a new drop-down option in the editor's toolbar for setting the "font family" and "font size" of any text in the editor. |
14.3.5 | 4/25/2024 | Standard | Improvement | Improvement: When using MyCap in a longitudinal project, users can now decide on the event display format (ID, Label, or None) for titles of MyCap tasks displayed in the Upcoming Tasks section. |
14.3.5 | 4/25/2024 | Standard | Change | Change/improvement: A few more pages were added to the "Navigate to page" widget to allow users to go to specific pages via PID and keyboard shortcuts. |
14.3.5 | 4/25/2024 | Standard | Change | Change: The video "A Brief Overview of REDCap" was replaced with a new video. |
14.3.5 | 4/25/2024 | Standard | Change | Various changes/improvements to the External Module Framework, including 1) Allow external module ajax requests to work on dashboards & reports, 2) Added an instance parameter to the resetSurveyAndGetCodes() method, 3) Improve performance of the disabled modules dialog, and 4) Misc. security scan script improvements. |
14.0.21 | 4/18/2024 | Long Term Support (LTS) | Change | Change: All hard-coded references to "redcap.vanderbilt.edu" have been changed to "redcap.vumc.org" to reflect the recent change of the Vanderbilt REDCap server's domain name. Note: The old URL will continue to work and automatically redirect to the new URL until April 2025. |
14.3.4 | 4/18/2024 | Standard | Improvement | Improvement: New built-in PDF Viewer | This built-in PDF viewer remediates an old gap of functionality in which iOS and Android devices are not able to display more than the first page of an inline PDF. So whenever REDCap is displaying an inline PDF (e.g., for a Descriptive field, when using the INLINE action tag on a File Upload field, or on the e-Consent certification page), if the current device is iOS or Android or if it lacks a native PDF viewer, then REDCap's built-in PDF Viewer will be utilized automatically. For all other devices, the device's native PDF viewer will be used. | Notable change: Previous versions of REDCap would not attempt to display an inline PDF on the certification page of an e-Consent survey, in which it would say "This browser does not support inline PDFs. Please open the PDF in a new tab.". But now, it will actually display the inline PDF for all devices on the e-Consent certification page, whether using the device's native PDF viewer or if using REDCap's PDF viewer. |
14.3.4 | 4/18/2024 | Standard | Improvement | Improvement: The "Help & FAQ" page has been updated with new content (thanks to the FAQ Committee). |
14.3.4 | 4/18/2024 | Standard | Improvement | Improvement: Videos hosted by the VidYard video service (http://vidyard.com ) can now be utilized for the "Embed media" option on Descriptive Text fields. Thus, VidYard URLs (e.g., https://share.vidyard.com/watch/XYZXYZ) are now fully compatible, similar to how YouTube and Vimeo URLs have always been. |
14.3.4 | 4/18/2024 | Standard | Improvement | Improvement: When moving one or more fields in the Online Designer, a new option will appear in the field selection drop-down to allow the user to move a field to an empty instrument (i.e., an instrument with no defined fields). In previous versions, fields could only be moved to an instrument containing at least one field (not counting the Form Status field). |
14.3.4 | 4/18/2024 | Standard | Change | Change: All hard-coded references to "redcap.vanderbilt.edu" have been changed to "redcap.vumc.org" to reflect the recent change of the Vanderbilt REDCap server's domain name. Note: The old URL will continue to work and automatically redirect to the new URL until April 2025. |
14.3.4 | 4/18/2024 | Standard | Change | Change: New MLM tip added at the bottom of the "Forms/Surveys" tab on the MLM setup page. The tip reads as follows: "Tip: Choose your "ASI Language Source" wisely - If ASIs have been translated in your MLM setup, it is typically recommended that you utilize the "Language preference field" option for determining the translation to be used for an ASI survey invitation. Choosing "User's or survey respondent's active language" as the ASI Language Source can have unexpected results. For example, if a participant's survey response triggers the ASI, the ASI's invitation text will be output in the correct language since it uses what the participant has chosen previously. However, if the ASI is triggered by an action of the project user, such as a data import or saving a data entry form, the ASI's text will be in the language of the project user, which may not be the language that the participant prefers." |
14.3.4 | 4/18/2024 | Standard | Change | Change: When copying a project via the Other Functionality page, a new note appears below the copy project option that says "NOTE: The new project will not contain the project's logging history (audit trail), but if you wish to obtain it, you may freely download it any time at the top of the Logging page.". This will help users understand upfront that the logging does not get copied during this process. (Ticket #228253) |
14.3.4 | 4/18/2024 | Standard | Change | Various fixes and changes to the External Module Framework, including the following: 1) Made it possible to download a list of users that have Project Design rights for all projects where a given module is enabled (appears as a new button in the View Usage dialog in the Control Center), 2) Queued all External Module AJAX requests to prevent them from getting canceled by REDCap's duplicate query protection, and 3) Miscellaneous security scan improvements. |
14.3.3 | 4/11/2024 | Standard | Change | Change: When editing a MyCap task's settings in the Online Designer, if a task is scheduled one time then the "allow retroactive" option will now not be available. |
14.3.3 | 4/11/2024 | Standard | Change | Improvement/change: When uploading static attachment files to an alert on the Alerts & Notifications page, the maximum allowed attachment size has been increased from 10 MB to 20 MB. Please note that sending attachments larger than 10 MB might cause the email to be rejected by certain email providers. |
14.3.2 | 4/4/2024 | Standard | Improvement | Improvement: When moving one or more fields in the Online Designer, a new option will appear at the end of the field selection drop-down to allow the user to auto-create an instrument while moving the field(s) to that new instrument. Note: The new instrument will be named "New Instrument" by default, although the user can always rename it after the fact. (Ticket #227034) |
14.3.2 | 4/4/2024 | Standard | Change | Various updates and fixes to the External Module Framework, including 1) Added validation button and use of Logic Editor for JSON settings, and 2) Miscellaneous security scan script improvements. |
14.3.1 | 3/28/2024 | Standard | New Feature | New hook: redcap_project_delete_after - Allows custom actions to be performed after a delete action has been initiated. This allows for close control of the delete operation on a project. |
14.3.1 | 3/28/2024 | Standard | New Feature | New hook: redcap_project_save_after - Allows custom actions to be performed after a project has been saved from a newly created, copied, or modified project. This allows for close control of the create, copy, and modify operations on a project. |
14.3.1 | 3/28/2024 | Standard | Improvement | Improvement: MyCap now supports repeating instrument functionality for longitudinal projects. In previous versions, repeating instruments were only supported for class/non-longitudinal projects. |
14.3.0 | 3/21/2024 | Standard | New Feature | New action tags: @MC-PARTICIPANT-JOINDATE-UTC and @MC-PARTICIPANT-TIMEZONE - These action tags will capture the MyCap participant's timezone and also the install date/time (in UTC time) of the MyCap participant whenever the participant joins a project via the MyCap mobile app. NOTE: This is used only for the MyCap mobile app. The fields' values are not generated when viewing the data entry form but only when the MyCap app is making a call to REDCap when the participant joins the project. Additionally, while these action tags can be added to a new field in already-existing MyCap projects, a field with this action tag will be auto-added to any projects where MyCap is enabled in the project after the fact and for any new projects created using the MyCap project template. |
14.3.0 | 3/21/2024 | Standard | New Feature | New feature: Custom Query Folders - For improved organization, Custom Queries on the Database Query Tool page can now be organized into folders. Additionally, custom queries can be exported and imported using a CSV file. |
14.3.0 | 3/21/2024 | Standard | Improvement | Improvement: API examples in C Sharp (C#) code were added to the API Playground. |
14.3.0 | 3/21/2024 | Standard | Improvement | Improvement: In the Online Designer, the variable name for each field on the page is clickable, and when clicked, will copy the variable name to the user's clipboard. |
14.3.0 | 3/21/2024 | Standard | Improvement | Improvement: In the Online Designer, when a user attempts to click into the variable name field in the Edit Field popup while the project is in production, the dialog that notes that the variable name is not editable when in production will now also display the variable name as clickable in the dialog's text, and when clicked, will copy the variable name to the user's clipboard. |
14.3.0 | 3/21/2024 | Standard | Improvement | Improvement: In the Online Designer, when a user clicks on the green button "Field is embedded elsewhere on this page" on an embedded field in the table, the page will scroll up to where the field is embedded and flash a red border around the container field. This will make it easier for users to find where a field is embedded. |
14.3.0 | 3/21/2024 | Standard | Improvement | Improvement: When viewing a user on the Browse Users page in the Control Center, it now lists a new row "Number of users of which user is a sponsor" in the table. It will list how many sponsees the user has and also a link to open a dialog that will list the username and first/last name of all their sponsees. (Ticket #225819) |
14.2.2 | 3/7/2024 | Standard | Improvement | Improvement: The Custom Event Label, if being used in a longitudinal project, will now display at the top of the data entry form in the yellow event bar. In previous versions, it only appeared above each event column on the Record Home Page. Now it appears in both places. |
14.2.2 | 3/7/2024 | Standard | Improvement | Improvement: Users may now use "now" or "today" (wrapped in quotes) instead of a field variable in the special functions day(), month(), and year() in order to capture a specific date component of today's date. |
14.2.2 | 3/7/2024 | Standard | Change | Change: The Configuration Check page will no longer display a warning if any REDCap database tables have "compressed" row_format. REDCap now allows both "compressed" and "dynamic" as the row_format. (Ticket #224878) |
14.0.14 | 2/29/2024 | Long Term Support (LTS) | Change | Bug fix/change: The "Azure AD" authentication is now referred to as "Microsoft Entra ID (formerly Azure AD)" in the REDCap user interface due to the fact that Microsoft renamed the product to "Microsoft Entra ID" at the end of 2023. |
14.2.1 | 2/29/2024 | Standard | Change | Bug fix/change: The "Azure AD" authentication is now referred to as "Microsoft Entra ID (formerly Azure AD)" in the REDCap user interface due to the fact that Microsoft renamed the product to "Microsoft Entra ID" at the end of 2023. |
14.2.0 | 2/22/2024 | Standard | New Feature | New feature: Account Expiration Email Templates - At the bottom of the User Settings page in the Control Center, administrators may optionally customize the email text of the account expiration emails that are sent to users prior to the users' impending expiration. Two text editors exist on the page, in which admins may define text for users with sponsors and also for users without sponsors. If no custom text is provided, stock text will be utilized in the outgoing emails to users. (Ticket #58767) |
14.2.0 | 2/22/2024 | Standard | New Feature | New feature: Project Dashboard Folders - Project Dashboards in a project can now be organized into folders. If a user has Project Setup & Design privileges, they will see an "Organize" link on the left-hand project menu above the Project Dashboards panel. They will be able to create folders and then assign their Project Dashboards to a folder, after which the Project Dashboards will be displayed in collapsible groups on the left-hand menu. (Ticket #137183) |
14.2.0 | 2/22/2024 | Standard | Improvement | Improvement: If using CDIS, new data fields "Legal Sex" and "Sex for Clinical Use" can now be mapped for Clinical Data Pull projects and also will be included in Clinical Data Mart projects. Note: Currently, only Epic is providing data for these fields, but other EHR systems will likely add them too in the near future. |
14.2.0 | 2/22/2024 | Standard | Improvement | Improvement: New "Test Run" option when re-evaluating Alerts and Automated Survey Invitations - When performing the "Re-evaluate" feature for Alerts and ASIs, a new toggle that says "Enable Test Run?" can be clicked in the dialog, which will perform a test run (dry run) to simulate what would have happened (e.g., schedule or send alerts/invitations) but without actually doing anything. This will allow users to feel more confident if they actually need to perform a real re-evaluation of Alerts or ASIs so that they know beforehand how many records will be affected during the re-evaluation. In addition, users may download a CSV file of all affected record names afterward, whether using the test run option or not. |
14.2.0 | 2/22/2024 | Standard | Improvement | Improvement: The "Help & FAQ" page has been updated with new content (thanks to the FAQ Committee). |
14.2.0 | 2/22/2024 | Standard | Improvement | Improvement: The Project Home Page now contains an icon in the Current Users table to allow users to download the current user list as a CSV file. |
14.1.6 | 2/15/2024 | Standard | Improvement | Improvement: The "Help & FAQ" page has been updated with new content (thanks to the FAQ Committee). |
14.1.6 | 2/15/2024 | Standard | Improvement | Improvement: The "Help & FAQ" page has been updated with new content (thanks to the FAQ Committee). |
14.1.6 | 2/15/2024 | Standard | Change | Change/improvement: All logged events concerning Alerts & Notifications will now additionally display the alert's Unique Alert ID in order to make it easier to discern alerts from each other if alerts are reordered or moved after being created (i.e., if their alert number changes over time). (Ticket #222857) |
14.1.6 | 2/15/2024 | Standard | Change | Change: The "Email Alerts" converter that migrates alerts from the Email Alerts external module to alerts in "Alerts & Notifications" has been officially removed. This feature was technically removed four years ago, but there still existed an Easter Egg in the redcap_config database table that would allow it to be used during emergency situations. |
14.1.6 | 2/15/2024 | Standard | Change | Several bug fixes for the External Module Framework. |
14.1.5 | 2/8/2024 | Standard | Improvement | Improvement: Administrators are now able to view survey pages even when the system or a project is in "offline" status. Note: The admin must have logged into REDCap (i.e., they have a session cookie) before the system/project was taken offline in order to access a survey page. (Ticket #223524) |
14.1.5 | 2/8/2024 | Standard | Improvement | Improvement: Enhanced settings for importing email addresses from EHRs via Clinical Data Interoperability Services (CDIS) - Previous versions of REDCap had a CDIS feature to allow or disallow projects from importing the email addresses of patients from the EHR, in which it was either completely disallowed or an admin could enable the feature on an individual project via the Edit Project Settings page. The new features provide more options so that it can be 1) disabled for all projects, 2) enabled for all projects, or 3) allow individual projects to decide (via the admin-only setting on the Edit Project Settings page). (Ticket #223068) |
14.1.5 | 2/8/2024 | Standard | Improvement | Improvement: When using CDIS in a project, a new status indicator for FHIR access tokens will appear underneath each user in the Current Users table on the Project Home page. This feature helps team members and admins quickly see who needs to update their access token, essential for CDIS background fetch processes. |
14.1.5 | 2/8/2024 | Standard | Change | Various updates to the External Module Framework, including adding the "redcap_module_api_before" hook and miscellaneous security scan improvements. |
14.1.3 | 1/25/2024 | Standard | Change | Various updates and fixes for the External Modules Framework, including 1) Fixed a module setting race condition when using a "Read Replica" database server, and 2) Displayed logged parameters on the View Logs page for External Modules. |
14.1.2 | 1/18/2024 | Standard | Change | Change: The "Copy Project" page now contains more informational text when copying a project containing surveys. The new text explains that when copying all records, the survey completion time for any survey responses will not be copied with the normal project data because the completion times are considered to be equivalent to project logging, which never gets copied during this process. (Ticket #222256) |
14.1.2 | 1/18/2024 | Standard | Change | Various changes and fixes for the External Modules Framework, including fixing a bug that was preventing link editing in rich text module settings caused by a conflict between Bootstrap dialogs and TinyMCE. |
14.1.1 | 1/11/2024 | Standard | Improvement | Improvement: If a user has a sponsor, their sponsor's username, name, and email will be listed at the top of their Profile page. (Ticket #138684) |
14.1.0 | 1/4/2024 | Standard | New Feature | New Multi-EHR functionality for Clinical Data Interoperability Services (CDIS)- Multiple electronic health record systems (EHRs) can now be defined on the CDIS page in the Control Center, whereas in previous versions only one could be defined. This will allow users to pull clinical data from many different EHR systems, if they desire. After a REDCap administrator has defined one or more EHR systems on the CDIS page, any given REDCap project can utilize a specific EHR connection. Note: A project can only be connected to one single EHR. The first EHR connection will serve as the default, and thus whenever CDP or Data Mart is enabled in a project, it will initially point to the default connection, but this can be changed after the fact to point to one of the other EHR connections that are defined in the Control Center. As previously, all users attempting to pull data from any EHR connection will need to have signed in through the EHR (either using the Standalone Launch or CDPs EHR Launch) in order to obtain a FHIR access token for that specific EHR. Thus the user must still have a valid account for each EHR from which they are attempting to pull data. |
14.1.0 | 1/4/2024 | Standard | Improvement | Improvement: Performance improvement when using iMagick (i.e., rendering PDF attachments for Descriptive fields as images embedded inside REDCap-generated PDFs) by using a new internal image cache. Whenever a PDF attachment for a Descriptive field is rendered as an image via iMagick, the image of each PDF page will be cached and stored separately so that the next time the PDF attachment is being rendered inside a PDF, it will use the cached image(s) rather than perform a real-time conversion of the PDF to images every time, which can be time consuming. Note: The image cache of the PDF attachment will be stored and used for up to 30 days, after which it will be automatically deleted from the system. |
14.1.0 | 1/4/2024 | Standard | Improvement | Improvement: New Read Only user privilege for the User Rights page- Users and roles can now be given Read Only access to the User Rights page, which will allow users to view the page but not be able to take any actions on the page. Note: If a user is in a Data Access Group while viewing the page, it is still the case that they can only view users from their own DAG on the page. |
14.1.0 | 1/4/2024 | Standard | Change | Change/improvement: A notice was added on the Database Query Tool page so that when exactly 500 rows are returned from a query that does not contain a "limit" clause, it notes that more rows might exist that are not being displayed on the page. This is because "limit 0,500" is always appended to any query that lacks a "limit" clause. This will reduce confusion for admins who might assume that they are viewing the full results of a query when they might not be. |
14.0.4 | 12/28/2023 | Standard | Change | Change/improvement: When using the eConsent Framework on a survey, the certification page now says "Working..." until the inline PDF finally loads on the page. This will reduce confusion for participants in case the PDF takes an abnormal time to load. (Ticket #221228) |
14.0.5 | 12/28/2023 | Long Term Support (LTS) | New Feature | New LTS branch based off of REDCap 14.0.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. |