Innovate2012_MAC-2196

Healthcare Management System Reference
Architecture: Model-Driven Architecture,
TOGAF, and Collaboration Key to
Advances in Healthcare Ecosystem
Arman Atashi
Senior Enterprise Solution Architect
BlueCross BlueShield of North Carolina
arman.atashi@bcbsnc.com
MAC-2196

© 2012 IBM Corporation
2
The Premier Event for Software and Systems Innovation
 Introduction
 M3 Primer
– M3 Framework
– MDA Principles & Disciplines
– Context for Enterprise Modeling
– Modeling Environment & Summary
 M3 & TOGAF
– Synergy
– Concept Mapping
– RSA Template
 HealthCare Management System Reference Architecture
– Architecture Vision
– Business Architecture
– Applications Architecture
– Technology Architecture
 RSA Reference Architecture Walkthrough
Agenda

3
Introduction
 This session presents an extensible reference architecture for the development of standards-
based integrated healthcare management solution by combining:
– M3 (Modeling at 3 levels), an enterprise modeling framework based on model driven architecture
guidelines and unified modeling language notation,
– TOGAF® (The Open Group Architecture Framework), a method for developing enterprise architecture,
– and utilizing IBM Rational Software Architect for model construction, IBM Rational Team Concert for
model lifecycle management, and IBM Rational Software Architect Design Manager for collaboration

4
 Introduction
 M3 Primer
– M3 Framework
 M3 & TOGAF
– Synergy
– Concept Mapping
– RSA Template
– Applications Architecture
 Reference Architecture Walkthrough
Agenda

5
PRIMER
3
3
™

6
M3 Framework
 M3 framework identifies five components necessary for developing and maintaining
enterprise models
Modeling
Workflow
M3
Framework
Components Integration
Model
View
Aggregation
Modeling
Notation
Modeling
Environment
3
3
™

7
M3 Framework
Modeling Workflow
Integration Model
View Aggregation
Modeling Notation
Modeling Environment
3
3
™
MDA Principles and Disciplines Context for Enterprise Modeling
M3
Framework
Components

8
MDA Principles & Disciplines
M3 MDA Models
Use Case Model Activity ModelDomain Model
Computation Independent Model (CIM)
Component ModelType Model
Platform Independent Model (PIM)
Service Model
Runtime Model Deployment ModelData Model
Platform Specific Model (PSM)
Platform Specific Implementation (PSI)
<<artifact>>
Script
<<artifact>>
Code
<<artifact>>
Configuration
Domain Model describes the problem domain in terms
of business concepts
Use Case Model describes functionality of a system in
terms of use cases/user tasks/actions
Activity Model describes behaviors of a system in
terms of activities, actions, controls, and data flows
Type Model specifies domain objects in terms of types,
attributes, associations, collaborations
Component Model specifies the scope,
responsibilities, and supported interfaces for the
discovered components,
Service Model specifies services which provide
reusable business functionality
Data Model represents the structure and relationship of
data in information repositories,
Runtime Model illustrates the structure of the elements
that have runtime presence
Deployment Model depicts how the system is
deployed to hardware infrastructure

9
MDA Principles & Disciplines
M3 MDA Models
Service Model
Platform Specific Implementation (PSI)
<<artifact>>
Script
<<artifact>>
Code
<<artifact>>
Configuration
Requirements Analysis
Specification
Architectural Design
Specification
Implementation Deployment
Specification
High Level Design Model
Construction & Assembly
Detailed Design Model
Business Requirements
Requirements Model
Test & Deployment
Implementation Artifacts
GenericSDLC

10
Context for Enterprise Modeling
 M3 extends MDA viewpoints and defines an independent model, Integration Specific Model
(ISM), that has no dependencies with other three models
– ISM reflects the Enterprise Integration viewpoint of the system
– Models are extracted from the three M3 Models (CIM, PIM, and PSM)
M3 Integration
Model
<<Integration Level>>
Interface
Platform
Business
Integration Specific
Model (ISM)
Subset of the CIM, includes
business, process, and workflow
integration models
Subset of the PIM, includes
technology independent
component and service
interfaces integration models
Subset of the PSM, includes
services, distributed objects and
components, data exchange
formats, application
programming interfaces, and
data access integration models

11
Context for Enterprise Modeling
Business
Architecture
Information
Architecture
Application
Architecture
Technical
Architecture
Enterprise
Architecture
 The model structures and cross-model interrelationships form the basis of M3 view
aggregation
 View aggregation is achieved by assembling M3 UML packages
 The aggregated views present the information in other meaningful ways to different
stakeholders reflecting four key scopes of Enterprise Architecture

12
 Each M3 model is a distinct model (emx file) in RSA
 M3 models are published from RSA to RTC
