Introduction to Hospital Information Systems

Module M30c

Contents

Audience and Objectives Bibliography, References, and Acknowledgements

About this document...

To return to the Table of Contents, click on the rainbow bar wherever you see it.

Definition And Purpose Of Hospital Information Systems

What is a Hospital Information System? What is it for?

A Hospital Information System (HIS) is a computerized system designed to meet the information needs of all (or most) of a hospital. This includes many diverse types of data, such as:

This module focuses only on parts of Hospital Information Systems directly involved with patient care.

Advantages of Hospital Information Systems

Why all the fuss about Hospital Information Systems? What's so great about them? A 1992 survey of executive nurses (Simpson 1992) listed these benefits: But what about the cost? Here are some interesting estimates:

Development And Future Of Hospital Information Systems

Early hospital computer systems developed from business computing systems in the late 1950s and early 1960s, and were used for accounting, billing, inventory and similar business-related functions.

Others were developed during the 1960s primarily for storing patient information to be used by medical staff.

These types of systems have been slow to integrate. Surveys (Dorenfest 1987, 1992) of hospitals since 1980 have shown that less than half of community hospitals have full Hospital Information Systems, mainly because few were available to integrate all the functions needed. Research and teaching hospitals presumably have a much higher usage of Hospital Information Systems.

The future is not certain. Several factors are at work:

Types Of Hospital Information System

Hospital Information Systems come in many flavors, depending on whether they are based on...

Centralized vs. Decentralized

This distinction is based on whether information is kept primarily in a central computer, or is distributed over a number of workstations or servers located around the hospital.

There are variations on this; for example, a system may be partially centralized but integrated with powerful and somewhat independent satellite systems. Examples:

Business Oriented vs. Patient Oriented

Though both these types of systems handle patient information, the orientation of the original designers may affect the procedures and general "character" of a HIS.

Terminal vs. Workstation Oriented

Terminals and workstations are computer devices that often look very similar: both usually have a keyboard and a CRT display screen, and are often confused with one another. What's the difference?

Terminals are electronic devices that let humans communicate with a computer. They are generally connected to minicomputers or mainframes, which could be close by or halfway around the world. They may have some minor processing power of their own, but are generally not able to do anything if not attached to a (functioning) computer.

Workstations are computers designed for professional use by one person at a time. They are fully functional computers on their own, but they can be networked to other workstations, mainframes, or minicomputers. (The term workstation can refer to any personal computer, but is often applied to specially powerful microcomputers.)

Terminal-oriented systems are by nature very centralized, since the terminal can't do anything on their own. Workstation-oriented systems can be either centralized or decentralized, because the processing power of the workstation gives system designers a lot of flexibility.

The trend in most types of computer work is toward decentralization, but this trend is somewhat slower in hospitals because of the high risks associated with failure in hospitlas and the consequent reluctance to change systems that are working now.

Still, workstation-oriented systems offer a number of advantages over terminal-oriented ones:

How Hospital Information Systems Are Organized

Here are diagrams of some of the possible configurations discussed above. Of course, these are only a representative sampling.

Symbols used in these diagrams:


(Figure 0)

How do these different systems affect you?

Nursing Informatics: What It Is And How It Impacts Hospital Caregivers

What is Nursing Informatics; Who is Involved?

Nursing Informatics is the systematic application of nursing science to computer systems, in order to provide clinical information in the most convenient form. Nursing Informatics provides a conceptual framework for studying the type of information needed in nursing.

Nurses may specialize in informatics, taking jobs with titles such as:

The need for Nursing Informatics

Nursing Informatics arose from the realization that nobody can provide the exact information needed by nurses, except the nurses themselves. Physicians have their own perspective on what is needed; computer scientists are involved in the technical details of computer systems. If nurses and other medical caregivers don't take an active role in deciding exactly what information is needed and how to present it, it certainly won't drop out of the sky!

Nurses identified as informatics specialists numbered 15 in 1981; there were over 5,000 by 1991 (Saba & McCormick 1996). Many hospitals, recognizing the need for this type of person, select nurses with computer facility to study and become the resident specialist.

Impact of Nursing Informatics

In hospitals, nursing informatics specialists serve to: Nursing informatics plays a larger role on the national and international level:

