System for monitoring caregivers and equipment

Information

  • Patent Grant
  • 9230421
  • Patent Number
    9,230,421
  • Date Filed
    Monday, June 30, 2014
    9 years ago
  • Date Issued
    Tuesday, January 5, 2016
    8 years ago
Abstract
A hospital monitoring system for monitoring hospital personnel, a plurality of patient locations for patients, and associated devices is configured to control the associated devices based on the presence of hospital personnel or alarms.
Description
BACKGROUND AND SUMMARY OF THE INVENTION

The present invention relates to a hospital monitoring system, and more particularly, to hospital monitoring system for monitoring hospital personnel, a plurality of patient locations for patients, and associated devices.


Hospital staff, including doctors, nurses, physician assistants, orderlies, etc., provide patient care while the patient is undergoing treatment and/or therapy during a hospital visit. A number of systems have been developed to facilitate providing patient care, such as personnel locating systems, nurse call systems, bed status information systems, and patient monitoring devices. Details of such systems are disclosed in U.S. Pat. No. 6,067,019 (Bed Exit Detection Apparatus); U.S. Pat. No. 5,838,223 (Patient/Nurse Call System); U.S. Pat. No. 5,808,552 (Patient Detection System for a Patient-Support Device); U.S. Pat. No. 5,699,038 (Bed Status Information System for Hospital Beds); U.S. Pat. No. 5,561,412 (Patient/Nurse Call System); and U.S. Pat. No. 5,537,095 (Incontinence Detection Device), the disclosures of which are incorporated herein by reference. Additionally, co-pending U.S. Nonprovisional application Ser. No. 09/849,580, filed May 4, 2001, entitled “Patient Point of Care Computer System,” and Ser. No. 09/848,941, filed May 4, 2001, entitled “Remote Control For a Hospital Bed,” the disclosures of which are incorporated herein by reference, also disclose systems that have been developed to facilitate providing patient care.


The systems disclosed above facilitate various patient alarms, such as a patient exiting a bed, an incontinence event, or an emergency call for a caregiver. Typically, a caregiver will enter the patient's room when responding to an alarm. However, the caregiver often must manually silence the alarm, adjust the room lighting, or shut off a television or radio prior to attending to the patient. This manual preparation of the working environment may distract the caregiver and further increases response time to critical alarms. The disclosure is directed toward the automatic silencing of such alarms and/or preparing the working environment when a responsive caregiver enters the patient's room. Further, the disclosure is directed toward preparing the working environment when an alarm is received. Further still, the disclosure is directed toward preparing the working environment when an alarm is received, subject to environmental and patient control overrides depending on the nature of the alarm and time of the alarm.


The system disclosed also provides for automatic lockouts of patient and environmental controls when the caregiver enters the room, regardless of the presence of an alarm. As a caregiver makes his or her rounds, the caregiver may need to tend to the patient's needs. Often a caregiver must ensure that patient activated controls are locked out during this time, as the patient may inadvertently activate a control and interfere with the caregiver's duties. Also disclosed is a system that provides for the automatic enablement of patient controls, bed controls, and/or environmental controls when a caregiver is in the room.


One illustrative embodiment prevents the status of bed lockouts from being changed without an authorized caregiver within the room. When the caregiver enters the room, the system receives a caregiver identification signal from a caregiver badge. After the system authenticates the identification signal, the system then permits the bed lockout status to be changed. The bed lockout controls prevent the patient on bed from actuating certain controls. These lockouts are typically actuated by pressing a button or a combination of two or more buttons on the bed to lock out various bed controls, environmental controls, or other functions.


Another embodiment is designed for use with beds which are movable from a generally flat bed position to a chair position. In this embodiment of the present invention, the bed is unable to move to a chair position unless an authorized caregiver is located within the room. Again, the system must receive and authenticate the identification signal from caregiver badge before the bed is permitted to move to the chair position.


In yet another embodiment, the status of patient environmental controls adjacent a bed is automatically altered when the caregiver enters the room. For example, in one embodiment the sound on a TV/radio device is muted and specific light sources are activated when the caregiver enters the room. A system receives the caregiver identification signal. After the system authenticates the identification signal, the system instructs the TV/radio device to mute all sound and the light source to activate specific lights. In another embodiment, the system locks out one or more of the environmental controls within the room once the control unit authenticates the identification signal from the caregiver badge. Therefore, the patient can no longer control the environmental functions such as, for example, the radio, television or lighting when an authorized caregiver is in the room.


According to the invention, a hospital monitoring system for monitoring hospital personnel, a plurality of patient locations for patients, and associated devices is disclosed. The system comprises a plurality of transmitters carried by hospital personnel, each transmitter periodically transmitting a transmitter signal unique to that transmitter; a plurality of receivers, each receiver corresponding to a patient location, the receivers receiving the transmitter signals and outputting a receiver signal; and a computer coupled to the associated devices, the computer configured to receive the receiver signals and determine the presence of hospital personnel in the patient locations, the computer further configured to alter device states based on the presence of hospital personnel.


Also according to the invention, a method of controlling devices in a patient location is provided. The method comprises the steps of associating the patient location to a patient; associating devices to the patient location; determining the presence of hospital personnel in the patient location; and altering the state of the devices based the presence of hospital personnel.


Also according to the invention, a hospital monitoring system for monitoring hospital personnel, a plurality of patient locations for patients, and associated devices is provided. The system comprises a locating and tracking system configured to locate and track hospital personnel located in the plurality of patient locations; a computer coupled to the associated devices and the locating and tracking system, the computer configured to determine the presence of hospital personnel in the patient locations from the locating and tracking system, the computer further configured to alter device states based on the presence of hospital personnel. The computer also includes a database, the database comprising a patient database, the patient database associated each patient with a patient location; a hospital personnel database, the hospital personnel database associating each hospital personnel with a caregiver or non-caregiver class, the hospital personnel database further associating hospital personnel with a patient; and an alarm database, the alarm database associating a plurality of alarms with the hospital personnel.


Additional features of the invention will become apparent to those skilled in the art upon consideration of the following detailed description of illustrated embodiments exemplifying the best mode of carrying out the invention as presently perceived.





BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description particularly refers to the accompanying figures in which:



FIG. 1 is a block diagram illustrating the components of the hospital monitoring and control system of the present invention;



