Infusion module adapter

Abstract

An infusion module adapter is configured to couple a control unit of a patient care system to an infusion pump. The adapter system includes a first interconnect system on a first side and a second interconnect system on a second side. The first interconnection system includes: a mechanical connector having a first support contact for mechanical coupling to the control unit; and a logic connector having a first power contact and a first communication contact for logically coupling to the control unit. The second interconnection system includes an integrated connector having a second support contact, a second power contact, and a second communication contact for mechanical and logical coupling to the infusion pump. The adapter system also includes a power conversion circuit configured to convert a power signal between the first power contact and the second power contact, and a processing circuit configured to convert a message between the first communication contact and the second communication contact.

Description

BACKGROUND OF THE INVENTION

[0001] Infusion pumps are complex electromechanical devices used to deliver fluids to a patient's body in a controlled manner. They typically serve the needs of inpatients, among whom life-saving medications are often delivered via intravenous infusion. Infusion pump systems typically include multiple modules configured for different programming and pumping functions. These modules generally work together using compatible power specifications, communication protocols, and mechanical interconnections.

[0002] To maintain cross-compatibility between modules in a conventional infusion pump system, it is generally not possible to upgrade one module without upgrading the entire system. However, upgrading a group of infusion pump systems in a healthcare facility can be prohibitively costly. Instead of upgrading individual modules or components as needed, it may be more economical to wait until more components of the system need upgrading and then replace the entire system. However, the cost of waiting is the delay in obtaining the efficiency and safety feature improvements offered by newer modules. Thus, there is a trade-off between cost optimization and feature optimization when deciding whether and how often to upgrade a conventional infusion pump system. SUMMARY OF THE INVENTION

[0003] Based on the foregoing discussion and other problems and disadvantages of the related art, there is a need for an infusion pump system that can be partially upgraded while maintaining cross-compatibility between the various modules included in the system. Such a system addresses the trade-off between cost optimization and feature optimization by providing the ability to upgrade a single module (e.g., a primary point-of-care unit) without having to upgrade every module simultaneously, while maintaining the functionality of other modules (e.g., a pump module). The infusion pump system as described herein uses an infusion module adapter system that interfaces two or more subsystems having components that are incompatible with each other, thereby providing modular, physical interoperability, and logical interoperability between other incompatible subsystems of the infusion pump system.

[0004] In accordance with aspects of the present subject matter, an infusion module adapter system couples a control unit of a patient care system to an infusion pump. The adapter system includes a first interconnection system on a first side and a second interconnection system on a second side. The first interconnection system includes: a mechanical connector having first support contacts for mechanical coupling to the control unit; and a logical connector having first power contacts and first communication contacts for logical coupling to the control unit. The second interconnection system includes an integrated connector having second support contacts, second power contacts, and second communication contacts for mechanical and logical coupling to the infusion pump. The adapter system further includes a power conversion circuit configured to convert a power signal between the first power contacts and the second power contacts, and a processing circuit configured to convert a message between the first communication contacts and the second communication contacts.

[0005] In some embodiments, the first support contact of the mechanical connector of the first interconnect system includes a latching mechanism that supports the physical continuity of the attachment to the control unit; and the second support contact of the integrated connector of the second interconnect system includes a latching mechanism that supports the physical continuity of the attachment to the infusion pump.

[0006] In some embodiments, the first power contact of the logic connector of the first interconnect system is configured to receive a first power signal from the control unit, where the first power signal is characterized by a first voltage, a first amplitude, or a first frequency; the power management module is configured to convert the first voltage, the first amplitude, or the first frequency to a second voltage, a second amplitude, or a second frequency; and the second power contact of the integrated connector of the second interconnect system is configured to transmit the second power signal to the infusion pump, where the second power signal is characterized by a second voltage, a second amplitude, or a second frequency.

[0007] In some embodiments, the first communication contact of the logic connector of the first interconnect system is configured to send messages to and receive messages from the control unit; the second communication contact of the integrated connector of the second interconnect system is configured to send messages to and receive messages from the infusion pump; and the processing circuit of the communication conversion module is configured to: transform the messages received from the control unit into a message format consumable by the infusion pump and send the transformed control unit messages to the infusion pump; and transform the messages received from the infusion pump into a message format consumable by the control unit and send the transformed infusion pump messages to the control unit.

[0008] In some embodiments, the messages received from the control unit include pumping instructions. In some embodiments, the messages received from the infusion pump include pumping status or alarm data.

[0009] In some embodiments, the processing circuit of the communication conversion module is configured to manage the state transitions of the pump state of the infusion pump. In some embodiments, the processing circuit of the communication conversion module is configured to receive programming updates and facilitate the interoperability of multiple infusion pumps.

[0010] In some embodiments, the infusion module adapter system further includes a wireless transceiver. In some embodiments, the processing circuit of the communication conversion module is configured to receive firmware updates via the wireless transceiver. In some embodiments, the processing circuit of the communication conversion module is configured to transmit logging and / or asset tracking messages via the wireless transceiver.

[0011] In some embodiments, the processing circuitry of the communication conversion module is configured to verify compatibility with the infusion pump when the infusion pump is attached to the infusion module adapter system. In some embodiments, the processing circuitry of the communication conversion module is configured to verify compatibility by validating an authorization code stored in a data storage device of the infusion module adapter system.

[0012] In some embodiments, the processing circuitry of the communication conversion module is configured to verify compatibility by validating (i) the firmware or software versions of the control unit and the infusion module adapter system, (ii) the infusion module adapter system and the infusion pump, and / or (iii) the control unit and the infusion pump.

[0013] In some embodiments, the processing circuitry of the communication conversion module is configured to verify compatibility by validating the cross-compatibility, product-level compatibility, and / or version-level compatibility of (i) the control unit and the infusion module adapter system, (ii) the infusion module adapter system and the infusion pump, and / or (iii) the control unit and the infusion pump.

[0014] In some embodiments, the mechanical connector of the first interconnect system is a mechanical modular interconnect (M-MIC) connector. In some embodiments, the logical connector of the first interconnect system is an electrical modular interconnect (E-MIC) connector. In some embodiments, the integrated connector of the second interconnect system is an inter-unit interface (IUI) connector.

[0015] In some embodiments, the mechanical connector of the first interconnect system and the integrated connector of the second interconnect system are disposed in the upper portion of the infusion module adapter system; and the logical connector of the first interconnect system is disposed in the lower portion of the infusion module adapter system.

[0016] In some embodiments, the mechanical connector of the first interconnect system is disposed in the upper portion of the infusion module adapter system; and the logical connector of the first interconnect system and the integrated connector of the second interconnect system are disposed in the lower portion of the infusion module adapter system.

[0017] It will be understood that other configurations of the subject technology will be readily apparent to those skilled in the art from the following detailed description, wherein various configurations of the subject technology are illustrated and described by way of example. As will be recognized, the subject technology is capable of other and different configurations and its several details are capable of modification in various other respects, all without departing from the scope of the subject technology. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] To better understand the various described embodiments, reference should be made to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings and the description, like reference numerals refer to corresponding parts.

