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.

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
Early and ongoing engagement with regulatory bodies is essential to align endpoint development with regulatory expectations.
There are distinct pathways for drugs and medical devices, with specific meeting types (e.g., Type B and Type C meetings) available for each.
Qualification programs help establish the utility and validity of digitally-derived endpoints across different drugs, devices, or diseases.
Regulatory agencies provide detailed feedback on analytical and clinical validation, ensuring endpoints meet clinical relevance and reliability standards.
The document emphasizes the importance of understanding and navigating distinct regulatory frameworks (e.g., IND/NDA for drugs and IDE/510(k) for devices).

Recommendations
Engage with regulatory bodies, such as the FDA and EMA, early in the development process to obtain critical input.
Utilize structured programs, like the Drug Development Tool (DDT) and Medical Device Development Tools (MDDT) qualification pathways, to validate endpoints.
Schedule appropriate regulatory meetings, including Type B and Type C meetings for drugs or Q-Submission and Agreement Meetings for devices.
Consider utilizing general advisory sessions (e.g., Critical Path Innovation Meetings or Innovation Task Force Briefings) to enhance endpoint development strategies.
Document and align endpoint development with regulatory frameworks, ensuring compliance with safety, efficacy, and performance standards.

Regulatory Considerations
Use FDA’s IND/NDA and IDE/510(k) pathways for endpoint validation, tailoring engagement to the specific type of medical product.
Schedule Type B and Type C meetings for focused discussions on endpoint development, including context of use and validation.
Engage with EMA through pre-submission meetings for scientific advice, ensuring endpoints meet requirements for clinical relevance and robustness.
Leverage qualification advice meetings with EMA for methodologies applicable across multiple products or diseases.
Seek assistance from regulatory initiatives, such as the FDA’s Digital Health Center of Excellence or EMA’s Qualification Advice Programs, for specialized guidance.

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
Software changes must be assessed for potential impacts on the safety and effectiveness of the device, even if they are routine updates.
A risk-based assessment is required to determine whether changes introduce new risks, modify existing risks, or necessitate new risk controls.
Cybersecurity updates, routine maintenance changes, and minor clarifications may not require a new 510(k) if they do not affect performance specifications or safety.
Substantial modifications, such as adding new algorithms, introducing new functionalities, or modifying clinical performance, generally require a new 510(k).
Manufacturers must document all changes, even those not requiring a new 510(k), in compliance with QS regulations.

Recommendations
Use the provided flowchart and guiding principles to evaluate whether software changes exceed the regulatory threshold for submission of a new 510(k).
Conduct a risk-based assessment for all changes, focusing on new or modified risks and the adequacy of existing risk controls.
Verify and validate changes to ensure they meet device specifications and do not introduce unintended consequences.
Submit a new 510(k) for changes that significantly affect clinical functionality, performance specifications, or introduce new risks that are not mitigated.
Maintain detailed documentation of all decisions regarding software changes, including rationale for whether submission of a new 510(k) was required.

Regulatory Considerations
Submission of a new 510(k) is required for changes that could significantly impact the safety or effectiveness of a device or constitute a major modification to its intended use.
Cybersecurity updates generally do not require a new 510(k) if they solely strengthen security without affecting device performance.
Manufacturers must evaluate cumulative changes and submit a new 510(k) if the combined impact exceeds the regulatory threshold.
Device software changes involving substantial algorithm modifications or system architecture updates are likely to require a new 510(k).
Changes that address compliance during a recall or correction must be evaluated under FDA's guidance for recalls and device enhancements.

Findings
An accessory is defined as a finished device that supports, supplements, or augments the performance of a parent device.
Accessories are classified based on their individual risk profiles when used with parent devices, which may differ from the classification of the parent device.
The De Novo process can be used for new accessory types with no existing classification, enabling lower-risk accessories to be classified in Class I or II.
Articles not specifically intended for use with a medical device (e.g., generic batteries or monitors) are not considered accessories unless labeled or promoted for such use.
FDA encourages using pre-submission requests to obtain feedback before submitting Accessory Requests or De Novo classifications.

Recommendations
Determine whether an article qualifies as an accessory by evaluating its intended use with a parent device based on labeling and promotional materials.
Evaluate the risks associated with the accessory when used as intended with its parent device, considering both unique and parent-related risks.
Use the Accessory Request process for new or existing accessories to propose appropriate classifications, supported by evidence of risk profiles and proposed regulatory controls.
Submit De Novo requests for new accessory types lacking existing classifications, providing data on performance, risks, and mitigation measures.
Include clear and comprehensive labeling for accessories, specifying compatibility and performance with identified parent devices.

Regulatory Considerations
Classification of accessories should reflect their risks and required controls, independent of their parent device classification.
Accessories categorized as Software as a Medical Device (SaMD) must meet the same risk-based classification framework applied to other medical devices.
Manufacturers can request reclassification or exemption from 510(k) requirements for previously classified accessories through applicable FDA mechanisms.
FDA must respond to Accessory Requests for existing accessory types within 85 days and De Novo requests within 120 days, as specified in the FD&C Act.
The Paperwork Reduction Act governs the submission of accessory classification requests, requiring compliance with established timelines and documentation requirements.