Skip to Content

Wiki source code of b. Use Case with Claims

Last modified by Dhara Shah on 2025/11/04 09:32
Show last authors
1 {{html}}
2 <label for="status">Status:</label>
3 <select name="status" id="status">
4 <option value="Not Started">Not Started</option>
5 <option value="In Progress">In Progress</option>
6 <option value="Under Review">Under Review</option>
7 <option value="In Evaluation">In Evaluation</option>
8 <option value="Finalized">Finalized</option>
9 </select>
10 {{/html}}
11
12 == **UC-01: Finding Overlapping Interests Between Patients** ==
13
14 |(% style="width:166px" %)**Scope**|(% style="width:653px" %)Enable dementia patients to discover and share common interests with peers, fostering social connection and reducing loneliness.
15 |(% style="width:166px" %)**Objective**|(% style="width:653px" %)Enhance social interactions by helping patients identify shared hobbies, experiences, or preferences, and by facilitating introductions or conversation starters through the robot.
16 |(% style="width:166px" %)**TDP**|(% style="width:653px" %)TDP 2, 3
17 |(% style="width:166px" %)**IDP**|(% style="width:653px" %)(See Section Interaction Design Pattern)
18 |(% style="width:166px" %)**Actors**|(% style="width:653px" %)(((
19 **System: **Social Robot (conversation partner, memory support)
20
21 **Primary: **Dementia Patient (socializer)
22
23 **Secondary: **Caregiver (human support)
24 )))
25 |(% style="width:166px" %)**Triggers**|(% style="width:653px" %)(((
26 * Robot detects a patient sitting alone or being inactive in a social setting (idle).
27 * Patient expresses boredom or lack of engagement (“I don’t know what to do”).
28 * Caregiver signals that a resident could benefit from social interaction.
29 )))
30 |(% style="width:166px" %)**Pre-Condition**|(% style="width:653px" %)(((
31 * **Environmental State:** In the facility’s common lounge; several residents are present, engaged in light conversation or individual activities.
32 * **Human State:** Rebecca is seated alone and not participating in social interaction. The caregiver is assisting another resident and cannot intervene.
33 * **System State:** The robot is active and monitoring the environment. It has access to previously collected interest profiles from questionnaires and conversational data (all consented and locally stored). Facial and speech-recognition modules are active for detecting presence and affect.
34 )))
35 |(% style="width:166px" %)**Main Flow**|(% style="width:653px" %)(((
36 **MF1. **Robot notices Rebecca alone and greets her (“Hi Rebecca, how are you today?”).
37
38 **MF2.** Robot asks light, open-ended questions to elicit interests (“What kind of music do you like?”) or have small conversation ("How are you?")
39
40 **MF3.** Robot retrieves or updates Rebecca’s stored interests.
41
42 **MF4.** Robot cross-checks interests with nearby patients.
43
44 **MF5.** Robot facilitates an introduction (“Mary was just telling us about her honeymoon—you also love to travel!”).
45
46 **MF6.** Robot monitors conversation and provides light prompts if needed, then disengages once social interaction continues naturally.
47 )))
48 |(% style="width:166px" %)**Alternative Flow**|(% style="width:653px" %)(((
49 **AF1:** Patient gives minimal answers → Robot probes gently with new topics or uses family-provided interest data.
50
51 **AF2:** No matching interests detected → Robot suggests group activity or transitions to general chat.
52
53 **AF3:** Patient expresses distress → Robot stops and alerts caregiver.
54 )))
55 |(% style="width:166px" %)**Post-Condition**|(% style="width:653px" %)(((
56 * **Environmental State:** The common lounge now has active conversation between Rebecca and another resident. Socializing has increased in general in the room.
57 * **Human State:** Rebecca is conversing comfortably, showing positive affect or laughter. The caregiver observes improved engagement without direct facilitation.
58 * **System State:** Robot logs the successful introduction, updates both residents’ interest profiles, and flags new social pairings for caregiver review. Robot returns to monitoring mode.
59 )))
60 |(% style="width:166px" %)**Exceptions**|(% style="width:653px" %)(((
61 * **If system/data is unavailable** → Robot defaults to general conversation starter prompts.
62 * **If patient consent is withdrawn** → Robot disables access to personal data.
63 * **If patient refuses engagement** → Robot politely disengages and records the event.
64 )))
65 |(% style="width:166px" %)**Data Used / Produced**|(% style="width:653px" %)(((
66 |=Data Type|=Source|=Usage|=Consent & Storage
67 |Patient interest profiles|Questionnaire, prior chats, family input|Identifying overlapping interests|Informed consent from family or patient; encrypted local storage
68 |Conversational data|Speech logs|Detect interest and update profiles|Informed consent from family or patient; Temporary storage
69 |Social pairing logs|System-generated|Track successful interactions|Informed consent from family or patient; Local storage (visible to caretakers)
70
71
72 )))
73
74 |(% style="width:135px" %)**Claims (title)**|(% style="width:245px" %)**Function**|(% style="width:238px" %)**Effect(s)**|(% style="width:201px" %)**Action Sequence Step(s)**
75 |(% style="width:135px" %)CL1|(% style="width:245px" %)Monitoring mode|(% style="width:238px" %)System accurately detects when a patient is in need of introduction or conversational help.|(% style="width:201px" %)MF1
76 |(% style="width:135px" %)CL2|(% style="width:245px" %)Interest gathering|(% style="width:238px" %)Accurate detection and recall of user interests.|(% style="width:201px" %)MF2, MF3, MF6
77 |(% style="width:135px" %)CL3|(% style="width:245px" %)Social matching|(% style="width:238px" %)Users feel more socially connected after facilitated introduction. Patient feels more engaged/interested in the conversation|(% style="width:201px" %)MF4, MF5
78 |(% style="width:135px" %)CL4|(% style="width:245px" %)Conversation facilitation|(% style="width:238px" %)Increases comfort and participation in dialogue.|(% style="width:201px" %)MF2, MF5, MF6
79
80 == **UC-02: Scheduling Meaningful Activities** ==
81
82 |(% style="width:166px" %)**Scope**|(% style="width:653px" %)Enable dementia patients to participate in meaningful daily activities and reduce boredom through contextual reminders, personalized scheduling, activity facilitation.
83 |(% style="width:166px" %)**Objective**|(% style="width:653px" %)Provide meaningful structure and reduce boredom in the patients' day by organizing and facilitating activities based on personal preferences and contextual cues
84 |(% style="width:166px" %)**TDP**|(% style="width:653px" %)TDP 2, 3
85 |(% style="width:166px" %)**IDP**|(% style="width:653px" %)(See Section Interaction Design Pattern)
86 |(% style="width:166px" %)**Actors**|(% style="width:653px" %)(((
87 **System**: Social Robot (activity scheduler and reminder)
88
89 **Primary**: Dementia Patient (activity participant)
90
91 **Secondary**: Caregiver (human support)
92 )))
93 |(% style="width:166px" %)**Triggers**|(% style="width:653px" %)(((
94 * The patient expresses boredom, inactivity is detected, or it is time for a scheduled activity.
95 * The caregiver updates or confirms available activities in the system.
96 )))
97 |(% style="width:166px" %)**Pre-Condition**|(% style="width:653px" %)(((
98 * **Environmental State:** Several residents are seated in the common lounge of the care facility. No scheduled group activity is currently in progress.
99 * **Human State:** Rebecca, a PwD, appears idle and disengaged. Caregiver John is occupied with administrative tasks and not in the immediate area.
100 * **System State:** The robot is active and connected to the facility’s scheduling database. The system has detected an unstructured time period and has access to stored patient profiles, including Rebecca’s activity preferences and consent information.
101 )))
102 |(% style="width:166px" %)**Main Flow**|(% style="width:653px" %)(((
103 **MF1**. Robot detects unstructured time or recognizes the patient’s idle state.
104
105 **MF2**. Robot retrieves data on available activities, locations, and required caregivers.
106
107 **MF3**. Robot cross-references patient interests and current availability.
108
109 **MF4**. Robot offers suitable activities using polite, supportive phrasing:
110
111 * (% style="background-color:transparent" %)“Would you like to get coffee with Maria in the lounge?”
112 * “There’s a group walk starting in 10 minutes—should I walk with you there?”
113 * “There’s a music group in the blue common area. Would you like to join?”
114
115 **MF5**. Patient responds verbally or through tablet interface.
116
117 **MF6**. Robot confirms choice, provides reminder when closer to activity, provides guidance or directions, and notifies caregivers if their presence is needed.
118
119 **MF7**. After the activity, robot asks for quick feedback: “Did you enjoy that?” or notes attendance/participation.
120
121 **MF8**. Robot updates patient preference data accordingly.
122 )))
123 |(% style="width:166px" %)**Alternative Flows**|(% style="width:653px" %)(((
124 **AF1**: Patient declines → Robot offers gentle alternative (“Would you like to do something quieter, like reading or listening to music?”).
125
126 **AF2**: No available activities → Robot engages patient in conversation, suggests conversation with another patient, or suggests a solo task.
127
128 **AF3**: Patient is confused or unsure → Robot repeats the prompt more slowly or displays a visual option on its tablet. If needed, alerts a caregiver.
129 )))
130 |(% style="width:166px" %)**Post-Condition**|(% style="width:653px" %)(((
131 * **Environmental State:** An activity (e.g., coffee meeting or music session) is now in progress. The lounge area shows increased engagement and social interaction among residents.
132 * **Human State:** Rebecca has agreed to and joined an appropriate activity, expressing interest or enjoyment. Caregiver John has been automatically notified of participant status and required supervision, if applicable.
133 * **System State:** The robot has logged Rebecca’s participation, updated her preference data, and recorded feedback to refine future suggestions. The robot returns to standby or assists additional patients.
134 )))
135 |(% style="width:166px" %)**Exceptions**|(% style="width:653px" %)(((
136 * **If system/data is unavailable **→ Robot defaults to generic prompts (“Would you like to do something fun now?”).
137 * **If consent is revoked **→ Robot ceases using personalized data and switches to neutral, non-specific suggestions.
138 * **If patient is distressed or has a negative reaction ->** Robot apologizes, ends interaction, and alerts caregiver.
139 )))
140 |(% style="width:166px" %)**Data Used / Produced**|(% style="width:653px" %)(((
141 |=Data Type|=Source|=Usage|=Consent & Storage
142 |Patients preferences & interests|Family questionnaires, caretaker input, human-robot interactions|Tailor activity suggestions|Informed consent from family or patient; encrypted local storage
143 |Facility activity schedule|Facility database (if available) or caretaker input|Identify available activities and sessions|Institutional approval; local storage
144 |Possible activities|Staff input, approval from caretaker for new activities|Ensure if activity is possible and if caretaker supervision is required|Institutional approval; local storage
145 |Caregiver availability|Facility database (if available), or notification and approval from caretaker|Ensure supervisions for activities where required|Institutional approval; local storage
146 |Activity feedback|Human-robot interactions, robot survey of attendance|Adapt patient  preference database|Informed consent from family or patient;  encrypted local storage or anonymized data
147
148
149 )))
150
151 |(% style="width:135px" %)**Claims (title)**|(% style="width:245px" %)**Function**|(% style="width:238px" %)**Effect(s)**|(% style="width:201px" %)**Action Sequence Step(s)**
152 |(% style="width:135px" %)CL1 |(% style="width:245px" %)Activity organizing and scheduling|(% style="width:238px" %)More time spent in meaningful activity blocks; fewer idle periods. Patients feel less bored and more independent.|(% style="width:201px" %)MF4, MF6
153 |(% style="width:135px" %)CL2|(% style="width:245px" %)Personalized activity matching|(% style="width:238px" %)Increases user interest and likelihood to join activities.|(% style="width:201px" %)MF3
154 |(% style="width:135px" %)CL3|(% style="width:245px" %)Persuasive but polite prompting|(% style="width:238px" %)Supportive tone increases comfort and trust causing more willingness to join activity and interact with robot.|(% style="width:201px" %)MF4, MF6, MF7
155 |(% style="width:135px" %)CL4|(% style="width:245px" %)Data collection|(% style="width:238px" %)Allows the robot to provide more useful suggestions. |(% style="width:201px" %)MF1, MF2, MF3, MF6, MF7, MF8
156 |(% style="width:135px" %)CL5|(% style="width:245px" %)Notification and reminder system for patients and caretakers|(% style="width:238px" %)Patients know what is happening at the facility. Caretakers feel less burden keeping track of activities.|(% style="width:201px" %)MF6
157 |(% style="width:135px" %)CL6|(% style="width:245px" %)Providing contextual suggestions|(% style="width:238px" %)Contextual reminders improve recall and activity follow-through.|(% style="width:201px" %)MF4