Health Information Management: Integrating Information Technology ...
Health Information Management: Integrating Information Technology ...
Health Information Management: Integrating Information Technology ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
170 STRATEGY, IMPLEMENTATION AND EVALUATION<br />
following chapter, in other words, we are more concerned with understanding,<br />
acting upon and structuring the implementation process than with the futile attempt<br />
to isolate individual contributors to either ‘success’ or ‘failure’.<br />
THREE MYTHS ABOUT IS IMPLEMENTATION<br />
Myth 1:<br />
PCIS implementation is the technical realization ofa<br />
planned system in an organization<br />
Overlooking the fact that PCIS implementation will fundamentally affect the<br />
health care organization’s structures and processes is one core reason for<br />
implementation failure. All too often, still, we hear project leaders or IS<br />
professionals speaking about ‘rolling out’ a system, or planning its ‘diffusion’.<br />
Such terminology underestimates that whether it is anticipated as such or not, the<br />
implementation of an information system in an organization involves the mutual<br />
transformation of the organization by the technology, and of the system by the<br />
organization. As emphasized in Chapter 2, this is a two-way process. On the one<br />
hand, the technology will affect the distribution and content of work tasks,<br />
change information flows, and affect the visibility of these work tasks and<br />
information flows. Because of this, it will also change relationships between<br />
(groups of) health care professionals and/or other staff. Electronic patient<br />
records, for example, inevitably change one’s recording practices, and raise<br />
questions about who will get access to whose data, under which conditions. This<br />
may seem self-evident and innocuous, but such changes inevitably trigger subtle<br />
(and sometimes not so subtle) social and political processes about who gets to<br />
fill in what parts of the record, who ‘owns’ what information, and who gets to<br />
check on whose work. In the case study of the implementation of a physician orderentry<br />
system mentioned above, Massaro describes how physicians reacted<br />
forcefully against the need to be more structured and precise in their writing of<br />
their orders. The fact that Massaro chose to describe the physicians’ slow<br />
adjustment to the system in terms of Kübler-Ross’s phases of mourning (denial,<br />
anger, acceptance and so forth) is an indication of the depth at which these<br />
change processes can affect existing organizational realities (Massaro 1993b).<br />
Such organizational processes in their turn inevitably affect the system.<br />
Pressures on the implementation staff may lead them to change authorization<br />
procedures, for example, or to throw out elaborately coded entry-screens that (in<br />
the eyes of the users) take up too much time.<br />
CASE VIGNETTE<br />
In a PCIS developed for a mental health care organization in the Netherlands,<br />
we found that discussions about access rights to patient information had resulted<br />
in an unwieldy explosion of over 25 different authorization levels. In this case,