REDCap Change Log

This page documents all changes to REDCap from version to version and provides a list of changes, improvements, and added features for each version of REDCap that is released.

REDCap v10.3.5
New Features
  • New feature: Added "Language of text to be spoken" for the "Text-To-Speech" survey functionality, which is available on the Survey Settings page.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.
Improvements
  • 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.
  • Security improvement: The concept of “public projects” have been removed and thus the My Projects page will no longer display the list of public projects at the bottom of the page. 
  • 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: Import Records API method has a new parameter “csvDelimiter” to specify the delimiter character when sending data in CSV format. Options include: comma ',' (default), 'tab', semi-colon ';', pipe '|', or caret '^'.
  • 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.
REDCap v10.2.3
 
New feature: Integration of Paul Litwin's Stealth Queue external module
  • 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.
 
Improvements to the 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.

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. 
 
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.

REDCap v10.1.5

  • 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.
  • New feature: Granular administrator privileges - There now exist seven different categories of privileges that may be attributed to a REDCap administrator. If a user has at least one admin privilege, they are considered a REDCap administrator and thus will be able to access the Control Center; however, they will only be able to access the things to which they have been granted access. Note: Following the upgrade to v10.1.0, any users who were designated as REDCap administrators beforehand will now have all seven categories enabled. Thus they will not lose any privileges at all after the upgrade. Listed below are each of the admin privilege categories and an explanation of what they mean and where they apply.
  • 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.

REDCap v10.0.3

  • Change: To be more inclusive in our community, all references to the terms “blacklist” and “whitelist” have been replaced with “blocklist” and “allowlist”, respectively, in the REDCap user interface, the REDCap code, and in all database table names and columns.

REDCap v10.0

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).

Improvement: “My Projects Tweaks” External Module - Improvements for the My Projects page

  • Adds project PIDs (for REDCap Admins only): Adds a new PID column (in between Project Title and Records). The PIDs are links that lead to the Edit Project's Settings 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.

REDCap v9.9.2

  • Improvement: 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.
  • Improvement/change: A new "Clear the Record List Cache" button has been added to the Other Functionality page in a project, in which this button is only available to administrators to use. If there appear to be records missing from the project (in reports, record status dashboards, or elsewhere), then the Record List Cache (a secondary list of all record names) might be out of sync and thus might need to be cleared. Clearing the cache will cause the Record List Cache to regenerate and bring back records that appear to be orphaned/missing in the project. Clicking this button will clear the cache and fix the record list. NOTE: This is normally not needed, but there have been instances in which unknown factors caused the Record List Cache to get out of sync, which could cause major problems for some projects.
  • Improvement: A new field “Preferred language” has been added to projects that are created as Clinical Data Mart projects. This field will serve as the location where a patient’s preferred language will be imported as freeform text (e.g., “English”) from the EHR. If a Data Mart project was created in an earlier version of REDCap, this field can simply be added after the fact by adding the variable name “preferred_language” as a Text field with no field validation on the Demography data collection instrument.
  • Improvement/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).
  • Changes for long-standing quirks with calc fields and branching logic
    • Change: 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).
    • Change: 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.
    • Change/improvement: 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.

REDCap v9.9.0 to v9.9.1

  • New feature: DAG Switcher
    • 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.
  • Improvement/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.
  • Improvement/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.
  • Improvement: 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.).

REDCap v9.8.1 to v9.8.4

  • Various security fixes
  • Various bug fixes

REDCap v9.8.0

Project life cycle changes

  • 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.
  • 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.
  • 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: 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.

Below are the visuals of the project life cycle found under the “Other Functionality” tab.

Project Ownership External Module

A REDCap module to aid in the collection and management of project ownership details. This module collects project ownership data at project creation, requires PI contact details on research projects, and provides interfaces to search, display and edit ownership details.

The project ownership details are collected on the project creation page. Three fields are required: first name, last name and email. Alternatively, the user can set a REDCap username, so the required information is pulled from that user account.

Ownership auto assign

Users may click on the "I am the owner" link to auto-assign the ownership.

Autocomplete from PI information

If the purpose of the project is "Research", the ownership fields are auto-completed as the PI information is filled out.

Autocomplete PI information

The PI information can also be automatically filled in when the "I am the owner" link to auto-assign the ownership is clicked.

Checking and updating project ownership

The same field set from the project creation page may be seen at project settings modal - where users are able to check and update ownership information.

Projects ownership list

A list of project ownership is accessible to users at My Projects page.



REDCap v9.7.8

  • Various security fixes
  • Various bug fixes

REDCap v9.7.4 to v9.7.7

  • Various security fixes
  • Various bug fixes

REDCap v9.7.3

  • Change/improvement: Inclusion of the SweetAlert2 JavaScript framework for displaying custom dialogs.
  • 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.
  • Various security fixes
  • Various bug fixes

REDCap v9.7.0 to v9.7.2

  • Various security fixes
  • Various bug fixes

