M2M enablement in pla-orm- centric ehealth service delivery: the FI- STAR approach

Transcription

1 M2M enablement in pla-orm- centric ehealth service delivery: the FI- STAR approach Dr. Stefan Covaci, Technische Universität Berlin Andreea Ancuta Corici, Fraunhofer FOKUS

2 A FI- PPP Use- Case Biggest FI- PPP Phase II Use- Case Project: 46 Partners: Healthcare InsOtuOons & Providers, & Pla-orm Operators, Technology Providers, Academia, R&D NGOs, Legal, StandardisaOon,. 13 Million EURO EC funding (16,5 Million EURO costs) Answer the quesoon: Is the social- technical alignment required by the healthcare sector realisable by FI- WARE technology and if yes how and with which efficiency gains? i.e. evaluate applicability of FI technology in ehealth. Berlin, Nov 13 th

3 FI- STAR delivers A robust technology framework based on FI- WARE Generic Enablers (GEs) FI- STAR pla-orm is a specialised Core Pla-orm Instance using GEs and SEs (Specific Enablers) Development, Test and validaoon framework for enablers and Apps Introduces paradigm shi2 So2ware to Data, considering deployment requirements of the customer Berlin, Nov 13 th

4 Requirements Trends in Healthcare Health / Insurance Provider Requirements User / Data Owner Requirements Across OECD countries, health expenditure has grown by 4% annually over the past decade, compared with 1.6% for GDP growth More and more paoents will be treated or cared for outside hospitals, in their homes, GP pracoces, nursing homes, day surgeries, day clinics, day rehabilitaoon, and over the Internet Reduce costs OpOmise healthcare decision making processes OpOmise sourcing (e.g. cloud, outsourcing) Engage cared for / insured in proac<ve healthcare and wellness Behaviour change capabilioes Ubiquitous Access anyome and from everywhere (online, off- line, mobile) Flexible sharing with different providers / sources interoperability Data portability Informa<on accountability CerOficaOon (legal, ethical, technological) Monitoring Have control of own data: storage and access Storage by a trusted organisaoon offering data / access informaoon accountability measures Secure storage in a unique place Accessible anyome and from everywhere (online and off- line, mobile) Flexible sharing with different processors / sources Data portability Monitoring Access Social interac<ons Avoid Past failures of new technology User Centricity: Other Stakeholders Requirements Developers: Secure development environment Test and CerOficaOon Monitoring DocumentaOon Sample Code Social InteracOons Auditors: Berlin, Nov 13 th

5 categories 5

6 Architecture Overview 6

7 Relevant achievements Design of the Specific Enablers (5 in the Front- End and 10 in the back- End) is based on Generic Enablers by appropriately enhancing their funcoonality 14 GEs have been idenofied and are used The license under which the FI- STAR Specific Enablers will be released is depending on the license of the Generic Enablers used AddiOonal Specific Enablers are added as a result of the outcome of the FI- STAR open call E.g. SemanOc Enrichment, Geo- fencing, PseudonymisaOon, EHR gateway, Berlin, Nov 13 th

8 Development & IntegraOon Aspects For each SE component Specific Use- Cases have been elaborated (incl. administraoon) Interfaces have been defined (incl. admin ) Component diagrams have been created Reference ImplementaOon(s) has been developed Unit tests have been developed DocumentaOon and sample code for app developers IntegraOon: IntegraOon tests Chains of SE Use- Cases / Pipes Berlin, Nov 13 th

9 Example Event service Admin Interfaces Publish Interfaces - REST - XML- RPC Event Broker Event SE Subscribe Interfaces - REST - XML- RPC REST Event DB Context Broker GE 9

10 Example - TargeOng and Profiling REST interfaces - provided - required Event Analysis Management/Administration/ Visualization Targeting and Profiling SE Big Data Analysis GE Complex Event Processing GE OAuth 2.0 Security & Privacy SE 10

11 FI- Star Architecture ApplicaOon Frontend Pla-orm TargeOng & Profiling SE Backend Pla-orm Real- Ome com. Provider Zone ApplicaOon 3 rd Party or legacy NoOficaOon SE Security & Privacy Event MediaOon PaOent Local storage Local Data Processing ConnecOvity FE ConnecOvity BE Device Management Medical personnel Legacy System Protocol Adapter Sensor Data CollecOon SE Monitoring Time Health QuesOonnaire 11

12 Sensor Data CollecOon SE Features: Collect Data from sensor A Device Adapter for each connected sensors Publish list of sensors to Device Management Server Based on OMA Lightweight M2M device management protocol Manage white/black list of devices paired with Smart Phone Back-end App can dynamically enable/disable sensors and properties to measure FOKUS LWM2M extension Design partially from FI-WARE, implementation from OpenMTC 12

13 ConnecOvity SE Supported Standards: ETSI M2M Front End Connectivity using retargeting to reach Back End Connectivity OMA NGSI Event based enabled to increase the flexibility Supported Transport Protocols: CoAP, CoAP with DTLS Based on UDP, energy-efficient, not overloading the Back End Connectivity HTTP, HTTPS Certificate validation Support for Online Certificate Status Protocol (OCSP) RFC 2560 Better than using Certificate Revocation List (CRL) Profile No storage needed for CRL, implicit timestamp checking 13

