The complete record.

The mandate

Ultragenyx needed patient- and site-facing digital capabilities that could support unusual rare-disease research requirements and operate within a regulated clinical environment. Kevin joined in January 2019 and founded the Innovation Lab within Global Development Operations. His initial work included longitudinal research and patient-reported data in X-linked hypophosphatemia. He turned the opportunity for better digital patient engagement into an executive business case for an internal development capability.

The resulting organization combined the work normally spread across product teams, technology vendors, validation functions, and participant-support operations. Kevin’s remit extended from deciding what to build to ensuring that studies, sites, patients, and support teams could use it.

Organization and financial responsibility

Kevin recruited, organized, and led a distributed team spanning product ownership, business analysis, clinical informatics, solution architecture, software engineering, QA, computer system validation, vendor management, and service delivery. His later career record describes an organization of up to 54 staff. An earlier CV snapshot records 38 people and a $9 million departmental budget; subsequent career materials describe an annual budget approaching $10 million. These are different points in the organization’s development.

He owned prioritization, product roadmaps, resource allocation, operating cadence, delivery accountability, stakeholder engagement, performance management, and executive reporting. The scope required balancing reusable platform investments against study-specific deadlines and the support requirements of systems already in operation.

From an idea to an institutional capability

The Innovation Lab grew from early prototyping and a small internal team into an organization capable of designing, validating, deploying, and supporting clinical applications. Kevin established intake and governance routines, staffed specialist functions, and connected delivery decisions to study needs. He worked across Clinical Development, Clinical Operations, Data Management, QA, Vendor Performance Management, and external partners.

His leadership included mentoring colleagues to conduct buy-versus-build analyses and to source or develop electronic clinical outcome assessment capabilities. Establishing the function meant creating an operating model for repeated delivery rather than treating every study as an isolated software project.

Clinical and executive interfaces

Kevin participated in Operations Leadership and Strategic Leadership teams and served as a technology-feasibility representative on protocol development teams. His contributions addressed endpoint strategy, participant and site experience, operational risk, device integration, and the feasibility of turning scientific requirements into usable systems. His reporting line sat within Global Development Operations.

The organization supported natural-history and disease-monitoring work, Phase II–III interventional trials, and Phase IV programs. Rarify became a central example of the internal platform strategy. The broader portfolio included metabolic and bone diseases, connected devices, participant engagement, and near-real-time clinical and operational data.

Results and operating significance

The career record documents deployment of Rarify, expansion of service delivery, and a pre-pivotal Phase III audit of the digital clinical environment with zero findings. The audit result is reported in Kevin’s career documents; the underlying audit report is not a public attachment.

This work demonstrates responsibility for organizational design and sustained execution in addition to technology strategy. It connects the executive questions—investment, staffing, priorities, governance, and delivery performance—to the practical questions of how a participant uses a device, how a site receives data, and how a quality team evaluates a release.

The problem to solve

Rare-disease protocols can require participant interactions and measurements that do not fit comfortably into a generic electronic data-capture workflow. The challenge is broader than creating a questionnaire: the scientific intent has to survive patient burden, site practice, device behavior, data timing, and operational support. Kevin developed Rarify within Ultragenyx to bring these needs into a coordinated platform and delivery model.

Kevin’s contribution

Kevin created the strategy and business rationale for the internal capability, shaped the product vision and roadmap, and led the organization responsible for development, quality, deployment, and support. He coined the Rarify name and built the operating relationships with study teams and internal stakeholders. His scope included staffing, budgeting, SOP development, external services, intellectual-property coordination, and study-team alignment.

He did not treat the application as a stand-alone software release. The delivery model incorporated participant and site workflows, training, loaner-device logistics, connectivity, support, data management, and informatics. Those functions were part of making the clinical platform usable in practice.

Data and workflow architecture

Rarify supported collaborative web-based data capture by patients and site personnel, patient-reported information, clinical observations, and connected-device workflows. Application materials describe near-real-time collaboration for metabolic monitoring, ePRO collection, and study decision support. The architecture connected the people generating information with those responsible for reviewing and acting on it.

The platform used reusable software components and agile delivery to support varying study needs. Kevin’s CV describes a React-based application environment and computer software assurance practices. The important operating principle was repeatability: a shared foundation could support protocol-specific behavior while keeping quality and support responsibilities visible.

Study portfolio and execution

The Innovation Lab’s work included natural-history studies, longitudinal disease-monitoring programs, and interventional research. Rarify applications supported rare metabolic and bone-disease programs, with an EMEA pivotal Phase III application described in the 2024 CV. The wider organization supported Phase II–III trials and Phase IV work.

During the COVID period, Kevin’s organization integrated remote engagement, telehealth workflows, endpoint-data capture, participant feedback, device logistics, and support. The work connected study execution to what participants and sites could actually sustain outside conventional visits.

Quality and lifecycle ownership

QA, validation, change management, service expectations, and operational risk were incorporated into the delivery organization. Kevin worked with Quality Assurance and study stakeholders to align development choices with regulated use. The pre-pivotal Phase III audit with zero findings is part of his documented career account.

Lifecycle responsibility included deciding which capabilities were worth building, setting acceptance expectations, deploying into studies, learning from use, and maintaining support. A capability that met a demonstration requirement still had to function for sites and patients over time.

Dexcom mobile and cloud components: strategic purpose

As part of Rarify, Kevin led product strategy and development of mobile and cloud applications for a Dexcom sensor workflow. These particular components did not enter production. According to his account, approximately $150,000 in internal development created a credible threat of replacing an approximately $2.5 million IQVIA engagement and improved the vendor’s performance against study requirements. The components served that strategic vendor-management purpose. This is a component-specific maturity statement, separate from Rarify’s other operational applications; the vendor engagement value is not a savings figure.

What the work establishes

Rarify connects product leadership, clinical systems, operating-model design, global delivery, and patient-data strategy in one substantial project. It demonstrates experience taking an internal clinical technology capability from a business case into regulated operational use. Public LC-FAOD publication evidence supports Kevin’s participation in the associated rare-disease research environment; it does not replace the internal records for every Rarify feature or result.

Scope of the work

Kevin’s Ultragenyx remit included electronic clinical outcome assessment and electronic patient-reported outcome capabilities supporting Phase II–III research and Phase IV programs. He founded and mentored the Innovation Lab to assess whether a requirement should be met through an external product, an internal application, or a combination of capabilities.

His experience joins endpoint and protocol discussions to the operational detail of patient and site data capture. It includes product ownership, requirements, vendor governance, development oversight, quality, validation, training, support, and continuing improvement.

Connecting an endpoint to a usable workflow

The relevant design work began with the clinical need and the intended users. Kevin served on protocol development teams where technology feasibility, endpoint strategy, patient burden, site practice, and operational risk had to be considered together. His organization translated those requirements into data-capture experiences and the associated support model.

A survey is only one part of that system. The participant must receive the right request, understand what to report, have a workable device and connection, and know where to obtain help. The site and study team must be able to recognize missing information and distinguish a data problem from a workflow problem. These are the operating concerns his platform and service-delivery work addressed.

Sourcing and development leadership

Kevin led vendor evaluation and governance while also building an internal alternative. This gave his team responsibility for examining functional fit, implementation effort, the quality system, integration needs, support obligations, and the total operational burden of a solution. His role included mentoring others in the analysis rather than keeping every decision at department-head level.

For internally developed applications, the organization provided product, engineering, QA/CSV, informatics, and service delivery. For external capabilities, Kevin coordinated expectations with regulated technology partners and internal quality and study stakeholders.

Relevant delivery evidence

Rarify is the principal platform example. It brought patient- and site-reported information into a collaborative clinical environment, alongside metabolic monitoring and connected-device data. The Innovation Lab supported validation and release readiness, and extended service delivery to training, participant/site support, and device logistics.

The evidence establishes leadership of eCOA/ePRO technology selection and execution. It should not be interpreted as a claim that Kevin personally developed every clinical instrument, performed psychometric validation, or served as the statistical authority for the endpoints.

Why this experience transfers

Electronic outcome-assessment programs need someone who can connect clinical purpose, product choices, vendor obligations, and real-world participation. Kevin has led the organization performing that work and has managed its financial, technical, and service dimensions. The combination is particularly relevant when a sponsor is establishing a new function, reviewing its vendor model, or introducing data collection that crosses patient, site, and device boundaries.

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.

Program context

BEYONDXLH was an Ultragenyx-sponsored disease monitoring program involving the XLH Network as co-sponsor and Yale as the centralized research site. Kevin’s career record places his work from January 2019 through December 2023. The program formed part of his early sponsor-side responsibility for longitudinal clinical research and patient self-reported data.

Kevin’s responsibilities

Kevin’s documented work includes study leadership, design enhancements, compliance oversight, procedure development, system testing, data analysis, data-loss prevention, and program improvements. His later responsibilities included mentoring the lead study manager. These roles combined program management with technology and data-quality judgment.

Working across internal stakeholders, research investigators, research associates, technology vendors, and patient-community organizations required a shared understanding of what participants were being asked to do and how that effort supported the research objective.

Patient and site experience

Longitudinal programs depend on participants being able to keep contributing information as their circumstances change. Kevin’s work emphasized patient-facing data capture, collaborative site workflows, and operational feedback. The systems had to fit participants’ lives while also supporting research procedures and data continuity.

The involvement of an advocacy organization and an academic research partner is significant: participant engagement, scientific requirements, and sponsor execution had to remain aligned. Kevin’s wider Ultragenyx work also included structured patient-community consultation under compliance oversight.

Connection to the Innovation Lab

Experience with these research requirements helped Kevin identify the value of a reusable internal clinical technology capability. His CV describes development of a strategic plan, early prototypes, and executive approval to establish the Innovation Lab. BEYONDXLH therefore connects direct study work with the later platform and organization-building story.

Rarify and the broader clinical technology portfolio expanded the ability to support patient and site collaboration, longitudinal collection, and varied protocol needs.

Evidence and scope

The responsibilities and dates above come from Kevin’s career documents. They establish his contribution to the program; they do not imply authorship of every XLH publication or ownership of the medical conclusions. Public author-credit evidence in this archive is strongest for the separate LC-FAOD disease-monitoring abstract, which is identified separately.

Breadth of disease and study context

