...
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
Title: Enable Vehicle Incident TypeOSHA 300/301 Case Data E-Submission
Public/Private: Private Public
Default: No
Existing System: Doesn't have a
...
list to view OSHA 300/301 data.
Purpose:
...
To comply with regulatory requirements.
Enhanced System:
Reporting ScreenPermission:
A new field 'Vehicle Incident type' has been added to the Reporting screen.
It is a dropdown field and the values can be configured from the Module Setup.
This field can be mandatory/non-mandatory based on the Custom Setting.
...
permission 'E-Submission of OSHA 300/301 Case Data' will be added under Work Place Incident Report - Injury/Illness > Regulatory Forms.
New Menu:
The new menu 'OSHA 300/301 Case Data' will be shown below 'OSHA 301' menu.
This menu will be driven based on the permission (details given in the below section).
It will be shown for both 'Location' and 'Level' (**only US Locations and Level).
New System Views:
There will be two System Views:
All Cases - Previous Year (Default View)
All Cases - Current Year
This screen will show the records for the following Cases i.e. similar to the implementation for 'OSHA 300' and 'OSHA 301' List screens:
Other Recordable
Restricted Duty
Lost Time
Death
Generate CSV :
There will be a 'Generate CSV' button at the top right corner of the screen.
*Note: There won't be any separate permission to enable/disable this button.
Impacts: Mobile, Reports, RC, Cognos, Outbound API
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
Title: Display Vehicle Accident Rate KPI
Public/Private: Public
Default: No
Existing System:
The Vehicle Incident Metrics do not capture the 'Vehicle Accident Rate'.
Purpose:
Add a new KPI 'Vehicle Accident Rate' to the 'Vehicle Incident Metrics'.
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
Title: Enable Confidential Incident Feature
Public/Private: Public
Default: Yes
Existing System:
Does not have the feature to hide any incident that requires privacy. So such type of incidents are deleted from the system (if already reported) and managed elsewhere to avoid disclosure.
Purpose:
Introduce a new feature so as to maintain the Confidential Incidents in the application with limited access to the authorized users.
...
An Incident can be categorized as confidential at any stage in the Incident workflow (Example: During Incident Reporting, Incident Detail Report is completed, Investigation is in progress or completed, etc.).
'Record Level Security' permission
When the Custom Setting for this feature is turned ON, a new permission 'Record Level Security' will be shown in the Permission screen.
Users having this permission will be able to see the 'Confidentiality Details' section in the Reporting screen.
Incident Reporting screen
A new section 'Confidentiality Details' will be shown in the Reporting screen if user has the 'Record Level Security' permission.
This section will have two fields:
Would you like to make this incident confidential?
Authorized Team
If the user selects 'Yes' then it will throw a confirmation alert as shown below.
Clicking on the 'Ok' button in the confirmation alert will close the popup and display the 'Authorized Team' field (with the logged in user name by default).
...
New Notification for Confidential Incident
An immediate notification will be sent to the authorized users when an incident is made confidential.
Manage Incident List Screen
...