Modular power and connection system for infusion devices

Abstract

A modular power and connectivity assembly and system are provided. The modular power and connectivity assembly includes a housing, a power assembly, and a communication assembly. The modular power and connectivity assembly is reusable and provides power and communication to a removably coupled infusion device. The system includes a plurality of modular power and connectivity assemblies, a charging station for charging the modular power and connectivity assemblies, a connection hub for communicating with the modular power and connectivity assemblies, and a cloud interface for a healthcare system for sending and receiving information to and from the modular power and connectivity assemblies. A method of operating a modular power and connectivity system is also provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 949,305, filed on December 17, 2019, entitled “MODULAR POWER AND CONNECTIVITY SYSTEM FOR INFUSION DEVICES,” the disclosure of which is incorporated herein by reference in its entirety for all purposes. Technical Field

[0003] The present disclosure relates generally to power and connectivity for devices, and in particular to a modular system of power and connectivity for infusion devices. Background Art

[0004] Infusion devices are used in the medical field for intravenous (IV) applications. Typical infusion devices require independent power and connections to provide the desired infusion results. Typical infusion systems require physical connection of each infusion device to the existing infrastructure, and / or require each device to include its own power source and connection hardware, resulting in increased costs and / or undesirable compromises in the infusion workflow. For example, typical infusion devices follow an "all-in-one" approach, in which all aspects of the infusion device (e.g., power, connection) are included in the device. However, infusion set devices (e.g., IV line components) are typically single-use devices that are disposable, making the handling of high-cost components undesirable.

[0005]

[0006] It would therefore be desirable to provide a non-disposable modular power and connection assembly for a disposable infusion set. Summary of the invention

[0006] One or more embodiments provide a modular power and connection assembly. The modular power and connection assembly includes a housing including a cavity configured to receive a device coupling member, a power assembly configured to provide power to an infusion device, and a communication assembly configured to provide communication with the infusion device. The modular power and connection assembly is configured to be reusable and removably coupled to an infusion device.

[0007] One or more embodiments provide a power and connection system. The power and connection system includes one or more reusable modular power and connection components. Each reusable modular power and connection component includes a housing having a cavity configured to receive a device coupling member, a power component configured to provide power to an infusion device, and a communication component configured to provide communication with the infusion device. Each modular power and connection component is configured to be removably connected to an infusion device. The power and connection system also includes a connection hub configured to transmit electronic signals to and receive electronic signals from the one or more reusable modular power and connection components.

[0008] One or more embodiments provide a method of operating a modular power and connectivity system. The method includes: removably coupling a modular power and connectivity assembly to an infusion device; transmitting power from the modular power and connectivity assembly to the infusion device; providing a communication link between the modular power and connectivity assembly and the infusion device; transmitting data from the infusion device to the modular power and connectivity assembly; transmitting at least a portion of the data from the modular power and connectivity assembly to a connectivity hub; and transmitting the portion of the data from the connectivity hub to a cloud interface of a healthcare network.

[0009] The foregoing and other features, aspects, and advantages of the disclosed embodiments will become more apparent from the following detailed description and accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the principles of the disclosure.

[0011] Figure 1 A schematic diagram of an exemplary infusion set with a typical infusion device is shown.

[0012] Figure 2 A perspective view of a modular power and connectivity assembly in accordance with some aspects of the subject technology is shown.

[0013] Figure 3 A perspective view of a modular power and connectivity assembly in accordance with some aspects of the subject technology is shown.

[0014] Figure 4 A perspective view of a charging station is shown in accordance with some aspects of the subject technology.

[0015] Figure 5 An example of a healthcare organization network in accordance with some aspects of the subject technology is shown.

[0016] Figure 6 An example of a modular power and connectivity assembly in communication with a user device having an exemplary graphical user interface in accordance with some aspects of the subject technology is shown.

[0017] Figure 7 An example of an institutional patient care system for a healthcare organization in accordance with some aspects of the subject technology is shown.

[0018] Figure 8 is a conceptual diagram illustrating an exemplary electronic system for communicating with and controlling modular power and connectivity components in accordance with some aspects of the subject technology.

[0019] Fig. 9 A method of operating a modular power and connection system is shown. DETAILED DESCRIPTION

[0020] The detailed description given below describes various configurations of the present technology and is not intended to represent the only configuration in which the present technology can be implemented. In order to provide a thorough understanding of the present technology, the detailed description includes specific details. Accordingly, as a non-limiting example, dimensions are provided with respect to certain aspects. However, it will be apparent to those skilled in the art that the present technology can be implemented without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring the concept of the present technology.

[0021] It should be understood that the present disclosure includes examples of the present technology and does not limit the scope of the appended claims. Various aspects of the present technology will now be disclosed based on specific but non-limiting examples. The various embodiments described in this disclosure can be implemented in different ways and variations and according to the desired application or implementation.

[0022] The subject technology provides a modular solution with independent power and connection. For example, a non-disposable, rechargeable power supply source allows the function of a disposable peripheral infusion device (e.g., sensor, pumping element). The modular design provides a lower total device cost, a smaller environmental impact from processing electronics, prevents incorrect connection of the device, and prevents cybersecurity risks via a proprietary interface. The modular solution further reduces the cost burden on consumers by separating high-cost non-disposable components (e.g., batteries, communication interfaces) from low-cost disposable components (e.g., sensors, pumping elements).

[0023] The present disclosure relates to an infusion set assembly, such as a non-disposable modular power and connection assembly for an infusion set. The modular power and connection assembly can provide power and connection to any desired infusion set (e.g., sensor, pump). Typically, a standard infusion set 10 is used to infuse fluids into a subject. Figure 1An example of a standard infusion set 10 is shown.

