CN116433206A

Movatterモバイル変換

Info

Publication number: CN116433206A
Application number: CN202310458461.2A
Authority: CN
Inventors: 刘喜; 卜满钊; 原亚飞
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2023-04-18
Filing date: 2023-04-18
Publication date: 2023-07-14
Anticipated expiration: 2043-04-18
Also published as: CN116433206B

Abstract

The application relates to an event reminding method, an event reminding device, computer equipment, a storage medium and a program product. The method comprises the following steps: when the event description information exists, displaying an event execution plan of at least one to-be-confirmed state adapted to the event description information; the event description information is provided with an item name matched with an item identification in an event execution plan, and the event reminding time description information corresponding to the item identification in the event execution plan is matched with the event execution time description information of the item name in the event description information; in response to an enabling trigger operation of the event execution plan for any one of the to-be-confirmed states, displaying the event execution plan for which the trigger operation is enabled as being in an enabled state; when the reminding time divided according to the event reminding time description information of any event execution plan in the enabled state is reached, triggering event reminding corresponding to the event execution plan reaching the reminding time. By adopting the method, the interaction efficiency in the event reminding process can be improved.

Description

Event reminding method, event reminding device, computer equipment, storage medium and program product

Technical Field

The present invention relates to the field of computer technology, and in particular, to an event reminding method, an event reminding device, a computer device, a storage medium, and a computer program product.

Background

With the development of computer technology, various event reminders can be realized through computer equipment, for example, some people need to take medicines at regular time, but due to busy work and the like, people often forget to take medicines on time, so that the curative effect is reduced, even the illness state is aggravated, and in this case, the medicine taking reminder can be realized through the computer equipment.

Disclosure of Invention

In view of the foregoing, it is desirable to provide an event reminding method, apparatus, computer device, computer readable storage medium, and computer program product that can improve interaction efficiency in event reminding.

In one aspect, the present application provides an event alert method. The method comprises the following steps:

when event description information exists, displaying an event execution plan of at least one to-be-confirmed state adapted to the event description information; the event description information is provided with an item name matched with an item identifier in the event execution plan, and event reminding time description information corresponding to the item identifier in the event execution plan is matched with event execution time description information of the item name in the event description information;

Responding to an enabling trigger operation of an event execution plan aiming at any state to be confirmed, and displaying the event execution plan aiming at the enabling trigger operation as being in an enabled state;

when any reminding time divided according to the event reminding time description information of any event execution plan in the enabled state is reached, triggering event reminding corresponding to the event execution plan reaching the reminding time.

In some embodiments, the plurality of options includes at least a first option and a second option; the screening conditions corresponding to the first options are used for determining event execution plan sets corresponding to logged-in user accounts; and screening conditions corresponding to the second option, wherein the screening conditions are used for screening the event execution plans with the enabled states, the reminding time of which is within a specified period, from the event execution plan set.

In some embodiments, the event description information is an electronic prescription and belongs to a logged-in user account, and the event execution plan is a medication plan: the event execution plan of the at least one state to be confirmed is generated by a medication plan generation step including:

acquiring an electronic prescription belonging to the user account, generating prescription information based on the electronic prescription through a producer thread, and writing the prescription information into an information queue;

Reading prescription information from the information queue through a consumer thread, and extracting medicine names and medicine frequency from the read prescription information;

and generating at least one medicine taking plan matched with the electronic prescription according to the medicine name and the medicine taking frequency through the consumer thread.

On the other hand, the application also provides an event reminding device. The device comprises:

the first display module is used for displaying an event execution plan of at least one to-be-confirmed state which is adapted to the event description information when the event description information exists; the event description information is provided with an item name matched with an item identifier in the event execution plan, and event reminding time description information corresponding to the item identifier in the event execution plan is matched with event execution time description information of the item name in the event description information;

the second display module is used for responding to the starting trigger operation of the event execution plan aiming at any state to be confirmed and displaying the event execution plan aiming at the starting trigger operation as being in a started state;

and the event reminding module is used for triggering event reminding corresponding to the event execution plan reaching the reminding time when reaching any reminding time divided according to the event reminding time description information of any event execution plan in the started state.

In another aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor which when executing the computer program performs the steps of:

In another aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:

In another aspect, the present application also provides a computer program product. The computer program product comprises a computer program which, when executed by a processor, implements the steps of:

Drawings

FIG. 1 is an application environment diagram of an event alert method in some embodiments;

FIG. 2 is a flow chart of an event reminding method according to some embodiments;

FIG. 3 is a schematic diagram of a medication intake plan interaction page in some embodiments;

FIG. 4 is a schematic diagram of a notification message card in some embodiments;

FIG. 5 is a schematic diagram of a session page with a service account in some embodiments;

FIG. 6 is a schematic diagram of an event execution validation page in some embodiments;

FIG. 7 is a schematic diagram showing a medication confirmation portal in some embodiments;

FIG. 8 is a schematic diagram of a page displaying hints information in some embodiments;

FIG. 9 is a schematic diagram of a page displaying a reminder message card in some embodiments;

FIG. 10 is a schematic diagram of a medication confirmation page in other embodiments;

FIG. 11 is a diagram of a page corresponding to the present day medication in some embodiments;

FIG. 12 is a schematic diagram of a medication editing page in some embodiments;

FIG. 13 is a schematic illustration of a medication program interaction page in further embodiments;

FIG. 14 is a diagram of an architecture of a message queue in some embodiments;

FIG. 15 is a flowchart illustrating steps for generating a medication intake plan in some embodiments;

FIG. 16 is a schematic page view of a traditional Chinese medicine filling prescription content in some embodiments;

FIG. 17 is a schematic diagram of a encryption flow chart in some embodiments;

FIG. 18 is a flow diagram of timing task involvement in some embodiments;

FIG. 19 is a flowchart of a method for event notification in some embodiments;

FIG. 20 is a flow chart of an electronic prescription in some embodiments;

FIG. 21 is a timing diagram of a one-time request process in some embodiments;

FIG. 22 is a block diagram of an event reminder in some embodiments;

FIG. 23 is an internal block diagram of a computer device in some embodiments;

FIG. 24 is an internal block diagram of a computer device in some embodiments.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

Artificial intelligence (Artificial Intelligence, AI) is the theory, method, technique and application system that uses a digital computer or a machine controlled by a digital computer to simulate, extend and extend human intelligence, sense the environment, acquire knowledge and use the knowledge to obtain optimal results. In other words, artificial intelligence is an integrated technology of computer science that attempts to understand the essence of intelligence and to produce a new intelligent machine that can react in a similar way to human intelligence. Artificial intelligence, i.e. research on design principles and implementation methods of various intelligent machines, enables the machines to have functions of sensing, reasoning and decision.

The artificial intelligence technology is a comprehensive subject, and relates to the technology with wide fields, namely the technology with a hardware level and the technology with a software level. Artificial intelligence infrastructure technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a voice processing technology, a natural language processing technology, machine learning/deep learning, automatic driving, intelligent traffic and other directions.

Computer Vision (CV) is a science of studying how to "look" a machine, and more specifically, to replace a human eye with a camera and a Computer to perform machine Vision such as recognition and measurement on a target, and further perform graphic processing to make the Computer process an image more suitable for human eye observation or transmission to an instrument for detection. As a scientific discipline, computer vision research-related theory and technology has attempted to build artificial intelligence systems that can acquire information from images or multidimensional data. Computer vision technologies typically include image processing, image recognition, image semantic understanding, image retrieval, OCR, video processing, video semantic understanding, video content/behavior recognition, three-dimensional object reconstruction, 3D technology, virtual reality, augmented reality, synchronous positioning and mapping, autopilot, intelligent transportation, etc., as well as common biometric technologies such as face recognition, fingerprint recognition, etc.

Natural language processing (Nature Language processing, NLP) is an important direction in the fields of computer science and artificial intelligence. It is studying various theories and methods that enable effective communication between a person and a computer in natural language. Natural language processing is a science that integrates linguistics, computer science, and mathematics. Thus, the research in this field will involve natural language, i.e. language that people use daily, so it has a close relationship with the research in linguistics. Natural language processing techniques typically include text processing, semantic understanding, machine translation, robotic questions and answers, knowledge graph techniques, and the like.

The scheme provided by the embodiment of the application relates to the technologies of computer vision, natural language processing and the like of artificial intelligence, and is specifically described by the following embodiments:

the event reminding method provided by the embodiment of the application can be applied to an application environment shown in fig. 1. Wherein the terminal 102 communicates with theserver 104 via a network. The data storage system may store data that theserver 104 needs to process. The data storage system may be integrated on theserver 104 or may be located on the cloud or other servers. When there is event description information, the terminal 102 may display an event execution plan of at least one to-be-confirmed state adapted to the event description information, where there is an item name matching an item identification in the event execution plan, and event reminder time description information corresponding to the item identification in the event execution plan matches the event execution time description information of the item name in the event description information, and the terminal 102 may display the event execution plan for which the trigger operation is enabled as being in an enabled state in response to an enable trigger operation of the event execution plan for any to-be-confirmed state, and trigger an event reminder corresponding to the event execution plan for which the trigger operation is enabled when any reminder time divided according to the event reminder time description information of any event execution plan in the enabled state is reached. The terminal 102 may be, but not limited to, various desktop computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices, where the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. Theserver 104 may be implemented as a stand-alone server or as a server cluster or cloud server composed of a plurality of servers.

In some embodiments, as shown in fig. 2, an event reminding method is provided, where this embodiment is exemplified by applying the method to the terminal 102 in fig. 1, it is understood that the method may also be applied to a server, and may also be applied to a system including a terminal and a server, and implemented through interaction between the terminal and the server. In this embodiment, the method includes the steps of:

step 202, when event description information exists, displaying an event execution plan of at least one to-be-confirmed state adapted to the event description information; the event description information has an item name matched with the item identification in the event execution plan, and the event reminding time description information corresponding to the item identification in the event execution plan is matched with the event execution time description information of the item name in the event description information.

