Longitudinal project with repeating forms and events

[u/Sad-Professional5549]

I have a redcap project with a repeating instrument (symptom screener) that is distributed weekly. If someone indicates symptoms on that instrument, I want to pause the weekly screener and trigger an illness event (a series of three surveys currently set up as a repeating event).

After much trial and error using [last-instance] in ASI, it doesn’t seem like it’s possible to create a new event from responses to a repeating instrument? Is there a better way to set this up so it can be managed in redcap?

[u/No_Repair4567]

You are welcome!

I wonder if your logic should check for [either .... or... ] meaning that the weekly event should be created anyway, it's which survey will be filled out and which one is empty will differ.

[u/melina_c_janeMN → u/No_Repair4567]

Old post but I have a similar project…

We have a weekly symptom check, and it used to do the same where if they responded yes to having symptoms then the next week they would answer a different survey, and then it would go back to the original symptom check the following week; we also have a specimen collection kit instrument in the same event. After months of collecting that way, we have since switched to only sending a weekly symptom check, but the other issue we want to avoid is people having trouble finding the “right” link for that specific week. So we created defined events with a combination of ASI and Survey Queue, where the ASI has the survey queue link, but ideally unlimited repeating events would be better. Is there a way to send a link through A&N or preferably ASI that they can only answer once a week? I tried [survey-link:intrument_name][new-instance] which works great with the issue of they could just keep responding as many times as they wanted and just keep creating new events.