Systems, methods and devices for electronic patient care

Abstract

To provide a system for patient care in a hospital.SOLUTION: A system includes: determining if a monitoring client is connected to a base through a physical connection; establishing a first communications link between the monitoring client and the base through the physical connection; updating, if necessary, an interface program on the monitoring client and the base through the first communications link; establishing a second communications link between the monitoring client and the base using the first communications link; and communicating data from the base to the monitoring client using the second communications link.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application is a continuation of "Systems, Methods and Apparatus for Communicating Data," filed December 21, 2012. " U.S. Provisional Patent Application No. 61 / 740,474 (Attorney Docket No. J80) This is a non-provisional patent application claiming priority, which is incorporated herein by reference in its entirety.

[0002] This application also relates to a patent application filed on December 21, 2012 entitled "Systems, Methods and Apparatus for Electronic Patient Care." The first patent application was U.S. Patent Application No. 13 / 723,253 entitled "Method and Apparatus for Detecting and Removing Microwave Oscillators," and was subsequently filed in 2013. U.S. Patent Application Publication No. 2013-0191413A1 (Attorney General) published on July 25th This application is a continuation-in-part of the application for the same application numbered J85, which claims priority to the following application: A patent application entitled "Systems, Methods and Apparatus for Infusion," filed December 21, 2011, National Provisional Patent Application No. 61 / 578,649 (Attorney Docket No.: J02); "System, Method and Apparatus for Estimating Fluid Delivery Volume," filed December 21, 2011 U.S. Provisional Patent Application No. 61 / 578,658 (Attorney Docket No. J04); A patent application filed on December 21, 2011 entitled "Systems, Methods and Devices for Oral Drug Delivery" U.S. Provisional Patent Application No. 61 / 578,674 (Attorney Docket No. J05); A patent application filed on May 24, 2012 entitled "Systems, Methods and Apparatus for Electronic Patient Care" U.S. Provisional Patent Application No. 61 / 651,322 (Attorney Docket No. J46); and "Systems, methods and methods for monitoring, regulating or controlling infusion flow" filed August 3, 2012 U.S. Provisional Patent Application No. 61 / 679,117 (Attorney Docket No. J30 ). Each of the above applications is incorporated herein by reference in its entirety. U.S. Patent Application No. 13 / 723,253, filed December 21, 2011, is an "Electronic Patient U.S. Patent Application No. 13 / 333,574 entitled "Systems, Methods and Apparatus for Nursing Care" No. 2012-01, subsequently published on July 19, 2012. No. 85267A1 (Agent Reference Number: J97) and A patent application filed on December 21, 2011 entitled "Systems, Methods and Apparatus for Electronic Patient Care" PCT Application No. PCT / US11 / 66588 (Attorney Docket No. I97WO), This is a continuation-in-part application of US Pat. No. 6,299,499, both of which are incorporated herein by reference in their entireties. U.S. Patent Application No. 13 / 333,574, filed January 21, 2011, is an "Electronic Patient Monitor" The first patent application was U.S. Patent Application No. 13 / 011,543 entitled "Visual System," which was subsequently filed in 201 U.S. Patent Application Publication No. 2011-0313789A1 (published December 22, 2011) This application is a continuation-in-part application of the patent application Ser. No. I52, filed on January 22, 2010. U.S. Provisional Patent Application No. 61 / 29 entitled "Electronic Instruction Intermediation System for Medical Equipment" No. 7,544 (Attorney Reference Number: H53), both of which claim the benefit of priority. is incorporated herein by reference in its entirety.

[0003] This application also relates to a patent application filed on December 21, 2012 entitled "Systems, Methods and Apparatus for Electronic Patient Care." The first patent application was U.S. Patent Application No. 13 / 723,239 entitled "Method and Apparatus for Detecting and Removing Microwave Oscillators," and was subsequently filed in 2013. U.S. Patent Application Publication No. 2013-0297330A1 (Attorney General) published on November 7th This application is a continuation-in-part of the application for the International Patent Application No. J77, which claims priority to the following application: A patent application entitled "Systems, Methods and Apparatus for Infusion," filed December 21, 2011, National Provisional Patent Application No. 61 / 578,649 (Attorney Docket No.: J02); "System, Method and Apparatus for Estimating Fluid Delivery Volume," filed December 21, 2011 U.S. Provisional Patent Application No. 61 / 578,658 (Attorney Docket No. J04); A patent application filed on December 21, 2011 entitled "Systems, Methods and Devices for Oral Drug Delivery" U.S. Provisional Patent Application No. 61 / 578,674 (Attorney Docket No. J05); A patent application filed on May 24, 2012 entitled "Systems, Methods and Apparatus for Electronic Patient Care" U.S. Provisional Patent Application No. 61 / 651,322 (Attorney Docket No. J46); and "Systems, methods and methods for monitoring, regulating or controlling infusion flow" filed August 3, 2012 U.S. Provisional Patent Application No. 61 / 679,117 (Attorney Docket No. J30 ), each of which is incorporated herein by reference in its entirety. U.S. Patent Application No. 13 / 723,239 claims priority to and is based on the following applications: This is a continuation-in-part of the application: A patent application filed on December 21, 2011 entitled "Systems, Methods and Apparatus for Electronic Patient Care" No. 13 / 333,574, subsequently published on July 19, 2012. U.S. Patent Application Publication No. 2012-0185267A1 (Attorney Docket No. J97 This application is based on a U.S. patent application entitled "Electronic Patient Monitoring System" filed on January 21, 2011. Patent Application No. 13 / 011,543, which was subsequently published on December 22, 2011. U.S. Patent Application Publication No. 2011-0313789A1 (Attorney Docket No. I52) This is a continuation of the patent application filed on January 22, 2010, entitled "Electronic Instruction and Intermediation System for Medical Equipment." U.S. Provisional Patent Application No. 61 / 297,544 (Attorney Docket No. H5 3) that claims priority to; and A patent application filed on December 21, 2011 entitled "Systems, Methods and Apparatus for Electronic Patient Care" PCT Application No. PCT / US11 / 66588, filed on September 12, 2013. International Application Publication No. WO2013 / 095459 (Attorney Reference Number: I97 WO), each of which is incorporated herein by reference in its entirety.

[0004] This application also relates to a patent application filed on December 21, 2012 entitled "Systems, Methods and Apparatus for Electronic Patient Care." The first patent application was U.S. Patent Application No. 13 / 723,242 entitled "Method and Apparatus for Detecting and Removing Microwave Oscillators," and was subsequently filed in 2013. U.S. Patent Application Publication No. 2013-0317753A1 (Attorney) published November 28 This application is a continuation-in-part of the application No. J78, which claims priority to the following application: : A patent application filed on May 24, 2012 entitled "Systems, Methods and Apparatus for Electronic Patient Care" No. 61 / 651,322 (Attorney Docket No. J46), which is incorporated herein by reference in its entirety. The disclosure is incorporated herein by reference.

[0005] This application also relates to "Systems, Methods and Methods for Electronic Patient Care," filed May 23, 2013. The patent application is entitled "Device for Producing a Fluorescent Lamp," and was subsequently filed in January 2013. U.S. Patent Application Publication No. 2013-0317837A1 (Attorney General) published on January 28, This application is a continuation-in-part application of the "Electronic Patent Application No. K66" filed on May 24, 2012. U.S. Provisional Patent Application No. 61 / 651 entitled "Systems, Methods and Apparatus for Child Patient Care" ,322 (Attorney Reference Number: J46), both of which are incorporated herein by reference in their entireties. and is incorporated herein by reference. U.S. Patent Application No. 13 / 900,655 is also a continuation-in-part application, which is incorporated herein by reference in its entirety. Claims priority to: A U.S. patent entitled "Blood Processing System and Method" filed on May 24, 2012 Application No. 13 / 480,444, subsequently published on February 14, 2013, U.S. Pat. Publication No. 2013-0037485A1 (Attorney Reference Number: J43); and PCT application entitled "Blood Processing System and Method" filed May 24, 2012 No. PCT / US12 / 00257, subsequently published on November 29, 2012. International Publication No. WO2012 / 161744 (Attorney Reference Number: J43WO).

[0006] This application also relates to a patent application filed on May 23, 2013 entitled "Systems, Methods and Procedures for Electronic Patient Care." PCT Application No. PCT / US13 / 42350 (Attorney Docket No. PCT / US13 / 42350) entitled "Method and Apparatus for :K66WO), which is a continuation-in-part application of "Systems and methods for electronic patient care" and U.S. Provisional Patent Application No. 61 / 651,322 (Attorney Docket No. J46), both of which are incorporated herein by reference in their entireties. PCT Application No. PCT / US13 / 42350 is also a continuation-in-part application, which is incorporated herein by reference in its entirety. Priority of the application of: A U.S. patent entitled "Blood Processing System and Method" filed on May 24, 2012 Application No. 13 / 480,444, subsequently published on February 14, 2013, U.S. Pat. Publication No. 2013-0037485A1 (Attorney Reference Number: J43); and PCT application entitled "Blood Processing System and Method" filed May 24, 2012 No. PCT / US12 / 00257, subsequently published on November 29, 2012 International Publication No. WO2012 / 161744 (Attorney Reference Number: J43WO).

[0007] This application may also be related to one or more of the following patent applications, all filed on December 21, 2012: All of which are incorporated herein by reference in their entireties: U.S. Non-Provisional Patent Application No. 13 / 7 for "Systems, Methods and Apparatus for Clamping" No. 23,238 (Agent reference number: J47); U.S. Non-Provisional Patent Application No. 13 / 72 for "Systems, Methods and Apparatus for Oral Medication Administration" No. 3,235 (Agent reference number: J74); PCT Application No. PCT / US12 for "Systems, Methods and Apparatus for Oral Drug Administration" / No. 71131 (Agent reference number: J74WO); U.S. Non-Provisional Patent Application No. 13 / 1999 for "Systems, Methods, and Apparatus for Fluid Delivery Volume Estimation" No. 724,568 (Agent reference number: J75); U.S. Non-Provisional Patent Application No. 13 / 725,7 for "Systems, Methods and Apparatus for Infusion" No. 90 (Agent reference number: J76); PCT Application No. PCT / US12 / 71 for "Systems, Methods and Apparatus for Infusion" No. 490 (Agent reference number: J76WO); U.S. Nonprovisional Patent for "Systems, Methods, and Apparatus for Monitoring, Regulating, or Controlling Infusion Flow" Patent Application No. 13 / 723,244 (Attorney Docket No.: J79); PCT Application for "Systems, Methods and Apparatus for Monitoring, Regulating or Controlling Infusion Flow" No. PCT / US12 / 71142 (Attorney docket number: J79WO); U.S. Non-Provisional Patent Application No. 13 / 1999 for "Systems, Methods, and Apparatus for Fluid Delivery Volume Estimation" No. 723,251 (Attorney Reference Number: J81); and PCT Application No. PCT / US for "Systems, Methods and Apparatus for Estimating Fluid Delivery Volume" No. 12 / 71112 (Agent docket number: J81WO).

[0008] This application may also be related to one or more of the following patent applications, all of which are incorporated herein by reference: The entire contents of which are incorporated herein by reference: "System for detecting air in a liquid line using active rectification," filed December 18, 2012 U.S. Provisional Patent Application No. 61 / 738,447 (Attorney Docket No. 61 / 738,447) entitled "Systems, Methods and Apparatus" Reference number: J32); U.S. patent application filed March 15, 2013, entitled "Systems, Methods, and Apparatus for Infusion" Patent Application No. 13 / 840,339 (Attorney Docket No.: K14); PCT application filed March 15, 2013, entitled "Systems, Methods and Apparatus for Infusion" T Application No. PCT / US13 / 32445 (Attorney docket number: K14WO); A patent application entitled "Syringe Pump and Related Methods" filed on March 15, 2013 National Patent Application No. 13 / 833,432 (Attorney Reference Number: K21); A patent application filed on March 15, 2013 entitled "System and Device for Electronic Patient Care" National Patent Application No. 13 / 836,497 (Attorney Reference Number: K22); "Systems, Methods and Apparatus for Clamping," filed March 15, 2013 U.S. Patent Application No. 13 / 833,712 (Attorney Docket No. K23) entitled "Compounds for the Prescription of Novel Coronavirus Infections and Related Disorders"; "Systems, methods and methods for monitoring, regulating or controlling infusion flow" filed March 15, 2013 U.S. Patent Application No. 13 / 834,030 (Attorney Docket No. K28 ); "Application filed on July 31, 2013, for detecting bubbles in a liquid line using a split-ring resonant circuit" No. 61 / 860,398, entitled "Systems, Methods and Apparatus for the Presence of a Fluorescent Lamp," Agent reference number: J31); "Systems, methods and methods for monitoring, regulating or controlling infusion flow" filed November 6, 2013 U.S. Provisional Patent Application No. 61 / 900,431 (Attorney Docket No. K5 2); A patent application filed on October 23, 2013 entitled "Syringe Pump and Related Methods" U.S. Provisional Patent Application No. 61 / 894,801 (Attorney Docket No.: K88); A patent application filed on July 8, 2013 entitled "Systems, Methods and Apparatus for Clamping" No. 61 / 843,574 (Attorney Docket No. K74); U.S. patent application Ser. No. 2013 / 08 / 2013 entitled "Electronic Patient Monitoring System" No. 13 / 971,258 (Agent reference number: K84); A patent application filed on November 14, 2013 entitled "Syringe Pump and Related Methods" U.S. Provisional Patent Application No. 61 / 904,123 (Attorney Docket No.: L33); "Foam Detection in Liquid Lines Using Split-Ring Resonant Circuits," filed December 10, 2013 No. 14 / 101,848, entitled "Systems, Methods and Apparatus for Using a Digital Image Processor," Agent reference number: L05); "Systems, methods and apparatus for data communications," filed December 20, 2013 US Patent Application (Attorney Docket No.: L49); "Systems, methods and apparatus for data communications," filed December 20, 2013 PCT application (Attorney Reference Number: L49WO); "Computer-Implemented Method for Electronic Patient Care," filed December 20, 2013 U.S. patent application for "System and Apparatus" (Attorney Docket No. K50); "Computer-Implemented Method for Electronic Patient Care," filed December 20, 2013 PCT application for "Systems and Apparatuses" (Attorney Docket No. K50WO); and "Systems, methods and devices for electronic patient care," filed December 20, 2013 US Patent Application (Attorney Docket Number: L52).

[0009] Technical Field The present disclosure relates to patient care. More particularly, the present disclosure relates to a system for electronic patient care, The present invention relates to a method and an apparatus. [Background technology]

[0010] Providing patient care in a hospital typically involves the work of many professionals and caregivers (e.g. , physicians, nurses, pharmacists, technicians, nurse practitioners, etc.), and a given patient The treatment of these conditions requires the interaction of multiple medical devices / systems. Summary of the Invention [Problem to be solved by the invention]

[0011] Electronic Medical Record (EMR) and Computerized Provider Order Entry (CPOE) Despite the existence of systems intended to facilitate the care process, such as The process of providing comprehensive care to patients, including prescribing and delivering medical care such as medication, Several important issues are involved. [Means for solving the problem]

