FI-STAR (Future Internet Social and Technological Alignment Research - E-Health) Enablers

a)     Local Data Processing Service

http://fistarcatalogue.fiware.eng.it/enablers/local-data-processing-service

An implementation of the Local Data Processing Service SE of the open specification version 1.0. as native Android library (.jar). A sample Android application (.apk) for the definition of rules and the processing functionality to be used by application developers.

Why to get it

To implement the event-based processing for application modules and Specific Enablers (SEs) deployed in the front-end.

 

b)    Local Data Storage Service

http://fistarcatalogue.fiware.eng.it/enablers/local-data-storage-service

An implementation of the Local Data Storage Service SE of the open specification version 1.0. as native Android library (.jar). A sample Android application (.apk) for demonstration how the service can be used by application developers.

Why to get it

To implement secure storage for application modules and Specific Enablers (SEs) deployed in the front-end.

 

c)     Mediation Service

http://fistarcatalogue.fiware.eng.it/enablers/mediation-service

The Mediation Services enabler (BMED) permits the creation of mediation services based on mediation tasks.
This allows other FISTAR SE to interact with legacy system in the health sector (existing eHR, existing hospital systems, etc.).
Mediation tasks for health sector are available
And sample services are provided in the package as a base for customized services and for testing purposes.
The BMED works over WSO2 ESB.

Why to get it

Use it if you need to intearct with a legacy system. You will get some templates and guides for the creation of mediation services for the health sector, such as but not limited to: translate HL7 to/from custom XML or Json, translate SOAR2REST and REST2SOAP, send email messages

 

d)    Monitoring Service

http://fistarcatalogue.fiware.eng.it/enablers/monitoring-service

The Monitoring Service SE provides monitoring information about the used resources as well as the deployed services to multiple stakeholders: administrators, end-users and other FI-STAR Backend Platform components. They might have different interest on monitoring parameters. This SE supports cross-layer monitoring from low-level infrastructure resources (physical and virtual) up to application level. From this prospective, several system related metrics are measured, such as CPU-, memory- and disk-usage, network throughput and latency, as well as services specific parameters like availability, load, throughput, downtime and failure rate. It allows its user to even define and measure own customized (user-defined) metrics that can be used to monitor user applications. Furthermore, it includes a set of probes used to retrieve monitoring information from OpenStack-based cloud platforms (e.g. deployed tenants, list of instances per tenants, CPU-, memory- and disk-usage per tenant, etc.) and make them available for their administrators. Measurement data is provided on-demand through different interfaces.

Why to get it

In principle, monitoring information is required in any infrastructure to ensure its availability, health and performance. Besides, in cloud-based infrastructures, monitoring plays a major role in terms of improving resource utilization, management and elasticity support. According to the requirements of the FI-STAR there is a need for providing monitoring information about the deployed resources hosting the FI-STAR platform and also about the running services. It is also required to provide monitoring information for validating SLAs.

 

e)     Motion Evaluation

http://fistarcatalogue.fiware.eng.it/enablers/motion-evaluation

The Motion Evaluation SE provides a secure REST API for analyzing and comparing human motion data. It offers the capability to evaluate motion data according to user desires and skill requirements. 

Why to get it

With increasing pressure being placed on medical institutions within Europe and around the world, it is becoming more and more important for health care professionals to be prescribing home based exercise rehabilitation treatments to empower patients to self-monitor their rehabilitation journey. Home-based exercise rehabilitation has been shown to be highly effective in treating conditions such as Cardio Vascular Disease.  However, adherence to home based exercise rehabilitation remains low. Possible causes for this are that patients are not monitored, they cannot be confident that they are performing the correct exercise or that they are performing the exercise accurately and they receive no feedback.

Novel patient-centric gamified rehabilitation exercise platforms can help address the issue of adherence to these programmes. The key underlying technology to a system like this is the ability to record and compare the patient movements with the precise exercises that they have been prescribed. This is where the motion analysis S.E. comes in.

