Medication management method and device

Abstract

The invention discloses a medication management method and device, and relates to the technical field of intelligent medical treatment. A specific embodiment of the method comprises the following steps: in response to a monitored patient medicine taking event, acquiring prescription information and medical record information of a patient from a hospital information system; generating a medication plan list according to the prescription information and the medical record information; generating medication reminding information according to the prescription information, the medical record information and the medication plan list; and carrying out medication reminding according to the medication reminding information so as to carry out medication management. According to the embodiment, the corresponding medication plan and medication reminding information can be automatically generated when the patient takes the medicine, the trouble that the patient manually adds medication reminding is solved, and the medication reminding and management mode is more intelligent and flexible.

Description

Technical Field

[0001] The present invention relates to the field of smart medical technology, and in particular to a method and device for medication management. Background Art

[0002] Existing medication reminder or management software typically requires users to manually add reminders based on their doctor's prescriptions and drug inserts, as well as manually set dosage and schedule. This approach to medication management, which requires users to manually add reminders, is inflexible, inefficient, and complex. Summary of the Invention

[0003] In view of this, an embodiment of the present invention provides a method and device for medication management, which can automatically generate corresponding medication plans and medication reminder information when patients pick up medicines, solving the problem of patients having to manually add medication reminders. The medication reminder and management method is more intelligent and flexible, and the operation is simple.

[0004] To achieve the above object, according to one aspect of an embodiment of the present invention, a method for medication management is provided, comprising: In response to monitoring the patient's medication collection event, obtain the patient's prescription information and medical record information from the hospital information system; generating a medication plan list based on the prescription information and the medical record information; generating medication reminder information based on the prescription information, the medical record information, and the medication plan list; Medication reminders are provided based on the medication reminder information to manage medication.

[0005] Optionally, the prescription information includes the name of the drug, the frequency and time of use of each drug, and medical order information; a medication plan list is generated based on the prescription information and the medical record information, including: creating a medication plan corresponding to each drug based on the drug name in the prescription information; determining the medication cycle and medication date corresponding to each medication plan based on the frequency and time of use of each drug in the prescription information; generating a medication plan description text through a large model based on the medical order information in the prescription information, the medical record information and detailed drug information of each drug, the drug detailed information is generated based on the drug instructions; generating a medication plan list based on the medication plans corresponding to each drug, the medication cycle and medication date corresponding to each medication plan, and the medication plan description text.

[0006] Optionally, medication reminder information is generated based on the prescription information, the medical record information and the medication plan list, including: generating prompt words based on the prescription information, the medical record information and the medication plan list, and generating medication reminder information corresponding to the medication plan list through a large model based on the prompt words.

[0007] Optionally, medication reminder information is generated based on the prescription information, the medical record information and the medication plan list, including: determining whether the patient already has medication reminder information; in response to the patient not having medication reminder information, generating a prompt word based on the prescription information, the medical record information and the medication plan list, and generating medication reminder information corresponding to the medication plan list through a large model based on the prompt word; in response to the patient already having medication reminder information, determining whether a medication reminder has been performed based on the existing medication reminder information; in response to no medication reminder being performed, obtaining existing prescription information corresponding to the existing medication reminder information; in response to the existing prescription information being inconsistent with the prescription information, generating a prompt word based on the prescription information, the medical record information and the medication plan list, and generating medication reminder information corresponding to the medication plan list through a large model based on the prompt word.

[0008] Optionally, the method further includes: generating medication process record information based on the medication plan list; generating medication management information based on the medication reminder information and the medication process record information, so as to perform medication reminders and medication status records based on the medication management information.

[0009] Optionally, medication process record information is generated based on the medication plan list, including: obtaining the patient's ongoing medication plan list, and generating a drug list based on the drugs included in each medication plan list, each drug in the drug list has a medication cycle; determining the date range of the medication process based on the medication cycle of each drug, and generating a medication calendar; obtaining the medication status of each drug within the medication cycle, and determining the daily medication status within the date range of the medication process based on the medication status of each drug within the medication cycle; marking the daily medication status within the date range of the medication process in the medication calendar to obtain medication process record information.

[0010] Optionally, the daily medication status within the date range of the medication process is determined based on the medication situation of each drug within the medication cycle, including: for each date within the date range of the medication process, if no medication is required on that date, the medication status of that date is no medication required; if the number of times any drug is used on that date is less than the number of times the medication is used, the medication status of that date is incomplete; if the number of times all drugs on that date are used reaches the number of times the medication is used, the medication status of that date is completed.

[0011] Optionally, performing medication reminders and recording medication status based on the medication management information includes: generating a medication management component based on the medication management information, so as to perform medication reminders and record medication status through the medication management component, the medication management component having a human-computer interaction interface, and the human-computer interaction interface is used to interact with the user to query medication management information and record medication status.

[0012] Optionally, recording medication usage according to the medication management information includes: in response to detecting a user access operation to the medication management information, obtaining the medication status of the target drug corresponding to the access operation on the target date; in response to the absence of medication on the target date, modifying the number of times the target drug is used, wherein, if the target date is today, the number of times the target drug is used is recorded as 1; if the target date is not today, the number of times the target drug is used is recorded as the number of times the medication is applied; in response to the existence of medication on the target date, modifying the number of times the target drug is used, wherein, if the target date is today, the number of times the target drug is used is increased by 1; if the target date is not today, the number of times the target drug is used is recorded as the number of times the medication is applied.

[0013] Optionally, in response to the existence of medication on the target date, before modifying the number of times the target drug is used, the method further includes: determining that the number of times the target drug is used is less than the number of times the drug is used.

[0014] According to another aspect of an embodiment of the present invention, there is provided a device for managing medication, comprising: An information acquisition module is used to obtain the patient's prescription information and medical record information from the hospital information system in response to monitoring the patient's medication collection event; A medication plan generation module, configured to generate a medication plan list based on the prescription information and the medical record information; A medication reminder generating module, configured to generate medication reminder information based on the prescription information, the medical record information, and the medication plan list; The medication reminder module is used to provide medication reminders based on the medication reminder information to manage medication.

