Findings
Collaborative Communities are sustained, multi-stakeholder forums (including patients, industry, academia, and the FDA) dedicated to solving shared challenges in the medical device ecosystem. These communities are not intended to replace formal regulatory mechanisms. They are equipped to perform activities such as:
Developing best practices and strategies.
Generating and evaluating evidence to support novel approaches.
Clarifying ill-defined challenges and generating consensus on definitions.
Addressing issues related to product quality and safety.

Recommendations
The FDA/CDRH does not establish or fund these communities. Instead, the FDA recommends that interested stakeholders convene and lead these groups. The FDA reviews opportunities on a case-by-case basis for participation, considering:
The community's potential public health impact.
Alignment with the CDRH mission, priorities, and resources.
The existence of a formal governance structure, a convener, a plan to measure success, and a mechanism for sustained engagement.

Regulatory Considerations
The FDA's participation in these communities is a strategic priority for advancing regulatory science and fostering responsible medical device innovation. Examples of digital health-related collaborations include those focused on AI/ML, Digital Biomarkers, Digital Health Technologies (DHTs), and Real-World Data (RWD). The outcomes developed by these groups can inform and accelerate the development of science-based solutions to policy and scientific challenges.

Findings
Regulatory Acceptance is Complex: Gaining regulatory acceptance for endpoints derived from Digital Health Technologies (DHTs) is a lengthy, multifaceted, and costly process that requires a global strategy and early health authority consultation.
"Fit-for-Purpose" is Key: A DHT's clearance or approval as a medical device does not automatically ensure it is fit-for-purpose in a clinical trial; its intended use must align with the specific context of use (COU) in the study.
Meaningfulness is a Hurdle: Demonstrating the clinical meaningfulness of novel digital endpoints, especially for abstract concepts like cognitive decline in Alzheimer's Disease, remains a significant challenge for regulatory acceptance.
International Harmonization is Lacking: Differences in regulatory requirements for DHT validation between major health authorities can delay or prevent the successful implementation of digital measures in global clinical trials.
Technology Changes Pose Risks: Software and hardware updates to DHTs during a clinical trial can have significant implications, potentially invalidating study results if not managed through a predetermined change-control plan.

Recommendations
Engage Health Authorities Early and Often: Sponsors should conduct multiple consultations with major health authorities (e.g., FDA, EMA) early in the development process to align on the Concept of Interest (COI), COU, and the validation roadmap.
Develop a Comprehensive Regulatory Strategy: A global regulatory strategy should be an integral part of the overall development plan, tailored to the program's objectives and endpoint hierarchy.
Establish "Fit-for-Purpose" Criteria: Before selecting a DHT, sponsors should establish the minimum technical and performance specifications required for the specific COU to guide the selection of a fit-for-purpose device.
Create a Conceptual Framework: For novel endpoints, sponsors should develop a conceptual framework that visualizes how the DHT-derived measure relates to meaningful health concepts and patient experiences.
Plan for Change and Missing Data: Sponsors should establish predetermined change-control plans with manufacturers to manage DHT updates and create risk management plans to minimize and handle missing data from remote acquisition.

Regulatory Considerations
Distinct Pathways in US vs. EU: The US FDA uses a risk-based approach for DHTs that are medical devices, while in Europe, CE marking for the intended COU is generally expected by the EMA.
Qualification is an Option, Not a Requirement: Both the FDA and EMA offer voluntary qualification programs for Drug Development Tools (DDTs), which can validate a DHT for a specific COU across multiple drug programs, though the process is resource-intensive.
Scientific Advice for Individual Programs: For DHTs used within a single drug development program, engaging with health authorities through scientific advice meetings is a more targeted and confidential pathway for gaining feedback and agreement.
Data Privacy and Security are Paramount: Sponsors must ensure that the collection, transfer, and storage of personal data via DHTs comply with all applicable regulations, such as GDPR in the EU, including cybersecurity and data transfer measures.

Findings
Regulatory inconsistencies across different FDA divisions and international jurisdictions create inefficiencies in the approval process for digital health products.
Lack of alignment between regulatory approval and payer reimbursement requirements poses a significant barrier to commercialization and widespread adoption of digital health innovations.
There are limited regulatory pathways for novel digital health products, including AI-enabled solutions, requiring new frameworks to address iterative software development and real-world data integration.
Existing health technology assessment (HTA) models do not fully accommodate digital health technologies, limiting their inclusion in reimbursement decisions.
Industry stakeholders emphasize the need for clearer guidelines on cloud-based infrastructure, third-party AI model validation, and digital health interoperability.

Recommendations
FDA and international regulatory bodies should improve coordination to establish standardized approval processes and consistent clinical evidence requirements.
New regulatory pathways should be introduced for AI-driven and software-based digital health products, considering their unique lifecycle and iterative development models.
Greater transparency and communication between FDA divisions should be established to ensure consistent decision-making and regulatory interpretations across centers.
Policymakers should prioritize payer alignment strategies, incorporating real-world evidence (RWE) to streamline reimbursement and market access processes.
The digital health industry should collaborate with regulators to create standardized best practices for AI validation, cloud security, and digital biomarker evaluation.

Regulatory Considerations
FDA should clarify the evidentiary standards for AI-enabled medical devices and establish predefined change control plans for software updates.
Digital health products should adhere to globally recognized standards such as HL7 for interoperability and ISO regulations for data security.
Market access pathways must integrate pricing and reimbursement considerations to facilitate the commercial viability of digital health technologies.
The use of real-world data (RWD) should be expanded in regulatory decision-making, supporting the approval and post-market surveillance of digital health innovations.
Regulatory frameworks should be updated to accommodate cloud-based health platforms, addressing issues such as data privacy, operational security, and compliance with HIPAA and GDPR.

