The Missing Ingredient in Healthcare AI Adoption: Accountability

June 27, 2026

Content contribution by Elissa Torres, Director of Transformation and Enablement


Healthcare organizations are under growing pressure to move from AI experimentation to AI adoption. Vendor demonstrations for various AI solutions are everywhere and executive teams are being asked to improve efficiency, reduce administrative burden, strengthen decision-making, and do more with limited resources. AI appears to offer a path forward. 


Yet despite the enthusiasm, many organizations find themselves stuck in a familiar cycle of aligning on the potential value of AI, but struggling to align on the process for deploying it. The challenge is often attributed to regulation, data quality, integration complexity, or organizational resistance to change. 


While those factors certainly play a role, but beneath many stalled AI initiatives is a more fundamental issue: accountability. Healthcare organizations can find themselves struggling to define who owns the decisions AI influences, who monitors outcomes over time, and who is ultimately accountable when those outcomes fall short of expectations. Until those questions are answered, AI adoption will continue to move more slowly than the technology itself. 

 

The Accountability Gap in Healthcare AI 


When an AI-enabled system generates a recommendation, identifies a pattern, or surfaces a potential action, multiple stakeholders are involved: 

  • Technology teams manage implementation. 
  • Clinical teams use the outputs. 
  • Compliance teams evaluate risks. 
  • Leadership teams approve investments. 

 

Everyone has a role. What is often less clear is who owns the outcome. This ambiguity creates friction long before an AI system reaches production. Questions about governance, oversight, monitoring, and accountability begin to surface. Organizations slow down at this stage because they have not established clear ownership around how it will be used, leading to an accountability gap. 


Healthcare has spent decades building systems designed to support accountability. Electronic health records creating audit trails, medication orders requiring verification and clinical protocols, documenting decisions and approvals are all processes that happen every day. They exist because healthcare organizations recognize the importance of understanding who made a decision, when it was made, and how it was approved. 


AI introduces a new layer of complexity into these existing processes and governance. As AI adoption accelerates, accountability frameworks often lag behind. A systematic review published in npj Digital Medicine in 2026 examined 35 healthcare AI governance frameworks and reached a sobering conclusion: while guidance exists across seven critical domains, most frameworks remain fragmented and rarely assign clear human ownership to AI-assisted decisions. The American Hospital Association has drawn a parallel to financial services, recommending a three-layer accountability model spanning front-line operations, risk management, and internal audit. The architecture exists in theory.  Most organizations have simply not built anything like this. 

 

The Role of Compliance 


Compliance and risk teams are often viewed as the groups slowing AI adoption. In reality, they are frequently identifying questions that organizations need to answer before scaling AI responsibly.


Questions such as: 

  • Who approved this AI system for this use case? 
  • Who is responsible for monitoring performance over time? 
  • How are recommendations validated? 
  • What happens if outcomes do not align with expectations? 
  • These are not barriers to innovation. 


Organizations that dismiss these concerns as resistance often find themselves revisiting them later under far more difficult circumstances. Organizations that address them early create a stronger foundation for adoption, trust, and scalability, and accountability, and accountability needs to be designed into the deployment process from the beginning. 


Four Questions Every Healthcare AI Initiative Should Answer 


Before deploying AI at scale, healthcare organizations should be able to answer four fundamental questions. 

  1. Who approved the AI system for this specific use case? 
  2. Every AI implementation should have clearly defined executive, operational, or clinical ownership. Approval should be intentional and documented. 
  3. Who monitors performance over time? 
  4. AI governance cannot end at deployment. Organizations need designated owners responsible for monitoring performance, identifying drift, and evaluating outcomes. 
  5. Who owns the decision informed by AI? 
  6. AI may support decision-making, but accountability ultimately remains with people. Organizations should clearly define how human oversight is incorporated into AI-enabled workflows. 
  7. Who is accountable when outcomes fall short? 
  8. Every governance framework should establish escalation paths, review processes, and accountability structures before issues arise. 
  9. This checklist serves as a good reminder that these questions are not unique to AI. Financial services, aviation, and pharmaceutical organizations have spent decades building governance frameworks around accountability. Healthcare organizations can apply many of the same principles as AI adoption continues to expand. 


Start with Readiness 


Successful AI adoption requires the governance structures, accountability models, and operational foundations needed to support those tools at scale. At Kona Kai, we help healthcare organizations assess AI readiness across governance, accountability, data, security, and operating model maturity. Before investing in another AI initiative, understand whether your organization has the foundation necessary to support it. 


Take the Kona Kai AI Readiness Assessment  and identify the gaps that could prevent AI from delivering meaningful business value. 


INSIGHTS

