
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.
510(k) Premarket Notification
510(k) Premarket Notification
The Premarket Notification (510(k)) database is a critical component of the FDA's regulatory framework for medical devices. Its primary function is to house information on devices that have been cleared through the 510(k) pathway, which is the most common route to market for medical devices in the U.S.
A 510(k) submission's central requirement is to demonstrate "substantial equivalence" to a legally marketed predicate device. This means the new device is as safe and effective as a device already on the market. Clearance of a 510(k) does not denote "approval" in the same way as a Premarket Approval (PMA) application but rather confirms that the device meets the necessary criteria for marketing.
The database provides transparency and serves as an essential resource for manufacturers to identify potential predicate devices for their own submissions. For healthcare providers, patients, and researchers, it offers a way to verify the regulatory status and clearance basis for a specific device.
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.
FDA Consensus Standards Database
FDA Consensus Standards Database
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.
Library of Digital Measurement Products
Library of Digital Measurement Products
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.
Computer-Assisted Detection Devices Applied to Radiology Images and Radiology Device Data – Premarket Notification [510(k)] Submissions
Computer-Assisted Detection Devices Applied to Radiology Images and Radiology Device Data – Premarket Notification [510(k)] Submissions
CADe devices must meet classification requirements under 21 CFR 892.2050, including general and special controls, and require FDA clearance through 510(k) submissions.
Each new CADe device or significant modification must demonstrate substantial equivalence to a predicate device in terms of safety and effectiveness.
Robust testing and validation are necessary, including standalone and clinical performance assessments, to evaluate detection accuracy and false positive rates.
Devices with substantive technological differences or new intended uses may require clinical performance assessments.
Enrichment strategies for study populations (e.g., including challenging cases) are encouraged but should not bias performance evaluations.
Recommendations
Clearly describe the CADe algorithm, training datasets, scoring methodologies, and intended use in premarket submissions.
Conduct standalone performance assessments to measure detection accuracy and generalizability.
Compare new devices to predicate devices whenever possible, using consistent datasets and methodologies.
Develop and submit user training materials that address expected device performance, limitations, and appropriate usage scenarios.
Provide comprehensive labeling, including indications for use, directions, warnings, precautions, and performance metrics, to ensure clinician understanding and appropriate application.
Regulatory Considerations
All CADe devices under 21 CFR 892.2050 must comply with 510(k) premarket notification requirements, including general and special controls.
Changes to CADe algorithms or device characteristics must be evaluated for significant impact on safety and effectiveness, potentially requiring new submissions.
Devices with altered indications for use or significant technological differences may need additional clinical performance studies to demonstrate substantial equivalence.
Labeling must comply with 21 CFR Part 801 and provide sufficient information to describe the device, its intended use, and directions for use.
Manufacturers should consult FDA for guidance on substantial modifications or unique device characteristics.
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.
Case Study: Developing Novel Endpoints Generated Using Digital Health Technology: Diabetes Mellitus
Case Study: Developing Novel Endpoints Generated Using Digital Health Technology: Diabetes Mellitus
Traditional endpoints like HbA1c are insufficient to assess hypoglycemia's impact on quality of life and daily function for diabetes patients.
CGM offers continuous, objective glucose monitoring, enabling the detection of glycemic variability and hypoglycemic episodes in real-time.
Stakeholders, including regulators, industry, and patients, emphasize the need for CGM-derived endpoints to complement traditional biomarkers.
Challenges include standardizing hypoglycemia definitions, creating shared databases for CGM data, and addressing technical limitations at lower glucose levels.
Patient-reported outcomes (PROs) combined with CGM data can provide a comprehensive view of treatment effects but require further validation.
Recommendations
Establish consensus definitions of hypoglycemia and standardized metrics for CGM-based endpoints, such as percent reduction in hypoglycemia duration or frequency.
Create shared CGM databases to facilitate data analysis and validation of novel endpoints across clinical trials.
Conduct CGM-based studies to correlate hypoglycemia metrics with meaningful patient outcomes, including wellness, disease burden, and functional impacts.
Integrate CGM endpoints into regulatory submissions alongside traditional measures like HbA1c to demonstrate comprehensive treatment effects.
Collaborate with stakeholders to address technical challenges, such as CGM accuracy at lower glucose levels, and explore their application in pediatric populations in the future.
Regulatory Considerations
Validate CGM-derived endpoints to align with regulatory requirements, demonstrating their predictive value for severe hypoglycemia and other meaningful outcomes.
Engage regulators early to ensure CGM metrics complement existing endpoints like HbA1c and address unmet needs in diabetes trials.
Address technical limitations, such as CGM calibration and data accuracy at low glucose levels, to meet evidentiary standards for clinical trial endpoints.
Develop and document statistical methodologies for analyzing CGM-derived endpoints, including handling missing data and variability.
Include patient-reported outcomes and quality-of-life measures to contextualize CGM data in 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.
Case Study: Developing Novel Endpoints Generated Using Digital Health Technology: Heart Failure
Case Study: Developing Novel Endpoints Generated Using Digital Health Technology: Heart Failure
Existing PROs for HF, such as KCCQ and MLHFQ, are insufficiently sensitive and rely on subjective assessments.
Accelerometer technology offers objective and continuous real-world data that may better capture patient activity and health.
Novel endpoints must be validated through analytical and cross-sectional studies, correlating "time walking" with HF severity and clinical outcomes.
Developing and validating these endpoints is more feasible for patients with NYHA class II/III HF due to their moderate activity levels.
Future refinements and central databases of accelerometer data will enhance endpoint development and application.
Recommendations
Use accelerometer-derived metrics, such as "time spent walking per day," as novel endpoints to complement traditional clinical measures.
Validate novel endpoints through controlled and real-world studies, including correlating them with existing HF measures and clinical outcomes.
Include accelerometer endpoints in exploratory analyses within ongoing HF trials to gather supportive data without requiring regulatory submission.
Establish data standards and centralized databases for accelerometer-derived endpoints to streamline future development.
Collaborate across stakeholders, including patients, clinicians, investigators, and regulators, to align endpoint development with real-world applicability and regulatory requirements.
Regulatory Considerations
Demonstrate that accelerometer-derived endpoints reflect meaningful changes in patient health and correlate with established HF measures.
Validate endpoints in diverse patient populations and real-world settings to support generalizability and regulatory acceptance.
Address missing data and potential biases in accelerometer readings during endpoint analysis and validation.
Ensure endpoints align with regulatory trial design and analysis standards, including blinding and pre-specified analytical plans.
Develop frameworks for incorporating accelerometer-based endpoints into regulatory submissions alongside traditional clinical outcomes.
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.