Specifically, when there is event description information, the terminal may acquire at least one event execution plan automatically generated according to the event description information, and since the event execution plan is automatically generated according to the event description information, there is an item name matching with an item identification in the event execution plan in the event description information, and event reminding time description information corresponding to the item identification in the event execution plan matches with event execution time description information of the item name in the event description information, the at least one event execution plan acquired by the terminal is not enabled at this time and is in a state to be confirmed, and the terminal may display the event execution plans, so that the user can enable the event execution plans through an interaction operation with the terminal.

In some specific embodiments, one event execution plan is for one item, and when there are a plurality of item names in the event description information, for each item name, an event execution plan corresponding to the item described by the item name is generated. It will be appreciated that in other embodiments, an event execution plan may be generated for two or more items, i.e., multiple items together.

In some specific embodiments, an application capable of providing a reminding service may be installed on the terminal, and the application may receive an event description picture uploaded by a user, automatically identify the event description picture to obtain item description information and event execution description information in the event description picture, and generate an event execution plan of at least one to-be-confirmed state adapted to the event description picture according to an item name in the item description information and the event execution time description information in the event execution description information. Alternatively, the application that can provide the alert service may be a native application running in an operating system, and the native application may be any one of a communication application, a file management application, a mail application, a shopping application, a map application, a game application, or the like; the application that can provide the alert service may also be a sub-application, i.e. an application running in a native application, which may specifically be an applet.

In some specific embodiments, the medication description information may be an electronic prescription stored in a server, the server may automatically generate a medication plan according to the electronic prescription, and when the user needs to start the medication reminder, the medication plan corresponding to the electronic prescription may be acquired from the server through the terminal.

In some specific embodiments, when the user edits the medicine name editing item in the editing item, the terminal may display a medicine selection page, and when the user inputs a part of the content of the medicine name in the medicine selection page, the terminal may search from the medicine database according to the medicine name and display candidate medicine names matched with the part of the content, and the terminal may further respond to a selection operation of the user on one of the candidate medicine names, and use the candidate medicine name acted by the selection operation as the editing content of the medicine name editing item, and since the user does not need to input the complete medicine name, interaction efficiency in the editing process may be improved.

In some specific embodiments, after displaying the event execution plan of the at least one to-be-confirmed state adapted to the event description information, the terminal may respond to a deletion operation of the execution plan for any event, delete the event execution plan for which the deletion operation is directed, and after deleting, the event execution plan is no longer displayed and no longer triggers an event reminder. For example, with continued reference to fig. 3, when the "delete" button displayed in the medicationintake plan card 304 in fig. 3 is clicked, the medicationintake plan card 304 may be deleted.

In step 204, in response to the enabling trigger operation of the event execution plan for any one of the pending states, the event execution plan for which the enabling trigger operation is directed is displayed as being in the enabled state.

Wherein, the triggering operation is a preset operation for enabling the triggering control. The preset operation may specifically be a touch operation, a cursor operation, a key operation, or a voice operation. The touch operation can be a touch click operation, a touch press operation or a touch slide operation, and the touch operation can be a single-point touch operation or a multi-point touch operation; the cursor operation may be an operation of controlling the cursor to click or an operation of controlling the cursor to press; the key operation may be a virtual key operation or a physical key operation, etc.

Specifically, the user may perform an enabling trigger operation for an enabling trigger control of any one of the at least one event execution plan of the state to be confirmed, and the terminal may display the event execution plan for which the enabling trigger operation is directed as being in an enabled state in response to the enabling trigger operation.

In some specific embodiments, each event execution plan may correspond to an enabling trigger control, and when the terminal receives a preset operation acting on a certain enabling trigger control, the event execution plan corresponding to the enabling trigger control is displayed as being in an enabled state. For example, with continued reference to fig. 3, two different medicines, such as XX injection and XX ointment, in fig. 3 are respectively displayed in different medicine taking plan cards, an "open reminder" button is displayed in each medicine taking plan card, the "open reminder" button is an enabling trigger control, and when a user clicks any one of the "open reminder" buttons, a medicine taking plan in the card where the "open reminder" button is located is displayed in an enabled state. In other embodiments, the event execution plan interaction page may display only one enabling trigger control, the terminal may display the event execution plan selected by the selection operation as being in an enabled state in response to the selection operation of the one or more event execution plans and the preset operation of the enabling trigger control, and the enabling of the plurality of event execution plans is controlled by the one enabling trigger control, so that interaction efficiency may be improved.

In some specific embodiments, the event execution plan for which the trigger operation is enabled may be the original event execution plan displayed by the terminal, for example, as shown in fig. 3, when the user clicks the "on reminder" button in themedication plan card 304, the terminal displays the medication plan displayed by the medication plan card in an enabled state in response to the click operation. In other embodiments, the event execution plan for which the trigger operation is enabled may be an event execution plan after editing the original event execution plan, i.e., the displayed event execution plan may be edited first, and then the trigger operation is enabled for the edited event execution plan.

In some specific embodiments, the manner in which the terminal displays the event execution plan to be confirmed may specifically be that the event execution plan to be confirmed marks a "to confirm" tag, so that the event execution plan for which the trigger operation is enabled is displayed as being in an enabled state, and may specifically be that the "to confirm" tag of the event execution plan for which the trigger operation is enabled is updated to be an "enabled" tag.

Step 206, triggering the event reminder corresponding to the event execution plan reaching the reminder time when reaching any reminder time divided according to the event reminder time description information of any event execution plan in the enabled state.

The reminding time divided according to the event reminding time description information can be one or more. The reminding time can be a time point, for example, the reminding frequency of taking medicine is twice in 1 day, and the reminding time divided according to the reminding frequency of taking medicine can be 09:00 and 21:00; the reminding time can also be a time period, for example, the reminding frequency of taking medicine is twice in 1 day, the reminding time divided according to the reminding frequency of taking medicine can be 08:55 to 09:00 and 20:55 to 21:00, and for example, the meeting reminding time is 10:00, the reminding time divided according to the meeting reminding time can be 09:55 to 10:00, in this case, the reminding in advance can be realized for the time point set by the user, and therefore, sufficient preparation time for taking medicine can be reserved for the user. It can be appreciated that the reminder time divided according to the event reminder time description information can be divided by user specification or by default.

Specifically, when any reminding time divided according to the event reminding time description information of any event execution plan in the enabled state is reached, the terminal can trigger the event reminding corresponding to the event execution plan reaching the reminding time. It will be appreciated that different event reminders are triggered for different events, for example, for taking a medication, a medication reminder is triggered, and for sending a mail, a mail sending reminder is triggered.

In a specific application, the reminding mode of the triggered event reminding can comprise one or more of telephone reminding, short message reminding or message reminding.

As can be seen from the above embodiments, in the event reminding method of the present application, when event description information exists, an event execution plan of a to-be-confirmed state adapted to the event description information can be displayed, and the following embodiments further describe a specific implementation process of the event execution plan of the to-be-confirmed state.

In some embodiments, when there is event description information, displaying an event execution plan of at least one to-be-confirmed state adapted to the event description information, including: when the event description information exists, displaying an event execution plan display entry adapted to the event description information; and in response to a trigger operation of the display portal for the event execution plan, displaying the event execution plan of at least one to-be-confirmed state adapted to the event description information.

The event execution plan display entry is an entry capable of responding to a trigger operation to display an event execution plan adapted to the event description information, and specifically may be event execution plan display prompt information or a trigger control. The event execution plan display prompt information is information capable of prompting the user to perform a trigger operation, and may include one or more of text prompt information, voice prompt information, or picture prompt information, for example, the event execution plan display prompt information may be "click jump to medicine taking plan display page". The triggering control is a visualized element and has a function of executing or triggering code running and completing response by responding to user operation, and the triggering control can be a button, for example, any one of a click button, a sliding button, a pressing button and the like; the trigger control may also be a single box or a set of options. The triggering operation for the event execution plan display portal refers to a preset operation for triggering the event execution plan display portal, and specifically may be any one or more types of operation such as a touch operation, a cursor operation, a key operation, a voice operation, and a gesture operation.

Specifically, when the event description information exists, the terminal may display an event execution plan display entry adapted to the event description information, and the user may trigger the event execution plan display entry to generate a trigger operation, so that the terminal may obtain an event execution plan automatically generated according to the event description information in response to the trigger operation, and display the event execution plans in a state to be confirmed.

In the above embodiment, when the event description information exists, the event execution plan display entry adapted to the event description information may be displayed, and the user may trigger the event execution plan display entry to display the event execution plan, thereby improving convenience of displaying the event execution plan.

In some embodiments, when event description information exists, displaying an event execution plan display portal adapted to the event description information, including: when generating event description information belonging to a logged-in user account, responding to a notification event for the event description information, and displaying a notification message card for the event description information; and displaying the notification message content indicated by the notification event in the notification message card, and displaying an event execution plan display entry matched with the event description information.

In this embodiment, an application capable of providing a reminder service is installed on a terminal, the application logs in with a user account, event description information belongs to the logged in user account, when event description information is generated, a notification message for the event description information may be further generated, the notification message may trigger a notification event in the application logged in by the user account, further the terminal may respond to the notification event, display a notification message card for the event description information, in the notification message card, display a notification message content indicated by the notification event, and in the notification message card, may also display an event execution plan display entry adapted to the event description information.

In some specific embodiments, the notification message is generated by a server corresponding to the application, that is, when the server detects the event description information belonging to the logged-in user account, the server may automatically generate at least one adapted event execution plan according to the event description information, and may further send a reminder message to the terminal, where the reminder message triggers a notification event in the application of the terminal, so that the terminal may display a notification message card in response to the notification event. For example, referring to fig. 4, a schematic diagram of a notification message card in some specific embodiments is shown, in which the event description information is an electronic prescription, and is generated after the user makes an online inquiry at a terminal, and a title, an inquiry doctor, a reminder content, a prompt description, and a medicationplan display portal 402 are displayed in the notification message card displayed by the terminal, where the medication plan display portal displays the prompt information as a medication plan display portal, and when the user clicks the medicationplan display portal 402, the user can jump to a medication plan interaction page, and the medication plan interaction page may refer to fig. 3, for example.

