Key Principles
The guidance establishes a predictable and efficient framework for formal interactions between the FDA and sponsors. Its core principle is that timely, high-quality communication is critical to a streamlined drug development process. The document clarifies that different stages of development require different types of meetings (e.g., Type A, B, and C), each with specific timelines and objectives. A key principle is that productive meetings depend on the sponsor providing a comprehensive meeting package in advance, allowing the FDA to prepare and provide substantive feedback.

Recommendations for Sponsors
Sponsors are strongly recommended to engage with the FDA early and throughout the drug development process. To ensure a productive meeting, sponsors should clearly articulate the purpose of the meeting, provide specific questions, and submit a well-organized and complete meeting package by the specified deadline. It is recommended that sponsors carefully consider the type of meeting that is most appropriate for their stage of development and the nature of the questions they have. Following the meeting, sponsors should adhere to the timelines and procedures for submitting meeting minutes for the official record.

Regulatory Considerations
This guidance is a key component of the regulatory framework under the Prescription Drug User Fee Act (PDUFA). Adherence to the procedures outlined in this document is a matter of regulatory compliance. The formal meetings described are a critical part of the Investigational New Drug (IND) and Marketing Authorization Application processes. The meeting process is designed to provide regulatory clarity, reduce the risk of clinical holds or refuse-to-file actions, and ultimately support a more efficient and predictable path to drug approval. The written record of these meetings serves as an important part of the administrative file for a product's development program.

Findings
There is a lack of standardized methodologies for deriving meaningful change thresholds for digital endpoints (DEs).
Challenges exist in identifying DEs that capture the most meaningful concepts to patients.
There is a need for further unification and synergy of efforts in the field, especially given the absence of clear cross-agency regulatory frameworks.

Recommendations
Form multidisciplinary task forces to develop consensus expert guidance recommendations.
Improve transparency and sharing of learnings within the industry.
Engage with regulatory bodies early and frequently throughout the DHT development process.
Use anchor-based methods as the primary approach for deriving meaningful change thresholds.
Ensure DEs reflect concepts that are meaningful to patients.

Regulatory Considerations
Early and frequent engagement with regulators is crucial.
DEs must reflect meaningful patient concepts and be validated early in the development process.
Anchor-based methods are preferred by regulatory authorities for deriving meaningful change thresholds.

Findings
The clinical research ecosystem has longstanding diversity gaps, making targeted DEI strategies essential for equitable healthcare innovation.
Digital tools, including virtual visits, digital outreach campaigns, and AI-driven analytics, can increase access to trials for underrepresented populations.
Real-world data (RWD) and real-world evidence (RWE) help identify diverse participant pools and optimize recruitment strategies.
eConsent and educational resources improve patient engagement and retention by making clinical trials more transparent and accessible.
Trust-building measures, such as community partnerships and patient advocacy collaborations, are critical for long-term success in diversifying clinical trials.

Recommendations
Clinical trial sponsors should integrate digital tools at each stage of trial design to enhance participant diversity and reduce barriers to participation.
AI/ML and real-world data should be leveraged to identify, recruit, and retain diverse patient populations in a data-driven manner.
Digital engagement strategies, including social media outreach and mobile-friendly platforms, should be employed to improve awareness and accessibility.
Transparent communication, including clear eConsent processes and on-demand educational materials, should be prioritized to foster participant trust.
A comprehensive tracking system should be implemented to measure progress on diversity goals, ensuring accountability in clinical trial execution.

Regulatory Considerations
The FDA Diversity Plan requirement should be incorporated into clinical trial planning, with measurable targets for diverse participant inclusion.
Digital tools used for recruitment and engagement must comply with HIPAA, GDPR, and other privacy regulations to protect participant data.
The use of real-world evidence (RWE) in regulatory submissions should be expanded to demonstrate the efficacy of digital recruitment and retention strategies.
Standardized DEI reporting frameworks should be established to ensure regulatory bodies can assess the impact of diversity initiatives in clinical research.
Clinical trials utilizing digital tools should align with decentralized clinical trial (DCT) regulatory guidance to maximize accessibility and equity.

Findings
A need for additional regulatory clarity specific to DHT-derived endpoints.
The official clinical outcome assessment qualification process is impractical for the biopharmaceutical industry.
A lack of comparator clinical endpoints.
A lack of validated DHTs and algorithms for concepts of interest.
A lack of operational support from DHT vendors.

Recommendations
Engage key stakeholders early.
Incorporate DHT-derived endpoints in early-phase trials and observational studies.
Invest in COA development initiatives.
Engage technology manufacturers early in the development process.

Regulatory Considerations
The EMA published a Q&A document on DHT use in clinical trials.
The FDA released guidance on collecting patient data remotely using DHTs.
The FDA established the Digital Health Center of Excellence to facilitate early regulatory engagement.

Findings
There is a need for a structured framework to leverage prior work in the use of DHTs in clinical trials.
The current body of evidence supporting DHTs is growing, but there is a lack of clarity on how to effectively utilize this evidence.
The V3 framework provides a process for validating DHTs, but its application across different medical product development programs is inconsistent.

Recommendations
Implement a framework to reuse analytical and clinical validation data for existing DHTs.
Encourage early and continuous communication with regulatory health authorities.
Leverage prior work to share best practices and consistent approaches in employing DHTs.
Use the V3 framework to ensure DHTs are fit-for-purpose in clinical trials.
Develop a strategic approach to incorporate DHTs and digitally derived endpoints within clinical development programs.