REDCap 9.7.0

  • New feature: REDCap-branded URL Shortener (https://redcap.link)
    • 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 (https://redcap.link) 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 redcap.link URL. We ask that you please try to limit the usage of this feature to only REDCap-related and work-related things.
  • Change/improvement: 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.
  • Major bug fix: Most non-project types of actions by users were mistakenly not being logged in REDCap due to a query that failed when inserting a new row into the redcap_log_event database table. All project-level logging was correctly being logged, but non-project activities (such as creating users, resetting passwords, etc.) were mistakenly not getting logged. Bug emerged in REDCap 9.6.0 Standard. (Ticket #77584)

REDCap v9.6.3 to v9.6.5

  • Various security fixes.
  • Various bug fixes

REDCap v9.6.2

  • 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”.
  • 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/change: 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.
  • Various security fixes.
  • Various bug fixes.

REDCap v9.6.1

  • Major bug fix: If the Twilio telephony feature has been disabled at the system level on the Modules/Services Configuration page in the Control Center, then when adding/editing an alert on the Alerts & Notifications page in a project, the "Email From", "Email To", and "Subject" settings would mistakenly not be displayed and thus would prevent users from creating or editing an alert.
  • Various security fixes.
  • Various bug fixes.

REDCap v9.6.0

  • 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?”
  • Various security fixes.
  • Various bug fixes.

REDCap v9.5.3

  • Bug Fixes

REDCap v9.5.2

  • 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 (module level setting - disabled by default)

For any given module that has been enabled in the system and that has also been set as “Discoverable”, a REDCap administrator may optionally set a module setting (in the Configure Module popup for the module in the Control Center) that 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).

Since this is a module-level setting, it is completely opt-in by the REDCap administrator for any given discoverable module.

  • New feature: Standalone Launch for CDP and Data Mart - When using the Clinical Data Pull or Clinical Data Mart functionality, it is no longer required for users to have to log in to the EHR and launch the embedded REDCap window inside the EHR interface as a means of establishing a connection between their REDCap account and the EHR. This is now optional. Users may now alternatively establish a connection with the EHR by logging into to the EHR via a prompt while inside REDCap. If a user in REDCap attempts to pull clinical data from the EHR, in which it determines that the user has not established a connection yet with the EHR, it will prompt them to log into their EHR directly in their web browser, after which it will redirect them back to REDCap to begin pulling the clinical data from the EHR. Thus setting up a REDCap launch button in the EHR interface is no longer required but optional since the connection can now be completely established on the REDCap side alone. NOTE: For those using Epic, this means that creating an FDI Integration Record and Menu Record are no longer mandatory as part of the general CDIS setup process.
  • Various security fixes.
  • Various bug fixes.

REDCap v9.5.1

  • Major bug fix:When clicking the "Remove file" link on a data entry form or survey page when attempting to delete a file or signature for a File Upload field or Signature field, it would mistakenly fail and prevent the user from successfully deleting the file. Bug emerged in v9.5.0.
  •  Various security fixes.
  • Various bug fixes.

REDCap v9.5.0

  • Improvement: 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.
  • Various security fixes.
  • Various bug fixes.

REDCap v9.4.2

  • 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.
  • Various security fixes.
  • Various bug fixes.

REDCap v9.4.1

  • 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.
  • Various security fixes.
  • Various bug fixes.

REDCap v9.4.0

  • New feature: Missing Data Codes (i.e., “Data Missingness” functionality)
  • 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.
  • 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.
  • 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 no-reply@vumc.org (assuming this to be the catch-all universal address, for example), it instead will appear to be from “joe.user@gmail.com <no-reply@vumc.org>. This is an improvement because it provides the recipient with more context with regard to who the sender is.
  • Various security fixes.
  • Various bug fixes.

REDCap v9.3.7

  • 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: The "Data Search" feature on the "Add/Edit Records" page will no longer allow users to search over "All fields" if a project contains more than 20,000 records. This is done for performance reasons so that it does not bog down the database server.
  • Various security fixes.
  • Various bug fixes.

REDCap v9.3.6

  • 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.
  • Various security fixes.
  • Various bug fixes.

REDCap v9.3.5

  • Improvement: If the "File Upload field enhancement: Password verification & automatic external file storage" setting has been enabled in a project, then when a user attempts to delete a file for a File Upload field (including the deletion of older revisions for that field), it will provide a text box in the "Delete file?" popup in order to allow the user to optionally provide a reason for why they are deleting the file (if they wish), after which this reason will be logged on the Logging page.
  • Improvement: The bottom of the "Clinical Data Interoperability Services" page in the Control Center has a new setting "Allow the patient's email address to be imported from the EHR?". It is initially set to "No", but if changed to "Yes", it will display the "email address" field in the field mapping tree for both Clinical Data Pull and Clinical Data Mart, thus allowing users to import a patient's email address into REDCap, if they desire. Previous versions of REDCap did not allow the patient email address to be imported
  • Various security fixes.
  • Various bug fixes.

REDCap v9.3.4

  • Improvement: On the Survey Settings page, the "Redirect to a URL" option now allows the Smart Variable [survey-url] to be used - e.g., [survey-url:other_survey].
  • Change: If the "Name of REDCap Administrator" setting is set to something other than blank/null on the "Edit a Project's Settings" page in the Control Center for a given project, then the blue button on the project's left-hand menu will have the button text as "Contact X" (where X is the name entered) rather than the hard-coded text "Contact REDCap Administrator".
  • Various security fixes.
  • Various bug fixes.

REDCap v9.3.0

  • New feature: File Version History for File Upload fields (project-level setting)
    • This feature allows a new file to be uploaded onto a File Upload field that already has a file uploaded for it. If a file has already been uploaded, the field will have a new link “Upload new version”, and after being clicked, it will allow the user to upload another file without having to delete the existing one. The old/existing file will not be deleted but will still be accessible as an older version of that file in the Data History popup (by clicking the “H” icon next to the field). Within the Data History popup, a user may view, download, or delete any existing version of the file that exists, in which all versions of the file will be displayed in a table format and listed in chronological order with regard to being uploaded.
    • “Import File” API behavior: When the File Version History feature is enabled for a project, and the “Import File” API method is used to import a file into a File Upload field that already has a file saved for it, the new file will overwrite the existing file but keep the existing file in the File Version History, thus not deleting it. This is different for projects that have the File Version History disabled, in which importing a new file will delete the existing file.
    • For all upgrades/installs, this feature will be enabled for the system and for all projects. It may be disabled for all projects by disabling the system-level setting, which is located on the Modules/Services Configuration page in the Control Center. Alternatively, it may be left enabled at the system level, and you may set it so that all new projects (created in the future) will have the feature enabled or disabled, which can be done on the Default Project Settings page in the Control Center. While this feature will be enabled by default for all projects, if you wish to disable it for all existing projects, then you may run the following SQL on the database after the upgrade: UPDATE redcap_projects SET file_upload_versioning_enabled = 0;
  • New feature: File Upload field enhancement: Password verification & automatic external file storage (project-level setting)     
    • This feature allows users to utilize extra functionality regarding the use of File Upload fields 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: Any user that is uploading a file for a File Upload field on a data entry form or survey will be asked to confirm that the file is the correct file. And when on data entry forms specifically, it will additionally ask the user to enter their REDCap password as part of the verification process. Once confirmed, the file will successfully upload, and in addition to saving the file normally in REDCap, it will also store a duplicate copy of the file on a secure, external server using the configuration settings defined in the Control Center.
    • 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.
  • Improvement: The Data History Popup for File Upload fields now provides more detailed information, such as the filename of the uploaded file.
  • Various security fixes.
  • Various bug fixes.

REDCap v9.2.1

  • 10 new Smart Variables
  • [project-id] - The Project ID (i.e., PID) of the current REDCap project.
  • [user-fullname] -The current user's first and last name (as listed on their My Profile page).
  • [user-email] - The current user's primary email address (as listed on their My Profile page).
  • [redcap-base-url] - The base web address for the REDCap installation.
  • [redcap-version] - The current REDCap version number of the REDCap installation.
  • [redcap-version-url] - The base web address of the current REDCap version directory for the REDCap installation.
  • [survey-base-url] - The base web address for surveys for the REDCap installation.
  • [instrument-name] - The unique instrument name of the current survey or data entry form. It will return a blank value if not in an instrument context.
  • [instrument-label] - The instrument label of the current survey or data entry form. It will return a blank value if not in an instrument context.
  • [survey-title] - The survey title of the instrument specified by the 'instrument' parameter (if provided). If the 'instrument' parameter is not provided, the current survey instrument will be used, else it will return a blank value if not in an instrument/survey context.
  • 4 new Action Tags
  • @NOW_SERVER - Loads the REDCap server's date+time into a blank Text field - similar to the @TODAY tag but additionally includes the time portion. If the field has validation, the value will adjust to match the date format. NOTE: The time used will be the REDCap server's local time, which might be different from the user's local time if in another timezone. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field.
  • @TODAY_SERVER - Loads the REDCap server's date into a blank Text field - similar to the @NOW tag but without the time portion. If the field has validation, the value will adjust to match the date format. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field.
  • @NOW_UTC - Loads the current UTC/GMT date+time into a blank Text field - similar to the @TODAY tag but additionally includes the time portion. If the field has validation, the value will adjust to match the date format. NOTE: The time used will be the current UTC/GMT time, which might be different from the user's local time if in another timezone. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field.
  • @TODAY_UTC - Loads the current UTC/GMT date into a blank Text field - similar to the @NOW tag but without the time portion. If the field has validation, the value will adjust to match the date format. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field.
  • Various security fixes.
  • Various bug fixes.

 

REDCap v9.1.2

  • New feature: Rich text editor for field labels and section headers
    • For any field on an instrument in the Online Designer, users may optionally utilize the rich text editor for styling field labels or section headers with many text-formatting options. The rich text editor allows users to change the color of text (including background color), create tables, add text of varying sizes, bullet lists, and more. For any field labels that were originally created without the rich text editor, users may optionally enable the rich text editor for any field by clicking the 'Use the Rich Text Editor' checkbox. It may also be disabled afterward at any time just the same. Rich text is enabled by default for any new fields being created via the Online Designer.
    • Note: The PDF export of surveys/instruments will *not* reflect all the styling of the rich text editor, so keep in mind that line breaks and paragraphs should be represented well in PDFs, but other text-formatting options, such as large text, bullet points, and colors are not able to be translated into the PDF export of the instrument. This is a current limitation in REDCap.
  • Various security fixes.
  • Various bug fixes.

 

REDCap v9.0 through v9.0.1

  • New feature: Alerts & Notifications
  • The Alerts & Notifications feature allows you to construct alerts and send customized email notifications. These notifications may be sent to one or more recipients and can be triggered or scheduled when a form/survey is saved and/or based on conditional logic whenever data is saved or imported. When adding/editing an alert, you will need to 1) set how the alert gets triggered, 2) define when the notification should be sent (including how many times), and 3) specify the recipient, sender, message text, and other settings for the notification. For the message, you may utilize customized options such as rich text, the piping of field variables (including Smart Variables), and uploading multiple file attachments. While similar in many respects to Automated Survey Invitations, Alerts & Notifications allow for greater complexity and have more capabilities. For example, alerts apply to both data entry forms and surveys, and they also allow for more options regarding who can be the recipient of a notification (project users, survey participants, etc.).
  • Converting existing Email Alerts into Alerts & Notifications – If your REDCap installation currently has the Email Alerts external module installed and is being used in projects, there will be an option (a green button) at the top left of the Email Alerts configuration page to convert all the Email Alerts in a given project into Alerts & Notifications. This is an opt-in setting, and must be done for each project one at a time. It will present a dialog popup with information so that the user understands that there are some differences between EA and A&N, but overall, everything will be able to be converted, although the alerts might look slightly different afterward as A&N’s. Once the Email Alerts are converted, the Email Alerts module will be automatically disabled for the project, and the user will be redirected to the A&N page. Note: The conversion instructions notes that if (for whatever reason) the A&N’s are not behaving like the user anticipated, they can easily revert back to using Email Alerts again by 1) deactivating all the A&N’s that were created from the conversion, and 2) have an administrator re-enable the Email Alerts module.
  • Improvement: The rich text editors on the Survey Settings page have now been updated to a newer version of the TinyMCE package. (Note: IE9 and IE10 will still use the older version of the rich text editor because they are not compatible with the newer one.)
  • Improvement: New records can now be created directly from the Record Status Dashboard. If record auto-numbering is enabled, it will display an “Add new record” button, otherwise it will display a text field for users to enter a new record name to create.
  • Improvement: Links to the Online Designer, Data Dictionary Upload page, and Codebook were added to the left-hand project menu for easier navigation. Also, a new section “Project Home and Design” was added on the left-hand menu to contain all these links, as well as the Project Home and Project Setup page links.
  • Change: The Quick Tasks box on the Project Home page was removed since all the pages listed inside it are now located on the left-hand project menu, thus making the Quick Tasks box redundant.
  • Change: Replaced many of the older icons in the user interface with Font Awesome icons, especially on the left-hand project menu and left-hand Control Center menu.
  • Various security fixes.
  • Various bug fixes.

 

