The full system matching must-have requirements, supporting the patient journey.
Requirements:
• All above, and:
• 5.1, 11.3 Provide a measure (estimate) for physical fitness (+ algorithm) (5 days, excluding algorithm development)
• 1.4, 3.3 Identity-card creation (What labels do you associate with who you are?) (2 days)
• 2.1 End-user driven identification of high risk situations (HRS) (bare minimum: end-user names HRS) (2 days)
• 2.2 System-driven identification of smoking HRS (timeframe, mood, plans) (5 days, excluding algorithm development)
• 2.3 System-driven identification of physical activity HRS (timeframe, mood, plans) (5 days, excluding algorithm development)
• 2.4 User-driven "Help" / "Danger" function when in a HRS with answer from VC (details to be explored) (2 days)
• 3.1 Possibility for users to discern individual motives, goals and challenges for behavior change (5 days)
• 3.2, 4.4, 11.2 VC can create, store and access persuasive profile for each user (3 days)
• 6.1, 9.1 Coaching applied specifically to (re)lapse (3 days)
• 6.3, 11.1 Run the (predictive) model to create actionable advice based on data (e.g. personalized training plans) (5 days, excluding algorithm development)
• 6.4 System automatically learns coaching preferences based on interactions (5 days, excluding algorithm development)
• 7.1 VC employs a few (identity-related) coaching techniques (details to be explored) (3 days)
• 7.2, 8.1 System allows for provision of (psycho)education about smoking and PA to end-user (e.g. handbook on how to quit smoking) (3 days, assuming content exists)
• 10.1 Measurement of psychosocio and behavioral characteristics (motivation, self-efficacy, intention, identity) to evaluate change (research perspective) (5 days)
• 10.3, 12.1 User activities in physical world (e.g. about smoking) can be suggested and tracked (8 days, excluding algorithm development)
• 12.2 VC can understand user progress (5 days, excluding algorithm development)
• 14.1 Conversations with end-users and health-care professionals to determine whether blended coaching is desired (5 days)
• Solving and preventing technical debt (8 days)
• Changes coming out of user testing of MFP (5 days)
User testing: When the MVP is finished it must be tested by users