Season 7
Episode 218 - Podcast with Umesh Rustogi, General Manager, HLS Dragon & Platform, Microsoft
Using Multimodal Foundations and Ambient AI to Scale Clinical Impact
In this episode, Umesh Rustogi, General Manager, Healthcare & Life Sciences Dragon & Platform at Microsoft, explains that meaningful AI outcomes depend on combining unified multimodal data foundations with clinician-centered design to achieve healthcare’s quadruple aim: improving care quality, patient experience, operational efficiency, and workforce well-being.
Addressing the severe nursing shortage and turnover driven by administrative burnout, Umesh details how Microsoft co-innovated with nine major health systems to deploy Dragon Copilot for Nursing, a clinical assistant that works alongside nurses. By leveraging ambient AI on mobile devices, the solution helps nurses capture flow sheet documentation for their review and maintains a running cognitive memory across shifts, significantly lowering cognitive load and enabling nurses to be truly present with their patients.
Umesh also emphasizes that enterprise-scale success requires far more than model selection. It demands responsible AI governance, transparent audit capabilities, deep workflow customization, and robust change management, including nurse leader sponsorship and dedicated unit champions. He envisions smart hospital rooms, multimodal AI, wearable integration, and agentic workflows transforming clinical operations by delegating non-patient-facing tasks so caregivers can focus on delivering better care. Take a listen.
This guest appearance was facilitated through conversations initiated at HIMSS.
About Our Guest