[0019] Figure 1 Depicts an exemplary infusion pump system in its intended environment according to some embodiments.

[0020] Figure 2 Depicts an infusion pump system having a plurality of subsystems that can be interfaced using compatible mechanical and electrical interconnects.

[0021] Figure 3 Depicts an infusion pump system having a plurality of subsystems that can be interfaced using compatible mechanical and electrical interconnects.

[0022] Figure 4 Depicts an infusion pump system having Figure 3-4 a combination of the subsystems described in, where the subsystems are not interfacable due to having incompatible mechanical and electrical interconnects.

[0023] Figure 5 Depicts an infusion pump system having a plurality of subsystems and a plurality of infusion module adapters, the plurality of subsystems having incompatible mechanical and electrical interconnects, the plurality of infusion module adapters having a set of interconnects compatible with different subsystems of the infusion pump system.

[0024] Figures 6A-6B Depicts a close-up view of different configurations of an infusion module adapter according to some embodiments.

[0025] Figure 7 Is a conceptual diagram showing an example electronic system for interfacing subsystems having incompatible interconnects when operating an infusion pump. DETAILED DESCRIPTION

[0026] Reference will now be made to embodiments, examples of which are illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide an understanding of the various described embodiments. However, it will be apparent to those of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

[0027] Figure 1Illustrates an example patient care system 100 according to some embodiments. The patient care system 100 includes a plurality of infusion pumps 110 (e.g., large - volume pumps (LVPs)) and a control unit 120 (sometimes referred to as an interface unit). The infusion pumps 110 are used to accurately deliver fluids to a patient via an intravenous or epidural path for treatment and / or diagnostic purposes, typically at a rate of 0.1 to 999 mL / hr or higher. The control unit 120 (also referred to as an infusion controller) is the basic programming unit that drives communication and interaction before and during the infusion process. The control unit 120 may include a display and an interface (e.g., a keyboard or a touchscreen) that trained nursing professionals use to program the infusion pumps 110. Each infusion pump 110 can be programmed with a specific amount of fluid to be delivered into the patient, one or more timing parameters for delivering the fluid, and other specific instructions.

[0028] In the depicted example, the patient care system 100 includes four fluid infusion pumps 110, and each fluid infusion pump 110 is in operable communication with a corresponding fluid delivery device 112. The infusion pumps 110 are directly or indirectly connected to and controlled by the control unit 120. The fluid supply 114 can take various forms, but in this example is shown as a bag, which is inverted and hung above the corresponding infusion pump 110. The fluid supply 114 can also take the form of a bottle or other types of containers. The control unit 120 and the fluid supply 114 are mounted to a roller stand or pole 130. Each fluid supply 114 is connected to the patient through a corresponding delivery device 112 such that the patient can receive the fluid from all fluid supplies 114.

[0029] In the depicted example, separate infusion pumps 110 are used to infuse each fluid from the fluid supplies 114 into the patient. The infusion pumps 110 are flow - control devices that act on the corresponding tubes or fluid conduits of the corresponding delivery devices 112 to move the fluid from the fluid supplies 114 through the catheter and to the patient. Since separate infusion pumps 110 are used, each pump can be individually set with the infusion pumping or operating parameters required to infuse a specific medical fluid from the corresponding fluid supply 114 into the patient at a specific rate prescribed by the clinician for that fluid.

[0030] In some embodiments, each infusion pump 110 may include various sensors and detectors configured to monitor fluid flow and detect hazards. For example, an air-in-line (AIL) detector may be configured to detect air in the tubing of the delivery device 112. In another example, an occlusion sensor may be configured to detect a pressure change in the tubing upstream or downstream of the delivery device 112, indicating an occlusion in the line. Various other hazard sensors may be configured to monitor any other aspect of the infusion process associated with the corresponding infusion pump 110. The foregoing sensors may monitor air, pressure, flow, or any other infusion metric at intervals or for a time series by sampling values over time. When these metrics are collected for analysis, the collected metrics may reflect an average value, a moving average, a periodic maximum, a periodic minimum, or a correspondence with a threshold or range of the underlying value detected by the corresponding sensor or detector, etc.

[0031] In some embodiments, any one or all of the above sensors and detectors may be located inside the corresponding infusion pump 110. In some embodiments, any one or all of the foregoing sensors and detectors may be located upstream or downstream of the infusion pump 110, provided that a portion of each delivery device 112 passes through or near the corresponding sensor or detector.

[0032] The infusion pumps 110 may be configured to adjust their operation based on the foregoing sensor metrics. For example, if the AIL metric of a particular infusion pump 110 exceeds a safety threshold (e.g., a maximum number of bubbles within a given amount of time or volume of fluid), the infusion pump 110 may pause the pumping operation corresponding to the AIL detector for which the measured AIL metric exceeded the safety threshold. The infusion pump 110 or the control unit 120 may output a notification to inform the clinician that the safety threshold has been exceeded. The particular infusion pump 110 or the control unit 120 may output the notification on a display, output the notification as an audio alert from a speaker, and / or send the notification to another computing device communicatively coupled to the control unit 120 (e.g., an external device such as a medical facility server or other computer, and having a portable processor such as a handheld communication device or a portable computer, or other information device accessible by the clinician).

[0033] Generally, the medical fluid delivery device 112 has more components than Figure 1 shown. Many have check valves, drip chambers, valved ports, connectors, and other devices well known to those skilled in the art. For the sake of clarity of illustration, these other devices are not included in the drawings.

[0034] In some embodiments, each infusion pump 110 includes a door and a handle that is operable to lock the door in a closed position for operation and to unlock and open the door to access the internal pumping and sensing mechanisms and to load a drug delivery device 112 for the infusion pump. When the door is open, the tubing of the corresponding drug delivery device 112 can be connected to the infusion pump. When the door is closed, the tubing enters into operational connection with the infusion pumping mechanism, upstream and downstream pressure sensors, and other devices of the infusion pump. In this embodiment, a display (such as an LED display) is in a planar view on the door and can be used to visually communicate various information related to the infusion pump 110, such as alert indications (e.g., alert messages).

[0035] In some embodiments, control keys are present on each infusion pump 110 and control unit 120 for programming and controlling the operation of the infusion pump as needed. In some embodiments, the control keys can be presented as interactive elements on a display (e.g., a touchscreen display). The infusion pump 110 and / or the control unit 120 can also include an audio alert device in the form of a speaker (not shown).

[0036] In some embodiments, the control unit 120 includes: a display for visually communicating various information such as the operating parameters of the connected pump and alert indications and alert messages; and control keys for selecting and / or setting control parameters and / or options for controlling the infusion pump 110 and other connected modules. The control unit 120 can also include a speaker to provide an audible alert. In some embodiments, the display can be implemented as a touchscreen display. In such an embodiment, the control keys can be omitted or reduced in number by providing corresponding interactive elements via a graphical user interface (presented via the display). In some embodiments, each control key can select a corresponding option displayed in the display.

