RE: [use cases] Remote health monitoring system - updated with mapping to proposed architecture

See attachment. I added slide 3 that maps this use case to the architecture we are discussing.

BR

Claes Nilsson
Master Engineer - Web Research
Advanced Application Lab, Technology

Sony Mobile Communications
Tel: +46 70 55 66 878
claes1.nilsson@sonymobile.com<mailto:Firstname.Lastname@sonymobile.com>

sonymobile.com<http://sonymobile.com/>

[cid:image002.png@01D07CF0.1AD5D140]

From: Nilsson, Claes1
Sent: den 21 april 2015 11:42
To: 'public-wot-ig@w3.org'
Subject: RE: [use cases] Remote health monitoring system - updated and slides

Below is the updated use case text. I also attach the slides I showed at the F2F on April 21st.


-------
What is the user motivation for the use case
-------
John is retired and lives alone in his own apartment. He has bad legs and there is a constant risk that he falls. If that happens he is not able to rise from the floor without help. In addition, John suffers from heart arrhythmias and diabetes.

Due to John's condition he needs remote monitoring by his healthcare provider. He therefore wears a wristband capable of continuously monitoring his heart rate and detect irregular heart rhythms as well as detecting a fall situation. A future version of the wristband will also be capable of non-invasive monitoring of his blood glucose level. The wristband communicates wirelessly with John's healthcare provider. This remote monitoring system could be seen as a complement to a normal home alarm system for elderly people with which old persons manually could call an emergency service. The differences are that the wristband system detects severe conditions automatically, which is needed if the old person is confused or gets unconscious, and also has the possibility to measure medical parameters such as heart rate and heart rhythm.


-------
How does this translate to a technical Description
--------
When the system is in operation everything works automatic without any user interface. The remote monitoring application runs in a cloud server and can communicate with the wristband. A local router, situated for example in a smartphone, may be needed to translate between a local communication method such as Bluetooth Low Energy and the mobile network or wifi, but at application level end-to-end security and communication through firewalls are achieved. The communication must be reliable and the power consumption in the wristband low to achieve long battery life.

User interaction is only required at system installation. The user, or another trusted person, e.g. a relative, health care personnel or personal assistant, has to use a web browser to log in to the remote monitoring application and the user has to approve that the application is given access to his/her wristband using an existing authorize system, e.g. OAuth.

To provide service discovery for applications the wristband, during the system installation, is registered in a discovery service that contains a service description for the wristband. This service description states for example manufacturer, owner and the APIs to access the resources of the wristband.

Other issues to consider are for example:

*        Use of IPv6 to give the wristband a unique and possible global and persistent address

*        Access to the resources in the device through URIs and REST APIs

*        Need for protocol converting, e.g. HTTP-CoAP, gateways

*        Need for cloud backend to the wristband


-------
What application domains are related (e.g. referring to the taxonomy)
-------
main: Smart lifecare / Healthcare and medical / Remote patient monitoring and care
related:


-------
What interaction pattern with or btw things can be observed
-------
Registration and authorization:  Registration of IoT device to make it discoverable and accessible by applications. Registration and authorization of applications to access resources on IoT devices.
User interface: User interface only for registration and authorization. Operation is "user interface less".
Security: End-to-end security cloud service - IoT device


-------
Accessibiliy considerations
-------
Low vision, blindness, deafness and hearing loss does not provide any limitation for users during operation of the system as the system is UI-less. However, the system installation process requires operation of a normal web browser, which may require assistance for people with physical or mental limitations.


-------
Which aspects are not considered
-------
Life cycle of devices, services and applications
Dealing with faults
Replacing devices
Taking devices out of operation


Claes Nilsson
Master Engineer - Web Research
Advanced Application Lab, Technology

Sony Mobile Communications
Tel: +46 70 55 66 878
claes1.nilsson@sonymobile.com<mailto:Firstname.Lastname@sonymobile.com>

sonymobile.com<http://sonymobile.com/>

[cid:image003.png@01D07CF0.1AD5D140]