The analysis and comparison component of the Motion Evaluation SE works by comparing two motion capture skeletal movement sequences. Advanced algorithms allow the two sequences to be analysed and outputs a percentage based on how similar the two sequences are.  This will allow users to create a wide range of rehabilitation and exercise scenarios that can accurately measure the quality of the movements being performed.

 

f)      Notification Service

http://fistarcatalogue.fiware.eng.it/enablers/notification-service

An implementation of the Notification Service SE of the open specification version 1.0. as native Android library (.jar).

A sample Android application (.apk) for the definition of notification events and pub/sub functionality to be used by application developers.

Why to get it

To implement the event-based communication between application modules and Specific Enablers (SEs) deployed in the front-end, and between the front-end and back-end services. The notification events between components in the front-end are transmitted via the pub/sub mechanism and the native front-end communication system, while the communication to/from the back-end is handled by the Connectivity Service SE. Events between front- and back-end must be registered both in the Notification Service (front-end) and the Event Service (back-end).

 

g)     PACS

http://fistarcatalogue.fiware.eng.it/enablers/pacs

The FI-STAR “Picture Archiving and Communication System” Specific Enabler (FI-STAR PACs) is a web based platform for the management and exchange of (health) images and related information. It is based on the DICOM open standard and implements some IHE (Integrating the Healthcare Enterprise) profiles. It is delivered as a web platform in order to maximize its collaborative nature.

Why to get it

The interoperability and images information sharing is a key aspect for the success towards the collaboration among different departments (e.g. radiology, endoscopy, pathology etc.) of the same (or distinct) health agency. The possibility for such institutions to integrate, within their Information System, a layer able (i) to support the images exchange (for both senders and receivers) (ii) to adopt an unique information model and (iii) to offer information management services, has a value because it fix the interoperability problems and makes easier and faster the integration of such images into the Patient Master Record (e.g. EHR).

The goal of the PACs enabler is exactly to provide such kind of capability to third party applications (such as those developed by SMEs involved in Phase 3).

 

h)    Real Time Communication Service

http://fistarcatalogue.fiware.eng.it/enablers/real-time-communication-service

The Real Time Communication Service SE offers back-end, infrastructural services enabling audio-video conferencing busienss levle sessions management, low level technical signalling according to the WebRTC protocol and NAT traversing capabilities.

Why to get it

As the native support of the modern web browsers for the emerging new standard for real time network communication namely webRTC procol is relatively easy to exploit, the infrastructural part needed to estabilish this p2p connection is still an issues. Indeed, paid SaaS/IaaS services for e.g. webRTC signalling or NAT network traversing are available but still these are external 3rd-party solution that developers/service provider cannot fully control. This is even more important in cases, when a privacy of peers is a priority (e.g. FI-STAR helath domain). Therefore, the complete software infrastructure enabling webRTC signaling, presence, session management and monitoring for streaming clients (peers) is provided by this SE. In particular this SE provides a RESTful interface for audio-video sessions management, websockets (socket.io) interface for signalling purposes based on open-source EasyRTC and STUN/TURN services basing on Google rfc5766-turn-server implementation.

 

i)      Security&Privacy-CMS

http://fistarcatalogue.fiware.eng.it/enablers/securityprivacy-cms

The Security&Privacy-CMS SE provides

Why to get it

Digital Certificates have a wide range of application especially in the health-care domain. Most of the times the usage of certificates are accompanied with the complexity of setting up and maintaining a PKI infrastructure. Such infrastructure requires the operation of  many parallel Authorities (Registration, Verification etc). Many of these authorities are realized by many open-source modules (OpenSSL). However, there are many fully-fledged PKI solutions that can be used in order to operate such an environment. One of this solution is EJBCA  which is a Certificate Authority software, built using Java (JEE) technology.

