Medisoft Version 19 SP1 - Claims Management

Posts related Medisoft software.
Post Reply
nathanburgess
Posts: 17
Joined: Mon Mar 31, 2014 6:47 pm

Medisoft Version 19 SP1 - Claims Management

Post by nathanburgess » Mon Mar 31, 2014 6:55 pm

Even after an upgrade to version 19 SP1 of Medisoft we are still getting this error within some practices. This error even occurs after repair payment preference or repair practice data we get the errors. The error: Access violation at address 00C808E8 in module 'MAPA.exe'. Read address 00000038. This does not occur in all practices and when it does most times the repair practice data fixes the issue.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: Medisoft Version 19 SP1 - Claims Management

Post by Gavin Walker » Tue Apr 01, 2014 8:24 am

What are you doing in Medisoft when you get the error?
Gavin Walker
Walker Tek Solutions, LLC
417-890-6777 x0
fax: 417-763-6386

nathanburgess
Posts: 17
Joined: Mon Mar 31, 2014 6:47 pm

Re: Medisoft Version 19 SP1 - Claims Management

Post by nathanburgess » Wed Apr 02, 2014 2:27 pm

Running statements from the billing statement manager.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: Medisoft Version 19 SP1 - Claims Management

Post by Gavin Walker » Wed Apr 02, 2014 3:07 pm

Try backing up and packing all data and rebuilding all indexes. Does the error occur when you print to a printer?

nathanburgess
Posts: 17
Joined: Mon Mar 31, 2014 6:47 pm

Re: Medisoft Version 19 SP1 - Claims Management

Post by nathanburgess » Thu Apr 03, 2014 6:56 am

Have done all that pack and index actually do that for every practice each month before monthly statements. It is when we go to Print/Send the created statement. After we select statement template, after the data selection question it errors out after that.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: Medisoft Version 19 SP1 - Claims Management

Post by Gavin Walker » Thu Apr 03, 2014 9:40 am

I am leaning towards data corruption, but does it happen after something prints out or before? Try printing half of your statements alphabetically and see if that prints. Then try to work your way down to one problem statement and then go into that patient's ledger and look for anything unusual.

nathanburgess
Posts: 17
Joined: Mon Mar 31, 2014 6:47 pm

Re: Medisoft Version 19 SP1 - Claims Management

Post by nathanburgess » Thu Apr 03, 2014 1:04 pm

was thinking the same thing. We have gone through that process and trying only 1 or 2 statements but same get the error right away. We will prepare and call you guys to get the data set repaired.

Post Reply