Interconnection of drug delivery systems

JP2022549330A5Inactive Publication Date: 2024-11-15JANSSEN PHARMACEUTICALS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2022518969
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2020-05-06
Filing Date
2020-09-24
Publication Date
2024-11-15
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing drug administration systems face challenges in ensuring compliance with guidelines, preventing human error, and securely sharing patient data, which can lead to adverse effects and ineffective drug administration.

Method used

A drug delivery device equipped with sensors, memory, and processors that anonymize and encrypt data, allowing secure communication with remote servers to monitor and control drug delivery, providing reminders, and adjusting delivery parameters based on patient data.

Benefits of technology

Enhances compliance with administration guidelines, ensures secure data sharing, and optimizes drug delivery by adjusting parameters based on patient-specific data, reducing adverse effects and improving treatment efficacy.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

Generally, an interconnection of a medication administration system is provided. In an exemplary embodiment, a medication administration device and a remotely located server may establish a unique key for wireless communication between the device and the server. The medication administration device may be configured to sense information about at least one of the device and the medication and to anonymize data indicative of the sensed information using a key stored in a memory of the device. The medication administration device may also be configured to use the key in decrypting data received from the server.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments described herein relate to devices for the administration and / or delivery of drugs. The present disclosure further relates to systems in which the devices can be used, methods of administration, and further methods associated with the systems.

Background Art

[0002] Pharmaceutical products (including macromolecular and small molecule pharmaceuticals, hereinafter referred to as "drugs") are administered to patients in a variety of different ways for the treatment of specific medical indications. Regardless of the mode of administration, care must be taken when administering drugs to avoid adverse effects on the patient. For example, care must be taken not to administer to the patient an amount of drug that exceeds a safe amount. This requires consideration of the amount of the dose administered, and the time frame in which the dose is delivered, which may sometimes be related to previous doses or doses of other drugs. Further, care must be taken not to inadvertently administer to the patient the wrong drug, or a drug that has deteriorated due to its age or storage conditions. All of these considerations can be communicated in a guide associated with a particular drug or combination of drugs. However, this guide is not always correctly followed, for example, due to mistakes such as human error. This can lead to adverse effects on the patient or result in inappropriate drug administration, for example, an insufficient or excessive volume of drug being administered for a particular medical indication.

[0003] Regarding how drugs are administered to patients, there are various dosage forms that can be used. For example, these dosage forms can include parenteral, inhaled, oral, ophthalmic, nasal, topical, and suppository forms of one or more drugs.

[0004] The dosage forms can be administered directly to the patient via a drug delivery device. There are many different types of drug delivery devices commonly available for the delivery of various dosage forms, including syringes, injection devices (e.g., autoinjectors, jet injectors, and infusion pumps), nasal spray devices, and inhalers.

[0005] It is sometimes desirable to monitor adherence to guidelines associated with medications administered to patients in various dosage forms. This provides assurance that correct procedures are being followed and can help avoid the adoption of inaccurate and potentially dangerous approaches. Furthermore, this may also allow for the optimization of drug administration to patients.

[0006] Furthermore, data related to therapeutic procedures, such as a patient's medical history, current health status, and / or the use of drug delivery devices, may include confidential information that is typically shared only between the patient and appropriate healthcare professionals. Data encryption makes it possible to share data between users and computer systems in a secure and anonymized manner. Data encryption can be implemented using key-based encryption systems to ensure that data, such as confidential medical data, is shared without the risk of exposure of the nature or content of the data to unintended users. Key-based encryption systems enable secure data transmission using a public-key / private-key architecture; anyone can encrypt data using their public key, but the encrypted data can only be decrypted with the recipient's private key. However, due to numerous factors, including patients' unfamiliarity with the devices and the need to communicate medical information in a timely manner without harming the patient, properly configuring patient-managed devices and ensuring effective communication can be challenging.

[0007] Patients typically administer medication according to the instructions, but often without any notification or feedback regarding medication administration. Therefore, patients may forget to administer medication, administer it incorrectly based on their interpretation of the instructions, and / or administer medication without any awareness of their own physiological state. Incorrect medication administration or failure to follow healthcare professional instructions can have serious, even life-threatening, consequences for the patient.

[0008] Patients receiving medication may experience negative side effects or adverse clinical outcomes associated with the medication and should typically initiate contact with the appropriate healthcare professional who prescribed the medication to explore alternative medications, drug delivery devices, and / or guidance that may alleviate the side effects or adverse conditions the patient is experiencing. Patients may delay providing feedback to the appropriate healthcare professional, potentially worsening adverse conditions they may be experiencing, inadvertently failing to report relevant information, and / or further delaying adjustments or readjustments of their drug delivery device with new medication dosages or delivery schedules that may alleviate the problems they are experiencing.

[0009] Furthermore, a large number of patients with a given set of conditions represent a potentially useful resource for accumulating data on physiological responses. However, because it is difficult to collect all of this data, potential trends and correlations may be missed. [Overview of the project] [Means for solving the problem]

[0010] In one embodiment, a drug delivery device is provided configured to hold a drug internally, and in one embodiment, the drug delivery device includes a sensor configured to sense information about at least one of the drug delivery device and the drug. The drug delivery device also includes a memory configured to store data internally. The stored data includes a key established with a remotely located server. The key is unique to the drug delivery device and the remotely located server. The drug delivery device also includes a communication interface configured to wirelessly transmit data indicating the sensed information to a remotely located communication interface. The drug delivery device also includes a processor configured to use the key to anonymize the data indicating the sensed information before transmitting the data indicating the sensed information.

[0011] A drug delivery device can have numerous variations. For example, a drug delivery device may include one of the following: a syringe, an inhaler, an inhaler, a nasal spray device, and an infusion pump. In another example, a processor may be configured to use a key when anonymizing all data transmitted from one communication interface to a remotely located communication interface. In yet another example, a processor may be configured to use the key repeatedly to anonymize multiple datasets representing information perceived by a sensor.

[0012] In yet another example, the communication interface may be configured to wirelessly receive data from a remotely located communication interface, and the processor may be configured to use a key when decrypting the data received from the remotely located communication interface. In at least some embodiments, the processor may be configured to use a key when decrypting all data received from the remotely located communication interface.

[0013] In another example, a communication interface may be configured to wirelessly receive data from a remotely located communication interface, and the data may include information regarding the proper disposal of the drug delivery device after the drug has been delivered from the drug delivery device. In at least some embodiments, a processor may be configured to provide the user of the drug delivery device with notification regarding information regarding proper disposal.

[0014] In yet another example, a drug delivery device may include a label containing information about the proper disposal of the drug delivery device after the drug has been delivered from the device.

[0015] In yet another example, the processor may be configured to control the delivery of the drug from the drug delivery mechanism based at least in part on the information it senses. In yet another example, the drug may include at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.

[0016] In another embodiment, the drug delivery device includes a memory configured to internally store an algorithm having at least one variable parameter, a communication interface configured to wirelessly receive data from a remotely located communication interface, and a processor configured to use the algorithm in controlling the delivery of a drug from the drug delivery device to a patient. The processor is also configured to modify at least one variable parameter of the algorithm stored in the memory based on the data received from the remotely located communication interface.

[0017] A drug delivery device can have numerous variations. For example, a drug delivery device may include one of a syringe, injector, inhaler, nasal spray device, and infusion pump. In another example, a drug delivery device may include a drug holder configured to hold a drug inside, and controlling the delivery of the drug from the drug delivery device to the patient may include controlling the release of the drug from the drug holder. In yet another example, a drug delivery device may be an auto-injector configured to automatically advance a needle into the patient, with at least one variable parameter including the speed at which the needle automatically advances into the patient, and data received from a remotely located communication interface including another speed at which the needle automatically advances into the patient, and changing at least one variable parameter may include replacing that speed with the updated speed in an algorithm. In yet another example, at least one variable parameter may include at least one of the delivery rate of the drug from the drug delivery device to the patient, the timing between doses of drug delivered from the drug delivery device to the patient, and the temperature of the drug. In yet another example, data received from a remotely located communication interface may be based on a physician requesting a change to the algorithm input in a remotely located computer system.

[0018] In another example, the processor may also be configured to have a communication interface send a request to a remotely located communication interface, the request may request an algorithm update, and the data received from the remotely located communication interface may respond to the request. In at least some embodiments, the communication interface may receive a response to the request from the remotely located communication interface indicating that an algorithm update is not necessary, and the processor does not change at least one variable parameter of the algorithm stored in memory.

[0019] In yet another example, the processor may be configured to use an algorithm to control the delivery of a drug from a drug delivery device, and then to use the same algorithm to control another delivery of the drug from the drug delivery device to the patient.

[0020] In another example, a drug delivery device may include a sensor configured to sense information about at least one of the drug delivery device and the drug. In at least some embodiments, a communication interface may be configured to transmit data indicating the sensed information to a remotely located communication interface, and data received from the remotely located communication interface may be at least partially based on the data indicating the sensed information. In some embodiments, a processor may also be configured to change at least one variable parameter of a memory-stored algorithm based on the sensed information without first transmitting data indicating the sensed information to the remotely located communication interface.

[0021] In yet another example, data received from a remotely located communication interface may be automatically transmitted back to the communication interface without responding to a request from that interface for an algorithm update.

[0022] In yet another example, the communication interface may also be configured to wirelessly receive algorithm data from a remotely located communication interface, and the processor may also be configured to modify the algorithm stored in memory based on the data received from the remotely located communication interface. In at least some embodiments, modifying the algorithm may include adding at least one additional variable parameter to the algorithm.

[0023] In another example, the drug may include at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.

[0024] In another embodiment, the drug delivery device includes a memory configured to store algorithms, a communication interface configured to wirelessly receive data from a remotely located communication interface, a drug holder configured to hold a drug internally, and a processor configured to control the delivery of drug doses from the drug holder to the patient by executing algorithms. The processor is configured to adjust the algorithms stored in memory based on data received from the remotely located communication interface and to control the delivery of subsequent doses from the drug holder to the patient by executing the adjusted algorithms.

[0025] The drug delivery device may have numerous variations. For example, the drug delivery device may include one of a syringe, injector, inhaler, nasal spray device, and infusion pump. In another example, the algorithm may include at least one variable parameter, and the processor adjusting the algorithm may include changing at least one variable parameter of the algorithm. In yet another example, adjusting the algorithm may include adding at least one variable parameter to the algorithm. In yet another example, the drug may include at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.

[0026] In one embodiment, the drug administration device includes a drug holder configured to hold a drug internally, a display, and a processor. The processor is configured to cause the display to show at least one of the following: a reminder of the current required to manually administer a drug dose from the drug holder to the patient; a pre-planned summary of the drug dose from the drug holder to the patient; and an indication of the correlation between previously delivered drug doses from the drug holder to the patient and the timing of at least one medical event experienced by the patient.

[0027] Drug delivery devices can have numerous variations. For example, a drug delivery device can include one of a syringe, an injector, an inhaler, a nasal spray device, and an infusion pump. In another example, the device's processor can be configured to cause at least a reminder to be displayed on the display. In yet another example, the device's processor can be configured to cause at least a summary to be displayed on the display, the summary including at least one of an indication of all doses that failed among the previously scheduled doses, an indication of all doses that were successfully delivered among the previously scheduled doses, an indication of the timing of previously delivered doses compared to a predetermined delivery schedule of the doses, an indication of the intended therapeutic effect of the drug on the patient, and an indication of the expected remaining duration of the effect of the drug on the patient. In yet another example, the processor can be configured to cause at least an indication of a correlation to be displayed on the display.

[0028] In another example, the device can include a communication interface configured to wirelessly receive data from a remotely located communication interface, and the processor can be configured to cause information indicative of the data received from the remotely located communication interface to be displayed on the display. In at least some embodiments, the data received from the remotely located communication interface can include the patient's medical history information. In at least some embodiments, the data received from the remotely located communication interface can include help information regarding the correct use of the drug delivery device, and the processor can also be configured to cause information indicative of the help information to be displayed on the display.

[0029] In yet another example, the device may include a sensor configured to sense information regarding at least one of a drug administration device and a drug, and the processor may be configured to cause a display to display information indicative of the sensed information. In at least some embodiments, the device wirelessly transmits data indicative of the sensed information to a remotely located communication interface and subsequently includes a communication interface configured to wirelessly receive data from the remotely located communication interface, at least partially based on the transmitted data, and the processor may be configured to cause a display to display information indicative of the data received from the remotely located communication interface. In another example, the drug may include at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.

[0030] In another aspect, a drug administration system is provided. In one embodiment, the drug administration system includes a server including a communication interface configured to wirelessly receive data and wirelessly transmit data, a memory configured to internally store a key, and a processor. The system also includes a drug administration device including a memory configured to internally store a key. The key is unique to the drug administration device and the server. The drug administration device includes a communication interface configured to wirelessly transmit data to the communication interface of the server and wirelessly receive data from the communication interface of the server. The drug administration device also includes a processor configured to use the key to anonymize all data transmitted to the communication interface of the server prior to its transmission. The processor of the server is configured to use the key to anonymize all data transmitted to the communication interface of the drug administration device prior to its transmission.

[0031] This system can be modified in various ways. For example, data sent to the server's communication interface may include data in response to data requests received from the server. In yet another example, the drug administration device may include one of the following: a syringe, injector, inhaler, nasal spray device, and infusion pump.

[0032] In another example, the drug delivery device may also include sensors configured to sense information about at least one of the drug delivery device and the drug, and the data transmitted to the server's communication interface may include data indicating the sensed information. In at least some embodiments, the drug delivery device's processor may be configured to control the delivery of the drug from the drug delivery device to the patient based at least in part on the sensed information.

[0033] In another example, the server's processor may be configured to decrypt all data received from the drug delivery device's communication interface using a key, and the drug delivery device's processor may be configured to decrypt all data received from the server's communication interface using a key. In yet another example, the server's processor may be configured to automatically upload the data received from the drug delivery device's communication interface to at least one of the patient's Electronic Health Record (EHR) and / or patient monitoring form for drug risk evaluation and mitigation strategies (REMS) associated with the drug delivery device. In yet another example, the drug may include at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.

[0034] In another embodiment, the drug administration system includes a drug administration device configured to hold a drug internally for delivery to a patient, a display, a communication interface configured to wirelessly receive data indicating medical information about the patient, and a processor. The processor is configured to display at least one of the following: a reminder of the current required to manually administer a drug dose to the patient from the drug administration device configured to hold the drug internally, a summary of pre-planned drug doses from the drug holder to the patient, and an indication of a correlation between previously delivered drug doses from the drug administration device to the patient and the timing of at least one medical event experienced by the patient.

[0035] A drug delivery system can have any number of variations. For example, a drug delivery device may include one of a syringe, injector, inhaler, nasal spray device, and infusion pump. In another example, the system may include a communication interface configured to wirelessly receive data from a remotely located communication interface, and a processor may be configured to display information on a display indicating the data received from the remotely located communication interface.

[0036] In yet another example, the system may include a sensor configured to sense information about at least one of a drug delivery device and a drug, and the processor may be configured to display information on a display indicating the sensed information. In at least some embodiments, the system may include a communication interface configured to wirelessly transmit data indicating the sensed information to a remotely located communication interface and subsequently wirelessly receive data from the remotely located communication interface based at least in part on the transmitted data, and the processor may be configured to display information on a display indicating the data received from the remotely located communication interface. In at least some embodiments, the system's drug delivery device may include a communication interface.

[0037] In yet another example, a drug delivery device may include a display and a processor. In yet another example, a server may include a display and a processor. In yet another example, a mobile device may include a display and a processor. In yet another example, a drug may include at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.

[0038] In another embodiment, a drug delivery method is provided, which in one embodiment includes establishing a unique key for wireless communication between a drug delivery device and a server located remotely from the drug delivery device. The key is stored in the memory of the drug delivery device and in the memory of the server. The method also includes a sensor in the drug delivery device sensing information about at least one of the drug delivery device and the drug. The method also includes a processor in the drug delivery device anonymizing data indicating the sensed information using the key stored in the memory of the drug delivery device. The method also includes a processor in the drug delivery device using the key stored in the memory of the drug delivery device when decrypting data received from the server.

[0039] The method may have numerous variations. For example, the method may further include a processor in a drug delivery device that controls the delivery of a drug from the drug delivery device based at least in part on sensed information. In another example, the drug delivery device may include one of a syringe, injector, inhaler, nasal spray device, and infusion pump. In another example, the drug may include at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.

[0040] In yet another example, the data may include information regarding the proper disposal of a drug delivery device after the drug has been delivered from the device. In at least some embodiments, the method may include using a processor to provide the user of the drug delivery device with information regarding proper disposal.

[0041] In another embodiment, the drug delivery method includes using the processor of the drug delivery device to execute an algorithm that controls the delivery of a dose of drug from the drug delivery device to the patient. The algorithm is stored in the memory of the drug delivery device. The method also includes receiving data wirelessly from a remotely located communication interface at the drug delivery device data communication interface. The method also includes using the processor to modify at least one variable parameter of the algorithm stored in memory based on the data received from the remotely located communication interface. The method also includes using the processor to execute the modified algorithm that controls the delivery of a different dose of drug from the drug delivery device to the patient.

[0042] The method may have numerous variations. For example, the drug may include at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.

[0043] In another embodiment, a sensor is provided which is configured to sense information about a patient's physiological parameters, and in one embodiment, the sensor includes a memory configured to store data internally, the stored data including a key established with a remotely located server, the key being unique to the sensor and the remotely located server; a communication interface configured to wirelessly transmit data indicating the sensed information to a remotely located communication interface; and a processor configured to anonymize the data indicating the sensed information using the key before transmitting the data indicating the sensed information.

[0044] The sensor can have numerous variations. For example, the processor may be configured to use a key when anonymizing all data transmitted from one communication interface to a remotely located communication interface. In another example, the processor may be configured to use the key repeatedly to anonymize multiple datasets representing information sensed by the sensor. In at least some embodiments, the sensor may be configured to acquire information about a patient's physiological parameters at least once every 24 hours.

[0045] In yet another example, the sensor's communication interface may be configured to wirelessly receive data from a remotely located communication interface, and the processor may be configured to use a key when decoding the data received from the remotely located communication interface. In at least some embodiments, the processor may be configured to use a key when decoding all data received from the remotely located communication interface.

[0046] In yet another example, the physiological parameter measured by the sensor may be at least one of blood glucose level, blood oxygen saturation, body weight, blood pressure, heart rate, and sleep duration. In yet another example, the drug may include at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.

[0047] In another example, the sensor system may include a server which includes a sensor, a communication interface configured to receive data wirelessly, a memory configured to store keys internally, and a processor.

[0048] The sensor can have numerous variations. For example, the server's processor may be configured to use a key to anonymize all data sent to the sensor's communication interface before transmission. In at least some embodiments, the server's processor may be configured to use a key to decrypt all data received from the sensor's communication interface. The data sent to the server's communication interface may include data in response to data requests received from the server.

[0049] In another example, the sensor system may further include a plurality of sensors, and a sensor may be one of the plurality of sensors. In at least some embodiments, the plurality of sensors may include sensors configured to measure different physiological parameters in the same patient. The plurality of sensors may further include sensors configured to measure corresponding physiological parameters in multiple patients. The server may be configured to store data indicating the sensed information along with the indications of the physiological parameters and the patient. The server may be configured to receive and store data indicating information about drug administration devices associated with each patient. The server may be configured to receive and store data indicating the nutritional intake of each patient. In yet another example, the drug may include at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.

[0050] In another embodiment, a method is provided for sensing information about a patient's physiological parameters, in one embodiment the method includes establishing a unique key for wireless communication between a sensor and a server located remotely from the sensor, the key being stored in the sensor's memory and the server's memory; the sensor sensing information about a patient's physiological parameters; the sensor's processor anonymizing data indicating the sensed information using the key stored in the sensor's memory; and the sensor's processor using the key stored in the sensor's memory when decrypting data received from the server.

[0051] The method may have numerous variations. For example, the drug may include at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate. [Brief explanation of the drawing]

