Translational Medical AI: From AI Research to Real-World Deployment as SaMD

About this Series: Artificial Intelligence (AI) is rapidly evolving and no longer confined to controlled research settings but increasingly entering and shaping clinical practice. It holds enormous transformative potential for medicine, but translating academic research into real-world clinical application requires more than technical and clinical expertise. This blog series explores the pathways from AI research to Software as a Medical Device (SaMD), focusing on the regulatory, technical, and institutional practices that help bridge the gap.

Part 1: Regulatory considerations when bridging the research-deployment gap

Why regulation matters early in research

As AI models and tools transition from research into practice, this inevitably raises questions about regulatory oversight. Some AI tools used in healthcare may qualify as Software as a Medical Device (SaMD), which software that serves a medical purpose without being an actual physical device [1].

However, not all AI in healthcare falls under medical device regulations (MDR). For example, tools used solely for administrative purposes, pure educational or academic tools, and decision-support software that meets certain criteria may be exempt. These considerations can be very nuanced. For example, educational tools with respective disclaimers and clear intended use statements are very likely outside the scope of MDR. However, as soon as personalized advice comes into place that may be used to guide clinical decisions, it may cross into the regulated domain.

a human head silhouette with circuit lines and binary code

AI as SaMD – Understanding the concept

If considered as SaMD, Health Canada classifies it using a risk-based approach, as laid out in the MDR (Schedule 1) and elaborated in the SaMD guidance[2]. The classification depends on the severity of the condition, the role of the software in clinical decision-making, and whether it provides informative vs. directive outputs. More precisely Health Canada defines two axes:

  • state of healthcare situation or condition (from critical to serious and non-serious) and
  • significance of information provided by SaMD to inform healthcare decision (from treat or diagnose to drive clinical/patient management and inform clinical/patient management)

A critical healthcare situation would be a life-threatening state of health, a major therapeutic intervention or a fragile intended target population (e.g., pediatrics). A non-serious situation would be a slow and predictable disease state, minor (and normally non-invasive) therapeutic interventions or a non-patient target population.

This classification determines the level of regulatory scrutiny and evidence required for deployment. Class IV is the most demanding from a regulatory perspective and requires more comprehensive evaluation, documentation, and quality management, while Class I is the least demanding and can often be addressed within existing institutional research infrastructures.

Examples of SaMD classification in practice

While the principles of SaMD classification may seem abstract, seeing how they apply to real or hypothetical AI can help researchers determine the class of their tool. The following examples are taken from Health Canada’s guidance on SaMD[3], including non-medical device software as well as Class I to Class III examples. Note that, in principle, SaMD can also fall into Class IV, but typically not as a standalone software which is why they are not considered in the following examples. 

Read through the examples and check your intuition:

Examples of SaMD Classification in Practice
ExampleClass
Software that provides a diabetic patient with simple tools to organize and track their health information. The healthcare professional can input medical information for diabetes-related conditions such as kidney and eye function as well as drug dosage. The software also obtains data from a closed-loop blood glucose monitor. The software analyzes the information collected to provide early diagnosis of a diabetic emergency. When a patient experiences a diabetic emergency, the software will alert the healthcare professional and use the analyzed information to make treatment decisions based on the patient’s unique health profile.III
Software intended for health care professionals that uses an algorithm to analyze patient information, such as blood pressure, heart rate, weight, and age to determine which treatment plan is likely to be most effective in treating the patient's condition. These patient-specific treatment recommendations would otherwise not be available to the health care professional. The healthcare professional cannot independently review the calculations made by the algorithm. II
Software that provides patients with simple tools to organize and track their health information. The information is intended to be shared with a healthcare provider as part of a pre-diabetes management plan.NA (not a medical device)
Software that uses artificial intelligence to tailor mental health treatment plans, including medication dosing, based on patient-derived signals. The software also calculates the probability of remission for a given treatment plan. The software is intended for use in the clinician's office during a routine appointment.II
Software that is intended for use in rehabilitation and active range of motion assessment. This software analyzes images from cameras to generate objective measurements of joint mobility and posture. The data generated by the software is intended to function as a clinical aid in the assessment and rehabilitation of joint dysfunction and posture imbalance.I
Software intended to be used as an annotation tool for the production of diagnostic and prognostic reports of clinical electroencephalogram (EEG) studies, based on a user's traditional visual interpretation of EEG. It is intended to standardize and structure reporting of cl inical EEG according to an international academic standard. The software is also intended to reduce the workload of the reporting doctor by automatically importing minimal pieces of information from an external EEG system.NA (not a medical device)
Chat-based triage software intended to guide users to the most appropriate form of help based on their medical symptoms. The chat-based triage software outcomes are intended to indicate to a user the next best step to take when seeking further health care, and to provide safe and appropriate clinician-vetted advice where appropriate. Triage advice outcomes include self-care, pharmacy, primary care, dental, ophthalmic, sexual health and emergent care advice outcomes.NA (not a medical device)
Radiation treatment planning software that accepts patient images, allows for a healthcare professional to identify and delineate tumours, healthy tissues, and critical organs, calculates a complex plan for how the therapy system will deliver radiation, and then serves as input for medical linear accelerators in the treatment of cancer.III

