REDCap Terminology: Arms: group events into 'arms‘; there may be one or more arms/groups per project. Each arm can have as many events as needed. Branching Logic: Branching Logic may be employed when fields/questions need to be hidden for data entry under certain conditions. Calendar: project calendar to help organize the patients’ scheduling and keep track of any upcoming events. Data Collection Instrument: survey page or data entry form Data Dictionary: Excel .csv file, containing the list of fields of a given project and their associated attributes. Events: allow for the utilization of data collection forms multiple times for any given project record (often used when collecting longitudinal data). An 'event' may be a temporal event in the course of a project, such as a participant visit or a task to be performed Field Label: the text that will be visible to researchers and/or participants during data entry. File Repository: repository that stores and retrieves files and documents used for a project. Whenever a data export is performed, the resulting data and syntax files are also stored in the file repository of the project. Project Status: development, production, draft, inactive and archived. Project Type: Traditional Project: Classic model with data entry forms Single Survey Project: utilizes only one data collection instrument Longitudinal Project: multi-use data entry forms with abstract time points Longitudinal Project + Scheduling: multi-use data forms with defined time points Operations: use case for non-study/non-trial Variable Name: the name of the variable that is stored in REDCap (not visible during data entry).
User Rights User Rights: Project owners will be access to the “User Rights” section of REDCap. This will allow them to assign project permissions to project personnel. The following user rights are available: User Right Access Notes Potential to Access Protected Health Info (PHI)? Data Entry Rights Grants user “No Access”, “Read Only”, “View&Edit”, “Edit Survey Responses” rights to the project’s data collection instruments. WARNING: The data entry rights only pertain to a user's ability to view or edit data on the web page. It has NO effect on what data is included in data exports or downloaded to a device*. YES. If access to a form with PHI is “Read Only” or “View&Edit”, user will be able to view PHI. Manage Survey Participants Grants user access to manage the public survey URLs, participant contact lists, and survey invitation log. YES. Email addresses (PHI) may be listed for the participant contact lists and invitation logs. Emails can be downloaded to a device.
Calendar Grants user access to study progress and allows user to update calendar events, such as mark milestones, enter ad hoc meetings. In combination with the scheduling module the calendar tool can be used to add, view and update project records are due for manipulation. YES. PHI can be entered and viewed in the “notes” field. Data entered can be printed to PDF and downloaded to a device. Data Export Tool Grants user “No Access”, Only” and “Full Data Set” access to export all or selected data fields to one of the 5 default programs in REDCap (SAS, SPSS, R, Stata, Excel). Default Access: access shifts all dates even if they are not marked as identifiers. text fields and note fields (free text) are also automatically removed from export. WARNING: The option is contingent upon correctly flagging identifiers in each field. It is advised to mark all PHI fields as identifiers and restrict export access to YES. PHI can be exported and downloaded to a device. Exporting data is NOT linked to Data Entry Rights. User with Full Export Rights can export ALL data from all data collection instruments. Please see “Data Export Tool” FAQ for additional info. Data Import Tool Grants user access to download and modify import templates for uploading data directly into the project bypassing data entry forms. WARNING: This will give the user the capability to overwrite existing data. Blank cells in the data import spreadsheet do not overwrite fields with data. Data Comparison Tool Grants user access to see two selected records side by side for comparison. Extremely helpful when using double data entry. YES. PHI can be viewed. Data can be printed and downloaded to a device. ALL data discrepancies for all fields in project are displayed identified
and can be downloaded to user with access to this module – NOT linked to Data Entry Rights or Data Export Tool Rights. Logging Grants user access to view log of all occurrences of data exports, design changes, record creation, updating & deletion, user creation, record locking, and page views. This is the audit trail for the project. Useful for audit capability. YES. ALL data entered, modified and changed is listed in module, can be viewed and downloaded to a device. File Repository Grants user access to upload, view, and retrieve project and documents (ex: protocols, instructions, announcements). In addition, it stores all data and syntax files when data is exported using the Data Export Tool. WARNING: While users with restricted data export rights will not be able to access saved exports, they will be able to view any other sensitive information stored in the file repository such as photos or scanned documents. Limit this privilege to those who should have access to PHI. YES. Depending on Data Export Tool rights, PHI can be downloaded to a device. User Rights Grants user access to change the rights and privileges of all users on a particular project, including themselves. WARNING: Granting User Rights privileges gives the user the ability to control other users’ project access. This user should be very trusted and knowledgeable YES. User can change own User Rights and grant access to any module where PHI can be viewed or downloaded to a device.
about the project and REDCap. Giving user rights to team members should be a carefully thought out decision. The consequences of poor user rights assignments could be damaging to both the security and integrity of your project. For instance, giving record deletion or project design rights to an unqualified person could result in data loss or database integrity issues. Data Access Groups Grants user access to create and add users to data access groups. User should not assign their self to a data access group or they will lose their access to update other users to data access groups. Therefore, user with this privilege should be able to see all project data regardless of group. For multisite studies this allows the ability to place barriers between sites' data (i.e. group A cannot see, export, or edit group B's data). Graphical Data View & Stats Grants user access to view simple statistics on each field in the project in real time. If user does not have access to a data collection instrument, that instrument will Outliers can be identified and clicked on which will take you immediately to the record, form and field of the individual with YES. Depending on Data Entry Rights, PHI can be viewed.
not be listed on the page. the outlier data. Data Quality Grants user access to find data discrepancies or errors in project data by allowing user to create & edit rules; and execute data quality rules. If user does not have access to a data collection instrument that the query is referencing, access will be denied for query results. YES. Depending on Data Entry Rights, PHI can be viewed. Reports & Report Builder Grants user access to build simple queries within the project. If user does not have access to a data collection instrument that the report is pulling data from, access will be denied for report. For complex querying of data, best results are acquired by exporting data to a statistical package. YES. Depending on Data Entry Rights, PHI can be viewed. Project Design and Setup Grants user access to add, update or delete any forms within the project. Also allows user to enable and disable project features and modules. This should be allocated only to trained study members and should be limited to a very few number of users per study. Lock/Unlock Records Grants user access to lock/unlock a record from editing. without this right will not be able to edit a locked record. User will need “Read Only” or “View&Edit” to lock/unlock a data collection instrument. A good tool for a staff member who has verified the integrity of a record to ensure that the data will not be manipulated further. Works best if few team members have this right. Yes. Depending on Data Entry Rights, PHI can be viewed.