23
Mr S.K.Mouleeswaran Mr R.Ashok SSIET Coimbatore

Harnessing and securing cloud in patient health monitoring

Embed Size (px)

Citation preview

Mr S.K.MouleeswaranMr R.Ashok

SSIETCoimbatore

ABSTRACTOpen Cloud Care-remote health monitoringAtlas middleware-scalable integrationService Oriented Architecture-easy

implementationTele monitoringHL7-electronic health record

INTRODUCTIONOnline health monitoringSenior citizens independent of hospitalizationHL7-transfer of electronic medical recordCloud-most scalable and reliable to meet this

demand

Increasing Elderly Population

EXISTING SYSTEM AND STANDARDSCurrent Scenario in patient health

monitoringPDA and Grid Computing platformUbiMon-data storage and processingMobile communication based Health

monitoring systemCommercial brands-viterion™, healthHero™,

GE QuietCare® and CardGuard™, Intel’s HealthGuide and Philips Telestation.

Cont...Communication StandardsISO/IEEE 11073, IEEE P145, Continua

Alliance,the IHE Initiative and Health Level 7 (HL7)

Key objective- real-time plug-and-play interoperability for medical devices

secured exchange of patient related data among multiple applications in real time

Why we need CloudSl. No

Conventional Tele-monitoring Systems

Cloud Computing

1 Huge capital expenditure (CAPEX) required on IT spending

Pay per use model ;OPEX (Operational expenses) only

2 Securing and maintaining the infrastructure is costlier as well as less reliable

Reliability is the integral part of the cloud

3 Need to architect from ground up and is complex in nature

Modular design approach is possible – Scalable with on demand resources availability

Why we need Cloud…4 Complex infrastructure

is setup.No infrastructure is required.

5 Requires large deployment effort; Consumes higher TCO(total cost of ownership)

SLA driven operations (Service level agreement) reduce the deployment efforts in the customer side; Much lesser TCO

6 Customer is responsible for the reliability and the availability of the IT infrastructure

Cloud service provider isolates the non functional requirements from the clients.

Why we need Cloud…7 Bandwidth and storage

limitedInfinite elastic scalability of storage and bandwidth

8 Bringing all the health care institutions in one platform is complex and manual

Automatic usage metering simplifies the integration of different health care providers under one roof

9 Interoperability support is complex

Interoperability support for hybrid environments are possible

10 Clients need to maintain the separate IT team to implement all the features and security

IT features and services and abstracted and encapsulated from the clients; Clients focus on what they do – monitoring the patient health, leaving the IT hiccups to the cloud provider.

Easy Migration to CloudHarvesting under CloudStep 1: Conduct the cloud migration assessmentStep 2: Isolate the dependenciesStep 3: Map the messaging and environmentStep 4: Re-architect and implement the lost

functionalitiesStep 5: Leverage cloud functionalities and

featuresStep 6: Test the migrationStep 7: Iterate and Optimize

Easy Migration to Cloud

PROPOSED ARCHITECTURERequirementsPrivacy protection, legal requirements (such as HIPAA),data accessibility system usability.

Front End

Back End

ComponentsSystem architecture-componentsAtlas middleware- expandable network

oriented middleware Device Kit- device interfacing via IP,

Bluetooth, file, URL, and RS-232 Serial Port ,OHF

DDL: integrates blood pressure monitoring system and GPS enabled instruments.

Components…OSGi- supports service-oriented

architecture, efficient search and deployment of the multiple cloud applications

OSGI4C: interface between OSGI and cloud applications using the support of P2P services such as JXTA.

Business process support bundles- patient registration, reports view, HR management for hospitals, scheduling and time keeping.

Components…Core applications bundles Patient EHR storage and management EHR access management workflow management

procedure monitoring services

SECURING THE SYSTEMMandate on EHR SecurityIntegrity- Data shall not be modified in an

unauthorized mannerAvailability- Data is readily accessible upon

demand by an authorized personal. Confidentiality- Data or information is not

given to unauthorized users or applications.

Cont…Cloud Security Infrastructure (CSI)Security management -Intrusion detection -Authorization -Authentication -Anti virus management -Cryptographic key management -User managementBinding security -Binding protocols- IIOP and SOAPPolicy management- The HL7 standard describes

a simple way for managing policies(scenario driven approach)

CONCLUSION Cloud architecture for remote patient health

monitoringArchitecture is an information system based

on service oriented architecture with HL7 policy manager

FUTURE SCOPEIndividual security components can be

investigated

THANK YOU

QUERIES???