Hi Charlie,
I am in agreement with you 100%. There was a BAR issue that was opened several months ago that was supposed to fix an issue that was happening when screening a claim. When they moved the changes in to "fix" this problem, users noticed that when they went to edit or view a claim, they were getting kicked out of the system. I notified MEDITECH by a phone call AND opening a ticket, asking them to get this fixed ASAP, because our internal auditor had a deadline she needed to meet by the end of the day, and she needed to be able to view some claims. It was not fixed until the next day. Not only that, but we have also purchased their Scanning & Archiving solution and are in the middle of setting this up. We just had to cancel the Apps visit, because we had 17 tasks open with them relating to problems that I have found so far while setting this up. There was no point in having Apps training when their product is not functioning correctly in TEST. Also, the archiving functionality was described differently when they were selling the product as opposed to when we went to dictionary training. I have also discovered "functionality" that was mentioned in the demo training is not working correctly. I opened a task about it.to summarize, when he told me that it would not work, I told him what we said to our CFO at the demo visit regarding this issue, because she was the one asking questions about it. In the end, the specialist said that he had spoken with development, who said that this functionality was not available, and that he was incorrect of his understanding of the functionality. Every time I take 2 steps forward, I get knocked 3 steps back. I go to set up one part of the product, and I find that something is not working correctly. I open a task to get the problem corrected. And the cycle repeats itself. They definitely oversold this "unfinished" product. They told us things that would happen that are not going to happen. Our HIS director is peeved. Her department is in desperate need of this product, because they are running out of space keeping up with medical records. She realizes that we are not the problem, but that MEDITECH is the problem, and she is VERY unhappy with them. I could go on and on about things I am displeased with concerning this product, other issues, and with MEDITECH, but I could be here all day typing, and you could be here all day reading. I will mention one more thing.I get very annoyed when I have to reset the modems for MEDITECH to dial in and fix something, because other people who dialed in previously did not log out correctly!! Jay Gilmore Systems Analyst Crisp Regional Hospital (229) 276-3173 [EMAIL PROTECTED] _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Charlie Downs Sent: Wednesday, June 20, 2007 8:44 AM To: MEDITECH-L@MTUSERS.COM Subject: [MEDITECH-L] Buggy Meditech programming of DTS's I don't know about everyone else, but I feel that was as Meditech users, really need to get Meditech to improve on their programming accuracy. I've run into more and more programming problems that have totally unintended consequences unrelated to the problems that they were supposed to fix. Below is an e-mail that I sent to our VP of IT this morning. I would like to see some discussion on the L as to how to go about getting Meditech to change. Thanks, Charlie We had a huge problem which we discovered last week, but only realized the consequences this weekend from a DTS which Meditech moved to Live on Thursday. Pharmacy Issue #5294828 was a problem that one had to give a reason when re-processing a billing error when we should have not been prompted for a reason. For some reason, this tied to the drug dictionary where one had to give a reason when updating it. This was totally unrelated to billing, yet when they moved this to live, it not only caused Pyxis billing to stop, but each time an item was removed, it credited a previously removed item. When I called on Thursday, Meditech denied that this was what was causing my problem. I've pasted what they found was the problem below: Rebhan,Maria (MEDITECH) - Jun 18, 2007 - 0948 EDT: Brian, there is a problemwith the DTS we delivered. It was patched correctly but, the code from it iswrong. I've fixed this Inhouse and will just need change control for TEST. Tx If this issue would have been a billing issue, I would have tested it thoroughly before having them move it to live, but it was not a billing issue. I am seeing more and more of this that when Meditech moves a DTS to test or live, it has uninteded consequences that are often not noticed until we are live with it, because no amount of testing will pick up an unintended change entirely unrelated to the DTS. Another example is Pharmacy Issue #5237726. It was supposed to fix a problem with a field not defaulting from the formulary service when adding a new drug (FirstDataBank). After this was moved to live, I noticed that we could not look up drugs as we had before and instead had to use extra keystrokes for look-ups. The hours to correct all of the billing problems is huge. I strongly feel that Meditech needs to be held accountable for what I see as increasingly sloppy programming. I would like to see us file a formal complaint with Meditech over this issue since this is one of many times that I have seen this happen in pharmacy and cause huge problems. Meditech does not even have a Pyxis machine to test out the Pyxis fixes, and instead is relying on the users to test the fixes. In addition, they need to thorougly test other programming changes more thoroughly instead of using their customers as basically alpha test sites. Unfortunately, sometimes we only find out about these programming errors after the fact, which is not right. Hopefully, by filing a formal complaint, we can get their attention, but I would hold my breath. We had an interesting discussion at MUSE about how to get Meditech to change their business practices, and short of a large group of users agreeing to withhold maintenance payments, I don't see them changing. Perhaps it is time for Meditech users to band together and consider such action. Charles Downs PharmD Washington County Hospital 251 E. Antietam Street Hagerstown, MD, 21740 301-790-8904 ***** CONFIDENTIALITY NOTICE ***** This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= To subscribe or unsubscribe to the meditech-l, visit MTUsers.NET. To check the status of the meditech-l, visit MTUsers.NET. For help, email [EMAIL PROTECTED] Visit the MTUsers WikiPedia at MTUsers.NET/mwiki ______________________________________ meditech-l mailing list meditech-l@MTUsers.com http://mtusers.com/mailman/listinfo/meditech-l
