Hand hygiene compliance monitoring

Information

  • Patent Grant
  • 10529219
  • Patent Number
    10,529,219
  • Date Filed
    Friday, November 9, 2018
    5 years ago
  • Date Issued
    Tuesday, January 7, 2020
    4 years ago
Abstract
A system and associated processes monitor hand hygiene compliance. For example, the hand hygiene compliance system may monitor, analyze and report on hand hygiene compliance after usage of bathroom facilities. Usage of bathroom facilities is determined by sensing activation (e.g., flushing) of a toilet or a urinal. Each activation event gives rise to a hand hygiene opportunity, and should be followed by performance of a corresponding hand hygiene procedure in order for the hand hygiene opportunity to be deemed “compliant”. Performance of a hand hygiene procedure is determined by sensing actuation of a hand hygiene product dispenser. To determine whether a hand hygiene opportunity is compliant, the system may determine whether a dispenser actuation event occurred within a predetermined period of time from the activation event.
Description
TECHNICAL FIELD

The disclosure relates to monitoring of hand hygiene compliance.


BACKGROUND

The practice of proper hand hygiene has been recognized as an effective way to reduce pathogen transmission in settings such as the health care and food service industries. Hands are one of the main pathways for germ transmission during health care food preparation activities. Despite this, compliance with hand hygiene practices remains low, and improvement efforts tend to lack sustainability. Measuring adherence to hand hygiene practices is therefore important, both to identify where hand hygiene compliance is low, and to determine how compliance may be improved.


However, measuring worker adherence to hand hygiene guidelines is not a simple matter. There is no standardized measure for collecting and reporting rates of hand hygiene compliance. Different organizations may require very different hand hygiene practices. For example, both how and when hand hygiene hand should be performed may vary widely depending upon the type of establishment. In addition, even within an organization, hand hygiene requirements may vary depending upon a person's job role and their likelihood of coming into contact with, and/or transmitting, pathogens.


SUMMARY

In general, the disclosure relates to systems and associated processes that monitor hand hygiene compliance. For example, the hand hygiene compliance system may monitor, analyze and report on hand hygiene compliance after activation of a toilet or a urinal.


In one example, the disclosure is directed to a system that monitors hand hygiene compliance at a facility, comprising an activation sensor module that senses activation of a toilet/urinal and transmits corresponding activation event data including an activation sensor identifier and a date and time associated with the sensed activation of the toilet/urinal, the activation event data identifying an associated hand hygiene opportunity; a dispenser actuation sensor module that senses actuation of a hand hygiene product dispenser and transmits corresponding dispense event data including a dispenser actuation sensor identifier and a date and time associated with the sensed actuation of the hand hygiene product dispenser; and a computing device that receives the activation event data and the dispense event data and determines whether the hand hygiene opportunity was compliant with one or more hand hygiene compliance rules, the compliance rules including a predetermined period of time within which actuation of the hand hygiene product dispenser must occur subsequent to the sensed activation of the toilet/urinal in order for the computing device to determine that the hand hygiene opportunity is compliant.


The system may further include a plurality of dispenser actuation sensors, each associated with a different one of a plurality of hand hygiene product dispensers located throughout a facility, the compliance rules further including an association between the activation sensor module and at least one of the plurality of hand hygiene product dispensers, such that actuation of at least one of the associated dispensers must occur within the predetermined period of time subsequent to the sensed activation of the toilet/urinal in order for the computing device to determine that the hand hygiene opportunity is compliant.


The system may further include a plurality of activation sensor modules, each associated with a different one of a plurality of toilet/urinals. The association between the activation sensor module and the at least one of the plurality of hand hygiene product dispensers may be based on their installation in the same restroom.


The remote computing system may further include a reporting application that generates reports concerning hand hygiene compliance at the facility. The remote computing system may further permit users to remotely request and receive the reports. The remote computing system may generate a compliance score according to the equation:







%





Hand





Hygiene





Compliance

=



Hand





Hygiene





Opportunities
×
100


Compliant





Hand





Hygiene





Events


.





The hand hygiene product dispenser may dispense any one of a hand soap, a hand sanitizer, a hand rub, or an aqueous solution. The hand hygiene product dispenser may dispense any one of a liquid, a gel, a lotion, or a foam.


The system may further comprise a compliance badge including a badge module that stores badge identification data uniquely associated with a user, and that communicates the badge identification data to the toilet/urinal activation sensor upon, wherein the toilet/urinal activation sensor stores the badge identification data as part of the activation event data and the dispenser actuation sensor module stores the badge identification data as part of the dispenser data. The compliance rules may include a predetermined period of time within which actuation of the hand hygiene product dispenser associated with the badge identification data must occur subsequent to the sensed activation of the toilet/urinal associated with the badge identification data in order for the computing device to determine that the hand hygiene opportunity is compliant.


In another example, the disclosure is directed to a system that monitors hand hygiene compliance at a facility, comprising an activation sensor module that senses activation of a toilet/urinal and transmits corresponding activation event data including an activation sensor identifier and a date and time associated with the sensed activation of the toilet/urinal, the activation event data identifying an associated hand hygiene opportunity; a dispenser actuation sensor module that senses actuation of a hand hygiene product dispenser and transmits corresponding dispense event data including a dispenser actuation sensor identifier and a date and time associated with the sensed actuation of the hand hygiene product dispenser; and a computing device that receives the activation event data and the dispense event data and determines whether the dispense event occurred within a predetermined period of time of the activation event to determine whether the hand hygiene opportunity was a compliant hand hygiene opportunity.


The computing device may further associate the toilet/urinal with one or more hand hygiene product dispensers based on the toilet/urinal and the one or more hand hygiene product dispensers being located in the same restroom, and may further determine whether the dispense event occurred at one of the one or more associated hand hygiene product dispensers to determine whether the hand hygiene opportunity was a compliant hand hygiene opportunity.


The remote computing system may generate a compliance score based on the activation event data and the dispense event data. The remote computing system may generate the compliance score according to the equation:







%





Hand





Hygiene





Compliance

=



Hand





Hygiene





Opportunities
×
100


Compliant





Hand





Hygiene





Events


.





The system may further include a plurality of toilet/urinal activation modules, each uniquely associated with a different one of a plurality of toilet/urinals; a plurality of dispenser actuation modules, each uniquely associated with a different one of a plurality of hand hygiene product dispensers, and the computing device further determines a compliance score based on a plurality of activation events received from the toilet/urinal activation modules and based on a plurality of dispense events received from the dispenser actuation modules.


The compliance score may be determined on a per toilet/urinal basis, a per hand hygiene product dispenser basis, a per restroom basis, a department basis, a facility-wide basis, or a corporate-wide basis. The compliance score may be determined based on a time period, a workday shift, a day, a week, a month, or a year.


The predetermined period of time may be based at least in part on a distance between the toilet/urinal and the hand hygiene product dispenser. The predetermined period of time may be based at least in part on dimension of a room in which the toilet/urinal and the hand hygiene dispenser are located. The predetermined period of time may be based at least in part on a number of hand hygiene product dispensers. The predetermined period of time may be based at least in part on preferred hand hygiene practices of the facility.


In another example, the disclosure is directed to a method of monitoring hand hygiene compliance at a facility, comprising sensing activation of a toilet/urinal and transmitting corresponding activation event data including an activation sensor identifier and a date and time associated with the sensed activation of the toilet/urinal, the activation event data identifying an associated hand hygiene opportunity; sensing actuation of a hand hygiene product dispenser and transmitting corresponding dispense event data including a dispenser actuation sensor identifier and a date and time associated with the sensed actuation of the hand hygiene product dispenser; associating, by a computing device, the toilet/urinal with one or more hand hygiene product dispensers based on the toilet/urinal and the one or more hand hygiene product dispensers being located in the same restroom; and determining, the computing device, whether the hand hygiene opportunity was a compliant hand hygiene opportunity, including determining, by the computing device, whether the dispense event occurred within a predetermined period of time of the activation event; and determining, by the computing device, whether the dispense event occurred at one of the one or more associated hand hygiene product dispensers.


The method may further comprise generating a report concerning hand hygiene compliance at the facility, wherein the report includes a comparison of hand hygiene opportunities and compliant hand hygiene opportunities at the facility over time to determine whether improvement in hand hygiene practices has occurred. The method may further comprise generating a report including hand hygiene data at multiple facilities.


The method may further comprise receiving, by the computing device, first badge identification data that uniquely identifies a first one of a plurality of users from a first compliance badge associated with the activation event; receiving, by the computing device, second badge identification that uniquely identifies a second one of a plurality of users from a second compliance badge associated with the dispense event; comparing, by the computing device, the first badge identification data with the second badge identification data; and determining, by the computing device, whether the hand hygiene opportunity was a compliant hand hygiene opportunity if the first badge identification data matches the second badge identification data.


The details of one or more examples are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings, and from the claims.





BRIEF DESCRIPTION OF DRAWINGS


FIG. 1 is a diagram of an example restroom including example toilet/urinal activation sensors and example hand hygiene product dispenser actuation sensors.



FIG. 2 is a block diagram illustrating an example hand hygiene compliance system.



FIG. 3 is a block diagram of an example dispenser actuation sensor for a hand hygiene product dispenser.



FIG. 4 is a block diagram of an example toilet/urinal activation sensor.



FIG. 5 is a flow chart illustrating an example process by which a computing device may analyze toilet/urinal activation data and dispenser actuation data to monitor hand hygiene compliance.



FIG. 6 is a chart including example toilet/urinal activation data, example dispenser actuation data, and example results of an analysis to monitor hand hygiene compliance.



FIG. 7 is an example graph illustrating example toilet/urinal activation data and example dispenser actuation data over the course of one workday period.



FIG. 8 is an example graph illustrating example compliance scores generated from the example data shown in the graph of FIG. 7.



FIG. 9 is a block diagram of an example compliance badge.





DETAILED DESCRIPTION

In general, the disclosure relates to a system and associated processes that monitor hand hygiene compliance. For example, the hand hygiene compliance system may monitor, analyze and report on compliance with hand hygiene practices after usage of bathroom facilities. In some examples, the system provides a relatively non-intrusive way to measure and improve employee hand hygiene processes that does not involve identification of individual users, requires no added personal hardware, and fits within normal employee use patterns. In other examples, the system includes compliance badges for identification and monitoring of an individual user's hand hygiene practices.


For purposes of the present disclosure, usage of bathroom facilities is determined by sensing activation (e.g., flushing) of a toilet or a urinal. Each sensed activation defines a corresponding toilet/urinal activation event, or simply, activation event. Sensing flushing of a toilet/urinal helps to ensure that the system accurately captures the high-risk events in a bathroom where potential transmission of pathogens is relatively higher, as compared to relatively lower risk events, such as a user merely entering a bathroom to wash their hands before or after lunch, to brush their teeth, or to comb their hair.


Upon sensing an activation event, the system of the present disclosure determines whether the activation event is followed by performance of a compliant hand hygiene procedure. Performance of a hand hygiene procedure is determined by, for example, sensing actuation of a manual or automatic hand hygiene product dispenser. Each sensed dispenser actuation defines a corresponding dispenser actuation event, or simply, dispense event.


Activation of a toilet or a urinal may be automatic or manual. In one example, to detect automatic activation of a toilet/urinal, the system may receive a signal associated with activation of the toilet/urinal from an automatic or touchless toilet/urinal flushing device. In another example, to sense manual activation of a toilet/urinal, the system may receive a sensed signal associated with flushing of a toilet/urinal from a sensor that senses mechanical movement of the toilet flush lever/handle, a water level sensor in the toilet tank, a sensor on the fill or flush valve, a sensor associated with the toilet tank float or float arm, or other mechanism for sensing flushing of a toilet/urinal, such as a tilt sensor, vibration sensor, acoustic sensor, or other type of sensor.


In either case, each toilet/urinal activation event further gives rise to a hand hygiene opportunity. Each hand hygiene opportunity should be followed by a corresponding hand hygiene procedure in order for the hand hygiene opportunity to be deemed “compliant”. To determine whether a hand hygiene opportunity is compliant, the system includes one or more sets of compliance rules that define compliant and non-compliant hand hygiene opportunities. For example, the compliance rules may define a predetermined period of time within which a dispense event must follow an activation event in order to determine the hand hygiene opportunity to be compliant. In other words, to determine whether a hand hygiene opportunity is compliant, the system may determine whether a dispenser actuation event occurred within a predetermined period of time from the toilet/urinal activation event. If a dispenser actuation event is sensed within the predetermined period of time, the hand hygiene opportunity is determined to be “compliant”. If a dispenser actuation event does not occur within the predetermined period of time from the activation event, the hand hygiene opportunity is determined to be “non-compliant.”


In some examples, the compliance rules may further associate each toilet/urinal with one or more hand hygiene product dispensers, and only actuation of one of the associated dispensers within a predetermined period of time will result in a compliant hand hygiene procedure. For example, one or more toilets/urinals and one or more hand hygiene product dispensers may be associated with each other due to their being installed in the same restroom or other area of concern. In this way, only usage of one of the associated hand hygiene dispensers within the predetermined period of time will result in a compliant hand hygiene procedure. This may help to identify when usage of bathroom facilities, such as a toilet or a urinal, is not followed by performance of a compliant hand hygiene procedure before a user leaves the restroom or other area of concern.


In some examples, a plurality of compliance badges are uniquely assigned to each of a plurality of users whose hand hygiene practices are to be monitored. Upon sensing of an activation event and/or dispense event, badge identification information is obtained from the badge and associated with the activation event and/or dispense event. In this way, individual compliance/non-compliance with hand hygiene procedures may be monitored and analyzed.


In some examples, the predetermined period of time may be defined differently for different situations. For example, the predetermined period of time within which a dispense event must follow an activation event may be customized for each toilet/urinal based on one or more factors. For example, the predetermined period of time for hand hygiene opportunity generated from a toilet activation may be different than the predetermined period of time for a hand hygiene opportunity generated from a urinal activation. As another example, the predetermined period of time may be adjusted for each individual toilet/urinal based on the size (dimensions) of the restroom, the distance between a toilet or urinal from the associated hand hygiene product dispensers, the number of toilets/urinals in a restroom, or other factor affecting the amount of time a user should be reasonably given to perform a compliant hand hygiene procedure following usage of bathroom facilities. The acceptable predetermined time frame between hygiene signal and wash signal will may be tuned, for example, by bathroom size and by a statistical analysis of the activation event data and the dispense event data and devising a cut-off related a confidence interval around the mean time between flush and wash, or it may be determined via a machine learning algorithm. Different compliance rules may therefore apply to different toilets and/or urinals, depending upon one or more of these factors.


Upon sensing each toilet/urinal activation event, an activation sensor may store a data record of the activation event, including an associated time stamp identifying the date and time of the activation. The activation event data may further include a toilet/urinal identifier, an activation sensor device identifier, a restroom/location identifier, a facility identifier, and/or any other information pertinent to the activation event. In examples where compliance badges are used, the activation event data may include a badge/user identifier. The activation sensors may further include communication capability that enables the activation sensors to connect and exchange data with one or more local or remote computing devices. For example, each activation sensor may include a wired or wireless transmitter/receiver by which it may transmit the activation event data to one or more local and/or remote computing devices for further analysis and reporting. The activation sensors may further receive operating setting data, software updates, or requests from the one or more local and/or remote computing devices via the wired or wireless transmitter/receiver. The communications may occur through one or more wired or wireless local or wide area network(s), the internet, a mobile phone network, or other means of inter-device connectivity. The activation sensors may further include communication capability that enables the activation sensors to connect and exchange data with one or more compliance badges. For example, each activation sensor may include a wireless short-range transmitter/receiver by which it may communicate with and receive badge identification data from one or more compliance badges within range of the activation sensor.


Similarly, upon sensing each hand hygiene dispenser actuation, a dispenser actuation sensor may store a data record of the dispense event, including an associated time stamp identifying the date and time of the dispenser actuation. The dispense event data may further include a dispenser identifier, an actuation sensor identifier, a location identifier, a facility identifier, and/or any other information pertinent to the dispenser actuation event. In examples where compliance badges are used, the dispense event data may include a badge/user identifier. The dispenser actuation sensors may further include communication capability that enables the sensors to connect and exchange data with one or more local or remote computing devices. For example, each dispenser actuation sensor may include a wired or wireless transceiver by which it may transmit the dispense event data to one or more local and/or remote computers for further analysis and reporting. The actuation sensors may further receive operating setting data, software updates, or requests from the one or more local and/or remote computing devices via the wired or wireless transmitter/receiver. The communications may occur through one or more wired or wireless local or wide area network(s), the internet, a mobile phone network, or other means of inter-device connectivity. The dispenser actuation sensors may further include communication capability that enables the dispenser actuation sensors to connect and exchange data with one or more compliance badges. For example, each dispenser actuation sensor may include a wireless short-range transmitter/receiver by which it may communicate with and receive badge identification data from one or more compliance badges within range of the dispenser actuation sensor.


Transmission of the activation event data and/or the dispense event data by the activation sensors and the dispenser actuation sensors to the local or remote computing devices may be wired or wireless. The communications may further occur in real-time, such as upon detection of each activation event and/or dispense event. The communications may alternatively or in addition occur at defined periodic times or time intervals, and/or may be on demand upon request of a local or remote computing device.


The analysis and/or reporting performed by the local and/or remote computing systems may be performed in real-time, on a periodic basis, or on demand upon receipt of a request from a user computing device.


The hand hygiene product dispensers may include any type of manual or automatic (i.e., touchless, touch free, or hands free) hand hygiene product dispenser that dispense any type of hand hygiene product intended for cleansing, disinfecting, or sanitizing of the hands. Such hand hygiene products may include hand soaps, hand sanitizers, hand rubs, alcohol-based hand rubs, aqueous scrubs, or any other type of hand hygiene product. The hand hygiene products may be in the form of a liquid, a gel, a lotion, a foam, a solution, or any other form of hand hygiene product.