[0015] According to another aspect of an embodiment of the present invention, an electronic device is provided, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for medication management provided by an embodiment of the present invention.

[0016] According to another aspect of an embodiment of the present invention, a computer-readable medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method for medication management provided by an embodiment of the present invention is implemented.

[0017] According to another aspect of the embodiments of the present invention, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, the method for medication management provided by the embodiments of the present invention is implemented.

[0018] One embodiment of the above invention has the following advantages or beneficial effects: by responding to monitoring the patient's medication pickup event, obtaining the patient's prescription information and medical record information from the hospital information system; generating a medication plan list based on the prescription information and medical record information; generating medication reminder information based on the prescription information, medical record information and medication plan list; the technical solution of providing medication reminders based on the medication reminder information to manage medication can automatically generate corresponding medication plans and medication reminder information when the patient picks up the medicine, solving the problem of patients manually adding medication reminders, and the medication reminder and management method is more intelligent and flexible.

[0019] In addition, the present invention also provides a medication management component for medication management. This component features a flexible and intuitive human-computer interaction interface. Using date as the horizontal axis and the medication list as the vertical axis, it provides a one-screen overview of medication usage across multiple medications and dates, eliminating the need for patients to perform complex medication information queries. Finally, the present invention also provides daily medication reminders. By combining the patient's medical history, prescription information, and drug instructions, the present invention generates user-friendly daily medication reminders through a large model. This, combined with the medication management component, provides users with a superior medication experience.

[0020] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with specific embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings are provided for a better understanding of the present invention and are not intended to limit the present invention. Figure 1 This is a schematic diagram of the main steps of a method for medication management according to an embodiment of the present invention; Figure 2 This is a schematic diagram of a process for generating a medication plan list according to an embodiment of the present invention; Figure 3 This is a schematic diagram of the process of generating medication reminder information according to an embodiment of the present invention; Figure 4 This is a schematic diagram of a medication reminder process according to an embodiment of the present invention; Figure 5 This is a schematic diagram of the interface of a medication management component according to an embodiment of the present invention; Figure 6This is a schematic diagram of an interface of a medication management component in an abbreviated state according to an embodiment of the present invention; Figure 7 This is a schematic diagram of a drug management interface according to an embodiment of the present invention; Figure 8 This is a schematic diagram of the process of generating medication process record information according to an embodiment of the present invention; Figure 9 This is a schematic diagram of a medication record process according to an embodiment of the present invention; Figure 10 is a schematic diagram of main modules of a medication management device according to an embodiment of the present invention; Figure 11 is an exemplary system architecture diagram in which embodiments of the present invention may be applied; Figure 12 It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0022] The following description of exemplary embodiments of the present invention is made in conjunction with the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding. These details should be considered as merely exemplary. Therefore, it should be appreciated by those skilled in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0023] It should be noted that the collection, collection, updating, analysis, processing, use, transmission, and storage of user personal information involved in the technical solutions disclosed in this invention all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken with respect to user personal information to prevent unauthorized access to user personal information data and to safeguard the security of user personal information, network security, and national security.

[0024] Existing software for medication reminders or medication management generally requires users to manually add medication reminder information based on the doctor's prescription and drug instructions, and manually set the dosage and time of each medication. This method of medication management requires users to manually add medication reminders, which is not flexible and intelligent enough, and the operation is complicated. It cannot provide an integrated service for patients to see a doctor, get prescriptions, generate medication plans, and receive medication reminders. In addition, when existing medication reminders or medication management software are used for medication reminders, the drug reminder interface is mostly based on a daily dimension, and the medication reminders at the set time are displayed according to the timeline of the day. The presentation form is not intuitive enough, and viewing previous medication record information requires a single click to switch, which is complicated to operate and lacks a global visual experience. Finally, the medication reminder content of the existing technology is limited to static medication information, without intelligent human-computer interaction text, and is relatively dull and uninteresting.

[0025] In order to solve at least one of the above technical problems, the present invention provides a method for medication management, provides an integrated medication reminder service, connects the hospital information system HIS (Hospital Information System), monitors patient medication collection events and retrieves the patient's prescription information and medical record information from the HIS, and automatically generates a corresponding medication plan when the patient picks up the medicine, solving the problem of patients manually adding medication reminders. In addition, when performing medication management, the present invention also provides a medication management component with a flexible and intuitive human-computer interaction interface. It uses the date as the horizontal axis and the drug list as the vertical axis to provide a one-screen overview of multiple drugs and cross-date medication status, eliminating the patient's complicated medication information query operations. Finally, the present invention also provides daily medication reminder text. Combined with the patient's medical record information, prescription information, drug instructions, etc., a friendly daily medication reminder text is generated through a large model, and combined with the medication management component to bring users a good medication experience.

[0026] In the introduction of the embodiments of the present invention, the users mentioned refer to patients.

[0027] Figure 1 FIG. 1 is a schematic diagram of the main steps of the method for medication management according to an embodiment of the present invention. Figure 1 As shown, the medication management method according to the embodiment of the present invention mainly includes the following steps S101 to S104.

[0028] Step S101: In response to monitoring a patient medication pickup event, the patient's prescription information and medical history information are retrieved from the hospital information system. According to the technical solution of the present invention, to intelligently generate medication reminders, the medication management system is data-connected with the hospital information system and can monitor event messages indicating that a patient has completed medication pickup. Upon receiving an event message indicating that a patient has completed medication pickup, the system automatically queries the hospital information system for the patient's prescription information, medical history information, and other information. Based on the medication plan generation rules and the patient's prescription information, medical history information, and other information, a medication plan list is generated and stored in the database.

[0029] Prescription information includes, for example, the prescription number, the prescribed medications, the number of days for each medication, the frequency of use, the dosage per dose, the time of use, the drug specifications, the quantity of the medication, the urgency of the use, and the doctor's order information. Medical history information includes, for example, the doctor's examination information, diagnosis information, and treatment information of the patient's condition.

