MH@A - Deliverable 3.6 inc Appendix II/file/D3 6 - Acceptance of Hardware... · T3.2-026 Alarm list...

DELIVERABLE 3.6

05-10-2009

1 (27)

www.myhealth-age.eu

Deliverable3.6ACCEPTANCEOFHARDWAREANDSOFTWAREPROTOTYPE

IMPLEMENTATION

Revision:PA4Authors: StevenDevlin,GeorgeMoore–UniversityofUlster

DELIVERABLE 3.6

05-10-2009

2 (27)

www.myhealth-age.eu

Contents 1 OverviewofDeliverable 3

2 D3.6‐AcceptanceofHardwareandSoftwarePrototypeImplementation‐MobileSafetyAlarm 4

3 D3.6‐AcceptanceofHardwareandSoftwarePrototypeImplementation‐PrescribedHealthcare 7

4 D3.6‐AcceptanceofHardwareandSoftwarePrototypeImplementation‐SocialNetworking 10

5 HandsetEvaluationinNorthernIreland 16 AppendixI NorthernIrelandHandsetEvaluationForm 22AppendixII AcceptanceTestingReportfromNorway 23

DELIVERABLE 3.6

05-10-2009

3 (27)

www.myhealth-age.eu

1 OverviewofDeliverable

Thegoalofthisdeliverableisdetailthecurrentstateofprototypedevelopment.Followingonfrom

the tasks specified inDeliverables3.2–3.5,RequirementsSpecifications,each task is classifiedaseither Developed, Not Developed or Partially Developed (denoted as Yes / No / Partial), anddependingonthestate,ifthishasbeencarriedoutasaFullorPrototypeAcceptablestate,andany

otherrelevantnoteswithreferencetothetask.

The tablesused in thisDeliverable canbe cross‐referencedwithDeliverables3.2–3.5 for furtherdetailsoneachTask.

Followingon fromsubsequent iterationsof theMH@APrototype, thisdeliverablewillbeupdatesaccordingly.

IncludedinthisDeliverableisanoverviewoftheHandsetEvaluationinNorthernIreland.TheUser

Group were asked to use and evaluation 4 handsets. Their evaluation and comments wererecorded;Section5isanoverviewofthis.

AlsoincludedisareportfromAcceptanceTestingcarriedoutinNorway.Someoftheresultsofthishavebeenmergedwith Sections 2 – 4, but as someother relevant findingswere included in this

report,ithasbeenincorporatedinthisDeliverableinAppendixII.

ID Title Implemented Acceptance

T3.2-001 Communication with alarm centre

Yes Requires field testing

T3.2-002 Voice call to the person who initiated mobile alarm


T3.2-003 Mobile safety alarm reliability - Operational

Yes Tested with BTS server. Requires field testing

T3.2-004 Mobile safety alarm initiation (active initiation)

Yes Tested with BTS server. Two minute activation delay and two minute connection delay may be too long. Requires field testing

T3.2-005 Mobile safety alarm initiation (passive initiation)

Yes Tested with BTS server. Two minute activation delay and two minute connection delay may be too long. Requires field testing

T3.2-006 Alarm if electrical appliances are on for a long time (stove, coffee machine, television etc.)

No Not included in this iteration

T3.2-007 House surveillance. Alarm if not all doors and windows are not closed when leaving the home.

No Not included in this iteration

T3.2-008 Activate assault alarm Yes Requires field testing

T3.2-009 Notification that the mobile safety alarm has been initiated properly


T3.2-010 Cancel false alarm Yes Cancels on releasing button making it difficult to determine when the button has been held down long enough to cancel the alarm. Difficult to understand the feedback beeps. May be confusing for end user. Difficult to cancel if not in Safety Alarm application.

T3.2-011 Mobile safety alarm charging Not tested Dependent on use. Requires field testing.

T3.2-012 Wireless connection between smart phone and fall sensor

Yes Occasionally slow to connection, despite Bluetoth pairing having been established.

T3.2-013 Fall sensor range Not tested Limited by range of Bluetooth connection, as anticipated.

T3.2-014 Mobile safety alarm – physical robustness

Not tested Fall sensor has been built to withstand appropriate drops. The mobile phone handset should also hve been drop tested but is the more fragile device.

General System Requirements

Alarm customer end-user requirements

PrototypeImplementa.on‐MobileSafetyAlarmD3.6‐AcceptanceofHardwareandSo>ware

