U.S. patent application number 14/678115 was filed with the patent office on 2015-08-20 for hand hygiene compliance system.
The applicant listed for this patent is Georgia-Pacific Consumer Products LP. Invention is credited to Morgan Lowery, Michael J. Pelland, Richard S. Walters.
Application Number | 20150235550 14/678115 |
Document ID | / |
Family ID | 45004699 |
Filed Date | 2015-08-20 |
United States Patent
Application |
20150235550 |
Kind Code |
A1 |
Pelland; Michael J. ; et
al. |
August 20, 2015 |
HAND HYGIENE COMPLIANCE SYSTEM
Abstract
A system and method for performing hand hygiene compliance. The
method includes receiving a notification that an individual has
entered a physical location. The notification is received by a node
in a wireless mesh network that includes a plurality of nodes
corresponding to objects in the physical location. A hand hygiene
protocol is identified for the individual. It is determined that
the individual has not followed the hand hygiene protocol. The
determining is performed by software executing on the nodes in the
wireless mesh network and responsive to a previous and a current
location of the individual relative to the objects in the physical
location. The individual is notified in response to determining
that the individual has not followed the hand hygiene protocol.
Inventors: |
Pelland; Michael J.;
(Princeton, WI) ; Lowery; Morgan; (DeForest,
WI) ; Walters; Richard S.; (Hugo, MN) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Georgia-Pacific Consumer Products LP |
Atlanta |
GA |
US |
|
|
Family ID: |
45004699 |
Appl. No.: |
14/678115 |
Filed: |
April 3, 2015 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
13114216 |
May 24, 2011 |
9000930 |
|
|
14678115 |
|
|
|
|
61347715 |
May 24, 2010 |
|
|
|
Current U.S.
Class: |
340/573.1 |
Current CPC
Class: |
G08B 21/245 20130101;
G01S 5/02 20130101; G08B 21/24 20130101; G08B 21/22 20130101 |
International
Class: |
G08B 21/24 20060101
G08B021/24 |
Claims
1. A computer implemented method for monitoring the performance of
hand hygiene compliance, the method comprising: identifying, via a
node in a wireless mesh network, that an individual has entered a
physical location, the wireless mesh network comprising a plurality
of nodes corresponding to objects in the physical location;
identifying a hand hygiene protocol for the individual; determining
that the individual has not followed the hand hygiene protocol; and
in response to determining that the individual has not followed the
hand hygiene protocol, generating a notification indicative thereof
and viewable by the individual, wherein the notification is
generated at least in part based upon one or more predefined
preferences, the one or more predefined preferences being
associated with at least one of the individual or one or more
parameters dependent upon the physical location.
2. The method of claim 1 wherein the notification is further
generated based at least in part on a patient status.
3. The method of claim 1, wherein the notifying includes one or
more of an audio, visual, and haptic alert.
4. The method of claim 3, wherein the selection of the one or more
of the audio, visual, and haptic alert is based at least in part on
the one or more predefined preferences.
5. The method of claim 1, further comprising transmitting data to a
central monitoring location in response to determining that the
individual has not followed the hand hygiene protocol.
6. The method of claim 1, further comprising transmitting data to a
central monitoring location in response to detecting activity
associated with the hand hygiene protocol.
7. A computer implemented method for monitoring the performance of
hand hygiene compliance, the method comprising: identifying, via a
node in a wireless mesh network, that an individual has entered a
physical location, the wireless mesh network comprising a plurality
of nodes corresponding to objects in the physical location;
identifying a hand hygiene protocol for the individual, wherein the
identified hand hygiene protocol is identified at least in part by
one or more nodes in the wireless mesh network and in the vicinity
of the individual and is based at least in part on a patient
treatment that could be provided by the individual in the physical
location; determining that the individual has not followed the hand
hygiene protocol; and notifying the individual in response to
determining that the individual has not followed the hand hygiene
protocol.
8. The method of claim 7 wherein the notification is further
generated based at least in part on at least one of a status
associated with a patient or characteristics of the physical
location.
9. The method of claim 7, wherein the notifying includes one or
more of an audio, visual, and haptic alert.
10. The method of claim 9, wherein the selection of the one or more
of the audio, visual, and haptic alert is based at least in part on
at least one of a status associated with a patient or
characteristics of the physical location.
11. The method of claim 7, further comprising transmitting data to
a central monitoring location in response to determining that the
individual has not followed the hand hygiene protocol.
12. The method of claim 7, further comprising transmitting data to
a central monitoring location in response to detecting activity
associated with the hand hygiene protocol.
13. A computer implemented method for monitoring the performance of
hand hygiene compliance, the method comprising: identifying, via a
node in a wireless mesh network, that an individual has entered a
physical location, the wireless mesh network comprising a plurality
of nodes corresponding to objects in the physical location;
identifying a hand hygiene protocol for the individual, wherein the
identified hand hygiene protocol is identified at least in part by
one or more nodes in the wireless mesh network and in the vicinity
of the individual and is based at least in part on a status
associated with a patient in the vicinity of the individual;
determining that the individual has not followed the hand hygiene
protocol; and notifying the individual in response to determining
that the individual has not followed the hand hygiene protocol.
14. The method of claim 13 wherein the notification is further
generated based at least in part on characteristics of the physical
location.
15. The method of claim 13, wherein the notifying includes one or
more of an audio, visual, and haptic alert.
16. The method of claim 15, wherein the selection of the one or
more of the audio, visual, and haptic alert is based at least in
part on at least one of the status associated with the patient or
characteristics of the physical location.
17. The method of claim 13, further comprising transmitting data to
a central monitoring location in response to determining that the
individual has not followed the hand hygiene protocol.
18. The method of claim 13, further comprising transmitting data to
a central monitoring location in response to detecting activity
associated with the hand hygiene protocol.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] The present application is a continuation of U.S.
application Ser. No. 13/114,216, filed May 24, 2014, which claims
the benefit of provisional application No. 61/347,715 filed May 24,
2010, the content of which are hereby incorporated by reference in
their entireties herein.
BACKGROUND OF THE INVENTION
[0002] The subject matter disclosed herein relates generally to
hand hygiene compliance (HHC), and particularly to tracking and
encouraging worker compliance with hand hygiene protocols. In a
hospital setting, hospital associated infections (HAIs) may cause
undue illness to patients. One way of decreasing the number of HAIs
is for hospital workers to wash their hands at key phases of
patient care. In an effort to reduce the number of HAIs, hospitals
have implemented hand hygiene protocols for hospital staff. For
example, staff at a hospital may be instructed to wash their hands
when they enter a patient room, before any patient contact, before
an aseptic task, after body fluid exposure risk, after patient
contact, after contact with patient surroundings, and upon exiting
the patient room.
[0003] Hospitals have a variety of techniques for reminding workers
to follow hand hygiene protocols and for tracking worker compliance
with hand hygiene protocols. One method of reminding workers to
follow hand hygiene protocols is to send a signal (e.g., an audio
or visual reminder) to the health care worker (HCW) when the HCW
enters or exits a patient's room. This method works well when hand
hygiene requirements are the same for all patients and when the
requirements are associated with a HCW being at a particular
location. This method does not work well when hand hygiene
requirements differ across patients, when the requirements differ
based on a particular path taken by the HCW, and/or they differ
based on an amount of time spent by the HCW at a particular
location (e.g., next to the patient's bed). One method of tracking
hand hygiene compliance (HHC) is to use "secret shoppers" to watch
the staff to see if they are following the protocol. The secret
shoppers may remind the HCWs and/or they may report on compliance.
One drawback to the use of secret shoppers is that knowledge of the
secret shoppers can cause an artificial spike in hand hygiene
compliance, because the workers know that they are being
watched.
[0004] Accordingly, and while existing HHC systems may be suitable
for their intended purpose, there remains a need in the art for HHC
systems that overcome these drawbacks.
[0005] This background information is provided to reveal
information believed by the applicant to be of possible relevance
to the present invention. No admission is necessarily intended, nor
should be construed, that any of the preceding information
constitutes prior art against the present invention.
BRIEF DESCRIPTION OF THE INVENTION
[0006] An embodiment of the invention is a computer implemented
method for performing hand hygiene compliance (HHC). The method
includes receiving a notification that an individual has entered a
physical location. The notification is received by a node in a
wireless mesh network that includes a plurality of nodes
corresponding to objects in the physical location. A hand hygiene
protocol is identified for the individual. It is determined that
the individual has not followed the hand hygiene protocol. The
determining is performed by software executing on the nodes in the
wireless mesh network and is responsive to a previous and a current
location of the individual relative to the objects in the physical
location. The individual is notified in response to determining
that the individual has not followed the hand hygiene protocol.
[0007] An embodiment of the invention is a HHC system. The system
includes a plurality of nodes corresponding to objects in a
physical location, where the nodes form a wireless mesh network.
The system also includes HHC software for execution on the nodes in
the wireless mesh network to perform a method. The method includes
receiving a notification that an individual has entered the
physical location and identifying a hand hygiene protocol for the
individual. The method also includes determining that the
individual has not followed the hand hygiene protocol. The
determining is responsive to a previous and a current location of
the individual relative to the objects in the physical location.
The method further includes notifying the individual in response to
determining that the individual has not followed the hand hygiene
protocol.
[0008] Another embodiment of the invention is a computer program
product for performing HHC. The computer program product includes a
tangible storage medium readable by a processing circuit and
storing instructions for execution by the processing circuit for
performing a method. The method includes receiving a notification
that an individual has entered a physical location. The
notification is received by a node in a wireless mesh network that
includes a plurality of nodes corresponding to objects in the
physical location. A hand hygiene protocol is identified for the
individual. It is determined that the individual has not followed
the hand hygiene protocol. The determining is performed by software
executing on the nodes in the wireless mesh network and is
responsive to a previous and a current location of the individual
relative to the objects in the physical location. The individual is
notified in response to determining that the individual has not
followed the hand hygiene protocol.
[0009] A further embodiment of the invention is a computer
implemented method for performing HHC. The method includes
receiving a notification that an individual has entered a first
physical location. The notification is received by a node in a
wireless mesh network that includes a plurality of nodes
corresponding to objects in the first physical location. A hand
hygiene protocol is identified for the individual. It is determined
that the individual has not followed the hand hygiene protocol. The
determining is performed by software executing on a processor
located in a second physical location, the determining responsive
to a previous and a current location of the individual relative to
the objects in the first physical location. The individual is
notified in response to determining that the individual has not
followed the hand hygiene protocol.
[0010] A further embodiment of the invention is a system for
performing HHC. The system includes a plurality of nodes
corresponding to objects in a first physical location. The
plurality of nodes form a wireless mesh network. The system also
includes HHC software for execution on a processor located in a
second physical location for performing a method. The second
physical location is different than the first physical location.
The method includes receiving a notification that an individual has
entered the first physical location and identifying a hand hygiene
protocol for the individual. The method also includes determining
that the individual has not followed the hand hygiene protocol. The
determining is responsive to a previous and a current location of
the individual relative to the objects in the first physical
location. The method further includes notifying the individual in
response to determining that the individual has not followed the
hand hygiene protocol.
[0011] A further embodiment of the invention is a computer program
product for performing HHC. The computer program product includes a
tangible storage medium readable by a processing circuit and
storing instructions for execution by the processing circuit for
performing a method. The method includes receiving a notification
that an individual has entered a first physical location. The
notification is received by a node in a wireless mesh network that
includes a plurality of nodes corresponding to objects in the first
physical location. A hand hygiene protocol is identified for the
individual. It is determined that the individual has not followed
the hand hygiene protocol. The determining is performed by software
executing on a processor located in a second physical location, the
determining responsive to a previous and a current location of the
individual relative to the objects in the first physical location.
The individual is notified in response to determining that the
individual has not followed the hand hygiene protocol.
BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Referring to the exemplary drawings wherein like elements
are numbered alike in the accompanying Figures:
[0013] FIG. 1 depicts a hand hygiene compliance (HHC) system that
may be implemented in accordance with an embodiment;
[0014] FIG. 2 depicts application, instruction, and transport
layers that may be implemented in accordance with an
embodiment;
[0015] FIG. 3 depicts a HHC system that spans two physical
locations that may be implemented in accordance with an
embodiment;
[0016] FIG. 4 depicts a mesh network spanning a hospital that may
be implemented in accordance with an embodiment;
[0017] FIG. 5 depicts a mesh network spanning a section of a
hospital that may be implemented in accordance with an
embodiment;
[0018] FIG. 6 depicts a subset of a mesh network spanning a room
that may be implemented in accordance with an embodiment;
[0019] FIG. 7A depicts an example process flow that may be
implemented when a HCW enters a patient's room and FIG. 7B depicts
a portion of a mesh network that may participate in the process
flow depicted in FIG. 7A, in accordance with an embodiment;
[0020] FIG. 8 depicts HCW reminders that may be generated in
accordance with an embodiment;
[0021] FIG. 9 depicts a process flow that may be implemented when a
HCW interacts with a patient in accordance with an embodiment;
[0022] FIG. 10 depicts a process flow that may be implemented in a
restroom in accordance with an embodiment;
[0023] FIG. 11 depicts a process flow for monitoring HHC and
changing HCW preferences in accordance with an embodiment;
[0024] FIG. 12 depicts a system for providing mobile monitoring in
accordance with an embodiment;
[0025] FIGS. 13A and 13B depict systems for bridging the HHC system
to an existing network in accordance with various embodiments;
and
[0026] FIG. 14 depicts a badge that may be implemented in
accordance with an embodiment.
DETAILED DESCRIPTION OF THE INVENTION
[0027] Although the following detailed description contains many
specifics for the purposes of illustration, anyone of ordinary
skill in the art will appreciate that many variations and
alterations to the following details are within the scope of the
invention. Accordingly, the following embodiments of the invention
are set forth without any loss of generality to, and without
imposing limitations upon, the claimed invention.
[0028] An embodiment of the invention, as shown and described by
the various figures and accompanying text provides a hand hygiene
compliance (HHC) system. An embodiment of the system monitors
healthcare worker (HCW) compliance with a hand hygiene protocol. If
a HCW is not following the protocol, reminders are sent to the HCW.
In addition, the non-compliance may be reported to a supervisor or
other HHC personnel. An embodiment provides for two-way
communication between an integrated circuit (IC) located on an
employee badge and ICs corresponding to various objects (e.g.,
located on or integrated into) in a hospital. In an embodiment, the
ICs on the badge and other objects are nodes in a wireless mesh
network and include application software, mesh network protocols,
and storage locations. The two-way communication between the nodes
allows for more granular tracking of HCW actions that may require
hand hygiene, for more reminders to the HCWs, and for more targeted
reminders to the HCWs. In addition, the ability to store data at a
node can provide for more customized hand hygiene instructions. For
example, a node at a patient bed may store information about the
status of the patient (e.g., staph infection). The node at the
patient bed can communicate with a node in a sink and a node in a
badge that the HCW is wearing to assure that the HCW has followed
the procedure associated with the patient status (e.g., wash hands
for three minutes and use soap with higher antibacterial
content).
[0029] In an embodiment, a specific application is implemented on
each node. This specific application, implemented by an application
layer, is used to interface with the object and with nodes on other
objects to assure that a specific process of HHC has been completed
(e.g., that a hand hygiene protocol has been followed by a HCW). An
example is that a node on a soap dispenser will relay location
information but also can tell whether or not a HCW used soap from
the soap dispenser. In addition, a sink node may relay location
information and can also monitor the duration of hand scrubbing. In
addition, the application layer may communicate to nodes on the
soap dispenser and the sink to assure that both processes were
performed by the same HCW, in order to assure that proper hand
hygiene was performed. Examples of objects associated with nodes
having application layers include, but are not limited to: beds,
sanitizing gel dispensers, badges, room sensors, and any other
object that is either involved in hand hygiene or contamination
areas.
[0030] An example system implemented by an embodiment includes a
badge node located on a HCW, an object node located at a door to a
patient room, an object node located on a patient bed, and an
object node located on a soap dispenser. One scenario for using the
system includes the HCW entering the patient room. The object node
located on the patient bed communicates the patient care
requirements (e.g., hand hygiene requirements) to the other nodes
in the network. If the HCW enters the room and walks towards the
patient bed without exercising proper hand hygiene, the soap
dispenser will communicate to the node on the badge and to the node
on the bed that the soap dispenser has not been used. Then, the
nodes (badge, soap dispenser, and bed) can use their relative
proximity to determine that hand hygiene actions that should have
been performed by the HCW have not been performed. In response to
this determination, the HCW's badge flashes (or takes some action
to get the HCW's attention and/or a supervisor's attention, such as
vibrate for example) and/or the soap dispenser beeps (or takes some
action to get the HCW's attention). Alternatively, if the HCW
enters the room and performs hand hygiene, then the object node
located on the soap dispenser may verify that the patient care
requirements have been met (type of soap, length of washing, hand
drying, etc.). All or a subset of the actions detected, as well as
any other activities associated with the hand hygiene protocol, may
be logged and reported.
[0031] FIG. 1 depicts a HHC system implemented in accordance with
an embodiment. The system depicted in FIG. 1 includes a wireless
mesh network 114 made up of one or more badge nodes 102 and object
nodes 104. As depicted in FIG. 1, the wireless mesh network 114 is
in communication (e.g., via a transmission control
protocol/Internet protocol or "TCP/IP" connection) with an existing
network 106 for accessing a host application located on a host
system 110. In an embodiment, the existing network 106 (e.g., an
existing IT network) is implemented by a local area network (LAN).
It will be appreciated that existing network 106 can be implemented
using other types of networks such as, but not limited to the
Internet, and an intranet. As depicted in FIG. 1, existing network
106 is in communication with the host system 110, a storage device
112, and a user device 108. The wireless mesh network 114 depicted
in FIG. 1 covers one room. It will be appreciated that the system
includes a plurality of wireless mesh networks 114. Each wireless
mesh network 114 may span a variety of physical locations (also
referred to herein as physical areas) such as, but not limited to,
a single room, a group of rooms, a floor, a building, and two or
more buildings. In an embodiment, the host system 110 is
implemented by one or more processors, each of which may be located
in the same physical location or a different physical location than
the wireless mesh network.
[0032] Advantages to utilizing a wireless mesh network 114 includes
the ability to provide seamless integration into existing
buildings, independent operation from existing networks, self
healing network if a node is damaged, sub-room level real-time
asset tracking, ease of installation and maintenance, and ease of
expandability.
[0033] Badge node 102 is located on a badge worn by a HCW. The
badge node 102 includes network protocols, storage locations, and
application software. The network protocols are used to transmit
packets from the badge node 102 to the object nodes 104 (and to
other badge nodes 102 if present in network 114) in wireless mesh
network 114. The badge storage stores information associated with
the HCW such as, but not limited to: name, occupation, specific
hand hygiene procedures, location history including different
contamination level zones, HHC history and accuracy, notification
preferences. In an embodiment, the storage locations are
implemented by a storage mechanism such as, but not limited to,
random access memory (RAM) or nonvolatile memory (NVM).
[0034] In an embodiment, the application software located on the
badge node 102 implements the functions described herein to perform
HHC including: locating the HCW, determining a possible HHC
protocol violation, reminding the HCW of the hand hygiene protocol,
and reporting the possible violation. It will be appreciated that
the badge node 102 may be located on the HCW by means other than a
badge. For example, the badge node 102 may be located on a belt
worn by the HCW or attached to a portable hand sanitizer carried by
the HCW.
[0035] In an embodiment, locating the HCW is performed by a real
time location system (RTLS) 103 using a methodology such as active
radio frequency identification, infrared hybrid, optical locating,
low-frequency signpost identification, semi-active radio frequency
identification, ultrasound identification, ultrasonic ranging,
ultrawide band, wide-over-narrow band, wireless local area network,
and radio frequency transceivers. These methodologies may use a
variety of algorithms to determine locations (e.g., of the HCWs)
including, but not limited to: angle of arrival, line-of-sight,
time of arrival, time difference of arrival, received channel power
indicator, received signal strength indication, time of flight,
symmetrical double sided--two way ranging, and near-field
electromagnetic ranging. The RTLS 103 may be implemented via
application software located on the badge node 102 and/or one or
more object nodes 104.
[0036] In an embodiment, object nodes 104 are located on objects in
a building. In the example depicted in FIG. 1, object nodes 104 are
located on a patient bed, a soap dispenser, and at a sink. An
object node 104 includes network protocols, storage locations, and
application software. The network protocols are used to transmit
and receive packets, and the application software implements
functions described herein. The storage locations store information
associated with the object such as, but not limited to: patient
instructions, specific hand hygiene procedures, contamination zone
level, HHC history and accuracy, notification preferences.
[0037] In an embodiment, an object node 104 is integrated into an
object such as a soap dispenser or towel dispenser. In an
embodiment, the object node 104 is built into the object during
manufacturing and the HHC functionality described herein is enabled
by providing a software key (or any other manner).
[0038] The user device 108 depicted in FIG. 1 is utilized to access
the host application executing on host system 110. In an
embodiment, the host application includes software instructions to
set application parameters on the badge nodes 102 and object nodes
104, to generate reports on HHC, to provide software updates to the
badge nodes 102 and object nodes 104, to store reports in the
storage device 112, and to perform administrative functions (e.g.,
set up access security, and add users). In an embodiment, the host
application includes software instructions to locate the HCW, to
determine a possible HHC protocol violation, to remind the HCW of
the hand hygiene protocol, and to report the possible
violation.
[0039] In an embodiment, the user device 108 is used to monitor
current HHC data related to a selected portion of a hospital (e.g.,
a room, a floor, a department). In an embodiment, access to monitor
HHC data is restricted and only authorized users are given access
to selected portions of the HHC data. For example, one user may be
able to access HHC data for only one room, while another user may
be given access to HHC data for a group of rooms or for an entire
floor. In an embodiment, current HHC data is stored in storage
device 112 and status is monitored via the user device 108. In
another embodiment, all or a portion of the HHC data is not
reported back to the host application.
[0040] In an embodiment, the host application is executed by an
object node 104 located in wireless mesh network 114. The host
application executing on an object node 104 may include a subset of
the functionality provided when the host application executes on
the host computer 110. In an embodiment, the subset includes
monitoring and no reporting. In this manner, no reporting is sent
back to a central location and the system is used to increase
compliance, as opposed to also being used to report
non-compliance.
[0041] FIG. 2 depicts application, instruction, and transport
layers implemented in accordance with an embodiment. The
application layer 202 depicted in FIG. 2 includes the application
software and storage locations to carry out the node functions
described herein. The application software is customized based on
customer hand hygiene protocols. In an embodiment, all of the nodes
(including the badge nodes 102 and the object nodes 104) contain
the same software. In this embodiment, the object nodes 104 and
badge nodes 102 may include customizations to differentiate them
from each other, with the customizations stored in storage
locations on the object nodes 104 and badge nodes 102. In another
embodiment, the badge nodes 102 contain one set of software
instructions and the object nodes 104 contain a different set of
software instructions. In a further embodiment, two of more of the
object nodes 104 contain a different set of software instructions
tailored to the attached object.
[0042] Also depicted in FIG. 2, is an instruction layer 204,
transport layer 206, and communication conduit 208 to carry out the
networking functions described herein. In an embodiment, the
instruction layer 204 and transport layer 206 are implemented using
off the shelf software, and the communication conduit 208 is
implemented using off the shelf hardware. In the embodiment
depicted in FIG. 2, the instruction layer 204 is a native mesh
implemented by using the standard command class structure of the
selected protocol. These types of command classes may or may not
have existing classes for HHC objects (i.e., a soap dispenser
device command class). In many cases there will be no class
structure for objects in the HHC system and a more generic command
class will be used (e.g., for the soap dispenser, a single pull
light switch device class, which will be on or off may be used).
Another example is that a command class for a dimmer may be used to
generate a percentage of run time on a pump in an alcohol dispenser
to aid in determining how much of the alcohol was dispensed to a
HCW.
[0043] In the embodiment depicted in FIG. 2, the transport layer
206 is a mesh protocol that interacts with the application layer
202 to communicate specific information pertaining to the HHC
system. The application layer 202 handles the new HHC classes of
devices and translates them into standard instruction layer device
classes so that these new device classes can communicate directly
with the mesh protocol in the transport layer 206. As shown in FIG.
2, the transport layer 206 is implemented by a wireless mesh
network communication protocol, such as, but not limited to: ANT,
ZigBee, and ZWave. In the embodiment depicted in FIG. 2, the
transport layer 206 allows for new objects and commands to be
entered into the network and decisions about them being handled by
the device itself, or some variant of many other devices.
[0044] It will be appreciated that one reason that the ANT protocol
may be preferable over the ZigBee protocol is because of battery
life. A transport layer 206 implemented in the ANT protocol
consumes much less battery power than a transport layer 206
implemented n ZigBee. Devices using the ZigBee protocol are usually
utilized for line power, and therefore, built for use in the
lighting industry. In the ZigBee protocol the battery powered nodes
are in a separate network than the line powered nodes. This is done
to save battery life, because a battery powered node does not have
to awake all of the time to be ready to pass messages in a ZigBee
implementation. In the HHC system, the badge node and object nodes
need to be awake at all times and ready to pass messages.
[0045] In the embodiment depicted in FIG. 2, the communication
conduit 208 is a radio frequency (RF) transceiver operating at
between 900 megahertz (MHZ) and 2.4 gigahertz (GHZ) to provide a
wireless connection for the nodes. However, other frequencies are
contemplated. The instruction layer 204 communicates with the
communication conduit 208 to provide wireless communication between
the object nodes 104 and badge nodes 102.
[0046] A mesh network can be broken up into small subparts,
referred to herein as "meshlets." When another node that can
communicate with the nodes in a meshlet (e.g., it "speaks" the same
language as the meshlet), comes into proximity of the meshlet, the
other node and the nodes in the meshlet can all start
communication. In an embodiment, the ability for the badge node 102
to communicate to object nodes 104 (and any other badge nodes 102)
in the meshlet is used to determine if a HCW is in a room, how
close the HCW is to a patient bed, and other data.
[0047] FIG. 3 depicts an embodiment of a HHC system that spans two
physical locations. As depicted in FIG. 3, a HHC system in a clinic
302 is in communication with an HHC system in a hospital via, for
example, an existing TCIP infrastructure. The ability to link HHC
systems together allows user devices with monitoring dashboards
associated with the HHC systems to be located in any facility.
Thus, the hospital 304 can monitor HHC at the clinic 302.
[0048] FIG. 4 depicts a parent mesh network spanning a hospital
that is implemented in accordance with an embodiment. As depicted
in FIG. 4, the physical location covered by the parent mesh network
is the entire hospital 402. The parent mesh network depicted in
FIG. 4 is made up of a plurality of meshlets.
[0049] FIG. 5 (with periodic reference back to elements shown in
FIG. 4) depicts a parent meshlet that spans a section 502 of the
hospital 402 that is implemented in accordance with an embodiment.
As depicted in FIG. 5, the physical location covered by the parent
meshlet is a section 502 of the hospital 402 such as a floor, a
group, a wing, and/or a department. The parent meshlet depicted in
FIG. 5 is made up of a plurality of micro meshlets and may also
contain additional transceivers. In an embodiment, a meshlet
(parent, micro, etc.) can be thought of as a team of nodes that are
designed to perform a task, and that task is HHC for a room or a
floor. The team of nodes in the meshlet communicate to each other
at much higher frequencies than to a node at a different part of
the hospital (even though communication is possible). The meshlet,
which may contain other meshlets, works to ensure HHC for that
room, or other defined space. In an embodiment, nodes located on a
soap dispenser, a bed and a sink are in control of a room and don't
require any outside information (e.g., information from nodes) to
complete the task of ensuring HHC for the room. A plurality of
these room meshlets may be combined to complete the task of
ensuring HHC for a floor. In this case, all of the rooms on the
floor work together to assure HHC on the floor so they have formed
a meshlet.
[0050] FIG. 6 depicts a micro meshlet that is contained in a
hospital room in accordance with an embodiment. As depicted in FIG.
6, the physical location covered by the meshlet is the hospital
room. The meshlet includes a badge node 102, a portable hand
sanitizer 708, and a plurality of object nodes 104 located at a
towel dispenser 11, a sink monitor 12, a bed monitor or dispenser
13, and several foam dispensers 14.
[0051] FIGS. 7A and 7B depicts a process flow that is implemented
by an embodiment of the HHC system when a HCW enters a patient's
room in accordance with an embodiment. At block 702, the HCW enters
the room and is identified by the nearest object node 104, which in
this example, is located on an alcohol foam dispenser. The HCW is
identified when a badge node 102 located on the HWC initiates a
communication with the object nodes 104 in the room, the
communication including information about the HCW such as employee
identification. The object node 104 waits for compliance with a
hand hygiene protocol that includes applying alcohol foam while the
HCW is in short range. At block 704, if hand hygiene is performed
using the alcohol foam dispenser, then no reminder is triggered and
the event is logged. In an embodiment, the event is logged into a
storage device that is accessible by monitoring and/or reporting
functions. At block 706, if the HCW proceeds closer to the patient
bed or closer to other nodes (other than a sink), then a reminder
is sent to the HCW. The HCW in FIG. 7B is wearing a portable hand
sanitizer 708.
[0052] FIG. 8 depicts HCW reminders that are generated by the HHC
system in accordance with an embodiment. In an embodiment, the
reminders include notifying the HCW using one or more of an audio
3, visual, and haptic alert 4. The reminder may be customized by
individual HCW or based on patient needs. For example, if the HCW
has a vibrating buzzer tag (an example of a haptic alert), the HCW
can set this as their preference. Similarly, the HCW can set a
preference for an audible beep or light emitting diode (LED)
lights. Additionally, if the patient room needs to be quiet, or
policy requires minimal noise, the volume can be set for each
patient or globally. In one embodiment, object nodes 104 installed
in outlets are used to perform tasks that require more power such
as verbal audio reminders. In another embodiment, a wearable
sanitizer dispenser with battery power for hands free operation
utilizes the battery for vibration. In some embodiments, an object
node 104 and/or a badge node 102 may communicate with a ceiling
node 105. The ceiling node 105 may be in communication with other
nodes of the wireless mesh network 114, network 106, user device
108, and/or the like, as indicated by the dot-dashed lines.
[0053] FIG. 9 depicts a process flow implemented by an embodiment
of the HHC system when a HCW interacts with a patient in accordance
with an embodiment. As depicted in FIG. 9, a patient identifier
object node 104 located on a patient's wrist and/or a bed object
node 104 located on the patient's bed is used to track patient
interaction. This allows the HHC system to offer reminders based on
time or patient treatment. For example, if the patient requires
aseptic tasks or there is a greater chance of bodily fluid contact,
more reminders can be triggered.
[0054] FIG. 10 depicts a process flow that is implemented by the
HHC system to provide HHC in another industry, such as the food
service in accordance with an embodiment. As depicted in FIG. 10,
after the worker passes an object node 104 located on the soap
dispenser, or is in close proximity to the object node 104 located
on the soap dispenser, the soap dispenser or the worker's badge
generate a reminder to the worker. If the worker uses the
dispenser, the reminder is quiet and the worker actions are
recorded. If no soap dispensing occurs, then failure is reported.
As depicted in FIG. 10, optional object nodes 104 are located on a
faucet and sink bowl to track washing details such as duration and
scrub style.
[0055] It will be appreciated that embodiments are not limited to
health care environments, and that embodiments can be utilized in
any environment (e.g., health care, food service, education, etc.)
where individuals (e.g., workers such as HCWs, visitors, patrons,
etc.) are required to follow a process.
[0056] FIG. 11 depicts a process flow for monitoring HCWs and for
changing HCW preferences in accordance with an embodiment. A HCW,
with the proper security access, can view group HHC or personal HHC
performance data on a display 1104. In addition, HCWs can change
their personal reminder preferences via the display 1104. As shown
in FIG. 11, the display 1104 is a node in the wireless mesh
network. Also as shown in FIG. 11, the display 1104 is connected to
existing network 106 via a network bridge 1102 to transfer HHC
compliance data to a centrally located storage device 112. As shown
in FIG. 11, a manager may then access the host application on the
host device 110, via the user device 108 to manage and observe
results from the HHC system. Reports may be generated automatically
or manually.
[0057] FIG. 12 depicts a system for providing mobile monitoring in
accordance with an embodiment. In the embodiment depicted in FIG.
12, a manager is observing results from the HHC system via an
application on a mobile telephone 1202 or other mobile device,
possibly in communication with a server for mobile monitoring. For
example, a manager may observe from a mobile phone app via wi-fi or
3G, etc.
[0058] FIGS. 13A and 13B depict example systems for bridging the
HHC system to an existing network in accordance with an embodiment.
The HHC system in the top portion of FIG. 13 is connected to
existing network 106 via a USB device 1302. The HHC system in
bottom portion of FIG. 13 is connected to existing network 106 via
an ANT to WiFi or Ethernet device 1304.
[0059] FIG. 14 depicts a badge 1402 that may be implemented in
accordance with an embodiment. In the embodiment depicted in FIG.
14, the badge 1402 is inserted into a badge shape 1404 that
provides one or more of sight, sound and feel reminder options.
FIG. 14 also depicts a charging station 1406 for charging the badge
shape 1404.
[0060] Technical effects and benefits include the ability to more
closely monitor the position of a HCW within a room and to send
more customized reminders based on hand hygiene compliance
opportunities that are detected by nodes in a wireless mesh
network. In addition, zone based needs may be enforced for
notifications (e.g., no audio alerts in a quiet zone). Another
benefit is the ability to use the system for reminders only, thus
providing an opportunity to increase compliance without the
drawbacks of the "secret shopper" method described previously. A
further benefit is the ability to integrate the HHC system with a
RTLS 103 to locate HCWs and objects.
[0061] As will be appreciated by one skilled in the art, aspects of
the present invention may be embodied as a system, method, or
computer program product. Accordingly, aspects of the present
invention may take the form of an entirely hardware embodiment, an
entirely software embodiment (including firmware, resident
software, micro-code, etc.) or an embodiment combining software and
hardware aspects that may all generally be referred to herein as a
"circuit," "module" or "system." Furthermore, aspects of the
present invention may take the form of a computer program product
embodied in one or more computer readable medium(s) having computer
readable program code embodied thereon.
[0062] Any combination of one or more computer readable medium(s)
may be utilized. The computer readable medium may be a computer
readable signal medium or a computer readable storage medium. A
computer readable storage medium may be, for example, but not
limited to, an electronic, magnetic, optical, electromagnetic,
infrared, or semiconductor system, apparatus, or device, or any
suitable combination of the foregoing. More specific examples (a
non-exhaustive list) of the computer readable medium would include
the following: an electrical connection having one or more wires, a
portable computer diskette, a hard disk, a random access memory
(RAM), a read-only memory (ROM), an erasable programmable read-only
memory (EPROM or Flash memory), an optical fiber, a portable
compact disc read-only memory (CD-ROM), an optical storage device,
a magnetic storage device, or any suitable combination of the
foregoing. In the context of this document, a computer readable
storage medium may be any tangible medium that may contain, or
store a program for use by or in connection with an instruction
execution system, apparatus, or device.
[0063] A computer readable signal medium may include a propagated
data signal with computer readable program code embodied therein,
for example, in baseband or as part of a carrier wave. Such a
propagated signal may take any of a variety of forms, including,
but not limited to, electro-magnetic, optical, or any suitable
combination thereof. A computer readable signal medium may be any
computer readable medium that is not a computer readable storage
medium and that can communicate, propagate, or transport a program
for use by or in connection with an instruction execution system,
apparatus, or device.
[0064] Program code embodied on a computer readable medium may be
transmitted using any appropriate medium, including but not limited
to wireless, wireline, optical fiber cable, RF, etc., or any
suitable combination of the foregoing.
[0065] Computer program code for carrying out operations for
aspects of the present invention may be written in any combination
of one or more programming languages, including an object oriented
programming language such as Java, Smalltalk, C++ or the like and
conventional procedural programming languages, such as the "C"
programming language or similar programming languages. The program
code may execute entirely on the user's computer, partly on the
user's computer, as a stand-alone software package, partly on the
user's computer and partly on a remote computer or entirely on the
remote computer or server. In the latter scenario, the remote
computer may be connected to the user's computer through any type
of network, including a local area network (LAN) or a wide area
network (WAN), or the connection may be made to an external
computer (for example, through the Internet using an Internet
Service Provider).
[0066] Aspects of the present invention are described with
reference to flowchart illustrations and/or block diagrams of
methods, apparatus (systems) and computer program products
according to embodiments of the invention. It will be understood
that each block of the flowchart illustrations and/or block
diagrams, and combinations of blocks in the flowchart illustrations
and/or block diagrams, may be implemented by computer program
instructions.
[0067] These computer program instructions may be provided to a
processor of a general purpose computer, special purpose computer,
or other programmable data processing apparatus to produce a
machine, such that the instructions, which execute via the
processor of the computer or other programmable data processing
apparatus, create means for implementing the functions/acts
specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a
computer readable medium that may direct a computer, other
programmable data processing apparatus, or other devices to
function in a particular manner, such that the instructions stored
in the computer readable medium produce an article of manufacture
including instructions which implement the function/act specified
in the flowchart and/or block diagram block or blocks.
[0068] The computer program instructions may also be loaded onto a
computer, other programmable data processing apparatus, or other
devices to cause a series of operational steps to be performed on
the computer, other programmable apparatus or other devices to
produce a computer implemented process such that the instructions
which execute on the computer or other programmable apparatus
provide processes for implementing the functions/acts specified in
the flowchart and/or block diagram block or blocks.
[0069] The flowchart and block diagrams in the Figures illustrate
the architecture, functionality, and operation of possible
implementations of systems, methods, and computer program products
according to various embodiments of the present invention. In this
regard, each block in the flowchart or block diagrams may represent
a module, segment, or portion of code, which comprises one or more
executable instructions for implementing the specified logical
function(s). It should also be noted that, in some alternative
implementations, the functions noted in the block may occur out of
the order noted in the figures. For example, two blocks shown in
succession may, in fact, be executed substantially concurrently, or
the blocks may sometimes be executed in the reverse order,
depending upon the functionality involved. It will also be noted
that each block of the block diagrams and/or flowchart
illustration, and combinations of blocks in the block diagrams
and/or flowchart illustration, may be implemented by special
purpose hardware-based systems that perform the specified functions
or acts, or combinations of special purpose hardware and computer
instructions.
[0070] While the invention has been described with reference to
example embodiments, it will be understood by those skilled in the
art that various changes may be made and equivalents may be
substituted for elements thereof without departing from the scope
of the invention. In addition, many modifications may be made to
adapt a particular situation or material to the teachings of the
invention without departing from the essential scope thereof.
Therefore, it is intended that the invention not be limited to the
particular embodiment disclosed as the best mode contemplated for
carrying out this invention, but that the invention will include
all embodiments falling within the scope of the appended claims.
Moreover, the use of the terms first, second, etc. do not denote
any order or importance, but rather the terms first, second, etc.
are used to distinguish one element from another. Furthermore, the
use of the terms a, an, etc. do not denote a limitation of
quantity, but rather denote the presence of at least one of the
referenced item.
* * * * *