[0052] The present invention will be described with reference to the attached figures as follows. [Figure 1] This is a schematic diagram of the first type of drug delivery device, namely an autoinjector. [Figure 2] This is a schematic diagram of the second type of drug delivery device, namely an infusion pump. [Figure 3] This is a schematic diagram of a third type of drug delivery device, namely an inhaler. [Figure 4] This is a schematic diagram of the fourth type of drug delivery device, namely a nasal spray device. [Figure 5A] This is a schematic diagram of a typical drug delivery device. [Figure 5B] This is a schematic diagram of a universal drug delivery device. [Figure 6] This is a schematic diagram of the housing for the dosage form. [Figure 7] This is a schematic diagram of one embodiment of a communication network system in which a drug delivery device and housing can operate. [Figure 8] This is a schematic diagram of one embodiment of a computer system in which a drug delivery device and housing can operate. [Figure 9] This is a schematic diagram of one embodiment of a drug delivery system including a cloud computing system and a drug delivery device. [Figure 10] This is a flowchart illustrating one embodiment of a method for administering drugs using a key-based security system. [Figure 11] This is a schematic diagram of one embodiment of a drug delivery system including a drug delivery device and a remote computer system. [Figure 12] This is a schematic diagram of another embodiment of a drug delivery system, including a drug delivery device and a remote computer system. [Figure 13] This flowchart shows one embodiment of a method for administering a drug using a control algorithm. [Figure 14] This is a schematic diagram of one embodiment of a user interface. [Figure 15] This is a schematic diagram of one embodiment of a system using sensors. [Figure 16] This flowchart shows one embodiment of a method for updating a patient monitoring form and identifying one or more abnormal sensing parameters. [Modes for carrying out the invention]

[0053] Specific exemplary embodiments will now be described so that the structure, function, manufacturing and use principles of the devices, systems, and methods disclosed herein can be understood comprehensively. One or more of these embodiments are illustrated in the accompanying drawings. Those skilled in the art will understand that the devices, systems, and methods described herein and shown in the accompanying drawings are non-limiting exemplary embodiments and that the scope of the invention is defined solely by the claims. Features illustrated or described in relation to one exemplary embodiment can be combined with features of other embodiments. Such modifications and variations are included within the scope of the invention.

[0054] Furthermore, in this disclosure, components with similar names in embodiments generally have similar characteristics, and therefore, in a particular embodiment, each characteristic of each component with a similar name is not necessarily described in full detail. In addition, to the extent that linear or circular dimensions are used in the description of the disclosed systems, devices, and methods, such dimensions are not intended to limit the types of shapes that can be used in combination with such systems, devices, and methods. Those skilled in the art will recognize that dimensions equivalent to such linear and circular dimensions can be easily determined for any geometric shape. Those skilled in the art will understand that even if the dimensions are not exact values, they can be considered to be close to them due to factors such as manufacturing tolerances and the sensitivity of measuring instruments. The size and shape of systems and devices, and their components, may depend on the size and shape of at least the components in which the systems and devices are used together.

[0055] Examples of various types of drug delivery devices, namely an auto-injector 100, an infusion pump 200, an inhaler 300, and a nasal spray device 400, are described below with reference to the above reference diagram.

[0056] Auto injector Figure 1 is a schematic illustrative diagram of a first type of drug delivery device, i.e., an injection device, in this example, an autoinjector 100, which can be used in embodiments described herein. The autoinjector 100 comprises a drug holder 110 that holds the drug to be dispensed, and a dispensing mechanism 120 configured to dispense the drug from the drug holder 110 so that the drug can be administered to a patient. The drug holder 110 is typically in the form of a container that holds the drug, for example, the drug holder 110 may be supplied in the form of a syringe or vial, or any other suitable container that can hold the drug. The autoinjector 100 comprises a dispensing nozzle 122, for example, a syringe needle provided at the distal end of the drug holder 110. The dispensing mechanism 120 comprises a drive element 124, the drive element itself may also comprise a piston and / or piston rod, and a drive mechanism 126. The distribution mechanism 120 is located proximal to the end of the drug holder 110 and toward the proximal end of the autoinjector 100.

[0057] The auto-injector 100 comprises a housing 130 which not only houses a drug holder 110, a drive element 124, and a drive mechanism 126 within the body of the housing 130, but also a discharge nozzle 122 which is typically fully housed within the housing before injection but extends from the housing 130 to deliver the drug during the injection sequence. The distribution mechanism 120 is arranged such that the drive element 124 is advanced through the drug holder 110 to distribute the drug through the discharge nozzle 122, thereby enabling the auto-injector to administer the drug held in the drug holder 110 to the patient. In some cases, the user may manually advance the drive element 124 through the drug holder 110. In other cases, the drive mechanism 126 may include a stored energy source 127 that advances the drive element 124 without user assistance. The stored energy source 127 may include a spring, a pressurized gas, or an elastically biased member such as an electronically powered motor and / or gearbox.

[0058] The auto-injector 100 includes a distribution mechanism protection mechanism 140. The distribution mechanism protection mechanism 140 typically has two functions. Firstly, the distribution mechanism protection mechanism 140 may function to prevent access to the discharge nozzle 122 before and after injection. Secondly, the auto-injector 100 may function such that the distribution mechanism 120 can be activated when it is activated, for example, when the distribution mechanism protection mechanism 140 is moved to the unlocked position.

[0059] The protective mechanism 140 covers at least a portion of the dispensing nozzle 122 when the drug holder 110 is in a retracted position proximal to the housing 130. This is to prevent contact between the dispensing nozzle 122 and the user. Alternatively or additionally, the protective mechanism 140 is configured to retract proximal to expose the dispensing nozzle 122, thereby allowing the dispensing nozzle 122 to come into contact with the patient. The protective mechanism 140 comprises a shielding member 141 and a return spring 142. The return spring 142 causes the shielding member 141 to extend from the housing 130, thereby acting to cover the dispensing nozzle 122 when no force is applied to the distal end of the protective mechanism 140. When a user applies force to the shielding member 141 against the action of the return spring 142 in order to overcome the biasing of the return spring 142, the shielding member 141 retracts within the housing 130, thereby exposing the dispensing nozzle 122. The protective mechanism 140 may optionally or additionally include an extension mechanism (not shown) for extending the discharge nozzle 122 beyond the housing 130, and may further include a retraction mechanism (not shown) for retracting the discharge nozzle 122 into the housing 130. The protective mechanism 140 may optionally or additionally include a housing cap and / or discharge nozzle boot that can be attached to the auto-injector 100. When the housing cap is removed, the discharge nozzle boot is typically also removed from the discharge nozzle 122.

[0060] The auto-injector 100 also includes a trigger 150. The trigger 150 comprises a trigger button 151 located on the outer surface of the housing 130 so as to be accessible to the user of the auto-injector 100. When the trigger 150 is pressed by the user, the trigger 150 acts to release the drive mechanism 126, as a result the drug is ejected from the drug holder 110 via the drive element 124, and then via the ejection nozzle 122.

[0061] The trigger 150 may also cooperate with the shield member 141 in such a way that it prevents the trigger 150 from being activated until the shield member 141 is sufficiently retracted proximal to its unlocked position within the housing 130, for example, by pressing the distal end of the shield member 141 against the patient's skin. Once this is done, the trigger 150 is unlocked and can be pressed, and the auto-injector 100 is then activated so that the injection and / or drug delivery sequence is initiated. Alternatively, retracting the shield member 141 proximal into the housing 130 on its own may act to activate the drive mechanism 126 and initiate the injection and / or drug delivery sequence. In this way, the auto-injector 100 has a device operation prevention mechanism that prevents drug distribution, for example, by preventing accidental release of the distribution mechanism 120 and / or accidental activation of the trigger 150.

[0062] The foregoing description relates to an example of an auto-injector, but this example is presented purely for illustrative purposes, and the present invention is not limited to such an auto-injector. Those skilled in the art will understand that various modifications to the described auto-injector can be made within the scope of this disclosure.

[0063] The autoinjector of this disclosure may be used to administer any of the following drugs: epinephrine, Rebif, Enbrel, Aranesp, atropine, pralidoxime chloride, and diazepam.

[0064] injection pump In other situations, patients may require precise, continuous delivery of medication or regular or frequent delivery at set cyclical intervals. Infusion pumps can provide such controlled drug infusion by facilitating the administration of medication at a precise rate that keeps drug concentrations within therapeutic limits, without requiring frequent attention from healthcare professionals or the patient.

[0065] Figure 2 is a schematic illustrative diagram of a second type of drug delivery device, namely an infusion pump 200, usable in embodiments described herein. The infusion pump 200 comprises a drug holder 210 in the form of a reservoir for containing the drug to be delivered, and a distribution mechanism 220 having a pump 216 adapted to distribute the drug contained in the reservoir so that the drug can be delivered to the patient. These components of the infusion pump are located within a housing 230. The distribution mechanism 220 further comprises an infusion line 212. The drug is delivered from the reservoir via the infusion line 212, which may take the form of a cannula, when the pump 216 is operated. The pump 216 may take the form of an elastomer pump, a peristaltic pump, an osmotic pump, or a motor-controlled piston in a syringe. Typically, the drug is delivered intravenously, but subcutaneous, arterial, and epidural injections may also be used.

[0066] The infusion pump of this disclosure may be used to administer any of the following drugs: insulin, antropine sulfate, avibactam sodium, bendamustine hydrochloride, carboplatin, daptomycin, epinephrine, levetiracetam, oxaliplatin, paclitaxel, pantoprazole sodium, treprostinil, vasopressin, voriconazole, and zoledronic acid.

[0067] The infusion pump 200 further comprises a processor 296 in addition to a control circuit, such as a memory 297 and a user interface 280, which together provide a trigger mechanism and / or a dosage selector for the pump 200. The user interface 280 may be implemented by a display screen located on the housing 230 of the infusion pump 200. The control circuit and user interface 280 may be located inside or outside the housing 230 and communicate with the pump 216 via a wired or wireless interface to control its operation.

[0068] The operation of pump 216 is controlled by a processor 296 that communicates with pump 216 to control its operation. The processor 296 can be programmed by a user (e.g., a patient or healthcare professional) via a user interface 280. This enables the infusion pump 200 to deliver drugs to the patient in a controlled manner. The user can input parameters such as infusion duration and delivery rate. The delivery rate can be set by the user to a constant infusion rate or, typically, as a set interval within pre-programmed limits for periodic delivery. The programmed parameters for controlling pump 216 are stored in and retrieved from memory 297, which communicates with the processor 296. The user interface 280 may take the form of a touchscreen or a keypad.

[0069] The power supply 295 may take the form of an energy source integrated with the pump 216 and / or a mechanism for connecting the pump 216 to an external power source.

[0070] The infusion pump 200 can take on a variety of different physical forms depending on its designated use. For example, the infusion pump 200 may be a fixed, non-portable device for use at the patient's bedside, or it may be a portable infusion pump designed to be portable or wearable. The integrated power supply 295 is particularly beneficial for portable infusion pumps.

[0071] The above description relates to an example of an injection pump, which is provided purely for illustrative purposes. This disclosure is not limited to such an injection pump. Those skilled in the art will understand that various modifications to the described injection pump can be made within the scope of this disclosure. For example, the processor may be pre-programmed so that the injection pump does not need to include a user interface.

[0072] inhaler Figure 3 is a schematic diagram of a third type of drug administration device, namely an inhaler 300. The inhaler 300 includes a drug holder 310 in the form of a canister. The drug holder 310 typically contains a drug in solution or suspension form using a suitable carrier liquid. The inhaler 300 further includes a pressurized gas for pressurizing the drug holder 310, and a distribution mechanism 320 including a valve 325 and a nozzle 321. The valve 325 forms the outlet of the drug holder 310. The valve 325 includes a narrow opening 324 formed within the drug holder 310 and a movable element 326 that controls the opening 324. When the movable element 326 is in the resting position, the valve 325 is in a closed or non-operating state, where the opening 324 is closed and the drug holder 310 is sealed. When the movable element 326 is operated from the resting position to the operating position, the valve 325 is operated to an open state, where the opening 324 is open. The movement of the movable element 326 from the resting position to the operating position involves moving the movable element 326 into the drug holder 310. The movable element 326 is elastically biased to the resting position. With the valve 325 open, pressurized gas pushes the drug, which is in a solution or suspension state using a suitable liquid, out of the drug holder 310 at high speed through the opening 324. The high-speed passage of the liquid through the narrow opening 324 causes the liquid to atomize, i.e., convert from bulk liquid into a mist and / or gas cloud of fine droplets of liquid. The patient can inhale the mist and / or gas cloud of fine droplets into their respiratory tract. Thus, the inhaler 300 can deliver the drug held in the drug holder 310 into the patient's respiratory tract.

[0073] The drug holder 310 is removably held within the housing 330 of the inhaler 300. A passage 333 formed within the housing 330 connects a first opening 331 within the housing 330 with a second opening 332 within the housing 330. The drug holder 310 is received within the passage 333. The drug holder 310 is slidably inserted into the passage 333 through the first opening 331 of the housing 330. The second opening 332 of the housing 330 forms a mouthpiece 322 configured to be placed in the patient's mouth, or a nosepiece configured to be placed in the patient's nostrils, or a mask configured to be placed over the patient's mouth and nose. The drug holder 310, the first opening 331, and the passage 333 are sized so that air can flow through the passage 333 around the drug holder 310 between the first opening 331 and the second opening 332. The inhaler 300 may also include a dispensing mechanism protection mechanism 140 in the form of a cap (not shown) that can be fitted onto the mouthpiece 322.

[0074] The inhaler 300 further comprises a trigger 350, which includes a valve actuation feature 355 configured to actuate a valve 325 when the trigger 350 is actuated. The valve actuation feature 355 is a projection of the housing 330 into the passage 333. The drug holder 310 is slidably movable within the passage 333 from a first position to a second position. In the first position, the end of the movable element 326 in the resting position abuts against the valve actuation feature 355. In the second position, the drug holder 310 can be displaced toward the valve actuation feature 355 so that the valve actuation feature 355 moves the movable element 326 into the drug holder 310, thereby actinguating the valve 325 to an open position. The user's hand provides the force necessary to move the drug holder 310 from the first position to the second position against the elastically biased movable element 326. The valve operating feature 355 includes an inlet 356 connected to the nozzle 321. The inlet 356 of the valve operating feature 355 is sized and positioned to connect to the opening 324 of the valve 325 so that the discharged droplet mist and / or gas cloud can enter the inlet 356 and exit through the nozzle 321 into the passage 333. The nozzle 321 assists in atomizing the bulk liquid into droplet mist and / or gas cloud.

[0075] Valve 325 provides a metering mechanism 370. The metering mechanism 370 is configured to close the valve after a measured amount of liquid, and therefore drug, has passed through the opening 324. This allows a controlled dose to be administered to the patient. Typically, the amount of liquid to be measured is preset, but the inhaler 300 may also include a user-operable dose selector 360 to vary a defined amount of liquid.

[0076] The foregoing description relates to one specific example of an inhaler, but this example is purely illustrative. The description should not be considered as being limited to such an inhaler. Those skilled in the art will understand that a number of other types of inhalers and nebulizers may be used in conjunction with the disclosure. For example, the drug may be in powder form, the drug may be in liquid form, or the drug may be atomized by other forms of distribution mechanisms 320 including ultrasonic vibrations, compressed gas, a vibrating mesh, or a heat source.

[0077] The inhaler of this disclosure may be used to administer any of the following drugs: mometasone, fluticasone, ciclesonide, budesonide, beclomethasone, vilanterol, salmeterol, formoterol, umeclidinium, glycopyrrolate, tiotropium, aclidinium, indacaterol, salmeterol, and olodaterol.

[0078] Nasal spray device Figure 4 is a schematic diagram of a fourth type of drug administration device, namely a nasal spray device 400. The nasal spray device 400 is configured to deliver a drug into the patient's nose. The nasal spray device 400 includes a drug holder 402 configured to contain a drug for delivery from the device 400 to the patient. The drug holder 402 may have various configurations such as a bottle reservoir, a cartridge, a vial (as in this exemplary embodiment), a blow-fill-seal (BFS) capsule, or a blister pack. In one exemplary embodiment, the drug holder 402 is a vial. The exemplary vial is formed from one or more materials, such as glass, polymer, etc. In some embodiments, the vial may be formed from glass. In other embodiments, the vial may be formed from one or more polymers. In yet another embodiment, different parts of the vial may be formed from different materials. The exemplary vial may have various features that facilitate sealing and storing the drug inside, as described herein and shown in the drawings. However, those skilled in the art will recognize that vials may include only some of these features and / or various other features known in the art. The vials described herein are intended to represent specific exemplary embodiments only.

[0079] The opening 404 of the nasal spray device 400, through which the drug exits the nasal spray device 400, is formed within the dispensing head 406 of the nasal spray device 400, specifically within the tip 408 of the dispensing head 406. The tip 408 is configured to be inserted into the patient's nostril. In one exemplary embodiment, the tip 408 is configured to be inserted into the patient's first nostril during the first stage of operation of the nasal spray device 400, and into the patient's second nostril during the second stage of operation of the nasal spray device 400. The first and second stages of operation involve two distinct acts of the nasal spray device 400: a first act corresponding to the delivery of a first dose of the drug, and a second act corresponding to the delivery of a second dose of the drug. In some embodiments, the nasal spray device 400 is configured to be acted only once to deliver one nasal spray. In some embodiments, the nasal spray device 400 is configured to operate three or more times to deliver three or more nasal sprays, for example, four, five, six, seven, eight, nine, or ten times.

[0080] The dispensing head 406 includes a depth guide 410 configured to contact the patient's skin between the patient's first and second nostrils, such that the longitudinal axis of the dispensing head 406 is substantially aligned with the longitudinal axis of the nostril into which the tip portion 408 is inserted. A person skilled in the art will understand that, due to any number of factors such as manufacturing tolerances and the sensitivity of the measuring instrument, the longitudinal axis may not be precisely aligned, but may be considered substantially aligned.

[0081] In an exemplary embodiment, as shown in Figure 4, the dispensing head 406 has a tapered shape and has a smaller diameter at its distal end than at its proximal end where the opening 404 is located. The relatively small diameter of the opening 404 facilitates the spraying of the drug from the opening 404, as will be understood by those skilled in the art. The spray chamber 412, through which the drug passes before exiting the opening 404, is located within the proximal portion of the tapered dispensing head 406 distal to the opening 404. As the drug rapidly passes through the spray chamber 412, the spray chamber 412 facilitates the generation of a fine mist that exits the opening 404 in a consistent spray turn. The arrow 414 in Figure 4 indicates the path of drug movement from and out of the drug holder 402 and the opening 404.

[0082] In some embodiments, the dispensing head 406 may include two tip portions 408, each having an opening 404 inside, so that the nasal spray device 400 is configured to deliver a dose of the drug into two nostrils simultaneously in response to a single action.

[0083] The dispensing head 406 is configured to actuate the nasal spray device 400 by being pushed toward the drug holder 402, for example, by a user pressing down on the depth guide 410. In other words, the dispensing head 406 is configured as an actuator that is actuated to eject the drug from the drug holder 402 and from the nasal spray device 400. In an exemplary embodiment, the nasal spray device 400 is configured for self-administration, such that the user who actsuates the nasal spray device 400 is the patient receiving the drug from the nasal spray device 400, but another person may actuate the nasal spray device 400 for delivery to another person.

[0084] The operation of the dispensing head 406, for example, by pressing, is configured to allow venting air into the drug holder 402, as indicated by arrow 416 in Figure 4. The air entering the drug holder 402 moves the drug in the drug holder through tube 418 and then into the metering chamber 420, where the metering chamber 420 moves the drug through cannula 422 proximal to the spray chamber 412 and then out through opening 404. In response to the release of the dispensing head 406, for example, when the user stops pressing the dispensing head 406 downward, the biasing spring 426 returns the dispensing head 406 to its default resting position, positioning the dispensing head 406 relative to the drug holder 402 for subsequent operation and drug delivery.

[0085] The above description relates to one specific example of a nasal spray device, but this example is purely illustrative. This description should not be considered as being limited to such a nasal spray device. Those skilled in the art will understand that the nasal spray device 400 may have different features in different embodiments depending on various requirements. For example, the nasal spray device 400 may lack a depth guide 410 and / or include one or more of the following: a device indicator, a sensor, a communication interface, a processor, memory, and a power supply.

