Skip to content

Submitting with IRBNet

IRBNet is an online submission platform used by the UNM IRB to conduct reviews. Researchers submitting protocols to the UNM IRB must use IRBNet. IRBNet houses all determinations, communications, and documents reviewed by the UNM IRB over the life of a project and archives documents after a project has closed. Each researcher needing access to the study in IRBNet must create their own account, setting up an individual user name and password (which is not linked to their UNM NetID). For assistance with using IRBNet, see the IRBNet Submission Instructions or attend an IRBNet workshop offered by the OIRB.

Benefits of IRBNet:

  • On-demand status updates - having a centralized system makes the review process more transparent
  • Easy access to IRB documents - all IRB documents are conveniently available in the same place, even for different projects
  • View project history - the system stores document histories so that the investigator and the IRB can see changes to documents over the course of the project
  • Keep track of deadlines - IRB deadlines across studies can be easily viewed to help the investigator stay compliant

Some important tips for submitting through IRBNet

  • IRBNet consists of projects and packages. A project is the umbrella term for all submissions related to one study/protocol. A package is one submission within a project, it could be an amendment, continuing review, response to requested modifications, etc. It is important to ensure that all submissions for a study are submitted in the exisiting project. Failure to do so will result in delays in IRB review.
  • The UNM IRB communicates during the review process through IRBNet and these messages are sent to the email account entered by the researcher when they create an account. If you are not getting IRBNet emails, then log-in to IRBNet and verify the email address in the user profile is correct.
  • After a new project submission has gone through review, the IRB may request modifications, or after approval, the researcher may want to make changes/amendments. In these instances, edited documents need to be uploaded using a version trail. To upload a document creating a version trail, use the pencil icon next to the exisiting document in IRBNet and then upload the edited document. This will remove the document from the lower table and it will appear in the upper table. You can verify that a version trail was created by clicking the stacked paper icon¬† to view documents in the trail. Failure to upload documents creating a version trail will result in delays in IRB review.
  • When submitting revised documents, make sure to use track changes. You will upload the document with the tracked changes visible. Do NOT submit a clean copy.
  • Students must share the IRBNet project with the faculty PI. PIs should be shared with "full" access. Projects without the PI on the project will not be reviewed.
  • The PI must sign the package in IRBNet. Students are not able to sign a package on behalf of the PI.
  • Once the researcher is ready, the final step is to submit the project. The OIRB/IRB is unable to see the submission until it is submitted. If the researcher sees work in progress (not submitted)¬†, then it is not submitted and not under review. Once a package has been submitted, it will say pending review .
  • If a package is unlocked, the review process pauses until revisions are marked complete. Once revisions are marked complete and the icon changes from a red unlocked padlock to a green locked padlock, the review process will resume. Researchers have 30 days to response to unlocked packages; unaddressed packages will be withdrawn.
  • All determination letters are available on the "Reviews" page of the project in IRBNet.