[0012] In an exemplary embodiment relating to medication prescription and administration, the electronic patient care system 1. A data collection module (e.g., a monitoring client), which communicates instructions or patient-related a second instruction input module having a user interface for receiving information (e.g., For example, a fixed or portable monitoring client may be provided. The monitor displays the patient's current status, such as blood pressure, heart rate, cardiac rhythm, temperature, oxygenation, respiratory rate or ventilation. The device is configured to receive and store measured parameters relating to a condition (e.g., a patient condition parameter). The first module may also be configured to detect, for example, drug allergies or hypersensitivities. , other currently administered medications present in the patient's tissues, age, weight, height, kidney or A first database (e.g., patient-related parameters) containing patient status parameters such as liver function. information about existing parameters related to the patient from the EHR database containing the patient's The first module may be configured to receive, for example, blood pressure, pulse, heart rhythm, or Secondary data such as known drug interactions, drug effects, or existing medications on the respiratory Indicated medications from a database (e.g., drug information database) and / or existing The first module may also be configured to obtain medication information regarding the medication. The currently measured and received existing patient status parameters are compared against known normal ranges and create a table of patient condition parameters that are found to be outside of normal ranges. The first module can then be configured to generate a table of patient condition parameters. Comparing the data with a table of corresponding parameters obtained from a drug information database A match between the patient status parameter table and the corresponding parameter table can be made. If it is found to exist, the first module then sends a Retrieving one or more pre-entered, stored messages for transmission to the These messages may include, for example, the specific medications prescribed, the patient's existing medications and and alerts to the user of the second module appropriate to the patient's current and pre-existing medical condition. Optionally, the alert can be received by a second module, which can then forward the alert to the user interface. The second module is confirmed by the user through an input signal from the interface. This will avoid further repetition of the warning.

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

[0014] In other embodiments, the first module or other modules of the electronic patient care system may be Use a barcode reader or RFID tag at the patient's bedside Identify the prescribed medication to be delivered (through tag and scanner) and schedule the appropriate medication and administration It is also possible to verify that the dose has been prepared and delivered to the patient. The first module may also include a patient device, such as an infusion pump or pill dispenser, that administers the treatment. It can interact with care devices through wired or wireless communication links. In the case of an infusion pump, the first module or another connecting module can tell the infusion pump to provides patient treatment parameters such as infusion setpoints, including infusion pressure, from which e.g. the presence of air in the inlet line, the amount of solution remaining in the connected intravenous bag, or Various operating parameters may be received, such as the pressure of the fluid in the infusion line. If a parameter is found to be abnormal, the first module sends a signal to the infusion pump. Responds by sending a signal to the venous line to interrupt the infusion, or signals a mechanical occlusion. Respond by occluding the inlet, changing the infusion rate, and / or Directly via alarms built into the module or by transmitting alarms to a second module configured to alert healthcare providers and others of anomalies, either by In another embodiment, the first module also monitors the patient's condition and For example, blood pressure monitors, ECG monitors, pulse oximetry monitors, temperature monitors, etc. The device is adapted to communicate with various patient-care devices used to determine patient status parameters. The various parameters measured can be configured by the mobile device and and / or within the EMR, may be monitored and / or recorded. The first module may be configured to monitor the patient condition when the monitored patient condition parameter is outside a predetermined range. The device may be programmed to alert the user or others. In the first module, a signal is transmitted to a monitoring client to monitor the patient-care device. to obtain additional patient status parameters by performing unscheduled measurements. The first module communicates with various healthcare providers in various locations. In one embodiment, the first module notifies the assigned patient of the abnormality. It is possible to prompt corrective action, for example by an audible warning or a recorded message. I can recommend it.

[0015] In one embodiment, the microinfusion pump is prepared using a system monitored Client, pharmacy computer, compounding robot, microinfusion pump, and a data download device. The monitoring client The pharmacy computer is configured to communicate the prescription instructions via the pharmacy computer interface. is in operative communication with the monitoring client to receive prescription instructions. configured to prepare the prescription into at least one liquid corresponding to the prescription instructions The microinfusion pump dispenses at least one liquid corresponding to the prescription instructions. The data download device is configured to receive prescription instructions. The Chloride infusion pump is configured for download into its memory.

[0016] In some embodiments, the compounding robot may be configured to pump a small amount of The compounding robot operates with a data download device. The compounding robot can communicate with the prescription data download device. Instructs the microinfusion pump to download the instructions into its memory. The data download device may download prescription instructions to a compounding robot and / or In some embodiments, the compounding robot may receive the prescription from a pharmacy computer. The pharmacy receives the prescription order from the pharmacy computer.

[0017] In one embodiment of the present disclosure, the system includes a hub. The hub is configured to connect the patient-care devices to the hub. The hub is configured to monitor the operating system components (which can be implemented by the processor) and Sandbox components (which can be embodied as runtime software) The operating system components are responsible for the hardware resources of the hub. access at least one of the software resources of the It is composed of:

[0018] Sandbox components share hardware and software resources. The hub is configured to control access to at least one of the sources. identifies the patient-care device and runs the application to monitor the patient-care device The hub is further configured to run the app in a sandbox component. This allows the application to run in a sandbox environment. A small percentage of hardware and software resources are used through components. Access at least one.

[0019] The hub may be further configured to control a patient-care device. The devices include infusion pumps, pill dispensers, microinfusion pumps, ECG monitors, blood pressure monitor, pulse oximeter, CO2 capnometer, intravenous bag, and / or Or it may be one or more of an infusion flow meter.

[0020] The hub retrieves identifying information (e.g., serial number, encrypted or receives an unencrypted code or other identifying value associated with the identifying information The hub may be configured to download applications from a server. receives an identification from the patient-care device and receives an access request from the server associated with the identification. The application may be configured to update the application.

[0021] Hardware resources include disk drives, memory, buzzers, microphones, The software resources may be variables, secure objects, or devices. Data objects, secure variables, protected APIs, APIs and hardware It may be one of the software representations of the component.

[0022] In yet another embodiment, a system for electronic patient care includes a hub. The hub includes: Configured to monitor patient-care devices. The sandbox is Controlling access to at least one of the following resources: The hub can be configured to identify the patient-care device and The hub is further configured to run a Run the application in a box component, which allows the application The application can access hardware resources and software through the sandbox component. The hub controls the patient-care device and accesses at least one of the software resources. The hub may be further configured to receive identification information from the patient-care device. and downloading the application from a server associated with the identity. The hub may be configured to receive the identification information from the patient-care device and The device may be further configured to update the application from an attached server.

[0023] Hardware resources include disk drives, memory, buzzers, microphones, The software resources may be variables, secure objects, or devices. Data objects, secure variables, protected APIs, APIs and hardware It may be one of the software representations of the component.

[0024] In yet another embodiment, a system for electronic patient care includes a monitoring client. The monitoring client is configured to monitor a patient-care device. The client is responsible for the hardware resources of the monitoring client and the software resources of the monitoring client. an operating system configured to access at least one of the software resources The sandbox component is Hardware and / or software resources The monitoring client is configured to identify and control access to patient-care devices. and further configured to run an application to monitor the patient-care device. The monitoring client may monitor applications in the sandbox component. This allows the application to access the hardware through the sandbox component. Access to at least one of the following: hardware and software resources The monitoring client is further configured to control the patient-care device.

[0025] Patient care devices include infusion pumps, pill dispensers, microinfusion pumps, pump, ECG monitor, blood pressure monitor, pulse oximeter and / or CO2 capnometer The device may be a syringe, an intravenous bag, and an intravenous flow meter.

[0026] The monitoring client receives the identification information from the patient-care device and The device may be further configured to download the application from a server. The patient-care client receives the identification information from the patient-care device and It may further be configured to update the application from the server.

[0027] Hardware resources include disk drives, memory, buzzers, microphones, The software resources can be variables, secure devices, and Data objects, secure variables, protected APIs, API and hardware components It may also be a software representation of a component.

[0028] In yet another embodiment, a system for electronic patient care monitors a patient-care device. The monitoring client is configured to: Controlling access to at least one of the following resources: The sandbox component is configured to monitor the client. identifies the patient-care device and runs the application to monitor the patient-care device The monitoring client may be further configured to: This allows the application to run in a sandboxed environment. of hardware and software resources through components The monitoring client has access to at least one patient-care device. It may further be configured as:

[0029] Patient care devices include infusion pumps, pill dispensers, microinfusion pumps, pump, ECG monitor, blood pressure monitor, pulse oximeter and / or CO2 capnometer The device may be a syringe, an intravenous bag, and an intravenous flow meter.

[0030] The monitoring client receives the identification information from the patient-care device and The device may be further configured to download the application from a server. The patient-care client receives the identification information from the patient-care device and It may further be configured to update the application from the server.

[0031] Hardware resources include disk drives, memory, buzzers, microphones, The software resources can be variables, secure devices, and Data objects, secure variables, protected APIs, API and hardware components It may be one of the software representations of the component.

[0032] In another embodiment, a system for electronic patient care is configured to communicate with an electronic medical record. The hub includes a patient and a patient-care device. The hub may also be configured to identify certain medical devices (e.g., infusion pumps) from the electronic medical record. At least one treatment parameter (e.g., infusion drug, and / or infusion rate or rate) Download the patient care data (e.g., a clinical profile) and The hub is configured to program the RFID device using an RFID interrogator. Reading ID tags, using voice recognition software coupled with a microphone Voice, facial, and biometric reading using facial recognition software coupled with a camera Biometric parameters, identification information, barcode reading by barcode reader In one particular embodiment, the hub identifies the patient according to at least one of the following: The method further comprises: determining at least one treatment parameter using one or more of the identification techniques described herein; You can download the data.

[0033] In another embodiment, a system for electronic patient care is configured to communicate with an electronic medical record. The monitoring client includes a patient-care device. and configured to identify a patient-care device (e.g., an infusion pump). The client also receives at least one treatment parameter (e.g., infusion medication) from the electronic medical record. and / or infusion rate or rate profile) and The patient-care device is configured to program both the patient-care device and the patient-care device with the same therapy parameters. The monitoring client uses an RFID interrogator to read the RFID tag, Voice recognition software integrated into the phone, facial recognition software integrated into the camera Biometric parameters of face biometric reading using software, According to at least one of the following: identification information, barcode reading by a barcode reader In one particular embodiment, the monitoring client identifies the patient using the downloading at least one treatment parameter using one or more of the identification techniques provided; It is possible.

[0034] In yet another embodiment, a system for electronic patient care includes a monitoring client, a monitoring cluster, and Includes a client dock, patient care device and device dock. The antenna is configured to communicate at least one patient-care parameter. The client dock is a patient client dock for docking a monitoring client there. The patient-care device is configured to receive at least one patient-care client. The device dock is configured to communicate patient care parameters. configured to receive a patient-care device for docking the chair thereto. .

[0035] In one embodiment, the monitoring client dock and the device dock wirelessly and a cable operably coupled to the monitoring client dock and the device dock. The device is configured to communicate one way through the router.

[0036] In another embodiment, the monitoring client wirelessly monitors at least one patient-care parameter. It is configured to communicate via

[0037] In another embodiment, the monitoring client dock communicates wirelessly with the monitoring client. The monitoring client is configured to monitor at least one patient-care parameter. Wirelessly with the patient dock, via a cable to the dock, and via a docked patient The patient-care device is in operative communication with the patient-care device by communicating with the patient-care device.

[0038] In another embodiment, the monitoring client is configured to communicate over a cable where communication over a cable is not available. and the monitoring client is undocked from the monitoring client dock, When the monitoring client determines that at least one of the following is true, the monitoring client and operatively communicating at least one patient-care parameter using wireless communication with the network. .

[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 Patient care parameters are transmitted to a docked patient care device to facilitate patient care. The device is in operative communication with the protection device.

[0040] In another embodiment, the monitoring client is configured to communicate over a cable where communication over a cable is not available. Communication between the monitoring client and the monitoring client dock is not available, and the monitoring The monitoring client was undocked from the monitoring client dock, When the monitoring client determines that both are the same, it stops wireless communication with the device dock. The system is utilized to operatively communicate at least one patient-care parameter.

[0041] In another embodiment, the patient-care device is configured to communicate wirelessly with the monitoring client. and the monitoring client transmits at least one patient care parameter to the patient care device. Communicate wirelessly with the chair.

[0042] In another embodiment, the monitoring client is configured to communicate over a cable where communication over a cable is not available. Communication between the monitoring client and the monitoring client dock is not available, device Communication between the dock and the patient-care device is not available, and the monitoring client At least one of the monitoring clients has been undocked from the dock. When the monitoring client determines that at least one patient care device is Operatively communicate care parameters.

[0043] In another embodiment, the monitoring client dock and the device dock include at least The system is further configured to wirelessly communicate one patient parameter. A client dock and a device dock are operably coupled with a cable. The monitoring client dock and device dock are The client dock and at least one of the monitoring clients must have a cable for the communication link. and configured to communicate wirelessly when it determines that the device is not available as a wireless device.

[0044] In another embodiment, the monitoring client communicates with the patient-care device via multiple communication links. and a monitoring client configured to monitor the operation of the plurality of communication links. Communicate through what is possible.

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

[0046] In another embodiment, the patient care parameters include intravenous pump flow parameters, ECG parameters, meter, blood pressure parameters, pulse oximeter parameters, CO2 capnometer parameters Patient parameters, intravenous bag parameters, and infusion flow meter values. The care parameters may be patient condition parameters and / or patient treatment parameters. stomach.

[0047] In another embodiment, the patient-care devices may be wirelessly connected as nodes in a mesh network. is configured to communicate.

[0048] In another embodiment, the cable is connected to the monitoring client dock and the device dock. The patient-care device is docked in the device dock and the monitoring client is operationally coupled. When the Ant is docked in the monitoring client dock, the monitoring client and communicating at least one patient-care parameter to a patient-care device through the cable. It is structured as follows.

[0049] In yet another embodiment, a system for electronic patient care includes a monitoring client, a patient care The device and device dock are equipped. The monitoring client must have at least one The patient-care device is configured to communicate a patient-care parameter. The device dock is configured to communicate one patient care parameter. receiving a patient-care device for docking the care device thereto; The system is configured to receive a monitoring client to dock thereon.

[0050] In yet another embodiment, the system for electronic patient care includes at least one patient care processor. a patient-care device configured to communicate a patient-care parameter; a monitoring client configured to communicate patient-care device parameters and a and a device dock configured to receive the patient-care device for docking. 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 processor. a stackable monitoring client configured to communicate parameters; and at least one a stackable patient-care device configured to communicate two patient-care parameters; Stackable monitoring clients and stackable patient care devices Through 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 processor. a patient-care device configured to communicate a patient-care parameter; Hub Clients configured to communicate patient care devices with the Hub Clients. a device dock configured to receive a patient-care device for docking; The hub is plugged into the device dock and establishes a communication link between the two. The system further includes a monitoring client in operative communication with the hub. , may receive at least one patient care parameter. The patient care parameter may be received from the hub. and the hub can operatively communicate the patient treatment parameters to the patient-care device. Communicate.

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

[0054] In certain embodiments, the monitoring client may include a user interface. The monitoring client sends patient treatment parameters to the patient-care device through the hub. Before doing so, the user may be required to authenticate.

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

[0056] The hub may be configured to monitor the patient-care devices. The hub must have at least one hardware and software resource. It also has a sandbox component configured to control access to good.

[0057] The Hub also identifies the patient-care device and runs the application to communicate with the patient-care device. The hub can be configured to monitor the sandbox components. You can run applications within a sandbox, which allows the application to Hardware and software resources through the box components access at least one of the

[0058] In another embodiment, a system for electronic patient care comprises at least: at least one patient monitor adapted to monitor at least one patient parameter; and operatively communicating with at least one patient monitor to transmit at least one patient parameter thereto. a monitoring client in operative communication with the monitoring client to receive the monitoring signal from the monitoring client; A monitoring server that receives at least one patient parameter from the client.

[0059] In another embodiment, the system further comprises: The system may also include a remote communicator for receiving at least one patient parameter.

[0060] At least one patient monitor must be an electrocardiogram monitor, a blood pressure monitor, a pulse oximeter, The monitoring client may include at least one of a monitor and a CO2 capnometer. The client is configured to download patient information according to a specified unique patient identifier. The unique patient identifier can be coded on a barcode placed on the wristband. The unique patient identifier can be coded into an RFID tag attached to a wristband. Patient information can be coded on the tag (e.g., RFID interrogator). The unique patient identifier is operatively transmitted to the monitoring server. Electronic authorization to communicate patient-specific data can be obtained through the A subset of may be stored in the memory of the monitoring client. , a new prescription is based on a predetermined criteria based on a subset of patient-specific data stored in memory. may be adapted to determine whether

[0061] In another embodiment, the system further comprises: The surveillance client and / or At least one of the remote communicators is adapted to communicate new instructions to the monitoring server. The monitoring server may then determine whether the new instruction meets other predetermined criteria. The device may be adapted to determine

[0062] In another embodiment, the new order may be a medication order, and the monitoring server may New prescriptions are identified by determining whether the prescription is contraindicated with currently prescribed medications. The monitoring server may be adapted to determine whether the communicates with the database to determine whether the new instruction meets other predetermined criteria The monitoring server may also detect when a new instruction does not meet other predetermined criteria. It may be configured to send an alert to the monitoring client.

[0063] In another embodiment, the system comprises at least one of a monitoring client and a monitoring server. The device may include a remote communication device adapted to operatively communicate with the device.

[0064] In another embodiment, the monitoring client may be a desk-based device, a portable device, or a devices, handheld controllers, notebook PCs, netbook PCs, tablet PCs The monitoring client may be a touch screen or a smartphone. It is prepared.

[0065] In another embodiment, the system may further comprise an infusion pump and a monitoring client. The client is in operative communication with an infusion pump. The infusion pump is attachable to a monitoring client. The infusion pump may be detachable from the monitoring client.

[0066] In another embodiment, the system further comprises: a monitoring client docked to the infusion pump; The device has a dock configured to accommodate the device.

[0067] In another embodiment, the monitoring client is operable with the infusion pump via a wireless link. Communicate.

[0068] In another embodiment, the monitoring server is configured to communicate with multiple databases. and at least one of the plurality of databases is connected to another of the plurality of databases. It includes a data format or communication protocol that differs from the base.

[0069] In another embodiment, the monitoring server formats data from multiple databases. and adapted to download the data to a monitoring client. In some specific embodiments, the monitoring client also includes at least one patient profile. In certain embodiments, the patient parameters may be communicated to the monitoring server. Pump treatment progress, ECG signal, blood pressure signal, pulse oximeter signal, one or more of a CO2 capnometer signal, and / or a temperature signal; and and / or at least one of these.

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

[0071] The monitoring client can receive user requests and read patient parameters. , and the monitoring device can be queried to receive patient parameters.

[0072] In another embodiment, the system may further comprise a portable surveillance client. The portable monitoring client is in operative communication with the monitoring client to directly communicate patient information. The portable monitoring client may communicate with the monitoring server, thereby bypassing the monitoring server. modifying at least one parameter of the infusion pump and The device may be configured to communicate the determined parameters to a monitoring server.

[0073] Changes to patient orders presented through a portable monitoring client cannot be made to 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. and storing the patient-specific data in a patient-specific database.

[0075] The system further includes another device adapted to receive information from a patient-specific database. A monitoring client may be provided.

[0076] Information includes patient orders, patient medications, progress notes, monitoring data from patient monitors, and The data may include at least one of therapy data from an attached device.

[0077] The monitoring server queries the electronic health record database and receives patient information therefrom. The monitoring server may further be configured to set a predetermined set of The information can be configured to be input to the monitoring client.

[0078] The predetermined set of information includes the patient's age, height, weight, diagnosis, current medications, medication categories, This may include at least one of drug allergy and hypersensitivity.

[0079] In another embodiment, the remote portable monitoring client communicates with the monitoring client via the monitoring server. The remote portable monitoring client is adapted to communicate with the tablet. It can be one of the laptops, netbooks and PCs. Remote portable monitoring client The device may be equipped with a touch screen.

[0080] In another embodiment, a method for electronic patient care includes the steps of: displaying a plurality of displaying a patient associated with one of the plurality of patients on the display; displaying at least one patient parameter associated with the patient on the display; displaying at least one alert that has been received; and selecting the patient from the plurality of patients. Section.

[0081] In some particular embodiments, the above method further comprises: and transmitting the alert to a portable remote communicator device having That's fine.

[0082] In yet another embodiment, the electronic patient care system comprises at least one of: a monitoring client configured to communicate a patient care parameter of at least one a patient-care device configured to communicate a patient-care parameter; and at least one Discover the presence of one patient-care device and monitor the communication signals from that device. By translating the communication protocol associated with the a communication interface configured to facilitate communication between at least one patient-care device and the patient-care device; Face.

[0083] In certain embodiments, the communication interface further comprises additional other patient-intervention devices that are different from each other. Discover the presence of protected devices and transmit communication signals from these devices to the monitoring client. configured to translate to the associated communication protocol.

[0084] In another particular embodiment, the communication interface further comprises: In yet another particular embodiment, the system is further configured to provide Accessible by the monitoring client taking into account at least one central store of user information one or more databases of patients associated with the available and / or monitoring clients It includes downloadable information that can be used for treatment.

[0085] In yet another particular embodiment, the communication interface further comprises at least one of the following: and (b) performing fault checking for one of the following: communication with the patient-care device. Assess the data integrity of the monitoring client; assess whether the client is functioning properly; Assessing patient-care devices for proper functioning; and / or communication interfaces Evaluate whether the face is functioning properly.

[0086] In yet another embodiment, the electronic patient care system comprises at least one of: at least one hub client configured to communicate patient care parameters; a patient-care device configured to communicate a patient-care parameter; and Discovers the presence of one patient-care device and associates the communication signal from that device with the hub The Hub and at least one patient care device are connected by converting the device to a specific communication protocol. a communication interface configured to facilitate communication between the device and the

[0087] In certain embodiments, the communication interface further comprises additional other patient-intervention devices that are different from each other. It discovers the presence of a protected device and sends communication signals from that device to a communication It is configured to convert the

[0088] In another particular embodiment, the communication interface further comprises: In yet another particular embodiment, the system is further configured to provide One or more accessible by the hub allowing for at least one central store of user information. database and / or can be used to treat patients associated with the Hub It also includes download information.

[0089] In yet another particular embodiment, the communication interface further comprises at least one of: and performing fault checking for: communication with the patient-care device. Assess data integrity; assess whether monitoring clients are functioning properly; Evaluate whether the patient-care device is functioning properly; and / or Evaluate whether the interface is functioning properly.

[0090] In yet another embodiment, the electronic patient care system comprises at least one of: a dock configured to communicate a patient care parameter of at least one patient care a patient-care device configured to communicate a patient care parameter; and Discovers the presence of an elderly care device and associates the communication signal from that device with the dock The dock and at least one patient-care device are connected by translating the A communication interface configured to facilitate communication between a computer and a remote server.

[0091] In certain embodiments, the communication interface further comprises additional other patient-intervention devices that are different from each other. It discovers the presence of a protected device and associates the communication signal from that device with the dock. The communication protocol is configured to convert the

[0092] In another particular embodiment, the communication interface further comprises: In yet another particular embodiment, the system is further configured to provide One or more data accessible by the dock that allows for at least one central store of user information. may be used to treat patients associated with the database and / or the doctor It has download information available.

[0093] In yet another particular embodiment, the communication interface further comprises at least one of: and performing fault checking for: communication with the patient-care device. Assess data integrity; assess whether monitoring clients are functioning properly; Evaluate whether the patient-care device is functioning properly; and / or Evaluate whether the interface is functioning properly.

[0094] In one embodiment, the patient-care device comprises: a body; a conduit in the main body configured as follows; and a conduit connected to the main body, the main body being frictionally locked to the support in the conduit. two friction members configured to:

[0095] In one embodiment, the hub comprises: a patient-care device interface; coupled to a patient-care device interface and providing power to the patient-care device; a processor; and communication between the processor and the patient-care device. a transceiver coupled to a patient-care device interface configured to enable In some particular embodiments, the processor may be configured to: The device may be configured to disable the elderly care device.

[0096] In one embodiment, the dock comprises: a patient-care device interface; coupled to the patient-care device interface and powering the patient-care device a power supply configured to communicate with the patient-care device; a processor; and a transmitter coupled to a patient-care device interface configured to enable communication In some particular embodiments, the processor, when in an alarm state, It may be configured to disable the patient-care device.

[0097] In one embodiment, the communication module comprises: a patient-care device interface; interface; coupled to the patient-care device interface and provides power to the patient-care device a power source configured to supply a processor to the patient-care device and another device; a patient-care device interface configured to enable communication to the patient-care device; In some particular embodiments, the processor detects an alarm condition. may be configured to disable the patient-care device when

[0098] In another embodiment, the patient-care system comprises: a dock; a plurality of modular patient-care devices configured to monitor a patient; and a monitoring client. Retractable display. Modular patient care devices can be staggered or may interface with the dock along the horizontal plane via

[0099] In yet another embodiment, the electronic patient care system receives and stores information about the patient. a first module configured to store the information in a device connected to the patient; data relating to a first parameter of the patient measured by the device, and information about the patient; and a second database including data relating to a second parameter of the patient received from a first database including information on the patient's condition. The first module contains the user interface associated with the second module. and configured to receive medication instructions from a user via a first module; and a second module configured to communicate to the first module. The rule further includes: a) retrieving drug information about the drug or other drugs from a second database; and includes data providing limitations under which such drugs may generally be administered. b) obtaining the medication order, the medication information, the value of the first parameter, and the value of the second parameter; The second module (in this particular embodiment) determines based on the value of the parameter and c) determining whether the a predetermined message is transmitted from the first module to the second module to wherein the message confirms or relates to the acceptability of the medication order. It is designed to warn, communicate, or

[0100] Drug information includes drug interaction information, drug allergy information, blood pressure action information, heart rate action information, etc. The first parameter or The second parameter is the patient's current medications, known drug allergies, Data on current blood pressure, current heart rate, current heart rhythm, current respiratory rate or current ventilation Includes data.

[0101] The predetermined message should include a warning about the potential effects of the indicated medication. The warning can be generated based on measured data for a first parameter, measured data for a second parameter, and The received data includes the medication information obtained by the first module.

[0102] The first module is configured to execute a predetermined message after the predetermined message has been transmitted and after the user has A confirmation signal from the second module is triggered by an input signal from the interface. After receiving the signal, the medication order or amended medication order will be processed. It may be configured to generate a signal.

[0103] In another embodiment, the patient-care device includes a first communication link and a second communication link. The dock includes a first communication link and a second communication link. When the patient-care device is within a predetermined range of the dock, the patient-care device and the dock They are paired using one communication link and, after pairing, use a second communication link. The pairing that is performed using the first communication link remains possible using the second communication link. The patient-care device and the dock may be paired for a communication link. The first communication link may be a short-range wireless communication link and the second communication link may be a Bluetooth Whether it's Bluetooth, Bluetooth Low Energy, WiFi, or other communication links good.

[0104] In another embodiment, the patient-care device includes a first communication link and a second communication link. the monitoring client includes a first communication link and a second communication link. If the patient-care device is within a predetermined range of the monitoring client, and the monitoring client are paired using a first communication link, and Afterwards, the communication continues using the second communication link. This pairing allows the patient-care device and monitoring client to communicate over a second communication link. The first communication link may be a short-range wireless communication. The second communication link is Bluetooth, Bluetooth Low Energy · It may be energy, WiFi, or other communication link.

[0105] In some embodiments, the patient-care device includes a user interface template. The user interface templates are stored in a memory. , docks, hubs and / or monitoring clients to communicate with the docks, hubs and / or monitoring clients. can be displayed on the user interface of the monitoring client. An interface template is a set of one or more patient care parameters received from a patient care device. The device may be configured to display the parameters (e.g., in real time).

[0106] In yet another embodiment, the infusion pump includes an attachable electronic component. The electronic components that can be installed include at least one processor, power regulator, and It is equipped with a pressure regulator, pressure regulator, and control system.

[0107] In one embodiment, the communication module includes at least one processor and a transceiver. , a battery, and one or more of a power supply device, and Provided to patient care devices.

[0108] In yet another embodiment, the wearable system monitor includes a watchdog controller. The wearable system monitor is equipped with a wearable component and a transceiver. a processor coupled to a chuckdog component and a transceiver, It can perform watchdog function for at least one paired device. Paired devices can be docks, hubs, monitoring clients and / or patients. The device may be at least one of a patient care device.

[0109] In yet another embodiment, the method includes one or more of the following steps: establishing a communications link between the patient and the monitoring server; and communicating the patient care parameters to the monitoring server. de-identifying the patient care parameters; and / or de-identifying the patient care parameters in the monitoring server. storing the patient care parameters.

[0110] In yet another embodiment, the method includes one or more of the following steps: establishing a communication link between a plurality of patient-care devices associated with the plurality of patients; communicating patient-care parameters from the plurality of patient-care devices to a monitoring server; storing the patient care parameters in the monitoring server; treating a patient; and determining a plurality of patient care parameters associated with the plurality of patients. Analyzing the subset to determine the effectiveness of the treatment.

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

[0112] In yet another embodiment, a hot-swappable patient-care device, such as an infusion pump, The method includes one or more of the following steps: receiving one or more patient-care parameters in a non-volatile memory of the patient-care device; storing the one or more patient care parameters in the active memory; loading the parameters; and resuming operation of the patient-care device. In an additional embodiment, determining that operation of the patient-care device can resume. may also include:

[0113] In yet another embodiment, a hot-swappable patient-care device, such as an infusion pump, The method includes one or more of the following steps: calculating the operating parameters; and storing the operating parameters in a non-volatile memory of the patient-care device; storing the operating parameters; storing one or more operating parameters in the operating memory; and resuming operation of the patient-care device. In some embodiments, the method includes determining that operation of the patient-care device can resume. Good too.

[0114] In yet another embodiment, the method of pairing includes the steps of: and / or a hub with a user interface connected to a patient care device (e.g., a note placing the patient-care device within operating distance of the patient-care device; displaying the user interface; for pairing using the user interface selecting a patient-care device as a monitoring client and / or pairing the client to the hub; and / or monitoring the patient care parameters. and / or a hub. The method further comprises transmitting additional patient-care parameters through the patient-care device to another patient-care device. operatively communicating with, for example, a monitoring client and / or a hub. This can be done.

[0115] In yet another embodiment, the method includes the steps of: docking the patient-care device into the dock. a step of identifying the patient-care device; a step of controlling the patient-care device; querying the server for applications; and / or downloading into the monitoring client; executing the application using a viewing client; and Controlling a patient-care device using the device.

[0116] In yet another embodiment, a method includes placing a patient-care device in operative communication with a hub. the hub being capable of identifying the patient-care device, The server can be queried for applications to control the device, and the application You can download applications into the hub, run the applications, and applications can be used to control patient-care devices.

[0117] In yet another embodiment, a method includes placing a patient-care device in operative communication with a dock. the dock being capable of identifying the patient-care device, The server can be queried for applications to control the protected device, and the application You can download applications into the dock and run them. and the application can be used to control the patient-care device.

[0118] In yet another embodiment, a method comprises: operatively enabling a patient-care device with a monitoring client; the monitoring client identifying the patient-care device and arranging the monitoring client to communicate with the patient-care device. and querying the server for applications to control the patient-care devices. The application can be downloaded to the monitoring client and and can use the application to It is possible to control the speed.

[0119] In yet another embodiment, the method can include the steps of: Presenting the request on the interface; verifying the request; and transmitting the request. receiving a request with a check value; and verifying that the check value complies with the request before sending it. This is the process of confirming that:

[0120] In yet another embodiment, the hub includes a dock for receiving a patient-care device and a dock for receiving another patient-care device. at least one coupled to the open door configured to receive a patient-care device; and a connector.

[0121] In yet another embodiment, the hub may include a plurality of devices for controlling and / or monitoring the patient-care devices. To achieve this, at least one of the following must be provided: electronic medical record, DERS, CPOE, and / or internet. In operative communication with

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

[0123] In yet another embodiment, the battery pack is connected to a patient-care device interface a battery and a power supply configured to power a patient-care device using the battery The battery is recharged using a DC power source in some embodiments. It is possible.

[0124] In one embodiment, the patient-care device includes a screen and an accelerometer. The patient-care device is configured to display the screen in an upright position determined using an accelerometer. It is structured as follows:

[0125] In yet another embodiment, the electronic patient care system includes a monitoring client and a stanchion. The dock may be configured to couple to the adapter. The adapter includes at least one electronic coupler to connect the patient-care device to the monitoring client. The patient-care device can be placed in operative communication with the adapter. You can also slide it to

[0126] In yet another embodiment, the electronic patient-care system includes a monitoring client, a patient-care device, and patient-care device and / or communication module. The monitoring client is fault tolerant. For example, the monitoring client , the patient-care device cannot be instructed to perform unsafe actions.

[0127] For the purposes of the following embodiments, a base may refer to a medical device, a dock, a cradle, , Hub, Pill Dispenser, Syringe Pump, Infusion Pump, Microinfusion Pumps, communication modules, ECG monitors, blood pressure monitors, pulse oximeters, CO2 It may also be a capnometer, a communication relay, etc.

[0128] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method to determine whether a monitoring client is connected to the base through a physical connection is establishing a communication link between the monitoring client and the base through the physical connection; and, if necessary, communicating the information on the monitoring client and the base through a first communication link. updating the interface program to the monitoring client using the first communication link; establishing a second communication link between the terminal and the base, and and communicating the data from the base to the monitoring client.

[0129] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method is performed when the processor is located on the monitoring client.

[0130] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method is performed when the processor is located on the base.

[0131] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method further comprises communicating data from the base to the monitoring client using a second communication link. and a client monitoring the data by the base using a second communication link. This is done when the method includes a step of transmitting the information to the

[0132] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method further comprises communicating data from the base to the monitoring client using a second communication link. an act of receiving the data by the monitoring client using a second communications link; This is done when the process includes a step of

[0133] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method displays the data to the monitoring client in accordance with the data communicated from the base. The method further includes the steps of:

[0134] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method further includes initializing treatment for the patient using the monitoring client.

[0135] In another embodiment, the method further comprises the step of initializing treatment for the patient using the monitoring client. The method may also be implemented by an operative set of processor-executable instructions, The method further includes treating a patient using the base.

[0136] In another embodiment, the method further comprises the step of initializing treatment for the patient using the monitoring client. The method may also be implemented by an operative set of processor-executable instructions, The method further includes treating the patient using the hemodialysis system as a base.

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

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

[0139] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method further includes removing a physical connection between the monitoring client and the base; and continuing communication between the monitoring client and the base using a second communication link. Further includes:

[0140] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method further includes removing a physical connection between the monitoring client and the base; and continuing communication between the monitoring client and the base using a second communication link. and further comprising monitoring a link quality value of the second communication link.

[0141] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method is to maintain the link quality between the monitoring client and the base station as long as the link quality value exceeds a predetermined threshold. The method further includes communicating the data via the

[0142] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method includes: screening the monitoring client when the link quality value falls below a first predetermined threshold. The method further includes the step of entering a state where there is no lean indication.

[0143] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method includes: screening the monitoring client when the link quality value falls below a first predetermined threshold. The method further includes the step of entering a state in which there is no lean display, in which case the monitoring client A message responding to the absence of a clean display is displayed in the user interface.

[0144] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method includes: screening the monitoring client when the link quality value falls below a first predetermined threshold. The method includes entering a state where there is no lean indication, in which case a message is sent to the user regarding the monitoring cluster. He motions Ianto closer to the base.

[0145] In another embodiment, the monitoring client is notified when the link quality value falls below a first predetermined threshold. operative operation of the processor-executable instructions, including the step of placing the computer in a state without a screen display. The method realized by one set of available link quality values ​​is to measure each link quality value at regular intervals. and determining whether the respective link quality values ​​exceed a first predetermined threshold. Further includes:

[0146] In another embodiment, the monitoring client is notified when the link quality value falls below a first predetermined threshold. operative operation of the processor-executable instructions, including the step of placing the computer in a state without a screen display. The method implemented by the set of available methods is to detect when a link quality value exceeds a first predetermined threshold. When the screen is not displayed, the method further includes the step of leaving the screen in a state where no display is displayed.

[0147] In another embodiment, the monitoring client is notified when the link quality value falls below a first predetermined threshold. operative operation of the processor-executable instructions, including the step of placing the computer in a state without a screen display. The method realized by one possible set is to detect a link quality value greater than a first predetermined threshold. a step of leaving the screen display blank when the predetermined threshold value of 2 is exceeded; Further includes:

[0148] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method may include, if necessary, communicating with an interface on the monitoring client through a first communication link. an act of updating a monitoring client program over a first communication link; The process of transmitting the version number of the interface program from the client to the base, Determine whether the interface program on the client is the latest version. The latest version of the interface program is downloaded from the server by the base. The process of updating the interface program and the latest version of the interface program The method includes the step of overwriting the data with the original data.

[0149] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method includes 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. and, if necessary, interrupting the pairing between the other monitoring client and the base. creating a configuration file using the base; and transmitting the configuration file to a first communication link. communicating from the base to the monitoring client using a link; reading the file by the monitoring client, and connecting the base to the monitoring client for wireless communication. and pair it with the client, and then connect the monitoring client to the base according to the configuration file. This is done when the method includes the step of establishing a second communication link.

[0150] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method involves displaying a screen to the monitoring client when the link quality value falls below a predetermined threshold. The process of entering a non-indicated state, interrupting data communication between the base and the monitoring client. process, and a message requesting the user to move the monitoring client closer to the base. The method includes displaying the page in a graphical user interface.

[0151] In another embodiment, the method is implemented by an operative set of processor-executable instructions. The method is to reset the base to the state without a screen display when the link quality value falls below a predetermined threshold. a step of interrupting communication of data between the base and the monitoring client; and indicating that the base has entered a state without a screen display.

[0152] In another embodiment, a processor-executed The method implemented by one operable set of possible instructions is to provide a method for determining whether a link quality value exceeds a predetermined threshold. and communicating data between the monitoring client and the base as long as the link quality exceeds entering a no screen display state when the link quality value falls below a predetermined threshold; Remaining in a no-screen state as long as the link quality value remains below a predetermined threshold; determining whether the link quality value has returned above a predetermined threshold; and The method includes a step of exiting a state where there is no screen display when the screen is not displayed.

[0153] In another embodiment, a processor-executed The method, as embodied by one operable set of instructions, includes: communicating data between the monitoring client and the base as long as the threshold is exceeded; entering a no screen display state when the link quality value falls below a first predetermined threshold; remaining in a state where the screen display is absent as long as the ink quality value remains below a predetermined second threshold. determining whether the link quality value increases above a second predetermined threshold; exiting the no screen display state when the block quality value exceeds a second predetermined threshold. include.

[0154] In one embodiment of the present disclosure, a system for communicating between a monitoring client and a base is provided. The system includes a base having a communication component that: The monitoring client is configured to: communicating data between the base and the switch when the link quality value falls below a predetermined threshold; Entering a clean state; the screen remains blank as long as the link quality value remains below a given threshold. Determine whether the link quality value returns above a predetermined threshold. and when the link quality value returns above a predetermined threshold, the screen goes from blank to To take off.

[0155] In one embodiment of the present disclosure, a system for communicating between a monitoring client and a base is provided. The system includes a base having a communication component that: The monitoring client is configured to: communicating data between the ant and the base; and determining whether the link quality value is less than a first predetermined threshold. Entering a no screen display state when the link quality value is below a second predetermined threshold. the screen display remains off as long as the link quality value remains above a second predetermined threshold. determining whether the link quality value exceeds a second predetermined threshold; and To get out of a no-screen state when

[0156] In one embodiment of the present disclosure, a system for communicating between a monitoring client and a base is provided. The system includes a base having an update component, the update component Configured to: The monitoring client is connected to the base through a physical connection. determining whether a first connection exists between the monitoring client and the base through a physical connection; establishing a communication link; if necessary, connecting the monitoring client to the first communication link; and updating an interface program on the base; using the first communication link. establishing a second communication link between the monitoring client and the base using the second Communicating data from the base to the monitoring client using the communications link.

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

[0158] In one embodiment of the present disclosure, the update component runs in a sandbox. In some embodiments, the sandbox comprises at least one of a hub, a dock, and a cradle. can also be contained within one.

[0159] In one embodiment of the present disclosure, a system for enabling electronic patient care includes: a monitoring client connected to a base, At least one of the devices has a processor configured to do at least one of the following: establishing a first communication link between the monitoring client and the base through a physical connection; A first communication link connects the monitoring client and the interface program on the base. and updating the system using a first communication link between the monitoring client and the base. establishing a second communications link to

[0160] In one embodiment of the present disclosure, the processor is located on the monitoring client. In one embodiment, the processor is located on the base. A second communication link transmits data from the base to the monitoring client. In an embodiment, the monitoring client receives the data using a second communication link. In one embodiment, the monitoring client is configured to display data communicated from the base. In one embodiment of the present disclosure, the monitoring client is configured to initialize the patient's treatment. In one embodiment of the present disclosure, the base is configured to treat a patient. In one embodiment of the present disclosure, the base is a hemodialysis system.

[0161] In one embodiment of the present disclosure, the base is a patient care device. In form, patient care devices include infusion pumps, pill dispensers, microinfusers, Pumps, ECG monitors, blood pressure monitors, pulse oximeters, CO2 capnometers an intravenous bag and an infusion flow meter.

[0162] In one embodiment of the present disclosure, the system further comprises: a first initiation treatment signal; In one embodiment of the present disclosure, the monitoring client includes a The communication link between the client and the base is wireless. In one embodiment of the present disclosure, the base The second communication link is configured to monitor a link quality value of the second communication link. In this case, the system will communicate with the monitoring client and the base station as long as the link quality value is above a predetermined threshold. The device is configured to communicate data with the server.

[0163] In one embodiment of the present disclosure, the monitoring client is configured to: When the temperature drops below 100°C, the screen enters a no-screen display state. In an embodiment, the monitoring client may be configured to disable the user interface in response to a screen display absence. In one embodiment of the present disclosure, the message is configured to be displayed on the face. The message instructs the user to move the monitoring client closer to the base. In one embodiment, the base measures each link quality value at regular intervals, configured to determine whether the respective link quality values ​​exceed a first predetermined threshold. will be done.

[0164] In one embodiment of the present disclosure, the base is determined based on whether the link quality value exceeds a first predetermined threshold. If the screen is not displayed, the screen is configured to remain blank. In this embodiment, the base is a link quality value greater than a second predetermined threshold that is greater than the first predetermined threshold. If the value is exceeded, the screen is configured to remain blank.

[0165] In one embodiment of the present disclosure, at least one of the monitoring client and the base The interface program is updated through one communication link by at least one of the following: The monitoring client is configured to communicate with the network through a first communication link. configured to pass the version number of the interface program to the base; The client checks whether the interface program on the monitoring client is the latest version. and further configured to determine whether the base is the latest version of the interface program. The version is configured to be read from the server; and the base is configured to be an interface The program is further configured to overwrite the latest version of the interface program. It is done.

[0166] In one embodiment of the present disclosure, the system communicates with a monitoring client using a first communication link. and at least one of the following to establish a second communication link between the client and the base: Configured to: Whether the processor is paired with a base or a different monitoring client If necessary, the processor is configured to determine whether the It is further configured to abort pairing with the base; the base creates a configuration file a first communication link for transmitting the configuration file from the base to the monitoring client; The monitoring client is configured to communicate with the base and the base is configured to pair with the monitoring client for wireless communication. The base that is paired with the monitoring client for wireless communication is stored in the configuration file. Thus, 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 a memory. The memory may be configured to cause one or more processors to: The tablet has an operable set of executable instructions. Determine whether the tablet is connected to the base; establishing a first communication link between the updating an interface program on the printer using the first communication link; establishing a second communication link between the bullet and the base; and Use it to communicate data from the base to the tablet.

[0168] The tablet may be configured to: (1) monitor the operation of the base; (2) controlling the operation of the base; and (3) receiving error conditions from the base. (4) monitoring the operation of the base to determine if any error conditions exist; (5) monitoring the operation of the base to determine whether an unsafe condition exists; (6) storing error or operational parameters and sending them to the server; (7) -or storing operating parameters and transmitting them to the base for storage within the base; (8) Stores error or operational parameters and sends them to the base for relay to the server. and / or (9) watching video games, movies, or other similar activities while the patient is receiving treatment. Providing patient entertainment selected from a group consisting of recorded songs and web browsing. [Brief explanation of the drawings]

[0169] These and other aspects will be more fully understood from the following detailed description of various embodiments of the present disclosure, taken in conjunction with the drawings. A more detailed explanation will make this clearer.

[0170] [Figure 1] FIG. 1 is a block diagram of an electronic patient-care system having two docks according to an embodiment of the present disclosure. [Figure 2]2 is a flowchart illustrating a method for maintaining communication between the monitoring client and the patient-care device of FIG. 1 according to an embodiment of the present disclosure. [Figure 3] FIG. 10 is a block diagram of an electronic patient-care system having two docks with wireless communication therebetween according to another embodiment of the present disclosure. [Figure 4] 4 is a flowchart illustrating a method for maintaining communication between the monitoring client and the patient-care device of FIG. 3 according to an embodiment of the present disclosure. [Figure 5] FIG. 10 is a block diagram of an electronic patient-care system having a dock for docking a monitoring client and a patient-care device together according to yet another embodiment of the present disclosure. [Figure 6] 6 is a flowchart illustrating a method for maintaining communication between the monitoring client and the patient-care device of FIG. 5 according to an embodiment of the present disclosure. [Figure 7] FIG. 10 is 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] FIG. 10 is a block diagram of an electronic patient-care system having a hub according to yet another embodiment of the present disclosure. [Figure 9] FIG. 10 is a block diagram of an electronic patient-care system having stackable monitoring clients and stackable patient-care devices according to yet another embodiment of the present disclosure. [Figure 10] FIG. 10 is a flowchart diagram of 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] FIG. 1 is a flowchart diagram of a method for aggregating patient-care parameters for multiple patients in a monitoring server according to an embodiment of the present disclosure. [Figure 12] FIG. 10 is a flowchart diagram of a method for recovering a patient-care device when operation of the patient-care device is interrupted, according to an embodiment of the present disclosure. [Figure 13]FIG. 10 is a flowchart diagram of a method for pairing a monitoring client with a patient-care device according to an embodiment of the present disclosure. [Figure 14] FIG. 10 is a flowchart diagram of a method for monitoring operation of a patient-care device using a wearable system monitor paired to the patient-care device according to an embodiment of the present disclosure. [Figure 15] FIG. 10 is a flowchart diagram of a method for displaying a user interface using a user interface template according to an embodiment of the present disclosure. [Figure 16] FIG. 10 is a flowchart diagram of a method for downloading an application to control a patient-care device according to an embodiment of the present disclosure. [Figure 17] FIG. 10 is a flowchart diagram of a method for ensuring data integrity when communicating data for a patient-care device according to an embodiment of the present disclosure. [Figure 18] FIG. 10 is a block diagram of an electronic patient-care system according to yet another embodiment of the present disclosure. [Figure 19] FIG. 10 is a block diagram of an electronic patient-care system according to another embodiment of the present disclosure. [Figure 20] FIG. 20 is a block diagram of a dock of the electronic patient-care system of FIG. 19 in accordance with an embodiment of the present disclosure.

[0171] [Figure 21] FIG. 1 illustrates an electronic patient-care system having a tablet docked in a dock with a cable electrically coupled to the patient-care device according to an embodiment of the present disclosure. [Figure 22] FIG. 1 illustrates 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] FIG. 1 illustrates an electronic patient care system having a modular infusion pump docking into a dock having a monitoring client with a retractable user interface, according to an embodiment of the present disclosure. [Figure 24]FIG. 24 is a side view of the electronic patient-care system of FIG. 23 in accordance with an embodiment of the present disclosure. [Figure 25] A diagram showing an electronic patient care system having staggered modular infusion pumps docking into a dock having a monitoring client with a retractable user interface according to another embodiment of the present disclosure. [Figure 26] A diagram illustrating an electronic patient care system having modular infusion pumps docked in a dock along a common horizontal plane, including a monitoring client with a retractable user interface, according to yet another embodiment of the present disclosure. [Figure 27] FIG. 27 is a side view of the electronic patient-care system of FIG. 26 in accordance with another embodiment of the present disclosure. [Figure 28] FIG. 10 illustrates an electronic patient care system having modular infusion pumps docked in a dock along a common horizontal plane, including a monitoring client with a retractable user interface, and having a hub coupled to the scanner and dock, according to yet another embodiment of the present disclosure. [Figure 29] 29 is a side view of the electronic patient-care system of FIG. 28 in accordance with another embodiment of the present disclosure. [Figure 30-32] 10A-10C illustrate several views of a clutch system for mounting an electronic patient-care system on a pole in accordance with an embodiment of the present disclosure. [Figure 33] 1 illustrates an infusion pump and a dock coupled to a support pole, according to an embodiment of the present disclosure. [Figure 34] 10A-10C illustrate another infusion pump coupled to an open connector and an infusion pump with an open connector according to an embodiment of the present disclosure. [Figure 35] FIG. 34 illustrates the infusion pump of FIG. 33 with two additional infusion pumps each coupled to an open connector, according to an embodiment of the present disclosure. [Figure 36] FIG. 36 is a top view of one of the infusion pumps and hub of FIGS. 33-35 according to an embodiment of the present disclosure. [Figure 37]1 illustrates a square-shaped hub with several connectors according to an embodiment of the present disclosure. [Figure 38] FIG. 10 illustrates an electronic patient-care system having a hub coupled to a post according to another embodiment of the present disclosure. [Figure 39] FIG. 10 illustrates an electronic patient-care system having a hub coupled to a support pole and a portable dock with a quick-release handle for removing the portable dock from the hub in accordance with another embodiment of the present disclosure. [Figure 40] FIG. 10 illustrates an electronic patient-care system having a hub coupled to a pole and a dock coupled to the hub according to another embodiment of the present disclosure.

