Please note: The material in this page is intended to: 1) describe OHSU's model of support and OCTRI operations, and 2) supplement the help material integrated into REDCap itself. If you are interested in learning more about this feature, check REDCap for a video, check the REDCap FAQ, and review the documentation in REDCap.


Description

Build alerts and send customized email notifications to other users and/or participants.

Feature Type

Elective advanced project application available on every project.

Fees

Custom support fees for setup help or help troubleshooting.

Eligible Projects/Project Status Dependency

  • Recommended Project Status at Setup = Development
  • Support Track = All support tracks

Request Process

  • Does not need to be requested.
  • Standard elective functionality that is available for use, out of the box, on every project.

REDCap Skills, Experience, Knowledge

  • Advanced Syntax

    • For creating the condition(s) to trigger the alert. You might have experience with advanced syntax if you've built a data quality rule, a calculated field, an advanced form filter, advanced branching logic, an or Automated Survey Invitation.
  • Codebook
    • To find variable names, form names and raw values used to construct the logic for the alert trigger or to include data in the notification message.
  • Piping
    • To include already collected data into the notification message.
  • Smart Variables
    • Can be included in the alert trigger syntax or as a source for piping values into a message.
    • For example, the Smart Variable [record-dag-name] corresponds to the unique group name of Data Access Group to which the current record belongs, and could be used in the alert trigger syntax to send a notification to a user based, in part, on the record's DAG assignment. The Smart Variable, [form-link:instrument:Custom Text], could be used to include an HTML web link in the notification, so the user could navigate to the specified data entry form for the current record/event/instance.

Installation, Configuration and Implementation

User Permissions

User will need permission enabled for the Alerts & Notifications user right.

magnifying glass tilted right Find: Alerts & Notifications

Access Alerts & Notifications via Lefthand Nav Menu > Applications Section > Alerts & Notifications.

Help and Support

Email and drop-in help are not provided for setting up or trouble shooting Alerts & Notifications.

Components of Building an Alert

  • Define how the alert gets triggered.
  • Define when and how many times the notification message will be sent
  • Specify the recipient, sender and message content.
  • Notifications can be sent to more than one recipient.
  • The message can include rich text, piping values from field variables and Smart Variables, and uploading one or more file attachments.
  • All messages to participants should have IRB approval

Testing an Alert

  • All Alerts & Notifications should be thoroughly vetted and tested before the project is moved to production.
  • To implement an Alert in a production project, the study personnel should request a copy of their project to first build and test the Alert before they activate the Alert in their production project.


Support Track Availability

Standard Service for Research

Self Service for Research

Standard Service for Non-Research

This is elective functionality that is available, out of the box, on every project and that can be set up by a project builder to meet study specific requirements through self-directed instruction. For help with this feature, custom support is available for projects using Standard Research or Standard Non-Research support tracks, for which there are charges.

  • No labels