
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.
Recommendations for Selecting and Testing a Digital Health Technology
Recommendations for Selecting and Testing a Digital Health Technology
The selection of DHTs must align with the specific goals of the trial, focusing on unmet patient or scientific needs.
A specification-driven approach, rather than solely relying on a technology's regulatory status, ensures alignment with trial requirements.
Verification and validation are distinct processes; both are critical to confirm the reliability and clinical relevance of DHTs.
Pre-trial feasibility studies help identify potential issues, such as wear-time compliance or usability concerns, before full implementation.
DHTs can alter participant interactions and trial workflows, necessitating clear communication, training, and management plans.
Recommendations
Define Measurement Goals Before Selection: Ensure that the decision to use a DHT is based on unmet needs or the promise of reducing trial burdens.
Adopt a Specification-Driven Selection Process: Tailor DHT selection to technical performance, participant needs, and study-specific requirements.
Verify and Validate Technologies Thoroughly: Collaborate with manufacturers to ensure DHTs are tested in both controlled and real-world settings and validated for the target population.
Conduct Feasibility Studies: Test DHTs for tolerability, usability, and compliance within the specific trial context to identify and address issues early.
Prepare for Operational Challenges: Develop a robust management plan with standard operating procedures (SOPs) to address potential failures and ensure smooth implementation.
Regulatory Considerations
The regulatory status of a DHT should not solely drive its selection; instead, focus on its ability to meet trial specifications.
Ensure transparent collaboration with manufacturers to document DHT performance characteristics and limitations.
Validate endpoints and DHT data to align with evidentiary standards for regulatory submissions.
Use feasibility studies and SOPs to ensure that DHTs comply with regulatory and operational requirements during trials.
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.
Regulatory Engagement Opportunities when Developing Digitally Derived Endpoints
Regulatory Engagement Opportunities when Developing Digitally Derived Endpoints
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.
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.
Risk Based Monitoring
Risk Based Monitoring
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.
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.
Steps for Novel Endpoint Development, with Suggested Approaches and Considerations
Steps for Novel Endpoint Development, with Suggested Approaches and Considerations
Developing a novel endpoint requires an iterative and patient-centered approach, beginning with defining the study population and relevant health aspects.
Concepts of interest (COIs) must be specific, measurable, and clinically meaningful, with input from patients and caregivers.
Endpoint validation includes defining meaningful change, ensuring content validity, and demonstrating the ability to detect change.
Digital tools must meet criteria for usability, analytic validity, and tolerability within the target population.
Regulatory engagement and alignment throughout the process are critical to endpoint acceptance.
Recommendations
Define the study population and context of use (COU) early to guide endpoint and technology selection.
Identify meaningful health aspects (MHA) and concepts of interest (COI) with input from patients and clinicians.
Select and validate DHTs based on performance, usability, and their ability to capture meaningful data.
Establish meaningful change thresholds and validate endpoints in real-world settings.
Engage with regulators at every stage to align endpoints with evidentiary and regulatory standards.
Regulatory Considerations
Define and validate meaningful change thresholds that reflect treatment benefits for regulatory acceptance.
Ensure DHTs meet analytic validity standards, including accuracy, reliability, and reproducibility.
Demonstrate content validity, ensuring that endpoints accurately reflect the intended COI across the full range of anticipated data.
Align with regulatory requirements to incorporate validated endpoints into pivotal trials.
Address usability, data privacy, and compliance concerns to meet regulatory and operational standards.
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.
Twenty-Four-Hour Ambulatory Blood Pressure Measurement Using a Novel Noninvasive, Cuffless, Wireless Device
Twenty-Four-Hour Ambulatory Blood Pressure Measurement Using a Novel Noninvasive, Cuffless, Wireless Device
The PPG-based Wrist-monitor provides comparable measurements to traditional devices with less inconvenience.
Further research is needed to confirm accuracy in specific subpopulations.
Current ABPM devices may impact long-term adherence due to discomfort.
Recommendations
Conduct further studies on the device's accuracy in various subpopulations.
Consider the PPG-based device for continuous BP monitoring.
Use the device for hypertension diagnosis and treatment.
Explore the device's use in other inpatient settings.
Regulatory Considerations
The device is FDA cleared for BP measurements.
It is undergoing validation for other inpatient settings.
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.
A Roadmap to Inform Development, Validation and Approval of Digital Mobility Outcomes: The Mobilise-D Approach
A Roadmap to Inform Development, Validation and Approval of Digital Mobility Outcomes: The Mobilise-D Approach
Lack of widely accepted tools for digital mobility assessment.
Challenges in technical and clinical validation due to multiple expertise requirements.
Inconsistent testing procedures and variations in norms.
Limitations of current mobility measurement methods.
Need for real-world mobility assessment.
Recommendations
Adopt best practices and innovate with standards and open access tools.
Ensure transparency through regular interaction with stakeholders.
Develop algorithms in an agnostic and fully documented manner.
Make data accessible through a digital data biobank.
Aim for regulatory approval with accurate real-world mobility measurement.
Regulatory Considerations:
Engage in early dialogue with regulatory authorities.
Understand different regulatory requirements based on context of use.
Focus on qualification of new methodologies for safety and efficacy.
Use DMOs to monitor disease progression and as surrogates for secondary endpoints.
Adopt a staged approach to regulatory qualification.
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.
A Shared Perspective of Patient Technology Implementation in Clinical Trials
A Shared Perspective of Patient Technology Implementation in Clinical Trials
Patient technologies were used across 55 countries, with mobile applications (53%) and wearable devices (33%) being the most common technologies.
Common data issues included data transmission failures, duplicate or missing data, and integration challenges with other datasets.
Factors like technical literacy, device usability, and preferences for paper-based alternatives affected adoption rates, particularly in elderly populations.
Varying broadband connectivity, importation hurdles, and compliance with regulations like GDPR posed significant challenges.
Most sponsors (54%) were willing to reuse technologies, citing improved retention, compliance, and remote monitoring capabilities as key benefits.
Recommendations
Consider patient demographics, such as age and technical literacy, when selecting and implementing technologies.
Offer multi-format training for sites, patients, and monitors, and provide robust support systems to address technical and compliance issues.
Risk Mitigation: Anticipate potential issues like data loss, non-compliance, and technical failures by incorporating backup processes into protocols.
Conduct feasibility assessments for site infrastructure and regulatory compliance in target regions to minimize delays.
Regularly gather experiential feedback from patients to refine technologies and improve future trial designs.
Regulatory Considerations
Seek advice from regulators to ensure patient technologies align with clinical trial protocols and data submission requirements.
Ensure Compliance with GDPR and Local Regulations: Address privacy concerns and adapt technologies to meet country-specific requirements.
Prepare Documentation for Importation: Account for additional time and costs related to import licenses and customs requirements.
Plan for the impact of technical updates on clinical data reliability and regulatory submissions.
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.
Biomarker Qualification: Evidentiary Framework
Biomarker Qualification: Evidentiary Framework
A universally applicable evidentiary standard for biomarker qualification is not feasible; the necessary level of evidence depends entirely on the specific Context of Use (COU). The framework emphasizes that the strength of evidence is evaluated based on the potential risk and benefit associated with the biomarker's intended application in drug development. The relationship between a biomarker and clinical outcomes must be robustly demonstrated, but there are no fixed quantitative criteria for this association. The overall confidence in a biomarker is derived from a combination of analytical validation, clinical validation, and the strength of the biological rationale.
Recommendations
Sponsors should clearly define the specific COU for the biomarker early in the development process, as this will dictate the required evidentiary support. It is recommended that sponsors engage with the FDA throughout the biomarker development and validation process to ensure alignment on the evidentiary requirements. Submissions for biomarker qualification should include a comprehensive package of evidence detailing the analytical validation (how well the test measures the biomarker) and the clinical validation (how well the biomarker relates to a clinical endpoint). Sponsors should provide a strong biological rationale for the biomarker's role in the disease process and its relevance to the proposed COU.
Regulatory Considerations
The FDA's evidentiary framework is designed to be a flexible, risk-based approach to biomarker qualification. The qualification is specific to the COU for which it was evaluated and does not imply acceptance for other uses. The framework is intended to support the use of biomarkers as Drug Development Tools (DDTs), which can include uses for patient selection, as surrogate endpoints, or to demonstrate a drug's mechanism of action. The level of regulatory scrutiny is proportional to the impact the biomarker will have on drug development and clinical decision-making. Qualified biomarkers can help to de-risk and streamline the drug development process.
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.
BioMeT and Algorithm Challenges: A Proposed Digital Standardized Evaluation Framework
BioMeT and Algorithm Challenges: A Proposed Digital Standardized Evaluation Framework
Lack of security and confidence in digital health technologies hampers adoption.
Absence of suitable guidance for selecting BioMeTs based on clinical requirements.
BioMeTs (DHTs) and algorithms are often created without expert guidance and transparency.
No standardized evaluation resources for testing, verifying, and validating BioMeTs.
Inconsistencies in algorithm application across different cohorts.
Recommendations
Develop a standardized BioMeT and algorithm evaluation framework.
Create professionally tailored standardized guidelines for BioMeT use.
Implement a framework with unique identifiers for BioMeTs and algorithms.
Establish mechanisms for dynamic updates of hardware or software.
Use systematic reviews and Delphi processes to inform framework development.
Regulatory Considerations
Assign unique identifier numbers to BioMeTs and algorithms.
Provide mechanisms for dynamic hardware or software updates.
Ensure robust deployment through standardized evaluation protocols.
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.
Choosing a Mobile Sensor Technology for a Clinical Trial: Statistical Considerations, Developments and Learnings
Choosing a Mobile Sensor Technology for a Clinical Trial: Statistical Considerations, Developments and Learnings
The complexity of selecting appropriate technology due to an increasing array of devices and sensors.
Risks associated with choosing inappropriate MSTs, including susceptibility to missing data or erroneous data transmission.
The need for both manufacturers and clinical trial sponsors to ensure analytical validation supports MST use.
Recommendations
Identify a digital outcome that meets an unmet need for the planned trial or population.
Determine whether the technology is fit-for-purpose based on the measure, context of use, and classification as a medical device.
Ensure devices are reliable and reproducible for collecting required data.
Conduct statistical analysis according to a predefined analysis plan.
Consider adaptive designs to reduce resource requirements and increase study success.
Regulatory Considerations
Compliance with medical device classifications such as 510(k)s and CE marks.
Ensure devices and platforms comply with HIPAA, GDPR, and data privacy regulations.
Be aware of potential updates to technology or software that could impact trials.
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.
Considerations for development of an evidence dossier to support the use of mobile sensor technology for clinical outcome assessments in clinical trials
Considerations for development of an evidence dossier to support the use of mobile sensor technology for clinical outcome assessments in clinical trials
Mobile sensors provide unique opportunities for objective, real-world data collection but face challenges in achieving regulatory acceptance due to a lack of standardization and validation frameworks.
A comprehensive evidence dossier must address three key components: verification, analytical validity, and clinical validation, to ensure endpoints are fit-for-purpose.
Demonstrating content validity is critical, especially when endpoints are not directly measuring meaningful aspects of health but infer these through related concepts.
Early engagement with regulatory bodies (e.g., FDA, EMA) is recommended to align expectations and address evidentiary gaps.
Usability and feasibility research are vital to ensure patient compliance and data quality in real-world applications.
Recommendations
Develop Comprehensive Dossiers: Include sections on endpoint definition, concept of interest, content validity, clinical validation, analytical validation, and implementation details to support regulatory review.
Ensure Content Validity: Demonstrate a clear relationship between sensor-derived endpoints and meaningful health outcomes, supported by literature, patient interviews, and expert consensus.
Engage with Regulators Early: Discuss the proposed endpoint and its context of use with regulatory agencies to ensure alignment and identify potential challenges.
Standardize Validation Processes: Use rigorous methods for verification, analytical validation, and construct validation to establish the reliability and accuracy of sensor technologies.
Promote Collaboration: Share validation data and methodologies across stakeholders to reduce redundancy and accelerate the adoption of mobile sensor endpoints.
Regulatory Considerations
Verification of Sensor Technologies: Demonstrate that sensors produce accurate, reliable, and consistent raw data under various conditions, including environmental variability.
Analytical Validation: Show that firmware and algorithms used to process raw data maintain high technical performance and align with regulatory standards.
Clinical Validation: Provide evidence that sensor-derived data reliably measure the concept of interest and are responsive to meaningful clinical changes.
Context of Use: Clearly define the intended application of the endpoint, including target populations, trial design, and labeling claims, to guide regulatory evaluation.
Data Security and Privacy: Ensure compliance with data protection regulations, such as 21 CFR Part 11, to secure patient data during collection, transmission, and storage.
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.
Continuous heart rhythm monitoring using mobile photoplethysmography in ambulatory patients
Continuous heart rhythm monitoring using mobile photoplethysmography in ambulatory patients
The CardiacSense PPG device can reliably detect heart rate in various situations, but noise suppression during activity remains a challenge.
The study did not directly address the device's ability to detect atrial fibrillation in ambulatory patients, indicating a gap in current research.
Further studies are needed to confirm the device's effectiveness in detecting AF during ambulatory conditions.
Recommendations
Improve noise suppression technology to enhance the device's accuracy during motion.
Conduct further studies to validate the device's ability to detect atrial fibrillation in ambulatory patients.
Continue research to address the limitations identified in the current study.
Regulatory Considerations
Adherence to FDA guidance for new medical device applications is crucial.
Ensure compliance with regulatory standards for digital health technologies.
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.