Kevin’s Ultragenyx record includes work related to X-linked hypophosphatemia, glycogen storage disease types Ia and III, and long-chain fatty acid oxidation disorders. The clinical technology portfolio crossed natural-history research, longitudinal monitoring, interventional trials, and post-marketing work. Scientific and therapeutic programs varied; Kevin’s contribution centered on the systems and operating model for collecting and using information.

His CV describes work involving gene-therapy and mRNA research contexts as well as metabolic monitoring. The breadth matters because the technology requirements had to be evaluated against the particular protocol and participant experience rather than imposed as a uniform digital template.

What Kevin led

Responsibilities included patient/site workflows, device and biosensor integration, technology feasibility, platform strategy, quality and validation coordination, data informatics, and service operations. He helped translate protocol intent into operational requirements and coordinated the functions needed to deliver them.

The data environment included patient-reported information, clinical observations, biometrics, endpoint-related data, and measures of study activity. Each type of information carried a different meaning and required an appropriate route into review and action.

LC-FAOD publication trail

The ACMG 2021 supplement of Molecular Genetics and Metabolism includes abstract eP029, describing a long-term, prospective, multicenter, in-clinic and online disease monitoring program for LC-FAOD. Kevin McMahon appears in the author group. The DOI is 10.1016/S1096-7192(21)00116-5.

This is public evidence of contribution to the disease-monitoring research program. It is a conference abstract rather than a full clinical outcomes paper. It should not be extended into unsupported claims about authorship on unrelated disease programs or the efficacy of a therapy.

The longitudinal operating problem

Disease monitoring asks an organization to sustain data collection beyond a single encounter. Patient contact, usable workflows, clinical relevance, support, and continuity of data become part of the research infrastructure. Kevin’s experience joins those requirements to the sponsor’s need for oversight, quality, and coordination.

The same experience is relevant when teams assess the feasibility of a rare-disease network, participant recontact, patient-generated information, or long-term follow-up.

The remit

Kevin established a clinical systems data informatics function within the Ultragenyx digital clinical organization. His responsibilities included business intelligence, data forensics, data-quality monitoring, operational insight, and decision support. The work addressed how information generated through patient-facing systems, connected devices, sites, and delivery operations could become usable across different teams.

Data as an operating product

His career materials describe reusable data structures, business rules, measures, metadata, provenance, and governed consumption patterns. These elements allow teams to understand what a value means, where it came from, how it has changed, and what decisions it can support. The approach connects product design to the integrity of the information produced by the product.

Patient-reported information, device readings, clinical data, and workflow status are not interchangeable. Kevin’s role was to connect them with enough context to preserve their meaning and to make differences in quality or timing visible to the people using the data.

Quality and feedback

The organization used workflow analysis, KPI monitoring, user feedback, and iterative product improvement to address adoption and completeness. Later career materials report approximately 30% improvement in utilization and data completeness relative to vendor alternatives. The available career records do not include a public metric specification, denominator, study-level breakdown, or independent validation of that figure. It is therefore a reported operating result, not a clinical effect estimate.

The more fully documented responsibility is the creation of the function and its working relationship with product, operations, engineering, quality, and study teams. Those relationships enabled the organization to investigate whether an apparent data problem originated in a device, interface, process, or participant-support gap.

Governance and consumption

Kevin coordinated with Data Management, Clinical Development, QA, vendors, and technology teams. His role included defining business expectations and practical controls around the information the clinical platform produced. Governance was tied to use: different consumers needed different views, responsibilities, and escalation paths.

This work informed his later Operational Telemetry framework, which places trusted and curated data ahead of cross-system signal generation. The later framework is a design proposal; the clinical informatics function described here was part of his employer-side operating experience.

Where this experience is useful

The combination is relevant to patient-data product leadership, digital clinical development, data-quality operations, and organizations trying to connect patient-generated information with research and service decisions. Kevin’s role is strongest in product and operating architecture, interdisciplinary translation, and governance.

A career spanning both sides of the decision

Kevin has built products, sold platforms, formed commercial partnerships, led internal technology organizations, and managed external vendors. That combination gives him experience with the incentives and obligations on both sides of a sourcing decision. His early finance, audit, procurement, and vendor-management work at GTE provided an operational foundation; later roles added enterprise commercialization and regulated clinical delivery.

Ultragenyx sourcing responsibilities

At Ultragenyx he led vendor selection and performance governance across regulated technology partners and worked with quality agreements and operational expectations. The portfolio included clinical data, patient-facing capabilities, eCOA/ePRO, connected devices, and supporting services. He coordinated with Clinical Development, Data Management, QA, and Vendor Performance Management.

Kevin also founded and mentored the internal organization that could build selected capabilities. This allowed sourcing analysis to consider a real internal delivery option, including the staffing, validation, support, and lifecycle responsibilities it would require.

A concrete in-house alternative for IQVIA

Kevin led licensing and adaptation of Dexcom’s Bluetooth reference application for direct communication with the body-worn sensor, with research UI/UX and GCP requirements informing the work. The integration was not deployed in production. Its value included making an in-house development alternative credible in vendor discussions.

According to Kevin’s account, he used the possibility of replacing the external solution to improve IQVIA’s responsiveness to study requirements. The supported result is that reported responsiveness improvement, rather than an assertion that IQVIA was replaced or a quantified cost saving was achieved.

What the decision had to cover

His documented work connects clinical need, target users, workflow integration, technical feasibility, regulatory considerations, evidence requirements, adoption measures, and business rationale. The decision could not rest on a demonstration alone. A product had to fit the study’s timing, data needs, users, support model, and quality environment.

Internal development likewise required more than engineering capacity. Product ownership, QA/CSV, service delivery, vendor dependencies, maintenance, and change management had to be funded and organized. Kevin’s departmental budget and portfolio responsibilities made those costs part of the same decision.

Commercial and enterprise foundation

Earlier roles included RFP response leadership and complex enterprise deals. His career record includes a $9 million prepaid platform deployment with Optus Australia and a $3 million strategic partnership with Amdocs at Vitria. The amounts are career-reported transaction values, not published financial disclosures linked in this archive.

At Diabetech, he combined product development with partnerships involving device companies, telecommunications firms, payers, providers, academic collaborators, and public programs. The relationships had to connect technical capability to an operating and commercial model.

Management implications

Kevin’s strongest contribution is connecting the purchase or build decision to what the organization must operate afterward. That includes ownership, workflow compatibility, performance expectations, accountability, and risk. The same experience is applicable to platform rationalization, upstream innovation, partner assessment, and establishment of a new clinical technology function.

Quality as part of the operating organization

Kevin’s Innovation Lab included QA and validation specialists alongside product, engineering, informatics, and service delivery. The organization was responsible for clinical systems used by patients and sites, so quality work had to accompany requirements, development, release, and ongoing support. Kevin’s role was to establish the organization and maintain alignment between clinical use, delivery, and quality expectations.

Device behavior and proportionate quality response

Kevin’s CGM experience includes challenging an automatic CAPA response to a two-hour data gap when he understood such gaps to be inherent in the product’s stated design. QA’s completeness assumption expected 100% of readings at five-minute intervals. He brought device knowledge and research-operating judgment to the discussion about whether the gap represented expected behavior or a quality event requiring corrective and preventive action.

This is a record of the position Kevin argued. It does not establish QA’s final disposition, closure of a CAPA, or a general exemption for missing CGM data. The related Dexcom reference-app integration was not deployed in production.

Documented responsibilities

His career documents describe SOP development, QA/CSV, computer software assurance, vendor governance, change management, validation workstreams, and operational-risk routines. He worked with Quality Assurance rather than treating the function as an after-the-fact sign-off. The organization’s service responsibilities also made training, support, and the handling of changes part of the delivery model.

The relevant experience includes GCP systems and electronic clinical records. References to regulated-system requirements describe the environment in which he led delivery; they are not offered as a legal determination that every system or later design satisfies a particular regulation.

Audit outcome

Kevin’s CV and subsequent career materials report a pre-pivotal Phase III audit of the digital clinical environment with zero findings. The CV also describes expanded autonomy for the Innovation Lab QA lead following the audit. The underlying report is not published in this archive.

The result is tied to the audited environment and point in time. It is not a claim of FDA approval of Rarify, an assertion that all products passed every audit, or a guarantee of future compliance. The useful evidence is that Kevin helped establish an organization able to deliver a clinical platform and prepare its operating environment for scrutiny.

Governance across internal and external delivery

Kevin worked with regulated vendors under formal quality and performance expectations. Internal and external capabilities had to be coordinated around intended use, study needs, change management, and ownership. This responsibility connects to his buy-versus-build work: whichever delivery route was chosen, the sponsor still needed a workable quality and support model.

His later AI and Operational Telemetry designs carry forward the same concern for traceability and human decision rights. Those later designs remain separately labeled as exploratory or conceptual; they do not inherit the validation status of the Ultragenyx environment.

Leadership relevance

The experience is applicable when an organization must connect software delivery to clinical use without losing clarity about who owns requirements, validation, release, and operation. Kevin’s contribution is executive and cross-functional leadership grounded in an actual digital clinical organization, with specialist quality professionals embedded in the work.

The service obligation

Deploying a clinical application creates a continuing obligation to the people using it. Kevin expanded the Innovation Lab’s service-delivery function to include study loaner devices with global wireless data, site training, real-time informatics, and direct support for patients and sites. His organization brought these responsibilities into the platform operating model.

What the organization covered

The team included product ownership, business analysis, engineering, quality, validation, vendor management, informatics, and service operations. Later records describe up to 54 globally distributed staff. Kevin managed operating cadence, performance expectations, prioritization, cross-functional accountability, and executive reporting across this distributed organization.

The service work connected with study teams and external partners. A system could be technically available while a participant could not use it because of a device, connection, training, or workflow issue. Those were delivery concerns that had to be addressed alongside software behavior.

Remote and decentralized study execution

During the COVID period, the team supported decentralized trial execution by combining digital data collection, telehealth workflows, device logistics, participant support, and feedback. Kevin’s record describes near-real-time connections among patients, site personnel, clinical teams, devices, and data workflows.

The underlying operating experience is relevant to distributed care and research because it crosses the digital/physical boundary. Technology selection affects shipping and support; protocol requirements affect participant effort; operational failures affect the completeness and timeliness of data.

Hardware logistics tracking requirements

