Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

New and Improved Features 

...

Configurable


Anchor
PMP-91123
PMP-91123
PMP-91123: Show/Hide menus based on permission

Configurable: No

  • Title: NA
  • Public/Private: NA
  • Default: NA

...

  • Following menus are shown even if user doesn't have the required permission for any of the Incident types and also the message shown are not consistent in some of the cases :
MenusMessage shown
Report New IncidentNo permission to Report/Create New Incident
Manage Incident ReportsYou do not have permissions. Please contact system administrator.
Manage Action ItemsYou do not have permissions. Please contact system administrator.
Management ReviewNo permission to View/Edit Management Review.
Lessons LearnedYou do not have permissions. Please contact system administrator.
Manage ClaimsNo permission to View/Edit Manage Claims.
MetricsNo View Permission

Purpose: 

  • Show/Hide the menus based on permission so as to avoid confusion.

...

  • Following three menus will be shown/hidden based on the permissionspermission:
    • Management Review
    • Manage Claims 
    • Metrics

Impacts: NA

Back to top

Image RemovedPMP-91334: Save Claim Summary Details while submitting the Claims

Configurable: No

  • Title: NA
  • Public/Private: NA
  • Default: NA

Existing System:

  • As per current implementation, whenever user submits a Claim, the Claim Summary Details under 'TPA Costs and Notes' section are not saved automatically and every time the user has to explicitly go to the ‘TPA Cost & Notes’ section and hit the 'Save' button.
  • From application end, all the three sections i.e. ‘Summary’, ‘Cost’ and ‘Claim Adjuster’ shown in the 'TPA Cost and Notes' screen are independent and can be saved without any dependency on the other sections.
  • Many a times, the Cost section gets the details through the TPA via the Inbound flow but in this case the Claim Summary details are still not saved because this needs to be explicitly saved by the user. As per Cognos model, ‘Claim Summary’ and ‘TPA Cost & Notes’ are dependent and until and unless the Claim Summary details are saved, the Cost details cannot be shown.

Purpose:

  • Save the Claim Summary details when user submits the Claim so as to resolve the bug wherein the data is not getting reflected in Cognos.

Enhanced System:

  • Save the Claim Summary details (i.e. the details auto-populated from Incident) when user submits the Claim.

Image Removed

...

  • If the user doesn't have permission for other menus then it will be still visible with a standard message - "You do not have permissions. Please contact system administrator".

Impacts: NA

Back to top



Anchor
PMP-86126
PMP-86126
PMP-86126: Contractor Management

Configurable: Yes

  • Title:

...

Display 'Was Contractor Involved?' field

...

'Was Contractor Involved?' field as Mandatory/Non-Mandatory

...

'Contractor Name' field as Mandatory/Non-Mandatory

...

Default value selection 'Other(List)' for 'Contractor Name' field

...

Existing System

  • Contractor fields are present only for three incident Types - Near Miss, Property Damage and Environmental. Moreover, the fields are not consistent and present under different sections in the Reporting screen.
Incident TypeSectionField NamesMandatory/OptionalConfiguration
  • Near Miss
General DetailsIs Contractor Involved?MandatoryShow/Hide - Public Configuration
Please provide Contractor Name, CompanyMandatory
  • Property Damage
  • Environmental


Damage Summary

Was a Contractor Involved in the Incident?Optional
Please provide Contractor Details (Name, Company, Phone, etc.)Mandatory
Was The Contractor Trained On Company Policies?Mandatory

 *Note: As per existing implementation, Injury/Illness, Vehicle and General Liability Incident Types doesn't did not have the above mentioned Contractor fields.

  • The system has a look up value for Contractor information where customers can maintain the details of Contractor Names. However, this look-up is not integrated with integrated with the Contractor field in the Reporting screen. So  So this feature is not being utilized to it’s potential. As of now, user has to enter contractor name manually.
  • 'Contractor Name' field shown upon selecting the 'Personnel Type' as 'Unsupervised Contract Employee' is a free text field and not integrated with any lookup.

Purpose: 

  • Standardize the set of Contractor fields shown for different Incident Types.
  • Integrate Contractor Name field shown in the Reporting screen with the Lookup.

Enhanced System:

  • Have same set of Contractor fields for all the Incident Types.
Incident TypeSection NameField NameField TypeMandatory/OptionalDependencyConfiguration

1. Near Miss

2. Injury/Illness

3. Vehicle

4. General Liability

5. Property Damage

6. Environmental




General Details


Was Contractor involved?Radio-button 

Mandatory/Optional

(*Based on Custom Setting)


  • Custom Setting key to Show/Hide the field by Incident Type
  • Custom Setting key to handle Mandatory/ Non-Mandatory by Incident Type
Contractor Name

