User authentication for drug delivery devices - Patents.com
The method of user authentication through motion data analysis in drug delivery devices ensures only authorized users can operate the device, enhancing safety and simplifying operation by integrating with daily routines.
Patent Information
- Application Number
- JP2024526567
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-11-03
- Filing Date
- 2022-11-02
- Publication Date
- 2024-11-13
AI Technical Summary
Existing drug delivery devices lack effective user authentication methods to prevent unauthorized use, particularly in scenarios where multiple users have access and the device operation must be user-specific, such as for patients with chronic diseases like diabetes.
A method of user authentication using motion data analysis, where the device compares acquired motion data with user-specific records to enable or disable functionality, utilizing sensors and electronic circuitry integrated into or attached to the drug delivery device or mobile electronic devices like smartphones and smartwatches.
Enhances patient safety by ensuring only authorized users can operate the device, preventing unauthorized use and simplifying operation through user-specific authentication that integrates seamlessly with daily routines.
Smart Images

Figure 2024542090000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a method of authenticating a user for using a drug delivery device, an authentication system for authenticating a user, a computer program for user authentication, and a mobile electronic device for providing user authentication. [Background technology]
[0002] Drug delivery devices for setting and expelling single or multiple doses of liquid medication are per se well known in the art. In general, such devices have a purpose substantially similar to that of a conventional syringe.
[0003] Drug delivery devices, e.g. injection devices such as pen-type syringes and needle-based injection systems (NIS) devices, must meet various user-specific requirements. For example, in the case of patients suffering from chronic diseases such as diabetes, the patient may be physically debilitated and may also have poor eyesight. Therefore, a suitable drug delivery device, especially for home drug treatment, needs to be robust in construction and should be easy to use. Furthermore, the operation and general handling of the device and its components should be clear and easy to understand. Such an injection device should allow the setting and subsequent ejection of drug doses of varying sizes. Moreover, the dose setting and dose ejection procedures must be easy to perform and unambiguous.
[0004] Patients suffering from certain diseases require certain amounts of medication to be infused through a syringe pen or through a pump.
[0005] Some drug delivery or infusion devices select variable sized doses of drug and inject preset doses, while other infusion devices set and expel a fixed dose, where the amount of drug to be infused according to some prescribed schedule is always the same and does not change or can not be altered over time.
[0006] Needle injections, as performed with various injection devices, are increasingly associated with measuring and logging of data relating to the amount of medication set or dispensed or injected at a particular date or time. To this end, injection devices may be provided with electronic circuitry that provides for data acquisition and / or data logging, as well as communication of collected or measured dispense-related data.
[0007] Such an electronic circuit or electronic unit may be implemented in or integrated into the injection device itself. Alternatively, such an electronic circuit or electronic unit may be provided by an auxiliary or accessory device configured to be removably attached to the injection device and operable to record injection-related data during use of the injection device. Furthermore, the electronic circuit for data logging may also be provided with a communication interface to transfer previously stored injection-related data to an external electronic device for further data processing.
[0008] Some users or patients may need to administer different medications using different drug delivery devices, which may appear similar at first glance, and which may be located in a home where, in theory, multiple people can access the device rather than just one.
[0009] It is therefore desirable to provide an improved method and system for authenticating a user to use a particular drug delivery device. It is further desirable to provide a computer program, and respective hardware components, for improving patient safety and preventing fraudulent use of a drug delivery device by users not authorized to use the drug delivery device. Summary of the Invention [Means for solving the problem]
[0010] According to one aspect, the present disclosure relates to a method of user authentication for use of a drug delivery device, such as an injection device, comprising the steps of acquiring motion data of a user and comparing the acquired motion data with stored motion data of a user-specific data record. Based on the comparison, a data matching index is generated. The data matching index indicates a degree of matching or similarity between the acquired motion data and the stored motion data. Furthermore, a function, such as an electronically implemented function of the drug delivery device, is enabled, disabled, triggered, or terminated based on the data matching index.
[0011] Typically, an authorized user of a drug delivery device is identified by its motion data. The motion data is typically acquired or collected by the drug delivery device itself or by a mobile electronic device, for example carried by or attached to the user. Typically, the user's motion data is acquired over a predefined period of time, and / or the motion data is acquired at a particular predefined time point or on a particular day. The motion data is characteristic and distinct for each user who uses the drug delivery device. This may provide a kind of fingerprint for each user.
[0012] Typically, a first user is characterized by the motion data of a first user-specific data record, and a second user is thus characterized by the motion data of a second user-specific data record. By comparing the motion data captured while a user is moving or performing or engaging in a particular movement or motion pattern, and by comparing the captured motion data of this user with the motion data of the user-specific data record, a user of the mobile electronic device and / or a user of the drug delivery device can be identified.
[0013] Typically, and in some instances, a user-specific data record is assigned or mapped to a particular drug delivery device, and when the same user uses the drug delivery device, motion data for this particular user is captured, and a comparison of the captured motion data with the user-specific data record assigned or mapped to the drug delivery device shows a high degree of matching or similarity, and therefore the user is permitted to use the drug delivery device.
[0014] Thus, at least one function of the drug delivery device is enabled, disabled, triggered, or terminated at the request of the user of the drug delivery device. In other circumstances, if a second user who is not authorized to use the drug delivery device attempts to use this particular device, the motion data of this second user is collected or acquired and compared with the motion data of the user-specific data record of the first user mapped to this particular drug delivery device. Since the motion data of the second user is distinct from the motion data of the user-specific data record, a lower degree of matching or similarity will be identified between the acquired motion data of the second user and the stored motion data of the user-specific data record of the first user. Thus, the function of the drug delivery device is enabled, disabled, triggered, or terminated based on the data matching index.
[0015] In some examples, when a user is authenticated to use the drug delivery device, the device functionality may be enabled or triggered, whereas in other situations, if an analysis or evaluation of the user's motion data indicates that the user is not authenticated to use the drug delivery device, for example due to a poor degree of matching between the captured motion data and the stored motion data, the drug delivery device functionality may be disabled or terminated.
[0016] According to another example, the user's motion data is acquired by an electronic circuit including at least one of a communication interface and a sensor. In some examples, the electronic circuit is implemented or incorporated in the drug delivery device or in an auxiliary device that can be attached to the drug delivery device. In other examples, the electronic circuit is implemented or incorporated in a mobile electronic device such as a smartphone, a smart watch, a tablet computer, a fitness tracker, or a radio tag. Typically, such a mobile electronic device can be carried by a user in some manner. In this way, the mobile electronic device can collect or acquire the user's motion data from time to time or permanently. It can therefore be operable to perform a comparison between the acquired motion data and the stored motion data of a user-specific data record.
[0017] In another example, if electronic circuitry is implemented within or attached to the drug delivery device, movements of the drug delivery device, e.g., performed by a user of the device, can be detected, e.g., when the user picks up the injection device or lifts the injection device off a desk.
[0018] The sensor may recognize the user's movements or motion patterns and / or gestures when he or she moves or when he or she moves the mobile electronic device and / or the drug delivery device. In this way, the user's movement profile or patterns or typical gestures of the user can be detected and / or quantitatively measured. Such movement patterns or gestures can be permanently or occasionally captured and compared with the movement or motion patterns and / or gesture data stored in one of the drug delivery device, the auxiliary device, and the mobile electronic device.
[0019] Differences in the acquired motion data from the stored motion data can be detected, which therefore leads to a lower degree of matching and thus to the generation of a lower matching index. Depending on the magnitude of the matching index, execution of a function of the drug delivery device that typically requires such authorization can be enabled, disabled, triggered or terminated.
[0020] According to another example, at least a portion of the user's motion data is acquired by a sensor. The sensor includes at least one of an acceleration sensor, a rotation sensor, a position sensor, a distance sensor, and a physiological data capture sensor. The sensor is operable to generate an electrical sensor signal. The sensor is typically operatively connected to an electronic circuit and a processor operable to evaluate and / or analyze the sensor signal to derive and / or characterize motion data indicative of a characteristic movement or gesture of the user when moving the sensor.
[0021] In some examples, the sensor includes a physiological data capture sensor, which may be operable to measure at least one of temperature, blood pressure, heart rate, respiration rate, oxygen saturation, or other physiological parameters indicative of a user's health condition.
[0022] Where the sensor comprises a position sensor, this may be operable to determine an absolute or relative position, for example by communication with a satellite positioning system or by communication with other electronic devices, In this way, either the absolute position of the sensor, for example in the form of geographical coordinates, or in the form of relative coordinates with respect to other electronic devices, can be measured or determined.
[0023] In another example, the electronic circuitry may also include a clock, which may map motion or position data acquired by the sensor to dates, time points, and / or time intervals. In this manner, a motion or movement profile over a period of time may be generated that is indicative of a user's typical motion patterns.
[0024] As an example, a user may be identified as being in a particular geographic location at a typical point in time or time interval. For example, a first user may be characterized as being in a particular office building for 8 hours a day, e.g., from 9:00 to 17:00. The user may leave the office building at a regular time and take a lunch break, e.g., for 30 minutes.
[0025] Furthermore, a user may be recognized by traveling from home to work by car or public transportation at a particular time. Such motion data may be captured and acquired over a relatively long period of time. If the currently acquired motion data significantly deviates from the long-term average of the motion data, this may indicate a situation in which a different user uses the electronic circuit.
[0026] The deviation of the captured motion data from the stored or average motion data can be quantitatively expressed by a data matching index. In this way, a probability or likelihood can be generated of whether and to what extent the currently captured motion data is derived from a particular user that has been mapped or assigned to a user-specific data record.
[0027] According to another example, at least a portion of the user's motion data is obtained by the communication interface through wireless communication with a satellite positioning system, an access point of a communication network, a counterpart communication interface of a mobile electronic device, such as an auxiliary device attached to the drug delivery device, an electronic unit or electronic circuit of the drug delivery device, or one of the mobile electronic devices.
[0028] In this way, a high degree of flexibility is provided in how to acquire the user's motion data. Thus, the user's motion data can also be acquired by electronic devices that do not have sensors, such as acceleration sensors, rotation sensors, position sensors, and distance sensors. For example, in an urban area, multiple access points of a communication network may be provided with which the communication interface of the electronic circuit establishes a communication link when the electronic circuit is subject to a movement or movement. By simply recording the establishment of communication links with different access points of the communication network during a movement or movement from one place to another, a motion pattern or motion profile indicative of the user's habitual movement or movement can be generated.
[0029] Of course, the communication interface may establish a communication link, e.g. a downlink communication, with a satellite positioning system. In this way, the communication interface may be operable to determine absolute or earth geographic coordinates or a respective geographical position. The communication interface may also communicate with a counterpart communication interface of another mobile or fixed electronic device. Here, also at least relative distance or relative position information between the communication interface of the electronic circuit and the counterpart communication interface of the other mobile or fixed electronic device may be obtained.
[0030] Because there are various ways to obtain user motion data, the method for authenticating a user using the user motion data can be implemented in a wide variety of hardware and software configurations.
[0031] According to another example, the captured or stored motion data includes at least one of gesture data indicative of a characteristic gesture of a user or a motion pattern indicative of at least one of a position and motion profile of a user at a particular point in time or during a particular time interval.
[0032] The mutual mapping of position or movement with time or duration, or with time intervals, is characteristic of a certain user of the drug delivery device. In this way, and by determining the user's position and / or motion at a particular time or during a particular time interval, the user can be accurately identified. The gesture data can typically be acquired by a sensor in an electronic circuit. The gesture data can characterize how a person or user moves, or what kind of gestures are typical for such a user.
[0033] Based on the sensor signals, it can be determined whether a left-handed or right-handed user has moved the electronic circuit, for example by picking up or handling the electronic circuit and / or the drug delivery device comprising the electronic circuit. A typical gesture can be defined by an acceleration or speed profile that indicates how a user picks up a particular object and / or at what speed such a procedure is performed. Of course, this requires that the electronic circuit comprising the sensor is attached, for example, to the user's hand or wrist.
[0034] According to another example, the user-specific data record is obtained by at least one of deriving and storing motion data from previously acquired motion data for the user, or requesting and receiving user-specific motion patterns and / or user-specific gesture data from a database. In some examples, the method is performed as a self-learning method. For example, the acquired motion data for the user can be stored as user-specific motion data in the user-specific data record. Repeated acquisitions of motion data, for example at the same time or at the same or similar location or position, can also be stored in the user-specific data record.
[0035] Prior to or during storage of the captured motion data in the user-specific data record, the captured motion data may be evaluated and mapped to characteristic motion patterns or gestures for that user. Repeatedly captured motion data, and particularly repeated captured motion data of one and the same gesture or motion pattern, may enrich the content of the user-specific data record.
[0036] For example, in a fairly simple example, motion data can be characteristic of a user leaving home, e.g., to go to work, and the movement can be mapped to a particular time or time period. Capture of motion data over an extended period of time can determine that a user typically leaves home between 7:15-7:25, Monday through Friday. If currently captured motion data reveals that the user left home at, e.g., 9 a.m. on Tuesday, this can be a direct indication of a high degree of mismatch between the captured motion data and their stored motion data.
[0037] This mismatch can therefore be used to not allow the user to use the drug delivery device, or at least to prompt the user to verify whether they are truly authenticated to use the drug delivery device.
[0038] In another example, the user-specific motion pattern may be programmed or defined by the user himself. In another example, the user-specific motion pattern and / or the user-specific gesture data may be obtained from a database. Nowadays, there are many service providers, such as fitness tracker manufacturers and retailers, that collect periodic motion data, motion patterns, and / or motion profiles or physiological data of users carrying the fitness trackers. Here, each user-specific motion data or user-specific physiological data may be stored in a database.
[0039] The method may then directly request access to such databases to obtain or evaluate such user-specific data to verify user authentication or user authorization. Here, it is not necessary for the drug delivery device or electronic circuitry of the drug delivery device to permanently collect or acquire the user's motion data. It may be sufficient that such data, collected in any manner by any other entity, is made available through communication over the network.
[0040] According to another example, execution of a function of the drug delivery device is enabled or triggered when the data matching index exceeds a data matching upper threshold. In some examples, the function of the drug delivery device may be setting a dose of a drug or expelling a dose. Setting or expelling a dose may be enabled or triggered only if the data matching index is higher than the data matching upper threshold, and thus only if the user of the drug delivery device is identified by his or her own motion data. In this way, patient safety and unintended use of the drug delivery device by others can be prevented.
[0041] In yet another example, a function of the drug delivery device is disabled or terminated when the data matching index is below a data matching lower threshold. Here, in the example of a dose setting or dose delivery function of the drug delivery device, the dose setting or dose delivery may be effectively blocked as long as the data matching index is below the data matching lower threshold. A user exhibiting motion data that does not match the stored motion data of the user specific data record is not permitted to perform a particular function of the drug delivery device, such as setting and / or delivering a dose of medication.
[0042] In another example, depending on the functionality of the drug delivery device, it is also envisaged that the execution of the functionality is indeed triggered when the data matching index is lower than a data matching upper threshold and higher than a data matching lower threshold, where, as a typical example, the functionality of the drug delivery device may include or include the generation of a signal or warning to the user to manually check his / her authorization to use the drug delivery device.
[0043] In such a situation, at least one of the mobile electronic device, the drug delivery device, or the auxiliary device may be configured to generate a signal or indication to the user to take care not to use an incorrect drug delivery device.
[0044] In some examples, a further authentication routine may be automatically triggered that prompts the user to authenticate with the drug delivery device, for example by entering an identification code or similar identifying information.
[0045] According to another example, the method further includes entering into a dialog with a user or generating and outputting a user request when the data matching index is lower than the data matching upper threshold and higher than the data matching lower threshold.
[0046] As a further step, the drug delivery device functionality may then be enabled or triggered in response to a user dialogue or in response to a user reaction to a user request, where the user may be prompted to confirm that he or she does in fact have permission to use the drug deal delivery device, and once confirmation is given, the device functionality in question may be enabled or directly triggered.
[0047] If the user does not respond appropriately, within a user dialog or upon user request, the relevant function of the drug delivery device may be disabled or may remain disabled, or the currently executing function may be immediately terminated.
[0048] In another aspect, the present disclosure relates to an authentication system configured and / or operable to authenticate and / or authorize a user to use a drug delivery device. The authentication system includes an electronic circuit embedded in or attachable to the drug delivery device. The electronic circuit is operable to enable, disable, or trigger or terminate execution of a function of the drug delivery device. The functions are typically implemented as electronic functions of the drug delivery device.
[0049] The authentication system further includes at least one of a sensor and a communication interface operable to acquire motion data of a user attempting to use the drug delivery device. The authentication system further includes a storage operable to store the motion data in a user-specific data record. The authentication system further includes at least one processor operable to compare the acquired motion data with the stored motion data. The processor is further operable to generate a data matching index indicative of a degree of matching between the acquired motion data and the stored user-specific motion data. The data matching index is configured to at least one of enable, disable, trigger, or terminate execution of a function of the drug delivery device.
[0050] Typically, an authentication system is implemented to perform the above-mentioned method of authenticating a user to use a drug delivery device. Up to this point, all features, effects and advantages described above in relation to the method of authenticating and / or authorizing a user apply equally to the authentication system and vice versa.
[0051] The user-specific data record includes stored motion data characteristic of a user's typical actions, gestures, or motion or gesture profiles. The sensors and / or communication interfaces operable to acquire the motion data may be implemented in the drug delivery device, in an auxiliary device attachable to the drug delivery device, or in a mobile electronic device. Any such device is typically moved or carried by the user. In this manner, the sensors and / or communication interfaces are operable to acquire, collect, track, and / or record the user's motion data.
[0052] The captured motion data of the user, which typically includes gesture data and / or motion patterns of the user, may be characterized and compared to stored motion data in a user-specific data record. The comparison of the captured motion data to the stored motion data may be based on a predefined timeline and / or based on absolute positions of the at least one sensor and communication interface or relative positions with respect to, for example, other electronic devices.
[0053] In some examples, the motion data may also be obtained by requesting and receiving a motion pattern or motion profile from a database. In a typical usage scenario, the motion pattern or motion profile of a user carrying a smartphone or smartwatch may be tracked and / or recorded by the mobile electronic device. The motion data and / or motion profile, as well as typical gestures, may be uploaded to the database and may be requested and downloaded upon request of an authentication system for user recognition purposes.
[0054] Depending on the degree of matching, and therefore the magnitude of the data matching index, the processor may perform different data-matching and therefore different actions regarding the execution of functions of the drug delivery device. For example, in case of a higher data matching index, certain functions of the drug delivery device may be enabled or directly triggered. Such functions may include setting a dose, expelling a dose, unlocking the drug delivery device, starting or executing a user dialogue with the user, providing the user with information regarding the use of the drug delivery device, and many others.
[0055] In case of a moderate data matching index, some functions of the drug delivery device may be disabled or the execution of certain functions of the drug delivery device may be terminated. For example, in case of a moderate data matching index and therefore a moderate match between the acquired motion data and the stored user-specific motion data, the setting and / or ejection of the dose may be invalidated and thus disabled. A mechanical or electromechanical interlock of the drug delivery device may be enabled or activated. At the same time, the execution of a dialogue with the user may be triggered to prompt the user to confirm that he or she is really authorized to use the drug delivery device.
[0056] In other usage scenarios, the intermediate data matching index may implement yet another user authentication routine, where the user may be prompted to enter a user-specific or device-specific authentication code to enable and / or trigger desired features of the drug delivery device.
[0057] In case of a lower degree of matching between the acquired motion data and the stored user-specific data, other functions of the drug delivery device may be enabled or disabled, where it is conceivable that an electromechanical interlock of the drug delivery device is activated and the user must perform an alternative routine or procedure to unlock the drug delivery device.
[0058] According to another example, the electronic circuit is part of an auxiliary device that can be attached to the drug delivery device. Alternatively, the electronic circuit is part of an electronic unit that is integrated into the drug delivery device. Typically, the electronic unit includes a unit processor that is operable to perform the functions of the drug delivery device. This may then be another or the same processor that is operable to compare the acquired motion data with the stored motion data, generate or derive a data matching index, and determine which functions of the drug delivery device should be enabled, disabled, triggered, or terminated based on the data matching index.
[0059] In another example, the electronic circuit is provided with a unit communication interface by which the electronic circuit receives at least one control command from another electronic device, the other electronic device including a processor operable to compare the acquired motion data with the stored motion data and further operable to generate a data matching index.
[0060] In other examples, an electronic circuit that is part of the auxiliary device or part of an electronic unit integrated in the drug delivery device may operate alone. The electronic circuit may acquire motion data of a user, for example, when the user picks up the drug delivery device from a desk. Here, the electronic circuit may comprise a sensor implemented as, for example, one of an acceleration sensor, a rotation sensor, a position sensor, a distance sensor, and / or a physiological data capture sensor. The electronic circuit of the auxiliary device or of the drug delivery device may then acquire the motion data of the user. The same electronic circuit may also be configured to compare the acquired motion data with stored motion data. Here, the stored motion data may be stored locally in the electronic circuit of the auxiliary device or in the electronic unit of the drug delivery device.
[0061] Alternatively, the electronic circuitry is provided with a communication interface for communicating with the electronic device or with a network to request and receive user specific motion patterns from a database.
[0062] According to another example, the authentication system includes at least one mobile electronic device including at least one of a sensor and a communication interface for acquiring at least a portion of the user's motion data, which in some examples is a mobile electronic device operable to store a user-specific data record.
[0063] In another example, this is a mobile electronic device that includes at least one processor, thus operable to perform a comparison of the actual captured motion data with the previously stored, and thus user specific, motion data, and then this is a mobile electronic device that generates a data matching index.
[0064] Therefore, the mobile electronic device may also be configured to make a decision regarding enabling, disabling, triggering or terminating the execution of a particular function of the drug delivery device based on the data matching index, where at least one or some of the above-mentioned method steps of acquiring motion data, comparing the acquired motion data as well as generating the data matching index, and making a decision regarding enabling, disabling, triggering or terminating the execution of a function of the drug delivery device are provided by the mobile electronic device.
[0065] The mobile electronic device may be implemented as a smartphone, a smart watch, a tablet computer, a fitness tracker, or a radio tag, typically carried by a user who wishes to use the drug delivery device.
[0066] According to another example of the authentication system, the electronic circuit includes a circuit communication interface configured to wirelessly communicate with a wireless interface of at least one mobile electronic device. In this example, the electronic circuit is typically implemented in one of the auxiliary device and the drug delivery device. The circuit communication interface may establish a communication link between the electronic circuit of one of the auxiliary device and the drug delivery device and the at least one mobile electronic device. In this manner, the electronic circuit implemented in one of the auxiliary device and the drug delivery device and operable to at least one of enable, disable, trigger, or terminate execution of a function of the drug delivery device may be controlled by the mobile electronic device.
[0067] In this example, this is a mobile electronic device that acquires motion data of the user. A communication link between the electronic circuitry and the at least one mobile electronic device allows the acquired motion data to be transferred and transmitted from the mobile electronic device to the electronic circuitry of the drug delivery device and / or the auxiliary device. Further processing of the motion data can then be performed by the auxiliary device or on-board by the drug delivery device.
[0068] In another example, it can be envisaged that the processing of the motion data, i.e. the comparison of the acquired motion data with the stored user-specific motion data, is performed by the mobile electronic device, and a data matching index derived based on this comparison may be generated by the mobile electronic device and transmitted to the electronic circuitry of the auxiliary device and / or the drug delivery device to enable, disable, trigger or terminate the execution of certain device functions.
[0069] In another example, the decision-making regarding enabling, disabling, triggering or terminating the execution of the functions of the drug delivery device may even be performed by at least one mobile electronic device. Each execution command generated by the mobile electronic device may simply be transmitted to a communication interface of the electronic circuitry of one of the drug delivery device and the auxiliary device via a communication interface of the at least one mobile electronic device. Upon receiving such an execution command, the electronic circuitry of at least one of the electronic units of the auxiliary device and the drug delivery device may then be operable to enable, disable, trigger or terminate the execution of the functions of the drug delivery device accordingly.
[0070] In another example, it is a circuit communication interface operable to receive at least a portion of the motion data acquired by at least one mobile electronic device. In another example, it is a mobile electronic device including at least one of an external electronic device, for example a wearable electronic device such as a smartphone, a smart watch or a fitness tracker, and a wireless tag. The wireless tag may be operable to establish a wireless communication link with other mobile electronic devices or fixed electronic devices.
[0071] At least one of the absolute and relative positions of the wireless tag can be measured, identified and / or tracked by other electronic devices to obtain motion data of a user provided with the wireless tag. In a typical usage scenario, the wireless communication link between the wireless tag and other electronic devices as well as the communication link between the auxiliary device and / or the drug delivery device and the mobile electronic device can be implemented based on electromagnetic ultra-wideband technology.
[0072] According to another example, a processor of the authentication system is operable to enable, disable, trigger or terminate execution of a function of the drug delivery device in response to the data matching index, which may be the same or another processor that compares the acquired motion data with the stored motion data and generates the data matching index.
[0073] In some examples, there may be a sole processor, for example of the auxiliary device, or of the drug delivery device, that performs the comparison between the acquired motion data and the stored motion data. The same processor may also be operable to enable, disable, trigger or terminate the execution of a function of the drug delivery device depending on the data matching index.
[0074] In another example of the authentication system, for example implemented in at least one of the auxiliary device and the drug delivery device and in one mobile electronic device, multiple processors may be provided that are embedded therein, where a first processor may be operable to acquire motion data, the same or another processor may be operable to compare the acquired motion data with stored motion data of a user specific data record, another processor may be operable to generate a data matching index, and yet another processor may be operable to process the data matching index and determine which functions of the drug delivery device are enabled, disabled, triggered or terminated based on the data matching index.
[0075] Multiple processors, which may be distributed among multiple hardware components, e.g., an auxiliary device, a drug delivery device, or any mobile electronic device, are typically operable to communicate with each other, e.g., by establishing respective wireless communication links using respective wireless communication interfaces.
[0076] According to another aspect, the present disclosure relates to a computer program comprising computer readable instructions which, when executed by at least one processor of the aforementioned authentication system, cause the processor to acquire motion data of a user, compare the acquired motion data with stored motion data of a user-specific data record, generate a data matching index indicating the degree of matching between the acquired motion data and the stored motion data, and enable, disable, trigger or terminate performance of a function of a drug delivery device based on the data matching index.
[0077] Typically, the computer program is configured to be executed by at least one or more hardware components of the aforementioned authentication system to perform the aforementioned user authentication method. Up to now, all the features, effects and advantages mentioned above in relation to the user authentication method and authentication system apply equally to the computer program and vice versa.
[0078] The computer program may be executed by multiple hardware components in a distributed hardware environment. Only a part or the whole of the computer readable instructions may be executed by a processor of the electronic circuitry of the auxiliary device, of the drug delivery device, or of the mobile electronic device, or by a processor of a database accessible via a data communication network. In some examples, the computer program may be executed alone, for example by a processor of the electronic circuitry of the auxiliary device, or by the electronic unit of the drug delivery device. In some examples, the computer readable instructions are executed at least in part or in whole by the electronic circuitry and the processor of the mobile electronic device.
[0079] According to another aspect, the present disclosure relates to a set including any one or all of the following: - a drug delivery device provided with an electronic circuit of an authentication system; - an auxiliary device that can be attached to the drug delivery device and that is provided with an electronic circuit of the authentication system as described above; - a mobile electronic device including at least one of the sensors and the communication interface of the authentication system described above.
[0080] In general, the scope of the present disclosure is defined by the content of the claims. The infusion device is not limited to a particular embodiment or example, but includes any combination of elements of the various embodiments or examples. Thus, the present disclosure covers any combination of the claims, as well as any technically possible combination of the features disclosed with respect to the various examples or embodiments.
[0081] In the context of this application, the term "distal" or "distal end" refers to the end of the injection device that faces an injection site on a human or animal. The term "proximal" or "proximal end" refers to the opposite end of the injection device that is furthest from an injection site on a human or animal.
[0082] The terms "drug" or "medicament" are used interchangeably herein to describe a pharmaceutical formulation containing one or more active pharmaceutical ingredients or pharma- ceutically acceptable salts or solvates thereof, and optionally a pharma- ceutically acceptable carrier. An active pharmaceutical ingredient ("API"), in its broadest sense, is a chemical structure that has a biological effect on humans or animals. In pharmacology, drugs or medicines are used to treat, cure, prevent, or diagnose diseases or otherwise improve physical or mental well-being. Drugs or medicines can be used for a limited duration or periodically for chronic disorders.
[0083] As described below, a drug or agent may include at least one API or a combination thereof in various types of formulations for the treatment of one or more diseases. Examples of APIs include small molecules with molecular weights of 500 Da or less, polypeptides, peptides and proteins (e.g., hormones, growth factors, antibodies, antibody fragments and enzymes), carbohydrates and polysaccharides, as well as nucleic acids, double-stranded or single-stranded DNA (including naked and cDNA), RNA, antisense nucleic acids, such as antisense DNA and RNA, small interfering RNA (siRNA), ribozymes, genes and oligonucleotides. Nucleic acids can be incorporated into molecular delivery systems such as vectors, plasmids or liposomes. Mixtures of one or more drugs are also contemplated.
[0084] The drug or agent may be contained in a primary package or "drug container" adapted for use in a drug delivery device. The drug container may be, for example, a cartridge, syringe, reservoir, or other rigid or flexible vessel configured to provide a chamber suitable for storage (e.g., short-term or long-term storage) of one or more drugs. For example, in some cases, the chamber may be designed to store the drug for at least one day (e.g., from one day to at least 30 days). In some cases, the chamber may be designed to store the drug for about one month to about two years. Storage may be at room temperature (e.g., about 20°C) or at refrigerated temperatures (e.g., from about -4°C to about 4°C). In some cases, the drug container may be or include a dual chamber cartridge configured to separately store two or more components of a pharmaceutical formulation to be administered (e.g., an API and a diluent or two different drugs), one in each chamber. In such cases, the two chambers of the dual chamber cartridge may be configured to allow mixing between the two or more components before and / or during administration to the human or animal body. For example, the two chambers may be configured to be in fluid communication with each other (e.g., via a conduit between the two chambers) and to allow mixing of the two components by a user, if desired, prior to administration. Alternatively or additionally, the two chambers may be configured to allow mixing upon administration of the components to the human or animal body.
[0085] The drugs or agents contained in the drug delivery devices described herein can be used for the treatment and / or prevention of many different types of medical disorders. Examples of disorders include, for example, diabetes or complications associated with diabetes, such as diabetic retinopathy, thromboembolic disorders, such as deep vein thromboembolism or pulmonary thromboembolism. Further examples of disorders are acute coronary syndromes (ACS), angina, myocardial infarction, cancer, macular degeneration, inflammation, hay fever, atherosclerosis and / or rheumatoid arthritis. Examples of APIs and drugs are those listed in handbooks such as the Rote Liste 2014, including, but not limited to, main groups 12 (antidiabetic drugs) or 86 (oncology drugs), and the Merck Index 15th Edition.
[0086] Examples of APIs for the treatment and / or prevention of type 1 or type 2 diabetes mellitus or complications of type 1 or type 2 diabetes mellitus include insulin, e.g., human insulin, or an insulin analog or derivative, glucagon-like peptide (GLP-1), a GLP-1 analog or GLP-1 receptor agonist, or an analog or derivative thereof, a dipeptidyl peptidase-4 (DPP4) inhibitor, or a pharma-ceutically acceptable salt or solvate thereof, or any mixture thereof. As used herein, the terms "analog" and "derivative" refer to a polypeptide having a molecular structure that can be derived formally from the structure of a naturally occurring peptide, e.g., that of human insulin, by deleting and / or substituting at least one amino acid residue present in the naturally occurring peptide and / or by adding at least one amino acid residue. The added and / or substituted amino acid residue can be either a codable amino acid residue or other naturally occurring residue, or a purely synthetic amino acid residue. Insulin analogs are also referred to as "insulin receptor ligands". In particular, the term "derivative" refers to a polypeptide having a molecular structure that is formally derivable from the structure of a naturally occurring peptide, e.g., the structure of human insulin, in which one or more organic substituents (e.g., fatty acids) are attached to one or more of the amino acids. Optionally, one or more amino acids found in the naturally occurring peptide may be deleted and / or replaced by other amino acids, including non-codable amino acids, or amino acids, including non-codable amino acids, may be added to the naturally occurring peptide.
[0087] Examples of insulin analogues are Gly(A21), Arg(B31), Arg(B32) human insulin (insulin glargine); Lys(B3), Glu(B29) human insulin (insulin glulisine); Lys(B28), Pro(B29) human insulin (insulin lispro); Asp(B28) human insulin (insulin aspart); human insulin in which the proline in position B28 can be replaced by Asp, Lys, Leu, Val or Ala and in position B29 Lys can be replaced by Pro; Ala(B26) human insulin; Des(B28-B30) human insulin; Des(B27) human insulin and Des(B30) human insulin.
[0088] Examples of insulin derivatives are e.g. B29-N-myristoyl-des(B30) human insulin, Lys(B29)(N-tetradecanoyl)-des(B30) human insulin (insulin detemir, Levemir®); B29-N-palmitoyl-des(B30) human insulin; B29-N-myristoyl human insulin; B29-N-palmitoyl human insulin; B28-N-myristoyl-LysB28ProB29 human insulin; B28-N-palmitoyl-LysB28ProB29 human insulin; B30-N-myristoyl-ThrB29LysB30 human insulin. B29-N-palmitoyl-ThrB29LysB30 human insulin; B29-N-(N-palmitoyl-gamma-glutamyl)-des(B30) human insulin, B29-N-omega-carboxypentadecanoyl-gamma-L-glutamyl-des(B30) human insulin (insulin degludec, Tresiba®); B29-N-(N-lithocholyl-gamma-glutamyl)-des(B30) human insulin; B29-N-(ω-carboxyheptadecanoyl)-des(B30) human insulin and B29-N-(ω-carboxyheptadecanoyl) human insulin.
[0089] Examples of GLP-1, GLP-1 analogs and GLP-1 receptor agonists are e.g. lixisenatide (Lyxumia®), exenatide (exendin-4, Byetta®, Bydureon®, a 39 amino acid peptide produced by the salivary glands of the flatfish), liraglutide (Victoza®), semaglutide, taspoglutide, albiglutide (Syncria®), dulaglutide (Trulicity®), rExendin-4, CJC-1134-PC, PB-1023, TTP-054, langrenatide / HM-11260C, HM-15211, CM-3, GLP-1 Erigen, ORMD-0901, NN-9423, NN-9709, NN-9924, NN-9926, NN-9927, Nodexene, Viador-GLP-1, CVX-096, ZYOG-1, ZYD-1, GSK-2374697, DA-3091, MAR-701, MAR709, ZP-2929, ZP- 3022, ZP-DI-70, TT-401 (pegapamoditide), BHM-034, MOD-6030, CAM-2036, DA-15864, ARI-2651, ARI-2255, tirzepatide (LY3298176), bamadutide (SAR425899) exenatide-XTEN and glucagon-Xten.
[0090] Examples of oligonucleotides include, for example: mipomersen sodium (Kynamro®), a cholesterol-lowering antisense therapeutic for the treatment of familial hypercholesterolemia, or RG012 for the treatment of Alport Syndrome.
[0091] Examples of DPP4 inhibitors include linagliptin, vildagliptin, sitagliptin, denagliptin, saxagliptin, and berberine.
[0092] Examples of hormones include pituitary or hypothalamic hormones or regulatory active peptides such as gonadotropins (follitropin, lutropin, chorion gonadotropin, menotropin), somatropin (somatropin), desmopressin, terlipressin, gonadorelin, triptorelin, leuprorelin, buserelin, nafarelin and goserelin, and their antagonists.
[0093] Examples of polysaccharides include glycosaminoglycans, hyaluronic acid, heparin, low molecular weight heparin, very low molecular weight heparin or derivatives thereof or sulfated forms of the above polysaccharides, such as polysulfated forms, and / or pharma- ceutically acceptable salts thereof. An example of a pharma-ceutically acceptable salt of polysulfated low molecular weight heparin is enoxaparin sodium. An example of a hyaluronic acid derivative is sodium hyaluronate Hylan GF 20 (Synvisc®).
[0094] The term "antibody" as used herein refers to an immunoglobulin molecule or an antigen-binding portion thereof. Examples of antigen-binding portions of an immunoglobulin molecule include F(ab) and F(ab')2 fragments that retain the ability to bind to an antigen. The antibody may be a polyclonal antibody, a monoclonal antibody, a recombinant antibody, a chimeric antibody, a deimmunized or humanized antibody, a fully human antibody, a non-human (e.g., murine) antibody, or a single chain antibody. In some embodiments, the antibody has effector function and is capable of fixing complement. In some embodiments, the antibody has reduced or no binding ability to Fc receptors. For example, the antibody may be an isotype or subtype, an antibody fragment, or a mutant that does not support binding to Fc receptors, e.g., with a mutation or deletion of the Fc receptor binding region. The term antibody also includes antigen-binding molecules based on tetravalent bispecific tandem immunoglobulins (TBTI) and / or dual variable region antibody-like binding proteins (CODV) with crossover binding region orientation.
[0095] The term "fragment" or "antibody fragment" refers to a polypeptide (e.g., antibody heavy and / or light chain polypeptide) derived from an antibody polypeptide molecule that does not include the full-length antibody polypeptide but comprises at least a portion of the full-length antibody polypeptide that is still capable of binding to an antigen. An antibody fragment may include truncated portions of a full-length antibody polypeptide, but the term is not limited to such truncated fragments. Antibody fragments useful in the present invention include, for example, Fab fragments, F(ab')2 fragments, scFv (single-chain Fv) fragments, linear antibodies, monospecific or multispecific antibody fragments, such as bispecific, trispecific, tetraspecific and multispecific antibodies (e.g., diabodies, triabodies, tetrabodies), monovalent or multivalent antibody fragments, such as bivalent, trivalent, tetravalent and multivalent antibodies, minibodies, chelating recombinant antibodies, tribodies or bibodies, intrabodies, nanobodies, small modular immunopharmaceuticals (SMIPs), binding domain immunoglobulin fusion proteins, camelized antibodies and VHH-containing antibodies. Additional examples of antigen-binding antibody fragments are known in the art.
[0096] The term "complementarity determining region" or "CDR" refers to short polypeptide sequences in the variable regions of both heavy and light chain polypeptides that are primarily responsible for mediating specific antigen recognition. The term "framework region" refers to amino acid sequences in the variable regions of both heavy and light chain polypeptides that are not CDR sequences and that are primarily responsible for maintaining the proper arrangement of the CDR sequences to allow antigen binding. Although the framework region itself typically does not directly participate in antigen binding, as is known in the art, certain residues in the framework region of a particular antibody may be directly involved in antigen binding or may affect the ability of one or more amino acids in the CDR to interact with the antigen.
[0097] Examples of antibodies are anti-PCSK-9 mAb (e.g., alirocumab), anti-IL-6 mAb (e.g., sarilumab), and anti-IL-4 mAb (e.g., dupilumab).
[0098] Pharmaceutically acceptable salts of any of the APIs described herein are contemplated for use in the drug or medicament in the drug delivery device. Pharmaceutically acceptable salts include, for example, acid addition salts and base salts.
[0099] Those skilled in the art will appreciate that modifications (additions and / or removals) of the various components of the APIs, formulations, devices, methods, systems and embodiments described herein may be made without departing from the full scope and spirit of the invention, which encompasses such modifications and all equivalents thereof.
[0100] Furthermore, it will be apparent to those skilled in the art that various modifications and variations can be made to the present disclosure without departing from the scope of the present disclosure. Furthermore, any reference numbers used in the appended claims shall not be construed as limiting the scope of the present disclosure.
[0101] In the following, various examples of methods for authenticating a user to use a drug delivery device, as well as various hardware configurations including various implementations of the authentication system, electronic circuitry, drug delivery device, auxiliary device, and mobile electronic device, are described in more detail with reference to the following drawings: [Brief description of the drawings]
[0102] [Figure 1] 1 illustrates an example of a drug delivery device implemented as a pen injection device. [Diagram 2] 1 shows an injection device with an auxiliary device. [Diagram 3] 1 shows a longitudinal cross-section of an example of a pen injection device. [Figure 4] 1 illustrates various hardware components of the authentication system. [Diagram 5] 1 illustrates a block diagram of an example of an authentication system. [Figure 6] 1 illustrates a block diagram of another implementation of an authentication system. [Figure 7]1 shows a block diagram of another implementation of an authentication system. [Figure 8] 1 illustrates a block diagram in which an auxiliary device attached to an infusion device is operable to communicate with at least one or more mobile electronic devices. [Figure 9] 1 illustrates wireless communication between a mobile electronic device and an electronic unit of a drug delivery device. [Figure 10] 2 shows a schematic representation of different users being assigned different data records; [Figure 11] 1 shows a flow chart of a method for authenticating a user for use of a drug delivery device. [Figure 12] 4 shows a comparison of captured and stored motion data. [Figure 13] 4 shows a flowchart of another implementation of a method for authenticating a user. [Figure 14] 4 shows another flow chart of a method for authenticating a user. [Figure 15] 4 shows another flow chart of a user authentication method. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0103] In Figures 1 to 3 an example of a drug delivery device 1 implemented as an injection device is shown diagrammatically. The drug delivery device 1 comprises an elongated housing 16, for example of cylindrical or tubular form. The housing 16 extends along a length direction. Towards the distal direction 2, and thus towards the distal end, an injection needle 19 can be attached to a reservoir housing 18 forming or constituting the distal part of the housing of the injection device 10. Towards the proximal direction 3, and thus at the proximal end of the injection device 10, a dose dial 12 and / or a dose button 14 are provided for setting the dose of medicament 8 and expelling the dose, respectively.
[0104] The container housing 18 is configured and shaped to receive the medicament container 5. The medicament container 5 may include a tubular barrel. The medicament container 5, for example implemented as a standard cartridge, may be sealed towards the proximal direction 3 by a movable stopper 6. The distal end of the medicament container 5 is typically sealed by a pierceable seal 7. The outlet of the medicament container 5 is thus covered by the pierceable seal, which is secured to the top of the medicament container 5, for example by a crimp cap (not shown).
[0105] The injection device 10 further comprises a drive mechanism at 11. The drive mechanism 11 comprises a piston rod 24 which is elongate and extends along the length of the housing 16. Inside the housing 16 an inner body 15 may be provided which serves as a support or mount for the drive mechanism 11. The piston rod 24 may be threadably engaged with the inner body 15. Thus, rotation of the piston rod 24 guided by the drive mechanism 11 may result in forward movement of the piston rod 24 relative to the inner body 15 and relative to the housing 16, thereby urging or moving the stopper 6 in the distal direction 2 relative to the medicament container 5. In this way, a dose of medication 8 can be expelled from the outlet of the medication container 5. Typically, the seal 7 is pierceable by a double-tipped injection needle 19 as shown in Figures 4 and 5. The injection needle, for example comprising a threaded needle hub, can be detachably or releasably connected to the distal end of the container housing.
[0106] The drive mechanism 11 typically includes a dial sleeve 21 that is at least partially visible through a window 20 provided in the housing 16 of the injection device 10. When setting a dose, the dial sleeve 21 undergoes a rotational movement. Thus, dose display numbers may be displayed in ascending order in the window 20, indicating the size of the dose currently being set. The drive mechanism 11 further includes a drive sleeve 22. The drive sleeve 22 is operatively connected or coupled to a piston rod when the drive mechanism 11 is in a dose delivery or dose injection mode. Pressing the dose button 14 may initiate a rotation of the drive sleeve 22, which is operatively connected to the piston rod 24 by actuation of a clutch, inducing a dose delivery rotation and a distal longitudinal forward movement of the piston rod 24.
[0107] The piston rod 24 is provided with a pressure piece 25 at its distal end. The pressure piece 25 is typically rotatably supported at the distal end of the piston rod 24. The pressure piece 25 transmits the distal thrust generated by the piston rod 24 to a thrust receiving surface at the proximal end of the stopper 6. In some examples, the drive mechanism 11 is provided with a mechanical energy store such as a spring. The mechanical energy store may be biased during or at the time of dose setting. By pressing the dose button 14, mechanical energy stored in the mechanical energy store is released to provide a driving torque or force for advancing the piston 24 in the distal direction 2 to expel a dose of the drug 8. In other examples, the drive mechanism 11 does not have a mechanical energy store. Here, substantially all of the force applied by the user to the dose button 14 is converted into the driving force required to move the piston rod 24 in the distal direction.
[0108] Exemplary drug delivery devices may include needle-based injection systems as described in Table 1 of Section 5.2 of ISO 11608-1:2014(E). As described in ISO 11608-1:2014(E), needle-based injection systems may be broadly categorized into multi-dose container systems and single-dose (with partial or complete evacuation) container systems. The container may be an exchangeable container or an integrated non-exchangeable container.
[0109] As further described in ISO 11608-1:2014(E), a multi-dose container system may include a needle-based injection device with an exchangeable container. In such a system, each container holds multiple doses, the size of which may be fixed or variable (pre-set by the user). Another multi-dose container system may include a needle-based injection device integrated with a non-exchangeable container. In such a system, each container holds multiple doses, the size of which may be fixed or variable (pre-set by the user).
[0110] The drive mechanism 11 described above is merely an example for one of various configurations of drive mechanisms that can be generally implemented in disposable or reusable pen-type injectors. The drive mechanism described above is described in more detail, for example, in WO 2004 / 078239 A1, WO 2004 / 078240 A1, or WO 2004 / 078241 A1, which are incorporated herein by reference in their entirety. Another example of the drive mechanism 11 implemented in the injection device 10 can be found in WO 2014 / 033195 A1 or WO 2014 / 033197 A1, which are incorporated herein by reference in their entirety. The drive mechanism discussed in WO 2014 / 033195 A1 is a reusable drive mechanism. The drive mechanism disclosed in WO 2014 / 033197 A1 is an example of a disposable drive mechanism that does not have a reset function.
[0111] In Fig. 4, various components of an authentication system 1000, as described below, are shown diagrammatically. The infusion device 10 may comprise an electronic unit 60. The electronic circuitry 60 typically comprises an electronic circuit 61. The electronic circuitry 61 comprises a processor 62 and a battery 63. Furthermore, in a typical example, the electronic unit 60 embedded or integrated in the infusion device 10 also comprises a storage 64, a sensor 65, a communication interface 66, a proximity sensor 67 and a signal unit 68.
[0112] As shown in FIG. 4, the electronic unit 60 may be disposed inside the dose dial 12. The dose button 14 may close a receptacle of the dose dial 12, which is sized to accommodate at least a portion of the electronic unit 60. As further shown in FIG. 4, the authentication system 1000 may include at least one mobile electronic device 80, 100, 120. The mobile electronic device 80 may be implemented as an external electronic device. It may include a smartphone. The smartphone 80 typically includes an input 89 and a display 91. Here, the input 89 may be integrated into the display 91, which is then implemented as a touch-sensitive display. In another example, the mobile electronic device 100 is implemented as a wearable electronic device. The wearable electronic device 100 may include a strap 112 or a wristband, by which the mobile electronic device 100 may be attached, for example, to a user's wrist or hand. The mobile electronic device 100 may be implemented as a smart watch.
[0113] Typically, the mobile electronic device includes a housing 110 that houses an electronic circuit 101 comprising a processor 102, a battery 103, a storage 104, a sensor 105, a communication interface 106, a proximity sensor 107, and a signal unit 108. The housing 110 may be closed or covered by a display 111. In some examples, the mobile electronic device 100 is mountable on the wrist or arm of a user 4. In other examples, the mobile electronic device 100' may be mounted on other parts of the user's body. As an example, the mobile electronic device 100' may be implemented as a belt or integrated into the user's belt.
[0114] The mobile electronic device 120 may be implemented as a radio tag. The radio tag 120 may include a housing 129. Typically, the radio tag 120 includes an electronic circuit 121, which may include, for example, a printed circuit board. The electronic circuit 121 may include at least one of a processor 122, a battery 123, a sensor 125, a communication interface 126, a proximity sensor 127, and a signal unit 128. The mobile electronic device 120 is typically carried by a user 4.
[0115] In some examples, the mobile electronic device 120 may be permanently attached to a user's possession, such as a key. In another example, the mobile electronic device 120 may be attached to the drug delivery device 1.
[0116] 5 , the drug delivery device 1 and thus the injection device 10 further comprises a movable part 26. The movable part 26 may be implemented in the drive mechanism 11. The movable part of the drive mechanism 11 may form or constitute the movable part 26. The movement or position of the movable part 26 of the drive mechanism 11 may be detected or tracked by an electronic unit 60 of the injection device 10.
[0117] The detectable position or orientation of the movable part 26 may indicate the current state or configuration of the injection device 10. The position of the movable part 26 along the length may directly indicate the remaining amount of medicament 8 provided in the medicament container 5. By detecting or quantitatively measuring the position and / or orientation of the movable part 26, the electronic unit 60 may accumulate device specific information regarding the temporal state or configuration of the injection device. In this manner, the electronic unit 60 may be configured to collect and / or accumulate data indicative of the operational state or usage history of the injection device 10. The electronic unit 60 may collect data such as a dosing or ejection history, including information regarding the amount of medicament ejected on a particular date and / or time.
[0118] The injection device 10 may further comprise an electromechanical interlock 30. The electromechanical interlock 30 may be integrated into the drive mechanism 11. The interlock 30 may be operable by an electronic unit 60 of the injection device 10.
[0119] 5, the injection device 10 comprises an electronic unit 60. The electronic unit 60 comprises a printed electronic circuit 61, a processor 62, a battery 63, a storage 64, at least one sensor 65, a communication interface 66, a proximity sensor 67 and / or a signal unit 68.
[0120] The signal unit 68 is configured to generate a user-perceivable signal. It may include a speaker for generating an audio signal. It may include a display for visualizing information to a user. It may include a flashing lamp, such as an LED. It may include multiple LEDs or light sources configured to generate light indications or light pulses of different colors and / or durations. The signal unit 68 may also include a buzzer or similar electromechanical unit that generates a vibration or other tactilely detectable signal.
[0121] The communication interface 66 is configured to communicate with other communication interfaces 86 of the mobile electronic device 80. Alternatively or additionally, the communication interface 66 is configured to communicate with the database 140 via the network 130. The communication interface 66 may access the database 140 and / or the network 130 by means of a specific access point 131. The communication between the communication interface 66 and the network 130 is typically implemented as a wireless communication link.
[0122] The mobile electronic device 80 may be implemented as a smartphone. It includes an electronic circuit 81, a processor 82, a battery 83, a storage 84, a sensor 85, a communication interface 86, a proximity sensor 87, a signal unit 88, a user operable input 89, a housing 90, and a display 91. The mobile electronic device 80 may be configured to communicate with a satellite positioning system 95 to store global or regional location information. Typically, the communication interface 86 of the mobile electronic device 80 is configured to communicate with a network 130 by at least one of several access points. It may communicate with a database 140 to store or receive requested data from the database 140.
[0123] In a further example of an authentication system 1000 as shown in Fig. 6, not only one mobile electronic device 80 but also another mobile electronic device 100, for example in the form of a smart watch or a fitness tracker, is provided. The mobile electronic device 100 also includes at least one of an electronic circuit 101, a processor 102, a battery 103, a storage 104, a sensor 105, a communication interface 106, a proximity sensor 107, and a signal unit 108. All these components may be enclosed in a housing 110. The signal unit 108 may include a display 111. The signal unit 108 may be implemented in the same or similar manner as the signal unit 68 described above with respect to the electronic unit 60.
[0124] The mobile electronic device 100 is operable to communicate with the network 130 and the database 140 via the communication interface 106. The mobile electronic device 100 may also wirelessly communicate with the electronic unit 60 of the drug delivery device 1 as well as with the communication interface 86 of the mobile electronic device 80. In a further example, the mobile electronic device 100 may also communicate directly or indirectly with a satellite positioning system 95 to obtain geographical location data, for example to obtain absolute or relative location data of the mobile electronic device 100.
[0125] In another example, as shown in Fig. 7, the drug delivery device 1 may not include an electronic unit 60 as described above. The injection device 10 and / or the drive mechanism 11 may be all mechanically implemented. Here, the injection device 10 may comprise an auxiliary device 40. The auxiliary device 40 typically includes a fastener 49 for removably fastening or fixing the auxiliary device 40 to the housing 16 of the injection device 10.
[0126] The auxiliary device 40 includes a signaling unit 48. The signaling unit 48 may include one of a light source such as a flashing lamp, a display, a speaker, and a vibration generating unit. When implemented as a display or a flashing lamp, it may provide visual information or a visual warning to the user. Typically, the auxiliary device 40 also includes at least one of an electronic circuit 41, a processor 42, a battery 43, a storage 44, a sensor 45, a communication interface 46, and a proximity sensor 47. Typically, the auxiliary device 40 is operatively connected or coupled to the interlock 30 of the drive mechanism 11 when attached to the injection device 10.
[0127] Additionally or alternatively, the auxiliary device 40, and in particular its sensor 45, may be operatively connected or coupled to the movable part 26 of the drive mechanism 11. In this manner, the auxiliary device 40 is operable to obtain or acquire information regarding a temporal state of the drive mechanism 11, which reflects the position, orientation or movement of the movable part 26. Similarly, and as previously described with respect to the electronic unit 60 or the mobile electronic device 100, the auxiliary device 40 is operable to wirelessly communicate with the mobile electronic devices 80, 100, 120.
[0128] The auxiliary device 40 may also be operable to communicate directly with the database 140 via the communication interface 130. As further shown in Figure 8, the auxiliary device 40 and / or the electronic unit 60 of the injection device 10 may be operable to communicate with at least one or several of the mobile electronic devices 80, 100, 120. A wireless communication link may be established between at least two of the electronic unit 60, the auxiliary device 40, the mobile electronic device 80, the mobile electronic device 100, the mobile electronic device 120. Furthermore, the mobile electronic devices 80, 100, 120 may communicate between each other.
[0129] A first wireless communication link may be established between at least one of the electronic unit 60 and the auxiliary device 40 and one of the mobile electronic devices 80, 100, 120. Another wireless communication link may be established between the electronic unit 60, the auxiliary device 40, any of the mobile electronic devices 80, 100, 120 and the communication network 130 and / or the database 140.
[0130] The sensor 45, 65, 85, 105, 125 may be implemented as one of an acceleration sensor, a rotation sensor, a position sensor, a distance sensor, and a physiological data capture sensor. The implementation of the physiological data capture sensor is typically provided in the wearable electronic device 80, 100, 120. The sensor 45, 64, 85, 105, 125 allows obtaining motion data of the corresponding electronic circuit 41, 61, 81, 101, 121.
[0131] Each motion data may be stored in an associated storage 44, 64, 84, 104, 124 of the respective electronic circuit 61. The acquired motion data may also be communicated and / or transmitted to other electronic circuits 41, 61, 81, 101, 121 via a communication interface 46, 66, 86, 108, 126. The motion data of the user 4 may also be acquired by establishing a communication link with a database 140 via a network 130. The motion data collected by any of the sensors 45, 65, 85, 105, 125 may be stored in the database 140 and made available to any other electronic circuits 41, 61, 81, 101, 121.
[0132] Furthermore, at least a portion of the motion data may be acquired or collected by a first mobile electronic device 100 , 120 carried by, for example, a user 4 .
[0133] Another portion of the motion data may be acquired or collected by sensors 44, 65 attached to or incorporated in the infusion device 10. Different portions of the motion data may be combined or collected through a wireless communication link between the respective mobile electronic device 80, 100, 110 and at least one of the auxiliary device 40 and the electronic unit 60. Any of the wireless communication interfaces 46, 66, 86, 106, 126 may be operable to transmit and receive (transmit and / or receive) in a particular frequency range according to a particular transmission protocol. A wireless communication interface may include multiple communication circuits, each of which transmits and receives in different frequency ranges and / or according to different wireless transmission protocols.
[0134] At least one or some of the wireless communication interfaces 46, 66, 86, 106, 126 described herein include at least one RFID communication circuit (Radio Frequency Identification). The wireless communication interface may include an NFC (Short Range Communication) circuit, such as an active NFC circuit (preferably with an associated power source, e.g. a battery such as a printed battery) or a passive NFC circuit (preferably without a power source powering the circuit). The wireless communication interface may include at least one Bluetooth and / or BLE (Bluetooth Low Energy) communication circuit. The wireless communication unit may include at least one WiFi (e.g. Wireless Fidelity according to IEEE 802.11 standard / protocol) communication circuit. Alternatively or additionally, the wireless communication unit may include a magnetometer / compass circuit for detecting changes in a magnetic field, e.g. changes caused by a wireless communication circuit of a component of the drug delivery device.
[0135] In some examples, at least one or some of the wireless communication interfaces 46, 66, 86, 106, 126 described herein are implemented as UWB (Ultra Wideband) communication interfaces.
[0136] At least one of the wireless communication interfaces 46, 66, 86, 106, 126 is configured to generate an UWB signal that enables communication with another one of the wireless communication interfaces 46, 66, 86, 106, 126. The UWB signal includes an ultra-short RF pulse (e.g., less than 1 ns) that spans a large portion of the radio spectrum (e.g., a bandwidth greater than 500 MHz or 20% of the center frequency, whichever is lower) at an ultra-low energy level. The operating frequency is selected according to one or more national and federal regulations. For example, a frequency band that is widely accepted internationally is about 6.5 GHz to about 8 GHz. In some implementations, the UWB signal includes a UWB standard that is widely accepted and available in smartphones from major vendors, thereby allowing a standard smartphone to be used as the mobile electronic device 80.
[0137] In some implementations, the UWB communication includes a proprietary UWB protocol. The proprietary UWB protocol uses coding that consists of a combination of time modulation, signal waveform modulation, and amplitude modulation. A proprietary UWB device (e.g., a USB dongle for a smartphone) can be used as the wireless tag 120. The transmission of the UWB signal can be triggered by a user action.
[0138] In some examples, as shown in Fig. 9, wireless communication between the injection device 10 and / or the auxiliary device 40 and / or the mobile electronic device 80, 100, 120 provides a pager functionality. For example, if the communication link is established using UWB communication protocol, it can in principle provide precise location tracking of the electronic unit 60. Thus, the position of the drug delivery device 10 and / or the auxiliary device 40 can be precisely identified or measured with an accuracy of just a few centimeters or even millimeters.
[0139] Additionally or alternatively, the wireless communication link may also provide an identification and / or quantitative measurement of at least one of the distance and relative position between the first electronic circuit and the second electronic circuit, e.g., the distance and / or relative position between the injection device 10 and one of the mobile electronic devices 80, 100, 120.
[0140] As shown in Fig. 9, the mobile electronic device 80 includes a communication interface 86 with an antenna 96, a ranging unit 97, and a location unit 98. The antenna 96, implemented for example as a UWB antenna, is operable to communicate with the electronic unit 60 or with the electronic circuit 41 of the auxiliary device 40. In some examples, the antenna 96 and thus the communication interface 86 is operable to wirelessly communicate with the communication interface 66 and / or with the proximity sensor 67 of the electronic unit 60. The UWB antenna 96 is not limited to being implemented within the mobile electronic device 80. The antenna 96, ranging unit 97, and location unit 98 configured to generate and / or process UWB signals for accurate position and distance measurement between any two mobile electronic devices 80, 100, 120 and / or electronic circuits 41, 61 can be implemented in any of the communication interfaces 46, 66, 106, 126 as well.
[0141] The antenna 96 may be configured such that the time characteristics of the UWB signal are constant across the frequency spectrum, resulting in minimal pulse distortion. The antenna 96 may exhibit a fairly flat frequency spectrum, resulting in wide pulses with very little resonant distortion. The antenna 96 may be integrated into any one of the communication interfaces 46, 66, 86, 106, 126, typically near the surface of the respective housing, thereby minimizing signal attenuation. A possible implementation of the antenna 96 is the integration of a chip antenna or a conductive layer acting as the antenna 96 into one of the plastic components of any one of the injection device 10, the auxiliary device 40, or any one of the mobile electronic devices 80, 100, 120. The counterpart communication interface 46, 66, 86, 106, 126 operable to communicate with the antenna 96 may be configured to constantly or intermittently wait for incoming data packets transmitted by the antenna 96.
[0142] A ranging unit 97 operatively coupled to the antenna 96 may be capable of deriving or quantitatively measuring the distance between the electronic unit 60 and the communication interface 86, and thus between the electronic unit 60 and the device 80, based on signal dispersion, time-of-flight measurements, dynamic or static triangulation techniques, or any other commonly available distance or position measurement scheme compatible with the wireless communication protocol in question.
[0143] The antenna 96 may be implemented as an array antenna that can determine from which direction a signal or a response signal from the electronic unit 60 is received. A wireless communication link between the mobile electronic device 80 and one of the electronic unit 60 and the auxiliary device 40 can provide the direction and therefore the relative position as well as the distance, e.g. 1.5 m, between the devices 10, 40, 80, e.g. in the form of a visible symbol on the display 91 of the mobile electronic device 80, thus assisting the user 4 to find or look for the electronic unit 60 if said device is lost or if the user does not know at the moment where the infusion device 10 is located.
[0144] In Fig. 10, a data record 250 for a first person 4 and another data record 250' for another person 4' are shown. The data records 250, 250' contain motion data 251, 251'. The motion data 251 includes gesture data 252 and / or motion patterns 254 of the user 4. The gesture data 252 is characteristic of a particular movement or gesture made or performed by the user 4, for example the way the user walks or the way the user picks up the device.
[0145] The motion pattern 254 may be characteristic of or indicative of a motion profile of the relevant user 4. The motion pattern 254 may include information about the user's habits. For example, the motion pattern 254 may indicate that a particular user A is at home on a particular day of the week and is in the house for a particular time, e.g., at night.
[0146] The motion pattern 254 may include a typical movement profile and may provide a mapping of the user's location over time. Optionally, the data record 250 may also include a user identification 256. The user identification 256 may include a unique identification name of the user. The data record 250 may be permanently updated since the user 4 is equipped with a mobile electronic device 80, 100, 120 that is not capable of capturing and / or obtaining respective motion or movement data over a period of time.
[0147] The data record 250 includes motion data 251 and may be stored in any of the aforementioned storages 44, 64, 84, 104, 124. This may be made available upon request, for example, to the authentication system 1000 to compare actual or newly acquired motion data 261 to previously stored motion data 251 to identify or derive a data matching index 270.
[0148] 10, the other user B includes another data record 250', which may be constructed in the same manner as data record 250. Data record 250' also includes gesture data 252', motion patterns 254', and optionally user identification information 256'. Motion data 251 is characteristic of the first user 4, and motion data 251' is characteristic of the other user 4'.
[0149] As further shown in Figure 11, when deploying the drug delivery device 1 and / or auxiliary device 40 to a particular user 4, the delivery device 1 is assigned to user A in step 200. Once the authentication system 1000 is deployed, motion data 251 of user A is acquired over time or obtained from database 140. In step 202, the user-specific data record 250 in question is stored in one of storages 44, 64, 84, 104, 124 and can be made available upon request.
[0150] In a next step 204, when the user 4 attempts to use the drug delivery device 1, actual or recent motion data 261 is acquired or derived from the movements of the user 4 as shown in Fig. 12. The acquisition of the actual motion data 261 is performed, for example, by at least one of the aforementioned sensors 45, 65, 85, 105, 125, or the respective motion data 261 may be acquired or obtained directly or indirectly, for example, from the database 140, via wireless communication provided by one of the aforementioned communication interfaces 46, 66, 86, 106, 126.
[0151] In a next step 206, the actual captured motion data 261 is compared to previously stored motion data 251 of the stored data record 250 assigned to the user 4. Thus, the recently captured motion data 261 is compared to the previously stored motion data 251. Here, the stored gesture data 252 can be compared to the actual recorded or captured gesture data 262. Additionally or alternatively, the actual captured motion pattern or motion profile 264 can be compared to the previously stored motion pattern 254.
[0152] In step 208, a data matching index 270 is generated by the comparison, thus identifying whether the captured motion data of the user 4 matches the previously stored motion data of the user to whom the drug delivery device 1 is assigned. If there is a high degree of matching between the acquired motion data 261 and the stored motion data 251, then certain device functions may be enabled, disabled, triggered or terminated. In general, various device functions are provided that may be enabled, disabled, triggered or terminated once a user is identified as authorized to use the drug delivery device.
[0153] When the degree of data matching is high, for example, dosage setting of the infusion device may be enabled, an interlock may be disabled, a user guidance routine may be triggered, and / or the standby mode of the infusion device may be terminated.
[0154] At the same time, for example, if a poor match is found between the acquired motion data 261 and the previously stored motion data 251, an interlock may be activated or enabled and another authentication routine may be triggered, whereby the user may have to manually authorize himself / herself through other authentication methods of the infusion device or mobile electronic device. In another scenario, if there is a poor data match, the standby mode of the infusion device 10 and / or the auxiliary device 40 may be maintained.
[0155] In some examples, an optional user ID 266 may be obtained from the user and compared to a stored user ID 256 in the user's data record. Comparing user IDs may require the user to manually authenticate at one of the mobile electronic devices 80, 100, 120, for example by entering a code, by fingerprint recognition, or by a camera-based face recognition procedure.
[0156] Additionally, the captured motion data may also include physiological data of the user 4. The respective physiological data may also be stored in the data record 250. The physiological data may include at least one of the user's heart rate, respiration rate, blood pressure profile, oxygen saturation, or another measurable physiological parameter, which may essentially be stored in the data record 250. Measurement of such physiological data by the sensors 85, 105, 125 of the mobile electronic device 80, 100, 120 may enable a comparison to be made between the stored physiological data and the actually measured physiological data, thus allowing identification of the user of the mobile electronic device 80, 100, 120.
[0157] In Fig. 13 an example of a method for authenticating a user to use a drug delivery device is described. In step 300, motion data of a user 4 is captured or acquired by using a mobile electronic device 80, 100, 120 or by an electronic circuit 41 of an auxiliary device 40 and / or by an electronic circuit 61 of an electronic unit 60 integrated in an injection device 10. The captured motion data 261 is then compared with previously stored motion data 251 of a user 4 authorized to use the drug delivery device 1. This comparison is performed in step 302. In the next step 304, the comparison result is evaluated and a data matching index 270 is generated. In step 304, the data matching index indicative of a match between the previously stored motion data and the actually captured motion data 261 is evaluated and analyzed.
[0158] If the match is poor, the method continues to step 306, where certain device functions are, for example, disabled. As a next step 380, the authentication and authorization method then continues to initiate a user request. However, the user is given another possibility to authenticate in front of the drug delivery device. In step 308, the user may be prompted to perform a manual authentication procedure, for example by entering a code into one of the mobile electronic devices 80, 100, 120. If the user enters the code correctly and therefore gives the appropriate authorization, the method continues to step 312, where the respective device function is enabled or triggered.
[0159] Optionally, or additionally, the captured motion data may be used to modify the stored data records in step 314, particularly if the data matching index does not explicitly lead to approval or disapproval of enabling or disabling of device functionality. In this way, the method is self-learning and can automatically adjust to changing user habits. If, in step 310, the user fails to authenticate with the infusion device 10 or with any of the electronic devices 80, 100, 120, the device functionality may remain disabled in step 316.
[0160] Generally, if at step 304 the captured motion data 261 matches the previously stored motion data 251 of the user-specific data record 250, the method continues directly to step 312. Thus, if the captured or captured motion data 261 matches the previously stored motion data 251, the respective device function is enabled or triggered without requiring any further authentication of the user 4. Here, the user 4 may not even be aware that he or she unlocks or activates the device function simply by tracking or recording one of its gestures and / or its motion patterns. In this way, user authentication is simplified and may be smoothly integrated into the user's daily life, and may not require any active interaction with the user 4.
[0161] Another flow chart of a method for authenticating a user for using a drug delivery device is illustrated in Fig. 14. Here, in a first step 400, the user may be prompted to perform a drug delivery procedure, e.g. an injection procedure, by a software routine in one of the mobile electronic devices 80, 100, 120 or in the auxiliary device 40. In a next step 402, motion capture or acquisition of motion data may be activated in at least one of the electronic circuit 41, the electronic unit 60 and / or one of the mobile electronic devices 80, 100, 120.
[0162] In a next step 404, the user 4 may for example pick up the drug delivery device 1. Now, the motion sensor 65 implemented in the electronic unit 60 or other motion detector or sensor 45 integrated in the auxiliary device 40 and attached to the drug delivery device 1 starts to capture or acquire the respective motion data in step 406. In step 408, the motion data thus acquired is evaluated and / or analyzed. Now, in step 408, the actually acquired motion data 261 is compared with the previously stored motion data 251 of users authorized to use the drug delivery device 1.
[0163] If in a next step 410 the user is recognised as an authenticated or authorised user to use the drug delivery device 1, a user support routine may be triggered on the auxiliary device 40 or by the electronic unit 60 of the drug delivery device 1. For example, the drug delivery device and / or the auxiliary device 40 may be switched from a standby mode to an active mode. Optionally, by means of a communication link with at least one of the mobile electronic devices 80, 100, 120, a user assistance routine may be triggered to assist the user in performing the drug delivery procedure.
[0164] If user recognition fails in step 410, for example due to a poor match between the acquired motion data 261 and the stored motion data 251, the procedure may continue with entering a user dialogue in step 414. Certain device functions may be disabled and the user 4 may be prompted to authenticate himself, for example via one of the mobile electronic devices 80, 100, 120 or by interaction with the auxiliary device 40. Here, the user 4 may be prompted to enter a code or to perform any other authentication routine, for example fingerprint detection or face recognition.
[0165] In the flow chart of Fig. 15, another implementation of the method for authenticating a user for using a drug delivery device 1 is shown diagrammatically. In a first step 500, the user is reminded to perform an injection procedure and to follow a predefined injection schedule. Then, in step 502, the user picks up the injection device 10. In a next step, the injection device 1, in particular its electronic unit 60, is connected with the mobile electronic device 80, 100, 120 of the user 4. User motion data 251, 261, e.g. the user's motion profile or motion pattern 254, 264, previously or recently collected and acquired by the mobile electronic device 80, 100, 120, is provided to the electronic unit 60 of the injection device 10.
[0166] This may be provided by a wireless communication link between the electronic unit 60 and at least one of the mobile electronic devices 80, 100, 120. The motion data 251, 261 previously or recently acquired by at least one of the mobile electronic devices 80, 100, 120 is then provided to the electronic unit 60 of the drug delivery device 1 for further evaluation in step 508, similar to the method described above. The electronic unit 60, in particular its processor 62, may then at least one of enabling, disabling, triggering or terminating the execution of at least one function of the drug delivery device. In this implementation, the electronic unit 60 of the injection device 10 may not have a sensor 65 or a proximity sensor 67. The respective motion data capable of characterizing the user 4 of the injection device may be obtained through a wireless communication link between the electronic unit 60 and any one of the mobile electronic devices 80, 100, 120.
[0167] In yet another implementation of the method, it is also possible to envisage a computer program and authentication system 1000 in which the evaluation and / or analysis of the motion data is not performed on-board by the auxiliary device 40 or by the electronic unit 60 of the injection device. Instead, the data analysis or data evaluation may be performed by at least one of the databases 140 or by at least one of the mobile electronic devices 80, 100, 120. In this way, the computing power required for the data analysis or data evaluation can be provided outside the drug delivery device 1, thus saving energy at the drug delivery device 1.
[0168] In some examples, the mobile electronic device 80, 100, 120 may be paired with the electronic unit 60 and / or with the auxiliary device 40. In this way, only one of the multiple mobile electronic devices 80, 100, 120 is given the possibility to communicate with the auxiliary device 40 or with the electronic unit 60. Thus, only one of the multiple mobile electronic devices 80, 100, 120 may be authorized to send any command to the auxiliary device 40 or to the electronic unit 60 of the drug delivery device 1. In a situation where an electronic device 80, 100, 120 paired with or authenticated to communicate with the electronic unit 60 or with the auxiliary device is used by another user who is not authorized or authenticated to use the drug delivery device in question, the acquisition and evaluation or analysis of the motion data can be effectively used to prevent unauthorized use of the drug delivery device. In this way, the patient's safety and the compatibility with the prescribed or intended use of the drug delivery device 1 or the infusion device 10 can be improved with little impact on the user interaction. [Explanation of symbols]
[0169] 1. Drug Delivery Devices 2 Tip direction 3 Proximal direction 4. Users 5. Drug containers 6 Stopper 7 Seal 8. Drugs 10 Injection Device 11 Drive mechanism 12 Dosage Dial 14 Dose Button 15 Inner body 16 Housing 17 Protective Cap 18 Container housing 19 Injection needle 20. Windows 21 Dial Sleeve 22 Drive sleeve 24 Piston rod 25 Pressure Welding Piece 26 Moving parts 30 Interlock 40 Auxiliary Devices 41 Electronic circuit 42 processors 43 Battery 44 Storage 45 Sensors 46 Communication Interface 47 Proximity Sensor 48 Signal Unit 49 Fixtures 50 Housing 51 Display 60 Electronic Unit 61 Electronic circuit 62 processors 63 Battery 64 Storage 65 Sensors 66 Communication Interface 67 Proximity Sensor 68 Signal Unit 80 Mobile Electronic Devices 81 Electronic Unit 82 processors 83 Battery 84 Storage 85 Sensors 86 Communication Interface 87 Proximity Sensor 88 Signal Unit 89 Input 90 Housing 91 Display 95 Satellite Positioning System 96 Antenna 97 Distance measuring unit 98 Position Detection Unit 100 Mobile Electronic Devices 101 Electronic circuits 102 processors 103 Battery 104 Storage 105 Sensors 106 Communication Interface 107 Proximity Sensor 108 Signal Unit 110 Housing 111 Display 112 Strap 120 Mobile Electronic Devices 121 Electronic circuits 122 processors 123 Battery 125 Sensors 126 Communication Interface 127 Proximity Sensor 128 Signal Unit 129 Housing 130 Network 131 Access Points 140 Databases 250 data records 251 Motion Data 252 Gesture Data 254 Motion Patterns 256 User Identification Information 260 data records 261 Motion Data 262 Gesture Data 264 Motion Pattern 266 User Identification Information 270 Matching Index 1000 Authentication System
Claims
1. A method for authenticating a user (4) to use a drug delivery device (1), comprising: - acquiring motion data (261) of said user (4), - comparing said captured motion data (261) with stored motion data (251) of a user specific data record (250) to generate a data matching index (270) indicative of the degree of matching between said captured motion data (261) and said stored motion data (251); - enabling, disabling, triggering or terminating the execution of a function of said drug delivery device (1) based on said data matching index (270); The method includes:
2. The method of claim 1 , wherein the motion data (261) of the user (4) is acquired by an electronic circuit (41, 61, 81, 101, 121) including at least one of a communication interface (46, 66, 86, 106, 126) and a sensor (45, 65, 85, 105, 125).
3. 3. The method of claim 2, wherein at least a portion of the motion data (261) of the user (4) is acquired by the sensors (45, 65, 85, 105, 125), the sensors (45, 65, 85, 105, 125) including at least one of an acceleration sensor, a rotation sensor, a position sensor, a distance sensor, and a physiological data capture sensor.
4. At least a portion of the motion data (261) of the user (4) is transmitted via the communication interface (46, 66, 86, 106, 126), - satellite positioning systems (95), an access point (131) of a communication network (130), the corresponding communication interface (46, 66, 86, 106, 126) - an auxiliary device (40) attachable to said drug delivery device (1), - an electronic unit (60) of said drug delivery device (1), - mobile electronic devices (80, 100, 120) At least one of the following communication interfaces (46, 66, 86, 106, 126): The method according to claim 2 or 3, wherein the information is acquired through wireless communication with at least one of the following:
5. The motion data (261) - gesture data (262) representative of characteristic gestures of said user (4), and a motion pattern (264) indicative of the position and / or motion profile of said user (4) at a particular time or during a particular period of time; The method according to any one of claims 1 to 4, comprising at least one of:
6. The user specific data record (250) comprises: - deriving and storing motion data (251) from previously captured motion data (261) of said user (4); - requesting and receiving from the database (140) user-specific motion patterns (252) and / or user-specific gesture data (252); The method according to any one of claims 1 to 5, wherein the method is obtained by at least one of the following:
7. The method according to any one of claims 1 to 6, wherein the execution of the function of the drug delivery device (1) is enabled or triggered when the data matching index (270) is higher than an upper matching threshold.
8. The method according to any one of claims 1 to 7, wherein execution of the function of the drug delivery device (1) is disabled or terminated when the data matching index (270) is below a lower matching threshold.
9. 1. A method comprising: - entering into a dialogue with said user (4), generating and outputting a user request when the data matching index is lower than the data matching upper threshold and higher than the data matching lower threshold; - enabling or triggering said functionality of said drug delivery device (1) in response to said user dialogue or in response to said user's reaction to said user request. The method of claim 7 or 8, further comprising:
10. An authentication system (1000) for authenticating a user (4) to use a drug delivery device (1), comprising: an electronic circuit (41, 61) integrated in or attached to said drug delivery device (1), said electronic circuit (41, 61) operable to enable, disable, trigger or terminate the execution of a function of said drug delivery device (1); at least one of a sensor (45, 65, 85, 105, 125) and a communication interface (46, 66, 86, 106, 126) operable to acquire motion data (261) of said user (4); a storage (44, 64, 84, 104, 124) operable to store motion data (251) of a user specific data record (250); at least one processor (42, 62, 82, 102, 122) operable to compare acquired motion data (261) with stored motion data (251) and to generate a data matching index (270) indicative of a degree of matching between said acquired motion data (261) and said stored user specific motion data (251), said data matching index (270) being configured to at least one of enable, disable, trigger or terminate execution of said function of said drug delivery device (1); An authentication system (1000) including:
11. The authentication system (1000) of claim 10, wherein the electronic circuit (41) is part of an auxiliary device (40) attachable to the drug delivery device (1), or the electronic circuit (61) is part of an electronic circuit (60) incorporated in the drug delivery device (1).
12. The authentication system (1000) of claim 10 or 11, further comprising at least one mobile electronic device (80, 100, 120), the at least one mobile electronic device (80, 100, 120) comprising at least one of the sensors (85, 105, 125) and the communication interface (86, 106, 126) for acquiring at least a portion of the motion data (261) of the user (4).
13. The authentication system (1000) of claim 12, wherein the electronic circuit (41, 61) includes a circuit communication interface (46, 66) configured for wireless communication with the communication interface (86, 106, 126) of the at least one mobile electronic device (80, 100, 120).
14. The authentication system of claim 13, wherein the circuit communication interface (46, 66) is operable to receive at least the portion of the motion data (261) acquired by the at least one mobile electronic device (80, 100, 120).
15. The authentication system of any one of claims 10 to 14, wherein the mobile electronic device comprises at least one of an external electronic device (80), a wearable electronic device (100), and a wireless tag (120).
16. The authentication system (1000) according to any one of claims 10 to 15, wherein the processor (42, 62, 82, 102, 122) is integrated into one of the electronic circuit (41, 61) and the at least one mobile electronic device (80, 100, 120).
17. The authentication system (1000) of any one of claims 10 to 16, wherein the processor (42, 62, 82, 102, 122) is operable to enable, disable, trigger or terminate execution of the function of the drug delivery device (1) depending on the data matching index (270).
18. A computer program, said program being executed by at least one processor (42, 62, 82, 102, 122) of an authentication system (1000) according to any one of the preceding claims 10 to 17, said processor (42, 62, 82, 102, 122) being adapted to: - obtaining motion data (261) of said user (4), - comparing the acquired motion data (261) with the stored motion data (251) of the user specific data record (250); generating a data matching index (270) indicative of the degree of matching between the acquired motion data (261) and the stored motion data (251); - enabling, disabling, triggering or terminating the execution of said functions of said drug delivery device (1) based on said data matching index (270); A computer program comprising computer readable instructions.
19. A set, a drug delivery device (1) provided with an electronic circuit (61) of the authentication system (1000) according to claim 10; an auxiliary device (40) attachable to said drug delivery device (1) and provided with an electronic circuit (41) of said authentication system (1000) according to claim 10; A mobile electronic device (80, 100, 120) comprising at least one of the sensors (85, 105, 125) and the communication interface (86, 106, 126) of the authentication system (1000) according to claim 10. A set including one, an optionally selected plurality, or all of:
Citation Information
Patent Citations
Personal identification device
JP2010044639A
drug delivery device
JP2018506401A
