2009-dec-10 Architectuur en HL7


Published on

Waarom Architectuur, waarom Architectuur in HL7 en SAEAF

Published in: Health & Medicine, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

2009-dec-10 Architectuur en HL7

  1. 1. Architectuur en HL7 Nationaal Standaardisatiecongres, 10-dec-2009 University Medical Center Groningen, Netherlands Michael van der Zel HIT-Architect
  2. 2. Me UMCG – HIT Architect Results 4 Care – DCM MDA Tooling & ISO Standaard HL7 RIMBAA Co-Chair Parelsnoer Expertgroep Klinische Bouwstenen Michael van der Zel 10-dec-2009
  3. 3. Michael van der Zel 10-dec-2009
  4. 4. Wat? Architectuur gaat over kaders Inzicht, overzicht en samenhang Architectuur “tool” binnen HL7 Michael van der Zel 10-dec-2009
  5. 5. Michael van der Zel 10-dec-2009
  6. 6. http://softwareindustrialization.com/content/binary/design.jpg Michael van der Zel 10-dec-2009
  7. 7. Chaos Michael van der Zel 10-dec-2009
  8. 8. Gartner: The new enterprise architecture Align your architecture with your business goals Create order from chaos Kaders Keuzes Matrixes Michael van der Zel 10-dec-2009
  9. 9. Project Enterprise Domain Enterprise = Stad Domain = Wijk Michael van der Zel 10-dec-2009 Project = Straat
  10. 10. Efficient Mooi Praktisch Michael van der Zel 10-dec-2009
  11. 11. Michael van der Zel 10-dec-2009
  12. 12. Een Matrix Why? Enterprise & Proces What? The Architect Informatie How? Dynamisch Where? Techniek Project A Project B Project C De projectleider Michael van der Zel 10-dec-2009
  13. 13. HL7 SOA-Aware Enterprise Architecture Executive Summary HITSP October 28, 2008 10-12-09 12:17
  14. 14. Preface A few notes … • The HL7 Services Aware Enterprise Architecture Framework (SAEAF, pronounced “SAFE”) was commissioned to find the language, processes, and artifacts to talk about a Enterprise Architecture appropriate for an SDO using Services as a backbone concept. • Services (and SOA) are not technology per se. Rather, they are a framework for approaching the problem of how to design distributed capabilities (information and functionality sharing). They are not equivalent to Web Services Page 14
  15. 15. The Goal of the HL7 Enterprise Architecture Working Interoperability The following are required for any interoperability: Definition of Information to be exchanged Definition of Functions by which the information is exchanged Mappings to Real World Events and Business Processes Reference Terminology / Language for understanding these things Engineering / Technology Bindings to deliver these things HL7 and its Standardized Specifications should deliver these things for stakeholders so that actual Implementations may be built Page 15
  16. 16. The SAEAF (Part 2) HL7, MDA, CSI, SOA, and Distributed Systems Architecture • The intersection of HL7, MDA, Distributed Systems Architecture, SOA, and CSI provide a goal, the artifacts, portions of a methodology, and the framework for defining robust, durable business-oriented constructs that provide extensibility, reuse, and governance. Health Level 7 Service Oriented Architecture Computable Semantic Interoperability Reference Model For Open Distributed Processing Model Driven Architecture You are here (Vous êtes ici) Page 16
  17. 17. The SAEAF (Part 3) RM-ODP Multi-Dimensional Specification Pattern from the 5 Viewpoints Enterprise View: concerned with the purpose, scope and policies governing the activities of the specified system within the Why? organization of which it is a part Information View: concerned with the kinds of information handled by the system and constraints on the use and interpretation of that information; What? Computational View: concerned with the functional decomposition of the system into a set of objects that interact at interfaces – enabling system distribution; How? Engineering View: concerned with the infrastructure required to, and distribution of, the computing resources defined in the Computational View. Where? Technology View: concerned with the choice of technology to support system distribution True? ISO Standard (RM – ODP, ISO/IEC IS 10746 | ITU-T X.900 ) Page 17
  18. 18. The SAEAF (Part 4) The HL7 Specification Stack – Detail of the The Specification and Conformance Patterns Specification Enterprise / Information Computational Engineering Conformance Business Viewpoint Viewpoint Viewpoint Level Viewpoint Reference EHR-FM, RIM, Structured EHR-FM - Reference Vocab, ADTs Clinical Statements Analysis Business DIM Dynamic N/A Blueprint Context, Blueprint, Reference Functional Context Profile(s) Conceptual Business CIM, LIM Dynamic Model, N/A Platform Design Governance Interface Independent Specification Implementable N/A Transforms, Orchestration, Execution Platform Bound Design Schema Interface Context, Realization Specification Bindings, Deployment Model Page 18
  19. 19. SAEAF summary “ SAEAF is, in the end, intended to be used comprehensively across all of the Work Groups of HL7 to create standards that either build on or further enhance Working Interoperability between healthcare, clinical research, and life science systems, regardless of the Interoperability Paradigm used by these systems to exchange information and/or coordinate behaviors. ” Michael van der Zel 10-dec-2009
  20. 20. Samenvatting Inzicht, overzicht en samenhang creëren en borgen door middel van matrixen, en taal, en .. Architectuur gaat over kaders op 3 nivo's; enterprise, domein en project SAEAF is voor HL7 “Architectuur tooling” Michael van der Zel 10-dec-2009
  21. 21. SAEAF Info Training <http://www.hl7.org/events/ trainingandcertification.cfm> Motorcycle guy <http://motorcycleguy.blogspot.com/ 2009/09/demystifying-saeafmaybe.html> SAEAF Wiki <http://wiki.hl7.org/index.php?title=SAEAF> Hitchhikers Guide to SAEAF Michael van der Zel 10-dec-2009
  22. 22. Bedankt voor de aandacht Michael van der Zel 10-dec-2009