Since EJBCA is delivered as a cloud applicance (CA-in-a-box), through the usage of the specific SE, a full REST-layer for managing the internal CA entities can be accomplished.

 

j)      Security&Privacy-IAC

http://fistarcatalogue.fiware.eng.it/enablers/securityprivacy-iac

You get a reference implementation of an integrated RESTful access control service for emerging healthcare application and service development.

Why to get it

Access control is the key security concern for any system that contains sensitive data especially healthcare domain. By externally offering such functionalities, this enabler helps application/service developers not only saving a lot of time when implementing their security logic but also adapting easily to new requirements. Moreover,

- Various related Future Internet technologies are taken into account to fulfill the security and privacy requirements from healthcare including those are specific such as the capability to support specific attributes for user identification and authorization.

- Different security standards are taken into account including two current high-interested ones: OASIS XACML and IETF OAUTH. The former is the fine-grained access control for enterprise applications. The latter, an evolving open authorization framework, was designed to secure API access for cloud-based application/service.

- Is flexible enough to deploy in the cloud, on customer premise or user machine.

The goal of the Security&Privacy-IAC (Integrated Access Control) enabler is exactly to provide such kind of capability to third party applications (such as those developed by SMEs involved in FI-PPP Phase 3).

 

k)    Security&Privacy-TSL

http://fistarcatalogue.fiware.eng.it/enablers/securityprivacy-tsl

A TSL Module SE which is an implementation of HTTP/S REST APIs exposing ETSI TSL (Trust Service Status List) 102.231 standard for their creation in XML or ASN.1 formats. For example, to create a TSL asset, required are REST APIs to manage TSL’s, scheme information, trust service providers (TSPs), service information and service history Information. The APIs use JSON or XML formats.

Why to get it

Provides the ability to create, read, update and delete TSL components. Mostly will be used for the needs of SEs or GEs requiring a Trust-Service-Status-List endpoint for checking validity of Certificate Authority CAs. The TSL provides another level of trust for any issued certificate tokens from a PKI.

 

l)      Semantic Enricher

http://fistarcatalogue.fiware.eng.it/enablers/semantic-enricher

The FI-STAR Semantic Enricher Specific Enabler is offered as Android Library that can be included in project in order to enable data enrichment with semantic information. Semantic enrichment is done through the configuration of the Semantic Enricher which is done by the application. Source of data can be changed through provided interface. Communication between Semantic Enricher and application is done as reply/response via Broadcast Intents.

Why to get it

Due to a huge expansion of the usage of sensing devices, esp. for wearable sensing, the problem of the interoperability between different types of sensors has become critical for the success/adoption of modern eHealth (esp. mHealth) solutions. Indeed, current solutions for sensing are based on proprietary approaches and specialized APIs, so that the integration of the signals from different sensors is difficult and possible only on the syntax level. The main goal of this Semantic Event Enrichment SE is to enable semantic complex processing of the real-time signals sensed from different types of sensors and to offer this capability to third party applications (such as those developed by SMEs involved in Phase3). Such an approach will support:

 

m)  Sensor Data Collection Service

http://fistarcatalogue.fiware.eng.it/enablers/sensor-data-collection-service

The Sensor Data Collection Service SE is the gateway between FI-Star SEs and health device. It supports a set of interfaces to manage these devices and to collect data measured/scanned by these sensors. The current version is compatible with Android-based devices and thus it makes use of Android libraries.

Why to get it

The Sensor Data Collection Service SE provides an abstraction layer to interconnect to various health devices through NGSI-9/10 like and ETSI M2M interfaces, which are adapted by both FI-Star and FI-Ware projects. Different (communication) technologies can be used to feed up data to the Protocol Adapter. Each of these technologies is integrated through the means of a Device Adapter. A Device Adapter provides the Protocol Adapter with basic functionalities related to a specific communication technology. The APIs are based on Android Intents for upper levels towards applications and FI-STAR Notification Service, the interface towards the Protocol adapter can either be based on Android Intents or AIDL specified service. The beta version is interworking with the Protocol Adapter (https://github.com/theIoTLab/ProtocolAdapterManager) to collect data from sensors, manage configuration, activate sensors.

 

n)    Targeting & Profiling Service

