System and method of pairing an infusion pump with a remote control device

Information

  • Patent Grant
  • 11984223
  • Patent Number
    11,984,223
  • Date Filed
    Monday, October 10, 2022
    2 years ago
  • Date Issued
    Tuesday, May 14, 2024
    6 months ago
Abstract
Embodiments of the present disclosure enable a user-wearable infusion pump that may have a limited user interface including no display to be paired with a remote control device that can include a remote consumer electronic device such as a smartphone and/or a dedicated remote controller.
Description
TECHNICAL FIELD

The present invention relates to medical pumps for delivering medicament to a patient, and more specifically, to a user-wearable pump controllable with a remote control device.


BACKGROUND

There are many applications in academic, industrial, and medical fields that benefit from devices and methods that are capable of accurately and controllably delivering fluids, such as liquids and gases, that have a beneficial effect when administered in known and controlled quantities. Such devices and methods can be particularly useful in the medical field where treatments for many patients include the administration of a known amount of a substance at predetermined intervals.


One category of devices for delivering such fluids is that of insulin injecting pumps that have been developed for the administration of insulin for those suffering from both Type 1 and Type 2 diabetes. Some insulin injecting pumps configured as portable infusion devices can provide continuous subcutaneous insulin injection and/or infusion therapy for the treatment of diabetes. Therapy may include the regular and/or continuous injection or infusion of insulin into the skin of a person suffering from diabetes and offer an alternative to multiple daily injections of insulin by an insulin syringe or an insulin pen. These pumps can be ambulatory/portable infusion pumps that are worn by the user and may use replaceable cartridges. Medicaments other than or in addition to insulin, such as glucagon, pramlintide, etc. can also be delivered. Examples of such pumps and various features that can be associated with such pumps include those disclosed in U.S. Patent Application Publication No. 2013/0053816, U.S. Pat. Nos. 8,573,027, 8,986,253, U.S. Patent Application Publication No. 2013/0324928, U.S. Patent Application Publication No. 2013/0331790, U.S. Pat. Ser. No. 8,287,495 and U.S. patent application Ser. No. 15/158,125, each of which is hereby incorporated herein by reference in its entirety.


One type of pump that has been developed is a patch pump, or micro pump. Patch pumps are small pumps, typically ambulatory, that may be carried directly on the skin under the user's clothing. In some cases, the pumps are situated directly on, or very near to, the injection site such that little or no tubing is required to deliver the insulin or other medicament to the patient. Some patch pumps include a single button on the pump to initiate delivery of medicament and do not include a built-in display or user interface. These pumps are therefore primarily remote-controlled. Having only a single button on the pump provides the advantage of being more robust for waterproofing and resistance to external contaminants. However, a disadvantage is that the functionality of a pump with a single button is limited without the use of a remote control apparatus, typically including a user interface.


With the proliferation of handheld electronic devices, such as mobile phones (e.g., smartphones), there is a desire to be able to remotely utilize such devices, as well as dedicated wireless controllers designed to work with one or more infusion pumps and/or types of infusion pumps, to optimize usage of infusion pumps. These remote controllers would enable a pump to be monitored, programmed and/or operated more privately, more conveniently and more comfortably. Accordingly, one potential use of dedicated remote devices and handheld consumer electronic devices (such as smartphones, tablets and the like) is to utilize such devices as controllers for remotely programming and/or operating infusion pumps.


To use a smartphone or dedicated remote control device to control an infusion pump, the device must be paired with the particular pump in order to enable the pump to execute commands sent by the remote device. However, with patch pumps described above that may not have a display or robust user interface, there is a limited ability to enter input into the pump to pair the pump with the remote and/or to provide an indication from the pump that the pump has been paired.


SUMMARY

Embodiments of the present disclosure enable a user-wearable infusion pump that may have a limited user interface including no display to be paired with a remote control device that can include a remote consumer electronic device such as a smartphone and/or a dedicated remote controller.


In embodiments, a user-wearable infusion pump includes one or more indicator lights, a single input button and no visual display. Such a pump can be paired for wireless control with a remote control device by following a step by step sequence of instructions displayed on the display of the remote control device. The sequence can include instructions for how to position the pump during the pairing process, such as on an inductive charging pad. The sequence can further include instructions to the user to interact with the input button on the pump in particular ways at particular stages of the pairing process. Feedback to the user as to whether or not the pairing process is being properly navigated and completed can be provided by the one or more indicator lights of the pump as well as on the display of the remote control device during the sequence of instructions.


In an embodiment, a method of pairing a user-wearable infusion pump including one or more indicator lights and no display screen with a remote control device is provided. The method includes receiving input at the remote control device to initiate a pairing procedure for pairing the remote control device with the user-wearable infusion pump and determining, with the remote control device, whether the user-wearable infusion pump is available for the pairing procedure. After determining that the user-wearable infusion pump is available for the pairing procedure, the remote control device can initiate the pairing procedure. Step by step instructions for the pairing procedure can be presented on a display screen of the remote control device and visual feedback as to an ongoing status of the pairing procedure can be provided with the one or more indicator lights of the user-wearable infusion pump. Successful pairing of the remote control device with the user-wearable infusion pump can be confirmed with both the display screen of the remote control device and the one or more indicator lights of the user-wearable infusion pump.


In an embodiment, a system for pairing an infusion pump with a remote control device can include a user-wearable infusion pump including one or more indicator lights and no display screen and a remote control device including a display screen. The remote control device can include a processor configured to receive input at the remote control device to initiate a pairing procedure for pairing the remote control device with the user-wearable infusion pump and determine whether the user-wearable infusion pump is available for the pairing procedure. The processor can initiate the pairing procedure with the remote control device after determining that the user-wearable infusion pump is available for the pairing procedure. Step by step instructions for the pairing procedure can be presented on the display screen of the remote control device and the user-wearable infusion pump can provide visual feedback as to an ongoing status of the pairing procedure with the one or more indicator lights. Successful pairing of the remote control device with the user-wearable infusion pump can be indicated with both the display screen of the remote control device and the one or more indicator lights of the user-wearable infusion pump.


The above summary is not intended to describe each illustrated embodiment or every implementation of the subject matter hereof. The figures and the detailed description that follow more particularly exemplify various embodiments.





BRIEF DESCRIPTION OF THE DRAWINGS