[0030] Step S102: Generate a medication plan list based on prescription information and medical history information. According to the technical solution of the present invention, after obtaining prescription information and medical history information, a medication plan list is generated based on the patient's prescription information and medical history information. Each prescription may correspond to at least one drug, and each drug corresponds to a medication plan. The medication plans corresponding to each drug in a prescription constitute a medication plan list.

[0031] In one embodiment of the present invention, before generating a medication plan list based on prescription information and medical record information, it is also possible to determine whether all prescriptions for which the patient has paid have been filled, and to perform deduplication processing based on the prescription information (for example, prescription number) to avoid repeated generation of medication plan lists due to problems such as the hospital information system repeatedly sending patient medication collection events.

[0032] According to one embodiment of the present invention, prescription information includes the name of the drug, the frequency and time of use of each drug, and medical order information. Generating a medication plan list based on the prescription information and medical record information can specifically include: creating medication plans corresponding to each drug based on the drug name in the prescription information; determining the medication cycle and medication date corresponding to each medication plan based on the frequency and time of use of each drug in the prescription information; generating a medication plan description copy through a large model based on the medical order information, medical record information, and detailed drug information of each drug in the prescription information, where the drug detailed information is generated based on the drug instructions; generating a medication plan list based on the medication plan corresponding to each drug, the medication cycle and medication date corresponding to each medication plan, and the medication plan description copy.

[0033] In specific implementation, a medication plan is first created for each drug based on the drug name in the prescription information. Next, based on pre-set medication rules, the corresponding medication cycle and date are determined based on the medication time (including medication date, medication time period, etc.) and frequency of each drug in the prescription information. A medication rule, for example, is a medication dictionary that describes the specific medication dosage, including dosage frequency (e.g., 3 times per day), medication cycle (e.g., 14 days), and medication interval (e.g., every 2 days). Based on the medication rules and prescription information, the medication cycle, date, and other information for each medication plan are determined. Then, based on the doctor's order information, medical history information, and detailed drug information for each drug, a large model is used to generate medication plan descriptions. The detailed drug information is generated based on the drug insert and includes, for example, information on drug ingredients, adverse reactions, and precautions. Finally, a medication plan list is generated by combining the generated medication plans for each drug, the corresponding medication cycle and date, and the medication plan descriptions.

[0034] Figure 2 FIG. 1 is a flow chart of generating a medication plan list according to an embodiment of the present invention. Figure 2 As shown, in one embodiment of the present invention, the process for generating a medication plan list is as follows: upon receiving a patient medication pickup event, prescription information (including the prescription number) is retrieved from the hospital information system. Based on the prescription information, it is determined whether a medication plan has been generated for the prescription. If so, no further processing is required, and the process ends. Otherwise, a medication plan is constructed for each drug based on the drug name in the prescription information, and detailed drug information is determined based on the drug insert and added to the medication plan. The medication plan construction can be implemented according to pre-set medication plan generation rules. Next, the medication cycle and date corresponding to each medication plan are determined based on the medication time and frequency of each drug in the prescription information. Medical record information is then retrieved from the hospital information system. Prompt words are constructed based on the prescription order information, medical record information, and detailed drug information for each drug. A medication plan description is then generated using a large model. Finally, a medication plan list is generated based on the medication plan corresponding to each drug, the medication cycle and date corresponding to each medication plan, and the medication plan description.

[0035] Step S103: Generate medication reminder information based on prescription information, medical record information and medication plan list.

[0036] According to the technical solution of the present invention, after the patient picks up the medicine, the medication plan list and medication reminder information can be automatically generated, which solves the problem of patients manually adding medication reminders, and the medication reminder and management method is more intelligent and flexible.

[0037] According to one embodiment of the present invention, medication reminder information is generated based on prescription information, medical history information, and a medication plan list. Specifically, this may include: generating prompt words based on the prescription information, medical history information, and medication plan list, and generating medication reminder information corresponding to the medication plan list using a large model based on the prompt words. Specifically, a large model can be pre-trained to generate prompt words based on prescription information, medical history information, and a medication plan list, and the large model can be used to generate medication reminder information corresponding to the medication plan list. Generating medication reminder information using a large model makes the generated medication reminder information more friendly and interesting, rather than being a dull reminder.

[0038] According to one embodiment of the present invention, medication reminder information is generated based on prescription information, medical record information and a medication plan list, which may specifically include: determining whether the patient already has medication reminder information; in response to the patient not having medication reminder information, generating prompt words based on the prescription information, medical record information and the medication plan list, and generating medication reminder information corresponding to the medication plan list through a large model based on the prompt words; in response to the patient already having medication reminder information, determining whether a medication reminder has been performed based on the existing medication reminder information; in response to no medication reminder being performed, obtaining existing prescription information corresponding to the existing medication reminder information; in response to the existing prescription information being inconsistent with the prescription information, generating prompt words based on the prescription information, medical record information and the medication plan list, and generating medication reminder information corresponding to the medication plan list through a large model based on the prompt words.

[0039] Specifically, when generating medication reminders, you can set a scheduled task and execute it daily to generate the next day's medication reminder. Alternatively, you can generate a medication plan list after the user picks up medication, and use the plan list to generate the next day's medication reminder. Typically, on the day of medication pick-up, there is no need for a medication reminder, so the next day's medication reminder can be generated directly.

