footer-brand.svg

Privacy Policy

About Us

Contact Us

Notice

YourStory

Economic Times

Express Computers

CIOL

LinkedIn

Instagram

Facebook

Twitter

Industries

Healthcare

BFSI

Travel and Loyalty

E-commerce

EdTech

MarTech

Real Estate

Shipping and Logistics

Services

Web Development

Mobile Development

UX Design

Generative AI

DevOps Services

Quality Engineering

Data Science

Low-Code Platforms

Cybersecurity

Work

Careers

Insights

Blogs

Whitepapers

IIT2026 Recap: The Conversation Shift From AI Models to Enterprise Momentum

The Acceleration Continues: Reflecting on the Key Themes of HIMSS 2026 and How Our Focus Areas Provide a Path Forward

Why Governance is Critical for Healthcare AI To Succeed

Revolutionizing Prior Authorization with GenAI: A Blueprint for Faster, More Efficient Care Outcomes

AI's Big Leap in Healthcare in 2026

From Full-Stack to AI-Stack: The New Developer Badge

2025: The Year Context Took the Lead in AI Engineering

A Step-by-Step Guide to Automating CloudFormation Deployments Using GitHub

Never Lose Uptime Again: Building a Self-Healing AWS Infrastructure with Terraform

Building an EKS Cluster with Terraform: A Modern, Modular Approach

How to Automate Static Website Deployment with GitHub Actions and AWS S3

How to Scale Kubernetes Governance with Kyverno and Slack

AI Won't Replace You, Unless You Let It.	

Your REST API Isn’t Agent-Ready—Here’s How MCP Transforms It

Vibe Coding vs AI-Assisted Development: Why Human Theory Still Matters 

GPT‑5: When the Hype of a "Pair Programmer" Falls Flat 

Is Poor UX the Silent Killer of GenAI Adoption?

 Understanding the AI Maturity Curve and Why Most AI Ambitions Collapse Before They Scale

What’s Breaking Agentic AI and How MCP Solves It

07 Rules Of Design: Why Expert Swear By Them?

The Protocol That Could Fix Agentic AI’s Biggest Flaw

The Missing Link in Enterprise AI? It’s Probably MCP

How a Leading Edtech Platform Replaced Manual Support With Real-Time Systems

Scaling Client Experience with AI and Real-Time Visibility in Outreach-Driven Enterprises

The Next Frontier in Healthcare: AI-Powered Connected Ecosystems

2025 Tech Trends Overload: How AI, Crypto, and Big Shifts Will Change Everything

Banking on the Cloud for Agility, Security, and Innovation

Modernize or Fall Behind – 9 Essential Strategies for Future-Proofing Your Apps

What Can Transaction Data Teach You About Your Customers’ Behavior? 

The Architect’s Blueprint to Crafting Software That Lasts

Provisioning a Python Function App with Terraform: Avoiding Common Pitfalls

Set Up Pritunl Server Monitoring Using Filebeat, Elasticsearch, and Kibana

Streamlining Security and Efficiency with FreeIPA: A Comprehensive Guide

A Hands-on Guide to Kubernetes Setup Using Kubespray

Streamline Your ECS Deployments with Jenkins Shared Libraries

Navigating the Oncology Frontier: Genomics, Challenges, and the GenAI Paradigm

Synchronous and Asynchronous Communication in Microservices

Coditas at HIMSS 2024: A 5-Day Expedition of Innovation, Connection, and Transformation in Healthcare

The Role of Generative AI in Facilitating Prior Authorization Decisions

Agile in Healthcare?

The 80/20 Rule of Health: Decoding the SDOH Advantage

Unveiling the Potential of Generative AI in Administrative Healthcare Tasks

The Importance of Patient Consent Management Systems

Healthcare and GenAI Trends to Look For in 2024: A Glimpse into the Future of Wellness

Learning from Angel One: The Guardian Angel of Investments

How Fintech is Booming in Latin America: A Look at the Future of Financial Services

Visual Storytelling in UX Design

Is Multitasking Bad for productivity?

No Work Diwali: An Idea That Became a Movement

KPIs That Determine the Success of a Product

In Conversation with Devyani Jaiswar

08 MISTAKES TO AVOID WHEN YOU ARE LEARNING TO CODE

