IRIS FAQ's and known issues

If the following frequently asked questions and known issues do not resolve your issue, please check the IRIS guidance materials before requesting additional support.

IRIS guidance materials, training and support

Frequently Asked Questions

A 403 Error message appears when trying to access IRIS from an unsecure network. To rectify this, use the University's network or connect to a University VPN service.

403 error

403 Error Message

 

Find out more about VPN use at the University 

Sessions time out on IRIS after a set period of inactivity. You will then be taken to the log in screen shown below. Clicking the link "Log in with IRIS" in the second box will redirect you to the University's Single Sign On (SSO) log in screen. Your SSO credentials will allow you to log back into the system.

log in screen

IRIS Log In Screen

Clicking the link "Log in with IRIS" in the second box will redirect you to the University's Single Sign On (SSO) log in screen. Your SSO credentials will allow you to log into the system and view the content of the link in the email notification.

log in screen

You received an email notification similar to the one below.

action email ea

Clicking on the link in the email takes you to a screen similar to the one below. Enter the resolution to your action in the "Action Taken" field.

action close out

Click "Submit". The action will now be closed.

As the name suggests, this means that a crucial piece of information has not been provided in the review of the incident. There are three ways this status can be generated:

1. The question 'Is a Risk Assessment required?' has been answered as 'Not known'

Consult with your Area or Divisional Safety Officer as to whether a risk assessment is required or not. This will need to then be updated in the DSO Review with a definitive yes or no response.

2. The question 'Was the employee absent from work?' has been answered as 'Not known'

Often this is done as the information was not available when the DSO Review was completed. This will need to be updated.

Please Note: Employee Absence

This field should only be completed for injured parties or potentially exposed persons who are employees of the University. All other groups e.g. contractors, members of the public and students, are not employed directly by the University and therefore the correct option should be N/A.

 

3. The question 'Was the employee absent from work?' has been answered as 'Yes' but no return to work date has been entered.

Like with scenario 2 above, this information may not be available at the time the DSO Review was completed. This will need to be updated.

Please Note: Updating the Reportable Classification

The reportable classification field may need to be updated in light of employee absence. Please refer to the relevant guidance document for advice.

 

Allow for any calculations being run in the system to finish. These are normally shown by a spinning wheel and the word calculating as shown below.

calculating

Refresh the page. The statuses should now have updated.

Known issues on the IRIS system

Details of any known issues awaiting a solution will be listed here:

  • IRIS Log In Screen - The log in screen displays email and password fields implying these should be used to log in. This is for use by system administrators only. Use the 'Log in with IRIS' button to be redirected to the University's SSO log in page.
log in screen

IRIS Log In Screen

 

System updates

The following updates to the IRIS system have taken place or are due to take place:

Date Update details Status
08/02/2021

Update to the look and feel of the system in line with University branding.

Completed
08/03/2021 Support model update. Self-service requests launched. First point of contact for other support requests moved to the IT Service Desk. Completed
01/04/2021 Update to the Reportable Classification/RIDDOR workflow. Completed
13/04/2021 Microsoft Azure infrastructure upgrade. System unavailable from 1pm.

Completed

01/12/2021 Assigning actions via the workflow box functionality to be removed. This will leave assigning actions via an email address as the sole method of assigning actions and reduce confusion between the two methods. Completed