RSA
Create &
Refine
RTC
Publish &
Manage
RDM
Collaborate
& Manage

13
 Cross-model interrelationships is expressed by UML packages dependencies

14
M3 Model RSA Model Package Owner Role Collaborator Role
CIM – The Outside Activity Model
Use case Model
Domain Model
Application System Analyst Business Analyst
Project Lead Architect
PIM – The Edge Component Model
Type Model
Service Model
Project Lead Architect Domain Architect
PSM – The Inside Runtime Model
Deployment Model
Data Model
Application System Designer Project Lead Architect
Data Modeler
ISM – The Extension Business
Interface
Platform
Project Lead Architect Domain Architect

15
M3 Modeling Methodology Summary
RSA Model Project Templates
M3 Models
Activity Model
CIM
Use Case Model
Domain Model
Component Model
PIM
Type Model
Service Model
Runtime Model
PSM
Deployment Model
Data Model
Platform
ISM
Business
Interface
UML Diagrams Used in Models
Component Class Sequence
Deployment
Class
Use Case
Class
Activity
Class
Sequence
Package
Package & State Machine
diagrams may be used in
all models
State Machine
PIM
Diagrams
CIM
Diagrams
PSM
Diagrams
Roles & Responsibilities
Collaborator Owner
Requirements Analysis
Specification
Architectural Design
Specification
Implementation
Deployment Specification
Modeling Workflow
 Models describe the problem
domain and business
requirements
 Focus is UML behavioral
modeling
 Models specify supported
and required, interfaces,
components, and services
 Focus is UML structural and
interaction modeling
 Models describe software
implementation and
deployment for the selected
computing platform
 Focus is UML structural
modeling
Enterprise Integration
Specification
 Models are subsets of CIM,
PIM, PSM, and describe
supported levels of
integration
CIMTheOutside
Level1
PIMTheEdge
Level2
PSMTheInside
Level3
ISMTheExtension
IntegrationLevels

16
A complete framework for enterprise modeling, integration, and
architecture representation
M3 MDA Models
Service Model
M3 Integration
Model
Interface
Platform
Business
Integration Specific
Model (ISM)
3
3 Modeling
Methodology
™
Enterprise
Architecture
<<EA>>
Business
<<EA>>
Information
<<EA>>
Application
<<EA>>
Technical

17
 Introduction
 M3 Primer
– M3 Framework
 M3 & TOGAF
– Synergy
– Concept Mapping
– RSA Template
– Application Architecture
Agenda

18
M3 & TOGAF
3
3
™
TOGAF®

19
Synergy
 TOGAF (The Open Group Architecture Framework) is a framework for developing an
enterprise architecture
 TOGAF supports four architecture domains; Business, Data, Application, and Technology
 TOGAF ADM (Architecture Development Method) is a process for developing architectures
and identifies eight phases/cycles

20
Synergy
 M3 and TOGAF ADM complement each other in key areas
 The resources (models/views and framework) can be mapped to produce different types of
architecture describing an overall Enterprise Architecture
 M3 models and views map on to the first four phases of ADM; A, B, C, and D

21
Concept Mapping  M3 View Aggregation
 M3 UML package compositions constitute a generic model for enterprise architecture domains
Enterprise
Architecture
<<CIM>>
Activity Model
<<CIM>>
Use Case Model
<<CIM>>
Domain Model
<<PIM>>
Service Model
<<PSM>>
Data Model
<<PIM>>
Type Model
<<CIM>>
Domain Model
<<PSM>>
Runtime Model
<<PSM>>
Data Model
<<PIM>>
Component Model
<<PSM>>
Deployment Model
<<PSM>>
Deployment Model
<<PSM>>
Data Model
Business
Architecture
Information
Architecture
Application
Architecture
Technical
Architecture

22
Concept Mapping  Enterprise Architecture Domains
Architecture
Vision
Business
Architecture
Information Systems
Architectures
Applications
Architecture
Technology
Architecture
TOGAF
Enterprise Architecture
Segment
Architecture(s)
Opportunities
and Solutions
Strategic Architecture
Capability Architecture(s)
Data
Architecture
Business
Architecture
Information
Architecture
Application
Architecture
Technical
Architecture
Enterprise
Architecture
M3 Generic Enterprise
Architecture Domains

23
Concept Mapping  M3 Models & TOGAF ADM
 Architecture Vision
– Defines relevant stakeholders, key business requirements and the scope of architecture, and
demonstrates how the vision responds to the requirements
– Includes high-level M3 CIM and PIM Models
 Business Architecture
– Defines key business processes, business requirements ,and service strategy
– Includes M3 CIM Models
 Information Systems Architectures (Applications and Data)
