For security reasons, any account that is not active at least once in every 180 days is suspended automatically.

REDCap users will receive an automated email from REDCap warning if this expiry is approaching.

To prevent account expiry, simply log in to REDCap prior to 180 days being reached.

To request account reactivation, email redcapadmin@uwa.edu.au

When completing the initial REDCap Project Request Form, there is space to name up to five colleagues to have access to the project.

To add additional REDCap users to a project, email redcapadmin@uwa.edu.au

University staff members, research students, or honorary staff are eligible to use the UWA REDCap instance for HREC approved research projects. 

Non-UWA research staff are eligible for a user account if sponsored by a UWA staff member related to the research project. Sponsors will need to apply for a Digital Guest Access on the researcher’s behalf. 

Please note that non-UWA users can only have Data Entry roles. All users are required to provide an institutional email address.

Automatically generated emails from REDCap are plain text without official branding, so emails such as an account invitation to create a password, or password expiry emails, may seem illegitimate.

If you have any concerns about the legitimacy of an email regarding REDCap, please contact redcapadmin@uwa.edu.au to confirm.

Calculated fields in REDCap can use data entered into a form in mathematical equations. For example, if research participants are asked to enter their date of birth, a calculated field can automatically supply the participant's age in years at the time of completing the form.

Calculated fields in the UWA instance of REDCap will sometimes only work while accessing REDCap from the UWA VPN on or while on campus. If experiencing problems creating calculated fields, such as the field entry options being unavailable, please try connecting to the UWA VPN. 

• Student guides to setting up the UWA VPN
• UWA Staff guides to setting up the UWA VPN

Issues with calculated fields may also by resolved by trying different browsers.

In general, it is not recommended to bookmark or link to specific pages in a REDCap project. Specific URLs like this contain the REDCap version number.

For example, this link references REDCap version 10.6.26:

https://www.redcap.research.uwa.edu.au/fmdhs/redcap_v10.6.26/DataQuality/field_comment_log.php?pid=226

When REDCap is updated to a new version number, this link no longer works.

Instead, bookmark or link to only the base URL: https://redcap.research.uwa.edu.au/

When a variable name is changed, REDCap treats this as a whole new variable which is read by the system as a different field from the previous field name. Any test data attached to this variable at the time of name change will be lost. When you move to production (before inputting any actual data) the field names will lock.

If changing a variable name in a draft project, please ensure you back up test data prior to the change.

If the layout or formatting of a question text in REDCap (ie; a Field Label) is not appearing correctly for some users, this is likely due to browser differences.

The display of formatting can vary between different browsers. Whenever you create a field label where the layout is important, you need to check it in different browsers: Edge, Firefox, Chrome, Vivaldi/Opera, Safari, etc.

Note also that layout can be very different if a user is accessing an instrument or survey on a mobile device.

You may use the same branching logic on multiple fields in a survey.

When editing branching logic, if REDCap detects the same branching logic is reused on another field, the following pop-up will appear:

"This branching logic is shared by multiple fields. Would you like to automatically update those fields now?"

Mistakenly clicking 'Yes' to this popup can edit branching logic on fields where this may not have been intended (ie. you may have intended for the one field you were editing to have different logic to the other fields).

Unfortunately, the only easy way to correct this is to re-load a backup of the Data Dictionary from prior to the edit.

If no usable backup exists, fields must be edited manually. The project's 'Codebook' can be searched for all instances of the updated branching logic, then each field which should not have that logic must be manually edited.