A kind of children's asthma inhaled glucocorticoid administration management system for guardian collaborative intervention

Abstract

The application discloses a kind of children's asthma inhaled glucocorticoid administration management systems for guardian collaborative intervention, it is characterized in that, including: child patient basic information module, for gathering and storing the identity information of child patient, age, asthma control classification and guardian information;Medication regimen configuration module is connected with the child patient basic information module, for setting the dosing frequency of inhaled glucocorticoid, dosing time, dosage and treatment cycle according to medical order or medication plan, and generates medication plan data;Guardian binding module is connected with the child patient basic information module, for establishing the binding relationship of child patient and one or more guardian accounts, and the collaborative authority of each guardian is configured;Reminding scheduling module is connected with the medication regimen configuration module, for sending medication reminding to child patient terminal and at least one guardian terminal simultaneously according to the medication plan data at preset dosing time point;Medication record acquisition module is connected with the reminding scheduling module.

Description

Technical Field

[0001] This invention relates to the field of medical information management technology, and in particular to a management system for the administration of inhaled corticosteroids for childhood asthma, designed for collaborative intervention by guardians. Background Technology

[0002] Childhood asthma is one of the most common chronic respiratory diseases in childhood. In the long-term management of childhood asthma, inhaled corticosteroids (ICS) are the basic medication for controlling airway inflammation and preventing acute asthma attacks. They usually need to be inhaled regularly every day for several months or even years.

[0003] However, due to their young age, limited self-management abilities, and insufficient understanding of the disease, pediatric patients are often unable to independently administer and record medications. The actual medication process heavily relies on the participation, reminders, supervision, and confirmation of their guardians. In the out-of-hospital, home setting, the collaboration between guardians and children directly impacts medication adherence and long-term control outcomes.

[0004] Existing medication management solutions have the following main shortcomings: First, the reminder methods are limited. Existing technologies mostly use timed reminders or one-way push notifications, sending reminder information only to the child's terminal and failing to send collaborative reminders to the guardian's terminal simultaneously. This results in guardians not being able to know the medication time in a timely manner, and the level of collaborative participation is low.

[0005] Second, medication records are incomplete. Current technology relies on manual recording by the child or guardian, lacking a two-way verification mechanism. When the child makes a mistake or the guardian is not involved, the authenticity and completeness of the medication records are difficult to guarantee.

[0006] Third, abnormal medication use is detected late. Current technology lacks the ability to identify abnormal medication use behaviors such as missed doses, delayed doses, and continuous interruptions in real time. These behaviors are often only discovered in retrospect, missing the window for timely intervention.

[0007] Fourth, adherence assessment is crude. Existing technologies mostly use simple statistics on the number of medications taken or calculations of medication rates, failing to comprehensively consider multiple dimensions such as guardian confirmation behavior, timeliness of medication, and continuity, resulting in inaccurate adherence assessment results.

[0008] Fifth, follow-up management is fragmented. In existing technologies, outpatient medication management and inpatient follow-up management are independent of each other, lacking an automatic follow-up task generation mechanism based on medication adherence and risk warning, resulting in poor continuity and weak targeting of follow-up.

[0009] Therefore, there is a need for a management system for inhaled corticosteroids in children with asthma that is designed for collaborative intervention by guardians, in order to improve the efficiency of guardians' collaborative participation, the completeness of medication records, the timeliness of abnormal medication detection, the accuracy of compliance assessment, and the continuity of follow-up management. Summary of the Invention

[0010] The present invention provides a management system for inhaled corticosteroids in children with asthma, designed for collaborative intervention by guardians. This system addresses the problems of insufficient guardian collaboration, incomplete medication records, delayed detection of abnormal medication use, poor compliance assessment, and fragmented follow-up management in existing technologies. It improves the efficiency, record completeness, timeliness of reminders, continuity of follow-up, and accuracy of compliance assessment in the management of inhaled corticosteroids in children with asthma.

[0011] To achieve the above objectives, the present invention provides the following technical solution: A management system for inhaled corticosteroids in children with asthma, designed for collaborative intervention by guardians, includes: The basic information module for children with asthma is used to collect and store the child's identity information, age, asthma control level, and guardian information. The medication regimen configuration module is connected to the child's basic information module. It is used to set the frequency, timing, dosage, and course of treatment of inhaled corticosteroids according to medical orders or medication plans, and to generate medication plan data. The guardian binding module is connected to the child's basic information module and is used to establish a binding relationship between the child and one or more guardian accounts, and to configure the collaborative permissions of each guardian; The reminder scheduling module, connected to the medication plan configuration module, is used to synchronously send medication reminders to the child's terminal and at least one guardian's terminal at preset medication time points based on the medication plan data. The medication record collection module, connected to the reminder scheduling module, is used to receive medication execution records uploaded by the child's terminal. The medication execution records include a medication timestamp and a medication dose identifier. The guardian confirmation module, connected to the medication record collection module and the guardian binding module, is used to receive confirmation information, supplementary information or error correction information from the guardian's terminal regarding the medication execution record, and to update the medication execution record; An abnormal medication identification module, connected to the medication record acquisition module, the guardian confirmation module, and the medication plan configuration module, is used to compare the medication plan data with the medication execution record to identify missed medication events, delayed medication events, and continuous interruption events. The adherence assessment module, connected to the abnormal medication identification module, is used to calculate an adherence score or adherence level based on the planned number of medications, the actual number of recorded medications, the number of missed medications, the number of late medications, the number of consecutive days of interruption, and the timeliness of guardian confirmation. The risk warning module, connected to the compliance assessment module and the abnormal medication identification module, is used to generate graded warning information and send it to the guardian's terminal and the medical staff's terminal based on the continuous interruption events, the compliance score, and the preset risk threshold. An intervention strategy generation module, connected to the risk warning module, is used to generate intervention suggestions for guardians based on the graded warning information. The intervention suggestions include reminder reinforcement and instructions for guardians to perform tasks or follow-up tasks. The follow-up management module, connected to the intervention strategy generation module, is used to generate follow-up tasks according to the follow-up task triggering instruction and push follow-up reminders to the guardian terminal and the medical staff terminal.

