Is Your EHR Relationship Showing Signs of Stockholm Syndrome?

How capable leadership teams can end up having to defend decisions they never made

In August of 1973, a man walked into a bank in Stockholm, took four employees hostage, and held them in the vault for six days. When it ended, the hostages defended him. They told reporters they had been more frightened of the police than of the man who pointed a gun at them. They refused to testify. One of them is said to have helped raise money for his defense.

Most of us know the phrase that came out of it: Stockholm Syndrome. Psychologists have argued about it ever since, and it has never been an official diagnosis. But there is reasonable agreement on the conditions that tend to produce the pattern. Four of them come up again and again:

● The other party holds real power over whether you are okay.

● Small courtesies feel much larger than they are.

● Leaving appears impossible.

● You are cut off from anyone who might offer different thoughts on your situation.

Read that list again with the relationship between a health system and its EHR vendor in mind. It stops being a story about a bank in Sweden.

Is this an argument against the EHR, or against EHR vendor lock-in?

This conversation usually dies in the second paragraph over a misunderstanding, so it is worth getting ahead of it.

The modern electronic health record was a genuine achievement. It ended the paper chart. It made the record portable, legible, and eventually safer. It got dragged through Meaningful Use and came out the other side. It held up in 2020 when it badly needed to. The people who led those implementations did some of the hardest and least appreciated work in this industry, and many of them are still doing it.

Nobody is suggesting a health system rip out its EHR. That is not a real option, and it is not the point.

The point is that somewhere between “we implemented a system of record” and where the industry is now, a lot of organizations handed over some other things without ever quite deciding to. And what got handed over in each case is not just a task. It is a decision right that used to sit with the executive team.

What have health systems handed over to their EHR vendor?

Workflow. When a system defines how the work happens, it eventually defines what the work is. Care teams reshape their processes around the technology. Ideally, it is the other way around where solid processes are supported and enhanced by technology.

In hospital after hospital, a real clinical operations question ends with “that’s just how it works in the system,” and everyone nods and moves on. That one sentence is too common in American hospitals. It also happens to be measurable: a widely cited time-and-motion study funded by the American Medical Association found that physicians spend nearly two hours on EHR and desk work for every hour of direct clinical face time with patients. That is not a training problem. That is the system, not the executive team, setting the terms of the clinical day.

Who you are allowed to work with. This one has changed meaningfully over the last several years, and the industry has not been especially honest about it. Integration used to be a technical question. It is now a permission question, and permission carries a price. Interface work, certification programs, marketplace terms, review calendars, per-transaction economics. Put them together and what you have is a toll booth standing between an organization and anyone else it might want to bring in.

The EHR vendor holds a commercial interest in decisions a hospital makes about partners it does not own, which makes this a position of leverage rather than a piece of integration architecture. And the field of realistic alternatives keeps narrowing: KLAS Research data shows the leading EHR vendor now holds 43.7% of U.S. acute care hospitals and 56.9% of hospital beds, up from 31% of hospitals just four years earlier. When almost every large health system decision goes the same direction, “we could always switch” stops being a credible check on anyone’s behavior.

Function, by way of bundling. The two most effective words in healthcare technology sales are “it’s included.” Mediocre-and-included beats excellent-and-separate on a budget line almost every time. What never appears on that line is the operational cost of the difference between the two.

Time. “It’s on the roadmap.” Organizations defer real operational problems for years waiting on a module. The ED keeps boarding. Length of stay keeps creeping. The margin keeps thinning. The roadmap keeps moving.

Look at that list again. Workflow, partnership decisions, product decisions, and the calendar itself: these are the exact levers an executive team is supposed to hold. They did not disappear. They moved.

What’s the real cost of an EHR implementation?

There is another form of captivity that requires no coercion at all. You simply keep the hostage busy.

Consider what an EHR implementation actually consumes. Two or three years in which nearly every clinical, operational, and IT leader in the building is assigned to one project. During that stretch, almost nothing else starts. Not because anyone decided it shouldn’t. There was simply nobody left to run it.

Then go-live. Then stabilization. Then optimization, which turns out to be a destination nobody ever quite arrives at. Wave one. Wave two. The upgrade. The new module. The next wave. This is not an isolated complaint. In the 2026 CHIME CIO survey, EHR optimization jumped to the top budget priority among large health systems, a category that had not even ranked as the leading priority the year before. The work is not winding down. It is becoming more central, not less, at the exact organizations with the most at stake.

And the calendar is not the hospital’s. Release windows, upgrade cycles, and certification timelines are all set somewhere else. An organization’s improvement agenda now runs downstream of someone else’s release schedule.

Here is a question worth putting to any leadership team: name the operational improvement work this organization has completed since go-live that had nothing to do with the EHR. Then pay attention to how long the pause is.

The real cost of all this was never the license fee. It is the years of operational improvement that did not happen, and the fact that everyone was far too busy to notice they were not happening. When implementation never really ends, the vendor's roadmap becomes the organization's agenda by default, not because anyone handed it over, but because a permanently full calendar leaves no room to set one. And the strategic question, “what should this organization take on next, and why?”, simply stops getting asked.