REDCap v8.11

  • New feature: The "Sticky Matrix Header" external module was integrated into REDCap. This feature will cause matrix headers to float and stick to the top of a page on either a survey or data entry form so that the matrix headers are always visible, which is helpful for matrices with many rows.
  • New feature: The "REDCaptcha" external module was integrated into REDCap
    • This feature allows users to utilize the Google reCAPTCHA functionality to help protect public surveys from abuse from “bots”, which are automated software programs that might enter trash data into surveys. Users will be able to choose to enable the Google reCAPTCHA functionality on the Public Survey page in their project, after which the public survey will display the reCAPTCHA checkbox and “I’m not a robot” text on a survey page prior to allowing the participant to view the public survey. This feature is not employed on any private survey links because those are unique to a record and thus would never be made publicly available like a public survey link would.
    • Note: A survey participant will never have to pass the reCAPTCHA test more than once per day on a given device/computer.
    • Additional note: If this external module was already enabled on the REDCap installation, it will NOT automatically be disabled during the upgrade process. Thus you may consider disabling the module after the upgrade if you wish the utilize this new integrated feature.
  • New feature: The "Codebook Concertina" external module was integrated into REDCap. This feature will display Expand and Collapse buttons for each instrument listed on the Codebook page in a project. If this external module was already enabled on the REDCap installation, it will automatically be disabled during the upgrade process to prevent any possible conflicts.
  • Improvement: When enabling an instrument as a survey or editing an existing survey's survey settings, it now displays a "Save Changes" button at the top of the page (next to the Cancel button) so that the user does not necessarily have to scroll all the way to the bottom to submit the page.
  • Change/improvement: When viewing a survey response on a data entry form that had been completed using the E-consent Framework, users with Record Locking privileges will now be able to Lock and E-sign the instrument. Previously in all versions of REDCap version 8.10.X, the entire instrument was read-only, including the Locking and E-signature options.
  • Change/improvement: The Custom Record Label and Secondary Unique Field values are now displayed with the record name in the table on the "PDF Survey Archive" tab in the File Repository if the "PDF Auto-Archiver" is enabled for one or more surveys in a project. In previous versions, it did not display them next to the record name.
  • Change: For projects in production, the settings on the Record Locking Customization page can now be edited by any user that has "Record Locking Customization" privileges in the project. In previous versions, only REDCap administrators could modify this page's settings while in production.
  • Change/improvement: In the popup dialog for moving a project to production, it now displays the number of records in the project to help the user decide if they wish to keep all data or have all records deleted when moving to production.

  • Change/improvement: When using the e-Consent Framework, a new option was added to the Survey Settings page: "Allow e-Consent responses to be edited by users?". If left unchecked (default), then users will not be able to edit a completed e-Consent response (although it can be locked or e-signed by a user with locking/e-signature privileges). If the setting is checked, then users will be able to modify the survey response so long as they have "Edit survey responses" privileges for that survey instrument. Note: If the e-Consent survey response is modified after being completed, this will not affect the e-Consent PDF file that was stored in the File Repository.
  • Improvement: When copying a project, there are now separate options for copying users and/or user roles. In previous versions, these were combined as a single choice "Copy users and roles", but now users may decide to copy one or the other.
  • Change: Added a link to the Codebook page on the Data Import Tool instructions to allow users to more easily find the raw coded values for multiple choices fields that they wish to import.
  • Change: When a user clicks the "Help & FAQ" link on a project's left-hand menu, it will now load the "Help & FAQ" page in a new window to prevent the user from losing their current page context in the project as they view the "Help & FAQ" page.
  • Various security fixes.
  • Various bug fixes.

REDCap v8.10

  • New feature: Many project components added to the Project XML file – When downloading the Project XML of metadata or metadata+data on the Project Setup->Other Functionality page, it now provides checkboxes to allow users to incorporate the project components listed below in the XML file. This means that all these things will be easily transferable now when exporting/importing the Project XML to create a new project on the same REDCap server or on a different REDCap server. Note: The server on which a project is being created using a Project XML file must also be on REDCap 8.10.0 or higher in order for these components to be added, otherwise it will simply ignore these components when creating the new project.
  • Data Access Groups (including DAG assignments for records if data is included in the XML file)
  • Data Quality Rules
  • User Roles
  • Surveys and survey settings (including a survey logo, if used)
  • Automated Survey Invitations
  • Survey Queue
  • Reports
  • Report Folders
  • Record Status Dashboards
  • DDP Field Mappings (for DDP Custom and DDP on FHIR) – administrator must still enable DDP in the project manually
  • Change: When granting a user access to a project via the User Rights page, in which the "notify user via email" checkbox is checked, it now includes a link directly to the project in the resulting email to the user, whereas previous versions only included a link to the main REDCap home page.
  • Improvement: New options added to Secondary Unique Field functionality - In the "Additional Customizations" popup on the Project Setup page, users may now choose to optionally display the Secondary Unique Field's value in conjunction to displaying a record name on various project pages (in previous versions it was always displayed regardless). If left unchecked, the uniqueness of the value will still be checked during data entry or import, but the Secondary Unique Field's value will not be displayed next to the record name anywhere (e.g., in record lists, record status dashboards, reports). A second option has also been added that dictates whether or not the field label of the Secondary Unique Field will be displayed next to the value (if the value is set to be displayed next to a record name).
  • Improvement: The External Modules Framework now has a new "Update All" button in the Control Center to allow administrators to easily upgrade all their installed modules to the latest version of each module with a single button click.
  • Change/improvement: The "Help & FAQ" page was updated with new content.
  • Change: Dashes/hyphens can now be used as the raw coded value for multiple choice fields. 

REDCap v8.8 through 8.9

  • New feature: Report Folders - Reports can now be organized into folders in any given project. If a user has "Add/Edit Reports" privileges, they will see an "Organize" link on the left-hand project menu above the project’s reports. They will be able to create folders and then assign their reports to a folder, after which the project's reports will be displayed in collapsible groups on the left-hand menu.Improvements related to viewing or creating reports
  • New feature: “Edit Access” for reports - In addition to setting "View Access" when creating or editing a report, users can now set the report's "Edit Access" (under Step 1) to control who in the project can edit, copy, or delete the report. This setting will be very useful if one wishes to prevent certain users from modifying or deleting particular reports.
  • New feature: Report search - A new search feature exists on the left-hand menu to allow users to search within the title of that project’s reports to help them navigate to a report very quickly.
  • Change: Changed the text "Manage Survey Participants" to "Survey Distribution Tools", which more clearly describes the pages in that section.
  • Change: Users that do not have "Project Design and Setup" privileges will no longer be able to navigate to or view the Project Setup page in a given project. Since such users cannot effectively perform any actions on the Project Setup page (i.e., everything on the page is disabled), it does not make much sense for them to be able to access it at all. 
  • Change: On the "Add/Edit Records" page for projects in development status, the notice that real data should not be entered into a project while in development has been moved more to the top of the page to make it more prominent as a reminder to users.
  • Improvement: When copying a project, a new checkbox has been added to the Copy Project page to copy "all report folders". In the previous version, it would always copy all reports and report folders if the "all reports" option was checked, but now it allows reports to be copied without copying report folders, if need be.
  • Change/improvement: When importing data via the Data Import Tool, if a CSV data file is re-uploaded on the second page after the initial attempt (e.g., due to errors displayed after the first attempt), it now hides all the error messages on the page after clicking the Upload File button to re-upload the file. Thus it resets the page so that the user does not get confused thinking that the previous errors apply to the current upload if the re-upload process takes a while.
  • Change/improvement: When importing data via the Data Import Tool and an error is detected in the data file, the header text of the error message has been changed slightly to prevent confusion so that users more clearly understand that the file was not fully uploaded.
  • Improvement: A new search utility was added to the top of the “Help & FAQ” page to make finding keywords easier on the page. It allows for multiple word matches and also “exact phrase” matching. When performing the search, all matching questions/answers will be displayed on the page with the keywords being highlighted while non-matching questions/answers will be hidden on the page.
  • Improvement: A new "Filter by event" option was added to the Logging page: "Record deleted (only)". This allows users to display only the logged events in which a record was deleted in the project.
  • Change: Data Quality rules A and B have always ignored checkbox fields. But since a checkbox field can be set as "required", in which it produces an error message if no checkbox option is checked, then DQ rule A and B appear to be inconsistent with regard to whether a checkbox field can truly be empty/blank. To make these consistent when interpreting the missingness of checkbox fields, DQ rules A and B will no longer ignore checkboxes but will return discrepancies for a checkbox if it has no options checked.
  • Various security fixes.
  • Various bug fixes.

