
Welcome to the sDHT Adoption Library, featuring NaVi
NaVi is a closed-environment AI research assistant that leverages a carefully curated library of more than 300+ vetted documents, including FDA guidance and industry best practices. NaVi helps you search and explore content across the sDHT Adoption Library and Roadmap using natural language questions.
The Library is intended to serve as a living resource. Content is added periodically as new guidance, standards, and peer-reviewed research are released.
Meet NaVi: Your AI-Powered Research Assistant
Library scope and selection
To ensure high-quality, relevant results, the Library follows a predefined scoping approach:
- Inclusions: FDA guidance, non-commercial standards, and peer-reviewed research (2018–Present) focused on sDHTs being used as measurement tools for medical products in U.S.-based clinical trials.
- Exclusions: Materials from single commercial entities, non-U.S. regulatory bodies (except select EMA guidances with direct U.S. cross-relevance), and conference proceedings, and conference proceedings.
Inclusion in the Library does not imply endorsement, completeness, or regulatory acceptability.
Library scope
Resources in the sDHT Adoption Library are identified using a predefined scoping approach and include publicly available FDA guidance, non-commercial standards and guidance, and peer-reviewed research relevant to sDHT use in U.S.-based clinical trials. Materials from single commercial entities, non-U.S. regulatory bodies, conference proceedings, and studies conducted exclusively outside the United States are excluded; inclusion does not imply endorsement or regulatory acceptability.
Last updated 2026: Library content is reviewed and updated on a periodic basis as new eligible materials become available.
Core Digital Measures of Pediatric Rare Disease
Core Digital Measures of Pediatric Rare Disease
Findings
Fragmented and inconsistent measurement approaches currently hinder the generation of decision-grade evidence for pediatric rare diseases. Small and geographically dispersed patient populations make traditional site-based clinical assessments operationally difficult and burdensome for families. Digital health technologies can capture subtle functional changes and "functional fingerprints" in home settings that are often missed during infrequent clinic visits. Standardized core digital measures across conditions allow for the aggregation of data and the creation of a shared evidence base for rare disorders. Meaningful aspects of health identified by patients and caregivers include motor function, communication, sleep quality, and autonomic stability.
Recommendations
Sponsors should adopt the core set of digital clinical measures to reduce trial timelines, lower development costs, and decrease participant burden. Researchers should prioritize passive and objective data collection to minimize the need for manual tracking by caregivers. Clinical trial designs should transition toward decentralized or hybrid models to improve access for children and families regardless of their location. Stakeholders should use the project's conceptual model to identify and customize digital measures that align with the specific health priorities of their target population. Developers should focus on human-centered design to ensure digital tools are usable and sustainable for pediatric patients and their support networks.
Regulatory Considerations
The FDA and EMA provide specific pathways and interaction opportunities to accelerate the acceptance of digital endpoints in rare disease trials. Digital measures must be validated as "decision-grade" endpoints to meet the evidentiary requirements for regulatory submission and marketing approval. Alignment with industry standards for data elements and interoperability is necessary to ensure data integrity across multi-site studies. Early engagement with regulatory bodies through meetings and formal submissions is critical for confirming the suitability of new digital biomarkers. Compliance with data privacy and ethical standards is paramount when collecting continuous, real-world data from vulnerable pediatric populations.
Some summaries are generated with the help of a large language model; always view the linked primary source of a resource you are interested in.
Advancing the Integration of Digital Health Technologies in the Drug Development Ecosystem
Advancing the Integration of Digital Health Technologies in the Drug Development Ecosystem
Findings
The rapid advancement of sensor technology and connectivity has enabled high-frequency, longitudinal monitoring of physiological processes, yet the infrastructure for large-scale deployment remains resource-intensive. Current challenges include a lack of standardized terminology for digital decision-making tools and significant variability in environmental factors that affect sensor performance. Proprietary algorithms and device-specific barriers often hinder the verification and validation processes necessary for regulatory approval. Additionally, there is a distinct gap between granular digital features and their clinical relevance or meaningfulness to patients. Ethical concerns are emerging around data management, patient anxiety in psychiatric contexts, and the responsibility for addressing adverse events detected by remote monitoring.
Recommendations
Stakeholders should develop consensus-driven frameworks for standardized device performance reporting and environmental testing to streamline evaluations for specific contexts of use. The community should adopt a modular approach to data standards that bins requirements by concept of interest and disease-specific needs. Collaborative efforts between patients and developers are essential to bridge the gap between technical metrics and meaningful aspects of health. It is recommended to implement ""bring-your-own-device"" (BYOD) frameworks that ensure data reliability while supporting the inevitable evolution of technology during long-term studies. Researchers and clinicians must be trained in the ethical, legal, and social implications of digital health technology use, particularly regarding data privacy and the management of remote-detected safety signals.
Regulatory Considerations
Digital health technologies used to collect endpoints must meet high evidentiary requirements for validation, with complexity increasing when multiple sensors or complex software are bundled. Regulatory agencies like the FDA and EMA have established pathways for the qualification of drug development tools, including biomarkers and clinical outcome assessments. Integration of new draft guidance on remote health monitoring with existing regulatory workflows is necessary to reduce uncertainty in trial evaluations. While many digital health technologies do not qualify as medical devices unless they have a specific medical purpose, synergies between device risk assessments and drug trial data integrity frameworks should be explored. Early engagement with regulators remains a critical step for obtaining feedback on novel digital endpoints and ensuring the suitability of evidentiary support.
Some summaries are generated with the help of a large language model; always view the linked primary source of a resource you are interested in.
Artificial Intelligence in Software as a Medical Device
Artificial Intelligence in Software as a Medical Device
The traditional medical device regulatory paradigm is not designed for the adaptive nature of AI/ML technologies, which can learn and change after they are on the market. A key benefit of AI/ML is its ability to improve performance by learning from real-world data, but this also presents a unique regulatory challenge. To ensure patient safety and device effectiveness, a new, flexible regulatory framework is required that can accommodate these iterative improvements. Transparency and robust monitoring are essential to manage the risks associated with evolving algorithms.
Recommendations
The FDA proposes a "Predetermined Change Control Plan" (PCCP) to be included in premarket submissions. This plan would specify the anticipated modifications to the device (the "what") and the methodology for implementing and validating those changes (the "how"). The development of "Good Machine Learning Practice" (GMLP) is encouraged to ensure that AI/ML algorithms are developed and validated using best practices. Manufacturers should implement robust real-world performance monitoring to ensure that their devices remain safe and effective after deployment.
Regulatory Considerations
The FDA is developing a new regulatory framework tailored to the unique aspects of AI/ML-based SaMD, which will leverage a TPLC approach. The agency has issued an "AI/ML SaMD Action Plan" that outlines its multi-pronged approach, including issuing draft guidance on PCCPs and promoting the harmonization of GMLP. The FDA is actively collaborating with stakeholders to foster innovation while ensuring patient safety. The agency maintains a public list of authorized AI/ML-enabled medical devices to enhance transparency.
Some summaries are generated with the help of a large language model; always view the linked primary source of a resource you are interested in.
Building the business case for digital endpoints
Building the business case for digital endpoints
Digital endpoints must not only support regulatory approval but also provide evidence that meets payer expectations for reimbursement and value-based care. The lack of early engagement with payers and health technology assessment (HTA) agencies is a key barrier to the adoption of digital clinical measures. Digital measures can enhance value-based care models by capturing patient-centered outcomes, reducing healthcare costs, and improving early disease detection. The scalability and generalizability of digital endpoints remain challenges, particularly for diverse populations and real-world healthcare settings. Technical and systematic barriers—such as data heterogeneity, stakeholder knowledge gaps, and inconsistent regulatory-payer alignment—are slowing the adoption of digital endpoint data for reimbursement decisions.
Recommendations
Pharma and medical product developers should engage early with payers and regulators to ensure digital endpoints align with reimbursement expectations. Payers and HTA bodies should establish clear evidence thresholds for digital endpoint validation, ensuring consistency in market access decisions. Digital endpoints should be validated against health-related quality of life (HRQoL) measures and patient-reported outcomes (PROs) to demonstrate clinical relevance. Real-world evidence (RWE) should be incorporated into clinical trials alongside digital endpoints to strengthen reimbursement applications. Stakeholders should prioritize scalable, patient-centered digital measures that capture disease progression over time and across different care settings.
Regulatory Considerations
Integrated Evidence Plans (IEPs) should be developed early to align digital endpoint evidence with regulatory and payer requirements. Digital endpoints should be assessed through multi-stakeholder collaboration, ensuring validation across pharmaceutical, regulatory, and reimbursement frameworks. Payers and regulators should work together to create aligned pathways for digital measure acceptance, reducing delays in market access. Data security, privacy, and interoperability must be addressed to support regulatory approval and patient trust in digital health solutions. The industry should leverage international regulatory-payer collaboration models, such as the HTA-EMA partnership and the FDA Payor Communication Task Force, to accelerate global digital endpoint adoption.
Some summaries are generated with the help of a large language model; always view the linked primary source of a resource you are interested in.
Cybersecurity in Medical Devices Frequently Asked Questions (FAQs)
Cybersecurity in Medical Devices Frequently Asked Questions (FAQs)
Cybersecurity is an integral part of medical device safety and effectiveness, and manufacturers are responsible for addressing it throughout the entire device lifecycle. The FDA considers a device's cybersecurity as part of its benefit-risk assessment for both premarket and postmarket activities. A lack of robust cybersecurity controls can lead to patient harm, compromised device functionality, and breaches of data privacy. The dynamic nature of cybersecurity threats requires ongoing monitoring, risk management, and timely implementation of mitigation strategies.
Recommendations
Manufacturers should build cybersecurity into devices from the design phase ("secure by design") and conduct a thorough risk analysis to identify and mitigate potential vulnerabilities. Premarket submissions should include comprehensive documentation of the device's cybersecurity controls, a risk management plan, and a plan for postmarket surveillance and response. Manufacturers should establish a robust postmarket surveillance program to monitor for, identify, and address new cybersecurity threats in a timely manner. Clear and informative labeling is essential to help users understand and manage cybersecurity risks.
Regulatory Considerations
The FDA has the authority to take action against devices with inadequate cybersecurity that pose a risk to public health. The agency recommends that manufacturers use the Q-submission process to discuss specific cybersecurity questions related to their device submissions. Compliance with recognized standards and best practices for cybersecurity is strongly encouraged. Manufacturers must report certain cybersecurity incidents to the FDA as part of their postmarket reporting requirements. The FDA collaborates with other government agencies and stakeholders to promote a coordinated approach to medical device cybersecurity.
Some summaries are generated with the help of a large language model; always view the linked primary source of a resource you are interested in.
Delivering regulatory impact from consortium-based projects
Delivering regulatory impact from consortium-based projects
Findings
Establishing cross-sector consortia does not guarantee success without a unified objective and stakeholder buy-in. A neutral, independent facilitator is a key element for successful governance in many collaborative platforms. Many consortia lack consistent methods for storing critical data, meeting minutes, and regulatory briefing packages, which creates barriers after project completion. Regulatory success depends heavily on the early development of a strategy that defines the necessary evidence to validate innovative methodologies. Successful examples include the qualification of biomarkers for polycystic kidney disease and type 1 diabetes, as well as imaging measures for Alzheimer’s disease.
Recommendations
Consortium members should develop an initial regulatory strategy during the project scoping and planning phases. Teams must explicitly define the context of use for any proposed tool to articulate exactly what decisions the output will inform. A robust data strategy should be implemented early, including formal agreements for data use, standardization, and sharing that remain in place in perpetuity. Consortia must prioritize sustainability plans to ensure data and active databases remain available for research and regulatory use after funding expires. Projects should integrate regulatory science expertise from the start to cover both EU and US frameworks.
Regulatory Considerations
Regulators require individual patient-level data that is fully curated, standardized, and presented through formal submissions like qualification applications. Formal regulatory endorsement ensures a tool can be trusted for consistent interpretation in drug development and marketing authorization evaluations. Early engagement with agencies such as the FDA and EMA is essential to gain feedback on novel methodologies and align study designs with regulatory expectations. Specific pathways like the EMA Qualification of Novel Methodologies and the FDA Qualification Process for Drug Development Tools should be utilized. Regulatory qualification may require ongoing access to databases to support the long-term use of the methodology.
Some summaries are generated with the help of a large language model; always view the linked primary source of a resource you are interested in.
List of qualified DDTs
List of qualified DDTs
The database provides a transparent and accessible way for the public to track the progress of various Drug Development Tools (DDTs) through the FDA's qualification pipeline. This includes biomarkers, clinical outcome assessments, and animal models. The information available, such as submission status and supporting documentation, offers insight into the types of tools being developed and the evidence required for their qualification. The platform reveals that a wide range of tools are in development across numerous therapeutic areas, highlighting active areas of research and innovation in drug development.
Recommendations
Stakeholders in the drug development ecosystem are encouraged to utilize this database to inform their research and development strategies. By reviewing the status of existing DDT submissions, sponsors can identify opportunities for collaboration, avoid duplicative efforts, and better understand the evidentiary requirements for tool qualification. Prospective tool developers should use the database to learn from successful submissions and to align their own development plans with FDA expectations.
Regulatory Considerations
This database is a direct implementation of the transparency provisions of the 21st Century Cures Act. The public availability of this information is intended to foster trust and collaboration in the DDT qualification process. By providing a clear view of the regulatory journey of various tools, the FDA aims to standardize the qualification process and encourage the development and use of novel, validated tools in drug development. Users of the database should be aware that the information reflects the status of a DDT at a particular point in time and that the qualification process is an iterative one.
Some summaries are generated with the help of a large language model; always view the linked primary source of a resource you are interested in.
Patient Engagement Synapse: Resource Directory
Patient Engagement Synapse: Resource Directory
Traditional, site-based clinical trials often create significant burdens for participants, which can hinder recruitment, retention, and the enrollment of diverse populations.
A lack of early and sustained patient engagement in trial design can lead to research protocols that are misaligned with patient needs and endpoints that are not meaningful to them.
The underrepresentation of diverse racial, ethnic, and other demographic groups in clinical trials limits the generalizability of study results and can perpetuate health disparities.
Emerging digital health technologies (DHTs) and real-world data (RWD) present significant opportunities to make clinical trials more efficient, patient-centric, and inclusive, but their adoption has been inconsistent.
Recommendations
Sponsors and research teams should engage patients and patient advocacy groups as active partners throughout the entire clinical trial lifecycle, from design to dissemination.
Decentralized clinical trial (DCT) elements should be incorporated to reduce patient burden, improve access for diverse populations, and enhance the quality of data collection.
Trial sponsors must develop and implement proactive strategies to enhance the diversity and inclusion of trial participants to ensure results are applicable to all patient populations.
Novel endpoints derived from DHTs should be developed and validated to capture more objective, real-world measures of how patients feel, function, and survive.
Multi-stakeholder collaboration between industry, academia, patient groups, and regulators is essential to address systemic challenges and improve the clinical trial enterprise.
Regulatory Considerations
Early and frequent communication with regulators, such as the FDA, is critical when implementing novel approaches like DCTs or developing new digital endpoints for pivotal trials.
Regulatory frameworks must support the use of innovative technologies and trial models while ensuring data integrity, reliability, and patient safety.
The use of a single Institutional Review Board (IRB) for multi-site trials is a key regulatory-supported mechanism for streamlining ethics review and increasing trial efficiency.
When using DHTs and decentralized methods, robust plans for data quality, privacy, and security are necessary to meet regulatory standards for trial data submission.
Some summaries are generated with the help of a large language model; always view the linked primary source of a resource you are interested in.
Using Artificial Intelligence & Machine Learning in the Development of Drug & Biological Products: Discussion Paper and Request for Feedback, 2025 (FDA)
Using Artificial Intelligence & Machine Learning in the Development of Drug & Biological Products: Discussion Paper and Request for Feedback, 2025 (FDA)
The use of Artificial Intelligence (AI) and Machine Learning (ML) is being applied to a broad range of drug development activities with the potential to accelerate the process and make clinical trials safer and more efficient. The inclusion of AI/ML is most common in the clinical development/research phase of regulatory submissions. Concerns exist that AI/ML algorithms could amplify errors and preexisting biases in underlying data sources, which raises issues related to generalizability and ethical considerations. Other challenges include limited explainability due to model complexity and proprietary reasons, as well as managing risks related to data quality, reliability, and representativeness. The FDA recognizes that a careful, risk-based assessment of the specific context of use (COU) is needed when evaluating AI/ML.
Recommendations
Stakeholders should adhere to practices in three key areas: human-led governance, accountability, and transparency; quality, reliability, and representativeness of data; and model development, performance, monitoring, and validation. A risk management plan should be applied to identify and mitigate risks based on the COU, guiding the level of documentation and transparency. Practices are needed to ensure the integrity of AI/ML and address issues like bias and missing data. For models, developers should use pre-specification steps and clear documentation for development and assessment criteria. Models must be monitored over time for reliability and consistency, and Real-World Data (RWD) performance can provide valuable feedback, including for potential re-training.
Regulatory Considerations
The FDA encourages early engagement through mechanisms like the Critical Path Innovation Meetings (CPIM), ISTAND Pilot Program, and Emerging Technology Program to discuss relevant AI/ML methodologies or technologies. The Verification and Validation (V&V 40) risk-informed credibility assessment framework and the principles for Good Machine Learning Practices (GMLP), while not specific to drug development, are helpful guides for evaluating models. The industry is exploring the use of a Predetermined Change Control Plan (PCCP) mechanism for AI/ML-based devices to proactively specify and manage modifications, enhancing adaptability. In general, a risk-based approach should guide the level of evidence and record keeping needed for the verification and validation of AI/ML models for a specific COU.
Some summaries are generated with the help of a large language model; always view the linked primary source of a resource you are interested in.
Best Practices and Recommendations for Sites Utilizing Connected Devices
Best Practices and Recommendations for Sites Utilizing Connected Devices
Sites must establish effective data privacy and security plans, especially considering regional and global regulations like GDPR.
Risk mitigation is critical, including plans to address unanticipated issues and potential patient disengagement due to technology challenges.
Budgeting and contracting often involve additional considerations, such as storage, training, and technical support requirements for connected devices.
Sites require adequate training to ensure staff and patients are prepared to use connected devices efficiently.
Companion applications or services often play an essential role in device functionality and data transmission.
Recommendations
Develop a clear plan for data pathways, including storage, security, and regulatory compliance.
Establish detailed risk mitigation and management strategies to handle unexpected challenges.
Ensure comprehensive training programs for site staff and patients to enhance device usability.
Incorporate device storage and resource allocation into budgeting and contracting processes.
Facilitate effective communication with sponsors and vendors to resolve operational and technical issues promptly.
Regulatory Considerations
Ensure connected devices comply with CFR 21, Part 11, and other relevant data collection and transmission regulations.
Understand and adhere to local and regional data privacy laws, such as GDPR, when managing patient data.
Verify that appropriate licenses and regulatory approvals are in place for device data transmission and storage.
Assess and address shipping and handling regulations for devices, ensuring safe and compliant transportation.
Some summaries are generated with the help of a large language model; always view the linked primary source of a resource you are interested in.
Building Fit-for-Purpose Sensor-based Digital Health Technologies: A Crash Course
Building Fit-for-Purpose Sensor-based Digital Health Technologies: A Crash Course
Usability gaps in sDHTs remain a barrier to adoption, with many technologies failing to prioritize ease of use, accessibility, and diverse user needs
Human-centered design is critical for ensuring that digital health solutions are intuitive, functional, and scalable across different healthcare environments
Standardized usability metrics for evaluating digital health technologies are lacking, leading to inconsistent reporting and validation of usability outcomes
Use-related risk analysis is essential to identifying and mitigating risks associated with user errors, ensuring the safety and effectiveness of sDHTs
The V3+ framework provides a structured approach to integrating usability validation into digital health technology development, aligning with global regulatory expectations
Recommendations
Developers should incorporate human-centered design principles from the outset, ensuring that usability, accessibility, and user needs are central to sDHT development
Usability validation should be standardized, with clear methodologies for measuring usability, including satisfaction, ease of use, efficiency, and error mitigation
Regulatory and clinical stakeholders should collaborate on defining best practices for usability evaluation, ensuring that digital endpoints are both meaningful and scalable
Risk analysis should be iterative, with developers continuously refining their technologies based on real-world user feedback and testing
The usability validation component of V3+ should be widely adopted to ensure that digital clinical measures meet patient-centered, regulatory, and technical expectations
Regulatory Considerations
Regulators are emphasizing the need for usability validation to ensure that digital endpoints are both clinically relevant and patient-friendly
sDHTs must comply with human factors engineering guidelines, aligning with global regulatory frameworks such as ISO 9241-210 and FDA usability requirements
Data security, privacy, and interoperability must be ensured, particularly as sDHTs become integrated into remote monitoring and decentralized clinical trials
Real-world evidence (RWE) should support usability validation, helping to bridge the gap between regulatory approval and real-world adoption
Regulatory bodies should work toward standardizing usability testing methodologies, ensuring consistency across clinical research, digital endpoints, and medical device evaluations
Some summaries are generated with the help of a large language model; always view the linked primary source of a resource you are interested in.
Electronic Systems, Electronic Records, and Electronic Signatures in Clinical Investigations: Questions and Answers
Electronic Systems, Electronic Records, and Electronic Signatures in Clinical Investigations: Questions and Answers
The FDA considers electronic records and signatures equivalent to their paper counterparts when they meet the requirements of 21 CFR Part 11. Due to technological advances, electronic systems and digital health technologies (DHTs) are now integral to clinical trials, requiring a modern, risk-based approach to ensure data integrity. Sponsors remain ultimately responsible for the quality and integrity of all data submitted, even when using third-party IT service providers or data from real-world sources like EHRs. The authenticity, integrity, and confidentiality of electronic data are paramount and must be maintained through robust system controls throughout the data lifecycle.
Recommendations
Regulated entities should use a justified and documented risk-based approach to validate all electronic systems before and during a clinical trial, with the level of validation depending on the system's potential to impact participant safety and trial result reliability. Secure, computer-generated, time-stamped audit trails must be implemented to track the creation, modification, and deletion of all electronic records without obscuring original data. Robust logical and physical access controls are necessary to limit system access to authorized individuals. Entities should have written agreements with IT service providers that clearly define roles, responsibilities, and procedures for ensuring data security and long-term retention.
Regulatory Considerations
The requirements of 21 CFR Part 11 apply to all electronic records created, modified, or submitted to the FDA under predicate rules for clinical investigations, including those from foreign sites under an IND or IDE. While the FDA does not intend to assess the Part 11 compliance of external source systems like EHRs, data becomes subject to these regulations once transferred into the sponsor's electronic system. During inspections, the FDA will focus on system validation, data handling procedures, security protocols, audit trails, and documentation of sponsor oversight. Users must certify to the FDA that their electronic signatures are the legally binding equivalent of handwritten signatures.
Some summaries are generated with the help of a large language model; always view the linked primary source of a resource you are interested in.