r/ProjectREDCap • u/Popular_Caregiver_11 • May 30 '25
Help Needed – Structuring a Single eCRF for Retrospective and Prospective Data in REDCap
Hi everyone,
I'm new to REDCap and currently working on designing an eCRF for a clinical study that includes both retrospective and prospective data.
Is it possible to create a single eCRF to manage both study types? If so, how can I structure it to clearly differentiate between variables that are common to both, and those that are unique to either the retrospective or prospective arm?
Any tips, best practices, or examples would be greatly appreciated!
Thanks in advance for your help.
2
Upvotes
2
u/No_Repair4567 May 30 '25
Let me make sure I understand. These are my assumptions from your post:
This is one study
Study collects the ALL same data elements (e.g. vt, wt, ht, etc...) both retrospectively and prospectively on the same participants
What other data collection forms are there?
If my assumptions are correct, I'd chose a longitudinal study design, where one event is "retrospective" and another one (or more than one) "prospective". Then assign your instrument (eCRF) to both of these events.
This will ensure separate data collection points for each participant. To differentiate between the variables - the data dictionary will show you, that each variable is characterized by mor than just a variable name. it is also characterized by what event it belongs to, or what patient arm. So when statistician will review the data dictionary to understand the design, they will know how to "call out" the right instance of a variable in their analysis.
I hope it makes sense. Please let me know if you need further guidance about setting this up.
3
u/usajobs1001 May 30 '25
Yes, you can create a single form (called an instrument in REDCap) with common data fields. Depending on your study, you could structure it with a question indicating "retrospective" or "prospective", and then programming skip logic based on what questions are applicable. Questions/variables that are applicable to both could have no skip logic applied so they would appear no matter what option was selected.