Subject matter hereof may be more completely understood in consideration of the following detailed description of various embodiments in connection with the accompanying figures, in which:



FIGS. 1A-1C depicts an embodiment of a pump system according to the disclosure.



FIGS. 2A-2C depict an embodiment of a pump system according to the disclosure.



FIG. 3 depicts an embodiment of a pump system according to the disclosure.



FIGS. 4A-4B depict remote control devices for a pump system according to embodiments of the disclosure.



FIGS. 5A-5D depict a procedure for inductively charging a battery of a pump system according to an embodiment of the disclosure.



FIG. 6 schematically depicts a pairing sequence for an infusion pump and a remote control device according to an embodiment of the disclosure.



FIGS. 7A-7I depict exemplary screen shots on a remote control device for the pairing sequences of FIGS. 6, 8 and/or 10.



FIG. 8 schematically depicts a pairing sequence for an infusion pump and a remote control device according to an embodiment of the disclosure.



FIG. 9 depicts an exemplary screen shot on a remote control device for the pairing sequences of FIGS. 6, 8 and/or 10.



FIG. 10 schematically depicts a pairing sequence for an infusion pump and a remote control device according to an embodiment of the disclosure.



FIGS. 11A-11B depict exemplary screen shots on a remote control device for the pairing sequences of FIGS. 6, 8 and/or 10.





While various embodiments are amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the claimed inventions to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter as defined by the claims.


DETAILED DESCRIPTION OF THE DRAWINGS

Referring to FIGS. 1A-1C, a pump system 100 including a pump 102 is depicted in accordance with an embodiment of the disclosure. Drive unit 118 of pump 102 includes a drive mechanism 122 that mates with a recess in medicament cartridge 116 of pump 102 to attach the medicament cartridge 116 to the drive unit 118. Further details regarding example embodiments of such delivery mechanisms can be found in U.S. Patent Publication No. 2017/0049957, which is hereby incorporated by reference in its entirety.


As depicted in the embodiment of FIGS. 2A-2B, pump system 100 can include a pump 102 and an infusion set 145. FIG. 2A depicts this infusion set 145 as not connected to pump while FIG. 2B depicts infusion set 145 connected to pump 102 via connectors 154 and 152. Infusion set 145 can include tubing 144 extending between a connector 154 and a site connector 146. Connector 154 can be configured to couple to pump 102 at connector 152. Site connector 146 can be configured to be attached to an infusion site on a user, while pump 102 can be carried in a separate location, such as the user's pocket or another location on the user's body. Various lengths of tubing 144 can be used in this embodiment to accommodate the user's preference. Further details regarding such pumps can be found in U.S. Pat. Nos. 9.993,595; 10,279,106; and 10,279,107, each of which is hereby incorporated herein by reference in its entirety.


In one embodiment, pump 102 includes a processor that controls operations of the pump and, in some embodiments, may communicate in either one-way or two-way modes to, e.g., receive operational commands and/or other signals, including data, from a separate device and/or, e.g., to send signals, including data, to a separate device. Pump 102 can include one or more buttons configured to cause the processor to initiate one or more functions. In the depicted embodiment, pump 102 includes only a single button 172, although more than one button may be present on pump 102. Button 172 can be configured to, for example, initiate delivery of medicament. Any single button such as button 172 can be utilized to execute a plurality of functions or operations. For example, a single press of button may initiate one function, holding the button down for a predetermined period of time may initiate another function, etc. Because the depicted pump 102 optionally does not itself include a display or user interface, information and feedback regarding medicament delivery or dosing initiated with button 172 can be communicated to and displayed on a remote control device or other device having a display and/or other type of user interface. Further details regarding use of button 172 can be found in U.S. Patent Publication No. 2018/0193555, which is hereby incorporated by reference in its entirety.


In one embodiment, pump 102 includes a light source, such as a light emitting diode (LED) 174. Light source 174 can be configured to provide user feedback regarding user input and/or the performance of a desired function. For example, in one embodiment, light source 174 can illuminate or blink one or more times to indicate that the one or more buttons 172 have been activated and/or that a desired function has been initiated. In one embodiment, pump 102 can additionally and/or alternatively vibrate and/or provide audible notifications to indicate that the one or more buttons 172 have been activated and/or that a desired function has been initiated or, e.g., to provide user feedback regarding user input and/or the performance of the desired function. Illumination of light source 174 and/or vibrations and/or audible notifications may be executed in any number of patterns, frequencies, durations, sequences, combinations, colors, brightness levels, etc. to indicate particular information, such as particular input received and/or particular functions or operations enabled and/or initiated, to the pump user or caregiver. FIG. 2C depicts another embodiment of a pump 102 that includes two indicator lights 174.


Referring to FIGS. 3-4B, one or more remote control devices 170, 171 can be used to communicate with the processor of pump 102 to control delivery of medicament and transfer data with pump 102 via a wired or a wireless electromagnetic signal, such as via, e.g., a near field communication (NFC) radio frequency (RF) modality or other RF modalities such as Bluetooth®, Bluetooth® low energy, mobile or Wi-Fi communication protocols, for example, according to embodiments of the present disclosure. Such a remote control can include, for example, a mobile communication device 170, such as a smart phone (as depicted in FIG. 3) executing a software application for control of the pump, a dedicated remote controller 171 (as depicted in FIGS. 4A-4B), a wearable electronic watch or electronic health or fitness monitor or personal digital assistant (PDA), etc., or a tablet, laptop or personal computer. Such communications between (and among) the one or more remote control devices 170, 171 and pump 102 may be one-way or two-way for, e.g., effective transfer of data among the devices and the pump, control of pump operations, updating software on the devices and/or pump, and allowing pump-related data to be viewed on the devices and/or pump.


Embodiments of the present invention include components capable of and methods using wired and wireless transmission and receipt of signals for exchange of information and commands between and among any of the components as described herein, including, e.g., between a pump and a smartphone; among a pump, a CGM and a smartphone; between a dedicated remote controller and a pump; among a dedicated remote controller, a CGM and a pump; among a dedicated remote controller, a BGM and a pump, and other combinations as would be contemplated by those of skill in the art.


