Define the user story for this milestone

[kaichih]

Define the user story for this milestone. To define a smaller scope based on a given user story helps us to focus on something concrete. Then, derive it to detailed items that we should work on as first few milestones. The benefits of smaller user stories include but not limited to,

1. to be able to prove what we would like to do from a smaller scope. Prove of concept, basically.
2. to be easier to convince people and us that, we are moving with concrete goals.
3. to be able to present something exciting to community members.
4. to move the project dynamically, with flexibility.
5. to be easier to be adopted when we have limited engineering resource.

We used to conduct a systematic way to summarize a very useful user story. That was done for 2016 London Work Week, and we put our proposal here,
https://github.com/OpenIoMeT/Iomet-wiki/wiki/Meetup-and-Demo

Let me copy & paste here,

In order to identify most valuable user stories and include them into our first demo in the future, we collect most significant pain points, prioritize them, and then pick 4 of them based on technical evaluation and also the major concept of this project. We put all our meeting notes regarding to the demo online. 4 chosen user scenarios are:

1. Users get suggestions based on the health status / other information.
2. Users get the suggestions to locate closest hospitals.
3. The recovery status and health condition can be monitored.
4. Users get reminders to take medicines or any other instructions given by doctors.

Then, we proposed to have the following demo scripts to represent the main idea of the first 3 user scenarios:

A 70 years old Taiwanese elder who wants to join a marathon in London in 2016 June. To join a marathon is his/her dream. Due to some reasons, body condition for this user is actually not so proper for this, hence the health condition for this user has been mentioned for 3 months, together with regular appointment with a home doctor in Taiwan. This user is wearing a medical device that keeps monitoring the data, and sends to the home doctor via a smart-phone, together with geolocation & weather status. While the user is in London, the doctor from Taiwan find some abnormal of those indicators, hence suggests the user to find a proper hospital in London for further checks. The user then gets hospital suggestions from Open IoMeT.

The doctor provides medical suggestions based on the weather and the health condition to this user who is in London, and decide if this user is capable of joining the planned marathon. A no-go advise is suggested from the doctor due to some abnormal health condition data, and the list of closest hospitals will be delivered to the user. Further health condition will be monitored and sent to the doctor.

I would suggest to review this user story, and maybe we need to break this big user story into smaller user stories, and start from here. How about this?

[kaichih]

Copied from Greg:

For this particular user story, what we can complete without problem are:

1. Health suggestion information collection and representing in digested UI
2. Hospital and other medial resources based on geolocation

While the following features need experts:

1. From the information we collected, give suggestions to a group or individual users. Since we don't know how to determine what kind of indicates should trigger alarm, especially for individuals with special condition. Although for some basic indicates like air pollution we can survey public resources that should be available for everyone

2. For personal medical condition monitoring, and to remind taking pills or other necessary therapy, we can make it usable, technically. However, this heavily relies on whether user is willing and if user is able to keep the record accurate. For example, if user have a prescription for taking pills 3 times per day, our app only works if user keep tracking or input the correct data for tracking. I think this is kinda UX issue, but I have no idea about how to improve feature like this, to make it useful than a regular alarm app.

Rest parts are just solid enough to implement. Basically, just hard work for API, website, app, database, and other standard tech requirements. So we should have issues to raise our non-tech requirement and to see who can take some of them, as well as having some tech issues to solve for the same user story. Since we are using GitHub, that means we may use milestone for the whole single user story, and have tech and non-tech issues for requirements to complete the story.

[kaichih]

No matter what features we would like to include, we need to have a place to reside and represent them to users. What's in our mind? Would it be an app? Thanks.