Record allocation to treatment arms

[Courtney Hill]

Hi All,

Does anyone know if it is possible to move/change/reassign a record from one treatment arm to another in REDCap?

For my project, patients need to be added as a new record "registered (confirmed eligible)" first and then they will be assigned their treatment arm.

So far in REDCap all I can see is that you are made to add a new record and assign them to a treatment arm immediately. This doesn't work in my case because if a patient is not eligible first prior to assigning them to a treatment arm.

 any work around suggestions are appreciated!

[Luke Stevens]

Hello Courtney,

 

There are external modules you can use that facilitate copying of data from one place to another. "Copy Data on Save" could, for example, create a record in a particular arm based on the result of a randomisation in arm 1 (disclosure – it's one of mine).

 

Do you really need multiple REDCap "arms" though? In my experience it is very rarely the case that REDCap's "arms" functionality is necessary or desirable to support different treatment arms of a study. I tend to use arms only for modelling where the records are actually different things e.g. students/teachers. Do you really need multiple REDCap "arms"?

Regards,

Luke

 

From: redca...@googlegroups.com <redca...@googlegroups.com> On Behalf Of Courtney Hill
Sent: Wednesday, 26 May 2021 14:51
To: redcap open <redca...@googlegroups.com>
Subject: [EXTERNAL]Record allocation to treatment arms

 

CAUTION:  External Email. Please be cautious with attachments and clicking links

 

--
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/f745af5f-b299-403c-adcb-56bde2d1ba8an%40googlegroups.com.

This e-mail and any attachments to it (the "Communication") are, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Murdoch Children’s Research Institute (MCRI) ABN 21 006 566 972 or any of its related entities. MCRI does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication.

[Courtney Hill]

Hi Luke,

Thanks for getting back to me. I was hoping to use arms due to my two dose groups having two different treatment schedules (i.e. different tasks needing to be completed at different timepoints) My trial has a minimum of 10 cycles and the days change for task depending on the group and the cycle

Group 1 needs tasks done on Cycle 1 Days 1, 12, 15 & 19

Group 2 needs tasks done on Cycle 1 Days 1, 5, 8, 12, & 19

If I created all the days as their own events it would make the dashboard huge as I would end up with 30+ events (trying to avoid making it huge and potentially condense where able). Since the trial is so complex between the two dose groups and their treatment schedules it would require a lot of complex branching logic to run it just on one arm. I was trying to avoid having it so complex if it wasn't needed.

I agree the REDCap arms don't seem to be as functional as they appear from the outside.

Cheers,

courtney

[Matthew Rackham]

Hi Courtney,

You might find this helpful: https://clelandcm.github.io/REDCap-MOST/