Referring to FIGS. 5A-5D, pumps according to embodiments of the present disclosure can include one or more rechargeable batteries in and/or associated with the pump drive unit 118. In some embodiments, a rechargeable battery can be wirelessly charged, for example through inductive charging by an inductive charging pad 180. As depicted in FIG. 5B, in some embodiments, the charging pad 180 can include a cover 182 having a cutout sized to receive pump 102 in order to properly position and retain pump 102 on the charging pad 180 during recharging. In some embodiments, as shown in FIGS. 5A, 5B and 5D, the charging pad 180 may receive power by being connected to a wall outlet. In other embodiments, the charging pad 180 may additionally or alternatively include a wired and/or wireless power connection to, for example, a computer (e.g., via USB or IEEE 1394), a 12 volt automobile outlet, a battery pack (e.g., via USB or IEEE 1394), optical means, and/or a solar panel, among others.


For a pump 102 to be able to be controlled by a remote control device such as a smartphone 170 operating a software application for controlling the pump or dedicated remote controller 171 via wireless communication such as, for example, Bluetooth, the pump must be paired with the control device to establish the mutual connection between the devices. However, due to the limited communication capabilities of some user-wearable infusion pumps 102 such as those depicted in FIGS. 1A-1C and 2A-2C that do not include a display screen, it may be difficult to cause the pump to participate in the pairing process and to follow the status of the pump during pairing. Embodiments of the present invention therefore employ additional elements of the system to aid in the pairing process.



FIG. 6 schematically depicts a pairing sequence 200 for pairing remote control device 170, 171 with an infusion pump 102 according to an embodiment. The display screens 202-216 depicted in FIG. 6 can be displayed on the remote control device 170, 171 whereas the depicted LED annunciation patterns 220-232 depict the indicator lights 174 of a pump 102 such as that depicted in FIG. 2C during the pairing sequence. Display screens 202-216 are further depicted clearly in FIGS. 7A-7I. In some embodiments, a quick bolus, i.e., a bolus delivered using only the button on the pump, is disabled throughout the pairing process due to the need to use the button to initiate the pairing sequence.


A user first navigates to a Bluetooth Settings screen 202 on the remote device 170, 171 and, if not already done so, the device's Bluetooth (or other wireless modality) must be turned on.


The pairing process is then initiated by selection of a Pair Pump menu item displayed on the Bluetooth settings screen 202 when the device is not paired to a pump. The remote device 170, 171 then scans for the pump 102 as indicated by a Scanning for Pump screen 204. As the remote device scans for the pump 102, the pump indicator lights 174 are off as indicated by lights 220. If a pump 102 is discovered by the remote device 170, 171, a Pump Discovered screen 206 will be displayed. Once a pump has been discovered, the pump indicator lights 174 will transition from an off state 220 to a discovered state 222. In one embodiment, both indicator lights 172 will blink off and on in a particular color, such as, for example, orange to indicate a pump alert that the pump has been discovered. If a pump is not discovered by the remote device 170, 171, the remote can display a Pump Timeout screen 210 informing the user that the pump and controller could not be connected.


In various embodiments, the pairing sequence can utilize the inductive charging pad 180 (or other charging device) to aid in the pairing process. After the remote device 170, 171 has indicated to the user that a pump 102 is discovered, the remote device 102 can display an initiate pairing screen 208 instructing the user to place the pump 102 on the charging pad 180 and press the pump's input button 172 to initiate the pairing sequence. In one embodiment, the user may be instructed to press the input button 172 twice in succession to initiate the sequence. When the pump 102 is first placed on the charging pad 180, the indicator lights 174 can indicate a charging state 224. After the user has initiated the pairing sequence, the indicator lights 174 can indicate a pairing state 226 such as, for example, continually blinking in a given color (e.g., green). The initiate pairing screen 208 can further instruct the user to press a Next input item once the indicator lights 174 are flashing to indicate that pairing has been initiated. If the user does not press the Next input item within a predetermined period of time after pairing has been initiated, such as, for example, 30 seconds, or if the user presses the Next key when the indicator lights were not in the pairing state 226 (i.e., pairing had not been initiated), the remote 170, 171 display will revert to the Pump Timeout screen 210. See U.S. Patent Publication No. 2018/0193555, previously incorporated by reference herein in its entirety, for further description of how a pump can be configured such that the button 172 can perform different functions in the presence of absence of an inductive charging signal.


If a pump alarm, alert, etc. occurs during the pairing process, such as, for example, an occlusion indicated by the Occlusion Alarm screen 212, the user is instructed to close the alert and is then automatically routed back to the initial Bluetooth Settings screen 202 to reinitiate the pairing process once the cause of the alarm, alert, etc. has been addressed.


If no alarm, alert, etc. has occurred, after the user has pressed the Next input item on the initiate pairing screen 208, a ready to pair screen 214 is displayed on the remote device 170, 171. The ready to pair screen 214 informs the user that the pump is ready to be paired and instructs the user to hold the input button 172 for a given period of time, e.g., two seconds, to pair the pump 102 to the control device 170, 171. The indicator lights 174 can provide visual feedback that the user is properly holding the input button 172 to execute the pairing process. In one embodiment, a first pairing indicator 228 includes a first indicator light pulsating in a given color (e.g., green) during a first portion of the period of time (e.g., the initial second) and then a second pairing indicator 230 includes the first light being stably displayed in the color and the second light pulsating during the second portion of the period of time (e.g., the final second). If the user releases the input button prior to the period of time required for pairing, the indicator lights will revert to the blinking state 226 indicating the device is ready to pair. As noted above, if a pump alarm, alert, etc. occurs during the pairing process, the remote device displays the corresponding alarm or alert screen, such as the Occlusion Alarm screen 212, which will cause the user to be routed back to the initial Bluetooth Settings screen 202 to reinitiate the pairing process once the screen is closed. Similarly, if the user does not pair the pump as instructed on the ready to pair screen 214 within a preset period of time, such as 30 seconds, the Pump Timeout screen 210 will be displayed as discussed above.


If the user has properly paired the pump 102 with the remote device 170, 171, a Pump is Paired screen 216 is displayed confirming to the user that the devices are securely paired and connected. The pairing indicator 232 can display both indicator lights 174 in the solid color to indicate successful pairing on the pump. The Pump is Paired screen 216 instructs the user to close the screen, which returns the remote control 170, 171 display to the Bluetooth Settings screen 202 and the indicator lights 174 to the off state 220. The Bluetooth Settings screen 202 now indicates that the pump is paired and provides an ability to disconnect the pump and the remote device with an Unpair Pump input item.


