1 / 19

Interoperability Capability Guidelines

Interoperability Capability Guidelines. Key points from the Australian eHealth Interoperability Framework HL7 ARB Presentation Zoran Milosevic, NEHTA, July 2012. Positioning interoperability. Interoperability practice. Integration practice. Common Architecture Practices. Closed world.

regina-clements
Download Presentation

Interoperability Capability Guidelines

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. Interoperability Capability Guidelines Key points from the Australian eHealth Interoperability Framework HL7 ARB Presentation Zoran Milosevic, NEHTA, July 2012

  2. Positioning interoperability Interoperability practice Integration practice Common Architecture Practices Closed world Open world Viewpoints Principles Close coupling Loose coupling Method Patterns Traceability Bespoke solutions Standards - conformance Governance Technical focus Federation Maturity Single time point Multiple time points Enterprise Architecture Practices Rationalization Flexibility Integration points 1, 2, 3 … Interoperability timeline

  3. Architecture vs. Interoperability • Interoperability at its most challenging is process of alignment of multiple architectures over time in the midst of multiple governance contexts • Sound architecture is a precondition for sound interoperability • Interoperability is to architecture as acceleration is to speed • Interoperability supports architecture in transit

  4. Problem : Interoperability Capability • Establish guidelines and best practices for • Measuring interoperability levels • Continuous improving of interoperability capability • Targets • eHealth specification and systems • Organisations developing/participating in eHealth solutions

  5. Solution approach • Leverage CMMI Framework • Use existing structuring approach • Tailor it for the purpose of interoperability • Use existing concepts and add new ones as required • Ensure compliance • Essentially a new CMMI constellation • In addition to Development, Service and Acquisition constellations

  6. CMMI – Continuous representation* * See http://www.sei.cmu.edu/library/abstracts/reports/10tr033.cfm

  7. CMMI – Staged representation

  8. Categorising capability: approaches eHealthSystem (artifacts) Organisation (processes) Organisation (processes) ML5 Process Area 1 Process Area 2 L 4 ML4 CL3 L 3 ML3 CL2 ML2 L 2 CL1 ML1 L 1 Specific Goals Specific Goals Maturity Levels Capability Levels Existing approaches Predefined sets Organisation specific (Walker and LCIM) CMMI Continuous CMMI Staged

  9. Concept relationship Maturity Level GG3: CL3 - Defined Equivalent staging Generic Goals GG2: CL2 - Managed GG1: CL1 - Performed Principles CL0 - Incomplete determine Characterised by Process Areas Capability Level identify 1, …* has Artefact (Work Product) Specific Goals Attributes 1, …* qualify as Interoperability Goals Practices produced by realise To be defined and agreed

  10. Approach • Process areas are needed • group related specific interoperability goals • Principles useful in identifying key process areas • Governance • Policy compliance • Service orientation • Conformity Assurance • Common Semantics • Technical interoeprability

  11. Multiplicity • Governance contexts • Service types • Technology options • Points in time • Necessary vs sufficient conditions • Architecture vs interoperability

  12. Governance

  13. Policy Compliance

  14. Collaboration and stakeholders

  15. Service Orientation

  16. Conformity Assurance

  17. Common Semantics

  18. Technical Interoperability

  19. Next steps • Agree Interoperability Process Areas • vs Architecture Process • For each area agree on • Specific goals • Practices • Work products

More Related