We've annotated some screen shots from a demo project we use in our Survey training to help explain the components of an Automated Survey Invitation. In our survey training, we build out an ASI, and walk through all the elements of the invitation annotated in the screenshot below, as well as demonstrate triggering the ASI by creating a record and entering and saving some data. The material below is intended as reference material.
Need help: We expect most builders will need need help applying the material covered in our training to building out ASIs for the requirements of their study. Sign up for drop-in for help.
This is a screenshot of an email invitation set up for a survey that's intended to be sent out to participants every month for 3 months in a row, starting 30 days after the date of enrollment. This is the invitation for month one.
Basic Elements of ASI the Builder Configures
Closer Look at the Logic Statement in STEP 2: Conditions
This is a screenshot of the logic statement from the invitation above for month one.
Understanding the Logic Statement
All ASI logic statements are boolean expressions that are evaluated to be true or false. The logic statement in this example is constructed to automate the following two activities:
Line by line, the logic is evaluating data in each participant record as follows:
Connecting the Logic to Data Entry
These are screenshots of the data entry forms that contain the fields that capture the data the logic checks
Understanding the Data Entry Component
By default, data entry activity triggers REDCap to check ASI conditions. This means every time a participant record in your project is created or updated REDCap checks if the data that's been entered and saved to the record meets the conditions defined by the logic statement.
It's important to remember a record can be updated through manual data entry, the participant responding to survey, or through importing data manually or programatically.
Additionally, if a logic statement includes a temporal condition like our example does, via the datediff() function on the 4th line of the statement, REDCap runs additional ASI condition checks about every 10 minutes.
These ASI condition checks, whether triggered by data entry activity or run by the system to accomodate temporal conditions, will have one of the following outcomes.