U.S. patent application number 16/159995 was filed with the patent office on 2019-02-14 for systems and methods for hand sanitization monitoring and compliance.
The applicant listed for this patent is Cullen Thomas Easter. Invention is credited to Cullen Thomas Easter.
Application Number | 20190051138 16/159995 |
Document ID | / |
Family ID | 62980093 |
Filed Date | 2019-02-14 |
United States Patent
Application |
20190051138 |
Kind Code |
A1 |
Easter; Cullen Thomas |
February 14, 2019 |
SYSTEMS AND METHODS FOR HAND SANITIZATION MONITORING AND
COMPLIANCE
Abstract
Hand-washing systems and methods are proposed enabling
monitoring, reminding, recording, and reporting functionalities.
The hand-washing systems and methods include wearable devices
equipped with RFID and vibration capabilities. The wearable RFID
devices permit users to provide data pertaining to the hand-washing
activities of the user in, for example, health care related
settings. The data can be collected and, in turn, shared with
relevant entities for reporting purposes.
Inventors: |
Easter; Cullen Thomas;
(Upland, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Easter; Cullen Thomas |
Upland |
CA |
US |
|
|
Family ID: |
62980093 |
Appl. No.: |
16/159995 |
Filed: |
October 15, 2018 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
15885471 |
Jan 31, 2018 |
10102735 |
|
|
16159995 |
|
|
|
|
62452851 |
Jan 31, 2017 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G08B 21/245 20130101;
H04Q 2209/47 20130101; G16H 10/65 20180101; G16H 40/20
20180101 |
International
Class: |
G08B 21/24 20060101
G08B021/24; G16H 40/20 20060101 G16H040/20 |
Claims
1. A wearable device, the device comprising: a power supply; a
first processor; a vibration module; and a radio frequency
identification-enabled (RFID) sensor; and wherein the RFID sensor
and the first processor selectively receives electrical power from
the power supply; and wherein the first processor is in
communication with the vibration module and the RFID sensor.
2. The wearable device of claim 1, the wearable device further
comprising: a first antenna; and a first memory operable to store
at least one of data and instructions for execution by the
processor; and wherein the first antenna and first memory
selectively receives electrical power from the power supply; and
wherein the first antenna receives radio frequency signals for
transmission as electrical signals to the RFID sensor.
3. The wearable device of claim 2, wherein: the first antenna
further transmits radio frequency signals received as electrical
signals from the processor; and the wearable device is operable to
communicate with an RFID scanner device.
4. The wearable device of claim 3, wherein the RFID scanner device
comprises: a second processor; a communication module; a second
RFID sensor; a second antenna; and a second memory.
5. The wearable device of claim 4, wherein the wearable device is
in further operable to communicate, via the RFID scanner device
with components of a network, the network comprising: at least one
server; at least one monitor; and a plurality of RFID scanner
devices.
6. The wearable device of claim 5, wherein at least one of the
plurality of RFID scanner devices comprises at least one of a door
sensor, a hand-washing station sensor, and a bed frame sensor.
7. The wearable device of claim 5, wherein the RFID scanner device,
via the network, is operable to communication with one or more
third parties.
8. The wearable device of claim 4, wherein the wearable device is
further operable to communicate via the wearable device with a bed
guard system, wherein the bed guard system employs at least one
light emitting diode (LED) energized in response to a
hand-sanitization requirement of one or more health care workers
(HCWs) determined by the first processor and signaled via the
wearable device to the bed guard system.
9. The wearable device of claim 7, wherein the wearable device is
further operable to communicate via the wearable device with a bed
guard system, wherein the bed guard system employs at least one
light emitting diode (LED) energized in response to a
hand-sanitization requirement of one or more health care workers
(HCWs) determined by the first processor and signaled via the
wearable device to the bed guard system, and wherein data,
comprising the hand sanitation requirement, is communicated, via
the network, to the one or more third parties.
10. An electronic hand-washing reminder system, the system
comprising: (a) one or more wearable devices, each of the one or
more wearable devices comprising: (i) a vibration module; (ii) a
radio frequency identification-enabled (RFID) sensor; and (b) one
or more RFID scanner devices, wherein the one or more RFID scanner
devices is in communication with (a) the one or more wearable
devices.
11. The electronic hand-washing reminder system of claim 10, the
system further comprising: (a) a bed guard function system, wherein
the bed guard function system comprises: (i) a plurality of LED
lights; (ii) a monitor display device; (iii) a memory storage
device; (iv) a processor; and (v) a network connection.
12. The electronic hand-washing reminder system of claim 10,
wherein each of (b) the one or more RFID scanner devices comprises:
(i) a processor; (ii) a communication module; (iii) an RFID sensor;
(iv) an antenna; (v) a battery; (vi) storage; and (vii) memory.
13. The electronic hand-washing reminder system of claim 10, the
system further comprising: (a) a bed guard function system, wherein
the bed guard function system comprises: (i) a plurality of LED
lights; (ii) a monitor display device; (iii) a memory storage
device; (iv) a processor; (v) a network connection; (vi) a battery;
and, wherein each of (b) the one or more RFID scanner devices
comprises: (i) a processor; (ii) a communication module; (iii) an
RFID sensor; (iv) an antenna; (v) storage; and (vi) memory.
14. A method of reminding one or more health care workers to
sanitize their hands, the method comprising: activating a wearable
radio frequency identification-enabled (RFID) device; emitting a
reminder to sanitize hands; and monitoring hand-sanitizing
activities.
15. The method of claim 14, wherein the step of activating a
wearable RFID device comprises: communicating between the wearable
RFID device and an RFID scanner device.
16. The method of claim 15 further comprising: recording data
associated with hand-sanitizing activities; and reporting data
associated with hand-sanitizing activities.
17. The method of using an electronic hand-washing reminder system
of claim 16, wherein the step of reporting data associated with
hand-sanitizing activities consists of reporting data associated
with hand-sanitizing activities to an insurance company.
18. The method of using an electronic hand-washing reminder system
of claim 16, wherein the step of reporting data associated with
hand-sanitizing activities consists of reporting data associated
with hand-sanitizing activities to a United States federal health
care agency.
19. The method of claim 15 further comprising: activating a bed
guard function system, wherein the bed guard function system is in
communication with the wearable RFID device, and wherein the bed
guard system employs a plurality of light emitting diodes (LEDs) to
alert one or more health care workers (HCWs) of hand-sanitization
requirements.
20. The method of claim 16 further comprising: activating a bed
guard function system, wherein the bed guard function system is in
communication with the wearable RFID device, and wherein the bed
guard system employs a plurality of light emitting diodes (LEDs) to
alert one or more health care workers (HCWs) of hand-sanitization
requirements.
Description
[0001] This present application is a continuation of U.S. patent
application Ser. No. 15/885,471, filed Jan. 31, 2018, and claims
priority to U.S. Provisional Application No. 62/452,851, filed Jan.
31, 2017, the entire disclosure of which is hereby incorporated by
reference.
FIELD
[0002] The present disclosure is generally directed toward systems
and methods used to monitor hand-sanitization practices of
employees, and particularly directed toward monitoring the
hand-sanitization practices of health-care providers and recording
and reporting data to meet compliance requirements.
BACKGROUND
[0003] The medical advantages of hand washing can be traced as far
back as 1847 stemming from the work of Semmelweis, who was an early
pioneer in the field of aseptic procedures. Semmelweis instituted
hand washing with non-medicated soap in combination with
chlorinated lime solution and discovered decreases in mortality
rates in patents. What Semmelwis's work uncovered, and the modern
medical profession knows well today, is that microorganisms can be
transferred from health care workers (HCWs) to patients and vice
versa.
[0004] Most commonly, this transmission occurs is through direct
contact by the HCW with the pathogen. The hands of HCWs may be
colonized or contaminated with pathogens, such as Staphylococcus
aureus, Klebsiella pneumoniae, Acinetobacter species, Enterobacter
species, or Candida species, for example. In addition, it has been
demonstrated that microorganisms accumulate on HCWs' hands over
time during patient care. Therefore, hands of HCWs can transmit
pathogens even without previous contact with other patients. Even
using gloves does not completely protect against contamination of
the hands.
[0005] Hospital acquired infections (HAIs), also known as
nosocomial infections, are a serious public health problem and a
major cause of morbidity and mortality. HAIs can also prolong the
length of hospital stays thereby increasing costs throughout a
healthcare system and further increase chances for additional
infections. This problem of HAI is, in part, directly related to
lack of compliance for hand washing amongst HCWs. The financial
impact to hospitals, specifically, and the health care system,
generally, is appreciable and unacceptable. HAIs stemming from
failure to comply with hand-washing protocols is avoidable.
Furthermore, strategies investing in systems and methods to
minimize the occurrence of HAIs could potentially free up monies to
be invested elsewhere, for instance, in renovations of the
hospital, research and development, and recruitment and retention
of HCWs.
SUMMARY
[0006] A long-felt and unmet need exists for systems and methods to
monitor and record hand-sanitization practices of employees, and
particularly monitoring and recording the hand-sanitization
practices of WCWs. It is further advantageous for such recording
and reporting of hand-washing methods to be compiled in useable
data, which can be reported to show compliance with sanitary
requirements.
[0007] The present disclosure is directed to a spatially activated
reminding device to track users and their activities in a space.
Furthermore, the present disclosure includes systems and methods
that utilize modern technology in a novel way to meet hand-washing
compliance requirements for HCWs: radio frequency identification
(RFID) technology, vibration motors, and communication
networks.
[0008] RFID is a generic term for technologies using radio waves to
automatically identify people or objects. There are several methods
of identification, but the most common is to store a serial number
that identifies a person or object, and perhaps other information,
on a microchip that is attached to an antenna (the chip and the
antenna together are called an RFID transponder or an RFID tag).
The antenna enables the chip to transmit the identification
information to a reader. The reader converts the radio waves
reflected back from the RFID tag into digital information that can
then be passed on to computers that can make use of it.
[0009] An RFID system consists of a tag, which is made up of a
microchip with an antenna, and an interrogator or reader with an
antenna. The reader sends out electromagnetic waves. The tag
antenna is tuned to receive these waves. A passive RFID tag draws
power from field created by the reader and uses it to power the
microchip's circuits. The chip then modulates the waves that the
tag sends back to the reader and the reader converts the new waves
into digital data.
[0010] Active RFID tags have a battery, which is used to run the
microchip's circuitry and to broadcast a signal to a reader (the
way a cell phone transmits signals to a base station). Passive tags
have no battery. Instead, they draw power from the reader, which
sends out electromagnetic waves that induce a current in the tag's
antenna. Semi-passive tags use a battery to run the chip's
circuitry, but communicate by drawing power from the reader. Active
and semi-passive tags are useful for tracking high-value goods that
need to be scanned over long ranges, such as railway cars on a
track, but they cost a dollar or more, making them too expensive to
put on low-cost items. Companies are focusing on passive UHF tags,
which cost less than 50 cents today in volumes of 1 million tags or
more. Their read range isn't as far--typically less than 20 feet
vs. 100 feet or more for active tags--but they are far less
expensive than active tags and can be disposed of with the product
packaging.
[0011] Passive and active RFID transponders or tags contain coiled
antennas to enable them to receive and respond to radio-frequency
queries from an RFID reader or transceiver (which also includes an
antenna). The transceiver converts the radio waves returned from
the RFID tag into a form that can be passed onto computers.
Typically, a serial number that identifies a product uniquely, and
sometimes other information, is stored on the RFID tag (which
typically can store up to 2 KB of data). Passive RFID tags do not
have a power supply. A minute electrical current induced in an
antenna by the incoming radio-frequency scan provides enough power
for the tag to send a response. Active RFID tags have an on-board
power source and may have longer ranges and larger memories than
passive tags and the ability to store additional information sent
by the transceiver. Semi-passive RFID tags use an on-board power
source to run the tag's circuitry but communicate by drawing power
from the transceiver. Chips in RFID tags can be read-write or
read-only.
[0012] In embodiments a spatially activated reminding device
utilizing RFID technology and vibration mechanisms remind the HCW
to wash his or her hands upon entering and exiting the patient
hospital room. When the HCW enters the room, a vibration may be
activated on the wearable RFID device reminding the HCW to sanitize
their hands utilizing known methods, including, without limitation,
antiseptic gels, soaps, and foams, before and after making patient
contact. The tactile stimulation being used may be randomized and
pulse modulation employed each time provider enters and exits room,
thus eliminating the chances of becoming immune to the reminder.
The device may be paired with an RFID reading sensor which may be
installed on a single or multiple locations; including: (1) door
frames to patient rooms, (2) sink/hand gel sanitizing units
throughout the hospital. In an embodiment, every sink or hand gel
unit with a soap and/or hand-gel dispenser will be paired with a
sensor and communication device. Every time the sink or hand gel
unit is activated by dispensing soap and/or hand-gel, the sink or
hand gel dispenser will send data corresponding to the activation
to an appropriate data collection and analysis location. Data will
then be collected from the sink and gel station activations and
analyzed as a percentage compliance rate. This data will be
compared to pre-existing HAI rates to determine the effectiveness
of the product. Data will be utilized as a means to report
percentage compliance rates which will then be used to communicate
with billing insurance companies such as Medicare/Medicaid to
negotiate new pricing for services provided given that they stay
above a set percentage compliance rate.
[0013] Personal Wearable RFID Device
[0014] In an exemplary embodiment, a healthcare worker (HCW) wears
or otherwise carries a personal device. The device may utilize one
or more communication modules, for example a radio frequency
identification (RFID) unit. The device may be in the form of or
attached to a wearable article, for example a cellular telephone,
bracelet, anklet, or necklace, or may be clipped onto clothing.
[0015] In some embodiments, the wearable device may comprise an
RFID tag (comprising a microchip with an antenna) and a battery.
The RFID tag may optionally be passive such that a battery would
not be required, or active or semi-passive, in which a battery may
be required. In addition to an RFID tag, the wearable device may
comprise an RFID scanner. The wearable device may also comprise a
processor in communication with memory and a storage device.
[0016] The wearable device may additionally comprise one or more
feedback modules, including for example a speaker, a vibrator, and
a display. The wearable device may comprise a speaker operable to
perform one or more of a number of functions, e.g. beep upon low
battery, beep upon crossing through a doorway, beep upon satisfying
a requirement (e.g. visiting a handwashing station), sending a
message to the wearer, etc.
[0017] The wearable device may comprise a vibrator module. The
vibration module may comprise a motor in connection to a power
source. The vibration module may be configured to cause a portion
of the wearable device to vibrate at particular times. The
vibration module may vibrate every time the wearable device is
scanned by an RFID scanner, or scanned by a particular RFID scanner
or a group of scanners. For example, a user wearing the wearable
device may be notified via a vibration upon entering a patient room
due to the wearable device being scanned by an RFID scanner on a
doorframe.
[0018] The wearable device may comprise an LED light, or other form
of display, may be used to track a battery level, flash upon
crossing through a doorway, or flash upon satisfying some
requirement (e.g. visiting a handwashing station).
[0019] The wearable device may comprise a communication module, for
example one or more of a wireless network adapter, Bluetooth, USB,
etc. In some embodiments, the wearable device comprises one or more
communication modules. A communication module may comprise one or
more of a wireless internet connection (Wi-Fi) adapter, Bluetooth,
a USB connection, etc. The wearable device may be powered by a
battery. Alternatively, in an embodiment the wearable device may be
simply comprise an RFID tag with no power source.
[0020] The wearable device may comprise software operable to
perform a number of functions. For example, in some embodiments,
the wearable device may comprise an RFID scanner. Upon scanning a
doorway RFID tag, the wearable device may be operable to perform a
number of reactions in response. For example, the wearable device
may vibrate in some pattern to remind the HCW to wash his or her
hands. Alternatively, or in addition to vibrating, the wearable
device may flash LED lights or make a noise upon scanning a doorway
RFID tag. Tags in other locations or on particular doorways could
be associated with different reactions.
[0021] In other embodiments, the wearable device may comprise an
RFID tag which, when scanned by an RFID scanner, reacts in a number
of possible ways. For example, an RFID scanner on a doorway may
scan the wearable device upon the wearer crossing through the
doorway. The wearable device may react by vibrating, lighting up,
beeping, or some other way of notifying the user.
[0022] Scanners or RFID tags in other locations may be associated
with different reactions. For example, different vibration
patterns, beep tones, lights, etc. may be programmed based on a
particular door, a particular sink/gel station, or a particular
bedframe.
[0023] Bedframe RFID Scanners and/or Tags
[0024] RFID scanners and/or RFID tags may be affixed to stationary
objects, such as doorframes, sink/gel stations, and beds.
[0025] In some embodiments, RFID scanners, or RFID readers, may be
positioned on doorframes and operable to scan wearable devices as
an HCW wearing a wearable device walks through the door. Such an
RFID scanner may be operable to alert the wearable device it has
been scanned, as well as record into a storage device connected to
the RFID scanner a database entry listing a wearable device ID and
a timestamp in association with the scanned wearable device.
[0026] In embodiments wherein a doorframe is equipped with an RFID
scanner, the scanner may be in communication with a number of
elements, for example a memory and storage device, a processor, a
battery or other electrical power component, an LED or other
display device, a speaker, and/or a network connection (e.g. a
Wi-Fi adapter, Ethernet cable, or other device). In such
embodiments, the RFID scanner should be operable to record
instances of wearable devices being read by the scanner. A database
may be created and stored in memory or other storage on the scanner
device. The database may otherwise be stored on a server connected
to one or more RFID scanners via a network connection. Database
entries may comprise instances of scanned HCW wearable devices.
[0027] In an exemplary embodiment, a database may be created and
stored on an RFID doorframe scanner device hard drive, the database
storing instances of HCW wearable devices scanned by said
particular doorframe scanner device. Such a database, or entries
thereof, may be transmitted via a network and combined with
databases from other scanners to create a master database
comprising a list of all wearable devices scanned by all readers
throughout the network.
[0028] In some embodiments, doorframes may be equipped with passive
RFID tags. In such embodiments, a wearable device worn by a HCW may
be operable to scan such tags and record each instance of
scanning.
[0029] Sink and Gel Station RFID Sensors, Scanners, Readers, and
Tags
[0030] In some embodiments, RFID scanners, or RFID readers, may be
positioned on or around a sink and/or gel station and operable to
scan wearable devices as an HCW wearing a wearable device
approaches and/or uses the sink and/or gel station. Such an RFID
scanner may be operable to alert the wearable device it is being
scanned, as well as record into a storage device connected to the
RFID scanner a database entry listing a wearable device ID and a
timestamp in association with the scanned wearable device.
[0031] In embodiments wherein a sink and/or gel station is equipped
with an RFID scanner, the scanner may be in communication with a
number of elements, for example a memory and storage device, a
processor, a battery or other electrical power component, an LED or
other display device, a speaker, and/or a network connection (e.g.
a Wi-Fi adapter, Ethernet cable, or other device). In such
embodiments, the RFID scanner should be operable to record
instances of wearable devices being read by the scanner. A database
may be created and stored in memory or other storage on the scanner
device. The database may otherwise be stored on a server connected
to one or more RFID scanners via a network connection. Database
entries may comprise instances of scanned HCW wearable devices.
[0032] In an exemplary embodiment, a database may be created and
stored on an RFID sink and/or gel station scanner device hard
drive, the database storing instances of HCW wearable devices
scanned by said particular sink and/or gel station scanner device.
Such a database, or entries thereof, may be transmitted via a
network and combined with databases from other scanners to create a
master database comprising a list of all wearable devices scanned
by all readers throughout the network. In some embodiments, sinks
and/or gel stations may be equipped with passive RFID tags. In such
embodiments, a wearable device worn by a HCW may be operable to
scan such tags and record each instance of scanning.
[0033] In certain embodiments, a sink and/or hand gel unit can be
equipped with an automatic soap and/or hand-gel dispenser. Upon
activation of the automatic soap and/or hand-gel dispenser by a
user to disinfect the HCW's hands, a signal will be communicated
from the sink and/or hand gel unit though one or more paired
sensors and/or communication devices. Every time the sink and/or
hand gel unit is activated by the HCW to dispense soap and/or
hand-gel, the sink and/or hand gel dispenser will send data
corresponding to the activation to an appropriate data collection
and analysis location. The sink can be programmed to only send data
when soap and/or gel is either automatically dispensed or manually
dispensed, and not send data upon dispensing only water.
[0034] Bedframe RFID Scanners, Readers, and/or Tags
[0035] In some embodiments, RFID scanners, or RFID readers, may be
positioned on bedframes and operable to scan wearable devices as an
HCW wearing a wearable device walks near or up to a bed. Such an
RFID scanner may be operable to alert the wearable device it has
been scanned, as well as record into a storage device connected to
the RFID scanner a database entry listing a wearable device ID and
a timestamp in association with the scanned wearable device.
[0036] In embodiments wherein a bedframe is equipped with an RFID
scanner, the scanner may be in communication with a number of
elements, for example a memory and storage device, a processor, a
battery or other electrical power component, an LED or other
display device, a speaker, and/or a network connection (e.g. a
Wi-Fi adapter, Ethernet cable, or other device). In such
embodiments, the RFID scanner should be operable to record
instances of wearable devices being read by the scanner. A database
may be created and stored in memory or other storage on the scanner
device. The database may otherwise be stored on a server connected
to one or more RFID scanners via a network connection. Database
entries may comprise instances of scanned HCW wearable devices.
[0037] In an exemplary embodiment, a database may be created and
stored on an RFID doorframe scanner device hard drive, the database
storing instances of HCW wearable devices scanned by said
particular bedframe scanner device. Such a database, or entries
thereof, may be transmitted via a network and combined with
databases from other scanners to create a master database
comprising a list of all wearable devices scanned by all readers
throughout the network. In some embodiments, bedframes may be
equipped with passive RFID tags. In such embodiments, a wearable
device worn by a HCW may be operable to scan such tags and record
each instance of scanning.
[0038] In yet another embodiment, a room could have multiple beds
and the system could notify a HCW to wash his/her hands after the
HCW's wearable device has been scanned by a bedframe RFID
scanner.
[0039] LED "Bed Guard", "Stop/Go" Feature
[0040] In one embodiment, a hospital room may be equipped with an
LED "bed guard" or "stop/go" feature. This feature may be
particularly useful in contact isolation cases. In such an
embodiment, a bed in a hospital room may be surrounded by lights
placed in the floor. The lights may operate to alert HCW of a
requirement to perform some function upon entering the room. For
example, the lights may turn red upon detecting a HCW entering the
room. The lights may remain red until (1) the HCW visits the sink
and/or gel station to wash his/her hands, or (2) the HCW exits the
room, at which point the lights may turn off or turn green or
otherwise alert the HCW of the possibility of approaching the
bed.
[0041] In some embodiments, the lights are to remain red at all
times except when a HCW is detected entering a room and then
his/her wearable device is scanned by a sink or gel station RFID
scanner. In other embodiments, the lights are to remain off at all
times except when a HCW is detected entering a room, at which point
the lights turn red. If the HCW is detected as approaching the
sink/gel station, the lights may turn green. If the HCW is detected
as leaving the room, the lights may turn off.
[0042] In yet another embodiment, the lights may turn back to red
upon detecting a second HCW entering the room, despite having
turned green for a first HCW after the first HCW is detected as
using the sink/gel station.
[0043] In embodiments wherein a room is equipped with a "Bed Guard"
function, the LED lights may be in communication with a number of
elements, for example a memory and storage device, a processor, a
battery or other electrical power component, a display device, a
speaker, and/or a network connection (e.g. a Wi-Fi adapter,
Ethernet cable, or other device). In such embodiments, the "Bed
Guard" function should be operable to record instances of the "Bed
Guard" function being used. A database may be created and stored in
memory or other storage on the scanner device. The database may
otherwise be stored on a server connected to one or more RFID
scanners via a network connection. Database entries may comprise
instances of scanned HCW wearable devices.
[0044] A bed guard function processor may operate in communication
with doorframe, bedframe, and sink/gel station RFID scanners within
the room and compile a database of all instances such scanners read
wearable device RFID tags. Such a database may be used to verify
the functionality of the bed guard function, the obedience of HCW
to follow guidelines, and for the processor to determine in which
state the LED lights should be.
[0045] In yet another embodiment, a room could have multiple beds
and a number of bed guard function systems could be used to control
the movement of doctors and nurses throughout a hospital room, and
could notify a HCW to wash his/her hands after the HCW's wearable
device has been scanned by a bedframe RFID scanner. For example, if
a doctor enters a room with three beds, the bed guard functions of
all three beds could turn red. After doctor visits a sink, all
three could turn green. After doctor visits the first bed, the
other two beds could turn red. After the doctor returns to the
sink, all three beds could return to green. After the doctor is
scanned exiting the room, all three bed guard functions could turn
off
[0046] Another embodiment of the bed guard function could operate
with a display monitor as opposed to or in addition to LED lights.
For example, if three doctors, A, B, and G, are scanned entering a
hospital room with one bed, a monitor could display the names of
detected wearable devices. The names could appear red to signify
the doctors have not yet visited the sink/gel station. After doctor
A visits the gel station, his name could turn green, signifying
permission to visit the bed. This system could be expanded for a
room with multiple beds, wherein each bed has a separate monitor,
or a large monitor could show statuses of all HCWs with wearable
devices in the room for each bed.
[0047] Servers/Databases
[0048] All sensors within a hospital may be operably connected to a
computer or server located in the hospital or externally.
Information collected from the sensors may be sent to third
parties, e.g. insurance companies. For example, an insurance
company may use sensor data to verify the completion of proper
procedure within a hospital to provide benefits to cooperating
hospitals or to adjust rates based on good hospital behavior.
[0049] In embodiments, sensor data is sent to a server from a
sensor via packets comprising database entries for each instance of
the sensor reading a wearable device. For example, a doorframe
mounted sensor may operate to be directly connected via a network
to a server and send each scanner reading, comprising, e.g., a
wearable device ID, a timestamp, and a sensor ID. Each sensor may
be assigned a sensor ID so that the sensors may easily be
identified and associated with other sensors in the same or nearby
rooms. For example, room 321 may comprise sensors with sensor IDs
of Door321, Sink321, and BedFrame321. Similarly, wearable devices
may be associated with wearable device IDs so that wearers of each
device may be identified. For example, a Doctor Alex may wear a
wearable device with a wearable device ID of DrA. When Dr. Alex
walks into room 321, the doorframe RFID sensor should read his
wearable device ID and send a database entry to the server
identifying the sensor as Door321 and the wearable device as
DrA.
[0050] The data collected from the sensors may be monitored over
time and used to compare a hospital to other hospitals or compare
wards or floors within a hospital. The sensor data may also be used
to conduct other research, for example percentage compliance rates,
to keep track of who was in what room at what time, and to keep
track of where people are at the present time in order to be better
able to track people down and page people.
[0051] The system disclosed herein may be used in any number of
combinations of the features described. For example, a beginner
option could be used by a hospital to simply remind HCWs entering a
room to perform a function. Such a system could be implemented
simply via a wearable device and a door mounted RFID scanner. An
intermediate option could be used wherein HCWs wear wearable
devices, and data is collected from RFID scanners on doorframes
and/or sink/gel stations. An advanced option could be used with all
or some of the functions described herein.
BRIEF DESCRIPTION OF THE DRAWINGS
[0052] The accompanying drawings, which are incorporated in and
constitute a part of the specification, illustrate embodiments of
the disclosure and together with the general description of the
disclosure given above and the detailed description of the drawings
given below, serve to explain the principles of the
embodiments.
[0053] FIG. 1 is a block diagram depicting details of an RFID
scanner device in accordance with embodiments of the present
disclosure.
[0054] FIG. 2 is a block diagram depicting details of a wearable
device in accordance with embodiments of the present
disclosure.
[0055] FIG. 3 is a block diagram depicting details of a database
hierarchical structure in accordance with embodiments of the
present disclosure.
[0056] FIGS. 4A and 4B are block diagrams depicting details of
exemplary packets in accordance with embodiments of the present
disclosure.
[0057] FIG. 5 is a block diagram depicting details of a
communication system in accordance with embodiments of the present
disclosure.
[0058] FIGS. 6A and 6B are block diagrams depicting details of an
additional database hierarchical structure in accordance with
embodiments of the present disclosure.
[0059] FIGS. 7A and 7B are block diagrams depicting details of an
additional database hierarchical structure in accordance with
embodiments of the present disclosure.
[0060] FIG. 8 is a block diagram depicting details of an exemplary
display in accordance with embodiments of the present
disclosure.
[0061] FIG. 9 is a flow diagram depicting a hand-washing monitoring
method in accordance with embodiments of the present disclosure
[0062] Drawings are not necessarily to be interpreted as being
drawn to scale, or to any one particular scale.
DETAILED DESCRIPTION
[0063] FIG. 1 illustrates an exemplary RFID scanner device 101.
Such a scanner device 101 may be installed on a doorframe, sink/gel
station, bedframe, or any location to operate to scan a wearable
device as discussed herein or any RFID tag. As illustrated in FIG.
1, a scanner may comprise a processor 107, a storage device 102, a
memory device 103, a communication module 104, an RFID sensor 105,
and an antenna 106. An RFID scanner to be used in the system
disclosed herein may comprise any or all of the features
illustrated in FIG. 1.
[0064] FIG. 2 illustrates an exemplary wearable device 201. Such a
wearable device 201 may comprise an RFID tag 202 or an RFID scanner
204 with an antenna 205, or a combination thereof. The wearable
device 201 may also comprise one or more of an LED light 203, a
battery 206, a processor 207, a memory device 208, and a vibration
module 209. A wearable device to be used in the system disclosed
herein may comprise any or all of the features illustrated in FIG.
2.
[0065] The vibration module 209 may comprise various types of
vibration motors. For example, the vibration module 209 may include
an eccentric rotating mass vibration motor (ERM), which utilizes a
small unbalanced mass on a DC motor. When the ERM rotates it
creates a force that translates to vibrations. Further, a linear
resonant actuator (LRA) contains a small internal mass attached to
a spring, which creates a force when driven. The present disclosure
contemplates two aspects of vibration: vibration frequency, and
vibration amplitude. Vibration frequency is denoted in hertz which
is measured as Hz=1 cycle per second. Thus, vibration frequency
(Hz) is RPM/60.
[0066] Vibration amplitude is the strength of the force generated
by the motor which can be determined by the following equation:
F=(m)(r)(w.sup.2). F=centripetal force in Newtons (N). m=Mass of
eccentric mass in (Kg). r=Eccentricity of eccentric mass (m).
w=Angular velocity (Rads-1) aka Radians per second. The wearable
device 209 as contemplated herein may, thus, be designed to emit
vibrations at various frequencies and amplitudes.
[0067] FIG. 3 illustrates an exemplary database 300 storing
information collected by a number of sensors as described herein.
The database 300 may comprise a number of database entries (304,
305, 306) comprising a DeviceID 301, a SensorID 302, and a
Timestamp 303. For example, a sensor with the SensorID 302 of
"Patient0Door" may scan a wearable device with a DeviceID of "DrA"
on Feb. 2, 2015 at 12:47 PM. A database entry 304 may be created
storing this information and stored on a server connected via a
network to the Patient0Door sensor. This information may be
collected to conduct analysis, for example, in the database 300
illustrated in FIG. 3, it can be seen that DrA, after entering
Patent0Door, visited the sink station before approaching the bed.
In contrast, it can be seen that DrA entered Patient2Door and
approached Patient2Bed without being scanned by a sink/gel station
RFID scanner.
[0068] FIG. 4A illustrates an exemplary packet 410 sent from a
sensor to a server database via a network. The packet 410 may
comprise fields for factors such as a device ID 411, a sensor ID
412, and a timestamp 413. Other fields 414 may be used for any
other information needed for a database, such as a room number, a
hospital ID, a ward ID, etc.
[0069] FIG. 4B illustrates a second exemplary packet 420 sent from
a sensor to a server database via a network. The packet 420 may
comprise fields for factors such as a device ID 421, a sensor ID
422, a type 423 (e.g. Door, Sink, Bed) and a timestamp 424. Other
fields 425 may be used for any other information needed for a
database, such as a room number, a hospital ID, a ward ID, etc.
[0070] FIG. 5 illustrates an exemplary system 500 as described
herein. The system 500 may comprise a server 502 with a monitor 501
connected to a communication network 504. The server 502 may be
accessed by an insurance company 503 via the communication network
504 as well as by one or more third parties 505. The communication
network may connect to the sensors via a communication sub system
507 and a network 508. The sensors of the system 500 may comprise a
bedframe sensor 511, a bed guard function system 509, a sink/gel
station sensor 510, a door sensor 512, and/or other sensors
513.
[0071] FIG. 6A illustrates an exemplary database 610 which may be
stored on a server operably connected to a number of sensors. Such
a database may comprise fields for a device ID 611, a Room number
612, a timestamp 613, and a sensor type 614. For example, a
database entry 615 may show a device with a device ID of DrA was
scanned by a BED sensor in room 412 at 12:49 on Feb. 2, 2015. A
second DOOR scan, or a DOOR scan following a BED or SINK scan may
show a doctor has left a room. Such a scan may be shown via an
entry in the database, e.g. database entry 616.
[0072] FIG. 6B illustrates an exemplary database 620 which may be
stored on a server operably connected to a number of sensors and
used to operate a "Bed Guard" function. Such a database may
comprise fields for a sensor ID 621, a timestamp 622, a "Bed Guard"
light status 623, and a user ID 624. For example, a database entry
625 may show a device with data showing that a DOOR sensor scanned
a wearable device associated with a DRA. The lights of the "Bed
Guard" system, upon detecting a user entering a door turn red as
shown in the database entry 625. The light status may change, for
example after the doctor enters the door and approaches the sink
station, the lights may turn green. The database may show details
for a number of wearable devices, such as NurseG in database entry
626, and NurseX in database entry 627. As seen in the database
entry 628, NurseX visited the sink sensor and the bed guard
function lights turned Green.
[0073] FIG. 7A illustrates an exemplary database 700 associated
with a single sensor describing the scanned devices with the device
ID data field as well as a timestamp in a timestamp field 702.
Example entries 703, 704 and 705 show a wearable device with a
device ID of DrA was scanned by the sensor a number of times.
[0074] FIG. 7B illustrates an exemplary database used to control
the function of a bed guard function for a hospital room with a
number of beds. In this example, a room with three beds has lights
for each of the three beds. When a first user is scanned by a door
sensor the lights for all three beds turn red. When the first user
visits the sink, all three door lights turn green. When the first
user visits a bed number 1, the bed number 1 lights remain green
while the lights for the other beds may turn red. When the first
user leaves the room, the lights may turn off. Such a database
entry 716 shows userID 711 of DrA scanned by sensorID 712 of DOOR
and the light status of Bed1 713, Bed2 714, and Bed3 715 as turn
off. When a second user, as shown in entry 717, enters and visits
the sink, all lights turn green. When the second user, as shown in
entry 718, leaves the room, the lights may turn off.
[0075] FIG. 8 illustrates an exemplary display for use in a
hospital room computer monitor, showing permissions for a number of
users. For example, if a DrA has entered a room and washed his
hands, the monitor may show under a column HCW 801 that DrA has
permission 802 to visit any and all beds (entry 803). DrB may have
washed her hands and visited Bed1, thus the system shows DrB has
permission to visit only Bed1 in entry 804. Nurse A may have
similarly washed his hands and visited Bed 2 in entry 805, and DrD
may have entered the room but has not yet washed her hands and thus
is shown to have no permission to visit any beds. The display may
be shown in sight of all in the room so that each user in the room
may quickly assess the current permission status for themselves and
other users. This monitor information may be communicated via a
network to a master monitor in a control room for the hospital.
[0076] FIG. 9 illustrates an exemplary method of employing a
hand-washing system according to various embodiments of the present
disclosure. The method is initiated when a user applies a wearable
RFID device 201 (step 902). In embodiments the user optionally
covers the wearable RFID device with one or more barriers step 904.
Barriers may include garments of clothing. Such articles of
clothing may include a cotton or wool sock or nylon stocking.
Additional articles of clothing include pant legs, skirts, or
scrubs.
[0077] Once the wearable RFID device 201 is applied to the user,
the user may activate the wearable RFID device at a first RFID
scanner device 101 (step 906). Optionally, a vibration module 209
reminds the HCW to wash his or her hands upon entering or exiting
the patient hospital room (step 908). For example, when the HCW
enters the room, a vibration, or other method of notification
including audible sound or visible light, may be activated on the
wearable RFID device reminding the HCW to sanitize their hands
utilizing known methods, including, without limitation, antiseptic
gels, soaps, and foams, before and after making patient contact
(step 910).
[0078] In embodiments of the disclosure, the method includes the
additional steps including activating the wearable RFID device 201
at an RFID scanner device 101 at or near the patients' location
(step 912). As an additional and optional step (step 916), a
vibration module 209 reminds the HCW to wash his or her hands after
completion of performing the work-related activity (step 914).
After the HCW washes his or her hands (steps 910 and 918), an RFID
scanner device 101 located at the cleaning station 510 may record
(step 920) and report (step 922) compliance data according to the
embodiments of the present disclosure. Furthermore, any RFID
scanner device 101 regardless of its location may function to
record (step 920) and report (step 922) compliance data as
contemplated in the present disclosure.
[0079] The phrases "at least one", "one or more", "or", 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", "A, B, and/or
C", and "A, B, 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.
[0080] 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.
[0081] The term "automatic" and variations thereof, as used herein,
refers to any process or operation, which is typically continuous
or semi-continuous, done without material human input when the
process or operation is performed. However, a process or operation
can be automatic, even though performance of the process or
operation uses material or immaterial human input, if the input is
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".
[0082] The term "computer-readable medium" as used herein refers to
any computer-readable storage and/or transmission medium that
participate in providing instructions to a processor for execution.
Such a computer-readable medium can be tangible, non-transitory,
and non-transient and take many forms, including but not limited
to, non-volatile media, volatile media, and transmission media and
includes without limitation random access memory ("RAM"), read only
memory ("ROM"), and the like. Non-volatile media includes, for
example, NVRAM, or magnetic or optical disks. Volatile media
includes dynamic memory, such as main memory. Common forms of
computer-readable media include, for example, a floppy disk
(including without limitation a Bernoulli cartridge, ZIP drive, and
JAZ drive), a flexible disk, hard disk, magnetic tape or cassettes,
or any other magnetic medium, magneto-optical medium, a digital
video disk (such as CD-ROM), any other optical medium, punch cards,
paper tape, any other physical medium with patterns of holes, a
RAM, a PROM, and EPROM, a FLASH-EPROM, a solid state medium like a
memory card, any other memory chip or cartridge, a carrier wave as
described hereinafter, or any other medium from which a computer
can read. A digital file attachment to e-mail or other
self-contained information archive or set of archives is considered
a distribution medium equivalent to a tangible storage medium. When
the computer-readable media is configured as a database, it is to
be understood that the database may be any type of database, such
as relational, hierarchical, object-oriented, and/or the like.
Accordingly, the disclosure is considered to include a tangible
storage medium or distribution medium and prior art-recognized
equivalents and successor media, in which the software
implementations of the present disclosure are stored.
Computer-readable storage medium commonly excludes transient
storage media, particularly electrical, magnetic, electromagnetic,
optical, magneto-optical signals.
[0083] 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 storage
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
can contain, or store a program for use by or in connection with an
instruction execution system, apparatus, or device.
[0084] 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. A computer readable signal medium may convey 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. Program code embodied on a computer
readable signal 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. 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.
[0085] The term "means" as used herein shall be given its broadest
possible interpretation in accordance with 35 U.S.C., Section(s)
112(f) and/or 112, Paragraph 6. Accordingly, a claim incorporating
the term "means" shall cover all structures, materials, or acts set
forth herein, and all of the equivalents thereof. Further, the
structures, materials or acts and the equivalents thereof shall
include all those described in the summary, brief description of
the drawings, detailed description, abstract, and claims
themselves.
[0086] 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.
[0087] The preceding is a simplified summary of the disclosure to
provide an understanding of some aspects of the disclosure. This
summary is neither an extensive nor exhaustive overview of the
disclosure and its various aspects, embodiments, and/or
configurations. It is intended neither to identify key or critical
elements of the disclosure nor to delineate the scope of the
disclosure but to present selected concepts of the disclosure in a
simplified form as an introduction to the more detailed description
presented herein. As will be appreciated, other aspects,
embodiments, and/or configurations of the disclosure are possible
utilizing, alone or in combination, one or more of the features set
forth above or described in detail below. Also, while the
disclosure is presented in terms of exemplary embodiments, it
should be appreciated that individual aspects of the disclosure can
be separately claimed.
[0088] Although the present disclosure describes components and
functions implemented in the embodiments with reference to
particular standards and protocols, the disclosure is not limited
to such standards and protocols. Other similar standards and
protocols not mentioned herein are in existence and are considered
to be included in the present disclosure. Moreover, the standards
and protocols mentioned herein and other similar standards and
protocols not mentioned herein are periodically superseded by
faster or more effective equivalents having essentially the same
functions. Such replacement standards and protocols having the same
functions are considered equivalents included in the present
disclosure.
[0089] The present disclosure, in various embodiments,
configurations, and aspects, includes components, methods,
processes, systems and/or apparatus substantially as depicted and
described herein, including various embodiments, sub-combinations,
and subsets thereof. Those of skill in the art will understand how
to make and use the systems and methods disclosed herein after
understanding the present disclosure. The present disclosure, in
various embodiments, configurations, and aspects, includes
providing devices and processes in the absence of items not
depicted and/or described herein or in various embodiments ,
configurations, or aspects 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.
[0090] The foregoing discussion of the disclosure has been
presented for purposes of illustration and description. The
foregoing is not intended to limit the disclosure to the form or
forms disclosed herein. In the foregoing Detailed Description for
example, various features of the disclosure are grouped together in
one or more embodiments, configurations, or aspects for the purpose
of streamlining the disclosure. The features of the embodiments,
configurations, or aspects of the disclosure may be combined in
alternate embodiments, configurations, or aspects other than those
discussed above. This method of disclosure is not to be interpreted
as reflecting an intention that the claimed disclosure 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,
configuration, or aspect. 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
disclosure.
[0091] Moreover, though the description of the disclosure has
included description of one or more embodiments, configurations, or
aspects and certain variations and modifications, other variations,
combinations, and modifications are within the scope of the
disclosure, 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,
configurations, or aspects 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.
* * * * *