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.
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.