http://fistarcatalogue.fiware.eng.it/enablers/targeting-profiling-service

The Targeting & Profiling Service SE provides an administrative GUI and secure REST API for receiving events and processing the events according to user defined rules.

Why to get it

The administrative GUI simplifies the use of the underlying complex event processing engine (CEP), accelerating the application development and event processing . Moreover, the The Targeting & Profiling Service SE provides secure NGSI10 compliant interfaces, providing authentication via the GUI and API authorization based on OAuth2.

 

o)     Time Service SE

http://fistarcatalogue.fiware.eng.it/enablers/time-service-se

The Time Service SE is specified here as a component that enables other modules to use it  and to get accurate time for orchestrating events to be occurred, keep transaction integrity high and maintain authentication and logging features. To this purpose, the Time Service SE synchronises with an official - source time information and makes time and date data available as a service. This time information is distributed over several stages within the FI-STAR Backend Platform and offered upon request to other platform components.

Why to get it

According to the requirements of the FI-STAR there is a need for maintaining accurate and reliable time service as a supported service for other SEs. Specifically, SEs like Real Time Communication Service SE and others will need a Time service in order to synchronize or characterize their interactions in time. The service will highlight advantages such as keeping synchronization of clocks between SEs that could be deployed in different time zone datacenters as well as to offer resolution in services involving deadlines. The SE includes two categories for time synchronization, the Time Service Synchronization for physical machines (including an NTP stratum 1 and 2 servers) and the Time Service Interaction for utilizing RESTFul API solution that uses a custom HTTP scheme to allow communication.

 

p)    Connectivity Service

http://fistarcatalogue.fiware.eng.it/enablers/connectivity-service

The connectivity service SE acts as a mediator between front-end and backend SEs. It supports several interfaces for data transmission based either on HTTP or CoAP protocol with an end-to-end security support. It acts as a proxy between the front-end SEs and the other FI-Star SEs. In case the frontend SE (i.e. deployed in a mobile device) is (intentionally or unintentionally) unreachable, the SE will store the data temporary that can be retrieved once the device is reachable. For managing the connectivity over dedicated wireless access technologies (e.g. selecting cellular network at certain time for certain type/class of traffic), the connectivity service SE can select the appropriate access technology based on received network policy and data priority.

A second functionality is to act a device mangement client acting in the name of the device itself for connectivity monitoring and for managing the attached devices (sensors and actuators).

Beta version brought support for mobile communication, not only WiFi as well as support for HTTPS and CoAP with DTLS. Certificates can be generated and signed by the Security and Privacy SE or using OpenSSL. Please take a look at the documentation from: https://github.com/rbit/pydtls/blob/master/dtls/test/makecerts

Why to get it

The connectivity service is the anchor for all messages interactions between the frontend and backend SEs and core connectivity component. It acts as proxy for HTTP and CoAP messages and interconnect with core network components for mobility management and device reachability. Therefore, it is an extension for FI-Ware S3C GE.

 

q)    Connectivity Service Backend

http://fistarcatalogue.fiware.eng.it/enablers/connectivity-service-backend

The Connectivity Service SE Back-end is to be used by other FI-STAR to send data to the front-end or receive data from the front-end SEs. It allows creation of device informations in the back end and offers a forwarding of this information to the EventService using Events. Its input supports CoAP or HTTP as transports protocols and its output is NGSI9/NGSI10 compliant.