In the above embodiment, since the event execution plan display entry can be displayed in the notification message card, the event execution plan can be ensured to be displayed in time at the terminal, so that the situation that the user forgets to start the event execution plan is avoided, and the effectiveness of event reminding is ensured.

In some embodiments, the event reminder is a medication reminder; when the event description information exists, displaying an event execution plan display entry adapted to the event description information, comprising: a conversation page for conversation between the logged-in user account and the service account is used for displaying a medicine taking description information message card for browsing the medicine taking description information when the service account triggers the medicine taking description information aiming at the user account; and displaying a medicine taking plan display entrance matched with the medicine taking description information corresponding to the medicine taking description information message card.

The service account is an account for serving a user account to generate medication description information, and the service account may be a doctor account, for example. The medicine taking description information message card refers to a message card for displaying medicine taking description information, and the message card can respond to triggering operation to display specific content of the medicine taking description information, so that a user can browse the medicine taking description information corresponding to the message card.

Specifically, the terminal is provided with an application capable of providing a reminding service, the application logs in with a user account, through the user account, the terminal can establish session connection with the service account to trigger the service account to generate medicine taking description information, the medicine taking description information can be sent to the terminal through the established session connection in a session message mode, after the terminal receives the session message, the medicine taking description information message can be displayed in a message card of a session page corresponding to the session connection, and in the session page, a medicine taking plan display inlet can be displayed at a position corresponding to the medicine taking description information message card.

For example, as shown in fig. 5, which is a schematic diagram of a session page with a service account in some specific embodiments, it can be seen from fig. 5 that a user logs in through a user account of a terminal to perform a session with a doctor account, so that the terminal can receive an electronic prescription sent by the doctor account, the electronic prescription is displayed in amessage card 502 of the session page, when the user clicks a "view electronic prescription" button, the user can browse the detailed content of the electronic prescription, a medicationplan display entry 504 is displayed corresponding to themessage card 502, and when the user clicks the medication plan display entry, a medication plan interaction page corresponding to the electronic prescription can be displayed, for example, refer to fig. 3.

In the above embodiment, the administration description information is displayed in the message card of the session interface, and the administration plan display portal adapted to the administration description information may also be displayed, so that the user may conveniently and rapidly trigger the display of the administration plan, and the convenience of displaying the administration plan is improved.

The above embodiments introduce a specific procedure for displaying an event execution plan, and after the event execution plan is displayed, the event execution plan may be enabled, so that an event reminder may be further triggered. It should be noted that, in other embodiments of the present application, to further ensure that the user can execute the event on time, when the reminding time is reached, an event execution confirmation function may also be provided, through which the user may "punch a card" through the event execution confirmation function, and the following embodiments will describe the event execution confirmation function.

In some embodiments, the event alert method further comprises: when any reminding time divided according to the event reminding time description information of any event execution plan in the enabled state is reached, displaying an event execution confirmation page corresponding to the event execution plan reaching the reminding time, and displaying an event execution confirmation mark in a to-be-executed state on the event execution confirmation page; in response to a trigger operation for the event execution validation token, the state of the event execution validation token is updated to an executed state.

The event execution confirmation mark refers to a mark capable of updating an execution state in response to a trigger operation, and the event execution confirmation mark can be a control in various forms.

Specifically, when any reminder time divided according to the event reminder time description information of the event execution plan in the enabled state is reached, the terminal may display an event execution confirmation page corresponding to the event execution plan reaching the reminder time, in which event execution confirmation page may display item information corresponding to item target identities in the event execution plan, and in the case of a drug, the drug information corresponding to the drug identity may be one or more of a name of the item, a usage amount, an attention event when taking the drug, and the like, corresponding to the item information, and may display an event execution confirmation flag whose initial state is a state to be executed, the state to be executed indicating that the user has not performed event execution confirmation, and when the user performs a trigger operation for the event execution confirmation flag, the terminal may update the state of the event execution confirmation flag to be an executed state in response to the trigger operation, the executed state indicating that the user has performed event execution confirmation.

For example, referring to fig. 6, in some embodiments, the event execution confirmation page is specifically a medication confirmation page, the event execution confirmation mark is specifically a medication confirmation mark, the medication confirmation mark in the state to be taken is atrigger control 602 in fig. 6 (a), after the terminal responds to the clicking operation on 602, thetrigger control 602 is updated to be in the state of being taken, and thetrigger control 604 is displayed as atrigger control 604 in fig. 6 (b).

In some specific embodiments, the medication confirmation page may also display other medication notes. With continued reference to fig. 6, the medication confirmation page may also display the notes for each medication as well as for pregnant women.

In some specific embodiments, the medication confirmation page may also display statistics related to the user medication confirmation, which may specifically be the total number of times and the duration of the medication confirmation. With continued reference to fig. 6 (a), the position corresponding to thetrigger control 602 in the medication confirmation page may also display "you have taken medicine for 3 days, and accumulated for 5 times of punching a card", and after the user clicks thetrigger control 602, the statistical information related to medication confirmation is updated, and in fig. 6 (b), the statistical information is updated to "you have taken medicine for 3 days, and accumulated for 6 times of punching a card".

In the above embodiment, by displaying the event execution confirmation flag in the to-be-executed state on the event execution confirmation page, the terminal may update the state of the event execution confirmation flag to the executed state in response to the trigger operation for the event execution confirmation flag, thereby improving the effectiveness of event reminding.

In some embodiments, the enabled state event execution plan is displayed on an event execution plan interaction page; displaying an event execution confirmation page corresponding to the event execution plan reaching the reminding time, comprising: displaying an event execution confirmation entry corresponding to the event execution plan reaching the reminding time in the event execution plan interaction page; and in response to the triggering operation of the event execution confirmation entry, displaying an event execution confirmation page corresponding to the event execution plan reaching the reminding time.

In the above embodiment, the event execution confirmation page may be conveniently and quickly entered by displaying the event execution confirmation entry in the event execution plan interaction page, so as to improve interaction efficiency in the medicine taking confirmation process.

In the above embodiment, the event execution plan and the event execution plan entry are displayed in the same card, so that the user can better perceive the event execution confirmation entry for the event execution plan, and thus, the user can accurately enter the event execution confirmation page corresponding to the event execution plan through the event execution confirmation entry, thereby improving the accuracy of medication confirmation.

In some embodiments, displaying an event execution confirmation page corresponding to an event execution plan that reaches a reminder time includes: displaying prompt information of event reminding; responding to the checking operation of the prompt information, and displaying a prompt message card for prompting the event; displaying the reminding message content of event reminding in a reminding message card, and displaying an event execution confirmation entry corresponding to an event execution plan reaching reminding time; and in response to the triggering operation of the event execution confirmation entry, displaying an event execution confirmation page corresponding to the event execution plan reaching the reminding time.

The prompting message of the event prompt refers to information prompting that the event prompt is received, and the event prompt refers to prompting message, namely the event prompt is presented in a prompting message mode. The prompt may be of various types, for example, may be one or more of a text prompt, a voice prompt, or a picture prompt. In a specific application, when an application capable of providing a reminding service is installed on a terminal and the application logs in a user account, a server corresponding to the application can send a reminding message of event reminding to the terminal logged in by the user account, and in this case, the reminding message is used for reminding a user that the reminding message of event reminding has been received.

Specifically, when any reminding time divided according to the event reminding time description information of any event execution plan in the enabled state is reached, the terminal can receive a reminding message, the reminding message can trigger the terminal to display reminding information, the reminding information prompts a user to check the received reminding message, when the user checks the reminding information displayed by the terminal, the terminal can respond to the checking operation to display a reminding message card, in the reminding message card, the reminding message content of event reminding can be displayed, the reminding message content can comprise one or more of information such as item identification, event execution time and reminding description in the event execution plan reaching the reminding time, in the reminding message card, an event execution confirmation entry corresponding to the event execution plan reaching the reminding time can be displayed, and further when the user performs triggering operation on the event execution confirmation entry, the terminal can respond to the triggering operation to display an event execution confirmation page corresponding to the event execution plan reaching the reminding time.

For example, referring to fig. 8, in order to display a page schematic diagram of a prompt message, where "medication reminding notification" is a prompt message of an event reminder, when a user clicks on the prompt message to view, the terminal may continue to display a reminder message card, such as the page shown in fig. 9, in order to display a page schematic diagram of the reminder message card, one or more reminder message cards may be displayed in the page, for example 902 in fig. 9, and a medication confirmation entry is displayed in the reminder message card, for example 904 in fig. 9.

In the embodiment, the event execution confirmation entrance can be displayed in the notification message card, so that the user can be timely reminded of carrying out event execution confirmation, the effectiveness of event reminding is further ensured, the user can conveniently and rapidly enter the event execution confirmation page, and the interaction efficiency in the event execution confirmation process is improved.

In some embodiments, the event reminder is a medication reminder and the event execution plan is a medication plan; when reaching any reminding time divided according to the event reminding time description information of any event execution plan in the enabled state, displaying an event execution confirmation page corresponding to the event execution plan reaching the reminding time, and displaying an event execution confirmation mark in the to-be-executed state on the event execution confirmation page, wherein the method comprises the following steps: when a plurality of started medicine taking plans exist and the same reminding time divided according to the medicine taking reminding frequency of each of the plurality of started medicine taking plans is reached, displaying a medicine taking confirmation page commonly corresponding to the plurality of started medicine taking plans; in the medicine taking confirmation page, medicine identifications corresponding to the medicine taking plans in the started states are displayed; in the medication confirmation page, one medication confirmation mark for simultaneous medication confirmation for a plurality of medication plans in the enabled state is displayed.

The same reminding time divided according to the respective taking reminding frequency of the taking plans in the activated state means that the same reminding time exists among the taking plans in the activated state, for example, one reminding time divided according to the taking reminding frequency of the taking plan A is 9:00, if the one reminding time divided according to the taking reminding frequency of the taking plan B is 9:00, the same reminding time exists between the taking plan A and the taking plan B, and the same reminding time is 9:00.

