Findings
Patient experience data provides critical context for regulatory review by illuminating disease burden, unmet medical needs, and the aspects of a condition that matter most to patients.
A systematic approach is necessary to ensure patient experience data is robust enough for regulatory consideration, moving beyond anecdotal evidence to scientifically rigorous data collection.
Early engagement between sponsors and the FDA is a key factor for successfully incorporating patient perspectives into a drug development program.
The value of patient-reported outcomes (PROs) and other clinical outcome assessments (COAs) is highly context-dependent, varying significantly across different diseases and patient populations.

Recommendations
Drug sponsors should leverage the FDA's meeting process to discuss their strategies for collecting and submitting patient experience data early in the development lifecycle.
Sponsors should utilize the repository of meeting reports as a learning resource to understand best practices and common challenges in patient-focused drug development for specific conditions.
Patient advocacy groups should actively participate in these discussions to ensure the full spectrum of patient experiences is captured and communicated to both regulators and developers.
Researchers should develop and validate novel tools and methodologies for capturing and analyzing patient experience data that are meaningful for both clinical and regulatory purposes.

Regulatory Considerations
Patient experience data is a key component of the benefit-risk assessment, providing evidence that can inform regulatory decisions regarding a drug's approval and labeling.
The FDA's review of patient experience data is guided by a commitment to patient-focused drug development, as mandated by the 21st Century Cures Act and supported by user fee agreements like PDUFA.
The scientific rigor of data collection and analysis is paramount; for patient experience data to be influential, it must meet high standards of validity and reliability.
Transparency is a core principle, and the publication of these meeting reports is intended to provide clear examples of how patient input can be effectively integrated into regulatory submissions.

Key Principles (Findings)
The central principle of the DDT Qualification Programs is to create a formal pathway for the FDA to conclude that a specific tool is well-suited for a particular Context of Use (COU) in drug development. A key finding, as reflected in the program's design, is that qualification de-risks drug development by allowing a tool to be used in any regulatory submission for its qualified COU without needing to be re-validated each time. The program is designed to foster stakeholder collaboration, encouraging the development of tools that can benefit the entire research community, thereby reducing the burden on individual sponsors.

Program Activities (Recommendations)
The structure of the DDT programs serves as a series of recommendations for tool developers:
Engage Early and Collaboratively: The programs are designed to provide a framework for early and ongoing scientific collaboration with the FDA to facilitate the development of new tools.
Follow a Staged Process: Developers are guided through a multi-stage process, typically involving a Letter of Intent, a Qualification Plan, and a Full Qualification Package, to systematically build the evidence needed for qualification.
Seek Public Qualification: The ultimate recommendation is to achieve public qualification for a DDT, which makes the tool available for broad use and integrates it into the regulatory review process, expediting future drug development.

Regulatory Considerations
The DDT Qualification Programs are a formal regulatory framework established under the 21st Century Cures Act. A "qualified" DDT has a specific regulatory status; it can be relied upon to have a specific interpretation and application in drug development and regulatory review for its stated Context of Use (COU). This qualification is publicly available and allows the tool to be included in Investigational New Drug (IND), New Drug Application (NDA), or Biologics License Application (BLA) submissions without the FDA needing to reconsider its suitability. This creates a more efficient and predictable regulatory compliance pathway for sponsors who use the qualified tool.

Findings
Diverse Pathways to Market Exist: The case studies demonstrate there is no single "right" way to approach the FDA; successful strategies are highly varied and include De Novo requests, 510(k) clearances, and leveraging established pathways for new indications.
Early FDA Engagement is Crucial: A consistent theme across the successful case studies is the value of engaging with the FDA early and often. This collaborative approach helps de-risk the development process, clarify evidentiary requirements, and build trust.
"Drug-like" Evidence Can Be a Differentiator: For novel software-based interventions, particularly digital therapeutics, generating a robust body of evidence similar to that of a pharmaceutical (i.e., randomized controlled trials) is a key strategy for gaining regulatory and commercial success.
Platform-Based Approaches are Emerging: Companies are finding success by moving from single-product solutions to integrated platforms that can monitor multiple health aspects, which requires a more holistic regulatory strategy.

