Have you heard of Good Machine Learning Practice (GMLP)?
Health Canada, the US Food & Drug Administration, and the UK’s Medicines & Healthcare products Regulatory Agency (MHRA) have collaborated to identify 10 guiding principles to govern the development of Good Machine Learning Practice (GMLP).
Medical devices that use artificial intelligence (AI) and machine learning (ML) technologies are increasingly recognized for their potential impact on health care. Regulatory agencies acknowledge that although real-world data from software algorithms is improving the performance of medical devices, it also presents unique considerations due to their “complexity and iterative and data-driven nature of their development.”1
The assurance of safety and effectiveness
Regulatory agencies around the world have conducted case studies to explore the application of AI. For example, using a software app to track patient responses to a therapeutic intervention or using AI to detect safety signals in pharmacovigilance. The question is, how does one provide reasonable assurance of safety and effectiveness where AI/ML technologies are involved? And, is it always possible? Some Software as a Medical Device (SaMD) products are continuously learning & evolving based on real-world data (adaptive algorithms), while others are not. There are cases where the inner workings of an algorithm are not directly observable – so, how can these be validated?
The following 10 Guiding Principles for GMLP are intended to help Regulators, international standards organizations, and various other bodies, come together to address these challenges, and inform new policies and guidelines for the AI/ML field.
10 Guiding Principles for GMLP
1. Multi-Disciplinary Expertise Is Leveraged Throughout the Total Product Life Cycle
In-depth understanding of a model’s intended integration into clinical workflow, and the desired benefits and associated patient risks, can help ensure that ML enabled medical devices are safe and effective and address clinically meaningful needs over the lifecycle of the device.
2. Good Software Engineering and Security Practices Are Implemented
Model design is implemented with attention to the “fundamentals”: good software engineering practices, data quality assurance, data management, and robust cybersecurity practices. These practices include methodical risk management and design process that can appropriately capture and communicate design, implementation, and risk management decisions and rationale, as well as ensure data authenticity and integrity.
3. Clinical Study Participants and Data Sets Are Representative of the Intended Patient Population
Data collection protocols should ensure that the relevant characteristics of the intended patient population (for example, in terms of age, gender, sex, race, and ethnicity), use, and measurement inputs are sufficiently represented in a sample of adequate size in the clinical study and training and test datasets, so that results can be reasonably generalized to the population of interest. This is important to manage any bias, promote appropriate and generalizable performance across the intended patient population, assess usability, and identify circumstances where the model may underperform.
4. Training Data Sets Are Independent of Test Sets
Training and test datasets are selected and maintained to be appropriately independent of one another. All potential sources of dependence, including patient, data acquisition, and site factors, are considered and addressed to assure independence.
5. Selected Reference Datasets Are Based Upon Best Available Methods
Accepted, best available methods for developing a reference dataset (that is, a reference standard) ensure that clinically relevant and well characterized data are collected and the limitations of the reference are understood. If available, accepted reference datasets in model development and testing that promote and demonstrate model robustness and generalizability across the intended patient population are used.
6. Model Design Is Tailored to the Available Data and Reflects the Intended Use of the Device
Model design is suited to the available data and supports the active mitigation of known risks, like overfitting, performance degradation, and security risks. The clinical benefits and risks related to the product are well understood, used to derive clinically meaningful performance goals for testing, and support that the product can safely and effectively achieve its intended use. Considerations include the impact of both global and local performance and uncertainty/variability in the device inputs, outputs, intended patient populations, and clinical use conditions.
7. Focus Is Placed on the Performance of the Human-AI Team
Where the model has a “human in the loop,” human factors considerations and the human interpretability of the model outputs are addressed with emphasis on the performance of the Human-AI team, rather than just the performance of the model in isolation.
8. Testing Demonstrates Device Performance During Clinically Relevant Conditions
Statistically sound test plans are developed and executed to generate clinically relevant device performance information independently of the training data set. Considerations include the intended patient population, important subgroups, clinical environment and use by the Human-AI team, measurement inputs, and potential confounding factors.
9. Users Are Provided Clear, Essential Information
Users are provided ready access to clear, contextually relevant information that is appropriate for the intended audience (such as health care providers or patients) including: the product’s intended use and indications for use, performance of the model for appropriate subgroups, characteristics of the data used to train and test the model, acceptable inputs, known limitations, user interface interpretation, and clinical workflow integration of the model. Users are also made aware of device modifications and updates from real-world performance monitoring, the basis for decision-making when available, and a means to communicate product concerns to the developer.
10. Deployed Models Are Monitored for Performance and Re-training Risks Are Managed
Deployed models have the capability to be monitored in “real world” use with a focus on maintained or improved safety and performance. Additionally, when models are periodically or continually trained after deployment, there are appropriate controls in place to manage risks of overfitting, unintended bias, or degradation of the model (for example, dataset drift) that may impact the safety and performance of the model as it is used by the Human-AI team.
For regulatory and quality support with regulated products using AI and ML technologies, contact AXSource today at firstname.lastname@example.org.