11.6 | Navigating AI/ML Challenges in Medical Software Development — Medical Software Course
YaleCoursesShow Notes
In this lesson, Professor John Onofrey delves into the unique practical issues and challenges that Artificial Intelligence and Machine Learning applications encounter throughout the medical software life cycle. He contrasts these with traditional software development, highlighting the critical role of training data, risk assessment from sources like distributional shifts and adversarial attacks, and the necessity for robust system design to manage the inherent 'black box' nature and potential failures of AI/ML models in clinical settings.Uploaded 22-08-25🎯 Learning Objectives• Differentiate the unique requirements and challenges of AI/ML applications within the medical software life cycle from traditional software.• Identify and understand critical risk factors for AI/ML systems, such as distributional shifts, adversarial attacks, and performance drift.• Explain the intrinsic link between training data, model development, and the importance of reproducibility and quality control.• Articulate the concept of treating AI/ML components as "unsafe" and designing robust systems with failure mitigation strategies, including human-in-the-loop approaches.• Describe the distinct workflows for training and deploying AI/ML models and the need for continuous post-market monitoring. Learn more about your ad choices. Visit megaphone.fm/adchoices Learn more about your ad choices. Visit megaphone.fm/adchoices
More from YaleCourses
Game Theory (ECON 159)Uploaded 20-11-08We first play and then analyze wars of attrition; the games that afflict trench warfare, strikes, and businesses in some competitive settings. We find long and damaging fights can occur in class in these games even when the prizes are small in relation to the accumulated costs. These could be caused by irrationality or by players' having other goals like pride or reputation. But we argue that long, costly fights should be expected in these games even if everyone is rational and has standard goals. We show this first in a two-period version of the game and then in a potentially infinite version. There are equilibria in which the game ends fast without a fight, but there are also equilibria that can involve long fights. The only good news is that, the longer the fight and the higher the cost of fighting, the lower is the probability of such a fight.00:00 - Chapter 1. Wars of Attrition: The Rivalry Game17:39 - Chapter 2. Wars of Attrition: Real World Examples24:04 - Chapter 3. Wars of Attrition: Analysis47:53 - Chapter 4. Wars of Attrition: Discussion of SPEs01:06:54 - Chapter 5. Wars of Attrition: GeneralizationComplete course materials are available at the Yale Online website: online.yale.eduThis course was recorded in Fall 2007. Learn more about your ad choices. Visit megaphone.fm/adchoices Learn more about your ad choices. Visit megaphone.fm/adchoices
This video is the live capture of the Yale Quantum Institute Course on Quantum Error Correction, held at the Yale University in July 2025, in partnership with NC A and T.Uploaded 27-08-25This short course will provide viewers strong foundation on Quantum Error Detection and Quantum Error Correction. Viewers are encouraged to take an introduction to quantum information science before viewing this content. Thank you to the Yale ASCEND Initiative for making this short course possible. And for more information on everything quantum at Yale, visit quantuminstitute.yale.edu Learn more about your ad choices. Visit megaphone.fm/adchoices Learn more about your ad choices. Visit megaphone.fm/adchoices
Game Theory (ECON 159)Uploaded 20-11-08We develop a simple model of bargaining, starting from an ultimatum game (one person makes the other a take it or leave it offer), and building up to alternating offer bargaining (where players can make counter-offers). On the way, we introduce discounting: a dollar tomorrow is worth less than a dollar today. We learn that, if players are equally patient, if offers can be in rapid succession, and if each side knows how much the game is worth to the other side, then the first offer is for an equal split of the pie and this offer is accepted. But this result depends on those assumptions; for example, bargaining power may depend on wealth.00:00 - Chapter 1. Ultimatum Games: Why Backward Induction Fails Here14:15 - Chapter 2. Bargaining Games: Setup and Generalization 47:44 - Chapter 3. Bargaining Games: Summary of Proof of Generalization54:29 - Chapter 4. Bargaining Games: Assumptions and ConclusionsComplete course materials are available at the Yale Online website: online.yale.eduThis course was recorded in Fall 2007. Learn more about your ad choices. Visit megaphone.fm/adchoices Learn more about your ad choices. Visit megaphone.fm/adchoices
In this lesson, we dive into the fundamental principles of creating a robust validation plan for medical software. You'll learn how to translate qualitative user needs into objective, quantitative criteria, understand the structure of a comprehensive plan, and discover why early engagement with a statistician is paramount for successful validation studies.Uploaded 22-08-25🎯 Learning Objectives• Understand the foundational principles for creating a medical software validation plan.• Learn to define specific, quantitative, and testable goals for validation studies.• Grasp the four key components of a validation plan: goal, rationale, methods, and data analysis.• Recognize the critical importance of early consultation with a statistician for effective study design and analysis.• Explore examples of how to validate new solutions against existing methods or the standard of care. Learn more about your ad choices. Visit megaphone.fm/adchoices Learn more about your ad choices. Visit megaphone.fm/adchoices
In this lesson, we dive into the critical components of a System Requirement Specification (SRS) template, essential for any medical software development. We'll explore each section, from the cover page to functional and non-functional requirements, and learn how to draft precise, testable requirements that drive successful project outcomes. We also discuss the often-overlooked yet vital "significance" section and the impact of "intended use" on regulatory clearance. Uploaded 19-08-25🎯 Learning Objectives• Identify the key sections of a System Requirement Specification (SRS) document.• Understand the purpose and importance of each SRS section, including significance and intended use.• Differentiate between functional and non-functional requirements in medical software development.• Learn the characteristics of a well-written requirement, focusing on testability and appropriate abstraction.• Explain how a change in the intended use of medical software can impact regulatory clearance. Learn more about your ad choices. Visit megaphone.fm/adchoices Learn more about your ad choices. Visit megaphone.fm/adchoices