-
Type:
Enhancement
-
Status: Production Complete
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Module:BenAdmin - Export
-
Reported by:White Label
-
Item State:Production Complete - Closed
Hi all - this is on the UHC log as being resolved but UHC tested it and says it still does not work. Please see below and advise. Thanks!
OAD and Terms happening at different times within the same month, COBRA files only passing the initial event and not picking up the second event.
This is how I tested in Prod.
I tested with “Testing test” in FDU Prod. The child termed 2/18 and passed on the COBRA file as an OAD. Then I termed the EE 2/21/16 and ran the cobra file again and the EE did not appear on the COBRA file (Test CB Par_RA delete after testing).
Original email to Russ November 19, 2014
I just wanted to follow up on this issue that we had in September as I don't believe it was resolved yet.
We had this for FDU on the COBRA term file. The issue was that if there was an overage dependent that termed earlier in the month and the Employee terms later in the same month, the employee termination would not be picked up on the cobra because it already recognized the overage dependent term that occurred earlier in the month.
I believe that you were looking to see if there was any additional logic that could be placed on the files so that the file could recognize and send both the overage dependent and the Employee.
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Satya [ ID10004 ] | Rohan Khandave [ rohan.khandave ] |
| Assignee | Rohan Khandave [ rohan.khandave ] | Vinayak Kulkarni [ vinayak.kulkarni ] |
We have analyzed this issue and got below query.
If we solve this issue and while sending employee termination which is second event then the child which was already sent as OAD will come again on COBRA file for employee termination event. Is this fine?
Also, this is exactly what I asked in JIRA WT-668, Event though this issue & WT-668 are different, but their root cause is same.
Please update us on query so that we can share ETA.
We have analyzed this issue and got below query.
If we solve this issue and while sending employee termination which is second event then the child which was already sent as OAD will come again on COBRA file for employee termination event. Is this fine?
Also, this is exactly what I asked in JIRA WT-668, Event though this issue & WT-668 are different, but their root cause is same.
Please update us on query so that we can share ETA.
| Assignee | Vinayak Kulkarni [ vinayak.kulkarni ] | Jennifer Leugers [ jennifer.leugers ] |
| Assignee | Jennifer Leugers [ jennifer.leugers ] | Rakesh Roy [ rakeshr ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Assignee | Rakesh Roy [ rakeshr ] | Jennifer Leugers [ jennifer.leugers ] |
FYI - replied with this question on the other ticket but putting it here as well.
Are you able to drop the dependent from the second event since the child has already been passed? In the case of an OAD and an employee term that occurs in the same month or reporting period, we would expect the OAD to pass on the PAR file and to not pass again as a dependent when the EE terminates.
| Assignee | Jennifer Leugers [ jennifer.leugers ] | Vinayak Kulkarni [ vinayak.kulkarni ] |
| Component/s | BenAdmin [ 10000 ] |
We are working on this, We have analyzed & found out way to pick up second event i.e. employee termination.
However, in that way it is picking up dependent as well in second event even if child has already been passed on file.
Now, we are analyzing to drop the dependent from second event. We will provide ETA by tomorrow.
Hi all - expecting an ETA yesterday. Please advise. Thanks!
Development of this fix is in progress, We are targeting to complete it by 11th Feb 2016.
Hi all - is the comment above accurate? We are past February 11, 2016
Hi all - please provide an update as the one three days ago I do not think is accurate.
Hi Jennifer, I meant to say March 11 (Friday), It was typed as "Feb" mistakenly.
Sorry for inconvenience caused to you.
Hi Jennifer,
We are working on this issue , as per complexity this will take 03/15/2016 IST into our local testing environment also it required lots of scenario testing. So you can have it on stage 03/22/2016 IST if every thing goes perfectly.
| Environment | Production [ 10005 ] | |
| Issue Type | Support Activity [ 10301 ] | Enhancement [ 4 ] |
| Status | In Progress [ 3 ] | Local Testing [ 10200 ] |
| Workflow | WT_Support [ 13286 ] | WT_Features [ 14101 ] |
| Item State | Parent values: Local QA(10201)Level 1 values: In Testing(10210) |
Hrishikesh Deshpande please verify.
| Assignee | Vinayak Kulkarni [ vinayak.kulkarni ] | Hrishikesh Deshpande [ hrishikesh.deshpande ] |
| Assignee | Hrishikesh Deshpande [ hrishikesh.deshpande ] | Aniruddha Dev [ aniruddha.dev ] |
| Module | Parent values: BenAdmin(10100) | Parent values: BenAdmin(10100)Level 1 values: Export(10110) |
Verified this enhancement for below scenarios on Payroll Data Template for Old COBRA implementation
1) Coverage Tier : EE+CH
Scenario : Child made ineligible on 03/16/2016 and COBRA file exported on 03/17/2016 . After exporting COBRA child on file status of the employee changed to terminated and again exported the cobra file
Result : COBRA child (Ineligible Dependent) exported for 1st run and COBRA employee (Termination) exported on 2nd run.
2) Repeated above scenario for EE+SP+CH, EE+SP+4Ch Coverage Tier .
3) Also verified employee termination after OE changes scenario as well
Scenarios working fine on LB
| Item State | Parent values: Local QA(10201)Level 1 values: In Testing(10210) | Parent values: Local QA(10201)Level 1 values: Ready for Stage(10213) |
| Status | Local Testing [ 10200 ] | Pending for Stage Approval [ 10300 ] |
| Developer | Rohan Khandave [ rohan.khandave ] | |
| QA | Aniruddha Dev [ aniruddha.dev ] |
| Status | Pending for Stage Approval [ 10300 ] | Approved for Stage [ 10030 ] |
| Status | Approved for Stage [ 10030 ] | Stage Testing [ 10201 ] |
| Item State | Parent values: Local QA(10201)Level 1 values: Ready for Stage(10213) | Parent values: Stage QA(10202) |
Verified on stage on Prime Healthcare for HSPL company
Working as expected on Stage
| Status | Stage Testing [ 10201 ] | Pending for Production Approval [ 10301 ] |
| Item State | Parent values: Stage QA(10202) | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) |
| 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) |
Hi all - please let me know if we have an ETA for prod. Thanks!
Jennifer Leugers
Hi Jennifer,
We will deploy this on Production on Thursday, 03/31/2016 IST. We will let you know once its deployed.
Regards,
Aniruddha Dev
| Status | Pending for Production Approval [ 10301 ] | Approved for production [ 10034 ] |
| Status | Approved for production [ 10034 ] | Production Testing [ 10202 ] |
The issue is verified on production. Please verify.
| Assignee | Aniruddha Dev [ aniruddha.dev ] | Jennifer Leugers [ jennifer.leugers ] |
| Item State | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) | Parent values: Production Complete(10222)Level 1 values: Closed(10223) |
| Account Executive | Jennifer Leugers [ jennifer.leugers ] |
| Resolution | Fixed [ 1 ] | |
| Status | Production Testing [ 10202 ] | Production Complete [ 10028 ] |
Hi all - how was this tested? UHC is saying this is not working. Please see below -
I retested this with the test person: Ima Test in Prod and it doesn’t appear to be working the way I expected. Ima Test had an OAD on 4/12, and then the EE termed 4/20. The OAD was sent on the first COBRA file, however, on the second COBRA file, there was not EE (PAR) or Coverage file generated, but both dependents (including OAD) was sent on the DEP file.
We were expecting that the second file generated would contain the following:
Par file: EE termination (currently missing)
Dep file: the remaining dependents excluding the OAD
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
Hi Jennifer,
Yes, we observed some issues in this as there are lot of cobra file types we have in our system. We will fix this asap.
but testing it would take some time, we will share New ETA once we get issue resolved at local environment.
Aniruddha Dev Please create another JIRA for this and have following clients to our local environment set up to test.
FDU ( UHC ) Cobra notice
PRIME - HR Simplified
MATT - COBRA FEED Indicator Columnwise ( wageworks cobra )
JAMBA JUICE - Discovery benefits Cobra
UVU – Wage Works cobra ( dependent on subscriber sub template )
and find one normal cobra feed indicator row-wise
Also please note down test case as per todays discussion. Thanks.
WT-2008 is created for above .
| Transition | Time In Source Status | Execution Times |
|---|
|
1d 3h 17m | 1 |
|
18d 6h 58m | 1 |
|
3d 22h 15m | 1 |
|
3d 1h 3m | 1 |
|
2s | 1 |
|
2d 19h 33m | 1 |
|
5d 9h 36m | 1 |
|
1d 17h 42m | 1 |
|
14d 22h 42m | 1 |
Please check