As noted above, illumination of the one or more indicator lights 174, and particularly in a pump such as that in FIG. 2C having two indicator lights 174, can be executed in any number of patterns, frequencies, durations, sequences, combinations, colors, brightness levels, etc. to indicate particular information. The examples given above with respect to various colors, illumination patterns and combinations, etc. are illustrative only and it should be understood that different information can be conveyed by varying the output of indicator lights 174 in any number of ways.



FIG. 8 schematically depicts a pairing sequence 300 for pairing a remote control device 170, 171 with an infusion pump 102 according to another embodiment. Sequence 300 is substantially similar to sequence 200 described above. Display screens 302-310 and 314-316 are substantially identical to the corresponding screens in sequence 200 and the transitions between screens substantially similar. As shown in sequence 300, alternatively or in addition to the Occlusion Alarm screen 212 indicating that any pump alarm, alert, etc. during the pairing process can cause the pairing process to terminate, any controller alert, such as that indicated by the controller Low Power Alert screen 312 can also terminate the pairing process. The Low Power Alert screen 312 is shown in greater detail in FIG. 9. Indicator statuses 320-332 of indicator lights 174 are substantially similar to the corresponding indicator statuses 220-232, although, as noted above, the colors, patterns, etc. may be varied. In addition, indicator status 326 notes that, in some embodiments, the pump may also emit a unique sound along with the indicator light pattern to indicate that the pairing sequence has been initiated. Sequence 300 further notes that, in some embodiments, once the pump is in the pairing state as indicated by the pairing state 326 of the indicator lights, the pump no longer needs to be on the charging pad to complete the pairing process. Thus, in some embodiments, the charging pad is only used to initiate the pairing process and does not need to be present to actually pair the pump and the control once the pump is ready to be paired.



FIG. 10 schematically depicts a pairing sequence 400 for pairing a remote control device 170, 171 with an infusion pump 102 according to another embodiment. Sequence 400 is substantially similar to sequences 200 and 300 described above. Display screens 402-406, 410 and 416 are substantially identical to the corresponding screens in sequences 200 and 300 and screen 412 is substantially identical to the corresponding screen in sequence 300 with the transitions between screens also substantially similar. Screens 408 and 414 are similar to the corresponding screens, but, as shown in FIGS. 11A-11B, including visual X and check mark cues for closing or advancing the screen rather than text. Sequence 400 additionally expressly depicts that if the X icon on screen 408 indicating that the pump indicator lights have not started flashing or the X icon on screen 414 are selected, that the workflow returns to the initial Bluetooth Settings screen 402. Indicator statuses 420-432 of indicator lights 174 are substantially similar to the corresponding indicator statuses 220-232 and 320-332 although, as noted above, the colors, patterns, etc. may be varied. Pairing sequence 400 further notes that a HOME button that may be provided on the remote control to return the remote control display to a home screen or main menu may be disabled during the pairing process such that the pairing process may only be exited from within a screen in the workflow sequence.


Although the pump system described herein is described as a user-wearable pump system that has no display or user interface and is primarily controlled by a remote device, it should be understood that aspects of the present disclosure can be incorporated into other types of infusion pumps. For example, full-featured user-wearable infusion pumps having display and input capabilities, such as a touchscreen display on the pump housing, one example of which is disclosed in U.S. Pat. No. 8,287,495, which is hereby incorporated by reference herein, can incorporate aspects of the present disclosure.


Although the embodiments herein have been specifically described with respect to an ambulatory infusion pump, the inventions disclosed herein could be employed with any other type of programmable medical device capable of receiving and executing remote commands. Such devices include, for example, implantable pumps, defibrillators, spinal cord stimulation systems, etc. Embodiments could further include non-medical applications.


Also incorporated herein by reference in their entirety are commonly owned U.S. Pat. Nos. 6,999,854; 8,133,197; 8,287,495; 8,408,421 8,448,824; 8,573,027; 8,650,937; 8,986,523; 9,173,998; 9,180,242; 9,180,243; 9,238,100; 9,242,043; 9,335,910; 9,378,333; 9,381,271; 9,421,329; 9,486,171; 9,486,571; 9,492,608; 9,503,526; 9,555,186; 9,565,718; 9,603,995; 9,669,160; 9,715,327; 9,737,656; 9,750,871; 9,867,937; 9,867,953; 9,940,441; 9,993,595; 10,016,561; 10,201,656; 10,279,105; 10,279,106 and 10,279,107; commonly owned U.S. Patent Publication Nos. 2009/0287180; 2012/0123230; 2013/0053816; 2014/0276419; 2014/0276423; 2014/0276569; 2014/0276570; 2016/0082188; 2017/0142658; 2017/0182248; 2017/0250971; 2018/0021514; 2018/0071454 and 2018/0193555; commonly owned U.S. patent application Ser. Nos. 16/266,471; 16/380,475; and 16/423,675.


Various embodiments of systems, devices, and methods have been described herein. These embodiments are given only by way of example and are not intended to limit the scope of the claimed inventions. It should be appreciated, moreover, that the various features of the embodiments that have been described may be combined in various ways to produce numerous additional embodiments. Moreover, while various materials, dimensions, shapes, configurations and locations, etc. have been described for use with disclosed embodiments, others besides those disclosed may be utilized without exceeding the scope of the claimed inventions.


Persons of ordinary skill in the relevant arts will recognize that the subject matter hereof may comprise fewer features than illustrated in any individual embodiment described above. The embodiments described herein are not meant to be an exhaustive presentation of the ways in which the various features of the subject matter hereof may be combined. Accordingly, the embodiments are not mutually exclusive combinations of features; rather, the various embodiments can comprise a combination of different individual features selected from different individual embodiments, as understood by persons of ordinary skill in the art. Moreover, elements described with respect to one embodiment can be implemented in other embodiments even when not described in such embodiments unless otherwise noted.


Although a dependent claim may refer in the claims to a specific combination with one or more other claims, other embodiments can also include a combination of the dependent claim with the subject matter of each other dependent claim or a combination of one or more features with other dependent or independent claims. Such combinations are proposed herein unless it is stated that a specific combination is not intended.