[0040] For a daily scheduled task to generate medication reminders for the next day, the scheduled task (for example, a task executed at 9:00 PM daily) first retrieves the patient information for the existing medication plan list. Then, based on each patient's configured medication reminder time, medication reminders are generated one by one. For each patient, the medication plan list consisting of all medication plans and the patient's medication reminder record for the day are first obtained and compared as follows to generate the next day's medication reminder information: (1) If the patient has no medication reminder information on that day, a large model prompt word Prompt is assembled based on the prescription information, medical record information, and medication plan list data, and the medication reminder information for the next day is generated through the large model; (2) If the patient has medication reminder information on that day, it is determined whether the medication reminder information has been pushed on that day. If it has been pushed, there is no need to push it again, and the logic of generating medication reminder information for the patient will be skipped; if it has not been pushed, the prescription corresponding to the medication reminder information on that day is compared with the prescription corresponding to the medication plan list to see if there is any difference; (3) If there is no difference, there is no need to repeatedly generate medication reminder information for the patient, and the logic of generating medication reminder information for the patient is skipped; (4) If there is a difference, it means that it is a new prescription scenario. Then, the large model prompt word Prompt is assembled based on the data in the prescription information, medical record information and medication plan list, and the medication reminder information for the next day is generated through the large model, and the medication reminder information for the current day is updated.

[0041] Figure 3 FIG. 1 is a schematic diagram of a process flow for generating medication reminder information according to an embodiment of the present invention. In the embodiment of the present invention, the process flow for generating medication reminder information can be triggered in two execution modes.

[0042] If it is triggered by a daily scheduled task, first obtain the set of patients who already have a medication plan list, and then generate medication reminder information for each patient one by one according to the medication reminder time configured for each patient from early to late. Among them, for each patient, first obtain the medication plan list consisting of all the medication plans of the patient. If there is no medication plan list, then end the process of generating medication reminder information for the patient; if there is a medication plan list, obtain the prescription set A corresponding to the medication plan list, and then search for the patient's medication reminder information for that day. If there is no medication reminder information for the patient on that day, directly call the large model to generate medication reminder information for the next day; if there is medication reminder information for the patient on that day, determine whether the medication reminder information has been pushed on that day. If it has been pushed, end the process of generating medication reminder information for the patient; otherwise, obtain the prescription set B corresponding to the medication reminder information for that day. Afterwards, determine whether the prescription set A corresponding to the medication plan list is consistent with the prescription set B corresponding to the medication reminder information of the day. If they are consistent, the process of generating medication reminder information for the patient is ended; otherwise, based on the prescription set A corresponding to the medication plan list, call the large model to generate the medication reminder information for the next day, and update the medication reminder information of the day.

[0043] If it is triggered by the patient's medication collection event, first determine whether the current time is later than the medication reminder time based on the medication reminder time configured by the patient. If it is later, no medication reminder is required on that day, and the process of generating medication reminder information for the patient ends; otherwise, obtain a medication plan list consisting of all medication plans for the patient. The subsequent implementation process of generating the patient's medication reminder information for the next day based on the medication plan list is the same as the implementation process of generating the patient's medication reminder information for the next day triggered by the daily scheduled task mentioned above, and will not be repeated here.

[0044] Step S104: Medication reminders are issued based on the medication reminder information to manage medication. When issuing a medication reminder, the reminder will be completed according to the reminder time set by the patient. Medication reminders can be issued through various channels, such as push notifications of medication reminder message cards, notifications on the top of the head, and notifications on a public account. The specific channel can be set by the user and is not limited in this invention.

[0045] Figure 4 FIG. 1 is a flowchart of a medication reminder according to an embodiment of the present invention. Figure 4 As shown, when performing medication reminders, the reminder process can be set to execute every half hour, the same granularity as the user-set reminder time. When the medication reminder process is triggered, the current time is first obtained. Based on the current time and the user-set reminder time, the patient set A for this medication reminder is determined. For each patient in patient set A, the medication reminder is triggered based on the patient's medication reminder information and the set reminder channel, and the patient's medication reminder status is updated to "Reminded".

[0046] According to another embodiment of the present invention, the medication management method may further include: generating medication progress record information based on the medication plan list; and generating medication management information based on the medication reminder information and the medication progress record information, so as to provide medication reminders and record medication status based on the medication management information. Specifically, the medication progress record information may include, for example, a medication calendar, medication status, and other information used to record the medication progress.

[0047] According to another embodiment of the present invention, medication process record information is generated based on the medication plan list, which can specifically include: obtaining the patient's ongoing medication plan list, and generating a drug list based on the drugs included in each medication plan list, each drug in the drug list has a medication cycle; determining the date range of the medication process based on the medication cycle of each drug, and generating a medication calendar; obtaining the medication status of each drug within the medication cycle, and determining the daily medication status within the date range of the medication process based on the medication status of each drug within the medication cycle; marking the daily medication status within the date range of the medication process in the medication calendar to obtain medication process record information.

[0048] In specific implementations, the date range for the medication process can be determined based on the union of each drug's medication cycles to generate a medication calendar. For example, if the medication cycle for drug A is January 1st to January 8th, and the medication cycle for drug B is January 5th to January 15th, the union of these two medication cycles is January 1st to January 15th. This union can then be used as the date range for the medication process. Alternatively, a calendar display number of days can be pre-set (e.g., 60 days), and the sum of the number of days before and after the union and the union can be used as the date range for the medication process. Alternatively, the current date can be centered, and a sliding range of dates (e.g., 60 days) can be used as the date range for the medication process. Once the date range is determined, a quadrant representing the medication use, composed of dates and drugs, can be generated, with the date as the X-axis and the drug list as the Y-axis. For the medication calendar, a different background color can be set for each drug displayed to differentiate them.

[0049] Afterwards, the medication status of each drug within the medication cycle is obtained, and the medication status of each day within the date range of the medication process is determined based on the medication status of each drug within the medication cycle. In one embodiment of the present invention, the medication status of each day within the date range of the medication process is determined based on the medication status of each drug within the medication cycle. For example, the following may be included: for each date within the date range of the medication process, if no medication is required on that date, the medication status of that date is "no medication required"; if the number of times any drug is used on that date is less than the number of times it is used, the medication status of that date is "incomplete"; if the number of times all drugs on that date are used reaches the number of times they are used, the medication status of that date is "completed".

