ES2831803T3 - Context-Sensitive Healthcare Notification System - Google Patents

Abstract

A method of providing context-associated information to a user device (140) associated with a healthcare professional, the method comprising: an infusion device, detecting a wireless signal transmitted from the user device (140) characterized by; determining, by the infusion device and in response to detection, that the user device (140) is in the vicinity of the infusion device, wherein the infusion device is configured to deliver a drug to a patient; providing, by the infusion device, an indication to a system (110) that the user device (140) is in the vicinity of the infusion device; providing, to the control system (110) from the infusion device, an identifier for the patient; receiving, via the control system (110), a first information related to the patient and the infusion device from a healthcare system (120); receiving, by means of the control system (110) from the infusion device, a second information related to the progress of the administration of the medication to the patient; determining, by the control system (110), whether the first information or the second information indicates that corrective action is required; transmitting, from the control system (110) to the nearby user device (140), an alert, the alert indicating a course of action to take corrective action; displaying, by the user device (140), the alert when corrective action is required; and reprogramming, with the user device (140), the infusion device based on a characteristic of the alert.

Description

DESCRIPTION

Context-Sensitive Healthcare Notification System

Cross reference to related requests

Technical field

The present description refers generally to a notification system, and more particularly, but not exclusively, to a context-sensitive health care notification system.

Background

Healthcare facilities, such as hospitals, may use many different user devices, healthcare devices, and / or healthcare systems to facilitate the delivery of healthcare to patients. For example, a healthcare facility may use healthcare systems to facilitate the delivery of healthcare to patients, such as through physician order entry systems, pharmacy information systems, hospital information systems, and so on. The healthcare facility may also use healthcare devices to facilitate the provision of healthcare to patients, such as infusion devices, dispensing devices, respiratory devices, etc. In addition, the healthcare facility may use user devices to facilitate the delivery of medical care to patients, such as computer stations located throughout the healthcare facility, personal digital assistants (PDAs) carried by healthcare professionals, etc.

However, the healthcare facility may not be able to provide relevant information from healthcare systems and healthcare devices to user devices in a timely manner.

US 2006/122481 A1, which is considered the closest prior art, discloses a system and method for locating and repairing a healthcare device. A portable computing system transmits a wireless signal to physically locate and identify the medical device that is disposed near the portable computing system. Additionally, the medical device can be wirelessly coupled to the portable computer system. The device can be serviced by a field engineer and / or a remote service center via the portable computer system and wireless connection.

Document US 2012/191052 A1 discloses a system, method and apparatus for real-time measurement and monitoring of various personal health parameters, including controlled drug / medication administration by smart pumping devices, smart inhalation devices and devices. of smart skin patches used on its own or in a wired or wireless network setup, along with various peripheral devices, other smart gadgets, servers, RF ID tags, and fixed / mobile devices.

WO 2012/095829 A2 discloses a medical device that includes a therapeutic component to provide one or more therapeutic functionalities during the therapeutic mode. The medical device may also enter a device sleep mode (DSM). A transceiver is configured to provide the medical device with wireless connectivity and can transition further to Transceiver Sleep Mode (TSM) substantially simultaneously with the transition to DSM,

Summary

The invention is defined by the independent claims. Advantageous embodiments of the invention are given in the dependent claims.

The disclosed subject relates to a user device to facilitate medical care. The user device can include a processor and memory. The memory may include instructions that, when executed by the processor, cause the processor to: determine when the user's device is close to at least one health care device, receive information pertaining to at least one health care device when the device is near the at least one health care device and displays at least some of the information received.

The disclosed subject also relates to a user device for facilitating medical care that includes a wireless interface, a receiver, a processor and a display. The wireless interface can be configured to determine when the user device is located near a patient. The receiver can be configured to receive patient-related information when the user's device is in close proximity to the patient. The processor can be configured to determine if the information indicates that corrective action is required. The The display can be configured to display at least a portion of the information when the information indicates that corrective action is required.

The disclosed subject also relates to a method for providing context sensitive information to a user device. The method includes determining, by a user device, that the user device is close to a patient or a healthcare device. The method further includes receiving, from the device, information related to the patient or health care device and determining, from the device, whether the information indicates that corrective action is required or a safety concern exists. The method further includes displaying, by the device, at least a portion of the information when the information indicates that corrective action is required or the security problem exists.

The theme revealed also refers to a system. The system includes one or more processors and a memory. The memory includes instructions that, when executed by one or more processors, cause the one or more processors to: determine when a user device is close to at least one healthcare device or at least one patient, receive the first related information with the at least one health care device or the at least one patient of a plurality of health care systems through a communication network, when it is determined that the user's device is close to the at least one health care device or of the at least one patient, and transmits, to the user device via the communication network, at least a part of the first information related to the at least one health care device or the at least one patient.

It is understood that other configurations of the subject technology will be readily apparent to those skilled in the art from the following detailed description, in which various configurations of the subject technology are shown and described by way of illustration. As will be seen, the subject technology is capable of other different configurations and its various details can be modified in various other respects, all without departing from the scope of the subject technology. Accordingly, the drawings and detailed description are to be construed as being illustrative and not restrictive in nature.

Brief description of the drawings

Certain characteristics of the subject technology are set forth in the appended claims. However, for purposes of explanation, various embodiments of the subject technology are set forth in the following figures.

Figure 1 illustrates an example network environment in which a context-sensitive health care notification system may be implemented in accordance with one or more embodiments.

Figure 2 illustrates an example messaging architecture in which a context-sensitive health care notification system may be implemented in accordance with one or more embodiments.

Figure 3 illustrates an alternative example messaging architecture in which a context sensitive health care notification system may be implemented in accordance with one or more embodiments.

Figure 4 illustrates a flow diagram of an example process for a context sensitive health care notification system in accordance with one or more embodiments.

Figure 5 illustrates a flow chart of an example process for a user device in a context sensitive health care notification system in accordance with one or more embodiments.

Figure 6 illustrates a flow chart of an example process for a user device in a context sensitive health care notification system in accordance with one or more embodiments.

Figure 7 illustrates an example user interface that may be implemented in a context-sensitive health care notification system in accordance with one or more embodiments.

Figure 8 illustrates an example user interface that may be implemented in a context-sensitive health care notification system in accordance with one or more embodiments.

Figure 9 illustrates an example user interface that may be implemented in a context-sensitive health care notification system in accordance with one or more embodiments.

Figure 10 illustrates an example user interface that may be implemented in a context-sensitive health care notification system in accordance with one or more embodiments.

Figure 11 conceptually illustrates an electronic system with which one or more realizations of the object technology.

Detailed description

The detailed description that follows is intended to be a description of various configurations of the subject technology and is not intended to represent the only configurations in which the subject technology can be practiced. The accompanying drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details in order to provide a thorough understanding of the subject technology. However, it will be clear and apparent to those skilled in the art that the subject technology is not limited to the specific details set forth herein and can be practiced using one or more embodiments. In one or more cases, well-known structures and components are shown in block diagram form to avoid obscuring the concepts of the subject technology.

FIG. 1 illustrates an example network environment 100 in which a context-sensitive health care notification system may be implemented in accordance with one or more embodiments. However, not all of the components depicted may be necessary and one or more embodiments may include additional components that are not shown in the figure. Fewer additional or different components may be provided.

Network environment 100 includes network 105, a control system 110, one or more healthcare systems 120A-D, one or more healthcare devices 130A-F, and one or more user devices 140A-C. Control system 110, healthcare systems 120A-D, healthcare devices 130A-F, and / or user devices 140A-C may be communicatively coupled to each other, for example via network 105. In one or more In further embodiments, one or more of the control system 110, healthcare systems 120A-D, healthcare devices 130A-F, or user devices 140A-C can be directly coupled to each other. In addition, there may be a number of other devices connected to the network 105, such as additional healthcare systems, for example, other clinical and / or logistics systems, additional healthcare devices, external systems, computing devices, mobile devices, etc. . The control system 110, one or more healthcare systems 120A-D, one or more healthcare devices 130A-F, and / or one or more user devices 140A-C may be, or may include all or part of the system. electronic which is discussed below with respect to Figure 11.