[0086] The nasal spray device of this disclosure may be used to administer any of a variety of drugs, such as ketamine (e.g., Ketalar®), esketamine (e.g., Spravato®, Ketanest®, and Ketanest-S®), naloxone (e.g., Narcan®), and sumatriptan (e.g., Imitrex®).

[0087] Drug administration devices As can be understood from the foregoing, various components of a drug delivery device are common to all such devices. These components form the essential components of a universal drug delivery device. The drug delivery device delivers the drug to the patient, and the drug is provided within the drug delivery device in a defined dosage form.

[0088] Figure 5A is a generalized schematic diagram of such a universal drug delivery device 501, and Figure 5B is an exemplary embodiment of such a universal drug delivery device 500. Examples of universal drug delivery devices 500 include injection devices (e.g., auto-injectors, jet injectors, and infusion pumps), nasal spray devices, and inhalers.

[0089] As shown in Figure 5A, the drug administration device 501, in a typical form, includes the features of a drug holder 10 and a dispensing mechanism 20. The drug holder 10 holds the drug in the dosage form to be administered. The dispensing mechanism 20 is configured to release the dosage form from the drug holder 10 so that the drug can be administered to the patient.

[0090] Figure 5B shows a further universal drug administration device 500 including several additional features. Those skilled in the art will understand that these additional features are optional for different embodiments and may be available in various different combinations, depending on requirements such as the type of drug, the dosage form of the drug, the medical indication being treated with the drug, safety requirements, whether the device is powered, whether the device is portable, whether the device is used for self-administration, and many other requirements that will be understood by those skilled in the art. Similar to the universal device in Figure 5A, the drug administration device 500 comprises a drug holder 10 and a housing 30 housing a distribution mechanism 20.

[0091] The device 500 includes a trigger mechanism 50 for initiating the release of a drug from the drug holder 10 by a dispensing mechanism 20. The device 500 also includes a metering / dosing mechanism 70 that measures a set dose to be released from the drug holder 10 via the dispensing mechanism 20. In this way, the drug administration device 500 can provide a known dose of a determined size. The device 500 includes a dose selector 60 that allows the user to set the dose volume of the drug measured by the metering mechanism 70. The dose volume can be set to one specific value from a plurality of predetermined individual dose volumes, or to any value of a predetermined dose volume within a range of dose volumes.

[0092] The device 500 may include a device operation prevention mechanism 40 or 25, which, when locked, prevents and / or stops the dispensing mechanism 20 from releasing a drug from the drug holder 10, and when unlocked, allows the dispensing mechanism 20 to release a drug dose from the drug holder 10. This prevents accidental drug administration, for example, to prevent administration at the wrong time or to prevent inattentive operation. The device 500 also includes a dispensing mechanism protection mechanism 42, for example, for safety reasons, which prevents access to at least a portion of the dispensing mechanism 20. The device operation prevention mechanism 40 and the dispensing mechanism protection mechanism 42 may be the same component.

[0093] Device 500 may include a device indicator 85 configured to display information about the status of the drug administration device and / or the drug contained therein. The device indicator 85 may be a visual indicator, such as a display screen, or an audio indicator. Device 500 may include a user interface 80 which may be configured to display information about Device 500 to the user of Device 500 and / or to allow the user to control Device 500. Device 500 may include a device sensor 92 configured to sense information related to the drug administration device and / or the drug contained therein, such as dosage form and device parameters. For example, in an embodiment including a metering mechanism 70 and a dose selector 60, the embodiment may further include one or more device sensors 92 configured to sense one or more of the doses selected by the user using the dose selector 60, the dose metered by the metering mechanism 70, and the dose distributed by the dispensing mechanism 20. Similarly, an environmental sensor 94 is provided which is configured to sense information about the environment in which Device 500 exists, such as ambient temperature, ambient humidity, location, and time. For example, there may be a dedicated position sensor 98 configured to determine the geographical location of device 500 via satellite positioning such as GPS. Device 500 also includes a communication interface 99 that can communicate data acquired from various sensors relating to the device and / or drug to the outside.

[0094] If necessary, the device 500 includes a power supply 95 for delivering power to one or more electrical components of the device 500. The power supply 95 may be a power supply integrated with the device 500 and / or a mechanism for connecting the device 500 to an external power supply. The drug delivery device 500 also includes a device computer system 90, which includes a processor 96 and memory 97, powered by the power supply 95, and which communicate with each other and, optionally, with other electrical and control components of the device 500, such as an environmental sensor 94, a position sensor 98, a device sensor 92, a communication interface 99, and / or an indicator 85. The processor 96 is configured to acquire and process data obtained from the environmental sensor 94, the device sensor 92, the communication interface 99, the position sensor 98, and / or the user interface 80, and to provide data outputs to, for example, the indicator 85 and / or the communication interface 99.

[0095] In some embodiments, the drug delivery device 500 is sealed within a packaging 35. The packaging 35 may further include a combination of a processor 96, memory 97, user interface 80, device indicator 85, device sensor 92, position sensor 98, and / or environmental sensor 94, as described herein, which may be located outside the housing of the device 500.

[0096] Those skilled in the art will understand that a universal drug administration device 500 comprising a drug holder 10 and a dispensing mechanism 20 may have the various optional features described above in several different combinations. Furthermore, the drug administration device 500 may optionally include two or more drug holders 10, each having two or more dispensing mechanisms 20, such that each drug holder has a dispensing mechanism 20 associated with itself.

[0097] Drug dosage forms Traditionally, drug delivery devices utilize liquid dosage forms. However, it should be understood that other dosage forms are also available.

[0098] One such common dosage form is the tablet. Tablets can be formed from a combination of the drug and an excipient that is compressed together. Other dosage forms include pastes, creams, powders, ear drops, and eye drops.

[0099] Further examples of drug dosage forms include skin patches, drug-eluting stents, and intrauterine devices. In these examples, the body of the device may contain the drug and be configured to allow drug release under specific circumstances. For example, a skin patch may contain a polymer composition containing the drug. The polymer composition allows the drug to diffuse from the polymer composition into the patient's skin. Drug-eluting stents and intrauterine devices may operate in a similar manner. Thus, the patch, stent, and intrauterine device may be considered themselves drug holders with associated distribution mechanisms.

[0100] Any of these dosage forms may be configured to initiate drug release under specific conditions. This may allow the drug to be released at a desired time or location after the dosage form has been introduced to the patient. In particular, drug release may be initiated by an external stimulus. Furthermore, these dosage forms may be housed in a housing, which may be in the form of packaging, prior to administration. This housing may include some of the optional features described above that are utilized in the universal drug delivery device 500.

[0101] The drugs administered by the drug delivery devices of this disclosure may be any substance that causes physiological or psychological changes in an organism when consumed. Examples of drugs that can be administered by the drug delivery devices of this disclosure include 5-alpha-reductase inhibitors, 5-aminosalicylates, 5HT3 receptor antagonists, ACE inhibitors with calcium channel blockers, ACE inhibitors with thiazides, adamantane antiviral drugs, corticosteroids, corticosteroid inhibitors, adrenergic bronchodilators, emergency treatments for hypertension, treatments for pulmonary hypertension, aldosterone receptor antagonists, alkylating agents, allergens, α-glucosidase inhibitors, alternative drugs, amoebicides, amino Glycosides, aminopenicillins, aminosalicylic acids, AMPA receptor antagonists, amylin analogs, combination analgesics, analgesics, androgens and anabolic steroids, angiotensin-converting enzyme inhibitors, angiotensin II inhibitors with calcium channel blockers, angiotensin II inhibitors with thiazides, angiotensin receptor blockers, angiotensin receptor blockers and neprilysin inhibitors, anorectal preparations, appetite suppressants, antacids, anthelmintics, anti-angiogenic ophthalmic agents, anti-CTLA-4 monoclonal antibodies, anti-infective agents, anti PD-1 monoclonal antibodies, thiazide-containing anti-adrenergic agents (central), thiazide-containing anti-adrenergic agents (peripheral), anti-adrenergic agents, centrally acting, anti-adrenergic agents, peripherally acting, anti-androgens, anti-anginal agents, antiarrhythmic agents, combination anti-asthmatic agents, antibiotics / antineoplastic agents, anticholinergic antiemetics, anticholinergic antiparkinsonian agents, anticholinergic bronchodilators, anticholinergic chronotropic agents, anticholinergic / antispasmodics, anticoagulant reversals, anticoagulants, anticonvulsants, antidepressants, antidiabetic drugs Combinations of antidiabetic drugs, antidiarrheals, antidiuretic hormones, detoxifiers, antiemetics / anti-vertigo drugs, antifungal drugs, antigonadistants, antigout drugs, antihistamines, antihyperlipidemic drugs, combinations of antihyperlipidemic drugs, combinations of antihypertensive drugs, antihyperuricemia drugs, antimalarial drugs, combinations of antimalarial drugs, antimalarial quinolones, antimanic drugs, antimetabolites, antimigraine drugs, combinations of antitumor drugs, antitumor drug detoxifiers, antitumor drug interferon, antitumor drugs, antiparkinsonian drugs, antiplatelet drugs, anti-Pseudomonas penicillin, psoriasis treatment drugs, antipsychotic drugs, antirheumatic drugs,Preservatives and bactericides, antithyroid agents, antitoxins and antibenins, antituberculosis agents, combinations of antituberculosis agents, antitussives, antiviral agents, antiviral boosters, combinations of antiviral agents, antiviral interferons, anxiolytics, sedatives, and hypnotics, aromatase inhibitors, atypical antipsychotics, azole antifungals, bacterial vaccines, barbiturate anticonvulsants, barbiturates, BCR-ABL tyrosine kinase inhibitors, benzodiazepine anticonvulsants, benzodiazepines, beta-blockers including calcium channel blockers, beta-blockers including thiazides, beta-adrenergic Phosphate blockers, beta-lactamase inhibitors, bile acid chelating agents, biological agents, bisphosphonates, bone morphogenetic proteins, bone resorption inhibitors, combination bronchodilators, bronchodilators, calcium receptor agonists, calcineurin inhibitors, calcitonin, calcium channel blockers, carbamate anticonvulsants, carbapenems, carbapenem / beta-lactamase inhibitors, carbonic anhydrase inhibitor anticonvulsants, carbonic anhydrase inhibitors, cardiac stress agents, cardiac selective beta-blockers, cardiovascular agents, catecholamines, cation exchange resins, CD20 monoclonal antibodies, CD30 monoclonal antibodies Noclonal antibodies, CD33 monoclonal antibodies, CD38 monoclonal antibodies, CD52 monoclonal antibodies, CDK4 / 6 inhibitors, central nervous system drugs, cephalosporins, cephalosporin / beta-lactamase inhibitors, selmenoristics, CFTR combinations, CFTR enhancers, CGRP inhibitors, chelating agents, chemokine receptor antagonists, chloride channel activators, cholesterol absorption inhibitors, cholinergic agonists, cholinergic muscle stimulants, cholinesterase inhibitors, CNS stimulants, coagulation modifiers, colony-stimulating factors, contraceptives, adrenal cortical stimulants Hormones, coumarins and indanedions, Cox-2 inhibitors, decongestants, dermatological drugs, diagnostic radiopharmaceuticals, diarylquinolines, dibenzazepine anticonvulsants, digestive enzymes, dipeptidyl peptidase-4 inhibitors, diuretics, dopaminergic antiparkinsonists, drugs used for alcohol dependence, echinocandin, EGFR inhibitors, estrogen receptor antagonists, estrogens, expectorants, factor Xa inhibitors, fatty acid derivative anticonvulsants, fibrinic acid derivatives, first-generation cephalosporins, fourth-generation cephalosporins, functional bowel disorder agents, gallstone solubilizers,γ-aminobutyric acid analogs, γ-aminobutyric acid reuptake inhibitors, gastrointestinal drugs, general anesthetics, urogenital tract drugs, gastrointestinal stimulants, glucocorticoids, glucose-raising agents, glycopeptide antibiotics, glycoprotein platelet inhibitors, glycylcycline, gonadotropin-releasing hormone, gonadotropin-releasing hormone antagonists, gonadotropins, group I antiarrhythmic agents, group II antiarrhythmic agents, group III antiarrhythmic agents, group IV antiarrhythmic agents, group V antiarrhythmic agents, growth hormone receptor blockers, growth hormone, guanylate cyclase-C agonists, Helicobacter pylori eradicators, H2 antagonists Antidotes, Hedgehog pathway inhibitors, hematopoietic stem cell mobilizers, heparin antagonists, heparin, HER2 inhibitors, herbal products, histone deacetylase inhibitors, hormones, hormone / antineoplastic drugs, hydantoin anticonvulsants, hydrazide derivatives, illegal (street) drugs, immunoglobulins, immunosuppressants, immunostimulants, immunosuppressants, impotence agents, in vivo diagnostic biological agents, incretin mockups, inhaled anti-infectives, inhaled corticosteroids, inotropic agents, insulin, insulin-like growth factor, integrase chain transfer inhibitors, interferon, interleukin inhibitors Interleukins, intravenous nutrition products, iodized contrast agents, ionic iodized contrast agents, iron products, ketride, laxatives, anti-leprosy drugs, leukotriene modifiers, lincomycin derivatives, locally injectable anesthetics, locally injectable anesthetics containing corticosteroids, loop diuretics, pulmonary surfactants, lymph dyes, lysosomal enzymes, macrolide derivatives, macrolides, magnetic resonance imaging contrast agents, mast cell stabilizers, medical gases, meglitinide, metabolites, methylxanthines, mineralocorticoids, minerals and electrolytes, other drugs, other analgesics, other antibiotics, and so on. Other anticonvulsants, other antidepressants, other antidiabetic drugs, other antiemetics, other antifungals, other antihyperlipidemia drugs, combinations of other antihypertensive drugs, other antimalarial drugs, other antitumor drugs, other antiparkinsonian drugs, other antipsychotics, other antituberculosis drugs, other antivirals, other anxiety relievers, sedatives and hypnotics, other bone resorption inhibitors, other cardiovascular drugs, other central nervous system drugs, other coagulation modifiers, other diagnostic dyes, other diuretics, other urogenital drugs, other gastrointestinal drugs, other hormones, other metabolites,Other ophthalmic drugs, other ear drugs, other respiratory drugs, other sex hormones, other topical drugs, other unclassified drugs, other vaginal drugs, mitotic inhibitors, monoamine oxidase inhibitors, oral and throat products, mTOR inhibitors, mucolytics, multikinase inhibitors, muscle relaxants, mydriatics, combinations of narcotic analgesics, narcotic analgesics, nasal anti-infectives, nasal antihistamines and decongestants, nasal lubricants and washes, nasal preparations, nasal steroids, natural penicillin, neprilysin inhibitors, neuraminidase inhibitors, neuromuscular blockers, neuronal potassium channel blockers Puna, next-generation cephalosporins, nicotinic acid derivatives, NK1 receptor antagonists, NNRTIs, non-cardiac selective beta-blockers, non-iodinated contrast agents, non-ionic iodinated contrast agents, non-sulfonylurea, nonsteroidal anti-inflammatory drugs, NS5A inhibitors, nucleoside reverse transcriptase inhibitors (NRTIs), nutritional supplements, nutritional products, ophthalmic anesthetics, ophthalmic anti-infectives, ophthalmic anti-inflammatory drugs, ophthalmic antihistamines and decongestants, ophthalmic diagnostic agents, ophthalmic glaucoma drugs, ophthalmic lubricants and washes, ophthalmic preparations, ophthalmic steroids, ophthalmic steroids including anti-infectives, ophthalmic surgical drugs, oral nutritional supplements Drugs, other immunostimulants, other immunosuppressants, ear anesthetics, ear anti-infectives, ear preparations, ear steroids, ear steroids containing anti-infectives, oxazolidinedione anticonvulsants, oxazolidine antibiotics, parathyroid hormone and analogues, PARP inhibitors, PCSK9 inhibitors, penicillinase-resistant penicillin, penicillin, peripheral opioid receptor antagonists, peripheral opioid receptor mixed agonists / antagonists, peripheral vasodilators, peripheral-acting anti-obesity drugs, phenothiazine antiemetics, phenothiazine antipsychotics, phenylpiperazine antidepressants, phosphate binders, PI3K inhibitors, blood Serum expanders, platelet aggregation inhibitors, platelet stimulants, polyenes, potassium-sparing diuretics including thiazides, potassium-sparing diuretics, probiotics, progesterone receptor modulators, progestins, prolactin inhibitors, prostaglandin D2 antagonists, protease inhibitors, protease-activated receptor 1 antagonists, proteasome inhibitors, proton pump inhibitors, psoralens, psychotropic drugs, combinations of psychotropic drugs, purine nucleosides, pyrrolidine anticonvulsants, quinolones, radiocontraceptives, radioactive adjuvants, radiotherapeutic drugs, radioconjugates, radiopharmaceuticals.Recombinant human erythropoietin, renin inhibitors, respiratory agents, respiratory inhalation products, rifamycin derivatives, salicylic acid, sclerosing agents, second-generation cephalosporins, selective estrogen receptor modifiers, selective immunosuppressants, selective phosphodiesterase-4 inhibitors, selective serotonin reuptake inhibitors, serotonin-norepinephrine reuptake inhibitors, serotonergic neurolubricating modulators, sex hormone combinations, sex hormones, SGLT-2 inhibitors, skeletal muscle relaxant combinations, bone Muscle relaxants, smoking cessation agents, somatostatin and somatostatin analogs, spermicides, statins, sterile washing solutions, streptogramin, streptomyces derivatives, succinimide anticonvulsants, sulfonamides, sulfonylureas, synthetic ovulation stimulants, tetracyclic antidepressants, tetracyclines, therapeutic radiopharmaceuticals, therapeutic vaccines, thiazide diuretics, thiazolidinediones, thioxanthenes, third-generation cephalosporins, thrombin inhibitors, thrombolytic agents, thyroid agents, TNF-alpha inhibitors Harmful agents, topical acne agents, topical agents, topical allergy diagnostic agents, topical anesthetics, topical anti-infective agents, topical antirosacea agents, topical antibiotics, topical antifungal agents, topical antihistamines, topical antitumor agents, topical antipsoriasis agents, topical antiviral agents, topical astringents, topical wound cleansers, topical depigmentants, topical emollients, topical keratolytic agents, topical nonsteroidal anti-inflammatory drugs, topical photochemotherapeutic agents, topical rubefacient agents, topical steroids, topical steroids including anti-infective agents, trans tyretin benzoate Examples of drugs include sterilizers, triazine anticonvulsants, tricyclic antidepressants, trifunctional monoclonal antibodies, ultrasound contrast agents, upper respiratory tract conjugates, urea anticonvulsants, urea cycle disruptors, urinary antiinfectives, urinary antispasmodics, urinary pH adjusters, uterine contraction agents, vaccine combinations, vaginal antiinfectives, vaginal preparations, vasodilators, vasopressors, VEGF / VEGFR inhibitors, viral vaccines, mucus supplements, vitamin and mineral combinations, vitamins, or VMAT2 inhibitors. The drug delivery devices of this disclosure include epinephrine, Rebif, Enbrel, Aranesp, atropine, pralidoxime chloride, diazepam, insulin, antropine sulfate, avibactam sodium, bendamustine hydrochloride, carboplatin, daptomycin, epinephrine, levetiracetam, oxaliplatin, paclitaxel, pantoprazole sodium,Treprostinil, vasopressin, voriconazole, zoledronic acid, mometasone, fluticasone, ciclesonide, budesonide, beclomethasone, vilanterol, salmeterol, formoterol, umeclidinium, glycopyrrolate, tiotropium, acridinium, indacaterol, salmeterol, A drug selected from ru and olodaterol may be administered.

[0102] As described above, any of the various drugs can be delivered using a drug delivery device. Examples of drugs that can be delivered using the drug delivery devices described herein include Remicade® (infliximab), Stellara® (ustekinumab), Simponi® (golimumab), Simponi Aria® (golimumab), Darzalex® (daratumumab), Tremfya® (guselkumab), Eprex® (epoetin alfa), Risperdal Constra® (risperidone), Invega Sustenna® (paliperidone palmitate), Spravato® (esketamine), ketamine, and Invega Trinza® (paliperidone palmitate).