REDCap v8.5 through 8.7

  • Improvements related to viewing or creating reports
    • New report option that will combine checkbox options into a single column of only the checked-off options. Previously, any checkbox fields in a report would have their choices represented as separate columns in the report, but with this new setting, they can now all be represented as a single column with comma-delimited values and comma-delimited labels. Note: If data is exported to a stats package on a report using this option, checkbox fields will be represented as text fields in the stats package’s syntax file that gets generated by REDCap.
    • Report description – Users may now optionally set a description for a report, in which the description gets displayed as text below the report title on the report page. This allows users to provide instructions or explanatory text for the report. Note: HTML may be used in the description to add links or to style the text.
    • Change: When exporting a report, it now includes the report’s title as part of the resulting export files’ file name. This should make it easier to distinguish different exported data sets if a user is exporting several reports for a given project.
    • Improvement/bug fix: In previous versions it was very difficult (and sometimes impossible) to create reports with lots of fields in projects that contained >1000 total fields. In some cases, it would cause the Create Report page to be very sluggish or even to crash in some cases. This should no longer happen, and users should be able to easily create reports with thousands of fields, if they wish, with no problem.
  • Improvement: Performance boost – Certain pages in projects with thousands or more records should now load much faster in most cases. This includes the Record Status Dashboard, various pages utilizing Data Access Groups, and certain reports. Reports A and B should especially see significantly faster loading (excluding when viewing “all” pages in report A or B).
  • Change: When exporting a data dictionary, it will now automatically prepend the Field Annotation column with a single space character if the value begins with an "@" sign. This is to prevent issues when loading the data dictionary into Microsoft Excel, which uses "@" to denote the beginning of an equation. When the data dictionary is re-uploaded back into REDCap, the extra space will be subsequently removed to maintain the integrity of the initial value in the data dictionary as it was exported.
  • Change: When exporting data to SPSS, date and datetime fields are now represented as A500 and text fields as A1000 in the SPSS syntax file, whereas previously they were all represented as A30000, which could cause very slow processing when loading the data into SPSS.
  • Improvement: A "Copy existing choices" link was added to the "Add Matrix of Fields" popup on the Online Designer page (just like the same link in the "Add New Field" popup on that same page) to copy the choices from an existing multiple choices field to that matrix of fields.
  • Change: When viewing a partially completed or fully completed survey response on a data entry form, the text color and background color of the red box near the top of the page have been changed to reflect the state of the response more accurately (i.e., it is no longer displayed as a red box, which often evokes a sense of there being an error). If the response is partially completed, it is displayed as an orange box, whereas if it is fully completed, it is displayed as a green box. The box color is thus consistent with the color instrument status icons used.
  • Change/improvement: The JS/CSS front-end libraries jQuery and Bootstrap have been upgraded to jQuery 3 and Bootstrap 4.
  • Change: When exporting data in CSV format (raw data or labels) on the "My Reports & Exports" page, it now maintains all double quotes in free-form text, whereas previous versions would replace all double quotes with single quotes in a CSV export. Note: When exporting to stats packages, it will still replace double quotes with single quotes for compatibility purposes.
  • Change: The footer of survey pages now says "Powered by REDCap", whereas previous versions have "REDCap X.X.X - © 20XX Vanderbilt University". For non-survey pages, the footer will remain the same.
  • Change/improvement: When displaying the filename of an uploaded file on a File Upload field on a form or survey, if the filename is very long (>34 characters in length), it now truncates the filename with an ellipsis closer to the middle of the filename rather than at the end. This allows the file extension to be visible, whereas in previous versions it was impossible to tell what type of file it is without downloading it if the filename was long.
  • Improvement: Data Quality rule H (i.e., "Incorrect values for calculated fields") and auto-calcs (i.e., the process of calc fields being triggered by data imports or cross-form/cross-event calculations) can now handle Smart Variables that are used inside calculated field equations. In previous versions, such calc fields could only successfully run while on a data entry form or survey page.
  • Improvement: Smart Variables are now able to be utilized in Data Quality rule logic. Note: In many cases, Smart Variables in the logic may cause Data Quality rules to take much longer to complete, which is due to the fact that the logic has to be re-evaluated for *every* item being processed by the DQ rule, whereas normally the logic only needs to be evaluated just once at the beginning of when the DQ rule is executed.
  • Improvement: The REDCap Mobile App v3.0 and later supports the Repeating Instruments and Events feature in REDCap projects.
  • Improvement: PDF Customization Options - Users may change or remove the “Confidential” text displayed in the header of all PDFs in a project. Also, instead of displaying the REDCap logo and REDCap website URL at the bottom right of all PDF pages, they can instead choose to display the text “Powered by REDCap” in small font. These two settings are project-level, so they will be applied to every page of a PDF for all instruments in a project (for both forms and surveys). These settings can be found in the Additional Customizations popup on the Project Setup page. 
  • Various security fixes.
  • Various bug fixes.

REDCap v8.4

  • New Feature: Smart Variables:
    • Smart Variables are dynamic variables that can be used in calculated fields, conditional/branching logic, and piping. Similar to using project variable names inside square brackets - e.g., [heart_rate], Smart Variables are also represented inside brackets - e.g., [user-name], [survey-link], [previous-event-name][weight], or [heart_rate][previous-instance]. But instead of pointing to data fields, Smart Variables are context-aware and thus adapt to the current situation. Some can be used with field variables or other Smart Variables, and some are meant to be used as stand-alone. There are many possibilities.
    • 35 Smart Variables are available. They can reference things with regard to users, records, forms, surveys, events/arms, or repeating instances. Documentation and examples for using Smart Variables are included on the Project Setup page, Online Designer, and other places throughout REDCap in a popup and alternatively as a standalone page.
    • Note: While Smart Variables can be used for filters in reports and for filters for Custom Record Status Dashboards, they are not yet able to be utilized in Data Quality rule logic. 
  • Improvement: SQL fields can utilize Smart Variables:
    • SQL Fields, as always, are only available for admins. But utilizing Smart Variables in SQL fields can be very powerful because they allow the query to be truly dynamic and change from context to context or record to record, rather than it always being a static query that gets executed against the database.   
    • Note: When using Smart Variables inside the query of an SQL field, you do NOT need to wrap the Smart Variable in quotes or apostrophes because the Smart Variable itself will be replaced with a value already wrapped in single quotes. Also, the value of the Smart Variable will be SQL-escaped when placed inside the query so that no user can inject values to manipulate the query. This has no effect on how one constructs the query, but for security purposes it is good to know that this is being done.
  • Improvement: Custom Record Labels now use proper piping syntax and can also utilize Smart Variables.
    • Because Custom Record Labels existed long before the concept of piping was created in REDCap, they did not adhere to typical piping concepts – e.g., they could not use prepended event names; they would display the raw value of a multiple choice field whereas piping would instead display the label of a multiple choice field. There also used to be certain limitations Custom Record Labels, in which they could only use data from fields on the very first event (of the current arm). Now that Custom Record Labels can be used like regular piping, they can target fields on any event in a project, and they can also utilize Smart Variables.
    • Note: Any longitudinal projects existing before the upgrade that currently use Custom Record Labels will automatically have all fields in the Custom Record Label prepended with the [first-event-name] Smart Variable in order to maintain the existing behavior from previous versions that could only pull data from the first event of the current arm. So prepending [first-event-name] allows existing longitudinal projects to maintain the way they worked prior to the upgrade to this REDCap version.
  • Improvement/change: New method for composing survey invitation text using Smart Variables for survey link
    • When composing a survey invitation, the standard text and survey link are no longer automatically appended to the survey invitation text at the time the email is sent. Instead, users must now specify all the entirety of the text of the email (including the stock text and survey link that used to be appended automatically, if they wish) and therefore must supply [survey-url] and/or [survey-link] in the text if they wish to provide the participant with a link to the survey.
    • If the user forgets to enter the survey URL Smart Variable in the text, REDCap will automatically suggest to them that they should.
    • If using the Twilio telephony module for sending invitations, the standard instructional text will still be appended in the SMS message as in previous versions EXCEPT for the “Email invitation” and “SMS invitation (contains survey link)” invitation types, which require [survey-url] and/or [survey-link] in the SMS text in order for the participant to receive a survey link.
    • Note: All survey invitations that were scheduled prior to this upgrade will still have the standard text and survey link appended to their survey text. Additionally, during the upgrade to this version, all saved configurations for Automated Survey Invitations (ASIs) will have the standard text and survey link automatically appended to the saved ASI email text, thus allowing the ASI behavior to remain exactly the same after the upgrade and allowing it to be backward compatible.
  • New feature: New syntax for referencing fields on repeating instances in piping, logic, and calculations
    • Fields that exist on a repeating instrument or on a repeating event can be referenced using a new syntax (note: repeating events and instruments are used the exact same way). This is done by appending the “repeat instance” number to the field inside square brackets – e.g., [weight][2], which points to repeating instance #2 for the field “weight”.
    • Please note the distinction that unique event names should be *prepended* to variables whereas repeating instance numbers must be *appended* to them. For example, if the field “weight” exists on a form in the event “Visit Data” in a longitudinal project, you might reference instance #2 for that field on that specific event with the following: [visit_data_arm_1][weight][2].
    • Smart Variables can be used in place of the repeating instance number, in which there are 5 instance-related Smart Variables: [previous-instance], [next-instance], [current-instance], [first-instance], and [last-instance]. For example, if you wish to use @DEFAULT action tag to carry over data from the previous instance of a repeating instrument, it might be set up as follows: @DEFAULT=”[weight][previous-instance]”.
  • Improvement: Piping can now be used for checkbox fields
    • Piping from Checkbox fields is slightly different than with other field types because checkboxes allow for multiple saved values. There are options to display a list of checked choices, unchecked choices, or a specific choice.
      • [my_checkbox:checked] - Appending ':checked' will display a comma-delimited list of choice labels that have been checked - e.g., 'Sunday, Tuesday, Thursday'. Note: If neither ':checked' nor ':unchecked' is appended to the variable, then it will default to ':checked'.
      • [my_checkbox:unchecked] - Appending ':unchecked' will display a comma-delimited list of choice labels that have NOT been checked - e.g., 'Monday, Wednesday, Friday, Saturday'.
      • [my_checkbox(code)] - If a coded value of the checkbox is included inside parentheses after the variable name - e.g., [my_checkbox:(2)] - then it will output the word 'Checked' or 'Unchecked' regarding whether or not that specific choice has been checked off.
    • Please note that while the checkbox piping options listed above will return the text labels, you may also append ':value' to the variable to return the raw value instead of the label. For example, [my_checkbox:checked:value] and [my_checkbox:unchecked:value] might return '1, 3, 5' and '2, 4, 6, 7', respectively, and [my_checkbox(2):value] will return 1 or 0 if checked or not checked, respectively.
  • Improvement: Multiple choice fields can now have their raw value (as opposed to their choice label) piped by appending “:value” to the variable name – e.g., [my_radio_field:value]. Note: This can also be used for SQL Fields to display the raw value of the SQL Field drop-down.
  • Improvement: Multiple choice fields can now have their raw value (as opposed to their choice label) piped inside an @DEFAULT action tag by appending “:value” to the variable name – e.g., @DEFAULT=”[my_radio_field:value]”. 
  • Various security fixes.
  • Various bug fixes.

