presented 11 May 2011

1. How Do Community Workers Feel about mHealth?
CORE Group Spring Session 2011

2. Mali Bolivia Yemen
El Salvador Armenia Sudan
Guatemala Haiti Uganda
Egypt Mozambique Vietnam
Jordan Mali Philippines
Bangladesh Pakistan Myanmar
Malawi Tajikistan Guinea
Afghanistan West Bank

3. Awaiting Data Input – Haiti (Save the Children USA)

4. Survey Coordinator – Bolivia (Save the Children USA)

5. Microfinance Registries – Myanmar (Save UK)

6. Laptop Netbook
PDA The Tools
Cell Phones

7. Because it is everywhere…

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. The Users

10. “People don't want to have apps which
solve what YOU think are problems
They want apps which solves what THEY
think is a problem.”
- Christopher Kusek (@CXI), retweeted by Ed Jezierski
(@edjez) 3 May 2011

11. The Users
Photo: CommCare – Futures Group, 18 Dec 2009

12. Each technology deployment has
unique characteristics and needs.

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. Fight the urge to push the
solution without input of all
stakeholders.

15. The solution must satisfy the program need.
But, it must work in the hands of the User.

16. It’s not about technology…
it’s about People.

17. Afghanistan March 2011

18. Technology is becoming easy...
Problems can be solved - they are technical!

19. The Challenge is:
Point of interaction between user and
beneficiary

20. How should I begin?

21. Technology Solution Criteria
Functionality - What can it do?
Usability - Can it be used?
Scalability – Can it be used on a wider scale?

22. Functionality
1st – clearly understand your “What”
•Program and intervention needs.
•M&E indicators(Results Framework)

23. Functionality
The “What” always precedes the “How”
(The “How” is the technology “Solution”)

24. Functionality
Technology serves your “What”…
…not the other way around.
Resist forcing your “What” to fit the “How”.

25. Usability
Technology always works in the lab and
during training…
…it can quickly become irrelevant in
the context of field conditions.

26. “What Device?”

27. Usability
“If it doesn’t work in the field…
…then it doesn’t work”.

28. Scalability
Small pilots are often successful…
but they seldom scale up to wider
implementations

29. Scalability
So….Your solution worked!
Can your solution expand to additional
locations?
Hint: Consider “Cloud”-based Software
as a Service” (SaaS) solutions.

30. Additional Considerations Before You Begin
Connectivity: not available  available
Power availability: low (car battery/solar)  high
Data transfer method: USB  SMS  GPRS  Network
Data quality: not important  important
Survey structure: simple  complex (branching)
Data Privacy and Security: low  high

31. mHealth and the CHW
Google Groups: ICT4CHW
ict4chw@go​oglegroups​.com
Moderated by Dr. Neal Lesh of D-Tree

32. SixBlue Data
David Isaak – Mobile Technology
http://www.sixbluedata.com
http://www.sixbluedata.com
disaak@sixbluedata.com