introducing the mhealth platform as a service

Introducing the mHealth Platform as a Service

Jesus Rodriguez, KidoZen

Welcome Back!

About Me• Hackerpreneur• Co-Founder KidoZen, Inc• Advisor to software companies(Microsoft, Oracle….)• Board member• Speaker, Author• Investor• http://jrodthoughts.com• http://weblogs.asp.net/gsusx • https://twitter.com/jrdothoughts • http://kidozen.com

Enterprise Mobile-First PaaS

Messaging APIs

LOB Connector Services

App Center Storage APIs

HTML5 Hosted Apps

Security APIs

Integration APIs

SDKs

KidoZen

Your Datacenter

Agenda• mHealth today• mHealth beyond mobile apps• Introducing the mHealth PaaS• Five steps to build a mHealth PaaS• Benefits

Mobile Health Today

Flash News: World Healthcare Systems are Broken

It Costs Too Much

Systems are not Optimized for Modern Technologies

Regulatory and Compliance Concerns

Healthcare Needs Are Growing Faster than Providers

Mobile Can Be The Solution…

mHealth

Mobile Technologie

s

Professional Health

Consumer Health

mHealth

And So Far We Have Focused on Apps…

Way too May Apps

Lots of Room for Growth

As a Result…

• Consumers are overwhelmed with choices

• The ecosystem is incredibly crowded

• There is not clear connection between consumer apps

and medical institutions

• Providers enabling access to data and capabilities

• Users reporting data

• The complexity of building mHealth apps is linear

mHealth Beyond Mobile Apps…

Not Everything is About Apps

mHealth Data Access

Security

Compliance

Every mHealth App Requires Complex Backed Infrastructure

App Management

Monitoring & Analytics

An App-Centric Strategy Doesn’t Scale Beyond Smartphones or Tablets

It’s not about building mHealth apps?

It’s about providing the foundation to facilitate the implementation, management and distribution of

mHealth Solutions

Introducing the mHealth Platform as a Service

Goal: A platform that enables the implementation, management and lifecycle of mHealth applications

Goal: Remove the barriers for building mHealth applications

Goal: Bring mobile talent to mHealth solutions

mHealth PaaS

mHealth PaaS

Data Services

Analytics Services

Security Services

Mobile Infrastructure

mHealth App Store

Compliance Services

Mobile Client SDKs

App Monitoring

App Analytics

mHealth PaaS: Data Services

Provide mobile-first APIs that enable secure-compliant access to healthcare data sources

Remove the complexities of integrating mHealth apps with backend data

Electronic medical records, insurance records, wearable sensor data

mHealth PaaS: Security Services

Enable security and privacy capabilities for mobile applications

Abstract the complexities of implementing Health Care and enterprise security protocols in mHealth applications

Ex: Multi factor authentication, trust-federation protocols, data encryption, signature protocols

mHealth PaaS: Infrastructure Services

Enable the backend infrastructure required by mHealth applications

Allow mHealth app developers to focus on building apps, not infrastructure

Ex: Video, secure storage, push notifications, secure SMS, etc

mHealth PaaS: Business Intelligence Services

Provide consumers with intelligent information or analytics to improve the value of specific mHealth apps

Provide app builders with artificial intelligence and analytic capabilities that can be incorporated into applications

Ex: Patient outcome statistics, treatment recommendations

mHealth PaaS: Compliance Services

Provide a compliant set of mobile first APIs that can be consistently leveraged by mHealth applications

Provide on-demand compliance and policy management capabilities applied to the data and APIs used by mHealth apps

Ex: HIPAA, PHI, FDA compliance

mHealth PaaS: mHealth App Store

Enable secure distribution mechanisms for mHealth applications

Enable patients with apps that can improve the value of the care provided by medical institutions

Ex: Patient app store

mHealth PaaS: mHealth Apps

Enable secure distribution mechanisms for mHealth applications

Enable patients with apps that can improve the value of the care provided by medical institutions

Ex: Patient driven outcome apps, mobile health games, scheduling, EMR, etc

mHealth PaaS: mHealth Devices

Enable secure distribution mechanisms for mHealth applications

Enable patients with apps that can improve the value of the care provided by medical institutions

Ex: Patient driven outcome apps, mobile health games, scheduling, EMR, etc

mHealth PaaS: App Analytics

Provide consumers with intelligent information or analytics to improve the value of specific mHealth apps

Provide app builders with artificial intelligence and analytic capabilities that can be incorporated into applications

Ex: Patient outcome statistics, treatment recommendations

Five steps to build a mHealth PaaS

You can’t buy it. You need to build it!

Expose Mobile-First mHealthAPIs• Enable mobile integration with your healthcare

backend systems: EMRs, Patient study databases • Enable mobile integration with other backend

systems: databases, patient social networks, etc• You can use: • API Gateways: Apigee, Layer7• Enterprise Mobile Backend as a Service: KidoZen, FeedHenry• Build your own• Mobile Enterprise Application Platforms: SAP SMP, IBM

Worklight (if you have a high tolerance for pain)

Enable Additional Mobile-FirstInfrastructure Capabilities• Multi-Factor Authentication• Storage• Push Notifications • Logging • You can use:

• Build your own infrastructure• Enterprise Mobile Backend as a Service: KidoZen, FeedHenry• Build your own• Mobile Enterprise Application Platforms: SAP SMP, IBM Worklight (if you are mad at your employer)

Provide an App-API-Data Marketplace• Expose your mHealth app catalog• List the APIs available to developers• List the data sources available to mHealth applications• You can use: • Build your own infrastructure• Enterprise App Stores: Apperian• Enterprise Mobile Backend as a Service: KidoZen, FeedHenry• Mobile Enterprise Application Platforms: SAP SMP, IBM

Worklight (if you are really depressed)

Build your Mobile SDKs• Simplify the mobile developer experience• Enable mobile client side capabilities: in-device

storage, inter-app communication• You can use: • Build your own SDKs

Add Compliance • Create compliant versions of any storage used by the

platform• Create compliance policies that can be added to any

mobile API for the platform • You can use: • Build your own• Enterprise Mobile Backend as a Service: KidoZen, FeedHenry• Mobile Enterprise Application Platforms: SAP SMP, IBM

Worklight (if like to write big checks)

You are set!

Some Things to Consider• Cloud vs. On-Premise vs. Hybrid• Geographic Locations • App Distribution Models• Developer Engagement• App Monitoring and User Engagement

If we have a mobile health paas…

Developers can write mHealth applications without being concerned about the backed infrastructure

Any mobile developer will be a potential mHealth developer

mHealth applications will share and use data in standard, secure and compliant ways

Consumers will willingly share mobile data in order to obtain better value from their mHealth solutions

Sensors, smart objects, smartphones and tablets will share the same infrastructure

Providers of mHealth solutions can leverage a consistent and interoperable model to access

mHealth data and services

Summary• The first generation of mHealth solutions have been

focusing on mobile apps• The mHealth PaaS is a next generation model to

enable the implementation of mHealth solutions• The mHealth PaaS focusing on enabling data access,

security, compliance and management services to simplify the implementation of mHealth apps• Technologies such as enterprise mobile backend as a

service can provide the foundation to the mHealth PaaS

Thanksjr@kidozen.com

http://www.kidozen.comhttp://jrodthoughts.comhttp://twitter.com/#!/

jrodthoughtshttp://weblogs.asp.net/gsusx