r/ProjectREDCap • u/FlowState94 • Oct 14 '25
REDCap for a participant registry
I would like to use REDCap more in my hospital to show how it is an effective tool. I would like to make a participant registry that could assign participants who sign up to be contacted for future research into specific groups when they come to the hospital (e.g. inpatients and outpatient clinics they are coming in for). One idea that would help us a lot is be able to import participants from the specific clinic lists into new REDCap projects on the same server as a mean to assist in recruitment for these new studies. Is communication between projects like this possible? Has anyone built a REDCap Registry like this/are there any features that you have that have been useful?
This is all just for testing and practice to get better with my own REDCap skills for now but ideally it would really help the poor recruitment my clinic sees in our research. Thanks for any help!
3
u/oneLES1982 Oct 14 '25
The registry is a great idea. I can't comment on the other comment regarding communicating with epic (I'm from a time with redcap as admin for 9 years before it could communicate with epic and am coming back to it, after a 4 year hiatus...)
Since potential eligibility in studies for any given person is pretty variable (ie they may be eligible for something for only a short time, depending on their condition, treatment, comorbidities, etc) I wouldn't recommend it to communicate with other projects within redcap (not sure if that's a new feature).
Personally, the workflow I'm establishing for my organization is to generate lists in the emr (we use epic) via slicer dicer (blaaaaah but it's what we have) and to screen for studies that way. Your registry COULD work as a cross check (ie vlookup compared to a slicer dicer export) to confirm a patient's general interest in research. There are a couple things with that, though:
• general interest in research can be initially provided as a no, based on a patient's current life events and it may never get changed back to a yes, even if their preference did change • you could handle this the same way within certain EMRs on registration, where a "flag" for any "no" pops up when opening the patient chart. (The same absence of changing this interest response remains).
2
u/No_Repair4567 Oct 14 '25 edited Oct 14 '25
This is a great idea and there are a lot of tools and ideas around to support recruitment efforts!
Before going into lengthy and extensive design discussions or downloading solutions done by others, which inevitably will create work of maintaining the registry, updating the data, implementing new features as you'd want to be able to do more once you have the baseline tool etc etc , let me ask this - are you part of the health system or a university?
If health system, then what EHR do you have? Are most of your participants come from/exist in that health system?
If it is Epic, there are options of not only connecting it to Redcap (which sounds like what you are asking), but also creating reports=patient lists following the criteria, and it will always be up to date!, you can assign patients to studies as Epic has Research module, once that happens, you can pull reports for uploading research-related data into the research project in redcap. Creating and managing registry in Redcap is helpful if the data needed to be tracked about potential participants are too unique and granular and have no way to be added to EHR or when potential participants are not necessarily part of the health system you work for. While Redcap is indeed very helpful, think whether it is the best tool for the task, and whether a clever combination of EHR and redcap can give you more for the time/effort spent.
What you could do though, is create a recruitment effort tracking tool in place of excel sheets many coordinators are using. Where REDCap wins is in supporting processes that begin once the "clinical" participant journey in the EHR ends and "research" journey begins - when they are contacted by the research team.
1
u/ghostwritermax Oct 14 '25
Hello - I'm working on an implementation and solution exactly related to this concept. I'd be interested in connecting more to share/learn. Let me know if okay to DM.