[0024] The infusion set 10 includes a puncture tip 20, which can be a sharp tip for puncturing a rubber stopper, or rounded and blunt for insertion into a bag (not shown). The tip 20 contains a channel for fluid and an optional second channel for ventilation. A vent 21 is typically located near the puncture tip 20 to allow air to flow into the drip chamber 22. The vent 21 can be provided with a bacterial filter to prevent bacteria from entering the device.

[0025] The drip chamber 22 has a droplet generator 23 at the top of the drip chamber 22, which generates droplets of a certain size. Droplets from the droplet generator 23 fall into the drip chamber 22, so that the drip chamber 22 is partially filled with liquid. This prevents air bubbles from entering the connecting tube 24, which is harmful to the patient. A particle filter (not shown) can be provided at the lower orifice of the drip chamber 22.

[0026] The connecting tube 24 connects the drip chamber 22 to the patient. The connecting tube 24 is typically about 150 cm long and can be made of PVC. For clarity, the tube 24 is shown in FIG. Figure 1 The connecting tube 24 generally has a continuous diameter over the entire length of the tube 24 .

[0027] At the end of the connecting tube 24 is a Luer connector 25, which is standardized for connection to all other components of the device having a standard Luer taper. It will be appreciated by those skilled in the art that the Luer connector 25 can be mounted to an infusion pump or hypodermic needle (not shown) for infusing medical fluids into the patient's circulatory system (e.g., into a vein).

[0028] Between the drip chamber 22 and the Luer connector 25 and engaged with the connecting tube 24 is a roller clamp 26 for controlling the flow of fluid through the connecting tube 24. Also between the drip chamber 22 and the Luer connector 25 and engaged with the connecting tube 24 is an infusion set 28 (e.g., a pressure sensor). The infusion set 28 typically requires a connection to a hard-wired power source, such as a power cable / wire connection between the infusion set 28 and a power source outlet. Communication to / from the infusion set 28 typically requires a connection to a hardware communication device, such as a communication cable / wire connection between the infusion set 28 and a router (for example).

[0029] refer to Figure 2, a modular power and connection assembly 100 for an infusion device is shown. The modular power and connection assembly 100 has a housing 105 that is sized and configured to receive an infusion device 110 (e.g., a sensor device, a pump device). For example, the infusion device 110 can be a sensor for sensing the pressure of a fluid flowing through the tube 24. The housing 105 can also be sized and configured to receive tubing, such as a connecting tube 24. For example, the housing 105 can include a tube recess 107 that is sized and configured to receive the tube 24, which can help keep the tube 24 connected to the infusion device 110, help prevent the tube 24 from kinking or shifting, and / or help connect the infusion device 110 to the modular power and connection assembly 100.

[0030] The modular power and connection assembly 100 can be configured as a non-disposable device that can be repeatedly used to provide power and / or communication to multiple disposable infusion sets 10 and / or disposable infusion devices 110. For example, the modular power and connection assembly 100 can be used to provide power and communication to a first disposable infusion device 110, which is then thrown away, and the modular power and connection assembly 100 can be used to provide power and communication to a second disposable infusion device 110. The second disposable infusion device 110 can be used with the same infusion set used with the first disposable infusion set 110, such as replacing the first pressure sensor with the second pressure sensor if the first pressure sensor is broken or if a different type of pressure sensor is needed during an infusion process using the infusion set. In another example, the second disposable infusion device 110 can be used with a different infusion set, such as for the same patient in a different infusion process, or for a new patient.

[0031] In use, the infusion set 110 may be on an infusion line or attached to an infusion line, such as tubing 24. For example, Figure 2 An infusion set 110 is shown having a fluid inlet 112 coupled to a first tube 24a and a fluid outlet 114 coupled to a second tube 24b. Here, fluid may flow from the first tube 24a, through the infusion set 110 (e.g., pressure sensor, pump element), and out through the second tube 24b, such that the infusion set 110 may observe or monitor various aspects of the fluid as it passes (e.g., fluid pressure, fluid color, presence of bubbles), and / or act on the fluid (e.g., pump the fluid, filter the fluid, mix gas / other fluid into the fluid).

[0032] like Figure 2As shown, the modular power and connection assembly 100 is removably connected to the infusion set 110. The housing 105 may include a receiving cavity or cutout 109 that is sized and dimensioned to receive the infusion set 110. The housing 105 and the infusion set 110 may be connected in any desired manner. For example, the housing 105 and the infusion set 110 may have magnetic elements that attract each other. In another example, the receiving cavity 109 may include one or more engagement members (e.g., snaps, sockets, pins, Velcro, tabs) that are configured to engage with opposing engagement members on the infusion set 110. Therefore, the modular power and connection assembly 100 can be easily connected to or disconnected from the infusion set 110 before or after the infusion set 110 and the tube 24 are connected.

[0033] The connection between the housing 105 and the infusion device 110 may include a power connection (e.g., pins, cables) configured to provide power from the modular power and connection assembly 100 to the infusion device 110 when the connection assembly 100 is physically coupled to the infusion device 110. The power connection may be configured as a wireless power transfer, where the housing 105 may have a wireless power transmitter and the infusion device 110 may have a wireless power receiver. Thus, the infusion device 110 may not require a physical connection to the modular power and connection assembly 100, because power may be transferred to the infusion device 110 when the infusion device 110 is in the vicinity of the modular power and connection assembly 100.