Specifically, when there are a plurality of taking plans in an enabled state and the same reminding time divided according to the taking reminding frequency of each of the taking plans in the enabled state is reached, the terminal can display the medicine identifications of the taking plans on the same taking confirmation page and control the taking confirmation of the taking plans by using the same taking confirmation mark, and when the user triggers the taking confirmation mark, the taking confirmation can be simultaneously performed on the taking plans corresponding to all the taking identifications displayed in the page. For example, referring to fig. 10, which is a schematic diagram of a medication confirmation page in some embodiments, as can be seen in fig. 10, where two medications are displayed, when the user clicks the medication punching button in fig. 10, the corresponding medication plans of the two medications shown in fig. 10 can be simultaneously punched and confirmed.

In some specific embodiments, when the medication identifier corresponding to each of the plurality of medication plans is displayed in the medication confirmation page, a selection control may be further displayed for each medication identifier, and the terminal may perform medication confirmation on the medication plan corresponding to the medication identifier selected by the selection operation in response to a selection operation triggered by the user through the selection control and a triggering operation on the medication confirmation mark. Further, for a drug identifier not selected by the user, the terminal may trigger a delayed reminder for a medication plan corresponding to the drug identifier, for example, after a preset time, such as 5 minutes, the medication reminder may be performed again.

In the embodiment, the medicine identifiers of the plurality of medicine taking reminding plans are displayed in one page, and the plurality of medicine taking plans are checked and confirmed through the same medicine taking confirmation identifier, so that the interaction efficiency when medicine taking and checking are performed on the plurality of medicine taking plans can be improved, and the operation resources of the terminal in the checking and confirming process can be saved.

In some embodiments, displaying a medication confirmation page that collectively corresponds to a plurality of enabled medication schedules includes: displaying medication confirmation entries corresponding to each of the plurality of activated medication schedules; in response to a trigger operation for any one of the displayed medication confirmation portals, a medication confirmation page commonly corresponding to the plurality of activated-state medication plans is displayed.

Specifically, when there are a plurality of medication plans in an enabled state and the same reminder time divided according to the medication reminder frequency of each of the medication plans in the plurality of enabled states is reached, for each of the medication plans, the terminal may display a medication confirmation entry corresponding thereto, when a user performs a trigger operation for any one of the medication confirmation entries, the terminal may display a medication confirmation page in response to the trigger operation, and in the displayed medication confirmation page, display the medication identifications in the medication plans corresponding to all of the medication confirmation entries. For example, with continued reference to fig. 9, two reminder message cards 902 and 906 are shown in fig. 9, where the two reminder cards respectively display

medication confirmation entries

904 and 908 corresponding to different medication plans, and a user clicks any one of the entries to enter a medication confirmation page as shown in fig. 10, so that medication identifiers in the medication plans corresponding to the reminder cards 902 and 906 can be displayed in the page at the same time, so that the user can confirm that the two medication plans are simultaneously taken.

In the above embodiment, when the user performs the triggering operation for any one of the plurality of medication confirmation portals, the medication confirmation page corresponding to the medication plans together may be displayed, so that the interaction efficiency in the medication confirmation process may be improved.

In some embodiments, the enabled event execution plan is displayed in an event execution plan display area in an event execution plan interaction page, the event execution plan interaction page including a plurality of options capable of being in a selected state in response to a selection operation, the enabled event execution plan displayed in the event execution plan display area conforming to a filter condition corresponding to the option in the selected state among the plurality of options.

The event execution plan display area in the event execution plan interaction page refers to an area for displaying an event execution plan in the event execution plan interaction page, and a plurality of options can be displayed outside the event execution plan display area, each option can respond to a selected operation to be in a selected state, and each option corresponds to a screening condition used for screening the event execution plan from the event execution plan set. The options in the event execution plan interaction page can be customized according to service requirements, specifically can include options with screening conditions for defining reminding time, for example, the options can be "today's medication", "week's medication", the options can also include options with screening conditions for defining user requirements, for example, "collection medication", "all medications", and of course, other customized options can also be included.

In a specific application, the terminal may switch the event execution plan displayed in the event execution plan display area to an event execution plan satisfying the screening condition corresponding to the option selected by the selected operation in response to the selected operation for any option.

In some embodiments, the plurality of options includes at least a first option and a second option; the screening conditions corresponding to the first options are used for determining event execution plan sets corresponding to logged-in user accounts; and screening the event execution plan with the enabled state of the reminding time in the specified period from the event execution plan set according to the screening condition corresponding to the second option.

For example, referring to fig. 3, the event execution plan interaction page displays two options of "all medications" and "today's medications", and in fig. 3, all the medications of the user may be displayed in the page, when the user clicks the "today's medications" option, the medications that the user needs to remind for taking the medications today may be displayed, referring to fig. 11, a page diagram corresponding to the today's medications may be shown, and when the "today's medications" option is in the selected state, only the medications that need to remind today are displayed in the medications plan display area.

In some specific embodiments, when the second option is in the selected state and the event execution plan display area displays the event execution plans of which the reminder time is in the enabled state within the specified period, the terminal may further increase the size of the event execution plan card displayed by the event execution plan to increase the display area for displaying the event execution confirmation entry in response to reaching the reminder time of any one of the displayed event execution plans, and display the event execution confirmation entry corresponding to the event execution plan reaching the reminder time in the increased display area. For example, with continued reference to FIG. 11, when the "present medication" option is in the selected state, and the reminder time 16 for the medication plan in the medication plan card 1102 is reached; 34, a "medication confirmation" button as a medication confirmation portal may be added to the medication plan card 1102.

In the above embodiment, by displaying the option of the user screening the event execution plan in the event execution plan interaction page, the terminal may screen the event execution plan for display in response to the selection operation of the option by the user, so as to facilitate the management of the event execution plan by the user and improve the interaction efficiency of the event execution plan.

As can be seen from the foregoing embodiments, when there is event description information, the terminal may display at least one event execution plan of a to-be-confirmed state adapted to the event description information, when the event execution plan of any one to-be-confirmed state is updated from the to-be-confirmed state to the enabled state, the terminal may perform event reminding according to the event execution plan, in this case, the event reminding time description information of the event execution plan is matched with the event execution time description information in the event description information by default, and the reminding time divided according to the event reminding time description information is a preset fixed time, for example, three taking reminding times may be preset for three taking reminding frequencies of 1 day, namely, 9:00, 15:00 and 21:00, respectively, so that for any one taking reminding frequency of 1 day, taking reminding times are all the three times, which may not meet the requirement of the user, and cause the event reminding to become invalid, so the present application also provides the function of editing the event execution plan, for example, the following embodiments will introduce editing the event execution plan.

In some embodiments, in response to an enabling trigger operation of an event execution plan for any of the to-be-confirmed states, displaying the event execution plan for which the enabling trigger operation is directed as being in an enabled state, comprising: responding to the editing triggering operation of the event execution plan aiming at any state to be confirmed, entering an event execution plan editing page, and displaying at least one editing item of the event execution plan aiming at the editing triggering operation in the event execution plan editing page; displaying editing contents of the editing operation in response to the editing operation for any one of the at least one editing item; in response to an enabling trigger operation for an event execution plan containing editing content, the event execution plan for which the trigger operation is enabled is displayed in an enabled state.

Specifically, when the user performs an edit triggering operation for an event execution plan of any one state to be confirmed, an event execution plan editing page may be entered in which the event execution plan may be edited. The event execution plan editing page includes a plurality of editing items, each of which may correspond to different contents in the event execution plan, taking a medication plan as an example, and the editing items may include one or more of a medication reminding frequency, a medication name, a reminding time, a reminding period duration, a dosage of each medication, a reminding start time, or the like, for example.

It can be understood that, at the beginning, all the editing items are displayed by default, that is, all the editing items such as event reminding time description information, item names, reminding time, reminding period duration and the like are displayed by default and the data matched with the related information in the event description information, for example, if the taking frequency of a certain medicine in the taking description information is three times in 1 day, entering the taking editing page, and the taking reminding frequency is three times in one day; the reminding start time defaults to the current date, for example, the current date is 3 months and 2 days, and then enters the medicine editing page, and the reminding start time defaults to 3 months and 2 days. For each of these editing items, the user may edit, after the editing is completed, an enabling trigger operation may be performed for the event execution plan including the editing content, so that the terminal may display the event execution plan in an enabled state, and thereafter, the terminal may trigger an event reminder according to the edited event execution plan.

In the above embodiment, since the event execution plan of the state to be confirmed can be edited, the event reminder can better meet the user needs, and the effectiveness of the event reminder is improved.

In some embodiments, the event reminder is a medication reminder; in response to an editing operation for any of the at least one editing item, displaying editing content of the editing operation, comprising: responding to a first editing operation aiming at a medicine taking reminding frequency editing item in at least one editing item, displaying medicine taking reminding frequency edited by the first editing operation, and displaying reminding time editing items with matched quantity corresponding to medicine taking times in a single medicine taking period appointed by the displayed medicine taking reminding frequency; and displaying the reminding time edited by the second editing operation in response to the second editing operation for the reminding time editing item.

Specifically, the reminding time is divided according to the medicine taking reminding frequency, so that the number of the medicine taking reminding times is dynamically changed according to the medicine taking reminding frequency, in this embodiment, the terminal may respond to a first editing operation for the medicine taking reminding frequency editing item in at least one editing item, display the medicine taking reminding frequency edited by the first editing operation, and follow the medicine taking times in a single medicine taking period specified by the medicine taking reminding frequency edited by the first editing operation, and may automatically dynamically display the reminding time editing item with the matched number, for example, assuming that the medicine taking reminding frequency is 1 day for two times, the terminal may display two reminding time editing items, and if the medicine taking reminding frequency is 1 day for three times, the terminal may display three reminding time editing items, so that a user may perform editing operations for the reminding time editing items to edit and obtain the reminding time.

