mHealth at the Community Level: Recommendations for Roll-out_Isaak_5.11.11
Upcoming SlideShare
Loading in...5
×
 

mHealth at the Community Level: Recommendations for Roll-out_Isaak_5.11.11

on

  • 375 views

 

Statistics

Views

Total Views
375
Views on SlideShare
375
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

mHealth at the Community Level: Recommendations for Roll-out_Isaak_5.11.11 mHealth at the Community Level: Recommendations for Roll-out_Isaak_5.11.11 Presentation Transcript

  • How Do Community Workers Feel about mHealth?CORE Group Spring Session 2011
  • Awaiting Data Input – Haiti (Save the Children USA)
    View slide
  • Survey Coordinator – Bolivia (Save the Children USA)
    View slide
  • Microfinance Registries – Myanmar (Save UK)
  • Laptop
    Netbook
    PDA
    The Tools
    Cell Phones
  • Because it is everywhere…
  • 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
  • The Users
  • “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
  • The Users
    Photo: CommCare – Futures Group, 18 Dec 2009
  • Each technology deployment has unique characteristics and needs.
  • The solution must be carefully thought out.
    It must be inclusive of all stakeholders.
    • Donor
    • Program
    • M&E
    • IT
    • Field Staff
    • CHW
    • Beneficiary
  • Fight the urge to push the solution without input of all stakeholders.
  • The solution must satisfy the program need.
    But, it must work in the hands of the User.
  • It’s not about technology…
    it’s about People.
  • Afghanistan March 2011
  • Technology is becoming easy...
    Problems can be solved - they are technical!
  • The Challenge is:
    Point of interaction between user and beneficiary
  • How should I begin?
  • Technology Solution Criteria
    Functionality - What can it do?
    Usability - Can it be used?
    Scalability – Can it be used on a wider scale?
  • Functionality
    1st – clearly understand your “What”
    • Program and intervention needs.
    • M&E indicators(Results Framework)
  • Functionality
    The “What” always precedes the “How”
    (The “How” is the technology “Solution”)
  • Functionality
    Technology serves your “What”…
    …not the other way around.
    Resist forcing your “What” to fit the “How”.
  • Usability
    Technology always works in the lab and during training…
    …it can quickly become irrelevant in the context of field conditions.
  • “What Device?”
  • Usability
    “If it doesn’t work in the field…
    …then it doesn’t work”.
  • Scalability
    Small pilots are often successful…
    but they seldom scale up to wider implementations
  • Scalability
    So….Your solution worked!
    Can your solution expand to additional locations?
    Hint: Consider “Cloud”-based Software as a Service” (SaaS) solutions.
  • 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
  • mHealth and the CHW
    Google Groups: ICT4CHW
    ict4chw@go​oglegroups​.com
    Moderated by Dr. Neal Lesh of D-Tree