[0034] Similarly, the connection between the housing 105 and the infusion set 110 may include a communication connection (e.g., pins, cables) configured to provide communication between the modular power and connectivity assembly 100 and the infusion set 110 when the modular power and connectivity assembly 100 is physically coupled to the infusion set 110. The communication connection may be configured as a wireless communication transmission (e.g., Bluetooth, WiFi, Zigbee), wherein the housing 105 and the infusion set 110 may each have a wireless communication component (e.g., a transmitter, a receiver, a transceiver). Thus, the infusion set 110 may not require a physical connection to the modular power and connectivity assembly 100, as communications may be transmitted and received when the infusion set 110 is in proximity to the modular power and connectivity assembly 100.

[0035] like Figure 3As shown, the modular power and connection assembly 100 may include a harness assembly 120. The harness assembly 120 may include a base 122 and an extension member 124. Here, the infusion device 110 may be coupled to the base 122 (e.g., pins, magnets), and the extension member 124 may couple the base 122 to the housing 105. The extension member 124 may include power and / or communication wires to provide power and / or communication transmission between the modular power and connection assembly 100 and the base 122. The base 122 may be configured as described above to provide power to the infusion device 110 and / or provide communication to / from the infusion device 110 (e.g., physical or wireless transmission). In another example, the extension member 124 may not provide a physical power / communication connection (e.g., formed of a non-conductive material), and power / communication may be transmitted wirelessly between the housing 105 and the base 122, and further transmitted between the base 122 and the infusion device 110. In yet another example, power / communication may be transmitted wirelessly directly between the housing 105 and the infusion set 110 .

[0036] If the infusion set 110 is not sized to fit within the cavity 109, such as if the infusion set 110 is larger than the cavity 109 or the infusion set 110 needs to be connected to other tubes and / or devices, the modular power and connection assembly 100 can be configured to use the harness assembly 120. As another example, the modular power and connection assembly 100 can be configured to use the harness assembly 120 in most or all operations, such as even if the infusion set 110 is sized to fit within the cavity 109. The harness assembly 120 can be configured to be removably connected to the modular power and connection assembly 100 so that the modular power and connection assembly 100 can be used in any of the above-described configurations. As another example, the harness assembly 120 can be integrally formed with the housing 105.

[0037] The housing 105 may also include an indicator 103 (e.g., an LED light) configured to provide a visual indication of the power level in the modular power and connectivity assembly 100. For example, the modular power and connectivity assembly 100 may include one or more rechargeable batteries (e.g., lithium-ion) disposed within the housing 105. The indicator 103 may be configured to provide a visual indication of the power remaining in the battery. The indicator 103 may also be configured to provide a visual indication of a communication link between, for example, the modular power and connectivity assembly 100 and the infusion device 110.

[0038] like Figure 4As shown, the subject technology may also include a charging station 150 configured to provide power for charging one or more modular power and connectivity assemblies 100. For example, the charging station 150 may have a base 152 and a receiving slot 154, wherein the modular power and connectivity assemblies 100 may be inserted into the receiving slot 154. Power may be transferred from the charging station 150 directly to the modular power and connectivity assemblies 100 through a physical connection (e.g., pins, ridges) between a portion of the modular power and connectivity assemblies 100 and the base 152. Power may be transferred from the charging station 150 to the modular power and connectivity assemblies 100 indirectly via a wireless power connection.

[0039] Charging station 150 can be hardwired into a power source (e.g., building electrical wiring) so that charging station 150 is substantially permanently located at a particular location. Charging station 150 can be configured as a portable unit by including an electrical plug for plugging into an electrical outlet and / or a portable battery (e.g., a rechargeable battery).

[0040] like Figure 5 As shown, the subject technology may also include a connection hub 200 configured to enable communication and / or control interconnection between the modular power and connectivity assembly 100 coupled to an infusion set 110 and a cloud interface 250 of an institutional patient care system of a healthcare organization having a user device 260. For example, the connection hub 200 may be configured to send / receive information between the modular power and connectivity assembly 100 and the patient care system to provide mobile control of the infusion set 110 coupled to the modular power and connectivity assembly 100.

