eIRB FAQs

This page contains frequently asked questions about the new Penn eIRB system.

Frequently Asked Questions about eIRB

 

If you have additional questions about eIRB, please contact e-irb@pobox.upenn.edu.

General eIRB FAQs

The launch approach impacts all studies on the same day (exact date is TBD, but sometime in early February 2026). 

The IRB is shifting to a number format that uses a combination of year and count. For example, the first submission created in eIRB in 2026 would be 26-0000, followed by 26-0001. 

You may continue to use your legacy protocol number in study documents and cover letters. The system allows you to search by either the legacy or the new eIRB protocol number.

Migration of Existing Studies FAQ

HSERA will be accessible in a view-only format for one-year post-launch. You will be able to download documents as well. It is strongly encouraged that you obtain what you need during this one year period. After one year, the data will be archived, and access to HSERA will cease. IRB staff will have access to the archival data in cases where data or documents are needed for audits or inspections, etc. However, the data may not be in HSERA format. You can reach out to the IRB office if you need something retrieved.

They will be migrated, but show up as inactive in eIRB. You should remove them before or after migration for accurate record keeping.

Studies that have closed or expired within <1 year of eIRB launch will be available in eIRB for you to reopen, as needed. If the study has been closed or expired for more than 1 year as of the eIRB launch date, it will not be available in eIRB. In this latter case, you would need to resubmit the study for IRB review, which is also current IRB policy. 

The IRB will reach out to teams managing sIRB studies and work with them to add relying study sites to eIRB before or at eIRB launch. The IRB will assist with any issues as well as relying site access to the system. Teams managing sIRB studies should also notify their relying sites of the new system launch and prepare them for the transition from paper forms to e-forms and eIRB access.  After launch, research teams and relying sites should promptly review applications for completeness and site accuracy. For protocols requiring continuing review, ensure relying site accounts are set up before the review expiration date.

IRB approval letters will migrate.

Most field data will transfer, but some will not, due to system and application logic changes. Refer to this guidance document: https://upenn.app.box.com/s/y740gor0dk8vwqvb94cvtyyzfw576ild 

A very high-level history of the study will be available in eIRB, but the full submission history will not be migrated from HSERA. eIRB will provide a high-level overview of submission types, key dates, and the decision for the submission. To see the full protocol history you will need to access HSERA, which will remain view only for one year after launch.

Protocol study documents will not migrate. HSERA will remain view-only for one year, so documents can be retrieved if needed. Research teams must upload current documents and complete any missing information with their first submission in eIRB.

Draft submissions in HSERA will not be migrated. Draft submissions must be submitted by the deadline given by the IRB. Please refer to the eIRB webpage and IRB Bulletins for up to date deadlines. After that date, any unsubmitted drafts will be available in HSERA but cannot be edited or submitted. Note that you may submit an incomplete draft submission to be migrated, and request that the IRB return it to you in eIRB to finish the submission.

For paper protocols, the entire eIRB should be completed as only limited information is currently available in electronic form about these studies.

For HSERA studies, only certain critical fields need to be completed. Please refer to: https://upenn.box.com/s/tpj0fzgcaokp886s2o8t3kfxecng29ni as to what fields should be completed. You may fully complete the eIRB application, but the IRB is not requiring this because the IRB considers the original HSERA application to be IRB-approved.

Study teams will need to ensure that mandatory questions are complete and accurate (as applicable), upload all current documents, and include a cover letter that outlines the purpose of the submission. For example, when submitting an amendment, the cover letter should differentiate between documents being uploaded for application completeness versus documents being revised, to facilitate IRB review.

If the protocol isn’t migrated, you won’t be able to close it in HSERA after eIRB launch. Please contact the IRB office in these situations.

Policy Changes FAQs

Annual check-ins are required for exempt studies, expedited studies that do not require continuing review, and reliance agreements.

 

Annual check-ins are not required if there is already a continuing review requirement. In essence, it does not apply to GTMR and FDA-regulated research.

The annual check-in form will not undergo IRB review. The annual check-in is an administrative process solely intended to ensure that studies are not left open indefinitely without activity.  

It is expected that there will be an adjustment period as IRB staff and submitters adjust to using eIRB. eIRB has been designed to increase efficiency, so it is expected that turnaround times will be faster in the long-term. 

Many IRB forms that are currently in a Word document format will be deactivated. For example, the Word version of the following forms will no longer be used: Modification, Continuing Review, Deviations, Adverse Events, Exception Requests. There will still be some lesser used supplemental forms that require upload.  

As part of eIRB, the IRB will no longer store human research records indefinitely. All study types and review levels will be automatically archived six years after closure. Archiving deletes the study documents, approval letters, and most protocol data. A basic record with minimal information will remain for future reference.

eIRB Functionality FAQs

Personnel Related Functionality FAQs

Yes, they will be able to access prior submissions. For prior submissions in HSERA, only dates and approval status are visible in eIRB, without details. For new eIRB protocols, future team members will have full access to submission history. 

Yes, there is greater flexibility around this. You will be able to identify more than three study contacts. “Study Contact” will no longer be a personnel role. It will be a permission that you set for each study personnel. It is already defaulted for the PI, research coordinator, and regulatory manager roles. You will want to assign study contact permissions to anyone that you want to receive communications about the application. Additionally, study contact is no longer tied to edit permissions. This is a separate permission in eIRB. 