[0012] Preferably, the reminder scheduling module is specifically used to: send a first-level reminder to the child's terminal 1 minute before the preset drug administration time point; simultaneously send a second-level reminder to the child's terminal and all bound guardian terminals at the preset drug administration time point; and send a delay warning reminder to the guardian terminal when the drug administration record is not received after the preset drug administration time point T2 minutes have passed.

[0013] Preferably, the medication execution record received by the medication record acquisition module is generated in at least one of the following ways: the child or guardian manually confirms the completion of medication on the child's terminal; the child's terminal automatically records the medication by scanning the identification code on the inhalation device with a camera; or the child's terminal receives a medication completion signal sent by an external smart inhalation device.

[0014] Preferably, the guardian confirmation module is specifically used for: receiving confirmation operations uploaded by the guardian's terminal, the confirmation operations including an acknowledgment identifier for the medication execution record and a guardian identity identifier; receiving supplementary or corrective data uploaded by the guardian's terminal when the medication execution record has time deviations, dosage abnormalities, or omissions; comparing the timestamp of the confirmation operation with the timestamp of the medication execution record, calculating the guardian confirmation delay, and incorporating the guardian confirmation delay into the evaluation indicators of the compliance assessment module.

[0015] Preferably, the rules for the abnormal medication identification module to identify the missed medication event, the late medication event, and the continuous interruption event are as follows: if no corresponding medication execution record is received within T3 hours after a planned medication time point, it is determined to be a missed medication event; if the timestamp of the medication execution record deviates from the planned medication time by more than T4 minutes but not more than T3 hours, it is determined to be a late medication event; if missed medication events occur at N consecutive planned medication time points, it is determined to be a continuous interruption event, where N is a preset threshold.

[0016] Preferably, the compliance assessment module calculates the compliance score using the following formula: Compliance Score = W1 × (Actual Recording Times / Planned Medication Times) - W2 × (Number of Late Uses / Planned Medication Times) - W3 × (Number of Missed Uses / Planned Medication Times) + W4 × Timely Confirmation Rate by Guardian - W5 × Consecutive Interruption Penalty Item, where W1, W2, W3, W4, and W5 are preset weighting coefficients, and the consecutive interruption penalty item is positively correlated with the number of consecutive interruption days; based on the compliance score, the compliance level is divided into four levels: excellent, good, moderate, and unsatisfactory.

[0017] Preferably, the risk warning module generates the graded warning information according to the following rules: when a single missed use event occurs and the compliance score is above the first threshold, a low-level warning is generated; when the cumulative number of late use events reaches the second threshold or the compliance score is below the first threshold, a medium-level warning is generated; when the continuous interruption event occurs or the compliance score is below the third threshold, a high-level warning is generated and marked as requiring medical intervention.

[0018] Preferably, the logic of the intervention strategy generation module in generating the intervention suggestion based on the graded early warning information is as follows: when a low-level early warning is received, a reminder reinforcement instruction is generated for the guardian, increasing the reminder frequency of the reminder scheduling module; when a medium-level early warning is received, a task is generated for the guardian to perform, which includes mandatory confirmation, medication accompaniment, or medication environment inspection; when a high-level early warning is received, the follow-up task trigger instruction is triggered, and the child's information is marked as a key focus object.

[0019] This invention also provides a method for managing inhaled corticosteroids in children with asthma through collaborative intervention by guardians, comprising the following steps: S1: Collect the child's identity information, age, asthma control level, and guardian information, and establish a binding relationship between the child and one or more guardian accounts; S2: Based on the doctor's orders or medication plan, set the frequency, timing, dosage, and duration of inhaled corticosteroid administration, and generate medication plan data; S3: Simultaneously send medication reminders to the child's terminal and at least one guardian's terminal at preset medication time points; S4: Receive medication execution records uploaded by the child's terminal and confirmation information uploaded by the guardian's terminal. The medication execution records include a medication timestamp and a dosage identifier. S5: Compare the medication plan data with the medication execution record to identify missed medication events, late medication events, and continuous interruption events; S6: Calculate the compliance score or compliance level based on the planned number of medications, the actual number of recorded medications, the number of missed medications, the number of late medications, the number of consecutive days of interruption, and the timeliness of guardian confirmation; S7: Based on the continuous interruption events, the compliance score, and the preset risk threshold, generate graded early warning information and send it to the guardian's terminal and the medical staff's terminal; S8: Generate intervention suggestions for the guardian based on the tiered early warning information, and generate follow-up tasks to be pushed to the guardian's terminal and the medical staff terminal.

