Streamlining pairing between multi-pump infusion systems and mobile devices

Abstract

An example system for pairing multiple ambulatory infusion pumps with a mobile device includes first and second ambulatory infusion pumps, as well as packaging therefor. The packaging features a machine-readable code that encodes a first unique identifier associated with the first ambulatory infusion pump. The first ambulatory infusion pump includes a first memory that stores the first unique identifier, and the second ambulatory infusion pump includes second memory that stores a second unique identifier. Additionally, the first ambulatory infusion pump is configured to detect a pairing request for pairing with a mobile device, authenticate the mobile device using the first unique identifier, and then pair with the mobile device. Moreover, the second ambulatory infusion pump is configured to authenticate the mobile device using a second unique identifier and pair with the mobile device after authenticating the mobile device.

Description

Streamlining Pairing BetweenMulti-Pump Infusion Systems and Mobile DevicesTECHNICAL FIELD

[0001] The present disclosure relates, generally, to medical devices and, more specifically, to ambulatory infusion pumps and processes for pairing said pumps with mobile devices.BACKGROUND

[0002] Ambulatory infusion pumps have revolutionized medication delivery for patients outside of traditional hospital settings. For people with diabetes, these devices offer greater freedom and flexibility in their daily lives, removing the need for regular insulin injections or the bulky equipment associated therewith.

[0003] Notwithstanding recent developments in the field, there remain opportunities for further improvements to ambulatory infusion technologies. Many modern pumps, for instance, remain difficult to use and generate significant amounts of waste. Additional innovation in this space promises to further aid diabetics in managing their blood-glucose levels and improving their overall quality of life.SUMMARY

[0004] The innovations discussed herein are particularly relevant to multi-pump infusion systems that include two or more ambulatory infusion pumps. These pumps are at least somewhat reusable, thus reducing costs to the patient and offering a more environmental solution for mobile medication management. The pumps can be rechargeable, too, allowing the patient to use one pump while another is being charged.

[0005] Of course, introducing additional pumps runs the risk of over-complicating or over- extending the pump-initialization process. Thus, one aim of the present disclosure is to streamline that process for multi-pump systems. This is especially important for ambulatory infusion pumps that lack physical interfaces (e.g., for waterproofing purposes) as these pumps are generally more difficult to pair with mobile devices.

[0006] One solution discussed herein allows a user to pair two or more ambulatory infusion pumps with a mobile device based on an initialization process not unlike that required for a standard, single-pump system. For example, in some embodiments, the first ambulatory infusion pump includes pairing information for the other ambulatory infusion pumps. Thus, after the mobiledevice pairs with the first pump, it can then automatically initiate pairing with the other pumps in the system based on pairing information received from the first pump.

[0007] Exemplary embodiments include the following:

[0008] A System. The system is for pairing multiple ambulatory infusion pumps with a mobile device. It includes a first ambulatory infusion pump, a second ambulatory infusion pump, and packaging for the first and second ambulatory infusion pumps. The packaging features a machine- readable code that encodes at least a first unique identifier associated with the first ambulatory infusion pump. The first ambulatory infusion pump includes a first memory that stores the first unique identifier, and the first ambulatory infusion pump is configured to detect a pairing request for pairing with a mobile device and then authenticate the mobile device using the first unique identifier. The first unique identifier is retrieved by the mobile device from the machine-readable code featured on the packaging. The first ambulatory infusion pump is also configured to pair with the mobile device after authenticating the mobile device. Additionally, the second ambulatory infusion pump includes a second memory that stores a second unique identifier associated with the second ambulatory infusion pump, and the second ambulatory infusion pump is configured to authenticate the mobile device using the second unique identifier and pair with the mobile device after authenticating the mobile device.

[0009] An Ambulatory Infusion Pump. The pump includes a first memory and a processor. The first memory stores a first unique identifier associated with the ambulatory infusion pump and a second unique identifier associated with a second ambulatory infusion pump. The processor is configured to detect a pairing request for pairing the ambulatory infusion pump with a mobile device. The processor is also configured to authenticate the mobile device using the first unique identifier after detecting the pairing request. Additionally, the processor is configured to, after authenticating the mobile device using the first unique identifier, pair the ambulatory infusion pump with the mobile device and provide the second unique identifier to the mobile device. The second ambulatory infusion pump includes a second memory that stores the second unique identifier. Also, the second ambulatory infusion pump is configured to authenticate the mobile device using the second unique identifier and pair with the mobile device after authenticating the mobile device using the second unique identifier.

[0010] A Computer-Implemented Method. The method is for pairing multiple ambulatory infusion pumps with a mobile device. It includes detecting a pairing request for pairing a firstambulatory infusion pump with a mobile device. The first ambulatory infusion pump includes a first memory that stores a first unique identifier associated with the first ambulatory infusion pump and a second unique identifier associated with a second ambulatory infusion pump. The method also includes authenticating the mobile device using the first unique identifier after detecting the pairing request. Additionally, the method includes, after authenticating the mobile device using the first unique identifier, pairing the first ambulatory infusion pump with the mobile device and providing the second unique identifier from the first ambulatory infusion pump to the mobile device. The second ambulatory infusion pump includes a second memory that stores the second unique identifier. Also, the second ambulatory infusion pump is configured to authenticate the mobile device using the second unique identifier and pair with the mobile device after authenticating the mobile device using the second unique identifier.

[0011] A Method for Manufacturing Ambulatory Infusion Pumps. The method includes providing a first ambulatory infusion pump including a first memory and storing a first unique identifier in the first memory, where the first unique identifier is associated with the first ambulatory infusion pump. The method also includes configuring the first ambulatory infusion pump to detect a pairing request for pairing with a mobile device and then authenticate the mobile device using the first unique identifier after detecting the pairing request. The first unique identifier is retrieved by the mobile device from a machine-readable code. The method also includes configuring the first ambulatory infusion pump to pair with the mobile device after authenticating the mobile device. Additionally, the method includes providing a second ambulatory infusion pump including a second memory and storing a second unique identifier in the second memory. Further, the method includes configuring the second ambulatory infusion pump to authenticate the mobile device using the second unique identifier and pair with the mobile device after authenticating the mobile device. Moreover, the method includes providing packaging for the first and second ambulatory infusion pumps, where the packaging features a machine-readable code that encodes at least the first unique identifier. Furthermore, the method includes inserting the first and second ambulatory infusion pumps into the packaging.