Claims
  • 1. A method of pairing a user-wearable infusion pump with a remote control device, the user-wearable infusion pump having no display screen, comprising; presenting instructions for a pairing procedure for pairing the remote control device for control of the user-wearable infusion pump on a display screen of the remote control device;providing feedback during the pairing procedure as to a status of the pairing procedure with the user-wearable infusion pump; andconfirming successful pairing of the remote control device with the user-wearable infusion pump with both the display screen of the remote control device and the user-wearable infusion pump.
  • 2. The method of claim 1, wherein the user-wearable infusion pump includes one or more indicator lights and wherein at least one of providing feedback with the user-wearable infusion pump and confirming successful pairing with the user-wearable infusion pump is provided by the one or more indicator lights.
  • 3. The method of claim 1, wherein at least one of providing feedback with the user-wearable infusion pump and confirming successful pairing with the user-wearable infusion pump is provided audibly by the user-wearable infusion pump.
  • 4. The method of claim 1, wherein at least one of providing feedback with the user-wearable infusion pump and confirming successful pairing with the user-wearable infusion pump is provided with one or more vibrations of the user-wearable infusion pump.
  • 5. The method of claim 1, wherein presenting instructions includes presenting an instruction on the display screen of the remote control device for the user-wearable infusion pump to be placed on an inductive charging device.
  • 6. The method of claim 5, wherein the pairing procedure is only initiated after it is determined that the user-wearable infusion pump has been placed on the inductive charging device.
  • 7. The method of claim 6, where the pairing procedure continues if the user-wearable infusion pump is removed from the inductive charging device after the pairing procedure is initiated.
  • 8. The method of claim 1, wherein the pairing procedure is not initiated until a pairing initiation input is detected from the user-wearable infusion pump.
  • 9. The method of claim 8, wherein the pairing initiation input is input at the user-wearable infusion pump with an input button disposed on the pump.
  • 10. The method of claim 1, wherein presenting instructions includes presenting one or more instructions on the display screen of the remote control device for the user to interact with an input button of the user-wearable infusion pump.
  • 11. The method of claim 1, further comprising detecting a pump alarm or alert prior to confirming successful pairing and terminating the pairing procedure in response to detecting the pump alarm or alert.
  • 12. The method of claim 1, wherein the step of providing feedback as to a status of the pairing procedure includes indicating different statuses with different types of feedback.
  • 13. A method of pairing a user-wearable infusion pump with a remote control device, comprising: presenting an instruction on the display screen of the remote control device for the user-wearable infusion pump to be placed on an inductive charging device;determining whether the user-wearable infusion pump has been placed on the inductive charging device; andinitiating a pairing procedure for pairing the user-wearable infusion pump with the remote control device if the user-wearable infusion pump has been placed on the inductive charging device.
  • 14. The method of claim 13, where the pairing procedure continues if the user-wearable infusion pump is removed from the inductive charging device after the pairing procedure is initiated.
  • 15. The method of claim 13, where the pairing procedure is terminated if the user-wearable infusion pump is removed from the inductive charging device after the pairing procedure is initiated.
  • 16. The method of claim 13, wherein the pairing procedure is not initiated until a pairing initiation input is detected from the user-wearable infusion pump.
  • 17. The method of claim 16, wherein the pairing initiation input is input at the user-wearable infusion pump with an input button disposed on the pump.
  • 18. The method of claim 13, further comprising detecting a pump alarm or alert prior to confirming successful pairing and terminating the pairing procedure in response to detecting the pump alarm or alert.
RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/145,809, filed Jan. 11, 2021, which in turn is a continuation of U.S. patent application Ser. No. 16/507,146, filed Jul. 10, 2019, now U.S. Pat. No. 10,888,655, issued Jan. 12, 2021, which claims the benefit of U.S. Provisional Application No. 62/807,496, filed Feb. 19, 2019, each of which is hereby incorporated herein in its entirety by reference.

