Blog Tag: Software as a Medical Device
Tel Aviv-based MedyMatch Technology recently announced it has received Expedited Access Pathway (EAP) designation from the FDA for its intracranial hemorrahage (ICH) detection software medical device.
According to Gene Saragnese, Chairman & CEO of MedyMatch, the platform is a “first-in-class hemorrhage detection tool.” The MedyMatch device utilizes artificial intelligence and deep learning technologies to analyze non-contrast head CT images for signs of ICH. Further implementations of the MedyMatch deep vision platform include diagnosis and monitoring of acute and chronic diseases based on concurrent analysis of imaging data and other patient data. Vice President of Clinical, Regulatory, and Quality Affairs, Dr. Joshua Schulman, said:
This designation is a recognition of both the need for new assessment tools for intracranial hemorrhage and an affirmation of MedyMatch’s technical approach to assisting clinicians to need to make time-sensitive yet accurate decisions in emergency settings.
The EAP Program, intended to speed approval of certain medical devices, generally includes priority review, more interactive review, and senior management involvement. EAP designation can be awarded for devices that address unmet needs for treatment or diagnosis of life-threatening or irreversibly debilitating conditions. It is said to be expected that EAP designated devices will be transitioned to the new Breakthrough Devices program established under the 21st Century Cures Act of 2016.
The U.S. Food and Drug Administration announced the availability of a draft guidance for the clinical evaluation of software as a medical device (SaMD). The draft guidance was prepared by the SaMD Working Group of the International Medical Device Regulators Forum (IMDRF), an international group of medical device regulatory authorities including the FDA. When finalized by the IMDRF, the draft guidance will represent the FDA’s “current thinking” on SaMD clinical evaluation and will not be binding.
SaMD is defined in the guidance as software that functions as a medical device and can run on a general purpose computing platform, “without being part of a hardware medical device.” Unlike other medical device-related software, SaMD primarily has risks associated with incorrect output affecting clinical management of a patient, rather than risks resulting from direct patient contact. Thus, the guidance is intended to address the “uniqueness of indirect contact between patients and SaMD” and provide globally harmonized principles for establishing scientific validity, clinical performance, and analytical validity for a SaMD.
The FDA is seeking public comment on the draft guidance generally, and related to eight specific issues:
Does the document address the intention captured in the introduction/scope or vice versa?
Does the document appropriately translate and apply current clinical vocabulary for SaMD?
Are there other types of SaMD beyond those intended for non-diagnostic, diagnostic and therapeutic purposes that should be highlighted/considered in the document?
Does the document adequately address the relevant clinical evaluation methods and processes for SaMD to generate clinical evidence?
Are there other appropriate methods for generating clinical evaluation evidence that are relevant for SaMD beyond those described in the document?
Are the recommendations related to the “importance of clinical evidence and expectations” appropriate as outlined for the different SaMD categories?
Are the recommendations related to the “importance of independent review” appropriate as outlined for the different SaMD categories?
Given the uniqueness of SaMD and the proposed framework—is there any impact on currently regulated devices or any possible adverse consequences?
The draft guidance is available for comment until December 13, 2016.