Kevin created requirements and provided oversight for a hardware logistics tracking system as part of the work around connected clinical research. This is a specific requirements and oversight contribution. The record does not establish production deployment or a measured performance outcome for that tracking system. The related Dexcom reference-app integration likewise remained outside production.

Management and resource allocation

Kevin coordinated portfolio priorities with resources and existing service commitments. His work included vendor expectations, service performance, operational risks, and quality/change-management requirements. The organization had to deliver new capabilities while maintaining the systems already supporting research.

This is part of why his experience extends beyond product strategy into operations. The same leadership function had to connect decisions about the next release with the capacity and accountability required for daily execution.

Evidence of scope

The staffing, budget, and service responsibilities are documented in career records and career materials. The archive does not infer that every person was a direct report or that the organization was a separate commercial CRO. It was an internal sponsor-side clinical technology and operations capability with responsibilities often associated with external delivery organizations.

Origin and company scope

Kevin founded Diabetech after his daughter’s type 1 diabetes diagnosis in 2001. The initial problem was practical: useful glucose information existed with the patient, while parents and other caregivers often received it late or incompletely. His background in mobile platforms and telecommunications provided a foundation for connecting medical devices to remote information and support workflows.

Over the following 17 years, the work evolved from connected telemetry into virtual disease management and broader population-health engagement. The HealthCordia and Healthimo records describe these later phases separately so the development of the business remains visible.

Product and technology leadership

Kevin led hardware, software, and hosted/cloud product development for six wireless diabetes devices, including GlucoMON and GlucoMON-ADMS. His record describes architecture spanning medical-device interfaces, wireless transmission, remote device management, web applications, automated rules, caregiver alerts, and backend analytics.

The objective was to reduce the extra work required to share data and to make timely information available to the people supporting the patient. The product combined physical devices, network services, software, data, and clinical workflows rather than ending at the meter.

Evidence and field operations

The company operated research and care programs involving patients, clinicians, payers, employers, hospitals, and public programs. Kevin’s later career materials describe more than 20 observational, interventional, and population-health studies and programs, and more than $4 million invested in field testing. These are career-reported portfolio figures.

His responsibilities included technology and protocol design, training, support, outcomes analysis, partnership development, and—in selected studies—principal-investigator duties. The 2012 Diabetes Care randomized trial provides a public research example. Contemporary reporting and the patent record establish that the connected-care architecture was being developed well before remote monitoring became a familiar commercial category.

Business and operating model

Kevin owned product, partnerships, commercialization, and business execution. Programs integrated patient identification, enrollment, home diagnostics, device logistics, remote glucose data, support, clinical workflows, payer reporting, and reimbursement-related processes. Partnerships and programs involved organizations such as BellSouth/AT&T, Blue Cross Blue Shield of Texas, McKesson/Texas Medicaid, Kaiser Permanente, NHS collaborators, LifeScan, and regional health systems.

Commercial licensing and platform lineage are described in his career record as progressing through Telcare and BioTelemetry into Philips Virtual Care Management. The archive preserves that account while treating Philips’ current product announcement as market context rather than proof of every historical transaction.

What endured

The recurring principle was to connect observation, interpretation, communication, intervention, and feedback. The architecture made daily patient information useful beyond the device itself. Kevin carried that operating experience into sponsor-side clinical development at Ultragenyx and later work on patient narratives and operational signals.

Diabetech is both a technical origin and an operating-business record. It shows experience building a capability, obtaining partners and users, generating research evidence, and dealing with the practical conditions under which the system had to work.

A connected system around an existing care task

GlucoMON and the Automated Diabetes Management System addressed the work of getting glucose information from daily life into timely family and care-team awareness. Instead of relying entirely on handwritten logs or delayed downloads, the architecture connected a glucose meter to wireless transmission and a hosted information service. Kevin led product architecture, development, commercialization, and deployment into research and care programs.

The operating architecture

The work covered device interfaces, collection of readings, wireless transmission, remote device management, hosted data handling, automated rules, reporting, and notifications. GlucoDYNAMIX supported the backend analysis and feedback environment. Kevin’s patent application describes a wider architecture connecting patients, devices, servers, and management teams.

The system design considered both individual events and longitudinal patterns. It supported delivery of information to caregivers through practical communication channels, with an emphasis on reducing additional participant effort. The specific configuration varied across device generations and programs.

Clinical research use

The 2012 Diabetes Care randomized controlled technology trial evaluated the Automated Diabetes Management System in families of children with type 1 diabetes. Forty-eight children were followed for 12 months. The system automatically collected glucose values and provided parents with recurring trend information. The published study reported better glycemic outcomes in the intervention group, with use frequency relevant to the observed improvement.

Kevin McMahon is a co-author. This evidence supports the particular intervention and population studied. It does not establish that all connected devices or every later program produced the same result.

Public technical record

US20050038680A1 names Kevin McMahon as inventor and records priority in December 2002, filing in February 2004, and publication in February 2005. The application covers remote monitoring, data movement, analysis, communications, and patient-management workflows. It is identified here as a patent application, not an active granted patent.

Contemporary D CEO and David Mendosa reporting provide additional historical accounts of the technology. These sources are useful because they describe the product while it was being introduced, rather than relying only on a later retrospective.

Transferable engineering and product judgment

Kevin’s contribution spans the physical product, the network, the hosted software, the data model, and the human workflow. That combination is relevant to modern connected medical products and sensor-based clinical systems, where a measurement has value only when it arrives reliably and is interpreted in context.

The experience also supplies a foundation for evaluating emerging technology without assuming that connectivity alone creates a useful care intervention. The product must fit the user’s routine and the responsibilities of the people receiving the information.

The product problem

Remote care still needs meaningful measurements. Kevin developed and commercialized HomeCheck-A1c as a way to connect at-home sample collection with laboratory processing and results that patients and care teams could use. The product made the diagnostic workflow part of the larger care program.

What Kevin owned

His career materials describe patient onboarding, home finger-stick sample collection, mail-in logistics, processing through HPLC laboratories, digital results delivery, and follow-up workflows. He connected product design with the commercial and operational conditions needed for actual use.

The service had to span physical and digital tasks: obtaining the kit, understanding the collection process, returning a sample, associating the result with the participant, and delivering the result into the next appropriate interaction. Kevin’s remit included those transitions rather than only the front-end ordering experience.

Place in remote-care programs

Home A1c measurement complemented glucose telemetry and patient-support workflows. It offered a periodic outcome-related measure alongside daily readings and engagement information. Kevin integrated diagnostic and monitoring workflows into payer-, employer-, and patient-facing programs.

In his direct-to-patient work, early practical reinforcement was an important design principle. Participants needed useful feedback that made continued effort meaningful. The diagnostic result could therefore serve an engagement purpose as well as a measurement purpose, while clinical interpretation remained with the appropriate care professionals.

Commercial and operational relevance

This work connects diagnostics product management, logistics, laboratory partnerships, patient communications, provider information, and care-program economics. It is relevant to organizations developing home-based testing, direct-to-patient services, remote research, or diagnostic engagement programs.

The description is based on Kevin’s career account. The distinguishing experience is building and operating the service around the measurement.

Evolution from telemetry to care delivery

HealthCordia represents the phase of Kevin’s work in which connected-device evidence and experience became a broader remote diabetes disease-management service. His career materials describe the BellSouth/AT&T pilot as an important foundation. The business problem expanded from transmitting information to making a complete care model operate around it.

The Diabetech, HealthCordia, and Healthimo dates in the career chronology describe overlapping evolution and primary operating emphasis. They should not be read as three unrelated companies with no continuity or as exact corporate incorporation dates.

Program architecture

Kevin designed infrastructure spanning connected devices, analytics, care kits, supplies, education, diagnostic logistics, participant support, telehealth coordination, and home-based engagement. Programs also required clinician workflows, patient-generated data review, escalation, reporting, and payer/employer interfaces.

This operating scope connected recruitment and enrollment with the work that followed. A participant needed to receive equipment, understand the service, contribute useful information, obtain support, and remain connected to the appropriate care pathway. The clinical and financial organizations needed corresponding visibility and accountability.

Payer and provider environments

Career records describe Blue Cross Blue Shield of Texas provider contracts, Texas Medicaid disease-management work under a Diabetech/McKesson subcontract, employer-sponsored programs, NHS work, and related Diabetes HouseCall telemedicine collaboration. Kevin’s responsibilities crossed patient support, provider engagement, program reporting, and reimbursement-related processes.

The Medicaid account includes recruitment from a pool of more than 1,500 diagnosed adults. That is a recruitment-pool description, not evidence that 1,500 participants enrolled in a particular Diabetech pilot. The archive keeps that distinction explicit.

Clinical workflow and participant experience

The service design combined automated information with human review and support. Case managers and care teams needed to interpret information, validate exceptions, and route clinically meaningful findings. The program also had to work for participants with different levels of digital access and confidence.

Kevin’s use of mail-in diagnostics, SMS, printed materials, telehealth, and other channels reflects that requirement. The care model could use a digital component without making every patient interaction digital.

What this adds to the career record

HealthCordia establishes operational experience in virtual care and disease management beyond device development. It connects product strategy to clinical service delivery, logistics, patient engagement, payer requirements, and sustained execution. This is a useful foundation for leadership roles that need one accountable view of product, care operations, and the participant journey.

A complete remote program

Kevin’s career record describes a BellSouth Active Disease Management diabetes program involving approximately 200 participants, with related type 1 and type 2 diabetes work in 2006–2007. The program combined connected blood glucose monitoring, remote participation, home A1c measurement, participant support, and social-support concepts.

The employer relationship required more than supplying devices. The program had to recruit and onboard people, support their use of the service, organize clinical interactions, and make information useful to patients, clinicians, and the organization sponsoring the work.

Kevin’s responsibilities

His CV identifies sales and account management, protocol design, outpatient support, wireless blood glucose monitoring devices, and patient outcomes analysis. It also describes establishing an industry IRB for oversight of non-significant-risk device research. His later career materials add the operating detail of remote consent/enrollment packages, copay strategy, claims, medical-necessity support, physician sign-off, visit scheduling, and remote visit coordination.

These responsibilities connect commercial leadership with clinical research operations. Kevin had to make the service viable for the sponsor and usable for the people participating in it.

Behavior and feedback

The program used mobile diagnostics, automated rules, and social-support mechanisms to make education and feedback timely and relevant. Remote glucose information was one input; home A1c provided another measurement, and participant communications helped keep the program connected to daily life.

