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.

THE CONTEXTUAL NATURE OF INFORMATION 67<br />

staging leukaemia. In this situation, this was a very efficient way of<br />

communicating between each other—clear to everyone involved. In a different<br />

clinical situation, this information might have meant something completely<br />

different. If the patient would have been older, and suffering from another<br />

chronic leukaemia, ‘Spleen—’ might have been taken to indicate that the<br />

physician had confirmed that the spleen had been surgically removed. Or, in the<br />

context of a patient who had been suffering from swollen axillar nodes, ‘Nodes—’<br />

would indicate that the physician had looked at these nodes and found that the<br />

swelling had disappeared.<br />

The mutual elaboration of medical data also evolves over time: the temporal<br />

dimension is as crucial to medical information as it is to a story. In the course of<br />

a patient’s illness trajectory, data items are constantly reinterpreted and<br />

reconstructed. Consider the following sequence of blood pressure measurements<br />

in the post-operative patient mentioned above: at 6 a.m., 120/70; at 9 a.m., 125/<br />

75; at 11 a.m., 115/65. If all other clinical signs would remain unchanged, then<br />

this series of readings would most likely be read as a ‘stable blood pressure’. But<br />

if the 1 p.m. reading would be 100/50, then the 11 p.m. reading would be<br />

reinterpreted as the beginning of the decline. At many medical wards, medical<br />

work is characterized by this ongoing (re)interpretation of the tendencies in<br />

graphs and tables: is this temperature going up? Is this haemoglobin level stable?<br />

Again, medical information is not a timeless collection of unchangeable entities,<br />

that retain their essence once captured in a record.<br />

So far, then, we have seen two ways in which medical information is<br />

entangled with the context of its production: medical data are tied to the purpose<br />

of their generation and they are part of an evolving array of medical data which<br />

continually reshapes their meanings. The two are closely related: doctors are<br />

aware of the constantly evolving nature of the data they produce, and they<br />

generate their data accordingly. When Agnes checked upon this patient the next<br />

day, she did not change the entry for the blood pressure she had entered the day<br />

before (‘135/70’), although the monitor now read ‘125/65’. For all practical<br />

purposes, and in this particular, stable patient, this was not a difference worthy of<br />

registration. Agnes does not intend the ‘S1 S2’ and ‘none’ entries to stand for an<br />

in-depth scrutiny of this patient at that particular time. Rather, those marks are<br />

intended to convey an ongoing monitoring process, in which, at this particular<br />

moment, nothing noteworthy has changed or is expected to change within the<br />

next monitoring episode.<br />

The third way in which medical information is inextricably context-bound is<br />

that ‘physicians [and other health workers] typically asses the adequacy of<br />

medical information on the basis of the perceived credibility of the source’<br />

(Cicourel 1990). That is: whenever a physician takes a specific piece of<br />

information into account, s/he will assess that information in the light of who or<br />

what generated it. When the supervising senior physician at the ICU encountered<br />

Agnes’s progress notes during his rounds later the same day, he just nodded and<br />

moved to the next patient. Agnes is an experienced resident, who has been

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

Saved successfully!

Ooh no, something went wrong!