[0050] Medication status includes, for example, whether medication is needed, medication completion status, and specific medication progress. Daily medication status can be determined based on the medication status. In one embodiment, medication status can be categorized into the following: unfinished medication, not started, in progress, completed, and no medication required. For each day within the medication process's date range, if the date is less than today, whether medication is needed on that day is determined. If no medication is needed, the status is marked as "no medication required." If medication is needed, the medication status is determined. If unfinished medication is marked as "unfinished," and if completed medication is marked as "completed." If the date is today, whether medication is needed on that day is determined. If no medication is needed, the status is marked as "unfinished," and if completed medication is marked as "completed." If medication is needed, the medication status is determined. If unfinished medication is marked as "in progress," and if completed medication is marked as "completed." If the date is greater than today, whether medication is needed on that day is determined. If no medication is needed, the status is marked as "no medication required," and if not, the status is marked as "not started."

[0051] During the specific implementation process, different display forms can be set for different medication statuses. For example, if medication is not needed on a certain date, a "background color" is displayed; if medication is needed on a certain date but has not yet started, a "hollow circle icon" is displayed; if medication is needed on a certain date and has been completed, a "check mark icon" is displayed; if medication is needed today and has not been completed, the specific medication progress is displayed, marked by a "progress circle", such as 1 / 3, indicating that the number of medication applications today is 3, and the number of medication applications is 1; if medication was needed in the past and was not completed, an "exclamation mark icon" is displayed, and so on.

[0052] In one embodiment of the present invention, medication reminders and medication status records are performed based on medication management information, which may specifically include: generating a medication management component based on the medication management information, so as to perform medication reminders and medication status records through the medication management component, and the medication management component has a human-computer interaction interface, and the human-computer interaction interface is used to interact with the user to query medication management information and record medication status.

[0053] In an embodiment of the present invention, if the medication management component is a medication reminder message card, and medication reminders are sent by pushing medication reminder message cards, the previous day's medication reminder message card will be converted to an abbreviated state before pushing today's medication reminder message card. This abbreviated medication reminder message card only displays the daily medication reminder information. In contrast, the normal medication reminder message card can display medication progress information in addition to the medication reminder information.

[0054] Figure 5 This is a schematic diagram of the interface of a medication management component according to an embodiment of the present invention; Figure 6 FIG. 1 is a schematic diagram of an interface of a medication management component in an abbreviated state according to an embodiment of the present invention. Figure 6 As shown in the figure, the abbreviated interface of the medication management component only displays medication reminder information in the form of text. Figure 5 As shown, in addition to displaying medication reminder information, the normal state interface of the medication management component can also display medication process record information, including: medication calendar (the drug list only displays the first character of the drug name, filtering out special symbols in the drug name, such as "》", "(", and other emphasis symbols), basic drug information (including drug name, frequency of use, dosage per time, method of use, etc.), etc. In addition, a page turning icon can be displayed in this interface, which can be used to easily view the medication management information of the previous day and the next day.

[0055] Figure 7 FIG. 1 is a schematic diagram of a drug management interface according to an embodiment of the present invention. Figure 7 As shown, the drug management interface is used to manage the drugs to be displayed in the medication management component. Specifically, through the drug management interface, you can set the switch for sending drug reminders and the reminder time, you can also freely switch the disabled and enabled status of the drugs, dynamically select the drugs to be reminded and display the relevant drug list in groups, and sort the ongoing drug list, etc. Among them, the ongoing drug list can be dragged and sorted, and the order of the drugs in the medication management component will change accordingly. When a disabled drug is switched to the enabled state, the drug will be placed first in the ongoing drug list and regarded as an important drug. It should be noted that drugs that have exceeded the medication cycle are not allowed to be activated again.

[0056] Figure 8 This is a schematic diagram of the generation process of medication process record information according to an embodiment of the present invention. Figure 8 As shown, in one embodiment of the present invention, the process of generating medication process record information is mainly as follows: (1) Obtain the list of medication plans for the current patient within the medication cycle, merge them by drug number to obtain a drug list, and perform regular sorting on the merged drug list: patient drag sorting is prioritized, and the latest medication collection time is secondary priority; (2) Traverse the drug list and construct basic drug information, including drug name, frequency of use, dosage per time, method of use, etc., and calculate the medication cycle and number of days for each drug; (3) Calculate the maximum medication cycle and medication days of the drug list based on the medication cycle and medication days of each drug, and fill the medication cycle table of each drug according to the maximum cycle to generate a medication calendar, and process the irregular medication calendar into a standard rectangular medication calendar; (4) Match the colors of the drug list. Specifically, each color can be taken out from the color pool in sequence through a pointer and matched in a loop according to the order of the drugs. (5) Query the medication status of each drug and process it into a medication status data pool with a key-value pair structure; (6) Traverse the medication cycle of each drug, from the start time to the end time of medication, and extract the current medication status from the medication record pool, and then determine the daily medication status based on the medication status; (7) Traverse the medication calendar, mark the daily medication status and today's medication situation in the medication calendar, and generate medication process record information.

[0057] According to another embodiment of the present invention, recording medication usage according to medication management information may specifically include: in response to detecting a user access operation to the medication management information, obtaining the medication usage of the target drug corresponding to the access operation on the target date; in response to the absence of medication on the target date, modifying the number of times the target drug is used, wherein if the target date is today, the number of times the target drug is used is recorded as 1; if the target date is not today, the number of times the target drug is used is recorded as the number of times the medication is applied; in response to the presence of medication on the target date, modifying the number of times the target drug is used, wherein if the target date is today, the number of times the target drug is used is increased by 1; if the target date is not today, the number of times the target drug is used is recorded as the number of times the medication is applied.

[0058] According to another embodiment of the present invention, in response to medication usage on the target date, before modifying the number of medications used for the target drug, it is necessary to determine whether the number of medications used for the target drug is less than the number of medications used. If the number of medications used for the target drug has already reached the number of medications used, there is no need to modify the number of medications used.

[0059] According to the technical solution of the present invention, the number of times each drug is used can be recorded separately. Only drugs in the two medication statuses of "medication in progress" and "medication not completed" can have their medication status recorded. Medication status records are not allowed for drugs in the medication statuses of "medication completed", "no medication needed" and "medication not started".

