Selected fields for repeating events

[Sonia Picht]

Hola! Fellow REDCap people!

I hope all is well with you!

I am working on a REDCap design right now.

Basically I don't want to alter the flow of questions for the first baseline survey while I have to ask only selected questions for the next survey.

So I will have to break down a string of questions into fragmented instruments.

Is there a way to ask only selected fields depending on the defined events?

Thanks!

Have an awesome day!

Sonia

[David Edwards]

Hi Sonia,

I might be misunderstanding what you need here but if you wanted to hide certain questions on an instrument depending on what event it appeared under, you could use the @IF() action tag on said fields like this:

@IF([event-name]='my_event_arm_1', @HIDDEN, '')

If there are more caveats you can nest those @IF(action tags). I've not actually tried this out so might take a bit of experimentation but it should work.

Good luck,

David.

---

From: redca...@googlegroups.com <redca...@googlegroups.com> on behalf of Sonia Picht <sonia...@gmail.com>
Sent: 14 October 2023 16:57
To: redcap open <redca...@googlegroups.com>
Subject: Selected fields for repeating events

 

--
You received this message because you are subscribed to the Google Groups "redcap open" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redcap_open...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/redcap_open/a036720d-ef99-4132-958b-d591f30a6108n%40googlegroups.com.

[Sonia Picht]

Yes yes!!! This will work!!!

Thank you so much for helping me, David!

Sonia

[Peter Macisaac (POP)]

You can also hide questions using display logic

On top of head it seems that display logic and @hidden action tag perform the same function

Wonder if others can think of any advantage of using one over the other

Peter

To view this discussion on the web visit https://groups.google.com/d/msgid/redcap_open/2dca3b26-e168-4863-a656-8c98be96bb6en%40googlegroups.com.

[Sonia Picht]

Peter,

Thank you so much!!!!

As of now, what David told me - IF/HIDDEN action tag- works great. 

But I will try display logic as well. 

Thank you, Peter!!!!

Sonia

Sent from my iPhone

On Oct 15, 2023, at 3:37 AM, Peter Macisaac (POP) <pe...@macisaacinformatics.org> wrote:

You can also hide questions using display logic

[David Edwards]

I'm glad it worked Sonia - but I would definitely try what Peter suggested instead - because that's the built-in way to show/hide stuff in REDCap based on conditions - I'm a bit embarrassed I didn't think of that first! But thanks Peter for picking that up.
All the best,

David.

---

From: redca...@googlegroups.com <redca...@googlegroups.com> on behalf of Sonia Picht <sonia...@gmail.com>

Sent: 15 October 2023 13:40
To: Peter Macisaac (POP) <pe...@macisaacinformatics.org>
Cc: redcap open <redca...@googlegroups.com>
Subject: Re: Selected fields for repeating events

 

To view this discussion on the web visit https://groups.google.com/d/msgid/redcap_open/C2DB64B9-4473-4DEE-88F6-6AD0DEBD3287%40gmail.com.

[Sonia Picht]

David and Peter,

I just looked into display logic. Display logic is selecting certain "instruments" per event. What I wanted to display in a certain event is selective "fields" within instruments. 

So for my need this time, I will use "IF/HIDDEN" action tag, because I do not want to break a set of questions into multiple instruments.

Thank you both, David and Peter!!

This community is really helpful. 

While REDCap is a great tool, searching for the specific application is often hard to figure out without any help.

I truly appreciate your help.

Thank you!!!!!

Sonia

[David Edwards]

Hi Sonia - just a quick one from me - I think Peter meant branching logic, not form display logic.

So whatever conditions you were putting in the @IF() action tag, you could take and put in the branching logic for those fields instead. However, please bear in mind that branching logicworks in revers  to the @IF/@HIDDEN tges - so you need to give it the condition for the fields to be visible, rather than hidden.

So for example if you had the following condition on a yes/no field ...  @IF(([field1]='0' or [field1]=''), @HIDDEN, '') ... then you would need to put this in the branching logic ... [field1]='1'

