How to submit the SaMD documentation to Health Canada?

Once all the necessary documents for the SaMD application package have been gathered, it is time to submit them to Health Canada. The submission must be in electronic format, sent via email or on CD/DVD as required. The regulatory agency also suggests using their online web-based form for faster processing times. Additionally, any questions about the process can be addressed directly to the Health Canada staff.

What is the Health Canada’s Medical Device Regulatory Framework?

Health Canada’s Regulatory Framework for Medical Devices is comprised of a number of regulations, classifications, and guidelines. These include the Medical Device Regulations, the Food and Drugs Act, the Cosmetic Regulations, Guidance Documents, and Natural Health Product Regulations. All products intended to be sold or used in Canada must meet these criteria before they can be approved by Health Canada.

What is Software as Medical Devices (SaMD)?

Software as Medical Devices (SaMD) refers to software that is intended to be used for medical purposes, without the need for additional hardware. This can include software used for diagnosis, treatment, or prevention of diseases or medical conditions. SaMD can be used on a variety of devices, including smartphones, tablets, and computers. The use of SaMD is becoming increasingly popular in the healthcare industry due to its ability to provide more personalized and efficient care.

What are the SaMD Regulations and Guidelines?

SaMD is regulated by various organizations, including the US Food and Drug Administration (FDA) and the International Medical Device Regulators Forum (IMDRF). The FDA has issued guidelines for SaMD, which include recommendations for risk management, clinical evaluation, and cybersecurity. The IMDRF has also developed guidelines for SaMD, which focus on the safety and effectiveness of the software. It’s important for developers and healthcare providers to stay up-to-date on these regulations and guidelines to ensure the safe and effective use of SaMD.

Why is SaMD Classification and Risk Management important?

SaMD classification and risk management are important because they help ensure the safety and effectiveness of the software. SaMD is classified based on its intended use and risk level, with higher risk devices requiring more stringent regulations and testing. Risk management involves identifying potential risks associated with the software and implementing measures to mitigate those risks. This includes conducting clinical evaluations, ensuring cybersecurity, and monitoring the software for adverse events. By following these guidelines, developers and healthcare providers can ensure that SaMD is safe and effective for patients.

What is SaMD Development and Validation?

SaMD development and validation involves a series of steps to ensure that the software is safe and effective for its intended use. This includes defining the intended use and user requirements, designing and developing the software, and conducting testing and validation to ensure that it meets regulatory requirements and performs as intended. Developers must also document their processes and maintain records to demonstrate compliance with regulations. Validation is an ongoing process that involves monitoring the software for safety and effectiveness and making updates as needed. By following these steps, developers can ensure that SaMD is safe and effective for patients.

What is the regulatory landscape for SaMD?

The regulatory landscape for SaMD can vary depending on the country or region in which it will be marketed. In the United States, the Food and Drug Administration (FDA) regulates SaMD as medical devices and requires them to meet certain standards for safety and effectiveness. In the European Union, SaMD is regulated under the Medical Device Regulation (MDR) and must also meet specific requirements. It’s important to research and understand the regulatory requirements in the markets where you plan to market your SaMD.

How does the SaMD medical device classification system work?

The classification system for SaMD is based on the level of risk associated with the device. The FDA and the European Union both have their own classification systems, but they are similar in that they classify devices into different classes based on the level of risk. Class I devices are considered low risk, while Class III devices are considered high risk. The classification of your SaMD will determine the level of regulatory scrutiny it will receive and the requirements it must meet for safety and effectiveness. It’s important to understand the classification system in the markets where you plan to market your SaMD to ensure compliance with regulatory requirements.

Why is a SaMD regulatory strategy and plan important?

A regulatory strategy and plan for SaMD is important because it helps ensure compliance with regulatory requirements and can help expedite the approval process. It also helps to identify potential regulatory hurdles early on in the development process, allowing for adjustments to be made before significant time and resources are invested. A well-developed regulatory strategy and plan can also help to mitigate risks and ensure the safety and effectiveness of the SaMD.

How to conduct SaMD testing and validation?

SaMD testing and validation are critical components of the regulatory requirements for SaMD. Testing and validation ensure that the SaMD is safe, effective, and performs as intended. The testing and validation process should be well-documented and include testing for functionality, performance, and usability. It should also include testing for cybersecurity and data privacy. Validation should be conducted in accordance with applicable regulatory requirements, such as the FDA’s guidance on software validation. It’s important to involve regulatory experts in the testing and validation process to ensure compliance with regulatory requirements.

Software as a Medical Device (SaMD)

Software as a Medical Device - Classification and Registration in Canada

