Code modified and checked into trunk and LB, (SP modified: dbo.OES_SP_Fetch_COBRAReason)
This has happened due to WT-687 changes.

Rohan J Khandave

Cause: As employee is getting duplicates rows due to two cobra events in history, coverage tier calculation was going wrong as per employee count per cobra event.
We should have one employee per cobra event.

Correction: Code is modified to handle this scenario, but needs to be regressed WT-687 with this.

check after LB build

Couldn't check this due to other priority tasks3

Will check this tomorrow

Hello - please check asap. Need to get COBRA files streamlined so little to no errors are received weekly.

Thank you!

Vinayak Kulkarni

Hi Vinayak,

Verified on LB on Prime Healthcare company. Tried above scenario but didn't get Enrollment COBRA coverage tier label after termination.

Below is the scenario steps and details
Employee Name : LUMBERA GREGORIA
Company Name: Prime Healthcare

1) Changed employee class to Per Diems with (effective date :02/01/2016)enrollment in EPO 3 Plan CHMC CNA got terminated with 04/30/2016 along with dental and vision plans as per Event Rule
2) Exported the NEW HRSimplified_COBRA Coverage Template
3) Above change exported on the file with enrollment COBRA coverage tier label
4) Enrollment added to Value Plan CHMC PD by raising qualifying event from today's date with Spouse coverage.
5) Terminated Employee Status with 04/25/2016.
6) Exported NEW HRSimplified_COBRA Coverage template
7) Record exported with blank Cobra Coverage Tier label

Please look into this scenario and let me know .

Hi Anirudha,

It is coming up blank due to both different cobra event happened on same day, i.e.
1] Full time to part time
2] Termination

And our current new cobra approach implementation have problem in this case for cobra tier.
As it is assumed that only one cobra event will take place on any given day for a employee.
And this is rarest scenario so that it is yet to handle.

After exporting file, please change dates of LB server to make second cobra event and test this.

Vinayak Kulkarni

I've generated scenarios for WT-687 and for the description mentioned above. Verified for the first COBRA event today (04/18/2016) . will perform the second COBRA event tomorrow (04/19/2016) and update you with the results accordingly.

*Note: *Unable to perform these by changing system date (app server, web server , db server) as getting server error while export after second COBRA event after date change to 04/20/2016. (PFA attached error log 4202016124232PM_1601_12304.txt ). When contacted N &S team regarding workterrauser password expiration . They said it was reset last week only, it expires after 30 days from the date of reset.

Hi Vinayak,

One thing I noticed on 'NEW HRSimplified_COBRA Coverage' template today (04/19/2016) while going ahead with the yesterday's scenario(04/18/2016)). Below are the steps and result I found

1) Started OE on Prime Healthcare effective 05/01/2016
2) Made OE changes (Removed Children from EPO3 Plan) for an employee CORTES SANDRA.
3) Terminated this employee effective from 05/01/2016 on 04/18/2016
4) Exported 'NEW HRSimplified_COBRA Coverage' template .
5) Teminated employee exported (along with COBRA coverage tier Label) on the file.
6) Terminated employee effective from 04/25/2016 (Name : ANGELY LEDESMA PUUPATAMMATA) for which class change scenario has been performed yesterday.

Result : Still getting records (Med,Den,Vis) for CORTES SANDRA every time I export the 'NEW HRSimplified_COBRA Coverage' without deleting previous run date.

Please look into this improper behavior of the template and let me know with your findings.

Company Name :Prime Healthcare
Testing Environment : LB

Note: Also tried exporting 'NEW HR Simplified_COBRA Participant' template. Same record getting exported on every export

Hi Vinayak Kulkarni
Verified the termination followed by class change scenario along the scenario for WT-687 on LB on Prime Healthcare Company .

File exported successfully and records are as expected . COBRA Coverage tier label populated as expected in case of both above scenarios

Note:Also verified above mentioned issue (Termination is continuously exporting on file) scenario is also fixed

Please change the status of this JIRA item so that we can move it to the stage.

Please move to production. Not sure how to change the status above.

Thank you!

Hi Aniruddha,

We cannot move this without WT-2008 as changes are same for both.

Hi Vinayak Kulkarni

Verified the class change followed by termination scenario on Prime Healthcare company on LB .
COBRA COVERAGE Tier Label exported on the file is sgl+spo. Spouse was enrolled in the plan before employee termination. This is doubtful because as per your comment on WT-2008. It should be 'sgl' only right ?
Please update on this ?

Test Employee : MARCIA MOORE

