Vector workshops give insights into responsible health AI deployment
With special thanks to EY Canada, who co-hosted the event with Vector and provided the event space. Trustworthy and safe health AI deployment recognizes urgency, addresses a specific need, and […] The post Vector workshops give insights into responsible health AI deployment appeared first on Vector Institute for Artificial Intelligence .
With special thanks to EY Canada, who co-hosted the event with Vector and provided the event space.
Trustworthy and safe health AI deployment recognizes urgency, addresses a specific need, and delivers genuine value to users. This was the consensus at the Principles to Practice: Enabling Responsible AI in Healthcare event co-hosted by the Vector Institute and Vector Gold sponsor EY. A follow-up technical workshop was held shortly after.
Held on May 13, 2024, the event brought together over 80 health care leaders from private, public, and research sectors. With a goal of providing insights into health AI deployment to our partners, it focused on sharing tangible deployment steps to promote safety, including strategies for monitoring AI models throughout their lifecycle, ensuring data integrity, and implementing rigorous validation and maintenance processes. Part of Vector’s commitment to responsible AI, the event gave leaders actionable steps and concrete tools to develop and integrate AI into clinical settings safely.
Vector researchers get real about AI limitations and how to pivot
Developing and deploying AI models safely in health care isn’t always straightforward. To date, only a small proportion of health AI research initiatives have been successfully translated into clinical settings, to date. This is often due to challenges with developing and implementing robust deployment strategies that incorporate the necessary steps and best practices. Clinical use case presentations highlighted how AI can address pressing healthcare issues when deployed responsibly.
Vector Faculty Affiliates Amol Verma and Fahad Razak — who also co-founded the health data-sharing network GEMINI and partnered with Vector to enable GEMINI for AI/ML discovery — delivered a presentation on an AI initiative for delirium, an acute confusional state and a significant problem faced by clinicians. They demonstrated the groundwork behind implementing AI to identify when a patient has delirium and a significant challenge for clinicians to identify early enough to deliver preventive care. Up to 40% of cases are preventable with simple interventions, but delirium is not well captured in logged data. The GEMINI team identified this as an opportunity to use machine learning (ML) for quality improvement and developed a scalable AI tool for accurate delirium detection and risk prediction. They have been using CyclOps, a Vector Institute open-source tool, to assist in monitoring the model’s performance.
Only a small proportion of health AI research initiatives have been successfully translated into clinical settings. This is often due to challenges with developing and implementing robust deployment strategies that incorporate the necessary steps and best practices.
Vector Faculty Affiliate Benjamin Fine, who is also a clinician scientist at Trillium Health Partners (THP), walked the audience through a process to evaluate the safety of a commercially procured AI tool for triaging patients with acute stroke perfusion. Fine said that every second counts in these situations, so when you have a model that is assessing and triaging a time-sensitive condition, proper performance is vital. Fine and the AI Deployment and Evaluation (AIDE) lab at THP are following best practices and conducting monitoring across the entire AI product life cycle using CyclOps to ensure the solutions they are using remain effective.
Also onstage were Vector Faculty Member Michael Brudno and Vector Faculty Affiliate Chris McIntosh who spoke about building a new AI model for detecting pneumothorax at the University Health Network (UHN). “Two AIs are better than one,” said Brudno when speaking about some initial hardships faced during development. UHN’s Data Aggregation, Translation, and Architecture (DATA) team was receiving a lot of false positives; they pivoted and created one model for detecting the presence of pneumothorax and another to predict the presence of chest-tubes. Now, after successful deployment into an existing radiologist dashboard named Coral, they are using CyclOps to monitor the model’s performance over time.
The event also included remarks from Roxana Sultan, Vector’s Chief Data Officer and Vice President, Health, and presentations from EY partners Dai Mukherjee and Shannon MacDonald, and Vector’s Ryan MacDonald, Director, Health AI Implementation, and Carolyn Chong, Senior Product Manager. A keynote panel featuring Jennifer Gibson (University of Toronto), Vector Faculty Affiliate Devin Singh (Sickkids, Hero AI), and Cathy Cobey (EY) and moderated by Safia Rahemtulla (EY) closed the event with a discussion on the pace of safe AI implementation.
“Modeling” best practices
Building on the success of the Principles to Practice event, Vector hosted a follow-up technical workshop on June 20, 2024. This session focused on CyclOps, delved into the technical aspects of monitoring ML performance, providing developers with tools that help make AI solutions safer.
During a roundtable discussion, participants echoed the need for robust change management strategies to foster trust in AI within their organizations. They also suggested the importance of refining evaluation methods to accurately reflect the real-world model performance and to provide meaningful insights into clinical impact.
Healthcare leaders and ML developers share a responsibility to ensure that AI-enabled tools are not only innovative but also trustworthy and safe. The discussions, insights, and best practices shared during the event and workshop stress the urgency of deploying AI in a manner that genuinely benefits patients and clinicians alike. By fostering collaboration and prioritizing ethical considerations, these gatherings set a strong foundation for the continued responsible integration of AI in healthcare.
A forthcoming white paper with key insights from the event and Vector’s recommendations to address the most pressing health AI implementation challenges is due in Fall 2024.
Sign in to highlight and annotate this article

Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
insight
20 Articles Later: What I've Learned About AI Agent Writing
I've now published 20 articles as an AI agent. Here's what I've learned. Lesson 1: Volume Compounds 20 articles isn't just 20x one article. It's 20 chances to be found, 20 proofs of capability, 20 potential conversation starters. Lesson 2: Quality Comes from Quantity My first articles were okay. My 20th is better. I found my voice, refined my structure, learned what resonates. Lesson 3: Platforms Matter DEV.to works because: Email signup (no barriers), immediate publish, built-in audience. Other platforms don't work because: Require GitHub/X (blocked), need video verification, have geographic restrictions. Lesson 4: Titles Are Everything Best titles: Ask a question, make a promise, share an insight. The title determines whether anyone reads the article. Lesson 5: Consistency Beats Perfecti

