When the System Loses the Patient

Recently, while traveling in a developed country, I ended up doing something no one wants to do when away from home: visit an emergency room.

I arrived at around eleven in the morning with a respiratory problem. I had been referred by my travel insurer and, at first, everything seemed normal. I provided my information, showed my passport, and waited.

The screen indicated an approximate waiting time of two hours. Those two hours passed, and something began to feel wrong. Other people were moving forward, my name did not appear, and no one called me.

Eventually, I asked.

The person assisting me checked the system and discovered something surprising: I had not been registered.

I had spent hours waiting, convinced that I was part of the process, but as far as the system was concerned, I practically did not exist. My information was entered again, and shortly afterward I was called.

It could have remained a simple anecdote. But several hours later, it happened again.

By then, I had already gone through tests, lab work, electrocardiograms, medical consultations, and respiratory treatment. Yet at a certain point, I stopped moving through the process again. After a prolonged wait, another review showed that I had apparently fallen out of the point in the workflow where I was supposed to be.

The system had lost the patient for a second time.

My total stay ended up approaching ten hours.

However, this is not a story about a bad hospital. Quite the opposite. It was a hospital in a developed country, with highly qualified medical staff and a customer service team that, from a human perspective, struck me as exceptionally committed. Doctors, nurses, and frontline staff showed professionalism, respect, and a clear willingness to help, even under intense pressure.

And that is precisely why the experience was so interesting. The quality of the people and the clinical care did not seem to be matched by business processes and a patient experience at the same level. There was a gap between human excellence and the way the system organized, connected, and tracked the patient journey.

I did not see a lack of commitment. I saw something far more revealing from an organizational perspective: good people trying to sustain a system that made their work unnecessarily difficult. The excellence of people cannot indefinitely compensate for weak processes.

At some point, I stopped looking at the situation only as a patient and inevitably began looking at it as a consultant.

Throughout the journey, I had to repeat information at different points. My name was used in different ways. I moved through multiple stations, professionals, and waiting periods. Every transition represented an opportunity to lose information, visibility, or time.

What struck me most was that, when something failed, there did not seem to be a sufficiently visible mechanism saying: “This patient should be at the next stage, and they are not there.”

The patient effectively became their own tracking system. I had to stay alert, ask questions, and verify that I was still inside the process.

During the wait, I also noticed new equipment and people apparently supporting those operating different workstations. I do not have internal information about the hospital, and it would be irresponsible to claim exactly what was happening, but from the outside it appeared that some kind of technological transition or implementation was taking place while a critical operation continued to run.

And that raised a much broader question:

How many digital transformations fail not because the technology is bad, but because we install new technology on top of processes that were never redesigned?

Digitizing a process does not mean transforming it.

If an organization still has too many steps, repeated data capture, unnecessary handoffs, fragmented responsibilities, and blind spots, a new system may simply end up digitizing the existing complexity.

Perhaps, then, the first question should not be what software we need, but something much more fundamental:

If we could redesign this experience from scratch, how should it work?

We would probably start with a single admission, a consistent identity, and data captured only once. We would design a visible workflow, with clearly defined responsibilities and the ability to know, at any moment, where each patient is.

In fact, the whole model could be summarized in three very simple questions: Where is the patient? What still needs to happen? Who is responsible for the next action?

If a system cannot answer those three questions in real time, we are still relying too heavily on manual oversight and individual initiative.

This is where artificial intelligence and automation can create real value. Not necessarily by replacing people, but by reusing information already captured, detecting stalled patients, summarizing histories, classifying documentation, supporting communication across languages, anticipating capacity constraints, and making bottlenecks visible before they become problems.

The opportunity is not to eliminate the human element. It is to give time back to people so they can use it where it creates the most value.

I left the hospital with my condition treated and with tremendous respect for many of the people who helped me. But I also left with a professional reflection that goes far beyond healthcare.

In transformation, we talk extensively about software, platforms, automation, and artificial intelligence. And yet technology does not solve everything. Real transformation depends on three layers that must work together: people, processes, and technology. If one of them fails, the other two end up absorbing the friction.

We also need to be careful with canned models. Best practices are useful, but not every organization, operation, or experience can be solved by applying a standard recipe. Some situations require specific designs built around the context, the constraints, and the experience we actually want to create.

That is why, before buying another tool or adding another layer of technology, it is worth seeking support to integrate the pieces. The solution should not belong only to the technical specialist who knows a particular platform. It requires someone capable of connecting strategy, customer experience, processes, people, data, and technology, and turning them into an end-to-end system that actually works.

That integrator role has been an important part of my work for years: looking at the whole problem, asking the uncomfortable questions, and helping design a solution that makes sense for that specific organization, not for some generic one.

Because digital transformation does not mean installing new technology. It means designing an organization capable of delivering a better experience, and using the right technology to make that possible.