Medical delivery device with regimen identification feature
09734302 · 2017-08-15
Assignee
Inventors
- Ole C. Nielsen (Hilleroed, DK)
- Michael Monrad (Frederiksberg, DK)
- Mads Moeller (Hundested, DK)
- Torkil Filholm (Dyssegaard, DK)
Cpc classification
A61J7/0436
HUMAN NECESSITIES
A61J1/00
HUMAN NECESSITIES
G16H50/20
PHYSICS
A61M2205/3592
HUMAN NECESSITIES
A61M2005/3125
HUMAN NECESSITIES
A61M5/00
HUMAN NECESSITIES
A61M2205/3379
HUMAN NECESSITIES
A61J7/049
HUMAN NECESSITIES
A61J2205/50
HUMAN NECESSITIES
A61M2205/52
HUMAN NECESSITIES
International classification
G08B1/00
PHYSICS
A61M5/00
HUMAN NECESSITIES
A61J7/00
HUMAN NECESSITIES
A61J1/00
HUMAN NECESSITIES
A61J7/04
HUMAN NECESSITIES
Abstract
A drug delivery system comprising a controller adapted to detect when a given user-actuated operation being part of the expelling of an amount of drug is performed, record detected operations as a function of time, and estimate, based on recorded operations, time parameters for the detected operations, thereby providing time parameters for a medical regimen on which the detected operations are assumed to be based upon.
Claims
1. A drug delivery system adapted to estimate time parameters for a medical regimen comprising one or more administering events at a given time within a given period, comprising: a controller, a drug reservoir or structure for receiving a drug reservoir, drug expelling structure for expelling an amount of drug from the reservoir, wherein the expelling of an amount of drug requires at least one user-actuated operation to be performed, and wherein the expelling of an amount of drug represents an administering event, the controller being adapted to: detect when a given user-actuated operation being part of the expelling of an amount of drug is performed, record detected operations as a function of time, and estimate, based on recorded operations, regimen time parameters for the detected operations, including: the periodicity, and a time or time window for each operation in the estimated period, thereby providing estimated time parameters for a medical regimen on which the detected operations are assumed to be based upon.
2. A drug delivery system as in claim 1, the system being configured to be set in a programming mode and a non-programming mode, wherein operations are detected and recorded when in the programming mode.
3. A drug delivery system as in claim 1, the system being configured to dynamically estimate time parameters incorporating most recent detected and recorded operations.
4. A drug delivery system as in claim 1, wherein the controller comprises information about a number of predefined regimens, the estimated parameters being matched to the best-fitting pre-defined regimen if possible for a given predefined confidence level.
5. A drug delivery system as in claim 1, wherein the system comprises: structure for receiving a drug reservoir, structure for detecting an identifier provided on a received drug reservoir, wherein the controller comprises information about at least two identifiers, each identifier being related with at least one predefined regimen, the estimated parameters being matched to the best-fitting predefined regimen if possible for a given predefined confidence level.
6. A drug delivery system as in claim 1, wherein the drug expelling structure comprises: setting structure allowing a user to set a dose amount to be expelled, and actuation structure for driving or releasing the drug expelling structure to expel the set dose.
7. A drug delivery system as in claim 6, wherein the controller is configured to detect the amount of drug expelled, the controller estimating for each action in an identified regimen an amount or a range of drug expelled.
8. A drug delivery system as in claim 6, wherein the system is configured to provide reminders to the user based on the estimated time parameters.
9. A drug delivery system as in claim 6, wherein the system is configured to provide warnings to the user based on the estimated time parameters and the actual use of the delivery system.
10. A drug delivery system as in claim 6, adapted to for a given time period calculate a compliance value based on calculated regimen time parameters and corresponding detected operations, the compliance value being indicative of the user's adherence to the regimen, wherein the compliance value is calculated for a user-selectable time period.
11. A drug delivery system as in claim 6, adapted to for a given time period calculate a compliance value based on the calculated regimen time parameters and corresponding detected operations, the compliance value being indicative of the user's adherence to the regimen, the drug delivery further being adapted to display compliance value information comprising icons selected in accordance with the degree of compliance.
12. A method adapted to estimate time parameters for a medical regimen comprising one or more administering events at a given time within a given period, comprising the steps: providing a system comprising: a controller, a drug reservoir or structure for receiving a drug reservoir, drug expelling structure for expelling an amount of drug from the reservoir, wherein the expelling of an amount of drug requires at least one user-actuated operation to be performed, and wherein the expelling of an amount of drug represents an administering event, detecting when a given user-actuated operation being part of the expelling of an amount of drug is performed, record detected operations as a function of time, and estimate, based on recorded operations, regimen time parameters for the detected operations, including: the periodicity, and a time or time window for each operation in the estimated period, thereby providing estimated time parameters for a medical regimen on which the detected operations are assumed to be based upon.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
(1) In the following the invention will be further described with reference to the drawings, wherein
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14) In the figures like structures are mainly identified by like reference numerals.
DESCRIPTION OF EXEMPLARY EMBODIMENTS
(15) When in the following terms such as “upper” and “lower”, “right” and “left”, “horizontal” and “vertical” or similar relative expressions are used, these only refer to the appended figures and not to an actual situation of use. The shown figures are schematic representations for which reason the configuration of the different structures as well as there relative dimensions are intended to serve illustrative purposes only.
(16) Referring to
(17) When using a drug delivery device of the above general type (which may have other formfactors and also be provided with a motorized expelling mechanism), the user is typically recommended to take a subcutaneous injection by performing the following steps: remove the cap to uncover the needle mount, mount a new needle assembly, set a dose amount to be expelled by rotating the dose setting member, when the needle has been inserted subcutaneously actuate the release means for driving or releasing the drug expelling means to expel the set dose, after having withdrawn the needle from the skin remove the needle assembly from the needle mount, and re-attach the cap to cover the needle mount.
(18) The purpose of the disclosed drug delivery device is to provide an easy-to-use reminder programming functionality, where normal use of the drug delivery device provides automatic programming of a reminder scheme based in estimated time parameter values for a drug regimen as e.g. prescribed by a patient's medical practitioner. The device may be intended to be used with a single type of drug, e.g. a diabetes drug which is to be taken once daily, e.g. Levemir® or Victoza® from Novo Nordisk, or a diabetes drug which has to be taken twice or more daily, e.g. NovoRapid® or NovoMix® from Novo Nordisk, or it may be a general-purpose device adapted to identify a variety of drug regimens. In the following a number of examples illustrating different aspects of the present invention will be given.
(19) Tables 1a, 1b, 1c and 1d show examples of medical regimens identified as a result of an analysis performed by the injection device on a number of previously taken injections. It contains a number of data set containing injection time and injection amount information with a repetition period, i.e. a ‘wrap around’ time.
(20) TABLE-US-00001 TABLE 1a [6 h 30 m, 7 h 30 m] & [30, 35] IU
(21) Table 1a shows a once daily regimen, systematic with a ‘wrap around’ time of 24 hours. Each day the patient is supposed to make an injection between half past 6 and half past 7 in the morning (i.e. 6.30, 7.30) and with an out-dosing amount between 30 and 35 IU (International Units).
(22) TABLE-US-00002 TABLE 1b [6 h 30 m, 7 h 30 m] & [30, 35] IU [18 h 30 m, 19 h 30 m] & [30, 35] IU
(23) Table 1b shows a twice daily regimen, systematic with a ‘wrap around’ time of 24 hours. Each day the patient is supposed to make an injection between half past 6 and half past 7 in the morning (i.e. 6.30, 7.30) and again in the evening between half past 6 and half past 7 o'clock (i.e. 18.30, 19.30). Both in the morning and in the evening the out-dosing drug amount should be between 30 and 35 IU (International Unit).
(24) TABLE-US-00003 TABLE 1c [1 d 6 h 30 m, 1 d 7 h 30 m] & [30, 35] IU [1 d 18 h 30 m, 1 d 19 h 30 m] & [30, 35] IU [2 d 6 h 30 m, 2 d 7 h 30 m] & [30, 35] IU [2 d 18 h 30 m, 2 d 19 h 30 m] & [30, 35] IU [3 d 6 h 30 m, 3 d 7 h 30 m] & [30, 35] IU [3 d 18 h 30 m, 3 d 19 h 30 m] & [30, 35] IU [4 d 6 h 30 m, 4 d 7 h 30 m] & [30, 35] IU [4 d 18 h 30 m, 4 d 19 h 30 m] & [30, 35] IU [5 d 6 h 30 m, 5 d 7 h 30 m] & [30, 35] IU [5 d 18 h 30 m, 5 d 19 h 30 m] & [30, 35] IU [6 d 6 h 30 m, 6 d 7 h 30 m] & [30, 35] IU [6 d 18 h 30 m, 6 d 19 h 30 m] & [35, 40] IU [7 d 8 h 00 m, 7 d 9 h 00 m] & [35, 40] IU [7 d 20 h 00 m, 7 d 21 h 00 m] & [30, 35] IU
(25) Table 4c shows a twice daily regimen, systematic with a ‘wrap around’ time of 7 days. It can be seen that the first 5 days the regimen is the same each day but for the last 2 days (day 6 and 7) the out-dosing time and amount differs a little.
(26) TABLE-US-00004 TABLE 1d [7 h 30 m, 8 h 30 m] & [20, 35] IU [12 h 30 m, 13 h 30 m] & [30, 35] IU [18 h 30 m, 19 h 30 m] & [40, 45] IU
(27) Table 1d, shows a three times daily regimen, systematic with a ‘wrap around’ time of 24 hours: Injections taken in a time window morning, midday and evening and with three different out-dosing intervals.
(28) As mentioned above the identification of the patient regimen can be performed in different ways by using automatic analytical methods conducted by the injection device. The most general regimen analytical algorithm is where the injection device figures out which regimen the patient is following by solely acquiring patient usage date during a time period. When doing this it has to arrange the data in a systematic way to identify the regimen. A very important variable in doing this is the above mentioned time ‘wrap around’ defining the systematic time period for the treatment. For example, if the medical regimen or treatment is dividable into a time period of one day, e.g. once or twice daily treatment, this is the systematic ‘wrap around’ time period.
(29) As an example an overall method could be (i) identify the time ‘wrap around’ period, (ii) identify the regimen number of out-dosing per time period, and (iii) eventually compare and further fit more closely the found regimen with one of a number of preselected regimen.
(30) In
(31)
(32) If an out-dosing (injection) regimen change is big, as would normally be the case in changes in time zones, the regimen estimator cannot necessary cope with the change in a transparent way for the user for which reason the device may warn or alert the user correspondingly for a period of time. However, after some time the estimator will include the regimen alterations into the new estimate automatically. Another way to cope with big alterations in regimen is to include the patient into some kind of set-up decision or decision to postpone the delivery device's warnings/alerts until the estimator is updated.
(33) It is common to precede an injection with an air shot or otherwise priming of the device. This to assure that the device is working properly or to remove air or air bubbles in the liquid system or to align/attach the injection devices piston rod with the drug containers piston. If the device is able to sense the dismantling of the cap from the device, e.g. if the electronics of the device is located in the cap, then this would not provide a problem as normally the user will not put the cap back on between the two operations. However, if other inputs are detected, e.g. expelling of a dose, the regimen estimator algorithm may recognize such an event. For example, if the time between two expelling actions is within a short period of time, e.g. 1 minute, the two actions may be recognized as a single dosing event. Such an algorithm could also take into account the amount of out-dosing in order to differentiate between a divided out-dosing and a preceding air shot/priming out-dosing.
(34) With reference to
(35) When identifying and using a confidence interval, this could be combined with always assuring that it is within a certain interval and if outside then reduced to a certain maximum or increased to a certain minimum value. This to prevent that a patient who adopts to the regimen estimators analysed interval will be led to a still narrower interval or on the other hand a patient who always a number of times are outside the interval could be led to a still bigger interval.
(36) TABLE-US-00005 TABLE 2 Data sets corresponding to the data sets in FIG. 4B, i.e. from a moving window of days 2-11 (10 days), where the injection has been forgotten one day. The table contains both injection time as well as injection a mount data. Day Time amount 2 6 h 02 m 40 IU 3 6 h 05 m 41 IU 4 6 h 00 m 40 IU 5 6 6 h 12 m 40 IU 7 6 h 38 m 45 IU 8 6 h 41 m 45 IU 9 6 h 11 m 40 IU 10 6 h 08 m 39 IU 11 6 h 10 m 40 IU
(37) TABLE-US-00006 TABLE 3 Data sets corresponding to the data sets in FIG. 4C, i.e. for days 3-12 (10 days). Day Time Amount 3 6 h 05 m 41 IU 4 6 h 00 m 40 IU 5 6 6 h 12 m 40 IU 7 6 h 38 m 45 IU 8 6 h 41 m 45 IU 9 6 h 11 m 40 IU 10 6 h 08 m 39 IU 11 6 h 10 m 40 IU 12 6 h 11 m 40 IU
(38) Based on data in tables 2 and 3 the mean day time value and the approximate 95% confidence interval can then be calculated.
(39) Mean day time value to be used for day 12 respectively day 13:
(40)
‘n’ being the actual number of data sets in the data window (excluding day 5).
(41) The (approximately) 95% confidence interval window:
[t.sub.mean−2*σ;t.sub.mean+2*σ],
(42) The numbers for t.sub.mean and σ is from the moving actual window of data set (day 2-11 or day 3-12).
(43) The calculated statistical population standard deviation s is used for σ, i.e.
(44)
‘n’ being the actual number of data set in the data window, ‘a’ is the first day and ‘b’ is the last day in the moving window of data set (2, 11 respectively 3, 12 in the examples).
(45) The actual calculation of confidence interval to be used to compare the next injection time which can be set more or less aggressively. For example, a smaller confidence interval will require the next injection to be closer to the mean value than a wider interval.
(46) Though the calculation shown here is simple much more advanced calculations can be taken into account including fitting against special distributions, dynamic length windows (number of samplings of data set) e.g. requiring certain values for the statistical variance. These statistical variance targets could also be depending of the result itself for an estimated regimen.
(47) For table 2 the mean day time for injection can now be calculated by:
(48)
giving t.sub.mean,2,11=6h13m
(49) And the (approx.) 95% confidence interval for injections day time can be calculated by:
(50)
(51) Giving 95% confidence interval=[5h45m, 6h41m] (day 5 not included in the calculation).
(52) The regimen in this embodiment is a once daily injection taken between 15 minutes to 6 o'clock and 19 minutes to 7 o'clock for day 12. It can be seen that the delivery time for day 12 is within the confidence interval calculated above [5h45m, 6h41m], namely at 11 minutes past 6 o'clock. Correspondingly, the delivery at day 12 is regarded done accordingly to the patient's medical regimen as defined by the regimen estimator of the injection device.
(53) With regard to the data set of table 3 the regimen estimator now estimates a new confidence window for the injection time, this is [5h48m, 6h42m] to be used for day 13.
(54) A more sophisticated regimen estimator can also include the amount of insulin taken each time. Indeed, this would require a drug delivery system with dose capture and not just a relatively simple cap device. For example, to fit both for injection time and out-dosing amount in the ‘wrap around’ time period. If the injection times fit but not the belonging out-dosing amount, it can be caused by the ‘wrap around’ time is to short, e.g. day based and not week based thereby not including patient's weekend/workday differences in behaviour or it could be caused by the medical regimen requires different drug amount at different times of day or caused by different actual needs during the day or week. The estimator tries to use as short a period (‘wrap around’ time) as possible taking both time and out-dosing amount into account. If it is not able to fit within required margins (e.g. measured in standard deviations) it should extend the period to a next level and make a new calculation on the acquired data set and data set groups. If still not able to fit it should extend to the next following level and so on.
(55) If after a certain time (this time either set up in the device initially or by a user or possibly derived from the acquired data set itself) the regimen estimator still can't find a fit for both the time of injection regimen as well as the belonging injections amount it can either choose to only use the time information for the regimen or ask the user to suggest a regimen or to continue the acquiring of data set trying to get a fit.
(56) If the regimen estimator identifies the medical regimen including a number of out-dosing then also the expected amount belonging to the out-dosing time can be estimated in similar ways as the injection time itself by using more or less sophisticated statistical methods. A simple estimate (for the next out-dosing amount) can be based on a confidence interval similar to the one described above for the time of out-dosing.
(57) E.g. by using data set from the table in table 2, the mean out-dosing amount is:
(58)
(59) And the (approx.) 95% confidence interval for out-dosing amount can be calculated by:
(60)
(61) And with the actual values inserted the (approx.) 95% confidence interval for the out-dosing amount based on day 2 to 11 is calculated to [37, 45] IU.
(62) When out-dosing (or not) on day 12 the out-dosing time and amount can be compared with the time window and amount window based on the above calculated 95% confidence intervals based on data set from day 2 to day 11.
(63) As can be seen in the example above based on table 2 the 95% confidence interval is [5h45m, 6h41m]. This means that according to the regimen estimator the next delivery should take place between 5:45 and 6:41. Besides deliveries being within this time window also the amount of out-dosed drug can be compared with the calculated estimate. As can be seen from the example above the (approx.) 95% confidence interval is [37, 45] IU. So with this regimen estimator the next out-dosing amount should be within this window. There are three different cases when comparing a given dose delivery with the calculated time interval.
(64) A: If an Injection is Taken Before the Time Window
(65)
(66) B: If an Injection is Taken within the Time Window
(67)
(68) C: If an Injection is Taken after the Time Window
(69)
(70) If the drug delivery system is adapted to detect the amount of expelled drug, warnings may be given if doses outside the estimated range for an estimated dose-delivery may be given. The means of communication may include any suitable means for making a visual, audible or tactile signal. Besides communicating directly to the patient the information can also be sent to other devices, e.g. a person's smartphone or computer network by electronics means including NFC and RF communication.
(71) With reference to
(72)
(73) In the distal cavity the electronic means 230 providing the reminder functionality of the cap is arranged, the electronic means comprising a processor and associated memory (not shown), an electric cell 231 (“battery”), a buzzer 232 and a read switch 233 which is actuated when the actuation member is moved distally when a pen body is inserted in the proximal cavity of the pen cap. Depending on the specific design of the actuation member, actuation of the read switch may or may not require that a needle assembly is mounted on the pen body.
(74)
(75) In the shown embodiment of
(76)
(77) If the device already contains information on a number of known regimens for patients using the actual type of injection device this could be used to ease or secure the correct identification of the patient actual medical regimen. Correspondingly, the pen may be adapted to receive data to be used by the estimating algorithm. For example, to ease the complexity of the task to identify the regimen helpful information would be the specific drug loaded in the injection device. This information can be input to the injection device by the user, e.g. by set-up buttons on the device or by use of another device able to communicate to the device, e.g. a mobile phone or a PC and communicated by some communication protocol, e.g. NFC or Bluetooth.
(78) The drug information could also be read by the injection device either from another physical item, e.g. the drug secondary package (e.g. by NFC reading an RFID tag), or a separate item where the information is displayed or embedded or by some information or characteristics of the drug itself or of the primary packaging of the drug, e.g. a coded information on the label on a drug container.
(79) When a drug delivery system has been provided with information in respect of a medical regimen to be followed, e.g. by automatic estimation as described above, and is adapted to detect an event indicative of the actions of the regimen being performed, then it would be possible to compare actual events with planned or estimated events, and then calculate a compliance value for a given period. Thus, each event may be evaluated against a criterion which consists of a reference time period termed a “compliance window”. The periods before and after the window may either be identical or individually defined, depending on medical considerations. An event inside the compliance window is considered compliant, while an event outside the compliance window is considered none-compliant. The compliance value may be calculated for one or more periods serving different purposes. For example, for the patient it may be of greatest interest to know the compliance for the most recent past, e.g. for the last week, whereas for a medical practitioner a longer period may be relevant, e.g. for a diabetes patient 3 months corresponding to the period for which a HbA1.sub.c measurement is indicative of the patient's average blood sugar concentration.
(80) Calculations of actual use of the device against medical regimen can be performed by utilizing simple statistics or more complex statistics. An example of a simple routine or calculation is to count the number of non-compliant injections against total number of injections for a prolonged period and displaying this calculation as a percentage rate, e.g. a regimen for a 91 day period has resulted in 7 non-compliant situations, e.g. forgotten injection (out-dosing), resulting in a non-compliant percentage of 7/91=7.7%
(81) An example of a slightly more sophisticated calculation could be to count and sum up the amount of out-dosed drug within a period and to compare it with the regimen prescribed or estimated amount together with a count of missed time windows and/or amount windows out-dosed in the period. For example, if for a twice daily regimen for a 7 days period two injections have been forgotten and one injection has been less than the prescribed dose (15 instead of 20 IU), this would result in a non-compliance of total amount of −16% ((235−280)/280), time window −14% (−2/14), amount window −21% (−3/14). More statistical methods can be taken into action e.g. calculations of standard deviation to indicate the spread in deviations.
(82) A further analysis and/or break-down of non-compliance situations to see if there are certain times or certain conditions where it is more likely for the patient to have a non-compliance situation can be identified and displayed. An example could be to break down a prolonged period into e.g. week-days to see if there are certain days and/or time of day where non-compliant situations are more frequent than others. Hereby the patient as well as the caring personal has a fast and efficient method to identify not only compliance or non-compliance of the patient regarding a medical regimen but also to identify potential situations or times where the likelihood for non-compliant behaviour is higher than else.
(83) An example of this is shown in
(84) As the regimen will differ from patient to patient the system is configured to generate a display view adapted to the identified regimen. As appears, the
(85) In the above a pen-formed drug delivery device is used to illustrate different examples embodying aspects of the present invention, however, the invention may be used in many other types of devices, e.g. medical aerosol inhalers, tablet dispensing devices and blood glucose meters etc.
(86) In the above description of the preferred embodiments, the different structures and means providing the described functionality for the different components have been described to a degree to which the concept of the present invention will be apparent to the skilled reader. The detailed construction and specification for the different components are considered the object of a normal design procedure performed by the skilled person along the lines set out in the present specification.