The network 105 may be a communication network, such as a public communication network (such as the Internet, cellular data network, dial-up modem through a telephone network), a private communication network (such as a telephone network). private local area ("LAN"), leased lines), etc. The network 105 may also include, but is not limited to, one or more of the following network topologies, including a bus network, a star network, a ring network, a mesh network, a star-bus network, a hierarchical tree or network and the like. Network 105 connections can be wired or wireless. For example, one or more of the control system 110, healthcare systems 120A-D, healthcare devices 130A-F, and / or user devices 140A-C can transmit wireless signals over network 105, such as radio frequency (RF) signals, infrared (IR) signals, Bluetooth signals or any other means capable of transporting information wirelessly between devices that have suitable transmitters and / or receivers.

Control system 110 may be a single computing device, such as a computing server. Alternatively, the control system 110 may represent one or more computing devices (such as a cloud of computers and / or a distributed system) that are communicatively coupled, such as communicatively coupled through network 105, and that collectively or individually , perform one or more functions that can be performed on the server side, such as receiving messages, transmitting messages, storing messages, receiving control commands, providing user interfaces, transmitting notifications, etc. The one or more computing devices of the control system 110 may be geographically located and / or the one or more computing devices of the control system 110 may be located differently. Control system 110 may be coupled with various databases, such as data warehouse 114, storage services, or other computing devices. Control system 110 and attached databases, storage services, or other computing devices may be geographically located or may be located differently. In one or more embodiments, the control system 110 includes a processing device 112 and a data store 114. Processing device 112 executes computer instructions stored in data store 114. In one or more embodiments, data store 114 can store computer instructions on a non-transient computer-readable medium.

The one or more healthcare systems 120A-D can be any system that facilitates the provision of medical care and / or the provision of medical care. In Figure 1, Healthcare System 120A is a Hospital Information System (HIS), Healthcare System 120B is a Physician Order Entry System (POE), Healthcare System 120C is an Information System Pharmaceutical (PIS) and Healthcare 120D System is a Laboratory Information System (LIS). The HIS can, for example, store information related to the administration of the healthcare facility, such as a hospital. E1HIS can provide and / or interact with a server that provides billing and accounting functions. The POE system can be used, for For example, by physicians to enter patient orders, such as orders to administer medications to patients, which are then transmitted to the PIS.

The PIS can store, for example, information pertaining to a pharmacy of a health center, such as pending orders, completed orders, profiles / medical records of patients, etc. For example, the PIS can provide a library of drug allergies and adverse drug interactions against which each incoming order or prescription is checked as part of the drug ordering / dispensing process to identify potential allergies and adverse drug interactions and help to prevent the administration of drugs to a patient in which the patient could be harmed by the prescribed course of therapy. In addition, the PIS can check to determine if any therapies are being duplicated, for example, such as when two or more drugs can be used to treat a diagnosed disease, if they are synergistic or antagonistic, and if the prescribed therapy should be modified accordingly. The LIS can store laboratory results, such as tests performed to facilitate the provision of medical care to patients.

Health care devices 130A-F may include infusion devices, such as infusion pumps, drug delivery devices, dispensing devices, such as automated dispensing machines, smart beds, monitoring devices, respiratory devices, such as ventilators, waste devices, such as drug disposal devices or, in general, any device that can facilitate the provision of medical care and / or can provide medical care. Health care devices 130A-F may include a processor and memory. Alternatively or additionally, healthcare devices 130A-F may be communicatively coupled to a device that includes a processor and memory, such as through a serial port.

For example, 130A-F healthcare devices can include Pyxis Medstations ™ to store and dispense medications at nurse checkpoints, providing distributed access to medications needed to treat patients, Pyxis® Anesthesia Systems to store and administer medications used by anesthetists in the operating room, Pyxis SpecialtyStations ™ to store specific medications and supplies in individual treatment areas and Pyxis OncologyStations ™ in oncology departments to administer hazardous and specialty medications used to treat cancer. Healthcare devices 130A-F may also include waste devices that accept and store wasted drugs, eg, excess drugs, from healthcare professionals and track the amount of drugs wasted by healthcare professionals. In one or more embodiments, one or more of the waste devices can be a Pyxis EcoStation ™ system.

User devices 140A-C can be electronic devices, such as laptop or desktop computers, mobile phones, personal digital assistants ("PDAs"), portable media players, tablets, televisions or other displays, or other appropriate computing devices that are may be used to display user interfaces that facilitate the provision of medical care to patients, such as user interfaces that display information related to the provision of medical care to patients and / or user interfaces that enable a healthcare professional, such as as a doctor or nurse, access, create and / or modify information related to the provision of medical care to patients, such as modifying a schedule to prepare IV in the PIS. Example user interfaces are discussed below with respect to Figures 7-10. In the example of Figure 1, user device 140A is represented as a mobile phone, user device 140B is represented as a desktop computer, and user device 140C is represented as a personal digital assistant ("PDA"). , for example, a tablet. In one or more embodiments, user devices 140A-C may include a processor and memory.

In one or more embodiments, user devices 140A-C may be, may include, and / or may be communicatively coupled to a Medical Transaction Transporter (MTC). The user devices 140A-C and / or the MTCs included therein and / or communicatively coupled to them, can be configured to initiate communication with the control system 110 and / or any of the health care devices 130A-F, when User devices 140A-C are located in the vicinity of, for example, a predetermined distance, from any of the healthcare devices 130A-F, and / or in the vicinity of one or more patients. Alternatively or additionally, the control system 110 and / or any of the healthcare devices 130A-F may be configured to initiate communication with the user devices 140A-C, and / or the MTCs included therein. and / or communicatively coupled thereto, when the user devices 140A-C are located in the vicinity, for example, at a predetermined distance, of any of the health care devices 130A-F and / or in the vicinity of one or more patients.

In one or more embodiments, the user devices 140A-C, and / or the MTCs included therein and / or communicatively coupled to them, may be configured to initiate communication with any of the healthcare systems 120A-D when the devices User 140A-C are located in the vicinity, eg, at a predetermined distance, of any of the healthcare devices 130A-F, and / or in the vicinity of one or more patients. Alternatively or additionally, any of the 120A-D healthcare systems can be configured to initiate communication with user devices 140A-C, and / or the MTCs included in them and / or communicatively coupled thereto, when the user devices 140A-C are located in the vicinity, for example, at a predetermined distance, of any of the health care devices 130A-F, and / or in the vicinity of one or more patients.

In operation, the control system 110, health care systems 120A-D, health care devices 130A-F, and / or user devices 140A-C can transmit electronic data streams to each other over the network 105 The messages may be related to healthcare that is being facilitated by any of the healthcare systems 120A-D, healthcare devices 130A-F, and / or user devices 140A-C. For example, a message can include an order for a drug that is transmitted from a POE system to a PIS. In one or more embodiments, the PIS may subsequently transmit at least a portion of the message to a healthcare device 130A, indicating that the requested medication is to be administered to the patient. Alternatively or additionally, a message may be related to the progress of the administration of the medication, such as by one or more of the healthcare devices 130A-F. For example, healthcare device 130A may transmit a message to the PIS indicating the progress of administration of medication by healthcare device 130A to the patient. For example, the message may indicate that the healthcare device 130A has started to administer the medication, the healthcare device 130A has administered an indicated amount of the medication, or the healthcare device 130A has completed the administration of the medication.