The underlying design concern was whether people would continue participating after enrollment. Kevin’s later patient-journey work draws on that experience: a program needs practical reinforcement, workable logistics, and support that responds to what is happening with the participant.

Connection to HealthCordia

Kevin’s career chronology presents the BellSouth/AT&T work as evidence and operating experience that supported the later HealthCordia virtual disease-management model. The progression moved from devices and data into the full structure of a remote-care service.

This record is grounded in Kevin’s CV and career materials. The original pilot poster is a historical program artifact; it is not reproduced here. The approximate participant count is a career-reported program figure, and no unsupported clinical or financial outcome is attached to it.

Relevance to current work

The project demonstrates experience with end-to-end patient journeys that include access, operations, reimbursement-related processes, diagnostics, data, and engagement. It is particularly relevant to organizations developing direct-to-patient or employer-supported services where enrollment is the beginning of the operating challenge.

Program and population

Kevin’s CV identifies a Texas Medicaid adult type 2 diabetes demonstration pilot from September 2009 through April 2011. The work operated within the broader McKesson disease-management environment. His responsibilities connected patient-generated data, home-based screening, intensive behavior support, and clinical research operations.

Later career materials describe recruitment from a pool of more than 1,500 diagnosed adults. That number describes the potential recruitment population. It is not used here as a count of enrolled study participants or as the size of a completed randomized trial.

Kevin’s role

As principal investigator, Kevin designed technology, protocols, and patient-facing materials while managing a process of home diagnostic screening and behavioral support. His CV describes motivational interviewing and a social-network model for peer influence. His broader operating work included case-manager workflows, remote monitoring, patient support, provider coordination, and program reporting.

The responsibilities combined research design and implementation. Technology choices had to fit participants’ access, language, routines, and the operating practices of the care organization.

Systems and human review

The program architecture connected medical-device telemetry to an intervention hub. Kevin’s career account describes review of patient-generated data, validation of exceptions, interpretation of risk signals, escalation of meaningful findings, and patient or clinical interventions. Human review was a working part of the model.

Operational information—enrollment, adherence, data completeness, intervention activity, workflow status, service performance, and outcomes—also mattered. It allowed teams to see whether the service was functioning and where additional attention was required.

Evidence boundaries

The historical proposal and operating materials include objectives and proposed measures around A1c, self-management, satisfaction, emergency-department use, and hospitalization. Those objectives are not presented as achieved results without a corresponding outcome source. Confidential proposal text, pricing, and proprietary program material are not republished.

The linked government reports describe the Texas Medicaid/McKesson program environment. They support the institutional context, while Kevin’s CV and project record support his specific responsibilities. Keeping those two forms of evidence separate makes the account more precise.

Operating relevance

The work is relevant to payer-connected virtual care, chronic disease management, health equity, remote clinical operations, and practical use of patient-generated data. It demonstrates familiarity with the interaction of participant behavior, diagnostics, devices, clinical oversight, and service execution in a population that cannot be assumed to have frictionless digital access.

The operating challenge

Kevin’s career record describes direct Blue Cross Blue Shield of Texas remote diabetes services and a Diabetes HouseCall telemedicine model. The work addressed how a care program could operate around the patient’s home while connecting with clinicians and a payer.

It required an arrangement that made sense clinically, operationally, and commercially. Remote data and coaching were useful only if the program could support participation, physician involvement, and a viable payment and service model.

Kevin’s contribution

Kevin developed the program and commercial relationships, connected supporting evidence with actuarial review, and worked on reimbursement for the remote diabetes-management service. His responsibilities included the systems around patient access and continuing care rather than only the technology.

His broader direct-to-patient account includes inbound referrals, prior-authorization-related workflows, claims, case-manager assignment, logistics, primary-care coordination, medical-necessity support, and remote visit arrangements. These are connected operating capabilities across the portfolio; the archive does not imply that every workflow was identical in every payer contract.

Care delivery and engagement

The model combined patient-generated information, home diagnostics, education, remote interactions, and clinician participation. It reflects a recurring feature of Kevin’s work: the patient journey extends through the handoffs between digital tools, physical services, reimbursement, and people.

The service also connected to his collaboration with Stephen Ponder and other clinical professionals. Kevin’s role was program and business leadership; clinical medical decisions belonged to qualified care professionals.

Commercial relevance

This experience is relevant to companies building direct-to-patient services, remote specialty support, diagnostics-enabled care, or payer-facing digital products. It provides a concrete example of linking product architecture to a reimbursed care model.

The account is based on career documentation. Original payer contracts and actuarial materials are not public attachments, and no reimbursement rate, financial return, or payer endorsement is inferred beyond the documented operating relationship.

The next operating layer

Healthimo expanded the earlier connected-diabetes work into a broader community-health and engagement model. Kevin’s career chronology emphasizes the 2012–2018 scaling phase, while historical Healthimo materials describe activity before 2012. The dates reflect operating emphasis rather than an assertion that the brand or technology began in 2012.

The platform combined education, participant information, remote data, and pathways into more intensive condition-specific programs. It linked community participation to the services and research opportunities available around the participant.

Recruitment, activation, and routing

Kevin designed broad engagement funnels and low-friction entry points, then connected participants to condition-specific messaging and care pathways. His record includes work across U.S. and U.K. programs, local partnerships, community activation, communications, and program execution.

The South Texas work emphasized children, parents, extended families, and community influence. The design recognized that a person’s ability to engage with health information often depends on the surrounding social environment and on the relevance of the next requested action.

A hybrid information network

A historical Healthimo overview describes patient participation through mobile text messaging, wireless glucose devices, web forms, interactive video, and prepaid mail-in surveys. Home sample kits and laboratory results added another data source. The network brought patient and clinician information together for education, support, and research.

This is an important part of the design record: paper collection and digital processing were integrated into the same program. Digital access was a means to participation, not a condition every participant had to satisfy.

Scale and historical claims

Kevin’s CV reports a regional community growing to more than 30,000 members in less than a year. A separate historical Healthimo overview reports an earlier registry of more than 10,000 and a future recruitment target. These are different snapshots and definitions. The archive does not combine them into a new aggregate or treat a historical target as an achieved result.

The overview also describes U.S. and U.K. clinical-center participation. Its figures are historical company-reported information, not claims about the current size or operation of Healthimo.

Leadership and product relevance

Healthimo connects program architecture, community activation, data collection, international partnerships, and a service model that could sustain engagement beyond initial recruitment. It is particularly relevant to patient/member engagement, population health, lifecycle strategy, and products serving people with varied access and support needs.

The operating lesson is concrete: a broad front door can reduce recruitment friction, but it must lead somewhere useful. Kevin’s work connected entry, profiling, education, routing, support, and measurement.

Program setting

Kevin’s CV identifies Mobile Community Health Networks for diabetes and asthma, supported by HRSA/Office for the Advancement of Telehealth grant H2AIT16625-02-02, from September 2009 through August 2011. He served as grant writer, protocol author, and program manager with Driscoll Children’s Health Plan.

Related career accounts describe Healthy Families of South Texas and a seven-county population-health effort. The work extended participation beyond an individual child to parents, extended family, and the local community.

Design responsibilities

Kevin designed an engagement model that could recruit broadly, profile participants, and connect them to condition-specific intensive messaging protocols and available services. The experience combined program strategy with the practical details of recruitment, communications, enrollment, local partnerships, and execution.

He treated community trust and ease of participation as operating requirements. A technically sophisticated website would not be sufficient if the population was more likely to respond through SMS, printed materials, or a familiar community pathway.

Channel and workflow choices

The wider Healthimo infrastructure supported mobile participation, prepaid paper surveys, device data, education, and laboratory information. These channels could bring participants into a shared data and engagement model without requiring identical technology habits.

The program’s value depended on what followed sign-up. Participant information needed to produce relevant education, encouragement, routing, or service connection. Broad engagement and intensive management therefore played different roles in the design.

Scale in the career record

Kevin’s CV describes a community growing to more than 30,000 members in under a year. The figure is a career-reported community reach/participation measure. It is not presented as a randomized study sample, an active medical caseload, or an independently audited retention measure.

The account supports experience with population-scale activation and program architecture. Claims of downstream medical cost reduction would require separate outcome evidence and are not inferred from the participation number.

Where the experience connects

The work is relevant to member activation, patient journeys, public-health engagement, community referral models, and products addressing health inequity. It demonstrates the ability to connect a broad participation strategy to concrete operating pathways and to adapt collection and communication methods to the people a program intends to reach.

Two distinct program contexts

Kevin’s CV identifies easySHARE pediatric type 1 diabetes remote monitoring and self-care work with Salford Royal from 2010 to 2017. It separately identifies diabetes-in-pregnancy intensive remote monitoring from 2010 to 2015, including pre-existing type 1/type 2 diabetes and gestational diabetes.

The programs share a remote-monitoring foundation but involve different participants, care relationships, and research needs. They demonstrate application of the operating model across clinical contexts and health systems.

Kevin’s role

His documented responsibilities were protocol design and clinical trial operations. These activities connected the remote data and technology environment to the research procedure and the needs of patients and clinical teams. They drew on the earlier Diabetech and Healthimo work in wireless glucose collection, information sharing, and engagement.

The international setting added a different provider and service environment. Kevin’s broader career account includes U.K. joint-venture and program-development work, partner workflows, and community-health models.

What the experience demonstrates

Remote data collection needs a clear place in care and research. The relevant experience is designing and operating the connection between participant behavior, device information, protocol requirements, and the professionals receiving the data. It is not simply international distribution of a device.

The pediatric and pregnancy settings also underline the importance of timing, burden, support, and collaboration. The operating model must be adapted to its participants and clinical use rather than assuming one interface or intervention fits every population.

Evidence scope

The dates and responsibilities come from Kevin’s CV. This record does not attach an unverified clinical result or claim author credit on publications that have not been identified. It documents protocol and trial-operations experience with the named programs and supports the broader account of international connected-care work.

The research question

The Kaiser collaboration examined how wireless technology and a supporter selected by the patient could make self-management support more timely and useful. Kevin’s CV identifies work from August 2009 to April 2010 on the Diabetes Social Support Feasibility Pilot Study. A related abstract appeared in Clinical Medicine & Research in 2010.

