Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Data Collection Requirements for Mobile Connect...

Jos
October 30, 2016

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

Jos

October 30, 2016
Tweet

More Decks by Jos

Other Decks in Research

Transcript

  1. Data Collection requirements for Mobile Connected Health An End User

    Development approach Jose Juan Dominguez Veiga – [email protected] @josmasflores
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. Jeff Patton, the Spice Girls and Johnny Rotten Mobile!2016 Oct.

    2016 21 http://jpattonassociates.com/dont_know_what_i_want/
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. 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
  22. It is not as easy as it may seem… •

    Gets complicated easily Mobile!2016 Oct. 2016 46
  23. It is not as easy as it may seem… II

    • Asynchronous calls Mobile!2016 Oct. 2016 48
  24. It is not as easy as it may seem… III

    • UI style of programming Mobile!2016 Oct. 2016 50
  25. Lack of support for most Background Processes • Only the

    Texting component “listens” when the app is not running. Mobile!2016 Oct. 2016 53
  26. 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
  27. 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
  28. Current work • A Pedometer working as a background process

    • Diary functionality with external, configurable forms (ESM) Mobile!2016 Oct. 2016 58
  29. Future work • Integration with a Context aware framework •

    A BLE framework (not the current available extension) Mobile!2016 Oct. 2016 60
  30. 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
  31. Questions? I am interviewing more researchers! [email protected] @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