Content Comparison

...

Version	Release Date	Version Type	Log type	Description
15.0.8	2025-01-30	Standard	Change	Change: Support has been dropped for PHP 7 - The minimum required PHP version is now PHP 8.0.2. All major versions of PHP 8 (i.e., 8.0 through 8.4) are supported.
15.0.9	2025-01-30	Long Term Support (LTS)	Change	New LTS branch based off of REDCap 15.0.8 (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.
15.0.6	2025-01-26	Standard	Change	Change: If Easy Upgrade is enabled/available in REDCap, the top of the main Control Center page will now always display a "Check again" link to check for new REDCap versions. This will allow REDCap admins to always be able to check for new REDCap versions that have recently become available.
15.0.6	2025-01-26	Standard	Change	Change: The "Choose action for record" menu on the Record Home Page now always displays the "Survey Queue" option for a given record, even if the record's queue currently contains no items. In previous versions, the option would only be displayed if the record's queue contained one or more items. Additionally, the "Survey Queue" option in the drop-down now has a sub-option to allow the user to copy the survey queue link to their clipboard.
15.0.3	2025-01-23	Standard	Improvement	Improvement: In a MyCap-enabled project, the "Messages" tab on the "MyCap Participant Management" page now allows users to use a rich text editor when composing messages and announcements sent to MyCap participants. This allows limited text formatting/styling and clickable links to be used in the messages/announcements.
15.0.3	2025-01-23	Standard	Improvement	Improvement: The "Choose action for record" drop-down list on the Record Home Page now lists links to the Logging page, Notification Log, and Survey Invitation Log (if the user has privileges to those pages), in which the current record will already be preselected when navigating to those pages. This improvement serves as the integration of Luke Stevens' "Record Logging Links" External Module. (Ticket #247752b)
15.0.3	2025-01-23	Standard	Improvement	Improvement: When AI Services are enabled, specifically the Writing Tools feature, the magic wand icon for the AI Writing Tools now appears in the rich text editor for Notes fields with the RICHTEXT action tag when on data entry forms. Note: This does not appear for the same fields on survey pages but only for authenticated users on data entry forms.
15.0.3	2025-01-23	Standard	Improvement	Improvement: When the Survey Queue is enabled in a project and a record contains one or more uncompleted items in its queue, an option to open the Survey Queue page for the record will now appear in the "Choose action for record" drop-down list on the Record Home Page. (Ticket #247752)
15.0.3	2025-01-23	Standard	Improvement	Improvements to the Codebook page: Form names in the Instruments table are now internal links to the corresponding form in the fields table to allow users to move to that form quickly on the Codebook page. Forms have a new Edit icon next to the form name leading to the field-edit view of the Online Designer. The "Return to Codebook" button on the Online Designer now leads back to the form/field (instead of just to the top)
15.0.3	2025-01-23	Standard	Change	Change/improvement: In a MyCap-enabled project, the Online Designer now displays the version (i.e., "English" or "Spanish") in the instrument label of MTB Active Tasks on the instrument-level view.
15.0.1	2025-01-16	Standard	Improvement	Improvement: REDCap now supports the "blockquote" HTML tag so that it may be utilized in user input (e.g., field labels, survey instructions). (Ticket #247361)
15.0.1	2025-01-16	Standard	Improvement	Improvement: The MLM setup page now shows hints that choice labels are fixed for true/false and yes/no fields and thus cannot be translated on a per-field basis. (Ticket #246312)
15.0.1	2025-01-16	Standard	Improvement	Improvement: The user interface of the "Data Dictionary" page in a project has been simplified and improved to help users better understand the general process of editing and uploading a data dictionary. Additionally, buttons have replaced the links for downloading the data dictionary for improved web accessibility and for a better user experience. (Ticket #246206)
15.0.1	2025-01-16	Standard	Improvement	Improvement: When using Multi-Language Management, it is now possible to preset the language for a participant's Survey Queue by supplying the URL parameter "__lang", which must be set to a valid (active) language id (and is case-sensitive). Example: [survey-queue-url]&__lang=es or https://redcap.vanderbilt.edu/surveys/?sq=ABC123&__lang=es. (Ticket #247173)
15.0.1	2025-01-16	Standard	Change	Change/improvement: When a user is opening a data query in the Data Resolution Workflow and is assigning the query to a user, if the project contains Data Access Groups and is also using the DAG Switcher, users that can access the current record due to DAG Switching (but are not currently assigned to the record's DAG) will be displayed in the user assignment drop-down for assigning the data query. In previous versions, the user assignment drop-down would only display the users that were currently in the record's DAG and did not respect possible DAG Switcher assignments. (Ticket #246453)
15.0.1	2025-01-16	Standard	Change	Change: Slightly modified the styling of the buttons on the randomization model setup page to make the individual steps more distinct.
15.0.1	2025-01-16	Standard	Change	Change: When AI data summarization feature for reports is enabled for a project, the "Summarize Data" button displayed on a given report will no longer be visible when there are no fields from the report available to summarize data (i.e., there are no unvalidated Text fields or Notes fields).
15.0.0	2025-01-09	Standard	New Feature	New features: Implementation of Artificial Intelligence (AI) Background: REDCap can use Artificial Intelligence (AI) to help users perform certain tasks in the application that augment existing REDCap features. These features are implemented by connecting to an AI service that is served over a private endpoint on an virtual network that your institution controls, thereby ensuring the highest level of security and privacy. Enabling AI Services: In order to use the new AI services, a REDCap admin must first enable them on the "Modules & Services Configuration" page in the Control Center. REDCap's AI services currently only use the Microsoft Azure OpenAI deployment of ChatGPT. However, the REDCap development team plans to make more AI deployment options available for use in the future, such as ChatGPT deployments on other cloud hosting services and/or other AI products. You will find instructions here (https://learn.microsoft.com/en-us/azure/ai-services/openai/how-to/create-resource?pivots=web-portal ) regarding how to set up and deploy an isolated instance of ChatGPT in Microsoft Azure, or alternatively you may do a web search for "Create and deploy an Azure OpenAI Service resource" to find the instructions. Financial Notice: Since the AI-based features in REDCap utilize a third-party service, these services are not free to use. As such, as the AI services are used by the application, funds will be deducted from your cloud account (i.e., Azure). It is up to your institution to set up your cloud account, get your API keys, manage your funds, etc. Project-level Override: The AI service configuration values (e.g., endpoint URL, API key) may be overridden by project-level values by an admin on the "Edit Project Settings" page for a given project. If you do not want to enable AI services globally but only on certain projects, you may leave the fields in the "Modules & Services Configuration" page blank and then enter values for the AI configuration fields on the "Edit Project Settings" page for a given project. NOTE: By default, the AI services enabled at the system level will be enabled on all projects. Overview of the AI Services: This release comes with three (3) different AI-based services, which are described in detail below. Please note that each service can be enabled/disabled independently. Service 1: "Writing Tools" feature in the rich text editor to enhance text - A magic wand icon will appear in the toolbar of all rich text editors throughout REDCap (with the exception of the RICHTEXT action tag) and will allow users to alter and enhance text in the rich text editor, including changing the length, tone, reading level of the text, etc. Service 2: Summarize free-form text data on reports - A magic wand icon will appear next to free-form text fields displayed on reports in REDCap projects to allow users to have the fields' text values be summarized by the AI service. The user will click a "Summarize" button, after which the service will return a summary of the text and its major concepts based on the action text (i.e. chatp prompt) provided by the user.. Service 3: Auto-translate text on the MLM setup page - When using Multi-Language Management (MLM) in a project or in the Control Center, a button will appear on the page that (when clicked) will auto-translate all untranslated text on the page. This will more rapidly allow users to utilize MLM in their projects since they will not need to perform translations of the text manually.
15.0.0	2025-01-09	Standard	Improvement	Improvement: Custom text option for Create New Project page - Admins may now provide custom text to display at the top of the Create New Project page, if desired. This allows for the opportunity to display important information to users before they create (or request creation of) a new project. This custom text can be set in a rich text editor near the bottom of the General Configuration page in the Control Center.
15.0.0	2025-01-09	Standard	Improvement	Improvement: To boost performance, Rapid Retrieval caching was added to the Participant List page, Participant List CSV export, and the API Export Participant List method.
15.0.0	2025-01-09	Standard	Change	Change/improvement: The logging mechanism for Break the Glass actions in CDIS projects has been improved. Logs now include detailed information not only for successful operations but also for scenarios where the action cannot be performed, such as when Break the Glass is deemed unnecessary or when an error occurs.
15.0.0	2025-01-09	Standard	Change	Change: Added more description to the MyCap Configuration Check page in the Control Center if the "Communication to MyCap Central" test fails.
15.0.0	2025-01-09	Standard	Change	Change: In the MyCap settings in the Online Designer, the "Modify Project Title" button was moved down to the "About" section.
14.9.5	2025-01-02	Standard	Improvement	Improvement/change: The user list table on the Project Home page now displays "EHR Access" in its own column in CDIS projects, separate from the user information. The table style was also slightly tweaked to enhance responsiveness, making the interface cleaner and more user-friendly across devices.
14.9.5	2025-01-02	Standard	Improvement	Improvement: The "Help & FAQ" page has been updated with new content (thanks to the FAQ Committee).
14.9.5	2025-01-02	Standard	Change	Change/improvement: All rich text editors now utilize the browser's native spell check functionality by putting a red underline under a misspelled word. (Ticket #246649)
14.9.5	2025-01-02	Standard	Change	Change: Text and phrases on certain MyCap-related pages were abstracted to allow for translation.
14.9.3	2024-12-19	Standard	Improvement	Improvement: A new FHIR Statistics page has been added to the Control Center to allow admins to view counts and visualize the EHR data being imported into REDCap via CDIS. There are date-range controls to filter the data by a min/max date, and an export option also exists on the page for exporting the counts. Note: Due to issues with the stats collection not being accurate in previous versions, REDCap will unfortunately be starting with a blank slate stats-wise with this version. For more details, see the FHIR stats-related bug listed below.
14.9.3	2024-12-19	Standard	Improvement	Improvement: When a REDCap administrator is in a project uploading a data dictionary that contains Dynamic SQL fields, the page now displays the following warning to provide more info and transparency when a SQL field is being added or modified: "Allowable warnings found in your Data Dictionary: An 'sql' field is being modified or added in this project. Please confirm that this is acceptable." (Ticket #246357)
14.9.3	2024-12-19	Standard	Improvement	Improvement: When using MyCap together with MLM, the MyCap language codes are now more flexible when adding a language on the MLM setup page. For example, if the language code is "en", "en-US", or "en-UK" on the MLM page, the MyCap mobile app will recognize any of those generally as "English".
14.9.2	2024-12-12	Standard	Improvement	Improvement: Allow for multiple IdPs for Shibboleth authentication - This allows multiple Shibboleth Login Options to be configured on the Security & Authentication page in the Control Center when using Shibboleth authentication. Previously, this was only possible when using Shibboleth+Table-based authentication. If no Login Option is defined, then authentication functions as normal for Shibboleth. However, if at least one Login Option is defined, then authentication functions much more like Shibboleth+Table-based authentication. Specifically, users will be presented with a login screen identical with the Shibboleth+Table screen except that there is no option for local REDCap login.
14.9.2	2024-12-12	Standard	Improvement	Improvement: Public project dashboard links can now be turned into QR codes. If a public link is created for a project dashboard (including custom/short links), a button next to the public URL on the Edit Project Dashboard view will appear that (when clicked) will display the QR code representing the dashboard link. The QR code image can also be downloaded in SVG format or copied to the user's clipboard.
14.9.2	2024-12-12	Standard	Change	Change/improvement: The "View modules available in the REDCap Repo" button in the External Modules Module Manager in the Control Center now opens the REDCap Repo website in a new tab, whereas in previous versions it opened in the same tab. (Ticket #245904)
14.9.2	2024-12-12	Standard	Change	Change/improvement: When using MyCap in a project, a new UI improvement has been made for making the 'enable/disable for event' buttons more noticeable on the MyCap Task setup page for longitudinal projects.
14.9.0	2024-12-05	Standard	New Feature	New feature: Organize stored files into subfolders by project (for "Local" storage only) This is an optional feature that allows files for a given project to be stored in a subdirectory named "pidXXXX", in which XXXX is the PID of the project, rather than storing the files associated with that project in the main local storage directory on the web server. This feature can aid in the organization of files if IT/server admins are not happy with there being thousands or millions of files stored in the main storage directory. Once enabled, this setting will be applied to new projects that are created after the fact. This setting will not apply to any existing projects that were created before this setting was enabled. This feature can be enabled near the top of the File Upload Settings page in the Control Center. When upgrading, this setting will be disabled by default, although it will be enabled by default when performing a fresh install of REDCap. This feature is only applicable for REDCap installations that are using "Local" file storage or "Google Cloud Storage (for Google App Engine hosting only)". When enabled, if REDCap is unable (due to a directory permissions issue, etc.) to create a project-level subfolder when a new project is created, it will instead default to storing all project files in the main Local File Storage directory (specified above) for that project.
14.9.0	2024-12-05	Standard	Improvement	Improvement/change: Added 8 new MTB measures for use in MyCap-enabled projects: Spanish versions of Arranging Pictures, Arrows, FNAME Learning, FNAME Test, Number Match, Sequences, Shape-Color Sorting, Word Meaning Form 1.
14.9.0	2024-12-05	Standard	Improvement	Improvement: The PDF Snapshot Archive page in the File Repository now contains a new button to allow users to download the PDF Archive's file list as a CSV file. (Ticket #245337)
14.9.0	2024-12-05	Standard	Improvement	Improvement: When a project is created from a Project XML file, additional info about the file (source system REDCap version and the XML file's creation date) is displayed on the page, or a warning message is displayed if the XML file appears not to be a proper REDCap Project XML file. (Ticket #245469)
14.9.0	2024-12-05	Standard	Improvement	Minor security improvement: The SameSite attribute for cookies utilized by REDCap now defaults to the value "Strict", which provides more security by preventing cookie information leakage to first-party or same-site context. In previous versions, the default value for the SameSite attribute was "Lax".
14.9.0	2024-12-05	Standard	Change	Change: A cookie policy was added that specifies the details of how cookies are utilized by a person's web browser when using REDCap. A link to the policy exists at the bottom of every webpage in REDCap.
14.9.0	2024-12-05	Standard	Change	Change: When an admin clicks the "Compose confirmation email" button to send an email to the user via the Project Modifications Review page for Draft Mode, the logged event description (i.e., "Send email to user from admin") now includes the recipient's email address so that their email appears in the project logging to provide more context.
14.9.0	2024-12-05	Standard	Change	Various changes for the External Module Framework, including 1) Relaxed tag vs. release zip comparison during security scans, 2) EM Logs table within the project context will now properly maintain PID context (this prevents it from navigating away to the Control Center when trying to use search parameters), 3) Added 'Record' and 'UserName' columns to the report table of EM logs, 4) Included the framework's twig dependency when checking for composer conflicts, and 5) Misc. minor changes.
14.8.3	2024-11-26	Standard	Improvement	Improvement: When creating an alert in a longitudinal project, users can now select an email field from the current event where the alert is triggered to be used as the "Email To" setting for the alert. This allows for flexibility when using different email addresses on each event in the project. In previous versions, email fields in specific events only could be selected.
14.8.3	2024-11-26	Standard	Improvement	Minor security improvement: The HTTP header "Referrer-Policy: strict-origin-when-cross-origin" was added to prevent the leakage of referrer information when navigating to external websites from REDCap.
14.8.3	2024-11-26	Standard	Change	Change/improvement: Allow multiple PHP errors to be logged in the "redcap_error_log" database table for a single request (i.e., single log_view_id).
14.8.3	2024-11-26	Standard	Change	Change: REDCap is now officially compatible with PHP 8.4. Note: It was noted in a previous release that REDCap 14.7.4 and higher was compatible with PHP 8.4, but that was incorrect. Only REDCap 14.8.3 and higher are compatible with PHP 8.4. Additionally, the current recommended PHP versions for REDCap are PHP 8.1, 8.2, 8.3, and 8.4. Note: REDCap is currently compatible with PHP version 7.3.0 and all later versions (including PHP 8.4.X).
14.8.1	2024-11-20	Standard	Improvement	Minor security improvement: A couple different project pages might mistakenly allow knowledgeable malicious users to email any recipient as many times as they wish (i.e., spam any email address), although the email itself would still have to come "From" one of the user's email addresses as listed in their REDCap user profile. Exploiting this feature is no longer possible.
14.8.1	2024-11-20	Standard	Change	Change/improvement: When using the Data Resolution Workflow, the "assign user" drop-down list in the DRW dialog is now displayed as an auto-complete drop-down to help users more easily select a user from the list in projects that have a large number of users.
14.8.1	2024-11-20	Standard	Change	Change: Performance improvements on the MLM setup page, which should load faster than in previous versions.
14.8.0	2024-11-14	Standard	New Feature	New feature: Descriptive Popups This feature represents the integration of Mark McEver's "Inline Descriptive Popup" External Module. Note: Upgrading to this version will not disable the "Inline Descriptive Popup" EM nor will it migrate any settings from the EM if the EM is being used in a project. Summary: Descriptive popups are custom popups of text that become visible after hovering over a specific word or phrase on a data entry form or survey. They have two main components: 1) the link text, which should match a word or phrase used on a form or survey, and 2) the custom text for the popup content. Users may set a descriptive popup to work on all instruments/surveys (default) or on specific ones. Descriptive popups are a great way to convey extra information on a form or survey without the text taking up space on the page. Users may configure their descriptive popups to be activated only on specific instruments. By default, they are enabled on all instruments. Additionally, if the popups are enabled to work on a survey, especially a multi-page survey, users can specify specific page numbers on which the popups will be activated. When copying a project or exporting a project via a Project XML file, there is now an option to copy/export the descriptive popup settings, respectively. Web accessibility: Descriptive popups are WCAG compliant, thus they will work with screen readers. MLM: Both the link text and popup content text of descriptive popups can be translated using Multi-Language Management.
14.8.0	2024-11-14	Standard	New Feature	New feature: Draft Preview Mode Draft Preview Mode allows users to preview their data entry forms with their current drafted changes as if they were live. This allows users to fully test the changes they have made in Draft Mode, including all branching logic, calculations, action tags, and embedded fields, before submitting their drafted changes for approval. Additionally, Draft Preview Mode will simulate live data entry on data entry forms, thus allowing users to enter ephemeral data that is stored only in their session; however, no data will actually be saved to the project. Once a user leaves Draft Preview Mode, all ephemeral data that has been entered will vanish. Limitations: While in Draft Preview Mode, the following limitations exist: No new records can be created. No data can be changed or stored in the project (all data changes are transient and are bound to the user's login session). Only changes to already existing forms can be previewed. Delete operations (deleting whole records or deleting data for forms/events) are disabled. Several more limitations exist and are delineated in the Online Designer before enabling Draft Preview Mode. Note: Draft Preview Mode only operates on data entry pages, the Record Status Dashboard, and the Record Home Page. It does not impact any other pages, and it currently does not work on survey pages.
14.8.0	2024-11-14	Standard	Improvement	Improvement: REDCap now supports the "address" HTML tag so that it may be utilized in user input (e.g., field labels, survey instructions). (Ticket #244390)
14.8.0	2024-11-14	Standard	Change	Change: In a MyCap-enabled project, REDCap now prevents the user from accessing the "View participant QR code" and "Invite Template" popups until the first MyCap app version has been published for the project.
14.8.0	2024-11-14	Standard	Change	Change: In a MyCap-enabled project, the "Messages" feature is now disabled in the MyCap participants list for participants that have not yet joined the project using the MyCap mobile app (i.e., their install date is blank).
14.8.0	2024-11-14	Standard	Change	Change: The "Learn Advanced Design Features" link on the left-hand project menu is now only displayed to users with Project Setup & Design privileges. (Ticket #244150)
14.7.4	2024-11-07	Standard	Improvement	Security improvement: When using REDCap's Two-Factor Authentication, the OTP (One Time Password) encryption secret, which is stored for a user in the back-end database and is used to generate their QR code for 2FA, has been increased to 160 bits to meet certain security standards. Note: This change will not affect existing users' ability to continue using their already-established Microsoft/Google Authenticator mobile app for 2FA in REDCap.
14.7.4	2024-11-07	Standard	Change	~~Change: Updated REDCap's session handler functions to be compatible with the upcoming PHP 8.4 release. Thus, the only REDCap versions that are compatible with PHP 8.4 are REDCap 14.7.4 and higher.~~
14.7.4	2024-11-07	Standard	Change	Change/improvement: The dates displayed in the "Other useful info" box on the main Control Center page are now listed in the date format dictated by the user's profile date format preference.
14.7.4	2024-11-07	Standard	Change	Change: On the Survey Invitation Log and Notification Log, a new warning has been added to the page when a project is in Analysis/Cleanup project status to denote that any already-scheduled survey invitations or alerts will not be sent while in Analysis/Cleanup status, despite the fact that the user may see scheduled invitations/alerts on those pages.
14.7.4	2024-11-07	Standard	Change	Change: The "Online Designer" video on the Training Videos page was updated, and a new video "Randomization" was added.
14.7.4	2024-11-07	Standard	Change	Change: When using Multi-Language Management in a MyCap-enabled project, the MLM setup page will now display a warning to users when adding an MLM language when the country code isn't supported in the MyCap mobile app.
14.7.3	2024-10-31	Standard	Change	Change/improvement: Better error reporting during CSV file import into MLM.
14.7.3	2024-10-31	Standard	Change	Change/improvement: Minor changes have been made to how the syntax files for R and SPSS are generated in order to improve the coding of labels in the syntax files. (Ticket #225047)
14.7.3	2024-10-31	Standard	Change	Change: New clarifying text was added to the instructional text displayed above the "Consent Form (Rich Text)" option in the "Add Consent Form" dialog on the e-Consent Framework page in order to indicate that images added via the rich text editor there will not be rendered in PDF exports or in stored PDF snapshots that include that consent form text.
14.7.3	2024-10-31	Standard	Change	Various changes for the External Module Framework, including the following: 1) The External Modules Framework error handling behavior has changed significantly. Every module error detected is now logged in the database instead of emailed. When errors occur, one email is sent per module per hour asking admins to check the "Recent Errors" page in Control Center for more details. And 2) Misc. security scan improvements.
14.7.2	2024-10-24	Standard	Improvement	Improvement: Users may now pipe the field label of a given field (instead of its data value) by appending ":field-label" to the variable name inside the square brackets. (Ticket #229991)
14.7.2	2024-10-24	Standard	Change	Change/improvement: Added a new "Learn Advanced Design Features" link on the project left-hand menu that, when clicked, opens a panel displaying buttons to learn about Smart Variables, Piping, Action Tags, Embedding, and Special Functions.
14.7.2	2024-10-24	Standard	Change	Change/improvement: The API Token Request Email that is sent to an administrator when a user requests a token (if this behavior is enabled at the system level) now contains the project PID number and a link to the project. (Ticket #242747)
14.7.2	2024-10-24	Standard	Change	Change: The "Video Tutorials" link on the project left-hand menu now takes the user to the Training Video page rather than displaying a list of specific video links below it.
14.7.1	2024-10-17	Standard	Improvement	Improvement: Better error handling in PHP for External Modules. Additionally, a new Control Center menu item named "Recent Errors" now appears on the left-hand menu in the "Dashboards & Activity" section.
14.7.1	2024-10-17	Standard	Improvement	Improvement: In MyCap-enabled projects, a new "Form completion status" setting has been added in the Online Designer that controls how a MyCap task's form completion status value is set when a task is submitted by a participant from the MyCap mobile app to the REDCap server. In previous versions, the MyCap task's form completion status would always be set to Incomplete. But now, it can be set to Incomplete, Unverified, or Complete so that the form status value is set to that specified status value any time that a participant completes a MyCap task. This setting can be modified at any point during data collection in a MyCap project. Note: Existing projects will maintain their existing default status setting of Incomplete, but that setting can be changed after the fact if desired. In contrast, all newly created projects will default to a status setting of Complete. However, if a new project is created using a Project Template that has MyCap enabled, the new project will adopt the MyCap form status setting of the Project Template. If you wish to change the default MyCap form status setting for all Project Templates that have MyCap enabled, run the following SQL (this is optional). This will ensure that all new projects, including those created via Project Templates will have this new setting set to Complete by default. Optional SQL: UPDATE redcap_projects p, redcap_projects_templates t SET p.task_complete_status = '2' WHERE p.mycap_enabled AND p.project_id = t.project_id;
14.7.1	2024-10-17	Standard	Improvement	Improvement: MLM languages now have a "Notes" field that can hold general notes regarding each MLM language on the MLM setup page (inside the Add/Edit Language dialog). These notes have no impact on MLM performance.
14.7.1	2024-10-17	Standard	Improvement	Improvements: New CDIS-related resource monitor which helps manage resource-intensive processes more effectively. This does not have a user interface but just helps improve performance in the background. Additionally, the number of queued records for Clinical Data Pull (CDP) being fetched from the EHR system during a single cron job batch has been increased to allow for more records to be processed in a given period of time.
14.7.1	2024-10-17	Standard	Improvement	Various changes and improvements for the External Module Framework, including the following: Added isMlmActive() method and getCurrentLanguage() method to javascript external module objects Renamed the bundled "Configuration Example" external module to "Module Development Examples" Added the $module->getSelectedCheckboxes() method Added a Twig development exercise to the external module documentation Prevented an error when "Export list with design rights users" is selected for modules not enabled on any projects Misc. security scan improvements
14.7.1	2024-10-17	Standard	Change	Change/improvement: In MyCap-enabled projects, several MyCap settings (Baseline Date Settings, Custom Event Label Settings, and new Form Completion Status setting) in the Online Designer have now been aggregated in a new"Additional Settings" dialog on that page.
14.7.1	2024-10-17	Standard	Change	Change: The instructional text for the "Automatic Triggering Option" on the Randomization page has been modified for improved clarity.
14.7.0	2024-10-09	Standard	New Feature	New features: Randomization enhancements Note: Thanks to Luke Stevens (Murdoch Children's Research Institute) for his contribution in building these new randomization features. A) Multiple randomizations in a project - Users may now define more than one randomization model in a single project. Each randomization model has its own settings (e.g., strata, randomization field, allocation table), and is completely independent of the other models. B) Blinded randomization support - Users may now create a randomization model that is blinded/concealed as a means of concealing the allocation (randomization value) from users to be able to have a truly blinded randomized clinical trial, for example. Users may still choose to create an "open" randomization model (as they always could) by choosing a single-select multiple choice field (e.g., drop-down or radio) to be the randomization field. Alternatively, users may now choose any text field [that does not have field validation] to represent the "randomization number". The randomization number can be uploaded as part of the allocation table, and when a record is then randomized, the field is given the randomization number as its value. C) New Smart Variables [rand-number] - The randomization number assigned to the record. For randomization in a text field (blinded allocation), this is equivalent to piping the randomization field. For randomization in a categorical field (open allocation), this will be the randomization number associated with the randomization group allocation, if one has been uploaded (this is optional). Use :n to refer to a specific randomization where a project has more than one (default=1). [rand-time] - The server date and time at which a record was randomized. In a piping context, such as in a field label, survey invitation, or inside the @default action tag, the format of the date and time will be displayed based on the current user's date/time display preferences. If you wish to have it return the raw value, which will instead be in 'YYYY-MM-DD HH:MM:SS' format and would be more appropriate for conditional logic or calculated fields, simply append :value. Use :n to refer to a specific randomization where a project has more than one (default=1). [rand-utc-time] - The UTC date and time at which a record was randomized. In a piping context, such as in a field label, survey invitation, or inside the @default action tag, the format of the date and time will be displayed based on the current user's date/time display preferences. If you wish to have it return the raw value, which will instead be in 'YYYY-MM-DD HH:MM:SS' format and would be more appropriate for conditional logic or calculated fields, simply append :value. Use :n to refer to a specific randomization where a project has more than one (default=1). D) New "Randomize Record" API method - This method allows an API user to randomize a record using the API. The API parameters required are content="record", action="randomize", record=Record name of record to randomize, and randomization_id=The unique id of the randomization (viewable on the Randomization page for users with Design permissions or on the API Playground page), which corresponds to a specific target field and event. This API method returns the value for the target randomization field (plus optionally the alternative target value), or an error message on failure (such as if the record does not exist or if stratification information is missing). E) New developer methods REDCap::getNextRandomizationAllocation() - Returns the integer allocation id if an unallocated entry is found, or string '0' if no entry is available (allocation table is exhausted). Returns false on error, e.g. if incorrect stratification information provided. REDCap::updateRandomizationTableEntry() - Updates the target (randomization field or number), alternate target (randomization group or number), or "is_used_by" (e.g., the record to which this allocation/sequence belongs) details for a specified allocation table entry. For example, this method can be utilized to effectively perform the randomization action itself. F) New External Module Hook "redcap_module_randomize_record" - Allows custom actions to be performed prior to the randomization of a record - e.g., to override the default randomization allocation. This hook enables implementation of custom randomization allocation routines, e.g. dynamic randomization via minimization. It is expected that only one external module implementing this hook will be enabled in a single project. A warning will be generated if multiple external modules return results from this hook. Location of Execution: The function is executed immediately prior to lookup and assignment of the next available entry in the randomization allocation table. This lookup and allocation is skipped if all redcap_randomize_record hooks return false. G) Real-Time Trigger Logic - Randomization can be automated to occur in real time when an instrument is saved and a specified logic expression becomes True, in which all required stratification information must be present. At the bottom of the randomization setup page for a given randomization model, the following options are displayed. Manual only (default) - A user with "Randomize" user permissions must click the "Randomize" button on the data entry form where the randomization field is located. Trigger logic, for users with Randomize permissions only - When the Save button on a specified data entry form is clicked, if the logic expression provided evaluates to True and the current user has "Randomize" user permissions, the record will automatically be randomized (i.e., without clicking a "Randomize" button). Trigger logic, for all users (including survey respondents) - When the Save button on a specified data entry form or survey page is clicked, if the logic expression provided evaluates to True (despite the user's permissions if on a data entry form), the record will automatically be randomized. H) New options for REDCap administrators [only] to perform the actions below, which are meant to be used in rare/unexpected situations. These can be found when viewing the allocation table under the Dashboard section of a randomization model. Note: Whenever an administrator uses one of the actions, they must provide a "reason" as text, which gets added to the project Logging. Manually randomize a record - Provide a value for a randomization group or number to manually set the randomization value for a specified record. Remove the randomization for a record (un-randomize it) - If a record has already been randomized, remove that record's randomization allocation so that it will no longer appear randomized and so that another record might possibly get assigned that allocation. Edit an allocation/sequence - Modify the randomization group and/or randomization number value for an unallocated sequence. This is essentially the equivalent of modifying an existing allocation table. Make an allocation/sequence unavailable - Remove an allocation/sequence so that it will not be used in a future randomization. This is essentially the equivalent of removing a row from an existing allocation table. I) Project XML & Copy Project - Randomization model settings have now been added as an optional component to copy when doing a "Copy Project" action or when exporting->creating a project via a Project XML file.
14.7.0	2024-10-09	Standard	Improvement	Improvement: In a MyCap-enabled project that is using Multi-Language Management, users can now more easily populate the MyCap Language ID and Language display name by clicking the MLM language ID from the allowed languages list on the MLM setup page for the MyCap mobile app (via the Add/Edit Language popup). These were merely displayed in previous versions, but now they are clickable, which makes them easier to add to the MLM setup page.
14.7.0	2024-10-09	Standard	Improvement	Improvement: In a MyCap-enabled project, the "View Task Details" popup in the Online Designer now includes detailed scheduling information per event for longitudinal projects.
14.7.0	2024-10-09	Standard	Improvement	Improvement: New MLM action tag LANGUAGE-MENU-STATIC - When this action tag is present on any field of an instrument enabled as a survey, and Multi-Language Management is active with at least two active languages, the language selection menu will remain visible at all times (i.e., it will not collapse after a language button has been clicked). (Ticket #241790)
14.7.0	2024-10-09	Standard	Improvement	Improvement: New piping option ":hideunderscore" - If a field value or Smart Variable value is blank/null (i.e., does not exist), then by default the blank value will be piped as six underscore characters (literally ______) as a placeholder to visually indicate that no value exists. However, if this behavior is not desired, users may append :hideunderscore to the variable name inside the square brackets (e.g., [first_name:hideunderscore], [race:value:hideunderscore]), and this will cause value to be piped as-is, that is, as a blank/null/invisible value. Note: The :hideunderscore notation may be appended to both field variables and Smart Variables.
14.7.0	2024-10-09	Standard	Change	Change: On the MyCap Configuration Check page in the Control Center, the PID has been added for each project displayed in the project drop-down list on that page.
14.7.0	2024-10-09	Standard	Change	Change: The newer-style "disabled" buttons in the Online Designer (added in REDCap 14.6.11) have been slightly modified from an encircled X to an encircled dash since it is thought that an X might imply a "delete" action rather than a "disabled" state. Additionally, the event-level ASI "Modify" buttons that are displayed in longitudinal projects when clicking the "Automated Invitations" button next to each survey in the Online Designer were updated with the new icons that were added elsewhere in the previous version.
14.7.0	2024-10-09	Standard	Change	Change: Two new videos were updated: "Field Types" and "Online Designer".
14.7.0	2024-10-09	Standard	Change	Change: Various minor bug fixes and enhancements for Multi-Language Management (mostly related to export and change tracking with regard to MyCap items).
14.6.11	2024-10-03	Standard	Improvement	Improvement: A new PDF download button has been added to the instrument-view of the Online Designer to allow users to download all instruments as a single PDF.
14.6.11	2024-10-03	Standard	Improvement	Improvement: REDCap now supports the "progress" and "meter" HTML tags so that they may be utilized in user input (e.g., field labels, survey instructions).
14.6.11	2024-10-03	Standard	Improvement	Improvement: Slight aesthetic changes have been made to the buttons displayed in the instrument-view of the Online Designer. Additionally, the "e-Consent and PDF Snapshot" button has been separated into two separate buttons under Survey Options and Form Options, respectively.
14.6.11	2024-10-03	Standard	Improvement	Improvement: The improved "Field Navigator" on the Online Designer now always floats on the right-hand side of the page and also has links to allow users to jump to specific Section Headers on the page.
14.6.11	2024-10-03	Standard	Improvement	Improvement: When the Google reCAPTCHA feature is enabled, administrators may now set the default state of that feature (as either initially enabled or disabled) in newly created projects. This can be set in the Google reCAPTCHA section of the Modules/Services Configuration page in the Control Center. By default, this new setting is set to "Disabled by default for new projects". (Ticket #237045)
14.6.11	2024-10-03	Standard	Change	Change: For predefined ResearchKit active tasks in MyCap-enabled longitudinal projects, the "Active Task Settings" section on the task setup page has been moved to the task-level instead of the event-level (as seen in previous versions). Thus, there will be only one "active task setting" per task available even if multiple events are enabled on the task setup.
14.6.11	2024-10-03	Standard	Change	Change: Question Numbering on surveys is now set to "Custom numbered" by default when enabling an instrument as a survey.
14.6.11	2024-10-03	Standard	Change	Change: The "Preview instrument" button on the field-view page of the Online Designer has now been removed due to seldom use and also because in recent years it no longer provides a reliable presentation of the instrument for moderately-complex projects. (Ticket #241293)
14.6.10	2024-09-26	Standard	Improvement	Improvement: Accessibility improvements have been made to all Control Center pages and other non-project pages (e.g., My Projects, REDCap Home Page) with specific regard to improving the color contrast of text on the page.
14.6.10	2024-09-26	Standard	Improvement	Improvement: More documentation has been added for Shibboleth authentication on the Security & Authentication page to set up the auto-import feature for a user's first name, last name, and/or email address.
14.6.9	2024-09-20	Standard	Improvement	Improvement: For MyCap projects that are longitudinal with multiple arms, users may now designate a Baseline Date Field for every arm on the baseline date setup popup in the Online Designer.
14.6.9	2024-09-20	Standard	Improvement	Improvement: When using Shibboleth authentication for REDCap, admins may now enable a new setting on the Security & Authentication page to allow REDCap to automatically import a user's first name, last name, and/or email address the first time they log in or every time they log in to REDCap. Note: This may require some configuration changes on the Shibboleth side so that these user attributes appear as new $_SERVER variables.
14.6.8	2024-09-18	Standard	Improvement	Various changes and fixes for the External Modules Framework, including: 1) Added a warning about External Module composer dependency conflicts above the Control Center module management list, 2) Fixed an error with the "external_modules" framework development dir's out of date detection, 3) Updated Twig from v3.11.0 to v3.11.1, and 4) Misc. security scan updates.
14.6.8	2024-09-18	Standard	Change	Change/improvement: Better support for handling various authentication methods in a CDIS context (e.g., logging into REDCap via "Launch from EHR" context for CDP).
14.6.6	2024-09-15	Standard	Improvement	Improvement: Enhancement to the information provided for the existing EHR access status and auto-login indicators in the CDIS panel of REDCap projects. EHR Access Status: Detailed information about the user's current EHR access is now available when clicking on the EHR access indicator within the CDIS panel. Additionally, this information is also displayed on the Project Home page of CDIS projects. Auto-login Indicator: Clicking on the auto-login indicator in the CDIS panel now provides users with additional details about how the auto-login feature works, including the process of mapping REDCap and EHR accounts during the "Launch from EHR" process.
14.6.6	2024-09-15	Standard	Improvement	Improvement: The field validation type is now displayed below each Text field in the Online Designer (similar to how action tags are displayed for each field).
14.6.5	2024-09-05	Standard	Improvement	Improvement: On the External Modules page in the Control Center, a new warning will be displayed when REDCap detects potentially incompatible Composer packages (i.e., third-party libraries) used inside the code of individual External Modules that may cause REDCap to crash unexpectedly. This warning will provide a list of which EMs might not be compatible with other EMs installed in the system, and provides information that can be given to the EM's creator to resolve these potential compatibility issues.
14.6.5	2024-09-05	Standard	Improvement	Improvement: When exporting the Project XML file for a project that has alerts, there is now a new checkbox "Leave Alerts enabled (unless disabled)" on the Other Functionality page below the "Alerts & Notifications" checkbox. Going forward, all alerts in the Project XML file will be disabled by default unless the user checks the new checkbox to keep them enabled. In previous versions, alerts in the Project XML file would import into the new project as is (i.e., if enabled, it would stay enabled, and if disabled, it would stay disabled). This new option gives users more control over the default state of alerts in the newly created project. (Ticket #238810)
14.6.5	2024-09-05	Standard	Change	Change: When deleting a data quality rule when the Data Resolution Workflow feature is enabled in a project, the rule deletion dialog will now display a red warning to the user to inform them that deleting the rule will also delete any data queries (open or closed) that are currently associated with that data quality rule. (Ticket #219303)
14.6.4	2024-08-29	Standard	Improvement	Change/improvements: The following web accessibility improvements were added to the REDCap Home Page: 1) Fixed headings so that it starts with h1 tag, 2) Moved navigation section outside of main section, 3) Added "skip to main content" link (press the Tab key to reveal the link), and 4) Fixed headings within Messenger (i.e. proper h tag level for Notifications and Conversations in Messenger) on Home page.
14.6.4	2024-08-29	Standard	Improvement	Various changes and improvements to the External Module Framework, including 1) Added built-in Twig support via module framework version 16, and 2) Expanded $module->getChoiceLabels() to support true/false & yes/no fields.
14.6.3	2024-08-22	Standard	Improvement	Improvement: Slight change in the Database Query Tool's "show more" link's behavior to improve performance after being clicked on a page with large column values.
14.6.3	2024-08-22	Standard	Change	Change: After completing a survey, the "Close survey" button is now displayed below the Survey Completion Text so that it is no longer the first thing that participants see on the page.
14.6.3	2024-08-22	Standard	Change	Change: Background Data Imports would automatically be halted if they took more than 24 hours to complete. This limit has been increased to 48 hours to allow some very large imports more time to import all their data.
14.6.2	2024-08-15	Standard	New Feature	New feature: Clinical Data Pull Dashboard - New admin-only page that appears on the left-hand menu in CDP projects. Key features: Queueing and Fetching: The dashboard outlines the cron job processes for queueing records based on specific criteria and fetching queued data for caching and further review. Manual Queueing: Users have the ability to manually mark non-queueable records as QUEUED, forcing their data to be fetched during the next data fetching cycle. Cached Data Page: A dedicated "Cached" page allows users to view and decrypt detailed information for each record and field, including timestamps, to ensure data accuracy and timeliness. Administrator Access: A link to the Dashboard is available exclusively for administrators in the "Clinical Data Interoperability Services" or "Clinical Data Pull" panels.
14.6.2	2024-08-15	Standard	Improvement	Improvement/change: Optimization for the Background Data Import process for importing records faster for very large projects (e.g., >100K records). (Ticket #237549)
14.6.2	2024-08-15	Standard	Improvement	Improvement: If MySQL/MariaDB clustering or replication is implemented on your REDCap database server, in which it might be required that every database table has an auto-incremented Primary Key, the Configuration Check (at the bottom of the page) will auto-generate and display all the SQL needed to add auto-incrementing Primary Keys to all REDCap database tables that currently do not have them. (Ticket #236440)
14.6.2	2024-08-15	Standard	Improvement	Improvement: On the Security & Authentication page, administrators using "OpenID Connect" or "OpenID Connect & Table-based" authentication can now optionally set a custom logout URL to direct users to after logging out of the application. (Ticket #143391)
14.6.0	2024-08-01	Standard	New Feature	New feature: Bulk Record Delete Users may use the Bulk Record Delete page to delete multiple records from the project or alternatively to delete data for multiple instruments across multiple records. To perform either of those two actions, a user must have "Delete Records" privileges, and for the partial delete option, a user must additionally have "View & Edit" instrument-level privileges for the instrument that they select. The Bulk Record Delete page can be accessed from two different locations in a project: 1) On the Other Functionality page, and 2) On the Record Status Dashboard via the new Multi-Record Actions dropdown. If the project has the GDPR-related feature "Delete a record's logging activity when deleting the record?" enabled in the project, the user will be prompted with a checkbox to additionally delete the record's logged events on the Logging page when deleting entire records. If the "Require reason for change" option is enabled in the project, users will be prompted to enter a reason that will get logged when performing a partial delete of one or more instruments. The Bulk Record Delete feature can be disabled for the whole system on the Modules/Services Configuration page in the Control Center, if desired. By default, this feature will be enabled. Note: If a user is performing a partial delete, the instrument's data cannot be deleted in the following situations: 1) If the form is locked, 2) If no users are allowed to modify survey responses (via the system-level setting) and the data of the selected instrument(s) is a survey response, 3) If the user does not have form-level rights to modify survey responses for the selected instrument(s) and the data of the selected instrument(s) is a completed survey response, or 4) If the selected instrument(s) is a completed e-Consent response and e-Consent responses are not allowed to be edited per the survey's e-Consent settings.

Version	Old Version 1	New Version Current
Changes made by	Christopher Sorensen	Christopher Sorensen
Saved on	Feb 11, 2025	Feb 11, 2025

Content Comparison

Versions Compared

Key