The design brought people around the patient into the intervention. It considered how glucose information, communication, and social support could work together, rather than treating engagement as a sequence of generic reminders.

Kevin’s responsibilities

Kevin served as a co-investigator and worked with the behavioral research team to recruit, train, and engage participants from a Kaiser facility and a federally qualified health center serving a low-income population. His responsibilities connected the wireless tools and patient/supporter workflow to the study’s feasibility and usability questions.

His approved career record describes implementation of motivational-interviewing-based digital engagement in the Kaiser work. He translated concepts such as readiness, autonomy, relevance, and sustained participation into patient-facing digital workflows.

Published and public context

The 2010 pilot abstract includes Kevin McMahon among the authors. Douglas Roblin’s 2011 Journal of Health Communication article discusses cellular technology and social networks in chronic-disease self-management. An AHRQ-hosted presentation describes the use of mobile information and communications technology for social support.

These are complementary sources. Kevin’s author credit is attached to the pilot abstract; the Roblin article and presentation provide collaboration and design context. They are not all labeled as works authored by Kevin.

Operational significance

The work connects patient-generated data to a real support relationship. A data point may be useful because it prompts an informed family member, peer, or care professional to respond at a meaningful time. The design therefore includes the message, the recipient, the relationship, and the participant’s willingness to continue.

This experience is relevant to patient-journey innovation, family engagement, behavioral product design, activation, retention, and AI personalization that needs to respect human context. It demonstrates applied collaboration with behavioral researchers.

A research role that developed through field work

Kevin’s research experience began with connected-diabetes systems and expanded into sponsor-side rare-disease development. His CV describes technology design, protocol development, study sponsorship and oversight, training, outpatient support, outcomes analysis, partnership development, and selected principal-investigator responsibilities. The roles varied by study.

The later Ultragenyx work added clinical systems strategy, protocol-development-team participation, digital endpoints, data collection, and regulated operating infrastructure across a portfolio.

Selected documented studies

The early end-to-end wireless diabetes feasibility work ran from June 2002 to November 2003 and connected automated collection, analysis, feedback, and social support. Kevin’s role included technology design, protocol development, sponsorship, oversight, training, support, and presentation of findings.

The Proactive Diabetes Interventions work in 2004–2005 examined automated transfer and support in newly diagnosed children and children beginning insulin-pump therapy, with an additional summer-camp feasibility component. The CV documents technology, protocol, oversight, and support responsibilities.

The 2007–2011 automated diabetes-management trial led to the 2012 Diabetes Care publication. The Texas Medicaid adult type 2 diabetes demonstration pilot lists Kevin as principal investigator from 2009–2011. The Kaiser social-support pilot lists him as co-investigator.

Hospital and academic collaborations

Other CV entries include protocol design, data management, and trial operations for Detemir: Role in Type 1 Diabetes (NCT00564395); partnership and clinical operations for a school-nurse intervention (NCT00340613); partnership and operations in a Baylor pancreatic islet-cell transplantation program (NCT00530686); and operations in a real-time glucose-alert study (NCT00322478).

These identifiers are included as historical references from the CV. The record does not describe Kevin as the principal investigator on every study or as the clinical authority for each therapeutic intervention.

Research governance

Kevin’s BellSouth program account includes establishment of an industry IRB for non-significant-risk investigational-device research. His work connected patient safety, protocol compliance, study procedures, technology operation, and participant support.

At Ultragenyx, quality and validation were embedded in the digital clinical organization, with specialist QA/CSV functions and coordination across clinical, data, and vendor teams. This is a different institutional role from his earlier investigator work, but it draws on the same concern for reliable execution.

Public results and attribution

The Diabetes Care randomized trial, the Kaiser pilot abstract, the Diabetes Spectrum article, and the LC-FAOD disease-monitoring abstract provide identifiable public evidence. Some other projects are documented in Kevin’s CV without a public results link. That distinction is preserved throughout the archive.

The research portfolio supports experience moving between clinical intent and practical execution. It does not imply that all projects were randomized, all planned studies completed, or all program objectives became demonstrated outcomes.

Program context

The South Texas Diabetes and Asthma Network included a study of children with diabetes using mobile wireless technology for remote clinical monitoring and intervention. Kevin’s CV places this work from January 2006 through February 2009. It identifies a competitive $455,000 USDA telemedicine grant supporting the program.

The regional setting connected pediatric specialty care with patients outside the clinic. Wireless information and practical support had to function across the participant’s daily environment and the care organization’s response process.

Kevin’s contribution

Kevin was a primary contributing author of the clinical protocol. His responsibilities included outpatient technical support, GPRS glucose-monitoring devices, and patient outcomes analysis. The work combined proposal development, clinical research design, and delivery.

It also formed part of a longer relationship with Driscoll Children’s Hospital, its research collaborators, and South Texas community-health programs. Those relationships contributed to the subsequent family/community engagement and population-health work.

Technology and intervention

Remote transmission gave the program a route to receive glucose information without waiting for an office visit. The program then needed relevant review, support, and feedback. Kevin’s wider Diabetech architecture connected mobile diagnostics, information processing, and timely communication with patients and caregivers.

The work demonstrates grant-supported implementation experience. The award amount in the career record is a grant figure, not Kevin’s personal compensation, a revenue total, or proof of a particular clinical effect.

Connection to the research record

The 2012 Diabetes Care paper is a separate identifiable outcome publication within the broader Driscoll/Diabetech research history. This archive does not automatically attribute that trial’s result to every USDA-funded activity. Each project retains its own scope and evidence.

Together, the records show experience working with hospital teams, public funding, clinical protocols, connected devices, outpatient support, and data analysis. That combination is relevant to organizations translating an evidence-generation plan into an operating program.

A journey has operational dependencies

Kevin’s patient-journey work crosses remote diabetes care, payer-supported programs, home diagnostics, rare-disease research, education, and exploratory patient-data products. The common responsibility is to make the service coherent from the participant’s perspective while coordinating the organizations and systems behind it.

His experience includes recruitment, referral pathways, enrollment, onboarding, device and supply logistics, support, clinical coordination, data capture, reimbursement-related workflows, education, and continuing engagement. These activities are connected: an apparently successful enrollment can still fail if the next steps are unclear or impractical.

Evidence across the lifecycle

BellSouth/AT&T provides an example of a remote program linking connected glucose data, enrollment, home A1c, patient support, physician participation, and payer-aware operations. HealthCordia extends that into virtual disease management. Blue Cross Blue Shield of Texas and Diabetes HouseCall add payer/provider and reimbursed-service context.

At Ultragenyx, Rarify and BEYONDXLH required participants and sites to contribute information over time, with quality, training, device, and support considerations. Healthimo and the South Texas work demonstrate broad community entry points and routing toward more specific services.

Behaviorally informed design

Kevin’s Kaiser collaboration connected wireless information to a patient-selected supporter and applied behavioral principles to participation. His work with patient communities and education added practical experience with autonomy, cognitive burden, trust, family influence, and relevance.

The operating concern is not simply the number of messages sent. The program needs to understand whether the participant can act, whether the action is worthwhile, and whether the timing and channel fit the situation. His physical/digital channel choices reflect that concern.

Measurement and iteration

Kevin’s product and operations work includes KPI monitoring, user feedback, adoption, data completeness, and iterative enhancement. He connected those measures to workflow changes and service expectations. Engagement data were useful when they helped the team identify a problem and improve the experience.

Metrics need their own definitions. Enrollment, active participation, completed data, retention, and clinical outcomes describe different things. His archive separates these measures rather than treating them as interchangeable proof of success.

Leadership contribution

The role requires coordination among product, clinical, data, quality, commercial, and service functions. Kevin has led an organization covering those responsibilities and has operated at the seams between partners. He can therefore connect a journey design to staffing, vendor decisions, implementation, and ongoing accountability.

The experience is applicable to patient/member engagement, digital health leadership, direct-to-patient models, care operations, customer adoption, and lifecycle strategy. The strongest examples are named operating programs, with their specific responsibilities and evidence linked below.

A central design principle

Kevin’s work has repeatedly used physical and digital methods together. A postcard, home sample kit, text message, connected device, phone call, family member, clinician, or automated workflow can each have a role in a care program. The channel is chosen for the action and the person.

This principle predates the current interest in digital health. Historical Healthimo materials explicitly describe prepaid mail-in surveys alongside mobile text messages, device data, web forms, video interactions, and home laboratory kits.

What was implemented

The Healthimo network gathered participant information through channels suited to different levels of access and comfort. HomeCheck-A1c joined physical sample collection and mailing with laboratory processing and digital results. GlucoMON reduced the effort needed to transmit glucose information. South Texas community programs used low-friction recruitment and communication around local participation.

These examples demonstrate a practical architecture in which physical collection can feed digital systems and digital signals can trigger human or physical actions. A participant does not have to use every available channel.

Why paper can have a useful role

Printed materials are persistent and can be visible in a household after a digital notification has disappeared. They can introduce a service, support a task, provide a reminder, collect information, or reconnect someone who has gone quiet through other channels. These are design applications, not claims that every use was experimentally proven in Kevin’s programs.

The operating model still needs to account for response capture, data entry or digitization, identity matching, follow-up, and participant consent. The physical element is part of a larger information and service workflow.

Designing for actual participation

Kevin’s community and payer-program work taught him to consider language, relevance, trust, technology access, family context, and cognitive burden. The user’s existing habits can determine whether a program is usable. The goal is to make the next meaningful action easier and to connect it to a useful result.

This is relevant to remote care, clinical research, member engagement, older or underserved populations, and programs that need to reach beyond self-selected digital enthusiasts. The evidence is the historical integration of these channels, with current design implications labeled as such.

Experience at several levels

Kevin’s work combines a personal origin in family diabetes care with professional experience building products, operating programs, conducting research, and collaborating with patient communities. The professional contribution is the translation of lived experience into requirements and operating decisions.

The record includes pediatric diabetes, adult chronic-care programs, family and social support, community-health engagement, and rare-disease research. Different groups required different engagement and collaboration models.

Sponsor-side co-design

At Ultragenyx, Kevin’s career materials describe collaboration with patient advocacy organizations and paid patient-community consultants under legal and compliance oversight. The purpose was to incorporate real-world needs and behaviors into clinical workflows and digital experiences.

BEYONDXLH involved the XLH Network and Yale in a longitudinal monitoring program. Kevin’s responsibilities connected study design, patient-reported information, program improvements, and study-manager mentoring.

