Embodiments generally relate to medication delivery. More particularly, embodiments relate to drug delivery systems that rely on associated sensors.
Many conventional drug delivery systems include a drug delivery device and an associated sensor. The sensor can determine and store data related to a user of the drug delivery device. The drug delivery device can then be operated based on the data related to the user. Often, the sensor and the drug delivery device are controlled by a remote device. Conventional sensors generally operate at low power levels to conserve resources. As a result of low transmission power levels, many conventional sensors cannot always relay the stored data to the remote control to ensure efficient operation of the drug delivery device. Further, many conventional drug delivery systems that combine or collocate the sensor and the drug delivery device fail to account for the different durations of use of the sensor and the drug delivery device. As a result, either the sensor is prematurely replaced or the infusion site of the drug delivery device is not spaced far enough away or changed frequently enough in relation to the sensing site of the cannula.
Accordingly, there is a need for a drug delivery system that includes a drug delivery device and associated sensor that ensures data from the sensor can be provided to a remote controller device and improves management of the infusion site in view of the sensing site.
This disclosure presents various systems, components, and methods related to a drug delivery system. Each of the systems, components, and methods disclosed herein provides one or more advantages over conventional systems, components, and methods.
Various embodiments include a drug delivery system having a drug delivery device and an associated sensor. The sensor can be associated with a sensing site on the body of a user. The drug delivery device can be positioned over the sensor in any rotational position and can be associated with an infusion site on the body of the user. The close positioning of the sensor and the drug delivery device allows data from the sensor to be relayed to the drug delivery device and then on to a remote control device. Further, the drug delivery device can be replaced at the end of its duration of use, which is shorter than the duration of use of the sensor, without disturbing the sensor. One or more subsequent drug delivery devices can be used with the sensor while allowing each corresponding infusion site to be changed, thereby providing more efficient operation of the drug delivery system. Other embodiments are disclosed and described.
The sensor 104 can be any type of sensor. The sensor 104 can monitor one or more health, biological, biomedical, or medical conditions of a user. In various embodiments, the sensor can be a continuous glucose monitoring (CGM) sensor.
As shown in
The CGM sensor 104 can include a base component 110 and a housing component 112. The base 110 can include a lip component or portion that extends around and beyond the housing 112. The housing 112 can be cylindrically shaped with a circular cross-sectional profile but is not so limited. The base 110 can also be circular but is not so limited. In various embodiments, the circular base 110 can have a diameter that is larger than a diameter of the housing 112 such that the base 110 includes an edge or lip portion that extends beyond the outer diameter of the housing 112. The CGM sensor 104 can include all components for monitoring glucose levels of a user. The drug delivery device 102 and the CGM sensor 104 can each have any size, shape, or form factor. In general, the drug delivery device 102 and the CGM sensor 104 can each be made to be small and compact with low profile form factors (e.g., as shown in
In various embodiments, the drug delivery system 100 can be a wearable drug delivery system. For example, the drug delivery system 100 can be worn directly on the body or skin of a user. In various embodiments, the CGM sensor 104 can be positioned within a central opening of the drug delivery device 102 (as indicated by indicator 114). In such embodiments, the base 110 and the housing 112 of the CGM sensor 104 can fit within the central cavity of the drug delivery device 102. The drug delivery device 102 can fit over the CGM sensor 104 such that the bottom surfaces of the drug delivery device 102 and the CGM sensor 104 are aligned and/or level (e.g., coplanar). In this way, the drug delivery system 100 can be easily attached to a user and can rest comfortably on the user.
In various embodiments, the arrangement of the drug delivery device 102 and the CGM sensor 104 allows the drug delivery device 102 to be removed and replaced. When replacing the drug delivery device 102, a new drug delivery device 102 can be positioned on top of the CGM sensor 104. The CGM sensor 104 can generally have a duration of use that is longer than the duration of use of the drug delivery device 102. In various embodiments, the CGM sensor 104 can have a first duration of use that can be approximately twelve (12) days. During the duration of use of the CGM sensor 104, a sensing cannula of the CGM sensor 104 can remain fixed in place (e.g., within the body of the user).
In various embodiments, the drug delivery device 102 can have a duration of use that can be approximately three (3) days. During the duration of use of the drug delivery device 102, an infusing cannula of the drug delivery device 102 can remain fixed in place (e.g., within the body of the user). With the drug delivery system 100, the infusion site for a user can be changed each time the drug delivery device 102 is replaced. This is advantageous as an infusion site can become less effective after roughly three (3) days of use.
Accordingly, when a first drug delivery device 102 is removed and replace with a second drug delivery device 102, the infusion site can be changed. The drug delivery device 102 can be replaced several times (e.g., four (4) times) before both the last drug delivery device 102 and the CGM sensor 104 are both removed and replaced together (e.g., at a new site on the body of the user). In this way, the drug delivery system 100 enables a sensing site for glucose monitoring to be maintained for the entire duration of use of the CGM sensor—which increases the effectiveness of the monitoring or sensing site—while providing the flexibility to adjust the infusion site.
As further shown in
A cannula 212 (e.g., a sensing cannula) can extend from the bottom surface 208. The cannula 212 can be positioned along any portion of the bottom surface 208. In various embodiments, the cannula 212 can extend from a center of the bottom surface 208.
As further shown in
The cannula 206 can have a depth (e.g., an infusion depth) 310. Similarly, the cannula 212 can have a depth (e.g., a sensing depth) 312. The depths 310 and 312 can be the same depths (as shown in
In various embodiments, the drug delivery device 102 can be positioned over the CGM sensor 104 in any orientation—for example, the infusion site can be spaced the distance 308 from the sensing site at any angular orientation relative to the sensing site. This allows the infusion site provided by the cannula 206 to be rotated or adjusted around the body of the user while the sensing site remains fixed—for example, when the drug delivery device 102 is removed and replaced with a subsequent or next drug delivery device 102. When removing the drug delivery device 102, the attachment of the CGM sensor 104 can be undisturbed. The next drug delivery device 102 can then be placed over and fitted on top of the CGM sensor 104 in the same manner the original drug delivery device 102 was placed over the CGM sensor 104. Again, this allows the CGM sensor to operate using a sensing site that remains fixed over the duration of use of the CGM sensor while the infusion sites associated with one or more corresponding drug delivery devices 102 can be changed with each new drug delivery device 102.
The cloud component 606 can represent a remote computing platform. The cloud component 606 can monitor operation of the drug delivery system 100 through connectivity with the controller device 604. The cloud component 606 can store and analyze data related to operation of the drug delivery system 100 (e.g., as determined or adjusted by the controller device 604). The cloud component 606 can be connected to one or more remote computing devices to facilitate viewing or manipulation of any stored operational data. For example, a mobile device of a remote caregiver can receive operational data stored by the cloud component 606 for viewing and/or manipulation.
In various embodiments, a communications link 608 can provide connectivity between the drug delivery system 100 and the controller device 604 and a communications link 610 can provide connectivity between the controller device 604 and the cloud component 606. The communication links 608 and 610 can be bi-direction communication links and can include wired, wireless, optical, and/or infrared communication links. The communication links 608 and 610 can operate according to any known communications standard or protocol over any type of communications medium or link. In various embodiments, a computing device coupled to the cloud component 606 can control operation of the drug delivery system 100 (e.g., by a caregiver during an emergency).
In various embodiments, the CGM sensor 104 can monitor glucose levels and store data indicative of the same. This data can be provided to the drug delivery device 102 to adjust operation of the drug delivery device 102. In various embodiments, data from the CGM sensor 104 can be passed along to the controller device 604 and/or the cloud component 606 by the drug delivery device 102.
To facilitate data sharing between the CGM sensor 104 and the drug delivery device 102, the CGM sensor and the drug delivery device 102 can be connected over a wired, wireless, optical, and or infrared communication link. The communication link coupling the CGM sensor 104 to the drug delivery device 102 can operate according to any known communications standard or protocol over any type of communications medium or link.
In various embodiments, the drug delivery device 102 can communicate with the controller device 604 over Bluetooth Low Energy (BLE). In various embodiments, the CGM sensor 104 can communicate with the drug delivery device 102 over Near-field communication (NFC), a radio-frequency (RF) communication standard, or BLE. In general, the drug delivery device 102 can include more resources (e.g., power resources and/or transmission signal strength) for providing more reliable communications with the controller device 604 compared to the resources (e.g., power resources and/or transmission signal strength) of the CGM sensor 104 for communicating with the drug delivery device 102.
For conventional CGM sensors that communicate with separate (e.g., de-coupled) conventional drug delivery devices, the conventional CGM sensors often are unable to relay stored data to a conventional controller device—e.g., because the communication protocol and/or transmission levels of the conventional CGM sensors are often too low such that the conventional controller devices are often out of range of the conventional CGM sensors. As a result, many conventional CGM sensors cannot provide their monitored glucose data to a conventional controller device such that the data can be used to more efficiently operate a conventional drug delivery device. As a result, often the data collected by the conventional CGM sensor is lost or unused. Alternatively, a user of such a conventional CGM sensor must awkwardly wave her conventional controller device over the conventional CGM sensor repeatedly to ensure reception of the transmitted data. “Picking up” the stored glucose data from the conventional CGM sensor in this manner is often required during inconvenient times for the user, making the process cumbersome and undesirable.
In contrast to such conventional systems and conventional CGM sensors, the drug delivery system 100 provides improved communication capabilities by closely locating (e.g., co-locating) the CGM sensor 104 with the drug delivery device 102. In doing so, even if the CGM sensor 104 uses a traditionally low power method of communication (e.g., a low power wireless standard), the drug delivery device 102 can detect any data transmission from the CGM sensor 104 due to the close proximity of the CGM sensor 104 and the drug delivery device 102. As a result, data from the CGM sensor 104 can be relayed to the controller device 604 (and subsequently on to the cloud component 606) by the drug delivery device 102. In turn, the drug delivery device 102 can be operated more efficiently to better manage the health of the user 602.
In various embodiments, the CGM sensor 104 can be worn by a patient for twelve (12) days. Accordingly, the cannula 212 is positioned as shown for the entirety of the twelve (12) days (e.g., the cannula 212 can be located as shown for the entire duration of use of the CGM sensor 104). In various embodiments, the drug delivery device 102 can be used for three (3) days and then replaced with another drug delivery device 102. In various embodiments, the position of the cannula 206 can be changed or adjusted for each new drug delivery device 102. In particular, the position of the cannula 206 can be rotated along the circle 702.
Site 706 can represent a second site for the cannula 206 (e.g., for days 4-6). The second site 706 can represent the position of the cannula 206 when a second drug delivery device 102 replaces the first drug delivery device 102 that is associated with the first site 704. The second site 706 can also be positioned along the axis 714. The second site 706 can be positioned 180 degrees away from the first site 704 along the circle 702 relative to the fixed location of the cannula 212.
Site 708 can represent a third site for the cannula 206 (e.g., for days 7-9). The third site 708 can represent the position of the cannula 206 when a third drug delivery device 102 replaces the second drug delivery device 102 that is associated with the second site 706. The third site 708 can be positioned along a second central axis 712. The second central axis 712 can be perpendicular to the first central axis 714. The third site 708 can be positioned 90 degrees away from the second site 706 along the circle 702 relative to the fixed location of the cannula 212.
Site 710 can represent a fourth site for the cannula 206 (e.g., for days 10-12). The fourth site 710 can represent the position of the cannula 206 when a fourth drug delivery device 102 replaces the third drug delivery device 102 that is associated with the third site 708. The fourth site 710 can be positioned along the first axis 714. The fourth site 710 can be positioned 180 degrees away from the third site 708 along the circle 702 relative to the fixed location of the cannula 212.
As described herein, a sensor and drug delivery device can have different durations of use. For example, a sensor (e.g., a CGM sensor) can be used for longer periods of time (e.g., coupled to a user) than a drug delivery device (e.g., a wearable drug delivery device such as an insulin pump). In various embodiments, a CGM may have a duration of use of 12 days or longer while a wearable drug delivery device may have a duration of use of 3 days. Accordingly, a drug delivery system incorporating a CGM sensor and a wearable drug delivery device that relies on the CGM sensor for effective operation is to account for the different durations of use in accordance with the techniques disclosed herein.
Further, a sensor (e.g., a CGM sensor) can be sterilized in a first manner that may not be compatible with a wearable drug delivery device. For example, a CGM sensor may be effectively sterilized using gamma radiation. However, for a wearable drug delivery device, which may include electronics, sterilization by gamma radiation may not be possible. Instead, for the wearable drug delivery device, Ethylene Oxide (EO) sterilization may be used, which is not compatible with the CGM sensor. Accordingly, a drug delivery system incorporating a CGM sensor and a wearable drug delivery device that relies on the CGM sensor for effective operation is to account for the different sterilization methods for the two components.
Lastly, many sensors such as a CGM sensor may need to be coupled to a use for a period of time before the site properly provides proper sensor measurements. That is, a CGM sensor may need to be in place for roughly a day or so before measurements made by the CGM sensor can be considered accurate and trustworthy. In contrast, the infusion site associated with a wearable drug delivery device may only be useable for a few days (e.g., at most 3 days) before the site becomes unusable (e.g., due to the user's body resisting the infusion site after a few days). Accordingly, a drug delivery system incorporating a CGM sensor and a wearable drug delivery device that relies on the CGM sensor for effective operation is to account for these different use restrictions.
The disclosed systems, devices, methods, and techniques disclosed herein can account for and accommodate these competing characteristics of a CGM sensor and wearable drug delivery device.
An outline 806 indicates where a drug delivery device (e.g., an insulin pump) can be attached to the adhesive pad 802 as described further herein. In various embodiments, the drug delivery device can be separately attached to the adhesive pad 802 having the incorporated CGM sensor 804. In this way, the drug delivery device can be sterilized according to a separate technique more suitable to the drug delivery device and then later coupled to the CGM sensor 804. The drug delivery device can be attached to the adhesive pad by a variety of techniques including using snaps or connectors 808. Any number of snaps and/or connectors 808 can be used.
Indicator 810 shows a position of a sensing site associated with the CGM sensor 804. That is, a sensing needle (or needles) can extend from the underside of the CGM sensor 804 at the site 810. The site 810 is shown in phantom to indicate that the site is position on the underside of the CGM sensor 804 at an opening of the adhesive pad 802. In various embodiments, the adhesive pad 802 can be positioned over an entirety of the underside of the CGM sensor 804 other than at the opening to accommodate the site 810.
In various embodiments, the adhesive pad 802 and the incorporated CGM sensor 804 can be attached to a user. The adhesive pad 802 and the incorporated CGM sensor 804 can be coupled to a user for a first period of time before a drug delivery device is coupled to the adhesive pad 802 and the incorporated CGM sensor 804 (or before a coupled drug delivery device is activated). In this way, the sensing site (or sites) associated with the adhesive pad 802 and the incorporated CGM sensor 804 can operate over the first period of time to reach a steady state (e.g., allowing the sensing sites to become reliable).
In various embodiments, once the CGM sensor 804 has been coupled to the user for a desired period do time, the drug delivery device can be coupled over the CGM sensor 804 and can be coupled to the adhesive pad 802 by the connectors 808. In various embodiments, the connectors 808 can be mechanical and can be, for example, latches or other devices providing a press fit.
In various embodiments, the adhesive pad 802 can include a first infusion site or opening 812 and a second infusion site or opening 814. The drug delivery device when attached to the adhesive pad 802 can use either the first or second openings 812 and 814 for deploying an infusion needle or cannula. As the adhesive pad 802 and the CGM sensor 804 can be coupled to the user for a period of time longer than the drug delivery device, an initial drug delivery device can be removed and replaced with a second drug delivery device. The first drug delivery device can use the first opening 812 for the infusion site. The second drug delivery device can use the second opening 814 for the infusion site. In this way, the infusion site can be rotated and changed over the duration of use of the adhesive pad 802 with the incorporated CGM sensor 804.
The openings 812 and 814 can be holes or openings within the adhesive pad 802. The adhesive pad 802 is no limited to the shape depicted. In various embodiments, the adhesive pad 802 can have any shape including round or oval. In various embodiments, the adhesive pad 802 can have multiple openings to facilitate rotation of the infusion site (e.g., more than the two openings 812 and 814). In various embodiments, the drug delivery device can be rotated in any manner with respect to the sensing site opening 810.
In various embodiments, the drug delivery system 800 can be used to initially attach the adhesive pad 802 with the incorporated CGM sensor 804 to a user. The CGM sensor 804 can be configured for operation and can be operated to have one or more sensing sites. After a period of time has elapsed, during which operation of the CGM sensor 804 reaches a steady state (e.g., at a time when measurements made by the CGM sensor 04 are accurate and/or reliable), the drug delivery device can be attached to the adhesive pad 802 (and positioned over top of the CGM sensor 804). The drug delivery device can use on of the two openings 812 and 814 for the first infusion site. After the drug delivery device has been used for a few days, it can be removed/de-coupled from the adhesive pad 802 and replaced with another drug delivery device. The second drug delivery device can use one of the openings 812 and 814 not used by the first drug delivery device. This process can be repeated until the duration of use of the CGM sensor 804 has been reached with each drug delivery device using a different infusion site from the prior drug delivery device.
The drug delivery system 800 and any constituent component thereof can have any size shape, and/or form factor and is not limited to the exemplary shapes shown in
The CGM sensor configuration module 1202 can be used to configure operation of the CGM sensor 804. After configuring the CGM sensor 804, the CGM sensor configuration module 1202 can be removed and/or detached from the adhesive pad 802 and/or the CGM sensor 804 and replaced with the drug delivery device 902.
In various embodiments, the CGM sensor configuration module 1202 can include a user interface component 1204. The user interface component 1204 can comprise a button and/or a knob. In various embodiments, the user interface component 1204 can be used to activate the CGM sensor 804—for example, by the user turning a knob and/or pressing a button. In various embodiments, the user interface component 1204 can be used to set a number of sensing sites to be used (e.g., a number of sensing cannulas to deploy), set a depth of sensing (e.g., set a depth for each sensing cannula), and/or to trigger release of the cannulas. Once the one or more sensing cannulas (e.g., cannulas 906 and 908) are deployed, the CGM sensor 804 can begin operation.
After the CGM sensor configuration module 1202 has been used to configure operation of the CGM sensor 804, the CGM sensor configuration module 1202 can be removed from the adhesive pad 802. After the CGM sensor 804 has been operating for an appropriate amount of time, the drug delivery device 902 can be coupled to the adhesive pad 802 and positioned over the CGM sensor 804. The drug delivery device 902 can be coupled in a manner to enable glucose measurements or other data collected or derived by the CGM sensor 804 to be passed to the drug delivery device 902 for use in controlling operation of the drug delivery device 902 (e.g., adjusting a dose of a medicine provided to the user).
In various embodiments, the adhesive pad 802 can have any number of holes positioned on any portion of the adhesive pad 802. In various embodiments, the adhesive pad 802 can have four holes positioned a same distance from a center of a bottom surface of the adhesive pad 802. The four holes can be positioned along a circle that surrounds the center of the bottom surface of the adhesive pad 802, with the center representing a position from which the one or more sensing cannulas of the CGM sensor 804 extend.
In various embodiments, the CGM sensor 804 can be incorporated into the adhesive pad 802 to form a single combined component. In various embodiments, the CGM sensor 804 can only include mechanical components and does not contain any electrical components. In various embodiments, the drug delivery device 902 can include mechanical and/or electrical components. In various embodiments, the CGM sensor configuration module 1202 can include mechanical and/or electrical components. This can allow the drug delivery device 902 and the CGM sensor configuration module 1202 to undergo a sterilization process that is different from a sterilization process that the adhesive pad 802 and incorporated CGM sensor 804 can undergo. In various embodiments, the CGM sensor configuration module 1202 can include only mechanical components, allow the CGM sensor configuration module 1202, the adhesive pad 802, and the incorporated CGM sensor 804 to all undergo the same sterilization process and to be provided to a user connected together as one assembly. Then, once the user configures operation of the CGM sensor 104, the user can snap off the CGM sensor configuration module 1202 and replace it with the drug delivery device 902.
In various embodiments, the adhesive pad 1404 can be positioned toward a periphery or outer portion of the bottom surface of the CGM sensor 1402. The adhesive pad 1404 can be arranged in a first circle. The first electrode 1406 can be positioned toward a middle portion of the bottom surface of the CGM sensor 1402. The first electrode 1406 can be arranged in a second circle (e.g., concentric with the first circle of the adhesive pad 1404 and smaller). The second electrode 1408 can be positioned toward a central portion of the bottom surface of the CGM sensor 1402. The second electrode 1408 can be arranged in a third circle (e.g., concentric with the first circle of the adhesive pad 1404 and second circle of the first electrode 1406 and smaller).
In various embodiments, the CGM sensor 1402 can include a sensing cannula. The sensing cannula can extend from any portion of the bottom surface of the CGM sensor 1402 (e.g., from a center of the bottom surface). In various embodiments, the CGM sensor 1402 can be coupled to a user for multiple days—for example, for a period of time of 10 days or more.
The drug delivery device 1410 can include an opening 1414. The CGM sensor 1402 can be positioned into the opening 1414. When positioned in the opening 1414, the CGM sensor 1402 can be coupled to the body of the user (e.g., the adhesive pad 1404 and the first and second electrodes 1406 and 1408 can contact the body of the user). Further, the CGM sensor 1402 can be electrically coupled to the drug delivery device 1410 when positioned in the opening 1414 to allow data from the CGM sensor 1402 to be provided to the drug delivery device 1410.
The drug delivery device 1410 can include an infusion cannula. Indicator 1416 shows a position or site of the infusion cannula (in phantom to indicate the site 1416 extends from the bottom surface of the drug delivery device 1410). In various embodiments, the CGM sensor 1402 can first be coupled to the body of a user. The drug delivery device 1410 can then be positioned over the CGM sensor 1402 such that the CGM sensor 1402 is positioned within the opening 1414. The drug delivery device 1410 can be positioned in any orientation relative to the CGM sensor 1402 such that the infusion site 1416 can be at any rotational position from a center of the CGM sensor 1402.
When the first drug delivery device 1410 has been used for its duration of use, it can be detached from the user without disrupting the position of the CGM sensor 1402. A second or subsequent drug delivery device 1410 can then be positioned over the CGM sensor 1402 and attached to the user. The second drug delivery device 1410 can be rotated relative to the former position of the first drug delivery device 1410 such that the infusion sites 1412 differ (e.g., vary by at least 90 degrees relative to a center of the CGM sensor 1402). In this way, the drug delivery system 1400 enables an unlimited number of orientations of the drug delivery device 1410 relative to the CGM sensor 1402 and therefore an unlimited number of possible infusion sites 1416 that can be changed over the course of use of the CGM sensor 1402 as multiple drug delivery device 1410 are used with the same CGM sensor 1402.
In various embodiments, the CGM sensor 1402 can include electronic components. In various embodiments, the drug delivery device 1410 can include only mechanical components. In various embodiments, the CGM sensor 1402 can include a controller component to control operation of the drug delivery device 1410.
Each of the drug delivery devices described herein can be a wearable or on-body drug delivery device or pump, such as an OmniPod (Insulet Corporation, Billerica, Mass., USA) device and/or any of the drug delivery devices described in U.S. Pat. Nos. 7,303,549; 7,144,384; 7,137,964; 6,960,192; 6,740,059; 6,699,218; 9,402,950; 7,771,412; 7,029,455; 6,740,05; and 6,656,159, each of which is incorporated herein by reference in its entirety. As such, each of the drug delivery devices disclosed herein can include one or more reservoirs or chambers configured to store a liquid drug and a drug delivery mechanism or component for extracting (e.g., pumping) the liquid drug out of the reservoir for delivery to a user. Further, each of the drug delivery devices disclosed herein can include one or more infusion cannulas for provided the stored liquid drug to the user over one or more doses and/or based on data provided by any of the sensors disclosed herein. In each of the disclosed embodiments, the sensor can be coupled to the drug delivery device in any manner (e.g., over a wired or wireless link) to allow the bidirectional flow of any data (e.g., control data, user data, etc.).
The following examples pertain to further embodiments.
Example 1 is a method comprising positioning a sensor on a body of a user, attaching the sensor to the body of a user with a first adhesive component positioned on a bottom surface of the sensor, positioning a drug delivery device over the sensor, the sensor positioned within a central opening of the drug delivery device, the drug delivery device covering all portions of the sensor except the bottom surface of the sensor attached to the user, the drug delivery device including a reservoir configured to store a liquid drug and a drug delivery component configured to extract the liquid drug from the reservoir for delivery to the user, attaching the drug delivery device to the body of the user with a second adhesive component positioned on a bottom surface of the drug delivery device, extending a sensing cannula from a center of the bottom surface of the sensor into the user, and extending an infusion cannula from a periphery of the bottom surface of the drug delivery device, the first infusion cannula spaced a predetermined distance from the sensing cannula.
Example 2 is an extension of Example 1 or any other example disclosed herein, wherein positioning the drug delivery device over the sensor further comprises positioning a base of the sensor within a recess of the drug delivery device, the recess of the drug delivery device surrounding the central opening of the drug delivery device.
Example 3 is an extension of Example 2 or any other example disclosed herein, wherein positioning the base of the sensor within the recess of the drug delivery device further comprises aligning the bottom surface of the sensor with the bottom surface of the drug delivery device.
Example 4 is an extension of Example 3 or any other example disclosed herein, wherein the bottom surface of the sensor is coplanar with the bottom surface of the drug delivery device.
Example 5 is an extension of Example 4 or any other example disclosed herein, wherein the sensor is a continuous glucose monitor (CGM) sensor and the liquid drug stored in the reservoir of the drug delivery device is insulin.
Example 6 is an extension of Example 5 or any other example disclosed herein, further comprising transmitting data indicative of glucose levels associated with the user from the CGM sensor to the drug delivery device.
Example 7 is an extension of Example 6 or any other example disclosed herein, further comprising wirelessly transmitting the data indicative of the glucose levels associated with the user from the drug delivery device to a controller component configured to control operation of the CGM sensor and the drug delivery device.
Example 8 is an extension of Example 5 or any other example disclosed herein, further comprising removing the drug delivery device after a first period of time while maintaining attachment of the CGM sensor to the body of the user, positioning a second drug delivery device over the CGM sensor, the CGM sensor positioned within a central opening of the second drug delivery device.
Example 9 is an extension of Example 8 or any other example disclosed herein, further comprising extending a second infusion cannula from a periphery of the bottom surface of the second drug delivery device, the second infusion cannula spaced the predetermined distance from the sensing cannula, the second infusion cannula spaced 180 degrees from a former position of the infusion cannula relative to a fixed position of the sensing cannula.
Example 10 is an extension of Example 9 or any other example disclosed herein, further comprising removing the second drug delivery device after a second period of time while maintaining attachment of the CGM sensor to the body of the user, positioning a third drug delivery device over the CGM sensor, the CGM sensor positioned within a central opening of the third drug delivery device.
Example 11 is an extension of Example 10 or any other example disclosed herein, further comprising extending a third infusion cannula from a periphery of the bottom surface of the third drug delivery device, the third infusion cannula spaced the predetermined distance from the sensing cannula, the third infusion cannula spaced 90 degrees from a former position of the second infusion cannula relative to the fixed position of the sensing cannula.
Example 12 is an extension of Example 11 or any other example disclosed herein, further comprising removing the third drug delivery device after a third period of time while maintaining attachment of the CGM sensor to the body of the user, positioning a fourth drug delivery device over the CGM sensor, the CGM sensor positioned within a central opening of the fourth drug delivery device.
Example 13 is an extension of Example 12 or any other example disclosed herein, further comprising extending a fourth infusion cannula from a periphery of the bottom surface of the fourth drug delivery device, the fourth infusion cannula spaced the predetermined distance from the sensing cannula, the fourth infusion cannula spaced 180 degrees from a former position of the third infusion cannula relative to the fixed position of the sensing cannula.
Example 14 is an extension of Example 13 or any other example disclosed herein, further comprising removing the fourth drug delivery device and the CGM sensor after a fourth period of time.
Example 15 is a method comprising attaching a bottom surface of a continuous glucose monitor (CGM) sensor to a body of a user, placing a first drug delivery device over the CGM sensor and positioning the CGM sensor within a central opening of the first drug delivery device, the first drug delivery device covering all of the CGM sensor other than the bottom surface of the CGM sensor, aligning the bottom surface of the CGM sensor to be coplanar with a bottom surface of the first drug, attaching the bottom surface of the first drug delivery device to the body of the user, extending a sensing cannula from a center of the bottom surface of the CGM sensor at a sensing site on the body of the user, extending a first infusion cannula from a periphery of the bottom surface of the first drug delivery device at a first infusion site on the body of the user, delivering a liquid drug to the first infusion site, the liquid drug stored in a reservoir of the first drug delivery device, detaching the first drug delivery device from the body of the user after a first period of time elapses while maintaining the sensing site, placing a second drug delivery device over the CGM sensor and positioning the CGM sensor within a central opening of the second drug delivery device, and extending a second infusion cannula from a periphery of a bottom surface of the second drug delivery device at a second infusion site on the body of the user, the second infusion site rotated at least 90 degrees from the first infusion site relative to the sensing site.
Example 16 is a drug delivery system comprising a sensor having a base component and a housing component positioned on the base component, the base component extending beyond a periphery of the housing component, a bottom surface of the base component configured to attach to a body of a user and a drug delivery device having a base component and a housing component positioned on the base component, the drug delivery device having a central opening in the base component and extending into the housing component configured to cover all portions of the sensor other than the bottom surface of the base component of the sensor, the drug delivery device having a recess surrounding the central opening, the recess configured to cover the base component of the sensor, the drug delivery device configured to store a liquid drug, wherein the bottom surface of the sensor is coplanar with the bottom surface of the drug delivery device when the sensor is positioned within the central opening of the drug delivery device, wherein the sensor includes a sensing cannula configured to extend from a center of the bottom surface of the base component of the sensor, wherein the drug delivery device includes an infusion cannula configured to extend from a periphery of the bottom surface of the drug delivery device, wherein the infusion cannula is configured to extend at a first position at any rotational position relative to the sensing cannula and spaced a first distance from the sensing cannula.
Example 17 is an extension of Example 16 or any other example disclosed herein, wherein the drug delivery device is configured to be positioned over the sensor in any rotational positional relative to the sensor.
Example 18 is an extension of Example 17 or any other example disclosed herein, wherein the drug delivery device and the sensor are communicatively coupled together when the drug delivery device is positioned over the sensor.
Example 19 is an extension of Example 18 or any other example disclosed herein, wherein the sensor is a continuous glucose monitor (CGM) senor and the liquid drug is insulin.
Example 20 is an extension of Example 19 or any other example disclosed herein, wherein the drug delivery device is configured to be removed after a first duration of use and replaced with a subsequent drug delivery device that is configured to be positioned over the CGM sensor.
Example 21 is an extension of Example 20 or any other example disclosed herein, wherein an infusion cannula of the subsequent drug delivery device is configured to extend from a second position at any rotational position relative to the sensing cannula, the second position different from the first position, and spaced the first distance from the sensing cannula.
Example 22 is an extension of Example 21 or any other example disclosed herein, wherein the second position is 180 degrees rotated from the first position relative to the sensing cannula.
Example 23 is an extension of Example 22 or any other example disclosed herein, wherein the second position is at least 90 degrees rotated from the first position relative to the sensing cannula.
Example 24 a method comprising attaching an adhesive pad having an incorporated continuous glucose monitor (CGM) sensor to a body of a user, coupling a CGM sensor configuration module to the adhesive pad and over the CGM sensor, engaging a user interface component positioned on the CGM sensor configuration module to configure operation of the CGM sensor, extending one or more sensing cannulas from a center of a bottom surface of the CGM sensor, removing the CGM sensor configuration module from the adhesive pad, coupling a first drug delivery device to the adhesive pad and over the CGM sensor in a first position, the first position one of a plurality of possible orientations relative to a positioning of the adhesive pad having the incorporated CGM sensor, extending a first infusion cannula from the first drug delivery device through a first opening in the adhesive pad to reach the body of the user, the first opening associated with the first position of the first drug delivery device, and infusing a liquid drug into the body of the user from the first drug delivery device over a first duration of use time period.
Example 25 is an extension of Example 24 or any other example disclosed herein, further comprising removing the first drug delivery device from the adhesive pad having the incorporated CGM sensor while maintaining the positioning of the adhesive pad having the incorporated CGM sensor, coupling a second drug delivery device to the adhesive pad and over the CGM sensor in second position, the second position one of the plurality of possible orientations relative to the positioning of the adhesive pad having the incorporated CGM sensor, the second position different from the first position, extending a second infusion cannula from the second drug delivery device through a second opening in the adhesive pad to reach the body of the user, the second opening associated with the second position of the second drug delivery device, and infusing the liquid drug into the body of the user from the second drug delivery device over a second duration of use time period.
Example 26 is an extension of Example 25 or any other example disclosed herein, wherein the second opening is rotated 180 degrees from the first opening relative to a position of the sensing cannula.
Example 27 is an extension of Example 26 or any other example disclosed herein, wherein the first and second openings are each positioned a same distance from the sensing cannula.
Example 28 is a drug delivery system comprising an adhesive pad having a plurality of openings configured to provide access to a body of a user, a bottom surface of the adhesive pad configured to be coupled to the body of the user, a continuous glucose monitor (CGM) sensor incorporated into the adhesive pad, the CGM sensor having one or more sensing cannulas extending from a bottom surface of the adhesive pad, a CGM sensor configuration module configured to be releasably attachable to the adhesive pad and positioned over the CGM sensor, the CGM sensor configuration module having a user interface component for configuring operation of the CGM sensor when the CGM sensor configuration module is attached to the adhesive pad and over the CGM sensor, a drug delivery device configured to be releasably attachable to the adhesive pad in one of a plurality of positions relative to a fixed position of the adhesive pad, the drug delivery device having an infusion cannula configured to extend through a first one of the plurality of openings of the adhesive pad to reach the body of the user, the drug delivery device configured to be detached from the adhesive pad after a first period of time without disrupting a positioning of the one or more sensing cannulas and to be replaced by a second drug delivery device.
Certain embodiments of the present invention were described above. It is, however, expressly noted that the present invention is not limited to those embodiments, but rather the intention is that additions and modifications to what was expressly described herein are also included within the scope of the invention. Moreover, it is to be understood that the features of the various embodiments described herein were not mutually exclusive and can exist in various combinations and permutations, even if such combinations or permutations were not made express herein, without departing from the spirit and scope of the invention. In fact, variations, modifications, and other implementations of what was described herein will occur to those of ordinary skill in the art without departing from the spirit and the scope of the invention. As such, the invention is not to be defined only by the preceding illustrative description.
Number | Name | Date | Kind |
---|---|---|---|
441663 | Hofbauer | Dec 1890 | A |
955911 | Saegmuller | Apr 1910 | A |
4206401 | Meyer | Jun 1980 | A |
4307713 | Galkin et al. | Dec 1981 | A |
4398542 | Cunningham et al. | Aug 1983 | A |
4560979 | Rosskopf | Dec 1985 | A |
4587850 | Moser | May 1986 | A |
4801957 | Vandemoere | Jan 1989 | A |
4836752 | Burkett | Jun 1989 | A |
4850954 | Charvin | Jul 1989 | A |
4882600 | Van de Moere | Nov 1989 | A |
4961055 | Habib et al. | Oct 1990 | A |
4973998 | Gates | Nov 1990 | A |
5045871 | Reinholdson | Sep 1991 | A |
5239326 | Takai | Aug 1993 | A |
5452033 | Balling et al. | Sep 1995 | A |
5563584 | Rader et al. | Oct 1996 | A |
5576781 | Deleeuw | Nov 1996 | A |
5585733 | Paglione | Dec 1996 | A |
5586553 | Halili et al. | Dec 1996 | A |
5647853 | Feldmann et al. | Jul 1997 | A |
5660163 | Schulman et al. | Aug 1997 | A |
5726404 | Brody | Mar 1998 | A |
5726751 | Altendorf et al. | Mar 1998 | A |
5785681 | Indravudh | Jul 1998 | A |
5800420 | Gross et al. | Sep 1998 | A |
5830999 | Dunn | Nov 1998 | A |
5867688 | Simmon et al. | Feb 1999 | A |
5899882 | Waksman et al. | May 1999 | A |
6171264 | Bader | Jan 2001 | B1 |
6381029 | Tipirneni | Apr 2002 | B1 |
6685452 | Christiansen et al. | Feb 2004 | B2 |
6768319 | Wang | Jul 2004 | B2 |
6830558 | Flaherty et al. | Dec 2004 | B2 |
7018360 | Flaherty et al. | Mar 2006 | B2 |
7128727 | Flaherty et al. | Oct 2006 | B2 |
7144384 | Gorman et al. | Dec 2006 | B2 |
7182726 | Williams et al. | Feb 2007 | B2 |
7303073 | Raynal-Olive et al. | Dec 2007 | B2 |
8056719 | Porret et al. | Nov 2011 | B2 |
8105282 | Susi et al. | Jan 2012 | B2 |
8285487 | Bergstrom et al. | Oct 2012 | B2 |
8454557 | Qi et al. | Jun 2013 | B1 |
8461561 | Freeman et al. | Jun 2013 | B2 |
8727117 | Maasarani | May 2014 | B2 |
9005166 | Uber, III et al. | Apr 2015 | B2 |
9248229 | Devouassoux et al. | Feb 2016 | B2 |
9427710 | Jansen | Aug 2016 | B2 |
9598195 | Deutschle et al. | Mar 2017 | B2 |
9862519 | Deutschle et al. | Jan 2018 | B2 |
10086131 | Okihara | Oct 2018 | B2 |
10342926 | Nazzaro et al. | Jul 2019 | B2 |
10441717 | Schmid et al. | Oct 2019 | B2 |
10894122 | Nishimura | Jan 2021 | B2 |
20020032374 | Holker et al. | Mar 2002 | A1 |
20020161307 | Yu et al. | Oct 2002 | A1 |
20030073952 | Flaherty et al. | Apr 2003 | A1 |
20040010207 | Flaherty et al. | Jan 2004 | A1 |
20040010507 | Bellew | Jan 2004 | A1 |
20040085215 | Moberg et al. | May 2004 | A1 |
20040215492 | Choi | Oct 2004 | A1 |
20050055242 | Bello et al. | Mar 2005 | A1 |
20050238507 | Dilanni et al. | Oct 2005 | A1 |
20060086909 | Schaber | Apr 2006 | A1 |
20060092569 | Che et al. | May 2006 | A1 |
20060282290 | Flaherty et al. | Dec 2006 | A1 |
20070027370 | Brauker et al. | Feb 2007 | A1 |
20070078784 | Donovan et al. | Apr 2007 | A1 |
20070118405 | Campbell et al. | May 2007 | A1 |
20070179885 | Bird et al. | Aug 2007 | A1 |
20070191770 | Moberg et al. | Aug 2007 | A1 |
20070233051 | Hohl et al. | Oct 2007 | A1 |
20080004515 | Jennewine | Jan 2008 | A1 |
20080027371 | Higuchi et al. | Jan 2008 | A1 |
20080033272 | Gough et al. | Feb 2008 | A1 |
20080077081 | Mounce | Mar 2008 | A1 |
20080173073 | Downie et al. | Jul 2008 | A1 |
20080255438 | Saidara et al. | Oct 2008 | A1 |
20080269723 | Mastrototaro et al. | Oct 2008 | A1 |
20080281290 | Yodfat et al. | Nov 2008 | A1 |
20090062767 | Van Antwerp et al. | Mar 2009 | A1 |
20090069787 | Estes et al. | Mar 2009 | A1 |
20090112769 | Dicks et al. | Apr 2009 | A1 |
20090254041 | Krag et al. | Oct 2009 | A1 |
20100076275 | Chu et al. | Mar 2010 | A1 |
20100094251 | Estes | Apr 2010 | A1 |
20100137784 | Cefai et al. | Jun 2010 | A1 |
20100145272 | Cefai et al. | Jun 2010 | A1 |
20100185175 | Kamen et al. | Jul 2010 | A1 |
20100286997 | Srinivasan | Nov 2010 | A1 |
20110124996 | Reinke et al. | May 2011 | A1 |
20110142688 | Chappel et al. | Jun 2011 | A1 |
20110152658 | Peyser et al. | Jun 2011 | A1 |
20110213306 | Hanson et al. | Sep 2011 | A1 |
20110218495 | Remde | Sep 2011 | A1 |
20110225024 | Seyer et al. | Sep 2011 | A1 |
20110246235 | Powell et al. | Oct 2011 | A1 |
20110313680 | Doyle, III et al. | Dec 2011 | A1 |
20110316562 | Cefai et al. | Dec 2011 | A1 |
20120029941 | Malave et al. | Feb 2012 | A1 |
20120050046 | Satorius | Mar 2012 | A1 |
20120054841 | Schultz et al. | Mar 2012 | A1 |
20120153936 | Romani et al. | Jun 2012 | A1 |
20120182939 | Rajan et al. | Jul 2012 | A1 |
20120184909 | Gyrn | Jul 2012 | A1 |
20120203085 | Rebec | Aug 2012 | A1 |
20120232520 | Sloan et al. | Sep 2012 | A1 |
20120265166 | Yodrat | Oct 2012 | A1 |
20120277667 | Yodat | Nov 2012 | A1 |
20130030841 | Bergstrom et al. | Jan 2013 | A1 |
20130036100 | Nagpal et al. | Feb 2013 | A1 |
20130060194 | Rotstein | Mar 2013 | A1 |
20130080832 | Dean et al. | Mar 2013 | A1 |
20130138452 | Cork et al. | May 2013 | A1 |
20130173473 | Birtwhistle et al. | Jul 2013 | A1 |
20130245545 | Arnold et al. | Sep 2013 | A1 |
20130274576 | Amirouche | Oct 2013 | A1 |
20140114277 | Eggert et al. | Apr 2014 | A1 |
20140163664 | Goldsmith | Jun 2014 | A1 |
20140180203 | Budiman et al. | Jun 2014 | A1 |
20150038898 | Palmer et al. | Feb 2015 | A1 |
20150057913 | Benhammou | Feb 2015 | A1 |
20150290391 | Schmid et al. | Oct 2015 | A1 |
20160022905 | Nagar et al. | Jan 2016 | A1 |
20160184517 | Baek et al. | Jun 2016 | A1 |
20170173261 | O'Connor | Jun 2017 | A1 |
Number | Date | Country |
---|---|---|
2863379 | Aug 2013 | CA |
201134101 | Oct 2008 | CN |
1762263 | Mar 2007 | EP |
1839694 | Oct 2007 | EP |
1852703 | Nov 2007 | EP |
24453628 | Apr 2008 | EP |
2099384 | Sep 2009 | EP |
2353628 | Aug 2011 | EP |
3068290 | Sep 2016 | EP |
2559866 | Feb 2016 | ES |
1401588 | Jul 1975 | GB |
2176595 | Dec 1986 | GB |
2443260 | Apr 2008 | GB |
2443261 | Apr 2008 | GB |
2461086 | Dec 2009 | GB |
2495014 | Mar 2013 | GB |
2524717 | Oct 2015 | GB |
2525149 | Oct 2015 | GB |
2001190659 | Jul 2001 | JP |
2003154190 | May 2003 | JP |
2007144141 | Jun 2007 | JP |
2007307359 | Nov 2007 | JP |
2008242502 | Oct 2008 | JP |
2012210441 | Nov 2012 | JP |
9801071 | Jan 1998 | WO |
9819145 | May 1998 | WO |
9824495 | Jun 1998 | WO |
9841267 | Sep 1998 | WO |
0010628 | Mar 2000 | WO |
0013580 | Mar 2000 | WO |
0019887 | Apr 2000 | WO |
0061215 | Oct 2000 | WO |
0078210 | Dec 2000 | WO |
2005031631 | Apr 2005 | WO |
2007112034 | Oct 2007 | WO |
2008024814 | Feb 2008 | WO |
2009023634 | Feb 2009 | WO |
2009032399 | Mar 2009 | WO |
2010025433 | Mar 2010 | WO |
2010078434 | Jul 2010 | WO |
2010146579 | Dec 2010 | WO |
2011133823 | Oct 2011 | WO |
2013149186 | Oct 2013 | WO |
2014136105 | Sep 2014 | WO |
2017089289 | Jun 2017 | WO |
2017205816 | Nov 2017 | WO |
Entry |
---|
European Search Report and Written Opinion for the European Patent Application No. EP19194241, dated Oct. 22, 2019, 7 pages. |
European Search Report for the European Patent Application No. EP03743667, dated Jul. 22, 2008. |
International Search Report and Written Opinion dated Sep. 9, 2016, issued in PCT Patent Application No. PCT/US2016/037189, 14 pages. |
International Preliminary Report on Patentability dated Dec. 21, 2017, issued in PCT Patent Application No. PCT/US2016/037189. |
U.K. Intellectual Property Office, GB Application No. GB 1401587.9, “Search Report under Section 17(5)” dated Aug. 11, 2015, 3 pages. |
European Patent Office, “Notification of Transmittal of the ISR and the Written Opinion of the International Searching Authority, or the Declaration,” in PCT Application No. PCT/GB2015/050247, dated May 8, 2015, 15 pages. |
Extended Search Report mailed Nov. 24, 2017, issued in European Patent Application No. 15779465.2, 10 pages. |
PCT International Search Report and Written Opinion dated Jul. 8, 2015, received in corresponding PCT application No. PCT/US15/26875, 13 pages. |
U.K. Intellectual Property Office, GB Application No. GB 1401588.7, “Search Report under Section 17(5)” dated Aug. 17, 2015, 3 pages. |
U.K. Intellectual Property Office, GB Application No. GB 1401589.5, “Search Report under Section 17” dated Jul. 27, 2015, 3 pages. |
European Patent Office, “Notification of Transmittal of the ISR and the Written Opinion of the International Searching Authority, or the Declaration,” in PCT Application No. PCT/GB2015/050250, dated May 7, 2015, 9 pages. |
3GPP TS 23.003 V10.0.0.0 Numbering, addressing and identification. Dec. 2010. |
European Patent Office, “Notification of Transmittal of the ISR and the Written Opinion of the International Searching Authority, or the Declaration,” in PCT Application No. PCT/GB2015/050251, dated Jun. 12, 2015, 10 pa. |
International Preliminary Report on Patentability for the International Patent Application No. PCT/US2017/061095, dated May 23, 2019, 2019, 7 pages. |
International Search Report and Written Opinion for PCT/US18/52468, dated Feb. 26, 2019, 16 pages. |
International Search Report and Written Opinion for PCT/US2017/061095, dated Feb. 20, 2018, 8 pages. |
European Search Report for the European Patent Application No. EP19194241, dated Oct. 22, 2019, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20200069875 A1 | Mar 2020 | US |