New Features

• Action Tags

  • @DOWNLOAD-COUNT
    • Automatically count the number of downloads for a File Upload field or a Descriptive field attachment. 
  • @MAXCHOICE-SURVEY-COMPLETE
    • Disable one or more specified choices for a checkbox, radio button, or drop-down field after a specified amount of records have been saved with that choice for completed survey responses only.

• Additional Customization: Prevent branching logic from hiding fields that have values

  • Change default behavior of branching logic, which erases the value entered in a field that should be hidden by branching logic, to prevent data from being erased from fields that are hidden by branching logic.
    • Fields that have values will not be hidden by the branching logic.
    • When a field that should be hidden by branching logic is made visible because it has a value, an icon will be displayed on the field to indicate this to the user.
    • The name of corresponding Data Quality rule F changes when this setting is enabled from “Hidden fields that contain values” to “Fields that contain values that should be hidden”.
  • Project builder can enable via Project Setup tab > Additional Customizations.
  • Applies to both data entry forms and survey

• Smart Variables

  • [event-id]
    • Event id number for current event (longitudinal projects).
  • [survey-access-code:instrument]
    • Survey Access Code for specified survey for a given record/event/instance.
    • The format must be [survey-access-code] or [survey-access-code:instrument], in which 'instrument' is the unique form name of the specified instrument.
    • [survey-access-code] can be included in a survey invitation, and the 'instrument' is assumed to be the current survey instrument that corresponds to the invitation.
  • [survey-return-code:instrument]
    • Survey Return Code for specified survey for a given record/event/instance in order to allow a participant to return to a completed or partially completed survey response when using the 'Save & Return Later' survey feature.
    • The format must be [survey-return-code] or [survey-return-code:instrument], in which 'instrument' is the unique form name of the desired instrument. 
    • [survey-return-code] can be included in a survey invitation, and the 'instrument' is assumed to be the current survey instrument that corresponds to the invitation.
  • [user-role-id]
    • Role ID of the user role to which the current user is assigned (blank if not assigned to any user role).
    • The ID is auto-generated for each user role and unique to the project. 
  • [user-role-name]
    • Unique role name of the user role to which the current user is assigned (blank if not assigned to any user role).
    • This role name is auto-generated for each user role and unique to the project. 
  • [user-role-label] -
    • The name/label of the user role to which the current user is assigned (blank if not assigned to any user role).
    • This value is defined by the user that creates the user role.

• Tableau Data Export (API)

  • Export all records into Tableau via the REDCap API.
  • Connect Tableau to a REDCap project using an API token.
  • Project data can be exported on demand and be available for use within Tableau to produce summaries and visualizations.
  • API token required to use this feature.

• Video Tutorials

  • Project Dashboards and Smart Charts/Functions/Tables videos available on the Training Video page, Project Dashboards page, and Smart Variable popup documentation.

Changes & Improvements

• Data Entry/Data Entry Forms

  • New PDF Download Option
    • "This data entry form with saved data (send to printer: select "Save as PDF" for Printer/Destination)" option renders an improved browser-based print option to print/save the webpage as a PDF compared to the existing server-side PDF rendering options.

• Online Designer

  • Survey Settings included downloadable instrument zip file.

• Piping

  •  Add ":ampm" parameter when piping data or datetime validated field (e.g., [visit_time:ampm]) to display the time in am/pm format (e.g., 4:45pm, 10:35am) instead of military time.

• Reports

  • HTML 
    • URL or email address entered in a text or notes field will be converted into clickable link and mailto link when viewing the data in a report.
    • HTML tags will be rendered as HTML when viewing a report.
  • Live Filters included in Reports A and B 
    • Filter on: 1) the record ID field, 2) a list of all events (if the project is longitudinal), and 3) a list of all Data Access Groups (if the project contains DAGs and the current user is not assigned to a DAG).
  • Logging Improvements
    • More detailed logging descriptions on the Logging page, such as mentioning the report name and report ID.
  • Report Options for Creating New Report of Editing Existing Report
    • Display options for column headers can be customized to be field label, variable name, or both (default view).
    • Display options for multiple choice fields can be customized to be the field label, raw data value, or both (default view).
    • Exclude redcap_repeat_instrument and redcap_repeat_instance columns for projects that have have repeating instruments and/or repeating events.

• Survey Invitations

  • REDCap no longer automatically adds links to invitations for projects using Twilio, invitations configured to send the "Use participant's preference". 

Due to several factors, support for non-research REDCap projects is currently limited to: 1) processing system requests, 2) self-directed help and learning resources in the REDCap wiki, and 3) Basics and Survey training sessions. Please review the details below.

Funding for REDCap is currently only for research activities, which is also REDCap’s intended use – data collection for research studies. Although We are in the process of revising our model of support to work with both research and non-research projects in a more sustainable and beneficial way. However, at this time we are understaffed for the volume of project requests at OHSU.  and Given our mission and funding, we must prioritize providing support for research activities. Additionally, please note: we do expect the new model of support to include fees for non-research projects. We will share more details about the new model of support in upcoming months.

Training is still required for personnel building and managing non-research projects, but limited support means we are unable to provide help for non-research projects over email or at our drop-in sessions. At the present time, for non-research projects, we will be processing requests: 1) requests for new projects, 2) requests to move projects to production, and 3) system requests to approve form modifications that require a REDCap Admin’s review. We will conduct abbreviated pre-production review of survey projects over email.