27
Connected Health Reference Architecture Shiroshica Kulatilake Architect, Solutions Architecture WSO2

Connected Health Reference Architecture

  • Upload
    wso2

  • View
    1.097

  • Download
    1

Embed Size (px)

Citation preview

Connected Health Reference

Architecture

Shiroshica KulatilakeArchitect, Solutions Architecture

WSO2

Agenda

An overview of Connected Health

Towards building a Connected Health architecture

Reference Architecture

Demo

Overview

Connected Health as a concept

What drives Connected Health

Governments

Citizens

Healthcare organizations

Health insurance organizations

World health care institutions

Research entities / Universities

Connected health vision

Building an information sharing ecosystem with all

connected health care entities

Goals in healthcare business

Providing the best possible service through accurate and timely

information sources

Decrease latencies in connected services

Reduce manual executions to reduce human errors (i.e data entry etc.)

High availability of medical information

Intelligence via information sharing

Big data analytics for healthcare research

The business architecture

healthcare cloud

Integrated healthcare ecosystem

Building blocks for Connected Health

Technology landscape in healthcare

Heterogeneous devices / applications / data formats /

protocols (i.e hospital information system)

heterogenous integrations in a hospital

Devices & Services

Classic use-case where devices and services

connects to a private cloud

Protocols & Data formats

HL7 (v2 / v3 / FHIR) over HTTP

HL7 (v2) over MLLP

SOAP / XML over HTTP

REST / JSON over HTTP

Messaging over JMS

XML, CSV over FTP

Custom binary protocols (certain HC devices)

Legacy CORBA based systems

Interoperability

Interoperability issues are solved via a bus architecture in

Health Care Information System (HCIS)

interoperability with healthcare bus architecture bus

Data storage and transformation

In a distributed HCIS data can reside in multiple different locations

Data would be stored in different formats

There would be data which is common across several entities

Some data needs to be consolidated before consumption

Aggregation of data can be a function of data federation and service mediation

Data federation & mediation

data bus

HCSBcloud services

Data accessibility and integrity

Distributed transactions (maintaining the ACID

properties in health data)

Who can access the data

From where the data is accessed

Entitlement policies

Data governance & entitlement

data bus

HCSBcloud services

ide

ntity

& e

ntitle

me

nt b

us

Health events

Admission, discharge and transfer events

Scheduling of surgeries / patient care / lab activity

Readings of healthcare devices (HC telemetries)

Alerts and events of registered patients

Insurance claim management

Disease control and vaccination related alerts

Hospital inventory management

Equipment maintenance alerts

Complex health event processing

HC cloud

co

mp

lex e

ve

nts

pro

ce

sso

r

HCSB

event queue

email / alerts

dashboards

Availability and Scalability

Healthcare PaaS

Elastic scaling on demand

Minimum HA setup

Availability zones and regions

Reference Architecture

The connected reference architecture

data bus

healthcare cloud

HCB

HC API gateway

security

gate

way

event pro

cessor

big

data

analy

tics

event queue

data queue

cloud services

services workflows

The connected reference architecture

data bus

healthcare cloud

HCB

HC API gateway

security

gate

way

event pro

cessor

big

data

analy

tics

event queue

data queue

cloud services

services workflows

external ecosystem

internal ecosystem

WSO2 view on the reference model

data bus

healthcare cloud

HCB

HC API gateway

security

gate

way

event pro

cessor

big

data

analy

tics

event queue

data queue

cloud services

services workflows

Demo

Thank You!