Control system 110 may provide user identity and notification systems. For example, control system 110 can authenticate users and can control access for one user or group of users. For example, a physician may be allowed to enter orders in a POE system, while a nurse practitioner may only be allowed to view orders in the POE system. Thus, the control system 110 may provide different views of the information, for example, information received from one or more of the healthcare systems 120A-D and / or healthcare devices 130A-F, to different users in depending on the access privileges of the users. Control system 110 can also provide user interfaces to users, such as through user devices 140A-C, and can manage user interactions with user interfaces. In one or more embodiments, the control system 110 may provide information for a patient to a user device 140A to be displayed on one of the user interfaces when the control system 110 determines that the user device 140A is close to the patient. patient and / or in the vicinity of one of the healthcare devices 130A-F that provides and / or facilitates the delivery of healthcare to the patient. An example process of a context-sensitive notification system is discussed below with respect to Figure 4.

Alternatively or additionally, the user device 140A may determine that it is located in the vicinity of a patient and / or in the vicinity of the healthcare devices 130A-F. User device 140A may then transmit an indication to control system 110 indicating that user device 140A is located in the vicinity of the patient and / or one of the healthcare devices 130A-F. In response, the control system 110 may transmit information to the user device 140A pertaining to the patient and / or the one of the healthcare devices 130A-F. Example processes for one or more of the user devices 140A-C in a context-sensitive notification system are described below with respect to Figures 5 and 6.

Control system 110 may also transmit notifications to one or more of the users, such as through user devices 140A-C. For example, the control system 110 may transmit a notification to a user device 140A accessed by a user, for example, a user device 140A in which the user has authenticated, when the control system 110 determines that the user is in the vicinity of a patient who may need care, for example, a patient who is receiving medical care from one of the healthcare devices 130A-F who may be experiencing an error. In one or more embodiments, one or more of the notifications may be transmitted to user devices 140A-C through a user interface. For example, the notification may cause a graphical indicator to be displayed on a user interface that is displayed on a user device 140A. Example user interfaces for presenting notifications are discussed below with respect to Figures 7 and 10.

Figure 2 illustrates an example messaging architecture 200 in which a context-sensitive health care notification system may be implemented in accordance with one or more embodiments. However, not all of the components depicted may be necessary and one or more embodiments may include additional components that are not shown in the figure. Fewer additional or different components may be provided.

Messaging architecture 200 includes control system 110, one or more healthcare systems 120A-D, one or more healthcare devices 130A-F, and one or more user devices 140A-C. Control system 110, healthcare systems 120A-D, healthcare devices 130A-F, and user devices 140A-C can be communicably coupled to each other, such as via network 105 shown in Figure 1 The one or more healthcare systems 120A-D, one or more healthcare devices 130A-F, and one or more user devices 140A-C may include and / or may be coupled to interfaces 210A-M. The interfaces 210AM can be adapters that are used by one or more healthcare systems 120A-D, one or more healthcare devices 130A-F, and one or more user devices 140A-C to transmit messages to each other through system 110 of control. In one or more embodiments, the 210A-M interfaces may be, and / or may include, the adapters described in US Patent Application Serial No. 13 / 421,776, entitled "Scalable Communication System," filed March 15. from 2012,

In one or more embodiments, messages transmitted by healthcare systems 120A-D, healthcare devices 130A-F, and / or user devices 140A-C may be routed through control system 110, for example, through the 210A-M interfaces. For example, if a healthcare device 130A is sending a message to healthcare system 120C, healthcare device 130A can use interface 210A to transmit the message to control system 110, and control system 110 can forward the message to interface 210H, which provides the message to healthcare system 120C. In one or more embodiments, the control system 110 may store the messages, such as in the data store 114, for further processing, such as to identify whether any information indicated in the messages should be transmitted to one or more of the user devices 140A-C, such as by notification and / or by a user interface.

In one or more embodiments, control system 110 may include an interface system that receives messages from one or more of health care systems 120A-D, health care devices 130A-F, and / or devices 140A- User C, through the 210AM Interfaces. The interface system can provide the 210A-M interfaces to one or more of the 120A-D healthcare systems, the 130A-F healthcare devices and the 140A-C user devices, and one or more of the 120A systems. -D healthcare devices, healthcare devices 130A-F and user devices 140A-C can transmit messages to the interface system using interfaces 210A-M.

In one or more embodiments, the interface system receives the messages in a first external format, for example, a native format of the device and / or transmission system converts the messages into an internal messaging format, for example, to process and store the messages, converts the messages into a second external format, for example, a format native to the receiving device and / or system, and then transmits the messages in the second external format to the receiving device. In one or more embodiments, the first external format can be the same as the second external format. The interface system can be implemented as described, for example, in United States Patent Application Serial No. 13 / 421,776, entitled "Scalable Communication System" filed March 15, 2012,

Alternatively or additionally, one or more of the healthcare systems 120A-D, healthcare devices 130A-F and / or user devices 140A-C can communicate with the control system 110 without using the interfaces. 210A-M. Alternatively or additionally, one or more of the healthcare systems 120A-D, healthcare devices 130A-F and / or user devices 140A-C can transmit messages directly to each other, for example, without routing. the messages through the control system 110.

Figure 3 illustrates an alternative example messaging architecture 300 in which a context-sensitive health care notification system may be implemented in accordance with one or more embodiments. However, not all of the components depicted may be necessary and one or more embodiments may include additional components that are not shown in the figure. Fewer additional or different components may be provided.

The messaging architecture 300 includes an interface system 320, the control system 110, one or more healthcare systems 120A-D, one or more healthcare devices 130A-F, and one or more user devices 140A-C. Control system 110, interface system 320, healthcare systems 120A-D, healthcare devices 130A-F, and user devices 140A-C can be communicably coupled to each other, such as over the network. 105 shown in Figure 1. The one or more healthcare systems 120A-D, one or more healthcare devices 130A-F, and one or more user devices 140A-C may include and / or may be coupled to 210A interfaces. -M. Control system 110 may include and / or may be communicatively coupled to interface 310. Interfaces 210A-M, 310 may be adapters that are used by one or more healthcare systems 120A-D, one or more devices 130A- F, one or more user devices 140A-C, and control system 110 to transmit messages to each other through interface system 320. In one or more embodiments, the interfaces 210A-M, 310 may be, and / or may include, the adapters described in United States Patent Application Serial No. 13 / 421,776, entitled "Scalable Communication System", filed 15 March 2012.

In messaging architecture 300, interface system 320 may be separate from control system 110, for example, so that messages to / from control system 110 are sent through interface system 320. For example, the control system 110 and the interface system 320 can be separate devices, such as separate servers, or the control system 110 and the interface system 320 can be and / or can include different hardware on the same device. Alternatively, the control system 110 may receive messages directly from interface system 320, for example, without the use of interface 310. Thus, in messaging architecture 300, messages are sent through interface system 320, rather than through system 110 control, as previously discussed with respect to Figure 2.

Alternatively or additionally, one or more of the healthcare systems 120A-D, healthcare devices 130A-F, user devices 140A-C, and / or control system 110 may communicate with system 320 interface without using interfaces 210A -M, 310. Alternatively or additionally, one or more of the 120A-D healthcare systems, 130A-F healthcare devices, 140A-C user devices and / or or the control system 110 can transmit messages directly to each other, for example, without routing the messages through the interface system 320.

Figure 4 illustrates a flow diagram of an exemplary process 400 for a context-sensitive health care notification system in accordance with one or more embodiments. For purposes of explanation, the exemplary process 400 is described herein with reference to the exemplary network environment 100 control system 110 of FIG. 1; however, the example process 400 is not limited to the control system 110 of the example network environment 100 of Figure 1. For example, in one or more embodiments, the example process 400 may be performed by the system 320 of interface of Figure 3 and / or any of the healthcare systems 120A-D of Figure 1. In addition, for purposes of explanation, the example process blocks 400 are described herein as being serially or linearly produced. . However, several blocks of the example process 400 can occur in parallel. Furthermore, it is not necessary to perform the blocks of the example process 400 in the order shown and / or it is not necessary to perform one or more of the blocks of the example process 400.

