Home Forums Discussions Amazing Charts Practice Management acpm disaster

PSA...don't make the switch.

we switched our practice management software to acpm hoping to consolidate our emr and billing/scheduling. It has been a total disaster.

Our launch day was yesterday- which we have known about for the past few months. We advised AC that we did not have access earlier this week. We still don't have access at this point. We have gotten very little response or help from technical support. I am not even sure if they are working on it.

Our old biller has suggested we continue to use our old practice management software (and biller) in the meantime.

Which is fine, but we would be paying for two different PM companies. we cannot get any help from ac. Many of our physicians have spent time trying to fix it to no avail.

AC is not the same company they were when we signed up a decade ago.

For what it's worth...
Over the years we switched software billing services three times (none involving AC). Each time we were promised the patient and billing data could be cleanly transferred. Each time, the data was totally corrupt. By the third time, we knew what was coming, and did what we did the previous times right off the bat; make all patients re-register and re-enter their data, run new charges on the new system, and keep the old one alive until the AR were thoroughly run out. It also served to clean up a LOT of bad phones, addresses, insurance data, etc.

thanks. it was a stressful 1st 48 hours but ac technical support were able to fix the issue. it seems to be working fine now.

definitely helpful to keep the old system up an running though.

I can tell you from years of hard experience: There is NO SUCH THING as a clean transfer. Anyone who tells you that is a blatant liar.

1. It is unreasonable to think that two different softwares from two different companies written by two different development teams will have the exact same features.

2. It is unreasonable to think that two different softwares from two different companies written by two different development teams will have implemented their similar features the same way.

3. It is entirely possible that one vendor uses a very well known as easily useable database, such as SQL Server, while the other vendor uses a less well known and very finicky database such as DBISAM or Postgres. Or both vendors will use less well known databases.

Best bet is to do a test run of any data conversion, work out the bugs, then schedule a REASONABLE go-live date for a final conversion then move to production.

JamesNT

AC is a great company. Both regimes made two decisions which I never thought were in the best interest of the user.

1. Jon Bertman - part of the reason if not the reason Jon got out when he did was the debacle of developing his own PM. This was too big an endeavor and also coincided with meaninglessuse.

2. After Pri-Med bought it, ACPM was developed.

While in a perfect world, and for many ACPM is great and I am trying not to bash it, it's just as James said everything has to work perfectly together.

But, for those who it works for that is great.

And then there was Inlight
(actually not a bad product but going off in a completely different direction)