[0020] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described method.

[0021] The present invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.

[0022] The beneficial effects of this invention are as follows: 1. This invention achieves synchronous reminders between the child's terminal and the guardian's terminal through the cooperation of the guardian binding module and the reminder scheduling module, bringing the guardian into the medication reminder closed loop and improving the timeliness and initiative of the guardian's collaborative participation.

[0023] 2. This invention establishes a two-way confirmation mechanism by using a guardian confirmation module to perform secondary confirmation, supplementation, or correction of medication administration records, which significantly improves the authenticity and completeness of medication records.

[0024] 3. This invention uses an abnormal medication identification module to identify abnormal medication behaviors such as missed use, delayed use, and continuous interruption in real time. Combined with the risk warning module's tiered warning system, it enables timely detection and rapid response to abnormal medication use.

[0025] 4. This invention calculates a compliance score by comprehensively considering multiple dimensions of indicators, including the number of planned medication administrations, the number of actual recorded administrations, the number of missed administrations, the number of late administrations, the number of consecutive days of interruption, and the timeliness of guardian confirmation, thereby improving the accuracy and discriminative power of compliance evaluation.

[0026] 5. This invention, through the linkage of the intervention strategy generation module and the follow-up management module, automatically generates intervention suggestions and follow-up tasks for guardians based on risk warnings, realizing a closed-loop connection between outpatient medication management and inpatient follow-up management, and improving the continuity and pertinence of follow-up.

[0027] 6. This invention incorporates the collaborative behavior of guardians into the core indicators of compliance assessment and risk warning, highlighting the key role of guardians in the long-term management of childhood asthma and meeting the actual needs of childhood chronic disease management. Attached Figure Description

[0028] Figure 1 This is a structural block diagram of the system of the present invention; Figure 2 This is a schematic diagram of the data flow in the system of the present invention; Figure 3 This is a flowchart of the guardian collaborative intervention process of the present invention; Figure 4 This is a flowchart of the abnormal medication identification and early warning system of the present invention; Figure 5 This is a flowchart of the compliance assessment and follow-up management process of the present invention. Detailed Implementation

[0030] The present invention will now be described in further detail with reference to the accompanying drawings and specific embodiments. Example 1

[0031] like Figure 1 and Figure 2 As shown, this embodiment provides a management system for inhaled corticosteroids in children with asthma, designed for collaborative intervention by guardians. The system is deployed on a server and interacts with the child's terminal, guardian's terminal, and medical staff's terminal via a network. The child's terminal and guardian's terminal can be mobile devices such as smartphones or tablets, while the medical staff's terminal can be a hospital information system or a doctor's workstation.

[0032] This system includes the following modules: I. Basic Information Module for Patients The basic information module for children is used to collect and store the child's identity information, age, asthma control level, and guardian information. The identity information includes the child's name, gender, date of birth, and unique identifier. The asthma control level can be entered based on the doctor's diagnosis, such as well-controlled, partially controlled, or uncontrolled. The guardian information includes the guardian's name, relationship to the child, and contact information.

[0033] In this embodiment, the basic information module for patients receives patient information submitted by medical staff or guardians, verifies it, stores it in the database, and generates a unique patient identifier for each patient.

[0034] II. Medication Plan Configuration Module The medication regimen configuration module is connected to the child's basic information module. It is used to set the frequency, timing, dosage, and course of treatment of inhaled corticosteroids according to medical orders or medication plans, and to generate medication plan data.

[0035] In this embodiment, the healthcare provider sets a medication regimen for inhaled corticosteroids based on the child's asthma control level and treatment needs. For example, twice daily, at 8:00 AM and 8:00 PM, with each inhalation dose being 200 micrograms, and a treatment course lasting 3 months. The medication regimen configuration module receives the above settings and generates medication plan data, which includes the planned medication time sequence, the dose for each administration, and the start and end dates of the treatment course.

[0036] The medication plan configuration module also supports adjustments and updates to the medication plan. When healthcare professionals modify the medication plan, the medication plan configuration module automatically updates the medication plan data and pushes a plan change notification to both the child's and the guardian's terminals.

[0037] III. Guardian Binding Module The guardian binding module is connected to the child's basic information module to establish a binding relationship between the child and one or more guardian accounts, and to configure the collaborative permissions of each guardian.

[0038] In this embodiment, the guardian registers an account through the guardian's terminal and submits the child's unique identifier and relationship proof information. After verification by the guardian binding module, a binding relationship is established between the child's and the guardian's account. A child can be bound to multiple guardians, such as a father, mother, or grandparents.

[0039] The guardian binding module configures collaborative permissions for each guardian. These collaborative permissions include: receiving reminders, viewing records, confirming records, supplementing records, and receiving alerts. In this embodiment, parents are typically configured with all permissions, while grandparents can be configured with receiving reminders and viewing records.

[0040] IV. Reminder and Scheduling Module The reminder scheduling module is connected to the medication plan configuration module and is used to send medication reminders synchronously to the child's terminal and at least one guardian's terminal at preset medication time points based on the medication plan data.

