-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:
-
Environment:Production
-
Bug Severity:Medium
-
Module:BenAdmin - Report
-
Reported by:Client
-
Company:County of Sutter
-
Item State:Development - On Hold
-
Reported by Customer:BCC
Please see the email below from BCC
The Retiree NM Anthem PPO 1000 0-4 sub rate for the Retiree NM Anthem PPO 1000 2 plan is not calculating correctly on the invoice. The billed rate should be $0 and it listed correctly as $0 in the subrate rate metric. The system is billing the $601.00 self-insured component that is listed in the rates, which is incorrect as the bill shouldn’t be picking up any of the self-insured components of the rate. This is working properly for the other sub rates in this plan, but it is not working correctly for this new 0-4 sub rate.
I manually edited the November invoice to $0 so I could post the invoice today. Can you please look into why the system isn’t suppressing the self-insured component for this plan/sub rate?
- duplicates
-
-
- Closed
-
No fix / correction related to this JIRA is pending.
We have not done any fix against this JIRA. Mentioned issue was handled by backend data manipulation.
We had a call with BCC on 24-Oct-2017, in which changes on Rates Matrics screen related to self insured component were discussed. Please refer Call_24OCT2017_MOM.oft
for MOM.
Discussion related to changes on Rates Matrics screen is in progress on email for which new JIRA will be created once the change is finalized.
Thank you!
cc: Debbie Kulling, Kira Hamilton, Gaurav Sodani, Jyoti Agrawal, Venkatesh Pujari
Adding comments for clarification:
This issue was fixed when bug WT-7195 (which was discovered by QA team) was resolved. Therefore this issue is no longer occurring and will not occur moving forward.
For this client, the data was corrected, therefore this ticket needs to be closed. Since the issue was initially found in ticket WT-7195, this one should be closed as a duplicate.
Let me know if I misunderstood or if there is another reason why this ticket is still open.
Jennifer Reed (Inactive)
added a comment - Satya Prasanna Karlekar
Adding comments for clarification:
This issue was fixed when bug WT-7195 (which was discovered by QA team) was resolved. Therefore this issue is no longer occurring and will not occur moving forward.
For this client, the data was corrected, therefore this ticket needs to be closed. Since the issue was initially found in ticket WT-7195 , this one should be closed as a duplicate.
Let me know if I misunderstood or if there is another reason why this ticket is still open. Hi Jennifer Reed,
Yes, you are correct. The issue was fixed with WT-7195 and will no longer occur.
Also, this JIRA can be closed as duplicate.
But at the same time, please note that, for one scenario client needs incorrect data to reside in our component tracking table. For this scenario, we have manipulated the data which was correct. Proper fix for this, will be change on Rates Matrics screen related to self insured component, that is shared in Call_24OCT2017_MOM.oft email for which new JIRA will be created and worked up on.
Do let us know if you need any more inputs on this. Also closing this JIRA.
Thank you!
cc: Satya, Gaurav Sodani, Jyoti Agrawal
Closing the ticket. marking it as duplicate
CC: Kira HamiltonDebbie KullingJennifer ReedPrasanna KarlekarSatya
Gaurav Sodani (Inactive)
added a comment - Closing the ticket. marking it as duplicate
CC: Kira Hamilton Debbie Kulling Jennifer Reed Prasanna Karlekar Satya 
Hi Kira Hamilton,
Following are the updates regarding pending Billable flag manipulation for County of Sutter:
1. As discussed, we have manipulated IsBillable flag value as 0 for component named "Non Billable" in our tracking table. This has no impact on any other module of the system except for Invoice. Impacted employee was "SAIGEON JANELLE". Due to this manipulation, cost for component named "Non Billable" is not appearing on Invoice for this employee.
2. There was also a scenario, where a Non Billable component was stored as Billable in the tracking table. Due to this instead of Billed Rate, Self Insured Component was getting considered. Impacted employee was "ANNE WESTLAKE". We have done corrections for this too. This will have no impact on Invoice as well as Provider wise export as:
We have done this correction for data consistency.
After correction we have regenerated and verified the changes for Dec-2017 invoice on HSPL copy.
Cost appearing on Invoice seems to be fine.
Kindly regenerate the Dec 2017 invoice and confirm the changes related to component named Non Billable.
Do let us know, if anything more is required.
Thank you!
cc: Debbie Kulling, Jyoti Agrawal, Gaurav Sodani, Venkatesh Pujari, Lalit Kumar