T3.2-015 Navigation precision Yes GPS position when available is passed to the Alarm Center users regardless of alarm status. However it will not be forwarded by SMS/EMail unless there is an alarm. Accuracy of GPS is dependent on location. Requires field testing.

T3.2-016 Navigation reliability Yes GPS position is supported. GSM/3G cell positioning not supported. Accuracy of GPS is dependent on location. Requires field testing

T3.2-017 Navigation availability Yes This functionality already available via BTS Server and PC Client software upon request. Accuracy of GPS is dependent on location. Requires field testing

T3.2-018 Navigation support No Mapping application already available. Not yet integrated with Mobile Alarm Software. Requires field testing

T3.2-019 Configuration of alarm receivers Partial Partial. Native feature of BTS PC client app. Requires Field Testing.

T3.2-020 Integrity Not Tested This is possible via BTS Server. Requires field testing.

T3.2-021 Manual/ instructions Yes Requires field testing

T3.2-022 Warning when alarm customer moves outside area where alarm assistance is provided

Yes Boundaries can be configured for end customers using BTS PC Client software, and alarms may be initiated when the end customer leaves the region defined by the boundary. Red spot and distance shown when outside boundary but this could be confused as there not being a GPS signal.

T3.2-023 Presentation of alarm customer information

Not Tested Access not provided. Requires field testing

T3.2-024 Presentation of GPS information Not Tested Available on Alarm Center PC Client software, but the Arctic Group Mobile Alarm has not yet been integrated into the BTS Handset software. Access not provided. Requires field testing

T3.2-025 Distribute alarm assistance request

Not Tested Access not provided. Requires field testing

T3.2-026 Alarm list No Access not provided. Requires field testing

T3.2-027 Alarm notification Partial BTS PC Client can be configured to give Audio alarms if neccessary. Same with BTS Handset Client (for prefessionals). Access not provided. Requires field testing

T3.2-027 Restrict alarm notification to my actual region

No Access not provided. Requires field testing

T3.2-029 Activate/deactivate availability to provide alarm support.

Partial May be done by request, and may then be done using BTS Client software.Access not provided. Requires field testing

Alarm Centre requirements

Requirements from people providing support to the person in need

T3.2-030 Accept/reject alarm request No Access not provided. Requires field testing

T3.2-031 Help to find person in need Partial Existing BTS Handset software provides maps that can show assistant's position and position of person in need. Not yet integrated with Mobile Alarm software. No voice directions yet. Access not provided. Requires field testing

T3.2-032 Picture of alarm end-user No Access not provided. Requires field testing

T3.2-033 Voice communication with other alarm list members and the alarm centre

No Access not provided. Requires field testing

T3.2-034 Urgancy of safety alarm Yes Alarm type is shown by the BTS PC client software and passed on by SMS/EMail. e.g It says PANIC or SENSOR_MODULE:FALL. Access not provided. Requires field testing


T3.3-001 Integrity No Not a design task. All patients participating in the field trial are assumed to have approved of making their data available for healthcare and welfare staff

T3.3-002 Safety Yes Full

T3.3-003 Access to own medical data Partial Much of the interface has not been translated to other languages. This prevents access to the system. Not accepted.

T3.3-004 Get professional healthcare and welfare advice on activities of importance for personal good health.

Partial Requires field testing

T3.3-005 Medical help based on actual health status

Partial Prototype.This must be accounted for by the healthcare staff. Data entered in the system will be stored and ordered according to actuality, Requires field testing

T3.3-006 Easily understandable information about my health

Partial Prototype: This must be accounted for by the healthcare staff. Requires field testing

T3.2-007 Send requests to healthcare and welfare professionals


T3.2-008 Get notification when it is time to do prescribed healthcare activities


General system requirements

Elderly People end-user requirements

D3.6‐AcceptanceofHardwareandSo5ware Prototype Implementation - Prescribed Healthcare

T3.3-009 Report when prescribed healthcare activities are performed and visualization of series of measurements

Yes Visualisations are largely text based and at times formating is not acceptable. Requires further refinment. Requires field testing

T3.3-010 Check that medication is correct Yes Requires field testing

T3.3-011 Receive feedback from relevant medical personal


T3.3-012 Receive information regarding tests taken at healthcare centres or hospitals


T3.3-013 Measurement and presentation of walking exercise


T3.3-014 Measurement of blood pressure Yes Requires field testing