At block 402, the control system 110 determines that one of the user devices 140A-C, such as the user device 140A, is located in the vicinity of one of the healthcare devices 130A-F, such as the healthcare device 130A, and / or in the vicinity of a patient, such as a patient for whom one of the healthcare devices 130A-F, such as healthcare device 130A, is providing and / or facilitating care medical. In one or more embodiments, the control system 110 may receive an indication from the user device 140A and / or one or more of the healthcare devices 130A-F, indicating that the user device 140A is located in the vicinity of one. healthcare devices 130A-F and / or one or more patients. For example, healthcare device 130A can be configured to determine when one of user devices 140A-C is located in the vicinity of healthcare device 130A, for example, by detecting one or more wireless signals transmitted by devices 140A- C user, such as infrared signals, wireless Ethernet signals, Bluetooth signals, or generally any wireless signal that is transmittable by user devices 140A-C. Alternatively or additionally, the healthcare device 130A can include an induction coil and the healthcare device 130A can be configured to use the induction coil to determine if the healthcare device 130A can interact with any of the devices. 140A-C user.

Alternatively or additionally, the control system 110 may determine that the user device 140A is located in the vicinity of the healthcare device 130A based at least in part on the information and / or signals that are received, directly or indirectly. , from user device 140A and / or healthcare device 130A. For example, control system 110 may use triangulation or other positioning techniques to determine the locations of user device 140A and / or healthcare device 130A based on wireless signals received from user device 140A and / or device. 130A health care. Alternatively or additionally, the control system 110 may receive information from one or more of the healthcare systems 120A-D indicating the location of the healthcare device 130A, such as through network 105. Thereafter , the control system 110 may determine the location of the user device 140A and / or if the user device 140A is located in the vicinity of the location of the healthcare device 130A.

In one or more embodiments, the healthcare device 130A may store an identifier of a patient to whom the healthcare device 130A is providing medical care and / or facilitating the provision of medical care. Thus, health care device 130A may provide control system 110 with a patient identifier that may be located in the vicinity of user device 140A, for example, when health care device 130A is located in the vicinity of the user device. user device 140A. Alternatively or additionally, the control system 110 may retrieve an identifier of the patient to whom the healthcare device 130A is providing and / or facilitating the delivery of medical care from one or more of the healthcare systems 140A-D.

In one or more embodiments, patients may be provided with a patient information device, such as a bracelet, necklace, anklet, etc., which may be, or may include, an active embedded computer and / or a passive device, such as a radio frequency identification device. The patient information device may respond to devices located throughout the healthcare facility, such as readers or wireless transmitters / receivers, to provide the identity of the patient associated with the patient information device and / or other information, when the device displays patient information is queried, for example, activated, by devices. In one or more embodiments, any of the healthcare devices 130A-F and / or any of the user devices 140A-C, may include the devices that query, for example, activate, the patient information device and receive the patient identifiers from patient information devices.

Therefore, in one or more embodiments, the devices that are located throughout the hospital can receive identifiers of patients located in the vicinity, for example, patients that are near the devices, and the devices can transmit the identifiers of the devices. patients to the control system. 110, such as through network 105. Control system 110 may retrieve device locations from one or more of health care systems 120A-D, such as a hospital information system, and hospital information system 110. control can determine approximate patient locations based on the location of the devices that transmitted the patient identifiers. The control system 110 can then determine if any of the user devices 140A-C are located in the vicinity of the approximate locations of any of the patients.

At block 404, the control system 110 may receive information from one or more of the healthcare systems 120A-D that is related to the healthcare device 130A that is located near the user device 140A and / or that is relating to any patient in the vicinity of the user device 140A. For example, the control system 110 may receive information from one or more of the health care systems 120A-D through the network 105. In one or more embodiments, the information received may include information regarding the medications being used. provide a patient, such as from the pharmacy information system, laboratory results for a patient, such as from a laboratory information system, a medical history and / or profile of the patient, such as from the pharmacy information system and / or a hospital information system, the status of the medications being prepared for the patient, such as a pharmacy information system, maintenance information and / or calibration related to the health care device 130A and / or , in general, any information that may be provided by any of the 120A-D healthcare systems. In one or more embodiments, the control system 110 may not receive any information from any of the health care systems 120A-D, for example, the control system 110 may, in one or more embodiments, bypass block 404.

At block 406, the control system 110 may receive information from the healthcare device 130A that is in the vicinity of the user device 140A. The information received can be related to the healthcare device 130A and / or the information received can be related to any patient in the vicinity of the user device 140A. For example, the control system 110 may receive information from the healthcare device 130A via the network 105. In one or more embodiments, the information may include information related to the progress of the administration of a medication to a patient, such as such as from an infusion pump, information related to monitoring a patient's vital sign, such as from a monitoring device, information related to the progress of a breathing protocol being implemented for the patient, such as from a device respiratory, or, generally, any information that may be received from the healthcare device 130A. In one or more embodiments, the control system 110 may not receive any information from the healthcare device 130A, for example, the control system 110 may, in one or more embodiments, bypass block 406.

At block 408, the control system 110 transmits at least a portion of the information received from one or more of the healthcare systems 120A-D, and / or the healthcare device 130A, to the user device 140A. For example, the control system 110 may transmit at least a portion of the received information to the user device 140A through the network 105. In one or more embodiments, the user device 140A may display at least some of the information, for example, to a healthcare professional, such as a doctor or nurse, as explained below with respect to Figures 5-6.

Alternatively or additionally, control system 110 may process information received from one or more healthcare systems 120A-D and / or healthcare device 130A, to generate workflow information, control information, or other information that may be generated from the processing of the information received. The control system 110 can then transmit the processed information and / or the information generated at least in part from the processing of the received information, to the user device 140A. For example, the control system 110 may process the received information to determine if corrective actions are required, a security problem exists, and / or an error exists. If the control system 110 determines that corrective action is required, a safety problem exists, and / or an error exists, the control system 110 may transmit an indication of the corrective action, the safety problem, and / or the error to the device. 140A user, such as through an alert and / or notification.

In one or more embodiments, control system 110 may process information received from one or more healthcare systems 120A-D and / or healthcare device 130A, in addition to information received from user device 140A, with in order to provide context for an alert and / or notification. The control system 110 may use information such as the proximity of the user device 140A to the monitoring device 130A. healthcare, a condition of a patient for whom the healthcare device 130A is providing healthcare, a type of medication being administered to the patient, or generally any other information received, to provide context for an alert and / or notification. For example, if the processed information indicates that a healthcare professional is next to the healthcare device 130A, then the monitoring system 110 may cause a visual alert to be displayed to the healthcare professional, rather than an audible alert. Similarly, if the processed information indicates, for example, that the medication in an infusion pump is not life-critical, then the monitoring system 110 may provide a notification to a healthcare professional who is caring for the patient but is You are away from the infusion pump, rather than any healthcare professional in the vicinity of the infusion pump.

Alternatively or additionally, the control system 110 may delay alarms on the healthcare devices 130A-F and / or may allow a healthcare professional to indicate that they will respond to an alarm within a configurable period of time. For example, if a healthcare professional indicates that it will respond to an alarm from a healthcare device 130A within a configurable period of time, the control system 110 can cause the healthcare device 130A not to generate the alarm unless there is an alarm. the configurable time has elapsed and the healthcare professional has not responded to the alarm.

In one or more embodiments, a healthcare professional can remotely determine, such as through one of the 140A-C user devices, that a pump should take action, such as restarting the pump when the volume drops to zero and adding a small amount of volume to allow the infusion to restart and provide the associate nurse practitioner with a more convenient time to approach the infusion, for example to switch to a new bag. Thus, a healthcare professional may be able to remotely direct an alarm from a healthcare device 130A, such as through one of the user devices 140A-C. Alternatively or additionally, the control system 110 and / or a drug library may store actions that can be taken remotely, for example, through one of the user devices 140A-C, based on the features of the health care device 130a, patient, alarm, etc. For example, the control system 110 may allow different actions to be performed remotely, by reprogramming a healthcare device 130A, based on one or more of: the type of drug being administered by the medical device 130A health care, the type of alarm that the health care device 130A generates, the patient care area where the health care device 130A is located and / or, in general, any characteristic associated with the health care device 130A and / or the patient.