For example, referring to fig. 12, which is a schematic diagram of a medicine taking editing page in some embodiments, the medicine taking frequency in fig. 12 is 2 times per day, so the number of displayed reminding time editing items is 2, default times of the two reminding time editing items are 09:00 and 21:00, after the two reminding time editing items can be edited by a user, after the editing is completed, when the user clicks an "open reminding" button, the terminal will remind to take medicine according to the edited time.

In the above embodiment, the terminal can automatically adjust the number of the reminding time editing items according to the medicine taking reminding frequency edited by the user, so that on one hand, the influence of the user on the interaction efficiency caused by manually adding the reminding time editing items can be avoided, and on the other hand, the interaction efficiency in the medicine taking plan editing process is improved, and on the other hand, the resource waste caused by displaying too many reminding time editing items can be avoided, so that the memory resource of the terminal is saved.

In some embodiments, the event execution plan of the at least one to-be-confirmed state is shown in a to-be-confirmed plan display area in the event execution plan interaction page; in response to an enabling trigger operation of an event execution plan for any one of the to-be-confirmed states, displaying the event execution plan for which the enabling trigger operation is directed as being in an enabled state, comprising: and in response to the enabling trigger operation of the event execution plan aiming at any to-be-confirmed state, transferring the event execution plan aimed at by the enabling trigger operation from the to-be-confirmed plan display area to an enabled plan display area in the event execution plan interaction page.

The to-be-confirmed plan display area is used for displaying the to-be-confirmed event execution plans, and when a plurality of to-be-confirmed event execution plans exist, all to-be-confirmed event execution plans can be displayed in an aggregation mode in the area. The enabled plan display area is used for displaying the event execution plans in the enabled state, and when a plurality of event execution plans in the enabled state exist, all the event execution plans in the enabled state can be displayed in an aggregation mode in the area. In particular applications, the to-be-validated plan display area may be associated with a to-be-validated tag, and the enabled plan display area may be associated with an enabled identifier.

Specifically, the state change of the event execution plan may be represented by a change of the display area, when a certain event execution plan is in a state to be confirmed, the event execution plan may be displayed in the display area of the plan to be confirmed, and when the user performs an enabling triggering operation on the event execution plan, the terminal may transfer the event execution plan from the display area of the plan to be confirmed to the enabled plan display area, so that the event execution plan is displayed in the enabled plan display area to be displayed in the enabled state.

For example, referring to fig. 3 and 13, when the "on reminder" control in the medicationintake plan card 306 of fig. 3 is clicked, the medication intake plan in the medicationintake plan card 306 is transferred from the to-be-confirmed plan display area to the enabled plan display area in fig. 13, wherein the to-be-confirmed plan display area is the display area under the "to-be-confirmed" tab and the enabled plan display area is the display area under the "enabled" tab.

In the above embodiment, the change of the state of the event execution plan is reflected by the change of the display area, so that the event execution plans in the same state are displayed in the same area in a centralized manner, which is convenient for the user to manage the event execution plans in each state, and avoids the interference of the event execution plans in other states when the event execution plans in one state are interacted, thereby improving the interaction efficiency of the event execution plans.

In some embodiments, the event descriptive information is an electronic prescription and belongs to a logged-in user account, and the event execution plan is a medication plan: the event execution plan of the at least one state to be confirmed is generated by a medication plan generation step including: acquiring an electronic prescription belonging to a user account, generating prescription information based on the electronic prescription through a producer thread, and writing the prescription information into an information queue; reading prescription information from the information queue through a consumer thread, and extracting medicine names and medicine frequency from the read prescription information; at least one medication plan is generated by the consumer thread according to the medication name and the frequency of medication administration that is compatible with the electronic prescription.

Specifically, the step of generating the medication intake plan in the embodiment of the present application may be performed by a terminal, or may be performed by a server, or may be performed by the terminal and the server together. After the server obtains the electronic prescription belonging to the user account, the producer thread can be called to generate a prescription message according to the electronic prescription and put the prescription message into a message queue, the prescription message is read from the message queue through the consumer thread, at least one medicine taking plan matched with the electronic prescription is generated according to the medicine name and the medicine taking frequency of the medicine to be taken by the user in the prescription message, the generated medicine taking plan is in a state to be confirmed at the moment, when the user performs starting triggering operation on any medicine plan, the server receives a request for starting the medicine taking plan sent by the terminal, and the server can update the state of the medicine taking plan for starting the triggering operation into the started state according to the request. The producer thread and the consumer thread of the message queue can asynchronously generate the medicine taking plan, so that the generation efficiency of the medicine taking plan is improved.

In a specific application, the message queue may be Kafka, which is a high throughput distributed publish-subscribe message system, allowing the appropriate data to appear in the appropriate form where appropriate. Kafka can enable a producer thread to add data to the tail end of a queue through a message queue, and enable a plurality of consumers to sequentially read the data from the interior of the queue and then process the data by themselves. As shown in FIG. 14, in some specific embodiments, the architecture of Kafka is shown in FIG. 14, where it can be seen that asynchronous sending of messages can be achieved by Kafka, producer threads are responsible for writing messages into Kafka clusters, producer threads do not need to pay attention to sending of messages, consumer threads read messages from Kafka clusters to send messages, kafka cluster messages can be stored in different topics, multiple partitions can be included in each topic, data of the same topic in different partitions is not repeated, and the partitions function as loads to improve throughput of Kafka.

In some specific embodiments, the specific flow of the medication schedule generating step may refer to fig. 15, specifically including the following steps:

step 1502, an electronic prescription is created.

Specifically, the user may conduct an online inquiry, and the doctor creates an electronic prescription according to the inquiry situation. When a doctor prescribes or continues a prescription to a user, information to be acquired is classified into user information and drug information. The user information includes information of the name, age, disease diagnosis result, and the like of the user. The medicine information records all data of prescription medicines, including the name, function description, specification number, usage amount, orders and the like. Referring to fig. 16, in some embodiments, a page view of the prescription contents is filled out by a doctor, and when the doctor clicks the "ok and send" button in fig. 16, the electronic prescription may be submitted, at which point the creation of the electronic prescription is completed.

The user information and the medication information may be stored in a database. Considering that the two information categories are different in data scale, read-write frequency, data updating mode and other dimensions, the two information categories can be analyzed and compared in each dimension according to the actual service condition, and a proper database is selected for storage. Aiming at the medicine information, considering that the quantity and scale of the medicine information are relatively fixed, the information such as the type increase of prescription medicines, the usage amount of medicines, function description and the like is less changed, and the conventional mysql data instance on public cloud can be selected. For user information, a highly reliable DBMS database can be selected and a cache database can be used to improve the operational performance of the data, considering that the number of users will continue to increase.

Step 1504, determining whether the electronic prescription passes the audit, if so, enteringstep 1506, and if not, reenteringstep 1502.

Atstep 1506, the producer thread encrypts the prescription content to generate a prescription message.

Instep 1508, the consumer thread consumes the prescription message.

Specifically, the electronic prescription created by the doctor enters an auditing stage, and if the auditing is passed, the electronic prescription carries an identification field which is passed by the auditing, so that the electronic prescription can produce a message through kafka and put in a message queue of a publishing and subscribing mode. There are three messaging mechanisms for kafka messaging, simple messaging, synchronous messaging and asynchronous messaging. Considering that a scene that a plurality of users ask for a plurality of doctors at the same time exists, if the synchronous message transmission is carried out, only one message can be transmitted at the same time, so that a plurality of messages cannot be directly transmitted, the messages are delayed, and the benefit cannot be maximized, in the implementation of the application, a mechanism for asynchronously transmitting the messages can be selected, namely, prescription information is generated by encrypting prescription contents of the electronic prescription through a producer thread and written into a message queue of kafka, and the prescription information is asynchronously read from the message queue through a consumer thread.

In a specific application, when prescription information is produced to kafka, personal information, disease information and drug information of a user are recorded in prescription content, and the prescription information belongs to user privacy data, so that the prescription information is encrypted and then put into a message queue, and the security of the user privacy data is protected. The encryption mode can adopt AES (Advanced Encryption Standard) algorithm to encrypt, the flow of AES encryption algorithm can refer to FIG. 17, the encryption process comprises a plurality of rounds, and one round of encryption can comprise 4 operations: byte substitution, row displacement, column mixing, round key addition, wherein: the byte substitution is to replace each byte with the corresponding byte by a non-linear replacement function in a lookup table manner; the row displacement is to circularly shift each row in the matrix; column blending can fully blend the operations of the individual columns in the matrix, in particular linear conversion can be used to blend the four bytes of each column; round key addition is a bitwise exclusive-or operation of each byte in the matrix with the round key.

The AES implementation modes mainly have five kinds: 1. the second Cipher block chaining mode can be used for encryption in the embodiment of the application, encryption can be realized by introducing two packages of 'crypto/aes' and 'crypto/Cipher', encryption can be realized by only transmitting plaintext and key to an encryption function, and similarly, decryption can be realized by only transmitting ciphertext and key to a decryption function and storing the key in a configuration management mode.

Step 1510, it is determined whether the prescription corresponding to the prescription message passes the audit, if so,step 1512 is entered, and if not,step 1510 is entered.

Atstep 1512, the prescription message is marked as processed.

Atstep 1514, the prescription message is decrypted to generate a medication schedule.

Step 1516, a notification message is sent prompting the start of the medication schedule.

Specifically, after the encrypted prescription message is sent to the message queue, the consumer thread can acquire the prescription message from the message queue, and after decrypting by using the AES algorithm, judge whether the prescription audits the identification field, and when the prescription passes the audit, generate a medicine taking plan of the user according to the user information and the medicine taking information in the prescription message, wherein the state is not started, namely the state to be confirmed. And simultaneously creating a notification message to be sent, wherein the sending time of the notification message can be 24 hours, and the notification message triggers a notification event at the terminal to remind a user to start a medicine taking reminder.

