Skip to main content

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 not provide adequate assistance, it will transfer the case to a real-life doctor.

As a skeptic technologist, I am a bit uncomfortable with this buzz.  Chatbot is just a computer program designed to carry on a dialogue with people. It can be as smart or as dumb as the developer makes it. Chatbot only replaces web pages or application screens with text. That's it. There is nothing it can do which a simple standard app cannot do. The fact that chatbots do not require a computer screen and present themselves as humans should not give them extra credit from a technological perspective.

The ability to provide a service in a dialogue manner is, however, a valuable asset. It is more natural for us humans and aligns with the way we communicate in our daily life. 
But the real value is the ability to operate almost everywhere. Since small or no screen is required, chatbots can be used to consume healthcare services in ways not possible before. For example, over a virtual assistance agent like Siri or over your favorite messaging platform like WhatsApp and Telegram, we use to communicate with our friends.

The way I see it, chatbots are really all about increasing connectivity. But we cannot overlook this advantage. After all, "It's just about increasing connectivity" is what they used to say about the Internet in its early days...

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

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

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