or you could just put brackets around the whole thing and put an exclamation mark at the front to achieve the same thing !([field1]='0' or [field1]='')

Again, forgive me for giving you a bit of a bum steer in my first answer. I hope I havent confused things too much. But as Peter advised, I think branching logic is definitely the way to go for this.

All the best,

David.

---

From: redca...@googlegroups.com <redca...@googlegroups.com> on behalf of Sonia Picht <sonia...@gmail.com>

Sent: 15 October 2023 15:48
To: redcap open <redca...@googlegroups.com>

To view this discussion on the web visit https://groups.google.com/d/msgid/redcap_open/1627342e-4c6d-4374-abaa-f75d7e3f8559n%40googlegroups.com.

[Sonia Picht]

David,

Thanks so much for giving me one more way to implement it. 

I tried and changed all action tags into branch logic, and yes! they work well.

I will keep the branch logic way, because I can see it in the field editor (designer) as opposed to action tags don't show the logic details.

I really appreciate your help.

Thanks!!!!!

Sonia

[David Edwards]

Oh good I'm glad that worked. Thanks to Peter for spotting that.

Cheers,

David.

---

From: redca...@googlegroups.com <redca...@googlegroups.com> on behalf of Sonia Picht <sonia...@gmail.com>

Sent: 15 October 2023 22:15

To view this discussion on the web visit https://groups.google.com/d/msgid/redcap_open/2cc3583c-0cab-4b12-aea9-cfd85e59ccfen%40googlegroups.com.

[Rain Bosworth]

Hi, I have been following this thread because I am trying to do a similar @if action, instead the following:

 

If any one of four consent forms is signed by both subject and researcher, deploy four background questionnaire survey for them to fill out… easy….

But then, if a 2^nd consent form is signed (like a participant joins a 2^nd study), do not deploy a survey that has already been completed.

 

I assume this is:  if [instrument-name] is not blank or status is incomplete, send in the ASI?  What script would I use for that?

 

Thanks

Rain

--
You received this message because you are subscribed to a topic in the Google Groups "redcap open" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/redcap_open/JGEFcLz8hGs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to redcap_open...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/redcap_open/DB9P193MB12575188B98F50CFEFB8F04BBFD0A%40DB9P193MB1257.EURP193.PROD.OUTLOOK.COM.

[Sonia Picht]

Hi Rain! 

I think you can use branch logic to open up the questionnaire.

[consent_1] = '1' OR [consent_2] = '1' OR [consent_3] = '1' OR [consent_4] = '1' 

The questionnaire will show only once.

Let me know if this answers your question.

Sonia

[Peter Macisaac (POP)]

Yes I did mean branching logic -  apologies for senior moment

As David points out branching logic is designed to do this job and there is I think a range of background logic and support that helps us use this function - I would us this before @HIDDEN for your needs

I often use the hidden field that covers the form status

 {form_name_complete]

If a survey is finished it is marked as complete - this is a way to know if an instrument has been opened and completed

[assessment_complete]

Section Header: Form Status Complete?

dropdown 0 Incomplete 1 Unverified 2 Complete

Peter

To view this discussion on the web visit https://groups.google.com/d/msgid/redcap_open/168c94f2-2b1d-4000-a8f5-cac2efb23decn%40googlegroups.com.

[Jean Tittley]

Hi Rain

If I’m right, your issue is to prevent opening a survey that has already been completed, and this can be managed independently of any other form (your consent forms). In the form display logic, I would try this condition for keeping forms active :

[[instrument-name]_complete] <> '2'

In fact I don’t know if the brackets into brackets will work. If not, you throw away the smart variable instrument-name and you it separately for each form, and I guess it will do the job.

Hope this helps

Jean

[Sonia Picht]

Peter, 

Thanks!

Yes, both branch logic and Action tag works for my purpose, and I use branch logic.

Thank you.