FIG. 5 illustrates a flow chart of an example process 500 for a user device 140A in a context-sensitive health care notification system in accordance with one or more embodiments. For purposes of explanation, the example process 500 is described herein with reference to the user device 140A of the example network environment 100 of Figure 1; however, the example process 500 is not limited to the user device 140A of the example network environment 100 of Figure 1. In addition, for purposes of explanation, the blocks of the example process 500 are described herein as being they produce in series or linearly. However, several blocks of the example process 500 can occur in parallel. Furthermore, it is not necessary to perform the blocks of the example process 500 in the order shown and / or it is not necessary to perform one or more of the blocks of the example process 500.

At block 502, a user device 140A determines that it is located in the vicinity of a healthcare device and / or a patient. For example, user device 140A may include a device that is configured to query patient information devices that, for example, patients may wear. Thus, user device 140A can determine that it is located in the vicinity of a patient when user device 140A receives a response from a patient querying patient information device for a patient. In one or more embodiments, the user device 140A may determine that it is located in the vicinity of a healthcare device 130A based on wireless signals received from the healthcare device 130A, and / or a wireless device or interface coupled thereto. . Wireless signals can include, for example, infrared signals, Bluetooth signals, wireless Ethernet signals, and / or generally any wireless signal. For example, user device 140A can measure the strength of a signal received from healthcare device 130A, such as a wireless Ethernet signal and / or other long-range wireless signals, and / or user device 140A can determine whether receives some signal from the healthcare device 130A, such as infrared signals, Bluetooth signals, and / or other short-range wireless signals. In one or more embodiments, user device 140A may include an induction coil that can be used by user device 140A to determine if user device 140A can interact with healthcare device 130A, such as by identification by radio frequency. User device 140A may transmit an indication to control system 110, interface system 320, and / or any of the healthcare systems 120A-D, when user device 140A determines that it is located in the vicinity of device 130A. health care.

Alternatively or additionally, the user device 140A may receive an indication from the control system 110, the healthcare device 130A, the interface system 320, and / or any of the healthcare systems 120A-D, indicating that user device 140A is located in the vicinity of user device 130A medical care and / or one or more patients. In this case, the user device 140A may determine that it is located in the vicinity of the healthcare device 130A and / or the one or more patients based at least in part on the received indication.

At block 504, the user device 140A receives information regarding the nearby health care device 130A and / or the one or more patients located nearby. For example, user device 140A may receive information from control system 110, such as through network 105. Alternatively or additionally, user device 140A may receive information from one or more of the systems. 120A-D healthcare and / or interface system 320, such as through network 105.

At block 506, the user device 140A determines whether the received information indicates that corrective action is required, a security problem exists, or an error exists with respect to the healthcare device 130A and / or one or more patients located nearby. In one or more embodiments, the control system 110 may determine that corrective action is required, a security problem exists, and / or an error exists, and the information received may indicate the corrective action, the security problem, and / or the error. determined by the control system 110, such as a safety issue or an error regarding administration protocols, drug interactions, etc.

If, at block 506, the user device 140A determines that corrective action is required, a security problem exists, and / or an error exists, the user device 140A moves to block 508. At block 508, the device User 140A displays an alert or notification indicating the required corrective action, security issue, and / or error. For example, user device 140A may display a graphical indicator to indicate the existence of a required corrective action, safety issue, or error, with respect to healthcare device 130A and / or one or more patients located nearby, such as such as the asterisk indicator ("*") discussed below with respect to Figures 7 and 10.

If, at block 506, the user device 140A determines that the received information does not indicate that corrective action is required, a security problem exists, and / or an error exists, the user device 140A moves to block 510. At at block 510, user device 140A displays at least a portion of the received information. For example, user device 140A may display at least a portion of the information received through one or more of the user interfaces discussed below with respect to Figures 7-10.

Alternatively or additionally, the user device 140A may not display the at least part of the information received until requested to do so by a user, such as a healthcare professional who interacts with the user device 140A. For example, the user device 140A may display a notification to the healthcare professional indicating that the information received is available and requesting if the healthcare professional wants the user device 140A to display at least part of the information received on a screen of the user device 140A and / or on a display or monitor located near user device 140A.

FIG. 6 illustrates a flow diagram of an example process 600 for a user device 140A in a context-sensitive health care notification system in accordance with one or more embodiments. For purposes of explanation, the example process 600 is described herein with reference to the user device 140A of the example network environment 100 of Figure 1; however, the example process 600 is not limited to the user device 140A of the example network environment 100 of Figure 1. Furthermore, for purposes of explanation, the blocks of the example process 600 are described herein as being they produce in series or linearly. However, several blocks of the example process 600 can be produced in parallel. Furthermore, it is not necessary to perform the blocks of the example process 600 in the order shown and / or it is not necessary to perform one or more of the blocks of the example process 600.

At block 602, user device 140A receives an indication that it is located in the vicinity of a healthcare device 130A and / or one or more patients. For example, user device 140A may receive indication from control system 110, healthcare device 130A, interface system 320, and / or any of the healthcare systems 120A-D, such as through the network 105. In one or more embodiments, the indication may be a wireless signal generated by the healthcare device 130A, and / or a device that is communicatively coupled thereto, that is detected by the user device 140A, such as a infrared signal, a Bluetooth signal, a radio frequency identification signal or, in general, any wireless signal.

At block 604, user device 140A receives information that relates to healthcare device 130A and / or the one or more patients located nearby. As previously discussed, user device 140A may, for example, receive information from one or more of control system 110, healthcare systems 120A-D, and / or interface system 320, such as through network 105.

At block 606, the user device 140A may display at least a portion of the received information, such as via one or more of the user interfaces discussed below with respect to Figures 7-10. In one or more embodiments, a user interacting with user device 140A, such as a healthcare professional, can use the displayed information to facilitate the provision of healthcare to a patient. For example, the healthcare professional can use the user interface to adjust a parameter associated with the delivery of healthcare to the patient, such as the rate at which the healthcare device 130A delivers a medication to the patient, the scheduled time at that the pharmacy will prepare a medicine for the patient, for example through the pharmacy information system, or, in general, any parameter that relates to the provision of medical care to the patient that can be configured through the user device 140A , such as through network 105.

FIG. 7 illustrates an example user interface 700 that may be implemented in a context-sensitive health care notification system in accordance with one or more embodiments. However, not all of the components depicted may be necessary and one or more embodiments may include additional components that are not shown in the figure. Fewer additional or different components may be provided.

User interface 700 can display information related to ongoing actions performed by one or more of the healthcare devices 130A-F, such as medical orders being administered. For example, the user interface 700 displays a report of IVs that are being administered by, and / or with the facilitation of, one or more of the healthcare devices 130A-F. In one or more embodiments, medical order administrations that will end within a preselected period of time can be distinguished at user interface 700 from other administrations by color highlighting or other means. User interface 700 can further display time remaining, medication, and patient name, as well as buttons for program control. In one or more embodiments, the user interface 700 may display pending infusions or infusions scheduled to begin within a preselected period of time.

In operation, the user interface 700 may be provided by the control system 110 and / or one or more of the healthcare systems 120A-D, for display on a screen, such as a screen of one or more of the devices. 140A-C user and / or a display or monitor associated with one or more of the 120A-D healthcare systems. For example, the control system 110 may receive messages from one or more of the healthcare devices 130A-F related to actions being performed by the one or more healthcare devices 130A-F. The control system 110 may analyze the received messages to obtain the information displayed on the user interface 700, and / or the received messages may be displayed on the user interface 700.