Where is Nursing Informatics Used?

Nursing informatics specialists provide planning and guidance in creating computer systems for:

Patient Documentation Systems

From the perspective of the medical caregiver, Hospital Information Systems are tools for storing and retrieving patient information. What information is kept in these systems?

Getting Computer Access Where It Needs To Be In Hospitals

When medical caregivers work with Hospital Information Systems, what is the most convenient and efficient place to give them access to it? For most inpatient settings, there are usually three locations available:
  1. By the patient's bed
  2. In the hall close to the patient's bed
  3. In a staff-only area such as the nursing station or ward office
By the patient's bed
Bedside placement is necessary for monitoring systems and intervention control devices like infusion pumps. For documentation of patient condition, however, there is no advantage to this. A study (Marr et al. 1993) found that reporting did not improve when nurses had bedside access to the HIS, since most of their note were entered either outside patients' rooms, or in the rooms of other patients. However, putting HIS access by the bedside did improve the use of computerized patient care plans, calculation of patient acuity, and billing for nursing services.
In the hall
Hallway placement of HIS access appears to be gaining popularity. It allows nurses to do their documentation very soon after leaving the patient's bedside, without the distraction of having the patient present, possibly demanding attention. There is a security risk in the hall, as unauthorized individuals may gain information about a patient's condition by peering over the nurse's shoulder.
Staff-only area
Placing access in areas where only staff are permitted has the advantage of greater security. But the price is loss of convenience and timeliness, as the staff need to take a hike from the patient's room every time they need to enter information.
Other possibilities
"Electronic clipboards" (similar to the devices used by delivery companies such as United Parcel Service and Federal Express) have great promise in making it easier to enter reports in a timely manner. One possible disadvantage: "Whose room did I leave that confounded clipboard in this time?!?"

Working with Hospital Information Systems

What are the most important things a Hospital Information System does for nurses? Here's what 340 nursing administrators said, when surveyed in 1992 (Simpson, 1992):
  1. Order entry
  2. Integrate care plans with charting functions
  3. Prepared patient care plans
  4. Track medication administration
  5. Discharge planning
  6. Determine patient acuity level (severity of patient's condition)
  7. Provide flexibility to customize the system for your hospital
  8. Report generator capability
  9. Prepare nursing assessments
  10. Patient education
  11. Quality assurance
  12. Access to information in many departments of the hospital
  13. Admission interview
  14. Patient acuity list
  15. Cost tracking and reporting
  16. Electronic mail to other departments
  17. Graphical display of patient data
  18. Automated medical record
  19. Bedside capability (but only 29% said they had this)
  20. Case management of critical pathways

Bibliography, References, and Acknowledgments

Much of the information discussed here is drawn from Saba & McCormick 1996.
Dorenfest, S. 1993.
The Dorenfest 3000+ Database and the Dorenfest Guide to the Hospital Information Systems Market. Chicago: published by the author. Quoted in Saba and McCormick 1996, p. 190.
Marr, P., E. Duthie, K. Glassman et al. 1993.
Bedside terminals and quality of nursing documentation. Computers in Nursing, 11(4), 176-182. Quoted in Saba and McCormick 1996, p.371.
Saba, V. and K. McCormick. 1996.
Essentials of Computers for Nurses. Second edition. New York: McGraw-Hill.
Simpson, R. 1992.
What nursing leaders are saying about technology. Nursing Management, 23(7), 28-32. Quoted in Saba & McCormick, pp. 358-9.

Audience:

This module is for people with a general knowledge of computers (modules G01c-G05c) who want to know more about Hospital Information Systems. An overview of the uses of computers in hospitals is helpful (module M08c).

Objectives

When you successfully complete this lesson, you will be able to...

About this document...

Module M30c: Introduction to Hospital Information Systems

Review: Reviewm30cr.txt
Author:
Laurence J. Krieg
Institution:
Department of Computer Information Systems, Washtenaw Community College
Date:
Original 9 April 1996; review added 26 March 1999
Copyright ©1996, 1999  Laurence J. Krieg. All rights reserved. Instructors: you may use this material in your classes so long as no charge is made beyond duplication costs, and so long as this notice appears with the text. Students: you may duplicate this material for your own educational purposes. All other uses: contact the author for permission.