[0103] Drug Housing As described above, dosage forms may be provided in holders suitable for the specific dosage form being used. For example, a drug in liquid dosage form may be held in a holder in the form of a vial with a stopper or a syringe with a plunger before administration. For example, a drug in solid or powder dosage form as a tablet may be housed in a housing positioned to securely hold the tablet before administration.

[0104] The housing may comprise one or more drug holders, each holder containing a dosage form, for example, the drug may be in tablet form, and the housing may be in the form of a blister pack in which the tablets are held within each of the holders. The holders may be in the form of recesses in the blister pack.

[0105] Figure 6 shows a housing 630 comprising a plurality of drug holders 610, each containing a dosage form 611. The housing 630 may have at least one environmental sensor 94 configured to sense information about the environment in which the housing 630 exists, such as ambient temperature, time, or location. The housing 630 may include at least one device sensor 92 configured to sense information about the drugs of the dosage forms 611 contained within the holders 610. There may be a dedicated position sensor 98 configured to determine the geographical location of the housing 630, for example, via satellite positioning such as GPS.

[0106] The housing 630 may include an indicator 85 configured to provide the user of the drug housing with information regarding the status of the drug dosage form 611 contained within the holder 610. The housing 630 may also include a communication interface 99 that can communicate information externally via wired or wireless transmission of data relating to the drug housing 630, the environment, time, or location, and / or the drug itself.

[0107] If necessary, the housing 630 may include a power supply 95 for supplying power to one or more electrical components of the housing 630. The power supply 95 may be a power supply integrated with the housing 630 and / or a mechanism for connecting the housing 630 to an external power supply. The housing 630 may also include a device computer system 90, including a processor 96 and memory 97, which is powered by the power supply 95 and communicates with each other and optionally with other electrical and control components of the housing 630, such as an environmental sensor 94, a position sensor 98, a device sensor 92, a communication interface 99, and / or an indicator 85. The processor 96 is configured to acquire data from the environmental sensor 94, the device sensor 92, the communication interface 99, the position sensor 98, and / or the user interface 80, process it, and provide data outputs to, for example, the indicator 85 and / or the communication interface 99.

[0108] The housing 630 may be in the form of packaging. Alternatively, additional packaging may exist to house and surround the housing 630.

[0109] The holder 610 or additional packaging may itself comprise one or more of the device computer systems, including, as described above, a device sensor 92, an environmental sensor 94, an indicator 85, a communication interface 99, a power supply 95, a position sensor 98, and a processor 96 and memory 97.

[0110] Electronic communications As described above, the communication interface 99 may be associated with the drug delivery device 500 or drug housing 630 by being contained within or on the housing 30, 630, or alternatively, within or on the packaging 35. Such a communication interface 99 may be configured to communicate with a remote computer system, such as the central computer system 700 shown in Figure 7. As shown in Figure 7, the communication interface 99 associated with the drug delivery device 500 or housing 630 is configured to communicate with the central computer system 700 from any number of locations, such as a medical facility 706, such as a hospital or other medical center, a home base 708 (e.g., a patient's home or office, or a caretaker's home or office), or a mobile location 710, via the communication network 702. The communication interface 99 may be configured to access the system 700 via wired and / or wireless connections to the network 702. In one exemplary embodiment, the communication interface 99 in Figure 6 is configured to access the system 700 wirelessly, for example, via a Wi-Fi connection, thereby facilitating accessibility of the system 700 from virtually any location in the world.

[0111] Those skilled in the art will understand that the system 700 may include security features such that the configuration of the system 700 available to any particular user may be determined, for example, based on the user's identification information and / or the location from which the user is accessing the system. To this end, each user may have a unique username, password, biometric data, and / or other security credentials to facilitate access to the system 700. The received security parameter information may be checked against a database of authorized users to determine whether the user is authorized and to what extent the user is permitted to interact with the system, view information stored in the system, etc.

[0112] Computer system As discussed herein, one or more embodiments or features of the subject matter described herein, for example, components of the central computer system 700, processor 96, power supply 95, memory 97, communication interface 99, user interface 80, device indicator 85, device sensor 92, environmental sensor 94, and position sensor 98, can be implemented as digital electronic circuits, integrated circuits, application-specific integrated circuits (ASICs), field-programmable gate array (FPGA) computer hardware, firmware, software, and / or combinations thereof. These various embodiments or features may include the execution of one or more computer programs executable and / or interpretable on a programmable system including at least one programmable processor, the processor may be a dedicated or general-purpose processor connected to receive and transmit data and instructions from a storage system, at least one input device, and at least one output device. The programmable system or computer system may include clients and servers. Clients and servers are generally geographically distant from each other and typically interact via communication networks, such as the Internet, wireless wide area networks, local area networks, wide area networks, or wired networks. The client-server relationship arises from computer programs running on each computer that have a client-server relationship with each other.

[0113] A computer program, also known as a program, software, software application, application, component, or code, contains machine instructions for a programmable processor and can be implemented in a high-level procedural language, object-oriented programming language, functional programming language, logic programming language, and / or assembly / machine language. As used herein, the term “machine-readable medium” means any computer program product, equipment, and / or device, such as magnetic disks, optical disks, memory, and programmable logic devices (PLDs), which are used to provide machine instructions and / or data to a programmable processor, including machine-readable medium that receives machine instructions as machine-readable signals. The term “machine-readable signal” means any signal used to provide machine instructions and / or data to a programmable processor. A machine-readable medium can non-temporarily store such machine instructions, such as non-transient solid memory or magnetic hard drives, or any equivalent storage medium. Machine-readable media can store such machine instructions in an alternative or additional manner, for example, in a temporary manner such as a processor cache or other random-access memory associated with one or more physical processor cores.

[0114] To provide user interaction, one or more embodiments or features of the subject matter described herein, for example, the user interface 80 (which may be integrated into or separate from the administration device 500 or housing 630), may be implemented on a computer having a display screen such as a cathode ray tube (CRT), liquid crystal display (LCD), or light-emitting diode (LED) monitor for displaying information to the user. The display screen may allow input to the display screen directly (e.g., as a touchscreen) or indirectly (e.g., via input devices such as a keypad or voice recognition hardware and software). User interaction can be provided in a similar manner using other types of devices. For example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback, and input from the user may be received in any form, including but not limited to acoustic input, voice input, or tactile input. As described above, this feedback may be provided via one or more device indicators 85 in addition to the user interface 80. The device indicator 85 may interact with one or more of the device sensor 92, the environment sensor 94, and / or the position sensor 98 in order to provide this feedback or to receive input from the user.

[0115] Figure 8 shows an exemplary embodiment of computer system 700, indicated as computer system 800. The computer system includes one or more processors 896 configured to control the operation of computer system 800. The processors 896 may include any type of microprocessor or central processing unit (CPU), including a programmable general-purpose or dedicated microprocessor, and / or one of various dedicated or commercial single or multiprocessor systems. Computer system 800 also includes one or more memories 897 configured to provide temporary storage for code executed by processor 896, or for data obtained from one or more users, storage devices, and / or databases. Memory 897 may include read-only memory (ROM), flash memory, one or more different types of random access memory (RAM) (e.g., static RAM (SRAM), dynamic RAM (DRAM), or synchronous DRAM (SDRAM)), and / or combinations of memory technologies.

[0116] Various elements of the computer system are coupled to the bus system 812. The illustrated bus system 812 is an abstraction representing any one or more separate physical buses, communication lines / interfaces, and / or multidrop or point-to-point connections connected by appropriate bridges, adapters, and / or controllers. The computer system 800 also includes one or more network interfaces 899 (also referred to herein as communication interfaces), one or more input / output (IO) interfaces 880, and one or more storage devices 810.

[0117] The communication interface 899 is configured to allow the computer system to communicate with remote devices, such as other computer systems and / or device 500 or housing 630, via a network, or may be, for example, a remote desktop connection interface, an Ethernet adapter, and / or other local area network (LAN) adapters. The I / O interface 880 includes one or more interface components for connecting the computer system 800 to other electronic devices. For example, the I / O interface 880 may include high-speed data ports such as a Universal Serial Bus (USB) port, a 1394 port, Wi-Fi, or Bluetooth. Additionally, the computer system may be accessible to human users, and therefore the I / O interface 880 may include a display, speakers, a keyboard, a pointing device, and / or various other video, audio, or alphanumeric interfaces. The storage device 810 includes any conventional medium for storing data in a non-volatile and / or non-transient manner. Thus, the storage device 810 is configured to hold data and / or instructions in a persistent state in which the values ​​are retained despite power interruptions to the computer system. The storage device 810 may include one or more hard disk drives, flash drives, USB drives, optical drives, various media cards, diskettes, compact discs, and / or any combination thereof, and may be directly connected to a computer system or remotely connected to a computer system, such as via a network. In an exemplary embodiment, the storage device 810 includes, for example, a tangible or non-temporary computer-readable medium configured to store data, such as a hard disk drive, flash drive, USB drive, optical drive, media card, diskette, or compact disc.

[0118] The elements illustrated in Figure 8 may be some or all of the elements of a single physical machine. Furthermore, not all of the illustrated elements need to be located on or within the same physical machine.

[0119] Computer system 800 may include a web browser for searching for web pages or other markup language streams, presenting those pages and / or streams (visually, audibly, or otherwise), executing scripts, controls, and other code on those pages / streams, accepting user input to those pages / streams (e.g., to complete input fields), issuing HyperText Transfer Protocol (HTTP) requests to those pages / streams, or otherwise (e.g., to submit information from completed input fields to a server). Web pages or other markup languages ​​may be HyperText Markup Language (HTML), or other conventional forms including Embedded Extensible Markup Language (XML), scripts, controls, etc. Computer system 800 may also include a web server for generating and / or delivering web pages to client computer systems.

[0120] As shown in Figure 7, the computer system 800 in Figure 8 may form a component of a central computer system 700 that communicates with one or more of the device computer systems 90 of one or more individual drug delivery devices 500 or housings 630, as described above. Data such as operational data of the devices 500 or housings 630, and patient medical data acquired by such devices 500 or housings 630, may be exchanged between the central and device computer systems 700 and 90.

[0121] As described above, the computer system 800 may also be integrated into or adjacent to the drug delivery device 500 or housing 630 to form a component of the device computer system 90. In this regard, one or more processors 896 correspond to processor 96, the network interface 799 corresponds to communication interface 99, the I / O interface 880 corresponds to user interface 80, and memory 897 corresponds to memory 97. Furthermore, additional storage devices 810 may also be present within the device computer system 90.

[0122] In one exemplary embodiment, the computer system 800 may form a device computer system 90 as a single unit, for example, a single package 35 of one or more drug administration devices 500 housed in a single drug administration device housing 30, or a housing 630 having a plurality of drug holders 610. The computer system 800 may form a central computer system 700 as a single unit, as a single server, or as a single tower.

[0123] A single unit may be modular so that its various forms can be swapped in / out as needed for, for example, upgrades, replacements, or maintenance, without interrupting the functionality of any other form of the system. Thus, a single unit can also be made expandable by the ability to add additional modules, and / or to enhance the functionality of existing modules as desired and / or improved.

[0124] The computer system may also include, for example, an operating system and a database management system, among other various software and / or hardware components. While exemplary computer systems are illustrated and described herein, it will be understood that these are for general concepts and convenience. In other embodiments, the computer system may differ in architecture and operation from those shown and described herein. For example, memory 897 and storage device 810 may be integrated together, or the communication interface 899 may be omitted if communication with another computer system is not required.

[0125] Implementation form In at least some implementations, the communication interface, such as the communication interface 99 described above, may be configured to communicate securely and anonymously with a remote computer system, such as the central computer system 700 described above. In this way, data relating to a patient's drug administration device, drugs that can or have been distributed from the device, and / or physiological parameters can be transmitted from the communication interface to the remote computer system without identifying patient information that would compromise the patient's privacy if intercepted by an unauthorized third party. A remembered link can be established between the device including the communication interface, for example, any of the drug administration devices in Figures 1 to 5B, any of the drug housings 30 and 630 in Figures 5B and 6, the packaging 35 in Figure 5B, sensors, etc., and the remote computer system to facilitate this secure and anonymous communication of data. In exemplary embodiments, a stored link includes established keys unique to the device and the remote computer system, stored in each of the device and the remote computer system, so that the remote computer system can receive anonymous data from the device, but can use the keys to accurately identify the data as data from that particular device, and therefore as data related to a particular patient associated with that particular device, which has been previously programmed in the computer system or is available from another computer system. Thus, the remote computer system can aggregate the data received from the device, as well as data related to the device, drug, and / or patient, to evaluate the patient's condition and treatment, and / or the effectiveness of the device and / or drug. The evaluation can be performed manually by a healthcare professional or automated by the remote computer system.

[0126] Identifying data as data relevant to a specific patient does not necessarily require identifying the patient's complete details. Basic-level identification of data as data relevant to a specific patient can preserve patient privacy. Therefore, while individual data identification is not possible, it is still possible to aggregate multi-bit data related to a single patient. This allows for the collection of anonymized data that can be used to evaluate correlations and trends related to drug administration or other conditions the patient encounters. This anonymized data can also be used as a substitute for a control group as part of a clinical trial.

[0127] The computer system is configured to establish unique keys for each of multiple drug delivery devices, drug housings, packaging, and / or sensors, enabling the computer system to aggregate data from each of the different sources, thereby enabling data analysis across different patients and / or across different devices / housing / packaging. Such analysis can be beneficial for a variety of reasons, including enabling evaluation of treatment for different patients to obtain optimal clinical outcomes, enabling assessment of patient compliance to individual medical treatment plans, and / or enabling insurance companies to more effectively correlate drug use with drug costs.

[0128] The stored links use encryption to achieve secure, private, and anonymous data communication. In exemplary implementations, the computer system includes a server configured with a key-based security system, such as a public-key / private-key cryptography system, to enable data encryption and decryption. In exemplary embodiments, the server is remotely located relative to a drug administration device, housing, or other device communicating with them. Thus, the server includes a database, such as memory 897, and / or additional storage device 810, configured to store the public and private keys of devices configured to communicate with the system. The public and private keys may be generated by the server using cryptographic algorithms. The keys may be used to encrypt data for transmission and to decrypt encrypted data received from different computing devices. In such a system, data can be encrypted using the public key corresponding to the intended data recipient, but the encrypted data can be decrypted using only the recipient's private key. In at least some embodiments, the server includes a cryptographic system, such as a public key infrastructure (PKI), where one or more third parties known as "certification authorities" can prove ownership of the public and private key pair. Examples of key-based security systems include the Diffie-Hellman key exchange protocol, the Digital Signature Standard (DSS) protocol, the Password Authentication Key Agreement protocol, the Rivest-Shamir-Adelman (RSA) encryption algorithm, the Cramer-Shoup cryptosystem, and the YAK Authentication Key Agreement protocol.

[0129] More specifically, encryption is achieved using algorithms that encrypt and decrypt messages by using a key to convert text or other data into an unrecognizable digital format, and then restoring it to its original format. The longer the key, the more computation is required to decrypt the code. Computer keys consist of bits of information of varying lengths. For example, an 8-bit key has 256 (2 to the power of 8) possible values. In another example, a 56-bit key creates 72,000 trillion possible combinations. If the key is 128 bits long, i.e., equivalent to a 16-character message on a personal computer, a brute-force attack is 47 quintillion (4,700,000,000,000,000,000,000) times more difficult to crack than a 56-bit key. Encryption generally prevents misuse of data, even in the rare case that transmitted data is intercepted by an unauthorized third party.

[0130] A unique identification (ID) number or code is registered and stored in the device's memory, for example, in the memory 97 of device 500 in Figure 5B, during the manufacturing process before the device is put into use. While the ID number / code is unique to a device, it may include additional identification information, such as a model or model family number or code, which may be common to multiple devices and useful for analyzing common trends across multiple related devices. In exemplary embodiments, the ID number is transmitted to a computer system along with data from a drug delivery device, drug, and / or sensor, allowing the computer system to easily identify that the data was received from that particular device. The computer system can perform this identification in various ways, such as by correlating the ID number / code of a device that can communicate with the device with a specific key, or by searching for the ID number / code in a lookup table stored in the computer system, so that the computer system can identify a previously generated key to decrypt the data received from the device. The lookup table can also correlate the ID number / code with a specific device and / or a specific patient associated with that device. The ID number / code is not encrypted in the data transmitted from the device to the computer system, which may allow the computer system to read the ID number / code and identify the correct key to use for decryption.

[0131] A key generated in a computer system to communicate with a specific device, such as any of the drug delivery devices in Figures 1 to 5B, any of the drug housings 30 and 630 in Figures 5B and 6, the packaging 35 in Figure 5B, a sensor, etc., is shared with the device as described above and stored in the device's memory. In some embodiments, the device may perform key generation and send the key to the computer system for storage, rather than the computer system generating the key and sending it to the device for storage. However, since a remotely located computer system typically has higher processing power than a device, in exemplary embodiments, key generation occurs in the remotely located computer system. In other embodiments, each of the computer system and the device participates in key generation so that the key is sent to one of the computer system and the device, using a specific key generation protocol that will be understood by those skilled in the art. This can help improve security by preventing the key from being intercepted by an unauthorized third party.

[0132] As described above, the keys stored in the drug delivery device can individually identify the drug delivery device and the patient associated with it. In exemplary embodiments, the drug delivery device may store only one key. In such embodiments, it is intended that only one patient will use the drug delivery device. In other exemplary embodiments, the drug delivery device may store multiple keys, each of which individually identifies the drug delivery device and one of several patients associated with it. Thus, the drug delivery device may be used by each of several patients and may be configured to send and receive data specific to only one of those patients based on the key used to send and receive data. The drug delivery device may be used by multiple patients if, for example, the drug holder of the drug delivery device is configured to be removed from the drug delivery device after the drug has been delivered from the drug holder and replaced with a second drug holder containing the drug to be delivered from the drug delivery device.

[0133] The data transmitted from the device to the computer system may include any of various types of data. In an exemplary embodiment, the data represents sensed information collected by one or more sensors configured to sense information about at least one of the drug administration device and the drug, such as one or more of the device sensor 92, environmental sensor 94, and position sensor 98 described above.

[0134] The data transmitted from the sensor to the computer system may include information about the patient's physiological parameters. The sensor may be configured to sense physiological parameters such as blood glucose levels, blood oxygen saturation, body weight, or sleep duration. Further examples of physiological features that can be sensed by the sensor include blood pressure, sweating level, respiratory rate, heart rate, core temperature, tremor detection, metabolic rate, and inflammatory response. Physiological parameters may also include nutritional intake. Nutritional intake can be assessed by imaging the food consumed by the patient. Alternatively, nutritional intake may be manually recorded by the patient.

[0135] The sensors described herein may be configured to collect data on various conditions, such as device conditions (e.g., sensed by device sensor 92), environmental conditions (e.g., sensed by environmental sensor 94), and location conditions (e.g., sensed by location sensor 98). Examples of conditions include geographical location (e.g., sensed by a location sensor configured to sense GPS or other location), time (e.g., sensed by a clock device such as a timer or electromagnetic clock), date (e.g., sensed by a timer), temperature (e.g., sensed by a temperature sensor), ultraviolet (UV) irradiation (e.g., sensed by a UV sensor configured to sense UV levels), humidity (e.g., sensed by a humidity sensor configured to sense humidity levels), contact (e.g., sensed by a contact sensor), and pressure (e.g., sensed by a pressure sensor).