14 ConnecOvity SE (2) Connectivity Policies Supports Handovers Static: from configuration file: Access Networks and appropriate Request Category Dynamic: Application running on top of the Device Management Server (FOKUS extension of LWM2M) Local Connectivity Monitoring Front End Application subscribe for IP change using ETSI M2M LWM2M Connectivity Monitoring Management Object IPAddress Front End Application gets notified when IP changes Supported OS Linux, Ubuntu, Android Design partially from FI-STAR, implementation from OpenMTC 14

15 Device Management SE Supported Standards: OMA LW M2M v1.0 Based on CoAP (Constraint Application Protocol) RFC 7252 Connectivity Monitoring, Location, ehealth Connectivity Management Web GUI and API for Sensor and Properties Enable/Disable Currently integrated in OpenMTC and interfaced with OpenSDNCore 15

16 Device Management (2) Comparison with other Device Management protocols OMA DM OMA LW M2M Transport HTTP, WSP and OBEX bindings CoAP over UDP and SMS bindings CommunicaOon Model Data Model Message Overhead Complex, OMA DM protocol packages DM tree with open very complex Management Objects. Server needs to know management tree structure of each device before it can manage HTTP+XML Messages (100s of bytes) ApplicaOon Data? No Yes Device Availability Mobile phones, tablets and M2M gateways RegistraOon followed by simple CoAP GET, PUT, POST, DELETE Flat, simple objects with uniform URI across devices CoAP + binary encoded TLV or JSON (10s of bytes) Constrained local wireless or M2M Cellular based 16

17 InteracOon Flow ApplicaOon Frontend Pla-orm TargeOng & Profiling SE Backend Pla-orm Real- Ome com. Provider Zone ApplicaOon 3 rd Party or legacy NoOficaOon SE Security & Privacy Event MediaOon PaOent Local storage Local Data Processing ConnecOvity FE ConnecOvity BE Device Management Medical personnel Protocol Adapter Sensor Data CollecOon SE Device Management Monitoring based on OMA lightweight M2M Time Health QuesOonnaire Legacy System 17

18 InteracOon Flow ApplicaOon Frontend Pla-orm TargeOng & Profiling SE Backend Pla-orm Real- Ome com. Provider Zone ApplicaOon 3 rd Party or legacy NoOficaOon SE Security & Privacy Event MediaOon PaOent Local storage Local Data Processing ConnecOvity FE ConnecOvity BE Device Management Medical personnel Legacy System Protocol Adapter Sensor Data CollecOon SE Local Monitoring data processing and rendering Time Health QuesOonnaire 18

19 InteracOon Flow ApplicaOon Frontend Pla-orm TargeOng & Profiling SE Backend Pla-orm Real- Ome com. Provider Zone ApplicaOon 3 rd Party or legacy NoOficaOon SE Security & Privacy Event MediaOon PaOent Local storage Local Data Processing ConnecOvity FE ConnecOvity BE Device Management Medical personnel Protocol Adapter Sensor Data CollecOon SE Secure and real- Monitoring Ome data transmission to network app Time Health QuesOonnaire Legacy System 19

20 FI-STAR executes seven early trials across Europe. Trials validate the FI-PPP core platform and introduce ultra-light mobile interactive applications for user functionality and a secure service access and data sharing provided by the PaaS operator. Osakidetza, in Bilbao, Spain Developing Interactive Future Internet based services for people with Mental Health problems. Improve access to care and apply Core Platform to other already existing services successively. Medichem, in Leeds, UK To implement the 2-D Pharmacy bar-coding, offering a real time reverse supply chain model to prevent error and counterfeiting and create interfaces to additional third part services. CUP 2000, in Bologna, Italy Developing healthcare networks to allow healthcare professionals to share data in realtime, allowing citizens to access healthcare data anytime, anywhere. Early Trials Berlin, Nov 13 th

21 Early Trials Norwegian Centre for Integrated Care and Telemedicine in Tromsø, Norway To improve the existing telehealth network for Diabetes patients, aiming at the development of smart phone based multi-channeling, allowing for streaming of different data at the same time (sensor data and audio and video) John Paul II Hospital, in Krakow, Poland Designing interactive facilities for cancer patients, using life monitoring sensors, tablets, cameras, web based, treatment diary, mobile and video conferencing client. University of Medicine and Pharmacy Carol Davila in Bucharest, Romania Online Cardiology service for people with heart failure by testing software, applications and internet-monitoring. Improvement of physical training and also the improvement in secondary prevention programs. Klinikum Rechts der Isar, Technical University, in Munich, Germany Implementation of the virtualization of operating theatres to develop methodologies for minimal invasive operating theatre environments with real time data integration for monitoring, to reduce error rates.

22 Contacts FI- STAR project coordinator Anastasius Gavras, Eurescom GmbH FI- STAR technical director Stefan Covaci, Technische Universität Berlin FI- STAR medical director Christoph Thuemmler, Edinburgh Napier University Project website: hup:// star.eu Project blog: hup://fistarblog.com/ YouTube channel: hup:// E- mail contact: star.eu This project has received funding from the European Union s Seventh Framework Programme for research, technological development and demonstra?on under grant agreement no