Hi Tracy Kot,

I have verified your concern as per our observation this is not an issue.
Employee Lucas Godwin Enrolled In Blue Saver Medical plan with tier EE+SP+CH.

This plan has General contingent on HSA plan.
When Admin raised QE of birth of a child and enrolled in to the Blue Saver Medical plan with tier EE+SP+2CH because of tier change HSA plan is terminated.
refer below screen shots.

kindly, let us know if you have any concern.

Thanks,
Rashmita

Rashmita Dudhe, The Tier Level should NOT term HSA. If EE is in Blue Saver EE can be in HSA. So just because EE had a QE and is still in Blue Saver it should NOT term the HSA plan.

CC: Mandar Kulkarni, Samir

Hi Jyoti Mayne

CC:Amruta Lohiya,Hrishikesh Deshpande,Rakesh Roy,Vijay Siddha

I have verified above issue and it is getting reproduced below are the steps:
1]Blue Saver Medical plan has general contingent on HSA plan.

2]Employee Lucas Godwin Enrolled In Blue Saver Medical plan with tier EE+SP+CH.
3] When Admin or partner raised QE of birth of a child and enrolled into the Blue Saver Medical plan with tier EE+SP+2CH because of tier change HSA plan is terminated. But it should not be terminate when we Increase or Decrease tier.

refer below screen shots.

Thanks,
Rashmita

Deborah Mascot adding Debbie as a watcher in case it is impacting other clients.

Please see WT-5064 for reference to the Softchoice HSA regression testing. Amruta Lohiya

Hi Tracy Kot,

We are working on this issue. We will update you soon.

CC: Amruta Lohiya,Samir,Vijay Siddha
Thanks

Hi Rashmita Dudhe,

Please verify if this issue is getting reproduced on LB environment.

Thanks.

Hi Girija Potdar,

CC:Hrishikesh Deshpande,Jyoti Mayne,Rakesh Roy

I have verified above issue on LB Environment and it is getting reproduced below are the steps:
1]Blue Saver Medical plan has general contingent on HSA plan.
2]Employee Lucas Godwin Enrolled In Blue Saver Medical plan with tier EE+SP+CH. with Effective date 01/01/2016
3]In OE Employee Enrolled into the HSA plan with Effective date 01/01/2017
4 Admin or partner raised QE of birth of a child and enrolled into the Blue Saver Medical plan with tier EE+SP+2CH with Effective date 12/01/2016 because of tier change HSA plan is terminated. But it should not be terminate when we Increase or Decrease tier.
refer below screen shots.

Thanks,
Rashmita

High Priority,
The client gave me another employee this impacted in addition to the Lucas Godwin. Employee Matt Mirtsching had a baby and added her medical, dental and vision. However, client doesn't see his HSA election-but it’s not in waived as if he cancelled the plan.
URGENT.

CC: Deborah Mascot Mandar Kulkarni Samir Hrishikesh Deshpande Jyoti Mayne Rakesh Roy

Hi Tracy Kot,

Please find our analysis details below for Lucas Godwin.

• Initially Lucas Godwin got election in '2016 Health Savings Account' from 01/01/2016 to NULL.
• Later, mid night service set term date for this election to 12/31/2016 as '2016 Health Savings Account' has termination date 12/31/2016.
• Again mid night service has set its termination date to 12/14/2016 as Lucas is not eligible in '2016 Health Savings Account' from 12/14/2016.
• From 12/14/2016 and onward, he is not eligible for any HSA plan hence not getting election in HSA plans.

Please let us know if more details are required regarding Lucas Godwin's election in HSA.

I'll share details about HSA election of Matt Mirtsching in sometime.

Thanks and Regards,
:: Umesh Kadam

CC : Deborah Mascot, Samir, Vijay Siddha, Amruta Lohiya, Mandar Kulkarni, Hrishikesh Deshpande, Jyoti Mayne

Hi Tracy Kot,

CC: Deborah Mascot, Samir, Amruta Lohiya, Vijay Siddha, Rakesh Roy

We have done analysis of this issue.
This issue is scenario specific .
1) If medical plan enrolled with 1/1/2016 to NULL
2) Two HSA plans are contingent on medical plan and there enrollment are like this
2016 HSA: 1/1/2016 to 12/31/2016
2017 HSA: 1/1/2017 to NULL

If any child/spouse added with effective 12/1/2016 and enrolled to medical plan then
system will check contingent eligibility of plan 2016 HSA with effective 12/1/2016. (plan is eligible will not terminate this plan)
Next will check 2017 HSA with effective 12/1/2016. On 12/1/2016, 2017 HSA plan is not eligible So, this plan is terminated in the system.

This fix require core module code change, so we are in progress of fixing this code with proper analysis.
We will update you progress of this issue.
We will let you know once data correction done for affected employee.

