WO2005045461A1 - Systeme universel de communications, de surveillance, de localisation et de controle pour etablissement sanitaire - Google Patents

Systeme universel de communications, de surveillance, de localisation et de controle pour etablissement sanitaire Download PDF

Info

Publication number
WO2005045461A1
WO2005045461A1 PCT/US2004/034473 US2004034473W WO2005045461A1 WO 2005045461 A1 WO2005045461 A1 WO 2005045461A1 US 2004034473 W US2004034473 W US 2004034473W WO 2005045461 A1 WO2005045461 A1 WO 2005045461A1
Authority
WO
WIPO (PCT)
Prior art keywords
communicator
voice command
voice
location
asset
Prior art date
Application number
PCT/US2004/034473
Other languages
English (en)
Inventor
Matthew W. Weismiller
Timothy D. Wildman
Carl W. Riley
Craig A. Mcneely
Thomas M. Fleck
Dennis J. Gallant
Keith Adam Huster
Original Assignee
Hill-Rom Services, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hill-Rom Services, Inc. filed Critical Hill-Rom Services, Inc.
Priority to US10/575,801 priority Critical patent/US20070080801A1/en
Publication of WO2005045461A1 publication Critical patent/WO2005045461A1/fr

Links

Classifications

    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00—Measuring for diagnostic purposes; Identification of persons
    • A61B5/41—Detecting, measuring or recording for evaluating the immune or lymphatic systems
    • A61B5/411—Detecting or monitoring allergy or intolerance reactions to an allergenic agent or substance
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
    • G01S5/02—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using radio waves
    • G01S5/0205—Details
    • G01S5/0221—Receivers
    • G01S5/02213—Receivers arranged in a network for determining the position of a transmitter
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
    • G01S5/02—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using radio waves
    • G01S5/0205—Details
    • G01S5/0226—Transmitters
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Z—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS, NOT OTHERWISE PROVIDED FOR
    • G16Z99/00—Subject matter not provided for in other main groups of this subclass
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00—Measuring for diagnostic purposes; Identification of persons
    • A61B5/103—Detecting, measuring or recording devices for testing the shape, pattern, colour, size or movement of the body or parts thereof, for diagnostic purposes
    • A61B5/11—Measuring movement of the entire body or parts thereof, e.g. head or hand tremor, mobility of a limb
    • A61B5/1113—Local tracking of patients, e.g. in a hospital or private home
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S13/00—Systems using the reflection or reradiation of radio waves, e.g. radar systems; Analogous systems using reflection or reradiation of waves whose nature or wavelength is irrelevant or unspecified
    • G01S13/87—Combinations of radar systems, e.g. primary radar and secondary radar
    • G01S13/878—Combination of several spaced transmitters or receivers of known location for determining the position of a transponder or a reflector
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
    • G01S5/0009—Transmission of position information to remote stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements

Definitions

  • Caregivers such as physicians, nurses and other staff in a hospital ward, hospital wing, or other healthcare facility generally work under high pressure, high stress and long hours. These caregivers should be highly responsive to patient needs, in non-emergency as well as emergency situations. Due to ever-increasing costs of healthcare and other economic practicalities, efficient deployment of the caregivers in a healthcare facility is desired, particularly at night when the number of caregivers is typically maintained at a minimum. Nevertheless, optimizing efficiency is of secondary importance relative to the primary objective of providing a high level of healthcare. Accordingly, it is desirable to increase the efficiency of caregivers and improve the healthcare provided to patients.
  • the present invention provides an integrated, universal communications, tracking, monitoring and control system for a healthcare facility.
  • the system permits direct wireless communication among personnel, wireless access to continuously updated, stored information relating to patients, personnel and other assets, covert or automatic collection of information relating to the movement and status of such patients, personnel and other assets, and control (either manually, such as through voice commands, or automatically) of equipment and environmental features of the facility based on activities and/or the movement or status of patients, personnel or other assets.
  • "high resolution" location information for patients, personnel, and other assets and/or use or status information for patents, personnel, and other assets is provided along with the capability to perform various tasks, communicate, retrieve information, or initiate tasks via a "hands-free” or a "near hands-free" communicator.
  • a hands-free communicator is herein defined as a device which permits a user to perform various tasks, communicate, retrieve information, or initiate tasks without the usage of one's hands.
  • a near hands-free communicator is herein defined as a device which permits a user to perform various tasks, communicate, retrieve information, or initiate tasks by requiring only minimal usage of one's hands, such as to depress a button to initiate a call.
  • Hands-free communicators and near hands-free communicators may be either portable devices which are carried by, worn by, or associated with patients, personnel, and/or other assets, or fixed devices either associated with a patient, a personnel member, an asset, or location.
  • a hands-free communicator is not required to be hands-free for all operations nor is a near hands-free communicator required to be limited to minimal usage of one's hands.
  • a hands-free communicator can also facilitate "hands on" interaction to perform certain tasks and still be considered a hands-free communicator if it is capable of allowing a user to perform tasks, communicate, retrieve information or initiate tasks by a hands-free operation such as initiating a call with a voice command.
  • a near hands-free communicator can also facilitate "hands-on" interaction to perform certain tasks and still be considered a near hands-free communicator if it is capable of allowing a user to perform tasks, to communicate, retrieve information, or initiate tasks by a near hands-free operation such as initiating a call with a voice command. Additional features of the present invention will be evident from the following description of the drawings and exemplary embodiments.
  • FIG. 1 is a block diagram of one embodiment of a system according to the present invention.
  • FIG. 2 is a block diagram of an expanded system according to the present invention.
  • FIG. 3 is a side elevational view of a room including a plurality of components of the system shown in FIG. 2.
  • FIG. 4 is a side elevational view of a pass through wall component of the system shown in FIGs. 1 and 2.
  • FIGS. 5A-C are system architecture diagrams for portable communicators interfacing with the system of Fig. 1.
  • FIG. 6A is a block diagram of a hands-free portable communicator.
  • FIG. 6B is a block diagram of a near hands-free portable communicator.
  • FIG. 7A is a flowchart of an exemplary monitor routine for the hands-free portable communicator of FIG. 6A.
  • FIG. 7B is a flowchart of an exemplary standby routine for the near hands-free portable communicator of FIG. 6B.
  • FIG. 8A is a block diagram of one embodiment of a hands-free fixed communicator.
  • FIG. 8B is a block diagram of one embodiment of a near hands-free fixed communicator.
  • FIG. 9 is a flowchart of an exemplary call routine.
  • FIG. 10 is a flowchart of an exemplary receive call routine.
  • FIG. 11 is a flowchart of an exemplary send message routine.
  • FIG. 12 is a flowchart of an exemplary receive unheard message routine.
  • FIG. 13 is a flowchart of an environmental setting routine.
  • FIG. 14 is a flowchart of an exemplary navigation assistance routine.
  • FIG. 15 is a flowchart of an exemplary secure access routine.
  • FIG. 16 is a flowchart of an exemplary unauthorized movement routine.
  • FIG. 17 is a flowchart of an exemplary request location routine.
  • FIG. 1 shows components of a system according to one embodiment of the present invention.
  • System 10 of FIG. 1 shows components of a system according to one embodiment of the present invention.
  • server 12 generally includes a server 12, a first network 14, a second network 16, a plurality of first transceivers 18 connected to first network 14, a plurality of second transceivers 20 connected to first network 14, a plurality of active tags 22 (only one shown), a plurality of passive tags 24 (only one shown), a plurality of client devices 26 (only one shown), a plurality of work stations 28 (only one shown), each connected to an interface 30 and to first network 14, and a plurality of routers 32 connected to second network 16 and server 12.
  • server 12 may further be coupled to a hospital information system network, network 34, and another communications network 36 external to the facility in which system 10 is installed, for example, the internet.
  • Server 12 may be any of a variety of conventional computing devices such as a mainframe computer, a workstation computer, a personal computer, etc. As will be apparent to one skilled in the art, server 12 may be selected based on speed, memory capacity, and other performance characteristics necessary for providing the communications and data handling functions described herein. Server 12 is depicted as a single device having logic software 38 and a database 40, both of which are stored in a conventional storage media (not shown) coupled to server 12. It should be understood, however, that server 12 may be implemented as a plurality of separate servers connected together over a network.
  • database 40 may include multiple databases (each containing a different type or amount of information). Database 40 may further be a distributed database, having portions stored in a plurality of different locations.
  • server 12 is referred to herein as a single, central server having a single database 40.
  • Network 14 and network 16 may be implemented as a single network (indicated in FIG. 1 as network 19) that is wired, wireless, or a combination of wired and wireless.
  • network 14 is a wired network such as a conventional wired Ethernet. Accordingly, transceivers 18, transceivers 20, workstations 28, other systems 15 and displays 17 are coupled to network 14 using conventional wire technology.
  • network 16 is a wireless communication network such as a wireless Ethernet conforming to the 802.11(b) communications standard.
  • network 16 includes a plurality of conventional access points 21 positioned at various locations throughout the facility such as in patient rooms, hallways, or other locations. As is well known in the art, the spacing between such access points 21 should be such that wireless devices in communication with network 16 will always be within range of an access point 21, thereby providing complete coverage of the facility or a section of the facility.
  • Network 16 is in communication with server 12 via routers 32 which process communications between network 16 and server 12 according to principles that are well known in the art.
  • Transceivers 18 are of the type suitable for an equipment and/or personnel locating and tracking system. In one embodiment of the invention, transceivers 18 are of the type suitable for use with active tags 22 that periodically transmit an identification signal to receivers (not shown) in transceivers 18 using active infrared (IR), active radio frequency (RF), or other suitable communications technology.
  • IR infrared
  • RF active radio frequency
  • Transmitters (not shown) in transceivers 18 similarly transmit signals to active tags 22 using active communications technology.
  • transceivers 18 are mounted at various locations throughout the facility such as in patient rooms, hallways, and other locations. The location of each transceiver 18 is known by server 12.
  • server 12 can determine that active tag 22 is within range of the particular transceiver 18.
  • server 12 can access database 40 to determine which person or piece of equipment has been associated with the active tag 22 that transmitted the identification signal.
  • transceivers 18 and transceivers 20 are shown as two separate sets of transceivers to indicate two different types of locating technology.
  • transceivers 20 are RFID transceivers suitable for communications with RFID tags 24 using either passive or active RFID technology.
  • RFID tags 24 are RFID transceivers suitable for communications with RFID tags 24 using either passive or active RFID technology.
  • transceivers 20 may be mounted at various locations throughout the facility such as near or on hygiene equipment, waste disposal equipment, patient beds, door jams, care zones adjacent patient beds, family zones within patient rooms, openings in walls though which supplies are passed (as further described herein), facility shipping and receiving areas, hallways, nursing stations, and any other desired location within the facility.
  • RFID tags 24 may be mounted to items worn or carried by people, including the hands-free communicators and the near hands-free communicators described herein, equipment, and supplies of any type (collectively referred to herein as assets). Each RFID tag 24 is associated in database 40 with the asset to which the tag is assigned based on the unique identification signal generated by the tag.
  • Transceivers 20 receive these identification signals from RFID tags 24, and transmit messages to server 12 via network 14 that identify RFLD tags 24 within range of transceivers 20. Since the location of each transceiver 20 and the association between RFID tags 24 and the assets to which they are assigned are known (and stored in database 40), server 12 can access database 40 to determine (and/or update) the location of each asset having an RFID tag 24 as further described herein. Additional details concerning the structure and function of suitable systems for locating and tracking assets and to support various other features of the present invention are disclosed in U.S. Patent 5,561,412, U.S. Patent 6,344,794, co-pending U.S.
  • Patent Application S/N 09/751,241 entitled “PERSONNEL AND ASSET TRACKING METHOD AND APPARATUS,” filed December 29, 2000, co-pending U.S. Patent Application S/N 09/699,796, entitled “HYGIENE MONITORING
  • Client device 26 may include any of a variety of conventional portable computing and communication devices including laptops, tablet PCs, pocket PCs, mobile PCs, and PDAs.
  • Client device 26 includes wireless functionality for communications over network 16. Accordingly, client device 26 includes a transceiver module, a microphone, and a speaker (none shown).
  • One suitable client device 26 is a Compaq iPAQ H3600, H3700 and H3800 Series Pocket PC with a
  • the hands-free communicator and near hands-free communicators described herein are exemplary client devices 26.
  • Client device 26 further includes a display 27, and an RFID interface 42 for reading information from RFID tags 24 and writing information to RFID tags 24 as is further described below.
  • RFID interface 42 may be any of a variety of conventional RFID read/write devices such as those available from Northern Apex of Indiana, and is coupled to client device 26 according to principles that are well known in the art. While both client device 26 and workstation 28 are described herein as including RFID interfaces 30, 42, is should be understood that bar code technology (or other suitable technology) could readily be used instead of or in addition to RFID technology.
  • Client device 26 may be configured as a thin client such that client device 26 obtains information as needed from server 12 via network 16, and only a minimal amount of data is actually stored in the memory (not shown) of client device 26. It should be understood, however, that client devices 26 may alternatively store information obtained by system 10 in a distributed database configuration as mentioned above.
  • client devices 26 may share information over network 16 rather than access information stored in a central location such as database 40. It should also be understood that client devices 26 may communicate directly with one another without accessing an access point of network 16 so long as the client devices 26 are within range of one another. This communication may include text, audio and/or video content. Additionally, client device 26 may include a cellular telephone or pager to permit direct communications with systems that are external to the facility (such as cell phone networks). It is also within the scope of the invention to interface either of networks 14, 16 with a PBX to permit communications between client devices 26 using the 802.11(b) or another wireless communication standard and conventional telephones using the Plain Old Telephone System (POTS).
  • POTS Plain Old Telephone System
  • client devices 26 may also include one of tags 22, 24 to permit locating and tracking of client devices 26 (in addition to any tags 22, 24 worn by the user of a client device 26). This feature could be a theft deterrent or used as a reminder for charging the battery (not shown) of client device 26.
  • client device tag 22, 24 is detected by an appropriate transceiver 18, 20 at an exit to the facility, software 38 of server 12 could be configured to activate an alarm, transmit a message to security personnel, or otherwise automatically respond to the potential theft.
  • a battery charging station for client devices 26 may include an appropriate transceiver 18, 20 for detecting the presence of client devices 26.
  • Software 38 may be configured to transmit a message to appropriate personnel to retrieve a client device 26 from its known location if the client device 26 is not detected at the battery charging station at a certain time (e.g., within one hour after the shift of the person associated with the client device 26). It should be understood that some information relating to the location of client device 26 may be obtained simply by determining the access point 21 used by client device 26 to connect to network 16. Such information is transmitted to server 12 which, based on the known locations of the access points 21, can determine a general area (corresponding to the reception area of the access point) in which client device 26 is operating. Workstations 28 may also include any suitable type of computing device having sufficient performance characteristics to function as described herein.
  • workstations 28 are PCs at essentially fixed locations throughout the facility.
  • workstations 28 may be located in an admissions area, at nurse stations throughout the facility, in administrative areas, etc.
  • Some or all of workstations 28 may be coupled to an RFID interface 30 similar to
  • Workstations 28 may also be configured to function as thin client devices, and primarily access information from server 12 via network 14. Alternatively, workstations 28 may be configured to function in a serverlike fashion, collecting information directly via an input device such as a keyboard, and from a plurality of transceivers 18, 20 in proximity to workstation 28. In such an embodiment, each workstation 28 may communicate information with server 12 and other workstations 28, while maintaining a database of information corresponding to the components of system 10 in proximity to (or otherwise associated with) workstation 28. As should be apparent from the foregoing, other systems 15 connected to network 14 may provide additional information to server 12 or enhance the functionality of system 10.
  • FIG. 2 depicts such an architecture of system 10. System
  • Enterprise server 12 includes an enterprise server 12 that may correspond to the central server 12 described above.
  • Enterprise server 12 is coupled to networks 34, 36 as described above.
  • Server 12 is further coupled to a network 116 that includes transceivers 18 and/or transceivers 20 and manual data input devices 120 such as keypads, keyboards, touch screens, voice activated input devices, barcode readers, biometric recognition devices, etc.
  • Server 12 of system 10 is coupled to a plurality of other servers (described below) and display devices 17 by network 19 described above.
  • Display devices 17 may be monitors, electronic whiteboards, computer displays, displays of client devices 26, or any other type of device for displaying information.
  • Network 19 may correspond to networks 14, 16 of system 10 or any other suitable local area or wide area network.
  • the plurality of additional servers connected to network 19 include a first nurse call server 126 of a first communications system 127, a second nurse call server 128 of a second communications system 129, a first equipment monitoring server 130 of a first monitoring system 131, a second equipment monitoring server 132 of a second equipment monitoring system 133, and a universal server 134 of a combined communications and equipment monitoring system 135.
  • First nurse call server 126 may be a server such as that used in the COMposer ® communication system available from Hill-Rom.
  • first nurse call server 126 is coupled via a DXP switching network 137 to a plurality of room boards 136 located in patient rooms. Each room board 136 is coupled to an indicator light 138, a room audio station (RAS 140), and a plurality of input and output devices such as other lights, switches, and sensors (collectively referred to by the designation 142). ! Essentially, first nurse call server 126 controls communications among caregivers and patients and provides various status indications of certain conditions. For example, first nurse call server 126 may receive a nurse call request generated by a patient at an input device 142 such as a nurse call button.
  • an input device 142 such as a nurse call button.
  • the signal may be transmitted to first nurse call server 126 via room board 136.
  • First nurse call server 126 may then transmit a signal to a pager (not shown) carried by the appropriate caregiver or to a hands-free communicator or near hands-free communicator carried by the appropriate caregiver.
  • First nurse call server 126 may further cause room board 136 to change the appearance of indicator light 138 (positioned, for example, outside the patient's room) to indicate that the patient has placed a call to receive assistance from a caregiver.
  • the caregiver may respond to the call by using an intercom system (part of first nurse call server 126) or by using a hands-free communicator or near hands-free communicator to contact the patient through RAS 140 (including a speaker, microphone and a display) located in the patient's room.
  • RAS 140 including a speaker, microphone and a display
  • Another of the input devices 142 coupled to room board 136 is a code blue switch (not shown), activation of which results in automatic transmission by first nurse call server 126 of notification signals to appropriate caregivers, and a change in the appearance of indicator light 138 to indicate a code blue situation.
  • Information describing any and all of the communication traffic and other functions performed by first communication system 127 controlled by first nurse call server 126 may be provided to server 12 via network 19. This information may permit system 10 to notify appropriate personnel of certain conditions or otherwise automatically respond to certain conditions as further described herein.
  • Second communications system 129 is similar to first communications system . 127.
  • Second communications system 129 may be the COMlinxTM communications system available from Hill-Rom and described in the COMlinxTM Enterprise Solutions User's Guide and System Configuration Guide, and the Nurse Communication Module Installation and Service Guide, all of which are hereby expressly incorporated herein by reference.
  • System 129 includes components that are similar to those of system 127, including room controllers 144 located in patient rooms. Each room controller 144 is connected to an indicator light 146, a RAS 148, and a plurality of input and output devices collectively referred to by designation 150. Room controllers 144 are connected to second nurse call server 128 by a data and voice network 152. Second nurse call server 128 may provide similar information to server 12 as that provided by first nurse call server 126.
  • First equipment monitoring server 130 of first equipment monitoring system 131 is connected to a plurality of data acquisition and display devices (DADDs 154) which in turn are coupled to fetal monitoring equipment 156. Each DADD 154 is coupled to a data network 158.
  • First equipment monitoring system 131 may be an obstetrical patient data management system such as the WatchChild system available from Hill-Rom and described in the WatchChild User's Guide and System Configuration Guide, which are hereby expressly incorporated herein by reference.
  • First equipment monitoring server 130 may therefore provide information to server 12 via network 19 describing the output of the various fetal monitoring equipment 156.
  • Second equipment monitoring system 133 is simply a more generalized version of first equipment monitoring system 131.
  • second equipment monitoring server 132 is coupled via data network 164 to a plurality of DADDs 160 configured to receive, display, and transfer information from any of a plurality of different monitoring equipment 162 such as cardiac monitoring equipment, etc. Accordingly, second equipment monitoring server 132 may provide information to server 12 via network 19 describing the output of the various other monitoring equipment 162.
  • Universal server 134 of combined communications and equipment monitoring system 135 is coupled via data and voice network 166 to a plurality of room controllers 168 located in a plurality of patient rooms. Room controllers 168 are coupled to indicator lights 170, RASs 172, and a plurality of input and output devices collectively referred to by designation 174.
  • Room controllers 168 are further coupled to one or more DADDs 176 in the room, which in turn are coupled to a plurality of other devices 178 such as monitors, beds, and other equipment in the room. Accordingly, universal server 134 receives information including communications information and equipment output and status information in the manner described above with reference to the other systems coupled to network 19. As such, universal server 134 may provide any of the above-described information to server 12 via network 19 in the manner described above. It should be noted that the connection between RASs 172 and room controllers 168 and between DADDs 176 and room controllers 168 are indicated by dotted lines to denote wireless connections. Any of the connections between the various components, however, could readily be implemented using wired or wireless technology. Additionally, a plurality of patient point of care devices may be coupled to network 19 such as those disclosed in co-pending U.S. Patent Application S/N
  • point of care devices may provide information regarding meals, entertainment uses, scheduling, and messaging that may readily by stored on database 40, and accessed by appropriate facility personnel using, for example, client devices
  • any combination of the above-described systems may be coupled to server 12 via network 19. It is further within the scope of the invention to couple multiple systems 10 together over a network such as network 36.
  • a data warehouse may be provided wherein multiple facilities share information from their respective databases 40 with a central database at the data warehouse.
  • the data warehouse may include an automatic archival function wherein certain data is saved to a permanent storage media, and a reporting feature wherein reports relating to the operations of the facilities are generated and automatically transmitted to the facilities.
  • FIG. 3 depicts a room 180 incorporating some of the above-described components of system 10. More specifically, room 180 depicts an example of a portion of combined communications and equipment monitoring system 135. Room 180 includes a room controller 168 powered by an AC power outlet 182 and/or a DC power back-up system (not shown). As also shown in FIG. 2, room controller 168 is coupled to a data and voice network 166, an indicator light 170, and a RAS 172. The plurality of input and output devices 174 of FIG. 2 are depicted in FIG.
  • sensors 186, 188 are of the same technology as either of transceivers 18 or 20. Sensors 186, 188 are associated with room controller 168 because they are used to perform certain nurse call locating activities. For example, when a caregiver enters room 180 wearing active tag 22, sensor 188 receives an identification signal from active tag 22 and transmits a signal to room controller 168, which is forwarded to universal server 134. Room controller 168 responds to the identification signal from sensor 188 by, for example, changing the activated status of indicator light 170 to indicate that a caregiver is in room 180. Sensor 186 similarly senses the caregiver leaving room 180 and cause room controller
  • Client device 26 includes the combined functions of a pocket PC 196 (generically referred to as a handheld computer), a wireless telephone 198, a pager 200, and a headset 202.
  • client device 26 may further include an RFID interface 42 for reading information from and writing information to RFID tags 24 as further described below.
  • the voice over IP communications features provided by client device 26 are as shown and described in Figs. 4-19 and the accompanying disclosure of the co-pending parent application Serial No. 10/673,980.
  • the various networks and systems described above provide automatic data collection that may be used in a plurality of different ways.
  • system 10 By receiving continuously updated information about the location of the various people, equipment, and supplies, system 10 maintains an accurate database (such as database 40) of the current locations of such assets. Additionally, by retaining a history of such location data, the status of assets may readily be determined by applying certain logical rules.
  • system 10 may update the caregiver' s hygiene compliance status to "clean.” If a caregiver leaves a patient's room without washing his or her hands, then system 10 may update the caregiver's hygiene compliance status to "contaminated.” If the caregiver then enters another patient's room, system 10 may automatically prompt the caregiver to wash his or her hands by sending a message to client device 26 associated with the caregiver, activating a light attached to active tag 22 worn by the caregiver, causing indicator light 170 to flash or otherwise indicate a warning condition, causing an automatic message to be played over RAS 172, or otherwise urging compliance with the facility hygiene policy.
  • client device 26 associated with the caregiver
  • indicator light 170 to flash or otherwise indicate a warning condition
  • RAS 172 causing an automatic message to be played over RAS 172, or otherwise urging compliance with the facility hygiene policy.
  • Another application of system 10 is automatic dispatching of messages. For example, when wall switch 184 is activated to indicate a code blue condition, the location of the code blue source may be determined by system 10 as well as the identities of caregivers in proximity of room 180. System 10 may then automatically transmit a code blue message indicating the location of the code blue source to those caregivers nearest to the source. Such messages may be transmitted as text (e.g., an email message) over network 16 to client devices 26 carried by the caregivers. Client device 26 may be configured to activate an audible indicator (e.g., the speaker of client device 26) to notify the caregiver of the receipt of a code blue message.
  • an audible indicator e.g., the speaker of client device 26
  • the code blue message in one example, is an audio message provided to client devices 26, such as hands-free communicators or near hands-free communicators. Additionally, system 10 may cause transmitters 18 to transmit a signal to an active tag 22 worn by the caregiver to activate a light on tag 22 to indicate that a code blue message has been sent to the caregiver. The caregiver may then respond to the code blue condition by entering room 180. Movement of the caregiver into room 180 may be detected by either of transceivers 18, 20 (FIG. 1) or sensor 188 (FIG. 3). The presence of the caregiver in room 180 may then cause system 10 to send another signal to client device 26 to clear the code blue message.
  • client devices 26 such as hands-free communicators or near hands-free communicators.
  • system 10 may cause transmitters 18 to transmit a signal to an active tag 22 worn by the caregiver to activate a light on tag 22 to indicate that a code blue message has been sent to the caregiver.
  • the caregiver may then respond to the code blue condition by entering room 180. Movement of the caregiver into room 180 may be detected by either
  • system 10 may be automatically notified by system 10 of the code blue condition. Any other type of activity based automatic notification process may be employed using system 10
  • Another application of system 10 is associating information with assets and updating the information to indicate the present status of the assets.
  • system 10 facilitates association of information with patients, caregivers, and other assets in a hospital and, in addition to automatically updating the associated information as further described herein, enables caregivers, administrators, and other personnel to update the information as the status of the tagged person or other asset changes.
  • a patient may be processed using a conventional admissions procedure wherein information relating to the patient is manually entered at a processing terminal such as workstation 28. This information may then be provided to server 12 via network 14 for storage in database 40. Additionally, RFID interface 30 may be used to create an RFID tag 24 for the patient as further described below.
  • RFID tag 24 may include a conventional plastic wristband with an RFID device attached thereto (or printed thereon using an RFID printer as described in co-pending U.S. Patent Application S/N 10/154,644 referenced above). As the patient moves throughout the facility as detected by transceivers 20, the location information associated with the patient (as identified by the RFID unique identification number stored in the memory (not shown) of RFID tag 24) may be automatically updated by server 12 in database 40.
  • caregivers and/or other personnel may write information to the patient's RFID tag 24 to indicate the occurrence of certain events including administration of medications, completion of therapies, evaluations, etc.
  • This updated status information may be read by transceivers 20 (or RFID interfaces 30 or 42), transmitted over the appropriate network 14, 16 or combination thereof, and stored in database 40 by server 12.
  • transceivers 20 or RFID interfaces 30 or 42
  • FIGS. 20-33 One software application for associating information with RFID tags 24 is depicted in FIGS. 20-33 and described below.
  • the RFID features of the present invention are as shown and described in FIGS. 20-43 and the accompanying disclosure of the parent application, Serial No. 10/673,980.
  • FIG. 4 depicts another feature of one embodiment of system 10 for monitoring the status and movement of assets within the facility.
  • Pass through wall 800 may include a housing 806 mounted within a wall 807 supporting a pair of movable drawers 808, 810. It should be understood that in accordance with the principles of the present invention, one or more drawers may be used, and such drawers may be arranged in any desired fashion relative to one another in addition to the vertically stacked arrangement shown in FIG. 4. Also, the drawers may be housed separately and spaced apart from one another such that one drawer extends through one wall of a room and another draw extends through another wall of the room. Moreover, the drawers may be of any acceptable configuration or shape.
  • a simple opening in a wall or barrier may be configured as a pass through wall according to the present invention, with no moving parts.
  • drawer 808 is designated for moving assets into area 804 as indicated by arrow 812
  • drawer 810 is designated for moving assets out of area 804 as indicated by arrow 814.
  • Mounted adjacent drawer 808 is at least one RFID sensor 816 for reading unique identification numbers stored on RFID tags 24 associated with assets moved from area 802 to area 804 in drawer 808.
  • at least one RFID sensor 818 is mounted adjacent drawer 810 for reading unique identification numbers from RFID tags 24 associated with assets moved from area 804 to area 802 in drawer 810.
  • a pair of RFID sensors 816 are mounted adjacent drawer 808 (e.g., one on either side of drawer
  • RFID sensors 818 are mounted adjacent drawer 810 in a similar fashion.
  • RFID sensors 816, 818 are connected via conductors 820 (e.g., coax) to an interface module 822.
  • RFID sensor 816, 818 are conventional RFID antenna
  • interface 822 is a conventional RFID interface that provides power to sensors 816, 818, interprets the signals provided by sensor 816, 818, and provides a serial output to a computing device.
  • interface 822 may be connected to a personnel computer or workstation 28 coupled to server 12 via network 14.
  • Workstation 28 may be used to configure pass through wall 800 by assigning a location to each of RFID sensors 816, 818 and a direction for the drawers monitored by sensors 816, 818.
  • RFID sensors 816 may be associated with a particular patient's room (area 804) and designated to indicate movement of assets through drawer 808 into area 804.
  • RFID sensors 818 may be also associated with area 804 and designated to indicate movement of assets out of area 804 through drawer 810.
  • system 10 can interpret the corresponding signal from interface 822 as indicating the movement of that asset into area 804.
  • Signals detected by RFID sensors 818 may similarly indicate movement of assets out of area 804.
  • One use of pass through wall 800 includes controlling (in addition to monitoring) the movement of assets into and out of, for example, a patient's room. For example, when assets such as used bed linens are moved out of area 804 into drawer 810, sensors 818 detect the presence of the RFID tag 24 attached to the bed linens, and interface 822 provides a signal to workstation 28 indicating the presence of the bed linens in drawer 810.
  • the software of the present invention is configured to interpret the presence of bed linens in drawer 810 by associating a contaminated status with the bed linens in database 40 of server 12. Facility personnel responsible for collecting contaminated bed linens may be notified in any of the ways described above to collect the bed linens disposed in drawer 810.
  • transceivers 20 located in the cleaning area may detect the presence of RFID tag 24 associated with the bed linens and transmit the new location information to server 12 in the manner described above.
  • Logic software 38 of server 12 may determine, based upon the presence of the bed linens in a cleaning area, that the status of the bed linens should be changed to "cleaned.” As such, the bed linens may be moved into another patient's room or back into area 804 through drawer 808. If, on the other hand, facility personnel attempt to return the bed linens to area 804 prior to cleaning them, sensors 816 will detect the presence of the bed linens in drawer 808 by reading the identification number of the RFID tag 24 associated with the bed linens.
  • Interface 822 will notify workstation 28 and server 12 in the manner described above. Workstation 28 or server 12 may then activate a lock out feature such as a mechanical or electro-mechanical lock that prevents movement of drawer 808 into area 804. Additionally, an alarm may be sounded or a visual indication of the lock out condition may be provided to alert personnel of an attempt to move a contaminated asset into area 804. It should be understood that RFID sensors 816, 818 may, like RFID interfaces
  • RFID sensor 818 could write information to RFID tag 24 associated with the bed linens when the bed linens are placed in drawer 810 to indicate in the memory of RFID tag 24 that the bed linen status is "contaminated.” As such, even if server 12 is inoperable for some reason, the contaminated status of the bed linens may still be detected by RFID sensors 816, 818 when the bed linens are placed into drawer 808. Accordingly, workstation 28 may initiate a lock out condition as described above without accessing status information stored in database 40 in association with RFID tag 24 attached to the bed linens. Obviously, the movement and status of any of a variety of different types of assets may be monitored and controlled in the manner described above.
  • logic software 38 may automatically cause server 12 to issue messages to appropriate personnel to prepare a recovery room or deliver required equipment to the destination of the patient. If, after a predetermined period of time, server 12 does not receive information from transceivers 18, 20, client devices 26, workstations 28, or otherwise, indicating that the patient is located in an acceptable location, accompanied by appropriate personnel, equipment and supplies, server 12 may again issue messages in the manner described above to personnel responsible for ensuring the appropriate response to movement of the patient out of the operating room. In this manner, system 10 not only monitors heath care situations, but automatically intervenes and corrects inappropriate responses to situations based on predetermined business rules.
  • logic software 38 may be configured such that it automatically modifies certain business rules based on data reflecting historical responses to situations using available principles of artificial intelligence.
  • activity based responses enabled by system 10 involves the discharge or transfer of a patient.
  • system 10 may automatically respond based on a predetermined protocol. For example, an automatic message may be distributed to a receiving nurse and a receiving charge nurse to indicate that the discharge has initiated.
  • Other personnel copied on the message may include dietary personnel (to avoid misrouting of future meals), pharmacy and IV personnel (to avoid misrouting of equipment and medicine), housekeeping personnel (to permit prompt cleaning of the vacated room), case management personnel, therapy personnel, and other physicians associated with the patient.
  • Family members may further be notified of changes in location or status of patients by automatic posting of information to displays 17 positioned within the facility for viewing by family members, etc.
  • Periodic follow-up messages may automatically be sent if the desired movement of appropriate personnel and/or equipment, or the desired changes in status of the patient or assets are not detected by system 10 in the manner described herein.
  • interface 822 and workstation 28 may utilize conventional anti-collision technology to enable RFID sensors 816, 818 to simultaneously process signals from a plurality of different RFID tags 24 placed in drawers 808, 810.
  • pass through wall(s) 800 could be located at a centralized or distributed receiving area for inventory tracking purposes, at a centralized or distributed shipping area to monitor movement out of the facility of materials such as contaminated items, biological samples in containers having RFID tags 24 attached thereto, or other items. Additionally, pass through wall 800 may be used to track and control movement of medications such as initiating an above-described lock out condition if the medication detected by RFID sensors 816 are not associated with, for example, a patient located in area 804 as indicated by data stored in database 40.
  • assets that require preventative maintenance after a certain number of uses may be monitored using pass through wall 800.
  • information reflecting the number of uses of a particular asset may be updated each time the asset is detected as moving into and out of area 804. This updated use information may be stored in database 40, in the memory of RFID tag 24 associated with the asset, or both.
  • logic software 38 of server 12 may automatically change the status information associated with the asset in database 40 to "unavailable" and send notification to the appropriate facility personnel responsible for completing the preventative maintenance required.
  • system 10 provides a high resolution of location data by the detection of tags 22 by transceivers 18 and the detection of tags 24 by transceivers 20.
  • Examples of high resolution include the ability to distinguish the location of a patient, personnel, or other asset between floors of a facility, the ability to distinguish the location of a patient, personnel, or other asset between rooms, common areas, corridors, and/or other sub-divisions of a facility, and/or the ability to distinguish the location of a patient, personnel, or other asset between sub- areas within a room, corridor, common area, and/or other sub-divisions of a facility, such as near a door or sink, within a patient zone, or within a family zone.
  • the various networks and systems described herein provide automatic high resolution location data collection that may be used in a plurality of different ways.
  • system 10 By receiving continuously updated location information about various assets, such as people, equipment, and supplies, system 10 maintains an accurate database (such as database 40) of the current locations of such assets. Additionally, by retaining a history of such location data, the status and/or use of assets may readily be determined by applying certain logical rules, such as compliance with hygiene requirements for caregivers. Further, non-location and/or location independent status and use information is stored in database 40, such as medications taken. As such, logical rules may be derived from high resolution location information, non-location and/or location independent information. As also stated herein, network 16 is primarily configured to provide generally complete coverage of the facility for communication purposes, as opposed to being configured for high resolution locating and tracking, such that client devices 26 are generally always capable of communicating with the rest of system 10.
  • system 10 includes client devices 26 which are responsive to voice commands.
  • System 10 further includes appropriate logical software 38 to permit users to interact with the rest of system 10 and other users in a hands-free or near hands-free manner.
  • System 10 still maintains and updates a high resolution location and status/use database, such as database 40.
  • users of client devices 26 have the use of hands-free or near hands- free communication and control along with the ability to leverage the high resolution location information, location-derived status/use information, non-location information, and/or location-independent status/use information.
  • client device 26 may be a communicator, such as communicator 880.
  • communicator 880 may be a hands-free communicator and/or a near hands- free communicator.
  • communicator 880 may be a portable communicator, such as communicators 900, 920 (FIGS. 6A-B) described below, or a fixed communicator, such as communicators 940, 960 (FIGS. 8A-B) described below.
  • a near hands-free embodiment such as communicators 920, 960, a physical cue is required to indicate that a voice signal, such as a command and/or message, is being presented.
  • the physical cue is generic for all near hands-free communicators, such as a button.
  • the physical cue is customizable for each communicator and/or each user, such as a PIN code, fingerprint identification, or other biometric identification. It should be understood that verification information related to the custom physical cue may be stored in a local memory of the respective communicator or in a database accessible by system 10, such as database 40.
  • an audible cue may be required to indicate that a voice signal, such as a command or message is being presented.
  • hands-free communicators 900, 940 recognize a keyword as an audible cue, such as "Communicator.”
  • the keyword and/or generally phonetically similar words are not typically used in general conversation in the healthcare industry.
  • the audible cue is a common term or other easily recognizable audible signal.
  • the audible cue is a sound or series of sounds, such as a clap.
  • the audible cue is generic for all communicators.
  • the audible cue is customizable for each communicator and/or user.
  • verification information related to the custom audible cue may be stored in a local memory of the respective communicator or in a database accessible by system 10, such as database 40.
  • hands-free communicators and near hands-free communicators communicate or interact with server 882 through at least one of network 16, 19.
  • Server 882 includes logical software 884 and associated databases 886 to interact with the voice commands generated by communicators 880.
  • Database 886 may include user information, such as login information, voice characteristics, voice commands, missed call queues (described herein), message queues (described herein), event queues (described herein) and additional information.
  • Portable communicators described generally herein as communicators 900, 920 interact with server 882 over network 16.
  • Fixed communicators described generally herein as communicators 940, 960 interact with server 882 over network 19 (or alternatively network 18).
  • Server 882 is connected to server 12 and hence logical software 38 and database 40 through connection 888. As such, server 882 can query database 40 for various location, status, and/or use information, such as the high resolution data described above. Additionally, server 882, like server 12, is able to access networks 34, 36. Therefore, users of communicators 880 may perform all the functionality herein described for client devices 26 through voice commands.
  • database 886 is associated with server 12 and maintained separate from database 40.
  • Communicators 880 interact with server 12 over networks 16, 19.
  • Logical software 38 is configured to interact with the voice commands received from communicators 880.
  • database 886 is integrated with database 40 and logical software 38 is configured to interact with voice commands received from communicators 880. Any other configuration of distributed databases and/or logical software is within the teachings provided herein.
  • An exemplary hands-free portable wireless communicator 900 is shown in FIG. 6A. Hands-free communicator 900 includes a processor 902, a transceiver 904, a speaker 906, a microphone 908, and a memory 909.
  • Hands-free communicator 900 communicates with other communicators or other components accessible by system 10 over a network, such as network 16 (shown in FIGS. 1, 5A-C) and described above.
  • Transceiver 904 transmits signals to and receives signals from network 16.
  • Speaker, 906 annunciates the received voice messages.
  • Microphone 908 receives voice messages from the area proximate to communicator 900.
  • Processor 902 includes firmware or is operably coupled to software configured to control the operation of transceiver 904, speaker 906, and microphone 908 and to recognize a cue and various voice commands.
  • FIG. 7 A provides an exemplary monitor routine 910 executed by processor 902 for a hands-free communicator, such as communicator 900.
  • communicator 900 continually monitors microphone 908 for an audible signal in the absence of a request received by transceiver 904, as discussed below.
  • processor 902 determines whether the detected audible signal includes the audible cue, as represented by block
  • characteristics of the audible cue are stored locally in memory 909 and compared to characteristics of the detected audible signal.
  • characteristics of the audible cue are stored in a database of system 10, such as database 40 or 886, and are requested by processor 902 through transceiver 904 for comparison to characteristics of the detected audible signal.
  • characteristics of the audible cue are both stored locally in memory 909 and in a database of system 10. If the characteristics of the detected audible signal matches the characteristics of the audible cue, then processor 902 generates a prompt to the user requesting instructions, such as a voice command, as represented by block 913. In one example, the prompt is an audible prompt sent via speaker 906.
  • the prompt is one of a visual prompt (an optional display 919), a tactile prompt, or a combination of two or more of an audible prompt, a visual prompt, and a tactile prompt.
  • exemplary operations include various communication functions, equipment or personnel requests, status updates, or event reporting, such as Patient X is leaving surgery. Specific exemplary operations are provided herein. It should be understood that any operation requested by the user, such as initiating a call to Dr. Smith by stating the voice command "Call" followed by the identifier "Dr. Smith,” may include multiple steps or other operations, and may progress without the need of presenting the audible cue prior to each audible signal.
  • communicator 900 may time out after a period of time if no voice command is presented. Further, operations may be suspended in order to process other operations, such as a call waiting feature wherein a first call operation is suspended to receive a second call operation, as represented by blocks
  • Block 915 indicates the end of the current operation.
  • Dr. Jones is using a hands-free communicator 900, when the command is given to add Dr. Jones to the conference call, system 10 locates Dr.
  • Dr. Jones (either through the access point 21 that detects the communicator 880 associated with Dr. Jones or through the high resolution locating system) and sends the following prompt to Dr. Jones, "Conference call from Dr. Smith and X. Accept Call?" or "Incoming Call. Accept Call?”.
  • the prompt is represented by block 917 and may be an audible prompt, a textual prompt displayed on optional display 919, a tactile prompt, or a combination of two or more of an audible prompt, such as a tone, a visual prompt, such as text, and a tactile prompt.
  • Dr. Jones may then accept the call by giving the voice command "Accept Call” or decline the call by stating "Decline Call,” as represented by block 918.
  • the call may be accepted or declined without first presenting the audible cue.
  • the audible cue in order to accept or decline the call the audible cue must be presented prior to the respective voice command.
  • a user of communicator 900 may receive a request over network 16 through transceiver 904, as represented by block 916.
  • communicator 900 if Dr. Jones is already engaged in another conversation or operation, communicator 900 provides an audible prompt similar to call waiting features on traditional phones.
  • Communicator 900 and system 10 are configured to permit Dr. Jones to suspend a current call or operation and to toggle to the incoming call and back and forth, generally represented by blocks 894, 895. Additionally, operations may be terminated, as represented by block 897.
  • communicator 900 options similar to Caller ID, Call Forwarding, Voice Mail, and other suitable calling features may be incorporated into the functionality of communicator 900. Additionally, if Dr. Jones has left the facility and is no longer detected by system 10, system 10 will either transfer the call to Dr. Jones' voice mail, state in a prompt that
  • Communicator 920 is generally similar to communicator 900, expect that a button 922 is included to provide a physical cue to processor 902 that a voice command is being presented to microphone 908.
  • the caregiver associated with communicator 920 desires to initiate a voice command or perform other voice related functions, the caregiver provides the respective physical cue, depresses button 922, which signals processor 902 to monitor for an incoming voice command.
  • communicator 920 may time out after a period of time if no voice command is presented.
  • FIG. 7B provides an exemplary routine 923 executed by processor 902 for a near hands-free communicator, such as communicator 920.
  • communicator 920 is in a standby mode until a request is received over network 16 through transceiver 904, as represented by block 926, or until the respective physical cue is received, as represented by block 928. If either a request is received, as represented by block 926, or a physical cue is received, as represented by block 928, communicator 920 prompts the user for instructions, as represented by blocks 930 and 932, respectively. In one example, the prompt is an audible prompt sent via speaker 906.
  • the prompt is one of a visual prompt, a tactile prompt, or a combination of two or more of an audible prompt, a visual prompt, and a tactile prompt.
  • the user responds to the prompt with a requested operation which is then performed, as represented by block 934.
  • any operation requested by the user such as initiating a call to Dr. Smith by stating "Call to Dr. Smith" may include multiple steps or operations and may process without the need of presenting the physical cue prior to each audible signal.
  • any time the user wishes to initiate a voice command the user must provide the physical cue before stating the voice command.
  • routine 923 permits the user to suspend a current operation to initiate a second operation, as represented by blocks 925, 927. Also, suspended operations may be resumed, as represented by blocks 929, 931.
  • a user of communicator 920 may receive a request through transceiver 904, as represented by block 926. The user is prompted whether to accept the call or not, as represented by blocks 930, 936. In one example, the call may be accepted or declined without first presenting the physical cue. In another example, in order to accept or decline the call, the physical cue must be presented prior to the respective voice command. If a current operation is active, then the current operation may be suspended, as represented by blocks 933, 935.
  • communicator 920 is capable of various calling features including Call Waiting, Caller ED, Call Forwarding, Voice Mail, and other suitable calling features, and is capable of connecting to external networks, such as a cellular network.
  • Client devices 26 as described herein include many of the features of hands- free portable communicators 900 and near hands-free portable communicators 920.
  • client devices 26 require the user to select options from a menu-driven system to initiate voice communication or perform other related functions.
  • client devices 26 are configured to provide the same functionality as described herein with voice commands as opposed to menu- driven commands.
  • display 27 of client device 26 shows the corresponding menu selections if applicable.
  • Other exemplary portable communicators compatible with network 16, along with exemplary voice commands and database configurations, are described in U.S. Patent Application Serial No. 09/947,235, published as U.S. Published Patent Application No. US2003/0045279A1, to Shostak, entitled "VOICE-CONTROLLED WIRELESS COMMUNICATIONS SYSTEM AND METHOD" and U.S. Patent
  • communicator 880 may be a fixed hands-free communicator, such as communicator 940 shown in FIG. 8 A, or a fixed near hands- free communicator, such as communicator 960 shown in FIG. 8B.
  • Fixed communicators 940, 960 function similar to portable communicators 900, 920 except that the location of communicators 940, 960 is fixed.
  • fixed communicators 940, 960 are incorporated into transceivers, such as transceivers 18, 20, RAS, such as RAS 140, workstations, such as workstations 28, bed communication devices, and/or stand alone communicator devices.
  • Exemplary bed communication devices and other controllable bed devices are disclosed in the above- referenced locating and tracking patents and patent applications incorporated by reference and in U.S. Patent No. 5,715,548, filed February 10, 1998, entitled “Chair Bed,” and U.S. Patent No. 6,560,798, filed September 26, 2002, entitled “Hospital Bed Communication and Control Device", the disclosures of which are incorporated by reference herein.
  • Hands-free fixed communicator 940 executes a similar routine as hands-free portable communicator 900 and as shown in FIG. 7A.
  • Communicator 940 includes a network interface 905 which couples or otherwise connects communicator 940 to network 19. Since hands-free fixed communicator 940 is not assigned to a particular person, in one embodiment, hands-free fixed communicator 940 includes security measures to ensure that a received voice command is being given by a person with the appropriate authorization to give the voice command.
  • hands-free fixed communicator 940 includes a transceiver similar to transceivers 18 or 20 and detects the identificatipn signal presented by all (tags 22, 24) proximate to hands-free fixed communicator 940.
  • Hands-free fixed communicator 940 requests that system 10 send the access level associated with the detected personnel and/or the voice characteristics associated with the detected personnel or simply any indication of whether any of the detected personnel have the required access level. In one example, hands-free fixed communicator 940 compares the required access level for the received voice command with the access level of the detected personnel to determine if any of the personnel ' have the appropriate access level. In another example, hands-free fixed communicator 940 further compares the voice characteristics of the received voice command with the retrieved voice characteristics to determine if any of the personnel have the appropriate access level and if the person associated with the tag is the same person providing the voice command.
  • hands-free fixed communicator 940 communicates to the user that the request is accepted. Otherwise, hands-free fixed communicator 940 communicates to the user that the request is denied. In another embodiment, hands-free fixed communicator 940 sends the received voice command and/or information related to the detected tags 22, 24 to server 12. In one example, logical software 38 compares the required access level for the received voice command with the access level of the detected personnel to determine if any of the personnel have the appropriate access level. In another example, logical software 38 compares the voice characteristics of the received voice command with the retrieved voice characteristics to determine if any of the personnel have the appropriate access level.
  • near hands-free fixed communicator 960 executes a similar routine as near hands-free portable communicator 920 and as shown in FIG. 7B.
  • Communicator 960 includes a network interface 905 which couples or otherwise connects communicator 940 to network 19.
  • near hands-free fixed communicator 960 includes a transceiver similar to transceivers 18 or 20 and detects the identification signal presented by all users proximate to near hands-free fixed communicator 960.
  • Near hands-free fixed communicator 960 requests that system 10 send the access level associated with the detected personnel or an indication of whether any of the detected personnel have the required access level. In one example, near hands-free fixed communicator 960 compares the required access level for the received voice command with the access level of the detected personnel to determine if any of the personnel has the appropriate access level. In another example, near hands-free fixed communicator 960 further compares the voice characteristics of the received voice command with retrieved voice characteristics to determine if any of the personnel has the appropriate access level and if the person associated with the tag 22, 24 is the same person providing the voice command. If the voice command is from a person having the appropriate authorization, near hands-free fixed communicator 960 communicates to the user that the request is accepted.
  • fixed communicator 960 communicates to the user that the request is denied.
  • fixed communicators 940, 960 may be used to provide information to a user. For instance, if an incoming call is for Dr. Smith, server 12 checks database 40 to determine the location of Dr. Smith and then forwards the call to the communicator 940, 960 proximate to Dr. Smith or to one of communicator 900, 920, if Dr. Smith is carrying one of communicator 900, 920. Dr.
  • the present invention contemplates several exemplary applications utilizing voice commands and communication. For example, in one embodiment, the call routine discussed above in connection with FIGS. 10-14 is earned out with hands-free communicators 900 , 940 or near hands-free communicators 920, 960.
  • call initiation routine 1000 is shown. It should be understood that call initiation routine 1000 is executed by hands-free communicators 900, 940 and near hands-free communicators 920, 960 at the respective perform operation blocks 914, 934 in respective figures, FIG. 7 A, FIG. 7B.
  • the respective communicator receives a voice command to call an entity.
  • exemplary entities include a person, an organization, a group, or system 10.
  • the voice command can identify the entity by a name, a number, a title, a job function, or a group. For instance, a call may be placed to "Dr.
  • a call may be made to server 12 to query database 40.
  • communicator 880 sends a request over network 16, 19 to call the given entity, as represented by block 1004.
  • An exemplary Call voice command is "Call.”
  • a voice request might be "Communicator Call Dr. Smith”.
  • communicator 880 includes a listing of known voice commands and compares the received voice command to the list of known voice commands to verify that received voice command is a known voice command.
  • communicator 880 simply forwards the received voice command and associated identifiers and qualifiers, if any, to server 12.
  • Logical software 38 is configured to analyze the voice command and compares the voice command to a list of known voice commands to determine the desired function.
  • communicator 880 receives a signal back over network 16, 19 as to whether the call was accepted or declined. If the call was accepted, then communicator 880 permits the user to carry on a conversation with the entity and waits for a further cue, either audible or physical, an end of the current call, or a request received through the respective transceiver indicating another pending operation. It should be understood that if a further cue or other pending operation is detected, the current call operation may be suspended and later resumed or may be terminated.
  • communicator 880 is returned to its monitoring loop or standby mode or to other pending operations. If the call to the entity was declined, as explained in more detail below in connection with FIG. 10, communicator 880 sends a call denied message to the user, as represented by block 1012.
  • Communicator 880 next gives the user the option of initiating a messaging routine, such as messaging routine 1040, which allows the user to send a message to the entity, as represented by block 1014. If the user chooses not to initiate the messaging routine, then the call routine 1000 is ended, as represented by block 1010. However, if the user decides to initiate the messaging routine, communicator 880 next invokes messaging routine 1040 (shown in FIG. 11), as represented by block 1016. In a first example, a user, Dr. Smith, initiates call routine 1000 to call Dr.
  • Dr. Smith after providing the respective audible or physical cue states the voice command "Call" followed by the identifier "Dr. Jones.”
  • Communicator 880 sends the request to call Dr. Jones over network 16, 19.
  • Server 12 receives the request to call Dr. Jones and determines the location of Dr. Jones either through network 14, network 16, or network 19.
  • Server 12 then sends a message to communicator 880 associated Dr. Jones, either fixed or portable, stating that a call from Dr. Smith is incoming, as explained herein with reference to FIG. 10. Assuming Dr. Jones accepts the call, Dr. Smith's communicator 880 provides the verbal message to Dr.
  • Technician Jones is working with a piece of equipment and desires to speak with a technical expert from the manufacturer of the piece of equipment. In such a situation, Technician Jones may provide the voice command "Call" followed by the identifier "Customer support for asset A”.
  • a request is sent to server 12.
  • Server 12 through database 40 determines the customer support number associated with asset A and initiates a call through external communication system 36. Once the customer support line answers the call, Technician Jones communicator 880 states "Call accepted, begin conversation now.”
  • server 12 looks at the current location of Technician Jones and the various assets that are detected at the same location, and initiates a call based upon the asset that is proximate to Technician Jones.
  • Dr. Smith may wish to provide feedback on Resident Jones because Resident Jones has assisted Dr. Smith in providing care to Dr. Smith's patients. As such, Dr. Smith sends the following voice command "Call" followed by the identifier "Supervisor for Resident Jones.”
  • Server 12 references database 40 to determine the supervisor currently assigned for Resident Jones and attempts to complete a call to the supervisor. In yet another example, Dr. Smith may wish to determine the allergies of
  • Dr. Smith sends the following voice command "Call" followed by the identifier "Patient Allergy Database" Once the call is completed Dr. Smith is prompted for the patient name or patient id requested. In a further example, Dr. Smith may wish to speak to someone in IT support.
  • Server 12 references database 40 and initiate a call to the IT support line and connects Dr. Smith. It should be understood that Dr. Smith may also provide qualifiers after the identifier. For example, Dr. Smith may state the voice command "Call” followed by the identifier "IT support” followed by the qualifier "Closest Location.” Server 12 references database 40 to determine the IT staff member whose location is the closest to Dr. Smith and connects Dr. Smith to that person. In yet a further example, Dr. Smith may wish to send a call to a group of people such as Surgical Team A. This may be done by issuing the voice command
  • calls initiated through communicator 880 may be routed to another communicator 880, a paging system, a traditional phone system, a cellular phone system, an RSA , such as RAS 140 discussed above, or other suitable communication devices and networks accessible by system 10.
  • a paging system a traditional phone system
  • a cellular phone system a cellular phone system
  • an RSA such as RAS 140 discussed above
  • an incoming call routine 1018 is shown. Incoming calls may be initiated from other communicators 880 using call routine 1000, paging systems, traditional phone networks, cellular networks, or other communication networks connected to system 10. Further, incoming calls may be generated by server 12 based upon the updated location information of persons and assets and use/status information of assets.
  • server 12 detecting a code blue situation can automatically dispatch calls to communicators 880 which are associated to caregivers who are in the proximity of the code blue situation and/or caregivers which are assigned to the patient associated with the code blue situation.
  • incoming calls may be initiated by server 12 based upon the location information of various tags 22, 24. For example, the detection of a patient leaving an operating room could trigger a call to appropriate caregivers to prepare a recovery room to notify family members, or to notify appropriate caregivers that the patient will soon be located in the recovery area.
  • the incoming call is received from network 16, 19 by communicator 880.
  • Communicator 880 may be configured to block incoming calls based on priorities, calling entities, or calls in general.
  • communicator 880 checks to see if the incoming call is a currently blocked call. If the call is not blocked, communicator 880 prompts the user of the incoming call, as represented by block
  • An exemplary prompt is "Call from Dr. Smith. Accept call?" The user then responds with a voice command to either accept the call "Accept call” or to decline the call “Decline call.” If the call is accepted, then communicator 880 permits the conversation to transpire, as represented by block 1028. If the call is not accepted, communicator 880 sends a call declined message through network 16, 19, as represented by block 1030. Server 12 then notifies the calling party that the call has been declined. In one example, either server 12 or communicator 880 keeps a list of declined callers in a missed call queue as represented by block 1032. As such, the user of communicator 880 is provided with a list of all callers who have attempted to call communicator 880, but were declined.
  • a message routine 1040 is shown.
  • communicator 880 receives a voice command to send a message to an entity. Similar to the "Call" voice command, the "Send Message" voice command may be sent to a name, a number, a title, a job function, server 12, or a group.
  • Communicator 880 then prompts the user to record the message, as represented by block 1044.
  • An exemplary prompt is "Please record message after the tone" followed by a tone.
  • communicator 880 Once the user has completed the message detected by communicator 880 by either a cue, a cue followed by a voice command, and/or silence for a predetermined period of time, the user is given the option to have the message replayed, as represented by block 1046. If the user decides to have the message replayed, communicator 880 plays the message, as represented by block 1048. After the user has heard the replay of the message, the user is presented with a prompt asking if they wish to record a new message, as represented by block 1050. If the user responds with a "Yes" voice command, communicator 880 again prompts the user to record the message, as represented by block 1044.
  • the user responds with a "No" voice command, the user is then prompted whether to send the message or not, as represented by block 1052. If the user chooses to send the message (responds with a "Yes" voice command), the message is sent over network 16, 19 to the respective entity, as represented by block 1054 and the operation is ended as represented by block 1056. If the user decides not to send the message (responds with a "No” voice command), then the operation ends, as represented by block 1056.
  • the message sent by the user as discussed above, is received by the communicator 880 associated with the recipient.
  • the associated communicator 880 either portable or fixed, initiates the receive message routine 1060 as shown in FIG. 12. The user is notified of unheard messages, as represented by block 1062.
  • communicator 880 identifies the unheard message, as represented by block 1064.
  • An example identifier is "Unheard message from Dr. Smith.”
  • communicator 880 in one example adds the message to a message queue, the contents of which are presented to the user once the calls are unblocked. The user is then prompted whether they wish to play the message, as represented by block 1066. If the user responds with a "No" voice command, then the user is next prompted whether to delete the message, as represented by block 1068. If the user responds with a "Yes" voice command, the message is deleted, as represented by block 1070.
  • the message is retained in the message queue and communicator 880 queries to see if additional unheard messages are present in the message queue, as represented by block 1072. In one embodiment, messages may be forwarded to another entity.
  • the user if the user instead decides to play the message by responding with a "Yes" voice command, the message is played for the user, as represented by block 1073. After the message has been played, the user is prompted whether they wish to call the sender, as represented by block 1074. If the user responds with a "No" voice command, the user is then presented with the option to delete the message, as represented by block 1068.
  • call routine 1000 is initiated, as represented by block 1076.
  • the receive messages routine 1060 is suspended while call routine 1000 is active. Once call routine 1000 has terminated, the user is returned to message routine 1060, as represented by block 1078.
  • Communicator 880 next checks to see if additional unheard messages are present in the queue, as represented by block 1072. If additional messages are not present in the queue, the receive message routine 1060 ends operation, as represented by block 1080.
  • the system provides the message to the user "no unheard messages.” If additional unheard messages are present in the queue, communicator 880 identifies the next message in the queue, as represented by block 1082, and the user is again presented with the option to play the message, as represented by block 1066.
  • the message routine 1060 continues until all unheard messages have been considered. However, as explained above, message routine 1060 like other operation routines may be suspended or interrupted by other operations.
  • FIG. 13 an environmental setting routine is shown. As described herein, various environmental settings including lighting, audio and television volumes, bed controls, and other settings may be automatically controlled by the detection of a tag 22, 24 within a particular area, such as a caregiver entering a patient room.
  • the environmental settings for a particular area may be adjusted based upon voice commands received by communicator 880.
  • communicator 880 receives a voice command related to an environmental setting for an asset or a location.
  • An exemplary voice command would be "mute television.”
  • the voice command is forwarded to server 12, which in turn causes the environmental setting to be adjusted.
  • server 12 determines the current location of the person associated with communicator 880 initiating the request through database 40 and the television proximate to that location. The system then sends a signal to the television to mute the television. In one example, once the caregiver leaves the area, the television is returned to its previous settings. As represented by block 1096, the adjusted setting is communicated to the user through communicator 880. An example, message would be "Television muted.” Alternatively, if the environmental setting change requested cannot be processed, server 12 notifies the requestor with a message such as "Not able to mute television at this time.” As represented by block 1098, the operation is then ended.
  • An ambulatory navigation system for persons within a facility may be implemented with communicators 880.
  • An exemplary ambulatory navigation system is provided in co-pending application Serial No. 09/798,398, published as U.S. Published Patent Application No. US 2002/0123843 Al, filed March 2, 2001, the disclosure of which is expressly incorporated herein by reference.
  • the disclosed ambulatory navigation system provides a user with instructions on how to reach a given location in a facility from the current location of the user.
  • FIG. 14 an exemplary navigation assistance routine 1100 for use with communicators 880 is shown.
  • Communicator 880 receives a voice command related to navigation assistance as represented by block 1102.
  • An example voice command would be "Navigation Instructions" followed by the identifier "Location X.”
  • server 12 determines a path from the current location of the user stored in database 40 to the requested location, as represented by block 1104. It should be understood that the determined path should be selected based upon areas that the user has privilege or access to enter. The access level of the user is stored in database 40. Server 12 then provides instructions from the current location to the requested location to the user, as represented by block 1106. Alternatively, the user is first prompted regarding whether the user prefers to receive complete instructions or incremental instructions, as represented by block 1108.
  • the user responds with the voice command, "Complete Instructions,” the user is provided with complete instructions, as represented by block 1106 and the operation ends, as represented by block 1108.
  • “Incremental Instructions” the user is first provided instructions to a location along the path to the requested location proximate to the current location. For example, the instructions to the incremental location may be "head west along corridor to the bank of elevators.” Next, the current location of the user is compared to the requested location to determine if the user is at the requested location, as represented by block 1112. If the current location and the requested location are the same, then the operation ends, as represented by block 1109.
  • a secure access routine 1120 is shown. Often times a given area, such as a portion of a facility or a medicine cabinet, may be locked and a user has to request access to such area. Access to a secure area is based upon the access level of the requester.
  • the identification of the tags proximate to an entrance to the secure area are used to assist in determining if the requester has the required access level.
  • Secure access routine 1120 uses both the identification of tags proximate to the entrance of the secure area and the voice characteristics of the person requesting access to determine whether the requestor is authorized to gain access to the secure area.
  • communicator 880 receives a voice command requesting access to the secure area.
  • a exemplary voice command is "Unlock medicine cabinet.” This voice command is then processed by server 12, which checks to see if one or more tags 22, 24 are proximate to the secure area, as represented by block 1124.
  • server 12 determines the identity of the tags 22, 24 proximate to the secure area, as represented by block 1128. Further, the system analyzes the voice characteristics of the voice command, as represented by block 1130. The voice characteristics from the voice command are compared to the voice characteristics associated with the identified tags 22, 24 which are stored in database 40 as represented by blocks 1132A-B. Assuming the two voice characteristics match, the user is sent a request granted message, as represented by block 1134, access is permitted (unlocked), and the operation ends as represented by block 1136.
  • the system also notifies security personnel proximate to the secure area of the attempted unauthorized entry, as represented by block 1140.
  • Shown in FIG. 16 is a security routine 1150.
  • Security routine 1150 monitors the movement of tags 22, 24 and detects the movement of tags 22, 24 into an unauthorized area as represented by block 1152.
  • movement of a tag into an unauthorized area is the movement of a piece of equipment beyond the entrance or exit of a facility.
  • Another example of unauthorized movement is the positioning of an infant near an exit of the maternity ward.
  • an alert message is sent to communicators 880 associated with the identified personnel, as represented by block 1160.
  • a description of the items associated with tag 22, 24 is given in the alert message along with other characteristics of the item.
  • the system may provide additional security based on the location of the unauthorized tag 22, 24, such as the locking of doors or an audible alarm, as represented by block 1162.
  • the system continues to track the movement of the unauthorized tag 22, 24, as long as the tag is detected by the system, as represented by block 1164. As the unauthorized tag 22, 24 moves throughout the facility, the personnel who are proximate to the current location of the unauthorized tag continually changes and the system updates a listing of qualified personnel proximate to the unauthorized tag, as represented by block 1166.
  • the system next determines if the unauthorized tag 22, 24 has been captured, as represented by block 1168. In one example, the system determines the tag 22, 24 has been captured based upon the proximity of the tag to the tag of identified personnel. In another example, the system determines if the tag 22, 24 has been captured when it receives a voice command from a communicator located proximate to the captured tag stating that the tag has been captured. If the tag 22, 24 has been captured, the system then sends a captured tag message to all communicators 880 which were previously placed on alert, as represented by block 1170, and the operation is ended, as represented by block 1172.
  • a location monitoring routine 1180 is shown.
  • Location monitoring routine 1180 permits a user to request the location of an asset or person to automate the retrieval of the asset or to initiate a call to the person responsible for the asset.
  • Location monitoring routine 1180 further permits a user to monitor the location of an asset or person and be notified of changes in location. For example, a caregiver may be notified when a patient wanders beyond a predetermined boundary or exits his bed.
  • Communicator 880 receives a voice command requesting location or status information of an asset or person, as represented in block 1182.
  • An example voice command is "Retrieve location” followed by the identifier "Dr. Smith.”
  • Server 12 determines the location and/or status of Dr. Smith and returns that information to communicator 880.
  • Communicator 880 then receives the location and/or status information related to the asset or person, as represented by block 1184, and communicates the location or status information to the user, as represented by block
  • the location or status request can include qualifiers following the identifier. For example, a user can give the voice command “Retrieve location” followed by the identifier "Wheelchair” followed by the two qualifiers “Closest” and "Available.” Server 12 will determine the location of all wheelchairs and return the location of the closest available wheelchair.
  • the determination of the closest wheelchair may return a location of "at the end of the hall” instead of "directly above the user on the next floor.”
  • communicators 880 are fixed communicators, such as communicators 940, 960
  • the location of the closest wheelchair may be determined by the location system of network 16 because a knowledge of the location of communicators 940, 960 assists in determining the location of the requestor. The user is then prompted whether they wish to call the identified person, if a person was requested, or to call a person assigned to the asset, as represented by block
  • call routine 1000 is initiated to either call the identified person or to call a person whose job function and/or proximity is associated with the requested asset, as represented by block 1192.
  • the user of communicator 880 requests the location information about a person or asset such as a patient assigned to that user. In one example, the patient is in surgery and the user wishes to verify that the patient is still in surgery. The user is prompted as to whether the user wants to add an event to monitor the location of the patient, as represented by block 1194.
  • the user may wish to monitor when the patient leaves the surgical room such that the caregiver may be prepared to take care of the patient when he arrives in his patient room. If the caregiver responds that he does not want to add an event to an event monitoring queue, then the operation is ended, as represented by block 1190. If the caregiver wants to add an event to the event monitoring queue, then the caregiver provides voice commands related to the event to be monitored, as represented by block 1196.
  • communicators 880 may be used to notify caregivers of alerts generated by the exubation prevention method and of alert messages generated by the fall prevention method, both of which are disclosed in co-pending U.S. Patent Application Serial No. 10/141,457 referenced above, the disclosure of which is incorporated by reference herein.
  • the disclosed system sends an alert to communicator 880 of the caregiver assigned to the patient.
  • the disclosed system sends an alert to communicator 880 of the caregiver determined to be closest to the patient associated with the alert.
  • communicators 880 may be used to notify caregivers of alerts or alarms, patient medication information, and/or location data generated by the medication tracking system, including the location of medication, the activation of transmitters, and verification that the medication is in the target location, disclosed in co-pending U.S. Patent Application Serial No. 10/211,187, filed August 2, 2002, and published as U.S. Published Application No. US2003/0048187A1, the disclosure of which is incorporated by reference herein.
  • the disclosed medication tracking system sends an alert, patient medication information, and/or location ⁇ information to communicator 880 of the caregiver proximate to the medication.
  • the disclosed medication tracking system sends an alert, patient medication information, and/or location information to communicator 880 of the caregiver assigned to the patient.
  • communicators 880 may be used to notify caregivers of alerts generated by the proximity alarm systems in response to the separation between two tags 22, 24 exceeding a predetermined maximum distance, disclosed in co-pending U.S. Patent Application Serial No. 10/430,643, filed May 6, 2003, entitled "MEDICAL EQUIPMENT CONTROLLER," the disclosure of which is incorporated by reference herein.
  • the disclosed system sends an alert to communicator 880 of the personnel or caregiver assigned to the one of the two tags
  • the disclosed system sends an alert to communicator 880 of the personnel or caregiver determined to be closest to the patient associated with the alert. In yet another example, the disclosed system sends an alert to communicator 880 of the personnel or caregiver determined to be closest to the patient associated with the alert and which are qualified to respond to the alert. While the invention has been illustrated and described in detail in the drawings and foregoing description, such illustration and description is to be considered as exemplary and not restrictive in character, it being understood that only exemplary embodiments have been shown and described and that all changes and modifications that come within the spirit of the invention are desired to be protected.

Abstract

L'invention concerne un système de communication, de localisation et de suivi de biens mis en oeuvre par un dispositif sans fil de localisation et de suivi à haute résolution comprenant plusieurs récepteurs situés à différents emplacements de l'établissement, tels que les planchers, les pièces, les couloirs, les espaces communs ou leurs parties, à l'intérieur de l'établissement. Le système de localisation est relié à un système de communications sans fil présentant plusieurs points d'accès et dispositifs de communications mains libres à commande vocale. L'émission d'une commande vocale destinée au dispositif de communications permet au système de localiser un bien.
PCT/US2004/034473 2003-10-16 2004-10-18 Systeme universel de communications, de surveillance, de localisation et de controle pour etablissement sanitaire WO2005045461A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/575,801 US20070080801A1 (en) 2003-10-16 2004-10-18 Universal communications, monitoring, tracking, and control system for a healthcare facility

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US51173703P 2003-10-16 2003-10-16
US60/511,737 2003-10-16

Publications (1)

Publication Number Publication Date
WO2005045461A1 true WO2005045461A1 (fr) 2005-05-19

Family

ID=34572748

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2004/034473 WO2005045461A1 (fr) 2003-10-16 2004-10-18 Systeme universel de communications, de surveillance, de localisation et de controle pour etablissement sanitaire

Country Status (2)

Country Link
US (1) US20070080801A1 (fr)
WO (1) WO2005045461A1 (fr)

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1954186A1 (fr) * 2005-11-23 2008-08-13 Koninklijke Philips Electronics N.V. Moniteur de parametres multiples porte au poignet presentant une meilleure fonctionnalite et une plus grande precision
US20090051546A1 (en) * 2006-04-10 2009-02-26 Neeraj Bhavani Intelligent Routing Of Patients Using Distributed Input Devices
US8760260B2 (en) 2007-05-18 2014-06-24 3M Innovative Properties Company Method for tracking cyclical procedures performed on personal protection equipment
US9492690B2 (en) 2007-08-31 2016-11-15 3M Innovative Properties Company Determining conditions of components removably coupled to personal protection equipment
US9536209B2 (en) 2007-08-31 2017-01-03 3M Innovative Properties Company Tracking compliance of personal protection articles
US9564951B2 (en) 2007-05-18 2017-02-07 3M Innovative Properties Company Method for tracking procedures performed on personal protection equipment and actions of individuals
US9901125B2 (en) 2007-08-31 2018-02-27 3M Innovative Properties Company Determining conditions of personal protection articles against at least one criterion
CN110931089A (zh) * 2018-08-30 2020-03-27 希尔-罗姆服务公司 用于emr生命体征记录的系统和方法
US10610624B2 (en) 2013-03-14 2020-04-07 Smith & Nephew, Inc. Reduced pressure therapy blockage detection
US10639502B2 (en) 2010-10-12 2020-05-05 Smith & Nephew, Inc. Medical device
US11049611B1 (en) * 2018-06-13 2021-06-29 Ortelligence, Inc. Systems, methods and devices for dynamic procedure management
US11315681B2 (en) 2015-10-07 2022-04-26 Smith & Nephew, Inc. Reduced pressure therapy device operation and authorization monitoring
US11348443B2 (en) 2019-10-23 2022-05-31 Gojo Industries, Inc. Methods and systems for improved accuracy in hand-hygiene compliance
US11369730B2 (en) 2016-09-29 2022-06-28 Smith & Nephew, Inc. Construction and protection of components in negative pressure wound therapy systems
US11602461B2 (en) 2016-05-13 2023-03-14 Smith & Nephew, Inc. Automatic wound coupling detection in negative pressure wound therapy systems
US11712508B2 (en) 2017-07-10 2023-08-01 Smith & Nephew, Inc. Systems and methods for directly interacting with communications module of wound therapy apparatus
US11793924B2 (en) 2018-12-19 2023-10-24 T.J.Smith And Nephew, Limited Systems and methods for delivering prescribed wound therapy
US11862330B2 (en) 2006-04-10 2024-01-02 Tagnos, Inc. Proximity based systems for contact tracing

Families Citing this family (54)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2408230A1 (fr) 2000-05-05 2001-11-15 Hill-Rom Services, Inc. Systeme informatique utilisable a l'emplacement des soins prodigues a un patient
EP1894138A1 (fr) * 2005-06-08 2008-03-05 Nycomed GmbH Méthode
US7286057B2 (en) * 2005-06-20 2007-10-23 Biovigil Llc Hand cleanliness
US8502681B2 (en) * 2005-06-20 2013-08-06 Biovigil, Llc Hand cleanliness
US7616122B2 (en) * 2005-06-20 2009-11-10 Biovigil, Llc Hand cleanliness
US7936275B2 (en) * 2005-06-20 2011-05-03 Biovigil, Llc Hand cleanliness
US20090315735A1 (en) * 2006-04-10 2009-12-24 Bhavani Neeraj S Patient flow management and analysis using location tracking
US20080031838A1 (en) * 2006-08-03 2008-02-07 Bolling Steven F Tracing hand cleaner
JP5185570B2 (ja) * 2007-06-07 2013-04-17 株式会社ユニバーサルエンターテインメント 個人識別通信システム及び個人識別通信システムにおいて実行されるプログラム
US20090066486A1 (en) * 2007-09-11 2009-03-12 Omni Control Systems, Inc. Modular signal device for a room occupancy management system and a method for using same
US7893842B2 (en) * 2007-10-05 2011-02-22 Richard Deutsch Systems and methods for monitoring health care workers and patients
EP2211689A4 (fr) * 2007-10-08 2013-04-17 Univ California Ucla Office Of Intellectual Property Tableau de bord d'informations cliniques à commande vocale
US9026447B2 (en) 2007-11-16 2015-05-05 Centurylink Intellectual Property Llc Command and control of devices and applications by voice using a communication base system
WO2009097096A1 (fr) * 2008-01-28 2009-08-06 Richard Deutsch Système et méthode de suivi du personnel de santé et des patients
EP2793154B1 (fr) * 2008-05-27 2021-03-31 Stryker Corporation Agencement sans fil de contrôle de salle médicale pour contrôler une pluralité de dispositifs médicaux
US8255225B2 (en) 2008-08-07 2012-08-28 Vocollect Healthcare Systems, Inc. Voice assistant system
US8451101B2 (en) * 2008-08-28 2013-05-28 Vocollect, Inc. Speech-driven patient care system with wearable devices
US9147334B2 (en) 2008-11-19 2015-09-29 Proventix Systems, Inc. System and method for monitoring hospital workflow compliance with a hand hygiene network
US9305191B2 (en) 2009-11-17 2016-04-05 Proventix Systems, Inc. Systems and methods for using a hand hygiene compliance system to improve workflow
US7920061B2 (en) * 2008-11-26 2011-04-05 General Electric Company Controlling an alarm state based on the presence or absence of a caregiver in a patient's room
AU2009327083A1 (en) * 2008-12-18 2011-06-23 Safe Contact Aps Hand hygiene system
US8310374B2 (en) * 2009-03-04 2012-11-13 General Electric Company Telemetry system and method
US8203447B2 (en) * 2009-03-04 2012-06-19 General Electric Company Telemetry system and method
WO2010108018A2 (fr) * 2009-03-18 2010-09-23 Mayo Foundation For Medical Education And Research Surveillance et commande de respirateur
US9619617B2 (en) * 2009-08-13 2017-04-11 Aethon, Inc. System and method for determining a location and a status of an asset
US20110057799A1 (en) * 2009-09-01 2011-03-10 Yordan Gineff Taneff Hand washing monitoring system
US9030325B2 (en) 2009-09-01 2015-05-12 Yordan Gineff Taneff Hand washing enforcement system
US8564431B2 (en) * 2010-01-07 2013-10-22 Ultraclenz, Llc Wireless monitoring and communication for sanitizer dispenser systems
US20110234598A1 (en) * 2010-03-25 2011-09-29 General Electric Company System and method to manage hand hygiene
JP5039214B2 (ja) * 2011-02-17 2012-10-03 株式会社東芝 音声認識操作装置及び音声認識操作方法
US20120290311A1 (en) * 2011-05-13 2012-11-15 Saurabh Tara Method and Apparatus for Physician Location Tracking
US20140081659A1 (en) 2012-09-17 2014-03-20 Depuy Orthopaedics, Inc. Systems and methods for surgical and interventional planning, support, post-operative follow-up, and functional recovery tracking
EP2775463A1 (fr) * 2013-03-06 2014-09-10 Koninklijke Philips N.V. Systèmes et procédés pour réduire l'impact de sons d'alarme sur des patients
US10872387B2 (en) * 2013-03-15 2020-12-22 Teletracking Technologies, Inc. Hospital bed event notification
US20160012249A1 (en) * 2013-03-15 2016-01-14 Ellipson Data Llc Method for collecting and securing physiological, biometric and other data in a personal database
CN103792947A (zh) * 2014-02-28 2014-05-14 哈尔滨伟方智能科技开发有限责任公司 一种小型医疗救助旋翼飞行机器人
AU2015229693B2 (en) 2014-03-10 2016-10-06 Gojo Industries, Inc. Hygiene tracking compliance
US20150281810A1 (en) * 2014-03-31 2015-10-01 Funai Electric Co., Ltd. Information Processing Apparatus, Information Transmission System, and Method for Transmitting Information
US10764081B2 (en) * 2014-07-28 2020-09-01 Vivint, Inc. Asynchronous communications using home automation system
US9871830B2 (en) * 2014-10-07 2018-01-16 Cisco Technology, Inc. Internet of things context-enabled device-driven tracking
WO2016099521A1 (fr) * 2014-12-18 2016-06-23 Draeger Medical Systems, Inc. Commande d'annonce d'alarme et de caractéristiques de fonctionnement de moniteur de patient sur la base de la proximité de personnel soignant
US20160373909A1 (en) * 2015-06-17 2016-12-22 Hive Life, LLC Wireless audio, security communication and home automation
US9626850B2 (en) 2015-09-02 2017-04-18 Vivint, Inc. Home automation communication system
US9839735B2 (en) * 2015-09-08 2017-12-12 Fresenius Medical Care Holdings, Inc. Voice interface for a dialysis machine
US9877266B1 (en) * 2015-12-10 2018-01-23 Massachusetts Mutual Life Insurance Company Methods and systems for beacon-based management of shared resources
US10409550B2 (en) * 2016-03-04 2019-09-10 Ricoh Company, Ltd. Voice control of interactive whiteboard appliances
CN108781406B (zh) * 2016-03-14 2021-09-07 罗伯特·博世有限公司 用于内部通话系统的无线接入点和路由音频流数据的方法
US10157536B2 (en) * 2016-08-08 2018-12-18 Yair Zuckerman Dispatch management platform for nurse call system
US11069220B2 (en) 2017-07-10 2021-07-20 Biovigil Hygiene Technologies, Llc Hand cleanliness monitoring
CN108062164A (zh) * 2018-01-15 2018-05-22 杭州易同全科技有限公司 用于手卫生依从性监管的智能终端
US11062707B2 (en) * 2018-06-28 2021-07-13 Hill-Rom Services, Inc. Voice recognition for patient care environment
US10734110B2 (en) * 2018-12-05 2020-08-04 Hill-Rom Services, Inc. Caregiver locating tag having advanced functionality
US11626001B1 (en) * 2020-07-28 2023-04-11 United Services Automobile Association (Usaa) Wearable system for detection of environmental hazards
US11881219B2 (en) 2020-09-28 2024-01-23 Hill-Rom Services, Inc. Voice control in a healthcare facility

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5515426A (en) * 1994-02-28 1996-05-07 Executone Information Systems, Inc. Telephone communication system having a locator
WO1998048394A1 (fr) * 1997-04-22 1998-10-29 Koninklijke Philips Electronics N.V. Dispositif de commande a distance
US6281811B1 (en) * 1999-06-11 2001-08-28 Anthony S Ranzino Communication and location system for shopping malls, parks, business districts, and the like
US20020126035A1 (en) * 2001-03-12 2002-09-12 Shaw-Yuan Hou Voice-activated remote control unit for multiple electrical apparatuses
US6456239B1 (en) * 1999-08-25 2002-09-24 Rf Technologies, Inc. Method and apparatus for locating mobile tags
US20030022696A1 (en) * 2001-07-24 2003-01-30 S. Jeffrey Rosner Wireless communications system fully integrated with the infrastructure of an organization
US20030073434A1 (en) * 2001-09-05 2003-04-17 Shostak Robert E. Voice-controlled wireless communications system and method

Family Cites Families (102)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
BE531515A (fr) * 1953-09-14
US3439320A (en) * 1967-09-21 1969-04-15 Relton Corp Personnel location system
US3714573A (en) * 1970-05-06 1973-01-30 Hazeltine Corp Spread-spectrum position monitoring system
US3739329A (en) * 1971-05-24 1973-06-12 Recognition Devices Electronic system for locating
US3805265A (en) * 1971-10-06 1974-04-16 Rcds Enterprises Inc Radiant wave locating system
US3805227A (en) * 1972-10-03 1974-04-16 Rcds Enterprises Inc Electronic tracking locating system using multiple frequency, modulated, and time delayed ultrasonic signals
US4151407A (en) * 1977-04-28 1979-04-24 Texas Instruments Incorporated Low-power, infrared information transmission system
US4216462A (en) * 1978-03-06 1980-08-05 General Electric Company Patient monitoring and data processing system
US4275385A (en) * 1979-08-13 1981-06-23 Bell Telephone Laboratories, Incorporated Infrared personnel locator system
US4601064A (en) * 1983-01-13 1986-07-15 Fisher Berkeley Corporation Communication system
US4649385A (en) * 1982-08-13 1987-03-10 Teloc R & D Ltd. Electronic locating system for persons receiving telephone calls
US4598275A (en) * 1983-05-09 1986-07-01 Marc Industries Incorporated Movement monitor
US4843640A (en) * 1986-04-24 1989-06-27 Gte Valeron Corporation Industrial identification transponder
US4728928A (en) * 1986-05-08 1988-03-01 Fisher Berkeley Corporation Call switch for wet areas
US4740792A (en) * 1986-08-27 1988-04-26 Hughes Aircraft Company Vehicle location system
US4837568A (en) * 1987-07-08 1989-06-06 Snaper Alvin A Remote access personnel identification and tracking system
US5027314A (en) * 1988-03-17 1991-06-25 United Manufacturing Co., Inc. Apparatus and method for position reporting
AU4292689A (en) * 1988-10-14 1990-04-26 Total Alert Corportation Personal locator transmitter
US4981141A (en) * 1989-02-15 1991-01-01 Jacob Segalowitz Wireless electrocardiographic monitoring system
GB2230365B (en) * 1989-02-18 1993-05-26 Olivetti Research Ltd Mobile carrier tracking system
JPH02228939A (ja) * 1989-03-03 1990-09-11 Fukuda Denshi Co Ltd Ｌａｎを用いた患者監視システム
US5012113A (en) * 1989-04-28 1991-04-30 Martin Marietta Energy Systems, Inc. Infrared system for monitoring movement of objects
US4990892A (en) * 1989-08-07 1991-02-05 Westcom, A Division Of Westside Communications Of Jacksonville, Inc. Personnel locator system
US5036852A (en) * 1989-12-08 1991-08-06 Leishman Mark L Medical equipment monitor apparatus and method
US5226090A (en) * 1989-12-29 1993-07-06 Pioneer Electronic Corporation Voice-operated remote control system
US5119104A (en) * 1990-05-04 1992-06-02 Heller Alan C Location system adapted for use in multipath environments
US5594786A (en) * 1990-07-27 1997-01-14 Executone Information Systems, Inc. Patient care and communication system
US5291399A (en) * 1990-07-27 1994-03-01 Executone Information Systems, Inc. Method and apparatus for accessing a portable personal database as for a hospital environment
US5214421A (en) * 1990-07-30 1993-05-25 Support Systems International Corp. Automatic keyboard and monitor switching device
CA2090608C (fr) * 1990-08-31 2000-01-11 James P. Welch Reseau de dispositifs portatifs de surveillance des patients
US5493283A (en) * 1990-09-28 1996-02-20 Olivetti Research Limited Locating and authentication system
EP0556277A1 (fr) * 1990-11-06 1993-08-25 Westinghouse Electric Corporation Systeme d'identification electronique a deux modes
US5231991A (en) * 1990-12-21 1993-08-03 Protocol Systems, Inc. Apparatus for promoting waste-free primary flow in a patient monitoring device
US5218344A (en) * 1991-07-31 1993-06-08 Ricketts James G Method and system for monitoring personnel
US5396224A (en) * 1991-11-22 1995-03-07 Hewlett-Packard Company Telemetered patient location system and method
CH684134A5 (de) * 1991-12-16 1994-07-15 Heinrich Sieber An einen Gegenstand anbringbarer Sicherungsanhänger zur Signalisierung eines versuchten Diebstahls.
US5390238A (en) * 1992-06-15 1995-02-14 Motorola, Inc. Health support system
US5426425A (en) * 1992-10-07 1995-06-20 Wescom, Inc. Intelligent locator system with multiple bits represented in each pulse
US5590648A (en) * 1992-11-30 1997-01-07 Tremont Medical Personal health care system
US5319191A (en) * 1993-03-25 1994-06-07 K & M Electronics, Inc. Ask receiver with signal delay and stretching
SG46326A1 (en) * 1993-05-06 1998-02-20 Spectronics Micro Syst Ltd Improvements in automatic vehicle location system
US5412715A (en) * 1993-05-19 1995-05-02 Executone Information Systems, Inc. Apparatus and method for connecting telephone switching devices
US5627524A (en) * 1993-06-07 1997-05-06 Lifecom, Llc Infrared locator system
US5387993A (en) * 1993-06-25 1995-02-07 Precision Tracking Fm, Inc. Method for receiving and transmitting optical data and control information to and from remotely located receivers and transmitters in an optical locator system
US5561412A (en) * 1993-07-12 1996-10-01 Hill-Rom, Inc. Patient/nurse call system
US5621384A (en) * 1993-07-26 1997-04-15 K And M Electronics, Inc. Infrared communicating device
US5635907A (en) * 1993-08-10 1997-06-03 Bernard; Hermanus A. Location system
US5525967A (en) * 1993-11-01 1996-06-11 Azizi; S. Massoud System and method for tracking and locating an object
IL107461A (en) * 1993-11-01 1997-04-15 Tadiran Ltd Personal location and message system and unit
US5504477A (en) * 1993-11-15 1996-04-02 Wybron, Inc. Tracking system
US5417222A (en) * 1994-01-21 1995-05-23 Hewlett-Packard Company Patient monitoring system
US5534876A (en) * 1994-03-10 1996-07-09 Motorola, Inc. Multipath tolerant location system and method therefor
US5652570A (en) * 1994-05-19 1997-07-29 Lepkofker; Robert Individual location system
US5600108A (en) * 1994-08-29 1997-02-04 Bed-Check Corporation Docking module enclosure including connectors and power switching
CA2320671A1 (fr) * 1994-09-21 1996-03-28 Robert T. Shipley Appareil de transmission optique de donnees et de localisation, et systeme, procede, emetteurs et recepteurs utilises conjointement
US5541585A (en) * 1994-10-11 1996-07-30 Stanley Home Automation Security system for controlling building access
NL9402126A (nl) * 1994-12-15 1996-07-01 Hollandse Signaalapparaten Bv Informatiesysteem voor een schip.
US5629678A (en) * 1995-01-10 1997-05-13 Paul A. Gargano Personal tracking and recovery system
US5532690A (en) * 1995-04-04 1996-07-02 Itt Corporation Apparatus and method for monitoring and bounding the path of a ground vehicle
US5640002A (en) * 1995-08-15 1997-06-17 Ruppert; Jonathan Paul Portable RF ID tag and barcode reader
US5748148A (en) * 1995-09-19 1998-05-05 H.M.W. Consulting, Inc. Positional information storage and retrieval system and method
US6040773A (en) * 1995-10-11 2000-03-21 Motorola, Inc. Radio frequency identification tag arranged for magnetically storing tag state information
US5722599A (en) * 1996-02-21 1998-03-03 Central Sprinkler Corporation Sidewall fire sprinkler head
FR2745093B1 (fr) * 1996-02-21 1998-04-24 Legrand Sa Procede et dispositif de detection de presence d'un etre vivant d'espece particuliere dans un espace surveille par un capteur doppler
US5714932A (en) * 1996-02-27 1998-02-03 Radtronics, Inc. Radio frequency security system with direction and distance locator
US5767788A (en) * 1996-03-19 1998-06-16 Ness; James C. Computer aided dispatch and locator cellular system
US5732401A (en) * 1996-03-29 1998-03-24 Intellitecs International Ltd. Activity based cost tracking systems
US5745037A (en) * 1996-06-13 1998-04-28 Northrop Grumman Corporation Personnel monitoring tag
US5731757A (en) * 1996-08-19 1998-03-24 Pro Tech Monitoring, Inc. Portable tracking apparatus for continuous position determination of criminal offenders and victims
US5926090A (en) * 1996-08-26 1999-07-20 Sharper Image Corporation Lost article detector unit with adaptive actuation signal recognition and visual and/or audible locating signal
US5732711A (en) * 1996-08-27 1998-03-31 Air-Shields, Inc. Body function measuring apparatus
US6272457B1 (en) * 1996-09-16 2001-08-07 Datria Systems, Inc. Spatial asset management system that time-tags and combines captured speech data and captured location data using a predifed reference grammar with a semantic relationship structure
US5771003A (en) * 1996-09-24 1998-06-23 Elenco Electronics, Inc. Locating system and process
US5748084A (en) * 1996-11-18 1998-05-05 Isikoff; Jeremy M. Device security system
US5742233A (en) * 1997-01-21 1998-04-21 Hoffman Resources, Llc Personal security and tracking system
US5920287A (en) * 1997-01-21 1999-07-06 Widata Corporation Radio location system for precisely tracking objects by RF transceiver tags which randomly and repetitively emit wideband identification signals
US6204813B1 (en) * 1998-02-20 2001-03-20 Trakus, Inc. Local area multiple object tracking system
US5914671A (en) * 1997-02-27 1999-06-22 Micron Communications, Inc. System and method for locating individuals and equipment, airline reservation system, communication system
US6353413B1 (en) * 1997-08-29 2002-03-05 Stanley A. White Multi-function universal controller and locator systems
US6037879A (en) * 1997-10-02 2000-03-14 Micron Technology, Inc. Wireless identification device, RFID device, and method of manufacturing wireless identification device
JP2001526417A (ja) * 1997-11-03 2001-12-18 ヒル−ロム，インコーポレイティド 人員および資産追跡方法並びに装置
US6204765B1 (en) * 1997-12-23 2001-03-20 Inkrmec Ip Corp. Method of detecting relative direction of motion of a radio frequency (RF) tag
US6091332A (en) * 1998-06-09 2000-07-18 Motorola, Inc. Radio frequency identification tag having printed circuit interconnections
US6177861B1 (en) * 1998-07-17 2001-01-23 Lucent Technologies, Inc System for short range wireless data communication to inexpensive endpoints
AU5916799A (en) * 1998-09-11 2000-04-03 Key-Trak, Inc. Object tracking system with non-contact object detection and identification
US6133832A (en) * 1998-10-22 2000-10-17 Winder; Jeffrey S. Article location system
US6252512B1 (en) * 1999-03-05 2001-06-26 Hill-Rom, Inc. Monitoring system and method
US7196659B1 (en) * 1999-05-07 2007-03-27 Garmin Corporation Combined global positioning system receiver and radio
US6211781B1 (en) * 1999-05-24 2001-04-03 United States Postal Service Method and apparatus for tracking and locating a moveable article
US6539393B1 (en) * 1999-09-30 2003-03-25 Hill-Rom Services, Inc. Portable locator system
AU2001259828A1 (en) * 2000-05-05 2001-11-20 Hill-Rom Services, Inc. Remote control for a hospital bed
US6662137B2 (en) * 2000-12-19 2003-12-09 Hewlett-Packard Development Company, L.P. Device location discovery by sound
US6732934B2 (en) * 2001-01-12 2004-05-11 Symbol Technologies, Inc. Escorted shopper system
US6816075B2 (en) * 2001-02-21 2004-11-09 3M Innovative Properties Company Evidence and property tracking for law enforcement
US7000116B2 (en) * 2001-03-12 2006-02-14 International Business Machines Corporation Password value based on geographic location
US6901255B2 (en) * 2001-09-05 2005-05-31 Vocera Communications Inc. Voice-controlled wireless communications system and method
US7034691B1 (en) * 2002-01-25 2006-04-25 Solvetech Corporation Adaptive communication methods and systems for facilitating the gathering, distribution and delivery of information related to medical care
GB0211644D0 (en) * 2002-05-21 2002-07-03 Wesby Philip B System and method for remote asset management
US8611919B2 (en) * 2002-05-23 2013-12-17 Wounder Gmbh., Llc System, method, and computer program product for providing location based services and mobile e-commerce
US6768450B1 (en) * 2002-11-07 2004-07-27 Garmin Ltd. System and method for wirelessly linking a GPS device and a portable electronic device
US8090402B1 (en) * 2003-09-26 2012-01-03 Iwao Fujisaki Communication device
US7881862B2 (en) * 2005-03-28 2011-02-01 Sap Ag Incident command post

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5515426A (en) * 1994-02-28 1996-05-07 Executone Information Systems, Inc. Telephone communication system having a locator
WO1998048394A1 (fr) * 1997-04-22 1998-10-29 Koninklijke Philips Electronics N.V. Dispositif de commande a distance
US6281811B1 (en) * 1999-06-11 2001-08-28 Anthony S Ranzino Communication and location system for shopping malls, parks, business districts, and the like
US6456239B1 (en) * 1999-08-25 2002-09-24 Rf Technologies, Inc. Method and apparatus for locating mobile tags
US20020126035A1 (en) * 2001-03-12 2002-09-12 Shaw-Yuan Hou Voice-activated remote control unit for multiple electrical apparatuses
US20030022696A1 (en) * 2001-07-24 2003-01-30 S. Jeffrey Rosner Wireless communications system fully integrated with the infrastructure of an organization
US20030073434A1 (en) * 2001-09-05 2003-04-17 Shostak Robert E. Voice-controlled wireless communications system and method

Cited By (47)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1954186A1 (fr) * 2005-11-23 2008-08-13 Koninklijke Philips Electronics N.V. Moniteur de parametres multiples porte au poignet presentant une meilleure fonctionnalite et une plus grande precision
US11170324B2 (en) * 2006-04-10 2021-11-09 Tagnos, Inc. Intelligent routing of patients using distributed input devices
US20090051546A1 (en) * 2006-04-10 2009-02-26 Neeraj Bhavani Intelligent Routing Of Patients Using Distributed Input Devices
US11862330B2 (en) 2006-04-10 2024-01-02 Tagnos, Inc. Proximity based systems for contact tracing
US9996842B2 (en) 2007-05-18 2018-06-12 3M Innovative Properties Company Method for tracking procedures performed on personal protection equipment and actions of individuals
US9972017B2 (en) 2007-05-18 2018-05-15 3M Innovative Properties Company Method for tracking procedures performed on personal protection equipment and actions of individuals
US9665999B2 (en) 2007-05-18 2017-05-30 3M Innovative Properties Company Method for tracking procedures performed on personal protection equipment and actions of individuals
US9721407B2 (en) 2007-05-18 2017-08-01 3M Innovative Properties Company Method for tracking procedures performed on personal protection equipment and actions of individuals
US9799038B2 (en) 2007-05-18 2017-10-24 3M Innovative Properties Company Method for tracking procedures performed on personal protection equipment and actions of individuals
US9798992B2 (en) 2007-05-18 2017-10-24 3M Innovative Properties Company Method for tracking procedures performed on personal protection equipment and actions of individuals
US11416873B2 (en) 2007-05-18 2022-08-16 3M Innovative Properties Company Personal protection equipment system
US10445747B2 (en) 2007-05-18 2019-10-15 3M Innovative Properties Company Personal protection equipment system
US9978032B2 (en) 2007-05-18 2018-05-22 3M Innovative Properties Company Method for tracking procedures performed on personal protection equipment and actions of individuals
US9996841B2 (en) 2007-05-18 2018-06-12 3M Innovative Properties Company Method for tracking procedures performed on personal protection equipment and actions of individuals
US10803467B2 (en) 2007-05-18 2020-10-13 3M Innovative Properties Company Personal protection equipment system
US9996812B2 (en) 2007-05-18 2018-06-12 3M Innovative Properties Company Method for tracking procedures performed on personal protection equipment and actions of individuals
US10223700B2 (en) 2007-05-18 2019-03-05 3M Innovative Properties Company Personal protection equipment system
US9564951B2 (en) 2007-05-18 2017-02-07 3M Innovative Properties Company Method for tracking procedures performed on personal protection equipment and actions of individuals
US8760260B2 (en) 2007-05-18 2014-06-24 3M Innovative Properties Company Method for tracking cyclical procedures performed on personal protection equipment
US10349686B2 (en) 2007-08-31 2019-07-16 3M Innovative Properties Company Determining conditions of personal protection articles against at least one criterion
US9492690B2 (en) 2007-08-31 2016-11-15 3M Innovative Properties Company Determining conditions of components removably coupled to personal protection equipment
US11612195B2 (en) 2007-08-31 2023-03-28 3M Innovative Properties Company Personal protection article system
US10387696B2 (en) 2007-08-31 2019-08-20 3M Innovative Properties Company Determining conditions of components removably coupled to personal protection equipment
US10729186B2 (en) 2007-08-31 2020-08-04 3M Innovative Properties Company Personal protection article system
US9536209B2 (en) 2007-08-31 2017-01-03 3M Innovative Properties Company Tracking compliance of personal protection articles
US10817683B2 (en) 2007-08-31 2020-10-27 3M Innovative Properties Company Determining conditions of components removably coupled to personal protection equipment
US9901125B2 (en) 2007-08-31 2018-02-27 3M Innovative Properties Company Determining conditions of personal protection articles against at least one criterion
US11354523B2 (en) 2007-08-31 2022-06-07 3M Innovative Properties Company Determining conditions of components removably coupled to personal protection equipment
US11278064B2 (en) 2007-08-31 2022-03-22 3M Innovative Properties Company Personal protection article system
US10639502B2 (en) 2010-10-12 2020-05-05 Smith & Nephew, Inc. Medical device
US11565134B2 (en) 2010-10-12 2023-01-31 Smith & Nephew, Inc. Medical device
US10610624B2 (en) 2013-03-14 2020-04-07 Smith & Nephew, Inc. Reduced pressure therapy blockage detection
US11633533B2 (en) 2013-03-14 2023-04-25 Smith & Nephew, Inc. Control architecture for reduced pressure wound therapy apparatus
US10905806B2 (en) 2013-03-14 2021-02-02 Smith & Nephew, Inc. Reduced pressure wound therapy control and data communication
US11783943B2 (en) 2015-10-07 2023-10-10 Smith & Nephew, Inc. Reduced pressure therapy device operation and authorization monitoring
US11315681B2 (en) 2015-10-07 2022-04-26 Smith & Nephew, Inc. Reduced pressure therapy device operation and authorization monitoring
US11602461B2 (en) 2016-05-13 2023-03-14 Smith & Nephew, Inc. Automatic wound coupling detection in negative pressure wound therapy systems
US11369730B2 (en) 2016-09-29 2022-06-28 Smith & Nephew, Inc. Construction and protection of components in negative pressure wound therapy systems
US11712508B2 (en) 2017-07-10 2023-08-01 Smith & Nephew, Inc. Systems and methods for directly interacting with communications module of wound therapy apparatus
US11049611B1 (en) * 2018-06-13 2021-06-29 Ortelligence, Inc. Systems, methods and devices for dynamic procedure management
US11189377B2 (en) * 2018-06-13 2021-11-30 ORtelligence LLC Systems, methods and devices for dynamic procedure management
US11657914B2 (en) 2018-06-13 2023-05-23 Ortelligence, Inc. Systems, methods and devices for dynamic procedure management
US20210287788A1 (en) * 2018-06-13 2021-09-16 Ortelligence, Inc. Systems, methods and devices for dynamic procedure management
CN110931089A (zh) * 2018-08-30 2020-03-27 希尔-罗姆服务公司 用于emr生命体征记录的系统和方法
US11793924B2 (en) 2018-12-19 2023-10-24 T.J.Smith And Nephew, Limited Systems and methods for delivering prescribed wound therapy
US11704993B2 (en) 2019-10-23 2023-07-18 Gojo Industries, Inc. Methods and systems for improved accuracy in hand-hygiene compliance
US11348443B2 (en) 2019-10-23 2022-05-31 Gojo Industries, Inc. Methods and systems for improved accuracy in hand-hygiene compliance

Also Published As

Publication number Publication date
US20070080801A1 (en) 2007-04-12

Similar Documents

Publication Publication Date Title
US20070080801A1 (en) Universal communications, monitoring, tracking, and control system for a healthcare facility
US7734476B2 (en) Universal communications, monitoring, tracking, and control system for a healthcare facility
US11024142B2 (en) Event detector for issuing a notification responsive to occurrence of an event
US9104927B2 (en) Using a RFID paging infrastructure
CN1638313B (zh) 具有语音通信能力的警报通知系统和设备
US20200074840A1 (en) Monitoring activity of an individual
US20220304577A1 (en) Method and system to reduce infrastructure costs with simplified indoor location and reliable commumications
US7301451B2 (en) Notification alarm transfer methods, system, and device
US7907053B2 (en) Combined locating, tracking and communications system
US7589637B2 (en) Monitoring activity of an individual
US20130150686A1 (en) Human Care Sentry System
US20060089539A1 (en) Integrated messages from multiple patient care devices
US20050146431A1 (en) Alarm notification system, receiver, and methods for providing live data
US20100001838A1 (en) Automated Association of Patient Care Devices
US20050148890A1 (en) Alarm notification system and receiver incorporating multiple functions
US20110050411A1 (en) Integrated healthcare communication and locating system
US7348883B2 (en) Medical communication and locator system and method
US20140056417A1 (en) Method, system and device for voice message recording and playback at point of care
US8115633B2 (en) Tracking system
CA2157405C (fr) Systeme de communication pour le soin des malades
US20150199481A1 (en) Monitoring system and method
JP2002312471A (ja) Ｉｄマウスペンダント方式による病院内リスクマネジメントシステム
Ali et al. Developing a Fall-Prevention System for Nursing Homes
Solvoll Mobile communication in hospitals: Problems, possibilities, and solutions
JP3352624B2 (ja) 非常通報システム

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 69(1) EPC

WWE Wipo information: entry into national phase

Ref document number: 2007080801

Country of ref document: US

Ref document number: 10575801

Country of ref document: US

122 Ep: pct application non-entry in european phase
WWP Wipo information: published in national office

Ref document number: 10575801

Country of ref document: US