How can you tell if your health system is over-dependent on its EHR vendor?

It shows up in how this industry talks, and it is language nearly everyone in it uses.

“We’re an ______ shop.” That is an identity statement, not a technology statement.

“We can’t do that, it isn’t supported.” Said the way you would describe gravity.

“Why would we buy that? It’s included.” Asked without anyone having checked whether the included version works the way you need to to.

“We just need to optimize.” Five years and three optimization waves in.

And the most telling one: hospital executives put in the position of defending their EHR vendor to their own board, often requiring more conviction than the vendor’s account team would bring to the same room.

That isn’t the language of a customer so much as someone explaining why the situation is fine.

How does EHR Vendor dependence affect health system leadership?

It would be easy to read all of this as a knock on health system leadership. It is not, and the reason matters.

None of this is a diagnosis of anyone. The argument is that this industry has built a structure that produces all four of those conditions, and then acts surprised when the predictable result follows.

Consider what an organization asks of a CIO or CMIO after an implementation of that size. The job becomes making it work, and most of them do that exceptionally well under conditions few other executives ever face.

What nobody assigns is the separate question of whether the arrangement built around that system is still serving the organization. There's rarely a forum for that question, rarely an owner, and rarely a point on the calendar where it would naturally come up.

It's also a question without a ready answer. As the market numbers above suggest, this is often a single vendor that doesn't acquire, doesn't partner much, and builds nearly everything itself, so there are few alternatives standing by to consider. Asking the question honestly means sitting with it unresolved for a while, and few leadership teams have that kind of room.

Now add a calendar already filled with someone else's work. What you get is a group of highly capable people operating sensibly inside a structure that gives them very little room to do otherwise. This is what happens when the incentives, the economics, the calendar, and the absence of a real alternative all drive in the same direction.

Which is why the question rarely comes from inside the building. It isn't that anyone is avoiding it. It's that it has never been anyone's job.

Is an EHR the same as a hospital’s operating model?

There is one distinction that resolves most of this.

An EHR is built to document what happened. It is a system of record, and a very good one.

Running a hospital is a different problem. It is deciding what should happen next, across every unit and department, in the next several hours. That is a system of operations, and it rests on different assumptions. Documentation is retrospective and patient by patient. Operations is forward-looking and house-wide, built on different data, a different cadence, and a different chain of accountability.

Ask a record system to run operations and it will produce dashboards. It will not produce decisions, or ownership, or escalation when something has been sitting too long.

A hospital can have the best chart in the country and still have fifty patients boarding in its ED at two o’clock on a Tuesday afternoon.

That is what an operating model is for. It defines the roles, so everyone knows who does what. It sets the standard processes for moving patients from admission to discharge. It puts a name on every patient's progress, so ownership and accountability are clear. And it lays out the escalation path, so when something stalls, the right person hears about it fast. None of that is native to an EHR, and forcing it into a system built for documentation rarely holds up on a busy day.

We make that case in more detail in “What Is Your EHR Leaving on the Table?” For now, the short version is that the record and the running of the hospital are two different jobs, and only one of them was ever meant to be assigned to the EHR.

What six questions should health system leadership ask about EHR dependency?

It’s not feasible to leave the relationship. Instead, the goal is taking back the decision rights that drifted away, and that starts with a leadership team able to answer these out loud:

1. Where are we reshaping our operating model to fit the software instead of the other way around?

2. What other solutions have we not evaluated in the last three years because something was included in our EHR?

3. The last time we said no to a partner, was that a clinical decision, a financial decision, or a permission decision?

4. What are we waiting on a roadmap for, and what has that wait cost us in boarding hours, avoidable days, and length of stay?

5. What share of our total change capacity is committed to the EHR right now, and who approved that allocation?

6. Who is accountable for operational performance? Is it distinct from who is accountable for the record?

That last one is an answer that rarely exists. It is also the most important one, and it points to where to start.

Where should a health system start taking back control?

None of this is anti-EHR so much as pro-sovereignty. An organization should be making these decisions itself, not inheriting them from its EHR vendor and then having to defend them.

Where do you start though?

The answer is not to take on everything at once. Start with one area that has a direct effect on the margin and that the EHR was never designed to manage.

For most health systems, that is operations: how patients move through the hospital, hour by hour, unit by unit. It is also the easiest place to begin, because it does not need a spot on anyone’s roadmap. The work sits outside the record. So, it can be run from outside the record.

Start with an operating model that belongs to the hospital, with named owners, a daily rhythm, and escalation that actually happens. Then bring in technology whose job is to serve that model and make it stick, instead of a model shaped around whatever the software allows.

That is the work Care Logistics does. Our Operational Model lets leadership decide how the hospital runs, instead of letting the EHR make those decisions by default. CareEdge technology hardwires the model into the daily work so it lasts. It runs alongside the EHR, not in place of it.

The people in that Stockholm vault ended up defending the man who held them. Health systems don't have to end up defending decisions they never made. Once a year, out loud, ask the question: are we making these decisions, or are we explaining them?