Version Changes

This page lists all relevant changes that have been made during a version release. It indicates the date installed or when it was released which will approximate the installation date. Bug fixes are not itemized as they are not relevant to this page but are indicated so that you are aware no new functionality or change has been made. Only changes that have been made over the past 12 months are shown.

Version 10.3.4 (released on 2020-09-25) - (installed 9/25/2020)


Version 10.3.3 (released on 2020-09-17) - (installed 9/25/2020)


Version 10.3.2 (released on 2020-9-11) - (installed 9/4/2020)


CHANGE: If a project has Randomization enabled and is currently in production, REDCap administrators will not be allowed to move the project back to development status as they normally can on the Other Functionality page. This option is disabled in this case to prevent issues occurring with randomization, such as the fact that all values for the randomization field get erased when moving from development to production.

Version 10.3.1 (released on 2020-09-03) - (installed 9/4/2020)


Version 10.3.0 (released on 2020-08-27) - (installed 9/4/2020)


NEW FEATURE: Added "Language of text to be spoken" for the "Text-To-Speech" survey functionality which is available on the Survey Settings page. For several years, REDCap has had a Text-to-Speech feature for surveys that, when enabled, allows questions and other text on survey pages to be converted into natural-sounding audio for the participant to hear. Up until now, it supported English only, but now REDCap users may utilize the Text-to-Speech feature in a variety of non-English languages and voices, assuming that the survey text is in a non-English language. This includes Arabic, Brazilian Portuguese, English (UK and US), French, German, Italian, Japanese, and Spanish (Castilian, Latin American, and North American).

NEW FEATURE: Users may re-evaluate some or all Automated Survey Invitations for all records in a project. If an ASI has been modified after data has already been entered in the project, users may click the “Re-evaluate Auto Invitations” button in the Online Designer, which will re-evaluate selected ASIs for all records to ensure that invitations get properly sent or scheduled based on the new conditions of the ASI (otherwise they could only be triggered if each individual record had data modified). If a user modifies the conditional logic of an ASI, it will recommend that they utilize the “Re-evaluate Auto Invitations” functionality. If an ASI has the “Ensure logic is still true…” option checked, then it is possible during this process that some already-scheduled invitations might get removed (and thus would no longer be scheduled) based on the new conditions.

NEW FEATURE: Users may re-evaluate some or all Alerts & Notifications for all records in a project. If an alert has been modified after data has already been entered in the project, users may click the “Re-evaluate Alerts” button on the Alerts & Notifications page, which will re-evaluate selected alerts for all records to ensure that notifications get properly sent or scheduled based on the new conditions of the alert (otherwise they could only be triggered if each individual record had data modified). If a user modifies the conditional logic of an alert, it will recommend that they utilize the “Re-evaluate Alerts” functionality. If an alert has the “Ensure logic is still true…” option checked, then it is possible during this process that some already-scheduled notifications might get removed (and thus would no longer be scheduled) based on the new conditions.

IMPROVEMENT: When deleting an invitation from the Survey Invitation Log (either as a single invitation or using the multi-select option to delete many invitations at once), it now provides a new option in the dialog prompt to “Permanently cancel this invitation?”, in which the phrase “permanently cancel” implies that the invitation cannot be re-triggered/scheduled again in the future even if the ASI conditions are met again. If the user chooses to uncheck the option, then the scheduled invitation will be removed, but could possibly get re-triggered in the future if the ASI conditions are met again (assuming it was originally scheduled via an ASI).

IMPROVEMENT: The Survey Invitation Log has a new filter drop-down option to view “only deleted invitations” (i.e., permanently cancelled invitations).

IMPROVEMENT: Large performance improvement when importing lots of records (via Data Import Tool, Mobile App, API, or REDCap::saveData) when record auto-numbering is enabled in a project and the import process is forcing the new records to be auto-numbered on the fly.

IMPROVEMENT: Smart Variables and regular field variables can now be piped into the URL of Project Bookmarks. Note: While many Smart Variables can be piped successfully outside of a record context (e.g., [redcap-base-url]), all field variables (e.g., [age], [dob]) and some Smart Variables (e.g., [record-name], [previous-event-name]) can only be piped into the URL while the user is inside a record context, such as viewing the Record Home Page or data entry form.

CHANGE: Slight re-organization of buttons at the top of the instrument list on the Online Designer.

Version 10.2.3 (released on 2020-08-21) - (installed 9/4/2020)


IMPROVEMENT: When importing a CSV file of data on the Data Import Tool or when importing a CSV Data Dictionary, users may now specify the delimiter of the CSV file as a Comma (default), Tab, or Semicolon.

IMPROVEMENT: In previous versions, the DAG Switcher would not be very performant if there existed very many users and/or Data Access Groups within a project, thus the DAG Switcher would (by design) be automatically disabled for projects in those situations, which was not ideal with regard to user experience. The DAG Switcher is now no longer limited in that way and will now function fully regardless of there being many users and DAGs in a given project.

Version 10.2.2 (released on 2020-08-14) - (installed 9/4/2020)


Version 10.2.1 - (installed 8/9/2020)


IMPROVEMENT: The "Response Limit" option on the Survey Settings page now allows for the use of the rich text editor when defining custom text to display to respondents on the survey when limit is reached.

Version 10.2.0 - (installed 8/3/2020)


NEW FEATURE: New Stealth Queue Functionality

  • New ”Keep the Survey Queue hidden from participants?” setting in the “Set up Survey Queue” dialog on the Online Designer
  • This setting will keep the Survey Queue table hidden from participants, and will force Auto Start to be enabled for all queue-activated surveys. This is useful if users wish to use the Survey Queue to automatically guide survey participants to the next survey without displaying the queue of surveys.

