Skip to main content
search
Category

REDCap

May 05
Love0

Successful REDCap Transition to Okta

By News, REDCap

Friday, May 15th 8:00PM CST: REDCap has been successfully transitioned to the Okta/CNetID login method. Going forward, please use your CNetID and password through Okta authentication when accessing REDCap. If you are experiencing any problems logging in or notice anything unexpected, please contact REDCap Support at redcap@uchicago.edu so we can address it promptly. Thank you for your patience and support during this transition.

Below are Frequently Asked Questions (FAQs) to help our REDCap user community navigate this transition:

1. What is Okta?
Okta is the University’s secure identity and access management platform. It provides single sign-on (SSO) capabilities, allowing users to access multiple applications, now including REDCap, using one set of credentials (your CNetID).
2. What is a CNetID?
A CNetID is your University-issued username used to access central University systems and services. It will now be the standard login credential for REDCap as well.
3. What is changing?
Login access to REDCap will no longer utilize BSDAD or UCHAD active directory credentials. Instead, users will log in using their University CNetID through Okta authentication.
4. Why is the REDCap login method changing? 
REDCap login method is moving to CNetID login via the University’s Okta platform to ensure a more secure, centralized, and consistent login experience, as well as to align with University-wide identity standards.
5. Who is affected by this change?
All University of Chicago and Medical Center REDCap users, including external account collaborators, will be affected. Survey participants will not be impacted (as survey links do not require logging in).
6. How do I log in to REDCap after this change?
Users can continue to access REDCap through the login page: https://redcap.uchicago.edu/. Users will be redirected to the University’s Okta login screen, where they will log in using their CNetID to gain access to REDCap.
7. Where can I look up my CNetID?
Navigate to the WhoAmI website https://cnet.uchicago.edu/WhoAmI/, select Name from the Search on dropdown, enter your first and last names, and hit enter.
8. Do I need to take any additional steps before or after the transition?
No, all existing active user accounts (BSDAD, UCHAD, external collaborator) were mapped to their corresponding CNetID ahead of this transition.
9. What if I have login issues after the transition?
Contact REDCap support at redcap@uchicago.edu with any initial issues. If we determine the issue is not related to the Okta transition (such as a disabled CNetID or an expired password), we will redirect you to the appropriate service desk (UCMIT Service Now Portal or BSDIS Service Desk) for additional account assistance, as REDCap Support does not own or manage CNetID accounts or passwords.
10. I am able to log in with my CNetID, but I no longer see My Projects.
Contact REDCap support at redcap@uchicago.edu with your previous account (BSDAD or UCHAD) and your CNetID so that we can transition your projects asap.
11. Is the external collaborator account request process changing?
No, all new account requests for external collaborators should still be submitted through the BSDIS Service Desk’s Collaborator Account Request website: https://collab.bsd.uchicago.edu/. Please contact the BSDIS Service Desk at bsdis@bsd.uchicago.edu or 773-834-4000 for help with new account requests.
12. Where can I stay updated on this transition?
We encourage you to stay informed by visiting this same page for further communications regarding this transition.
Mar 05
Love0

REDCap Downtime and Upgrade

By News, REDCap

Event: REDCap Scheduled Downtime and Upgrade

Date/Time: Friday, March 13th, 2026, 5PM

Website: https://redcap.uchicago.edu

Reason: REDCap will be upgraded to the latest version to introduce new functionality and apply critical security enhancements.

Who Is Affected: All University of Chicago REDCap users, including non-UChicago external collaborators, mobile app users, API users, and survey participants.

Impact: REDCap will be unavailable starting at 5PM for approximately 2–4 hours. Unavailability is defined as:

  • Survey emails (manual and automated) and Alerts & Notifications will be halted until the upgrade is complete.
  • Survey links will be inaccessible and will display a REDCap is offline message when clicked on.
  • API activity will be halted until the upgrade is complete.

Updates: A message will be posted on the REDCap login page confirming the upgrade’s completion, along with details of the newest features and improvements.