– Provides the blueprint for deployed systems showing their interactions and describes the structure of
logical and physical data resources
– Includes M3 PIM and PSM Models
 Technology Architecture
– Describes software and hardware infrastructure required to support the deployed application(s)
– Includes M3 PSM Models

24
Concept Mapping  Reference Guide
TOGAF
Enterprise Architecture
CIM PIM PSM Reference
Architecture
Architecture Vision Use Case Model
[high-level]
Component Model
[high-level]
Business Context
Business Architecture Domain Model
Activity Model
Use Case Model
Service Model Domain Interaction
Context
Information System Architecture
Applications Architecture
Component Model
Service Model
Run Time Model Implementation
Context
Information System Architecture
Data Architecture
Domain Model Type Model Data Model Entity Context
Technology Architecture Run Time Model
Deployment Model
Technical Context

25
RSA Template  Model Composition
 Similar to the other M3 RSA templates, M3 TOGAF is a distinct model (emx file) in RSA
 It consists of five UML packages reflecting the first four phases of TOGAF ADM

26
RSA Template  Model Navigation
 Each M3 TOGAF UML package includes a
TOGAF right navigation bar
 Information Systems Architecture is further
divided into its perspective domains
 Requirements Management may be linked
to the requirements repository and/or
documents

27
 Introduction
 M3 Primer
– M3 Framework
 M3 & TOGAF
– Synergy
– Concept Mapping
– RSA Template
Agenda

28
HEALTHCARE MANAGEMENT SYSTEM
REFERENCE ARCHITECTURE
3
3
™
TOGAF®

29
Organizational Delivery Model
Source: External (enterprise planning activity, business strategy & goals)

30
Member Health Information Transformation Cycle
Create & Employ
Knowledge
Manage
Member’s Health
Acquire &
Manage Data
Aggregate &
Analyze Data
Acquire & Manage
Data
Aggregate &
Analyze Data
Create & Employ
Knowledge
Manage Member’s
Health
•Membership
•Claims
•External Data
•Biometric Data
•Surveys
•HRA/Self-reported
•Data Extract
•Data Mining
•Predictive Analytics
•Scorecards & Reporting
•Cost & Performance
Models
•Gaps in care
•Inclusion List
•Criteria sets
•Evidence based
guidelines & tools
•UM/CM/DM & Appeals
•Medical Review
•Workflow Efficiency
•Lifestyle Assessment
•Personal Wellness
Information-Centric View of Business Processes
Source: External (business processes & workflows, business operations)

31
Process and Service Capability
Source: M3 CIM Use Case Model

32
Business Components
Source: M3 PIM Component Model

33
Business & System Actors

34
System Context

35
Key Use Cases

36
Partial Domain Model
Source: M3 CIM Domain Model

37
Service Interface
Source: M3 PIM Component Model

38
Service Integration
Source: M3 PSM Deployment Model

39
 Introduction
 M3 Primer
– M3 Framework
 M3 & TOGAF
– Synergy
– Concept Mapping
– RSA Template
Agenda

40
RSA REFERENCE ARCHITECTURE
WALKTHROUGH
3
3
™
TOGAF®

41
www.ibm.com/software/rational

42

43
Daily iPod Touch giveaway
 Complete your session surveys online each day at a conference kiosk or on your
Innovate 2012 Portal!
 Each day that you complete all of that day’s session surveys, your name will be entered
to win the daily IPOD touch!
 On Wednesday be sure to complete your full conference evaluation to receive your
free conference t-shirt!

44
Acknowledgements and disclaimers
© Copyright IBM Corporation 2012. All rights reserved.
– U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM, the IBM logo, ibm.com, Rational, the Rational logo, Telelogic, the Telelogic logo, Green Hat, the Green Hat logo, and other IBM products and
services are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these
and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate
U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or
common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at
www.ibm.com/legal/copytrade.shtml
References
[The Open Group, 2012] The Open Group Architecture Framework (TOGAF) Version 9.1, http://www.opengroup.org/togaf/
[OMG, 2012] Object Management Group, Unified Modeling Language: Infrastructure & Superstructure: Version 2.4.1 http://www.omg.org/technology/
Other company, product, or service names may be trademarks or service marks of others.
Availability: References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries
in which IBM operates.
The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for
informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant.
While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS-IS without
warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this
presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or
representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of
IBM software.
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have
achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to,
nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

45
© Copyright IBM Corporation 2012. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind,
express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have
the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM
software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities
referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature
availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines
Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.

Innovate2012_MAC-2196

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Innovate2012_MAC-2196

Similar to Innovate2012_MAC-2196 (20)

Innovate2012_MAC-2196