[0041] like Figure 3 As shown, the workflow of the reminder scheduling module is as follows: 1. The reminder scheduling module reads the medication plan data and obtains all planned medication time points for the day.

[0042] 2. A first-level reminder is sent to the child's terminal 1 minute before the preset drug administration time. In this embodiment, T1 is set to 15 minutes, and the first-level reminder is a mild reminder, such as a notification bar message or vibration alert.

[0043] 3. At the preset medication administration time, a second-level reminder is simultaneously sent to the child's terminal and all bound guardian terminals with reminder receiving permissions. The second-level reminder is a stronger reminder, such as a pop-up notification or ringtone reminder, and the reminder content includes medication time, dosage, and method of administration.

[0044] 4. When the preset medication administration time T2 minutes have elapsed, the reminder scheduling module queries the medication record collection module to determine whether the corresponding medication execution record has been received. In this embodiment, T2 is set to 30 minutes. If no medication execution record has been received, the reminder scheduling module sends a delay warning reminder to the guardian's terminal with warning reception authority. The reminder content includes "The child has not completed this medication administration; please urge the child to complete it."

[0045] V. Medication Record Collection Module The medication record collection module is connected to the reminder scheduling module and is used to receive medication execution records uploaded by the child's terminal. The medication execution records include medication timestamps and medication dose identifiers.

[0046] In this embodiment, medication administration records can be generated in the following ways: Method 1: The child or guardian manually confirms the completion of medication on the child's terminal. After the child's terminal displays the medication reminder, it provides a "Completed" button. After the child or guardian clicks it, the child's terminal automatically records the current timestamp and generates a medication execution record, which is then uploaded to the medication record collection module.

[0047] Method 2: The child's terminal automatically records the medication administration information by scanning the identification code on the inhalation device using a camera. In this embodiment, the inhalation device has a QR code or barcode affixed to it. After the child or guardian scans the code using the child's terminal, the terminal identifies the inhalation device information, records the current timestamp, and generates and uploads a medication administration record.

[0048] Method 3: The child's terminal receives a medication completion signal from an external smart inhalation device. In this embodiment, if a smart inhalation device with Bluetooth or WiFi communication capabilities is used, the device automatically sends a medication completion signal to the child's terminal after the child finishes inhaling. Upon receiving the signal, the child's terminal generates and uploads a medication execution record.

[0049] After receiving the medication administration record, the medication record collection module stores it in the database and marks it as pending guardian confirmation.

[0050] VI. Guardian Confirmation Module The guardian confirmation module is connected to the medication record collection module and the guardian binding module. It is used to receive confirmation information, supplementary information or error correction information of the medication execution record from the guardian's terminal, and update the medication execution record.

[0051] like Figure 3 As shown, the workflow of the guardian confirmation module is as follows: 1. After receiving the push notification of the medication administration record on the guardian's terminal, the guardian can view the detailed information of the medication administration record, including the medication timestamp and the medication dose identifier.

[0052] 2. The guardian performs a confirmation operation on the guardian's terminal. The confirmation operation includes an acknowledgment mark for the medication administration record (e.g., clicking the "Confirm" button) and a guardian identity mark (e.g., guardian account identifier). The guardian's terminal uploads the timestamp of the confirmation operation and the guardian identity mark to the guardian confirmation module.

[0053] 3. After receiving the confirmation operation, the guardian confirmation module updates the status of the medication execution record to "confirmed" and records the guardian confirmation timestamp.

[0054] 4. When a guardian discovers discrepancies in the medication administration record, such as time discrepancies, dosage abnormalities, or omissions, the guardian can submit supplementary or corrective data on their terminal. For example, if the child completed their medication at 8:10 but it wasn't recorded in time, the guardian can record the medication time as 8:10 on their terminal. After receiving the supplementary or corrective data, the guardian confirmation module updates the medication administration record and marks it as supplementary data or correction by the guardian.

[0055] 5. The guardian confirmation module compares the timestamp of the guardian's confirmation action with the timestamp of the medication administration record to calculate the guardian confirmation lag. For example, if the medication administration record timestamp is 8:05 and the guardian confirmation timestamp is 8:20, then the guardian confirmation lag is 15 minutes. The guardian confirmation lag is transmitted as an assessment indicator to the compliance assessment module.

[0056] VII. Abnormal Medication Use Identification Module The abnormal medication identification module is connected to the medication record collection module, the guardian confirmation module, and the medication plan configuration module. It is used to compare medication plan data with medication execution records to identify missed medication events, late medication events, and continuous interruption events.

[0057] like Figure 4 As shown, the identification rules of the abnormal medication identification module are as follows: 1. Missed Dosage Event Identification: The abnormal medication identification module periodically queries medication plan data and medication execution records. If no corresponding medication execution record is received within T3 hours after a planned medication time, it is determined to be a missed dosage event. In this embodiment, T3 is set to 6 hours. For example, if the planned medication time is 8:00, and no corresponding medication execution record is received before 14:00, it is determined to be a missed dosage event, and the missed dosage time and missed dose are recorded.