[0136] Using the universal drug administration device 500 in Figure 5B and the computer system 700 in Figure 7 as examples, the drug administration device 500 can manage data storage operations and data transmission operations between the device 500 and the system 700 using a key-based security system. Keys can be established between the device 500 and the computer system 700 using one of various key establishment protocols. The keys can be stored in the device 500's memory 97 and also in the computer system 700's memory, enabling the device 500 to use the keys to encrypt data and securely transmit the encrypted data to the computer system 700 in an anonymous manner that does not identify the device 500 or the associated patient. The device's memory 97 can also internally store the device 500's unique ID number / code. The device's processor 96 may be configured to use the keys when encrypting data indicating information sensed by one or more of the device's sensors 92, 94, and 98. The data may include metadata of the sensed information, such as the time and date the data was collected. The device's processor 96 may be configured to wirelessly transmit encrypted data to the system 700 via the device 500's communication interface 99. The computer system 700 then receives the data via its communication interface, identifies the correct key stored in its memory for use in decrypting the received data, and can then decrypt the received data using the identified, stored key. In this way, the computer system 700 may be configured to remove the anonymized aspects of the data so that the device 500 and patient associated with the data can be identified. This is because the computer system 700 already knows that the key is associated with the particular device 500 and patient. As described elsewhere in this specification, if precise patient identification is not required, the level of anonymity removal may maintain some degree of patient privacy.Conversely, a third party without the authority to intercept data transmitted by device 500 cannot remove the anonymized aspects of the data, and therefore, even if interception occurs, patient privacy is maintained. The drug administration device 500 can encrypt all data transmitted from device 500 to system 700 using a generated key. The computer system 700 can also encrypt all data transmitted from there to device 500 using a generated key stored therein, and device 500 can decrypt such information using its stored key. Examples of data transmitted from the system 700 to the device 500 include, in embodiments not configured to automatically transmit sensed information to the system 700, requests to the device 500 to transmit sensed information to the system 700, requests to the device 500 to initiate drug delivery from the device 500, and requests to the device 500 to allow the user to manually perform drug delivery from the device 500 by changing at least one variable parameter of an algorithm stored in the device 500 to administer a drug dose to a patient from the device 500, for example, by changing the device operation prevention mechanism 40 or 25 of the device 500 from a locked state to an unlocked state.

[0137] Figure 9 shows one embodiment of a drug delivery system 950, which includes a cloud computing system 951 configured to communicate with one or more devices in a secure and anonymous manner using a key-based security system. The drug delivery system 950 in this illustrated embodiment includes a drug delivery device 952 configured to communicate with the cloud computing system 951 using a key-based security system, a smart mobile device 953 configured to communicate with the cloud computing system 951 and the drug delivery device 952, a patient 954 to whom drugs are delivered from the drug delivery device 952 and configured to interact with the mobile smart device 953, one or more apps 955 installed on the smart device 953 and configured to facilitate patient interaction with the smart device 953 associated with the drug delivery device 952, and a computer system for the pharmaceutical company related to the drug, which pushes informational notifications to the app 955 (for example, to provide software updates to the app 955). The system includes a pharmaceutical company's computer system 956 configured to communicate electronically with a drug delivery device 952 (for example, to push drug-related notifications to the drug delivery device 952 and provide them to the patient 954 via the user interface of the device 952), a payer database 957 configured to store payer data related to the patient 954 and to be accessible to the cloud computing system 951, a manufacturing database 958 configured to store drug data related to the manufacture of the drug and to be accessible to the cloud computing system 951, and a patient database 959 configured to store patient data related to the patient 954 and to be accessible to the cloud computing system 951, the patient 954, and the smart device 953. The patient database 959 includes data-side healthcare provider (HCP) data relating to the patient 954, which is configured to be accessible to the cloud computing system 951.The patient database 959 also includes patient-side HCP data relating to patient 954, which is configured to be accessible to patient 954, such as via a smart device 953 under the patient's control.

[0138] A key can be established between the drug delivery device 952 and the cloud computing system 951 using one of various key establishment protocols. The key can be stored in the memory of the device 952 and also in the memory of the cloud computing system 951, enabling the device 952 to use the key to encrypt data and transmit the encrypted data securely and anonymously to the computer system 951, without identifying the device 952 or the associated patient 954. The device's memory can also internally store a unique ID number / code for the device 952. The device's processor can be configured to use the key when encrypting data indicating information sensed by one or more of the device's sensors. Alternatively, the device may be the sensor itself and therefore configured to use the key when encrypting data indicating the information it senses. The data may include metadata of the sensed information, such as the time and date the data was collected. The device's processor can be configured to transmit the encrypted data wirelessly to the system 951 via the device's communication interface. Next, system 951 can receive data via its communication interface, identify the correct key stored in its memory from the received data for use in decrypting the received data, and then decrypt the received data using the identified, stored key. In this way, system 951 can be configured to remove the anonymized aspects of the data so that the device 952 and patient 954 associated with the data can be identified. This is because system 951 already knows that the key is associated with the particular device 952 and patient. Conversely, a third party without the authority to intercept the data transmitted by device 952 cannot remove the anonymized aspects of the data, and therefore, even if interception occurs, the patient's privacy is maintained. The drug delivery device 952 can use the generated key to encrypt all data transmitted from device 952 to system 951.System 951 can also encrypt all data transmitted from it to device 952 using a generated key stored therein, and device 952 can decrypt the information using the stored key. Examples of data transmitted from system 951 to device 952 include, in embodiments where device 952 is not configured to automatically transmit sensed information to system 951, a request to device 952 to transmit sensed information to system 951; in another example, a request to device 952 to initiate drug delivery from device 952 to patient 954; and in yet another example, a request to device 952 to allow the user to manually initiate drug delivery from device 952 by changing at least one variable parameter of an algorithm stored in device 952 to administer a drug dose from device 952 to patient 954, for example, by changing the device operation prevention mechanism of device 952 from a locked state to an unlocked state. In at least some embodiments, keys may be similarly established and used between the cloud computing system 951 and each of one or more of the other computer systems 953, 957, 958, and 959 within system 950, and the cloud computing system 951 is configured to communicate with them.

[0139] Figure 10 is a flowchart illustrating an exemplary embodiment of Method 900 using a key-based security system. Method 900 is described with respect to the drug delivery device 500 in Figure 5B and the system 700 in Figure 7 for ease of explanation, but other devices and systems, such as the sensor itself if not part of the drug delivery device, can be implemented similarly as described above. The key-based system is used to encrypt and decrypt data transmitted between the drug delivery device 500 and the system 700, so that the data can be passed in a secure, confidential, and anonymized manner.

[0140] In operation 905, the key-based security system establishes a unique key for wireless communication between the drug delivery device 500 and a system 700 located remotely from the device 500. In at least some embodiments, a server configured within the system 700 implements the key-based security system. The unique key is stored in the memory of the remotely located server, as well as in any additional storage devices that may be configured within the system 700. The system 700 can transmit the key to the device 500 for storage in its memory 97, or, as described above, the device 500 may be configured to generate its own key for a pair of keys used in the key-based security system.

[0141] In operation 910, the drug delivery device 500 uses one or more of the sensors 92, 94, and 98 to sense information about at least one of the drug delivery device 500 and the drug being dispensed from it. The sensed information may include, for example, data related to the dosage and the delivery schedule of the drug to be administered via the drug delivery device 500.

[0142] In operation 915, the processor 96 of the drug delivery device 500 encrypts and anonymizes the data indicating the sensed information using a generated key stored in memory 97. In operation 920, the processor 96 anonymizes and encrypts the data before transmission to the remotely located computer system 700, so that when transmitted, the data is sent in a secure, encrypted form. The transmission in operation 920 also includes a unique ID number / code for the device to facilitate the decryption of the data received from the device 500 by the computer system.

[0143] In operation 925, if the drug delivery device 500 receives encrypted data from the system 700, the drug delivery device 500 decrypts the received data using a key stored in memory 97.

[0144] With respect to a sensor configured to sense information about a patient's physiological parameters, the sensor may be configured to periodically acquire information about the physiological parameters, for example, at least once every 24 hours, once every 12 hours, once every 3 hours, once every hour, once every 30 minutes, or once every 10 minutes. This can be selected according to the frequency of the data required. This data can then be transmitted anonymously to a server at the corresponding or less frequent frequencies as necessary, as described herein. Thus, the sensor may enable data collection in an anonymous manner without the risk of identifying the original patient, and therefore facilitate obtaining patient consent regarding the collection of patient data.

[0145] A single patient may have multiple sensors to measure different parameters, which may be further physiological parameters. These sensors are all related to the same patient within the system, enabling the aggregation of data on a server regarding this patient.

[0146] In addition to physiological information acquired by sensors, data related to a single patient may also be acquired. For example, a patient-related drug delivery device may also transmit patient-related data, as described herein, which can be aggregated with physiological information on a server to provide an indication of the physiological response to the performance of a particular drug delivery device.

[0147] Each of the multiple patients may have at least one sensor to measure physiological parameters. Each sensor is associated with each patient in the system, enabling the storage of patient-specific data. This allows for the collection of many data points across a range of patients, which can help in detecting trends and correlations. Specifically, each of the multiple patients may have multiple sensors contributing to more data points that support further analysis of observed outcomes. Each of the multiple patients may also have a drug administration device associated with them, providing additional data to the server.

[0148] In one embodiment of the operation, a sensor configured to sense information about a patient's physiological parameters senses the physiological parameters.

[0149] In the next step, the sensor uses a key to anonymize the data indicating the sensed physiological parameters and wirelessly transmits this data to a remotely located communication interface. This is repeated periodically, for example, once every 24 hours. Periodic measurements can be repeated for at least 24 hours, such as 48 hours, 7 days, 14 days, 30 days, 90 days, 120 days, 180 days, or 365 days. In this way, it is possible to complete short-term tests over a few hours or days, but it is also possible to accumulate more data over longer periods to enable highly accurate tests. For example, if the physiological parameters being monitored include blood glucose levels and nutritional intake such as carbohydrate intake and body weight, this process can be repeated for 365 days to provide highly accurate long-term glucose monitoring that cannot be achieved with conventional methods. This allows for better provision of information for actual treatment algorithms.

[0150] If a patient has a first sensor and a second sensor, each configured to sense physiological parameters, the first sensor may be configured to sense the patient's blood glucose level, and the second sensor may be configured to sense one or more of nutrient intakes, such as carbohydrate intake, protein intake, and fat intake. Monitoring these parameters can be achieved using various sensors, such as patient sensor 92, as described elsewhere in this specification. Thus, glucose testing can be performed each time the patient eats, providing a more convenient and time-efficient method of glucose tolerance testing than conventional approaches.

[0151] Figure 15 shows one embodiment of a system for accumulating data related to one patient among several patients. The system can identify one patient and therefore extract record data related to this patient. In this embodiment, the extracted data are blood glucose levels, carbohydrate intake, and the patient's response to insulin administration. By analyzing this data, the response ratio to insulin dose / carbohydrate ratio can be provided as a short-term average of 30 days and 7 days. The sensed data also provides average blood glucose levels as a 90-day average for long-term analysis. The ability to extract such data can make it possible to establish trends for individual patient situations. Such patient data can be combined with patients in similar situations to construct a real picture of trends across any particular part of the population. This can be useful in optimizing medication schemes for new patients for whom there is no medical history data.

[0152] Sensor data (and / or other data) received for a specific patient may be automatically uploaded to the patient's electronic health record (EHR) and / or to forms necessary for use in conjunction with a specific drug, such as a patient monitoring form for REMS for esketamine, ketamine, or other controlled substances. Therefore, the EHR and / or forms can be updated accurately and in a timely manner.

[0153] Figure 16 shows one embodiment of a method 1200 for updating a patient monitoring form with data sensed by one or more sensors for a specific patient. The patient monitoring form can also be updated with other data, such as data input to the user interface of a drug delivery device, and transmitted to a remote computer system, such as a central computer system 700. For example, psychological state data can be collected in various ways, such as through the patient's answers to questionnaire questions stored on an external device, user input to one or more questions presented through the user interface of a drug delivery device, such as answers to psychological stress tests, such as the Kessler Psychological Distress Scale (K10) or any of various other indices and scales, or through healthcare provider evaluation notes about the patient stored on an external device. Psychological state data can be used, for example, by a processor to evaluate when a drug should be delivered to the user from the drug delivery device 500 and to determine how the user is responding to the current treatment. For example, a tendency toward improvement in psychological state may indicate effective drug treatment for depression, and as a result, the drug dosage and / or frequency of drug administration may be reduced. In another example, a tendency towards a decline in psychological state or a static tendency in psychological state may indicate that the dosage and / or frequency of drug administration should be increased for a drug used to treat depression.

[0154] In this exemplary embodiment, the parameters to be sensed include the patient's heart rate (HR), respiratory rate (RR), and blood pressure (BP), but other conditions may be sensed as discussed herein. One or more sensors collect data 1202, and the drug delivery device 500 transmits the sensed data to a computer system 700 (or other devices described herein) 1204. The computer system 700 inputs the received sensed data into a patient monitoring form for temporary storage 1206. For each sensed parameter, the computer system 700 determines, as appropriate for the particular condition being measured, whether the sensed data is above a predetermined maximum threshold or below a predetermined minimum threshold. If not, the sensed data is considered normal, e.g., within acceptable limits, and the computer system 700 inputs the sensed data for that sensed condition into the patient monitoring form 1208. If so, the sensed data is considered abnormal, e.g., outside acceptable limits. The computer system 700 determines whether this anomaly determination is a first determination of anomaly for this sensed parameter with respect to this patient. If this anomaly determination is a first determination of anomaly for this sensed parameter with respect to this patient, the sensed data is not yet entered into the patient monitoring form 1208. Instead, after the parameter is sensed again 1202, the computer system 700 receives the sensed parameter data and enters the received sensed data into the patient monitoring form which temporarily holds the data 1206. If the computer system 700 determines that the sensed data is, as appropriate, above a predetermined maximum threshold or below a predetermined minimum threshold with respect to the specific condition being measured, so as to constitute a second instance of anomaly sensed data with respect to this sensed condition, the computer system 700 provides an alert to healthcare professionals, such as staff on-site with the patient using the drug administration device 500, or the patient's healthcare provider, for evaluation and possible interventions 1210.The alerted healthcare worker can, for example, manually review the data on the display screen of the computer system 700 to confirm the abnormal sensing data 1212, and can, for example, provide an input to the user interface of the computer system 700 that triggers an input 1208, thereby causing the sensing data to be entered into the patient monitoring form 1208. The human review of the sensing data and confirmation of abnormal sensing data by the healthcare worker may help enable insurance reimbursement because it involves human activity. If the computer system 700 determines, as appropriate, that the sensing data for a particular condition being measured does not exceed a predetermined maximum threshold and does not fall below a predetermined minimum threshold, the first abnormal determination is considered abnormal, and the computer system 700 enters the sensing data for that sensed condition into the patient monitoring form 1208.

[0155] In other embodiments of Method 1200, the patient monitoring form to be temporarily retained may be omitted. In such embodiments, the patient monitoring form may be populated with all sensing data, even sensing data that was determined to be abnormal on the first occasion 1208, thereby providing a more complete patient record.

[0156] In another embodiment of Method 1200, healthcare workers may be alerted to a first abnormal sensing condition, which may help enable more rapid medical intervention in an emergency.

[0157] In at least some implementations, drug delivery can be modified using data transmitted in a secure and anonymized manner from a device such as one of the drug delivery devices in Figures 1 to 5B, one of the drug housings 30 and 630 in Figures 5B and 6, the packaging 35 in Figure 5B, or a sensor, to a remote computer system such as the central computer system 700 in Figure 7. To modify drug delivery, the remote computer system using the data received in a secure and anonymized manner, as described above, can help ensure that drug delivery from the device is modified based on information verified to be associated with the device. This is because the remote computer system can only decrypt the data if it can identify a suitable key for decryption and possesses that key. In other words, the data self-verifies for use in modifying drug delivery, as the remote computer system can only read the received data and use it to modify drug delivery if the remote computer system and the device have previously established a secure and anonymized communication protocol. However, the data used to modify drug delivery may be transmitted from the device to the remote computer system by means other than the secure and anonymized communication implementations described above.

[0158] When delivering drugs, various factors other than the simple initial drug dose itself can influence drug administration, absorption, and the effects on the patient. For example, the individual patient's physiology or condition, the physiological effects of the drug on the patient, and the external circumstances surrounding the patient can all influence the outcome of drug delivery to the patient. Therefore, it can be beneficial to enable drug delivery to be adjusted based on various different factors that arise during the use of drug delivery devices, providing more personalized treatment while also supporting patients receiving and / or physicians providing specialized care tailored to the specific patient being treated. Furthermore, the ability to automate much of the drug delivery adjustment process can help simplify the delivery process for both patients and physicians, potentially improving patient outcomes.

[0159] In exemplary embodiments, drug delivery may be modified based on instructions from a remote computer system. A drug delivery device, for example, an algorithm stored in its memory, is executable on the device, for example, by its processor, to administer a dose of drug to a patient. The algorithm is stored in the form of one or more sets of data points that define and / or represent instructions, notifications, signals, etc., to control the function of the device and the administration of the drug. Data received by the drug delivery device is used, for example, by the device's processor, as a set of data points via its communication interface, to modify at least one variable parameter of the algorithm. The at least one variable parameter lies among the data points of the algorithm and is included, for example, in instructions for drug delivery, and each can therefore be modified by modifying one or more of the stored data points of the algorithm. After at least one variable parameter has been modified, subsequent executions of the algorithm will administer a different dose of drug according to the modified algorithm. Thus, drug delivery over time can be remotely managed for the patient, for example, by a healthcare professional providing input to a computer system for modifications to drug delivery, thereby increasing the beneficial outcomes of the drug. Modifications to at least one variable parameter and / or one or more doses themselves are automated to improve patient outcomes. Therefore, drug delivery devices can be configured to provide smart systems for drug delivery, offering patient-based, personalized medicine.

[0160] Typically, upgrading a remote computer system is cheaper and / or easier than upgrading a patient's drug delivery device or acquiring a new drug delivery device. Therefore, by offloading processing and variable parameter control to a remote computer system, the lifespan of drug delivery devices can be extended and / or it may be possible to perform a single update (for the remote computer system) rather than multiple updates (for each drug delivery device communicating with the remote computer system).

[0161] In exemplary embodiments, the data on which the device's algorithm is modified includes at least data collected by at least one sensor configured to collect data relating to characteristics of the drug delivery device and / or the drugs that can be delivered therefrom. Thus, the drug delivery device may use local processing to customize drug delivery based on information sensed by the device and, in at least some embodiments, on one or more additional factors such as past drug delivery and dosage data collected by a computer system. If the device includes two or more sensors, each sensor is configured, in exemplary embodiments, to collect data relating to different characteristics in order to help improve the customization of the algorithm by considering a number of factors.