[0037] The control unit 120 can include a communication system (not shown) using which the control unit 120 can communicate with external devices (such as a medical facility server or other computer) and with portable processors (such as a handheld communication device or a portable computer) or other information devices that a clinician may have for transferring information and for downloading a drug library (e.g., to the infusion pump 110). The communication module can be used to transfer access and interaction information to a clinician encountering the control unit 120 or the infusion pump 110 coupled thereto. The communication system can include one or more of a radio frequency (RF) system, an optical system (e.g., infrared), a Bluetooth system, or other wired or wireless systems. The communication system can additionally or alternatively be included integrally with the infusion pump 110, such as in cases where the control unit 120 is not used.

[0038] In addition, other types of modules can be connected to the infusion pump 110 and / or the control unit 120, such as an injection pump module, a patient-controlled analgesia module, an external safety device (ESD), a patient safety device (such as an end-tidal CO2 monitoring module or a pulse oximeter monitoring module), and the like. Some ESDs can include, for example, an air trap, an air detector (e.g., an AIL detector as described herein), a flow detector, a particle detector, or a spectral analyzer.

[0039] Figure 2 An infusion pump system 200 having multiple subsystems is depicted, and the multiple subsystems can be interconnected using compatible mechanical and electrical interconnects. System 200 includes multiple infusion pumps 210 (e.g., corresponding to Figure 1 the infusion pump 110) and a control unit 220 (e.g., corresponding to Figure 1 the control unit 120). The infusion pumps 210 and the control unit 220 in system 200 have the same or similar features as those described above with reference to system 100 ( Figure 1 ).

[0040] The infusion pumps 210, the control unit 220, and any other modules (e.g., those discussed above with reference to Figure 1 ) can be configured as subsystems of an infusion pump system 200. These subsystems can be coupled to each other using a modular interconnect system 230. The modular interconnect system 230 can include multiple connectors attached to each side of each module, thus allowing the infusion pump system 200 to be modular and configurable for customer needs. The modularity of the connectors can be achieved through plug-and-socket connection types (sometimes referred to as male and female connection types) and different degrees of distribution of mechanical (M), communication (C), and power (P) characteristics.

[0041] The design and function of the connectors in a given interconnect system can depend on the model and version of the modules (infusion pumps 210 and control unit 220) to which they are connected. Thus, various interconnect systems can include different types of connectors (also referred to as interconnects), each having a different function. Although the interconnect systems for different subsystems can be different, the connectors in each system have a common function incorporated into their design to provide a mechanical connection (M), a communication connection (C), and a power connection (P) between the modules to which they are attached (e.g., between the control unit 220 and one or more infusion pumps 210). Additional mechanical connections can be made using a latch L1 and a corresponding latch release R1 (e.g., a control component that releases the latch when activated).

[0042] Mechanical connector M includes physical connections (e.g., latches) that support physical interoperability between various modules. These connectors form a support structure that supports the continuity of attachment for the connected modules when connected. As described above, although the control unit 220 can be mounted to a roller rack or rod (e.g., Figure 1 130 in

[0043] ), the infusion pump 210 is mounted to the control unit 220 or to each other. This mounting is enabled by the mechanical connector M.

[0044] Communication connector C includes connections that support logical interoperability between various modules. These connectors form a communication bridge that supports the sending and receiving of messages between the infusion pump 210 and the control unit 220. Example messages include infusion instructions such as infusion rate, volume, and timing sent from the control unit 220 to one or more infusion pumps 210. Example messages also include data such as alert status and infusion status sent from the infusion pump 210 to the control unit 220.

[0045] Mechanical connector, power connector, and communication connector MPC can be implemented as an inter-unit interface (IUI) in the system 200. Example communication paths of the IUI include (i) a module detection (MODDET) path configured to control power to the connected modules, (ii) a transmit and receive (TxD and RxD) path configured to handle communication between the control unit and the connected modules, (iii) a unit ID detection path configured to allow the control unit to determine when a module is attached, and (iv) a unit ID enable path configured to control access to the system channel.

[0046] The IUI connector integrates the mechanical connection M with the power connection P and the communication connection C into a single connector MPC (e.g., a single plug or a single corresponding socket). Integrating the mechanical connection, communication connection, and power connection into a single connector provides operational simplicity, making the interconnected system easier to operate because only one plug or only one socket provides all the functions required for physical and logical interoperability between the various subsystems of the infusion pump system 200. However, a single connector integrating the connections for all the aforementioned functions is more complex and thus may have a shorter lifespan.

[0047] Figure 3Depicts an infusion pump system 300 having multiple subsystems that may be aggregated using compatible mechanical and electrical interconnects. System 300 includes multiple infusion pumps 310 (e.g., corresponding to Figure 2 infusion pump 210) and a control unit 320 (e.g., corresponding to Figure 2 control unit 220). The infusion pumps 310 and control unit 320 in system 300 have features that are the same as or similar to those described above with reference to system 200 ( Figure 2 ) and those described above with reference to system 100 ( Figure 1 ).

[0048] The infusion pumps 310, control unit 320, and any other modules (e.g., those discussed above with reference to Figure 1 ) may be configured as subsystems of an infusion pump system 300. These subsystems may be coupled to each other using a modular interconnect system 330. The modular interconnect system 330 may include multiple connectors attached to each side of each module, thus allowing the infusion pump system 300 to be modular and configurable for customer needs. The modularity of the connectors may be achieved through plug-and-socket connection types (sometimes referred to as male and female connection types) and different degrees of distribution of mechanical (M), communication (C), and power (P) features.

[0049] The design and function of the connectors in a given interconnect system may depend on the model and version of the modules (infusion pumps 310 and control unit 320) to which they are connected. Thus, various interconnect systems may include different types of connectors (also referred to as interconnects), each having a different function. Although the interconnect systems for different subsystems may be different, the connectors in each system have common functions incorporated into their design to provide a mechanical connection (M), a communication connection (C), and a power connection (P) between the modules to which they are attached (e.g., between the control unit 320 and one or more infusion pumps 310). Additional mechanical connections may be made using a latch L2 and a corresponding latch release R2 (e.g., a control component that releases the latch when activated).

[0050] The mechanical connector M and the power and communication connector PC can be implemented as modular interconnects (MICs) in the system 300, where the mechanical connector (mechanical modular interconnect, M-MIC) is independent of the communication and power connectors (electrical modular interconnect, E-MIC). Keeping the mechanical M and the power / communication PC connections separate can provide increased reliability because each physical connector can be optimized for its specific function without sacrificing the physical layout of the connectors. Additionally, connectors with fewer functions can be easier to design and implement, leading to longer lifetimes. However, due to the use of multiple connectors (as opposed to only one IUI), the MIC interconnect system as a whole may be more complex, which may increase costs due to having more components in the bill of materials.

