CIMI Enterprise Architecture Proposal April 12 2013 1

CIMI Enterprise Architecture Proposal April 12, 2013 1 3/3/2021

What is Enterprise Architecture? � “The structure of components, their interrelationships, 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 2 3/3/2021

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

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 4 3/3/2021

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) 5 3/3/2021

TOGAF Layers and Typical Artifacts � Business Architecture: � � � 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: � � 6 Actors Use cases Processes, workflows, activity diagrams Products 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 3/3/2021

TOGAF Arch. Development Methodology 7 3/3/2021

CIMI EA Proposal for Version 1 � Internal architecture � � 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 � � � 8 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 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 3/3/2021

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 3/3/2021

Examples � Roles (discharge summary solution) 10 3/3/2021

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 11 3/3/2021

Examples � Use Case Model (RTLS) 12 3/3/2021

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 13 3/3/2021

Examples � Process 14 diagram (discharge summary solution) 3/3/2021

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) 15 3/3/2021

Examples � Info 16 scope and organization model 3/3/2021

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 17 3/3/2021

Examples � Systems/Tools 18 Capability Model (RTLS) 3/3/2021

Examples � Systems/Tools Context Diagram (client relationship management solution) 19 3/3/2021

CIMI External IA / AA (i. EHR example) 20 3/3/2021

Summary � Create lean CIMI EA v 1 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 21 3/3/2021

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 22 4/10/2013