T3.3-015 Measurement of blood glucose Yes Requires field testing

T3.3-016 INR monitoring to get Waran medication instructions


T3.3-017 2-chanel ecg-monitoring Yes Requires field testing

T3.3-018 Support to quit smoking Partial A link to a lifestyle centre will be provided. Requires field testing

T3.3-019 Support for people with extensive overweight to loose weight

Partial A link to a lifestyle centre will be provided. Requires field testing

T3.3-020 Support to warn when eating to much

Partial A link to a lifestyle centre will be provided, Requires field testing

T3.3-021 Diary Yes Requires field testing

T3.3-022 Schedule with appointments Yes Full

T3.3-023 Phone book with contact information to healthcare and welfare professionals

No No. It would be more appropriate to handle this through the address book of the mobile terminal

T3.3-024 Clean hospitals that don’t make elderly people sick

No Outside the scope of the project

T3.3-025 Transfer instructions to the end-user.


T3.3-026 Receive questions from the end-users


T3.3-027 Receive diagnose measurements


T3.3-028 Receive ECG-diagrams Yes Prototype: An external programme will be needed to view the ECG:s

Healthcare and welfare professionals requirements


T3.4-001 Map Based User Interface for use with Resources

No Now falls outside the scope of the project

T3.4-002 Map Based User Interface for use with People


T3.4-003 Text based user interface for use with Resources

Yes Resources may be tagged. Requires field testing.

T3.4-004 Text based user interface for use with People


T3.4-005 Text based user interface for use with Discussions


T3.4-006 Responsive in Use - Interaction Yes Instant in general use

T3.4-007 Responsive in Use – Results of Interaction

Yes One second in general use

T3.4-008 Secure Data Storage Yes On advice from supplier. Requires field testing

T3.4-009 Secure Data Communication Yes? On advice from supplier. Requires field testing

T3.4-010 Secure Data Management Yes? On advice from supplier. Requires field testing

T3.4-011 Operating System Support Yes Requires field testing

D3.6‐AcceptanceofHardwareandSo5warePrototypeImplementa;on‐SocialNetworking

T3.4-012 Reliable Operational Yes Requires field testing

T3.4-013 Reliable Recovery Yes Requires field testing

T3.4-014 Optimised power consumption N/A Requires field testing

T3.4-015 Wide communication range Yes Requires field testing

T3.4-016 Precise location data No Now falls outside the scope of the project

T3.4-017 Precise navigation data - Walking


T3.4-018 Precise navigation data - Driving


T3.4-019 Data Storage Yes On advice from supplier. Requires field testing

T3.4-020 Data Sharing Yes Inherent in the system

T3.4-021 Data Privacy Yes On advice from supplier. Requires field testing

T3.4-022 Multichannel communication - SMS

Yes Now not the preferred channel. Requires field testing

T3.4-023 Multichannel communication – Web-Based Interface

Yes Provides additional features to the mobile client. Requires field testing

T3.4-024 Multichannel communication – email

Yes Not the preferred channel. Requires field testing

T3.4-025 Multichannel communication – Instant Messaging

Indirectly Core messageing was moved to an IP based mobile client.This provides almost instant messaging without additional per message cost. Requires field testing

T3.4-026 Multichannel communication – Voice

Partial As a mobile phone but not explicitly supported by the social networking system. Requires field testing

T3.4-027 User should be able to share their location with other users.

Yes Can be shared by messaging and resources may be tagged. Requires field testing.











T3.4-033 User Management of Location Access - Who has access

No Location is not actively shared by the system. It is shared as the user desires through message content and tagging. Requires field testing

T3.4-034 User Management of Location Access -Mode of access


T3.4-035 User Management of Location Access - Amend access


T3.4-036 User Management of Location Access - Amend mode of acess


T3.4-037 Show Map Based Location of People


T3.4-038 Show Map Based Location of Resources


T3.4-039 Show Text Based Location of People


T3.4-040 Show Text Based Location of Resources


T3.4-041 Allow user to manage their profile data - Viewing


T3.4-042 Allow user to manage their profile data - Editing

No Profiles are created by the administrator. Requires field testing

T3.4-043 Allow users to Include who can contact them

Yes User controls which groups they join. Requires field testing

T3.4-044 Allow users to Exclude who can contact them

Yes User controls which groups they join. Requires field testing

T3.4-045 Allow users to control when they can be contacted by Individuals

