Data Collection Requirements for Mobile Connected Health: an End User Development approach

A number of interview findings about creating mhealth data collection apps through an end-user development approach with tools such as MIT App Inventor. Presentation at Mobile! workshop, SPLASH16 in Amsterdam

Transcript

1. Data Collection requirements for Mobile Connected Health An End User Development approach Jose Juan Dominguez Veiga – jose.dominguez@insight-centre.org @josmasflores
2. José Dominguez jose.dominguez@insight-centre.org @josmasflores Mobile!2016 Oct. 2016 2
3. Agenda • Closed Loop Digital Therapeutics • Interviews • Summary of Main Findings • End User Development • App Inventor Main Limitations and some Potential Solutions • Current (and Future) Work Mobile!2016 Oct. 2016 3
4. DIGITAL THERAPEUTICS
5. Mobile!2016 Oct. 2016 5 According to Health Standards
6. Mobile!2016 Oct. 2016 6 Picture credits: http://my.medixprt.com/assets/img/ite m/brief-3.png http://www.kingsfund.org.uk/sites/file s/kf/media/8-technologies-1- smartphone.png http://www.kingsfund.org.uk/sites/file s/kf/media/8-technologies-4- therapeutics.png
7. Typical Digital Therapeutics Architecture 2: Wearable data collected 1: Set Intervention parameters 3: Not enough walk detected 4: Intervention range exceeded Operational API Notifications Data Service SERVICES Mobile!2016 Oct. 2016 7
8. DT Architecture: meet Bob 2: Wearable data collected 1: Set Intervention parameters 3: Not enough walk detected 4: Intervention range exceeded Operational API Notifications Data Service SERVICES Mobile!2016 Oct. 2016 8
9. DT Architecture: meet Mary 2: Wearable data collected 1: Set Intervention parameters 3: Not enough walk detected 4: Intervention range exceeded Operational API Notifications Data Service SERVICES Mobile!2016 Oct. 2016 9
10. DT Architecture: Intervention parameters 2: Wearable data collected 1: Set Intervention parameters 3: Not enough walk detected 4: Intervention range exceeded Operational API Notifications Data Service SERVICES Mobile!2016 Oct. 2016 10
11. DT Architecture: Data collection 2: Wearable data collected 1: Set Intervention parameters 3: Not enough walk detected 4: Intervention range exceeded Operational API Notifications Data Service SERVICES Mobile!2016 Oct. 2016 11
12. DT Architecture: inner subject loop 2: Wearable data collected 1: Set Intervention parameters 3: Not enough walk detected 4: Intervention range exceeded Operational API Notifications Data Service SERVICES Mobile!2016 Oct. 2016 12
13. DT Architecture: external loop 2: Wearable data collected 1: Set Intervention parameters 3: Not enough walk detected 4: Intervention range exceeded Operational API Notifications Data Service SERVICES Mobile!2016 Oct. 2016 13
14. WHO BUILDS AND PAYS FOR ALL THIS?
15. Interviews 12 Researchers, 4 countries, 4 different institutions: • Mechanical and Electronic Engineering • Sports and Exercise Science • Neuroscience • Physiotherapy • Psychology • Health Promotion and Education Mobile!2016 Oct. 2016 15
16. Interviews 12 Researchers, 4 countries, 4 different institutions: • Mechanical and Electronic Engineering • Sports and Exercise Science • Neuroscience • Physiotherapy • Psychology • Health Promotion and Education Mobile!2016 Oct. 2016 16 http://vignette4.wikia.nocookie.net/halo/images/7/71/Halo_3_Logo.png
17. Interviews II Mobile!2016 Oct. 2016 17 https://static01.nyt.com/images/2015/03/26/business/MACHINE/MACHINE-blog427.jpg
18. Interviews III Mobile!2016 Oct. 2016 18 https://obolobo.files.wordpress.com/2014/03/i-beg.jpg
19. Interviews IV Mobile!2016 Oct. 2016 19 http://rlv.zcache.com/will_code_for_food_mug-r99e03ff348fe4a7a822a3397d5a40543_x7jsd_8byvr_512.jpg
20. Interviews V Mobile!2016 Oct. 2016 20 http://verysmartbrothas.com/images/planb.png
21. Jeff Patton, the Spice Girls and Johnny Rotten Mobile!2016 Oct. 2016 21 http://jpattonassociates.com/dont_know_what_i_want/
22. Mobile!2016 Oct. 2016 22
23. Mobile!2016 Oct. 2016 23
24. Mobile!2016 Oct. 2016 24
25. Do it yourself… if you can?
26. End User Development A set of methods, techniques and tools that allow users of software systems, who are acting as non-professional software developers, at some point to create, modify, or extend a software artifact. Lieberman, H, Paterno, F, Klann, M, and Wulf, V. (2006). End-user development: An emerging paradigm. Mobile!2016 Oct. 2016 26
27. End User Development A set of methods, techniques and tools that allow users of software systems, who are acting as non-professional software developers, at some point to create, modify, or extend a software artifact. Lieberman, H, Paterno, F, Klann, M, and Wulf, V. (2006). End-user development: An emerging paradigm. Mobile!2016 Oct. 2016 27
28. End User Development: Examples Mobile!2016 Oct. 2016 28 Image credits: http://sine.ni.com/cms/images/casestudies/a14_02.jpg http://brainimaging.waisman.wisc.edu/~tjohnstone/Image9.gif https://upload.wikimedia.org/wikipedia/commons/thumb/5/50/OpenOffice.org_Calc.png/400px-OpenOffice.org_Calc.png
29. End User Development: MIT App Inventor Mobile!2016 Oct. 2016 29
30. End User Development: MIT App Inventor II Mobile!2016 Oct. 2016 30
31. MAIN FINDINGS: REQUIREMENTS
32. Interview findings • 11 out of 12 want to use it – At least for prototyping Mobile!2016 Oct. 2016 32 http://img.pixfans.com/2014/12/lan_party.jpg
33. Interview findings II • Different levels of abstraction in the data Mobile!2016 Oct. 2016 33
34. Interview findings II • Different levels of abstraction in the data Mobile!2016 Oct. 2016 34
35. Interview findings III • Social feedback loop Mobile!2016 Oct. 2016 35
36. 2: Wearable data collected 1: Set Intervention parameters 3: Not enough walk detected 4: Intervention range exceeded Operational API Notifications Data Service SERVICES DT Architecture: external loop Mobile!2016 Oct. 2016 36
37. Interview findings III • Social feedback loop Mobile!2016 Oct. 2016 37
38. Interview findings IV • Security and Privacy concerns are only as important as Ethical concerns Mobile!2016 Oct. 2016 38 https://cfa-wpengine.netdna-ssl.com/investor/files/2014/12/Staying-off-the-slippery-slope-ethics-advice-for-those-new-to-the-industry.jpg
39. Mobile!2016 Oct. 2016 39 https://speakerdeck.com/josmas/a-homespun-decentralised-diy-data-science-research-pipeline-for-the-internet-of-star-your-star-things
40. Mobile!2016 Oct. 2016 40 https://speakerdeck.com/josmas/a-homespun-decentralised-diy-data-science-research-pipeline-for-the-internet-of-star-your-star-things
41. Google APIs Terms and Conditions. Section 5: Content b. Submission of Content Some of our APIS allow the submission of content. Google does not acquire any ownership of any intellectual property rights in the content that you submit to our APIs through your API Client, except as expressly provided in the Terms. For the sole purpose of enabling Google to provide, secure, and improve the APIs (and the related ser- vice(s)) and only in accordance with the applicable Google privacy policies, you give Google a perpetual, irrevocable, worldwide, sublicensable, royalty- free, and non-exclusive license to Use content submitted, posted, or displayed to or from the APIs through your API Client. ”Use” means use, host, store, modify, communicate, and publish. Before you submit content to our APIs through your API Client, you will ensure that you have the necessary rights (including the necessary rights from your end users) to grant us the license. Mobile!2016 Oct. 2016 41
42. Google APIs Terms and Conditions. Section 5: Content b. Submission of Content Some of our APIS allow the submission of content. Google does not acquire any ownership of any intellectual property rights in the content that you submit to our APIs through your API Client, except as expressly provided in the Terms. For the sole purpose of enabling Google to provide, secure, and improve the APIs (and the related service(s)) and only in accordance with the applicable Google privacy policies, you give Google a perpetual, irrevocable, worldwide, sublicensable, royalty-free, and non-exclusive license to Use content submitted, posted, or displayed to or from the APIs through your API Client. ”Use” means use, host, store, modify, communicate, and publish. Before you submit content to our APIs through your API Client, you will ensure that you have the necessary rights (including the necessary rights from your end users) to grant us the license. Mobile!2016 Oct. 2016 42
43. Google APIs Terms and Conditions. Section 5: Content b. Submission of Content Some of our APIS allow the submission of content. Google does not acquire any ownership of any intellectual property rights in the content that you submit to our APIs through your API Client, except as expressly provided in the Terms. For the sole purpose of enabling Google to provide, secure, and improve the APIs (and the related service(s)) and only in accordance with the applicable Google privacy policies, you give Google a perpetual, irrevocable, worldwide, sublicensable, royalty- free, and non-exclusive license to Use content submitted, posted, or displayed to or from the APIs through your API Client. ”Use” means use, host, store, modify, communicate, and publish. Before you submit content to our APIs through your API Client, you will ensure that you have the necessary rights (including the necessary rights from your end users) to grant us the license. Mobile!2016 Oct. 2016 43
44. Mobile!2016 Oct. 2016 44 https://speakerdeck.com/josmas/a-homespun-decentralised-diy-data-science-research-pipeline-for-the-internet-of-star-your-star-things
45. APP INVENTOR MAIN LIMITATIONS
46. It is not as easy as it may seem… • Gets complicated easily Mobile!2016 Oct. 2016 46
47. Mobile!2016 Oct. 2016 47
48. It is not as easy as it may seem… II • Asynchronous calls Mobile!2016 Oct. 2016 48
49. Mobile!2016 Oct. 2016 49
50. It is not as easy as it may seem… III • UI style of programming Mobile!2016 Oct. 2016 50
51. Mobile!2016 Oct. 2016 51
52. Mobile!2016 Oct. 2016 52
53. Lack of support for most Background Processes • Only the Texting component “listens” when the app is not running. Mobile!2016 Oct. 2016 53
54. Limited Export to Java • There is only experimental support for exporting to Java • Other types of Textual coding would be helpful Mobile!2016 Oct. 2016 54
55. Limited Layout and Styling functionality • It is difficult to create an App that looks OK, straight out the MIT server Mobile!2016 Oct. 2016 55
56. CURRENT (AND FUTURE) WORK
57. Current work • A Pedometer working as a background process Mobile!2016 Oct. 2016 57
58. Current work • A Pedometer working as a background process • Diary functionality with external, configurable forms (ESM) Mobile!2016 Oct. 2016 58
59. Future work • Integration with a Context aware framework Mobile!2016 Oct. 2016 59
60. Future work • Integration with a Context aware framework • A BLE framework (not the current available extension) Mobile!2016 Oct. 2016 60
61. Future work • Integration with a Context aware framework • A BLE framework (not the current available extension) • On-device ML with WEKA Mobile!2016 Oct. 2016 61
62. Questions? I am interviewing more researchers! jose.dominguez@insight-centre.org @josmasflores 62 2: Wearable data collected 1: Set Intervention parameters 3: Not enough walk detected 4: Intervention range exceeded Operational API Notifications Data Service SERVICES Mobile!2016 Oct. 2016