The information displayed on the user interface 700 may be updated in real time as the control system 110 and / or one or more of the healthcare systems 120A-D receive messages from the healthcare devices 130A-F, such as while orders are administered to patients. In one or more embodiments, user interface 700 can be used to modify drug preparation, such as by scheduling and / or reprogramming, drug preparation.

In one or more embodiments, the user interface 700 may also display notifications and / or alerts, such as when a healthcare professional is associated with a user device 140A that displays the user interface 700. For example, in the user interface 700, notifications can be indicated with an asterisk ("*"). In one or more embodiments, the healthcare professional may select information that is displayed with an asterisk, for example, by tapping or clicking the information, to receive additional information regarding the notification. In one or more embodiments, one or more of the alerts and / or notifications can only be viewed when the healthcare professional is located near the one or more healthcare devices 130A-F to which the alerts and / or notifications pertain.

FIG. 8 illustrates an example user interface 800 that may be implemented in a context-sensitive health care notification system in accordance with one or more embodiments. However, not all of the components depicted may be necessary and one or more embodiments may include additional components that are not shown in the figure.

Fewer additional or different components may be provided.

User interface 800 may display information related to a patient, such as information received from one or more of the healthcare systems 120A-C and / or one or more of the healthcare devices 130A-F. The information displayed may include information related to medications and / or infusions, such as IVs, that are programmed for the patient, and the information may be received from the healthcare system 120C. The information may further include information related to medications and / or infusions being administered to the patient and this information may be received from one or more of the healthcare devices 130A-F. For example, the user interface 800 displays information related to scheduled medications and IVs for an identified patient. In one or more embodiments, the user interface 800 may be color-coded to indicate the status and timing of each medication administration. For example, a medication delivery window that extends from thirty minutes before and thirty minutes after the Scheduled delivery can be indicated by a yellow band on the user interface 800.

In operation, the user interface 800 may be provided by the control system 110 and / or one or more of the healthcare systems 120A-D, for display on a screen, such as a screen of one or more of the user devices 140A-C and / or a display or monitor associated with one or more of the healthcare systems 120A-D. For example, the control system 110 may receive messages from one or more of the healthcare systems 120A-D, and / or one or more of the healthcare devices 130A-F, that relate to a patient. The control system 110 can analyze the received messages to obtain the information displayed on the user interface 800 and / or the received messages can be displayed on the user interface 800.

In one or more embodiments, the user interface 800 may be automatically provided to the user device 140A of a healthcare professional when the healthcare professional is in the vicinity of the patient and / or in the vicinity of one or more care devices 130A-F. that provide and / or facilitate the provision of medical care to the patient. Thus, the healthcare professional user device 140A can automatically display, and / or prepare to display, information related to an identified patient when the healthcare professional is near the patient, such as at the patient's bedside. Consequently, the information displayed on the user interface 800 may change as the healthcare professional moves through the healthcare facility.

In one or more embodiments, user device 140A may receive information to display user interface 800 when the healthcare professional is in close proximity to the patient, but user device 140A may not display user interface 800 until informed. ask the healthcare professional. For example, the user device 140A may receive the information to display the user interface 800 and then it may display a notification to the healthcare professional indicating that the information is available and requesting whether the healthcare professional wants the user interface 800 to be displayed on. the user device 140A and / or on a display or monitor located near the user device 140A.

Information displayed on user interface 800 may be updated in real time as control system 110 and / or one or more of healthcare systems 120A-D receive messages from healthcare devices 130A-F, such as as, while orders are being administered. to the patient. In one or more embodiments, user interface 800 can be used to schedule and / or reprogram drug preparation, such as by healthcare system 120C.

Information displayed on user interface 800 can be updated in real time as control system 110 and / or one or more of healthcare systems 120A-D receive messages from healthcare devices 130A-F and / or healthcare systems 120A-D, such as while administering orders to patients, while preparing orders for administration to patients, and / or when receiving orders from an order entry system from a doctor. In one or more embodiments, user interface 800 may be used to verify order delivery, such as a healthcare professional verifying that a drug scheduled for delivery and / or a drug being delivered matches the ordered drug. In one or more embodiments, a healthcare professional may be able to select, such as touch or click, an command and the user interface 800 may display an image of the medication being administered, or about to be administered. .

FIG. 9 illustrates an example user interface 900 that may be implemented in a context-sensitive health care notification system in accordance with one or more embodiments. However, not all of the components depicted may be necessary and one or more embodiments may include additional components that are not shown in the figure. Fewer additional or different components may be provided.

The user interface 900 may also display information to an identified healthcare professional that relates to ongoing actions they are performing, and / or the facilitation of, one or more of the healthcare devices 130A-F, and for which the healthcare professional is facilitating and / or monitoring. The user interface 900 may also display information to the identified healthcare professional that relates to future actions that they will take, and / or the facilitation of, one or more of the healthcare devices 130A-F and for which the healthcare professional is concerned. facilitating and / or monitoring. Alternatively or additionally, user interface 900 may display information related to ongoing or future actions that are being performed near user device 140A and a healthcare professional accessing user device 140A. For example, user interface 900 displays a report of IVs being administered by one or more of the healthcare devices 130A-F. In one or more embodiments, the user interface 900 may include scheduling medication administrations to ensure adequate patient medication while spreading the workload over a period of time to ensure that all medication is administered rapidly.

In operation, the user interface 900 may be provided by the control system 110 and / or one or more of the healthcare systems 120A-D, for display on a screen, such as a screen of one or more of the devices. User 140A accessed by a healthcare professional and / or a display or monitor associated with one or more than 120A-D healthcare systems. For example, the control system 110 may receive messages from one or more of the healthcare systems 120A-D, and / or one or more of the healthcare devices 130A-F, that relate to ongoing actions and / or or future actions that are to be performed with the facilitation of the healthcare professional and / or are performed in close proximity to the healthcare professional, as indicated by the location of the user device 140A. The control system 110 can analyze the received messages to obtain the information displayed on the user interface 900 and / or the received messages can be displayed on the user interface 900.

In one or more embodiments, the user interface 900 may be automatically provided to the user device 140A of a healthcare professional when the healthcare professional is in the vicinity of the patient and / or in the vicinity of one or more care devices 130A-F. providing medical care and / or facilitating the provision of medical care to one or more patients. Thus, the healthcare professional user device 140A can automatically display, and / or prepare to display, information related to ongoing and / or future actions that are being performed and / or will be performed near the location of the healthcare professional. Consequently, the information displayed on the user interface 900 may change as the healthcare professional moves through the healthcare facility.

In one or more embodiments, user device 140A may receive information to display user interface 900 when the healthcare professional is near ongoing or future actions, but user device 140A may not display user interface 900 until requested by the healthcare professional. For example, the user device 140A may receive the information to display the user interface 900 and then it may display a notification to the healthcare professional indicating that the information is available and requesting whether the healthcare professional wants the user interface 900 to be displayed on. the user device 140A and / or on a display or monitor located near the user device 140A.

Information displayed on user interface 900 may be updated in real time as control system 110 and / or one or more of healthcare systems 120A-D receive messages from healthcare devices 130A-F, such as while administering orders to patients. In one or more embodiments, user interface 900 may be used to verify order delivery, such as a healthcare professional verifying that a drug scheduled for delivery and / or a drug being delivered matches the ordered drug. In one or more embodiments, a healthcare professional may be able to select, such as tapping or clicking, an command and the user interface 900 may display an image of the medication being administered, or about to be administered. .

Figure 10 illustrates an example user interface 1000 that may be implemented in a context-sensitive health care notification system in accordance with one or more embodiments. However, not all of the components depicted may be necessary and one or more embodiments may include additional components that are not shown in the figure. Fewer additional or different components may be provided.