In the above embodiment, since the medication plan is asynchronously generated through the message queue and the prescription message is encrypted, the medication plan generation efficiency can be improved while the data security is improved.

In some embodiments, the alert information for the event alert is generated by an alert information generating step comprising: when the reminding time divided according to the event reminding time description information of any event execution plan in the enabled state is reached, writing a reminding message generated according to the event execution plan reaching the reminding time into a reminding message data table through a first timing task; traversing the reminding message in the reminding message data table through the second timing task; triggering and generating prompt information corresponding to the prompt messages aiming at each traversed prompt message.

Specifically, in the embodiment of the present application, the event execution plan generating step may be executed by a terminal, may be executed by a server, or may be executed by both the terminal and the server. In this embodiment of the present application, the server may set two timing tasks, write, by using the first timing task, a reminder message generated according to an event execution plan that reaches a reminder time into a reminder message data table, traverse, by using the second timing task, the reminder message in the reminder message data table, and trigger, by using the traversed reminder message, generation of reminder information corresponding to the reminder message.

In the embodiment, the two timing tasks are set to trigger the generation of the prompt information, and the two timing tasks are coordinated to cooperate with each other, so that the generation efficiency of the prompt information can be improved.

In some embodiments, the event reminder is a medication reminder, the event execution plan is a medication plan, and the enabled medication plan is stored in a medication plan data table; writing the reminding message generated according to the event execution plan reaching the reminding time into a reminding message data table through a first timing task, wherein the method comprises the following steps: traversing the medicine taking plan in the started state in the medicine taking plan data table through the first timing task; inquiring the reminding time of the traversed medicine taking plan from a reminding time data table associated with the medicine taking plan data table through a first timing task aiming at each traversed medicine taking plan; when any one of the inquired reminding time is reached, a reminding message is generated according to the traversed medicine taking plan through the first timing task and is written into a reminding message data table.

Specifically, considering that a plurality of reminding times may exist in the same medicine taking plan, in the embodiment of the present application, the medicine taking plan and the reminding time may be stored in association with each other, the medicine taking plan is stored in the medicine taking plan data table, the reminding time corresponding to the medicine taking plan is stored in the reminding time data table, so that the repeated storage of the content of the same medicine taking plan may be avoided, and storage resources in the database are saved.

In some specific embodiments, as shown in fig. 19, an event reminding method is provided, where this embodiment is exemplified by applying the method to the terminal 102 in fig. 1, it is understood that the method may also be applied to a server, and may also be applied to a system including a terminal and a server, and implemented through interaction between the terminal and the server. In this embodiment, the method includes the steps of:

in step 1902, when generating event description information pertaining to a logged-in user account, a notification message card for the event description information is displayed in response to a notification event for the event description information.

The event may be any event that needs to trigger an event reminder, such as taking a medicine, taking a meeting, making a call, visiting a client, sending a mail, or taking an express, etc. In different events, different items are involved, e.g. medication administration events relate to medications, meeting events relate to meetings.

In step 1904, in the notification message card, the notification message content indicated by the notification event is displayed, and an event execution plan display entry adapted to the event description information is displayed.

The event description information is provided with an item name matched with an item identification in the event execution plan, and the event reminding time description information corresponding to the item identification in the event execution plan is matched with the event execution time description information of the item name in the event description information.

In step 1906, in response to a trigger operation for the event execution plan display portal, an event execution plan of at least one to-be-confirmed state adapted to the event description information is displayed.

The event execution plan of at least one state to be confirmed is displayed in a display area of the plan to be confirmed in the event execution plan interaction page.

In step 1908, in response to the enabling trigger operation of the event execution plan for any one of the to-be-confirmed states, the event execution plan for which the enabling trigger operation is directed is transferred from the to-be-confirmed plan display area to the enabled plan display area in the event execution plan interaction page to display the event execution plan for which the enabling trigger operation is directed as being in the enabled state.

In a specific application, the terminal may further enter an event execution plan editing page in response to an editing trigger operation of the event execution plan for any state to be confirmed, display at least one editing item of the event execution plan for which the editing trigger operation is directed in the event execution plan editing page, display editing contents of the editing operation in response to an editing operation of any one of the at least one editing item, and further may respond to an enabling trigger operation of the event execution plan for which the editing contents are included.

Step 1910, triggering an event reminder corresponding to the event execution plan reaching the reminder time when reaching any reminder time divided according to the event reminder time description information of any event execution plan in the enabled state.

In a specific application, the event reminder triggered by the terminal at least includes a message reminder, that is, when any reminder time divided according to the event reminder time description information of any event execution plan in an enabled state is reached, the terminal can receive a reminder message sent by the server.

Further, when any reminding time divided according to the event reminding time description information of any event execution plan in the enabled state is reached, the terminal may display an event execution confirmation entry corresponding to the event execution plan reaching the reminding time, in this embodiment of the present application, the event execution confirmation entry may be displayed by the following steps 1912 to 1916, on the one hand, and the event execution confirmation entry may be displayed by the following steps 1918 to 1922, on the other hand.

Step 1912, displaying the event execution plan interaction page, and displaying each enabled event execution plan in each event execution plan card in the event execution plan display area of the event execution plan interaction page.

In a specific application, the event execution plan card is displayed in an event execution plan display area in an event execution plan interaction page, the event execution plan interaction page comprises a plurality of options which can respond to a selected operation to be in a selected state, and the event execution plan in an enabled state displayed in the event execution plan display area accords with screening conditions corresponding to the options in the selected state in the plurality of options.

At step 1914, the size of the event execution plan card that reaches the reminder time is increased to increase the display area for displaying the event execution confirmation entry.

The event execution confirmation entry is an entry capable of responding to a trigger operation to display an event execution confirmation page, and specifically may be a prompt message or a trigger control.

In step 1916, an event execution confirmation entry corresponding to the event execution plan that reaches the reminder time is displayed in the added display area.

Specifically, the size of the increased size of the event execution plan card may be set according to actual needs, and a display area for displaying the event execution confirmation entry may be increased in the event execution plan card by the size increase, and then one event execution confirmation entry is displayed in the increased display area.

At step 1918, a reminder of the event reminder is displayed.

Specifically, when any reminding time divided according to the event reminding time description information of any event execution plan in the enabled state is reached, the terminal can also display the reminding information of the event reminding.

In step 1920, a reminder message card for the event reminder is displayed in response to the viewing operation for the reminder information.

In step 1922, the reminder message content of the event reminder is displayed in the reminder message card, and an event execution acknowledgment entry corresponding to the event execution plan for the reminder time is displayed.

The reminding message content can comprise one or more of information such as item identification, event execution time, prompt description and the like in the event execution plan reaching the reminding time.

In step 1924, in response to the trigger operation for the event execution confirmation entry, an event execution confirmation page corresponding to the event execution plan reaching the reminder time is displayed, and an event execution confirmation flag in a state to be executed is displayed on the event execution confirmation page.

In step 1926, the state of the event execution validation token is updated to the executed state in response to the trigger operation for the event execution validation token.

In a specific application, the event execution confirmation mark displayed by the terminal may be a button displayed with "punch" content, and when the user clicks the button, the display content of the button is changed to "punch".

It will be appreciated that the explanation of this embodiment may be with reference to the above embodiments.

In the above embodiment, the terminal can implement triggering event reminding only by enabling the event execution plan to be in the enabled state in response to the enabling triggering operation for the event execution plan, so that the interaction in the whole event reminding process is simple, the interaction efficiency in the event reminding process can be improved, and the terminal can update the state of the event execution confirmation mark to be the executed state in response to the triggering operation for the event execution confirmation mark, thereby improving the effectiveness of medicine taking reminding.

In some specific embodiments, the application further provides an application scenario, in which the terminal runs an application capable of providing a reminder service, the application is a sub-application, and the sub-application runs in one of the native applications installed by the terminal, and the native application logs in with a user account. In the application scenario, the event description information is an electronic prescription, the event execution plan is a medicine taking plan, the items are medicines in the electronic prescription, and the event reminding is a medicine taking reminding. The following specifically describes the implementation process of the event reminding method in the application scene:

After the prescription is successfully created and passes the auditing, the server can generate prescription information based on the electronic prescription through a producer thread and write the prescription information into a message queue, the consumer thread reads the prescription information from the message queue, the medicine name and the medicine frequency are extracted from the read prescription information, and at least one medicine taking plan matched with the electronic prescription is generated according to the medicine name and the medicine frequency through the consumer thread, so that the medicine taking plan is automatically generated and stored in a medicine taking plan data table, and the state of the medicine taking plan is in a state to be confirmed.

After 24 hours from the successful creation and passing the audit of the prescription, the server may send a notification message to the terminal logging into the user account to remind the user to timely start the medication reminder. After the notification message reaches the terminal, triggering and generating a notification event at the terminal, wherein the terminal can respond to the notification event, display a notification message card aiming at the medicine taking description information, display notification message content indicated by the notification event in the notification message card, and display a medicine taking plan display entrance matched with the medicine taking description information, and further respond to triggering operation aiming at the medicine taking plan display entrance, display at least one medicine taking plan of a state to be confirmed matched with the medicine taking description information. The specific display page of the notification message card may refer to fig. 4, and when the user clicks on the click jump to [ take management list page: all medications ], entering a medication management interface shown in fig. 3, wherein the medication management page integrates the functions of editing, viewing and deleting medication reminding plans, and a user can flexibly set medication time, usage amount or delete unnecessary medication plans according to needs.

The terminal may display the medication plan for which the activation trigger operation is directed as being in the activated state in response to the activation trigger operation of the medication plan for any one of the to-be-confirmed states. Specifically, if the user directly clicks the "start reminder" button in a certain medication plan card displayed by the terminal, the medication plan is counted as a reminder start time from the day of clicking, and the state is changed into an enabled state, and the display is transferred from the plan display area to be confirmed to the enabled plan display area in the medication management page for display. If the user clicks other areas except the start reminding button in the medicine taking plan card, the user enters a medicine taking plan editing page, the medicine taking plan editing page can refer to fig. 12 specifically, after the user edits the medicine taking plan, the user clicks the start reminding button in the page, the edited medicine taking plan becomes an enabled state, and the display area of the enabled plan in the medicine taking management page is displayed. It will be appreciated that after the service plan is changed from the to-be-validated state to the enabled state, the server may correspondingly change the state of the medication plan in the medication plan data table.

