Health Information Management: Integrating Information Technology ...
Health Information Management: Integrating Information Technology ...
Health Information Management: Integrating Information Technology ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
STARTING POINTS 93<br />
answer the question as the patient phrased it. To translate between patient and<br />
tool requires interpretation by the secretary— and knowledge about what the<br />
tool’s purpose is, and what the meaning of the preset categories is. Similarly,<br />
paramedics responsible for a diagnostic ‘pre-trajectory’ should be able to react<br />
properly to a patient whose situation is such that a test is unlikely to provide<br />
clinically relevant information. It requires much skill to act appropriately in such<br />
situations: knowledge about the test’s purposes, and clinical skills to realize its<br />
inappropriateness.<br />
For the potential synergy between the PCIS and professional work to emerge,<br />
then, the tool’s coordination tasks should not be seen as self-sufficient. In the<br />
common parlance of ‘intelligent agents’ and ‘computerized care paths’, this<br />
imperative is easily forgotten. Yet we already concluded that constantly bridging<br />
the needs of the patient or the work situation and the tool’s or care path’s<br />
demands is a highly skilled activity. It is crucial that the secretary, the<br />
paramedics and other users are supported in this task: through formal training,<br />
but also through the opportunity to constantly learn from and interact with the<br />
other actors in the ‘care chain’. Such ‘lateral connections’ between individuals<br />
that hold seemingly independent positions in the formal ‘workflow’ are essential<br />
to facilitate this articulation work (Brown and Duguid 2000). This comes down<br />
to facilitating physical access to each other, and enhancing unstructured modes<br />
of communication such as e-mail or telephone. This implies not being too rigid<br />
when trying to reduce interferences: when the care path or PCIS controls the<br />
work process so rigidly that the receptionist is no longer in touch with the<br />
specialist, then the former will fail to grasp just what the triage aims to do. Their<br />
tasks may be formally separated: according to a workflow diagram, these two<br />
individuals need not be in direct personal contact with one another. But without<br />
adequate and unstructured contacts between the two, they lose the opportunity to<br />
inform and learn from each other. These are simple things that may seem<br />
insignificant in the light of the larger organizational changes that the PCIS and<br />
care paths bring. Yet they make the difference between being able or not to<br />
integrate the functionality of these standardizing tools in the ongoing flow of<br />
work. Thereby, they make the difference between an innovation that clashes with<br />
that flow of work, and an innovation that lifts professionals’ work to a higher<br />
level.<br />
CONCLUSION<br />
In this chapter, we greatly increased the stakes. This was nothing more or less<br />
than a highly ambitious—yet necessary—requirement specification for the<br />
redesign of care delivery at the level of the actual care processes. This redesign is<br />
necessary because it is the only way to ensure high quality of care without<br />
sacrificing one dimension (say ‘effectivity’) to another (say ‘efficiency’). It is<br />
ambitious, because concrete, successful examples of similar attempts are hard to<br />
find in Western health care practices. A systematic approach such as proposed