Free EMR Newsletter Want to receive the latest news on EMR, Meaningful Use, ARRA and Healthcare IT sent straight to your email? Join thousands of healthcare pros who subscribe to EMR and EHR for FREE!

Is It Time To Divorce Your HIT Vendor?

Posted on May 2, 2017 I Written By

Anne Zieger is veteran healthcare consultant and analyst with 20 years of industry experience. Zieger formerly served as editor-in-chief of and her commentaries have appeared in dozens of international business publications, including Forbes, Business Week and Information Week. She has also contributed content to hundreds of healthcare and health IT organizations, including several Fortune 500 companies. Contact her at @ziegerhealth on Twitter or visit her site at Zieger Healthcare.

Few organizations are totally satisfied with their technology vendors. Even if they’re doing their best, their relationship with you can be disrupted by issues like staff turnover, changes in the product roadmap or an acquisition. Depending on how well your partnership worked in the first place – and how dependent you are on their technology – you may choose to ride out such issues.

But there are times that you have to make some hard decisions about your future with a vendor, particularly if their overall strategy diverges from yours. If you’re wondering how to sort out whether you need to part ways, you might want to consider some suggestions from Dick Taylor, MD, executive vice president with healthcare IT consulting firm MedSys Group. Dr. Taylor’s “Signs Your Vendor’s Not That Into You” include:

  • The new upgrade comes with sticker shock: If the new software calls for a costly “forklift upgrade,” and all told will create a lot of expense and issues, be concerned.
  • Their technology is very dated: If the vendor hasn’t adopted current technologies like virtualization, web services and the cloud – or at least considered whether they’re appropriate for customer needs — it’s a bad sign. Remember that part of your maintenance fees should go to long-term planning by the vendor that incorporates emerging tech as needed.
  • They haven’t stayed in touch post-sale: Expect for not only sales people to touch base, but also experts from R&D, support engineering and implementation to check in and ask about your needs and concerns. If they don’t, maybe they just see you as a revenue stream.
  • Their engineering staff has been gutted: Some vendors reduce their engineering roster, particularly if they’ve acquired the product in question, seemingly in the belief that their source code will maintain itself. This will not end well.
  • They don’t have customers like you on board anymore: You don’t want to be part of a dying customer base. In fact, you want to make sure other customers like you – such as, say, other large health systems – are still part of the mix. Otherwise, it’s unlikely developers will address your specific interests.
  • They’ve lost their focus: Given the rapid pace at which new healthcare technologies emerge, it’s easy for vendors to get distracted. Of course, it’s all well and good that they’re aware of cutting-edge technologies. That being said, make sure they don’t plan to rush in a new direction and ignore your needs.

Other vendor warning signs that came to mind for me included:

  • They don’t respond promptly to service requests
  • The people who interact with you are rude or poorly trained
  • Their new contract has hidden “gotchas” in it that they won’t consider addressing
  • The product can no longer do the job for which you acquired it, and they don’t seem capable of fixing it to your satisfaction

In some ways, important vendor relationship are like marriages in that every situation is different and that some give and take is involved. But if your relationship isn’t working, or undermining your plans, you’ve probably reached the end of the road.

Switching EMR and EHR Software

Posted on August 16, 2012 I Written By

John Lynn is the Founder of the blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of and John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

I’ve long been concerned about the challenge of switching EHR software. I’ve recently got into some discussions with people asking why EHR certification and meaningful use didn’t require EHR data portability as part of the requirement.

I’d forgotten that Jerome Carter had pointed out in a previous EHR switching post where HHS asked for comments on EHR data portability in the proposed certification rule for EHR (PDF) under the section “Request for Additional Comments”. Here’s his comment with the page number that addresses it:

John, this series of posts on changing EHR systems is interesting. The data issues that arise when switching EHRs can catch providers off guard. In reading through the proposed certification rules for EHRs, I found a section on data portability that you might find interesting. It is on page 13872.


It’s an interesting section to read. The key is that they acknowledge the need to have some EHR data portability if you’re a doctor. Then, they look at these 4 questions:
1. Is the consolidated CDA enough?
2. How much EHR data do you need to move to the new EHR?
3. Could they start with an incremental approach that could expand later?
4. What are the security issues of being able to easily export you EHR data?

These are all good questions. I’d answer them simply:
1. Is the consolidated CDA enough?
No, you need more.

2. How much EHR data do you need to move to the new EHR?
All. Otherwise, you have to keep the old EHR running and what if that old EHR is GONE.

3. Could they start with an incremental approach that could expand later?
I think they need to go all in with this. The consolidated CDA is basically an incremental approach already.

4. What are the security issues of being able to easily export you EHR data?
I always love to follow it with the opposite, what are the issues of not having this EHR data portability available? You do have to be careful when you can export all of your EHR data, but the security is manageable.

What are your thoughts on EHR data portability? I’d still love to find a way to help solve this problem. It’s a big one that would provide amazing value.