Findings
There is a lack of alignment in concepts, definitions, and terminology related to digital health technologies, which hinders global drug development programs.
Different regulatory agencies interpret common terms like "monitoring" differently, leading to confusion and inconsistency.
The classification of digital measures impacts evidentiary requirements and regulatory acceptance, but detailed guidance on these requirements is lacking.

Recommendations
Align terminology and definitions across stakeholders to ensure consistency in understanding and communication.
Reuse existing terms where possible to avoid unnecessary complexity.
Focus on what is measured rather than how it is measured to streamline regulatory processes.
Encourage companies and regulators to reflect on and adopt a common lexicon within their organizations.
Move quickly to address critical questions about evidence needed for validation of digital measures.

Regulatory Considerations
Regulatory authorities should apply consistent standards for all endpoints, regardless of data acquisition methods.
The classification of DHTs as medical devices or not will impact their regulatory pathway and requirements.
There is a need for dialogue with regulators to clarify source data requirements for data acquired by DHTs.

Findings
Regulatory frameworks differ across regions, with the FDA focusing on digital health technologies and the EU emphasizing digital methodologies under MDR.
Determining whether a DHT qualifies as a medical device depends on its intended use and functionality, necessitating region-specific evaluations.
Health authority engagement can occur through FDA pathways like Critical Path Innovation Meetings (CPIM) and EMA’s Innovation Task Force (ITF).
Verification and validation of DHTs are crucial to ensure reliability and compliance with regulatory requirements in clinical trials.
Cybersecurity and compliance with privacy laws, such as GDPR, are mandatory considerations for DHT implementation.

Recommendations
Engage Regulators Early: Utilize FDA, EMA, or MHRA pathways (e.g., CPIM, ITF) during early development to align on requirements and mitigate risks.
Conduct thorough assessments to determine if a DHT qualifies as a medical device under regional regulations.
Implement robust validation and verification processes to confirm that DHTs are fit-for-purpose in clinical investigations.
Ensure compliance with GDPR, HIPAA, and other relevant data protection standards to safeguard patient information.
Adhere to GCP guidelines, including the ALCOA+ principles, to maintain data credibility and patient safety throughout the trial.

Regulatory Considerations
FDA Regulations: Evaluate DHTs under the FDA’s framework for medical devices, including exemptions under 21 CFR Part 812 and the Digital Health Software Precertification Program.
EU MDR/IVDR: Comply with MDR for medical devices and IVDR for in-vitro diagnostics, ensuring alignment with Annex VIII for software classification.
UK MHRA Guidance: Reference MHRA’s flowcharts for determining if a software qualifies as a medical device and ensure compliance with UK-specific regulatory requirements.
Global Harmonization Efforts: Consider global standards, such as ICH E6 (R2) and GHTF/IMDRF guidelines, to align multinational clinical trials.
Leverage pathways like EMA’s qualification process for novel methodologies and FDA’s DDT qualification program for broader acceptance of digital endpoints.

Findings
The QS regulation under 21 CFR Part 820 has been effective but requires updates to align with global standards like ISO 13485.
Adopting ISO 13485 will harmonize FDA requirements with international practices, benefiting manufacturers that sell devices globally.
FDA’s proposed amendments retain some unique provisions to ensure alignment with the Federal Food, Drug, and Cosmetic Act (FD&C Act).
The incorporation of risk management principles throughout the product lifecycle is more explicit in ISO 13485 than in the current QS regulation.
The proposed changes are expected to reduce regulatory burdens and enhance device quality and accessibility.

Recommendations
Align quality management systems with ISO 13485 to ensure compliance with both U.S. and international regulatory requirements.
Establish documentation processes that meet FDA’s additional requirements, such as those for traceability and complaint handling.
Incorporate risk management throughout the device lifecycle, as emphasized in ISO 13485.
Manufacturers should train personnel and update their systems to comply with the new requirements within the proposed one-year transition period.
Provide comments on the proposed rule to FDA before the deadline to address any potential concerns or suggestions for improvement.

Regulatory Considerations
The proposed rule incorporates ISO 13485:2016 by reference and aligns FDA’s QS regulation with international QMS standards.
FDA-specific requirements include:
Traceability for certain life-supporting devices.
Documentation of unique device identifiers (UDI) in compliance with FDA’s regulations.
Complaint handling and servicing records that meet FDA standards.
FDA inspections will not issue ISO 13485 certifications but will assess compliance with the proposed Quality Management System Regulation (QMSR).
Manufacturers must continue to comply with existing FDA regulations where conflicts with ISO 13485 arise.

Findings
Traditional on-site monitoring, which often involves 100% source data verification, is not the most effective way to ensure data quality and can divert resources from more critical activities. A risk-based approach allows for the early identification of potential issues, enabling proactive risk mitigation and improved trial oversight. The successful implementation of RBM requires a cultural shift within organizations, moving from a reactive to a proactive mindset. Collaboration among sponsors, CROs, and sites is essential for the effective adoption of RBM methodologies.

Recommendations
Sponsors should adopt a systematic, risk-based approach to monitoring that is tailored to the specific risks of their clinical trial. This includes conducting a thorough risk assessment during the planning phase to identify critical data and processes. The use of centralized monitoring and advanced analytics should be a core component of any RBM strategy to detect unusual patterns or trends in the data. Training for all stakeholders, including site staff and monitors, is crucial for the successful implementation of RBM.

Regulatory Considerations
Global regulatory agencies, including the FDA, EMA, and Japan's PMDA, have issued guidance that supports and encourages the use of risk-based approaches to monitoring clinical trials. Regulatory submissions should include a description of the RBM methodology used in the trial and a justification for the approach taken. The adoption of RBM is consistent with Good Clinical Practice (GCP) principles, which emphasize a focus on patient safety and data quality.