GLOBAL HEALTH 2013 : The Second International Conference on Global Health Challenges TICE.Healthy Framework for Developing an Ecosystem of Applications in the Domain of Informal Health Pedro Catré, Jorge Dias João Quintas, Alcides Marques Faculty of Sciences and Technology IPN Laboratory of Automatic and Systems and Laboratory University of Coimbra of Informatics and Systems Coimbra, Portugal Instituto Pedro Nunes [email protected], [email protected] Coimbra, Portugal [email protected], [email protected] Abstract— This paper presents a platform being developed in a it provides for developers, the types of applications that are large scale national project that aims to create an ecosystem of supported in the marketplace and a high-level view of its services and applications where patients, relatives and architecture. Section VI provides conclusions for this paper. healthcare professionals can cooperate in day-to-day activities. It will implement functionalities for managing medical, social II. STATE OF THE ART and context information, for integrating mobile devices, This section analyses current market solutions that remote control and sensors, with insurance of information present comparable functionalities to the ones required by security. the eVida platform. Although this analysis includes eHealth Keywords-eHealth; informal healthcare; service-oriented platforms it does not focus exclusively on that use case. architecture; REST. A. Commercial Web Portals Google Health has been permanently discontinued since I. INTRODUCTION it did not reach the initially expected product adoption. TICE.Healthy – Health and Quality of Life Systems – is However, it is still relevant since it was one of the primary a research and development project that represents a commercial platforms available providing personal health collaborative effort to design and deploy innovative products records. This platform allowed users to persist, manage and and applications in the fields of eHealth and Ageing-Well. share the user’s health data with other users. It also provided The main goal of this project is to create a web-based an API allowing the users to share data with external platform, named eVida, designed to ensure a set of applications that could provide several services like services/features to support the creation of new products, scheduling appointments, processing health data, among processes, services and applications [1], [2]. others [6]. From a global perspective, the platform being developed Microsoft HealthVault is an XML-over-HTTP web plays the central role within the project TICE.Healthy. Its service exposing a set of XML-based methods that primary objectives are data acquisition and processing from developers can leverage to build applications that connect to various collaborating entities (data providers – supply side) HealthVault. Also, a number of SDKs are available that so that it can be shared and used by service providers. The deliver platform-specific abstractions for working with eVida website can be consulted at [3], and a promotional HealthVault [7]. It is worth noting that this platform is only video demonstrating some of its features is available at [4]. available in the United States of America and the United It is true that we are now witnessing a proliferation of Kingdom. Although Microsoft Health Vault supports an eHealth platforms [5]; however, they are mainly focused on ecosystem of other platforms and partner services to leverage offering a single service. eVida’s innovation comes precisely the user’s data, assuming the required permissions over the from breaking free of this paradigm by allowing the creation data were granted, it lacks many important features. of an ecosystem of applications that can provide Specifically, this platform does not integrate web complementing capabilities and whose value can potentially applications in a single place and it does not provide the final supersede the sum of the benefits delivered by each user with a transparent and singular experience while using individual application. the platform. In other words, HealthVault does not support This paper presents the architectural approach and a brief embedded applications, meaning each application runs description of the main modules comprising the eVida independently, outside of HealthVault and no mechanisms platform. are provided for inter-app communication. Furthermore, it The paper is organized as follows. Section II presents an does not provide Single-Sign-On [8], which is a facility analysis of related work. Section III gives an overview of the through which a user logs in once and gains access to all platform’s architecture. Section IV presents the main systems without being prompted to log in again at each of modules that make up the platform. Section V describes the them. In fact, in order to start using a new application the Web Portal, more specifically: its purpose, the main features user is taken to the service provider’s website where he Copyright (c) IARIA, 2013. ISBN: 978-1-61208-314-8 49 GLOBAL HEALTH 2013 : The Second International Conference on Global Health Challenges needs to register, sign-in and link the new account to the on - HealthVault account. ons - iGoogle is a service provided by Google that consists of a apps apps apps web portal that supports web feeds and web gadgets. The Cross browser Supports Supports Granular Granular Embedded Embedded Permissi native mobile mobile native Consistent UI Consistent gadgets are defined through an open custom specification web Supports Single Single sign called Google Gadgets [9]. Both the development and use of LinkedIn ✓ ✓ ✓ ✓ ✓ ✓ ✗ the applications is open to the public [10]. It works similarly Apps to other portals such as My Yahoo!, Netvibes and Pageflakes Twitter ✗ ✓ ✓ ✗ ✓ ✓ ✓ [11]. Apps Facebook Apps consist of applications hosted in an Chrome external server that are accessed in Facebook in a page called Web ✗ ✗ ✓ ✗ ✗ ✓ ✗ Canvas. Together, they provide functionality through APIs, Store Podio such as the Social Channels API that includes bookmarks, App ✓ ✓ ✗ ✓ ✓ ✓ ✓ notifications, News Feed stories and search [12]. Facebook Store also offers an authentication system, called Facebook eVida ✓ ✓ ✓ ✓ ✓ ✓ ✓ Connect, as an alternative mechanism to the registration of a user. In other words, Facebook Connect allows external applications to support Facebook accounts [13]. eVida already supports the most common features LinkedIn supports applications that follow the provided by major web portals. However, it is an ongoing OpenSocial specification [14]. These applications can be project with many required functionalities still in added to the user’s homepage and to his personal profile development, such as a payment system for the marketplace [15]. and a fully featured interoperability module. Twitter does not support applications in the same way as III. PLATFORM ARCHITECTURE OVERVIEW the previous examples. It offers a REST API that enables third-party applications to interact with the majority of the The platform’s architecture is based on the design web site’s functionalities [16]. It also provides an principles of service-oriented architectures (SOA), because authorization and authentication mechanism that can be used of its distributed and extensible nature. This approach by external applications (similarly to Facebook Connect). increases the abstraction and encapsulation within the To that end, Twitter employs OAuth. The permissions that a system. The platform exposes a set of Representational State user can grant are granular enough that he can limit the Transfer (REST) services as the communication mechanism access to specific data and communication on his behalf. with the data and service providers. Fig. 1 illustrates the Chrome Web Store allows the specification of high-level architecture of the platform. Three main applications published as a compressed archive composed of components can be easily identified, which implement the a manifest, HTML, CSS, and JavaScript files [17] or as a information and interaction channels for selling products and pointer to an external server [18]. Neither type of application health services: the database stores all the administrative is embedded in the Chrome Web Store. Also, the mechanism data, and configuration data of the platform; the backend for executing the applications is not interoperable; it’s services provide security, interoperability and information restricted to the Chrome browser. services; and the frontend is comprised by the platform’s Podio is a web system that supports collaborative work web portal, which exposes the tools to submit and publish for companies and provides extensibility through external applications within the platform’s ecosystem. web applications. It allows the discovery and purchase of applications similarly to the Chrome Web Store [19]. Table I presents a comparison of the functionalities of the various commercial projects that were presented. TABLE I. COMPARISON OF THE FUNCTIONALITIES OF THE COMMERCIAL PROJECTS THAT WERE ANALYSED Figure 1. The platform’s high-level architecture. on This platform implements functionalities to manage - ons - medical, social and context information, for integrating mobile devices, remote control and sensors, with insurance apps apps apps Cross browser Supports Supports Granular Granular of information security. Embedded Embedded Permissi native mobile mobile native Consistent UI Consistent Supports web Supports Single Single sign Google IV. PLATFORM