[0012] Based on the Detailed Description below, other configurations of the subject technology will be apparent to those skilled in the art. The Detailed Description describes various configurations of the subject technology, particularly with respect to illustrations thereof. Notwithstanding, the subject technology is capable of other and different configurations, and itsseveral details are capable of modification in various other respects - all without departing from the scope of the subject technology. The Drawings and Detailed Description are therefore presented as illustrative in nature and should not be construed as restricting the present disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0013] For a better understanding of the present disclosure, reference should be made to the Detailed Description, below, in conjunction with the following drawings. Like reference numerals refer to corresponding parts throughout the figures and the description.

[0014] Figures 1A and IB illustrate an example ambulatory infusion pump 100, according to various aspects of the subject technology.

[0015] Figures 2A through 2D illustrate example multi-pump infusion systems, according to various aspects of the subject technology.

[0016] Figure 3 illustrates an example process 300 for pairing multiple ambulatory infusion pumps with a mobile device, according to various aspects of the subject technology.DETAILED DESCRIPTION

[0017] Figures 1A and IB illustrate an example ambulatory infusion pump 100, according to various aspects of the subject technology. In Figure 1A, the pump 100 is adhered to the arm of a user 104 via an adhesive patch 102. On the backside of the pump 100, a cannula or infusion needle inserted into the user’ s arm allows the pump to provide the user 104 with a medicament. As persons with skill in the art will appreciate, the pump 100 can be configured to provide the medicament to the user according to a regular routine or based on various physiological parameters, such as the user’s blood-glucose level or the like.

[0018] In Figure IB, the top and bottom portions 110-111 of the ambulatory infusion pump 100 are separated to reveal a cartridge 112 containing a fluid medicament, such as insulin or glucagon. The cartridge 112 is fluidically connected to the aforenoted cannula or infusion needle such that the pump 100 can provide the fluid therein to the user 104 by operating a drive mechanism of the ambulatory infusion pump 100.

[0019] The top and bottom portions 110-111 are separable to allow for removal of the cartridge 112. For example, after the fluid in the cartridge 112 is exhausted, the user 104 can separate the top and bottom portions 110-110 of the pump 100 to remove the cartridge 112 and replace it with another one. Thereafter, the user can close the pump 100 by bringing the top and bottom portions 110-111 together and then rotating them with respect to each other, as suggestedby arrows 114-1 15. As compared to disposable infusion pumps, this configuration may result in less waste and may also be cheaper for the user 104.

[0020] As discussed in more detail below, the ambulatory infusion pump 100 can also include memory (e.g., random-access memory, non-transitory memory), a processor, an accelerometer, a wireless charging system, or a near-field communication (NFC) component (e g., an NFC tag, an NFC reader). The memory may store one or more unique identifiers, such as a unique identifier associated with the pump 100 and for authenticating a mobile device (e.g., a smartphone, a laptop). The memory may also store instructions for execution by the processor, which may cause the pump 100 to perform operations such as those discussed herein. And, as discussed in more detail below, the accelerometer, wireless charging system, and NFC component can be used to detect a pairing request for pairing the pump 100 with a mobile device.

[0021] Figures 2A through 2D illustrate example multi-pump infusion systems 200, 220, 240, and 260, according to various aspects of the subject technology. As noted above, multi-pump infusion systems offer significant benefits, including the reduction of both cost and waste. However, these systems can also be difficult for users to setup (e.g., pair to smartphone), multiplying the pain points associated with a single-pump system across two or more infusion pumps. The following discussion touches on some of the pain points associated with pairing a mobile device to multiple ambulatory infusion pumps, while also providing innovative solutions for alleviating said pain points without sacrificing the benefits of multi-pump infusion systems.

[0022] Many of the innovations heretofore discussed with regard to the multi-pump infusion systems 200, 220, 240, and 260 are likewise applicable to systems that include a mobile device (e.g., mobile device 202), an ambulatory infusion pump (e.g., pump 204, 205), and another electronic device (e.g., a continuous glucose monitor, a fitness tracker, a smartwatch) in addition to or in place of pumps 204 or 205. For example, the pairing innovations discussed for figures 2B to 2D could be applied to such systems.

[0023] Figure 2B, for instance, illustrates a memory 222 that includes pairing information for the second pump 205; this memory 222 can also or alternatively include pairing information for the aforenoted other electronic device, which the mobile device 202 can use for authentication with the other electronic device. Similarly, the machine-readable code 244 of figure 2C can encode pairing information for the other electronic device, and the other electronic device can be prepaired to a user’s account as discussed for figure 2D.

[0024] Referring now to figure 2A, a mobile device 202 pairs with a first ambulatory infusion pump 204 (e.g., pump 100) and a second ambulatory infusion pump 205 (e.g., pump 100). This pairing process can be initiated by a user action indicative of the user’s intent to pair one of the infusion pumps 204-205 with the mobile device 202. As used herein, “pairing request” refers to such an action. For example, if the pump has a physical interface (e g., a button), the pairing request may be as simple as pressing a button for a certain amount of time.

[0025] However, in some embodiments, the pumps 204-205 do not include such an interface and are instead configured to detect a pairing request via other means. Detecting the pairing request may include, for example, detecting a predetermined motion pattern via an accelerometer, detecting a predetermined interaction with a wireless charger, detecting a signal from an NFC component, and so on. For example, the first pump 204 can be configured to determine that the user (e.g., user 104) intends to pair the pump 204 with the mobile device after the pump 204 is placed on a wireless charger, removed from the charger within a predetermined amount of time (e.g., five seconds), and then moved in a particular way (e.g., shaken three times).

[0026] In some embodiments, the second pump 205 is provided to the user in a Bluetooth low- energy (BLE) pairing mode. For example, the manufacturer can place the pump 205 in the BLE pairing mode prior to shipping it to the user. Placing the pump 205 into the BLE pairing mode may remove the need for the user to manually place the second pump 205 into a pairing mode with a pairing request, thus simplifying the pairing process for the user. Additionally, according to some embodiments, the first pump 204 is also provided to the user in a BLE pairing mode such that the user does not need to place either of the first or second pumps 204-205 into pairing mode.

