Date post: | 02-Jun-2018 |
Category: |
Documents |
Upload: | health-it-workforce-curriculum-2012 |
View: | 219 times |
Download: | 0 times |
of 31
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
1/31
Enterprise Architecture Models
Networking and Health Information
Exchange
This material Comp9_Unit8 was developed by Duke University, funded by the Department of Health and Human Services,
Office of the National Coordinator for Health Information Technology under Award Number IU24OC000024.
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
2/31
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
3/31
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
4/31
4Health IT Workforce CurriculumVersion 3.0/Spring 2012
Service Oriented Architecture (SOA)
Is an automation of common services
Ensures functional consistency across applications
Minimizes duplication across applications
Reuse Messages can be either payloads in or infrastructure
beneath services
Is an accepted industry best practice
Is used in many key products But interfaces are not exposed
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
5/31
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
6/31
6Health IT Workforce CurriculumVersion 3.0/Spring 2012
Defining SOA
SOA interface is defined in terms of protocolsand functionality
SOA separates functions into distinct services
Accessible over a network Permits users to combine and reuse them in
different applications
Data is passed in a well-defined format
SOA service is self-contained
It makes no calls out of its service package
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
7/31
7Health IT Workforce CurriculumVersion 3.0/Spring 2012
Understanding Services
Services
Perform specific tasks
Have a well-defined interface
May use different implementation languages XML is commonly used for interfacing with SOAservices
SOA contrasts with API approach
Provides flexibility Modules can be updated or exchanged simply
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
8/31
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
9/31
9Health IT Workforce CurriculumVersion 3.0/Spring 2012
Services
XML is typically used to structure data that is
wrapped in a nearly exhaustive description-
container Web Services Description Language (WSDL)
describes the services
Simple Object Application Protocol (SOAP)
describes the communication protocols
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
10/31
10Health IT Workforce CurriculumVersion 3.0/Spring 2012
Usage
SOA permits developers to string together large
chunks of functionality to build applications
Building an application is like taking a set ofblocks, each representing a service, and
stringing them together to create the application
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
11/31
11Health IT Workforce CurriculumVersion 3.0/Spring 2012
SOA relies on service-orientation as its
fundamental design-principle
Simple interface can abstract away theunderlying complexity
Users can access independent services without
knowledge of the services platform
implementation
Value Component
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
12/31
12Health IT Workforce CurriculumVersion 3.0/Spring 2012
What SOA Buys
Can use any Master Patient Index (MPI) withoutre-integrating
Can painlessly integrate data from new clinical
systems into a patients health summary
Heterogeneous systems can be accessed
consistently from an installed application base
Standards support ability to redeploy or
distribute hardware and software withoutbreaking things
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
13/31
13Health IT Workforce CurriculumVersion 3.0/Spring 2012
Requirements to Use SOA
Interoperability between different systems as the
basis for integration between applications on
different platforms through a communication
protocol. Messages are used across channelsfor communication and transfer of data.
Create a federation of resources. Data flow is
established and maintained in a federated
database allowing new functionality developedto reference a common business format for
each data element.
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
14/31
14
Health IT Workforce Curriculum
Version 3.0/Spring 2012
Guiding Principles
Service encapsulation
Service loose coupling
Service contract
Service abstraction Service usability
Service composability
Service autonomy
Service optimization Service discoverability
Service relevance
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
15/31
15
Health IT Workforce Curriculum
Version 3.0/Spring 2012
Service Contract
Header
Name of service
Version Owner
Responsibility assignment
Type (presentation, process, business, data,
integration)
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
16/31
16
Health IT Workforce Curriculum
Version 3.0/Spring 2012
Service Contract (contd)
Functional
What the service accomplishes
Service operations
How to invoke service (SOAP, event triggers)
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
17/31
17
Health IT Workforce Curriculum
Version 3.0/Spring 2012
Service Contract (contd)
Non-Functional
Security constraints
Quality of service Translational
Service level agreement
Semantics Process
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
18/31
18
Health IT Workforce Curriculum
Version 3.0/Spring 2012
Enterprise Architecture (EA)
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.
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
19/31
5 Viewpoints to an EA
Enterprise ViewWhy?
Information ViewWhat?
Computational ViewHow? Engineering ViewWhere?
Technology ViewTrue?
19
Health IT Workforce Curriculum
Version 3.0/Spring 2012
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
20/31
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
21/31
21
Health IT Workforce Curriculum
Version 3.0/Spring 2012
How IsSOA Different FromMessaging?
A common practice in healthcare, just not yet in healthcare IT
Many key products use them but do not expose interfaces
Ensures functional consistency across applications
Accepted industry best practice
Furthers authoritative sources of data
Minimizes duplication across applications, provides reuse Messages can be either payloads in or infrastructure beneath
services
Service-oriented architecture provides the framework for automation
of common services
Still, SOA has to be done well. It is cheaper and easier than ever tocreate badly designed applications and spaghetti integration
Fits well with Open Source
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
22/31
22
Health IT Workforce Curriculum
Version 3.0/Spring 2012
HL7 Services-Aware Enterprise
Architecture Framework (SAEAF)
Interoperability Framework for Enterprise
Architecture
Uses v3/RIM artifacts and expertise Supports measurable, testable conformance and
compliance
Provides directly implementable solutions
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
23/31
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
24/31
24
Health IT Workforce Curriculum
Version 3.0/Spring 2012
SAEAF Core Components
Information Framework
Behavioral Framework
Enterprise Conformance and ComplianceFramework
Governance Framework
Implementation Guide
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
25/31
25
Health IT Workforce Curriculum
Version 3.0/Spring 2012
What Is Being Specified?
Standards are being developed for:
Entity Identification
Record Location & Retrieval Decision Support Services
Terminology Service
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
26/31
26
Health IT Workforce Curriculum
Version 3.0/Spring 2012
Where Would Specifications Be Used? Inter-Enterprise (such as National Health Information
Network, Regional Health Information Organizations) By functionally specifying behavior, roles between applications
and products are clarified, and the technologies supporting them
can be profiled and sharpened
Intra-Enterprise
Standardization on functionality allows for better integration ofoff-the-shelf and custom development environments, and
promotes more of a plug and play environment
Intra-Product Facilitates vendors ability to integrate third-party value-add
components and speed design phase with higher confidence Custom-Implementation
Affords organizations wishing to custom-develop the opportunity
to later integrate off-the-shelf
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
27/31
27
Health IT Workforce Curriculum
Version 3.0/Spring 2012
Services In Particular Are
More coarsely granulated than messages
More readily traceable to business, clinical capabilities,
and requirements
Specifications for a service are of the form:
Functional Profile (collection of operations offered by a
service) + Semantic Profile (static semantics utilized byoperations in FP) + Conformance Profile (testable
(automated or human) conformance standards against
which an implementation may make pair-wise
conformance assertions) Combination of these two points above provides a
foundation for both intra- and inter-enterprise durable
services interfacesNetworking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
28/31
28
Health IT Workforce Curriculum
Version 3.0/Spring 2012
Healthcare Service SpecificationProject (HSSP)
Effort to create common service interface specifications
trackable within Health IT
Joint standards development project by HL7 and Object
Management Group (OMG) Objectives:
To create useful, useable healthcare standards that address
functions, semantics and technologies
To complement existing work and leverage existing standards
To focus on practical needs and not perfection To capitalize on industry talent through community participation
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
29/31
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
30/31
Enterprise Architecture ModelsSummary
Regional health care networks
National health care networks
SOA EA
30
Health IT Workforce Curriculum
Version 3.0/Spring 2012
Networking and Health Information Exchange
Enterprise Architecture Models
8/10/2019 09- Networking and Health Information Exchange- Unit 8- Enterprise Architecture Models
31/31