IMPROVEMENT: Data Resolution Workflow feature

  • When a user is opening a new data query and assigning the query to a user, there are new options to send a notification to the assigned user via email and/or REDCap Messenger to inform them about their query assignment.
  • Attachment files that have been uploaded to an opened data query may now be deleted after the fact, if needed. Note: As a precaution, only REDCap administrators may delete such attachments.
  • For existing data queries, users may now be assigned to an opened query after the fact, and if the data query already has a user assigned to it, it may be reassigned to another user.

Version 10.1.5 - (installed 7/26/2020)


Version 10.1.4 - (installed 7/18/2020)


Version 10.1.3 - (installed 7/17/2020)


CHANGES: he text was updated for the REDCap features listed on the REDCap Home Page

Version 10.1.2 - (installed 7/17/2020)


Version 10.1.1 - (installed 7/17/2020)


NEW FEATURE: Select and modify multiple fields together on the Online Designer - Users may select multiple fields on the Online Designer by holding the Ctrl, Shift, or Cmd key on their keyboard while clicking on the field in the table, which will reveal the options to Move, Copy, or Delete all the selected fields. To make users aware of this feature, a floating note now appears near the right side of the page in the Online Designer with instructions on how to use this.

Version 10.1.0 - (installed 7/4/2020)


CHANGES: In Alerts & Notifications, the email "To" field that is used for an alert now allows fields having custom email validation (i.e., added manually in the redcap_validation_types database table) to be utilized as the recipient. Previous versions only allowed fields to be used that had the explicit "email" field validation.

Version 10.0.4 - (installed 6/28/2020)


IMPROVEMENT: In REDCap 10.0.2, a new feature was added to the Online Designer’s “Add/Edit Branching Logic” dialog to help users modify branching logic for many fields at once if they had the exact same branching logic. Now this has been improved further so that if users do not want to keep seeing this prompt when editing branching logic, a new checkbox in the dialog that says “Do not show this message again” can be checked, which will prevent the prompt from being displayed in that project for that user during the remainder of their REDCap session.

Version 10.0.3 - (installed 6/28/2020)


CHANGE: When exporting data to a stats package (R, Stata, SPSS, SAS), if a field contains a long field label, it now truncates the field label in the center of the text (i.e., putting an ellipsis in the middle) to make it more compatible with and easier to read in certain stats packages.

CHANGE: When copying a project via the Copy Project page, Alerts & Notifications will now be automatically set to "Deactivated" status in the newly created project, similar to Automated Survey Invitations when copying a project. This is to ensure that they do not start getting triggered and start sending if all the project records were copied from the original project.