[0027] After either of the pumps 204-205 detects a pairing request, the pump 204 or 205 then attempts to authenticate the mobile device 202. (Note, in embodiments where one or both of the pumps 204-205 are provided to the user while already in BLE pairing mode, the pumps 204-205 may automatically attempt to authenticate the mobile device 202 while the pumps 204-205 are within a pairing distance of the mobile device 202.) This authentication can be accomplished via multiple processes; however, it generally includes confirmation of a shared secret. For example, the first ambulatory infusion pump 204 may attempt to authenticate the mobile device 202 by determining whether the mobile device 202 is aware of a unique identifier associated with the first pump 204. If authentication is successful, the pump 204 or 205 then pairs with the mobiledevice 202 and exchanges data therewith, allowing the mobile device 202 to control the pump 204 or 205 or at least receive information from it.

[0028] Pairing the first pump 204 to the mobile device 202 takes time, especially when the pairing process requires involved interaction from the user. And requiring the user to repeat that process for the second pump 205 is time consuming and inconvenient.

[0029] As illustrated Figure 2B, the pairing process can be streamlined by storing pairing information for the second pump 205 in memory 222 of the first pump 204. This pairing information may include, for instance, a unique identifier associated with the second pump 205. After the first pump 204 successfully authenticates the mobile device 202 or pairs with the mobile device 202, the pump 204 can then provide the pairing information for the second pump 205 to the mobile device 202, which the mobile device 202 can then use for authentication with the second pump 205. In this manner, the mobile device may only need pairing information (e.g., a unique identifier) for the first pump 204 in order to pair with both the first and second pumps 204-205.

[0030] Additionally, as illustrated in Figure 2C, the pairing process can be streamlined by featuring a machine-readable code 244 (e.g., a barcode, a quick response code) on packaging 246 for the pumps 204-205, where the code 244 encodes the pairing information for at least one or both of the ambulatory infusion pumps 204-205. The mobile device 202 can capture an image of the code 244 using a camera 242 and then determine the pairing information based on the captured image, further simplifying the pairing process as compared to requiring the user to manually provide the mobile device 202 with the pairing information.

[0031] In some embodiments, the machine-readable code also encodes a link (e.g., a URL) to a website for installation of an application for managing the first and second ambulatory infusion pumps 204-205. The application may, for instance, assist the user by providing reminders regarding pump battery levels or by visualizing data transmitted from the pumps 204-205. After the mobile device 202 scans the code 244, it can install the pump-management application, removing the need for the user to locate the pump-management application in an application storefront and install it themselves. Further, in some embodiments, one or more of the pumps 204- 205 is configured to confirm installation of the application on the mobile device 202 prior to or after pairing with the mobile device 202.

[0032] Further, as illustrated in Figure 2D, the pairing process can be streamlined by involving a remote server 262 in the process. The pumps 204-205 can be associated with a user account, forinstance, before the pumps 204-205 are even provided to the user. After receiving the pumps 204- 205, the user may then be able to automatically pair them to their mobile device 202, for instance, by logging into the user account via a pump-management application, such as the application discussed above with respect to Figure 2C. After logging into their account, the pump-management application can then communicate with the server 262, determine that the pumps 204-205 are paired to the user account, and initiate the pairing process accordingly. In this manner, the user may be able to skip one or more steps of the typical pairing process.

[0033] In some embodiments, the server 262 is also used to simplify pairing for replacement pumps. For example, if the user orders a replacement for the first pump 204, the replacement pump can be associated with their account and then automatically paired to the user device 202 after the user receives the new pump. This may be especially useful where the pump to be replaced is configured to operate according to particular settings. After the replacement pump is paired with the mobile device 202, the server 262 or the mobile device 202 can then provide the particular settings to the replacement pump, thus removing the need for the user to reconfigure the new pump.

[0034] Figure 3 illustrates an example process 300 for pairing multiple ambulatory infusion pumps with a mobile device, according to various aspects of the subject technology. The operations of process 300 can be carried any of the devices discussed above with respect to Figures 1A through 2D, such as one or more ambulatory infusion pumps (e.g., pump 100, pump 204-205), a mobile device (e.g., mobile device 202), or a server (e g., server 262). In some embodiments, the process 300 is executed by a processor configured to execute instructions stored in a non-transitory, computer-readable medium, where the instructions correspond to the various operations of the process 300.

[0035] As with figures 2 A to 2D, the innovations discussed for figure 3 are likewise applicable for pairing a mobile device (e.g., mobile device 202) with one or more infusion pumps (e.g., pumps 204, 205) and another electronic device (e.g., a continuous glucose monitor, a smartwatch, a fitness tracker). Accordingly, the following discussion of pairing first and second ambulatory infusion pumps with a mobile device should also be understood as disclosing and teaching pairing an ambulatory infusion pump and another electronic device with a mobile device.

[0036] The process 300 includes detecting (302) a pairing request for pairing a first ambulatory infusion pump (e.g., pump 204) with a mobile device (e.g., mobile device 202). The first ambulatory infusion pump comprises a first memory (e.g., memory 222) that stores a firstunique identifier (e.g., an alphanumeric code) associated with the first ambulatory infusion pump, as well as a second unique identifier (e.g., an alphanumeric code) associated with a second ambulatory infusion pump. Note, in some embodiments where the ambulatory infusion pump is already in a pairing mode (e.g., a BLE pairing mode), the process 300 does not include detecting (302) the pairing request.

[0037] The process 300 also includes authenticating (304) the mobile device with the first unique identifier. In some embodiments, the first unique identifier is encoded in a machine- or human-readable code featured on packaging (e.g., packaging 246) for the first ambulatory infusion pump or featured on the pump itself. The mobile device may retrieve the first unique identifier, for instance, by capturing an image of a machine-readable code that encodes the first unique identifier and then determining the first unique identifier based on the captured image. Likewise, in embodiments where the machine-readable code encodes the second unique identifier, the mobile device can retrieve the second unique identifier from the machine-readable code (e.g., based on a captured image thereof). After retrieving the first unique identifier, the mobile device can then authenticate with the first ambulatory infusion pump by proving to the first ambulatory infusion pump that the mobile device is aware of the first unique identifier.

[0038] If the authentication is successful, then the process continues with pairing (306) the first ambulatory infusion pump with the mobile device. Further, the process 300 includes providing (308) a second unique identifier from the first ambulatory infusion pump to the mobile device, whereafter the mobile device can use the second unique identifier to authenticate with the second ambulatory infusion pump. (Alternatively, in some embodiments, the mobile device retrieves the second unique identifier from a machine-readable code, like that discussed above with respect to the first unique identifier.) Like the first ambulatory infusion pump, the second ambulatory infusion pump may be configured to authenticate the mobile device using the second unique identifier and pair with the mobile device after authenticating the mobile device using the second unique identifier.