By Carly Whitte • September 19, 2026
Dreamforce always offers a glimpse into where enterprise technology is heading. This year, the message is especially clear: AI is moving from experimentation into the systems, workflows, and decisions that power everyday business. Here are five developments the Kona Kai team is watching closely: 1. AI agents are taking on more meaningful work Agentforce continues to evolve beyond simple tasks. Salesforce’s newest agents are designed to pursue longer-term goals, learn new skills, collaborate with other agents, and handle more complex work across sales, service, commerce, and workforce operations. 2. Salesforce is building AI specifically for CRM reasoning One of the biggest announcements is Koa, Salesforce’s first CRM reasoning model, developed with NVIDIA. Koa is purpose-built to help agents reason through complex, multistep enterprise workflows using nearly three decades of Salesforce CRM intelligence. 3. AIforce is taking Salesforce beyond the traditional CRM interface Salesforce introduced AIforce , a new live interface layer that essentially makes Salesforce’s data, workflows, business logic, permissions, security, and governance available within the AI tools where people are already working. That means employees and AI agents can interact with Salesforce capabilities through experiences like Claude, Slack, and custom AI interfaces without always having to work directly inside the traditional Salesforce UI. AIforce is launching with Claudeforce, Slackforce, and Agentforce Coworker. For enterprises, that could fundamentally change how employees interact with CRM while making strong data architecture, permissions, and governance even more important. 4. Slack is becoming a true AI workspace Salesforce continues to position Slack as a place where people, agents, enterprise data, and workflows come together. Instead of AI existing as a separate tool, the goal is to bring intelligence and actions directly into the conversations where work is already happening. 5. Governance is becoming part of the AI infrastructure As agents become more autonomous and Salesforce capabilities become available across more interfaces, trust and governance have to evolve with them. It reinforces something we talk about often at Kona Kai: successful AI adoption depends on more than deploying the technology. Organizations need the right governance, people, data, and processes around it. Our biggest takeaway The conversation is shifting from “What can AI do?” to “How do we operationalize it responsibly across the enterprise?” The announcements coming out of Dreamforce show just how quickly the technology is evolving. For organizations, the opportunity now is to make sure their strategy, systems, data, and people are ready to evolve with it.
By Paul Benvenuto • August 19, 2026
AI is changing workforce training from a one-time project into a continuous business capability. For decades, enterprise technology transformations have followed a predictable pattern. A new system is implemented, then employees learn how to use it. Productivity dips for a while, then recovers as the organization adapts. Whether it was a CRM implementation, ERP modernization, a claims platform replacement, or a core banking upgrade, the skills gap eventually disappeared because the technology itself stopped changing. AI is different. Unlike traditional enterprise software, AI capabilities continue to evolve after implementation. New models are released, AI agents become more capable, and workflows change faster than most organizations can retrain employees. The result is a workforce that isn't simply learning a new system, but continuously adapting to one. That fundamentally changes how organizations should think about workforce readiness. Recent research from the World Economic Forum and Microsoft's Work Trend Index suggests many organizations already recognize the challenge. Are enterprises doing enough to prepare for a skills gap that may never close? AI Changes the Rules for Workforce Training Traditional enterprise software had a finish line. Once employees learned the new system, their knowledge remained valuable for years. Training programs could be planned, measured, completed, and archived because the technology itself remained relatively stable. AI doesn't offer that stability. Employees who learned effective prompting techniques six months ago may now be using AI agents. Teams that started with document generation may now be automating entire workflows. Capabilities continue to expand, changing what effective work looks like almost as quickly as organizations can document it. That means workforce readiness can no longer be viewed as a milestone that follows implementation, as it needs to become part of day-to-day operations. The AI Skills Gap Doesn't End After Go-Live The challenge isn't simply that AI is changing jobs. It's that AI itself keeps changing. Foundation models continue to improve. New copilots are released. AI agents take on increasingly sophisticated tasks. Features that didn't exist six months ago become standard workflow tomorrow. Employees aren’t learning one “system” because they need to continuously adapt to new capabilities. Someone who learned the most effective way to use AI six months ago may already be working differently today. Traditional training models weren't designed for that pace of change. AI Is Reshaping the Workforce Faster Than Organizations Can Respond The World Economic Forum's Future of Jobs Report 2025 highlights just how significant this challenge has become.
By Paul Benvenuto • July 31, 2026
PwC's April 2026 AI Performance Study surveyed 1,217 senior executives across 25 sectors and found something that should reframe how every regulated organization talks about AI investment: nearly three quarters of AI's economic value is being captured by just one fifth of organizations. Not because that top fifth has better models. PwC is specific about the differentiator: those organizations are 1.7 times more likely to have a Responsible AI framework and 1.5 times more likely to have a cross functional AI governance board. Their employees trust AI outputs at twice the rate of everyone else's. The value gap is structural, not a matter of who bought the better tool. That finding lands differently once you connect it to where trust actually comes from. It doesn't come from a more sophisticated model. It comes from knowing where your data originated, who touched it along the way, and what controls sat around it the entire time.  McKinsey's June 2026 research on AI data readiness makes the case that most organizations manage data like a storage problem when they should be managing it like a supply chain. A single PDF can expand into extracted text, tables, images, metadata, sensitivity tags, and quality scores, each one an intermediate artifact that AI systems reuse and recombine downstream. A small error introduced upstream doesn't stay small. It propagates. This matters more in regulated industries than almost anywhere else, because the data causing the most exposure is usually the data getting the least attention. Structured fields get governed. Clinical notes, claim narratives, loan officer comments, and audit trails, the unstructured stuff, usually don't, even though AI systems depend on it heavily. Gartner and IDC both put the share of enterprise data that is unstructured at somewhere around 80 to 90 percent. McKinsey's own research doesn't cite that specific figure, but makes the same underlying point: unstructured content is where AI systems draw the most context, and where governance attention is thinnest. None of this is an argument for waiting until your data is perfect before you deploy anything. PwC's 2026 Digital Trends in Operations Survey argues directly against that instinct: AI can help bridge data gaps, particularly through agents that reason using whatever data is actually available. The real mandate isn't clean data as a prerequisite. It's disciplined governance and iterative improvement running in parallel with deployment, calibrated to how much risk a given use case actually carries. So what does that look like in practice for a CIO or CDO sitting inside a regulated organization right now? A few diagnostic questions worth asking before your next AI initiative launches: Where does data quality actually break down in your pipeline, and does anyone own fixing it? Is lineage visible for the data feeding your highest risk AI use cases, or is it assumed? Where do unstructured assets, like clinical notes, policy documents, and loan files, enter your systems without any governance attached? Have you defined what "good enough" data quality means for each use case, calibrated to its actual risk profile, rather than applying one standard everywhere? Answering those honestly is uncomfortable in most organizations, because the answer is usually "we don't fully know." That's the point. You cannot govern what you cannot see, and you cannot trust an AI output built on a data foundation nobody has actually traced. The organizations in PwC's top 20 percent didn't get there by waiting for perfect data or by buying a better model. They got there by treating governance as a financial performance variable, not a compliance checkbox, and by building the lineage and controls that make trust possible at scale. Kona Kai's data supply chain assessment is built to answer exactly these questions before tool selection, not after. If you're not certain where your organization would land on that list, that uncertainty is worth resolving now. Get in touch to talk through what the assessment covers. Sources: PwC 2026 AI Performance Study, April 13, 2026 (74%/20% figure and 1.7x/1.5x/2x multipliers confirmed directly at pwc.com); McKinsey, AI Data Readiness: The Key to Scaling Impact, June 2026; Gartner and IDC estimates for the 80-90% unstructured data share; PwC 2026 Digital Trends in Operations Survey.
By Paul Benvenuto • July 29, 2026
Every governance and workflow framework most organizations are running today was built for AI that waits for a human to ask it something. Agentic AI doesn't wait. It initiates, executes, and chains actions across systems on its own, and the workflows built around human initiated, human reviewed steps simply don't have
By Paul Benvenuto • July 27, 2026
Education was the number one way companies say they adjusted their talent strategy in response to AI. And yet most organizations still treat training as an event. A workshop. A certificate. A box that gets checked once and never revisited.
By Paul Benvenuto • July 20, 2026
Most organizations think they have AI governance because someone in legal drafted a policy and got it signed off. They don't. A policy sitting in a shared drive doesn't know where your AI is actually running. It doesn't flag it when a model drifts. It doesn't do a single thing when an employee routes a client file thro
By Paul Benvenuto • July 20, 2026
Governance, people, data, and process are not sequential steps. They are four load-bearing walls, and in regulated industries, a crack in any one of them shows up as risk somewhere else. Here is where each pillar actually breaks down today, and what the data says about the gap between where most organizations sit and w
By Carly Whitte • July 1, 2026
AI success depends on more than technology. Governance, regulation, and operational oversight are helping organizations turn AI pilots into scalable business capabilities.
By Carly Whitte • May 24, 2026
AI-powered “vibe coding” is accelerating enterprise software creation, but governance and security controls are struggling to keep pace. Learn the hidden risks of AI-generated applications and why responsible AI governance is critical for scalable enterprise adoption.
By Carly Whitte • May 6, 2026
Why does AI adoption stall in healthcare? Discover how accountability, governance, and risk management influence success beyond change management.