Family and social context

The Kaiser social-support study used supporters chosen by participants, while the South Texas work expanded the program frame from the child to parents, extended family, and community. These examples show that Kevin’s patient engagement work includes the people influencing daily behavior, not only the individual account holder.

Sugar Surfing and the associated community and workshop work added experience translating technical information into practical education for patients, families, and clinicians. Kevin partnered with qualified clinical experts in producing that education.

Value to product and program teams

Patient input becomes valuable when it changes a decision: the burden of a collection task, the clarity of a message, the timing of feedback, the availability of support, or the way a clinical workflow is presented. Kevin’s experience connects those decisions to teams capable of implementing and maintaining them.

The record documents repeated collaboration across the groups needed to make healthcare products and research usable.

From opportunity to an executable product

Kevin’s career includes enterprise platforms, connected medical devices, home diagnostics, virtual-care services, clinical applications, and publishing products. Across those settings, he has been responsible for connecting a product idea to users, workflows, technical feasibility, economics, and a delivery organization.

The Ultragenyx Innovation Lab is a substantial recent example. Kevin identified unmet needs, developed a strategic plan, secured support for internal development, and built the functions necessary to deliver and operate the resulting capability.

Portfolio and lifecycle scope

His responsibilities included vision, roadmaps, intake, prioritization, resource allocation, operating cadence, portfolio governance, lifecycle management, stakeholder alignment, adoption, and executive reporting. These responsibilities were tied to an annual departmental budget and a globally distributed team.

The work required tradeoffs between reusable platform capabilities and study-specific needs, between internal and external delivery, and between new projects and existing support commitments. Kevin’s role connected the decisions to owners, milestones, and operational expectations.

Technology assessment and business rationale

His career materials describe defining clinical need, target users, workflow integration, technical feasibility, regulatory considerations, evidence requirements, adoption measures, and business rationale for emerging capabilities. He established gating, milestones, validation workstreams, accountability, and transition plans from concept toward operational use.

This experience is relevant to upstream innovation and product-concept work because he has also owned the downstream consequences. A funded concept must eventually work within service, quality, support, and commercial constraints.

Earlier product and commercial examples

Diabetech joined devices, wireless networks, cloud services, analytics, research, and care operations. HomeCheck-A1c combined a physical diagnostic kit with laboratory and information services. Enterprise technology roles involved mobile platforms, wireless location services, telecommunications infrastructure, middleware, partner distribution, and complex RFPs.

MediSelf Press adds a different form of product execution: packaging expertise into published work, coordinating production, distribution, fulfillment, customer experience, and marketing. These examples show a recurring ability to integrate the components required for a product to reach and serve its user.

Leadership contribution

Kevin’s strongest role is where a team needs both product judgment and operating accountability. He can help determine what should exist, how it should be delivered, and what the organization must measure and support after launch. The project records provide named examples rather than an undifferentiated list of product-management keywords.

Commercial experience across several models

Kevin’s commercial work includes enterprise platform sales, embedded software distribution, connected medical products, diagnostics, payer-supported services, and direct publishing. It spans both creating the product and obtaining the relationships needed for it to reach a user.

That background informs his later clinical technology decisions. Product value, delivery cost, partner obligations, and the operating model remain connected even when the immediate customer is an internal sponsor organization.

Enterprise transactions

At Vitria, Kevin led telecom channel development and platform-integration strategy during the post-IPO scaling period. His career record describes a $3 million strategic partnership with Amdocs for embedded middleware distribution. Earlier telecommunications platform work included RFP response leadership and a $9 million prepaid platform deployment with Optus Australia.

These transaction values are reported in Kevin’s career documents. They demonstrate the scale and nature of commercial responsibility claimed, while original contracts and financial disclosures are not public attachments.

Healthcare models

At Diabetech, Kevin combined product development with partnerships involving LifeScan, telecommunications companies, payers, providers, researchers, and health systems. HealthCordia and Diabetes HouseCall connected technology to care operations and reimbursement. HomeCheck-A1c brought laboratory processing, logistics, and results delivery into a patient-facing service.

His experience includes program evidence and actuarial review supporting payer conversations, plus practical knowledge of access, claims, support, and physician participation. Commercial design therefore extended beyond selling a device or licensing software.

Platform lineage

Kevin’s later career account describes licensing connected-device and cloud technology into a commercial lineage through Telcare and BioTelemetry to Philips Virtual Care Management. The archive presents this as his documented career account. Philips’ 2023 announcement is linked for the later market context, not as independent verification of each transaction in that chain.

No claim of present ownership, ongoing royalties, or responsibility for Philips’ current products is implied.

Direct channels and publishing

MediSelf Press demonstrates direct product packaging, ecommerce, distribution, customer support, fulfillment, and audience development around specialist content. Sugar Surfing combines a clinical collaboration with a published product and a sustained patient community.

Together, the record shows how Kevin links product decisions to a viable way of reaching users, delivering value, and sustaining operations. The experience is relevant to product strategy, partner development, commercial readiness, and operating leadership.

Career sequence

Kevin’s career materials identify finance, audit, and vendor-management work at GTE, now part of Verizon, from 1991–1997; product management and business development within the Tandem/Compaq/HP lineage from 1997–2000; Vitria channel development from 2000–2001; and Vice President of Sales at eLagent from 2001–2002. Some roles overlap with the founding period of Diabetech.

The historical company names matter. Later resumes sometimes group the earlier enterprise work under HPE as a corporate lineage reference; this archive does not describe HPE as the employer’s contemporaneous name in the 1990s.

Finance, audit, and vendor foundation

At GTE, Kevin worked with enterprise processes, internal audit, procurement, vendor management, operational systems, and executive reporting. His career record includes process-improvement and time-accounting work intended to improve billable utilization.

This foundation gave him experience with the economic and control systems behind delivery. It later informed program budgeting, partner evaluation, portfolio governance, and the operating discipline of regulated technology organizations.

Mobile and network platforms

The 1997–2000 period included product management and business development across wireless location services, mobile platforms, intelligent networks, network-connected touchscreen PDAs, mobile commerce, and distributed computing. Work included APAC customers and international telecommunications operators.

Kevin translated requirements across device hardware, client software, networks, and enterprise backend systems into product concepts, roadmaps, and partner ecosystems. His record describes RFP response leadership and a $9 million prepaid platform deployment with Optus Australia.

Embedded distribution and channel development

At Vitria, Kevin led telecom channel development and platform integration during the company’s post-IPO scale phase. He reports closing a $3 million strategic partnership with Amdocs that enabled embedded middleware distribution within telecommunications operator environments. The integration was part of the commercial model.

At eLagent, he led sales and commercialization of distributed-computing capabilities across defense, insurance, and developer markets. This added experience connecting a technical platform to varied enterprise customer needs.

Consumer media exposure

Kevin has also identified participation on the Americast business review team before launch. That is specific pre-launch consumer-media and aggregation experience. The record does not assign him a broader streaming-product leadership role or responsibility for the platform’s launch.

These experiences provide an enterprise and consumer-platform foundation for his later connected-health work. They demonstrate that his systems and commercial experience extends beyond the healthcare domain.

Status and purpose

Operational Telemetry for Clinical Trials: The C4I+T Control Tower Model for Clinical Operations is Kevin’s March 2026 draft concept brief. It applies lessons from earlier remote-device telemetry and sponsor-side clinical technology work to the problem of overseeing a distributed trial environment. It is a framework proposal, not a claim of an enterprise platform already deployed across sponsors.

The objective is to produce trusted operational signals that can support timely action and appropriate automation. Kevin emphasizes reducing dependence on manual trackers and fragmented reporting by establishing a more reliable information foundation.

Why the trial network is different

The brief distinguishes relatively structured device transmissions from the heterogeneous systems used in clinical trial operations. Trial information comes from sites, vendors, study teams, CTMS, EDC, and other systems of record, each with its own timing and definitions. Cross-study analysis can be misleading if those differences are ignored.

Kevin places governance before signal generation. Data must be curated and assessed for trust, consistency, and traceability before a leadership view or workflow relies on it. The design concern is not only where information is displayed, but how the organization knows what the information represents.

Four interacting functions

Ingestion brings operational information from the systems of record into the model with source and timing context. Governance evaluates whether information is sufficiently reliable and appropriate for the intended use. Analysis identifies patterns, exceptions, clusters, or changes that may warrant attention. Execution connects the signal to a defined response and accountable owner.

These are interacting functions rather than a one-time reporting pipeline. An intervention creates new information about whether the problem was understood and whether the response helped. That feedback can improve the next interpretation and the operational process itself.

Beyond a single-study view

Sites work on multiple protocols, vendors serve multiple sponsors, and shared resources can introduce problems that are visible across a network before they become obvious within one study. The brief proposes a layer of operational awareness that can examine those patterns while preserving study-level responsibilities.

Examples in the design include recruitment performance, screening inefficiency, dropout patterns, infrastructure delays, staffing changes, and vendor processing bottlenecks. They are examples of proposed signals and views, not a claim that the framework has prospectively demonstrated prediction of all those events.

Time and movement

The concept brief includes an animated recruitment-risk view in which sites move as performance changes over time. The purpose is to make direction and emerging patterns easier to recognize, alongside a static point-in-time view. A cluster moving together might prompt investigation of a shared protocol, training, or vendor issue.

The visualization is a design example. The value depends on the quality and interpretation of the underlying information; visual movement alone does not establish causation or prescribe a clinical or operational decision.

Relationship to Kevin’s operating experience

The framework draws on the Diabetech sequence of collection, analysis, feedback, and intervention, plus the Ultragenyx experience with clinical informatics, regulated delivery, and cross-functional operations. Those earlier projects are documented separately as operating experience. The 2026 framework is an explicit extension of the ideas into a broader oversight model.

It is relevant to clinical operations strategy, patient-data products, portfolio governance, AI-enabled operations, and teams replacing uncontrolled trackers with more dependable signals. The design contribution is the relationship among trust, interpretation, ownership, and action.

The operating position

Kevin’s recent independent work explores how language models and AI-assisted workflows can organize patient information and support useful products. His strongest contribution is the design of the surrounding operating model: what information enters, what the user receives, which decisions require human review, and how changes remain traceable.