[0039] In some embodiments, the first ambulatory infusion pump further includes an accelerometer, and detecting the pairing request includes detecting a predetermined motion pattern via the accelerometer. For example, the predetermined motion pattern can be a predetermined number of shakes (e.g., three shakes) within a predetermined amount of time (e.g. three seconds).

[0040] In some embodiments, the first ambulatory infusion pump further includes a wireless charging system (e.g., a wireless charging receiver, power management circuitry), and detecting the pairing request includes detecting a predetermined interaction with a wireless charger via the wireless charging system. For example, the predetermined interaction can be connecting and then disconnecting the first ambulatory infusion pump to and from the wireless charger a predetermined number of times (e.g., five times) within a predetermined amount of time (e.g., ten seconds).

[0041] In some embodiments, the first ambulatory infusion pump further comprises an NFC component, the mobile device comprises another NFC component, and detecting the pairing request comprises detecting a signal from the other NFC component of the mobile device via the NFC component of the first ambulatory infusion pump.

[0042] In some embodiments, a third ambulatory infusion pump is for replacing either the first or second ambulatory infusion pump. Additionally, another machine-readable code encodes a third unique identifier associated with the third ambulatory infusion pump. The third ambulatory infusion pump comprises a third memory that stores the third unique identifier, and the third ambulatory infusion pump is configured to detect another pairing request for pairing with the mobile device, authenticate the mobile device with the third unique identifier after detecting the pairing request, and pair with the mobile device after authenticating the mobile device.

[0043] In some embodiments, the first ambulatory infusion pump is configured to operate according to first settings and the second ambulatory infusion pump is configured to operate according to second settings. Additionally, the third ambulatory infusion pump is configured to receive initialization settings after pairing with the mobile device, where the initialization settings are either the first settings or second settings based on whether the third ambulatory infusion pump is replacing the first or second ambulatory infusion pump, respectively.

[0044] In some embodiments, the first ambulatory infusion pump is further configured to operate in a low-power mode prior to detecting the pairing request and then operate in a standardpower mode after detecting the pairing request. Additionally, the first ambulatory infusion pump is configured to send a wake-up signal to the second ambulatory infusion pump after detecting the pairing request, where the second ambulatory infusion pump is further configured to operate in the low-power mode prior to receiving the wake-up signal from the first ambulatory infusion pump and then operate in the standard-power mode after receiving the wake-up signal.

[0045] In some embodiments, the machine-readable code further encodes a link to a website for installation of an application for managing the first and second ambulatory infusion pumps, and the first ambulatory infusion pump is further configured to confirm installation of the application on the mobile device prior to or after pairing with the mobile device.

[0046] In some embodiments, the mobile device is configured to automatically initiate pairing with the second ambulatory infusion pump after pairing with the first ambulatory infusion pump. For example, a user may cause the mobile device to initiate pairing with the first ambulatory infusion pump by pressing a pairing button displayed at the mobile device. This may cause the mobile device to pair with the first ambulatory infusion pump as well as the second ambulatory infusion pump - without requiring the user to again press the pairing button or perform other actions required to facilitate pairing with the first ambulatory infusion pump, such as those discussed above with respect to the first ambulatory infusion pump and pairing requests.

[0047] Illustrative Clauses. For further reference, example aspects of the present disclosure are included below as numbered clauses. These clauses are provided for illustrative purposes and are not intended to limit the subject technology.

[0048] Clause 1. A system for pairing multiple ambulatory infusion pumps with a mobile device, the system comprising: a first ambulatory infusion pump, a second ambulatory infusion pump, and packaging for the first and second ambulatory infusion pumps, wherein the packaging features a machine-readable code that encodes at least a first unique identifier associated with the first ambulatory infusion pump; wherein the first ambulatory infusion pump comprises a first memory that stores the first unique identifier, and the first ambulatory infusion pump is configured to: detect a pairing request for pairing with a mobile device; authenticate the mobile device using the first unique identifier after detecting the pairing request, wherein the first unique identifier is retrieved by the mobile device from the machine-readable code featured on the packaging; and pair with the mobile device after authenticating the mobile device; and wherein the second ambulatory infusion pump comprises a second memory that stores a second unique identifier associated with the second ambulatory infusion pump, and the second ambulatory infusion pump is configured to: authenticate the mobile device using the second unique identifier; and pair with the mobile device after authenticating the mobile device.

[0049] Clause 2. The system of Clause 1, wherein: the first memory of the first ambulatory infusion pump further stores the second unique identifier and the first ambulatory infusion pumpis further configured to provide the second unique identifier to the mobile device after authenticating the mobile device; or the machine-readable code further encodes the second unique identifier and the second unique identifier is retrieved by the mobile device from the machine- readable code featured on the packaging.

[0050] Clause 3. The system of either Clause 1 or 2, wherein: the mobile device is configured to automatically initiate pairing with the second ambulatory infusion pump after pairing with the first ambulatory infusion pump.

[0051] Clause 4. The system of any one of Clauses 1 through 3, wherein: the first ambulatory infusion pump further comprises an accelerometer; and detecting the pairing request comprises detecting a predetermined motion pattern via the accelerometer.

[0052] Clause 5. The system of any one of Clauses 1 through 4, wherein: the first ambulatory infusion pump further comprises a wireless charging system; and detecting the pairing request comprises detecting a predetermined interaction with a wireless charger via the wireless charging system.

[0053] Clause 6. The system of any one of Clauses 1 through 5, wherein: the first ambulatory infusion pump further comprises a NFC component; the mobile device comprises another NFC component; and detecting the pairing request comprises detecting a signal from the other NFC component of the mobile device via the NFC component of the first ambulatory infusion pump.

[0054] Clause 7. The system of any one of Clauses 1 through 6, further comprising: a third ambulatory infusion pump for replacing either the first or second ambulatory infusion pump; and another machine-readable code that encodes a third unique identifier associated with the third ambulatory infusion pump; wherein the third ambulatory infusion pump comprises a third memory that stores the third unique identifier, and the third ambulatory infusion pump is configured to: detect another pairing request for pairing with the mobile device; authenticate the mobile device with the third unique identifier after detecting the pairing request; and pair with the mobile device after authenticating the mobile device.