[0058] 2. Late Dosing Event Identification: When the deviation between the timestamp of the medication execution record and the planned medication time exceeds T4 minutes but does not exceed T3 hours, it is determined as a late dosing event. In this embodiment, T4 is set to 60 minutes. For example, if the planned medication time is 8:00 and the timestamp of the medication execution record is 9:10, the deviation is 70 minutes, exceeding 60 minutes but not exceeding 6 hours, which is determined as a late dosing event, and the duration of the late dosing and the number of doses administered are recorded.

[0059] 3. Continuous Interruption Event Identification: A continuous interruption event is defined as when a medication is missed at N consecutive planned medication time points. In this embodiment, N is set to 4. For example, if a child misses both morning and evening doses for two consecutive days, i.e., misses medication at four consecutive planned medication time points, it is defined as a continuous interruption event, and the start time and number of consecutive interruption days are recorded.

[0060] The abnormal medication identification module transmits the identification results to the adherence assessment module and the risk warning module.

[0061] VIII. Compliance Assessment Module The compliance assessment module is connected to the abnormal medication identification module and is used to calculate the compliance score or compliance level based on the planned number of medications, the actual number of recorded medications, the number of missed medications, the number of late medications, the number of consecutive days of interruption, and the timeliness of guardian confirmation.

[0062] In this embodiment, the compliance assessment module calculates the compliance score using the following formula: Compliance score = W1 × (Number of actual doses / Number of planned doses) - W2 × (Number of late doses / Number of planned doses) - W3 × (Number of missed doses / Number of planned doses) + W4 × Timely confirmation rate by guardian - W5 × Penalty for continuous interruption in: - W1, W2, W3, W4, and W5 are preset weighting coefficients, which are set to 0.5, 0.15, 0.25, 0.1, and 0.2 respectively in this embodiment; - The actual number of records is the number of valid medication execution records received by the medication record collection module; - The planned number of medication administrations refers to the number of planned medication administrations within the assessment period as shown in the medication administration plan data; - Guardian confirmation timeliness rate = (Number of records where the guardian completes confirmation within 30 minutes) / (Actual number of records); - The continuous interruption penalty is positively correlated with the number of consecutive interruption days. The calculation formula is: continuous interruption penalty = number of consecutive interruption days × 0.05, with an upper limit of 0.5.

[0063] For example, a child is scheduled to take medication 60 times a month (twice daily for 30 days), but actually takes it 52 times, with 6 doses delayed and 8 doses missed. The guardian confirms the medication 45 times within 30 minutes. There is one instance of continuous interruption (two consecutive days, i.e., four time points). Then: Actual number of recorded doses / planned number of doses = 52 / 60 ≈ 0.867 Number of delayed doses / Planned number of doses = 6 / 60 = 0.1 Missed doses / planned doses = 8 / 60 ≈ 0.133 Timely confirmation rate by guardians = 45 / 52 ≈ 0.865 Continuous interruption penalty = 2 × 0.05 = 0.1 Compliance score = 0.5 × 0.867 - 0.15 × 0.1 - 0.25 × 0.133 + 0.1 × 0.865 - 0.2 × 0.1 = 0.4335 - 0.015 - 0.03325 + 0.0865 - 0.02 ≈ 0.45 The compliance assessment module categorizes compliance levels into four levels based on compliance scores: - Excellent: Compliance score ≥ 0.8 - Good: 0.6 ≤ Compliance score < 0.8 - Moderate: 0.4 ≤ Compliance score < 0.6 - Not meeting the standard: Compliance score < 0.4 In the example above, the compliance score is 0.45, and the compliance level is moderate.

[0064] The adherence assessment module transmits adherence scores and adherence levels to the risk warning module, and can generate adherence analysis reports based on requests from healthcare professionals or guardians. The reports include adherence trend charts, details of abnormal medication use, and analysis of guardian participation.

[0065] IX. Risk Warning Module The risk warning module is connected to the compliance assessment module and the abnormal medication identification module. It is used to generate graded warning information based on continuous interruption events, compliance scores and preset risk thresholds and send it to the guardian's terminal and the medical staff's terminal.

[0066] like Figure 4 As shown, the rules for generating tiered early warning information by the risk warning module are as follows: 1. Low-level warning: A low-level warning is generated when a single missed medication event occurs and the compliance score is above the first threshold. In this embodiment, the first threshold is set to 0.6. The low-level warning message includes "One missed medication event detected, please remember to take your medication on time," and is sent to the guardian's terminal.

[0067] 2. Intermediate Warning: An intermediate warning is generated when the cumulative number of late usage events reaches the second threshold or the compliance score falls below the first threshold. In this embodiment, the second threshold is set to 5 times. The intermediate warning message includes "Recent late usage or omissions have increased, compliance has declined, and it is recommended to strengthen supervision," and is sent to the guardian's terminal and the medical staff's terminal.

[0068] 3. Advanced Warning: When consecutive medication interruptions occur or the adherence score falls below the third threshold, an advanced warning is generated and the patient is marked as requiring intervention from healthcare professionals. In this embodiment, the third threshold is set to 0.4. The advanced warning message includes "Consecutive medication interruptions or non-compliance have been detected; it is recommended to contact a doctor as soon as possible," and is sent to both the guardian's terminal and the healthcare professional's terminal, where the patient is marked as a high-priority individual.

[0069] The risk warning module transmits tiered warning information to the intervention strategy generation module.

[0070] 10. Intervention Strategy Generation Module The intervention strategy generation module is connected to the risk warning module and is used to generate intervention suggestions for guardians based on the graded warning information. The intervention suggestions include reminder reinforcement and instructions for guardians to perform tasks or follow-up tasks.

[0071] like Figure 5 As shown, the logic of the intervention strategy generation module in generating intervention recommendations based on tiered early warning information is as follows: 1. Upon receiving a low-level warning, a reinforcement instruction for the guardian is generated. The intervention strategy generation module sends an instruction to the reminder scheduling module to increase the reminder frequency, for example, sending reminders 30 minutes, 15 minutes, and 0 minutes before the preset medication time, and sending a delayed warning reminder every 15 minutes after the timeout until the medication execution record is received.

[0072] 2. Upon receiving a medium-level warning, a guardian task is generated. The guardian task includes mandatory confirmation, medication accompaniment, or medication environment inspection. In this embodiment, the intervention strategy generation module pushes the task to the guardian's terminal, requiring the guardian to perform one of the following operations at the next medication administration: mandatory confirmation (the guardian must personally confirm medication completion), medication accompaniment (the guardian supervises the child's medication administration on-site), or medication environment inspection (checking if the inhaler is usable and if the child has any medication difficulties). After completing the task, the guardian must submit task completion feedback on the guardian's terminal.

[0073] 3. Upon receiving a high-level alert, a follow-up task trigger instruction is activated, and the child's information is marked as a priority case. The intervention strategy generation module sends the follow-up task trigger instruction to the follow-up management module and marks the child's information as a red alert on the medical staff's end, prompting medical staff to prioritize the case.

[0074] XI. Follow-up Management Module The follow-up management module is connected to the intervention strategy generation module. It is used to generate follow-up tasks based on follow-up task trigger instructions and push follow-up reminders to the guardian's terminal and the medical staff's terminal.

[0075] like Figure 5 As shown, the workflow of the follow-up management module is as follows: 1. After receiving the follow-up task trigger instruction sent by the intervention strategy generation module, the follow-up management module automatically generates a follow-up task, which includes a follow-up time suggestion, a follow-up content suggestion, and a medication adherence report for the child.

[0076] 2. Follow-up time is recommended to be automatically calculated based on the current date and the child's medication cycle. For example, it is recommended to conduct a follow-up within 3 working days after an advanced warning is triggered.

[0077] 3. Follow-up recommendations include: understanding the reasons for recent decline in medication adherence, assessing asthma control status, checking inhalation technique, adjusting medication regimen (if necessary), and strengthening health education for guardians.

[0078] 4. The follow-up management module pushes follow-up reminders to the guardian's terminal. The reminder content includes "Your child's medication adherence has been poor recently. It is recommended to make an appointment for a follow-up as soon as possible," and provides an online appointment portal or medical staff contact information.

[0079] 5. The follow-up management module pushes follow-up tasks to the medical staff. After receiving the task, the medical staff arranges the follow-up time and enters the follow-up record after the follow-up is completed. The follow-up record includes the follow-up date, the child's condition, medication regimen adjustments, health education content, etc.

[0080] 6. The follow-up management module supports tracking the status of follow-up tasks, including statuses such as pending appointment, scheduled appointment, completed, and canceled, and provides a follow-up task management interface on the medical staff's end.

[0081] 12. Data Display Module (Optional) In this embodiment, the system may further include a data display module, used to provide visualized data displays to the guardian's terminal, the child's terminal, and the medical staff's terminal. The data display module can display the following content: 1. Medication Calendar: Displays daily medication completion status in calendar format, with green indicating timely completion, yellow indicating late completion, and red indicating missed completion.

[0082] 2. Compliance Trend Chart: Displays the recent trend of compliance scores using a line chart or bar chart.

[0083] 3. Guardian Collaboration Analysis: Displays the number of times each guardian confirms, the timeliness of confirmation, and the ranking of participation.

[0084] 4. Abnormal Medication Use Statistics: Displays the time distribution and frequency statistics of missed medications, late medications, and continuous interruption events.

[0085] 5. Early Warning Records: Displays historical early warning information and the implementation status of intervention measures. Example 2

[0086] like Figure 3 As shown, this embodiment provides a specific application scenario for collaborative intervention by guardians: Xiaoming, a 6-year-old child, was diagnosed with partially controlled asthma. The doctor prescribed an inhaled corticosteroid regimen for him: inhaling once at 8:00 am and once at 8:00 pm daily, at a dose of 200 micrograms per inhalation, for a course of 3 months.

[0087] 1. The child's mother and father each registered an account on the guardian's terminal and linked it to Xiaoming's patient account. The mother was configured with full collaboration permissions, while the father was configured with permissions to receive reminders and view records.

[0088] 2. At 7:45 a.m. one morning, the reminder scheduling module sent a first-level reminder to Xiaoming's patient terminal (a children's smartwatch), prompting "Medication needs to be inhaled in 15 minutes".

[0089] 3. At 8:00 AM, the reminder scheduling module simultaneously sends a second-level reminder to Xiaoming's patient terminal, mother terminal, and father terminal, prompting "It is medication time now, please use the inhalation device."

[0090] 4. The mother urged Xiaoming to complete the inhalation and clicked the "Completed" button on the child's terminal. The child's terminal recorded a timestamp of 8:05 and uploaded the medication execution record to the medication record collection module.

