An Investigational Device Exemption (IDE) application is submitted to the FDA to allow a medical device that would otherwise require premarket approval to be used in a clinical investigation to collect safety and effectiveness data. The IDE includes a complete investigational plan, a description of the device and its manufacturing, a risk analysis, a summary of prior investigations, the clinical investigation protocol, and information about the investigators and institutions involved. The IDE enables lawful shipment and use of an unapproved device for clinical study purposes. Significant risk devices require FDA approval of the IDE before the study can begin, while nonsignificant risk devices may proceed with Institutional Review Board (IRB) approval alone. The IDE sets the framework for data collection that will ultimately support a PMA, De Novo, or 510(k) submission.
The EU MDR Technical File is the complete set of technical documentation required under Annex II and III of the EU Medical Device Regulation (2017/745) for Class I, IIa, and IIb devices. It includes the device description and specifications, design and manufacturing information, General Safety and Performance Requirements (GSPR) checklists, risk management documentation, product verification and validation data, and the clinical evaluation report. The Technical File must demonstrate full compliance with all applicable MDR requirements and must be maintained and kept up to date throughout the device's commercial life. It is reviewed by Notified Bodies for devices requiring conformity assessment and must be made available to competent authorities upon request. The Technical File is a living document that requires updates as clinical data accumulates, standards evolve, or design changes are implemented.
A 510(k) submission is a premarket notification submitted to the U.S. Food and Drug Administration (FDA) to demonstrate that a new medical device is substantially equivalent to a legally marketed predicate device. The submission includes device descriptions, intended use statements, technological comparisons, performance data (bench testing, biocompatibility, clinical data if needed), and labeling. The FDA uses this information to determine whether the new device can be cleared for commercial distribution. The 510(k) pathway is the most common route to market for moderate-risk (Class II) medical devices in the United States. A well-prepared 510(k) requires careful predicate device selection, thorough comparative analysis, and supporting test data that demonstrates the device is as safe and effective as the predicate. The submission may be Traditional, Special, or Abbreviated depending on the circumstances.
A Premarket Approval (PMA) application is the most rigorous type of device marketing submission required by the FDA, applicable to Class III medical devices that pose the highest risk. The PMA must contain sufficient scientific evidence to provide reasonable assurance of the device's safety and effectiveness, including detailed manufacturing information, preclinical studies, clinical investigation data, and proposed labeling. Unlike the 510(k) pathway, PMA requires demonstration of safety and effectiveness through valid scientific evidence, often including data from well-controlled clinical trials. The application undergoes a thorough review process involving advisory panel meetings, manufacturing facility inspections, and detailed scientific analysis. PMA approval is considered a private license granted to the applicant for marketing a particular device.
A De Novo submission is a regulatory pathway for novel, low-to-moderate risk medical devices that have no legally marketed predicate device. This classification request provides a route to market for devices that would otherwise default to Class III due to lack of a predicate, but for which general and special controls can provide reasonable assurance of safety and effectiveness. The submission includes a risk-based classification assessment, proposed special controls, and performance data. Once a De Novo request is granted, the device receives a new classification regulation and product code, and it can then serve as a predicate for future 510(k) submissions. The De Novo pathway has become increasingly important for innovative devices, including digital health technologies and novel diagnostic tools, that do not fit neatly into existing device classifications.
An EU MDR Gap Analysis is a systematic evaluation that identifies the differences between a medical device's existing technical documentation (typically prepared under the MDD) and the requirements of the EU Medical Device Regulation (EU 2017/745). The analysis maps current documentation against MDR Annexes II and III, General Safety and Performance Requirements, and other applicable provisions to identify areas where additional work is needed to achieve compliance. This deliverable is particularly critical for manufacturers transitioning legacy devices from MDD certification to MDR compliance. The gap analysis provides a prioritized roadmap of documentation updates, additional testing, clinical evidence generation, and process changes required. It serves as a planning tool for resource allocation and project management during the MDR transition process.
Device Classification Reports ▼
A Device Classification Report is a regulatory analysis document that determines the appropriate classification of a medical device under applicable regulatory frameworks such as the FDA classification system (Class I, II, or III) or the EU MDR classification rules (Annex VIII). The report evaluates the device's intended purpose, mechanism of action, duration of contact, invasiveness, and other classification criteria to arrive at the correct regulatory class. Accurate device classification is foundational to the entire regulatory strategy, as it determines the applicable premarket submission pathway, conformity assessment route, quality system requirements, and post-market obligations. The classification report typically includes a description of the device and its intended use, an analysis of each applicable classification rule or regulation, a comparison with similar classified devices, and a conclusion with supporting rationale.
Predicate Device Comparison ▼
A Predicate Device Comparison is an analytical document prepared as part of a 510(k) submission that systematically compares a new medical device to one or more legally marketed predicate devices. The comparison evaluates similarities and differences in intended use, indications for use, technological characteristics, design features, materials, performance specifications, and biocompatibility to establish substantial equivalence. This comparison is the foundation of the 510(k) substantial equivalence argument. A strong Predicate Device Comparison clearly identifies any differences between the subject and predicate devices and explains why those differences do not raise new questions of safety or effectiveness, or demonstrates through testing that the differences do not adversely affect the device. Predicate selection is a critical strategic decision that can significantly influence the review pathway and timeline.
Q-Submission / Pre-Submission ▼
A Q-Submission (also known as a Pre-Submission or Pre-Sub) is a formal mechanism for requesting feedback from the FDA prior to submitting a marketing application. It allows device manufacturers to present their regulatory strategy, proposed testing protocols, clinical study designs, or specific questions to the FDA review division and receive written feedback or participate in a meeting. This process is covered by FDA guidance on the Q-Submission Program. Q-Submissions are a strategic tool that can significantly improve the quality and efficiency of subsequent regulatory submissions. By engaging the FDA early, manufacturers can identify potential issues, confirm acceptable testing methodologies, clarify predicate device selection, and align on the clinical data needed to support clearance or approval. The feedback received is non-binding but is highly influential in shaping the submission strategy.
Technical Documentation ▼
Technical Documentation is a broad term for the comprehensive compilation of records that demonstrate a medical device's compliance with applicable regulatory requirements. Depending on the regulatory framework, this may encompass design specifications, manufacturing processes, verification and validation test results, risk management files, biocompatibility evaluations, labeling, and clinical evidence. It serves as the primary evidence package reviewed by regulatory authorities and Notified Bodies. For EU MDR purposes, Technical Documentation follows the structure specified in Annexes II and III. For FDA submissions, it supports the Device Master Record and submission dossier. Regardless of jurisdiction, Technical Documentation must be logically organized, traceable to design inputs and regulatory requirements, and maintained throughout the product lifecycle to reflect the current state of the device.
A Design Dossier is a comprehensive document package historically required under the EU Medical Device Directives (MDD/AIMD) for Class III and certain Class IIb devices undergoing Notified Body review via the full quality assurance or type examination routes. It encompasses design documentation, manufacturing information, risk analysis, preclinical and clinical data, and declarations of conformity that demonstrate the device meets Essential Requirements. Although the EU MDR has largely replaced the Design Dossier requirement with the broader Technical Documentation framework, the term remains in use in the industry. The Design Dossier concept continues to inform the structure and completeness expected in modern technical documentation, particularly for high-risk devices undergoing Notified Body scrutiny under the MDR conformity assessment process.
Substantial Equivalence Report ▼
A Substantial Equivalence Report is a detailed document within a 510(k) submission that presents the scientific and regulatory argument that a new device is substantially equivalent to a predicate device. It goes beyond a simple comparison by providing a comprehensive analysis of how the device's indications, technology, and performance characteristics compare to the predicate, supported by bench testing, biocompatibility data, and clinical evidence where applicable. The report must demonstrate that the device has the same intended use as the predicate and either has the same technological characteristics or, if it has different technological characteristics, that those differences do not raise different questions of safety and effectiveness and that the device is at least as safe and effective as the predicate. The FDA reviewer relies heavily on this report to make a substantial equivalence determination.
Equivalence Justification ▼
An Equivalence Justification is a regulatory document that establishes the clinical, technical, and biological equivalence between a subject medical device and a chosen equivalent device for the purpose of using the equivalent device's clinical data to support the subject device's clinical evaluation. Under the EU MDR, equivalence must be demonstrated across all three dimensions (clinical, technical, biological) with a high level of specificity. The EU MDR has significantly tightened the requirements for claiming equivalence compared to the MDD, particularly requiring a contractual agreement with the equivalent device manufacturer to access their technical documentation (unless both devices are made by the same manufacturer). The justification must detail each equivalence parameter, address any differences, and explain why those differences do not affect the applicability of the equivalent device's clinical data.
Regulatory Response Letters ▼
Regulatory Response Letters are formal written communications prepared in response to questions, deficiency notices, or additional information requests issued by regulatory authorities such as the FDA, Notified Bodies, or other health authorities during the review of a marketing submission. These letters must address each concern raised by the reviewer with clear, well-organized, and scientifically supported responses. The quality and completeness of response letters can significantly impact review timelines and outcomes. Effective response letters include point-by-point responses to each question, reference supporting data or documentation, provide clear rationale for any disagreements with the reviewer's position, and include any revised submission sections as needed. They require careful coordination across regulatory, clinical, and technical teams.
Notified Body Responses ▼
Notified Body Responses are formal written communications addressing questions, observations, or deficiencies raised by Notified Bodies during their review of IVD technical documentation as part of the conformity assessment process. These responses must systematically address each point raised with clear explanations, supporting evidence, and any revised documentation. Effective Notified Body responses require a thorough understanding of both the specific technical questions and the broader regulatory context. They must be precise, well-referenced, and demonstrate that the manufacturer has fully considered and addressed the Notified Body's concerns. Response quality directly impacts the timeline for CE marking and can affect the overall relationship with the Notified Body.
A Risk Management Report documents the complete risk management process for a medical device as required by ISO 14971. It summarizes all risk management activities conducted throughout the device lifecycle, including hazard identification, risk estimation, risk evaluation, risk control measures, and residual risk assessment. The report provides evidence that the overall residual risk associated with the device is acceptable when weighed against the intended clinical benefits. The Risk Management Report is a critical component of the device's technical documentation and regulatory submissions. It typically references the Risk Management Plan, Failure Mode and Effects Analyses (FMEAs), risk-benefit analyses, and post-production monitoring activities. The report must be updated whenever new hazards are identified, design changes are made, or post-market data reveals previously unidentified risks.