The current projects are exploratory. This archive does not describe PatientStories as a validated clinical AI product, an autonomous diagnostic system, or a production deployment with proven clinical outcomes.

Consent and source context

PatientStories design work emphasizes consent-aware collection of sensitive information, patient control, and preservation of the original narrative context. The product concept connects patient-authored stories with structured longitudinal signals, while keeping the relationship between a derived statement and its source visible.

Human review includes the ability to accept, edit, or remove suggested content. The distinction between patient statements, inferred structure, and clinical interpretation matters because an AI-produced summary can otherwise appear more certain than its source.

Participant value before secondary use

The design emphasizes a health biography, reflection, and preparation for clinical conversations as direct participant benefits. Research or life-sciences insight is a separate potential use that depends on appropriate consent, governance, trust, and data integrity.

That sequence reflects Kevin’s patient-journey experience: a product should earn continuing participation through usefulness. Data extraction alone is not a sufficient value proposition for the person asked to contribute.

Practical AI fluency

Kevin’s recent career materials describe hands-on work with AI-assisted prototyping, product mockups, data modeling, workflow automation, LLMs, and agentic concepts. He has used these methods to explore information products and operating workflows. His Ultragenyx materials also describe investigation and prototyping of conversational AI for clinical-development use cases.

The evidence supports product and operational fluency.

Relationship to earlier systems

Diabetech used rules-based analysis and human intervention workflows long before modern generative AI. Those systems should be described as rules-based decision support, not retroactively labeled as LLM products. The relevant continuity is the discipline of connecting information to a governed response.

The Operational Telemetry framework carries that logic into proposed cross-system clinical oversight. The archive keeps implemented historical systems and current design work distinct so that their contributions can be assessed accurately.

Project status

PatientStories.ai is independent, exploratory product and program-design work begun after Kevin’s Ultragenyx role. The project explores patient narrative, longitudinal context, and AI-assisted information products. Development was deprioritized in September 2026 while Kevin focused on employment opportunities and publishing work.

The archive presents the project as design evidence. It does not represent an active scaled patient network, a validated clinical system, or a commercial research service with established outcomes.

The problem being explored

A glucose trace, survey answer, or clinical observation captures only part of a person’s experience. PatientStories asks how patient-authored narrative might preserve the context behind those signals: daily burden, access barriers, workarounds, support, goals, and changes over time.

The product thesis is to organize that information without stripping away the participant’s agency or making a derived summary appear to be a clinical fact. The design connects raw narrative, human review, structured categories, and a longitudinal view.

Participant-facing design

Concepts developed during the project include a health biography, reflection check-ins, a doctor-visit report, consent and participant identifiers, and personal/community views. The health biography provides a concrete participant benefit: an organized account that can support reflection and communication.

Kevin’s design work also considered how to keep the capture and review burden manageable. Adaptive prompts could request missing context, but the user would remain able to review, revise, or remove AI-derived material.

Information and governance model

The design considers the relationship between source narrative, derived signals, consent, and permitted use. Proposed categories include care friction, adherence barriers, emotional burden, workarounds, support systems, and tradeoffs. These categories are a design taxonomy rather than a validated clinical classification.

Potential research use would require separate governance and appropriate evaluation. Early feasibility plans are plans, not proof of completed enrollment or established regulatory compliance. Kevin’s clinical quality experience informs the design but does not automatically validate an independent prototype.

What Kevin contributed

His work includes product thesis, user journeys, data modeling, governance strategy, rapid prototyping, AI-assisted workflows, and practical value exchange. The project connects his earlier patient-data and engagement experience to emerging tools while remaining honest about its stage.

It provides a current example of product and systems thinking. The strongest evidence remains the design work itself and its relationship to the implemented clinical and remote-care programs documented elsewhere in the archive.

Co-authorship and the original work

Sugar Surfing: How to Manage Type 1 Diabetes in a Modern World was co-authored by Stephen W. Ponder and Kevin L. McMahon and published by MediSelf Press in 2015. It captured a period when continuous glucose monitoring was changing what people with type 1 diabetes, their families, and their care teams could see and understand about daily glucose patterns.

Kevin’s contribution combined writing and product development with publishing, digital properties, community development, and the practical work of bringing the book to readers. Clinical expertise, lived experience, authorship, design, education, and delivery involved collaboration; the record identifies Kevin’s role within that work.

From CGM access to practical use

Access to a continuous stream of glucose information is only part of making CGM useful. People also need a way to interpret patterns, understand context, discuss what they see with their care team, and incorporate the information into everyday life. Sugar Surfing addressed this educational and practical usability problem.

Kevin worked with a clinician co-author to communicate pattern recognition, context, and practical self-management concepts. His contribution includes authorship, product architecture, design execution, and commercial packaging. This work supports the adoption and use of CGM through education and communication, alongside his separate experience with connected-device and clinical research systems.

Direct-to-patient and provider impact

The book and its associated educational activity reach people with type 1 diabetes and families directly, while also serving clinicians and other professionals who support CGM use. Kevin’s career record describes print and digital publishing, digital media and community tools, institutional bulk purchases, and systems supporting workshop marketing and billing. Related Dynamic Diabetes Management nonprofit activity sought to expand patient and professional education.

Kevin identifies the work as an ongoing contribution to CGM uptake and usability in type 1 diabetes: making continuous data more understandable, giving patients and providers shared language, and connecting technical capability with practical use. The contribution therefore spans patient activation, provider communication, education, and implementation, as well as publishing.

Dexcom bulk purchases for sales and prescriber education

Kevin reports that Dexcom purchased Sugar Surfing in bulk for two purposes: educating its sales representatives and giving copies to prescribing endocrinologists. This identifies a specific manufacturer purchase and educational distribution channel for the book, alongside its direct reach to patients and families.

The connection adds professional and commercial context to Kevin’s co-authorship: the CGM manufacturer purchased the work for internal education and distribution to clinicians who prescribe its products. The purchase and intended uses are recorded from Kevin’s firsthand account. The public book sources identify the work and its authors; they do not independently verify the Dexcom transaction. No quantity, purchase value, date, measured prescribing effect, or personal ownership of the purchase negotiation is asserted here. The account also does not establish that Kevin personally delivered training to Dexcom staff.

Continuing reach and relevance

MediSelf Press remains the publishing imprint behind the original work and its renewed availability. Sugar Surfing continues to be available to readers, and Kevin’s ongoing publishing and community activity sustains a route to patient and provider education. The professional contribution extends beyond the original publication date.

Current responsibilities include product packaging, expert collaboration, customer experience, commerce, fulfillment, and audience development. Those activities keep an established CGM education resource accessible and connect its content with the people who use or recommend it.

Evidence and attribution

The identifiable public evidence is the book, its co-authorship, and the publishing and educational activity. Kevin’s account describes its contribution to CGM uptake and practical usability. Educational contribution is distinct from a measured adoption-rate increase, a device-performance result, or a quantified clinical outcome.

The archive does not assign an unverified aggregate sales figure to a particular edition or channel. It also does not present the book as evidence that Kevin designed a CGM sensor or performed a specific manufacturer’s engineering work. His Dexcom clinical-integration record documents a different contribution.

Professional continuity

MediSelf Press is the established publishing imprint behind Sugar Surfing, first published in 2015. It is part of Kevin’s long-running work translating patient and clinical expertise into useful information products. It is not described as a newly formed subsidiary of PatientStories.

The current work provides professional continuity after Ultragenyx through publishing, education, expert collaboration, digital engagement, and product operations.

End-to-end responsibilities

Kevin’s publishing work includes author collaboration, editorial and production coordination, product design, print and ebook formats, distribution, ecommerce, fulfillment, customer support, and post-launch marketing. These tasks must fit together for a reader to receive a coherent product and for an author’s expertise to reach its audience.

The operating work includes managing external contributors and service providers, evaluating production choices, coordinating schedules, and connecting customer-facing promises to the ability to deliver.

Product and commercial judgment

Publishing requires choices about audience, value, format, packaging, pricing, distribution, and the ongoing relationship with readers. Kevin brings the same concern for operational fit that appears in his technology and care programs. A product must be understandable, obtainable, deliverable, and useful.

The record includes experience across direct channels and third-party platforms, physical and digital products, print-on-demand, and specialist patient education. These are actual operating categories; the archive does not disclose private author agreements, sales ledgers, or unpublished manuscripts.

Relationship to the wider career

The work strengthens the communication and commercialization side of Kevin’s profile. It demonstrates an ability to work with experts, shape complex material for an audience, manage delivery dependencies, and sustain a customer-facing operation.

PatientStories explores a different information model around patient-authored narratives. The projects share interests in patient experience and useful information, while their products and stages remain distinct.

Scope of the record

Kevin’s career archive includes early remote-command-and-control concepts, a glucose-monitoring patent application, and his 2014 presentation Road to the Artificial Pancreas. The contribution concerns system architecture and practical operating context around sensors, dosing devices, communications, software, and people.

These are historical design and education records. They do not claim that Kevin independently invented all automated insulin delivery, obtained approval for an artificial pancreas, or owns current commercial AID products.

The system view

The 2014 presentation distinguishes static configuration from dynamic information and emphasizes that an automated system must work with the limitations of its devices, software, networks, and users. It considers remote communication, synchronization, device condition, contextual signals, user communication, and caregiver awareness.

This is consistent with the earlier patent application’s wider architecture for remote data, analysis, feedback, and patient-management teams. The concept recognizes that local automation and the ability to understand what is happening around it are connected design problems.

Human factors and situational awareness

Kevin’s presentation discusses making information readily perceptible and adding useful context from activity, environment, and user behavior. It includes the need to inform the patient or a remote caregiver, not only to compute an output.

The practical focus on context later appears in Sugar Surfing’s education work, clinical sensor integration at Ultragenyx, and patient-narrative exploration. The continuity is an operating and information-design perspective, not a claim that all of these projects are the same technology.

Evidence and attribution

The public patent application names Kevin as inventor and provides a dated technical record. Road to the Artificial Pancreas is Kevin’s own 2014 presentation preserved in his career archive. Related implantable-sensing and artificial-pancreas material exists in the archive, but this public account does not assign an unverified specialist engineering role or grant outcome to Kevin.

The record is useful for understanding his long-term engagement with connected devices, remote oversight, human factors, and the limits of automation.

The program-design perspective