The user interface 1000 may display information related to patients in a healthcare facility and / or in an area of a healthcare facility, such as alerts or notifications related to medical care being administered to patients in a healthcare facility. For example, the user interface 1000 may display a graphical representation of each room in an area of the healthcare facility, the name of the patient occupying each room, if any, and any alerts or notifications that apply to any of the displayed patients. In the user interface 1000, an alert or notification is indicated by an asterisk ("*"); however, any other graphical indicator can be used to indicate an alert and / or notification.

In operation, the user interface 1000 may be provided by the control system 110 and / or one or more of the healthcare systems 120A-D, for display on a screen, such as a screen of one or more of the devices. 140A-C user and / or a display or monitor associated with one or more of the 120A-D healthcare systems. For example, the control system 110 may receive messages from one or more of the healthcare devices 130A-F related to actions being performed by the one or more healthcare devices 130A-F. The control system 110 can analyze the received messages to determine if any alterations and / or notifications should be displayed through the user interface 1000, such as if discrepancies and / or errors are identified from the received messages.

In one or more embodiments, the user interface 1000 may be automatically provided to the user device 140A of a healthcare professional when the healthcare professional is in the vicinity of the healthcare facility area depicted on the user interface 1000. Thus, the healthcare professional user device 140A can automatically display, and / or prepare for display, the user interface 1000 when a healthcare professional is in the vicinity of the depicted area. Consequently, the information displayed on the user interface 1000 may change as the healthcare professional moves through the healthcare facility.

In one or more embodiments, user device 140A may receive information to display user interface 1000 when the healthcare professional is located near the area depicted, but user device 140A may not display user interface 1000 until requested by the healthcare professional. For example, him User device 140A can receive the information to display the user interface 1000 and can then display a notification to the healthcare professional indicating that the information is available and requesting if the healthcare professional wants the user interface 1000 to be displayed on the user device 140A. user and / or on a screen or monitor located near the user device 140A.

Information displayed on user interface 1000 may be updated in real time as control system 110 and / or one or more of healthcare systems 120A-D receive messages from healthcare devices 130A-F, such as while orders are administered to patients.

In one or more embodiments, the user interface 1000 may display the infusion status for each patient and when an alert occurs, the box representing the patient's room flashes red to draw attention to the alert. Consequently, a healthcare professional accessing the user interface 1000 can quickly and easily identify the patient from the user interface, such as at a nursing check-in, and take appropriate action to address the condition causing the alert. In one or more embodiments, certain alerts that have been identified as particularly important events may be displayed on multiple screens throughout the healthcare facility, such as in the pharmacy.

In one or more embodiments, the user interface 1000 may also be used to update the administrative records of the healthcare facility. For example, if a patient changes rooms, a healthcare professional can transmit a notification of the room change to the control system 110 by selecting the patient's name and dragging that patient to the new room. In addition, the user interface 1000 may be updated to reflect the room change.

Figure 11 conceptually illustrates electronic system 1100 with which one or more embodiments of the subject technology can be implemented. The electronic system 1100, for example, may be, or may include, the control system 110, the interface system 320, one or more of the health care systems 120A-D, one or more of the devices 130A-F of healthcare, one or more of the 140A-C user devices, a desktop computer, a laptop, a tablet, a telephone, a personal digital assistant (PDA) and / or generally any electronic device that transmits signals through a network. Such an electronic system includes various types of computer-readable media and interfaces to various other types of computer-readable media. The electronic system 1100 includes bus 1108, processing unit (s) 1112, system memory 1104, read-only memory (ROM) 1110, permanent storage device 1102, input device interface 1114, output device interface 1106, and network interface 1116 or subsets and variations thereof.

The bus 1108 collectively represents all of the system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the electronic system 1100. In one or more embodiments, bus 1108 communicatively connects processing unit (s) 1112 with ROM 1110, system memory 1104, and permanent storage device 1102. From these various memory units, the processing unit (s) 1112 retrieve instructions to execute and data to process in order to execute the processes of the subject disclosure. The processing unit (s) may be a single processor or a multi-core processor in different embodiments.

ROM 1110 stores static data and instructions that are necessary for processing unit (s) 1112 and other electronic system modules. Permanent storage device 1102, on the other hand, is a read / write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic 1100 is turned off. One or more embodiments of the subject disclosure use a mass storage device (such as a magnetic or optical disk and its corresponding disk drive) as a permanent storage device 1102.

Other embodiments use a removable storage device (such as a floppy disk, a flash drive, and a corresponding disk drive) as the permanent storage device 1102. Like permanent storage device 1102, system memory 1104 is a read / write memory device. However, unlike storage device 1102, system memory 1104 is volatile read and write memory, such as random access memory. System memory 1104 stores any of the instructions and data that processing unit (s) 1112 need at run time. In one or more embodiments, the processes of the subject disclosure are stored in system memory 1104, permanent storage device 1102, and / or ROM 1110. Of these various memory units, unit (s) 1112 Processing retrieves instructions to execute and data to process in order to execute the processes of one or more realizations.

Bus 1108 also connects to input and output device interfaces 1114 and 1106. The input device interface 1114 allows a user to communicate information and select commands to the electronic system. Input devices used with input device interface 1114 include, for example, alphanumeric keyboards and pointing devices (also called "cursor control devices"). The output device interface 1106 enables, for example, the display of images generated by the electronic system 1100.

Output devices used with the output device interface 1106 include, for example, printers and display devices, such as a liquid crystal display (LCD), a light-emitting diode (LED) display, a diode display organic light emitter (OLED), a flexible screen, a flat screen, a solid state screen, a projector or any other device to send information.

One or more embodiments may include devices that function as both input and output devices, such as a touch screen. In these embodiments, the feedback provided to the user can be any form of sensory feedback, eg, visual feedback, auditory feedback, or tactile feedback; and user input can be received in any form, including acoustic, voice, or tactile input.