The connectivity service SE acts as a mediator between front-end and backend SEs. It supports several interfaces for data transmission based either on HTTP or CoAP protocol with an end-to-end security support. It acts as a proxy between the front-end SEs and the other FI-Star SEs. In case the frontend SE (i.e. deployed in a mobile device) is (intentionally or unintentionally) unreachable, the SE will store the data temporary that can be retrieved once the device is reachable. For enabling the Connectivity Service SE to request QoS allocation and retrieve device status from an EPC (Evolved Packet Core) based operator core network PCRF (Policy and Charging Rules Function) component, the 3GPP Rx interface is supported.

Why to get it

The Connectivity Service BackEnd is a built-in part of the Connectivity Service. Its simple interface with the Connectivity Service FrontEnd allows management of device informations over HTTP or CoAP, depending on the application choice. The dynamic forwarding of information to the Event Service is a key element to simplify end to end communications. 

The connectivity service is the anchor for all messages interactions between the frontend and backend SEs and core connectivity component. It acts as proxy for HTTP and CoAP messages and interconnect with core network components based on Diameter protocol. Therefore, it is an extension for FI-Ware S3C GE.

 

r)     Device Management

http://fistarcatalogue.fiware.eng.it/enablers/device-management

The Device Management provides interfaces to manage the M2M devices information in general and in the FI-STAR context adressing medical devices. It is developed as a OMA Leightweight M2M Device Management server. The medical devices register to it. Applications can subscribe to device availability and get notified accrdingly. The mentioned operations are part of the OMA Leightweight M2M standard. The transport protocol is Constraint Application Protocol (CoAP), an efficient transport protocol for constrained devices in terms of battery and connection bandwidth, for example.

Why to get it

The component enables an application to be aware of the available medical devices and the information related to their capabilities for example the measurements that they provide.

 

s)     HER

http://fistarcatalogue.fiware.eng.it/enablers/ehr

An Electronic Health Record (EHR) specific enabler for the development of EHR applications. The EHR SE is being implemented as a BACK END API. The EHR SE can be linked with the epSOS SE and the PACs SE.

Why to get it

An electronic health record (EHR), is a systematic collection of electronic health information about an individual patient or population. It is a record in digital format that is theoretically capable of being shared across different health care settings. In some cases this sharing can occur by way of network-connected, enterprise-wide information systems and other information networks or exchanges. EHRs may include a range of data, including demographics, medical history, medication and allergies, immunization status, laboratory test results, radiology images, vital signs, personal statistics like age and weight etc.

The EHR SE will offer the capabilities to provide third party applications (such as those developed by SMEs involved in FI-PPP Phase 3) that include these functionalities as well as the possibility to communicate and exchange data between different health agencies or different departments of the same health agency.

 

t)      epSOS SE

http://fistarcatalogue.fiware.eng.it/enablers/epsos-se

A patient Summary application based on epSOS (www.epsos.eu) for the development of the patient summary epSOS specific enabler. The epSOS SE is being implemented as a BACK END API. The epSOS SE can be linked with the EHR SE.

Why to get it

The “European Patients’ Smart Open Services” epSOS project was initiated in 2008 and at the time it involved a few stakeholders that gradually grew to encompass 25 countries and about 50 beneficiaries. The focus of the project has been to offer safe, secure and high-quality services for exchange of patient summary data and ePrescriptions between European countries, in line with the Directive 2011/24/EU that provides rules for facilitating the access to safe and high-quality cross-border healthcare and promotes cooperation on healthcare between Member States, in full respect of national competencies in organizing and delivering healthcare. More specifically, the Article 14 (2) (b) (i) of the Directive 2011/24/EU has identified an objective for the eHealth Network to draw up guidelines on a non-exhaustive list of data that are to be included in patients’ summaries. These guidelines will follow the preliminary work in the field of eHealth, and in particular from the epSOS pilot that provided a solid and reliable foundation.

