From 14 to 14,000 patients: How UCHealth scales healthcare with AI | Richard Zane (UCHealth)

Building deterministic security for multi-agent AI workflows | David Gildea (Druva)

David Gildea [https://www.linkedin.com/in/david-gildea-5b54341a/] has learned that traditional security models collapse when AI agents start delegating tasks to 50 or 60 other agents in enterprise workflows. As VP of Product for AI at Druva [https://www.druva.com/], he's building deterministic security harnesses that solve the authentication nightmare of multi-agent systems while maintaining the autonomous capabilities that make AI valuable. David explains why MCP specifications gained faster enterprise adoption than A2A despite having weaker security features, telling Ravin [https://www.linkedin.com/in/ai-security/] how his team is addressing authentication gaps through integration with existing identity management systems like Okta. He shares Druva's approach to wrapping AI agents in security frameworks that require human approval for high-risk actions while learning from user behavior to reduce approval friction over time. He also covers Druva's evolution from custom RAG systems to AWS Bedrock Knowledge Bases, demonstrating how to build knowing that components will be replaced by better solutions.  Topics discussed: * Multi-agent workflow security challenges with 50+ agent delegation chains * MCP specification adoption advantages over A2A for enterprise authentication * Deterministic security harnesses wrapping non-deterministic AI agent behaviors * Identity management complexity when agents impersonate human users in enterprise systems * Human-in-the-loop scaling problems and supervisor agent solutions for authorization * AI-first capability layers replacing traditional API structures for agent interactions * Hyper-personalization learning from individual user behavior patterns over time * Objective-based chat interfaces eliminating traditional software navigation complexity * Building replaceable AI components while maintaining development velocity and learning Listen to more episodes:  Apple  [https://podcasts.apple.com/us/podcast/ai-adoption-playbook/id1789171691] Spotify [https://open.spotify.com/show/6gayb8ofLAvVqjOSIHr1uH?si=31486c38903b4f67]  YouTube [https://youtube.com/playlist?list=PLZ1jCb6_G_LklMnVqkVtVdhCFt0_tu1Li&si=UKu8SnIyGNfN1nJ5] Website [https://www.credal.ai/podcasts]

Building AI agents that learn from feedback: BigPanda's drag-and-drop system | Alexander Page

The fastest path to production AI isn't perfect architecture, according to Alexander Page [https://www.linkedin.com/in/alexanderkpage/]. It's customer validation. In his former role of Principal AI Architect at BigPanda [https://www.bigpanda.io/], he transformed an LLM-based prototype into "Biggy," an AI system for critical incident management. BigPanda moved beyond basic semantic search to build agentic integrations with ServiceNow and Jira, creating AI that understands organizational context and learns from incident history while helping with the entire lifecycle from detection through post-incident documentation. Alexander also gives Ravin [https://www.linkedin.com/in/ai-security/] BigPanda's framework for measuring AI agent performance when traditional accuracy metrics fall short: combine user feedback with visibility into agent decision-making, allowing operators to drag-and-drop incorrect tool calls or sequence errors. He reveals how they encode this feedback into vector databases that influence future agent behavior, creating systems that genuinely improve over time.    Topics discussed: * LLM accessibility compared to traditional ML development barriers * Fortune 500 IT incident management across 10-30 monitoring tools * Building Biggy, an AI agent for incident analysis and resolution * Customer-driven development methodology with real data prototyping * Agentic integrations with ServiceNow and Jira for organizational context * Moving beyond semantic search to structured system queries * AI agent performance evaluation when accuracy is subjective * User feedback mechanisms for correcting agent tool calls and sequences * Encoding corrections into vector databases for behavior improvement * Sensory data requirements for human-level AI reasoning Listen to more episodes:  Apple  [https://podcasts.apple.com/us/podcast/ai-adoption-playbook/id1789171691] Spotify [https://open.spotify.com/show/6gayb8ofLAvVqjOSIHr1uH?si=31486c38903b4f67]  YouTube [https://youtube.com/playlist?list=PLZ1jCb6_G_LklMnVqkVtVdhCFt0_tu1Li&si=UKu8SnIyGNfN1nJ5] Website [https://www.credal.ai/podcasts]

From 14 to 14,000 patients: How UCHealth scales healthcare with AI | Richard Zane (UCHealth)

UCHealth [https://www.uchealth.org/]’s healthcare AI methodology currently enables 1 nurse to monitor 14 fall-risk patients, with plans to scale to 140, then 1,400 through computer vision and predictive analytics. Instead of exhausting pilots, they deploy in phases: test, prove, optimize, then scale. This has created a system that prioritizes force multiplication of current staff rather than replacing them, enabling healthcare professionals to work at the top of their scope. Richard Zane [https://www.linkedin.com/in/richard-zane-md-9b87b5a/], Chief Innovation Officer also tells Ravin [https://www.linkedin.com/in/ai-security/] how their computational linguistics system automatically categorizes thousands of chest X-ray incidental findings into risk levels and manages closed-loop follow-up communication, ensuring critical findings don't fall through administrative cracks. Richard's three-part evaluation framework for technology partners — subject matter expertise, technical deep dive, and financial viability — helps them avoid the startup graveyard.    Topics discussed: * UCHealth's phase deployment methodology: test, prove, optimize, scale * Force multiplication strategy enabling 1 nurse to monitor 14+ patients * Computational linguistics for automating incidental findings * Three-part startup evaluation: subject matter, technical, and financial assessment * FDA regulatory challenges with learning algorithms in healthcare AI * Problem-first approach versus solution-seeking in healthcare AI adoption * Cultural alignment and operational cadence in multi-year technology partnerships Listen to more episodes:  Apple  [https://podcasts.apple.com/us/podcast/ai-adoption-playbook/id1789171691] Spotify [https://open.spotify.com/show/6gayb8ofLAvVqjOSIHr1uH?si=31486c38903b4f67]  YouTube [https://youtube.com/playlist?list=PLZ1jCb6_G_LklMnVqkVtVdhCFt0_tu1Li&si=UKu8SnIyGNfN1nJ5] Website [https://www.credal.ai/podcasts]

How construction companies can leverage AI at scale | Dan Williamson

The construction industry sits on goldmines of unstructured data that could revolutionize how buildings get built. From thousands of contracts to communication logs spanning 12-36 month building cycles, Dan Williamson [https://www.linkedin.com/in/danwilliamson1/], Director of Artificial Intelligence at Ryan Companies US [https://www.ryancompanies.com/], says all that data remains largely untapped. Dan walks Ravin [https://www.linkedin.com/in/ai-security/] through how Ryan is building AI systems to unlock this data, from contract risk analysis to robots doing reality capture on job sites. But the real challenge is organizational. Getting trade workers who've operated the same way for decades to embrace robotic assistants requires finding business evangelists willing to co-create change rather than having it imposed from above. Topics discussed: * Building enterprise AI strategy in traditional construction and real estate industries * Leveraging unstructured data from contracts, communications, and building drawings * Finding business evangelists to co-create change rather than imposing technology top-down * Deploying robots on job sites for reality capture and progress tracking * Processing hundreds of thousands of leases and construction contracts with AI * Transforming construction drawings from unstructured data into actionable insights * Managing 60+ contracts per project across 100-250 annual construction projects * Automating safety risk assessment through job site communication analysis * Replacing manual data entry with AI-powered construction workflow applications

Why AI should live in the business unit, not security: Lessons from mobile and cloud transitions | Mandy Andress (Elastic)

At Elastic [https://www.elastic.co/], CISO Mandy Andress [https://www.linkedin.com/in/mandyandress/] learned that pragmatic guardrails work better than blanket bans for managing AI adoption across their 3,500-person distributed workforce. Instead, she enables AI tools with smart controls rather than block them entirely. As both a customer and provider in the AI ecosystem, Elastic faces unique challenges in AI strategy. Mandy explains how they're applying hard-learned lessons from cloud vendor lock-in to build flexible AI systems that can switch foundation models with minimal engineering effort.  She also shares why AI ownership is naturally migrating from security teams to business units as organizations mature their understanding of the technology.   Topics discussed: * Elastic's dual role as vector database provider and AI customer. * Transitioning AI ownership from security teams to business units. * Building foundation model flexibility to avoid vendor lock-in. * Quantifying AI business value through time auditing versus traditional ROI. * Managing enterprise AI tool procurement floods without innovation barriers. * Pragmatic AI guardrails versus blanket AI-blocking strategies. * AI team organizational structures based on technical maturity. * Focusing AI governance on access controls and API fundamentals. * Behavioral analytics for credential-based attack detection. Listen to more episodes:  Apple  [https://podcasts.apple.com/us/podcast/ai-adoption-playbook/id1789171691] Spotify [https://open.spotify.com/show/6gayb8ofLAvVqjOSIHr1uH?si=31486c38903b4f67]  YouTube [https://youtube.com/playlist?list=PLZ1jCb6_G_LklMnVqkVtVdhCFt0_tu1Li&si=UKu8SnIyGNfN1nJ5] Website [https://www.credal.ai/podcasts]