Page 1 of 1

Revenue management

Posted: Sat Oct 24, 2015 9:42 am
by NJMD
I use Medisoft Version 19.1.3.38 Networking on a total of 3 computers. We set up RM a few months ago on all three but used only one to send claims. Somewhere along the RM program updated itself to 3.1914.15253.377. The other two clients were not using the installed RM. Today when I tried to run RM on those rarely used clients the RM gives an error saying the RMdatabase has been changed to a newer version so you need to upgrade RM also. The client version of RM on these two computers is 3.1914.15118.363. It also instructs how to upgrade by going to Start>Programs>revenue management>upgrade however such file does not exist. I am stumbled on how to upgrade. All computers have same version of medisoft. Please guide. Thanks

Re: Revenue management

Posted: Sat Oct 24, 2015 10:59 am
by NJMD
I was able to solve it.

In case somebody else has the same problem here is what I did:

On the client computer which needs the RM updated go to the C:\Medisoft\Bin\RCM folder and run the CCupdate.exe and CMupdate.exe files and it would download patches and update the RM.

Re: Revenue management

Posted: Mon Oct 26, 2015 8:24 am
by Andrew
You can also go to Start>All Program>Revenue Management> Check for Updates on OS with start menu. You can also type in update in newer Microsoft OS and run Check for Updates. It will have a globe and lightning arrow on it as the icon.

Re: Revenue management

Posted: Tue Oct 27, 2015 7:50 pm
by forza42
I got the update an RM is still saying there was an error. It says to redo my actions because my claims were not submitted, but they were accepted by Relay Health? I just can't get the reports. Any ideas? Thanks!

Re: Revenue management

Posted: Wed Oct 28, 2015 10:29 am
by NJMD
Andrew wrote:You can also go to Start>All Program>Revenue Management> Check for Updates on OS with start menu. You can also type in update in newer Microsoft OS and run Check for Updates. It will have a globe and lightning arrow on it as the icon.
Andrew for some reasons I was not able to able to make this way work although that was the path the error alert was advising. Don't know why! Regardless it works for now.Thanks