...
| Anchor | ||||
|---|---|---|---|---|
|
New Features (Product Level)
PMP-95698 - Update to Riddor Functionality RIDDOR classification changes to be compliant with UK Regulatory Laws
PMP-95697 - Field Level Security - Self Permission Implementation
Usability Changes (Product Level)
PMP-97263 - Ability to generate a QR Code for Incident Reporting
PMP-97264 - Ability to view "Incident Description" from the “Manage Incidents List screen”
Improvements (Product Level)
Configurable
None
| Anchor | ||||
|---|---|---|---|---|
|
Configurable: No
Title: NA
Public/Private: NA
Default: NA
...
Impacts: None.
| Anchor | ||||
|---|---|---|---|---|
|
...
- RIDDOR classification changes to be compliant with UK Regulatory
...
Laws
Configurable: No
Title: NA
Public/Private: NA
Default: No NA
Existing System: Currently,
Currently, we support only 'Dangerous occurrence' for Near Miss. We don’t have “Dangerous Gas Fitting“ as a near-miss RIDDOR classification.
We don’t support capturing HSE reference ID and the ability to upload a RIDDOR report.
Completing RIDDOR classification for multiple employees has to be done from a RIDDOR screen which was not user-friendly.
Purpose: To be compliant with the UK regulatory laws.
Enhanced System: Impacts: None
We have re-positioned the RIDDOR section from the reporting screen to the incident summary (as this classification always happens after reporting an incident).
The summary screen would show RIDDOR forms created for each employee involved in the Incident.
So, with this user can find all the information at one place and doesn’t have to navigate to the RIDDOR List.
The RIDDOR form can be accessed from the summary along with the HSE validation section.
Changes to HSE validation section to incorporate HSE Reference ID and ability to upload a RIDDOR report.
Included “Dangerous Gas Fitting“ as one more RIDDOR classification for Near Miss incident.
Deprecated the RIDDOR section from mobile as classification will be done after reporting an incident.
...
Impacts: Reports, Mobile.
| Anchor |
|---|
...
|
...
|
...
-95697 - Field Level Security - Self Permission Implementation
Configurable: No
Title: NA
Public/Private: NA
Default: No NA
Existing System: Currently,
Incident creators always have permission to view sensitive field information.
The same sensitive information is also available in the employee picklist.
Purpose:
To apply field-level security even for the record creator.
Enhanced System:
Impacts: None.
...
Configurable:
Title:
Public/Private:
Default: No
...
Purpose:
...
Introduce 'Self' permission in Security > Field Level Security Section.
Employee Sex
Hire Date
Supervisor Name
Supervisors Email
State of License
Date of Expiration
All users with others' permission for these fields would be assigned self-permission by default
Also, the above sensitive fields were removed from the employee picklist as well. (Common Change)
...
Impacts: None.
| Anchor |
|---|
...
|
...
|
...
97263 - Ability to generate a QR Code for Incident Reporting
Configurable: Yes
Title: ShowIncidentQRCode
Public/Private: Public
Default: No
Yes, if mobile is available and No for others.
Existing System: Currently, we have the QR code only to report near misses but it is not available for download from the application.
Purpose:
To improve the ease of use of reporting an incident from mobile.
Enhanced System:
User will have the option to generate a QR Code for reporting a new incident from the incident list screen.
By scanning this QR Code, the user will be able to directly land to report a new incident screen.
Scanning can be done using the mobile camera or the scan option in the Ideagen EHS app.
Generate QR Code from List | On scanning, Landing Screen |
|---|---|
 |  |
Impacts: None.
| Anchor |
|---|
...
|
...
|
...
97264 - Ability to view "Incident Description" from the “Manage Incidents List screen”
Configurable: No
Title: NA
Public/Private: NA
Default: No NA
Existing System: Currently, the description field is available only in the details screen.
Purpose: To be able to view the incident description with fewer clicks.
Enhanced System:
The user would be able to see the first 50 characters of the incident description on the list.
There is a hyperlink provided which would help users to view the full text of 2000 characters.
On clicking Export to Excel, the full description will be downloaded to the sheet as a column.
This column is available for selection from the incident list columns. (Not part of any system view by default).
...
Impacts: None.
| Anchor |
|---|
...
|
...
|
...
95700 - Validation implementation in Case Management screen on case status change
Configurable: NO
Title: NA
Public/Private: NA
Default: No NA
Existing System: Currently,
we have the validation on case status only when creating a new case progression.
and, we are allowing users to change case status to Closed even without the case progression dates.
Purpose: To eliminate inconsistencies in metric data calculations.
Enhanced System:
Users would be restricted from changing the case status without adding Last day for the latest case progression.
This validation is similar to what we have when we add a new case without a date entered for the previous case.
...
Impacts: None.