Finally, as shown in FIG. 11, bus 1108 also couples electronic system 1100 to a network (not shown) via network interface 1116. In this way, the computer can be part of a computer network (such as a local area network ("LAN"), a wide area network ("WAN") or an Intranet, or a network of networks, such as Internet Any or all of the components of the electronic 1100 system may be used in conjunction with the subject disclosure.

Many of the features and applications described above can be implemented as software processes that are specified as a set of instructions written on a computer-readable storage medium (alternatively called computer-readable media, machine-readable media, or computer-readable storage media. machine). When these instructions are executed by one or more processing units (for example, one or more processors, processor cores, or other processing units), they cause the processing unit (s) to perform the actions indicated in the instructions. . Examples of computer-readable media include, but are not limited to, RAM, ROM, read-only compact discs (CD-ROM), recordable compact discs (CD-R), rewritable compact discs (CD-RW), digital versatile discs read-only (e.g. DVD-ROM, double-layer DVD-ROM), various recordable / rewritable DVDs (e.g. DVD-rA m, d Vd -RW, DVD RW, etc.), flash memory (e.g. SD cards, mini-SD cards, micro-SD cards, etc.), magnetic and / or solid-state hard drives, ultra-density optical discs, any other optical or magnetic media, and floppy disks. In one or more embodiments, the computer-readable media does not include carrier waves and electronic signals that pass wirelessly or over wired connections, or any other ephemeral signals. For example, computer-readable media can be completely restricted to tangible physical objects that store information in a form that is computer-readable. In one or more embodiments, the computer-readable media is non-transient computer-readable media, computer-readable storage media, or non-transient computer-readable storage media.

In one or more embodiments, a computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, or declarative languages. or procedural, and can be implemented in any form, including as a standalone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but not necessarily, correspond to a file in a file system. A program can be stored in a part of a file that contains other programs or data (for example, one or more scripts stored in a markup language document), in a single specialized file of the program in question, or in multiple coordinated files ( for example, files that store one or more modules, applets, or chunks of code). A computer program can be implemented to run on one computer or on multiple computers that are located at one site or spread across multiple sites and interconnected by a communication network.

While the above discussion is primarily concerned with multi-core microprocessors or processors running software, one or more embodiments are realized by one or more integrated circuits, such as application-specific integrated circuits (ASICs) or field-programmable gate arrays ( FPGA). In one or more embodiments, such integrated circuits execute instructions that are stored in the circuit itself.

Those skilled in the art will appreciate that the various illustrative blocks, modules, components, methods, and algorithms described herein can be implemented as electronic hardware, computer software, or combinations of both. To illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, components, methods, and algorithms have been described above, generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in varying ways for each particular application. Various components and blocks can be arranged differently (eg arranged in a different order or divided in a different way) all without departing from the scope of the subject technology.

Any specific order or hierarchy of blocks in the disclosed processes is understood to be an illustration of example approaches. Based on design preferences, it is understood that the specific order or hierarchy of blocks in the processes can be rearranged, or that all the illustrated blocks can be realized. Any of the blocks can be done simultaneously. In one or more embodiments, multitasking and processing in parallel can be advantageous. Furthermore, the separation of various system components in the above-described embodiments should not be understood as requiring such separation in all embodiments and it should be understood that the described program and system components can be generally integrated together into a single software product or packaged. across multiple software products.

As used herein, the phrase "at least one of" before a series of items, with the term "and" or "or" to separate any of the items, modifies the list as a whole, rather than each member of the list (that is, each item). The phrase "at least one of" does not require the selection of at least one of each item listed; rather, the phrase allows a meaning that includes at least one of any one of the elements and / or at least one of any combination of the elements and / or at least one of each of the elements. By way of example, the phrases "at least one of A, B, and C" or "at least one of A, B, or C" each refer to only A, only B, or only C; any combination of A, B and C; and / or at least one of each of A, B and C.

The predicate words "configured for", "operable for" and "programmed for" do not imply any particular tangible or intangible modification of a subject, but rather are intended to be used interchangeably. In one or more embodiments, a processor configured to monitor and control an operation or a component can also mean that the processor is programmed to monitor and control the operation or that the processor is operable to monitor and control the operation. Also, a processor configured to execute codes can be interpreted as a processor programmed to execute codes or operable to execute codes.

A phrase such as "an aspect" does not imply that such an aspect is essential to the subject's technology or that it applies to all configurations of the subject technology. A disclosure related to one aspect may apply to all configurations or to one or more configurations. One aspect may provide one or more examples of the disclosure. A phrase, such as an "aspect", can refer to one or more aspects and vice versa. A phrase such as an "embodiment" does not imply that such an embodiment is essential to the subject's technology or that such an embodiment applies to all configurations of the subject's technology. A disclosure related to one embodiment may apply to all embodiments, or one or more embodiments. One embodiment may provide one or more examples of the disclosure. A phrase such as an "embodiment" can refer to one or more embodiments and vice versa. A phrase such as a "configuration" does not imply that such configuration is essential to the subject technology or that said embodiment applies to all configurations of the subject technology. A disclosure related to a configuration may apply to all configurations or to one or more configurations. One configuration may provide one or more examples of the disclosure. A phrase, such as a "configuration" can refer to one or more configurations and vice versa.

The word "exemplary" is used herein to mean "serving as an example, case, or illustration." Any embodiment described herein as "exemplary" or as an "example" should not necessarily be construed as preferred or advantageous over other embodiments. Furthermore, to the extent that the term "include", "have" or the like is used in the description or claims, said term is intended to be inclusive in a similar way to the term "comprise" as "comprise" is interpreted when used as a transition word in a claim.

Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly cited in the claims.

The description above is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications of these aspects will be readily apparent to those skilled in the art and the generic principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but the full scope should be given consistent with the claims in language, in which reference to an element in the singular does not mean "one and only one" unless specifically stated, but rather "one or more". Unless otherwise specified, the term "some" refers to one or more. Pronouns in masculine (for example, his) include the feminine and neuter gender (for example, his and his) and vice versa. Titles and subtitles, if any, are used for convenience only and do not limit the disclosure of the subject matter.

Claims (12)

1. A method of providing context-associated information to a user device (140) associated with a healthcare professional, the method comprising: an infusion device, detecting a wireless signal transmitted from the user device (140) characterized by ; determining, by the infusion device and in response to detection, that the user device (140) is in the vicinity of the infusion device, wherein the infusion device is configured to deliver a drug to a patient; providing, by the infusion device, an indication to a system (110) that the user device (140) is in the vicinity of the infusion device; providing, to the control system (110) from the infusion device, an identifier for the patient; receiving, via the control system (110), a first information related to the patient and the infusion device from a healthcare system (120); receiving, by means of the control system (110) from the infusion device, a second information related to the progress of the administration of the medication to the patient; determining, by the control system (110), whether the first information or the second information indicates that corrective action is required; transmitting, from the control system (110) to the user device (140) in the vicinity, an alert, the alert indicating a course of action to take corrective action; displaying, by the user device (140), the alert when corrective action is required; and reprogramming, with the user device (140), the infusion device based on a characteristic of the alert. The method of claim 1, wherein the detection comprises detecting a radio frequency signal transmitted to the infusion device. 3. A system, comprising: a plurality of user devices (140), each associated with a healthcare professional; at least one infusion device configured to deliver a drug to a patient and a control system (110), comprising: one or more processors; Y a memory characterized in that said infusion device is configured to detect a wireless signal from at least one selected of the plurality of user devices (140) when the at least selected one of the plurality of user devices (140) enters the vicinity of the at least one infusion device; and said memory includes: Instructions that, when executed by one or more processors, cause one or more processors to: receive, from the infusion device, an indication that the selected one of the plurality of user devices (140) is in the vicinity of the infusion device; receive the first information related to the patient and the at least one infusion device from a plurality of healthcare systems (120) through a communication network (105), when it is determined that the user device (140) is in the vicinity of the at least one infusion device; Y transmit, to the selected one of the plurality of user devices (140) through the communication network (105), at least a part of the first information comprising an alert related to the at least one infusion device and the patient, the alert indicating a course of action to take corrective action with the infusion device, wherein the selected one of the plurality of user devices (140) is configured to reprogram the infusion device based on a characteristic of the alert. The system of claim 3, wherein at least one of the plurality of health care systems (120) comprises a pharmacy information system, a hospital information system, or a medical order entry system and each of the plurality of user devices (140) comprises a portable device with a display. The system of claim 4, wherein at least the part of the first information comprises laboratory results for at least one patient, the laboratory results being received from an information system of laboratory. The system of claim 3, wherein the instructions, when executed by one or more processors, further cause the one or more processors to: receive second information from the at least one infusion device through the communication network (105), when it is determined that the selected one of the plurality of user devices (140) is in the vicinity of the at least one infusion device or of the patient; Y transmit, to the selected one of the plurality of user devices (140) via the communication network (105), at least a portion of the second information. The method of claim 1, further comprising providing a further audible alert with the user device (140) when the user device (140) is away from the infusion device and wherein displaying the alert comprises providing an alert. visual when the user device (140) is in the vicinity of the infusion device. The system of claim 3, wherein the first information portion included an alert, wherein the selected one of the plurality of user devices (140) is configured to visually display the alert when the device (140) user device is in the vicinity of the infusion device and wherein the selected one of the plurality of user devices (140) is further configured to provide an audible alert when the selected one of the plurality of user devices (140) is away from the infusion device. The method of claim 1, wherein the wireless signal included at least an infrared signal, a Bluetooth signal, or a wireless Ethernet signal. The system of claim 3, wherein the wireless signal comprises at least an infrared signal, a Bluetooth signal, or a wireless Ethernet signal. The method of claim 1, further comprising reprogramming, by the control system (110), the infusion device based at least in part on the first information or the second information. The method of claim 1, wherein the user device (140) comprises one of a plurality of user devices (140), each associated with a healthcare professional for the patient.