Skip to main content

On vendor lock (or how to turn a customer to an enemy)


All looks perfect when you are in love. The person you're with seems to have all the qualities you were looking for in a partner. He is always there for you, attentive to your needs, promising to fulfill all of your wishes. But as this story goes the statistics kicks in, and you soon find yourself sitting with your friends and moan about very similar things.

When it comes to a healthy relationship between clients and suppliers it is good to follow the same advise a psychologist will give you for maintaining the relationship between you and your partner in life: have constant and open communication, align your plans together etc. But there is one very important recommendation that often escapes and is the hardest to implement and that is to keep your independence!
The advice is really relevant for all industries and is not specific to healthcare, however, when it comes to healthcare it is much easier, as a customer to lose your independence and without even noticing it. Since health organizations tend to be quite different from one another, so is the way the software are being implemented to support the processes and local systems in place. The more a health organization invests in tying a solution that meets its needs, the tighter the bondage between it and the software vendors gets. Contributing to the problem are the facts that many software are considered "mission critical" and the poor financial state of health organizations around the globe doesn't help either.




So what can be done to avoid a vendor lock? It starts with selecting your partner. On your qualification checklist you should have the ability to adjust and extend the software without requiring the vendor. This can be in the form of a solution designer editor or an SDK that you or other service providers can use. 
When building your solution it is better to adopt common practices and standards which are easier to replace, even if it means compromising on your dream solution.
Get to know your vendor clients and share your roadmap and pains on a constant basis – you will be much stronger and vocal together as a group when confronting your vendor. 
Finally, prepare to the day after from day one with a prenup. Make sure the vendor will be committed to assist in migrating the data to a new software if you decide to break apart.

And always remember – a true love comes when you know you can do without it!

Comments

Popular posts from this blog

FHIR Status Check

 More than 2 years have past since I wrote my article  on the Fast Healthcare Interoperability Resources (FHIR®) standard and it’s time to do a quick status check and revisit the predictions I made back then. The FHIR standard continues the strong trajectory of adoption and is now used across the globe. The application programming interface (i.e. the FHIR API) is available in most major EHR systems today. According to the US Office of the National Coordinator Health Information Technology an estimated 85% of hospitals have FHIR in their systems. The NHS has been quick to adopt FHIR and the adoption curve in the UK is high. The NPfIT (NHS Care Record Service) HL7 V3 interfaces are being redeveloped in FHIR®, and new NHS specifications such as the CareConnect standard for secured Transfer of Care  are being specified in FHIR® by default. Despite the industry enthusiasm about the potential of FHIR still the old and faithful HL7 v2 remains the predominant interoperability sta...

Your Hospital on FHIR

As a technologist, I am always skeptical when hearing about a brand new technology that is going to solve all of our current problems. I feel it is my responsibility to warn people about these types of promises. Claims of “solving all healthcare information exchange (HIE) problems” are often being made about the emerging HL7 FHIR standard. According to Gartner’s hype cycle, the standard is at the “Peak of Inflated Expectations,” which I view as a stage where wishful thinking fills the gap created by a lack of knowledge and understanding. FHIR, which stands for Fast Healthcare Interoperability Resources, is a draft standard from HL7 International. This standard is designed to be easier to implement, more open and more extensible than its predecessors, V2 and V3 standards. So what’s the big deal here? Aren’t we simply replacing one transport protocol with another? FHIR claims to bring a change in paradigm to the way health information can be accessed and consumed. Since FHIR is ...

The case for PAA

PAA stands for Patient Admission App. In a nutshell it is a platform in which the hospital can communicate with its patients and their relatives before, during and after their stay in  the hospital. A patient's encounter with a hospital is often a traumatic event to both the patient and his family. A lack of  proper communication between the parties can have major implications on the hospital efficiency and the patient's experience which research shows has a critical impact on the quality of care. From red tape to red carpet  A PAA should accompany the patient throughout his journey by keeping him informed and engaged. This starts prior to the actual admission when the patient feels scared, anxious and confused. A PAA should provide the patient with all the information related to his upcoming treatment. This can include treatment reminders such as not to eat x hours before a planned anesthesia, orientation map, etc. It should also handle in...