[0162] Examples of sensors that can sense data used to modify the algorithm are sensors 92, 94, and 98 mentioned above. Examples of characteristics that can be sensed by sensors and used to modify the algorithm are the patient's physiological characteristics, the patient's physical characteristics, and the patient's situational characteristics. Any of the various physiological characteristics that can be monitored include blood glucose levels (e.g., using a glucose monitor), blood pressure (e.g., using a blood pressure monitor), sweating levels (e.g., using a fluid sensor), respiratory rate (e.g., using a respiratory monitor, a thermal sensor located near the nose or mouth and configured to detect heat in exhaled breath or the inflow and outflow of air, a pressure sensor located near the nose or mouth and configured to detect pressure in exhaled breath or the inflow and outflow of air, a spirometer, etc.), and heart rate (e.g., using a heart rate monitor).Core temperature (e.g., using a temperature sensor), tremor detection (e.g., using an accelerometer), fall detection (e.g., using an accelerometer), irregular gait detection (e.g., using an accelerometer), time (e.g., using a timer), date (e.g., using a timer), patient activity level (e.g., using a motion sensor), blood pressure (e.g., using a blood pressure monitor), metabolic rate (e.g., using heart rate as described herein), altitude (e.g., using an altimeter), drug temperature (e.g., using a temperature sensor), drug viscosity (e.g., using a viscometer), GPS information (e.g., using a position sensor), weather information (e.g., using a temperature sensor, humidity sensor, etc.), room temperature or ambient temperature (e.g., using a temperature sensor), angular velocity (e.g., using an inertial measurement unit (IMU) or magnetic / angular velocity / gravity (magnetic, angular rate, and Numerous different situational characteristics can be monitored, including gravity (using MARG sensors), body orientation (e.g., using an IMU), motor current used for drug delivery (e.g., using a current sensor), blood oxygen concentration (e.g., using a blood oxygen sensor), sunlight exposure (e.g., using a UV sensor), osmolality (e.g., using a blood monitor), air quality (e.g., using a UV sensor), inflammatory response, one or more images and / or videos of the patient and / or the environment in which the patient is located (e.g., to analyze food intake, to determine whether solid food or liquid food was consumed, to determine the patient's location or activity, to determine the patient's condition such as skin reactions, respiration, eye dilation, sedation, dissociation, and vocal characteristics such as tone and pitch), general health status, pain score, and user input data such as the recurrence cycle of a specific disease.Any of the various different physical characteristics may be monitored, such as metabolic requirements measured using at least one of temperature, metabolic demand, cognitive function, air pollution rate, food intake, and basal metabolic rate (BMR), body weight, and one or more images and / or videos of the patient and / or the environment in which the patient is located (e.g., to analyze food intake, to determine whether solid food or liquid food was consumed, to determine the patient's location or activity, to determine the patient's condition such as skin reactions, etc.). U.S. Patent Application Publication No. 2011 / 0295337, entitled “Systems and Methods For Regulating Metabolic Hormone Producing Tissue,” published on December 1, 2011; U.S. Patent No. 8,696,616, entitled “Obesity Therapy And Heart Rate Variability,” issued on April 15, 2014; U.S. Patent No. 9,427,580, entitled “Devices And Methods For The Treatment Of Metabolic Disorders,” issued on August 30, 2016; and U.S. Patent No. 9,168,000, entitled “Meal Detection Devices And Methods,” issued on October 27, 2015, further describe the identification of types of information relating to food and / or beverages, which are incorporated herein by reference in their entirety. In various embodiments, the sensor includes an imaging device such as a camera, and the processor is configured to analyze images and / or video captured by the imaging device to analyze all food intake and / or determine one or more side effects such as a patient's skin reaction to a drug, the patient's level of sedation, the patient's level of dissociation, and vomiting. Facial ID may be used to identify the patient in images captured by the sensor, including the camera, to help ensure that relevant data is collected and analyzed.U.S. Patent Publication 2012 / 0330684, published on December 27, 2012, entitled "Medication Verification And Dispensing," whose disclosures are incorporated herein by reference, further describes image acquisition devices. U.S. Patent Publication 2002 / 0014951, published on February 7, 2002, entitled "Remote Control For A Hospital Bed," and U.S. Patent Publication 2007 / 0251835, published on November 1, 2007, entitled "Subnetwork Synchronization And Variable Transmit Synchronization Techniques For A Wireless Medical Device Network," whose disclosures are incorporated herein by reference, further consider various sensors.

[0163] Using the universal drug delivery device 500 in Figure 5B and the computer system 700 in Figure 7 as examples, the memory 97 of the device 500 may have algorithms stored internally, and the device's processor 96 may be configured to execute algorithms that control the delivery of drug doses distributed by the device's distribution mechanism 20. The device's communication interface 99 may be configured to receive instructions from the communication interface of the remote computer system 700 requesting a change to at least one variable parameter of the stored algorithm. In response to the instruction, the device's processor 96 may change at least one variable parameter of the algorithm as requested, and as a result, the dose delivered after the change to at least one variable parameter may be configured to be controlled by executing the modified algorithm.

[0164] Figure 11 shows one embodiment of a drug administration system 1050, which includes a local processing system 1051, a remotely located computer system 1052 (located remotely from the local processing system 1051) configured to communicate with the local processing system 1051, and local sensors 1053 (local to the patient associated with the local processing system 1051), each configured to communicate with the local processing system 1051.

[0165] The local processing system 1051 includes a drug delivery device 1054 and a mobile smart device 1055 configured to communicate electronically with the drug delivery device 1054. The memory of device 1054 may store algorithms internally, and the device's processor may be configured to execute algorithms that control the delivery of drug doses distributed by the device's distribution mechanism. The device's communication interface may be configured to receive commands from the communication interface of a remote computer system 1052 requesting a change to at least one variable parameter of the stored algorithm. In response to the command, the device's processor may change at least one variable parameter of the algorithm as requested, and as a result, the dose delivered after the change to at least one variable parameter may be controlled by executing the modified algorithm. Alternatively, the memory of the smart device 1055 may have algorithms stored internally, and the remote computer system 1052 may instead communicate with the smart device 1055 to control algorithm updates, execute the algorithm, and thereby provide commands for drug delivery to the drug delivery device 1054.

[0166] The smart device 1055 and / or the drug delivery device 1054 may be configured to receive data from the sensor 1053 and display information thereon on its user interface. In this illustrated embodiment, the sensor 1053 may be a subcutaneous sensor, a skin patch sensor, an implantable sensor, and a wearable sensor. The received sensor data may be transmitted to the remote system 1052 for analysis, as described herein, which may trigger an algorithm update. The smart device 1055 and / or the drug delivery device 1054 may each include one or more onboard sensors in addition to or instead of any or all of the offboard sensors 1053. The onboard sensor data may be transmitted to the remote system 1052 for analysis, as described herein, which may trigger an algorithm update.

[0167] Figure 12 shows another embodiment of the drug administration system 2000, which includes a universal drug administration device 2002 and a remotely located computer system 3002 configured to communicate with each other. The drug administration device 2002 in this illustrated embodiment includes a housing 2004, a drug holder 2010, a distribution mechanism 2020, at least one sensor 2030, 2040, a memory 2050 configured to internally store an algorithm 2052, a processor 2060, a user interface 2080, an indicator 2085, a power supply 2095, and a communication interface 2099. The computer system 3002 in this illustrated embodiment includes a server 3004, a memory 3050, a user interface 3080, a processor 3060, and a communication interface 3099. Furthermore, as described above with respect to the universal drug administration device 500 in Figure 5B, those skilled in the art will understand that the universal drug administration device 2000 in Figure 12, comprising a drug holder 2010, a distribution mechanism 2020, a processor 2060, a memory 2050, and sensors 2030, 2040, may have the above-described functions in several different combinations. For example, device 2000 may include at least two of the sensors 2030, 2040, and 2045, and may not have a user interface 2080. In this illustrated embodiment, sensors 2030 and 2040 are each included in device 2000, but one or more of sensors 2030, 2040 may be separated from device 2000, for example, by being attached to a patient, located in a geospatial area shared with the patient, attached to another device or instrument, or as part of an application on a mobile phone used by the patient.

[0168] Memory 2050 is configured to store data from sensors 2030 and 2040, but in other embodiments, this data may be stored elsewhere, such as in another memory on device 2000 and / or in a remote memory accessible to device 2000 via a communication interface 2099. The algorithm 2052 stored in memory 2050 represents instructions for device 2000 regarding how to administer a drug in drug holder 2010 and is configured to be executed by processor 2060. The algorithm 2052 is stored in the form of a plurality of data points that define and / or represent instructions, notifications, signals, etc., for controlling drug administration, and at least one variable parameter is common to the data points such that changing at least one variable parameter of algorithm 2052 results in at least one change in the method of drug administration. The at least one variable parameter may be any of a variety of different delivery and / or drug parameters. Examples of variable parameters include the rate of drug delivery from drug holder 2010 to the patient, the time interval between dose deliveries such that the dose delivered after a change in at least one variable parameter differs from the dose delivered before the change, the dose, the concentration, whether any additional doses are delivered, such as stopping a second dose or all subsequent doses, or stopping administration before the first dose or before all subsequent doses after the first dose and then resuming administration, the speed at which the device needle automatically advances into the patient, and the temperature of the drug. Adjusting the speed at which the device needle automatically advances into the patient can be important. This is because if the speed is too slow, it may not enter the patient at all or to the intended depth, and if the speed is too fast, it may cause discomfort to the patient.

[0169] The processor 2060 of device 2002 is configured to execute algorithm 2052 to control the administration of one or more doses of a drug to a patient. In an exemplary embodiment, the processor 2060 executes algorithm 2052 to control the delivery of at least a first dose of the drug to the patient, modifies at least one variable parameter of algorithm 2052 in response to a command from the remote system 3002, and executes algorithm 2052 after modifying at least one variable parameter to control the delivery of at least one subsequent dose of the drug. In some embodiments, the processor 2060 may control the delivery of the first dose by modifying at least one variable parameter of algorithm 2052 before executing algorithm 2052, for example, by changing a variable parameter from one indicating that administration has been stopped (e.g., because the device operation prevention mechanism of the drug delivery device is in a state that prevents drug delivery, or the power supply of the drug delivery device does not have enough power to deliver the dose) to one indicating that administration is permitted (e.g., because the device operation prevention mechanism of the drug delivery device is in a state that allows drug delivery, or the power supply of the drug delivery device has enough power to deliver the dose). To execute algorithm 2052, processor 2060 is configured to execute a program stored in memory 2050 to access multiple data points of algorithm 2052 in memory 2050. To modify at least one variable parameter of algorithm 2052, processor 2060 is configured to modify or update the data point of at least one variable parameter in memory 2050. Processor 2060 may also be configured to execute instructions stored in memory 2050 to control device 2000, which generally includes other electrical components such as communication interface 2099, indicator 2085, and user interface 2080.

[0170] The processor 2060 may be configured to automatically control the delivery of drug doses based on one or more predetermined schedules or dosing intervals for a patient, which may be predetermined before the initial dose or determined during use of the device 2000 after the delivery of the first dose, and which are set so that future doses may be based on a predetermined schedule. The predetermined schedule may also be determined by a physician or other healthcare provider, may be automatically generated based on the algorithms 2052 and / or sensors 2030, 2040 used, or may be several combinations of the two. In at least some embodiments, at least one variable parameter includes the timing between doses, and instructions to change the variable parameter of the timing between doses may be modified based on a new drug delivery schedule input to the system 3002 by an appropriate healthcare professional after recognizing a decline in a particular clinical outcome of the patient, so as to be reflected in the data received by the system 3002 from the device 2000.

[0171] In some cases, a drug delivery device may malfunction and fail to deliver the dose properly, even though the device is activated to deliver the dose. In some cases, a drug delivery device may be activated accidentally, such as when an inhaler delivers the drug before it is inserted into the patient's mouth, or when a nasal spray device delivers the drug through its nozzle before the nozzle is inserted into the patient's nostril. In cases of device malfunction and / or accidental activation, the patient may not receive the prescribed amount of drug, even though the drug delivery device has been activated at least once to deliver the prescribed amount of drug. Therefore, it may be beneficial to increase the maximum number of permissible doses, such as from 1 to 2, 2 to 3, 2 to 4, 3 to 4, 4 to 5, 4 to 6, etc., to ensure that the prescribed amount of drug is actually delivered to the patient. Instructions to change the variable parameters of the maximum number of permissible doses (and / or timing between doses, device lock / unlock status, dose, etc.) may be changed based on input to System 3002 by an appropriate healthcare professional after receiving notification that the device needs to be activated at least one additional time due to device malfunction or accidental activation. Healthcare professionals may receive notification in various ways, such as by being present with the patient when a device malfunction or accidental activation occurs, or by receiving communications from the patient, such as text messages, emails, phone calls, or other notification mechanisms. In an exemplary embodiment, the algorithm may be modified to increase the number of acceptable additional device activations by only one. In other embodiments, the number of acceptable additional device activations may be two or more. However, limiting additional dose delivery to one may help prevent drug abuse and / or allow healthcare professionals to deepen their intervention with the user, for example, by assessing whether additional training is needed if two or more accidental activations are entered before an additional dose is permitted, or by assessing whether a new device is needed rather than an additional dose from a malfunctioning device due to a device malfunction.

[0172] The processor 3060 of the remote system 3002 is configured to receive and analyze data indicating information collected by one or more sensors 2030, 2040 of the drug delivery device, and to send commands to device 2002 to change at least one variable parameter of algorithm 2052 based on this analysis. The processor 3060 is configured to control drug delivery from device 2002 through any of several different mechanisms, such as by sending commands to device 2002 using communication interfaces 2099, 3099, and having the device's processor 2060 execute commands to perform drug delivery (for example, by providing device 2002 with multiple data points that define one or more commands).

[0173] The algorithm is configured to modify based on data collected by one or more of the sensors 2030, 2040, enabling automated response based on patient situation awareness. In at least some embodiments, at least one variable parameter is modified to provide adaptive dose adjustments based on various readings and / or data from one or more of the sensors 2030, 2040. For example, a user of device 2000 can record the cycle time of a disease or disease relapse cycle, at which point the drug administration schedule reflected in algorithm 2052 is adjusted after analysis by the remote processor 3060 to take this into account for better disease management.

[0174] As another example, changes in a patient's altitude can potentially alter the effectiveness of a drug and, in some cases, lead to toxicity. Therefore, the duration during which a patient is at different altitudes can be read by one or more of the sensors 2030, 2040 and used by the remote processor 3060 to adjust subsequent drug dosages by causing the local processor 2060 to change at least one variable parameter.

[0175] In another example, the remote computer system 3002 may be configured to completely discontinue treatment based on one or more sensor readings, and in at least some embodiments, the patient may be notified so through the device indicator 2085 and / or user interface 2080. For example, glucose concentration may drop significantly, activity levels may begin to increase, blood pressure may drop, sweating may increase sharply, insufficient REM cycles in sleep may be detected by a sleep quality sensor, and tremors that may occur may be detected by a tremor detection sensor. These measured characteristics may be analyzed by a remote processor 3060, each of which can be identified as corresponding to hypoglycemia, and thus instruct the device 2002, which is an insulin pump configured to deliver insulin in this example, to terminate insulin delivery by changing at least one variable parameter to reflect a zero dose, for example, by changing the dose to zero or by making the administration frequency an unachievable period. The administration does not wait until the glucose concentration falls below a normal, i.e., safe threshold before responding, but rather terminates rapidly at the onset of any possible hypoglycemic event, allowing the patient's glucose concentration to resume a rapid rise and then return to a healthier, i.e., normal, range and then to the ideal range. Embodiments of the insulin pump are further described in U.S. Patent Application Publication 2009 / 0069787, filed on September 7, 2007, entitled "Activity Sensing Techniques for an Infusion Pump System," which is incorporated herein by reference in its entirety.

[0176] In another example, changing at least one variable parameter may result in a controlled infusion rate, i.e., flow rate, for each dose provided, for example, at least one variable parameter may include the infusion rate, i.e., flow rate. In yet another example, as described in U.S. Patent Application Publication No. 2002 / 0042596, published on April 11, 2002, entitled “Method And Apparatus To Sense Temperature In An Implantable Pump,” which is incorporated herein by reference in its entirety, the temperature of a drug can be varied to produce a constant flow rate.

[0177] In another example, system 3002, for example its processor 3060, can analyze data received from device 2000, such as physiological characteristics data and / or physical characteristics data, and determine that the patient's drug administration frequency is excessive, thereby creating a risk of negative side effects, and in some cases, an overdose.

[0178] The remote system 3002 may be configured to update algorithm 2052 in response to receiving data over a period of time from continuously monitoring a sensed variable, such as a patient's blood glucose level sensed using a glucose monitor. For example, if device 2002 is configured to administer insulin to a patient, algorithm 2052 may be updated in response to monitoring the patient's blood glucose level over an hour, day, week, month, etc. Blood glucose data can be used by system 3002 to determine a modified version of control algorithm 2052, and once the algorithm is delivered as an instruction to update drug delivery device 2002, the amount or timing of insulin that may be administered to the patient can be controlled by processor 2060, which is executing algorithm 2052. In at least some embodiments, control algorithm 2052 may be updated by adding at least one variable parameter to control algorithm 2052. For example, a suitable healthcare professional may want to control drug administration via a secondary parameter, i.e., a control variable, which has not been considered in algorithm 2052 but which the healthcare professional deems appropriate after reviewing the sensed data received by system 3002. In at least some embodiments, the control algorithm 2052 may be updated based on a processor 3060 that completes a calibration routine or process for the drug delivery device 2002. The calibration process may determine one or more calibration variables that may be common to at least one variable parameter of the control algorithm 2052 by determining the accuracy of the device's sensors 2030, 2040 and the accuracy of the dose delivered through the device 2002.

[0179] In at least some embodiments, rather than being automatically updated by system 3002 in response to analysis of data received from device 2002, control algorithm 2052 may be configured to be updated in response to requests from users associated with the drug delivery device 2002, such as a patient using device 2002, who can provide input to device 2002 via user interface 2080, or from healthcare professionals providing treatment guidance to patients, who can provide input to a remote system 3002 located in a medical facility such as medical facility 706 in Figure 7, or in a mobile location such as mobile location 710 in Figure 7. Users may not be aware of algorithm 2052 at all or in detail, and therefore may not specifically request changes to algorithm 2052, but rather may more generally request changes to drug delivery on the device, which are substantially requests for changes to algorithm 2052. For example, a user can establish a communication link with a computer system that communicates with system 3002, such as device 2002, or a computer system located in a medical facility such as medical facility 706 in Figure 7, or a computer system located in a mobile location such as mobile location 710 in Figure 7, and request an update of the control algorithm 2052 based on the adverse effects or clinical outcomes experienced by the patient, indicated by data from sensors 2030, 2040 transmitted to system 3002 and / or inputs to device 2002 transmitted to system 3002 via the user interface 2080.

[0180] System 3002 may be configured to automatically update algorithm 2052 in response to a request by analyzing data received from device 2002 and adjusting algorithm 2052 accordingly. Alternatively, system 3002 may be configured to present the user with one or more alternative control algorithm configurations, e.g., one or more sets of different variable parameter settings for algorithm 2052, which are transmitted to device 2002 and stored, e.g., in memory 2050. The selection of alternative control algorithms available to the user may be determined by the system's processor 3060 based on sensing information received by system 3002 and / or clinical outcomes reported by the patient. System 3002 may be configured so that the user selects one of the presented alternative algorithm configurations, e.g., via the user interface 2080 of device 2002 or the user interface of the computer system the user is using to interact with system 3002, and transmits the variable parameter settings of the selected algorithm to device 2002, so that device 2002 can update algorithm 2052. In other embodiments, the system 3002 may be configured so that the user can modify algorithm 2052 as a medical professional based on a medical professional's analysis of the data received by the system 3002 from device 2002, thereby enabling algorithm 2052 that is more nuanced than the alternative algorithms provided by the system 3002 for the user to choose.

[0181] In at least some embodiments, system 3002 may be configured to perform a bulk update of algorithms stored in each of multiple drug delivery devices. For example, a bulk update may be desirable when a new version of device firmware or operating system becomes available from the device manufacturer. In such cases, each algorithm to be updated by system 3002 is associated with a related drug delivery device, such as each device being the same model or from the same production batch. In another example, a healthcare professional may want to initiate a bulk update of control algorithms in multiple drug delivery devices, each associated with patients belonging to a similar diagnosis group or patients experiencing common side effects. For example, U.S. Patent Application Publication No. 2002 / 0077852, published June 20, 2002, entitled “Infusion Pump With An Electronically Loadable Drug Library And A User Interface For Loading The Library,” which is incorporated herein by reference in its entirety, describes various embodiments of drug delivery parameters and protocols for various drugs deliverable by an infusion pump.

[0182] In at least some implementations, the drug delivery device 2002 may be configured to autonomously update the control algorithm 2052 without explicit user instructions or without a request for an update of the control algorithm 2052 from the system 3002. The drug delivery device 2002 may be configured to check for updates to the control algorithm with respect to one or more of the following: specific algorithm settings, variable parameters, security updates, etc. The drug delivery device 2052 may be configured to continuously search for open communication channels over a wireless network to connect to the system 3002, and when the system 3002 determines the availability of a control algorithm update and determines that an update for the device's algorithm 2052 is available, it may request that the update be sent to the device 2002 so that the algorithm 2052 can be modified according to the update. Such a configuration may prevent the system 3002 from sending update requests to devices that are not currently available for updates, for example, because the device is turned off because it is no longer used by a patient, or because the device is outside the network's communication range. Alternatively, once a communication channel is established, the drug delivery device 2002, for example its processor 2060, may be configured to receive the latest available version of the control algorithm from the system 3002, compare the version received from the system 3002 with the currently installed version of the algorithm 2052 stored in the device's memory 2050 to determine if an update is necessary, and, if necessary, update the stored algorithm 2052 by replacing it with the latest available version.