Recommendations
Leverage Pre-Submission (Pre-Sub) Meetings: Sponsors are strongly encouraged to use the Q-Submission program to gain valuable, early feedback from the FDA on their validation plans and overall regulatory strategy.
Build a Multi-faceted Commercialization Plan: Regulatory clearance is only one step. The case studies recommend developing a comprehensive strategy that considers market access, reimbursement, and payer engagement from the outset.
Address Underserved Markets: The examples highlight opportunities for innovation in underserved areas, such as pediatrics and behavioral health, where DHTs can fill significant gaps in care.
Innovate on Evidence Generation: Sponsors should be prepared to innovate not just in their technology, but also in their approach to clinical evidence, tailoring their trial designs to best demonstrate the unique value of their digital product.

Regulatory Considerations
Understand the Risk Classification: The regulatory pathway for a DHT is determined by its intended use and associated risk level. Sponsors must correctly classify their device to determine if a 510(k), De Novo, or other pathway is appropriate.
AI/ML Devices Have Unique Needs: For products incorporating artificial intelligence or machine learning, sponsors must address specific regulatory considerations, such as predetermined change control plans (PCCPs), to manage algorithm updates post-market.
Interoperability is a Key Factor: For devices intended to be part of a connected health ecosystem (e.g., automated insulin dosing systems), demonstrating interoperability and cybersecurity is a critical component of the regulatory submission.

Findings
Product development firms are hesitant to increase DHT use despite regulatory support.
Conventional hardware-based technologies are preferred over newer digital tools.
Operational barriers contribute to the low adoption of DHTs in product development trials.

Recommendations
Reduce operational barriers to facilitate DHT adoption.
Provide additional regulatory clarity to encourage DHT use.
Encourage the incorporation of more DHTs and patient-centric endpoints in clinical trials.

Regulatory Considerations
The FDA's guidance on DHT use is evolving and not yet fully formalized.
There is a need for harmonization between US and non-US regulatory agencies.
The impact of recent regulatory support may take years to be fully realized.

Findings
A proactive risk assessment is essential for optimizing study quality by identifying and mitigating risks to human subject protection and data integrity before and during a trial. Monitoring should be comprehensive, addressing not only likely risks identified initially but also less probable, high-impact risks and unanticipated issues that emerge. The effectiveness of a monitoring strategy depends on tailoring its timing, frequency, and methods to study-specific factors like complexity and site experience. Centralized monitoring, as part of a risk-based approach, can detect systemic issues like data omissions or protocol deviations more rapidly than traditional on-site visits alone.

Recommendations
Sponsors should formally document their risk assessment methodologies and ensure these assessments directly inform the creation and revision of monitoring plans. Monitoring plans must be detailed, outlining the study design, specific data sampling strategies, and clear protocols for escalating significant issues. When significant problems are identified, sponsors must conduct a timely root cause analysis and implement corrective and preventive actions. All monitoring activities, findings, and subsequent actions should be thoroughly documented and communicated to sponsor management, clinical site staff, and other relevant parties.

Regulatory Considerations
FDA regulations mandate sponsor oversight and proper monitoring but do not prescribe specific methods, providing the flexibility for sponsors to adopt a risk-based approach. The FDA may request a sponsor's risk assessment and monitoring plan documentation during an inspection. This guidance represents the Agency's current thinking and is nonbinding, allowing sponsors to use alternative approaches if they satisfy regulatory requirements. A key focus of monitoring should be to ensure critical trial processes, such as the maintenance of blinding, are protected to maintain overall data and trial integrity.

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
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.

Key Principles (Findings)
The core principle of the Critical Path Innovation Meeting (CPIM) program is that early, non-binding communication between the FDA and innovators can accelerate the development of new Drug Development Tools (DDTs). The program is designed to be a collaborative, scientific discussion, not a formal regulatory review of a specific product. A key finding from the program's existence is that a dedicated forum to discuss emerging science—outside the context of a specific drug application—is critical for advancing regulatory science and modernizing the drug development process.