Health Canada defines software as a medical device (SaMD) as a software intended to be used for one or more medical purposes and performs these purposes without being part of a hardware medical device. SaMD includes in-vitro diagnostic (IVD) medical devices and can run on non-medical computing platforms.

There are inclusion and exclusion criteria that must be met to determine if a device meets the definition of an SaMD. Health Canada follows standards developed by the International Medical Device Regulators Forum (IMDRF) in this criterion determination if the software is a medical device.

SaMD can apply to any of the four classes of medical devices that are under the classification system in Canada.

IEC 62304 Standard and Software Risk Classification for SaMD

The standards followed by Health Canada for SaMD is IEC 62304. This harmonized standard is specifically created for medical device software. There are 3 levels of software risk that Health Canada follows for SaMD (FDA follows 4 levels of software risk). These 3 levels are defined as follows:

Class A – no injury, death or hazardous outcome possible

Class B – no serious injury outcome though a hazardous situation is possible

Class C – death or serious injury is possible through a hazardous situation

This risk analysis and determination requires extensive documentation to support the class in which the device software falls into.

FDA Software Risk Classification based on IEC 62304

There are 4 risk categories for SaMD under the FDA framework.

Category 1 – Low impact SaMD that provides information to drive and/or inform clinical management for a disease or conditions in a serious or non-serious situation or condition.

Category 2 – Medium impact SaMD that provides information to drive and/or inform clinical management for a disease or conditions in a serious or non-serious situation or condition.

Category 3 – High impact SaMD that provides information to drive and/or inform clinical management for a disease or conditions in a serious or non-serious situation or condition.

Category 4 – Very high impact SaMD that provides information to drive and/or inform clinical management for a disease or conditions in a serious or non-serious situation or condition.

How Quality Smart Solutions can assist with your SaMD registration

The first step in our process is determining what class your device is and secondly, determining what risk classification your SaMD falls under based on the country of registration.

Upon determining class and risk categorization, a technical dossier will be prepared following IEC 62304 standards. When the technical dossier is completed, the medical device license application (if applicable) is prepared for submission to Health Canada and/or FDA.

How to establish Quality Assurance Systems for your medical devices?

It is important to establish a Quality Assurance System when producing medical devices, as this will help ensure that your products are safe and effective. Quality assurance systems should include documentation of all activities associated with product development, manufacturing, and customer service. This documentation should include product design reports that detail risk assessments, substantiation of compliance assurance plans, and verification tests performed throughout the production process.

What Software as a Medical Device submission documents are required?

For Software as a Medical Device to be approved and certified by Health Canada, you must submit an application package containing the following documents: Regulatory History Form; Device Master Record; Substantial Equivalence Report; Clinical Evaluation Reports; Design Verification & Validation Reports; Test Protocols; Post Market Surveillance Plan; Labelling & Instructions for Use.

What are the steps for compliance and recertification for your SaMD?

Once a SaMD has been approved by Health Canada and placed on the market for sale, companies must follow specific guidelines in order to maintain compliance. These include regular recertification that examines and confirms the product still meets regulatory requirements. Additionally, manufacturers are responsible for carrying out post-market surveillance activities that analyze customer feedback and any other relevant data collected in order to ensure customer safety throughout the life of the product.

Frequently Asked Questions

What is Health Canada software as a medical device (SaMD)?

Health Canada defines software as a medical device (SaMD) as a software intended to be used for one or more medical purposes and performs these purposes without being part of a hardware medical device. SaMD includes in-vitro diagnostic (IVD) medical devices and this software can run on non-medical purpose computing platforms.

There are inclusion and exclusion criteria that must be met to determine if they meet the definition of a SaMD. Health Canada follows standards developed by the International Medical Device Regulators Forum (IMDRF) in this criterion determination if the software is a medical device.

SaMD can apply to any of the four classes of medical devices that are under the Health Canada medical device classification system.

Can software be classified as a medical device?

Software as a Medical Device (SaMD) is software that is used for at least one medical purpose but is not a part of a medical device’s hardware. This type of software is defined by the Medical Device Regulations Forum (IMDRF). The only pre-requisite for obtaining registration is the existence of an ISO 13485 certificate. To learn the full process for registering your SaMD contact us at info@qualitysmartsolutions.com.

What is the Health Canada IEC 62304 standard?

The standard followed by Health Canada for SaMD is IEC 62304. This harmonized standard is specifically created for medical device software.

What is the Software Risk Classification for SaMD Health Canada?

There are 3 levels of software risk that Health Canada follows for SaMD (FDA follows 4 levels of software risk). These 3 levels are defined as follows:

Class A – no injury, death, or hazardous outcome possible