[0051] In some embodiments, the systems 200 and 300 can be different generations of infusion pump systems manufactured by the same company, where the system 300 is considered to have upgraded features (e.g., efficiency and / or safety features). In some embodiments, the systems 200 and 300 can be infusion pump systems with similar features but manufactured by different companies. At a minimum, the subsystems in the system 200 (infusion pump 210 and control unit 220) are configured to be mechanically and electrically coupled to each other, and the subsystems in the system 300 (infusion pump 310 and control unit 320) are configured to be mechanically and electrically coupled to each other, but the subsystems in one of the two systems 200 / 300 are not configured to be mechanically and / or electrically coupled to the subsystems in the other of the two systems 200 / 300 (e.g., infusion pump 210 is not compatible with control unit 320, and infusion pump 310 is not compatible with control unit 220).

[0052] Although the systems 200 and 300 implement, for example, IUI and MIC interconnect systems, the implementation of each system can additionally or alternatively implement other interconnect systems not described in this application. Thus, the IUI and MIC implementations are non-limiting examples that illustrate different ways of configuring connectors for the various subsystems of an infusion pump system. The concepts involved in the description of these example interconnect systems can be extended to other interconnect systems not included in this disclosure.

[0053] Figure 4 An infusion pump system 400 having multiple subsystems is depicted, the multiple subsystems including non-converging connectors. For example, the system 400 includes an infusion pump 210 from the system 200 ( Figure 2 ) and an infusion pump 310 from the system 300 ( Figure 3) of the infusion pump 210. Although the control unit 320 may provide upgraded functionality and safety features, the control unit 320 also includes an interconnect system that is incompatible with the connectors of the infusion pump 210. Specifically, the mechanical connector M and the power / communication connector PC of the control unit 320 cannot be connected to the mechanical / communication / power MPC connector of the infusion pump 210. In addition, the latch L2 of the control unit 320 is incompatible with the latch L1 and latch release R1 of the infusion pump 210.

[0054] System 400 depicts an example illustrating the incompatibility of two different interconnect systems. Although system 400 depicts incompatible IUI and MIC connectors, any other paired incompatible infusion interconnect systems (including those not described in this application) will prevent physical and / or logical interoperation between subsystems of an infusion pump system.