Artificial Intelligence for Rural India

In Conversation with Praveen Pundhir

Caching in Spring with Caffeine

Engineering Culture: A reliable backbone for Tech Organizations

5 Ways in which Programmers have changed the World

In Conversation with Sumedh Puntambekar

DevOps: A Culture beyond Departments

In Conversation with Yuvraj Pashankar

Artificial Intelligence and the Post-COVID-19 World

In Conversation with Khushboo Dengra

Becoming a Full-Stack Developer in 2020

In Conversation with Arnav Mediratta

All Things Design Part III: Become a Ninja

In Conversation with Sneha Suryawanshi

All Things Design Part II: Beyond Basics

In Conversation with Pratik Naik

All Things Design Part I: The Beginner's Guide

In Conversation with Sampada Deshmukh

Our Human Resource Team: A Story of Remote Working

In Conversation with Abhishek Sharma

Must-know Tips to Become an Efficient UI and UX Designer

10 Ways for Coders to Up-skill in 2020

The Ups & Downs of Remote Working: And How to Overcome the Odds

Becoming a Coder: Do You Need a Degree?

Mastering High Availability on AWS with Terraform: A Comprehensive Guide

Building a Bulletproof Photo-Sharing App: Security and Reliability with DevSecOps

Building a Cost-Optimized Jenkins with AWS Spot Instances

# AI Meets Enterprise Reality
IIT2026 brought together the global alumni network in Long Beach for three days of conversations across technology, entrepreneurship, investment, sustainability, health, and global collaboration. The conference celebrated 75 years of IIT excellence and brought together more than 1500 leaders, founders, operators, investors, technologists, and changemakers from across industries.
The event had the energy of a room where AI no longer needed a grand introduction. Everyone had seen enough pilots, tools, demos, and boardroom pressure to know the conversation had moved forward.

## What stood out was the kind of concern underneath the excitement.

Healthcare leaders were not responding to AI as a shiny interface. They were looking at care workflows where trust, documentation, data movement, and accountability decide whether technology can hold up. Enterprise leaders were weighing custom agents against a crowded market of vertical tools. Technology teams were thinking about older systems where years of product logic sit buried in code, tickets, documents, and memory. Different entry points. Same undertone.

Enterprises are no longer asking whether AI belongs in the business. They are asking what it will take to make AI work without losing control over the systems, knowledge, and decisions that keep the business running.

It all kept circling the same concern: **while AI is easy to buy, momentum is hard to build.**

## Healthcare As the First Stress Test
Healthcare has a way of cutting through loose AI language.

A prior authorization workflow is not the same as a generic productivity demo. It sits inside a chain of documentation, payer rules, patient access, compliance, cost, and clinical context. Value-based care brings another layer of complexity: outcomes, coordination, reimbursement, data quality, and trust.

Here, AI cannot simply sound impressive. It has to hold up.

People wanted to know how the demos were built, how the platform thinking came together, and how collaboration worked across stakeholders. The questions were more about the machinery underneath the experience:

_Who owns the data? Where does the intelligence sit? How much of the workflow stays inside the enterprise? What happens when a vendor’s agent becomes the place where your operating knowledge accumulates?_

**Because in healthcare, the risk is visible.**

The market is filling up with vertical AI agents. Some focus on billing. Some on claims. Some on documentation. Some on support. Many will solve narrow problems well. The problem starts when the enterprise slowly loses control of the intelligence layer.

A rented AI tool can make one workflow faster. It can also become the place where data, workflow logic, exceptions, and institutional learning move outside the business. Over time, the company may own the problem while someone else owns the operating memory.

One of the stronger conversations Coditas had at the event:** Enterprise AI is not only a capability question. It is an ownership question.**

## The AI Journey Needs a Sequence
Over the last two years, many AI programs have started with spending.

A board asks for AI movement. A CXO approves tools. Teams get access to copilots, cloud AI services, chatbot builders, or coding assistants. Everyone expects productivity to show up because the organization has finally paid for intelligence. That’s rarely how enterprise change works.

[McKinsey’s 2025 State of AI survey](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai/?utm_source=chatgpt.com) found that most organizations are still in experimentation or pilot mode. Nearly two-thirds had not started scaling AI across the enterprise, and only 39% reported enterprise-level EBIT impact from AI. At the same time, 62% were already experimenting with AI agents.

