100 likes | 227 Views
FHI & Text to Change. Building an IT Partnership in a World of Change. Where we began…. +. =. EC research in Ghana and Kenya identified: Lack of knowledge around contraceptive methods High rate of mobile phone ownership
E N D
FHI & Text to Change Building an IT Partnership in a World of Change
Where we began… + = • EC research in Ghana and Kenya identified: • Lack of knowledge around contraceptive methods • High rate of mobile phone ownership • What if we created a means of educating women and men about contraception using mobile phones?
First Steps – m4RH Concept • Idea originated from research with contraceptive users in East and West Africa • Concept Testing was conducted with family planning users in focus groups and individual interviews • Message Development: • m4RH: Based on WHO and Country Norms, Expert Review • ECINFO: Theory-driven role model stories • Message Testing wasconducted with health clinic clients and EC users • Usability Testing helped with refining system interaction and navigation
Technology Options • Web-based SMS service (e.g. Clickatell) • Desired more control over the system • Capability within FHI • First project of its kind at FHI; not a good business case • Investigated relationships with Net Hope, Nokia, Cisco, etc. • Direct collaboration with mobile provider – Safaricom • Off-the-shelf options • MobileActive.org comparison matrix • FrontlineSMS
FrontLine SMS • I <3 frontline • User-friendly interface • Great for initial demonstrations and system testing • Easily deployable in the field • Concerns regarding reliability • Short code or Phone Number? • Phone number seems too ‘clunky’ • Short code is more user friendly, easy to remember • Short code requires a lot of work and likely a 3rd party • We need a technical partner!!
…And Then There Were Three • Sex:Tech 2009 solicitation for partners • Narrowed options to Frontline SMS, Text to Change, and Voxiva • Key decision points for the system: • Flexibility • Reliability • Sustainability • Selected TTC as official partner for m4RH in 2009
Roles • FHI • Develop and test system content • Design research process • System usability testing (with ) • TTC • Programming • Input on design and proposed algorithm • Data monitoring
Other Considerations • Flexibility • Ability to refine ‘on demand’ • Extremely important, especially for a new system. • Quality control • Who is checking the system and data? • Cultural considerations • Having a partner in region is extremely helpful • IT versus Health Technology • TTC is knowledgeable in Public Health (as is Voxiva), which has made communication and collaboration easy
The BIG Considerations • Sustainability • Is the system flexible enough to support “in-a-box” packaging? • If not, where will the separation be made and how will the technical piece be incorporated? • Cost • If you are able to get to a packaged system how much will it cost to support it? • If you aren’t delivering a packaged system, how much will it cost to implement? • Management costs, short code, identification of partner, etc.
What We’ve Learned • Having a good IT partner is critical • Finding a partner can be a daunting process • When all else fails, just ask! • Location, location, location • Regional expertise is a benefit • Be clear in expectations • Upfront and long-range costs