No Only by exiting the application. Requires field testing

T3.4-046 Allow users to control when they can be contacted by Groups

No Only by exiting the application. Requires field testing

T3.4-047 Create discussions within user groups

Yes Users can create dicussions. Requires field testing

T3.4-048 Participate in discussions within user groups

Yes Can belong to multiple groups and discussions. Requires field testing

T3.4-049 Create discussions between user groups

Yes Users can create dicussions. Requires field testing

T3.4-050 Participate in discussions between user groups

Yes Can belong to multiple groups and discussions. Requires field testing

T3.4-051 Provide Context-Aware services - Location


T3.4-052 Provide Context-Aware services - Privacy


T3.4-053 Provide Context-Aware services - Contact


T3.4-054 Pervasive Service Delivery - Location

Yes Providing network coverage is available. Requires field testing

T3.4-055 Pervasive Service Delivery - Time

Yes Providing network coverage is available. Requires field testing

T3.4-056 Stable in operation Yes Requires field testing

T3.4-057 Upgradeable architecture Yes Exists as a web application

T3.4-058 Support for activities of daily living


T3.4-059 Support a feeling of safety Not Tested Improved social connection may meet this need. Requires field testing.

T3.4-060 Support independent living Not Tested Improved social connection may meet this need. Requires field testing.

T3.4-061 Support for social and recreational activities

Not Tested Improved social connection may meet this need. Requires field testing.

T3.4-062 Mobile platform Yes Mobile IP based client

T3.4-063 Support feeling of social inclusion

Not Tested Improved social connection may meet this need. Requires field testing.

T3.4-064 Include weather forecast No Now falls outside the scope of the project

T3.4-065 Home / Not Home No Now falls outside the scope of the project

5 Handset Evaluation in Northern Ireland

5.1 Introduction

Following confirmation of Ethical approval on the 2nd March 2009, a meeting with the User Group was organised for the 25th March, to focus on evaluation of the potential mobile handsets to be used for the evaluation phase.

Currently the Sony Ericsson XPERIA X1 is being used as the project’s handset of choice, pending user evaluation. The findings documented here should be used to inform future handset selection decisions.

The partners in attendance who helped facilitate the session where; Denise McBride (Newry & Mourne Senior Citizens Consortium), Patricia Toner (Southern Trust), Suzanne Martin (UUJ, WP2) and Steven Devlin (UUJ, WP3) attended the User Group Meeting. This document details the findings from this meeting.

5.2 Handsets, Evaluation and Results

In Northern Ireland, we were able to provide four handsets for evaluation. The Sony Ericsson XPERIA X1, HTC Touch Pro and Samsung Omnia are all Windows Mobile 6.1 Professional based handsets as per the requirements specified for the prototype. But we also decided to include the Apple iPhone in this evaluation as its innovative touchscreen interface is regarded as one of the easiest to use by many technical reviews.

We asked each member of the user group to engage with each of the handsets separately. On the Windows Mobile handsets, text could be viewed and entered using the ‘Notes’ application, and on Apple’s own ‘Notes’ application on the iPhone. While engaging with each handset, the user group were also asked to fill in a questionnaire on each handset, which can be seen in Appendix 1.

While the group were using each of the devices, the project members in attendance each sat with one or two of the group to record any other comments they had, assist in using the handsets and filling out the questionnaires where required. Table 1 shows the combined results from the questionnaires for all handsets from the entire group.

Very Easy Fairly Easy DifficultVery

Difficult

Sony Ericsson Xperia X1 3 3HTC Touch Pro 5 1Apple iPhone 4 1 1

Samsung Omnia 4 1 1


Difficult

Sony Ericsson Xperia X1 1 2 2 1HTC Touch Pro 3 2 1Apple iPhone 3 1 1 1

Samsung Omnia 2 1 3

Too SmallA Little Small

OKA Little Big

Too Big

Sony Ericsson Xperia X1 3 1 2HTC Touch Pro 2 4Apple iPhone 3 3

Samsung Omnia 1 5

Sony Ericsson Xperia X1 2 3 1HTC Touch Pro 3 2 1Apple iPhone 1 2 1 2

Samsung Omnia 3 1 2


Difficult

Sony Ericsson Xperia X1 2 3 1HTC Touch Pro 3 1 2Apple iPhone 6

Samsung Omnia 2 4


OKA Little Big

Too Big