[0041] like Figure 5 and Figure 6 As shown, the modular power and connection assembly 100 can transmit information (e.g., sensor information) from the infusion device 110 to the cloud interface 250 through the connection hub 200, reaching a specific user device 260 (e.g., a healthcare provider's smartphone). Therefore, the healthcare provider can remotely monitor the infusion process of the subject. As another example, the information flow can be reversed, where the healthcare provider can enter adjustments (e.g., change the pump rate) on the user device 260, which is then transmitted from the cloud interface 250 to the connection hub 200, to the modular power and connection assembly 100, and then to the infusion device 110 (e.g., pump element). Therefore, the healthcare provider can remotely control the infusion process of the subject. In one or more aspects of the subject technology, a Bluetooth connection can be provided between the modular power and connection assembly 100 and the connection hub 200, a WiFi connection can be provided between the connection hub 200 and the cloud interface 250, and a mobile interface 270 can provide an information connection between the cloud interface 250 and the user device 260.

[0042] Figure 7 An example of an institutional patient care system 300 for a healthcare organization in accordance with some aspects of the subject technology is shown. Figure 7 , patient care devices (or generally "medical devices") 312 are connected to the healthcare facility network 310. The term patient care device (or "PCD") can be used interchangeably with the term patient care unit (or "PCU"), either of which can include various auxiliary medical devices, such as infusion pumps, vital signs monitors, medication dispensing devices (e.g., cabinets, handbags), medication preparation devices, automatic dispensing devices, modules connected to one of the above devices (e.g., a syringe pump module configured to be attached to an infusion pump), or other similar devices. Each medical device 312 is connected to the internal healthcare network 310 via a transmission channel 331. The transmission channel 331 is any wired or wireless transmission channel, such as an 802.11 wireless local area network (LAN). In some embodiments, the network 310 also includes computer systems located in various departments throughout the healthcare facility. For example, Figure 7 The network 310 optionally includes computer systems associated with an admissions department, a billing department, a biomedical engineering department, a clinical laboratory, a central supply department, one or more unit station computers, and / or a medical decision support system. As further described below, the network 310 may include discrete sub-networks. In the example shown, the network 310 includes a device network 340 through which patient care devices 312 (and other devices) communicate in accordance with normal operation.

[0043] In addition, the institutional patient care system 300 may include a separate information system server 330, the functionality of which will be described in more detail below. In addition, although the information system server 330 is shown as a separate server, the functionality and programming of the information system server 330 can be incorporated into another computer if desired by the engineers designing the institution's information system. The institutional patient care system 300 may further include one or more device terminals 332 for connecting and communicating with the information system server 330. The device terminal 332 may include a personal computer, a personal data assistant, a mobile device (such as a laptop, a tablet computer, an augmented reality device, or a smart phone) configured with software for communicating with the information system server 330 via the network 310.

[0044] The patient care device 312 includes a system for providing patient care, such as described in U.S. Patient No. 5,713,856 to Eggers et al., which is incorporated herein by reference for this purpose. The patient care device 312 may include or contain pumps, physiological monitors (e.g., heart rate, blood pressure, ECG, EEG, pulse oximeters and other patient monitors), therapeutic devices, and other drug delivery devices that can be used according to the teachings set forth herein. In the example shown, the patient care device 312 includes a control module or unit 314, also referred to as an interface unit 314, which is connected to one or more functional modules 316, 318, 320, 322. The interface unit 314 includes a central processing unit (CPU) 350 connected to a memory (e.g., a random access memory (RAM) 358), and one or more interface devices, such as a user interface device 354, an encoded data input device 360, a network connection 352, and an auxiliary interface 362 for communicating with additional modules or devices. Although not required, the interface unit 314 also includes a main non-volatile storage unit 356 (such as a hard drive or non-volatile flash memory) for storing software and data, and one or more internal buses 364 for interconnecting the aforementioned elements.

[0045] In various embodiments, the user interface device 354 is a touch screen for displaying information to the user and allowing the user to input information by touching a predetermined area of ​​the screen. Additionally or alternatively, the user interface device 354 may include any device for displaying and inputting information, such as a monitor, printer, keyboard, soft key, mouse, trackball and / or light pen. The data input device 360 ​​may be a barcode reader capable of scanning and interpreting data printed in a barcode format. Additionally or alternatively, the data input device 360 ​​may be any device for inputting encoded data into a computer, such as a device for reading a magnetic stripe, a radio frequency identification (RFID) device, whereby the reader 360 captures digital data encoded in an RFID tag or smart tag (defined below) via radio waves, PCMCIA smart cards, radio frequency cards, memory strips, CDs, DVDs or any other analog or digital storage media. Other examples of the data input device 60 include a voice activation or recognition device or a portable personal data assistant (PDA). Depending on the type of interface device used, the user interface device 354 and the data input device 360 ​​may be the same device.

[0046] Although the data input device 360 ​​is Figure 7314, it should be appreciated that the data input device 360 ​​may be integrated into the pharmacy system 334, or located externally and communicate with the pharmacy system 334 via an RS-232 serial interface or any other suitable communication means. The auxiliary interface 362 may be an RS-232 communication interface, however, any other device for communicating with a peripheral device (such as a printer, patient monitor, infusion pump or other medical device) may be used without departing from the subject technology. In addition, the data input device 360 ​​may be a separate functional module, such as modules 316, 318, 320 and 322, and configured to communicate with the control unit 314 or any other system on the network using appropriate programming and communication protocols.

[0047] The network connection 352 can be a wired or wireless connection, such as through Ethernet, WiFi, BLUETOOTH, an integrated services digital network (ISDN) connection, a digital subscriber line (DSL) modem, or a cable modem. Any direct or indirect network connection can be used, including but not limited to a telephone modem, a MIB system, an RS232 interface, an auxiliary interface, an optical link, an infrared link, a radio frequency link, a microwave link, a WLANS connection, or other wireless connection.

[0048] Functional modules 316, 318, 320, 322 are any devices used to provide care to a patient or to monitor the patient's condition. Figure 7 As shown, at least one of functional modules 316, 318, 320, 322 can be an infusion pump module, such as an intravenous infusion pump for delivering drugs or other fluids to a patient. For the purpose of discussion, functional module 16 is an infusion pump module. Each functional module 318, 320, 322 can be any patient treatment or monitoring device, including but not limited to an infusion pump, a syringe pump, a PCA pump, an epidural pump, an enteral pump, a blood pressure monitor, a pulse oximeter, an EKG monitor, an EEG monitor, a heart rate monitor or an intracranial pressure monitor, etc. Functional modules 318, 320 and / or 322 can be a printer, a scanner, a barcode reader or any other peripheral input, output or input / output device.

[0049] Each functional module 316, 318, 320, 322 communicates directly or indirectly with the interface unit 314, wherein the interface unit 314 provides overall monitoring and control of the device 312. The functional modules 316, 318, 320, 322 can be physically and electronically connected to one or both ends of the interface unit 314 in a serial manner, such as Figure 7, or as detailed by Eggers et al. However, it should be appreciated that other means of connecting the functional modules to the interface unit may be used without departing from the subject technology. It should also be appreciated that a device that provides sufficient programmability and connectivity (such as a pump or patient monitoring device) may have the ability to operate as a stand-alone device and may communicate directly with the network without being connected through a separate interface unit or control unit 314. As described above, additional medical devices or peripheral devices may be connected to the patient care device 312 via one or more auxiliary interfaces 362.

[0050] Each functional module 316, 318, 320, 322 may include a module-specific component 376, a microprocessor 370, a volatile memory 372 for storing information, and a non-volatile memory 374. Figure 7 314, but any number of devices may be directly or indirectly connected to the central control unit 314. The number and type of functional modules described herein are intended to be illustrative and in no way limit the scope of the subject technology. Module-specific components 376 include any components required for the operation of a particular module, such as a pumping mechanism for an infusion pump module 316.

[0051] Although each functional module may be capable of at least some degree of independent operation, interface unit 314 monitors and controls the overall operation of device 312. For example, as will be described in more detail below, interface unit 314 provides programming instructions to functional modules 316, 318, 320, 322 and monitors the status of each module.

[0052] The patient care device 312 can operate in several different modes or characteristics, each of which is defined by a configuration database. The configuration database can be a database on a storage unit 356 inside the patient care device 312, or an external database 337. A specific configuration database is selected based at least in part on patient-specific information (such as device or patient location, age, physical characteristics, or medical characteristics). Medical characteristics include, but are not limited to, patient diagnosis, treatment prescriptions, medical history, medical records, patient care provider identity, physiological characteristics, or psychological characteristics. As used herein, patient-specific information also includes care provider information (such as physician identity) or the location of the patient care device 260 in a hospital or hospital computer network. Patient care information can be input through a network connection 352 or any input / interface device 354, 360, or 362, and can come from anywhere in the network 310, such as, for example, from a pharmacy server, an admission server, a laboratory server, etc.

[0053] Medical devices incorporating aspects of the subject technology may be equipped with a network interface module (NIM) that allows the medical device to participate in a network as a node. Although for clarity, the subject technology will be described as operating in an Ethernet environment using the Internet Protocol (IP), it should be understood that the concepts of the subject technology are equally applicable to other network environments, and these environments are intended to be within the scope of the subject technology.

[0054] Using existing technology, data to and from various data sources can be converted into network compatible data, and information movement between medical devices and networks can be achieved in various ways. For example, patient care device 312 and network 310 can communicate via automatic interaction, manual interaction, or a combination of automatic and manual interaction. Automatic interaction can be continuous or intermittent, and can be achieved through direct network connection 354 (such as Figure 7 ) or occurs via an RS232 link, MIB system, RF link (such as Bluetooth), IR link, WLANS, digital cable system, telephone modem or other wired or wireless communication. Manual interaction between the patient care device 312 and the network 310 involves the physical transfer of data between the systems intermittently or periodically using, for example, a user interface device 354, a coded data input device 360, a bar code, a computer disk, a portable data assistant, a memory card or any other medium for storing data. In various aspects, the communication method is bidirectional and data can be accessed from as many distributed data source points as possible. Decisions can occur in various places within the network 310. For example, but not by way of limitation, decisions can be made in the HIS server 330, the decision support 348, the remote data server 349, the hospital department or unit station 346, or in the patient care device 312 itself.

[0055] According to the subject technology, all direct communications with medical devices operating on the network can be performed through an information system server 30, referred to as a remote data server (RDS). According to some aspects of the subject technology, a network interface module incorporated into a medical device (such as, for example, an infusion pump or a vital sign measurement device) ignores all network traffic that does not originate from an authenticated RDS. The primary responsibility of the RDS of the subject technology is to track the location and status of all networked medical devices with a NIM and maintain open communications.

[0056] A medical device including one or more of the described features may be implemented as an ambulatory medical device. An ambulatory medical device generally refers to a device designed to be portable to support drug administration during transport of a patient or remote drug administration (e.g., outside a healthcare facility, such as in a user's home). U.S. Pat. No. US7163381 to Barak describes a pump that may be adapted for ambulatory care and modified to help provide safe administration during mobility. The disclosure of US7163381 is incorporated herein by reference in its entirety.

[0057] Figure 8 4 is a conceptual diagram illustrating an example electronic system 400 for powering, communicating, monitoring, and controlling a medical device (e.g., an infusion device 110) according to some aspects of the subject technology. The electronic system 400 may be a system for performing operations related to Figure 1-7 A computing device that provides software associated with one or more components and processes, including but not limited to an information system server 330, a device terminal 332, computing hardware within a patient care device 312, or an external database 337. Figure 1-7 The electronic system 400 may be representative of the disclosure of the present invention. In this regard, the electronic system 400 may be a personal computer or a mobile device, such as a smart phone, a tablet computer, a laptop computer, a PDA, an augmented reality device, a wearable device (such as a watch or a band or glasses or a combination thereof), or other touch screen or television having one or more processors embedded therein or coupled thereto, or any other type of computer-related electronic device having a network connection.

[0058] The electronic system 400 may include various types of computer-readable media and interfaces for various other types of computer-readable media. In the example shown, the electronic system 400 includes a bus 408, a processing unit 412, a system memory 404, a read-only memory (ROM) 410, a permanent storage device 402, an input device interface 414, an output device interface 406, and one or more network interfaces 416. In some embodiments, the electronic system 400 may include or be integrated with other computing devices or circuits for operating the various components and processes described previously.

[0059] Bus 408 collectively represents all system, peripheral, and chipset buses that communicatively connect the various internal devices of electronic system 400. For example, bus 408 communicatively connects processing unit 412 with ROM 410, system memory 404, and permanent storage 402.

[0060] Processing unit 412 fetches instructions to be executed and data to be processed from these various memory units in order to perform the processes of the subject disclosure. In various implementations, the processing unit may be a single processor or a multi-core processor.

[0061] ROM 410 stores static data and instructions required by processing unit 412 and other modules of the electronic system. On the other hand, permanent storage 402 is a read-write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic system 400 is turned off. Some embodiments of the subject disclosure use a mass storage device (such as a magnetic or optical disk and its corresponding disk drive) as permanent storage 402.

[0062] Other embodiments use removable storage devices (such as floppy disks, flash drives and their corresponding disk drives) as permanent storage devices 402. Similar to permanent storage devices 402, system memory 404 is a read-write memory device. However, unlike storage devices 402, system memory 404 is a volatile read-write memory, such as random access memory. System memory 404 stores some instructions and data required by the processor at runtime. In some embodiments, the processes disclosed in the subject matter are stored in system memory 404, permanent storage devices 402, and / or ROM 410. Processing unit 412 extracts instructions to be executed and data to be processed from these different memory units in order to perform the processes of some embodiments.

[0063] The bus 408 is also connected to input and output device interfaces 414 and 406. The input device interface 414 enables a user to communicate information and select commands to the electronic system. Input devices used with the input device interface 414 include, for example, an alphanumeric keyboard and a pointing device (also referred to as a "cursor control device"). The output device interface 406, for example, enables the display of images generated by the electronic system 400. Output devices used with the output device interface 406 include, for example, printers and display devices, such as cathode ray tubes (CRTs) or liquid crystal displays (LCDs). Some embodiments include devices that function as both input and output devices (such as touch screens).

[0064] In addition, if Figure 8As shown, bus 408 also couples electronic system 400 to a network (not shown) via network interface 416. Network interface 416 may include, for example, a wireless access point (e.g., Bluetooth or WiFi) or a radio circuit for connecting to a wireless access point. Network interface 416 may also include hardware (such as Ethernet hardware) to connect the computer to a portion of a computer network, such as a local area network ("LAN"), a wide area network ("WAN"), a wireless LAN or intranet, or a network of networks, such as the Internet. Any or all components of electronic system 400 may be used in conjunction with the subject disclosure.

[0065] refer to Fig. 9 , a method 500 of operating a modular power and connection assembly 100 is provided. In step 510, the modular power and connection assembly 100 is coupled to an infusion set 110. For example, the infusion set 110 connected to the tube 24 can be inserted into the housing 105 or connected to the base 122 of the harness assembly 120.

[0066] In step 520, the modular power and connectivity assembly 100 provides power to the infusion device 110. For example, the modular power and connectivity assembly 100 may transmit power through a physical connection (e.g., pins, cables) between the housing 105 and the infusion device 110, or transmit power through wireless power transmission between the modular power and connectivity assembly 100 and the infusion device 110.

[0067] In step 530, the modular power and connectivity assembly 100 communicates with the infusion set 110. For example, the modular power and connectivity assembly 100 may receive sensor information from the infusion set 110 and / or transmit control information to the infusion set 110.

[0068] In step 540, the modular power and connectivity assembly 100 communicates with the healthcare network. For example, the modular power and connectivity assembly 100 may transmit received data or sensor information to the connection hub 200, which in turn may be transmitted to the cloud interface 250 and ultimately received by the user interface 260. Thus, the user interface 260, such as the mobile interface 270, may provide data or information from the infusion device 110 to a user (e.g., a healthcare worker). As another example, the modular power and connectivity assembly 100 may receive control information from the connection hub 200, which in turn may be received from the cloud interface 250, which in turn may be received from the user interface 260. Thus, the user interface 260, such as the mobile interface 270, may provide control information from the healthcare worker to the infusion device 110.

[0069] As used herein, a "user interface" (also referred to as an interactive user interface, a graphical user interface, or a UI) may refer to a network-based interface that includes a data field and / or other control elements for receiving input signals or providing electronic information and / or for providing information to a user in response to any received input signals. Control elements may include dials, buttons, icons, optional areas, or other perceptible markers presented via a UI that, when interacted with (e.g., clicked, touched, selected, etc.), initiate data exchange for a device presenting the UI. The UI may be implemented in whole or in part using technologies such as hypertext markup language (HTML), FLASHTM, JAVATM, .NETTM, web services, or rich site summaries (RSS). In some embodiments, the UI may be included in an independent client (e.g., a thick client, a fat client) configured to communicate (e.g., send or receive data) according to one or more aspects described. Communications may be to or from a medical device or server communicating therewith.

[0070] The functions described above can be implemented in computer software, firmware or hardware. These technologies can be implemented using one or more computer program products. Programmable processors and computers can be included in mobile devices or packaged as mobile devices. Processes and logic flows can be performed by one or more programmable processors and by one or more programmable logic circuits. General and special computing devices and storage devices can be interconnected through a communication network.

[0071] Some embodiments include electronic components, such as microprocessors, storage, and memory, which store computer program instructions in machine-readable or computer-readable media (or otherwise referred to as computer-readable storage media, machine-readable media, or machine-readable storage media). Some examples of such computer-readable media include RAM, ROM, compact disk-read only (CD-ROM), compact disk-recordable (CD-R), compact disk-rewritable (CD-RW), digital versatile disk-read only (e.g., DVD-ROM, dual-layer DVD-ROM), various recordable / rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD card, mini SD card, micro SD card, etc.), magnetic disks and / or solid-state hard drives, read-only and recordable A computer readable medium may store a computer program that is executable by at least one processing unit and includes a set of instructions for performing various operations. Examples of computer programs or computer code include machine code (such as produced by a compiler) and files including higher-level code that is executed by a computer, electronic component, or microprocessor using a decoder.

[0072] Although the above discussion primarily involves microprocessors or multi-core processors that execute software, some implementations are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). In some implementations, such integrated circuits execute instructions stored on the circuits themselves.

