A note on RDCRN IDs

The vast majority of applications in the cloud-based RDCRN data ecosystem (e.g., RDCRN Box, RDCRN REDCap, RDCRN Complion, etc.) are accessible to RDCRN members via a process called “Single Sign-On”: members use the same credentials and the same authentication process to log in regardless of which application they intend to use. Additionally, once a member has authenticated, all applications are accessible for a certain period of time without having to re-authenticate. This should greatly enhance the end-user experience as well as simplify the DMCC’s tasks when provisioning and de-provisioning accounts and permissions.

As part of this single-sign-on implementation, RDCRN members are assigned an “RDCRN identity” when their account is created by the DMCC. For the most part, this identity is not explicitly used by members, but they may see their RDCRN ID in some applications (e.g., in their user profile).

RDCRN IDs are auto-generated and generally have the following format:

For example, Joe User with an email address of joe.user@xyzhospital.com might be assigned the RDCRN ID Joe.User.XYZHospital@rdcrn.org. This ID is used in the context of RDCRN applications only and should not be used outside of the RDCRN data ecosystem. Emails sent to an RDCRN ID are automatically forwarded to the email address on file with the DMCC - but RDCRN IDs should not be used as email addresses by users or non-RDCRN applications.

RDCRN IDs are meant to be immutable, i.e., they should never change after they are created. If your RDCRN ID does not reflect your current name or institutions, please don’t be alarmed as it is exclusively for RDCRN-internal use. Members will be able to change their profiles (including names, institutions, contact addresses etc.) in their members' profile on the Members' Landing Page.