- Definitions
- IDE Requirements/Exemptions
- Device and Technology Guidance
- IRB Application (Consent Forms, Reporting, Responsibilities)
- Types of Marketing Applications
- Resources
The Food and Drug Administration (FDA) requires sponsors or sponsor-investigators to obtain an Investigational Device Exemption (IDE) approval from the FDA before conducting research on a new device, or on a new use of an already-approved device, unless the device is determined IDE Exempt or is deemed a Non-Significant Risk device by the IRB using the abbreviated IDE process. The FDA provides a helpful summary presentation about IDEs on this webpage. The information below provides guidance on the applicability of IDE regulations.
Definitions
IDE Requirements
Device and Technology Guidance
Non-Traditional Medical Devices
When thinking about medical devices, some obvious examples may come to mind, such as a pacemaker, an MRI, or a blood pressure cuff. However, there are other "less traditional" devices that also require FDA oversight as medical devices. These are described below.
In vitro diagnostics (IVDs)
- IVDs are those reagents, instruments, and systems intended for use in the diagnosis of disease or other conditions.
- For example, pregnancy test, HIV blood screening test, oncogene testing
- The FDA considers the IVD to be the entire process from specimen collection to results reporting:
- Specimen collection and transport
- Specimen preparation
- Specimen examination/analysis
- Method of calculating/reporting results
- Clinical studies, particularly drug studies, often include objectives to determine whether biomarkers correlate with disease state, treatment response, or disease risk. Depending on the study design, this analysis can be considered the early development of an IVD that is subject to 21 CFR 812.
- Some things to consider when deciding whether 21 CFR 812 may apply are whether the targets for the analysis are specific and well-defined, how much is already known about the biomarkers, and/or how the disease-correlating signature is used.
- CLIA-Certified Laboratory Developed Tests: while these generally fit the definition of in vitro diagnostic medical devices, the FDA is currently exercising enforcement discretion for CLIA-certified LDTs regarding IDE and marketing regulations. Accordingly, the UCSF IRB will not make IDE device determinations for CLIA-certified LDTs. See FDA rescission of the LDT final rule.
- Clinical Decision Support Software (CDSS): The FDA considers some CDSS to fall outside the definition of a medical device only if it meets four conditions: it does not analyze medical images or signals; it only displays/prints/analyzes medical information normally shared among clinicians; it offers recommendations or options (not definitive diagnoses or directives) to a licensed health-care professional (not directly to patients); and it presents enough information for the clinician to independently review the logic behind those recommendations. See FDA CDSS Guidance.
General Wellness Devices: The FDA considers some General Wellness devices to fall outside the definition of a medical device. The devices must be low risk with an intended use limited to encouraging or maintaining general health and wellness, rather than diagnosing or treating any specific disease. See FDA General Wellness app guidance.
The 21st Century CURES Act has exempted certain software functionality from Medical Device regulations.
Such products are intended for use in the collection, preparation, and examination of specimens taken from the human body, e.g., blood, spinal fluid, tissue samples, serum, and urine
Software Functions and Mobile Medical Applications
- The FDA has regulatory oversight of software functions that meet the definition of a device in section 201(h) of the Federal Food, Drug, and Cosmetic Act (FD&C Act). These software functions are referred to as "device software functions." Device software functions may include "Software as a Medical Device (SaMD)" and "Software in a Medical Device (SiMD)."
- A Mobile Medical Application (MMA) "… is a mobile app that incorporates device software functionality that meets the definition of a device in section 201(h) of the FD&C Act; and either is intended:
- Device software functions may be used on a mobile platform (e.g., mobile medical apps), other general-purpose computing platforms, or in the function or control of a hardware device.
- Generally, if a software function is intended to perform a medical device function (i.e., to diagnose disease or other conditions, or to cure, mitigate, treat, or prevent disease), it is regulated as a medical device, regardless of the platform on which it runs.
- FDA intends to focus its regulatory oversight only on those device software functions that could pose a risk to a patient’s safety if they fail to function as intended:
- "Software functions that are an extension of one or more medical devices by connecting to such device(s) for purposes of controlling the device(s) or analyzing medical device data."
- For example, software that enables control of inflation and deflation of a blood pressure cuff via a mobile platform.
- "Software functions (typically, mobile apps) that transform the mobile platform into a regulated medical device by using attachments, display screens, or sensors, or by including functionalities similar to those of currently regulated medical devices."
- For example, a software function that uses the built-in accelerometer on a mobile platform to collect motion information for monitoring sleep apnea.
- "Software functions that become a regulated medical device by performing patient-specific analysis and providing patient-specific diagnosis, or treatment recommendations."
- For example, software functions that use patient-specific parameters and calculate dosage or create a dosage plan for radiation therapy.
- "Software functions that are an extension of one or more medical devices by connecting to such device(s) for purposes of controlling the device(s) or analyzing medical device data."
- For software functions that fall under FDA regulatory oversight, the IDE regulations are enforced and apply when the objective of the clinical investigation is to assess the safety and/or effectiveness of the software function.
- FDA intends to exercise enforcement discretion (meaning it does not intend to enforce requirements under the FD&C Act) for software functions that:
- "Help patients (i.e., users) self-manage their disease or conditions without providing specific treatment or treatment suggestions; or
- Automate simple tasks for health care providers."
- "Help patients (i.e., users) self-manage their disease or conditions without providing specific treatment or treatment suggestions; or
- For software functions that fall under FDA enforcement discretion, the IDE regulations are not currently being enforced.
For IDE Exempt studies, fill out and attach the UCSF Worksheet: Devices
IRB Application and Supporting Documentation Requirements
Timing the IDE Submission
Types of Marketing Applications
Premarket Notification (510(k) applies to Class I, Class II, and some Class III devices.
- A sponsor must demonstrate “substantial equivalence,” meaning that a new device is as safe and effective as the predicate device(s).
- Guidelines describing streamlined 510(k) options are available.
- Clinical studies using 510(k) devices may be subject to IDE regulations. Prior FDA and IRB approval are required.
Premarket Approval (PMA) has more stringent requirements for high-risk Class II devices. In most cases, an IDE is required to clinically evaluate devices subject to PMA regulations.
Humanitarian Device Exemption (HDE), as discussed above, is aimed at encouraging device development for conditions with no more than 8000 patients.
Resources
- UCSF HRPP: Worksheet (Devices)
- FDA Regulatory Support at UCSF (Office of Ethics and Compliance)
- Is Your Study IDE exempt or Non-Significant Risk (NSR)? (Office of Ethics and Compliance)
- Significant and Non-Significant Risk Devices:
- FDA: Device Advice: Comprehensive Regulatory Assistance
- FDA: 21 CFR 812: Investigational Device Exemptions
- FDA: 21 CFR 814: Premarket Approval of Medical Devices
- FDA: 21 CFR 860: Medical Device Classification Procedures