Questions? Please email REDCap Support.

Jul 18
Love0

REDCap Scheduled Downtime

By News, REDCap

Event: REDCap Scheduled Downtime
Date/Time: Friday, July 25th, 2025, 5PM-6PM CST
Reason: The application will be down for scheduled maintenance.
Who Is Affected: All University of Chicago REDCap users, including non-UChicago external collaborators, mobile app users, API users, survey participants.
Impact: REDCap will be unavailable during this downtime. Unavailability is defined as:

  • Survey links will be inaccessible and will display a ‘REDCap is offline’ message when clicked on.
  • Survey emails and Alerts & Notifications will be halted until the maintenance is complete.
  • API activity will be halted until the maintenance is complete.
  • Mobile app users are strongly encouraged to sync any data on their devices back to their REDCap project before the maintenance begins. Although not recommended, offline data collection may continue in the app during the maintenance, however the online sync process will not be available until the maintenance is complete.

Updates: A message will be posted on this page confirming the maintenance completion and system availability.
Questions? Please email REDCap Support.

Jun 15
Love0

REDCap Page Loading Issue

By News, REDCap

Monday June 16th 8:00AM CST – REDCap may continue to experience sporadic page loading issues whereby a page may stop working or keep processing with no completion, including this login page. If you continue to encounter this issue, 1) disable all your browser extensions, 2) open an incognito window, 3) log into and work in REDCap via the incognito window. If this does not solve the issue, please contact REDCap Support and include the browser version, page URL, and the error time. Thank you for your continued patience and cooperation!

Nov 09
Love0

REDCap Upgrade Complete and Service Restored

By News, REDCap

Saturday 11/9/24 7:00AM CST: REDCap is back online and available for use. Please view the new features and functionality here. We sincerely apologize for the inconvenience this outage caused and appreciate your patience while we restored service. Please contact REDCap Support with any further questions. Thank you.

Event: REDCap Scheduled Downtime and Upgrade

Date/Time: Wednesday, November 6th, 2024, 5PM-7PM CST

Website: https://redcap.uchicago.edu

Reason: The REDCap application will be upgraded to a newer version of the software.

Who Is Affected: All University of Chicago REDCap users, including non-UChicago external collaborators, mobile app users, API users, survey participants.

Impact: REDCap will be unavailable during this downtime. Unavailability is defined as:

  • Survey emails and Alerts & Notifications will be halted until the upgrade is complete.
  • Survey links will be inaccessible and will display a ‘REDCap is offline’ message when clicked on.
  • API activity will be halted until the upgrade is complete.
  • Mobile app users are strongly encouraged to sync any data on their devices back to their REDCap project before the upgrade begins. Although not recommended, offline data collection may continue in the app during the upgrade, however the online sync process will not be available until the upgrade is complete.

Updates: A message will be posted on the REDCap login page confirming the upgrade’s completion, along with details of the newest features and improvements.

Questions? Please email REDCap Support.

Oct 16
Love0

REDCap Email Improvements

By News, REDCap

The following is a summary of improvements being made on Wednesday, October 16th, 2024 for the handling of outgoing REDCap email messages.  There will be no application downtime needed for these improvements, as they will happen on REDCap’s back-end email message handling setup.

All University and UCMC REDCap users including external collaborators who send email messages within REDCap will be affected. This includes email messages sent as part of:

  • Survey Invitations (both manual and automated, and reminders)
  • Alerts & Notifications
  • Survey Confirmations