[0183] When the drug delivery device 2002 recognizes that an update to the control algorithm 2052 is available, the device 2002 may be configured to generate a notification to a user associated with the device 2002, such as a patient or a healthcare professional associated with the patient, and to identify any further input required to install the control algorithm update, either by continuously searching channels to check for the algorithm update or by periodically sending pings to the system 3002 requesting the algorithm update according to a predetermined schedule. The notification may be provided in various ways, such as audio and / or visual alerts, via the device's user interface 2080, via the system's user interface 3080, or via other computer systems accessible to the user, such as an app installed on the user's mobile device.

[0184] Control algorithm updates may be mandatory updates required by the device manufacturer or healthcare professional for a specific group of patients, such as updates to variable parameters related to drug delivery timing or dosage. Alternatively, control algorithm updates may be optional updates that may or may not be applicable based on the configuration, model, and use of a particular drug delivery device 2002. Whether mandatory or optional, updates may be updates to one or more variable parameters of algorithm 2052, such as adding one or more new variable parameters, removing one or more existing variable parameters, or changing the coefficients of one or more variable parameters; they may be updates to algorithm 2052 as a whole or to a part of algorithm 2052. Mandatory and optional control algorithm updates may include algorithm updates customized for specific patients by the appropriate healthcare professional. In addition, or alternatively, available control algorithm updates may be determined based on the compilation of different data sets by system 3002. By processing the data sets, it may be possible to determine updated control algorithms that provide more accurate sensing or administration control, which may result in improved safety, patient compliance, and / or improved clinical outcomes or patient responses.

[0185] Device 2002 and at least one additional drug delivery device associated with the same patient may each be configured to transmit data to system 3002. In such cases, system 3002 may be configured to aggregate and edit data from multiple devices, e.g., data sensed by each device and / or data entered into each device by the user, to provide insights into the patient's drug delivery timing and drug dosage over time. The aggregated data can be correlated with clinical outcomes or self-reported states experienced by the patient after drug delivery over time, enabling healthcare professionals to modify or correct the control algorithm 2052 of device 2002 (and / or any control algorithm of any other devices associated with the patient) based on time-based responses and trends observed for the patient. Embodiments of multiple interconnected computing devices related to drug administration systems are further described in U.S. Patent Application Publication No. 2014 / 0243635, “Device For Enabling Patient Self Testing And Treatment Self-Administration And System Using The Device For Managing The Patient's Health Care,” published on 28 August 2014, and U.S. Patent Application No. 2016 / 0045674, “Supplemental Device for Attachment to an Injection Device,” published on 18 February 2016, which are incorporated herein by reference in their entirety.

[0186] In at least some implementations, system 3002 may be configured to aggregate data received from device 2002 and provide a display of drug dosage and clinical outcomes over time as a graphic plot on the device's user interface 2080 and / or the system's user interface 3080, etc. The response plot may display specific control variables of the tracked algorithm 2052, such as sensing data related to the patient's blood glucose levels. The sensing data may be displayed together with drug administration data and any lifestyle or health events reported by the patient, which may include meals, sleep, activity levels, etc. A suitable healthcare professional can evaluate the response plot and determine whether any adjustments should be made to the control algorithm 2052, and if adjustments should be made, a request for an algorithm update to the device 2002 can be pushed to system 3002 by a healthcare professional, for example, by providing input to system 3002 via user interface 3080.

[0187] In at least some implementations, device 2002, for example its processor 2060, may be configured to perform analysis of the collected information before, or instead of, system 3002, for example its processor 3060, performs the analysis described above. Having system 3002 and device 2002 jointly perform the analysis can be particularly beneficial for various reasons. For example, if device 2002 is configured to continuously collect information from at least one of its sensors 2030, 2040, continuous data collection can result in a relatively large amount of data that can be more easily processed by multiple processors 2060, 3060. In another example, device 2002, which locally processes data indicating sensed information, can receive data indicating sensed information from system 3002, then, based on an analysis of the received data, identify the changes and bring about the necessary changes in algorithm 2052 before those changes can be brought about. In yet another example, system 3002 may receive data from numerous different drug delivery devices in addition to data from drug delivery device 2002, resulting in the need to queue the analysis of data from various devices and process one device at a time. Therefore, device 2002, which processes at least some of the sensed information locally, can analyze the sensed information more quickly than if the data had to wait in a queue for analysis in system 3002, thereby reducing the time lag in adjusting algorithm 2052. In yet another example, distributed processing can reduce execution time and memory consumption and / or achieve better load balancing of data exchanged between drug delivery device 2002 and system 3002. As a result, drug delivery device 2002 can receive updates to control algorithm 2052 more quickly and with less latency compared to drug delivery devices or systems that do not support distributed processing.Similarly, in at least some embodiments, where system 3002 is entirely responsible for data analysis, or where device 2002 and system 3002 share responsibility for data analysis, distributed processing may be shared between system 3002 and at least one other computer system, such as one or more computing devices located at the medical facility 706 in Figure 7, the home base 708 in Figure 7, and the mobile location 710 in Figure 7.

[0188] Data that device 2002 is configured to process locally for the purpose of determining whether changes to algorithm 2052 may be altered. For example, device 2002 may be configured to analyze data collected by one of its sensors 2030, 2040 and to send data collected by the other of sensor 2030, 2040 to system 3002 for analysis. In another example, device 2002 may be configured to analyze data collected during a first period, such as during a typical sleep period, and to send data collected during a second different period, such as during a typical wake period, to system 3002 for analysis, where more sensing data may be collected. In yet another example, device 2002 may be configured to offload data processing as needed, such as when device 2002 is performing continuous monitoring or similar non-stop sensing operations. The patient may request an overview and / or display of drug delivery data regarding the drug delivery device 2002, for example, by providing input via interface 2080. However, the device 2002 attempts to continuously monitor the perceived information and simultaneously executes complex drug delivery regimens that require the control algorithm 2052 to be executed frequently over short periods. Therefore, the drug delivery device 2002 may be configured to determine ownership of certain high-priority execution tasks while delegating low-priority execution tasks to system 3002 or distributing them in other ways. In this way, higher-priority execution tasks can proceed without placing an excessive load on the processor 2060 of the drug delivery device 2002.

[0189] Figure 13 is a flowchart illustrating an exemplary embodiment of Method 1000 for administering a drug using an algorithm. Method 1000 will be described in relation to the drug administration device 2002 and system 3002 shown in Figure 12 for ease of explanation, but other devices and systems may be implemented similarly as described above.

[0190] In operation 1005, the drug delivery device 2002 executes algorithm 2052 to control the delivery of drug doses from the device 2002 to the patient, for example, by causing the dispensing mechanism 2020 to release the drug from the drug holder 2010 to the patient. In operation 1010, the drug delivery device 2002 wirelessly receives data from a system 3002 located remotely from the device 2002, which includes instructions to update algorithm 2052. As described above, the transmission of instructions by the system may be triggered by an analysis of data received from the device 2002, indicating information collected by one or more of the device's sensors 2030, 2040, and / or information otherwise received from the device 2002, such as information input to the device 2002 via the user interface 2080. As also mentioned above, the transmission of commands by the system may be triggered by input of commands or requests from a medical professional to a computer system communicating with system 3002, such as via a drug administration app configured on a mobile device at mobile location 710 in Figure 7, or via a computing device at medical facility 706 in Figure 7. Device 2002 may execute algorithm 2052 multiple times to deliver multiple doses before device 2002 receives a command and modifies algorithm 2052 in operation 1010.

[0191] In operation 1015, the drug delivery device 2002 modifies at least one variable parameter of algorithm 2052 stored in memory 2050 based on data received from a remotely located communication interface in operation 1010. In operation 1020, the drug delivery device 2002 executes the modified control algorithm 2052 to control the delivery of drug doses from the drug delivery device 2002. The device 2002 may execute the modified algorithm 2052 multiple times to deliver multiple doses before the device 2002 receives another instruction in operation 1010 and modifies algorithm 2052 again.

[0192] In at least some implementations, information indicating at least some of the data transmitted in a secure and anonymized manner from the device, such as one of the drug delivery devices in Figures 1 to 5B, one of the drug housings 30 and 630 in Figures 5B and 6, or the packaging 35 in Figure 5B, to a remote computer system such as the central computer system 700 in Figure 7, may be provided via the device's user interface by visual and / or audio information. As mentioned above, this data may include data sensed by the device's sensors. Therefore, patients using the device may continue to be provided with information collected by the sensors.

[0193] In at least some implementations, information indicating at least a portion of the data received from a remote computer system, such as the central computer system 700 in Figure 7, may be provided via the device's user interface by visual and / or audio information, in any of the drug delivery devices in Figures 1 to 5B, any of the drug housings 30 and 630 in Figures 5B and 6, or the packaging 35 in Figure 5B. Thus, a patient using the device may continue to be provided with information, for example, about adjustments made to the algorithm for administering drug doses to the patient, which are executable on the device by its processor, in response to the data received from the remote computer system.

[0194] In at least some implementations, information about a patient's drug delivery device may be provided to a user, e.g., the patient or a healthcare professional associated with the patient, via a user interface. In exemplary embodiments, the information may include feedback and / or notifications (also referred to as “warnings”) regarding the patient’s drug delivery, treatment compliance, current health status, and / or the configuration of the patient’s drug delivery device. The feedback and notifications are configured to facilitate appropriate treatment of the patient by promptly notifying and correcting any discrepancies in drug delivery as needed, such as when drug delivery was not made on schedule, and / or to provide reassurance and positive reinforcement to the user by indicating that drug delivery was made on schedule. Healthcare professionals may receive data on multiple patients and thereby monitor drug dosage and drug delivery data related to patients using the same or different drug delivery devices or housings.

[0195] In exemplary embodiments, feedback and / or notifications are provided via a drug administration app or program on a mobile computing device located at a mobile location, such as the mobile location 710 in Figure 7, which is configured to interoperate with a central computer system (e.g., system 700 in Figure 7) and / or a drug administration device and / or housing (e.g., drug administration device 500 in Figure 5B and / or housing 630 in Figure 6). The drug administration app is configured to receive commands from the command device instructing it to provide notifications.

[0196] In at least some embodiments, the drug administration app may integrate with a health tracking app or similar activity tracking program implemented on the mobile device by the mobile device manufacturer. To avoid sharing private or personal data stored in the health tracking app on the mobile device, the drug administration app may be configured to remove personal and private data that may be stored in the health tracking app when the drug administration app is operating to transmit data from other locations, such as a dispensing device. Similarly, when data is received on the mobile device, the drug administration app may be configured to remove hierarchical criteria categories or other medical administrative data from the data. In at least some embodiments, the drug administration app may be configured to import health data or activity data from other health tracking applications that may be installed on the mobile device. In at least some embodiments, the drug administration app may include a dashboard that integrates the user's health data and activity data with drug administration data and / or relevant medical information that may be available from other locations, e.g., drug administration device 500, housing 630, and / or system 700. As a result, the user may view and interact with an integrated display of health status data and disease management data.

[0197] Integrating a drug administration app into an application consisting of health tracking data and mobile devices may enable trend analysis of a patient's health status. The drug administration app may be configured to provide lifestyle management advice based on trends and corresponding changes determined by the patient's health status as sensed or determined by the drug administration device, housing, and / or system. In at least some embodiments, the drug administration app may be configured to perform cost analysis related to the patient's treatment and determine projected costs that may occur in the future. The drug administration app may be configured to allow the user to access their personal medical records, make appointments, and access the patient's billing, insurance, and payment information. When used by appropriate healthcare professionals, the drug administration app may enable faster onboarding for new healthcare professionals by providing training on new treatments, medications, or alternative therapies. In these embodiments, the drug administration app may be configured to identify conflicting activities of the patient and side effects of medications, and may be configured to suggest new or alternative treatments for the patient. Various notices and further explanations regarding their provision are provided in U.S. Patent Application Publication No. 2014 / 0081659, entitled “Systems And Methods For Surgical And Interventional Planning, Support, Post-operative Follow-up, And Functional Recovery Tracking,” published on March 20, 2014, which is incorporated herein by reference in its entirety.

[0198] A drug administration app may be configured to provide interactive digital assistance to healthcare professionals regarding drug administration data related to a patient or patient group. For example, a drug administration app may be configured to provide automated conversations and assessments of a patient's mental or emotional state. Such conversations and assessments may be useful in detecting the level of a patient's cognitive ability or cognitive impairment, as well as symptoms of depression, agitation, stress, or anxiety. In at least some embodiments, a drug administration app may be configured to answer basic questions that healthcare professionals may ask regarding medication instructions, drug interactions, and / or side effects. Further descriptions of interactive digital assistance that may be provided to healthcare professionals regarding drug administration are provided in U.S. Patent Application Publication No. 2014 / 0081659, “Systems And Methods For Surgical And Interventional Planning, Support, Post-operative Follow-up, And Functional Recovery Tracking,” published on March 20, 2014, and U.S. Patent No. 5,363,842, “Intelligent Inhaler Providing Feedback To Both Patient And Medical Professional,” issued on November 15, 1994, both of which are incorporated herein by reference in their entirety.

[0199] A drug administration app may be configured to provide interactive digital assistance by creating questions to be presented to the patient regarding their health status and lifestyle management. The drug administration app may be configured to customize questions created regarding the patient's overall health and / or current treatment. In at least some embodiments, the drug administration app may be configured to summarize the patient's physiological data, dosage data, dosage delivery schedule, and / or dosage compliance data, so that the user can extract insights and apply or collect other supporting data or metadata. For example, an algorithm may be applied to the data based on processing of an aggregated data source to determine maintenance or escalation procedures that may be required when the patient's physiological data exceeds a certain threshold. Further explanation of using the data to extract or find supporting data is provided in U.S. Patent Application Publication 2005 / 0027791, “Method Of Controlling Delivery Of A Service And Devices For Performing This Method,” published on 3 February 2005, which is incorporated herein by reference in its entirety.

[0200] Digital assistance features configured within a drug administration app can provide patients with better self-administration, self-management of disease prevention, and health solutions. For example, the digital assistance features may be configured to recommend new treatment providers located within the patient's geographical area and capable of specializing in the patient's specific disease or health condition. In at least some embodiments, the digital assistance features may be configured to identify social networks or online communities that can provide support to the patient based on the patient's needs and health condition. Other self-administration and self-management features of the interactive digital assistance features configured within the drug administration app 714 may include suggestions for alternative injection sites or drug delivery mechanisms based on self-reported health status data and sensory information collected by sensors in the drug administration device and / or housing. In at least some embodiments, the digital assistance features may be configured to generate recommendations to avoid relapses of drug addiction based on behavioral data and sensory information collected from sensors in the drug administration device and / or housing. Further explanations regarding the provision of the proposal are found in U.S. Patent Publication No. 2014 / 0081659, entitled “Systems And Methods For Surgical And Interventional Planning, Support, Post-operative Follow-up, And Functional Recovery Tracking,” published on March 20, 2014, and U.S. Patent Publication No. 2017 / 0286610, entitled “Systems and Methods for Predicting Metabolic and Bariatric Surgery Outcomes,” published on October 5, 2017, both of which are incorporated herein by reference in their entirety.

[0201] In at least some embodiments, feedback / notifications may be provided to the user based on certain aspects of data related to the patient's drug delivery device that have exceeded a threshold, or based on rules. In at least some embodiments, feedback / notifications may be provided hierarchically based on the importance of a particular individual or a combination of data parameters. For example, if data related to the operation of the patient's drug delivery device, such as a decrease in needle insertion depth, is combined with a specific physiological condition sensed via at least one sensor of the drug delivery device, such as an elevated blood glucose level, the user interface of the drug delivery device may be configured to notify the user of the drug delivery device to take corrective action for a malfunctioning device that may be causing an elevated blood glucose level. The feedback / notifications may specify corrective action, such as contacting the patient's healthcare professional or requesting an updated control algorithm for the drug delivery device.

[0202] Notifications and feedback may be configured to be transmitted between devices associated with the computing system. In one embodiment, the drug administration app may exchange data with the drug administration device and / or housing so that the user can configure notification settings for the drug administration device and / or housing. In at least some embodiments, the drug administration app may be configured to allow the user to configure audio, visual, or haptic notifications.

[0203] In some embodiments, for example, feedback / notifications provided to the user via a user interface or app may include information regarding the proper disposal of the drug delivery device when drug delivery from the drug delivery device is complete and the drug delivery device is no longer needed, or when drug delivery has not taken place and the drug delivery device is not empty. Disposal of the drug delivery device may be final disposal of the drug delivery device (e.g., as medical waste) or recycling of the drug delivery device. Therefore, information regarding the proper disposal of the drug delivery device may be final disposal information or recycling information. Some drugs, such as esketamine, ketamine, and other controlled substances, may be disposed of according to government requirements, e.g., requirements of the U.S. Drug Enforcement Administration, non-U.S. federal requirements, state requirements, or local requirements, for example, to ensure that the drugs do not fall into the hands of unauthorized third parties. Even if the drug delivery device is used properly and delivers such drugs from the drug delivery device, disposal of the drug delivery device may still be necessary. This is because, for example, after proper use of the drug delivery device, there may be residual drug in the drug delivery device that could potentially fall into the hands of unauthorized third parties or users.

[0204] One example of proper disposal of a drug administration device is for the user to contact supplier "X" to schedule a pickup of the device, and contact information may be provided to supplier "X". Another example of proper disposal of a drug administration device is for the user to ship the used drug administration device to company "Y", and the mailing address and / or postage information of company "Y" may be provided.

[0205] In exemplary embodiments, information regarding the proper disposal of the drug delivery device is provided after all prescribed doses have been delivered from the drug delivery device, although this information may be provided at other times. In some embodiments, the drug delivery device, for example, its processor, is configured to locally determine that all prescribed doses have been delivered from the drug delivery device. For example, the drug delivery device may include a counter that counts the number of doses delivered from the drug delivery device, and the processor may be configured to determine when the counter reaches a predetermined number corresponding to the number of prescribed doses. In another example, the drug delivery device may include a counter that counts down one from a maximum number of prescribed doses each time a dose is delivered from the drug delivery device, and the processor may be configured to determine when the counter reaches zero. In other embodiments, the drug delivery device is configured to transmit drug delivery information to a remote computer system, such as the central computer system 700 in Figure 7, and the remote computer system is configured to determine that all prescribed doses have been delivered from the drug delivery device in any of the various ways, such as by the examples described above. In response to determining that all prescribed doses have been delivered from the drug delivery device, the remote computer system may be configured to send a request to the drug delivery device to provide information regarding the proper disposal of the drug delivery device.

[0206] Information regarding the proper disposal of drug delivery devices may be provided based on the user's geographical location. Since medical waste disposal requirements may vary by jurisdiction (e.g., county, city, state, federal), information regarding the proper disposal of drug delivery devices based on the user's geographical location can help ensure compliance with local regulations. The user's geographical location may be known, for example, by a drug delivery device including a geographic sensor, or, in another example, by a user's mobile device including location-sensing capabilities, as understood by those skilled in the art, and the mobile device is configured to communicate with the drug delivery device and / or a remote computer system.

[0207] A drug delivery device and / or remote computer system that may include digital Instructions for Use (IFU) may be configured to access a disposal database that internally includes information correlating disposal instructions for the drug delivery device with geographical location, for example, a lookup table that correlates each of several geographical locations with disposal instructions for the drug delivery device specific to that geographical location. The disposal database may be maintained in the remote computer system and / or in another computer system, such as a computer system maintained by the manufacturer of the drug delivery device and / or the drugs delivered by the drug delivery device.

[0208] In some embodiments, the waste database also includes carbon footprint information regarding the disposal of drug delivery devices. This carbon footprint information may be correlated with each geographical location, for example, in a lookup table. The carbon footprint information may include disposal instructions for drug delivery devices, which can help notify users of environmental factors associated with the drug delivery devices. Alternatively, the carbon footprint information may be calculated after the geographical location of a particular drug delivery device is known, based on the disposal requirements of that geographical location, for example, based on facilities that dispose of or recycle drug delivery devices, and / or based on the geographical location itself, for example, after a predetermined number of drug delivery devices have been disposed of from geographical locations where the manufacturer of the drug delivery device and / or drug would engage in activities to reduce the carbon footprint, such as planting trees or making charitable donations.

