1 / 31

Challenges in Health Care Architectures - Better Connecting Critical Systems

Challenges in Health Care Architectures - Better Connecting Critical Systems. Lee 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

leala
Télécharger la présentation

Challenges in Health Care Architectures - Better Connecting Critical Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Challenges in Health Care Architectures- Better Connecting Critical Systems • Lee Kinsman • (soon to be) Consultant, Chamonix IT Consulting • (most previously) Sales Engineer, InterSystems • (but you may know me as) Software IT Architect, IBM

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

  3. Health can be a real challenge! • Why? • Health is complex • Health is evolving • Health Care industry has grown • Technology evolved • Data has evolved • Populations have grown • Medical care has advanced • User expectations have risen • The business struggles to adapt and can be reactive

  4. What does the business want? • Easy, instant & appropriate access to data • Secure solutions • Composite applications • eHealth record • Streamlined processes • Paperless/electronic solutions • Smart device integration • Centralised data • Business intelligence • Standards implementation & adherence

  5. What about data? • Data has evolved • Data 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

  6. How do we get Health there? • Integration Broker • Leverage and integrate existing systems & datastores • Composite Applications • Centralised Data • Data warehousing • Data mining / Business Intelligence • Identity Management • Authorisation, Authentication & Privacy

  7. What is an integration broker? • A centralised broker handling: • Communication • Access • Security • This is achieved through using integration servers: • InterSystems Ensemble • IBM Websphere Message Broker • Microsoft BizTalk • Tibco

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

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

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

  11. Business Intelligence Tools • IBM Cognos • InterSystems DeepSee • Microsoft SQL Server Reporting & Analytics Server • Oracle Business Intelligence Suite • SAP Netweaver • etc... • Choose real time embedded BI for use in Health composite applications

  12. 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: • IBM • InterSystems • Microsoft

  13. IBM Health Strategy Link: IBM Health Strategy Launch

  14. IBM Health Strategy

  15. IBM Health Strategy

  16. IBM Health Strategy

  17. InterSystems • Cache • Ensemble • DeepSee • HealthShare • TrackCare • Link: Intersystems

  18. InterSystems

  19. Microsoft’s Connected Health Framework • A Stable Foundation for Agile Health and Social Care • Link: Connected Health Framework

  20. Microsoft’s Connected Health Framework The Vision: “Joined Up” Technical Interoperability • 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 • 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 Disaster • Recovery • Realizing the Value of Common • Infrastructure

  21. Microsoft’s Connected Health Framework • Reference Architecture for Health and Social Care

  22. Microsoft’s Connected Health Framework

  23. What are the common threads? • Integration Broker • Business components • Loose coupling • Services • Leverage existing assets

  24. What about resourcing? • Health resources are stretched • Use your resources wisely! • Leverage existing tools, frameworks and strategies • Have resources working on tasks to suit their skillset • Use methodologies

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

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

  27. Use a methodology • ...appropriate to the solution • Agile • RUP • Extreme • Scrum • ...etc • Communicate via modelling: • UML • BPEL • ...have a plan, follow it, document it, live it

  28. Use architectural best practice • ...Health is an enterprise, always come back to these principles • Zachman • TOGAF • The Federated Enterprise Architecture • The Gartner Methodology

  29. A good health architecture should: • Mitigate risk (for systems, staff and patients) • Consider benefits to both patients and staff • Consider security ethics • Facilitate rapid (and appropriate) sharing of data • Loosely couple systems & services • Suit the organisational maturity and have a growth vision • Be agile and responsive to the changing needs of the business • Provide technical connectivity and interoperability

  30. Has anyone done this? • Consider Health globally for examples • Right now there are many partial examples, eg: • Australia is still getting there • Estonia has implemented eHealth record • Scotland has eHealth record • Sydney IVF has implemented a patient record • Lothian (UK) has connected care for patients • ....etc

  31. Questions? Connect with me on LinkedIn Lee Kinsman

More Related