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.
Care and program lifecycles
Sources and record basis
- Current program contextCMS · ACCESS Model
Official program information for ACCESS. Kevin’s discussion is an application of his program-design experience, not a claim of CMS employment or program participation.
- Current program contextFDA · TEMPO Digital Health Devices Pilot
Official TEMPO information. The archive distinguishes current market interpretation from Kevin’s historical project work.
- Market contextPhilips · Virtual Care Management announcement, 2023
Describes Philips Virtual Care Management. It illustrates the later market category; it is not, by itself, verification of the full Diabetech licensing chain.
CMS ACCESS and FDA TEMPO are external program context. The archive does not establish Kevin’s participation, employment, or an award from either initiative.