Systems, methods, and apparatus for electronic patient care

Abstract

To provide a patient with comprehensive care including instructions and delivery of medical treatment such as medication.SOLUTION: A method, a related system, and a related device are disclosed. The method is achieved by one operable set of processor-executable instructions configured so as to be executed by a processor. The method includes: determining whether or not a monitoring client is connected to a base through physical connection; establishing a first communication link between the monitoring client and the base through the physical connection; updating an interface program on the monitoring client and the base through the first communication link, if necessary; establishing a second communication link between the monitoring client and the base using the first communication link; and transmitting data from the base to the monitoring client using the second communication link.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] Cross-reference of related applications This application is a non-provisional application claiming priority to U.S. Provisional Patent Application No. 61 / 740,474, filed Dec. 21, 2012, entitled “System, Method, and Apparatus for Communication Data” (Attorney Docket No.: J80), which is incorporated herein by reference in its entirety.

[0002] This application is also a partial continuation application of U.S. Patent Application No. 13 / 723,253, filed Dec. 21, 2012, entitled “System, Method, and Apparatus for Electronic Patient Care,” and published as U.S. Patent Application Publication No. 2013-0191413A1 on Jul. 25, 2013 (Attorney Docket No.: J85), which claims priority to the following applications: U.S. Provisional Patent Application No. 61 / 578,649, filed Dec. 21, 2011, entitled “System, Method, and Apparatus for Infusion” (Attorney Docket No.: J02); U.S. Provisional Patent Application No. 61 / 578,658, filed Dec. 21, 2011, entitled “System, Method, and Apparatus for Estimating Infusion Delivery Amount” (Attorney Docket No.: J04); U.S. Provisional Patent Application No. 61 / 578,674, filed Dec. 21, 2011, entitled “System, Method, and Apparatus for Oral Medication Administration” (Attorney Docket No.: J05); U.S. Provisional Patent Application No. 61 / 651,322, filed May 24, 2012, entitled “System, Method, and Apparatus for Electronic Patient Care” (Attorney Docket No.: J46); and U.S. Provisional Patent Application No. 61 / 679,117, filed Aug. 3, 2012, entitled “System, Method, and Apparatus for Monitoring, Adjusting, or Controlling Infusion Flow” (Attorney Docket No.: J30 Each of the above applications is incorporated herein by reference in whole. U.S. Patent Application No. 13 / 723,253, filed December 21, 2011, concerns an "electronic patient" U.S. Patent Application No. 13 / 333,574, entitled "System, Method and Apparatus for Caregiving" This is the same patent application, and was subsequently published on July 19, 2012, as U.S. Patent Application Publication No. 2012-01. 85267A1 (Agent Reference Number: J97) and A patent application filed on December 21, 2011, for "System, method, and apparatus for electronic patient care" Name of PCT application, PCT / US11 / 66588 (Agent reference number: I97WO), This is a continuation application in part, and both are incorporated herein by reference in whole. U.S. Patent Application No. 13 / 333,574, filed on January 21, 2011, is for "electronic patient monitoring." The U.S. Patent Application No. 13 / 011,543, titled "Visual System," was subsequently filed in 201 U.S. Patent Application Publication No. 2011-0313789A1 (represented by) published on December 22, 2011. This is a continuation application of the previous application (Reference No.: I52), which was filed on January 22, 2010. U.S. Provisional Patent Application No. 61 / 29 for “Electronic Instruction Intermediation System for Medical Equipment” They are claiming the interest of priority in No. 7,544 (Agent Reference Number: H53), and both of these This is incorporated herein by reference in its entirety.

[0003] This application also relates to the application filed on December 21, 2012, "System, method and The U.S. Patent Application No. 13 / 723,239, titled "device for 'device'", was subsequently filed in 2013. U.S. Patent Application Publication No. 2013-0297330A1 (Agent Arrangement) was published on November 7. This is a continuation application of application number J77), and this application claims priority over the following application: A US patent application filed on December 21, 2011, entitled "System, method and apparatus for intravenous fluid administration" National Provisional Patent Application No. 61 / 578,649 (Agent Reference Number: J02); The "System, Method, and Apparatus for Estimating Infusion Delivery Volume" filed on December 21, 2011, U.S. Provisional Patent Application No. 61 / 578,658 (Agent Reference Number: J04) The patent application filed on December 21, 2011, is titled "System, method, and apparatus for oral drug administration." U.S. Provisional Patent Application No. 61 / 578,674 (Agent Reference Number: J05); The patent application filed on May 24, 2012, is titled "System, Method and Apparatus for Electronic Patient Care." U.S. Provisional Patent Application No. 61 / 651,322 (Agent Reference Number: J46); and "System, method and U.S. Provisional Patent Application No. 61 / 679,117 for "Apparatus" (Agent Reference Number: J30) Each of the above is incorporated herein by reference in whole. U.S. Patent Application No. 13 / 723,239 claims priority to the following applications, and also the following This is a continuation application in part: A patent application filed on December 21, 2011, for "System, method, and apparatus for electronic patient care" The name is U.S. Patent Application No. 13 / 333,574, which was subsequently published on July 19, 2012. U.S. Patent Application Publication No. 2012-0185267A1 (Agent Reference Number: J97) This application is a US patent application filed on January 21, 2011, titled "Electronic Patient Monitoring System". This was national patent application No. 13 / 011,543, which was subsequently published on December 22, 2011. U.S. Patent Application Publication No. 2011-0313789A1 (Agent Reference Number: I52) This is a continuation application, which is a "Electronic Instruction Intermediation System for Medical Equipment" filed on January 22, 2010. U.S. Provisional Patent Application No. 61 / 297,544, titled "Stem" (Agent Reference Number: H5 Those who claim priority in 3); and A patent application filed on December 21, 2011, for "System, method, and apparatus for electronic patient care" The name is PCT application number PCT / US11 / 66588, and subsequently filed on September 12, 2013. International patent application publication WO2013 / 095459 (agent reference number: I97) published on [date]. WO). Each of these is incorporated herein by reference in whole.

[0004] This application also relates to the application filed on December 21, 2012, "System, method and The U.S. Patent Application No. 13 / 723,242, titled "device," was subsequently filed in 2013. U.S. Patent Application Publication No. 2013-0317753A1 (Agent) published on November 28. This is a continuation application of (Reference No.: J78), and this application claims priority over the following application. : The patent application filed on May 24, 2012, is titled "System, Method and Apparatus for Electronic Patient Care." U.S. Patent Application No. 61 / 651,322 (Agent Reference Number: J46). This is the whole. This is incorporated herein by reference.

[0005] This application also relates to the application filed on May 23, 2013, "System, method and for electronic patient care." The U.S. Patent Application No. 13 / 900,655, titled "Apparatus," was subsequently filed in 2013. U.S. Patent Application Publication No. 2013-0317837A1 (Agent Arrangement) was published on January 28. This is a continuation application of the "Electricity" application filed on May 24, 2012 (Application No.: K66), and this application is a continuation application of the "Electricity" application filed on May 24, 2012. U.S. Provisional Patent Application No. 61 / 651, entitled “System, Method and Apparatus for the Care of Child Patients” Claiming priority in No. 322 (Agent Reference Number: J46), both of these refer to the whole. and is incorporated herein by reference. U.S. Patent Application No. 13 / 900,655 is also a partial continuation application, which claims priority to the following applications : U.S. Patent Application No. 13 / 480,444, filed on May 24, 2012, with the title "Blood Treatment System and Method", and U.S. Patent Publication No. 2013-0037485A1 (Attorney Docket No.: J43), published on February 14, 2013; and PCT Application No. PCT / US12 / 00257, filed on May 24, 2012, with the title "Blood Treatment System and Method", and International Publication No. WO2012 / 161744 (Attorney Docket No.: J43WO), published on November 29, 2012. This application is also a partial continuation application of PCT Application No. PCT / US13 / 42350, filed on May 23, 2013, with the title "Systems, Methods, and Devices for Electronic Patient Care" (Attorney Docket No. : K66WO), which claims priority to U.S. Provisional Patent Application No. 61 / 651,322, filed on May 24, 2012, with the title "Systems, Methods, and Devices for Electronic Patient Care" (Attorney Docket No.

[0006] : J46), and both are incorporated herein by reference in their entirety. PCT Application No. PCT / US13 / 42350 is also a partial continuation application, which claims priority to the following applications: U.S. Patent Application No. 13 / 480,444, filed on May 24, 2012, with the title "Blood Treatment System and Method", and U.S. Patent Publication No. 2013-0037485A1 (Attorney Docket No.: J43), published on February 14, 2013; and PCT Application No. PCT / US12 / 00257, filed on May 24, 2012, with the title "Blood Treatment System and Method", : U.S. Patent Application No. 13 / 480,444, filed on May 24, 2012, with the title "Blood Treatment System and Method", and U.S. Patent Publication No. 2013-0037485A1 (Attorney Docket No.: J43), published on February 14, 2013; and PCT Application No. PCT / US12 / 00257, filed on May 24, 2012, with the title "Blood Treatment System and Method", : It was PCT / US12 / 00257, and was subsequently published on November 29, 2012. International Publication No. WO2012 / 161744 (Agent Reference Number: J43WO).

[0007] This application is also related to one or more of the following patent applications filed on December 21, 2012. This may be done, and all of these are incorporated herein by reference: U.S. Nonprovisional Patent Application No. 13 / 7 relating to "System, method and apparatus for clamping" No. 23,238 (Agent reference number: J47); U.S. Non-Provisional Patent Application No. 13 / 72 relating to "System, method, and apparatus for oral drug administration" No. 3,235 (Agent reference number: J74); PCT Application No. PCT / US12 relating to "Systems, methods, and apparatus for oral drug administration" / No. 71131 (Agent reference number: J74WO); U.S. Nonprovisional Patent Application No. 13 / relating to "System, Method and Apparatus for Estimating Fluid Delivery Volume" No. 724,568 (Agent reference number: J75); U.S. Nonprovisional Patent Application No. 13 / 725,7 relating to "Systems, methods, and apparatus for intravenous fluid administration" No. 90 (Agent reference number: J76); PCT application PCT / US12 / 71 relating to "Systems, methods, and apparatus for intravenous fluid administration" No. 490 (Agent reference number: J76WO); U.S. Non-Provisional Patent for "Systems, Methods, and Apparatus for Monitoring, Regulating, or Controlling Infusion Flow" Application No. 13 / 723,244 (Agent Reference Number: J79); PCT application relating to "Systems, methods and apparatus for monitoring, regulating or controlling infusion flow" No. PCT / US12 / 71142 (Attorney docket number: J79WO); U.S. Nonprovisional Patent Application No. 13 / relating to "System, Method and Apparatus for Estimating Fluid Delivery Volume" Nos. 723,251 (Agent Reference Number: J81); and PCT Application No. PCT / US relating to "System, method, and apparatus for estimating the amount of intravenous fluid delivered". No. 12 / 71112 (Agent reference number: J81WO).

[0008] This application may also relate to one or more of the following patent applications, and all of them The entirety of this is incorporated herein by reference: Application filed December 18, 2012, "System for detecting air in a liquid line using activated rectifier" U.S. Provisional Patent Application No. 61 / 738,447, titled "System, Method and Apparatus" (Agent) Reference number: J32); A US patent application filed on March 15, 2013, entitled "System, method, and apparatus for infusion". Patent Application No. 13 / 840,339 (Agent Reference Number: K14); A PC filed on March 15, 2013, titled "System, method, and apparatus for intravenous fluid administration" T Application No. PCT / US13 / 32445 (Attorney docket number: K14WO); A US patent application filed on March 15, 2013, entitled "Syringe Pump and Related Methods" National Patent Application No. 13 / 833,432 (Agent Reference Number: K21); A US patent application filed on March 15, 2013, entitled "System and Apparatus for Electronic Patient Care" National Patent Application No. 13 / 836,497 (Agent Reference Number: K22); The patent application filed on March 15, 2013, for "System, method and apparatus for clamping" U.S. Patent Application No. 13 / 833,712 (Agent Reference Number: K23) "System, method and U.S. Patent Application No. 13 / 834,030, titled "device" (Agent reference number: K28) ); Application filed July 31, 2013, "A method for detecting bubbles in liquid lines using a split ring resonant circuit." U.S. Provisional Patent Application No. 61 / 860,398, entitled "System, Method and Apparatus" Agent reference number: J31); "System, method and U.S. Provisional Patent Application No. 61 / 900,431 for "device" (Agent reference number: K5 2); The patent application filed on October 23, 2013, entitled "Syringe Pump and Related Methods" U.S. Provisional Patent Application No. 61 / 894,801 (Agent Reference Number: K88); A patent application filed on July 8, 2013, entitled "System, method and apparatus for clamping" U.S. Provisional Patent Application No. 61 / 843,574 (Agent Reference Number: K74); U.S. Patent Application No. 20, filed August 20, 2013, entitled “Electronic Patient Monitoring System” No. 13 / 971,258 (Agent reference number: K84); The patent application filed on November 14, 2013, titled "Syringe Pump and Related Methods" U.S. Provisional Patent Application No. 61 / 904,123 (Agent Reference Number: L33); Application filed December 10, 2013, "Bubble detection in liquid lines using a split ring resonant circuit" U.S. Patent Application No. 14 / 101,848, entitled "System, Method and Apparatus for" Agent reference number: L05); Regarding the "System, Method and Apparatus for Data Communication" filed on December 20, 2013. U.S. patent application (Agent reference number: L49); Regarding the "System, Method and Apparatus for Data Communication" filed on December 20, 2013. PCT application (Agent reference number: L49WO); "Computer-driven method for electronic patient care, filed on December 20, 2013" U.S. patent application relating to "systems and apparatus" (Agent reference number: K50); "Computer-driven method for electronic patient care, filed on December 20, 2013" PCT application relating to "Systems and Apparatus" (Agent reference number: K50WO); and Regarding the patent application filed on December 20, 2013, concerning "System, method, and apparatus for electronic patient care" U.S. patent application (Agent reference number: L52).

[0009] Technical field This disclosure relates to patient care. More specifically, this disclosure relates to a system for electronic patient care. Regarding methods and apparatus. [Background technology]

[0010] Providing patient care in a hospital generally involves many professionals and caregivers (for example) (including doctors, nurses, pharmacists, technicians, nurse practitioners, etc.), and a given patient It requires the interaction of numerous medical devices / systems necessary for treatment. [Overview of the project] [Problems that the invention aims to solve]

[0011] Combining electronic medical records (EMR) and computerized provider instruction entries (CPOE) Despite the existence of systems intended to facilitate care processes such as those already included The process of providing comprehensive care to patients, including ordering and delivering medication and other medical treatments, Several important issues are related. [Means for solving the problem]

[0012] In exemplary embodiments relating to drug ordering and administration, the electronic patient care system is: 1. A data acquisition module (e.g., a monitoring client), which transmits instructions or patient-related information. A second instruction input module having a user interface for receiving information (e.g.) For example, it may include a fixed or portable monitoring client. The system measures the patient's current condition, including blood pressure, heart rate, cardiac rhythm, temperature, oxygenation, respiratory rate, or ventilation. It receives and stores measurement parameters related to a state (e.g., patient state parameters). The first module may also be configured as follows: , other medications currently being administered that are present in the patient's tissues, age, weight, height, kidney or A first database (for example, regarding patients) that includes patient status parameters such as liver function. Information on existing patient-related parameters is obtained from the EHR database (which contains the information). The first module may be configured to receive, for example, blood pressure, pulse, heart rhythm, etc. Alternatively, second data such as known drug interactions related to respiration, drug effects, or existing drugs. Prescribed medications and / or existing medications from a database (e.g., a drug information database). It can also be configured to obtain drug information about medications. The first module is for patients The currently measured patient status parameters and the received existing patient status parameters are known as normal Create a table of patient condition parameters that are found to be outside the normal range after comparing them to the normal range. It can be configured in such a way. The first module then processes the patient status parameters. Compare the bull with a table of corresponding parameters obtained from a drug information database. This is possible. A match can be found between the patient status parameter table and the corresponding parameter table. If it is found that the first module exists, then the second (instruction input) module To communicate to the message, read one or more pre-entered and stored messages. These messages can, for example, specify the prescribed medication, or the patient's existing medications. and include warnings to the user of the second module that are appropriate to the patient's current and existing medical condition. This is possible. In optional mode, the warning is received by the second module, and the warning is sent to the user. Confirmed by the user of the second module via input signals from the interface. This will help avoid further repetition of the warning.

[0013] In other embodiments, the electronic patient care system provides the user with information obtained from a drug information database. Editable default values ​​derived from established standard medication and administration guidelines are provided. It can be provided with the patient's current and existing medical conditions, allergies, existing medications, or other symptoms. Changes that can be indicated based on user status parameters can be alerted to the user. Electronic patient care systems are preferred to minimize the amount of typing required from the user. It's nice.

[0014] In other embodiments, the first module or other modules of the electronic patient care system are Use it at the patient's bedside (e.g., barcode and reader, or RFID tag). Identify the prescribed medication being delivered (through a scanner) and determine the appropriate medication and administration. It is also possible to verify that the quantity has been prepared and delivered to the patient. In one embodiment, The first module also includes an infusion pump or pill dispenser for the patient receiving treatment. It can interact with care devices via wired or wireless communication links. In the case of a pump, the first module or another connecting module controls the injection speed of the injection pump. Alternatively, it provides patient treatment parameters such as injection settings including injection pressure, and from there, for example, The presence of air in the inlet line, the amount of solution remaining in the connected intravenous bag, or It can receive various operating parameters such as the fluid pressure in the injection line. If the meter is found to be abnormal, the first module will signal the injection pump. Responding by sending a signal to interrupt the infusion, mechanically occluding the venous laxative Responding by blocking the inlet, changing the injection rate, and / or the first module Alarms are transmitted directly or to a second module via alarms built into the module. The system is configured to issue an alert to healthcare providers, etc., in case of an anomaly. It is possible. In another embodiment, the first module also monitors the patient's condition, For example, blood pressure monitors, ECG monitors, pulse oximetry monitors, temperature monitors, etc. To communicate with various patient care devices used to determine patient status parameters. It can be configured as follows. Various parameters to be measured are measured by the mobile device and In some cases, monitoring and / or recording can be done within EMR. The first module, when the monitored patient status parameter is outside a predetermined range, It can be programmed to issue an alert to a person or other person. Several embodiments The first module then transmits a signal to the monitoring client, which then connects to the patient care device. Perform unscheduled measurements to obtain other patient status parameters. This is possible. The first module communicates with various healthcare providers in various locations. In one embodiment, the first module can inform the assigned patient of an abnormality. It is possible to implement corrective actions, for example, through audible warnings or recorded messages. I can recommend it.

[0015] In one embodiment, a system for preparing a microinfusion pump monitors Client, pharmacy computer, compounding robot, microinfusion pump, and includes a data download device. The monitoring client is user i The pharmacy computer is configured to communicate prescription instructions via the interface. It communicates with the monitoring client in an operational manner to receive prescription instructions. The compounding robot, It is configured to prepare a prescription into at least one liquid corresponding to the prescription instructions. The microinfusion pump dispenses at least one liquid corresponding to the prescription instructions. It is configured to receive. The data download device will receive prescription instructions. It is configured to download into the memory of the chloroinfusion pump.

[0016] In some embodiments, the compounding robot uses a microinfusion pump with minimal It fills with at least one liquid. The compounding robot works with a data download device. The formulation robot can communicate and download data to the formulation device. Instruct the microinfusion pump to download the prescription instructions into its memory. It may be used. The data download device will provide prescription instructions to the compounding robot and / or Or it can be received from a pharmacy computer. In some embodiments, a compounding robot The system receives prescription instructions from the pharmacy computer.

