Overview
At CHIME Fall Forum 2026, one theme came through clearly. Healthcare organizations need to be deliberate about what they scale, simplify, and stop. These five takeaways show how stronger accountability, trusted data, streamlined technology environments, and the right partnerships can help leaders reduce complexity and create greater value.
Key takeaways
- Establish clear AI accountability. Define who owns each use case, its outcomes, and decisions about whether to scale or stop.
- Simplify to strengthen resilience. Reduce unnecessary applications, dependencies, costs, and risk.
- Turn connected data into trusted decisions. Focus interoperability and data investments on information people can confidently act on.
- Start with the problem, not the product. Scale technology when it improves care, access, cost, experience, and performance.
- Expect more from strategic partners. Match expertise, ownership, and accountability to the work rather than handing off complexity.
Healthcare has gotten very good at adding. New applications, digital access points, interfaces, data sources, vendors, and now more AI tools and use cases.
Our Nordic team spent several days at CHIME Fall Forum 2026 attending sessions and talking with health system leaders about what’s working, what isn’t, and what’s getting harder to manage. A consistent tension emerged from those conversations. Health systems need to keep innovating without adding unnecessary cost, risk, and operational complexity.
For me, that reinforces a lesson I’ve learned over nearly three decades in healthcare technology. Start with the problem, not the product. Then determine what combination of technology, people, processes, partnerships, and operating models gives you the best chance of solving it.
Some of the most honest conversations I had during CHIME happened away from the main stage, over breakfast with a small group of women leading technology and transformation, in a focus group with health IT executives, and around dinner tables with health system leaders. In the focus group especially, the message was clear. Leaders aren’t looking for more. They want less complexity and more accountability.
Here are five questions we brought back from CHIME that are worth asking inside your own organization.
Before scaling AI, who has the authority to say no?
Health systems are already adopting AI. The challenge now is putting enough accountability around it to know what should scale, what needs more scrutiny, and what should stop.
The CHIME agenda included multiple sessions on those considerations, including governance after AI adoption has already begun, executive accountability when AI influences decisions, clinician trust, and the infrastructure required to scale AI responsibly.
That theme carried onto the main stage, where a keynote policy panel of women leaders from the C-suite to D.C. examined AI oversight and what federal priorities mean for the health systems that must put them into practice.
The practical lesson is that we can’t let the ability to deploy AI become the reason to deploy it. Every use case should begin with a defined problem and an accountable owner. Leaders should know what outcome they expect to change, how they will measure it, and what would cause them to reconsider the investment.
That discipline is important as AI moves deeper into clinical, operational, and patient-facing workflows. Responsible AI leadership means knowing where to accelerate, but also when to say no.
Do you know what your organization depends on?
Healthcare technology environments are deeply interconnected. Applications depend on interfaces; vendors depend on cloud services; workflows depend on third-party tools; and AI and automation operate across them all. That creates dependencies you may not discover until something fails.
Several CHIME sessions approached resilience from this perspective, examining business continuity, third-party risk, vendor accountability, infrastructure and application modernization, and hidden operational dependencies.
We’re seeing that simplification is a resilience strategy. An application that delivers little value still requires support, security, maintenance, integration, testing, and recovery planning. A redundant tool adds licensing expense while also expanding the environment your organization must understand and protect.
Application rationalization therefore deserves to sit alongside cybersecurity and resilience conversations. Leaders should know which systems are critical, what depends on them, who owns them, and whether maintaining them still creates enough value to justify their cost and risk.
Is more connected data creating better decisions?
Healthcare has invested heavily in interoperability, analytics, dashboards, and data platforms. Yet several CHIME sessions challenged the assumption that more information automatically produces better decisions.
Fragmented definitions, inconsistent governance, poor data quality, and disconnected workflows can leave executives and clinicians with enormous amounts of information but insufficient confidence to act. That has implications well beyond analytics.
Interoperability should not be judged solely by whether data moves. Its real value comes when trusted information reaches the right person early enough to change a clinical, operational, or financial decision. When it comes to AI, an organization cannot build reliable intelligence on data its clinicians and leaders do not trust.
Before adding another dashboard, interface, or data source, leaders should be clear about the decision it will support, what action it will enable, and whether the information will be trusted and available when it’s needed. The goal is less friction between information and action.
It’s a question I keep coming back to: How do we tell the difference between information that changes care and information that simply creates noise?
What are you scaling that isn’t improving care or performance?
Throughout CHIME, there were compelling discussions about what healthcare should stop scaling. Virtual care, ambient technology, digital engagement, AI, and automation can improve care delivery. But an innovation that adds another queue, handoff, login, exception process, or support burden may only move the bottleneck. That is why adoption alone is an incomplete measure of success.
CHIME’s virtual care programming, for example, pointed toward measures such as time to visit, cost per visit, no-show rates, and patient and provider satisfaction. Those measures connect technology to tangible problems such as access, cost, capacity, and experience.
This is where starting with the problem matters. Leaders should always evaluate if an innovation eliminates work, improves work, redistributes work, or just moves work somewhere else.
I like to test this against a single patient. As we prepare a patient-journey showcase for the SoCal HIMSS Winter Collaborative, we’ve asked participating companies to think less about “How do we showcase our product?” and more about “How does our solution help Mary, a hypothetical patient, receive more connected, coordinated, and effective care?” It’s a useful test for any investment. If the honest answer is that it doesn’t help Mary, that’s your signal.
The answer may suggest scaling the investment. It may reveal a workflow that needs redesign. Or it may show that something technically successful should not continue.
Stopping can be a strategic decision, too.
What work should your internal IT team still own?
Deciding what to stop is not limited to technology. Leaders also need to reconsider how work gets done.
Healthcare IT teams are expected to support mission-critical EHR and application environments while strengthening cybersecurity, enabling AI, modernizing infrastructure, improving interoperability, controlling costs, and supporting new models of care.
The reflexive response can’t always be to add another priority to the same team. Instead, leaders should distinguish between work that requires their organization’s institutional knowledge and strategic ownership and work that primarily requires reliable, specialized execution. At CHIME, Nordic held a focus group with health IT executives. We weren’t there to present. We were there to listen. One participant summed up the conversation in five words: “My mess for less never works.”
That stuck with me. Leaders don’t want to outsource their complexity at a discount. They want partners who change how the work gets done. They shouldn’t have to figure out which vendor owns a problem. They want value they can see and measure, not generic promises about scale or savings. And as another participant noted, when managing a partner becomes harder than doing the work yourself, the partnership is at risk.
So, the question isn’t just “What can we hand off?” It’s “Where does our institutional knowledge matter most, and where would the right partner simplify the work, own the outcome, and make it better?”
Start with the problem, not the delivery model. Then match the expertise, ownership, and accountability each priority needs.
Addition cannot remain healthcare’s default strategy
What we heard at CHIME is that healthcare needs to be more disciplined about what it scales, what it simplifies, and what it stops.
For years, new needs have often produced new applications, vendors, interfaces, data sources, and programs. AI dramatically increases both the opportunity and the consequences of continuing that pattern without examining the environment underneath it.
Healthcare leaders should bring the same rigor to subtraction that they bring to investment, starting with the problem they need to solve and working backward from the outcome they need to achieve.
That means being deliberate about what to scale, optimize, consolidate, retire, and manage differently, and making sure each decision reflects the value, cost, risk, and ongoing effort involved. Those decisions affect the IT portfolio, cost, cybersecurity risk, workforce burden, data quality, access, patient and clinician experience, and your organization’s ability to respond when something goes wrong.
Dr. Stephen Trzeciak’s keynote on compassion as a leadership strategy in the age of AI offered a fitting reminder that hope, for patients and for the teams who care for them, is a measurable driver of outcomes. Giving clinicians and IT teams fewer things to manage is one of the most practical ways to protect it.
Healthcare already knows how to add. The next test is knowing when to simplify, rethink, or let go.
If you’re evaluating what to scale, simplify, consolidate, or manage differently across your health IT environment, schedule a complimentary consultation with Nordic to take an objective look at your priorities, identify opportunities to reduce complexity, and determine where your investments can create greater value.
About the author
-
Rachel Weissberg
Rachel Weissberg, Vice President of Client Partnerships at Nordic, is a healthcare technology executive and commercialization leader with nearly three decades of experience connecting healthcare challenges with solutions that can deliver meaningful, sustainable impact. Her experience spans go-to-market strategy, commercialization, digital transformation, virtual care, patient access, operational transformation, and new models of care, with a focus on starting with the problem to be solved and aligning technology, people, and process around better outcomes.