Introduction to Information Architecture Informatics Training for CDC Public Health Advisors

Imagine building a house.. n without any architectural plans n with only general sketches as to how it’s supposed to look, or only detailed diagrams for wiring, plumbing, etc. n with each subcontractor doing whatever they thought best, without consulting with the owner or other contractors n with no specialized functions for the rooms (e.g., every room has its own little stove, bed, bathtub…) n where the house had to be torn down to remodel one room S.O.P. for building information systems in public health.

Information architecture n A metaphor for a systematic, ‘planful’ approach to building enterprise-wide information systems. Information architecture refers to the totality of the data, processes, and technology used in a given enterprise, and the relations between them. It includes databases, applications, standards, procedures, hardware, software, networks, etc.

Attributes of a good architect n Can communicate well with the customer n Can develop general drawings and diagrams based on the descriptions of customer’s wants and needs n Can develop more specific drawings and diagrams for communicating with the builders (general contractor and subcontractors) n Can communicate well with the builders, and help devise solutions as problems present themselves n Can provide a consistent, overall vision throughout the project, and work with the customers and the builders to achieve that vision.

An information architecture … n Provides a guiding plan across projects Promotes component orientation  smaller units, more easily upgraded n Eases maintenance, by defining ‘natural boundaries’ between information systems (e.g., budgeting, surveillance) n Simplifies systems, by decreasing redundancy of data entry, storage

An information architecture … n Breaks big problems into manageable chunks n Allows the efficiency and interoperability inherent in standards n Promotes planning, clarifies business processes n Facilitates solving a common problem once, instead of solving it many ways, many times n Allows flexible incorporation of new IT

An information architecture … n Returns locus of control and decision making to the executive level, away from the IT community. An information architecture provides the basis of business control over the distributed development of information systems.

Information architecture ‘views’ n Multiple levels of architectural plans are needed, from the general (representing overall ‘business’ processes & objectives), to the specific (indicating specific technology and implementation details) n The specific (technical) views of the architecture should be based on higher, business views--i.e., the IT architecture should be tightly tied to the business processes and objectives

Information architecture ‘views’ Business views of the architecture  What needs to be automated Information technology views of the architecture  How that should be automated n Business views should be relatively stable; IT views should be able to adapt to improvements in technology

The Zachman Framework n A two-dimensional structure for describing the information architecture of an enterprise n 1 st dimension: the roles involved in information systems design (planner, owner, designer, builder) n 2 nd dimension: What, How, Where, etc.

Info Architecture “pearls” n We need to develop high-level blueprints of our public health agencies’ information needs, and use these blueprints to guide systems development n Tools exist to help with this process (e.g., the Zachman Framework) n New information systems applications should be developed within the context of a larger, coherent information architecture n Public health leaders, not technologists, must drive the process

Info Architecture “pearls” (cont’d) n See Cook’s Building enterprise information architectures for an excellent review of this area. n More to come: We will revisit the idea of information architecture on Thursday.