REDCap v8.3

  • New feature: PDF Auto-Archiver:Upon survey completion, a compact PDF copy of the survey response can be automatically stored in the project's File Repository, from which the archived PDFs can be downloaded at any time. This setting is located on the Survey Settings page in the Online Designer, thus it can be enabled for any given survey in a project. 
  • New feature: Survey-specific email invitation fields
    • This is a new option on the Survey Settings page that can be enabled for any given survey, in which a user may designate an email field for sending survey invitations for that survey only.
    • The email field being utilized for the survey can exist on any instrument in the project, and you may use a different email field on each survey. You may also use the same email field for multiple surveys.
    • This feature is similar to the project-level email invitation field except that it is employed only for the survey where it has been enabled. This allows users to have data entry workflows that require multiple surveys where the participant is different for each survey. Using this feature, multiple people can be emailed a survey invitation, after which all the survey data they enter goes into the same record in the project.
  • Improvement: The Survey Invitation Log now contains an extra column on the right-hand side to allow users to delete many scheduled invitations at once (rather than having to delete them one at a time).
  • Change: When using the designated email invitation field (enabled on the Project Setup page), if the field is located on an instrument that gets used on multiple longitudinal events or if it is located on a repeating instrument/event, all occurrences of the field will now be forced to have the same value. This means that if one value is entered for the field, that value will always be the value seen in other events or other repeating instances of the instrument. And if the value is changed on any event or repeated instance, then that value will be updated on all events or repeating instruments/events where the field has a value. This will keep the field's value in sync in all locations since the underlying assumption of the designated email invitation field is that there is really only one single value, which is the email address of the survey participant.
  • Various security fixes.
  • Various bug fixes.

REDCap v8.2

  • Improvement: New "compact" option for PDFs of forms/surveys in which a compact-formatted PDF is produced that excludes fields that have no data saved and excludes unselected multiple choice options, thus producing a smaller PDF file. (Note: Section headers and descriptive fields will still be included.) On all pages that offer a PDF download option, there is now an extra "compact" option.
  • Improvement: Added new "Record ID" column in the Survey Invitation Log table to allow users to find specific invitations more efficiently. Note: If the record name should not be displayed in order to preserve the anonymity of a response (e.g., participant identifier is not used, designated email field is not used), it will instead display an icon indicating that the record name cannot be displayed.
  • Improvement: Added new filter on the Survey Invitation Log table to allow users to filter the invitations by record ID.
  • Improvement: Added new filter on the Survey Invitation Log table to allow users to filter the invitations by record ID.
  • Improvement/change: Added new "Record ID" column in the Participant List table. In previous versions, the record ID was appended to the email address in the "Email" column. Having its own column will allow users to find specific participants more efficiently.
  • Improvement: When opening the "Add/Edit Branching Logic" popup in the Online Designer, it could sometimes be very slow to open if the project contains many fields, especially many multiple choice fields.To improve this, it now defaults to selecting the "Advanced" option first when the popup opens and only attempts to load the "Drag-N-Drop" draggable field choices when that option has been selected by a user.
  • Improvement: If a field has branching logic, the Online Designer now displays the logic (up to the first 65 characters) on the field so that the user can view it easily without having to open the Add/Edit Branching Logic popup.
  • New API method: Export Repeating Instruments and Events - This method allows you to export a list of the repeated instruments and repeating events for a project. This includes their unique instrument name as seen in the second column of the Data Dictionary, as well as each repeating instrument's corresponding custom repeating instrument label. For longitudinal projects, the unique event name is also returned for each repeating instrument. Additionally, repeating events are returned as separate items, in which the instrument name will be blank/null to indicate that it is a repeating event (rather than a repeating instrument).
  • Improvement/change: The project Logging page now provides useful contextual information for the ASI logged event "Automatically schedule survey invitation", in which it will display the record name, survey title, and event name (if longitudinal).
  • Improvement/change: The project Logging page now logs when a survey invitation that was scheduled via ASI gets deleted due to the ASI option "Ensure logic is still true before sending invitation?", in which the logged event will display useful contextual information, such as the record name, survey title, and event name (if longitudinal).
  • Performance improvement: For projects containing a large amount of records (i.e., thousands or tens of thousands), some pages in the project might become very slow, and if a user repeatedly attempts to open a page that is initially slow to open, often due to slow database queries being executed, then those queries can get backlogged on the database server and reduce performance over time. A new mechanism has been implemented that will improve server performance in these cases by actively killing off any abandoned MySQL processes that are still running on the server.
  • Updated Help & FAQ page content.
  • Various security fixes.
  • Various bug fixes.

REDCap v8.1

  •  New action tag: @MAXCHOICE
    • Causes one or more specified choices to be disabled (i.e., displayed but not usable) for a checkbox, radio button, or drop-down field after a specified amount of records have been saved with that choice. For example, @MAXCHOICE(0=50,1=75,2=50) would imply that once 50 records have selected the '0' coded choice, that choice will become disabled for any record viewed afterward that does not have that choice saved, such as when the form/survey is opened for a new record, and thus 75 records for choice '1', 50 for choice '2', etc.
    • The format must be the action tag name followed by the choice designations inside parentheses, in which each will follow the format of ChoiceCode=MaxCount with each choice separated by commas. Note: For longitudinal projects, when counting the number of choices saved for records, it will treat all events as separate, meaning that in the example above, choice '0' can have a max number of 50 selections in EACH event in the project.
    • Note: This action tag not only gets employed when a form or survey is loaded but also when a form or survey is submitted in order to prevent users/respondents from going over the max amount specified. If a user submits a form/survey, at which point the maximum has been reached due to simultaneous users entering data just before them, it will not save that field’s value (but will save all the other fields on the form/survey), and it will reload the form/survey and tell the user to make another selection for the field.
  • New action tag: @MAXCHECKED - Allows a checkbox field to have a maximum number of checkboxes that can be checked. If other checkbox options are clicked after the maximum has been reached, those choices will not be able to be checked. The format must be @MAXCHECKED=#, in which # is a positive integer. For example, @MAXCHECKED=3 will allow a maximum of 3 checkbox choices to be checked. NOTE: This action tag can only be utilized by Checkbox fields, and it does not get enforced during data imports.
  • New feature: New option to allow respondents to return to a partially completed or fully completed survey response without needing a return code. When enabling "Save & Return Later" for a survey on the Survey Settings page, it will still default to requiring a return code in order for a respondent to continue the survey where they left off. But a user may opt to allow respondents to return to and continue their survey with only the survey link (i.e., without needing a return code in addition to the link) to view and modify their previous responses on that survey. Note: A warning exists in bold text in the informational popup for this feature that states the following: "If you are collecting identifying information (e.g., PII, PHI), for privacy reasons it is HIGHLY recommended that you leave the option unchecked so as to enforce a return code."
  • Change: For PDF exports of data entry forms with data, if a field that is normally removed from exports due to users having export rights of "De-Identified" or "Remove all tagged Identifier fields" is being used in the Custom Record Label or Secondary Unique Field value in the PDF file, that field value will no longer be piped in the PDF file but will instead be redacted (i.e., replaced with the text "[*DATA REMOVED*]"). This change is made to increase security/privacy regarding de-identification of data in data exports.
  • Change: The action tags @TODAY and @NOW will no longer hide the Today/Now button, will no longer hide the date-picker icon, and will no longer make the field read-only by default. From this version onward, users will need to additionally use @READONLY in order to accomplish those things. For backward compatibility, the REDCap upgrade process will automatically replace all instances of the @TODAY and @NOW action tags with "@TODAY @READONLY" and "@NOW @READONLY", respectively, to maintain the existing behavior for fields already using @TODAY and @NOW.
  • Change: When field values get modified via the action tags @TODAY, @NOW, @LATITUDE, @LONGITUDE, and @USERNAME, it now displays the red side bar on the right side of the text field (just like calculated fields do when changed) to denote there was a value that changed.  
  • Various security fixes.
  • Various bug fixes.

