Patent Grant
11878151
This disclosure relates to medicine administering and tracking systems, devices, and processes.
Diabetes mellitus, also referred to as diabetes, is a metabolic disease associated with high blood sugar due to insufficient production or use of insulin by the body. Diabetes is widely spread globally, affecting hundreds of millions of people, and is among the leading causes of death globally. Diabetes has been categorized into three categories or types: type 1, type 2, and gestational diabetes. Type 1 diabetes is associated with the body's failure to produce sufficient levels of insulin for cells to uptake glucose. Type 2 diabetes is associated with insulin resistance, in which cells fail to use insulin properly. The third type of diabetes is commonly referred to as gestational diabetes, which can occur during pregnancy when a pregnant woman develops a high blood glucose level. Gestational diabetes can develop into type 2 diabetes, but often resolves after the pregnancy.
Systems, devices, and techniques are disclosed for administering and tracking medicine to patients and providing health management capabilities for patients and caregivers.
In some aspects, an intelligent medicine administering system includes a medicine injection device having a multi-channel, mechanical encoder that detects fault conditions (e.g., such as open or short circuits) and a patient user's companion device including a software application operable to implement algorithms for detecting faults and communication loss and alerting the patient user for safety and fail-safes of the medicine injection device.
In some aspects, a system for administering insulin to a patient includes an injection pen device, the injection pen device structured to contain a medicine cartridge and include a dose setting mechanism to set a dose of insulin stored in the medicine cartridge to be dispensed by the injection pen device, a dispensing mechanism to dispense the insulin according to the set dose, a sensor unit to detect a dispensed dose, an electronics unit including a processor, a memory, and a wireless transmitter, the electronics unit configured to process the detected dispensed dose with time data associated with a dispensing event to generate dose data, and to wirelessly transmit the dose data, and a multi-channel encoder, in communication with the electronics unit and one or both of the dose setting mechanism and the dispensing mechanism, to monitor a dose setting operation or a dose dispensing operation; and the injection pen device in wireless communication with a mobile communication device that includes a data processing unit including a processor and memory to receive and process the dose data, wherein one or both of the electronics unit of the injection pen device or the data processing unit of the mobile communication device are configured to determine a fault in an operation of the injection pen device indicative of an error based on a quality of signal from the multi-channel encoder, wherein the fault is determined based on a signal quality analysis of at least one of electrical noise, signal frequency error, phase error, or duty cycle error.
In some aspects, a multi-channel encoder for an insulin injection device includes a first component including a substrate and a pattern of electrically conductive segmented contact pads in a first region of the substrate, and a plurality of channel pads disposed on the substrate in a second region, the plurality of channel pads including an electrical ground pad and at least three input channel pads; and a second component including an electrically conductive sweeping contact that electrically interfaces with individual segmented contact pads of the first component, one at a time, during the sweep of the pattern, wherein the second component is configured to rotate about a shared axis with the first component, or vice versa, such that the sweeping contact sweeps along the pattern of segmented contact pads during rotation wherein the multi-channel encoder is in communication with a processing unit of the insulin injection device.
Various diseases and medical conditions, such as diabetes, require a patient to self-administer doses of a fluid medication. Typically, when administering a fluid medication, the appropriate dose amount is set and dispensed by the patient using a syringe, a pen, or a pump. For example, self-administered medicaments or medicine include insulin used to treat diabetes, Follistim® used to treat infertility, or other injectable medicines such as Humira®, Enbrel®, Lovenox® and Ovidrel®, or others.
A medicament pen is a device that can be used to inject a quantity of a medicine (e.g., single or multiple boluses or doses of the medicine) into a user's body, where more than one dose can be stored in a medicine cartridge contained in the pen device. Pens offer the benefit of simplicity over other methods of delivery, such as syringe or pump-based methods. For example, syringes typically require more steps to deliver a dose, and pumps typically are more complicated to use and require a constant tether to the patient. However, previously there has not been an automated way to track and communicate the doses given with the pen in a simple, effective and reliable manner. In addition, it can be difficult to know how much to dose with the pen, when to dose, or if the patient dosed at all.
As with the dosing of any medication, it is sometimes hard for a patient to remember if a dose has been given. For this reason, for example, pill reminders have been developed where the patient places the medication for the day in a cup labeled with that day. Once they take their medication, there is no question it has been taken because the pills are no longer in the cup. Yet, there are no widely acceptable solutions that address this problem for injection-based therapies. Therefore, without simple, effective and reliable ways of tracking medicine doses, particularly for managing lifelong or chronic conditions like diabetes, patients may easily miss a dose or administer an incorrect dose (e.g., under-dose or over-dose) of their medicine which may result in serious, dangerous consequences to their health.
In addition to the challenges of tracking doses, calculating the right dose at the right time or under the right conditions is a widespread problem for patients of chronic conditions requiring daily dosing of medicine. Conventional dose calculators for administering insulin for Type I and Type II diabetes typically require manual estimation of carbohydrates (“carbs”) at mealtime. For some users, carb counting and estimating may be too difficult, and some users may not utilize the dose calculator due to the manual work and number of steps required to do so, e.g., taking out one's smartphone, opening up an app, manually typing calculator inputs, etc.
Systems, devices, and techniques are disclosed for administering and tracking medicine to patients and providing health management capabilities for patients and caregivers, which include a medicine injection device having a multi-channel, mechanical encoder that detects fault conditions (e.g., such as open or short circuits) and a patient user's companion device including a software application operable to implement algorithms for detecting faults and communication loss and alerting the patient user for safety and fail-safes of the medicine injection device.
In some embodiments in accordance with the present technology, an intelligent medicine administering system provides medicine dose recommendation and management capabilities for Type I and Type II diabetes patients and their caregivers. In some aspects, the system includes a medicine injection device (e.g., insulin pen, also referred to as a “pen” or “pen device”), in wireless communication with a patient's companion device (e.g., smartphone). The companion device includes a software application (“app”) having a dose calculator and decision support modules to calculate and recommend the dose of a medicine (e.g., insulin) the patient should administer using the wirelessly connected medicine injection device, as well as to provide control over several functionalities of the injection device, e.g., such as monitoring and recording dose sizes dialed on the injection device.
Communication between the pen device and the companion device provides the ability for dose tracking, logging, calculating, recommending, and/or communicating dose data with a user (e.g., patient user, health care provider (HCP) and/or caregiver), and other advantages of the intelligent medicine administering system. For example, each bolus that is dispensed by the pen device can be automatically logged and communicated to the companion device.
The companion device 5 can be used to obtain, process and/or display contextual data that can be used to relate to the patient user's health condition, including the condition for which the pen device 10 is used to treat. In an illustrative example, the companion device 5 is operable to track the patient user's location; the patient user's physical activity including step count, movement distance and/or intensity, estimated calories burned, and/or activity duration; and/or the patient user's interaction pattern with the companion device 5. The app associated with the system 100 can aggregate and process the contextual data to generate decision support outputs to guide and aid the patient user in using the pen device 10 and/or managing their behavior to promote better health outcomes in treating his/her health condition.
In some embodiments, the system 100 includes a sensor device 50 to monitor one or more health metrics of the patient user. Examples of health metric data monitored by the sensor device 50 include analytes, such as glucose, heart rate, blood pressure, user movement, or other. In some implementations, the sensor device 50 is a wearable sensor device such as a continuous glucose monitor (CGM) to obtain transcutaneous or blood glucose measurements that are processed to produce continuous glucose values. For example, the continuous glucose monitor can include a glucose processing module implemented on a stand-alone display device and/or implemented on the companion device 5, which processes, stores and displays the continuous glucose values for the patient user.
The pen device 10 is configured in communication with the patient user's mobile computing and communication device 5, e.g., such as the user's smartphone, tablet, and/or wearable computing device, such as a smartwatch, smartglasses, etc. and/or a user's laptop and/or desktop computer, a smart television, or network-based server computer.
In some implementations of the system 100, for example, to use the pen device 10, the user first dials up a dose using a dose knob. The dose knob of the pen device 10 can be included as part of the dose setting mechanism and/or the dose dispensing mechanism. For example, the dose may be adjusted up or down prior to administration of the dose. When the user applies a force against a dose dispensing button (e.g., presses against the dose dispensing button that is caused to protrude outward from the pen's body upon dialing the dose using the dose knob), a pushing component (e.g., also referred to as a ‘plunger’) of the dose dispensing mechanism is depressed against an abutment of the medicine cartridge loaded in the pen device 10 to cause the pen device 10 to begin to dispense the medicine, in which the quantity dispensed is in accordance with that set by the dose setting mechanism. In such implementations, the operations monitoring mechanism of the pen device 10 will begin to sense movement of a rotating component or shaft that drives the plunger, for example, in which the movement is sensed through an encoder. In some examples, the encoder can be configured to sense the rotation of a component that is coupled to the drive shaft, and as the drive shaft rotates the plunger moves linearly; and therefore by sensing rotation of the component, the movement of the drive shaft and the plunger is sensed. Movement of the encoder may be detected as data processed by a processor of the electronics unit of the pen device 10, which can be used to measure the dose. In some implementations, the processor can then store the size of the dose along with a time stamp for that dose. In some implementations, the pen device 10 can then transmit the dose and related information to the companion device 5. In such implementations when the dose is transmitted, the data associated with the particular transmitted dose is marked in the memory of the pen device 10 as transmitted. In such implementations if the dose was not yet transmitted to the companion device 5, then the data associated with the dose will be transmitted at the next time a successful communication link between the pen device 10 and the companion device 5 is established.
The operations monitoring mechanism of the pen device 10 can include a sensor that can utilize any method of sensing rotary or linear movement. Non-limiting examples of such sensors include rotary and linear encoders, Hall effect and other magnetic based sensors, linearly variable displacement transducers, or any other appropriate method of sensing known in the art.
The dose dispensing mechanism of the pen device 10 can include a manually powered mechanism or a motorized mechanism. In either case, a force (e.g., either produced by the patient or by an electrically-powered motor) pushes on the plunger of the dose dispensing mechanism to in turn force a receiving plunger of the medicament vial or cartridge to deliver the specific amount of the medicament. In some implementations, for example, the dose dispensing mechanism can be adjusted to deliver the dose over a different period of time. In one example, the dose dispensing mechanism can be operated such that the plunger is pushed in by an adjustable tension spring or change the speed of the motor to inject the dose over a time frame (e.g., 1 s, 5 s or other) to aid in reducing the pain of dosing. In one example, the dose dispensing mechanism can be operated over a much longer period of time, e.g., to better match the dynamics of carbohydrates, which can be like an extended bolus with a pump.
The software application (app) of the companion device 5 associated with the pen device 10 provides a user interface to allow the user to manage his/her health related data. In some implementations, for example, the companion device 5 can be configured to control some functionalities of the pen device 10. In some implementations, for example, the companion device 5 includes the user's existing smartphone, tablet, or wearable computing device. In some implementations, for example, the companion device 5 is an independent portable device that the user may carry on his/her person. In one example embodiments of an independent portable companion device 5, the companion device 5 includes a data processing unit, wireless communication unit to allow the device to communicate with the pen device 10, and a display unit.
In various operations of the intelligent medicine administering system 100, for example, when a dosing event (e.g., an amount of fluid is dispensed from the pen device 10), a time stamp associated with the dispensing is referenced is recorded by the processing unit of the pen device 10 (e.g., stored in the memory of the pen device 10). For example, the time stamp may be the current time or a time where a count-up timer is used. When the dose information is eventually transmitted to the companion device 5, the time stamp and/or a ‘time-since-dose’ parameter is transmitted by the pen device 10 and received by the companion device 5 and stored in the memory of the data processing unit of the companion device 5. In some implementations, for example, the time of the dose can be determined without the pen having to know the current time. This can simplify operation and setup of the pen device 10. In some implementations, for example, a user time is initialized on the pen device 10 from the companion device 5, in which the user time is used for dose time tracking. Using the system 100, the companion device 5 can know the time of the dose relative to the current time.
Once the companion device 5 receives the dose related information (e.g., which can include the time information and dose setting and/or dispensing information, and other information about the pen device 10 related to the dosing event), the companion device 5 stores the dose related information in memory, e.g., which can include among a list of doses or dosing events. For example, via the software application's user interface, the companion device 5 allows the patient to browse a list of previous doses, to view an estimate of current medicament active in the patient's body (“medicament on board”) based on calculations performed by a medicine calculation module of the software application, and/or to utilize a dose calculation module of the software application to assist the patient regarding dose setting information on the size of the next dose to be delivered. For example, the patient could enter carbohydrates to be eaten, current blood sugar, and the companion device 5 would already know insulin on board. Using these parameters a suggested medicine dose (e.g., such as insulin dose), calculated by the dose calculation module, may be determined. In some implementations, for example, the companion device 5 can also allow the patient to manually enter boluses into the pen device 10 or another medicine delivery device. This would be useful if the patient was forced to use a syringe, or if the battery in the pen device 10 was depleted.
Example embodiments and implementations of the disclosed intelligent medicine administering system, including a medicine injection device (e.g., pen device) in communication with a companion device, are described herein. Some examples of features of an intelligent medicine administering system that can be used with the example devices, systems, and methods for monitoring dose settings and dispensing operations are described in U.S. Pat. No. 9,672,328 B2, entitled “Medicine Administering System Including Injection Pen and Companion Device,” the entire content of which is incorporated by reference in this disclosure.
While the disclosed embodiments described herein are primarily based on diabetes management systems and methods involving insulin pen and glucose monitoring devices to facilitate understanding of the underlying concepts, it is understood that the disclosed embodiments can also include treatment of other health conditions using other medications by the pen device and/or monitoring of other analytes by sensor devices.
Robust Dose Measurement and Tracking Device for Medicine Dispensing Device
In a drug delivery device, such as a smart insulin pen, the amount of drug delivered may be measured by quantifying mechanism rotation with a rotary encoder.
A conventional two-channel quadrature encoder has two channels with only four possible states, all of which are valid, i.e., [00], [10], [01], and [11], and which occur in order as the encoder rotates and in the reverse order when the encoder rotated in the opposite direction. These signals are generated as electrical contacts sweep across a conductive pattern with alternating segments of conductive and non-conductive areas. In principle, when a contact touches a conductive area, it outputs a “1”, and when it disconnects and is in a nonconductive area it outputs a “0”. However, a short circuit caused by damage or liquid ingress will appear as [11] and an open circuit caused by damage or contamination will appear as [00]. However, since these are valid normal states, no error would be detected by this conventional two-channel encoder. Instead, for example, it would just appear that the encoder was not moving. Where an encoder is placed to detect medicine dose size (such as in a smart insulin pen), this would incorrectly indicate that no dose was taken.
In various uses of conventional encoders, typically the encoder pattern is connected to electrical ground and the inputs are pulled high via a pull-up resistor; but, in any of the examples the polarity could be reversed or voltage levels changed. All that is required is that there is a voltage differential between the pattern and the input contacts, so that connection with the pattern can be detected. The assignment of 0 or 1 to connected/disconnected or high/low voltage can also be arbitrarily defined for each application.
These and other limitations of conventional encoders for use in accuracy-critical devices, like medicine dispensing devices, create dangerous risks to the end users of such devices. Therefore, medicine dispensing device would greatly benefit from newer designs and data processing schemes to ensure valid states of an encoder are indicative of the performance accuracy of the medicine dispensing device.
Example embodiments of a multi-channel, mechanical encoder for a medicine dispensing device (such as pen device 10) are described for detecting fault conditions (e.g., such as open or short circuits) and improving the accuracy of dose setting and dispensing tracking capabilities of the medicine dispensing device. Furthermore, example embodiments of methods which can be implemented using a software application on the medicine injection device and/or a corresponding companion device are described for detecting fault conditions of encoders and the loss of communications to and/or alerting of the patient user in events of damage or other causes that affect signal quality of a mechanical encoder and lead to erroneous results.
In various implementations, the software architecture 150 processes the data from the pen device 10, associated with the detected and/or pre-processed output signals of an encoder configured on the pen device 10. In some embodiments, one of the data processing modules of the software architecture 150 includes an encoder output processing module 152 to receive and process the output signals received by the encoder. The encoder output processing module 152 is able to monitor the ‘health’ of the pen device 10 to detect false positives or missed negatives associated with the output of the encoder, which monitors operations of the dose setting and/or dispensing mechanisms of the pen device. For example, conventional encoders are susceptible to nondetection of liquid ingress in the pen, e.g., due to indication of valid state [11], and nondetection of damage of the pen, e.g., due to a detection of valid state [00]. The encoder output processing module 152 is capable of interrogating the output signals of the encoder, e.g., including that of conventional encoders, in a manner that can distinguish additional information in the output signals and identify such detrimental conditions of the pen device, like liquid ingress or mechanical or electrical damage. Additionally, the encoder output processing module 152 is configured to detect and alert the patient user of faults in pen device, and/or to determine loss of communications and alerting the patient user accordingly. Fault conditions of the pen device can include a mechanically damaged/disconnected electrical contact or connection of the encoder, excessive contact wear and/or mechanism wear affecting proper alignment of components of the encoder, liquid intrusion (e.g., of water, insulin, or other conductive liquid) into the encoder, and/or corrosion, particulate or foreign material contamination of the encoder.
The software architecture 150 may also be configured to process health metric data and contextual data obtained by the app on the companion device 5, from the pen device 10, from the sensor device 50, and/or from other devices of the patient user and/or apps on the companion device 5. In some embodiments, for example, the software architecture 150 includes a data aggregator module 154 to obtain the health metric data from a device, such as the pen device 10, sensor device 50, and/or other devices or apps in communication with the companion device 5. The software architecture 150 includes or is in communication with a database 156 to store the health data and contextual data associated with the patient user and populations of patient users In some embodiments, the software architecture 150 includes a dose determination module 158, such as a dose calculator module, to autonomously calculate a dose of the medicine associated with dose injections from the pen device 10 based on time-relevant and context or circumstances-relevant data specific to the patient user of the pen device 10. The example modules shown in the software architecture diagram can be organized to provide data to one another in various ways, including directly (e.g., module-to-module) and/or indirectly (e.g., via an intermediary module), based on a periodic, an intermittent, and/or a per-request basis.
Quantification of Signal Quality from Encoder Output
A well-functioning encoder should have distinct rising and falling edges in its signal, and for example, with minimal bounce, no erratic spikes or high-frequency transitions, and edges in the proper sequence for the direction of encoder rotation.
In some implementations of an intelligent medicine administering system 100 including the example encoder output processing module 152, the system 100 includes a quantitative encoder signal analysis algorithm to detect and quantify the signal quality of an encoder in a dispensing device, such as a medicament pen device, e.g., identifying if there is a poor signal quality of the encoder. In some embodiments, the quantitative encoder signal analysis algorithm can be resident in the encoder output processing module 152 of the app, as illustrated in the example of
In various embodiments, the quantitative encoder signal analysis algorithm includes a process to detect the rising portions (e.g., signal portion that trends upward from “0” to “1” or points therebetween) and falling portions (e.g. signal portion that trends downward from “1” to “0” or points therebetween). The algorithm includes a process to quantitatively analyze the rising and falling portions. In some embodiments of the quantitative encoder signal analysis algorithm, the quantitative analytical process examining one or more of the frequency, phase, duty cycle and/or resistance of the signal to quantify and characterize noise in the mechanical encoder, which is used to affect (e.g., detect or correct potential problems in) the performance of the encoder and validate results by the encoder. The output of the algorithm can include a binary result (e.g., valid or invalid), or other output characterizing the signal.
Implementations of the quantitative encoder signal analysis algorithm are beneficial to an encoder used on devices like a medicament delivery pen due to the design and configuration of the dose setting and/or dispensing mechanisms of such pen devices. For example, other encoders, like on a volume knob of a stereo, might very well be turned erratically in both directions at varying speed. However, this is a highly unlikely, if not impossible, scenario for medicament dispensing devices because such devices have certain mechanical constraints. These constraints provide can be accounted for in the quantitative encoder signal analysis algorithm to allow the detections of detrimental conditions of the pen that conventional encoders may fail to identify. As an example, in pen devices, any movement is typically a single continuous rotation in a single direction. The quantitative encoder signal analysis algorithm thereby can account for this operation in at least some of the detection modes described below.
Frequency analysis: The algorithm can be used to analyze frequency of the encoder signal. For example, the algorithm can identify noise in the encoder, which, given the physical constraints of the encoder's maximum speed, the electrical signal output of the encoder that exceeds the maximum speed is indicative of erratic noise.
Phase analysis: The algorithm can be used to analyze phase of the encoder signal. For example, the algorithm can identify noise in the encoder, in which, for a given direction of rotation, there is a single correct sequence of encoder edges. If edges are observed out of the usual order, it indicates a problem.
Duty cycle: The percent of the time an encoder switch is connected is called the duty cycle. At a constant rotational speed, the duty cycle for a particular encoder is fixed by the conductive pattern strip spacing. In some applications, the duty cycle should be 50%, indicating that the contact is connected for as much time as it is disconnected. If the contact wears, creating a wider contact patch, that will increase the duty cycle. If the pattern gets contaminated at the edges, covering part of the pattern, that may decrease the duty cycle. The algorithm can be used to analyze duty cycle of the encoder signal to identify noise associated with a fault in the encoder. In an example of a pen device, a manual pen will not rotate at exactly a fixed speed, but by averaging the duty cycle observed over several cycles of the encoder, e.g., possibly over several doses over time, the actual duty cycle can be roughly calculated. If it exceeds a preset threshold, or preset amount of drift from the initial value, the algorithm produces an output indicative of a problem with the encoder based on the duty cycle of the signal. For example, the threshold can be a value or range based on empirical or precomputed data values.
Resistance: The algorithm can be used to analyze resistance of the encoder signal to identify noise in the encoder. An analog voltage measurement of the input lines can give a rough measure of resistance in the encoder circuit. Resistance should either be very low when connected, or very high when disconnected. If an abnormal resistance between the normal values is observed, e.g., determined by an instability of an output signal of an encoder channel, this can be indicative of dirty or corroded contacts, contamination, or ingress of a conductive liquid such as water or insulin.
Example Embodiments of Multi-Channel Pattern Encoders
Three-Channel Pattern Encoder Embodiments
As shown in the diagram of
Multi-Channel Sequential Pattern Encoder Embodiments for Intrinsic Fault Detection
In another example embodiment of a multi-channel encoder in accordance with the present technology, e.g., the encoder includes a three (or more) channel encoder that can traverse a pattern in such a way that there is always at least one contact disconnected, and always at least one contact connected. An example sequence for clockwise rotation may be: [001], [011], [010], [110], [100], [101], [001], etc. In this way, the states [000] and [111] are invalid, indicating an open circuit (e.g., connection fault) or a short circuit (e.g., liquid ingress). As such, the example multi-channel pattern encoder is capable of detecting intrinsic faults in the interfaced device, e.g., such as the pen device 10.
Multi-Channel Sequential Pattern Encoder Embodiments for Explicit Fault Detection
In some implementations of an intelligent medicine administering system 100 including the example multi-channel pattern encoder 200 or other example embodiments of a multi-channel encoder in accordance with the present technology, the system is configured to provide explicit fault detection capabilities based on operations of the encoder, e.g., for liquid detection and ground sensing.
Liquid detection: The system 100 can detect explicit faults in a medicament delivery device based on the presence of liquid in the device. For example, the encoder of the pen device, such as the encoder 200 of the pen device 210, can be configured such that, with an encoder pattern connected to ground and the two active contacts pulled high (e.g., connected to a 1.5 volt source through 500 k-ohm resistors), the third input line is pulled high. As such, the third line could be exposed near the active contacts but not directly contacting any other components, such that any conductive liquid (such as tap water or insulin) entering the encoder would bridge the liquid detection contact and the pattern wheel. This would then be detected as a voltage drop of the liquid detection input, and indicative of a fault with the pen device 210.
Ground sensing: For conventional mechanical encoders, typically a rotary encoder pattern consists of a solid inner conductive ring used for connection to ground, and segmented conductive areas around the ring, used for rotational measurement. A sweeping electrical contact contacts the solid ring to hold the pattern at ground, while active contacts trace across the conductive segments. By adding another contact on the solid ring, set as an input, this contact can be used to constantly detect the ground connection. This input should always detect ground, and if it does not then that indicates damage, contamination, corrosion, or some other connection problem.
In some embodiments of the multi-channel encoder, the encoder includes a ground sensing contact that is operable as an input with respect to the encoder. Yet, during an active dose setting and/or dispensing event in which the encoder is operated, for example, while edge transitions are being detected by the active channels, the ground sensing contact channel may be set as a ground output. In this way, the ground ring will have redundant ground connections, helping ensure clean signal quality. Then when the dose is complete, the contact can be set to an input again to monitor proper ground connection.
Multi-Channel Sequential Pattern Encoder Embodiments for Intrinsic Detection with Quadrature Encoder
In some implementations of the intelligent medicine administering system 100 including the example including the example encoder output processing module 152, the system is configured to provide intrinsic fault detection capabilities based on data processing the outputs of an encoder, e.g., including the disclosed multi-channel pattern encoders and a conventional quadrature encoder.
Pattern Resistance: The quadrature encoder includes a solid conductive ring that forms the encoder pattern when the ring is a material with a moderate resistivity, or the encoder includes a fixed resistor between the ground connection ring and the segmented pattern. For example, with a moderate resistivity, or the fixed resistor configuration, any time an input line contacts the pattern, it should read a specific resistance (or voltage level) indicating that current is flowing only through the pattern. If the resistance is lower than expected, then that indicates a contaminate such as water also carrying some current, lowering the overall resistance in the circuit.
Resistance in Pattern Gaps: For conventional encoders, typically there is a dielectric (such as plastic or soldermask) between the conductive segments of the encoder pattern. Instead, if this material is slightly conductive (with high resistance) and in contact with ground, or if it is conductive (with low internal resistance) and connected to ground via a large value resistor, then it can help detect damage. Whereas a conventional quadrature encoder would either be completely connected or completely disconnected, the example embodiments of the encoder 200 can include material with a moderate resistivity and/or a fixed resistor coupled between the inner conductive ground ring and the segmented pattern to provide inputs that should never be completely disconnected from ground. They should only alternate between sections of high and low resistance. In this way, if they are ever completely disconnected, this indicates damage to the encoder, circuitry or other components of the device, e.g., pen device 10.
In some implementations of these example embodiments of the encoder 200, the encoder can be read (e.g., by the electronics unit) by continually monitoring analog voltage of the inputs and evaluating it as it rises and falls.
Yet, in some implementations of these example embodiments of the encoder 200, a simpler and faster method than continuous analog measurement (e.g., continually monitoring analog voltage of the inputs) is to only measure analog voltage when the encoder is at rest. For example, once motion is detected, the input can be switched to a digital mode. If the pattern resistance is sufficiently low and the gap resistance is sufficiently high, a digital input can still correctly interpret the encoder signal. Then when it returns to rest, the analog voltage can again be sampled to ensure proper connections.
Example Embodiments and Implementations of Fault Direction Using an Encoder with a Single Trace Contact and a Multi-Channel Active Pattern
For example, some encoders have multiple input contacts that sweep across conductive stripes on a grounded pattern. One requirement of this approach is that the alignment between contacts is critical to ensure proper pattern sequencing. In some instances, the contacts may be spring-loaded and flexible, which can create challenges in ensuring the required alignment between contacts, especially for high resolution encoders.
As shown in
Additional advantages of such embodiments of the encoder include, for example, opportunities for saving energy by de-powering unnecessary channels and preventing quiescent current draw through them.
Nominally this example encoder 600 produces the pattern [100] [110] [010] [011] etc. However, contacting two channels at once may only be instantaneous as the contact transitions from one pad to the next, so in practice it would be useful to simply monitor for the triggering of the next expected channel and disregard when the previous channel is disconnected, since those will both happen nearly instantaneously.
For example, from initial state [100] the state [110] indicates that channel B has now been connected, but the next state [010] when channel A (first active region) disconnects is not considered significant, as it will happen almost immediately anyway. In the state [100] the only important channel to monitor is B, and possibly C if the system needs to also detect reverse rotation. Once A has been contacted, it is no longer critical to monitor its value. Since A is no longer critical, it can be de-powered to save energy. Its state will be unknown to the system, but this doesn't matter. De-powering can be done instantaneously during rotation, or after a brief timeout period indicating that movement has stopped.
In various embodiments, the system can include a power management algorithm for the example single-trace multi-channel encoder to monitor the state changes, determine what channels are critical to have power supplied, regulate the power to those presently non-critical (e.g., depower non-critical) and those soon-to-be critical (e.g., power a presently depowered channel), and repeating this process continually or intermittently.
As shown in the top portion of the diagram labeled 810, in the initial position the encoder has previously detected contact with A so it is no longer useful to spend power monitoring that channel, so it is shown as de-powered with a ? state. Similarly, assuming we are not concerned with accurately measuring backward motion, there is no need to power channel C either, as it is known that B will be contacted first, so the state of C is irrelevant. Only channel B is powered, as the processor waits for contact indicating forward movement.
In the subsequent three positions, as shown in the middle portion of the diagram labeled 820, all of the channels are powered during the movement of the single trace so that the processor can measure the magnitude of the movement.
Finally, as shown in the bottom portion of the diagram labeled 830, after no changes in input are registered for some timeout period, the trace contact contacts channels B and C. Because C was the last channel detected, channels B and C are de-powered, preventing energy loss while they remain connected, and only channel A needs to be powered to detect the next forward movement. If a channel is powered while connected, it draws current and uses energy, draining power from the battery or other energy source. If a channel is powered but not connected, it uses a negligible amount of power, so it is energy efficient to power only channels that are disconnected.
Robust Communication
Insulin is a lifesaving drug for people with diabetes, but an overdose can be dangerous or even lethal. For this reason, it is critical for the system to keep an accurate record of all insulin taken by the patient. If the user is relying on the system (for example, an app display) to recommend doses or remind them that they have not yet taken a dose, any interruption in the performance of the device or its communication with the display could lead to the system missing actual doses taken. For instance, the user may have taken a dose, but if the system does not receive this as input or identify a fault condition, it could over-recommend the next dose and possibly lead to overdose. Other drugs, besides insulin, taken with a smart delivery system may have similar dangers if over-dosed.
To improve safety and guarantee the user that data is current and correct, it is helpful to have fail-safes for the following scenarios. For example, the example encoders detect fault conditions, as described above for the various embodiments, when: (i) the pen's sensor becomes disconnected or damaged; (ii) the pen's sensor is shorted due to damage or flooding with liquid; and/or (iii) the pen's sensor wears out and signal becomes unreliable. For example, the example fault conditions can be detected by the system due to transmission and reception faults, when: (i) the pen's electronics or software malfunction such that it stops transmitting; and/or there is a transmission issue between the pen and app, e.g., such as interference, poor reception, or the companion device 5 being in a non-communication mode (e.g., airplane mode on a smartphone).
To robustly identify transmission and reception fault conditions, the display (e.g., the app resident on the companion device 5) must ensure that the medicine dispensing device is operational, communication is functioning correctly, and data is up to date.
One example method for accomplishing this include the following. The pen device 10 may periodically (e.g., every 2 seconds) transmit a beacon indicating that its self-tests are successful, even if there is no new data to transmit. In this way, if the beacon is not received, regardless of the cause, the app can identify that there is a system fault and the potential for dose information to be incomplete.
Another example method to ensure the pen device 10 is operational, communicating correctly and up-to-date with data includes the following: the app may send a request to the pen device 10 to transmit status. The pen device 10 would then respond with its status, validating that the system is functioning. If a response is not received, then this indicates a system fault.
In some implementations, the beacon or response from the device may also incorporate encryption or a walking code to protect against malicious interference from an attacker, further ensuring that the user's own pen is connected.
In some implementations, the beacon from the device may be initiated by a user action such as a button press or dialing a dose. For example, the app may prompt the user to press a button on the pen to transmit its status and indicate that the system is functioning properly.
Example embodiments of a medicine delivery system are described which includes a device with a fault-identifying encoder, and an app that monitors for proper communication with the device and displays appropriate messages if communication is lost for any reason. With end-to-end fault detection, a patient user of the system can be sure that the displayed dosing information is accurate, and if there is a fault anywhere in the system that could lead to an actual dose being missed, it will be communicated.
In some embodiments in accordance with the present technology (example 1), a system for administering a medicine to a patient includes an injection pen device, the injection pen device structured to contain a medicine cartridge and include: a dose setting mechanism to set a dose of a medicine stored in the medicine cartridge to be dispensed by the injection pen device, a dispensing mechanism to dispense the medicine according to the set dose, a sensor unit to detect a dispensed dose, an electronics unit including a processor, a memory, and a wireless transmitter, the electronics unit configured to process the detected dispensed dose with time data associated with a dispensing event to generate dose data, and to wirelessly transmit the dose data, and a multi-channel encoder, in communication with the electronics unit and one or both of the dose setting mechanism and the dispensing mechanism, to monitor a dose setting operation and/or a dose dispensing operation; and the injection pen device is capable of being in wireless communication with a mobile communication device that includes a data processing unit including a processor and memory to receive and process the dose data, wherein one or both of the electronics unit of the injection pen device or the data processing unit of the mobile communication device are configured to determine a fault based on a detected error and/or a quality of signal from the multi-channel encoder.
Example 2 includes the system of example 1, wherein the multi-channel encoder includes: a first component including a substrate and a pattern of electrically conductive segmented contact pads in a first region of the substrate, and a plurality of channel pads disposed on the substrate in a second region, the plurality of channel pads including an electrical ground pad and at least three input channel pads, wherein the at least three input channel pads include a first channel and a second channel associated with measuring rotation of the dose setting mechanism and/or the dispensing mechanism, and a third channel associated with holding at least some of the pattern of segmented contact pads at electrical ground during a sweep of the pattern; and a second component including an electrically conductive sweeping contact that electrically interfaces with individual segmented contact pads of the first component, one at a time, during the sweep of the pattern, wherein the second component is configured to rotate about a shared axis with the first component, or vice versa, such that the sweeping contact sweeps along the pattern of segmented contact pads during rotation.
Example 3 includes the system of example 2, wherein the first component and the second component are configured as annular rings.
Example 4 includes the system of example 2, wherein the first component includes a printed circuit board, and the pattern of segmented contact pads and the plurality of channel pads include planar metallic contacts.
Example 5 includes the system of example 2, wherein the sweeping contact includes a spring-loaded arm that is coupled to a body of the second component.
Example 6 includes the system of example 2, wherein the first component further includes one or more base pads electrically coupled to the electrical ground pad.
Example 7 includes the system of example 6, wherein the multi-channel encoder further includes one or more spring connectors to interface between the second component and the one or more base pads, wherein the second component includes an interior track along a side of the second component that faces the first component such that second component slides along a contacting surface of the spring connectors in the interior track as the sweeping contact sweeps across the pattern of segmented contact pads during rotation.
Example 8 includes the system of example 2, wherein the third channel of the multi-channel encoder is operable to actively monitor ground for detection of damage to the injection pen device.
Example 9 includes the system of example 1, wherein the fault is determined based on signal quality analysis of one or more of electrical noise, signal frequency error, phase error, duty cycle error.
Example 10 includes the system of example 1, wherein the fault is determined based on monitoring of channel disconnection or channel short circuit associated with the multi-channel encoder.
Example 11 includes the system of example 1, wherein the determined fault is based on a contaminant or a water ingress in the injection pen device.
Example 12 includes the system of example 11, wherein the third line the contaminant or the water ingress in the multi-channel encoder bridges an active signal monitoring channel and a channel connected to ground to cause a detectable voltage drop indicative of the fault with the injection pen device.
Example 13 includes the system of example 1, wherein the injection pen device is operable to transmit a beacon to the companion device periodically indicative of normal function of the injection pen device, such that the data processing unit of the companion device is configured to (i) detect the fault when the beacon is not received within one or more of the beacon periods and (ii) produce an alert to be presented on the companion device indicative of the fault and/or (iii) disable a module associated with display or calculation of the medicine.
Example 14 includes the system of example 1, wherein at least one of the injection pen device or the mobile communication device includes a software application program product comprising a non-transitory computer-readable storage medium having instructions, which when executed by the processor, cause the device to process the output signal data from the recorder to detect a fault in one or both of the dose setting mechanism and the dispensing mechanism of the injection pen device, and to generate an alert associated with the detected fault.
Example 15 includes the system of example 14, wherein the instructions of the software application program product, which when executed by the processor, further cause the device to process communication data between the injection pen device and the mobile communications device to determine a loss of communications, and to generate an alert associated with the determined loss of communications.
Example 16 includes the system of example 1, wherein the mobile communication device is implemented on a smartphone, a tablet, a wearable computing device including a smartwatch or smartglasses, a computer including a laptop computer, or one or more computers networked in a communication network through the Internet.
In some embodiments in accordance with the present technology (example 17), multi-channel encoder for medicament injection device includes a first component including a substrate and a pattern of electrically conductive segmented contact pads in a first region of the substrate, and a plurality of channel pads disposed on the substrate in a second region, the plurality of channel pads including an electrical ground pad and at least three input channel pads, wherein the at least three input channel pads include a first channel and a second channel associated with measuring rotation of a dose setting and/or dispensing mechanism of the medicament injection pen, and a third channel associated with holding at least some of the pattern of segmented contact pads at electrical ground during a sweep of the pattern; and a second component including an electrically conductive sweeping contact that electrically interfaces with individual segmented contact pads of the first component, one at a time, during the sweep of the pattern, wherein the second component is configured to rotate about a shared axis with the first component, or vice versa, such that the sweeping contact sweeps along the pattern of segmented contact pads during rotation wherein the multi-channel encoder is in communication with a processing unit of the medicament injection pen.
Example 18 includes the multi-channel encoder of example 17, wherein the first component and the second component are configured as annular rings.
Example 19 includes the multi-channel encoder of example 17, wherein the first component includes a printed circuit board, and the pattern of segmented contact pads and the plurality of channel pads include planar metallic contacts.
Example 20 includes the multi-channel encoder of example 17, wherein the sweeping contact includes a spring-loaded arm that is coupled to a body of the second component.
Example 21 includes the multi-channel encoder of example 17, wherein the first component further includes one or more base pads electrically coupled to the electrical ground pad.
Example 22 includes the multi-channel encoder of example 21, wherein the multi-channel encoder further includes one or more spring connectors to interface between the second component and the one or more base pads, wherein the second component includes an interior track along a side of the second component that faces the first component such that second component slides along a contacting surface of the spring connectors in the interior track as the sweeping contact sweeps across the pattern of segmented contact pads during rotation.
Example 23 includes the multi-channel encoder of example 17, wherein the third channel of the multi-channel encoder is operable to actively monitor ground for detection of damage to the injection pen device.
In some embodiments in accordance with the present technology (example 24), a system for administering a medicine to a patient includes an injection pen device, wherein the injection pen device includes an electronics unit including a processor and a memory, and the injection pen device includes an encoder (e.g., rotary encoder) to monitor a dose setting operation and/or a dose dispensing operation, the encoder including a pattern of contact pads in which at least a portion of the contact pads include a resistive material, where the processor is configured to analyze an output signal of the encoder to determine a rotation of a dose setting and/or dose dispensing mechanism of the injection pen and/or to estimate an amount of a medicine (e.g., insulin) dispensed or pre-set for dispensing from the injection pen device. In some example embodiments, the system is configured to confirm that the output signal is within a threshold of an expected signal (e.g., voltage) based on an electrical resistance associated with the pattern of contact pads. In such example embodiments, the system is configured to determine a short circuit when an analyzed voltage output is above the threshold of the expected signal and identify a short circuit fault condition, and/or the system is configured to determine an open circuit when an analyzed voltage output is below the threshold of the expected signal and identify an open circuit fault condition, such that the identified fault conditions are indicative of one or more of a dirty or contaminated electrical contact or connection in the multi-channel encoder, a corroded or damaged electrical contact or connection within the multi-channel encoder, or an ingress of a liquid within the multi-channel encoder.
Implementations of the subject matter and the functional operations described in this disclosure can be implemented in various systems, digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Implementations of the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a tangible and non-transitory computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more of them. The term “data processing unit” or “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.
A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
It is intended that the specification, together with the drawings, be considered exemplary only, where exemplary means an example. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Additionally, the use of “or” is intended to include “and/or”, unless the context clearly indicates otherwise.
While this disclosure contains many specifics, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of this disclosure. Certain features that are described in this disclosure in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the embodiments described in this disclosure should not be understood as requiring such separation in all embodiments.
Only a few implementations and examples are described, and other implementations, enhancements, and variations can be made based on what is described and illustrated in this disclosure.
This application is a continuation of U.S. patent application Ser. No. 17/156,681, filed on Jan. 25, 2021, now U.S. Pat. No. 11,369,743, which is a continuation of U.S. patent application Ser. No. 16/407,046, filed on May 8, 2019, now U.S. Pat. No. 10,898,653, which claims the benefit of the filing date of provisional U.S. Patent Application No. 62/668,723, filed on May 8, 2018.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4498904 | Turner et al. | Feb 1985 | A |
| 4515584 | Abe et al. | May 1985 | A |
| 4950216 | Weder | Aug 1990 | A |
| 4973318 | Holm et al. | Nov 1990 | A |
| 4988660 | Campbell | Jan 1991 | A |
| 5279586 | Balkwill | Jan 1994 | A |
| 5626566 | Petersen et al. | May 1997 | A |
| 5681285 | Ford et al. | Oct 1997 | A |
| 5822715 | Worthington et al. | Oct 1998 | A |
| 5925021 | Castellano et al. | Jul 1999 | A |
| 5984900 | Mikkelsen | Nov 1999 | A |
| 6004297 | Steenfeldt-Jensen et al. | Dec 1999 | A |
| 6042571 | Hjertman et al. | Mar 2000 | A |
| 6235004 | Steenfeldt-Jensen et al. | May 2001 | B1 |
| 6302855 | Lav et al. | Oct 2001 | B1 |
| 6482185 | Hartmann | Nov 2002 | B1 |
| 6817986 | Slate et al. | Nov 2004 | B2 |
| 7591801 | Brauker et al. | Sep 2009 | B2 |
| 7905833 | Brister et al. | Mar 2011 | B2 |
| 7955303 | Burren et al. | Jun 2011 | B2 |
| 7976492 | Brauker et al. | Jul 2011 | B2 |
| 8221356 | Enggaard et al. | Jul 2012 | B2 |
| 8229535 | Mensinger et al. | Jul 2012 | B2 |
| 8231531 | Brister et al. | Jul 2012 | B2 |
| RE43834 | Steenfeldt-Jensen et al. | Nov 2012 | E |
| 8460231 | Brauker et al. | Jun 2013 | B2 |
| 8565848 | Brister et al. | Oct 2013 | B2 |
| D694252 | Helm | Nov 2013 | S |
| 8591455 | Mensinger et al. | Nov 2013 | B2 |
| 8663109 | Brister et al. | Mar 2014 | B2 |
| 8721585 | Mensinger et al. | May 2014 | B2 |
| 8750955 | Mensinger et al. | Jun 2014 | B2 |
| 8808228 | Brister et al. | Aug 2014 | B2 |
| 8882741 | Brauker et al. | Nov 2014 | B2 |
| 8920401 | Brauker et al. | Dec 2014 | B2 |
| 8926585 | Brauker et al. | Jan 2015 | B2 |
| D727928 | Allison et al. | Apr 2015 | S |
| 9020572 | Mensinger et al. | Apr 2015 | B2 |
| 9050413 | Brauker et al. | Jun 2015 | B2 |
| D738385 | Lim et al. | Sep 2015 | S |
| 9143569 | Mensinger et al. | Sep 2015 | B2 |
| 9155843 | Brauker et al. | Oct 2015 | B2 |
| D747333 | Supino et al. | Jan 2016 | S |
| D748101 | Bang et al. | Jan 2016 | S |
| D748126 | Sarukkai et al. | Jan 2016 | S |
| D749103 | Song | Feb 2016 | S |
| D753685 | Zimmerman et al. | Apr 2016 | S |
| D754689 | Lee | Apr 2016 | S |
| D759684 | Bijlani et al. | Jun 2016 | S |
| D761280 | Chung et al. | Jul 2016 | S |
| D763308 | Wang et al. | Aug 2016 | S |
| D766958 | Salazar Cardozo et al. | Sep 2016 | S |
| 9446194 | Kamath et al. | Sep 2016 | B2 |
| D777760 | Zhao et al. | Jan 2017 | S |
| D781890 | Gathman et al. | Mar 2017 | S |
| D783037 | Hariharan et al. | Apr 2017 | S |
| D783648 | Vazquez et al. | Apr 2017 | S |
| D784391 | Yuguchi et al. | Apr 2017 | S |
| D785025 | Zimmerman et al. | Apr 2017 | S |
| D786273 | Herman et al. | May 2017 | S |
| 9672328 | Saint et al. | Jun 2017 | B2 |
| D791806 | Brewington et al. | Jul 2017 | S |
| D794047 | Gandhi et al. | Aug 2017 | S |
| D795900 | Bischoff et al. | Aug 2017 | S |
| D795919 | Bischoff et al. | Aug 2017 | S |
| D795927 | Bischoff et al. | Aug 2017 | S |
| D797760 | Tsujimura et al. | Sep 2017 | S |
| D798312 | Tsujimura et al. | Sep 2017 | S |
| 9775543 | Brister et al. | Oct 2017 | B2 |
| D808986 | Dudey | Jan 2018 | S |
| D809544 | Ambielli | Feb 2018 | S |
| D809545 | Ban et al. | Feb 2018 | S |
| D811425 | Olsen et al. | Feb 2018 | S |
| D815127 | Phillips et al. | Apr 2018 | S |
| D815667 | Yeung | Apr 2018 | S |
| 9937293 | Brauker et al. | Apr 2018 | B2 |
| D819043 | Yamaura et al. | May 2018 | S |
| D820297 | Gardner et al. | Jun 2018 | S |
| 9996668 | Reihman et al. | Jun 2018 | B2 |
| D831049 | Agarwal et al. | Oct 2018 | S |
| D831684 | Ghosh | Oct 2018 | S |
| D832292 | Hu et al. | Oct 2018 | S |
| D832870 | Hu | Nov 2018 | S |
| D833469 | Coleman et al. | Nov 2018 | S |
| D835118 | Lee et al. | Dec 2018 | S |
| D837807 | Baber et al. | Jan 2019 | S |
| D838734 | Kruse et al. | Jan 2019 | S |
| 10169539 | Reihman et al. | Jan 2019 | B2 |
| D842888 | Krainer et al. | Mar 2019 | S |
| D843402 | Casse et al. | Mar 2019 | S |
| D846590 | Cabrera et al. | Apr 2019 | S |
| D847165 | Cheney et al. | Apr 2019 | S |
| 10271766 | Parker, Jr. | Apr 2019 | B1 |
| D849757 | Jing et al. | May 2019 | S |
| 10278580 | Brister et al. | May 2019 | B2 |
| 10898653 | Saint et al. | Jan 2021 | B2 |
| 11369743 | Saint et al. | Jun 2022 | B2 |
| 20030065536 | Hansen et al. | Apr 2003 | A1 |
| 20040039255 | Simonsen et al. | Feb 2004 | A1 |
| 20050038674 | Braig et al. | Feb 2005 | A1 |
| 20050049179 | Davidson et al. | Mar 2005 | A1 |
| 20050182358 | Veit et al. | Aug 2005 | A1 |
| 20050192494 | Ginsberg | Sep 2005 | A1 |
| 20050192557 | Brauker et al. | Sep 2005 | A1 |
| 20060036144 | Brister et al. | Feb 2006 | A1 |
| 20060173417 | Rosen et al. | Aug 2006 | A1 |
| 20070021715 | Kohlbrenner et al. | Jan 2007 | A1 |
| 20070038044 | Dobbles et al. | Feb 2007 | A1 |
| 20070173708 | Dobbles et al. | Jul 2007 | A9 |
| 20070186923 | Poutiatine et al. | Aug 2007 | A1 |
| 20070239486 | Gordon | Oct 2007 | A1 |
| 20080162192 | Vonk et al. | Jul 2008 | A1 |
| 20080188813 | Miller et al. | Aug 2008 | A1 |
| 20080201169 | Galasso et al. | Aug 2008 | A1 |
| 20080234663 | Yodfat et al. | Sep 2008 | A1 |
| 20080235053 | Ray et al. | Sep 2008 | A1 |
| 20080262469 | Brister et al. | Oct 2008 | A1 |
| 20090036771 | Fago et al. | Feb 2009 | A1 |
| 20090048561 | Burren et al. | Feb 2009 | A1 |
| 20090069742 | Larsen | Mar 2009 | A1 |
| 20090131875 | Green | May 2009 | A1 |
| 20090163793 | Koehler | Jun 2009 | A1 |
| 20090209938 | Aalto-Setala | Aug 2009 | A1 |
| 20090216103 | Brister et al. | Aug 2009 | A1 |
| 20090240120 | Mensinger et al. | Sep 2009 | A1 |
| 20090240128 | Mensinger et al. | Sep 2009 | A1 |
| 20090240193 | Mensinger et al. | Sep 2009 | A1 |
| 20090299276 | Brauker et al. | Dec 2009 | A1 |
| 20100049126 | Bronfeld et al. | Feb 2010 | A1 |
| 20100063438 | Bengtsson | Mar 2010 | A1 |
| 20100081993 | O'Connor | Apr 2010 | A1 |
| 20100185075 | Brister et al. | Jul 2010 | A1 |
| 20100261987 | Kamath et al. | Oct 2010 | A1 |
| 20100331656 | Mensinger et al. | Dec 2010 | A1 |
| 20100331657 | Mensinger et al. | Dec 2010 | A1 |
| 20110009727 | Mensinger et al. | Jan 2011 | A1 |
| 20110264033 | Jensen et al. | Oct 2011 | A1 |
| 20110270158 | Brauker et al. | Nov 2011 | A1 |
| 20110275986 | Bashan | Nov 2011 | A1 |
| 20110281791 | Zion et al. | Nov 2011 | A1 |
| 20110313349 | Krulevitch et al. | Dec 2011 | A1 |
| 20110313350 | Krulevitch et al. | Dec 2011 | A1 |
| 20110313395 | Krulevitch et al. | Dec 2011 | A1 |
| 20120072236 | Atkin | Mar 2012 | A1 |
| 20120186581 | Brauker et al. | Jul 2012 | A1 |
| 20120190953 | Brauker et al. | Jul 2012 | A1 |
| 20120191063 | Brauker et al. | Jul 2012 | A1 |
| 20120215201 | Brauker et al. | Aug 2012 | A1 |
| 20120220979 | Brauker et al. | Aug 2012 | A1 |
| 20120238852 | Brauker et al. | Sep 2012 | A1 |
| 20120296311 | Brauker et al. | Nov 2012 | A1 |
| 20130035575 | Mayou et al. | Feb 2013 | A1 |
| 20130035865 | Mayou et al. | Feb 2013 | A1 |
| 20130035871 | Mayou et al. | Feb 2013 | A1 |
| 20130171938 | Mears et al. | Jul 2013 | A1 |
| 20130184996 | Zivitz et al. | Jul 2013 | A1 |
| 20130197445 | Schabbach et al. | Aug 2013 | A1 |
| 20130197479 | Butler et al. | Aug 2013 | A1 |
| 20130211248 | Cowan et al. | Aug 2013 | A1 |
| 20130291116 | Homer | Oct 2013 | A1 |
| 20140012117 | Mensinger et al. | Jan 2014 | A1 |
| 20140012118 | Mensinger et al. | Jan 2014 | A1 |
| 20140012510 | Mensinger et al. | Jan 2014 | A1 |
| 20140012511 | Mensinger et al. | Jan 2014 | A1 |
| 20140074041 | Pedersen et al. | Mar 2014 | A1 |
| 20140113856 | Pohl et al. | Apr 2014 | A1 |
| 20140114158 | Brister et al. | Apr 2014 | A1 |
| 20140114161 | Kamath et al. | Apr 2014 | A1 |
| 20140257065 | Walsh | Sep 2014 | A1 |
| 20140276531 | Walsh | Sep 2014 | A1 |
| 20140288494 | Brister et al. | Sep 2014 | A1 |
| 20150073337 | Saint et al. | Mar 2015 | A1 |
| 20150202377 | Haupt | Jul 2015 | A1 |
| 20150351683 | Brauker et al. | Dec 2015 | A1 |
| 20150359965 | O'Connor et al. | Dec 2015 | A1 |
| 20160012205 | Saint | Jan 2016 | A1 |
| 20160030683 | Taylor | Feb 2016 | A1 |
| 20160066843 | Mensinger et al. | Mar 2016 | A1 |
| 20160081632 | Kamath et al. | Mar 2016 | A1 |
| 20160101232 | Kamath et al. | Apr 2016 | A1 |
| 20160175097 | Chechik | Jun 2016 | A1 |
| 20170068799 | Mensinger et al. | Mar 2017 | A1 |
| 20170124272 | Reihman et al. | May 2017 | A1 |
| 20170124275 | Reihman et al. | May 2017 | A1 |
| 20170124350 | Reihman et al. | May 2017 | A1 |
| 20170131993 | Salameh et al. | May 2017 | A1 |
| 20170132120 | Salameh et al. | May 2017 | A1 |
| 20170185283 | Bhavaraju et al. | Jun 2017 | A1 |
| 20170185284 | Bhavaraju | Jun 2017 | A1 |
| 20170189625 | Cirillo et al. | Jul 2017 | A1 |
| 20170270276 | Saint et al. | Sep 2017 | A1 |
| 20170286194 | Morris et al. | Oct 2017 | A1 |
| 20170286614 | Morris et al. | Oct 2017 | A1 |
| 20170366617 | Mensinger et al. | Dec 2017 | A1 |
| 20170367627 | Brister et al. | Dec 2017 | A1 |
| 20180185587 | Brauker et al. | Jul 2018 | A1 |
| 20180303417 | Mensinger et al. | Oct 2018 | A1 |
| 20180353698 | Saint et al. | Dec 2018 | A1 |
| 20190015020 | Brister et al. | Jan 2019 | A1 |
| 20190035500 | Saint et al. | Jan 2019 | A1 |
| 20190125224 | Kamath et al. | May 2019 | A1 |
| 20190132801 | Kamath et al. | May 2019 | A1 |
| 20190173885 | Kamath et al. | Jun 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 0298067 | Jan 1989 | EP |
| 0513128 | Nov 1992 | EP |
| 0927057 | Jul 1999 | EP |
| 2491857 | Aug 2012 | EP |
| 2572740 | Mar 2013 | EP |
| 9638190 | Dec 1996 | WO |
| 2010052275 | May 2010 | WO |
| 2011041007 | Apr 2011 | WO |
| 2012046199 | Apr 2012 | WO |
| 2013053695 | Apr 2013 | WO |
| 2014128157 | Aug 2014 | WO |
| 2015047870 | Apr 2015 | WO |
| 2015169814 | Nov 2015 | WO |
| 2015185686 | Dec 2015 | WO |
| 2016071912 | May 2016 | WO |
| 2017132577 | Aug 2017 | WO |
| Entry |
|---|
| Cision PR News Wire, “CompaNion Medical Announces Insights by InPen, the Future of MDI Reports”, Jun. 20, 2018. |
| Copenheaver, B. R., Authorized Officer, ISA/US, International Search Report and Written Opinion, International Application No. PCT/US2014/056336, dated Dec. 31, 2014, 10 pages. |
| Young, Lee W., ISA/US, International Search Report, International Application No. PCT/US15/40069, dated Dec. 22, 2015, 13 pages. |
| Young, Lee W., ISA/US, Invitation to Pay Additional Fees and Partial Search Report, International Application No. PCT/US15/40069, dated Oct. 1, 2015, 2 pages. |
| Extended European Search Report for European Patent Application No. 14849422.2, dated May 4, 2017, 11 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2018/036768; dated Aug. 31, 2018, 10 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2017/15452, dated May 23, 2017, 14 pages. |
| Extended European Search Report for European Patent Application No. 17745019.4, dated Aug. 6, 2019, 9 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2018/55646, dated Feb. 6, 2019, 15 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220347390 A1 | Nov 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62668723 | May 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17156681 | Jan 2021 | US |
| Child | 17846406 | US | |
| Parent | 16407046 | May 2019 | US |
| Child | 17156681 | US |