You can find details and further examples in the Health Canada’s guidance on SaMD[3]. These examples illustrate that SaMD classification is often highly nuanced, and that the outcome ultimately depends on the intended use. The intended use of SaMD is reflected across multiple sources, such as labelling, user manuals, and websites. Regulators expect the relevant details to be captured clearly in the intended use statement.

doctor using a tablet

From SaMD to AIaMD

While the SaMD framework applies broadly to all medical software, AI presents unique regulatory challenges. Traditional medical devices are static, but AI can learn and evolve after deployment. To address this, health regulators have started to publish specific guidance documents such as, for example, the Good Machine Learning Practice for Medical Device Development: Guiding Principles [4] and Transparency for Machine Learning-Enabled Medical Devices: Guiding Principles [5] collaboratively developed by FDA (US), MHRA (UK) and Health Canada. These documents mark a shift toward lifecycle-based oversight recognizing that AI are dynamic systems that may evolve post-deployment.

What’s next?

For researchers, understanding and addressing regulatory implications early in AI development can facilitate future clinical translation. Study design, validation strategies, and documentation practices can be aligned with potential regulatory classification, and these activities should be planned and budgeted for within the research project. Integrating regulatory considerations into research planning helps ensure that promising AI innovations can make a smooth (regulatory compliant) transition to real-world healthcare deployment.

In the next article, we’ll take a closer look at SaMD Class I and give practical insights into how research institutions can establish the processes, documentation, and governance structures needed to deploy their Class I AI within a regulated framework.

Read Part 2 in the series: Navigating Class I SaMD as an AI Researcher

References

  1. Palaniappan K, Lin EYT, Vogel S. Global Regulatory Frameworks for the Use of Artificial Intelligence (AI) in the Healthcare Services Sector. Healthcare. 2024;12:562. doi: 10.3390/healthcare12050562
  2. Health Canada. Guidance Document: Software as a Medical Device (SaMD): Definition and Classification. 2019.
  3. Health Canada. Guidance Document: Software as a Medical Device (SaMD): Classification Examples. 2019.
  4. Health Canada, Food and Drug Administration, Medicines and Healthcare products Agency. Good Machine Learning Practice for Medical Device Development: Guiding Principles. FDA. Published Online First: 27 October 2021.
  5. Health Canada, Food and Drug Administration, Medicines and Healthcare products Agency. Transparency for machine learning-enabled medical devices: Guiding principles. Published Online First: 2021.
  6. Health Canada. Pre-market guidance for machine learning-enabled medical devices. 2025.
  7. US Food and Drug Administration. Artificial Intelligence-Enabled Device Software Functions: Lifecycle Management and Marketing Submission Recommendations. 2025.
  8. Medicines and Healthcare products Agency. Predetermined change control plans for machine learning-enabled medical devices: guiding principles. 2023.

Note: The article above is not intended to provide legal advice.