Crafting an intended purpose in the context of Software as a Medical Device (SaMD)
Guidance on defining intended purpose for Software as a Medical Device (SaMD), to help SaMD manufacturers in meeting their statutory obligations.
Latest change: First published.
AI Summary
This guidance from the UK Medicines and Healthcare products Regulatory Agency (MHRA) outlines the requirements for products classified as Software as a Medical Device (SaMD) under the UK medical devices regulations. While this document does not target a specific company or reference individual inspection dates, it serves as a broad directive for all legal manufacturers operating within the UK market. The primary focus is the necessity for manufacturers to demonstrate that their products' benefits outweigh potential risks by adhering to current state of the art standards throughout the design and manufacturing lifecycle. A central issue identified by the MHRA involves the submission of vague or insufficient intended purpose statements. Such inadequacies can lead to legal non-compliance and significant safety concerns, as they fail to accurately establish the product's risk level or the specific evidence required for safety verification. To rectify these issues, the MHRA requires manufacturers to develop highly specific intended purpose statements. These documents must clearly articulate what the software does, define the specific population intended to benefit, identify the authorized users, and specify the clinical or home environments where the product will be used. This initiative is part of the Software and AI as a Medical Device Change Programme, aimed at ensuring that regulatory requirements remain clear and that patient safety is prioritized as technology evolves.
The full document, source attachments, and change history are available on KeyPedia. Sign in to view.