[0017] In one embodiment of the present disclosure, the system comprises a hub. The hub is a patient care device It is configured to monitor the hub. The hub is (specifically as processor execution software) Operating system components (which can be modified) and (processor actual It includes a sandbox component (which can be materialized as a running software). It is. The operating system components are the hub's hardware resources. Access to at least one of the software resources of the hub and the hub. It is composed of.

[0018] The sandbox component utilizes hardware resources and software resources. The hub is configured to control access to at least one of the sources. It identifies patient care devices, runs applications, and monitors patient care devices. It is further configured to do so. The hub is an app within a sandbox component. The application can run, and this allows the application to run in a sandbox environment. Through the component, a small portion of hardware and software resources Access at least one.

[0019] The hub may be further configured to control patient care devices. The products include infusion pumps, pill dispensers, microinfusion pumps, and ECG monitors. T, blood pressure monitor, pulse oximeter, CO2 capnometer, intravenous bag, and / Alternatively, one or more drip flow meters may be used.

[0020] The hub retrieves identification information (e.g., serial number, encrypted data) from patient care devices. It receives an unencrypted code, or other identification value, and associates it with the identification information. It may also be configured to download applications from a server. It receives identification information from the patient care device and retrieves data from the server associated with the identification information. The application may be configured to update.

[0021] Hardware resources include disk drives, memory, buzzer, microphone, It may also be a speaker and a camera. Software resources are variables, secure Data objects, secure variables, protected APIs, APIs and hardware. It may also be one of the software representations of a component.

[0022] In yet another embodiment, the electronic patient care system includes a hub. The hub is It is configured to monitor patient care devices. The sandbox is hardware-based. Control access to at least one of the following: resources and software resources. It can be configured to do the following: The hub identifies patient care devices and applications The hub is further configured to run and monitor patient care devices. The application runs within the box component, thereby the application The system uses hardware resources and software through the sandbox component. Access at least one of the shared resources. The hub controls patient care devices. It may be further configured to control. The hub receives identification information from the patient care device. Furthermore, to download the application from the server associated with the identification information It may be configured as follows: The hub receives identification information from the patient care device and associates the identification information with It may also be further configured to update applications from the attached server.

[0023] Hardware resources include disk drives, memory, buzzer, microphone, It may also be a speaker and a camera. Software resources are variables, secure Data objects, secure variables, protected APIs, APIs and hardware. It may also be one of the software representations of a component.

[0024] In yet another embodiment, the system for electronic patient care includes a monitoring client. The monitoring client is configured to monitor patient care devices. Ianto provides hardware resources for monitoring clients and software for monitoring clients. Operator configured to access at least one of the software resources It has a sandbox system component. The sandbox component is For at least one of hardware resources and software resources It is configured to control access. The monitoring client recognizes the patient care device. In addition, the application is further configured to run and monitor patient care devices. The monitoring client may also apply within the sandbox component. This executes, thereby allowing the application to use the sandbox component. Access to at least one of the following: hardware resources and software resources. The monitoring client is further configured to control patient care devices.

[0025] Patient care devices include infusion pumps, pill dispensers, and microinfusion pumps. Pumps, ECG monitors, blood pressure monitors, pulse oximeters and / or CO2 capnometers It may also be a drip bag, an intravenous bag, and a drip flow meter.

[0026] The monitoring client receives identification information from the patient care device and associates it with the identification information. It may be further configured to download the application from the server. The visual client receives identification information from the patient care device and associates the identification information with It may also be further configured to update applications from the server.

[0027] Hardware resources include disk drives, memory, buzzer, microphone, It may also be a speaker and a camera. Software resources are variables, secure data Data objects, secure variables, protected APIs, APIs and hardware controls It may also be a software representation of the component.

[0028] In yet another embodiment, the system for electronic patient care monitors the patient care device. It has a monitoring client configured as follows. The monitoring client is hardware-based. Control access to at least one of the following: resources and software resources. It features a sandbox component configured for monitoring clients. It identifies patient care devices, runs applications, and monitors patient care devices. It may be further configured to do so. The monitoring client is a sandbox component. The application runs within the sandbox, thereby allowing the application to be used in a sandbox environment. Through the components, hardware resources and software resources Access at least one. The monitoring client controls the patient care device. It may be further configured as follows.

[0029] Patient care devices include infusion pumps, pill dispensers, and microinfusion pumps. Pumps, ECG monitors, blood pressure monitors, pulse oximeters and / or CO2 capnometers It may also be a drip bag, an intravenous bag, and a drip flow meter.

[0030] The monitoring client receives identification information from the patient care device and associates it with the identification information. It may be further configured to download the application from the server. The visual client receives identification information from the patient care device and associates the identification information with It may also be further configured to update applications from the server.

[0031] Hardware resources include disk drives, memory, buzzer, microphone, It may also be a speaker and a camera. Software resources are variables, secure data Data objects, secure variables, protected APIs, APIs and hardware controls It may also be one of the software representations of the component.

[0032] In another embodiment, the system for electronic patient care is configured to communicate with an electronic medical record. It comprises a hub and patient care devices. The hub connects the patient and patient care devices ( For example, it is configured to identify an infusion pump. The hub also extracts less data from the electronic medical record. At least one treatment parameter (e.g., the injected drug and / or the injection rate or speed) Download (such as degree profiles) and patient care data with at least one treatment parameter. The vice is configured to be programmed. The hub uses an RFID caller to transmit RF Reading ID tags and using voice recognition software integrated into the microphone. Voice, face recognition software combined with camera, biometric readings Biometric parameters, identification information, and barcode reading by a barcode reader. Identify the patient according to at least one of the following: In one particular embodiment, hub This involves using one or more of the identification techniques described herein to determine at least one therapeutic parameter. You can download the file.

[0033] In another embodiment, the system for electronic patient care is configured to communicate with an electronic medical record. It includes a monitoring client and a patient care device. The monitoring client is patient It is also configured to identify patient care devices (e.g., infusion pumps). The client also needs at least one treatment parameter (e.g., infusion medication) from the electronic medical record. Download the object and / or injection rate or rate profile, etc. Both are configured to program patient care devices with a single treatment parameter. The monitoring client reads the RFID tag using an RFID caller, micro Voice using voice recognition software integrated into the phone, and face recognition software integrated into the camera. Face using software, biometric parameters for biometric reading, According to at least one of the following: identification information or barcode reading by a barcode reader. To identify the patient. In one particular embodiment, the monitoring client is as described herein. Download at least one treatment parameter using one or more of the following identification technologies. It is possible.

[0034] In yet another embodiment, the system for electronic patient care includes a monitoring client and a monitoring client. The device includes an Iant Dock, patient care devices, and a device dock. Ant is configured to communicate at least one patient care parameter. Monitoring The client dock is used to dock the monitoring client to the patient. It is configured to receive a patient care device. It is configured to communicate patient care parameters. The device dock is configured to communicate patient care devices. The chair is configured to receive patient care devices in order to dock there. .

[0035] In one embodiment, the monitoring client dock and the device dock are wirelessly connected. and cables operably coupled to the monitoring client dock and device dock. It is configured to communicate in one direction through the other.

[0036] In another embodiment, the monitoring client wirelessly transmits at least one patient care parameter. It is configured to communicate using [this method].

[0037] In another embodiment, the monitoring client dock communicates wirelessly with the monitoring client. It is configured such that the monitoring client monitors at least one patient care parameter. The client can connect to the dock wirelessly, via cable, or to the docked patient. By communicating with the caregiver's device, it enables operational communication with the patient's care device.

[0038] In another embodiment, the monitoring client is unable to communicate via cable. And the monitoring client has been undocked from the monitoring client dock. When the monitoring client determines that at least one of the following is true, the monitoring client dot Using wireless communication with the system, at least one patient care parameter is communicated in an operable manner. .

[0039] In another embodiment, the device dock is configured to communicate wirelessly with the monitoring client. The monitoring client communicates wirelessly with the device dock to at least one By sending patient care parameters to the docked patient care device, patient care Communicates with the protection device in an operational manner.

[0040] In another embodiment, the monitoring client is one for which communication via cable is unavailable. Communication between the monitoring client and the monitoring client dock is unavailable, and monitoring Among the cases where a viewing client was undocked from the monitoring client dock, When the monitoring client determines that both are the same, wireless communication with the device dock is initiated. It is used to enable communication of at least one patient care parameter.

[0041] In another embodiment, the patient care device is configured to communicate wirelessly with a monitoring client. The monitoring client has set at least one patient care parameter to the patient care device. It communicates wirelessly with the chair.

[0042] In another embodiment, the monitoring client is one for which communication via cable is unavailable. Communication between the monitoring client and the monitoring client dock is unavailable. • Communication between the dock and patient care devices is unavailable, and the monitoring client is At least one of the following is: the monitoring client has been undocked from the dock. When the monitoring client determines, at least one patient will be contacted wirelessly by the patient care device. Communicate care parameters in an operable manner.

[0043] In another embodiment, the monitoring client dock and the device dock are at least It is configured to communicate one patient parameter wirelessly. The system further monitors Equipped with cables operably coupled to the client dock and device dock. The monitoring client dock and device dock are the device dock, monitoring At least one of the Ryandock and Surveillance clients has a cable that is a communication link. It is configured to communicate wirelessly when it determines that it is not available for use as a wireless device.

[0044] In another embodiment, the monitoring client connects to patient care devices via multiple communication links. It is configured to communicate with, and the monitoring client is one of several communication links. Communicate through whatever means possible.

[0045] In another embodiment, the patient care device includes an infusion pump, a pill dispenser, and a micro- Infusion pump, ECG monitor, blood pressure monitor, pulse oximeter, CO2 monitor It is one of a phnometer, intravenous bag, and infusion flow meter.

[0046] In another embodiment, patient care parameters include intravenous pump flow parameters and ECG parameters. Meters, blood pressure parameters, pulse oximeter parameters, CO2 capnometer parameters At least one of the following: lap time, intravenous bag parameters, and infusion flow meter value. Care parameters may also be patient status parameters and / or patient treatment parameters. stomach.

[0047] In another embodiment, the patient care device acts as a node in a mesh network wirelessly. It is configured to communicate.

[0048] In another embodiment, the cable moves between the monitoring client dock and the device dock. The patient care device is docked to the device dock and monitored by a hygrometer. When Ant is docked to the monitoring client dock, the monitoring client , communicate at least one patient care parameter to the patient care device via cable. It is structured in this way.

[0049] In yet another embodiment, the system for electronic patient care includes a monitoring client and patient care It includes a device and a device dock. The monitoring client has at least one It is configured to communicate patient care parameters. The patient care device is at least It is configured to communicate one patient care parameter. The device dock is configured to communicate with the patient The patient care device is received and the care device is docked there, and the monitoring client It is configured to receive monitoring clients in order to dock there.

[0050] In yet another embodiment, the system for electronic patient care includes at least one patient care package A patient care device configured to communicate a lameter, and at least one patient care device A monitoring client configured to communicate with the meter, and a patient care device there Equipped with a device dock configured to receive patient care devices for mounting. The device dock and monitoring client are integrated together.

[0051] In yet another embodiment, the system for electronic patient care includes at least one patient care package A stackable monitoring client configured to communicate with Lameter, and at least one A stackable patient care device configured to communicate one patient care parameter and It features a stackable monitoring client and stackable patient care devices. via daisy-chain communication links and / or using a backplane, At least one patient care parameter may be communicated.

[0052] In yet another embodiment, the system for electronic patient care includes at least one patient care package A patient care device configured to communicate a lameter, and at least one patient care device A hub client configured to communicate with LaMeter and patient care devices there A device dock configured to receive patient care devices for docking It is equipped with the necessary components. The hub is plugged into the device dock to establish a communication link between the two. The system can also include a monitoring client that can communicate with the hub in an operable manner. Patient care parameters may receive at least one patient care parameter. Patient treatment parameters are hub The hub can communicate in an operable manner and transmit patient treatment parameters to patient care devices. To communicate.

[0053] In certain embodiments, the hub may include a user interface, and the hub may be patient User authentication may be required before transmitting treatment parameters to the patient care device.

[0054] In certain embodiments, the monitoring client may include a user interface. The monitoring client transmits patient treatment parameters to the patient care device through the hub. Before proceeding, user authentication may be required.

[0055] In certain embodiments, the patient care device may include a user interface. The patient care device requires user authentication of patient treatment parameters before treating the patient. You may do so.

[0056] The hub can be configured to monitor patient care devices. In certain embodiments, The hub is connected to at least one of the hardware resources and software resources. Even with a sandbox component configured to control access to it good.

[0057] The hub further identifies patient care devices and runs applications to enable patient care data It can be configured to monitor the vice. The hub is a sandbox component. Applications can run within the sandbox, which allows the application to run within the sandbox. Hardware resources and software resources through box components Access at least one of the S's.

[0058] In another embodiment, the system for electronic patient care includes: at least At least one patient monitor adapted to monitor one patient parameter; less It communicates with at least one patient monitor and controls at least one patient parameter. A monitoring client that receives from; and communicates with the monitoring client in an operable manner, and monitors A monitoring server that receives at least one patient parameter from a client.

[0059] In another embodiment, the system further communicates operably with at least one patient monitor. The system may also include a remote communicator that receives at least one patient parameter.

[0060] At least one patient monitor must be an electrocardiogram monitor, blood pressure monitor, or pulse oximeter. It may be equipped with at least one of a monitor and a CO2 capnometer. The system is configured to download patient information according to a specified unique patient identifier. It is possible. A unique patient identifier is recorded on the barcode placed on the wristband. It can be coded. A unique patient identifier is an RFID tag attached to the wristband. It can be coded on a device (for example, an RFID caller). Patient information is also available, including the patient's condition. This includes patient care parameters. A unique patient identifier is transmitted to the monitoring server in an operable manner. This allows for electronic authorization to communicate patient-specific data. A subset of may be stored in the monitoring client's memory. The monitoring client is , a predetermined criterion based on a subset of patient-specific data stored in memory for new instructions It may be adapted to determine whether the condition is met.

[0061] In another embodiment, the system further presents new instructions to the monitoring client. It features a portable monitoring client that conforms to the requirements. Monitoring client and / or At least one of the remote communicators is suitable for communicating new instructions to the monitoring server. Even if combined, the monitoring server will determine whether the new instructions meet other predetermined criteria. It may be adapted to be fixed.

[0062] In another embodiment, the new instruction may be a drug instruction, and the monitoring server will control the drug By determining whether the instruction is contraindicated with the currently prescribed medication, a new instruction can be made. The monitoring server may be adapted to determine whether it meets other predetermined criteria. It communicates with the database to determine whether the new instructions meet other predetermined criteria. It is possible. The monitoring server will, when a new instruction does not meet another predetermined criterion, It may be configured to send alerts to monitoring clients.

[0063] In another embodiment, the system comprises at least one monitoring client and monitoring server. It can be equipped with remote communication adapted to enable communication with the system.

[0064] In another embodiment, the monitoring client is a desktop-based device, a portable device Vices, handheld controllers, notebook PCs, netbooks, tablet PCs , and may also be one of the smartphones. The monitoring client has a touchscreen. They are prepared.

[0065] In another embodiment, the system may further include an injection pump and a monitoring client. The system communicates with the injection pump in an operational manner. The injection pump can be attached to the monitoring client. It may be possible. The injection pump may be detachable from the monitoring client.

[0066] In another embodiment, the system further docks a monitoring client to the injection pump. It is equipped with a dock that is configured to accommodate this.

[0067] In another embodiment, the monitoring client can operate with the injection pump via a wireless link. To communicate.

[0068] In another embodiment, the monitoring server is configured to communicate with multiple databases. Furthermore, at least one of the multiple databases contains data from another of the multiple databases. Includes data formats or communication protocols different from the base.

[0069] In another embodiment, the monitoring server formats data from multiple databases. The data is then adapted to be downloaded to the monitoring client. (Optional) In some specific embodiments, the monitoring client also monitors at least one patient. The parameters may be communicated to the monitoring server. In certain embodiments, patient parameters are injectable. Progress of pump treatment, electrocardiogram signals, blood pressure signals, pulse oximeter signals, One or more of the following: CO2 capnometer signal and / or temperature signal. It can include a name and / or at least one of these.

[0070] In another embodiment, the monitoring server sends operational instructions to the injection pump via the monitoring client. It may be configured to be downloaded.

[0071] The monitoring client can receive user requests and read patient parameters. Furthermore, it can query monitoring devices to receive patient parameters.

[0072] In another embodiment, the system may further include a portable monitoring client. The portable monitoring client communicates with the monitoring client in an operational manner to directly obtain patient information. It may communicate directly with the monitoring server, thereby bypassing it. Portable monitoring client This modifies at least one parameter of the injection pump, and at least one of those parameters is changed. The parameters may be configured to be communicated to the monitoring server.

[0073] Changes to patient instructions presented via the portable monitoring client are handled by another portable monitoring client. This can be communicated to the client.

[0074] In another embodiment, the monitoring client periodically uploads information to the monitoring server. It is configured to be stored in a patient-specific database.

[0075] The system is further adapted to receive information from a patient-specific database. It can be equipped with a monitoring client.

[0076] Information includes patient instructions, patient medication, progress notes, monitoring data from patient monitors, and It may include at least one piece of treatment data from the attached device.

[0077] The monitoring server queries the electronic health record database and retrieves patient information from there. It can be configured in such a way. The monitoring server further sets a predetermined set according to the patient information. This information can be configured to be input to the monitoring client.

[0078] The information in the specified set includes the patient's age, height, weight, diagnosis, current medications, and medication category. It may include at least one of drug allergies and hypersensitivity reactions.

[0079] In another embodiment, the remote portable monitoring client communicates with the monitoring server via the monitoring client. It is adapted to communicate with Ianto. The remote portable monitoring client is a tablet. It may be a netbook or PC. Remote portable monitoring client The device can be equipped with a touchscreen.

[0080] In another embodiment, the method for electronic patient care includes the following steps: multiple steps on a display The process of displaying patients; associating one of several patients on the display. A step of displaying at least one patient parameter; associated with the patient on the display. A step of displaying at least one warning; and a step of selecting the patient from a group of patients. Approximately.

[0081] In some specific embodiments, the above method allows the monitoring client to access the display. The process further includes transmitting alerts to a portable remote communicator device. That's fine.

[0082] In yet another embodiment, the electronic patient care system includes: at least one A monitoring client configured to communicate patient care parameters; at least one A patient care device configured to communicate patient care parameters; and at least one The presence of a patient care device was discovered, and the communication signal from that device was monitored by a client. By converting to the communication protocol associated with the client, the monitoring client and fewer A communication interface configured to facilitate communication between at least one patient care device. Face.

[0083] In certain embodiments, the communication interface may further include additional other patient-related interfaces that are different from each other. The system detects the presence of security devices and monitors the communication signals from these devices to the monitoring client. It is configured to convert to the associated communication protocol.

[0084] In another specific embodiment, the communication interface further provides a power supply suitable for each device. It is configured to provide. In yet another specific embodiment, the system further provides the patient Accessible by a monitoring client that takes into account at least one of the central storage locations of user information. One or more databases capable of monitoring patients associated with the monitoring client. It includes downloadable information that can be used for treatment.

[0085] In yet another specific embodiment, the communication interface further comprises at least one of the following: It is configured to perform fault checks for: communication with patient care devices. Evaluate data integrity; assess whether monitoring clients are functioning correctly; Evaluate whether patient care devices are functioning properly; and / or communication interfaces Evaluate whether the clubface is functioning correctly.

[0086] In yet another embodiment, the electronic patient care system includes: at least one A hub client configured to communicate patient care parameters; at least one A patient care device configured to communicate patient care parameters; and at least The presence of one patient care device was discovered, and the communication signals from that device were associated with the hub. By converting to the attached communication protocol, the hub and at least one patient care device A communication interface configured to facilitate communication with the device.

[0087] In certain embodiments, the communication interface may further include additional other patient-related interfaces that are different from each other. The system detects the presence of a protective device and records the communication signals from that device to the hub. It is configured to convert to the communication protocol.

[0088] In another specific embodiment, the communication interface further provides a power supply suitable for each device. It is configured to provide. In yet another specific embodiment, the system further provides the patient One or more accessible by a hub that takes into account at least one of the central memory locations for user information. It can be used to treat patients associated with the database and / or hub. It includes download information.

[0089] In yet another specific embodiment, the communication interface is further at least one of the following: It is configured to perform fault checks for: communication with patient care devices Evaluate data integrity; assess whether monitoring clients are functioning properly; treat Evaluate whether the care device is functioning properly; and / or communication interface Evaluate whether the face is functioning properly.

[0090] In yet another embodiment, the electronic patient care system includes: at least one A dock configured to communicate patient care parameters; at least one patient care A patient care device configured to communicate care parameters; and at least one patient The presence of a caregiving device was discovered, and the communication signal from that device was associated with the dock. By converting to a standard communication protocol, the dock and at least one patient care device A communication interface configured to facilitate communication between devices.

[0091] In certain embodiments, the communication interface may further include additional other patient-related interfaces that are different from each other. The presence of a protective device was discovered, and the communication signal from that device was associated with the dock. It is configured to convert to a communication protocol.

[0092] In another specific embodiment, the communication interface further provides a power supply suitable for each device. It is configured to provide. In yet another specific embodiment, the system further provides the patient One or more accessible by the dock, taking into account at least one of the central memory for user information The above database and / or can be used to treat patients associated with the checkup. It includes download information.

[0093] In yet another specific embodiment, the communication interface is further at least one of the following: It is configured to perform fault checks for: communication with patient care devices Evaluate data integrity; assess whether monitoring clients are functioning properly; treat Evaluate whether the care device is functioning properly; and / or communication interface Evaluate whether the face is functioning properly.

[0094] In one embodiment, the patient care device comprises: a main body; and a support column. A conduit within the main body, which is connected to the main body and locks the main body to the support column by friction within the conduit. Two friction members configured to perform the following actions.

[0095] In one embodiment, the hub includes: a patient care device interface. ;Connects to patient care device interfaces and supplies power to patient care devices. A power supply; a processor; and communication between the processor and the patient care device, all configured to do so. Trans coupled to a patient care device interface configured to enable The processor, in some specific embodiments, when an alarm state is in place, The care device may be configured to be disabled.

[0096] In one embodiment, the dock includes: patient care device interface S; coupled to a patient care device interface, and supplies power to the patient care device. A power supply; a processor; and communication between the processor and the patient care device, configured to do so. Trap coupled to a patient care device interface configured to enable trust The processor, in some specific embodiments, when it is in an alarm state, The patient care device may be configured to be disabled.

[0097] In one embodiment, the communication module includes: patient care device interface -Face; coupled to patient care device interface, powering the patient care device Power supply configured to supply; processor; and patient care devices and other devices A patient care device interface configured to enable communication with a chair. Coupled transceivers. The processor, in some specific embodiments, is an alarm state. The patient care device may be configured to be disabled if it is in this state.

[0098] In another embodiment, the patient care system includes: a dock; docking to the dock. Multiple modular patient care devices configured for grouping; and monitoring clients. Retractable display. Modular patient care devices, staggered or connected. The dock and interface connection may be made along the horizontal plane via this.

[0099] In yet another embodiment, the electronic patient care system receives and records information about the patient. A first module configured to store the information on a device connected to the patient. Data related to the patient's first parameter measured by the system, and information about the patient. Includes data related to the patient's second parameter received from the first database, which includes reports. The first module and the user interface associated with the second module It is configured to receive drug instructions from the user via a first module, and further configures the treatment instructions to It comprises a second module configured to transmit to the first module Furthermore, a) drug information regarding the drug or other drugs from a second database There are drugs that include data providing limitations on when such drugs are generally administered. a) obtaining information, drug instructions, drug information, the value of the first parameter, and the second Based on the parameter values, the second module (in this particular embodiment) confirms: Determining whether it is necessary, and c) displaying it on the user interface. To do this, a predetermined message is transmitted from the first module to the second module. This means that the message confirms the acceptability of the drug instruction, or relating thereto It is designed to warn, to communicate, and to deliver information.

[0100] Drug information includes drug interaction information, drug allergy information, blood pressure effect information, and heart rate information. Information on usage, cardiac rhythm, or respiratory function can be cited, and the first parameter or The second parameter is the medications the patient is currently taking, known drug allergies, Data regarding current blood pressure, current heart rate, current rhythm, current respiratory rate, or current tidal volume. Includes data.

[0101] The predetermined message must include a warning about the potential effects of the prescribed medication. This can be done, and the warning will be issued based on the measured data for the first parameter and the second parameter. This includes received data or drug information obtained by the first module.

[0102] The first module, after a predetermined message has been transmitted, and the user Confirmation signal from the second module, initiated by an input signal from the interface. After receiving the drug order, the drug order or modified drug order will be processed. It may be configured to generate signals.

[0103] In another embodiment, the patient care device has a first communication link and a second communication link. is provided, and the dock includes a first communication link and a second communication link. When the patient care device is within a predetermined range from the dock, the patient care device and the dock are paired using the first communication link, and after pairing, they maintain a state where they can communicate using the second communication link. The pairing performed using the first communication link may be to pair the patient care device and the dock with respect to the second communication link. The first communication link may be short-range wireless communication, and the second communication link may be Bluetooth, Bluetooth Low Energy, WiFi, or other communication links. In another embodiment, the patient care device includes a first communication link and a second communication link, and the monitoring client includes a first communication link and a second communication link. When the patient care device is within a predetermined range from the monitoring client, the patient care device and the monitoring client are paired using the first communication link, and after pairing, they remain communicating using the second communication link. The pairing that occurs using the first communication link can pair the patient care device and the monitoring client with respect to the second communication link. The first communication link may be short-range wireless communication, and the second communication link may be Bluetooth, Bluetooth Low Energy, WiFi, or other communication links.

[0104] In some embodiments, the patient care device includes a memory in which a user interface template is stored. The user interface template

[0105] ​ , communicate with docks, hubs and / or monitoring clients, docks, hubs and / or This can be displayed on the user interface of the monitoring client. The interface template is a set of one or more patient care packages received from a patient care device. The parameters may be configured to be displayed (for example, in real time).

[0106] In yet another embodiment, the injection pump includes attachable electronic components. Yes. Installable electronic components include at least one processor, power regulator. It is equipped with a meter and a control system.

[0107] In one embodiment, the communication module includes at least one processor and a transceiver A device comprising a battery and one or more power supply units, providing at least one of communication capabilities and power supply. We provide patient care devices.

[0108] In yet another embodiment, the wearable system monitor is a watchdog controller. It is equipped with a port and transceiver. The wearable system monitor is a watch Equipped with a processor coupled to the crossdog component and transceiver, with fewer It can provide watchdog functionality for at least one paired device. Yes. Paired devices include docks, hubs, monitoring clients and / or patient It may be at least one of the care devices for the person.

[0109] In yet another embodiment, the method includes one or more of the following steps: patient care device and monitoring The process of establishing a communication link with the monitoring server; communicating patient care parameters to the monitoring server. The process of de-identifying patient care parameters; and / or de-identifying them within the monitoring server. A process for storing standardized patient care parameters.

[0110] In yet another embodiment, the method includes one or more of the following steps: monitoring a server and multiple patients The process of establishing a communication link between multiple patient care devices associated with a person; multiple patients The process of communicating patient care parameters from multiple patient care devices to a monitoring server; patient care Process to de-identify parameters; process to store patient care parameters in the monitoring server; multiple The process of treating patients; and multiple patient care parameters associated with multiple patients The process of analyzing a subset to determine the effectiveness of a treatment.

[0111] In yet another embodiment, the patient care device (e.g., infusion pump) is a dock, hub and / or hot-swappable in at least one of the monitoring client connections ru.

[0112] In yet another embodiment, a hot-swappable patient care device, such as an infusion pump, is used. A method comprising one or more of the following steps: one associated with a patient care device The process of receiving the above patient care parameters; one in the non-volatile memory of the patient care device The process of storing the above patient care parameters; one or more patient care parameters in the active memory A step of loading parameters; and a step of restarting the operation of the patient care device. The method In an additional embodiment, the step of determining that the operation of the patient care device can be resumed. It may include.

[0113] In yet another embodiment, a hot-swappable patient care device, such as an infusion pump, is used. A method having [the following] includes one or more of the following steps: calculating one or more operating parameters associated with a patient care device; storing one or more operating parameters in a non-volatile memory of the patient care device; loading one or more operating parameters into the operating memory; and resuming operation of the patient care device. The method may, in an additional embodiment, include the step of determining that operation of the patient care device can be resumed.

[0114] In yet another embodiment, the pairing method includes the following steps: placing a hub having a monitoring client and / or a user interface within the operating range of a patient care device (e.g., an infusion pump); displaying identification information of the patient care device on the user interface; selecting the patient care device for pairing using the user interface; pairing the patient care device with the monitoring client and / or with the hub; and / or communicating patient care parameters to the monitoring client and / or the hub. In yet another embodiment, and optionally, the method includes the step of operably communicating additional patient care parameters through the patient care device to another patient care device and communicating same, for example, to the monitoring client and / or the hub.

[0115] In yet another embodiment, the method includes the following steps: docking the patient care device in a dock; identifying the patient care device; querying a server for an application for controlling the patient care device; and transferring the application to the dock, the hub, and ​​​ / or the process of downloading into the monitoring client; dock, hub, and / or monitoring The process of running the application using a visual client; and the application A process of using a patient care device to control it.

[0116] In yet another embodiment, the method enables patient care devices to communicate operably with a hub. The process includes the step of arranging, and the hub can identify patient care devices and patient care data The application for controlling the device can query the server, and the application You can download the application into the hub and run it. And the patient care device can be controlled using the application.

[0117] In yet another embodiment, the method enables the patient care device to communicate with the dock in an operable manner. The process includes arranging the dock so that it can identify patient care devices and patient care The application for controlling the protective device can query the server, and the application You can download the application into the dock and run the application. It is possible to control patient care devices using the application.

[0118] In yet another embodiment, the method enables a patient care device to operate with a monitoring client. The process includes arranging for communication, and the monitoring client identifies the patient care device. It can query the server for applications to control patient care devices. It is possible to download the application to the monitoring client, and the app It can perform communications and use the application to perform patient care devices It can control the situation.

[0119] In yet another embodiment, the method may include the following steps: Use of a communication device The process of presenting a request on the interface; the process of confirming the request; the process of sending the request. The process; the process of receiving the request with a check value; and the process of confirming that the check value conforms to the request before transmission. The process of confirming that.

[0120] In yet another embodiment, the hub is a dock for receiving patient care devices and another patient At least one connected to an open door, configured to receive a care device It is equipped with a connector.

[0121] In yet another embodiment, the hub controls and / or monitors patient care devices. Therefore, at least one of the following: electronic medical records, DERS, CPOE and / or the internet It communicates in an operational manner.

[0122] In another embodiment, the hub is adapted to connect to a cradle, and the cradle Control one or more coupled patient care devices.

[0123] In yet another embodiment, the battery pack is a patient care device interface. , a battery, and a device configured to use the battery to power a patient care device. It is equipped with a power supply. In some embodiments, the battery is recharged using a DC power supply. It is possible.

[0124] In one embodiment, the patient care device includes a screen and an accelerometer. The patient care device displays the screen in an upright position determined using an accelerometer. It is composed of sea urchin.

[0125] In yet another embodiment, the electronic patient care system includes a monitoring client and a support column. It has a dock configured to connect. The adapter may be connected to the dock. The adapter includes at least one electronic coupler and monitors the patient care device with a climate. The patient care device can be positioned to communicate with the device in an operable manner. You can slide it to that position.

[0126] In yet another embodiment, the electronic patient care system includes a monitoring client and a patient care device. It includes a chair and a communication module. Patient care device and / or communication module The system is fault-tolerant for monitoring clients. For example, the monitoring client is It is not possible to instruct patient care devices to perform unsafe actions.

[0127] For the purposes of the embodiments described below, the base refers to a medical device, dock, or cradle. Hubs, pill dispensers, syringe pumps, infusion pumps, microinfusions • Pump, communication module, ECG monitor, blood pressure monitor, pulse oximeter, CO2 Capnometers, communication relays, etc., may also be used.

[0128] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method involves determining whether the monitoring client is connected to the base via a physical connection. The process involves establishing a communication link between the monitoring client and the base through the physical connection. The process involves, if necessary, monitoring the client and the base via the first communication link. The process of updating the interface program involves using the first communication link to monitor the client. The process of establishing a second communication link between the base and the terminal, and using the second communication link This includes the process of communicating data from the base to the monitoring client.

[0129] In another embodiment, this is achieved by an operable set of processor-executable instructions. This method is used when the processor is located on the monitoring client.

[0130] In another embodiment, this is achieved by an operable set of processor-executable instructions. This method is used when the processor is located on the base.

[0131] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method involves using a second communication link to communicate data from the base to the monitoring client. The act uses a second communication link to monitor the data on the client. This is done when the process includes sending the data to a third party.

[0132] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method involves using a second communication link to communicate data from the base to the monitoring client. The action is performed so that the data is received by the monitoring client using the second communication link. This is performed when the process includes a step that is performed by [a specific method / step].

[0133] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method involves displaying the data to the monitoring client according to the data communicated from the base. Further steps are included.

[0134] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method further includes the step of initializing the patient's treatment using a monitoring client.

[0135] In another embodiment, the process of initializing patient treatment using a monitoring client is further... The method, which includes, is achieved by an operable set of processor-executable instructions, This also includes the process of treating patients using the base.

[0136] In another embodiment, the process of initializing patient treatment using a monitoring client is further... The method, which includes, is achieved by an operable set of processor-executable instructions, This also includes the process of treating patients using a hemodialysis system as a base.

[0137] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method includes the step of the monitoring client sending an initiation treatment signal to the base.

[0138] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method further includes the step of removing the physical connection between the monitoring client and the base.

[0139] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method further includes the step of removing the physical connection between the monitoring client and the base, Furthermore, the process of continuing communication between the monitoring client and the base using a second communication link is also performed. It also includes.

[0140] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method further includes the step of removing the physical connection between the monitoring client and the base, Furthermore, the process of continuing communication between the monitoring client and the base using a second communication link is also performed. The method further includes a step of monitoring the link quality value of the second communication link.

[0141] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method is as long as the link quality value exceeds a predetermined threshold between the monitoring client and the base. This further includes the process of communicating data.

[0142] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method involves, when the link quality value falls below a first predetermined threshold, the monitoring client is shut down. This further includes a process to enter a state where lean indication is not present.

[0143] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method involves, when the link quality value falls below a first predetermined threshold, the monitoring client is shut down. The process further includes a step to put the system into a state where the lean display is not available, in which case the monitoring client will A message will be displayed in the user interface in response to the absence of a clean display.

[0144] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method involves, when the link quality value falls below a first predetermined threshold, the monitoring client is shut down. This process includes entering a state where the lean display is not shown, and in that case, a message is sent to the user monitoring the cloud. I instructed them to make it more like the Ianto base.

[0145] In another embodiment, a monitoring client is monitored when the link quality value falls below a first predetermined threshold. The process includes the step of putting the device into a state where there is no screen display, and the operation of processor-executable instructions. The method, achieved by a single set of capable devices, involves measuring the quality value of each link at regular intervals. The process involves determining whether each of the link quality values ​​exceeds a first predetermined threshold. It also includes.

[0146] In another embodiment, a monitoring client is monitored when the link quality value falls below a first predetermined threshold. The process includes the step of putting the device into a state where there is no screen display, and the operation of processor-executable instructions. The method achieved by a single set of capabilities is when the link quality value exceeds a first predetermined threshold. The process further includes the step of leaving the screen display as it is.

[0147] In another embodiment, a monitoring client is monitored when the link quality value falls below a first predetermined threshold. The process includes the step of putting the device into a state where there is no screen display, and the operation of processor-executable instructions. The method achieved by a single set of capabilities is when the link quality value is greater than a first predetermined threshold. If the predetermined threshold in 2 is exceeded, the process of leaving the screen display off is performed. It also includes.

