Medical Billing - Software System Reports

In the land of medical billing, we get so caught up in the day-to-day operations of getting the bills out, we completely forget about checking to see if our software system is operating the way it should. Needless to say, as problems become noticeable, it is usually because of neglect in keeping an eye on things. In this review, we'll go over some basic system reports that you should be running just to make sure that your software is performing the way it should.

The first report that you should be running is an error report. All software packages track any kind of errors that occur during processing. This could be any kind of processing from submitting claims, to printing forms to running other reports. This error report should be run on a daily basis. The number of errors that occur should be minimal to say the least. If you find a gradual increase in the number of daily errors, this could be an indication that there are problems with the software. The most common of these are corrupted databases. If you suspect this, run a utility to check the integrity of your various databases.

The next report you should run is what is called a failed request report. This usually has to be run on the server unless the software package itself has this capability. Most high end DME software packages do produce a limited failed request report. But if you really want to get a full blown report with all the details that you're going to need. The usual cause of failed request is a bad network connection. If this is what you suspect, have your network administrator run diagnostics on the network. Also have him check all the wiring and network cards in all the computers. Usually the failed requests will come from one particular computer which narrows down your search for the culprit.

You're also probably going to want to run a report on network activity and system resources. For the most part, unless you have a massive billing department, the activity on the server should be minimal. Memory usage shouldn't even register a blip. However, if you find that there are spikes in memory usage, you might want to look at the times of the day that this is occurring. Find out from the billing department when their heaviest periods are as far as billing and other activities. See if there is a correlation between the two.

Finally, you're going to want to run a report to see the rate at which your databases are increasing in size. If you are a large medical billing company, your databases are going to grow at an alarming rate. While your server capacity may be in the gigabytes, it doesn't take long before you find that your medical billing software is hogging up 50% of your disk space. Once you see this happening, you're going to need to make plans to either add another drive or upgrade the one you have.

Medical billing is more than just sending out bills. If your system isn't functioning properly, you could be out of business before you even know what happened.

Michael Russell

Your Independent guide to Medical Billing