...
| Anchor | ||||
|---|---|---|---|---|
|
Product Level Change
No itemsNone
Configurable
PMP-94330 - Ability User would like to have the ability to generate and export OSHA 300-301 CSV file
PMP-95310 - User would like to edit DOB field in OSHA 301 screen based on a configuration
PMP-94956 - Implement access in the summary report so that only authorized users can see the investigation data95710 - User would like to submit 300A data using the API Token
Performance
PMP-94436 - IMS-Autocomplete Control Performance Improvement
...
PMP-94407 - AAP Retail Calendar - DB Design & Script to load data
PMP-94443 - IMS-Checkmarx Version Upgrade (9.5.0)
PMP-94777 - IMS Datamart - SQL Server Upgrade 2019
PMP-93190 - IMS-SQL Server Upgrade 2019 - Feed
| Anchor | ||||
|---|---|---|---|---|
|
...
User would like to have the ability to generate and export OSHA 300-301 CSV file
Configurable: Yes
Title: Enable Vehicle Incident TypeOSHA 300/301 Case Data E-Submission
Public/Private: Private Public
Default: No
Existing System:
...
Currently,systemdoesn't have a
...
Purpose:
...
list screen to display OSHA 300/301 data and also generate a CSV file.
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.
Incident Detail Report Notification Template
Impacts: Mobile, Reports, RC, Cognos, Outbound API
...
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'.
Enhanced System:
The new KPI 'Vehicle Accident Rate' has been added under the 'Incident rate' section.
Vehicle Accident Rate = (Number of Vehicle Accidents*1,000,000)/Miles Driven
Impacts: Outbound API, Cognos
...
permission 'E-Submission of OSHA 300/301 Case Data' is added under Work Place Incident Report - Injury/Illness > Regulatory Forms.
By default, it would be 'No'.
New Menu:
The new menu 'OSHA 300/301 Case Data' is shown below 'OSHA 301' menu.
This menu will be driven based on the permission and data will be shown for both 'Location' and 'Level' (**only US Locations and Level).
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
Two System Views:
All Cases - Previous Year (Default View)
All Cases - Current Year
300 & 301 Review Status Display & Validation:
300 & 301 Screen review status will be displayed on the list.
Only if all required fields are completed and saved, then 300 & 301 review is treated as complete.
CSV can be generated only once both screen's status turns 'Complete'.
Generate CSV :
There will be a 'Generate CSV' button at the top right corner of the screen.
There won't be any separate permission to enable/disable this button.
New Permission:
...
New Menu:
...
Impacts: None.
| Anchor | ||||
|---|---|---|---|---|
|
Configurable: Yes
Title: Enable Confidential Incident FeatureIMSEmpDOBPrivacyInfoShowYN
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:
...
Currently, DOB field in OSHA 301 screen is auto-populated from the foundation employee profile and it is non-editable in OSHA 301 screen.
Purpose: To provide flexibility to the OSHA 301 user.
Enhanced System:
When can you make an incident confidential?
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
Authorized Users:
'Incident ID' link remains enabled with complete data shown in all the columns of the grid.
Authorized users will be able to delete a confidential incident if they have the required delete permission.
Unauthorized Users:
'Incident ID' link will be disabled.
'Incident Title' will be masked with text 'Confidential'.
'Incident Reported As' and 'Incident Date' column will show the details.
Unauthorized users cannot delete the confidential incident record even if they have the delete permission.
Incident Summary Screen
Only Authorized users will be able to access the Incident Summary page for a Confidential Incident either by navigating through the list screen or notification link.
A new label 'Confidential Incident' will be shown on the Incident Summary screen. This will have 'Yes' or 'No' based on the response selected in the Reporting screen.
'Email Incident Summary' link in the Incident Summary screen will be disabled for the Incidents categorized as confidential (even if the authorized user has the permission for emailing Summary Report).
Authorized users can download different Reports from the Summary Screen - Incident Summary Report, Vehicle Claim Report, Claim Report, etc.
Case Management List Screen
Authorized Users:
'Case Number' link remains enabled with complete data shown in all the columns of the grid.
Unauthorized Users:
'Case Number' link will be disabled.
'Incident Title' will be masked with text 'Confidential'.
'Date Occurred' column will show the details.
*Note: Every other List screens like - Lessons Learned, Claim List, Management review, etc. has similar implementation wherein the Authorized users will be able to see the complete set of data and the Unauthorized users will be able to see the record in the list screen but most of the data will be either blank or masked as 'Confidential'.
Action Item List Screen
Authorized Users and Unauthorized Users:
Incident ID column will show the confidential incident icon.
Data in the column 'Incident Title' will be masked with text 'Confidential' for all the Action Items linked to the confidential incident.
Data in all the other columns will remain as-is.
Action Item Details Screen
Data shown in the field 'Source Title' will be masked with text 'Confidential' for the action items linked to the confidential incidents.
Calendar > Manage Action Items List Screen
Data in the column 'Source Title' will be masked with text 'Confidential' for all the Action Items linked to confidential incidents.
'View Incident Details' link in 'Reference' column will be disabled for the Action Items linked to confidential incidents.
Data in all the other columns will remain as-is.
Incident Summary Report
'Confidentiality Details' section will show the Authorized Team details.
Widgets
Authorized Users
Authorized User will see the complete data pertaining to the Confidential Incident on the following three Widgets - New Incident Widget, Recently Updated Widget and Risk Point Widget.
They can click on the confidential incident record and navigate to the List screen.
Unauthorized Users
For confidential incidents, the 'Incident Title' will be masked with text 'Confidential'.
Data will be shown for the fields - Incident Date, Reported As, Created Date/Updated Date.
Data shown in all the other fields (Personnel Type, Incident Status, Classification of Case, Claim Status, Management Review Status) will be hidden.
The confidential incident record will be disabled so that unauthorized users cannot navigate to the List screen.
Notifications
All the Incident Notifications (which includes Immediate notifications, Daily notifications for Location and Module) will be suspended for the Incidents marked as Confidential.
*Note: This suspension will be applicable from the point of time when the incident is saved as confidential.
Only Action Item notification will be triggered for a confidential incident.
Regulatory List screens or Reports
No changes have been implemented for any of the Regulatory Reports like OSHA, MSHA, IR Forms, etc.
Report Central
Confidential Incident record(s) will be hidden in Report Central.
Insight
Confidential Incident record(s) will be available in Insight. However, user can use a flag (Would you like to make this incident confidential) to filter the Confidential/Non-Confidential Incidents.
Outbound API
Confidential Incident data will not be exported from the system.
...
User will be able edit DOB field in OSHA 301 based on permission and configuration.
The existing custom setting (Which is already in use in the reporting screen) is used in the OSHA 301 screen as well.
Additionally, if the user has edit OSHA 301 permission, then the DOB field would be visible and available for editing.
If the user only has view OSHA 301 permission, then DOB field would just show as “Privacy Information”.
Impacts: None.
...
| Anchor | ||||
|---|---|---|---|---|
|
Configurable: No
Title: OSHA Form 300A Electronic Submission using API Token
Public/Private: NA
Default: NA
Existing System: Currently, the system doesn't have an option to submit 300A data to OSHA's ITA (Injury Tracking Application) using the new API Token process as the 300A data was previously transmitted to OSHA’s ITA by entering ITA account credentials
Purpose: To comply with regulatory requirements.
Enhanced System:
Enhanced the submit using OSHA API option to allow users to paste an API Token copied from OSHA’s ITA (Injury Tracking Application) in order to transfer a location's 300A data to ITA.
Added guidance information to the information pop-up.