In some examples, the system as a whole may include a plurality of toilet/urinal activation sensors, each associated with a different one of a plurality of toilets/urinals. The system may further include a plurality of dispenser actuation sensors, each associated with a different one of a plurality of hand hygiene product dispensers. Each toilet/urinal activation sensor may be further associated with one or more of the plurality of dispenser actuation sensors. The system may further include a plurality of compliance badges, each uniquely associated with a different one of a plurality of users. However, it shall be understood that the system need not necessary include compliance badges. In some applications, for example, monitoring and analysis of identified individual hand hygiene compliance is not desired.


The system may, either locally or remotely (or both), analyze the toilet/urinal activation event data from the activation sensors and the dispense event data from the dispenser actuation sensors to monitor, measure, and/or generate reports on hand hygiene compliance after usage of bathroom facilities.


The system may generate one or more measures of hand hygiene compliance. In one example, the system may measure and report a hand hygiene compliance score based on the activation event data and the dispense event data. In some examples, the hand hygiene compliance score may be based on the following:







%





Hand





Hygiene





Compliance

=


Hand





Hygiene





Opportunities
×
100


Compliant





Hand





Hygiene





Events






Example hand hygiene compliance scores may be determined on a per toilet/urinal basis, a per dispenser basis, a per restroom basis, a department basis, a facility-wide basis, corporate-wide basis, or other location-based measure. In examples where compliance badges are used, hand hygiene compliance scores may be determined on a per user or per compliance badge basis. Example hand hygiene compliance scores may also be determined by time period, workday shift, day, week, month, or other time-based measure. It shall be understood, however, that other measures of hand hygiene compliance may also be used, and that the disclosure is not limited in this respect. The activation event data, dispense event data, and/or compliance scores may be averaged, combined, or otherwise manipulated to identify where and when hand hygiene compliance is satisfactory or unsatisfactory, to identify trends or patterns, provide benchmarks, or to measure the effect on compliance after implementation of training procedures or changes in hand hygiene practices (such as changes in hand hygiene products dispensed, the type of dispensers used, the number or location of dispensers within a restroom or other area of concern, etc.).


In addition to monitoring hand hygiene practices, collection of the bathroom fixture activation signal may additionally provide the opportunity to trigger a cleaning message after a defined number of sensed activations. It may also serve to normalize worker hours and/or soap usage when combined with a dispense signal from a hand hygiene product dispenser thereby creating a way to standardize scores for other connected fixtures in a facility.


In some examples, the hand hygiene compliance information collected and generated is anonymous; that is, the individual worker or employee performing a toilet/urinal activation and/or a hand hygiene dispenser actuation is not identified. In other examples, the system may also include worker identification methods such as electronic compliance badges, and the employee/user data may also be collected and analyzed in the hand hygiene compliance system as described herein.



FIG. 1 is a block diagram illustrating an example restroom 140 installed for hand hygiene compliance monitoring after usage of bathroom facilities according to the present disclosure. Example restroom 140 includes several standard bathroom fixtures including a toilet 130, two urinals 132A and 132B, two sinks 122A and 122B and two hand hygiene product dispensers 120A and 120B. Each toilet/urinal is associated with a toilet/urinal activation sensor, referred to generally as a toilet/urinal activation sensor module 150. For example, toilet 130 is associated with activation sensor module 150A, urinal 132A is associated with activation sensor module 150B, and urinal 132B is associated with activation sensor module 150C. Each hand hygiene product dispenser 120 is associated with a dispenser actuation sensor module 100. For example, hand hygiene product dispenser 120A is associated with dispenser actuation sensor module 100A and hand hygiene product dispenser 120B is associated with dispenser actuation sensor 100B. The hand hygiene product dispensers 120 may, but need not necessarily have, a one-to-one correspondence with sinks 122.


In some examples, compliance badges 10 are worn or carried by users or employees, such as user 11, of the facility in which hand hygiene compliance is to be monitored. The badges 10 are capable of short-range wireless communication with the dispensers 120, the dispenser actuation modules 100, and/or the toilet/urinal activation sensor modules 150 in order to monitor and track hand hygiene compliance of individual users at the facility.


Each activation sensor module 150 senses activation (e.g., flushing) of the respective toilet or urinal. In some examples, each activation sensor module 150 is connected to receive an activation signal from an automatic toilet flushing device installed on the respective toilet/urinal. In those examples, the activation sensors 150 are able to make use of signals generated by automatic flushing devices that are already installed in many commercial bathrooms. In other examples, each activation sensor module 150 is connected to receive an activation signal from manual activation sensor, such as a sensor that senses mechanical movement of the toilet flush lever/handle, a water level sensor in the toilet tank, a sensor on the fill or flush valve, a sensor associated with the toilet tank float or float arm, or other mechanism for sensing flushing of a toilet/urinal, such as a tilt sensor, vibration sensor, acoustic sensor, or other type of sensor.


The automatic toilet flushing device may be implemented using a customized or commercially available automatic toilet flushing device.


Each activation sensor module 150 may include an internal memory or data storage device. Upon sensing of a toilet/urinal activation event, an activation sensor module 150 may store a data record of the activation event, including an associated time stamp identifying the date and time of the activation. The activation event data may further include a toilet/urinal identifier, an activation sensor device identifier, a restroom/location identifier, a facility identifier, and/or any other information pertinent to the activation event. For example, activation sensor module 150A may store an activation event including an activation event identifier or event number, an identifier uniquely assigned to toilet 130, a sensor identifier uniquely associated with activation sensor module 150A, a restroom identifier uniquely associated with restroom 140, a facility identifier uniquely associated with the building, restaurant, healthcare facility or other location identifier in which restroom 140 is located.


In examples where users wear or carry compliance badges 10, the activation sensor module 150 may further include short range wireless communication capability that enables the activation sensor module 150 to communicate with compliance badge 10 within range of the activation sensor module. In such examples, upon sensing of a toilet/urinal activation event, activation sensor 150 may wirelessly communicate with a compliance badge 10 within range of the toilet/urinal activation sensor, receive badge identification data or user identification data from the badge 10, associate the badge identification data with the activation event, and store the user and/or badge identification data as part of the activation event data.


Each activation sensor module 150 may further include communication capability that enables activation sensor module 150 to connect and exchange data with one or more local or remote computing devices (see, e.g., FIG. 2). For example, each activation sensor module 150 may include a wired or wireless transmitter/receiver by which it may transmit the activation event data to one or more local and/or remote computing devices for further analysis and reporting. The activation sensors may further receive operating setting data, software updates, or requests from the one or more local and/or remote computing devices via the wired or wireless transmitter/receiver. The communications may occur through one or more wired or wireless local or wide area network(s), the internet, a mobile phone network, or other means of inter-device connectivity. The activation event data and other transmissions to and from devices 150A-150C may be routed through one or more wired or wireless network hubs or repeaters, such as device 142, or through other existing local network infrastructure, before being transmitted to one or more local or remote computing devices for analysis.


Each dispenser actuation sensor module 100 senses manual of automatic actuation of the respective hand hygiene product dispenser. In some examples, each actuation sensor module 100 is connected to receive an actuation signal from an automatic (i.e., touchless, touch free, or hands free) hand hygiene product dispenser. In other examples, each actuation sensor module 100 is connected to receive an actuation signal from manual actuation sensor, such as a sensor that senses mechanical movement of a dispenser pushbar or button, mechanical movement of a pump or portions of a pump, or other mechanism for sensing manual actuation of hand hygiene product dispenser.


Each actuation sensor module 100 may include an associated memory or data storage device. Upon sensing of a dispense event, an actuation sensor module 100 may store a data record of the actuation event, including an associated time stamp identifying the date and time of the dispenser actuation. The actuation event data may further include a dispense event identifier or number, a dispenser identifier, an activation sensor device identifier, a restroom/location identifier, a facility identifier, and/or any other information pertinent to the activation event. For example, actuation sensor module 100A may store in its associated memory or data storage device actuation event data including an actuation event identifier or event number, an identifier uniquely assigned to dispenser 120A, an sensor identifier uniquely associated with dispenser actuation sensor module 100A, a restroom identifier uniquely associated with restroom 140, a facility identifier uniquely associated with the building, restaurant, healthcare facility or other location identifier in which restroom 140 is located, or other information pertinent to the dispense event.


In examples where users wear or carry compliance badges 10, the dispenser actuation sensor module 100 may further include short range wireless communication capability that enables the dispenser actuation sensor module 100 to communicate with compliance badge 10 within range of the activation sensor module. In such examples, upon sensing of a dispenser actuation event, dispenser actuation sensor module 100 may wirelessly communicate with a compliance badge 10 within range of the dispenser actuation sensor, receive badge identification data or user identification data from the badge 10, associate the badge identification data with the dispense event, and store the user and/or badge identification data as part of the dispense event data.


Each actuation sensor module 100 may further include communication capability that enables actuation sensor module 100 to connect and exchange data with one or more local or remote computing devices (see, e.g., FIG. 2). For example, each actuation sensor module 100 may include a wired or wireless transmitter/receiver by which it may transmit the actuation event data to one or more local and/or remote computing devices for further analysis and reporting. The actuation sensors may further receive operating setting data, software updates, or requests from the one or more local and/or remote computing devices via the wired or wireless transmitter/receiver. The communications may occur through one or more wired or wireless local or wide area network(s), the internet, a mobile phone network, a satellite network, or other means of inter-device connectivity. The actuation event data and other transmissions to and from devices 100A-100C may be routed through one or more wired or wireless network hubs or repeaters, such as device 142, or through other existing local network infrastructure, before being transmitted to one or more local or remote computing devices for analysis.


In accordance with the present disclosure, each toilet/urinal activation event detected by the system will be identified as a hand hygiene opportunity. The system further determines whether each identified hand hygiene opportunity is followed by a corresponding compliant hand hygiene procedure. For example, in an application that does not utilize compliance badges, assume an employee enters restroom 140 and uses toilet 130, which includes an automatic (i.e., touchless, touch free, or hands free) flushing device. The automatic flushing device generates an activation signal to automatically flush the toilet in accordance with a predetermined method. The toilet activation signal generated by the toilet 130 automatic flushing device is also received by the activation sensor module 150A, which determines that an activation event has occurred, and stores the activation event data including a time stamp including the date and time at which the activation signal was received, an activation event number, the identifier corresponding to toilet 130, the identifier corresponding to activation sensor module 150A, an identifier corresponding to the bathroom 140, etc. In systems including compliance badges, upon receiving the toilet activation signal, the activation sensor module would initiate short range wireless communication to locate and receive compliance badge identification data from any compliance badges within range of the activation sensor module. The activation event data stored by the activation sensor module 150A would include the badge identification data received from the employee's compliance badge.


To determine whether the hand hygiene opportunity associated with the employee's use of toilet 130 is compliant, the system determines whether a dispenser actuation event at one of dispensers 120A or 120B within the restroom 140 occurred within a predetermined period of time from the toilet/urinal activation event. If a dispenser actuation event at one of dispensers 120A or 120B is sensed by dispenser actuation sensors 100A or 100B, respectively, within the predetermined period of time, the hand hygiene opportunity identified by the activation of toilet 130 is determined to be “compliant”. If the dispenser actuation sensors 100A or 100B do not detect a dispenser actuation event at either dispenser 120A or 120B, respectively, within the predetermined period of time from the activation event, the hand hygiene opportunity is determined to be “non-compliant.” In systems where compliance badges are not used, the system may determine whether a dispenser actuation occurred within the predetermined period of time. In systems where compliance badges are used, the system may determine whether a dispenser actuation corresponding to the same badge identification data occurred within the predetermined period of time of the toilet/urinal activation.


In this example, each toilet/urinal 130, 132A and 132B may be associated with hand hygiene product dispensers 120A and 120B by virtue of their installation in the same restroom, and only actuation of one of the associated dispensers within a predetermined period of time will result in a compliant hand hygiene procedure. In this way, only usage of one of the associated hand hygiene dispensers within the predetermined period of time will result in a compliant hand hygiene procedure. This may help to ensure that a compliant hand hygiene procedure is performed before a user leaves the restroom 140 whenever an activation event is detected at one of the toilets 130 or urinals 132A, 132B within the restroom 140.


In some examples, the predetermined period of time may be defined differently for different situations. For example, the predetermined period of time within which a dispense event must follow an activation event may be customized for each toilet/urinal based on one or more factors. For example, the predetermined period of time for a hand hygiene opportunity generated from an activation event at toilet 130 may be different than the predetermined period of time for a hand hygiene opportunity generated from an activation event at urinal 132A and/or urinal 132B. This may be due at least in part to the different amounts of time in which a user may reasonably be expected to wash their hands after usage of a toilet as compared to usage of a urinal. The differing predetermined period(s) of time may further be due at least in part to the physical layout of the bathroom and the resulting different distances between a first bathroom fixture (e.g., toilet or urinal) and an associated hand hygiene product dispenser and the distance between a second bathroom fixture (e.g., toilet or urinal) and an associated hand hygiene product dispenser. This may further be due at least in part to the habits of the users of the restroom and/or any required bathroom or handwashing procedures of the workplace. In some examples, the predetermined period of time may be customized or adjusted for each individual toilet/urinal based on the size (dimensions) of the restroom, the physical layout of the restroom, the distance between a toilet or urinal from the associated hand hygiene product dispensers, the number of toilets/urinals in a restroom, or other factor affecting the amount of time a user should be reasonably given to perform a compliant hand hygiene procedure following usage of bathroom facilities.


For example, a predetermined amount of time for a compliant hand hygiene procedure (dispense event) may be between 10-120 seconds after sensing of a toilet activation event, whereas a predetermined amount of time for a compliant hand hygiene procedure (dispense event) may be 3-90 seconds after sensing of a urinal activation event. However, it shall be understood that these time frames are given for purposes of example only, and that the amounts of time may be adjusted and customized according to the factors discussed herein, and that the disclosure is not limited in that respect.



FIG. 2 is a block diagram illustrating an example hand hygiene compliance system 101 in accordance with the present disclosure. One or more facilities 110A-110N, such health care facilities, restaurants, or food processing facilities, are each associated with a local computing system, such as local computing system 112A, that is in communication, via network 160, with a remote computing system 180 and one or more user computing device(s) 170. Although certain features of system 100 are shown and described herein as being performed by remote computing system 180, in other examples, the features and techniques attributed to system remote computing system 180 may be performed internally, by local components of local computing systems 112A-112N, or by remote user computing device(s) 170.


Each facility 110A-110N includes an associated local computing system 112A-112N, respectively. Each facility, such as facility 110A, further includes one or more hand hygiene product dispensers 120A-120N, each associated with one of a plurality of dispenser actuation sensors 100A-100N. Each facility further includes a plurality of toilet/urinal activation sensors 150A-150N, each associated with one of a plurality of toilets or urinals within the facility, as shown in FIG. 1. In some examples, each facility further includes a plurality of compliance badges 10A-10N, each uniquely associated with a different one of a plurality of users.


Remote computing system 180 includes one or more processors 182, a hand hygiene analysis module 184, and a hand hygiene reporting module 186. A data store 190 may be local or a remotely located from the remote computing system 180, and includes data storage for facility data 191, hand hygiene system data 192, compliance rule data 193, dispenser data 194, activation data 196, and reports/analysis data 198. Hand hygiene analysis module 184 includes programmed instructions that, when executed by one or more processors 182, analyze the toilet/urinal activation event data generated by the activation sensors 150A-150N and the dispense event data generated by the dispenser actuation sensors 120A-120N to monitor compliance with established hand hygiene procedures after usage of bathroom facilities. Hand hygiene reporting/service module 186 includes instructions that, when executed by the one or more processors 182, provide a hand hygiene compliance monitoring service, thus providing the results of the analysis performed under direction of the analysis module 184, to user computing devices 170 or to the local computing systems 112A-112N.


Facility data 191 includes data concerning each of facilities 110A-110N, such as the name of the facility; the type of facility (e.g., restaurant, healthcare facility, food processing facility, etc.); location information such as address, city, state, and zip code; employee information; management information; accounting information; business information; information concerning those persons or entities authorized to access the reports generated by the hand hygiene compliance system; and any other pertinent facility data that may be used or generated by the remote computing system 180 during performance of the hand hygiene compliance analysis or providing access to the hand hygiene compliance monitoring service.


Hand hygiene system data 192 includes data concerning the physical and virtual set up of the various devices and sensors that make-up the hand hygiene compliance monitoring systems in each location 110A-110N. For example, hand hygiene system data 192 includes identification and other relevant information (such as dispenser type, location, dispensed product name; dispensed product type (e.g., sanitizer, soap, alcohol, etc.); dispensed product form (solid, liquid, gel, foam, etc.); dispensed product amounts (by volume, weight, or other measure)), etc. for each of the hand hygiene product dispensers 120A-120N; identification and other relevant information for each of the dispenser actuation sensors 100A-100N; and identification and other relevant information for each of the toilet/urinal activation sensors 150A-150N at each location 110A-110N. The hand hygiene system data 192 may also include any of the following: data uniquely associating each dispenser 120A-120N with one of dispenser actuation sensors 100A-100N; data uniquely associating each dispenser 120A-120N, dispenser actuation sensor 100A-100N, and activation sensors 150A-150N with a specific room within a facility 110; data associating each activation sensor module 150A-150N with one or more specific ones of the dispensers 120A-120N and/or dispenser actuation sensors 100A-100N; data defining the predetermined period of time within which a compliant hand wash procedure must be performed for each of the toilet/urinal activation sensors 150A-150N; and any other hand hygiene system information that may be used or generated by the hand hygiene analysis module during performance of the hand hygiene compliance analysis or by the hand hygiene reporting module while providing access to the hand hygiene compliance monitoring service. In examples where compliance badges are used, hand hygiene system data 192 may include assigned compliance badge identification data uniquely associated with each employee or user in the system for which hand hygiene compliance is to be monitored and/or analyzed.


Compliance rules 193 include one or more sets of rules used by computing system 180 during analysis of the activation event data and the dispense event data to determine whether a hand hygiene opportunity is compliant. The compliance rules define compliant and non-compliant hand hygiene opportunities. The sets of compliance rules may be different depending upon the factors described herein, such as the number and type of toilets/urinals in a restroom, the preferred hand hygiene practices of the establishment or facility, the dimensions or layout of the restroom, the habits of the employees of the establishment, whether or not compliance badges are implemented in the particular system, etc. Each toilet/urinal in a facility is therefore associated with one of the sets of compliance rules for determining whether a compliant hand hygiene procedure was performed. The compliance rules may include, for example, identifiers for one or more associated dispensers at which a compliant dispense event may take place and a predetermined period of time in which a dispense event at an associated dispenser must take place in order for an activation at the toilet/urinal to be compliant.


Dispense event data 194 stores the dispense event records received from dispenser actuation sensors 100A-100N from each facility 110A-110N. The dispense event data may include but is not limited to a time stamp identifying the date and time of the dispenser actuation, a dispenser identifier, a dispenser actuation sensor identifier, a location (e.g., restroom) identifier, a facility identifier, and/or any other information pertinent to the dispenser actuation event. In systems employing compliance badges, the dispense event data may further include badge identification data received from a compliance badge within range of the dispenser actuation sensor module at the time of the dispense event.


Activation event data 196 stores all of the activation event records received from toilet/urinal activation sensors 150A-150N from each facility 110A-110N. The activation event data may include but is not limited to a time stamp identifying the date and time of the activation event, a toilet/urinal identifier, a toilet/urinal activation sensor identifier, a location (e.g., restroom) identifier, a facility identifier, and/or any other information pertinent to the toilet/urinal activation event. In systems employing compliance badges, the activation event data may further include badge identification data received from a compliance badge within range of the toilet/urinal activation sensor module at the time of the activation event.


Reports/analysis data 198 stores some or all of the results of analysis executed by hand hygiene analysis module 184 and/or hand hygiene reporting/service module 186. Reports may be generated, for example, during provision of a hand hygiene compliance monitoring service under control of reporting/service module 186 to authorized employees at one or more of the facilities 110A-110N. For example, a user working from a user computing device 170 (which may be local to or remotely located from the facility itself) may access the hand hygiene compliance monitoring service provided by remote computing system 180 and reporting/service module 186 to request hand hygiene compliance reports that provide detailed information and analysis of the hand hygiene compliance at the one or more facilities 110A-110N. Access to the hand hygiene compliance monitoring service may be accessed via a username and password, and any reports generated may be associated with the user and stored as reports 198 for future access.


Network 160 represents any public or private communications network, for instance, cellular, Wi-Fi, and/or other types of wired or wireless networks, for transmitting data between computing systems, servers, and computing devices. Local computing systems 112A-112N, remote user computing devices 170 and/or remote computing system 180 may exchange data, via network 160, with each other to provide a hand hygiene compliance monitoring service that is accessible to local computing system 112A-112N and/or remote user computing devices 170 when such computing systems and devices are connected to network 160.


Network 160 may include one or more network hubs, network switches, network routers, repeaters, or any other network equipment, that are operatively inter-coupled thereby providing for the exchange of information between systems/computing devices 112, 170 and 180. Local computing system 112A-112N, user computing devices 170, and remote computing system 180 may transmit and receive data across network 160 using any suitable communication techniques. Local computing systems 112A-112N, user computing devices 170, and remote computing system 180 may each be operatively coupled to network 160 using respective network links. The links coupling local computing systems 112A-112N, user computing devices 170, and remote computing system 180 to network 130 may be Ethernet or other types of network connections and such connections may be wireless and/or wired connections.


Local computing system 160 and remote computing system 180 may represent any suitable computing systems, such as one or more desktop computers, laptop computers, mainframes, servers, cloud computing systems, etc. capable of sending and receiving information both to and from a network, such as network 160. Remote computing system 180 may host (or at least provides access to) a hand hygiene compliance monitoring service. In some examples, remote computing system 180 represents a cloud-based computing system that provides access to their respective services via a cloud computing network.


User computing devices 170 may represent one or more individual mobile or non-mobile computing devices. Examples of a user computing device 170 include a mobile phone, a tablet computer, a laptop computer, a desktop computer, a server, a mainframe, a set-top box, a television, a wearable device (e.g., a computerized watch, computerized eyewear, computerized gloves, etc.), a home automation device or system (e.g., an intelligent thermostat or home assistant device), a personal digital assistant (PDA), a gaming system, a media player, an e-book reader, a mobile television platform, an automobile navigation or infotainment system, or any other type of mobile, non-mobile, wearable, and non-wearable computing device configured to communicate and receive information via a network, such as network 160.


Remote computing system 180 may communicate with user computing devices 170 and/or devices in the local computing systems 112A-112N via network 160 to give computing devices 170 or local computing systems 112A-112N access to the hand hygiene compliance monitoring service provided by remote computing system 180.


Hand hygiene reporting module 186 may generate a variety of reports that present the analyzed data for use by the person(s) responsible for overseeing hand hygiene compliance at each location or facility 110A-110N. Reporting module 186 may generate a variety of reports to provide users local to each facility 110A-110N or users of remote computing devices 170 with both qualitative and quantitative data regarding hand hygiene compliance at their location or facility, and/or to compare data over time to determine whether improvement has occurred. Reporting module 186 may also allow users to benchmark hand hygiene compliance at multiple facilities.


For example, reporting application 186 may generate one or more reports concerning hand hygiene compliance at the facility. The reports may include a comparison of hand hygiene opportunities and compliant hand hygiene opportunities at the facility over time to determine whether improvement in hand hygiene practices has occurred. Reporting application 186 may also generate one or more reports including hand hygiene opportunity/compliance data at multiple facilities.


Local computing systems 112A-112N (FIG. 1) or an associated datastore may also store the above-described hand hygiene data associated with that facility. Local computing system 112A-112N and/or user computing devices 170 may also include local analysis and reporting applications such as those described above with respect to analysis module 184 and reporting module 186. In that case, reports associated with that particular facility may be generated and viewed locally, if desired. In another example, all analysis and reporting functions are carried out remotely at remote computing system 100, and reports may be requested, accessed, viewed, downloaded or otherwise obtained remotely. In other examples, some of the local computing systems 112A-112N may include local storage and/or analysis and reporting functions while other of the local computing systems 112A-112N may rely on remote storage and/or analysis and reporting. Thus, although the general case of data being stored and analysis/reporting being carried out and provided by the server computing system 180 is described herein, it shall be understood that these storage, analysis and reporting functions may also be carried out locally or at some other location, and that the disclosure is not limited in this respect.


Reporting module 186 may generate many different types of reports and present the raw data and/or the results of the analysis in many different ways during provision of the hand hygiene compliance monitoring service. Reporting module 186 may permit the user to request reports that convey the data in a variety of different ways. For example, reporting module 186 may permit a user to select a particular format (text, graphs, tables, combinations thereof, etc.); select by data type (dispense event data, activation event data, etc.); select by time, time period, or date; select by shift, department, facility or multiple facilities; by percent compliance (for example, to select or rank by highest, lowest or average compliance); or to create and generate reports based on nearly any data collected and stored by hand hygiene compliance system 100. In systems where compliance badges are used, the reporting module 186 may generate reports based on compliance badge identification data or employee identification data; and may permit a user to generate and view hand hygiene compliance data on a per employee/user basis.


These reports may include, for example, detailed analysis and reporting on key metrics, including hand hygiene compliance department, type of department, shift, individual facility, individuals, across multiple facilities, corporate-wide, etc. The reports may benchmark current hand hygiene practices, and may include trending of various key metrics over time, identify particular problem areas (e.g., certain workday shifts, employees, or locations having unsatisfactory hand hygiene compliance) provide actionable improvement plans and assess current practices relative to best hand hygiene practices. Reports may compare highest, lowest and/or average percentage compliance by any of these breakdowns; reports compare highest, lowest and/or average number of dispense events per dispenser. Reports may present trend data showing past, present and projected future hand hygiene compliance.


The reports may indicate whether the number of dispense events per dispenser, per room, per shift, per employee, per department, per facility etc. is within acceptable limits and whether it met specified targets for dispense events for each of these parameters.


The reports may highlight particular problems areas where hand hygiene compliance thresholds are not being met. For example, the reports may identify employees, shifts, departments or facilities having hand hygiene compliance below a specified threshold. This information can help to identify where additional training or corrective action may be necessary.


The reports may also provide a summary of recommended next steps that a facility may take to improve their hand hygiene compliance results in the future. For example, suggested next steps may be given for continuous improvement and education directed toward identified employees, shifts or departments, operational processes, hand hygiene outcome efficiency, etc.



FIG. 3 is a block diagram illustrating an example implementation of a dispenser actuation sensor module 100. In this example, dispenser actuation sensor module 100 includes a controller 102, a power source 107, such as one or more batteries, an actuation or dispense event sensor 105, a transmitter/receiver module 104, and a memory or data storage device 106.


A dispense event module 103 stored in memory 106 and executed by controller 102 provides the instructions by which dispense event module 100 senses/receives a dispenser actuation signal from an associated dispenser and stores or transmits the corresponding dispense event data to a local or remote computing device for further analysis.


Dispense event sensor 105 detects actuation of the associated hand hygiene product dispenser. For example, dispense event sensor 105 may be implemented using a mechanical or electronic switch, a photo interrupter, a flex sensor, an acceleration sensor, an IR interrupter, an IR reflectance sensor, or other mechanism for detecting mechanical movement of a dispenser button or bar when manually activated by a user, detecting movement of a dispensing mechanism or pump that causes the hand hygiene product to be dispensed, optically detecting such mechanical movement(s) or optically detecting movement of dispensed product, etc. The dispense event sensor 105 may further be connected to receive one or more signals from an automatic (i.e., touchless, touch free, or hands free) hand hygiene product dispenser that is generated upon detection of presence of a user in close proximity to the dispenser or presence of a user's hands under or in close proximity to the dispenser, and/or that is generated to cause an automatic dispense mechanism or pump to dispense the hand hygiene product in response to detection of presence of the user or the user's hands. In the event of an automatic dispenser, the signal received from the dispenser may include dispenser actuation data including a time stamp for the actuation, a dispenser identifier, and other pertinent dispenser information. Alternatively, the dispenser identifier may be stored by the actuation sensor 100.


Further example automatic hand hygiene product dispensers and/or example dispenser actuation sensor modules are described in U.S. Pat. No. 8,502,680 issued Aug. 6, 2013, U.S. Pat. No. 8,395,515 issued Mar. 12, 2013, U.S. Pat. No. 8,872,665 issued Oct. 28, 2014, U.S. Pat. No. 8,842,406 issued Jul. 9, 2013, U.S. Pat. No. 8,783,511 issued Jul. 22, 2014, U.S. Pat. No. 8,564,431 issued Oct. 22, 2013, U.S. Pat. No. 8,264,343 issued Sep. 11, 2012, U.S. application Ser. No. 14/819,349 filed Aug. 5, 2015, U.S. application Ser. No. 15/406,129 filed Jan. 13, 2017, and U.S. Provisional Application No. 62/468,214 filed Mar. 7, 2017, each of which is incorporated herein by reference in their entirety.


Storage device(s) 106 stores an actuation sensor identifier 108 uniquely associated with actuation sensor module 100. The actuation sensor identifier may also include additional data associated with the actuation sensor module, such as the associated dispenser identifier, location information such as a restroom number or identifier, a facility identifier, etc., or other information that may be included in the dispense event data generated upon sensing of a dispense event.


Storage device(s) 106 further stores dispense event data 109 associated with each detected dispenser actuation event. For example, dispense event data for each dispense event may include a time stamp identifying the date and time of the dispenser actuation, a dispense event identifier or count, a dispenser identifier, an actuation sensor identifier, a location identifier, a facility identifier, and/or any other information pertinent to the dispenser actuation event. For applications in which compliance badges are used, the dispense event data may further include compliance badge identification data obtained from a compliance badge within range of the dispenser module at or near the time of the dispense event.


Transmitter/receiver 104 provides for wireless communication between actuation sensor module 100 and a local computing network. For example, transmitter/receiver 104 may be implemented IR, RF, Wi-Fi, satellite, cellular, Bluetooth, or other wireless communication techniques. However, it shall be understood that other wired or wireless communication modules and/or protocols could be used and that the disclosure is not limited in this respect. Transmitter/receiver 104 may also provide for short-range wireless communication between actuation sensor module 100 and one or more compliance badges 10. In the examples described herein, the short-range wireless communication may include distances of up to a few meters. Such relatively short transmission distances may be accomplished using any type of short-range communication techniques including short-range radio (RF) (e.g., Bluetooth, ZigBee, or ultra-wide band (UWB)) communication, infrared (IR) communication, or near field (NFC) communication techniques.


Controller 102 executes instructions stored in dispense event module 103 that control detection of dispense events, communication with one or more compliance badge(s) 10, and/or communication to and from dispense event sensor module 100 via transmitter/receiver 104. For example, upon receiving each dispenser actuation signal from dispense event sensor 105, controller 102 generates a dispense event record, including corresponding time stamp, dispenser identifier, and/or dispenser actuation sensor module identifier, and stores the dispense event record in dispense event data 109. Controller 102 may further initiate short range wireless communication in an attempt to locate any compliance badges within range of dispenser module 100, receive the associated compliance badge identification data, and store the badge identification data as part of the dispense event data. Dispense event module 103 may transmit dispense event record each time a dispense event occurs, may transmit one or more stored dispense event records on a periodic basis, or may transmit one or more dispense event records upon request from a local or remote computing device.



FIG. 4 is a block diagram illustrating an example implementation of a toilet/urinal activation sensor module 150. In this example, toilet/urinal activation sensor module 150 includes a power source 153, such as one or more batteries, an activation event sensor 155, a controller 152, a transmitter/receiver module 154, and a memory or data storage device 156.


An activation event module 159 stored in memory 156 and executed by controller 152 provides the instructions by which activation event module 150 senses/receives a dispenser actuation signal from an associated dispenser and stores or transmits the corresponding dispense event data to a local or remote computing device for further analysis.


Toilet/urinal activation event sensor 155 detects activation (e.g., flushing) of the associated toilet or urinal. For example, activation event sensor 155 may be implemented using a mechanical or electronic switch, or other mechanism for detecting mechanical movement of a toilet lever or handle when manually activated by a user, detecting movement of a toilet float, or sensing the opening or closing of a toilet/urinal flush or fill valve, or by sensing any of the above mechanical motions using a tilt sensor or vibration sensor, or by using an acoustic sensor, etc. In another example, activation event sensor 105 receives an activation signal from an automatic (i.e., touchless, touch free, or hands free) toilet flushing device.


An example automatic toilet flushing unit operates as follows. A typical automatic flushing unit includes a presence sensor that senses when a user enters its effective range. Once a user remains in the effective range for a certain minimum period of time, the unit waits for the user to step away out of the effective range, and will then initiate a flush cycle. Many units allow either the effective range and/or the minimum amount of time to be adjusted. Initiation of the flush cycle includes generation of an electronic activation signal, which may be sensed or received by a toilet/urinal activation sensor module as described herein.


Storage device 156 stores a toilet/urinal activation sensor identifier 157 that uniquely associated with activation sensor module 100. The activation sensor identifier 157 may also include additional data associated with the activation sensor module 100, such as the associated toilet/urinal identifier, a location identifier, or other information that may be included in the activation event data generated upon sensing of a toilet/urinal activation event.


Storage device 156 further stores activation event data 158 associated with each detected toilet/urinal activation event. For example, activation event data for each detected activation event may include a time stamp identifying the date and time of the toilet/urinal activation, an activation event identifier or number, a toilet/urinal identifier, an activation sensor identifier, a location identifier, a facility identifier, and/or any other information pertinent to the activation event. For applications in which compliance badges are used, the activation event data may further include compliance badge identification data obtained from a compliance badge within range of the activation module at or near the time of the activation event.


Transmitter/receiver 154 provides for wireless communication between activation sensor module 150 and a local computing network. For example, transmitter/receiver 154 may be implemented IR, RF, Wi-Fi, satellite, cellular, Bluetooth, or other wireless communication techniques. However, it shall be understood that other wired or wireless communication modules and/or protocols could be used and that the disclosure is not limited in this respect. Transmitter/receiver 154 may also provide for short-range wireless communication between activation sensor module 150 and one or more compliance badges 10. In the examples described herein, the short-range wireless communication may include distances of up to a few meters. Such relatively short transmission distances may be accomplished using any type of short-range communication techniques including short-range radio (RF) (e.g., Bluetooth, ZigBee, or ultra-wide band (UWB)) communication, infrared (IR) communication, or near field (NFC) communication techniques.


Controller 152 executes instructions stored in activation event module 159 that control detection of toilet/urinal activation events and communication to and from activation sensor module 150 via transmitter/receiver 154. For example, upon receiving each toilet/urinal activation signal from activation event sensor 155, controller 152 generates an activation event record, including corresponding time stamp, toilet/urinal identifier, and/or toilet/urinal activation sensor module identifier, and stores the activation event record in activation event data 158. Controller 152 may further initiate short-range wireless communication in an attempt to locate any compliance badges within range of activation sensor module 150, receive the associated compliance badge identification data, and store the badge identification data as part of the activation event data. Activation event module 159 may transmit activation event record each time an activation event occurs, may transmit one or more stored activation event records on a periodic basis, or may transmit one or more activation event records upon request from a local or remote computing device.