[0091] 5. The mother receives a push notification of the medication execution record on her terminal. After viewing it, she clicks the "Confirm" button. The guardian confirmation module records the mother's confirmation timestamp as 8:08, and calculates the guardian confirmation delay as 3 minutes.

[0092] 6. At 8:00 PM, the reminder scheduling module sent another reminder, but Xiaoming was out and about and could not inhale it in time.

[0093] 7. At 8:30 PM, the scheduling module checks and finds that no medication execution record has been received. It then sends a delay warning to the mother's and father's terminals: "Xiaoming has not yet completed his evening medication. Please urge him to complete it."

[0094] 8. After seeing the delay warning, the mother called Xiaoming and urged him to take his medication immediately upon returning home. Xiaoming completed the inhalation at 21:20, and the mother recorded the medication time as 21:20 on the child's terminal.

[0095] 9. The abnormal medication identification module identifies this medication as a delayed event (deviation of 80 minutes) and records the duration and number of delayed doses.

[0096] 10. After one month of medication management, the adherence assessment module calculated Xiaoming's adherence score to be 0.72, indicating a good adherence level. There were 2 missed doses and 8 late doses during the period, but no consecutive interruptions occurred, and the guardian's timely confirmation rate was 0.88%.

[0097] 11. The risk warning module generates an intermediate warning based on the number of late uses (8 times) exceeding the second threshold (5 times), and sends it to the mother's terminal and the medical care terminal.

[0098] 12. The intervention strategy generation module generates a guardian task, requiring the mother to perform the medication accompaniment task at least 3 times in the next week to ensure that Xiaoming takes his medication on time.

[0099] 13. After receiving the task on the guardian terminal, the mother supervised Xiaoming's medication administration on-site during the subsequent medication times and submitted task completion feedback.

[0100] 14. One week later, Xiaoming's compliance score improved to 0.85, and his compliance level was excellent. The number of times he was late or missed using the product decreased significantly. Example 3

[0101] This embodiment provides a method for managing inhaled corticosteroids in children with asthma with the assistance of guardians, including the following steps: S1: Collect the child's identity information, age, asthma control level, and guardian information, and establish a binding relationship between the child and one or more guardian accounts.

[0102] S2: Based on the doctor's order or medication plan, set the frequency, time, dosage and course of treatment of inhaled corticosteroids, and generate medication plan data.

[0103] S3: At preset medication administration times, medication reminders are simultaneously sent to the child's terminal and at least one guardian's terminal. The medication reminders employ a tiered reminder mechanism, including pre-reminders, simultaneous reminders, and delayed early warning reminders.

[0104] S4: Receive medication execution records uploaded by the child's terminal and confirmation information uploaded by the guardian's terminal. The medication execution records include medication timestamps and medication dose identifiers.

[0105] S5: Compare the medication plan data with the medication execution records to identify missed medication events, late medication events, and continuous interruption events. A missed medication event is defined as no medication execution record is received within T3 hours after the planned medication time point; a late medication event is defined as a deviation between the medication execution record and the planned time exceeding T4 minutes but not exceeding T3 hours; a continuous interruption event is defined as missed medication occurring at N consecutive planned medication time points.

[0106] S6: Calculate the adherence score or adherence level based on the planned number of medication administrations, the actual number of recorded administrations, the number of missed administrations, the number of late administrations, the number of consecutive days of interruption, and the guardian's timely confirmation rate. The adherence score comprehensively considers the medication completion rate, medication timeliness, guardian's cooperative participation, and continuous penalties, and adopts a weighted calculation method.

[0107] S7: Based on the continuous interruption events, the compliance score, and the preset risk threshold, generate tiered early warning information and send it to the guardian's terminal and the medical staff's terminal. The tiered early warning information includes low-level, medium-level, and high-level early warnings, dynamically determined according to the severity of abnormal medication use and the level of compliance.

[0108] S8: Based on the tiered early warning information, intervention suggestions are generated for the guardian, and follow-up tasks are generated and pushed to the guardian's terminal and the medical staff's terminal. The intervention suggestions are divided into reminder reinforcement, guardian task execution, and follow-up task triggering according to the early warning level, forming a tiered response mechanism from automated reminders to manual intervention.

Claims

