FOR REMOTE MONITORING PATIENT S HEALTH STATE

Transcription

1 THE CONCEPT OF A PLATFORM FOR REMOTE MONITORING PATIENT S HEALTH STATE Authors: Marcos Da Silveira Nicolas Guelfi

2 Introduction 2 Objectives: The identification of needs from medical sector in order to implement home monitoring services The selection of a set of technologies that can be used to implement these services The definition of an architecture that promote interoperability between medical applications The implementation of a case study that validate the proposed p concepts

3 General Requirements 3 Composed of loose coupling components Use standards to implement communication Manage Security and Safety Operate synchronously or asynchronously Operate in a heterogeneous communication environment

4 Architecture 4 Network Architecture (Infrastructure) How to connect different stakeholders? How to find EHR and services providers? Business Framework How to proceed to design new services? How to establish collaboration? Service Architecture How to coordinate process execution? How to interface resources and services?

5 Network Architecture 5 Local Component Service Performs Resource Sends/Receives MSG Conform Policies

6 Network Architecture 6 EHR-Locator H-Center Service-Locator Service Resource MSG Policies To/from HL7 Internet

7 Choreography: Describes how each component will CDL contribute to execute the service. WS-Policy, Describes general rules to perform WSa service and Specification take into account some customizations (requested by the user). Workflow: Describes the workflow that implements BPEL the service. Business Framework Security Users Business Layer Business Collaboration Mgt ext Service Registry Level 1 Publish the properties (interface, status, etc.) of tasks WSDL, that are available UML in the Level 3 system. Business Business Model Model Level 2 Control Model Application Layer Control Model int Service Registry Level 4 7 Mainframe Technologies Progiciel DB Level 5

8 Service Architecture 8 Users Business Layer Business Collaboration Mgt Business Model Business Model Control Model Control Model Web Service Application Layer int Service Registry HL7 WS-Sec. Java Messages Composition HL7 CXF Technologies DB Middleware (Mule)

9 Message Composition 9 Web services Intranet HL7 adapter BPEL engine WS Security Security CXF Mule Middleware Java VM SOAP Internet

10 The case study 10 Monitoring System (MSY) Home Monitoring Center (HMC) Medical Terminal (MT)

11 Scenario Details 11 MSY 8h Start Stop Comment Alarm 17h ADSL+VPN HMC Security Mgt Store Data Transform Data Process Net Configuration Install Agents Visualize Set Journey Diagnosis Comment Configure RS232 XML Configuration Messages XML 18h Measures Profile Other Configurations: 2 nd Opinion: on (authorized) Goal: Medication test Net: Account, IP Connection: ADSL Incoming/Outgoing: MSY ID Transmission i time: 6pm Hw interface: start off, end on Sw interface: start on, end on Security: VPN MT Journey: Measures: 2x a day (8am/5pm) Variance: 30min Signals: Weight, ECG Alarm: on

12 Interoperability 12 Components must communicate using a well-know protocol Medical and Patient data are transmitted throughout an EAI (Mule) Avoid reinventing the wheel and use international standards We are using Username Token authentication, X.509 Encription and Time-stamping

13 Mule 13 Mule is lightweight java framework It implements several transport protocols: ftp, http, smtp, web services and others Provides a uniform configuration methodology using xml files To change the transport its is not necessary to touch the implementation Acts as a high level backbone

14 Mule 14 Service Implementation Inbound CXF Router Transformers Outbound SMTP Router

15 Database Representation 15

16 Services Diagram 16 Custumer Web-Service Platform Services

17 Services Diagram The Keys 17 Every secure connection must share a key-par The public key is represented by an open Padlock and the private by a key.

18 Future Works 18 Implementation of Registries Integration t ti of BPEL and CDL Monitoring workflows Secure BPEL, constraints description Search Engine with fault tolerance Business B i x Application = Control Model Ontology Automatic Re-configuration

19 19 Diagnosis? Second opinions? Marcos Da Silveira: