Enterprise Architecture (EA) Terms Accuracy - Qualitative assessment to which data accurately reflects real-world objects or matches the original source of data measured by percent of values that are correct when compared to actual value. (Source: Graduate School, USDA)

Accountable Care Organization (ACO) – Organizations that attempt to coordinate care for individuals in order to improve overall health status, with particular emphasis on the relationship between a person and his/her primary care provider – sometimes referred to as the “patient-centered medical home.” (HIMSS ACO FAQ)

Applications - Programs in which end users interact with IT systems. Examples in healthcare include electronic medical record systems, physician or patient portals, and patient billing. (Source: Gerstner)

Architect - Responsible for the effectiveness of the overall structure of both data management process and all data sources. (Source: Graduate School, USDA)

Architecture Segment - A part of the overall EA that documents one or more lines of business, including all levels and threads. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ )

Artifact - A documentation product, such as a text document, diagram, spreadsheet, briefing slides, or video clip. EA artifacts document EA components. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/)

Business Case - A collection of descriptive and analytic information supporting an investment in resource(s) and/or capabilities. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/

Business Reference Model (BRM) - Model for business processes. The BRM provides a comprehensive blueprint of the federal government around common business models. By focusing on common business models spanning multiple agencies, it promotes agency collaboration and facilitates the alignment of business functions with common FEA solutions and E-Gov strategies. (Source: http://www.whitehouse.gov/sites/default/files/omb/assets/fea_docs/OMB_EA_Assessment_Framewor k_v3_1_June_2009.pdf)

Capability Architecting - Translating capability needs to enterprise engineering requirements. (Source: Graduate School, USDA)

Capital Planning - The management and decision-making process associated with the planning, selection, control, and evaluation of investments in resources, including EA components such as systems, networks, knowledge warehouses, and support services for the enterprise. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea- terms-definitions/ )

Common Off-the-Shelf Software - Software that is available commercially

Community of Interest (COI) - A group or community of individuals that collaborates on a particular topic or subject area. COIs can be used to solve a common business problem, or they can simply be used as a forum to share ideas and information.

Completeness - The degree to which values are present in the attributes that require them. It is measured by percent of data fields having values entered into them. (Source: Graduate School, USDA)

Component - EA components are those plug-and-play resources that provide capabilities at each level of the framework. Examples include strategic goals and measures, business services, information flows and data objects, information systems, Web services and software applications, voice/data/video networks, and associated cable plants. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ )

Composite - An EA artifact that uses several documentation modeling techniques and/or represents several types of EA components. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/)

Configuration Management- The process of managing updates to EA components and artifacts, ensuring that standards are being followed. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/)

Consistency - The degree to which redundant faces are equivalent across two or more databases. It is measured by matching values across tables/files/records. (Source: Graduate School, USDA)

Crosscutting Component - An EA component that serves several lines of business. Examples include email systems that serve the whole enterprise, and financial systems that serve several lines of business. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ )

Culture - The beliefs, customs, values, structure, normative rules, and material traits of a social organization. Culture is evident in many aspects of how an organization functions. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea- terms-definitions/ )

Current View - An EA artifact that represents an EA component or process that currently exists in the enterprise. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ )

Data - Data items refer to an elementary description of things, events, activities, and transactions that are recorded, classified, and stored, but not organized to convey any specific meaning. Data items can be numeric, alphabetic, figures, sounds, or images. A database consists of stored data items organized for retrieval. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ )

Data Administration - A business function responsible for identifying, documenting, and modeling business information requirements and for maintaining the business set of data definitions and standards. (Source: Graduate School, USDA)

Data Architecture - The science and method of designing and constructing a data resource that is business-driven and implemented in appropriate environments. The overall structure of a data resource that provides a consistent foundation across organizational boundaries to provide easily identifiable, readily available high-quality data to support business activities. Examples of data resources include a database, a data dictionary, a data model, a data repository, and an XML schema. (Source: Graduate School, USDA)

Data Base Administrator (DBA) - Supplies data access capabilities to business users by operating and maintaining business data and the supporting infrastructure such as databases and underlying DMBS’s. (Source: Graduate School, USDA)

Data Governance - The exercise of decision-making and authority for data-related matters. (Source: Graduate School, USDA)

Data Management - The policies, procedures, and processes for managing data as a resource. Functions of data management include data standardization, data governance, master data management, data security, and metadata management. (Source: Graduate School, USDA)

Data Management Functions - Examples include data governance, metadata management, data quality management, master data management, data security, and data standardization (Source: Graduate School, USDA)

Data Quality - The degree of excellence of data factors contributing to data quality. This includes the data is stored according to its data type; the data is consistent; the data is not redundant; the data can be used with business rules; the data corresponds to established domains; the data is timely; the data is well-understood; the data satisfy the needs of the business; the user is satisfied with the validity of the data and the information derived from that data; the data is complete; and there are no duplicate records. For example, this means that a customer’s name is spelled correctly and the address is correct. (Source: Graduate School, USDA)

Data Security - The means of ensuring that data is kept safe from corruption and that access to it is suitably controlled. It is the process of protecting information from unauthorized use. Thus, data security helps to ensure privacy. It also helps in protecting personal data. An example is the use of credit card numbers on the Internet to purchase merchandise and services. Without data security measures in place, unauthorized persons can access the information. (Source: Graduate School, USDA)

Data Standardization - The process of achieving agreement on common data definitions, representation, and structures to which all data layers must conform. (Source: Graduate School, USDA)

Department of Defense Architectural Framework (DoDAF) – The overarching, comprehensive framework and conceptual model enabling the development of architectures to facilitate the ability of Department of Defense (DoD) managers at all levels to make key decisions more effectively through organized information sharing across the Department, Joint Capability Areas (JCAs), Mission, Component, and Program boundaries. (Source: http://cio- nii.defense.gov/sites/dodaf20/background.html)

Developer - Designs, specifies, and acquires or builds specific data assets, combining internal construction activities and external acquisitions to produce the required data assets. (Source: Graduate School, USDA)

Disruptive Innovations - Innovations that cause changes in established processes resulting in new policies or modes of operation. These innovations could be a result of government compliance and law changes, by new technology, or new competitors in the market. Recent disruptive innovations in healthcare are electronic health records, meaningful use, advances in mobile computing, and national Healthcare reform. Disruptive innovations cause an atmosphere of creativity as solutions are conceived to overcome barriers of operation. Disruptive innovations can also enable new technological applications and advances. Disruptive innovations are usually seen by users of a system as a negative, due to their resistance to change, but can be applied as positive forces. Companies that adapt during disruptive innovations (or who drive them) tend to succeed. Those that do not adapt or innovate tend to fail. (Source: Gerstner)

Data Reference Model (DRM) - Model for business information/data. The DRM enables information sharing and reuse across the federal government through the standard description and discovery of common data and the promotion of uniform data management practices. This model provides guidance on the implementation of consistent processes to enable data sharing through federal government-wide agreements. (Source: http://www.whitehouse.gov/sites/default/files/omb/assets/fea_docs/OMB_EA_Assessment_Framewor k_v3_1_June_2009.pdf)

Electronic Health Record (EHR) - A digital record of patient or health information that can be shared across different healthcare environments and networks.

Enterprise - An area of common activity and goals within an organization or between several organizations, where information and other resources are exchanged. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ )

Enterprise Architecture (EA) - The analysis and documentation of an enterprise in its current and future states from an integrated strategy, business, and technology perspective. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ ) Note: In a healthcare context, EA has the potential to facilitate integrating healthcare units with business architecture (Source: Kamran A. Healthcare Modeling through Enterprise Architecture: A Hospital Case. 2010).

Enterprise or Business View - A view used to communicate consistent definition of the meanings and descriptions of the data. This view is focused on the semantics (i.e., meaning) of the information stored as objects of interest, and is independent of how that data is stored or accessed. (Source: Graduate School, USDA)

Federal Enterprise Architecture (FEA) – Framework used by the US federal government to facilitate shared development of common processes and information amongst federal agencies. (Source: https://www.cms.gov/EnterpriseArchitecture/02_FEAF.asp )

Framework - A structure for organizing information that defines the scope of the architecture (what the EA program will document) and how the areas of the architecture relate to each other. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea- terms-definitions/ )

Future View - An EA artifact that represents an EA component or process that does not yet exist in the enterprise. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ )

Governance - A group of policies, decision-making procedures, and management processes that work together to enable the effective planning and oversight of activities and resources. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea- terms-definitions/ )

Health Information Exchange (HIE) - The transfer of healthcare information electronically across local healthcare organizations and groups. (Source: Grinberg)

Healthcare Information Technology (HIT) - Global term (which encompasses electronic health records and personal health records) to indicate the use of computers, software programs, electronic devices and the Internet to store, retrieve, share, update, transmit and use healthcare information and knowledge for communication and decision making regarding a patient’s healthcare. (Source: Brailer & Thompson, 2004 and Central Indiana Alliance for Health)

Horizontal Component - A horizontal (or crosscutting) component is a changeable goal, process, program, or resource that serves several lines of business. Examples include email and administrative support systems that serve the whole enterprise. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ )

Information - Data that has been organized so that it has meaning and value to the recipient. The recipient interprets the meaning and draws conclusions and implications. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ )

Information Consumer View - The external perspective of the information typically provided in reports, transactions, and screens. (Source: Graduate School, USDA)

Information Sharing - Information or data that is defined and structured such that it can be accessed, used, and understood by multiple systems. (Source: Graduate School, USDA)

Information Supply Chain- Usually a pictorial representation of how the information flows through a system. It shows data origination points, data processing, and data storage points. It should show information or data that is shared, and when that data is accessed, and by whom. (Source: Gerstner)

Integrated Definition Language (IDEF) - Developed by the US Air Force, it is an early effort (the Wing- IDEF Project started in 1993) to model and document model business process, data, and other influencers for software development projects. There are 16 methods (IDEF0 - IDEF14) for documenting the range of business or system functions, business processes, drill down information, and the inter- relationships. (Source: Gaboury)

Integrator - Coordinates budgets, contracts, schedules, manpower, and other physical resources to acquire or develop the specific data assets needed. Also documents and coordinates business data requirements of individual projects as a consistent whole within the current or future enterprise data environment. (Source: Graduate School, USDA)

Line of Business - A distinct area of activity within the enterprise. It may involve the manufacture of certain products, the provision of services, or internal administrative functions. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ )

Master Data Management - The process of dealing with data that needs to be shared among different systems- accessible to multiple users- often by merging records into one authenticated master file. (Source: Graduate School, USDA)

Metadata - Data about data. This could also be data about the data resource. Metadata describes how, when, and by whom a particular set of data was collected, and how the data is formatted. Metadata is essential for understanding information stored in data warehouses and has become increasingly important in SML- based Web applications. Also can mean additional information that describes the data. Can encompass meaning (semantic), resource (bibliographic info), discovery (location tagging), or structural aspects (schema or file formats). (Source: Graduate School, USDA)

Metadata Management - The management of metadata, which is becoming important because as systems become more and more interdependent, it is vital to know the impact that results when data is altered. (Source: Graduate School, USDA)

Methodology - The EA methodology defines how EA documentation will be developed, archived, and used, including the selection of a framework, modeling tools, and on-line repository. (Source: Graduate School, USDA)

Operational Architecting - Selecting and integrating operational forces into effective mission focused structure and development. (Source: Graduate School, USDA)

Physical View - The view of the information producer. It is a focus on the physical access, storage and retrieval methods used to implement the data requirement. (Source: Graduate School, USDA)

Policy Maker - Establishes and enforces data management policies. A policy maker defines data management vision, goals, organization and objectives. (Source: Graduate School, USDA)

Precision - The degree to which data is known to the right level of granularity, measured by percent of data fields having the appropriate level of granularity. (Source: Graduate School, USDA)

Primitive - An EA artifact that uses one modeling technique to describe an EA component. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea- terms-definitions/ )

Program - A group of related projects managed in a coordinated way. Programs usually involve an element of ongoing activity. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ )

Project - A temporary endeavor undertaken to create a unique product, service, or result. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea- terms-definitions/ )