Kevin designs care programs around the interaction among the participant, intervention, channel, timing, and feedback. A device is one possible component. Home diagnostics, SMS, postcards, phone calls, family support, clinicians, and automated workflows can also contribute. The operating design determines how these pieces fit together.

His historical examples include remote diabetes management, employer and payer programs, home A1c, family/social support, community-health recruitment, and clinical research. The current ACCESS and TEMPO discussion applies that experience to emerging program contexts.

Five recurring design questions

Program design starts with who the service is for and what each level of care includes. Device and vendor selection asks which tools actually fit the model. Governance defines the responsibilities around clinical guardrails, data provenance, privacy, validation, and vendors. Patient decision logic considers what information should lead to a change in support. Program optimization asks what the operating data reveal about which components are useful.

These are Kevin’s design questions, not a statement of official program requirements. Current government requirements should be taken from the linked CMS and FDA sources.

Two feedback loops

At the participant level, the program asks what this person needs now and which response is appropriate. At the program level, it asks which features, channels, vendors, and workflows are delivering value and where the design should change.

The distinction matters because an intervention can be useful to one participant while the overall operating model is inefficient, or the program can appear efficient while missing the people who need a different form of support. Kevin’s operating experience connects those views through patient data and service information.

Historical foundations

Diabetes HouseCall and Blue Cross Blue Shield of Texas provide payer and reimbursement context. BellSouth/AT&T demonstrates remote-program execution. HomeCheck-A1c adds home measurement and feedback. Kaiser adds behavior and social support. Texas Medicaid and Healthimo demonstrate practical participation and service design across different populations.

Rarify and Ultragenyx add a more recent regulated clinical-development setting, including data quality, biosensors, patient/site systems, and governance. The value is the combination of these experiences, with each project’s evidence retained separately.

Current market context

CMS ACCESS and FDA TEMPO are linked as current external context for technology-supported care and evidence generation. Kevin has not claimed employment by either agency or participation in these initiatives. His contribution is a program-design perspective grounded in earlier work.

The government links are the authoritative place for current program details. The archive uses them to explain why integrated program operations matter, without presenting old project experience as a credential awarded by a current initiative.

Public record

The Texas House Research Organization’s 2005 analysis of HB 984 includes Kevin McMahon of Diabetech in the witness record supporting legislation on diabetes self-care in schools. It is a dated public record of participation in the policy discussion.

The record is evidence of advocacy and engagement. It does not establish that Kevin alone wrote the law, caused its passage, or determined every subsequent implementation decision.

Connection to the operating work

Kevin’s professional work involved children, families, school-related care, remote monitoring, physician participation, and reimbursement. The policy environment affected where and how a service could function. His career narrative includes advocacy around recognition of the home as a telemedicine setting and practical access to remote support.

The strongest linked public source here concerns the school self-care legislation. Broader causal claims about telemedicine policy are not inferred from that source.

Product and service relevance

Policy and reimbursement can shape a product’s actual usefulness. A remote technology may be technically feasible while the service model still depends on clinician participation, acceptable care settings, and payer arrangements. Kevin’s experience includes working across those constraints rather than considering them only after development.

This record adds public-policy participation to the broader account of product, clinical, and commercial collaboration. It complements the payer-program and care-delivery records without substituting for their distinct evidence.

Different sources establish different things

The archive includes outcome research, authored analysis, conference abstracts, patent applications, government records, independent reporting, and market context. Each type supports a different claim. A trial can support a result for a defined population; a patent application can establish inventor attribution and a dated design; a government record can establish participation or recognition.

Kevin’s career account supplies additional operating responsibilities and organizational details. Those are labeled as career records rather than presented as independently verified by an unrelated public link.

Diabetes Care, 2012

Kevin is a co-author of Integrating an Automated Diabetes Management System into the Family Management of Children with Type 1 Diabetes: Results from a 12-Month Randomized Controlled Technology Trial. The study followed 48 children and evaluated automated glucose-data collection and family feedback. It provides a specific outcome-research anchor for the Diabetech story.

The archive links the full article and DOI. Readers should use the original paper for study design, endpoints, statistical results, and limitations.

Diabetes Spectrum, 2013

Kevin authored Power and Pitfalls of Social Media in Diabetes Care. The article examines patient information and support in relation to clinical workflow and the risks of unreliable advice. It connects his technology and community experience to a professional discussion of how healthcare teams can engage with patient information networks.

Kaiser and rare-disease abstracts

The 2010 Diabetes Social Support Feasibility Pilot Study abstract includes Kevin in its author group. It supports his contribution to technology-mediated social support research. Related Roblin publications and an AHRQ-hosted presentation supply additional context but are not all represented as Kevin-authored works.

The 2021 ACMG supplement includes the LC-FAOD disease-monitoring-program abstract eP029, also listing Kevin as an author. This is public evidence for his rare-disease research contribution. It is an abstract rather than a full treatment-outcomes publication.

Technical and public records

US20050038680A1 names Kevin as inventor and dates the remote monitoring architecture to the early 2000s. The archive identifies it as a patent application and does not claim it is an active granted patent. D CEO and David Mendosa reporting describe Diabetech and GlucoMON during their early commercial period. Texas government documents add recognition and policy-participation context.

The separate publication index provides the original links, source descriptions, and distinctions between direct evidence and contextual material.

The published work

TrialTelemetry.com presents Kevin’s clinical-trial signal framework and a May 2026 white paper. The paper develops the March Operational Telemetry concept into a broader model for trial information, including endpoint, safety, patient, device, vendor, data-quality, and operational signals.

The website and paper are public work products grounded in his earlier operating history. They demonstrate a developed architecture and point of view. They are not presented as evidence of an undisclosed sponsor deployment or a regulator-endorsed product.

A signal needs an operating definition

The May paper treats a useful signal as more than a metric. It must have an identifiable origin, definition, timing expectation, context of use, and route to an accountable party. The model asks whether the underlying information is sufficiently complete, current, and trustworthy for its intended decision.

That distinction changes the architecture. Data may be suitable for exploratory analysis but not for a workflow with clinical consequences. An apparent change may reflect delayed entry, an altered definition, or a vendor bottleneck rather than a change in the underlying clinical or operational condition.

Systems of record remain important

The framework considers information from EHRs, EDC, CTMS, eTMF, IRT, eCOA, digital health technologies, safety systems, laboratories, imaging vendors, sites, and patient-generated sources. These are proposed source environments for the model. The framework coordinates signals across them while retaining their roles as systems of record.

Governance includes identity, authorized originators, timing, definitions, provenance, auditability, privacy, validation, change control, and traceability. The objective is to preserve enough context to know what moved through the system and why it was used.

C4I + Trust in practical terms

Kevin describes four interacting functions: ingestion, governance, analysis, and execution. Ingestion receives information with source context. Governance assesses whether and how it may be used. Analysis identifies meaningful patterns or exceptions. Execution connects the result to review, escalation, clarification, or an appropriately controlled automated task.

Trust is the condition for moving between those functions. The model also needs a record of what happened after a signal was generated: who reviewed it, what action occurred, and whether the action was documented.

Proposed use cases

The paper develops bounded use cases around recruitment and screening efficiency, query aging, site burden, vendor/infrastructure performance, digital endpoint readiness, safety-review support, and portfolio awareness. It also considers continuous inspection readiness and carefully defined regulator-facing signal exchange.

These are proposed applications of the framework. Each would require its own intended use, data assessment, evaluation, operational ownership, and appropriate specialist review. The paper is most useful as a way to make those dependencies explicit before a team commits to a technology implementation.

AI within a governed workflow

The design allows for rules-based, statistical, AI-assisted, and human analysis. Kevin places model context of use, input lineage, performance expectations, drift monitoring, human review, and accountability around any AI-derived signal. The model does not assume that an output becomes trustworthy merely because it can be generated quickly.

This connects the framework to his recent AI governance work and to the earlier clinical informatics experience. It also distinguishes current AI methods from the rules-based systems used in his historical remote-care programs.

Relationship to clinical operations and product leadership

The framework translates Kevin’s experience with patient-facing data capture, clinical systems, biosensors, vendor dependencies, quality, and distributed delivery into a lifecycle design method. Its pre-FPI review considers whether the trial can reliably generate and use the information on which its decisions depend.

The contribution is both strategic and practical: define a bounded need, map the data and human workflow, establish ownership and trust conditions, then evaluate the pathway before scaling it. The independent framework remains separate from the proprietary detail of his former employer’s systems.

The review objective

The Trial Telemetry pre-FPI review examines whether a trial can generate the signals its protocol, safety oversight, and operating decisions require. Kevin’s framework brings this examination into planning, before live execution reveals avoidable gaps. The method is a published advisory design rather than a claim of completed engagements for named sponsors.

Signal and source feasibility

The review starts with what the trial needs to know and when it needs to know it. Each signal is connected to its source, collection workflow, responsible party, timing, definition, and intended use. That makes it possible to examine whether the proposed data path can support the decision.

The method distinguishes event time from entry or receipt time. A quickly refreshed view can still reflect information entered well after the underlying event. The review therefore examines collection and handoff latency as part of the design.

Endpoint, device, and participant readiness

The framework considers whether endpoint-related collection fits the protocol and the participant’s actual experience. Devices, connectivity, availability, support, data completeness, and site responsibilities can all affect whether information arrives as intended.

Kevin’s experience with Rarify, eCOA/ePRO, and global service delivery, together with his non-production Dexcom integration development, provides the foundation for this analysis. The pre-FPI method organizes those concerns into a focused review rather than assuming that selection of a vendor resolves them.

Site burden and handoffs

A site may work across multiple studies, systems, and vendors. The review examines duplicate effort, workflow friction, handoff ownership, escalation, and the practical burden imposed by the technology stack. It also considers what happens when a source is missing, a device stops transmitting, or an expected step is delayed.

The aim is to identify an accountable response path. A risk that appears in a report still needs someone to investigate it and a defined way to act on the finding.

Governance and outputs

Kevin’s model calls for traceability among the original information, the rule or interpretation applied, the review decision, and the resulting action. It considers authorization, source context, quality expectations, privacy, and change management.

Useful review outputs would include a signal inventory, source/workflow map, ownership and escalation definitions, identified failure modes, and a bounded readiness plan. These are intended deliverables of the method, not completed study artifacts represented as historical results. The method can support sponsors, CROs, product teams, and clinical technology leaders evaluating a new data or endpoint pathway.