Hi all - how did you verify the OAD scenario? UHC is stating it still is not working. Please see below -

I’ve tested this in FDU Prod and it looks like it is working under the Divorce scenario, however, the OAD scenario is still incorrect.

The Par files and the COV files are pulling in the correct info, but the Dep file is still pulling in the terminated (already previously sent) overaged dependent on the second set of dependent termination files.

I tested this in FDU Prod with Jenna Test (OAD) and Travis Test (Divorce).

These are what we are expecting on these connections:

First set of test files run after the dependent is terminated:

Par file: Dep (OAD/Ex-Spouse) termination

Dep file: blank

COV file: the coverage for the family

Second Set of Test files after the EE has terminated status:

Par file: EE termination

Dep file: the remaining dependents (if any) excluding the OAD or Exspouse (Currently Ex-Spouse is correctly being withheld, OAD’s are still being passed)

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

For Jenna Test, She had a child (Baby Test) who turned 26 on 7/21/16. The OAD service ran and removed her coverage. The first set of COBRA files picked up the Baby correctly. Jenna then termed status on 8/2. On the second set of COBRA files, the Par and COV files pulled the correct information, however, the child was still passed on the Dep file.

After high level analysis we found below

This occurs only when OAD and OAD followed by EE Termination scenarios take place in different months (as in case of Jenna Test). Implementation works fine when OAD and Employee Termination happen in same month.