Hi Chris,

We have corrected coverage tiers from back-end, see attached list for affected people, Thanks.

SDRMA_GSRMA_CoverageTierCorrection.xls

Vinayak Kulkarni

Hello,

One more person is being reported having the incorrect coverage tier level.

SDRMA - Adah McArtor

This seems to be a very recent enrollment that may have been entered after the previous corrections.

Can we please determine the root cause of this so it does not happen again?

Thanks,
Chris

Yes Chris, this has entered after last correction so I am passing this to enrollment team to get root cause & possible fix.

Amnesh Goel
Can you look into this, I have corrected this one on SDRMA but this is happening frequently and affecting files.

Hi Chris Ellenberger and Vinayak Kulkarni,

Do we have any idea how this is getting happen? means some sort of steps to understand the flow of this problem?

Rakesh Roy Hrishikesh Deshpande Deepali Tidke @ I'd need your help on this. Please help to understand and repro this ticket.

Jyoti Mayne marking to you in case you have any idea over here.

Thanks,
Amnesh Goel

Hi Amnesh,

Nothing specific happened, its simple enrollment added with QE and with wrong HealthTierID.

Amnesh Goel We have tried to reproduced this issue but it is not reproducing.

Employee can enrolled into any plan with any specific coverage tier and same is exporting on file. I dont find scenario to enter Null Coverage Tier Level.

Hi All,

We are trying to repro this at Dev side.

Thanks,
Jyoti M

Hrishikesh Deshpande Amnesh Goel Jyoti Mayne

Hello,

Blue Shield reported another incorrect coverage tier level.

Bartels*Jeremy*J

Showing "EMP" as the tier level but should be "ESP" as his spouse is enrolled.

Please correct this ASAP. Really need to get to the bottom of why this is still occuring...

Thanks,
Chris

Hi Chris Ellenberger,

We have corrected data for 'Bartels Jeremy'.

This issue was not reproducing at our end. So to find the root cause, we added logs in code and deployed on 06/28/2016 but this issue reoccurred for 'Bartels Jeremy' on 6/21/2016. To avoid this issue in future, we are working on highest priority to resolve it.

Thanks and Regards,
:: Umesh Kadam

CC: Amruta Lohiya, Neelam Yangal

Samir
As per our discussion, need audit and correction team for this.

Samir Neelam Yangal Umesh Kadam Amruta Lohiya

Hello,

Update on this please?

Thanks,
Chris

Hello,

Can we please close this ticket? Has been open with no activity since July 2016.

Thanks,
Chris

Hello,

Followed up several times on this ticket. SDRMA is no longer a client of WorkTerra. Please determine if there is a need to continue or if the root cause of this issue has been resolved through another ticket.

Thanks,
Chris

cc Abhay Patil Cindy Wibbing

Satya Jaideep Vinchurkar Please look into this.

Hi Chris Ellenberger,

We have kept this ticket open since the same issue have been reported by other clients as well. Example: WT-9722.
This is not getting reproduced in normal scenario, however keeping this open will help us fix the root cause.

No action required from your side, will update our findings in this JIRA ticket.

Regards,
Satya Prakash

Cc: Jyoti Mayne Vijay Siddha Rakesh Roy Vinayak Kulkarni Jaideep Vinchurkar

Hi All,

This RCF is from last year and we tried in different ways, with different browser. But it was non reproducible. We put log files as well, but due to performance, we removed that code. Today (26th July) we got this year corrupted data. So I will start this RCF after my current task WT-10204 .

Thanks & Regards,
Vinanti R. Yadav

CC :Amruta Lohiya, Satya, Vijay Siddha

I am removing EDI analyst from this ticket as this is purely in the development mode.

Rakesh Roy
Not able to reach the actual root cause. So assigning it to QA if they can help.

Hrishikesh DeshpandePrasad Pise

Rashmita Dudhe As discussed please update max by Sep 20. Earliest updated would be appreciated.

Hrishikesh DeshpandeSatyaAmruta Lohiya

Verified above issue but it is not getting reproduced.
As per reported employee view history tried below scenarios

1]Import employee data
2]Import spouse Information
3]Done election import on Superior Vision Exam & Materials Plan with EE+SP Tier
4]Done election In OE period on same plan
5]Cross verified through Database it showing Correct Healthtier id for both enrollment
6] the Same scenario is done by UI using OE with the retro date current date and future date
7]again Cross verified through Database it showing Correct Healthtier id for both enrollment

Thanks,
Rashmita

Hi Chris Ellenberger,

We have tried at our end but this is not getting reproduced.
You can close this Jira now.

Thanks,
Rashmita

Thanks Chris Ellenberger for closing this .