Systems and methods for monitoring a medicament dosing schedule
A mobile application addresses the challenge of missed doses by providing timely reminders and guided dosing processes, enhancing medication adherence for conditions like atopic dermatitis and asthma by adjusting schedules based on user interactions and medication-specific guidelines.
Patent Information
- Application Number
- SA1120263415
- Authority / Receiving Office
- SA · SA
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2026-04-23
- Publication Date
- 2026-10-05
AI Technical Summary
Existing medication management systems fail to effectively notify users of missed or delayed doses and provide proactive guidance for adhering to dosing schedules, particularly for conditions treated with a single medication like dupilumab, which can be complex due to varying dosages and frequencies.
A mobile application that provides timely reminders, notifications, and guided dosing processes, allowing users to manage their medication regimen by recording doses, offering silent, summary, and pop-up notifications, and adjusting schedules based on user interactions and medication-specific guidelines.
Enhances medication adherence by promptly alerting users to missed doses, offering customizable guidance, and adjusting dosing schedules, thereby improving treatment compliance for conditions such as atopic dermatitis, asthma, and other immune-related diseases.
Smart Images

Figure 0BFC0ACA-CACC-453E-8F66-A6C7198F3420 
Figure 360B04AD-F1D9-4283-BB5B-4DCA2BFB182F 
Figure 3825A02B-F6AC-474C-A95F-21189B7FB166
Abstract
Description
This disclosure pertains to an application that can be run on the user's device and assists them by notifying them of missed or delayed doses, providing proactive guidance on managing late doses, and allowing the user some control over their dosing schedule when a dose is missed. The application also helps the user adhere to their prescribed medication regimen by providing timely reminders and warnings, and clearly explaining the options available after a missed or delayed dose. The app can be used to manage a wide range of diseases treated with a combination of different medications. While some specific examples below illustrate the treatment of atopic dermatitis and / or asthma with a single medication, the app is not limited to this extent. Many immunological and other conditions can also be managed with the app, where one or more of these conditions can be treated with a single medication approved for use in one or more of these conditions. A single medication might include, for example, different doses containing the same active pharmaceutical ingredient (API), different sizes or concentrations of the same API, or different formulations containing the same API. In some examples, a single medication might include a monoclonal antibody (mAb) against the interleukin-4 receptor (such as dupilumab). Furthermore, a wide range of immune and other conditions can be managed with the app.A user can be prescribed one or more medications, and the app provides personalized support based on their prescription and health condition. For example, the app can be configured to support a number of inflammatory conditions, including type II. In the context of skin conditions, this might include atopic dermatitis, pruritus nodularis, bullous pemphigoid, urticaria (e.g., chronic spontaneous urticaria or cold inducible urticaria), hand, foot, or itchy rash, all of which can be treated with Dupixent® injections or other injectable medications, as well as certain oral and topical medications.In the context of respiratory diseases, this may include asthma, nasal polyps, sinusitis (for example, chronic sinusitis with or without nasal polyps), allergic bronchopulmonary aspergillosis (ABPA), allergic fungal rhinosinusitis (AFRS) (which can be treated with Dupixent® injections or other injectable drugs as well as some oral medications), and chronic obstructive pulmonary disease (COPD), which can be treated with Dupixent® injections or other injectable drugs. In the context of gastrointestinal diseases, this may include Inflammatory Bowel Disease (IBD), Eosinophilic Esophagitis (EoE), Eosinophilic Gastroenteritis (EGE), or Ulcerative Colitis, which are diseases that can be treated by Dupixent® injections or other injectable drugs in addition to some oral medications. Table 1 Amino acid sequences of the complement-specific region in the antibody to interleukin-4α (such as dupilumab). Sequence ID number: Description Sequence Sequence ID number: 1. The boundary region for completion is 1 of the heavy variable sequence GFTFRDYA. Sequence ID number: 2. The boundary region for completion is 2 of the variable heavy chain ISGSGGNT. Sequence ID number: 3. The boundary region for completion is 3 of the variable heavy chain AKDRLSITIRPRYYGLDV Sequence ID number: 4. The boundary region for completion is 1 of a variable light string QSLLYSIGYNY. Sequence ID number: 5, region 2 of the LGS variable light chain. Sequence ID number: 6, boundary region for completion 3 of a variable light string MQALQTPYT Table 2 Nucleotide sequences of the complement-specific region in the antibody to interleukin-4α (such as dupilumab). Sequence ID number: Description Sequence Sequence ID number: 7 The region of completion is defined as 1 of a heavy variable sequence ggattcacct ttagagacta tgcc Sequence ID number: 8 The region defined for completion is 2 of a heavy variable sequence attagtggtt ccggtggtaa caca Sequence ID number: 9 The region limiting completion is 3 of a heavy variable sequence gcgaaagatc gactctctat aacaattcgc ccacgctatt atggtttgga cgtc Sequence ID number: 10 The boundary region for completion 1 of a variable light string cagagcctcc tgtatagtat tggatacaac tat Sequence ID number: 11 The region defined for completion is 2 of a variable light string ttgggttct Sequence ID number: 12 The region limiting completion is 3 of a variable light chain atgcaagctc tacaaactcc gtacact Table 3 Nucleotide sequences of the variable region of the heavy and light chains For the antibody to interleukin-4 alpha (such as dupilumab). Sequence ID number: Description Sequence Sequence ID number: 13, Region EVQLVESGGGLEQPGGSLRLSCAGS The variable GFTFRDYAMTWVRQAPGKGLEWV For the heavy series SSISGSGGNTYYADSVKGRFTISRDN SKNTLYLQMNSLRAEDTAVYYCAK DRLSITIRPRYYGLDVWGQGTTVTV S Sequence ID number: 14 Light string DIVMTQSPLSLPVTPGEPASISCRSSQ For the series SLLYSIGYNYLDWYLQKSGQSPQLLI Light YLGSNRASGVPDRFSGSGSGTDFTLK ISRVEAEDVGFYYCMQALQTPYTFG QGTKLEIK Table 4 Nucleotide sequences of the variable region of the heavy and light chains For the antibody to interleukin-4 alpha (such as dupilumab). Sequence ID number: Description Sequence Sequence ID number: Region gaggtgcagc tggtggagtc tgggggaggc ttggaacagc 15 variable cggggggggtc cctgagactc tcctgtgcag gctctggatt For series cacctttaga gactatgcca tgacctggggt ccgccaggct الثقيلة ccagggaagg gactggagtg ggtctcatct attagtggtt ccggtggtaa cacatactac gcagactccg tgaagggccg gttcaccatc tccagagaca attccaagaa cacgctgtat ctgcaaatga acagcctgag agccgaggac acggccgtat attactgtgc gaaagatcga ctctctataa caattcgccc acgctattat ggtttggacg tctggggcca agggaccacg gtcaccgtct cc رقم معرف المتوالية: المنطقة gacatcgtga tgacccagtc tccactctcc ctgcccgtca ١٦ المتغيرة cccctggaga gccggcctcc atctcctgca ggtctagtca للسلسلة gagcctcctg tatagtattg gatacaacta tttggattgg الخفيفة tacctgcaga agtcagggca gtctccacag ctccttatct atttgggttc taatcgggcc tccggggtcc ctgacaggtt cagtggcagt ggatcaggca cagattttac actgaaaatc agcagagtgg aggctgagga tgttgggttt tattactgca tgcaagctct acaaactccg tacacttttg gccaggggac caagctggag atcaaa الجدول ٥ Stable amino acid sequences for heavy chain and light chain For the antibody to interleukin-4 alpha (such as dupilumab). Sequence ID number: Sequence description Sequence ID number: 17 Heavy chain EVQLVESGGGLEQPGGSLRLSCAGSG FTFRDYAMTWVRQAPGKGLEWVSSI SGSGGNTYYADSVKGRFTISRDNSKN TLYLQMNSLRAEDTAVYYCAKDRLS ITIRPRYYGLDVWGQGTTVTVSSAST KGPSVFPLAPCSRSTSESTAALGCLVK DYFPEPVTVSWNSGALTSGVHTFPAV LQSSGLYSLSSWTVPSSSLGTKTYTCN VDHKPSNTKVDKRVESKYGPPCPPCP APEFLGGPSVFLFPPKPKDTLMISRTPE VTCVVVDVSQEDPEVQFNWYVDGVE VHNAKTKPREEQFNSTYRVVSVLTVL HQDWLNGKEYKCKVSNKGLPSSIEKT ISKAKGQPREPQVYTLPPSQEEMTKN QVSLTCLVKGFYPSDIAVEWESNGQP ENNYKTTPPVLDSDGSFFLYSRLTVD KSRWQEGNVFSCSVMHEALHNHYTQ KSLSLSLG Sequence ID number: 18 light string DIVMTQSPLSLPVTPGEPASISCRSSQSL LYSIGYNYLDWYLQKSGQSPQLLIYLG SNRASGVPDRFSGSGSGTDFTLKISRVE AEDVGFYYCMQALQTPYTFGQGTKLE IKRTVAAPSVFIFPPSDEQLKSGTASVV CLLNNFYPREAKVQWKVDNALQSGNS QESVTEQDSKDSTYSLSSTLTLSKADY EKHKVYACEVTHQGLSSPVTKSFNRG EC Table 6 The future of human interleukin-4. Sequence ID number: Sequence description Sequence ID number: human MKVLQEPTCVSDYMSISTCEWKMNGP 19 Interleukin-4 receptor TNCSTELRLLYQLVFLLSEAHTCIPENN GGAGCVCHLLMDDVVSADNYTLDLW AGQQLLWKGSFKPSEHVKPRAPGNLT VHTNVSDTLLLTWSNPYPPDNYLYNH LTYAVNIWSENDPADFRIYNVTYLEPS LRIAASTLKSGISYRARVRAWAQCYNT TWSEWSPSTKWHNSYREPFEQH Pharmaceutical formulations: This discovery presents methods involving the administration of an antibody to interleukin-4alpha, such as dupilumab, to a subject, where the antibody is a component of a pharmaceutical formulation. Effective pharmaceutical formulations are prepared using suitable vectors, excipients, and other agents that provide appropriate transport, delivery, tolerability, and other characteristics. Giving: Therapeutic formulations will be given using appropriate carriers, excipients and other agents that are incorporated into formulations to provide improved transport, delivery and tolerability, and the like. Dosage: In some cases, one or more doses (e.g., 1, 2, 3, 4, or 5) are given at the start of a treatment regimen as "loading doses," followed by subsequent doses given less frequently (e.g., "maintenance doses"). For example, an IC4 antagonist may be given to a subject with a loading dose of approximately 200 mg, 400 mg, or 600 mg, followed by one or more maintenance doses of approximately 75 mg to 300 mg. In one formulation, the initial dose and one or more maintenance doses consist of 50 mg to 600 mg of the IC4 antagonist, for example, 100 mg, 150 mg, 200 mg, 250 mg, 300 mg, 400 mg, 500 mg, or 600 mg of the IC4 antagonist. In some incarnations, the primary dose and one or more secondary doses contain the same amount of the antagonist to the interleukin-4 receptor.In other formulations, the initial dose consists of a first amount of the interleukin-4 receptor antagonist, and one or more subsequent doses consist of a second amount of the same antagonist. For example, the initial amount of the antagonist may be 1.5 times, 2 times, 2.5 times, 3 times, 3.5 times, 4 times, or 5 times greater than the second amount. In one typical formulation, for a subject weighing <30 kg (e.g., ≥15 kg to <30 kg), the antagonist is administered as a loading dose of approximately 200 mg followed by one or more maintenance doses of approximately 100 mg, or as a loading dose of approximately 600 mg followed by one or more maintenance doses of approximately 300 mg.In another typical embodiment, for a subject weighing ≥30 kg (e.g., ≥30 kg to <60 kg), the interleukin-4 receptor antibody could be administered as a loading dose of approximately 400 mg followed by one or more maintenance doses of approximately 200 mg, or as a loading dose of approximately 600 mg followed by one or more maintenance doses of approximately 300 mg. In yet another typical embodiment, for a subject weighing ≥60 kg, the interleukin-4 receptor antibody could be administered as a loading dose of approximately 600 mg followed by one or more maintenance doses of approximately 300 mg. In some cases, a single initial dose of 600 mg (two 300 mg injections at different injection sites) is given, followed by a 300 mg dose every two weeks. In some cases, it is administered via a pre-filled syringe. In some cases, it is administered via a pre-filled pen. In some cases, it is administered via an auto-injector. In some cases, it is administered by injecting a 300 mg dose diluted in 2 mL of solution into a pre-filled, single-dose syringe with a protective needle cap. In some cases, a single initial dose of 400 mg (two 200 mg injections at different injection sites) is given, followed by a 200 mg dose every two weeks. In some cases, it is administered by injecting a 200 mg dose diluted in 1.14 mL of solution into a pre-filled, single-dose syringe with a protective needle cap. In some respects, it is administered by injecting a 300 mg dose diluted in a 2 ml solution into a pre-filled, single-dose syringe. Referring to Figure 1, a schematic overview of the System 100 architecture is shown. The System 100 architecture displays a set of functional modules and the graphical links that connect them. It includes a User 104 device running an application containing several functional modules, as shown in the central box. The System 100 architecture also illustrates how the application running on User 104 interacts with other service providers to enhance the information that can be delivered to the user through the application. For example, this can be achieved by connecting to insurance / benefits providers and pharmacies. One such functional module is Log 102. Log 102 is configured to allow the user to maintain a record of one or more of their medical conditions. The record may contain multiple entries detailing episodes of the condition or conditions, such as symptoms, the user's health data, contextual information, or similar details. The record can be used to monitor the condition or conditions to identify patterns and potential triggers for episodes. Log 102 may connect to an external service called Adverse Events. The log may transmit patient information related to episodes of the condition or conditions to the Adverse Events service. The record may also maintain a record of the user's adherence to a treatment regimen, such as a medication regimen. For example, a record entry might include a record of a dose of medication (such as a scheduled dose) taken by the user, like an injection record. The record might also be a dose record, which includes a set of information related to the dose the user took. The record can be stored as part of a record entry or independently of it. The functional unit may also include a memory module or database module 106. Memory module 106 is configured to store log entries added by the user via log module 102 for later retrieval and / or analysis. In some implementations, memory module 106 can be connected to the cloud and store entries in the memo remotely. In some implementations, the functional modules may also include a Weather 108 module. The Weather 108 module is configured to determine and / or record weather conditions at the user's location. The user's location can be determined, for example, using the Global Positioning System (GPS) feature on the user's device. The Weather 108 module can, for example, access an online weather forecasting system to obtain current, past, and / or future weather forecasts. The Weather 108 module can then provide the Log 102 module with weather conditions for inclusion in log entries. In addition to weather conditions such as general weather, temperature, humidity, atmospheric pressure, and ultraviolet index, the Weather module may also obtain air quality information such as pollen count, pollution index, nitrogen dioxide (NO2) count, and / or air quality index. Another functional module is the user management module 110. The user management module 110 is responsible for obtaining user preferences and creating notifications to be displayed on the user's device 104. The data necessary for the notification system may be stored in memory module 106. The user management module 110 can also update the information stored in memory module 106 during application use. The User Management Unit 110 can define and implement a notification system that specifies when a notification should be created and how it should be displayed on the User 104 device. This notification system may include three main types of notifications: (1) silent notifications, (2) summary notifications, and (3) pop-up notifications. In some implementations, a silent notification may be sent to the app without an audible alert, making it visible only within the app. A silent notification may also be presented to the user within the app, for example, on the app's home screen. In some implementations, silent notifications are displayed to the user when certain requirements are met and do not require any action from the user. A summary notification may relate to several different reminders and other notifications. The user can interact with the summary notification to expand it and view individual notifications. The summary notification may indicate the number of notifications the user needs to review. A push notification may relate to a single notification and be sent to the lock screen or home screen of the user's device. In some implementations, pop-up notifications are urgent and contain items requiring immediate action, demanding the user's attention. These notifications are intended for actions related to the user's treatment routine or as follow-up to actions that may affect the user's access to treatment or medication. Notifications may escalate, meaning they move to a higher level of notification, depending on the user's actions (or inaction). For example: A. Five days before the user’s next medication dose, a reminder of their next dose will appear as a silent notification within the application, for example, below the horizontal scroll bar on the application’s home page. b. In the days leading up to the dose appointment, the app will send group notifications to the user to review instructional videos, book a call with a nurse, or review self-use instructions. c. On the day of the dose, one hour before the scheduled time, the app will send a notification to the user to remind them to take their dose. If the user's medication is refrigerated, the notification will instruct the user to remove it from the refrigerator. Responding to this notification will trigger a preset timer for their medication. Another functional unit is Health / Assessment 112. Health / Assessment 112 is responsible for user registration and collecting details about the user's medical conditions and the medications used to treat them. Health / Assessment 112 may also collect information about the user's prescriptions and manage medication delivery. Another functional unit is the Health Care Professional (HCP) Services unit. The HCP is responsible for facilitating communication with nurses, doctors, or other healthcare professionals, including scheduling reminders for appointments and calls, prompting users to create reports or prepare for upcoming appointments or calls, initiating audio or video calls, providing follow-up notifications after calls or appointments, and initiating post-call or post-appointment log entry. The HCP interacts with the online Patient Support Program. Healthcare professionals may also have access to certain aspects and information held by the Patient Support Program to facilitate communication with the user and monitor the user's treatment and / or disease progression. Another functional unit is the consent module, which—in conjunction with other system components—manages consents and permissions related to accessing patient information, such as the user's health data. Memory module 106 can be configured to store user ID and role information, as well as consent templates, for use within the consent module. Memory module 106 may also store consent and permission information entered by the user through the consent module, including any time limits set for those consents and permissions. The consent unit may communicate with an external service called the Consent Management Service. Consent information and authorizations generated by the consent unit may be stored or copied to the Consent Management Service. The Consent Management Service may also be responsible for sending patient information to third parties when the associated consents indicate that such communication is permissible. Another functional unit is the Content Unit. The Content Unit is responsible for receiving and recording personalized content and / or preferences set by the user. The Content Unit may connect to an external service called Content Management 132. The Content Management service is responsible for providing patient-specific content or settings from an external user, such as a healthcare professional. The Content Unit may also interact with the Memory Unit 106 to store personalized content and / or settings. Another functional unit is the benefits unit, which—in conjunction with other aspects of the system—is responsible for managing patient access to healthcare. The benefits unit may include a pharmacy integration service and / or a benefits integration service. The information generated by the benefits unit may be responsible for sending patient-specific information to third parties to indicate that the patient has access to healthcare services. The benefits unit may also interact with external services, such as benefits provider systems and pharmacy services. Another functional unit is the analytics unit. Analytics Unit 126 is responsible, in conjunction with information from User Management Unit 110 and Record Unit 102, for analyzing patient information related to the user's medical condition and / or treatment. Another functional unit is the messaging system. The messaging system may connect to the analytics unit. For example, if the analytics unit detects a seizure or a seizure trigger in one or more of the user's medical conditions, the messaging system will send a message reporting this finding. The messaging system may also connect to an external service called the information center. The information center may store data received from the messaging system. It may also interact with other service providers to improve the information that can be stored about the user through the application. For example, by connecting to patient support programs, insurance / benefits provider systems, pharmacies, adverse event services, etc. Now, referring to Figure 2, a flowchart illustrates the steps the application takes to monitor the medication dosage schedule and help the user manage overdue doses. The application is run on a computing device, such as a mobile phone, tablet, smartwatch, or other wearable device. In step 200, the application monitors the current medication dosage schedule set within the application. The medication dosage schedule contains the prescribed dose frequency, which is the primary metric monitored. In step 202, the application determines that the time period for taking a scheduled dose has been exceeded. The medication's dosing schedule may specify the day the user takes their dose, and the "time period" may be a full 24-hour period within that day. A specific time within the day may not be required; as long as the user takes the prescribed dose before midnight on the specified day, it is considered to have been taken on time. Therefore, the application may determine that the time period for taking a scheduled dose has been exceeded if, by midnight on the specified day, it does not receive input from the user indicating that the prescribed dose has been taken. In some other instances, a specific time within the specified day may be designated as the end of the time period. In step 204, the application determines whether the scheduled dose has been missed by more than a minimum time. This minimum time is set within the application and may define the minimum period after which specific missed dose procedures should be recommended to the user. The minimum time may depend on the specific medication being monitored, the dosage of that medication, the specific illness or illnesses for which the medication is prescribed, and the frequency of doses prescribed to the user. Examples of different dose frequencies and minimum time limits are discussed below, with reference to Figures 3A–9. If, in step 204, the scheduled dose period has been exceeded by more than the minimum time, the application will proceed to step 206, where it will display a late dose notification to alert the user to the missed dose. The late dose notification can be displayed as a pop-up notification on the computer's lock screen or home screen, as shown in Figures 3a and 4a. Alternatively, the late dose notification can appear as a notification within the application's graphical user interface (GUI). Any additional content of the late dose notification may depend on the specific medication being monitored, the dosage of that medication, the specific illness or illnesses for which the medication was prescribed, and the frequency of the user's prescribed doses. The late dose notification may advise the user not to take the missed dose immediately and to wait until the next scheduled dose (as shown in Figure 3a). Alternatively, the late dose notification may advise the user to take the missed dose immediately or as soon as possible. The late dose notification can be determined or otherwise interacted with by the user. In step 208, in response to the detection of user interaction with the late dose notification, the application provides the user with two options: either to indicate that they have taken their scheduled dose or to indicate that they have not. More than one form of each option can be presented. For example, options might be offered to indicate that the user took their scheduled dose that day or the previous day. Options available to the user to indicate that they have not taken their scheduled dose might include an option to be reminded later to take their scheduled dose and an option to initiate the guided dosing process. If the user indicates that they wish to initiate a guided dosing process, the application might then begin displaying a step-by-step self-dosing guide. The options can be displayed on the user's device screen as selectable UI icons. For example, the icons might be selectable radio buttons with appropriate text. In some other incarnations, the options may be presented audibly, either in addition to or as an alternative to the visual display.The audio options may require the user to indicate whether or not they have taken the scheduled dose through an audio response. After receiving user input indicating that they have taken a dose, the application may display another screen asking the user to specify when the dose was taken (as shown in Figure 3c). From this answer, the application can determine whether the dose was taken after the minimum time limit. In step 210, the application receives user input indicating that the user has taken the scheduled dose after the minimum time limit. In response, in step 212, the application provides the user with two options: either to reset the current medication dosing schedule or to maintain the current schedule. The options may be displayed on the user's device screen as selectable UI icons. For example, the icons may be selectable radio buttons with appropriate text (as shown in Figure 3f and Figure 5a). In some other incarnations, the options may be presented audibly, either in addition to or as an alternative to the visual display. The audible options may prompt the user to indicate whether they wish to reset or maintain the current medication dosing schedule via an audio response. The process may end after the user selects one of the options presented in step 212. If the user chooses to maintain the current schedule, a relevant information screen may be displayed. If the user chooses to reset the current schedule, a screen may be displayed providing information about the new schedule. This screen may also allow the user to specify the time they wish to receive a reminder to take their next scheduled dose on the designated day. As discussed above, the application can be programmed to behave differently with regard to missed dose notifications and related actions, depending on the specific medication being monitored, the dosage of that medication, the specific illness or illnesses for which the medication was prescribed, and the frequency of doses prescribed to the user. The flowcharts in Figures 7-9 illustrate three different typical ways the application might operate. Figure 7 shows a flowchart illustrating the steps the application performs to monitor a medication dosing schedule in the first typical mode. In step 700, the application monitors the current medication dosing schedule set within the application and determines that the time period for taking a scheduled dose has been exceeded. This can also be called a "late dose." The medication dosing schedule specifies the day the user takes their dose, and the "time period" is a full 24-hour period within that specified day. Step 700 involves the application determining that the user has not provided an entry indicating that the scheduled dose was taken on the scheduled day. Step 700 may be very similar to steps 200, 202, and 204 combined, as illustrated in Figure 2. In response to the detection that the scheduled dose has been missed, the application displays a notification at step 702 to take the scheduled dose. This notification can also be called a "late dose notification." Its primary purpose is to alert the user that they appear to be late in taking their scheduled dose, but it may also provide guidance on the recommended next steps, in this case, to take the scheduled dose as soon as possible. Step 702 may be very similar to step 206, as illustrated in Figure 2. In step 704, the application determines whether the user has taken the scheduled dose. The late dose notification can be selected or otherwise interacted with by the user. In response to the detection of user interaction with the late dose notification, the application provides the user with two options: either to indicate that they have taken the scheduled dose or to indicate that they have not. The display of these two options may correspond to step 208, illustrated with reference to Figure 2. The user may indicate that they have taken the scheduled dose ("Yes" in step 704) by selecting the first GUI icon displaying text indicating this (see item 340 in Figure 4b). This may correspond to step 210, illustrated with reference to Figure 2. In step 706, the user may indicate that they have not taken the dose (the "No" option in step 704) by selecting the second GUI icon with text indicating that the user is ready to begin the dosing process now (see item 342 in Figure 4b). Alternatively, in step 706, the user may indicate that they have not taken the dose (the "No" option in step 704) by selecting the GUI icon with text indicating that the user wishes to be reminded to take the dose at a later time (see item 344 in Figure 4b). When the application receives user input indicating that the user has taken their scheduled dose late, in step 710, the application determines whether the dose was delayed by more than x days. The symbol x represents a variable integer number of days. If the dose was delayed by more than x days ('Yes' in step 710), the application will automatically reset the dosing schedule in step 712. A suitable screen may be displayed to inform the user that the dosing schedule is being reset (e.g., as shown in Figure 5b). If the dose was not delayed by more than x days ('No' in step 710), the application will first provide an option to reset the dosing schedule in step 714 and a second option to maintain the current dosing schedule in step 716. These two options are provided simultaneously (e.g., as shown in Figure 5a). Steps 714 and 716 may be concurrent with step 212, as shown in Figure 2. The process shown in the flowchart in Figure 7 can be used for a dosing schedule with any dosing frequency (time between scheduled doses) and any value of x. In one implementation, the process in Figure 7's flowchart is used for a weekly schedule (dosing frequency every 7 days) with x set to 6 days. In this implementation, the application will offer the option to reset or maintain the dosing schedule if a dose is taken 6 days or less after the scheduled day. If a dose is taken 7 days or more after the scheduled day, the dosing schedule will be automatically reset, and the user will be notified. Figure 8 shows a flowchart illustrating the steps the application performs to monitor the medication dosing schedule in typical mode 2. In step 800, the application monitors the current medication dosing schedule set within the application and determines that the time period for taking a scheduled dose has been exceeded. This can also be called a "late dose." The medication dosing schedule specifies the day the user takes their dose, and the "time period" is a full 24-hour period within that specified day. Step 800 involves the application determining that the user has not provided an entry indicating that the scheduled dose was taken on the scheduled day. Step 800 may be very similar to steps 200 and 202 combined, as illustrated in Figure 2. In step 802, the application determines whether the scheduled dose interval has been exceeded by more than x' days. This step may be very similar to step 204 in the figure, where x' represents the minimum time. If the scheduled dose interval has not been exceeded by more than x' days ("No" in step 802), the application will display a late dose notification in step 804 to alert the user to a possible late dose (e.g., Figure 4a) and optionally advise them to take their scheduled dose. In step 808, the app determines whether the user has taken the scheduled dose. The late dose notification from step 804 can be selected or otherwise interacted with by the user. Upon detecting user interaction with the late dose notification, the app provides the user with two options: to indicate that they have taken the scheduled dose or to indicate that they have not. In step 810, the user may indicate that they have not taken the dose (the "No" option in step 808) by selecting the second GUI icon with text indicating that the user is ready to begin the dosing process now (see item 342 in Figure 4b). Alternatively, in step 812, the user may indicate that they have not taken the dose (the "No" option in step 808) by selecting the GUI icon with text indicating that the user wishes to be reminded to take the dose at a later time (see item 344 in Figure 4b). The user may indicate that they have taken the scheduled dose (“Yes” in step 808) by selecting the first GUI icon displaying text indicating this (see item 340 in Figure 4b). In response, in step 814, the application maintains the current dosing schedule. The application may display a suitable screen to inform the user that the dosing schedule will be maintained (for example, as shown in Figure 4c). Returning to step 802, if the scheduled dose period is exceeded by more than x' days (a "yes" response in step 802), the application will display a late dose notification in step 806 to alert the user to the potential late dose and advise them to wait until the next scheduled dose, i.e., not to take the missed dose (e.g., Figure 3a). A "yes" response in step 802 may be equivalent to a "yes" response in step 204 in Figure 2, while step 806 may be very similar to step 206 illustrated in Figure 2. In step 816, the application determines whether the user has taken the scheduled dose. The late dose notification from step 806 can be selected or otherwise interacted with by the user. In response to the detection of user interaction with the late dose notification, the application provides the user with two options: either to indicate that they have taken the scheduled dose or to indicate that they have not taken the scheduled dose, for example, as shown in Figure 3b. The display of these two options may correspond to step 208, illustrated with reference to Figure 2. The user may indicate that they have not taken the dose ("No" in step 816) by selecting a GUI icon with text indicating this or a more general text indicating negation (see item 306 in Figure 3b). In response, the application proceeds to step 814, where it maintains the current dosing schedule. The application may display a screen to inform the user that the dosing schedule will be maintained (for example, as shown in Figure 4c). The user may indicate that they have taken the scheduled dose (“Yes” in step 816) by selecting a GUI icon with text indicating this (see item 308 in Figure 3b). This may correspond to step 210, illustrated with reference to Figure 2. In response, the application in step 818 determines whether the dose has been delayed by more than y’ days. The symbol y’ represents a variable integer of days. If the dose has been delayed by more than y’ days (“Yes” in step 818), the application in step 820 will automatically reset the dosing schedule. A suitable screen may be displayed to inform the user that the dosing schedule is being reset (e.g., as shown in Figure 5b). If the dose has not been delayed by more than y’ days (“No” in step 818), the application in step 822 will provide an option to reset the dosing schedule and in step 824 will provide a second option to maintain the current dosing schedule. These two options are provided simultaneously (e.g., as shown in Figure 5a). Steps 822 and 824 may together correspond to step 212 shown with reference to Figure 2. The process shown in the flowchart in Figure 8 can be used for a dosing schedule with any dosing frequency (time between scheduled doses), any value of x', and any value of y' greater than x'. In one implementation, the process in the flowchart in Figure 8 is used for a two-week schedule (dosing frequency every 14 days), with x' being 7 days and y' being 13 days. In this implementation, the app will provide a notification to take the scheduled dose if it is 7 days or less after the scheduled day. It will provide a notification to wait for the next scheduled dose if it is 8 days or more after the scheduled day. In this implementation, the app will also offer the option to reset or maintain the dosing schedule if the dose is taken 13 days or less after the scheduled day. If the dose is taken 14 days or more after the scheduled day, the dosing schedule will be automatically reset, and the user will be notified. Figure 9 shows a flowchart illustrating the steps the application performs to monitor a medication dosing schedule in typical mode 3. In step 900, the application monitors the current medication dosing schedule set within the application and determines that the time period for taking a scheduled dose has been exceeded. This can also be called a "late dose." The medication dosing schedule specifies the day the user takes their dose, and the "time period" is a full 24 hours within that specified day. Step 900 involves the application determining that the user has not provided an entry indicating that the scheduled dose was taken on the scheduled day. In step 902, the application determines whether the scheduled dosing period has been exceeded by more than x'' days. In this typical mode, x'' is the only threshold value used. If the scheduled dosing period has not been exceeded by more than x'' days ("No" in step 902), the application will maintain the current dosing schedule in step 904. The application may display a suitable screen to inform the user that the dosing schedule will be maintained (for example, as shown in Figure 4c). In step 906, the app determines whether the user has taken the scheduled dose. Even if the scheduled dose is delayed by x'' days or less, the app does not display any notification of the delayed dose. If the app does not receive user input indicating that the dose has been taken ("No" in step 906), the app will continue monitoring for the potential delayed dose in step 902. If the app does not receive user input indicating that there is a delay in taking the dose of less than x'' days ("Yes" in step 906), the app will maintain the current dosing schedule in step 908. The app may display an appropriate screen to inform the user that the dosing schedule will be maintained (for example, as shown in Figure 4c). Returning to step 902, if the scheduled dose period is exceeded by more than x'' of days ("Yes" in step 902), the application in step 910 will display a late dose notification to alert the user to a possible late dose (see Figure 6) and to optionally advise them to take the scheduled dose. In step 912, the application again determines whether the user has taken the scheduled dose. The late dose notification in step 910 can be selected or otherwise interacted with by the user. In response to the detection of user interaction with the late dose notification, the application provides the user with two options: to indicate that they have taken the scheduled dose or that they have not, for example, as shown in Figure 4b. The user may indicate that they have taken the scheduled dose ("Yes" in step 912) by selecting the first GUI icon displaying text indicating this (see item 340 in Figure 4b). In response, the application automatically resets the dose schedule in step 918. A suitable screen may be displayed to inform the user that the dose schedule is being reset (for example, as shown in Figure 4d or Figure 5b). In step 914, the user may indicate that they have not taken the dose ("No" in step 912) by selecting the second GUI icon with text indicating that the user is ready to begin the dosing process now (see item 342 in Figure 4b). Alternatively, in step 916, the user may indicate that they have not taken the dose (the alternative option "No" in step 912) by selecting the GUI icon with text indicating that the user wishes to be reminded to take the dose at a later time (see item 344 in Figure 4b). The process shown in the flowchart in Figure 9 can be used for a dosing schedule with any dosing frequency (time between scheduled doses) and any value for x''. In one implementation, the process in Figure 9's flowchart is used for a four-week schedule (dosing frequency every 28 days) with a value of x'' of 7 days. In this implementation, the app will not adjust the dosing schedule if the user takes a dose 7 days or less after the scheduled day. The app will provide a notification if the scheduled dose is taken 8 days or more after the scheduled day. If the dose is taken 8 days or more after the scheduled day, the dosing schedule will be automatically reset, and the user will be notified. Now, looking at Figures 3A through 3G, we see screenshots that the app displays when monitoring the current medication dosing schedule and provides guidance and follow-up options for the user, according to some representations. In the first screen, 300, shown in Figure 3A, the app displays Notification 302 on the screen of user 104's device. Notification 302 may be a pop-up message displayed on the lock screen or home screen of user 104's device. Notification 302 may be displayed in response to the app determining that the time period for taking a scheduled dose has been exceeded by more than the minimum time. For example, if the time period for taking a scheduled dose has been exceeded by more than the minimum time and the app has not received input from the user confirming that the scheduled dose has been taken, Notification 302 will be displayed. Notification 302 may be called the "Late Dose Notification." Notification 302 may alert the user to the fact that they appear to be late in taking a scheduled dose. Notification 302 displays the text: "It appears you are more than 7 days late for your last dose," in which case 7 days represents the minimum time. However, any suitable text can be used to alert the user.Notice 302 also provides some guidance to the user, in this case: "We recommend waiting until the next scheduled dose on June 15." The date and text are just examples. In this way, the app can implement guidance for missed doses based on the specific combination of medication and the condition being treated, and proactively deliver this guidance to the user at the most effective time. When the user interacts with notification 302, the application may display screen 304, shown in Figure 3b. This screen 304 reiterates the information that the user is more than 7 days late in taking their dose and recommends waiting until the next scheduled dose. Screen 304 may also explicitly state that this recommendation is based on the Missed Dose Guidelines and / or provide a link to view these guidelines in full. Screen 304 also indicates that if the user has already taken the dose, they can record this in the application to maintain an accurate record. Screen 304 also presents the user with two options to indicate whether they have taken their scheduled dose or not. The first option, selectable by user 306, may be a negative option and could contain appropriate text such as "Close," "I did not take my last scheduled dose," or something similar. The second option, selectable by user 308, may be a positive option and could contain appropriate text such as "I took my last scheduled dose," or something similar. If the user selects the first option, selectable by user 306, the application may close. Alternatively, the application may first display a confirmation screen (not shown) explaining that the user's current dosing schedule will be maintained and they will be reminded of the date of their next scheduled dose. If the user selects the second user-selectable option, 308, the application will begin the dose recording process by displaying a third screen, 310, as shown in Figure 3c. This third screen contains appropriate text prompting the user to enter when the last dose was taken and one or more input boxes, 312, to specify the day and, optionally, the time of the last dose. The input boxes, 312, can be implemented as drop-down lists, scrollable or draggable icons, selection wheels, free-text boxes, or any other suitable data entry method. After confirming the day and, optionally, the time of the last dose, the application may display a fourth screen, 316, as shown in Figure 3d. This screen displays a model of the human body (e.g., a mannequin) with several different body regions identified. These body regions are linked to common, predefined injection sites. This allows both the user and the healthcare provider to track the injection site over time and ensure that the same area is not overused. If the medication dose is not administered by injection or infusion, the fourth screen, 316, will not be displayed. As used in this document, the term injection or self-injection is intended to include intravenous injection, intramuscular injection, infusion, or any injection system containing a needle, as defined in Table 1 of Section 5.2 of ISO 11608-1:2014(E). As defined in ISO 11608-1:2014(E), needle-based injection systems can be broadly distinguished into multi-dose container systems and single-dose container systems (with partial or complete evacuation). The container may be a replaceable container or a non-replaceable integrated container. When the user selects to continue from screen 4 (316), the application displays screen 5 (318), as shown in Figure 3E. Screen 5 (318) prompts the user to indicate how easy or difficult it was to take the dose using a digital scale. Any other suitable method of indication can be used, such as a qualitative description (e.g., "difficult," "good," "easy") or visual cues, such as emojis. While the application may also provide a full daily function allowing the user to track their treatment and disease progression in detail, the entry for the delayed dose may be brief to encourage users to complete this entry, thus keeping the dose log up to date. After completing the short log entry shown in Figures 3C to 3E, the application confirms, through the information entered on screen 310, that the user is more than seven days late in taking their scheduled dose. In response, the application displays screen 320, as shown in Figure 3F, to inform the user that they are more than seven days late in taking their scheduled dose and recommends contacting their healthcare provider for guidance on their dosing schedule. Screen 320 also provides the user with two options: to reset their current medication dosing schedule or to maintain their current schedule. A selectable reset button (322) is provided with appropriate text such as "Reset Injection Reminders." A selectable continuation button (324) is also provided with appropriate text such as "Maintain My Current Routine." When the user selects the Reset button 322, the application displays a seventh screen 326 showing the dosing routine details, as illustrated in Figure 3g. This seventh screen 326 contains one or more Information boxes 328 that specify the day of the next scheduled dose and, optionally, the dosing frequency, which in this case is every two weeks. The Information boxes 328 may not be editable by the user and may have a different appearance (e.g., appear grayed out) to indicate this. The seventh screen 326 also displays a Reminder input box 330. The user may interact with the Reminder input box 330 to set the time they wish to receive a reminder to take their next scheduled injection on the designated day. The Reminder input box 330 can be implemented as a drop-down list, a scrollable or draggable icon, a selection wheel, a free text input box, or any other suitable data entry method. Finally, the seventh screen 326 may display a Step-by-Step Guide 332 toggle that allows the user to select whether or not they wish to view the Step-by-Step Dosing Guide at the time of the next scheduled dose. Figures 4A to 4F show typical screenshots that the application displays regarding additional notifications and subsequent action options. In screen 834, shown in Figure 4A, the application displays Notification 336 on user 104's device screen. Notification 336 may be a pop-up message displayed on the lock screen or home screen of user 104's device. Notification 336 may alert the user that they may have missed a scheduled dose. Notification 336 displays the text: "Did you miss your last dose?" and / or "It looks like you missed your last scheduled dose on June 1st." However, any appropriate text can be used to alert the user. Notification 336 may also provide some guidance to the user, such as recommending that the user take their scheduled dose now or as soon as possible. Notice 336 may be displayed in two different scenarios, depending on the dosing frequency and late dose guidelines for the specific drug / disease combination being monitored. In the first scenario, Notice 336 is displayed in response to the application determining that the time interval for taking a scheduled dose has been exceeded by more than the minimum time. For example, if the time interval for taking a scheduled dose is exceeded by more than the minimum time and the application does not receive input from the user confirming that the scheduled dose has been taken, Notice 336 will be displayed. Notice 336 may therefore be a form of "late dose notification" displayed instead of Notice 302, as shown in Figure 3A. In some implementations, Notice 336 is displayed when the dosing frequency is every 7 days and the minimum time is one day; that is, if the user is one day or more late in taking the dose, Notice 336 is displayed (see also the flowchart in Figure 7). In the second scenario, notification 336 is displayed in response to the application's determination that the time period for taking a scheduled dose has been exceeded by less than the minimum time. For example, if the time period for taking a scheduled dose is exceeded by less than the minimum time and the application does not receive input from the user confirming that the scheduled dose has been taken, notification 336 will be displayed. In this case, notification 336 may be displayed in addition to notification 302 shown in Figure 3A and can be called the "Missed Dose Notification" to distinguish it from the "Late Dose Notification" discussed in Figure 3A. As is standard practice, in the second scenario, if the user is more than a minimum time late in taking their scheduled dose, screen 300 shown in Figure 3A will be displayed, while if they are less than a minimum time late, screen 334 shown in Figure 4A will be displayed. Therefore, the Missed Dose 336 notification may initially be displayed for one day or more, and if the user does not interact with the Missed Dose 336 notification before the minimum time limit is exceeded, the Late Dose 302 notification will be displayed instead of the Missed Dose 336 notification.In some incarnations, Notice 336 is displayed when the frequency of doses is every 14 days and the minimum time is 7 days, i.e. if the user is 7 days or less late in taking the dose, then Notice 336 is displayed. If the user is 8 days or more late in taking the dose, Notice 302 will be displayed (see also the flowchart in Figure 8). In this way, the application can implement guidelines for missed doses according to the specific combination of the drug and the disease being treated for multiple different dosing schedules and proactively deliver these guidelines to the user at the most effective time. In either of the two scenarios described above, when the user interacts with notification 336, the application may activate and display screen 9 338, as shown in Figure 4b. This screen 9 338 presents the user with one option to indicate that they have taken their last scheduled dose and two options to indicate that they have not yet taken their last scheduled dose. The first selectable option 340 states that the user has taken their last scheduled dose and may include appropriate text such as "I have taken this dose and would like to record the details." The second selectable option 342 states that the user has not yet taken the dose but will do so now and may include appropriate text such as "I am ready to start the process now." The third selectable option 344 states that the user has not yet taken the dose and would like to be reminded to do so later and may include appropriate text such as "Remind me later today." If the user selects the first selectable option, 340, the application may display screens suitable for log entry, such as screens 3 through 5, 310, 316, and 318, as shown in Figures 3c through 3e. If the user selects the second selectable option, 342, the application may display the upcoming injection screen, such as screen 354, as shown in Figure 4f. Screen 354 may display dose preparation information confirming the date of the next dose and, optionally, the time the user requested to be reminded to take this dose, as well as the method of administration and the dose amount. The user can review this information and select the Continue button. The application may then display a step-by-step dosing guide. When the dose is an injection, the preparation information may also include a reminder to remove the medication from the refrigerator at a predetermined time before the injection. The application may also provide a countdown timer to help the user monitor this warm-up period. If the user selects the third selectable option, 344, the application may display a screen suitable for creating reminders.The reminder can be limited to a later time on the same day (or within the same 24-hour period). Figures 4C and 4D illustrate examples of the final screens that may appear in different scenarios, depending on the dosing frequency and delayed dose guidelines for the specific drug / disease combination being monitored. Figure 4C shows screen 10, screen 346, which appears when the user is 7 days or less late in taking their dose when the dosing frequency is every 14 days. In this case, screen 10, screen 346 indicates that no change will be made to the user's dosing schedule and informs them of the date of the next scheduled dose according to the current schedule; that is, the user does not have the option to change the dosing schedule in this situation. In some cases, a maximum time limit is set, so that if it is exceeded, the application automatically resets the user's dosing schedule. Figure 4D shows screen 11348, which appears when the user takes their dose after exceeding the maximum time limit. The maximum time limit may be equal to the dosing frequency. For example, screen 10348 may appear when the user is 14 days or more late in taking their dose when the dosing frequency is every 14 days. Screen 11348 indicates that the user is late (in this example, more than 14 days late while the dosing frequency was every 14 days), although it may not explicitly state that they have exceeded the maximum limit. Screen 11348 informs the user that the dosing schedule will be reset and provides a selectable button350 for the user to confirm their understanding and perform the schedule reset. Resetting the dosing schedule generally means that the dosing frequency is reset so that it is calculated starting from the current day. Figure 4E shows screen 12, screen 352, which may appear whenever the dosing schedule is reset. Screen 12, screen 352 displays the application's main graphical user interface. An additional prominent notification appears in the graphical user interface to indicate that the dosing schedule has been reset. Figures 5A and 5B illustrate examples of the final screens that may be displayed in different situations, depending on the frequency of dosing and delayed dosing guidelines for the specific drug / disease combination being monitored. Figure 5A illustrates screen 14 (500), which appears when a user misses a dose by more than one day on a 7-day dosing schedule. In this case, screen 14 (500) informs the user that they have taken the scheduled dose outside their treatment cycle and recommends they contact their healthcare provider for guidance on the dosing schedule. Screen 14 (500) also provides the user with two options: to reset their current dosing schedule or to maintain their current dosing schedule. A selectable reset button (502) is provided with appropriate text such as "Reset Injection Reminders." A selectable continuation button (504) is also provided with appropriate text such as "Maintain My Current Routine." When the user selects the reset button (502), the application displays screen 7 (326), which shows the dosing routine details, as illustrated and described above in Figure 3G. Figure 5b illustrates screen 506, which appears when a user is 7 days or more late in taking their dose when the dosing schedule is 7 days apart. In this case, screen 506 informs the user that they have taken the scheduled dose outside of their treatment cycle and recommends that they contact their healthcare provider for guidance on the dosing schedule. Screen 506 informs the user that the dosing schedule will be reset and provides a selectable button (508) for the user to confirm their understanding and proceed with the reset; the user does not have the option to maintain the dosing schedule in this situation. Figure 6 shows another example of a screen 600 containing a late dose notification (602) that the application causes to appear on the screen of user 104's device. Notification 602 may be a pop-up message displayed on the lock screen or home screen of user 104's device. Notification 602 is displayed in response to the application determining that the time period for taking a scheduled dose has been exceeded by more than the minimum time. For example, if the time period for taking a scheduled dose has been exceeded by more than the minimum time and the application has not received input from the user confirming that the scheduled dose has been taken, notification 602 will be displayed. Notification 602 may be called a "late dose notification." Notification 602 may alert the user to the fact that it appears they are late in taking a scheduled dose. Notification 602 displays the text: "It appears you are more than 7 days late for your last dose," in which case 7 days represents the minimum time. However, any appropriate text can be used to alert the user. The 602 notification also provides some guidance to the user, in this case: "When you take your next dose, we will adjust your treatment routine." In this way, the app can implement guidance for missed doses based on the specific combination of medication and the condition being treated, and proactively deliver this guidance to the user at the most effective time. When the user interacts with notification 602, the application may display screen 9 (338) shown in Figure 4b, where the user can indicate whether or not they have taken their dose. Once the user indicates that they have taken their dose, the application either displays a screen similar to screen 10 (346) shown in Figure 4c, where the user's dose schedule is maintained (i.e., they do not have the option to reset the dose schedule), or it displays a screen similar to screen 11 (348) shown in Figure 4c, where the user resets their dose schedule (i.e., they do not have the option to maintain the dose schedule). The example in Figure 6 may apply to a dose frequency of 28 days with a minimum interval of 7 days (see also the flowchart in Figure 9). Figure 10 schematically illustrates a User 400 device in various configurations. A User 400 device might be a mobile phone or a tablet. It is an example of a wireless communication device. A User 400 device can also be referred to as a communication device, computer, computing device, or mobile device, and is not necessarily associated with a single user. The User 400 device is configured to wirelessly connect to a communications network using a wireless communication protocol, such as, but not limited to, 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) and / or New Radio (NR) or WiFi (IEEE 802.11). The User 400 device may also be configured to communicate using Bluetooth, NFC, Zigbee, Ultra Wideband, IrDa, or similar technologies. The communications network may consist of one or more network nodes. The communications network may also connect via a core network and / or an intermediate network to a host computer (not shown), which may be integrated into the hardware and / or software of a standalone server, a cloud server, or a distributed server.The user device 400 and the host computer can be configured to exchange data between them. The User 400 device may consist of equipment that includes the Processing 401 circuitry. The Processing 401 circuitry may consist of a Processor 402 and Memory 404. The User 400 device may also consist of a Wireless Transceiver 406, User Inputs 408, a Display 412, a Camera 410, a Microphone 416, a Radio Frequency Identification (RFID) Reader 418, and a Speaker 414. The Wireless Transceiver 406 may be configured to establish and maintain a wireless connection to the network node. The Wireless Transceiver 406 may consist of one or more radio transmitters and one or more radio receivers. The Display may be touch-sensitive and may be based on capacitive or resistive sensing technology. The Processing 401 circuitry may include, for example, a microprocessor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or similar components. The 402 processor can be configured to read and / or write from 404 memory.404 memory may consist of volatile and / or non-volatile memory, such as cache memory, Random Access Memory (RAM), and / or Read-Only Memory (ROM), etc. A user device (400) can consist of a program stored, for example, in memory (404). The program can be executed by the processing circuit (401). The program may include an application, such as the one described above. In some implementations, the host computer may communicate with the application. The application can request data from the host computer and / or provide user data to it. The 401 processing circuit can be configured to execute or cause the execution of any of the methods described in this document. In some implementations, the program / software may contain instructions that, when executed by the 401 processing circuit, cause the 401 processing circuit to execute the methods described in this document. 404 memory may consist of program memory, which stores program code (such as software or firmware), and main memory, which stores data. The 401 processing circuit can be configured to execute the program code stored in program memory and to read, write, and delete data from main memory. In some implementations, the program code may be an application that can be downloaded and installed on the user's 400 machine. The application may be a disease management, treatment, and tracking tool for patient use. The program memory may be, for example, read-only memory (ROM), and the main memory may be, for example, random access memory (RAM). The User 400 device contains one or more User 408 inputs, for example, a touchscreen, mini-keyboard, keyboard, accelerometer, gyroscope, mouse, or microphone 416 for receiving voice commands. The User 400 device may also contain a Camera 410 configured to capture images of the user and images of labels, symbols, and similar information displayed on medication delivery devices, filling solutions, or storage solutions. The User 400 device may be configured to inspect medication delivery devices (such as injectors or inhalers) using an inspection device. An inspection device may refer to a Camera 410 or an RFID reader 418. The term "inspection," as used in connection with the User 400 device, may refer to the use of any of these vehicles to read information presented externally or internally on medication delivery devices. The terms "drug" and "drug" are used interchangeably in this specification and describe a pharmaceutical formulation containing one or more active pharmaceutical ingredients, their salts, or pharmacologically acceptable solvents, and may optionally contain a pharmacologically acceptable carrier. An active pharmaceutical ingredient is, in its broadest sense, a chemical compound that produces a biological effect in humans or animals. In pharmacology, drugs or medicines are used to treat, cure, prevent, or diagnose diseases, or are otherwise used to promote physical or mental health. Drugs or medicines may be used for a limited time or regularly to treat chronic disorders. As explained below, drugs or medicines can include at least one active pharmaceutical ingredient or a combination of ingredients in various types of formulations to treat one or more diseases. Examples of active pharmaceutical ingredients can include small molecules with a molecular weight of 500 Daltons or less, polypeptides, peptides, proteins (such as hormones, growth factors, antibodies, antibody fragments, and enzymes), carbohydrates, polysaccharides, and nucleic acids, such as double-stranded or single-stranded deoxyribonucleic acid (DNA) (including exposed and complementary deoxyribonucleic acid), ribonucleic acid (RNA), antisense nucleic acids, such as deoxyribonucleic acid and antisense RNA, small interfering ribonucleic acid (siRNA), ribozymes, genes, and oligonucleotides.Nucleic acids can be incorporated into molecular delivery systems such as vectors, plasmids, or liposomes. The use of mixtures consisting of one or more drugs is also being considered. Drugs or medications may be stored in a primary container or "drug box" designed for use with injectable drug devices. For example, a drug container may be a cartridge, syringe, reservoir, or a rigid or flexible container designed to provide a suitable compartment for storing one or more drugs (e.g., for short-term or long-term storage). For example, in some cases, the compartment may be designed to store a drug for at least one day (e.g., from 1 to at least 30 days). In other cases, the compartment may be designed to store a drug for approximately one month to two years. Storage may be at room temperature (e.g., around 20°C) or at refrigerated temperatures (e.g., from around -4°C to around 4°C). In some cases, a drug container may be a dual-compartment cartridge designed to store two or more components of a pharmaceutical formulation (e.g., an active pharmaceutical ingredient and a diluent, or two different drugs) separately, each in its own compartment.In such cases, the two chambers of a dual-chamber cartridge may be designed to allow mixing of the two or more components before and / or during administration into the human or animal body. For example, the chambers may be designed to be connected in terms of fluid flow (e.g., via a channel connecting the chambers), allowing the user to mix the components whenever desired before injection. Alternatively, or in addition, the chambers may be designed to allow mixing during administration into the human or animal body. The drugs or medications contained in drug delivery devices, as described in this specification, can be used to treat and / or prevent many different types of medical disorders. As used in this document, the terms "analogue" and "derivative" refer to a polypeptide whose molecular structure can be formally derived from that of a natural peptide by deleting and / or substituting at least one of the amino acid residues present in the natural peptide and / or adding at least one amino acid residue. The added and / or substituted amino acid residues can be either coding amino acid residues, other naturally occurring residues, or entirely synthetic amino acid residues. Specifically, the term "derivative" refers to a polypeptide whose molecular structure can be formally derived from that of a natural peptide, where one or more organic substituents (such as a fatty acid) are attached to one or more amino acids. Optionally, one or more of the amino acids present in the natural peptide may be omitted and / or replaced by other amino acids, including non-coding amino acids, or amino acids, including non-coding ones, may be added to the natural peptide. The term "antibody," as used in this specification, refers to an immunoglobulin molecule or a fragment thereof that binds to an antigen. Examples of antigen-binding fragments in immunoglobulin molecules include the F(ab) and F(ab')2 subunits that retain the ability to bind to an antigen. An antibody may be polyclonal, monoclonal, recombinant, chimeric, immunoreceptor-mediated, humanized, fully human, non-human (e.g., mouse-specific), or a single-chain antibody. In some incarnations, the antibody has an effector function and can bind complement. In other incarnations, the antibody has limited or no ability to bind to the Fc receptor. For example, the antibody may be a homologous, subtype, fragment, or mutant antibody that does not support binding to the Fc receptor, for instance, it may contain a genetically modified or deleted Fc receptor-binding region.The term antibody also includes an antigen-binding molecule based on tetravalent bispecific tandem immunoglobulins (TBTI) and / or an antibody-like binding protein with two cross-over binding region orientation (CODV) and a cross-arrangement of binding regions. The terms "fragment" or "antibody fragment" refer to a polypeptide derived from an antibody polypeptide molecule (e.g., a heavy-chain and / or light-chain antibody polypeptide) that does not contain the full-length antibody but still includes at least the antigen-binding portion of the full-length antibody polypeptide. Antibody fragments can include a truncated portion of a full-length antibody polypeptide molecule, although the term is not limited to such truncated fragments.The antibody fragments useful in this invention include, for example: Fab fragments, F(ab')2 fragments, scFv fragments (single-chain Fv fragments), linear antibodies, monovalent or polyvalent antibody fragments, such as bivalent, trivalent, and tetravalent antibodies, polyvalent antibodies (such as bivalent, trivalent, and tetravalent antibodies), monovalent or polyvalent antibody fragments, such as bivalent, trivalent, and tetravalent antibodies, microbodies, chelated recombinant antibodies, trivalent or bivalent antibodies, intrinsic antibodies, nanobodies, small modular immunopharmaceuticals (SMIPs), immunoglobulin fusion proteins with a binding domain, antibodies similar to their counterparts in the camel family, and antibodies containing VHH. Additional examples of antigen-bound antibody fragments are common in the field. The terms "framework regions" or "CDRs" refer to short peptide chains within the variable region of heavy and light-chain polypeptides that are primarily responsible for mediating the recognition of a specific antigen. The term "framework region" refers to amino acid sequences within the variable region of heavy and light-chain polypeptides that are not CDR sequences and are primarily responsible for maintaining the CDR sequences in the correct position to enable antigen binding. Although the framework regions themselves are not usually directly involved in antigen binding, as is well known in the field, certain residues within the framework regions of specific antibodies may be directly involved in antigen binding or may influence the ability of one or more amino acids in the CDRs to interact with the antigen. Examples of monoclonal antibodies include proprotein convertase subtilisin / Kexin type 9 (PCSK-9) (such as Alirocumab), a monoclonal antibody that targets the interleukin-6 receptor (such as Sarilumab), and a monoclonal antibody that targets the interleukin-4 receptor (such as Dupilumab). Pharmaceuticalally acceptable salts of any active pharmaceutical ingredient described in this specification may also be used in drugs or medications within a drug delivery device. Pharmaceuticalally acceptable salts include, for example, salts resulting from the addition of acids and basic salts. Professionals in the field will understand that modifications (additions and / or removals) can be made to various components of the active pharmaceutical ingredient, formulations, devices, methods, systems and embodiments described in this specification without going outside the full scope and basic concept of this invention which includes these modifications and any analogues thereof. A typical drug injector may include a needle-based injection system, as described in Table 1 of Section 5.2 of ISO 11608-1:2014(E). As described in ISO 11608-1:2014(E), needle-based injection systems can be broadly distinguished into multi-dose container systems and single-dose container systems (with partial or complete evacuation). The container may be a replaceable container or a non-replaceable integrated container. As described in more detail in ISO 11608-1:2014(E), a multi-dose container system may include a needle-based injector with a replaceable container. In this system, each container holds multiple doses, which may be fixed or variable (predefined by the user). Another multi-dose container system may include a needle-based injector with a built-in, non-replaceable container. In this system, each container holds multiple doses, which may be fixed or variable (predefined by the user). As described in more detail in ISO 11608-1:2014(E), a single-dose container system may include a needle-based injector with a replaceable container. In one example of such a system, each container holds a single dose, with the entire deliverable dose volume emptied (full discharge). In another example, each container holds a single dose, with only a portion of the injectable dose volume emptied (partial discharge). Also as described in ISO 11608-1:2014(E), a single-dose container system may include a needle-based injector with a built-in, non-replaceable container. In one example of such a system, each container holds a single dose, with the entire deliverable dose volume emptied (full discharge). In another example, each container holds a single dose, with only a portion of the injectable dose volume emptied (partial discharge).
Claims
1. A non-transitory computer-readable storage medium containing instructions that, when executed by a computing device, cause the computing device to: execute a program for managing the user's medical condition or treatment; monitor the current medication dosing schedule defined within the program and the medication dosing schedule containing the dosing frequency; determine that the time period for taking a scheduled dose has been exceeded; in response to the determination that the time period for taking the scheduled dose has been exceeded by more than the minimum time, display a late dose notification to alert the user to the missed dose; in response to the detection of user interaction with the late dose notification, provide the user with two options: (1) to indicate that they have taken the scheduled dose or (2) to indicate that they have not taken the scheduled dose; and when it is detected that the user indicates that they have taken the scheduled dose after the minimum time, provide the user with two options: (1) to reset the current medication dosing schedule in the1. The program or (2) maintains the current medication dosing schedule in the program.
2. Non-transitory computer-readable storage medium, according to protection element 1, where determining that a scheduled dose has been exceeded includes determining that the program did not receive user input indicating that a dose was taken at the end of the time period.
3. Non-transitory computer-readable storage medium, according to protection element 1 or protection element 2, where the late dose notification is displayed as a pop-up notification on the lock screen or home screen of the computing device.
4. Non-transitory computer-readable storage medium, according to any previous protection element, where providing the user with two options (1) to indicate that they have taken the scheduled dose or (2) to indicate that they have not taken the scheduled dose includes displaying a first selectable user interface icon and a second selectable user interface icon.
5. Storage mediumNon-transitory computer-readable storage medium, according to any previous safeguard, where the options available to the user to indicate that they have not taken the scheduled dose include an option to initiate the guided dosing process and an option to set a reminder to take the dose at a later time.
6. Non-transitory computer-readable storage medium, according to safeguard 5, where further instruction configuration, when executed by the computing device, causes the computer to: In response to receiving the user's selection of the option to initiate the guided dosing process, display a step-by-step self-dosing guide.
7. Non-transitory computer-readable storage medium, according to any previous claim, where further instruction configuration, when executed by the computer, causes the computer, upon detecting that the user has indicated that they have taken the scheduled dose, to: provide a user interface to specify the date and time of the dose; and provide an interfaceA user is used to determine the body position through which the dose was injected or pumped.
8. Non-transitory computer-readable storage medium: According to any previous safeguard, when it is detected that the user has selected the medication dosing schedule reset option, the instructions are further configured so that their execution by the computing device results in the computer providing a schedule reset screen that informs the user of the day of the next scheduled dose. The schedule reset screen is configured to allow the user to set a time to receive a reminder on the day of the next scheduled dose.
9. Non-transitory computer-readable storage medium: According to safeguard 8, the schedule reset screen can be further configured to allow the user to specify whether they want to review the step-by-step dosing guide at the time of the next scheduled dose.
10. Non-transitory computer-readable storage medium: According to any previous safeguard,Further instruction configuration, when executed by a computing device, results in the following: In response to the determination that the scheduled dose period has been exceeded by more than the maximum time, a late dose notification is displayed to alert the user to the missed dose; in response to the detection of user interaction with the late dose notification, two options are provided to the user: (1) to indicate that they have taken the scheduled dose or (2) to indicate that they have not taken the scheduled dose; and when it is detected that the user indicates that they have taken the scheduled dose after the maximum time limit, a dosing reset information screen is displayed, informing the user that the medication dosing schedule will be reset.
11. Non-transitory computer-readable storage medium according to security element 10, where the maximum time is equal to the dosing frequency.
12. Non-transitory computer-readable storage medium according to any previous security element, where the dosing frequency is every 7 days orEvery 14 days or every 28 days.
13. Non-transitory computer-readable storage medium: According to any of the safeguards 1 through 11, the delayed dose notification recommends that the user wait until the next scheduled dose.
14. Non-transitory computer-readable storage medium: According to safeguard 13, the dose frequency is every 14 days and the minimum interval is 7 days.
15. Non-transitory computer-readable storage medium: According to any of the safeguards 1 through 11, the delayed dose notification recommends that the user take the next scheduled dose.
16. Non-transitory computer-readable storage medium: According to safeguard 15, the dose frequency is every 7 days and the minimum interval is 1 day.
17. Non-transitory computer-readable storage medium: According to safeguards 1 through 11Protection 1-11, where further instruction configuration, when executed by a computing device, results in the computer performing the following: In response to the determination that the scheduled dose period has been exceeded by less than the minimum time, a missed dose notification is displayed to alert the user to the missed dose; in response to the detection of user interaction with the missed dose notification, two options are provided to the user: (1) to indicate that they have taken the scheduled dose or (2) to indicate that they have not taken the scheduled dose; and when it is detected that the user indicates that they have taken the scheduled dose before the minimum time, the current dosing schedule is maintained.
18. A user device that includes a processing circuit configured to: execute a program for managing the user's medical condition or treatment; monitor the current medication dosing schedule defined within the program and the medication dosing schedule that contains the dosing frequency; determine that the scheduled dose period has been exceeded; in response to the determination that the scheduled dose period has been exceeded by more than the minimum time, displaysA late dose notification alerts the user to a missed dose. In response to the detection of a user interaction with the late dose notification, the user is given two options: (1) to indicate that they have taken the scheduled dose or (2) to indicate that they have not taken the scheduled dose. When it is detected that the user indicates that they have taken the scheduled dose after the minimum time limit, the user is given two options: (1) to reset the current medication dosing schedule in the program or (2) to maintain the current medication dosing schedule in the program.
19. A computer-based method, which includes: implementing a program to manage the user's medical condition or treatment; monitoring the current medication dosing schedule defined within the program and the medication dosing schedule that contains the dosing frequency; determining that the time period for taking a scheduled dose has been exceeded; in response to the determination that the time period for taking the scheduled dose has been exceeded by more than the minimum time limit, a late dose notification is displayed to alert the user to the missed dose. In response to the detection of a user interactionWith a late dose notification, the user is provided with two options: (1) to indicate that they have taken the scheduled dose or (2) to indicate that they have not taken the scheduled dose. When it is detected that the user indicates they have taken the scheduled dose after the minimum time limit, the user is provided with two options: (1) to reset the current medication dosing schedule in the program or (2) to maintain the current medication dosing schedule in the program.
20. Non-transitory computer-readable storage medium containing instructions that, when executed by a computing device, cause the computing device to: execute a program for managing the user's medical condition or treatment; monitor the current medication dosing schedule defined within the program and the medication dosing schedule containing the dosing frequency; determine that the time limit for taking a scheduled dose has been exceeded; and respond to the determination that the time limit for taking the scheduled dose has been exceeded by more than the minimum.For the time frame, a late dose notification is displayed to alert the user to a missed dose. In response to the detection of user interaction with the late dose notification, the user is given two options: (1) to indicate that they have taken the scheduled dose or (2) to indicate that they have not taken the scheduled dose. When the user is detected indicating that they have taken the scheduled dose after the minimum time, a dosing reset information screen is displayed, informing the user that the medication dosing schedule will be reset.
21. Non-transitory computer-readable storage medium (CDSM) according to security element 20, where the late dose notification recommends that the user take the next scheduled dose.
22. Non-transitory computer-readable storage medium according to security element 21, where the dosing frequency is every 28 days and the minimum time is 7 days.
23. Non-transitory computer-readable storage medium according to security element 9, where the user is responsible forAlso, administering the next prescribed dose to himself.
24. A computer-based method for treating the subject with an anti-interleukin-4 receptor alpha antibody (anti-IL-4Rα), which includes providing guidance on administering a therapeutically effective amount of an anti-interleukin-4 receptor alpha antibody to the subject. The method includes the following: implementing a program to manage the user's condition or treatment; monitoring the current medication dosing schedule assigned within the program and the medication dosing schedule that contains the frequency of doses; determining that the time period for taking a scheduled dose has been exceeded; in response to determining that the time period for taking the scheduled dose has been exceeded by more than the minimum time, a late dose notification is displayed to alert the user to the missed dose; in response to detecting the user's interaction with the late dose notification, two options are provided to the user: (1) to indicate that he has taken the scheduled dose or (2) to indicate that he has not taken the scheduled dose; When it is discovered that the user indicates that they have taken the scheduled dose afterAt a minimum time, the user is provided with two options: (1) to reset the current medication dosing schedule in the program or (2) to maintain the current medication dosing schedule in the program, where the anti-interleukin-4 receptor alpha antibody includes the following: Complementarity-determining region 1 (CDR1) of the variable heavy chain of sequence ID: 1 (GFTFRDYA); Complementarity-determining region 2 of the variable heavy chain of sequence ID: 2 (ISGSGGNT); Complementarity-determining region 3 of the variable heavy chain of sequence ID: 3 (ISGSGGNT); Complementarity-determining region 1 of the variable light chain of sequence ID: 4 (QSLLYSIGYNY); The complementarity-determining region 2 of a variable light chain for the sequence numberDefinition: 5 (LGS); and the Complementarity-determining region 3 of the variable light chain of sequence ID: 6 (MQALQTPYT).
25. The method implemented by the computer according to security element 24, where the dose frequency is every 7 days, every 14 days, or every 28 days.
26. The method implemented by the computer according to security element 24, where the delayed dose notification recommends that the user wait until the next scheduled dose.
27. The method implemented by the computer according to security element 24, where the dose frequency is every 14 days and the minimum time is 7 days.
28. The method implemented by the computer according to security element 24, where the delayed dose notification recommends that the user take the next scheduled dose.
29. The method implemented by the computer according to security element 24, where the dose frequency is every 7 days and the minimum time is one day.
30. The method is based on protection element 24, where the anti-interleukin-4 receptor alpha antibody includes a heavy chain variable region (VH).The amino acid sequence includes ID: 13 and a light chain variable region (VL) includes the amino acid sequence includes ID:
14.
31. A computer-based method for treating a subject with an anti-interleukin-4 receptor alpha antibody, which includes providing guidance on administering a therapeutically effective amount of an anti-interleukin-4 receptor alpha antibody to the subject. The method includes the following: executing a program to manage the user's condition or treatment; monitoring the current medication dosing schedule assigned within the program and the medication dosing schedule that contains the frequency of doses; determining that the time period for taking a scheduled dose has been exceeded; in response to determining that the time period for taking the scheduled dose has been exceeded by more than the minimum time, a late dose notification is displayed to alert the user of the missed dose; In response to the detection of user interaction with the late dose notification, two options are provided to the user (1) to indicate that they have taken the scheduled dose or(2) To indicate that he did not take the scheduled dose; and when it is detected that the user indicates that he took the scheduled dose after the minimum time, a dosing reset information screen is displayed informing the user that the medication dosing schedule will be reset, as the anti-interleukin-4 receptor alpha antibody includes the following: Complementarity-determining region 1 of the variable heavy chain of sequence ID: 1 (GFTFRDYA); Complementarity-determining region 2 of the variable heavy chain of sequence ID: 2 (ISGSGGNT); Complementarity-determining region 3 of the variable heavy chain of sequence ID: 3 (ISGSGGNT); Complementarity-determining region 1 of the variable light chain of sequence ID: 4 (QSLLYSIGYNY); Complementarity-determining region 2 of the variable light chain32. The method implemented by the computer according to security element 31, where the delayed dose notification recommends that the user take the next scheduled dose.
33. The method implemented by the computer according to security element 32, where the dose frequency is every 28 days and the minimum time is 7 days.
34. The method implemented by the computer according to security element 24 or security element 31, where administration is via a pre-filled syringe.
35. The method implemented by the computer according to security element 24 or security element 31, where administration is via a pre-filled pen.
36. The method implemented by the computer according to security element 24 or security element 31, where administration is via an auto-injector.
37. The method implemented by the computer, according to security element 24 or security element 31, involves administering the anti-interleukin-4 receptor alpha antibody to the subject as an initial dose, followed by...One or more secondary doses.
38. The method implemented by the computer according to protection element 37, where the initial dose is approximately 600 mg and each secondary dose is approximately 300 mg.
39. The method implemented by the computer according to protection element 37, where the initial dose is approximately 400 mg and each secondary dose is approximately 200 mg.
40. The method implemented by the computer according to protection element 37, where each secondary dose is administered every two weeks.
41. The method implemented by the computer according to protection element 31, where the anti-interleukin-4 receptor alpha antibody includes a heavy chain variable region containing amino acid sequence ID: 13 and a light chain variable region containing amino acid sequence ID:
14.
42. The method implemented by the computer, according to security element 24 or security element 31, is such that, in response to a delayed dose notification, the user is given a therapeutically effective amount of the anti-interleukin-4 alpha receptor antibody.receptor alpha itself.
