Modular Power and Connectivity System for Infusion Devices

Abstract

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

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 62 / 949,305, entitled "MODULAR POWER AND CONNECTIVITY SYSTEM FOR INFUSION DEVICES," filed December 17, 2019, the disclosure of which is incorporated herein by reference in its entirety for all purposes.

[0002] TECHNICAL FIELD The present disclosure relates generally to power and connectivity for devices, and more particularly to a modular system for power and connectivity for infusion devices. [Background technology]

[0003] Infusion devices are used in the medical field for intravenous (IV) applications. Typical infusion devices require independent power and connectivity to provide the desired infusion outcome. Typical infusion systems require a physical connection between each infusion device and the existing infrastructure and / or each device must contain its own power and connectivity hardware, thus increasing costs and / or creating undesirable trade-offs 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, connectivity) are contained within the device. However, infusion set devices (e.g., IV line components) are generally disposable, single-use devices, making disposal of costly components undesirable.

[0004] Therefore, it is desirable to provide a non-disposable modular power and connectivity assembly for a disposable infusion device. Summary of the Invention [Means for solving the problem]

[0005] One or more embodiments provide a modular power and connectivity assembly that 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 communications assembly configured to provide communications with the infusion device. The modular power and connectivity assembly is configured to be reusable and to be removably coupled to the infusion device.

[0006] One or more embodiments provide a power and connectivity system. The power and connectivity system includes one or more reusable modular power and connectivity assemblies. Each reusable modular power and connectivity assembly includes a housing including a cavity configured to receive a device coupling member, a power assembly configured to provide power to the infusion device, and a communication assembly configured to provide communication with the infusion device. Each modular power and connectivity assembly is configured to be removably coupled to the infusion device. The power and connectivity system also includes a connectivity hub configured to transmit electronic signals to and receive electronic signals from the one or more reusable modular power and connectivity assemblies.

[0007] One or more embodiments provide a method of operating a modular power and connectivity system, the method including the steps of 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 communications 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 a portion of the data from the connectivity hub to a cloud interface of a healthcare network.

[0008] The foregoing and other features, aspects, and advantages of the disclosed embodiments will become more apparent from the following detailed description and accompanying drawings.

[0009] The accompanying drawings are included to provide a further understanding of the present disclosure, and are incorporated in and constitute a part of this specification, illustrating embodiments of the present disclosure, and together with the description, serve to explain the principles of the disclosure. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a schematic diagram of an exemplary infusion set with a typical infusion device. [Figure 2] FIG. 1 is a perspective view of a modular power and connectivity assembly in accordance with an aspect of the subject technology. [Figure 3] FIG. 1 is a perspective view of a modular power and connectivity assembly in accordance with an aspect of the subject technology. [Figure 4] FIG. 1 is a perspective view of a charging station in accordance with aspects of the subject technology. [Figure 5] FIG. 1 illustrates an example of a healthcare institution network in accordance with aspects of the subject technology. [Figure 6]1 illustrates an example of a modular power and connectivity assembly in communication with a user device having an exemplary graphical user interface, in accordance with aspects of the subject technology. [Figure 7] FIG. 1 illustrates an example of an in-house patient care system for a healthcare institution, in accordance with aspects of the subject technology. [Figure 8] 1 is a conceptual diagram illustrating an exemplary electronic system for communication and control of a modular power and connectivity assembly, in accordance with an aspect of the subject technology. [Figure 9] FIG. 1 illustrates a method of operating a modular power and connectivity system. DETAILED DESCRIPTION OF THE INVENTION

[0011] The detailed description set forth below describes various configurations of the subject technology and is not intended to represent the only configurations in which the subject technology may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the subject technology. Accordingly, dimensions are provided as non-limiting examples with respect to particular embodiments. However, it will be apparent to those skilled in the art that the subject technology may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring the concepts of the subject technology.

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

[0013] The subject technology provides a modular approach with independent power and connectivity. For example, a non-disposable, rechargeable power supply enables the functionality of disposable peripheral infusion devices (e.g., sensors, pumping elements). The modular design offers reduced total device cost, reduces the environmental impact of electronic waste, prevents device misconnection, and prevents cybersecurity risks through proprietary interfaces. The modular approach further lowers costs to the consumer by separating high-cost, non-disposable components (e.g., batteries, communication interfaces) from lower-cost, disposable components (e.g., sensors, pumping elements).

[0014] The present disclosure relates to infusion device assemblies, such as non-disposable modular power and connectivity assemblies for infusion devices. The modular power and connectivity assemblies are capable of providing power and connectivity to any desired infusion device (e.g., sensors, pumps). Typically, a standard infusion set 10 is used to infuse fluids into a subject. An example of a standard infusion set 10 is shown in FIG. 1.

