-
Type:
Bug
-
Status: Production Complete
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Module:BenAdmin - Export
-
Reported by:Client
-
Item State:Production Complete - Closed
-
Issue Importance:Must Have
Hi all - how did you verify the OAD scenario? UHC is stating it still is not working. Please see below -
I’ve tested this in FDU Prod and it looks like it is working under the Divorce scenario, however, the OAD scenario is still incorrect.
The Par files and the COV files are pulling in the correct info, but the Dep file is still pulling in the terminated (already previously sent) overaged dependent on the second set of dependent termination files.
I tested this in FDU Prod with Jenna Test (OAD) and Travis Test (Divorce).
These are what we are expecting on these connections:
First set of test files run after the dependent is terminated:
Par file: Dep (OAD/Ex-Spouse) termination
Dep file: blank
COV file: the coverage for the family
Second Set of Test files after the EE has terminated status:
Par file: EE termination
Dep file: the remaining dependents (if any) excluding the OAD or Exspouse (Currently Ex-Spouse is correctly being withheld, OAD’s are still being passed)
COV file: the coverage for the EE and remaining dependents
These are the file templates I used:
Test_RA clone COBRA PAR Del after testing
Test_RA Clone COBRA dep del aft testing
Test RA Clone COBCOV med Del aft test
For Jenna Test, She had a child (Baby Test) who turned 26 on 7/21/16. The OAD service ran and removed her coverage. The first set of COBRA files picked up the Baby correctly. Jenna then termed status on 8/2. On the second set of COBRA files, the Par and COV files pulled the correct information, however, the child was still passed on the Dep file.
After high level analysis we found below
This occurs only when OAD and OAD followed by EE Termination scenarios take place in different months (as in case of Jenna Test). Implementation works fine when OAD and Employee Termination happen in same month.
- relates to
-
-
- Closed
-
| Description |
This is related to It occurs only when OAD and OAD followed by EE Termination scenarios take place in different months (as in case of Jenna Test). Implementation works fine when OAD and Employee Termination happen in same month. |
Hi all - how did you verify the OAD scenario? UHC is stating it still is not working. Please see below - I’ve tested this in FDU Prod and it looks like it is working under the Divorce scenario, however, the OAD scenario is still incorrect. The Par files and the COV files are pulling in the correct info, but the Dep file is still pulling in the terminated (already previously sent) overaged dependent on the second set of dependent termination files. I tested this in FDU Prod with Jenna Test (OAD) and Travis Test (Divorce). These are what we are expecting on these connections: First set of test files run after the dependent is terminated: Par file: Dep (OAD/Ex-Spouse) termination Dep file: blank COV file: the coverage for the family Second Set of Test files after the EE has terminated status: Par file: EE termination Dep file: the remaining dependents (if any) excluding the OAD or Exspouse (Currently Ex-Spouse is correctly being withheld, OAD’s are still being passed) COV file: the coverage for the EE and remaining dependents These are the file templates I used: Test_RA clone COBRA PAR Del after testing Test_RA Clone COBRA dep del aft testing Test RA Clone COBCOV med Del aft test For Jenna Test, She had a child (Baby Test) who turned 26 on 7/21/16. The OAD service ran and removed her coverage. The first set of COBRA files picked up the Baby correctly. Jenna then termed status on 8/2. On the second set of COBRA files, the Par and COV files pulled the correct information, however, the child was still passed on the Dep file. After high level analysis we found below This occurs only when OAD and OAD followed by EE Termination scenarios take place in different months (as in case of Jenna Test). Implementation works fine when OAD and Employee Termination happen in same month. |
Rajendra, Please check this.
| Assignee | Vinayak Kulkarni [ vinayak.kulkarni ] | Rajendra Pawar [ rajendra.pawar ] |
| Status | Open [ 1 ] | In Development [ 10007 ] |
| Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) |
| Dev Due Date | 05/Aug/2016 |
| Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) | Parent values: Development(10200)Level 1 values: In Progress(10206) |
| Item State | Parent values: Development(10200)Level 1 values: In Progress(10206) | Parent values: Development(10200)Level 1 values: Ready for Review(10208) |
| Code Review Date | 05/Aug/2016 | |
| Code Reviewed By | Vinalyak Kulkarni [ 12100 ] | |
| Developer | Vinayak Kulkarni [ vinayak.kulkarni ] | Rajendra Pawar [ rajendra.pawar ] |
| Attachment | Affected Files.txt [ 23378 ] |
| Item State | Parent values: Development(10200)Level 1 values: Ready for Review(10208) | Parent values: Development(10200)Level 1 values: Ready for Local Testing(10209) |
Gokul Sonawane (Inactive)
made changes -
| Item State | Parent values: Development(10200)Level 1 values: Ready for Local Testing(10209) | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
| Assignee | Rajendra Pawar [ rajendra.pawar ] | Aniruddha Dev [ aniruddha.dev ] |
Hi Aniruddha,
We need to regress all cobra scenario for this testing, major part of testing could be
1] Employee Termination ( with Employee Only and with Dependents both)
2] Divorce
3] Employee Termination after Divorce ( in same month of divorce and in next month of divorce)
4] OAD
5] Employee Termination after OAD ( in same month of OAD and in next month of OAD)
6] Employee Deceased
And include various Cobra approaches as well like FDU COBRA, MATT QE, and Jamba Juice's Discovery Benefits.
Let us know if you need more information on this.
| Item State | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) | Parent values: LB QA(10201)Level 1 values: In Testing(10210) |
Hi Jennifer Leugers,
We have started this testing on our Local Environment. We will complete this testing and move patch on Stage environment by Friday,08/12 and then on Production environment by Tuesday,08/16.
Thanks,
Hrishikesh.
Gokul Sonawane (Inactive)
made changes -
| Item State | Parent values: LB QA(10201)Level 1 values: In Testing(10210) | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) |
| Item State | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) | Parent values: LB QA(10201)Level 1 values: In Testing(10210) |
Tested the fix on LB on FDU company with below scenarios
1) Employee Termination (having EE, EE+SP, EE+SP+2ch coverage tiers)
(Current Month Termination and Next Month Termination)
2) Overage Dependent Scenario (having EE+2ch, EE+SP+ch, EE+SP+2ch coverage tiers)
3) Overage Dependent followed by EE Termination (for #2 scenarios)
(in same month, end of same month and in next month of OAD)
4) Divorce (EE+sp, EE+SP+ch, EE+SP+2ch)
5) Divorce followed by EE Termination (for #4 scenarios)
(in same month and in next month of OAD)
All above scenarios are working as expected on LB . This fix Ready for Stage deployment
Note: Deceased Scenario is not implemented for COBRA notice Indicator. Will check COBRA scenarios for Matt and Jamba Juice on stage as these companies are not present on LB.
| Item State | Parent values: LB QA(10201)Level 1 values: In Testing(10210) | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) |
Gokul Sonawane (Inactive)
made changes -
| Item State | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) |
| Item State | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) |
HI Jennifer Leugers,
We have deployed and Tested the fix on Stage . Verified the scenarios on UHC COBRA Templates on FDU test company on stage with all above listed scenarios .
Fix is working as expected on stage and it is Ready for Production. This will be moved to Production as per patch process on Tuesday (08/16/2016) , till then you can start testing on Stage FDU.
Regards,
Aniruddha Dev
.
| Item State | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) |
| Production Due Date | 12/Aug/2016 | |
| Stage Due Date | 11/Aug/16 [ 2016-08-11 ] |
| Production Due Date | 12/Aug/2016 | 16/Aug/2016 |
| Status | Local Testing [ 10200 ] | Stage Testing [ 10201 ] |
| Item State | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) | Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) |
| Status | Stage Testing [ 10201 ] | Production Testing [ 10202 ] |
| Item State | Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) | Parent values: Production Complete(10222)Level 1 values: Closed(10223) |
This fix has been deployed on Production and working as expected.
Thanks,
Hrishikesh.
| Assignee | Aniruddha Dev [ aniruddha.dev ] | Jennifer Leugers [ jennifer.leugers ] |
| Resolution | Fixed [ 1 ] | |
| Status | Production Testing [ 10202 ] | Production Complete [ 10028 ] |
| Transition | Time In Source Status | Execution Times |
|---|
|
1d 23h 29m | 1 |
|
1d 5h 2m | 1 |
|
6d 19h 59m | 1 |
|
4d 12m | 1 |
|
3h 3m | 1 |
Jennifer Leugers
Hi Jennifer,
This is in progress and we would be done with fix by end of this week on our local environment, it would take end of next week to get this deployed on production.
Thanks,
Vinayak