[0060] "Medication in Progress" indicates the current medication status for a particular drug, and the interface interaction is a "progress circle." Each time you record a medication use, the number of times the current medication is used increases by 1, until the number of uses reaches the required number of times. For example, if a medication is used three times a day, after recording a medication use, the current progress for that medication is 1 / 3. After three clicks, the medication status changes to "Completed" and the interface interaction changes to a "check mark icon."

[0061] "Incomplete Medication" indicates a medication status for a past date, meaning it was not completely taken. The interface interaction icon is an exclamation mark. This type of medication record is a supplemental record of past medication use, so clicking on the medication once will change the status to "Completed Medication" and the interface interaction icon will change to a check mark icon.

[0062] Figure 9 FIG. 1 is a flowchart of a medication record process according to an embodiment of the present invention. Figure 9 As shown, in one embodiment of the present invention, the medication record process is mainly as follows: (1) According to the user's access operation to the medication management information, the target drug and target date for medication record are obtained; (2) Obtain the patient's medication status on the target date to determine whether medication use exists; (3) If there is no medication, first determine whether the target date is today. If it is today, record the number of times the target drug is used as 1; if it is not today, that is, it is a historical date, then directly record the number of times the target drug is used as the number of times the drug is used; (4) If medication usage already exists, first determine whether the target date is today. If it is today, determine whether the number of medication usage is less than the number of medications used. If so, increase the number of medications used by the target drug by 1. Otherwise, do not record the medication usage and end the process. If it is not today, that is, it is a historical date, determine whether the number of medication usage is less than the number of medications used. If so, directly record the number of medications used by the target drug as the number of medications used. Otherwise, do not record the medication usage and end the process.

[0063] Figure 10 FIG is a schematic diagram of the main modules of the device for medication management according to an embodiment of the present invention. Figure 10 As shown, the medication management device 1000 according to the embodiment of the present invention mainly includes an information acquisition module 1001 , a medication plan generation module 1002 , a medication reminder generation module 1003 and a medication reminder module 1004 .

[0064] The information acquisition module 1001 is used to obtain the patient's prescription information and medical record information from the hospital information system in response to monitoring the patient's medication collection event; Medication plan generation module 1002, for generating a medication plan list based on prescription information and medical record information; Medication reminder generation module 1003, for generating medication reminder information based on prescription information, medical record information and medication plan list; The medication reminder module 1004 is used to provide medication reminders based on the medication reminder information to manage medication.

[0065] According to one embodiment of the present invention, prescription information includes the name of the drug, the frequency and time of use of each drug, and medical advice information; the medication plan generation module 1002 can be specifically used to: create a medication plan corresponding to each drug according to the drug name in the prescription information; determine the medication cycle and medication date corresponding to each medication plan according to the frequency and time of use of each drug in the prescription information; generate a medication plan description text through a large model based on the medical advice information, medical record information and detailed drug information of each drug in the prescription information, and the drug detailed information is generated based on the drug instructions; generate a medication plan list according to the medication plan corresponding to each drug, the medication cycle and medication date corresponding to each medication plan, and the medication plan description text.

[0066] According to another embodiment of the present invention, the medication reminder generation module 1003 can be specifically used to: generate prompt words based on prescription information, medical record information and medication plan list, and generate medication reminder information corresponding to the medication plan list through a large model based on the prompt words.

[0067] According to another embodiment of the present invention, the medication reminder generation module 1003 can be specifically used to: determine whether the patient already has medication reminder information; in response to the patient not having medication reminder information, generate prompt words based on prescription information, medical record information and medication plan list, and generate medication reminder information corresponding to the medication plan list through the big model based on the prompt words; in response to the patient already having medication reminder information, determine whether a medication reminder has been performed based on the existing medication reminder information; in response to no medication reminder being performed, obtain existing prescription information corresponding to the existing medication reminder information; in response to the existing prescription information being inconsistent with the prescription information, generate prompt words based on prescription information, medical record information and medication plan list, and generate medication reminder information corresponding to the medication plan list through the big model based on the prompt words.

[0068] According to another embodiment of the present invention, the medication management device 1000 also includes: a process record information generation module (not shown in the figure), which is used to: generate medication process record information based on the medication plan list; a medication management module (not shown in the figure), which is used to: generate medication management information based on medication reminder information and medication process record information, so as to perform medication reminders and medication status records based on the medication management information.

[0069] According to another embodiment of the present invention, the process record information generation module (not shown in the figure) can be specifically used to: obtain the patient's ongoing medication plan list, and generate a drug list based on the drugs included in each medication plan list, each drug in the drug list has a medication cycle; determine the date range of the medication process based on the medication cycle of each drug, and generate a medication calendar; obtain the medication situation of each drug within the medication cycle, and determine the daily medication status within the date range of the medication process based on the medication situation of each drug within the medication cycle; mark the daily medication status within the date range of the medication process in the medication calendar to obtain medication process record information.

[0070] According to another embodiment of the present invention, when determining the daily medication status within the date range of the medication process based on the medication situation of each drug within the medication cycle, the process record information generation module (not shown in the figure) can be specifically used to: for each date within the date range of the medication process, if the date does not require medication, the medication status of the date is no medication required; if the number of times any drug is used within the date is less than the number of times it is used, the medication status of the date is incomplete; if the number of times all drugs on the date are used reaches the number of times they are used, the medication status of the date is completed.

[0071] According to another embodiment of the present invention, a medication management module (not shown in the figure) can be specifically used to: generate a medication management component based on medication management information, so as to provide medication reminders and record medication status through the medication management component. The medication management component has a human-computer interaction interface, and the human-computer interaction interface is used to interact with the user to query medication management information and record medication status.