[0148] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method involves, if necessary, using the interface on the monitoring client via the first communication link. This includes updating the program, and such action is monitored via the first communication link. The process of communicating the version number of the interface program from Ant to Base, monitoring A process to determine whether the interface program on the client is the latest version. Then, the latest version of the interface program from the server is imported based on the base. The process and the interface program are updated to the latest version of the interface program. This process includes overwriting with a new file.

[0149] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method involves using the first communication link to establish a second communication link between the monitoring client and the base. The act of establishing a link determines whether the base is paired with another monitoring client. This process may interrupt the pairing between the other monitoring client and the base if necessary. The process of creating a configuration file using the base, and the process of sending the configuration file to the first communication link The process of communicating from the base to the monitoring client using a link, and the configuration received from the base. The process involves reading files by the monitoring client, and the monitoring client setting up a base for wireless communication. Pair with Iant and, according to the configuration file, between the monitoring client and the base This is performed if it includes the step of establishing a second communication link.

[0150] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method involves monitoring the client on a screen display when the link quality value falls below a predetermined threshold. The process of entering a state where there is no indication interrupts data communication between the base and the monitoring client. A message requesting that the process and users be brought closer to the monitoring client. This includes the step of displaying the page in a graphical user interface.

[0151] In another embodiment, this is achieved by an operable set of processor-executable instructions. The method involves setting the base to a state where there is no screen display when the link quality value falls below a predetermined threshold. The process of putting it into state, the process of interrupting data communication between the base and the monitoring client, and This includes a step of indicating that the base has entered a state where there is no screen display.

[0152] In another embodiment, processor execution is configured to be performed by the processor. The method, achieved by an operable set of possible instructions, is such that the link quality value is a predetermined threshold As long as it exceeds the limit, the process of communicating data between the monitoring client and the base, link quality The process in which the screen display is turned off when the value falls below a predetermined threshold, the link quality value The process remains in a state where there is no screen display as long as the link quality value is below a predetermined threshold. A work procedure to determine whether the value returns to above a predetermined threshold, and if the link quality value returns to above a predetermined threshold. This includes the process of exiting a state where there is no screen display.

[0153] In another embodiment, processor execution is configured to be performed by the processor. A method achieved by an operable set of possible instructions is such that the link quality value is a first predetermined value The process of communicating data between the monitoring client and the base as long as the threshold is exceeded, A process in which the screen display is turned off when the quality value falls below a first predetermined threshold. A process in which the screen display remains off as long as the index quality value remains below a predetermined second threshold. , a step of determining whether the link quality value increases to a second predetermined threshold, and The process of exiting the state of no screen display when the quality value exceeds a second predetermined threshold is as follows: include.

[0154] One embodiment of this disclosure provides a system for communicating between a monitoring client and a base. The system comprises a base having a communication component, the communication component being as follows: The monitoring client is configured to do the following as long as the link quality value exceeds a predetermined threshold. The communication of data between the base and the link quality value; if the link quality value falls below a predetermined threshold, Entering a state where there is no clean display; as long as the link quality value remains below the predetermined threshold, the screen will not be displayed. Remaining in a state where no link is displayed; determining whether the link quality value returns to above a predetermined threshold. and when the link quality value returns to exceed a predetermined threshold, the screen display will be removed. To break free.

[0155] One embodiment of this disclosure provides a system for communicating between a monitoring client and a base. The system includes a base having a communication component, the communication component being the following: It is configured to monitor the link quality value as long as it exceeds a first predetermined threshold. The communication of data between the antenna and the base; the link quality value falls below a first predetermined threshold. Entering a state where there is no screen display when descending; the link quality value is below the second predetermined threshold. As long as it remains at that level, there will be no screen display; the link quality value will remain at a second predetermined threshold. To determine whether it increases beyond a certain limit; and if the link quality value exceeds a second predetermined threshold. To escape a state where there is no screen display.

[0156] One embodiment of this disclosure provides a system for communicating between a monitoring client and a base. The system includes a base with an update component, the update component being: It is configured to: The monitoring client is connected to the base via a physical connection. Determining whether or not; monitoring the first between the client and the base via physical connection Establish a communication link; if necessary, connect the monitoring client through the first communication link. and update the interface program on the base; use the first communication link to establish a second communication link between the monitoring client and the base; and the second Communicating data from the base to the monitoring client using a communication link.

[0157] In one embodiment of the present disclosure, the base is a medical device, dock, cradle, hub, Pill dispensers, syringe pumps, infusion pumps, microinfusion pumps Communication module, ECG monitor, blood pressure monitor, pulse oximeter, CO2 capnometer It is one of the data relays and communication relays.

[0158] In one embodiment of this disclosure, the update component is executed within a sandbox. In some embodiments, the sandbox includes at least a hub, dock, and cradle. It can also be done within one.

[0159] In one embodiment of this disclosure, a system enabling electronic patient care is provided via a physical connection. and a monitoring client connected to the base, the monitoring client and the base At least one of the processors has been configured to do at least one of the following: Establishing a first communication link between the monitoring client and the base through a logical connection; The monitoring client and the interface program on the base via the first communication link Updating the system; and using the first communication link between the monitoring client and the base. To establish a second communication link.

[0160] In one embodiment of this disclosure, the processor is located on the monitoring client. In one embodiment, the processor is placed on a base. In one embodiment of the present disclosure, The second communication link transmits data from the base to the monitoring client. One example of this disclosure In this configuration, the monitoring client receives data using a second communication link. In one embodiment, the monitoring client displays the data communicated from the base. It is configured as follows. In one embodiment of the present disclosure, the monitoring client initializes the patient's treatment. It is configured to treat a patient. In one embodiment of the present disclosure, the base is configured to treat a patient. In one embodiment of this disclosure, the base is a hemodialysis system.

[0161] In one embodiment of this disclosure, the base is a patient care device. In terms of form, patient care devices include infusion pumps, pill dispensers, and microinfuses. ECG pump, ECG monitor, blood pressure monitor, pulse oximeter, CO2 capnometer Selected from the group consisting of a densa, intravenous bag, and drip flow meter.

[0162] In one embodiment of this disclosure, the system further sends an initiation treatment signal based on It comprises a monitoring client configured as follows. In one embodiment of the present disclosure, the monitoring client The communication link between the base and the terminal is wireless. In one embodiment of this disclosure, the base is It is configured to monitor the link quality value of the second communication link. One embodiment of the present disclosure So, the system will monitor the client and the client as long as the link quality value exceeds a predetermined threshold. It is configured to communicate data between the two devices.

[0163] In one embodiment of the present disclosure, the monitoring client determines that the link quality value is a first predetermined threshold. The system is configured to enter a state where there is no screen display when the value falls below a certain level. One example of this disclosure In this configuration, the monitoring client responds to the absence of a screen display via the user interface. It is configured to display a message on the face. In one embodiment of the present disclosure, Sage instructs users to move closer to the monitoring client. In one embodiment, the base measures each link quality value at regular intervals, The system is configured to determine whether each of the link quality values ​​exceeds a first predetermined threshold. It will be done.

[0164] In one embodiment of this disclosure, the base is such that the link quality value exceeds a first predetermined threshold. In such cases, the system is configured to remain in a state where there is no screen display. One of the disclosures In this embodiment, the base is a second predetermined threshold where the link quality value is greater than a first predetermined threshold. If the value is exceeded, the system is configured to remain in a state where there is no screen display.

[0165] In one embodiment of this disclosure, at least one of the monitoring clients and bases is: To update the interface program through one communication link, the following are at least It is configured such that: the monitoring client interacts through the first communication link - Configured to communicate based on the version number of the face program; monitoring client Ant checks if the interface program on the monitoring client is the latest version. It will be further configured to determine if the base is the latest interface program. The version is configured to be read from the server; and the base is the interface. Further configuration to override the latest version of the interface program in the program It will be accomplished.

[0166] In one embodiment of the present disclosure, the system uses a first communication link to monitor the climate To establish a second communication link between the base and the hub, at least one of the following: The processor is configured such that the base is paired with another monitoring client. It is configured to determine whether; if necessary, the processor will interact with another monitoring client. Further configuration to interrupt pairing with the base; the base creates a configuration file. It is configured to be; the first communication link is based on the configuration file and monitors the client. Configured to communicate to the monitoring client; the monitoring client receives the configuration file from the base. Configured to read the log; and paired with a monitoring client for wireless communication. The base paired with the monitoring client for the wireless communication is configured in the configuration file. Therefore, a second communication link is established between the monitoring client and the base.

[0167] In yet another embodiment, the tablet comprises one or more processors and one memory. Memory is a processor configured to allow one or more processors to do the following: The tablet has an operable set of executable instructions: the tablet has a physical connection to the tablet. To determine if it is connected to the base; to connect the tablet and base via a physical connection. Establish a first communication link between them; if necessary, through the first communication link Update the interface program on the ret; use the first communication link to Establish a second communication link between Bullet and Base; and the second communication link To use it to transfer data from the base to the tablet.

[0168] The tablet may be configured to: (1) monitor the base operation (2) to control the operation of the base; (3) to receive error conditions from the base. (4) Monitor the operation of the base system and determine if any error conditions exist. (5) Monitor the operation of the base and determine whether an unsafe condition exists. (6) To store errors or operational parameters and send them to the server; (7) Error - Or to store operating parameters and send them to the base for storage within the base; (8) Store errors or operational parameters and send them to the base for relay to the server. (9) While the patient is receiving treatment, video games, movies, etc. To provide patients with selected entertainment from a group consisting of recorded songs and web browsing. [Brief explanation of the drawing]

[0169] These other embodiments are described below in detail with reference to the drawings of various embodiments of this disclosure. A more detailed explanation will make this clearer.

[0170] [Figure 1] This is a block diagram of an electronic patient care system having two docks according to an embodiment of the present disclosure. [Figure 2]This flowchart illustrates a method for maintaining communication between the monitoring client and the patient care device shown in Figure 1, according to an embodiment of the present disclosure. [Figure 3] This is a block diagram of an electronic patient care system having two docks and communicating wirelessly between them, according to another embodiment of the present disclosure. [Figure 4] This flowchart illustrates a method for maintaining communication between the monitoring client and the patient care device shown in Figure 3, according to an embodiment of the present disclosure. [Figure 5] This is a block diagram of an electronic patient care system having a dock for docking together a monitoring client and a patient care device, according to yet another embodiment of the present disclosure. [Figure 6] This flowchart illustrates a method for maintaining communication between the monitoring client and the patient care device shown in Figure 5, according to an embodiment of the present disclosure. [Figure 7] A block diagram of an electronic patient care system having a monitoring client with an integrated dock for docking a patient care device thereto, according to yet another embodiment of the present disclosure. [Figure 8] This is a block diagram of an electronic patient care system having a hub according to yet another embodiment of the present disclosure. [Figure 9] This is a block diagram of an electronic patient care system having a stackable monitoring client and stackable patient care devices according to yet another embodiment of the present disclosure. [Figure 10] This is a flowchart illustrating a method for communicating patient care parameters of a patient care device to a monitoring server according to an embodiment of the present disclosure. [Figure 11] This is a flowchart illustrating a method for collecting patient care parameters for multiple patients in a monitoring server according to an embodiment of the present disclosure. [Figure 12] This is a flowchart illustrating a method for recovering a patient care device when its operation is interrupted, according to an embodiment of the present disclosure. [Figure 13]This is a flowchart illustrating a method for pairing a monitoring client with a patient care device according to an embodiment of the present disclosure. [Figure 14] This is a flowchart illustrating a method for monitoring the operation of a patient care device using a wearable system monitor paired with the patient care device, according to an embodiment of the present disclosure. [Figure 15] This is a flowchart illustrating a method for displaying a user interface using a user interface template according to an embodiment of the present disclosure. [Figure 16] This is a flowchart illustrating a method for downloading an application to control a patient care device according to an embodiment of the present disclosure. [Figure 17] This is a flowchart illustrating a method for ensuring data integrity when communicating data for a patient care device according to an embodiment of the present disclosure. [Figure 18] This is a block diagram of an electronic patient care system according to yet another embodiment of the present disclosure. [Figure 19] This is a block diagram of an electronic patient care system according to another embodiment of the present disclosure. [Figure 20] This is a block diagram of the dock of the electronic patient care system shown in Figure 19, according to an embodiment of the present disclosure.

[0171] [Figure 21] This figure shows an electronic patient care system according to an embodiment of the present disclosure, which has a tablet docked in a dock having a cable electrically coupled to a patient care device. [Figure 22] This figure shows an electronic patient care system having a tablet docked in a dock for wireless communication with a patient care device, according to an embodiment of the present disclosure. [Figure 23] This figure shows an electronic patient care system according to an embodiment of the present disclosure, having a modular infusion pump docked in a dock with a monitoring client equipped with a retractable user interface. [Figure 24]This is a side view of the electronic patient care system shown in Figure 23, according to an embodiment of the present disclosure. [Figure 25] This figure shows an electronic patient care system according to another embodiment of the present disclosure, having staggered modular infusion pumps docked in a dock having a monitoring client with a retractable user interface. [Figure 26] This figure shows an electronic patient care system according to yet another embodiment of the present disclosure, having a modular infusion pump that docks in a dock along a common horizontal plane, including a monitoring client with a retractable user interface. [Figure 27] Figure 26 is a side view of an electronic patient care system according to another embodiment of the present disclosure. [Figure 28] This figure shows an electronic patient care system according to yet another embodiment of the present disclosure, which includes a scanner and a dock-coupled hub, as well as a modular infusion pump that docks in a dock along a common horizontal plane, and a monitoring client with a retractable user interface. [Figure 29] Figure 28 is a side view of an electronic patient care system according to another embodiment of the present disclosure. [Figure 30-32] These are some figures illustrating a clutch system for mounting an electronic patient care system on a support column according to embodiments of the present disclosure. [Figure 33] This figure shows an injection pump and a dock coupled to a support column according to an embodiment of the present disclosure. [Figure 34] This figure shows another injection pump coupled to an open connector, and an injection pump equipped with an open connector, according to an embodiment of the present disclosure. [Figure 35] This figure shows the injection pump of Figure 33, in which two additional injection pumps are each connected to an open connector, according to an embodiment of the present disclosure. [Figure 36] Figures 33-35 show a top view of one of the injection pumps and a hub according to an embodiment of the present disclosure. [Figure 37]This figure shows a rectangular hub having several connectors according to an embodiment of the present disclosure. [Figure 38] This figure shows an electronic patient care system having a hub coupled to a support column, according to another embodiment of the present disclosure. [Figure 39] This figure shows an electronic patient care system according to another embodiment of the present disclosure, having a hub coupled to a support column and a portable dock, with a quick-release handle for removing the portable dock from the hub. [Figure 40] This figure shows an electronic patient care system according to another embodiment of the present disclosure, having a hub coupled to a support column and a dock coupled to the hub.

[0172] [Figure 41] This figure shows an electronic patient care system having a hub coupled to a support column, according to another embodiment of the present disclosure. [Figure 42] This figure shows an electronic patient care system according to another embodiment of the present disclosure, having a monitoring client coupled to a hub having a notch for receiving patient care devices. [Figure 43] This is an enlarged view of a T-shaped connector connecting to a hub notch, as shown in Figure 42, according to another embodiment of the present disclosure. [Figure 44] This figure shows an electronic patient care system having a stackable patient care device and a stackable container for storing infusion bags, according to another embodiment of the present disclosure. [Figure 45] This figure shows an electronic patient care system having stackable patient care devices that can be stacked next to another stack of patient care devices, according to yet another embodiment of the present disclosure. [Figure 46] This figure shows an electronic patient care system having a stackable patient care device equipped with a syringe-pump patient care device having a single syringe, according to another embodiment of the present disclosure. [Figure 47]This figure shows an electronic patient care system having a stackable patient care device equipped with a syringe-pump patient care device having two syringes, according to another embodiment of the present disclosure. [Figure 48] This figure shows an electronic patient care system having stackable patient care devices, each having a display, according to another embodiment of the present disclosure. [Figure 49] This is an enlarged view of the handle of the electronic patient care device shown in Figure 48, according to another embodiment of the present disclosure. [Figure 50] Figure 48 is an enlarged view of an infusion line port of an electronic patient care system according to another embodiment of the present disclosure, showing the infusion line arranged through it. [Figure 51] This figure shows another embodiment of an electronic patient care system, illustrating the removal of stackable patient care devices according to another embodiment of the present disclosure. [Figure 52] This figure shows an electronic patient care system prepared for transport according to another embodiment of the present disclosure. [Figure 53] This figure shows an electronic patient care system having stackable patient care devices according to another embodiment of the present disclosure. [Figure 54] This figure shows an electronic patient care system having stackable patient care devices that can be stacked from bottom to top, according to another embodiment of the present disclosure. [Figure 55] This figure shows an electronic patient care system having stackable patient care devices that are coupled to a support column and stackable from top to bottom, according to another embodiment of the present disclosure. [Figure 56] This is a perspective view of a clutch system for gripping a support column by friction, having a release handle, according to another embodiment of the present disclosure. [Figure 57] Figure 56 is a rear view of the clutch system, showing a transparent back, according to another embodiment of the present disclosure. [Figure 58] Figure 56 shows a top cross-sectional view of the clutch system according to another embodiment of the present disclosure. [Figure 59]This is a block diagram of a system for controlling an injection pump according to an embodiment of the present disclosure. [Figure 60] This is a block diagram of an electronic patient care system having a hub for communicating with several electronic patient care devices according to an embodiment of the present disclosure.

[0173] [Figure 61] This is a block diagram of an electronic patient care system having a dock that can be connected to a patient care device via USB connection, according to an embodiment of the present disclosure. [Figure 62] This is a process diagram illustrating several stages of electronic patient care according to embodiments of the present disclosure. [Figure 63-66] This figure shows several configurations of an electronic patient care system according to embodiments of the present disclosure. [Figure 67] This is a timing diagram of an electronic patient care treatment using an infusion pump according to an embodiment of the present disclosure. [Figures 68A-68B] This is a flowchart illustrating the method for illustrating the timing diagram in Figure 67 according to an embodiment of the present disclosure. [Figure 69-70] This figure shows an additional configuration of the electronic patient care system according to an embodiment of the present disclosure. [Figure 71] This is a timing diagram of an electronic patient care treatment using an infusion pump according to an embodiment of the present disclosure. [Figures 72A-72B] This is a flowchart illustrating the method for illustrating the timing diagram in Figure 71 according to an embodiment of the present disclosure. [Figure 73] This is another timing diagram of an electronic patient care treatment using an infusion pump according to an embodiment of the present disclosure. [Figure 74] This is a flowchart illustrating the method for illustrating the timing diagram in Figure 73 according to an embodiment of the present disclosure. [Figure 75] This is yet another timing diagram of an electronic patient care treatment using an infusion pump, according to another embodiment of the present disclosure. [Figure 76] This is a flowchart illustrating the method for illustrating the timing diagram in Figure 75 according to an embodiment of the present disclosure. [Figures 77-78] This figure shows several configurations of an electronic patient care system according to embodiments of the present disclosure. [Figure 79] This is another timing diagram of an electronic patient care treatment using an infusion pump, according to another embodiment of the present disclosure. [Figures 80A-80B] This is a flowchart illustrating the method for illustrating the timing diagram in Figure 79 according to an embodiment of the present disclosure.

[0174] [Figure 81] This is another timing diagram of an electronic patient care treatment using an infusion pump, according to another embodiment of the present disclosure. [Figures 82A-82B] This is a flowchart illustrating the method for illustrating the timing diagram in Figure 81 according to an embodiment of the present disclosure. [Figure 83-89] This figure shows some additional embodiments of an electronic patient care system according to some embodiments of the present disclosure. [Figure 90] This is a block diagram of the electronic circuit of an embodiment of a hub according to the embodiments of the present disclosure. [Figure 91] This is a block diagram of an electronic circuit for interface connection with an injection pump according to an embodiment of the present disclosure. [Figure 92] This figure shows another embodiment of an electronic patient care system having patient care devices docked in a dock and arranged vertically, according to embodiments of the present disclosure. [Figure 93] This is a block diagram of the electronic circuit of an embodiment of a hub according to the embodiments of the present disclosure. [Figure 94] This is a block diagram of the electronic circuit of a communication module according to an embodiment of the present disclosure. [Figures 95-98] This figure shows some embodiments of an electronic patient care system having an infusion pump coupled to a communication module, according to some embodiments of the present disclosure. [Figure 99-101] These are some block diagrams of the electronic circuits of a dock according to some embodiments of the present disclosure.

[0175] [Figure 102] This is a block diagram of a battery pack according to an embodiment of the present disclosure. [Figure 103-104] This figure shows an additional embodiment of the electronic circuit of the dock according to an additional embodiment of the present disclosure. [Figure 105-116] This figure shows some embodiments of a mountable pump attached to a monitoring client, according to additional embodiments of the present disclosure. [Figure 117] This figure shows a backplane for use in an injection pump according to an embodiment of the present disclosure. [Figure 118] This is a cross-sectional view of the backplane panel shown in Figure 117 according to an embodiment of the present disclosure. [Figure 119-120] This figure shows some embodiments of a mountable pump attached to a monitoring client, according to additional embodiments of the present disclosure.

[0176] [Figure 121] This figure shows a communication module according to an embodiment of the present disclosure. [Figure 122] This figure shows a communication module attached to a patient monitoring device according to an embodiment of the present disclosure. [Figure 123] This is a diagram of the electronic circuit of the communication module shown in Figure 121, according to an embodiment of the present disclosure. [Figure 124] This is a diagram of an electronic circuit that converts short-range wireless communication to UHF according to an embodiment of the present disclosure. [Figure 125-127] This figure shows several antennas according to additional embodiments of the present disclosure. [Figure 128] This figure shows a patient wristband with an RFID tag according to an embodiment of the present disclosure. [Figure 129] This figure shows a split-ring resonant circuit used on the wrist band in Figure 128, according to an embodiment of the present disclosure. [Figure 130] This figure shows a near-field antenna according to an embodiment of the present disclosure. [Figure 131]This figure shows the equivalent circuit of the split ring resonant circuit of Figure 130 according to an embodiment of the present disclosure. [Figure 132] This figure shows a 5R checklist that can be displayed on a monitoring client according to an embodiment of the present disclosure. [Figure 133] This figure shows a blockage checklist that can be displayed on a monitoring client according to an embodiment of the present disclosure. [Figure 134] This figure shows a display of a monitoring client that communicates operably with several injection pumps according to an embodiment of the present disclosure. [Figure 135] This figure shows a display on a healthcare provider's portable monitoring client, illustrating a list of patients whose patient information the provider can access, according to an embodiment of the present disclosure. [Figure 136] This figure shows a display on a healthcare provider's portable monitoring client showing a device associated with a specific patient, with one-touch access to current data from the device and some of the patient's medical information, according to an embodiment of the present disclosure. [Figure 137] This figure shows a display on a healthcare provider's portable monitoring client indicating a data input area for a drug prescription, for use with an intravenous infusion pump, according to an embodiment of the present disclosure. [Figure 138] This figure shows a display on a healthcare provider's portable monitoring client, as created by the monitoring client, indicating the risk factors associated with the prescribed medication and the suggested course of action, according to an embodiment of the present disclosure. [Figure 139] This figure shows a display on a healthcare provider's portable monitoring client showing a drug prescription ready to be presented by the prescribing provider, according to an embodiment of the present disclosure. [Figure 140] This figure shows a display on a healthcare provider's portable monitoring client illustrating how a monitoring system according to an embodiment of the present disclosure can display to a prescription provider confirmation that a prescription has been delivered to a pharmacist.

[0177] [Figure 141] This is a perspective view of a microinfusion pump coupled to an adapter according to an embodiment of the present disclosure. [Figure 142] This is a perspective view of a wireless hub device according to an embodiment of the present disclosure, which wirelessly relays data from a patient care device to a monitoring client, another hub, or dock. [Figure 143] This is a front perspective view of an electronic patient care system having modular patient care devices coupled to a monitoring client via an adapter and a dock, according to an embodiment of the present disclosure. [Figure 144] Figure 143 is a side perspective view of the electronic patient care system according to an embodiment of the present disclosure. [Figure 145] Figure 143 is an enlarged perspective view of one interface of the patient care device according to an embodiment of the present disclosure. [Figure 146] Figure 143 is a top view of the electronic patient care system according to an embodiment of the present disclosure. [Figure 147] This figure shows a system for an electronic patient care system according to an embodiment of the present disclosure. [Figure 148] This is a block diagram of an electronic patient care system according to an embodiment of the present disclosure. [Figure 149] This is a block diagram of the bedside portion of the electronic patient care system according to an embodiment of the present disclosure, as shown in Figure 147 and / or Figure 148. [Figure 150] Block diagrams of the dock / hub according to embodiments of the present disclosure are shown in Figures 147, 148, and / or 149. [Figure 151] This is a block diagram showing the injection pump circuit of Figures 148 and / or 149 according to an embodiment of the present disclosure. [Figure 152] This is a block diagram showing a sensor coupled to the mechanism of an injection pump according to an embodiment of the present disclosure.

[0178] [Figures 153A-153B]This flowchart illustrates a method of communication between a tablet and a base according to an embodiment of the disclosed invention. [Figure 154] This flowchart illustrates a method for updating an interface program according to an embodiment of the disclosed invention. [Figure 155] This flowchart illustrates a method for establishing a second communication link between a tablet and a base according to an embodiment of the disclosed invention. [Figure 156] This flowchart illustrates a method for communicating data between a tablet and a base, as long as the link quality value of the second communication link exceeds a threshold, according to an embodiment of the disclosed invention. [Figure 157] This flowchart illustrates an example of a method, according to an embodiment of the disclosed invention, for entering a state where there is no screen display when the link quality value falls below a threshold. [Modes for carrying out the invention]

[0179] A technology that facilitates patient care is disclosed. This technology is, for example, an exemplary embodiment. Having one or more patient care devices that are communicably coupled to a monitoring client. This can be implemented within the system. Patient care devices have a wide variety of functions. It may be equipped with and / or manufactured by different manufacturers. In one such case, between the client monitoring station and various patient care devices, The communication interface, along with discovery and protocol conversion, has various other functions, for example To name a few, power provisioning, compliance with various standards, and user interface This also enables things like infusion pumps and microinfusions. Patient care devices include infusion pumps and microinfusions. Pumps, insulin pumps, syringe pumps, pill dispensers, dialysis machines, artificial respiration pumps Inhaler, ultrasound diagnostic equipment, ECG monitor, blood pressure monitor, pulse oximeter, CO2 capnometer Meters, infusion counters, infusion flow meters, optical Doppler devices, heart rate monitors, intravenous Bags, hemodialysis machines, peritoneal dialysis machines, intestinal dialysis machines, patient thermometers and / or other bedside devices. It could also be a patient care device.

