FAQs
- All
- CDEs
- Consent/Protocol Language
- Data sharing
- IRB
- Viral standards
It is customary to let the prospective participants know what data are being collected, how and whether data will be either anonymized or handled in terms of confidentiality – all of this is very much a part of any normal consent. How we convey this information needs to be accurate, accessible, and transparent so that…
If you don’t have that information, you can explain why you were unable to collect it. Whether you get data from a chart or from the patient themselves depends on your IRB-approved protocol.
Have a good relationship with the patients or the participants in the community, make sure that they’re treated with respect, and listen to them. There is so much that goes into developing a trusted relationship.
Submit as much data as you can and, if possible, conforms to the CDEs. If needed, we can have a one-on-one meeting with the particular project member, and just answer why it’s not possible to collect a certain element – that’s why we’re here.
We have created a checklist to help you make sure that the data you plan to share in the repository does not violate the Safe Harbor requirements. You would apply the checklist tool to the data before you ever share it with the DCC. You can find it here: https://www.radxrad.org/resource/hipaa-safe-harbor-checklist-from-for-radx-rad/.
The DCC will only accept de-identified data. Sites are responsible for de-identification of data prior to sharing with the DCC. We will determine a global study ID to link across the various repositories.
The projects funded by RADx-rad are research studies. These studies are designed for the purpose of developing and evaluating novel approaches to testing, diagnoses and surveillance. The research conducted by the RADx-rad awardees may contribute to better public health practices and surveillance models in the future. The de-identified data deposited in the NIH repository may be used for purposes…
Each awardee can discuss with their respective Program Officers whether a waiver for a particular CDE item is appropriate or if an amendment will be needed.
The central contact for DCC-related CDE questions is Kirk Roberts: kirk.roberts@uth.tmc.edu. Please also “cc” the RADx-rad central email address at: radx-rad-admin@ucsd.edu.
The latest set of minimum CDEs has been updated to reflect many of the concerns related to underserved communities. There are still questions related to race, ethnicity, disability, insurance status, etc. These are included precisely because NIH wants to gauge the involvement of underserved communities in the RADx-rad projects.
Within the chemosensory group it makes sense to add that prior smell or taste disorders to medical history for all participants. The purpose of the data standards meetings is for each project to agree on things that would be scientifically interesting to have across the project.
What we are recommending is to collect data according to the CDEs and not in a different format. Prospective data are those data that come into existence after your study begins and may require informed consent or a waiver of consent by the IRB. Consult with your IRB as needed.
Please see sample language below: “The data collected from you may be used for research that is not yet defined. If that occurs, your information will not be connected to your identity. We call that ‘de-identified. De-identified, individual-level, personal health data will be shared with the UC San Diego Data Coordinating Center. Since this information about…
CDEs are required for observational or interventional studies.
Questions can be sent to the RADx-rad central email address: radx-rad-admin@ucsd.edu
The CDEs are required for prospective data. Please contact your Program Officer to discuss the possible impact of including the minimum CDE changes on your project.
The DCC conducted a substantial process to identify which CDEs should change for pediatric projects. Ultimately, there was no real consensus beyond the wording of some CDE questions. At least one pediatric project has successfully petitioned for a waiver for CDE change. Please email Kirk Roberts (kirk.roberts@uth.tmc.edu) for an example that can be used for a similar waiver request.
No. Each project should have its own data collection mechanism. If there is a website that asks for viable/PHI information, it would be protected at the institution that is conducting the study.
As described in the above question, we will work with awardees and NIH to develop recommended CDEs for each research area including those do not involve human subjects (e.g., wastewater). Please note those that additional CDEs are not required, but highly recommended, in order to improve data interoperability across studies in the same research area.
For study variables in existing datasets that can be mapped to CDEs in the minimum set, DCC will work with awardees to transform those study variables to CDEs. However, it is not required that awardees re-contact subjects to collect minimum CDEs that are missed in the existing dataset.
We will provide examples of statements that can be adapted for use in consent documents to convey the rationale for requesting CDEs and how those data will be stored and shared.
We are selecting and producing variants now. Please reach a member of the Diagnostic Core or send your request to radx-rad-admin@ucsd.edu
Please reach a member of the Diagnostic Core or send your request to radx-rad-admin@ucsd.edu
We will work together with awardees and the NIH RADx Data Hub team to develop recommendations to CDEs for each FOA. We are setting up meetings with awardees for each FOA group, to discuss CDEs suitable for each research area. Please join us at those meetings so that we can hear your thoughts. We can…
You can use your own internal Identifier (ID). Or you may use the tool in https://www.radxrad.org/resource/rtb/ to generate Study IDs.
Yes, you may have to amend your IRB protocols to include the minimum CDEs, if they are not already included in your existing protocols. Feel free to join our weekly office hours on IRB issues.