Hi Kira Hamilton,

Below are updates :-
Issue 1(The EHCW fee is showing as $76.63):
This is a script issue. Invoice is considering current as well as extended rate.
We will be creating new bug ticket to give fix for this.
For now we have done script correction in City of SeaTac. Please regenerate December invoice to get correct cost $41.63.

Issue 2 (The EHCW fee for $41.63 is also being credited back for terminated employees):
As per data in tables invoice is pulling correct adjustments. For employees getting adjustments, rate 'EHCW 2017/2018' was active from 4/1/2017 and has been termed as never effective by '3/31/17'. Hence, adjustments are appearing back from April.

We will ask enrollment team to look into this

Hi Jyoti Mayne, could you please check Issue 2.

Thanks,
Jyoti Agrawal

cc:Prasanna Karlekar,Gaurav Sodani

As per discussion, deleting a newly created bug JIRA for this and converting this JIRA to bug.
We will be giving code fix in this JIRA itself.

cc:Gaurav Sodani

Hi All,

We are working on this.
As per discussion Corrections will be done 11/21/2017 IST.

Regards,
Abhilash Warkari

CC : Jyoti Mayne, Gaurav Sodani, Jyoti Agrawal

Hello,

For clarification, will Issue 2 be resolved by tomorrow November 21?

Also, per the client, "if you refer back to WT-11058, you will see that the April terms were not correct. They occurred as a result of updating a user defined field in error when the employees were already terminated. There should be no credits."

Thank you,
Kira Hamilton
Debbie Kulling

Hi Kira Hamilton,

Please find updates for Point #2.

Concern: The EHCW fee for $41.63 is also being credited back for terminated employees

Cause: EE 'MARGARITA FLORES' was having correct rate before rate recalculation of date time 2017-11-16 12:03:10.300.
Initially EE was terminated with 9/30/17 effective date on 0/6/2017 11:43:25. Again on 09/07/2017 06:08:18 datetime, his effective date changed from 9/30/17 to 4/1/2017. So he is terminated with effective 4/1/17.
Due to 2017-11-16 12:03:10.300 rate recalculation, system terminated 4/1/17 rate as never effective, as rate is not eligible for terminated EE.

Same issue happened with two other EEs.

Correction: We have corrected rate data from back end for reported 3 EEs.

Note: To avoid such type of issue in future, please do not recalculate rate for terminated EEs.

Jyoti Agrawal, Please verify on invoice.

Cc: Amruta Lohiya, Prasanna Karlekar

Hi Kira Hamilton,

The concern raised are resolved now.
EHCW fee will be showing $41.63 and terminated employees will not get adjustments. To see changes please regenerate December invoice.

Please note we are still keeping this JIRA open as we need to give a code fix for Issue 1.

Jyoti Mayne, I have verified records in invoice, terminated employees are not getting adjustment now. Thank You for correction.

Thank You!
Jyoti Agrawal

cc:Prasanna Karlekar

Hi All,

Attaching the development approval email for your reference

Regards
Gaurav

Hi Prasanna Karlekar,

Tested the scenarios attached in the excel on LB on City of durham for hspl company. All the scenarios worked as per expectation.

This is ready for Stage.

Thanks,
Venkatesh

Following are the 3Cs:
Concern:
1. The EHCW fee is showing as $76.63 which is incorrect
2. On extending the rates termination date, in Self Insured Component tracking table, value after decimal is missing
3. On extending the rates termination date, when multiple components are mapped,value for single component getting inserted multiple times which was equal to number of components mapped to the rate.

Cause:
1. Earlier EHCW 2017/2018 rate was only till 12/31/2017. Recently this was extended to 12/31/2018. On extending the rate, new entry effective from 1/1/2018 got inserted in Component tracking table. At the time of invoice generation, sum up of cost effective with 1/1/2017 and 1/1/2018 was happening. Instead it should have only considered the cost which was effective for the span of 1/1/2017
2. While extending the rates, component cost was considered of type integer instead of decimal
3. To fetch the isbillable flag of Self Insured component, we have referred Self Insured Components table. Due to JOIN condition, 1 record set was repeated for numeber of self insured components binded to a rate.

Correction:
1. We have added condition to consider cost from billed rate/component tracking tables, which has effective date less than or equal to invoice month that is being generated.
2. We have changed the data type to decimal
3. Added distinct condition to avoid repeatition.

Scenarios Unit tested:
1. Adjustments related to Billed Rate and Self Insured Components, with and without Rates extension
2. Self Insured Components tracking table on rate extension.

Affected files:
For #1: OES_SP_GetRetroBillingDetails_InvoiceBenefitWise
For #2, #3: trgUpdBilledRateAndSelfInsuredChanges_Log

Impacted areas:
1. Adjustment section
2. Self Insured Components tracking table, when Rate is extended

Hi Prasanna Karlekar,

I have updated the testcases and also tested them on LB. All the scenarios are working fine as expected.

This is ready for Stage.

Thanks,
Venkatesh

Hi All,

This ticket has been approved for stage deployment on 12/21/17.

Regards
Gaurav

Hi Prasanna Karlekar,

I have tested all the test cases on Stage on 2018 CHMC For Hspl company. They are working fine as expected. This is ready for Production

Sachin Hingole,Hrishikesh Deshpande

Thanks,
Venkatesh

Hi Prasanna Karlekar,

I have tested all the test cases on Production on AFI For Hspl company. They are working fine as expected.

Sachin Hingole,Hrishikesh Deshpande

Thanks,
Venkatesh

Hi Kira Hamilton,

The issue has been resolved and also tested on Production. Please could you verify and close this ticket.

Thanks,
Venkatesh

Hi All,

Attaching the production deployment approval email for reference

Regards
Gaurav