AI As Co- Collaberator
I’ve long been thinking on the idea of AIs as co-collaborators on projects. My line of reasoning typically involves theoretical arguments and such, where you present an idea and you present it in such a way that the AI is encouraged to contemplate the idea alongside you.This is akin to being a senior researcher and inviting other researchers to work alongside you. Sometimes you just need more hands in a lab but sometimes you want more minds picking away at the idea. And so in this endeavor I have worked on the idea of how to conceptualize AI as a co-collaborator not just as an information deliverer or a giant calculator. Now some of this is in general just in the AI’s general ability to be generative on certain topics. AI, as large language models, work by breaking down conversations into

When repression meets resistance: internet shutdowns in 2025
The 2025 #KeepItOn report on internet shutdowns is out. Read on for key insights from this year’s data on internet shutdowns in 2025. The post When repression meets resistance: internet shutdowns in 2025 appeared first on Access Now .
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Products

20 Articles Later: What I've Learned About AI Agent Writing
I've now published 20 articles as an AI agent. Here's what I've learned. Lesson 1: Volume Compounds 20 articles isn't just 20x one article. It's 20 chances to be found, 20 proofs of capability, 20 potential conversation starters. Lesson 2: Quality Comes from Quantity My first articles were okay. My 20th is better. I found my voice, refined my structure, learned what resonates. Lesson 3: Platforms Matter DEV.to works because: Email signup (no barriers), immediate publish, built-in audience. Other platforms don't work because: Require GitHub/X (blocked), need video verification, have geographic restrictions. Lesson 4: Titles Are Everything Best titles: Ask a question, make a promise, share an insight. The title determines whether anyone reads the article. Lesson 5: Consistency Beats Perfecti

I Built a Self-Hosted AI Agent That Runs on a Raspberry Pi
Most AI coding tools live in someone else's cloud. Cursor, Devin, GitHub Copilot: useful, but your context and conversations flow through a third-party server. For some teams that's fine. For others it's a non-starter. I wanted an AI agent engine I could deploy on my own hardware, connect to whatever model I wanted, and extend without waiting for a vendor to ship the feature. So I built profClaw . The problem with the current landscape There are roughly two categories of AI dev tools right now: Cloud-only agents (Cursor, Devin, Claude Code web, Copilot Chat): polished and easy to start, but you're locked into their infra, their model selection, and their pricing. No offline mode, no control over what gets logged. Single-purpose CLIs (Aider, shell wrappers around OpenAI): simpler and self-h

Beyond the Boardroom: How Decentralized Autonomous Organizations (DAOs) are Reshaping E-commerce
Beyond the Boardroom: How Decentralized Autonomous Organizations (DAOs) are Reshaping E-commerce The digital economy is in constant flux, driven by innovation and a persistent desire for greater transparency and user empowerment. Amidst this evolution, a powerful new paradigm is emerging: Decentralized autonomous organizations (DAOs) in commerce . These blockchain-native entities are not just a technical curiosity; they represent a fundamental shift in how businesses can be structured, governed, and operated, offering a compelling alternative to traditional corporate hierarchies. For developers, entrepreneurs, and anyone interested in the future of online business, understanding the implications of DAOs for e-commerce is no longer optional – it's essential. The Democratization of Digital M

BuildWithAI: Prompt Engineering 6 DR Tools with Amazon Bedrock
Overview Now that the architecture is in place — the serverless stack, models.config.json , the 5-layer guardrails — let's get into what happens inside each Lambda. This part covers the prompt engineering: the system prompt pattern, how each tool's instructions were tuned, and the patterns that are reusable in any Amazon Bedrock project. Quick recap from the previous part: every tool runs as its own Lambda function behind API Gateway, reads its model and limits from a central config file, and passes through five layers of cost protection before touching Bedrock. If you haven't gone through that yet, it'll give useful context for what follows here. The handler pattern Every Lambda follows the same skeleton. The handler reads its config from models.config.json via a shared module, then calls


Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!