[0209] In some embodiments, instead of the drug administration device providing information regarding the proper disposal of the drug administration device, the disposal container may be a smart container that houses multiple used drug administration devices and is configured to provide information regarding the proper disposal of the drug administration devices housed inside, for example, on its user interface. The container may be configured to transmit data and display information similar to the information described above regarding the drug administration device. The container is configured to provide information regarding the proper disposal of the drug administration devices housed inside based on the geographical location of the container, and the same container can be used in any geographical location, but it provides information specific to that geographical location. Therefore, the container can be manufactured more efficiently because it does not need to be customized for a particular geographical location. In an exemplary embodiment, the container is configured to provide information regarding the proper disposal of drug administration devices housed inside after a predetermined threshold number of drug administration devices have been disposed of inside. The predetermined threshold number may vary based on the size of the container and the size of the drug administration devices disposed inside, but generally corresponds to the number of drug administration devices that fill or nearly fill the container. In some embodiments, a site (e.g., a hospital, clinic, or other healthcare facility) may be certified as a supplier of a particular type of drug delivery device and may receive smart containers after such certification. A site may need to be certified for a particular type of drug, such as esketamine, ketamine, or other regulated substances for which site certification is required as a REMS requirement, and therefore may need to be certified for drug delivery devices that deliver those types of drugs.

[0210] In some embodiments, instead of the drug administration device or smart container providing information regarding the proper disposal of the drug administration device, the shipping carton may be a smart carton configured to provide information regarding the proper disposal of the drug administration device shipped in the carton, for example, on its user interface. The carton may be configured to transmit data and display information similar to the information described above regarding the drug administration device. The carton is configured to provide information regarding the proper disposal of the drug administration device shipped in it, based on the carton's geographical location, and the same carton can be used in any geographical location, but it provides information specific to that geographical location. Therefore, the carton can be manufactured more efficiently because it does not need to be customized for a particular geographical location.

[0211] In some embodiments, instead of the drug delivery device, smart container, or smart carton providing information regarding the proper disposal of a drug delivery device, the drug delivery device, smart container, or smart carton may have a label attached to the drug delivery device, smart container, or smart carton (or, in other ways, part of the drug delivery device, smart container, or smart carton) that is configured to be electronically read and provide information regarding the proper disposal of a drug delivery device for the drug delivery device, the drug delivery device in the smart container, or the drug delivery device in the smart carton or smart container. The label may have a variety of configurations. For example, the label may include an integrated circuit configured to transmit drug holder data from the drug holder. In another example, the label may be a radio frequency identification (RFID) tag. In yet another example, the label may be in the form of a barcode. The label may be a single label or multiple labels. When multiple labels are used, each may be of a different type (e.g., one including a barcode and the other including an RFID tag), which can help provide redundancy and / or allow disposal information to be obtained even when a particular type of data communication is not currently available, for example, when an RFID scanner is absent or malfunctioning. Various types of readers, such as barcode scanners, RFID scanners, and mobile phones with barcode reading capabilities, can be used to electronically read labels in a manner appropriate to the type of label. The reader may be configured to display the read information regarding the appropriate disposal of the drug delivery device on the reader, or the reader may be configured to transmit the read information to a computer system that displays the read information regarding the appropriate disposal of the drug delivery device.

[0212] Figure 14 shows one embodiment of a user interface 1100 that displays data, feedback, and notifications. In the exemplary embodiment shown in Figure 14, the user interface 1100 relates to a patient receiving insulin via a drug delivery device to lower the patient's blood glucose, but other types of drugs and other types of drug delivery devices may be used as described herein.

[0213] The user interface 1100 includes patient identification information 1105, date and time identification information 1110, configuration icons 1115, a current status section 1120, a reminder section 1125, an overview section 1130, an indication section 1135, and a received data section 1140. In at least some embodiments, the layout and arrangement of the identification information and sections within the user interface 1100 can be rearranged interactively by the user as understood by those skilled in the art. In this way, the user can create a customizable dashboard-like data display organized to suit the user's preferences.

[0214] Patient identification information 1105 identifies patient "JaneSmith". User interface 1100 is configured to display the user's name after the user has properly authenticated themselves to each device or system they are interacting with, in order to help provide a secure system. Users can authenticate their identity in various ways, such as by using single-factor, two-factor, multi-factor, and / or strong authentication methods. Users can authenticate their identity using one or more authentication factors, such as a password, passphrase, personal identification number (PIN), challenge-response, security question, ID card, security token, software or hardware token, fingerprint, retinal pattern, signature, user's face or voice, or biometric authentication.

[0215] The date and time identifier 1110 displays the current date and time. The current date and time may provide the user with temporal context to other schedule-based data, such as reminders, notifications, or reminders for the time to administer the next dose of medication.

[0216] The configuration icon 1115 is an interactive graphic affordance or icon that, when selected or otherwise activated, causes the user interface 1100 to display additional functions related to the settings and configuration of the user interface. The selection / activation of the configuration identifier 1115 is configured to provide the user with tools to configure not only the display of the user interface 1100, such as the arrangement or order of identifiers and parts within the user interface, but also the configuration of the device displaying the user interface 1100. In at least some embodiments, the configuration identifier 1115 is configured to display information indicating help information regarding the correct use of the patient drug delivery device or housing for which the user interface 1100 provides information. For example, the configuration identifier 1115 may include additional graphic affordances or indicators, such as icons, symbols, or numbers indicating to the user that an update is available to help the user correctly use the patient drug delivery device or housing for which the user interface 1100 provides information. The indicated update may relate to an updated version of software available for download and installation on the patient drug delivery device or housing for which the user interface 1100 provides information. The range of acceptable configuration changes, provided by the configuration identification information 1115, can be adjusted as a preference within the system.

[0217] The current state section 1120 of the user interface 1100 includes sensor data, such as sensors 92, 94, and 98 of the drug administration device 500 in Figure 5B, sensors of the mobile device on which the user interface 1100 is displayed, or other sensors, and other sensor-sensed information. In this example, the current state section 1120 displays the patient's heart rate (78 beats per minute), body temperature (99.1 degrees Fahrenheit), respiratory rate (18 breaths per minute), and activity level (6,235 steps against a target of 8,000 steps per day).

[0218] The reminder section 1125 provides reminders for one or more next drug doses and / or other aspects of the patient's treatment plan. In this example, the reminder section 1125 provides a reminder that “Next dose: Today @ 9:30 pm”. Since the current time is “6:24 pm”, the user is reminded that the next dose will be administered in approximately three hours. Other examples that may be provided in the reminder section 1125 include reminders indicating the current required to manually administer a drug dose to the patient, as well as reminders to change the battery in the patient's drug administration device, charge the battery in the patient's drug administration device, or order a drug refill for the drug administration device. In at least some embodiments, audio, visual, or tactile notifications may be provided in conjunction with the reminders displayed in the reminder section 1125 to prompt the user to notice newly provided reminders and / or to help prompt the user to perform the action at the appropriate time.

[0219] Summary section 1130 provides an overview view of the pre-scheduled doses of the drug to the patient. As in this illustrated embodiment, summary section 1120 can also provide an indication of the intended therapeutic effect of the drug to the patient, indicated by “1. Pre-scheduled dose to reduce blood glucose”. As shown in Figure 14, summary section 1130 includes a list of three pre-scheduled doses, items a-c. As indicated by item a, summary section 1130 indicates that the pre-scheduled dose was administered “Today @ 9:30 am” and was successfully delivered (“Completed”) at “1 / 30 / 19 @ 9:33 am”. In this way, summary section 1130 intuitively shows the user the timing of previously delivered doses compared to a predetermined delivery schedule for these doses. As indicated by item a, sub-item i, summary section 1130 also provides the user with an indication of the estimated remaining period of effectiveness of the drug to the patient, “Expiration Date: 1 / 30 / 19 @ 11:00 pm”. Item c also shows information about the delivered dose ("Yesterday @ 9:30am - Completed 1 / 29 / 19 @ 9:26am"). Pre-scheduled doses, shown in summary section 1130, may also indicate the time when the patient failed to deliver a previously scheduled dose, as shown in item b "Yesterday @ 9:30pm - Failed". Summary section 1130 may be configured to scroll to display additional summary information, such as doses scheduled before "Yesterday @ 9:30am". Other parts of the user interface 1100 may also be configured to scroll to display additional information.

[0220] In at least some embodiments, the summary section 1130 may include other interactive graphic affordances, such as tabs or icons, which, when selected or activated, are configured to display dose delivery data over time in a graphical format, such as a graph or chart. In at least some embodiments, the dose delivery data included in the summary section 1130 may be provided in relation to other clinical outcomes, perceived data events, and / or self-reported health status data provided by the patient. In at least some embodiments, the dose delivery data included in the summary section 1130 may be provided in relation to data received from system 700 or from other data sources that may be accessible via system 700 and network 702.

[0221] The indication section 1135 provides a correlation between the timing of previously delivered drug doses from the drug delivery device or housing to the patient and the timing of medical events experienced by the patient. In this illustrated embodiment, the indication section 1135 includes a list of the three most recent pre-scheduled doses and one or more sensed characteristics of the patient, which in this illustrated embodiment includes, for example, the patient's blood glucose level measured at each time of the pre-scheduled dose, measured by one of the sensors of the drug delivery device. Once insulin has been properly administered according to the pre-scheduled times, as shown in doses 1 and 3 ("completed" in summary section 1130), the patient's blood glucose level has remained within the normal range, as shown in the measurement of 85 mg / dL corresponding to dose 1 completed at "today @ 9:30 am" and the measurement of 78 mg / dL corresponding to dose 3 completed at "yesterday @ 9:30 am". However, when the patient failed to administer dose 2 “yesterday at 9:30 pm” (“failure” in summary section 1130), the patient’s blood glucose level was 225 mg / dL. The indication section 1135 may be configured to correlate the timing of previously delivered drug doses with various medical events the patient may experience at the time of the previously delivered dose. In at least some embodiments, medical event data may originate from the patient’s medical records, and the indication section 1135 may provide a correlation between the timing of previously delivered doses and medical record data (including, for example, clinical laboratory results).

[0222] The received data portion 1140 displays data that may be received from a remote location, such as the system 700 in Figure 7, or from a remote data source available through the system 700 via the network 702. As shown in Figure 14, the received data portion 1140 in this illustrated embodiment includes updated medical record information, "1. Updated Medical Records - Currently Available." The updated medical record information may be received from a medical record database configured within the system 700 in Figure 7 or from a database associated with a computer system located in the medical facility 706 in Figure 7. In an exemplary embodiment, the user may view the updated medical records by clicking or otherwise selecting a uniform resource locator (URL) provided by the user interface 1100. In this illustrated example, clicking the word "here," as indicated in "b. Click here to view," is configured to cause the user interface 1100 to display the updated medical records. The URL may be used, not limited to the user interface 1100, to provide additional data for display to the user.

[0223] As also shown in the received data portion 1140, the user may receive data that provides help information regarding the use of the drug delivery device and / or housing. For example, in this illustrated embodiment, the received data portion 1140 may present help information as update information, indicated as "2. New device software - downloadable". Help information may include new device configuration settings and product documentation such as user manuals related to the patient's drug delivery device or housing. The user may have the help information sent to and installed on the drug delivery device or housing by clicking the configuration identification information 1115 or by selecting it in another way.

[0224] The received data portion 1140 may include data that can be received remotely based on information sensed or determined by the patient's drug delivery device 500 or housing. For example, in this illustrated embodiment, the received data portion 1140 includes remote data received as “3. Compliance message from Dr. Jones.” Based on the patient's drug delivery device and / or housing sensors sensing a 225 mg / dL increase in blood glucose level resulting from a drug dose that was pre-scheduled and not administered “yesterday @ 9:30 pm,” the drug delivery device and / or housing may transmit the sensed blood glucose level (in addition to drug delivery and compliance data) for display in the received data portion 1140 of the user interface 1100. In this illustrated example, as a result of receiving the sensed blood glucose level (in addition to summary data indicating the failed dose that was scheduled for “yesterday @ 9:30 pm”), the system may notify the patient's healthcare professional to send a compliance message to the patient, for example via a notification in the reminder portion 1125, reminding the patient of appropriate guidance and drug delivery schedules necessary to lower the patient's elevated blood glucose level. In this way, data sensed by the patient's drug delivery device or housing, or determined by other means, may be transmitted to a remote computer system. The remote computer system may be configured to receive the sensed information, generate data related to the sensed information, send it back to the drug delivery device or housing, and provide it to the user via the user interface 1100.

[0225] Further explanations regarding the data and data display provided within user interfaces, such as the user interface 80 of the drug delivery device 500 or housing 630, or the user interface 2080 of the drug delivery device 2002, are provided in U.S. Patent Application Publication No. 2002 / 0091454, entitled "Remotely Programmable Infusion System," published on 11 July 2002, and U.S. Patent Application Publication No. 2008 / 0139907, entitled "Intelligent Personal Health Management Appliance For The Measurement And Monitoring Of Health Factors And Controlled Delivery Of Drugs," published on 12 June 2008, both of which are incorporated herein by reference in their entirety.

[0226] All of the apparatus and systems disclosed herein may be designed to be discarded after a single use or to be designed for multiple uses. However, in either case, the apparatus may be readjusted for reuse after at least one use. Readjustment may include any combination of disassembly of the apparatus, subsequent cleaning or replacement of specific parts, and subsequent reassembly. Specifically, the apparatus may be disassembled, and any number of specific parts or components of the apparatus may be selectively replaced or removed in any combination. Once the specific parts have been cleaned and / or replaced, the apparatus may be reassembled for subsequent use in a readjustment facility or by a surgical team immediately before surgical intervention. Those skilled in the art will understand that various techniques for disassembly, cleaning / replacement, and reassembly are available for readjusting the apparatus. The use of such techniques and the resulting readjusted apparatus are all within the scope of this application.

[0227] The devices disclosed herein may preferably be sterilized before use. This can be done by various methods known to those skilled in the art, such as beta- or gamma-ray emission, ethylene oxide, steam, and liquid baths (e.g., cryogenic immersion). Exemplary embodiments for sterilizing a device including internal circuitry are described in more detail in U.S. Patent Publication 2009 / 0202387, “System and Method of Sterilizing An Implantable Medical Device,” published on August 13, 2009. If the device is to be implanted, it is preferably to be completely sealed. This can be done by various methods known to those skilled in the art.

[0228] This disclosure is described only within the context of the entire disclosure provided herein, through the examples. It will be understood that modifications can be made to the intent and scope of the claims without departing from the overall scope of this disclosure.

Claims

1. 1. A drug delivery device configured to hold a drug therein, comprising: a sensor configured to sense information regarding at least one of the medication administration device and the medication; a memory configured to store data therein, the stored data including a key and an algorithm including at least one variable parameter, the key being established with a remotely located server and being unique to the drug administration device and the remotely located server; a communication interface configured to wirelessly transmit data indicative of the sensed information to a remotely located communication interface and configured to wirelessly receive data from the remotely located communication interface; a processor configured to use the key to anonymize the data indicative of the sensed information prior to the transmission of the data indicative of the sensed information, to use the key in decrypting the data received from the remotely located communication interface, to use an algorithm in controlling delivery of a drug from the drug administration device to a patient, and to modify the at least one variable parameter of the algorithm stored in the memory based on data received from the remotely located communication interface.

2. The device of claim 1 , wherein the drug administration device is one of a syringe, an injector, an inhaler, a nasal spray device, and an infusion pump.

3. The device of claim 1 , wherein the processor is configured to use the key in anonymizing all data transmitted to the communication interface that is remote from the communication interface.

4. The device of claim 1 , wherein the processor is configured to repeatedly use the key to anonymize multiple data sets indicative of information sensed by the sensor.

5. The device of claim 1 , wherein the processor is configured to use the key in decrypting all data received from the remotely located communications interface.

6. 10. The device of claim 1, wherein the communication interface is configured to wirelessly receive data from a remotely located communication interface, the data including information regarding proper disposal of the drug administration device after the drug has been delivered from the drug administration device.

7. The device of claim 1 , wherein the processor is configured to cause a user of the medication administration device to provide notification of the information regarding appropriate disposal information.

8. The device of claim 1, further comprising a label containing information regarding proper disposal of the drug administration device after the drug has been delivered from the drug administration device.

9. The device of claim 1 , wherein the processor is configured to control delivery of the medication from the medication administration device based at least in part on the sensed information.

10. 10. The device of claim 1, wherein the drug comprises at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.

11. 1. A drug delivery system comprising: A server, a communications interface configured to wirelessly receive data and wirelessly transmit data; a memory configured to store a key therein; A server including a processor; 1. A drug administration device comprising: a memory configured to store therein the key and an algorithm including at least one variable parameter, the key being unique to the drug administration device and the server; a communication interface configured to wirelessly transmit data to the communication interface of the server and wirelessly receive data from the communication interface of the server; a medication administration device including a processor; the processor of the server is configured to use the key to anonymize all data transmitted to the communication interface of the medication administration device prior to said transmission; The processor of the drug administration device is configured to use the key to anonymize all data before it is transmitted to the communication interface of the server, configured to use the key when decrypting the data received from the communication interface of the server, configured to use an algorithm when controlling delivery of the drug from the drug administration device to a patient, and configured to modify the at least one variable parameter of the algorithm stored in the memory based on the data received from the communication interface of the server.

12. 12. The system of claim 11, wherein the drug administration device is one of a syringe, a syringe, an inhaler, a nasal spray device, and an infusion pump.

13. the processor of the server is configured to use the key to decrypt all data received from the communication interface of the medication administration device; The system of claim 11, wherein the processor of the medication administration device is configured to use the key to decrypt all data received from the communication interface of the server.

14. The system of claim 11, wherein the processor of the server is configured to automatically upload the data received from the communication interface of the drug administration device to at least one of a patient's electronic health record (EHR) associated with the drug administration device and a patient monitoring form for drug risk assessment and mitigation strategy (REMS).

15. The system of claim 11, wherein the drug administration device also includes a sensor configured to sense information regarding at least one of the drug administration device and the drug, and the data transmitted to the communication interface of the server includes data indicative of the sensed information.

16. 16. The system of claim 15, wherein the processor of the drug administration device is configured to control delivery of the drug from the drug administration device to a patient based at least in part on the sensed information.

17. The system of claim 11 , wherein the data transmitted to the server's communications interface comprises data in response to a data request received from the server.

18. 12. The system of claim 11, wherein the drug comprises at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.

19. A method of drug administration comprising: establishing a unique key for wireless communication between a drug administration device and a server located remotely from the drug administration device, the key being stored in a memory of the drug administration device and in a memory of the server; sensing information about at least one of the medication administration device and the medication with a sensor of the medication administration device; anonymizing, at a processor of the medication administration device, the data indicative of the sensed information prior to the transmission of the data indicative of the sensed information using the key stored in the memory of the medication administration device; using, at the processor of the medication administration device, the key stored in the memory of the medication administration device when decrypting data received from the server; using an algorithm in controlling delivery of the drug from the drug administration device to the patient; modifying the at least one variable parameter of the algorithm stored in the memory based on data received from the server; A method comprising:

20. 20. The method of claim 19, wherein the drug administration device is one of a syringe, an injector, an inhaler, a nasal spray device, and an infusion pump.

21. 20. The method of claim 19, further comprising controlling, at the processor of the drug administration device, delivery of the drug from the drug administration device based at least in part on the sensed information.

22. 20. The method of claim 19, wherein the data includes information regarding proper disposal of the drug administration device after the drug has been delivered from the drug administration device.

23. 23. The method of claim 22, further comprising using the processor to provide a notification of the information regarding appropriate disposal information to a user of the medication administration device.

24. 20. The method of claim 19, wherein the drug comprises at least one of infliximab, golimumab, ustekinumab, daratumumab, guselkumab, epoetin alfa, risperidone, esketamine, ketamine, and paliperidone palmitate.