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

Get ready for the invasion of the healthcare bots

Everywhere I go lately I hear people chatting about chatbots. It seems that every health organization is preparing to launch a chatbot service or at least has it on their roadmap. Once I noticed this trend, I keep asking the people I meet about their "bot strategy" and thus having my own small contribution to the trend. There are countless cases where a digital personal assistant or a chatbot could help physicians, nurses, patients or their families. From assistance in simple routine tasks like finding a doctor or scheduling an appointment, to better organization of patient pathways, medication management, help in emergency situation and offering a solution for simpler medical issues. The general idea behind the buzz is that in the future, these talking or texting smart algorithms might become the first contact point for primary care. Patients will not get in touch with caregivers directly for health questions but will turn to chatbots first. Only in case the bot can ...

Clinical data warehouses: Sometimes it's worth being lazy

If you are a health organization you probably have or thinking of having a clinical data warehouse. A Clinical Data Warehouse (CDW), sometimes called Clinical Data Repository (CDR), is a database that consolidates data from a variety of clinical sources to form a unified view of a the data for various purposes. Typical data types which are often found within a CDW include: clinical laboratory test results, vital signs, patient demographics, administered meds, hospital admissions, ICD-9 codes and more. Developing and sustaining an effective CDW operations unit is a substantial effort and long-term commitment. The main challenge in designing a CDW is defining its scope and the use cases it should support. In theory a CDW can serve as a basis for reporting, studying and planning. The use case that is often mentioned in relate to CDW is supporting clinical trials. This would allow for researchers to have all the information from a study in one place as well as let other researchers benefit...

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...

Digital Health Thoughts

Search This Blog