FIG. 2 is a perspective view of a portion of a hospital room which illustrates a patient station in a patient room and the physical arrangement of other components, including an incontinence detection device;



FIG. 3 depicts a database structure used to associate patients with hospital personnel, and associate hospital personnel with alarms;



FIG. 4 depicts the database association for a specific patient record, the patient associated with hospital personnel, and the hospital personnel associated with alarms;



FIG. 5 is a flowchart of an illustrative embodiment of an automatic alarm silencing process that includes association of patients, hospital personnel and alarms;



FIG. 6 is a flowchart of another illustrative embodiment of an automatic alarm silencing process that includes association of patients and hospital personnel;



FIG. 7 is a flowchart of an illustrative embodiment of an alarm silencing process in conjunction with a patient control lockout that includes a lockout of patient activated controls;



FIG. 8 is a flowchart of another illustrative embodiment of an automatic alarm silencing process in conjunction with a patient control lockout that includes a lockout of patient activated controls upon the occurrence of the alarm;



FIG. 9 is a flow chart of another illustrative embodiment describing a process that locks out patient bed controls and environmental controls based on the alarm priority;



FIG. 10 is a flow chart of another illustrative embodiment describing a process that prepares the patient environment for the caregiver based on the alarm priority;



FIG. 11 is a flow chart of another illustrative embodiment describing a process that prepares the patient environment for the caregiver based on the alarm priority, with each environmental preparation subject to an override condition;



FIG. 12 depicts the database association of the alarm database, the database containing Type, Priority, Lockouts and Overrides fields;



FIG. 13 is a block diagram illustrating the control circuitry for several environmental controls;



FIG. 14 is a block diagram illustrating the bed controller and associated bed controls;



FIG. 15 is a flow chart of another illustrative embodiment describing a process which lockouts and/or alters selected patient and environmental controls when a caregiver is present in the room; and



FIG. 16 is a flow chart of another illustrative embodiment describing a process which enables selected patient and environmental controls when a caregiver is present the room.





DETAILED DESCRIPTION OF THE DRAWING

Referring now to the drawings, FIGS. 1 and 2 illustrates a block diagram of the hospital monitoring and control system 10 of the present invention, and an illustrative hospital environment in which the system is utilized.



FIG. 2 illustrates a patient room 130 which includes a patient station 22 and the physical arrangement of other components, including an incontinence detection device 65. The patient station 22 is illustratively a component of a nurse call system 40. Caregiver 110 wears a badge 24 which clips to the caregiver's 110 clothing. The badge 24 transmits a pulse-coded signal, preferably infrared or RF, which is received by receiver 25, which is preferably located at the patient station 22, and/or an overhead receiver 125 so that the location and tracking systems 20 can determine and continuously update locations of caregivers 110 on duty. Overhead light 122 provides room illumination, and reading light 123 provides reading illumination for the patient. Overhead light 122 and reading light 123 are controlled by light controls 132 and 133, respectively.


Pillow unit 28 connects via a cable 26 to a receptacle 27 which, in turn, is connected to the nurse call system 40. Pillow unit 28 allows the patient 100 to manually place a nurse call or alarm via nurse call system 40. Pillow unit also allows patient 100 access to bed 90 controls and environmental controls 50. Bed 90 controls are also accessible by the caregiver 110 via control panel 140.


Incontinence detection device 65 is interposed between the bed 90 and patient 110. Incontinence detection device 65 is connected to the computer 12 via bed 90 electronics and cable 91 via receptacle 27.


The system 10 illustratively includes a computer 12 configured to monitor various system alarms, device status, the hospital personnel information, and patient information. Computer 12 is coupled to a location and tracking system 20. Location and tracking system 20 monitors and tracks the location of hospital personnel, patients and equipment within the hospital. Computer 12 is also connected to nurse call system 40. Nurse call system 40 is associated with various alarms 42. The alarms 42 illustratively include the following:

















ALARM
PRIORITY
GENERATED BY









Code Blue
1
Human/Input Device



Staff Emergency
2
Human/Input Device



Bathroom
3
Human/Input Device



Shower
4
Human/Input Device



Patient Equipment
5
Automatic/Input Device










Illustratively, the alarms 42 will place a call to a caregiver through location and tracking system 20 and nurse call system 40.


Computer 12 is also connected to hospital bed 90. Hospital bed 90 is associated with alarms 92. Alarms 92 include bed malfunction alarms and/or bed exit alarms, and incontinence detection device 65 alarms. Illustratively, alarms 92 will place a call to a caregiver through location and tracking system 20 and nurse call system 40.


Bed 90 includes frame and resting surface devices 190 adjust the position of bed 90 and the position and shape of the resting surface, as illustrated in FIG. 14. In addition, other devices are included in frame and resting surface devices 190, such as resting surface vibration, temperature and firmness controls. Caregiver 110 accesses and changes the state of frame and resting surface devices 190 via control panel 140, shown in FIG. 2. FIG. 14 shows several frame and resting surface devices 190, however FIG. 14 should not be considered an exhaustive list. Examples of frame and resting surface devices 190 include head position control 275, back position control 280, seat/thigh position control 285, heating control 290, firming bladder 295, retracting footboard control 300, turn assist bladder control 305 and vibration control 310.


Head position control 275, back position control 280 and seat/thigh position control 285 all alter the shape of the resting surface of bed 90. Head position control 275 raises or lowers the head position of the resting surface generally coincident with the head of the patient. Back position control 280 raises or lowers the middle portion of the resting surface generally coincident with the back of the patient. Seat/thigh position control 285 raises or lowers the lower portion of the resting surface generally coincident with the seat and thighs of a patient.


Heating control 290 controls the temperature of the resting surface of bed 90. Similarly, vibration control 310 controls the vibratory action of the resting surface of bed 90. Firming bladder control 295 controls the firmness of the resting surface of bed 90. Retracting footboard control 300 adjusts the length of the foot portion of the resting surface of bed 90. This allows bed 90 to accommodate patients of various heights comfortably. Turn assist bladder control 305 controls rotation of the patient to reduce the likelihood of pulmonary complications. An interface pressure sensor and controller for a patient support surface such as an air mattress may also be coupled to the controller 190.