Autocomplete 

Mandatory/Optional

(*Based on Custom Setting)

Dependent on the field 'Was Contractor Involved?'

  • Custom Setting key to handle Mandatory/ Non-Mandatory
  • Custom Setting key to show the default value as 'Other (List)' with a textbox
Contractor DetailsTextboxOptional
Was the Contractor trained on Company Policies?Radio-button Mandatory

Image RemovedImage Added

Image RemovedImage Added

 Image RemovedImage Added

  • 'Contractor Name' field (shown upon selecting the 'Personnel Type' as 'Unsupervised Contract Employee') has been changed to an autocomplete control (integrated with a lookup).

Image Removed

...

  • If user doesn't have lookup configured then select the 'Other(List)' option from the list and fill in the Contractor Name manually.
  • Prior to saving an Incident, the 'Contractor Name' provided under the 'General Details' section will auto-populate in the 'Employee/Individual Details' section. However, user can update the auto-populated value, if needed.

Image Added

 Image Added

  • A new System View 'Contractor Incidents - Current Year' has been added

...

 Image Added

  • Following two fields have been added in the Incident Details Report Notification template for all the Incident Types:
    • Was Contractor Involved?
    • Contractor Name
  • 'Contract Profile' Widget has a data point 'Total Incidents Involved' which will show the count of incidents with Contractor involvement.

Anchor
Configurations
Configurations
Configurations Table:

S.No.ConfigurationCommentsKey Name
1Display 'Was Contractor Involved?' fieldEach incident type has a cutom setting key
  • WRAIMS_INCIDENT_CONTRACTOR_INVOLVED
  • ContractorInvolvedYNENV
  • ContractorInvolvedYNPD
  • ContractorInvolvedYNInjury
  • ContractorInvolvedYNGL
  • ContractorInvolvedYNVH
2'Was Contractor Involved?' field as Mandatory/Non-MandatoryEach incident type has a cutom setting key
  • ContractorInvolvedMandatoryYNNM
  • ContractorInvolvedMandatoryYNPD
  • ContractorInvolvedMandatoryYNENV
  • ContractorInvolvedMandatoryYNVH
  • ContractorInvolvedMandatoryYNInjury
  • ContractorInvolvedMandatoryYNGL
3'Contractor Name' field as Mandatory/Non-MandatoryOne custom setting key for all incident types
  • ContractorNameMandatoryYN
4Default value selection 'Other(List)' for 'Contractor Name' fieldOne custom setting key for all incident types
  • ContractorDefaultvalue

Impacts: Reports, Mobile, Outbound API 


Back to top

Anchor
PMP-89380
PMP-89380
PMP-89380: Investigator Report

Configurable: Yes

  • Title: Investigator Report
  • Public/Private: Private
  • Default: Enabled

Existing System: 

  • Does not provide any statistics related to the Incident, Involved Employee, Supervisor of the Employee, Department, Work Shift, etc. in an single Report.

Purpose: 

  • To assist investigation teams during the investigation process by providing insight into the statistics related to the Incident, Involved Employee, Supervisor of the Employee, Department, Work Shift, etc.
  • Provide Incident-related data points from different modules in one place for a quick view. 

Enhanced System:

  • This report will be available only for Injury/Illness Incident Type.
  • 'Investigator Report' button is visible in the Incident Summary screen as soon as the Detail Report is completed for an Injury/Illness Incident. This button is available for users who have Injury/Illness Investigation View Permission.
  • Clicking on the 'Investigator Report' button redirects the user to a new screen which displays different statistics related to the Incident, Incident Type, Incident Department, Involved Employee, Employee Supervisor, Employee Job etc.
  • The screen is in read only mode and all statistics shown are till the Date of Incident.
  • The screen has 2 buttons:
    • Back - To navigate back to the Incident Summary screen
    • Export - To download the the Report as a PDF
  • The report will pull all statistics for the Incident as per Incident Date. However, the statistics will be a snapshot of the time when detail report is completed for the incident. After that the report will always show same statistics irrespective of the changes made in the application for existing incident.
  • The metrics displayed in the Report are until the date of the Incident.
  • In case of multiple injuries data available in the report is only for the first Employee.
  • Metrics from other modules like BBS, LMS, Asset, etc. are displayed in the Report if the customer has a subscription to these modules.
  • Report will be available only for new Incidents created after the release.
  • The permission to access this report is dependent on the Investigation details permissions
  • The metrics in the Report are divided into the following sections:
    • Metrics of employee involved in the Incident
    • Summary of similar Incidents 
    • BBS metrics
    • Training metrics
    • Asset related incidents
    • Employee’s supervisor’s metrics
    • Metrics of the employee’s job title

Image Added


 Image Added


Impacts: No Impact