Uploaded image for project: 'WORKTERRA'
  1. WORKTERRA
  2. WT-5420

El Camino Hospital OE 2017: Life Plan Coverage Increase

    Details

    • Type: Bug
    • Status: Production Complete
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      Stage
    • Module:
      BenAdmin
    • Reported by:
      Support
    • Company:
      El Camino Hospital
    • Item State:
      Production Complete - Closed

      Description

      Hello

      We have created new life and LTD plans due to carrier change effective 01/01/2017.

      For the Vol life plans The system is not recognizing the enrollment history and due to this, the system is not all9owing the coverage increase without a pending EOI. For example: EE Christine Lui currently enrolled Vol life $30K, for OE she would like to increase her election by $10K which is allowed and set-up under the plan.

      Can we create a fix that would allow in the coverage increase without a pending EOI? if not, can we keep the existing plan, roll back the enrollment and make the rollover change after OE to allow the coverage increase?

        Attachments

          Issue Links

            Activity

            Hide
            alankar.chavan Alankar Chavan (Inactive) added a comment -

            Hello Amruta Lohiya,

            We have fixed and tested above listed concerns on El Camino Hospital OE 2017 For HSPL - system is giving an expected behavior now.

            Please have a look on all the tried scenario -

            *For OE *

            created P1 and P2 plan - with same customization
            GI set at 10000 for OE
            Employee Coverage Increase for OE = 10000

            • employee enrolled in plan P1 with OE (01/01/2016) [applied = 30K | approved = 10k]
            • eoi request sent for admin approval - admin accepted election with 30K [applied = 30K | approved = 30k]
            • employee tried enrolling in Plan P1 as well as for P2 with next Year OE (01/01/2017). For both of the plans - system allowed employee to enroll with coverage 40K without sending the election request for Pending EOI [last enrollment with 30 K + 10K Employee Coverage Increase = 40K ]
            • employee enrolled with 50K [applied = 50K | approved = 40k]
            • eoi request sent for admin approval - admin accepted election with 50K [applied = 50K | approved = 50k]

            Hence, the 'Allow Coverage Increases that Exceed GI amount, but do not require EOI' functionality works well across multiple plans under a same benefit type

            *For QE *

            created P1 and P2 plan - with same customization
            GI set at 10000 for QE
            Employee Coverage Increase for QE = 10000
            employee enrolled in plan P1 with QE (01/01/2016) [applied = 30K | approved = 10k]

            • eoi request sent for admin approval - admin accepted election with 30K [applied = 30K | approved = 30k]
            • employee tried enrolling in Plan P1 as well as for P2 with next Year QE (01/01/2017). For both of the plans - system
            • allowed employee to enroll with coverage 40K without sending the election request for Pending EOI [last enrollment with 30 K + 10K Employee Coverage Increase = 40K ]
            • employee enrolled with 50K [applied = 50K | approved = 40k]
            • eoi request sent for admin approval - admin accepted election with 50K [applied = 50K | approved = 50k]
            • employee tried enrolling in Plan P1 as well as for P2 with next Year QE (01/01/2018). For both of the plans - system allowed employee to enroll with coverage 60K without sending the election request for Pending EOI [last enrollment with 50 K + 10K Employee Coverage Increase = 60K ]

            Hence, the 'Allow Coverage Increases that Exceed GI amount, but do not require EOI' functionality works well across multiple plans under a same benefit type

            Additional Scenarios -

            For Employee - Ines C Mancebo

            1. was enrolled in 'VOLUNTARY LIFE' in 2015 with 360k
            2. was enrolled in 'VOLUNTARY LIFE' in 2016 with 370k
            3. in OE 2017 - now he can enroll in 'Voluntary Life' upto amount 380k without sending election request to pending EOI. If he tries to enroll in plan with higher amount than 380k,
            election request will go to pending EOI with approved amount as 380k

            For Employee - Ginger J Wong

            1. this employee had an enrollment from 01/01/2015 to 12/31/2015 in voluntary life plan with coverage amount as 440K
            2. no enrollment in 2016
            3. hence when went on enroll now screen with OE 01/01/2017 -> employee has approved amount as 440k + 10k = 450k which is as per the functionality

            For New Hires

            1. when employee tries to enroll in voluntary life plan - system sends the election request to pending EOi when selected coverage amount is exceeding the GI amount which is 340K

            For other existing Employees

            1. we went on the enrollment screens for few existing employees who were enrolled in voluntary life plans in past (2015 and/or 2016)
            2. when these employees tried to enroll in the plan with 2017 OE - system offered them 10k bump up amount with their last year existing enrollment coverage amount - as per the expectations

            For new test employees - OE

            1. was enrolled in 'VOLUNTARY LIFE' in 2016 with 360k
            2. in OE 2017 - now he can enroll in 'Voluntary Life' upto amount 370k without sending election request to pending EOI. If he tries to enroll in plan with higher amount than 380k,
            election request will go to pending EOI with approved amount as 380k
            3. also if employee waives his election in OE 2017 - when he tries to enroll again - the approved amount = last year enrollment's approved amount + 10k bump up amount
            ie 370k in above example

            CC - Umesh Kadam Deepali Tidke Rakesh Roy Vijay Siddha Samir

            Show
            alankar.chavan Alankar Chavan (Inactive) added a comment - Hello Amruta Lohiya , We have fixed and tested above listed concerns on El Camino Hospital OE 2017 For HSPL - system is giving an expected behavior now. Please have a look on all the tried scenario - *For OE * created P1 and P2 plan - with same customization GI set at 10000 for OE Employee Coverage Increase for OE = 10000 employee enrolled in plan P1 with OE (01/01/2016) [applied = 30K | approved = 10k] eoi request sent for admin approval - admin accepted election with 30K [applied = 30K | approved = 30k] employee tried enrolling in Plan P1 as well as for P2 with next Year OE (01/01/2017). For both of the plans - system allowed employee to enroll with coverage 40K without sending the election request for Pending EOI [last enrollment with 30 K + 10K Employee Coverage Increase = 40K ] employee enrolled with 50K [applied = 50K | approved = 40k] eoi request sent for admin approval - admin accepted election with 50K [applied = 50K | approved = 50k] Hence, the 'Allow Coverage Increases that Exceed GI amount, but do not require EOI' functionality works well across multiple plans under a same benefit type *For QE * created P1 and P2 plan - with same customization GI set at 10000 for QE Employee Coverage Increase for QE = 10000 employee enrolled in plan P1 with QE (01/01/2016) [applied = 30K | approved = 10k] eoi request sent for admin approval - admin accepted election with 30K [applied = 30K | approved = 30k] employee tried enrolling in Plan P1 as well as for P2 with next Year QE (01/01/2017). For both of the plans - system allowed employee to enroll with coverage 40K without sending the election request for Pending EOI [last enrollment with 30 K + 10K Employee Coverage Increase = 40K ] employee enrolled with 50K [applied = 50K | approved = 40k] eoi request sent for admin approval - admin accepted election with 50K [applied = 50K | approved = 50k] employee tried enrolling in Plan P1 as well as for P2 with next Year QE (01/01/2018). For both of the plans - system allowed employee to enroll with coverage 60K without sending the election request for Pending EOI [last enrollment with 50 K + 10K Employee Coverage Increase = 60K ] Hence, the 'Allow Coverage Increases that Exceed GI amount, but do not require EOI' functionality works well across multiple plans under a same benefit type Additional Scenarios - For Employee - Ines C Mancebo 1. was enrolled in 'VOLUNTARY LIFE' in 2015 with 360k 2. was enrolled in 'VOLUNTARY LIFE' in 2016 with 370k 3. in OE 2017 - now he can enroll in 'Voluntary Life' upto amount 380k without sending election request to pending EOI. If he tries to enroll in plan with higher amount than 380k, election request will go to pending EOI with approved amount as 380k For Employee - Ginger J Wong 1. this employee had an enrollment from 01/01/2015 to 12/31/2015 in voluntary life plan with coverage amount as 440K 2. no enrollment in 2016 3. hence when went on enroll now screen with OE 01/01/2017 -> employee has approved amount as 440k + 10k = 450k which is as per the functionality For New Hires 1. when employee tries to enroll in voluntary life plan - system sends the election request to pending EOi when selected coverage amount is exceeding the GI amount which is 340K For other existing Employees 1. we went on the enrollment screens for few existing employees who were enrolled in voluntary life plans in past (2015 and/or 2016) 2. when these employees tried to enroll in the plan with 2017 OE - system offered them 10k bump up amount with their last year existing enrollment coverage amount - as per the expectations For new test employees - OE 1. was enrolled in 'VOLUNTARY LIFE' in 2016 with 360k 2. in OE 2017 - now he can enroll in 'Voluntary Life' upto amount 370k without sending election request to pending EOI. If he tries to enroll in plan with higher amount than 380k, election request will go to pending EOI with approved amount as 380k 3. also if employee waives his election in OE 2017 - when he tries to enroll again - the approved amount = last year enrollment's approved amount + 10k bump up amount ie 370k in above example CC - Umesh Kadam Deepali Tidke Rakesh Roy Vijay Siddha Samir
            Hide
            alankar.chavan Alankar Chavan (Inactive) added a comment -

            Hi lisa davison,

            Please do let us know if you find any problem . If everything working as per the expectations, we can move this patch to Production.

            Show
            alankar.chavan Alankar Chavan (Inactive) added a comment - Hi lisa davison , Please do let us know if you find any problem . If everything working as per the expectations, we can move this patch to Production.
            Hide
            lisadavison lisa davison added a comment -

            Hello

            Working as expected. Please implement in production.

            Thanks

            Show
            lisadavison lisa davison added a comment - Hello Working as expected. Please implement in production. Thanks
            Hide
            rakeshr Rakesh Roy (Inactive) added a comment -

            Thanks lisa davison for confirming, will move this patch tomorrow on production.

            Show
            rakeshr Rakesh Roy (Inactive) added a comment - Thanks lisa davison for confirming, will move this patch tomorrow on production.
            Hide
            rakeshr Rakesh Roy (Inactive) added a comment -

            lisa davison This is deployed on production, please check and confirm.

            Show
            rakeshr Rakesh Roy (Inactive) added a comment - lisa davison This is deployed on production, please check and confirm.

              People

              Assignee:
              lisadavison lisa davison
              Reporter:
              lisadavison lisa davison
              Developer:
              Umesh Kadam (Inactive)
              QA:
              Alankar Chavan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: