US20100326472A1 - Automated washing system with compliance verification - Google Patents
Automated washing system with compliance verification Download PDFInfo
- Publication number
- US20100326472A1 US20100326472A1 US12/880,946 US88094610A US2010326472A1 US 20100326472 A1 US20100326472 A1 US 20100326472A1 US 88094610 A US88094610 A US 88094610A US 2010326472 A1 US2010326472 A1 US 2010326472A1
- Authority
- US
- United States
- Prior art keywords
- compliance
- cleaning
- user
- data
- station
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/20—Education
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
- G07F17/18—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for washing or drying persons
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B21/00—Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
- G08B21/18—Status alarms
- G08B21/24—Reminder alarms, e.g. anti-loss alarms
- G08B21/245—Reminder of hygiene compliance policies, e.g. of washing hands
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H20/40—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to mechanical, radiation or invasive therapies, e.g. surgery, laser therapy, dialysis or acupuncture
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/63—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for local operation
Definitions
- the present invention relates to automated washing systems, and more particularly, to automated washing systems comprising a way of monitoring and/or verifying user participation. Methods of providing compliance verification are also provided.
- Touchless automated hand-washing devices are designed to wash the hands of the user and provide the proper amount of antimicrobial solution in a set time. Additionally, these systems diminish the deterrent effects of friction and irritation associated with frequent manual hand-washing. Notwithstanding the benefits and convenience of automated washing devices, difficulties still exist with verifying employee or staff use of the washing apparatus. Accordingly, it would be advantageous to have a system that provides automated washing with a way of verifying usage by the intended users.
- problems also exist with verifying that the proper soap solutions or disinfectants are being used in a cleaning station.
- problems exist with assessing whether a user has an allergy where the user should not use a certain type of soap or disinfectant provided in a cleaning station.
- problems exist in providing a solution in a cleaning station to avoid an allergy of a user.
- problems exist in providing user specific formulations that address, for example, the user's specific job duties.
- problems exist in motivating users to stay at a cleaning station for its entire cleaning cycle.
- problems exist in providing information to a manager or administrator regarding monitoring one or more cleaning stations, wherein the monitoring may include review of data directed to addressing one or more of the above noted problems.
- U.S. Pat. No. 7,015,816, U.S. Pat. No. 6,727,818 and United Stated Patent Application Publication No. 2006/0132316 are directed to systems that in part address the problems outlined above.
- the summary of each document indicates that the disclosed systems are directed to monitoring or gathering information on locations of person, equipment, and/or activities associated with a facility. The gathered information is used to evaluate compliance with hygiene requirements as defined by a hygiene policy for a facility.
- facility e.g. hospital
- These systems also make no allowance for people with no hand-washing requirements such as visitors to the facility.
- these systems include a burdensome system of in/out zones, do not provide for automatic reporting, and do not include hand-washing requirements that are specific to a person's job title. Furthermore, these systems do not disclose a system for automatically providing hygiene compliance information to a regulatory body.
- a Radio Frequency Identification (“RFID”) system for use in connection with an automated hand-washing station.
- RFID Radio Frequency Identification
- other identifying technologies are appropriate, and such technologies are encompassed by the scope of the present invention. Examples include bar codes, biometric technology and the like. It is to be understood therefore, that RFID is used as an example and is not intended to limit the scope of the present invention.
- the system is operable to record and report on user compliance with hand-washing requirements. To ensure user safety and product performance, the system has the capability to ensure that only authorized consumable solutions are used in the cleaning station.
- the RFID data capture capability in conjunction with a video system, allows users to have real time feedback of their personal compliance as well as individual user focused information conveyed at the time of utilizing the cleaning station.
- the user carries a RFID tag that is programmed with information specific to the individual.
- an RFID reader Upon approaching the cleaning station, an RFID reader recognizes the user's tag and records the user name, time, date, station location, and whether the cleaning event was a complete cycle.
- the data is stored in the readers' database until captured via various methods and transferred into a report format for the administrator. The administrator can then review the compliance statistics for the various users.
- the RFID system is well suited to monitoring whether a consumable item used in the cleaning station is authentic or not authorized. Upon detection of an improper consumables item the cleaning station may deactivate.
- An RFID tag is attached to the consumable product, such as a cleaning solution bottle. When installed in the cleaning station, the tag attached to the solution bottle will confirm to the RFID system by way of the unique tag identifier that the subject bottle contains an authorized solution. Without this verification, a user of the station may inadvertently use another solution that is harmful to the user or ineffective for the use intended.
- Another benefit is that an authorized solution will be at the correct viscosity to ensure the proper dosage is used in the wash cycle and the mechanical action of the station will not be compromised by plugged fluid nozzles and lines.
- Embodiments of the present invention include methods of providing compliance or non-compliance information regarding hygiene efforts.
- a method for performing hygiene compliance verification comprising:
- a method of performing hygiene compliance verification comprising: receiving hygiene compliance data associated with a plurality of enterprise networks, each network being associated with a different enterprise comprising one or more automated sensors; storing the hygiene compliance data; and providing at least one hygiene compliance data report, the hygiene compliance data report including hygiene compliance data received from a particular enterprise network of the plurality of enterprise networks.
- an electronic hygiene compliance verification data signal comprising:
- a compliance monitoring system comprising: means for receiving compliance data associated with a plurality of enterprise networks; means for storing the compliance data in a plurality of electronic storage locations, wherein each storage location corresponds to one enterprise network of the plurality of enterprise networks; and means for providing at least one compliance data report, the compliance data report including compliance data received from a particular enterprise network of the plurality of enterprise networks.
- Such system may further include means for providing the compliance data report to a web user, the web user having supplied a valid password.
- such system may further include means for providing the compliance data report to a compliance monitor.
- a computer readable medium comprising a set of data structures
- the set of data structures comprising:
- a compliance monitoring system for use with at least one hygiene station comprising:
- an electronic storage location for storing compliance data collected by the at least one hygiene station, wherein the compliance data comprises a plurality of different object identifiers and different protocol identifiers, each protocol identifier being associated with a different cleaning protocol, wherein each object identifier has a corresponding protocol identifier and wherein at least one protocol identifier indicates that no cleaning be performed for the corresponding object identifier.
- the system may further comprise a plurality of enterprise networks, each enterprise network including at least one corresponding hygiene station; and a plurality of electronic storage locations, each storage location being associated with a corresponding enterprise network and storing compliance data collected by the at least one corresponding hygiene station in the corresponding enterprise network.
- Embodiments of the present invention cover compliance verification of different forms of a hygiene station.
- one or more embodiments of the present invention are appropriate for monitoring associated with hygiene stations that comprise a sink and a faucet, automated cleaning stations, disinfection stations, sanitizer dispensers, sanitizer gel dispensers, lotion dispensers, hand soap dispensers, or other ancillary devices, et cetera.
- each of the expressions “at least one of A, B and C”, “at least one of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B, or C” and “A, B, and/or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.
- automated refers to any process or operation done without material human input when the process or operation is performed. However, a process or operation can be automatic even if performance of the process or operation uses human input, whether material or immaterial, received before performance of the process or operation. Human input is deemed to be material if such input influences how the process or operation will be performed. Human input that consents to the performance of the process or operation is not deemed to be “material”.
- module refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and software that is capable of performing the functionality associated with that element. Also, while the invention is described in terms of exemplary embodiments, it should be appreciated that individual aspects of the invention can be separately claimed.
- FIG. 1 is a block diagram of components that may be included in embodiments of the present invention.
- FIG. 2 is a schematic depiction of a cleaning station in accordance with embodiments of the present invention.
- FIG. 3 is a block diagram of a cleaning station operations monitor in accordance with embodiments of the present invention.
- FIG. 4 is an exemplary station-use record in accordance with embodiments of the present invention.
- FIG. 5A is an exemplary employee record in accordance with embodiments of the present invention.
- FIG. 5B shows a set of data structures according to an embodiment of the present invention
- FIG. 6 is a block diagram of an administration computer in accordance with embodiments of the present invention.
- FIG. 7 is an exemplary compliance report in accordance with embodiments of the present invention.
- FIG. 8 is a flow chart depicting aspects of a method of monitoring hand-washing compliance in accordance with embodiments of the present invention.
- FIGS. 9A and 9B are a compliance monitoring system according to another embodiment of the present invention.
- FIG. 10 is an exemplary data management module report
- FIG. 11 is a flow chart according to an embodiment of the present invention.
- FIG. 12 shows a set of data structures according to an embodiment of the present invention.
- FIG. 13 is a flow chart according to an embodiment of the present invention.
- the exemplary embodiments illustrated herein show the various components of the system collocated, certain components of the system can be located remotely, at distant portions of a distributed network, such as a LAN and/or the Internet, or within a dedicated system.
- the components of the system can be combined in to one or more devices, such as a washing station, or collocated on a particular node of a distributed network, such as an analog and/or digital telecommunications network, a packet-switched network, or a circuit-switched network.
- the components of the system can be arranged at any location within a distributed network of components without affecting the operation of the system.
- the various components can be located in a switch, media server, gateway, in one or more washing stations, at one or more users' premises, or some combination thereof.
- the various links connecting the elements can be wired or wireless links, or any combination thereof, or any other known or later developed element(s) that is capable of supplying and/or communicating data to and from the connected elements.
- These wired or wireless links can also be secure links and may be capable of communicating encrypted information.
- Transmission media used as links can be any suitable carrier for electrical signals, including coaxial cables, copper wire and fiber optics, and may take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
- the present invention is directed to a system and method for ensuring employee compliance with washing requirements, such as hand-washing requirements.
- washing requirements such as hand-washing requirements.
- embodiments of the present application are also applicable to other types of washing systems, including for example, boot-washing systems.
- employee use of one or more automated cleaning stations is monitored.
- the cleaning stations operate to dispense one or more fluids, such as water, a cleaning fluid, such as soap, and/or a disinfectant, etc., while a person's hands are placed in a washbasin.
- a “washbasin” means a structure associated with the cleaning station where the hands (or boots) are cleaned, such as one or more wash cylinders, spray areas, pans, tubs, etc.
- the cleaning stations are operable to record and report data related to employee compliance with such requirements. At least some employees may not be required to wash their hands.
- an “object” may refer to anything cleaned by the automated cleaning station.
- An object may be, for example, an appendage of a user, a tool, a boot, and/or an inanimate object, etc.
- inanimate object means an object that is principally not a biological tissue, although biological matter may be associated with the inanimate object, for example, a virus, bacteria, and/or pieces of tissue on a tool.
- FIG. 1 components of a compliance system in accordance with embodiments of the present invention are illustrated in block diagram form.
- a plurality of cleaning stations 100 a, 100 b . . . 100 n may be used by people employed at a facility that requires employees to wash their hands.
- Such facilities may include, for example, restaurants, food processing facilities, hospitals and laboratories.
- an administration computer 104 for use by a manager or administrator of the facility.
- the administration computer 104 is operable to generate a compliance report as described herein.
- an administration computer 104 may include a file server or other network computer operable to serve as a data collection point for data associated with cleaning stations 100 a . . . 100 n . Additionally, it should be understood that separate computational devices may be used to store data and to access the stored data.
- the administration computer 104 communicates with the cleaning stations 100 a - 100 n over a plurality of communication links 108 a, 108 b . . . 108 n.
- the communication links may be implemented by any one of a variety of methods and may depend on the type of facility in which the cleaning stations 100 a - 100 n are used.
- the communication links 108 a - 108 n may be implemented as part of a local area network (LAN) or a wide area network (WAN).
- LAN local area network
- WAN wide area network
- a “communication link” does not imply a direct connection between two endpoints.
- a “communication link” may include a communication session having parts that are routed through various nodes of a communication network.
- the communication links 108 a - 108 n may be implemented using such protocols as Ethernet or USB.
- the communications links 108 a - 108 n may be implemented as wired or wireless connections. It may be the case that the administration computer 104 is located in a separate facility from one or more of the cleaning stations 100 a - 100 n. In this case, a distributed data network such as the Internet may form part of the communication links 108 a - 108 n.
- the cleaning station 100 a includes a cleaning station operations monitor 200 .
- the cleaning station operations monitor 200 may comprise a computational device such as a general-purpose computer, controller, or ASIC that controls and coordinates the operation of the various electronic components associated with the cleaning station 100 a. Additionally, the cleaning station operations monitor 200 is operable to record data associated with employee use of the cleaning station 100 a and to report the data to the administration computer 104 .
- the cleaning station operations monitor 200 may be incorporated into the cleaning station 100 a or, alternatively, may be implemented as a separate computing device.
- the user 204 may be an employee or visitor who is required to wash their hands because of the nature of their work or the nature of the facility.
- the user 204 is shown wearing a user RFID tag 208 .
- the user RFID tag 208 is programmed by an RFID tag programming device (not shown) with information such as an employee number that, when read, uniquely identifies the employee or user 204 .
- the RFID tag 208 may be incorporated into an identification badge or bracelet worn by the user 204 .
- the cleaning station 100 a includes an RFID reader 212 and an optical sensor 216 .
- the RFID reader 212 is positioned so as to be able to read the user RFID tag 208 when the user 204 is washing his or her hands at the cleaning station 100 a.
- the RFID reader 212 may be incorporated into the cleaning station 100 a or, alternatively, may be implemented as a stand-alone device.
- the RFID reader 212 may be positioned adjacent to a cabinet associated with the cleaning station 100 a.
- the optical sensor 216 is positioned so as to be able to sense that the hands of the user 204 are placed within the washbasin 220 in a position where they will properly receive cleaning fluids, such as water, soap and/or disinfectant as dispensed by the cleaning station 100 a.
- the RED reader 212 and the optical sensor 216 are in communication with cleaning station operations monitor 200 , which, in turn, is operable to collect data associated with these devices. In particular, data is collected from the RFID reader 212 indicating the identity of the user 204 . Additionally, the cleaning station operations monitor 200 records the length of time in which the hands of the user 204 were placed in the washbasin 220 as indicated by the optical sensor 216 .
- a user may be identified by means of a typed password, retinal scan, voice print, palm print, fingerprint, face identification, bar coding (on an employee ID), etc.
- the cleaning station 100 a also includes a video display 224 positioned for viewing by the user 204 when he or she is washing his or her hands.
- the video display 224 may be incorporated in the cleaning station 100 a or, alternatively, may be implemented as a separate device.
- the video display 224 may be positioned on a wall in front of the user 204 as they stand at the cleaning station 100 a.
- the video display 224 operates to display brief video segments to the user 204 while the cleaning station 100 a is cleaning his or her hands.
- the video display 224 may be under the control of the cleaning station operations monitor 200 . As the user 204 is utilizing the cleaning station 100 a, administrator-selected data is transmitted to the video display 224 .
- This information may be simple feedback to the user 204 informing them of the amount of hand washings they did in the current day, week, month, etc.
- This system has the flexibility to provide a wide range of communications to the user 204 .
- a consumables container 228 that contains a material, such as soap or disinfectant used in connection with the operation of the cleaning station 100 a .
- a plurality of consumable containers 228 may be associated with a cleaning station 100 a.
- the consumables container 228 includes a detachable connection to a consumable receptacle 230 associated with the cleaning station 100 a so that the consumable container 228 may be removed and disposed of when its contents are expended. After the disposal of a used consumables container 228 , a new consumables container 228 is then attached to the cleaning station 100 a.
- the consumables container 228 also includes a consumables RFID tag 232 that contains information related to the consumable container 228 .
- a consumables RFID reader 236 associated with the cleaning station 100 a reads the consumables RFID tag 232 and communicates information related to the consumables container 228 to the cleaning station operations monitor 200 .
- RFID is discussed herein for use of identification of consumables, other types of identification systems may be used, such as bar codes.
- the cleaning station monitor 200 is a computational device. Accordingly, the cleaning station operations monitor 200 includes a processor 300 , a memory 304 and signaling interfaces 308 and 312 operable to communicate with external electronic and/or computational components.
- the first signaling interface 308 operates to communicate with the administration computer 104 over communication link 108 a, as described above.
- the second signaling interface 312 operates to communicate with the various electronic components associated with the cleaning station 100 a including the RFID readers 212 and 236 , the optical sensor 216 , and the video display 224 .
- the second signaling interface 312 may be a portion of a backplane incorporated into cleaning station 100 a that includes a connection to the cleaning station's 100 a electronic components.
- the cleaning station operations monitor 200 may communicate with the cleaning station's electronic components through a network or serial bus connection.
- the memory 304 includes a plurality of stored program applications or modules that implement various features of a compliance monitoring system.
- the memory 304 may include a compliance-monitoring module 316 , a training module 320 , a consumables authentication module 324 , and/or a solutions selection module 328 .
- the memory 304 may include data structures 332 associated with the various modules.
- the data structures 332 include a station-use record 336 and one or more employee records 340 . The operation of the various modules and data structures is described in greater detail below.
- the compliance-monitoring module 316 operates to monitor and record the activity of a plurality of users 204 of the cleaning station 100 a.
- the process is outlined as follows.
- the user 204 approaches a cleaning station 100 a with a RFID tag 208 on their person, which was programmed with a RFID tag programming device with the individual's name or number, and/or other pertinent data.
- the tag 208 is read by the RFID reader 212 when the user 204 approaches and/or begins using the cleaning station 100 a.
- the optical sensor 216 initiates a cleaning cycle.
- the optical sensor 216 will indicate in the data structure 332 that the user 204 did not have a complete cleaning.
- the data showing such items as user name, time, date, station location and/or identification, and whether the cycle was complete, etc., is stored in the data structure 332 .
- the stored data is later accessed by the administration computer 104 in connection with the generation of a compliance report.
- an exemplary station-use record 336 having data associated with a plurality of users 204 is shown in FIG. 4 .
- an entry in the station-use record 336 may include an employee name 400 indicating who used the cleaning station 100 a, a time stamp 404 indicating when the cleaning cycle was initiated, a duration 408 indicating how long the user 204 kept his or her hands in the washbasin 220 , the date 412 , and a compliance indicator 416 specifying whether or not the user 204 kept his or her hands in the washbasin 220 for the required time.
- the station-use record 336 may contain only raw data such as the time 404 , date 412 and duration 408 of the cleaning cycle while determinations related to compliance requirements are made by a separate module running on the administration computer 104 .
- the compliance-monitoring module 316 may also operate to monitor hand-washing requirements that are specific to each employee. Some employees may have stricter hand washing requirements than others at the same facility. For example, a hospital emergency room may employ both surgeons and social workers. As can be appreciated, the surgeons will be required to wash their hands more frequently and more thoroughly than the social workers. Accordingly, the compliance-monitoring module 316 may access employee records to determine the type, concentration, and/or amount of cleaning fluid to be dispensed for a particular employee. Additionally, employee records may contain other hand washing compliance data that is specific to each employee such as the amount of time and/or frequency that an employee is required to wash his or her hands. Washing requirements may also depend on an employee's history of compliance with his or her washing requirements. For example, an employee may be required to wash his or her hands more thoroughly if his or her previous hand washings were incomplete or hand not been wash for some period of time.
- Embodiments of the present invention may include a training module 320 .
- the training module 320 operates to transmit educational information to the user 204 while the cleaning cycle is running via sound and/or a visual source, such as a video display 224 .
- the information may comprise segments equal in duration, or slightly longer or shorter in duration than the cleaning cycle.
- the segments may contain information regarding hand hygiene in a series of segments lasting approximately 10-15 seconds.
- the employee record 340 portion of the data structure 332 keeps track of the user 204 and knows the sequence of training segments so each time a user 204 uses the cleaning station 100 a, the next pertinent training segment will display on the video display 224 .
- the training module 320 may access the employee record 340 to provide custom designed content in conjunction with the user's 204 needs/requests. Accordingly, as one possible alternative to educational/training content, entertainment content specific to the user's 204 preferences may be displayed. Here, other information is conveyed to the user, such as news (e.g., weather, breaking stories, current events, stock prices, etc.) and sports information. The training module 320 may, therefore, accommodate specific requests to convey information of interest to the user. In at least one embodiment of the present invention, the information conveyed to the user may be anything other than information about a cleaning station function parameter (e.g., water pressure, soap level, etc.). That is, content other than information about the cleaning station operating parameters so that the user is interested in staying at the cleaning station for an entire wash cycle.
- a cleaning station function parameter e.g., water pressure, soap level, etc.
- the training module 320 may give feedback to the user 204 through the video display 224 , including such information as their hand-washing statistics over a given period of time.
- the administrator of a facility may want to encourage system usage by conveying one or more compliance statistics, and/or informing a user 204 that the user 204 has won a prize by having high marks for compliance with the hand-washing protocol.
- the employee record 340 may keep track of data associated with user 204 , and this data may be accessed by the training module 320 to inform the user 204 in real time, and/or the administrator in a subsequent report, as to compliance statistics.
- the video display 224 may be used to provide notices, such as for upcoming meetings and events that are pertinent to all staff or to a specific person.
- the solutions selection module 328 may determine which solution is to be used with each individual user 204 . For example, one user 204 may have an allergy to the standard solution, so the system is programmed to automatically use a different and appropriate solution when this user 204 is identified through their RFID tag 208 . Information related to user allergies may be contained in the employee record 340 .
- an exemplary employee record 340 for use in connection with both the training module 320 and the solutions selection module 328 is shown in FIG. 5A .
- an entry in the employee record 340 may include the employee name 500 , hand-washing 504 statistics associated with employee, current training segment 508 to be viewed by the employee, the employee's preferred entertainment content 512 , and/or a listing of the employee's allergies 516 .
- the employee record shown in FIG. 5A indicates that Bill Forbes is in 97% compliance with the hand-washing requirement, has currently viewed seven training modules, prefers to watch the news while washing his hands, and has an allergy to cleaning solution A.
- an employee record may include a lookup table that indicates a particular cleaning protocol that is to be applied to a particular employee.
- An exemplary lookup table 520 is shown in FIG. 5B .
- the lookup table 520 includes a plurality of employee identifiers 524 and, for each employee identifier, a corresponding employee type indicator 528 and cleaning protocol identifier 532 .
- the employee identifier 524 is commonly an RFID or suitable wirelessly readable identification code.
- the employee type indicator 528 commonly references the job responsibilities and/or title/position of the identified employee.
- a “1” might refer to a nurse, a “2” to an imaging technician, a “3” to a doctor, and a “4” to a member of the janitorial staff.
- the particular individuals may be identified by a key code including a name or a job description.
- the cleaning protocol identifier 532 refers to the particular cleaning protocol to be used for the corresponding identified employee.
- each cleaning protocol has a corresponding set of cleaning medium to be used, medium application duration, and wash duration.
- cleaning protocol identifier “1” may require a ChlorHexidine Gluconate (“CHG”) wash, a “2” either a CHG wash or alcohol towelette or wipe, and a “3” a CHG wash followed by an alcohol wipe.
- CHG ChlorHexidine Gluconate
- Examples of other sanitizing solutions that may be used individually or collectively in cleaning protocol(s) include quaternary ammonium solutions.
- the cleaning protocol identifier is further varied based upon the location of the corresponding washing station, which is readily determined from the station identifier. A washing station in a highly hygiene sensitive area, such as an operating room, may provide a more demanding cleaning protocol than a station at a less hygiene sensitive area, such as a nursing station.
- the cleaning protocol identifier may indicate that no cleaning is required.
- the data structures of FIG. 5B show that, for employee type “4”, the protocol identifier has a value of “0”, or no cleaning is required.
- a particular employee record 340 may include other fields such as, for example, a user's department, an auto-assigned system identification number, a RFID number, a user identification number, one or more contact telephone numbers, and/or a contact email address.
- the choice of data fields used in a particular employee record 340 will vary depending on the context and the requirements that are particular to each use of the present invention.
- the employee record 340 may be an instance of a global employee record maintained centrally at the administration computer 104 . Accordingly, the administration computer may periodically access and/or update a plurality of instances of employee records 340 associated with each cleaning station 100 a - 100 n in order to maintain a comprehensive employee record.
- the employee use record 340 or data described herein as being associated with the employee use record 340 may be stored in the RFID tag 208 worn by the user 204 .
- a list of the user's 204 allergies may be stored in his or her RFID tag 208 and read by the RFID reader 212 when the user 204 washes his or her hands.
- Embodiments of the present invention may include operation of a consumables authentication module 324 that operates to recognize when a non-authorized solution is introduced into the system.
- the consumables container 228 and/or a receptacle or fitting associated with the cleaning station 100 a for receiving the consumables container 228 may be mechanically designed to discourage introducing non-authorized solutions to the system.
- the consumables container 228 includes a consumable container RFID tag 232 that is recognized by the RFID reader 236 as an approved solutions container.
- the RFID reader 236 will recognize the tag as invalid and warn the user 204 through the video display 224 and/or the administrator through the administration computer 104 that this is not acceptable and potentially void the product warranty.
- the cleaning station 100 a will stop functioning at the direction of the consumables authentication module 328 until a proper consumables container 228 with a valid RFID tag 232 is inserted into the cleaning station solution receptacle 230 .
- the known number of doses or applications of the consumable material may be associated with a valid RFID tag 232 and monitored by the consumables authentication module 328 so that once the number of applications is reached (and thus the consumable expended) the cleaning station 100 a cannot be used until another valid consumables container 228 is installed.
- the consumables container 228 contains enough cleaning fluid for approximately 500 hand-washing cycles. Once the cleaning station 100 a has administered approximately 500 hand-washing cycles using a particular consumables container 228 , then this container will no longer be operable with the cleaning station 100 a.
- the consumable container 228 may be identified by a bar code and bar code reader.
- the present invention may include modules that perform other functions such as collecting and reporting maintenance data; reporting information on the last recorded information transfer; and/or reporting the cleaning station's name, type, IP address and current software version.
- Administration computer 104 includes a processor 600 , a memory 604 and signaling interfaces 608 and 612 operable to communicate with external electronic and/or computational components.
- the first signaling interface 608 operates to communicate with the cleaning stations 100 a - 100 n over communication links 108 a - 108 n, as described above.
- the second signaling interface operates to communicate with the various input 616 and output 620 devices associated with the administration computer 104 .
- the input device 616 may be, for example, a keyboard or a mouse.
- the output device 620 may be, for example, a monitor or a printer.
- the memory 604 includes a plurality of stored program applications or modules that implement various features of a compliance monitoring system.
- the memory 604 may include a data retrieval module 624 and a custom report module 628 .
- the memory 604 may include data structures 632 associated with the various modules.
- the data structures 632 may include an employee record 636 and/or a compliance report 640 .
- the memory 604 may include database structures implemented using suitable database software (such as SQL Server Express).
- the data retrieval module 624 operates to retrieve data associated with cleaning stations 100 a - 100 n. Such data may include data related to cleaning station usage and/or employee specific data. The data may be contained in a cleaning station-use record 336 and/or an employee record 340 associated with a cleaning station 100 a - 100 n. Additionally, the data retrieval module 624 may operate to maintain a global employee record 636 as described above.
- the custom report module 628 operates to generate the compliance report 640 .
- the compliance report is generated from data contained in each station-use record 336 associated with cleaning stations 100 a - 100 n.
- An exemplary compliance report is shown in FIG. 7 .
- an entry in the compliance report 640 may include an employee name 700 , time stamp 704 indicating when a cleaning cycle was initiated, the date 708 of the cleaning cycle, the location 712 where the cleaning cycle took place, and a compliance indicator 716 specifying whether or not the user 204 met the compliance requirement.
- the compliance report shown in FIG. 7 indicates that on May 21, 2006 Janet Smith met the hand-washing requirement by completing a cleaning cycle that was initiated at 8:00.00 A.M at cleaning station A.
- compliance reports may include data pertaining to user statistics. Alternatively, or in addition to reports comprising user statistics, reports may be generated that are directed to the consumables, such as soap and disinfectants.
- the compliance report 640 may be generated at different time intervals and may be grouped based on different criteria. For example, the compliance report may be generated daily, weekly, monthly, yearly, et cetera. Moreover, the compliance report 640 may be generated that are grouped by individual or station.
- FIG. 8 shows a block diagram illustrating the steps of a method of monitoring a compliance requirement.
- a user 204 approaches a cleaning station 100 a and presents a badge having a RFID tag 208 to an RFID reader 212 .
- the RFID tag 208 is read and the user 204 is identified.
- the user's 204 name, the date, the time, and the location of the cleaning station 100 a are recorded.
- a cleaning cycle is initiated when the user 204 places her or his hands in position to be washed.
- the user 204 is provided with educational or entertainment content through the video display 224 .
- the wash cycle is completed and data is recorded including the duration of time the user 204 allowed his or her hands to be washed.
- the transaction is completed and recorded.
- data is collected from the cleaning stations 100 a - 100 n over the communication links 108 a - 108 n. In particular, data may be routed to a central collection point or FTP folder.
- the collected data is used to generate a compliance report 640 .
- Additional steps associated with the method may include: monitoring proper use of consumables; warning that an improper consumables container 228 has been installed; warning that a consumables container 228 is empty or nearly empty based on the number of uses since being installed; and warning that none or more users are failing to meet compliance requirements.
- a web-enabled hygiene monitoring system is provided.
- the system 900 includes a plurality of discrete monitored entities 904 a,b - w , each comprising first, second, . . . xth; first, second, . . . yth; or first, second, . . . jth washing stations 100 a - x , 100 a - y or 100 a - j , respectively, a compliance data hub 912 , a compliance monitor 916 a,b - p , and a compliance filter 920 , all interconnected by a data network 924 .
- the entities 904 a,b - w are each a monitored location. Particular monitored entities may be discrete facilities of a common monitored enterprise.
- the compliance data hub 912 may monitor a network of hospitals or restaurants. Referring to FIG. 9A , the monitored entities 904 a and 904 b represent different locations associated with a common business enterprise 906 . Alternatively, a monitored enterprise may include only one monitored entity. In FIG. 9A , monitored entity 904 w represents a separate business enterprise.
- the compliance data hub 912 may be associated with a plurality of business enterprises that are owned and operated by different companies, and one or more of those enterprises may include a plurality of different locations or facilities. Examples of enterprises include health care providers, food service providers (e.g., restaurants), food and/or drink manufacturers (e.g., meat packing plants, dairy product manufacturers, and the like), and other types of providers subject to internal and/or regulatory cleaning requirements.
- each monitored entity 904 network includes an administration computer 104 a,b - w or data collection point that collects cleaning information from each washing station 100 a - x, a - y, a - j in the corresponding enterprise network and, periodically or continually, provides the information to the compliance server 932 (shown in FIG. 9B ) of the compliance data hub 912 .
- an administration computer may be a network computer or server and may include a database.
- the cleaning information may be pushed by the administration computer 104 a,b - w to the compliance server 932 or pulled from the administration computer 104 a,b - w by the compliance server 932 .
- configuration of the each monitored entity 904 a,b - w substantially corresponds to the embodiment of the present invention shown in FIG. 1 .
- Each administration computer 104 a,b - w may include a user interface through which employee related data may be entered.
- the user interface may be implemented using any suitable software package (such as Access 2003) and can include portions that are icon driven to facilitate data entry and include drop down menus to ensure consistency of data. Additionally, data may be dynamically saved when possible.
- the user interface may include a plurality of screens wherein data is saved after a screen is changed. When changing screens, a user may be prompted to enter data not previously saved. Moreover, mandatory data fields may be supported for a software versions.
- the washing stations 100 a - x, a - y, a - j can be any type of cleaning equipment and are typically at different spatial locations in the monitored entity.
- washing stations include manual and automated body member (e.g., hand, foot, etc.) and other object washing stations, such as automated hand washers, sinks/faucets and cleaning solution dispensers, and the like.
- object refers to living or animate organisms, such as people and animals, as well as inanimate objects or entities, such as equipment and tools.
- each monitored entity 904 a,b - w has a corresponding unique monitored entity identifier
- each washing station 100 a - x, a - y, a - j has a unique station identifier.
- each pairing of monitored entity and station identifiers is unique.
- an object type identifier (not shown) is used in addition to the employee type identifier.
- the object type identifier refers to animate and inanimate objects, each of which has a unique or substantially unique identifier. While the identifier is carried removably by persons, the identifier may be attached permanently or semi-permanently to the inanimate object.
- the identifier can be, for example, a passive RFID tag, a bar code label, and the like.
- employee identifiers which, for an enterprise, are unique
- inanimate object identifiers may not be unique for each individual object in the enterprise but unique for a class of objects of the same type.
- objects of the same type have a common identifier, while objects of different types have different identifiers.
- Each washing station 100 a - x, a - y, a - j includes a compliance module 316 that in turn includes a processor and computer readable storage medium.
- the compliance module 316 identifies objects to be cleaned, determines a suitable cleaning protocol for the object to be cleaned, records object identifiers, object type identifiers, cleaning protocol identifiers, timestamps, compliance indicators, alert instances, and the like, determines the compliance or noncompliance of a cleaning, and generates appropriate alerts.
- each washing station 100 a - x, a - y, a - j can further include modules to determine whether the operational status of the corresponding washing station or a component thereof.
- the operational status includes not only whether the washing station or a component thereof is fully or partly operational or nonoperational, but also quantitatively a current level or remaining amount of a consumable item, such as soap or a cleaning/antimicrobial solution, or qualitatively whether the consumable level falls below a threshold level.
- Each module 316 may be associated with a memory 304 that typically includes a record or lookup table listing, by employee identifier, a corresponding cleaning protocol identifier.
- the compliance data hub 912 generally collects, stores, and analyzes cleaning information from the various administration computers 104 a,b - w .
- the administration computers 104 a,b - w having collected hand-washing data from the individual cleaning stations 100 a - x, a - y, a - j .
- the compliance data hub 912 includes a compliance server 932 for receiving cleaning information and forwarding the cleaning information to an appropriate storage location in the compliance data hub 912 , and for retrieving requested cleaning information from an appropriate storage location and forwarding the information to an authorized and verified entity, such as compliance monitor 916 a,b - p .
- the compliance data hub 912 further includes one or more databases 936 a - n for storing cleaning information and a Local Area Network 940 interconnecting the databases with the server 932 .
- the databases 936 a - n may be separate, as shown, with each database corresponding to a monitored entity 904 a - n or a single database partitioned into segments, one segment for each monitored entity 904 .
- the databases 936 a - n may be implemented using suitable database software (such as SQL Server Express).
- the various administration computers 104 a,b - w associated with the various monitored entities may support modules that communicate with compliance data hub 912 .
- it may by necessary to import a license token from the compliance data hub 912 in order to enable modules used at the administration computer level.
- the token may be specific to a particular enterprise and may include: the company name, a primary contact and primary contact information, a secondary contact and secondary contact information, the number of licensed users, and the type of service supported.
- the token may be an encrypted string of text that will be delivered as a token license file.
- the compliance data hub 912 may periodically access and/or update modules at the administration computer level.
- an email may be generated providing notice that a particular module was accessed or updated.
- the compliance server 932 includes a data management module 944 that queries administration computers 104 a,b - w for cleaning information, forwards received cleaning information to an appropriate database 936 for storage, receives requests for cleaning information and, after successful authentication and verification of the request source, retrieves and forwards the requested cleaning information to the requesting source, and analyzes the cleaning information for instances of compliance and/or noncompliance events.
- a data management module 944 that queries administration computers 104 a,b - w for cleaning information, forwards received cleaning information to an appropriate database 936 for storage, receives requests for cleaning information and, after successful authentication and verification of the request source, retrieves and forwards the requested cleaning information to the requesting source, and analyzes the cleaning information for instances of compliance and/or noncompliance events.
- the data management module 944 is operable to provide a data management module report.
- An exemplary data management module report 1000 is shown in FIG. 10 .
- the data management module report 1000 may include an enterprise identification number 1004 .
- the compliance data hub 912 may assign a unique enterprise identification number 1004 to each business enterprise monitored by the compliance data hub 912 .
- the enterprise identification number 1004 having a value “123456”, as shown in FIG. 10 may be associated with the business enterprise 906 shown in FIG. 9A .
- a particular compliance data report 1000 may be provided in connection with a particular business enterprise and will typically not include compliance data associated with other entities monitored by the compliance data hub 912 .
- monitored entity 904 w which is not part of business enterprise 906 , would be associated with a different enterprise identification number 1004 . Accordingly, compliance data associated with the monitored entity 904 w would not appear on the exemplary compliance data module report shown in FIG. 10 .
- the data hub 912 may maintain a contacts module operable to store and track contact information associated with each monitored business enterprise.
- the data management module report 1000 may additionally include a station identification number 1008 and a user identification number 1012 .
- the station identification number 1008 indicates the particular washing station where the washing took place.
- the user identification number 1012 is associated with a particular individual, such as an employee. Accordingly, for a particular entry in the report the user identification number indicates who used the washing station.
- Each entry in the report 1000 includes a date 1016 and time 1020 indication when the washing took place.
- a facility identifier 1024 may also be included if the monitored enterprise associated with the report 1000 includes more than one location or facility. The facility identifier 1024 may indicate in which facility within a particular enterprise the washing took place.
- the report also includes an indication 1028 of whether or not a complete wash cycle wash performed.
- the data management module report 1000 may include a compliance monitor identification number 1032 .
- the compliance monitor identification number 1032 may be used to indicate which compliance monitor 916 a,b - p of a plurality of compliance monitors 916 a,b - p is currently receiving or will be receiving compliance data associated with a particular item in the data management module report 100 .
- the compliance monitor identification number 1032 may be used by the compliance filter 920 in connection with determining which data items in the data management module report will be sent to the compliance monitors 916 a,b - p .
- a particular report may include other fields not shown in FIG. 10 .
- the report may include a wash station name or a wash station IP address.
- Data management module reports 1000 may be generated at different time intervals and may be grouped based on different criteria. For example, reports 1000 may be generated daily, weekly, monthly, yearly, et cetera. Moreover, reports 1000 may be generated that are grouped by individual, company, facility, station, et cetera.
- the compliance hub 912 may allow particular individuals to access stored data and/or reports including the data management module report 1000 .
- a report 1000 may be accessed remotely through a web interface.
- web user 948 with proper access permission, can access compliance data stored in the compliance data hub 912 .
- Particular individuals given access to stored data may include, for example, company managers and/or officers.
- a report may be provided to a compliance monitor 916 a,b - p.
- Access to data management module reports 1000 and other stored data may be limited and/or controlled by a security system.
- the data compliance hub 912 may include a group security module that provides a password protected control to stored data.
- the level of access allowed to a particular individual may be based on their membership in a particular group.
- Particular groups can include, for example, account manager, customer, demo, administration, data hub administration, and developer.
- Particular functions such as view, store and print may be useable based on the level of access granted.
- the compliance data hub 912 can perform a variety of data processing functions.
- the compliance data hub 932 can compare cleaning information, or a given sensed parameter, to identify events, temporal trends, or differences and, if necessary, generate appropriate alarms.
- the alarms can be logged internally and/or forwarded to the respective cleaning station 100 a - x, a - y, a - j .
- the cleaning station 100 a - x, a - y, a - j can then provide the alarm or warning to the appropriate cleaned object that, for instance, the cleaning provided was not compliant.
- An exemplary alarm may be “Successful Cleaning”, “Warning Cleaning Failed”, and the like.
- the compliance data hub 912 can also provide communications to the cleaning stations.
- the communications can, for example, be audio and video information for display to users of the stations.
- the audio and video information may be streaming media transmitted over the data network 924 , including, but not limited to, video transmitted to video display 224 .
- the databases 936 further include, or reference, information collected and stored by the enterprise security system (not shown).
- employee badge activated entrances typically collect the badge identifier (or employee identifier) and a timestamp when the badge identifier was received.
- Such information can be used in analyzing compliance by determining whether the employer having the sensed badge identifier used the washing station in temporal proximity to passing through the secured entrance.
- the spatial locations of activated entrances and washing stations are known and can be used, collectively, to monitor compliance.
- the one or more compliance monitors 916 a,b - p may be, for example, an entity responsible for monitoring and/or otherwise administering the hygiene policies and/or requirements of the one or more enterprises associated with the monitored entities 904 .
- the monitor may be a governmental entity, such as a department of health and human services and the U.S. Food and Drug Administration, to name but a few, or a private entity such as a hygiene administration department.
- a plurality of compliance monitors 916 a,b - p are involved, with each monitor being associated with a different local, state, or national (federal) government entity.
- a facility of an enterprise 906 may need to report compliance data to multiple compliance monitors 916 a,b - p , such as at the city or municipality, county, state, and federal levels.
- a compliance filter 920 may be used.
- the compliance filter 920 receives outgoing transmissions of cleaning information and filters the information before it is provided to one or more of the compliance monitors 916 a,b - p .
- the compliance filter 920 may be part of or separate from (as shown) the compliance data hub 912 .
- the compliance filter 920 ensures that cleaning information from different monitored enterprises 906 is not intermixed and only necessary cleaning information is provided to the compliance monitor 916 a,b - p , thereby protecting client/customer confidentiality and legally recognized privileges.
- the compliance filter 920 is a law firm responsible for and knowledgeable about compliance monitoring requirements. Attorneys may review the cleaning information and maintain the confidentiality of the cleaning information under the attorney-client privilege.
- the compliance filter 920 is an auditing entity other than a law firm.
- the data network 924 can be any circuit- or packet-switched network, with a packet-switched network, such as the Internet or World Wide Web, being preferred.
- the cleaning information is typically converted into a selected form, packetized, and transmitted over the network 924 .
- the form of the information can be in accordance with any selected language, such as the eXtensible Markup Language or XML, the HyperText Markup Language or HTML, Remote Method Invocation or RMI, or Direct Socket Connections.
- the packets can be transported using any suitable protocol, such as the Transport Control Protocol/Internet Protocol suite of protocols, Simple Object Access Protocol, or User Datagram Protocol.
- step 1100 the compliance module 316 of a selected washing station 100 identifies an object within range of the sensor. For example, an RFID tag identifier code associated with an animate or inanimate object is read by the RFID reader. Control then passes to step 1104 .
- step 1104 the sensed identifier code and a first timestamp are recorded by the module 316 .
- the first timestamp is indicative of the start time of the cleaning or washing cycle.
- the actual time that the cleaning cycle is commenced is sensed by a suitable sensor, such as an infrared sensor, motion sensor, or other type of optical or electromagnetic sensor, and recorded.
- the module 316 maps the sensed identifier code against the lookup table of FIG. 5B and determines, for the sensed identifier code, a corresponding value for the cleaning protocol to be employed. The module 316 then configures the corresponding washing station 100 for performing the cleaning steps required by the protocol.
- step 1112 under the control of the module 316 the washing station 100 cleans the identified object according to the requirements of the cleaning protocol.
- the washing station 100 provides audible or visual instructions to the identified object or to an operator cleaning the identified object regarding the protocol requirements and senses when the various protocol steps are performed.
- the module 316 records the sensed identifier and a second timestamp when one or more steps of the cleaning protocol is/are completed or, if the cleaning protocol steps are not completed, when the object to be cleaned is no longer within range of a sensor (e.g., the RFID reader or infrared sensor) of the washing station 100 .
- the module 316 further records, for the sensed identifier, the protocol identifier for the corresponding protocol, and a compliance indicator (e.g., whether the protocol was successfully or unsuccessfully completed before the sensed identifier left sensor range).
- step 1120 an appropriate alert is generated depending on whether the protocol was successfully or unsuccessfully completed.
- the alert or warning can be provided to the object by the washing station 100 .
- the module 316 determines whether collected compliance data or cleaning information should be uploaded to the data network 924 for transmission to the compliance server 932 .
- the trigger for uploading the information could be, for example, time-based, based on the number of washings performed by the corresponding station, or based on the available or unavailable memory capacity of the module 316 in the corresponding station.
- the trigger could be the receipt of a request from the server 932 for the information.
- the module 316 When the collected compliance data is to be provided to the server 932 , the module 316 generates one or more signals containing the data and includes, in each signal, the monitored entity identifier of the corresponding monitored entity (e.g., the identifier of the enterprise operating the washing station 100 ) and station identifier of the washing station 100 performing the cleaning. As noted, the monitored entity identifier is unique among the monitored entities, and the station identifier among the various stations 100 operated by the corresponding monitored entity. The signal(s) are then forwarded to the compliance server 932 .
- the monitored entity identifier e.g., the identifier of the enterprise operating the washing station 100
- station identifier of the washing station 100 performing the cleaning.
- the signal(s) are then forwarded to the compliance server 932 .
- the data management module 944 based on the enterprise identifier, forwards the signals to the appropriate compliance database 936 , or storage location(s), for storage and analysis. As will be appreciated, the module 944 maps the monitored entity identifier against a lookup table indexing monitored entity identifiers against database address and/or storage address range. The received information is then forwarded to an interface for the corresponding database for storage. The table is further used to retrieve compliance data for an identified, monitored entity.
- the data management module 944 and/compliance filter 920 use location information to identify appropriate compliance monitor(s) 916 a,b - p to which to report, to configure collection parameters, and/or to configure compliance reports for transmission to the identified compliance monitor(s) 916 a,b - p .
- the location information can be in many different forms. For example, each monitored facility of a common enterprise or each monitored enterprise is assigned geographical information indicating the physical location of the monitored entity. In another example, each monitored facility of a common enterprise or each monitored enterprise is assigned geopolitical information indicating the regulatory jurisdiction or political location of the monitored entity. By way of illustration, the political location of the facility would identify each compliance monitor 916 a,b - p to which activities at the facility must be reported.
- each washing station is assigned geographic and/or geopolitical information.
- each washing station has an embedded location module, such as a GPS or other satellite enabled locating device, which provides location coordinates. In this example, as the washing station is moved from one facility to another the location information is changed dynamically.
- the data management module 944 determines the corresponding monitoring and reporting requirements for the pertinent compliance monitor(s) 916 a,b - p . This is typically done using a lookup table, such as that shown in FIG. 12 .
- the geographic location information 1200 is mapped against compliance monitor 1202 , compliance data required 1204 , required reporting frequency 1208 , and reporting requirements 1212 .
- the geographic location information 1200 refers to the expression of geographical and/or geopolitical location used to signify the location of the monitored entity.
- the geographic location information 1200 can be satellite-enabled location coordinates, compliance monitor identifiers, city identifiers, county identifiers, state identifiers, country identifiers, and the like.
- the compliance monitor designation 1202 identifies the compliance monitor 916 a,b - p to which compliance reports are to be provided.
- the values in column 1202 can be values associated with the compliance monitor 916 a,b - p (which may be an electronic address).
- Compliance data required 1204 refers to the information to be collected to comply with requirements of the identified compliance monitor. Compliance data required 1204 includes, for example, a number of required washes/station, percent compliance (determined on a suitable basis), number of required washes/employee, and the like.
- the required reporting frequency 1208 refers to how frequently compliance data/reports are to be forwarded to the identified compliance monitor. The frequency, for example, can be daily, weekly, monthly, yearly, and the like.
- report requirements 1212 refer to requirements for the compliance information provided to the identified compliance monitor.
- Report requirements 1212 can refer to how the compliance data is to be transmitted to the monitor (e.g., by email, by mail, by upload/download operation over the data network 924 , and the like), the formatting and organizational requirements for the report, the entities associated with the monitor to whom the information is to be provided and each entity's address information, and the like.
- Other information in column 12 includes whether the information is to be encrypted and, if so, what key(s) are to be employed, the human or computer language in which the report is to be expressed (e.g., German, English, HTML, XML, and the like), and the like.
- a scheduling module (not shown) generates an interrupt identifying one or more compliance monitors 916 a,b - p requiring compliance report(s) to be provided.
- the interrupt is received by the data management module 944 .
- the module 944 determines the location information associated with a selected one of the compliance monitors referenced in the interrupt. This can be done by mapping an identifier of the selected compliance monitor against a listing of location information regulated or serviced by the selected compliance monitor 916 a,b - p.
- the module 944 determines, based on the geographic location information 1200 , each of the monitored entities 904 a,b - w monitored by the selected compliance monitor and, based on the geographic location information 1200 a monitored entity identifier for each of the identified entities, the compliance data required 1204 .
- the module 944 retrieves the required compliance data. This is typically done iteratively on an enterprise-by-enterprise basis to avoid intermixing compliance data for different enterprises. Compliance data may be collected by querying the appropriate one of the first, second, . . . nth databases 936 a - n and/or obtaining compliance information from each of the first, . . . xth washing stations 100 a - x at the subject facility for each identified enterprise.
- step 1316 the module 944 determines the reporting requirements 1212 for the selected compliance monitor.
- the module 944 uses the reporting requirements and compliance data obtained, generates and sends the report to the compliance filter 920 and/or directly to the compliance monitor 916 a,b - p .
- the filter 920 can remove unnecessary information collected by the washing stations and forward the filtered report to the compliance monitor 916 a,b - p.
- the module 944 determines whether the interrupt identified a next compliance monitor. If not, control returns to step 1300 . If so, the next compliance monitor is selected, and the module returns to step 1304 .
- An automated washing compliance verification system provided in association with a plurality of enterprise networks, the system comprising:
- a compliance data hub including a memory, the memory comprising:
- the data management module is operable to produce a data management report including compliance data collected in at least one enterprise network of the plurality of enterprise networks.
- each enterprise network has a corresponding unique enterprise identifier and wherein each storage location is associated with a different enterprise identifier.
- each washing station has a corresponding station identifier, with each station identifier being unique in the enterprise network containing the washing station.
- each object identifier has a corresponding protocol identifier and wherein at least one protocol identifier indicates that no cleaning be performed for the corresponding object identifier.
- a compliance filter operable to filter compliance data prior to the data being provided to the compliance monitor.
- each enterprise network includes a custom report module in communication with the data management module associated with the compliance data hub, each custom report module being enabled by a token imported from the compliance data hub, the token including at least one of:
- an identification apparatus operatively associated with the washing station, the identification apparatus operable to at least automatically identify at least one of:
- washing station operations monitor operatively associated with the cleaning station and the identification apparatus
- a memory associated with the washing station operations monitor comprising at least one of:
- a hygiene compliance verification system a computer readable medium comprising a set of data structures, the set of data structures comprising:
- the location information identifying at least one of a geographical and geopolitical location monitored by the compliance monitor.
- a compliance monitoring system for use with at least one hygiene station comprising;
- an electronic storage location for storing compliance data collected by the at least one hygiene station, wherein the compliance data comprises a plurality of different object identifiers and different protocol identifiers, each protocol identifier being associated with a different cleaning protocol, wherein each object identifier has a corresponding protocol identifier and wherein at least one protocol identifier indicates that no cleaning be performed for the corresponding object identifier.
- each enterprise network including at least one corresponding hygiene station
- each storage location being associated with a corresponding enterprise network and storing compliance data collected by the at least one corresponding hygiene station in the corresponding enterprise network.
- each enterprise network has a corresponding unique identifier and wherein each storage location is associated with a different enterprise identifier.
- each hygiene station has a corresponding station identifier, with each station identifier being unique in the enterprise network containing the hygiene station.
- the hygiene station comprises a sink and a faucet
- the compliance monitoring system further comprises at least one sensor at or proximate to at least one of the sink and the faucet.
- a compliance monitoring system comprising:
- each storage location corresponds to one enterprise network of the plurality of enterprise networks
- the compliance data report including compliance data received from a particular enterprise network of the plurality of enterprise networks.
- a method of performing hygiene compliance verification comprising:
- the hygiene compliance data report including hygiene compliance data received from a particular enterprise network of the plurality of enterprise networks.
- filtering prior to providing the hygiene compliance data report to the compliance monitor, filtering the hygiene compliance data, wherein filtering includes removing at least one data item from the hygiene compliance data.
- the cleaning station including an apparatus for automatically washing at least a portion of the user
- a method for reporting hygiene compliance comprising:
- a method for performing hygiene compliance verification comprising:
- An electronic hygiene compliance verification data signal comprising:
- the hygiene compliance information comprises hygiene compliance data received from a particular enterprise network of a plurality of enterprise networks, the particular enterprise network associated with the enterprise identifier, the plurality of enterprise networks including at least a second enterprise network, wherein the second enterprise identifier is associated with the second enterprise network.
- the hygiene compliance information includes information associated with a hygiene station comprising a sink and a faucet, wherein the hygiene station further comprises at least one sensor at or proximate to at least one of the sink and the faucet.
- the hygiene compliance information includes information associated with a hygiene station comprising an automated cleaning station, wherein the hygiene station further comprises at least one sensor at or proximate to the automated cleaning station.
- the present invention in various embodiments, includes components, methods, processes, systems and/or apparatus substantially as depicted and described herein, including various embodiments, subcombinations, and subsets thereof. Those of skill in the art will understand how to make and use the present invention after understanding the present disclosure.
- the present invention in various embodiments, includes providing devices and processes in the absence of items not depicted and/or described herein or in various embodiments hereof, including in the absence of such items as may have been used in previous devices or processes, e.g., for improving performance, achieving ease and ⁇ or reducing cost of implementation.
Abstract
A system is provided for providing automated washing and verifying compliance of use. The system provides for identifying individual users of one or more cleaning stations through various technologies, such as RFID. Individual's use of cleaning stations is monitored to determine compliance with hand-washing requirements. A compliance report may be generated based on data associated with one or more individuals' use of the cleaning station(s). Educational and/or entertainment content may be displayed to the user when he or she is using the cleaning station. Additionally, the cleaning station may identify containers having authorized consumables such as soap or disinfectant. Optional automated collection and forwarding of hygiene compliance information is performed to provide compliance monitors, such as a regulatory agency, with such information.
Description
- This application claims the benefit of U.S. Provisional Application No. 60/863,753, filed Oct. 31, 2006 and the benefit of U.S. Provisional Application No. 60/909,280, filed Mar. 30, 2007 the entire contents of both applications are incorporated herein by reference in their entirety.
- The present invention relates to automated washing systems, and more particularly, to automated washing systems comprising a way of monitoring and/or verifying user participation. Methods of providing compliance verification are also provided.
- The importance of cleanliness has long been recognized, particularly in the fields of heath-care, food preparation, and laboratories, to name but a few. The practice of surgical scrubbing by surgeons and other operating room personnel is probably the epitome of efforts to cleanse the hands and forearms of persons working in sterile environments. Although manual hand-washing can appear effective, medical experts have concluded that automated hand-washing increases hand-washing compliance and reduces the risk of infection.
- Touchless automated hand-washing devices are designed to wash the hands of the user and provide the proper amount of antimicrobial solution in a set time. Additionally, these systems diminish the deterrent effects of friction and irritation associated with frequent manual hand-washing. Notwithstanding the benefits and convenience of automated washing devices, difficulties still exist with verifying employee or staff use of the washing apparatus. Accordingly, it would be advantageous to have a system that provides automated washing with a way of verifying usage by the intended users.
- In addition to the foregoing, problems also exist with verifying that the proper soap solutions or disinfectants are being used in a cleaning station. In addition, problems exist with assessing whether a user has an allergy where the user should not use a certain type of soap or disinfectant provided in a cleaning station. In addition, problems exist in providing a solution in a cleaning station to avoid an allergy of a user. Also, problems exist in providing user specific formulations that address, for example, the user's specific job duties. In addition, problems exist in motivating users to stay at a cleaning station for its entire cleaning cycle. Also, problems exist in providing information to a manager or administrator regarding monitoring one or more cleaning stations, wherein the monitoring may include review of data directed to addressing one or more of the above noted problems.
- U.S. Pat. No. 7,015,816, U.S. Pat. No. 6,727,818 and United Stated Patent Application Publication No. 2006/0132316 are directed to systems that in part address the problems outlined above. The summary of each document indicates that the disclosed systems are directed to monitoring or gathering information on locations of person, equipment, and/or activities associated with a facility. The gathered information is used to evaluate compliance with hygiene requirements as defined by a hygiene policy for a facility. These systems suffer from several drawbacks including facility (e.g. hospital) liability concerns introduced by the disclosed monitoring methods. These systems also make no allowance for people with no hand-washing requirements such as visitors to the facility. Additionally, these systems include a burdensome system of in/out zones, do not provide for automatic reporting, and do not include hand-washing requirements that are specific to a person's job title. Furthermore, these systems do not disclose a system for automatically providing hygiene compliance information to a regulatory body. These shortcomings are addressed by the various embodiments of the present invention.
- In accordance with embodiments of the present invention, a Radio Frequency Identification (“RFID”) system is disclosed for use in connection with an automated hand-washing station. However, as described herein, other identifying technologies are appropriate, and such technologies are encompassed by the scope of the present invention. Examples include bar codes, biometric technology and the like. It is to be understood therefore, that RFID is used as an example and is not intended to limit the scope of the present invention.
- The system is operable to record and report on user compliance with hand-washing requirements. To ensure user safety and product performance, the system has the capability to ensure that only authorized consumable solutions are used in the cleaning station. The RFID data capture capability, in conjunction with a video system, allows users to have real time feedback of their personal compliance as well as individual user focused information conveyed at the time of utilizing the cleaning station.
- In accordance with one or more embodiments described herein, the user carries a RFID tag that is programmed with information specific to the individual. Upon approaching the cleaning station, an RFID reader recognizes the user's tag and records the user name, time, date, station location, and whether the cleaning event was a complete cycle. The data is stored in the readers' database until captured via various methods and transferred into a report format for the administrator. The administrator can then review the compliance statistics for the various users.
- In a separate aspect of the invention, and in accordance with one or more embodiments described herein, the RFID system is well suited to monitoring whether a consumable item used in the cleaning station is authentic or not authorized. Upon detection of an improper consumables item the cleaning station may deactivate. An RFID tag is attached to the consumable product, such as a cleaning solution bottle. When installed in the cleaning station, the tag attached to the solution bottle will confirm to the RFID system by way of the unique tag identifier that the subject bottle contains an authorized solution. Without this verification, a user of the station may inadvertently use another solution that is harmful to the user or ineffective for the use intended. Another benefit is that an authorized solution will be at the correct viscosity to ensure the proper dosage is used in the wash cycle and the mechanical action of the station will not be compromised by plugged fluid nozzles and lines.
- Embodiments of the present invention include methods of providing compliance or non-compliance information regarding hygiene efforts. By way of example and not limitation, a method for performing hygiene compliance verification is provided, comprising:
- (a) receiving an object identifier;
- (b) determining a cleaning protocol from a plurality of different protocols to be used on an object associated with the object identifier; and
- (c) implementing the cleaning protocol in connection with the object.
- Other methods are also encompassed by the present invention. By way of example and not limitation, a method of performing hygiene compliance verification is provided, comprising: receiving hygiene compliance data associated with a plurality of enterprise networks, each network being associated with a different enterprise comprising one or more automated sensors; storing the hygiene compliance data; and providing at least one hygiene compliance data report, the hygiene compliance data report including hygiene compliance data received from a particular enterprise network of the plurality of enterprise networks.
- Computer readable medium operable to perform the steps of any of the methods described herein are encompassed by the present invention.
- Various signals, such as, by way of example and not limitation, a data signal associated with a carrier wave, that include at least one piece of hygiene compliance information are encompassed by the present invention. By way of example and not limitation, an electronic hygiene compliance verification data signal is provided, comprising:
-
- (a) source and destination addresses;
- (b) hygiene compliance information; and
- (c) an enterprise identifier; and
- (d) a compliance monitor identifier.
- A variety of different ways of providing a compliance monitoring system are encompassed by the present invention. By way of example and not limitation, a compliance monitoring system is provided, comprising: means for receiving compliance data associated with a plurality of enterprise networks; means for storing the compliance data in a plurality of electronic storage locations, wherein each storage location corresponds to one enterprise network of the plurality of enterprise networks; and means for providing at least one compliance data report, the compliance data report including compliance data received from a particular enterprise network of the plurality of enterprise networks. Such system may further include means for providing the compliance data report to a web user, the web user having supplied a valid password. In addition, such system may further include means for providing the compliance data report to a compliance monitor.
- In a hygiene compliance verification system, and by way of example and not limitation, a computer readable medium comprising a set of data structures is provided, the set of data structures comprising:
-
- (a) a first set of information identifying a hygiene compliance monitor;
- (b) compliance data required to be reported to the compliance monitor; and
- (c) reporting requirements associated with the compliance monitor;
wherein the data structures are used to produce a data management report including the compliance data. The set of data structures may further comprise a reporting frequency required by the compliance monitor. The set of data structures may further comprise location information, the location information identifying at least one of a geographical and geopolitical location monitored by the compliance monitor.
- A variety of compliance monitoring systems are encompassed by the present invention. By way of example and not limitation, a compliance monitoring system for use with at least one hygiene station is provided, the system comprising:
- (a) a verification module; and
- (b) an electronic storage location for storing compliance data collected by the at least one hygiene station, wherein the compliance data comprises a plurality of different object identifiers and different protocol identifiers, each protocol identifier being associated with a different cleaning protocol, wherein each object identifier has a corresponding protocol identifier and wherein at least one protocol identifier indicates that no cleaning be performed for the corresponding object identifier.
- The system may further comprise a plurality of enterprise networks, each enterprise network including at least one corresponding hygiene station; and a plurality of electronic storage locations, each storage location being associated with a corresponding enterprise network and storing compliance data collected by the at least one corresponding hygiene station in the corresponding enterprise network.
- Embodiments of the present invention cover compliance verification of different forms of a hygiene station. By way of example and not limitation, one or more embodiments of the present invention are appropriate for monitoring associated with hygiene stations that comprise a sink and a faucet, automated cleaning stations, disinfection stations, sanitizer dispensers, sanitizer gel dispensers, lotion dispensers, hand soap dispensers, or other ancillary devices, et cetera.
- Other aspects of various embodiments not summarized here are also considered to form part of the present invention, either alone or in combination with other aspects. Accordingly, aspects may be claimed alone or in combination with other aspects.
- As used herein, “ at least one”, “one or more”, and “and/or” are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions “at least one of A, B and C”, “at least one of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B, or C” and “A, B, and/or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.
- It is to be noted that the term “a” or “an” entity refers to one or more of that entity. As such, the terms “a” (or “an”), “one or more” and “at least one” can be used interchangeably herein. It is also to be noted that the terms “comprising”, “including”, and “having” can be used interchangeably.
- The term “automatic” and variations thereof, as used herein, refers to any process or operation done without material human input when the process or operation is performed. However, a process or operation can be automatic even if performance of the process or operation uses human input, whether material or immaterial, received before performance of the process or operation. Human input is deemed to be material if such input influences how the process or operation will be performed. Human input that consents to the performance of the process or operation is not deemed to be “material”.
- The terms “determine”, “calculate” and “compute,” and variations thereof, as used herein, are used interchangeably and include any type of methodology, process, mathematical operation or technique.
- The term “module” as used herein refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and software that is capable of performing the functionality associated with that element. Also, while the invention is described in terms of exemplary embodiments, it should be appreciated that individual aspects of the invention can be separately claimed.
- Various embodiments of the present invention are set forth in the attached figures and in the detailed description of the invention as provided herein and as embodied by the claims. It should be understood, however, that this Summary does not contain all of the aspects and embodiments of the present invention, is not meant to be limiting or restrictive in any manner, and that the invention as disclosed herein is and will be understood by those of ordinary skill in the art to encompass obvious improvements and modifications thereto.
- Additional advantages of the present invention will become readily apparent from the following discussion, particularly when taken together with the accompanying drawings.
-
FIG. 1 is a block diagram of components that may be included in embodiments of the present invention; -
FIG. 2 is a schematic depiction of a cleaning station in accordance with embodiments of the present invention; -
FIG. 3 is a block diagram of a cleaning station operations monitor in accordance with embodiments of the present invention; -
FIG. 4 is an exemplary station-use record in accordance with embodiments of the present invention; -
FIG. 5A is an exemplary employee record in accordance with embodiments of the present invention; -
FIG. 5B shows a set of data structures according to an embodiment of the present invention; -
FIG. 6 is a block diagram of an administration computer in accordance with embodiments of the present invention; -
FIG. 7 is an exemplary compliance report in accordance with embodiments of the present invention; -
FIG. 8 is a flow chart depicting aspects of a method of monitoring hand-washing compliance in accordance with embodiments of the present invention; -
FIGS. 9A and 9B are a compliance monitoring system according to another embodiment of the present invention; -
FIG. 10 is an exemplary data management module report; -
FIG. 11 is a flow chart according to an embodiment of the present invention; -
FIG. 12 shows a set of data structures according to an embodiment of the present invention; and -
FIG. 13 is a flow chart according to an embodiment of the present invention; - The drawings are not necessarily to scale.
- The exemplary systems and methods of this invention will be described in relation to distributed processing networks. However, to avoid unnecessarily obscuring the present invention, the following description omits a number of known structures and devices. This omission is not to be construed as a limitation of the scope of the claimed invention. Specific details are set forth to provide an understanding of the present invention. It should, however, be appreciated that the present invention may be practiced in a variety of ways beyond the specific detail set forth herein.
- Furthermore, while the exemplary embodiments illustrated herein show the various components of the system collocated, certain components of the system can be located remotely, at distant portions of a distributed network, such as a LAN and/or the Internet, or within a dedicated system. Thus, it should be appreciated, that the components of the system can be combined in to one or more devices, such as a washing station, or collocated on a particular node of a distributed network, such as an analog and/or digital telecommunications network, a packet-switched network, or a circuit-switched network. It will be appreciated from the following description, and for reasons of computational efficiency, that the components of the system can be arranged at any location within a distributed network of components without affecting the operation of the system. For example, the various components can be located in a switch, media server, gateway, in one or more washing stations, at one or more users' premises, or some combination thereof.
- Furthermore, it should be appreciated that the various links connecting the elements can be wired or wireless links, or any combination thereof, or any other known or later developed element(s) that is capable of supplying and/or communicating data to and from the connected elements. These wired or wireless links can also be secure links and may be capable of communicating encrypted information. Transmission media used as links, for example, can be any suitable carrier for electrical signals, including coaxial cables, copper wire and fiber optics, and may take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
- Also, while the flowcharts have been discussed and illustrated in relation to a particular sequence of events, it should be appreciated that changes, additions, and omissions to this sequence can occur without materially affecting the operation of the invention.
- The present invention is directed to a system and method for ensuring employee compliance with washing requirements, such as hand-washing requirements. However, it is to be understood that embodiments of the present application are also applicable to other types of washing systems, including for example, boot-washing systems. In accordance with embodiments of the present invention, employee use of one or more automated cleaning stations is monitored. The cleaning stations operate to dispense one or more fluids, such as water, a cleaning fluid, such as soap, and/or a disinfectant, etc., while a person's hands are placed in a washbasin. As used herein, a “washbasin” means a structure associated with the cleaning station where the hands (or boots) are cleaned, such as one or more wash cylinders, spray areas, pans, tubs, etc. Employees may be instructed to wash their hands for a minimum amount of time that has been determined to be sufficient to provide a complete cleaning. The minimum time needed to provide a complete cleaning and/or the types of fluids, agents, and/or cleaning methods used in the automated cleaning may vary depending a variety of factors including the employee's job duties and/or his or her past noncompliance. The cleaning stations are operable to record and report data related to employee compliance with such requirements. At least some employees may not be required to wash their hands.
- For purposes of discussion, the various embodiments of the present invention are discussed herein in connection cleaning an appendage of a user. However, it should be understood that the various embodiments may be used in connection with other objects. As used herein an “object” may refer to anything cleaned by the automated cleaning station. An object may be, for example, an appendage of a user, a tool, a boot, and/or an inanimate object, etc. As used herein, “inanimate object” means an object that is principally not a biological tissue, although biological matter may be associated with the inanimate object, for example, a virus, bacteria, and/or pieces of tissue on a tool.
- Referring now to
FIG. 1 , components of a compliance system in accordance with embodiments of the present invention are illustrated in block diagram form. Shown inFIG. 1 is a plurality of cleaningstations FIG. 1 is anadministration computer 104 for use by a manager or administrator of the facility. Theadministration computer 104 is operable to generate a compliance report as described herein. As used herein, anadministration computer 104 may include a file server or other network computer operable to serve as a data collection point for data associated with cleaningstations 100 a . . . 100 n. Additionally, it should be understood that separate computational devices may be used to store data and to access the stored data. - The
administration computer 104 communicates with the cleaning stations 100 a-100 n over a plurality ofcommunication links administration computer 104 is located in a separate facility from one or more of the cleaning stations 100 a-100 n. In this case, a distributed data network such as the Internet may form part of the communication links 108 a-108 n. - Referring now to
FIG. 2 , anexemplary cleaning station 100 a is illustrated. The cleaningstation 100 a includes a cleaning station operations monitor 200. The cleaning station operations monitor 200 may comprise a computational device such as a general-purpose computer, controller, or ASIC that controls and coordinates the operation of the various electronic components associated with the cleaningstation 100 a. Additionally, the cleaning station operations monitor 200 is operable to record data associated with employee use of the cleaningstation 100 a and to report the data to theadministration computer 104. The cleaning station operations monitor 200 may be incorporated into the cleaningstation 100 a or, alternatively, may be implemented as a separate computing device. - Also shown in
FIG. 2 is auser 204 of the cleaningstation 100 a. Theuser 204 may be an employee or visitor who is required to wash their hands because of the nature of their work or the nature of the facility. Theuser 204 is shown wearing auser RFID tag 208. Theuser RFID tag 208 is programmed by an RFID tag programming device (not shown) with information such as an employee number that, when read, uniquely identifies the employee oruser 204. TheRFID tag 208 may be incorporated into an identification badge or bracelet worn by theuser 204. - In accordance with embodiments of the present invention, the cleaning
station 100 a includes anRFID reader 212 and anoptical sensor 216. TheRFID reader 212 is positioned so as to be able to read theuser RFID tag 208 when theuser 204 is washing his or her hands at the cleaningstation 100 a. TheRFID reader 212 may be incorporated into the cleaningstation 100 a or, alternatively, may be implemented as a stand-alone device. For example, theRFID reader 212 may be positioned adjacent to a cabinet associated with the cleaningstation 100 a. Theoptical sensor 216 is positioned so as to be able to sense that the hands of theuser 204 are placed within thewashbasin 220 in a position where they will properly receive cleaning fluids, such as water, soap and/or disinfectant as dispensed by the cleaningstation 100 a. TheRED reader 212 and theoptical sensor 216 are in communication with cleaning station operations monitor 200, which, in turn, is operable to collect data associated with these devices. In particular, data is collected from theRFID reader 212 indicating the identity of theuser 204. Additionally, the cleaning station operations monitor 200 records the length of time in which the hands of theuser 204 were placed in thewashbasin 220 as indicated by theoptical sensor 216. In addition to RFID, other methods of identifying a user are within the scope of the present invention. In particular, a user may be identified by means of a typed password, retinal scan, voice print, palm print, fingerprint, face identification, bar coding (on an employee ID), etc. - The cleaning
station 100 a also includes avideo display 224 positioned for viewing by theuser 204 when he or she is washing his or her hands. Thevideo display 224 may be incorporated in the cleaningstation 100 a or, alternatively, may be implemented as a separate device. For example, thevideo display 224 may be positioned on a wall in front of theuser 204 as they stand at the cleaningstation 100 a. Thevideo display 224 operates to display brief video segments to theuser 204 while the cleaningstation 100 a is cleaning his or her hands. Thevideo display 224 may be under the control of the cleaning station operations monitor 200. As theuser 204 is utilizing the cleaningstation 100 a, administrator-selected data is transmitted to thevideo display 224. This information may be simple feedback to theuser 204 informing them of the amount of hand washings they did in the current day, week, month, etc. In addition, there may be training programs that communicate information to theuser 204, such as the risks of hand borne pathogens, to constantly remind theuser 204 of the importance of hand hygiene. This system has the flexibility to provide a wide range of communications to theuser 204. - Also shown in
FIG. 2 is aconsumables container 228 that contains a material, such as soap or disinfectant used in connection with the operation of the cleaningstation 100 a. Although not shown, a plurality ofconsumable containers 228 may be associated with a cleaningstation 100 a. Theconsumables container 228 includes a detachable connection to aconsumable receptacle 230 associated with the cleaningstation 100 a so that theconsumable container 228 may be removed and disposed of when its contents are expended. After the disposal of a usedconsumables container 228, anew consumables container 228 is then attached to the cleaningstation 100 a. In accordance with embodiments of the present invention, theconsumables container 228 also includes aconsumables RFID tag 232 that contains information related to theconsumable container 228. Aconsumables RFID reader 236 associated with the cleaningstation 100 a reads theconsumables RFID tag 232 and communicates information related to theconsumables container 228 to the cleaning station operations monitor 200. Although RFID is discussed herein for use of identification of consumables, other types of identification systems may be used, such as bar codes. - Referring now to
FIG. 3 , a block diagram of components and features of the cleaning station operations monitor 200 is shown. As mentioned previously, the cleaning station monitor 200 is a computational device. Accordingly, the cleaning station operations monitor 200 includes aprocessor 300, amemory 304 and signalinginterfaces first signaling interface 308 operates to communicate with theadministration computer 104 over communication link 108 a, as described above. Thesecond signaling interface 312 operates to communicate with the various electronic components associated with the cleaningstation 100 a including theRFID readers optical sensor 216, and thevideo display 224. Thesecond signaling interface 312 may be a portion of a backplane incorporated into cleaningstation 100 a that includes a connection to the cleaning station's 100 a electronic components. Alternatively, if the cleaning station operations monitor 200 is implemented as a stand-alone computer, the cleaning station operations monitor 200 may communicate with the cleaning station's electronic components through a network or serial bus connection. - The
memory 304 includes a plurality of stored program applications or modules that implement various features of a compliance monitoring system. In accordance with embodiments of the present invention, thememory 304 may include a compliance-monitoring module 316, atraining module 320, aconsumables authentication module 324, and/or asolutions selection module 328. Additionally, thememory 304 may includedata structures 332 associated with the various modules. In accordance with embodiments of the present invention, thedata structures 332 include a station-use record 336 and one or more employee records 340. The operation of the various modules and data structures is described in greater detail below. - The compliance-
monitoring module 316 operates to monitor and record the activity of a plurality ofusers 204 of the cleaningstation 100 a. The process is outlined as follows. Theuser 204 approaches acleaning station 100 a with aRFID tag 208 on their person, which was programmed with a RFID tag programming device with the individual's name or number, and/or other pertinent data. Thetag 208 is read by theRFID reader 212 when theuser 204 approaches and/or begins using thecleaning station 100 a. When theuser 204 places his or her hands into the cleaningstation washbasin 220, theoptical sensor 216 initiates a cleaning cycle. If the hands of theuser 204 do not stay in thewashbasin 220 for the full cycle time, theoptical sensor 216 will indicate in thedata structure 332 that theuser 204 did not have a complete cleaning. Once the user is finished using thecleaning station 100 a, the data showing such items as user name, time, date, station location and/or identification, and whether the cycle was complete, etc., is stored in thedata structure 332. The stored data is later accessed by theadministration computer 104 in connection with the generation of a compliance report. - An exemplary station-
use record 336 having data associated with a plurality ofusers 204 is shown inFIG. 4 . In accordance with embodiments of the present invention, an entry in the station-use record 336 may include anemployee name 400 indicating who used the cleaningstation 100 a, atime stamp 404 indicating when the cleaning cycle was initiated, aduration 408 indicating how long theuser 204 kept his or her hands in thewashbasin 220, thedate 412, and acompliance indicator 416 specifying whether or not theuser 204 kept his or her hands in thewashbasin 220 for the required time. As an example, the station-use record shown inFIG. 4 indicates that on May 21, 2006 Janet Smith met the hand-washing requirement by completing a cleaning cycle that was initiated at 8:00.00 A.M. and that lasted for 10 seconds. In an alternative embodiment, the station-use record 336 may contain only raw data such as thetime 404,date 412 andduration 408 of the cleaning cycle while determinations related to compliance requirements are made by a separate module running on theadministration computer 104. - The compliance-
monitoring module 316 may also operate to monitor hand-washing requirements that are specific to each employee. Some employees may have stricter hand washing requirements than others at the same facility. For example, a hospital emergency room may employ both surgeons and social workers. As can be appreciated, the surgeons will be required to wash their hands more frequently and more thoroughly than the social workers. Accordingly, the compliance-monitoring module 316 may access employee records to determine the type, concentration, and/or amount of cleaning fluid to be dispensed for a particular employee. Additionally, employee records may contain other hand washing compliance data that is specific to each employee such as the amount of time and/or frequency that an employee is required to wash his or her hands. Washing requirements may also depend on an employee's history of compliance with his or her washing requirements. For example, an employee may be required to wash his or her hands more thoroughly if his or her previous hand washings were incomplete or hand not been wash for some period of time. - Embodiments of the present invention may include a
training module 320. In accordance with at least one embodiment of the present invention, thetraining module 320 operates to transmit educational information to theuser 204 while the cleaning cycle is running via sound and/or a visual source, such as avideo display 224. The information may comprise segments equal in duration, or slightly longer or shorter in duration than the cleaning cycle. For example, the segments may contain information regarding hand hygiene in a series of segments lasting approximately 10-15 seconds. In accordance with at least one embodiment of the present invention, theemployee record 340 portion of thedata structure 332 keeps track of theuser 204 and knows the sequence of training segments so each time auser 204 uses thecleaning station 100 a, the next pertinent training segment will display on thevideo display 224. - In accordance with at least one embodiment of the present invention, the
training module 320 may access theemployee record 340 to provide custom designed content in conjunction with the user's 204 needs/requests. Accordingly, as one possible alternative to educational/training content, entertainment content specific to the user's 204 preferences may be displayed. Here, other information is conveyed to the user, such as news (e.g., weather, breaking stories, current events, stock prices, etc.) and sports information. Thetraining module 320 may, therefore, accommodate specific requests to convey information of interest to the user. In at least one embodiment of the present invention, the information conveyed to the user may be anything other than information about a cleaning station function parameter (e.g., water pressure, soap level, etc.). That is, content other than information about the cleaning station operating parameters so that the user is interested in staying at the cleaning station for an entire wash cycle. - The
training module 320 may give feedback to theuser 204 through thevideo display 224, including such information as their hand-washing statistics over a given period of time. For example the administrator of a facility may want to encourage system usage by conveying one or more compliance statistics, and/or informing auser 204 that theuser 204 has won a prize by having high marks for compliance with the hand-washing protocol. Accordingly, theemployee record 340 may keep track of data associated withuser 204, and this data may be accessed by thetraining module 320 to inform theuser 204 in real time, and/or the administrator in a subsequent report, as to compliance statistics. Additionally, thevideo display 224 may be used to provide notices, such as for upcoming meetings and events that are pertinent to all staff or to a specific person. - The
solutions selection module 328 may determine which solution is to be used with eachindividual user 204. For example, oneuser 204 may have an allergy to the standard solution, so the system is programmed to automatically use a different and appropriate solution when thisuser 204 is identified through theirRFID tag 208. Information related to user allergies may be contained in theemployee record 340. - An
exemplary employee record 340 for use in connection with both thetraining module 320 and thesolutions selection module 328 is shown inFIG. 5A . In accordance with embodiments of the present invention, an entry in theemployee record 340 may include theemployee name 500, hand-washing 504 statistics associated with employee,current training segment 508 to be viewed by the employee, the employee'spreferred entertainment content 512, and/or a listing of the employee'sallergies 516. As an example, the employee record shown inFIG. 5A indicates that Bill Forbes is in 97% compliance with the hand-washing requirement, has currently viewed seven training modules, prefers to watch the news while washing his hands, and has an allergy to cleaning solution A. - In accordance with embodiments of the present invention, an employee record may include a lookup table that indicates a particular cleaning protocol that is to be applied to a particular employee. An exemplary lookup table 520 is shown in
FIG. 5B . The lookup table 520 includes a plurality ofemployee identifiers 524 and, for each employee identifier, a correspondingemployee type indicator 528 andcleaning protocol identifier 532. Theemployee identifier 524 is commonly an RFID or suitable wirelessly readable identification code. Theemployee type indicator 528 commonly references the job responsibilities and/or title/position of the identified employee. For example, in a caregiver application a “1” might refer to a nurse, a “2” to an imaging technician, a “3” to a doctor, and a “4” to a member of the janitorial staff. Alternatively or in combination, the particular individuals may be identified by a key code including a name or a job description. Thecleaning protocol identifier 532 refers to the particular cleaning protocol to be used for the corresponding identified employee. Typically, each cleaning protocol has a corresponding set of cleaning medium to be used, medium application duration, and wash duration. For example, cleaning protocol identifier “1” may require a ChlorHexidine Gluconate (“CHG”) wash, a “2” either a CHG wash or alcohol towelette or wipe, and a “3” a CHG wash followed by an alcohol wipe. Examples of other sanitizing solutions that may be used individually or collectively in cleaning protocol(s) include quaternary ammonium solutions. In one configuration, the cleaning protocol identifier is further varied based upon the location of the corresponding washing station, which is readily determined from the station identifier. A washing station in a highly hygiene sensitive area, such as an operating room, may provide a more demanding cleaning protocol than a station at a less hygiene sensitive area, such as a nursing station. In some cases, the cleaning protocol identifier may indicate that no cleaning is required. For example, the data structures ofFIG. 5B show that, for employee type “4”, the protocol identifier has a value of “0”, or no cleaning is required. - It should be understood that the data fields associated with the
exemplary employee record 340 discussed above and shown inFIG. 5A and the lookup table 520 shown inFIG. 5B are by way of illustration and not limitation. Aparticular employee record 340 may include other fields such as, for example, a user's department, an auto-assigned system identification number, a RFID number, a user identification number, one or more contact telephone numbers, and/or a contact email address. As can be appreciated, the choice of data fields used in aparticular employee record 340 will vary depending on the context and the requirements that are particular to each use of the present invention. - In accordance with embodiments of the present invention, the
employee record 340 may be an instance of a global employee record maintained centrally at theadministration computer 104. Accordingly, the administration computer may periodically access and/or update a plurality of instances ofemployee records 340 associated with each cleaning station 100 a-100 n in order to maintain a comprehensive employee record. Alternatively, at least a portion of theemployee use record 340 or data described herein as being associated with theemployee use record 340 may be stored in theRFID tag 208 worn by theuser 204. For example, a list of the user's 204 allergies may be stored in his or herRFID tag 208 and read by theRFID reader 212 when theuser 204 washes his or her hands. - Embodiments of the present invention may include operation of a
consumables authentication module 324 that operates to recognize when a non-authorized solution is introduced into the system. Theconsumables container 228 and/or a receptacle or fitting associated with the cleaningstation 100 a for receiving theconsumables container 228 may be mechanically designed to discourage introducing non-authorized solutions to the system. In accordance with embodiments of the present invention, theconsumables container 228 includes a consumablecontainer RFID tag 232 that is recognized by theRFID reader 236 as an approved solutions container. If theconsumables container 228 is withdrawn from the cleaningstation 100 a and reinstalled, theRFID reader 236 will recognize the tag as invalid and warn theuser 204 through thevideo display 224 and/or the administrator through theadministration computer 104 that this is not acceptable and potentially void the product warranty. Alternatively, or in addition thereto, an option is available where the cleaningstation 100 a will stop functioning at the direction of theconsumables authentication module 328 until aproper consumables container 228 with avalid RFID tag 232 is inserted into the cleaningstation solution receptacle 230. In yet another possible alternative and/or in addition to the options provided above, the known number of doses or applications of the consumable material may be associated with avalid RFID tag 232 and monitored by theconsumables authentication module 328 so that once the number of applications is reached (and thus the consumable expended) thecleaning station 100 a cannot be used until anothervalid consumables container 228 is installed. For example, say that oneconsumables container 228 contains enough cleaning fluid for approximately 500 hand-washing cycles. Once the cleaningstation 100 a has administered approximately 500 hand-washing cycles using aparticular consumables container 228, then this container will no longer be operable with the cleaningstation 100 a. This prevents theconsumable container 228 from being removed, refilled with a non-approved cleaning fluid, and then reattached for use with the cleaningstation 100 a. Such forced compliance for use of the proper consumables provides compliance regulators and/or administrators confidence that, for example, the approved disinfectants are being applied to theusers 204 hands with each cleaning or use. - In addition to RFID, other methods and/or systems may be used to identify the
consumables container 228. In particular, theconsumable container 228 may be identified by a bar code and bar code reader. Moreover, the present invention may include modules that perform other functions such as collecting and reporting maintenance data; reporting information on the last recorded information transfer; and/or reporting the cleaning station's name, type, IP address and current software version. - Referring now to
FIG. 6 , a block diagram showing components and features of theadministration computer 104 is illustrated.Administration computer 104 includes aprocessor 600, amemory 604 and signalinginterfaces first signaling interface 608 operates to communicate with the cleaning stations 100 a-100 n over communication links 108 a-108 n, as described above. The second signaling interface operates to communicate with thevarious input 616 andoutput 620 devices associated with theadministration computer 104. Theinput device 616 may be, for example, a keyboard or a mouse. Theoutput device 620 may be, for example, a monitor or a printer. - The
memory 604 includes a plurality of stored program applications or modules that implement various features of a compliance monitoring system. In accordance with embodiments of the present invention, thememory 604 may include adata retrieval module 624 and acustom report module 628. Additionally, thememory 604 may includedata structures 632 associated with the various modules. In accordance with embodiments of the present invention, thedata structures 632 may include anemployee record 636 and/or acompliance report 640. As can be appreciated by one of skill in the art from the disclosure herein, thememory 604 may include database structures implemented using suitable database software (such as SQL Server Express). - The
data retrieval module 624 operates to retrieve data associated with cleaning stations 100 a-100 n. Such data may include data related to cleaning station usage and/or employee specific data. The data may be contained in a cleaning station-use record 336 and/or anemployee record 340 associated with a cleaning station 100 a-100 n. Additionally, thedata retrieval module 624 may operate to maintain aglobal employee record 636 as described above. - The
custom report module 628 operates to generate thecompliance report 640. The compliance report is generated from data contained in each station-use record 336 associated with cleaning stations 100 a-100 n. An exemplary compliance report is shown inFIG. 7 . In accordance with embodiments of the present invention, an entry in thecompliance report 640 may include anemployee name 700,time stamp 704 indicating when a cleaning cycle was initiated, thedate 708 of the cleaning cycle, thelocation 712 where the cleaning cycle took place, and acompliance indicator 716 specifying whether or not theuser 204 met the compliance requirement. As an example, the compliance report shown inFIG. 7 indicates that on May 21, 2006 Janet Smith met the hand-washing requirement by completing a cleaning cycle that was initiated at 8:00.00 A.M at cleaning station A. As noted, compliance reports may include data pertaining to user statistics. Alternatively, or in addition to reports comprising user statistics, reports may be generated that are directed to the consumables, such as soap and disinfectants. - The
compliance report 640 may be generated at different time intervals and may be grouped based on different criteria. For example, the compliance report may be generated daily, weekly, monthly, yearly, et cetera. Moreover, thecompliance report 640 may be generated that are grouped by individual or station. - In accordance with embodiments of the present invention,
FIG. 8 shows a block diagram illustrating the steps of a method of monitoring a compliance requirement. Initially, at step 800 auser 204 approaches acleaning station 100 a and presents a badge having aRFID tag 208 to anRFID reader 212. Atstep 804 theRFID tag 208 is read and theuser 204 is identified. Atstep 808 the user's 204 name, the date, the time, and the location of the cleaningstation 100 a are recorded. At step 812 a cleaning cycle is initiated when theuser 204 places her or his hands in position to be washed. During the wash cycle, atoptional step 816, theuser 204 is provided with educational or entertainment content through thevideo display 224. Atstep 820 the wash cycle is completed and data is recorded including the duration of time theuser 204 allowed his or her hands to be washed. Atstep 824 the transaction is completed and recorded. Atstep 828, data is collected from the cleaning stations 100 a-100 n over the communication links 108 a-108 n. In particular, data may be routed to a central collection point or FTP folder. Finally, atstep 832, the collected data is used to generate acompliance report 640. Additional steps associated with the method may include: monitoring proper use of consumables; warning that animproper consumables container 228 has been installed; warning that aconsumables container 228 is empty or nearly empty based on the number of uses since being installed; and warning that none or more users are failing to meet compliance requirements. - In another embodiment, a web-enabled hygiene monitoring system is provided. As shown in
FIGS. 9A-B , the system 900 includes a plurality of discrete monitoredentities 904 a,b-w, each comprising first, second, . . . xth; first, second, . . . yth; or first, second, . . . jth washing stations 100 a-x, 100 a-y or 100 a-j, respectively, acompliance data hub 912, acompliance monitor 916 a,b-p, and acompliance filter 920, all interconnected by adata network 924. - The
entities 904 a,b-w are each a monitored location. Particular monitored entities may be discrete facilities of a common monitored enterprise. For example, thecompliance data hub 912 may monitor a network of hospitals or restaurants. Referring toFIG. 9A , the monitoredentities common business enterprise 906. Alternatively, a monitored enterprise may include only one monitored entity. InFIG. 9A , monitoredentity 904 w represents a separate business enterprise. In other words, thecompliance data hub 912 may be associated with a plurality of business enterprises that are owned and operated by different companies, and one or more of those enterprises may include a plurality of different locations or facilities. Examples of enterprises include health care providers, food service providers (e.g., restaurants), food and/or drink manufacturers (e.g., meat packing plants, dairy product manufacturers, and the like), and other types of providers subject to internal and/or regulatory cleaning requirements. - In accordance with embodiments of the present invention, each monitored entity 904 network includes an
administration computer 104 a,b-w or data collection point that collects cleaning information from each washing station 100 a-x, a-y, a-j in the corresponding enterprise network and, periodically or continually, provides the information to the compliance server 932 (shown inFIG. 9B ) of thecompliance data hub 912. As can be appreciated, an administration computer may be a network computer or server and may include a database. In this configuration, the cleaning information may be pushed by theadministration computer 104 a,b-w to thecompliance server 932 or pulled from theadministration computer 104 a,b-w by thecompliance server 932. Furthermore, it is noted that configuration of the each monitoredentity 904 a,b-w substantially corresponds to the embodiment of the present invention shown inFIG. 1 . - Each
administration computer 104 a,b-w may include a user interface through which employee related data may be entered. The user interface may be implemented using any suitable software package (such as Access 2003) and can include portions that are icon driven to facilitate data entry and include drop down menus to ensure consistency of data. Additionally, data may be dynamically saved when possible. The user interface may include a plurality of screens wherein data is saved after a screen is changed. When changing screens, a user may be prompted to enter data not previously saved. Moreover, mandatory data fields may be supported for a software versions. - The washing stations 100 a-x, a-y, a-j can be any type of cleaning equipment and are typically at different spatial locations in the monitored entity. Examples of washing stations include manual and automated body member (e.g., hand, foot, etc.) and other object washing stations, such as automated hand washers, sinks/faucets and cleaning solution dispensers, and the like. As will be appreciated, “object” refers to living or animate organisms, such as people and animals, as well as inanimate objects or entities, such as equipment and tools.
- As discussed below, each monitored
entity 904 a,b-w has a corresponding unique monitored entity identifier, and, within each monitoredentity 904 a,b-w, each washing station 100 a-x, a-y, a-j has a unique station identifier. Accordingly, each pairing of monitored entity and station identifiers is unique. In one configuration, an object type identifier (not shown) is used in addition to the employee type identifier. The object type identifier refers to animate and inanimate objects, each of which has a unique or substantially unique identifier. While the identifier is carried removably by persons, the identifier may be attached permanently or semi-permanently to the inanimate object. The identifier can be, for example, a passive RFID tag, a bar code label, and the like. Unlike employee identifiers, which, for an enterprise, are unique, inanimate object identifiers may not be unique for each individual object in the enterprise but unique for a class of objects of the same type. Thus, objects of the same type have a common identifier, while objects of different types have different identifiers. - Each washing station 100 a-x, a-y, a-j includes a
compliance module 316 that in turn includes a processor and computer readable storage medium. Thecompliance module 316 identifies objects to be cleaned, determines a suitable cleaning protocol for the object to be cleaned, records object identifiers, object type identifiers, cleaning protocol identifiers, timestamps, compliance indicators, alert instances, and the like, determines the compliance or noncompliance of a cleaning, and generates appropriate alerts. Additionally, each washing station 100 a-x, a-y, a-j can further include modules to determine whether the operational status of the corresponding washing station or a component thereof. As noted, the operational status includes not only whether the washing station or a component thereof is fully or partly operational or nonoperational, but also quantitatively a current level or remaining amount of a consumable item, such as soap or a cleaning/antimicrobial solution, or qualitatively whether the consumable level falls below a threshold level. Eachmodule 316 may be associated with amemory 304 that typically includes a record or lookup table listing, by employee identifier, a corresponding cleaning protocol identifier. - The
compliance data hub 912 generally collects, stores, and analyzes cleaning information from thevarious administration computers 104 a,b-w. (Theadministration computers 104 a,b-w having collected hand-washing data from the individual cleaning stations 100 a-x, a-y, a-j.) Thecompliance data hub 912 includes acompliance server 932 for receiving cleaning information and forwarding the cleaning information to an appropriate storage location in thecompliance data hub 912, and for retrieving requested cleaning information from an appropriate storage location and forwarding the information to an authorized and verified entity, such as compliance monitor 916 a,b-p. In that regard, thecompliance data hub 912 further includes one or more databases 936 a-n for storing cleaning information and aLocal Area Network 940 interconnecting the databases with theserver 932. The databases 936 a-n may be separate, as shown, with each database corresponding to a monitored entity 904 a-n or a single database partitioned into segments, one segment for each monitored entity 904. The databases 936 a-n may be implemented using suitable database software (such as SQL Server Express). - The
various administration computers 104 a,b-w associated with the various monitored entities may support modules that communicate withcompliance data hub 912. In accordance with embodiments of the present invention, it may by necessary to import a license token from thecompliance data hub 912 in order to enable modules used at the administration computer level. The token may be specific to a particular enterprise and may include: the company name, a primary contact and primary contact information, a secondary contact and secondary contact information, the number of licensed users, and the type of service supported. In accordance with embodiments of the present invention, the token may be an encrypted string of text that will be delivered as a token license file. Moreover, thecompliance data hub 912 may periodically access and/or update modules at the administration computer level. In accordance with embodiments of the present invention, an email may be generated providing notice that a particular module was accessed or updated. - As shown in
FIG. 9B , thecompliance server 932 includes adata management module 944 that queriesadministration computers 104 a,b-w for cleaning information, forwards received cleaning information to an appropriate database 936 for storage, receives requests for cleaning information and, after successful authentication and verification of the request source, retrieves and forwards the requested cleaning information to the requesting source, and analyzes the cleaning information for instances of compliance and/or noncompliance events. - The
data management module 944 is operable to provide a data management module report. An exemplary datamanagement module report 1000 is shown inFIG. 10 . The datamanagement module report 1000 may include anenterprise identification number 1004. Thecompliance data hub 912 may assign a uniqueenterprise identification number 1004 to each business enterprise monitored by thecompliance data hub 912. For example, theenterprise identification number 1004 having a value “123456”, as shown inFIG. 10 , may be associated with thebusiness enterprise 906 shown inFIG. 9A . A particular compliance data report 1000 may be provided in connection with a particular business enterprise and will typically not include compliance data associated with other entities monitored by thecompliance data hub 912. In particular, monitoredentity 904 w, which is not part ofbusiness enterprise 906, would be associated with a differententerprise identification number 1004. Accordingly, compliance data associated with the monitoredentity 904 w would not appear on the exemplary compliance data module report shown inFIG. 10 . Thedata hub 912 may maintain a contacts module operable to store and track contact information associated with each monitored business enterprise. - The data
management module report 1000 may additionally include astation identification number 1008 and auser identification number 1012. For a particular entry in thereport 1000, thestation identification number 1008 indicates the particular washing station where the washing took place. Theuser identification number 1012 is associated with a particular individual, such as an employee. Accordingly, for a particular entry in the report the user identification number indicates who used the washing station. Each entry in thereport 1000 includes adate 1016 andtime 1020 indication when the washing took place. Afacility identifier 1024 may also be included if the monitored enterprise associated with thereport 1000 includes more than one location or facility. Thefacility identifier 1024 may indicate in which facility within a particular enterprise the washing took place. The report also includes anindication 1028 of whether or not a complete wash cycle wash performed. - Additionally, the data
management module report 1000 may include a compliancemonitor identification number 1032. The compliancemonitor identification number 1032 may be used to indicate which compliance monitor 916 a,b-p of a plurality of compliance monitors 916 a,b-p is currently receiving or will be receiving compliance data associated with a particular item in the data management module report 100. In addition or in the alternative, the compliancemonitor identification number 1032 may be used by thecompliance filter 920 in connection with determining which data items in the data management module report will be sent to the compliance monitors 916 a,b-p. It should be appreciated that a particular report may include other fields not shown inFIG. 10 . For instance, the report may include a wash station name or a wash station IP address. - Data management module reports 1000 may be generated at different time intervals and may be grouped based on different criteria. For example, reports 1000 may be generated daily, weekly, monthly, yearly, et cetera. Moreover, reports 1000 may be generated that are grouped by individual, company, facility, station, et cetera.
- The
compliance hub 912 may allow particular individuals to access stored data and/or reports including the datamanagement module report 1000. In accordance with embodiments of the present invention, areport 1000 may be accessed remotely through a web interface. In that regard,web user 948, with proper access permission, can access compliance data stored in thecompliance data hub 912. Particular individuals given access to stored data may include, for example, company managers and/or officers. As described in greater detail below, a report may be provided to acompliance monitor 916 a,b-p. - Access to data management module reports 1000 and other stored data may be limited and/or controlled by a security system. In that regard, the
data compliance hub 912 may include a group security module that provides a password protected control to stored data. The level of access allowed to a particular individual may be based on their membership in a particular group. Particular groups can include, for example, account manager, customer, demo, administration, data hub administration, and developer. Particular functions such as view, store and print may be useable based on the level of access granted. - The
compliance data hub 912 can perform a variety of data processing functions. Thecompliance data hub 932, for example, can compare cleaning information, or a given sensed parameter, to identify events, temporal trends, or differences and, if necessary, generate appropriate alarms. The alarms can be logged internally and/or forwarded to the respective cleaning station 100 a-x, a-y, a-j. The cleaning station 100 a-x, a-y, a-j can then provide the alarm or warning to the appropriate cleaned object that, for instance, the cleaning provided was not compliant. An exemplary alarm may be “Successful Cleaning”, “Warning Cleaning Failed”, and the like. In another configuration, the alarm is that a consumable level is low and requires replacement or that the wrong consumable is being used. Thecompliance data hub 912 can also provide communications to the cleaning stations. The communications can, for example, be audio and video information for display to users of the stations. As will be appreciated, the audio and video information may be streaming media transmitted over thedata network 924, including, but not limited to, video transmitted tovideo display 224. - In one configuration, the databases 936 further include, or reference, information collected and stored by the enterprise security system (not shown). For example, employee badge activated entrances typically collect the badge identifier (or employee identifier) and a timestamp when the badge identifier was received. Such information can be used in analyzing compliance by determining whether the employer having the sensed badge identifier used the washing station in temporal proximity to passing through the secured entrance. As will be appreciated, the spatial locations of activated entrances and washing stations are known and can be used, collectively, to monitor compliance.
- The one or more compliance monitors 916 a,b-p may be, for example, an entity responsible for monitoring and/or otherwise administering the hygiene policies and/or requirements of the one or more enterprises associated with the monitored entities 904. The monitor may be a governmental entity, such as a department of health and human services and the U.S. Food and Drug Administration, to name but a few, or a private entity such as a hygiene administration department. Typically, a plurality of compliance monitors 916 a,b-p are involved, with each monitor being associated with a different local, state, or national (federal) government entity. By way of example, a facility of an
enterprise 906 may need to report compliance data to multiple compliance monitors 916 a,b-p, such as at the city or municipality, county, state, and federal levels. - In one or more embodiments of the present invention, a
compliance filter 920 may be used. Thecompliance filter 920, in one configuration, receives outgoing transmissions of cleaning information and filters the information before it is provided to one or more of the compliance monitors 916 a,b-p. Thecompliance filter 920 may be part of or separate from (as shown) thecompliance data hub 912. Thecompliance filter 920 ensures that cleaning information from different monitoredenterprises 906 is not intermixed and only necessary cleaning information is provided to the compliance monitor 916 a,b-p, thereby protecting client/customer confidentiality and legally recognized privileges. In one configuration, thecompliance filter 920 is a law firm responsible for and knowledgeable about compliance monitoring requirements. Attorneys may review the cleaning information and maintain the confidentiality of the cleaning information under the attorney-client privilege. Furthermore, in at least one embodiment, thecompliance filter 920 is an auditing entity other than a law firm. - The
data network 924 can be any circuit- or packet-switched network, with a packet-switched network, such as the Internet or World Wide Web, being preferred. - The cleaning information is typically converted into a selected form, packetized, and transmitted over the
network 924. The form of the information can be in accordance with any selected language, such as the eXtensible Markup Language or XML, the HyperText Markup Language or HTML, Remote Method Invocation or RMI, or Direct Socket Connections. The packets can be transported using any suitable protocol, such as the Transport Control Protocol/Internet Protocol suite of protocols, Simple Object Access Protocol, or User Datagram Protocol. - The operation of the hygiene monitoring system will now be discussed with reference to
FIG. 11 . - In
step 1100, thecompliance module 316 of a selected washing station 100 identifies an object within range of the sensor. For example, an RFID tag identifier code associated with an animate or inanimate object is read by the RFID reader. Control then passes to step 1104. - In
step 1104, the sensed identifier code and a first timestamp are recorded by themodule 316. The first timestamp is indicative of the start time of the cleaning or washing cycle. In other configurations, the actual time that the cleaning cycle is commenced is sensed by a suitable sensor, such as an infrared sensor, motion sensor, or other type of optical or electromagnetic sensor, and recorded. - In
step 1108, themodule 316 maps the sensed identifier code against the lookup table ofFIG. 5B and determines, for the sensed identifier code, a corresponding value for the cleaning protocol to be employed. Themodule 316 then configures the corresponding washing station 100 for performing the cleaning steps required by the protocol. - In
step 1112, under the control of themodule 316 the washing station 100 cleans the identified object according to the requirements of the cleaning protocol. In one configuration, the washing station 100 provides audible or visual instructions to the identified object or to an operator cleaning the identified object regarding the protocol requirements and senses when the various protocol steps are performed. - In
step 1116, themodule 316 records the sensed identifier and a second timestamp when one or more steps of the cleaning protocol is/are completed or, if the cleaning protocol steps are not completed, when the object to be cleaned is no longer within range of a sensor (e.g., the RFID reader or infrared sensor) of the washing station 100. Themodule 316 further records, for the sensed identifier, the protocol identifier for the corresponding protocol, and a compliance indicator (e.g., whether the protocol was successfully or unsuccessfully completed before the sensed identifier left sensor range). - In
step 1120, an appropriate alert is generated depending on whether the protocol was successfully or unsuccessfully completed. The alert or warning can be provided to the object by the washing station 100. - In
decision diamond 1124, themodule 316 determines whether collected compliance data or cleaning information should be uploaded to thedata network 924 for transmission to thecompliance server 932. The trigger for uploading the information could be, for example, time-based, based on the number of washings performed by the corresponding station, or based on the available or unavailable memory capacity of themodule 316 in the corresponding station. Alternatively, the trigger could be the receipt of a request from theserver 932 for the information. - When the collected compliance data is to be provided to the
server 932, themodule 316 generates one or more signals containing the data and includes, in each signal, the monitored entity identifier of the corresponding monitored entity (e.g., the identifier of the enterprise operating the washing station 100) and station identifier of the washing station 100 performing the cleaning. As noted, the monitored entity identifier is unique among the monitored entities, and the station identifier among the various stations 100 operated by the corresponding monitored entity. The signal(s) are then forwarded to thecompliance server 932. - The
data management module 944, based on the enterprise identifier, forwards the signals to the appropriate compliance database 936, or storage location(s), for storage and analysis. As will be appreciated, themodule 944 maps the monitored entity identifier against a lookup table indexing monitored entity identifiers against database address and/or storage address range. The received information is then forwarded to an interface for the corresponding database for storage. The table is further used to retrieve compliance data for an identified, monitored entity. - In another embodiment, the
data management module 944 and/compliance filter 920 use location information to identify appropriate compliance monitor(s) 916 a,b-p to which to report, to configure collection parameters, and/or to configure compliance reports for transmission to the identified compliance monitor(s) 916 a,b-p. The location information can be in many different forms. For example, each monitored facility of a common enterprise or each monitored enterprise is assigned geographical information indicating the physical location of the monitored entity. In another example, each monitored facility of a common enterprise or each monitored enterprise is assigned geopolitical information indicating the regulatory jurisdiction or political location of the monitored entity. By way of illustration, the political location of the facility would identify each compliance monitor 916 a,b-p to which activities at the facility must be reported. In yet another example, each washing station is assigned geographic and/or geopolitical information. In yet another example, each washing station has an embedded location module, such as a GPS or other satellite enabled locating device, which provides location coordinates. In this example, as the washing station is moved from one facility to another the location information is changed dynamically. - Using the location information, whether associated with the facility as a whole or separately with each washing station in the facility, the
data management module 944 determines the corresponding monitoring and reporting requirements for the pertinent compliance monitor(s) 916 a,b-p. This is typically done using a lookup table, such as that shown inFIG. 12 . - Referring to
FIG. 12 , thegeographic location information 1200 is mapped againstcompliance monitor 1202, compliance data required 1204, requiredreporting frequency 1208, andreporting requirements 1212. Thegeographic location information 1200 refers to the expression of geographical and/or geopolitical location used to signify the location of the monitored entity. As noted, thegeographic location information 1200 can be satellite-enabled location coordinates, compliance monitor identifiers, city identifiers, county identifiers, state identifiers, country identifiers, and the like. Thecompliance monitor designation 1202 identifies the compliance monitor 916 a,b-p to which compliance reports are to be provided. The values incolumn 1202 can be values associated with the compliance monitor 916 a,b-p (which may be an electronic address). Compliance data required 1204 refers to the information to be collected to comply with requirements of the identified compliance monitor. Compliance data required 1204 includes, for example, a number of required washes/station, percent compliance (determined on a suitable basis), number of required washes/employee, and the like. The requiredreporting frequency 1208 refers to how frequently compliance data/reports are to be forwarded to the identified compliance monitor. The frequency, for example, can be daily, weekly, monthly, yearly, and the like. Finally,report requirements 1212 refer to requirements for the compliance information provided to the identified compliance monitor.Report requirements 1212, for example, can refer to how the compliance data is to be transmitted to the monitor (e.g., by email, by mail, by upload/download operation over thedata network 924, and the like), the formatting and organizational requirements for the report, the entities associated with the monitor to whom the information is to be provided and each entity's address information, and the like. Other information incolumn 12 includes whether the information is to be encrypted and, if so, what key(s) are to be employed, the human or computer language in which the report is to be expressed (e.g., German, English, HTML, XML, and the like), and the like. - The operation of this embodiment will now be discussed with reference to
FIG. 13 . - In
step 1300, a scheduling module (not shown) generates an interrupt identifying one or more compliance monitors 916 a,b-p requiring compliance report(s) to be provided. The interrupt is received by thedata management module 944. - In
step 1304, themodule 944 determines the location information associated with a selected one of the compliance monitors referenced in the interrupt. This can be done by mapping an identifier of the selected compliance monitor against a listing of location information regulated or serviced by the selected compliance monitor 916 a,b-p. - In
step 1308, themodule 944 determines, based on thegeographic location information 1200, each of the monitoredentities 904 a,b-w monitored by the selected compliance monitor and, based on the geographic location information 1200 a monitored entity identifier for each of the identified entities, the compliance data required 1204. - In
step 1312, themodule 944 retrieves the required compliance data. This is typically done iteratively on an enterprise-by-enterprise basis to avoid intermixing compliance data for different enterprises. Compliance data may be collected by querying the appropriate one of the first, second, . . . nth databases 936 a-n and/or obtaining compliance information from each of the first, . . . xth washing stations 100 a-x at the subject facility for each identified enterprise. - In
step 1316, themodule 944 determines thereporting requirements 1212 for the selected compliance monitor. - In
step 1320, themodule 944, using the reporting requirements and compliance data obtained, generates and sends the report to thecompliance filter 920 and/or directly to the compliance monitor 916 a,b-p. When the report is sent to thecompliance filter 920, thefilter 920 can remove unnecessary information collected by the washing stations and forward the filtered report to the compliance monitor 916 a,b-p. - In
decision diamond 1324, themodule 944 determines whether the interrupt identified a next compliance monitor. If not, control returns to step 1300. If so, the next compliance monitor is selected, and the module returns to step 1304. - The following U.S. patents are incorporated herein by reference in their entireties U.S. Pat. Nos. 823,447; 5,265,628; 4,817,651; and 4,925,495.
- Though the description of the invention has included description of one or more embodiments and certain variations and modifications, other variations and modifications are within the scope of the invention, e.g., as may be within the skill and knowledge of those in the art, after understanding the present disclosure. It is intended to obtain rights which include alternative embodiments to the extent permitted, including alternate, interchangeable and/or equivalent structures, functions, ranges or steps to those claimed, whether or not such alternate, interchangeable and/or equivalent structures, functions, ranges or steps are disclosed herein, and without intending to publicly dedicate any patentable subject matter. Moreover, various other aspects of the invention disclosed herein are set out in the following numbered clauses:
- 1. An automated washing compliance verification system provided in association with a plurality of enterprise networks, the system comprising:
- a plurality of washing stations each operable to wash an object, the plurality of washing stations being associated with the plurality of enterprise networks; and
- a compliance data hub including a memory, the memory comprising:
-
- (a) a data management module; and
- (b) a plurality of electronic storage locations, each storage location being associated with a corresponding enterprise network and storing compliance data collected by at least one washing station in the corresponding enterprise network;
- wherein the data management module is operable to produce a data management report including compliance data collected in at least one enterprise network of the plurality of enterprise networks.
- 2. The automated washing compliance verification system of
clause 1, wherein each enterprise network has a corresponding unique enterprise identifier and wherein each storage location is associated with a different enterprise identifier. - 3. The automated washing compliance verification system of
clause 2, wherein each washing station has a corresponding station identifier, with each station identifier being unique in the enterprise network containing the washing station. - 4. The automated washing compliance verification system of
clause 1, wherein the compliance data comprises a plurality of different object identifiers and different protocol identifiers, each protocol identifier being associated with a different cleaning protocol. - 5. The automated washing compliance verification system of clause 4, wherein each object identifier has a corresponding protocol identifier and wherein at least one protocol identifier indicates that no cleaning be performed for the corresponding object identifier.
- 6. The automated washing compliance verification system of
clause 1, wherein the data management module is operable to provide the data management module report to a web user, the web user having supplied a valid password. - 7. The automated washing compliance verification system of
clause 1, wherein the data management module is operable to provide the data management module report to a compliance monitor. - 8. The automated washing compliance verification system of clause 7, wherein the compliance monitor includes at least one of:
- a city government entity;
- a state government entity;
- a federal government entity; and
- a private compliance monitoring entity.
- 9. The automated washing compliance verification system of clause 7, further comprising:
- a compliance filter operable to filter compliance data prior to the data being provided to the compliance monitor.
- 10. The automated washing compliance verification system of clause 9, wherein the compliance filter modifies at least one data item from the compliance data.
- 11. The automated washing compliance verification system of
clause 1, wherein the data management module reports one or more entries, the entries including at least one of: - an enterprise identifier;
- a station identifier;
- a user identifier;
- a date;
- a time;
- a facility identifier;
- a compliance monitor identifier; and
- a compliance indicator.
- 12. The automated washing compliance verification system of
clause 1, wherein the plurality of business enterprises include a first and a second business enterprise, the first and second business enterprise being separately owned. - 13. The automated washing compliance verification system of
clause 12, wherein the first enterprise includes a plurality of discrete facilities. - 14. The automated washing compliance verification system of
clause 1, wherein each enterprise network includes a custom report module in communication with the data management module associated with the compliance data hub, each custom report module being enabled by a token imported from the compliance data hub, the token including at least one of: - a company name;
- primary contact information;
- secondary contact information;
- number of licensed users; and
- type of service supported.
- 15. The automated washing compliance verification system of
clause 1, wherein the data management module is operable to provide an analysis of the compliance data, and based on the analysis, provide at least one alarm to at least one enterprise network. - 16. The automated washing compliance verification system of
clause 1, wherein the compliance data associated with a particular enterprise network includes data collected by a security system associated with the particular enterprise network. - 17. The automated washing compliance verification system of
clause 1, wherein the at least one washing station includes: - (a) an identification apparatus operatively associated with the washing station, the identification apparatus operable to at least automatically identify at least one of:
-
- (1) the user, and
- (2) an object;
- (b) a washing station operations monitor operatively associated with the cleaning station and the identification apparatus; and
- (c) a memory associated with the washing station operations monitor, the memory comprising at least one of:
-
- (1) a compliance module operable to record data associated with the user;
- (2) an information module operable to provide the user with at least one segment of information about at least one of entertainment, a cleaning history statistic, and training;
- (3) a consumables-authentication module operable to verify that the washing station is operating with a particular substance; and
- (4) a solutions selection module operable to direct the washing station to perform at least one of the following:
- (A) based on a user identifier, administer at least one of:
- (i) a predetermined mixture; and
- (ii) a substance;
- and
- (B) operate a function for a predetermined period of time based on a history of washing compliance for the user.
- (A) based on a user identifier, administer at least one of:
- 18. In a hygiene compliance verification system, a computer readable medium comprising a set of data structures, the set of data structures comprising:
-
- (a) a first set of information identifying a hygiene compliance monitor;
- (b) compliance data required to be reported to the compliance monitor; and
- (c) reporting requirements associated with the compliance monitor;
- wherein the data structures are used to produce a data management report including the compliance data.
- 19. The medium of clause 18, wherein the set of data structures further comprises:
-
- a reporting frequency required by the compliance monitor.
- 20. The medium of clause 18, wherein the set of data structures further comprises:
- location information, the location information identifying at least one of a geographical and geopolitical location monitored by the compliance monitor.
- 21. A compliance monitoring system for use with at least one hygiene station, the system comprising;
- (a) a verification module; and
- (b) an electronic storage location for storing compliance data collected by the at least one hygiene station, wherein the compliance data comprises a plurality of different object identifiers and different protocol identifiers, each protocol identifier being associated with a different cleaning protocol, wherein each object identifier has a corresponding protocol identifier and wherein at least one protocol identifier indicates that no cleaning be performed for the corresponding object identifier.
- 22. The system of
clause 21, further comprising: - a plurality of enterprise networks, each enterprise network including at least one corresponding hygiene station; and
- a plurality of electronic storage locations, each storage location being associated with a corresponding enterprise network and storing compliance data collected by the at least one corresponding hygiene station in the corresponding enterprise network.
- 23. The system of clause 22, wherein each enterprise network has a corresponding unique identifier and wherein each storage location is associated with a different enterprise identifier.
- 24. The system of clause 23, wherein each hygiene station has a corresponding station identifier, with each station identifier being unique in the enterprise network containing the hygiene station.
- 25. The system of
clause 21, wherein the hygiene station comprises a sink and a faucet, and wherein the compliance monitoring system further comprises at least one sensor at or proximate to at least one of the sink and the faucet. - 26. The system of
clause 21, wherein the hygiene station comprises an automated cleaning station, and wherein the compliance monitoring system further comprises at least one sensor at or proximate to the automated cleaning station. - 27. The system of
clause 21, further comprising a compliance filter, wherein the compliance filter receives the compliance data and filters the compliance data before it is provided to one or more compliance monitors. - 28. A compliance monitoring system, comprising:
- means for receiving compliance data associated with a plurality of enterprise networks;
- means for storing the compliance data in a plurality of electronic storage locations, wherein each storage location corresponds to one enterprise network of the plurality of enterprise networks; and
- means for providing at least one compliance data report, the compliance data report including compliance data received from a particular enterprise network of the plurality of enterprise networks.
- 29. The compliance monitoring system of clause 28, further comprising:
- means for providing the compliance data report to a web user, the web user having supplied a valid password.
- 30. The compliance monitor of clause 28, further comprising:
- means for providing the compliance data report to a compliance monitor.
- 31. A method of performing hygiene compliance verification, comprising:
- receiving hygiene compliance data associated with a plurality of enterprise networks, each network being associated with a different enterprise comprising one or more automated sensors;
- storing the hygiene compliance data; and
- providing at least one hygiene compliance data report, the hygiene compliance data report including hygiene compliance data received from a particular enterprise network of the plurality of enterprise networks.
- 32. The method of clause 31, further comprising:
- providing the hygiene compliance data report to a web user, the web user having supplied a valid password.
- 33. The method of clause 31, further comprising:
- providing the hygiene compliance data report to a compliance monitor.
- 34. The method of clause 33, wherein the compliance monitor includes at least one of:
- a city government entity;
- a state government entity;
- a federal government entity; and
- a private compliance monitoring entity.
- 35. The method of clause 33, further comprising:
- prior to providing the hygiene compliance data report to the compliance monitor, filtering the hygiene compliance data, wherein filtering includes removing at least one data item from the hygiene compliance data.
- 36. The method of clause 31, further comprising:
- analyzing the hygiene compliance data; and
- based on the analysis, providing at least one alarm to at least one enterprise network.
- 37. The method of clause 31, wherein the hygiene compliance data associated with a particular enterprise network includes data collected by a security system associated with the particular enterprise network.
- 38. The method of clause 31, wherein an automated sensor in each enterprise network compiles the hygiene compliance data by:
- automatically identifying a user of at least a first cleaning station, the cleaning station including an apparatus for automatically washing at least a portion of the user; and
- recording by a computer at least an identity of the user of the first cleaning station, the first cleaning station automatically washing at least the portion of the user.
- 39. The method of clause 31, wherein the hygiene compliance data is stored in a plurality of electronic storage locations, each storage location corresponding to one of the plurality of enterprise networks.
- 40. A method for reporting hygiene compliance, comprising:
- (a) determining automatically a geographic location information associated with a compliance monitor;
- (b) determining automatically a monitored entity identifier associated with the geographic location information, the monitored entity identifier being associated with at least one of an enterprise and a facility;
- (c) determining automatically hygiene compliance data required by the compliance monitor;
- (d) based on the hygiene compliance data required, providing hygiene compliance data associated with the monitored entity identifier;
- (e) determining automatically report requirements associated with the compliance monitor; and
- (f) forwarding the provided hygiene compliance data to the compliance monitor.
- 41. A computer readable medium operable to perform the steps of clause 40.
- 42. A method for performing hygiene compliance verification, comprising:
- (a) receiving an object identifier;
- (b) determining a cleaning protocol from a plurality of different protocols to be used on an object associated with the object identifier; and
- (c) implementing the cleaning protocol in connection with the object.
- 43. The method of clause 42, wherein the object identifier indicates that no cleaning is required.
- 44. The method of clause 42, wherein implementing the cleaning protocol includes:
- (i) cleaning the identified object in accordance with the cleaning protocol; and
- (ii) generating a compliant and/or noncompliant signal indicating compliance and/or noncompliance with at least part of the cleaning protocol.
- 45. The method of clause 42, wherein the object identifier is associated with an object type identifier.
- 46. The method of clause 45, wherein the object type identifier is indicative of a type of employee.
- 47. An electronic hygiene compliance verification data signal, comprising:
-
- (a) source and destination addresses;
- (b) hygiene compliance information; and
- (c) an enterprise identifier; and
- (d) a compliance monitor identifier.
- 48. The data signal of clause 47, wherein the hygiene compliance information comprises a station identifier.
- 49. The data signal of clause 47, wherein the hygiene compliance information comprises a user identifier.
- 50. The data signal of clause 47, wherein the hygiene compliance information comprises one or more of a date and a time.
- 51. The data signal of clause 47, wherein the hygiene compliance information comprises a facility identifier.
- 52. The data signal of clause 47, wherein the hygiene compliance information comprises a compliance confirmation.
- 53. The data signal of clause 47, wherein the hygiene compliance information comprises hygiene compliance data received from a particular enterprise network of a plurality of enterprise networks, the particular enterprise network associated with the enterprise identifier
- 54. The data signal of clause 47, further comprising at least a second enterprise identifier.
- 55. The data signal of clause 54, wherein the hygiene compliance information comprises hygiene compliance data received from a particular enterprise network of a plurality of enterprise networks, the particular enterprise network associated with the enterprise identifier, the plurality of enterprise networks including at least a second enterprise network, wherein the second enterprise identifier is associated with the second enterprise network.
- 56. The data signal of clause 47, wherein the compliance monitor identifier is associated with at least one of:
- a city government entity;
- a state government entity;
- a federal government entity; and
- a private compliance monitoring entity.
- 57. The data signal of clause 47, wherein the hygiene compliance information includes information associated with a hygiene station comprising a sink and a faucet, wherein the hygiene station further comprises at least one sensor at or proximate to at least one of the sink and the faucet.
- 58. The data signal of clause 47, wherein the hygiene compliance information includes information associated with a hygiene station comprising an automated cleaning station, wherein the hygiene station further comprises at least one sensor at or proximate to the automated cleaning station.
- The present invention, in various embodiments, includes components, methods, processes, systems and/or apparatus substantially as depicted and described herein, including various embodiments, subcombinations, and subsets thereof. Those of skill in the art will understand how to make and use the present invention after understanding the present disclosure. The present invention, in various embodiments, includes providing devices and processes in the absence of items not depicted and/or described herein or in various embodiments hereof, including in the absence of such items as may have been used in previous devices or processes, e.g., for improving performance, achieving ease and\or reducing cost of implementation.
- The foregoing discussion of the invention has been presented for purposes of illustration and description. The foregoing is not intended to limit the invention to the form or forms disclosed herein. In the foregoing Detailed Description for example, various features of the invention are grouped together in one or more embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the following claims are hereby incorporated into this Detailed Description, with each claim standing on its own as a separate preferred embodiment of the invention.
Claims (9)
1-16. (canceled)
17. A method for performing hygiene compliance verification, comprising:
(a) receiving an object identifier;
(b) determining a cleaning protocol from a plurality of different protocols to be used on an object associated with the object identifier; and
(c) implementing the cleaning protocol in connection with the object.
18. The method of claim 17 , wherein the object identifier indicates that no cleaning is required.
19. The method of claim 17 , wherein implementing the cleaning protocol includes:
(i) cleaning the identified object in accordance with the cleaning protocol; and
(ii) generating a compliant and/or noncompliant signal indicating compliance and/or noncompliance with at least part of the cleaning protocol.
20. The method of claim 17 , wherein the object identifier is associated with an object type identifier.
21. The method of claim 20 , wherein the object type identifier is indicative of a type of employee.
22-25. (canceled)
26. An automated washing station, comprising:
(a) an identification apparatus operatively associated with the washing station, the identification apparatus operable to at least automatically identify at least one of:
(1) the user, and
(2) an object;
(b) a washing station operations monitor operatively associated with the cleaning station and the identification apparatus; and
(c) a memory associated with the washing station operations monitor, the memory comprising at least one of:
(1) a compliance module operable to record data associated with the user;
(2) an information module operable to provide the user with at least one segment of information about at least one of entertainment, a cleaning history statistic, and training;
(3) a consumables-authentication module operable to verify that the washing station is operating with a particular substance; and
(4) a solutions selection module operable to direct the washing station to perform at least one of the following:
(A) based on a user identifier, administer at least one of:
(i) a predetermined mixture; and
(ii) a substance;
and
(B) operate a function for a predetermined period of time based on a history of washing compliance for the user.
27. A method, comprising:
providing a washing station, wherein the washing station comprises;
(a) an identification apparatus operatively associated with the washing station, the identification apparatus operable to at least automatically identify at least one of:
(3) the user, and
(4) an object;
(b) a washing station operations monitor operatively associated with the cleaning station and the identification apparatus; and
(c) a memory associated with the washing station operations monitor, the memory comprising at least one of:
(1) a compliance module operable to record data associated with the user;
(2) an information module operable to provide the user with at least one segment of information about at least one of entertainment, a cleaning history statistic, and training;
(3) a consumables-authentication module operable to verify that the washing station is operating with a particular substance; and
(4) a solutions selection module operable to direct the washing station to perform at least one of the following:
(B) based on a user identifier, administer at least one of:
(i) a predetermined mixture; and
(ii) a substance;
and
(B) operate a function for a predetermined period of time based on a history of washing compliance for the user.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/880,946 US20100326472A1 (en) | 2006-10-31 | 2010-09-13 | Automated washing system with compliance verification |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US86375306P | 2006-10-31 | 2006-10-31 | |
US90928007P | 2007-03-30 | 2007-03-30 | |
US11/852,099 US7818083B2 (en) | 2006-10-31 | 2007-09-07 | Automated washing system with compliance verification and automated compliance monitoring reporting |
US12/880,946 US20100326472A1 (en) | 2006-10-31 | 2010-09-13 | Automated washing system with compliance verification |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/852,099 Continuation US7818083B2 (en) | 2006-10-31 | 2007-09-07 | Automated washing system with compliance verification and automated compliance monitoring reporting |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100326472A1 true US20100326472A1 (en) | 2010-12-30 |
Family
ID=39331298
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/852,099 Active 2027-12-23 US7818083B2 (en) | 2006-10-31 | 2007-09-07 | Automated washing system with compliance verification and automated compliance monitoring reporting |
US12/880,946 Abandoned US20100326472A1 (en) | 2006-10-31 | 2010-09-13 | Automated washing system with compliance verification |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/852,099 Active 2027-12-23 US7818083B2 (en) | 2006-10-31 | 2007-09-07 | Automated washing system with compliance verification and automated compliance monitoring reporting |
Country Status (3)
Country | Link |
---|---|
US (2) | US7818083B2 (en) |
EP (1) | EP2078271A4 (en) |
WO (1) | WO2008055228A2 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100095983A1 (en) * | 2006-10-31 | 2010-04-22 | Resurgent Health & Medical,Llc | Automated appendage cleaning apparatus with brush |
US20100155420A1 (en) * | 2008-12-19 | 2010-06-24 | Resurgent Health & Medical,Llc | Dispensing System for Cleaning Devices |
US8085155B2 (en) | 2006-10-31 | 2011-12-27 | Resurgent Health & Medical, Llc | Sanitizer dispensers with compliance verification |
US8146613B2 (en) | 2008-04-29 | 2012-04-03 | Resurgent Health & Medical, Llc | Wash chamber for surgical environment |
WO2014074585A1 (en) | 2012-11-06 | 2014-05-15 | Johnson Raymond C | Virtual hand-washing coach |
WO2017112795A1 (en) * | 2015-12-21 | 2017-06-29 | Delta Faucet Company | Fluid delivery system including a disinfectant device |
US9824569B2 (en) | 2011-01-28 | 2017-11-21 | Ecolab Usa Inc. | Wireless communication for dispenser beacons |
WO2018090399A1 (en) * | 2016-11-21 | 2018-05-24 | 今日天鸿(天津)医疗卫生科技有限公司 | Internet of things based intelligent liquid extractor system and liquid extracting method |
US20200183354A1 (en) * | 2018-12-05 | 2020-06-11 | Juki Corporation | Monitoring system |
US11382995B2 (en) | 2020-07-24 | 2022-07-12 | 3Oe Scientific, LLC | Hand sanitizing aqueous ozone spray chamber |
Families Citing this family (80)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7607443B2 (en) * | 2006-10-31 | 2009-10-27 | Resurgent Health & Medical, Llc | Wash chamber for automated appendage-washing apparatus |
US20080131332A1 (en) * | 2006-11-06 | 2008-06-05 | Hap Nguyen | RFID-based medical equipment sterilization systems and disinfectant dispensers including methods relating thereto |
US8237558B2 (en) | 2007-03-30 | 2012-08-07 | University Health Network | Hand hygiene compliance system |
US7898407B2 (en) | 2007-03-30 | 2011-03-01 | Toronto Rehabilitation Institute | Hand hygiene compliance system |
US20100023353A1 (en) * | 2007-09-20 | 2010-01-28 | Stoffiere Richard L | Method for establishing, tracking and auditing compliance |
GB2467661B (en) | 2007-09-20 | 2013-02-13 | Bradley Fixtures Corp | Lavatory system |
US9254499B2 (en) * | 2007-10-24 | 2016-02-09 | Michael Klicpera | Apparatus for displaying shower or bath water parameters |
JP2009116600A (en) * | 2007-11-06 | 2009-05-28 | Mitsubishi Electric Corp | Entering and leaving management system |
US20090219131A1 (en) * | 2008-02-28 | 2009-09-03 | Barnett Michael H | System for tracking hand washing and other tasks |
US8212653B1 (en) * | 2008-03-20 | 2012-07-03 | The General Hospital Corp. | Protected zone system |
AU2009241249B2 (en) * | 2008-04-30 | 2013-11-07 | Ecolab Inc. | Validated healthcare cleaning and sanitizing practices |
US8279063B2 (en) * | 2008-11-12 | 2012-10-02 | Xhale, Inc. | Personnel location and monitoring system and method for enclosed facilities |
US8169325B2 (en) * | 2009-02-13 | 2012-05-01 | Verdiramo Vincent L | Portable hand wash monitoring system and method |
US8245879B2 (en) | 2009-03-13 | 2012-08-21 | Gojo Industries, Inc. | Touch-free biometric-enabled dispenser |
US20100306118A1 (en) * | 2009-05-29 | 2010-12-02 | Kochevar Peter D | System for process for remote determination of compliance status |
EP2860716B1 (en) | 2009-06-12 | 2017-04-12 | Ecolab USA Inc. | Hand hygiene compliance monitoring |
USRE48951E1 (en) | 2015-08-05 | 2022-03-01 | Ecolab Usa Inc. | Hand hygiene compliance monitoring |
US8547220B1 (en) | 2009-06-18 | 2013-10-01 | The General Hospital Corporation | Ultrasonic compliance zone system |
US8164439B2 (en) | 2009-06-18 | 2012-04-24 | The General Hospital Corp. | Ultrasonic compliance zone system |
WO2010151802A2 (en) | 2009-06-26 | 2010-12-29 | Madison Research Technologies, Inc. | System for monitoring patient safety suited for determining compliance with hand hygiene guidelines |
EP2486194B1 (en) | 2009-10-07 | 2022-08-24 | Bradley Fixtures Corporation | Lavatory system with hand dryer |
US8140258B1 (en) | 2010-03-02 | 2012-03-20 | The General Hospital Corporation | Wayfinding system |
WO2011119695A2 (en) * | 2010-03-23 | 2011-09-29 | Harkap Partners, LLC | Hand hygiene compliance device |
US10467884B2 (en) | 2010-04-07 | 2019-11-05 | Clean Hands Safe Hands Llc | Systems for monitoring hand sanitization |
US9123233B2 (en) | 2010-04-07 | 2015-09-01 | Clean Hands Safe Hands | Systems for monitoring hand sanitization |
US10223895B2 (en) | 2010-04-07 | 2019-03-05 | Clean Hands Safe Hands Llc | Systems for monitoring hand sanitization |
US10540881B2 (en) | 2010-04-07 | 2020-01-21 | Clean Hands Safe Hands Llc | Systems and methods for pattern recognition and individual detection |
US8847727B2 (en) * | 2010-04-26 | 2014-09-30 | David Alan Shapiro | Electronically-controlled water dispensing system |
WO2011149884A2 (en) | 2010-05-24 | 2011-12-01 | Georgia-Pacific Consumer Products Lp | Hand hygiene compliance system |
WO2012064718A2 (en) | 2010-11-08 | 2012-05-18 | Georgia-Pacific Consumer Products Lp | Hand hygiene compliance monitoring system |
US8482406B2 (en) | 2011-01-28 | 2013-07-09 | Ultraclenz, Llc | Sanitization compliance monitoring system |
US9295251B1 (en) | 2011-04-08 | 2016-03-29 | Safehands Solutions, LLC | Synergistic antimicrobial compositions of PCMX and carboxylic acid and related methods |
US9267736B2 (en) | 2011-04-18 | 2016-02-23 | Bradley Fixtures Corporation | Hand dryer with point of ingress dependent air delay and filter sensor |
US9170148B2 (en) | 2011-04-18 | 2015-10-27 | Bradley Fixtures Corporation | Soap dispenser having fluid level sensor |
WO2012170699A2 (en) * | 2011-06-07 | 2012-12-13 | Steven Bolling | Hand cleanliness |
US20130035900A1 (en) * | 2011-08-01 | 2013-02-07 | Ricky Wayne Purcell | Method for Promoting Hygiene and Cleanliness |
AT511784B1 (en) * | 2011-08-02 | 2016-09-15 | Hagleitner Hans Georg | DOSING DEVICE, ESPECIALLY SANITARY DISPENSERS, AND NETWORK FOR DATA COMMUNICATION |
AT511786A1 (en) * | 2011-08-02 | 2013-02-15 | Hagleitner Hans Georg | NETWORK FOR DATA COMMUNICATION |
US8599009B2 (en) | 2011-08-16 | 2013-12-03 | Elwha Llc | Systematic distillation of status data relating to regimen compliance |
USD663016S1 (en) | 2011-08-25 | 2012-07-03 | Bradley Fixtures Corporation | Lavatory system with integrated hand dryer |
US20150302769A1 (en) * | 2011-12-05 | 2015-10-22 | Raymond C. Johnson | Virtual Hand-Washing Coach |
IES86116B2 (en) * | 2012-02-21 | 2013-01-02 | John Crowe | Hand sanitizer device |
ES2682022T3 (en) | 2012-03-21 | 2018-09-18 | Bradley Fixtures Corporation | Pile and hand drying system |
US9135805B2 (en) | 2012-03-27 | 2015-09-15 | IntelligentM | Methods and systems for encouraging and enforcing hand hygiene |
US8645180B1 (en) * | 2012-07-11 | 2014-02-04 | Sap Ag | Automated impact assessment and updates of compliance response plans pursuant to policy changes |
US20140020166A1 (en) * | 2012-07-17 | 2014-01-23 | Darrell Metcalf | Valve-Controllable Urinal Drain Line and Plumbing Component Rinse Management System for Very Low Water and/or Non-Water Use Urinals |
US10100501B2 (en) | 2012-08-24 | 2018-10-16 | Bradley Fixtures Corporation | Multi-purpose hand washing station |
US11123153B2 (en) * | 2012-09-17 | 2021-09-21 | Sage Products, Llc | Method and system for ensuring and tracking hand hygiene compliance |
US10121149B2 (en) * | 2012-09-17 | 2018-11-06 | Sage Products, Llc | Methods for ensuring and tracking hand hygiene compliance |
US20140253334A1 (en) * | 2013-03-08 | 2014-09-11 | Ecolab Usa Inc. | Method and means for promoting health |
US20140266732A1 (en) * | 2013-03-15 | 2014-09-18 | Theodore R. Barbeau | Hand hygiene compliance system |
WO2014205283A1 (en) | 2013-06-19 | 2014-12-24 | Clean Hands Safe Hands | System and methods for wireless hand hygiene monitoring |
US10082805B2 (en) * | 2013-06-21 | 2018-09-25 | Sdb Ip Holdings, Llc | Removable time adjusting device, system, and method for adjusting an electronic plumbing controller |
EP3033630B1 (en) | 2013-08-12 | 2018-07-18 | University Health Network | Hand hygiene compliance |
JP6201063B2 (en) | 2014-03-10 | 2017-09-20 | ゴジョ・インダストリーズ・インコーポレイテッド | Hygiene compliance tracking method and system |
US9741233B2 (en) | 2014-07-03 | 2017-08-22 | Osla Technologies, L.L.C. | Personnel proximity detection and tracking system |
KR102394131B1 (en) * | 2015-02-25 | 2022-05-04 | 킴벌리-클라크 월드와이드, 인크. | Method and system for consumer reward program for washroom use |
BR112017018568B1 (en) | 2015-03-30 | 2023-03-21 | Kimberly-Clark Worldwide, Inc | METHOD FOR THE MAINTENANCE OF A PLURALITY OF SANITARY FACILITIES BY MAINTENANCE EMPLOYEES |
WO2016182478A1 (en) * | 2015-05-08 | 2016-11-17 | Ринат Жумагалеевич УСМАНГАЛИЕВ | Device for collecting statistical data, intended for a water dispenser |
US9542828B1 (en) | 2015-06-22 | 2017-01-10 | Peter D. Haaland | System, device, and method for measurement of hand hygiene technique |
US10767270B2 (en) | 2015-07-13 | 2020-09-08 | Delta Faucet Company | Electrode for an ozone generator |
US20170086625A1 (en) * | 2015-09-28 | 2017-03-30 | Betco Corporation | Dispenser device incorporating hand hygiene instructions |
CA2946465C (en) | 2015-11-12 | 2022-03-29 | Delta Faucet Company | Ozone generator for a faucet |
US10002518B1 (en) * | 2016-02-18 | 2018-06-19 | OND Creative Solutions, LLC | System and method of biological and germ cross contamination control |
US20170270258A1 (en) * | 2016-03-16 | 2017-09-21 | General Electric Company | Method and system for managing cleaning of medical devices |
US10235865B2 (en) | 2016-04-08 | 2019-03-19 | Hand Scan Llc | System and method for monitoring handwashing compliance |
US10041236B2 (en) | 2016-06-08 | 2018-08-07 | Bradley Corporation | Multi-function fixture for a lavatory system |
US11015329B2 (en) | 2016-06-08 | 2021-05-25 | Bradley Corporation | Lavatory drain system |
WO2018001880A1 (en) * | 2016-06-27 | 2018-01-04 | Konduto Ivs | Dispenser system |
EP3267378A1 (en) * | 2016-07-07 | 2018-01-10 | Smixin SA | Distributed system for resource management for hand hygiene units |
CN110383355B (en) | 2017-03-07 | 2021-08-27 | 埃科莱布美国股份有限公司 | Monitoring module for hand hygiene dispenser |
WO2019074926A1 (en) * | 2017-10-09 | 2019-04-18 | Pathspot Technologies Inc. | Systems and methods for detection of contaminants on surfaces |
US10529219B2 (en) | 2017-11-10 | 2020-01-07 | Ecolab Usa Inc. | Hand hygiene compliance monitoring |
BR112020008043A2 (en) * | 2017-11-29 | 2020-10-06 | Essity Hygiene And Health Aktiebolag | detection and reporting device, system and method for detecting an event |
CA3123862A1 (en) | 2018-12-20 | 2020-06-25 | Ecolab Usa Inc. | Adaptive route, bi-directional network communication |
EP4300441A3 (en) * | 2018-12-21 | 2024-01-24 | Essity Hygiene and Health Aktiebolag | Installation of hygiene equipment |
WO2020142528A1 (en) | 2019-01-02 | 2020-07-09 | Osborne Jr Charles Agnew | Power management system for dispensers |
CN110851686A (en) * | 2019-10-24 | 2020-02-28 | 广州水杯子分质供水工程有限公司 | School direct drinking water sanitation supervision system based on Internet of things |
EP4062412A4 (en) * | 2019-11-19 | 2023-12-20 | Hygiene IQ, LLC | Platform for hygiene behavioral monitoring and modification |
CN111249139B (en) * | 2020-01-22 | 2022-04-29 | 李榕 | Paediatrics skin protection nursing device |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5231594A (en) * | 1989-04-11 | 1993-07-27 | Ernst Knibiehler | Maintenance monitoring system |
US20070096930A1 (en) * | 2005-11-02 | 2007-05-03 | Joseph Cardoso | System and method for detecting proper cleaning of people and items entering a controlled area |
US8085155B2 (en) * | 2006-10-31 | 2011-12-27 | Resurgent Health & Medical, Llc | Sanitizer dispensers with compliance verification |
Family Cites Families (216)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US2325008A (en) | 1940-08-19 | 1943-07-20 | Falk Corp | Spray nozzle |
US2386455A (en) | 1942-06-05 | 1945-10-09 | Hartford Empire Co | Liquid spray discharge apparatus for and method of cooling the interior of bottles and other hollow glass articles |
US2522928A (en) | 1947-11-18 | 1950-09-19 | Monarch Mfg Works Inc | Spraying nozzle |
US2647801A (en) | 1950-10-09 | 1953-08-04 | Lycan Charles Lewis | Paint spraying nozzle |
US2769547A (en) | 1951-06-25 | 1956-11-06 | Hirsch Abraham Adler | Articulated surface washing device with oscillatory nozzles for filter beds |
US2789865A (en) * | 1955-02-03 | 1957-04-23 | Shaver Mfg Company | Mobile watering device |
US2896856A (en) | 1956-12-21 | 1959-07-28 | Licencia Talalmanyokat | Vaporizer for diesel engines |
US2826763A (en) * | 1957-02-04 | 1958-03-18 | Bass Lillian | Spray bathing apparatus with scrubbers |
DE1208732B (en) * | 1960-03-28 | 1966-01-13 | Fmc Corp | Method and device for the extraction of substances from solid material with a hot solvent |
US3059815A (en) | 1960-12-20 | 1962-10-23 | Jr Craig B Parsons | Surgeon's powder dispensing machine |
US3081471A (en) * | 1962-07-16 | 1963-03-19 | Robert E Newell | Hand washing machine |
US3220424A (en) | 1963-05-06 | 1965-11-30 | Warren W Nelson | Hand sanitizer |
US3529774A (en) | 1966-07-26 | 1970-09-22 | Edward W Apri | Adjustable liquid spray apparatus |
US3437274A (en) * | 1966-07-26 | 1969-04-08 | Edward W Apri | Liquid spray apparatus |
US3639844A (en) * | 1969-06-27 | 1972-02-01 | Whirlpool Co | Electronic timer for a multiple function appliance |
US3647147A (en) * | 1970-12-23 | 1972-03-07 | Norton Co | Spray nozzle orifice member |
US3699984A (en) | 1971-01-12 | 1972-10-24 | Charles T Davis | Cleaning and sterilizing device |
CH523059A (en) | 1971-05-06 | 1972-05-31 | Helbling Roman | Flake hand dryer |
US3881328A (en) * | 1971-12-22 | 1975-05-06 | Economics Lab | Electronic detergent dispensing system |
US3757806A (en) | 1972-01-19 | 1973-09-11 | Us Army | Pulsating hydrojet lavage device |
US3754559A (en) | 1972-01-31 | 1973-08-28 | Macleod Co | Drum type washer for metal borings and the like |
US3844278A (en) | 1973-01-26 | 1974-10-29 | Internax Holdings Ltd | Hydrotherapeutic massage device |
US3817651A (en) * | 1973-04-20 | 1974-06-18 | Carrier Corp | Control system having means for expanding the useful frequency response |
US3918987A (en) | 1973-11-09 | 1975-11-11 | Rudolph J Kopfer | Surgeon hand and arm scrubbing apparatus |
US4001599A (en) * | 1974-09-17 | 1977-01-04 | Whirlpool Corporation | Appliance programmer with integrated circuit |
US3918117A (en) | 1974-11-04 | 1975-11-11 | Lucille I Plante | Surgical washing device |
US3997873A (en) | 1975-03-31 | 1976-12-14 | Manitou Systems, Inc. | Multiterminal monitoring system |
US3967478A (en) | 1975-06-09 | 1976-07-06 | Guinn Stanley G | Door latching apparatus actuated by cleansing agent sensor |
GB1558566A (en) * | 1975-09-26 | 1980-01-03 | Wiggin & Co Ltd Henry | Apparatus for treating small articles with liquid |
US3992730A (en) | 1975-12-02 | 1976-11-23 | Edwin Dyer Davis | Scrub sink |
US4020856A (en) * | 1976-06-28 | 1977-05-03 | Masterson Albert C | Fingernail and hand cleaning appliance |
US4120180A (en) | 1977-05-10 | 1978-10-17 | Jedora John J | Machine for cleaning a fabric workpiece |
US4137929A (en) * | 1977-07-29 | 1979-02-06 | Grossman Peter J | Fingernail cleaner |
US4295233A (en) | 1977-12-30 | 1981-10-20 | Whirlpool Corporation | Automatic hand washer and drier |
US4219367A (en) | 1978-10-05 | 1980-08-26 | Cary George R Jr | Surgical prep hand cleaning |
JPS6027295B2 (en) | 1979-03-26 | 1985-06-28 | マシ−ネンフアブリ−ク アド シユ−ルテス ウント コンパニ− ア−ゲ− | hand washing device |
US4275385A (en) * | 1979-08-13 | 1981-06-23 | Bell Telephone Laboratories, Incorporated | Infrared personnel locator system |
USRE35035E (en) | 1980-10-06 | 1995-09-12 | Fisher Berkeley Corporation | Locating system and method |
US4601064A (en) | 1983-01-13 | 1986-07-15 | Fisher Berkeley Corporation | Communication system |
US4496519A (en) * | 1981-03-09 | 1985-01-29 | Mcguire Paul J | Nuclear reactor vessel decontamination systems |
US4402331A (en) | 1981-03-27 | 1983-09-06 | Delta Manufacturing And Sales, Inc. | Portable lavage device |
US4453286A (en) * | 1983-04-21 | 1984-06-12 | Wieland Clarence W | Vacuum induced trash collection system |
US4509543A (en) * | 1983-09-12 | 1985-04-09 | Beta Technology, Inc. | Industrial dishwasher monitor/controller with speech capability |
IT8421362V0 (en) * | 1984-03-26 | 1984-03-26 | Dragone Giorgio | DEVICE FOR DERMATOLOGICAL TREATMENT OF HANDS. |
US4606500A (en) | 1984-10-01 | 1986-08-19 | Rain Bird Consumer Products Mfg. Corp. | Releasable coupling assembly for oscillating wave lawn sprinkler |
US4606085A (en) | 1985-03-27 | 1986-08-19 | Davies Joseph R | Hand washing device |
DE3582065D1 (en) | 1985-04-10 | 1991-04-11 | Vetter & Co Apotheker | WASHING MACHINE FOR CLEANING ITEMS. |
US5238749A (en) | 1986-03-27 | 1993-08-24 | Clinitex Corporation | Antimicrobial coating process and product |
US4999613A (en) * | 1987-04-21 | 1991-03-12 | Guardian Technologies, Inc. | Remote confinement system |
US4769863A (en) | 1987-06-19 | 1988-09-13 | Satellite Industries, Inc. | Hand wash unit |
USRE33810E (en) * | 1987-07-17 | 1992-02-04 | Portable isolation enclosure for use in cleaning contaminated environments | |
US4817651A (en) * | 1987-10-26 | 1989-04-04 | Scientific Growth, Inc. | Hand and forearm cleansing apparatus |
US4925495A (en) * | 1988-01-25 | 1990-05-15 | Scientific Growth, Inc. | Washing apparatus and method |
US4916435A (en) * | 1988-05-10 | 1990-04-10 | Guardian Technologies, Inc. | Remote confinement monitoring station and system incorporating same |
CA1307078C (en) | 1988-06-29 | 1992-09-08 | Rudy Rosa | Hand sanitizing station |
US4896144A (en) * | 1988-09-29 | 1990-01-23 | Bogstad Naomi C | Hand washing alert |
US4921211A (en) * | 1989-02-24 | 1990-05-01 | Recurrent Solutions Limited Partnership | Method and apparatus for flow control |
IT1229331B (en) | 1989-05-03 | 1991-08-08 | Tecnobios S R L | AUTOMATIC HAND CLEANING DEVICE AND RELATED PROCEDURE. |
US5016172A (en) * | 1989-06-14 | 1991-05-14 | Ramp Comsystems, Inc. | Patient compliance and status monitoring system |
US5031258A (en) | 1989-07-12 | 1991-07-16 | Bauer Industries Inc. | Wash station and method of operation |
US5781942A (en) | 1989-07-12 | 1998-07-21 | Sloan Valve Company | Wash stations and method of operation |
US5060323A (en) | 1989-07-12 | 1991-10-29 | Bauer Industries, Inc. | Modular system for automatic operation of a water faucet |
US5086526A (en) * | 1989-10-10 | 1992-02-11 | International Sanitary Ware Manufacturin Cy, S.A. | Body heat responsive control apparatus |
FR2659217A1 (en) | 1990-03-08 | 1991-09-13 | Lechartier Marcel | Handwasher with automatic hot air recycling |
GB2244001A (en) * | 1990-04-30 | 1991-11-20 | Victor Paul Melech | Hand and forearm cleaning device |
US5119104A (en) * | 1990-05-04 | 1992-06-02 | Heller Alan C | Location system adapted for use in multipath environments |
US5594786A (en) | 1990-07-27 | 1997-01-14 | Executone Information Systems, Inc. | Patient care and communication system |
US5465082A (en) | 1990-07-27 | 1995-11-07 | Executone Information Systems, Inc. | Apparatus for automating routine communication in a facility |
US5455851A (en) | 1993-07-02 | 1995-10-03 | Executone Information Systems, Inc. | System for identifying object locations |
US5291399A (en) * | 1990-07-27 | 1994-03-01 | Executone Information Systems, Inc. | Method and apparatus for accessing a portable personal database as for a hospital environment |
US5822544A (en) | 1990-07-27 | 1998-10-13 | Executone Information Systems, Inc. | Patient care and communication system |
US5074322A (en) | 1990-12-06 | 1991-12-24 | Jaw Chin Woei | Structure of sterilizing hand dryer |
US5257423A (en) | 1990-12-31 | 1993-11-02 | Leer Manufacturing Limited Partnership | Service island wash station enclosure |
US5202666A (en) * | 1991-01-18 | 1993-04-13 | Net/Tech International Inc. | Method and apparatus for enhancing hygiene |
US5199118A (en) * | 1991-02-11 | 1993-04-06 | World Dryer, Division Of Specialty Equipment Companies, Inc. | Hand wash station |
US5184642A (en) * | 1991-05-22 | 1993-02-09 | Powell Jay H | Automatic water faucet or water faucet controller |
US5503840A (en) * | 1991-08-09 | 1996-04-02 | E. I. Du Pont De Nemours And Company | Antimicrobial compositions, process for preparing the same and use |
US5340581A (en) | 1991-08-23 | 1994-08-23 | Gillette Canada, Inc. | Sustained-release matrices for dental application |
US6125482A (en) | 1991-11-22 | 2000-10-03 | H.M.S.I. Limited | Hand washing unit |
GB9124819D0 (en) | 1991-11-22 | 1992-01-15 | Manufacturers Agents Limited | Hand washing unit |
US5265628A (en) | 1992-06-02 | 1993-11-30 | Meritech, Inc. | Automated cleansing chamber |
US20020104083A1 (en) | 1992-12-09 | 2002-08-01 | Hendricks John S. | Internally targeted advertisements using television delivery systems |
US5387993A (en) * | 1993-06-25 | 1995-02-07 | Precision Tracking Fm, Inc. | Method for receiving and transmitting optical data and control information to and from remotely located receivers and transmitters in an optical locator system |
US5699038A (en) | 1993-07-12 | 1997-12-16 | Hill-Rom, Inc. | Bed status information system for hospital beds |
US5561412A (en) | 1993-07-12 | 1996-10-01 | Hill-Rom, Inc. | Patient/nurse call system |
US5838223A (en) | 1993-07-12 | 1998-11-17 | Hill-Rom, Inc. | Patient/nurse call system |
US5548637A (en) | 1993-09-09 | 1996-08-20 | Precision Tracking Fm, Inc. | Method and apparatus for locating personnel and objects in response to telephone inquiries |
US5601100A (en) * | 1993-10-28 | 1997-02-11 | Mitsubishi Denki Kabushiki Kaisha | Washing apparatus |
US5515426A (en) | 1994-02-28 | 1996-05-07 | Executone Information Systems, Inc. | Telephone communication system having a locator |
US5793653A (en) * | 1994-07-12 | 1998-08-11 | Segal; Noel B. | Apparatus and method for monitoring compliance with handsink use regimen |
US20020019709A1 (en) * | 1994-07-12 | 2002-02-14 | Segal Noel B. | System for controlling operation of a sink |
US6236953B1 (en) * | 1994-07-12 | 2001-05-22 | Compliance Control, Inc. | System for monitoring compliance with apparatuses having predetermined operating parameters |
US5572195A (en) | 1994-08-01 | 1996-11-05 | Precision Tracking Fm, Inc. | Sensory and control system for local area networks |
JP3455744B2 (en) * | 1994-09-21 | 2003-10-14 | ヒルーロム サービスィズ,インコーポレーテッド | Optical data communication and position determining device, system and method, and transmitter and receiver for use therein |
US5765242A (en) * | 1994-11-30 | 1998-06-16 | Marciano; Joseph | Hand sanitizing apparatus |
US5702115A (en) | 1995-01-10 | 1997-12-30 | Pool; L. Frank | Patient care utility cart |
US5610589A (en) * | 1995-02-09 | 1997-03-11 | Bennie R. Evans | Method and apparatus for enforcing hygiene |
US7069451B1 (en) | 1995-02-13 | 2006-06-27 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5845225A (en) | 1995-04-03 | 1998-12-01 | Mosher; Frederick A. | Microcomputer controlled engine cleaning system |
US5900067A (en) * | 1995-05-16 | 1999-05-04 | Jones; C. Kerry | Handwashing technique analysis |
US6524390B1 (en) * | 1995-05-16 | 2003-02-25 | C. Kerry Jones | Handwashing technique analysis |
US5670945A (en) | 1995-07-06 | 1997-09-23 | Applonie; Alan R. | Self-monitoring hand-sanitizing station |
GB2328867B (en) | 1995-08-10 | 1999-04-28 | Hmsi | Handwash station |
US5695091A (en) | 1995-10-25 | 1997-12-09 | The Path-X Corporation | Automated dispenser for disinfectant with proximity sensor |
US5945068A (en) | 1996-01-26 | 1999-08-31 | Ferone; Daniel A. | Ozone hand sterilizer |
US5812059A (en) | 1996-02-23 | 1998-09-22 | Sloan Valve Company | Method and system for improving hand cleanliness |
US5863497A (en) * | 1996-03-11 | 1999-01-26 | The Proctor & Gamble Company | Electrostatic hand sanitizer |
US5774865A (en) * | 1996-04-19 | 1998-06-30 | Ideal Ideas, Inc. | Patient compliance and monitoring system for multiple regimens using a movable bar code reader |
US5727579A (en) * | 1996-05-29 | 1998-03-17 | 144 Limited Partnership | Automatic hand washing and drying apparatus including combined blow drying means and towel dispensing means |
US5860437A (en) * | 1996-08-07 | 1999-01-19 | Csia Research Foundation | Self-cleaning hand washer |
US5823447A (en) | 1996-08-27 | 1998-10-20 | Meritech, Inc. | Angled fan nozzle and unibody cylinder |
GB9625976D0 (en) | 1996-12-13 | 1997-01-29 | Hmsi Limited | Handwash apparatus |
AU6162898A (en) | 1997-02-18 | 1998-09-08 | Johnson, Raymond C. | Apparatus and method for monitoring hand washing |
US5870015A (en) * | 1997-03-14 | 1999-02-09 | Hinkel; Scott E. | Method and apparatus for instruction in toilet use and hygiene |
GB2324397A (en) | 1997-04-16 | 1998-10-21 | Michael Richard Goodier | Hand washing reminder alarm |
US6431189B1 (en) | 1997-06-02 | 2002-08-13 | 700303 Alberta Ltd. | Apparatus for and method of disinfecting hands |
US6110292A (en) * | 1997-08-12 | 2000-08-29 | Warren R. Jewett | Oscillating liquid jet washing system |
US5808553A (en) | 1997-10-29 | 1998-09-15 | Cunningham; William B. | Apparatus for enforcing hygiene |
AU1367699A (en) | 1997-11-03 | 1999-05-24 | Arial Systems Corporation | Personnel and asset tracking method and apparatus |
US7010369B2 (en) * | 1997-11-07 | 2006-03-07 | Hill-Rom Services, Inc. | Medical equipment controller |
US5952924A (en) | 1997-12-04 | 1999-09-14 | Bennie R. Evans | Method and apparatus for enforcing hygiene |
US6195588B1 (en) * | 1997-12-31 | 2001-02-27 | Sloan Valve Company | Control board for controlling and monitoring usage of water |
US5966753A (en) | 1997-12-31 | 1999-10-19 | Sloan Valve Company | Method and apparatus for properly sequenced hand washing |
US6038519A (en) * | 1997-12-31 | 2000-03-14 | Sloan Valve Company | Control board for controlling and monitoring usage of water |
US5945910A (en) * | 1998-02-11 | 1999-08-31 | Simoniz Usa, Inc. | Method and apparatus for monitoring and reporting handwashing |
US5924148A (en) | 1998-02-26 | 1999-07-20 | Flowers, Sr.; Stanley E. | Automatic hand washing and drying machine |
US5939974A (en) | 1998-02-27 | 1999-08-17 | Food Safety Solutions Corp. | System for monitoring food service requirements for compliance at a food service establishment |
US5900801A (en) * | 1998-02-27 | 1999-05-04 | Food Safety Solutions Corp. | Integral master system for monitoring food service requirements for compliance at a plurality of food service establishments |
US6236317B1 (en) * | 1998-04-29 | 2001-05-22 | Food Safety Solution Corp. | Method and apparatus for monitoring actions taken by a user for enhancing hygiene |
US6404837B1 (en) * | 1998-06-11 | 2002-06-11 | Ecolab, Inc. | Usage competent hand soap dispenser with data collection and display capabilities |
US6399853B1 (en) | 1998-06-29 | 2002-06-04 | The Proctor & Gamble Company | Disposable article having fecal component sensor |
US6424262B2 (en) | 1998-08-14 | 2002-07-23 | 3M Innovative Properties Company | Applications for radio frequency identification systems |
CN1312928A (en) * | 1998-08-14 | 2001-09-12 | 3M创新有限公司 | Application for a radio frequency identification system |
AU762475B2 (en) | 1998-08-14 | 2003-06-26 | 3M Innovative Properties Company | Applications for radio frequency identification systems |
CN100492388C (en) | 1998-08-14 | 2009-05-27 | 3M创新有限公司 | Radio frequency identification system applications |
US5992430A (en) | 1998-09-28 | 1999-11-30 | 144 Limited Partnership | Automatic hand washing and drying apparatus including combined blow drying means, towel dispensing means and waste disposal means |
US6131587A (en) | 1998-09-28 | 2000-10-17 | 144 Limited Partnership | Hand washing and drying apparatus and system including waste disposal apparatus and method |
US5966573A (en) | 1998-10-08 | 1999-10-12 | Xerox Corporation | Seamed flexible electrostatographic imaging belt having a permanent localized solid attribute |
US6031461A (en) * | 1998-10-13 | 2000-02-29 | Lynn; John M. | Method and apparatus for helping to assure the washing of hands |
US6147607A (en) * | 1998-10-13 | 2000-11-14 | Lynn; John M. | Method and apparatus for helping to assure the washing of hands |
US6029600A (en) * | 1998-11-23 | 2000-02-29 | Davis; Claude G. | Clean hands assured |
US5979500A (en) | 1999-01-19 | 1999-11-09 | Arichel Technologies, Inc. | Duration-indicating automatic faucet |
US6235351B1 (en) * | 1999-01-22 | 2001-05-22 | Northrop Grumman Corporation | Method for producing a self decontaminating surface |
DE19903079C2 (en) | 1999-01-27 | 2003-04-10 | Ophardt Product Kg | Procedure for monitoring disinfectant consumption in hospital rooms |
US6317717B1 (en) | 1999-02-25 | 2001-11-13 | Kenneth R. Lindsey | Voice activated liquid management system |
US6343425B1 (en) * | 1999-05-06 | 2002-02-05 | Intecon Systems, Inc. | Measurement and cleaning of elastomeric articles having particulate adhered thereto |
US6037871A (en) * | 1999-08-05 | 2000-03-14 | Babylon; Stephen K. | Bathroom hygiene training system |
US6161227A (en) | 1999-08-17 | 2000-12-19 | Bargenquast; Scott | Portable hand cleaning device |
US6539393B1 (en) | 1999-09-30 | 2003-03-25 | Hill-Rom Services, Inc. | Portable locator system |
US6727818B1 (en) | 1999-10-29 | 2004-04-27 | Hill-Rom Services, Inc. | Hygiene monitoring system |
US6542568B1 (en) * | 1999-12-09 | 2003-04-01 | Ecolab Inc. | Soap dispenser having reward program |
FR2802792B1 (en) * | 1999-12-24 | 2002-05-03 | Genie Et Environnement | IMPROVED HAND CLEANING DEVICE |
US6268797B1 (en) | 2000-03-15 | 2001-07-31 | Detection Systems, Inc. | Integrated portable tracking signal and access authorization signal generator |
JP2001259539A (en) | 2000-03-24 | 2001-09-25 | Ricoh Co Ltd | Cleaning system and cleaning method |
US6278372B1 (en) | 2000-06-01 | 2001-08-21 | Ecolab Inc. | Methods and apparatus for promoting hygiene |
US20060122474A1 (en) | 2000-06-16 | 2006-06-08 | Bodymedia, Inc. | Apparatus for monitoring health, wellness and fitness |
DE60119100T2 (en) | 2000-06-23 | 2006-08-31 | Bodymedia, Inc. | SYSTEM FOR THE MONITORING OF HEALTH, WELL-BEING AND CONDITION |
US6577240B2 (en) * | 2000-06-30 | 2003-06-10 | David N. Armstrong | Hand antiseptic system and method |
US6413921B1 (en) | 2000-08-01 | 2002-07-02 | Allegiance Corporation | Antimicrobial composition containing parachlorometaxylenol (PCMX) |
DE10042165C1 (en) * | 2000-08-17 | 2002-04-18 | Butzke Werke Aqua | System for controlling and monitoring sanitary fittings |
US6392546B1 (en) * | 2000-09-07 | 2002-05-21 | Judson L. Smith | Hand washing compliance measurement and recording system |
US6426701B1 (en) | 2000-09-20 | 2002-07-30 | Ultraclenz Engineering Group | Handwash monitoring system |
EP1322822B1 (en) | 2000-10-03 | 2004-02-04 | Edo Lang | Washing unit with a device for controlling and/or regulating the supply of a medium and a corresponding method |
JP4564179B2 (en) * | 2000-10-17 | 2010-10-20 | サラヤ株式会社 | Fluid supply device |
US6956498B1 (en) | 2000-11-02 | 2005-10-18 | Sloan Valve Company | System for remote operation of a personal hygiene or sanitary appliance |
US6832916B2 (en) | 2000-11-20 | 2004-12-21 | Venture Management Alliance, Llc | Soap dispenser hand wash interval timer |
US6671890B2 (en) * | 2000-12-15 | 2004-01-06 | San-Ei Faucet Mfg. Co., Ltd. | Automatic water feed method in lavatory using artificial retina sensor and automatic water feed mechanism in lavatory using artificial retina sensor |
US6975231B2 (en) * | 2001-01-23 | 2005-12-13 | Amron Corporation | Systems and methods for improving hand hygiene compliance |
US6970574B1 (en) | 2001-03-13 | 2005-11-29 | Johnson Raymond C | Pattern recognition system and method for monitoring hand washing or application of a disinfectant |
DE10159395B4 (en) | 2001-12-04 | 2010-11-11 | Braun Gmbh | Device for cleaning teeth |
US20020135486A1 (en) | 2001-03-23 | 2002-09-26 | Per Brohagen | Device and procedure for surveillance of the use of a hygiene station |
US7242306B2 (en) | 2001-05-08 | 2007-07-10 | Hill-Rom Services, Inc. | Article locating and tracking apparatus and method |
EP1386285A1 (en) | 2001-05-08 | 2004-02-04 | Hill-Rom Services, Inc. | Article locating and tracking system |
US20020175182A1 (en) | 2001-05-23 | 2002-11-28 | Matthews Shaun Kerry | Self contained dispenser incorporating a user monitoring system |
CA2443678A1 (en) | 2001-05-25 | 2002-12-05 | Hill-Rom Services, Inc. | A waste segregation compliance system |
US6417773B1 (en) | 2001-06-21 | 2002-07-09 | Gust N. Vlahos | Sound-actuated system for encouraging good personal hygiene in toilet facilities |
US6883563B2 (en) * | 2001-07-26 | 2005-04-26 | Judson L. Smith | Apparatus and method to monitor the usage of a network system of personal hand sanitizing dispensers |
US6351866B1 (en) * | 2001-08-31 | 2002-03-05 | Reiner George Bragulla | Arm scrubbing system |
US20030069815A1 (en) * | 2001-10-10 | 2003-04-10 | 3M Innovative Properties Company | RFID time tracking |
US6669089B2 (en) * | 2001-11-12 | 2003-12-30 | 3M Innovative Properties Co | Radio frequency identification systems for asset tracking |
WO2003082351A2 (en) * | 2002-03-22 | 2003-10-09 | Path-X International, Inc. | Hand-washing monitoring system |
US20030197122A1 (en) | 2002-04-22 | 2003-10-23 | Faiola Norman A. | System and method for tracking germ contamination |
US8611919B2 (en) | 2002-05-23 | 2013-12-17 | Wounder Gmbh., Llc | System, method, and computer program product for providing location based services and mobile e-commerce |
JP3828871B2 (en) | 2002-06-04 | 2006-10-04 | 本田技研工業株式会社 | Article washing equipment |
US6902397B2 (en) | 2002-08-01 | 2005-06-07 | Sunstar Americas, Inc. | Enhanced dental hygiene system with direct UVA photoexcitation |
US7020508B2 (en) * | 2002-08-22 | 2006-03-28 | Bodymedia, Inc. | Apparatus for detecting human physiological and contextual information |
US6733595B1 (en) * | 2002-09-04 | 2004-05-11 | Alphonse Grillo | Footbrush device and method of using |
CA2501732C (en) | 2002-10-09 | 2013-07-30 | Bodymedia, Inc. | Method and apparatus for auto journaling of continuous or discrete body states utilizing physiological and/or contextual parameters |
US7023980B2 (en) * | 2002-12-04 | 2006-04-04 | Avaya Technology Corp. | Outbound dialing decision criteria based |
US7174577B2 (en) * | 2003-01-16 | 2007-02-13 | Technical Concepts, Llc | Automatic proximity faucet |
US7293645B2 (en) | 2003-01-30 | 2007-11-13 | Judith Lee Harper | Method for monitoring hand hygiene compliance |
US6892143B2 (en) * | 2003-05-22 | 2005-05-10 | Ecolab Inc. | Controlling chemical dispense operations based on conductivity offset |
US20050139239A1 (en) | 2003-10-13 | 2005-06-30 | Prae Gary L. | Electrostatic hand cleanser apparatus and method of use |
US7242307B1 (en) * | 2003-10-20 | 2007-07-10 | Cognetive Systems Incorporated | System for monitoring hygiene appliances |
US20050134465A1 (en) | 2003-12-06 | 2005-06-23 | Rice Johnathan W. | Hand cleansing device with monitoring capability |
JP2005177389A (en) | 2003-12-24 | 2005-07-07 | Iwao Hishida | Method for washing and sterilizing finger |
US7783380B2 (en) * | 2003-12-31 | 2010-08-24 | Kimberly-Clark Worldwide, Inc. | System and method for measuring, monitoring and controlling washroom dispensers and products |
US7150293B2 (en) | 2004-01-12 | 2006-12-19 | Masco Corporation Of Indiana | Multi-mode hands free automatic faucet |
US7477148B2 (en) | 2004-06-01 | 2009-01-13 | Airborne Health, Inc | Soap dispenser and method for assuring clean hands |
US7195861B2 (en) | 2004-07-08 | 2007-03-27 | Agfa-Gevaert | Method for making a negative working, heat-sensitive lithographic printing plate precursor |
US7443305B2 (en) | 2004-10-06 | 2008-10-28 | Verdiramo Vincent L | Hand wash monitoring system and method |
US7423533B1 (en) * | 2004-10-19 | 2008-09-09 | Cognetive Systems, Incorporated | System for monitoring and recording cross-contamination events |
USD512648S1 (en) | 2004-12-15 | 2005-12-13 | Smith Judson L | Dispenser for fluid material |
US20060241396A1 (en) | 2005-02-10 | 2006-10-26 | Fabian Carl E | Multi-modal detection of surgical sponges and implements |
US7178729B2 (en) * | 2005-02-25 | 2007-02-20 | Cisco Technology, Inc. | Methods and devices for providing alerts for spoilage and hazardous combinations |
US7271719B2 (en) | 2005-03-15 | 2007-09-18 | Industrial Technology Research Institute | RFID system for monitoring food hygiene |
US20060229891A1 (en) | 2005-04-06 | 2006-10-12 | Ryko Manufacturing Company | Drive-up dispensing device for car wash facility |
US7271728B2 (en) * | 2005-06-13 | 2007-09-18 | Gojo Industries, Inc. | Method for assessing improvement in hand hygiene practices |
US20070020212A1 (en) * | 2005-07-19 | 2007-01-25 | Jesse Bernal | System and method to promote proper handwashing |
WO2007127495A2 (en) | 2006-05-03 | 2007-11-08 | Duke University & Duke University Health Systems | Rf controlled devices to increase compliance with handwashing protocols |
US20080001763A1 (en) | 2006-06-29 | 2008-01-03 | Raja Vishnu R | Hand washing compliance system |
US20080031838A1 (en) | 2006-08-03 | 2008-02-07 | Bolling Steven F | Tracing hand cleaner |
US7698770B2 (en) * | 2006-10-31 | 2010-04-20 | Resurgent Health & Medical, Llc | Automated appendage cleaning apparatus with brush |
US7607443B2 (en) * | 2006-10-31 | 2009-10-27 | Resurgent Health & Medical, Llc | Wash chamber for automated appendage-washing apparatus |
GB0624773D0 (en) | 2006-12-13 | 2007-01-17 | Validated Hygiene Solutions Lt | A facility decontaminaton system |
US20100155420A1 (en) | 2008-12-19 | 2010-06-24 | Resurgent Health & Medical,Llc | Dispensing System for Cleaning Devices |
-
2007
- 2007-09-07 US US11/852,099 patent/US7818083B2/en active Active
- 2007-10-31 WO PCT/US2007/083221 patent/WO2008055228A2/en active Application Filing
- 2007-10-31 EP EP07863731A patent/EP2078271A4/en not_active Withdrawn
-
2010
- 2010-09-13 US US12/880,946 patent/US20100326472A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5231594A (en) * | 1989-04-11 | 1993-07-27 | Ernst Knibiehler | Maintenance monitoring system |
US20070096930A1 (en) * | 2005-11-02 | 2007-05-03 | Joseph Cardoso | System and method for detecting proper cleaning of people and items entering a controlled area |
US8085155B2 (en) * | 2006-10-31 | 2011-12-27 | Resurgent Health & Medical, Llc | Sanitizer dispensers with compliance verification |
US8110047B2 (en) * | 2006-10-31 | 2012-02-07 | Resurgent Health & Medical, Llc | Automated washing system with compliance verification |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100095983A1 (en) * | 2006-10-31 | 2010-04-22 | Resurgent Health & Medical,Llc | Automated appendage cleaning apparatus with brush |
US8085155B2 (en) | 2006-10-31 | 2011-12-27 | Resurgent Health & Medical, Llc | Sanitizer dispensers with compliance verification |
US8110047B2 (en) | 2006-10-31 | 2012-02-07 | Resurgent Health & Medical, Llc | Automated washing system with compliance verification |
US8146613B2 (en) | 2008-04-29 | 2012-04-03 | Resurgent Health & Medical, Llc | Wash chamber for surgical environment |
US8294585B2 (en) | 2008-04-29 | 2012-10-23 | Resurgent Health & Medical, Llc | Complete hand care |
US8377229B2 (en) | 2008-04-29 | 2013-02-19 | Resurgent Health & Medical, Llc | Ingress/egress system for hygiene compliance |
US8400309B2 (en) | 2008-04-29 | 2013-03-19 | Resurgent Health & Medical, Llc | Hygiene compliance |
US20100155420A1 (en) * | 2008-12-19 | 2010-06-24 | Resurgent Health & Medical,Llc | Dispensing System for Cleaning Devices |
US9824569B2 (en) | 2011-01-28 | 2017-11-21 | Ecolab Usa Inc. | Wireless communication for dispenser beacons |
WO2014074585A1 (en) | 2012-11-06 | 2014-05-15 | Johnson Raymond C | Virtual hand-washing coach |
WO2017112795A1 (en) * | 2015-12-21 | 2017-06-29 | Delta Faucet Company | Fluid delivery system including a disinfectant device |
CN108463437A (en) * | 2015-12-21 | 2018-08-28 | 德尔塔阀门公司 | Fluid delivery system including chlorination equipment |
CN115093008A (en) * | 2015-12-21 | 2022-09-23 | 德尔塔阀门公司 | Fluid delivery system comprising a disinfection device |
US11458214B2 (en) * | 2015-12-21 | 2022-10-04 | Delta Faucet Company | Fluid delivery system including a disinfectant device |
WO2018090399A1 (en) * | 2016-11-21 | 2018-05-24 | 今日天鸿(天津)医疗卫生科技有限公司 | Internet of things based intelligent liquid extractor system and liquid extracting method |
US20200183354A1 (en) * | 2018-12-05 | 2020-06-11 | Juki Corporation | Monitoring system |
US11382995B2 (en) | 2020-07-24 | 2022-07-12 | 3Oe Scientific, LLC | Hand sanitizing aqueous ozone spray chamber |
US11389555B2 (en) | 2020-07-24 | 2022-07-19 | 3Oe Scientific, LLC | Aqueous ozone sanitizing system with ozone generator cartridge docking station |
US11534513B2 (en) | 2020-07-24 | 2022-12-27 | 3Oe Scientific, LLC | Docking ozone generator cartridge for ozonating water |
US11534514B2 (en) | 2020-07-24 | 2022-12-27 | 3Oe Scientific, LLC | Aqueous ozone generator cartridge with a water treatment manifold |
US11638768B2 (en) | 2020-07-24 | 2023-05-02 | 3Oe Scientific, LLC | Aqueous ozone generator controller and methods |
Also Published As
Publication number | Publication date |
---|---|
EP2078271A4 (en) | 2010-06-09 |
WO2008055228A2 (en) | 2008-05-08 |
US20080103636A1 (en) | 2008-05-01 |
EP2078271A2 (en) | 2009-07-15 |
US7818083B2 (en) | 2010-10-19 |
WO2008055228A3 (en) | 2008-10-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7818083B2 (en) | Automated washing system with compliance verification and automated compliance monitoring reporting | |
US7682464B2 (en) | Automated washing system with compliance verification | |
US8400309B2 (en) | Hygiene compliance | |
US20210350922A1 (en) | Methods for tracking hygiene compliance | |
US8742932B2 (en) | Hand wash and sanitation device | |
US10121149B2 (en) | Methods for ensuring and tracking hand hygiene compliance | |
US8249295B2 (en) | System for monitoring hand cleaning compliance | |
US20160117912A1 (en) | System and method for monitoring hospital workflow compliance with a hand hygiene network | |
US20120310664A1 (en) | System and Method for Monitoring Hospital Workflow Compliance with a Hand Hygiene Network | |
WO2008156956A1 (en) | System for maximizing the effectiveness of caregiving | |
US9892620B2 (en) | System and method for preventing transfer of infectious disease | |
NZ576011A (en) | Method and apparatus for generating patient reminders | |
WO2009134242A1 (en) | Sanitizer dispensers with compliance verification | |
GB2497992A (en) | Drip tray for monitoring hygiene standards compliance | |
Săndulescu et al. | Dispatching and management center for optimizing home care integrated services | |
Cantrell | Seeing is believing: electronic hand-hygiene systems take compliance to the next level | |
Cantrell | Seeing is believing | |
Warkad et al. | STRATEGIES TO ENSURE HIGH COMPLIANCE OF NABH IN A MULTI SPECIALITY HOSPITAL IN PUNE CITY | |
Ewings et al. | Blainroe Lodge, Coast Road, Blainroe, Wicklow. | |
Zeng et al. | Exploring the application opportunities of RFID in an Elderly Center |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: RESURGENT HEALTH & MEDICAL, LLC, COLORADO Free format text: MERGER;ASSIGNOR:ICON SYSTEMS, LLC;REEL/FRAME:024978/0529 Effective date: 20080915 Owner name: ICON SYSTEMS, LLC, COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GLENN, JAMES;SWARTZ, DOUGLAS W.;SIGNING DATES FROM 20070925 TO 20071005;REEL/FRAME:024978/0507 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |