Difference between revisions of "Unintended Consequences of HIT"

From Clinfowiki
Jump to: navigation, search
Line 5: Line 5:
 
These articles described specific cases in which HIT implementations have run up against severe unanticipated and unintended consequences. The goal of this section of the ClinfoWiki is to provide a forum for individuals to describe specific unintended consequences of HIT implementations that they have experienced.
 
These articles described specific cases in which HIT implementations have run up against severe unanticipated and unintended consequences. The goal of this section of the ClinfoWiki is to provide a forum for individuals to describe specific unintended consequences of HIT implementations that they have experienced.
  
Other non-peer-reviewed examples of unintended consequences:
+
== Other non-peer-reviewed examples of unintended consequences ==
# [[Flashing light used to notify nurses of new laboratory alerts]]
+
 
# [[Medical students write orders that residents will co-sign later]]
+
=== [[Flashing light used to notify nurses of new laboratory alerts]] ===
# [[Confusion over meaning of "cervical mass" e.g., re: cervix or cervical vertebrae]]
+
=== [[Medical students write orders that residents will co-sign later]] ===
# [[Use of common, floor-level computer login for clinical results review]]
+
=== [[Confusion over meaning of "cervical mass" e.g., re: cervix or cervical vertebrae]] ===
# [[Emergency department transfer orders canceled by system upon transfer to floor]]
+
=== [[Use of common, floor-level computer login for clinical results review]] ===
# [[X-Ray technician in room taking X-Ray before nurse is aware of order]]
+
=== [[Emergency department transfer orders canceled by system upon transfer to floor]] ===
# [[Orders on paper missed in system with hybrid electronic/paper systems]]
+
=== [[X-Ray technician in room taking X-Ray before nurse is aware of order]] ===
# [[Medications administered before pharmacy verification, because verification takes too long]]
+
=== [[Orders on paper missed in system with hybrid electronic/paper systems]] ===
# [[Add your example here...]]
+
=== Medications administered before pharmacy verification, because verification takes too long ===
 +
 
 +
Nurses report being impatient with the length of time it takes for pharmacy to approve medication orders (e.g., check for drug-drug interactions, verify dosage and route, etc.).  Because of the time lag, the nurses go ahead and administer the ordered meds, then check the verification afterwards.  This bypasses an important safety aspect of CPOE adoption.
 +
 
 +
=== [[Add your example here...]] ===

Revision as of 16:49, 18 October 2011

Unintended Consequences associated with Health Information Technology implementations abound. Over the past few years there have been several highly-publicized articles, for example:

These articles described specific cases in which HIT implementations have run up against severe unanticipated and unintended consequences. The goal of this section of the ClinfoWiki is to provide a forum for individuals to describe specific unintended consequences of HIT implementations that they have experienced.

Other non-peer-reviewed examples of unintended consequences

Flashing light used to notify nurses of new laboratory alerts

Medical students write orders that residents will co-sign later

Confusion over meaning of "cervical mass" e.g., re: cervix or cervical vertebrae

Use of common, floor-level computer login for clinical results review

Emergency department transfer orders canceled by system upon transfer to floor

X-Ray technician in room taking X-Ray before nurse is aware of order

Orders on paper missed in system with hybrid electronic/paper systems

Medications administered before pharmacy verification, because verification takes too long

Nurses report being impatient with the length of time it takes for pharmacy to approve medication orders (e.g., check for drug-drug interactions, verify dosage and route, etc.). Because of the time lag, the nurses go ahead and administer the ordered meds, then check the verification afterwards. This bypasses an important safety aspect of CPOE adoption.

Add your example here...