[Deloitte’s 2026 enterprise AI research](https://www.deloitte.com/cz-sk/en/services/consulting/research/the-state-of-ai-in-the-enterprise.html?utm_source=chatgpt.com) shows the same tension from another angle. Workforce access to AI grew by 50% in one year, from fewer than 40% to around 60% of workers with sanctioned AI tools. Still, fewer than 60% of workers with access use those tools in their daily workflow.

**Access is rising faster than adoption. Adoption is rising faster than measurable value.**

The conversations at IIT2026 reflected the gap. Leaders were no longer satisfied with “we have AI tools” as proof of progress. The better question was: _which process deserves AI in the first place?_ That’s where the sequence becomes important.

**First, digitize the process**. If work is still happening through calls, spreadsheets, emails, and undocumented manual checks, the business has no reliable data trail. AI cannot learn much from work that leaves no usable trace.

**Then connect the systems.** Sales, finance, engineering, service, compliance, and operations often hold different pieces of the same truth. If those systems do not talk to each other, AI receives information in fragments. Fragments create weak automation.

**Next, add intelligence.**

AI performs best when the enterprise has already done some of the less glamorous work. Clean up the workflow. Capture the data. Connect the context. Give teams a reason to trust what the system sees. This may not sound like the shiny part of AI, but it is usually the part that decides whether AI survives beyond the first demo.

## The Stack Beneath the Agent
A useful agent is rarely the beginning of the journey. It is usually the visible end of several decisions made earlier.

Coditas’ conversations at IIT2026 often came back to a five-layer view of enterprise AI. The words can sound simple: strategy, people, data, intelligence, platform. The work underneath each layer is anything but simple.

**The strategy layer is where the business has to slow down before it speeds up.**
_Which workflows should change? Which processes need digitization? Where is data disconnected? Which use cases have a real path to ROI?_

**The people layer is where adoption becomes honest.**  Teams do not change because a new tool appears. They change when the work around them changes, when incentives make sense, when they understand what AI will and will not do, and when leaders explain the new operating rhythm clearly.

**The data layer is where the system earns trust.** Poor data does more than produce poor answers. It makes users cautious. It makes governance harder. It makes automation risky.

**The intelligence layer gives business meaning to the data.** This is where semantics, context, rules, relationships, and domain logic start to matter. Raw information becomes more useful when the system understands how things relate.

**The platform layer is where repeatability enters**. One agent can be built as a project. Ten agents need a platform that can support observability, maintenance, reuse, controls, and future change.

Enterprises should not have to reinvent the wheel every time a new AI use case appears. Once the lower layers are healthier, the next agent should become easier to build, govern, and improve.

THAT is what momentum looks like in practice.

## Modernization is Essentially a Knowledge Reconstruction

Modernization came up in a different way at IIT2026.

Some people were less interested in AI agents as a standalone story. They were looking at older systems and asking **what happens when the software beneath the business is too old, too undocumented, or too difficult to change.**

This is where modernization becomes more interesting than technical debt reduction.

A legacy system is rarely just old code. It holds product memory. It holds workflows. It holds exceptions added for one customer years ago. It holds business rules that nobody fully remembers. It holds decisions made by developers who may have left the company a decade ago.

A traditional migration often moves a function from one technology to another. COBOL to Java. Old Java to new Java. .NET to a newer stack. May be necessary, but not always enough. The deeper opportunity is to recover what the system actually does before rebuilding it.

It means reconstructing the real specification of the product, asking what should remain, what should be simplified, and what should quietly disappear because its reason for existence no longer applies.

If a system has accumulated 100 features over 10 years, the question is not how to move all 100 into a modern stack, but if we were building this product today, knowing what we know now, what would we build?

AI can help recover trapped knowledge from legacy systems. Engineering teams can validate the recovered intent. Product teams can refine it. Business stakeholders can spot redundant workflows. Human review keeps judgment in the room. Hence, modernization starts becoming AI-ready. A company does not get a cleaner version of the same old system. It gets a chance to rebuild with context.

For enterprises looking at AI, this matters more than it may seem. Agents struggle when the systems around them are opaque. Modernization gives AI better surfaces to work with, better context to read, and cleaner paths to action.


## ROI is Becoming the Only Serious AI Language

The investment track at IIT2026 focused on capital, company building, valuation, fundraising, and scale. The theme fits the broader market well. [OECD data](https://www.oecd.org/en/about/news/announcements/2026/02/ai-firms-capture-61-percent-of-global-venture-capital-in-2025.html?utm_source=chatgpt.com) published in February 2026 found that AI firms captured 61% of global VC investment in 2025, or USD 258.7 billion out of USD 427.1 billion. AI infrastructure and hosting attracted USD 109.3 billion in 2025 alone.

Money is not the scarce part anymore. Judgment, definitely.

Every board wants to see AI movement. Every leadership team wants to avoid falling behind. Every function can find a reason to ask for tools. The harder discipline is deciding which AI bets deserve funding because they have a credible path to return.

[BCG’s 2026 research](https://www.bcg.com/publications/2026/how-ai-is-paying-off-in-the-tech-function?utm_source=chatgpt.com) found that only 5% of companies generate measurable AI value at scale, while 60% are not achieving material value. Yet within the technology function, the value of AI is rising. The share of companies scaling or fully deploying AI in one or more top tech use cases tripled from 9% in 2024 to 28% in 2025.

The use cases are telling: Software development. Data management. Compliance monitoring. IT project management. Service desk automation. Legacy modernization.

That’s often where ROI begins. A release cycle shortens. A report stops taking three days. Support teams find the right answer faster. A compliance check becomes easier to trace. A modernization team understands old code before rewriting it. A workflow drops steps that nobody needed anymore.

The first valuable AI use case may not be the one that looks best in a demo, but can remove friction from work the business already knows is slowing it down.

A demo earns attention. ROI earns permission to scale.

## Governance Belongs in the Build

Governance tends to enter AI conversations late, usually after enthusiasm has already done its damage. But it won’t work for long.

Once AI starts retrieving information, supporting decisions, calling tools, or moving work forward, governance becomes part of the build. It belongs in access design, logging, monitoring, escalation, model evaluation, data handling, and release practices.

[NIST’s AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) was created to help organizations manage AI risks and incorporate trustworthiness into the design, development, use, and evaluation of AI systems.

If an AI system in an enterprise touches a workflow that carries cost, customer impact, regulatory exposure, or operational risk, the business needs to know what happened, why it happened, and who can intervene. That requires audit trails, access rules, human review, monitoring, clear escalation paths, incident response, and most importantly, ownership. 

None of these is glamorous. All of them matter. Good governance does not slow AI down. It keeps AI from breaking trust faster than the business can repair it.

## Why the Room Still Matters
There is a reason a conference like IIT2026 matters even when most information is available online.

**A room changes the question.**

A business leader describes a workflow problem. An engineer hears an integration issue. A healthcare leader sees risk. An investor asks whether the motion can repeat. A modernization expert hears trapped knowledge inside legacy systems.

The same problem becomes clearer when different people turn it around from different sides — the value of IIT2026’s cross-industry setting. It brought together people who were not all solving the same problem, yet many were dealing with the same underlying constraints: **data, adoption, cost, ownership, trust, and scale.**

AI execution does not move through tools alone. It moves through conversations that sharpen judgment. It moves when the right problem meets someone who has seen a version of it before.


## What Leaders Should Carry Forward

The next “AI-driven” conversation should begin before the tool is chosen.

1. **Start with the business friction.** Where is the organization losing time, money, quality, trust, or revenue? It could be claims, reporting, engineering, customer support, sales operations, compliance, onboarding, approvals, documentation, or modernization.

2. **Revisit the workflow.** If a process has 10 steps, do all 10 still deserve to exist? AI should not speed up a bad workflow before someone asks why the workflow looks that way.

3. **Check whether the process is digitized.** Manual work leaves weak evidence behind. Without a reliable data trail, AI has little to learn from.

4. **Look at connection.** Does the process need context from finance, sales, engineering, operations, service, or compliance? If those systems remain separate, AI will keep seeing pieces rather than the whole.

5. **Examine the data and knowledge layer.** Which data can be trusted? Which rules are documented? Which decisions live only in someone’s memory? Which product behaviors are trapped in code, tickets, and old spreadsheets?

6. **Look at modernization.** Which systems can support AI as they are? Which should be wrapped, rebuilt, simplified, or retired? Which parts of the old system carry logic the business cannot afford to lose?

7. **Define governance.** What needs approval? What needs an audit trail? What needs human review? What should never be automated? Who owns the outcome when AI acts?

8. **Plan adoption.** How does work change for the people using the system? What will make them trust it? What will make them avoid it? What needs to change in roles, handoffs, reviews, and incentives?

9. **Measure ROI in business terms.** Speed. Cost. Quality. Risk. Revenue capture. Throughput. Margin. User satisfaction. A serious AI program should know what it expects to prove after 30, 60, and 90 days.

## From Attention to Momentum

Answering the right questions will help create better AI decisions. Why? **Because they compel the enterprise to look beneath the surface.**

The entire outlook is grounded in execution at Coditas. Enterprise AI creates value when strategy, data, knowledge, platform engineering, modernization, governance, and adoption move together. Progress slows when those decisions happen in isolation.

The conversation at IIT2026 was full of energy, but energy alone does not create movement.

Momentum comes from clearer choices. Stronger foundations. Better systems. Measurable value. People who know how to make technology hold up under real operating conditions.

AI already has the spotlight. Momentum will belong to enterprises that can make it work when the lights are off.

**Ready to move from AI attention to AI momentum?**

Coditas helps enterprises build AI strategies, data foundations, knowledge systems, modern platforms, and adoption models that can stand up to real operating conditions.

Let’s build what works beyond the pilot room. [Talk to us.](https://coditas.com/contact-us)


Desktop_Blog Main Card Banner.jpg

HIMSS 2026 felt like a market applying pressure on execution.

And it was visible across the event floor, in keynote sessions, and in the conversations healthcare leaders were willing to spend time on. The industry has moved into a more demanding phase of digital adoption. AI is now expected to work inside live environments. Platforms are expected to support measurable outcomes. Governance is expected to be part of the product. Usability is expected from the start. Buyers are asking sharper questions because the stakes are higher and the tolerance for vague value stories is lower.

This shift matters.

Healthcare has spent the last few years exploring the possibilities of AI, automation, cloud modernization, patient engagement, connected devices, and data interoperability. HIMSS 2026 showed what comes next. The market wants technologies that can carry weight inside real workflows. It wants systems that can reduce friction, support decisions, recover time, strengthen control, and hold up in regulated operating environments.

That is where the conversation has become more useful.

At HIMSS 2026, scale and seriousness came together. Around 24,000 attendees from 75 countries gathered in Las Vegas, and nearly one-third of them were C-suite leaders. That level of executive presence changes the tone of an event. The interest is still there. The curiosity is still there. The main difference is that buyers now want a clearer answer to one question: how does this move the organization forward in a way that is measurable, governable, and durable?
## Healthcare Has Entered an Accountability Era
The strongest signal from HIMSS 2026 was not excitement. It was accountability.

Healthcare organizations are under pressure from every direction. Costs remain high. Staffing remains tight. Administrative burden continues to drain time and focus. Data environments are still uneven. Patient expectations keep rising. Security concerns are growing. In such settings, technology needs to do more than impress. It needs to perform. This expectation shaped the way major announcements landed at the event.

The examples that drew attention were tied to workflow and outcome. Epic pointed to gains in prior authorization efficiency. Oracle highlighted a lower documentation burden. Abridge surfaced workload and satisfaction improvements. Amazon Health AI shared a reduction in call abandonment. These stories landed because they connected technology to operational value in terms healthcare organizations already understand.

That is where the market is now. Buyers are looking for practical movement across clinical, financial, and operational systems. They want technologies that fit the structure of healthcare work and make that work easier to execute with consistency.

It's a healthy shift for the industry. It raises the standard for builders and creates stronger conditions for adoption. Healthcare benefits when the market rewards systems that can prove relevance under pressure.

## AI Will Earn Its Place Inside Workflows
Agentic AI was the loudest theme at HIMSS 2026, though the more important point is where that conversation is heading.

The market is moving toward AI that can take part in the workflow itself. Epic’s Agent Factory, Microsoft’s expansion of Dragon Copilot, and the broader push from Google Cloud, Salesforce, Oracle, and Amazon all pointed in the same direction. AI is moving closer to action, to decision support, and of course, operational participation.

This movement not only brings real opportunity but also a stricter set of requirements in healthcare.

A healthcare workflow is a chain of dependencies. It involves timing, documentation, compliance, handoffs, escalation points, patient communication, and financial consequences. Intelligence in that environment needs to behave with discipline. It needs to surface the right information at the right time. It needs to support action without creating ambiguity. Most importantly, it needs to help teams move through complexity with greater speed and clarity.

This is why the next phase of healthcare AI will be won inside workflows.

Prior authorization, denial management, clinical risk review, intake orchestration, connected device operations, and remote monitoring are all strong examples. These are environments where work slows down because information is incomplete, coordination is fragmented, or teams are forced to repeat the same cognitive effort across cases. Well-designed intelligence can create meaningful lift here because the friction is already visible and the operational need is already established.

For Coditas, this is one of the clearest paths forward. Our focus areas sit inside the kinds of healthcare workflows where intelligence has a real chance to prove value. Revenue cycle teams need stronger orchestration and decision support. Connected care environments need continuity and visibility. Clinical intelligence needs to produce outputs that teams can understand and act on with confidence.

The opportunity here is straightforward. Apply intelligence where healthcare systems feel pressure every day and where the return on improvement is easy to recognize.

## Governance Is Now Product Infrastructure

HIMSS 2026 also made something else very clear. Governance has moved from the margins of the conversation into the center of product evaluation.

Healthcare organizations are advancing with AI, though governance maturity remains uneven across the market. The gap between deployment speed and governance readiness came through clearly in the conference insights. Concerns around validation, monitoring, auditability, passive listening environments, and patient trust are growing. These concerns deserve serious attention because AI in healthcare operates inside sensitive, regulated, and deeply human settings.

Trust will shape adoption from here on.

As AI becomes part of everyday healthcare operations, organizations need to understand how outputs are grounded, how decisions are logged, how exceptions are handled, where human review fits, and what evidence is preserved throughout the workflow. These details directly influence whether a system feels deployable at scale.

Cybersecurity sits inside the same reality. HIMSS 2026 featured 49 dedicated cybersecurity sessions, and the focus on medical device security, access control, identity, and attack surface management reflected the urgency of the moment. Connected care environments are growing. Medical device fleets are growing. Remote monitoring programs are growing. Each of those shifts expands the importance of secure architecture and disciplined access governance.

This dramatically changes how healthcare technology has to be built.

Governance-first design, role-based access, evidence tracking, secure data movement, explainable outputs, and audit readiness are now part of the product story. They shape trust. They reduce uncertainty. They give enterprise buyers stronger reasons to move forward with confidence.

This is a critical path forward for Coditas. In healthcare, strong architecture is now inseparable from strong product thinking.

## Revenue Cycle Remains the Clearest Proving Ground

Financial pressure continues to shape buying behavior across healthcare, and HIMSS 2026 reflected that reality clearly.

Healthcare organizations are still carrying the weight of reimbursement complexity, denials, administrative waste, staffing constraints, and the constant need to do more with limited capacity. That is one reason revenue cycle conversations continue to draw serious attention. They speak directly to cost, cash flow, visibility, and organizational control.

Hence, revenue-focused workflows remain such an important proving ground for healthcare AI.

Prior authorization, claims, denials, appeals, and documentation integrity are high-pressure environments with immediate business consequences. These workflows involve repetitive analysis, policy interpretation, evidence review, coordination across teams, and time-sensitive execution. They are exactly the kind of environments where intelligence can create visible operational return.

The market is looking for systems that support the full sequence of work with greater continuity. It wants stronger visibility into why denials occur, where cases are getting delayed, what information is missing, and how response quality can improve. Buyers are increasingly drawn to platforms that create connected workflow control rather than isolated workflow support.

For Coditas, this remains a strong strategic alignment. Revenue cycle intelligence matters because it addresses pain that buyers are already prioritizing. It also offers a clearer path to measurable value, which is exactly what this market wants right now.

## Experience Quality Now Shapes Enterprise Healthcare Value

One of the most important lessons from HIMSS 2026 had everything to do with experience.

The popularity of the “Kill the Clipboard” message captured a real frustration inside healthcare. Patients are tired of repetition. Clinicians are tired of friction. Operational teams are tired of systems that create work instead of reducing it. The strongest demos at the event succeeded because they made the next step feel simpler, clearer, and easier to complete. Samsung and b.well’s QR-based record population stood out for that reason. The value was immediate. The interaction felt intuitive.

Consider it a strategic signal for the industry.

Experience quality now affects access, engagement, completion, communication, confidence, and trust. It influences whether a user can move through the workflow smoothly and whether the technology becomes part of everyday behavior. In healthcare, that applies to patients, clinicians, operators, device teams, and revenue cycle users alike.

The experience layer now carries strategic weight.

A system may be technically capable, though real value only shows up when the user can understand it, move through it, and trust what happens next.

That is an important part of the path forward for Coditas. Stronger alignment between engineering, AI, and experience design will decide how much value healthcare organizations actually capture from the systems they invest in.

## The Way Ahead for Coditas

The deeper lesson from HIMSS 2026 is that healthcare is accelerating in a very specific direction.

The market is moving toward more active intelligence inside workflows. It is expecting stronger governance and security foundations. It is prioritizing measurable operational impact. It is demanding digital experiences that reduce friction across patients, clinicians, and enterprise users.

This gives us a very clear direction.

Coditas will continue to build where these forces intersect. Revenue cycle intelligence remains highly relevant because financial pressure still shapes technology priorities. Clinical and predictive intelligence matter in areas where trust, reproducibility, and actionability influence outcomes. Connected device ecosystems matter because distributed care and medical device operations continue to grow in scale and complexity. Experience-led healthcare products matter because usability still determines whether value is realized in the field.

We need to keep building systems that bring intelligence closer to action. We need to build regulated environments with secure and explainable foundations. We need to reduce fragmentation across healthcare workflows. We need to create digital experiences that support confidence, speed, and adoption.

## Closing Thoughts

HIMSS 2026 gave the industry a clearer signal than most conferences do.

Healthcare technology is moving into a more exacting phase. Buyers want value they can defend. They want workflows that move faster with stronger control. They want systems that can be governed responsibly. They want digital experiences that feel usable under pressure. They want partners that understand how healthcare actually operates.

The acceleration continues, and it is creating a real opportunity for teams that build with focus and discipline.

Desktop Blog Banner.jpg

<h2>The biggest risk as AI enters care delivery</h2>
<p>AI in healthcare has moved beyond pilot projects; it's now being implemented at scale. AI is now integrated into clinical workflows, operational decision-making, and patient access points, but with significant consequences. Commonly cited risks include bias, privacy concerns, and hallucinations.</p>
<p>While these are significant, a more fundamental risk exists: deploying AI into production environments without governance robust enough to withstand clinical scrutiny, regulatory review, and public accountability.</p>

<h2>My perspective</h2>
<p>I am Bhupesh Nadkarni. I have spent 25 years architecting solutions for healthcare tech.</p>
<p>Currently, I collaborate with healthcare leaders facing pressure to modernize, especially with AI. They require speed, precision, and systems that perform reliably in real-world settings. I also lead a team of 800 AI-enabled engineers who design and implement these systems at scale.</p>
<p>And in my experience, I have found that in healthcare, the milestone is not merely a model generating an answer. It is the organization's ability to defend that decision and make it auditable.</p>

<h2>Trust is the production requirement</h2>
<p>Healthcare is sustained by trust rather than novelty.</p>
<p>Clinicians place trust in systems they can validate, patients in those they can understand, and regulators in those that are traceable, auditable, and accountable. If AI-integrated systems do not meet these standards, they should not be deployed in production, regardless of their performance in demonstrations.</p>
<p>To be credible, AI must be built on three principles:</p>
<p>Transparency, explainability, and responsibility.</p>
<p>These are not aspirational values. They are essential conditions for safe deployment and sustaining the scaling needs of the industry.</p>

<h2>Pilots are controlled. Production is accountable.</h2>
<p>Pilot environments allow for greater flexibility, whereas production environments do not.</p>
<p>During pilot phases, oversight is intensive, volumes are limited, edge cases are managed manually, and risks are contained.</p>
<p>In production, AI becomes part of how care is delivered and how decisions are made. It can influence documentation quality, coding integrity, utilization decisions, and patient access. It also creates records that can be reviewed months later under audit pressure.</p>
<p>Consequently, the central question shifts. The question is no longer whether the model can generate an answer. Instead, it is whether the outcome can be justified to clinicians, patients, and auditors.</p>
<p>If this question cannot be answered with clarity, the system is not ready for production deployment.</p>

<h2>Governance is the gap that creates real risk</h2>
<p>When AI capabilities advance more rapidly than governance structures, predictable failure patterns emerge.</p>
<p><strong>Accountability becomes unclear.</strong> When an AI recommendation influences a decision, ownership must be explicit. In healthcare, blurred accountability quickly becomes unacceptable.</p>
<p><strong>Exceptions become commonplace</strong> as production workloads regularly reveal edge cases. Without clear escalation procedures and defined decision rights, teams may either over-rely on the tool or abandon it entirely. Both scenarios compromise safety and hinder adoption.</p>
<p><strong>Auditability is compromised</strong> when healthcare systems lack traceability. If an AI output cannot be linked to its inputs, underlying guideline logic, and supporting evidence, it becomes indefensible. At this stage, the system ceases to provide decision support and instead introduces operational risk.</p>
<p>Governance is essential because it safeguards care delivery while enabling innovation to scale.</p>

<h2>Being transparent, explainable, and responsible is how AI earns clinical confidence</h2>
<p><strong>Transparency</strong> requires that a system's behavior is visible, including the Patient Health Information (PHI) utilized, inaccessible data, underlying assumptions, and existing uncertainties.</p>
<p><strong>Explainability</strong> ensures that the rationale is immediately clear to clinicians. The system should reference the relevant clinical context, applicable guidelines, and factors influencing its recommendation, and indicate what could alter the output.</p>
<p><strong>Responsibility</strong> requires the health system to operate within established boundaries, respect defined roles and approvals, support overrides and escalation, and be monitored in production based on real-world outcomes rather than solely on model metrics.</p>
<p>If these conditions are unmet, confidence will erode in clinical, operational, and audit contexts.</p>

<h2>The non-negotiable questions production AI must answer</h2>
<p>Before AI can be considered production-ready, governance must address several unavoidable questions.</p>
<ul>
  <li>Does this recommendation tie back to the care guidelines clinicians follow?</li>
  <li>Can the rationale be explained to a clinician in plain language?</li>
  <li>Can it be explained to a patient without causing confusion?</li>
  <li>Can it be defended in an audit with evidence and traceability?</li>
  <li>Who owns the decision when AI is involved?</li>
  <li>What happens when the system is wrong?</li>
  <li>What happens when inputs are incomplete, outdated, or conflicting?</li>
</ul>
<p>If these answers lack clarity, scaling AI will increase risk rather than mitigate it.</p>

<h2>What strong governance looks like in practice</h2>
<p>Strong governance lives in real workflows. Policies only matter when they are enforced.</p>
<ul>
  <li>Clear ownership for each AI-enabled workflow across clinical, operational, and technical responsibilities.</li>
  <li>Defined decision boundaries so it is clear where AI can recommend, where it can act, and where it requires approval.</li>
  <li>Case-level traceability, including sources, guideline references, and context used.</li>
  <li>Readable audit logs that compliance teams can review without translating engineering artifacts.</li>
  <li>Continuous monitoring tied to operational and clinical outcomes, with thresholds that trigger review and correction.</li>
</ul>
<p>This approach enables healthcare organizations to scale AI while maintaining control.</p>

<h2>The future belongs to systems that can be defended</h2>
<p>The future of AI in healthcare will be defined by systems that consistently deliver safer care and more efficient operations under real-world conditions, not by impressive pilots.</p>
<p>When governance is robust and guiding principles are explicit, AI transitions from being perceived as a risk to becoming a dependable asset.</p>
<p>That is how we move from hype to impact.</p>
<p>That is also how we earn lasting confidence from the people delivering care every day.</p>

Desktop CS Banner (2).jpg

large_blogs.webp

medium_blogs.webp

small_blogs.webp

thumbnail_blogs.webp

blogs.webp

Our take on AI, UX, Digital Engineering, and the future of business innovation.

Our take on Digital Engineering, Generative AI, UX, Business Strategies, & Innovations that shape the future of industries, including Healthcare, BFSI, & more.

What We're Writing