Recommendations for Stakeholders
The program implicitly recommends that innovators (from industry, academia, etc.) proactively seek the FDA's perspective on novel methodologies and technologies. Stakeholders are encouraged to request a CPIM to discuss potential biomarkers, novel clinical outcome assessments (COAs), innovative clinical trial designs, and other new tools. The goal is for sponsors to gain a better understanding of the FDA's thinking on a particular topic, which can help guide their development efforts and de-risk future regulatory submissions.

Regulatory Considerations
A CPIM is an informal, non-binding scientific discussion and does not replace formal regulatory meetings like pre-IND or End-of-Phase meetings. The advice provided by the FDA during a CPIM does not constitute a regulatory decision or a commitment for a future approval pathway. The program is part of the FDA's broader "Critical Path Initiative" and is intended to promote innovation by enhancing communication. Any outcomes or suggestions from a CPIM are for informational purposes to help guide the development of novel tools and approaches.

Findings
Novel digitally-derived endpoints can provide more reliable data, increase trial efficiency, and enhance patient centricity.
Selecting appropriate outcome measures that are meaningful to patients and clinicians is critical to success.
Developing these endpoints requires a resource-intensive, systematic approach to meet stakeholder needs.
Demonstrating validity and utility of novel endpoints poses unique challenges, especially for new measures without established validation standards.
Sharing lessons learned and promoting transparency can advance the field by enabling collaboration and establishing standards.

Recommendations
Focus on measures that are meaningful to patients and clinically relevant by incorporating both patient and clinician perspectives.
Select technology after identifying the appropriate outcome to ensure alignment between the technology and trial objectives.
Engage with regulators early and often to ensure endpoint acceptance and alignment with regulatory requirements.
Include digitally-derived endpoints in early-phase trials and observational studies to validate their fit-for-purpose status.
Encourage knowledge sharing and collaboration among stakeholders to establish shared standards and accelerate adoption.

Regulatory Considerations
Engage with FDA, EMA, or other regulatory bodies during early stages of endpoint development to gather critical input.
Use established regulatory frameworks, such as Investigational New Drug (IND) or Investigational Device Exemption (IDE), for guidance on endpoint use in pivotal trials.
Validate technologies to meet performance characteristics, ensuring outputs correspond to clinical concepts of interest.
Include digitally-derived endpoints in exploratory studies to build evidence for their regulatory approval.
Reference resources such as the FDA and EMA guides for navigating endpoint-related regulatory interactions.

Findings
Meaningful outcome measures should align with patient priorities and clinical relevance, emphasizing aspects of health that impact daily life.
Digital tools must demonstrate value over traditional methods in capturing outcomes, especially in remote or decentralized contexts.
Questions about therapeutic benefit and endpoint sensitivity must address how these measures reflect patient improvements or disease progression.
Stakeholder collaboration is critical to selecting and validating concepts of interest and corresponding outcome measures.
Challenges include ensuring data privacy, operational feasibility, and addressing potential gaps in endpoint validation.

Recommendations
Engage patients and caregivers to identify meaningful aspects of health and concepts of interest relevant to their daily lives and goals.
Collaborate with clinicians to determine the clinical validity and utility of proposed measures and tools for endpoint development.
Ensure that DHTs selected for measurement add value beyond traditional methods and are feasible for clinical and real-world use.
Incorporate payer perspectives to align outcome measures with cost-benefit evaluations and reimbursement criteria.
Use the question bank as a flexible guide, adapting it to the specific needs and context of individual clinical trials.

Regulatory Considerations
Ensure endpoints and their measures meet regulatory standards for clinical relevance and sensitivity to therapeutic changes.
Align outcome measures with accepted core sets (e.g., COMET database) and validate them through stakeholder engagement.
Address concerns related to data privacy, scalability, and operational feasibility in the use of DHTs for endpoint development.
Plan for regulatory engagement to demonstrate the robustness of digitally-derived endpoints in pivotal clinical trials.
Provide evidence to support the incorporation of novel endpoints into regulatory and payer frameworks for decision-making.