WO2016099551A1 - Association basée sur l'emplacement d'un dispositif médical à un patient - Google Patents

Association basée sur l'emplacement d'un dispositif médical à un patient Download PDF

Info

Publication number
WO2016099551A1
WO2016099551A1 PCT/US2014/071529 US2014071529W WO2016099551A1 WO 2016099551 A1 WO2016099551 A1 WO 2016099551A1 US 2014071529 W US2014071529 W US 2014071529W WO 2016099551 A1 WO2016099551 A1 WO 2016099551A1
Authority
WO
WIPO (PCT)
Prior art keywords
medical device
patient
medical devices
proximity
medical
Prior art date
Application number
PCT/US2014/071529
Other languages
English (en)
Inventor
Michael D. Hirst
Joshua E. ABELL
Geoffrey Waite
Original Assignee
Draeger Medical Systems, 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 Draeger Medical Systems, Inc. filed Critical Draeger Medical Systems, Inc.
Priority to PCT/US2014/071529 priority Critical patent/WO2016099551A1/fr
Publication of WO2016099551A1 publication Critical patent/WO2016099551A1/fr

Links

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms

Definitions

  • the subject matter described herein relates to detection of electronic devices, in particular, the detection of medical devices in a proximity to a patient.
  • medical devices used in patient treatment, are often assigned to a single patient, in accordance with a treatment plan.
  • medical devices are moved from patient to patient as needed by physicians, or as patients enter or leave the facility or treatment area.
  • the association of medical devices with patients can be done by charts, tags, databases, etc.
  • the association of medical devices with patients can be referred to by physicians to prepare for operations, determine conflicts with other medical devices that may be needed, familiarize the physician with the current state of patient care, and the like.
  • the association of medical devices can be done at the device level, e.g. admitting a patient using a patient ID on the device, or can be done centrally in an information technology system, e.g. assigning a device at a certain location to the patient.
  • medical devices within a proximity to a patient are discovered.
  • the discovered devices are displayed within a graphical user interface of a computing device.
  • Data that is derived from response to user-generated input, via the graphical user interface, is received that selects one or more of the medical devices.
  • the selected medical devices are queried to determine whether the selected medical devices should be associated with the patient.
  • an association confirmation is received from a selected medical device.
  • the medical device that received association confirmation is then associated with the patient.
  • the discovering of the medical devices includes wirelessly transmitting a signal from the medical device to a base location.
  • the distance from the medical device to the base location can be determined based on the strength of the signal.
  • An inventory of medical devices with in the proximity can be compiled and stored in a database. Also, the medical device can be excluded from the inventory based on the medical device being outside the proximity.
  • a first signal can be transmitted from the base location to a distance that defines the proximity.
  • Second signals from the medical devices within the proximity can be received.
  • An inventory of the medical devices within the proximity can be compiled from the received second signals. The inventory can be stored in a database.
  • the proximity can correspond to a physical boundary of a patient treatment room and the medical device can be associated with an out-of-bounds status upon discovering the medical device to be outside the proximity.
  • the medical device can be confirmed by a user that the medical device is not being used by another patient when the device is within a predefined distance of an edge of the proximity and when the medical device includes a parameter indicating that medical device is a non-fixed device. If the medical device is being used by another patient, the medical device can be removed from the displayed medical devices.
  • the medical device have memory storing parameters including type, serial number, version, room identifier, other location identifier, and fixed or non-fixed status.
  • each discovered medical device can be compared to associated medical devices and when any of the medical devices are already associated with another message a conflict message can be transmitted.
  • the proximity is verified by transmitting a proximity verification signal that initiates a visual indication of all medical devices within the proximity. Also, the association can be removed upon the medical device being discovered outside the proximity.
  • the confirmation can be provided by a user engaging an actuator connected to the selected medical device.
  • the associating is executed by a first computing device and the discovered medical devices can be displayed within a second graphical user interface of a second computing device.
  • the medical devices can be discovered by wireless communication, which can be unidirectional. Association between the medical device and the patient can be established based in part on receiving, by the medical device, the wireless communication, or by analyzing the signal strength of the wireless communication received by the medical device.
  • the current subject matter provides many technical advantages. For example, the accurate location, type, state, etc. of medical devices proximate to a patient can be determined. Confirmation of the detected medical devices to be associated with the patient can easily be performed, reducing the risk of conflicting or unnecessary medical devices being connected to a patient. Also, accurate association between medical devices and patients prevents the inadvertent mixing of patient data or the loss of patient data. Additionally, unnecessary medical devices can easily be identified and removed from the patient.
  • FIG. 1 is a diagram illustrating a patient with a proximity that includes a number of medical devices
  • FIG. 2 is a diagram illustrating medical devices associated or unassociated with the patient
  • FIG. 3 is a process flow diagram illustrating associating medical devices with the patient
  • FIG. 4 is a process flow diagram illustrating compiling an inventory of associated medical devices
  • FIG. 5 is a process flow diagram illustrating setting an out-of-bounds status in the medical device
  • FIG. 6 is a process flow diagram illustrating confirming that mobile medical devices are not associated with another patient.
  • FIG. 7 is a process flow diagram illustrating transmission of a conflict message if the medical devices are associated with another patient.
  • the current subject matter is directed to methods, systems, apparatus, articles / computer program products for identifying medical devices connected to a patient.
  • the term "patient” can refer to any biological entity, e.g. persons or animals, and is not intended to be limiting in any way to persons under medical care or in a medical treatment facility.
  • the term “medical device” can refer to any device related to the treatment and wellness of a patient, irrespective of the function of the device, and is not intended to be limiting in any way to particular types of medical devices, unless otherwise specified.
  • FIG. 1 is a diagram illustrating a patient 1 10 with a proximity 120 that includes a number of medical devices 130.
  • the current subject matter describes locating and associating medical devices 130, 140, 150 within the proximity to the patient 1 10.
  • the proximity 120 To first locate the medical devices 130, the proximity 120 must be determined.
  • the proximity 120 can be a predetermined range of a transmitting device (not shown), a predetermined radius from the patient 1 10, or the proximity 120 defined at least in part by physical constraints, i.e. walls, ceilings, floors, etc. that correspond to a physical boundary of a patient treatment room.
  • some of the medical devices 130, 140, 150 can be within the proximity 120, whereas other medical devices 160, 170 are not.
  • the discovering of medical devices 130 within the proximity 120 can be based upon wirelessly transmitting a signal from the medical device 130 to a base location, which can correspond to the location of the patient
  • Positional information can be determined by using the strength of the signal, triangulation, or both.
  • the medical device can be included or excluded as a candidate for association with the patient. For example, if the distance exceeds a predetermined boundary, e.g. the proximity 120, then that information can be used in making a decision in whether or not to associate the medical device 130 with the patient 1 10.
  • a predetermined boundary e.g. the proximity 120
  • each of the medical devices 130 can have varying degrees of association with the patient 1 10.
  • Association with the patient 1 10 can be used to associate physiological data that is generated by a medical device with the patient 1 10. This physiological data from multiple medical devices that are associated with the patient 1 10 can be stored by a server or another medical device in a unified record for the patient 1 10, either as separate distinct data sets or combined into a single data set.
  • the medical device 130 being in the proximity 120 of the patient 1 10 is not sufficient to associate the medical device 130 with the patient 1 10.
  • the caregiver can also be required to provide confirmation that the medical device 130 is to be associated with the patient 1 10.
  • the confirmation can take the form of user-generated input to the computing device, GUI, etc.
  • the confirmation can be provided via engagement, by the caregiver or other user, of an actuator operably connected to the selected medical device.
  • the actuator can be, e.g. a button, switch, knob, etc.
  • the medical device 130 can be confirmed to be associated with the patient 110, whereas the medical device 140 can be connected to the patient 110, but not yet confirmed to be associated with the patient 110.
  • the medical device 150 can be within the proximity 120; however it does not have to be associated with the patient 110. [0030] Not all medical devices that can be discovered are necessarily within the proximity 120.
  • the medical devices 160 and 170 can be either outside of the proximity, and therefore not associated with the patient 1 10, or they can be associated with another patient.
  • the association with the patient 1 10 in the proximity can be removed, or recommended to be removed, upon the medical device being discovered outside the proximity 120, i.e. the medical device is removed from the area.
  • the process by which the proximity 120 to the patient 1 10 is determined and the association of the medical devices with the patient 1 10 is made is described in greater detail, below.
  • FIG. 2 is a diagram illustrating medical devices associated or unassociated with the patient 1 10.
  • FIG. 2 is similar to FIG. 1 , but showing more detail about the patient environment and the medical devices that are found within the patient environment.
  • the proximity corresponding to patient A 1 10 approximately corresponds to the care area for patient A 210.
  • a workstation 230 can be used, among other things, to monitor the medical devices within the proximity to the patient 1 10.
  • the workstation 230 can be, e.g. a computer terminal, a dedicated display having a graphical user interface (GUI), etc.
  • the workstation 230 and each medical device can have a transceiver that enables wireless transmission of signals to and/or from the medical devices in the proximity.
  • the transceivers can be, e.g. radio- frequency identifiers, BLUETOOTH enabled, electronic leashes, etc.
  • some of the medical devices can already be connected to a network via wireless connection, physical connection, e.g. ETHERNET, local-area-network, etc.
  • the network connection can alternatively be used to determine if the medical device is within the proximity to the patient 1 10, for example, if the medical device is plugged into a port in the care area for patient A 210, then that medical device can be a candidate for being associated with patient A 1 10.
  • the wireless communication can be unidirectional, that is that the medical devices include only a wireless receiver and not a wireless transmitter.
  • One example of the unidirectional wireless communication implementation can be a medical device 130 that receives a wireless signal, e.g. strength- limited in range or stopped by the physical boundaries of the patient treatment room, e.g. the care area for patient A 210.
  • the medical device 130 can be determined or inferred that the medical device 130 is a candidate for association with the patient Al 10.
  • an indicator on the medical device 130 e.g. visual as in an LED, audio as in a beeping speaker, etc. to indicate the presence of the medical device 130.
  • the medical devices 130 can be connected to a central computer system via a wired network (not shown). The medical device 130 can then transmit an indication of the receipt of the unidirectional wireless signal via wired signal through the network.
  • FIG. 3 is a process flow diagram 300 illustrating associating medical devices with the patient 1 10.
  • each of the medical devices within the proximity of a patient 1 10 can be discovered.
  • the discovering can be performed by sending a wireless transmission from, e.g. the workstation 230, a transmitter located at the patient 1 10 location, etc. to e.g. the medical devices, the transceivers, or identifying the medical devices by their physical or virtual access points to a network, etc.
  • the medical devices can then return a signal indicating that they are candidates for association with the patient 1 10.
  • the proximity can be determined and/or verified, by transmitting a proximity verification signal that initiates a visual indication of all medical devices within the proximity.
  • the medical devices can have a light-emitting diode (LED) that illuminates upon the medical devices receiving the proximity verification signal.
  • LED light-emitting diode
  • the discovered medical devices can be displayed on a GUI of a computing device.
  • the computing device can be, e.g. the workstation 230, a display located on the medical device, or a mobile device such as a smartphone, tablet computer, etc.
  • the computing device can receive data in response to user- generated input, via the graphical user interface, selecting one or more of the medical devices.
  • the data can be data that specifies selections or exclusions of medical devices for association with the patient 1 10.
  • the user-generated input can be, e.g. a touch on a touch-screen display, a mouse click, checking a checkbox, etc.
  • the selecting can be used to perform, in turn, confirmation in associating each candidate medical device with the patient 1 10.
  • the caregiver could receive a list of medical devices 130, 140, and 150 and examine the medical devices one at a time to confirm or deny their association with patient A 1 10.
  • each of the selected medical devices can be queried to determine whether each such medical device should be associated with the patient 1 10.
  • the querying can take the form of, e.g. determining already extant associations, providing information about the medical device to the caregiver, etc. Also, the querying can include displaying the results of the querying to the caregiver to aid in making a determination whether to confirm the association between the medical device and the patient 1 10.
  • the computing device can receive, in response to the querying, an association confirmation from at least one of the selected medical devices.
  • the confirmation can be an affirmative action taken by the caregiver to confirm that the candidate medical device, discovered in 310, is to be associated with the patient 1 10.
  • each selected medical device can be associated with the patient 1 10.
  • the association as described in FIG. 1 , can include storing the record of the association in the memory of the computing device, the medical device, and/or a server. Once associated, the medical device will be displayed as associated if discovered by another workstation 230 or computing device.
  • the displaying of the locations and/or associations of medical devices, or utility programs managing the detection/association of the medical devices can be implemented by graphical user interfaces on one or more devices.
  • graphical user interfaces on one or more devices.
  • 310, 330, 340, 350, and 360 are executed on a first computing device, e.g. the workstation 230, which can have a first GUI (not shown).
  • a second computing device, perhaps used by a caregiver, e.g. a mobile device, tablet, smartphone, etc. can have a second GUI (not shown), that can execute the displaying at 320 of the discovered medical devices.
  • FIG. 4 is a process flow diagram 400 illustrating compiling an inventory of associated medical devices.
  • the discovering in 310 can include additional features.
  • a first signal can be transmitted from a base location to a distance that defines the proximity, e.g. where the first signal is limited by walls, floors, etc. of a patient care area.
  • the base location can be the workstation 230, a transmitter at the patient 1 10 location, etc.
  • the distance that defines the proximity can be, e.g. predefined as described above, determined after the receiving of signals based on calculated distances, etc.
  • a second signal can be received from the medical devices within the proximity.
  • the first signal and the second signal can be separated by frequency, phase, or amplitude in order to distinguish the signals.
  • each medical device can have unique second signals to distinguish them from each other.
  • an inventory of the medical devices can be compiled based on the received second signals.
  • the inventory can include devices that are unassociated, associated, or unassociated but awaiting confirmation. Depending on the medical devices being within or outside of the proximity, the medical devices can be included or excluded from the inventory.
  • the inventory can be stored in a database or other computer memory.
  • the inventory can be present in e.g. the workstation 230, a mobile device, a server, the memory of the medical device, etc.
  • the inventory can periodically, or on- demand, be refreshed by a user or by the computer program executing the associating program. Older versions of the inventory can also be stored in the database to provide a record of changes in associations of the medical devices.
  • FIG. 5 is a process flow diagram 500 illustrating setting an out-of- bounds status in the medical device.
  • FIG. 5 is similar to FIG. 3, but includes the feature of designating the medical device as being out-of-bounds if detected, but determined to be outside the proximity.
  • the caregiver can be alerted to the fact that there is a medical device which is associated with the patient 1 10, but outside the proximity. Such status identification can be helpful in tracking down devices that have been misplaced from the designated patient 1 10.
  • FIG. 6 is a process flow diagram 600 illustrating confirming that non- fixed medical devices are not associated with another patient 1 10. In one
  • parameters i.e. an information tag
  • the medical devices can have computer memory that stores parameter including: type, serial number, version number, version, room identifier, other location identifiers, fixed or non-fixed status, etc.
  • the information tag can be, e.g. IBEACON, RFID, etc. Accordingly, the reader for the information tag can be integrated into the workstation 230 or any other computing device, e.g. laptop computer, tablet computer, mobile device, etc.
  • the device can be confirmed by a user that when the device is within a predefined distance of an edge of the proximity, and when the medical device includes a parameter indicating that the medical device is a non-fixed device, that the medical device is not being used by another patient 1 10.
  • the confirmation can take the form of e.g. manually verifying, referencing a database, etc.
  • the medical devices can be removed from the displayed medical devices if the medical devices are being used by another patient 1 10. Also, this can include overriding the association in the event that the medical device has an associated patient already, but in reality the patient is no longer connected to the medical device.
  • the removing can include, e.g. removing the already associated medical devices from a list or table, unchecking them from a checklist, etc.
  • FIG. 7 is a process flow diagram 700 illustrating transmission of a conflict message if the medical devices are associated with another patient 1 10
  • FIG. 7 is similar to FIG. 3, but includes features describing providing a conflict message to the caregiver to aid in determining if the medical device should be associated with the patient 1 10.
  • the discovered medical devices can be compared to the list of associated medical devices.
  • the conflict message can be transmitted to the computing device, medical device, or other device, indicating that the discovered medical device is already associated with another patient 1 10. After the conflict message is transmitted, it can be determined either manually or automatically, whether or not to remove the medical device from the list of discovered medical devices.
  • ASICs application specific integrated circuits
  • computer hardware firmware, software, and/or combinations thereof.
  • a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device (e.g., mouse, touch screen, etc.), and at least one output device.
  • a programmable processor which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device (e.g., mouse, touch screen, etc.), and at least one output device.
  • These computer programs which can also be referred to as programs, software, software applications, applications, components, or code, include machine instructions for a programmable processor, and can be implemented in a high-level procedural language, an object-oriented programming language, a functional
  • machine -readable medium refers to physically embodied apparatus and/or device, such as for example magnetic discs, optical disks, memory, and Programmable Logic Devices (PLDs), used to provide machine instructions and/or data to a programmable data processor, including a machine -readable medium that receives machine instructions as a machine-readable signal.
  • machine-readable signal refers to any signal used to provide machine instructions and/or data to a programmable data processor.
  • the machine-readable medium can store such machine instructions non-transitorily, such as for example as would a non-transient solid state memory or a magnetic hard drive or any equivalent storage medium.
  • the machine -readable medium can alternatively or additionally store such machine instructions in a transient manner, such as for example as would a processor cache or other random access memory associated with one or more physical processor cores.
  • the subject matter described herein can be implemented on a computer having a display device, such as for example a cathode ray tube (CRT) or a liquid crystal display (LCD) monitor for displaying information to the user and a keyboard and a pointing device, such as for example a mouse or a trackball, by which the user may provide input to the computer.
  • a display device such as for example a cathode ray tube (CRT) or a liquid crystal display (LCD) monitor for displaying information to the user and a keyboard and a pointing device, such as for example a mouse or a trackball, by which the user may provide input to the computer.
  • CTR cathode ray tube
  • LCD liquid crystal display
  • a keyboard and a pointing device such as for example a mouse or a trackball
  • Other kinds of devices can be used to provide for interaction with a user as well.
  • feedback provided to the user can be any form of sensory feedback, such as for example visual feedback, auditory feedback, or tactile feedback
  • touch screens or other touch-sensitive devices such as single or multi-point resistive or capacitive trackpads, voice recognition hardware and software, optical scanners, optical pointers, digital image capture devices and associated interpretation software, and the like.
  • the subject matter described herein may be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front- end component (e.g., a client computer having a graphical user interface or a Web browser through which a user may interact with an implementation of the subject matter described herein), or any combination of such back-end, middleware, or front-end components.
  • the components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN”), a wide area network (“WAN”), and the Internet.
  • LAN local area network
  • WAN wide area network
  • the Internet the global information network
  • the computing system may include clients and servers.
  • a client and server are generally remote from each other and typically interact through a communication network.
  • the relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