Computer 12 is also connected to coupler 60. The computer 12 may be coupled to monitors 26, treatment devices 72, and therapy devices 82 through coupler 60. Illustratively, coupler 60 may be an RS-232 compatible cable or other suitable connector, such as a RS-485 compatible cable, Ethernet, or other network connection device known to those of ordinary skill in the art. Computer 12 processes signals from the monitors 62, treatment devices 72, and therapy devices 82 on a real time basis. The monitors 62, treatment devices 72, and therapy devices 82 include, but are not limited to, heart rate monitors, temperature sensors, blood pressure monitors (invasive and noninvasive), EKG monitors, blood oxygen sensors, capnographs, ventilators, IV pumps, scales, chest drainage monitors, and the like. Monitors 62, treatment devices 72 and therapy devices 82 have associated alarms 64, 74 and 84, respectively. Illustratively, alarms 64, 74, and 84 will place a call to a caregiver through location and tracking system 20 and nurse call system 40.


Computer 12 is also connected to environmental devices 50. Alarm 52 is associated with environmental devices 50. Environmental devices 50 illustratively include temperature control devices, such as a thermostat, and humidity control devices, such as a humidifier. Additionally, environmental devices 50 illustratively include entertainment devices such as a television/radio 120, and lighting such as overhead light 122 and reading light 123, all of which do not have alarms associated therewith.


Environmental devices 50 control environmental parameters within the patient room. FIG. 13 shows several different environmental devices 50; however FIG. 13 should not be considered an exhaustive list. Examples of environmental devices 50 include TV/radio 120 control 345, room temperature control 350 and lighting control 355, which control overhead light 122 and reading light 123.


TV/radio 120 control 345 controls the functions of the TV/radio 120 in the room. Room temperature control 350 is a thermostat control for altering the temperature of the patient's room. Lighting control 355 controls overhead light 122 and reading light 123, and their brightness level.


In one embodiment, the status of the environmental controls is automatically altered when caregiver 110 enters the room. For example, the sound on TV/radio 120 is muted and overhead light 122 and/or reading light 123 controlled by lighting control 355 are activated. When caregiver 110 enters the room, receiver 25 receives the caregiver identification signal broadcast by caregiver badge 24. After the computer 12 authenticates the identification signal, the computer 12 instructs TV/radio 120 control 345 to mute all sound and lighting device 355 to illuminate overhead light 122 and reading light 123.


In another embodiment of the present invention, the computer 12 overrides one or more of the environmental controls within the room once the computer 12 authenticates the identification signal from the badge 24. In other words, the patient can no longer control the environmental functions such as, for example, the radio, television or lighting when an authorized caregiver 110 is in the room.


Bed 90 includes lockout controls which prevent the patient 100 on bed 90 from actuating certain controls. These lockouts are typically actuated by pressing a button or a combination of two or more buttons on the bed to lock out various bed controls, environmental controls, or other functions. In one embodiment of the present invention, these bed lockouts cannot be changed without an authorized caregiver 110 within the room. In other words, when caregiver 110 enters the room, the receiver 25 receives the caregiver identification signal from the badge 24. After the control unit authenticates the identification signal 24, computer 12 then permits the bed lockout status to be changed.


Certain beds such as the TotalCare® bed available from Hill-Rom, Inc. are capable of moving from a generally flat bed position to a chair position. In one embodiment of the present invention, the bed is unable to move to a chair position unless an authorized caregiver 110 is located within the room. Again, the computer 12 must receive and authenticate the identification signal from badge 24 before the bed is permitted to move to the chair position. Thus, a feature is selectively locked out in the absence of a caregiver 110.



FIG. 15 depicts shows a flow chart 1500 of the illustrative embodiments, and describes a process which lockouts and/or alters selected patient and environmental controls when a caregiver 110 is present in the room. In step 1502, the locating and tracking system 20 monitors the room for a caregiver 110. If a caregiver enters the room, step 1504 exits the monitoring loop and enables step 1506, which locks out and/or alters selected patient and environmental controls. In step 1508, the locating and tracking system 20 monitors the room for the presence of the caregiver 110 and retains the state of 1506 as long as the caregiver 110 is in the room. When the caregiver 110 exits the room, the patient lockouts are removed and the environment is restored, along with the patient 100 controls to alter the environment.



FIG. 16 depicts shows a flow chart 1600 of another one of the illustrative embodiments, and describes a process which enables and/or alters selected patient and environmental controls when a caregiver 110 enters the room. In step 1602, the locating and tracking system 20 monitors the room for a caregiver 110. If a caregiver enters the room, step 1604 exits the monitoring loop and enables step 1606, which enables and/or alters selected patient and environmental controls. In step 1608, the locating and tracking system 20 monitors the room for the presence of the caregiver 110 and retains the state of 1606 as long as the caregiver 110 is in the room. When the caregiver 110 exits the room, the patient and environmental lockouts are restored.



FIG. 3 depicts a database structure used to associate patients with hospital personnel, and associate hospital personnel with alarms. Patient information is stored in patient database 200. As depicted in FIG. 3, there are numerous patients in the database, ranging from record number 1 to k.


Hospital personnel information is stored in hospital personnel database 300. There are numerous hospital personnel in the hospital personnel database 300, ranging from record number 1 to m. Furthermore, hospital personnel information stored in hospital personnel database 300 is categorized by personnel position. Illustratively, the hospital personnel database contains a “doctor” class, a “nurse” class, and “orderly” class, and a “non-caregiver” class. Non-caregiver class illustratively includes security staff, administrative staff, or janitorial staff.


Alarm database 400 stores alarm information for alarm records 1 to n, each record associated with a different alarm. Furthermore, alarm information stored in alarm database 300 includes alarm type and alarm priority. Thus, alarm record 1, for example, may be associated with a cardiac arrest and allocated priority 1, the highest priority and thus requiring immediate attention, and alarm record n may be associated with an incontinence event, and be allocated a lower priority.



FIG. 4 depicts the database association for a specific patient record, the patient associated with hospital personnel, and the hospital personnel associated with alarms. Illustratively, patient record 221 is associated with hospital personnel records 11, 131, and 211. In the present example, the patient represented by patient record 221 has been admitted for a heart procedure requiring surgery. Hospital personnel records 11, 131, and 211 correspond to a surgeon, a cardiologist and a nurse, respectively. Alarms records 1-11 in alarm database 400 are associated with hospital personnel records 11, 131, and 211. In the illustrative example, alarm records 1-3 are associated with hospital personnel record 11, alarm records 3-7 are associated with hospital personnel record 131, and alarm records 8-11 are associated with hospital personnel record 211. Illustratively, alarm record 1 corresponds to a cardiac arrest, and has the highest priority, which requires the attention of a cardiologist. Alarm record 3 corresponds to a less severe cardiac event, such as an irregular heart rate, and thus has a lesser priority, and requires either the cardiologist or surgeon.


