Rohan J Khandave
More details:-
Issue:-Employee terms during OE (ensure term date passes to carriers as needed – seen as never effective)
EBS feedback:-This was discussed last year and was committed to being provided by OE 2016

EBS requesting more info on this - these are employees whose termination date equal end of policy year. System is not recognizing those transactions as something that should pass and is not sending on any feeds.

12/10 - Information required

Latest update:- If not done please provide ETA

Vinayak Kulkarni]Please check and update.

Hi all - please provide an update on this as my call with UHC is in a couple of hours.

Vinayak KulkarniRohan J KhandaveIs there any update on this?Please update if possible.

Hi Jennifer,

We are analyzing this issue, there are some code changes required to solve this issue.
Unfortunately, due to daily support tasks & other issues, We could not complete our analysis.

So at this moment, We do not have ETA but we will provide rough estimates by end of Monday 22th Feb 2016.
Please apologize for the inconvenience occurred.

Thanks

Vinayak KulkarniPlease check.

Hi Jennifer,

During analysis we got following query.

Lets consider below example.
An employee has medical election in plan P1 with Employee+Spouse+Child covered with effective date 01/01/2016.

Child became ineligible from 03/01/2016. So Employee+Spouse+Child election termed with termination date 02/29/2016.
And Employee+Spouse continued coverage with new effective date 03/01/2016.

This child went on Weekly cobra file as OAD.

Then in next week employee's employment got terminated ( status changed to terminated) with retro date 02/29/2016.
Due to this, new election (Employee+Spouse) which was effective from 03/01/2016 became terminated as never effective.
And Employee+Spouse+Child was already termed as 02/29/2016.

So in next Cobra file this employee will get reported with Spouse & Child as dependent.
Here Child's record is sent on two cobra file, one is due to Overage dependent & other due to employee's employment termination. Is this file?

Amit Thorve Jennifer Leugers Please look into this query.
If this is confusing to you then we can have a call to discuss this scenario.

Let us know your inputs on same.

Hi all - why are we talking about OADs? I don't think this issue has to do with overage dependents. This is in regards to OE and the term as never effective so the termination does not go over on the COBRA file as the system doesn't see an active plan to send.

Jennifer Leugers Yes, this issue is not related to OAD.

But the root cause for this issue & root cause of above mentioned OAD issue is same.
And solution for both the issues will be same. So before proposing a solution, we asked query about OAD issue.

Let me know if you have any queries on this.

Vinayak KulkarniRohan J KhandaveCan you provide the efforts required to fix this issue ?

Jennifer Leugers Rakesh Roy

Hello,

Any update on vinayak's query?

So we can do analysis and work accordingly to full fill your requirement.

Thanks,
RohanK

Hi all - 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.

Rohan J KhandavePlease update.

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.

I don't understand this comment ... this comment is also on JIRA 923. These are not the same issue.

There are two issues - one involving the OAD and one involving a "regular" employee term during Open Enrollment.

Vinayak Kulkarni Please chek

Hi all - any updates on this? It has been quite a awhile since any updates were on this ticket.

Jennifer Leugers fix deployed on our local testing environment.

Hrishikesh Deshpande Please verify.

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

Scenarios working fine on LB

Verified on stage on Prime Healthcare for HSPL company along with WT-923

Working as expected on Stage

Hi all - do we have a production deployment date?

Hi Jennifer,

This will be deployed on production in Tomorrow's patch.

The above issue is verified on production. Please check.

Hi all - the above seems to be in regards to an OAD which was another issue that UHC brought up. But the initial issue was in regards to employees terming and the terms not going over as it was seeing their benefits as termed as never effective due to OE elections. Example - I switch from the HMO to the PPO during OE in November with a 1.1.16 effective date. I then term in December but my term doesn't go over as the system sees that my plan was already termed (because I have new plans elected for 1.1.16)

Priya DhamandePlease update.

Hi Jennifer,

Yes, the initial issue mentioned by you related OE is also fixed on production.
Let us know if you have any queries on this.