[0072] According to another embodiment of the present invention, the medication management module (not shown in the figure) can be specifically used to: in response to detecting a user's access operation to the medication management information, obtain the medication status of the target drug corresponding to the access operation on the target date; in response to the absence of medication on the target date, modify the number of times the target drug is used, wherein if the target date is today, the number of times the target drug is used is recorded as 1; if the target date is not today, the number of times the target drug is used is recorded as the number of times the medication is applied; in response to the existence of medication on the target date, modify the number of times the target drug is used, wherein if the target date is today, the number of times the target drug is used is increased by 1; if the target date is not today, the number of times the target drug is used is recorded as the number of times the medication is applied.

[0073] According to another embodiment of the present invention, the medication management device 1000 also includes a medication frequency determination module (not shown in the figure), which is used to: in response to the existence of medication on the target date, determine that the medication frequency of the target drug is less than the application frequency before modifying the medication frequency of the target drug.

[0074] According to the technical solution of the embodiment of the present invention, by responding to monitoring a patient's medication collection event, the patient's prescription information and medical history information are obtained from the hospital information system; a medication plan list is generated based on the prescription information and medical history information; medication reminder information is generated based on the prescription information, medical history information, and medication plan list; and medication reminder information is used to manage medication. This technical solution can automatically generate corresponding medication plans and medication reminder information when the patient picks up medication, eliminating the problem of patients manually adding medication reminders and making medication reminders and management more intelligent and flexible. In addition, when managing medication, the present invention also provides a medication management component with a flexible and intuitive human-computer interaction interface. With the date as the horizontal axis and the drug list as the vertical axis, it provides a one-screen overview of the medication status of multiple drugs and across dates, eliminating the patient's complex medication information query operations. Finally, the present invention also provides daily medication reminder text. By combining the patient's medical history information, prescription information, drug instructions, etc., a user-friendly daily medication reminder text is generated through a large model. Combined with the medication management component, it provides a good medication experience for users.

[0075] Figure 11 An exemplary system architecture 1100 is shown to which the method or apparatus for medication management according to an embodiment of the present invention may be applied.

[0076] like Figure 11 As shown, system architecture 1100 may include terminal devices 1101, 1102, and 1103, a network 1104, and a server 1105. Network 1104 is used to provide a medium for communication links between terminal devices 1101, 1102, and 1103 and server 1105. Network 1104 may include various connection types, such as wired or wireless communication links or fiber optic cables.

[0077] Users can use terminal devices 1101, 1102, and 1103 to interact with server 1105 via network 1104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 1101, 1102, and 1103, such as shopping applications, online medical applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0078] The terminal devices 1101 , 1102 , and 1103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0079] Server 1105 may be a server that provides various services, such as a backend management server (for example only) that supports shopping websites browsed by users using terminal devices 1101, 1102, and 1103. The backend management server may respond to received medication management requests and other data by monitoring patient medication collection events, obtaining the patient's prescription information and medical history information from the hospital information system; generating a medication plan list based on the prescription information and medical history information; generating medication reminder information based on the prescription information, medical history information, and medication plan list; performing other processing based on the medication reminder information, such as medication reminders, and feeding back the processing results (for example, medication reminder results—for example only) to the terminal device.

[0080] It should be noted that the medication management method provided in the embodiment of the present invention is generally executed by the server 1105 , and accordingly, the medication management device is generally set in the server 1105 .

[0081] It should be understood that Figure 11 The number of terminal devices, networks and servers in the embodiment is merely illustrative. Any number of terminal devices, networks and servers may be provided as required.

[0082] Reference below Figure 12 , which shows a schematic structural diagram of a computer system 1200 of a terminal device or server suitable for implementing an embodiment of the present invention. Figure 12 The terminal device or server shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0083] like Figure 12 As shown, computer system 1200 includes a central processing unit (CPU) 1201, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1202 or a program loaded from a storage unit 1208 into a random access memory (RAM) 1203. Various programs and data required for the operation of system 1200 are also stored in RAM 1203. CPU 1201, ROM 1202, and RAM 1203 are connected to each other via a bus 1204. An input / output (I / O) interface 1205 is also connected to bus 1204.

[0084] The following components are connected to the I / O interface 1205: an input section 1206 including a keyboard, mouse, and the like; an output section 1207 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and speakers; a storage section 1208 including a hard disk; and a communication section 1209 including a network interface card such as a LAN card or a modem. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the I / O interface 1205 as needed. Removable media 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 1210 as needed, so that computer programs read from the removable media can be installed in the storage section 1208 as needed.

[0085] In particular, according to embodiments disclosed herein, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed herein include a computer program product comprising a computer program embodied on a computer-readable medium, the computer program containing program code for executing the methods illustrated in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1209 and / or installed from removable media 1211. When executed by central processing unit (CPU) 1201, the computer program performs the aforementioned functions defined in the system of the present invention.

[0086] It should be noted that the computer-readable medium described in the present invention may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. Computer-readable storage media may include, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or components, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present invention, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such a propagated data signal may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wireline, optical fiber cable, RF, or any suitable combination thereof.

[0087] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the above-mentioned module, program segment, or a part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0088] The units or modules involved in the embodiments of the present invention may be implemented in software or in hardware. The units or modules described may also be provided in a processor. For example, they may be described as follows: a processor includes an information acquisition module, a medication plan generation module, a medication reminder generation module, and a medication reminder module. The names of these units or modules do not, in certain cases, constitute limitations on the units or modules themselves. For example, a medication reminder module may also be described as a "module for providing medication reminders for medication management based on medication reminder information."

[0089] As another aspect, the present invention further provides a computer-readable medium, which may be included in the device described in the above embodiment; or may exist independently and not be incorporated into the device. The computer-readable medium carries one or more programs, and when the one or more programs are executed by the device, the device includes: in response to monitoring a patient medication pickup event, obtaining the patient's prescription information and medical history information from a hospital information system; generating a medication plan list based on the prescription information and medical history information; generating medication reminder information based on the prescription information, medical history information, and medication plan list; and providing medication reminders based on the medication reminder information to manage medication.