The flow diagram 500 of FIG. 5 depicts one illustrative embodiment of the automatic alarm silencing process that includes association of patients, hospital personnel and alarms. In step 502, the computer 12 receives an alarm from either the location and tracking system 20, the nurse call system 40, a treatment device 72, a therapy device 82, environmental devices 50, or the hospital bed 90. Upon receiving the alarm signal, computer 12 gets the alarm priority from alarm database 400, and may also notify the caregiver at their current location. In step 504, the computer monitors the room 130 from which the alarm was received for a caregiver. In the illustrative embodiment disclosed herein, patient station 22 monitors the room 130 via receiver 25. Upon entering the room 130, a caregiver is identified by badge 24, which emits an infrared pulse and is detected by receiver 25. Computer 12 receives the caregiver identification and thus identifies the associated hospital personnel record in hospital personnel database 300.


In step 506, computer 12 determines whether the caregiver in room 130 is associated with the alarm priority stored in alarm database 400. For example, if the alarm priority is 3, indicating a cardiac event of lower priority than a cardiac arrest, and the person entering the room is identified as a non-caregiver, e.g., a security officer, the alarm will not be silenced. Similarly, if the caregiver is identified as a nurse, the alarm will not be silenced. Conversely, if the caregiver is identified as a cardiologist or surgeon, which in this example is associated with the alarm of priority 3, then step 508 determines if the doctor identified is associated with that patient. If the doctor is associated with the patient, then the alarm is silenced in step 510. If the doctor is not associated with the patient, the alarm is not silenced.


The flow diagram 600 of FIG. 6 depicts another illustrative embodiment of the automatic alarm silencing process that includes associating patients with hospital personnel. In step 602, the computer 12 receives an alarm from either the location and tracking system 20, the nurse call system 40, a treatment device 72, a therapy device 82, environmental devices 50, or the hospital bed 90. Upon receiving the alarm signal, computer 12 monitors the room 130 from which the alarm was received for a caregiver, as shown in step 604. In the illustrative embodiment disclosed herein, patient station 22 monitors the room 130 via receiver 25. Upon entering the room 130, a caregiver is identified by badge 24, which emits an infrared and/or RF pulse and is detected by receiver 25. Computer 12 receives the caregiver identification and thus identifies the associated hospital personnel record in hospital personnel database 300. Step 606 determines if the caregiver is associated with the patient. If the caregiver is associated with the patient, then the alarm is silenced in step 608. If the caregiver is not associated with the patient, the alarm is not silenced.


The flow diagram 700 of FIG. 7 depicts another illustrative embodiment of the automatic alarm silencing process that includes a lockout of patient activated controls. In step 702, the computer 12 receives an alarm from either the location and tracking system 20, the nurse call system 40, a treatment device 72, a therapy device 82, environmental devices 50, or the hospital bed 90. Upon receiving the alarm signal, computer 12 monitors the room 130 from which the alarm was received for a caregiver, as shown in step 704. In the illustrative embodiment disclosed herein, patient station 22 monitors the room 130 via receiver 25. Upon entering the room 130, a caregiver is identified by badge 24, which emits an infrared pulse and is detected by receiver 25. Once the caregiver enters the room, step 706 silences the alarm and locks out any patient activated controls, such as bed 90 controls or television/radio 120 controls, thus decreasing the likelihood that the patient 100 may inadvertently interfere with caregiver 110 while the caregiver 110 administers the required therapy in response to the alarm.


The flow diagram 800 of FIG. 8 depicts another illustrative embodiment of the automatic alarm silencing process in conjunction with a patient control lockout that includes a lockout of patient activated controls immediately upon the occurrence of an alarm. Locking out patient and environmental controls as soon as an alarm is received is desirable should the patient 100 be suffering from severe condition, such as a cardiac arrest or seizure, so as to prevent a patient s involuntary movement from accidentally activating a bed 90 or environmental devices 50.


In step 802, the computer 12 receives an alarm from either the location and tracking system 20, the nurse call system 40, a treatment device 72, a therapy device 82, environmental devices 50, or the hospital bed 90. Upon receiving the alarm signal, computer 12 immediately locks out all patient and environmental controls as shown in step 804. Controller 12 then monitors the room 130 from which the alarm was received for a caregiver, as shown in step 806. Once the caregiver enters the room, step 808 silences the alarm.


Often an alarm may sound when a caregiver 110 in present in the hospital room 130. In such a situation, it is not desirable to automatically cancel the alarm, as the caregiver 110 may not immediately notice the alarm, or the alarm may be suppressed before it emits an audible signal. Accordingly, alternative embodiments to FIGS. 5-8 include a step that determines whether a caregiver 110 is present in the room 130 when the alarm sounds; if a caregiver 110 is present, the alarm is not automatically suppressed by the presence of the caregiver 110. Computer 12 is configured to allow the alarm to sound for a predetermined amount of time so that the caregiver 110 can assess which alarm is sounding. Alternatively, computer 12 is configured to require the caregiver 110 to manually shut off the alarm. Conversely, if a caregiver 110 is not in the room 130, then the processes are the same as depicted in FIGS. 5-8.


Depending on the alarm priority, locking out patient controls may not be desirable. For example, if patient 100 experiences an incontinence event, the patient may desire to exit the bed to personally tend to his hygiene needs. However, locking out the bed controls can impede patient 100 from exiting the bed. Conversely, if the patient is experiencing a seizure, locking out the bed 90 controls and environmental devices 50 is desirable so to prevent a patient's involuntary movement from accidentally activating a bed 90 or environmental devices 50.



FIG. 9 shows a flow chart 900 of another illustrative embodiment describing a process that locks out patient bed controls and environmental controls based on the alarm priority. In step 902, computer 12 receives an alarm. In step 904, the alarm priority is assessed. Step 906 determines whether a patient lock out is required. A higher priority alarm, such as a code blue or cardiac arrest alarm, will warrant locking out most, if not all, controls accessible by patient 90. Conversely, a lower priority alarm, such as an incontinence event, will warrant few, if any, control lock outs. Thus, step 908 determines whether a full lockout or a partial lockout is required. If a full lockout is required, step 910 selects all patient controls for lockout. Conversely, if only a partial lockout is required, step 912 selects which patient controls are to be locked out. The lockouts can either be preset in the system or manually set by hospital personnel. All selected controls are then locked out in step 914.


