https://github.com/QJl-leon/BUS-Coursework.git
- Bin He
- Emmanuel Omosebi
- Jialiang Qiu
- Mengze Wang
- Shuze Dong
Remote Health Monitoring - Supporting Independent Living for Older Adults in the UK
| Persona Name | Role/User type | Goals | Pain Points | Related User Stories (IDs) |
|---|---|---|---|---|
| JACK | Elder person | To easily record daily vital signs and understand their health is stable without complex technology. | Forget to take index readings; Forget where they wrote index readings |
S1 |
| JACK2 | Relative of Elder person (son, nephew, etc) | To monitor elderly person health remotely and receive alerts when readings become abnormal. | I don’t know if vitals are worsening; I only find out about health of elder during emergency |
S2 |
| JACK3 | Doctor / GP | Review patient data longitudinally to make informed decisions | Inability to collect data daily due to time/resource limits | S3 |
| JACK4 | Relative of Elder person (son, nephew, etc) | Convert health data and indexes to meaningful information | I don’t understand my health data | S4 |
| JACK5 | Relative of Elder | Remote live viewing of my elder relative health data | My dad leaves with me but I go to work from 9 to 4. I want to know he is okay even when I am not around without constantly contacting him. | S5 |
| JACK6 | Social care worker | I want to take over the patient from my colleagues efficiently. | Information gap: the latest care worker can not see the data of the last visit and the record, notes by other care worker. The newest up-date from doctor. | S6 |
| JACK7 | Social care worker | Provide clear, role appropriate escalation guidance for social care worker, when the elevated blood pressure is detected, so they can confidently without making clinical decisions outside their responsibility. | Responsibility boundary + Sensitive risk; Uncertainty around when to escalate the case |
S7 |
For elder patients, elder care clinics, social workers and families of elderly patients
Who is suffering from high blood pressure need continuous and reliable access to patient health information
The SmileCare system is a simplified monitoring and report system
That provides a centralized platform integrating both continuous health monitoring and structured visits records
Unlike traditional health care monitoring systems that rely on periodic manual entry and many different paper records
Our product delivers real time structured reports and early warning alerts easily and continuously to all stakeholders
| Story ID | Feature (epics) | Story title | User Story | Acceptance Criteria | Priority (Must / Should / Could) | Justification of prioritisation / Trade-off | Story Owner |
|---|---|---|---|---|---|---|---|
| S1 | Health Monitoring | Daily BP Status After Reading | As a 65-year-old patient with high blood pressure, I want to see a simple message after my daily test so I know whether I need to rest. | Given I select Hypertension Focus Feature, When I finish my blood pressure measurement, Then the system displays my BP status (Normal/High/Danger) and tells me if I need to rest. |
Must | Core functions, the basis of other functions | Jialiang Qiu |
| S2 | Alerts and Notifications | Alert When BP Approaches or Exceeds Danger Level | As a son of the patient, I want to receive a notification when a blood pressure reading becomes dangerous, so I can contact the GP or call an emergency. | Given the patient has a linked relative and BP thresholds are configured, When a new blood pressure reading meets or exceeds the Danger threshold, Then an alert is sent to the relative, including the reading, timestamp, and severity label. |
Must | Ensures timely intervention for emergencies; Directly addressing safety pain points from personas |
Bin He |
| S3 | Reporting and Trends | 7-Day BP Trend and Summary for GP | As a GP, I want a structured summary of my patient’s blood pressure readings over time, so I can review the trend quickly without manually gathering daily readings. | Given the patient has at least one blood pressure reading recorded on each of the last 7 days, When the GP opens the patient dashboard, Then the system displays a 7-day trend graph and a short summary (average BP, highest BP, and number of Danger readings). |
Must | GPs need to see whether blood pressure is improving or worsening over time. A trend graph and short summary make the readings usable in a real consultation, instead of scanning raw numbers. | Emmanuel Omosebi |
| S4 | Health Data Communication | Plain-Language BP Summary for Relatives | As a relative of an elder person, I want the system to convert blood pressure readings into simple explanations, so I can tell if my loved one is stable or worsening without medical training. | Given that blood pressure thresholds are configured, and historical readings exist, When a new reading is recorded or the relative opens the dashboard, Then the system displays a clear status label (Normal/High/Danger), and a short plain-language summary (1–2 sentences) based on the latest reading. |
Must | This feature directly addresses a core safety and usability pain point: relatives without medical training often struggled to interpret raw health data. Misinterpretation may lead to delayed intervention or unnecessary panic. Developing accurate medical interpretation logic requires validated thresholds and careful design to avoid misleading summaries. However, due to its strong impact on safety and user confidence, this feature is prioritized as must over purely aesthetic or convenience enhancements. |
Mengze Wang |
| S5 | Remote Monitoring | View Elder's Live BP Readings Remotely | As a relative of an elder person, I want to remotely view my elderly relative's blood pressure readings and status updates in near real-time during the day, so that I can feel reassured they are okay while I'm at work, without needing to call them constantly. | Given I am logged in as a linked relative, When I open the Remote View section, Then I can see the most recent blood pressure reading(s) with timestamp and status label. |
Should | This feature significantly enhances user experience and peace of mind, addressing the core pain point of "constantly disturbing them with phone calls." However, it depends on underlying data collection and transmission (e.g., basic monitoring in JACK2), so it is prioritised as "Should" to be implemented after core alerting features. | Shuze Dong |
| S6 | Data Access and Records | View Previous Visit Record and Notes | As a social care worker, I want to see the last visit’s blood pressure record and note. So that I can spot changes and avoid repeating question. | Given I am logged in as a social care worker with access to the patient, When I view the patient profile, Then the last visit’s blood pressure record and note are shown with a timestamp. |
Should | Reduces redundancy in care, aligns with J6 pain points on info gaps; Trade-off: Not must-have for MVP but enhances efficiency post-core monitoring |
Bin He |
| S7 | Urgent Action Recommendation | Recommended Next Step After High or Danger Reading | As a social care worker, I want the system to show a recommended next step after a high or dangerous blood pressure reading, so I know what action to take immediately and get reassurance when no escalation is needed. | Given BP thresholds are configured, When a reading is classified as High or Danger, Then the system shows a recommended next step (e.g., rest/recheck for High; contact GP/urgent guidance for Danger). And when a reading is Normal, Then the system shows reassurance text. |
Could | This feature reduces the risk for elderly patients, assists them in handling emergencies, and helps social care workers choose the correct response. It is an important link connecting patients, social workers, and doctors. |
Jialiang Qiu |