To view recording of this webinar please use the below link: https://wso2.com/library/webinars/2015/02/connected-health-reference-architecture/ The key focus areas of this session are Overview of healthcare IT landscape Standards and protocols widely used in healthcare platforms SOA is healthcare domain Quality of services in healthcare platforms A connected healthcare reference model

1. Connected Health Reference
Architecture
Shiroshica Kulatilake
Architect, Solutions Architecture
WSO2

2. Agenda
An overview of Connected Health
Towards building a Connected Health architecture
Reference Architecture
Demo

3. Overview

4. Connected Health as a concept

5. What drives Connected Health
Governments
Citizens
Healthcare organizations
Health insurance organizations
World health care institutions
Research entities / Universities

6. Connected health vision
Building an information sharing ecosystem with all
connected health care entities

7. 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

8. The business architecture
healthcare cloud
Integrated healthcare ecosystem

9. Building blocks for
Connected Health

10. Technology landscape in healthcare
Heterogeneous devices / applications / data formats /
protocols (i.e hospital information system)
heterogenous integrations in a hospital

11. Devices & Services
Classic use-case where devices and services
connects to a private cloud

12. 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

13. Interoperability
Interoperability issues are solved via a bus architecture in
Health Care Information System (HCIS)
interoperability with healthcare bus architecture bus

14. 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

15. Data federation & mediation
data bus
HCSB
cloud services

16. 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

17. Data governance & entitlement
data bus
HCSB
cloud services
identity&entitlementbus

18. 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

19. Complex health event processing
HC cloud
complexeventsprocessor
HCSB
event queue
email / alerts
dashboards

20. Availability and Scalability
Healthcare PaaS
Elastic scaling on demand
Minimum HA setup
Availability zones and regions

21. Reference Architecture

22. The connected reference architecture
data bus
healthcare cloud
HCB
HC API gateway
securitygateway
eventprocessor
bigdataanalytics
event queue
data queue
cloud services
services workflows

23. The connected reference architecture
data bus
healthcare cloud
HCB
HC API gateway
securitygateway
eventprocessor
bigdataanalytics
event queue
data queue
cloud services
services workflows
external ecosystem
internal ecosystem

24. WSO2 view on the reference model
data bus
healthcare cloud
HCB
HC API gateway
securitygateway
eventprocessor
bigdataanalytics
event queue
data queue
cloud services
services workflows

25. Demo

27. Thank You!