d-Nav System

The d-Nav System is a prescription software designed to optimize insulin management for adults with Type 2 diabetes by providing personalized insulin dose recommendations via a mobile application. Its methodology relies on an HCP-configured, algorithm-driven approach that analyzes blood glucose trends against target ranges, offering different treatment plans and leveraging local or cloud-based processing for dose calculations and instruction updates.

The d-Nav System is a prescription-only software device designed for adults with Type 2 diabetes to aid in optimizing insulin management. It consists of two main software elements: a Phone App for patients and a Website for Health Care Providers (HCPs). Patients use the Phone App on a mobile device to input blood glucose data (manually or automatically from a linked glucose meter via the cloud) and receive recommended insulin doses. HCPs, after training, use the d-Nav Website to configure the patient's Phone App, setting up physician-prescribed, patient-specific starting insulin dose instructions, including the treatment algorithm (treatment plan), insulin drug, and initial doses. The core of the system is the d-Nav Get-Dose Library, which calculates the next insulin dose; its "Recommend Dose" function is local on the phone, while the "Update Insulin Instruction" function can be local or cloud-based across four different operational models. The d-Nav System's methodology integrates HCP-prescribed starting parameters with automated dosing guidance. This guidance is based on comparing regularly measured blood glucose data trends against a device-specified target range, which is fixed based on the chosen treatment plan (basal, twice daily mixed, basal-bolus, or basal-bolus with carbohydrate counting). The dosing algorithm adjusts insulin doses based on these trends: decreases can be daily, while increases occur no more frequently than weekly. For dose decreases, it uses a single dose response, and for both increases and decreases, it can use an average response to similarly timed doses over a one-week period. The system includes safety checks, such as limits on dose adjustments (generally ≤ ±20%, with exceptions for basal-bolus plan increases up to <+30%) and halting titration if doses deviate significantly or exceed HCP-set thresholds. The architecture involves a mobile phone app (iOS/Android), a cloud-based d-Nav System Server (on AWS) housing databases and webservices, and options for local or cloud-based storage and processing of the Get-Dose Library functions.

AI Regulatory Concerns

Powered by

Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.

• Q1. How does the d-Nav System's algorithm for weekly average response compare in glycemic control efficacy and patient adherence to systems using only single-dose response calculations for insulin adjustments in Type 2 diabetes patients?; What are the specific safety thresholds and deviation percentages that trigger a halt in titration, and how were these determined to ensure patient safety across different treatment plans?; In real-world usage, what is the typical latency for insulin instruction updates when the "Get-Dose Library Update Insulin Instruction" function is cloud-hosted, and how does intermittent cloud connectivity impact dose recommendation accuracy and timeliness?; What human factors were identified as most critical during usability testing for both the patient Phone App and the HCP Website, particularly regarding the setup of complex treatment plans like basal-bolus with carbohydrate counting?; Given that changes in insulin dose recommendations can be sent to the patient without immediate prescriber concurrence, what mechanisms or alerts are in place for HCPs to monitor and intervene if a patient's glucose trends or dose adjustments become concerning?