The epSOS SE covers the exchange of patient data and implements the BACK-END API. The epSOS SE provides the functionality to develop the client site and the client connector to a local National Contact Point portal as it is defined by the epSOS Large Scale Pilot (LSP) and following the recommendations and guidelines offered by the OpenNCP platform. The patient summary will be supported by the EHR SE.

 

u)    Event Service

http://fistarcatalogue.fiware.eng.it/enablers/event-service

The Event Service SE provides an administrative GUI and secure REST API for NGSI9 and NGSI10 compliant Pub/Sub Services, as for example the Orion Publish/Subscribe Context Broker. Additionally, the SE provides a corresponding XML-RPC API as an extension to the REST API.

Why to get it

The administrative GUI simplifies the use of NGSI9 and NGSI10 compliant Pub/Sub Services, accelerating the application development and event handling. Moreover, the Event Service SE allows to secure NGSI9 and NGSI10 compliant interfaces, providing authentication via the GUI and API authorization based on OAuth2. To support a broader range of applications, the SE provides also an additional XML-RPC API to the NGSI9/10 REST API with the corresponding functionality.

 

v)     EXPOSE

http://fistarcatalogue.fiware.eng.it/enablers/expose

The EXPOSE SE provides pre-processing of real-time data collected from front-end sensors and their conversion to Proton CEP (Complex Event Processing) GE format. REST API provides for patient electronic health record management and configuration of rules to look for. The API also provides for formulating (from the nurse side) and answering (from the patient) side relevant questionnaires whose answers may be used in complex event processing. Two provided use-cases exemplify the SE operation.

Why to get it

You have real-time at the front-end and want to pre-process those for submission to COSMOS Complex Event Processing GE following certain rules and get notification in case of a complex event. The API also allows to formulate questionnaires as well as send/receive and further use respective answers in complex event processing.

 

w)   Fall Risk Evaluation

http://fistarcatalogue.fiware.eng.it/enablers/fall-risk-evaluation

The Fall Risk Evaluation (FRE) Specific Enabler aims at estimating the risk of falling for elderly users and notifying interested parties, including the actor himself, medical professional and carers (depending on their registered interests). The SE targets on specific biological parameters whose fluctuation outside predefined ranges indicates the presence of one or more conditions regarded as falls-risk factors. The upper and lower limit of each variable depends on the physiological features of the user/patient, in combination with a reference interval (standard range). The variables are vital signs including blood pressure, heart rate and rhythm, and body temperature, and two more measurements, blood oxygen saturation and blood glucose. Each of these is assessed in real time in pre-specified settings.

Why to get it

The Fall Risk Evaluation SE allows:

 

x)     GEO-FENCING

http://fistarcatalogue.fiware.eng.it/enablers/geo-fencing

Geofencing SE enables to enforce unified access control policies decoupling the policicy decision making from the application logic development. On one hand it includes the posibility to constraint access to any resource based on attributes where most significant is indoor/outdoor location of users and/or resources. It covers RBAC and ABAC requirements. On the other hand it enables to avoid applications recodification when any policy element is changed.

By means of integration and usability from developers point of view, simple REST interface call with some few parameters as authenticated_user_id, action and target_resource, gets granting or denying of permissions based on unified access control policy. It is fully integrated in OAuth schemas for authentication purposes.

Fine grained policies may require gathering some additional external data, performed transparently for the user and developer through internal data locators and retrievers.

This fine grained policies are edited through an intuitive and userfriednly graphical user interface, including the zonification and fence definitions for location based access control features.

Why to get it

User and resources indoor localization based fine grained access control policies enforcement is a must when Healthcare applications plan to exchange any sensible data in any process.

 

y)     Health Questionnaire Service

http://fistarcatalogue.fiware.eng.it/enablers/health-questionnaire-service

The Health questionnaire SE allows:.

The Health Questionnaire SE includes the following elements:

Why to get it

Questionnaire are widely used in the healthcare sector. The Health Questionnaire SE makes easier the creation of simple assessment and monitoring questionnaires.