Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Connected Health Reference Architecture

E71c1071861e4f8526d75feb67371bd1?s=47 Nuwan Bandara
October 29, 2014

Connected Health Reference Architecture

A connected reference architecture for healthcare #wso2con14sf

E71c1071861e4f8526d75feb67371bd1?s=128

Nuwan Bandara

October 29, 2014
Tweet

Transcript

  1. Connected Health Reference Architecture Nuwan Bandara Senior Lead, Solutions Architecture

    WSO2
  2. Connected health as a concept

  3. What drives connected health Governments Citizens Healthcare organizations Health insurance

    organizations World health care institutions Research entities / Universities
  4. Connected health vision Building an information sharing ecosystem with all

    connected health care entities
  5. Goals in healthcare business Intelligence via information sharing Decrease latencies

    in connected services Providing the best possible service through accurate and timely information sources Reduce manual executions to reduce human errors (i.e data entry etc.) High availability of medical information Big data analytics for healthcare research
  6. The business architecture healthcare cloud Integrated healthcare ecosystem

  7. Technology landscape in healthcare Heterogeneous devices / applications / data

    formats / protocols (i.e hospital information system) heterogenous integrations in a hospital
  8. Devices & Services Classic use-case where devices and services connects

    to a private cloud
  9. Protocols & Data formats HL7 (v2 / v3 / FHIR)

    over HTTP 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
  10. Interoperability Interoperability issues are solved via a bus architecture in

    Health Care Information System (HCIS) interoperability with healthcare bus architecture
  11. Data federation & mediation In a distributed HCIS data can

    reside in multiple different locations Some data needs to be consolidated before consumption Aggregation of data can be a function of data federation and service mediation
  12. Data federation & mediation data bus HCSB cloud services

  13. Data governance & entitlement Distributed transactions (maintaining the ACID properties

    in health data) Who can access the data From where the data is accessed Entitlement policies
  14. Data governance & entitlement data bus HCSB cloud services identity

    & entitlement bus
  15. Complex health events Readings of healthcare devices (HC telemetries) Alerts

    and events of registered patients Scheduling of surgeries / patient care Insurance claim management Disease control and vaccination related alerts Hospital inventory management Equipment maintenance alerts
  16. Complex health events HC cloud complex events processor HCSB event

    queue email / alerts dashboards
  17. Availability and scalability Healthcare PaaS Elastic scaling on demand Minimum

    HA setup Availability zones and regions
  18. The connected reference architecture data bus healthcare cloud HCB HC

    API gateway security gateway event processor big data analytics event queue data queue cloud services services workflows
  19. The connected reference architecture data bus healthcare cloud HCB HC

    API gateway security gateway event processor big data analytics event queue data queue cloud services services workflows external ecosystem internal ecosystem
  20. WSO2 view on the reference model data bus healthcare cloud

    HCB HC API gateway security gateway event processor big data analytics event queue data queue cloud services services workflows
  21. // Questions ? Thank You!