REDCap v8.0

  • New feature: External Modules are individual packages of software that can be downloaded and installed by a REDCap administrator. Modules can extend REDCap's current functionality, and can also provide customizations and enhancements for REDCap's existing behavior and appearance at the system level or project level. Modules can utilize REDCap hooks and also can have REDCap plugin pages as part of them.
  • Improvement: On the Public Survey Link page in a project, a new button "Open Public Survey + Logout" has been added to increase security in case users want to open the public survey while ensuring that the participant cannot access their REDCap account in the other browser tab.
  • Improvement: The datediff() function can now utilize the “now” variable as one of the two date/time parameters (in a similar way as the “today” variable). This is not only true for calc fields, but also for ASI logic, DQ rules, report filters, etc. You may use a time, date, datetime, or datetime_seconds field with the “now” parameter in datediff. Note: If using a date field with “now”, it will assume midnight (00:00) for the time component for the date field.
  • Change: When piping field values into an @DEFAULT action tag when the piped value is blank/non-existent, it now no longer replaces the [variable] with "______" but instead replaces it with "" (i.e., nothing), which is viewed as more preferable since the value is being input as a field value. This is only true for piping specifically within the @DEFAULT tag and not for piping in general.
  • Various security fixes.
  • Various bug fixes.

REDCap v7.6

  • New Feature: New Action Tags
    • @CHARLIMIT - Sets the maximum number of characters that can be entered into a Text field or Notes field, and also displays the number of characters remaining. The format must follow the pattern @CHARLIMIT=??, in which ?? is the desired max character count (alternatively, the number value can be inside single or double quotes). NOTE: This action tag cannot be used at the same time as @WORDLIMIT for the same field. NOTE: This action tag does *not* get applied during any data imports (via API or Data Import Tool) but only operates when viewing survey pages and data entry forms.
    • @WORDLIMIT - Sets the maximum number of words that can be entered into a Text field or Notes field, and also displays the number of words remaining. The format must follow the pattern @WORDLIMIT=??, in which ?? is the desired max word count (alternatively, the number value can be inside single or double quotes). NOTE: This action tag cannot be used at the same time as @CHARLIMIT for the same field. NOTE: This action tag does *not* get applied during any data imports (via API or Data Import Tool) but only operates when viewing survey pages and data entry forms.
    • @RANDOMORDER - Randomizes the order of multiple choice field options as displayed on survey pages and data entry forms, in which their order will be different each time the page is loaded. NOTE: This action tag can only be utilized for the following field types: Checkbox, Radio, Drop-down, Yes-No, and True-False. This tag also works for enhanced radios and checkboxes on surveys.
    • @HIDECHOICE - Hides one or more choices of a multiple choice field. This action tag is useful if you wish to retire a particular choice after utilizing it for a while in data collection, thus allowing you to hide the choice from that point after without orphaning any of the choice's data, which would happen if you simply deleted the choice. The format must follow the pattern @HIDECHOICE='??', in which the coded values should be inside single or double quotes for the choice(s) you wish to hide. If more than one choice needs to be hidden, then provide all the coded values separated by commas. For example, to hide the choice 'Monday (1)', you would have @HIDECHOICE='1', but if you wanted to additionally hide 'Tuesday (2)', you would have @HIDECHOICE='1,2'. NOTE: If the hidden choice has already been selected for a given record, then the choice will not be hidden on the survey or form for that record/event. NOTE: Hidden choices will still appear in reports and data exports. NOTE: This action tag can only be utilized for the following field types: Checkbox, Radio, Drop-down, Yes-No, and True-False. NOTE: This action tag works only in limited fashion with a matrix of fields, in which it will simply hide the checkbox/radio but still display the column for that choice in the matrix.
    • @ NONEOFTHEABOVE - Allows for the designation of a checkbox choice to be a 'none of the above' option, thus ensuring that no other choices are checked if that one choice is selected. This means that if that particular option is selected, it will alert the user that all other checked-off choices will be unchecked. And if the 'none of the above' option is already checked when the user checks off another choice, it will automatically uncheck the 'none of the above' option. This action tag makes it possible to have a 'none of the above' option without the risk of users mistakenly having other choices selected at the same time. The format must follow the pattern @NONEOFTHEABOVE=??, in which ?? is the coded value of the 'none of the above' checkbox choice - e.g., @NONEOFTHEABOVE=98. Alternatively, it is possible to set multiple options as a 'none of the above' option at the same time, in which the coded values must be comma delimited inside single or double quotes - e.g., @NONEOFTHEABOVE='45,99'. This is useful for certain situations, such as if you have a 'none of the above' option and also have a 'refuse to answer' option, thus allowing either of those to be the only option that can be selected at a time. NOTE: This action tag can only be utilized by Checkbox fields.
  • Improvement: Improved accessibility on surveys when using screen readers. Additionally, tabbing now works correct when tabbing through “Enhanced Radios and Checkboxes”, and the spacebar can be used to select a choice, as is always the case with standard radios and checkboxes.
  • Improvement: New "Save & Exit Record" button on data entry forms - After being clicked, the user is taken back to the Record Home Page to select another record or create a new one.
  • Improvement: New "Save & Go To Next Record" button on data entry forms - After being clicked, the user is taken to the Record Home Page for the record that follows the record just edited (according to the record order seen on the Record Status Dashboard).
  • Improvement: Record auto-numbering for data imports (Data Import Tool, API, and Mobile App). For the Data Import Tool, the user may enable the new setting “Force record auto-numbering”, and in the API, the new parameterforceAutoNumber=true can be used, which will create new record names that are auto-generated by REDCap during the import process. In an upcoming version of the REDCap Mobile App, the mobile app will provide this API parameter automatically for records created in the app that did not previously exist in the project on the server. Note: This feature can only be utilized for projects with record auto-numbering enabled. Also, a record number must still be provided as a placeholder during the data import (to associate multiple rows with the same record), but that record name will be automatically changed to a new record ID generated by REDCap.
  • Improvement: When adding new choices for a multiple choice field in the Online Designer, it will now display an error message if any choices have duplicate codings (e.g., two choices both coded as "4" - "4, Pink" and "4, 4"), thus letting the user know that they should remove any duplicates because duplicates will be automatically removed when saving the field.
  • Improvement: Attach PDF of responses in confirmation email - When using the “Send confirmation email” option on the Survey Settings page for a survey, that section now contains an additional option to “Include PDF of completed survey as attachment”, which will add the PDF of their responses sent to the participant in their confirmation email. This new option contains the following warning as a reminder to users: “WARNING: Since email is not considered a secure form of communication, the PDF attachment option is NOT recommended if the survey contains questions asking for identifying information (e.g., PHI).”.
  • Various security fixes.
  • Various bug fixes

REDCap v7.3

  • New feature: Time Limit for Survey Completion – Users may set the amount of time (in days, hours, and/or minutes) that each respondent has to complete a given survey based on when they were initially sent the survey invitation. Note: This feature excludes public survey links. When enabled, a new column is displayed on the Participant List where it denotes if a participant’s survey link has expired and also displays the expiration time if you hover over the icon. If the icon is clicked, the user can permanently override the link expiration time by setting it further in the future (to give the respondent more time), or else to expire the link sooner (or even immediately).
  • New feature: Response Limit for surveys – Users may set a response limit for any given survey to prevent respondents from starting the survey once a set number of responses have been collected. Note: It can be set so that the response count included either completed responses only or both partial and completed responses. Users may also set custom text to be displayed to respondents on the survey page when the response limit has been reached.
  • Improvement: The survey options at the top of a data entry form now include a new option “Log out + Open suvey”, which will simultaneously open the survey in a new browser tab while logging out the REDCap user in the current tab. This makes it easier for users to log out of their REDCap session in case they walk away from the computer while a participant takes the survey, thus ensuring that the participant is not able to go into the first tab and access the user’s REDCap account and projects.
  • Various security fixes.
  • Various bug fixes.

 

