Versions Compared

Key

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

New and Improved Features 

...

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.

...

PMP-91334: Save Claim Summary Details while submitting the Claims

Configurable: No

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

...

  • 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 Modified

Impacts: NA


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

Configurable: Yes

  • Title:
S.No.TitleComments
    1.

Display 'Was Contractor Involved?' field

Custom Setting key per Incident Type
    2.

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

Custom Setting key per Incident Type
    3.

'Contractor Name' field as Mandatory/Non-Mandatory

One Custom Setting key for all Incident Types
    4.

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

One Custom Setting key for all Incident Types


  • Public/Private: Public


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 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 the Contractor field in the Reporting screen. 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.

...

  • 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

(*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

 


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

...