Thanks,
Neelam

Please review Softchoice to determine if this is an issue with them as well.

Hi Tracy Kot,

CC: Deborah Mascot, Amruta Lohiya, Vijay Siddha, Samir, Satya, Rakesh Roy.

We have done with code fix and detailed analysis for this issue.
We will deploy this on local environment tomorrow and after QA verification it will go further through regular patch process.

Deborah Mascot: We will scan all affected companies with same issues.
and update you on affected employee and Data correction.

Thanks,
Neelam

Neelam Yangal, thank you. do you have an estimate on when it will be in PROD? Do you have a list of employees that were impacted by having their HSA dropped for JE Dunn?
Thanks again.

Hi Tracy Kot,

We are working on scanning all affected employee for all companies and also we will share JE Dunn affected employee in that.
Rakesh Roy: Could you please update estimated PROD date for this JIRA item (LB deployment date is 12/29/2016)?

Thanks,
Neelam

Please assign this to QA for thorough verification on LB.

Hi Rashmita Dudhe,

Please test following all scenarios
1) Core Plan Allocation (Contingent Scenario)
2) Coverage change of parent plan (Contingent Scenario)
3) Waive parent plan.
And this all scenarios from Import Routine as well.

Thanks,
Neelam

Hi Tracy Kot,

We have created affected employee script for one company
So please find affected employee from JE dunn only.
We provide rest by tomorrow,
1) Lance Gliser
2) Desmond Clark
3) John Schlick
4) Vincent Ward
5) Matthew Mirtsching.

Note: Employee Lucas Godwin has not listed in above because this employee status is terminated hence this employee no more eligible for this plan.

Thanks,
Neelam

Hi Neelam Yangal,

CC:Hrishikesh Deshpande,Rakesh Roy,Vijay Siddha, Amruta Lohiya

As per you mention Above i have verified below scenarios On Lb Environment:

Scenarios 1: (Verified Through UI Import)Eligibility Contingency :Retro tier Increase
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.

Scenarios 2: Eligibility Contingency :Waived parent Plan all Child plan is terminated
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.
4]Waived Medical plan the Both HSA 2016 and HSA 2017 Plan are terminated

Scenarios 3:(Verified Through UI Import)Eligibility Contingency :Future tier Increase
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 03/01/2016 And Increase tier 2017 Medical plan HSA plan Is not Impacted.

Scenarios 4: (Verified Through UI Import) Forced Contingency :Retro tier Increase
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.

Scenarios 5: Forced Contingency :Waived parent Plan all Child plan is terminated
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.
4]Waived Medical plan the Both HSA 2016 and HSA 2017 Plan are terminated

Scenarios 6:(Verified Through UI Import)Forced Contingency :Future tier Increase
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 03/01/2016 And Increase tier 2017 Medical plan HSA plan Is not Impacted.

Scenario:7 Consider Medical as Core plan and HSA Plan Force contingent On Medical Plan(Verified through UI and Import)
1]Added new employee with Effective date 01/01/2017.
2]All core plans are enrolled With Effective date 01/01/2017.
3]2017 HSA plan is also auto enrolled with effective date 01/01/2017.
4]But termination date is set for all Core plans 01/01/2079. Which is invalid refer attached screen shots

For above 6 Scenarios it is working as per expectation But for Scenario:7 Wrong termination date is set to employee.

Thanks,
Rashmita

Hi Tracy Kot,

CC: Satya

We have scanned affected employee on JE Dunn, ASML and Softchoice.
No affected employee found except JE Dunn.

Please let us know should we do data correction for JE Dunn?

Thanks,
Neelam

Hi Rashmita Dudhe,

CC: Satya

As per discussion with you scenario 7 is as per implementation in WT-3301.
Please let us know if you need any more information on this.

Thanks,
Neelam

Hi Neelam Yangal,

The issue related Core is came Because of Jira WT-7000.
So, I have verified all scenarios for this and it is working fine as expected.

Thanks,
Rashmita

Neelam Yangal yes, please send me the list of employees that were impacted by JE Dunn and yes please fix them ASAP?

CC: Satya

Hi Tracy Kot,

CC: Satya

We have done data correction, With tomorrows effective date service execution data will reflect in the system.
And Affected employees are:
1) Lance Gliser
2) Desmond Clark
3) John Schlick
4) Vincent Ward
5) Matthew Mirtsching.

Thanks,
Neelam

Neelam Yangal can you let me know if this was fixed in production yet so that it doesn't impact any others? Also, the client is saying this also appears to have impacted employee Nathan Mock which is not on your list above. Did this same issue impact Nathan Mock? EE had a QE and his HSA appears to be removed.

