Health Information Management: Integrating Information Technology ...

More documents

Recommendations

Info

STRATEGY, IMPLEMENTATION AND EVALUATION 161 PRIORITIES FOR THE INFORMATION MANAGEMENT AND FINANCIAL PRECONDITIONS The previous paragraph listed what should happen as far as ambition and necessity are concerned. This deliberately did not consider the financial aspects. Neither was a ranking of importance made for the desired projects and activities. In all probability, however, an initial tally of the necessary manpower and finances for executing the projects and activities will produce figures above those reserved by the health care organization for information management. Two questions then arise: how large should the health care organization’s expenditure be on information management, and what ranking principle can be applied to the sequence of projects and activities? Financing, not budgeting How large the expenditure on information management should be, should ideally be determined by the expected returns. The tally of business cases (determined per project/activity) determines the IT expenditure in a multi-year estimate. Unfortunately, the returns of PCISs can only partly be expressed in economic terms. Benefits include the increase in effectiveness of care, and the satisfaction of patients and care professionals (see also Chapter 11). The quality, speed and scope of information provision should improve, after all. Also, there are intangible benefits, such as being a front-line organization, and/or being an attractive organization for care professionals and researchers to work. In addition, the organizational impact and process changes associated with IT implementation make it difficult to calculate a simple economic yield (see Chapter 11). Listing the tangible and intangible information management benefits must be undertaken, however. No matter how imperfect, it provides a footing for the discussion on the funds to be channelled to information management. Simultaneously, comparative data from other information-intensive industries are helpful in the strategic discussion on the percentage of the budget that should be devoted to information management. <strong>Information</strong>-intensive, for-profit companies currently spend approximately 12 per cent of their annual costs on IT. The expenditure by hospitals, for example, is far below this; between 2 per cent and 4 per cent. For other health care organizations, these numbers are generally even lower. These figures make clear that health care organizations—a highly information-intensive industry, after all! —can benefit from pro-actively drawing up a multi-year budget that takes account of rising expenditures for information management. (The expectation of a rise in expenditures can also be built bottomup, by making a forward projection based on the expansion of the number of users, expansion of functionality, and replacement of existing systems.)
162 DEVELOPING THE INFORMATION STRATEGY Figure 8.9 Ranking principle for projects. Ultimately it is up to the health care organization’s BoD to agree on expenditure on information management in a multi-year framework, in line with the ambition, the strategy and the expected yields. Prioritizing projects and activities to be carried out The projects and activities that stem from the IT ambition level, in conjunction with the guidelines, can usually not all be carried out concurrently. A ranking principle needs to be agreed to determine the sequence. Figure 8.9 shows the outline for such a ranking principle. The starting point is that available resources (both manpower and financial resources) are introduced from top to bottom. Each project is added to the project list (projects are proposed by line managers). Projects which do not fall within the previous categories are placed ‘below the line’. The priority 1 projects are first subtracted from the total available budget. A percentile division for priorities 2, 3 and 4 is then made from the remainder. For priority 5 ‘projects below the line’ no budget will be available in the relevant time frame. Priority 1 are the information management infrastructure projects and activities. This refers to the ‘fundamental’ infrastructural projects, both organizational as well as hardware and software, which are preconditions for the other projects, ambitions and guidelines. For example the elaboration of the guidelines for standardization, or the addition of key-users, etc. Priority 2 are the projects and activities within the priority areas. These are the projects and activities required for fulfilling the ambition. The health care organization needs to make a ranking of the ambition per sector from the conceptual model. Derived from this is a ranking of the projects within the sector areas. The ranking determines the sequence of diminishing importance and cuts
Page 2 and 3:
Health Information Management In al
Page 4 and 5:
Health Information Management Integ
Page 6 and 7:
Contents List of illustrations vii
Page 8 and 9:
Illustrations FIGURES 3.1 Medicatio
Page 10 and 11:
Contributors Marc Berg is a physici
Page 12 and 13:
Series preface In almost all Wester
Page 14 and 15:
Acknowledgements I would like to th
Page 16 and 17:
Chapter 1 Introduction In all Weste
Page 18 and 19:
INTRODUCTION 3 touch upon the deplo
Page 20 and 21:
INTRODUCTION 5 can draw upon to mai
Page 22 and 23:
INTRODUCTION 7 Physician Order Entr
Page 24 and 25:
Part I Starting points Understandin
Page 26 and 27:
WAITING FOR GODOT 11 KEY TERMS ■
Page 28 and 29:
WAITING FOR GODOT 13 Netherlands an
Page 30 and 31:
WAITING FOR GODOT 15 facts to show
Page 32 and 33:
WAITING FOR GODOT 17 (Lewinski-Corw
Page 34 and 35:
WAITING FOR GODOT 19 In most cases,
Page 36 and 37:
WAITING FOR GODOT 21 (Anonymous 191
Page 38 and 39:
WAITING FOR GODOT 23 Because of the
Page 40 and 41:
WAITING FOR GODOT 25 they simply sa
Page 42 and 43:
WAITING FOR GODOT 27 expected. Stil
Page 44 and 45:
WAITING FOR GODOT 29 organize their
Page 46 and 47:
WAITING FOR GODOT 31 performance in
Page 48 and 49:
WAITING FOR GODOT 33 different HIS
Page 50 and 51:
WAITING FOR GODOT 35 CONCLUSION: TH
Page 52 and 53:
WAITING FOR GODOT 37 assumption tha
Page 54 and 55:
WAITING FOR GODOT 39 Anonymous (191
Page 56 and 57:
WAITING FOR GODOT 41 Berg, M. (1997
Page 58 and 59:
Chapter 3 Health care work and pati
Page 60 and 61:
HEALTH CARE WORK AND INFORMATION SY
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
THE CONTEXTUAL NATURE OF INFORMATIO
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Chapter 5 Meeting the challenge Int
Page 96 and 97:
STARTING POINTS 81 ‘gender, race,
Page 98 and 99:
STARTING POINTS 83 Now, imagine an
Page 100 and 101:
STARTING POINTS 85 organization,
Page 102 and 103:
STARTING POINTS 87 Figure 5.2 Incre
Page 104 and 105:
STARTING POINTS 89 already overflow
Page 106 and 107:
STARTING POINTS 91 responsibilities
Page 108 and 109:
STARTING POINTS 93 answer the quest
Page 110 and 111:
STARTING POINTS 95 Kohn, L.T., J.M.
Page 112 and 113:
Chapter 6 Designing interactions En
Page 114 and 115:
DESIGNING INTERACTIONS 99 the way t
Page 116 and 117:
DESIGNING INTERACTIONS 101 1 Identi
Page 118 and 119:
DESIGNING INTERACTIONS 103 the deve
Page 120 and 121:
DESIGNING INTERACTIONS 105 communic
Page 122 and 123:
DESIGNING INTERACTIONS 107 Figure 6
Page 124 and 125:
DESIGNING INTERACTIONS 109 ■ Figu
Page 126 and 127: DESIGNING INTERACTIONS 111 measurem
Page 128 and 129: DESIGNING INTERACTIONS 113 Figure 6
Page 130 and 131: DESIGNING INTERACTIONS 115 Figure 6
Page 132 and 133: DESIGNING INTERACTIONS 117 Covell D
Page 134 and 135: Part II Information strategy, imple
Page 136 and 137: INFORMATION STRATEGY: AN INTRODUCTI
Page 152 and 153: Chapter 8 Developing the informatio
Page 154 and 155: STRATEGY, IMPLEMENTATION AND EVALUA
Page 172 and 173: Guidelines for information system d
Page 180 and 181: Chapter 9 Implementing information
Page 182 and 183: IMPLEMENTING INFORMATION SYSTEMS 16
Page 198 and 199: Chapter 10 Project management of in
Page 226 and 227:
STRATEGY, IMPLEMENTATION AND EVALUA
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 236 and 237:
Index accumulation 53-4, 61, 73-4,
Page 238 and 239:
INDEX 223 contingent and emergent c
Page 240 and 241:
INDEX 225 satisfaction 176 patient
Page 242:
INDEX 227 support 164 technology de
show all

Health Information Management: Integrating Information Technology ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?