[0073] As used in this specification and any claims of this application, the terms "computer," "server," "processor," and "memory" refer to electronic or other technical devices. These terms do not include people or groups of people. For the purposes of this specification, the terms "display" or "present" refer to displaying on an electronic device. As used in this specification and any claims of this application, the terms "computer-readable medium" and "computer-readable media" are entirely limited to tangible physical objects that store information in a computer-readable form. These terms do not include any wireless signals, wired download signals, and any other transient signals.

[0074] To provide interaction with a user, embodiments of the subject matter described in this specification may be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user, and a keyboard and pointing device (e.g., a mouse or trackball), through which the user can provide input to the computer. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including acoustic, voice, or tactile input. In addition, the computer may interact with the user by sending documents to and receiving documents from a device used by the user; for example, by sending a web page to a web browser on a user's client device in response to a request received from the web browser.

[0075] Embodiments of the subject matter described in this specification may be implemented in a computing system that includes a back-end component (e.g., as a data server) or includes a middleware component (e.g., an application server) or includes a front-end component (e.g., a client computer with a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described in this specification), or any combination of one or more such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication, such as a communication network. Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), interconnected networks (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).

[0076] A computing system may include a client and a server. The client and the server are typically remote from each other and may interact via a communication network. The relationship of the client and the server is due to the computer programs running on the respective computers, and have a client-server relationship with each other. In some embodiments, the server sends data (e.g., an HTML page) to a client device (e.g., in order to display data to a user interacting with the client device and to receive user input from a user interacting with the client device). Data generated at the client device (e.g., the result of a user interaction) may be received from the client device at the server.