Performance Reference Model (PRM) - Provides a framework to use EA to measure the success of IT investments and their corresponding impact on strategic outcomes. This model links internal business components to the achievement of business and customer-centric outputs. (Source: http://www.whitehouse.gov/sites/default/files/omb/assets/fea_docs/OMB_EA_Assessment_Framewor k_v3_1_June_2009.pdf)

Reference Information Model (RIM) - A static model of health and healthcare information as viewed within the scope of HL7 (Health Level 7) standards development activities. It provides a static view of the information needs of HL7 Version 3 standards.

Service Component Reference Model (SRM) - Model for business intelligence. The SRM classifies service components according to their support for business and performance objectives. This model improves efficiency by exposing opportunities for the reuse of business components and services to support business functions across the federal government. (Source: http://www.whitehouse.gov/sites/default/files/omb/assets/fea_docs/OMB_EA_Assessment_Framewor k_v3_1_June_2009.pdf)

Silo- A vertical, top down or bottom up approach that does not consider outside influences in decision making. These influences could be interacting business units, or interacting companies. A silo creates a narrow vision and is a self- centered, antiquated business approach which does not efficiently use resources, nor allows for collaboration or shared assets. (Source: Gerstner)

Software-As-A-Service (SAAS) - Software functions or applications that are available over a network usually for a subscription price.

Steward - Establishes standardizes and certifies business data in assigned data subject area(s). At the enterprise level, stewards address organization data requirements in assigned subject areas across all business or functional areas. At the business functional area or application/project levels, stewards address data requirements within their organizational scope. (Source: Graduate School, USDA)

Strategic Architecting - Planning the alignment of resources within the corporate strategy (Source: Graduate School, USDA)

System - A type of EA component that is comprised of hardware, and software, and activities that has inputs and outputs. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea-terms-definitions/ )

Systems Architecting - Allocating engineering requirements to system/product components. (Source: Graduate School, USDA)

The Open Group Architecture Framework (TOGAF) - A framework for EA which provides a comprehensive approach for designing, planning, implementation, and governance of an enterprise information architecture. TOGAF is a registered trademark of The Open Group in the United States and other countries. TOGAF is a high level and holistic approach to design, which is typically modeled at four levels: Business, Application, Data, and Technology. It tries to give a well-tested overall starting model to information architects, which can then be built upon. It relies heavily on modularization, standardization and already existing, proven technologies and products. (Source: http://en.wikipedia.org/wiki/The_Open_Group_Architecture_Framework)

Technical Reference Model (TRM) - Categorizes standards and technologies to enable the delivery of service components and capabilities. This model provides a foundation to advance reuse and technology standardization from a government-wide perspective. It allows agencies to realize economies of scale by identifying and reusing the best solutions and technologies to support their mission and business functions. (Source: http://www.whitehouse.gov/sites/default/files/omb/assets/fea_docs/OMB_EA_Assessment_Framewor k_v3_1_June_2009.pdf )

Unstructured Data - Data that has not been structured and cannot be readily transformed into intelligence using the same tools and techniques as structured data. Unstructured data comprises 80-90 percent of the information in an organization. It includes documents, files containing any data that is not in tabular or delimited format. It is also known as recorded knowledge, Web content, data documents, etc. (Source: Graduate School, USDA)

Uniqueness - The degree to which there are no redundant occurrences or records of the same object or event. It is measured by the percent of records having a unique primary key. (Source: Graduate School, USDA)

Validity - The degree to which data conforms to its definition, domain values and business rules. It is measured by the percent of data having values that fall within their respective domain of values. (Source: Graduate School, USDA)

Vertical Component- An EA component that is contained within one line of business. Examples include a system, application, database, network, or website that serves one line of business. (Source: International Enterprise Architecture Institute. Available at http://internationaleainstitute.org/ea- terms-definitions/ )

Veterans Integrated System Technology Architecture (VISTA) - Developed by the VA for purposes of serving as an EHR. This architecture is now open source.

ZACHMAN Framework - Originally attributed to IBM Researcher whose first paper in 1987 identified the first EA Architecture. Zachman’s Framework is one that addresses who, what, where, when and why to identify system components in an EA architecture. It provides a way to identify existing and planned component parts and their relationships before beginning costly and time consuming efforts of transformation. Additional terms are available at: http://pubs.opengroup.org/architecture/togaf9- doc/arch/chap03.html