[0015] The infusion set 10 includes a piercing spike 20, which can be either a sharp spike for piercing a rubber stopper or a rounded, blunt spike for insertion into a bag (not shown). The spike 20 contains one channel for fluid and, optionally, a second channel for venting. A vent 21 is typically present near the piercing spike 20 to allow air to flow into the drop chamber 22. The vent 21 can be provided with a bacterial filter to prevent bacteria from entering the device.

[0016] The drop chamber 22 has a drop generator 23 at the top of the drop chamber 22, which creates drops of a specific size. Drops from the drop generator 23 fall into the drop chamber 22, causing the drop chamber 22 to be partially filled with liquid. This prevents air bubbles from entering the connector tube 24, which would be harmful to the patient. A particle filter (not shown) may be provided in the lower aperture of the drop chamber 22.

[0017] A connector tube 24 connects the drop chamber 22 to the patient. The connector tube 24 is typically about 150 cm long and may be manufactured from PVC. The tube 24 is shown shortened in FIG. 1 for clarity. The connector tube 24 typically has a continuous diameter throughout its length.

[0018] At the end of connector tube 24 is a luer fitting 25 that is standardized for connection to all other pieces of equipment with a standard luer cone. Those skilled in the art will recognize that luer fitting 25 may be attached to an infusion pump or hypodermic needle (not shown) for infusing medical fluids into a patient's circulatory system (e.g., into a vein).

[0019] A roller clamp 26 for controlling the flow rate of fluid through the connector tube 24 is located between the drop chamber 22 and the luer fitting 25 and engaged with the connector tube 24. Also, an infusion device 28 (e.g., a pressure sensor) is located between the drop chamber 22 and the luer fitting 25 and engaged with the connector tube 24. The infusion device 28 typically requires connection to a hardwired power source (e.g., a power cable / wire connection between the infusion device 28 and an electrical outlet, etc.). Communication to / from the infusion device 28 typically requires connection to a hardware communication device (e.g., a communication cable / wire connection between the infusion device 28 and a router, etc.).

[0020] Referring to FIG. 2 , a modular power and connectivity assembly 100 for an infusion device is shown. The modular power and connectivity assembly 100 includes a housing 105 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 a tube 24. The housing 105 can also be sized and configured to receive tubing (e.g., a connector tube 24, etc.). For example, the housing 105 can include a tube recess 107 sized and configured to receive the tube 24, which can help maintain the tube 24 connected to the infusion device 110, help prevent kinking or displacement of the tube 24, and / or assist in connecting the infusion device 110 to the modular power and connectivity assembly 100.

[0021] The modular power and connectivity assembly 100 may be configured as a non-disposable device that can be used repeatedly to provide power and / or communications for multiple disposable infusion sets 10 and / or disposable infusion devices 110. For example, the modular power and connectivity assembly 100 may be used to provide power and communications to a first disposable infusion device 110, after which the first disposable infusion device 110 is discarded and the modular power and connectivity assembly 100 may be used to provide power and communications to a second disposable infusion device 110. The second disposable infusion device 110 may be used with the same infusion set with which the first disposable infusion device 110 was used, e.g., to replace the first pressure sensor with a second pressure sensor if the first pressure sensor becomes faulty 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 may be used with a different infusion set (eg, with the same patient in a different infusion process or with a new patient).

[0022] In use, the infusion device 110 can be on or attached to an infusion line (e.g., tubing 24, etc.). For example, FIG. 2 shows the infusion device 110 with a fluid inlet 112 connected to a first tube 24a and a fluid outlet 114 connected to a second tube 24b. Here, fluid can flow in through the first tube 24a, through the infusion device 110 (e.g., pressure sensor, pumping element), and out through the second tube 24b, allowing the infusion device 110 to observe or monitor aspects of the fluid (e.g., fluid pressure, fluid color, presence of gas bubbles) and / or act on the fluid (e.g., pump the fluid, filter the fluid, mix gas / other fluids into the fluid) as it passes through.

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

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

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

[0026] 3, the modular power and connectivity assembly 100 can include a harness assembly 120. The harness assembly 120 can include a base 122 and an extension member 124. Here, the infusion device 110 can be coupled to the base 122 (e.g., a pin, a magnet), and the extension member 124 can couple the base 122 to the housing 105. The extension member 124 can include power and / or communication wires to provide power and / or communication transmission between the modular power and connectivity assembly 100 and the base 122. The base 122 can be configured to provide power to the infusion device 110 and / or to provide communication to / from the infusion device 110 (e.g., physical transmission or wireless transmission), as discussed above. In another example, the extension member 124 may not provide a physical power / communications connection (e.g., formed from a non-conductive material), and power / communications may be transmitted wirelessly between the housing 105 and the base 122, and further between the base 122 and the infusion device 110. In yet another example, power / communications may be transmitted wirelessly directly between the housing 105 and the infusion device 110.