Similarly, depending on the priority of the alarm, the patient 100 environment may be prepared for the arrival of the caregiver 110. For example, if patient 100 experiences a cardiac arrest while watching television/radio 120, television/radio 120 will be immediately shut off. As a cardiac arrest usually warrants a response team, shutting off the television/radio 120 will ensure that this device will not distract any member of the response team. Conversely, if a patient 100 experiences only a slight incontinence event while watching television, which may not even be noticeable to the patient 100, the better therapy may be to let the patient 100 rest and tend to the patient 100 at a later time. As such, the television/radio 120 will not be shut off automatically. Thus, the environmental devices 50 may not be altered, based on the event magnitude of an associated alarm.



FIG. 10 shows a flow chart 1000 of another illustrative embodiment describing that process that prepares the patient environment for the caregiver based on the alarm priority. In step 1002, computer 12 receives an alarm. In step 1004, the alarm priority is assessed. Step 1006 determines whether environmental preparation is required. A higher priority alarm, such as a code blue or cardiac arrest alarm, will warrant environmental preparation. Conversely, a lower priority alarm, such as a slight incontinence event, will not require an environmental preparation. If an environmental preparation is required, the environment is prepared in step 1008.



FIG. 11 shows a flow chart 1100 of another illustrative embodiment describing a process that prepares the patient environment for the caregiver based on the alarm priority, with each environmental preparation subject to an override condition. Illustratively, an environmental preparation can be subject to an override condition depending on the time of day. For example, if patient 100 experiences a cardiac arrest in the evening while sleeping, it is likely that room 130 lighting is low or off. Given the seventy of a cardiac arrest, which warrants a response team, an environmental preparation includes turning on the room 130 lighting. As such, overhead light 122 will immediately illuminate the room, as a response team will most likely arrive soon after the alarm is generated. Conversely, if a patient 100 experiences only a slight incontinence event during the evening while sleeping, the better therapy may be to let the patient 100 rest and tend to the patient 100 in the morning. As such, no environmental preparations is required and overhead light 122 remains off.


Once the environmental preparations are determined, step 1102 selects the next environmental preparation from the list, beginning with the first. In step 1104, the environmental preparation is checked for an override condition. Illustratively, overhead light 122, which normally would illuminate once an incontinence event is detected, will not illuminate if the time is outside visiting hours, e.g., from 8:00 PM-8:00 AM. If no override condition exists, the environment is prepared accordingly in step 1106; if an override condition for that particular environmental preparation exists, then the environment is not prepared with respect to that particular environmental preparation. If any environmental preparations remain, step 1108 repeats the process for the next environmental preparation. If no environmental preparations remain, then the process is complete.


The lockouts and overrides corresponding to an alarm can be configured through a common database structure. FIG. 12 depicts the database association of the alarm database 400, the database containing type 410, priority 420, lockout 430 and override 440 fields. The type 410 field stores the alarm type. Type 410 field contains records 1 . . . k, priority 420 field contains records 1 . . . 1, lockout 430 field contains records 1 . . . m, and override 440 field contains record 1 . . . n.


Illustratively, alarm types correspond to the equipment and/or patient 100 condition. Thus, type 410 values include “Incontinence Event”, “Cardiac Arrest”, “Low Blood Pressure”, “Smoke Alarm”, etc.


The priority 420 fields stores the alarm priority and corresponds the alarm priority to the alarm type. Illustratively, a higher alarm priority corresponds to more immediate needs of the patient 100 or possibly a life threatening condition the patient 100 is experiencing. As shown in FIG. 12, two records from the type 410 field have been assigned a priority 2. Thus, if an alarm corresponding to either of those two records is received, it is assigned priority 2.


The lockouts 430 field stores the patient lockouts, the environmental lockouts, and environmental preparations. Illustratively, the lockouts correspond to the alarm priority. As shown in FIG. 12, a priority 2 alarm has been assigned three lockouts. Illustratively, the lockouts correspond to bed 90 siderails, overhead light 122, and television/radio 120. Thus, if a priority 2 alarm is received, the patient will not be able to operate the bed 90 siderails, overhead light 122, and television/radio 120.


The override 440 field stores overrides corresponding to the lockouts 430. As shown in FIG. 12, one lockout has two potential overrides. Illustratively, the lockout corresponds to the bed 90 siderail, and the override conditions are “Visiting Hours” or “Minor Incontinence Event.” Thus, if a patient 90 experiences an incontinence event that is only a minor event, the bed 90 siderails will not be locked out. Additionally, if the incontinence event occurs during visiting hours, the bed 90 siderails will not be locked out.


One of ordinary skill in the art will readily appreciate that the database configuration of FIGS. 3, 4 and 12 are illustrative only, and that other configurations or structures are readily apparent. For example, overrides can be correlated to priority, or priority and lockouts, etc. Furthermore, the illustrative fields are not exhaustive and other categorization schemes exist known to those of ordinary skill in the art.


Although the invention has been described in detail with reference to certain illustrated embodiments, variations exist within the scope and spirit of the invention as described and as defined in the following claims.

