Skip to main content

SOS against capitalist healthcare pigs

We all hear those stories every now and then about the outrages amounts of money that health organizations spend on buying a piece of software. There are no secrets in the healthcare industry about which software vendors are the ones lifting the expenditure bar. The majority of them are US-based companies looking to expand internationally after they have pretty much exhausted their opportunity in their home territory, leaving it with almost twice the health expenditure per capita from the runner up in the world.

In any other industry, private companies generating large profits deserve nothing but applause. However, when it comes to the healthcare industry one cannot overlook the fact that money that was allocated to improve patients’ health is being transferred to wealthy businessmen.

It will be naive to think that when it comes to the healthcare industry executives and shareholders will abandoned their playbook for the good of their society. Therefore, with that in mind, the job of keeping costs down is left again to the buyers.


There are ongoing debates about which strategies yield the best ROI: best of bread vs. one stop shop, subscription vs. perpetual licensing model, etc.
I would like to suggest 3 different criteria for buyers to consider when evaluating healthcare IT products. Those are: Separation of concerns, Open source and Sharing of IP - SOS in short.
  
Separation of concerns – we all know that developing a product is essentially different than implementing a product, which is a completely different story than operating a product. A company which bundles those three activities together and provides implementation and hosting services on top of the product license should raise a flag. A health organization’s inability to select their service providers on top of the software they purchase, simply means that their software provider has a monopoly for providing services for its products. Like every monopoly in history, the provider will claim that their "consolidated" model reduce overall costs, however, as history taught us, lack of competition often results in inefficiencies and is a recipe for poor quality and high costs. Buyers should be free to choose their implementation and support partners and if their vendors do not allow that, they should ask themselves why. 


Open source – as a heavy regulated industry, healthcare IT was always a late adopter of technology. Open source products can be found nowadays in any technology stack from databases to front-end frameworks, and often get updated more frequently than their proprietaries counterparts. Why spend a ridiculous sum on Oracle when the free open source PostgreSQL DB can do an equally good job in terms of privacy and data protection that are so curtail when handling PHI? In addition,  vendors that make use of open source platforms (e.g. JS instead of JAVA) spend less on their infrastructure, something that will surely be reflected in their product costs. In 2019, being fashionably late, the time has come for healthcare IT to embrace open source!


Sharing of IP – how many times have you bought a product just to find out that you have to invest a huge amount of resources (and money) in implementing it, and eventually realize that much of its "content" is actually yours? The flexibility of a product to accommodate the buyer needs is much needed and welcome, but that agility should not be abused by vendors. Products are being evolved with every implementation and new IP  is being generated in this process. As a buyer of the product you should be able to easily leverage the knowledge gained in past implementations, and to be able to contribute your own experience to others to come. The mechanism for such knowledge sharing must be transparent and tangible. Customers should demand the ability to reuse any functionality created by another health organization at minimal cost and without redoing the work. This can be done via an online shop or even something simple as written instruction documents. Whatever the mechanism is it shouldn’t be just be described to you, you need to be able to actually get it!




Comments

Popular posts from this blog

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

Are we ready for a Cloud First hospital?

I will start this article by defining what I mean by the term a Cloud First hospital. The term cloud has been a buzz word in the past decade which led many organizations to declare their support for the cloud, sometime without understanding its true meaning. For the purpose of this article I am proposing a simple test to decide whether an organization is a cloud first or not. If you are software vendor you must have an IT department which directly in charge of the system up-time at your clients sites. If you are a health organization then you should never have visited the data center where your data resides. A Cloud First hospital is one which more than 50% of its systems reside in data center that none of its staff members ever visited or not even sure where they are. According to a recent survey by Datica, in the US only 17.7 percent of the respondents say they work with healthcare organizations that have more than 50% of the existing software infrastructure remotely hosted or

The big battle: Best of breed vs One stop shop

The world of economics has decided on this debate a long time ago: monopolies are bad, diversity is good. No matter what a monopoly promises, you can rest assure that over time the lack of competition will cause prices to go up and quality to go down. When it comes to healthcare IT, however, there is one unique factor that flips the coin – interoperability. Despite various attempts the healthcare industry has yet to solve the interoperability challenge in a satisfactory manner which will enable a full continuum of care across different health information systems within a health delivery organization. Taking a common scenario of prescribing a medication order in theatres using a surgical system to be later administered in a ward requires significant investment to achieve, even using the modern Fast Health Interoperability Resource (FHIR) protocol. The investment required to streamline the data flow across systems raise in an exponential order with every new system that is thrown to t