FIG. 9 is a block diagram illustrating an example implementation of a compliance badge 10. In this example, compliance badge 10 includes a power source 17, such as one or more batteries, a controller 12, a transmitter/receiver module 14, and one or more data storage device(s) 16. In some examples, compliance badge 10 may be an entirely passive device and therefore not include any type of batteries or power source, or it may include a power source and one or more active elements as shown in FIG. 9. A badge module 20 stored in storage device(s) 16 and executed by controller 12 provides the instructions by which compliance badge 10 communicates with a toilet/urinal activation sensor(s) 150 and/or dispenser actuation module(s) 100. Compliance badge 10 may further include one or more indicators 22. Indicators 22 may include one or more visual indicators or audible indicators that may be activated to communicate or invite a hand hygiene dispense event, indicate when the user has failed to perform a compliant hand hygiene event, or otherwise communicate hand hygiene status.


Transmitter/receiver 14 provides for short-range wireless communication between compliance badge 10 and one or more activation sensor module(s) 150 and/or one or more dispenser modules 100. In the examples described herein, the short-range wireless communication may include distances of up to a few meters. Such relatively short transmission distances may be accomplished using any type of short-range communication techniques including short-range radio (RF) (e.g., Bluetooth, ZigBee, or ultra-wide band (UWB)) communication, infrared (IR) communication, or near field (NFC) communication techniques.


Controller 12 executes instructions stored in badge module 20 that control communication to and from activation sensor module 150 and/or dispenser actuation module 100 via transmitter/receiver 14. For example, upon receiving each toilet/urinal activation signal from activation event sensor 155, controller 152 of activation sensor module 150 transmits a short-range interrogation signal via transmitter/receiver 154 in an attempt to locate a nearby compliance badge 10 with which to associate the dispense event. A badge 10 that is close enough to establish communication via transmitter/receiver 14 with transmitter/receiver 154 will respond to the interrogation signal and short-range communication between compliance badge 10 and activation sensor module 150 is established. Badge module 20 controls communication of the badge identification data 18 stored in storage device(s) 16 of compliance badge 10 to the activation sensor module 150. Upon receipt of badge identification data from the compliance badge 10, activation sensor module 150 associates the badge identification data with the activation event and stores the activation event record in activation event data 158.


Similarly, upon receiving each dispenser actuation signal from dispense event sensor 105, controller 102 of dispenser actuation sensor module 100 transmits a short-range interrogation signal via transmitter/receiver 104 in an attempt to locate a nearby compliance badge 10 with which to associate the dispense event. A badge 10 that is close enough to establish communication via transmitter/receiver 14 with transmitter/receiver 104 will respond to the interrogation signal and short-range communication between compliance badge 10 and dispenser actuation sensor module 100 is established. Badge module 20 controls communication of the badge identification data 18 stored in storage device(s) 16 of compliance badge 10 to dispenser actuation sensor module 100. Upon receipt of badge identification data from the compliance badge 10, dispenser actuation sensor module 100 associates the badge identification data with the dispense event data and stores the activation event record in storage device(s) 156 in dispense event data 109.



FIG. 5 is a flowchart illustrating a process by which a computing device, such as processors 182 remote computing system 180, determine whether a toilet/urinal activation event was followed by performance of a compliant hand washing procedure. For each toilet/urinal activation event (202), the computing device reviews determines whether any subsequent dispense events occurred at an associated hand hygiene product dispenser within the relevant predetermined period of time (204). If so, the activation/dispense is deemed to be a compliant hand hygiene event (206). If no such dispense event occurred within the relevant predetermined period of time, the toilet/urinal activation is determined to be noncompliant (208).


In some examples, if compliance badges are implemented, detection of an activation event (202) may further include receipt of compliance badge identification data uniquely identifying the compliance badge associated with the activation event. Similarly, in such examples, detection of a dispense event (204) may further include may further include receipt of compliance badge identification data uniquely identifying the compliance badge associated with the dispense event. For each toilet/urinal activation event (202) and associated compliance badge identification data, the computing device reviews determines whether any subsequent dispense events occurred at an associated hand hygiene product dispenser that were associated with matching compliance badge identification data within the relevant predetermined period of time (204). This is to ensure that the hand hygiene dispense event was associated with the same compliance badge (and thus, the same employee or user) with which the toilet/urinal activation event was associated. If so, the activation/dispense is deemed to be a compliant hand hygiene event (206). If no such dispense event with a matching compliance badge identification data occurred within the relevant predetermined period of time, the toilet/urinal activation is determined to be noncompliant (208).


The computing device may further determine a hand hygiene compliance score (210). In one example, the computing device determines the compliance score according to the equation:







%





Hand





Hygiene





Compliance

=


Hand





Hygiene





Opportunities
×
100


Compliant





Hand





Hygiene






Events
.







Example hand hygiene compliance scores may be determined for each toilet/urinal activation event, on a per toilet/urinal basis, a per dispenser basis, a per restroom basis, a department basis, a facility-wide basis, corporate-wide basis, or other location-based measure. Example hand hygiene compliance scores may also be determined by time period, workday shift, day, week, month, or other time-based measure. It shall be understood, however, that other measures of hand hygiene compliance may also be used, and that the disclosure is not limited in this respect. In examples where compliance badges are implemented, hand hygiene compliance scores may further be determined by employee, employee type, department, shift, facility, or other manner of grouping employees and their associated hand hygiene data.


Using the restroom 140 of FIG. 1 as an example, assume a worker uses urinal 132B, resulting in generation of a toilet/urinal activation event signal by toilet/urinal activation sensor module 150C. Assume for purposes of this example that the system does not make use of compliance badges. The worker then dispenses hand hygiene product using dispenser 120B, resulting in generation of a dispense event signal by dispenser actuation module 100B. To determine whether performance of the hand hygiene procedure at dispenser 120B was compliant (ref. num. 204 of FIG. 5), processor(s) 182 may compare the time stamp for the activation event with the time stamp for the dispense event to determine whether the dispense event occurred within the predetermined period of time from the activation event. Processor(s) 182 would further determine whether the dispenser 120B and/or the dispenser actuation sensor module 100B are associated with urinal 132B and/or toilet/urinal activation sensor module 150C. If both of these are answered in the affirmative, processor(s) 182 would determine that the urinal activation event was followed by a compliant hand hygiene dispense event. However, if the dispense event did not occur at an associated dispenser until after the predetermined period of time had elapsed, or if no dispense event occurred, the urinal activation event would be determined to be non-compliant. Similarly, if a dispense event occurred within the predetermined period of time but it did not occur at one of the dispensers associated with the toilet/urinal, the urinal activation would be determined to be non-compliant.


In another example using the restroom 140 of FIG. 1 as an example, assume a worker 11 wearing or carrying an associated compliance badge 10 uses urinal 132B, resulting in generation of a toilet/urinal activation event signal by toilet/urinal activation sensor module 150C. During and shortly following activation of toilet/urinal 132B, worker 11 is close enough to activation sensor module 150C such that activation sensor module 150C can establish short-range communication with compliance badge 10, and receives the compliance badge identification data from compliance badge 10. The worker then dispenses hand hygiene product using dispenser 120B, resulting in generation of a dispense event signal by dispenser actuation module 100B. During and shortly following actuation of dispenser 120B, worker 11 is close enough to actuation sensor module 100B such that actuation sensor module 100B can establish short-range communication with compliance badge 10, and receives the compliance badge identification data from compliance badge 10. To determine whether performance of the hand hygiene procedure at dispenser 120B was compliant (ref num. 204 of FIG. 5), processor(s) 182 may compare the time stamp for the activation event with the time stamp for the dispense event to determine whether the dispense event occurred within the predetermined period of time from the activation event. Processor(s) 182 would further determine whether the dispenser 120B and/or the dispenser actuation sensor module 100B are associated with urinal 132B and/or toilet/urinal activation sensor module 150C. Processor(s) 182 would further compare the badge identification data associated with the dispense event with the badge identification data associated with the toilet/urinal activation event. If all of these are answered in the affirmative, processor(s) 182 would determine that the urinal activation event was followed by a compliant hand hygiene dispense event (206). However, if the dispense event did not occur at an associated dispenser until after the predetermined period of time had elapsed, or if no dispense event occurred, the toilet/urinal activation event would be determined to be non-compliant (208). Similarly, if a dispense event occurred within the predetermined period of time but it did not occur at one of the dispensers associated with the toilet/urinal, or if the badge identification data did not match, the urinal activation would be determined to be non-compliant (208).



FIG. 6 is a table showing toilet/urinal activation event data and dispense event data for an example individual restroom. Compliance badge data is not shown in this example. The restroom includes a single toilet having a uniquely associated toilet activation sensor denoted by Sensor Number 1 (or simply, Sensor 1). The restroom also includes two urinals having uniquely associated activation sensors denoted by Sensor 2 and Sensor 3. The restroom further includes one hand hygiene product dispenser having a uniquely associated dispenser actuation sensor denoted by Sensor 11. The Device ID indicates whether the device in question is a toilet/urinal, which are denoted in this example by Device ID 100, or a hand hygiene product dispenser, which are denoted in this example by Device ID 2. Different types of hand hygiene product dispensers may be given different Device ID numbers. Likewise, toilets/urinals may be given different Device ID numbers in different examples.


In this case, because the toilet, urinals, and dispenser are in the same restroom, they are associated with each other in the sense that dispense events occurring at dispenser Sensor 11 may result in a compliant hand wash if they occur within the predetermined period of time of activation events detected by any one of sensors Sensor 1, Sensor 2, or Sensor 3. In other words, for example, the Sensor 1, Sensor 2 and Sensor 3 may be associated in memory with Sensor 11 at the remote computing system 180 of FIG. 2, and these associations may be stored in hand hygiene system data 192, which stores the information concerning the number and identification of each fixture (toilet, urinal) and hand hygiene product dispenser in a restroom, department, building, facility and/or corporation, and also stores information concerning which fixtures are associated with each other for purposes of identifying compliant and/or non-compliant hand hygiene opportunities.


The row labeled “Count” includes an absolute count of the total number of activations or actuations that have occurred since the sensor was installed. Thus, for example, in the first row, Sensor 2 has sensed a total of 124 urinal activations since it was installed. In row 2, Sensor 11 has sensed a total of 17,294 dispenser actuations since it was installed. The row labeled “Adjusted Count” may include, for example, the total activations or actuations that have been sensed so far in a particular time period. For example, the Adjusted Count may be reset to zero at midnight (or other defined time) each day, so that the Adjusted Count records the total number of activations/actuations sensed so far that day.


The far-right column indicates whether the toilet/urinal activation event recorded in that row were compliant (Y) or non-compliant (N). For example, the activation event detected at a urinal associated with Sensor 2 recorded in the first row of the table as indicated by reference numeral 220 was determined to be compliant, as indicated by the Y in the far-right column of that row. This is because a compliant dispense event at a hand hygiene product dispenser associated with Sensor 11 occurred at time 2:00:21 PM, which is 15 seconds after the activation event time stamp of 2:00:16 PM, which in this example is within the acceptable predetermined period of time (assuming, for purposes of this example that the predetermined period of time for a compliant dispense event is 3-120 seconds after a urinal activation). Similarly, the activation events recorded in rows indicated by reference numerals 222, 224, and 226 were also followed by compliant dispense events.


The activation event at row 230, which was detected at Sensor 2 at time 2:21:26 PM, is followed by a dispense event detected at Sensor 11 at time 2:24:00 PM. This is 2 minutes and 34 seconds (154 seconds) after the activation event, which is outside the predetermined period of time (assuming, for purposes of this example, that the predetermined period of time for a compliant dispense event is 5-120 seconds after a toilet activation). Thus, the activation event at row 230 is determined to be non-compliant as denoted by the N in the far-right column of row 230.


The activation event at row 232 is not followed by a dispense event within the predetermined period of time, and is therefore non-compliant.


The activation at row 234 which occurred at time 2:38:30 PM is followed by a dispense event 236 occurring at time 2:38:32 PM, and is therefore compliant. It is also followed by another dispense event 238 which occurred at time 2:45:33 PM. This dispense event 238 may be due to someone entering the restroom to wash their hands but who did not use the restroom facilities, and because a compliant dispense event was already identified, may be ignored.


The activations at rows 242 and 244 are both determined to be compliant activation events. The activation event at row 242 has a compliant dispense event recorded in row 246 (a time difference of 104 seconds, which is within the acceptable predetermined time limit of 120 seconds in this example), and the activation event at row 244 has a compliant dispense event recorded in row 248 (a time difference of 26 seconds, which is within the acceptable predetermined time limit of 120 seconds in this example).


The activation event recorded at row 250 is followed by a compliant dispense event recorded at row 252 (a time difference of 6 seconds). Additional dispense events are recorded as indicated by reference numerals 256 and 258; however, because a compliant dispense event was already detected, these are not associated with a detected activation event and may be ignored in this example.


Multiple dispenser actuations may also be observed when a user dispense hand hygiene product more than once per wash. However, as long as a dispense event occurs within the predetermined period of time for each activation event, the remaining dispenser actuations may be ignored for purposes of determining whether a toilet/urinal activation event was followed by a compliant dispense event.



FIG. 7 is an example graph showing toilet/urinal activations and dispenser actuation events detected for a particular restroom in 30-minute intervals over the course of a typical workday (in this case, from about 6:00:00 AM to 6:30:00 PM). Compliance badge data is not shown in FIG. 7. This graph shows a general trend of frequency of use during the observed period, during which higher use and lower use times are visible. Insights from this data could provide recommended times for cleaning a facility without too much disruption to traffic flow.



FIG. 8 is an example graph showing average compliance for each 30-minute interval over the course of a typical work day for the data of FIG. 7. Compliance badge data is not shown in this example. The number compliant or “good” hand hygiene opportunities and the number of non-compliant or “bad” hand hygiene opportunities is also shown for each 30-minute interval. In this example, heavier traffic seemed to result in a dip in compliance, and there is also a drop in compliance at the end of the work day. If the compliance were calculated or averaged over the entire day, the drop in compliance at certain times of day would not be noticed. This data may be used to recommend training sessions for employees that emphasize performance of compliant hand hygiene procedures at certain times of the day to improve compliance at those times of day in the future.


EXAMPLES
Example 1

A system that monitors hand hygiene compliance at a facility, comprising an activation sensor module that senses activation of a toilet/urinal and transmits corresponding activation event data including an activation sensor identifier and a date and time associated with the sensed activation of the toilet/urinal, the activation event data identifying an associated hand hygiene opportunity; a dispenser actuation sensor module that senses actuation of a hand hygiene product dispenser and transmits corresponding dispense event data including a dispenser actuation sensor identifier and a date and time associated with the sensed actuation of the hand hygiene product dispenser; and a computing device that receives the activation event data and the dispense event data and determines whether the hand hygiene opportunity was compliant with one or more hand hygiene compliance rules, the compliance rules including a predetermined period of time within which actuation of the hand hygiene product dispenser must occur subsequent to the sensed activation of the toilet/urinal in order for the computing device to determine that the hand hygiene opportunity is compliant.


Example 2

The system of Example 1, further including a plurality of dispenser actuation sensors, each associated with a different one of a plurality of hand hygiene product dispensers located throughout a facility, the compliance rules further including an association between the activation sensor module and at least one of the plurality of hand hygiene product dispensers, such that actuation of at least one of the associated dispensers must occur within the predetermined period of time subsequent to the sensed activation of the toilet/urinal in order for the computing device to determine that the hand hygiene opportunity is compliant.


Example 3

The system of Example 2, further including a plurality of activation sensor modules, each associated with a different one of a plurality of toilet/urinals.


Example 4

The system of Example 2, wherein the association between the activation sensor module and the at least one of the plurality of hand hygiene product dispensers is based on their installation in the same restroom.


Example 5

The system of Example 1, wherein the remote computing system further includes a reporting application that generates reports concerning hand hygiene compliance at the facility.


Example 6

The system of Example 1, wherein the remote computing system further permits users to remotely request and receive the reports.


Example 7

The system of Example 1, wherein the remote computing system generates a compliance score according to the equation:







%





Hand





Hygiene





Compliance

=


Hand





Hygiene





Opportunities
×
100


Compliant





Hand





Hygiene






Events
.







Example 8

The system of Example 1, wherein the hand hygiene product dispenser dispenses one of a hand soap, a hand sanitizer, a hand rub, or an aqueous solution.


Example 9

The system of Example 1 wherein the hand hygiene product dispenser dispenses one of a liquid, a gel, a lotion, or a foam.


Example 10

The system of Example 1 further comprising a compliance badge including a badge module that stores badge identification data uniquely associated with a user, and that communicates the badge identification data to the toilet/urinal activation sensor upon, wherein the toilet/urinal activation sensor stores the badge identification data as part of the activation event data and the dispenser actuation sensor module stores the badge identification data as part of the dispenser data.


Example 11

The system of Example 10 wherein the compliance rules include a predetermined period of time within which actuation of the hand hygiene product dispenser associated with the badge identification data must occur subsequent to the sensed activation of the toilet/urinal associated with the badge identification data in order for the computing device to determine that the hand hygiene opportunity is compliant.


Example 12

A system that monitors hand hygiene compliance at a facility, comprising an activation sensor module that senses activation of a toilet/urinal and transmits corresponding activation event data including an activation sensor identifier and a date and time associated with the sensed activation of the toilet/urinal, the activation event data identifying an associated hand hygiene opportunity; a dispenser actuation sensor module that senses actuation of a hand hygiene product dispenser and transmits corresponding dispense event data including a dispenser actuation sensor identifier and a date and time associated with the sensed actuation of the hand hygiene product dispenser; and a computing device that receives the activation event data and the dispense event data and determines whether the dispense event occurred within a predetermined period of time of the activation event to determine whether the hand hygiene opportunity was a compliant hand hygiene opportunity.


Example 13

The system of Example 12 wherein the computing device further associates the toilet/urinal with one or more hand hygiene product dispensers based on the toilet/urinal and the one or more hand hygiene product dispensers being located in the same restroom, and further wherein the computing device further determines whether the dispense event occurred at one of the one or more associated hand hygiene product dispensers to determine whether the hand hygiene opportunity was a compliant hand hygiene opportunity.


Example 14

The system of Example 12 wherein the remote computing system generates a compliance score based on the activation event data and the dispense event data.


Example 15

The system of Example 14 wherein the remote computing system generates the compliance score according to the equation:







%





Hand





Hygiene





Compliance

=



Hand





Hygiene





Opportunities
×
100


Compliant





Hand





Hygiene





Events


.





Example 16

The system of Example 12 further comprising a plurality of toilet/urinal activation modules, each uniquely associated with a different one of a plurality of toilet/urinals; a plurality of dispenser actuation modules, each uniquely associated with a different one of a plurality of hand hygiene product dispensers, and the computing device further determines a compliance score based on a plurality of activation events received from the toilet/urinal activation modules and based on a plurality of dispense events received from the dispenser actuation modules.


Example 17

The system of Example 16 wherein the compliance score is determined on a per toilet/urinal basis, a per hand hygiene product dispenser basis, a per restroom basis, a department basis, a facility-wide basis, or a corporate-wide basis.


Example 18

The system of Example 16 wherein the compliance score is determined based on a time period, a workday shift, a day, a week, a month, or a year.


Example 19

The system of Example 12 wherein the predetermined period of time is based at least in part on a distance between the toilet/urinal and the hand hygiene product dispenser.


Example 20

The system of Example 12 wherein the predetermined period of time is based at least in part on dimension of a room in which the toilet/urinal and the hand hygiene dispenser are located.


Example 21

The system of Example 12 wherein the predetermined period of time is based at least in part on a number of hand hygiene product dispensers.


Example 22

The system of Example 12 wherein the predetermined period of time is based at least in part on preferred hand hygiene practices of the facility.


Example 23

A method of monitoring hand hygiene compliance at a facility, comprising sensing activation of a toilet/urinal and transmitting corresponding activation event data including an activation sensor identifier and a date and time associated with the sensed activation of the toilet/urinal, the activation event data identifying an associated hand hygiene opportunity; sensing actuation of a hand hygiene product dispenser and transmitting corresponding dispense event data including a dispenser actuation sensor identifier and a date and time associated with the sensed actuation of the hand hygiene product dispenser; associating, by a computing device, the toilet/urinal with one or more hand hygiene product dispensers based on the toilet/urinal and the one or more hand hygiene product dispensers being located in the same restroom; and determining, the computing device, whether the hand hygiene opportunity was a compliant hand hygiene opportunity, including determining, by the computing device, whether the dispense event occurred within a predetermined period of time of the activation event; and determining, by the computing device, whether the dispense event occurred at one of the one or more associated hand hygiene product dispensers.


Example 24

The method of Example 23 further comprising generating a report concerning hand hygiene compliance at the facility, wherein the report includes a comparison of hand hygiene opportunities and compliant hand hygiene opportunities at the facility over time to determine whether improvement in hand hygiene practices has occurred.


Example 25

The method of Example 23 further comprising generating a report including hand hygiene data at multiple facilities.


Example 26

The method of Example 23 further comprising receiving, by the computing device, first badge identification data that uniquely identifies a first one of a plurality of users from a first compliance badge associated with the activation event; receiving, by the computing device, second badge identification that uniquely identifies a second one of a plurality of users from a second compliance badge associated with the dispense event; comparing, by the computing device, the first badge identification data with the second badge identification data; and determining, by the computing device, whether the hand hygiene opportunity was a compliant hand hygiene opportunity if the first badge identification data matches the second badge identification data.


Various examples have been described. These and other examples are within the scope of the following claims.

Claims
  • 1. A system that monitors hand hygiene compliance at a facility, comprising: an activation sensor module that senses activation of a toilet/urinal and transmits corresponding activation event data including an activation sensor identifier and a date and time associated with the sensed activation of the toilet/urinal, the activation event data identifying an associated hand hygiene opportunity;a dispenser actuation sensor module that senses actuation of a hand hygiene product dispenser and transmits corresponding dispense event data including a dispenser actuation sensor identifier and a date and time associated with the sensed actuation of the hand hygiene product dispenser; anda computing device that receives the activation event data and the dispense event data and determines whether the hand hygiene opportunity was compliant with one or more hand hygiene compliance rules,the compliance rules including a predetermined period of time within which actuation of the hand hygiene product dispenser must occur subsequent to the sensed activation of the toilet/urinal in order for the computing device to determine that the hand hygiene opportunity is compliant.
  • 2. The system of claim 1, further including a plurality of dispenser actuation sensors, each associated with a different one of a plurality of hand hygiene product dispensers located throughout a facility, the compliance rules further including an association between the activation sensor module and at least one of the plurality of hand hygiene product dispensers, such that actuation of at least one of the associated dispensers must occur within the predetermined period of time subsequent to the sensed activation of the toilet/urinal in order for the computing device to determine that the hand hygiene opportunity is compliant.
  • 3. The system of claim 2, further including a plurality of activation sensor modules, each associated with a different one of a plurality of toilet/urinals.
  • 4. The system of claim 2, wherein the association between the activation sensor module and the at least one of the plurality of hand hygiene product dispensers is based on their installation in the same restroom.
  • 5. The system of claim 1, wherein the remote computing system further includes a reporting application that generates reports concerning hand hygiene compliance at the facility.
  • 6. The system of claim 1, wherein the remote computing system further permits users to remotely request and receive the reports.
  • 7. The system of claim 1, wherein the remote computing system generates a compliance score according to the equation:
  • 8. The system of claim 1, wherein the hand hygiene product dispenser dispenses one of a hand soap, a hand sanitizer, a hand rub, or an aqueous solution.
  • 9. The system of claim 1 wherein the hand hygiene product dispenser dispenses one of a liquid, a gel, a lotion, or a foam.
  • 10. The system of claim 1 further comprising: a compliance badge including a badge module that stores badge identification data uniquely associated with a user, and that communicates the badge identification data to the toilet/urinal activation sensor upon,wherein the toilet/urinal activation sensor stores the badge identification data as part of the activation event data and the dispenser actuation sensor module stores the badge identification data as part of the dispenser data.
  • 11. The system of claim 10 wherein the compliance rules include a predetermined period of time within which actuation of the hand hygiene product dispenser associated with the badge identification data must occur subsequent to the sensed activation of the toilet/urinal associated with the badge identification data in order for the computing device to determine that the hand hygiene opportunity is compliant.
  • 12. A system that monitors hand hygiene compliance at a facility, comprising: an activation sensor module that senses activation of a toilet/urinal and transmits corresponding activation event data including an activation sensor identifier and a date and time associated with the sensed activation of the toilet/urinal, the activation event data identifying an associated hand hygiene opportunity;a dispenser actuation sensor module that senses actuation of a hand hygiene product dispenser and transmits corresponding dispense event data including a dispenser actuation sensor identifier and a date and time associated with the sensed actuation of the hand hygiene product dispenser; anda computing device that receives the activation event data and the dispense event data and determines whether the dispense event occurred within a predetermined period of time of the activation event to determine whether the hand hygiene opportunity was a compliant hand hygiene opportunity.
  • 13. The system of claim 12 wherein the computing device further associates the toilet/urinal with one or more hand hygiene product dispensers based on the toilet/urinal and the one or more hand hygiene product dispensers being located in the same restroom, and further wherein the computing device further determines whether the dispense event occurred at one of the one or more associated hand hygiene product dispensers to determine whether the hand hygiene opportunity was a compliant hand hygiene opportunity.
  • 14. The system of claim 12 wherein the remote computing system generates a compliance score based on the activation event data and the dispense event data.
  • 15. The system of claim 14 wherein the remote computing system generates the compliance score according to the equation:
  • 16. The system of claim 12 further comprising: a plurality of toilet/urinal activation modules, each uniquely associated with a different one of a plurality of toilet/urinals;a plurality of dispenser actuation modules, each uniquely associated with a different one of a plurality of hand hygiene product dispensers,and the computing device further determines a compliance score based on a plurality of activation events received from the toilet/urinal activation modules and based on a plurality of dispense events received from the dispenser actuation modules.
  • 17. The system of claim 16 wherein the compliance score is determined on a per toilet/urinal basis, a per hand hygiene product dispenser basis, a per restroom basis, a department basis, a facility-wide basis, or a corporate-wide basis.
  • 18. The system of claim 16 wherein the compliance score is determined based on a time period, a workday shift, a day, a week, a month, or a year.
  • 19. The system of claim 12 wherein the predetermined period of time is based at least in part on a distance between the toilet/urinal and the hand hygiene product dispenser.
  • 20. The system of claim 12 wherein the predetermined period of time is based at least in part on dimension of a room in which the toilet/urinal and the hand hygiene dispenser are located.
  • 21. The system of claim 12 wherein the predetermined period of time is based at least in part on a number of hand hygiene product dispensers.
  • 22. The system of claim 12 wherein the predetermined period of time is based at least in part on preferred hand hygiene practices of the facility.
  • 23. A method of monitoring hand hygiene compliance at a facility, comprising: sensing activation of a toilet/urinal and transmitting corresponding activation event data including an activation sensor identifier and a date and time associated with the sensed activation of the toilet/urinal, the activation event data identifying an associated hand hygiene opportunity;sensing actuation of a hand hygiene product dispenser and transmitting corresponding dispense event data including a dispenser actuation sensor identifier and a date and time associated with the sensed actuation of the hand hygiene product dispenser;associating, by a computing device, the toilet/urinal with one or more hand hygiene product dispensers based on the toilet/urinal and the one or more hand hygiene product dispensers being located in the same restroom; anddetermining, the computing device, whether the hand hygiene opportunity was a compliant hand hygiene opportunity, including: determining, by the computing device, whether the dispense event occurred within a predetermined period of time of the activation event; anddetermining, by the computing device, whether the dispense event occurred at one of the one or more associated hand hygiene product dispensers.
  • 24. The method of claim 23 further comprising generating a report concerning hand hygiene compliance at the facility, wherein the report includes a comparison of hand hygiene opportunities and compliant hand hygiene opportunities at the facility over time to determine whether improvement in hand hygiene practices has occurred.
  • 25. The method of claim 23 further comprising generating a report including hand hygiene data at multiple facilities.
  • 26. The method of claim 23 further comprising: receiving, by the computing device, first badge identification data that uniquely identifies a first one of a plurality of users from a first compliance badge associated with the activation event;receiving, by the computing device, second badge identification that uniquely identifies a second one of a plurality of users from a second compliance badge associated with the dispense event;comparing, by the computing device, the first badge identification data with the second badge identification data; anddetermining, by the computing device, whether the hand hygiene opportunity was a compliant hand hygiene opportunity if the first badge identification data matches the second badge identification data.
US Referenced Citations (758)
Number Name Date Kind
33861 Whitney Dec 1861 A
1643828 Young Sep 1927 A
1985615 Mitchell Dec 1934 A
2219597 Lutz Oct 1940 A
2319739 Kessler May 1943 A
2333791 Hutchinson Nov 1943 A
3091327 Lalley May 1963 A
3136157 Seed et al. Jun 1964 A
3412254 Meyer-Doering et al. Nov 1968 A
3526334 Ashton et al. Sep 1970 A
3578094 Henry et al. May 1971 A
3653544 Young et al. Apr 1972 A
3736584 Hackett et al. May 1973 A
3743598 Field Jul 1973 A
3754871 Hessel et al. Aug 1973 A
3760166 Adams et al. Sep 1973 A
3761909 Schweitzer et al. Sep 1973 A
3772193 Nelli et al. Nov 1973 A
3774056 Sample et al. Nov 1973 A
3786467 Cotter Jan 1974 A
3796349 Weber Mar 1974 A
3801977 Cotter Apr 1974 A
3826113 Boraas et al. Jul 1974 A
3826408 Berndt et al. Jul 1974 A
3866198 Cohen Feb 1975 A
3961321 Moss Jun 1976 A
3986182 Hackett Oct 1976 A
4040515 Hessel et al. Aug 1977 A
4046996 Williams et al. Sep 1977 A
4076146 Lausberg et al. Feb 1978 A
4117462 Miller Sep 1978 A
4083298 Schotten Nov 1978 A
4198618 Kleinschmidt Apr 1980 A
4199001 Kratz Apr 1980 A
4209776 Frederick Jun 1980 A
4211517 Schmid Jul 1980 A
4241400 Keifer Dec 1980 A
4247396 Buseing Jan 1981 A
4265266 Kierbow et al. May 1981 A
4275390 Heywang et al. Jun 1981 A
4319349 Hackett Mar 1982 A
4353482 Tomlinson et al. Oct 1982 A
4360905 Hackett Nov 1982 A
4373418 Rhodes et al. Feb 1983 A
4380726 Sado et al. Apr 1983 A
4396828 Dino et al. Aug 1983 A
4402426 Faulkner et al. Sep 1983 A
4404639 McGuire et al. Sep 1983 A
4463844 Huffman et al. Aug 1984 A
4482785 Finnegan et al. Nov 1984 A
4486910 Saalmann et al. Dec 1984 A
4509543 Livingston et al. Apr 1985 A
4539846 Grossman Sep 1985 A
4573606 Lewis et al. Mar 1986 A
4590460 Abbott et al. May 1986 A
4597091 Blake Jun 1986 A
4606085 Davies Aug 1986 A
4630654 Kennedy, Jr. Dec 1986 A
4644509 Kiewit et al. Feb 1987 A
4676399 Burckhardt Jun 1987 A
4688585 Vetter Aug 1987 A
4690305 Copeland Sep 1987 A
4697243 Moore et al. Sep 1987 A
4707848 Durston et al. Nov 1987 A
4711370 Goudy, Jr. et al. Dec 1987 A
4727522 Steiner et al. Feb 1988 A
4729120 Steiner et al. Mar 1988 A
4733971 Pratt Mar 1988 A
4756321 Livingston et al. Jul 1988 A
4766548 Cedrone et al. Aug 1988 A
4770859 Heiser, Jr. Sep 1988 A
4826661 Copeland et al. May 1989 A
4834546 Putz May 1989 A
4837811 Butler et al. Jun 1989 A
4839597 Rowland Jun 1989 A
4843579 Andrews et al. Jun 1989 A
4845965 Copeland et al. Jul 1989 A
4848381 Livingston et al. Jul 1989 A
4858449 Lehn Aug 1989 A
4867196 Zetena et al. Sep 1989 A
4867343 Ricciardi et al. Sep 1989 A
4896144 Bogstad Jan 1990 A
4908190 Maglio et al. Mar 1990 A
4938240 Lakhan et al. Jul 1990 A
4944428 Gmuer et al. Jul 1990 A
4964185 Lehn Oct 1990 A
4969011 Faull et al. Nov 1990 A
4974646 Martin et al. Dec 1990 A
4976137 Decker et al. Dec 1990 A
4980292 Elbert et al. Dec 1990 A
4987402 Nykerk Jan 1991 A
4991146 Ransdell et al. Feb 1991 A
4999124 Copeland Mar 1991 A
5006995 Toschi et al. Apr 1991 A
5014211 Turner et al. May 1991 A
5014877 Roos May 1991 A
5024352 Gmür et al. Jun 1991 A
5036479 Prednis et al. Jul 1991 A
5038807 Bailey et al. Aug 1991 A
5038973 Gmuer Aug 1991 A
5040699 Gangemi Aug 1991 A
5043860 Koether et al. Aug 1991 A
5053206 Maglio et al. Oct 1991 A
5064094 Roos et al. Nov 1991 A
5083298 Citterio et al. Jan 1992 A
5110364 Mazur et al. May 1992 A
5115842 Crafts et al. May 1992 A
5136281 Bonaquist Aug 1992 A
5147615 Bird et al. Sep 1992 A
5150099 Lienau Sep 1992 A
5153520 Dumbeck Oct 1992 A
5158895 Ashihara et al. Oct 1992 A
5199118 Cole et al. Apr 1993 A
5202666 Knippscheer Apr 1993 A
5203366 Czeck et al. Apr 1993 A
5219224 Pratt Jun 1993 A
5222027 Williams et al. Jun 1993 A
5240326 Evanson Aug 1993 A
5245317 Chidley et al. Sep 1993 A
5263006 Hermesmeyer Nov 1993 A
5268153 Muller Dec 1993 A
5279448 Hanlin et al. Jan 1994 A
5283639 Esch et al. Feb 1994 A
5294022 Earle Mar 1994 A
5309409 Jones et al. May 1994 A
5316195 Moksnes et al. May 1994 A
5322571 Plummer et al. Jun 1994 A
5332312 Evanson Jul 1994 A
5345379 Brous et al. Sep 1994 A
5369032 Pratt Nov 1994 A
5370267 Schroeder Dec 1994 A
5389344 Copeland et al. Feb 1995 A
5390385 Beldham Feb 1995 A
5397028 Jesadanont Mar 1995 A
5400018 Scholl et al. Mar 1995 A
5404893 Brady et al. Apr 1995 A
5407598 Olson et al. Apr 1995 A
5411716 Thomas et al. May 1995 A
5427748 Wiedrich et al. Jun 1995 A
5430293 Sato et al. Jul 1995 A
5463595 Rodhall et al. Oct 1995 A
5467481 Srivastava Nov 1995 A
5476385 Parikh et al. Dec 1995 A
5480068 Frazier et al. Jan 1996 A
5497914 Maltsis Mar 1996 A
5500050 Chan et al. Mar 1996 A
5505915 Copeland et al. Apr 1996 A
5556478 Brady et al. Sep 1996 A
5570079 Dockery Oct 1996 A
5580448 Brandreth Dec 1996 A
5581982 Schroeder et al. Dec 1996 A
5584025 Keithley et al. Dec 1996 A
5584079 Wong et al. Dec 1996 A
5609417 Otte Mar 1997 A
5610589 Evans et al. Mar 1997 A
5619183 Ziegra et al. Apr 1997 A
5625659 Sears Apr 1997 A
5625908 Shaw May 1997 A
5632411 Harty et al. May 1997 A
5636008 Lobiondo et al. Jun 1997 A
5638417 Boyer et al. Jun 1997 A
5653269 Miller et al. Aug 1997 A
5661471 Kotlicki Aug 1997 A
5671262 Boyer et al. Sep 1997 A
5679173 Hartman Oct 1997 A
5681400 Brady et al. Oct 1997 A
5684458 Calvarese Nov 1997 A
5687717 Halpern et al. Nov 1997 A
5694323 Koropitzer et al. Dec 1997 A
5695091 Winings et al. Dec 1997 A
5724261 Denny et al. Mar 1998 A
5731526 Kindrick Mar 1998 A
5735925 Scott Apr 1998 A
5745381 Tanaka et al. Apr 1998 A
5757664 Rogers et al. May 1998 A
5758300 Abe May 1998 A
5759501 Livingston et al. Jun 1998 A
5761278 Pickett et al. Jun 1998 A
5762096 Mirabile Jun 1998 A
5764136 Harron Jun 1998 A
5765605 Waymire et al. Jun 1998 A
5769536 Kotylak Jun 1998 A
5771925 Lewandowski Jun 1998 A
D396009 Reubens Jul 1998 S
5777895 Kuroda et al. Jul 1998 A
5781942 Allen et al. Jul 1998 A
H1743 Graves et al. Aug 1998 H
5793653 Segal Aug 1998 A
5808553 Cunningham Sep 1998 A
5812059 Shaw et al. Sep 1998 A
5821523 Bunte et al. Oct 1998 A
5826749 Howland et al. Oct 1998 A
5827486 Crossdale Oct 1998 A
5839097 Klausner Nov 1998 A
5851291 Poterala et al. Dec 1998 A
5861881 Freeman et al. Jan 1999 A
5864783 Struck et al. Jan 1999 A
5875430 Koether Feb 1999 A
5885446 McGrew, Jr. Mar 1999 A
5887145 Harari et al. Mar 1999 A
5887975 Mordaunt et al. Mar 1999 A
5897671 Newman et al. Apr 1999 A
5900067 Jones May 1999 A
5902749 Lichtwardt et al. May 1999 A
5913915 McQuinn Jun 1999 A
5917425 Crimmins et al. Jun 1999 A
5919567 Okada et al. Jul 1999 A
5931877 Smith et al. Aug 1999 A
5933479 Michael et al. Aug 1999 A
5938074 Dartus Aug 1999 A
5939974 Heagle et al. Aug 1999 A
5945910 Gorra Aug 1999 A
5952924 Evans et al. Sep 1999 A
5954069 Foster Sep 1999 A
5956487 Venkatraman et al. Sep 1999 A
5979703 Nystrom Sep 1999 A
5961561 Wakefield, II Oct 1999 A
5966753 Gauthier et al. Oct 1999 A
5967202 Mullen et al. Oct 1999 A
5973696 Agranat et al. Oct 1999 A
5974345 Buck et al. Oct 1999 A
5975352 Spriggs et al. Nov 1999 A
5977913 Christ Nov 1999 A
5980090 Royal et al. Nov 1999 A
5987105 Jenkins et al. Nov 1999 A
5992686 Cline et al. Nov 1999 A
6003070 Frantz Dec 1999 A
6007788 Bellon et al. Dec 1999 A
6012041 Brewer et al. Jan 2000 A
6029286 Funk Feb 2000 A
6031461 Lynn Feb 2000 A
6038331 Johnson Mar 2000 A
6049792 Hart et al. Apr 2000 A
6061668 Sharrow May 2000 A
6065639 Maddox et al. May 2000 A
6073124 Krishnan et al. Jun 2000 A
6082149 Woods Jul 2000 A
6098843 Soberanis et al. Aug 2000 A
6120175 Tewell Sep 2000 A
6125482 Foster Oct 2000 A
6129449 McCain et al. Oct 2000 A
6130607 McClanahan et al. Oct 2000 A
6133555 Brenn Oct 2000 A
6136184 King Oct 2000 A
6147607 Lynn Nov 2000 A
6164189 Anson Dec 2000 A
6167358 Othmer et al. Dec 2000 A
6175308 Tallman et al. Jan 2001 B1
6191693 Sangsingkeow Feb 2001 B1
6211788 Lynn et al. Apr 2001 B1
6213424 Helfer-Grand Apr 2001 B1
6220312 Hirsch et al. Apr 2001 B1
6221788 Kobayashi et al. Apr 2001 B1
6236317 Cohen et al. May 2001 B1
6236953 Segal May 2001 B1
6249778 Vaghi Jun 2001 B1
6259956 Myers et al. Jul 2001 B1
6269975 Soberanis et al. Aug 2001 B2
6278372 Velasco, Jr. et al. Aug 2001 B1
6279777 Goodin et al. Aug 2001 B1
6288641 Casais Sep 2001 B1
6314282 Weber et al. Nov 2001 B1
6321204 Kazami et al. Nov 2001 B1
6330499 Chou et al. Dec 2001 B1
6331964 Barone Dec 2001 B1
6347724 Chen et al. Feb 2002 B1
6351223 DeWeerd et al. Feb 2002 B1
6356205 Salvo et al. Mar 2002 B1
6357292 Schultz et al. Mar 2002 B1
6360181 Gemmell et al. Mar 2002 B1
6368420 Angevaare et al. Apr 2002 B1
6370454 Moore Apr 2002 B1
6375038 Daansen et al. Apr 2002 B1
6377868 Gardner, Jr. Apr 2002 B1
6392546 Smith May 2002 B1
6404837 Thompson et al. Jun 2002 B1
6417773 Vlahos et al. Jul 2002 B1
6418371 Arnold Jul 2002 B1
6426701 Levy et al. Jul 2002 B1
6438471 Katagishi et al. Aug 2002 B1
6463940 Thomas et al. Oct 2002 B1
6472615 Carlson Oct 2002 B1
6476385 Albert Nov 2002 B1
6485979 Kippenhan et al. Nov 2002 B1
6490513 Fish et al. Dec 2002 B1
6523193 Saraya Feb 2003 B2
6524390 Jones Feb 2003 B1
6547097 Cavallaro et al. Apr 2003 B1
6561381 Osterheld et al. May 2003 B1
6577240 Armstrong Jun 2003 B2
6611207 Yuan et al. Aug 2003 B1
6681003 Linder et al. Jan 2004 B2
6697706 Gardner, Jr. Feb 2004 B2
6707873 Thompson et al. Mar 2004 B2
6727818 Wildman et al. Apr 2004 B1
6730024 Freyre et al. May 2004 B2
6749148 Helfer-Grand Jun 2004 B2
6759959 Wildman Jul 2004 B2
6778092 Braune Aug 2004 B2
6781523 Matsui et al. Aug 2004 B2
6792395 Roberts Sep 2004 B2
6799085 Crisp, III Sep 2004 B1
6807460 Black et al. Oct 2004 B2
6882278 Winings et al. Apr 2005 B2
6882315 Richley et al. Apr 2005 B2
6883563 Smith Apr 2005 B2
6893321 Buchanan et al. May 2005 B1
6896140 Perry May 2005 B1
6897780 Ulrich et al. May 2005 B2
6917290 Land Jul 2005 B2
6919567 Iwasawa Jul 2005 B2
6921000 Wagner et al. Jul 2005 B2
6950683 Hunt Sep 2005 B2
6956498 Gauthier et al. Oct 2005 B1
6975231 Lane et al. Dec 2005 B2
6977588 Schotz et al. Dec 2005 B2
6987228 MacMichael et al. Jan 2006 B1
7015816 Wildman et al. Mar 2006 B2
7023341 Stilp Apr 2006 B2
7023356 Burkhardt et al. Apr 2006 B2
7042361 Kazdin et al. May 2006 B2
7056050 Sacks Jun 2006 B2
7067054 Fritze Jun 2006 B2
7069188 Roberts Jun 2006 B2
7075412 Reynolds et al. Jul 2006 B1
7099781 Heidl et al. Aug 2006 B1
7099856 Barangan et al. Aug 2006 B2
7117374 Hill et al. Oct 2006 B2
7119688 Wildman Oct 2006 B2
7119692 Lieffort et al. Oct 2006 B2
7128215 Danechi Oct 2006 B2
7142108 Diener et al. Nov 2006 B2
7154397 Zerhusen et al. Dec 2006 B2
7157045 McVey Jan 2007 B2
7160846 Biering et al. Jan 2007 B2
7175048 Wolfschaffner Feb 2007 B2
7187287 Ryal Mar 2007 B2
7191090 Cunningham Mar 2007 B1
7201005 Voglewede et al. Apr 2007 B2
7201290 Mehus et al. Apr 2007 B2
7202780 Teller Apr 2007 B2
7228990 Schmidt Jun 2007 B2
7236097 Cunningham Jun 2007 B1
7242306 Wildman et al. Jul 2007 B2
7242307 LeBlond et al. Jul 2007 B1
7248933 Wildman Jul 2007 B2
7265673 Teller Sep 2007 B2
7266347 Gross Sep 2007 B2
7267531 Anderson et al. Sep 2007 B2
7271728 Taylor et al. Sep 2007 B2
7272537 Mogadam Sep 2007 B2
7286057 Bolling Oct 2007 B2
7292914 Jungmann et al. Nov 2007 B2
7293645 Harper et al. Nov 2007 B2
7315245 Lynn et al. Jan 2008 B2
7320418 Sassoon Jan 2008 B2
7330108 Thomas Feb 2008 B2
7372367 Lane et al. May 2008 B2
7375640 Plost May 2008 B1
7400264 Boaz Jul 2008 B2
7408470 Wildman et al. Aug 2008 B2
7410290 Tanaka Aug 2008 B2
7411511 Kennish et al. Aug 2008 B2
7423533 LeBlond et al. Sep 2008 B1
7425900 Lynn et al. Sep 2008 B2
7440620 Aartsen Oct 2008 B1
7443302 Reeder et al. Oct 2008 B2
7443305 Verdiramo Oct 2008 B2
RE40588 Ostendorf et al. Nov 2008 E
7450472 Guyvarch Nov 2008 B2
7457869 Kernan Nov 2008 B2
7474215 Scott et al. Jan 2009 B2
7477148 Lynn et al. Jan 2009 B2
7482936 Bolling Jan 2009 B2
7486193 Elwell Feb 2009 B2
7487538 Mok Feb 2009 B2
7490045 Flores et al. Feb 2009 B1
7496479 Garcia et al. Feb 2009 B2
7530729 O'Callaghan May 2009 B2
7538680 Scott et al. May 2009 B2
7551092 Henry Jun 2009 B1
7597122 Smith Oct 2009 B1
7600137 Trappeniers et al. Oct 2009 B2
7605704 Munro et al. Oct 2009 B2
7611030 Reynolds et al. Nov 2009 B2
7616122 Bolling Nov 2009 B2
7682464 Glenn et al. Mar 2010 B2
7718395 Carling May 2010 B2
7755494 Melker et al. Jul 2010 B2
7770782 Sahud Aug 2010 B2
7780453 Carling Aug 2010 B2
7783380 York et al. Aug 2010 B2
7785109 Carling Aug 2010 B2
7812730 Wildman et al. Oct 2010 B2
7855651 LeBlond et al. Dec 2010 B2
7891523 Mehus et al. Feb 2011 B2
7893842 Deutsch Feb 2011 B2
7898407 Hufton et al. Mar 2011 B2
7952484 Lynn May 2011 B2
7978564 De La Huerga Jul 2011 B2
7982619 Bolling Jul 2011 B2
8020733 Snodgrass Sep 2011 B2
8026821 Reeder et al. Sep 2011 B2
8040245 Koblasz Oct 2011 B2
8045498 Hyland Oct 2011 B2
8056768 Snodgrass Nov 2011 B2
8085155 Prodanovich et al. Dec 2011 B2
D654743 Rospierski Feb 2012 S
8146613 Barnhill et al. Apr 2012 B2
8152027 Baker Apr 2012 B1
8154412 Verdiramo Apr 2012 B2
8196810 Sahud Jun 2012 B2
8212653 Goldstein et al. Jul 2012 B1
8237558 Momen et al. Aug 2012 B2
8240517 Stob et al. Aug 2012 B1
8249295 Johnson Aug 2012 B2
8258965 Reeder et al. Sep 2012 B2
8264343 Snodgrass Sep 2012 B2
8279063 Wohltjen Oct 2012 B2
8294585 Barnhill Oct 2012 B2
8342365 Snodgrass Jan 2013 B2
8344893 Drammeh Jan 2013 B1
8350706 Wegelin et al. Jan 2013 B2
8368544 Wildman et al. Feb 2013 B2
8372207 Shields Feb 2013 B1
8395515 Tokhtuev Mar 2013 B2
8400309 Glenn et al. Mar 2013 B2
8427323 Alper et al. Apr 2013 B2
8482406 Snodgrass Jul 2013 B2
8502680 Tokhtuev et al. Aug 2013 B2
8502681 Bolling et al. Aug 2013 B2
8511512 Carlson et al. Aug 2013 B2
8525666 Melker et al. Sep 2013 B2
8558660 Nix et al. Oct 2013 B2
8558701 Wegelin et al. Oct 2013 B2
8564431 Snodgrass Oct 2013 B2
D693140 Rospierski Nov 2013 S
8587437 Kyle et al. Nov 2013 B2
8598996 Wildman et al. Dec 2013 B2
8633806 Amir Jan 2014 B2
8633816 Snodgrass et al. Jan 2014 B2
8639527 Rensvold et al. Jan 2014 B2
8646656 Johnson Feb 2014 B2
8648724 Forsberg et al. Feb 2014 B2
8668145 Tessier Mar 2014 B2
8674840 Snodgrass Mar 2014 B2
8698637 Raichman Apr 2014 B2
8776817 Sawaski et al. Jul 2014 B2
8783511 Snodgrass Jul 2014 B2
8786429 Li et al. Jul 2014 B2
8816860 Ophardt et al. Aug 2014 B2
8823525 Cartner et al. Sep 2014 B2
8842406 Tseng et al. Sep 2014 B2
8847752 Wegelin et al. Sep 2014 B2
8872665 Snodgrass Oct 2014 B2
8903416 Perkins et al. Dec 2014 B1
8963721 Harris et al. Feb 2015 B2
8963723 Snodgrass Feb 2015 B2
8976031 Ophardt Mar 2015 B2
8988228 Iseri et al. Mar 2015 B2
8990098 Swart et al. Mar 2015 B2
8994537 Pokrajac Mar 2015 B2
8999261 Benedtto Apr 2015 B2
9000930 Pelland et al. Apr 2015 B2
9047755 Bonner Jun 2015 B2
9076044 Dryer et al. Jul 2015 B2
9111435 Gips et al. Aug 2015 B2
9117361 Hennigan et al. Aug 2015 B1
9123233 Hermann Sep 2015 B2
9159216 Limbert et al. Oct 2015 B2
9218734 Wallace et al. Dec 2015 B2
9235977 Deutsch Jan 2016 B2
9239361 Long Jan 2016 B2
9262905 Wegelin et al. Feb 2016 B2
9271611 Stratman Mar 2016 B2
9271612 Miller Mar 2016 B2
9311809 Diaz Apr 2016 B2
9317817 Barsky Apr 2016 B2
9328490 Bayley et al. May 2016 B2
9349274 Wegelin et al. May 2016 B2
9373242 Conrad et al. Jun 2016 B1
9437103 Ophardt Sep 2016 B2
9472089 Alhazme Oct 2016 B2
9478118 Keown et al. Oct 2016 B2
9497428 Gaisser et al. Nov 2016 B2
9524480 Christensen Dec 2016 B2
9524632 Moore Dec 2016 B2
9526380 Hamilton et al. Dec 2016 B2
9536415 De Luca et al. Jan 2017 B2
9633543 Wegelin et al. Apr 2017 B2
9633544 Wegelin et al. Apr 2017 B2
9633545 Wegelin et al. Apr 2017 B2
9640059 Hyland May 2017 B2
9824569 Snodgrass Nov 2017 B2
9881485 Hajdenberg Jan 2018 B2
20010023841 Zimmerman et al. Sep 2001 A1
20010028308 De La Huerga Oct 2001 A1
20010039501 Crevel et al. Nov 2001 A1
20010047214 Cocking et al. Nov 2001 A1
20010053939 Crevel et al. Dec 2001 A1
20010054038 Crevel et al. Dec 2001 A1
20020000449 Armstrong Jan 2002 A1
20020014496 Cline et al. Feb 2002 A1
20020019709 Segal Feb 2002 A1
20020050006 Saraya May 2002 A1
20020096537 Gardner, Jr. Jul 2002 A1
20020103671 Pederson et al. Aug 2002 A1
20020107744 Rosenberg et al. Aug 2002 A1
20020132343 Lum Sep 2002 A1
20020135486 Brohagen et al. Sep 2002 A1
20020145523 Robaey Oct 2002 A1
20020168216 Policicchio et al. Nov 2002 A1
20020175182 Matthews Nov 2002 A1
20020183979 Wildman Dec 2002 A1
20030030562 Lane et al. Feb 2003 A1
20030033396 McCall Feb 2003 A1
20030043688 Peterson et al. Mar 2003 A1
20030065536 Hansen et al. Apr 2003 A1
20030074222 Rosow et al. Apr 2003 A1
20030109057 DiCesare et al. Jun 2003 A1
20030121561 Wagner et al. Jul 2003 A1
20030155035 Ichikawa et al. Aug 2003 A1
20030182180 Zarrow Sep 2003 A1
20040001009 Winings et al. Jan 2004 A1
20040015269 Jungmann et al. Jan 2004 A1
20040028608 Saul et al. Feb 2004 A1
20040049369 Konicek et al. Mar 2004 A1
20040075347 Biskup, Sr. et al. Apr 2004 A1
20040088076 Gardner, Jr. May 2004 A1
20040090333 Wildman et al. May 2004 A1
20040148196 Kalies Jul 2004 A1
20040150527 Harper et al. Aug 2004 A1
20040162850 Sanville et al. Aug 2004 A1
20040220844 Sanville et al. Nov 2004 A1
20040226956 Brooks Nov 2004 A1
20040226959 Mehus et al. Nov 2004 A1
20040230339 Maser et al. Nov 2004 A1
20050065644 Gardner, Jr. et al. Mar 2005 A1
20050072793 Mehus et al. Apr 2005 A1
20050086341 Enga et al. Apr 2005 A1
20050102059 Gardner et al. May 2005 A1
20050102167 Kapoor May 2005 A1
20050134465 Rice et al. Jun 2005 A1
20050134466 Tirkel Jun 2005 A1
20050149341 Eguchi et al. Jul 2005 A1
20050171634 York et al. Aug 2005 A1
20050222889 Lai et al. Oct 2005 A1
20050248461 Lane et al. Nov 2005 A1
20060067545 Lewis et al. Mar 2006 A1
20060067546 Lewis et al. Mar 2006 A1
20060071799 Verdiramo Apr 2006 A1
20060104245 Narayanaswami et al. May 2006 A1
20060132316 Wildman et al. Jun 2006 A1
20060139449 Cheng et al. Jun 2006 A1
20060140703 Sacks Jun 2006 A1
20060154642 Scannell, Jr. Jul 2006 A1
20060156415 Rubinstein et al. Jul 2006 A1
20060191068 Vlahos et al. Aug 2006 A1
20060223731 Carling Oct 2006 A1
20060229821 Brossette et al. Oct 2006 A1
20060240397 Lynn et al. Oct 2006 A1
20060272361 Snodgrass Dec 2006 A1
20060273915 Snodgrass Dec 2006 A1
20060277065 Guten et al. Dec 2006 A1
20070008146 Taylor et al. Jan 2007 A1
20070008147 Bolling Jan 2007 A1
20070008149 Bolling Jan 2007 A1
20070016466 Taylor Jan 2007 A1
20070020212 Bernal et al. Jan 2007 A1
20070029962 Saeki Feb 2007 A1
20070044819 Chan et al. Mar 2007 A1
20070055483 Lee et al. Mar 2007 A1
20070056091 Bolton et al. Mar 2007 A1
20070069884 Waxman Mar 2007 A1
20070096930 Cardoso May 2007 A1
20070135866 Baker et al. Jun 2007 A1
20070182581 Elwell Aug 2007 A1
20070198067 Van den Heuvel et al. Aug 2007 A1
20070205861 Nair et al. Sep 2007 A1
20070213877 Hart et al. Sep 2007 A1
20070222599 Coveley et al. Sep 2007 A1
20070229288 Ogrin et al. Oct 2007 A1
20070247316 Wildman et al. Oct 2007 A1
20070257803 Munro et al. Nov 2007 A1
20070285277 Scott et al. Dec 2007 A1
20070290865 Lynn et al. Dec 2007 A1
20080001763 Raja et al. Jan 2008 A1
20080019489 Lynn Jan 2008 A1
20080019490 Lynn Jan 2008 A1
20080046278 Sanville et al. Feb 2008 A1
20080084315 Pittz Apr 2008 A1
20080087719 Sahud Apr 2008 A1
20080095677 McSherry et al. Apr 2008 A1
20080100441 Prodanovich et al. May 2008 A1
20080103636 Glenn et al. May 2008 A1
20080131332 Nguyen et al. Jun 2008 A1
20080136649 Van De Hey Jun 2008 A1
20080177155 Hansen et al. Jul 2008 A1
20080185540 Turner et al. Aug 2008 A1
20080189142 Brown et al. Aug 2008 A1
20080193631 Kanamori et al. Aug 2008 A1
20080246599 Hufton et al. Oct 2008 A1
20080262097 Eady et al. Oct 2008 A1
20080266113 Kennish et al. Oct 2008 A1
20080267408 Hsieh Oct 2008 A1
20080271928 Mehus et al. Nov 2008 A1
20080280380 Dietz et al. Nov 2008 A1
20080283145 Maxwell Nov 2008 A1
20080290112 Lynn Nov 2008 A1
20080303658 Melker et al. Dec 2008 A1
20090002644 Christensen et al. Jan 2009 A1
20090019552 McLaughlin et al. Jan 2009 A1
20090030721 Garcia et al. Jan 2009 A1
20090037026 Sostaric et al. Feb 2009 A1
20090049610 Heimbrock et al. Feb 2009 A1
20090051545 Koblasz Feb 2009 A1
20090068116 Arndt Mar 2009 A1
20090084407 Glenn et al. Apr 2009 A1
20090090564 Kresina Apr 2009 A1
20090091458 Deutsch Apr 2009 A1
20090102681 Brennan, Jr. et al. Apr 2009 A1
20090112360 Berg Apr 2009 A1
20090112541 Anderson et al. Apr 2009 A1
20090112630 Collins, Jr. et al. Apr 2009 A1
20090119142 Yenni et al. May 2009 A1
20090125424 Wegelin May 2009 A1
20090127282 Reynolds et al. May 2009 A1
20090138303 Seshadri May 2009 A1
20090145925 Wegelin Jun 2009 A1
20090148342 Bromberg et al. Jun 2009 A1
20090171502 Freidin Jul 2009 A1
20090195385 Huang et al. Aug 2009 A1
20090204256 Wegelin Aug 2009 A1
20090219131 Barnett Sep 2009 A1
20090219172 Wilbrod Sep 2009 A1
20090224907 Sinha et al. Sep 2009 A1
20090224924 Thorp Sep 2009 A1
20090266842 Snodgrass Oct 2009 A1
20090267776 Glenn et al. Oct 2009 A1
20090272405 Barnhill et al. Nov 2009 A1
20090273477 Barnhill Nov 2009 A1
20090276239 Swart et al. Nov 2009 A1
20090294469 Poulain et al. Dec 2009 A1
20090299787 Barnhill Dec 2009 A1
20090301523 Barnhill et al. Dec 2009 A1
20100084486 Kim Apr 2010 A1
20100094581 Cagle Apr 2010 A1
20100097224 Prodanovich et al. Apr 2010 A1
20100117823 Wholtjen May 2010 A1
20100117836 Seyed Momen May 2010 A1
20100134296 Hwang Jun 2010 A1
20100153374 LeBlond et al. Jun 2010 A1
20100173581 Dolan Jul 2010 A1
20100188228 Hyland Jul 2010 A1
20100233020 Klaassen et al. Sep 2010 A1
20100238021 Harris Sep 2010 A1
20100274640 Morey et al. Oct 2010 A1
20100315243 Tokhtuev et al. Dec 2010 A1
20100315244 Tokhtuev et al. Dec 2010 A1
20100328076 Kyle et al. Dec 2010 A1
20100332022 Wegelin et al. Dec 2010 A1
20110063106 Snodgrass Mar 2011 A1
20110088809 Lin Apr 2011 A1
20110093313 LeBlond et al. Apr 2011 A1
20110291841 Hollock et al. Apr 2011 A1
20110121974 Tenarvitz et al. May 2011 A1
20110169645 Cartner et al. Jul 2011 A1
20110169646 Raichman Jul 2011 A1
20110193703 Payton et al. Aug 2011 A1
20110196720 Guten et al. Aug 2011 A1
20110234598 Scarola et al. Sep 2011 A1
20110260872 Kennish et al. Oct 2011 A1
20110273298 Snodgrass et al. Nov 2011 A1
20110296664 Minard et al. Dec 2011 A1
20110316695 Li et al. Dec 2011 A1
20110316701 Alper et al. Dec 2011 A1
20110316703 Butler et al. Dec 2011 A1
20120024890 Ota et al. Feb 2012 A1
20120047988 Mehus et al. Mar 2012 A1
20120062382 Taneff Mar 2012 A1
20120112906 Borke et al. May 2012 A1
20120112914 Wegelin et al. May 2012 A1
20120168459 D'Onofrio Jul 2012 A1
20120212344 Forsberg Aug 2012 A1
20120245729 Wegelin et al. Sep 2012 A1
20120256742 Snodgrass et al. Oct 2012 A1
20120310664 Long et al. Dec 2012 A1
20120329438 Snodgrass Dec 2012 A1
20130045685 Kiani Feb 2013 A1
20130075346 Rumberger et al. Mar 2013 A1
20130076514 Wegelin et al. Mar 2013 A1
20130091631 Hayes et al. Apr 2013 A1
20130099900 Pulvermacher Apr 2013 A1
20130113931 Alper May 2013 A1
20130120120 Long et al. May 2013 A1
20130133762 Snodgrass May 2013 A1
20130224076 Hansmann et al. Aug 2013 A1
20130229276 Hunter Sep 2013 A1
20130234855 Knighton Sep 2013 A1
20130257615 Iseri et al. Oct 2013 A1
20130261795 Long et al. Oct 2013 A1
20130264355 Jodoin Oct 2013 A1
20130285814 Snodgrass Oct 2013 A1
20130290016 Alper et al. Oct 2013 A1
20130292407 Beavis et al. Nov 2013 A1
20130306105 Battah Nov 2013 A1
20130332184 Burnham et al. Dec 2013 A1
20130333184 Couture et al. Dec 2013 A1
20130342349 Cruz Dec 2013 A1
20140009292 Long et al. Jan 2014 A1
20140015670 Wegelin et al. Jan 2014 A1
20140070950 Snodgrass Mar 2014 A1
20140081653 Davis et al. Mar 2014 A1
20140108039 Rensvold et al. Apr 2014 A1
20140180713 Tenarvitz et al. Jun 2014 A1
20140210620 Snodgrass Jul 2014 A1
20140214449 Long et al. Jul 2014 A1
20140231455 Jersey et al. Aug 2014 A1
20140242562 McSterling et al. Aug 2014 A1
20140253334 Hanlin et al. Sep 2014 A1
20140279603 Ortiz et al. Sep 2014 A1
20140320289 Raichman Oct 2014 A1
20140327545 Bolling et al. Nov 2014 A1
20140333433 Li et al. Nov 2014 A1
20140347185 Smith et al. Nov 2014 A1
20140361898 Wegelin et al. Dec 2014 A1
20140366264 Ciavarella et al. Dec 2014 A1
20140368320 Hyland Dec 2014 A1
20150022361 Gaisser et al. Jan 2015 A1
20150035678 Long Feb 2015 A1
20150048940 Keown et al. Feb 2015 A1
20150070174 Douglas Mar 2015 A1
20150101121 Burgo Sr., et al. Apr 2015 A1
20150127365 Rizvi et al. May 2015 A1
20150134354 Alper et al. May 2015 A1
20150134357 Davis et al. May 2015 A1
20150179047 Wallace et al. Jun 2015 A1
20150194043 Dunn et al. Jul 2015 A1
20150199883 Hartley et al. Jul 2015 A1
20150221208 Knighton et al. Aug 2015 A1
20150278456 Bermudez Rodriguez et al. Oct 2015 A1
20150308149 Oshymansky et al. Oct 2015 A1
20150313422 Ophardt et al. Nov 2015 A1
20150366411 Yang et al. Dec 2015 A1
20160042635 Rosebraugh et al. Feb 2016 A1
20160068383 Falco, III Mar 2016 A1
20160093195 Ophardt Mar 2016 A1
20160128520 Wegelin et al. May 2016 A1
20160140830 Hathorn May 2016 A1
20160174022 Nhu Jun 2016 A1
20160179089 Stratmann Jun 2016 A1
20160240070 Wegelin et al. Aug 2016 A1
20160249774 Ophardt et al. Sep 2016 A1
20160267772 Iseri et al. Sep 2016 A1
20160292992 Ortiz et al. Oct 2016 A1
20170004287 O'Toole Jan 2017 A1
20170098366 Hood et al. Apr 2017 A1
20180255981 Rospierski Sep 2018 A1
Foreign Referenced Citations (192)
Number Date Country
200114943 May 2001 AU
2012360763 Jul 2013 AU
2015202637 Jun 2015 AU
2015258158 Dec 2015 AU
2015275337 Jan 2016 AU
2013378514 Nov 2017 AU
102012030486 Sep 2014 BR
2605412 Dec 2006 CA
2592814 Dec 2007 CA
2674654 Oct 2009 CA
2776280 Nov 2013 CA
2780411 Dec 2013 CA
2807337 Aug 2014 CA
2914864 Jun 2016 CA
2354482 Dec 1999 CN
1181415 Dec 2004 CN
100340935 Oct 2007 CN
101592510 Dec 2009 CN
201974318 Sep 2011 CN
202677403 Jan 2013 CN
103169409 Jun 2013 CN
103198628 Jul 2013 CN
203153706 Aug 2013 CN
203325033 Dec 2013 CN
103617349 Mar 2014 CN
204218783 Mar 2015 CN
104615091 May 2015 CN
104622348 May 2015 CN
204520455 Aug 2015 CN
105139320 Dec 2015 CN
105164737 Dec 2015 CN
204990347 Jan 2016 CN
101911108 Feb 2016 CN
205197874 May 2016 CN
106154902 Nov 2016 CN
69708606 Aug 2002 DE
10157975 Jun 2003 DE
69917795 Jul 2005 DE
19882120 Oct 2010 DE
102012105365 Dec 2013 DE
2015665 Nov 2009 DK
0921506 Jun 1999 EP
0927535 Jul 1999 EP
0940110 Sep 1999 EP
1121500 Oct 1999 EP
1245016 Oct 2000 EP
1049998 Nov 2000 EP
1099400 May 2001 EP
1201172 May 2002 EP
1390204 Dec 2004 EP
1034132 Aug 2005 EP
1483728 Oct 2006 EP
1791077 May 2007 EP
1794727 Jun 2007 EP
1872802 Jan 2008 EP
1872892 Jan 2008 EP
1874264 Jan 2008 EP
1913892 Apr 2008 EP
2012277 Jan 2009 EP
2223642 Sep 2010 EP
2511889 Oct 2010 EP
2395490 Dec 2011 EP
2509017 Oct 2012 EP
2637540 Sep 2013 EP
2860716 Apr 2015 EP
2956918 Dec 2015 EP
3153984 Apr 2017 EP
2872315 Dec 2005 FR
2997779 May 2014 FR
2052251 May 1980 GB
2137749 Oct 1984 GB
2217013 Oct 1989 GB
2299405 Feb 1996 GB
2298851 Sep 1996 GB
2324397 Oct 1998 GB
2337327 Nov 1999 GB
2340647 Feb 2000 GB
2394654 May 2004 GB
2417810 Mar 2006 GB
2417811 Mar 2006 GB
2425388 Oct 2006 GB
2446871 Aug 2007 GB
2436793 Oct 2007 GB
2437555 Oct 2007 GB
2439306 Dec 2007 GB
2439457 Dec 2007 GB
2452189 Feb 2009 GB
2457930 Sep 2009 GB
2458118 Sep 2009 GB
2469482 Oct 2010 GB
2474317 Apr 2011 GB
2486767 Jun 2012 GB
2537179 Oct 2016 GB
H01219439 Sep 1989 JP
10309540 Nov 1998 JP
11332961 Dec 1999 JP
2001292918 Oct 2001 JP
3281375 May 2002 JP
2002197559 Jul 2002 JP
2003105819 Apr 2003 JP
2003122823 Apr 2003 JP
2006132277 May 2005 JP
2005218999 Aug 2005 JP
2006198318 Aug 2006 JP
2008027436 Feb 2008 JP
2009282442 Dec 2009 JP
4523219 Aug 2010 JP
2013017631 Jan 2013 JP
2013180046 Sep 2013 JP
2013187557 Sep 2013 JP
2015153084 Aug 2015 JP
2015230207 Dec 2015 JP
2016520883 Jul 2016 JP
101632716 Jun 2016 KR
101647831 Aug 2016 KR
2012015244 Apr 2013 MX
882280 May 2002 PT
186323 Jan 2013 SG
WO9213327 Aug 1992 WO
WO9731350 Aug 1997 WO
WO199809261 Mar 1998 WO
WO1998036258 Aug 1998 WO
WO9930299 Jun 1999 WO
WO9933008 Jul 1999 WO
WO200022260 Apr 2000 WO
WO 0125730 Apr 2001 WO
WO2001033529 May 2001 WO
WO0131532 May 2001 WO
WO2010141612 Jun 2001 WO
WO2002021475 Mar 2002 WO
WO2002059701 Aug 2002 WO
WO02077927 Oct 2002 WO
WO2002094073 Nov 2002 WO
WO2005055793 Jun 2003 WO
WO0359143 Jul 2003 WO
WO2003079278 Sep 2003 WO
WO2003082351 Oct 2003 WO
WO 2004052162 Jun 2004 WO
WO 2005040984 May 2005 WO
WO2005055793 Jun 2005 WO
WO2005094711 Oct 2005 WO
WO2005117672 Dec 2005 WO
WO2006036687 Apr 2006 WO
WO 2006036227 Apr 2006 WO
WO 2006100495 Sep 2006 WO
WO2006135922 Dec 2006 WO
WO2007001866 Jan 2007 WO
WO2007090470 Aug 2007 WO
WO 2007127495 Nov 2007 WO
WO2007129289 Nov 2007 WO
WO2007133960 Nov 2007 WO
WO2008088424 Jul 2008 WO
WO 2008118143 Oct 2008 WO
WO2008133495 Nov 2008 WO
WO 2009087046 Jul 2009 WO
WO 2009097096 Aug 2009 WO
WO2009097096 Aug 2009 WO
WO2010026581 Mar 2010 WO
WO2010101929 Sep 2010 WO
WO 2011038173 Mar 2011 WO
WO 2011085292 Jul 2011 WO
WO 2011131800 Oct 2011 WO
WO 2011161475 Dec 2011 WO
WO2012064515 May 2012 WO
WO2012125320 Nov 2012 WO
WO 2012152495 Nov 2012 WO
WO 2012161766 Nov 2012 WO
WO2013025889 Feb 2013 WO
WO2013025956 Feb 2013 WO
WO 2013033243 Mar 2013 WO
WO2013049357 Apr 2013 WO
WO 2013049462 Apr 2013 WO
WO 2013055616 Apr 2013 WO
WO 2013058821 Apr 2013 WO
WO 2013063690 May 2013 WO
WO 2013070888 May 2013 WO
WO 2013074660 May 2013 WO
WO 2013140253 Sep 2013 WO
WO 2013165585 Nov 2013 WO
WO 2013190016 Dec 2013 WO
WO 2014027030 Feb 2014 WO
WO2014037938 Mar 2014 WO
WO2014046645 Mar 2014 WO
WO 2014035610 Mar 2014 WO
WO 2014060726 Apr 2014 WO
WO2014125320 Aug 2014 WO
WO 2014205283 Dec 2014 WO
WO2015061718 Apr 2015 WO
WO 2015054193 Apr 2015 WO
WO 2015055971 Apr 2015 WO
WO2015070016 May 2015 WO
WO 2016168082 Oct 2016 WO
Non-Patent Literature Citations (94)
Entry
“3M and Patient Care Technology Systems Collaborate on State of-the-Art Automated Hand Hygiene Solution to Improve Compliance,” retrieved from http://news.3m.com/pt/press-release/company/3m-and-patient-care-technology, on Apr. 13, 2017, 2 pp.
Al-Hamad et al., “How Clean is Clean? Proposed Methods for Hospital Cleaning Assessment,” Journal of Hospital Infection, vol. 70, Oct. 9, 2008, pp. 328-334.
“America's Dirty Little Secret: Second Handwashing Survey Reveals Americans Still Don't Get It,” American Society for Microbiology, Sep. 19, 2000, 3 pp.
Anonymous et al., “Hand Hygiene,” Progressive Grocer, vol. 76, No. 8, Aug. 1997, pp. 111-112.
“Bentley WiNET Tag User Guide—FAS1503, DOC1036,” UltraClenz, Jan. 25, 2011, 12 pp.
Bourn, Auditor General for Wales, “The Management and Delivery of Hospital Cleaning Services in Wales,” National Audit Office Wales, 39 pp., May 23, 2003.
CDC, HICPAC, “Guideline for Hand Hygiene in Health-Care Settings,” Morbidity and Mortality Weekly Report, Recommendations and Reports, (MMWR) vol. 51, No. RR-16, Oct. 25, 2002, 56 pp.
Dancer, “How do we Assess Hospital Cleaning? A Proposal for Microbiological Standards for Surface Hygiene in Hospitals” Journal of Hospital Infection, vol. 56, Sep. 2003, pp. 10-15.
Diller et al., “Estimation of hand hygiene opportunities on an adult medical ward using 24-hour camera surveillance: Validation of the HOW2 Benchmark Study,” American Journal of Infection Control, vol. 42, 2014 (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2014, is sufficiently earlier than the effective U.S. filing date, 2017, so that the particular month of publication is not in issue.) pp. 602-607.
Diversey, Diverlog-L Enhanced “DLE- Production Summary Reports,” Apr. 1990, 5 pp.
Diversey, “iMAP TM/MC . . . Data Collection & Reporting Platform,” Diversey Inc., Sep. 5, 2013, 2 pp.
Diversey “Sealed Air's Diversey Business Introduces Mobile Application to Capture Facility Auditing Data,” Diversey Inc., Oct. 18, 2011, 2 pp.
Diversey, “iMAP Internet Mobile Auditing Platform,” Diversey Inc., 2012 (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2012, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) 2 pp.
Diversey, “iMAPTM/MC Internet Mobile Auditing Platform”, 2012, (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2012, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) 2 pp.
Diversey, “Diversey VeriCiean™ System Implementation and Support Guide,” 2012, (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2012, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) 64 pp.
Diversey, “Unleash Your Data, The power of iMAP is now available on virtually any smart device. Get robust data collection and analysis anytime, anywhere, in any language,” Diversey Inc., Sep. 15, 2011, 2 pp.
Diversey, “Reporting,” downloaded from Diversey.com, Sep. 5, 2013, 1 pp.
Dix et al., “Environmental Surface Cleaning: First Defense Against Infectious Agents,” Infection Control Today Magazine, 6 pp., Dec. 1, 2005.
“Don't Get Caught Dirty Handed,” ASM's Microbes Afterhours, Sep. 6, 2009, 11 pp.
“Dr. Semmelweiss Was Right: Washing Hands Prevents Infection,” Water Quality and Health Council, retrieved from www.waterandhealth.org/newsletter/new/4/12/2017/right.htm, Feb. 2017, 2 pp.
ECOLAB® BALANCER. COM, MRE, Jun. 4, 1997, 4 pp.
ECOLAB® INC., product brochure: “relax. We've Got Your Pool Concerns Under Control,” copyright 1998, (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1998, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) 4 pp.
ECOLAB® INC., product brochure: “We'd like to make a couple of things perfectly CLEAR,” copyright 1998, (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1998, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) 4 pp.
Elliott, “Determining Three Metrics for Cleaning Satisfaction,” found at http://www.facilitiesnet.com/fn/article.asp?id-7698, equipmentrentaltools/article/Determining-Three-Metrics-for -Cleaning-Satisfaction-7698#, Nov. 2007, 2 pp.
“Evaluating Municipal Services: Scorecard Cleanliness Program Prospectus,” New York, found at http://www.worldsweeper.com/Street/Profiles/NYCScorecard.pdf, archived Jan. 5, 2009, 16 pp.
“Evidence of hand hygiene to reduce transmission and infections by multi-drug resistant organisms in health-care settings,” World Health Organization, Jan. 5, 2014, 7 pp.
Exner et al., “Household Cleaning and Surface Disinfection: New Insights and Strategies,” Journal of Hospital Infection, vol. 56, Apr. 2004, pp. s70-s75.
Florida Department of Health, “Guidelines for Control of Antibiotic Resistant Organisms,” Dec. 20, 1999, 34 pp.
Garner et al., “Guideline for Handwashing and Hospital Environmental Control,” CDC Prevention Guidelines, Jan. 1, 1985, 10 pp.
Garner, “Guidelines for Isolation Precautions in Hospitals,” Hospital Infection Control Advisory Committee, Jan. 1, 1996, 39 pp.
Green, “Hand hygiene in 2015: 7 Findings,” retrieved from http://www.beckershospitalreview.com/quality!hand-hygiene-i n-2015-7-findings.htm l?tm pl=com ponent&print= 1 &layout=default&page=, Nov. 12, 2015, 1 pp.
Griffith et al., “An Evaluation of Hospital Cleaning Regimes and Standards,” J. Hosp. Infect., vol. 45, pp. 19-28, 2000, accepted Dec. 23, 1999.
Griffith et al., “The Effectiveness of Existing and Modified Cleaning Regimens in a Welsh Hospital,” Journal of Hospital Infection, vol. 66, Jul. 26, 2007, pp. 352-359.
Griffith, “Nosocomial infection: Are there lessons from the food industry?” The Biomedical Scientist, pp. 697-699, Aug. 2006.
Hamilton et al., “Hand Hygiene,” Wild Iris Medical Education, Inc., 2014, (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2014, is sufficiently earlier than the effective U.S. filing date, 2017, so that the particular month of publication is not in issue.) 24 pp.
“Hand Washing, Cleaning, Disinfection and Sterilization in Health Care,” Infection Control Guidelines, Canada Communicable Disease Report, vol. 24S8, Dec. 1998, 66 pp.
HICPAC, “Recommendations for Preventing the Spread of Vancomycin Resistance,” Morbidity and CDC Mortality Weekly Report, Recommendations and Reports, vol. 44, No. RR-12, 1-13, Sep. 22, 1995, 16 pp.
“Home Routines for iPhone, iPod touch, and iPad on the iTunes App Store,” retrieved from the internet https:/litunes.apple.com/us/app/homeroutines/id353117370?mt=8, Sep. 5, 2013, 3 pp.
“Home Routines App for iPhone, iPad, & iPod touch,” retrieved from the Internet http://www.homeroutines.com/, (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2010, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) 7 pp.
Larson et al., “A Multifaceted Approach to Changing Handwashing Behavior,” American Journal of Infection Control, vol. 25, Feb. 1997, pp. 3-10.
Larson, “APIC Guideline for Hand Washing and Hand Antisepsis in Health-Care Settings*,” APIC Guidlines Committee, 1995, (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1995, is sufficiently earlier than the effective U.S. filing date, 2017, so that the particular month of publication is not in issue.), Am J Infect Control, 23:251, 18 pp.
Levchenko et al., “Embedded System for Hygiene Compliance Monitoring,” IEEE Transactions on Automation Science and Engineering, vol. 7, No. 3, Jul. 2010, 4 pp.
Lewis et al., “A Modified ATP Benchmark for Evaluating the Cleaning of Some Hospital Environmental Surfaces,” Journal of Hospital Infection, vol. 69, May 12, 2008, pp. 156-163.
Malik et al., “Use of Audit Tools to Evaluate the Efficacy of Cleaning Systems in Hospitals,” Am. J. Infect. Control, vol. 31, No. 3, p. 181-187, May 2003.
Mallow General Hospital, “Hygiene Services Assessment Scheme, Assessment Report,” 38 pp., Oct. 2007.
Mangram et al., “Guideline for Prevention of Surgical Site Infection, 1999,” Infection Control and Hospital Epidemiology, vol. 20, No. 4, Apr. 1999, pp. 247-278.
“Measuring Hand Hygiene Adherence: Overcoming the Challenges,” The Joint Commission et al., 2009 (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2009, is sufficiently earlier than the effective U.S. filing date, 2017, so that the particular month of publication is not in issue.) 234 pp.
Meengs et al., “Hand Washing Frequency in an Emergency Department,” Annals of Emergency Medicine, vol. 23, No. 6, Jun. 1994, pp. 1307-1312.
Mills et al., “Guidelines for Working with Rodents Potentially Infected with Hantavirus,” Journal of Mammalogy, vol. 76, No. 3, Aug. 1995, pp. 716-722.
Munro et al., “Treating Exposure to Chemical Warfare Agents: Implications for Health Care Providers and Community Emergency Planning,” Environmental Health Perspectives, vol. 89, 1990 (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1990, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) pp. 205-2015.
“Net/Tech to Unveil Patented Hygiene Guard Hand-Washing Monitoring System at the National Restaurant Show,” BusinessWire, Apr. 3, 1997, 3 pp.
Nexgen SI, Inc., “InTouch Water Treatment Information Management Solution,” Mar. 29, 1999, 59 pp.
Nova Controls, Nova News, “Save Money and Gain Sales Features?” Aug. 12, 1992, 1pg.
Nova Controls, “ORION Liquid Laundry Supply Dispenser,” Feb. 1989, 5 pp.
NOV ALINK™ brochure: “Laundry information System: Overview Reports,” Dec. 13, 1995, 6 pp.
NOV ALINK™ Laundry Information System, Control Master Version 2.0 for Windows User's Guide, 2000, 39 pp.
NOV ALINK™ OverViewTM Program Pricing. cited in an IDS in U.S. Appl. No. 10/436,454 on May 20. 2005. 1 pg.
Ophardt, Hygiene-Technik GmbH+ Co. KG, “Making the World a More Hygienic Place”, Hygiene Compliance Solutions, 2009 (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2009, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) 1 page.
“Patient Safeguard System Healthcare Worker Badge User's Guide,” DOC1046 Revision 8, UltraClenz, Mar. 14, 2012, 21 pp.
Persyst Inc., “Dial-A-Wash Automatic Laundry Room Attendant for Apartment and Complex Laundry Rooms,” cited in an IDS in U.S. Appl. No. 10/436,454 on May 20, 2005, 2 pp.
Persyst Inc., “LDAS-2000 Remote Information Control and Management System for the Commercial Laundryand Vending Industry,” cited in an IDS in U.S. Appl. No. 10/436,454 on May 20, 2005, 4 pp.
Pittet et al., “Compliance with Handwashing in a Teaching Hospital,” Annals of Internal Medicine, vol. 130, No. 2, Jan. 19, 1999, pp. 126-130.
PowerPoint Presentation: “ECOLAB® Aramark Uniform Services Joining Forces for Service Excellence,” 1998, (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1998, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) 69 pp.
“ProGiene System Description for UL and CE Mark Approval,” UltraClenz, Feb. 8, 2002, 5 pp.
Quattrin, Md, et al., “Application of Hazard Analysis Critical Control Points to Control Surgical Site Infections in Hip and Knee Arthroplasty,” Orthopedics 31:132, 6 pp., Feb. 2008, SLACK Incorporated.
SaferCorp, LLC, “SaferCorp Life Advantage Solutions presents SaferHands™ Hospital Automated Hand Hygiene Monitoring System”, retrieved electronically from http://www.guardianics.com/ on Dec. 15, 2010, 14 pp.
SaferCorp, LLC, Guardian™ Automated Infection Control Systems (GAICS), Feb. 6, 2010, 4 pp.
Sahud et al., “An Electronic Hand Hygiene Surveillance Device: A Pilot Study Exploring Surrogate Makers for Hand Hygiene Compliance,” Infection Control and Hospital Epidemiology, vol. 31, No. 6, Jun. 2010, 6 pp.
Sample Reports, NOVALINK™ System., Jan. 1996, 9 pp.
Sample Reports, Nova Controls, Oct. 1997, 8 pp.
Sax et al., “My five moments for hand hygiene: a user-centered design approach to understand, train, monitor and report hand hygiene,” Journal of Hospital Infection, vol. 67, Aug. 27, 2007, pp. 9-21.
Semmelweis, “The Etiology, Concept, and Prophylaxis of Childbed Fever,” The University of Wisconsin Press, 1983 (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1983, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) 14 pp.
Steed et al., “Hospital Hand Hygiene Opportunities: Where and When (HOW2)? The HOW2 Benchmark Study,” American Journal of Infection Control, vol. 39, Feb. 2011, 8 pp.
Sturman et al., “Cornell University Hospitality Report: A New Method for Measuring Housekeeping Performance Consistency,” CHR Reports, vol. 6, No. 11, Sep. 2006, 15 pp.
Swedberg, “RFID-based Hand-Hygiene System Prevents Health-Care Acquired Infections,” RFID Journal, Jun. 10, 2010, 2 pp.
Swoboda et al., “Electronic Monitoring and Voice Prompts Improve Hand Hygiene and Decrease Nosocomial Infections in an Intermediate Care Unit,” Crit Care Med, vol. 32, No. 2, 2004 (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2004, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) pp. 358-363.
Taylor, An Evaluation of Handwashing Techniques-1, Nursing Times, vol. 74, Jan. 12, 1978, pp. 54-55.
Thompson et al., “Handwashing and Glove Use in a Long -Term-Care Facility,” Infection Control and Hospital Epidemiology, vol. 18, No. 2, Feb. 1997, pp. 97-103.
Tibballs et al., “Teaching Hospital Medical Staff to Handwash,” The Medical Journal of Australia, vol. 164, No. 7, Apr. 1, 1996, pp. 395-398.
T-JET™ 2000 PC, “Wash-Aisle Productivity Manager Software Guide,” ECOLAB® Textile Care Division, undated, 2000 (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2000, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) 29 pp.
Tsai et al., “iMAT: Intelligent Medication Administration Tools,” Aug. 2010, 8 pp.
Van Ryzin et al., “Measuring Street Cleanliness: A Comparison of New York City's Scorecard and Results from a Citizen Survey,” Public Administration Review 68(2), Mar./Apr. 2008, pp. 295-303.
Watanakunakorn et al., “An Observational Study of Hand Washing and Infection Control Practices by Healthcare Workers,” Infection Control and Hospital Epidemiolgy, vol. 19, No. 11, Nov. 1998, pp. 858-860.
“WHO Guidelines on Hand Hygiene in Health Care,” World Health Organization, 2009 (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2009, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.) 270 pp.
“WHO Guidelines on Hand Hygiene in Health Care (Advanced Draft),” World Health Organization, Apr. 2006, 216 pp.
Yoshikura, “Workflow from Clean to Dirty, HACCP and Inclusiveness Principles in Effective Implementation of Hospital Infection Control,” Jpn. J. Infect. Dis. 53, Jun. 6, 2000, 2 pp.
Zuhlsdorf et al., “Cleaning Efficacy of Nine Different Cleaners in a Washer-Disinfector Designed for Flexible Endoscopes,” Journal of Hospital Infection, vol. 52, Oct. 9, 2002, pp. 206-211.
Prosecution History from U.S. Appl. No. 12/787,064, dated Dec. 6, 2012, through Apr. 8, 2013, 20 pp.
Prosecution History from U.S. Appl. No. 14/819,349, dated Apr. 5, 2019, 23 pp.
Prosecution History from U.S. Appl. No. 12/683,666, dated Aug. 21, 2012, through Apr. 17, 2013, 36 pp.
“Hygiene Connect,” Initial UK, retrieved from https://www.initial.co.uk/hygiene-connect/ on Jun. 18, 2019, 2 pp.
U.S. Appl. No. 14/819,349, filed Aug. 5, 2015, by Tokhtuev et al.
Final Office Action from U.S. Appl. No. 14/819,349, dated Oct. 9, 2019, 32 pp.
Amendment in Response to Office Action dated Apr. 5, 2019, from U.S. Appl. No. 14/819,349, filed Aug. 27, 2019, 20 pp.
Related Publications (1)
Number Date Country
20190147731 A1 May 2019 US
Provisional Applications (1)
Number Date Country
62584301 Nov 2017 US