Home Forums Discussions General Discussion FUBAR

As a 9 year veteran of amazing charts, all I can say is that the current system is FUBAR (MILITARY TERM). We upgraded to 7.12 2 weeks ago, and what a nightmare it has been ever since. I should have stayed with 6.33 and said the heck with meaningful use. Install was difficult and not reversible. Currently myself and my staff are typing in data from old patient charts that either did not or will not move to the new system. The new system does not like changes and I have a population of patients who are in insurance plans that will change because their companies have changed plans. OMG won't that be fun.
The new AC corporate mentality treats customers like step-children who they deal with as those who downloaded a dysfunctional computer game v.s. busy healthcare professionals. But, we professionals are the dumb ones who clicked the upgrade button.

Nate

One of my networks is named Fubar (and with good reason at the time but it's been stable for a long time now.)

I upgraded from 6.6.3 easily. There are many nuances in upgrades: what the starting point is, P2P vs server, server memory, locations of memory. All of them can introduce issues, I've noted in the past.

For me, the upgrade was smooth, faster than I've done in a long time. I did test it out on a trial computer. This occurred shortly after merging of my 2 databases.

I can't speak for you, but for me, it was not an issue at all to upgrade. It did make a number of things better.

A related question is how easy was it to get help (and by what route) and were they helpful?

Thank you for your response.
Going to 7.12 was full of problems. 1. some demographics transferred some didn't 2. most accounts will not let you correct data once you discover it's wrong 3. printing lab or x-ray orders does add dx code 4. encounter forms will not print simple pt. identifying data 5. program will not allow you to change insurance priority like primary to secondary 6. guardian angel support just keep passing it up the chain without letting me know what was going on 7. called, texted, and live chat support with no response ( I was just left hanging with a dysfunctional paid for EMR and paid support) 8. finally got someone who said they were passing it up chain, but there may be a "bug" in the program and therefore NOT fixable 9. not being able to go backward to an AC version (6.33) that was working well is just stupid. Checked and ZERO problem with my hardware.
Sorry, don't mean to unload all this on you.
Nate

4 dx code does NOT print

Did not have the same experience except #3 which is that you have to choose the dx before anything else or it is ignored. This started sometime during V6, it's not really new.
#1 did't have
#2 we change demographics all the time, no issue
#4 don't do encounter forms - can't comment
#5 no issue, do that all the time
#6 and #7 the biggest problem. Often they need to bump complicated things to level 2, but that should have occurred fairly quickly. Most things people call about are level 1 and easily solved. But it seems the way you were handled was unacceptable. I do know they have recently had some changes in support and this may have created some of the problems you've experienced but that is still not acceptable. Many things can be tolerated if you are treated the right way.