[0172] [Figure 41] FIG. 10 illustrates an electronic patient-care system having a hub coupled to a post according to another embodiment of the present disclosure. [Figure 42] FIG. 10 illustrates an electronic patient-care system having a monitoring client coupled to a hub having a notch for receiving a patient-care device according to another embodiment of the present disclosure. [Figure 43] FIG. 43 is a close-up view of a T-shaped connector that interfaces with the notch of the hub shown in FIG. 42 according to another embodiment of the present disclosure. [Figure 44] FIG. 10 illustrates an electronic patient-care system having stackable patient-care devices and stackable containers for storing infusion bags according to another embodiment of the present disclosure. [Figure 45] FIG. 10 illustrates an electronic patient-care system having a stackable patient-care device that is stackable next to another stack of patient-care devices according to yet another embodiment of the present disclosure. [Figure 46] FIG. 10 illustrates an electronic patient-care system having stackable patient-care devices including a syringe pump patient-care device having a single syringe according to another embodiment of the present disclosure. [Figure 47]FIG. 10 illustrates an electronic patient-care system having a stackable patient-care device including a syringe pump patient-care device having two syringes according to another embodiment of the present disclosure. [Figure 48] FIG. 10 illustrates an electronic patient-care system having stackable patient-care devices each having a display according to another embodiment of the present disclosure. [Figure 49] FIG. 49 is an enlarged view of the handle of the electronic patient-care device of FIG. 48 according to another embodiment of the present disclosure. [Figure 50] FIG. 49 is an enlarged view of the infusion line port of the electronic patient-care system of FIG. 48 showing an infusion line positioned therethrough in accordance with another embodiment of the present disclosure. [Figure 51] 10 illustrates another embodiment of an electronic patient-care system showing removal of stackable patient-care devices according to another embodiment of the present disclosure. [Figure 52] FIG. 10 illustrates an electronic patient-care system prepared for transport according to another embodiment of the present disclosure. [Figure 53] FIG. 10 illustrates an electronic patient-care system having stackable patient-care devices according to another embodiment of the present disclosure. [Figure 54] FIG. 10 illustrates an electronic patient-care system having stackable patient-care devices that are stackable bottom-up according to another embodiment of the present disclosure. [Figure 55] FIG. 10 illustrates an electronic patient-care system having stackable patient-care devices coupled to a support column and stackable from the top down according to another embodiment of the present disclosure. [Figure 56] FIG. 10 is a perspective view of a clutch system for frictionally gripping a pole having a release handle according to another embodiment of the present disclosure. [Figure 57] FIG. 57 is a rear view of the clutch system of FIG. 56 showing a transparent back surface according to another embodiment of the present disclosure. [Figure 58] FIG. 57 is a top cross-sectional view of the clutch system of FIG. 56 according to another embodiment of the present disclosure. [Figure 59]FIG. 1 is a block diagram of a system for controlling an infusion pump according to an embodiment of the present disclosure. [Figure 60] FIG. 1 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] FIG. 1 is a block diagram of an electronic patient-care system having a dock connectable to a patient-care device via a USB connection according to an embodiment of the present disclosure. [Figure 62] FIG. 1 is a process diagram illustrating several stages of electronic patient care, according to an embodiment of the present disclosure. [Figure 63-66] 1A-1D illustrate several configurations of an electronic patient-care system according to embodiments of the present disclosure. [Figure 67] FIG. 1 is a timing diagram of an electronic patient care therapy using an infusion pump according to an embodiment of the present disclosure. [Figure 68A-68B] FIG. 68 is a flowchart diagram of a method illustrating the timing diagram of FIG. 67 according to an embodiment of the present disclosure. [Figure 69-70] 10A-10C illustrate additional configurations of an electronic patient-care system according to embodiments of the present disclosure. [Figure 71] FIG. 1 is a timing diagram of an electronic patient care therapy using an infusion pump according to an embodiment of the present disclosure. [Figure 72A-72B] FIG. 72 is a flowchart diagram of a method illustrating the timing diagram of FIG. 71 according to an embodiment of the present disclosure. [Figure 73] FIG. 10 is another timing diagram of an electronic patient care therapy using an infusion pump according to an embodiment of the present disclosure. [Figure 74] FIG. 74 is a flowchart diagram of a method illustrating the timing diagram of FIG. 73 according to an embodiment of the present disclosure. [Figure 75] FIG. 10 is yet another timing diagram of an electronic patient care therapy using an infusion pump according to another embodiment of the present disclosure. [Figure 76] FIG. 76 is a flowchart diagram of a method illustrating the timing diagram of FIG. 75 according to an embodiment of the present disclosure. [Figure 77-78] 1A-1D illustrate several configurations of an electronic patient-care system according to embodiments of the present disclosure. [Figure 79] FIG. 10 is another timing diagram of an electronic patient care therapy using an infusion pump according to another embodiment of the present disclosure. [Figure 80A-80B] FIG. 80 is a flowchart diagram of a method illustrating the timing diagram of FIG. 79 according to an embodiment of the present disclosure.

[0174] [Figure 81] FIG. 10 is another timing diagram of an electronic patient care therapy using an infusion pump according to another embodiment of the present disclosure. [Figure 82A-82B] FIG. 82 is a flowchart diagram of a method illustrating the timing diagram of FIG. 81 according to an embodiment of the present disclosure. [Fig. 83-89] 10A-10D illustrate several additional embodiments of an electronic patient-care system, according to some embodiments of the present disclosure. [Figure 90] FIG. 2 is a block diagram of the electronics of an embodiment of a hub, according to an embodiment of the present disclosure. [Figure 91] FIG. 1 is a block diagram of an electronic circuit for interfacing with an infusion pump, according to an embodiment of the present disclosure. [Figure 92] FIG. 10 illustrates another embodiment of an electronic patient-care system with patient-care devices docked and arranged vertically within the dock in accordance with embodiments of the present disclosure. [Figure 93] FIG. 2 is a block diagram of the electronics of an embodiment of a hub, according to an embodiment of the present disclosure. [Figure 94] FIG. 2 is a block diagram of the electronic circuitry of a communication module according to an embodiment of the present disclosure. [Fig. 95-98] 1A-1C illustrate some embodiments of an electronic patient-care system having an infusion pump coupled to a communications module, according to some embodiments of the present disclosure. [Figure 99-101] 3A-3C are block diagrams of some of the electronic circuitry of the dock, according to some embodiments of the present disclosure.

[0175] [Figure 102] FIG. 1 is a block diagram of a battery pack according to an embodiment of the present disclosure. [Figure 103-104] 10A-10C illustrate additional embodiments of the electronic circuitry of the dock according to additional embodiments of the present disclosure. [Figures 105-116] 10A-10D illustrate some embodiments of an attachable pump attached to a monitoring client according to additional embodiments of the present disclosure. [Figure 117] FIG. 1 illustrates a backplane for use in an infusion pump, according to an embodiment of the present disclosure. [Figure 118] FIG. 118 is a cross-sectional view of the backplane panel of FIG. 117 according to an embodiment of the present disclosure. [Figure 119-120] 10A-10D illustrate some embodiments of an attachable pump attached to a monitoring client according to additional embodiments of the present disclosure.

[0176] [Figure 121] FIG. 1 illustrates a communication module according to an embodiment of the present disclosure. [Figure 122] FIG. 1 illustrates a communication module attached to a patient monitoring device according to an embodiment of the present disclosure. [Figure 123] FIG. 122 is a diagram of the electronic circuitry of the communication module of FIG. 121 in accordance with an embodiment of the present disclosure. [Figure 124] FIG. 1 is a diagram of an electronic circuit for converting short-range wireless communication to UHF, according to an embodiment of the present disclosure. [Figures 125-127] 10A-10C illustrate several antennas according to additional embodiments of the present disclosure. [Figure 128] FIG. 1 illustrates a patient wrist band with an RFID tag according to an embodiment of the present disclosure. [Figure 129] FIG. 129 illustrates a split-ring resonant circuit used on the wrist band of FIG. 128 in accordance with an embodiment of the present disclosure. [Figure 130] FIG. 1 illustrates a near-field antenna according to an embodiment of the present disclosure. [Figure 131]FIG. 131 illustrates an equivalent circuit of the split-ring resonant circuit of FIG. 130 in accordance with an embodiment of the present disclosure. [Figure 132] FIG. 1 illustrates a 5R checklist that can be displayed on a monitoring client in accordance with an embodiment of the present disclosure. [Figure 133] FIG. 10 illustrates an occlusion checklist that can be displayed on a monitoring client according to an embodiment of the present disclosure. [Figure 134] FIG. 1 illustrates a display of a monitoring client in operative communication with several infusion pumps, according to an embodiment of the present disclosure. [Figure 135] FIG. 10 is a diagram of a display on a healthcare provider's portable monitoring client showing a list of patients whose patient information the provider has access to, in accordance with an embodiment of the present disclosure. [Figure 136] FIG. 10 illustrates a display on a healthcare provider's portable monitoring client showing devices associated with a particular patient, with one-touch access to current data from the device and some of the patient's clinical information, in accordance with an embodiment of the present disclosure. [Figure 137] FIG. 10 illustrates a display on a healthcare provider's portable monitoring client showing a data entry area for a medication prescription for use with an intravenous infusion pump, according to an embodiment of the present disclosure. [Figure 138] FIG. 10 illustrates a display on a healthcare provider's portable monitoring client showing risk factors associated with prescribed medications and suggested courses of action, as generated by the monitoring client, in accordance with an embodiment of the present disclosure. [Figure 139] FIG. 10 illustrates a display on a healthcare provider's portable monitoring client showing a medication prescription ready to be presented by the ordering provider, according to an embodiment of the present disclosure. [Figure 140] FIG. 10 illustrates a display on a healthcare provider's portable monitoring client showing how the monitoring system can display confirmation to the ordering provider that the prescription has been transmitted to the pharmacist, according to an embodiment of the present disclosure.

[0177] [Figure 141] FIG. 1 is a perspective view of a micro-infusion pump coupled to an adapter, according to an embodiment of the present disclosure. [Figure 142] FIG. 1 is a perspective view of a wireless hub device that wirelessly relays data from a patient-care device to a monitoring client, another hub, or a dock, according to an embodiment of the present disclosure. [Figure 143] FIG. 1 is a front perspective view of an electronic patient-care system having a modular patient-care device coupled to a monitoring client via an adapter and a dock according to an embodiment of the present disclosure. [Figure 144] FIG. 144 is a side perspective view of the electronic patient-care system of FIG. 143 in accordance with an embodiment of the present disclosure. [Figure 145] FIG. 144 is an enlarged perspective view of one interface of the patient-care device shown in FIG. 143 according to an embodiment of the present disclosure. [Figure 146] FIG. 144 is a top view of the electronic patient-care system of FIG. 143 in accordance with an embodiment of the present disclosure. [Figure 147] 1 illustrates a system for an electronic patient care system according to an embodiment of the present disclosure. [Figure 148] 1 is a block diagram of an electronic patient-care system according to an embodiment of the present disclosure. [Figure 149] FIG. 149 is a block diagram of the bedside portion of the electronic patient-care system of FIG. 147 and / or FIG. 148 in accordance with an embodiment of the present disclosure. [Figure 150] FIG. 147, 148 and / or 149 is a block diagram of the dock / hub of FIG. 149 according to an embodiment of the present disclosure. [Figure 151] FIG. 149 is a block diagram illustrating the infusion pump circuit of FIGS. 148 and / or 149 in accordance with an embodiment of the present disclosure. [Figure 152] FIG. 10 is a block diagram illustrating a sensor coupled to a mechanism of an infusion pump according to an embodiment of the present disclosure.

[0178] [Figure 153A-153B]FIG. 10 is a flow chart diagram illustrating a method for communicating between a tablet and a base according to an embodiment of the present disclosure. [Fig. 154] FIG. 10 is a flow chart diagram illustrating a method for updating an interface program according to an embodiment of the present disclosure. [Figure 155] FIG. 10 is a flow chart diagram illustrating a method for establishing a second communication link between a tablet and a base according to an embodiment of the present disclosure. [Figure 156] FIG. 10 is a flow chart diagram illustrating a method for communicating data between a tablet and a base as long as a link quality value of a second communication link exceeds a threshold, according to an embodiment of the present disclosure. [Figure 157] FIG. 10 is a flow chart diagram illustrating a method for entering a no screen display state when a link quality value falls below a threshold value, according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0179] Techniques for facilitating patient care are disclosed, including, for example, in one exemplary embodiment: and one or more patient-care devices communicatively coupled to the monitoring client. The patient-care device may be implemented in any number of different functions. and / or may be manufactured by different manufacturers. In one case, such as between a client monitoring station and a variety of different patient care devices, The communication interface, along with discovery and protocol conversion, performs various other functions, e.g. Power provisioning, standards compliance and user interface to name a few. Patient care devices include infusion pumps, microinfusion devices, and Pumps, insulin pumps, syringe pumps, pill dispensers, dialysis machines, artificial ventilation Inhalers, ultrasound diagnostic machines, ECG monitors, blood pressure monitors, pulse oximeters, CO2 capnographs meters, drip counters, drip flow meters, optical Doppler devices, heart rate monitors, intravenous bags, hemodialysis machines, peritoneal dialysis machines, enteral dialysis machines, patient thermometers and / or other bedside devices. The device may be a portable patient care device.

[0180] U.S. Patent No. 6,200,000, filed February 9, 2007, entitled "Fluid Delivery System and Method" Application No. 11 / 704,899, subsequently published October 4, 2007, U.S. Pat. Publication No. 2007-0228071A1 (Attorney Reference Number: E70), February 2007 "Pump Fluid Delivery System and Method of Using Force-Applying Assembly," filed on the 9th of this month, and 11 / 704,896, filed September 20, 2007. U.S. Patent Application Publication No. 2007-0219496 (Attorney Docket No. E71 ), filed February 9, 2007, entitled "Patch-Sized Fluid Delivery System and Method" No. 11 / 704,886, subsequently published September 20, 2007. U.S. Patent Application Publication No. 2007-0219481 (Attorney Docket No. E72), "Adhesives and Peripheral Systems and Methods for Medical Devices," filed February 7, 2007 The patent application was filed on September 20, 2007, and is now U.S. Patent Application No. 11 / 704,897, entitled "Compounds for the Presence of a Novel Microcomputer." Published U.S. Patent Application Publication No. 2007-0219597 (Attorney Docket No. E73) , a U.S. patent application entitled "Infusion Pump Assembly," filed December 31, 2008; No. 12 / 347,985, which was 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" 47,982, subsequently published on November 12, 2009, U.S. Patent Application Publication No. No. 2009-0281497 (Attorney Reference Number: G76), filed December 31, 2008 No. 12 / 347,981 entitled "Infusion Pump Assembly" and subsequently published U.S. Patent Application Publication No. 2009-02758 on November 5, 2009. No. 96 (Attorney Reference Number: G77), filed on December 31, 2008, No. 12 / 347,984 entitled "Pump Assembly" U.S. Patent Application Publication No. 2009-0299289 (published December 3, 2009) Attorney Reference Number: G79), "Infusion Pump Assembly" filed October 10, 2008 12 / 249,882, which was subsequently filed on April 15, 2010. U.S. Patent Application Publication No. 2010-0094222 (Attorney Docket No. F5 1), "System and Method for Administering Infusible Fluids," filed October 10, 2008 The patent application was filed in April 2010 under the name of "U.S. Patent Application No. 12 / 249,636" and subsequently filed in April 2010 under the name of "U.S. Patent Application No. 12 / 249,636" U.S. Patent Application Publication No. 2010-0094261 (Attorney Docket No.: F52), filed October 10, 2008, entitled "Occlusion Detection System and Method" U.S. Patent Application No. 12 / 249,621, subsequently published April 15, 2010. U.S. Patent Application Publication No. 2010-0090843 (Attorney Docket No. F53), 200 "Multi-language / Multi-processor Infusion Pump Assembly" filed on October 10, 2018 and 12 / 249,600, filed April 15, 2010, entitled "Compounds for the Presence of a Novel Microcomputer-Readable Device," U.S. Patent Application Publication No. 2010-0094221 (Attorney Docket No. F54 ), "Infusion Pump Assembly with Backup Power Supply," published November 29, 2011 " U.S. Patent No. 8,066,672 (Attorney Docket No. F55), 2011 "Pump Assembly with Removable Cover Assembly" published on September 13, 2013 U.S. Patent No. 8,016,789 (Attorney Docket No. F56), 2007 U.S. Patent No. 7,306,555, entitled "Loading Mechanism for Infusion Pump," issued December 11, No. 78 (Attorney Reference Number: C54), all of which are incorporated herein by reference in their entirety. These technologies are used to enable seamless communication and fail-safe operation. Many other features, functions and applications will be apparent in light of this disclosure. .

[0181] General Overview As noted above, the process of providing comprehensive care to a patient, e.g., prescribing and delivering treatment, This is related to several important issues, such as the risk of important information being miscommunicated. and that treatment decisions are made without immediate access to complete information, and / or or delays in the execution of prescriptions due to unnecessarily lengthy and inefficient procedures. There is a great possibility.

[0182] More specifically, medication errors can cause hundreds of deaths each year in the United States alone. , potentially affecting thousands or even millions of people. Hospitals may experience many medication error incidents. Medications include insulin, narcotics, heparin, and chemotherapy. These include administering the wrong medication, administering the wrong concentration of medication, or administering the medication at the wrong rate. Delivering drugs or delivering drugs by the wrong route (drugs are given orally, intravenously, Into the pulse, into the muscle, subcutaneously, rectally, locally on the skin, eye or ear, intrathecally, intraperitoneally (It can be administered intravesically or even intravesically). Even with proper labeling, illegible handwriting, miscommunication of drug prescriptions, and Mispronunciation of drugs with such names can still result in drugs being administered inappropriately. To reduce medication error incidents, electronic medical records (EMR) and drug barcodes are being implemented. There is an emerging trend to use EMR systems, for example, to diagnose patients, identify allergies, and Computer Provider Order Entry (CPOE) not compatible with weight and / or age ) and flag prescriptions. However, these systems are widely adopted. The practice has not yet been adopted by the United States, and its implementation is limited to the practice of prescribing, preparing, and administering medications. This can result in significant delays and inefficiencies in the process.