[0077] It will be appreciated by those skilled in the art that the various illustrative blocks, modules, elements, parts, methods and algorithms described herein can be implemented as electronic hardware, computer software or a combination of the two. In order to illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, parts, methods and algorithms have been generally described above according to their functions. Such functions are implemented as hardware or software depending on the specific application and design restrictions imposed on the entire system. For each specific application, the described functions can be implemented in different ways. Various components and blocks can be arranged differently (e.g., arranged in different orders, or divided in different ways), without departing from the scope of the subject technology.

[0078] The term website as used herein may include any aspect of a website, including one or more web pages, one or more servers for hosting or storing web-related content, etc. Therefore, the term website may be used interchangeably with the terms web page and server. The predicates "configured to," "operable to," and "programmed to" do not imply any specific tangible or intangible modification of the subject matter, but are intended to be used interchangeably. For example, a processor configured to monitor and control an operation or component may also mean a processor programmed to monitor and control an operation or a processor operable to monitor and control an operation. Similarly, a processor configured to execute code may be interpreted as a processor programmed to execute code or operable to execute code.

[0079] It should be understood that any particular order or hierarchy of the blocks in the disclosed process method is an illustration of an exemplary scheme. Based on design or implementation preferences, it should be understood that the particular order or hierarchy of the blocks in the process can be rearranged, or all of the blocks shown are executed. In some embodiments, any block can be executed simultaneously.

