Software that diagnoses, monitors, or treats a health condition carries a different kind of regulatory weight than a physical device. If your company is developing or commercialising a digital health product, understanding the SaMD regulatory pathway in Canada and the U.S. is not optional. It is the difference between a compliant market entry and a costly setback. Both Health Canada and the FDA have developed distinct frameworks for software as a medical device, and the two systems do not map onto each other perfectly.
Knowing where they align and where they diverge shapes every decision your team makes, from product classification through to submission strategy. Product classification also happens earlier than most teams expect.
Getting it wrong tends to cascade into submission errors, review delays, and internal rework. This post walks through how each regulator defines and classifies SaMD, what the submission pathways look like, and where clinical evidence enters the picture.
How Health Canada Defines and Classifies SaMD
Health Canada regulates software as a medical device under the Medical Devices Regulations, SOR/98-282. To qualify, software must meet the definition in the Food and Drugs Act: it must be intended to diagnose, treat, mitigate, or prevent a disease or condition, or to restore, correct, or modify a physiological process.
General wellness apps and administrative tools fall outside this definition. However, the line between wellness and medical intent is not always obvious. Health Canada’s SaMD guidance has been progressively updated to help manufacturers work through that determination.
SaMD classification in Canada follows a four-tier risk-based system. Each class carries distinct pre-market requirements:
- Class I – Lowest risk. Requires a Declaration of Conformity only.
- Class II – Requires a Medical Device Licence (MDL) before sale in Canada.
- Class III – Requires an MDL plus Quality Management System (QMS) evidence.
- Class IV – Highest risk. Requires an MDL, QMS evidence, and the most rigorous pre-market review. Software that drives treatment decisions for serious or life-threatening conditions typically lands here.
Manufacturers without a physical presence in Canada must also appoint a Canadian Importer or Regulatory Representative. This structural requirement is often overlooked until it creates a hold-up late in the process.
The FDA’s Approach to SaMD Regulation
The FDA regulates software as a medical device through its Digital Health Center of Excellence. Its framework draws significantly from IMDRF SaMD risk categorization principles. Like Health Canada, the FDA applies a risk-based approach. Unlike Health Canada, the FDA’s classification system is condition-specific: both intended use and patient population factor into where the product lands.
For most SaMD products, FDA 510(k) clearance is the most common route to market. A 510(k) submission requires demonstrating that your software is substantially equivalent to a legally marketed predicate device. When no suitable predicate exists, the De Novo SaMD pathway becomes the appropriate route.
De Novo classification is a more intensive process. It establishes a new regulatory category for a novel device type. That said, a successful De Novo grant can itself serve as a predicate for future 510(k) submissions, which has long-term strategic value for companies building a product portfolio.
Premarket Approval (PMA) applies to the highest-risk Class III SaMD products. PMA requires valid scientific evidence of safety and effectiveness, including clinical data. This pathway is the most resource-intensive and applies to software that sustains or supports life or presents significant risk of harm.
For international manufacturers, FDA digital health submissions also require a U.S. Agent. This is a mandatory requirement under 21 CFR Part 807 for foreign establishments.
SaMD Clinical Evaluation Requirements
Both regulators expect manufacturers to demonstrate that their software performs as intended and does not introduce unacceptable risk. However, the SaMD clinical evaluation requirements differ in scope and format depending on classification level and jurisdiction.
Health Canada expects manufacturers to maintain technical documentation that includes a clinical evaluation. This assessment covers available clinical data, identifies residual risks, and demonstrates the benefit-risk profile of the device. For higher-class devices, the evaluation carries more weight and typically draws on published literature, usability testing, and, where appropriate, clinical trial data.
The FDA’s approach aligns with the IMDRF SaMD clinical evaluation framework. It assesses three factors: the state of the healthcare situation or condition, the significance of the information the software provides, and the intended use in that context. Higher-risk combinations require stronger clinical evidence.
One distinction worth understanding clearly: software validation confirms the software performs to its design specifications. Clinical evaluation asks whether those specifications translate into safe and effective use in a real clinical context. Both are required by both regulators. Conflating them is a common source of submission deficiencies.
Key Takeaways
- SaMD classification in Canada uses a four-tier risk system under the Medical Devices Regulations. Classes II through IV require an MDL before market entry.
- FDA 510(k) SaMD clearance is the most common pre-market pathway in the U.S. De Novo applies when no predicate device exists.
- IMDRF SaMD risk categorization principles inform both frameworks, but a Class II device in Canada does not automatically map to an FDA Class II device.
- Clinical evaluation and software validation serve distinct purposes. Both regulators require both, and submissions that blur the distinction typically generate clarification requests.
- Foreign manufacturers entering either market must appoint a designated in-country representative or agent before submitting.
Frequently Asked Questions
Does my digital health app qualify as SaMD?
Many companies assume their software does not meet the threshold for a medical device, only to find otherwise once the classification exercise begins. The question is not whether your app uses health data. It is whether the software is intended to diagnose, treat, mitigate, or prevent a disease or condition, or to modify a physiological process. Both Health Canada and the FDA examine intended use statements and marketing claims closely when making that determination. A classification review early in the development cycle is far less costly than a post-launch enforcement issue.
Can I use the same technical documentation for both Health Canada and the FDA?
Sharing documentation across jurisdictions is possible in some areas, but you cannot submit identical packages to both regulators. Health Canada’s MDL submission requirements and the FDA’s 510(k) or De Novo formats differ in structure, content expectations, and supporting evidence standards. That said, a well-organised technical file, including clinical evaluation documentation, software lifecycle records, and risk management files aligned to ISO 14971, provides a strong foundation that adapts well to both markets. Companies that invest in a harmonised documentation strategy at the outset tend to move faster when preparing jurisdiction-specific submissions.
What is the IMDRF SaMD framework and do I need to apply it?
Neither Health Canada nor the FDA mandates direct use of the IMDRF documents, but both frameworks draw from IMDRF principles. The IMDRF SaMD risk categorization framework categorises software based on the significance of the information it provides and the state of the healthcare situation or condition it addresses. Applying this framework internally helps manufacturers anticipate how regulators will view the product. It also helps build a submission strategy that reflects an accurate risk profile from the start.
Mapping Your SaMD Path to Market
Managing a SaMD submission across two jurisdictions requires more than regulatory familiarity. It requires a strategy that accounts for classification nuances, evidence expectations, and structural requirements specific to each market. Misreading any one of those factors can set a product back by months.
Whether you are pursuing Health Canada SaMD registration or FDA SaMD compliance, the pathway looks different for every product. Quality Smart Solutions works with medical device manufacturers at every stage of the process, from initial classification through to licensing and pre-market submissions.
The right strategy starts with the right conversation. Contact our medical device regulatory specialists to map the right approach for your product.
