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.

90 MEETING THE CHALLENGE<br />

PCIS abides by the decision criteria, terminology and work procedures that are<br />

formalized and explicated in the PCIS. As we argued in Chapters 3 and 4, more<br />

powerful ICT functionality requires more alignment of the professionals’<br />

activities with the PCISs’ demands. If the PCIS alerts a physician about a task<br />

that now has to be done, he or she should be able to trust that the activities that<br />

led up to this alert were indeed properly executed as agreed. If the PCIS should<br />

support health care workers in making decisions, in addition, the health care<br />

workers have to use the basic algorithms and terminology the PCIS draws upon<br />

to properly interpret its advices. Only by ‘preprogramming’ into the PCIS which<br />

patients have to be dealt with how, can more coordination tasks be delegated to<br />

the PCIS.<br />

A keen redesign would also maximally reduce the need to disrupt each other’s<br />

ongoing work activities to announce or request something (see Chapter 6). For<br />

every outsider observer, this incessant flow of interruptions is astonishingly<br />

inefficient—yet a health care professional’s working day is often more typified<br />

by the constantly ringing phone, beeper and colleagues dropping in than by the<br />

ability to actually concentrate on the work that needs to be done. On the one<br />

hand, these constant interruptions are part and parcel of the ‘unpredictable’<br />

nature of health care work, and cannot (nor should) thus ever be completely<br />

avoided (see further). Yet smartly restructuring the task divisions, and using the<br />

PCIS, may importantly reduce such interruptions. Tasks can be made more<br />

independent when optimally sequenced, and, moreover, those later on in the<br />

process can be more fully informed through the PCIS about the steps that went<br />

before. In addition, more asynchronous modes of communication (more informal<br />

such as e-mail, but also highly structured such as through a care path’s template)<br />

can be used to facilitate communication.<br />

Ideally, the redesign should be based on information about the ‘performance’<br />

of the care path (in terms of health outcomes, efficiency, patient satisfaction,<br />

safety and so forth). Also, once in place, the effect of the new organization<br />

should be equally measured. This improvement process should, in principle, be<br />

continuous: new data analysis leading to new innovation needs, requiring new<br />

redesigns and new measurements, and so forth. This is the principle of continuous<br />

quality improvement, or performance management (see Walburg forthcoming).<br />

Having standardized care paths greatly facilitates these processes of continuous<br />

improvement. Data registration becomes more uniform (since the care paths are<br />

more alike), and may also become more extensive (see also below). In addition,<br />

the standardized care paths themselves form the framework for the interpretation<br />

of the gathered data: they are, after all, guidelines that link the data that would<br />

otherwise remain difficult to integrate. Finally, these guidelines can also suggest<br />

proper outcomes to monitor, and/or performance levels that may be taken as<br />

target for the professionals.<br />

Standardization is necessary, but only there where it enhances competencies<br />

and quality rather than reduces it. In the alternative scenario, receptionists’ and<br />

nurses’ tasks are highly standardized. Yet they received new tasks and

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

Saved successfully!

Ooh no, something went wrong!