Drug delivery device having a sensing system - Patents.com
The drug delivery device addresses the need for accurate dose tracking and secure communication by using a rotatable dose button, switch, and controller to count doses reliably and transmit data securely, improving user compliance and device management.
Patent Information
- Application Number
- JP2022544855
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-12-11
- Filing Date
- 2020-02-20
- Publication Date
- 2024-11-14
- Estimated Expiration
- 2040-02-20
AI Technical Summary
Existing drug delivery devices lack a simple and cost-effective mechanism to accurately detect and record the number of doses administered, particularly in reusable pens where cartridges are replaced, and do not provide secure communication with remote devices.
A drug delivery device with a housing, a rotatable dose button, a printed circuit board, a switch, and a controller that counts dose settings using multiple techniques to ensure reliability, and communicates securely with remote devices via unencrypted wireless channels.
Accurately tracks dose administration and securely transmits data to remote devices, enhancing user compliance and device management.
Smart Images

Figure 0007583819000001 
Figure 0007583819000002 
Figure 0007583819000003
Abstract
Description
[Background technology]
[0001] Patients suffering from various diseases frequently have to inject themselves with medication. To allow humans to conveniently and accurately self-administer medication, various devices, commonly known as pen-type injectors or injection pens, have been developed. Generally, these pens are loaded with a cartridge that includes a piston and contains multiple doses of liquid medication. A drive member is movable forward to advance the piston in the cartridge to dispense the contained medication from an outlet at the distal cartridge end, typically through a needle.
[0002] In a disposable or pre-filled pen, after the pen has been utilized to deplete the supply of medication in the cartridge, the user discards the entire pen and begins using a new, replacement pen. In a reusable pen, after the pen has been utilized to deplete the supply of medication in the cartridge, the pen is disassembled to allow the used cartridge to be replaced with a new cartridge, and the pen is then reassembled for subsequent use.
[0003] Such devices may have components that physically interact with each other to effect a change of state or action by the device. For example, the device may have a cap that is removed prior to delivery, a dose button that can be turned to set a dose and / or actuated to deliver a dose, an "on" button to wake the device, etc.
[0004] The inventors recognized that a switch could be used to detect the occurrence of such interactions. The inventors also recognized that some of these physical interactions may occur repeatedly. Thus, the inventors recognized a need for a simple, low-cost switch that can be repeatedly opened and closed to detect such interactions. Summary of the Invention
[0005] The present disclosure relates to a medication delivery device, including a housing with a reservoir of sufficient size to hold a medication, a dose button rotatable relative to the housing for selecting a dose size of the medication for injection, a printed circuit board, a switch mounted on the printed circuit board, and a controller in communication with the switch, the controller configured to receive a set of signals from the switch, generate a first count of the set of signals based on the set of signals using a first counting technique, generate a second count of the set of signals based on the set of signals using a second counting technique, and determine data indicative of reliability of the first count, the second count, or both, based on the first count and the second count.
[0006] In one embodiment, a computerized method is provided, the method being executed by a controller of a medication delivery device, the controller being in communication with a switch mounted on a printed circuit board, the method including receiving a set of signals from the switch, generating a first count of the set of signals based on the set of signals using a first counting technique, generating a second count of the set of signals based on the set of signals using a second counting technique, and determining data indicative of reliability of the first count, the second count, or both, based on the first count and the second count.
[0007] In one embodiment, a medication delivery device is provided, the medication delivery device including a housing with a reservoir of sufficient size to hold a medication, a dose button rotatable relative to the housing for selecting a dose size of the medication for injection, a wireless communication module, and a controller in communication with the wireless communication module, the controller configured to generate infusion event information of the medication delivery device, connect to a remote computing device using the wireless communication module for wirelessly communicating with the remote computing device over an unencrypted wireless communication channel, and transmit encrypted data to the remote computing device using the wireless communication module over the unencrypted wireless communication channel, the encrypted data including data indicative of the infusion event information.
[0008] In one embodiment, a computerized method is provided, the method being executed by a controller of a medication delivery device, the controller being in communication with a wireless communication module, the method including: generating infusion event information of the medication delivery device; connecting to a remote computing device using the wireless communication module to wirelessly communicate with the remote computing device over an unencrypted wireless communication channel; and transmitting encrypted data to the remote computing device using the wireless communication module over the unencrypted wireless communication channel, the encrypted data including data indicative of the infusion event information.
[0009] In one embodiment, a computing device is provided, the computing device including at least one processor in communication with a memory configured to store machine-readable instructions that cause the at least one processor to connect to a wireless communication module of a medication delivery device for wirelessly communicating with the medication delivery device over an unencrypted wireless communication channel, the medication delivery device comprising (a) a housing having a reservoir of a size sufficient to hold a medication, (b) a dose button rotatable relative to the housing for selecting a dose size of the medication for injection, and (c) a controller in communication with the wireless communication module, and receive encrypted data from the medication delivery device using the wireless communication channel over the unencrypted wireless communication channel, the encrypted data including injection event information generated by the medication delivery device. [Brief description of the drawings]
[0010] Further embodiments of the present disclosure, as well as its features and advantages, will become more apparent by reference to the following description in conjunction with the accompanying drawings, in which components are not necessarily drawn to scale. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the different views.
[0011] [Figure 1] FIG. 1 is a perspective view of a medication delivery device having a dose detection system according to an aspect of the present disclosure. [Diagram 2] FIG. 2 is a partially exploded perspective view of the medication delivery device of FIG. 1 showing a dose button having a support and a cover, the cover being shown separated from the support. [Diagram 3] FIG. 2 is a partially exploded perspective view of the medication delivery device of FIG. 1 showing components of the dose detection system. [Figure 4] FIG. 2 is a cross-sectional view of the drug delivery device of FIG. 1. [Diagram 5] FIG. 2 is a partial cutaway view of the proximal end of the medication delivery device of FIG. 1 showing components of the dose detection system. [Figure 6]FIG. 2 is a bottom view of a portion of the dose button of FIG. 1, showing a printed circuit board held within the dose button cover. [Figure 7] FIG. 7 is an exploded view of a portion of the dose button shown in FIG. [Figure 8] FIG. 2 is a perspective view of a flange of a dose detection system of a medication delivery device. [Figure 9] FIG. 9 is a top view of the flange of FIG. 8. [Figure 10] FIG. 13 is a perspective view of the dose button support. [Figure 11] FIG. 11 is a top view of the dose button support of FIG. [Figure 12] FIG. 1 is a perspective view of a printed circuit board and a sensor switch according to an aspect of the present disclosure. [Figure 13] 13 is a perspective view of a cantilever arm and a base of the sensor switch of FIG. 12. [Figure 14] FIG. 14 is a side view of the cantilever arm and base of FIG. 13. [Figure 15] FIG. 13 is a side view of the cantilever arm of FIG. 12 positioned between two teeth of a flange. [Figure 16] 16 shows the cantilever arm of FIG. 15 being pushed by one of the teeth of the flange during rotation of the flange. [Figure 17] The cantilevered arm is shown being further pressed by a tooth on the flange so that a portion of the cantilevered arm moves toward and contacts the conductive pad, closing the switch. [Figure 18] A cantilevered arm is shown sliding over the teeth of the flange. [Figure 19] 1 shows the cantilever arm interacting with the next adjacent tooth on the flange. [Figure 20] FIG. 13 is a perspective view of a switch design according to another embodiment. [Figure 21] FIG. 21 is a side view of the switch of FIG. 20. [Figure 22] FIG. 13 is a perspective view of a switch design according to another embodiment. [Diagram 23] FIG. 23 is a side view of the switch of FIG. 22. [Figure 24]FIG. 23 is a perspective view of the switch of FIG. 22 interacting with a rotating flange. [Diagram 25] FIG. 21 is a side view of the switch of FIG. 20 showing the center of mass of the switch. [Figure 26A] FIG. 2 is an exemplary block diagram illustrating functional aspects of a printed circuit board for processing signals from a sensor, according to some embodiments. [Figure 26B] 1 is a graph illustrating an exemplary set of signals generated by a sensor, according to some embodiments. [Figure 27] 5 is a flowchart illustrating an example computerized method for processing signals from a rotation sensor, according to some embodiments. [Figure 28] 1 is a flowchart illustrating an exemplary cryptographic scheme that uses an open communication channel to exchange cryptographic information and access cryptographic information from a cloud computing device, according to some embodiments. [Figure 29] 1 is a flowchart illustrating an exemplary encryption scheme that uses an open communication channel to exchange encrypted information and determines the encrypted information from a barcode on a medication delivery device, according to some embodiments. [Diagram 30] 1A-1D illustrate various states of a drug delivery device and associated functionality, according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] For the purposes of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same, it being understood, however, that no limitation of the scope of the invention is intended.
[0013] The present disclosure relates to sensing systems for drug delivery devices.
[0014] In one aspect, the sensing system includes a switch having an arm that is movable to open and close the switch. The switch is used to sense relative rotational movement between a dose setting assembly and an actuator of the drug delivery device to determine the amount of the dose delivered by the drug delivery device. The sensed relative rotational movement correlates with the dose delivered. By way of example, the drug delivery device is described in the form of a pen injector. However, the drug delivery device may be any device used to set and deliver a dose of a drug, such as a pen injector, an infusion pump, and a syringe. The drug may be any of the types that can be delivered by such a drug delivery device.
[0015] The present disclosure also relates to various software and / or hardware based techniques for the drug delivery device and remote computing devices in communication with the drug delivery device.
[0016] In one aspect, the medication delivery device includes a housing with a reservoir of sufficient size to hold a medication, a dose button rotatable relative to the housing for selecting a dose size of the medication for injection, a printed circuit board, a switch mounted on the printed circuit board, and a controller in communication with the switch, the controller is configured to receive a set of signals from the switch, generate a first count of the set of signals based on the set of signals using a first counting technique, generate a second count of the set of signals using a second counting technique, and determine data indicative of reliability of the first count, the second count, or both, based on the first count and the second count.
[0017] In another aspect, a medication delivery device includes a housing with a reservoir of sufficient size to hold a medication, a dose button rotatable relative to the housing for selecting a dose size of the medication for injection, a wireless communication module, and a controller in communication with the wireless communication module, the controller configured to generate medication delivery device injection event information, connect to a remote computing device to wirelessly communicate with the remote computing device over an unencrypted wireless communication channel using the wireless communication module, and transmit encrypted data to the remote computing device over the unencrypted wireless communication channel using the wireless communication module.
[0018] The devices described herein may further include a drug, for example, in the reservoir or cartridge 20. In another embodiment, a system may include one or more devices, including device 10, and a drug. The term "drug" refers to one or more therapeutic agents, including, but not limited to, insulin, insulin analogs such as insulin lispro or insulin glargine, insulin derivatives, GLP-1 receptor agonists such as dalaglutide or liraglutide, glucagon, glucagon analogs, glucagon derivatives, gastric inhibitory polypeptide (GIP), GIP analogs, GIP derivatives, oxyntomodulin analogs, oxyntomodulin derivatives, therapeutic antibodies, and any therapeutic agent capable of being delivered by the above-mentioned device. Drugs as used in the device may be formulated with one or more excipients. The device is operated by the patient, a caregiver, or a medical professional in a manner generally as described above to deliver the drug to a human.
[0019] An exemplary medication delivery device 10 is shown in FIGS. 1-4 as a pen-type injector configured to inject medication into a patient through a needle. The device 10 includes a body 11, which may include an elongated pen-shaped housing 12 including a tip portion 14 and a proximal portion 16. The distal portion 14 may be received within a pen cap 18. With reference to FIG. 4, the distal portion 14 may house a reservoir or cartridge 20 configured to hold a medicinal fluid to be dispensed through a dispensing action of an outlet 21 of the housing. The outlet 21 of the distal portion 14 may include an injection needle 24. In some embodiments, the injection needle is removable from the housing. In some embodiments, the injection needle is replaced with a new injection needle after each use.
[0020] A piston 26 may be positioned within the reservoir 20. The drug delivery device may include an injection mechanism positioned within the proximal portion 16 operable to advance the piston 26 towards the outlet of the reservoir 20 to force the contained drug through the needle end during a dose-dispensing operation. The injection mechanism may include a drive member 28, illustratively in the form of a screw, axially movable relative to the housing 12 to advance the piston 26 through the reservoir 20.
[0021] The device may include a dose setting assembly coupled to the housing 12 for setting the dose dispensed by the device 10. As best seen in Figures 3 and 4, in the illustrated embodiment, the dose setting assembly includes a dose setting screw 32 and a flange 38. The dose setting screw 32 is in the form of a threaded element operable to helically move (i.e. move axially and rotationally simultaneously) relative to the housing 12 about a longitudinal axis of rotation AA during dose setting and dose dispensing. Figures 3 and 4 show the dose setting screw 32 fully threaded into the housing 12 at its home or zero dose position. The dose setting member 32 is operable to unscrew proximally from the housing 12 until it reaches a fully extended position corresponding to the maximum dose deliverable by the device 10 in a single injection. The extension position can be any position between a position corresponding to an incremental extension position (such as a 0.5 or 1 unit dose setting) to a fully extended position corresponding to the maximum dose deliverable by the device 10 in a single injection, where the housing 12 is screwed distally until a home or zero position is reached, corresponding to the minimum dose deliverable by the device 10 in a single injection.
[0022] 3 and 4, the dose setting screw 32 includes a helically threaded outer surface that engages a corresponding threaded inner surface 13 of the housing 12 to allow the dose setting screw 32 to helically move (i.e., rotate and translate simultaneously) relative to the housing 12. The dose setting screw 32 further includes a helically threaded inner surface that engages a threaded outer surface of a sleeve 34 (FIG. 4) of the device 10. The outer surface of the dose setting screw 32 includes dose indicator markings, such as numbers that are visible through a dose window 36 to indicate the set dose to a user.
[0023] As mentioned above, in some embodiments, the dose setting assembly further includes a tubular flange 38 coupled to the open proximal end of the dose setting screw 32 and axially and rotationally locked to the dose setting screw 32 by a protrusion 40 received within an opening 41 in the dose setting screw 32. The protrusion 40 of the flange 38 can be seen in Figures 3, 8 and 9, and the opening 41 in the dose setting screw 32 can be seen in Figure 3.
[0024] As seen in Figures 3 and 4, the delivery device 10 may include an actuator assembly having a clutch 52 and a dose button 30. The clutch 52 is received within the dose setting screw 32, and the clutch 52 includes an axially extending stem 54 at its proximal end. The dose button 30 of the actuator assembly is positioned proximal to the dose setting screw 32 and the flange 38. The dose button 30 includes a support 42, also referred to herein as the "under button," and a cover 56, also referred to herein as the "over button." As discussed, the support 42 and cover 56 enclose electronic components used to store and / or communicate data related to the amount of a dose delivered by the medication delivery device.
[0025] The dose button support 42 may be attached to the stem 54 of the clutch 52, such as by an interference fit or ultrasonic welding, to axially and rotatably secure the dose button 30 and clutch 52 together.
[0026] In some embodiments, a portion of the clutch may pass through a lumen 39 in the flange 38. The flange lumen 39 is best seen in Figures 8 and 9. The lumen 39 may, in some embodiments, serve to aid in centering the clutch 52 in place.
[0027] The proximal face 60 of the dose button 30 may serve as a pressing surface against which a force may be applied manually, i.e., directly by a user, to push the actuator assembly (dose button 30 and clutch 52) distally. A biasing member 68, illustratively a spring, may be disposed between a distal face 70 of the support 42 and a proximal face 72 of the tubular flange 38 (FIGS. 8 and 9) to bias the support 42 of the actuation assembly and the flange 38 of the dose setting assembly axially away from each other. The dose button 30 is depressible by a user to initiate a dose dispensing operation. In some embodiments, the biasing member 68 may be seated against this proximal face 72 and surround a raised collar 37 of the flange 38.
[0028] The delivery device 10 is operable in a dose setting mode and a dose dispensing mode. In the dose setting mode of operation, the dose button 30 is rotated relative to the housing 12 to set a desired dose to be delivered by the device 10. In some embodiments, rotating the dose button 30 in one direction relative to the housing 12 translates the dose button 30 axially proximally relative to the housing 12, and rotating the dose button 30 in the opposite direction relative to the housing 12 translates the dose button 30 axially distally relative to the housing. In some embodiments, clockwise rotation of the dose button moves the dose button 30 distally and counterclockwise rotation of the dose button moves the dose button proximally, or vice versa.
[0029] In some embodiments, rotating the dose button 30 and axially translating the dose button 30 in a proximal direction serves to increase the set dose, and rotating the dose button 30 and axially translating the dose button 30 in a distal direction serves to decrease the set dose. The dose button 30 is adjustable in predefined rotational increments that correspond to a minimum incremental increase or decrease in the set dose during a dose setting operation. The dose button may include a detent mechanism such that each rotational increment produces an audible and / or tactile "click." For example, one increment or "click" may be equal to ½ or 1 unit of medication.
[0030] In some embodiments, the set volume may be visible to the user via dial gauge markings shown through the dose window 36. During the dose setting mode, the actuator assembly, including the dose button 30 and clutch 52, moves axially and rotationally with the dose setting assembly, including the flange 38 and dose setting screw 32.
[0031] The dose setting screw 32 and the flange 38 are rotatably fixed to one another by a threaded connection between the dose setting screw 32 and the housing 12, which allows them to rotate and move proximally during dose setting. During this dose setting operation, the dose button 30 is rotatably fixed relative to the flange 38 and the dose setting screw 32 by complementary splines 74 of the flange 38 and the clutch 52 (FIG. 4), which are biased together by a biasing member 68. During the course of dose setting, the dose setting screw 32, the flange 38, the clutch 52, and the dose button 30 move in a helical manner (i.e., simultaneous rotation and axial translation) relative to the housing 12 from a "start" position to an "end" position. This rotation and translation relative to the housing is proportional to the amount of dose setting due to the operation of the drug delivery device 10.
[0032] Once the desired dose is set, the device 10 is manipulated so that the injection needle 24 properly penetrates, for example, the user's skin. The dose dispensing mode of operation is initiated in response to an axial distal force applied to the proximal face 60 of the dose button 30. The axial force is applied directly to the dose button 30 by the user. This results in axial movement of the actuator assembly (dose button 30 and clutch 52) in the distal direction relative to the housing 12.
[0033] Axial shifting motion of the actuator assembly compresses the biasing member 68, reducing or closing the gap between the dose button 30 and the tubular flange 38. This relative axial movement separates the clutch 52 and the complementary splines 74 on the flange 38, thereby disengaging the dose button 30 from rotatable fixation to the flange 38 and the dose setting screw 32. Specifically, the dose setting screw 32 is rotatably decoupled from the dose button 30 to allow back-drive rotation of the dose setting screw 32 relative to the dose button 30 and the housing 12. Also, rotation of the dose button 30 relative to the housing 12 is held by a user pressing and engaging the dose button 30 while the dose setting screw 32 and flange 38 are free to rotate relative to the housing 12.
[0034] As the dose button 30 and clutch 52 continue to be depressed axially without rotation relative to the housing 12, the dose set screw 32 is threaded back into the housing 12 as it rotates relative to the dose button 30. Dose markings are visible through the window 36, indicating the amount still remaining to be injected. As the dose set screw 32 is threaded distally, the drive member 28 advances distally to push the piston 26 through the reservoir 20 and expel medication through the needle 24.
[0035] During a dose dispensing operation, the amount of drug released from the drug delivery device is proportional to the amount of rotational movement of the dose setting screw 32 relative to the housing 12 as the dose setting screw 32 is screwed back into the housing 12. In some embodiments, since the dose button 30 is rotatably fixed relative to the housing 12 during the dose dispensing mode, the amount of drug released from the drug delivery device can be considered to be proportional to the amount of rotational movement of the dose setting screw 32 relative to the dose button 30 as the dose setting screw 32 is screwed back into the housing 12. The injection is completed when the female threads of the dose setting screw 32 reach the distal end of the corresponding male threads of the sleeve 34 (FIG. 4). The device 10 is then again disposed in the ready or zero dose position as shown in FIGS. 2 and 4.
[0036] As discussed above, the delivered dose may be derived based on the amount of rotation of the dose setting assembly (flange 38 and dose setting screw 32) relative to the actuator assembly (clutch 52 and dose button 30) during dose delivery. This rotation may be determined by detecting incremental movement of the dose setting assembly, which is "counted" as it rotates during dose delivery.
[0037] Further details of the design and operation of the exemplary delivery device 10 can be found in U.S. Patent No. 7,291,132, entitled Medication Dispensing Apparatus with Triple Screw Threads for Mechanical Advantage, the entire disclosure of which is incorporated herein by reference. Another example of a delivery device is an automatic injection device that can be found in U.S. Patent No. 8,734,394, entitled "Automatic Injection Device With Delay Mechanism Including Dual Functioning Biasing Member," the entire disclosure of which is incorporated herein by reference, where such a device is modified with one or more of the various sensor systems described herein to determine the amount of medication delivered from the medication delivery device based on sensing relative rotation within the medication delivery device. Another example of a delivery device is a reusable pen-type device that can be found in U.S. Patent No. 7,195,616, entitled "Medication Injector Apparatus with Drive Assembly that Facilitates Reset," which is incorporated by reference in its entirety herein, where such a device is modified with one or more of the various sensor systems described herein to determine the amount of medication delivered from the medication delivery device based on sensing relative rotation within the medication delivery device.
[0038] Described herein is a dose detection system that may be operable to determine the amount of a delivered dose based on relative rotation between a dose setting member and a device body. The dose detection system utilises a dose setting member attached to the device body and rotatable relative to the device body about an axis of rotation during dose delivery. A sensed element is attached to and rotationally fixed on the dose setting member. An actuator is attached to the device body and held against rotation relative to the device body during dose delivery. The sensed element thereby rotates relative to the actuator during dose delivery in relation to the amount of the delivered dose.
[0039] In some embodiments, the dose detection system comprises a rotational sensor attached to an actuator assembly and a sensed element including surface features evenly spaced radially about an axis of rotation of the sensing element.
[0040] In some embodiments, the dose detection system may include a sensor and a sensed component attached to a component of a drug delivery device. The term "attached" encompasses any manner of fixing the location of a component to another component or member of a drug delivery device such that they are operable as described herein. For example, the sensor may be attached to the component of the drug delivery device by being positioned directly on, received within, integral with, or otherwise connected to the component. The connection may include, for example, a connection formed by frictional engagement, spline, snap or press fit, sonic welding, or adhesive.
[0041] The term "directly attached" is used to describe an attachment in which two components, or one structural application and one member, are physically secured together without the use of intermediate members other than the attachment component. The attachment component may comprise a fastener, adapter, or other part of the fastening system (such as a compression membrane) that is interposed between the two components to facilitate the attachment. "Direct attachment" is distinguished from attachments in which components / members are joined by one or more intermediate functional members.
[0042] The term "fixed" is used to indicate that the indicated motion may or may not occur. For example, if two members are required to rotate and move together, then a first member is "rotationally fixed" with a second member. In one embodiment, a member may be "fixed" relative to another member functionally, rather than structurally. For example, one member may be pressed against another member such that a frictional engagement between the two members rotationally locks them together, but the two members cannot be fixed together without the pressing of the first member.
[0043] Various sensor arrangements are contemplated herein. Generally, a sensor arrangement comprises a sensor and a sensed component. The term "sensor" refers to any component capable of detecting the relative position or movement of the sensed component. The sensor may be used with associated electrical components to operate the sensor. A "sensed component" is any component capable of detecting the position and / or movement of the sensed component relative to the sensor. In the case of a dose detection system, the sensed component rotates relative to the sensor, and the sensor is capable of detecting the rotational movement of the sensed component. The sensor may comprise one or more sensing elements, and the sensed component may comprise one or more sensed elements. The sensor detects the movement of the sensed component and provides an output representative of the movement of the sensed component.
[0044] Illustratively, the dose detection system includes an electronics assembly suitable for operation of the sensor arrangement as described herein. The medication delivery device may include a controller operably connected to the sensor to receive an output from the sensor. The controller begins to receive a generated signal from the sensor indicative of a count from a first to a last for a total number of counts used to determine a total displacement, e.g., an angular displacement. When detecting an angular movement of the dose setting assembly, the controller may be configured to receive data indicative of an angular movement of the dose setting assembly, which may be used to determine from the output an amount of a dose delivered by operation of the medication delivery device. The controller may be configured to determine from the output a dose delivered by operation of the medication delivery device. The controller may include conventional components such as a processor, a power supply, a memory, a microcontroller, etc. Alternatively, at least some components may be provided separately, such as by a computer, a smartphone, or other device. Means are then provided for operably connecting an external controller component with the sensor at the appropriate time, such as by a wired or wireless connection.
[0045] According to one embodiment, the electronics assembly includes a sensor arrangement including one or more sensors in operative communication with a processor for receiving a signal from the sensor representative of a sensed rotation. An exemplary electronics assembly 76 is shown in FIGS. 5-7 and can include a sensor 86 and a printed circuit board (PCB) 77 having a number of electronic components. The printed circuit board can be a flexible printed circuit board. The circuit board of the electronics assembly 76 can include a microcontroller unit (MCU) as a controller with at least one processing core and an internal memory. The electronics assembly can include a power source 79, e.g., a battery, illustratively a coin cell, for powering the components. The controller of the electronics assembly 76 can include control logic operative to perform the operations described herein, including detecting angular movement of the dose setting assembly during dose setting and / or dose delivery based on a detected rotation of the dose setting assembly relative to the actuator assembly and / or detecting a dose delivered by the medication delivery device 10. Some, but not all, of the components of the electronics assembly can be housed in a compartment 85 within the dose button 30. In some embodiments, the compartment 85 may be defined between the proximal surface 71 of the dose button support 42 and the distal surface 81 of the dose button cover 56. In the embodiment shown in Figure 5, the electronics assembly 76 is permanently integrated within the dose button 30 of the delivery device. In other embodiments, the electronics assembly is provided as a module that can be removably attached to the actuator assembly of the medication delivery device.
[0046] An underside view of electronics assembly 76 held within cover 56 is shown in Figure 6, and an exploded view of electronics assembly 76 is shown in Figure 7. As shown in Figures 6 and 7, electronics assembly 76 may include a printed circuit board (PCB) 77 and a sensor 86 having a contact surface 111. As shown in Figure 7, electronics assembly 76 may also include a battery 79 and a battery cage 87.
[0047] In some embodiments, at least a portion of the sensor 86 extends outside the compartment 85 of the dose button 30. As best seen in Figures 10 and 11, the support 42 of the dose button 30 may include one or more openings 45 through which the sensor 86 may extend. In some embodiments, during assembly of the drug delivery device, the contact surface 111 of the sensor 86 passes through the opening 45 of the support 42. This may allow the contact surface 111 of the sensor to interact with components that are external to the compartment 85 of the dose button 30. In some embodiments, only one of the openings 45 of the support 42 is required to accommodate the sensor, although a second opening may be provided, for example, due to symmetry of the support component, which aids in manufacturing the component and / or assembly of the component with the drug delivery device.
[0048] The controller of the electronics assembly 76 may be operable to store in a local memory (e.g., internal flash memory or on-board EEPROM) the total angular movement used to determine dose delivery and / or the detected dose delivery. The controller may be further operable to wirelessly transmit a signal representative of the total count, the total angular movement, and / or the detected dose to an external device, such as a user's mobile device or a remote server. The transmission may be via, for example, Bluetooth Low Energy (BLE) or other suitable short-range or long-range wireless communication protocol. Illustratively, the BLE control logic and the controller are integrated on the same circuit.
[0049] As discussed, according to one aspect, the dose detection system includes detecting the relative rotational movement between two assemblies of the drug delivery device. The sensor operates to detect the amount of angular movement from the start of dose injection to the end of dose injection, with the degree of rotation having a known relationship to the amount of dose delivered. For example, in some embodiments, the relationship of the pen injector is such that an angular displacement of the dose setting assembly of 18° corresponds to one dose unit, but other angular relationships are also suitable, such as 9°, 10°, 15°, 20°, 24°, or 36° for one or half unit. The sensor system is operable to determine the total angular displacement of the dose setting member during dose delivery. Thus, if the angular displacement is 90°, then 5 units of dose have been delivered.
[0050] The angular displacement is determined by counting dose increments as the injection progresses. For example, the sensing system may use a repeating pattern of sensed elements such that each repetition is indicative of a predefined degree of rotation angle. Conveniently, the pattern may be established such that each repetition corresponds to a minimum dose increment that can be set with the drug delivery device.
[0051] The dose detection system components may be permanently or removably attached to the medication delivery device. In some embodiments, at least some of the dose detection system components are provided in the form of modules that are removably attached to the medication delivery device. In other embodiments, the dose detection system components are permanently attached to the medication delivery device.
[0052] In some embodiments, the sensor may detect the relative rotation of a sensed component rotatably fixed to the dose setting screw 32, which determines the amount of dose delivered by the medication delivery device during dose delivery. In one exemplary embodiment, the rotation sensor is attached to and rotatably fixed to the actuator assembly. The actuator assembly does not rotate relative to the device housing during dose delivery.
[0053] In some embodiments, the sensed component is attached to and rotatably fixed to the dose setting screw 32 and rotates relative to the dose button 30 and device housing 12 during dose delivery. In some of the embodiments described herein, the sensed component includes a ring structure having a plurality of proximally extending projections circumferentially arranged relative to one another. The projections are shaped and sized to deflect a movable element of the rotation sensor. One embodiment of such a sensed component is a tubular flange 38 (best shown in Figures 3, 5, 8, and 9). The embodiments described herein may be provided with a module that is removably attachable to the dose button of the delivery device or integrated within the dose button of the delivery device.
[0054] During dose delivery, the dose setting screw 32 is free to rotate relative to the dose button 30. In an exemplary embodiment, the electronics assembly 76 is rotatably secured by the dose button 30 and does not rotate during dose delivery.
[0055] As seen in Figures 2, 3, and 5, the dose button 30 includes a cover 56 coupled to the support 42. The electronics assembly 76 may be at least partially housed within a compartment 85 defined between the cover 56 and the support. In some embodiments, the cover and the support have corresponding splines that engage with one another to couple the cover and the support together. For example, in some embodiments, the cover 56 may be coupled to the support 42 via one or more snaps 57 on the cover 56 and corresponding to one or more protrusions 43 on the support. As seen in Figures 5 and 6, the snaps 57 on the cover 56 may be oriented radially inward from the inner peripheral sidewall 73. As seen in Figures 5, 10, and 11, the protrusions 43 of the support 42 may be oriented radially outward from the outer peripheral sidewall 75 of the support 42. The protrusions 43 may form a triangular ramp shape.
[0056] Snaps 57 on cover 56 are configured to snap over and mate with protrusions 43 of the support to couple the cover to the support. In some embodiments, the protrusions of the support comprise a continuous annular protrusion around the outer peripheral sidewall of the support. Cover 56 may be attached to support 42 via frictional engagement, interference fit, or any other suitable fit. In some embodiments, cover 56 is permanently secured to support 42 during assembly, for example, via ultrasonic welding, adhesive, or other suitable fastening techniques.
[0057] As seen in Figures 8 and 9, the tubular flange 38 may include a plurality of axially oriented teeth 102 evenly spaced radially about the axis of rotation and arranged to correlate to the equivalent of one unit of dosage. In this exemplary embodiment, the tubular flange 38 includes 20 teeth 102 that are rotatably spaced evenly from one another such that the rotational distance between two adjacent teeth corresponds to 18 degrees of rotation. Thus, with the tubular flange 38 of Figure 8, an 18 degree rotation of the tubular flange 38 may be used to represent one dosage unit or one-half dosage unit. It should be understood that in other embodiments, a different total number of teeth may be used to create other angular relationships, such as 9 degrees, 10 degrees, 15 degrees, 18 degrees, 20 degrees, 24 degrees, or 36 degrees for one unit or 0.5 units.
[0058] A recess 124 may be defined between each pair of adjacent teeth 102. Each tooth 102 may have a generally triangular-shaped profile and each may have a surface 120 against which the contact surface 111 of the sensor may slide.
[0059] In some embodiments, the sensor for detecting rotation of the tubular flange includes a spring-loaded movable element having a contact portion mountable to a tooth of the tubular flange such that the contact surface is configured to slide against and over the tooth during rotation of the flange relative to the actuator assembly during dose delivery. The sensor generates a signal corresponding to the flange in response to the contact portion moving over the tooth. The controller, in response to the signal generated by the sensor, determines a dose count for determining a delivered dose based on the detected rotation of the flange relative to the actuator assembly during dose delivery.
[0060] The contact surface may be biased against the physical feature of the tubular flange to ensure proper contact between the contact surface and the physical feature during rotation. In one embodiment, the movable member is a resilient member having one portion attached to the actuator at a position displaced from the contact surface. In one example, the movable member is a compliant member comprising a beam attached to the actuator at one end and having a contact surface at the other end. The beam is bent to bias the contact surface toward the surface feature. Alternatively, the movable member may be biased in any of a variety of other ways. In addition to the use of a resilient beam, biasing may be provided, for example, by the use of a spring component. Such a spring component may comprise, for example, a compression, tension, or torsion coil spring. In yet other embodiments, the movable member may be biased against the surface feature of the sensed element by a separate resilient member or spring component that supports the movable element.
[0061] FIG. 5 depicts an embodiment of a sensor 86 having a contact surface 111 that interacts with the teeth 102 of the tubular flange 38. As the flange 38 rotates relative to the dose button 30 during delivery, the teeth 102 of the flange contact and slide against the contact surface 111 of the sensor 86, causing the contact surface 111 to move in a vibratory fashion. The movement of the contact surface 111 can be a combination of axial and lateral movement such that the contact surface 111 slides into and out of the recesses 124 defined between the teeth 102 of the flange 38. The sensor 86 can be configured to track the movement of the contact surface 111 and associate the movement with an output signal that is sent to the controller. In one embodiment, the sensor 86 is a microswitch, and the contact surface 111 includes a trigger arm extending from the sensor body that can be moved between a neutral position and an actuated position to electronically signal a change in state, typically between an open and closed state, that is used to determine data. In the neutral position, the arm may be biased to a position (generally perpendicular to the body, as shown in FIG. 5). In the actuated position, the arm moves some distance or angle from the neutral position, and after the tines pass, the switch returns to the neutral position. As described below, the contact surface 111 may include different configurations of arms and sensor systems. All sensors described herein may be in an open state when unactuated and in a closed state when actuated, or vice versa, i.e., in a closed state when unactuated and in an open state when actuated.
[0062] As an alternative to teeth on the tubular flange, the surface feature that interacts with the sensor may comprise anything that can be detected by the sensor. The sensor arrangement may be based on a variety of sensed features, including, for example, tactile, optical, electrical, and magnetic properties. In the exemplary embodiment shown in the figures, the surface feature is a physical feature that allows for detection of incremental movement as the dose setting assembly rotates relative to the actuator assembly. In alternative embodiments, the sensor may be a piezoelectric sensor, a magnetic sensor such as a Hall effect sensor, an accelerometer for detecting vibrations, for example vibrations of a ratchet or other detent mechanism, which vibrations can be correlated with rotational movement, an optical sensor such as an accelerometer, a reflective sensor, a circuit breaker sensor, or an optical encoder, or any other sensor suitable for sensing the rotation of a first component relative to a second component.
[0063] In some embodiments, when a user presses axially on surface 60 of dose button 30, the dose button 30 advances distally relative to housing 12, compressing spring 68. Continued distal pressing of dose button 30 results in back-driving of dose setting screw 32 in a helical direction relative to housing 12. As a result, axial pressing of dose button 30 drives dose setting screw 32 and flange 38 to rotate. In some embodiments, the dose detection system is operable to detect a dose only while the dose button is pressed.
[0064] In some embodiments, the electronics assembly may include a clock or timer to determine the time elapsed between counts caused by the triggering of the rotational sensor from the surface features of the sensed element. If no counts are detected by the controller after a period of time, this may be used to indicate that the dose is complete.
[0065] In some embodiments, a single sensing system may be used for both dose detection sensing and wake-up activation. For example, the controller is configured to enable the electronics assembly to wake up or activate to a higher or full power state upon the sensor first sensing rotation of the sensed element. The wake-up feature is configured to enable power transfer from a power source (shown as a battery) to power up the electronic components to sense the dose, to minimize inadvertent power loss or usage when no dose dispensing event occurs. In other embodiments, a separate wake-up switch is provided and disposed within the dose button housing and may be triggered when the dose button is in its distal position. After actuation of the electronics assembly, the controller begins to receive a generated signal from the rotation sensor indicative of the total angular displacement and thus the first to last count of the total number of counts used to determine the delivered dose.
[0066] In some embodiments, the electronics assembly may have a controller configured to receive the output signal from the rotation sensor. The controller of the electronics assembly may be programmed to convert the intermediate signal into a conditioned digital signal, which may be a single step / square wave with a predetermined width representing a predetermined time. In some embodiments, output signals below a predetermined level may be filtered out or ignored.
[0067] According to one aspect, the medication delivery device includes a repeatedly actuable switch that can act as a sensor. In some embodiments, the switch acts as a rotational sensor in the dose detection system described above. However, in other embodiments, the switch can be used to detect other activities, such as cap removal.
[0068] In some embodiments, the switch includes a conductive pad and a cantilever arm that is movable relative to the conductive pad, the cantilever arm may be attached to the printed circuit board at a first end and a second end of the arm is not attached to the printed circuit board and may be free to move relative thereto.
[0069] According to one embodiment, the switch may have one or more features that help enable the switch to be repeatedly opened and closed. The switch may have one or more features that help prevent the switch from plastically deforming during repeated opening and closing, and thus help maintain the durability of the switch.
[0070] In some embodiments, the arm has a first curved portion at a first end of the cantilevered arm that attaches the arm to a printed circuit board. During switch closure, this first curved portion may move toward a straight configuration, and during switch opening, the straight configuration may move back toward the curved configuration. In an unstressed state, this first portion may be biased toward the curved configuration. Thus, the cantilevered arm may act as a spring that stores potential energy as it moves during sliding interaction against the sensed component, and the stored potential energy is released when the sliding contact force against the arm is reduced, causing the arm to move back toward the unstressed state.
[0071] In some embodiments, the cantilever arm can transition from a first curved portion to a second curved portion configured to move toward and contact a conductive pad mounted on a PCB, where contact between the second curved portion and the conductive pad closes the switch, while a lack of contact between the second curved portion and the conductive pad opens the switch.
[0072] In some embodiments, the cantilever arm may include a third curved portion configured to contact and slide against the sensed component, for example against the teeth of the rotating tubular flange 38 shown in Figures 8 and 9. In some embodiments, the third curved portion connects the first curved portion to the second curved portion. In such embodiments, the second curved portion configured to contact the conductive pad may be located at the second end of the cantilever arm, i.e., where the cantilever arm terminates. In other embodiments, the second curved portion connects the first and third curved portions. In such embodiments, the third curved portion configured to contact the sensed component may be located at the second end of the cantilever arm, i.e., where the cantilever arm terminates.
[0073] In some embodiments, having curved portions of the cantilevered arms may help avoid high stress concentrations in the arms and therefore help prevent plastic deformation of the arms, however, it should be understood that in other embodiments, one or more of the curved portions may be shaped differently.
[0074] In some embodiments, the switch may have one or more features that help the switch provide a cleaner, more easily readable output signal so that the controller can more accurately identify when the switch is open and when the switch is closed. In some embodiments, a blocking protrusion may be provided to interact with the second curved portion of the cantilever arm when the arm contacts the conductive pad. This blocking protrusion may be located directly adjacent or near the conductive pad and may prevent the arm from moving past the conductive pad. In some embodiments, the presence of the blocking protrusion may help reduce the "bounce" of the cantilever arm, which may help generate a cleaner output signal from the switch. In some cases, the "bounce" from the cantilever arm may cause quick and repeated contact and separation of the arm and the conductive pad for a short period of time, which may result in a noisy output signal that may be difficult for the controller to interpret. The blocking protrusion may help provide sustained contact between the cantilever arm and the conductive pad to provide a cleaner output signal. In some embodiments, the blocking protrusion may be made from a shock absorbing material that may help dampen the impact of the cantilever arm against the blocking protrusion to reduce bouncing or other vibrations.
[0075] One example of a switch is shown in Figure 12, which depicts a switch 86' having a conductive pad 89 and a contact surface including a cantilever arm 210. The conductive pad 89 and a first end 201 of the cantilever arm 210 are attached to the PCB 77.
[0076] 13 and 14, the cantilever arm 210 begins at a first curved portion 212 at its first end 201 and terminates at a second curved portion 214 at its second end 202. The arm also includes a U-shaped third curved portion 216 that connects the first curved portion 212 to the second curved portion 214. The second curved portion 214 is configured to contact a conductive pad and the third curved portion 216 is configured to contact a sensed component, such as the rotating tubular flange 38 shown in FIGS.
[0077] The switch also includes a base 200 connected to a cantilever arm 210. The base 200 is connected to the PCB to connect the cantilever arm to the PCB. The base and arm may together form a single monolithic component.
[0078] Figures 15-19 depict the cantilever arm 210 of the switch interacting with the rotating flange 38 from Figures 8 and 9. Figure 15 shows the arm 210 in an unstressed state when the third curved portion 216 is in the recess 124 between two adjacent teeth 103, 105. The switch may be positioned in this state when the flange 38 is in its home or zero dose position, for example, before use of the device, before setting a dose, or after dispensing is complete and the device is ready to set a dose.
[0079] 16, the flange 38 begins to rotate relative to the switch and PCB 77. As a result, the tooth 105 slides and pushes against the third curved portion 216 of the arm 210, causing the arm 210 to begin to deflect toward out of the recess 124. The first curved portion 212 begins to move toward a straight configuration and the second curved portion 214 begins to move toward the conductive pad 89.
[0080] In FIG. 17, the flange 38 has been rotated further than in FIG. 16, causing the teeth 105 to slide against the third curved portion 216 and almost completely out of the recess 124. The first curved portion 212 has moved even further toward a straight configuration. As a result, the second curved portion 214 contacts the conductive pad 89, thereby closing the switch. The second curved portion is also pressed against the blocking protrusion 204, preventing the second curved portion from moving further toward the first curved portion 212 and may also help prevent the second curved portion from repeatedly bouncing against the conductive pad 89 in a rapid manner that could result in a noisy output signal.
[0081] 18, the flange 38 has been rotated further than in FIG. 17, with the third curved portion 216 exiting the recess 124 and sliding across the top of the tooth 105. The second curved portion 214 remains in contact with both the conductive pad 89 and the blocking protrusion 204. The blocking protrusion 204 prevents the second curved portion 214 from moving closer to the first curved portion 212.
[0082] Finally, in Figure 19, flange 38 has rotated further than in Figure 18, with third curved portion 216 ceasing to contact tooth 105 and now beginning to contact the next adjacent tooth 107. During this transition, just as the next tooth 107 begins to press against arm 210, the arm, which is spring biased toward the position shown in Figure 15, swings back toward its unstressed state, thus moving first curved portion 212 toward a more curved shape, thereby moving third curved portion 216 toward the opposite direction to the direction of rotation of flange 38, and moving second curved portion 214 away from conductive pad 84, thereby opening the switch. Further rotation of flange 38 continues the cycle, causing the arm to move back toward the conductive pad to close the switch, and so on.
[0083] A first alternative embodiment of the switch is shown in Figures 20 and 21. This embodiment is similar to the embodiment shown in Figures 12-14, except that the second curved portion 224 is curved in the opposite direction. In the embodiment of Figures 12-14, the second curved portion 214 is curved such that the curvature of the second curved portion faces away from the first curved portion 212 when the cantilever arm is in an unstressed state. In the embodiment of Figures 20-21, the second curved portion 224 is curved such that the curvature of the second curved portion faces towards the first curved portion 222 when the cantilever arm is in an unstressed state. In other cases, the base 200, first curved portion 222, and third curved portion 226 of the embodiment of Figures 20-21 are the same as those of the embodiment of Figures 12-14.
[0084] A second alternative embodiment of the switch is shown in Figs. 22-23. In this embodiment, the first curved portion 232 is similar to the first curved portion of the other two embodiments, but the second and third curved portions are different. In this embodiment, the cantilever arm 230 terminates at the second end 202 with a third curved portion 236 instead of the second curved portion 234. The third curved portion 236 is still configured to contact and slide against a sensed component, such as a tubular flange, and the second curved portion 234 is still configured to contact a conductive pad to close the switch. As a result, in some embodiments, the second curved portion 234 connects the first curved portion 232 to the third curved portion 236. Furthermore, the second curved portion 234 is U-shaped. Taking this differently shaped arm in context, Fig. 24 shows the arm 230 interacting with the teeth 102 of the rotating tubular flange 38 and interacting with the conductive pad 89.
[0085] According to one aspect, the cantilever arm may be shaped such that the center of mass of the arm is located above the base to which it is connected. For example, as shown in FIG. 25 where the base and arm structure are upside down, the center of mass 221 of the arm 220 is located above the base 200. Such a feature may aid in assembling the base and arm with a PCB. For example, in some situations, it may be beneficial for a component to be able to stand on its own, for example to utilize reflow soldering. Having the center of mass 221 of the arm 220 located above the base 200 allows the arm and base structure to stand on its own on the PCB. It may also be beneficial for the center of mass to be relatively low, for example closer to the base than the furthest point of the arm at height H. The embodiments of FIGS. 12-14 and 22-23 are also examples of arm shapes having a center of mass located above the base.
[0086] According to one embodiment, the printed circuit board (e.g., printed circuit board 77 of FIG. 6) may include processing circuitry and / or logic for counting the number of times a sensor (e.g., sensor 86) is activated or triggered during an injection to determine the dose size of the injection. As described herein, relative rotational motion between the dose setting assembly and an actuator of the drug delivery device may be sensed to determine the amount of the dose delivered by the drug delivery device, as the sensed relative rotational motion may correlate to the amount of the dose delivered.
[0087] 26A is an exemplary block diagram pictorially illustrating functional aspects of a printed circuit board 2500 for processing signals from a sensor 2502, according to some embodiments. The sensor 2502 is in communication with both a counter block 2504 and a quadrature encoder 2506, both of which are in communication with a controller 2508. The sensor 2502 can be, for example, the sensor 86 of FIG. 6. For example, as described herein, the sensor 86 can be configured to track movement of the contact surface 111 and associate the movement with an output signal that is sent to the counter block 2504 and the quadrature encoder 2506, which can count the number of times the contact surface 111 slides in and out of the recess 124 defined between the teeth 102 of the flange 38, and provide the determined count to the controller 2508 (which can be used to determine the dose of the injection).
[0088] The controller 2508 includes at least one processor (e.g., microprocessor) that executes software and / or firmware stored in the controller's memory. The software / firmware code includes instructions that, when executed by the processor, cause the controller to perform the functions of the control logic and steps described herein. An exemplary controller includes a processing core, memory, power supply, and a communication module. These components can be mounted on and communicate via the printed circuit board 2500. The controller 2508 is operable to perform operations described herein, including determining a number of units indicating a total angular movement of the dose setting member that is used to determine the amount of drug delivered from the drug delivery device based on information received from the sensor 2502. The controller 2508 may store the detected units or angular movement and / or the amount of drug separately or together in a generated dose record in memory. The generated dose record may include a time / date stamp, a dose delivery amount, a battery charge status, an error log message, etc. The controller 2508 may also transmit dose recording data representing the amount of drug or units or angular movement detected via the communication port to a paired remote computing device 2509, such as a user's computer or smartphone or a computing cloud. Information may be transmitted from the communication port via wired or wireless communication protocols, such as Bluetooth low energy (BLE) (shown), WiFi, NFC, or cellular wireless communication protocols.
[0089] In some embodiments, the counter block 2504 and the quadrature encoder 2506 may be configured to process signals from the sensor 2502 using different techniques. Using different techniques may provide some redundancy in measuring signals from the sensor 2502 (e.g., to assess whether a measurement is accurate). FIG. 26B illustrates an exemplary set of six signals, in this example six square waves 2602-2612, each of which may be generated by the sensor 2502 for a particular actuation of the sensor 2502. The horizontal axis represents time and the vertical axis represents voltage. FIG. 27 is a flow chart illustrating an exemplary computerized method 2700 for processing signals from the rotation sensor 2502, according to some embodiments. Referring to the exemplary FIG. 26B and FIG. 27, in step 2702, the counter block 2504 analyzes the received signal using a first technique to generate a first count of the signal. For example, the counter block 2504 may be configured to count the rising edges of each square wave 2602-2612, one of which is labeled, for illustrative purposes, as rising edge 2602A of square wave 2602. In step 2704, the quadrature encoder 2506 analyzes the received signal using a second technique to generate a second count of the signal. For example, the quadrature encoder 2506 may be configured to count both the rising and falling edges of each square wave 2602-2612, one of which is labeled, for illustrative purposes, as falling edge 2602B of square wave 2602.
[0090] In some embodiments, the counter block 2504 and the quadrature encoder 2506 may be configured to process signals from the sensor 2502 using different sampling rates. For example, the counter block 2504 may have a sample rate configured to sample signals from the sensor 2502 to sense rising edges of each signal, and the quadrature encoder 2506 may have a different sampling rate configured to sample signals from the sensor 2502 to sense both rising and falling edges of each signal. By way of example, the counter block 2504 may be configured to use a sampling rate of 10 ms (100 Hz), while the quadrature encoder 2506 may be configured to use a sampling rate of 1 ms (1000 Hz).
[0091] In step 2706, the controller determines data indicative of the reliability of the first count, the second count, or both, based on the first count from the counter block 2504 and the second count from the quadrature encoder 2506. For example, the controller 2508 can compare the counts to determine if the counts match, evaluate the accuracy of one count based on the other count, etc.
[0092] In some embodiments, one of the counter block 2504 or the quadrature encoder 2506 can be a primary counting mechanism used to determine the actual count of the number of actuations of the sensor 2502, and the other can be a secondary counting mechanism used to determine the reliability of the signal from the sensor 2502 and / or a measurement of the count of the primary counting mechanism. For example, the counter block 2504 can be used to determine the actual number of times the sensor actuated (e.g., by counting the number of square waves in the signal from the sensor 2502, as described herein). The quadrature encoder 2506 can be used to analyze the same signal to determine whether the signal is a clean signal that should result in an accurate count by the counter block 2504 and / or whether the signal is too distorted / noisy to result in an accurate count. For example, with reference to the example signal shown in FIG. 26B, if the quadrature encoder 2506 determines 12 transitions (e.g., 6 rising edges and 6 falling edges), the controller 2508 can determine that a count of 6 by the counter block 2504 is likely to be an accurate count.
[0093] In some embodiments, the microcontroller 2508 may use a threshold when comparing the count determined by the counter block 2504 to the count from the quadrature encoder 2506 to determine whether the count of the counter block 2504 is reliable. For example, if the signal from the sensor 2502 contains some noise, the counter block 2504 may still achieve an accurate count when using a lower sampling rate than the quadrature encoder 2506 (e.g., because the lower sampling rate may filter out some of the noise in the signal). For example, the controller 2508 may determine that the count from the counter block 2504 is usable if it is within about 2-3 times the count determined by the quadrature encoder 2506. Assuming the sensor generates six actuation signals (e.g., six square waves) and there is some noise such that the quadrature encoder 2506 detects more than six leading edges and six trailing edges, then if the counter block 2504 determines a count of six and the quadrature encoder 2506 determines a count of 12 to 20 transitions, the controller 2508 may register a dose of six units. However, if the quadrature encoder 2506 determines a count greater than 20, the controller 2508 may consider the signal from the sensor 2502 to be too noisy (and, for example, not register the count as a dose).
[0094] In step 2708, the drug delivery device may optionally store, transmit and / or display data regarding the first count and / or the second count. In some embodiments, the drug delivery device may include display data regarding the first count and / or the second count on a display device (e.g., on a user interface, using one or more lights, using flashing lights and / or colored lights, etc.). In some embodiments, the drug delivery device may transmit data regarding the first count and / or the second count to a remote computing device. As described herein, the drug delivery device may be configured to communicate with a remote computing device. For example, the drug delivery device may be configured to communicate with a smartphone running an application. If the controller 2508 determines, based on the counts from the counter block 2504 and the quadrature encoder 2506, that the count generated by the counter block 2504 is reliable (e.g., an estimate of the injected dose can therefore be determined), the controller 2508 may cause the drug delivery device to transmit the calculated dose size to the remote computing device. Alternatively, if the controller 2508 determines that the count is unreliable, the medication delivery device may be configured to not transmit data to the remote computing device and / or transmit data indicative of an unknown or potential dose infusion event. An application running on the remote computing device may be configured to prompt the user to enter and / or verify the infusion amount. For example, even for counts believed to be accurate, the remote computing device may prompt the user to verify the infusion amount. As another example, for counts believed to be potentially inaccurate, the computing device may prompt the user to enter the infusion amount.
[0095] In some embodiments, as described herein, a user can press a dose button (e.g., dose button 30) with a desired pressure, which controls the rate of injection. Thus, in some embodiments, flange 38 can rotate at different speeds for each injection event. By way of example, depending on the pressure applied to the dose button, flange 38 can rotate from as slow as 1 Hz to as fast as 200 Hz.
[0096] In some embodiments, the controller 2508 may be configured to use the quadrature signals from the quadrature encoder 2506 to measure the rate of the infusion. For example, if the quadrature encoder 2506 may be configured to sense both the rising and falling edges of each signal from the sensors 2502, the controller 2508 may determine the time between actuation of each sensor 2502, which may be used to determine the overall rate of the infusion.
[0097] In some embodiments, as discussed further herein, the controller 2508 may measure the time of each injection, such as the start time of the injection, the end time of the injection, and the duration of the injection. The drug delivery device may be configured to store each infusion event as a dose record. The drug delivery device may transmit the dose record data to a remote computing device and / or the cloud, as further described herein.
[0098] In some embodiments, one signal (e.g., one pin of the controller 2508) can wake up the controller 2508 and cause the counter block 2504 and the quadrature encoder 2506 to sense a signal from the sensor 2502. For example, activating a dose button can send a signal that can be used to activate each of the controller 2508, the counter block 2504, and the quadrature encoder 2506.
[0099] FIG. 26A is intended to illustrate functional aspects of a printed circuit board, and therefore it should be understood that the actual circuitry, logic, and / or software may be implemented in a variety of ways without departing from the spirit of the technology described herein. For example, the counter block 2504 and / or the quadrature encoder 2506 may include dedicated hardware configured to perform the associated functionality described herein. As another example, the counter block 2504 and / or the quadrature encoder 2560 may be implemented as part of the hardware of the controller 2508 (e.g., a microcontroller). As a further example, the counter block 2504 and / or the quadrature encoder 2506 may be implemented as part of the sensor 2502. As another example, since both the counter block 2504 and the quadrature encoder 2506 may be used to process signals from the sensor 2502 to determine the dose size of the injected dose, some embodiments may include only one of the counter block 2504 or the quadrature encoder 2506.
[0100] According to one embodiment, the user may receive digital feedback regarding how much medication is remaining in the medication delivery device. When the medication level in the medication delivery device is low, the user may receive an alert from the medication delivery device and / or from an external device notifying the user that the medication level is low. For example, the user may receive an alert from a mobile device, such as from an app, text message, or SMS. The alert may be visual, audible, tactile (e.g., vibration), or any combination thereof.
[0101] As described herein, the printed circuit board can include non-volatile memory. The non-volatile memory can be used to store various usage information about the drug delivery device and store the history of the drug delivery device (e.g., manufacturing data, when the device was first activated, the number of days the device was used, the number of injections, the dose of each injection, the time of each injection, etc.). Because the memory is non-volatile, the drug delivery device can be stored and / or sent back to the manufacturer for analysis.
[0102] In some embodiments, the medication delivery device may include one or more aspects that control when the medication delivery device stores and / or discards data to be written to the non-volatile memory (e.g., if the non-volatile memory is a permanent write-only memory). For example, the medication delivery device may be configured to include a field or flag that the controller checks before writing data, so that the flag can be used to control whether the controller writes the data to the non-volatile memory or discards the data without writing it to the non-volatile memory. The flag may be set to a first value during the supply chain and / or during manufacturing to disable writing to the non-volatile memory. For example, if an inadvertent movement during manufacturing causes a sensor to output a signal (e.g., that may be interpreted as dose injection information), setting the flag to a value representing an invalid state may prevent the microcontroller from writing data to the non-volatile memory. When an appropriate trigger occurs (e.g., a user connects the pen to an application running on a remote computing device, presses a dose button, etc.), the microcontroller may be configured to change the flag to a value representing a valid state, so that when the user operates the medication delivery device, the microcontroller writes the data to the non-volatile memory. Once the flags are updated, the microcontroller will store the data, such as dose injection information, in non-volatile memory.
[0103] In some embodiments, the drug delivery device may include one or more aspects that may be used to control whether the drug delivery device is in an active state or a dormant state (e.g., to control the power consumption of the drug delivery device to conserve battery usage). During manufacturing and / or supply chain of the drug delivery device, the device may be initially set to a dormant state so that the controller is in a low power state to avoid consuming battery life. The controller may include a timer that, when started upon activation of the drug delivery device, causes the controller to return the drug delivery device to a dormant state if no activity is detected by the drug delivery device before the timer expires (e.g., no data indicative of an injection, no connection to an application running on a remote device, etc.). In some embodiments, the timer duration may be a number of hours, days, weeks, and / or any other predetermined period of time. In some embodiments, the timer may be implemented using a counter, and the timer duration may be a number of clock pulses (e.g., representing a desired number of hours, days, etc.). Switching the drug delivery device back to a dormant state may be implemented in a manner that is transparent to the user, allowing the drug delivery device to be activated and function normally when the user activates the drug delivery device even if the drug delivery device was previously returned to a dormant state.
[0104] In some embodiments, the timer may be implemented in combination with a flag used to prevent writing data to non-volatile memory. For example, when the controller is activated to come out of the hibernate state, the controller may check the value of the flag. If the controller determines that the flag is set to disable writing to non-volatile memory, the controller may return the medication delivery device to the hibernate state. Alternatively, if the controller determines that the flag is set to enable writing to non-volatile memory, the controller may proceed to enter the activated state.
[0105] In some embodiments, the technology may be used to manage multiple drug delivery devices. For example, a user may have access to and / or may be using multiple drug delivery devices. Each of the drug delivery devices may include unique identification information such that each device may be uniquely identified. As described herein, the drug delivery device may communicate with an application running on a remote computing device. Each time a user begins using a new drug delivery device, the application may create an entry for the device and keep a history of the infusion information and other information associated with the drug delivery device. For example, for some medications, the drug delivery device may be refrigerated prior to use and is recommended to be used within a predetermined period of time (e.g., within 28 days) after being used for the first time and removed from refrigerated storage. Thus, upon first use, the application may keep a history of the date and time each drug delivery device was activated to provide the user with information regarding when the user should use each drug delivery device.
[0106] In some embodiments, the user may be encouraged to refill their medications and / or, in the case of a reusable medication delivery device, to replace the medication cartridge with a new cartridge. In some embodiments, a refill request may be automatically sent to a pharmacy upon detecting a low medication level.
[0107] In some embodiments, the application can keep a history of how much medication remains in each medication delivery device (e.g., in conjunction with dosage information determined by the medication delivery device and / or input using the application). The application can manage the infusion delivery device to try and use all existing doses before they expire. For example, the application can include a visual indication of how much medication remains in the medication delivery device and / or when the medication delivery device will expire. In some embodiments, if only a certain number of units remain in the medication delivery device, the application can prompt the user to use the medication delivery device so that the user can use the available doses before they expire.
[0108] The method of determining the drug level can be accomplished in different ways. In some embodiments, the external device stores a record of the level of drug remaining in the drug delivery device. The drug delivery device may send a communication to the external device informing the external device of the delivered dose from each drug delivery event. The drug delivery device may determine such dosage information from the sensors described above. The external device may then calculate and store the remaining amount of drug after each drug delivery event. For example, the external device may subtract the delivered dose from the most recent remaining amount of drug.
[0109] In some embodiments, information regarding the amount of drug remaining in the drug delivery device may be calculated and / or stored by the drug delivery device itself, and the drug delivery device may then communicate to an external device how much drug remains in the drug delivery device.
[0110] As described herein, the drug delivery device can operate in various device states and can store various information that can be transmitted to a remote computing device. Figure 30 is a diagram 3000 illustrating various states and associated functionality of a drug delivery device, according to some embodiments. In device state 3002, the drug delivery device 3010 is in a dormant state (e.g., low power mode, no wireless communication). In device state 3004, the drug delivery device 3010 is in an active state, during which the drug delivery device 3010 is available for communication with a remote computing device. During the active state 3004, the drug delivery device performs the operations discussed herein, including activating a sensor upon detection of a first infusion event 3012, determining and recording a dose record 3014, and starting an internal clock of the device at 3016.
[0111] In the device state 3006, the drug delivery device 3010 is in an operational state during which the drug delivery device 3010 is in communication with a remote computing device (not shown, e.g., an application running on a smartphone). The drug delivery device 3010 connects (3014) to the remote computing device, and the drug delivery device 3010 can transmit various data to the remote computing device (e.g., upon request by the remote computing device). As shown by way of example in FIG. 30, the drug delivery device 3010 can transmit data indicative of one or more of the amount of insulin remaining 3016, an indication 3018 of whether the drug in the drug delivery device 3010 is the correct drug, manufacturing and / or supply chain information 3020 of the drug delivery device 3010, such as lot and / or serial number, drug expiration date 3022, and / or battery status 3024.
[0112] In the device state 3008, the drug delivery device is disconnected (3026) from the remote computing device, active and available for communication with another remote computing device (same and / or different device). The drug delivery device 3010 detects the next infusion event at 3028, stores a dose record of the infusion event at 3030, and returns to 3014 to connect to the device and transmit data requested by the device. Steps 3014-3030 can be repeated as necessary to process doses administered by the drug delivery device 3010.
[0113] As described herein in connection with FIG. 30, various manufacturing and drug data are stored in the drug delivery device and may therefore be provided to the remote computing device. In some embodiments, the drug delivery device may determine aspects of the data to be sent to the remote computing device, such as determining the battery status based on battery voltage information. In some embodiments, the drug delivery device may provide data (e.g., voltage information) to the remote computing device that the remote computing device can use to determine the battery status. For example, the remote computing device may be configured to use one or more voltage curves to estimate the battery life remaining in the drug delivery device. In some embodiments, different voltage curves may be used to estimate the remaining battery life, since different types and / or manufacturers of batteries may be used. The remote computing device may use manufacturing data (e.g., lot / serial number) of the drug delivery device to look up data regarding the battery of the drug delivery device to determine the appropriate voltage curve to use to estimate the battery.
[0114] As another example, in some embodiments, the drug delivery device and / or the remote computing device can use data from the drug delivery device to determine data indicative of the effectiveness of an administered dose. For example, the drug delivery device can store data regarding the temperature of the drug delivery device (e.g., at the time of injection, over the life of the drug delivery device, etc.), which can be used to determine the effectiveness of the dose, as temperature can affect the effectiveness of the drug in the drug delivery device.
[0115] In some embodiments, tracking the amount of medication remaining in the medication delivery device may be used for patient compliance purposes. A user, a caregiver, a health care provider, an insurance payer, and / or a company making the medication may want to monitor whether a user is taking the medication in the prescribed amount and / or at the prescribed time. In some embodiments, such information may be used in conjunction with other devices to improve the patient's treatment. For example, the medication delivery device may be used in conjunction with a glucose meter. The dosage delivered to the patient may be paired with glucose level information to determine information such as the effectiveness of the medication, the effectiveness of the patient's prescription regimen, etc. Such information may help improve the patient's treatment, for example, by suggesting possible ways to improve the patient's prescription regimen.
[0116] According to one aspect, the medication delivery device may have the ability to assist a user in locating the medication delivery device. The inventors have recognized that a user may have difficulty finding his or her medication delivery device, especially when it is portable and can be used in different locations. The inventors have recognized the need for a device location assistance to assist a user in locating the device.
[0117] In some embodiments, the location of the drug delivery device is tracked by one or more mobile devices. For example, the drug delivery device may be configured to communicate with one or more mobile devices or with other external devices, such as a remote server. The communication may be one-way or two-way.
[0118] In some embodiments, the drug delivery device periodically advertises information such as a unique identifier. The mobile device may periodically scan for drug delivery devices, and if an advertising drug delivery device is within communication range with the mobile device, the mobile device receives a communication from the drug delivery device. The mobile device, which may have built-in GPS or other location identification capabilities, may then associate a location with each received communication. In particular, if the communication protocol between the drug delivery device and the mobile device is a short-range communication protocol such as Bluetooth, the mobile device may assign its own current location, or a radius around its own current location, as the location of the drug delivery device. In some embodiments, when the mobile device no longer receives communication from the drug delivery device, indicating that perhaps the drug delivery device has moved out of the communication range of the mobile device, the mobile device stores the most recent location of the drug delivery device, which may be when the mobile device last received communication from the drug delivery device. This most recent location may be presented to the user to assist the user in determining the location of the drug delivery device.
[0119] In some embodiments, when the mobile device comes into communication range with a medication delivery device, the mobile device may inform the user that the medication delivery device is nearby, which may be used to assist the user in physically locating the medication delivery device.
[0120] In some embodiments, when the mobile device senses that the medication delivery device is no longer within communication range with the mobile device (e.g., the mobile device does not receive notifications from the medication delivery device within an expected period of time), the mobile device may notify the user that the medication delivery device is no longer nearby, or at least no longer near the mobile device itself. Such a feature may help the user avoid forgetting to bring the medication delivery device when the user leaves a location.
[0121] In some embodiments, multiple mobile devices may cooperate to help locate a medication delivery device. For example, a group of mobile devices may be configured to periodically scan for medication delivery devices. When one of the mobile devices locates a medication delivery device (e.g., by sensing that the medication delivery device is within communication range), it may communicate the identity and / or location of the found medication delivery device to the remaining mobile devices. This may be used, for example, in a household setting where each household member has their own mobile device.
[0122] In some embodiments, the medication delivery device may include a built-in speaker. To assist the user in finding the medication delivery device, the speaker may be triggered by the user to emit a sound. In some embodiments, the user may use the mobile device to trigger the speaker to emit a sound.
[0123] In some embodiments, the drug delivery device itself may have built-in GPS or other location-determining capabilities. The drug delivery device may communicate its location directly to a mobile device or other external device, for example to a remote server.
[0124] According to one aspect, the date, and in some embodiments the time, that the medication delivery device was first used is tracked.
[0125] One exemplary use case for such a feature is determining a medication expiration date. For example, in some embodiments, the medication delivery device may communicate to an external device that a user has opened, turned on, or activated the medication delivery device for the first time. The external device may ascertain whether the medication has expired, for example, by looking up the identification number of the medication delivery device in an expiration date database.
[0126] Another exemplary use case of such features is to aid in supply chain management. Still referring to Figure 30, various manufacturing and supply chain data may be stored by the drug delivery device 3010, such as manufacturing information (e.g., lot / serial number) 3020, expiration date data 3022, and battery status data 3024. Additional information may be maintained, such as initial activation data, temperature data, dosage records, and / or other data as described herein.
[0127] In some embodiments, the remote computing device can also interface with a remote server and / or a cloud computing device to process manufacturing / supply chain data. For example, the remote computing device can use manufacturing data from the drug delivery device to determine additional information about the drug delivery device, such as when the drug delivery device was manufactured, the duration from manufacturing to first use, etc. As another example, the remote computing device can obtain information determined by the drug delivery device throughout the manufacturing process, such as temperature throughout the supply chain, battery life throughout the supply chain, etc. As a further example, the drug delivery device information can be used to identify and / or prevent the use of counterfeit devices.
[0128] In some embodiments, implant data, such as the counts determined by counter block 2504 and the counts from quadrature encoder 2506, may be used for manufacturing purposes. For example, implant data may be used to monitor the performance of devices during manufacturing. In some examples, count data may be used to understand the performance of a product over various batches. For example, count data and / or other data may be used to identify defective batches of devices (e.g., to flag the batches in the system and / or to notify users of the devices to discard their devices). Such data may be used for process improvement, such as to identify manufacturing issues, material issues, material problems, etc.
[0129] Supply chain data may be used for a variety of purposes by the drug delivery device and / or the remote computing device. For example, knowing when a particular drug delivery device was first activated can pass important supply chain information to the manufacturer, such as how long it took for the drug delivery device to reach and be used by the user after the manufacturer shipped it for sale. When communicating the first use to the external device, the drug delivery device also communicates its specific identification number, allowing the manufacturer to associate the information with known devices and store the information in a database. The information may be categorized by device type, geography, etc.
[0130] In some embodiments, the time elapsed since the first use of the drug delivery device may be monitored. With some types of medications and drug delivery devices, the drug in the drug delivery device expires after a certain amount of time has passed since the drug delivery device was first used to deliver a quantity of drug. This may apply especially to multi-dose drug delivery devices. Thus, the drug delivery device may detect when the user activates the device to deliver the drug for the first time. In some embodiments, the device may then start a countdown of an internal timer and inform the user that the drug has expired when the timer reaches a predetermined time. Examples of alerts include turning a light on, off, or flashing, and / or using a particular color of light, an auditory sound, a vibration, or any combination thereof. In some embodiments, the drug delivery device may prevent the user from activating the device, for example, by a physical and / or electrical lockout that would make delivery impossible. In some embodiments, when the drug delivery device detects that the user has activated the device to deliver the drug for the first time, the drug delivery device may communicate to an external device that the first delivery has occurred. The external device may then start a countdown to the expiration date of the drug. When the countdown is complete, the external device may send an alert to the user and / or communicate to the medication delivery device that the medication has expired.
[0131] According to one aspect, the temperature of the drug may be monitored. The temperature of the drug may be monitored directly or indirectly. An example of a direct measurement includes placing a temperature sensor in actual contact with the drug. An example of an indirect measurement includes using a temperature sensor to measure the temperature of an area or component near the drug to approximate the actual temperature of the drug. For example, in one embodiment, the temperature sensor is located on a PCB of the drug delivery device. Another example of an indirect measurement includes directly measuring the temperature of a material in the drug delivery device that behaves in a realistic manner when exposed to various temperature environments.
[0132] Temperature measurements may occur periodically, information regarding the measured temperature may be stored within the drug delivery device, communicated to an external device, or any combination thereof, each time a measurement occurs, or in batches.
[0133] When the drug delivery device senses that the measured temperature is outside of an acceptable temperature range, referred to herein as a "temperature excursion," various responses may occur. In some embodiments, the drug delivery device may directly inform the user and / or communicate the information to one or more external devices, which in turn inform the user. An alert may occur in real time when a temperature excursion is detected, or the next time the user uses the drug delivery device. In some embodiments, when a temperature excursion is detected, the drug delivery device may store and / or communicate to an external device the time and / or date of the temperature excursion, as well as the measured temperature.
[0134] According to one aspect, the drug delivery device and / or an external program communicating with the drug delivery device, such as a mobile device app, may include security features to control wireless communication between the drug delivery device and the external device. In some embodiments, the drug delivery device includes a bond management feature that prevents unwanted access to the drug delivery device from a third party. In this bond management feature, users have already paired their drug delivery device to their mobile device, which may run an app specialized for use with the drug delivery device. If a different mobile device attempts to connect with the drug delivery device, the user may receive a notification that a third party is attempting to connect with the drug delivery device. The user may allow or deny the third party from connecting with the drug delivery device. In some embodiments, this setting may be "remembered" by the app and / or the drug delivery device to avoid repeated notifications. In some embodiments, the app may be configured to include a menu that allows the user to change past permission settings, e.g., allow access to a previously denied third party mobile device, or deny access to a previously approved third party mobile device.
[0135] Bluetooth Low Energy devices can be difficult to connect to remote computing devices such as smartphones in a secure manner because most use a secure connection (which can take time to establish) and then transmit plaintext data over the secure connection. In order to simplify the pairing process and make it hassle-free for users, a new pairing process is described below. In the new pairing method, the Bluetooth connection remains open so that the connection can be made quickly, but the data transmitted over the open connection is encrypted using a symmetric key. The inventors believe that this pairing method may enable users to quickly pair a BLE device to a smartphone while still establishing a secure connection.
[0136] FIG. 28 is a flow chart illustrating an example encryption scheme 2800 that uses an open (unencrypted) communication channel to exchange encrypted information and accesses the encrypted information from a cloud computing device, according to some embodiments. In step 2802, the medication delivery device generates infusion event information (e.g., in response to a user performing an infusion event). The infusion event information may be recorded in a dose record, as described herein. In step 2804, the medication delivery device connects to a remote computing device, such as by using an open / unencrypted wireless communication channel. For example, in the case of Bluetooth communication, the medication delivery device and the remote computing device may connect by agreeing to communicate at a particular time and frequency (e.g., channel), but without performing a handshake process and / or encryption key exchange.
[0137] In step 2806, the drug delivery device transmits data of the infusion event, which the remote computing device receives, and the data of the infusion event may include encrypted infusion event information and unencrypted data used to obtain an encryption key for decrypting the encrypted data (e.g., in this example, a unique identifier of the drug delivery device such as a serial number). In some embodiments, the drug delivery device may be configured to transmit data upon request by the remote computing device. Thus, the remote computing device may request infusion data from the drug delivery device, and the drug delivery device may transmit any available (e.g., not yet transmitted to the remote computing device) data. Because the encryption protocol may be managed separately from the wireless communication protocol, the device may be configured to transmit data in any desired format and may be changed over time. For example, the encryption key is requested using an identifier of the drug delivery device, but may be changed as desired. As another example, the format of the dose record data may be configured and / or changed as desired.
[0138] In step 2808, the remote computing device uses the unencrypted data to obtain a decryption key from a cloud computing device (e.g., a cloud computing device provided by the company that provided the medication delivery device). In step 2810, the remote computing device can use the obtained decryption key to decrypt the encrypted infusion event information.
[0139] In some embodiments, it may be desirable to avoid the use of the provided cryptographic techniques. For example, it may be desirable to avoid the need to perform a handshake process required to set up an encrypted communication channel (e.g., the handshake process used for encrypted Bluetooth communication). The handshake process may be burdensome to the user, given the length of time it may take, the difficulty of completing the handshake process, etc. As another example, some devices store a list of paired devices, so if a user uses multiple medication delivery devices, a very long list of paired devices may result on the user's smartphone. Using custom cryptographic techniques instead of existing cryptographic techniques may avoid such problems and hassles. Additionally or alternatively, using custom cryptographic techniques may allow custom control of the cryptographic environment by the medication delivery device provider (e.g., allowing the provider to change cryptographic protocols, cryptographic processes, etc.).
[0140] As part of the encryption process, the drug delivery device user may be required to first register with the application provider before being able to use the application. For example, the user may need to create an account and perform various authentication requirements before being granted access to the application. In addition, the particular encryption key used by the drug delivery device may be unique to the drug delivery device. Thus, even if the application is hacked and the hacker is able to infer the identity of the drug delivery device, the hacker cannot simply decrypt the drug delivery device communications, since the device may be located anywhere in the world.
[0141] FIG. 29 is a flow chart illustrating an example encryption scheme 2900 that uses an open (unencrypted) communication channel to exchange encrypted information and determines cryptographic information from a barcode on a medication delivery device, according to some embodiments. In step 2902, a remote computing device captures an image of a barcode on a medication delivery device. The barcode may be, for example, a two-dimensional barcode located on one of the medication delivery devices. In step 2904, the remote computing device decrypts the barcode to determine cryptographic information (e.g., a private encryption key) associated with the medication delivery device. The barcode may include the cryptographic information as well as other information associated with the medication delivery device, such as a unique identifier / serial number of the medication delivery device. The application may add the medication delivery device (based on its serial number) to a list of devices the user is using and associate the cryptographic information with the device entry.
[0142] In step 2906, the drug delivery device generates infusion event information (e.g., to be recorded in a dose record). In step 2908, the drug delivery device connects to a remote computing device, such as by using an open / unencrypted wireless communication channel as described herein. In step 2910, the drug delivery device transmits the encrypted infusion event information, which is received by the remote computing device. In step 2912, the remote computing device decrypts the encrypted infusion event information received in step 2910 using the decryption key determined in step 2904.
[0143] In some embodiments, the drug delivery device may include a termination feature that disables wireless transmissions when a user has finished using the drug delivery device. For example, if a user discards the drug delivery device, the termination feature may be used to prevent the barcode from being scanned and the encrypted data from being read and decrypted from the device. In some embodiments, the termination feature may be activated, such as upon an indication by the user within an application that the user is no longer using the drug delivery device after the expiration of a predetermined period of time.
[0144] In some embodiments, the drug delivery device may be configured to transmit wireless advertising packets for a short-range wireless communication protocol (e.g., used to connect to a remote computing device). The advertising packets may include various data such as cryptographic information (e.g., cryptographic keys), an identifier of the drug delivery device, and the like. In some embodiments, the drug delivery device may transmit unencrypted advertising packets since the communication protocol is only a short-range protocol. Thus, in such embodiments, the remote computing device does not need to decrypt the advertising packets to obtain the serial number of the drug delivery device, and the like. In some embodiments, the drug delivery device may encrypt the advertising packets. For example, the mobile application may obtain the information required to decrypt the advertising packets by decoding the barcode (e.g., as discussed in connection with FIG. 29). The mobile application may store a set of all active drug delivery devices and associated cryptographic information and attempt to decrypt the received advertising packets until the mobile application successfully decodes the received advertising packets.
[0145] According to one aspect, if the drug delivery device undergoes a recall, the user may be notified by an external device or by the drug delivery device itself. In some embodiments, the drug delivery device broadcasts its unique identification number to an external device that may communicate with a remote server having a database that associates recall information with the identification number. The drug delivery device may communicate directly with the remote server itself.
[0146] In some embodiments, an external device, such as a mobile device, informs the user that the medication delivery device and / or the medication within the device has undergone a recall and should not be used. The alert may take different forms, including a message displayed by an app running on the mobile device, via text message, via SMS, via email, or any combination thereof.
[0147] In some embodiments, the medication delivery device may be instructed by an intermediate external device, such as a remote server and / or a mobile device, to show an alert informing the user that the medication delivery device and / or medication have been recalled and should not be used. In some embodiments, the medication delivery device may activate a physical and / or electrical lockout that prevents the device from being used.
[0148] According to one embodiment, the drug delivery device can be used to detect failure to administer a dose according to the user's predetermined regimen. For example, if the user accidentally administers two doses at once or too close in time, an external device or the drug delivery device itself will notify the user of the error. As another example, the user may accidentally or intuitively forget to administer a dose or use the wrong dose.
[0149] Detection of this type of error may give the user an opportunity to take remedial action. The external device may provide the user with suggestions for remedial action, may notify the user's healthcare provider, may connect the user to a healthcare provider, or any combination thereof.
[0150] In some embodiments, the drug delivery device may be capable of detecting delivery of the drug and may also be capable of detecting the delivered dosage, and thus be able to monitor such errors. The drug delivery device may communicate such information to an external device.
[0151] The external delivery device or the drug delivery device itself may then determine whether such dosing was appropriate. In some embodiments, the external device or the drug delivery device itself may compare the timing and dosage of the actual dosing against the expected dosing. If the actual dosing does not match the expected dosing, the external device and / or the drug delivery device may inform the user, for example, that they have missed a dose, administered too much or too little, or any combination thereof. In one exemplary embodiment, the drug delivery device communicates the dosage and delivery time to the mobile device. The mobile device then communicates with a remote server to determine whether this actual dosing is consistent with the expected pre-determined regimen. If the actual dosing does not match the expected regimen, the mobile device informs the user of the dosing error. In a dose miss situation, the remote server may communicate with the mobile device to inform the mobile device of the dosage that should have been administered. If the mobile device does not receive information from the drug delivery device indicating that the dose was administered, the mobile device may send an alert to the user to remind the user to take their medication.
[0152] In some embodiments, the drug delivery device may include an on-board oscillator-based clock (e.g., on a printed circuit board) that counts clock pulses incrementally over time. Oscillator-based clocks may be less accurate than other types of clocks, such as quartz-based clocks, and therefore may be subject to drift that may cause clock measurements to be inaccurate over time. For example, the clock may have little or no drift the first day the drug delivery device is activated, but the drift may increase each day. For example, after two days, the drift may be off by 4 minutes, after five days, the drift may be off by 10 minutes, etc.
[0153] In some embodiments, the drug delivery device may be configured to periodically synchronize the clock time with a remote clock source (e.g., by connecting to an application on the remote device). Such synchronization may reduce the amount of drift of the clock over time. For example, upon initial activation of the drug delivery device, the clock value may be zeroed and the clock may begin counting at that point. Periodically, the drug delivery device is reset (e.g., to zero and / or a particular value) at each predetermined time period (e.g., number of hours, days, etc.), after each injection, each time the drug delivery device connects to a remote device, etc. As another example, the mobile application may keep a history of threshold counter values used to determine when to reset the clock (e.g., a reset may be triggered when the clock counter is greater than a threshold). For example, the threshold may be set to a count value indicating 12 hours, 1 day, 2 days, etc.
[0154] In some embodiments, the clock reset may be controlled by the remote device. For example, when using a counter threshold, the mobile device may resynchronize the drug delivery device clock when the mobile device determines that the drug delivery device counter is greater than the threshold. The mobile device may store an initial activation time when the drug delivery device clock first activates. The remote device may then maintain a history of each reset event. For example, the mobile application may maintain a history of the number of resets, the time of each reset, the clock value at each reset, and / or other relevant information.
[0155] The mobile device can determine the time of each injection using stored clock information including reset event data. For example, a clock counter can be zeroed upon initial activation, and the mobile device can record an initial activation time of 1:00 PM on day zero (e.g., recorded using a universal time such as Greenwich Mean Time), which the application can store locally on the remote device. Then, when the mobile device receives data indicating an injection, the remote device can determine an associated injection time based on dose record data transmitted by the drug delivery device, where the dose storage data can include clock information such as the current clock counter and the number of resets. Continuing with the above example of an initial activation time of 1:00 PM on day zero, assume that the mobile device receives dose record data with a clock counter indicating 60 minutes and no resets. The mobile device can be configured to determine that after 60 minutes the clock is likely to have a drift of approximately 1 minute, and therefore assign day zero 1:00 PM+59 seconds=1:59 PM.
[0156] In some embodiments, the techniques may include performing a clock reset based on one or more other triggers in addition to and / or instead of periodic synchronization (e.g., synchronizing with a phone as described herein). In some embodiments, the clock reset may be triggered based on one or more factors that may affect the accuracy of the clock. For example, the clock may be affected by battery life, temperature, moisture, movement, etc. As an example, oscillator-based clocks may be sensitive to rapid temperature changes, so the device may be configured to synchronize the clock if a temperature change is detected over a period of time that exceeds a threshold configured for clock synchronization.
[0157] The illustrated device is what is commonly referred to as a reusable pen-type drug injection device that is manually operated by a user to selectively set a dose and then inject the set dose. This type of injection device is well known, and the description of the device is merely exemplary, since the sensing system can be adapted for use with variously configured drug delivery devices, including otherwise constructed pen-type drug injection devices, alternatively shaped injection devices, and infusion pump devices. The drug can be any of the types that can be delivered by such drug delivery devices. The device is intended to be exemplary and not limiting, since the sensing system described further below can be used with other otherwise configured devices.
[0158] The techniques operating according to the principles described herein may be implemented in any suitable manner. The process and decision blocks of the above flow charts represent steps and acts that may be included in algorithms that perform these various processes. The algorithms derived from these processes may be implemented as software integrated with and directing the operation of one or more single-purpose or multi-purpose processors, as functionally equivalent circuits such as digital signal processing (DSP) circuits or application specific integrated circuits (ASICs), or in any other suitable manner. It should be understood that the flow charts included herein do not represent any particular circuit, or the syntax or operation of any particular programming language or type of programming language. Rather, the flow charts illustrate functional information that one skilled in the art may use to manufacture circuits that perform the processing of a particular device implementing the techniques of the types described herein, or to implement computer software algorithms that perform the processing of that particular device. It should also be understood that, unless otherwise indicated herein, the particular sequence of steps and / or acts described in each flow chart are merely illustrative of algorithms that may be implemented and varied in implementations and embodiments of the principles described herein.
[0159] Thus, in some embodiments, the techniques described herein may be embodied in computer-executable instructions implemented as software, including application software, system software, firmware, middleware, embedded code, or any other suitable type of computer code. Such computer-executable instructions may be written using any of a number of suitable programming languages and / or programming or scripting tools, and may be compiled as executable machine code or intermediate code that runs on a framework or virtual machine.
[0160] When the techniques described herein are embodied as computer-executable instructions, these computer-executable instructions may be implemented in any suitable manner, including as a number of functional facilities, each of which provides one or more operations for completing the execution of an algorithm operating according to these techniques. A "functional facility" is an instantiated, but structural component of a computer system, which is integrated with one or more computers and, when executed by one or more computers, causes the one or more computers to perform a particular operational role. A functional facility may be a portion or an entire software element. For example, a functional facility may be implemented as a function of a process, or as a separate process, or as other suitable processing units. When the techniques described herein are implemented as multiple functional facilities, each functional facility may be implemented in its own way, and need not all be implemented in the same way. In addition, these functional facilities may be executed in parallel and / or serially as needed, and may pass information between each other using shared memory on the computer on which they are executed, using a message passing protocol, or in other suitable manners.
[0161] Generally, functional facilities include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically, the functionality of the functional facilities may be combined or distributed as desired in the systems in which they operate. In some implementations, one or more functional facilities that implement the techniques herein may together form a complete software package. These functional facilities may, in alternative embodiments, be adapted to interact with other unrelated functional facilities and / or processes to implement a software program application.
[0162] Several exemplary functional facilities for performing one or more tasks are described herein. However, it should be understood that the described functional facilities and divisions of tasks are merely examples of types of functional facilities that may implement the exemplary techniques described herein, and the embodiments are not limited to being implemented with any particular number, division, or type of functional facilities. In some implementations, all functionality may be implemented in a single functional facility. It should also be understood that in some implementations, some of the functional facilities described herein may be implemented together with others or separately (i.e., as a single unit or separate units), or some of these functional facilities may not be implemented.
[0163] Computer-executable instructions implementing the techniques described herein (when implemented as one or more functional facilities or in any other manner) may, in some embodiments, be encoded on one or more computer-readable media to provide functionality to the media. Computer-readable media include magnetic media such as hard disk drives, optical media such as compact disks (CDs) or digital versatile disks (DVDs), persistent or non-persistent solid-state memory (e.g., flash memory, magnetic RAM, etc.), or any other suitable storage media (schematically shown as "memory" in FIG. 26A). Such computer-readable media may be implemented in any suitable manner. As used herein, "computer-readable media" (also referred to as "computer-readable storage media") refers to tangible storage media. Tangible storage media are non-transitory and have at least one physical structural component. In "computer-readable media," as used herein, the at least one physical structural component has at least one physical characteristic that may be altered in some way during the process of creating a medium with embedded information, recording information thereon, or any other process of encoding the medium with information. For example, the magnetization state of portions of the physical structure of the computer-readable medium may be altered during the recording process.
[0164] Additionally, some of the techniques described above include the act of storing information (e.g., data and / or instructions) in a particular manner for use by those techniques. In some implementations of these techniques, such as those in which the techniques are implemented as computer-executable instructions, the information may be encoded on a computer-readable storage medium. Where particular structures are described herein as advantageous formats for storing this information, those structures may be used to impart a physical organization of the information when encoded on the storage medium. Those advantageous structures may then provide functionality to the storage medium by affecting the operation of one or more processors that interact with the information, for example, by enhancing the efficiency of computer operations performed by the processors.
[0165] While the techniques may be embodied as computer-executable instructions, in some, but not all, implementations these instructions may be executed on one or more suitable computing devices operating in any suitable computer system, or one or more computing devices (or one or more processors of one or more computing devices) (shown diagrammatically as controller 2508 in FIG. 26A) may be programmed to execute the computer-executable instructions. A computing device or processor may be programmed to execute the instructions when the instructions are stored in a manner accessible to the computing device or processor, such as a data store (e.g., an on-chip cache or instruction register, a computer-readable storage medium accessible via a bus, a computer-readable storage medium accessible via one or more networks and accessible by the device / processor, etc.). The functional facilities containing these computer-executable instructions may be integrated with and direct the operation of a single general-purpose programmable digital computing device, a cooperative system of two or more general-purpose computing devices that share processing power and jointly perform the techniques described herein, a single computing device or a cooperative system of computing devices (co-located or geographically distributed) dedicated to performing the techniques described herein, one or more field programmable gate arrays (FPGAs) for implementing the techniques described herein, or any other suitable system.
[0166] The computing device may comprise at least one processor, a network adapter, and a computer-readable storage medium. The computing device may be, for example, a desktop or laptop personal computer, a personal digital assistant (PDA), a smart mobile phone, a server, or any other suitable computing device. The network adapter may be any suitable hardware and / or software that enables the computing device to communicate wired and / or wirelessly with any other suitable computing device over any suitable computing network. The computing network may include wireless access points, switches, routers, gateways, and / or other network equipment, as well as any suitable wired and / or wireless communication medium for exchanging data between two or more computers, including the Internet. The computer-readable medium may be adapted to store data to be processed and / or instructions to be executed by the processor. The processor enables the processing of data and the execution of instructions. The data and instructions may be stored on the computer-readable storage medium.
[0167] A computing device may additionally have one or more components and peripherals, including input devices and output devices. These devices may be used, among other things, to present a user interface. Examples of output devices that may be used to provide a user interface include a printer or display screen for visual presentation of output, and a speaker or other sound generating device for audible presentation of output. Examples of input devices that may be used for a user interface include pointing devices such as a keyboard, mouse, touchpad, digitizer tablet, etc. As another example, a computing device may receive input information through voice recognition or in other audible forms.
[0168] Embodiments have been described in which the present technology is implemented in circuits and / or computer-executable instructions. It should be understood that some embodiments may be in the form of a method, of which at least one example is provided. The acts performed as part of the method may be ordered in any suitable manner. Thus, although shown as sequential acts in the exemplary embodiments, embodiments may be constructed in which acts are performed in an order different from that shown, which may include performing some acts simultaneously.
[0169] Various aspects of the above embodiments may be used alone, in combination, or in various arrangements not specifically discussed in the foregoing embodiments, and therefore are not limited in their application to the details and arrangements of components set forth in the foregoing description or illustrated in the drawings. For example, aspects described in one embodiment may be combined in any manner with aspects described in other embodiments.
[0170] The use of ordinal terms such as "first," "second," "third," etc. in the claims to modify claim elements does not, by itself, imply any priority, precedence, or ordering of a claim element relative to another or the temporal order in which acts of a method are performed, but is used merely as a label to distinguish a claim element having a particular name from another element having the same name (but because of the use of ordinal terms) to distinguish between claim elements.
[0171] Also, the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of "including," "comprising," "having," "containing," "involving," and variations thereof are meant to encompass the items listed thereafter and equivalents thereof as well as additional items.
[0172] The term "exemplary" is used herein to mean serving as an example, instance, or illustration. Thus, any embodiment, implementation, process, feature, etc. described herein as exemplary is to be understood as an exemplary example and not as a preferred or advantageous example, unless otherwise specified.
[0173] By clarifying the use of the following and notifying the public hereof, 、 , ...and <n> At least one of the following" or "< / n> 、 、... <n> , or at least one of these combinations" or "< / n> 、 , ...and / or <n>The phrase " " is defined by the applicant in its broadest sense and supersedes any other implied definition above or below, unless expressly asserted to the contrary by the applicant, to mean one or more elements selected from the group including A, B... and N. In other words, the phrase means any combination of one or more of the elements A, B,... or N, including any one element alone or that one element in combination with one or more of the other elements, which may also include additional unlisted elements.
[0174] While various embodiments have been described, it will be apparent to those skilled in the art that many more embodiments and implementations are possible. Thus, the embodiments described herein are examples and are not the only possible embodiments and implementations. Moreover, the advantages described above are not necessarily the only advantages, and it is not necessarily expected that all of the advantages described will be achieved in each embodiment.
[0175] Various aspects are described in this disclosure, including but not limited to the following aspects.
[0176] [Aspect 1] A medication delivery device comprising: a housing with a reservoir of sufficient size to hold a medication; a dose button rotatable relative to the housing for selecting a dose size of the medication for injection; a printed circuit board; a switch mounted on the printed circuit board; and a controller in communication with the switch, the controller configured to: receive a set of signals from the switch; generate a first count of the set of signals using a first counting technique based on the set of signals; generate a second count of the set of signals using a second counting technique based on the set of signals; and determine data indicative of reliability of the first count, the second count, or both, based on the first count and the second count.
[0177] [Aspect 2] A drug delivery device as described in aspect 1, wherein the controller includes a counter block configured to analyze the set of signals using a first counting technique to generate a first count.
[0178] [Aspect 3] The drug delivery device of aspect 2, wherein the counter block is configured to generate the first count by counting the number of signals in the set of signals.
[0179] [Aspect 4] The drug delivery device of aspect 3, wherein each signal in the set of signals includes an associated square wave, each associated square wave including a rising edge at a beginning of the square wave, the counter block is configured to sample the set of signals at a sampling rate configured to capture each rising edge of each square wave, and generating the first count includes counting the number of rising edges.
[0180] [Aspect 5] A drug delivery device described in any one of aspects 1 to 4, wherein the controller includes a quadrature encoder configured to analyze the set of signals using a second counting technique to generate a second count.
[0181] [Aspect 6] The drug delivery device of aspect 5, wherein each signal in the set of signals includes an associated square wave, each square wave including a rising edge at a beginning of the square wave and a falling edge at an end of the square wave, the quadrature encoder is configured to sample the set of signals at a sampling rate configured to capture each rising edge and each falling edge of each square wave, and generating the second count includes counting a number of rising edges and a number of falling edges.
[0182] [Aspect 7] A drug delivery device described in any one of aspects 1 to 6, wherein the switch includes a contact surface arm extending from the printed circuit board, the arm configured to move to close or open the switch, and the drug delivery device further includes a rotatable element that is rotatable relative to the printed circuit board, the rotatable element having a series of protrusions spaced apart from each other, the rotatable element positioned to enable the protrusions to slide relative to the contact surface arm to move the switch to one of the closed or open states when the rotatable element is rotated.
[0183] [Aspect 8] A drug delivery device described in any one of aspects 1 to 6, wherein the switch includes a piezoelectric sensor, a magnetic sensor, an accelerometer, an optical sensor, a circuit breaker sensor, an optical encoder, or some combination thereof.
[0184] [Aspect 9] The drug delivery device described in Aspect 8, wherein the magnetic sensor is a Hall effect sensor.
[0185] [Aspect 10] The drug delivery device described in Aspect 8, wherein the optical sensor is a reflective sensor.
[0186] [Aspect 11] A computerized method executed by a controller of a medication delivery device, the controller communicating with a switch mounted on a printed circuit board, the method including receiving a set of signals from the switch; generating a first count of the set of signals using a first counting technique based on the set of signals; generating a second count of the set of signals using a second counting technique based on the set of signals; and determining data indicative of reliability of the first count, the second count, or both, based on the first count and the second count.
[0187] [Aspect 12] The computerized method of aspect 11, further comprising: using a counter block of the controller, analyzing the set of signals using a first counting technique to generate a first count.
[0188] [Aspect 13] The computerized method of aspect 12, further comprising generating a first count by counting, by a counter block, the number of signals in the set of signals.
[0189] [Aspect 14] The computerized method of aspect 13, wherein each signal in the set of signals includes an associated square wave, each associated square wave including a rising edge at a beginning of the square wave, and the method further includes sampling the set of signals by a counter block at a sampling rate configured to capture each rising edge of each square wave, and generating a first count, the first count including counting a number of rising edges.
[0190] [Aspect 15] The computerized method of any one of aspects 11 to 14, further comprising: using a quadrature encoder of the controller to analyze the set of signals using a second counting technique to generate a second count.
[0191] [Aspect 16] The computerized method of aspect 15, wherein each signal in the set of signals includes an associated square wave, each square wave including a rising edge at a beginning of the square wave and a falling edge at an end of the square wave, and the method further includes sampling the set of signals with a quadrature encoder at a sampling rate configured to capture each rising edge and each falling edge of each square wave, and generating a second count, the second count including counting a number of rising edges and a number of falling edges.
[0192] [Aspect 17] A medication delivery device comprising: a housing having a reservoir of sufficient size to hold a medication; a dose button rotatable relative to the housing for selecting a dose size of the medication for injection; a wireless communication module; and a controller in communication with the wireless communication module, the controller being configured to: generate injection event information of the medication delivery device; use the wireless communication module to connect to a remote computing device for wirelessly communicating with the remote computing device over an unencrypted wireless communication channel; and use the wireless communication module to transmit encrypted data to the remote computing device over the unencrypted wireless communication channel, the encrypted data including data indicative of the injection event information.
[0193] [Aspect 18] The drug delivery device of aspect 17, further comprising a two-dimensional barcode encoding encrypted data that can be used by the computing device to decrypt the encrypted data.
[0194] [Aspect 19] A drug delivery device as described in Aspect 18, wherein the encryption data includes a private encryption key.
[0195] [Aspect 20] A drug delivery device described in any one of aspects 17 to 19, wherein transmitting encrypted data further includes transmitting an unencrypted identifier of the drug delivery device.
[0196] [Aspect 21] A drug delivery device described in any one of aspects 17 to 20, wherein the controller is further configured to wirelessly transmit advertising packets to advertise the presence of the drug delivery device for connection.
[0197] [Aspect 22] The drug delivery device of aspect 21, wherein the controller is further configured to encrypt advertising packets.
[0198] [Aspect 23] A drug delivery device described in any one of aspects 17 to 22, wherein connecting to a remote computing device to wirelessly communicate with the remote computing device via an unencrypted wireless communication channel includes connecting to the remote computing device using an unencrypted Bluetooth communication channel.
[0199] [Aspect 24] A computerized method executed by a controller of a medication delivery device, the controller communicating with a wireless communication module, the method including: generating infusion event information of the medication delivery device; connecting to a remote computing device using the wireless communication module to wirelessly communicate with the remote computing device over an unencrypted wireless communication channel; and transmitting encrypted data to the remote computing device over the unencrypted wireless communication channel using the wireless communication module, the encrypted data including data indicative of the infusion event information.
[0200] [Aspect 25] The computerized method of aspect 24, wherein transmitting the encrypted data further comprises transmitting an unencrypted identifier of the medication delivery device.
[0201] [Aspect 26] The computerized method of aspect 24 or 25, further comprising wirelessly transmitting an advertising packet to advertise the presence of the medication delivery device for connection.
[0202] [Aspect 27] The computerized method of aspect 26, further comprising encrypting the advertising packets.
[0203] [Aspect 28] A computerized method described in any one of aspects 24 to 27, wherein connecting to a remote computing device to wirelessly communicate with the remote computing device over an unencrypted wireless communication channel includes connecting to the remote computing device using an unencrypted Bluetooth communication channel.
[0204] [Aspect 29] A computing device having at least one processor in communication with a memory configured to store machine-readable instructions, the machine-readable instructions causing the at least one processor to connect to a wireless communication module of a medication delivery device for wirelessly communicating with the medication delivery device over an unencrypted wireless communication channel, the medication delivery device having (a) a housing having a reservoir of a size sufficient to hold a medication, (b) a dose button rotatable relative to the housing for selecting a dose size of the medication for injection, and (c) a controller in communication with the wireless communication module, and receiving encrypted data from the medication delivery device using the wireless communication channel over the unencrypted wireless communication channel, the encrypted data including injection event information generated by the medication delivery device.
[0205] [Aspect 30] The computerized method of aspect 29, further comprising decrypting encryption data from a two-dimensional barcode on the drug delivery device, the encryption data being usable to decrypt the encrypted data.
[0206] [Aspect 31] The computerized method of aspect 30, wherein the cryptographic data includes a private cryptographic key.
[0207] [Aspect 32] The computerized method of any one of aspects 29 to 31, wherein receiving the encrypted data further includes receiving an unencrypted identifier of the medication delivery device.
[0208] [Aspect 33] The computerized method of any one of aspects 29 to 32, further comprising wirelessly receiving an advertising packet for advertising the presence of the drug delivery device for connection.
[0209] [Aspect 34] The computerized method of aspect 33, wherein the advertising packet is encrypted, the method further comprising decrypting the advertising packet.
[0210] [Aspect 35] A computerized method described in any one of aspects 29 to 34, wherein connecting to the drug delivery device to wirelessly communicate with the drug delivery device via an unencrypted wireless communication channel includes connecting to the drug delivery device using an unencrypted Bluetooth communication channel.
[0211] [Aspect 36] A drug delivery device described in any of aspects 1 to 35, containing a drug.< / n>
Claims
1. 1. A drug delivery device comprising: a housing having a reservoir large enough to hold the medicament; a dose button rotatable relative to the housing for selecting a dose size of the medication for injection; A printed circuit board; a switch mounted on the printed circuit board; A controller in communication with the switch, the controller comprising: receiving a set of electrical signals from the switch; generating a first count of the set of electrical signals using a first counting technique based on the set of electrical signals, the first counting technique including counting a number of rising edges; generating a second count of the set of electrical signals based on the set of electrical signals using a second counting technique, the second counting technique including counting a number of rising edges and a number of falling edges; and determining data indicative of reliability of the first count, the second count, or both based on the first count and the second count.
2. The medication delivery device of claim 1 , wherein the controller comprises a counter block configured to analyze the set of electrical signals using the first counting technique to generate the first count.
3. The medication delivery device of claim 2 , wherein the counter block is configured to generate the first count by counting a number of signals in the set of electrical signals.
4. each signal in the set of electrical signals includes an associated square wave, each associated square wave including a rising edge at a beginning of the square wave; 4. The medication delivery device of claim 3, wherein the counter block is configured to sample the set of electrical signals at a sampling rate configured to capture each rising edge of each square wave.
5. 5. The medication delivery device of claim 1, wherein the controller includes a quadrature encoder configured to analyze the set of electrical signals using the second counting technique to generate the second count.
6. each signal in the set of electrical signals includes an associated square wave, each square wave including a rising edge at a beginning of the square wave and a falling edge at an end of the square wave; 6. The medication delivery device of claim 5, wherein the quadrature encoder is configured to sample the set of electrical signals at a sampling rate configured to capture each rising edge and each falling edge of each square wave.
7. the switch comprises a contact surface arm extending from the printed circuit board, the contact surface arm configured to move to close or open the switch; A drug delivery device according to any one of claims 1 to 6, further comprising a rotatable element which is rotatable relative to the printed circuit board, the rotatable element having a series of protrusions spaced apart from one another, the rotatable element being positioned such that rotation of the rotatable element allows the protrusions to slide relative to the contact surface arm to move the switch to one of a closed or open state.
8. The medication delivery device of any one of claims 1 to 6, wherein the switch comprises a piezoelectric sensor, a magnetic sensor, an accelerometer, an optical sensor, a circuit breaker sensor, an optical encoder, or some combination thereof.
9. The medication delivery device of claim 8 , wherein the magnetic sensor is a Hall effect sensor.
10. The medication delivery device of claim 8 , wherein the optical sensor is a reflective sensor.
11. 1. A computerized method executed by a controller of a medication delivery device, comprising: The drug delivery device comprises: a housing having a reservoir large enough to hold the medicament; a dose button rotatable relative to the housing for selecting a dose size of the medication for injection; A printed circuit board; a switch mounted on the printed circuit board; a controller in communication with the switch; The controller communicates with switches mounted on a printed circuit board, and the method comprises: receiving a set of electrical signals from the switch; generating a first count of the set of electrical signals based on the set of electrical signals using a first counting technique, the first counting technique including counting a number of rising edges in the set of electrical signals; generating a second count of the set of electrical signals based on the set of electrical signals using a second counting technique, the second counting technique including counting a number of rising edges and a number of falling edges in the set of electrical signals; determining data indicative of a reliability of the first count, the second count, or both based on the first count and the second count.
12. 12. The computerized method of claim 11, further comprising: using a counter block of the controller to analyze the set of electrical signals using the first counting technique to generate the first count.
13. 13. The computerized method of claim 12, further comprising generating the first count by counting, by the counter block, a number of signals in the set of electrical signals.
14. each signal in the set of electrical signals includes an associated square wave, each associated square wave including a rising edge at a beginning of the square wave; The method comprises:
14. The computerized method of claim 13, further comprising sampling, by the counter block, the set of electrical signals at a sampling rate configured to capture each rising edge of each square wave.
15. 15. The computerized method of claim 11, further comprising: using a quadrature encoder of the controller, analyzing the set of electrical signals using the second counting technique to generate the second count.
16. each signal in the set of electrical signals includes an associated square wave, each square wave including a rising edge at a beginning of the square wave and a falling edge at an end of the square wave; The method comprises:
16. The computerized method of claim 15, further comprising sampling, by the quadrature encoder, the set of electrical signals at a sampling rate configured to capture each rising edge and each falling edge of each square wave.
Citation Information
Patent Citations
Drug delivery device with dose capture module
JP2016506845A
Monitoring system and method
JP2017524427A
SYSTEM AND METHOD FOR SECURE INTERNET OF THINGS (IoT) DEVICE PROVISIONING
JP2019502206A
Dosage measurement system in a pen button
US20190022328A1
Dose detection and drug identification for a medication delivery device
WO2018160425A1
