Findings
Pre-Submissions (Pre-Subs) allow submitters to obtain FDA feedback on specific questions before submitting formal IDEs, 510(k)s, PMAs, or other applications. Early feedback can improve submission quality and streamline the review process.
Submission Issue Requests (SIRs) provide a mechanism for addressing issues raised in FDA hold letters (e.g., 510(k) deficiencies) to help expedite resolutions.
Study Risk Determinations help sponsors clarify whether clinical studies are significant risk (SR), non-significant risk (NSR), or exempt from IDE regulations.
Informational Meetings are non-feedback sessions aimed at familiarizing FDA staff with new devices or sharing updates on ongoing development.
The program encourages timely submissions, including supplements for ongoing discussions and amendments to update materials.

Recommendations
Clearly define the purpose and goals of the Q-Sub in the submission to facilitate effective FDA review.
Include specific, well-formulated questions that focus on a limited number of topics to ensure actionable feedback.
For Pre-Subs, align planned testing and submissions with FDA guidance and include detailed device descriptions, testing protocols, and relevant background information.
Use SIRs to discuss proposed solutions to deficiencies raised in FDA hold letters, focusing on timely resolution.
Draft and submit meeting minutes promptly (within 15 days of meetings) to ensure accurate documentation of FDA feedback.

Regulatory Considerations
Submitters should adhere to the timelines specified for different Q-Sub types, including 70 days for Pre-Sub feedback or 21 days for SIRs submitted promptly after a hold letter.
Q-Subs should include all relevant regulatory history and references to prior FDA communications to streamline the review process.
FDA feedback through the Q-Sub program is non-binding and based on the information available at the time; subsequent submissions must align with the provided feedback to maintain consistency.
Informational Meeting requests should clearly state that feedback is not expected and may be used to track interactions outside other formal Q-Sub types.
Confidentiality of Q-Subs is maintained in compliance with FDA’s disclosure regulations and the Freedom of Information Act (FOIA).

Findings
Quantitative imaging extracts numerical values from medical data that are subject to systematic error and random variation. The utility of these values depends on well-characterized performance and sufficient user information for interpretation. Performance specifications often change throughout the operating range of a device, such as volumetric reproducibility varying by structure size. Fully automated functions require more robust analytical validation than manual or semi-automated functions because they lack the opportunity for expert user correction. While phantoms serve as high-quality reference standards for ground truth, they are simplifications that may not fully reflect clinical performance.

Recommendations
Manufacturers should provide a detailed technical description of the quantitative imaging function, including the measurand, algorithm training paradigms, and level of automation. Performance specifications should incorporate objective reference values when available to allow for comparisons between subject and predicate devices. A sensitivity analysis should be conducted to determine the impact of sources of error like patient characteristics, image acquisition protocols, and image processing. Labeling must include clear instructions for user-performed quality assurance and specify any limitations where the function has been found ineffective. For automated devices, manufacturers should help users understand scenarios where the function might generate an incorrect output that is not easily identifiable.

Regulatory Considerations
The FDA recommends following a ten-step technical performance assessment process, ranging from defining the measurand to comparing statistical results against pre-defined acceptance criteria. Premarket submissions should include performance data demonstrating that the device meets claims regarding bias, precision, linearity, and limits of quantitation. Uncertainty should be reported in units of the measurand and cover the entire operating range of the function. Manufacturers are encouraged to use the Q-Submission process to address questions regarding regulatory status or specific requirements. Software implementation details should align with existing FDA guidance for the content of premarket software documentation.

Findings
FDA requires OUS clinical investigations to comply with GCP, ensuring the credibility and accuracy of data and protecting human subjects.
Statements on GCP compliance and supporting information are mandatory for OUS data submissions.
Waivers are permitted in circumstances where GCP compliance is unattainable or where local regulations differ significantly from FDA requirements.
Investigations must demonstrate that OUS data are applicable to U.S. populations and medical practices.
Sponsors must provide robust documentation, including investigator qualifications, site descriptions, IEC reviews, and informed consent processes.

Recommendations
Ensure clinical investigations adhere to GCP standards, including IEC review and informed consent, for all OUS clinical data submitted to FDA.
Include detailed supporting information in submissions, such as investigator qualifications, facility descriptions, protocols, and data summaries.
Clearly identify any deviations from GCP and justify how data integrity and subject protection were maintained.
Use FDA’s Pre-Submission Program to discuss potential challenges with GCP compliance or data validation before submission.
Retain all required records for at least two years after FDA’s decision on the application or submission.

Regulatory Considerations
FDA evaluates OUS clinical data on a case-by-case basis, considering the adequacy of GCP compliance and supporting documentation.
For significant risk device investigations, sponsors must provide the most comprehensive documentation, while non-significant risk and exempt devices require less detailed information.
Waivers may be granted when justified by public health considerations or when local laws prohibit compliance with specific FDA requirements.
FDA retains the right to inspect clinical sites or review source documents to validate data integrity and compliance with GCP.
Sponsors must ensure that OUS data are valid and relevant to the U.S. population and medical practice.

Findings
RF wireless technologies in medical devices must account for crowded RF environments, coexistence issues, and risks associated with data loss, interference, and security breaches.
The quality of wireless signals (QoS) is critical for devices with time-sensitive or critical functionalities, such as alarms and life-support systems.
Electromagnetic compatibility (EMC) testing must address both emissions and immunity, ensuring devices can operate safely in shared RF environments.
Device labeling must inform users about potential interference, wireless security measures, and operating limitations in specific environments.
Postmarket risk management must address failure trends related to RF wireless performance, incorporating corrective and preventive actions to maintain safety.

Recommendations
Design Considerations: Use risk management practices to evaluate wireless technologies and determine appropriate risk mitigation strategies.
Limit RF output power to the minimum necessary to ensure functionality and reduce interference risks.
Testing and Validation: Conduct coexistence testing to evaluate performance in environments with other RF systems.
Perform EMC immunity testing under real-world operating conditions.
Security Measures: Implement encryption and authentication protocols to protect against unauthorized access.
Disable automatic connection modes (e.g., Bluetooth™ discovery) for safety-critical applications.
Premarket Submissions: Include a detailed description of the device’s wireless functions, risk mitigations, and testing protocols.
Summarize test results, including coexistence, EMC, and security assessments.
Labeling and User Instructions: Provide clear guidance on device setup, operation, and troubleshooting.
Include warnings about potential RF interference and instructions for maintaining signal quality and security.

Regulatory Considerations
Premarket submissions must include a description of the wireless technology, its intended use, and test data demonstrating compliance with standards.
EMC testing must conform to recognized consensus standards, such as IEC 60601-1-2, with modifications to address wireless technology.
FDA requires labeling to include information on operating frequencies, effective radiated power, and mitigation strategies for coexistence and security.
Postmarket risk management must analyze failure trends and implement corrective actions to address RF-related performance issues.
Compliance with Federal Communications Commission (FCC) regulations, including frequency band allocation and RF emission limits, is mandatory.