[0055] Clause 8. The system of Clause 7, wherein: the first ambulatory infusion pump is configured to operate according to first settings and the second ambulatory infusion pump is configured to operate according to second settings; and the third ambulatory infusion pump is configured to receive initialization settings after pairing with the mobile device, wherein the initialization settings comprise (i) the first settings if the third ambulatory infusion pump isreplacing the first ambulatory infusion pump or (ii) the second settings if the third ambulatory infusion pump is replacing the second ambulatory infusion pump.

[0056] Clause 9. The system of any one of Clauses 1 through 8, wherein: the first ambulatory infusion pump is further configured to: operate in a low-power mode prior to detecting the pairing request; operate in a standard-power mode after detecting the pairing request; and send a wake-up signal to the second ambulatory infusion pump after detecting the pairing request; and the second ambulatory infusion pump is further configured to: operate in the low-power mode prior to receiving the wake-up signal from the first ambulatory infusion pump; and operate in the standardpower mode after receiving the wake-up signal.

[0057] Clause 10. The system of any one of Clauses 1 through 9, wherein: the machine- readable code further encodes a link to a website for installation of an application for managing the first and second ambulatory infusion pumps; and the first ambulatory infusion pump is further configured to confirm installation of the application on the mobile device prior to pairing with the mobile device.

[0058] Clause 11. An ambulatory infusion pump comprising: a first memory that stores a first unique identifier associated with the ambulatory infusion pump and a second unique identifier associated with a second ambulatory infusion pump; and a processor configured to: detect a pairing request for pairing the ambulatory infusion pump with a mobile device; authenticate the mobile device using the first unique identifier after detecting the pairing request; and after authenticating the mobile device using the first unique identifier, (i) pair the ambulatory infusion pump with the mobile device and (ii) provide the second unique identifier to the mobile device; wherein the second ambulatory infusion pump comprises a second memory that stores the second unique identifier, and the second ambulatory infusion pump is configured to (i) authenticate the mobile device using the second unique identifier and (ii) pair with the mobile device after authenticating the mobile device using the second unique identifier.

[0059] Clause 12. The ambulatory infusion pump of Clause 11, further comprising: an accelerometer, wherein detecting the pairing request comprises detecting a predetermined motion pattern via the accelerometer.

[0060] Clause 13. The ambulatory infusion pump of either Clauses 11 or 12, further comprising: a wireless charging system, wherein detecting the pairing request comprises detecting a predetermined interaction with a wireless charger via the wireless charging system.

[0061] Clause 14. The ambulatory infusion pump of any one of Clauses 1 1 through 13, further comprising: an NFC component, wherein the mobile device comprises another NFC component, and detecting the pairing request comprises detecting a signal from the other NFC component of the mobile device via the NFC component of the ambulatory infusion pump.

[0062] Clause 15. The ambulatory infusion pump of any one of Clauses 11 through 14, wherein: the processor is further configured to: operate in a low-power mode prior to detecting the pairing request; operate in a standard-power mode after detecting the pairing request; and send a wake-up signal to the second ambulatory infusion pump after detecting the pairing request; wherein the second ambulatory infusion pump is further configured to operate in the low-power mode prior to receiving the wake-up signal from the ambulatory infusion pump and operate in the standard-power mode after receiving the wake-up signal.

[0063] Clause 16. A computer-implemented method for pairing multiple ambulatory infusion pumps with a mobile device, the method comprising: detecting a pairing request for pairing a first ambulatory infusion pump with a mobile device, wherein the first ambulatory infusion pump comprises a first memory that stores a first unique identifier associated with the first ambulatory infusion pump and a second unique identifier associated with a second ambulatory infusion pump; authenticating the mobile device using the first unique identifier after detecting the pairing request; and after authenticating the mobile device using the first unique identifier: pairing the first ambulatory infusion pump with the mobile device; and providing the second unique identifier from the first ambulatory infusion pump to the mobile device; wherein the second ambulatory infusion pump comprises a second memory that stores the second unique identifier, and the second ambulatory infusion pump is configured to (i) authenticate the mobile device using the second unique identifier and (ii) pair with the mobile device after authenticating the mobile device using the second unique identifier.

[0064] Clause 17. The computer-implemented method of Clause 16, wherein: the first ambulatory infusion pump comprises an accelerometer; and detecting the pairing request comprises the first ambulatory infusion pump detecting a predetermined motion pattern via the accelerometer.

[0065] Clause 18. The computer-implemented method of either Clauses 16 or 17, wherein: the first ambulatory infusion pump further comprises a wireless charging system; and detecting thepairing request comprises the first ambulatory infusion pump detecting a predetermined interaction with a wireless charger via the wireless charging system.

[0066] Clause 19. The computer-implemented method of any one of Clauses 16 through 18, wherein: the first ambulatory infusion pump further comprises an NFC component; the mobile device comprises another NFC component; and detecting the pairing request comprises detecting a signal from the other NFC component of the mobile device via the NFC component of the first ambulatory infusion pump.

[0067] Clause 20. The computer-implemented method of any one of Clauses 16 through 19, further comprising: operating the first ambulatory infusion pump in a low-power mode prior to detecting the pairing request; operating the first ambulatory infusion pump in a standard-power mode after detecting the pairing request; and sending a wake-up signal from the first ambulatory infusion pump to the second ambulatory infusion pump after detecting the pairing request; wherein the second ambulatory infusion pump is further configured to operate in the low-power mode prior to receiving the wake-up signal from the first ambulatory infusion pump and operate in the standard-power mode after receiving the wake-up signal.

[0068] Clause 21. A method for manufacturing multiple ambulatory infusion pumps, the method comprising: providing a first ambulatory infusion pump comprising a first memory; storing a first unique identifier in the first memory, wherein the first unique identifier is associated with the first ambulatory infusion pump; configuring the first ambulatory infusion pump to: detect a pairing request for pairing with a mobile device; authenticate the mobile device using the first unique identifier after detecting the pairing request, wherein the first unique identifier is retrieved by the mobile device from a machine-readable code; and pair with the mobile device after authenticating the mobile device; providing a second ambulatory infusion pump comprising a second memory; storing a second unique identifier in the second memory; configuring the second ambulatory infusion pump to: authenticate the mobile device using the second unique identifier; and pair with the mobile device after authenticating the mobile device providing packaging for the first and second ambulatory infusion pumps, wherein the packaging features the machine-readable code that encodes at least the first unique identifier; and inserting the first and second ambulatory infusion pumps into the packaging.