Also Urgent, for John Schlick: It doesn't look right in Workterra. In WT confirm it shows $400 per pay period but if you look at view history the employee made an update on 12/27 during the birth QE. Why does the confirm show $400 per pay check if the employee made an update on 12/27? Did you may correct him in the wrong amount?
CC: Satya

Neelam Yangal any updates?

Satya and Mandar Kulkarni
Can I please get an update on this. For JE Dunn when EE had a QE their HSA enrollment termed and showed EE not enrolled in HSA. I do not have a good understanding if this is fixed or still an issue? Is this what happened to Nathan Mock too? Also, I already fixed John Schlick so do not update John Schlick. Thanks. CC: Neelam Yangal

Hi Tracy Kot

CC: Satya, Rakesh Roy
This patch is not deployed on stage and production yet, So Issue is coming on stage as well on production.
We had required some time for code review and testing core scenario on our local environment.
Now, we have done with code review by Amruta Lohiya and testing on local environment by Rashmita Dudhe.

Rakesh Roy: Could you please provide stage and production deployment date to Tracy.

We will update you once we done with data correction of affected employee.

Thanks,
Neelam

What can we do in the meantime to please prevent this from happening?

Could you please start testing on stage ASAP?

As per you mention Above i have verified below scenarios On Stage Environment:
Scenarios 1: (Verified Through UI Import)Eligibility Contingency :Retro tier Increase
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.

Scenarios 2: Eligibility Contingency :Waived parent Plan all Child plan is terminated
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.
4]Waived Medical plan the Both HSA 2016 and HSA 2017 Plan are terminated

Scenarios 3:(Verified Through UI Import)Eligibility Contingency :Future tier Increase
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 03/01/2016 And Increase tier 2017 Medical plan HSA plan Is not Impacted.

Scenarios 4: (Verified Through UI Import) Forced Contingency :Retro tier Increase
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.

Scenarios 5: Forced Contingency :Waived parent Plan all Child plan is terminated
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.
4]Waived Medical plan the Both HSA 2016 and HSA 2017 Plan are terminated

Scenarios 6:(Verified Through UI Import)Forced Contingency :Future tier Increase
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 03/01/2016 And Increase tier 2017 Medical plan HSA plan Is not Impacted.

all scenarios are working fine as expected

Hi Tracy Kot,

CC: Satya, Mandar Kulkarni

We have corrected affected employee
Please find below list

This patch is now ready for production. we will deploy this patch to production on 1/16/2017.

Currently we don't have any quick solution to prevent this, but still we will correct the data if we found any such affected employee.
Please let me know if any further action required on this.

Thanks,
Neelam

Hi Tracy Kot,

CC: Satya, Mandar Kulkarni, Rakesh Roy

As per production patch process we are going to deploy this patch on 1/17/2016.

Thanks,
Neelam

@neelam, was this done? Do you know of any other employees were impacted? Is this fixed in prod now? Thank you.

Tracy Kot This is deployed on production, please check and confirm.

Hi Rakesh Roy we are trying to confirm on this.

JE Dunn EE Jason Crookshank, in View History: WT shows $100 per pay check AND the $25 per pay check. As though he elected both at the same time.
But per the client he was going from the $100 per pay check to the $25 per pay check. Was this part of the issue and code you just fixed or is this a new separate issue?

Rashmita Dudhe Please check and confirm.

As per you mention Above i have verified below scenarios On Production Environment:
Scenarios 1: (Verified Through UI Import)Eligibility Contingency :Retro tier Increase
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.

Scenarios 2: Eligibility Contingency :Waived parent Plan all Child plan is terminated
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.
4]Waived Medical plan the Both HSA 2016 and HSA 2017 Plan are terminated

Scenarios 3:(Verified Through UI Import)Eligibility Contingency :Future tier Increase
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 03/01/2016 And Increase tier 2017 Medical plan HSA plan Is not Impacted.

Scenarios 4: (Verified Through UI Import) Forced Contingency :Retro tier Increase
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.

Scenarios 5: Forced Contingency :Waived parent Plan all Child plan is terminated
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.
4]Waived Medical plan the Both HSA 2016 and HSA 2017 Plan are terminated

Scenarios 6:(Verified Through UI Import)Forced Contingency :Future tier Increase
1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016
2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
3]Employee Raised QE with Effective date 03/01/2016 And Increase tier 2017 Medical plan HSA plan Is not Impacted.

all scenarios are working fine as expected

Hi Tracy Kot,

This issue was Existing and was resolved with this patch.

We have verified mention scenarios by adding employee with same customization.
and the issue is not existing as this is resolved with patch.

The mentioned issue came before the patch deployment on production.
Henceforth this issue will not replicate.

Thanks,
Rashmita

Rashmita Dudhe, thank you. If this resolved now and in production?

Hi Tracy Kot,

This patch is deployed and verified on Production.
Kindaly, Update Jira accordingly.

Thanks,
Rashmita