1. CIMI Enterprise Architecture Proposal
April 12, 2013
9/21/2018

2. What is Enterprise Architecture?
“The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time” (TOGAF)
Enterprise Architecture applies at the macro level
Applies to business practices, software and infrastructure
Works at the “system of systems level”
Focus more on how components work together instead of the architecture of a specific component
Typically creates as-is state, to-be state (in 5 years), goal- state (nirvana, undisclosed time), and transition plans
9/21/2018

3. Architecture Frameworks
HL7 SAIF (ECCF), TOGAF ADM, Zachman, DoDAF, FEAF
Who, What, Why, Where, When, How…
SAIF
TOGAF
FEAF
DODAF
OneVA
Others…
Common Characteristics
Business
Information and Data
Application and Services
Technology Infrastructure
Drivers, requirements and traceability
Actors, roles, groups, responsibilities
Processes, functions and use cases
Information models, terminologies, data dictionaries
Artifacts, business objects
Metadata
Data management, quality
Data persistence, source of truth
Knowledge management
Data flows
Systems, tools, software
Databases, data stores
Interfaces, integration
Orchestration, choreography, composition
User interfaces, portals
Platforms, storage and networks
Qualities of Service, Service Level Agreements
Devices and hardware
COOP and disaster recovery
9/21/2018

4. Why EA for CIMI CIMI is mini-enterprise CIMI in the “forming” stage
Lots of discussion about
Roles
Use Cases
Processes
Business Specifications
Tools
Products
EA can help formalize and standardize
EA can drive visualization, coherence, discussion, consensus, governance
9/21/2018

5. EA Suggested Guidelines for CIMI
Start small – Create a “lean” EA for CIMI
Use/modify TOGAF architecture development methodology (or comparable)
Drive tooling, technology, platforms, etc. from the business architecture
Build incrementally based on need
Use standard notation for EA diagrams: UML and Archimate
Separate the internal architecture of CIMI (how CIMI products are created) from the external architecture of CIMI (how CIMI products are used)
9/21/2018

6. TOGAF Layers and Typical Artifacts
Business Architecture:
Actors
Use cases
Processes, workflows, activity diagrams
Products
Information Systems Architecture (including both information architecture and application architecture):
System/component diagrams
Interfaces and data flows
Information models and terminologies
Sequence and collaboration diagrams
Technology Architecture:
Packaging and deployment
Tools and materials (e.g., specific platforms like Oracle)
Network, storage, operating systems topology and capability diagrams
Disaster recovery and COOP plans
9/21/2018

7. TOGAF Arch. Development Methodology
9/21/2018

8. CIMI EA Proposal for Version 1
Internal architecture
Future “goal-posts” – principles, best practices
Diagrams for the current/planned state (e.g., 2013)
Who, What and How for the business, information and application architecture layers
External architecture
Projected target state (e.g., 2 years from now) for CIMI customers
What and How for the information and application layers
Sample external architectures showing how CIMI products are used for one or more CIMI participants
Out of Scope
Why and Where (and Who for external architecture)
Business architecture layer of external architecture
Technology architecture (platforms, storage, network, etc.)
Target State internal architecture
Transition Plans
9/21/2018

9. CIMI Internal BA – Who is CIMI
Catalog of Actors
Key individuals
Contributing organizations
Catalog of Roles
Individual roles (e.g., leaders)
Groups (e.g., workgroups)
9/21/2018

10. Examples
Roles (discharge summary solution)
9/21/2018

11. CIMI Internal BA – What does CIMI do
Catalog of Published Products/Outcomes
Catalog of Functions/Use Cases
List of functions
Use Case model with primary roles
RACI charts for primary functions
9/21/2018

12. Examples
Use Case Model (RTLS)
9/21/2018

13. CIMI Internal BA – How does CIMI do it
Catalog of defined Processes
List of processes
Activity diagrams for primary processes with swimlanes for roles
Map processes to functions/use cases
9/21/2018

14. Examples
Process diagram (discharge summary solution)
9/21/2018

15. CIMI Internal IA
Catalog of Business objects (based on Steve’s document)
Context diagrams of business objects (e.g., conceptual model, logical model, reference set, etc.)
Map business objects to process charts
Information scope and organization
CIMI glossary
CIMI standards profile
(CIMI Information models and terminologies deferred to modeling workgroup)
9/21/2018

16. Examples
Info scope and organization model
9/21/2018

17. CIMI Internal AA Capability model Catalog of systems/toold
List of systems/tools
Systems/tools context diagrams (dependencies)
Map systems/tools to capabilities
Map systems/tools to business objects
Map systems/tools to process charts
System Interactions
Activity or sequence diagrams showing how systems/tools communicate to facilitate business processes and support use cases
9/21/2018

18. Examples
Systems/Tools Capability Model (RTLS)
9/21/2018

19. Examples
Systems/Tools Context Diagram (client relationship management solution)
9/21/2018

20. CIMI External IA / AA (iEHR example)
9/21/2018

21. Summary
Create lean CIMI EA v1 using standard architecture framework and methodology
Focus on parts of both internal and external architecture
Current state for internal architecture
Target state (2 years from now) for external architecture
Develop key views/diagrams within the business, information and application architecture layers
9/21/2018

22. Next Steps Establish CIMI EA team
Subject matter experts
EA developers (modeling expertise)
Reviewers and approvers
Approve scope, deliverables, timelines
Assign work
Define review/approval processes
EA “as-is” is a relative term requiring continuous review and update
4/10/2013