As a demonstration and educational tool, and to preview to executives anticipated sensor data analysis capabilities, we made a Windows application that simulated three typical insulin-dependent diabetic patients. One could elect to be the physician, reviewing three days of the patient’s recent history and making adjustments to insulin pump settings to improve their care, or choose to be the patient, selecting meals and insulin dosages over a two day period and seeing how your blood glucose responded to your choices.
Physician mode patient selection screen allowing healthcare providers to choose from three simulated diabetic patients and review their care history.Physician interface overlay showing additional controls and information available when reviewing patient data in healthcare provider mode.Physician view displaying three days of patient glucose data, insulin doses, and meal markers, allowing adjustments to pump settings to improve care.Patient mode interface allowing users to simulate being a diabetic patient, selecting meals and insulin dosages over two days to see blood glucose responses.Patient mode selection screen allowing users to choose which simulated patient they want to experience from the patient perspective.Lab report view showing laboratory test results and key health metrics for the simulated patient, providing additional clinical context.Bolus calculator wizard helping users determine appropriate insulin doses based on current glucose, carbohydrates, and correction factors.Language selection screen allowing users to choose their preferred interface language for the virtual patient application.
My role: concept, interaction and visual design, patient selection and operationalization, and numerous demonstrations to executives, visiting endocrinologists, and community groups
Lessons learned: A skilled, flexible developer and a designer who listens can make an experiment into something special, if they are both grounded in the subject matter.