[0055] Figure 5 An infusion pump system 500 is depicted having multiple subsystems 210 / 320 having incompatible mechanical and electrical interconnections (as described above with reference to Figure 4 To make the subsystems compatible with each other, the system 500 also includes a plurality of infusion module adapters 502 having a set of interconnects that are compatible with the interconnects of the different subsystems 210 / 320 of the infusion pump system 500. The adapters 502 provide modularity, physical interoperability, and logical interoperability between the various subsystems 210 / 320 to which they are physically and communicatively coupled.

[0056] System 500 is an example of a mixed house strategy in which a user can migrate from an old pump subsystem to a new pump subsystem through a series of versions. For example, a user may wish to upgrade a control unit (e.g., from Figure 2 The control unit 220 in Figure 3 control unit 320 in the same time as their pump modules (e.g. Figure 2 5) to a new system, as depicted in system 500. Using an older infusion pump 210 with an upgraded control unit 320 allows a user to bridge one product to another (e.g., a legacy pump to a new control unit) to allow the user to access new features of the upgraded control unit without having to replace all modules (subsystems) of the entire infusion pump system, thereby providing additional functionality at a reduced cost.

[0057] The infusion module adapter 502 is attached to an older module (e.g., infusion pump 210) and provides an electromechanical interface to a newer system (e.g., control unit 320). Although system 500 depicts an example where adapter 502 couples an older infusion pump 210 to an upgraded control unit 320, other combinations of new and old subsystems are possible. In other embodiments, rather than different subsystems 320 / 210 representing newer and older modules, they can alternatively or additionally represent modules from different manufacturers, regardless of technology generation. In other words, the modules / subsystems can be of substantially the same generation of technology (equivalent or substantially equivalent as old or new to each other).

[0058] Figures 6A-6B A close-up view depicting different configurations of the infusion module adapter 502 according to some embodiments is shown. In a first configuration (e.g., "left" configuration) 502-1, the adapter can be configured to couple to a first side of two sides of the control unit (e.g., couple to the Figure 5 left side of control unit 320 in ), and in a second configuration (e.g., "right" configuration) 502-2, the adapter can be configured to couple to a second side of two sides of the control unit (e.g., couple to the Figure 5 right side of control unit 320 in ).

[0059] The two configurations of adapter 502 include a mechanical (physical) connection M, a power connection P, and a communication (logical) connection C for coupling to corresponding connectors and paths on the various subsystems to which the adapter is configured to couple.

[0060] The mechanical connection M enables physical interoperability between the subsystems coupled to the adapter (e.g., Figure 5 control unit 320 and infusion pump 210 in ). For example, the mechanical connection M on the control unit side can also use an MIC-type connector (in addition to an optional latch mechanism L2 and corresponding latch release R2) to physically couple the adapter to the control unit. The mechanical connection on the infusion pump side (M in the MPC connector) can also use an IUI-type connector (in addition to an optional latch mechanism L1 and corresponding latch release R1) to physically couple the adapter to the infusion pump. Generally, the first side of the two sides of the adapter can use a mechanical connector of a first type (e.g., connector M on the control unit side), and the second side of the two sides of the adapter can use a mechanical connector of a second type different from the first type (e.g., connector MPC on the infusion pump side).

[0061] The power connection P extends the subsystems coupled to the adapter (e.g., Figure 5Power management between the control unit 320 and the infusion pump 210 in []. The adapter includes a power management module 610, and the power management module 610 includes an electronic circuit that regulates the power level between subsystems coupled to each side of the adapter. For example, the power circuit included in the power management module 610 can be configured to regulate the power level between the control area network bus of the control unit 320 and the IUI type connector (MPC) on the infusion pump side. Such a power circuit can include a voltage boost converter, a voltage buck converter, etc. Additionally, the power circuit included in the power management module 610 can include a short-term power storage circuit (e.g., one or more batteries or capacitors) to allow one subsystem (e.g., the infusion pump 210) to operate when not powered by another subsystem (e.g., the control unit 320).

[0062] The communication connection C enables logical interoperability between subsystems coupled to the adapter 502 (e.g., Figure 5 the control unit 320 and the infusion pump 210 in []). The adapter includes a communication conversion module 620, which includes an electronic circuit that drives and / or transforms the communication between the connected subsystems, thereby allowing each subsystem to communicate with the other subsystem without the need to change any hardware or software associated with the connected subsystems.

[0063] In each of the configurations 502-1 and 502-2, the adapter includes: (i) one or more connectors on the first (control unit) side, which are configured to physically and communicatively couple to corresponding connectors on the control unit (e.g., Figure 5 the control unit 320 in []), and (ii) one or more connectors on the second (pump) side, which are configured to physically and communicatively couple to corresponding connectors on the pump module (e.g., Figure 5 the infusion pump 210 in []).

[0064] In some embodiments, one of the first side and the second side includes only one electromechanical connector (e.g., the connector MPC on the infusion pump side), while the other of the first side and the second side includes two electromechanical connectors (e.g., the connectors M and PC on the control unit side).

[0065] In some embodiments, one of the first side and the second side includes only one electromechanical connector either in the upper part or only in the lower part of the adapter (e.g., the connector MPC on the infusion pump side in the upper part of the adapter), while the other of the first side and the second side includes one electromechanical connector in the upper part of the adapter (e.g., the connector M on the control unit side) and one electromechanical connector in the lower part of the adapter (e.g., the connector PC on the control unit side).

[0066] In some embodiments, one of the first side and the second side includes a single electromechanical connector (e.g., the connector MPC on the infusion pump side) that integrates mechanical connection features (M), electrical connection (P), and communication paths (C), while the other of the first side and the second side includes two electromechanical connectors that separate the functions of mechanical, electrical, and communication features (e.g., the connectors M and PC on the control unit side).

[0067] In some embodiments, the specific connector configuration can vary based on the corresponding connector types and locations on the various subsystems to which the adapter 502 is configured to couple.

[0068] In some embodiments, the communication conversion module 620 includes message conversion circuitry and / or firmware or software programs that convert software messages from one subsystem into a form consumable by another subsystem. For example, module 620 can convert or otherwise process infusion messages from the control unit 320 into a form consumable by the infusion pump 210. In another example, module 620 can convert or otherwise process alerts from the infusion pump 210 into a form consumable by the control unit 320. This communication processing allows for data exchange at the physical layer between the communication interfaces of one subsystem (e.g., the control area network bus protocol of the control unit 320) and the communication interface of another subsystem (e.g., the RS-485 connector to the infusion pump 210). In some embodiments, the message conversion circuitry can define a workable messaging interface to ensure the expected messaging behavior between subsystems (e.g., using different messaging protocols, timings, etc.).

[0069] In some embodiments, the communication conversion module 620 implements a state machine that manages state transitions of the pump state. Additionally, the communication conversion module 620 can include a system storage device (e.g., 702 as described below) to allow for programming updates and to facilitate interoperability between different pumps. For example, the memory can store communication specifications (e.g., timing diagrams and / or logic voltage levels) corresponding to different pump systems, such that the adapter 502 can translate messages between the various subsystems according to the stored specifications.

[0070] In some embodiments, the communication conversion module 620 can include or be communicatively coupled to a radio (e.g., 716 as described below) to allow for firmware updates, message handling, logging, asset tracking, etc.

[0071] In some embodiments, adapter 502 may include one or more mechanical switches (e.g., DIP switches) configured to signal to a first subsystem (e.g., a control unit) the identity or type of a second subsystem (e.g., a pump) to which the adapter is coupled. Thus, based on the switch configuration, the control unit may determine the type of infusion pump coupled to the adapter upon detecting the presence of the adapter.

[0072] In some embodiments, communication conversion module 620 may perform compatibility checks by verifying the cross-compatibility of attached subsystems. This feature may check authorizations (e.g., checking whether a particular control unit is authorized to work with a given pump and vice versa), software and / or firmware verification (e.g., checking whether the firmware of each subsystem supports the other and / or is up-to-date), etc. Specifically, communication conversion module 620 may determine and confirm software / firmware cross-compatibility, product-level compatibility, and / or version-level compatibility between control unit 320 and adapter 502, between adapter 502 and infusion pump 210, and / or between control unit 320 and infusion pump 210. To this end, the adapter software / firmware may support various versions and generations of control units, pumps, and other modules (e.g., as described above with reference to system 100).

[0073] In some embodiments, the same type of connector (M or C or P) may be provided on both sides of adapter 502, while a subset of the connector set may be implemented as different connector types on either side as described above. For example, mechanical connectors M may be aligned on both sides of adapter 502 for a general mechanical connection, but the power and communication connectors P and C may be placed differently or be different connector types to be compatible with different control units and infusion pumps on either side of adapter 502.

[0074] Figure 7 is a conceptual diagram showing an example electronic system 700 for connecting subsystems with incompatible interconnects when operating an infusion pump. Electronic system 700 may be a computing device for executing software, including but not limited to the computing hardware within infusion module adapter 502 and / or other specifically configured computing devices or associated terminals disclosed herein. In this regard, electronic system 700 may include infusion module adapter 502 and / or a computing device within or connected to infusion module adapter 502.

[0075] The electronic system 700 may include various types of computer-readable media and interfaces for various other types of computer-readable media. In the depicted example, the electronic system 700 includes a bus 708, one or more processing units 712, a system memory 704, a read-only memory (ROM) 710, a permanent storage device 702, one or more input device interfaces 714, one or more output device interfaces 706, and one or more network interfaces 716. In some embodiments, the electronic system 700 may include or be integrated with other computing devices or circuitry for operating the various components and methods described previously.

[0076] The bus 708 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the electronic system 700. For example, the bus 708 communicatively connects one or more processing units 712 to the ROM 710, the system memory 704, and the permanent storage device 702.

[0077] From these various memory units, one or more processing units 712 retrieve the instructions to be executed and the data to be processed in order to perform the processes disclosed by this subject matter. In different embodiments, one or more processing units may be a single-processor or multi-core processor.

[0078] The ROM 710 stores static data and instructions required by one or more processing units 712 and other modules of the electronic system. On the other hand, the permanent storage device 702 is a read-write memory device. Such a device is a non-volatile memory unit that stores instructions and data even when the electronic system 700 is turned off. Some embodiments disclosed by this subject matter use a mass storage device (such as a magnetic disk or an optical disk and its corresponding disk drive) as the permanent storage device 702.

[0079] Other embodiments use a removable storage device (such as a floppy disk, a flash drive, and its corresponding disk drive) as the permanent storage device 702. Like the permanent storage device 702, the system memory 704 is a read-write memory device. However, different from the storage device 702, the system memory 704 is a volatile read-write memory, such as random access memory. The system memory 704 stores some instructions and data required by the processor during operation. In some embodiments, the processes disclosed by this subject matter are stored in the system memory 704, the permanent storage device 702, and / or the ROM 710. From these various memory units, one or more processing units 712 retrieve the instructions to be executed and the data to be processed in order to perform the processes of some embodiments.

[0080] Bus 708 is also connected to input and output device interfaces 714 and 706. Input device interface 714 enables a user to communicate information to and select commands for the electronic system. Input devices used in conjunction with input device interface 714 include, for example, alphanumeric keyboards and pointing devices (also referred to as “cursor control devices”). Output device interface 706 enables, for example, the display of images generated by electronic system 700. Output devices used in conjunction with output device interface 706 include, for example, printers and display devices such as cathode ray tubes (CRTs) or liquid crystal displays (LCDs). Some embodiments include devices such as touchscreens that act as both input and output devices.

[0081] Bus 708 also couples electronic system 700 to a network (not shown) via network interface 716. Network interface 716 can include, for example, a wireless access point (such as Bluetooth or WiFi) or radio circuitry for connecting to a wireless access point. Network interface 716 can also include hardware (such as Ethernet hardware) for connecting a computer to a portion of one or more networks in a computer network such as a local area network (“LAN”), wide area network (“WAN”), wireless LAN, or intranet, such as the Internet. Any or all components of electronic system 700 can be used in conjunction with the present subject matter disclosure.

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

[0083] Some embodiments include electronic components such as microprocessors, storage, and memory that store computer program instructions on a machine-readable or computer-readable medium (also referred to as a computer-readable storage medium, machine-readable medium, or machine-readable storage medium). Some examples of such computer-readable media include RAM, ROM, compact discs read only (CD-ROMs), recordable compact discs (CD-Rs), rewritable compact discs (CD-RWs), digital versatile discs read only (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, mini SD cards, micro SD cards, etc.), magnetic and / or solid state disk drives, read only and recordable Disk, super-dense optical disk, other optical or magnetic media, and floppy disk. A computer-readable medium can store a computer program executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include machine code (such as that produced by a compiler), and files including higher-level code that is executed by a computer, an electronic component, or a microprocessor using an interpreter.

[0084] Although the above discussion mainly refers to a microprocessor or multi-core processor that executes software, some embodiments are executed by one or more integrated circuits, such as an application-specific integrated circuit (ASIC) or a field-programmable gate array (FPGA). In some embodiments, such integrated circuits execute instructions stored on the circuit itself.

[0085] As used in the specification and any claims of this application, the terms "computer", "server", "processor", and "memory" all refer to electronic or other technical devices. These terms do not include a person or a group of people. For the purposes of the specification, the term display or being displayed means being displayed on an electronic device. As used in the 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.

[0086] To provide interaction with a user, embodiments of the subject matter described in this specification can be implemented on a computer that has a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user, a keyboard, and a pointing device (e.g., a mouse or a trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and the input from the user can be received in any form, including sound, speech, or tactile input. Additionally, the computer can interact with the user by sending documents to and receiving documents from the device used by the user, for example, 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.

[0087] Embodiments of the subject matter described in this specification can be implemented in a computing system that includes backend components, such as a data server, or includes middleware components, such as an application server, or includes frontend components, such as a client computer having a graphical user interface or a web browser, through which a user can interact with embodiments of the subject matter described in this specification, or any combination of one or more such backend, middleware, or frontend components. The components of the system can 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”), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).

[0088] The computing system can include clients and servers. The clients and servers are typically far apart from each other and can interact through a communication network. The relationship between a client and a server arises from computer programs running on their respective computers and having a client-server relationship with each other. In some embodiments, the server transmits data (e.g., an HTML page) to the client device (e.g., to display data to and 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) can be received at the server from the client device.

[0089] Those skilled in the art will understand that the various illustrative blocks, modules, elements, components, methods, and algorithms described herein can 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 generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. For each particular application, the described functionality can be implemented in a different manner. The various components and blocks can be differently arranged (e.g., arranged in a different order, or partitioned in a different way), all without departing from the scope of the subject technology.

[0090] It will be understood that the specific order or hierarchy of steps in the disclosed processes is an illustration of example methods. Based on design preferences, it will be understood that the specific order or hierarchy of steps in a process can be rearranged. Some steps can be performed simultaneously. The appended method claims present elements of the steps in an example order and are not meant to be limited to the specific order or hierarchy presented.

[0091] Illustrative of the subject technology as a clause

[0092] For convenience, various examples of aspects of the present disclosure are described as numbered clauses (1, 2, 3, etc.). These are provided as examples and do not limit the claimed subject matter. Identification of the figures and reference numerals is provided below only as examples and for illustrative purposes, and the clauses are not limited by these identifications.

[0093] Clause 1: An infusion module adapter system (e.g., 502, Figure 5 ), configured to couple a control unit (e.g., 320, Figure 5 ) to an infusion pump (e.g., 210, Figure 5 ), the infusion module adapter system comprising: a first interconnection system on a first side of the adapter system (e.g., the control unit side, Figures 6A-6B ), and comprising: a mechanical connector (M) including first support contacts and configured to be mechanically coupled to a corresponding mechanical connector (M) on the control unit; and a logic connector (PC) including first power contacts and first communication contacts and configured for logical coupling to a corresponding logic connector (PC) on the control unit; a second interconnection system, the second interconnection system on a second side of the adapter system (e.g., the pump side, Figures 6A-6B ), and comprising: an integrated connector including second support contacts, second power contacts, and second communication contacts (MPC) and configured for mechanical coupling and logical coupling to a corresponding integrated connector on the infusion pump (MPC), wherein the second power contacts provide a second power signal different from the first power signal received at the first power contacts, and the second communication contacts provide a second data signal different from the first data signal received at the first communication contacts; a power management module (e.g., 610, Figures 6A-6B ) including a power conversion circuit configured to convert a power signal between the first power contacts of the logic connector of the first interconnection system and the second power contacts of the integrated connector of the second interconnection system; and a communication conversion module (e.g., 620, Figures 6A-6B ) including processing circuitry configured to convert a message between the first communication contacts of the logic connector of the first interconnection system and the second communication contacts of the integrated connector of the second interconnection system.

[0094] Clause 2: The infusion module adapter system according to Clause 1, wherein: the first support contacts of the mechanical connector of the first interconnection system include a latching mechanism that supports physical continuity of the attachment to the control unit; and the second support contacts of the integrated connector of the second interconnection system include a latching mechanism that supports physical continuity of the attachment to the infusion pump.

[0095] Clause 3: The infusion module adapter system according to Clause 1 or Clause 2, wherein: the first power contact of the logic connector of the first interconnection system is configured to receive a first power signal from the control unit, wherein the first power signal is characterized by a first voltage, a first amplitude, or a first frequency; the power management module is configured to convert the first voltage, the first amplitude, or the first frequency into a second voltage, a second amplitude, or a second frequency; and the second power contact of the integrated connector of the second interconnection system is configured to transmit the second power signal to the infusion pump, wherein the second power signal is characterized by a second voltage, a second amplitude, or a second frequency.

[0096] Clause 4: The infusion module adapter system according to any one of Clauses 1-3, wherein: the first communication contact of the logic connector of the first interconnection system is configured to send messages to and receive messages from the control unit; the second communication contact of the integrated connector of the second interconnection system is configured to send messages to and receive messages from the infusion pump; and the processing circuit of the communication conversion module is configured to: convert the messages received from the control unit into a message format consumable by the infusion pump, and send the converted control unit messages to the infusion pump; and convert the messages received from the infusion pump into a message format consumable by the control unit, and send the converted infusion pump messages to the control unit.

[0097] Clause 5: The infusion module adapter system according to Clause 4, wherein the messages received from the control unit include pumping instructions.

[0098] Clause 6: The infusion module adapter system according to Clause 4, wherein the messages received from the infusion pump include pumping status or alarm data.

[0099] Clause 7: The infusion module adapter system according to any one of Clauses 1-6, wherein the processing circuit of the communication conversion module is configured to manage the state transition of the pump state of the infusion pump.

[0100] Clause 8: The infusion module adapter system according to any one of Clauses 1-7, wherein the processing circuit of the communication conversion module is configured to receive programming updates and facilitate the interoperability of multiple infusion pumps.

[0101] Clause 9: The infusion module adapter system according to any one of Clauses 1-8, wherein the infusion module adapter system further includes a wireless transceiver.

[0102] Clause 10: The infusion module adapter system according to Clause 9, wherein the processing circuit of the communication conversion module is configured to receive firmware updates via the wireless transceiver.

[0103] Clause 11: The infusion module adapter system according to Clause 9, wherein the processing circuit of the communication conversion module is configured to transmit logging and / or asset tracking messages via the wireless transceiver.

[0104] Clause 12: An infusion module adapter system according to any one of Clauses 1 - 11, wherein the processing circuit of the communication conversion module is configured to: verify compatibility with an infusion pump when the infusion pump is attached to the infusion module adapter system.

[0105] Clause 13: The infusion module adapter system according to Clause 12, wherein the processing circuit of the communication conversion module is configured to verify compatibility by validating an authorization code stored in a data storage device of the infusion module adapter system.

[0106] Clause 14: The infusion module adapter system according to Clause 12, wherein the processing circuit of the communication conversion module is configured to verify compatibility by validating (i) the firmware or software versions of the control unit and the infusion module adapter system, (ii) the infusion module adapter system and the infusion pump, and / or (iii) the control unit and the infusion pump.

[0107] Clause 15: The infusion module adapter system according to Clause 12, wherein the processing circuit of the communication conversion module is configured to verify compatibility by validating (i) the cross - compatibility, product - level compatibility, and / or version - level compatibility of the control unit and the infusion module adapter system, (ii) the infusion module adapter system and the infusion pump, and / or (iii) the control unit and the infusion pump.

[0108] Clause 16: The infusion module adapter system according to any one of Clauses 1 - 15, wherein the mechanical connector of the first interconnection system is a mechanical modular interconnection (M - MIC) connector.

[0109] Clause 17: The infusion module adapter system according to any one of Clauses 1 - 16, wherein the logic connector of the first interconnection system is an electrical modular interconnection (E - MIC) connector.

[0110] Clause 18: The infusion module adapter system according to any one of Clauses 1 - 17, wherein the integrated connector of the second interconnection system is an inter - unit interface (IUI) connector.

[0111] Clause 19: The infusion module adapter system according to any one of Clauses 1 - 18, wherein: the mechanical connector of the first interconnection system and the integrated connector of the second interconnection system are disposed in the upper part of the infusion module adapter system; and the logic connector of the first interconnection system is disposed in the lower part of the infusion module adapter system.

[0112] Clause 20: An infusion module adapter system according to any one of Clauses 1-18, wherein: a mechanical connector of the first interconnection system is provided in an upper part of the infusion module adapter system; and a logical connector of the first interconnection system and an integrated connector of the second interconnection system are provided in a lower part of the infusion module adapter system.

[0113] Further contemplate

[0114] It will be understood that the specific order or hierarchy of steps in the disclosed processes are illustrations of example methods. Based on design preferences, it will be understood that the specific order or hierarchy of steps in a process may be rearranged. Some steps may be performed simultaneously. The appended method claims present the elements of the various steps in an example order and are not meant to be limited to the specific order or hierarchy presented.

[0115] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The foregoing description provides various examples of the subject technology, and the subject 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 applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, where a reference to an element in the singular is not intended to mean "one and only one" but "one or more" unless specifically so stated. The term "some" as used herein means one or more. Masculine pronouns (e.g., his) include feminine and neuter genders (e.g., her and its), and vice versa. Headings and subheadings, if any, are used for convenience only and do not limit the invention described herein.

[0116] The predicates "configured to", "operable to", and "programmed to" do not imply any particular tangible or intangible modification of the subject, but are intended to be used interchangeably. For example, a processor configured to monitor and control operations or components may also mean 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 may be interpreted as the processor being programmed to execute code or operable to execute code.

[0117] As used herein, the term automatic may include being performed by a computer or machine without user intervention, e.g., by instructions from a computer or machine or other initiating mechanism in response to a predicated action. The word "example" is used herein to mean "serving as an example or illustration". Any aspect or design described herein as an "example" is not necessarily to be construed as preferred or superior to other aspects or designs.

[0118] Phrases such as "aspect" do not imply that the aspect is essential to the subject technology or that the aspect applies to all configurations of the subject technology. Disclosures 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 "aspect" may refer to one or more aspects, and vice versa. Phrases such as "embodiment" do not imply that the embodiment is essential to the subject technology or that the embodiment applies to all configurations of the subject technology. Disclosures 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 "embodiment" may refer to one or more embodiments, and vice versa. Phrases such as "configuration" do not imply that the configuration is essential to the subject technology or that the configuration applies to all configurations of the subject technology. Disclosures related to a configuration may apply to all configurations, or one or more configurations. A configuration may provide one or more examples. Phrases such as "configuration" may refer to one or more configurations, and vice versa.

[0119] As used herein, a "user interface" (also referred to as an interactive user interface, graphical user interface, or UI) may refer to a web-based interface that includes data fields and / or other control elements for receiving input signals or providing electronic information and / or providing information to a user in response to any received input signal. The control elements may include dials, buttons, icons, selectable areas, or other perceivable markers presented via the UI that, when interacted with (e.g., clicked, touched, selected, etc.) via the UI, initiate a data exchange with the device presenting the UI. Technologies such as HyperText Markup Language (HTML), FlashTM, JavaTM,.NETTM, web services, or rich site summary (RSS) may be utilized to implement the UI in whole or in part. In some embodiments, the UI may be included in a stand-alone client (e.g., a thick client, fat client) that is configured to communicate (e.g., send or receive data) according to one or more of the aspects described. The communication may be to or from a medical device or a server that communicates with the medical device.

[0120] As used herein, the term "determine" or "determination" includes a variety of actions. For example, "determination" can include estimating, calculating, processing, deriving, generating, obtaining, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, etc. without user intervention via a hardware component. Additionally, "determination" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. without user intervention via a hardware component. "Determination" can include parsing, selecting, choosing, establishing, etc. without user intervention via a hardware component.

[0121] As used herein, the term "provide" or "supply" includes a variety of actions. For example, "supply" can include storing a value in a location of a storage device for subsequent retrieval, directly sending a value to a recipient via at least one wired or wireless communication medium, sending or storing a reference to a value, etc. "Supply" can also include encoding, decoding, encrypting, decrypting, validating, verifying, etc. via a hardware component.

[0122] As used herein, the term "message" includes a variety of formats for communicating (e.g., sending or receiving) information. A message can include a machine-readable aggregation such as an XML document, a fixed-field message, a comma-separated message, JSON, a custom protocol, or the like. In some embodiments, a message can include a signal for sending one or more representations of information. When recited in the singular, it is understood that a message can be composed, sent, stored, received, etc. in multiple parts.

[0123] As used herein, the term "selectively" or "selective" includes a variety of actions. For example, a "selective" process can include determining one option from a plurality of options. A "selective" process can include one or more of dynamically determined inputs, pre-configured inputs, or user-initiated inputs for making a determination. In some embodiments, an n-input switch can be included to provide a selective function, where n is the number of inputs for making a selection.

[0124] As used herein, the term "correspond to" or "corresponding to" includes a structural, functional, quantitative, and / or qualitative correlation or relationship between two or more objects, data sets, information, etc., preferably, where the correspondence or relationship can be used to transform one or more of the two or more objects, data sets, information, etc. to appear the same or equal. One or more of a threshold, a value range, fuzzy logic, pattern matching, a machine learning evaluation model, or a combination thereof can be used to evaluate the correspondence. The correspondence relationship can be based on a series of values, such as the air volume accumulated over a period of time.

[0125] In some embodiments, the generated or detected data may be forwarded to a "remote" device or location, where "remote" means a location or device other than the location or device where the program is executed. For example, a remote location may be another location in the same city (e.g., an office, a laboratory, etc.), another location in a different city, another location in a different state, another location in a different country, etc. Thus, when one project is indicated as "remote" from another project, this means that the two projects may be in the same room but separated, or at least in different rooms or different buildings, and may be at least one mile, ten miles, or at least one hundred miles apart. "Communicating" information involves sending the data representing the information as an electrical signal over a suitable communication channel (e.g., a private or public network). "Forwarding" an item means any way of taking the item from one location to the next, whether by physically transporting the item or otherwise (where possible), and in the case of data at least, includes physically transporting the medium carrying the data or causing the data to be communicated. Examples of communication media include radio or infrared transmission channels and network connections to another computer or networked device, as well as the Internet or including email transmissions and information recorded on websites, etc.

Claims

1. An infusion module adapter system, configured to couple a control unit to an infusion pump, the infusion module adapter system comprising: A first interconnect system, located on a first side of the adapter system, and comprising: a mechanical connector comprising a first support contact and configured to mechanically couple to a corresponding mechanical connector on the control unit; and a logic connector including a first power contact and a first communication contact and configured to logically couple to a corresponding logic connector on the control unit; a second interconnect system located on a second side of the adapter system and comprising: an integrated connector comprising a second support contact, a second power contact, and a second communication contact, and configured for mechanical and logical coupling to a corresponding integrated connector on the infusion pump, wherein the second power contact provides a second power signal different from a first power signal received at the first power contact, and the second communication contact provides a second data signal different from a first data signal received at the first communication contact; a power management module including a power conversion circuit configured to convert a power signal between a first power contact of a logic connector of the first interconnect system and a second power contact of an integrated connector of the second interconnect system; and A communication conversion module includes a processing circuit configured to convert messages between a first communication contact of a logical connector of the first interconnect system and a second communication contact of an integrated connector of the second interconnect system.

2. The infusion module adapter system of claim 1, wherein: the first supporting contact of the mechanical connector of the first interconnect system includes a latching mechanism that supports physical continuity of attachment to the control unit; and The second supporting contact of the integrated connector of the second interconnect system includes a latching mechanism that supports physical continuity of attachment to the infusion pump.

3. The infusion module adapter system of claim 1 or claim 2, wherein: The first power contact of the logic connector of the first interconnect system is configured to receive the first power signal from the control unit, wherein the first power signal is characterized by a first voltage, a first amplitude, or a first frequency; The power management module is configured to convert the first voltage, the first amplitude, or the first frequency into a second voltage, a second amplitude, or a second frequency; and The second power contact of the integrated connector of the second interconnect system is configured to transmit the second power signal to the infusion pump, wherein the second power signal is characterized by the second voltage, the second amplitude, or the second frequency.

4. The infusion module adapter system of claim 1 or claim 2, wherein: The first communication contact of the logic connector of the first interconnection system is configured to send messages to and receive messages from the control unit; The second communication contact of the integrated connector of the second interconnect system is configured to send messages to and receive messages from the infusion pump; and The processing circuit of the communication conversion module is configured as follows: converting a message received from the control unit into a message format that can be consumed by the infusion pump, and sending the converted control unit message to the infusion pump; as well as A message received from the infusion pump is converted into a message format that can be consumed by the control unit, and the converted infusion pump message is sent to the control unit.

5. The infusion module adapter system of claim 4, wherein: The message received from the control unit includes a pumping instruction.

6. The infusion module adapter system of claim 4, wherein: Messages received from the infusion pump include pumping status or alarm data.

7. The infusion module adapter system according to claim 1 or claim 2, wherein: The processing circuitry of the communication transition module is configured to manage state transitions of a pump state of the infusion pump.

8. The infusion module adapter system according to claim 1 or claim 2, wherein: The processing circuitry of the communication conversion module is configured to receive programming updates and facilitate interoperation of multiple infusion pumps.

9. The infusion module adapter system according to claim 1 or claim 2, wherein: The infusion module adapter system also includes a wireless transceiver.

10. The infusion module adapter system of claim 9, wherein: The processing circuitry of the communication conversion module is configured to receive a firmware update via the wireless transceiver.

11. The infusion module adapter system of claim 9, wherein: The processing circuitry of the communication conversion module is configured to transmit logging and / or asset tracking messages via the wireless transceiver.

12. The infusion module adapter system of claim 1 or claim 2, wherein: The processing circuitry of the communication conversion module is configured to verify compatibility with the infusion pump when the infusion pump is attached to the infusion module adapter system.

13. The infusion module adapter system of claim 12, wherein: The processing circuitry of the communication conversion module is configured to verify compatibility by verifying an authorization code stored in a data storage device of the infusion module adapter system.

14. The infusion module adapter system of claim 12, wherein: The processing circuitry of the communication conversion module is configured to verify compatibility by verifying firmware or software versions of: (i) the control unit and the infusion module adapter system, (ii) the infusion module adapter system and the infusion pump, and / or (iii) the control unit and the infusion pump.

15. The infusion module adapter system of claim 12, wherein: The processing circuit of the communication conversion module is configured to verify compatibility by verifying the cross-compatibility, product-level compatibility and / or version-level compatibility of: (i) the control unit and the infusion module adapter system, (ii) the infusion module adapter system and the infusion pump, and / or (iii) the control unit and the infusion pump.

16. The infusion module adapter system of claim 1 or claim 2, wherein the mechanical connector of the first interconnect system is a mechanical modular interconnect (M-MIC) connector.

17. The infusion module adapter system of claim 1 or claim 2, wherein the logic connector of the first interconnect system is an electrical modular interconnect (E-MIC) connector.

18. The infusion module adapter system of claim 1 or claim 2, wherein the integrated connector of the second interconnect system is an inter-unit interface (IUI) connector.

19. The infusion module adapter system of claim 1 or claim 2, wherein: the mechanical connector of the first interconnect system and the integrated connector of the second interconnect system being disposed in an upper portion of the infusion module adapter system; and The logic connector of the first interconnect system is disposed in a lower portion of the infusion module adapter system.

20. The infusion module adapter system of claim 1 or claim 2, wherein: The mechanical connector of the first interconnect system is disposed in an upper portion of the infusion module adapter system; and The logic connector of the first interconnect system and the integrated connector of the second interconnect system are disposed in a lower portion of the infusion module adapter system.

Images