For the interactive operations such as editing, state changing, viewing, deleting and the like of the medicine taking plan, the terminal can send a request to the server, a time sequence diagram of a one-time request process can refer to fig. 21 according to a response display operation result of the server, a request triggered by a sub-application reaches the server through a gateway layer, a medicine taking management background service is called in the server through BFF (Backend For Frontend) service, and after the background service processes the request through a database, the result is returned to the sub-application. The server in the embodiment of the application can be a public cloud server, that is, all service components of the server are uniformly deployed on the public cloud, and a high-availability and high-performance data service is provided by means of the capability provided by Iaas (Infrastructure as a Service ) on the cloud.

The terminal may further display prompt information of the medication reminder, display a reminder message card of the medication reminder in response to a viewing operation for the prompt information, display reminder message contents of the medication reminder in the reminder message card, and display a medication confirmation entry corresponding to the medication schedule reaching the reminder time, and display a medication confirmation page corresponding to the medication schedule reaching the reminder time in response to a triggering operation for the medication confirmation entry. Wherein when there are a plurality of taking plans in an enabled state and the same reminding time divided according to the taking reminding frequency of each of the taking plans in the enabled state is reached, the terminal displays taking confirmation entrances corresponding to each of the taking plans in the enabled state, displays a taking confirmation page commonly corresponding to the taking plans in the enabled state in response to a trigger operation for any one of the taking confirmation entrances displayed, displays a medicine identification corresponding to each of the taking plans in the enabled state in the taking confirmation page, and displays one taking confirmation mark for simultaneously taking confirmation for the taking plans in the enabled state. In a specific process, referring to fig. 9 and fig. 10, when a user clicks a medicine taking confirmation entry in any one of the reminding message cards in fig. 9, the user can enter a medicine taking and punching page in fig. 10, medicine names of two medicine taking plans reaching the same reminding time are simultaneously displayed in the page, and after the user clicks the medicine taking and punching, the user can take medicine and punch cards for the two medicines simultaneously. Aiming at the medicine taking and card punching operation of a user, the server can mark in a reminding time data table, so that the information such as card punching times, card punching days and the like of the user can be counted, and a card punching result is displayed on a medicine taking and card punching page of the terminal, and particularly, reference can be made to fig. 10.

In the above embodiment, based on the message queue, after the doctor creates the electronic prescription, the medicine taking plan is automatically generated and the message notification for starting the medicine taking reminding can be sent to the user, so that the medicine taking reminding can be received only through simple operation after the user inquires the doctor, the whole process is simple in interaction, and the interaction efficiency in the medicine taking reminding process is greatly improved.

In some specific embodiments, the application further provides another application scenario, in which an application capable of providing a reminding service is run by the terminal, a user can upload a prescription picture obtained by taking a paper prescription through the application, the terminal can identify the prescription picture, extract prescription information in the picture and automatically generate a medicine taking plan, when the user clicks a medicine taking plan display entrance displayed by the application interface, at least one medicine taking plan to be confirmed can be displayed, wherein a medicine name matched with a medicine identifier in the medicine taking plan exists in the prescription picture, medicine taking reminding frequency corresponding to the medicine identifier in the medicine taking plan is matched with medicine taking frequency of the medicine name in the prescription picture, the terminal can further respond to an enabling triggering operation of the medicine taking plan for any state to be confirmed, display the medicine taking plan for the enabling triggering operation as being in an enabled state, and trigger a reminder corresponding to the medicine taking plan to the reminding time when reaching any reminding time divided according to the medicine taking reminding frequency of any medicine taking plan in the enabled state. For specific implementation procedures, reference may be made to the above embodiments, which are not described herein in detail.

In some specific embodiments, the application further provides another application scenario, in which the terminal runs an application capable of providing a reminding service, a user can enter a session page with the robot account through the application, the user can send voice on the session page, the terminal can identify the voice, when event description information is identified, an event execution plan is automatically generated, and event reminding is performed through the event reminding method of the application. Optionally, when meeting description information such as meeting names and meeting time is identified, at least one meeting plan is generated according to the meeting description information, and a meeting plan display entry is displayed on the session page, the terminal further responds to a trigger operation for the meeting plan display entry to display at least one meeting plan in a to-be-confirmed state, the terminal further responds to an enabling trigger operation for any meeting plan in a to-be-confirmed state, the meeting plan for which the trigger operation is enabled is displayed in an enabled state, and when any reminding time divided according to the meeting time of any meeting plan in the enabled state is reached, meeting reminding corresponding to the meeting plan reaching the reminding time is triggered. The specific implementation and explanation of each step may refer to the above embodiments, and this application is not repeated herein.

It should be understood that, although the steps in the flowcharts related to the above embodiments are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides an event reminding device for realizing the event reminding method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in the embodiment of one or more event reminding devices provided below may refer to the limitation of the event reminding method hereinabove, and will not be repeated here.

In one embodiment, as shown in fig. 22, there is provided an event reminder 2200 comprising:

afirst display module 2202, configured to display, when there is event description information, an event execution plan of at least one to-be-confirmed state adapted to the event description information; the event description information has an item name matched with an item identification in the event execution plan, and the event reminding time description information corresponding to the item identification in the event execution plan is matched with the event execution time description information of the item name in the event description information;

asecond display module 2204 for displaying, in response to an enabling trigger operation of the event execution plan for any one of the to-be-confirmed states, the event execution plan for which the trigger operation is enabled as being in an enabled state;

theevent reminder module 2206 is configured to trigger an event reminder corresponding to an event execution plan that reaches a reminder time when reaching any reminder time divided according to the event reminder time description information of any event execution plan that is in an enabled state.

In some embodiments, the first display module is further configured to display an event execution plan display entry adapted to the event description information when the event description information exists; and in response to a trigger operation of the display portal for the event execution plan, displaying the event execution plan of at least one to-be-confirmed state adapted to the event description information.

In some embodiments, the first display module is further configured to, when generating the event description information pertaining to the logged-in user account, display a notification message card for the event description information in response to a notification event for the event description information; and displaying the notification message content indicated by the notification event in the notification message card, and displaying an event execution plan display entry matched with the event description information.

In some embodiments, the first display module is further configured to, when the service account triggers event description information for the user account, display an event description information message card for browsing the event description information on a session page for a session between the logged-in user account and the service account; and displaying an event execution plan display entry adapted to the event description information corresponding to the event description information message card.

In some embodiments, the event reminding device further includes a medicine taking confirmation module, configured to display an event execution confirmation page corresponding to the event execution plan reaching the reminding time when reaching any reminding time divided according to the event reminding time description information of any enabled event execution plan, and display an event execution confirmation mark in a state to be executed on the event execution confirmation page; in response to a trigger operation for the event execution validation token, the state of the event execution validation token is updated to an executed state.

In some embodiments, the enabled state event execution plan is displayed on an event execution plan interaction page; the medicine taking confirmation module is also used for displaying an event execution confirmation entry corresponding to the event execution plan reaching the reminding time in the event execution plan interaction page; and in response to the triggering operation of the event execution confirmation entry, displaying an event execution confirmation page corresponding to the event execution plan reaching the reminding time.

In some embodiments, the medication confirmation module is further configured to display a prompt message for event reminding; responding to the checking operation of the prompt information, and displaying a prompt message card for prompting the event; displaying the reminding message content of event reminding in a reminding message card, and displaying an event execution confirmation entry corresponding to an event execution plan reaching reminding time; and in response to the triggering operation of the event execution confirmation entry, displaying an event execution confirmation page corresponding to the event execution plan reaching the reminding time.

In some embodiments, the medicine taking confirmation module is further configured to display an event execution confirmation page that corresponds to the plurality of enabled event execution plans together when the plurality of enabled event execution plans exist and the same reminder time divided according to the respective event reminder time description information of the plurality of enabled event execution plans is reached; in the event execution confirmation page, displaying item identifiers corresponding to each of a plurality of event execution plans in an enabled state; in the event execution confirmation page, one event execution confirmation mark for simultaneous medication confirmation for a plurality of enabled event execution plans is displayed.

In some embodiments, the medication intake confirmation module is further configured to display an event execution confirmation entry corresponding to each of the plurality of enabled state event execution plans; in response to a trigger operation of executing a confirmation portal for any one of the displayed event execution confirmation portals, an event execution confirmation page is displayed that corresponds in common to the plurality of enabled state event execution plans.

In some embodiments, the second display module is further configured to enter an event execution plan editing page in response to an editing trigger operation of the event execution plan for any of the to-be-confirmed states, and display at least one editing item of the event execution plan for which the editing trigger operation is directed in the event execution plan editing page; displaying editing contents of the editing operation in response to the editing operation for any one of the at least one editing item; in response to an enabling trigger operation for an event execution plan containing editing content, the event execution plan for which the trigger operation is enabled is displayed in an enabled state.

In some embodiments, the second display module is further configured to display, in response to a first editing operation for an event reminder time description information editing item in the at least one editing item, event reminder time description information edited by the first editing operation, corresponding to a number of times of taking medicine within a single medicine taking period specified by the displayed event reminder time description information, and display a number of reminder time editing items that match; and displaying the reminding time edited by the second editing operation in response to the second editing operation for the reminding time editing item.

In some embodiments, the event execution plan of the at least one to-be-confirmed state is shown in a to-be-confirmed plan display area in the event execution plan interaction page; and the second display module is also used for responding to the starting trigger operation of the event execution plan aiming at any to-be-confirmed state and transferring the event execution plan aimed at by the starting trigger operation from the to-be-confirmed plan display area to the started plan display area in the event execution plan interaction page.