[0090] According to the technical solution of the embodiment of the present invention, by responding to monitoring a patient's medication collection event, the patient's prescription information and medical history information are obtained from the hospital information system; a medication plan list is generated based on the prescription information and medical history information; medication reminder information is generated based on the prescription information, medical history information, and medication plan list; and medication reminder information is used to manage medication. This technical solution can automatically generate corresponding medication plans and medication reminder information when the patient picks up medication, eliminating the problem of patients manually adding medication reminders and making medication reminders and management more intelligent and flexible. In addition, when managing medication, the present invention also provides a medication management component with a flexible and intuitive human-computer interaction interface. With the date as the horizontal axis and the drug list as the vertical axis, it provides a one-screen overview of the medication status of multiple drugs and across dates, eliminating the patient's complex medication information query operations. Finally, the present invention also provides daily medication reminder text. By combining the patient's medical history information, prescription information, drug instructions, etc., a user-friendly daily medication reminder text is generated through a large model. Combined with the medication management component, it provides a good medication experience for users.

[0091] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

Claims

1. A method for medication management, characterized in that: include: In response to monitoring the patient's medication collection event, obtain the patient's prescription information and medical record information from the hospital information system; generating a medication plan list based on the prescription information and the medical record information; generating medication reminder information based on the prescription information, the medical record information, and the medication plan list; Medication reminders are provided based on the medication reminder information to manage medication.

2. The method according to claim 1, characterized in that The prescription information includes the name of the drug, the frequency and time of use of each drug, and medical advice information; Generate a medication plan list based on the prescription information and the medical record information, including: Creating a medication plan corresponding to each drug according to the drug name in the prescription information; Determine the medication cycle and medication date corresponding to each medication plan based on the medication frequency and medication time of each drug in the prescription information; Generate a medication plan description using a large model based on the doctor's order information in the prescription information, the medical history information, and detailed information about each drug, where the detailed information is generated based on the drug insert; A medication plan list is generated based on the medication plans corresponding to the various drugs, the medication cycles and medication dates corresponding to each medication plan, and the medication plan description.

3. The method according to claim 1, characterized in that Generate medication reminder information based on the prescription information, the medical record information, and the medication plan list, including: Prompt words are generated according to the prescription information, the medical record information and the medication plan list, and medication reminder information corresponding to the medication plan list is generated through a large model according to the prompt words.

4. The method according to claim 1 or 3, characterized in that Generate medication reminder information based on the prescription information, the medical record information, and the medication plan list, including: Determining whether the patient already has medication reminder information; In response to the patient not having medication reminder information, generating a prompt word based on the prescription information, the medical record information, and the medication plan list, and generating medication reminder information corresponding to the medication plan list using a large model based on the prompt word; In response to the patient having medication reminder information, determining whether a medication reminder has been issued according to the existing medication reminder information; In response to not performing a medication reminder, obtaining existing prescription information corresponding to the existing medication reminder information; In response to the inconsistency between the existing prescription information and the prescription information, a prompt word is generated according to the prescription information, the medical record information and the medication plan list, and medication reminder information corresponding to the medication plan list is generated through a large model according to the prompt word.

5. The method according to claim 1, wherein The method further comprises: Generate medication process record information according to the medication plan list; Medication management information is generated according to the medication reminder information and the medication process record information, so as to perform medication reminders and medication status records according to the medication management information.

6. The method according to claim 5, characterized in that Generate medication process record information based on the medication plan list, including: Obtaining a list of ongoing medication plans for the patient, and generating a drug list based on the drugs included in each medication plan list, wherein each drug in the drug list has a medication cycle; Determine the date range of medication process according to the medication cycle of each drug and generate a medication calendar; Obtaining the medication status of each drug during the medication cycle, and determining the medication status of each drug on a daily basis within the date range of the medication process based on the medication status of each drug during the medication cycle; The medication status of each day within the date range of the medication process is marked in the medication calendar to obtain medication process record information.

7. The method according to claim 6, characterized in that Determine the daily medication status within the date range of the medication process based on the medication status of each drug during the medication cycle, including: For each date within the date range of the medication process, if no medication is needed on the date, the medication status of the date is no medication needed; If the number of times any drug is used on the date is less than the number of times the drug is used, the medication status on the date is incomplete; If the number of times all drugs are used on the date reaches the number of times of use, the medication status on the date is completed.

8. The method according to claim 5, characterized in that Medication reminders and medication status records are performed based on the medication management information, including: A medication management component is generated based on the medication management information to provide medication reminders and record medication status through the medication management component. The medication management component has a human-computer interaction interface, which is used to interact with the user to query medication management information and record medication status.

9. The method according to claim 5 or 8, characterized in that Medication management information is used to record medication usage, including: In response to detecting a user access operation to the medication management information, obtaining medication status of a target drug corresponding to the access operation on a target date; In response to the absence of medication use on the target date, modifying the number of medication uses of the target drug, wherein if the target date is today, the number of medication uses of the target drug is recorded as 1; if the target date is not today, the number of medication uses of the target drug is recorded as the number of medication applications; In response to the existence of medication on the target date, the number of times the target drug is used is modified, wherein if the target date is today, the number of times the target drug is used is increased by 1; if the target date is not today, the number of times the target drug is used is recorded as the number of times the medication is applied.

10. The method according to claim 9, characterized in that In response to the existence of medication use on the target date, before modifying the number of medications of the target drug, the method further includes: Determine that the number of times the target drug is used is less than the number of times the drug is applied.

11. A device for medication management, characterized in that: include: An information acquisition module is used to obtain the patient's prescription information and medical record information from the hospital information system in response to monitoring the patient's medication collection event; A medication plan generation module, configured to generate a medication plan list based on the prescription information and the medical record information; A medication reminder generating module, configured to generate medication reminder information based on the prescription information, the medical record information, and the medication plan list; The medication reminder module is used to provide medication reminders based on the medication reminder information to manage medication.

12. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 10.

13. A computer-readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 10 is implemented.

14. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 10 is implemented.

Images