Umesh Rustogi is General Manager of Microsoft's Healthcare & Life Sciences Dragon & Platform. Umesh leads product and engineering teams for Microsoft Dragon Copilot ambient nursing capabilities. With over 20 years in enterprise software—including roles at Microsoft, SAP, i2, and IBM—he brings deep expertise in engineering, architecture, and product strategy.
Recent Episodes
Ritu: Hello, listeners. Welcome to Season Seven of the Big Unlock Podcast. My name is Ritu Oberoi, and I’m managing partner at Damo Consulting and your host today. We are very excited to welcome Umesh to our podcast. Umesh Rastogi serves as General Manager in Microsoft’s Healthcare and Life Sciences Dragon and Platform Group. In this role, he leads product and engineering teams developing innovative AI solutions for nurses, as well as broader data platform capabilities for the healthcare industry. Umesh is deeply passionate about building technology-driven innovation to help the healthcare industry achieve its quadruple aim, and he has held pivotal roles in engineering, technology, architecture, and product management. Welcome, Umesh, to our podcast. Really happy to have you here.
Umesh: Glad to be here, Ritu.
Ritu: Would you like to add anything to that introduction?
Umesh: My journey has been more than two decades in enterprise software. I’ve held a variety of different roles and worked across both the applications domain and platform. My foray into healthcare was about ten years ago, actually when I was helping my daughter with her biology coursework — that’s when I thought about how I could use technology to have an impact on healthcare. Over the years I’ve had the opportunity to build hospital emergency response solutions, and when COVID hit, various other healthcare capabilities along the way. And as you mentioned, I’m now leading our product and engineering teams building the Dragon Copilot solution for nurses, and I’m very passionate about the work we’re doing there.
Ritu: Thank you for sharing that story. We always love origin stories, and we find out the most interesting things about people. Let’s get started. Healthcare leaders often talk about AI as if the primary challenge is just selecting the right model or the right LLM. But much of your recent work has focused on building unified multimodal healthcare data foundations. Are we at risk of overestimating the AI problem and underestimating the data problem? What does AI-ready really mean in a healthcare organization?
Umesh: That’s an excellent question. If you take a step back and ask what outcomes these organizations are typically trying to achieve, it fits within the quadruple aim: improve healthcare outcomes, improve patient experiences, reduce cost, and improve the well-being of clinicians — physicians, nurses, and so on. Whatever technology we pick has to address one or more of those aims. Many organizations end up making it purely an LLM or core model problem, but that’s just a piece of the puzzle. The whole technology stack actually starts from making sure you have access to the right data — the data on which you’re applying AI models and agents and enabling workflows for physicians, nurses, radiologists, and others.
Ritu: Tell us more about how Microsoft is partnering with health systems to responsibly scale AI-enabled clinical solutions specifically for nursing workflows.
Umesh: If you look at what’s happening in the nursing workforce, recent data points to a shortage of about 80,000 nurses as of last year, and that gap is expected to increase to about half a million by 2030. What’s driving that is obviously the increasing demand from an aging population, but more importantly, high turnover within the nursing workforce — on average about seventeen percent across health systems in the US. The primary driver of that turnover is that forty percent of nurses report high stress and burnout. And the biggest contributor to that stress and burnout is that they spend forty percent of a typical twelve-hour shift in the system rather than taking care of patients. The administrative work in EHR systems includes flow sheet documentation — rows and rows of data to capture as part of patient assessments, including vitals, head-to-toe assessments, patient safety documentation, and so on. That’s the biggest chunk of that forty percent. On top of that, nurses spend time looking for information — either in the EHR about the patient chart, or looking up drug adverse effects from external credible sources, or searching their own internal protocols and guidelines. And they handle various communication and coordination tasks, many of which could be delegated. All of this forty percent drives high cognitive load, turnover, overtime, and poor documentation quality. That’s the challenge nurses are facing today. What Dragon Copilot is doing to address this is somewhat unique. If you look at the differences between physician and nursing workflows, nursing is typically much more fast-paced and mobile. In an ambulatory setting, a patient comes to visit the doctor — it’s a different environment. In nursing, it’s a very fast-paced environment: nurses are moving around, taking care of patients, attending to a given patient multiple times during a shift. The workflows had to be rethought. Over the last two years we’ve been co-innovating with nine different organizations — including Mercy Health, Advocate Health, and Stanford — learning, validating, and iterating on the solution to make sure we get it right. We knew from day one that for nurses to actually use and like the solution, it had to be as low-friction as possible and naturally fit the workflows they were already accustomed to. We invested heavily in usability, in making sure AI accuracy was right, and in thinking through what organizations would need to scale the solution to thousands of nurses — because this is an entire workforce transformation. The result is what I would call the most comprehensive AI clinical assistant for nurses, which not only streamlines documentation but also surfaces information and automates tasks nurses currently handle manually. The nurse carries the app on a mobile phone, and as they see the patient at the bedside, they select the patient record and have a natural conversation with the patient. Or if they’re moving between patients and have an ad hoc observation — perhaps something they didn’t want to say in front of the patient — they record it and leave the rest to AI, which does the necessary extraction and automatically populates the flow sheet. Nurses can quickly review, edit if needed, and file. In addition, through Dragon Copilot’s chat functionality, nurses can ask about past patient interactions or access pending care activities, because Dragon Copilot provides a kind of cognitive memory of everything that has happened with the patient across the shift. The net result is a meaningful reduction in cognitive load.
Ritu: Thank you, Umesh — really detailed and well-explained. One of the great points you made is that the solution has to fit naturally within existing workflows and eliminate friction, because that’s what leads to so many technologies failing at the POC stage and never scaling. That leads into the next question: when nurses think about AI, there’s often resistance and skepticism. What have you actually seen resonate once nurses experience this AI firsthand? Are you seeing better adoption rates and a more open mindset toward the technology?
Umesh: There is a lot of hype and misinformation in the industry around what AI is and isn’t and how it will change things. From our standpoint, nurses who have actually experienced this technology firsthand tend to share feedback in two main categories. The first is around their own cognitive load. Nurses are saying the system is now doing a lot of things for them. Without this technology, when a nurse is doing documentation away from a workstation, they’re often scribbling observations on their hands to key in later, or trying to remember what they told a patient and whether they followed up. That adds to cognitive burden. Now, because the system ambiently listens to the conversation with the patient and records everything, nurses don’t have to carry that mental weight. The system has already extracted the information. And importantly, those conversations often contain more than just flow sheet data — for example, a promise to follow up on something. The system surfaces that as a pending care activity, and provides a running summary across all interactions with that patient during the shift. These capabilities significantly reduce cognitive load. The second big category is presence. Nurses are saying they now feel present with the patient. Previously, nurses might have their back to the patient while keying things into a workstation, or be mentally focused on documentation while asking questions — not truly present. With this technology, nurses report being fully there with the patient, with a much freer flow of communication and needs, without worrying about explicit documentation. They leave that to the system, which does the extraction automatically, ready for review and filing. Those are the two main categories of feedback we hear from nurses who are using the solution.
Ritu: This is what we’ve heard from other C-suite leaders as well — an indirect benefit is that patients also feel more heard, because nurses are articulating more. Since the ambient system is capturing everything, nurses explain things more fully, and that benefits patients too. As generative AI becomes more embedded in healthcare workflows, there’s increasing discussion about responsible AI, governance, and trust. How should health systems balance the urgency to innovate with the need to ensure that AI-generated insights remain transparent, explainable, and clinically trustworthy — especially as the volume of information makes a human-in-the-loop approach harder to sustain?
Umesh: I would identify three aspects. First, before we ship any product or AI capability, responsible AI is front and center in Microsoft’s product development process. Nothing gets released without going through all the necessary checks — bias evaluation, review by nurses on our own teams who can assess whether an answer makes sense, and all the compliance requirements. That evaluation is done before anything is released. Second, from a workflow standpoint, Dragon Copilot — whether for physicians, nurses, radiologists, or other clinicians — functions as a copilot. The user gets to review the AI output, edit if needed, and then file. Yes, AI can sometimes be wrong. And in these specific workflows, incorrect documentation could create patient safety risk, so clinicians are always expected to review the AI output before filing. The third aspect: many organizations are saying they can’t treat AI as a black box, and they want transparency into how it’s behaving. We’ve built capabilities within our product to address this — we believe in establishing trust through transparency. Customers can configure their system to export raw data into Microsoft Fabric or their own data lake, giving them access to recordings, transcripts, and full visibility into how the AI actually performed. Organizations use this for audit purposes, for research, and for training. Based on ongoing customer feedback, we continue to develop additional capabilities to provide even more transparency — including visibility into usage patterns and what kinds of outputs end users are receiving.
Ritu: You mentioned co-innovating with nine large health systems and learning from them. Given all that experience, what are the key lessons for implementing at enterprise scale? What would you caution health system leaders about, and what would you want them to take away?
Umesh: There were two distinct categories of learning as we went through this experience. The first was iterating on the technology and the core product. Through working with nurses, nurse informatics leaders, and nurse leaders, we enhanced AI accuracy, improved the usability of the solution, and added functionality to continuously reduce friction in the workflow. We also built the organizational tools needed for a mass rollout. Pilots were manageable — a few hundred users. But a full-scale rollout means thousands or tens of thousands of nurses. You need visibility into actual usage across your workforce, across nursing units. So we invested in analytics tools giving nurse informatics leaders access to usage data and patterns. We also built AI tuning and customization tools, because each organization — and even each unit within an organization — has its own flow sheet schemas and charting practices. The AI solution has to align with those specific schemas and practices. We gave customers and their nursing informatics teams the ability to tune the system accordingly. Almost equally important was the second learning: how these solutions actually get rolled out within organizations. At the end of the day, this is a workforce transformation and a change management challenge. It’s a different way of doing things — essentially building a new habit for nurses. Not every nurse is comfortable speaking aloud or charting aloud. We found demographic differences: more tenured nurses tend to be more comfortable with it than Gen Z nurses, which was somewhat counterintuitive. These non-product learnings about how the technology needs to be rolled out are critical to achieving maximum adoption. Change management is key — ensuring nursing leader sponsorship, nurse manager sponsorship, and dedicated champions for the technology in every nursing unit. We encapsulated these as change management best practices so that organizations can use the same technology in the best possible way for their specific context and actually achieve adoption.
Ritu: Digital literacy is so important — it helps remove the skepticism we talked about earlier. Once people understand the technology, they become much more open to adoption. We’re almost at the end of the podcast. Looking ahead one to three years — we used to say five years, but that horizon is now too far — do you believe the biggest impact of AI in healthcare will come from automating administrative work, enabling personalized patient engagement, or do you think an entirely new kind of care model will be unlocked?
Umesh: Restricting to the next three years and focusing on how nursing workflows and care delivery will change — I think we’ll see smart hospital rooms and wearable devices become far more integrated into workflows, creating a much more frictionless experience for both nurses and patients. Today we talk about audio; I think audio plus video will become integrated as well. I believe we’ll build a kind of AI-native UI that can pull together and surface information from far more data sources — delivering not just information but genuine insights. We already have early success there: bringing together data from the EHR with external credible sources and internal guidelines documents. Lastly, I think we’ll see a lot more agentic workflows rolled out. Today we talk primarily about streamlining documentation, but there is so much that nurses handle in interactions with supply departments, transportation, facilities, and so on — all of which takes time away from direct patient care. We’ll see more of those non-patient-facing activities delegated to agentic execution. I think those themes will come together very neatly over the next couple of years.
Ritu: Thank you, Umesh. Thank you for being on our podcast today and sharing all your learnings with us. I hope our listeners take away a lot of valuable insights. On behalf of the Big Unlock Podcast, thank you for joining us.
Umesh: Thank you, Ritu. It was great to be here.
—
Subscribe to our podcast series at www.thebigunlock.com and write us at info@thebigunlock.com
Disclaimer: This Q&A has been derived from the podcast transcript and has been edited for readability and clarity.
About the Host
Ritu M. Uberoy is a healthcare AI strategist, technology executive, educator, and author dedicated to advancing the responsible adoption of Artificial Intelligence across healthcare delivery, digital health, and life sciences. With more than twenty-five years of leadership experience spanning the United States and India, she is recognized for helping healthcare organizations move beyond experimentation to achieve scalable clinical, operational, and business transformation through AI.
She leads AI innovation initiatives, including the AI Center of Excellence at BigRio, where she works with health systems, healthcare technology companies, and life sciences organizations to operationalize Generative and Agentic AI solutions responsibly. Her work focuses on aligning AI innovation with clinical workflows, governance frameworks, workforce readiness, and patient trust—ensuring technology augments human judgment in high-consequence healthcare environments.
Ritu is the co-author of Generative AI: Unlocking the Next Chapter in Healthcare, a practical guide for healthcare executives navigating enterprise AI adoption. She also hosts The Big Unlock podcast, engaging global healthcare leaders on AI transformation and digital innovation. An active educator and speaker, she conducts executive workshops and participates in global forums like HIMSS, ViVE, Women in Tech, AI-Powered Women, RAISE, and more, shaping the future of AI-driven healthcare. Ritu holds advanced degrees in Computer Science and completed specialized AI programs at Harvard and MIT.
About the Legend
Paddy was the co-author of Healthcare Digital Transformation – How Consumerism, Technology and Pandemic are Accelerating the Future (Taylor & Francis, Aug 2020), along with Edward W. Marx. Paddy was also the author of the best-selling book The Big Unlock – Harnessing Data and Growing Digital Health Businesses in a Value-based Care Era (Archway Publishing, 2017). He was the host of the highly subscribed The Big Unlock podcast on digital transformation in healthcare featuring C-level executives from the healthcare and technology sectors. He was widely published and had a by-lined column in CIO Magazine and other respected industry publications.