The need for these improvements comes from email providers blocking emails whose ‘From:’ address does not match the domain name of the REDCap server (e.g., sending an email from user@uchospitals.edu from the server https://redcap.uchicago.edu). The following email address domains are now permitted to send email messages from our REDCap server, therefore, no blocked messages should occur going forward:

  • uchicago.edu
  • uchospitals.edu
  • uchicagomedicine.org
  • bsd.uchicago.edu
  • (department).bsd.uchicago.edu
  • dacc.uchicago.edu
  • radonc.uchicago.edu
  • ingalls.org
  • chapinhall.org

All other email address domains (not in the list above) will have no-reply-redcap@uchicago.edu as the ‘From:’ address (although the message will still have the ‘Reply-To’ value as the sender). This piece will mostly affect, for example, multi-site studies where external collaborators (e.g., Rush, Mayo, etc) are sending email messages from within UChicago REDCap projects.

Lastly, as a general rule to improve email delivery to inboxes, please refrain from sending email messages from external email accounts (e.g., Gmail, Yahoo, etc.) and instead always use an institutional email address.

Questions? Issues? Please email REDCap Support.

Feb 20
Love0

OHRP Interactive Informed Consent Training

By REDCap

The Office for Human Research Protections (OHRP) has created and posted a brand new interactive informed consent training program entitled “Participant-Centered Informed Consent Training”.  It consists of 6 modules and is intended to provide training to help design, create, use, and review consent forms or templates.

This training is intended to provide education that will aid in providing research participants with understandable content in the consent form document so that the participant can better understand the research taking place and how their decision on whether to participate could impact them personally. OHRP notes in the training modules that when participants understand the research and potential personal impact, it promotes trust and engagement in research.  It is important to note that this training is not intended to be a comprehensive overview of the regulatory requirements of informed consent.

OHRP describes the intended audience of this training to be anyone from an investigator or research coordinator to an IRB reviewer or even someone designing electronic consent forms for an online platform. The training is available now on OHRP’s website.  OHRP will also be conducting a demonstration of this new interactive training program on February 23, 2024, at 12:00 PM EST via this Zoom link.

Original News Source: University of Chicago – Office of Clinical Research, February 2024 Newsletter (Volume 13, Issue 8)

Feb 20
Love0

FDA Updates Guidance on Collecting Race and Ethnicity Data

By REDCap

The FDA recently issued a draft guidance entitled “Collection of Race and Ethnicity Data in Clinical Trials and Clinical Studies for FDA-Regulated Medical Products”. This guidance document would replace the current guidance document from 2016 entitled “Collection of Race and Ethnicity Data in Clinical Trials”. This new guidance document is meant to set FDA expectations and standards for collecting race and ethnicity data in submissions. Standardizing language and setting expectations for race and ethnicity data in this guidance document ensures that this data is consistently collected and reported to the FDA.

The FDA notes in this guidance document that collecting and reporting race and ethnicity data using standardized terminology is critically important in identifying population-specific signals, which while uncommon, have been observed in racially and ethnically diverse populations.

The draft guidance is proposing a two-question system for documenting race and ethnicity data in Clinical Trials and Clinical Studies using first “Are you Hispanic/Latino or not Hispanic/not Latino?” followed by “What is your race?”. They recommend the following options at a minimum for a response to this question regarding race: American Indian or Alaska Native, Asian, Black or African American, Native Hawaiian or Other Pacific Islander, and White.  They list OMB Policy Directive 15 recommended language regarding ethnicity and race question responses, noting that nonwhite is not demographic data that can be reported to the federal government. The FDA guidance recommends following best practices by having participants self-report their ethnicity and race rather than it being assigned by study team members, as well as instructing the participants to mark one or more race if needed in their self-report.

It is noted in the draft guidance that the FDA does recognize that racial and ethnicity data and recommendations provided in this guidance are focused in United States and may not be applicable to clinical trials that occur outside of the US and if more granularity is needed to follow the 2011 HHS Implementation Guidance on Data Collection Standards for Race, Ethnicity, Sex, Primary Language, and Disability Status.

The FDA also recommends in this guidance document that Investigation New Drug (IND), New Drug Applications (NDA), and Biologics License Applications (BLA) use the race and ethnicity guidelines laid out within this proposed guidance document to tabulate demographic data for new clinical trials and clinical studies.

This guidance document is open to comments from the public until April 29, 2024.

Original News Source: University of Chicago – Office of Clinical Research, February 2024 Newsletter (Volume 13, Issue 8)