US Referenced Citations (369)
Number Name Date Kind
RE28890 Ingram et al. Jul 1976 E
4624661 Arimond Nov 1986 A
4678460 Rosner Jul 1987 A
5000739 Kulisz et al. Mar 1991 A
5558638 Evers et al. Sep 1996 A
5578832 Trulson et al. Nov 1996 A
5582593 Hultman Dec 1996 A
5593552 Joshi et al. Jan 1997 A
5704366 Tacklind et al. Jan 1998 A
5860957 Jacobsen et al. Jan 1999 A
5954752 Mongeon et al. Sep 1999 A
6013020 Meloul et al. Jan 2000 A
6017318 Gauthier et al. Jan 2000 A
6070761 Bloom et al. Jun 2000 A
6144866 Miesel et al. Nov 2000 A
6165155 Jacobsen et al. Dec 2000 A
6185460 Thompson Feb 2001 B1
6223080 Thompson Apr 2001 B1
6238423 Bardy May 2001 B1
6398718 Yachia et al. Jun 2002 B1
6402689 Scarantino et al. Jun 2002 B1
6488652 Weijand et al. Dec 2002 B1
6514689 Han et al. Feb 2003 B2
6561978 Conn et al. May 2003 B1
6564104 Nelson et al. May 2003 B2
6594634 Hampton et al. Jul 2003 B1
6610003 Meloul et al. Aug 2003 B1
6649403 McDevitt et al. Nov 2003 B1
6656159 Flaherty Dec 2003 B2
6683690 Tobias Jan 2004 B1
6740059 Flaherty May 2004 B2
6804555 Warkentin Oct 2004 B2
6821249 Casscells, III et al. Nov 2004 B2
6827524 Starry, Jr. et al. Dec 2004 B2
6857572 Martin Feb 2005 B2
6864101 Winkler et al. Mar 2005 B1
6916159 Rush et al. Jul 2005 B2
6943034 Winkler et al. Sep 2005 B1
6960192 Flaherty et al. Nov 2005 B1
6963770 Scarantino et al. Nov 2005 B2
6970742 Mann et al. Nov 2005 B2
7010340 Scarantino et al. Mar 2006 B2
7011630 Desai et al. Mar 2006 B2
7025716 Meloul et al. Apr 2006 B1
7029455 Flaherty Apr 2006 B2
7053761 Schofield et al. May 2006 B2
7070577 Haller et al. Jul 2006 B1
7089608 Erb Aug 2006 B2
7137964 Flaherty Nov 2006 B2
7144384 Gorman et al. Dec 2006 B2
7181505 Haller et al. Feb 2007 B2
7193521 Moberg et al. Mar 2007 B2
7198603 Penner et al. Apr 2007 B2
7204823 Estes et al. Apr 2007 B2
7291107 Hellwig et al. Nov 2007 B2
7303549 Flaherty et al. Dec 2007 B2
7316899 McDevitt et al. Jan 2008 B2
7366925 Keely et al. Apr 2008 B2
7385443 Denison Jun 2008 B1
7399401 Rush Jul 2008 B2
7483743 Mann et al. Jan 2009 B2
7497827 Brister et al. Mar 2009 B2
7553281 Hellwig et al. Jun 2009 B2
7558629 Keimel et al. Jul 2009 B2
7604593 Parris et al. Oct 2009 B2
7605710 Crnkovich et al. Oct 2009 B2
7615007 Shults et al. Nov 2009 B2
7625354 Hochman Dec 2009 B2
7651489 Estes et al. Jan 2010 B2
7651868 McDevitt et al. Jan 2010 B2
7654976 Peterson et al. Feb 2010 B2
7654982 Carlisle et al. Feb 2010 B2
7691330 Winkler et al. Apr 2010 B1
7699775 Desai et al. Apr 2010 B2
7704227 Moberg et al. Apr 2010 B2
7711402 Shults et al. May 2010 B2
7713574 Brister et al. May 2010 B2
7714757 Denison et al. May 2010 B2
7722536 Goodnow May 2010 B2
7737581 Spurlin et al. Jun 2010 B2
7774145 Brauker et al. Aug 2010 B2
7775975 Brister et al. Aug 2010 B2
7788369 McAllen et al. Aug 2010 B2
7811279 John Oct 2010 B2
7826382 Sicurello et al. Nov 2010 B2
7837647 Estes et al. Nov 2010 B2
7850674 Goodnow et al. Dec 2010 B2
7928850 Hayter et al. Apr 2011 B2
7933780 De La Huerga Apr 2011 B2
7949382 Jina May 2011 B2
7973667 Crnkovich et al. Jul 2011 B2
8005547 Forsberg et al. Aug 2011 B2
8012119 Estes Sep 2011 B2
8029443 Goodnow Oct 2011 B2
8034019 Nair et al. Oct 2011 B2
8083718 Rush et al. Dec 2011 B2
8095197 Santini, Jr. et al. Jan 2012 B2
8100852 Moberg et al. Jan 2012 B2
8106534 Spurlin et al. Jan 2012 B2
8118770 Galley et al. Feb 2012 B2
8121857 Galasso et al. Feb 2012 B2
8147511 Perry et al. Apr 2012 B2
8149117 Fennell et al. Apr 2012 B2
8226558 Say et al. Jul 2012 B2
8234128 Martucci et al. Jul 2012 B2
8275438 Simpson et al. Sep 2012 B2
8277416 Gibbs et al. Oct 2012 B2
8280476 Jina Oct 2012 B2
8287454 Wolpert et al. Oct 2012 B2
8287495 Michaud et al. Oct 2012 B2
8311749 Brauker et al. Nov 2012 B2
8323188 Tran Dec 2012 B2
8357091 Say et al. Jan 2013 B2
8369919 Kamath et al. Feb 2013 B2
8372351 Ow-Wing Feb 2013 B2
8401194 Nierzwick et al. Mar 2013 B2
8402145 Holden et al. Mar 2013 B2
8414523 Blomquist et al. Apr 2013 B2
8414563 Kamen et al. Apr 2013 B2
8444595 Brukalo et al. May 2013 B2
8449523 Brukalo et al. May 2013 B2
8451230 Celentano et al. May 2013 B2
8454554 Reinke Jun 2013 B2
8454557 Qi et al. Jun 2013 B1
8456301 Fennell Jun 2013 B2
8460243 Goodnow et al. Jun 2013 B2
8461985 Fennell et al. Jun 2013 B2
8502662 Pohlman et al. Aug 2013 B2
8533475 Frikart et al. Sep 2013 B2
8573027 Rosinko et al. Nov 2013 B2
8639288 Friedman Jan 2014 B1
8726266 Kiaie et al. May 2014 B2
8932250 Montgomery et al. Jan 2015 B2
8986253 DiPerna Mar 2015 B2
9008803 Blomquist Apr 2015 B2
9049982 Brukalo et al. Jun 2015 B2
9132227 Bryant, Jr. et al. Sep 2015 B2
9155900 Meskens Oct 2015 B2
9173992 Bengtsson et al. Nov 2015 B2
9381297 Brown et al. Jul 2016 B2
9474856 Blomquist Oct 2016 B2
9486571 Rosinko Nov 2016 B2
9492608 Saint Nov 2016 B2
9565718 Swanson Feb 2017 B2
9603995 Rosinko et al. Mar 2017 B2
9675756 Kamen et al. Jun 2017 B2
9737656 Rosinko Aug 2017 B2
9750873 Brown et al. Sep 2017 B2
9940441 Walsh Apr 2018 B2
9970044 Tonks May 2018 B2
9970893 Morgan May 2018 B2
9974903 Davis et al. May 2018 B1
9980140 Spencer et al. May 2018 B1
9993595 Michaud Jun 2018 B2
10016561 Saint et al. Jul 2018 B2
10049768 Blomquist Aug 2018 B2
10201656 Rosinko Feb 2019 B2
10213547 Rosinko Feb 2019 B2
10279105 Rosinko May 2019 B2
10279106 Cook May 2019 B1
10279107 Michaud May 2019 B2
10357603 Michaud Jul 2019 B2
10357607 Blomquist et al. Jul 2019 B2
10430043 Rosinko et al. Oct 2019 B2
10463786 Saint Nov 2019 B2
10478551 Rosinko Nov 2019 B2
10492141 Kruse Nov 2019 B2
10736037 Kruse et al. Aug 2020 B2
10773015 Blomquist et al. Sep 2020 B2
10780215 Rosinko et al. Sep 2020 B2
10806851 Rosinko Oct 2020 B2
10864318 Michaud Dec 2020 B2
10888655 Farnan et al. Jan 2021 B2
10918785 Rosinko Feb 2021 B2
10926025 Betts et al. Feb 2021 B2
11305057 Michaud Apr 2022 B2
11464908 Michaud Oct 2022 B2
20010027791 Wallace et al. Oct 2001 A1
20020040208 Flaherty et al. Apr 2002 A1
20020072733 Flaherty Jun 2002 A1
20020126036 Flaherty et al. Sep 2002 A1
20030036683 Kehr et al. Feb 2003 A1
20030060765 Campbell et al. Mar 2003 A1
20030114836 Estes et al. Jun 2003 A1
20040010207 Flaherty et al. Jan 2004 A1
20040073161 Tachibana Apr 2004 A1
20040172222 Simpson et al. Sep 2004 A1
20040260233 Garibotto et al. Dec 2004 A1
20050060030 Lashinski et al. Mar 2005 A1
20050085760 Ware et al. Apr 2005 A1
20050137530 Campbell et al. Jun 2005 A1
20050171512 Flaherty Aug 2005 A1
20050228234 Yang Oct 2005 A1
20050277912 John Dec 2005 A1
20060001538 Kraft et al. Jan 2006 A1
20060137695 Hellwig et al. Jun 2006 A1
20060173444 Choy et al. Aug 2006 A1
20070150019 Youker et al. Jun 2007 A1
20070233051 Hohl et al. Oct 2007 A1
20070287985 Estes et al. Dec 2007 A1
20080004601 Jennewine et al. Jan 2008 A1
20080017194 Hassanein et al. Jan 2008 A1
20080089313 Cayo et al. Apr 2008 A1
20080097912 Dicks et al. Apr 2008 A1
20080097913 Dicks et al. Apr 2008 A1
20080097914 Dicks et al. Apr 2008 A1
20080097917 Dicks et al. Apr 2008 A1
20080125700 Moberg et al. May 2008 A1
20080125701 Moberg et al. May 2008 A1
20080195060 Roger et al. Aug 2008 A1
20080208627 Skyggebjerg Aug 2008 A1
20080215035 Yodfat et al. Sep 2008 A1
20080215120 Dicks et al. Sep 2008 A1
20080224852 Dicks et al. Sep 2008 A1
20080231226 Hoffman et al. Sep 2008 A1
20080287922 Panduro Nov 2008 A1
20080294024 Cosentino et al. Nov 2008 A1
20080312584 Montgomery et al. Dec 2008 A1
20090037020 Brown Feb 2009 A1
20090069868 Bengtsson et al. Mar 2009 A1
20090085768 Patel et al. Apr 2009 A1
20090088731 Campbell et al. Apr 2009 A1
20090108016 Brown et al. Apr 2009 A1
20090115628 Dicks et al. May 2009 A1
20090177142 Blomquist Jul 2009 A1
20090192366 Mensinger et al. Jul 2009 A1
20090192724 Brauker et al. Jul 2009 A1
20090192745 Kamath et al. Jul 2009 A1
20090209945 Lobl et al. Aug 2009 A1
20090212966 Panduro Aug 2009 A1
20090227855 Hill et al. Sep 2009 A1
20090227888 Salmi et al. Sep 2009 A1
20090240193 Mensinger et al. Sep 2009 A1
20090254037 Bryant, Jr. et al. Oct 2009 A1
20090267774 Enegren et al. Oct 2009 A1
20090267775 Enegren et al. Oct 2009 A1
20090270705 Enegren et al. Oct 2009 A1
20090281393 Smith Nov 2009 A1
20090306594 Pang Dec 2009 A1
20100022937 Bedingfield et al. Jan 2010 A1
20100023582 Pedersen et al. Jan 2010 A1
20100063765 Carlisle Mar 2010 A1
20100093319 Sherman Apr 2010 A1
20100094110 Heller et al. Apr 2010 A1
20100121169 Petisce et al. May 2010 A1
20100134305 Lu et al. Jun 2010 A1
20100152811 Flaherty Jun 2010 A1
20100160759 Celentano et al. Jun 2010 A1
20100179402 Goode, Jr. et al. Jul 2010 A1
20100192686 Kamen et al. Aug 2010 A1
20100198142 Sloan et al. Aug 2010 A1
20100198183 Lanigan et al. Aug 2010 A1
20100234709 Say et al. Sep 2010 A1
20100235439 Goodnow Sep 2010 A1
20100274218 Yodfat et al. Oct 2010 A1
20100286653 Kubel et al. Nov 2010 A1
20100292556 Golden Nov 2010 A1
20100305421 Ow-Wing Dec 2010 A1
20100324382 Cantwell et al. Dec 2010 A1
20110009824 Yodfat et al. Jan 2011 A1
20110040247 Mandro et al. Feb 2011 A1
20110040251 Blomquist Feb 2011 A1
20110044333 Sicurello et al. Feb 2011 A1
20110046469 Nelson et al. Feb 2011 A1
20110047499 Mandro et al. Feb 2011 A1
20110066555 Dicks et al. Mar 2011 A1
20110078441 Dicks et al. Mar 2011 A1
20110149759 Jollota Jun 2011 A1
20110152770 DiPerna et al. Jun 2011 A1
20110152970 Jollota et al. Jun 2011 A1
20110169610 Geissler et al. Jul 2011 A1
20110172744 Davis et al. Jul 2011 A1
20110190614 Brister et al. Aug 2011 A1
20110190694 Lanier, Jr. et al. Aug 2011 A1
20110193704 Harper et al. Aug 2011 A1
20110201911 Johnson et al. Aug 2011 A1
20110213329 Yodfat et al. Sep 2011 A1
20110213621 Dicks et al. Sep 2011 A1
20110256024 Cole et al. Oct 2011 A1
20110257895 Brauker et al. Oct 2011 A1
20120022324 Forsell Jan 2012 A1
20120029433 Michaud Feb 2012 A1
20120041415 Estes et al. Feb 2012 A1
20120091813 Spurlin Apr 2012 A1
20120095393 Reinke Apr 2012 A1
20120116197 Moberg et al. May 2012 A1
20120185267 Kamen Jul 2012 A1
20120232520 Sloan Sep 2012 A1
20120277667 Yodat Nov 2012 A1
20120302991 Blomquist et al. Nov 2012 A1
20130042865 Monsees Feb 2013 A1
20130053816 Diperna Feb 2013 A1
20130162426 Wiesner et al. Jun 2013 A1
20130283196 Farnan et al. Oct 2013 A1
20130317837 Ballantyme Nov 2013 A1
20130324928 Kruse Dec 2013 A1
20130331790 Brown Dec 2013 A1
20140054883 Lanigan et al. Feb 2014 A1
20140075169 Andrews Mar 2014 A1
20140113553 Brukalo et al. Apr 2014 A1
20140175682 Johnson Jun 2014 A1
20140187890 Mensinger et al. Jul 2014 A1
20140200426 Taub et al. Jul 2014 A1
20140276419 Rosinko et al. Sep 2014 A1
20140276423 Lecanu-Fayet Sep 2014 A1
20140323961 Blomquist et al. Oct 2014 A1
20140371816 Matos Dec 2014 A1
20150011970 Kamen et al. Jan 2015 A1
20150052511 Kiaie et al. Feb 2015 A1
20150077038 Chao et al. Mar 2015 A1
20150174320 Grant et al. Jun 2015 A1
20150187187 Del Toro Jul 2015 A1
20150314062 Blomquist et al. Nov 2015 A1
20160004390 Laska Jan 2016 A1
20160015888 Tieck et al. Jan 2016 A1
20160074573 Kohlbrecher Mar 2016 A1
20160098848 Zamanakos et al. Apr 2016 A1
20160228041 Heller et al. Aug 2016 A1
20160267242 Naker Sep 2016 A1
20160271325 Farnan et al. Sep 2016 A1
20160328991 Simpson et al. Nov 2016 A1
20160339172 Michaud Nov 2016 A1
20160367753 Kamen Dec 2016 A1
20170049957 Michaud Feb 2017 A1
20170049960 Nguyen Feb 2017 A1
20170056590 DiPerna et al. Mar 2017 A1
20170127462 Liu May 2017 A1
20170142658 Kruse May 2017 A1
20170173261 O'Connor Jun 2017 A1
20170179749 Mansour Jun 2017 A1
20170216523 Neftel Aug 2017 A1
20170266381 Bryant, Jr. Sep 2017 A1
20170290535 Rao Oct 2017 A1
20170300206 Rosinko et al. Oct 2017 A1
20170312423 Rosinko Nov 2017 A1
20180071454 Betts Mar 2018 A1
20180133398 Blomquist May 2018 A1
20180137252 Mairs et al. May 2018 A1
20180137938 Vaddiraju et al. May 2018 A1
20180193555 Michaud Jul 2018 A1
20180204636 Edwards Jul 2018 A1
20180226145 Walsh Aug 2018 A1
20180233221 Blomquist Aug 2018 A1
20180264189 Michaud et al. Sep 2018 A1
20180361060 Rosinko Dec 2018 A9
20190121506 Matikyan Apr 2019 A1
20190167901 Rosinko Jun 2019 A1
20190175823 Rosinko Jun 2019 A1
20190240398 Seitz et al. Aug 2019 A1
20190255248 Michaud Aug 2019 A1
20190321545 Rosinko Oct 2019 A1
20190321546 Michaud et al. Oct 2019 A1
20190321552 DiPerna et al. Oct 2019 A1
20190351134 Cook et al. Nov 2019 A1
20200009319 Ludolph Jan 2020 A1
20200009320 Ludolph Jan 2020 A1
20200086043 Saint Mar 2020 A1
20200101224 Lintereur Apr 2020 A1
20200206420 Michaud Jul 2020 A1
20200261644 Farnan et al. Aug 2020 A1
20200306445 Michaud et al. Oct 2020 A1
20200329433 Kruse et al. Oct 2020 A1
20200372995 Kruse et al. Nov 2020 A1
20200384191 Rosinko et al. Dec 2020 A1
20200405947 Blomquist et al. Dec 2020 A1
20210001044 Michaud et al. Jan 2021 A1
20220031456 Navia Feb 2022 A1
20230030704 Weinstein Feb 2023 A1
20230043768 Abraham Feb 2023 A1
Foreign Referenced Citations (10)
Number Date Country
2624745 Aug 2013 EP
WO-2005018507 Mar 2005 WO
WO-2007098265 Aug 2007 WO
WO-2007098287 Aug 2007 WO
WO-2009013736 Jan 2009 WO
WO-2009016636 Feb 2009 WO
WO-2016059616 Apr 2016 WO
WO-2016145094 Sep 2016 WO
WO-2017007775 Jan 2017 WO
WO-2018111928 Jun 2018 WO
Non-Patent Literature Citations (13)
Entry
Application and File history for U.S. Appl. No. 16/507,146, filed Jul. 10, 2019, Inventors Farnan et al., as available on PAIR at http://www.uspto.gov.
Application and File history for U.S. Appl. No. 15/868,461, filed Jan. 11, 2018, Inventors Michaud et al., as available on PAIR at http://www.uspto.gov.
Application and File history for U.S. Appl. No. 16/502,196, filed Jul. 3, 2019, Inventors Michaud et al., as available on PAIR at http://www.uspto.gov.
Application and File history for U.S. Appl. No. 16/830,415, filed Mar. 26, 2020, Inventors Michaud et al., as available on PAIR at http://www.uspto.gov.
International Search Report and Written Opinion for PCT Application No. PCT/US2019/041096, mailed on Nov. 15, 2019, 11 pages.
Wu J., et al., “Wireless Power and Data Transfer via a Common Inductive Link Using Frequency Division Multiplexing,” IEEE Transactions on Industrial Electronics, vol. 62 (12), Jul. 9, 2015, pp. 1-10.
Sony Corporation, MDR-ZX880BN Help Guide, 2016 SONY https://helpguide.sony.net/mdr/zx770bn/v1/en/contents/TP0000773472.html (Year: 2016).
Application and File history for U.S. Appl. No. 17/145,809, filed Jan. 11, 2021. Inventors Farnan, as available on PAIR at http://www.uspto.gov.
Extended European Search Report for Application No. dated Oct. 10, 2022, 8 pages.
International Preliminary Report on Patentability for Application No. PCT/US2018/013331, mailed on Jul. 25, 2019, 6 pages.
International Search Report and Written Opinion for Application No. PCT/US2018/013331, mailed on May 3, 2018, 12 pages.
Search Report and Written Opinion mailed Jul. 25, 2020 for PCT Application No. PCT/US2020/024857, 11 pages.
Search Report dated Jun. 29, 2020 for EP Application No. 187390329.8, 8 pages.
Related Publications (1)
Number Date Country
20230033867 A1 Feb 2023 US
Provisional Applications (1)
Number Date Country
62807496 Feb 2019 US
Continuations (2)
Number Date Country
Parent 17145809 Jan 2021 US
Child 17962652 US
Parent 16507146 Jul 2019 US
Child 17145809 US