Landscapes

  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Biomedical Technology (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Measuring And Recording Apparatus For Diagnosis (AREA)

Abstract

La présente invention concerne des dispositifs médicaux à proximité d'un patient. Les dispositifs découverts sont affichés dans une interface utilisateur graphique d'un dispositif informatique. Des données qui sont dérivées à partir de réponse à une entrée générée par un utilisateur, par l'intermédiaire de l'interface utilisateur graphique, est reçu, lequel sélectionne au moins un de ces dispositifs médicaux. Les dispositifs médicaux sélectionnés sont interrogés pour déterminer si les dispositifs médicaux sélectionnés doivent être associés au patient. En réponse à l'interrogation, une confirmation d'association est reçue en provenance d'un dispositif médical sélectionné. Le dispositif médical qui a reçu la confirmation d'association est ensuite associé au patient.
PCT/US2014/071529 2014-12-19 2014-12-19 Association basée sur l'emplacement d'un dispositif médical à un patient WO2016099551A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2014/071529 WO2016099551A1 (fr) 2014-12-19 2014-12-19 Association basée sur l'emplacement d'un dispositif médical à un patient

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2014/071529 WO2016099551A1 (fr) 2014-12-19 2014-12-19 Association basée sur l'emplacement d'un dispositif médical à un patient

Publications (1)

Publication Number Publication Date
WO2016099551A1 true WO2016099551A1 (fr) 2016-06-23

Family

ID=52278857

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2014/071529 WO2016099551A1 (fr) 2014-12-19 2014-12-19 Association basée sur l'emplacement d'un dispositif médical à un patient

Country Status (1)

Country Link
WO (1) WO2016099551A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060066450A1 (en) * 2004-09-15 2006-03-30 Radarfind Corporation Methods, location circuits and computer program products for automated location and monitoring of mobile devices
US20090115663A1 (en) * 2007-11-01 2009-05-07 Cardinal Health 303, Inc. System and method for determining locations of medical devices
US20090157695A1 (en) * 2007-08-10 2009-06-18 Smiths Medical Md Central Server for Medical Devices
US20110202371A1 (en) * 2008-09-12 2011-08-18 Capsule Technologie Device, system and method for providing contextualized medical data

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060066450A1 (en) * 2004-09-15 2006-03-30 Radarfind Corporation Methods, location circuits and computer program products for automated location and monitoring of mobile devices
US20090157695A1 (en) * 2007-08-10 2009-06-18 Smiths Medical Md Central Server for Medical Devices
US20090115663A1 (en) * 2007-11-01 2009-05-07 Cardinal Health 303, Inc. System and method for determining locations of medical devices
US20110202371A1 (en) * 2008-09-12 2011-08-18 Capsule Technologie Device, system and method for providing contextualized medical data

Similar Documents

Publication Publication Date Title
US11328227B2 (en) System for dynamic location-aware patient care process controls and dynamic location-aware tracking
AU2018222989B2 (en) Mobile device access for medical devices
US7627334B2 (en) Systems and methods for context relevant information management and display
US20110276338A1 (en) Automated workflow engine in a delivery of healthcare
US11914656B1 (en) Systems and methods for generating hypermedia-based graphical user interfaces for mobile devices
RU2678636C1 (ru) Монитор пациента и способ наблюдения за состоянием пациента
US10162938B2 (en) Health management system using home network and operation method thereof
US20140281015A1 (en) Post-Scheduling Ad Hoc Sequencing Of File Transfers
US11393259B2 (en) Information output method, information output device, and program
EP3770915A1 (fr) Procédés et systèmes permettant d'améliorer la lutte contre des infections dans une installation
JP6453024B2 (ja) 備品管理装置、及び備品情報提供方法
US20130311516A1 (en) Systems and methods for providing enterprise visual communications services
US11120681B2 (en) Method and system for monitoring hand hygiene compliance
WO2016099551A1 (fr) Association basée sur l'emplacement d'un dispositif médical à un patient
US20210313076A1 (en) Medical device information tracking, alert and integration system
JP5827447B1 (ja) 情報処理装置、情報処理方法及びプログラム
AU2021235734A1 (en) System, device, product, apparatus, and method for reading syringe information
JP2017148163A (ja) 患者識別端末、患者識別方法、および患者識別プログラム
CN113646609A (zh) 一种院内设备查找的路径规划方法
WO2010050536A1 (fr) Lecteur d'étiquette, procédé de commande de lecteur d'étiquette et programme de commande de lecteur d'étiquette
WO2018213046A1 (fr) Système et procédé de fourniture d'informations dynamiques basées sur l'emplacement
EP3123438A1 (fr) Système destiné à des contrôles de processus de soins d'un patient sensible à un emplacement dynamique et suivi d'actif sensible à un emplacement dynamique
KR101941095B1 (ko) 의약품 재고 관리 시스템 및 방법
Shi Context Awareness via a Smartphone Based Active RFID Proximity Detection System

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14822041

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14822041

Country of ref document: EP

Kind code of ref document: A1