Home Forums Discussions Problems Refill errors

I keep seeing that I have scripts that need renewals even though I've already sent them in. This actually started last week. I have one that stays in my renewal notification but when I click, nothing shows up. Anyone else having that problem

Has it matched ? Be careful of ones that appear to auto match as sometimes they accidentally match to the first one in your list - I find it is easy to Match a e refill to wrong one which usually based on the alphabet will be alprazolam, acetaminophen-hydrocodone, aspirin based on 1st scrip in their refills.

Hi Marty,

Where do you see this? Is it the "Renewals" on top of the main screen, just below "Scheduled patients" and "Messages"?

Gene

Gene,

It's next to "Renewals" at the top of the screen. Now it says 2(4)but there are only 3 renewals. Not sure where the other one went. And I keep getting repeats for one I've already refilled twice

Hi Marty,

This has been my experience (v6.1.2 and earlier, have not moved to 6.3.3 yet)-

When the erequest for rf cannot be matched, and we use the "Deny and write new rx" from that screen, then the counter on the main screen will not acknowledge that the rf request has been addressed. So I have a "permanent" 2 (2) showing.

The only workaround that I have found is to close the erequest box, go through the usual rx writers in AC, then go back to the erequest box and match and send.

Is this your situation? Gene

Gene,

I'm on 6.010. Have not had this issue until last week. Sounds like the same situation. I can live with it, just thought it strange that it just started doing this last week. Thanks for the feedback

I would recommend instead of using deny and redo ---- just go to match and advise no matching scrip. Then you can open the chart and send new scrip. It should then erase the pending and send them back a no - followed by new scrip.

I have the exact same problem. It shows that I have 5 refills but when i click nothing shows up. If it says 10 refills only 5 show up.

This has happened to me several times since I upgraded to version 6.xx. You can reset the counter to 0/0 by running the Database Tuner, same as when you are upgrading versions.

Thanks John, I'll have to try that. It's annoying