1992
DOI: 10.1046/j.1537-2995.1992.32392213810.x
|View full text |Cite
|
Sign up to set email alerts
|

Improving blood transfusion practice: role of a computerized hospital information system

Abstract: The recent focus on medical risk and financial cost has prompted a need for better guidelines for prescribing the transfusion of blood components. In 1987, to respond to the issues of quality transfusion practice and accurate evaluation, LDS Hospital (Salt Lake City, UT) began using a computerized, knowledge-based blood-ordering system. Each transfusion request was reviewed and flagged by the computer when it did not meet the criteria established by the medical staff. The study reviewed the use of red cells, p… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
22
0

Year Published

1994
1994
2016
2016

Publication Types

Select...
7
3

Relationship

0
10

Authors

Journals

citations
Cited by 71 publications
(22 citation statements)
references
References 22 publications
0
22
0
Order By: Relevance
“…Clinicians have a right to override, but not permanently disable, any computer-generated clinical alert, except those prohibiting events that should never occur (e.g., ordering promethazine as intravenous push by peripheral vein [ 46 ]). software bugs); situation-specifi c clinical exceptions, as when a user's request for blood transfusion is denied by Clinical Decision Support (CDS) intervention that did not capture active bleeding since last hemoglobin result [ 47 ]; and, user-interface limitations, such as in limited screen space available to show most recent laboratory results near medication order [ 48 ]. In reality, computers are often not able to interpret or convey the clinical context for many reasons: unavailable or inaccurate data; errors in logical processing (e.g.…”
Section: Ability To Override Computer-generated Alertsmentioning
confidence: 99%
“…Clinicians have a right to override, but not permanently disable, any computer-generated clinical alert, except those prohibiting events that should never occur (e.g., ordering promethazine as intravenous push by peripheral vein [ 46 ]). software bugs); situation-specifi c clinical exceptions, as when a user's request for blood transfusion is denied by Clinical Decision Support (CDS) intervention that did not capture active bleeding since last hemoglobin result [ 47 ]; and, user-interface limitations, such as in limited screen space available to show most recent laboratory results near medication order [ 48 ]. In reality, computers are often not able to interpret or convey the clinical context for many reasons: unavailable or inaccurate data; errors in logical processing (e.g.…”
Section: Ability To Override Computer-generated Alertsmentioning
confidence: 99%
“…Af ter such initial review, it will be evident whether and where problems do exist at a particular hospital. For example, LDS Hospital in Utah reported a transfusion rate out of guide lines of only 0.37% [9]. Thus, overall, there is little or no problem if appropriate review criteria are used, and only continuous monitoring is needed.…”
Section: Identification Of the Problem(s)mentioning
confidence: 99%
“…14. 15 These same principles can be carried over to cost containment efforts by giving suggestions to physicians to use less costly antibiotics for the given diagnosis and bacteriology results. ~6.~7 Reminders to stop medications have also proven to be very effective at reducing costs and improving the quality of care, especially in the area of prophylactic perioperative antibiotics.…”
Section: Assuring Quality Of Carementioning
confidence: 99%