On Line Service Composition in the Integrated Clinical Environment for eHealth and Medical Systems

Medical and eHealth systems are progressively realized in the context of standardized architectures that support safety and ease the integration of the heterogeneous (and often proprietary) medical devices and sensors. The Integrated Clinical Environment (ICE) architecture appeared recently with the goal of becoming a common framework for defining the structure of the medical applications as concerns the safe integration of medical devices and sensors.This research was partly supported by iLand (EU ARTEMIS-1-00026) granted by the ARTEMIS JUand the Spanish Ministry of Industry, Commerce and Tourism. It has also been partly funded by the REM4VSS (TIN2011-28339) project grant of the Spanish Ministry of Economy and Competitiveness and by Universidad Carlos III de Madrid. The authors would also like to mention the large development team of the iLand reference implementation that performed an outstanding role to achieve a software proven also on commercial applications, and they thank them for their valuable efforts and work.Publicad

Management and Service-aware Networking Architectures (MANA) for Future Internet Position Paper: System Functions, Capabilities and Requirements

Future Internet (FI) research and development threads have recently been gaining momentum all over the world and as such the international race to create a new generation Internet is in full swing: GENI, Asia Future Internet, Future Internet Forum Korea, European Union Future Internet Assembly (FIA). This is a position paper identifying the research orientation with a time horizon of 10 years, together with the key challenges for the capabilities in the Management and Service-aware Networking Architectures (MANA) part of the Future Internet (FI) allowing for parallel and federated Internet(s)

Specification of high-level application programming interfaces (SemSorGrid4Env)

This document defines an Application Tier for the SemsorGrid4Env project. Within the Application Tier we distinguish between Web Applications - which provide a User Interface atop a more traditional Service Oriented Architecture - and Mashups which are driven by a REST API and a Resource Oriented Architecture. A pragmatic boundary is set to enable initial development of Web Applications and Mashups; as the project progresses an evaluation and comparison of the two paradigms may lead to a reassessment of where each can be applied within the project, with the experience gained providing a basis for general guidelines and best practice. Both Web Applications and Mashups are designed and delivered through an iterative user-centric process; requirements generated by the project case studies are a key element of this approach