The disclosure generally relates to sanitization.
Approximately 10% of patients who are admitted to hospitals acquire an infection while in the hospital. These infections are typically more serious due to problems with antibiotic resistant strains. These infections not only dramatically increase the cost of care, but more importantly are a cause of substantial morbidity and mortality. The most common method for the spread of nosocomial infections is from direct contact with health care providers' hands. As a result, the CDC has issued recommendations that healthcare providers wash their hands or use an instant hand sanitizer before and after all patient's contacts.
At the present time nearly all hospitals have installed instant hand sanitizer dispensers in all patient rooms and strategically placed signs reminding health care workers to use the dispensers. Despite this improvement, there is at best 50% compliance among health care workers. In most cases the providers are distracted with other responsibilities and simply forget.
Although there are devices designed to monitor sanitization compliance, these devices tend to be impractical in hospital settings, are prohibitively expensive to use on a large scale, and/or would require substantial renovation to implement.
A hand sanitization system is provided that provides notice to a person of proximity to the system and non-compliance with sanitization protocols. In certain embodiments, the system also provides automated monitoring of compliance with sanitation protocols.
Generally, a hand sanitization system is provided that includes a unit housing, a proximity detector mounted to the housing operative to determine proximity of a person with respect to the detector; a dispenser mounted to the housing and being operative to dispense antiseptic solution; and an alarm mounted to the housing and being operative to provide an indication to the person, the indication corresponding to the person failing to dispense antiseptic solution from the dispenser within a predetermined period of time after moving within a predetermined range of the detector.
Many aspects of the disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
Systems for monitoring hand sanitization are provided, several exemplary embodiments of which will be described in detail. In this regard, such a system is designed to improve hand sanitization practices in locations such as hospitals rooms. Notably, the CDC recommends that healthcare providers wash their hands or use an antiseptic hand sanitizer before and after each patient contact. The system is configured to serve as a reminder to providers who enter a patient's room, for example, and forget to use a hand sanitizer. If a provider walks by a system sensor and does not use the sanitizer during a potentially variable time period, an alarm may sound until the provider uses the sanitizer.
An exemplary embodiment of a system for monitoring hand sanitization is depicted schematically in
Another exemplary embodiment of a system for monitoring hand sanitization is depicted schematically in
In the embodiment of
The output is then converted to a digital signal with the Schmitt trigger. Notably, a Schmitt trigger is a bistable multivibrator that either produces a high or low signal depending on the input signal. The Schmitt trigger use two PNP transistors and a series of five resistors that when combined produce either a high or low voltage. If the input exceeds the Von value, the output from the trigger is high or Vcc. The value for Von is:
If the input drops below Voff, the output from the trigger is low or ground. The value for Voff is:
A variable potentiometer 38 is used in some embodiments to adjust an effective range of the detector. In the representative circuit of
A representative microprocessor is a Microchip 12F508 microcontroller. The microcontroller takes inputs from both the Schmitt trigger and dispenser switch 40. The dispenser switch is connected to the hand sanitizer dispenser and closing this switch represents using the sanitizer. Based on the two inputs, the microcontroller can in turn activate the alarm. The microcontroller in this embodiment is programmed (such as shown in the attached
In this embodiment, there is a delay built into the program so that there is a three second delay between the time the Schmitt trigger is activated and the sounding of the alarm. This delay is incorporated so that the health care provider has adequate time to use the sanitizer before the alarm sounds. Once the dispenser switch is closed, there is a ten second period in which the alarm is silenced. This delay ensures that the alarm will not sound if the external switch is closed before or while the individual crosses in front of the sensor. Clearly, various delays can be implemented in other embodiments.
Additional features to the circuitry that could be easily added are a photo resistor and a low battery indicator. The low battery indicator could be made with a second Schmitt trigger that could be incorporated or provide input to the microcontroller so that if the battery dropped below a certain voltage (i.e. a low battery) a visual and/or audible alarm could be triggered.
The photo-resistor is a variable resistor that changes voltage based on the light that strikes the surface. This could be incorporated to detect the background light in the patient's room. This would enable the detection of whether the lights are off (i.e. a sleeping patient), and result in either a silenced or reduced volume of the audible alarm, so as not to disturb the patient.
The audible alarm that is incorporated into the device as its stands is a customizable audio recording. The recording is a voice message reminding the healthcare provider to use the hand sanitizer in the event that the user fails to do so while entering or exiting the room. The combination audio recording chip and microcontroller has the ability to play multiple recordings at varying volumes. The multiple recordings can be used to play randomly selected messages to reduce the potential of conditioning of the providers. Additionally, multiple recording could be played sequentially in the event that a provider fails to respond to the first message. The volume of the device could be adjusted based on the ambient light in the room (day/night) or could be varied based on the provider's response.
A representative audible alarm is a piezo-electric buzzer. In other embodiments, a speaker and driver can be used, among others. The microcontroller could be programmed to emit a variety of tones/buzzers or could be programmed to play a recorded message asking the healthcare provider to use the antiseptic solution. The microcontroller could also be programmed with several tones/recording as to vary the message played. This could help reduce conditioning of the health care providers resulting in them ignoring the system message.
Another feature that is included in certain embodiments is a modular antiseptic and battery pack (50 in
Additionally or alternatively, some embodiments can incorporate a solar cell for providing power to one or more of the electronic components of the system. By way of example, a solar cell (or array of cells) can be mounted to the housing and used to recharge the system battery, such as when the lights are turned on in the room in which the housing is located.
The device has the ability to track the compliance of all the devices. An exemplary monitoring scheme is shown in
To better monitor the compliance/usage of the sanitizer, data associated with such use could be stored and/or transmitted to another computer/device for recording (such as in a
This information could also be transmitted to a second device (either through a wired or wireless device) that could be used to analyze the handwashing compliance. At the present time there is no hand sanitizer monitoring device that is widely used in hospitals. The hand sanitizing practices consist of dispensers that are strategically placed and signs reminding health care workers to use them. Even with these improvements the best compliance rates are just approaching 50%. The current compliance tracking requirements are based on tracking aggregate compliance and not individual provider compliance.
An advantage of this device is that it actively reminds the health care provider to use the sanitizer. The system essentially ensures that anyone who walks into or out of a patient room will use the sanitizer. If they do not use the sanitizer, an alarm will activate until the sanitizer or the silence button is pressed. There have been other devices that are designed to monitor compliance, but they tend to be impractical in hospital settings, are prohibitively expensive to use on a large scale, or would require substantial renovation to implement them. This system potentially avoids this issue in that it is stand alone, and very low cost when compared to other devices.
There are certain instances, such as during a code or withdrawal, where it is not appropriate to monitor compliance or play the audio recording. In some embodiments, the device has a switch that can silence the alarm or deactivate the compliance tracking for a predetermined or indefinite period of time.
The most important application for this device is to reduce the incidence and mortality from hospital acquired infections. Roughly 2 million patients per year acquire infections while in the hospital, resulting in approximately 80,000 deaths per year. The most common route of spread is direct contract with health care workers and the commonly accepted solution is to improve hand sanitization practices. In the U.S., there is nearly $6 billion per year spent on treating nosocomial infections, most of which is paid directly by the hospital. According to the American Hospital Association there are roughly 950,000 hospital beds in the U.S., meaning that over $6300 dollars is spent per year just to treat infections acquired while in the hospital. It is estimated that it would cost $250,000 per year (in a 250 bed hospital) for an infection control program that has only achieved a 50% compliance rate in the best of circumstances. This roughly gives a cost of $1000 per bed in each hospital for an infection control program. Multiplying this by the 950,000 beds in the U.S., given an estimate of $950 million dollars per year spent on hospital infection programs.
Various functionality, such as that described above in the flowcharts, can be implemented in hardware and/or software. In the terms of hardware architecture, such a computing device can include a processor, memory, and one or more input and/or output (I/O) device interface(s) that are communicatively coupled via a local interface. The local interface can include, for example but not limited to, one or more buses and/or other wired or wireless connections. The local interface may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers to enable communications. Further, the local interface may include address, control, and/or data connections to enable appropriate communications among the aforementioned components.
The processor may be a hardware device for executing software, particularly software stored in memory. The processor can be a custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the computing device, a semiconductor based microprocessor (in the form of a microchip or chip set) or generally any device for executing software instructions.
The memory can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such a DRAM, SRAM, SDRAM, VRAM, etc.)) and/or nonvolatile memory elements (e.g., ROM, hard drive, tape, CD-ROM, etc.). Moreover, the memory may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory can also have a distributed architecture, where various components are situated remotely from one another, but can be accessed by the processor.
The software in the memory may include one or more separate programs, each of which includes an ordered listing of executable instructions for implementing logical functions. A system component embodied as software may also be construed as a source program, executable program (object code), script, or any other entity comprising a set of instructions to be performed. When constructed as a source program, the program is translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the memory.
The Input/Output devices that may be coupled to system I/O Interface(s) may include input devices, for example but not limited to, a keyboard, mouse, scanner, microphone, camera, proximity device, etc. Further, the Input/Output devices may also include output devices, for example but not limited to, a printer, display, etc. Finally, the Input/Output devices may further include devices that communicate both as inputs and outputs, for instance but not limited to, a modulator/demodulator (modem; for accessing another device, system, or network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, a router, etc.
When the computing device is in operation, the processor can be configured to execute software stored within the memory, to communicate data to and from the memory, and to generally control operations of the computing device pursuant to the software. Software in memory, in whole or in part, is read by the processor, perhaps buffered within the processor, and then executed.
One should note that the flowcharts included herein show the architecture, functionality, and operation of a possible implementation of software. In this regard, each block can be interpreted to represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order and/or not at all. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
One should note that any of the functionality described herein can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “computer-readable medium” contains, stores, communicates, propagates and/or transports the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (a nonexhaustive list) of a computer-readable medium include a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), and a portable compact disc read-only memory (CDROM) (optical).
It should be emphasized that the above-described embodiments are merely possible examples of implementations set forth for a clear understanding of the principles of this disclosure. Many variations and modifications may be made to the above-described embodiments without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the accompanying claims.
This application is a continuation of and claims the benefit under 35 U.S.C. §120 to U.S. patent application Ser. No. 13/639,669, filed Oct. 5, 2012, entitled, “Systems for Monitoring Hand Sanitization”, now U.S. Pat. No. 9,123,233, which is a National Stage entry of and claims benefit of and priority under 35 U.S.C. §371 to International Application No. PCT/US2011/031571, entitled, “Systems for Monitoring Hand Sanitization” filed on Apr. 7, 2011, which claims the benefit of and priority under 35 U.S.C. §§119, 120 to U.S. Provisional Application No. 61/321,595, filed Apr. 7, 2010, entitled, “Systems for Monitoring Hand Sanitization,” all of which are incorporated herein by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
5202666 | Knippscheer | Apr 1993 | A |
5223182 | Steiner | Jun 1993 | A |
5619188 | Ehlers | Apr 1997 | A |
5670945 | Applonie | Sep 1997 | A |
5695091 | Winings et al. | Dec 1997 | A |
5739759 | Nakazawa | Apr 1998 | A |
6166640 | Nishihira | Dec 2000 | A |
6325245 | Matthews | Dec 2001 | B1 |
7375640 | Plost | May 2008 | B1 |
7825812 | Ogrin | Nov 2010 | B2 |
20020135486 | Brohagen | Sep 2002 | A1 |
20020175815 | Baldwin | Nov 2002 | A1 |
20040196612 | Kraz | Oct 2004 | A1 |
20050242942 | Staats | Nov 2005 | A1 |
20070121319 | Wolf | May 2007 | A1 |
20070257803 | Munro | Nov 2007 | A1 |
20070279238 | Smith | Dec 2007 | A1 |
20080103636 | Glenn et al. | May 2008 | A1 |
20080131332 | Nguyen et al. | Jun 2008 | A1 |
20090051545 | Koblasz | Feb 2009 | A1 |
20090219131 | Barnett | Sep 2009 | A1 |
20100117836 | Seyed Momen | May 2010 | A1 |
20110025509 | Brow | Feb 2011 | A1 |
20110112696 | Yodfat | May 2011 | A1 |
20110169646 | Raichman | Jul 2011 | A1 |
20110234407 | Harris | Sep 2011 | A1 |
20110310071 | Segall | Dec 2011 | A1 |
20120218106 | Zaima et al. | Aug 2012 | A1 |
20130113291 | Recker et al. | May 2013 | A1 |
Number | Date | Country |
---|---|---|
2019950009364 | Jun 2006 | EP |
1019940008109 | Sep 1994 | KR |
2019950009364 | Oct 1995 | KR |
Entry |
---|
International Search Report and Written Opinion dated Nov. 6, 2014 mailed in International Application No. PCT/US2014043278. |
International Search Report dated Dec. 23, 2011 mailed in International Application No. PCT/US2011/031571. |
Number | Date | Country | |
---|---|---|---|
20160171874 A1 | Jun 2016 | US |
Number | Date | Country | |
---|---|---|---|
61321595 | Apr 2010 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13639669 | US | |
Child | 14840995 | US |