Wiki source code of b. Use Case with Claims
Version 10.1 by Dhara Shah on 2025/10/24 16:43
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 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 | == **Use case UC-01: Finding Overlapping Interests Between Patients** == | ||
| 13 | |||
| 14 | |(% style="width:166px" %)**Scope**|(% style="width:653px" %) | ||
| 15 | |(% style="width:166px" %)**Objective**|(% style="width:653px" %)Enhance social connections and reduce loneliness by helping dementia patients discover and share shared interests | ||
| 16 | |(% style="width:166px" %)**TDP**|(% style="width:653px" %)TBD | ||
| 17 | |(% style="width:166px" %)**IDP**|(% style="width:653px" %)TBD | ||
| 18 | |(% style="width:166px" %)**Actors**|(% style="width:653px" %)((( | ||
| 19 | Social Robot (conversation partner, memory support) | ||
| 20 | |||
| 21 | Dementia Patient (socializer) | ||
| 22 | |||
| 23 | Caregiver (human support) | ||
| 24 | ))) | ||
| 25 | |(% style="width:166px" %)**Pre-Condition**|(% style="width:653px" %)Rebecca is in the common areas or in an activity and is unsure of who is around her and what to talk to others about | ||
| 26 | |(% style="width:166px" %)**Post-Condition**|(% style="width:653px" %)Rebecca knows shared interests with peers and feels more confident starting a conversation | ||
| 27 | |(% style="width:166px" %)**Action Sequence**|(% style="width:653px" %)((( | ||
| 28 | ~1. Rebecca enters an activity or common area and robot notices her alone | ||
| 29 | |||
| 30 | 2. Robot greets Rebecca and asks her a question (ex. how was your day, what is your favorite music genre, etc.) | ||
| 31 | |||
| 32 | * OR Robot notices Rebecca's arrival into a group conversation or activity and brings her into the conversation (ex. "Hi Rebecca, welcome! Mary was just telling us a story about her honeymoon.") | ||
| 33 | |||
| 34 | 3. Robot recognizes key interests of Rebecca through conversation and stores information | ||
| 35 | |||
| 36 | * OR Robot uses responses from a questionnaire that Rebecca, her family, or the caretaker has filled out | ||
| 37 | * OR Robot systematically polls patients over time on interests | ||
| 38 | |||
| 39 | 4. Robot recalls and retrieves Rebecca's interests and compares it to other participants present in the area | ||
| 40 | |||
| 41 | 5. Robot guides Rebecca to Mary who also loved to travel and creates an introduction or re-introduction (ex. "Remember your friend Mary who loves to travel? Would you like to talk to her?") | ||
| 42 | |||
| 43 | * OR Robot brings up an overlapping interest with other patients near Rebecca (ex. Robot knows that both Robert and Rebecca had lots of pets growing up, and says "If I remember correctly, both you and Robert had dogs! What was your favorite part of having a dog?") | ||
| 44 | |||
| 45 | 6. Robot continues to facilitate different conversations and activities around the room as needed | ||
| 46 | |||
| 47 | * Examples | ||
| 48 | ** Suggests an activities such as dancing, singing, or playing cards | ||
| 49 | ** Reminds patients of their own stories and others ("What was that dessert that you told me your parents bought you every birthday?") ("What was that card game that you and Mary like to play in the main activity room?") | ||
| 50 | ))) | ||
| 51 | |(% style="width:166px" %) |(% style="width:653px" %) | ||
| 52 | |||
| 53 | |(% style="width:135px" %)**Claims (title)**|(% style="width:245px" %)**Function**|(% style="width:238px" %)**Effect(s)**|(% style="width:201px" %)**Action Sequence Step(s)** | ||
| 54 | |(% style="width:135px" %)CL1 Interest gathering|(% style="width:245px" %)Ask questions, store answers|(% style="width:238px" %)Patient preferences are captured and remembered|(% style="width:201px" %)Steps 2-3 | ||
| 55 | |(% style="width:135px" %)CL2 Social matching|(% style="width:245px" %)Match interest with others|(% style="width:238px" %)Patient is reminded of similarities with others and will feel more engaged/interested in the conversation|(% style="width:201px" %)Step 4 | ||
| 56 | |(% style="width:135px" %)CL3 Conversation facilitation|(% style="width:245px" %)Encourage interaction through introductions and conversation starters|(% style="width:238px" %)Patients feels more confident and relaxed engaging in conversation|(% style="width:201px" %)Steps 5-6 | ||
| 57 | |||
| 58 | == **Use case 2: Scheduling Meaningful Activities** == | ||
| 59 | |||
| 60 | |(% 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. | ||
| 61 | |(% 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 | ||
| 62 | |(% style="width:166px" %)**TDP**|(% style="width:653px" %)TBD | ||
| 63 | |(% style="width:166px" %)**IDP**|(% style="width:653px" %)TBD | ||
| 64 | |(% style="width:166px" %)**Actors**|(% style="width:653px" %)((( | ||
| 65 | **System**: Social Robot (activity scheduler and reminder) | ||
| 66 | |||
| 67 | **Primary**: Dementia Patient (activity participant) | ||
| 68 | |||
| 69 | **Secondary**: Caregiver (human support) | ||
| 70 | ))) | ||
| 71 | |(% style="width:166px" %)**Triggers**|(% style="width:653px" %)((( | ||
| 72 | * The patient expresses boredom, inactivity is detected, or it is time for a scheduled activity. | ||
| 73 | * The caregiver updates or confirms available activities in the system. | ||
| 74 | ))) | ||
| 75 | |(% style="width:166px" %)**Pre-Condition**|(% style="width:653px" %)((( | ||
| 76 | * **Environmental State:** Several residents are seated in the common lounge of the care facility. No scheduled group activity is currently in progress. | ||
| 77 | * **Human State:** Rebecca, a PwD, appears idle and disengaged. Caregiver John is occupied with administrative tasks and not in the immediate area. | ||
| 78 | * **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. | ||
| 79 | ))) | ||
| 80 | |(% style="width:166px" %)**Main Flow**|(% style="width:653px" %)((( | ||
| 81 | **MF1**. Robot detects unstructured time or recognizes the patient’s idle state. | ||
| 82 | |||
| 83 | **MF2**. Robot retrieves data on available activities, locations, and required caregivers. | ||
| 84 | |||
| 85 | **MF3**. Robot cross-references patient interests and current availability. | ||
| 86 | |||
| 87 | **MF4**. Robot offers suitable activities using polite, supportive phrasing: | ||
| 88 | |||
| 89 | * (% style="background-color:transparent" %)“Would you like to get coffee with Maria in the lounge?” | ||
| 90 | * “There’s a group walk starting in 10 minutes—should I walk with you there?” | ||
| 91 | * “There’s a music group in the blue common area. Would you like to join?” | ||
| 92 | |||
| 93 | **MF5**. Patient responds verbally or through tablet interface. | ||
| 94 | |||
| 95 | **MF6**. Robot confirms choice, provides guidance or directions, and notifies caregivers if their presence is needed. | ||
| 96 | |||
| 97 | **MF7**. After the activity, robot asks for quick feedback: “Did you enjoy that?” or notes attendance/participation. | ||
| 98 | |||
| 99 | **MF8**. Robot updates patient preference data accordingly. | ||
| 100 | ))) | ||
| 101 | |(% style="width:166px" %)**Alternative Flows**|(% style="width:653px" %)((( | ||
| 102 | **AF1**: Patient declines → Robot offers gentle alternative (“Would you like to do something quieter, like reading or listening to music?”). | ||
| 103 | |||
| 104 | **AF2**: No available activities → Robot engages patient in conversation, suggests conversation with another patient, or suggests a solo task. | ||
| 105 | |||
| 106 | **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. | ||
| 107 | ))) | ||
| 108 | |(% style="width:166px" %)**Post-Condition**|(% style="width:653px" %)((( | ||
| 109 | * **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. | ||
| 110 | * **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. | ||
| 111 | * **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. | ||
| 112 | ))) | ||
| 113 | |(% style="width:166px" %)**Exceptions**|(% style="width:653px" %)((( | ||
| 114 | * **If system/data is unavailable **→ Robot defaults to generic prompts (“Would you like to do something fun now?”). | ||
| 115 | * **If consent is revoked **→ Robot ceases using personalized data and switches to neutral, non-specific suggestions. | ||
| 116 | * **If patient is distressed or has a negative reaction ->** Robot apologizes, ends interaction, and alerts caregiver. | ||
| 117 | ))) | ||
| 118 | |(% style="width:166px" %)**Data Used / Produced**|(% style="width:653px" %)((( | ||
| 119 | |=Data Type|=Source|=Usage|=Consent & Storage | ||
| 120 | |Patients preferences & interests|Family questionnaires, caretaker input, human-robot interactions|Tailor activity suggestions|Informed consent from family or patient | ||
| 121 | |Facility activity schedule|Facility database (if available) or caretaker input|Identify available activities and sessions|Institutional approval | ||
| 122 | |Possible activities|Staff input, approval from caretaker for new activities|Ensure if activity is possible and if caretaker supervision is required|Institutional approval | ||
| 123 | |Caregiver availability|Facility database (if available), or notification and approval from caretaker|Ensure supervisions for activities where required|Institutional approval | ||
| 124 | |Activity feedback|Human-robot interactions, robot survey of attendance|Adapt patient preference database|Informed consent from family or patient | ||
| 125 | |||
| 126 | |||
| 127 | ))) | ||
| 128 | |||
| 129 | |(% style="width:135px" %)**Claims (title)**|(% style="width:245px" %)**Function**|(% style="width:238px" %)**Effect(s)**|(% style="width:201px" %)**Action Sequence Step(s)** | ||
| 130 | |(% style="width:135px" %)CL1 |(% style="width:245px" %)Collect and store data of possible activities|(% style="width:238px" %)Robot has a database of feasible activities for possible locations to be conducted by whichever available caretakers.|(% style="width:201px" %)Steps 1, 6, and 7 | ||
| 131 | |(% style="width:135px" %)CL2 |(% style="width:245px" %)Organize activities based on interests|(% style="width:238px" %)There are more meaningful activities available for patients to do|(% style="width:201px" %)Steps 2-3 | ||
| 132 | |(% style="width:135px" %)CL3 |(% style="width:245px" %)Schedules activities for patients|(% style="width:238px" %)Patients feel less bored because they know how they can fill their day|(% style="width:201px" %)Step 2 | ||
| 133 | |(% style="width:135px" %)CL4|(% style="width:245px" %)Reminds patients and caretakers of activities|(% style="width:238px" %)Patients know what is happening at the facility. Caretakers feel less burden keeping track of activities.|(% style="width:201px" %)Step 4 | ||
| 134 | |(% style="width:135px" %)CL 5|(% style="width:245px" %)Facilitate activities|(% style="width:238px" %)Patients know where to go, how long to wait, and information about the activity.|(% style="width:201px" %)Step 5 |