REDCap v7.2

  • New feature: Custom Record Status Dashboard:
    • Users can build and save custom versions of the Record Status Dashboard to customize the dashboard to their liking.
    • Custom dashboards have the following configuration options:
      • A title and a description/instructions
      • Which instruments to include or exclude in the dashboard’s display
      • Similar to building reports in REDCap, Custom Record Status Dashboards allow users to sort records in the dashboard by another field’s value.
      • One can set filter logic to filter the records displayed in the dashboard to a specific subset of the total records (e.g. [age] > 30 and [diabetes] = “1”).
      • There are aesthetic controls as well, such as being able to display the dashboard headers vertically, which will transpose them 90 degrees for a more compact display on the page.
  • New feature: Text searching and ordering on reports – Users now have a search box displayed at the top of every report where they can type text to search the report, in which it will only show the rows in the currently viewed report that match the search string that is typed. Additionally, any column in a report can have its column header clicked to sort the table according to the values in that column (in ascending or descending order).
  • Improvement: For longitudinal projects containing multiple arms, the Record Status Dashboard now displays each arm separately in a tabbed interface rather than trying to fit all arms in a single table, which typically is not the best way to view multiple arms of records.
  • Improvement: Checkbox fields on reports are now displayed better with their field label spanning all the choices as a row above all the choices and displaying just the choice text and variable in the individual choice column headers on the second row of the header. This groups the checkbox options together much better and is much more intuitive to read and interpret.
  • Improvement: The Group ID number for each Data Access Group (DAG) is now displayed in the DAG table on the Data Access Groups page in a project. The Group ID number is the number that is automatically generated by REDCap and is automatically prepended with a dash/hyphen to the record name when a user assigned to a DAG is creating a new record. The Group ID number is now displayed in the table on the page so that users are aware of what each DAG’s Group ID number is.
  • Various security fixes.
  • Various bug fixes.

 

REDCap v7.1

  • New feature: Repeatable Instruments and Events: REDCap now allows you to enable a form to be collected repeatedly, without having to predetermine how many times you might need it. This has been referred to as “ad hoc forms” or “one to many relationships.” This will be an extremely useful feature going forward. To read more about it, please visit: Repeating Instruments and Events. You can enable this feature in the Optional Modules section of Project Setup within your REDCap project.
  • New feature: Better device management for the REDCap Mobile App – The Mobile App page in a project now contains better methods for keeping track of the activity of the mobile app used on many devices at a time for a single project.
  • Improvement: New interface for Home/My Projects/Control Center pages.
  • Improvement: New font “Open Sans” is available to use for the font on surveys.
  • Improvement: The Project Revision History page is now much faster to load for production projects.
  • Improvement: The results displayed from executed rules on the Data Quality page now display the field label above the variable name and value. This provides better context for users who might not know the variable names.
  • Improvement: Execution of Data Quality rules should now be less intensive on the database server, especially when running them on larger data sets.
  • Improvement: A PDF of record data for all instruments/events for a given record can now be downloaded from the “Choose action for record” drop-down on the Record Home Page if the user has Data Export privileges.
  • Improvement: A zip file containing all uploaded documents (or signature files) for an individual record can now be downloaded from the “Choose action for record” drop-down on the Record Home Page if the user has Data Export privileges.
  • Improvement: File Upload fields that are displayed on reports will no longer display the text “[document]”, but will instead provide a “Download” button so that the user can actually download the file from the report.
  • Improvement/change: The $repeat_instance parameter was added to the two plugin/hook methods REDCap::getSurveyReturnCode and REDCap::getSurveyLink. The parameter is to be used only for projects with repeating instruments/events, in which it is the repeat instance number of the repeating event (if longitudinal) or the repeating instrument (if classic or longitudinal).
    Improvement: When the user clicks the “Save & Stay” button (formerly the “Save and Continue button) on a data entry form, it now says “Record XXXX was successfully edited” at the top of the page to denote that the form was saved.
  • Improvement/change: Assigning a record to a Data Access Group (or unassigning/reassigning a record) is now performed on the Record Home page using the “Choose action for record” drop-down list rather than on the data entry form. The only exception for this is when a record is being created on a data entry form (when the record does not yet exist), in which it will allow the user to set the Data Access Group using the drop-down list at the top right of the form. This is so a record can be assigned to a DAG at the moment of its creation.
  • Improvement: For records that have been assigned to a Data Access Group, it will now display their Data Access Group assignment under the recod name on the Record Home Page.
  • Improvement: When displaying a count of each project’s records on the My Projects page and on the Browse Projects page (in the Control Center), it now uses a cached count of the records in the project (if available) rather than calculating the number of records on the fly each time. This improves database server performance by making so many expensive queries to the database.
  • Change: REDCap’s base font is now Open Sans, and is slightly bigger in size, providing better readability. In previous versions, the base font was Arial. Note: Any plugins or hooks that don’t have their own specific stylesheets that set the font-family of their content will be affected by this.
  • Change: Renaming a record is now performed on the Record Home page using the “Choose action for record” drop-down list rather than on the first data entry form.
  • Change: The location of the “Design your data collection instruments” step and “Define your events” step (longitudinal projects only) on the Project Setup page will now remain in the same location on the page when in production status as they did when in development status. In previous versions, these two steps were moved to the bottom of the page. This change is to provide more consistency for where things are located during the entire development of a project.
  • Change: The method in which to delete an entire record has been changed. It is no longer done by clicking a button at the bottom of the data entry form, but rather it is done by selecting the Delete Record option in the record actions drop-down on the Record Home Page.
  • Change: The method in which to delete an entire event of a record has been changed (this applies to longitudinal projects only). It is no longer done by clicking a button at the bottom of the data entry form, but rather it is done by clicking the red X icons now displayed in the bottom row of the status table on the Record Home Page.
  • Change: Added new project template to showcase the Repeating Instruments functionality.
  • Various security fixes.
  • Various bug fixes.

 

REDCap v6.17

  • New feature: Data Dictionary Snapshot: You can now click a button on the Online Designer to create a snapshot of  instruments (i.e., CSV data dictionary) that gets stored on the Project Revision History page. Additionally, a data dictionary snapshot is also created automatically whenever a data dictionary is uploaded on the Data Dictionary Upload page or via the API metadata import.
  • New feature: Preview email – When composing a survey invitation (in either the Participant List or in Automated Survey Invitations set up), there is now a Preview option for viewing the fully-rendered HTML preview of the email that is being composed. Additionally, there is an option to send a test email to oneself in case they want to actually receive a copy the email being composed before officially sending it to others.
  • Improvement: When reviewing drafted changes in a production project, it now provides a “Compare” button for multiple choice fields that have a change in one or more choices. Clicking the button opens a popup with a table displaying each choice on a row and noting if the choice is Unchanged, Altered, Added, or Removed. Additionally, it also displays how many records have a saved value for the given choice. This will help when reviewing draft changes when in production status.
  • Improvement: When reviewing drafted changes in a production project, it will now give a warning on the page if a user has initialized the project in the REDCap Mobile App. It will note that the changes being made *may* affect the app user’s ability to sync data back to the project and recommends that perhaps the app user should first sync all their data back to the server before the changes are committed.
  • Improvement: When reviewing drafted changes in a production project, it now truncates any text (field labels, choices, etc.) in the table that is very long, and provides a “Show more” link if you wish to view the full text.
  • Improvement: When reviewing drafted changes in a production project, if any fields are being deleted and those fields contain data, it will note how many records will be affected for each field deleted. Also, if fields are being added and those fields previously existed in the project, in which they had data saved or them but then the fields were deleted, then it will note how many records have orphaned data for those fields (because that data will be restored if the fields are re-added – this is sometimes undesirable).
  • Various security fixes.
  • Various bug fixes.

 

REDCap v6.16

  • New feature: Enhanced radio buttons & checkboxes for surveys: Ordinary radio button fields and checkbox fields may now be transformed into more animated, modern-looking buttons on survey pages. These enhanced versions of radios and checkboxes are a good way to spice up your surveys with a more fresh, user-friendly interface. The enhanced choices feature can be enabled for any given survey in a project under the Survey Design Options section on the Survey Settings page in the Online Designer of your project. It operates at the survey level, so *all* radios and checkboxes on a survey will be transformed if this is enabled. Live demo survey of new enhanced choices.
  • New feature: New Action Tags:
    • @HIDEBUTTON: Hides the ‘Now’ or ‘Today’ button that is typically displayed to the right of date, time, and date/time fields. This will be very useful for some date/time fields that do not require a Now/Today button, such as Date of Birth, for example.
  • Improvement: Slider fields can be displayed as vertical by setting their Custom Alignment to right-vertical (RV) or left-vertical (LV).
  • Improvement: Server-side field validation – In addition to the existing client-side field validation that is performed on surveys and data entry forms, REDCap will now also perform server-side validation to validate all submitted values prior to saving them to ensure they are valid values. If they are considered invalid values, then the value will not be saved, and the page will be reloaded with an error message (similar to the Required Fields error message) informing the user that invalid values were entered and should thus be corrected, if desired. This new server-side validation improves the overall quality of data being entered on surveys and form.
  • New feature: Create custom public survey link – On the “Public Survey Link” page in a project that utilizes surveys, users now have the option to create their own custom public survey link that begins with “http://is.gd” (e.g., http://is.gd/diabeticsurvey), in which the custom URL will simply redirect to the public survey in their project. They may enter a desired URL, and it will check if the URL has already been taken.
  • Improvement: Updated “Help & FAQ” page. Has better navigation and is easier to read.
  • Improvement/change: If a user has had access to REDCap for more than 7 days and they are logging in to REDCap’s home page, then it will redirect them to the My Projects page after a successful login.
  • Various security fixes.
  • Various bug fixes.

 

