Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Introducing the mHealth Platform as a Service

4,122 views

Published on

Published in: Technology, Business

Introducing the mHealth Platform as a Service

  1. 1. Jesus Rodriguez, KidoZen
  2. 2. Welcome Back!
  3. 3. 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
  4. 4. Enterprise Mobile-First PaaS KidoZen App Center Storage APIs Security APIs Messaging APIs LOB Connector Services Integration APIs HTML5 Hosted Apps Your Datacenter
  5. 5. Agenda • mHealth today • mHealth beyond mobile apps • Introducing the mHealth PaaS • Five steps to build a mHealth PaaS • Benefits
  6. 6. Mobile Health Today
  7. 7. Flash News: World Healthcare Systems are Broken
  8. 8. It Costs Too Much
  9. 9. Systems are not Optimized for Modern Technologies
  10. 10. Regulatory and Compliance Concerns
  11. 11. Healthcare Needs Are Growing Faster than Providers
  12. 12. Mobile Can Be The Solution…
  13. 13. mHealth Mobile Technologies mHealth Consumer Health Professional Health
  14. 14. And So Far We Have Focused on Apps…
  15. 15. Way too May Apps
  16. 16. Lots of Room for Growth
  17. 17. 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
  18. 18. mHealth Beyond Mobile Apps…
  19. 19. Not Everything is About Apps
  20. 20. mHealth Data Access
  21. 21. Security
  22. 22. Compliance
  23. 23. Every mHealth App Requires Complex Backed Infrastructure
  24. 24. App Management
  25. 25. Monitoring & Analytics
  26. 26. An App-Centric Strategy Doesn’t Scale Beyond Smartphones or Tablets
  27. 27. It’s not about building mHealth apps?
  28. 28. It’s about providing the foundation to facilitate the implementation, management and distribution of mHealth Solutions
  29. 29. Introducing the mHealth Platform as a Service
  30. 30. Goal: A platform that enables the implementation, management and lifecycle of mHealth applications
  31. 31. Goal: Remove the barriers for building mHealth applications
  32. 32. Goal: Bring mobile talent to mHealth solutions
  33. 33. mHealth PaaS Data Services Analytics Services App Analytics Security Services App Monitoring mHealth PaaS Mobile Client SDKs Mobile Infrastructure Compliance Services mHealth App Store
  34. 34. 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
  35. 35. 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
  36. 36. 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
  37. 37. 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
  38. 38. 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
  39. 39. 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
  40. 40. 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
  41. 41. 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
  42. 42. 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
  43. 43. Five steps to build a mHealth PaaS
  44. 44. You can’t buy it. You need to build it!
  45. 45. Expose Mobile-First mHealth APIs • 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)
  46. 46. Enable Additional Mobile-First Infrastructure 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)
  47. 47. 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)
  48. 48. 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
  49. 49. 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)
  50. 50. You are set!
  51. 51. Some Things to Consider • Cloud vs. On-Premise vs. Hybrid • Geographic Locations • App Distribution Models • Developer Engagement • App Monitoring and User Engagement
  52. 52. If we have a mobile health paas…
  53. 53. Developers can write mHealth applications without being concerned about the backed infrastructure
  54. 54. Any mobile developer will be a potential mHealth developer
  55. 55. mHealth applications will share and use data in standard, secure and compliant ways
  56. 56. Consumers will willingly share mobile data in order to obtain better value from their mHealth solutions
  57. 57. Sensors, smart objects, smartphones and tablets will share the same infrastructure
  58. 58. Providers of mHealth solutions can leverage a consistent and interoperable model to access mHealth data and services
  59. 59. 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
  60. 60. Thanks jr@kidozen.com http://www.kidozen.com http://jrodthoughts.com http://twitter.com/#!/jrodthoughts http://weblogs.asp.net/gsusx

×