Regulatory Considerations
Sponsors should ensure their plans to leverage prior work are endorsed by regulatory health authorities.
Alignment with FDA guidance on digital health technologies is crucial.
The regulatory status of the DHT and its intended use should be clearly defined and considered in clinical trial applications.

N/A

Findings
AI-DSFs undergo iterative improvements, necessitating a structured framework for modifications to ensure safety and effectiveness.
PCCPs enable manufacturers to streamline modifications by avoiding repeated marketing submissions, reducing regulatory burden.
Critical elements of a PCCP include data management practices, re-training protocols, performance evaluation, and user update procedures.
Comprehensive risk management and transparency are essential to address potential biases and maintain user trust.
Certain modifications, such as those significantly affecting safety or effectiveness, may still require a new marketing submission.

Recommendations
Structure PCCPs with a clear description of planned modifications, a detailed modification protocol, and a robust impact assessment.
Include methods for data collection, re-training, and performance evaluation aligned with quality system regulations.
Specify user update procedures to communicate changes transparently and ensure safe device use.
Address cybersecurity risks and bias mitigation strategies in modification protocols.
Use the FDA Q-Submission Program to discuss PCCPs prior to submitting marketing applications for AI-DSFs.

Regulatory Considerations
Adherence to 21 CFR Part 820 Quality System Regulations, including design controls and risk management.
PCCPs must include modifications that would otherwise require a PMA supplement or new 510(k) submission.
Modifications implemented under PCCPs must conform to FDA-reviewed protocols and be documented in the device master record.
Transparency to users via device labeling updates and public summaries of authorized PCCPs is required.
Modifications outside the scope of an authorized PCCP or deviations from the protocol require new FDA marketing submissions.

Findings
There are gaps in assessing aspects of physical function that matter to patients.
Existing assessment methods have limitations, including their episodic nature and burden to patients.
There are currently no approved drugs in the United States for the treatment of cancer cachexia.

Recommendations
Develop and validate digital measures of health.
Ensure digital measures are meaningful to patients.
Qualify digital measures for use in clinical development and regulatory decision-making.

Regulatory Considerations
Qualification of digital measures as drug development tools is necessary.
Digital measures are gaining traction in regulatory decision-making.
The FDA recommends qualification of digital measures in their PFDD guidelines."

Findings
OTS software introduces unique risks due to its general-purpose design and lack of lifecycle control by medical device manufacturers.
Comprehensive testing and risk management are essential to mitigate safety hazards associated with OTS software in medical devices.
Regular updates and maintenance are critical for managing obsolescence and ensuring long-term safety and effectiveness of OTS components.
Networking and interoperability of OTS software pose additional risks related to data integrity, cybersecurity, and scalability.
Enhanced documentation is required for high-risk devices incorporating OTS software, especially those involving AI or ML functionalities.

Recommendations
Provide comprehensive descriptions of OTS software, including version details and system specifications.
Conduct thorough risk assessments and include mitigation plans in premarket submissions.
Perform rigorous testing, including integration and regression testing, for OTS software components.
Establish mechanisms for continued maintenance, support, and version control of OTS software.
Ensure that device labeling includes warnings and specifications related to OTS software compatibility and restrictions.

Regulatory Considerations
Adherence to 21 CFR Part 820 Quality System regulations, including design controls and purchasing controls for OTS software.
Submission of a risk management file and traceability documentation linking risks, design requirements, and testing outcomes.
Compliance with premarket submission requirements, including 510(k), IDE, and PMA applications, as applicable.
Use of device labeling to communicate hardware and software compatibility and restrictions to users.
Development of beta testing and investigational plans for clinical studies involving OTS software.

Key objectives of the initiative include:
Enhancing patient engagement and experience in clinical trials
Providing practical guidance for implementing patient-facing technologies
Addressing regulatory considerations and challenges
Facilitating collaboration among sponsors, sites, patients, and technology vendors

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
COA-based endpoints should reflect meaningful patient health aspects and support clear treatment effect inferences.
Selection of endpoints requires a well-supported rationale, including evidence of their importance to patients.
Use of MSD and MSR approaches enhances the interpretation of treatment effects by linking COA scores to meaningful patient experiences. Proper anchors (e.g., global impression of severity) are essential for validating these approaches.
Frequency and timing of COA data collection must align with disease characteristics and study objectives.
Adjustments for potential practice effects and assistive device use are critical for robust outcome measurement.
Proper handling of missing data and sensitivity analyses ensure valid conclusions from COA-based endpoints.
Continuous, ordinal, and dichotomized endpoints require tailored statistical methods for analysis.
Early engagement with the FDA is crucial for aligning study designs and COA approaches with regulatory expectations.

Recommendations
Engage patients and caregivers early to identify meaningful endpoints and assess potential barriers to COA use.
Use anchor-based methods to validate COA scores and define meaningful thresholds for interpretation.
Develop and pilot test study protocols to ensure COA reliability, usability, and alignment with regulatory requirements.
Implement strategies to reduce participant burden, such as concise COA instruments and patient-friendly data collection methods.
Submit comprehensive documentation, including endpoint justification and scoring rationale, to FDA for feedback before trial initiation.

Regulatory Considerations
Endpoints must be supported by evidence of their fit-for-purpose status and alignment with the trial’s objectives.
COAs used in digital or adaptive formats must meet FDA’s standards for usability and data integrity.
Trials with nonrandomized designs require robust measures to mitigate bias in COA-based endpoint analysis.
Thresholds for MSD or MSR must be prespecified and justified with empirical evidence.
Sponsors must follow FDA guidance for submitting COA-based data, ensuring compliance with electronic data standards.