REDCap v6.14

  • New feature: New Action Tags:
    • @USERNAME: Sets a field’s value to the username of the current REDCap user. If this is used on a survey, the value will be “[survey respondent]”. Once the value is captured, it will not be changed when visiting the page at a later time.
    • @DEFAULT: Sets a field’s initial (i.e. the default) value.
      • This action tag allows a field to have a specified default value when viewing the field on a survey or data entry form that has not yet had any data saved for it (i.e., when the form status icon is gray or when a survey has not been started).
      • The format must follow the pattern @DEFAULT=”????”, in which the desired default value should be inside single or double quotes.
      • For checkbox fields, simply separate multiple checkbox values with commas – e.g., @DEFAULT=’1,3,6′. NOTE: The default value does *not* get applied during any data imports (via API or Data Import Tool) but only operates when viewing survey pages and data entry forms.
      • NOTE: If being used on a date or datetime field, the date value inside the quotes must be in Y-M-D format – e.g., @DEFAULT=’2007-12-25′.
      • If this action tag is used on a survey question that is utilizing a survey pre-fill method (via query string or POST submit), then the pre-fill values supplied will override the default values provided by the action tag.
  • Improvement: Section headers and field annotations are now displayed in the codebook
  • Change/improvement: The mailto link at the bottom left of a project has now been replaced with a “Contact REDCap administrator” button that, when clicked, opens the user’s default email client and pre-fills the email body with their username, the title of the current project, and a link to the project. This should help administrators in case this information is not provided by the user themselves, which is often the case
  • Change: When adding a new field in the Online Designer, the Custom Alignment setting no longer resets back to “Right Vertical (RV)” alignment every time as it did in previous versions, but instead it now reverts to the alignment value of the previous field that was opened beforehand while on that page.
  • Various security fixes.
  • Various bug fixes.

 

REDCap v6.12

  • New feature: Project Exporting – An entire REDCap project can now be exported as a single XML file. The file includes events, arms, instruments, fields, and project attributes – even Descriptive field attachments. If the project contains data, then the user can also optionally export the project data (including uploaded files) in the same XML file. This XML file can serve as a snapshot or backup copy of the project, and can even be imported on the Create New Project page to create a clone (more or less) of the project.
  • Improvement: Live Filters in Reports. It has always been possible to add filters to your reports, but you may sometimes need to quickly filter your data further using another field. Before this version, you would have to create a separate reports for each filter. With the addition of Live Filters, any report can have up to 3 fields that can be designated as a Live Filter to be used to quickly filter the report on the fly (see the link below to view a quick video). Live Filters (similar to filtering in Excel) are displayed as drop-downs on a report at the top-right of the page, and selecting a Live Filter will cause the report to be re-run in real time using the Live Filter value as a filter. Note: Currently only multiple choice fields can be used as Live Filters (as well as Events, if longitudinal, and Data Access Groups, if any exist). Live Filters make it easy to view the data you want without having to create lots of similar reports. Watch a video of Live Filters in action (no audio).
  • Improvement: New option to download charts displayed on the “Stats & Charts” tab of the “Data Exports, Reports, and Stats” module. The charts will download as PNG image files.
  • Improvement: Users may now download and upload arms and events as a CSV file on the “Define My Events” page, as well as download and upload the instrument-event designations as a CSV file on the “Designate Instruments for My Events” page. Using these methods, users can now fully reconstruct the structure of a project if they wish to copy it, in which they could download the data dictionary file, arms file, events file, event mappings file, and data export file, and then upload all of them into a new project to recreate it.
  • Improvement: When an instrument has been enabled as a survey and the survey has the setting “Auto-continue to next survey” enabled, then a down arrow icon will now appear in the Online Designer for that survey to denote that this setting has been enabled.
  • Improvement: “select all” and “deselect all” links were added to the “Designate Instruments for My Events” page to allow users to more easily check off the checkboxes if many instruments and/or events exist in the project.
  • Improvement: When assigning projects to Project Folders, there is now a checkbox option to hide archived projects in the project list. This should make it easier for users to ignore those projects during the folder assignment process.
  • Change/improvement: When users are being assigned to a role while being granted access to a project on the User Rights page, it now displays a checkbox option to have the user emailed in order to notify them of having been granted access to the project.
  • Various security fixes.
  • Various bug fixes.

 

REDCap v6.10

  • New feature: Project Folders
    • Project Folders are a way for users to organize the projects on their My Projects page by putting them into groups. The folder can be given a name and can be color-coded (by setting a text color and background color) so that it displays boldly in the My Projects page.
    • Once a folder has been created, the user can assign any number of projects to a folder (and can even assign a single project to multiple folders). This allows the projects to be grouped together under that folder when displayed on the user’s My Projects page.
    • Project Folders are for personel organization, so no one else can see a user’s folders (except for REDCap administrators when viewing the user’s projects on the Browse Projects page in the Control Center).
  • New feature: Survey themes
    • 3 new options were added to the Survey Settings page for any given survey (accessed via the Online Designer):
      • Size of survey text – Set the survey text to a bigger font size (Normal, Large, or Very Large).
      • Font of survey text – Set the font family of all the text displayed on the survey (Arial, Georgia, Tahoma, and more).
      • Survey theme – Set the color scheme for the survey. There are 10 predefined themes available that users may use, but if they do not prefer them, users can easily click the Customize button to customize the color scheme of the survey any way they want, in which it will open up 8 different options for modifying the colors of various elements in the survey. Also, users may  create their own custom survey theme to save the theme with a specified name, after which they may easily use it their saved theme in the future for another survey.
    • A “survey design preview” box is displayed on the Survey Settings page so that the user can see how their survey design choices will make their survey look to respondents.
  • New feature: A project’s Survey Invitation Log is now downloadable in CSV format.
  • Improvement: On the Define My Events page in a longitudinal project, it no longer displays the Days Offset and Offset Range columns in the events table if the Scheduling module is not enabled for the project. Since those columns are only utilized during scheduling, this provides a simpler and less confusing interface for users when scheduling is not being used. When creating a new event in this case, the event name is the only thing that needs to be provided, after which the order of that event or any event in the current arm can be change using drag-n-drop by dragging that event’s row in the table.
  • Improvement: New styling options were added to the rich text editor for survey instructions and survey completion text, such as setting text color and background color, inserting tables, copy-paste options, and indentation options.

 

REDCap version 6.9

  • New feature: API Playground – The API Playground is an interface that allows experimentation with the REDCap API without actually writing any code. Users can explore all the different API methods and their various options to customize a given API request. Users may even execute a real API request and see the exact response that REDCap returns from the request.
  • Improvement: New look for API Documentation
  • New action tags
    • @LATITUDE – Allows a Text field to capture the latitude of the user, in which the user will be prompted on the webpage to allow or deny this. Once the value is captured, it will not be changed when visiting the page at a later time.
    • @LONGITUDE – Allows a Text field to capture the longitude of the user, in which the user will be prompted on the webpage to allow or deny this. Once the value is captured, it will not be changed when visiting the page at a later time.
    • @PASSWORDMASK – Masks the value of a Text field so that the true value is not visible on the webpage after it has been entered (like password fields on login pages).
    • @HIDDEN-APP – Hides the field only on the form ONLY on the REDCap Mobile App. Field will stay hidden even if branching logic attempts to make it visible.
    • @READONLY-APP – Makes the field read-only (i.e., disabled) on the form ONLY on the REDCap Mobile App so that its value cannot be changed.
    • @NOW – Automatically provides the user’s current time as the value of a Text when the page is loaded. Once the value is captured, it will not be changed when visiting the page at a later time. If the field has validation, the value will conform to the date/time format of the field.
    • @TODAY – Automatically provides the user’s current date as the value of a Text when the page is loaded. Once the value is captured, it will not be changed when visiting the page at a later time. If the field has validation, the value will conform to the date/time format of the field.
  • Improvement: Numbered lists and bullet lists (i.e., <ol>, <ul>, and <li> tags) can now be used in field labels, survey instructions, etc.