CHANGE: Date fields that have Y-M-D date format would allow M/D/Y format values (i.e., American format dates with slashes instead of dashes) to be entered, in which it would automatically reformat the value to a Y-M-D format date with dashes. This is a very old behavior from the earliest days of REDCap that was meant to be a convenience for users, who were mostly from the U.S. at that time. However, since that time REDCap has grown internationally, and it is no longer U.S.-centric as it was in the early days. It makes more sense at this time to remove this old behavior so that Y-M-D date formats only accept Y-M-D formatted values. (Ticket #86446)

Version 10.0.2 - (installed 6/14/2020)


IMPROVEMENT: Improvements for the My Projects page

  • Link to Online Designer: Adds links to the Online Designer page of projects in the Fields column.
  • Link to Record Status Dashboard: Adds links to the Record Status Dashboard in the Records column.
  • Collapse All: Adds a Collapse All button next to the Organize button that collapses all project folders.
  • Organize Projects filtering: Adds a filter in the Organize Projects pop-up.

IMPROVEMENT: When editing a field’s branching logic in the Online Designer’s “Add/Edit Branching Logic” dialog, when saving the branching logic for a given field, it will now check if any other fields in the project have identical branching logic and will prompt the user to ask them if they want to change the branching logic accordingly for all fields having the same branching logic.

CHANGE: When viewing an Automated Survey Invitation in which the From address belongs to a user that no longer has access to the project, it would display the note "[email no longer belongs to a project user]" next to the email address, but it would not display that note for Administrators. It now displays it to both regular users and Administrators to eliminate any confusion.

CHANGE: When viewing an alert on the Alerts & Notifications page in which the alert's From address belongs to a user that no longer has access to the project, it now displays the note "[email no longer belongs to a project user]" next to that email address in the drop-down list.

Version 10.0.1 - (installed 6/8/2020)


IMPROVEMENT: Survey pages are now considered ADA Section 508 compliant. The REDCap Development Team at Vanderbilt has been collaborating with the CDC to improve the accessibility of REDCap overall. While the user-facing side of REDCap (i.e., non-survey pages where users must authenticate) is not 508 compliant, it continues to be improved with regard to accessibility over time. But according to the CDC's recommendations and testing of REDCap, survey pages in REDCap do meet the minimum requirement for ADA Section 508 compliance.

Version 10.0.0 - (installed 5/31/2020)


NEW FEATURE: Field Embedding

  • Field Embedding is the ultimate way to customize surveys and data collection instruments to make them look exactly how you want. Field Embedding is a Shazam-like feature that allows you to reposition field elements on a survey page or data entry form so that they get embedded in a new location on that same page. Embedding fields gives users greater control over the look and feel of your instrument. Users may place fields in a grid/table for a more compact user-friendly page, or they can position fields close together in a group if they are related.
  • To use Field Embedding, users simply need to place the REDCap variable name of a field inside braces/curly brackets - e.g., {date_of_birth} - and place it in the Field Label, Field Note, Section Header, or Choice Label of any other field on that same instrument. Field embedding will not work across instruments but only on the current instrument/survey being viewed. If on a multi-page survey, then the embedded field must be on the same survey page as its host field.
  • No action tags or custom HTML is required to use Field Embedding. Users can simply use the rich text editor in the Online Designer to design their layout and then place the field variables inside that layout. The layout does not have to be a table/grid (although tables are common for this), and fields can be embedded inside *any* field type (not just Descriptive fields).
  • We wish to thank Andy Martin (Stanford) because his popular Shazam external module served as the conceptual inspiration of the Field Embedding feature.
  • Note: When installing or upgrading to v10.0.0, a new project “Field Embedding Example Project” will be automatically added as a project template to allow users and admins to easily see some examples of Field Embedding in action.

IMPROVEMENTS/CHANGE: Removed the thick black border seen on input fields that have focus for Chrome 83 and higher, which was by default adding the black border to all input fields on all webpages.

IMPROVEMENTS/CHANGE: Added better error detection to make the data import process more accurate and informational by ensuring that any datetime_seconds values that are missing a “seconds” component will be reformatted to append “:00” and if any datetime values are missing a “minutes” component it will be reformatted to append “:00”, in which it will display a warning to the user on the Data Import Tool page to inform the user that these modifications are happening. Also, if the first two digits of the “year” component are missing for a date or datetime value, it now displays a warning to inform the user that the full year value will be estimated and will note the resulting estimated year value.

IMPROVEMENTS/CHANGE: On the Survey Settings page, The Save & Return Later option "Allow respondents to return without needing a return code" now has a note immediately below it to encourage users not to use this survey option if they are collecting identifying information (PHI, PII) on their survey.

Version 9.10.0 - (installed 5/25/2020)


NEW FEATURE: Record-level locking feature

  • This feature allows users to lock an entire record (as opposed to locking individual instruments) so that none of the record’s data can ever be modified unless someone with record-level locking/unlocking privileges goes and unlocks the record again.
  • The old “lock all forms for all events” feature has been changed into this new record-level locking feature, which is distinguishable from the existing instrument-level locking feature. Now the instrument-level locking can only be used while on a data entry form (using the Locking checkbox at the bottom of the form). Whereas the record-level locking feature is available as an option on the Record Home Page and on the project’s left-hand menu after a record has been selected.
  • While records have always been able to be locked (i.e., made read-only) for individual data collection instruments in a project, you may now easily lock an ENTIRE record so that no data in the record can ever be modified while it is locked.
  • WHAT HAS CHANGED? It is important to note that the old user privilege "Lock all forms" has now been converted into the new record-level locking feature, which works completely independently from instrument-level locking (i.e., the checkbox at the bottom of data entry forms). Instead of that particular user privilege allowing you to lock all forms individually (which was the previous behavior), it will now serve in a slightly different capacity as the record-level locking user privilege to lock an entire record fully.
  • HOW TO USE IT: You may lock an entire record via the "choose action for record" drop-down on the Record Home Page or by clicking the "Lock Entire Record" link on the project's left-hand menu when viewing a record. Note: Since the record locking and instrument locking are completely separate features, they both may be used together in a project, if you wish. However, please note that since record locking is a higher-level locking than instrument locking, an entire record may be locked or unlocked while one or more instruments are currently locked, but an instrument cannot be locked or unlocked while the entire record is locked.

NEW FEATURE: Record-level Locking Enhancement: PDF confirmation & automatic external file storage

  • This feature allows users to utilize extra functionality regarding the use of record-level locking in a project. It must first be enabled at the system level (at the bottom of the Modules/Services Configuration page in the Control Center). It is disabled by default for all projects, but users with 'Project Setup & Design' rights can enable it for a project in the Additional Customizations popup on a project's Project Setup page.
  • How it works: When enabled for a project, if a user goes to lock an entire record, they will be presented on the page with an embedded PDF of the entire record’s data, and after confirming that the record is correct, the record will be locked at the record level and a PDF copy of the entire record will be stored in a “PDF Archive of Locked Records” section of the File Repository of the project and additionally will be stored on a secure external server via WebDAV or SFTP storage.
  • The connection to the external file server can be set up as WebDAV or SFTP, in which the details/credentials must be provided when enabling this system-level setting at the bottom of the Modules/Services Configuration page in the Control Center.
  • This feature may be utilized for projects wishing to adhere to certain regulatory compliance, such as 21 CFR Part 11 for FDA trials. Please note that enabling this feature does not make the feature or your REDCap installation automatically “Part 11 compliant”. It is assumed that if using this for Part 11 compliance that you have already gone through all the processes of documenting and validating your REDCap environment (or parts of it) to validate it as “Part 11 compliant” beforehand.

IMPROVEMENTS/CHANGE: The project ID (PID) of a project is now displayed immediately after the project title at the top of every project page. This will make it easier for users to obtain their project's PID when attempting to identify their project to administrators.

Version 9.9.2 - (installed 5/25/2020)


IMPROVEMENTS/CHANGE: New PDF customization to hide the Record ID from the PDF header. In the "PDF Customizations" section of the "Additional Customizations" dialog on the Project Setup page, users may set this option to display or hide the record name in the top header of every PDF page when downloading a PDF with data for a record. This is a project-level setting, so setting it applies to all PDFs generated for records in the project.

IMPROVEMENTS/CHANGE: The sending of a survey confirmation email now gets logged on the project Logging page when a confirmation email has been set to send to a survey participant after having completed a survey, in which the logged event will note the record name, the To address, the From address, the email subject, and whether or not the email contained attachments (including the PDF of the participant's survey responses).

IMPROVEMENTS/CHANGE: Changes for long-standing quirks with calc fields and branching logic

  •  In previous versions, calculated fields could only utilize either numeric fields or date/datetime fields in the calculation. Now non-numeric fields may be used, most notably inside IF statements. For example, if ([field1] = “A”, 0, 99).
  •  In previous versions, using > or < in branching logic would not always work as expected. For example, [a] > [b] would have to be formatted as [a]*1 > [b]*1 to work correctly 100% of the time, which is not intuitive. This is no longer required, in which [a] > [b] will work as one would expect in branching logic. Note: This does not apply to calc fields, which have never had this problem.
  • The datediff() function used in branching logic and calc fields no longer requires the date format parameter (“ymd”, “mdy”, “dmy”). This was required for datediff() in calc fields and branching logic but was not required elsewhere, such as in report filters, DQ rule logic, ASI/Alert conditions, etc. The $returnSignedValue parameter (if provided) can now be provided as the fourth parameter - e.g., datediff([dob], “today”, “y”, true). NOTE: Both of the date/datetime fields used in the datediff function must still be in the same date format (“mdy”, “dmy”, or “ymd”), so that is still a requirement.

Version 9.9.1 - (installed 5/25/2020)


IMPROVEMENTS/CHANGE: A new send-time option has been added when setting up Automated Survey Invitations and Alerts & Notifications. When defining when the ASI/Alert should be sent, the option “Send after a lapse of time” has a new setting added so that, if desired, the user may set the time lapse relative to the value of a date or datetime field in the project. In previous versions, the time lapse setting could only be set relative to the time in which the ASI/Alert was triggered. That is still an option, but now users may also opt to send the ASI/Alert a certain amount of time either before or after the date/time of a specific field. This new setting will allow users to have greater control with regard to setting when ASIs/Alerts will be sent without getting too complicated in their setup, such as having to use complex logic (with datediff, etc.).

Version 9.9.0 - (installed 5/3/2020)


NEW FEATURE: Users assigned to Data Access Groups (DAGs) can optionally be assigned to multiple *potential* DAGs, in which they may be given the privilege of switching in and out of specific DAGs on their own whenever they wish.

  • When assigned to multiple DAGs, the user will see a blue banner at the top of every project page, which will present them with the option to switch to another DAG. NOTE: Users may not move themselves into another DAG unless someone with rights to this page has explicitly granted them privileges to be in multiple DAGs.
  • To assign a user to multiple DAGs, navigate to the Data Access Groups page in a project where you will see the DAG Switcher near the bottom of the page. Then follow the directions provided there. The DAG
    Switcher feature is completely optional and can be used in any project that has Data Access Groups.
  • NOTE: The DAG Switcher feature does not override a user's current DAG assignment, as set on the Data Access Groups page or on the User Rights page.
  • This feature is the result of integrating the “DAG Switcher” external module that was built by Luke Stevens. We thank him for his contribution and for agreeing to let us integrate this useful module into REDCap. NOTE: Because the “DAG Switcher” external module is not compatible with this integrated functionality in v9.9.0, when upgrading REDCap to 9.9.0 or higher, if the “DAG Switcher” external module is already installed and enabled on your REDCap system, it will be automatically disabled at the system level during the upgrade process to prevent a conflict..

IMPROVEMENTS/CHANGE: Users are now able to utilize dots/periods/full stops in the codings of choices for checkbox fields. In previous versions of REDCap, this was not allowed for checkbox fields.

IMPROVEMENTS/CHANGE: By popular demand, users may once again utilize dots/periods/full stops in Missing Data Codes. They are no longer forbidden. They were originally allowed for Missing Data Codes, but then removed in REDCap 8.5.0. Now that checkboxes can have dots/periods in their codings as of v9.9.0, it is no longer an issue for Missing Data Codes to use them too.

Version 9.8.5 - (installed 4/26/2020)


Version 9.8.4 - (installed 4/19/2020)


Version 9.8.3 - (installed 4/19/2020)


Version 9.8.2 - (installed 4/10/2020)


Version 9.8.1 - (installed 4/6/2020)


Version 9.8.0 - (installed 3/29/2020)


CHANGE: The "Archived" project status has been removed and converted into a built-in Project Folder named "My Hidden Projects", as now seen at the bottom of each user’s My Projects page. If users wish to hide any projects from their My Projects list, they may click the Organize button on that page and place the projects into that new Project Folder. NOTE: Any already-archived projects will be automatically placed there and will have their project status set as "Analysis/Cleanup" to match the projects’ general behavior prior to the upgrade.

CHANGE: The "Inactive" project status has been renamed to "Analysis/Cleanup" status to help reinforce that cleaning and analyzing the data is the next logical step after data collection in Production status.

CHANGE: New records can no longer be created while in "Analysis/Cleanup" status. If users wish to create records, the project must be moved back to Production status.

NEW FEATURE: Projects that are in "Analysis/Cleanup" status can now optionally have their project data set as "Locked/Read-only" or "Editable" (see the top of the Project Setup or Project Home page). This will give users more control to prevent data collection from happening while in this project status.

NEW FEATURE: Mark a project as "Completed": If users are finished with a project and wish to make it completely inaccessible, they may mark the project as Completed. Doing so will take it offline and remove it from everyone's project list, after which it can only be seen again by clicking the Show Completed Projects link at the bottom of the My Projects page. Once marked as Completed, no one in the project (except for REDCap administrators) can access the project, and only administrators may undo the Completion and return it back to an accessible state for all project users. Marking a project as Completed is typically only done when users are sure that no one needs to access the project anymore, and they want to ensure that the project and its data remain intact for a certain amount of time.

Version 9.7.8 - (installed 3/15/2020)


Version 9.7.7 - (installed 3/4/2020)


Version 9.7.6 - (installed 3/2/2020)


Version 9.7.5 - (installed 2/24/2020)


Version 9.7.4 - (installed 2/24/2020)


Version 9.7.3 - (installed 2/13/2020)


IMPROVEMENTS: Inclusion of the SweetAlert2 JavaScript framework for displaying custom dialogs. It is worth noting that Internet Explorer 9 and 10 are not supported by SweetAlert2. So if users are using IE 9 or 10, the SweetAlert dialogs will not be displayed for them.

CHANGE: To wean users off of using Internet Explorer 9 and 10, any users using IE 9 or 10 will see a thin, yellow banner at the top of all project pages, which will inform them that their browser is not fully compatible with REDCap and thus will encourage them to upgrade to IE11 or use another browser. Technically, IE 9 and 10 will be supported till July 2020 in Standard Release, but this warning is mostly preemptive in preparation for that.

Version 9.7.2 - (installed 2/10/2020)


CHANGE: When viewing reports, it now displays "report execution time" in seconds near the top of the report. This denotes the total server execution time that it took to create the report. Note: This does not account for the rendering time of the report (i.e., via JavaScript), which can sometimes take several seconds or more (if the report is large) for a user's web browser to actually render the report's HTML on the page.

Version 9.7.1 - (installed 2/10/2020)


CHANGE: In the Online Designer's Edit Field dialog, the text area boxes (field label, field choices, and action tags) are now slightly bigger and are all resizable.

Version 9.7.0 - (installed 2/10/2020)


NEW FEATURE: REDCap-branded URL Shortener (

  • The “Get short survey link” and “Create custom survey link” buttons on a project’s Public Survey Link page now utilize the REDCap-branded URL Shortener ( instead of BIT.LY and IS.GD, which are third-party websites utilized by previous versions.
  • For administrators, a new “URL Shortener” link on the Control Center’s left-hand menu will take you to the “All-Purpose REDCap URL Shortener” page, which allows an admin to take *any* URL and shorten it as a custom URL. We ask that you please try to limit the usage of this feature to only REDCap-related and work-related things.
  • NOTICE: Since this feature is ultimately supported by Vanderbilt, which pays for the hosting and infrastructure on AWS, it is a requirement that the REDCap server must have reported its REDCap stats to the consortium first in order to be able to use the REDCap URL Shortener. If the server’s REDCap stats have never been submitted, then the feature will return an error when attempting to create a URL and will note this requirement in the error message.
  • To disable this feature and revert back to using BIT.LY and IS.GD for URL shortening for public survey links, you can run the following SQL query on your REDCap database: UPDATE redcap_config SET value = '0' WHERE field_name = 'enable_url_shortener_redcap';

IMPROVEMENTS: By popular demand, the "Send test email" link/feature has been re-added to all the following places where emails are composed: Email Users page in the Control Center, Automated Survey Invitations setup dialog, Compose Survey Invitations dialog for Participant List, Compose Survey Invitation dialog at the top right of data entry form, and the Confirmation Email setting on the Survey Settings page.

CHANGE: In a production project where repeating instruments/events are enabled, if a user opens the Repeating Instrument/Event setup dialog on the Project Setup page, in which one or more checkboxes are checked already in the setup, a warning dialog with red text will be displayed to inform the user that unchecking any of the checkboxes might cause data to be orphaned and thus will cause any data already collected from repeating instances to disappear indefinitely from the user interface, reports, and exports. This warning will help users to be aware of this possibility that might affect their data and thus might have otherwise caused confusion.

Version 9.6.5 - (installed 2/10/2020)


IMPROVEMENT: Adaptive and Auto-scoring instruments (i.e., PROMIS assessments) that have been downloaded from the REDCap Shared Library may now have their survey responses deleted via the Delete button at the bottom of the data entry form when viewing the survey response. In previous versions, if an Adaptive and Auto-scoring instrument had been partially completed or the wrong one had been taking accidentally, there was no way to remove the existing response since the whole response was locked afterward. Now the "Delete data for THIS FORM only" button appears at the bottom to allow users to remove the response if they wish to add another to replace it.

Version 9.6.4 - (installed 2/10/2020)


IMPROVEMENT: If the "email notifications for administrators" option is enabled on the To-Do List page, then when a user cancels a "move project to production" request or a "delete production project" request, it now sends an email notification to the REDCap administrator to inform the admin that the request was cancelled so that the admin does not attempt to process it (even though the admin will be prevented with an error message if they try to process it). In previous versions, the request would have been cancelled silently by the user without ever notifying the admin.

Version 9.6.3 - (installed 1/23/2020)


IMPROVEMENT: The text box fields for logic have been increased in size and made resizable for the following places: the Survey Queue setup popup in the Online Designer, the Add/Edit Branching Logic popup in the Online Designer, and the Advanced Filter Logic when creating/editing reports.

Version 9.6.2 - (installed 1/23/2020)


IMPROVEMENT: New options for Alerts & Notifications

  • A “Trigger Limit” setting was added to Step 1 in the Add/Edit Alert popup that allows users to define where and to what extent within a record that the alert will be triggered. Its options include “only once per record”, “only once per event”, “only once per instrument regardless of the event”, and others that are displayed if the project contains repeating instruments/events. The trigger limit will help users to limit alerts to only be triggered on certain parts of a record and/or so many times within a record to achieve the behavior they desire for their notifications. Note: For non-longitudinal projects that do not have repeating instruments, this option (Step 1C) will not be displayed at all since it would contain only one choice: “only once per record”. (Ticket #70860).
  • The “every time” option of the “Send it how many times?” setting in Step 2 has been expanded to have sub-options to provide more possible scenarios in which an alert will be triggered. In previous versions, the only option was to set an alert to be triggered “every time the form/survey in Step 1B is saved”, but now it contains two new variations: “every time the form/survey in Step 1B is saved with new or modified data” and “every time the form/survey in Step 1B is saved with new or modified data (ignoring calc fields)”.
  • Recurrence maximum - When setting an alert to send multiple times in a recurring fashion in Step 2, a new option has been added to limit the maximum number of recurrences (i.e., the total times the alert will be sent on its repeated schedule). In previous versions, the alert would continue sending indefinitely at its defined interval (typically until conditional logic became no longer true), but now the alert can be set to repeat up to 9999 times at the interval that has been defined.

IMPROVEMENT: If the Custom Record Label and/or Secondary Unique Field are being used in a project, their values will now be displayed on the Calendar page when viewing the Day or Agenda tab for any calendar event connected to a record in the project.

IMPROVEMENT: On the Alerts & Notifications page, users may now edit a deactivated alert. This is especially useful if a user is setting up part of an alert and wishes to make incremental edits to the alert prior to re-enabling it.

IMPROVEMENT: A new setting "Utilize the Display Name in all outgoing emails?" was added to the "Configuration for Outgoing Emails" section on the Control Center's "General Configuration" page. This setting allows administrators to disable the email Display Name feature in all outgoing emails from REDCap. This feature might need to be disabled if your institution is having a disproportionate amount of emails not being received due to email servers blocking them, sometimes due to the usage of the display name. This setting is enabled by default when upgrading or installing REDCap.

IMPROVEMENT: On the Clinical Data Interoperability Services (CDIS) page in the Control Center, a new helper popup was added to assist admins in quickly determining their EHR's "Patient Identifier String". A new button "Find patient identifier string" will appear on the page, and after clicking it, it will ask the administrator to enter the Social Security Number of any patient in the EHR system, which will return a list of all patient identifier strings that are available in the EHR. After finding the identifier string that corresponds to MRNs in the EHR system, that string can then be pasted and saved on that page so that the Clinical Data Mart and Clinical Data Pull services can begin functioning fully.

Version 9.6.1 - (installed 1/18/2020)


Version 9.6.0 - (installed 1/18/2020)


NEW FEATURE: SMS and Voice Calls for Alerts & Notifications

  • If Twilio services have not been disabled at the system level for the REDCap installation, then users may now send a notification as an SMS text message and/or as a one-way voice call for any given alert in a project by setting them up on the Alerts & Notifications page.
  • The Twilio telephony services must first be enabled on the project on the Project Setup page (the same way it has in the past when utilizing Twilio for surveys and survey invitations), and once enabled, using the Twilio configuration dialog users may choose to utilize Twilio in the project for surveys (default), alerts, or both surveys and alerts.
  • Once enabled for alerts, inside the Add/Edit Alert dialog on the Alerts & Notifications page users will see the options to send a notification as an email, SMS message, or voice call. If SMS or voice call is chosen, it will hide all email-specific settings and will reveal the “Phone Number” fields for entering the phone numbers of one or more recipients of the notification, which may include the following: the phone numbers of all project users (from their My Profile account settings), any fields having integer validation or phone validation, and the survey participant’s phone number (if also using Twilio services for surveys).
  • Note: Just as when SMS messages are sent and when voice calls are made via Twilio for surveys, REDCap has a cron job that runs every 2 minutes that will automatically delete all logs on the Twilio website for any SMS messages sent or voice calls made via Alerts & Notifications. This is for privacy reasons to remove any potentially sensitive information (e.g., recipient phone numbers) that might be stored in Twilio’s logs.
  • New system-level settings for Alerts & Notifications have been added to the “Modules/Services Configuration” page in the Control Center that allow REDCap administrators to disable the phone-related settings listed below (similar to the ones that currently exist regarding email address usage in alerts). Note: These settings are enabled by default when upgrading to 9.6.0 or higher or when installing REDCap.
    • Option: “Allow normal users to use project variables for phone fields and integer fields in the project for an alert's recipient phone numbers?
    • Option: “Allow normal users to manually enter email addresses as freeform text for an alert's recipient phone numbers?”

IMPROVEMENT: Added four new redcap_log_event database tables for new projects to improve server performance when REDCap is querying logging data for a project. Note: This will not improve performance when querying the logging records of existing projects but only applies to projects created after upgrading to v9.6.0 or higher.

IMPROVEMENT: To protect the performance of the REDCap server, safeguards have been added to prevent users from running more than five Data Quality rules simultaneously for a given project. If this is detected, REDCap will automatically kill all but the newest five Data Quality rule requests that are still running and will display an error message on the page explaining this.

Version 9.5.3 - (installed 1/4/2020)


IMPROVEMENT: New content was added to the "Help & FAQ" page

Version 9.5.2 - (installed 1/4/2020)


NEW FEATURE: Built-in activation process for external modules (system-level setting - enabled by default) All modules that have been set as “Discoverable” in the system will now have a “Request Activation” button displayed next to them when viewing the list of available modules on the External Modules page in a project. If a user with Project Setup/Design privileges in the project clicks the button, it will add a new item to the To-Do List in the Control Center (and also send an email to the REDCap administrator if admin email notifications are enabled) that will ask the admin to activate the module. Once the admin has activated the module for the user, the user will receive an email informing them that the module has been activated for the project. Note: This option can be disabled to hide this button for all discoverable modules (e.g., if you wish to use your own module activation process) at the top of the “Modules/Services Configuration” page in the Control Center.

NEW FEATURE: Users can self-activate an external module for a project. This will allow any user with Project Setup/Design privileges in a project to activate the module in their project on their own (i.e., without an administrator having to enable it for them).

CHANGES WHEN EXPORTING DATA FROM REDCap INTO SAS: Full integration of the Missing Data Code functionality in the SAS data export syntax file to prevent issues when loading data containing Missing Data Codes into SAS. Note: The SAS Pathway Mapper file has been removed and is no longer utilized. Users exporting data to SAS will now need to manually modify the path of the CSV data file in their .SAS syntax file to reflect its locally saved path on the device.

Version 9.5.1 - (installed 12/15/2019)


Version 9.5.0 - (installed 12/8/2019)


NEW ACTION TAG: @HIDDEN-PDF - Hides the field only in the downloaded PDF of one or more instruments (including blank PDFs, PDFs with data, and compact PDFs with data). Note: Other @HIDDEN action tags will not hide fields inside PDF exports, so @HIDDEN-PDF must be used specifically to hide fields in PDFs.

IMPROVEMENT: More rich text editors - The rich text editor is now available when composing survey invitations. This includes composing Automated Survey Invitations or invitations to be sent via the Participant List or via the Survey Options on data entry forms.Improvement: The rich text editor is now available on the Email Users page in the Control Center and also for the Survey Confirmation Email option on the Survey Settings page.

Version 9.4.2 - (installed 11/26/2019)


IMPROVEMENT: Line breaks may be preserved in data values in CSV data exports - When creating/editing a report, the section "Additional report options" contains a new setting: "Remove line breaks/carriage returns in all text data values (only applicable for CSV Raw and CSV Label data exports)". This setting will be enabled by default for all existing reports and for any new reports being created. The option will effectively not be enabled when exporting Reports A and B in order to be consistent with their current behavior in previous versions. This option is only used for CSV data exports and not for reports or exports to statistical analysis packages.

IMPROVEMENT: Added “Copy” and “Paste” options to the [right-click] context menu for all rich text editors.

Version 9.4.1 - (installed 11/16/2019)


IMPROVEMENT: A custom email “display name” can be set for the email sender when sending an email for Alerts & Notifications, the Survey Email Confirmation option on the Survey Settings page, and when sending survey invitations via Automated Survey Invitations, via the Participant List, or via the Compose Invitation option on a data entry form.

IMPROVEMENT: The email “display name” for most outgoing emails is now automatically populated and thus is able to be displayed in the recipient’s email client. Previous versions did not use the display name but left it blank for outgoing emails. For user requests that are triggered by users, such as production change requests, API token requests, etc., the user’s first and last name from their My Profile page will be used automatically as the display name in those emails. For emails originating from REDCap administrators that are automated by the system, the email display name will the “Name of REDCap Administrator” setting (from the General Configuration page) or else the “Contact name to display on Home page” (from the Home Page Configuration page), which is dependent upon the type of email being sent.

IMPROVEMENT: New system-level setting “Suppress usage of the Universal FROM Email address for specified email domains” on the General Configuration page - If the setting “Universal FROM Email address” is enabled for the system, then the Universal FROM Email address will be used for all outgoing emails. But if one or more domain names (e.g., are specified for “Suppress usage of the Universal FROM Email address for specified email domains”, then the Universal FROM Email address will NOT be used for any outgoing emails in which the FROM/sender's email address matches one of those domains. Instead the FROM/sender's email address will remain as-is.

IMPROVEMENT: The module/plugin method REDCap::email now has new parameters that can be passed to it: BCC, FromName, and Attachments. The parameter BCC represents the email address of someone being BCC'd on the email (if using more than one email address, they must be separated by commas and/or semicolons). The parameter FromName represents the sender's email display name that will be displayed in the recipient's email client next to the sender's email address (e.g., "Rob Taylor"). And the parameter Attachments should be an array of one or more file attachments, in which the array keys will represent the file name as seen in the email client and the corresponding array values will represent the full file path of the attachment file on the REDCap server. A new example is provided on the "Developer methods for Plugins, Hooks, & External Modules" page to illustrate how to use these new parameters.

CHANGE: The popup for displaying Project Notes on the My Projects page might not behave correctly under certain conditions. It is now displayed in a better format to avoid these issues.

Version 9.4.0 - (installed 11/12/2019)


NEW FEATURE: Missing Data Codes (i.e., “Data Missingness” functionality) (project-level setting)

  • Fields that have a blank/missing value may be marked with a custom 'Missing Data Code' to note why the value is blank. These missing codes may be used to aid in data analysis by specifying why a field lacks a value. Users may enable custom missing data codes at the project-level in the Additional Customizations popup on the Project Setup page. The missing codes should be coded just like the choices of a multiple choice field with code + comma + label, in which the codes can only have letters, numbers, dots, dashes, and underscores (e.g., '-999, Not asked' or 'UNK, Unknown'). If no codes are entered, this feature will remain disabled. After missing data codes have been set up in a project, you will see an 'M' icon next to each field when viewing a data entry form. Click the icon to open your list of missing data codes, and select one. Once selected, it will save the missing code as the literal data value for the field. Missing data codes can be used for any field type (e.g., date, slider, file upload fields).
  • If utilizing missing data codes, the functionality will be enabled on all fields by default, and the code will be saved as the literal data value for the field.
  • New action tag @NOMISSING can disable the missing data option for a given field
  • Behavior with branching logic – If a field should be hidden by branching logic, REDCap will ask the user (except on surveys) if they wish to delete the value of the field being hidden. But if the field has a missing data code saved for it, it will still hide the field but will not remove the missing data code as the field’s value. This allows a field to still be “blank” and have a missing code while being hidden by branching logic.
  • New isblankormissingcode() function for branching logic, logic, and calculations - Returns a boolean (true or false) if the field value is blank/null/"" or if the value is a Missing Data Code, in which Missing Data Codes have been explicitly defined in the project on the Project Setup page under Additional Customizations. E.g. isblankormissingcode([age]), in which if "age" has a value of "UNK" (which might be a Missing Data Code in a project), then it will return TRUE. And if the field has any non-blank/non-null value that is also not a Missing Data Code, it will return FALSE.
  • Missing data codes can be imported via API, Data Import Tool, or REDCap::saveData (for plugins/hooks/modules)
  • All the missing data codes are displayed for reference at the top of the Codebook page
  • When creating/editing a report, a new option exists under the “Addition report options” section: “Display any Missing Data Codes in place of blank values (where applicable)”. This option will allow users (based on their preference) to show or not show the Missing Data Codes (if they have been saved for any field in any record) in the report or export.Note: In PDF exports of data collection instruments, any Missing Data Codes will be represented as blank values in the PDF.
  • Changes for Data Quality Rules
    • DQ rule A and B (for finding blank values) will continue to return only truly blank values and thus will not return fields with missing data codes saved as the value.
    • New rule - DQ “Rule I (Fields containing missing data codes)” has been added as a new rule for specifically finding fields with missing data codes saved as the value.
    • DQ rule F (Hidden fields that contain values) will ignore fields that have a missing data code saved as the value because it is allowable for such fields to be hidden by branching logic while still maintaining a missing data code as a value.

IMPROVEMENT: If the Clinical Data Mart has been enabled for the system, the Control Center's System Statistics page now lists the following stats related to Data Mart under the "Modules Utilized" section: 1) Records with data values imported via Data Mart, and 2) Projects with data values imported via Data Mart.

IMPROVEMENT/ CHANGE: If a user is viewing a data entry form that has been enabled as a survey and then clicks "Compose survey invitation" in the survey options at the top right of the page, if they compose and send an invitation that is marked to be sent "Immediately", it will display a popup to inform the user that it is recommended that they leave the page very soon before the respondent has a chance to enter any data on the survey page. This is done because if the respondent begins entering data on the survey immediately after receiving the invitation, and then the user (while still viewing the data entry form) saves the form, the user could unwittingly erase the respondent's data values that were just entered.

CHANGE: When enabling the Twilio telephony services in a project, REDCap no longer performs a check to ensure that Twilio's "Request Inspector" feature is disabled. Due to technical issues with not being able to automatically disable the Request Inspector via Twilio's API for some REDCap server configurations, REDCap no longer forces the Request Inspector to be disabled but instead provides text to inform users during the Twilio setup process that it is *highly* recommended that they disable the Request Inspector manually in their Twilio account (especially if collecting identifying information) and provides information on where/how to do such.

CHANGE: REDCap now utilizes PHPMailer for all emails sent out.

IMPROVEMENT/ CHANGE: If the Universal “From” Email Address option is being utilized for the system, the sender’s email address now gets set as the Display Name in the email received. In previous versions, no Display Name is ever set for outgoing emails. So instead of the recipient only seeing that the sender is (assuming this to be the catch-all universal address, for example), it instead will appear to be from “ . This is an improvement because it provides the recipient with more context with regard to who the sender>

Version 9.3.8 - (installed 11/4/2019)


Version 9.3.7 - (installed 10/28/2019)

IMPROVEMENT: Major performance improvement when loading the Participant List page for projects with surveys. For projects with thousands of records or more, this page should be significantly faster.

IMPROVEMENT: Performance improvement for record searching on the "Add/Edit Records" page when entering part of a record name in the "Enter a new or existing [Record ID]" text box. For projects with thousands of records or more, this functionality should be much faster.

IMPROVEMENT: Performance improvement for projects using record auto-numbering, in which the process of generating the record name of the next potential record is much faster, especially for projects with many records.

CHANGE: Performance improvement for projects using record auto-numbering, in which the process of generating the record name of the next potential record is much faster, especially for projects with many records.

Version 9.3.6 - (installed 10/21/2019)

IMPROVEMENT: Performance improvement for large data exports that might have previously taxed the REDCap servers or might have failed to complete altogether for some large projects. An internal auto-batching mechanism is now utilized to limit the performance hit to the servers (both database and web server) when exporting large quantities of data (via API or user interface) in order to improve the user experience and to prevent REDCap processes from using up too many server resources. Note: This does not necessarily mean that data exports will be faster; in fact, some exports might be slightly slower as a means of preserving server resources used by REDCap processes.

IMPROVEMENT: Performance improvement for when REDCap is generating the record list cache for a project, especially for projects with Data Access Groups. For each project, REDCap maintains a record list in a database table that is used throughout a project. This record list improves overall performance, especially for large projects. Every few days the record list cache is automatically rebuilt internally. The process of rebuilding the record list is now more efficient, faster, and less error-prone than in previous versions.

IMPROVEMENT/CHANGE: The Codebook now denotes if an instrument is enabled as a survey, in which it is noted immediately to the right of the instrument name.

Version 9.3.5 - (installed 10/4/2019)


Version 9.3.4 - (installed 9/26/2019)


Version 9.3.3 - (installed 9/11/2019)