[0027] In cases where the infusion device 110 is not sized to fit within the cavity 109 (e.g., if the infusion device 110 is larger than the cavity 109 or if the infusion device 110 requires connection to other tubing and / or devices), the modular power and connectivity assembly 100 may be configured to use the harness assembly 120. As another example, the modular power and connectivity assembly 100 may be configured to use the harness assembly 120 for most or all operations (e.g., even if the infusion device 110 is sized to fit within the cavity 109). The harness assembly 120 may be configured to removably connect to the modular power and connectivity assembly 100, such that the modular power and connectivity assembly 100 may be used in any of the configurations discussed above. As another example, the harness assembly 120 may be integrally formed with the housing 105.

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

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

[0030] Charging station 150 may be hardwired to a power source (e.g., a building's electrical wiring) such that charging station 150 is typically permanently positioned at a particular location. Charging station 150 may 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).

[0031] 5, the subject technology may also include a connectivity hub 200 configured to interconnect communication and / or control between a modular power and connectivity assembly 100 coupled to an infusion device 110 and a cloud interface 250 of an institutional patient care system of a healthcare institution having a user device 260. For example, the connectivity 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 an infusion device 110 coupled to the modular power and connectivity assembly 100.

[0032] 5 and 6, the modular power and connectivity assembly 100 can transmit information (e.g., sensor information) from the infusion device 110 through the connectivity hub 200 to the cloud interface 250 and then to a specific user device 260 (e.g., a healthcare professional's smartphone). Thus, the healthcare professional can remotely monitor the subject's infusion process. As another example, the information flow can be reversed, where the healthcare professional can input an adjustment (e.g., change the pump speed) on the user device 260, which is then transmitted from the cloud interface 250 to the connectivity hub 200, to the modular power and connectivity assembly 100, and then to the infusion device 110 (e.g., the pump element). Thus, the healthcare professional can remotely control the subject's infusion process. In one or more aspects of the subject technology, Bluetooth® connectivity may be provided between the modular power and connectivity assembly 100 and the connectivity hub 200, WiFi connectivity may be provided between the connectivity hub 200 and the cloud interface 250, and the mobile interface 270 may provide information connectivity between the cloud interface 250 and the user device 260.

[0033] FIG. 7 illustrates an example of an internal patient care system 300 of a healthcare institution in accordance with aspects of the subject technology. In FIG. 7, patient care devices (or generally, "medical devices") 312 are connected to a healthcare facility network 310. The term patient care device (or "patient care device (PCD)") may be used interchangeably with the term patient care unit (or "patient care unit (PCU)"), either of which can include various ancillary medical devices, such as, for example, infusion pumps, vital signs monitors, medication dispensing devices (e.g., cabinets, totes), medication preparation devices, automated dispensing devices, modules coupled with one of the foregoing (e.g., a syringe pump module configured to attach to an infusion pump), or other similar devices. Each medical device 312 is connected to the internal healthcare network 310 by a transmission channel 331. The transmission channel 331 may be any wired or wireless transmission channel, for example, an 802.11 wireless local area network (LAN). In some implementations, network 310 also includes computer systems located in various departments throughout the healthcare facility. For example, network 310 of FIG. 7 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 described further below, network 310 can include discrete sub-networks. In the illustrated example, network 310 includes device network 340 over which patient care devices 312 (and other devices) communicate in accordance with normal operation.

[0034] Additionally, the institutional patient care system 300 may incorporate a separate information system server 330, the functionality of which will be described in more detail below. Moreover, although the information system server 330 is shown as a separate server, the functionality and programming of the information system server 330 may be incorporated into another computer if so desired by engineers designing the institutional information system. The institutional patient care system 300 may further include one or more device terminals 332 for connecting to and communicating with the information system server 330. The device terminals 332 may include personal computers, personal data assistants, mobile devices, such as laptop computers, tablet computers, augmented reality devices, or smartphones, configured with software for communicating with the information system server 330 over the network 310.

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

[0036] In various implementations, user interface device 354 is a touchscreen for displaying information to a user and allowing the user to input information by touching defined areas of the screen. Additionally or alternatively, user interface device 354 can include any means for displaying and inputting information (e.g., a monitor, printer, keyboard, softkeys, mouse, trackball, and / or light pen, etc.). Data input device 360 can be a barcode reader capable of scanning and interpreting data printed in barcode format. Additionally or alternatively, data input device 360 can be any device for inputting coded data into a computer, such as a device for reading magnetic strips, a radio frequency identification (RFID) device (whereby digital data (defined below) encoded in an RFID tag or smart label is acquired via radio waves by reader 360), a PCMCIA smart card, a radio frequency card, a memory stick, a CD, a DVD, or any other analog or digital storage medium. Other examples of data input device 60 include a voice-activated or recognized device or a portable personal digital assistant (PDA). Depending on the type of interface device used, user interface device 354 and data input device 360 can be the same device.

[0037] 7 as being disposed within interface unit 314, it will be appreciated that data input device 360 can be integrated into pharmacy system 334 or can be externally located and communicate with pharmacy system 334 through an RS-232 serial interface or any other suitable communication means. Auxiliary interface 362 can be an RS-232 communication interface, however, any other means for communicating with peripheral devices (e.g., printers, patient monitors, infusion pumps, or other medical devices) can be used without departing from the subject technology. Additionally, data input device 360 can be a separate functional module (e.g., modules 316, 318, 320, and 322, etc.) and can be configured to communicate with control unit 314 (or any other system over a network) using appropriate programming and communication protocols.

[0038] The network connection 352 can be a wired or wireless connection (e.g., via Ethernet, WiFi, BLUETOOTH, an Integrated Services Digital Network (ISDN) connection, a Digital Subscriber Line (DSL) modem, or a cable modem, etc.) Any direct or indirect network connection can be used, including, but not limited to, a telephone modem, an MIB system, an RS232 interface, an auxiliary interface, an optical link, an infrared link, a radio frequency link, a microwave link, or a WLANs connection, or other wireless connection.

[0039] Functional modules 316, 318, 320, and 322 can be any device for providing care to a patient or monitoring a patient condition. As shown in FIG. 7 , at least one of functional modules 316, 318, 320, and 322 can be an infusion pump module, such as an intravenous infusion pump for delivering medication or other fluids to a patient. For purposes of this discussion, functional module 316 is an infusion pump module. Each of functional modules 318, 320, and 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. 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.

[0040] Each functional module 316, 318, 320, 322 communicates directly or indirectly with the interface unit 314, which provides overall monitoring and control of the device 312. The functional modules 316, 318, 320, 322 may be physically and electronically connected in a serial manner to one or both ends of the interface unit 314, as shown in FIG. 7 or as described in detail in Eggers et al. However, it will be recognized that there are other means for connecting the functional modules with the interface unit that can be utilized without departing from the subject technology. It will also be recognized that devices such as pumps or patient monitoring devices that provide sufficient programmability and connectivity may be capable of operating as standalone devices and communicating directly with a network without being connected through a separate interface or control unit 314. As described above, additional medical or peripheral devices may be connected to the patient care device 312 through one or more auxiliary interfaces 362.

[0041] Each functional module 316, 318, 320, 322 can include module-specific components 376, a microprocessor 370, volatile memory 372 for storing information, and non-volatile memory 374. While four functional modules are shown in FIG. 7, it should be noted that any number of devices may be directly or indirectly connected to the central control unit 314. The number and types of functional modules described herein are intended for illustrative purposes and in no way limit the scope of the subject technology. Module-specific components 376 include any components necessary for the operation of a particular module (e.g., a pumping mechanism for the infusion pump module 316, etc.).

[0042] Although each functional module may be capable of at least some level 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.

[0043] The patient care device 312 can operate in several different modes (or personalities), each defined by a configuration database. The configuration database can be a database on the patient care device's 312 internal storage unit 356 or an external database 337. A particular configuration database is selected based at least in part on patient-specific information (e.g., device or patient location, age, physical characteristics, or medical characteristics). Medical characteristics include, but are not limited to, patient diagnosis, treatment prescription, medical history, medical records, patient care provider identification, physiological characteristics, or psychological characteristics. As used herein, patient-specific information also includes care provider information (e.g., physician identification) or the location of the patient care device 260 within the hospital or hospital computer network. Patient care information may be entered through network connection 352 or through any of input / interface devices 354, 360, or 362 and can originate from anywhere within network 310 (e.g., from a pharmacy server, an admissions server, a laboratory server, etc.).

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

[0045] Data to and from various data sources can be converted into network-compatible data by existing technology, and the movement of information between medical devices and the network can be accomplished by various means. For example, the patient care devices 312 and the network 310 can communicate through automated interaction, manual interaction, or a combination of both automated and manual interaction. Automated interaction can be continuous or intermittent and can occur through a direct network connection 354 (as shown in FIG. 7) or through an RS232 link, an MIB system, an RF link such as BLUETOOTH®, an IR link, WLANs, a digital cable system, a telephone modem, or other wired or wireless communication means. Manual interaction between the patient care devices 312 and the network 310 includes physically transferring data between the systems, either 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. The communication means in various embodiments is bidirectional, with access to data from as many points as possible of distributed data sources. Decision making can occur at various locations within the network 310. For example, but not limited to, it can occur within the HIS server 330, decision support 348, remote data server 349, hospital department or unit station 346, or within the patient care device 312 itself.

[0046] All direct communication with medical devices operating on a network in accordance with the subject technology may be conducted through an information system server 30 (known as a remote data server (RDS)). According to aspects of the subject technology, a network interface module built into a medical device (e.g., an infusion pump or a vital signs 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 network-connected medical devices with NIMs and maintain open communications.

[0047] 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 administration of medication during patient transport or remote medication administration (e.g., outside of a medical facility, such as in the user's home). U.S. Patent No. 7,163,381 to Barak describes a pump suitable for ambulatory care and that can be modified to help provide safe administration during mobile events. The disclosure of U.S. Patent No. 7,163,381 is incorporated by reference in its entirety.

[0048] FIG. 8 is a conceptual diagram illustrating an exemplary electronic system 400 for powering, communicating, monitoring, and controlling a medical device (e.g., infusion device 110) in accordance with aspects of the subject technology. Electronic system 400 can be a computing device for execution of software associated with one or more components and processes provided by FIGS. 1-7 , including, but not limited to, information system server 330, device terminal 332, computing hardware within patient care device 312, or external database 337. Electronic system 400, in combination with the disclosure relating to FIGS. 1-7 , can be representative. In this regard, electronic system 400 can be a personal computer or mobile device, such as a smartphone, tablet computer, laptop computer, PDA, augmented reality device, wearable (e.g., watch, band, or glasses), or the like, or a combination thereof, or other touchscreen or television with one or more processors embedded therein or coupled thereto, or any other type of computer-related electronic device with network connectivity.

[0049] The electronic system 400 can include various types of computer-readable media and interfaces for various other types of computer-readable media. In the illustrated example, 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 implementations, the electronic system 400 can include or be integrated with other computing devices or circuits for operation of the various components and processes previously described.

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

[0051] From these various memory units, the processing unit 412 retrieves instructions to execute and data to process in order to perform the processes of the subject disclosure. The processing unit can be a single processor or a multi-core processor in different implementations.

[0052] The ROM 410 stores static data and instructions needed by the processing unit 412 and other modules of the electronic system. The permanent storage device 402, on the other hand, is a readable and writable memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic system 400 is off. Some implementations of the subject disclosure use a mass storage device (e.g., a magnetic or optical disk and its corresponding disk drive) as the permanent storage device 402.

[0053] Other implementations use removable storage devices (e.g., floppy disks, flash drives, and their corresponding disk drives) as the permanent storage device 402. Like the permanent storage device 402, the system memory 404 is a read-and-write memory device. However, unlike the storage device 402, the system memory 404 is a volatile read-and-write memory (e.g., random access memory). The system memory 404 stores some of the instructions and data the processor needs during execution. In some implementations, the processes of the subject disclosure are stored in the system memory 404, the permanent storage device 402, and / or the ROM 410. From these various memory units, the processing unit 412 retrieves instructions to execute and data to process in order to perform the processes of some implementations.

[0054] The bus 408 also connects 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 by the input device interface 414 include, for example, an alphanumeric keyboard and a pointing device (also called a "cursor control device"). The output device interface 406 enables, for example, the display of images generated by the electronic system 400. Output devices used by the output device interface 406 include, for example, printers and display devices such as cathode ray tubes (CRTs) or liquid crystal displays (LCDs). Some implementations include devices that function as both input and output devices (e.g., touch screens, etc.).

[0055] 8, bus 408 couples electronic system 400 to a network (not shown) through network interface 416. Network interface 416 may include, for example, a wireless access point (e.g., Bluetooth or WiFi) or radio circuitry for connecting to a wireless access point. Network interface 416 may also include hardware (e.g., Ethernet hardware) for connecting a computer to a portion of a network of computers (e.g., a local area network ("LAN"), a wide area network ("WAN"), a wireless LAN, or an intranet), or to a network of networks (e.g., the Internet). Any or all of the components of electronic system 400 may be used in connection with the subject disclosure.

[0056] 9, a method 500 of operating the modular power and connectivity assembly 100 is provided. In step 510, the modular power and connectivity assembly 100 is coupled to an infusion device 110. For example, the infusion device 110, connected to tubing 24, may be inserted into the housing 105 or connected to the base 122 of the harness assembly 120.

[0057] The modular power and connectivity assembly 100 provides power to the infusion device 110 at step 520. For example, the modular power and connectivity assembly 100 can transfer power through a physical connection (e.g., pins, cables) between the housing 105 and the infusion device 110 or through wireless power transfer between the modular power and connectivity assembly 100 and the infusion device 110.

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

[0059] In step 540, modular power and connectivity assembly 100 communicates with the healthcare network. For example, modular power and connectivity assembly 100 can transmit received data or sensor information to connectivity hub 200, which can then transmit it to cloud interface 250 and receive it from user interface 260. Thus, user interface 260 (e.g., mobile interface 270, etc.) can provide data or information from infusion device 110 to a user (e.g., a healthcare worker). As another example, modular power and connectivity assembly 100 can receive control information from connectivity hub 200, which can be received from cloud interface 250, which can be received from user interface 260. Thus, user interface 260 (e.g., mobile interface 270, etc.) can provide control information from the healthcare worker to infusion device 110.

[0060] As used herein, a “user interface” (also referred to as an interactive user interface, graphical user interface, or UI) can refer to a network-based interface that includes data fields 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 can include dials, buttons, icons, selectable areas, or other perceptible indicators presented via the UI that, when interacted with (e.g., clicked, touched, selected, etc.), initiate an exchange of data for the device presenting the UI. The UI can be implemented in whole or in part using technologies such as Hypertext Markup Language (HTML), FLASH®, JAVA®, .NET™, web services, rich site summaries (RSS), or the like. In some implementations, the UI can be included in a standalone client (e.g., thick client, fat client) configured to communicate (e.g., send or receive data) according to one or more of the described aspects. The communication can be between the medical device or a server in communication with it.

[0061] The functions described above may be implemented in computer software, firmware, or hardware. The techniques may be implemented using one or more computer program products. The programmable processor and computer may be included in or packaged as a mobile device. The processes and logic flows may be implemented by one or more programmable processors and by one or more programmable logic circuits. General-purpose and special-purpose computing and storage devices may be interconnected through a communications network.

[0062] Some implementations include electronic components such as a microprocessor, storage, and memory (also referred to as a computer-readable storage medium, machine-readable medium, or machine-readable storage medium) that store computer program instructions in a machine-readable or computer-readable medium. Some examples of such computer-readable media include RAM, ROM, read-only compact discs (CD-ROMs), recordable compact discs (CD-Rs), rewritable compact discs (CD-RWs), read-only digital versatile discs (e.g., DVD-ROMs, dual-layer DVD-ROMs), various recordable / rewritable DVDs (e.g., DVD-RAMs, DVD-RWs, DVD+RWs, etc.), flash memory (e.g., SD cards, miniSD cards, microSD cards, etc.), magnetic and / or solid-state hard drives, read-only and recordable Blu-Ray® discs, ultra-density optical discs, any other optical or magnetic medium, and floppy disks. The computer-readable medium can store a computer program executable by at least one processing unit and including a set of instructions for performing various operations. Examples of computer programs or computer code include machine code (e.g., as produced by a compiler) and files (including high-level code that is executed by a computer, electronic component, or microprocessor using an interpreter).

[0063] Although the above discussion primarily refers to microprocessors or multi-core processors executing software, some implementations are performed by one or more integrated circuits (e.g., application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs)). In some implementations, such integrated circuits execute instructions stored on the circuit itself.

[0064] As used herein and in any claims of this application, the terms "computer," "server," "processor," and "memory" all refer to electronic or other technological devices. These terms exclude people or groups of people. For purposes of this specification, the terms "display" or "displaying" mean displaying on an electronic device. As used herein and in any claims of this application, the terms "computer-readable medium" and "computer-readable mediums" are strictly limited to tangible, physical objects that store information in a form readable by a computer. These terms exclude any wireless signals, wired download signals, and any other ephemeral signals.

[0065] To provide for interaction with a user, implementations of the subject matter described herein 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 a user, as well as a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other types of devices may be used to provide for interaction with a user as well. For example, feedback provided to a user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback), and input from a user can be received in any form (including acoustic, voice, or tactile input). Additionally, a computer may interact with a user by sending documents to and receiving documents from a device used by the user (e.g., by sending a web page to a web browser on the user's client device in response to a request received from the web browser).

[0066] Embodiments of the subject matter described herein may be implemented within a computing system that includes a back-end component, e.g., a data server, or a middleware component (e.g., an application server), or a front-end component (e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described herein), 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 (e.g., a communication network). Examples of communication networks include local area networks (“LANs”) and wide area networks (“WANs”), internetworks (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).

[0067] A computing system may include clients and servers. Clients and servers are generally remote from each other and may interact through a communication network. The relationship of client and server arises due to computer programs running on the respective computers and having a client-server relationship to each other. In some embodiments, a server transmits data (e.g., HTML pages) to client devices (e.g., for the purpose of displaying the data to a user interacting with the client device and receiving user input from the user). Data generated at the client device (e.g., the result of a user interaction) may be received from the client device at the server.

[0068] Those skilled in the art will recognize that the various illustrative blocks, modules, elements, components, methods, and algorithms described herein may be implemented as electronic hardware, computer software, or a combination of both. To illustrate this interchangeability of hardware and software, the various illustrative blocks, modules, elements, components, methods, and algorithms have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. The described functionality may be implemented in various ways for each particular application. The various components and blocks may be arranged differently (e.g., placed in a different order or partitioned in a different manner), all without departing from the scope of the subject technology.

[0069] As used herein, the term website can include any aspect of a website, including one or more web pages, one or more servers used to host or store web-related content, etc. Thus, the term website can be used interchangeably with the terms web page and server. The terms "configured to," "operable to," and "programmed to" do not imply any particular tangible or intangible modification of the subject matter, but rather are intended to be used interchangeably. For example, a processor configured to monitor and control operations or components also means that the processor is programmed to monitor and control operations or that the processor is operable to monitor and control operations. Similarly, a processor configured to execute code can be interpreted as a processor programmed to execute code or operable to execute code.

[0070] It is understood that any particular order or hierarchy of blocks in the disclosed process methods is an illustration of an example approach. Based on design or implementation preferences, it is understood that the particular order or hierarchy of blocks in the processes may be rearranged, or all of the illustrated blocks may be implemented. In some implementations, any of the blocks may be implemented simultaneously.

[0071] This disclosure is provided to enable any person skilled in the art to practice the various aspects described herein. This disclosure provides various examples of the subject technology, and the subject technology is not limited to these examples. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects.

[0072] Reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more." The term "some" refers to "one or more" unless specifically stated otherwise. Masculine pronouns (e.g., his) include feminine and neuter (e.g., "her" and "it"), and vice versa. Headings and subheadings, if any, are used merely for convenience and do not limit the invention.

[0073] 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, various alternative configurations and operations described herein may be considered at least equivalent.

[0074] As used herein, the phrase "at least one of" preceding a list of items (with the word "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 the selection of at least one item. Rather, the phrase allows for a meaning including at least one of any one of the items, and / or at least one of any combination of the items, and / or at least one of each of the items. By way of example, the phrase "at least one of A, B, or C" can refer to A only, B only, or C only; or any combination of A, B, and C.

[0075] The use of phrases such as "aspects" does not imply that such aspect is essential to the subject technology or that such aspect applies to all configurations of the subject technology. Disclosure of an aspect may apply to all configurations, or to one or more configurations. An aspect may provide one or more examples. A phrase such as an aspect may refer to one or more aspects, and vice versa. A phrase such as "embodiment" does not imply that such embodiment is essential to the subject technology or that such embodiment applies to all configurations of the subject technology. Disclosure of an embodiment may apply to all embodiments, or to one or more embodiments. An embodiment may provide one or more examples. A phrase such as an embodiment may refer to one or more embodiments, and vice versa. A phrase such as "configuration" does not imply that such configuration is essential to the subject technology or that such configuration applies to all configurations of the subject technology. Disclosure of a configuration may apply to all configurations, or to one or more configurations. A configuration may provide one or more examples. Any reference to such a configuration may refer to one or more configurations, and vice versa.

[0076] In one aspect, unless otherwise stated, all measurements, values, ratings, positions, dimensions, sizes, and other specifications set forth in this specification (including the claims that follow) are approximate and not exact, and in one aspect, are intended to have a reasonable range consistent with the functions to which they relate and functions customary in the art to which they pertain.

[0077] It is understood that the specific order or hierarchy of steps, operations, or processes disclosed is an illustration of example approaches. Based on design preferences, it is understood that the specific order or hierarchy of steps, operations, or processes may be rearranged. Some of the steps, operations, or processes may be performed simultaneously. Some or all of the steps, operations, or processes may be performed automatically, without user intervention. The accompanying method claims, if any, present elements of the various steps, operations, or processes in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[0078] All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or that later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be made available to the public, regardless of whether such disclosure is expressly recited in the claims. No element of a claim is to be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase "means for," or, in the case of a method claim, unless the element is recited using the phrase "step for." Moreover, to the extent terms such as "include" or "having" are used, such terms are intended to be inclusive in the same manner as the term "comprise," such as "comprise" is construed when used as a transitional phrase in a claim.

[0079] The Title of the Invention, Background Art, Summary of the Invention, Brief Description of the Drawings, and Abstract of the Disclosure are hereby incorporated into this disclosure and are provided as examples for purposes of illustrating the disclosure, not as a limiting description. They are submitted with the understanding that they will not be used to limit the scope or meaning of the claims. Additionally, in the Detailed Description, it can be understood that the description provides examples for illustrative purposes, and that various features have been grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed subject matter requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed structure or operation. The following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate claimed subject matter.

[0080] The claims are not intended to be limited to the embodiments described herein, but are to be accorded full scope consistent with the language of the claims and to encompass all legal equivalents. Nonetheless, none of the claims are intended to encompass subject matter that fails to satisfy the requirements of 35 U.S.C. §§ 101, 102, or 103, nor should they be so interpreted.

Claims

1. 1. A modular power and connectivity assembly, said modular power and connectivity assembly comprising: a housing including a cavity configured to receive a device coupling member of the infusion pump device; a power assembly configured to provide power to the infusion pump device; a communication assembly configured to provide communication with the infusion pump device; a harness assembly including a base and an extension member, the infusion pump device being connected to the base, the extension member connecting the base to the housing within the cavity; Including, the modular power and connectivity assembly is configured to be reusable, the modular power and connectivity assembly being configured to be removably coupled to the infusion pump device; The cavity is sized and dimensioned to receive the entire infusion pump device, a modular power and connectivity assembly.

2. The modular power and connectivity assembly of claim 1 , wherein the modular power and connectivity assembly further comprises a recess configured to receive a portion of a tube.

3. 10. The modular power and connectivity assembly of claim 1, wherein the modular power and connectivity assembly further comprises at least one indicator configured to visually indicate a level of power stored within the power assembly.

4. The modular power and connectivity assembly of claim 1 , wherein the infusion pump device includes the device coupling member and the cavity includes a cavity coupling member.

5. 5. The modular power and connectivity assembly of claim 4, wherein the device coupling member and the cavity coupling member are opposing connections configured to physically mate with one another.

6. 5. 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. 5. The modular power and connectivity assembly of claim 4, wherein the device coupling member and the cavity coupling member are a wireless assembly configured to wirelessly connect to one another.

8. 2. The modular power and connectivity assembly of claim 1, wherein the harness assembly includes the device coupling member and a base, and 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 harness assembly includes a base, the base configured to physically mate with the infusion pump device.

10. The modular power and connectivity assembly of claim 1 , wherein the harness assembly includes a base, the base configured to magnetically mate with the infusion pump device.

11. The modular power and connectivity assembly of claim 1 , wherein the harness assembly includes a base, the base configured to wirelessly connect to the infusion pump device.

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

13. 1. A power and connectivity system, the power and connectivity system comprising: one or more reusable modular power and connectivity assemblies; a connectivity hub configured to transmit electronic signals to and receive electronic signals from the one or more reusable modular power and connectivity assemblies; and Including, Each modular power and connectivity assembly is a housing including a cavity configured to receive a device coupling member of the infusion pump device; a power assembly configured to provide power to the infusion pump device; a communications assembly configured to provide communications with the infusion pump device, each modular power and connectivity assembly configured to be removably coupled to the infusion pump device; a harness assembly including a base and an extension member, the infusion pump device being connected to the base, the extension member connecting the base to the housing within the cavity; Including, The cavity is sized and dimensioned to receive the entire infusion pump device, power and connectivity system.

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

15. 15. The power and connectivity system of claim 14, further comprising a mobile interface configured to transmit electronic signals to and receive electronic signals from the cloud interface, the mobile interface being present on a portable electronic device.

16. 14. The power and connectivity system of claim 13, wherein the power and connectivity system further includes a charging station, the charging station configured to recharge the one or more reusable modular power and connectivity assemblies.

17. 17. The power and connectivity system of claim 16, wherein the charging station includes a rechargeable power source, the charging station being configured to be portable.

18. 14. A method of operating a modular power and connectivity system according to claim 13, said method comprising: removably connecting the modular power and connectivity assembly to an infusion pump device; transmitting power from the modular power and connectivity assembly to the infusion pump device; providing a communications link between the modular power and connectivity assembly and the infusion pump device; transmitting data from the infusion pump 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; transmitting the portion of the data from the connectivity hub to a healthcare network cloud interface; A method comprising:

Images