-
Type:
Enhancement
-
Status: Closed
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
Hello,
We received a request from the client and broker to include a new custom event for COBRA.
Note from the broker:
I have confirmed that the loss of health coverage for dependents’ of retirees that are terminated from retiree coverage for the reason of age (Medicare eligibility at age 65) are eligible for a 36 month COBRA offer. The retiree is not eligible for an offer. Only the dependents are eligible.
Linked to WT-8808
Please provide WTS for production deployment so i can communicate to Client, Broker and Vendor.
Thanks,
Chris
- affectedFiles.txt
- 0.4 kB
- Analysis of WT-8875.doc
- 112 kB
- template-statues.png
- 24 kB
- causes
-
WT-9260 Export > Getting server error on export for new HR Simplifed Cobra Participant template
-
- Closed
-
-
WT-9346 Export > Unable to change employee data when medicare event builder rule for retiree is created
-
- Closed
-
- relates to
-
WT-8808 City of Durham > HR Simplified COBRA > Custom Event Request > How to Achieve?
-
- Closed
-
Hi Chris,
We have started working on this, Below are some few points to be noted down.
We checked for cobra template and found "PandA Group_Cobra Term" on City of Durham ( COD )
This template is not pure cobra template ( not built using either new cobra or old cobra approach ), but as it has only Deceased, Retired and Terminated statuses selected, so it is working as cobra template, see below snap for the same template.
However, we are working to apply this enhancement to New cobra approach which uses event builder. So after this enhancement, we need to covert this template to New cobra approach template so that we can apply this enhancement to COD cobra template.
Please find analysis document Analysis of WT-8875.doc , which covers how we are going to achieve this and let us know your views and suggestions on the same. Thanks.
Hi Chris,
Please go through attached analysis document, So that we can proceed with the development.
Hi Vinayak Kulkarni,
Sorry for the delay. Everything looks good on the doc. Thank you for working on this. Will watch out for deployment.
Thanks,
Chris
Hi Anirudha,
Please refer analysis document attached and proceed with testing. Let us know if you have any questions on this, Thanks.
Started Verifying this on LB . Found issue for New HR Simplified COBRA Participant template without mapping Do not export blank cobra event Indicator. For Which WT-9260 is created . Testing is in progress with other scenarios
Please proceed as discussed. Let me know if any help required.
Regards,
Aniruddha Dev
Analysis and Testing
Hi Vinayak Kulkarni,
Created Template and scenarios,Testing is in progress.
CC:Hrishikesh DeshpandeAniruddha Dev
Regards,
Swapnil Eksambekar.
We have copied Production City of Durham company on our local environment for testing purpose. But we are getting some issues on this company while changing employee data .
Ashwin Wankhede and Khandu Kshirsagar are looking into this issue. Will start testing scenarios once this issue gets resolved. We will update you on its progress.
Ashwin Wankhede Khandu Kshirsagar
Can you please update once the issue gets resolved ?
We are unable to create medicare event scenarios . Due to this event builder for which WT-9346 OPEN is created. Can you please look into this , as we are blocked to test actual scenarios for which implementation is done ?
CC-Aniruddha DevHrishikesh Deshpande
Regards,
Swapnil Eksambekar.
Hi Swapnil,
I have updated WT-9346, please check.
Started Verifiying Basic COBRA scenarios for COBRA Data templates for Do not export blank cobra event Indicator on ASML templates . As it is taking too long to export COBRA file on City of Durham.
Will update once done
Verified basic COBRA scenarios with do not export blank cobra event Indicator as Following :-
1)Termination
2)Deceased
3)Divorce
OAD scenario is in progress
It is taking too much time to export and verify scenarios On City Of Durham we have used ASML Company by using same template as City of Durham. Testing is in progress.
Verified all COBRA scenarios for each members covered in the plan as Employee,Employee + Spouse ,Employee + Child,Employee + Spouse + Child with do not export blank cobra event Indicator as Following :-
1)Termination
2)Deceased
3)Divorce
4)OAD scenario
It is taking too much time to export and verify scenarios On City Of Durham we have used ASML Company by using same template as City of Durham.
Employees having Retiree plan scenario will be check on Stage as City Of Durham is taking too much time.
As COBRA file is taking too much time to export,Can you please look into this , as we are blocked to test actual scenarios for which implementation is done ?
CC-Aniruddha DevHrishikesh Deshpande
Regards,
Swapnil Eksambekar.
Hi Swapnil,
Checked this on City of Durham HSPL on stage and found it is not taking that much time to export the file. Below are the step i followed,
Created two cobra event builder
Created template: cobra_Data
Enabled CDC on company.
Set base run-date to 05/01/2017
Changed employee's status (LOUIS ABBOTT ) to terminated
Exported file.
Please make sure base rundate is set before you export the file. Let us know if you need more information on this. Thanks.
Verified all COBRA scenarios for each members covered in the plan as Employee,Employee + Spouse ,Employee + Child,Employee + Spouse + Child with do not export blank cobra event Indicator as Following :-
1)Termination
2)Deceased
3)Divorce
4)OAD scenario
5)Medicare
Dependents are not shown on Exported File For medicare event as well as OAD scenario also not working.
Hi Swapnil,
As discussed, please modify template customization and re-verify scenarios. Thanks.
After modification of template customization , re-verified all scenarios on STAGE.It is working as expected.Ready for production.
We have deployed this enhancement on production. This is implemented specifically for COBRA data template type which uses event builder.
We checked for cobra template on City of Durham (COD) on production and found "PandA Group_Cobra Term" Template. This template is not pure cobra template ( not built using either new cobra or old cobra approach ), but as it has only Deceased, Retired and Terminated statuses selected, so it is working as cobra template we need to covert this template to New cobra approach template so that we can apply this enhancement to COD cobra template.
To get this work we need to map Do not export blank cobra event Indicator on employee subtemplate which will block employee rows for Medicare event as it will find blank cobra event value in DTS. Please find Proposed Implementation in attached Analysis of WT-8875.doc
Let us know in case of any queries/issues
CC:Vinayak Kulkarni Hrishikesh Deshpande Swapnil Eksambekar
Thanks & Regards,
Aniruddha Dev
Hi Aniruddha Dev,
I am unclear what our exact actions are here to make this work.
I looked at the doc and it seems we have to build all of the events in event builder now?
Also, its mentioned that the template needs to be converted to new apporach as well. What exact settings, macros and/or indicators need to be mapped to make the template work as desired other than the new indicator mentioned called Do not export blank cobra event Indicator?
Thanks,
Chris
We have created new event builder for Medicare and also for Retired,Terminated, Deceased COBRA events. You can modify these or create event builder for other cobra events as per requirement.
Also we have cloned PandA Group_Cobra Term template and created a sample COBRA data Template on City Of Durham on Production with name PandA Group_Cobra Term_NEW and made below changes on it.
1) Selected Retiree Plans for Medical Benefit as these plans will be required for Medicare event to happen (You can modify the selection if needed)
2) Mapped Enrollment COBRA Reason in place of Enrollment Status change reason on (Employee, Spouse and Child) subtemplates
3) Kept blank Data transformation for COBRA reason for Medicare event on Employee subtemplate.
4) Mapped newly implemented Do not export blank cobra event Indicator on Employee Subtemplate
5) Also mapped Enrollment Export Participants and non Participants records indicator on Employee, spouse and child subtemplates so that respective dependents will also appear on export file in case of dependent specific COBRA events such as Divorce and Ineligible Dependent
We have enabled CDC on company so that it will track COBRA events from today onward. You can test the new implementation on this template and let us know in case of any queries/issues.
Also please let us know if we need to discuss these changes over a call if required.
CC:Vinayak Kulkarni Hrishikesh Deshpande
Thanks & Regards,
Aniruddha Dev
Hi Aniruddha Dev,
I went through the new template and i have identified there are differences in the new setup vs old approach...
1. On old approach there were two terminations types, Involuntary Termination and Voluntary Termination exporting. Only Termination is exporting now. Please advise why setup is different and what needs to be done for these two Termination types to work.
2. Was divorce never captured in the old approach? Not setup on new approach either.
3. Was normal OAD not populating on old approach? Not set up on new approach either
We really need this template to take over for the old file ASAP and i am still unclear what i need to do to make sure the new file operates just as the old, but with this new event added.
Thanks,
Chris
Please go through our comments on above points.
#1
We will surely find the way out to handle Voluntary and involuntary termination types on new approach . To achieve it, can you please provide the requirement specs document for this COBRA file ?
#2 & #3
Yes, Divorce and OAD events were never captured on Old Approach. Those will get captured on New Approach if Events Builders are created for the same.
Please let us know if we can help you further on this.
CC:Vinayak Kulkarni Hrishikesh Deshpande
Thanks & Regards,
Aniruddha Dev
Hi Aniruddha Dev,
I have finalized events and the new template. I matched the run date maintenance to a previous live file run date, but i am not getting all of the coverages for the participant that exported on the live file. Can you please check to see why they do not match?
Live Template: PandA Group_Cobra Term
-Latest file from 7/26/2017 exported medical, dental, vision and FSA for Samantha Quiser.
New Template: PandA Group_Cobra Term_NEW
-exported with matching previous run date maintenance but only one line for dental exported for Samantha Quiser.
Thanks,
Chris
We could not look into this today due to other priority tasks . We will update you on this by Monday,(07/31/2017).
CC:Hrishikesh Deshpande Vinayak Kulkarni
Thanks & Regards,
Aniruddha Dev
In order to get all coverages for Participant on export file for 'COBRA Data' type templates 'Enrollment Is COBRA Write All Plans Records Indicator' needs to be mapped on each subtemplate (Employee ,Spouse and Child).
Please add a dummy field on each subtemplate and map the mentioned indicator to it.
We have verified this on City Of Durham Test company on Production for 'PandA Group_Cobra Term_NEW Template' records exported properly for employee 'Samantha Quiser'.
Please let us know if we can help you further on this.
CC:Hrishikesh Deshpande Vinayak Kulkarni
Thanks & Regards,
Aniruddha Dev
Thanks Aniruddha Dev.
This template (PandA Group_Cobra Term_NEW) is now scheduled and will take over for the legacy file beginning Wednesday, 8/2/2017 and weekly on wednesdays going forward.
Thanks,
Chris
cc Kevin Walker
Hi Chris,
We would be starting development on 10th April as explained in linked ticket, this would be deployed on production by end of April.