In some embodiments, the event description information is an electronic prescription and belongs to a logged-in user account: the event reminding device further comprises an event execution plan generating module, which is used for: acquiring an electronic prescription belonging to a user account, generating prescription information based on the electronic prescription through a producer thread, and writing the prescription information into an information queue; reading prescription information from the information queue through a consumer thread, and extracting item names and event execution time description information from the read prescription information; at least one event execution plan adapted to the electronic prescription is generated by the consumer thread from the project name and the event execution time description information.

In some embodiments, the event reminding device further includes a prompt information generating module, configured to: when the reminding time divided according to the event reminding time description information of any event execution plan in the enabled state is reached, writing a reminding message generated according to the event execution plan reaching the reminding time into a reminding message data table through a first timing task; traversing the reminding message in the reminding message data table through the second timing task; triggering and generating prompt information corresponding to the prompt messages aiming at each traversed prompt message.

The modules in the event reminding device can be all or partially realized by software, hardware and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 23. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for storing data such as event execution plans, reminding time and the like. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program when executed by a processor implements an event alert method.

In one embodiment, a computer device is provided, which may be a terminal, and the internal structure thereof may be as shown in fig. 24. The computer device includes a processor, a memory, an input/output interface, a communication interface, a display unit, and an input means. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program when executed by a processor implements an event alert method. The display unit of the computer equipment is used for forming a visual picture, and can be a display screen, a projection device or a virtual reality imaging device, wherein the display screen can be a liquid crystal display screen or an electronic ink display screen, the input device of the computer equipment can be a touch layer covered on the display screen, can also be a key, a track ball or a touch pad arranged on a shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by those skilled in the art that the structures shown in fig. 23 and 24 are merely block diagrams of partial structures related to the present application and do not constitute a limitation of the computer device to which the present application is applied, and that a specific computer device may include more or less components than those shown in the drawings, or may combine some components, or have different arrangements of components.

In one embodiment, a computer device is provided that includes a memory having a computer program stored therein and a processor that when executing the computer program performs the steps of the event notification method described above.

In one embodiment, a computer readable storage medium is provided having a computer program stored thereon which, when executed by a processor, implements the steps of the event notification method described above.

In one embodiment, a computer program product is provided comprising a computer program which, when executed by a processor, implements the steps of the event notification method described above.

It should be noted that, the user information (including, but not limited to, user equipment information, user personal information, etc.) and the data (including, but not limited to, data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data are required to comply with the related laws and regulations and standards of the related countries and regions.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.

Claims

1. A method of event alerting, the method comprising:

2. The method according to claim 1, wherein the displaying the event execution plan of the at least one to-be-confirmed state adapted to the event description information when the event description information exists comprises:

displaying an event execution plan display entry adapted to event description information when the event description information exists;

and in response to the triggering operation of the program display portal for the event execution plan, displaying an event execution plan of at least one to-be-confirmed state matched with the event description information.

3. The method of claim 2, wherein displaying an event execution plan display portal adapted to the event description information when the event description information exists, comprises:

When generating event description information belonging to logged-in user account, responding to a notification event for the event description information, and displaying a notification message card for the event description information;

and displaying the notification message content indicated by the notification event in the notification message card, and displaying an event execution plan display entry adapted to the event description information.

4. The method of claim 2, wherein the event reminder is a medication reminder;

the event description information is present, and an event execution plan display entry adapted to the event description information is displayed, including:

a conversation page for conversation between a logged-in user account and a service account is used for displaying a medicine taking description information message card for browsing medicine taking description information when the service account triggers the medicine taking description information aiming at the user account;

and displaying a medicine taking plan display entrance matched with the medicine taking description information corresponding to the medicine taking description information message card.

5. The method according to claim 1, wherein the method further comprises:

when any reminding time divided according to the event reminding time description information of any event execution plan in the enabled state is reached, displaying an event execution confirmation page corresponding to the event execution plan reaching the reminding time, and displaying an event execution confirmation mark in a state to be executed on the event execution confirmation page;

In response to a triggering operation of the event execution validation token, updating a state of the event execution validation token to an executed state.

6. The method of claim 5, wherein the enabled state event execution plan is displayed on an event execution plan interaction page;

the displaying the event execution confirmation page corresponding to the event execution plan reaching the reminding time comprises the following steps:

displaying an event execution confirmation entry corresponding to the event execution plan reaching the reminding time in the event execution plan interaction page;

and responding to the triggering operation of the confirmation entry for the event, and displaying an event execution confirmation page corresponding to the event execution plan reaching the reminding time.

7. The method of claim 6, wherein each of the enabled state event execution plans is displayed in each of the event execution plan cards in an event execution plan display area of the event execution plan interaction page, respectively;

the displaying, in the event execution plan interaction page, an event execution confirmation entry corresponding to the event execution plan reaching a reminder time, including:

When the reminding time of the event execution plan in any event execution plan card is reached, increasing the size of the event execution plan card reaching the reminding time so as to increase a display area for displaying an event execution confirmation entrance;

in the added display area, an event execution confirmation entry corresponding to the event execution plan reaching the reminder time is displayed.

8. The method of claim 5, wherein displaying an event execution confirmation page corresponding to the event execution plan for which a reminder time is reached comprises:

displaying prompt information of the event prompt;

responding to the viewing operation of the prompt information, and displaying a prompt message card of the event prompt;

displaying the reminding message content of the event reminding in the reminding message card, and displaying an event execution confirmation entry corresponding to the event execution plan reaching the reminding time;

9. The method of claim 5, wherein the event reminder is a medication reminder and the event execution plan is a medication plan;

When any reminding time divided according to the event reminding time description information of any event execution plan in the enabled state is reached, displaying an event execution confirmation page corresponding to the event execution plan reaching the reminding time, and displaying an event execution confirmation mark in the to-be-executed state on the event execution confirmation page, wherein the method comprises the following steps:

when a plurality of started medicine taking plans exist and the same reminding time divided according to the medicine taking reminding frequency of each of the plurality of started medicine taking plans is reached, displaying a medicine taking confirmation page commonly corresponding to the plurality of started medicine taking plans;

in the medicine taking confirmation page, medicine identifiers corresponding to the medicine taking plans in the enabled states are displayed;

in the medication confirmation page, one medication confirmation mark for simultaneous medication confirmation for the medication plans of the plurality of enabled states is displayed.

10. The method of claim 9, wherein the displaying a medication confirmation page that collectively corresponds to the plurality of enabled medication schedules comprises:

displaying medication confirmation entries corresponding to each of the plurality of enabled medication schedules;

In response to a trigger operation for any one of the displayed medication confirmation portals, a medication confirmation page is displayed that corresponds in common to the plurality of enabled-state medication plans.

11. The method of claim 1, wherein the enabled event execution plan is displayed in an event execution plan display area in an event execution plan interaction page, the event execution plan interaction page including a plurality of options capable of being operated to be in a selected state in response to selection, the enabled event execution plan displayed in the event execution plan display area conforming to a filter condition corresponding to an option in the selected state among the plurality of options.

12. The method of claim 1, wherein the displaying the event execution plan for which the enabling trigger operation is directed to in an enabled state in response to an enabling trigger operation of the event execution plan for any of the to-be-confirmed states, comprises:

responding to the editing triggering operation of the event execution plan aiming at any state to be confirmed, entering an event execution plan editing page, and displaying at least one editing item of the event execution plan aiming at the editing triggering operation in the event execution plan editing page;

Displaying editing content of an editing operation in response to the editing operation for any one of the at least one editing item;

in response to an enabling trigger operation for an event execution plan containing editing content, the event execution plan for which the enabling trigger operation is directed is displayed as being in an enabled state.

13. The method of claim 12, wherein the event reminder is a medication reminder;

the displaying, in response to an editing operation for any one of the at least one editing item, editing contents of the editing operation, includes:

in response to a first editing operation for a medicine taking reminding frequency editing item in the at least one editing item, displaying the medicine taking reminding frequency edited by the first editing operation,

displaying reminding time editing items with matched quantity corresponding to the medicine taking times in a single medicine taking period appointed by the displayed medicine taking reminding frequency;

and responding to a second editing operation for the reminding time editing item, and displaying the reminding time edited by the second editing operation.

14. The method according to claim 1, wherein the event execution plan of the at least one state to be confirmed is presented in a plan to be confirmed display area in an event execution plan interaction page;

The enabling trigger operation responding to the event execution plan for any state to be confirmed, displaying the event execution plan for which the enabling trigger operation is aimed as being in an enabled state, comprising:

and responding to the starting triggering operation of the event execution plan aiming at any state to be confirmed, and transferring the event execution plan aiming at the starting triggering operation from the plan display area to be confirmed to the started plan display area in the event execution plan interaction page.

15. The method according to any one of claims 1 to 14, wherein the reminder of the event reminder is generated by a reminder generating step comprising:

when the reminding time divided according to the event reminding time description information of any event execution plan in the enabled state is reached, writing a reminding message generated according to the event execution plan reaching the reminding time into a reminding message data table through a first timing task;

traversing the reminding message in the reminding message data table through a second timing task;

triggering and generating prompt information corresponding to the prompt messages aiming at each traversed prompt message.

16. The method of claim 15, wherein the event reminder is a medication reminder, the event execution plan is a medication plan, and the enabled medication plan is stored in a medication plan data table;

the writing, by the first timing task, the reminder message generated according to the event execution plan reaching the reminder time into a reminder message data table includes:

traversing the taking schedule in the started state in the taking schedule data table through a first timing task;

inquiring the reminding time of each traversed medicine taking plan from a reminding time data table associated with the medicine taking plan data table through a first timing task according to each traversed medicine taking plan;

when any one of the inquired reminding time is reached, a reminding message is generated according to the traversed medicine taking plan through a first timing task and is written into a reminding message data table.

17. An event reminder device, the device comprising:

18. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any one of claims 1 to 16 when the computer program is executed.

19. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 16.

20. A computer program product comprising a computer program, characterized in that the computer program, when executed by a processor, implements the steps of the method of any one of claims 1 to 16.