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.
Sources and record basis
The project account is based on Kevin’s CV, approved career statements, and supporting project materials. Related public research and professional work are available in the source index.
Challenged automatic CAPA for a two-hour CGM data gap, citing product-design limitations; the account does not establish QA’s final disposition. The zero-findings audit is reported in Kevin’s career records. The underlying audit report is not a public attachment in this archive.