Healthcare Doesn’t Need More Technology. It Needs Its Tools to Work Together.
Healthcare organizations keep investing in new technology, yet frontline frustration continues to grow. Data volumes rise. Dashboards multiply. Decision-making still lags. The problem is not a lack of tools, but how loosely existing systems are connected to the work happening at the bedside.
What This Conversation Revealed
- Most health systems do not have a technology gap. They have an integration gap.
- Healthcare data largely flows upward to boards and regulators, not back to clinicians when decisions are being made.
- Outcomes data explains what happened months ago. Process data enables real-time changes that affect patients and clinicians.
Josh Clark, Vice President of Quality & Safety Operating Systems at the Institute for Healthcare Improvement (IHI), joined Healthcare IT Today at the annual IHI Forum to unpack a different way of thinking about health IT. He shared why quality and safety outcomes often stall despite heavy investment, and what changes when organizations slow their pace of adoption to focus on making existing systems work together.
Why Integration Strategy Needs More Attention in Healthcare
Many health systems assume progress comes from adding one more application to the stack. Clark sees the opposite risk. When new tools are rushed into environments that were never aligned, complexity compounds and frontline staff are forced to absorb yet another point of friction.
“There’s more opportunity to fall behind if we rush into things and force fit them into a system,” said Clark. “We need to do that more intentionally and strategically.”
In the systems IHI works with, platforms that are “good enough” are often already in place. What is missing, according to Clark, is the connective tissue that ties those systems together in service of care delivery, rather than adding more layers on top.
Fixing the Broken Feedback Loop Between Data and Clinicians
Healthcare generates enormous amounts of data, but much of it never returns to the people who need to act on it. Clark put it plainly: “Our frontline folks don’t have the data that they need to make decisions to drive care when they need it.”
In most organizations, data flows from the bedside to leadership, public reporting, and regulators. By the time it comes back down to frontline staff, if it comes back at all, the window to intervene has already closed.
The result is a steady stream of historical reports that arrive too late to change outcomes. Over time, they are ignored until the next quarterly meeting, when they are dusted off and presented back, often to the same leadership teams that commissioned them.
Clark points to mortality rates as a clear example. “The majority of the time we are looking at mortality outcomes which are often two or three months old. That’s not really actionable data.”
In contrast, he highlights areas like sepsis management, where real-time process data can guide immediate decisions. Which patients need antibiotics now? Who needs escalation? Waiting months to analyze outcomes may satisfy governance, but it does little for patients already in beds.
Rethinking the Operating System Beneath Healthcare IT
Throughout the conversation, Clark returned to a consistent theme. Progress does not come from more dashboards or more tools layered onto an already crowded environment. It comes from aligning technology, data, and process around outcomes that matter to patients and the staff delivering care.
When systems are tuned to support that work, other metrics tend to follow. Adoption becomes easier and new technology feels less like another demand and more like a continuation of progress already underway.
In Clark’s view, the most meaningful improvements often begin by resisting the urge to move faster. “We’d actually advise folks to pause for a little bit and spend some time creating a strategy to drive integration of the tech and the data that they already have.”
Questions This Conversation Raises
Why are healthcare IT investments failing to improve frontline workflows?
Because most investments focus on adding new tools instead of fixing how existing systems work together. Without intentional integration, technology increases complexity and pushes friction onto clinicians rather than reducing it.
Why doesn’t healthcare data reach clinicians when it’s most useful?
In many organizations, data flows upward to boards, regulators, and reports instead of back into clinical workflows. By the time insights return to frontline teams, the opportunity to intervene has often passed.
What’s the difference between outcomes data and process data?
Outcomes data explains what happened after the fact, often weeks or months later. Process data reflects what is happening now and can guide immediate actions, such as identifying which patients need escalation or treatment in the moment.
What does an “integration gap” mean in healthcare IT?
An integration gap exists when systems technically function but are not aligned around how care is actually delivered. Data may be captured and reported, but it is not connected in a way that supports real-time decision-making at the bedside.
Learn more about IHI at https://www.ihi.org/
Listen and subscribe to the Healthcare IT Today Interviews Podcast to hear all the latest insights from experts in healthcare IT.
And for an exclusive look at our top stories, subscribe to our newsletter and YouTube.
Tell us what you think. Contact us here or on Twitter at @hcitoday. And if you’re interested in advertising with us, check out our various advertising packages and request our Media Kit.
Healthcare organizations keep investing in new technology, yet frontline frustration continues to grow. Data volumes rise. Dashboards multiply. Decision-making still lags. The problem is not a lack of tools, but how loosely existing systems are connected to the work happening at the bedside.
What This Conversation Revealed
- Most health systems do not have a technology gap. They have an integration gap.
- Healthcare data largely flows upward to boards and regulators, not back to clinicians when decisions are being made.
- Outcomes data explains what happened months ago. Process data enables real-time changes that affect patients and clinicians.
Josh Clark, Vice President of Quality & Safety Operating Systems at the Institute for Healthcare Improvement (IHI), joined Healthcare IT Today at the annual IHI Forum to unpack a different way of thinking about health IT. He shared why quality and safety outcomes often stall despite heavy investment, and what changes when organizations slow their pace of adoption to focus on making existing systems work together.
Why Integration Strategy Needs More Attention in Healthcare
Many health systems assume progress comes from adding one more application to the stack. Clark sees the opposite risk. When new tools are rushed into environments that were never aligned, complexity compounds and frontline staff are forced to absorb yet another point of friction.
“There’s more opportunity to fall behind if we rush into things and force fit them into a system,” said Clark. “We need to do that more intentionally and strategically.”
In the systems IHI works with, platforms that are “good enough” are often already in place. What is missing, according to Clark, is the connective tissue that ties those systems together in service of care delivery, rather than adding more layers on top.
Fixing the Broken Feedback Loop Between Data and Clinicians
Healthcare generates enormous amounts of data, but much of it never returns to the people who need to act on it. Clark put it plainly: “Our frontline folks don’t have the data that they need to make decisions to drive care when they need it.”
In most organizations, data flows from the bedside to leadership, public reporting, and regulators. By the time it comes back down to frontline staff, if it comes back at all, the window to intervene has already closed.
The result is a steady stream of historical reports that arrive too late to change outcomes. Over time, they are ignored until the next quarterly meeting, when they are dusted off and presented back, often to the same leadership teams that commissioned them.
Clark points to mortality rates as a clear example. “The majority of the time we are looking at mortality outcomes which are often two or three months old. That’s not really actionable data.”
In contrast, he highlights areas like sepsis management, where real-time process data can guide immediate decisions. Which patients need antibiotics now? Who needs escalation? Waiting months to analyze outcomes may satisfy governance, but it does little for patients already in beds.
Rethinking the Operating System Beneath Healthcare IT
Throughout the conversation, Clark returned to a consistent theme. Progress does not come from more dashboards or more tools layered onto an already crowded environment. It comes from aligning technology, data, and process around outcomes that matter to patients and the staff delivering care.
When systems are tuned to support that work, other metrics tend to follow. Adoption becomes easier and new technology feels less like another demand and more like a continuation of progress already underway.
In Clark’s view, the most meaningful improvements often begin by resisting the urge to move faster. “We’d actually advise folks to pause for a little bit and spend some time creating a strategy to drive integration of the tech and the data that they already have.”
Questions This Conversation Raises
Why are healthcare IT investments failing to improve frontline workflows?
Because most investments focus on adding new tools instead of fixing how existing systems work together. Without intentional integration, technology increases complexity and pushes friction onto clinicians rather than reducing it.
Why doesn’t healthcare data reach clinicians when it’s most useful?
In many organizations, data flows upward to boards, regulators, and reports instead of back into clinical workflows. By the time insights return to frontline teams, the opportunity to intervene has often passed.
What’s the difference between outcomes data and process data?
Outcomes data explains what happened after the fact, often weeks or months later. Process data reflects what is happening now and can guide immediate actions, such as identifying which patients need escalation or treatment in the moment.
What does an “integration gap” mean in healthcare IT?
An integration gap exists when systems technically function but are not aligned around how care is actually delivered. Data may be captured and reported, but it is not connected in a way that supports real-time decision-making at the bedside.
Learn more about IHI at https://www.ihi.org/
Listen and subscribe to the Healthcare IT Today Interviews Podcast to hear all the latest insights from experts in healthcare IT.
And for an exclusive look at our top stories, subscribe to our newsletter and YouTube.
Tell us what you think. Contact us here or on Twitter at @hcitoday. And if you’re interested in advertising with us, check out our various advertising packages and request our Media Kit.
Go to Source
2026-01-22 21:30
Except for the headline, this story has not been edited by Healthcare Central is published from a syndicated feed.