Sony Ericsson Xperia X1 2 2 2HTC Touch Pro 1 1 4Apple iPhone 2 4

Samsung Omnia 3 3Samsung Omnia (Alt. Text Entry) 1 5

Too LightA Little Light

OKA Little Heavy

Too Heavy

Sony Ericsson Xperia X1 1 4 1HTC Touch Pro 2 4Apple iPhone 2 3 1

Samsung Omnia 6


OKA Little Big

Too Big

Sony Ericsson Xperia X1 5 1HTC Touch Pro 6Apple iPhone 2 4

Samsung Omnia 6

Lovely NiceNo So Good

Ugly

Sony Ericsson Xperia X1 5 1HTC Touch Pro 6Apple iPhone 1 5

Samsung Omnia 6

Definitely ProbablyPossibly Not

No

Sony Ericsson Xperia X1 1 2 3HTC Touch Pro 3 2 1Apple iPhone 4 1 1

Samsung Omnia 2 2 1 1

7. What do you think of the weight of the phone?

8. What do you think of the size of the phone?

9. What do you think of the appearance of the phone?

10. Would you use this phone?

4. How confident would you be that you could press the intended

5. What do you think of the force required to press the keyboard buttons?

6. What do you think of the size of the keyboard buttons?

Table 1 ‐ MH@A Phone Handset Evaluation Questionnaire Overview

CertainFairly Certain

UnsureVery

Unsure

1. How easy is it to see what is shown on the screen?

2. How easy is it to find each of the main (control) buttons?

3. What do you think of the size of the main (control) buttons?

main (control) button?

Following group evaluation of each handset, members were each asked to individually rank the phones in preference, with 1 being most preferable to 4 the least, to use during the field trail. The results of this are shown in Table 2.

Preference (lowest number)

1 2 3 4 5 6Sony Ericsson Xperia X1 4 3.5 4 3.5 3.5 3 21.5HTC Touch Pro 3 3.5 3 3.5 3.5 4 20.5Apple iPhone 1 1 2 1 2 2 9Samsung Omnia 2 2 1 2 1 1 9

Table 2 ‐ Users Ranking of Each Handset

Participant

Han

dset

Most of the Group felt that the Sony Ericsson XPERIA X1 and HTC Touch Pro were very similar handsets, and they did not differentiate much between them. There was a general consensus that both were too thick and heavy. There are more detailed comments later on in this document.

The Samsung Omnia was the most preferred handset for a number of reasons. It was the lightest phone evaluated. Although it has quite a large footprint, it is very slim and allowed for the largest Windows Mobile based display evaluated. The Omnia was also much liked due to the array of options available for text entry.

In Question 6 of Table 1, there are 2 entries for the Samsung Omnia. This has been shown to highlight the vast difference in ease of use between the standard portrait QWERTY keyboard and the various other keyboards available. Some of the various text entry methods can be seen in Figure 1. Users who already used mobile phones, and had used SMS text messaging mostly preferred using the standard numeric keypad layout for text entry. Nearly all found the standard portrait QWERTY keyboard too small for accurate text entry, both those who did not already use mobile phones and SMS messaging liked either the QWERTY keyboard in landscape mode, or portrait mode with 2 letters per button (which requires a double tap for the 2nd letter in the button).

F

Teop

Samsun

Figure 1:

ext Entry ptions on ng Omnia

5.3

5.3.1

•

•

•

5.3.2

•

•

•

Other Com

Sony Ericsso

A black XPERusers found of the XPERI

Some users the screen is

The higher rsome on‐scr

Apple iPhon

On‐screen teapplication.

Although thgroup, two touchscreen

There was Some users could get us

mments Mad

on XPERIA X1

RIA was usedthe keys verIA.

found the tos slid open, a

resolution ofreen elemen

ne –

ext in ‘Notes The text siz

e touchscreeusers com

n.

mixed feelinliked this ve

sed to it.

de by User

1 –

d in the evalry hard to se

op row of keand these ke

f the screen ts hard to re

s’ applicationze could not

en was genemmented on

ngs about hery much, ot

Group

uation. Theee. This is the

eys on the keeys very hard

compared wead.

n was very smbe changed.

erally found tn how stylu

ow the iPhothers found

keyboard ise same with

eyboard too d to press bec

with the sim

mall compar This can be

to be very acuses could

one automait a bit conf

s sliver with sboth the silv

close the topcause of this

ilarly sized H

ed with Wine seen in Figu

