Chris Ellenberger This is deployed on production, please check and confirm.

Chris Ellenberger Please confirm to avoid any delay.

Chris EllenbergerThis is deployed on stage, please verify and confirm to move on production.

We have found the resolution to the above query after internal discussion with Development Team for which WT-7426 is created .

The fix for original issue (Dependents sent on discovery COBRA) is working as expected.
We will move this fix forward .

Ready for stage deployment .

CC: Hrishikesh Deshpande Rohan J Khandave Vinayak Kulkarni

Hi Amit Thorve,

Can you please update us on the query for scenario 3 mentioned in above comment ?

CC: Vinayak Kulkarni Hrishikesh Deshpande Rohan J Khandave

Regards,
Aniruddha Dev

Verified this fix on LB on Test Employees for below scenarios.

Scenario-1 (Employee One)

• Previos Enrollment: Med , Den, Vis Benfits eff from 01/01/2016 - Null
• Covered Members : EE+SP+2CH
• Scenario : one child made OAD (Overage Dependent) on 12/15/2016. Enrolled EE+SP+CH in ANOTHER Medical and Dental plans effective from 02/01/2017 to NULL .Exported COBRA file after eligibility service run on 12/15/2016
• Result: only OAD child exported on file along with Previous Medical, Dental Vision plan terminations. Other dependents not exported on file - Pass

Scenario-2 (Employee Two)

• Previous Enrollment : Med , Den, Vis Benfits eff from 01/01/2016 - Null
• Covered Members : EE+SP+2CH
• Scenario : one child made OAD on 12/15/2016. Enrolled EE+SP+CH in SAME Medical and Dental plans effective from 02/01/2017 to NULL.Exported COBRA file after eligibility service run on 12/15/2016
• Result: only OAD child exported on file along with Previous Medical, Dental, Vision plan terminations. Other dependents not exported on file - Pass

Scenario -3 (Employee Three)

• Previous Enrollment : Med , Den, Vis Benfits eff from 01/01/2016-Null
• Covered Members : EE+SP+2CH
• Scenario : One child made OAD on 12/15/2016. Enrolled EE+SP+CH in ANOTHER Medical and Dental plans effective from 01/01/2017 to NULL . Exported COBRA file after eligibility service run on 12/15/2016
• Result: only OAD child exported on file along with only Vision plan Termination. Previous Medical and dental terminations were not exported on the file for this scenario (as these plans were already terminated on 12/31/2016 when enrollment in other Medical and Dental plans were done effective from 01/01/2017) - Query

Scenario 4 & 5 Also verified Termination and Deceased scenarios for this. - Pass

Hi Amit Thorve,

We have a query on Scenario no. 3 - Can you please let us know what is expected on the file in case of this scenario ? Currently ONLY Vision plan Termination is exporting on file for this OAD scenario.
PFA attached screenshot of test employee's enrollment history.

CC: Hrishikesh Deshpande Rohan J Khandave Vinayak Kulkarni

Regards,
Aniruddha Dev

Files Affected:

/branches/LB/Database Objects/MasterCompanyDB/02_UDFs/dbo.OES_UDF_Export_CobraNotice.UserDefinedFunction.sql
/branches/LB/Database Objects/MasterCompanyDB/02_UDFs/dbo.OES_UDF_Export_DiscoveryBenefitsCobraNotice.UserDefinedFunction.sql
/branches/LB/Database Objects/MasterCompanyDB/04_Stored Procedures/dbo.OES_SP_Export_GetCOBRAEventQualifyingMembers.StoredProcedure.sql

Hi Chris,

Please see below details about issue.

*Concern: * Dependents Jacquelin Phan, Luan Phan, Lu Phan and Anna Phan populated records on the COBRA term file on 11/24/2016 even though they are enrollment into 2017 plans.

Cause: For overage dependent, it was considered as midnight service will drop ineligible members from current plans and it will re-enroll all other eligible members in same plan, but here employee switched plan for next year.
So logic of checking dependent is covered under same plan in future failed and all dependent were treated as COBRA participants.

Correction: We need to change code logic to check if dependent is covered in same benefit instead of checking only for same plan in case of OAD.
We have done this change at our development environment and tested it and found these dependent did not roll out after change.

We will move this change as per QA approval and patch process to production.

Let us know if you have any questions.