Claims
  • 1. A method of monitoring a patient room, comprising monitoring a patient room for a signal indicating presence of a caregiver in the patient room,detecting a signal indicating presence of the caregiver in the patient room,determining the identity of the caregiver associated with the signal, andaltering the state of at least one device associated with the patient room in response to detecting the presence of the caregiver in the patient room and determining the identity of the caregiver associated with the signal.
  • 2. The method of claim 1, wherein the at least one device associated with the patient room is located in the patient room.
  • 3. The method of claim 1, wherein the at least one device associated with the patient room is located adjacent the patient room.
  • 4. The method of claim 1, wherein the at least one device associated with the patient room comprises an environment device.
  • 5. The method of claim 1, wherein the at least one device associated with the patient room comprises an entertainment device.
  • 6. The method of claim 1, wherein the at least one device associated with the patient room comprises a radio, a television, or a light located in the patient room.
  • 7. The method of claim 1, wherein the at least one device associated with the patient room comprises a control of a patient bed in the patient room.
  • 8. The method of claim 1, further comprising continuing to monitor the patient room to determine whether the caregiver is present in the patient room after the presence of the caregiver in the patient room has first been detected.
  • 9. The method of claim 8, further comprising retaining the altered state of the at least one device as long as the caregiver is present in the patient room.
  • 10. The method of claim 9, further comprising restoring the previous state of the at least one device if the caregiver's presence is no longer detected in the room.
  • 11. The method of claim 1, further comprising detecting an alarm signal associated with the patient room and responding to the alarm signal by initiating the monitoring of the patient room for presence of a caregiver in the patient room.
  • 12. The method of claim 1, further comprising identifying the caregiver as being a certain type of caregiver, and altering the state of at least one device associated with the patient room if the caregiver is of the certain type.
  • 13. The method of claim 1, further comprising determining the identity of a patient assigned to the patient room, determining whether the caregiver is assigned to the patient, and altering the state of at least one device associated with the patient room in response to determining that the caregiver is assigned to the patient.
  • 14. The method of claim 1, further comprising identifying the caregiver as being a certain type of caregiver, determining the identity of a patient assigned to the patient room, determining whether the caregiver is assigned to the patient, and altering the state of at least one device associated with the patient room in response to determining that the caregiver is assigned to the patient and in response to determining that the caregiver is of the certain type.
  • 15. The method of claim 1, further comprising detecting an alarm signal associated with the patient room and altering the state of at least one device associated with the patient room prior to detecting the presence of the caregiver in the patient room.
  • 16. The method of claim 1, further comprising detecting an alarm signal associated with the patient room, determining a priority of the alarm signal, and altering the state of at least one device associated with the patient room according to the alarm priority.
  • 17. The method of claim 1, further comprising detecting an alarm signal associated with the patient room, determining a type of the alarm signal, and altering the state of at least one device associated with the patient room according to the alarm type.
  • 18. At least one computer accessible storage medium comprising instructions for executing the method of claim 1.
  • 19. A computer configured to execute the method of claim 1.
  • 20. A system comprising a transmitter, a receiver, and a computer arranged to execute the method of claim 1.
REFERENCE TO PRIORITY APPLICATIONS

This application is a continuation of U.S. application Ser. No. 13/939,329, filed Jul. 11, 2013, now U.S. Pat. No. 8,766,804, which is a continuation of U.S. application Ser. No. 13/599,110, filed Aug. 30, 2012, now U.S. Pat. No. 8,487,774, which is a continuation of U.S. application Ser. No. 13/238,899, filed Sep. 21, 2011, now U.S. Pat. No. 8,258,965, which is a continuation of U.S. application Ser. No. 12/258,058, filed Oct. 24, 2008, now U.S. Pat. No. 8,026,821, which is a continuation of U.S. application Ser. No. 11/075,979, filed Mar. 9, 2005, now U.S. Pat. No. 7,443,302, which is a continuation of U.S. application Ser. No. 09/849,688, filed May 4, 2001, now U.S. Pat. No. 6,876,303, which claims the benefit of U.S. Provisional Application No. 60/202,283, entitled “Patient Point of Care Computer System,” filed May 5, 2000, and U.S. Provisional Application No. 60/202,284, entitled “Remote Control for a Hospital Bed,” filed May 5, 2000, and U.S. Provisional Application No. 60/229,136, entitled “Patient Point of Care Computer System,” filed Aug. 30, 2000, all of which are hereby incorporated herein by reference. The disclosures of related U.S. Nonprovisional application Ser. No. 09/849,580, entitled “Patient Point of Care Computer System”, filed May 4, 2001, and U.S. Nonprovisional application Ser. No. 09/848,941, entitled “Remote Control for a Hospital Bed” filed May 4, 2001 are incorporated herein by reference.