[0183] In addition, drug infusion devices, such as infusion pumps, are designed to minimize the risk of any infusion resulting in significant damage. It is associated with a significant number (e.g., up to one-third) of medication errors. or an incorrect parameter (e.g., drug concentration or infusion rate) is entered. or inappropriately modify existing infusion parameters. Nearly half of all deaths are due to user error, and many of these errors involve injection points. This may be due to an error in programming the pump.

[0184] An effective monitoring system monitors and corrects discrepancies in all aspects of the drug ordering and administration process. This minimizes any of the many adverse events that may result from the treatment. The drug treatment process can be conceptually divided into three stages: prescription stage, drug stage, and The drug prescription is written or When the drug is read out for use or mixed into a solution, or When medications are administered to patients, errors can occur.

[0185] Thus, in accordance with embodiments of the present disclosure, at least one patient-care parameter may be communicated. a monitoring client configured to communicate at least one patient-care parameter; and the presence of at least one patient-care device. Discover and monitor communication signals from that device. protocol to enable monitoring clients and at least one patient-care device and a communication interface configured to facilitate communication between the electronic patient monitor and the patient information processing device. In some embodiments, a patient care system is disclosed. The communication interface passively monitors the operation of the device. The communication interface may also be implemented by other different Additional patient-care devices (e.g., of various manufacturers, capabilities, and / or communication protocols) discover the presence of devices such as mobile phones and monitor communication signals from these devices can be configured to translate to the communication protocol associated with the hub. The communication interface allows for monitoring clients such as tablet computers. Healthcare providers may use the information collected to provide care to patients associated with a monitoring client. Effectively used as a common general user interface that can be used by any One or more databases accessible by the monitoring client. The database may be used for any purpose (as desired by the healthcare facility or database maintainer). Central storage of patient information (in a matrix and database structure) and associated with monitoring clients Information that may be used by healthcare providers in treating patients The communication interface may use wired and / or wireless technology. This can be implemented in several ways, allowing seamless communication between multiple patient care devices. Enables reliable signaling and fail-safe operation. Some patient-care devices, hubs, and docks and / or the monitoring client may simultaneously communicate over two or more communication links; can communicate simultaneously on two frequency channels (in some embodiments, (The data may be redundant.) In some embodiments, the communication module may Provides batteries and sufficient circuitry for ambulatory operation of patient care devices, such as infusion pumps This allows the patient-care device to be used in a portable manner. Additionally or alternatively, a patient wristband can be plugged into the communication module. It can have a battery that can power a patient care device (or some In embodiments, the communication module may be plugged directly into the patient-care device. It can be charged via line.

[0186] In some embodiments, a patient care parameter (e.g., in some embodiments, real-time parameters) to a cloud server for storage. and can be de-identified.

[0187] System Architecture As shown in FIG. 1, the electronic patient care system 100 includes a plurality of electronic patient care devices 200 assigned to each individual patient 2. one or more monitoring clients 1, 4 that may be in physical proximity to a patient 2; Upload information from several different monitoring clients 1, 4 and from various sources a remote monitoring server 3 that downloads information and instructions to the monitoring clients 1 and 4; When in the patient's room, the healthcare provider communicates directly with the monitoring client 1. Interact with the patient to get information about or enter instructions for patient 2. Multiple monitoring clients 1 can interact with one monitoring server 3. The monitoring server 3 is equipped with middleware (for example, the middleware on the monitoring server 3 in FIG. 1). Additionally or alternatively, it may be possible to provide a remote location (e.g., a doctor's office) Providers at the nurse station (5) and hospital pharmacy (6) communicate with the monitoring server (3). Through a link or a hospital local network with each monitoring client 1, 4 as a node It can interact with individual monitoring clients directly through the area network. Cut.

[0188] Remote communicator 11, other monitoring clients 4, nurses' stations 5, or The physician's office will receive a notification of the patient's personal EHR19 or pharmacy dispensing information. The prescription may be for pills, fluids, or other medications. The prescription may be for an infusion pump 7, a syringe, or for other treatments. Fluid is injected using a syringe pump 126 or a microinfusion pump 130. or to dispense pills using a pill dispenser 128. It's okay to have one.

[0189] The pharmacy 6 may include one or more computers connected to a network, e.g., the Internet. receiving a prescription and queuing the prescription within the one or more computers The pharmacy may use the prescription to: (1) For example, a device coupled to the one or more computers that can compound fluids or create pills. or using an automated compounding device capable of monitoring the queue of one or more computers. (2) Fluid reservoir of syringe pump 126; (3) programming the syringe pump 126 (e.g., the treatment (4) Microinfusion (5) Pre-filling the microinfusion pump 130; (6) pre-filling the intravenous bag 170; (7) programming the infusion pump 7; (8) pre-filling a pill dispenser 128; or (9) dispensing medicines according to a prescription. Program the pill dispenser 128 at the station. Automated compounding device, syringe pump 126, one or more of an intravenous bag 170 or a microinfusion pump 130 can be automatically filled with fluid and / or pills into pill dispenser 128. The automatic compounding device uses barcodes, RFID tags and and / or data can be generated. Information in the data may include treatment plans, prescriptions, and / or patient information. do.

[0190] The automatic compounding device includes: (1) a barcode infusion pump 7, a syringe pump 126, and a Microinfusion pump 130, pill dispenser 128 or intravenous bag 1 70, (2) RFID tags are attached to the infusion pump 7, syringe pump 126, and my Chloro infusion pump 130, pill dispenser 128 or intravenous bag 17 0, and / or (3) information or data on the infusion pump 7, syringe port pump 126, microinfusion pump 130, pill dispenser 128, and The device can program the RFID tag or memory in the intravenous bag 170. The data or information may be, for example, a barcode, an RFID tag, or a serial number in memory. or other identifying information to insert prescriptions into infusion pumps 7, syringe pumps 126, my Chloro infusion pump 130, pill dispenser 128 or intravenous bag 17 The database to associate with the 0 (e.g., the patient's EHR or the patient's personal EHR) 19').

[0191] Infusion pump 7, syringe pump 126, microinfusion pump 130 or pill dispenser 128 is connected to (1) syringe pump 126 or intravenous bag 17 (2) whether the microinfusion pump 130 has the correct fluid; (3) whether the pill dispenser 128 has the correct pills; (4) Infusion pump 7, syringe pump 126, microinfusion pump 130 or intravenous bag 170 programmed therapy, syringe pump 126 , compatible with the fluid in the micro-infusion pump 130 or intravenous bag 170 (5) whether the treatment programmed into pill dispenser 128 is whether the dispenser 128 accommodates the pills in it, and / or (6) the infusion pump 7; Syringe pump 126, microinfusion pump 130 or pill dispenser Therapies programmed into the sensor 128 may be transmitted via a patient barcode, RFID, or Determine if the scan is correct for the specific patient (determined from other patient identifying information) The device may have a built-in sensor (e.g., an RFID interrogator or a barcode scanner). That is, in some particular embodiments, the infusion pump 7, the syringe pump 126, the microphone The infusion pump 130 and / or pill dispenser 128 may be RFID Reads one or more serial numbers from a tag or barcode and checks if the value is found in the internal memory. that the values ​​match those obtained (e.g., downloaded via an automated compounding device) and The value is the value found in the patient's electronic medical record (e.g., the patient's EHR19 or patient's personal stored in the personal EHR or by scanning the patient's RFID tag or (patient serial number determined by scanning the barcode by the It can be proven.

[0192] For example, infusion pump 7, syringe pump 126, microinfusion pump 130 or pill dispenser 128 scanner scans the serial number of the patient care device Obtain the barcode of another patient-care device and determine the patient's serial number The patient's barcode can be scanned to identify the serial number of the patient-care device. , (which may have been updated, for example, by pharmacy 22 or the pharmacy's automated compounding device). The electronic medical record is used to determine whether it corresponds to a patient serial number stored in the electronic medical record. Medical record data can be viewed.

[0193] Additionally or alternatively, the monitoring client 6 may include: (1) a syringe pump 1 (2) whether the intravenous bag 26 or intravenous bag 170 has the correct fluid; (3) whether the power pump 130 has the correct fluid; (4) Infusion pump 7, syringe pump 126, microphone Therapy programmed into the infusion pump 130 or intravenous bag 170 However, syringe pumps 126, microinfusion pumps 130 or intravenous (5) whether the program is compatible with the fluid in the pill dispenser 128; whether the programmed treatment corresponds to the pills in the pill dispenser 128, and / or or (6) infusion pump 7, syringe pump 126, microinfusion pump Therapies programmed into the pill dispenser 130 or pill dispenser 128 (e.g., for a particular patient (as determined from barcode, RFID, or other patient identification information) To determine whether the injection is correct, the infusion pump 7, syringe pump 126, pill dispenser 128, microinfusion pump 130 or intravenous bag 170 Additionally or alternatively, the monitoring client 1 may Pump 7, syringe pump 126, microinfusion pump 130 or round The medication dispenser 128 may be, for example, an infusion pump 7, a syringe pump 126, a microinjector, or the like. on the infusion pump 130, pill dispenser 128 or intravenous bag 170 Validate or download prescriptions using barcode serial numbers Consult the electronic medical record database 19 or 19' and / or the pharmacy 22 to It is possible.

[0194] Optionally, instructions or requests are transmitted to a patient-care device 7, 14, 15, 16, 17, 35 , 126, 128, 130, 148, for example, bolus volume, infusion flow rate, total the meter delivered fluid, the start time of drug delivery, the stop time of drug delivery, or the delivery flow rate profile Infusion pump 7, syringe pump 126 and / or microinfusion pump monitoring client 1, other monitoring clients 4 and / or or a remote communicator 11. In some embodiments, e.g. , pill dispensing instructions for dispensing pills, pill types, pill dispensing schedules, and / or to send instructions or requests, such as a maximum pill dispensing criterion, to the pill dispenser 7. One or more of clients 1, 4, and 11 may be used. The maximum pill dispensing criteria is The maximum amount of drug that can be delivered in a given time period, e.g., if a particular drug is The drug is taken as needed (i.e., when needed), but if taken in excess, the drug is safe. It may not be possible to set a maximum pill dispensing standard, such as "a specified amount within a specified time." This can prevent the drug from being ingested by the patient in unsafe amounts.

[0195] Optionally, patient-care devices 7, 14, 15, 16, 17, 35, 126, 128 , 130, 148 also determine whether an alarm or alert should be issued or transmitted. determining whether a treatment or condition is safe for a patient, system 10 Determine if the system is operating properly or within predetermined boundaries and / or monitor the system. the display of the client 1, other monitoring clients 4 and / or remote communicators 11. To display data on the screen, monitor the data on client 1, and then monitor the other client. 4, and / or the remote communicator 11. For example, the optional Infusion pump 7, syringe pump 126 and / or microinfusion The pump 130 controls the upstream pressure, the change in the upstream pressure, the downstream pressure relative to the patient 2, and the the change in downstream pressure relative to the infusion line, the presence or absence of air in the infusion line, and the actual bolus volume delivered. Actual infusion rate, actual total fluid delivered, actual start time of drug delivery, actual time of drug delivery The downtime or actual delivery flow rate profile can be monitored by monitoring client 1, other monitoring clients, Client 4 and / or Remote Communicator 11 (if applicable) In another embodiment, the pill dispenser 128 can optionally communicate with, for example, For example, the actual pills dispensed, the actual pill type dispensed, and the actual pill quantity at the time of dispense. Monitoring clients can access data such as delivery schedules or whether maximum pill delivery criteria have been exceeded. The client 1 can reply to other monitoring clients 4 and / or remote communicators 11. This can be done.

[0196] Patient care devices 7, 14, 15, 16, 17, 35, 126, 128, 130, 14 The data received from 8 may be used in any predetermined manner to generate alarms and / or alerts. For example, one or more of monitoring clients 1, 4, and 11 can be analyzed for status. Infusion pump 7, syringe pump 126 and / or microinfusion pump Increased pressure downstream of the pump 130 may be used to prevent excessive clotting, seepage, blockage or obstruction of the tubing to the patient. by kinking or by materials such as contamination found within the intravenous bag 170. It can be used as an indication of downstream blockages. In response to the sudden increase in These alarms and / or warnings may be audible or audible. The alert may also prompt the nurse to take other appropriate action, e.g., downstream pressure on the patient is at a predetermined level. Replace needle if blockage (e.g., caused by clotting) occurs when the threshold rises above or when downstream pressure to the patient rises above a predetermined threshold. It can inform you to make suggestions to check for internal bends.

[0197] Additionally or alternatively, a sudden drop in downstream pressure to the patient 2 may This is an indication that the needle has become dislodged from the needle and / or that the needle is now removed from the patient. Depending on the patient, one or more of monitored clients 1, 4, and 11 may have tubing for continuous infusion. Provides visual and / or audible prompts to the user to reattach the needle or insert a new needle. An alarm or warning can also be issued when, for example, the tube is coming out of the needle. The patient may be bleeding when the device is disconnected from the knee. The dowel coupler may be bleeding, indicating that action must be taken quickly. do.

[0198] In some embodiments, one or more infusion pumps 7 may also or alternatively be used. The upstream pressure relative to the Contamination within the intravenous bag 170 can 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 upstream pressure on pump 7 may drop below that which would occur if there were no upstream blockage. Therefore, one or more of the monitoring clients 1, 4, 11 may be configured to monitor the upstream pressure. If the temperature drops below a threshold, an alarm or alert may be issued, for example to alert a caregiver to the tube or Suggest or request that the IV bag 170 be replaced to relieve the obstruction. There is a saying.

[0199] One or more of the monitoring clients 1, 4, 11 optionally monitors downstream pressure relative to the patient 2. infusion pump 7 to stop fluid delivery in response to a sudden rise and / or fall in , syringe pump 126, and / or microinfusion pump 130 The instructions may be sent to one or more.

[0200] As shown in FIG. 1, and in accordance with some embodiments, the system 100 includes a monitoring client. The monitoring client includes an Ant Dock 102 and a Device Dock 104. The dock 102 is configured to receive the monitoring client 1 and the device dock 104 receives one or more patient-care devices to facilitate bedside patient care. The device dock 104 is configured to: Although shown to be capable of receiving some patient care devices, other In an embodiment, the device dock 104 can accommodate one patient-care device, multiple patient-care devices, or or any number of patient-care devices. The monitoring client dock 102 is capable of receiving one monitoring client 1. Although shown as such, in other embodiments, the monitoring client dock 102 may include two One monitoring client1, three or more monitoring clients1, or any arbitrary number of monitoring clients It is possible to receive a viewing client 1.

[0201] In this exemplary embodiment, a cable 110 is coupled to both docks 102, 104. The cable 110 is connected to one of the docks 102, 104 to provide a communication link therebetween. or both, and may be permanently attached or attachable. Alternatively, the cable 110 may be connected to one or both of the docks 102, 104. may have one or more connectors (not explicitly shown) to plug into both .

[0202] In some embodiments, the docks 102, 104 may include one or more wired connections within the cable 110. The devices can communicate with each other using earphones and / or waveguides. In an embodiment, the cable 110 comprises a fiber optic waveguide and connects the docks 102, 104 In other embodiments, as will be appreciated in light of this disclosure, The module 110 may, if desired, include one or more wireless communication links (e.g., Bluetooth, etc.). ) can be substituted. Still other embodiments may use a wired connection between the docks 102, 104. and a combination of wireless communication channels may be utilized. Any number of suitable wired connection types can be used in various embodiments.

[0203] In some embodiments, the communication link between the docks 102, 104 may be serial, parallel, or both. communication, synchronous communication, asynchronous communication, packet-based communication, virtual circuit-based communication, etc. Any known communication link may be used. Therefore, in some embodiments, the communication link established between the docks 102, 104 may be wireless. Wire communication, wired communication, connectionless protocols, e.g., User Datagram Protocol Protocols such as UDP (User Datagram Protocol), or connection-based protocols such as Transmission Control Protocol (TCP) For example, communication between the docks 102 and 104 can be performed using a universal Serial bus standards, SATA, eSATA, Firewire, Ethernet standards, Fiber Channel, Bluetooth, Bluetooth Low Energy, WiFi, The network may be based on one or more of any physical layer technology, any OSI layer technology, and the like.

[0204] When monitoring client 1 is docked in monitoring client dock 102, The monitoring client 1 has access to the communication between the docks 102 and 104. For example, in some embodiments of the present disclosure, the monitoring client 1 is connected to the Through the provided communication link, electronic circuitry within the device dock 104, such as memory and Additionally or alternatively, the monitoring client 1 may the communication link provided by the bus 110 and / or one or more wireless communication links. can communicate with any device docked in the device dock 104. Yes, you can (described in more detail below).

[0205] With further reference to the exemplary embodiment shown in FIG. 1, the device dock 104 includes: Optionally, an attachable display 134, a camera 136, and a microphone 13 It can be equipped with various accessories such as a monitoring client dock 102. , various accessories such as a camera 140 and a microphone 142, each of which is optional. The surveillance client 1 may include a camera 144 and a The camera 136, 146, and various other accessories may be included. 0, 144, for example, providers (e.g., nurses, nurse practitioners, physicians) and / or facial recognition software to authenticate or identify the patient's presence. Additionally or alternatively, a microphone 138, 142 and 146, for example, to authenticate or identify the presence of a provider and / or patient. In light of this disclosure, As can be seen, cameras 136, 140, 144 and microphones 138, 142, 1 46, for example, before starting treatment to ensure the right patient receives the right treatment. The patient may communicate with a remote care provider and / or (e.g., via voice and / or face to enable confirmation of patient identity (using recognition technology, retinal scans, etc.) It can also be used for

[0206] As shown in FIG. 1, in some embodiments, a monitoring client 1, a monitoring client The dock 102 and the device dock 104 each include an antenna 11 for wireless communication. 2, 106, and 108 (each antenna 112, 106, and / or 108 (This is optional.) If the cable 110 is unplugged or the dock 10 is disconnected via the cable 110 If communication between the 2, 104 is interrupted or impaired in any other way, the monitoring client 102 and the device dock 104 receive the established wireless signal through antennas 106 and 108. They can continue to communicate with each other using a wired communication link. If the monitoring client 1 is removed from the monitoring client dock 102, can communicate directly to the device dock 104, for example, and / or to a monitoring client. Client 1 communicates via cable 110 or wireless communication between docks 102, 104. by wirelessly communicating with the monitoring client dock 102, which relays the communication over the link. As previously described, the device can communicate with the device dock 104. a monitoring device 1 and a dock 104 for communicating with various devices docked in the dock 104; The communication between the device dock 104 and the monitoring client 1 can be utilized. do.

[0207] In some embodiments, the monitoring client 1 may be, for example, a monitoring client dock 1 For docking to the 02 and monitoring client dock 102 and monitoring client Two of the connectors on Monitoring Client 1 are used to provide electrical communication between the By measuring the voltage or impedance between the electrical contacts of one or more connectors whether one or more electrical contacts of the monitoring client dock 102 are electrically engaged with the monitoring client dock 102; Making an electrical determination to determine whether the cable 110 is available as a communications link In addition, the monitoring client 1 can receive power from the cable 110. If it is determined that the cable 110 is not air-coupled, it is determined that the cable 110 is not available. Additionally or alternatively, in some embodiments, the dock 10 The magnetic force in the monitoring client 2 engages with the Hall effect sensor in the monitoring client 1, which then The monitoring client 1 uses the sensor to detect when the monitoring client 1 is not docked. The monitoring client 1 assumes that the communication link 110 is not available. Additionally or alternatively, the monitoring cluster may determine whether the The circuitry within the Client Dock 102 is used to communicate when a cable is not available as a communications link. In some embodiments, a signal can be sent to the monitoring client 1. Client 1 periodically connects to the device dock 104 via cable 110. The monitoring client can "ping" the device within a given time. If the monitoring client 1 does not receive a response from the device dock 104, the monitoring client 1 0 is not available as a communication link.

[0208] Monitoring client 1 determines that cable 110 is not available as a communication link In this case, the monitoring client 1 will use the speaker and / or vibration motor to generate an alarm or An alarm or alert may be issued and the alarm or alert may be sent to the remote communicator 11 to Uses a speaker and / or vibration motor to alarm or alert the remote communicator. and / or the monitoring client 1 may communicate with the patient care provider via other communication links. As used herein, the term "alert" refers to a device that is For example, you may want to avoid drawing attention to the object until the cause for alarm remains after a certain time has elapsed. The policy is intended to include "soft" vigilance.

[0209] In some embodiments of the present disclosure, the monitoring client dock 102 includes minimal circuitry. Used or unused circuit, monitoring client 1 to cable 110 For example, in some embodiments of the present disclosure, the monitoring The client dock 102 is electrically coupled directly to the cable 110 from the monitoring client 1. Additionally or alternatively, some implementations of the present disclosure may In some embodiments, the device dock 104 may use minimal or no circuitry. monitoring various docked devices and / or or one or more wires or waveguides that facilitate communication between the monitoring clients 1. The device dock 104 may be a cradle in some embodiments.

[0210] In an embodiment of the present disclosure, each monitoring client 1 is assigned to a particular patient 2 and It may be computer-based, portable, or handheld, and provides display and user The monitoring client 1 may be portable and may have an input capability. This allows for efficient data browsing and data entry, and the monitoring client 1 notebooks, netbooks, and touchscreen PCs with or without touch screens It may also be a tablet PC or a "smartphone." In some embodiments, the monitoring client 1 and / or the remote communicator 11 It is docked or mated to a cable connected to a much larger display, By using a much larger display (e.g., a 24-inch display), the monitoring The display may be on the client 1 and / or the remote communicator 11. The much larger display allows for monitoring clients and / or remote communicators Touch screen capability, touch pen input capability, keyboard input capability, remote It may have input capabilities such as control input capabilities. For example, an x-ray or patient imaging facility. The file viewing can be performed by using a monitoring client 1 and / or a remote communicator 11. This can be facilitated by docking the device into a monitoring dock coupled to the display. This allows caregivers to view patient imaging files on a larger display. The Viewing Dock can also be used by the monitoring client and / or the remote communicator. The battery 11 can be charged.

[0211] Monitoring client 1 is compatible with Linux-based operating systems, Android Blackberry-based operating system System, tablet-based operating system, iOS, iPad OS, i It can run a specific monitoring client for a specific patient. The designation of the first port may be, for example (but not limited to), a bar embedded in the wristband 118. Some of the features include a unique patient identifier encoded on the code 114 or RFID tag 116. This can be done using one of several methods. a scanner to determine the unique patient identifier of the code 114 or RFID tag 116 120. The scanner 120 is a laser barcode scanner, CCD-based barcode scanners, near-field communicators or interrogators, RFID readers, etc. In other embodiments, the unique patient identifier may be based on biometric data of the patient. In one such exemplary case, biometric capabilities (e.g., facial and / or voice recognition) retina scan, blood type monitor, fingerprint scan, etc.) embedded within the surveillance client 1 The device dock 104 may include, or may be otherwise associated with, Unique patient identifiers for the monitoring client dock 102, the monitoring client 1, and the monitoring server 3, remote communicator 11, other monitoring client 4, another server or electronic computing device to facilitate treatment of patient 2.

[0212] The monitoring client 1 is a microprocessor, a microcontroller, a logic device, and one or more digital circuits, analog circuits, etc., to monitor the care, condition, disease, or It can communicate (e.g., send or receive) information related to the treatment. Client 1 receives patient care data such as patient status parameters and / or patient treatment parameters. Some exemplary patient status parameters can be transmitted or received. The data includes blood pressure, body temperature, heart rate, pulse oximetry, CO2 levels, blood oxygen levels, and These measures include patient alertness, patient awareness, and patient responsiveness. Parameters include the drug being administered, the flow rate of the drug or fluid, the drug administration schedule, or or other bedside treatment parameters.

[0213] In some embodiments, for example, the monitoring client 1 may be physically associated with the infusion pump 7. can be attached, can be permanently attached, can be attached and can be removed from This means that two devices, e.g. For example, docking-in between the monitoring client dock 102 and the device dock 104 In one such embodiment, the monitoring client The client 1 is connected to an electrical connector, for example, through electrical contact with the docks 102, 104. or transceiver on each device using the respective antennas 112, 122A. The pump (or other patient care device) can be connected in several ways, including wirelessly via a Additionally or alternatively, the infusion pump may communicate with the monitoring client. When the monitoring client 1 is in operative communication with the monitoring client 1, the specific It may also include pre-programmed treatment data that indicates a particular treatment for the patient.

[0214] The monitoring client 1 also has access to one or more databases within the facility 8 and to the outside facilities 9, 10. departmental databases and / or public health professionals (including, for example, physicians, nurses, and pharmacists) Communicate with your healthcare provider using a Tablet Communicator 11 This is the case for devices such as Category 5 local area network connectors, USB Wired connection to the facility server 8 through a connector in the patient's room (e.g., wired Ethernet) or by wireless (e.g., WiFi, 3G, 4G, EVDO, WiMax, etc.) In one embodiment, intra- and extra-facility data Access to the database is through the monitoring server 3 (e.g., using middleware) mediated13, and then software and application programming interfaces Converging interfaces to handle data with heterogeneous organizations, formats, and communication protocols Therefore, in the embodiment of the present disclosure, any software can communicate with the The software update can be largely limited to the monitoring server 3, and the individual monitoring clients 1, 4, 1 Optionally, the monitoring client 1 may be configured to perform injection Communicate with patient treatment devices, such as pumps, to provide information about the progress of treatment (e.g., operating parameters) In another embodiment, the system can receive information related to the patient's condition and provide operational instructions to the patient treatment device. The monitoring client 1 may also communicate with patient-care devices for diagnostic or monitoring purposes. and patient status parameters (e.g., electrocardiogram (ECG) monitor 14, blood pressure (BP) monitor 15, other devices such as a pulse oximeter or CO2 capnometer 16, or a temperature monitor receiving read information from the device, and potentially 14, 15, 16, 17 as desired by the provider or algorithm The user may be instructed to perform a read if necessary.

[0215] In an embodiment of the present disclosure, the facility service 8 and / or the adverse drug event network 9 It can also be equipped with a Drug Error Reduction System (DERS). First set of predetermined criteria for triggering a hard alarm and / or a hard alarm. A soft alarm may include a second set of predetermined criteria for initiating the alarm. Use the user interface of the infusion pump 7 and / or monitoring client 1 can be overridden (e.g., stopped) by a caregiver (and may be audible and / or A hard alarm may be a simple alarm or a vibration alarm only, while a hard alarm may be an alarm that is triggered only after its cause has been removed. Discontinue treatment until

[0216] In yet a further embodiment of the present disclosure, the DERS system defines a soft limit. The first set of predetermined criteria that defines the minimum and / or maximum limits, and / or the second set that defines the hard limits. Hard and soft limits may include predefined criteria for size, weight, age, etc. , therapeutic limits, such as drug dosage limits, based on other patient parameters or other criteria. The soft limit defines the threshold for treatment even if the treatment falls outside the first set of predetermined criteria. without using the user interface of the infusion pump 7 and / or monitoring client 1. The device can be disabled by a caregiver and treatment can be initiated, while the hard The limit is set to meet a second set of predetermined criteria that defines the hard limit. Prevent treatment from starting until the condition is changed.

[0217] As further seen in the exemplary embodiment of FIG. 1, the system 100 also includes a communications module. Each of the antennas 122A to 122K is connected to a corresponding one of the antennas 124A to 124K. In some embodiments, each of the communication modules 124A-124K may include any optional and / or each device may have integrated communication capabilities Each of the communication modules 124A to 124K is configured to couple to a respective device. In another embodiment, the connectors of the communication modules 124A to 124K are They are permanently integrated into the device shown as installed in Figure 1. There are.

[0218] Each of the communication modules 124A-124K optionally supports one or more wireless links. through each other, to the device dock 104, to the monitoring client dock 102, The monitoring client 1, the remote communicator 11, the monitoring server 3, the local area network Networks and / or wide area networks (e.g., the Internet) 8 to a hub 802 (see FIG. 8) for communicating and / or otherwise One or more transceivers for communicating with any other device that has sufficient wireless communication capabilities. In some specific embodiments, the communication modules 124A-124K include For example, IEEE802.14.4, Zigbee, XBee, Wibree, IE It can operate as a wireless mesh network using EE802.11, for example. In a more general sense, the modules 124A-124K and the system 100 Other components (e.g., docks 102 and 104, monitoring clients 1, 4, 1 1) may be communicated between (e.g., monitoring clients 1, 4, 11 and / or or statically (to accommodate mobility of various medical devices associated with the dock 104). Whether in a dynamic, ad-hoc, or other topology, the devices described herein Any device discovery, handshaking, and / or inter-device communication that enables It can be implemented using a wireless communication protocol.

[0219] In other embodiments, each patient-care device may not include a module, and may have three or more modules (e.g., communication modules). A module may have certain features, for example WiFi, and the user may want to enable certain features. It is possible to select multiple modules each having their own characteristics and combine them together. The group of rules can then be applied to a patient care device, e.g., an infusion pump. Considering yet another embodiment, each module may have a primary processor, a backup processor, and a The processor may include a processor, and functional circuits, all in operative communication with each other. The functional circuitry may include a wireless transceiver, a battery, and an interface to a touchscreen or display. interface (allowing the display to be attached to the housing), wire connections, Bluetooth, Bluetooth Low Energy, WiFi, 3G, 4G, Coprocessor a control system (e.g., for controlling an infusion pump), a fluid measurement circuit, Selected modules can be connected to each other, for example in a daisy chain. The selected module can then be connected to the infusion pump. In this embodiment, for example, via a CAN bus, wired communication, wireless and / or other capable of operatively communicating with each other to coordinate their operations and / or functions .

[0220] Each module can include a speaker and a microphone. When two or more modules are connected to each other, they function as one module. One module sends a signal audibly to the speaker, while another module uses the microphone. This allows you to adjust the speaker's behavior and determine whether it is functioning properly. Several modules can each use their speakers at different frequencies. This allows any one of the modules to transmit sound through its microphone. It can detect voices and demodulate their different frequencies to test several speakers simultaneously. The test may be requested by the first module to the second module, and the second The second module can transmit the results of the test to the first module.

[0221] With continued reference to FIG. 1, one or more of the communication modules 124A-124K may also optionally Optionally, it may include one or more batteries to power devices coupled to it. For example, communication module 124A may be coupled to infusion pump 7 to provide power thereto. Other structures and functions of the communication modules 124A to 124K may be It can be provided depending on the purpose and function of the associated device. In some embodiments, the infusion is controlled by an infusion pump, and input regarding the desired delivery is received from the infusion pump. This is done at the input pump, and thus, in some embodiments of the present disclosure, the communication module 12 4A executes a control algorithm, e.g., a proportional-integral-derivative (PID) control loop, to In such a case, the monitoring client 1 may, for example, (e.g., wireless The fluid flow signal can be communicated to the communication module 124A (via a link), After this, the fluid is pumped through electrical contacts coupled to the motor (not explicitly shown) of the infusion pump 7. A signal corresponding to the flow signal is applied to achieve the desired flow rate. In this state, the infusion pump 7 receives a signal from the flow meter provided in the infusion pump 7 to the communication module 124. A, thereby providing one or more feedback signals to the communication module 124 A controls the operation of the injection pump 7 (e.g., some aspects of the operation of the PID control system, etc.). The results are delivered to the monitoring client 1 and are then used by the QT-based G In some embodiments, the UI may be displayed to the user using a GUI such as , monitoring client 1 is a tablet). In addition, or alternatively, several In some embodiments, the drip flow meter 148 is used to measure the flow rate associated with the drip flow meter 148. The flow rate is transmitted to the communication module 124A via the communication module 124K and the antenna 122K. can be communicated wirelessly.

[0222] As will be appreciated in light of this disclosure, communication modules 124A-124K may be used in conjunction with various patient care devices. Operatively connected to protection devices 7, 14, 15, 16, 17, 35, 126, 128, and 148 For example, still referring to FIG. 1, communication module 124B may be a serial The communication module 124C is operably coupled to the pill dispenser 126. 28. Additionally or alternatively, the communication module 12 4E is operatively coupled to the ECG monitor 12, and the communication module 124F is operatively coupled to the blood pressure monitor The communication module 124G is operably coupled to the pulse oximeter / C The communication module 124H is operably coupled to the O2 capnometer 16 and is connected to other monitors. 17, and the communication module 124I is operably coupled to the patient's intravenous access 35. operatively coupled to the communication module 124K, and the communication module 124K is operatively coupled to the drip flow meter 148. Each of the communication modules 124A to 124K is connected to Patient care devices 7, 14, 15, 16, 17, 35, 126, 128 or 148 , e.g., providing an appropriate control system, control algorithm, battery power supply or other functionality. It is possible.

[0223] Additionally or alternatively, in some embodiments, communication module 124D is docked in the device dock 104 and connects to, for example, a bus or backplane operatively coupled to the device dock 104 via the The electronic circuitry within the device dock 104 communicates with any attached device. , the electronic circuitry within the monitoring client dock 102, and / or the monitoring client 1 and Optionally, the communication module 124D is docked in the device dock 104. Any device used, such as an infusion pump 7, a syringe pump 126, a pill dispenser, a dispenser 128 or a microinfusion pump 130, The communication module 124D also functions as a device dock. Note that the circuitry of 104 itself may be integrated into the circuitry.

[0224] Additionally or alternatively, in some embodiments, the communication module 124 Each of the devices may be connected to one or more wired power sources, such as a bus or backplane within the device dock 104. Each device can be replenished by a power source accessible through the plane 7, 14, 15, 16, 17, 35, 126, 148 are designed to provide sufficient power supply. As noted above, in some embodiments of the present disclosure, Module 124D provides sufficient power to devices 7, 126, 128, 130 and 133 Provided to.

[0225] As noted above, in some embodiments, each of the communication modules 124 may include a power circuits (e.g., , voltage converters, regulation circuits, rectification and filtering circuits, buck circuits, boost circuits, Buck-boost circuits, switch-mode power supplies, etc. In some cases, this power circuitry may be used to power a variety of different patient care devices 7, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 7, 35, 126, 128, 148 associated with various power supply characteristics (e.g., voltage level, maximum load / current requirements, and A / C frequency) Any number of power provision and management schemes are possible in light of this disclosure. This is what I mean.

[0226] Optionally, in other embodiments of the present disclosure, one or more battery cells, such as lithium-ion batteries, A power module 132 having on-board battery cells is attached to the device dock 104. to provide sufficient power for the entire treatment duration. Additionally or alternatively, the power module 132 may be If necessary, plug it into an outlet in the patient's room (typically shown as AC source in Figure 1). In this case, outlet power, if available, is used to power the dock. 104 and charges the battery contained within the power module 132. (This may occur simultaneously.) Outlet power is lost, or If not otherwise available, the power module 132 and / or the communication module The batteries in modules 124A, 124B, and 124C provide power to the docked devices. It is possible.

[0227] The exemplary system 100 may optionally include a dongle 133. The guru 133 may be docked in the device dock 104 shown in FIG. 1 or in another In this embodiment, the device dock 104 and / or the monitoring client 1 may be remotely The dongle 133 may provide communication for wireless devices that would not otherwise be available. It can provide links or protocols, e.g., new wireless protocols, technologies As technologies, standards, and techniques become available over time, the use of dongles133 It is used to provide a bridge, router or repeater between new communication protocols, allowing one processor to The information conveyed in one protocol can be converted into another protocol, thereby , new protocol devices, patient care devices 7, 14, 15, 17, 35, 12 6, 128, 130, device dock 104, communication module 124D, monitoring client 8, the monitoring dock 102, the monitoring client 1, the hub 802 of FIG. 8, and / or other devices. The dongle 133 can communicate with, for example, the monitoring server 3 or the monitoring client. Patient care devices in formats known or used by each other, such as Ant1 Chairs 7, 14, 15, 17, 35, 126, 128, 130, device dock 104, Communications module 124D, monitoring client dock 102, monitoring client 1, FIG. 8 The wireless protocol used by the hub 802 and / or any one or more of the other devices The data received from a new communication link using a protocol, technology, standard or technique. The dongle 133 can also act as a communication bridge between EVDO or may be provided for cellular-based communication links, such as CDMA-based cellular systems. do.

[0228] In some embodiments, the dongle 133 receives patient data from one or more patient-care devices. Communicating care parameters, such as patient treatment parameters or patient status parameters, 8 to the monitoring client 1, the hub 802 in FIG. 8, and / or the monitoring server 3. Optionally, in some embodiments, the dongle 13 3. May be equipped with a wired mounting connector, e.g., an RS-232 connector, for legacy a device that can connect to the legacy device and route communications from the legacy device to one or more other patient care providers; 8, the monitoring device, the monitoring client 1, the hub 802 and / or the monitoring server 3, etc. Legacy devices include, for example, legacy patient care devices, legacy computing devices, The device may be a device that uses a legacy wired communication protocol, or another device that uses a legacy wired communication protocol.

[0229] Optionally, the system 100 also includes various devices, docks, monitoring clients, and and / or a wearable system monitor 131 for monitoring the operation of the server. The monitoring client 1, the remote communicator 11, and / or the The hub 802 is used to program the wearable system monitor 131. It can interact with and / or pair with wearables. The system monitor 131 can be worn by the patient 2 or the provider and can The wearable system monitor 131 can be used. System Monitor 131 can query various devices to ensure proper operation. For example, in one exemplary embodiment, a wearable system monitor 1 31 refers to patient care devices 14, 15, 16, 17, 35, 126, 128, 130, and monitoring devices. monitoring client 1, monitoring client dock 102, device dock 104 and / or 8. Alternatively, the hub 802 in FIG. 8 may be contacted to check for any malfunction, error, fraud, data corruption, or communication degradation. , determine whether incomplete operation, slow operation or other problems exist.

[0230] Communications from the wearable system monitor 131 include one or more interrogation signals. to verify that the device being queried is functioning properly and within its prescribed operating parameters. whether the equipment is functioning properly and / or is otherwise in an undesirable state or condition The system monitor 131 can determine whether the monitoring server 3, the monitoring client 8. The hub 802 communicates the detected condition or fault to one or more devices, such as port 1 or hub 802 of FIG. to alert the provider, initiate shutdown procedures, and / or The device may initiate other appropriate therapeutic actions as directed by the inactive device, for example: The system monitor 131 monitors the client 1, the network and / or the internet. The monitoring server 3, other monitoring clients 4, and the network are connected via a WiFi router. 124 or other devices configured with the remote communicator 11. The transceiver of the communication module 124J is used to detect abnormal or Absence of a signal can signal a warning and / or alarm. and / or alarms will cause the device to audibly sound an alert and / or alarm. In some embodiments of the present disclosure, the system monitor The patient 131 is a call button to allow the patient 2 to request a care provider. (not explicitly shown), e.g., to allow requests to be made to the user who owns the device. The request may be sent to the monitoring client 1 or a remote community to be visually and / or audibly indicated. Routed to the controller 11.

[0231] The system monitor 131 may, for example, (1) predict a response to a query within a predetermined time period; (2) incrementing a counter within the device being queried and then (3) a challenge-response query; and / or (4) modify its functionality in various ways, including other system monitoring techniques or methods. It can be implemented.

[0232] As noted above, in some embodiments, the system monitor 131 After querying a patient-care device paired to the monitor, the For example, the system monitor 131 may predict the response to the A text string message of "Query" can be sent to the infusion pump 7. Now, infusion pump 7 displays a message labeled "System Monitor Query" Receives messages from the system monitor 131 and uses one or more processors in it to process them. When the infusion pump 7 processes a message, the software Ching executes the code to send a response message again to the system monitor 131, for example For example, the response message sent to the system monitor 131 is "System Monitor Response In this embodiment, the system monitor 131 can expect to receive a response message within a predetermined time, such as 2 seconds, and If the system monitor 131 does not receive a response message within two seconds, the system monitor The network controller 131 may send alerts and / or warnings to other devices (e.g., system monitors, Monitor 131 can broadcast a warning or fault message, or an alarm or The processor provides an audible or visual alert via the remote communicator 11. (It can be done).

[0233] As noted above, in some embodiments, the system monitor 131 receives a query. Increments a counter in the device it is connected to and requests the value of the counter from the device after it has been incremented. For example, the System Monitor 131 displays messages such as "increment counter" on the device. The request can be sent to a patient care device, such as an infusion pump 7, by sending the request to the The processor of the device receives the "increment counter" message and Reads a value from a memory location and increments the value found at that memory location, overwriting the previous value. Then, in this embodiment, the processor writes the new value to the same memory location. The server reads the new value from the memory location and sends the new value to the system monitor, e.g. If so, it will be transmitted via a radio transceiver on the device being queried. In this embodiment, the data processor 131 predicts a specific value from the device being queried (this The predicted values ​​may be stored in the system monitor's memory, for example in a table. For example, the system monitor 131 might see a value of 48 previously received from the device. It can be stored in its memory and the value can be updated in the device when queried. After requesting 49, expect to receive a value of 49 from the device.

[0234] Also, as mentioned above, the challenge-response method query is 31. For example, System Monitor 131 can be used to A message can be sent to a patient-care device, which then For example, you can use the encryption key to decrypt a message and send it to System Monitor 131. The system monitor 131 will be tasked with sending the data again. It is possible to predict that new messages will be returned within a predetermined time. If the system monitor 131 does not receive a response message within a predetermined time, the system monitor 131 to send alerts and / or warnings to other devices (e.g., system The monitor 131 may broadcast a warning or alarm message, and / or These are connected to the monitoring client 1, the monitoring server 3, the hub 802 in FIG. 8 or the remote communication The alarm or warning may then be visually or audibly indicated. ).

[0235] In the embodiment of the present disclosure, the monitoring client 1 is a handheld or portable remote communication device. (e.g., smartphones, tablet computers, PDAs, laptops) a laptop or other portable computing device) to This can be achieved by radio 12. This allows for accurate location of the patient within the facility, or the provider within or outside the facility. In one embodiment, communication can be maintained regardless of the patient's location. The information can be stored locally within the monitoring client 1, thereby providing a Healthcare providers have direct access to information without needing to access the monitoring server 3 It is possible.

[0236] In some embodiments, optionally with appropriate safety and security checks By incorporating a connected infusion pump 7 or patient monitoring device 14-17, 3 Changes to the settings or flow parameters of 5, 126, 128, 130, 148 are The provider's monitoring client 11 and the monitoring client 1 (via wire or wireless communication) The selected changes can also be made directly between the monitoring server 3 and any Communicate to other appropriate locations such as the nurse station 5 and / or pharmacy 6 at your option Additionally, any new instructions regarding Patient 2 can be sent to the instructing provider's remote The information is input into the communicator 11 (for example, a smartphone) and transmitted to the monitoring client 1. The patient can then communicate with the caregiver (e.g., a caregiver's own portable communicator 11) via the caregiver's own portable communicator 11. For example, a nurse, nurse practitioner, doctor, physician, or other healthcare professional ) Additionally or alternatively, in some embodiments, , new instructions for infusion pumps 7 or patient monitoring devices 14-17, 35, 126, 128 , 130, 148, and thereby, being in or coupled thereto The control system can then change its behavior, e.g., setpoint, in response to the new instructions. In some embodiments, any acquired and stored data in the monitoring client 1 can be The information is periodically uploaded to the monitoring server 3 and stored in a patient-specific database. Therefore, if Patient Monitoring Client 1 stops working, you can add a new device to the patient. 2 and can quickly repopulate with the patient's current information from the monitoring server 3 Orders, medications, progress notes, monitoring data, and treatment data from patient-attached devices The data, patient treatment parameters, patient monitoring parameters and / or operating parameters may also be permanently For permanent, temporary or transient storage and / or for predetermined criteria, e.g., ranges, thresholds Monitor the patient's condition from monitoring client 1 for analysis to ensure that the patient's condition is in accordance with the values, etc. The EHR 19, any applicable remote communicator 11, the hub 802 of FIG. 8, and / or can be uploaded to the monitoring server 3.

[0237] In some embodiments, the monitoring server 3 may communicate with several monitoring clients 1 in the facility 8. , 4, 11. The monitoring server 3 may provide the monitoring clients 1, 4, and 11 with the facility 8 and The present disclosure may provide data extracted from multiple databases, both on-site and off-site. In this embodiment, the monitoring server 3 may monitor the facility's EHR for targeted information regarding the patient 2. The system 19 is then queried and a predetermined set of information is sent to the patient monitoring client 1. information (e.g., patient age, height, weight, disease category, current medications and medication categories) , drug allergies and hypersensitivity, etc.). For example, if monitoring client 1 is assigned to patient 2, monitoring server 3 20, EHR, lab, radiology, pharmacy, and / or other systems within the facility. systems (e.g., cardiology23 or scheduling databases24) A communication link may be established. The unique patient identifier allows the monitoring server 3 to store patient-specific data. Obtain electronic access (permission) to receive from and transmit to these systems. A predetermined (selectable) subset of the data can be stored in the memory of the monitoring client 1. (not explicitly shown in FIG. 1).

[0238] The information thus obtained is then used to generate a key against which new instructions can be analyzed. It can act as a database. The instructions may be checked for compatibility with patient-specific information obtained by the monitoring server 3. Optionally, for safety reasons, commands entered remotely from the communicator 11 can be The indications can be intercepted by the monitoring server 3 and checked in the same way. The vision server 3 may also obtain information from a drug database located in the facility's pharmacy 22 or externally. , whether the new patient instructions may result in incompatibility with the patient's existing medications, for example; In an embodiment of the present disclosure, the monitoring server 3 can determine whether publicly available internet The device is programmed to access the internet site 25 and provide the patient with prescribed medication. Download new information about and alert your patient's healthcare provider(s) The monitoring server 3 can determine whether the event should be transmitted as a warning or an alarm 13. In addition, information is transmitted between the remote portable communicator 11 and the patient monitoring client 1. It can be routed.

[0239] In an embodiment of the present disclosure, the patient's physician, nurse, or pharmacist may provide new a patient monitoring client 1 to relay or receive instructions (e.g., medication instructions, etc.); The monitoring client 1 or server 3 can then have access to the new The nurse's portable communication device records the order and sends the request to the pharmacist and the patient's nurse. relayed via the necator 11 and / or via a fixed terminal at the nurse station 5 A customized communication application with the monitoring client 1 may be provided. "Smartphones" (e.g., Google's Nexus One phone, Apple Pull iPhone, or RIM's Blackberry OS) (office or remote Portable, convenient for providers who are not in a fixed location (such as a base station) Can act as a communicator 11. Tablet PC, netbook, or laptop Laptop computers also come with convenient pockets for both portable or fixed locations. 11. The PC can be fixed or desktop. It can serve as a convenient communication device 11 for locations where the provider can If the provider is in the monitoring client 1, the provider can use the keyboard or touch screen to Direct input through the device may be used to enter or receive information about patient 2.

[0240] The monitoring client 1 sends information about a specific assigned or designated patient 2. The monitoring client 1 can receive, process, and transmit the data. The monitor may communicate with any other device to which Patient 2 may be connected or associated. The optical fiber cable 104 is most conveniently attachable or dockable to the optical fiber cable 104 and the optical fiber cable 104. The monitoring client 1 may be, for example, approximately the size of a wireless phone or a tablet netbook. The monitoring client 1 may be a handheld device such as a It is convenient to have a touch screen interface to use. or wireless connection in the patient's room or at the nurse's station5 or can provide output to a larger fixed display in another convenient location. Each monitoring client 1 can communicate with the central monitoring server 3, through which the settings are EHR database 19, laboratory database 20, radiology database 21, pharmacy database Access patient data from the department database22 or other databases from various other facility departments. In some cases, the monitoring client 1 can access the monitoring server 3. via patient monitoring devices 14-17 or provider input into the patient's EHR 19 The monitoring clients 1 and 4 can also upload information received from the internet. The information is received from an external database through a monitoring server 3 with an internet connection 25. Therefore, various drug information databases dealing with adverse drug-related events can be used. A variety of external databases9 are accessible, including the National Security and Security Agency (NSA) networks.

[0241] The monitoring server 3 may, for example, help the monitoring client 1 to keep its contents as up-to-date as possible. The system may be arranged to manage various levels of external database information. This includes, for example, comparing and matching patient-related safety and drug information as it becomes available. This is achieved by prioritizing updates / downloads on the data transfer schedule. The monitoring clients 1 and 4 can also be used by health care professionals such as nurses, physicians, and pharmacists. directly or in conjunction with a portable communicator 11 used by the care provider. can communicate through the monitoring server 3. In some cases, these devices When used in a fixed location (e.g., a hospital pharmacy or nurse's station) ) may have a wired connection to the monitoring server 3. In other cases, the portable The nicator 11 may communicate with the computer and the device 11 via wired or wireless (e.g., Bluetooth) Use a secure internet connection via a TWS or WiFi (802.11) connection 13 (e.g. VPN-based internet connection, UPN, Https, private key Alternatively, the device may communicate with the monitoring server 3 through a mobile device (such as a smartphone). The handheld remote communicator 11 (such as a mobile phone or tablet / netbook) may communicate 12 directly with the facility monitoring client 1 via the telephone network; and / or the equipment is connected to a WiFi network (e.g., 2.4GHz to 2.4835GHz) Private cell networks, which may include unlicensed ISM bands, are also available. good.

[0242] In some embodiments, the communication link between the monitoring clients 1, 4 and the monitoring server 3 over an Ethernet network if widely available within the facility, or All patient-specific monitoring clients are available via wireless transmission using one of several standards. The clients 1, 4 can be linked to a central monitoring server 3. The server 3 can then The equipment server 8, the web-based server 25, and the healthcare provider Acting as a relay for communication with portable communicators 11 within and outside the facility In some embodiments, the wireless network can be configured to provide a system for transmitting patient information regardless of where the patient 2 is located within the facility. Regardless of whether the server is a server or not, it provides additional functionality that allows it to communicate with the monitoring server 3.

[0243] One way to provide wireless coverage to an entire facility is to provide the facility with access to a private mobile phone network. Licenses must be obtained. Provides a local communications network throughout the facility. One or more micro-cellular frequencies may be acquired or leased for the purpose of Such an arrangement allows patients and monitoring clients 1, 4 to be easily transported from one location to another within the facility. Maintain communication when moving, monitoring server 3, various in-hospital and out-of-hospital databases 8, 25 and fixed stations (e.g., in some embodiments, nurse stations) with users in the hospital (applications5 and pharmacies6) or as a monitoring client either inside or outside the hospital. Ant 11 (e.g., mobile smartphone, laptop, or tablet type) In some embodiments, this type of system can maintain a connection with the The system provides additional security via the permitted cellular infrastructure. Additionally, in some embodiments, the active wireless system may measure the strength of use within an area. It can monitor and direct additional channel frequencies to the area. In this embodiment, the bandwidth capacity of the network is such that it can accommodate large volumes of data, such as those containing radiological images. This bandwidth-intensive approach may not allow for efficient transmission of large data files. Data files can be communicated more efficiently over a wired connection.

[0244] Alternatively or additionally, hospitals may use internet or intranet-based communication systems. The communication system can implement 802.11 WiFi type protocols are used for wireless communication between the individual monitoring clients 1 and 4 and the monitoring server 3. To ensure proper signal reception throughout your body, place a broadband antenna It can be mounted on the roof of a building to collect mobile phone signals from local wireless telephone companies. The fiber optic or cable network then transmits the signal throughout the facility. Additionally or alternatively, the monitoring server 3 may distribute The private mobile phone networks described above can be used. Systems are typically capable of providing secure communications, e.g., to radiology databases. It is possible to efficiently communicate large files such as radiological images stored in the Home or office based users may use VPN or wired or optical Separate secure access using fiber cable or through DSL phone lines to the hospital server It uses data encryption to provide patient data security. In some applications, asymmetric It may be advantageous to implement a high-bandwidth communication network. Licensed mobile frequencies are used in the "upstream" direction from Client 1 to Monitoring Server 3, and the monitoring server Unlicensed 802.11 WiFi frequency in the "downstream" direction from Server 3 to Monitoring Client 1 In this example, the upstream bandwidth and data rate requirements are based on the downstream requirements. In low priority upstream transmission, the monitoring client 1 For example, ZigBee networks, Bluetooth networks, mesh networks It allows data to be sent through more decentralized and cost-effective networks such as To do so.

[0245] As noted above, various monitoring devices, such as patient-care devices 14, 15, 16, 17, and 35, The communication between the device and the monitoring client 1 is performed, for example, using a ZigBee wireless mesh network. cost-effective way using a network and / or Bluetooth network Exemplary monitoring devices include, among others, an ECG monitor 14, a blood pressure monitor 15, and a monitors 15, pulse oximeters / capnometers 16, thermometers and weight scales. A common feature of most of these devices is the periodic control of a single or a few parameters. Wireless mesh network and other in-hospital device communication The system provides low-power digital wireless connectivity between devices and is compatible with widely available licenses. Use of sense-free frequency bands (e.g., 2.4 GHz in some jurisdictions) High-level communication protocols, such as TCP and UDP, can be used to ensure data integrity. For example, a symmetric encryption key can be used to wofish, Serpent, AES(Rijndael), Blowfish, CA Generated for cryptographic algorithms such as ST5, RC4, 3DES, IDEA, etc. This allows for secure communication between the monitoring client and the patient-care device. In addition to or instead of, for example, CRC, odd parity bit check, or can use various data integrity techniques, such as even parity bit checking. Cut.

[0246] Mesh networks are highly scalable, connecting many devices into a single, self-forming, Allows for use on a self-healing mesh network. The connected devices can communicate with each other and act as repeaters to forward data. Mesh networks are relatively low-cost, scalable, and monitored. In some embodiments, the wireless mesh network The wireless range for linked devices is 70 meters from each node of the system within the facility. Patient monitoring clients 1 and 4 can be used to monitor healthcare. Providers have portable communicators and their assigned patients Similar networks may be used to provide wireless links within a facility between

[0247] In many cases, the information conveyed to the monitoring client 1 is a single parameter value (e.g., The monitoring client 1 can then determine whether the value is Determine if the value is outside the normal range, record the value in the patient's EHR, and The system can be programmed to notify the appropriate provider via the Internet 11. The network allows two-way communication, and the monitoring client 1 can connect to a patient monitoring device (e.g. If so, it queries the BP monitor 15) and instructs it to take an unscheduled reading. This can occur, for example, when an abnormal reading is received and its authenticity needs to be verified. This can be useful when there is a need to request repeated readings. In another embodiment, the monitoring cluster can be programmed to verify abnormal readings. Client 1 monitors the infusion pumps based on the readings received from monitoring devices 14-17. 7. The device may be programmed to interrupt or adjust flow rates, operating parameters, and / or treatment parameters. For example, if the BP monitor 15 indicates a blood pressure below a predetermined acceptable range, If so, the monitoring client 1 may request the infusion pump 7 to stop the infusion. Emergency notifications can be programmed and monitored by one or more healthcare providers. In another embodiment, the infusion pump 7 can communicate to the patient 2. The amount of fluid being delivered (e.g., the flow rate or cumulative amount of fluid pumped over a period of time) ), the processor in the monitoring client 1 determines the delivered The cumulative volume can be tracked to estimate the amount of fluid remaining in the medication bag 170. Alternatively, a processor within the monitoring client 1 or infusion pump 7 may determine the infusion rate and The amount delivered may be calculated from the elapsed time of injection.

[0248] When the estimated residual volume reaches a predetermined volume, the monitoring client 1 sends a signal to the infusion pump 7. The patient's IV access35 is then drained by sending a signal to reduce the flow rate. For example, monitoring client 1 may request a specific and determine that the patient is scheduled to return at the nurse's scheduled return time. Rather than warning you before it goes missing and / or sending you an alarm, Client 1 will be given a predetermined time from the nurse's arrival or scheduled return time. Signal the infusion pump 7 to slow the infusion rate so that the intravenous bag is emptied after a certain time. A notification to the nurse monitoring client recommending the refilling of the intravenous bag 17 may also be sent. You can send it to Ant 11.

[0249] In some embodiments, the progress of the operation of the patient-care device is monitored by the data of the monitoring client 1. the status and / or progress of the patient-care device, as indicated by the outer edge of the display. For example, the percentage of the perimeter that is lit up (e.g., as the perimeter fills in, forming a buried periphery) is achieved by a patient care device, e.g., an infusion pump 7. The outer edge is displayed on the monitor client 1 display to show the progress of the treatment. This outer edge is monitored by the infusion pump 7 in an image format (e.g., JPEG, BMP, etc.). may be sent to client 1 and / or to the monitoring client as a filled percentage value. In the latter case, the monitoring client 1 creates the outer perimeter.

[0250] In some embodiments, a GPS and / or ranging module (e.g., time-of-flight (Ultrasonic ranging module used for estimation), infusion pump 7, monitoring client 1, caregiver The predetermined settings may be configured on the infusion pump 7, the monitoring client, and / or the patient. 8, a predetermined group of caregivers and / or patients may be In this state, prior to initiating treatment and / or monitoring the infusion pump7 and / or monitoring client Requires that the two devices must be within a certain distance of each other before configuring one of the devices. You may request it.

[0251] In some embodiments, the patient-care devices 7, 170, 126, 128, 130, 1 4, 15, 16, 17, 124 or 148, Dock 102 or 104, Surveillance Client Hub 802 in FIG. 8 may be used to address the cause of an alarm (e.g., without disrupting the patient). A predetermined time has passed (to allow the caregiver to find a solution to remove the until the alarm is turned off on the device that is emitting the alarm and / or on the monitoring client 1. without soft alarms, hard alarms, and / or non-critical alarms If the cause of the alarm is removed before the predetermined time, the alarm may be transmitted to the remote communicator 11. If an alarm is detected, the alarming device and / or monitoring client1 will be alerted. This may not be necessary, thereby preventing additional confusion for the patient.

[0252] In some embodiments, the AC cable of FIG. 1 includes a clip, which The intravenous line can be clipped there.

[0253] In some embodiments, the infusion pump 7 includes LED lights that indicate one or more of the following: Check that: safety checks have been passed; the pump is pumping; there is a blockage; and / or The user can use the monitoring client 1 to check the status of the camera 144 or camera 136, and / or scanner 120) The barcode on the plug 170 can be read, and the LED on the plug will flash. to indicate to the user that the tubing connected to the intravenous bag 170 should be inserted therein. It is possible.

[0254] In some embodiments, the numbers as shown in FIG. 1 or as described herein are Each item, component, device, patient, and The elderly care device, dock, and computing device are optional. For example, in some implementations In the embodiment, the monitoring client 1 is optional, the monitoring server 3 is optional, and the Service 8 is optional, and services 19, 20, 21, 22, 23, and 24 are optional. The cloud server 25 is optional, and the other monitoring clients 4 are online drug databases9 are optional; and adverse drug event networks are optional. The network is optional, the patient's personal EHR is optional, and / or Alternatively, or in addition, the treatment outcome database 10 is optional. 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 and List Band 118, RFID 116, barcode 114, scanner 120, display 134 and / or the AC power source, respectively, may optionally be used in some embodiments of the present disclosure. be.

[0255] Additionally, in some embodiments, a cellular membrane such as that shown in FIG. 1 or described herein may be used. There are several items, components, numbered and unnumbered, such as The components, device, patient-care device, dock, and computing device are combined into a single item. , components, devices, patient care devices, docks or computing devices Although it is used for multiple items, components, devices, patient care devices, drives, For example, a single infusion pump 7 is shown in FIG. Although two infusion pumps 7 may be used in some embodiments. , multiple infusion pumps 7 can be used, or any arbitrary number of infusion pumps 7 Additionally or alternatively, in some embodiments, Multiple device docks 104 and / or multiple monitoring client docks 102 It can be used.

[0256] Additionally or alternatively, certain patient care devices 7, 14, 15, 16, 1 7, 126, 128, 130, 148 are shown, but the specific patient care device Other combinations, subsets, multiples, or combinations thereof may also be used. For example, in some embodiments, only the infusion pump 7 is used among the patient care devices. 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 enabled, may be powered down, or may not be part of the system 100 of FIG. Additionally or alternatively, in some specific embodiments, patient care devices used Only devices can be docked in the device dock 104. For example, in this particular implementation In this embodiment, the infusion pump 7 is the only device docked within the device dock 104. device dock 104 receives only one device, e.g., infusion pump 7. Additionally, alternatively, or optionally, in some particular embodiments, the patient Elderly care devices 7, 14, 15, 16, 17, 35, 126, 128, 130, 148 , dockable, capable of operating undocked, and / or docked may not be capable of being used and may operate as a stand-alone patient care device. can.

[0257] In some embodiments, the patient-care devices 7, 14, 15, 16, 17, 35, 12 6, 128, 130 and / or 148, 1 monitoring client, 1 remote communicator 1, and the docks 102 and / or 104 may communicate the safety data, e.g., via an API. A class may be provided.

[0258] Any of the functionality described with reference to FIG. 1 may be implemented in some embodiments in the hub 802 of FIG. It may also be performed by

[0259] FIG. 2 illustrates a monitoring client, such as the monitoring client of FIG. 1, in accordance with an embodiment of the present disclosure. 1 and one or more of the patient-care devices, e.g., patient-care devices 7, 14, 15, and 16 of FIG. , 17, 35, 126, 128, 130, 148 to maintain communication with one or more 1 shows a flow chart diagram illustrating the method 150 of the present embodiment. The method 150 of the present embodiment includes acts 152-153. 69. The monitoring client 1 may communicate with a paired and / or designated patient care An icon can be displayed to indicate when a monitoring client is established on the monitoring device. 1. The patient-care device is paired with and / or communicates with the designated patient-care device at predetermined intervals. can be checked to determine if they are available for pairing or designated patient If communication to the elderly care device is not available for a predetermined time, the monitoring client 1 An alarm or alert can be sounded.

[0260] Act 152 provides that the monitoring client dock is connected to the monitoring client through the dock connector. The device determines whether the device is available as a communication link between the device and the monitoring client dock. If the communication link of act 152 is available, method 150 proceeds to act 154; If not, the method 150 proceeds to act 156 .

[0261] Act 156 comprises the monitoring client dock communicating with the monitoring client through a wireless link. Act 15: Determine whether a communication link between the monitoring client and the dock is available. If six links are available, method 150 proceeds to act 154; otherwise, method Act 150 proceeds to Act 158.

[0262] Act 154 provides that the monitoring client dock is connected to the monitoring client Determine whether a communication link between the dock and the device dock is available. If the communication link 54 is available, the method 150 proceeds to act 160; otherwise, If so, method 150 proceeds to act 158. Act 160 continues with The communication link between the computer and the patient-care device may be, for example, a wireless or wired communication link. If the communication link is available in act 160, the method 150 proceeds to act 166, otherwise, method 150 proceeds to act 162. 2. The patient care device can be connected to the monitoring client via a direct wireless link. Determine whether a communication link between the dock and the device is available. If is available, the method proceeds to act 166; otherwise, the method 150 proceeds to act 1 Go to 64.

[0263] Act 158 ​​provides that the device dock communicates with the monitoring client and the device dock through a wireless link. The communication link of act 158 ​​is determined to be available for communication with the dock. If not, the method 150 proceeds to act 162; otherwise, the method 150 proceeds to act 163. Therefore, proceed to step 160.

[0264] Act 166 communicates the monitoring client and the patient-care device using an available communication link. In an alternative embodiment, a handshake is used For example, not all protocols use handshaking between communication endpoints. Decision act 168 determines whether the handshake of act 166 was successful. If act 168 determines that the handshake of act 166 was not successful, act 164 , determining that communication with the patient-care device is not available, and / or method 150 Attempts to establish communication using other links (not explicitly shown). For example, if decision act 168 determines that the handshake of act 166 was successful, then act 16 9 uses a sufficient number of communication links determined to be available by method 150 Communicate data.

[0265] The method 150 includes maintaining communication between a monitoring client and one or more patient-care devices. 1 is an exemplary embodiment of the present disclosure describing a method for Although the method 150 includes scheduling of communication links, other schedules may be used. It can use broadcast, anycast, multicast or unicast. Routing algorithms can be used, such as distance vector routing programs. can use link-state routing protocols. When optimized link-state routing protocols can be used, the path vector - Protocols can be used and static routing with alternate communication paths in place and / or adaptive networks can be used. In some embodiments of the present invention, a weight may be assigned to each communication path, A tra algorithm communicates between the monitoring client 1 and one or more patient care devices. The weights may be determined in any known manner, e.g., by bandwidth, signal quality, etc. , may be determined as a function of the bit error rate, available data throughput or It may be linear in latency, and / or the like.

[0266] Referring to the drawings, FIG. 3 illustrates two docks 102, 103 in accordance with another embodiment of the present disclosure. 3 shows a block diagram of an electronic patient care system 300 having a plurality of patient care devices 302 and 304 for wireless communication therebetween. System 300 is similar to system 100 of FIG. 1, but includes a monitoring client dock 1 Communication between the device dock 104 and the device 102 is via a wireless link. In some embodiments, the system 300 of FIG. 3 may be configured without the cable 110 of FIG. 1 in an inactive or non-operational state, and in addition or alternatively 3. Now, the system 300 of FIG. 3 includes docks 102 that are not connectable together using a cable. and 104.

[0267] Optionally, instructions or requests are transmitted to a patient-care device 7, 14, 15, 16, 17, 35 , 126, 128, 130, 148, for example, bolus volume, infusion flow rate, total the meter delivered fluid, the start time of drug delivery, the stop time of drug delivery, or the delivery flow rate profile Infusion pump 7, syringe pump 126 and / or microinfusion pump 1, other monitoring clients 4, and / or Alternatively, a remote communicator 11 may be used. For example, pill dispensing instructions for dispensing pills, pill types, pill dispensing schedules, and / or or a maximum pill dispensing criterion. To do this, one or more of monitoring clients 1, 4, 11 may be used. The criterion is the maximum amount of drug that can be delivered in a given time, e.g., a particular drug is taken as needed (i.e., when needed), but if taken in excess The drug may be unsafe, and maximum pill dispensing criteria, e.g., "a given amount in a given time" " This can prevent the drug from being taken by the patient in unsafe amounts.

[0268] In some embodiments, remote communicator 11 is used to communicate with remote communicator 1 Initiate two-way audio / visual communication (e.g., video call) between the Monitoring Client 1 and the Monitoring Client 1. Additionally or alternatively, the monitoring client 1 may be used to Two-way audio / visual communication between the monitoring client 1 and the monitoring client remote communicator 11. Communication can be initiated.

[0269] Optionally, patient-care devices 7, 14, 15, 16, 17, 35, 126, 128 , 130, 148 also determine whether an alarm or alert should be issued or transmitted. determine whether the treatment or condition is safe for the patient, and the system 300 Determine whether the client is operating properly or within predetermined boundaries and / or monitor the client. on the display of the client 1, other monitoring clients 4 and / or remote communicators 11. To display data on the monitor client 1, other monitor clients 4, and and / or reply to the remote communicator 11. For example, optionally: Infusion pump 7, syringe pump 126, and / or microinfusion pump The pump 130 measures the upstream pressure, the change in the upstream pressure, the downstream pressure relative to the patient 2, and the change in the downstream pressure relative to the patient 2. changes in downstream pressure due to the injection, the presence or absence of air in the infusion line, the actual bolus volume delivered, and the actual infusion rate, actual total fluid delivered, actual start time of drug delivery, actual time of drug delivery The stop time or actual delivery flow rate profile can be monitored by monitoring client 1, other monitoring clients, 4, and / or one or more of the remote communicators 11 (if applicable). In another embodiment, the pill dispenser 128 may optionally include, for example, Actual pill dispensed, actual pill type dispensed, actual pill dispensed at time of dispense Monitor clients to see data such as schedules or whether maximum pill dispensing criteria have been exceeded. 1, other monitoring clients 4, and / or remote communicators 11. This can be done.

[0270] Patient care devices 7, 14, 15, 16, 17, 35, 126, 128, 130, 14 The data received from 8 may be used in any predetermined manner to generate alarms and / or alerts. For example, one or more of monitoring clients 1, 4, and 11 can be analyzed for status. Infusion pump 7, syringe pump 126 and / or microinfusion pump Increased pressure downstream of the pump 130 may be used to prevent excessive clotting, seepage, blockage or obstruction of the tubing to the patient. This may be one indication of kinking or other obstruction by material within the IV bag 170. In response to a sudden increase in downstream pressure, monitoring clients 1, 4, 11. One or more of the following may provide a visual or audible warning or alert to the user: Additionally or alternatively, a sudden drop in downstream pressure to the patient 2 may This is an indication that the tube has come off the needle and / or the needle is now out of the patient. In response, one or more of the monitoring clients 1, 4, 11 may provide a visual or audible notification to the user. One or more of the monitoring clients 1, 4, and 11 may Optionally, the flow is adjusted in response to sudden increases and / or decreases in downstream pressure to the patient 2. To stop delivery of the body fluids, turn off the infusion pump 7, syringe pump 126, and / or the machine. The instructions may be sent to one or more of the microinfusion pumps 130.

[0271] In some embodiments, the numbers as shown in FIG. 3 or as described herein are Each item, component, device, patient, and The elderly care device, dock, and computing device are optional. For example, in some implementations In the embodiment, the monitoring client 1 is optional, the monitoring server 3 is optional, and the Service 8 is optional, and services 19, 20, 21, 22, 23, and 24 are optional. The cloud server 25 is optional, and the other monitoring clients 4 are online drug databases9 are optional; and adverse drug event networks are optional. The network is optional, the patient's personal EHR is optional, and / or Alternatively, or in addition, the treatment outcome database 10 is optional. 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 and List Band 118, RFID 116, barcode 114, scanner 120, display 134, and / or the AC power source, each of which may be optional in some embodiments of the present disclosure. is.

[0272] Additionally, in some embodiments, a method for manufacturing a semiconductor device, such as that shown in FIG. 3 or described herein, may be used. There are several items, components, numbered and unnumbered, such as components, devices, patient-care devices, docks, and computing devices are integrated into a single item. system, component, device, patient care device, dock or computing device. Although multiple items, components, devices, patient care devices, A dock and computing device are contemplated. For example, a single infusion pump 7 is shown in FIG. Although shown, in some embodiments, two infusion pumps 7 may be used. , multiple infusion pumps 7 can be used, or any arbitrary number of infusion pumps 7 can be used. Additionally or alternatively, in some embodiments, multiple Multiple device docks 104 and / or multiple monitoring client docks 102 may be used. It can be used.

[0273] Additionally or alternatively, certain patient care devices 7, 14, 15, 16, 1 7, 126, 128, 130, 148 are shown, but the specific patient care device Other combinations, subsets, multiples, or combinations thereof may also be used. For example, in some embodiments, only the infusion pump 7 is used among the patient care devices. 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 running, may be powered down, or may not be part of the system 300 of FIG. Additionally or alternatively, in some embodiments, the only patient-care device used can be docked to the device dock 104. For example, in one particular embodiment, The infusion pump 7 is the only device docked in the device dock 104. The vice dock 104 receives only one device, for example, the infusion pump 7. Alternatively, or optionally, in some specific embodiments, the patient-care device 7, 14, 15, 16, 17, 35, 126, 128, 130, 148 are docking It can operate undocked and / or be dockable. It can operate as a stand-alone patient-care device without requiring a separate device.

[0274] In FIG. 3, the device dock 104 is capable of receiving several patient-care devices. Although shown as such, in other embodiments, the device dock 104 may be A single patient-care device, multiple patient-care devices, or any arbitrary number of patient-care devices Also, the dock section may not be in use, even if For example, as shown in FIG. 3, an empty compartment 170 is shown in the device dock 104. In addition, the monitoring client dock 102 can receive one monitoring client 1. Although shown to be possible, in other embodiments, the monitoring client dock The network 102 may be configured with two monitoring clients 1, three or more monitoring clients 1, or any Any number of monitoring clients 1 can be accommodated.

[0275] FIG. 4 illustrates a monitoring client, e.g., monitoring client 1, and a device according to an embodiment of the present disclosure. one or more of the patient-care devices, e.g., patient-care devices 7, 14, 15, 16, 17, and 35 of FIG. 126, 128, 130, 148. A flowchart showing the process is shown.

[0276] Act 204 provides a method for a monitoring client dock to connect a monitoring client to a dock connector through the dock connector. Determine whether the device is available as a communications link between the device and the monitoring client dock. If the communication link at 204 is available, the method 202 proceeds to act 206; otherwise, If so, the method 202 proceeds to act 208. Act 208 includes The link serves as a communication link between the monitoring client and the monitoring client dock. If the communication link of act 208 is available, method 202 continues with If so, the method 202 proceeds to act 206; otherwise, the method 202 proceeds to act 210.

[0277] Act 206 comprises a step of: transmitting the monitoring client dock to the monitoring client dock via a wireless link; Act 20 determines whether the device dock is available as a communication link between the device dock and the device dock. If six communication links are available, the method 202 proceeds to act 212; otherwise, , the method 202 proceeds to act 210.

[0278] Act 210 is a process for connecting the device dock to the monitoring client and the device dock via a wireless link. The communication link in act 210 is determined to be available for communication with the dock. If so, the method 202 proceeds to act 212; otherwise, the method 202 proceeds to act 212. Therefore, proceed to step 214.

[0279] Act 212 comprises a step of: causing the device dock to communicate between the device dock and the patient-care device; If the communication link of act 212 is available, determine whether it is available as a link. , the method 202 proceeds to act 216; otherwise, the method 202 proceeds to act 214.

[0280] Act 214 includes communicating with the patient-care device via a direct wireless link to the monitoring client. The communication link of act 214 is used to determine whether the communication link is available to the protection device. If the link is available, the method 202 proceeds to act 216; otherwise, the method 202 proceeds to act 218. determines that communication with the patient-care device is not available.

[0281] Act 216 communicates with the monitoring client using the available communication link(s). Attempt a handshake between the patient-care devices. In an alternative embodiment, the handshake No attempt has been made, for example some communication protocols do not utilize handshaking. The determining act 220 determines whether the handshake was successful and whether the monitoring client and device If act 220 determines that a communication link is established, The method 202 uses the available communication link(s) to communicate with the monitoring client during act 222. A decision act 220 determines whether the handshake is successful. If it is determined that communication with the device was not successful, the method 202 continues at act 218. The method 202 determines that the communication link is unavailable or is not verified (explicit The monitoring client attempts to communicate with the monitoring client through a network (not shown).

[0282] The method 202 includes maintaining communication between a monitoring client and one or more patient-care devices. 1 is an exemplary embodiment of the present disclosure, describing a method for 02 includes a schedule for communication links, but other schedules can be used. It can use anycast, multicast or unicast and is distance vector routing protocols that can use routing algorithms You can use a link-state routing protocol, Optimized link-state routing protocols can be used, and path vector protocols protocols and use static routing with alternate communication paths in place. and / or may use adaptive networks. In some embodiments, a weight may be assigned to each communication path, an algorithm for communicating between the monitoring client 1 and one or more patient care devices; The weights may be used in any known manner, e.g., based on bandwidth, signal quality, bit rate, etc. The available data throughput or latency may be determined as a function of the data error rate. It may be linear in between, and / or the like.

[0283] Referring now to FIG. 5, a monitoring client 1 and a and various patient-care devices (e.g., patient-care devices 7, 126, 128, or 13 0) together, a dock 502, a communication module 124D, and a dock An electronic patient care system 500 is shown in block diagram form having a group 133. The electronic patient care system 500 is similar to the electronic patient care system 100 of FIG. Vision client 1, patient care devices 7, 126, 128, 130, communication module 12 4D, and each of the dongles 133 are all dockable in the dock 502. As will be appreciated in light of this disclosure, the dock 502 may include one or more It may comprise a bus, a backplane, a communication path, an electronic circuit, or the like.

[0284] Optionally, instructions or requests are transmitted to a patient-care device 7, 14, 15, 16, 17, 35 , 126, 128, 130, 148, for example, bolus volume, infusion flow rate, total the meter delivered fluid, the start time of drug delivery, the stop time of drug delivery, or the delivery flow rate profile Infusion pump 7, syringe pump 126 and / or microinfusion pump 1, other monitoring clients 4, and / or Alternatively, a remote communicator 11 may be used. For example, pill dispensing instructions for dispensing pills, pill types, pill dispensing schedules, and / or or a maximum pill dispensing criterion. To do this, one or more of monitoring clients 1, 4, 11 may be used. The criterion is the maximum amount of drug that can be delivered in a given time, e.g., a particular drug is taken as needed (i.e., when needed), but if taken in excess The drug may be unsafe, and maximum pill dispensing criteria, e.g., "a given amount in a given time" " This can prevent the drug from being taken by the patient in unsafe amounts.

[0285] Optionally, patient-care devices 7, 14, 15, 16, 17, 35, 126, 128 , 130, 148 also determine whether an alarm or alert should be issued or transmitted. determine whether the treatment or condition is safe for the patient, and the system 500 Determine whether the client is operating properly or within predetermined boundaries and / or monitor the client. on the display of the client 1, other monitoring clients 4 and / or remote communicators 11. To display data on the monitor client 1, other monitor clients 4, and and / or reply to the remote communicator 11. For example, optionally: Infusion pump 7, syringe pump 126, and / or microinfusion pump The pump 130 measures the upstream pressure, the change in the upstream pressure, the downstream pressure relative to the patient 2, and the change in the downstream pressure relative to the patient 2. changes in downstream pressure due to the injection, the presence or absence of air in the infusion line, the actual bolus volume delivered, and the actual infusion rate, actual total fluid delivered, actual start time of drug delivery, actual time of drug delivery The stop time or actual delivery flow rate profile can be monitored by monitoring client 1, other monitoring clients, 4, and / or one or more of the remote communicators 11 (if applicable). In another embodiment, the pill dispenser 128 may optionally include, for example, Actual pill dispensed, actual pill type dispensed, actual pill dispensed at time of dispense Monitor clients to see data such as schedules or whether maximum pill dispensing criteria have been exceeded. 1, other monitoring clients 4, and / or remote communicators 11. This can be done.

[0286] Patient care devices 7, 14, 15, 16, 17, 35, 126, 128, 130, 14 The data received from 8 may be used in any predetermined manner to generate alarms and / or alerts. For example, one or more of monitoring clients 1, 4, and 11 can be analyzed for status. Infusion pump 7, syringe pump 126 and / or microinfusion pump Increased pressure downstream of the pump 130 may be used to prevent excessive clotting, seepage, blockage or obstruction of the tubing to the patient. This may be one indication of kinking or obstruction by other material within the IV bag 170. In response to a sudden increase in downstream pressure, monitoring clients 1, 4, 11. One or more of the following may provide a visual or audible warning or alert to the user: Additionally or alternatively, a sudden drop in downstream pressure to the patient 2 may This is an indication that the tube has come off the needle and / or the needle is now out of the patient. In response, one or more of the monitoring clients 1, 4, 11 may provide a visual or audible notification to the user. One or more of the monitoring clients 1, 4, and 11 may Optionally, the flow is adjusted in response to a sudden increase and / or decrease in downstream pressure to the patient 2. To stop delivery of the body fluids, turn off the infusion pump 7, syringe pump 126, and / or the machine. The instructions may be sent to one or more of the microinfusion pumps 130.

[0287] In some embodiments, the numbers, as shown in FIG. 5 or as described herein, Each item, component, device, patient, and The elderly care device, dock, and computing device are optional. For example, in some implementations In the embodiment, the monitoring client 1 is optional, the monitoring server 3 is optional, and the Service 8 is optional, and services 19, 20, 21, 22, 23, and 24 are optional. The cloud server 25 is optional, and the other monitoring clients 4 are online drug databases9 are optional; and adverse drug event networks are optional. The network is optional, the patient's personal EHR is optional, and / or Alternatively, or in addition, the treatment outcome database 10 is optional. 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 and List Band 118, RFID 116, barcode 114, scanner 120, display 134, and / or the AC power source, each of which may be optional in some embodiments of the present disclosure. is.

[0288] Additionally, in some embodiments, a method such as that shown in FIG. 5 or described herein may be used. There are several items, components, numbered and unnumbered, such as components, devices, patient-care devices, docks, and computing devices are integrated into a single item. system, component, device, patient care device, dock or computing device. Although multiple items, components, devices, patient care devices, A dock and computing device are contemplated. For example, a single infusion pump 7 is shown in FIG. Although shown, in some embodiments, two infusion pumps 7 may be used. , multiple infusion pumps 7 can be used, or any arbitrary number of infusion pumps 7 can be used. Additionally or alternatively, in some embodiments, multiple A number of docks 502 can be used.

[0289] Additionally or alternatively, certain patient care devices 7, 14, 15, 16, 1 7, 126, 128, 130, 148 are shown, but the specific patient care device Other combinations, subsets, multiples, or combinations thereof may also be used. For example, in some embodiments, only the infusion pump 7 is used among the patient care devices. 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 running, may be powered down, or may not be part of the system 500 of FIG. Additionally or alternatively, in some specific embodiments, the patient-care device used Only implants can be docked to the dock 502. For example, in one particular embodiment, The pump 7 is the only device docked in the device dock 502, and the device The dock 502 receives only one device, for example, the infusion pump 7. Alternatively, or optionally, in some specific embodiments, the patient-care device 7 , 14, 15, 16, 17, 35, 126, 128, 130, 148 are dockable and can operate undocked and / or not dockable , and can operate as a stand-alone patient care device.

[0290] In FIG. 5, dock 502 is shown as being capable of receiving several patient-care devices. Although shown in FIG. 1, in other embodiments, the dock 502 may accommodate one patient-care device. , multiple patient-care devices, or any arbitrary number of patient-care devices. Also, a section of the dock may be unused, e.g., as shown in Figure 5. , an empty compartment 170 is shown in the dock 502. In addition, the dock 502 has one Although the monitoring client 1 is shown as being capable of receiving the In some embodiments, the dock 502 may support two monitoring clients 1, three or more monitoring clients 1, , or any arbitrary number of monitoring clients 1.

[0291] FIG. 6 illustrates a monitoring client, such as the monitoring client of FIG. 5, in accordance with an embodiment of the present disclosure. 1 and one or more patient-care devices, such as patient-care devices 7, 14, 15, and 16 of FIG. , 17, 35, 126, 128, 130, 148 to maintain communication with one or more 3 is a flow chart diagram illustrating the method 304 of FIG.

[0292] The method further comprises, during act 306, connecting the dock to the monitoring client through the dock connector. The communication link of act 306 is determined to be available as a communication link between the network and the network. If not, the method 304 proceeds to act 308; otherwise, the method 304 proceeds to act 309. Act 310 continues with the dock as a communication link between the dock and the patient-care device. If the communication link of act 310 is not available, method 304 If so, the method 304 proceeds to act 312; otherwise, the method 304 proceeds to act 314.

[0293] Act 308 involves the dock connecting the communication link between the monitoring client and the dock over a wireless link. If the communication link in act 308 is not available, The method 304 proceeds to act 310; otherwise, the method 304 proceeds to act 312.

[0294] Act 312 includes communicating with the patient-care device via a direct wireless link to the monitoring client. The communication link of act 312 is used to determine whether the communication link is available to the protection device. If the network is not available, act 316 establishes a connection between the monitoring client and the patient-care device. Determine that communication is not available.

[0295] Act 314 communicates with the monitoring client using the available communication link(s). In an alternative embodiment, a handshake is not utilized. For example, some protocols do not utilize handshaking. , determine whether the handshake was successful, and if so, the method 304 continues with act 320 and communicates the data using the available communication link(s). If act 318 determines that the handshake was not successful in act 314, act 316 In another embodiment, determining act 318 determines that communication with the device is not available. If the handshake is determined not to be successful in act 314, the method 304 communicating with patient-care devices via communications links (not explicitly shown) not provided by the Try to.

[0296] The method 304 includes maintaining communication between the monitoring client and one or more patient-care devices. 1 is an exemplary embodiment of the present disclosure, which describes a method for Although 04 contains a schedule of communication links, other schedules may be used. It can use broadcast, anycast, multicast or unicast. Routing algorithms can be used, such as distance vector routing programs. can use link-state routing protocols. When optimized link-state routing protocols can be used, the path vector - Protocols can be used and static routing with alternate communication paths in place and / or adaptive networks can be used. In some embodiments of the present invention, a weight may be assigned to each communication path, A tra algorithm communicates between the monitoring client 1 and one or more patient care devices. The weights may be determined in any known manner, e.g., by bandwidth, signal quality, etc. , may be determined as a function of the bit error rate, available data throughput or It may be linear in latency, and / or the like.

[0297] Referring now to FIG. 7, a patient-care device 7, 1 according to yet another embodiment of the present disclosure. 26, 128, 130 to dock therein. 7 shows a block diagram of an electronic patient care system 700 having a client 1. In addition, In some embodiments, the communication module 124D and the dongle 133 all The patient care system 700 of FIG. Similar to patient care system 100, but with an integrated dock 702. In some embodiments, the monitoring client 1 is docked via a dock. When the monitoring client 1 is connected to the patient-care device, the monitoring client 1 communicates with the patient-care device. For example, patient care devices 7, 14, 15, 16, 17, 35, 126, 128, 130, If the monitoring client 1 cannot communicate with the monitoring client 148, the monitoring client 1 may communicate with the monitoring client 148 wirelessly, for example. Antenna 112 of Ant 1 can be used for communication.

[0298] Optionally, instructions or requests are transmitted to a patient-care device 7, 14, 15, 16, 17, 35 , 126, 128, 130, 148, for example, bolus volume, infusion flow rate, total the meter delivered fluid, the start time of drug delivery, the stop time of drug delivery, or the delivery flow rate profile Infusion pump 7, syringe pump 126 and / or microinfusion pump 1, other monitoring clients 4, and / or Alternatively, a remote communicator 11 may be used. For example, pill dispensing instructions for dispensing pills, pill types, pill dispensing schedules, and / or or a maximum pill dispensing criterion. To do this, one or more of monitoring clients 1, 4, 11 may be used. The criterion is the maximum amount of drug that can be delivered in a given time, e.g., a particular drug is taken as needed (i.e., when needed), but if taken in excess The drug may be unsafe, and maximum pill dispensing criteria, e.g., "a given amount in a given time" " This can prevent the drug from being taken by the patient in unsafe amounts.

[0299] Optionally, patient-care devices 7, 14, 15, 16, 17, 35, 126, 128 , 130, 148 also determine whether an alarm or alert should be issued or transmitted. determining whether a treatment or condition is safe for a patient, system 70 Determine if the system is operating properly or within predetermined boundaries and / or monitor the system. the display of the client 1, other monitoring clients 4 and / or remote communicators 11. To display data on the screen, monitor the data on client 1, and then monitor the other client. 4, and / or the remote communicator 11. For example, the optional Injection pump 7, syringe pump 126, and / or microinfusion pump The pump 130 measures the upstream pressure, the change in the upstream pressure, the downstream pressure relative to the patient 2, and the patient pressure. Changes in downstream pressure relative to 2, presence or absence of air in the infusion line, and actual bolus volume delivered , actual infusion flow rate, actual total fluid delivered, actual start time of drug delivery, time of drug delivery The actual stop time or actual delivery flow rate profile can be monitored by client 1, other monitoring Client 4, and / or one or more of Remote Communicators 11 (if applicable) In another embodiment, the pill dispenser 128 can optionally , e.g., actual pill dispensed, actual pill type dispensed, actual pill at time of dispense Data such as medication dispensing schedules or whether maximum pill dispensing criteria have been exceeded can be collected from the monitoring replies to the client 1, other monitoring clients 4, and / or remote communicators 11. It is possible.

[0300] Patient care devices 7, 14, 15, 16, 17, 35, 126, 128, 130, 14 The data received from 8 may be used in any predetermined manner to generate alarms and / or alerts. For example, one or more of monitoring clients 1, 4, and 11 can be analyzed for status. Infusion pump 7, syringe pump 126 and / or microinfusion pump Increased pressure downstream of the pump 130 may be used to prevent excessive clotting, seepage, blockage or obstruction of the tubing to the patient. This may be one indication of kinking or obstruction by other material within the IV bag 170. In response to a sudden increase in downstream pressure, monitoring clients 1, 4, 11. One or more of the following may provide a visual or audible warning or alert to the user: Additionally or alternatively, a sudden drop in downstream pressure to the patient 2 may This is an indication that the tube has come off the needle and / or the needle is now out of the patient. In response, one or more of the monitoring clients 1, 4, 11 may provide a visual or audible notification to the user. One or more of the monitoring clients 1, 4, and 11 may Optionally, the flow is adjusted in response to sudden increases and / or decreases in downstream pressure to the patient 2. To stop delivery of the body fluids, turn off the infusion pump 7, syringe pump 126, and / or the machine. The instructions may be sent to one or more of the microinfusion pumps 130.

[0301] In some embodiments, the numbers are as shown in FIG. 7 or as described herein. Each item, component, device, patient, and The elderly care device, dock, and computing device are optional. For example, in some implementations In the embodiment, the monitoring client 1 is optional, the monitoring server 3 is optional, and the Service 8 is optional, and services 19, 20, 21, 22, 23, and 24 are optional. The cloud server 25 is optional, and the other monitoring clients 4 are online drug databases9 are optional; and adverse drug event networks are optional. The network is optional, the patient's personal EHR is optional, and / or Alternatively, or in addition, the treatment outcome database 10 is optional. 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 and List Band 118, RFID 116, barcode 114, scanner 120, display 134, and / or the AC power source, each of which may be optional in some embodiments of the present disclosure. is.

[0302] Additionally, in some embodiments, a method such as that shown in FIG. 7 or described herein may be used. There are several items, components, numbered and unnumbered, such as components, devices, patient-care devices, docks, and computing devices are integrated into a single item. system, component, device, patient care device, dock or computing device. Although multiple items, components, devices, patient care devices, A single infusion pump 7 is shown in FIG. Although shown, in some embodiments, two infusion pumps 7 may be used. , multiple infusion pumps 7 can be used, or any arbitrary number of infusion pumps 7 can be used. Additionally or alternatively, in some embodiments, one A body dock 702 can be used.

[0303] Additionally or alternatively, certain patient care devices 7, 14, 15, 16, 1 7, 126, 128, 130, 148 are shown, but the specific patient care device Other combinations, subsets, multiples, or combinations thereof may also be used. For example, in some embodiments, only the infusion pump 7 is used among the patient care devices. 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 running, may be powered down, or may not be part of the system 700 of FIG. Additionally or alternatively, in some specific embodiments, the patient-care device used Only the integrated dock 702 can be docked. For example, in one particular embodiment, , the infusion pump 7 is the only device docked within the integrated dock 702, The mold dock 702 only receives one device, for example, an infusion pump 7. Alternatively, or optionally, in some particular embodiments, a patient-care device 7, 14, 15, 16, 17, 35, 126, 128, 130, 148 are dockable. Yes, it can operate undocked and / or is not dockable, It can operate as a stand-alone patient-care device.

[0304] In FIG. 7, an integrated dock 702 is capable of receiving several patient-care devices. Although shown as such, in other embodiments, the integrated dock 702 may be configured to accommodate a single patient. a patient-care device, a plurality of patient-care devices, or any number of patient-care devices Also, there may be unused sections of the dock, e.g., Figure 7 As shown in Figure 1, an empty compartment 170 is shown in 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 may include two integrated monitoring 1 client, 3 or more integrated monitoring clients, or any number of integrated A monitoring client 1 can be received.

[0305] FIG. 8 illustrates an electronic patient-care system having a hub 802 according to yet another embodiment of the present disclosure. 8 is a block diagram of a hub 800. Optionally, in some embodiments, the hub 802 A communication interface is provided between the monitoring client dock 102 and the device docks 804, 806. In yet additional embodiments, the hub 802 provides a monitoring client 1 , other monitoring clients 4, and / or remote communicators 11, without For example, the hub 802 may control a monitoring server 3, a facility service 8, a nurse service Station 5, pharmacy 6, cloud server 25, online drug database or drug Adverse Event Network, patient's personal EHR and / or treatment outcomes data The hub 802 can communicate with all devices ( For example, patient-care devices, monitoring clients, remote communicators, etc.) are connected to the hub 802. the real-time device uses the clock of the hub 802, or Provide a clock so that time-critical devices use the clock of the hub 802. It can be provided.

[0306] In some embodiments, a GPS and / or ranging module (e.g., ultrasonic ranging) module), infusion pump 830, monitoring client 1, hub 802, caregiver and / or The predetermined settings can be configured on the infusion pump 830, the monitoring client, or the patient. A predetermined group of participants, Hub 802, caregivers and / or patients, in this particular embodiment, , before starting treatment, and / or infusion pump 830, hub 802, and / or Before configuring one of the monitoring clients 1, they must be within a certain distance of each other. and may be required.

[0307] In some embodiments, the hub 802 may include an application programming interface. It has an API (Application Programming Interface) that allows monitoring clients1 and / or remote communication The GUI, windows, data, etc. are displayed on the data. The API is a secure data In yet additional embodiments, the dock 102, 804, and and / or 806, which has an API, a monitoring client 1, or a remote communicator 11 to display GUIs, windows, data, etc. The block 102, 804, or 806, or the hub 802, may be equipped with an API to communicate with the patient care device. GUI, windows, data, etc. on the devices 830, 810, and / or 814 Display.

[0308] In some embodiments, the hub 802 and / or the docks 102, 804, and / or or 806, associated patient-care devices (paired devices thereto, plugged into the hub 802 and / or docks 102, 804, and / or 806 or docked device) associated with it. The type of device can be identified and configuration data can be loaded.

[0309] In some embodiments, the hub 802 and / or the docks 102, 804, and / or or 806, identifying the type of patient-care device associated therewith, You can configure the UI using CSS, JavaScript, etc. In an embodiment, the hub 802 and / or the docks 102, 804, and / or 806 may have a distributed UI system.

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

[0311] Optionally, in some particular embodiments, the hub 802 may be connected to a monitoring client 1 and It contains all the safety-critical circuits and software to communicate. For example, in this particular embodiment, the hub 802 receives treatment parameters from the monitoring client 1. The hub 802 receives the message and some security information is sent to the monitoring client 1. Independent of the inspection, ensure that the treatment parameters are safe for Patient 2. In certain additional embodiments, the system 800 may optionally include a full It is fault-tolerant, for example, independent safety measures taken by monitoring client 1. All checks fail to meet a predetermined standard, e.g., a predetermined safety margin for drug delivery of the infusion pump 7. In this case, the instruction, request or parameter from the monitoring client 1 can be ignored. .

[0312] Optionally, in further specific embodiments, a catheter attached to the intravenous bag 170 may be provided. The barcode can be scanned by the scanner 120, which is the barcode for the given prescription. (e.g., from the patient's personal EHR) and / or inject The pump 830 is connected to the hub 802 when the hub 802 is docked to the dock 804. The uploaded prescription is then stored in the database. Optionally, hub 802 may initiate an infusion of intravenous bag 170 to patient 2 and monitor the progress of the treatment. In addition, alternatively, or optionally, this In certain embodiments, the caregiver may access the system 80 only through the hub 802, as shown in FIG. 0. Optionally, in some embodiments, the hub 802 , treatment, status, or patient information to the monitoring client 1. For example, the hub 802 receives treatment information from the infusion pump 830 or the skin on the intravenous bag 170. The medical information received from the patient's personal EHR19' corresponding to the scanned barcode is Upload it to the monitoring client 1 and display it to the user, who then confirms the information. The information can be recognized and stored in the monitoring client 1.

[0313] In some embodiments, the device dock 804 includes the infusion pumps 830, 810 and and 812. In some embodiments, the device dock 804 may include one, two, or Device Dock 806 can accommodate more than one patient care device. In some embodiments, the device dock 806 receives a pill dispenser 814. The device 802 may receive one, more than one, or multiple patient-care devices, such as a dispenser 806 . The device dock 804 includes an antenna 816 for wireless communication. Hub 806 includes an antenna 818 for wireless communication. Additionally or alternatively, the device may be equipped with a trusted antenna 820. The network 804, the hub 802 and / or the monitoring client 1 may be connected to each other using a wired connection. The hub 802 and the docks 804 and 806 each communicate with, for example, a USB Using a cable, using an Ethernet cable, and / or a wireless link Optionally, the hub 802 can communicate with the display 82. 2, camera 824, microphone 826, scanner 120, detachable display (Fig. As noted above, the hub 802 may include all Patient safety-critical functions can be provided by the monitoring client 1 and and / or may operate independently of the monitoring client dock 102.

[0314] Optionally, instructions or requests may be transmitted to a patient-care device 14, 15, 16, 17, 35, 8 30, 810, 812, 814, 148, e.g., bolus volume, infusion flow rate , total fluid delivered, start time of drug delivery, stop time of drug delivery, or delivery flow rate profile. The monitoring client may be configured to transmit the file to one or more of the infusion pumps 830, 810, 812. 1, other monitoring clients 4, and / or remote communicators 11. In some embodiments, for example, pill dispensing instructions for dispensing pills, Instructions or requests, such as type, pill dispensing schedule and / or maximum pill dispensing criteria one or more of monitoring clients 1, 4, 11 to send the The maximum pill dispensing criterion is the number of pills that can be delivered in a given time. The maximum amount of a drug, e.g., that a particular drug can be taken on an as-needed basis (i.e., when needed). However, the drug may be unsafe if taken in excess, and the maximum pill dispensing ratio The standard is, for example, "a specified amount within a specified time," so that the drug is not administered in an unsafe amount by the patient. It can prevent ingestion.

[0315] Optionally, patient-care devices 14, 15, 16, 17, 35, 830, 810, 8 12, 814, 148 also determine whether an alarm or alert should be issued or transmitted. determining whether a treatment or condition is safe for a patient; Determining and / or monitoring whether the 00 is operating properly or within predetermined boundaries Client 1, other monitoring clients 4 and / or remote communicators 11 To display data on the display, the data is sent to monitoring client 1 and other monitoring clients. The message may be sent back to the remote communicator 4 and / or the remote communicator 11. For example, One or more of the infusion pumps 830, 810, 812 may be configured to measure upstream pressure, changes in upstream pressure, Downstream pressure to Patient 2, change in downstream pressure to Patient 2, presence of air in the infusion line None, Actual bolus volume delivered, Actual infusion rate, Actual total fluid delivered, Drug delivery the actual start time of drug delivery, the actual stop time of drug delivery, or the actual delivery flow rate profile, A monitoring client 1, other monitoring clients 4, and / or a remote communicator 11 In another embodiment, the pill dispenser may communicate to one or more of the following (if applicable): The dispenser 814 optionally includes a dispensed actual pill, a dispensed actual pill tag, and a dispensed actual pill tag. Type, actual pill dispensing schedule at the time of dispensing or whether maximum pill dispensing criteria were exceeded The data such as whether the monitoring client 1, other monitoring clients 4 and / or remote You can reply to Communicator 11.

[0316] Patient care devices 14, 15, 16, 17, 35, 830, 810, 812, 814, The data received from 148 may be used anywhere to generate alarms and / or alerts. For example, one or more of monitoring clients 1, 4, and 11 may , increasing the pressure downstream of one or more of the infusion pumps 830, 810, 812 by increasing the pressure in the tubes to the patient. excessive clotting, penetration, blockage or kinking of the bag, or other material within the intravenous bag 170 This can be used as an indication of a blockage due to a sudden increase in downstream pressure. In response, one or more of the monitoring clients 1, 4, 11 may visually or audibly notify the user. Additionally or alternatively, a warning or alert may be issued to Patient 2. A sudden drop in downstream pressure may indicate that the tubing has become dislodged from the needle and / or the needle is no longer attached to the patient. In response, one or more of monitoring clients 1, 4, and 11 The monitoring client may issue a visual or audible warning or alert to the user. One or more of Ants 1, 4, 11 may optionally be infusion pumps 830, 810, 812. and transmitting instructions to one or more of the following: Depending on the situation, the delivery of fluid can be stopped.

[0317] In some embodiments, the numbers are as shown in FIG. 8 or as described herein. Each item, component, device, patient, and The patient-care device, dock, and computing device are optional. For example, in some implementations In the embodiment, the monitoring client 1 is optional, the monitoring server 3 is optional, and the 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 Optional, online drug database 9 is optional, Adverse Drug Events Network Work is optional, the patient's personal EHR is optional, and / or The treatment outcome database 10 is optional. In some embodiments, each patient-care device 830, 810, 812 is optional. Similarly, system monitor 131, wrist band 118, RFID 116, barcode 114, scanner 120, display 808 and / or AC power supply are each In some embodiments shown, this is optional.

[0318] Additionally, in some embodiments, a method such as that shown in FIG. 8 or described herein may be used. There are several items, components, numbered and unnumbered, such as components, devices, patient-care devices, docks, and computing devices are integrated into a single item. system, component, device, patient care device, dock or computing device. Although multiple items, components, devices, patient care devices, Docks and computing devices are contemplated. For example, a single pill dispenser 814 Although shown in FIG. 8, in some embodiments, two pill dispensers 814 Multiple pill dispensers 814 may be used, and may use any number of pill dispensers 814. In addition, Or alternatively, in some embodiments, multiple docks 804 or 806, and and / or multiple monitoring client docks 102 may be used.

[0319] Additionally or alternatively, certain patient-care devices 830, 810, 812 Although shown, other combinations, subsets, or multiples of specific patient care devices may be used. For example, in some embodiments, patient care Only the infusion pump 830 of the device is in use, and in this particular example, no other patient The elderly care devices 810, 812, 814 are disabled and are not present or available for system use. is not available, powered down, or is not part of the system 800 of FIG. Additionally or alternatively, in some particular embodiments, Only patient-care devices can be docked to dock 804 or 806. In one specific embodiment, the infusion pump 830 is the only pump docked within the dock 804. devices, and the dock 804 only receives one device, e.g., the infusion pump 830. do.

[0320] In FIG. 8, dock 804 is shown capable of receiving several patient-care devices. Although shown in FIG. 1, in other embodiments, the device dock 804 may be a single patient care a patient-care device, multiple patient-care devices, or any arbitrary number of patient-care devices Also, sections of the dock may not be used (not shown in Figure 8). In addition, the monitoring client dock 102 receives one monitoring client 1. Although shown to be possible, in other embodiments, the monitoring client The dock 102 can support two monitoring clients 1, three or more monitoring clients 1, or 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 dockable. It can operate without docking and / or is not dockable or standalone can operate as a patient care device.

[0321] The system 800 of FIG. 8 may be configured to maintain communication therewith using any known communication method. For example, in some embodiments, a schedule of any communication may be used. It can be used in broadcast, anycast, multicast or unicast mode. You can use routing algorithms such as distance vector routing. It can use a link-state routing protocol, and can use optimized link-state routing protocols, Path vector protocols can be used to provide static routing with predefined alternative communication paths. The present invention may use a networking technique and / or may use an adaptive network. For example, in some embodiments of the present disclosure, a weight may be assigned to each communication path. The Dijkstra algorithm is used to connect a monitoring client 1 or hub 802 with one or more patients. and care devices (e.g., patient-care devices 830, 810, 812, and 814). The weights may be used to communicate between the The signal quality may be determined as a function of the bit error rate and available data throughput. It may be linear in put or wait time, and / or the like.

[0322] In an embodiment of the present disclosure, the facility service 8 and / or the adverse drug event network 9 It may also be equipped with a Drug Error Reduction System (DERS). First set predetermined criteria for triggering an alarm, and / or hard alarm A soft alarm may include a second set of predetermined criteria for triggering. The user interface of the pump 830, the user interface of the hub 802 08 and / or to caregivers using the user interface of the monitoring client 1 can be disabled (e.g., turned off) by An alarm may be an alarm only, whereas a hard alarm is an alarm that is caused by a Treatment is discontinued until removed.

[0323] In yet a further embodiment of the present disclosure, the DERS system defines a soft limit. The first set of predetermined criteria that defines the minimum and / or maximum limits, and / or the second set that defines the hard limits. Hard and soft limits may include predefined criteria for size, weight, age, etc. , prescribing therapeutic limits, such as drug dosage, based on other patient parameters or other criteria The soft limits are set by the infusion pump 830 user interface, monitoring client, The user interface of the Ant 1 and / or the user interface of the Hub 802 may be overridden by a caregiver using the interface 808 to ensure that treatment does not exceed a first set of predetermined criteria. A hard limit allows treatment to begin even if the setting is outside the Treatment is continued until the threshold is met by a second set of predetermined criteria. from being started.

[0324] In some embodiments, the patient-care devices 830, 810, 812, 814, 14, 15, 16, 17, 35 and / or 148, Monitoring Client 1, Remote Communication The data acquisition unit 11, and the docks 102 and / or 804, and / or the hub 802, for example, For example, you may provide secure data classes via an API.

[0325] Referring again to the drawings, FIG. 9 illustrates a stackable storage container in accordance with yet another embodiment of the present disclosure. Monitoring client 902, stackable infusion pump 904, stackable syringe An electronic patient care system having a pump 906 and another stackable patient care device 908. A block diagram of a system 900 is shown. Stackable devices 902-908 are Lanes and / or buses may be used for communication (in some embodiments, stacked The enabled devices 902-908 communicate via a communication module.

[0326] Optionally, instructions or requests are transmitted to the patient-care devices 14, 15, 16, 17, 35, 1 28, 904, 906, 908, 148, e.g., bolus volume, infusion flow rate , total fluid delivered, start time of drug delivery, stop time of drug delivery, or delivery flow rate profile. Stackable infusion pump 904, stackable syringe pump 906, and and / or other stackable patient-care devices 908. 902, other monitoring clients 4, and / or remote communicators 11. In some embodiments, for example, pill dispensing instructions for dispensing a pill may be provided. instructions or information, such as pill type, pill dispensing schedule, and / or maximum pill dispensing criteria. or requests to the pill dispenser 128. One or more of the following criteria can be used: Maximum pill dispensing criteria is the number of pills that can be delivered within a given time period. This is the maximum amount of drug that can be administered, for example, if a particular drug is administered as needed (i.e., However, if taken in excess, the drug may be unsafe and may cause up to Pill dispensing criteria are used to ensure that medication is safely administered by the patient, for example, "a specified amount within a specified time." This can prevent unwanted intake.

[0327] Optionally, patient-care devices 14, 15, 16, 17, 35, 128, 904, 9 06, 908, 148 also transmit data to the monitoring client 902, other monitoring clients 4 and / or the remote communicator 11 to issue an alarm or alert or Determine whether a treatment or condition is safe for the patient Determine whether the system 900 is operating properly or within predetermined boundaries. , and / or the monitoring client 902, other monitoring clients 4 and / or remote The data can be displayed on the display of the communicator 11. For example, The options include a stackable infusion pump 904, a stackable syringe pump 906, and and / or other stackable patient-care devices 908 may be configured to control upstream pressure, upstream pressure changes, downstream pressure to patient 2; downstream pressure change to patient 2; air in infusion line presence or absence of medication, actual bolus volume delivered, actual infusion rate, actual total fluid delivered, medication Actual start time of drug delivery, actual stop time of drug delivery, or actual delivery flow rate profile The monitoring client 902, other monitoring clients 4, and / or remote communities In another embodiment, the , pill dispenser 128 optionally includes, for example, dispensed actual pills, dispensed actual pills, the actual pill type, the actual pill dispensing schedule when dispensed, or the maximum pill dispensing criteria The stackable monitoring client 902, other monitoring clients, and the like can send data such as whether the The message may be sent back to the client 4 and / or the remote communicator 11.

[0328] Patient care devices 14, 15, 16, 17, 35, 128, 904, 906, 908, The data received from 148 is analyzed for the presence of certain predetermined conditions and alarms and For example, one of the monitoring clients 902, 904, 901 may The above is a list of stackable infusion pumps 904 and / or stackable syringe pumps. Increased pressure downstream of pump 906 may be used to prevent excessive clotting, penetration, blockage or kinking of the tubing to the patient. This can be an indication of kinking or blockage by other material within the intravenous bag 170. In response to a sudden increase in downstream pressure, the monitoring clients 902, 904, 11. One or more of the following may provide a visual or audible warning or alert to the user: Additionally or alternatively, a sudden drop in downstream pressure to the patient 2 may This is an indication that the needle has become dislodged from the needle and / or that the needle is now removed from the patient. In response, one or more of the monitoring clients 902, 4, 11 may provide a visual or audible notification to the user. One of the monitoring clients 902, 904, 901 may visually issue an alert or warning. The above may optionally include a stackable infusion pump 904 and / or a stackable Send instructions to one or more of the syringe pumps 906 to rapidly increase downstream pressure to the patient 2. In response to a significant increase and / or decrease, fluid delivery can be stopped.

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

[0330] Daisy chaining can be done, for example, by stacking the monitoring client 902, stacking the Stackable patient-care device 908, stackable infusion pump 904 and stackable system through electrical conductors within each of the syringe pumps 906, thereby A continuous electrical contact is maintained between each of these devices.

[0331] Additionally or alternatively, stackable devices 902, 908, 904, 906 may optionally maintain wireless communication with each other. The client 902 is a stackable device 9 with daisy-chained conductors. An internal short circuit in one of the stackable devices 902, 908, 904, or 906 It can detect electrical non-reactions and is a stackable monitoring client 9 02 queries each stackable device 908, 904, 906 to determine which device After making this determination, the stackable monitoring The client 902 is one of the stackable devices 902, 908, 904, and 906. The faulty device is then disconnected by radio communication with the isolated disconnect circuit in the faulty device. - can be electrically disconnected from the chained conductor. Alternatively, one or more of the stackable devices 902, 908, 904, 906 may include: One of the stackable devices 902, 908, 904, 906 is faulty; and and / or one of the stackable devices 902, 908, 904, 906 is a daisy chain alerting the user that they are communicating wirelessly rather than via a wired communication link connected to the network; An alert may be sent and / or a message may be displayed.

[0332] Additionally or alternatively, stackable monitoring clients 902, stack stackable device 908, stackable infusion pump 904 and stackable syringe Each pump 906 is connected to each device below or above it in the daisy chain. For example, stackable infusion pump 904 may , buffering the data in an internal memory, and the stackable patient-care device 908 Patient care with stackable signals that indicate readiness to receive additional data By communicating that information when received from device 908, the stackable system All data received from the syringe pump 906 can be transmitted. In the form, the numbered items may be as shown in FIG. 8 or as described herein. Each item, component, device, patient care device, The dock and computing device are optional. For example, in some embodiments, the monitoring The client 1 is optional, the monitoring server 3 is optional, and the facility service 8 is optional. Each service 19, 20, 21, 22, 23, and 24 is optional and The cloud server 25 is optional, and each of the other monitoring clients 4 is optional. The online drug database is optional, and the adverse drug events network is optional. The patient's personal EHR is optional and / or the treatment outcome data is optional. The database 10 is optional. Additionally or alternatively, in some embodiments In this embodiment, each patient-care device 830, 810, 812 is optional. System monitor 131, wristband 118, RFID 116, barcode 114, scanner The power supply 120, the display 808 and / or the AC power source may each be implemented in accordance with some aspects of the present disclosure. In the embodiment, this is optional.

[0333] Additionally, in some embodiments, a method for detecting a cellular signal, such as that shown in or described in conjunction with FIG. Several items, both numbered and unnumbered, The components, devices, patient care devices and computing devices are single items, Although shown as a component, device, patient care device or computing device, However, multiple items, components, devices, patient care devices and computing devices For example, a single pill dispenser 128 is shown in FIG. However, in some embodiments, two pill dispensers 128 may be used. , multiple pill dispensers 128 can be used, or any arbitrary number of pills A dispenser 128 may be used.

[0334] Additionally or alternatively, certain patient-care devices 904, 906, 908 Although shown, other combinations, subsets, or multiples of specific patient care devices may be used. For example, in some embodiments, patient care Only one of the devices, the stackable infusion pump 904, is used, and in this particular implementation In the example, other patient devices 906, 908 are disabled and not present or available for system use. or is not available, powered down, or is not part of the system 900 of FIG. 9. Additionally or alternatively, in some specific embodiments, Only patient-care devices that are in the same position are stacked. For example, in one particular embodiment, only infusion ports are stacked. Pump 904 is the only device in the stack. , non-stacked patient-care devices, e.g., patient-care devices 904, 906 and and / or the 908 continues to operate when operating as a standalone device Additionally, alternatively, or optionally, some specific implementations may be In the form of patient-care devices 14, 15, 16, 17, 35, 904, 906, 908, The 128, 148 are dockable and can operate undocked, and and / or is not dockable and may operate as a standalone patient-care device. This can be done.

[0335] In Figure 9, a stack is shown in which several patient care devices can be stacked. Although shown in FIG. 1, in other embodiments, the stack may include one patient-care device, multiple patient-care device, or any number of patient-care devices. In addition, the stack is shown as being capable of receiving one monitoring client 902. Although shown, in other embodiments, two stackable monitoring clients 902 , three or more stackable monitoring clients 902, or any arbitrary number of stacks The network-enabled monitoring clients 902 are stacked together in the system 900 .

[0336] The system 900 of FIG. 9 may be configured to maintain communication therewith using any known communication method. For example, in some embodiments, a schedule of any communication may be used. It can be used in broadcast, anycast, multicast or unicast mode. You can use routing algorithms such as distance vector routing. It can use a link-state routing protocol, and can use optimized link-state routing protocols, Path vector protocols can be used to provide static routing with predefined alternative communication paths. may use a network and / or may use an adaptive network For example, in some embodiments of the present disclosure, a weight may be assigned to each communication path. and using the Dijkstra algorithm to connect the monitoring client 902 to one or more patient care providers. communicating with patient-care devices (e.g., patient-care devices 904, 906, 908); The weights can be calculated in any known manner, e.g., based on bandwidth, signal quality, bit error rate, available data throughput or latency, and It may be linear and / or similar.

[0337] Referring to Figures 1, 3, 5, 7, 8 and 9, various update techniques and / or methods can be utilized. Use the hub, dock, device, insulin pump, infusion pump and / or patient The patient-care device may be updated. For example, the patient-care device may be, for example, In this mode, RS232 format data is converted to, for example, I2C format data. A bus converter for connecting the bus to a computing device (in some embodiments, a personal computer) or any device that can be used in a manner similar to a personal computer The device may be coupled to a device such as, but not limited to, a tablet. devices, insulin pumps, infusion pumps and / or patient care devices In some embodiments, a processor in the server may execute an update program to, for example, Flash memory by the supervisor processor and / or command processor The downloading of software into the library may be controlled or organized. In embodiments, the computing device may be a hub, dock, device, insulin pump, infusion Download the software into the flash memory of the pump and / or patient care device. The software update obtained by the computing device may be organized to load , accessible by the supervisor processor and / or command processor The software updates can be stored in a flash memory (not shown). In some embodiments, it can be invoked automatically by a scripting process It may be a command line program.

[0338] In some embodiments, the hub, dock, device, insulin pump, or infusion pump and / or patient-care devices may use, including but not limited to, web-based secure Through the portal and / or via email and / or through wireless communication providers The protocol allows you to download applications, update software, Download new information, upload information, and / or transmit information to various machines It may also be a web-connected remote interface that may include the ability to Thus, in various embodiments, a remote interface The application can run on any functional device, not on the so-called dedicated device. Additionally, in some embodiments, the remote interface may be Including but not limited to, hubs, docks, devices, insulin pumps, infusion pumps, patients Care devices, Bluetooth or other communication devices, patient care devices, and / or or any other device, and Bluetooth allows you to communicate using line frequency ("RF") communications. , or may be otherwise enabled.

[0339] In some embodiments, the charging station may include a remote Septal interface, hub, dock, device, insulin pump, infusion pump Some embodiments may include a charging area for the patient-care device and / or the patient-care device. In some embodiments, the charging station may include a USB port. A USB port may be provided, so that in some embodiments, Hubs, Docks, Devices, Insulin Pumps, Infusion Pumps, Patient Care Devices and / or or the charging station receives power to charge the remote interface. Additionally and / or alternatively, the USB port may For connection to a computer or other device and / or computer-type equipment Therefore, the remote interface and / or hub, dock, device, insulin Configured for data transfer to / from pumps, infusion pumps and / or patient care devices In embodiments that include a USB port, the remote interface can be charged. The system is operated by a personal computer and / or a web portal Calls the software update check function to check for available software updates. If so, software updates may be downloaded via, for example, a USB connection. Updates are then performed when pairing the hub, dock, device, insulin pump, or infusion It can be transferred to a pump and / or patient care device.

[0340] Therefore, users can easily access the hub, dock, device, insulin pump, infusion pump and and / or connect the remote interface of the patient-care device to a personal computer. and / or in some embodiments, transmit the data to a remote interface. The data can be uploaded to a web portal or other device via the web interface. Now, this may be achieved during a "recharge" of the remote interface, which recharges: In some embodiments, this is done using a USB connection to a personal computer Well, this is a personal charger in addition to the charging / recharging remote interface. Sync data from your computer, 1908 and / or web portal, and At this time, the system may Are software updates available for the above and / or remote interfaces? The user can select "Download Updates" and These updates may occur when charging and / or when the remote interface is directly or indirectly Web sites specifically designed for personal computers and / or systems Anytime your hub, dock, device, or insulin pump is connected to the portal , downloaded to the remote interface of the infusion pump and / or patient care device As mentioned above, the remote interface is capable of communicating with a variety of devices. Therefore, software updates can be performed by remote interface to any This has many advantages, for example, Uploading data / information from, but not limited to, any of your devices; and / or from a personal computer and / or from the internet / web portal Both updates and / or downloading applications to any device A remote interface is connected to a personal computer / web portal for This can be desirable for a number of reasons, e.g. For example, but not limited to, being able to efficiently and easily update all your devices from one connection. and / or store all of your data from all your devices in one place. and / or personal computers 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 downloaded.

[0341] Thus, in some embodiments, a personal computer / web portal This includes, but is not limited to, all information from all devices, including remote interfaces. This allows new "remote interfaces" to be introduced into the system at any time. This will provide a new remote interface to the personal computer / web portal. and download all information about the system to the remote interface. In some embodiments, this can be achieved by first It may be necessary to remove the interface from the "Authorized Devices" list, but other implementations may require In this form, the system "allows" additional remote interfaces with permission from the user. Thus, the system can communicate with the device, and and / or a personal computer and / or a web portal can be connected All information and and the ability to download applications.

[0342] This also allows remote interfaces to access any application from the Internet. This allows you to download the application to any device in the system. In various embodiments of the system, the user may access the This includes several parameters such as the ability to communicate wirelessly and connect to a web portal. (including) any device that controls various devices, e.g., infusion pumps, and / or CGMs Sensors / transceivers and / or other analyte sensors and / or hubs, docks, devices other devices such as chairs, insulin pumps, infusion pumps and / or patient care devices devices that may receive data from and / or control the devices, In some embodiments, the remote interface and / or the remote One or more applications on the remote interface may be protected by a password or similar. It can be paired with one or more devices, e.g., an infusion pump and / or CGM sensor. The device may be paired with one or more other devices.

[0343] In some embodiments, the information on the remote interface is uploaded and / or synchronize with another device and / or computer and / or machine, e.g. Internet sites that may be password protected, including, but not limited to, Users may upload data to the portal. You may access information from your device and / or any device-specific applications. You may download information, including the application, to any device and therefore However, it can download user information, including history, preferred settings, and other information, to any device. You can download it.

[0344] FIG. 10 illustrates a method for monitoring patient-care parameters of a patient-care device on a monitoring server according to an embodiment of the present disclosure. 6 is a flowchart of a method 600 for communicating data. 608. The patient-care device of method 600 optionally includes a Any patient-care device, e.g., patient-care device 7, 14 of Figs. 15, 16, 17, 35, 126, 128, 130, 148, patient care device 1 of FIG. 4, 15, 16, 17, 830, 810, 812, 814, patient-care device 14 of FIG. , 15, 16, 17, 904, 906, 908 or other patient care methods disclosed herein It may also be a device.

[0345] Act 602 establishes a communication link between the patient-care device and the monitoring server. 04 transmits patient care parameters to a monitoring server, e.g., over a local area network and and / or over the Internet via WiFi, monitoring clients, one or more hubs or communicate through a dock, etc. Act 606 de-identifies the patient-care parameters. Action 606 may be performed, for example, within the monitoring server 3 of FIGS. This can be done dynamically and electronically. For example, removing the patient's name and monitoring A random serial number that cannot be used to determine the patient's identity in the server Act 608 may replace the de-identified patient care parameters. The data can be stored in a database, e.g., an SQL database, a relational database, or an associative database. The information is stored in a monitoring server such as a cloud server.

[0346] FIG. 11 illustrates a method for determining the patient-care device status in a monitoring server in accordance with an embodiment of the present disclosure. FIG. 7 is a flow chart diagram of a method 701 for collecting patient-care parameters from multiple patients. Act 701 includes acts 703-713. In some embodiments, acts 703-713 are all optional. The patient-care device may be any of the patient-care devices disclosed herein. 1, 3, 5 or 7, such as the patient care device 7, 14, 15, 16, 17, 3 5, 126, 128, 130, 148, patient care devices 14, 15, 16, 17 of FIG. , 830, 810, 812, 814, patient care devices 14, 15, 16, 17 of FIG. 904, 906, 90, or any other patient-care device disclosed herein. stomach.

[0347] Act 703 involves communicating with a monitoring server, e.g., monitoring server 3 of FIG. 1, 3, 5, 7, 8 or 9; Establishing communication links between a plurality of patient-care devices associated with a plurality of patients. Optionally, multiple patient-care devices may be associated with a single patient and / or Alternatively, multiple patient-care devices may be associated with different respective patients.

[0348] Act 705 comprises transmitting the plurality of patient-care parameters from the plurality of patient-care devices to a monitoring server. Act 707 de-identifies the patient care parameters, and act 709 communicates these patient care parameters. The care parameters are stored in the monitoring server, for example, in a SQL database, a relational database, or an associative database. Act 707 may automatically and / or Act 711 may be performed electronically. For example, a patient with high blood pressure may be treated with a drug designated to lower blood pressure. Act 713 may include sub-selecting a plurality of patient-care parameters associated with a plurality of patients. The data is analyzed to determine the effectiveness of the treatment. For example, all patients receiving blood pressure medication in act 711 Patients have their blood pressure compared to blood pressure readings at a given time, say 6 months later, and It can be determined whether a treatment is effective for one or more patients.

[0349] FIG. 12 illustrates a patient-care device when operation of the patient-care device is interrupted in accordance with an embodiment of the present disclosure. 8 is a flow chart diagram of a method 801 for recovery of a care device, e.g., a patient-care device. is removed from the dock, has lost power, and is experiencing a hardware or software failure. The device may be configured to temporarily disable one or more processors or other circuits within the device. Additionally or alternatively, one or more processes on the patient-care device may The device may implement method 801 so that the patient-care device is hot-swappable. good.

[0350] The method 801 includes acts 803-823. Each act 803-823 may be implemented in several ways. In some embodiments, the act 803 may be optional. The patient-care device of method 801 receives the patient-care parameters. The patient care device may be any patient care device, such as the patient care device of FIG. Devices 7, 14, 15, 16, 17, 35, 126, 128, 130, 148, Fig. 8 Patient-care device 14, 15, 16, 17, 830, 810, 812, 814 or FIG. 9 14, 15, 16, 17, 904, 906, 908 That's fine.

[0351] Act 805 stores one or more patient-care parameters in a non-volatile memory of the patient-care device. Patient care parameters include patient treatment parameters or patient status parameters. The value may be any value associated with patient care, including, for example, the infusion rate of an infusion pump. Patient treatment parameters.

[0352] Act 807 receives one or more operating parameters for the patient-care device. A meter can be anything related to the operation of a device, for example, an operating parameter. The data includes infusion pump motor speed limits, infusion pump speed, wireless radio wattage limits, and power Act 809 may be a battery discharge rate or rate limit, update frequency, etc. The device stores one or more operating parameters in a non-volatile memory.

[0353] Act 811 calculates one or more additional operating parameters for the patient-care device. The calculated operating parameters are any parameters calculated to operate the patient-care device. Parameters, e.g., proportional integral derivative with adaptive gain coefficients used in automatic gain control The gain coefficient of the PID (Proportional Integral Derivative) control loop. One or more additional operating parameters are stored in the memory.

[0354] Act 815 may include notifying the patient-care device that operation has been interrupted, e.g., power loss, a patient-care device failure, or a brownout CPU reset Act 817 determines that operation of the patient-care device can resume. Determine that.

[0355] Act 819 includes receiving or calculating one or more of the following in an operating memory of the patient-care device: and act 821 loads the operating parameters of the patient-care device. Act 823 loads one or more patient-care parameters into the patient-care device. Resume operation.

[0356] Referring now to FIG. 13, a diagram of a computer having a user interface according to an embodiment of the present disclosure is shown. 9 is a flowchart diagram of a method 900 for pairing a monitoring client to a patient-care device. The method 900 includes acts 902-912. 1, 3, 5, 7 or 8, or the monitoring client 1, or the remote communicator 11, Monitoring client 902 of FIG. 9, remote communicator 1 of FIG. 1. Mobile phones, handheld computers, tablet computers, laptop computers The method 900 may be implemented by a computer, a personal computer, a personal digital assistant, or the like. Although the document describes pairing between a monitoring client and a patient-care device, some In some embodiments, the method 900 may be used to connect a hub (e.g., hub 802 of FIG. 8) to a patient. Pair to care devices (e.g., patient-care devices 830, 810, 812, and 814) and connect the first patient-care device (e.g., patient-care device 830 of FIG. 8) to the second Pairing to a patient-care device (e.g., patient-care device 814 in FIG. 8) whereby the user interface of the first patient-care device controls the second patient-care device. Control and / or system monitor (e.g., the system in Figures 1, 3, 5, 7, 8 or 9) system monitoring 131) to a patient-care device (e.g., a patient-care device such as those shown in FIGS. 1, 3, 5, and 7). Care device 7, 170, 126, 128, 148, 14, 15, 16, 17 or 17 0, or the patient-care devices 830, 810, 812, 814, 14, 15, 16 of FIG. , 17 or 148, and / or patient-care devices 904, 906, 908 of FIG. Can be used to pair to any 14, 15, 16, 17 or 148.

[0357] Act 902 is a user interface (e.g., a display, a touch screen) a monitoring client with a patient interface (e.g., display, buttons, accelerometer for user input, etc.) Act 904 includes transmitting the patient-care device's identification information to the user. The patient-care device displays information such as serial number, device chair-type or patient-care devices using standard or custom discovery protocols The user input can be identified by a visual indication on the user input. Select the patient-care device to pair using the interface. For example, The user in act 906 touches the touchscreen of the monitoring client to initiate the patient care device. The selection of chairs may be displayed.

[0358] Act 908 pairs the patient-care device with the monitoring client. Pairing patient care devices to clients is done via Bluetooth. Low energy (IEEE802.15.1), WiFi, infrared communication, short range It can be achieved by using near field communication (NFC ISO 13157), IR communication or optical methods. As will be apparent in light of this disclosure, custom pairing protocols may be utilized as well. This may involve the use of a handshake sequence or Act 910 may include communicating patient-care parameters between the patient-care device and the monitoring client. for example, by which the patient-care device is communicated with the monitoring client. It may be controlled or monitored.

[0359] Act 912 optionally includes, through the patient-care device, adding another patient-care device. In act 912, the patient-care device operatively communicates additional patient-care parameters. a patient-care device if the patient-care device is operably coupled to or in operable communication with the patient-care device; The device can act as a relay or router, allowing monitoring clients to Additionally or alternatively, the patient may communicate with another patient-care device. A patient-care device may use information from another patient-care device for its operation. For example, an injection pump may operate at a flow rate determined by a flow meter or a temperature probe. Temperature and / or flow meters can be used to monitor the infusion pump and client In addition, the monitoring client can optionally relay information to the Multiple patients connected to paired patient-care devices, either in a row or in series Additionally or alternatively, some of the features of the present disclosure may be capable of communicating with a care device. In some embodiments, method 900 may involve monitoring clients using intravenous tubing to administer patient care. The communication is with a protective device implanted in or attached to the intravenous tubing. via electrical conductors, via electrical communication using the fluid in the IV tubing as the conductive medium; using sound waves traveling through intravenous tubing, or optically using the fluid in the tubing as an optical waveguide This may be done by using communication via an intravenous tube to communicate with another Use a link such as Bluetooth, Bluetooth Low Energy, or WiFi. (e.g., monitoring clients, hubs, docks, patient-care devices and / or monitoring one of the following: a patient care device, hub, dock, patient care device, and / or system monitor You may set up pairings between two or more system monitors.

[0360] In yet further embodiments of the present disclosure, the first device (e.g., a monitoring client, a patient care device or system monitor) to a second device (e.g., a monitoring Pairing with a device (client, hub, patient care device or system monitor) is the first These devices are configured and / or initialized using a communications link. The devices may be paired using a second communication link, for example, near field communication or I / O. R communication, e.g. Bluetooth, Bluetooth Low Energy or WiFi may be used to establish pairing between these devices (e.g., near field communication or Pairing setup (via IR communication) is different from pairing via Bluetooth, for example. Monitoring clients, hubs, and patients monitor device pairing requests. A request to a care device and / or system can be prompted. The patient-care device must be paired to a hub, monitoring client, and / or dock. Once installed, the ID and software version number will be displayed on the Hub, Monitoring Client and These are sent to a server, such as a monitoring server, middleware, or a client. Check your cloud server or other server to ensure the software on the patient-care device is up to date. If the software is out of date, the hub, monitoring client, The client, dock, or patient-care device itself (e.g., directly) downloads the updated software. The patient-care device allows the user to download and program the software. It can notify you if your software is up to date and / or prompt you with a touchscreen Gives options on Lean to optionally provide patient care if software is not up to date The device can be updated. A communication link (e.g., NFC) is used to set up pairing. and / or a communication link using pairing (e.g., Bluetooth or Bluetooth Tooth Low Energy) updates software, ID, software version For example, a pump patient care device may communicate a number and provide notifications thereof. Or you can use it with an insulin pump. "Infusion Pump Method and System," filed March 25, 2010, by Mandro et al. Patent Application No. 12 / 731,843 (Attorney Docket No.: I06), (2) 2009 Bryant et al., "Method and System for Controlling an Infusion Pump," filed April 4, 2004. Patent Application No. 12 / 416,662 (Attorney Docket No. G98), entitled "Compounds for the Prescription of Novel Coronavirus Infections," and / or (3) "Infusion Pump Assembly" filed December 31, 2009 by Kamen et al. This can be seen in patent application No. 12 / 347,985 (Attorney Docket No. G75) entitled and all three of which are incorporated herein by reference in their entirety.

[0361] FIG. 14 illustrates a wearable device paired with a patient-care device according to an embodiment of the present disclosure. How to Monitor Patient Care Device Operation Using a System Monitor The method 1000 includes acts 1014-1040, and includes various devices. 1002, 1004, 1006, 1008, 1100, 1112 are used to Facilitates pairing of devices with the Method 1000 wearable system monitor In some embodiments, each of acts 1014-1040 is optional.

[0362] The wearable system monitor of method 1000 is The wearable system monitor 131 may be one or more patient-care devices. How to pair 1000's system monitor to monitor device 1002

[012] or any sufficient device disclosed herein. For example, the user interface of the monitoring device 1002 may be used. the user interface of the remote communicator 1004, the communication device 1006 a user interface of the patient-care device 1008; The user interface of another patient-care device 1010 or a wearable system The method 1000 uses the user interface of the system monitor 1012 to The system monitor can be paired to a patient care device.

[0363] The patient-care device of method 1000 may be the patient-care device 7, 1 of FIG. 4, 15, 16, 17, 35, 126, 128, 130, 148, and patient care devices in Figure 8. 14, 15, 16, 17, 830, 810, 812, 814, and the patient-care device of FIG. 14, 15, 16, 17, 904, 906, 908 or other patients disclosed herein The patient-care device may be any of the patient-care devices disclosed herein, such as a patient-care device.

[0364] The system monitor of the method 1000 may be implemented as a system 100 of FIG. 1 or a system 300 of FIG. System 500 of FIG. 5, system 700 of FIG. 7, system 800 of FIG. 8, system 9 900, can be used in a standalone system, and and / or for use in any other sufficient system or group of devices disclosed herein It is possible.

[0365] Act 1014 provides for the use of voice recognition algorithms, facial recognition algorithms, barcodes, RFID Use one or more of tags, near field communication, simple login, secure signature, etc. to identify the caregiver (e.g. For example, the caregiver identification in act 1040 may be performed by the on-board camera. Using a camera and / or microphone, the monitoring client Docking stations, device docking stations, communication modules, etc. This can be done by the dock or hub. Safety checks can also be done by monitoring clients. The client, hub, dock, or patient-care device must not allow users to type in the font as displayed. This can prevent font corruption errors by requiring you to enter a Alternatively, in some embodiments, the device may be restarted after one or more failed login or authentication attempts. If the chair takes a photo and stores it, the photo will be stored in the middleware server. The device 1002-1012 may store the information in the storage device 1002-1012. The log entry records the presence of the caregiver at one or more of the devices 1002-1012. , the patient-care device described herein, the monitoring client described herein, The wearable system monitor described herein, the remote communication device described herein, The information may be stored in the nicator and / or any one of the hubs described herein. The act 1016 log could be for caregiver compliance, diagnostic purposes, etc. For example, if a caregiver is scheduled to show up but does not show up, act 1016 It may be possible to record that the caregiver did not show up at the scheduled time.

[0366] The facial recognition algorithm in Act 1014 may use relative body size, shape, and the position of the eyes, nose, chin, and cheekbones. relaying any caregiver's facial features, such as by analyzing facial features or other facial features; The facial recognition algorithm of Act 1014 may be based on 3D facial recognition, skin texture analysis, or Other facial recognition algorithms may be used. In this embodiment, the speech recognition algorithm of act 1014 is a hidden Markov model, dynamic Dynamic time warping-based speech recognition or other speech recognition algorithms (possible) may also be used.

[0367] Act 1018 removes the wearable system monitor from the wearable dock. For example, the system monitor 131 in Figure 1 is a wristwatch-like device. It can be worn on the patient's arm, like a wristband attached to a patient, and is a wearable Part of the system monitor is a wristband, and part of the system monitor is a wearable system monitor. a dock (referred to herein as a "wearable device") having a snap-fit ​​base member into which the It can be removed from the wearable system monitor. When the device is removed from its dock, act 1020 starts a timer. Each of the above and related acts is optional in the method 1000 of FIG.

[0368] The timer in act 1020 measures the time the wearable system monitor is out of its dock. Act 1022 provides that the wearable system monitor tracks the progress of the wearable Treatment stops when a predetermined time has elapsed after undocking from the dock. For example, The wearable system monitor of method 1000 sends a signal to the infusion pump, The pump infusion can be stopped. The wearable system monitor is re-docked. When the wearable system monitor is connected to the wearable device, act 1024 may, for example, - If treatment is interrupted due to being undocked from the dock, the device will Treatment is resumed after a period of time has elapsed.

[0369] As noted above, act 1018 transfers data from the wearable dock to the wearable system. Remove the monitor. Action 1026 may be implemented, for example, by a voice recognition algorithm, a face recognition algorithm, or the like. One or more of: system, barcode, RFID tag, near field communication, simple login, caregiver entry, etc. Act 1026 may be similar to act 1014, and may be similar to act 1014. The same software and / or device may be used as that used in 1014. However, in some embodiments, ...

Claims

1. 1. A system for electronic patient care, comprising: a medical sensor configured to be coupled to a patient and to measure a physiological parameter of said patient; a medical device configured to receive the measured physiological parameter from the medical sensor and configured to communicate the measured physiological parameter; and a server configured to communicate with the medical device and receive the measured physiological parameters; In addition to providing a second medical sensor coupled to the patient and configured to measure a second physiological parameter of the patient; the medical device is configured to receive a second physiological parameter measured from the medical sensor, and the server is configured to receive the measured second physiological parameter; the physiological parameter and the second physiological parameter include data regarding a current blood pressure, a current heart rate, a current cardiac rhythm, and a current respiratory rate; the server is further configured to communicate with a medication error reduction system; the medication error reduction system includes a first set of predetermined criteria for activating a soft alarm and / or a second set of predetermined criteria for activating a hard alarm based on information about the patient, and when the hard alarm is activated, the medication error reduction system interrupts drug treatment. system.

2. 10. The system of claim 1, the biomedical sensor comprises an accelerometer configured to measure patient movement; and the medical device is configured to alarm if the patient's movement does not exceed a predetermined threshold of movement. The system of claim 1 .

3. The system of claim 1 , further comprising a gateway, wherein the medical device is configured to communicate with the server through the gateway.

4. 4. The system of claim 3, wherein the medical devices communicate with the gateway using the web, the medical devices being web clients of the web, and the gateway being a web server of the web.

5. The system of claim 4 , wherein the medical device is configured to communicate with the gateway using at least one communication method for transacting over the web.

Images