[0180] A U.S. patent application filed on February 9, 2007, entitled "Fluid Delivery System and Method" Application No. 11 / 704,899, subsequently published as a U.S. patent on October 4, 2007. Application Publication No. 2007-0228071A1 (Agent Reference Number: E70), February 2007 The "Method Using a Pump Fluid Delivery System and Force-Applying Assembly" filed on the 9th of the month and The U.S. Patent Application No. 11 / 704,896, with the name [name of application], was subsequently filed on September 20, 2007. U.S. Patent Application Publication No. 2007-0219496 (Agent Reference Number: E71) was published in [location]. ), filed on February 9, 2007, under the name "Patch-Sized Fluid Delivery System and Method" This was U.S. Patent Application No. 11 / 704,886, which was subsequently published on September 20, 2007. U.S. Patent Application Publication No. 2007-0219481 (Agent Reference Number: E72), 2 The patent application filed on February 7, 2007, for "Methods for Adhesives, Peripheral Systems, and Medical Devices" The U.S. Patent Application No. 11 / 704,897, with the title [unclear], was subsequently filed on September 20, 2007. Published U.S. Patent Application Publication No. 2007-0219597 (Agent Reference Number: E73) , a U.S. patent application filed on December 31, 2008, titled "Injection Pump Assembly" Patent No. 12 / 347,985, subsequently published on December 3, 2009. Application Publication No. 2009-0299277 (Agent Reference Number: G75), December 3, 2008 U.S. Patent Application No. 12 / 3, filed on the 1st, entitled "Wearable Pump Assembly" This is patent number 47,982, which was subsequently published on November 12, 2009. Application No. 2009-0281497 (Agent Reference Number: G76), filed December 31, 2008. U.S. Patent Application No. 12 / 347,981, entitled “Injection Pump Assembly” Subsequently, on November 5, 2009, U.S. Patent Application Publication No. 2009-02758 was published. Application No. 96 (Agent Reference Number: G77), filed December 31, 2008, for "equipped with a switch" The U.S. Patent Application No. 12 / 347,984 is titled "Pump Assembly," and U.S. Patent Application Publication No. 2009-0299289, published on December 3, 2009 ( Agent reference number: G79), "Injection pump assembly" filed on October 10, 2008. This was U.S. Patent Application No. 12 / 249,882, and subsequently, on April 15, 2010... U.S. Patent Application Publication No. 2010-0094222 (Agent Reference Number: F5) published on [date] 1) "System and method for administering an injectable fluid," filed October 10, 2008. The U.S. Patent Application No. 12 / 249,636, titled "The Law," was subsequently filed in April 2010. U.S. Patent Application Publication No. 2010-0094261 (Agent Reference Number: F52), filed on October 10, 2008, entitled "Obstruction Detection System and Method" This was U.S. Patent Application No. 12 / 249,621, which was subsequently published on April 15, 2010. U.S. Patent Application Publication No. 2010-0090843 (Agent Reference Number: F53), 200 The "Multilingual / Multiprocessor Injection Pump Assembly" filed on October 10, 2008, and The U.S. Patent Application No. 12 / 249,600, with the name [name of application], was subsequently filed on April 15, 2010. U.S. Patent Application Publication No. 2010-0094221 (Agent Reference Number: F54) was published in [date]. ), published November 29, 2011, "Injection Pump Assembly with Backup Power Supply" U.S. Patent No. 8,066,672 (Agent Reference Number: F55), 2011, with the title "..." "Pump Assembly with Removable Cover Assembly" issued on September 13th. U.S. Patent No. 8,016,789 (Agent Reference Number: F56), 2007, with the name [name of patent]. U.S. Patent No. 7,306,5 issued on December 11th, titled "Loading Mechanism for Injection Pumps" All of the above in relation to No. 78 (Agent Reference Number: C54) is incorporated herein by reference in its entirety. These technologies are used to enable seamless communication and fail-safe operation. It is possible. Numerous other features, functions, and applications will be obvious in light of this disclosure. .

[0181] General Overview As mentioned above, the process of providing comprehensive care to patients, for example, instructing and delivering treatment This relates to several important issues. For example, the miscommunication of important information. And, treatment decisions are made without immediate access to complete information, and / or Alternatively, delays in the implementation of prescriptions may occur due to unnecessarily redundant and inefficient procedures. There is a good possibility.

[0182] More specifically, medication errors can cause hundreds of deaths, and in the United States alone, every year. It could be affecting thousands or even millions of people. A disease that is putting a strain on finances. The hospital may have experienced many medication error incidents. The most dangerous errors are those that can lead to misuse. Examples of medications include insulin, narcotics, heparin, and chemotherapy. Causes of medication errors Examples include administering the wrong drug, administering the wrong concentration of drug, or administering at the wrong rate. Delivering drugs, or delivering drugs via the wrong route (drugs are administered orally, intravenously) In the pulse, in the muscle, subcutaneously, in the rectum, locally in the skin, eye or ear, in the spinal cavity, in the abdominal cavity (It can be administered internally, or even intravesically.) Appropriate instructions and Even with proper labeling, illegible handwriting, incorrect transmission of medication prescriptions, and the same Due to mispronunciation of drug names, there is still a possibility that the drugs may be administered inappropriately. To reduce medication errors, electronic medical records (EMRs) and barcodes for medications are being implemented. A trend has emerged to use the system. EMR systems are used, for example, in patient diagnosis and allergy assessment. - Computer provider instruction input (CPOE) that is not suitable for weight and / or age. ) and flag prescriptions may be hastily implemented. However, these systems are widely adopted It has not yet been put into use, and its implementation involves instructing, preparing, and administering the drug. This can lead to significant delays and inefficiencies.

[0183] In addition, drug infusion devices, such as infusion pumps, can suffer significant damage from all injections. This is related to a significant number of drug errors (for example, up to one-third). Incorrect parameters (e.g., drug concentration or infusion rate) are entered and the value is reduced. or existing injection parameters may be inappropriately modified. Related to the injection pump Nearly half of the deaths are due to user error, and many of these errors are due to injection errors. This can sometimes be due to errors in programming the program.

[0184] An effective monitoring system will monitor both the ordering and administration of medications and detect any inconsistencies. Thus, minimizing any of the many adverse events that may result from the treatment. It can help in the transformation. Conceptually, the drug therapy process has three stages: the prescription stage and the drug stage. It can be divided into the drug preparation stage and the drug administration stage. When a prescription for a drug is written or When input, when a drug is read out for use, or when it is mixed into a solution, Errors can occur when medication is administered to patients.