US Referenced Citations (272)
Number Name Date Kind
4850040 Teich et al. Jul 1989 A
5003984 Muraki et al. Apr 1991 A
5036852 Leishman Aug 1991 A
5228449 Christ et al. Jul 1993 A
5291399 Chaco et al. Mar 1994 A
5319363 Welch et al. Jun 1994 A
5394882 Mawhinney et al. Mar 1995 A
5415167 Wilk et al. May 1995 A
5417222 Dempsey et al. May 1995 A
5511553 Segalowitz et al. Apr 1996 A
5515426 Yacenda et al. May 1996 A
5534851 Russek Jul 1996 A
5537095 Dick et al. Jul 1996 A
5544661 Davis et al. Aug 1996 A
5561412 Novak et al. Oct 1996 A
5579775 Dempsey et al. Dec 1996 A
5594786 Chaco et al. Jan 1997 A
5628324 Sarbach May 1997 A
5664270 Bell et al. Sep 1997 A
5678562 Sellers et al. Oct 1997 A
5687771 Clough et al. Nov 1997 A
5689229 Chaco et al. Nov 1997 A
5699038 Ulrich et al. Dec 1997 A
5712795 Layman et al. Jan 1998 A
5713856 Eggers et al. Feb 1998 A
5719761 Gatti et al. Feb 1998 A
5724025 Tavori Mar 1998 A
5738102 Lemelson Apr 1998 A
5772599 Nevo et al. Jun 1998 A
5781442 Engleson et al. Jul 1998 A
5800387 Duffy et al. Sep 1998 A
5808552 Wiley et al. Sep 1998 A
5822418 Yacenda et al. Oct 1998 A
5822544 Chaco et al. Oct 1998 A
5825283 Camhi et al. Oct 1998 A
5836910 Duffy et al. Nov 1998 A
5838223 Gallant et al. Nov 1998 A
5862803 Besson et al. Jan 1999 A
5867821 Ballantyne et al. Feb 1999 A
5873369 Laniado et al. Feb 1999 A
5919141 Money et al. Jul 1999 A
5941846 Duffy et al. Aug 1999 A
5944659 Flach et al. Aug 1999 A
5957854 Besson et al. Sep 1999 A
5990866 Yollin et al. Nov 1999 A
6009333 Chaco et al. Dec 1999 A
6014346 Malone et al. Jan 2000 A
6028519 Dessureau et al. Feb 2000 A
6038469 Karlsson et al. Mar 2000 A
6044283 Fein et al. Mar 2000 A
6044382 Martino et al. Mar 2000 A
6047203 Sackner et al. Apr 2000 A
6057758 Dempsey et al. May 2000 A
6067019 Scott et al. May 2000 A
6074345 Van Oostrom et al. Jun 2000 A
6078261 Davsko et al. Jun 2000 A
6080106 Lloyd et al. Jun 2000 A
6093146 Filangeri et al. Jul 2000 A
6125350 Dirbas et al. Sep 2000 A
6132371 Dempsey et al. Oct 2000 A
6135949 Russo et al. Oct 2000 A
6147592 Ulrich et al. Nov 2000 A
6147618 Halleck et al. Nov 2000 A
6150951 Olejniczak Nov 2000 A
6159147 Lichter et al. Dec 2000 A
6160478 Jacobsen et al. Dec 2000 A
6167258 Schmidt et al. Dec 2000 A
6171264 Bader Jan 2001 B1
6186962 Lloyd et al. Feb 2001 B1
6198394 Jacobsen et al. Mar 2001 B1
6213942 Flach et al. Apr 2001 B1
6259355 Chaco et al. Jul 2001 B1
6270457 Bardy Aug 2001 B1
6277080 Nissilä et al. Aug 2001 B1
6289238 Besson et al. Sep 2001 B1
6304774 Gorman Oct 2001 B1
6336900 Alleckson et al. Jan 2002 B1
6336903 Bardy Jan 2002 B1
6368284 Bardy Apr 2002 B1
6398727 Bui et al. Jun 2002 B1
6398728 Bardy Jun 2002 B1
6402691 Peddicord et al. Jun 2002 B1
6406426 Reuss et al. Jun 2002 B1
6407335 Franklin-Lees et al. Jun 2002 B1
6411840 Bardy Jun 2002 B1
6416471 Kumar et al. Jul 2002 B1
6441747 Khair et al. Aug 2002 B1
6443890 Schulze et al. Sep 2002 B1
6450953 Place et al. Sep 2002 B1
6475153 Khair et al. Nov 2002 B1
6493747 Simmon et al. Dec 2002 B2
6494829 New, Jr. et al. Dec 2002 B1
6496705 Ng et al. Dec 2002 B1
6497656 Evans et al. Dec 2002 B1
6517497 Rymut et al. Feb 2003 B2
6533729 Khair et al. Mar 2003 B1
6540686 Heikkilä et al. Apr 2003 B2
6544173 West et al. Apr 2003 B2
6544174 West et al. Apr 2003 B2
6551252 Sackner et al. Apr 2003 B2
6559620 Zhou et al. May 2003 B2
6569094 Suzuki et al. May 2003 B2
6575902 Burton Jun 2003 B1
6577893 Besson et al. Jun 2003 B1
6579231 Phipps Jun 2003 B1
6589170 Flach et al. Jul 2003 B1
6593528 Franklin-Lees et al. Jul 2003 B2
6594511 Stone et al. Jul 2003 B2
6595929 Stivoric et al. Jul 2003 B2
6600421 Freeman Jul 2003 B2
6602191 Quy Aug 2003 B2
6603401 Ueyama Aug 2003 B1
6605038 Teller et al. Aug 2003 B1
6611705 Hopman et al. Aug 2003 B2
6612984 Kerr, II Sep 2003 B1
6616606 Petersen et al. Sep 2003 B1
6640246 Gary, Jr. et al. Oct 2003 B1
6659947 Carter et al. Dec 2003 B1
6669630 Joliat et al. Dec 2003 B1
6671563 Engelson et al. Dec 2003 B1
6694180 Boesen Feb 2004 B1
6723046 Lichtenstein et al. Apr 2004 B2
6731989 Engleson et al. May 2004 B2
6736759 Stubbs et al. May 2004 B1
6740033 Olejniczak et al. May 2004 B1
6748250 Berman et al. Jun 2004 B1
6749566 Russ Jun 2004 B2
6758812 Lang Jul 2004 B2
6773396 Flach et al. Aug 2004 B2
6817979 Nihtilä et al. Nov 2004 B2
6819247 Bimbach et al. Nov 2004 B2
6823036 Chen Nov 2004 B1
6840904 Goldberg Jan 2005 B2
6870466 Rust Mar 2005 B2
6871211 Labounty et al. Mar 2005 B2
6875174 Braun et al. Apr 2005 B2
6876303 Reeder et al. Apr 2005 B2
6893396 Schulze et al. May 2005 B2
6897788 Khair et al. May 2005 B2
6915170 Engleson et al. Jul 2005 B2
6937150 Medema et al. Aug 2005 B2
6942616 Kerr, II Sep 2005 B2
6984297 Nisch et al. Jan 2006 B2
6987965 Ng et al. Jan 2006 B2
6988989 Weiner et al. Jan 2006 B2
7002468 Eveland et al. Feb 2006 B2
7004907 Banet et al. Feb 2006 B2
7010337 Furnary et al. Mar 2006 B2
7020508 Stivoric et al. Mar 2006 B2
7029455 Flaherty Apr 2006 B2
7053767 Petite et al. May 2006 B2
7053831 Dempsey et al. May 2006 B2
7088233 Menard Aug 2006 B2
7099895 Dempsey Aug 2006 B2
7103407 Hjelt et al. Sep 2006 B2
7104955 Bardy Sep 2006 B2
7107106 Engleson et al. Sep 2006 B2
7117041 Engleson et al. Oct 2006 B2
7123149 Nowak et al. Oct 2006 B2
7127261 Van Erlach Oct 2006 B2
7129836 Lawson et al. Oct 2006 B2
7130396 Rogers et al. Oct 2006 B2
7138902 Menard Nov 2006 B2
7153262 Stivoric et al. Dec 2006 B2
7153263 Carter et al. Dec 2006 B2
7154398 Chen et al. Dec 2006 B2
7156807 Carter et al. Jan 2007 B2
7171166 Ng et al. Jan 2007 B2
7197357 Istvan et al. Mar 2007 B2
7197492 Sullivan Mar 2007 B2
7215991 Besson et al. May 2007 B2
7222054 Geva May 2007 B2
7231258 Moore et al. Jun 2007 B2
7242308 Ulrich et al. Jul 2007 B2
7256708 Rosenfeld et al. Aug 2007 B2
7272428 Hopman et al. Sep 2007 B2
7277758 DiLorenzo Oct 2007 B2
7283423 Holm et al. Oct 2007 B2
7292135 Bixler et al. Nov 2007 B2
7292139 Mazar et al. Nov 2007 B2
7294105 Islam Nov 2007 B1
7301451 Hastings Nov 2007 B2
7304580 Sullivan et al. Dec 2007 B2
7319386 Collins, Jr. et al. Jan 2008 B2
7324824 Smith et al. Jan 2008 B2
7336563 Holm Feb 2008 B2
7352652 Holm et al. Apr 2008 B2
7362656 Holm Apr 2008 B2
7384110 Hoshiyama et al. Jun 2008 B2
7443302 Reeder et al. Oct 2008 B2
7454885 Lin et al. Nov 2008 B2
7480951 Weismiller et al. Jan 2009 B2
7920061 Klein et al. Apr 2011 B2
8026821 Reeder et al. Sep 2011 B2
8258965 Reeder et al. Sep 2012 B2
8487774 Reeder et al. Jul 2013 B2
8766804 Reeder et al. Jul 2014 B2
20010034475 Flach et al. Oct 2001 A1
20020103674 Reeder et al. Aug 2002 A1
20020165731 Dempsey Nov 2002 A1
20020198986 Dempsey Dec 2002 A1
20030025604 Freeman Feb 2003 A1
20030141981 Bui et al. Jul 2003 A1
20040072475 Istvan Apr 2004 A1
20040073127 Istvan et al. Apr 2004 A1
20040121767 Simpson et al. Jun 2004 A1
20040127802 Istvan et al. Jul 2004 A1
20040147818 Levy et al. Jul 2004 A1
20040167465 Mihai et al. Aug 2004 A1
20040176667 Mihai et al. Sep 2004 A1
20050140508 Tessier et al. Jun 2005 A1
20050148303 Dempsey Jul 2005 A1
20050168341 Reeder et al. Aug 2005 A1
20050177052 Istvan et al. Aug 2005 A1
20050197545 Hoggle Sep 2005 A1
20050206518 Welch et al. Sep 2005 A1
20050251002 Istvan et al. Nov 2005 A1
20050251003 Istvan et al. Nov 2005 A1
20050251004 Istvan et al. Nov 2005 A1
20060030759 Weiner et al. Feb 2006 A1
20060077759 Holm Apr 2006 A1
20060089539 Miodownik et al. Apr 2006 A1
20060106649 Eggers et al. May 2006 A1
20060122867 Eggers et al. Jun 2006 A1
20060136271 Eggers et al. Jun 2006 A1
20060143051 Eggers et al. Jun 2006 A1
20060190302 Eggers et al. Aug 2006 A1
20060214786 Bixler et al. Sep 2006 A1
20060220839 Fifoit et al. Oct 2006 A1
20060238350 Tessier Oct 2006 A1
20060239195 Camins et al. Oct 2006 A1
20060242293 Russ Oct 2006 A1
20060248221 Hottel et al. Nov 2006 A1
20060253281 Letzt et al. Nov 2006 A1
20060258926 Ali et al. Nov 2006 A1
20060267740 Bixler et al. Nov 2006 A1
20060277202 Dempsey Dec 2006 A1
20060279427 Becker et al. Dec 2006 A1
20060288095 Torok et al. Dec 2006 A1
20070013511 Weiner et al. Jan 2007 A1
20070040692 Smith et al. Feb 2007 A1
20070060976 Denzene et al. Mar 2007 A1
20070069887 Welch et al. Mar 2007 A1
20070080801 Weismiller et al. Apr 2007 A1
20070112602 Bellon et al. May 2007 A1
20070123955 Verhoef et al. May 2007 A1
20070135866 Baker et al. Jun 2007 A1
20070142716 Biondi Jun 2007 A1
20070156456 McGillin et al. Jul 2007 A1
20070156707 Fuchs et al. Jul 2007 A1
20070180140 Welch et al. Aug 2007 A1
20070208235 Besson et al. Sep 2007 A1
20070229249 McNeal et al. Oct 2007 A1
20070233199 Moore et al. Oct 2007 A1
20070251835 Mehta et al. Nov 2007 A1
20070255111 Baldus et al. Nov 2007 A1
20070255250 Moberg et al. Nov 2007 A1
20070255348 Holzclaw Nov 2007 A1
20070258395 Jollota et al. Nov 2007 A1
20070279211 Fenske et al. Dec 2007 A1
20080009694 Hopman et al. Jan 2008 A1
20080018435 Brown Jan 2008 A1
20080049555 Holm et al. Feb 2008 A1
20080114689 Psynik et al. May 2008 A1
20080120784 Warner et al. May 2008 A1
20080122616 Warner et al. May 2008 A1
20080126122 Warner et al. May 2008 A1
20080126132 Warner et al. May 2008 A1
20080147442 Warner et al. Jun 2008 A1
20090096615 Reeder et al. Apr 2009 A1
20120075464 Derenne et al. Mar 2012 A1
20130300558 Reeder et al. Nov 2013 A1
Non-Patent Literature Citations (8)
Entry
Composer SW Cofig Guide Rev B 1995, 154 pages.
“Cricket v2 User Manual,” MIT Computer Science and Artifical Intelligence Lab, Jan. 2005.
Priyantha, et al., “The Cricket Location-Support System,” ACM MOBICOM, Aug. 2000.
Chakraborty, Anit, “A Distributed Architecture for Mobile, Location-Dependent Applications,” Massachusetts Institute of Technology (1999).
Hill-Rom NetLinx, “The COMposer® Communication System,” www.hill-rom.com, 1999, 4 pages.
COMposer Communication System Service Manual, Nov. 1995, 426 pages.
The COMposer System Installation Manual, 2003, 225 pages.
Composer Communication System In-Service Getting Started, 1997, 32 pages.
Related Publications (1)
Number Date Country
20140320290 A1 Oct 2014 US
Provisional Applications (2)
Number Date Country
60202283 May 2000 US
60229136 Aug 2000 US
Continuations (6)
Number Date Country
Parent 13939329 Jul 2013 US
Child 14318803 US
Parent 13599110 Aug 2012 US
Child 13939329 US
Parent 13238899 Sep 2011 US
Child 13599110 US
Parent 12258058 Oct 2008 US
Child 13238899 US
Parent 11075979 Mar 2005 US
Child 12258058 US
Parent 09849688 May 2001 US
Child 11075979 US