18.05.2015 Views

Health Information Management: Integrating Information Technology ...

Health Information Management: Integrating Information Technology ...

Health Information Management: Integrating Information Technology ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

92 MEETING THE CHALLENGE<br />

improvization is crucial. Flexibility implies that the system is not more detailed<br />

than required, not more stringent than necessary, not more imperative than<br />

usable. A flexible PCIS or care path can be smoothly integrated in daily health<br />

care work. It implies not detailing thirty steps when three suffice; no choice of<br />

five thousand diagnostic categories when four hundred are sufficient. It implies,<br />

as illustrated above, that it should be possible, at each moment, to modify a<br />

standardized care path for an individual patient, or to take the patient out of the<br />

path. At that moment, the patient becomes one of the 20 per cent of patients that<br />

will be dealt with in the traditional fashion: step by step, with decisions taken at<br />

every turn, to optimally fit this specific patient’s problem.<br />

Flexibility also implies that the standard can be easily revised and adapted to<br />

local demands or to new scientific insights. Compared to Danish GP systems, for<br />

example, the coding schemes used in British primary care systems are easily<br />

adaptable, rendering the entire system more meaningful and acceptable to GPs<br />

(Winthereik in press). In addition, it should be possible to adapt standard care<br />

paths to newly emerging insights, for example based on feedback from<br />

aggregated health data tabulated from the support systems themselves.<br />

This might sound obvious and simple but it is not. The importance of local<br />

adaptability, for example, clashes with the demand that a standard is just that:<br />

standard. Everywhere applicable, everywhere similar. And simple, pragmatic<br />

standards that do not standardize more than necessary might lead to an unwieldy<br />

patchwork of overlapping and contradictory standards. Many standard<br />

developers abhor such disorder, and much effort is spent on attempts to develop<br />

(inter)national, all-encompassing models in which data, decision criteria and<br />

work processes are ordered in formal, unequivocal and universal ways. Both<br />

within several European countries and at the European level, many resources<br />

have been wasted at attempts to create the ‘ultimate’ model of the health care<br />

process. Likewise, much work has been—fruitlessly—invested in the quest for a<br />

modern Tower of Babel to resolve the vagueness and multiplicity of medical<br />

language. Such standards are inevitably very elaborate and complex, and contain<br />

a logic opaque to everyone except the designers themselves. Because these<br />

standards are so far removed from daily practice, they become difficult to<br />

implement and lead to manifold frictions in the care work. And once those<br />

standards are implemented, finally, they are very rigid and hard to change. Any<br />

proposed change to the complex whole has to be carefully investigated for its<br />

consistency and logic; any such proposition has to follow a long trajectory of<br />

(inter)national consultation rounds and committee meetings.<br />

The success of a redesign of the care process according to the first two<br />

principles is crucially dependent on the opportunities given to the professionals<br />

(and other users) to skilfully integrate the demands of the care paths and the<br />

PCIS in their work practice. Even for simple triage situations as described above<br />

(the outpatient clinic secretary categorizing a pregnant patient), decision support<br />

systems, when left to their own devices, are remarkably ineffective. Worried<br />

patients end up worrying more, and the tool’s answers more often than not fail to

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!