ccurate and not be use

atically correfusing, but th

silver buttonver and blac

p of the devis.

HTC Touch P

ndows Mobileure 2.

easy to use ed with the

ected mistyphought with

TextNotes

on

ns. Some k models

ice when

ro led to

e ‘Notes’

with the e iPhone

ped text. practice

Figure 2:

t size on the s application n the iPhone

5.3.3

•

5.3.4

•

5.4

In the otout, thethem to

• • •

These a

Samsung Om

As mentionetype accuratopens / closcan lead to i

Other Comm

The large texscreen text fThis comme

Other Regi

ther regions e user group use. In gen

Large Screen

Large Keybo

Large Button

are similar co

mnia

ed previouslytely, and othses the keyboinadvertently

ments –

xt option onfor most useent should be

ons

involved witps were askeeral, they wo

n

oard

ns

omments to t

y, the standaher keyboardoard is alwayy closing the

the Windowers. An exame considered

th the projeced about whould like –

those made

ard portrait Qds were mucys in the mide keyboard w

ws Mobile ‘Nmple of this c during the d

ct, although hat features

by the North

QWERTY keych more suitaddle of the bowhile typing.

otes’ applicaan be seen odevelopmen

a study withwould mak

hern Ireland

yboard was table. The soottom touch

ation is the idon the HTC Tt of the hand

h physical deve the hands

User Group

too small andoft touch buth bar of optio

deal size of oTouch Pro in dset prototy

vices was noset most suit

.

TNo

d hard to tton that ons. This

on‐Figure 3. pe.

ot carried table for

Figure 3

Text size on thtes applicatioon Window

Mobile handset

3:

he on ws 6 ts

Appenddix 1 – Evaluuation Queestionnaire

DELIVERABLE 3.6

05-10-2009

23 (27)

www.myhealth-age.eu

APPENDIXII‐MyHealth@AgeUserAcceptanceTestinNorwayThesmartphoneswereavailablefortheprojectmembersinthebeginningofJune2009.Theprojectmembers tried out the smart phone and the applications that were available (safety alarm andprescribedhealthcare)foraweek.TheseniorswereinvitedtoameetingatNCTonFriday,20thJune.Thesmartphoneswerehandedouttotheseniorsandprojectmembersgaveapresentationofthebasicsfunctionsofthephone(SIM,batterycharging,turnthephoneon/off,makephonecallsandmake SMS) and of the MyHealth@Age applications that were accessible. The seniors tried toactivate the different functions and projectmemberswere helping and answering questions. Themanualswere handed out and the seniors got a list of activities that they should try to performbeforethenextmeeting.Theyalsogotalistofcriteriatoevaluatethesmartphone.TheseniorsmetatNCTon29thJunetopresenttheirevaluation.Duringthetestperiodtheseniorshadnotbeenabletoaccesstheprescribedhealthcarewebpage.Theevaluationofthewebpageisbasedonthefirstmeeting(20thJune)andtheprojectmember’suseoftheprescribedhealthcare.Theseniors:TheMyHealth@Ageapplications:1) Thealarmwasfunctioning2) TheMyHealth@Ageapplicationsiseasytouse3) Aneedofashortermanual(withbasicfunctions)Thesmartphone:1) Thesymbolsontheedgearehardtonotice2) Theperiodbeforethelightonthescreenfadesawayistoshort3) Thepenistosmall(thin)4) Thehardkeypadisnotnecessary5) Thetelephonemenusaretoodifficulttounderstand6) Thewaytomovebetweenprogramsisdifficulttounderstand7) BatterytimeistoshortTheprojectmembers:TheMyHealth@Ageapplications:1) Unabletousedecimals(comma)whenfillingindata(glucosesetc)2) WaranmustbealteredtoINRorMarevaninNorwayThesmartphone:1) Badsoundquality/lowvolumeifyoudon’tholdthephoneintherightposition.2) Thetelephoneisheavy3) Longtimefromit’sputonbeforeit’sready4) Thekeypadsaresmall5) DifficulttochangebatteryandSIM6) Thetelephoneissometimeslockedanditisimpossibletoturnoffandonwithouthavingto

removetheSIM.

DELIVERABLE 3.6

05-10-2009

24 (27)

www.myhealth-age.eu

MyHealth@AgeThese are the result from the user acceptance test. The seniors were not able to activate theprescribedhealthcareduringthetestperiod.

1.1.1 Telephone

