Architectuur en HL7
Transcript of Architectuur en HL7
University Medical Center Groningen, Netherlands
Architectuur en HL7Nationaal Standaardisatiecongres, 10-dec-2009
Michael van der ZelHIT-Architect
Me
� UMCG – HIT Architect
Results 4 Care – DCM MDA Tooling & ISO Standaard� Results 4 Care – DCM MDA Tooling & ISO Standaard
� HL7 RIMBAA Co-Chair
� Parelsnoer Expertgroep Klinische Bouwstenen
Michael van der Zel 10-dec-2009
Wat?
� Architectuur gaat over kaders
Inzicht, overzicht en samenhang� Inzicht, overzicht en samenhang
� Architectuur “tool” binnen HL7
Michael van der Zel 10-dec-2009
Gartner: The new enterprise
architecture
� Align your architecture with your business goals
Create order from chaos� Create order from chaos
� Kaders
� Keuzes
� Matrixes
Michael van der Zel 10-dec-2009
EnterpriseProject
Domain
Michael van der Zel 10-dec-2009
Enterprise = Stad
Domain = Wijk
Project = Straat
EfficientEfficient MooiMooiEfficientEfficient MooiMooi
Michael van der Zel 10-dec-2009
PraktischPraktisch
Een Matrix
Why?
Enterprise
& Proces& Proces
What?
Informatie
How?
Dynamisch
Where?
The Architect
Michael van der Zel 10-dec-2009
Project A
Where?
Techniek
Project B Project C
De projectleider
HL7 SOA-Aware Enterprise ArchitectureHL7 SOA-Aware Enterprise Architecture
Executive Summary
HITSP
10-12-09 12:17
HITSP
October 28, 2008
PrefaceA few notes …
• The HL7 Services Aware Enterprise Architecture Framework (SAEAF, pronounced “SAFE”) was commissioned to find the language, processes, and 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.
Page 14
• 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 n ot equivalent to Web Services
The Goal of the HL7 Enterprise ArchitectureWorking Interoperability
The following are required for any interoperability:
� Definition of Information to be exchanged � 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
Page 15
HL7 and its Standardized Specifications should deliver these things for
stakeholders so that actual Implementations may be built
The SAEAF (Part 2)HL7, MDA, CSI, SOA, and Distributed Systems Archite cture
• 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.governance.
Service Oriented
Architecture
Computable Semantic
Health Level 7
Page 16
You are here (Vous êtes ici)
Reference Model
For Open Distributed
Processing Model Driven
Architecture
Computable Semantic
Interoperability
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 organization of which it is a part
Information View : concerned with the kinds of information
Why?
Information View : concerned with the kinds of information handled by the system and constraints on the use and interpretation of that information;
Computational View : concerned with the functional decomposition of the system into a set of objects thatinteract at interfaces – enabling system distribution;
Engineering View : concerned with the infrastructure required to, and distributionof, the computing resources defined in the Computational View. Where?
How?
What?
Page 17
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 )
The SAEAF (Part 4)The HL7 Specification Stack – Detail of the The Specification and Conformance Patterns
Specification Enterprise /
Business
Viewpoint
Information
Viewpoint
Computational
Viewpoint
Engineering
Viewpoint
Conformance
Level
Reference EHR-FM, RIM, Structured
Vocab, ADTs
EHR-FM - Reference
Clinical
Statements
Vocab, ADTs
Analysis Business
Context,
Reference
Context
DIM Dynamic
Blueprint,
Functional
Profile(s)
N/A Blueprint
Conceptual
Design
Business
Governance
CIM, LIM Dynamic Model,
Interface
N/A Platform
Independent
Page 18
Design Governance Interface
Specification
Independent
Implementable
Design
N/A Transforms,
Schema
Orchestration,
Interface
Realization
Execution
Context,
Specification
Bindings,
Deployment
Model
Platform Bound
SAEAF summary
“ SAEAF is, in the end, intended to be used “ 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
Michael van der Zel 10-dec-2009
systems, regardless of the Interoperability Paradigm
used by these systems to exchange information
and/or coordinate behaviors. ”
Samenvatting
� Inzicht, overzicht en samenhang creëren en borgen
door middel van matrixen, en taal, en ..� 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
SAEAF Info
� Training<http://www.hl7.org/events/<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>
Michael van der Zel 10-dec-2009
� SAEAF Wiki <http://wiki.hl7.org/index.php?title=SAEAF>
� Hitchhikers Guide to SAEAF