[0069] Clause 22. The method for manufacturing of Clause 21, wherein: the method further comprises (i) storing the second unique identifier in the first memory and (ii) configuring the firstambulatory infusion pump to provide the second unique identifier to the mobile device after authenticating the mobile device; or the machine-readable code further encodes the second unique identifier and the second unique identifier is retrieved by the mobile device from the machine- readable code featured on the packaging.

[0070] Clause 23. The method of either Clause 21 or 22, wherein: the mobile device is configured to automatically initiate pairing with the second ambulatory infusion pump after pairing with the first ambulatory infusion pump.

[0071] Clause 24. The method for manufacturing of any one of Clauses 21 through 23, wherein: the first ambulatory infusion pump further comprises an accelerometer; and detecting the pairing request comprises detecting a predetermined motion pattern via the accelerometer.

[0072] Clause 25. The method for manufacturing of any one of Clauses 21 through 24, wherein: the first ambulatory infusion pump further comprises a wireless charging system; and detecting the pairing request comprises detecting a predetermined interaction with a wireless charger via the wireless charging system.

[0073] Clause 26. The method for manufacturing of any one of Clauses 21 through 25, wherein: the first ambulatory infusion pump further comprises an NFC component; the mobile device comprises another NFC component; and detecting the pairing request comprises detecting a signal from the other NFC component of the mobile device via the NFC component of the first ambulatory infusion pump.

[0074] Clause 27. The method for manufacturing of any one of Clauses 21 through 26, further comprising: providing a third ambulatory infusion pump for replacing either the first or second ambulatory infusion pump, wherein the third ambulatory infusion pump comprises a third memory; providing another machine-readable code that encodes a third unique identifier associated with the third ambulatory infusion pump; storing the third unique identifier in the third memory; configuring the third ambulatory infusion pump to: detect another pairing request for pairing with the mobile device; authenticate the mobile device with the third unique identifier after detecting the pairing request; and pair with the mobile device after authenticating the mobile device.

[0075] Clause 28. The method for manufacturing of Clause 27, further comprising: configuring the first ambulatory infusion pump to operate according to first settings; configuring the second ambulatory infusion pump to operate according to second settings; and configuring thethird ambulatory infusion pump to receive initialization settings after pairing with the mobile device, wherein the initialization settings comprise (i) the first settings if the third ambulatory infusion pump is replacing the first ambulatory infusion pump or (ii) the second settings if the third ambulatory infusion pump is replacing the second ambulatory infusion pump.

[0076] Clause 29. The method for manufacturing of any one of Clauses 21 through 28, further comprising: configuring the first ambulatory infusion pump to: operate in a low-power mode prior to detecting the pairing request; operate in a standard-power mode after detecting the pairing request; and send a wake-up signal to the second ambulatory infusion pump after detecting the pairing request; and configuring the second ambulatory infusion pump to: operate in the low-power mode prior to receiving the wake-up signal from the first ambulatory infusion pump; and operate in the standard-power mode after receiving the wake-up signal; and placing the first and second ambulatory infusion pumps into the low-power mode prior to inserting the first and second ambulatory infusion pumps into the packaging.

[0077] Clause 30. The method for manufacturing of any one of Clauses 21 through 29, further comprising: configuring the first ambulatory infusion pump to confirm installation of a pumpmanagement application prior to pairing with the mobile device, wherein the pump-management application is for management of the first and second ambulatory infusion pumps; wherein the machine-readable code further encodes a link to a website for installation of the pumpmanagement application.

[0078] Further Consideration. The specific order or hierarchy of steps in the processes disclosed herein is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged. Some of the steps may be performed simultaneously. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[0079] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. The previous 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 readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with thelanguage claims, wherein 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.” Unless specifically stated otherwise, the term “some” refers to one or more. Headings and subheadings, if any, are used for convenience only and do not limit the invention described herein.

[0080] The predicate words “configured to,” “operable to,” and “programmed to” do not imply any particular tangible or intangible modification of a subject, but rather are intended to be used interchangeably. For example, a processor configured to monitor and control an operation or a component may also mean the processor being programmed to monitor and control the operation or the processor being operable to monitor and control the operation. Likewise, a processor configured to execute code can be construed as a processor programmed to execute code or operable to execute code.

[0081] A phrase such as an “aspect” does not imply that such aspect is essential to the subject technology or that such aspect applies to all configurations of the subject technology. A disclosure relating to an aspect may apply to all configurations, or 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 an “implementation” does not imply that such implementation is essential to the subject technology or that such implementation applies to all configurations of the subject technology. A disclosure relating to an implementation may apply to all implementations, or one or more implementations. An implementation may provide one or more examples. A phrase such as “implementations” may refer to one or more embodiments and vice versa. A phrase such as a “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. A disclosure relating to a configuration may apply to all configurations, or one or more configurations. A configuration may provide one or more examples. A phrase such as a “configuration” may refer to one or more configurations and vice versa.

[0082] As used herein, the terms “determine” and “determining” encompass a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, generating, obtaining, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like via a hardware element without user intervention. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like via a hardware element without user intervention. “Determining” may includeresolving, selecting, choosing, establishing, and the like via a hardware element without user intervention.

[0083] As used herein, the term “message” encompasses a wide variety of formats for communicating (e.g., transmitting or receiving) information. A message may include a machine readable aggregation of information such as an XML document, fixed field message, comma separated message, JSON, a custom protocol, or the like. A message may, in some embodiments, include a signal utilized to transmit one or more representations of the information. While recited in the singular, it will be appreciated that a message may be composed, transmitted, stored, received, and so on in multiple parts.

[0084] As used herein, the term “selectively” or “selective” may encompass a wide variety of actions. For example, a “selective” process may include determining one option from multiple options. A “selective” process may include one or more of dynamically determined inputs, preconfigured inputs, or user-initiated inputs for making the determination. In some embodiments, an n-input switch may be included to provide selective functionality where n is the number of inputs used to make the selection.

[0085] As used herein, the terms “correspond” or “corresponding” encompasses a structural, functional, quantitative and / or qualitative correlation or relationship between two or more objects, data sets, information and / or the like, preferably where the correspondence or relationship may be used to translate one or more of the two or more objects, data sets, information and / or the like so to appear to be the same or equal. Correspondence may be assessed using one or more of a threshold, a value range, fuzzy logic, pattern matching, a machine-learning assessment model, or combinations thereof.