ID Title Accepted Comment

Usersshouldbeabletomake phone calls withthedevice.

Yes

Usersshouldbeabletosend and receive SMSwiththedevice.

Yes

The users should beable to navigate to themain menus after 5trials

The users should beabletogetthedeviceinphone mode bypressingonebutton.

Yes

Theusershouldbeableto insert new phonenumber in Contact andbeablefindnumbersinContactafter5trials‐

Yes

The users should beable to start theMyHealth@Ageapplicationsbypressingnot more than twobuttons.

Yes

The users should beable to access theMyHealth@Age menuwith two clicks fromanywhere on thedevice.

Yes Users can start theapplicationsbyclickingthe“Xpanel”button,and then choosing theMyHealth@Agepanel.

Thedeviceshouldwarnthe user if the batterylevelislow.

Yes The user is warned by soundandtext

DELIVERABLE 3.6

05-10-2009

25 (27)

www.myhealth-age.eu

Theusershouldbeableto configure thiswarning, to be a textmessageorasound.

1.1.2 Mobile safety alarm

SenderofalarmID Title Accepted Comment Theuser should be able to start

thealarmfromthedevice.Yes

Theuser should be able to startthealarmfromthefallsensor.

Theusershouldbeabletocancelan alarm within 1 minute ofstartingit.

Yes

When the alarm is activated thedevice should make sounds andvibrate. This should also happenif the sound on the device isturnedoff.

Yes

Theusershouldbenotifiedwhenthealarmisconfirmed.

Yes

The device should display statusfor fall sensor, battery, fallsensor battery, alarm centreconnectionGPS.

Yes

The device should be able toreceive signals from the fallsensorifit’swithin10meters.

When the alarm menu isactivated, the telephone shouldbeon(andnot“gotosleep”)thewholetime.

ReceiverofalarmFallsensor

DELIVERABLE 3.6

05-10-2009

26 (27)

www.myhealth-age.eu

1.1.3 Prescribed health care

PrescribedhealthcareID Title Accepted Comment Theuser should be able to view

thereportedvalues.Yes

Theusershouldbealertedwhentheygetmessagesfromahealthcare worker in the prescribedhealthcaresystem.

Theusershouldbenotifiedwhenit is time to do PrescribedHealthcareactivities.

Theusershouldbeabletonotifythat he/she has performed thePrescribedHealthcareactivity.

Yes

Theusersshouldbeabletowriteapatientdiary.

Yes

Thedeviceshouldneverhavetouse more than 10 seconds toloadanewpage.

The web pages used inPrescribed Healthcare should beavailable at least 90 % of thetime.

No The users have not been able to access theprescribedhealthcareduringthetestperiod(9days)

The device should place thecursor in the text fieldautomatically when showing afieldthatneedstobefilledin.

No

PrescribedhealthcarecommunicationwiththeGPID Title Accepted Comment The user should be able to

reportuseofmedication.Yes

TheusershouldbeabletosendandreceivemessagestotheGP

Receivenottested

The user should be able toreportbloodpressure.

Yes

The user should be able toreportbloodglucose.

Yes

The user should be able toreportINRvalues.

Yes

The user should be able toreportECG.

Yes

The user should be able to fill No

DELIVERABLE 3.6

05-10-2009

27 (27)

www.myhealth-age.eu

invalueswithcomma/dot(e.g.102,3)

PrescribedhealthcarecommunicationwithnursesetcID Title Accepted Comment The user should be able to

send and receive messages tonursesetc.

Receivenottested

The user should be able toreportstepcountervalues.

Yes

The user should be able toreportpulsemetervalues.

Yes

The user should be able toreportweight.

Yes

1.1.4 Social networking

ID Title Accepted Comment Users should be able to find

their GPS position using thedevice.

Theusersshouldbeabletoseethepositionofotherusersonamap.

Theusersshouldbeabletogetthe location (address) of otherusersinamessage.

The user should be able todefine groups forcommunication (culture,walking,discussionetc)

The users should be able tosend SMS messages topredefinedgroups.

Theusersshouldbeabletosettheirstatusasnotavailable.

MH@A - Deliverable 3.6 inc Appendix II/file/D3 6 - Acceptance of Hardware... · T3.2-026 Alarm list...

Documents

Transcript of MH@A - Deliverable 3.6 inc Appendix II/file/D3 6 - Acceptance of Hardware... · T3.2-026 Alarm list...