Page 1 of 1
PPO Writeoff Report Bug
Posted: Wed Sep 17, 2008 7:20 am
by atd
I'm printing the PPO Writeoff report using the option to show insurance writeoffs using the procedure date instead of the insurance payment date. If I choose the "Individual Claims" report it works correctly. If I choose the "Group by Carrier" option it's not using the procedure date - it appears to be using the insurance payment date.
Re: PPO Writeoff Report Bug
Posted: Wed Sep 17, 2008 1:52 pm
by jordansparks
OK, I added it to the bugs list.
Re: PPO Writeoff Report Bug
Posted: Wed Oct 01, 2008 1:52 pm
by atd
The bug tracker shows this was fixed in version 6.0.3, but it still isn't working for me.
6.0.3(beta) Released 9/28/2008
6.0.3(beta)(foreign) Released 9/28/2008
PPO Writeoff report, option for procedure date, group by carrier, was not using procedure date.
Re: PPO Writeoff Report Bug
Posted: Wed Oct 01, 2008 8:20 pm
by jordansparks
Hmm. I tested it. Are you sure? I'll put it back on the bug list, but it will be next week until I can get to it. I was pretty sure I caught it.
Re: PPO Writeoff Report Bug
Posted: Fri Oct 03, 2008 7:49 am
by atd
Yes, I'm sure - I just checked again. For the same date range writeoffs show on the Individual Claims version, but the Group by Carrier report shows $0. Perhaps it's on version 6.0.4 instead? I'm running v6.0.3.
I also need to be able to run the report by individual clinic. Could either a clinic and/or provider list be added to the report choices?
Re: PPO Writeoff Report Bug
Posted: Fri Oct 03, 2008 4:45 pm
by jordansparks
That would be a request.
Re: PPO Writeoff Report Bug
Posted: Fri Oct 17, 2008 8:40 am
by jordansparks
I've tested the report repeatedly and it works perfectly. At this point, if you are absolutely convinced it's a bug, create a very simple situation that demonstrates the bug. Then, call us and show us the bug. You can explain to the technician who answers that I have already reviewed the report and do not see a bug. They will try to verify your bug, and then they will get a copy of your database so that we can see what you talking about.