Can I go from v11.1 back to v11.0 ???

[Smilesbypayet]

Ok, I know that I shouldn't have done this on the weekend, but I did, so sue me......LOL

I updated our software on Sunday from v.7.9/15 to 7.9.32, and then I wanted to update to v11, since Jordan said it was not in beta any more. HOWEVER, when I tried to find the update to v11, there was no option for it -- the only option I could see was for the 11.1 beta. So.......silly me, I decided to install it. DOH!

Now I want to know if there is any way to go BACK to v11?

If there is not, then my staff and I REALLY REALLY REALLY want to complain about the new set-up for entering insurance payments, because it adds at least a couple steps that are irritating, seemingly pointless, and "fixing" something that wasn't broken in the first place!

[drtech]

I don't think there is a way unless you want to restore to your Sunday database backup and loose everything from the last two days.

I haven't tried the new insurance entry...I take it from your comments that you REALLY don't like it?

[jordansparks]

No, can't go back. I just did a video on the batch insurance payments for our staff, and it worked as smoothly as I thought it would. I'll make it a priority to add that page to the manual. I am very curious why you think it takes longer.

[jordansparks]

Imagine that you are a large health clinic, and that you have just received an EOB with 200 claims on it. You have gone into each patient account and entered the amount paid. Now, it's time to create the insurance check. You cross your fingers and push the button. The check comes up with all 200 rows selected, but the amount is not the same as the amount on the EOB. What do you do? There is no way to audit. The order of the claims is different on the EOB versus the what you see on the screen. And god forbid that someone else in the office has started entering some other EOB, because then their claims will be intermingled with yours. So only one staff member at a time can enter payments. It will probably take you all day to sort it out, time that you simply do not have.

As I hope you can see from the very common scenario above, insurance payment entry WAS most definitely broken. This was not just an annoyance, but a major cashflow issue.

Instructions have now been entered in the manual.

[jordansparks]

OK, I finally see what the problem is. You want to be able to go see the account for each patient so that you can review it and take any necessary followup action. I have put it on the bug list as, "Batch insurance payments need to have an option to automatically attach paid claims."

It won't take much work for us to do that. Welcome to the wonderful world of beta testing.

[drtech]

I haven't tried it yet, so I may like it, but based on feedback here...if we have individual claims, do we have to use the batch process to enter the check from the manage module instead of right from the account/claim?

[jordansparks]

So we did a minor overhaul today, and the ins payment entry is now pretty much back to the old way of doing it unless you purposely choose to do a batch entry. It hasn't been released yet. Beta users need to regularly watch the bug tracker. Once you see that it's released, you can update.

[drtech]

the update is posted to the SVN...it is safe to use it if we compile right?

[jordansparks]

Yes.

[drtmz]

Front desk hates batch processing. Most of our bulk checks are 10 patients or less. Occasionally they are larger but not often.
Can't wait until the old way is restored. They are forming a 'flash mob'. Ykes!!

drtmz

[drtech]

my staff told me the new update is much better today than yesterday...thanks. (You have to compile it yourself to use it until OD officially releases the update)

[Smilesbypayet]

Since I have absolutely no idea what it means to "compile" anything in this context, I will wait until OD releases that bug fix. I just looked and saw an update for 11.2 - but it's dated 10/3 not today. I'm assuming then, that is not the bug fix we need? Should I still go ahead and install that small update?

Thanks, Jordan!

Indeed, we are not one of those big clinics. Probably 90% of our insurance payments are for individual claims, so it was making us jump through the hoop of using the batch payment method, even if it wasn't for batch checks.

At some point, though, I will be able to "just" install the most current stable version and get "off" the beta train?

[drtech]

I think you will find you always want to try out some new feature in beta once you step into it :p

[jordansparks]

Version 11.1 will gradually become more stable and less annoying. Over the next few months, it will gradually become the "non-beta" version. Just keep updating 11.1 frequently to take care of the little bugs, but don't update to 11.2 while it's still beta. So, yes you can get off the beta train slowly.

[Smilesbypayet]

I think you will find you always want to try out some new feature in beta once you step into it :p

While I'm sure you're correct that I will want to try out those new features, I'm also quite sure that most of my staff will not.

[Rickliftig]

And that's why you are the boss!!!! Although, many times, I feel like I'm Barney Miller in charge of a staff of characters.....

[Smilesbypayet]

And that's why you are the boss!!!! Although, many times, I feel like I'm Barney Miller in charge of a staff of characters.....

Rick, I have enough other problems to deal with right now......beta testing software is so NOT one of the ones I want!

[jordansparks]

But it's better now, right? It shouldn't be too painful from here on out. But usually only affect the new features, anyway.

[drtech]

my staff says it is much better...

[Smilesbypayet]

But it's better now, right? It shouldn't be too painful from here on out. But usually only affect the new features, anyway.

I haven't had a chance to do the newest updates - that is scheduled for tomorrow afternoon.

[jordansparks]

You realize that you only need to do it from one computer and that it will only take about 20 seconds, right? And you can actually do it right in the middle of a busy day (we do all the time). After that, as other users try to launch OD from each of the other workstations, it will automatically update, a process that takes less than 10 seconds. I'm talking about these minor "build" updates, not the major version updates that also make changes to the database.

[Smilesbypayet]

You realize that you only need to do it from one computer and that it will only take about 20 seconds, right? And you can actually do it right in the middle of a busy day (we do all the time). After that, as other users try to launch OD from each of the other workstations, it will automatically update, a process that takes less than 10 seconds. I'm talking about these minor "build" updates, not the major version updates that also make changes to the database.

Good to know; but I do need to have everyone logged out of the system when it's done, right? Or do you mean the minor updates can be done even while others are using OD live?

[jordansparks]

When you start the update, it will automatically log everyone out. So you can do it any time at all without even bothering to tell anyone you are about to do it. A warning will come up on each workstation telling them to save whatever screen they might be in within 15 seconds. Then, it forcefully shuts them down. Works great.