CORE Group 2011 SixBlue Data

450 views

Published on

presented 11 May 2011

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
450
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

CORE Group 2011 SixBlue Data

  1. 1. How Do Community Workers Feel about mHealth? CORE Group Spring Session 2011
  2. 2. Mali Bolivia YemenEl Salvador Armenia SudanGuatemala Haiti UgandaEgypt Mozambique VietnamJordan Mali PhilippinesBangladesh Pakistan MyanmarMalawi Tajikistan GuineaAfghanistan West Bank
  3. 3. Awaiting Data Input – Haiti (Save the Children USA)
  4. 4. Survey Coordinator – Bolivia (Save the Children USA)
  5. 5. Microfinance Registries – Myanmar (Save UK)
  6. 6. Laptop NetbookPDA The Tools Cell Phones
  7. 7. Because it is everywhere…
  8. 8. Start with the end-user in mind.How can mobile technology help them do what they’re already doing?- Adam Slote Chief Health Advisor, USAID Global Health, GH Mini U, October 2010
  9. 9. The Users
  10. 10. “People dont want to have apps which solve what YOU think are problemsThey want apps which solves what THEY think is a problem.”- Christopher Kusek (@CXI), retweeted by Ed Jezierski (@edjez) 3 May 2011
  11. 11. The UsersPhoto: CommCare – Futures Group, 18 Dec 2009
  12. 12. Each technology deployment has unique characteristics and needs.
  13. 13. The solution must be carefully thought out.It must be inclusive of all stakeholders. • Donor • Program • M&E • IT • Field Staff • CHW • Beneficiary
  14. 14. Fight the urge to push thesolution without input of allstakeholders.
  15. 15. The solution must satisfy the program need.But, it must work in the hands of the User.
  16. 16. It’s not about technology… it’s about People.
  17. 17. Afghanistan March 2011
  18. 18. Technology is becoming easy...Problems can be solved - they are technical!
  19. 19. The Challenge is:Point of interaction between user and beneficiary
  20. 20. How should I begin?
  21. 21. Technology Solution CriteriaFunctionality - What can it do?Usability - Can it be used?Scalability – Can it be used on a wider scale?
  22. 22. Functionality1st – clearly understand your “What”•Program and intervention needs.•M&E indicators(Results Framework)
  23. 23. FunctionalityThe “What” always precedes the “How”(The “How” is the technology “Solution”)
  24. 24. Functionality Technology serves your “What”… …not the other way around.Resist forcing your “What” to fit the “How”.
  25. 25. UsabilityTechnology always works in the lab andduring training……it can quickly become irrelevant inthe context of field conditions.
  26. 26. “What Device?”
  27. 27. Usability“If it doesn’t work in the field……then it doesn’t work”.
  28. 28. ScalabilitySmall pilots are often successful…but they seldom scale up to widerimplementations
  29. 29. Scalability So….Your solution worked!Can your solution expand to additionallocations?Hint: Consider “Cloud”-based Softwareas a Service” (SaaS) solutions.
  30. 30. Additional Considerations Before You BeginConnectivity: not available  availablePower availability: low (car battery/solar)  highData transfer method: USB  SMS  GPRS  NetworkData quality: not important  importantSurvey structure: simple  complex (branching)Data Privacy and Security: low  high
  31. 31. mHealth and the CHWGoogle Groups: ICT4CHWict4chw@go​oglegroups​.com Moderated by Dr. Neal Lesh of D-Tree
  32. 32. SixBlue DataDavid Isaak – Mobile Technology http://www.sixbluedata.com http://www.sixbluedata.com disaak@sixbluedata.com

×