Book Image

Transforming Healthcare with DevOps

By : Jeroen Mulder, Henry Mulder
Book Image

Transforming Healthcare with DevOps

By: Jeroen Mulder, Henry Mulder

Overview of this book

Healthcare today faces a multitude of challenges, which can be summed up as the barriers architects and consultants face in transforming the healthcare system into a more sustainable one. This book helps you to guide that transformation step by step. You’ll begin by understanding the need for this transformation, exploring related challenges, the possibilities of technology, and how human factors can be involved in digital transformation. The book will enable you to overcome inhibitions and plan various transformation steps using the Transformation into Sustainable Healthcare (TiSH) model and DevOps4Care. Next, you’ll use the observe, orient, decide, and act (OODA) loop as an iterative approach to address all stakeholders and adapt swiftly when situations change. Further, you’ll be able to build shared platforms that enable interaction between various stakeholders, including the technology-enabled care service teams. The final chapters will help you execute the transformation to sustainable healthcare using the knowledge you’ve gained while getting familiar with common pitfalls and learning how to avoid or mitigate them. By the end of this DevOps book, you will have an overview of the challenges, opportunities, and directions of solutions and be on your way toward starting the transformation into sustainable healthcare.
Table of Contents (18 chapters)
1
Part 1: Introducing Digital Transformation in Healthcare
7
Part 2: Understanding and Working with Shared Mental Models
12
Part 3: Applying TiSH – Architecting for Transformation in Sustainable Healthcare

Understanding people’s states of mind

In the previous section, we discussed two main movements in transformation: technology-driven acceleration and community deceleration or inhibition. Simply put, technology is developing faster than the community is accepting and capable of adopting new technology. Often, this is explained by the fear of that new technology, but that’s rarely true. The issue is that people are not trained to use the technology properly or they are not convinced of the added value. This is probably the main reason developers have a poor understanding of the real needs. The latter is typically fed by perception. Misperception or myths lead to inhibition, especially since one of the characteristics of societies is solidarity and protecting other people. Myths are widely spread and often rigidly fixed, reinforcing inhibition. Only some disruption will break this force. This force is called understanding customer needs. With this force, DevOps can create...