[0086] In any embodiment, data generated or detected can be forwarded to a “remote” device or location, where “remote,” means a location or device other than the location or device at which the program is executed. For example, a remote location could be another location (e.g., office, lab, etc.) in the same city, another location in a different city, another location in a different state, another location in a different country, etc. As such, when one item is indicated as being “remote” from another, what is meant is that the two items can be in the same room but separated, or at least in different rooms or different buildings, and can be at least one mile, ten miles, or at least one hundred miles apart. “Communicating” information references transmitting the data representing that information as electrical signals over a suitable communication channel (e.g., a private orpublic network). “Forwarding” an item refers to any means of getting that item from one location to the next, whether by physically transporting that item or otherwise (where that is possible) and includes, at least in the case of data, physically transporting a medium carrying the data or communicating the data. Examples of communicating media include radio or infra-red transmission channels as well as a network connection to another computer or networked device, and the internet or including email transmissions and information recorded on websites and the like.

Claims

CLAIMSWhat is claimed is:

1. A system for pairing multiple ambulatory infusion pumps with a mobile device, the system comprising: a first ambulatory infusion pump, a second ambulatory infusion pump, and packaging for the first and second ambulatory infusion pumps, wherein the packaging features a machine- readable code that encodes at least a first unique identifier associated with the first ambulatory infusion pump; wherein the first ambulatory infusion pump comprises a first memory that stores the first unique identifier, and the first ambulatory infusion pump is configured to: detect a pairing request for pairing with a mobile device; authenticate the mobile device using the first unique identifier after detecting the pairing request, wherein the first unique identifier is retrieved by the mobile device from the machine-readable code featured on the packaging; and pair with the mobile device after authenticating the mobile device; and wherein the second ambulatory infusion pump comprises a second memory that stores a second unique identifier associated with the second ambulatory infusion pump, and the second ambulatory infusion pump is configured to: authenticate the mobile device using the second unique identifier; and pair with the mobile device after authenticating the mobile device.

2. The system of Claim 1, wherein: the first memory of the first ambulatory infusion pump further stores the second unique identifier and the first ambulatory infusion pump is further configured to provide the second unique identifier to the mobile device after authenticating the mobile device; or the machine-readable code further encodes the second unique identifier and the second unique identifier is retrieved by the mobile device from the machine-readable code featured on the packaging.

3. The system of either Claim 1 or 2, wherein: the mobile device is configured to automatically initiate pairing with the second ambulatory infusion pump after pairing with the first ambulatory infusion pump.

4. The system of any one of Claims 1 through 3, wherein: the first ambulatory infusion pump further comprises an accelerometer; and detecting the pairing request comprises detecting a predetermined motion pattern via the accelerometer.

5. The system of any one of Claims 1 through 4, wherein: the first ambulatory infusion pump further comprises a wireless charging system; and detecting the pairing request comprises detecting a predetermined interaction with a wireless charger via the wireless charging system.

6. The system of any one of Claims 1 through 5, wherein: the first ambulatory infusion pump further comprises a NFC component; the mobile device comprises another NFC component; and detecting the pairing request comprises detecting a signal from the other NFC component of the mobile device via the NFC component of the first ambulatory infusion pump.

7. The system of any one of Claims 1 through 6, further comprising: a third ambulatory infusion pump for replacing either the first or second ambulatory infusion pump; and another machine-readable code that encodes a third unique identifier associated with the third ambulatory infusion pump; wherein the third ambulatory infusion pump comprises a third memory that stores the third unique identifier, and the third ambulatory infusion pump is configured to: detect another pairing request for pairing with the mobile device; authenticate the mobile device with the third unique identifier after detecting the pairing request; and pair with the mobile device after authenticating the mobile device.

8. The system of Claim 7, wherein: the first ambulatory infusion pump is configured to operate according to first settings and the second ambulatory infusion pump is configured to operate according to second settings; and the third ambulatory infusion pump is configured to receive initialization settings after pairing with the mobile device, wherein the initialization settings comprise (i) the first settings if the third ambulatory infusion pump is replacing the first ambulatory infusion pump or (ii) the second settings if the third ambulatory infusion pump is replacing the second ambulatory infusion pump.

9. The system of any one of Claims 1 through 8, wherein: the first ambulatory infusion pump is further configured to: operate in a low-power mode prior to detecting the pairing request; operate in a standard-power mode after detecting the pairing request; and send a wake-up signal to the second ambulatory infusion pump after detecting the pairing request; and the second ambulatory infusion pump is further configured to: operate in the low-power mode prior to receiving the wake-up signal from the first ambulatory infusion pump; and operate in the standard-power mode after receiving the wake-up signal.

10. The system of any one of Claims 1 through 9, wherein: the machine-readable code further encodes a link to a website for installation of an application for managing the first and second ambulatory infusion pumps; and the first ambulatory infusion pump is further configured to confirm installation of the application on the mobile device prior to pairing with the mobile device.

11. An ambulatory infusion pump comprising: a first memory that stores a first unique identifier associated with the ambulatory infusion pump and a second unique identifier associated with a second ambulatory infusion pump; and a processor configured to:detect a pairing request for pairing the ambulatory infusion pump with a mobile device; authenticate the mobile device using the first unique identifier after detecting the pairing request; and after authenticating the mobile device using the first unique identifier, (i) pair the ambulatory infusion pump with the mobile device and (ii) provide the second unique identifier to the mobile device; wherein the second ambulatory infusion pump comprises a second memory that stores the second unique identifier, and the second ambulatory infusion pump is configured to (i) authenticate the mobile device using the second unique identifier and (ii) pair with the mobile device after authenticating the mobile device using the second unique identifier.

12. The ambulatory infusion pump of Claim 11, further comprising: an accelerometer, wherein detecting the pairing request comprises detecting a predetermined motion pattern via the accelerometer.

13. The ambulatory infusion pump of either Claims 11 or 12, further comprising: a wireless charging system, wherein detecting the pairing request comprises detecting a predetermined interaction with a wireless charger via the wireless charging system.

14. The ambulatory infusion pump of any one of Claims 11 through 13, further comprising: an NFC component, wherein the mobile device comprises another NFC component, and detecting the pairing request comprises detecting a signal from the other NFC component of the mobile device via the NFC component of the ambulatory infusion pump.

15. The ambulatory infusion pump of any one of Claims 11 through 14, wherein: the processor is further configured to: operate in a low-power mode prior to detecting the pairing request; operate in a standard-power mode after detecting the pairing request; and send a wake-up signal to the second ambulatory infusion pump after detecting the pairing request;wherein the second ambulatory infusion pump is further configured to operate in the low- power mode prior to receiving the wake-up signal from the ambulatory infusion pump and operate in the standard-power mode after receiving the wake-up signal.

