Sanders-Healthcare-data-warehousing-2002
➤ Gửi thông báo lỗi ⚠️ Báo cáo tài liệu vi phạmNội dung chi tiết: Sanders-Healthcare-data-warehousing-2002
Sanders-Healthcare-data-warehousing-2002
Designing, Developing, and Supporting anEnterprise Data Warehouse (EDW)In HealthcareCopyright 2002Dale SandersIntermountain Health Care1IntroductionTh Sanders-Healthcare-data-warehousing-2002 he Dutch physicist. Heike Kammerlingh Onnes. discoverer of superconductivity in 1911, posted a sign above the entrance to his laboratory— "Through measurement, comes knowledge." In no other field of study, including physics, are measurement and true knowledge more complex, more elusive, or more subj Sanders-Healthcare-data-warehousing-2002 ective than that found in healthcare. We are measuring ourselves and in so doing, the observer becomes the observed. The challenge to find the Uuth isSanders-Healthcare-data-warehousing-2002
simultaneously fascinating and daunting. The essence of data warehousing IS not information technology; Information technology is merely the enabler.Designing, Developing, and Supporting anEnterprise Data Warehouse (EDW)In HealthcareCopyright 2002Dale SandersIntermountain Health Care1IntroductionTh Sanders-Healthcare-data-warehousing-2002 al change and Improvement. At Intermountain Health Care (IHC) in Salt Lake City. UT a team of medical informaticists and information systems professionals recruited from other industries was assembled in 1997 to develop and deploy an enterprise data warehouse (EDW) to measure and better understand I Sanders-Healthcare-data-warehousing-2002 HC s integrated delivery system. The intent of this chapter is to provide a brief review of transactionbased and analytical-based information systemsSanders-Healthcare-data-warehousing-2002
and the emergence of data warehousing as a sub-specialty in information systems, and discuss the lessons learned in the deployment of IHC'S EDW.BackgrDesigning, Developing, and Supporting anEnterprise Data Warehouse (EDW)In HealthcareCopyright 2002Dale SandersIntermountain Health Care1IntroductionTh Sanders-Healthcare-data-warehousing-2002 ally to Maslow s Hierarchy for human actualization. The success of a data warehouse begins with this sense of IT Actualization, as illustrated belowMetricsActualizationStrategyTechnologyProcessesPeopleVision2Successful IT systems must be founded upon a clear vision of the future for those systems an Sanders-Healthcare-data-warehousing-2002 d their role in the enterprise. They must be founded upon an environment that nurtures people that are values based, understand information technologySanders-Healthcare-data-warehousing-2002
(IT), and fully understand the business and clinical missions that they support. These same people must be allowed to define and operate within a fraDesigning, Developing, and Supporting anEnterprise Data Warehouse (EDW)In HealthcareCopyright 2002Dale SandersIntermountain Health Care1IntroductionTh Sanders-Healthcare-data-warehousing-2002 manifestation of the underlying vision, people, and processes in the journey to IT Actualization and success. All of these steps in the journey must be wrapped in a sense of metrics—measuring the progress towards Actualization—and a systemic strategy that unites each.Transaction and Analytical Syst Sanders-Healthcare-data-warehousing-2002 ems: At a high level, there are two basic types of functions supported by information systems—(1) Transaction processing that supports an event-drivenSanders-Healthcare-data-warehousing-2002
clinical or business process, such as patient scheduling, and (2) Analytical processing that supports the longitudinal analysis of information gatherDesigning, Developing, and Supporting anEnterprise Data Warehouse (EDW)In HealthcareCopyright 2002Dale SandersIntermountain Health Care1IntroductionTh Sanders-Healthcare-data-warehousing-2002 very rare. And in some cases, an information system is designed expressly for retrospective data analysis and supports very little in the way of true workflow. e g., a project time tracking systemThe purest form of an analytical information system is a data warehouse. Data warehouses have existed in Sanders-Healthcare-data-warehousing-2002 various forms and under various names since the early 1980 s. though the true origins are difficult to pinpoint. Military command and control and intSanders-Healthcare-data-warehousing-2002
elligence, manufactunng. banking, finance, and retail markets were among the earliest adopters. Though not yet called "data warehouses’, the space andDesigning, Developing, and Supporting anEnterprise Data Warehouse (EDW)In HealthcareCopyright 2002Dale SandersIntermountain Health Care1IntroductionTh Sanders-Healthcare-data-warehousing-2002 d off-line. A short and sometimes overlooked period in the history of information systems took place in the early to mid-1990s that also affected the evolution of data warehousing. During this period, there was great emphasis placed on 'downsizing" information systems, empowering end users, and dist Sanders-Healthcare-data-warehousing-2002 ributing processing to the desktop. Client-server computing was competing against entrenched glass house mainframes and was seen as the key to this doSanders-Healthcare-data-warehousing-2002
wnsizing and cost reduction. Many companies undertook projects to3convert mainframe databases and flat files to more modern relational databases, and Designing, Developing, and Supporting anEnterprise Data Warehouse (EDW)In HealthcareCopyright 2002Dale SandersIntermountain Health Care1IntroductionTh Sanders-Healthcare-data-warehousing-2002 computing was actually much more expensive than centralized applications and data, and thin clients. However, despite what some might call the failure of client-server computing, this IS the period that created the first data warehouses in private industry.In reality, a data warehouse is a symptom Sanders-Healthcare-data-warehousing-2002 of two fundamental problems in Information systems—(1) The inability to conduct robust analytical processing on Information systems designed to supporSanders-Healthcare-data-warehousing-2002
t transaction oriented business processes, and (2) Poorly integrated databases that provide a limited and vertical perspective on any particular businDesigning, Developing, and Supporting anEnterprise Data Warehouse (EDW)In HealthcareCopyright 2002Dale SandersIntermountain Health Care1IntroductionTh Sanders-Healthcare-data-warehousing-2002 cted on a single, monolithic information system. Such is the vision of "Enterprise Resource Planning" (ERP) systems, found more and more often in the manufacturing and retail markets. But even in these systems, the vision IS elusive, at best, and separate analytical and transaction systems are gener Sanders-Healthcare-data-warehousing-2002 ally still required to meet the needs of the company. Recognizing that transaction processing and analytical processing require separate IT strategiesSanders-Healthcare-data-warehousing-2002
IS an imperative in the architecture of a successful enterprise information system. Unfortunately, in many cases. IT strategies tend to place overwheDesigning, Developing, and Supporting anEnterprise Data Warehouse (EDW)In HealthcareCopyright 2002Dale SandersIntermountain Health Care1IntroductionTh Sanders-Healthcare-data-warehousing-2002 ime again, we witness situations in which transaction data IS collected quite effectively to support a workflow process, but extracting meaningful reports from this system for analysis is difficult or impossible. Rarely, if ever, is a transaction system deployed that will not require, at some point Sanders-Healthcare-data-warehousing-2002 in its lifetime, the analysis of the data it collects. Deliberately recognizing this fact in the requirements and design phase of the transaction systSanders-Healthcare-data-warehousing-2002
em will result in a much more elegant solution for the analytical function. The knowledge gained from the analytical function can be used to improve tDesigning, Developing, and Supporting anEnterprise Data Warehouse (EDW)In HealthcareCopyright 2002Dale SandersIntermountain Health Care1IntroductionTh Sanders-Healthcare-data-warehousing-2002 prove quality; adding additional data elements for collection deemed important to analysis, etc. In this regard, we can see the constant feedback and interplay between a well-designed information system- the transaction function supports4the analytical function which supports the improvement of the Sanders-Healthcare-data-warehousing-2002 transaction system, and so on in a constant cycle of improvement.As illustrated below, a data warehouse IS analogous to a library—a centralized logicaSanders-Healthcare-data-warehousing-2002
l and physical collection of data and information that is reused over and over to achieve greater understanding or stimulate new knowledge. A data marDesigning, Developing, and Supporting anEnterprise Data Warehouse (EDW)In HealthcareCopyright 2002Dale SandersIntermountain Health Care1IntroductionTh Sanders-Healthcare-data-warehousing-2002 m across the enterprises Analogous to a library•Data mart: A database repository that consolidates or integrates data and supports a single business area or specific reporting requirement■ Analogous tQ a section in a libraryIt is not the Clinical Data RepositoryIt is difficult to trace the origins o Sanders-Healthcare-data-warehousing-2002 f data warehousing because its beginnings evolved slowly and without a formal definition of ’What is a data warehouse?" Ralph Kimball is credited withSanders-Healthcare-data-warehousing-2002
driving the semantics of this specialty in information systems. Prior to his early writings, there was no common language to describe the specialty. Designing, Developing, and Supporting anEnterprise Data Warehouse (EDW)In HealthcareCopyright 2002Dale SandersIntermountain Health Care1IntroductionTh Sanders-Healthcare-data-warehousing-2002 no formal language existed to describe anything formal, especially between other companies facing the same challenges. Networking with other professionals about data warehousing did not take off until the mid-1990s, coincidentally with the publication of Kimball's first book on the topic.5 Sanders-Healthcare-data-warehousing-2002Gọi ngay
Chat zalo
Facebook