Findings
There is widespread confusion among digital health developers regarding the complex and evolving regulatory landscape, with many uncertain about whether their products require regulation or which pathway to pursue. This lack of a clear regulatory strategy acts as a significant barrier to market access, investor confidence, and user trust. The heterogeneity of the digital health sector, coupled with varying international requirements, further complicates the path to market for innovators, hindering the scalability of effective solutions.

Recommendations
Digital health innovators should proactively integrate a tailored regulatory strategy into their core business plan, viewing it as a commercial differentiator rather than a hurdle. Developers are encouraged to utilize resources like DiMe’s regulatory pathway tools to navigate the U.S. and global landscapes effectively. Early and continuous engagement with regulators and collaborative efforts across the industry are essential to ensure products are developed to meet both market needs and regulatory standards, ultimately accelerating the delivery of high-quality digital health solutions to patients.

Regulatory Considerations
A comprehensive policy framework is necessary for the successful integration of digital health technologies, encompassing regulatory authorization, value assessment, and reimbursement. Developers must understand the nuances of different regulatory classifications, such as Software as a Medical Device (SaMD), and their specific evidentiary requirements. Greater international harmonization of regulatory standards is crucial for enabling global scalability. Regulatory bodies should continue to develop agile frameworks that can accommodate the rapid pace of innovation in digital health while ensuring patient safety and product effectiveness.

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
There are various formal and informal engagement pathways available for developers of Digital Health Products and Combination Products to communicate with the FDA to seek advice regarding product classification, regulatory status, and submission strategies. Informal pathways include the Digital Health Inquiry (via the Digital Health Inbox), the DICE Mailbox Inquiry, and the Pre-RFD Process, which provide non-binding feedback. Formal pathways include the 513(g) Program for classification, and the Q-Submission Program (encompassing Pre-Submissions for pre-application feedback and SRD for risk determination).

Recommendations
Manufacturers should use the provided map to determine the appropriate pathway based on their product type (standalone digital health or combination product) and the type of advice they are seeking (informal or formal). The Pre-Submission (Pre-Sub) program is recommended as an opportunity to obtain formal feedback "prior" to submitting an application, particularly if a new product's regulatory pathway is unclear or if planning a study to support a future application. Combination Product manufacturers can use CPAMs to clarify marketing authorization standards or post-market modification requirements.

Regulatory Considerations
The 513(g) Request provides information on a product's classification and applicable regulatory requirements but does not determine substantial equivalence or make final marketing authorization decisions. Programs like the CDRH-Payor Connection and Parallel Review with CMS are voluntary and designed to expedite patient access by aligning clinical evidence for both regulatory clearance/approval and coverage decisions. Participation in these programs, however, does not alter the FDA’s existing, separate standards for regulatory review.