[0185] Therefore, according to embodiments of the present disclosure, at least one patient care parameter is communicated. A monitoring client configured to communicate at least one patient care parameter. A patient care device configured to such effect, and the presence of at least one patient care device. Discover and monitor the communication signals from that device and the communication pair associated with the client. By converting to Rotor, monitoring clients and at least one patient care device An electronic patient with a communication interface configured to facilitate communication between the patient and the device. A care system is disclosed. In some embodiments, a monitoring client controls the patient care data. The operation of the vice is passively monitored. The communication interface is the communication module described below. This can be done by [the system]. The communication interface can also be different from each other. Additional patient care devices (e.g., diverse manufacturers, functions, and / or communication protocols) The system detects the presence of devices such as [device names] and monitors communication signals from these devices, as well as the client. It can be configured to convert to the communication protocol associated with the hub. This means that monitoring clients such as tablets and computers are connected via a communication interface. When providing treatment to patients associated with monitoring clients, healthcare providers IDA can be effectively used as a common general user interface. This becomes possible. One or more databases accessible by the monitoring client The system is (as desired by healthcare facility or database maintenance and management companies, any form (In a mat and database structure) Central storage of patient information and associated with monitoring clients Information that can be used by healthcare providers when treating patients who have been diagnosed. Enables downloads. The communication interface uses wired and / or wireless technology. It can be implemented in several ways, and seamlessly connects numerous patient care devices. Enables reliable and fail-safe operation. Suitable for several patient care devices, hubs, and docks. , and / or monitoring clients may simultaneously use two or more communication links, and / or It can communicate simultaneously on two frequency channels (in some embodiments, (The data may be redundant). In some embodiments, the communication module is, for example Patient care devices, such as infusion pumps, are equipped with batteries and sufficient circuitry for mobile operation. This makes it possible to use the patient care device in a portable manner. In addition, or as an alternative, the patient wristband can be plugged into the communication module. Equipped with a battery, it can power patient care devices (or several In this embodiment, it can be plugged directly into the patient care device. The communication module is It can be charged via cable.

[0186] In some embodiments, patient care parameters (for example, in some embodiments, Data such as real-time parameters is transmitted to a cloud server for storage. This can be done, and the data can be de-identified.

[0187] System Architecture As shown in Figure 1, the electronic patient care system 100 is assigned to each individual patient 2. One or more monitoring clients 1, 4 that can be in physical proximity to patient 2, Information is uploaded from several different monitoring clients 1 and 4, and from various sources. The system includes a remote monitoring server 3 that downloads information and instructions to monitoring clients 1 and 4. When in the patient's room, the healthcare provider monitors client 1 directly. Interacting with Patient 2 to obtain information about Patient 2 or to input instructions about Patient 2 Yes, multiple monitoring clients 1 can interact with one monitoring server 3. The monitoring server 3 is equipped with middleware (for example, middleware on the monitoring server 3 in Figure 1). It is possible to obtain this. In addition, or as an alternative, remote locations (e.g., a doctor's office) Providers located at Nurse Station 5 and the hospital pharmacy 6 communicate with monitoring server 3. Through the link, or with each monitoring client 1, 4 acting as a node in the hospital local network. It is possible to interact directly with individual monitoring clients 1 via the area network. Cut.

[0188] Remote communicator 11, other monitoring clients 4, nurse station 5, or The doctor's office is used to update the patient's personal EHR19 or to dispense medications. The prescription sent to pharmacy 6 may be entered. The prescription is for pills, so the fluid is injected. It may be a prescription for use or other treatment. The prescription is for infusion pump 7, siri Inject the fluid using the range pump 126 or the microinfusion pump 130. A prescription for administering or dispensing pills using pill dispenser 128 It's okay to have it.

[0189] Pharmacy 6 is one or more computers connected to a network, such as the Internet. The system includes a mechanism for receiving prescriptions and placing those prescriptions into a queue in one or more computers. The pharmacy may use the prescription to do the following: (1) (e.g.) If, the one or more computers connected to the computer are capable of compounding fluids or producing pills Use an automated blending device or monitor the queue of one or more computers. (2) Mixing drugs manually by a pharmacist; (3) Fluid refilling syringe pump 126 (3) Pre-fill the syringe pump 126 (for example, the treatment unit) The image is programmed into the syringe pump 126; (4) Microinfusion (5) Pre-fill the pump 130; (5) Professionally fill the microinfusion pump 130. Gram; (6) Pre-fill intravenous bag 170; (7) Program infusion pump 7 (8) Pre-fill the pill dispenser 128; or (9) take the medicine according to the prescription. Program the pill dispenser 128 at the pharmacy. The automated compounding device is a syringe pump. 126, one or more intravenous bags 170 or microinfusion pumps 130 The fluid can be automatically filled into the pill dispenser 128 and / or the pill dispenser 128 It can be filled automatically. The automatic filling device uses barcodes, RFID tags and It can generate data such as barcodes, RFID tags, and / or data. Information within the data may include treatment plans, prescriptions, and / or patient information. ru.

[0190] The automated compounding device includes (1) barcode injection pump 7, syringe pump 126, and Microinfusion pump 130, pill dispenser 128, or intravenous bag 1 Attach to 70, (2) RFID tag to injection pump 7, syringe pump 126, My Chloe infusion pump 130, pill dispenser 128, or intravenous bag 17 Attach to 0 and / or (3) inject pump 7, syringe port with information or data Pump 126, microinfusion pump 130, pill dispenser 128, also The RFID tag or memory inside the intravenous bag 170 can be programmed. The data or information may be, for example, a barcode, RFID tag, or serial number in memory. Alternatively, use other identification information to send the prescription to infusion pump 7, syringe pump 126, My Chloe infusion pump 130, pill dispenser 128, or intravenous bag 17 Database to associate with 0 (e.g., patient's EHR19 or patient's personal EHR) It can be sent to 19').

[0191] Infusion pump 7, syringe pump 126, microinfusion pump 130 The pill dispenser 128 can be used with (1) a syringe / pump 126 or an intravenous bag 17 (2) Whether 0 has the correct fluid, and whether the microinfusion pump 130 is correct (3) Whether the pill dispenser 128 has the correct pill (4) Infusion pump 7, syringe pump 126, microinfusion pump The programmed treatment in 130 or intravenous bag 170, syringe pump 126 , compatible with the fluid in the microinfusion pump 130 or intravenous bag 170 (5) Whether or not the treatment programmed in the pill dispenser 128 is Whether it corresponds to the pills in Spencer 128 and / or (6) infusion pump 7, Syringe pump 126, microinfusion pump 130 or pill dispenser The treatment programmed within the 128 (for example, patient barcode, RFID or Scanning to determine if a particular patient is correct (based on other patient identification information) It may have a (for example, an RFID caller or a barcode scanner). In some specific embodiments, the injection pump 7, syringe pump 126, and microphone are used. The loinfusion pump 130 and / or pill dispenser 128 are RFID Read one or more serial numbers from the tag or barcode, and the values ​​are found in the internal memory. It must match the value (for example, downloaded via an automated blending device), and This value is the value found in the patient's electronic medical record (for example, the patient's EHR19 or patient's Percentage). Stored in the Sonal EHR19', or by scanning the patient's RFID tag or to the patient Ensure that it matches the patient's serial number (determined by scanning the barcode). It can be proven.

[0192] For example, injection pump 7, syringe pump 126, microinfusion pump The scanner for the 130 or pill dispenser 128 will scan the serial number of the patient care device. To obtain the barcode of another patient care device and determine the patient's serial number. Therefore, the patient's barcode can be scanned, and the serial number of the patient care device can be scanned. (For example, it may have been updated by pharmacy 22 or the pharmacy's automated compounding device.) To determine whether it corresponds to the patient's serial number stored in the electronic medical record, Medical record data can be accessed.

[0193] In addition, or as an alternative, the monitoring client 6 includes (1) syringe pump 1 (2) Whether 26 or intravenous bag 170 has the correct fluid, (2) microinfusion (3) Whether the ion pump 130 has the correct fluid, pill dispenser 128 (4) Infusion pump 7, syringe pump 126, microphone Therapy programmed into loinfusion pump 130 or intravenous bag 170 However, syringe pump 126, microinfusion pump 130 or intravenous (5) Whether it corresponds to the fluid in the bag 170, the prog in the pill dispenser 128 Whether the administered treatment corresponds to the pill in the pill dispenser 128, and / Or (6) Infusion pump 7, syringe pump 126, microinfusion pump The treatment programmed in the P130 or pill dispenser 128 is (for example, the patient) For a specific patient (determined from barcodes, RFID, or other patient identification information) To determine if it is correct, use injection pump 7, syringe pump 126, pill dispenser. Pensa 128, microinfusion pump 130 or intravenous bag 170 It can be canceled. In addition, or as an alternative, monitoring client 1, inject Pump 7, syringe pump 126, microinfusion pump 130 or round The drug dispenser 128 includes, for example, an infusion pump 7, a syringe pump 126, and a micro- On an infusion pump 130, pill dispenser 128 or intravenous bag 170 Use the barcode / serial number to verify or download your prescription. Therefore, query the electronic medical record database 19 or 19' and / or pharmacy 22. It is possible.

[0194] In optional settings, instructions or requests can be made to patient care devices 7, 14, 15, 16, 17, and 35. To send to 126, 128, 130, 148, for example, bolus volume, injection flow rate, Measuring delivery fluid, drug delivery start time, drug delivery stop time, or delivery flow rate profile infusion pump 7, syringe pump 126 and / or microinfusion pump To send to the 130, monitoring client 1, other monitoring clients 4 and / or Alternatively, a remote communicator 11 can be used. In some embodiments, for example, , pill dispensing instructions for distributing pills, pill type, pill dispensing schedule and / or It monitors and sends instructions or requests, such as the maximum pill dispensing standard, to the pill dispenser 7. Clients 1, 4, and 11 may be used in one or more cases. The maximum pill distribution standard is [specified]. This is the maximum amount of drug that can be delivered within a set time, for example, if a particular drug is needed. It is taken when necessary, but if taken in excess, the drug is not safe. It is possible that this is not the case, and the maximum pill distribution criteria may be, for example, "a predetermined amount within a predetermined time." This can prevent patients from ingesting medication in unsafe amounts.

[0195] For optional selection, patient care devices 7, 14, 15, 16, 17, 35, 126, and 128 are available. ,130,148 also ask whether an alarm or warning should be issued or transmitted. System 10 determines whether the treatment or condition is safe for the patient. Determine whether 0 is operating correctly or within a given boundary, and / or monitor the client. The display of the 1st, other monitoring clients 4 and / or remote communicator 11 To display the data on the ray, the data is monitored by client 1, and other monitoring clients... 4. It can reply to the remote communicator 11. For example, optional. Then, infusion pump 7, syringe pump 126 and / or microinfusion Pump 130: upstream pressure, change in upstream pressure, downstream pressure relative to patient 2, patient 2 Changes in downstream pressure, presence or absence of air in the injection line, actual bolus volume delivered, Actual injection flow rate, actual total fluid delivered, actual start time of drug delivery, actual drug delivery The downtime during the event, or the actual delivery flow profile, is monitored by client 1, other monitoring clients. One or more of the Liant 4 and / or remote communicators 11 (if applicable) It can communicate. In another embodiment, the pill dispenser 128 is optionally, for example For example, the actual pills that were distributed, the type of pills that were distributed, and the actual amount of pills distributed at that time. Data such as distribution schedules or whether the maximum pill distribution criteria have been exceeded are monitored by the monitoring client. Ant 1 replies to other monitoring clients 4 and / or remote communicator 11. It is possible.

[0196] Patient care devices 7, 14, 15, 16, 17, 35, 126, 128, 130, 14 The data received from 8 will be used to issue alarms and / or warnings, at any predetermined time. The state can be analyzed. For example, one or more of the monitoring clients 1, 4, and 11. This includes an infusion pump 7, a syringe pump 126, and / or a microinfusion pump. The increase in the downstream pressure of pump 130 may cause excessive coagulation, osmosis, or blockage of the tube to the patient. Bending, or by substances such as contamination found inside the intravenous bag 170, for example. It can be used as one manifestation of a blockage occurring downstream. Downstream pressure In response to the rapid increase, one or more of the monitoring clients 1, 4, and 11 will visually display to the user Alternatively, an audible alarm or warning may be issued. These alarms and / or Also, vigilance is required, and nurses should take other appropriate actions, such as ensuring that the downstream pressure on the patient is within the prescribed range. If the reading rises above the threshold, the needle is replaced depending on the obstruction (e.g., caused by coagulation). A proposal to do so, or if the downstream pressure on the patient rises above a predetermined threshold, the line You can be instructed to suggest checking for internal folds.

[0197] In addition, or alternatively, a rapid decrease in downstream pressure on patient 2 is a churning. This indicates that the needle has come off and / or that the needle is now detached from the patient. Depending on the monitoring client, one or more of the clients 1, 4, and 11 will insert the tube for continuous injection. To reattach the needle or insert a new needle, the user is given visual or auditory instructions. An alarm or warning can be issued. The alarm can also be issued, for example, if the tube is a needle. When the kneecap comes off, the patient may be bleeding, and the kneecap that is not attached may be bleeding. The Dolcapura may indicate that bleeding is occurring and therefore requires immediate action. ru.

[0198] In some embodiments, in addition to or as an alternative, one or more injection pumps 7 The upstream pressure can be monitored for any upstream blockage. For example, Contamination in intravenous bag 170 could block the tubing upstream of the infusion pump 7. Each time the infusion pump 7 attempts to pump fluid from the intravenous bag 170, the infusion pump The upstream pressure on pump 7 may drop lower than what would occur if there were no blockage upstream. Therefore, one or more of the monitoring clients 1, 4, and 11 will have a predetermined upstream pressure. If the threshold is lowered, an alarm or warning will be issued, for example, to the caregiver regarding the tube or To suggest or request that the occlusion be alleviated by replacing the intravenous bag 170 There is.

[0199] If one or more of the monitoring clients 1, 4, and 11 are selected, then the downstream pressure on patient 2 is... In response to a rapid rise and / or fall, injection pump 7 stops the delivery of fluid. , syringe pump 126 and / or microinfusion pump 130 You may send more than one instruction.

[0200] As shown in Figure 1, and similar to some embodiments, the system 100 monitors the climate It is equipped with Ant Dock 102 and Device Dock 104. Monitoring Client... Dock 102 is configured to receive monitoring client 1, and device dock 104 receives one or more patient care devices to facilitate bedside patient care. It is configured as follows (details below). Device dock 104 is Although it has been indicated that several patient care devices are available, other In this embodiment, the device dock 104 includes one patient care device and multiple patient care devices. They can receive vices, or any number of patient care devices. In addition, surveillance The client dock 102 can receive one monitoring client 1. Although shown in the above, in other embodiments the monitoring client dock 102 is 2 One monitoring client, three or more monitoring clients, or any number of monitoring clients It is possible to receive client 1.

[0201] In this exemplary embodiment, the cable 110 is connected to both docks 102 and 104. And in between, it provides a communication link. Cable 110 is connected to one of the docks 102 and 104. Or it can be permanently attached to both, or is attachable. In addition Alternatively, cable 110 can be connected to either dock 102 or 104. It may have one or more connectors (not explicitly shown) for plugging into both. .

[0202] In some embodiments, docks 102, 104 have one or more wires within the cable 110. They can communicate with each other using earpieces and / or waveguides. For example, the present disclosure In this embodiment, the cable 110 is equipped with an optical fiber waveguide between docks 102 and 104. To provide an optical communication link. In other embodiments, as can be seen in light of this disclosure, the cable The 110 can, if desired, use one or more wireless communication links (e.g., Bluetooth). ) can be replaced with. In yet another embodiment, a wired connection is made between docks 102 and 104. And combinations of wireless communication channels may be used. Any number of suitable wired connection types This can be used in various embodiments.

[0203] In some embodiments, the communication links between docks 102 and 104 are serial communication, parallel communication, etc. Communication, synchronous communication, asynchronous communication, packet-based communication, virtual circuit-based communication, etc. Any known communication link can be used. In addition to or alternatively In some embodiments, the communication link established between docks 102 and 104 is not Linear communication, wired communication, connectionless protocols, e.g., user datagram protocols Tocol (UDP), or connection-based protocols, such as the Communication Control Protocol (TCP) ) can be used. For example, communication between docks 102 and 104 is universal. • Serial Bus Standard, SATA, eSATA, FireWire, Ethernet Standard, Fiber Channel, Bluetooth, Bluetooth Low Energy, WiFi, Nintendo It can be based on one or more of the following: a physical layer technology, any OSI layer technology, etc.

[0204] When monitoring client 1 is docked to monitoring client dock 102 The monitoring client 1 has access to communication between docks 102 and 104. In some embodiments of this disclosure, the monitoring client 1 is connected by cable 110 Through the provided communication link, electronic circuits within the device dock 104, such as memory, and It can communicate. In addition, or alternatively, monitoring client 1 can The communication links provided by Bull 110, and / or one or more radio communication links Through this, it is possible to communicate with any device docked to device dock 104. Yes, it is possible (more details below).

[0205] Further referring to the exemplary embodiment shown in Figure 1, the device dock 104 is each Optional, mountable display 134, camera 136, and microphone 13 It can be equipped with various accessories such as the 8. Similarly, the monitoring client dock 102 These are various accessories, such as camera 140 and microphone 142, each of which is optional. It can be equipped with cameras 144 and It can be equipped with various accessories such as microphone 146. Camera 136, 14 0, 144 are, for example, providers (e.g., nurses, nurse practitioners, doctors). (etc.) and / or facial recognition software to authenticate or identify the presence of a patient It can be used in this way. In addition, or as an alternative, microphone 138, 142 and 146, for example, authenticate or recognize the presence of a provider and / or patient. To distinguish it, it can be used by speech recognition software. In light of this disclosure As you can see, cameras 136, 140, 144 and microphones 138, 142, 1 46, for example, to ensure that the right patient receives the right treatment, before starting treatment, The patient communicates with the remote care provider and / or (e.g., voice and / or face) To enable the verification of patient identification information (using recognition technology, retinal scans, etc.) It can also be used for other purposes.

[0206] As shown in Figure 1, in some embodiments, monitoring client 1, monitoring client Dock 102 and device dock 104 each have an antenna 11 for wireless communication. It has 2, 106, and 108 (each antenna 112, 106, and / or 108 (Optional). Cable 110 is unplugged, or the dock 10 is connected via cable 110. 2. If communication between 104 is interrupted or impaired by other means, monitoring client dock 102 and device dock 104 are connected via antennas 106 and 108. They can continue to communicate with each other using a linear communication link. In addition, monitoring clients If Ant 1 is removed from the monitoring client dock 102, monitoring client 1 For example, it can communicate directly with the device dock 104 and / or monitor the The lance 1 communicates wirelessly via cable 110 or between docks 102 and 104. By wirelessly communicating with the monitoring client dock 102, which relays communication via a link, This allows it to communicate with device dock 104. As previously mentioned, • To communicate with various devices docked to dock 104, monitoring device 1 and Communication with the device dock 104 can be utilized by the monitoring client 1. ru.

[0207] In some embodiments, the monitoring client 1 is, for example, the monitoring client dock 1. For docking to 02, and with surveillance client dock 102 and surveillance client Two connectors of monitoring client 1 used to provide telecommunications between it and client 1. By measuring the voltage or impedance between the electrical contacts of one or more connectors, Whether one or more electrical contacts are electrically engaged with the monitoring client dock 102 Electrically determine whether cable 110 is available as a communication link. It is possible. Also, monitoring client 1 can connect to cable 110. If it is determined that the cable is not gas-coupled, then cable 110 is deemed unavailable. It is possible. In addition, or alternatively, in some embodiments, dock 10 The magnetic force within 2 engages with the Hall effect sensor of monitoring client 1, and then the monitoring client To 1 uses the sensor to check the cable when monitoring client 1 is not docked. As monitoring client 1 infers that LU110 is not available as a communication link Determine whether it is docked or not. In addition, or alternatively, monitor the cluster. The circuitry within Ianto Dock 102 is configured in the case when the cable is not available as a communication link. A signal can be sent to the monitoring client 1. In some embodiments, the monitoring client Ant 1 periodically connects to the "network" of device dock 104 via cable 110. It is possible to "check the connection (ping)". The monitoring client will check the device within a specified time. If no response is received from IS-Dock 104, monitoring client 1 will use cable 11 It is presumed that 0 is not available as a communication link.

[0208] Monitoring client 1 determined that cable 110 was not available as a communication link. In this case, monitoring client 1 will use a speaker and / or vibration motor to trigger an alarm. Alternatively, an alarm or warning may be issued, and the alarm or warning is sent to the remote communicator 11. Use a PEEK and / or vibration motor to send an alarm or warning to a remote communicator. The client may also transmit and / or monitor the patient via other communication links. You may attempt to communicate with the device. The term “alert” as used herein means, for example If so, do not draw attention to it until the cause of suspicion still remains after a predetermined time has elapsed. This is intended to include a "soft" level of caution.

[0209] In some embodiments of this disclosure, the monitoring client dock 102 has minimal circuitry. 1 from monitoring client 1 to cable 110, whether used or not using the circuit It comprises one or more wires or waveguides. For example, in some embodiments of the present disclosure, monitoring The client dock 102 is directly electrically coupled to the cable 110 from the monitoring client 1. It is a cradle that gives. In addition to that, or alternatively, some implementations of the present disclosure In terms of form, the device dock 104 uses minimal circuitry or no circuitry at all. i, various docked devices and / or monitoring via client dock 102 Alternatively, it may include one or more wires or waveguides to facilitate communication between monitoring clients 1. In some embodiments, the device dock 104 may be a cradle.

[0210] In embodiments of this disclosure, each monitoring client 1 is assigned to a specific patient 2, and death It may be a base-mounted, portable, or handheld display and user It may have input capabilities. The monitoring client 1 may be portable and effective. It is possible to facilitate efficient data viewing and data entry, and monitoring client 1 is Notebook PCs, netbook PCs, and other devices with or without a touchscreen. A bullet PC may also be called a "smartphone." In addition to or as an alternative, In some embodiments, the monitoring client 1 and / or remote communicator 11 It docks or connects to a cable connected to a much larger display, and This allows for monitoring with much larger displays (e.g., 24-inch displays). It can be used as the display for Iant 1 and / or remote communicator 11. The much larger display is for monitoring client 1 and / or remote communicator 1. 1. Touchscreen capabilities, stylus input capabilities, keyboard input capabilities, remote It can have input capabilities such as control input capability. For example, X-ray or patient imaging Viewing the file requires monitoring client 1 and / or remote communicator 11 to be larger This can be easily done by docking it to a monitoring dock that is connected to the display. This allows caregivers to use a larger display to save patient images. It can be viewed. The viewing dock also allows monitoring clients and / or remote communication. It can charge the DATA 11.

[0211] Monitoring client 1 is a Linux-based operating system, android BlackBerry-based operating system, BlackBerry-based operating system System, tablet-based operating system, iOS, iPadOS, i It can run Phone OS, etc. Specific monitoring client for specific patient 2 The designation of T1 is (but not limited to) a bar embedded in the wristband 118. The code includes a unique patient identifier encoded on code 114 or RFID tag 116, This can be done using one of several methods. The device dock 104 is a bar To determine the unique patient identifier of code 114 or RFID tag 116, the scanner It is equipped with a 120. Scanner 120 is a laser barcode scanner, CCD based. This includes barcode scanners, short-range communicators or callers, RFID readers, etc. This may also be the case. In other embodiments, the unique patient identifier may be based on the patient's biometric data. Yes, it is possible. In one such exemplary case, biocompetence (e.g., facial and / or voice recognition) (including retinal scans, blood type monitors, fingerprint scans, etc.) are embedded within the monitoring client 1. It can be associated with or linked to other things. Device dock 104 is Unique patient identifiers are used by the monitoring client dock 102, monitoring client 1, and monitoring server. 3. Remote communicator 11, other monitoring client 4, another server or computer unit By communicating with them, the treatment of patient 2 can be facilitated.

[0212] Monitoring client 1 is a microprocessor, microcontroller, logical device, Equipped with one or more digital circuits, analog circuits, etc., for the care, condition, illness or Information related to treatment can be communicated (e.g., sent or received). For example, monitoring Client 1 provides patient information such as patient status parameters and / or patient treatment parameters. Patient status parameters can be sent or received. Some example patient status parameters The device measures blood pressure, body temperature, heart rate, pulse oximeter, CO2 level, blood oxygen level, and patient. These are measures such as the patient's alertness, the patient's consciousness, and the patient's response. Several exemplary patient treatment patterns Lameters include the drug being administered, the flow rate of the drug or liquid, the drug administration schedule, and Other bedside treatment parameters can be mentioned.

[0213] In some embodiments, for example, the monitoring client 1 physically interacts with the injection pump 7. It can be attached in series, permanently installed, and can be removed from there. It is possible to attach or detach it. This is possible for two devices, for example docking between the monitoring client dock 102 and the device dock 104 This can be achieved by a turf. In one such embodiment, a monitoring turf Ant 1, for example, through electrical contact with docks 102 and 104, connects to the electrical connector. Or, using the respective antennas 112 and 122A, the transceivers on each device The pump 7 (or other patient care device) is connected wirelessly by several means, including the B-c. It communicates. In addition, or alternatively, the injection pump 7 monitors the cry When Ant 1 communicates in an operational manner, certain information is uploaded to monitoring client 1. It may include pre-programmed treatment data indicating specific treatments for patients.

[0214] Monitoring client 1 also has access to one or more databases within facility 8 and outside of facilities 9 and 10. The department's database and / or (including, for example, physicians, nurses, and pharmacists) It can communicate with healthcare providers using the portable communicator 11. This is (for example, Category 5 Local Area Network Connector, USB) Wired connection to equipment server 8 via connectors in the patient's room (such as wired Ethernet) By or wirelessly (e.g., WiFi, 3G, 4G, EVDO, WiMAX, etc.) In 12, this can be achieved. In one embodiment, intra and extra equipment Access to the database is through monitoring server 3 (for example, using middleware). Intermediary 13, then, software and application programming interface Focusing on the face, data with heterogeneous organizations, formatting, and communication protocols. It can communicate with the database. Therefore, in embodiments of this disclosure, any software Software updates can be largely limited to monitoring server 3, and individual monitoring clients 1, 4, 1 1. Maintenance requirements can be reduced. Optionally, monitoring client 1 can inject It communicates with patient treatment devices such as Pump 7 to monitor the progress of treatment (including operating parameters). It can receive information and provide operational instructions to the patient treatment device. In another embodiment, The monitoring client 1 also communicates with patient care devices for diagnostic or monitoring purposes. Then, patient status parameters (e.g., electrocardiogram (ECG) monitor 14, blood pressure (BP) monitor) 15. Pulse oximeter or CO2 capnometer 16. Other devices such as temperature monitors It receives (such as a device), receives read information from the device, and potentially the device Chairs 14, 15, 16, and 17 are desired by the provider or by the algorithm. You may instruct it to perform a read operation in certain cases.

[0215] In embodiments of this disclosure, the facility service 8 and / or the adverse drug event network 9 are Furthermore, it can be equipped with a medication error reduction system (DERS). The DERS system is soft A predetermined set of criteria for activating the alarm, and / or hard alarm It may include a second set of predetermined criteria for starting the alarm. This uses the user interface of the injection pump 7 and / or monitoring client 1. It can be disabled (for example, stopped) by a caregiver (and also audible and / or (or it may be just a vibration alarm), on the other hand, a hard alarm is issued when the cause is removed. Suspend treatment until it is cured.

[0216] In further embodiments of this disclosure, the DERS system defines a soft limit. A first set of predetermined criteria, and / or a second set that defines hard limits. It may include the following criteria: hard and soft limits, body size, weight, age. Based on other patient parameters or other criteria, treatment limits such as drug dosage limits are set. The soft limit is defined even if the treatment falls outside the prescribed criteria of the first set. Instead, use the user interface of the injection pump 7 and / or monitoring client 1. It can be rendered ineffective by the caregiver and treatment can be initiated, on the other hand, hard re The mitts are modified to meet the specified criteria of the second set that define the hard limits. Prevent treatment from starting until it is corrected.

[0217] As can be seen further in the exemplary embodiment of Figure 1, the system 100 also includes a communication module. It is equipped with antennas 124A~124K, and each has its own antenna 122A~122K. It has. In some embodiments, each of the communication modules 124A to 124K is responsible This is optional, and / or each device may have integrated communication capabilities. Each of the communication modules 124A to 124K is coupled to its respective device. It is equipped with a connector. In other embodiments, it is the same as that of the communication modules 124A to 124K. It is permanently integrated with the device shown as attached in Figure 1. Yes, they are.

[0218] Each of the communication modules 124A to 124K can optionally include one or more wireless links. Through this, the device dock 104 and the monitoring client dock 102 communicate with each other. To the viewing client 1, to the remote communicator 11, to the monitoring server 3, to the local area Networks and / or wide-area networks (e.g., the Internet) Through this, to communicate with Hub 802 (see Figure 8), and / or otherwise One or more transceivers for communicating with any other device that has sufficient wireless communication capabilities It is equipped with a . In some specific embodiments, communication modules 124A~124K Examples include IEEE802.14.4, Zigbee, XBee, Wibree, and IE. Using EE802.11, for example, it can operate as a wireless mesh network. This is possible. In a more general sense, modules 124A~124K and system 100 Other components (e.g., docks 102 and 104, monitoring clients 1, 4, 1) Communication between (e.g., 1) and (e.g., monitoring clients 1, 4, 11 and / or) is, for example, (e.g., monitoring clients 1, 4, 11 and / or) (or static to accommodate the mobility of various medical devices associated with Dock 104) Whether dynamic or ad hoc topology, the device is configured as described herein. Anything that enables chair discovery, handshake, and / or interdevice communication This can be done using wireless communication protocols.

[0219] In other embodiments, each patient care device may not have a module, It may have three or more modules (for example, communication modules). For example, each module Joule can have certain functions, such as WiFi, and users can have those specific functions. Multiple modules can be selected and combined with each other. The group of components can then be applied to patient care devices, such as infusion pumps. Considering yet another embodiment, each module consists of a primary processor, a backup processor, and a It may have a transistor and functional circuits, all of which communicate with each other in an operable manner. The functional circuitry includes wireless transceivers, batteries, and touchscreens or displays. Interface (allows the display to be attached to the housing), wire connection, Bluetooth, Bluetooth Low Energy, WiFi, 3G, 4G, Coprocess A control system (for example, to control an injection pump), and a fluid measurement circuit for injection. It could be a drug or something similar. Selected modules can be connected to each other, for example, in a daisy-chain. It can be connected, and then it can be connected to the injection pump. Selected module In this embodiment, for example, via CAN bus, wired communication, wireless and / or other means, They can communicate with each other in an operable manner in order to coordinate their operation and / or functions. .

[0220] Each module can be equipped with a speaker and a microphone. If those modules are connected to each other, these modules are one module One module sends an audible signal to the speaker, while another module uses a microphone. By adjusting its operation in this way, it determines whether the speaker is functioning properly. This is possible. Several modules each use their speaker at different frequencies. This allows any one of the modules to produce sound through its microphone. It can detect voices, demodulate their different frequencies, and simultaneously test several speakers. Yes, it is possible. The inspection may be requested from the second module by the first module, and the second The module can send the test results to the first module.

[0221] Referring to Figure 1, one or more of the communication modules 124A to 124K are also optional. The selection allows for the use of one or more batteries to power the connected device. For example, the communication module 124A is coupled to the injection pump 7 and supplies it with power. It is possible. Other structures and functions of communication modules 124A~124K are available to them. It can be provided depending on the purpose and function of the associated device. For example, In some embodiments, injection control is performed by an injection pump, and inputs regarding the desired delivery are received by the injection pump. This is done by the pump, and in this manner, in some embodiments of the present disclosure, the communication module 12 4A executes a control algorithm, such as a proportional-integral-derivative (PID) control loop, and injects Control pump 7. In such a case, monitoring client 1 can, for example, (for example, wirelessly) The fluid flow signal can be communicated to the communication module 124A (via the link), and Subsequently, the fluid is passed through electrical contacts connected to the motor (not explicitly shown) of the injection pump 7. A signal corresponding to the flow rate signal is applied to achieve the desired flow rate. Several implementations In this configuration, the injection pump 7 receives a flow meter installed inside the injection pump 7 from the communication module 124 A is provided with one or more feedback signals, thereby the communication module 124 A controls the operation of the injection pump 7 (for example, several modes of operation such as a PID control system). It can be controlled. The results are sent to monitoring client 1 and QT-based G It can be displayed to the user using a GUI such as a UI (in some embodiments) (Monitoring client 1 is a tablet). In addition to that, or as an alternative, several In one embodiment, a drip flow meter 148 is used, and the drip flow meter 148 is associated with Through the signal module 124K and antenna 122K, traffic flows to the communication module 124A. It can communicate wirelessly.

[0222] As can be seen in light of this disclosure, communication modules 124A to 124K are used for various patient care Operable with protection devices 7, 14, 15, 16, 17, 35, 126, 128, and 148. It can be combined. For example, referring further to Figure 1, the communication module 124B is a series The communication module 124C is operably coupled with the dispenser pump 126 and the pill dispenser 1 It is operably coupled to 28. In addition to, or as an alternative, communication module 12 4E is operablely coupled to the ECG monitor 12, and the communication module 124F is connected to the blood pressure monitor The TA15 is operably coupled, and the communication module 124G is a pulse oximeter / C The O2 capnometer 16 is operably coupled, and the communication module 124H is connected to other monitors. Operablely coupled to 17, the communication module 124I is connected to the patient's intravenous access 35. The communication module 124K is operably coupled to the drip flow meter 148. Each communication module 124A~124K is coupled to each Patient care devices 7, 14, 15, 16, 17, 35, 126, 128 or 148 For example, providing a suitable control system, control algorithm, battery power supply, or other functions. It is possible.

[0223] In addition, or alternatively, in some embodiments, a communication module 124D It is docked within the device dock 104, for example, a bus or backplane It is operably coupled to the device dock 104 via and attached to the device dock 104. It communicates with all connected devices and, together with them, the electronic circuits in the device dock 104 , electronic circuits in the monitoring client dock 102, and / or monitoring client 1 and To communicate. Optionally, the communication module 124D is docked within the device dock 104. Any device that has been manufactured, such as injection pump 7, syringe pump 126, pill dispenser To the dispenser 128 or microinfusion pump 130, communication and / or It can supply power. The function of the communication module 124D is also device dock Note that it can be integrated into the circuit of the 104 itself.

[0224] In addition, or alternatively, in some embodiments, the communication module 124 is Each requires one or more wired power sources, for example, the bus or back in the device dock 104. Each device can be powered by a power source accessible through the plane. Configure to provide sufficient power to 7, 14, 15, 16, 17, 35, 126, and 148. Doing so is optional. As described above, in some embodiments of this disclosure, communication Module 124D provides sufficient power to devices 7, 126, 128, 130, and 133 To provide.

[0225] As described above, in some embodiments, the communication module 124 is sufficient Power circuits that supply power to the corresponding devices 7, 126, 128, and 130 (for example) Voltage converters, regulating circuits, rectifier and filtering circuits, buck circuits, boost circuits, It consists of a buck boost circuit, a switch-mode power supply, etc. In this case, this power circuit is used in various different patient care devices 7, 14, 15, 16, 1 Various power supply characteristics associated with 7, 35, 126, 128, and 148 (e.g., voltage) Configure to enable the provision of (level, maximum load / current requirements, and A / C frequency). This is possible. Any number of power supply and management schemes are obvious in light of this disclosure. That is the matter.

[0226] Optionally, in other embodiments of the present disclosure, one or more battery cells, for example, lithium-ion A power module 132 having an on-battery cell is attached to the device dock 104. Therefore, sufficient power is supplied to devices 7, 126, 128, 130, and 13 throughout the entire duration of treatment. Provided to 3. In addition, or as an alternative, the power module 132 is available in In combination, plug it into the outlet in the patient's room (generally shown as an AC source in Figure 1). This is possible. In such cases, if outlet power is available, it will be used, and the dock It supplies power to the devices in 104 and charges the battery contained in the power module 132. This can be done (this may be done simultaneously). Outlet power is lost, or Otherwise, if not available, power module 132 and / or communications module The batteries in the 124A, 124B, and 124C provide power to the docked device. It is possible.

[0227] The exemplary system 100 may optionally include a dongle 133. Glu 133 is docked within the device dock 104 shown in Figure 1, or otherwise In this embodiment, the device dock 104 and / or monitoring client 1 are remotely It may be a distance. Dongle 133 is a communication device for wireless devices that is not available to others. It can provide a link or protocol. For example, a new wireless protocol, tech As technologies, standards, and techniques become available over time, dongle 133 can be used. It provides a bridge, router, or repeater between new communication protocols, and one platform Information transmitted in a protocol can be converted to other protocols, thereby The new protocol devices are patient care devices 7, 14, 15, 17, 35, and 12. 6, 128, 130, Device Dock 104, Communication Module 124D, Surveillance Crypt Doc 102, monitoring client 1, hub 802 and / or other devices in Figure 8 It can communicate with the monitoring server 3 or the monitoring client. The dongle 133 can communicate with the monitoring server 3 or the monitoring client. In formats known to or used by each other, such as Ant1, patient care devices Chairs 7, 14, 15, 17, 35, 126, 128, 130, Device Dock 104, Communication module 124D, monitoring client dock 102, monitoring client 1, Figure 8 Wireless network used by one or more of the Hub 802 and / or other devices Using a rotocol, technology, standard, or technique, data received from a new communication link The data can be retransmitted. Dongle 133 also acts as a communication bridge, EVDO and This can be provided to mobile-based communication links, such as CDMA-based mobile systems. ru.

[0228] In some embodiments, the dongle 133 transmits patient data from one or more patient care devices to the patient. Communication of care parameters, such as patient treatment parameters or patient status parameters, This is to be retransmitted to monitoring client 1, hub 802 in Figure 8, and / or monitoring server 3. This is possible, and vice versa. In some embodiments, the dongle 13 3 can be equipped with a wired mounting connector, such as an RS-232 connector, and legacy... The device is connectable and allows communication from the legacy device to one or more other patient intermediaries. The monitoring device, monitoring client 1, hub 802 and / or monitoring server 3 in Figure 8, etc. We provide legacy devices, such as legacy patient care devices and legacy computing devices. This could also include a chair, or other devices using legacy wired communication protocols.

[0229] Optionally, System 100 also supports various devices, docks, and monitoring clients. Equipped with a wearable system monitor 131 for monitoring the operation of the server and / or the server. This can be achieved by monitoring client 1, remote communicator 11, and / or Figure 8. The wearable system monitor 131 is programmed using hub 802. It can interact with and / or pair with this wearable. The system monitor 131 can be worn by patient 2 or provider, and many The wearable system monitor 131 can be used. The Tem Monitor 131 will contact various devices to ensure proper operation. This is possible. For example, in one exemplary embodiment, a wearable system monitor 1 31 is patient care device 14, 15, 16, 17, 35, 126, 128, 130, supervision View client 1, monitoring client dock 102, device dock 104 and / Alternatively, it communicates with the hub 802 in Figure 8, in case of any malfunction, error, malfunction, data corruption, or communication degradation. Determine if there are any malfunctions, slow operation, or other problems.

[0230] Communication from the wearable system monitor 131 includes one or more query signals. Furthermore, it checks whether the device being inquired about is functioning properly and within the specified operating parameters. Is it functioning, and / or is it otherwise in an undesirable state or situation? It can determine whether it is working. The system monitor 131 controls the monitoring server 3 and the monitoring client. The detected status or error is communicated to one or more devices, such as T1 or Hub 802 in Figure 8. Then, an alert is sent to the provider, a shutdown procedure is initiated, and / or the system is running normally. It can initiate other appropriate therapeutic actions instructed by a device that is not currently functioning. For example, The system monitor 131 monitors client 1, the network and / or interface. The monitoring server 3 and other monitoring clients 4 are connected to the network via a Wi-Fi router. Communicates with other devices, which consist of the signal module 124 or the remote communicator 11. Using the transceiver of communication module 124J, an abnormal query response or query response The absence of a warning and / or alarm signal can be sent. The be / or alarm will cause the device to alert and / or sound an audible alarm. or can be made visible. In some embodiments of this disclosure, the system monitor Ta131 is a call button that allows patient 2 to make requests to the care provider. It includes (not explicitly shown) features, for example, enabling requests to be made to the user who owns the device. To indicate visually and / or audibly, the request is made to monitoring client 1 or remote communication It is routed to Nikator 11.

[0231] The system monitor 131, for example, (1) predicts a response to an inquiry within a predetermined time. (2) Increment a counter within the device receiving the query, and after the increment is complete. (3) Requesting the value of the counter from the vice, Challenge-response type query, and / or (4) the function in various ways, including other system monitoring techniques or methods. It can be implemented.

[0232] As described above, in some embodiments, the system monitor 131 is a system monitor After contacting the patient care device paired with Nita 131, the question will be answered within the specified time. Predicts the response to the match. For example, System Monitor 131 is "System Monitor A text string message "Inquiry" can be sent to the injection pump 7. (Example) Then, the injection pump 7 receives a message labeled "System Monitor Inquiry". The system monitor 131 receives the message and uses one or more of its processors to send the message. The message is processed. When the injection pump 7 processes the message, the software within it... Chin executes code to send a response message to system monitor 131 again, for example. For example, the response message is sent to the system monitor 131 as a "system monitor response". This may also be a text string message. In this embodiment, the system monitor 131 It can predict that a response message will be received within a predetermined time, such as 2 seconds. If the system monitor 131 does not receive a response message within 2 seconds, the system monitor The TA131 sends a warning and / or alert to other devices (e.g., system mo Nita 131 can broadcast warning or error messages, or alarms. This provides alerts to the processor via the remote communicator 11, either audibly or visually. (It is possible to do so.)

[0233] As described above, in some embodiments, the system monitor 131 receives inquiries. The counter within the device is incremented, and after the increment, the device is requested to retrieve the value of the counter. For example, the system monitor 131 displays messages such as "increment counter" on the device. By sending it to the system, the request is sent to the patient care device, for example, the infusion pump 7. This is possible. The device's processor receives the "increment counter" message, and the device Read the value from the memory location, increment the value found at the memory location, and overwrite the previous value. By doing so, a new value is stored in the same memory location. Then, in this embodiment, the process S reads a new value from the memory location and displays the new value to the system monitor 131, for example. The message is transmitted via the wireless transceiver on the device receiving the inquiry. System Monitor In this embodiment, TA131 predicts a specific value from the device receiving the query (this The predicted values ​​are stored in the system monitor's memory, for example, in a table. (This is possible). For example, the system monitor 131 can retrieve 48 values ​​previously received from the device. It can be stored in that memory, and the value needs to be updated within the device that receives the query. After calculating, it is expected that the device will receive a value of 49.

[0234] Furthermore, as mentioned above, the challenge-response query is handled by System Monitor 1 It can be used by 31. For example, the system monitor 131 is encrypted Messages can be sent to patient care devices. The patient care devices then, for example, For example, the encryption key is used to decrypt the message and send the message to the system monitor 131. The task is given to send again. System monitor 131 is not encrypted. It is possible to predict that the message will be returned within a predetermined time. In this embodiment, the system If the monitor 131 does not receive a response message within a specified time, the system monitor 131 alerts and / or sends warnings to other devices (e.g., system...). Monitor 131 can broadcast warning or alarm messages, and / or These are monitored by monitoring client 1, monitoring server 3, hub 802 in Figure 8, or remote communication It can be transmitted to the 11, and thereafter a warning or alarm can be displayed or audibly indicated. ).

[0235] In embodiments of this disclosure, the monitoring client 1 is a handheld or portable remote communication device. Niketa 11 (for example, smartphones, tablet computers, PDAs, laptops) Using a laptop or other portable computing device, healthcare professionals It has the ability to communicate with and interact directly with the VIDA. This is achieved by wireless 12. This allows for the determination of the patient's location within the facility, or the provider's location within or outside the facility. Communication can be maintained regardless of the location of the device. In one embodiment, the patient 2 is unique to the device. The information can be stored locally within the monitoring client 1, thereby allowing the patient to... Healthcare providers can access the information directly without needing to access monitoring server 3. It is possible.

[0236] In some embodiments, optionally, appropriate safety and security checks are performed. By incorporating it, the connected infusion pump 7 or patient monitoring device 14-17, 3 Changes to settings or flow rate parameters 5, 126, 128, 130, and 148 are (Yes (via wire or wireless communication) the provider's monitoring client 11 and monitoring client 1 This can be achieved directly between them, and the selected changes can also be made to monitoring server 3, therefore any The selection involves communicating to Nurse Station 5 and / or other appropriate locations such as Pharmacy 6. It is possible to remotely issue any new instructions regarding patient 2 to the issuing provider. The information is entered into communicator 11 (for example, a smartphone) and transmitted to monitoring client 1. This allows the caregiver to communicate via their own portable communicator 11 (e.g., For example, nurses, nurse practitioners, doctors, internists, or other healthcare professionals. This can be communicated to. In addition, or alternatively, in some embodiments New instructions for infusion pump 7 or patient monitoring devices 14-17, 35, 126, 128 It can communicate with 130 and 148, thereby being in or connected to them. The controlled system can change its operation, for example, set points, in response to new instructions. Yes, it is possible. In some embodiments, any data obtained and stored within the monitoring client 1 The information is periodically uploaded to monitoring server 3 and stored in a patient-specific database. Therefore, if patient monitoring client 1 is not working, a new device will be sent to the patient. Assigned to 2, it allows for quick re-addition of the patient's current information from monitoring server 3. Instructions, medications, progress notes, monitoring data, and treatment dates from the patient's implanted devices. Patient treatment parameters, patient monitoring parameters and / or operating parameters are also permanent. For permanent, temporary, or transient memory, and / or a predetermined standard, e.g., range, threshold. For analysis to confirm that the values ​​are being followed, monitor client 1 will provide data on the patient's condition. EHR19, any applicable remote communicator 11, hub 802 and / or This can be uploaded to monitoring server 3.

[0237] In some embodiments, the monitoring server 3 controls several monitoring clients 1 within the facility 8. ,4,11 communicate with several elements of control and can provide this computer It may be equipped with a monitor. The monitoring server 3 communicates to monitoring clients 1, 4, and 11 within the facility 8 Data extracted from numerous databases both outside the facility and outside of the facility may be provided. In this embodiment, the monitoring server 3 uses the EHR of the facility to obtain target information about patient 2. The system 19 is contacted, and then a predetermined set of information is sent to the patient's monitoring client 1. Report (e.g., patient's age, height, weight, disease category, current medication and medication category) (e.g., drug allergies and hypersensitivity) can be added. One such example According to the report, monitoring server 3, for example, when monitoring client 1 is assigned to patient 2 Within the facility, there are 19 EHRs, 20 laboratories, 21 radiology departments, 22 pharmacies and / or other systems. For systems (e.g., heart disease 23 or scheduling database 24, etc.) A communication link may be established. With a unique patient identifier, monitoring server 3 will receive patient-specific data. To obtain electronic access (permission) to receive from and transmit to these systems. This is possible. A predetermined (selectable) subset of the data is stored in the memory of monitoring client 1. It can be downloaded within (not explicitly shown in Figure 1).

[0238] The information obtained in this way can then be used to analyze new instructions in comparison to this information. - It can function as a database. Input is entered into monitoring client 1. The instructions are checked for compatibility with patient-specific information obtained by monitoring server 3. Yes, it is possible. In optional mode, for security reasons, the finger input remotely from communicator 11 is used. The information can be intercepted and checked by monitoring server 3. The visual server 3 also obtains information from the drug database located in the facility's pharmacy 22 or externally 9. Whether new patient instructions may result in incompatibility with the patient's existing medications. It can determine. In embodiments of this disclosure, the monitoring server 3 uses generally available information. Programmed to access Tarnet Site 25, patient-directed medications Download new information regarding this to alert the patient's healthcare provider(s). It can be determined whether to transmit it as a warning or alarm. The monitoring server 3 Furthermore, information is exchanged between the remote portable communicator 11 and the patient monitoring client 1. It can be routed.

[0239] In embodiments of this disclosure, the patient's physician, nurse, or pharmacist may provide new information regarding patient 2. To relay or receive instructions (e.g., medication instructions), patient monitoring client 1 It can have access to the monitoring client 1 or server 3. Record the instructions and make the request to the pharmacist and the patient's nurse, using the nurse's portable communication device. Relayed via nikata 11 and / or via the fixed terminal at nurse station 5. It may also have a customized communication application with monitoring client 1. "Smartphone" (for example, Google's Nexus One phone, etc.) (Pull iPhone, or RIM BlackBerry OS) (Office or remote A portable solution that is convenient for providers who are not located in a fixed location (such as a station). You can work as Communicator 11. Tablet PC, netbook, or Top-top computers are also convenient for both portable and fixed-location use. It can function as a double communicator 11. The PC can be fixed or desktop. It can function as a convenient communication device 11 for location. The provider can access the patient's room. If located, the provider will monitor the keyboard or touchscreen on client 1. Information about patient 2 may be entered or received using direct input.

[0240] Monitoring client 1 obtains information about a specific patient 2 that has been assigned or designated. It can receive, process, and transmit. Monitoring client 1 is the injection pump 7, or To communicate with any other devices that can connect to or associate with patient 2, It is most conveniently attachable to or dockable with the client dock 102. The monitoring client 1 is, for example, roughly the size of a wireless phone or a tablet netbook. It may be a handheld device. Monitoring client 1 is provided by the patient's provider. It is convenient to have a touchscreen interface for use. Also, wired Alternatively, via a wireless connection, within the patient's room, or at the nurse's station 5 It can provide output to a larger, fixed display located in another convenient location. Each monitoring client 1 can communicate with the central monitoring server 3, and through this, settings EHR database 19, laboratory database 20, radiology database 21, pharmaceutical Patient data from the bureau database 22, or other databases in various other facilities departments. It can access. In some cases, monitoring client 1 can access monitoring server 3. The patient's EHR19 can be accessed from patient monitoring devices 14-17, or via provider input. It can upload the information it receives. Monitoring clients 1 and 4 can also Information is received from an external database via a monitoring server 3 with a network connection 25. Therefore, various drug information databases that handle adverse drug-related events can be used. Various external databases 9, including security and surveillance networks, are accessible.

[0241] Monitoring server 3 helps, for example, keep the contents of monitoring client 1 as up-to-date as possible. It can be arranged to manage external database information at various levels. This, for example, compares patient-related safety and drug information when it becomes available, and This can be achieved by prioritizing updates / downloads on the data transfer schedule. It is possible. Monitoring clients 1 and 4 also provide support to healthcare professionals such as nurses, physicians, and pharmacists. The portable communicator 11 used by the Scare provider is used directly or They can communicate through monitoring server 3. In some cases, these devices (For example, when used in a fixed location such as a hospital pharmacy or nurse's station) ) It can have a wired connection to monitoring server 3. In other cases, portable communication The nikata 11 connects to the computer and device 11 via wired or wireless connection (e.g., blue Use a secure internet connection via Tooth or WiFi (802.11) connection 13. (For example, VPN-based internet connection, UPN, HTTPS, private key It can communicate with monitoring server 3 through (a mechanism, etc.). Alternatively, (smartphone The handheld remote communicator 11 (for phones, tablets, netbooks, etc.) is portable. The equipment may communicate directly with the monitoring client 1 via the telephone network, and / or the equipment is connected to a WiFi network (e.g., 2.4GHz to 2.4835GHz) Even with a private cell network that can include an unlicensed ISM band. good.

[0242] In some embodiments, the communication link between monitoring clients 1 and 4 and the monitoring server 3 However, if widely available within the facility, it can be done via an Ethernet network, or several It exists via wireless transmission using one of several standards, and all patient-specific monitoring criters Points 1 and 4 can be linked to the central monitoring server 3. Server 3 can then configure other settings 8 servers, 25 web-based servers, and the servers owned by the healthcare provider. To function as a relay for communication with the portable communicator 11 inside and outside the facility. This is possible. In some embodiments, the wireless network can determine where patient 2 is located within the facility. Regardless, it provides additional functionality that allows communication with monitoring server 3.

[0243] One way to cover the entire facility with wireless range is to have a private cell phone network on the facility. A license must be obtained. A local communication network must be provided throughout the entire facility. To do this, one or more micro-cellular frequencies can be obtained or rented. The arrangement allows patients and monitoring clients 1 and 4 to move from one location to another within the facility. When moving, maintain communication with monitoring server 3 and various in-hospital and out-of-hospital databases. 8, 25 and fixed stations (for example, in some embodiments, nurse stations) Monitoring users of 5 and 6) or either inside or outside the hospital Ant 11 (for example, mobile smartphones, laptops, or tablet types) It can maintain a connection with the device. In some embodiments, this type of The system provides additional security through authorized mobile communication infrastructure. In addition, in some embodiments, the active radio system uses a usage intensity within an area. It is possible to monitor and instruct additional channel frequencies in that area. However, some In this embodiment, the network bandwidth capacity is large, for example, including radiographic images. This can prevent the efficient transmission of large data files. Data files can be transmitted more efficiently via a wired connection.

[0244] Alternatively, or in addition, hospitals may use internet or intranet-based communication. The communication system can be implemented, and within that, the 802.11 WiFi type protocol This is used for wireless communication between individual monitoring clients 1 and 4 and the monitoring server 3. To ensure proper signal reception through the body, a broadband antenna is installed locally. To collect mobile phone signals from wireless telephone companies, they are installed on the roofs of buildings. This is possible. The fiber optic or cable network then transmits signals throughout the entire facility. Null can be distributed. In addition, or alternatively, monitoring server 3 can, The private mobile phone network described can be used. Typically, it is possible to provide secure communication, for example, a radiation database. It is possible to efficiently communicate large files, such as radiation images, stored within the 21. Yes. Home or office-based users can use, for example, VPN or wired or fiber optic connections. Another secure access method using fiber optic cable, or via DSL telephone line to the hospital server. It is possible to connect to it. Data encryption is used to ensure patient data security. It can be provided. In some applications, asymmetrical, to optimize infrastructure capabilities. It can be advantageous to implement a bandwidth communication network. This embodiment involves monitoring Authorized mobile frequencies are transmitted in the "upstream" direction from Lian 1 to monitoring server 3, and monitoring server Unlicensed 802.11 WiFi frequency in the "downstream" direction from B3 to monitoring client 1 This uses the upstream bandwidth and data transfer rate requirements, while the downstream requirements It is relatively small compared to the number of cases. In low-priority upstream communication, monitoring client 1, for example ZigBee network, Bluetooth network, mesh network This makes it possible to transmit data through more decentralized and cost-effective networks. I'll do that.

[0245] As mentioned above, various monitoring devices such as patient care devices 14, 15, 16, 17, and 35 Communication between the vice and the monitoring client 1 is, for example, via a ZigBee wireless mesh network. Using a network and / or Bluetooth network, in a cost-effective way This can be achieved. Examples of monitoring devices include, in particular, an ECG monitor 14 and a blood pressure monitor. Examples include a monitor 15, a pulse oximeter / capnometer 16, a thermometer, and a weighing scale. A common feature of most of these devices is the periodicity of one or a few parameters. This involves performing a specific read operation. This is related to communication between devices within a hospital, such as wireless mesh networks. The system provides low-power digital wireless connectivity between devices and is widely available. Utilize sense-free frequency bands (e.g., 2.4 GHz in some jurisdictions). This is possible. It utilizes high-level communication protocols such as TCP and UDP to track data traffic. Authenticity and security can be guaranteed. For example, using a symmetric encryption key, T wofish, Serpent, AES(Rijndael), Blowfish, CA This is generated for cryptographic algorithms such as ST5, RC4, 3DES, and IDEA. This ensures communication between the monitoring client and the patient care device. In addition to, or as an alternative to, for example, CRC, odd parity bit check, and It can use various data integrity techniques, such as even parity bit checks. Cut.

[0246] Mesh networks are highly scalable and allow many devices to form a single self-organizing network. Enables use on a self-healing mesh network. The connected devices can communicate with each other and act as repeaters to transfer data. Mesh networks are relatively low-cost, scalable, and monitored. It is portable for patients. In some embodiments, a wireless mesh network The wireless range for linked devices is 70 meters from each node of the system within the facility. It can reach Toll. Patient monitoring clients 1 and 4 provide healthcare • The provider has a portable communicator 11 and its assigned patient A similar network may be used to provide wireless links within the facilities.

[0247] In many cases, the information transmitted to monitoring client 1 is a single parameter value (for example, It can include blood pressure, etc., and a time stamp. Monitoring client 1 will find the value Determine whether the value is outside the specified range, record the value in the patient's EHR19, and monitor the client. It can be programmed to notify the appropriate provider via T11. The network enables bidirectional communication, and monitoring client 1 can connect with a patient monitoring device (for example) Then, consult the BP monitor (15) and instruct it to perform an unscheduled read. This is possible, for example, when an abnormal read is received and its authenticity needs to be verified. It may be useful when necessary. Monitoring client 1 requests repeated readings. In another embodiment, the monitoring cloud can be programmed to verify abnormal readings. Iant 1 receives readings from monitoring devices 14-17, and the injection pump 7. Interrupt or adjust the flow rate, operating parameters and / or therapeutic parameters. It can be programmed. For example, if the BP monitor 15 shows a blood pressure below a predetermined tolerance range. In this case, the monitoring client 1 instructs the injection pump 7 to stop the injection. It can be programmed to provide emergency notifications to one or more healthcare providers. This can be communicated to client 11. In another embodiment, the infusion pump 7 is used to deliver to patient 2. The amount of fluid being delivered (for example, the flow rate or cumulative amount of fluid pumped in over a period of time) If it is possible to determine the delivered, the processor in monitoring client 1 will determine the delivered The cumulative amount can be tracked, and the amount of fluid remaining in the drug bag 170 can be estimated. Alternatively, the processor in monitoring client 1 or injection pump 7 controls the injection rate and The amount delivered may be calculated from the time elapsed since injection.

[0248] When the estimated residual amount reaches a predetermined amount, the monitoring client 1 will instruct the injection pump 7 to Send a Gnar to reduce its flow rate and prevent the patient's intravenous access 35 from becoming empty. It is possible. For example, monitoring client 1 can identify when a nurse needs to change a bag. It was determined that the nurse was scheduled to return at a certain time, and the intravenous fluid was administered at the nurse's scheduled return time. Rather than warning and / or sending an alarm about it disappearing beforehand, monitoring Nurse 1 is determined by the time the nurse arrives or the time the nurse is scheduled to return. The infusion pump 7 is set to slow down the infusion rate so that the intravenous bag will be empty after a set time. You may send a message. Also, a notification recommending the replenishment of intravenous bag 17 should be sent to the nurse's monitoring client. You may send it to Ant-11.

[0249] In some embodiments, the progress of the operation of the patient care device is monitored by the monitoring client 1. The outer edge of the display indicates the status and / or progress of the patient care device. To show, for example, the proportion of the outer edge that is lit up (for example, as the outer edge is filled in, completely The formation of the embedded outer periphery is achieved by a patient care device, such as an infusion pump 7. The outer edge is displayed on the monitor client 1's display to show the progress of the treatment performed. This outer edge is monitored from the injection pump 7 in an image format (e.g., JPEG, BMP, etc.). It may be sent to client 1 and / or as a percentage value to the monitoring client It may also be sent to client 1, in which case monitoring client 1 creates the outer boundary.

[0250] In some embodiments, a GPS and / or ranging module (e.g., time-of-flight type) is used. An ultrasonic ranging module using estimation, infusion pump 7, monitoring client 1, caregiver and / or may be installed on the patient. The predetermined settings include the infusion pump 7, monitoring client T1, Hub 802 in Figure 8, a predetermined group of caregivers and / or patients, in this particular implementation In this state, before starting treatment, and / or infusion pump 7 and / or monitoring cryer Before forming one of the elements 1, they must be within a predetermined distance of each other. You may ask for it.

[0251] In some embodiments, patient care devices 7, 170, 126, 128, 130, 1 4, 15, 16, 17, 124 or 148, Dock 102 or 104, Surveillance Cryer Point 1, Hub 802 in Figure 8 (for example, to detect the cause of the alarm without confusing the patient) (To allow caregivers to find solutions to eliminate the problem) After a set amount of time has elapsed Until it is finished, the alarm-emitting device and / or monitoring client 1 will issue a warning. Without any soft alarm, hard alarm, and / or non-critical alarm The alarm may be sent to the remote communicator 11. If the cause of the alarm is removed before a specified time, If this occurs, the alarm-issuing device and / or monitoring client 1 will issue a warning. This may not always be the case, which can prevent further confusion for the patient.

[0252] In some embodiments, the AC cable in Figure 1 is equipped with a clip, thereby The venous duct can be clipped in there.

[0253] In some embodiments, the injection pump 7 is equipped with LED lights that display one or more of the following: ru: Passed safety check; pump is injecting; there is no blockage; and / ma The pump is turned off. The user uses monitoring client 1 to check (for example, (Using camera 144 or camera 136 and / or scanner 120) Intravenous The barcode on the 170 can be read, and at that time, the LED on the plug will blink. Then, the user is instructed to insert the tube connected to the intravenous bag 170 into it. It is possible.

[0254] In some embodiments, the numbers are as shown in Figure 1 or as described herein. Whether attached or not, each item, component, device, patient The care devices, docks, and computing devices are optional. For example, several practical In this configuration, monitoring client 1 is optional, and monitoring server 3 is optional. Service 8 is optional, and each of services 19, 20, 21, 22, 23, and 24 is optional. It is a choice, and the cloud server 25 is optional, and the other monitoring clients 4 are each This is optional, and the online drug database 9 is optional, and the drug adverse event network Twerking is optional, patient's personal EHR19' is optional, and / Alternatively, the treatment outcome database 10 is optional. In addition, or as an alternative, In some embodiments, each patient care device 7, 14, 15, 16, 17, 35, 12 6, 128, 130, and 148 are optional. Similarly, system monitor 131, RIS Band 118, RFID 116, barcode 114, scanner 120, display 134 and / or AC power supplies are optionally provided in some embodiments of this disclosure. be.

[0255] In addition, in some embodiments, as shown in Figure 1 or described herein There are several items, some numbered and some not, that are components. A single item containing a network, device, patient care device, dock, and computing device. , shown as component, device, patient care device, dock or computing device Although it is included, it is a collection of multiple items, components, devices, patient care devices, etc. A buck and computing device is intended. For example, a single injection pump 7 is shown in Figure 1. However, in some embodiments, two injection pumps 7 can be used. Multiple injection pumps 7 can be used, or any number of injection pumps 7 In addition, or alternatively, in some embodiments, Multiple device docks 104 and / or multiple monitoring client docks 102 It can be used.

[0256] In addition, or as an alternative, certain patient care devices 7, 14, 15, 16, 1 Although 7, 126, 128, 130, and 148 are shown, specific patient care devices Other combinations, subsets, multiples, or combinations thereof can also be used. For example, in some embodiments, only the infusion pump 7 among the patient care devices is used. In this particular embodiment, other patient care devices 14, 15, 16, 17, 126, 128, 130, and 148 are disabled and do not exist or are unavailable for system use. It may not be possible, the power may be off, or it may not be part of system 100 in Figure 1. In addition, or alternatively, in some specific embodiments, patient care is used. Only devices can be docked to the device dock 104. For example, this particular device In this configuration, the injection pump 7 is the only device docked within the device dock 104. The device dock 104 receives only one device, for example, the injection pump 7. In addition, as an alternative, or at the discretion of, in some specific embodiments, the patient Care devices 7, 14, 15, 16, 17, 35, 126, 128, 130, and 148 are It is dockable, can operate without docking, and / or docked It may not be possible to use it as a standalone patient care device. can.

[0257] In some embodiments, patient care devices 7, 14, 15, 16, 17, 35, 12 6, 128, 130 and / or 148, monitoring client 1, remote communicator 1 1, and docks 102 and / or 104, for example, via API, secure data. It may be possible to include a class.

[0258] All functions described with reference to Figure 1 are, in some embodiments, represented by the hub 802 in Figure 8. It may be done by [another method].

[0259] Figure 2 shows a monitoring client according to an embodiment of the present disclosure, for example, the monitoring client in Figure 1. 1 and one or more patient care devices, for example, patient care devices 7, 14, 15, 16 in Figure 1 , in order to maintain communication with one or more of 17, 35, 126, 128, 130, 148 A flowchart illustrating method 150 is shown. Method 150 in this embodiment involves actions 152-1 Includes 69. Monitoring client 1 communicates with paired and / or designated patient care An icon can be displayed to indicate when a monitoring device has been established. (Monitoring client) 1. Communication with paired and / or designated patient care devices is available at predetermined intervals. It can be checked to determine if it is available, pairing or designated patient If communication to the caregiver device is unavailable for a predetermined period of time, the monitoring client 1 It can sound an alarm or warning.

[0260] Act 152 is when the monitoring client dock transmits the monitoring client through the dock connector. Determine if it is available as a communication link between the dock and the monitoring client. If the communication link for act 152 is available, method 150 proceeds to act 154, and so on. If not, proceed to action 156 in method 150.

[0261] Act 156 is the monitoring client dock communicating with the monitoring client via a wireless link. Determine if it is available as a communication link between the monitoring client and the dock. Action 15 If link 6 is available, proceed to method 150 to action 154; otherwise, Article 150 of the law proceeds to Act 158.

[0262] Act 154 is when the monitoring client dock uses a cable to access the monitoring client. Determine if it is available as a communication link between the dock and the device dock. Action 1 If 54 communication links are available, method 150 proceeds to action 160; otherwise If so, method 150 proceeds to action 158. Action 160 is when the device dock is the device dock For example, a wireless or wired communication link can be used as the communication link between the device and the patient care device. Determine if it is available through. If the communication link for action 160 is available, the method If 150 proceeds to act 166, otherwise method 150 proceeds to act 162. Act 16 2. The patient care device communicates directly with the monitoring client via a wireless link. • Determine if it is available as a communication link to the dock. (Communication link in action 162) If available, the method proceeds to act 166; otherwise, method 150 proceeds to act 1 Proceed to 64.

[0263] Act 158 ​​involves the device dock monitoring the client and the device via a wireless link. Determine if it is available as a communication link to the dock. The communication link of action 158 is If it is not available, method 150 proceeds to action 162; otherwise, method 150 proceeds to action 162. Proceed to 160.

[0264] Act 166 uses available communication links to connect monitoring clients and patient care devices Attempt a handshake with S. In an alternative embodiment, a handshake is used. For example, not all protocols use a handshake between communication endpoints. Judgment action 168 determines whether the handshake in action 166 was successful. If action 168 determines that the handshake in action 166 was unsuccessful, then action 164 , determining that communication with the patient care device is unavailable, and / or method 150 Attempts to establish communication using other links (not explicitly shown). Otherwise If, then, judgment act 168 determines that the handshake in act 166 was successful, act 16 9 uses a sufficient number of communication links determined to be available by method 150 To transmit data.

[0265] Method 150 maintains communication between the monitoring client and one or more patient care devices. This is an exemplary embodiment of the present disclosure, describing a method for doing so. In some embodiments, Method 150 includes scheduling of communication links, but other schedules can be used. You can use broadcast, anycast, multicast, or unicast. Routing algorithms can be used, including distance vector routing programs. Tocol can be used, and link-state routing protocols can be used. The optimized link state routing protocol can be used, and path vector • The protocol can be used, and static routing is used on a designated alternative communication path. This is possible and / or adaptive networks can be used. For example, this development In some embodiments of the diagram, weights may be assigned to each communication path, Dykes The TRA algorithm communicates between monitoring client 1 and one or more patient care devices. It may be used for any known purpose, such as bandwidth, signal quality. , may be determined as a function of the bit error rate, or the available data throughput or It may be linear to waiting time and / or similar factors.

[0266] Referring to the drawings, Figure 3 shows two docks 102, 10 according to another embodiment of the present disclosure. A block diagram of an electronic patient care system 300 having 4 and communicating wirelessly between them is shown. System 300 is similar to System 100 in Figure 1, but with a monitoring client dock 1 Communication between 02 and device dock 104 is via a wireless link. For example In some embodiments, the system 300 in Figure 3 is configured such that the cable 110 in Figure 1 is absent. The system 100 in Figure 1 is either in operation or not, and in addition to or alternatively Therefore, the system 300 in Figure 3 cannot be connected together with the dock 102 using a cable. It may also have 104.

[0267] In optional settings, instructions or requests can be made to patient care devices 7, 14, 15, 16, 17, and 35. To send to 126, 128, 130, 148, for example, bolus volume, injection flow rate, Measuring delivery fluid, drug delivery start time, drug delivery stop time, or delivery flow rate profile infusion pump 7, syringe pump 126 and / or microinfusion pump To send to the 130, monitoring client 1, other monitoring clients 4, and / Alternatively, a remote communicator 11 can be used. In some embodiments, for example For example, a pill dispensing instruction, pill type, pill dispensing schedule, and / Alternatively, send instructions or requests, such as maximum pill dispensing criteria, to the pill dispenser 128. Therefore, one or more of the monitoring clients 1, 4, and 11 can be used. Maximum pill distribution The standard is the maximum amount of drug that can be delivered within a given time, for example, a specific drug. It is taken as needed (i.e., when necessary), but if taken in excess, The drug may not be safe, and the maximum pill dispensing standard is, for example, "a prescribed amount within a prescribed time." This can prevent patients from taking unsafe amounts of medication.

[0268] In some embodiments, the remote communicator 11 is used, and the remote communicator 1 Open two-way audio / visual communication (e.g., video call) between device 1 and monitoring client 1. It can be started. In addition, or alternatively, using monitoring client 1, Two-way audio / visual communication between monitoring client 1 and monitoring client remote communicator 11 You can initiate a communication.

[0269] For optional selection, patient care devices 7, 14, 15, 16, 17, 35, 126, and 128 are available. ,130,148 also ask whether an alarm or warning should be issued or transmitted. The system determines whether the treatment or condition is safe for the patient, and the system 300 Determine whether it is operating properly or within a predetermined boundary, and / or monitor clients. T1, on the display of other monitoring clients 4 and / or remote communicator 11 To display the data, the data is collected by monitoring client 1, other monitoring clients 4, and You can reply to the call / or remote communicator 11. For example, in optional mode, Infusion pump 7, syringe pump 126, and / or microinfusion pump Pump 130 measures upstream pressure, change in upstream pressure, downstream pressure relative to patient 2, and relative to patient 2. Changes in downstream pressure, presence or absence of air in the injection line, actual bolus volume delivered, actual Injection flow rate, actual total fluid delivered, actual start time of drug delivery, actual drug delivery Downtime, or actual delivery flow profile, monitored by client 1, other monitoring clients Ant 4 and / or one or more of the remote communicators 11 (if applicable) It can be believed. In another embodiment, the pill dispenser 128 is optionally, for example The actual pills that were distributed, the actual type of pills that were distributed, and the actual distribution of pills at the time of distribution. Data such as whether the schedule or the maximum pill distribution criteria have been exceeded will be monitored by the client. The system replies to 1, other monitoring clients 4, and / or remote communicators 11. It is possible.

[0270] Patient care devices 7, 14, 15, 16, 17, 35, 126, 128, 130, 14 The data received from 8 will be used to issue alarms and / or warnings, at any predetermined time. The state can be analyzed. For example, one or more of the monitoring clients 1, 4, and 11. This includes an infusion pump 7, a syringe pump 126, and / or a microinfusion pump. The increase in the downstream pressure of pump 130 may cause excessive coagulation, osmosis, or blockage of the tube to the patient. This may be a manifestation of kinking or obstruction by other substances within the intravenous bag 170. It can be used in response to a rapid increase in downstream pressure, monitoring clients 1 and 4. One or more of the 11 may provide the user with a visual or auditory warning or alert. In addition, or alternatively, a rapid decrease in downstream pressure for patient 2 is a sign of This indicates that the tube has come off the needle, and / or the needle is now detached from the patient. Accordingly, one or more of the monitoring clients 1, 4, and 11 will provide the user with visual or auditory information. It can issue warnings or alerts to the target. One or more of the monitoring clients 1, 4, and 11 In optional selection, the flow rate changes depending on the rapid increase and / or decrease in downstream pressure for patient 2. To stop the delivery of the body, use infusion pump 7, syringe pump 126, and / or Instructions can be sent to one or more of the icloinfusion pump 130.

[0271] In some embodiments, the numbers are as shown in Figure 3 or as described herein. Whether attached or not, each item, component, device, patient Care devices, docks, and computing devices are optional. For example, several practical In this configuration, monitoring client 1 is optional, and monitoring server 3 is optional. Service 8 is optional, and each of services 19, 20, 21, 22, 23, and 24 is optional. It is a choice, and the cloud server 25 is optional, and the other monitoring clients 4 are each This is optional, and the online drug database 9 is optional, and the drug adverse event network Twerking is optional, patient's personal EHR19' is optional, and / Alternatively, the treatment outcome database 10 is optional. In addition, or as an alternative, In some embodiments, each patient care device 7, 14, 15, 16, 17, 35, 12 6, 128, 130, and 148 are optional. Similarly, system monitor 131, RIS Band 118, RFID 116, barcode 114, scanner 120, display 134, and / or AC power supply are each optional in some embodiments of the present disclosure. That is the case.

[0272] In addition, in some embodiments, as shown in Figure 3, or described herein There are several items, some numbered and some not, that are components. Networks, devices, patient care devices, docks, and computing devices are integrated into a single item. It is referred to as a component, device, patient care device, dock, or computing device. However, multiple items, components, devices, patient care devices, A docking station and computing device are intended. For example, a single injection pump 7 is shown in Figure 3. However, in some embodiments, two injection pumps 7 can be used. Multiple injection pumps 7 can be used, or any number of injection pumps 7 It can be used. In addition, or as an alternative, in some embodiments, multiple Using a number of device docks 104 and / or a number of monitoring client docks 102 It can be used.

[0273] In addition, or as an alternative, certain patient care devices 7, 14, 15, 16, 1 Although 7, 126, 128, 130, and 148 are shown, specific patient care devices Other combinations, subsets, multiples, or combinations thereof can also be used. For example, in some embodiments, only the infusion pump 7 among the patient care devices is used. In this particular embodiment, other patient care devices 14, 15, 16, 17, 126, 128, 130, and 148 are disabled and are not present or available for system use. It may not be, or the power may have been turned off, or it may not be part of system 300 in Figure 3. In addition, or alternatively, in some embodiments, only the patient care device used It can be docked to the device dock 104. For example, in a particular embodiment, The injection pump 7 is the only device docked within the device dock 104. The Vice Doc 104 accepts only one device, for example, the injection pump 7. In addition Alternatively, or at an optional, in some specific embodiments, patient care devices S7, 14, 15, 16, 17, 35, 126, 128, 130, 148 are docking. It is possible, and it can operate without docking, and / or it is dockable. It can function as a standalone patient care device.

[0274] In Figure 3, the device dock 104 can receive several patient care devices. Although it is shown to be so, in other embodiments, the device dock 104 is 1 One patient care device, multiple patient care devices, or any number of patient care devices You can receive a vice. Also, there may be dock sections that are not in use, for example As shown in Figure 3, an empty compartment 170 is shown within the device dock 104. In addition, the monitoring client dock 102 receives one monitoring client 1. Although it is shown that this is possible, in other embodiments, the monitoring client dot Ku 102 is a combination of two monitoring clients 1, three or more monitoring clients 1, or any It can receive any number of monitoring clients.

[0275] Figure 4 shows a monitoring client according to an embodiment of the present disclosure, for example, monitoring client 1 and One or more of the vices, for example, patient care devices 7, 14, 15, 16, 17, 35 in Figure 3, Method 202 for maintaining communication with one or more of 126, 128, 130, and 148 The flowchart diagram is shown.

[0276] Act 204 is the monitoring client dock through the dock connector to the monitoring client Determine if it is available as a communication link between the dock and the monitoring client dock. If a communication link 204 is available, method 202 proceeds to action 206; otherwise, If so, method 202 proceeds to action 208. Action 208 is to monitor the client dock wirelessly. The link serves as a communication link between the monitoring client and the monitoring client dock. Determine if it is available. If the communication link for action 208 is available, method 202 The process proceeds to act 206; otherwise, method 202 proceeds to act 210.

[0277] Act 206 is the monitoring client dock via wireless link to the monitoring client dock Determine if it is available as a communication link between the dock and the device dock. Action 20 If communication link 6 is available, method 202 proceeds to action 212; otherwise Method 202 proceeds to action 210.

[0278] Act 210 involves the device dock monitoring the client and the device via a wireless link. Determine if it is available as a communication link to the dock. The communication link for action 210 is If available, method 202 proceeds to action 212; otherwise, method 202 proceeds to action 212. Proceed to 214.

[0279] Act 212 is the communication between the device dock and the patient care device. Determine if it is available as a link. If the communication link for action 212 is available. If method 202 proceeds to act 216, otherwise method 202 proceeds to act 214.

[0280] Act 214 involves the patient care device directly monitoring the client and patient care via a wireless link. Determine if it is available as a communication link with the protection device. If available, method 202 proceeds to act 216; otherwise, act 218 The system determines that communication with the patient care device is unavailable.

[0281] Act 216 involves using (one or more) available communication links to communicate with the monitoring client. Attempt a handshake between patient care devices. In an alternative embodiment, the handshake is This has not been attempted, and for example, some communication protocols do not utilize handshakes. Decision action 220 determines whether the handshake was successful and whether the monitoring client and device Determine if communication between them has been established. If action 220 determines that a communication link has been established, Method 202 uses one or more available communication links to monitor during action 222. Data is communicated between the user and the device. Decision action 220 is that the handshake If it is determined that the process was unsuccessful, method 202 states that communication with the device in action 218 is Method 202 determines that the communication link is unavailable or that it is not verified (explicitly). It attempts to communicate between monitoring clients via (not shown).

[0282] Method 202 maintains communication between a monitoring client and one or more patient care devices. This is an exemplary embodiment of the present disclosure that describes a method for doing so. In some embodiments, Method 2 02 includes the communication link schedule, but other schedules can also be used. You can use forwarding, anycast, multicast, or unicast, and route The routing algorithm can be used, and the distance vector routing protocol It can be used, and the link-state routing protocol can be used, Optimized link state routing protocols can be used, and path vector routing protocols can be used. Tokol can be used, and static routing on a designated alternative communication path can be used. This allows and / or the use of adaptive networks. For example, the present disclosure In some embodiments, weights may be assigned to each communication path, and Dijkstra Lugorism communicates between monitoring client 1 and one or more patient care devices. It may be used. The weights can be any known method, for example, bandwidth, signal quality, bit It may be determined as a function of the error rate, available data throughput or latency. It may be linear between and / or similar intervals.

[0283] Next, referring to Figure 5, a monitoring client 1 and and various patient care devices (for example, patient care devices 7, 126, 128, or 13) 0) Dock 502 for docking together, communication module 124D, and don An electronic patient care system 500 in block diagram form, having group 133, is shown in Figure 5. The electronic patient care system 500 is similar to the electronic patient care system 100 in Figure 1, but supervision Visual client 1, patient care devices 7, 126, 128, 130, communication module 12 Both the 4D and the dongle 133 are dockable to dock 502. As can be seen in light of this disclosure, dock 502 has one or more to facilitate communication It can be equipped with a bus, backplane, communication path, electronic circuits, and the like.

[0284] In optional settings, instructions or requests can be made to patient care devices 7, 14, 15, 16, 17, and 35. To send to 126, 128, 130, 148, for example, bolus volume, injection flow rate, Measuring delivery fluid, drug delivery start time, drug delivery stop time, or delivery flow rate profile infusion pump 7, syringe pump 126 and / or microinfusion pump To send to the 130, monitoring client 1, other monitoring clients 4, and / Alternatively, a remote communicator 11 can be used. In some embodiments, for example For example, a pill dispensing instruction, pill type, pill dispensing schedule, and / Alternatively, send instructions or requests, such as maximum pill dispensing criteria, to the pill dispenser 128. Therefore, one or more of the monitoring clients 1, 4, and 11 can be used. Maximum pill distribution The standard is the maximum amount of drug that can be delivered within a given time, for example, a specific drug. It is taken as needed (i.e., when necessary), but if taken in excess, The drug may not be safe, and the maximum pill dispensing standard is, for example, "a prescribed amount within a prescribed time." This can prevent patients from taking unsafe amounts of medication.

[0285] For optional selection, patient care devices 7, 14, 15, 16, 17, 35, 126, and 128 are available. ,130,148 also ask whether an alarm or warning should be issued or transmitted. The system determines whether the treatment or condition is safe for the patient, and the system 500 Determine whether it is operating properly or within a predetermined boundary, and / or monitor clients. T1, on the display of other monitoring clients 4 and / or remote communicator 11 To display the data, the data is collected by monitoring client 1, other monitoring clients 4, and You can reply to the call / or remote communicator 11. For example, in optional mode, Infusion pump 7, syringe pump 126, and / or microinfusion pump Pump 130 measures upstream pressure, change in upstream pressure, downstream pressure relative to patient 2, and relative to patient 2. Changes in downstream pressure, presence or absence of air in the injection line, actual bolus volume delivered, actual Injection flow rate, actual total fluid delivered, actual start time of drug delivery, actual drug delivery Downtime, or actual delivery flow profile, monitored by client 1, other monitoring clients Ant 4 and / or one or more of the remote communicators 11 (if applicable) It can be believed. In another embodiment, the pill dispenser 128 is optionally, for example The actual pills that were distributed, the actual type of pills that were distributed, and the actual distribution of pills at the time of distribution. Data such as whether the schedule or the maximum pill distribution criteria have been exceeded will be monitored by the client. The system replies to 1, other monitoring clients 4, and / or remote communicators 11. It is possible.

[0286] Patient care devices 7, 14, 15, 16, 17, 35, 126, 128, 130, 14 The data received from 8 will be used to issue alarms and / or warnings, at any predetermined time. The state can be analyzed. For example, one or more of the monitoring clients 1, 4, and 11. This includes an infusion pump 7, a syringe pump 126, and / or a microinfusion pump. The increase in the downstream pressure of pump 130 may cause excessive coagulation, osmosis, or blockage of the tube to the patient. This may be a manifestation of bending or obstruction by other materials within the intravenous bag 170. It can be used in response to a rapid increase in downstream pressure, monitoring clients 1 and 4. One or more of the 11 may provide the user with a visual or auditory warning or alert. In addition, or alternatively, a rapid decrease in downstream pressure for patient 2 is a sign of This indicates that the tube has come off the needle, and / or the needle is now detached from the patient. Accordingly, one or more of the monitoring clients 1, 4, and 11 will provide the user with visual or auditory information. It can issue warnings or alerts to the target. One or more of the monitoring clients 1, 4, and 11 In the optional selection, the flow is controlled in response to a rapid increase and / or decrease in the downstream pressure for patient 2. To stop the delivery of the body, use infusion pump 7, syringe pump 126, and / or Instructions can be sent to one or more of the icloinfusion pump 130.

[0287] In some embodiments, the numbers are as shown in Figure 5 or as described herein. Whether attached or not, each item, component, device, patient Care devices, docks, and computing devices are optional. For example, several practical In this configuration, monitoring client 1 is optional, and monitoring server 3 is optional. Service 8 is optional, and each of services 19, 20, 21, 22, 23, and 24 is optional. It is a choice, and the cloud server 25 is optional, and the other monitoring clients 4 are each This is optional, and the online drug database 9 is optional, and the drug adverse event network Twerking is optional, patient's personal EHR19' is optional, and / Alternatively, the treatment outcome database 10 is optional. In addition, or as an alternative, In some embodiments, each patient care device 7, 14, 15, 16, 17, 35, 12 6, 128, 130, and 148 are optional. Similarly, system monitor 131, RIS Band 118, RFID 116, barcode 114, scanner 120, display 134, and / or AC power supply are each optional in some embodiments of the present disclosure. That is the case.

[0288] In addition, in some embodiments, as shown in Figure 5, or described herein There are several items, some numbered and some not, that are components. Networks, devices, patient care devices, docks, and computing devices are integrated into a single item. It is referred to as a component, device, patient care device, dock, or computing device. However, multiple items, components, devices, patient care devices, A docking station and computing device are intended. For example, a single injection pump 7 is shown in Figure 5. However, in some embodiments, two injection pumps 7 can be used. Multiple injection pumps 7 can be used, or any number of injection pumps 7 It can be used. In addition, or as an alternative, in some embodiments, multiple The number of docks 502 can be used.

[0289] In addition, or as an alternative, certain patient care devices 7, 14, 15, 16, 1 Although 7, 126, 128, 130, and 148 are shown, specific patient care devices Other combinations, subsets, multiples, or combinations thereof can also be used. For example, in some embodiments, only the infusion pump 7 among the patient care devices is used. In this particular embodiment, other patient care devices 14, 15, 16, 17, 126, 128, 130, and 148 are disabled and are not present or available for system use. It may not be, or the power may have been turned off, or it may not be part of System 500 in Figure 5. In addition, or alternatively, in some specific embodiments, patient care devices are used Only the S can dock to dock 502. For example, in a particular embodiment, injection Pump 7 is the only device docked within device dock 502, and The S-Dock 502 accepts only one device, for example, an injection pump 7. In addition, Alternatively, or optionally, in some specific embodiments, a patient care device 7 Models 14, 15, 16, 17, 35, 126, 128, 130, and 148 are dockable. It can operate without docking, and / or is not dockable. It can operate as a standalone patient care device.

[0290] Figure 5 shows that the Doc 502 can receive several patient care devices. Although shown, in other embodiments, the dock 502 is a patient care device , receiving multiple patient care devices, or any number of patient care devices Yes, it is possible. Also, dock compartments may not be in use, as shown in Figure 5, for example. Empty section 170 is shown within Dock 502. In addition, Dock 502 has one Although it is indicated that it is possible to receive monitoring client 1, other implementations In terms of configuration, dock 502 has two monitoring clients 1, and three or more monitoring clients 1 , or it can receive any number of monitoring clients.

[0291] Figure 6 shows a monitoring client according to an embodiment of the present disclosure, for example, the monitoring client in Figure 5. 1 and one or more patient care devices, for example, patient care devices 7, 14, 15, and 16 in Figure 5. , in order to maintain communication with one or more of 17, 35, 126, 128, 130, 148 This is a flowchart illustrating method 304.

[0292] The method involves the dock monitoring the client and the dock through the dock connector during action 306. Determine if it is available as a communication link with K. If the communication link for action 306 is available If not possible, method 304 proceeds to act 308; otherwise, method 304 proceeds to act 3 Proceed to 10. Action 310 is the dock as a communication link between the dock and the patient care device. Determine if it is available. If the communication link for action 310 is unavailable, then method 304 If so, proceed to act 312; otherwise, method 304 proceeds to act 314.

[0293] Act 308 is the communication link between the dock and the monitoring client via the wireless link. Determine if it is available as a link. If the communication link for action 308 is not available, Method 304 proceeds to act 310; otherwise, Method 304 proceeds to act 312.

[0294] Act 312 involves the patient care device directly communicating with the monitoring client and patient care via a wireless link. Determine if it is available as a communication link with the protection device. If the service is unavailable, act 316 is performed between the monitoring client and the patient care device. It is determined that communication is unavailable.

[0295] Act 314 involves using (one or more) available communication links to communicate with the monitoring client. An attempt is made to shake hands with the device. In an alternative embodiment, the handshake is not used. However, for example, some protocols do not utilize handshakes. Judgment action 318 is Method 304 determines whether the handshake was successful, and if successful, then acts 320 Proceed to communicate data using (one or more) available communication links. (Decision-making action) If 318 determines that the handshake was unsuccessful in act 314, then act 316 is: It is determined that communication with the device is unavailable. In other embodiments, the determination action 318 is If it is determined that the handshake was unsuccessful in act 314, then method 304 is verified Communicating with patient care devices via unlisted communication links (not explicitly shown). I will try.

[0296] Method 304 maintains communication between a monitoring client and one or more patient care devices. This is an exemplary embodiment of the present disclosure that describes a method for doing so. In some embodiments, Method 3 04 includes the communication link schedule, but other schedules can be used. You can use broadcast, anycast, multicast, or unicast. Routing algorithms can be used, including distance vector routing programs. Tocol can be used, and link-state routing protocols can be used. The optimized link state routing protocol can be used, and path vector • The protocol can be used, and static routing is used on a designated alternative communication path. This is possible and / or adaptive networks can be used. For example, this development In some embodiments of the diagram, weights may be assigned to each communication path, Dykes The TRA algorithm communicates between monitoring client 1 and one or more patient care devices. It may be used for any known purpose, such as bandwidth, signal quality. , may be determined as a function of the bit error rate, or the available data throughput or It may be linear to waiting time and / or similar factors.

[0297] Next, referring to Figure 7, a patient care device 7, 1 according to yet another embodiment of the present disclosure. Surveillance unit with integrated dock 702 for docking units 26, 128, and 130 there. A block diagram of the electronic patient care system 700 having Liant 1 is shown. In addition In some embodiments, the communication module 124D and the dongle 133 are all, It can be docked to dock 702. The patient care system 700 in Figure 7 is the patient care system in Figure 1. Similar to the care system 100, the patient care system 700 is equipped with an integrated dock 702. In some embodiments, the monitoring client 1 is docked via a dock. If this occurs, it communicates with the patient care device, but the monitoring client 1 is the patient care device, For example, patient care devices 7, 14, 15, 16, 17, 35, 126, 128, 130, If it is not possible to communicate with 148, monitoring client 1 will wirelessly, for example, the monitoring client Ant 1 can communicate using its antenna 112.

[0298] In optional settings, instructions or requests can be made to patient care devices 7, 14, 15, 16, 17, and 35. To send to 126, 128, 130, 148, for example, bolus volume, injection flow rate, Measuring delivery fluid, drug delivery start time, drug delivery stop time, or delivery flow rate profile infusion pump 7, syringe pump 126 and / or microinfusion pump To send to the 130, monitoring client 1, other monitoring clients 4, and / Alternatively, a remote communicator 11 can be used. In some embodiments, for example For example, a pill dispensing instruction, pill type, pill dispensing schedule, and / Alternatively, send instructions or requests, such as maximum pill dispensing criteria, to the pill dispenser 128. Therefore, one or more of the monitoring clients 1, 4, and 11 can be used. Maximum pill distribution The standard is the maximum amount of drug that can be delivered within a given time, for example, a specific drug. It is taken as needed (i.e., when necessary), but if taken in excess, The drug may not be safe, and the maximum pill dispensing standard is, for example, "a prescribed amount within a prescribed time." This can prevent patients from taking unsafe amounts of medication.

[0299] For optional selection, patient care devices 7, 14, 15, 16, 17, 35, 126, and 128 are available. ,130,148 also ask whether an alarm or warning should be issued or transmitted. System 70 determines whether the treatment or condition is safe for the patient. Determine whether 0 is operating correctly or within a given boundary, and / or monitor the client. The display of the 1st, other monitoring clients 4 and / or remote communicator 11 To display the data on the ray, the data is monitored by client 1, and other monitoring clients... 4. It can reply to the remote communicator 11. For example, optional. So, the infusion pump 7, syringe pump 126, and / or microinfusion Pump 130 measures upstream pressure, change in upstream pressure, downstream pressure relative to patient 2, patient Changes in the downstream pressure relative to 2, presence or absence of air in the injection line, and the actual amount of bolus delivered. Actual injection flow rate, actual total fluid delivered, actual start time of drug delivery, drug delivery The actual downtime, or the actual delivery flow profile, is monitored by client 1, and other monitoring Client 4 and / or one or more of the remote communicators 11 (if applicable) It can communicate with. In another embodiment, the pill dispenser 128 can optionally For example, the actual pills that were distributed, the type of actual pills that were distributed, the actual pills at the time of distribution The monitoring system monitors data such as the drug distribution schedule or whether the maximum pill distribution criteria have been exceeded. Reply to client 1, other monitoring clients 4, and / or remote communicator 11. It is possible.

[0300] Patient care devices 7, 14, 15, 16, 17, 35, 126, 128, 130, 14 The data received from 8 will be used to issue alarms and / or warnings, at any predetermined time. The state can be analyzed. For example, one or more of the monitoring clients 1, 4, and 11. This includes an infusion pump 7, a syringe pump 126, and / or a microinfusion pump. The increase in the downstream pressure of pump 130 may cause excessive coagulation, osmosis, or blockage of the tube to the patient. This may be a manifestation of bending or obstruction by other materials within the intravenous bag 170. It can be used in response to a rapid increase in downstream pressure, monitoring clients 1 and 4. One or more of the 11 may provide the user with a visual or auditory warning or alert. In addition, or alternatively, a rapid decrease in downstream pressure for patient 2 is a sign of This indicates that the tube has come off the needle, and / or the needle is now detached from the patient. Accordingly, one or more of the monitoring clients 1, 4, and 11 will provide the user with visual or auditory information. It can issue warnings or alerts to the target. One or more of the monitoring clients 1, 4, and 11 In optional selection, the flow rate changes depending on the rapid increase and / or decrease in downstream pressure for patient 2. To stop the delivery of the body, use infusion pump 7, syringe pump 126, and / or Instructions can be sent to one or more of the icloinfusion pump 130.

[0301] In some embodiments, the numbers are as shown in Figure 7 or as described herein. Whether attached or not, each item, component, device, patient Care devices, docks, and computing devices are optional. For example, several practical In this configuration, monitoring client 1 is optional, and monitoring server 3 is optional. Service 8 is optional, and each of services 19, 20, 21, 22, 23, and 24 is optional. It is a choice, and the cloud server 25 is optional, and the other monitoring clients 4 are each This is optional, and the online drug database 9 is optional, and the drug adverse event network Twerking is optional, patient's personal EHR19' is optional, and / Alternatively, the treatment outcome database 10 is optional. In addition, or as an alternative, In some embodiments, each patient care device 7, 14, 15, 16, 17, 35, 12 6, 128, 130, and 148 are optional. Similarly, system monitor 131, RIS Band 118, RFID 116, barcode 114, scanner 120, display 134, and / or AC power supply are each optional in some embodiments of the present disclosure. That is the case.

[0302] In addition, in some embodiments, as shown in Figure 7, or described herein There are several items, some numbered and some not, that are components. Networks, devices, patient care devices, docks, and computing devices are integrated into a single item. It is referred to as a component, device, patient care device, dock, or computing device. However, multiple items, components, devices, patient care devices, A docking station and computing device are intended. For example, a single injection pump 7 is shown in Figure 7. However, in some embodiments, two injection pumps 7 can be used. Multiple injection pumps 7 can be used, or any number of injection pumps 7 It can be used. In addition, or as an alternative, in some embodiments, Body shape checkup device 702 can be used.

[0303] In addition, or as an alternative, certain patient care devices 7, 14, 15, 16, 1 Although 7, 126, 128, 130, and 148 are shown, specific patient care devices Other combinations, subsets, multiples, or combinations thereof can also be used. For example, in some embodiments, only the infusion pump 7 among the patient care devices is used. In this particular embodiment, other patient care devices 14, 15, 16, 17, 126, 128, 130, and 148 are disabled and are not present or available for system use. It may not be, or the power may have been turned off, or it may not be part of System 700 in Figure 7. In addition, or alternatively, in some specific embodiments, patient care devices are used Only the S can dock to the integrated dock 702. For example, in a particular embodiment, The injection pump 7 is the only device docked within the integrated dock 702, and is integrated Type dock 702 accepts only one device, for example, an injection pump 7. In addition, alternative Alternatively, or optionally, in some specific embodiments, the patient care device 7, Models 14, 15, 16, 17, 35, 126, 128, 130, and 148 are dockable. Yes, it can operate without docking, and / or is not dockable. It can operate as a standalone patient care device.

[0304] Figure 7 shows that the integrated dock 702 can receive several patient care devices. Although shown to do so, in other embodiments, the integrated dock 702 is for one patient A care device, multiple patient care devices, or any number of patient care devices It is possible to receive it. Also, the dock area may not be in use, for example, Figure 7 As shown, an empty compartment 170 is indicated within the integrated dock 702. In addition, The integrated dock 702 is capable of receiving one integrated monitoring client 1. Although shown, in other embodiments, the integrated dock 702 has two integrated monitoring units One operative, three or more integrated monitoring clients, or any number of integrated It can receive monitoring client 1.

[0305] Figure 8 shows an electronic patient care system having a hub 802 according to yet another embodiment of the present disclosure. This is a block diagram of the M800. In some optional embodiments, the hub 802 is A communication interface is provided between the monitoring client dock 102 and the device docks 804 and 806. - Provides a face. In an additional embodiment, the hub 802 provides a face to monitoring client 1 Without other monitoring clients 4 and / or remote communicators 11, patient care data It controls the vice. For example, Hub 802 controls the monitoring server 3, facility services 8, nurse services. Station 5, Pharmacy 6, Cloud Server 25, Online Drug Database or Drug Adverse event network 9, patient's personal EHR 19' and / or treatment outcome data It can communicate with Base 10. Hub 802 can communicate with all devices connected to it. For example, patient care devices, monitoring clients, remote communicators, etc. are connected to Hub 802 The real-time device uses the clock of the hub 802, or To ensure that time-critical devices use the hub 802's clock, provide the clock. It can be provided.

[0306] In some embodiments, a GPS and / or ranging module (e.g., ultrasonic ranging) is used. Module) includes infusion pump 830, monitoring client 1, hub 802, caregiver and / Alternatively, it can be installed on the patient. The predetermined settings are for the infusion pump 830 and the monitoring client. In this particular embodiment, a predetermined group of T1, hub 802, caregivers, and / or patients are, Before starting treatment, and / or before injecting the infusion pump 830, hub 802, and / or Before configuring one of the monitoring clients 1, they must be within a predetermined distance of each other. They may request that.

[0307] In some embodiments, the hub 802 is an application programming interface. - Equipped with a face (API), monitoring client 1 and / or remote communication Display GUI, windows, data, etc. on top of T11. The API is secure data • Classes may be included. Further embodiments include docks 102, 804, and 806 has an API for monitoring client 1 or remote communicator Display GUI, windows, data, etc. on top of 11. In further embodiments, The 102, 804, or 806, or Hub 802, are equipped with an API for patient care data GUI, windows, data, etc. on top of Vice 830, 810, and / or 814 Display.

[0308] In some embodiments, hub 802 and / or docks 102, 804, and / Alternatively, 806 refers to the associated patient care device (the device paired there, Plugged into hub 802 and / or docks 102, 804, and / or 806 Based on the type of device (or docked device), the patient care associated with it. It can identify the device type and load configuration data.

[0309] In some embodiments, hub 802 and / or docks 102, 804, and / Alternatively, 806 identifies the type of patient care device associated there, and html, The UI can be configured using CSS, JavaScript, etc. In this embodiment, hub 802 and / or docks 102, 804, and / or 806 It can have a distributed UI system.

[0310] The user interface described herein utilizes the request action framework. It may be used.

[0311] In optional configurations, in some specific embodiments, the hub 802 is connected to the monitoring client 1. It is equipped with all the safety-critical circuits and software necessary for communication. In this particular embodiment, the hub 802 receives treatment parameters from the monitoring client 1. Believe it, hub 802 detects some security activity that occurred somewhere, for example, on monitoring client 1. Independent of the inspection, ensure that the treatment parameters are safe for patient 2. In a particular embodiment, the system 800 optionally fully monitors client 1. It is fault-tolerant, for example, independent monitoring performed by client 1 The entire inspection did not meet the prescribed standards, for example, the prescribed safety range for drug delivery by the infusion pump 7. In some cases, instructions, requests, or parameters from monitoring client 1 can be ignored. .

[0312] Optionally, in additional specific embodiments, it can be attached to the intravenous bag 170. The barcode can be scanned by scanner 120, which is a prescribed prescription. Download (for example, from the patient's personal EHR19') and / or inject. Pump 830 is connected to hub 802 when hub 802 is docked to dock 804. It includes the uploaded prescribed prescription. Subsequently, in this particular embodiment, also In the optional course, Hub 802 initiated intravenous bag 170 in patient 2, and the treatment progressed. Monitor and ensure the safety of patient 2. In addition, as an alternative or optional measure, In a particular embodiment, the caregiver is connected to the system 80 via only the hub 802 as shown in Figure 8. It can interact with 0. In some embodiments, optionally, hub 802 Upload treatment, status, or patient information to monitoring client 1. For example, hub 802 is the treatment information received from the infusion pump 830, or the gap on the intravenous bag 170. Treatment information received from the patient's personal EHR19' corresponding to the scanned barcode. Upload the information to monitoring client 1, display it to the user, and allow the user to verify the information. It can recognize and store information within the monitoring client 1.

[0313] In some embodiments, the device dock 804 is connected to the injection pumps 830, 810 and It receives 812. In some embodiments, the device dock 804 is one, two The patient receives one or more of the above patient care devices. Device Dock 806 is a pill-shaped device. Spencer 814 is received. In some embodiments, the device dock 806 is a pill dock. Receive one, two or more, or more patient care devices such as the Dispenser 806. The device dock 804 is equipped with an antenna 816 for wireless communication, and the device dock The 806 is equipped with an antenna 818 for wireless communication. Similarly, the hub 802 is equipped with an antenna 818 for wireless communication. It is equipped with a trust antenna 820. In addition, or as an alternative, device dot Hub 804, Hub 802, and / or monitoring client 1 connect to each other using a wired connection. They communicate. Hub 802 and docks 804 and 806 each communicate, for example, via USB. Using a cable, using an Ethernet cable, and / or a wireless link They can communicate with each other through this. Optionally, hub 802 connects to display 82 2. Camera 824, microphone 826, scanner 120, detachable display (Figure) It may have additional accessories such as (not shown). As mentioned above, Hub 802 is all It can provide patient safety and critical functions, and monitor client 1 and Alternatively, it can operate independently of the monitoring client dock 102.

[0314] In optional settings, instructions or requests can be made to patient care devices 14, 15, 16, 17, 35, 8. For example, bolus volume, injection flow rate, to be sent to 30, 810, 812, 814, 148. , total delivery fluid, drug delivery start time, drug delivery stop time, or delivery flow rate profile To send the oil to one or more injection pumps 830, 810, or 812, monitor client Using 1, other monitoring clients 4, and / or remote communicator 11 This is possible. In some embodiments, for example, a pill dispensing instruction for dispensing pills, pills Instructions or requests such as type, pill distribution schedule and / or maximum pill distribution criteria. To send to pill dispenser 814, one or more monitoring clients 1, 4, and 11 It can be used. The maximum pill distribution standard is the amount of medicine that can be delivered within a given time. This is the maximum amount of the drug, for example, the amount of a particular drug taken as needed (i.e., when needed). Although taken, if taken in excess, the drug may be unsafe, and the maximum pill dispensing base The term "standard" means, for example, "a specified amount within a specified time," indicating that the drug is not administered in an unsafe amount by the patient. This can prevent ingestion.

[0315] For optional selection, patient care devices 14, 15, 16, 17, 35, 830, 810, 8 12, 814, 148 should also issue or transmit an alarm or warning. System 8 determines whether the treatment or condition is safe for the patient. Determine whether 00 is operating properly or within a predetermined boundary, and / or monitor Client 1, other monitoring clients 4 and / or remote communicator 11 To display the data on the screen, the data is monitored by client 1, and other monitoring clients... You may reply to 4 and / or the remote communicator 11. For example, optionally One or more of the injection pumps 830, 810, and 812 will monitor the upstream pressure, the change in upstream pressure, Downstream pressure relative to patient 2, change in downstream pressure relative to patient 2, presence of air in the injection line None, actual bolus volume delivered, actual injection flow rate, actual total fluid delivered, drug delivery The actual start time of the drug delivery, the actual stop time of drug delivery, or the actual delivery flow profile. Monitoring client 1, other monitoring clients 4, and / or remote communicator 11 It can communicate with one or more of the following (if applicable). In another embodiment, pills Spencer 814 is optional, for example, the actual pill that is distributed, the actual pill that is distributed The actual pill distribution schedule at the time of distribution or whether it exceeded the maximum pill distribution standard. Data such as this is transmitted to monitoring client 1, other monitoring clients 4 and / or remotely. You can reply to Communicator 11.

[0316] Patient care devices 14, 15, 16, 17, 35, 830, 810, 812, 814, Data received from 148 will be used to issue alarms and / or warnings everywhere. The analysis may be performed on a fixed state. For example, one or more of the monitoring clients 1, 4, and 11 are The increase in the downstream pressure of one or more infusion pumps 830, 810, and 812 is directed to the patient. Excessive coagulation, infiltration, blockage, or bending of the tubing, or other materials within the intravenous bag 170. It can be used as one manifestation of blockage caused by a rapid increase in downstream pressure. Accordingly, one or more of the monitoring clients 1, 4, and 11 provide the user with visual or auditory information. A warning or alert may be issued. In addition to or as an alternative to this, for patient 2 A sudden drop in downstream pressure indicates that the tube has come off the needle and / or the needle is now away from the patient. This indicates that it is out of range, and accordingly, one or more of the monitoring clients 1, 4, and 11 It can issue visual or audible warnings or alerts to the user. Ant 1, 4, 11 (or one or more) is optional for injection pumps 830, 810, 812. Send instructions to one or more devices to trigger a rapid increase and / or decrease in downstream pressure for patient 2. Depending on the situation, the delivery of the fluid can be stopped.

[0317] In some embodiments, the numbers are as shown in Figure 8 or as described herein. Whether attached or not, each item, component, device, patient The care device, dock, and computing device are optional. For example, several implementations In terms of configuration, monitoring client 1 is optional, monitoring server 3 is optional, and equipment Service 8 is optional, and each of services 19, 20, 21, 22, 23, and 24 is optional. The cloud server 25 is optional, and the other monitoring clients 4 are each It is optional, and the online drug database 9 is optional, and the drug adverse event network Work is optional, patient's personal EHR19' is optional, and / or The treatment outcome database 10 is optional. In addition, or alternatively, In some embodiments, each patient care device 830, 810, and 812 is optional. Similarly, the system monitor 131, wristband 118, RFID 116, and barcode 114, scanner 120, display 808 and / or AC power supply are each open In some embodiments of the diagram, this is optional.

[0318] In addition, in some embodiments, as shown in Figure 8, or described herein There are several items, some numbered and some not, that are components. Networks, devices, patient care devices, docks, and computing devices are integrated into a single item. It is referred to as a component, device, patient care device, dock, or computing device. However, multiple items, components, devices, patient care devices, A docking and computing device is intended. For example, a single pill dispenser 814 As shown in Figure 8, in some embodiments, two pill dispensers 814 It can be used, and multiple pill dispensers 814 can be used, It can use any number of pill dispensers 814. In addition, Alternatively, in some embodiments, a number of docks 804 or 806, and Alternatively, multiple monitoring client docks 102 can be used.

[0319] In addition, or as an alternative, certain patient care devices 830, 810, and 812 Although shown, other combinations, subsets, and numerous other combinations of specific patient care devices Or a combination thereof may be used. For example, in some embodiments, patient care Of the devices, only the infusion pump 830 is used, and in this particular embodiment, other patients Care devices 810, 812, and 814 have been disabled and are not present for system use. It is unavailable, powered off, or not part of System 800 in Figure 8. There is. In addition, or as an alternative, in some specific embodiments, it is used Only patient care devices can be docked to dock 804 or 806. For example, In one specific embodiment, the injection pump 830 is docked within the dock 804. It is a device, and dock 804 only receives one device, for example, injection pump 830. ru.

[0320] Figure 8 shows that the Doc 804 can receive several patient care devices. Although shown, in other embodiments, the device dock 804 is a single patient intermediary Patient care devices, multiple patient care devices, or any number of patient care devices It is possible to do this. Also, the dock area may not be used (not shown in Figure 8). In addition, the monitoring client dock 102 receives one monitoring client 1. Although it is shown to be possible, in other embodiments, the monitoring client... Dock 102 can handle two monitoring clients 1, three or more monitoring clients 1, or It can receive any number of monitoring clients. In addition, as an alternative , or optionally, in some specific embodiments, patient care devices 14, 15, 16, 17, 35, 830, 810, 812, and 814 are docking, and docking It can operate without docking and / or is standalone, not dockable. It can function as a patient care device.

[0321] The system 800 in Figure 8 maintains communication with it using any known communication method. It can be maintained. For example, in some embodiments, an arbitrary communication schedule can be used. It can be used with broadcast, anycast, multicast, or unicast. It is possible to use routing algorithms and distance vector routing. Link-state routing protocols can be used, and link-state routing protocols can be used. It can be used, and the Optimized Link State Routing Protocol can be used. Path vector protocols can be used, and static routing on a given alternative communication path A ping can be used and / or an adaptive network can be used. For example, in some embodiments of this disclosure, weights may be assigned to each communication path. Dijkstra's algorithm monitors client 1 or hub 802 and one or more patients Care devices (e.g., patient care devices 830, 810, 812, and 814) and It may be used to communicate between them. The weight can be any known method, for example, bandwidth. The signal quality may be determined as a function of the bit error rate, and the available data through It may be linear to a put or wait time and / or similar.

[0322] In embodiments of this disclosure, the facility service 8 and / or the adverse drug event network 9 are Furthermore, a medication error reduction system (DERS) may be provided. The DERS system is a soft-a A set of predetermined criteria for activating the alarm, and / or a hard alarm. It may include a second set of predetermined criteria for starting. A soft alarm is included. User interface for pump 830, user interface for hub 802 8 Using the user interface of 08 and / or monitoring client 1, caregivers can be informed Therefore, it can be disabled (for example, stopped) (and also audible and / or vibrated (It may be just an alarm), on the other hand, a hard alarm is the cause of the hard alarm. Treatment will be suspended until the parasite is removed.

[0323] In further embodiments of this disclosure, the DERS system defines a soft limit. A first set of predetermined criteria, and / or a second set that defines hard limits. It may include the following criteria: hard and soft limits, body size, weight, age. Based on other patient parameters or other criteria, treatment limits such as drug dosage are defined. The Soft Limit is the user interface for the injection pump 830, monitoring the client. The user interface of Ant 1, and / or the user interface of Hub 802 Disabled by caregiver using Face 808, treatment is performed according to the prescribed criteria of the first set. Treatment can be started even when outside, while hard limits are set to hard Treatment will continue until it is modified to meet the prescribed criteria of the second set that defines the limit. Prevent it from starting.

[0324] In some embodiments, patient care devices 830, 810, 812, 814, 14, 15, 16, 17, 35 and / or 148, Monitoring Client 1, Remote Communication T11, and Dock 102 and / or 804, and / or Hub 802, for example A secure data class may be provided via an API.

[0325] Referring again to the drawings, Figure 9 shows a stackable according to yet another embodiment of the present disclosure. Monitoring client 902, stackable infusion pump 904, stackable syringe. Electronic patient care system having pump 906 and another stackable patient care device 908 The block diagram of stem 900 is shown. Stackable devices 902-908 are backed by Communication may be conducted using lanes and / or buses (in some embodiments, stacked (Devices 902-908 that can connect communicate via a communication module.)

[0326] In optional settings, instructions or requests can be made to patient care devices 14, 15, 16, 17, 35, 1 For sending to 28, 904, 906, 908, 148, for example, bolus volume, injection flow rate. , total delivery fluid, drug delivery start time, drug delivery stop time, or delivery flow rate profile Stackable infusion pump 904, stackable syringe pump 906, and To send to the monitoring cliator of the 908 and / or other stackable patient care device Using terminal 902, other monitoring clients 4, and / or remote communicator 11 This is possible. In some embodiments, for example, a pill dispensing instruction for dispensing pills. Instructions such as pill type, pill dispensing schedule, and / or maximum pill dispensing criteria. Alternatively, to send the request to pill dispenser 128, monitoring client 902, 4, 1 One or more of the above may be used. The maximum pill distribution standard is to deliver within a specified time. This is the maximum amount of drug that can be administered, for example, if a specific drug is administered as needed (i.e., if it is needed). (If taken) it will be ingested, but if taken in excess, the drug may not be safe, and at the maximum The pill distribution criteria are such that the medication is administered safely to the patient, for example, "a specified amount within a specified time." This can prevent ingestion of excessive amounts.

[0327] For optional selection, patient care devices 14, 15, 16, 17, 35, 128, 904, 9 06, 908, 148 also monitor data client 902, other monitoring clients 4 and / or the remote communicator 11 will reply to issue an alarm or warning or To determine whether to send it, whether the treatment or condition is safe for the patient. Determine whether system 900 is operating properly or within a predetermined boundary. , and / or monitoring client 902, other monitoring clients 4 and / or remote Data can be displayed on the display of the communicator 11. For example, optional data can be displayed. The options include the stackable infusion pump 904, the stackable syringe pump 906, and The / other stackable patient care device 908 controls upstream pressure, changes in upstream pressure Factors, downstream pressure relative to patient 2, change in downstream pressure relative to patient 2, air in the injection line Presence or absence, actual bolus volume delivered, actual injection flow rate, actual total fluid delivered, drug Actual start time of material delivery, actual stop time of drug delivery, or actual delivery flow profile The monitoring client 902, other monitoring clients 4, and / or remote communication It can communicate with one or more of the caterers 11 (if applicable). In another embodiment, The pill dispenser 128 can optionally dispense actual pills, for example, the actual pills that are dispensed. The type of pill used, the actual pill distribution schedule at the time of distribution, or the maximum pill distribution standard. Data such as whether it exceeded a certain limit can be accumulated by the monitoring client 902 and other monitoring clients. You may reply to Liant 4 and / or Remote Communicator 11.

[0328] Patient care devices 14, 15, 16, 17, 35, 128, 904, 906, 908, The data received from 148 is analyzed to determine the presence or absence of any predetermined conditions, and alarms are triggered. / or it can issue an alert. For example, one of the monitoring clients 902, 4, or 11 The above describes the stackable infusion pump 904 and / or stackable syringe pump. Increased downstream pressure in the 906 tube can lead to excessive coagulation, infiltration, blockage, or kinking of the tube to the patient. It is used as one manifestation of bending or obstruction by other materials in the intravenous bag 170. It can be used. In response to a rapid increase in downstream pressure, monitoring client 902, 4, One or more of the 11 may provide the user with a visual or auditory warning or alert. In addition, or alternatively, a rapid decrease in downstream pressure for patient 2 is a churning sensation. This indicates that the needle has come off and / or that the needle is now detached from the patient. Depending on the situation, one or more of the monitoring clients 902, 4, and 11 may provide the user with visual or audio information. It can issue warnings or alerts automatically. One of the monitoring clients 902, 4, or 11. The above is optional for stackable injection pump 904 and / or stackable Send instructions to one or more syringe pumps 906 to rapidly increase the downstream pressure on patient 2. Depending on the rise and / or fall, the fluid delivery can be stopped.

[0329] Stackable monitoring client 902, stackable device 908, stackable The 904 infusion pump and the 906 stackable syringe pump are available on top of each device. They can be daisy-chained together via connectors attached to the top and bottom. For example, instead of the stackable syringe pump 906, monitor client 9 It can be stacked on top of 02, thereby enabling stackable syringe pump 9 The bottom connector of 06 is electrically coupled to the top connector of the monitoring client 902.

[0330] Daisy chains are stackable, for example, the 902 monitoring client, stackable A patient care device 908, a stackable infusion pump 904 and a stackable saddle It can be created through the electrical conductor inside each of the 906 syringe pumps, thereby Continuous electrical contact is maintained between each of these devices.

[0331] In addition, or as an alternative, stackable devices 902, 908, 904, 906 may optionally maintain wireless communication with one another. For example, stackable monitoring Client 902 is a device 9 in which daisy-chained conductors can be stacked. An internal short circuit in one of the stackable devices 02, 908, 904, or 906 It can detect electrical unresponsiveness and is a stackable monitoring client 9 02 queries each stackable device 908, 904, and 906 to determine which device It is possible to determine if the system has malfunctioned. After making this determination, cumulative monitoring can be performed. Client 902 is one of the stackable devices 902, 908, 904, and 906. Wireless communication with an isolated disconnected circuit within the faulty device to daisy the faulty device - It can be electrically engaged and disengaged from chain-connected conductors. In addition, Alternatively, one or more of the stackable devices 902, 908, 904, and 906 may be used. One of the stackable devices 902, 908, 904, and 906 is malfunctioning, and / or one of the stackable devices 902, 908, 904, or 906 is Daisy Chi It warns that communication is taking place wirelessly, rather than via a wired, connected communication link. You can send a warning and / or display a message.

[0332] In addition, or as an alternative, stackable monitoring client 902, stackable Possible device 908, stackable infusion pump 904 and stackable syringe Each pump 906 is connected to the device below or above it in a daisy chain. Information may be relayed or retransmitted to S. For example, stackable injection pump 904 The stackable patient care device 908 buffers data in its internal memory. Stackable patient care signals indicating readiness to receive additional data When information is received from device 908, it can be communicated to create stackable systems. All data received from the syringe pump 906 can be communicated. Several implementations In terms of form, there are also numbered ones, as shown in Figure 8 or as described here. Even those that are not attached, each item, component, device, patient care device, The dock and computing device are optional. For example, in some embodiments, monitoring Client 1 is optional, monitoring server 3 is optional, and equipment service 8 is optional. This is optional, and each service 19, 20, 21, 22, 23, 24 is optional, and The Udo server 25 is optional, and the other monitoring clients 4 are each optional. The online drug database9 is optional, and the drug adverse event network is optional. The patient's personal EHR19' is optional, and / or treatment outcome data Database 10 is optional. In addition, or as an alternative, several implementations In this configuration, each patient care device 830, 810, and 812 is optional. Similarly, the system Monitor 131, Wristband 118, RFID 116, Barcode 114, Scan Na 120, display 808 and / or AC power supply are, respectively, some of the present disclosures. In this embodiment, it is optional.

[0333] In addition, in some embodiments, as shown in Figure 9 or described together therein, Some items, both numbered and unnumbered, Components, devices, patient care devices, and computing devices are all part of a single item. As shown as a component, device, patient care device, or computing device However, multiple items, components, devices, patient care devices and computing devices A chair is intended. For example, a single pill dispenser 128 is shown in Figure 9. However, in some embodiments, two pill dispensers 128 can be used. , a large number of pill dispensers 128 can be used, or any number of pills Dispenser 128 can be used.

[0334] In addition, or as an alternative, certain patient care devices 904, 906, and 908 Although shown, other combinations, subsets, and numerous other combinations of specific patient care devices Or a combination thereof may be used. For example, in some embodiments, patient care Of the devices, only the stackable injection pump 904 is used, in this particular implementation In the example, other patient devices 906 and 908 are disabled and not present for system use. It is either unavailable, powered off, or not part of System 900 in Figure 9. There are also, in addition to or alternative to, in some specific embodiments, it is used Only patient care devices are stacked. For example, in one particular embodiment, an infusion port The Pmp 904 is the only device that is stacked. In addition to that, or as an alternative , patient care devices that are not stacked, for example, patient care devices 904, 906 and The 908 will continue to operate if it is running as a standalone device. It is possible. In addition, as an alternative or at your discretion, there are several specific implementations. In terms of form, patient care devices 14, 15, 16, 17, 35, 904, 906, 908, The 128 and 148 are dockable, and can operate without docking. It is not dockable and / or operates as a standalone patient care device. It is possible.

[0335] Figure 9 shows that the stack can hold several patient care devices. Although shown, in other embodiments, the stack consists of one patient care device, multiple The patient may receive any number of patient care devices. In addition, the stack indicates that it is capable of receiving one monitoring client 902. However, in other embodiments, two stackable monitoring clients 902 , 3 or more stackable monitoring clients 902, or any number of stackable The monitoring client 902, which is capable of handling this, is stacked together within system 900.

[0336] The system 900 in Figure 9 maintains communication with it using any known communication method. It can be maintained. For example, in some embodiments, an arbitrary communication schedule can be used. It can be used with broadcast, anycast, multicast, or unicast. It is possible to use routing algorithms and distance vector routing. Link-state routing protocols can be used, and link-state routing protocols can be used. It can be used, and the Optimized Link State Routing Protocol can be used. Path vector protocols can be used, and static routing on a given alternative communication path You can use a ping and / or an adaptive network. For example, in some embodiments of this disclosure, weights may be assigned to each communication path. It is possible to use Dijkstra's algorithm to monitor client 902 and one or more patients Communication with care devices (e.g., patient care devices 904, 906, 908) The weights can be determined by any known method, such as bandwidth, signal quality, and bit error rate. It may be determined as a function of available data throughput or latency, and / Or it may be linear in a similar way.

[0337] Referring to Figures 1, 3, 5, 7, 8, and 9, various update techniques and / or methods are utilized. Uses hubs, docks, devices, insulin pumps, infusion pumps and / or patients Care devices may be updated. For example, patient care devices may be, for example, several implementations In this state, RS232 format data is converted to, for example, I2C format data. The bus converter enables the computing device (in some embodiments, a personal computer) Any device that can be used in the same way as a data or personal computer. It can be attached to a chair (for example, but not limited to this, it could also be a tablet). B, dock, device, insulin pump, infusion pump and / or patient care device In some embodiments, the processor within the system performs updates, for example, Flash memos are generated by the pervisor processor and / or command processor. You may control or organize the download of software within the system. In this embodiment, the computing device includes a hub, a dock, a device, an insulin pump, and an infusion device. Download the software to the flash memory of the pump and / or patient care device. The loading process may be organized. Software updates obtained by computing devices are Accessible by the supervisor processor and / or command processor. It can be sent to a capable flash memory (not shown). The above software update is In some embodiments, it can be automatically invoked by a script process. It may also be a command-line program.

[0338] In some embodiments, the hub, dock, device, insulin pump, and infusion pump are used. and / or patient care devices, but not limited to, web-based secure • Through the portal, and / or via email, and / or wireless communication Tokol allows you to download applications and update software, although this is not limited to Tokol. Download new information, upload information, and / or send information to various machines. It may be a web-connected remote interface that can include the ability to do so, or It may have the capability of a remote interface. Therefore, in various embodiments, the remote interface The application can run on any functional device, so-called dedicated devices. This is not limited to vices. Furthermore, in some embodiments, the remote interface is , but not limited to these, hubs, docks, devices, insulin pumps, infusion pumps, patients Caregiving devices, Bluetooth or other communication devices, patient care devices, and / or or one or more devices which may include one or more other devices, for example, Even though Bluetooth makes it possible to communicate using line frequency ("RF") communication... , or may be made possible in other ways.

[0339] In some embodiments, the charging station may be equipped with a USB plug. Hubs, docks, devices, insulin pumps, infusion pumps for remote interfaces It may include a charging area for the patient care device and / or a patient care device. Some embodiments The charging station may also have a USB port, and in some embodiments, a mini It may also be equipped with a USB port, thereby, in some embodiments, through USB Hubs, docks, devices, insulin pumps, infusion pumps, patient care devices and / Alternatively, to charge the remote interface, the charging station will receive power. It can be made possible. In addition, and / or alternatively, the USB port can To connect to a computer or other device, and / or a computer-type device. Therefore, remote interfaces, and / or hubs, docks, devices, insulin... Designed for data transfer to and from pumps, infusion pumps, and / or patient care devices. This can be achieved. In embodiments including a USB port, the remote interface is charged. While this is happening, the system will be using personal computers and / or web portals. It will call up a command to check for available software updates, and if there are any available updates... In such cases, you can download software updates via, for example, a USB connection. The next update will be during pairing of the hub, dock, device, insulin pump, and infusion. It can be transferred to a pump and / or patient care device.

[0340] Therefore, the user will need a hub, dock, device, insulin pump, infusion pump. Connecting the remote interface of the patient care device to a personal computer It can continue, and / or, in some embodiments, the data can be transmitted via a remote interface. It can be uploaded from the face to a web portal, etc. Several embodiments This can be achieved during the "recharging" of the remote interface, and this recharging is In some embodiments, this is done using a USB connection to a personal computer. Also, this is often used for charging / recharging the remote interface, in addition to personal... Synchronize data from computers, 1908 and / or web portals, and / or you may upload / download. At this time, the system will select one of the devices Are software updates available for the above and / or remote interfaces? It can be determined. The user can select "Download update", These updates occur during charging, and / or via the remote interface, directly or indirectly. Web applications specifically designed for personal computers and / or their systems. Hubs, docks, devices, insulin pumps, etc., are connected to the portal at any time. Download to the remote interface of the infusion pump and / or patient care device. It is possible. As mentioned above, the remote interface can communicate with various devices. It has power. Therefore, software updates can be performed by any 1 remote interface. It can be transmitted to more than one device. This has many advantages, for example, Not limited to, but uploading data / information from all devices, and / or This can be accessed from a personal computer and / or from the Internet / web portal. Both updating and / or downloading the application to any device. Therefore, the remote interface is connected to a personal computer / web portal. One advantage is that it only requires doing this. This can be desirable for many reasons, for example. For example, and this is not limited to this, the ability to efficiently and easily update all devices from a single connection. The ability to do so, and / or all data from all devices in one location Being able to see and / or personal computer through a remote interface Download information and / or settings from your computer / web portal to any device. One of the advantages is that it can be used.

[0341] Therefore, in some embodiments, personal computer / web portal However, this is not the only example, but it includes all information from all devices, including remote interfaces. Therefore, a new "remote interface" can be introduced into the system at any time. This is a new remote interface for personal computers / web portals. Connect to it and download all system information to the remote interface. This can be achieved by first using the old remote input. It may be necessary to remove the Turface from the "Authenticated Devices" list, but other implementations In this configuration, the system "allows" additional remote interfaces based on user permission. It is possible. Therefore, the system is capable of communicating with the device, and / or personal computers and / or web portals can be connected. All information and It has the ability to download applications.

[0342] Furthermore, this allows the remote interface to access any application from the internet. It will become possible to download the application to any device within the system. Therefore, In various embodiments of the system, the user (personal computer and / or This includes several parameters such as the ability to wirelessly communicate with web portals and connect to them. (m) Control any device, various devices, such as injection pumps and / or CGM Sensors / transceivers and / or other sample sensors and / or hubs, docks, devices Other devices such as chairs, insulin pumps, infusion pumps and / or patient care devices A device that can receive data from the chair and / or control it, It can be changed. In some embodiments, a remote interface and / or remote One or more applications on a remote interface should be protected with a password or similar. It can be paired with one or more devices, such as an injection pump and / or CGM sensor. It is paired with the and / or one or more other devices.

[0343] In some embodiments, information on the remote interface is uploaded, and / or synchronize with another device and / or computer and / or machine, for example This is not limited to this, but any internet site (web) that is password protected You may upload data to the portal. Therefore, users can use any device Information can be accessed from the device and / or any device-specific application. Information including this can be downloaded to any device, therefore, not limited to this. However, user information, including history and preferred settings, can be downloaded to any device. It can be done.

[0344] Figure 10 shows the patient care parameters of the patient care device on the monitoring server according to an embodiment of the present disclosure. This is a flowchart of method 600 for communicating data. Method 600 is action 602 ~608 includes. The patient care device of method 600 is optional and is disclosed herein. Any patient care device, for example, patient care devices 7, 14 in Figures 1, 3, 5, or 7. 15, 16, 17, 35, 126, 128, 130, 148, Patient care device 1 in Figure 8 4, 15, 16, 17, 830, 810, 812, 814, Patient care device 14 in Figure 9 , 15, 16, 17, 904, 906, 908 or other patient care disclosed herein A device would also be acceptable.

[0345] Action 602 establishes a communication link between the patient care device and the monitoring server. Action 6 04 transmits patient care parameters to a monitoring server, for example, via a local area network. and / or via WiFi over the internet, monitoring clients, one or more hubs Alternatively, communication is conducted via a dock or similar device. Action 606 de-identifies patient care parameters. Action 606 is performed, for example, within the monitoring server 3 in Figures 1, 3, 5, 7, 8 and / or 9, This can be done dynamically and electronically. For example, removing the patient's name and monitoring Random serial numbers that cannot be used to determine patient identification information within the server. It may be replaced with a number or other mark. Act 608 is an unidentified patient care parameter The data can be stored in a database, such as an SQL database, a relational database, or an associative database. It is stored in monitoring servers such as cloud servers.

[0346] Figure 11 shows the determination made from the patient care device within the monitoring server according to an embodiment of the present disclosure. This is a flowchart of method 701 for collecting patient care parameters from a large number of patients. Act 701 includes acts 703-713. In some embodiments, acts 703-713 All options are optional. Patient care devices are any patient care devices disclosed herein. Chairs, for example, patient care devices 7, 14, 15, 16, 17, 3 in Figures 1, 3, 5, or 7. 5, 126, 128, 130, 148, Patient care devices 14, 15, 16, 17 in Figure 8 , 830, 810, 812, 814, patient care devices 14, 15, 16, 17 in Figure 9, This may also be patient care devices as disclosed in Sections 904, 906, 90, or other patient care devices disclosed herein. stomach.

[0347] Action 703 involves a monitoring server, for example, monitoring server 3 in Figures 1, 3, 5, 7, 8, or 9, Establish a communication link between multiple patient care devices associated with multiple patients. In terms of selection, multiple patient care devices can be associated with a single patient, and / or Alternatively, multiple patient care devices can be associated with different individual patients.

[0348] Action 705 transmits multiple patient care parameters from multiple patient care devices to a monitoring server. To communicate. Action 707 de-identifies patient care parameters, and action 709 these patients Care parameters are stored within the monitoring server, for example, in an SQL database, relational database, or associative database. It is stored in a database such as a database. Action 707 is automatically and / or It can be done electronically. Action 711 treats a subset of patients from among multiple patients. To treat. For example, a patient with high blood pressure may be treated with medication prescribed to lower their blood pressure. Yes, it is possible. Action 713 is a subset of multiple patient care parameters associated with multiple patients. The results are analyzed to determine the effectiveness of the treatment. For example, all of the blood pressure medications received under Act 711. In these patients, their blood pressure is compared to a blood pressure reading taken at a predetermined time, for example, 6 months later. It is possible to determine whether the treatment is effective for one or more patients.

[0349] Figure 12 shows the patient when the operation of the patient care device is interrupted according to an embodiment of the present disclosure. This is a flowchart of method 801 for recovering care devices. For example, patient care devices It has been unplugged from the dock, power has been cut off, and a hardware or software failure may occur. Possible solutions include temporarily disabling one or more processors or other circuits within the care device. It is possible. In addition, or as an alternative, one or more processes on the patient care device Even if Ssa implements method 801 so that the patient care device is hot-swappable, good.

[0350] Method 801 includes acts 803-823. Each act 803-823 is a several implementation In terms of form, it is optional. Action 803 is one or more associated with a patient care device. The patient care parameters are received. The patient care device of method 801 is disclosed herein. It may be any patient care device, for example, the patient care devices shown in Figures 1, 3, 5, or 7. Devices 7, 14, 15, 16, 17, 35, 126, 128, 130, 148, Figure 8 Patient care devices 14, 15, 16, 17, 830, 810, 812, 814 or Figure 9 One or more of the patient care devices 14, 15, 16, 17, 904, 906, and 908 That's fine.

[0351] Action 805 involves storing one or more patient care parameters in the non-volatile memory of the patient care device. It stores the patient care parameters, including patient treatment parameters or patient status parameters. This can be any value associated with patient care, for example, the infusion rate of the infusion pump is These are patient treatment parameters.

[0352] Action 807 receives one or more operating parameters for a patient care device. The meter can be anything related to the operation of the device. For example, operation parameters The parameters include the injection pump motor speed limit, injection pump speed, wattage limit on wireless communication, and power. This could also be the battery discharge speed or speed limit, or the update frequency. Action 809 is patient care device One or more operating pa...

Claims

1. A system for electronic patient care, A first pattern is detected based on first physiological parameters detected by a first medical sensor; A second pattern is detected based on a second physiological parameter detected by a second medical sensor; If the first pattern and the second pattern are detected within a predetermined time, it is determined that a medical condition exists; A first alert is generated when the first physiological parameter exceeds a first threshold; and A second alert is generated when the second physiological parameter exceeds a second threshold. A processor configured in such a way, An electronic patient care system equipped with [specific features / equipment].

2. The system according to claim 1, wherein the processor is configured to detect the first pattern and / or the second pattern without considering the magnitude of the first physiological parameter and / or the second physiological parameter.

3. The system according to claim 1, wherein the processor is configured to detect the first pattern and / or the second pattern without considering initial values ​​of the first physiological parameter and / or the second physiological parameter.

4. The system according to claim 1, wherein the first pattern is a tendency.

5. The system according to claim 4, wherein the second pattern is the second tendency.

6. The system according to claim 1, further comprising a medical sensor configured to measure the first physiological parameter and / or the second physiological parameter.

7. The system according to claim 6, wherein the processor is configured to receive a signal from the medical sensor and / or transmit a second signal corresponding to the signal.

8. The system according to claim 7, wherein the signal corresponds to the first physiological parameter and / or the second physiological parameter.

9. The system according to claim 1, wherein the processor is executed on a server.

10. The system according to claim 1, wherein the processor is executed within a medical device.

11. The system according to claim 1, wherein the first medical sensor includes the second medical sensor.

12. The system according to claim 10, further comprising the aforementioned medical device.

Images