16. A computer-implemented method for pairing multiple ambulatory infusion pumps with a mobile device, the method comprising: detecting a pairing request for pairing a first ambulatory infusion pump with a mobile device, wherein the first ambulatory infusion pump comprises a first memory that stores a first unique identifier associated with the first ambulatory infusion pump and a second unique identifier associated with a second ambulatory infusion pump; authenticating the mobile device using the first unique identifier after detecting the pairing request; and after authenticating the mobile device using the first unique identifier: pairing the first ambulatory infusion pump with the mobile device; and providing the second unique identifier from the first ambulatory infusion pump to the mobile device; wherein the second ambulatory infusion pump comprises a second memory that stores the second unique identifier, and the second ambulatory infusion pump is configured to (i) authenticate the mobile device using the second unique identifier and (ii) pair with the mobile device after authenticating the mobile device using the second unique identifier.

17. The computer-implemented method of Claim 16, wherein: the first ambulatory infusion pump comprises an accelerometer; and detecting the pairing request comprises the first ambulatory infusion pump detecting a predetermined motion pattern via the accelerometer.

18. The computer-implemented method of either Claims 16 or 17, wherein: the first ambulatory infusion pump further comprises a wireless charging system; and detecting the pairing request comprises the first ambulatory infusion pump detecting a predetermined interaction with a wireless charger via the wireless charging system.

19. The computer-implemented method of any one of Claims 16 through 18, wherein: the first ambulatory infusion pump further comprises an NFC component; the mobile device comprises another NFC component; and detecting the pairing request comprises detecting a signal from the other NFC component of the mobile device via the NFC component of the first ambulatory infusion pump.

20. The computer-implemented method of any one of Claims 16 through 19, further comprising: operating the first ambulatory infusion pump in a low-power mode prior to detecting the pairing request; operating the first ambulatory infusion pump in a standard-power mode after detecting the pairing request; and sending a wake-up signal from the first ambulatory infusion pump to the second ambulatory infusion pump after detecting the pairing request; wherein the second ambulatory infusion pump is further configured to operate in the low- power mode prior to receiving the wake-up signal from the first ambulatory infusion pump and operate in the standard-power mode after receiving the wake-up signal.

21. A method for manufacturing multiple ambulatory infusion pumps, the method comprising: providing a first ambulatory infusion pump comprising a first memory; storing a first unique identifier in the first memory, wherein the first unique identifier is associated with the first ambulatory infusion pump; configuring the first ambulatory infusion pump to: detect a pairing request for pairing with a mobile device; authenticate the mobile device using the first unique identifier after detecting the pairing request, wherein the first unique identifier is retrieved by the mobile device from a machine-readable code; and pair with the mobile device after authenticating the mobile device; providing a second ambulatory infusion pump comprising a second memory; storing a second unique identifier in the second memory; configuring the second ambulatory infusion pump to:authenticate the mobile device using the second unique identifier; and pair with the mobile device after authenticating the mobile device providing packaging for the first and second ambulatory infusion pumps, wherein the packaging features the machine-readable code that encodes at least the first unique identifier; and inserting the first and second ambulatory infusion pumps into the packaging.

22. The method for manufacturing of Claim 21, wherein: the method further comprises (i) storing the second unique identifier in the first memory and (ii) configuring the first ambulatory infusion pump to provide the second unique identifier to the mobile device after authenticating the mobile device; or the machine-readable code further encodes the second unique identifier and the second unique identifier is retrieved by the mobile device from the machine-readable code featured on the packaging.

23. The method of either Claim 21 or 22, wherein: the mobile device is configured to automatically initiate pairing with the second ambulatory infusion pump after pairing with the first ambulatory infusion pump.

24. The method for manufacturing of any one of Claims 21 through 23, wherein: the first ambulatory infusion pump further comprises an accelerometer; and detecting the pairing request comprises detecting a predetermined motion pattern via the accelerometer.

25. The method for manufacturing of any one of Claims 21 through 24, wherein: the first ambulatory infusion pump further comprises a wireless charging system; and detecting the pairing request comprises detecting a predetermined interaction with a wireless charger via the wireless charging system.

26. The method for manufacturing of any one of Claims 21 through 25, wherein: the first ambulatory infusion pump further comprises an NFC component; the mobile device comprises another NFC component; anddetecting the pairing request comprises detecting a signal from the other NFC component of the mobile device via the NFC component of the first ambulatory infusion pump.

27. The method for manufacturing of any one of Claims 21 through 26, further comprising: providing a third ambulatory infusion pump for replacing either the first or second ambulatory infusion pump, wherein the third ambulatory infusion pump comprises a third memory; providing another machine-readable code that encodes a third unique identifier associated with the third ambulatory infusion pump; storing the third unique identifier in the third memory; configuring the third ambulatory infusion pump to: detect another pairing request for pairing with the mobile device; authenticate the mobile device with the third unique identifier after detecting the pairing request; and pair with the mobile device after authenticating the mobile device.

28. The method for manufacturing of Claim 27, further comprising: configuring the first ambulatory infusion pump to operate according to first settings; configuring the second ambulatory infusion pump to operate according to second settings; and configuring the third ambulatory infusion pump to receive initialization settings after pairing with the mobile device, wherein the initialization settings comprise (i) the first settings if the third ambulatory infusion pump is replacing the first ambulatory infusion pump or (ii) the second settings if the third ambulatory infusion pump is replacing the second ambulatory infusion pump.

29. The method for manufacturing of any one of Claims 21 through 28, further comprising: configuring the first ambulatory infusion pump to: operate in a low-power mode prior to detecting the pairing request; operate in a standard-power mode after detecting the pairing request; andsend a wake-up signal to the second ambulatory infusion pump after detecting the pairing request; and configuring the second ambulatory infusion pump to: operate in the low-power mode prior to receiving the wake-up signal from the first ambulatory infusion pump; and operate in the standard-power mode after receiving the wake-up signal; and placing the first and second ambulatory infusion pumps into the low-power mode prior to inserting the first and second ambulatory infusion pumps into the packaging.

30. The method for manufacturing of any one of Claims 21 through 29, further comprising: configuring the first ambulatory infusion pump to confirm installation of a pumpmanagement application prior to pairing with the mobile device, wherein the pump-management application is for management of the first and second ambulatory infusion pumps; wherein the machine-readable code further encodes a link to a website for installation of the pump-management application.

Images