In the IREx Study Setup, Reviewing IRBs/sIRBs can choose to have IREx notify relying sites when a study-wide amendment is posted, and request sites update their local considerations in IREx if necessitated by the study changes. If sIRBs choose this option, they can also opt to choose a number of days sites have to submit their updates in IREx. This feature is only available on studies in which the sIRB is collecting local considerations in IREx.
Category Archives: IREx Study Setup
New Feature: Reviewing IRBs can now upload additional documents to share with sites
Reviewing IRBs can now indicate in the IREx Setup if they’d liked to provide additional documents to help facilitate the site’s local submission process. This question is found on the SIRB Instructions tab of the IREx Setup and defaults to ‘No.’ If selecting ‘Yes,’ the Reviewing IRB will be required to upload additional documents and a new ‘Documents’ tab will appear on the study page for all users to access the additional documents.
New Feature: IREx provides tailored Agreement and Single IRB Instructions for sIRB studies
Single IRBs can now use IREx to provide tailored instructions to relying sites, significantly reducing administrative burdens and accelerating research timelines. When completing the IREx Setup, Single IRBs can include site instructions for:
- Executing Required Agreements: Instructions for executing the necessary agreements between the Single IRB and relying sites. No more one-size-fits-all approaches – adapt the instructions to communicate the agreement requirements for your study.
- Completing the Single IRB Process: Guide relying sites through the single IRB process with clear and concise instructions for both the relying site HRPP and study teams.
Note: After the sIRB confirms the instructions in the IREx setup, sIRBs or lead study teams (“IREx Study Managers”) can use the Status Summary page to send the instructions to sites.
New Feature: How-to videos are embedded in the IREx Setup on Agreements tab.
Two videos are embedded in the IREx Setup on the “Agreement” tab to help sIRBs know (1) what agreements can be offered on a study and how to add them and (2) how to offer a non-SMART IRB Agreement to an existing study.
New Feature: Capture any reliance agreements in IREx.
SIRBs can now use IREx to track broad or study-specific reliance agreements, such as an IRB Authorization Agreement (IAA) or MOU, for sites who are unable to join SMART IRB. These reliance agreements can be designated as “broad” – to be used across multiple studies – or “study specific” – for use on a single study only. An sIRB can offer both SMART IRB plus another reliance agreement on the same study; when this happens, Relying Institutions that are part of SMART IRB will automatically default to using SMART IRB so no additional tracking is needed.
New Feature: Tracking Combo Sites Now Supported in IREx
Combo Sites, defined as one study team engaging multiple FWAs for the same study, are now supported on IREx. In the past, SIRBs and Study Managers had no way to group sites together to ensure all documentation was in place before review. Moreover, relying sites had to duplicate information (e.g., PI Survey). Now, Combo Sites are marked with a blue link icon throughout IREx and have several features to ensure reliance documentation is completed by each FWA in the most streamlined way possible. For more information, please visit our resources page, organized by role on our menu toolbar and watch our Combo Site trailer on YouTube.
Updated Feature: Redesigned Participating Sites Dialog for Study Managers and sIRBs
Updated Feature: Study Registration Redesigned and Questions Added for Participating Sites
New Feature: Lead Site Display
For some studies, the institution serving as the Reviewing or Single IRB (sIRB) is not the lead site for the study. To distinguish roles and provide greater specification, IREx now allows the sIRB to identify a Lead Site. This information will be displayed in the first tab in IREx, now called the “Study-wide Approvals Tab”.
Updated Feature: Protocol Version
When creating a study or adding an amendment, a version name is required for the protocol. The “Protocol Version” field has been relabeled as “Protocol Date and/or Version” to clarify that users should enter the version number as entered on the protocol, which is often a date. In IREx trainings, users have also been encouraged to enter the amendment number in the summary of changes so that it is reflected on IREx and on email notifications sent out when changes are made.