The system includes a mechanism to grant IRB delegate access. However, the PI is responsible for all submissions to the IRB. It is still required that the PI review and approve the submissions. If access is delegated, it is the expectation of the IRB that the PI’s approval will be documented via some other mechanism (e.g., an uploaded email that indicates approval). 

Anyone who is given edit access at the time of adding them in eIRB may address the comments and make changes to the application. Study contact and edit access are no longer tied together in eIRB to allow more flexibility. Designating someone as a study contact will ensure they receive communications about the study. Designating someone as having edit access gives them edit access to the application. 

Yes, external investigators may be added to the research team panel. Adding them via this mechanism allows their research engagement to be covered by the Penn IRB, assuming they do not have their own IRB to rely on. This will not give them access to eIRB. If an external person needs access to edit/view eIRB, the IRB would have to manually create an eIRB  account for them. A Penn key is NO LONGER required. Please contact the IRB if you need this. 

The system will send a in-system task and send follow up emails. For non-Penn users, you can upload a training document.

Any personnel can run reports for the studies on which they are listed as personnel. 

There is no limit to the number of Study Contacts on a study.

Yes; Please ensure that you submit a full amendment to change the PI.

Yes, you will be able to view a history of all personnel updates. If a review is required, you will be notified in the system and through an email notification.

Ancillary Committee / Research Support Office Related FAQs

Upon Department Chair sign off, ancillary review groups will receive a task for their review in eIRB. Ancillary committees will also have access to view submissions prior to this point if you need to consult with them prior to submission. Ancillary committee reviews and approvals (including, as applicable approval letters) will be documented in eIRB. At this time, there are no plans to migrate study documents from eIRB to other application. It is recommended that you consult with these committees to determine if they will be any changes in their submission requirements. 

RIS number

RIS number is not a mandatory field. However, contracting groups will search by RIS number in eIRB to find the associated IRB protocol. They may require you to enter it for their purposes. The IRB recommends that you add it via an amendment when you have the number to facilitate communications with contracting groups.

Funding Information

If you do not have this information at the time of initial review, select “Pending Proposal” to the question “Indicate if any part of your project is funded” within the Connect Projects panel. Here you can indicate the planned sponsor if the proposal is not selectable.

After IRB approval, study team members with edit access can update this section and link a proposal without submitting an amendment and prompting review by the IRB. Given this, with eIRB launch, IRB staff will begin enforcing updating these fields. 

It is a required field. If you don’t have the UPCC number at the time of IRB submission, you can enter “Pending” in field within the HRPP panel.

Other System Functionality FAQs

Yes, eIRB will provide increased transparency around the IRB review process and in cases where the level of review changes for a protocol. Refer to the Requirements table which informs the submitter about the current status of the review. 

eIRB has integrated in-system notifications and also generates tasks. The system also sends out emails for notifications and tasks. You will have some control over what notifications and emails you can opt out of.  For example, when it is time to submit a continuing review, the system will generate a task to do so. If the task is not completed, the system will send out notification reminders via email and within the system. 

Yes. The system allows you to move between panels even if not all questions are answered. 

Yes. You can download any revision as a PDF. Additionally, it gives you the option to select which sections/panels to include in the generated PDF. Look for the cloud icon with a down arrow near the top right. 

Yes. Once the protocol has been received by the IRB and has a status of IRB Review Pending or Preapproval Requirements the Request Mid-Review Edits option will appear. This is not available if the protocol is pending PI approval.

To request that the IRB return the application, open the IRB application for your protocol. Look for the light blue box at the top right of the eIRB screen that says Request Mid-Review Edits. This will send a request to the IRB staff member assigned. The IRB will decide whether it is appropriate to return the application depending on the state of the review.

The IRB defines a student project as a study that is written, led, and conducted by a student with faculty mentor oversight. This would include, but is not limited to, a PhD dissertation, Master’s thesis, etc. This could also include clinical residency projects as well. In these situations, the question should be answered no. The faculty mentor should be listed as the PI with the student listed as the Co-PI or Sub-I. 

You will find your documents in the panel next to the field where you uploaded them. 

Yes, you’ll receive email notifications and in-app notifications.

Yes, you can do this whether the protocol is open or closed. Within the protocol you want to copy, look for the light blue box at the top of the protocol that says “Copy Protocol.” Click copy. You can copy a protocol in its entirety, or you can select which sections of the application form you would like to copy.

Yes, look for the light blue box at the top of the IRB application entitled New Amendment or Continuing Review. Click request. In the drop down, select Continuing Review with Amendment. This will open up the IRB application for editing and generate the continuing review form to be completed. You cannot submit a continuing review and amendment as separate submissions at the same time. 

No. The application will be locked when someone else is already in the application. It is important that you close the protocol application window when you are not actively working within it to allow other study team members, the IRB and others the ability to work within the protocol.

The submission number appears in the Requirements panel under “Submission History,” where it is listed as the revision number.

Yes. When you initiate an Amendment or Amendment with Continuing Review (CR), the system reopens the original application so you can update information and upload any new documents. 

Latest status gives the approval status of the most recent eIRB protocol stage. A protocol stage in eIRB is one of the following submission types: initial, continuing review, or amendment.

Protocol overall status is the approval status of the protocol as a whole. 

You will need to submit a combined CR / amendment to update the Study Monitoring and Quality Control questions in the Risks and Benefits panel to correct this. 

The safety monitoring and quality control questions only populate when required, which is generally for protocols requiring full board review.