Product management and strategic ownership
Kevin’s role spanned product management, strategy, negotiations, and vendor management for CGM research at Ultragenyx. He translated metabolic-study needs into product and operational requirements, evaluated acquisition paths and build-versus-buy options, led Dexcom licensing negotiations, and managed IQVIA’s responsiveness to study requirements.
His remit also included research UI/UX, GCP-oriented requirements, development execution and oversight, hardware logistics tracking requirements, and technical education around data completeness and physiological plausibility. The role connected product decisions with partner access, research operations, quality expectations, and vendor accountability. These are responsibilities Kevin identifies in his career account; the engineering, clinical, data, quality, and study work involved multiple contributors.
The clinical technology problem
Kevin served as Ultragenyx’s subject-matter expert for CGM and wearable-device work across metabolic and gene-therapy programs. The research problem extended beyond obtaining a glucose value: study teams needed an appropriate acquisition path, participant interaction, data timing, and an operating model that could support protocol requirements.
He identified an opportunity to use Dexcom’s Bluetooth-enabled reference application to communicate directly with the body-worn sensor. This was a concrete integration strategy involving the manufacturer’s application and sensor connection, with licensing, product adaptation, research requirements, and vendor decisions considered together.
Licensing and the direct sensor connection
Kevin led the licensing work with Dexcom for its Bluetooth-enabled reference application and the strategy and execution for direct sensor integration. His career account identifies work with Don Browne and other colleagues on the application and data path. The contribution combined access to the manufacturer’s reference implementation with the ability to shape a research-specific mobile experience.
Kevin describes the conventional cloud-access option evaluated for this work as a retrospective API with approximately three hours of delayed data access. The licensed reference application instead communicated directly with the sensor over Bluetooth. This distinction concerns where data are acquired and which application controls the sensor-facing workflow, as well as timing.
He identifies the work as an uncommon integration opportunity. The archive does not assign a numerical rarity claim or imply exclusive access. Dexcom has also offered real-time Partner Web APIs to invited developers, as its linked announcement explains. The three-hour comparison therefore describes the retrospective option evaluated in Kevin’s account, not every Dexcom API or current partner arrangement. A cloud API and a licensed direct sensor connection remain distinct integration approaches.
Application adaptation for metabolic research
Kevin directed the stripping down and adaptation of the reference application’s UI/UX around study needs and GCP requirements. His work joined product insight, integration strategy, execution, and oversight of the changes needed for the intended research workflow. Colleagues and specialist functions contributed implementation and clinical, data, and quality expertise.
The direct sensor path and application work helped guide the approach to metabolic-disorder research. They provided a basis for evaluating how sensor information, mobile behavior, participant interaction, and research requirements should fit together. GCP-oriented optimization was a design objective; the record does not establish completed production validation, certification, or approval of the adapted application.
Quality judgment around missing CGM data
Kevin challenged a QA expectation of 100% data completeness based on a sensor reading every five minutes. In the discussion he describes, a two-hour interval of missing data was treated as requiring a corrective and preventive action, or CAPA. He argued that this kind of gap could be inherent in the product’s stated design and should not automatically be classified as a CAPA event solely because readings were absent.
The contribution was the technical and operational reasoning he brought to the quality discussion: distinguish the device’s documented behavior and limitations from the completeness assumption being imposed on it. The account does not establish that QA accepted his position, that a specific CAPA was closed, or that every two-hour gap is acceptable in every study. This discussion should not be read as evidence that the reference-app integration reached production.
Physiological plausibility and sensor-data accuracy
Kevin also educated colleagues on physiological plausibility when assessing CGM data accuracy. His account describes using the expected behavior of glucose and the timing of sensor readings to question abrupt changes that might represent suspect sensor data. The contribution joins device knowledge, interpretation of data timing, and practical communication with quality and research stakeholders.
The documented experience is the reasoning and education he contributed. A precise numerical rate-of-change cutoff is not asserted here: the units, sampling interval, supporting study, and applicable population need to be established before such a threshold can be used as a data-quality rule. The record does not claim that he independently validated a physiological limit or deployed a clinical decision algorithm.
Hardware logistics tracking requirements
Kevin also created requirements and provided oversight for a hardware logistics tracking system. That responsibility extended the integration problem into the physical equipment and operational dependencies around research. The supported contribution is requirements ownership and oversight, alongside the sensor and mobile-application work.
His broader Innovation Lab service model included study loaner devices, wireless connectivity, site training, informatics, and patient/site support. Those organizational responsibilities provide operating context. They are not evidence that this specific Dexcom integration or the logistics tracking system reached production.
Strategic investment and the IQVIA performance outcome
Kevin describes spending approximately $150,000 on internal development to create a credible replacement alternative for an approximately $2.5 million IQVIA engagement. The work included the mobile app and cloud application developed as part of Rarify for the Dexcom sensor workflow. He used the threat of vendor replacement to improve IQVIA’s performance and responsiveness to study requirements.
Those mobile and cloud components did not enter production, but they served their strategic purpose: they made in-house replacement credible and strengthened Kevin’s negotiating position with the incumbent vendor. The outcome belongs to product strategy, investment judgment, negotiations, and vendor management as well as technology development. Production deployment was not necessary for that reported vendor-management result.
The amounts and performance outcome are Kevin-reported. The approximately $2.5 million figure describes the vendor engagement, not money saved. The account does not establish quantified savings, a measured ROI, actual replacement of IQVIA, or termination of its contract. The non-production qualification applies to these specific Dexcom-related Rarify mobile and cloud components; it does not describe the maturity of the broader Rarify platform.
IQVIA sensor data and the GSDIa approval
Kevin reports that the data supplied through IQVIA from Dexcom sensors contributed to the clinical evidence supporting FDA approval of the gene therapy for glycogen storage disease type Ia (GSDIa, also written GSD1a). This adds a downstream regulatory milestone to the study-technology and vendor-management context of his work. The contribution concerns the IQVIA data route, separate from the in-house reference-app integration that never entered production.
FDA confirms accelerated approval of Genglycos on August 19, 2026. Ultragenyx identifies the therapy as DTX401 and the supporting Phase 3 GlucoGene study. The approved indication is reduction of daily cornstarch intake as an adjunct to nutritional management in adults and children aged eight years and older with GSDIa. FDA identifies reduced cornstarch intake as the surrogate endpoint supporting accelerated approval; confirmation of clinical benefit is required.
The public announcements establish the approval and study context. They do not identify IQVIA, Dexcom, or Kevin’s individual role in the data contribution. That specific connection is recorded as Kevin’s firsthand account. It does not establish that CGM data alone secured approval, that the CGM measure was the approval’s primary endpoint, that Kevin owned the regulatory submission, or that his non-production application generated the submitted data. The trial and approval reflect the work of participants, families, investigators, sponsor teams, vendors, and other contributors.
Sugar Surfing and Dexcom’s educational purchases
Kevin also co-authored Sugar Surfing with Stephen W. Ponder. He reports that Dexcom purchased the book in bulk to educate its sales representatives and give copies to prescribing endocrinologists. This provides a separate Dexcom relationship through educational publishing and distribution. The Sugar Surfing record describes that contribution and its continuing patient/provider impact. These purchases are Kevin-reported; they should not be conflated with his Ultragenyx licensing and research-integration responsibilities.
What the experience demonstrates
The experience connects licensing and partner access, direct Bluetooth sensor integration, research UI/UX, GCP requirements, hardware logistics requirements, and build-versus-buy execution. It is relevant to evaluating connected clinical products, biosensor partnerships, metabolic-research technology, and vendor accountability.
Kevin’s contribution was the insight, strategy, licensing, execution leadership, and requirements and oversight he supplied within collaborative work. The reference application and sensor technology originated with Dexcom. This record does not imply that Kevin invented the sensor, independently coded every component, or held sole medical responsibility for the use of the data.
The project, IQVIA responsiveness outcome, and specific IQVIA/Dexcom data contribution are described from Kevin’s career account and experience clarification. The public sources supply technical market context and verify the Genglycos approval milestone; they do not independently verify his license, implementation, or individual contribution.
Sources and record basis
- Technical market contextDexcom · Real-time Partner Web API announcement
Dexcom’s announcement describes real-time API access for invited third-party developers. It establishes that API access arrangements vary; it does not verify Kevin’s reference-app license, direct Bluetooth integration, or vendor-management outcome.
- Regulatory milestoneFDA · Genglycos accelerated approval for GSDIa
FDA confirms accelerated approval on August 19, 2026, based on reduced daily cornstarch intake. This announcement does not name IQVIA, Dexcom, or Kevin; the specific data-provider contribution is Kevin-reported.
- Clinical program contextUltragenyx · Genglycos (DTX401) approval and clinical program
Identifies Genglycos as DTX401 and the Phase 3 GlucoGene trial supporting accelerated approval. It does not independently verify the IQVIA/Dexcom data path or Kevin’s individual responsibilities.
Kevin’s account supports CGM product management, strategy, Dexcom licensing negotiations, IQVIA vendor management, direct Bluetooth integration development, research UI/UX and GCP requirements, and hardware logistics tracking requirements and oversight. The in-house reference-app integration was not deployed in production. He reports using that alternative to improve IQVIA’s responsiveness and reports that IQVIA’s separate Dexcom sensor data contributed to evidence supporting Genglycos’s FDA accelerated approval for GSDIa. Public sources confirm the approval milestone, not the specific IQVIA/Dexcom contribution or Kevin’s individual role. The account does not establish submission ownership, sole responsibility for approval, actual vendor replacement, quantified savings, or production validation of the in-house app. The three-hour comparison concerns the historical cloud-access option evaluated, not every Dexcom API. BEYONDXLH remains a separate XLH record. The BEYONDXLH record documents XLH research; it does not establish Dexcom CGM use in that program. The record supports physiological plausibility assessment of CGM data. It does not establish a universal numerical rate-of-change limit or a validated cutoff. Challenged automatic CAPA for a two-hour CGM data gap, citing product-design limitations; the account does not establish QA’s final disposition. Kevin reports approximately $150k development spending and a roughly $2.5M IQVIA engagement. The engagement value is not savings; measured ROI or quantified savings are not established. Dexcom-related Rarify mobile/cloud components created a credible IQVIA replacement threat; they did not enter production. That does not establish non-production status for Rarify’s broader platform. The in-house app did not enter production. Kevin attributes the GSDIa study-data contribution to IQVIA’s Dexcom route; this does not establish app-generated submission data. FDA identifies cornstarch reduction as the approval endpoint. Kevin reports IQVIA/Dexcom data contribution; this does not establish sole credit, submission ownership, or FDA verification of his role. Kevin reports IQVIA’s Dexcom data supported Genglycos’s FDA accelerated approval for GSDIa. This does not establish production deployment of his separate in-house app or submission ownership. The licensed Dexcom Bluetooth reference-app integration did not enter production. GCP-oriented adaptation is documented; completed production validation or certification is not established. The non-production Dexcom integration improved IQVIA’s responsiveness, according to Kevin’s account. Actual vendor replacement, contract termination, and quantified savings are not established. Kevin reports IQVIA/Dexcom data supported Genglycos’s GSDIa program. FDA confirms accelerated approval based on cornstarch reduction; this does not establish Kevin’s submission ownership. Kevin reports Dexcom bulk purchases of Sugar Surfing for education. That does not establish Dexcom employment, device-sales responsibility, sales quotas, or ADMS trial outcomes. The archive documents collaborative CGM integration and education. It does not establish invention or independent engineering of a CGM sensor. Kevin reports IQVIA/Dexcom data contributed to Genglycos’s accelerated approval. FDA confirms the milestone; its announcement does not verify his role or establish submission ownership.