As per our discussion on above comment. COBRA coverage tier Label getting exported on file is proper and it is Working as expected and WT-2008 is also fixed .

Marking this JIRA also Ready for Stage

Vinayak Kulkarni This is missed by Dev team or QA team. We need to provide reason and how we can catch such issue in future.

HI Rakesh, this was scenario specific issue where an employee had two cobra events. one in december 2015 and second is now.
And this multiple cobra events for single employee was not handled in code logic which was causing blank tier.

And this kind of scenario can happen on only selected client like prime where class change could cause employee to become cobra.

two cobra event were
1] Class change to part time or per diem
2] Employee termination

We need to add this scenario to our test cases to avoid such issue in future.

Hi Vinayak,

Verified below scenarios on Prime Prod Copy for HSPL on stage. on New HR Simplified Participant, New HR Simplified Dependent , New HR Simplified Coverage Templates .

1] Class change
2] Class Change followed by Employee Termination
3] OE Changes (OE Effective 06/01/2016) followed by Employee Termination on 06/01/2016

. Observed two issues for scenario #2 as below

Description :
1) Employee (MONIQUE,RAY) initially had class change on 12/19/2015 . Employee Exported on all files properly with COBRA coverage tier labels. Enrolled her in Value Plan (CHMC PD) effective from 04/01/2016 and status changed to terminated today (05/27/2016). Record exported with BLANK COBRA coverage Tier Label on Coverage File.

2) Qualifying event code getting exported for above employee on Participant file is RH instead of TE.

this is due to missing script , please test this after next stage patch.

Vinayak Kulkarni

Verified above after stage patch exporting these templates again.
Issues listed above still exist.

Hi Vinayak,

Verified again by recreating scenarios for Class Change followed by termination. .Issues listed above still exist.
Note: observed one more issue where old enrollments (Dental and Vision) also getting exported on coverage file which is not expected and these enrollments have cobra coverage coverage tier populated along with it. The new enrollment after class change populated BLANK COBRA coverage tier label on the file

Test Employee : STEVEN,RUSH
Company on stage : Prime Prod copy for HSPL

Thank you.

Discussed this with design team and came to solution, but need to check impact on existing solution then only we'll go the solution.

As per discussion, best possible solution is to have Member type for cobra events on event builder table.
But this input should not be taken from screen, instead we need to find out member type depending upon what are the fields used in event.

Export team will first verify this solution and will also check impact on existing file before giving go ahead for the change.

Putting onHold as awaiting changes to be done by EDS team.

Please clarify - you state "Putting onHold as awaiting changes to be done by E*D*S team." Did you mean E*B*S Team?

Jennifer Johnson

Thank you!

Hi Amber,

Its not EBS, we have development EDS team, sorry for the confusion.

High level estimates

Hi Vinayak Kulkarni

As per the discussion , as of now you can insert manual entries as workaround.
EDS team will take this as enhancement for permanent solution .

CC : Satya Vijay Siddha

Hi Vinayak Kulkarni

As of now, work around is done for this for Prime companies.
For actual enhancement , we don't have bandwidth till 16th Aug 2016. Please let us know if this is needed on priority .

CC : shyam sharma Satya Vijay Siddha Rohan J Khandave

Quick fix has been done on production for below Prime companies

Prime Healthcare
PrimeHealthcare
CHMC
EHMC
DMC

Do we need to keep this ticket open until the complete update can be done on August 16, 2016? Please advise.

Changed this story to Think story for analysis and coming up with implementation logic and test case writing. updating estimates only for Analysis.
Sheetal - please attach analysis document to this JIRA.

Hi Vinayak Kulkarni

Please find the Analysis document and WT-1850 Analysis.doc and ETA WT-1850 Estimates.xls
Please review and let us know if it is fine.

CC:Sheetal Bodhale Satya Swapnil Pandhare Vijay Siddha
Thanks,
Chaitali Acharya

Hi Chaitali,

We are find with the given analysis, Below is feedback.

1] Please change column name to "EventMemberTypeID"
2] Can we have data correction script to correct default value to spouse type or child type if applicable? Otherwise we will share list of companies where we need proper data. Thanks.

Hi Vinayak Kulkarni

We will change column name to "EventMemberTypeID".
We will prepare the correction script but please provide us list of companies as well to verify.

CC:Sheetal Bodhale Swapnil Pandhare Vijay Siddha
Thanks
Chaitali Acharya

Hello,

My name was added to this ticket in error. Think Story isn't my client.

Thank you!

Analysis has been completed. For implementation please refer JIRA ticket WT-7705