Challenges in Health Care Architectures - Better Connecting Critical Systems Lee Kinsman (soon to...

Post on 11-Jan-2016

213 views 0 download

transcript

Challenges in Health Care Architectures- Better Connecting

Critical SystemsLee Kinsman

(soon to be) Consultant, Chamonix IT Consulting(most previously) Sales Engineer, InterSystems

(but you may know me as) Software IT Architect, IBM

Agenda

•State of Health Care Architecture

•Where does Health want to be?

•Strategies to move Health forward

•How do we get Health there?

•What about security?

•Has anyone done this??

Health can be a real

challenge!Why?

Health is complexHealth is evolving

Health Care industry has grown

Technology evolvedData has evolved

Populations have grownMedical care has advanced

User expectations have risen

The business struggles to adapt and can be reactive

What does the business

want?Easy, instant & appropriate

access to dataSecure solutions

Composite applicationseHealth record

Streamlined processesPaperless/electronic

solutionsSmart device integration

Centralised dataBusiness intelligence

Standards implementation & adherence

What about data?

Data has evolvedData stores have grown

tremendously

Business requires access to data from anywhere

Business Intelligence now has a huge role in Health

This new powerful access to data needs to be

secured

How do we get Health

there? Integration Broker

Leverage and integrate existing systems &

datastoresComposite Applications

Centralised DataData warehousing

Data mining / Business Intelligence

Identity ManagementAuthorisation,

Authentication & Privacy

What is an integration

broker?A centralised broker

handling:Communication

AccessSecurity

This is achieved through using integration servers:

InterSystems EnsembleIBM Websphere Message

BrokerMicrosoft BizTalk

Tibco

What are composite

applications?

Combination of multiple existing systems, services

and/or data into a new application

Good composite applications are available to multiple devices (cross platform)

Web is an ideal platform for composite applications

Good composite applications provide exactly what is

needed

Explain data warehousing

& BI?Very simply, a database

used for reporting

Data is often cleaned and transformed (ie cubes) and made available for Business Intelligence &

Data Mining

The business desires BI to be embedded into their composite applications

Real time versus

traditional stored data?Often buy the time BI is run, data is out of date!

Is it possible to access data realtime without impacting live data?

yes it is!

Business Intelligence

ToolsIBM Cognos

InterSystems DeepSeeMicrosoft SQL Server

Reporting & Analytics ServerOracle Business Intelligence

SuiteSAP Netweaver

etc...

Choose real time embedded BI for use in Health

composite applications

So how to we achieve

all this?Be strategic, not reactive

Develop a solid and appropriate Health

Architecture strategy

Leverage existing frameworks, strategies & standards

3 Examples for today:

IBMInterSystems

Microsoft

IBM Health Strategy

IBM Health Strategy

IBM Health Strategy

InterSystems

CacheEnsembleDeepSee

HealthShareTrackCare

Link: Intersystems

InterSystems

Microsoft’s Connected

Health Framework

A Stable Foundation for Agile Health and Social

Care

Link: Connected Health Framework

Microsoft’s Connected Health Framework

The Vision: “Joined Up” Technical Interoperability • Flexibility and Agility • User Experience and Acceptance • Support for Multiplicity of Platform,Location, Language, Capability and Credentials • Handling Health Data • Identity and Access • Interoperability • Securing the Solution • Scalability and Performance• Availability, Resilience and DisasterRecovery • Realizing the Value of CommonInfrastructure

• Identity Management Services • Authentication and Authorisation

Services

• Service Publication and Discovery

Services

• e-Health Business Services

• Electronic Health Record Services

• Health Domain Services

• Health Registry Services

• Integration Services

• Data Services

• Communication Services

Microsoft’s Connected

Health Framework

Reference Architecture for Health and Social

Care

Microsoft’s Connected Health Framework

What are the common

threads?Integration Broker

Business componentsLoose coupling

ServicesLeverage existing assets

What about resourcing?

Health resources are stretched

Use your resources wisely!

Leverage existing tools, frameworks and

strategiesHave resources working

on tasks to suit their skillset

Use methodologies

What about security?

People are paranoid about their personal data!

Access to sensitive data needs to be restricted

Access to all data needs to be secure

Nehta Nehta develops national e-

health standards and infrastructure requirements for the electronic collection

and secure exchange of health information

This is being adopted across the boards in

Australian Health

Link: Nehta

Use a methodolog

y...appropriate to the solution

AgileRUP

ExtremeScrum...etc

Communicate via modelling:UMLBPEL

...have a plan, follow it, document it, live it

Use architectural

best practice

...Health is an enterprise, always come back to

these principles

ZachmanTOGAF

The Federated Enterprise Architecture

The Gartner Methodology

A good health

architecture should:

Mitigate risk (for systems, staff and patients)

Consider benefits to both patients and staff

Consider security ethicsFacilitate rapid (and

appropriate) sharing of dataLoosely couple systems &

servicesSuit the organisational maturity

and have a growth visionBe agile and responsive to the changing needs of the businessProvide technical connectivity

and interoperability

Has anyone done this?

Consider Health globally for examples

Right now there are many partial examples, eg:

Australia is still getting thereEstonia has implemented

eHealth recordScotland has eHealth recordSydney IVF has implemented

a patient recordLothian (UK) has connected

care for patients....etc

Questions?

Connect with me on LinkedIn

Lee Kinsman