[0080] The present disclosure is provided to allow any person skilled in the art to implement the various aspects described herein. The present disclosure provides various examples of the present technology, and the present technology is not limited to these examples. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applicable to other aspects.

[0081] Reference to an element in the singular is not intended to mean "one and only one" unless specifically so described, but rather "one or more". Unless specifically stated otherwise, the term "some" means one or more. Pronouns in the masculine gender (e.g., his) include the feminine and neuter gender (e.g., her and its) and vice versa. Headings and subheadings, if any, are for convenience only and do not limit the invention.

[0082] The word "exemplary" is used herein to mean "serving as an example or illustration." Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs. In one aspect, the various alternative configurations and operations described herein may be considered to be at least equivalent.

[0083] As used herein, the phrase "at least one of" following a list of items (with the term "or" separating any of the items) modifies the list as a whole, rather than each item in the list. The phrase "at least one of" does not require selection of at least one item; rather, the phrase allows for a meaning that includes at least one of any of the items, and / or at least one of any combination of the items, and / or at least one of each of the items. For example, the phrase "at least one of A, B, or C" may mean: only A, only B, or only C; or any combination of A, B, and C.

[0084] Phrases such as "aspects" do not imply that such aspects are essential to the present technology or that such aspects apply to all configurations of the present technology. The disclosure related to an aspect may apply to all configurations, or one or more configurations. An aspect may provide one or more examples. Phrases such as "an aspect" may refer to one or more aspects, and vice versa. Phrases such as "embodiments" do not imply that such embodiments are essential to the present technology or that such embodiments apply to all configurations of the present technology. The disclosure related to an embodiment may apply to all embodiments, or one or more embodiments. An embodiment may provide one or more examples. Phrases such as "an embodiment" may refer to one or more embodiments, and vice versa. Phrases such as "constructions" do not imply that such constructions are essential to the present technology or that such constructions apply to all configurations of the present technology. The disclosure related to a construction may apply to all configurations, or one or more configurations. A construction may provide one or more examples. Phrases such as "constructions" may refer to one or more constructions, and vice versa.

