Mobile Applications (Apps) for Community Pharmacy

1. Mobile Applications (Apps) for Community Pharmacy Will Lockwood American Society for Automation in Pharmacy

2. Learning Objectives • Compare and contrast website “mobile-optimization” and mobile applications (apps) • List criteria for evaluating a mobile app • Describe functionality that users look for in pharmacy apps and in retail apps in general

3. The Context Among U.S Adults • 85%use the internet1 72%of whom looked online for health information within the past year • 91%own a cell phone2 • 56% own a smartphone2 Susannah Fox, Maeve Duggan; Health Online 2013, Pew Internet & American Life Project, Jan. 15, 2013, http://pewinternet.org/Reports/2012/Mobile-Health/Key-Findings.aspx, accessed Oct. 9, 2013. Joanna Brenner; Pew Internet: Mobile, Pew Internet & American Life Project, Sept. 18, 2013, http://pewinternet.org/Commentary/2012/February/Pew-Internet-Mobile.aspx, accessed Oct. 9, 2013.

4. The Context Among U.S Adults Overall, 31% have used their phone to look for health information, up from 17% in 2010 (Sept. 2012 survey). 52%of smartphone users gather health information on their phones, compared with 6% of non-smartphone owners. Health status also plays a role. 80% receive and send texts, but only 9% report doing so for health or medical reasons. Women, those between the ages of 30 and 64, and smartphone owners are more to have signed up for health text alerts. 19% of smartphone owners have at least one health app on their phone. Exercise, diet, and weight apps are the most popular types (Sept. 2012 survey). Susannah Fox, Maeve Duggan; Mobile Health 2012, Pew Internet & American Life Project, Nov 8, 2012, http://pewinternet.org/Reports/2012/Mobile-Health/Key-Findings.aspx, accessed Oct. 9, 2013.

5. The Digital Platform Website Everyone should have this Buy/Develop Simple to complex Low cost to expensive Mobile Website Version of your website optimized to fit mobile devices Frequently offered as part of website package Add-on services available to avoid site revamp Both Require Connectivity to Work

6. The Digital Platform Mobile App Native application, not browser based Distributed through app stores Can operate: With or without data connection With or without user login Allows for two-way communications

7. Considerations: Building a Website Does your vendor/wholesaler/etc. offer a service or templates? Advantages: Easy branding, pharmacy-specific features such as refill requests/patient portal. If not, decide on how much functionality you need: Basic place-holder sites should be inexpensive Talk with vendor partners about options for adding refill functionality More complex, custom-designed sites can be expensive and require time & knowledge to administer maintain Make sure it’s mobile friendly

8. The Mobile App Three Options: • Build it yourself • Have someone build it for you • Buy a pharmacy ready app

9. Option 1: Build It Your Self Simple, generic solutions do exist. Can create Web-based HTML5 or native apps. Have to submit native apps to stores for distribution Require time to develop: You will need a clear vision of what look/features you want. Lots of possible features: Maps, forms, HTML, push notifications calendars, social, coupons, loyalty, etc. Pricing: Appears to run from $30/m to $100/m.

10. Option 1: Build It Your Self However… Is it white label? What about data integration? What about a migration path? What are the big players doing? What about pharmacy data security?

11. What Do Pharmacy Specific Apps Do? • Refills by Rx # Entry or by Scan • Profiles • Rx fill Status Updates • Alarms/Reminders/Push Messaging • Store Locator • Coupons • Reward/Loyalty Card and Account Details • Photo Printing Integration • eCommerce • Virtual Stores • Clinic Details, Including Insurance Accepted and Services Offered

12. Option 2: Get Someone to Build It What are you going to pay for? • Design • Coding • Server work • Project management • Hosting fees, yearly • Debugging • Unforeseen delays Source: http://www.formotus.com/14018/blog-mobility/figuring-the-costs-of-custom-mobile-business-app-development

13. Option 2: Get Someone to Build It Development Costs One iPad app development estimate ranges from $10,000 to $150,000 Low end gets you: “No integration, standard controls, minimal design and project management.” Higher costs for integration, and then you have to consider the need to partner with your system vendor. Greater degrees of branding, integration, security, and scalability all increase costs. Source: http://www.propelics.com/ipad-app-development-cost-a-breakdown/

14. Option 2: Get Someone to Build It Another estimate puts the “average cost of initial development for a typical mobile application (including environment setup, mobile service development, SDK and UI development, testing, deployment, and project management )” at an estimated $50,000 for a single app. http://www.anypresence.com/Mobile_Readiness_Report_2013.php pp. 11-12

15. Option 2: Get Someone to Build It The development process: Apple iOS

16. Option 2: Get Someone to Build It The development process: Android

17. Option 2: Get Some to Build It Maintenance One survey found that “Eighty-two percent of respondents report that their mobile applications are updated or enhanced at a minimum of every six months, and roughly a third report releasing updates or enhancements once a month or more frequently.” http://www.anypresence.com/Mobile_Readiness_Report_2013.php p. 4

18. The Mobile App Ecosystem Source: IDC Worldwide Quarterly Mobile Phone Tracker May 2013

19. The Mobile App Ecosystem That may look pretty good, but the mobile device ecosystem is very diverse: Relatively small number of dominant players (i.e., Apple, Google, Microsoft, Blackberry), but… “Fragmentation of the operating platforms and service provider-specific configurations multiply the variables that need to be considered for effective app development.” http://www.anypresence.com/Mobile_Readiness_Report_2013.php p. 6

20. The Mobile App Ecosystem Android Fragmentation (July 2013) 11,868 Distinct Android devices seen in 2013. 3,997 Distinct Android devices seen in 2012. 47.5% Samsung's share of those devices. 8 Android versions still in use. 37.9% Android users on Jelly Bean. Screen size also varies greatly Source: http://opensignal.com/reports/fragmentation-2013/

21. Mobile Ecosystem Fragmentation Source: http://opensignal.com/reports/fragmentation-2013/

22. Mobile Ecosystem Fragmentation Source: http://opensignal.com/reports/fragmentation-2013/

23. Mobile Ecosystem Fragmentation Android Screen Sizes iOS Screen Sizes Source: http://opensignal.com/reports/fragmentation-2013/

24. Option 3: Pharmacy Ready Apps Option 3: Buy a Pharmacy Ready App Many options out there from: Pharmacy system vendors IVR/Communications vendors App specialists Pharmacy Franchisers/Wholesalers

25. Option 3: Pharmacy Ready Apps Benefits: Costs can be low Often subscription based Offers pharmacy specific features Offers integration Offers outsourced development, app store needs, and maintenance Drawbacks: May be tied to a specific vendors tech ecosystem

26. Option 3: Pharmacy Ready Apps But there are solutions out there that can: • Let you start with basic features and fax/email submission of refill requests • Also offering a migration path to refill queue integration and more dynamic functionality.

27. Resources Development:http://www.forbes.com/sites/reuvencohen/2013/03/22/build-your-own-web-or-mobile-app-in-minutes-with-these-cloud-based-tools/ Distribution: http://en.wikipedia.org/wiki/Mobile_app#Development