1. A management system for inhaled corticosteroids in children with asthma, designed for collaborative intervention by guardians, characterized in that... ,include: The basic information module for children with asthma is used to collect and store the child's identity information, age, asthma control level, and guardian information. The medication regimen configuration module is connected to the child's basic information module. It is used to set the frequency, timing, dosage, and course of treatment of inhaled corticosteroids according to medical orders or medication plans, and to generate medication plan data. The guardian binding module is connected to the child's basic information module and is used to establish a binding relationship between the child and one or more guardian accounts, and to configure the collaborative permissions of each guardian; The reminder scheduling module, connected to the medication plan configuration module, is used to synchronously send medication reminders to the child's terminal and at least one guardian's terminal at preset medication time points based on the medication plan data. The medication record collection module, connected to the reminder scheduling module, is used to receive medication execution records uploaded by the child's terminal. The medication execution records include a medication timestamp and a medication dose identifier. The guardian confirmation module, connected to the medication record collection module and the guardian binding module, is used to receive confirmation information, supplementary information or error correction information from the guardian's terminal regarding the medication execution record, and to update the medication execution record; An abnormal medication identification module, connected to the medication record acquisition module, the guardian confirmation module, and the medication plan configuration module, is used to compare the medication plan data with the medication execution record to identify missed medication events, delayed medication events, and continuous interruption events. The adherence assessment module, connected to the abnormal medication identification module, is used to calculate an adherence score or adherence level based on the planned number of medications, the actual number of recorded medications, the number of missed medications, the number of late medications, the number of consecutive days of interruption, and the timeliness of guardian confirmation. The risk warning module, connected to the compliance assessment module and the abnormal medication identification module, is used to generate graded warning information and send it to the guardian's terminal and the medical staff's terminal based on the continuous interruption events, the compliance score, and the preset risk threshold. An intervention strategy generation module, connected to the risk warning module, is used to generate intervention suggestions for guardians based on the graded warning information. The intervention suggestions include reminder reinforcement and instructions for guardians to perform tasks or follow-up tasks. The follow-up management module, connected to the intervention strategy generation module, is used to generate follow-up tasks according to the follow-up task triggering instruction and push follow-up reminders to the guardian terminal and the medical staff terminal.

2. The inhaled corticosteroid medication management system for childhood asthma with guardian-led collaborative intervention as described in claim 1, characterized in that... The reminder scheduling module is specifically used for: A first-level reminder is sent to the child's terminal one minute before the preset drug administration time. At the preset medication administration time, a second-level reminder is simultaneously sent to the child's terminal and all bound guardian terminals; If the medication administration record is not received after 2 minutes from the preset dosing time point T, a delay warning reminder is sent to the guardian's terminal.

3. The inhaled corticosteroid medication management system for childhood asthma with guardian-led collaborative intervention as described in claim 1, characterized in that... The medication execution record received by the medication record acquisition module is generated in at least one of the following ways: The patient or their guardian must manually confirm the medication administration is complete on the patient's device. The patient's terminal automatically records the information by scanning the identification code on the inhalation device using a camera; The patient's terminal receives a medication completion signal from an external smart inhalation device.

4. The inhaled corticosteroid medication management system for childhood asthma, oriented towards collaborative intervention by guardians, as described in claim 1, is characterized in that... The guardian confirmation module is specifically used for: The system receives a confirmation message uploaded from the guardian's terminal. The confirmation message includes an acknowledgment identifier for the medication administration record and a guardian identification identifier. When there are time deviations, dosage abnormalities, or missing data in the medication administration record, the system receives supplementary or corrective data uploaded by the guardian's terminal. The timestamp of the confirmation operation is compared with the timestamp of the medication execution record to calculate the guardian confirmation delay, and the guardian confirmation delay is included in the evaluation indicators of the compliance assessment module.

5. A childhood asthma inhaled corticosteroid medication management system for collaborative intervention by guardians, as described in claim 1, is characterized in that... The rules for the abnormal medication identification module to identify the missed medication event, the late medication event, and the continuous interruption event are as follows: If no corresponding medication execution record is received within T3 hours after a planned medication time, it is considered a missed medication event. If the timestamp of the medication administration record deviates from the planned medication time by more than T4 minutes but less than T3 hours, it is considered a late medication event. When a missed medication event occurs at N consecutive planned medication time points, it is determined to be a continuous interruption event, where N is a preset threshold.

6. The inhaled corticosteroid medication management system for childhood asthma with guardian-led collaborative intervention as described in claim 1, characterized in that... The formula for calculating the compliance score by the compliance assessment module is as follows: Compliance score = W1 × (Number of actual doses / Number of planned doses) - W2 × (Number of late doses / Number of planned doses) - W3 × (Number of missed doses / Number of planned doses) + W4 × Timely confirmation rate by guardian - W5 × Consecutive interruption penalty item. Wherein, W1, W2, W3, W4, and W5 are preset weighting coefficients, and the continuous interruption penalty term is positively correlated with the number of consecutive interruption days; Based on the compliance score, compliance levels are divided into four categories: excellent, good, average, and unsatisfactory.

7. A childhood asthma inhaled corticosteroid medication management system for collaborative intervention by guardians, as described in claim 1, is characterized in that... The rule for the risk warning module to generate the tiered warning information is as follows: When a single missed use event occurs and the compliance score is above the first threshold, a low-level warning is generated; When the cumulative number of late use events reaches the second threshold or the compliance score falls below the first threshold, a medium-level warning is generated. When the continuous interruption event occurs or the compliance score falls below the third threshold, an advanced warning is generated and marked as requiring intervention from medical staff.

8. A childhood asthma inhaled corticosteroid medication management system for collaborative intervention by guardians, as described in claim 1, is characterized in that... The logic of the intervention strategy generation module in generating the intervention recommendations based on the tiered early warning information is as follows: When a low-level warning is received, a reminder reinforcement instruction is generated for the guardian, increasing the reminder frequency of the reminder scheduling module; When a medium-level warning is received, a guardian is assigned a task, which includes mandatory confirmation, medication accompaniment, or medication environment inspection. When a high-level alert is received, the follow-up task trigger instruction is activated, and the child's information is marked as a key focus.

Images