Robert Hancock,MobileSmith VP of Sales

May 30, 2013

Patient Engagement Apps: How to Get Started

Who is MobileSmith:

• Enterprise-class DIY app development platform

• Your app management back office in the Cloud

Who is Robert:

• MobileSmith VP of Sales • More than 15 years of experience

selling innovative technologies to vertical markets

1

Today We Will Explore:

• How to come up with great mobile use cases for efficient Patient Engagement

• How to design and wireframe your own Patient Engagement app

• How to prototype and build it easily and at low cost

2

Engagement: Key to Improved Trust

• Access to patient info online =peace of mind; feeling of control and empowerment

• Secure messaging = improved doctor/patient relationship & trust

Mayo Clinic’s recent survey of 45,000 patients:

Eric Manley, eHealth System Manager, Mayo Clinic

Patient Engagement is not just an IT solution. It’s a CARE solution. IT is just the mechanism.

3

Why Mobile Engagement?

• eClinicalWorks survey: 60% physicians said that at least half of their patients would be interested in appointment reminders via a mobile app

• Pew 2012: 50% of smartphone owners use their devices to get health information; 19% have downloaded a healthcare app

• 200 million active iOS and Android devices in the US

• Older demographics are catching up!

4

Poll: where does your organizationstand on mobile apps?

5

Thinking about it Building! Launched 1 app Launched 2 or more

App Ideas Just Pop Up

6

IT Department

Human Resources

Technology Partners

Patient RelationsMarketing

Medical Departments

Custom Apps are Costly!

7

Cost to build a custom, full-featured mobile app:from $30,000 to $150,000

Cost x2

And yet…

8

• Out of 97,000 health apps, 26% are used only once

• 74% of users drop out by the 10th use

• Top reason for dropping out:

lack of user friendliness

• 91% of users name ease of navigation

• Patients desire customized feedback based on condition

What makes Apps favorable?

From Idea to App: Key Steps

9

Idea

Requirements Dump

Wireframe Mockup Development

Testing

Good planning great app And vice versa!

Step 1: Idea!

10

• Check in the app stores: are there any apps already doing it? NO I may have a great app idea! Yes Can I improve the way they’re doing it?

• Could my idea be accomplished via a mobile website?

• Your app could be denied by Apple• Not a good use of resources

• Will the app connect to any data sources? • May require involvement of IT dept.

Yes!

Yes

Use-Case: Post-Tonsillitis Ice Cream App

11

Medication reminder

Checklist and regimen

Monitoring of ‘Red flags’

Follow-up reminder

Fun and treats for the child

Use-Case: Prescription Adherence

12

Medication reminder

Your home care team

Drugs reconciliation

Follow-up reminder

‘Red flags’ and responseInteractive care planfor the whole family

Use-Case: Cancer Center App

13

Track your treatment

Manage your care team

Network with patients

3D tour of the facility

Stay informed and entertained throughout your journey

Try on some wigs!

Step 2: Requirements Dump

14

• Put down everything you want in your app, in bullet points

• Group similar bullet points; whittle them down to make sense

• Pick out 1-2 key features to be the centerpiece of your app

• Pick 2-3 secondary features• Dump the rest!

Something to Consider During Steps 1-2:One or Several Apps?

15

• What audience am I trying to reach with my app?• Could it be too broad?

• Any there too many features in my app?• Diluted apps are not user-

friendly• Do I have any secondary

features on my list too good to dump?

Trimming Down Your Use Case

16

How do I feel today?

My care plan My care team Appointments Lab results Hospital info Facility tour Drug info Reconciliation Doctor info Doctor referral

Drug info Drug

reconciliation Fill

prescription

Doctor info Doctor Referral Feedback and

recommend

Step 3: Storyboarding

17

• Sketch your requirements as pages (views):• Start w ith the root v iew (Hom e page)

• List a ll the generic v iew s

• NO w orkflow ; NO interfaces at th is point!

• Get a clear view of all the pages: 10 or 100 pages? - Too m any or too few ?

• Sketch your requirements as pages (views):• Start with the root view (Home page)• List all the generic views• NO workflow; NO interfaces at this point!

• Get a clear view of all the pages: 10 or 100 pages? - Too many or too few?

HOMEMy

Care Plan

My Care Team

Add Doctor

How do I feel

today?

New Appointment

Etc.

Step 4: Wireframing

18

• Lay out each page from your storyboard: buttons, nav bar, tabs, m aps, im ages, m edia…

• Write in notes and arrow s for page transitions

• Describe everyth ing in deta il!

• Use graphic designer to ensure feasib ility

• Review w irefram es w ith people on your team least fam iliar w ith m obile

• Lay out each page from your storyboard: buttons, nav bar, tabs, maps, images, media…

• Write in notes and arrows for page transitions

• Describe everything in detail! • Use graphic designer to ensure

feasibility• Review wireframes with people

on your team least familiar with mobile

Ensuring the Best User Experience

19

• Keep in mind the user goals of your app (see your 1-2 key features)

• Tap through your wireframe: Can the user achieve each goal in 4-5

clicks? Do I have all the necessary screens and

buttons? Do all screens/elements have a purpose? Can the user navigate home easily? Are there easy ways to view & input data?

• Keep in mind the user goals of your app (see your 1-2 key features)

• Tap through your wireframe: Can the user achieve each goal in 4-5

clicks? Do I have all the necessary screens and

buttons? Do all screens/elements have a purpose? Can the user navigate home easily? Are there easy ways to view & input data?

USER EXPERIENCE: FUNCTIONALITY:

50% 50%

Step 5: Mockup

20

• Your designer creates page # 1 in Photoshop using defined color schem e

• You approve design : colors, shapes, im ages, font etc.

• Secondary pages are created and approved

• M obileSm ith has in -bu ilt design best practices for iOS and Android

• Your designer creates page #1 in Photoshop using defined color scheme

• You approve design: colors, shapes, images, font etc.

• Secondary pages are created and approved

• MobileSmith has in-built design best practices for iOS and Android

saves up to 70% of your designer’s time!

Step 6: Prototype & Review

21

• Option 1: review screenshots

• Option 2: review the prototype on your device:

• “Build for testing” on M obileSm ith

• Send the prototype OTA to your device or your colleagues’

• Review ; change design/layout; rebuild ; test again!

• Refine the U I/UX at m in im um cost

• Option 1: review screenshots• Option 2: review the prototype

on your device:• “Build for testing” on

MobileSmith• Send the prototype OTA to

your device or your colleagues’

• Review; change design/layout; rebuild; test again!

• Refine the UI/UX at minimum cost

What You Can Do With MobileSmith:

22

• Built-in design best practices for each OS: save up to 70% of time at mockup and prototype stages

• Need to reinvent your app quickly? No problem – and no additional cost!

• Streamlined app versioning• Enterprise-class security and robust scalable infrastructure

• Real-time updates and push notifications• Secure integration with your backend systems

• Your App Forge on the Cloud: create dozens of CUSTOM, native apps at the cost of one

: Where We Fit

23

Pure Custom App Development• The most expensive option• Requires development team• High long-term costs• Slow development• Limited creative input from

stakeholders

Template Based App• Low level creativity• Limited functionality• Lowest common denominator• No branding, no security

MobileSmith• You own the entire process

through completion• Rapid prototyping & development• Custom product at much lower

cost• Multiple apps instead of just one• Minimal long-term cost

Request a Demo and Start Building!

24

Questions?

(919) 602-3025