[0085] In one aspect, unless otherwise indicated, all measurements, values, ratings, positions, sizes, dimensions and other specifications given in this specification (including in the following claims) are approximate and not exact. In one aspect, they are intended to have a reasonable range consistent with the functions to which they are related and the customary practices in the field to which they belong.

[0086] It should be understood that the specific order or hierarchy of steps, operations or processes disclosed is an illustration of an exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of steps, operations or processes can be rearranged. Some of the steps, operations or processes can be performed simultaneously. Some or all of the steps, operations or processes can be performed automatically without user intervention. The accompanying method claims (if any) set forth the elements of the various steps, operations or processes in a sample order and are not intended to be limited to the specific order or hierarchy set forth.

[0087] All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or will become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included in the claims. In addition, nothing disclosed herein is intended to be contributed to the public, regardless of whether such disclosure is expressly recited in the claims. The claims shall not be interpreted under the provisions of 35 U.S.C. §112(f) unless the element is expressly recited using the phrase "device for XX" or, in the case of a method claim, the element is recited using the phrase "step for XX." Further, to the extent that the terms "including," "having," and the like are used, such terms are intended to be inclusive, in a manner similar to the term "comprising," as interpreted when "comprising" is adopted as a transitional word in a claim.

[0088] The title, background technology, summary of the invention, description of the drawings and abstract of the present disclosure are incorporated into the present disclosure and are provided as illustrative examples of the present disclosure, not as restrictive descriptions. It is submitted with the understanding that they will not be used to limit the scope or meaning of the claims. In addition, in the specific embodiments, it can be seen that the description provides illustrative examples and various features are combined together in various embodiments for the purpose of making the present disclosure smooth. This method of disclosure should not be interpreted as reflecting an intention that the claimed subject matter requires more features than those explicitly listed in each claim. On the contrary, as reflected in the following claims, the creative subject matter is in less than all the features of a single disclosed structure or operation. The following claims are thus incorporated into the specific embodiments, and each claim exists independently as a subject matter claimed separately.

[0089] The claims are not intended to be limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims and encompassing all legal equivalents. Nevertheless, no claim is intended to encompass subject matter that does not satisfy the requirements of 35 USC §101, 102, or 103, nor should they be interpreted in such a manner.

Claims

1. A modular power and connectivity assembly comprising: a housing including a cavity configured to receive a device coupling member; a power assembly configured to provide power to the infusion device; a communication assembly configured to provide communication with the infusion set; and a wiring harness assembly comprising a base to which the infusion set is coupled and an extension member coupling the base to the housing, wherein the modular power and connection assembly is configured to be reusable, and wherein the modular power and connection assembly is configured to be removably coupled to the infusion set, Wherein the housing includes a recess configured to receive a portion of the tube, and wherein the recess is a depressed portion provided in a surface of the housing.

2. The modular power and connection assembly of claim 1, further comprising at least one indicator configured to visually indicate a level of power stored in the power assembly.

3. The modular power and connectivity assembly of claim 1, wherein: The cavity is sized and dimensioned to receive the infusion set.

4. The modular power and connection assembly of claim 3, wherein: The infusion set comprises the set coupling member, and the cavity comprises a cavity coupling member.

5. The modular power and connectivity assembly of claim 4, wherein: The device coupling member and the cavity coupling member are opposing connectors configured to physically mate with each other.

6. The modular power and connectivity assembly of claim 4, wherein: The device coupling member and the cavity coupling member are magnet assemblies configured to magnetically attract each other.

7. The modular power and connectivity assembly of claim 4, wherein: The device coupling member and the cavity coupling member are wireless components configured to wirelessly connect to each other.

8. The modular power and connectivity assembly of claim 1, wherein: The wiring harness assembly includes the device coupling member, and wherein the cavity includes a cavity coupling member configured to physically mate with the device coupling member.

9. The modular power and connectivity assembly of claim 1, wherein: The base is configured to physically mate with the infusion set.

10. The modular power and connectivity assembly of claim 1, wherein: The base is configured to magnetically mate with the infusion set.

11. The modular power and connectivity assembly of claim 1 , wherein: The base is configured to wirelessly connect to the infusion set.

12. The modular power and connectivity assembly of claim 1, wherein: The power assembly includes one or more rechargeable batteries.

13. A power and connection system comprising: One or more reusable modular power and connection assemblies according to any one of claims 1-12; and A connection hub is configured to transmit and receive electronic signals to and from the one or more reusable modular power and connection components.

14. The power and connection system of claim 13, further comprising a cloud interface configured to transmit and receive electronic signals to and from the connection hub.

15. The power and connection system of claim 14, further comprising a mobile interface configured to transmit electronic signals to and receive electronic signals from the cloud interface, wherein the mobile interface is disposed on a portable electronic device.

16. The power and connection system of claim 13, further comprising a charging station configured to charge the one or more reusable modular power and connection assemblies.

17. The power and connection system of claim 16, wherein: The charging station includes a rechargeable source of electrical power, and wherein the charging station is configured to be portable.

18. A method of operating a power and connection system according to any one of claims 13 to 17, the method comprising: removably coupling the modular power and connection assembly to an infusion set; transmitting power from said modular power and connectivity assembly to said infusion set; providing a communication link between the modular power and connectivity assembly and the infusion set; transmitting data from said infusion set to said modular power and connectivity assembly; transmitting at least a portion of the data from the modular power and connectivity assembly to the connectivity hub; as well as The portion of the data is transmitted from the connectivity hub to a cloud interface of a healthcare network.

Images