CN115775610B

CN115775610B - Task execution method and storage medium based on electronic medical record

Info

Publication number: CN115775610B
Application number: CN202310094795.6A
Authority: CN
Inventors: 韦宝兴; 曾世鸿; 范熊磊
Original assignee: Chengdu Xintong Netease Medical Science And Technology Development Co ltd
Current assignee: Chengdu Xintong Netease Medical Science And Technology Development Co ltd
Priority date: 2023-02-10
Filing date: 2023-02-10
Publication date: 2023-05-12
Anticipated expiration: 2043-02-10
Also published as: CN115775610A

Abstract

The invention relates to a task execution method and a storage medium based on an electronic medical record, wherein the task execution method comprises the following steps: under the condition that the trigger event is monitored, inquiring a time limit rule table based on the trigger event, and acquiring a first target time limit rule corresponding to the trigger event; wherein the time limit rule table comprises a plurality of time limit rules which are pre-configured; judging whether the first target time limit rule comprises a triggering condition or not; the triggering condition is configured based on the customization requirement of the target hospital on the electronic medical record; if the first target time limit rule is determined to comprise the trigger condition, updating a task list for storing writing tasks of the electronic medical record based on the trigger condition and the rule scheduling configuration table under the condition that the trigger condition is met, and obtaining an updated task list; and executing the tasks in the updated task list at regular time to obtain a task execution result, thereby solving the two problems of flexible definition of time limit rules and configurable rule scheduling relationship.

Description

Task execution method and storage medium based on electronic medical record

Technical Field

The invention relates to the field of medical information processing, in particular to a task execution method and a storage medium based on an electronic medical record.

Background

Electronic medical records are digitized medical records that are stored, managed, transmitted, and reproduced with electronic devices. And according to the specification of the writing time limit of the national electronic medical records, the writing of various electronic medical records has related requirements. For example, the admission records must be completed within 24 hours after the admission of the patient and the patient at risk must write a course of disease record every 24 hours, etc.

The current common technical approach is to use a timer and a timeout function. For example, when a patient is admitted, a timer task with a period of 24 hours is started, whether writing exists in an admission record is judged in the task, if not, the rule of the admission record is judged to be violated, and the admission record is finished within 24 hours after the patient is admitted again or a plurality of times, and then the electronic medical record is deducted and evaluated according to a deduction item or a single item corresponding to the rule.

However, the conventional method using a single timer task processing scheme has the disadvantages of requiring redevelopment of codes during rule extension and new time limit rule addition, and increasing workload, and meanwhile, the technical architecture has poor ductility and poor maintainability of software.

Disclosure of Invention

First, the technical problem to be solved

In view of the above-mentioned drawbacks and shortcomings of the prior art, the present invention provides a task execution method and a storage medium based on an electronic medical record, which solve the technical problems of the prior art that a conventional task processing scheme using a single timer needs to redevelop codes.

(II) technical scheme

In order to achieve the above purpose, the main technical scheme adopted by the invention comprises the following steps:

in a first aspect, an embodiment of the present invention provides a task execution method based on an electronic medical record, including: under the condition that the trigger event is monitored, inquiring a time limit rule table based on the trigger event, and acquiring a first target time limit rule corresponding to the trigger event; the time limit rule table comprises a plurality of time limit rules which are pre-configured, and each time limit rule in the plurality of time limit rules is used for representing the time limit rule of the electronic medical record of the corresponding target hospital; judging whether the first target time limit rule comprises a triggering condition or not; the triggering condition is configured based on the customization requirement of the target hospital on the electronic medical record; if the first target time limit rule is determined to comprise the trigger condition, updating a task list for storing writing tasks of the electronic medical record based on the trigger condition and the rule scheduling configuration table under the condition that the trigger condition is met, and obtaining an updated task list; the rule scheduling configuration table is used for storing a plurality of pairs of time limit rules with mutual exclusion relation or dependency relation; and executing the tasks in the updated task list at regular time to obtain a task execution result.

Therefore, in the embodiment of the application, under the condition that the trigger event is monitored, a time limit rule table is queried based on the trigger event, a first target time limit rule corresponding to the trigger event is obtained, wherein the time limit rule table comprises a plurality of time limit rules which are configured in advance, each time limit rule in the plurality of time limit rules is used for representing the time limit rule of the electronic medical record of the corresponding target hospital, and whether the first target time limit rule comprises the trigger condition is judged; the triggering condition is configured based on the customization requirement of the target hospital on the electronic medical record. If the first target time limit rule is determined to comprise the trigger condition, under the condition that the trigger condition is met, updating a task list for storing writing tasks of the electronic medical record based on the trigger condition and the rule scheduling configuration table to obtain an updated task list, and performing timed execution on tasks in the updated task list to obtain a task execution result, so that the expansibility of the time limit rule can be improved, the maintenance and release cost of software is reduced, and the two problems that flexible definition of the time limit rule and configuration of the rule scheduling relation are required to be solved are solved.

In one possible embodiment, the triggering event is an event related to the target patient; inquiring a time limit rule table based on the trigger event to obtain a first target time limit rule corresponding to the trigger event, wherein the method comprises the following steps: acquiring department information of a target patient; a first target time limit rule is determined from the plurality of time limit rules based on the trigger event and the department information.

In one possible embodiment, the trigger condition includes enabling the trigger condition; under the condition that the trigger condition is met, updating a task list for storing writing tasks of the electronic medical record based on the trigger condition and the rule scheduling configuration table to obtain an updated task list, and obtaining the updated task list, wherein the method comprises the following steps: acquiring first parameter information related to an enabling trigger condition; judging whether an enabling triggering condition is met or not based on the first parameter information; if the trigger condition is met, adding the writing task of the electronic medical record corresponding to the first target time limit rule into the task list according to the rule scheduling configuration table.

In one possible embodiment, according to the rule scheduling configuration table, adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list includes: querying a rule scheduling configuration table by using the first target time limit rule to determine whether a second target time limit rule with a mutual exclusion relation with the first target time limit rule exists in the rule scheduling configuration table; the first target time limit rule and the second target time limit rule are two time limit rules corresponding to the same target patient in different disease states; if a second target time limit rule exists and a writing task of the electronic medical record corresponding to the second target time limit rule exists in the task list, adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list, and deleting the writing task of the electronic medical record corresponding to the second target time limit rule from the task list; if the second target time limit rule does not exist, adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list.

In one possible embodiment, according to the rule scheduling configuration table, adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list includes: querying a rule scheduling configuration table by using the first target time limit rule to determine whether a third target time limit rule with a dependency relationship with the first target time limit rule exists in the rule scheduling configuration table; the first target time limit rule and the third target time limit rule are two time limit rules corresponding to the same target patient in the same illness state; if the third target time limit rule exists and the writing task of the electronic medical record corresponding to the third target time limit rule does not exist in the task list, adding the writing task of the electronic medical record corresponding to the first target time limit rule and the writing task of the electronic medical record corresponding to the third target time limit rule into the task list respectively; if the third target time limit rule does not exist, adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list.

In one possible embodiment, the first target time limit rule includes classification information, trigger event, start time, and cycle time of the electronic medical record corresponding to the first target time limit rule.

In one possible embodiment, the trigger condition includes a stop trigger condition; under the condition that the trigger condition is met, updating a task list for storing writing tasks of the electronic medical record based on the trigger condition and the rule scheduling configuration table to obtain an updated task list, wherein the method comprises the following steps: acquiring second parameter information related to a stop triggering condition; judging whether a stop triggering condition is met or not based on the second parameter information; and if the stopping triggering condition is met, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list according to the rule scheduling configuration table.

In one possible embodiment, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list according to the rule scheduling configuration table includes: querying a rule scheduling configuration table by using the first target time limit rule to determine whether a fourth target time limit rule with a mutual exclusion relation with the first target time limit rule exists in the rule scheduling configuration table; if the fourth target time limit rule exists and the writing task of the electronic medical record corresponding to the fourth target time limit rule does not exist in the task list, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list, and adding the writing task of the electronic medical record corresponding to the fourth target time limit rule into the task list; and if the fourth target time limit rule does not exist, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list.

In one possible embodiment, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list according to the rule scheduling configuration table includes: querying a rule scheduling configuration table by using the first target time limit rule to determine whether a fifth target time limit rule with a dependency relationship with the first target time limit rule exists in the rule scheduling configuration table; the first target time limit rule and the fifth target time limit rule are two time limit rules corresponding to the same target patient in the same illness state; if the fifth target time limit rule exists and the writing task of the electronic medical record corresponding to the fifth target time limit rule exists in the task list, deleting the writing task of the electronic medical record corresponding to the first target time limit rule and the writing task of the electronic medical record corresponding to the fifth target time limit rule from the task list; and if the fifth target time limit rule does not exist, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list.

In a second aspect, embodiments of the present application provide a storage medium having stored thereon a computer program which, when executed by a processor, performs the method of the first aspect or any alternative implementation of the first aspect.

In a third aspect, an embodiment of the present application provides an electronic device, including: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory in communication via the bus when the electronic device is running, the machine-readable instructions when executed by the processor performing the method of the first aspect or any alternative implementation of the first aspect.

In a fourth aspect, the present application provides a computer program product which, when run on a computer, causes the computer to perform the method of the first aspect or any of the possible implementations of the first aspect.

(III) beneficial effects

The beneficial effects of the invention are as follows: the invention provides a task execution method and a storage medium based on electronic medical records, which are characterized in that a time limit rule table is inquired based on a trigger event to obtain a first target time limit rule corresponding to the trigger event, wherein the time limit rule table comprises a plurality of time limit rules which are preset, each time limit rule in the plurality of time limit rules is used for representing the time limit rule of the electronic medical record of a corresponding target hospital, and whether the first target time limit rule comprises a trigger condition is judged; the triggering condition is configured based on the customization requirement of the target hospital on the electronic medical record. If the first target time limit rule is determined to comprise the trigger condition, updating a task list for storing writing tasks of the electronic medical record based on the trigger condition and the rule scheduling configuration table under the condition that the trigger condition is met, obtaining an updated task list, and performing timing execution on tasks in the updated task list to obtain a task execution result, so that the expansibility of the time limit rule can be improved, and the maintenance and release cost of software can be reduced.

In order to make the above objects, features and advantages of the embodiments of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 shows a specific flowchart of a task execution method based on an electronic medical record shown in the application.

Detailed Description

The invention will be better explained by the following detailed description of the embodiments with reference to the drawings.

Medical history is a systematic record of the occurrence, progression, diagnosis, and treatment of a patient's disease. And, it is the disease archival data that the clinician obtains according to inquiry, physical examination, auxiliary examination and the detailed observation of the state of illness, through induction, analysis, arrangement, writing. In addition, the medical record can truly reflect the illness state of a patient and also can directly reflect the medical quality, academic level and management level of a hospital. And it not only provides basic information for medical treatment, teaching and scientific research, but also provides indispensable medical information for hospital management. And, medical history is an important basis for determining legal liability when medical disputes are involved. And, in medical insurance, the medical record is a credential of an associated medical payment.

And the electronic medical record quality control system analyzes the medical record of the patient on the basis of the use of the electronic medical record system in a hospital, and assists doctors and medical record management staff to efficiently and high-quality finish the writing of the medical record, the quality control of the medical record and the like. And, produce high-quality, precious electronic medical record data for medical treatment, teaching and scientific research workers, offer objective and fair legal basis for doctor-patient disputes at the same time.

And, the electronic medical record is a digitized medical record that is stored, managed, transmitted, and reproduced with the electronic device. And according to the specification of the writing time limit of the national electronic medical records, the writing of various electronic medical records has related requirements. For example, the admission records must be completed within 24 hours after the admission of the patient and the patient at risk must write a course of disease record every 24 hours, etc.

However, the method for judging the medical record writing time limit rule can meet the independent time limit rule only by using the timer and the timeout function, but has poor compatibility with the time limit rule with dependence and mutual exclusion and the customization requirement of a hospital.

For example, when the patient's condition is stable, according to the rules of "patient with stable condition records at least once every 3 days", it is necessary to write a record of the condition every 3 days, that is, to start a timer for 72 hours, and to monitor whether there is a written record of the condition in the timed task. And when the illness state of the patient changes into the illness state, the period is required to be adjusted to be 1 day according to the rule of the record of the illness course of the patient at least once every day. Because patient status is a mutually exclusive relationship between patient risk, patient severity, and patient severity, the adjustment process requires searching for all relevant timer tasks for patient stability and patient severity in the program, terminating the tasks, and then starting a new timer task (e.g., patient at risk records at least once a day). And, when the patient state changes, the limitation is that the adjustment of the time limit rule can only be written in the event processing function in which the patient state changes.

For another example, according to the time limit rule of "the admission record, the admission record should be completed within 24 hours after the patient is admitted", in the case that the patient is admitted for less than 24 hours, the rule should also be adjusted to "the admission and discharge record should be completed within 24 hours after the patient is discharged", and the adjustment of the time limit rule can only be written in the event processing function of the patient discharge.

Here, the above two examples are described by taking a time limit rule having a mutually exclusive relationship as an example.

For another example, according to the rules of the patient's records of the course of the illness at least once every 3 days, the time monitoring task started by the patient's illness is stabilized, when the patient's illness is at risk, if the illness is stabilized for more than half of the time (i.e. 36 hours), the time monitoring task is stopped except the rules of the patient's records of the course of the illness at least once every day, otherwise, if the illness is stabilized for more than half of the time, the time monitoring task is stopped.

Here, the above description is given by taking a time limit rule of a customization requirement of a hospital as an example.

From the above examples, it can be seen that the conventional method using a single timer task processing scheme has the disadvantages that code needs to be redeveloped when rules are extended and time limit rules are newly added, and the workload is increased, and meanwhile, the extensibility of the technical architecture is poor and the maintainability of software is poor. And when there is a small difference in the requirements of different hospitals on the same time limit rule, after the code update is changed, the regression test and the release process need to be re-executed, so that additional workload on management is brought, and quality risks are brought due to potential changes of the packaging environment (such as automatic upgrading of an operating system, upgrading of related compiling and packaging tool versions, and the like).

Based on this, the embodiment of the application provides a task execution scheme, by querying a time limit rule table based on a trigger event under the condition that the trigger event is monitored, acquiring a first target time limit rule corresponding to the trigger event, wherein the time limit rule table comprises a plurality of time limit rules which are configured in advance, each time limit rule in the plurality of time limit rules is used for representing the time limit rule of the electronic medical record of the corresponding target hospital, and judging whether the first target time limit rule comprises a trigger condition; the triggering condition is configured based on the customization requirement of the target hospital on the electronic medical record. If the first target time limit rule is determined to comprise the trigger condition, under the condition that the trigger condition is met, updating a task list for storing writing tasks of the electronic medical record based on the trigger condition, obtaining an updated task list, and performing timed execution on tasks in the updated task list to obtain a task execution result, so that the expansibility of the time limit rule can be improved, the maintenance and release cost of software is reduced, and the two problems that flexible definition of the time limit rule and configuration of a rule scheduling relationship are required to be solved.

In order that the above-described aspects may be better understood, exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

In order to facilitate understanding of the embodiments of the present application, some terms related to the embodiments of the present application are explained as follows:

time limit rule function of electronic medical record quality control system: the method can comprise time limit rule definition, a time limit rule application range, a time limit rule scheduling relationship, time limit task scheduling and monitoring, time limit result storage and display;

time limit rule: the method can comprise a rule code, a rule description, an enabling trigger event, a stopping trigger event, a circulation number, a circulation condition, medical record classification of rule detection, a violation threshold and a calculation method of violation judgment;

time limit rule application scope: it defines the department to which the current rule applies;

time limit rule scheduling relationship: it defines mutual exclusion and dependency relationships among rules;

Time limit task scheduling and monitoring: it may initiate a corresponding time-limited task by trigger event matching of time-limited rules, depending on external events (e.g. admission notifications, etc.). For example, for the rule that an admission record, a readmission or a plurality of admission records should be completed within 24 hours after the patient is admitted, a 24-hour timer is started, whether the admission record has been completed is detected in a timeout task, if not, a timeout is determined, otherwise, no timeout is determined. And starting or stopping timing tasks of other rules according to the state of the current rule according to the rule scheduling relation so as to achieve the purpose of task scheduling. Recording and updating the starting and stopping states of the tasks in real time, and showing the task scheduling and executing processes;

time limit result storage and display: the method can store the execution result of each time limit rule, feed back the execution result (including reminding) to a doctor station for timely correction and simultaneously provide a report and a graph mode multidimensional display result;

and, it is desirable to achieve the effects of strong expansibility of the time limit rule and reduced maintenance and release costs of the software, which needs to solve two problems of flexible definition of the time limit rule and configurable rule scheduling relationship.

Mutual exclusion relation: it may refer to a time limit rule having a mutually exclusive relationship with another time limit rule. For example, when a writing task corresponding to a certain electronic time limit needs to be started, stopping the writing task corresponding to another electronic time limit with a mutual exclusion relation; for another example, when it is necessary to stop the writing task corresponding to one electronic time limit, the writing task corresponding to another electronic time limit having the mutual exclusion relationship may be started.

Dependency relationship: it may refer to a time limit rule having a dependency relationship with another time limit rule. For example, when a writing task corresponding to a certain electronic time limit needs to be started, the writing task corresponding to another electronic time limit with the dependency relationship can be started at the same time; for another example, when it is necessary to stop a writing task corresponding to one electronic time limit, the writing task corresponding to another electronic time limit in which the dependency relationship exists may be stopped at the same time.

"customization requirement of hospitals for electronic medical records": the method is characterized in that the triggering conditions are configured or processed in a personalized way according to the requirements of hospitals, so that the generated electronic medical record meets the use requirements of the hospitals.

For example, the requirements for electronic medical records in some hospitals include: admission records need to be completed within 24 hours of admission; discharge records need to be completed within 24 hours of discharge. Thus, based on the above requirements, it is necessary to write an admission record and an discharge record when the patient discharge time minus the patient admission time is less than 24 hours.

However, current hospital customization requirements for electronic medical records include: and in the case that the patient discharge time minus the patient admission time is less than 24 hours, only one admission and discharge record needs to be written. Therefore, based on the customizing requirement of the hospital on the electronic medical record, the starting triggering conditions of the electronic medical record related to the admission and discharge records are as follows: patient discharge time-patient admission time < = 24h at patient discharge, and admission record uncommitted- > enabled; others-not enabled.

It should also be appreciated that the customization requirements may also be referred to as personalization requirements, may also be referred to as special requirements, may also be referred to as specification requirements, etc.

The following are flexible definition and scalability related schemes of time limit rules:

first, the time limit requirements for writing each electronic medical record document are different. For example, the admission record, re-admission record or records should be completed within 24 hours after the patient is admitted; for another example, a patient at risk records the course of a disease at least once a day; for another example, a patient with a severe disease records the course of the disease at least once every two days; for another example, a phase summary is required at least once a month.

And, every time a time limit rule is added/modified, because the types of medical records required to be detected are different (for example, the admission records or the disease course records) or the time for starting tasks is different (for example, the admission time or the time for changing the state of a patient, etc.), or the methods required by hospitals to judge timeout have a slight gap, the code is rewritten to realize, so that the workload of research and development test and redeployment is increased, and additional quality risks (such as problems caused by the change of project compiling and packaging environments, etc.) are brought.

In order to solve the problem, common time limit rules need to be summarized, common attributes are extracted for expansion design, a basic model of the time limit rules is established, and the model is defined in software and maintained.

The following are some common time limit rules:

the counting record of the operation should be completed immediately after the operation is finished;

the rescue record is full and full within 6 hours after the rescue is finished;

the first course of disease recording should be completed within 8 hours of patient admission;

the admission record, the readmission record or records should be completed within 24 hours after the patient is admitted;

the entry and discharge records within 24 hours should be completed within 24 hours after the patient discharge;

Surgical recording should be completed within 24 hours after surgery;

discharge records should be completed within 24 hours after patient discharge;

the first ward round record of the attending physician should be completed within 48 hours of the patient admission;

the first ward-round record of the primary physician should be completed within 72 hours of the patient admission;

the medical record discussion record of death should be completed within one week of death of the patient;

preoperative discussions must be completed prior to surgery.

The above rules are analyzed in grammar, and the following statement structure commonalities are found:

the "medical record type" is completed in the "event occurrence time" + "cycle time" period.

In order to facilitate understanding of the embodiments of the present application, a description is given below with specific examples.

For example, for a time limit of "the surgical inventory record should be completed immediately after the end of the surgery," it can be translated into: the operation counting record is completed in the operation ending time and the operation ending time plus the period time. Wherein the instant completion can be achieved by setting the cycle time to 5 minutes, 30 minutes, 2 hours, etc.

Here, the "operation end time" may represent the start time of the "operation count record", and the "operation end time" + "cycle time" may represent the end time of the "operation count record".

Correspondingly, other relevant descriptions are similar and will not be described in detail later. For example, "patient admission time" may represent a start time of "first course record" and "patient admission time" + "8 hours" may represent an end time of "first course record".

For another example, for a time period of "first course of disease record should be completed within 8 hours of patient admission" it can be translated into: the "first course of disease" is completed within the "patient admission time", "patient admission time" + "8 hours".

It should be understood that 8 hours may also be replaced with other times (e.g., 10 hours, 12 hours, etc.), and embodiments of the application are not so limited.

For another example, for a time limit of "preoperative must complete preoperative discussion," it can be translated into: the "preoperative discussion record" needs to be completed within the "operation start time", "operation start time" + "cycle time".

It should be noted here that the cycle time may be set to a negative number (e.g., -2 hours, etc.), and then the preoperative discussion record must be completed within "2 hours before the start of the procedure, the start of the procedure time".

Thus, the basic definition of the rules should contain the classification information, trigger events, start times, and cycle times of the electronic medical records.

And, can also make further expansion from the rule already abstracted, support periodic medical record rule and other extensions.

The following are some common periodic calendar rules:

the patient at risk records the course of the disease at least once a day;

a patient with severe disease records the course of the disease at least once every two days;

a patient with stable disease records the course of the disease at least once every 3 days;

at least one phase per month is required for the knot.

The following are related schemes of the round robin rule operating mechanism, specifically:

the first task run (first period) of the time limit of the periodic medical record is generated by event triggering as is the non-periodic medical record rule. For example, for a rule of "patient at risk record of disease at least once a day," the first periodic task initiation of the rule is generated by a patient admission event, and the second and subsequent task runs are generated based on the deadline of the previous cycle. And the patient's record of the patient at least once a day can be translated into the patient record which needs to be completed in the last patient record completion time and the last patient record completion time plus 48 hours.

Here, the start time of the first cycle is the patient admission time. I.e. "first course of disease recording" is to be completed within "patient admission time", "patient admission time" + "48 hours".

It should be noted that the creation of each periodic task is started when the last periodic task ends, but it should be noted that the start time of the next period (in which a disease record should be written) may be equal to or earlier than the end time of the last period. For example, if the medical record of the previous cycle is not completed after timeout, the end time of the previous cycle is used as the start time of the next cycle, and if the medical record of the previous cycle is not completed after timeout, the completion time of the medical record of the previous cycle is used as the time of the next cycle.

Furthermore, the following are related schemes of the loop termination mechanism, specifically:

and (3) circulating time limit monitoring tasks corresponding to medical records, and stopping the time limit monitoring tasks in certain scenes. For example, there is no continuous course record three days after operation, so the highest cycle number needs to be increased in the definition of the rule, and in order to improve the expansibility of the system, the setting of the cycle condition is also increased, that is, the time limit task of the next cycle is started only if the cycle number does not reach the preset number and the cycle condition is met.

In addition, the following are related schemes of other extensions of the rules, specifically:

For rule enablement and disablement conditions, in some cases, there are constraints of other dynamic conditions in addition to event triggering. For example, the rule that the record of discharge in 24 hours should be completed within 24 hours after discharge of the patient is activated when the discharge event of the patient occurs, and the condition of discharge time-discharge time < = 24 hours needs to be judged to be activated, and accordingly, the rule is stopped, so that the condition is restricted.

Thus, start trigger conditions and stop trigger conditions are added to the basic definition of the rule. Only if the event and trigger conditions are met will the corresponding time-limited task (or writing task called electronic medical record) be started/stopped.

And, for the applicable scope of the rule, since the definition of the rule may be only applicable to a specific business department, the definition of the rule increases the applicable department scope.

And, for the custom extension method, "rule enable trigger condition", "rule stop trigger condition" and "rule loop execution condition" from the rule definition described above. With different rule contents, the required trigger-dependent conditions and calculation modes are different, and the condition contents can be configured by adopting a Groovy script in order to improve the scalability and flexibility of the system. Further, the Groovy script is a piece of code that can be compiled during the running of the program and then run, and that can also reference data and variables that are generated in the current runtime system.

In summary, the basic definition of the time limit rule should contain rule content, enable event, enable trigger condition, stop event, stop trigger condition, number of loops, loop condition, enable range, and violation time.

The following are relevant schemes for scheduling of time limit rules, in particular:

because mutually exclusive rules exist in the time limit rules. For example, the patient condition states of the patient are serious, critical and stable rules respectively corresponding to the patient condition records of the patient at least once every 2 days, the patient condition records of the patient at least once every day, and the patient condition records of the patient at least once every 3 days, and the three rules cannot be operated simultaneously because the patient has only one state at the same time, otherwise, under the condition that the patient condition records are not written for 3 days, the system is caused to judge that the doctor violates 3 rules and execute corresponding performance deductions, so that the performance scores are deducted for 3 times due to the same defect.

To solve such problems, a scheduling mechanism of time limit rules, i.e., defining relationships between time limit rules, is introduced. The settings of the current actions are three of enable, stop and reset (timer restart), see in particular the relevant description of table 1 below, and table 1 is only a simple example.

TABLE 1

By the configuration of the scheduling, the situation that mutual exclusion and dependence exist among time limit rules can be solved. Taking the above example, when the patient state changes from patient to patient risk, the event change starts the monitoring task of rule "patient at patient risk at least once a day" and the content of the schedule configuration table (i.e. table 1) is queried, two pieces of data are found to match "rule 1 specific content", and the rule corresponding to "rule 2 specific content" is obtained for each piece of data, for example, the patient with stable disease at least once a 3 day patient record. And stopping the time limit task corresponding to the patient with stable illness state at least once every 3 days according to the stop instruction of the action of the rule 2, thereby completing the scheduling of the time limit task through three steps.

It should be noted that, although table 1 is described by taking two time limit rules of mutually exclusive relationships as an example, those skilled in the art should understand that the rule scheduling configuration table may further include other settings of time limit rules of association relationships (e.g., dependency relationships, etc.) that may be defined, and the embodiment of the present application is not limited thereto.

Referring to fig. 1, fig. 1 shows a specific flowchart of a task execution method based on an electronic medical record shown in the present application. The task execution method as shown in fig. 1 may be executed by a task execution device, and a specific device of the task execution device may be set according to actual requirements, and the embodiment of the present application is not limited thereto. For example, the task performing device may be a computer or a server. Specifically, the task execution method includes:

Step S110, under the condition that the trigger event is monitored, a time limit rule table is queried based on the trigger event, and a first target time limit rule corresponding to the trigger event is acquired. The time limit rule table comprises a plurality of time limit rules which are configured in advance, and each time limit rule in the plurality of time limit rules is used for representing the time limit rule of the electronic medical record of the corresponding target hospital.

It should be understood that the specific time of the triggering event may be set according to actual requirements, and embodiments of the present application are not limited thereto.

Optionally, the trigger event may also include an enable trigger event and a stop trigger event. The triggering event can be any one event of an in-department safe bed event, an out-of-hospital event, a death event, an invasive diagnosis and treatment operation completion event, a wound closing event, an operation ending event, an operation starting event, an emergency consultation sending event, an emergency consultation ending event, a conventional consultation application sending event, a rescue ending event, a department transfer-out event, a critical doctor's advice event and a post-operation doctor's advice event; the stop trigger event may include discharge, admission record commit event and death.

It should also be understood that the specific content included in the time limit rule may be set according to actual requirements, and embodiments of the present application are not limited thereto.

Alternatively, the temporal rules can include medical record classifications, violation thresholds, violation logic, enablement ranges, enablement trigger events, enablement trigger conditions, stop trigger events, stop trigger conditions, scheduling parameters, deadline loop conditions, and the like.

For example, for a rule that a 24 hour in-discharge record should be completed within 24 hours after patient discharge, the medical record classification may be "24 hour in-discharge record" and the violation threshold is "24 hours" and the violation logic is "no in-discharge record within 24 hours" and the "in-discharge record within 24 hours commit time-patient discharge time >24 hours" and the enabling range is "all departments" and the enabling trigger event is "discharge" and the enabling trigger condition is "patient discharge time out of time < = 24 hours and the admission record is not committed" - - - > enabled and the other- - > not enabled "and the stop trigger event is" none "and the stop trigger condition is" event code, discharge time, patient in-registration ID "and the deadline cycle condition is" not applicable ".

For another example, for the rules of "Admission record, re-Admission record should be completed within 24 hours after patient Admission," medical records classification may be "Admission record, re-Admission record," and violation logic is "Admission: the admission record is not existed, and the discharge time-admission time is more than 24 hours; the submitting time of admission record-patient admission time >24h, and the discharge time-admission time >24h; not discharged: the admission record does not exist; the "admission record" commit time-patient admission time >24h ", and the enabling range is" all departments ", and the enabling trigger event is" in triathlon ", and the enabling trigger condition is" none ", and the stop trigger event is" discharge or admission record commit event ", and the stop trigger condition is" discharge or admission record commit event ", and the scheduling parameters are" event code, event occurrence time (in triathlon time), patient admission registration ID ", and the deadline cycle condition is" inapplicable ".

It should also be understood that, based on the trigger event querying the time limit rule table, a specific process of acquiring the first target time limit rule corresponding to the trigger event may be set according to actual requirements, and embodiments of the present application are not limited thereto.

Alternatively, in the event that a triggering event is heard, information of a department (e.g., an operating room) where the target patient is located may be acquired, and a first target time limit rule is determined from a plurality of time limit rules based on the triggering event and the department information.

That is, the trigger event and the time limit rule table may be matched to obtain at least one time rule that is matched. And, because each time limit rule can include an enabling range, at least one time rule matched can be screened based on the information of the department where the target patient is located, so as to obtain a final first target time limit rule. For example, if the information of the department where the target patient is located is within the enabled range of the matched current time limit rule, the matched current time limit rule is reserved; for another example, if the information of the department where the target patient is located is not within the enabled range of the matched current time limit rule, deleting the matched current time limit rule.

Step S120, determining whether the first target time limit rule includes a trigger condition. The triggering condition is configured based on the customization requirement of the target hospital on the electronic medical record, and the first target time limit rule can include the triggering condition or not.

It should be understood that the specific conditions included in the triggering condition may be set according to actual requirements, and the embodiments of the present application are not limited thereto.

Alternatively, the trigger conditions may include an enable trigger condition and a stop trigger condition.

For example, for the rule that discharge records should be completed within 24 hours after patient discharge, the activation trigger condition is "when patient discharge, discharge records have been submitted- - - - > activated; at patient discharge, the admission record was not submitted, and discharge time-admission time >24 h- > was enabled, and discharge time-admission time < = 24 h- > rule, covered.

Step S130, if the first target time limit rule is determined to comprise a trigger condition, updating a task list for storing writing tasks of the electronic medical record based on the trigger condition and the rule scheduling configuration table under the condition that the trigger condition is met, and obtaining an updated task list. The rule scheduling configuration table is used for storing a plurality of pairs of time limit rules with mutual exclusion relation or dependency relation.

Optionally, in the case that the trigger condition includes an enabling trigger condition, first parameter information related to the enabling trigger condition is acquired, and whether the enabling trigger condition is satisfied is determined based on the first parameter information. If the starting triggering condition is met, adding a writing task of the electronic medical record corresponding to the first target time limit rule into a task list according to the rule scheduling configuration table; if the enabling trigger condition is not satisfied, no processing is performed and the current first target time limit rule can be skipped.

For example, when the first target time limit rule is "24 hours in which the discharge record should be completed within 24 hours after the discharge of the patient" and the activation trigger condition is "when the patient is discharged, discharge time-discharge time < = 24 hours, and the discharge record is not submitted- > activated; in other cases where "not enabled," the first parameter information may include discharge time, time of admission, and not submitted for admission records, so that if the trigger condition is met based on the first parameter, a writing task of the electronic medical record corresponding to "the discharge record should be completed within 24 hours after the patient is discharged" may be added to the task list.

It should be understood that, according to the rule scheduling configuration table, a specific method for adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list may be set according to actual requirements, and the embodiment of the application is not limited thereto.

Optionally, querying the rule scheduling configuration table by using the first target time limit rule to determine whether a second target time limit rule with a mutual exclusion relation with the first target time limit rule exists in the rule scheduling configuration table; the first target time limit rule and the second target time limit rule are two time limit rules corresponding to different illness states of the same target patient. If a second target time limit rule exists and a writing task of the electronic medical record corresponding to the second target time limit rule exists in the task list, adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list, and deleting the writing task of the electronic medical record corresponding to the second target time limit rule from the task list; if the second target time limit rule exists and the writing task of the electronic medical record corresponding to the second target time limit rule does not exist in the task list, the writing task of the electronic medical record corresponding to the first target time limit rule can be added into the task list only; if the second target time limit rule does not exist, adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list.

For another example, in the case where the first target time limit rule is "patient record of at least once every day of patient at risk" and "writing task of electronic medical record corresponding to patient record of at least once every two days of patient" exists in the task list, by referring to the schedule configuration table shown in table 1, determining that two second target time limit rules with mutual exclusion relation with the first target time limit rules are respectively 'patient with stable illness state record at least once every 3 days' and 'patient with severe illness state record at least once every two days', deleting writing tasks of electronic medical records corresponding to 'patient with severe illness state record at least once every two days' in a task list, and adding writing tasks of electronic medical records corresponding to 'patient with critical illness state record at least once every day' in the task list.

Optionally, querying the rule scheduling configuration table by using the first target time limit rule to determine whether a third target time limit rule with a dependency relationship with the first target time limit rule exists in the rule scheduling configuration table; the first target time limit rule and the third target time limit rule are two time limit rules corresponding to the same target patient in the same illness state. If the third target time limit rule exists and the writing task of the electronic medical record corresponding to the third target time limit rule does not exist in the task list, adding the writing task of the electronic medical record corresponding to the first target time limit and the writing task of the electronic medical record corresponding to the third target time limit rule into the task list respectively; if a third target time limit rule exists and a writing task of the electronic medical record corresponding to the second target time limit rule exists in the task list, adding the writing task of the electronic medical record corresponding to the first target time limit only in the task list; if the third target time limit rule does not exist, adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list.

For example, in the case where the first target time limit rule is "operation record should be completed within 24 hours after operation" and there is no "patient record of at least once a day of medical course for a patient at risk" in the task list, the recording time should be specific to the writing task of an electronic medical record corresponding to minute ", by referring to the schedule configuration table, it is determined that the third target time limit rule having a dependency relationship with the first target time limit rule is" patient record of at least once a day of medical course for a patient at risk "respectively, the recording time should be specific to minute", then it is possible to add "operation record should be completed within 24 hours after operation" in the task list "writing task of an electronic medical record corresponding to minute" and also add "patient record of at least once a day of medical course for a patient at risk" in the task list, and the recording time should be specific to the writing task of an electronic medical record corresponding to minute ". Wherein, the first target time limit and the third target time limit both represent two time limit rules of the same target patient in a disease state after operation.

And in the case that the trigger condition includes a stop trigger condition, acquiring second parameter information related to the stop trigger condition, and judging whether the stop trigger condition is satisfied based on the second parameter information. If the stopping triggering condition is met, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list according to the rule scheduling configuration table; if the stop trigger condition is not satisfied, no processing is performed.

It should be understood that, according to the rule scheduling configuration table, a specific method for deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list may also be set according to the actual requirement, and the embodiment of the application is not limited thereto.

Optionally, querying the rule scheduling configuration table by using the first target time limit rule to determine whether a fourth target time limit rule having a mutual exclusion relation with the first target time limit rule exists in the rule scheduling configuration table; if the fourth target time limit rule exists and the writing task of the electronic medical record corresponding to the fourth target time limit rule does not exist in the task list, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list, and adding the writing task of the electronic medical record corresponding to the fourth target time limit rule into the task list; if the fourth target time limit rule exists and the writing task of the electronic medical record corresponding to the fourth target time limit rule exists in the task list, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list; and if the fourth target time limit rule does not exist, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list.

Wherein the first target time limit rule and the fourth target time limit rule may be two rules triggered for a target event.

For example, in a case where a hospital has a customized requirement that a first ward round record is to be completed within 8 hours and a non-first ward round record (e.g., second, third, etc.) is to be completed within 48 hours, the first target time limit rule is "first ward round record is to be completed within 8 hours", the fourth target time limit rule is "non-first ward round record is to be completed within 48 hours", and the first target time limit rule and the fourth target time limit rule are mutually exclusive relationships. If the fourth target time limit rule exists in the rule scheduling configuration table and the writing task of the electronic medical record corresponding to the fourth target time limit rule does not exist in the task list, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list, and adding the writing task of the electronic medical record corresponding to the fourth target time limit rule in the task list, namely, the first ward round record is completed at the moment, the non-first ward round record needs to be executed, and the time limit requirement of the first ward round record is different from the time limit requirement of the non-first ward round record, so that the writing task of the electronic medical record corresponding to the first target time limit rule needs to be deleted, and the writing task of the electronic medical record corresponding to the fourth target time limit rule is added in the task list.

It should be noted here that different hospitals may have different time limit rule requirements, and may also have specific customization requirements.

Optionally, querying the rule scheduling configuration table by using the first target time limit rule to determine whether a fifth target time limit rule with a dependency relationship with the first target time limit rule exists in the rule scheduling configuration table; the first target time limit rule and the fifth target time limit rule are two time limit rules corresponding to the same target patient in the same illness state. If the fifth target time limit rule exists and the writing task of the electronic medical record corresponding to the fifth target time limit rule exists in the task list, deleting the writing task of the electronic medical record corresponding to the first target time limit rule and the writing task of the electronic medical record corresponding to the fifth target time limit rule from the task list; if the fifth target time limit rule exists and the writing task of the electronic medical record corresponding to the fifth target time limit rule does not exist in the task list, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list; and if the fifth target time limit rule does not exist, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list.

It should be noted here that each writing task in the task list may include a rule ID, a patient ID, a medical record category ID, a time entity, an advance notice time, and a violation threshold, etc.

Step S140, executing the tasks in the updated task list at regular time to obtain a task execution result.

Specifically, in the case where the current task in the updated task list expires (e.g., a 24-hour point in time), it may be determined whether the current task has been executed by querying the task execution record, and the task execution result may be saved. And if the loop is needed, continuing to execute the process when the next expiration occurs.

In addition, in the case that the first target time limit rule does not include a trigger event, the matched time limit rule may be used as the first target time limit rule, and the matched rule does not need to be screened through the trigger condition. And in the event that the trigger event is an enable trigger event, matching the first target time limit rule with the rule scheduling configuration table to determine how to execute the rule subsequently; and under the condition that the trigger event is a disabling trigger event, disabling the writing task of the electronic medical record corresponding to the first target time limit rule in the task list.

Therefore, by means of the technical scheme, the method and the device can flexibly realize flexible scheduling among time-limited tasks, and reduce development workload.

And because the technology of running dynamic configuration is used, software is not required to be recompiled and released under normal conditions, so that the software reissuing period is shortened, and the quality risk of online is reduced.

It should be understood that the above task execution method is only exemplary, and those skilled in the art can make various modifications according to the above method, and the solutions after the modifications also belong to the protection scope of the present application.

The present application provides a storage medium having stored thereon a computer program which, when executed by a processor, performs the method of the embodiments.

The present application also provides a computer program product which, when run on a computer, causes the computer to perform the method of the method embodiments.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions.

It should be noted that in the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the terms first, second, third, etc. are for convenience of description only and do not denote any order. These terms may be understood as part of the component name.

Furthermore, it should be noted that in the description of the present specification, the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to a specific feature, structure, material, or characteristic described in connection with the embodiment or example being included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art upon learning the basic inventive concepts. Therefore, the appended claims should be construed to include preferred embodiments and all such variations and modifications as fall within the scope of the invention.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, the present invention should also include such modifications and variations provided that they come within the scope of the following claims and their equivalents.

Claims

1. The task execution method based on the electronic medical record is characterized by comprising the following steps of:

under the condition that a trigger event is monitored, inquiring a time limit rule table based on the trigger event, and acquiring a first target time limit rule corresponding to the trigger event; the time limit rule table comprises a plurality of time limit rules which are pre-configured, and each time limit rule in the time limit rules is used for representing the time limit rule of the electronic medical record of the corresponding target hospital;

judging whether the first target time limit rule comprises a triggering condition or not; the triggering condition is configured based on the customization requirement of the target hospital on the electronic medical record;

If the first target time limit rule is determined to comprise the trigger condition, updating a task list for storing writing tasks of the electronic medical record based on the trigger condition and a rule scheduling configuration table under the condition that the trigger condition is met, and obtaining an updated task list; the rule scheduling configuration table is used for storing a plurality of pairs of time limit rules with mutual exclusion relation or dependency relation;

the triggering conditions comprise stopping triggering conditions, and second parameter information related to the stopping triggering conditions is acquired; judging whether the stop triggering condition is met or not based on the second parameter information; if the stopping triggering condition is met, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list according to the rule scheduling configuration table;

querying the rule scheduling configuration table by utilizing the first target time limit rule to determine whether a fourth target time limit rule which has a mutual exclusion relation with the first target time limit rule exists in the rule scheduling configuration table; if the fourth target time limit rule exists and the writing task of the electronic medical record corresponding to the fourth target time limit rule does not exist in the task list, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list, and adding the writing task of the electronic medical record corresponding to the fourth target time limit rule into the task list; if the fourth target time limit rule does not exist, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list;

And executing the tasks in the updated task list at regular time to obtain a task execution result.

2. The electronic medical record-based task execution method of claim 1, wherein the trigger event is an event related to a target patient; inquiring a time limit rule table based on the trigger event, and acquiring a first target time limit rule corresponding to the trigger event, wherein the method comprises the following steps:

acquiring department information of the target patient;

the first target time limit rule is determined from the plurality of time limit rules based on the trigger event and the department information.

3. The electronic medical record-based task execution method of claim 1, wherein the trigger condition includes enabling a trigger condition; under the condition that the trigger condition is met, updating a task list for storing writing tasks of the electronic medical record based on the trigger condition and the rule scheduling configuration table to obtain an updated task list, and obtaining the updated task list comprises the following steps:

acquiring first parameter information related to the enabling trigger condition;

judging whether the starting triggering condition is met or not based on the first parameter information;

And if the enabling triggering condition is met, adding the writing task of the electronic medical record corresponding to the first target time limit rule into the task list according to the rule scheduling configuration table.

4. The task execution method based on electronic medical records according to claim 3, wherein adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list according to the rule scheduling configuration table comprises:

querying the rule scheduling configuration table by utilizing the first target time limit rule to determine whether a second target time limit rule which has a mutual exclusion relation with the first target time limit rule exists in the rule scheduling configuration table; the first target time limit rule and the second target time limit rule are two time limit rules corresponding to the same target patient in different illness states;

if the second target time limit rule exists and the writing task of the electronic medical record corresponding to the second target time limit rule exists in the task list, adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list, and deleting the writing task of the electronic medical record corresponding to the second target time limit rule from the task list;

If the second target time limit rule does not exist, adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list.

5. The task execution method based on electronic medical records according to claim 3, wherein adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list according to the rule scheduling configuration table comprises:

querying the rule scheduling configuration table by using the first target time limit rule to determine whether a third target time limit rule with a dependency relationship with the first target time limit rule exists in the rule scheduling configuration table; the first target time limit rule and the third target time limit rule are two time limit rules corresponding to the same target patient in the same illness state;

if the third target time limit rule exists and the writing task of the electronic medical record corresponding to the third target time limit rule does not exist in the task list, respectively adding the writing task of the electronic medical record corresponding to the first target time limit rule and the writing task of the electronic medical record corresponding to the third target time limit rule in the task list;

If the third target time limit rule does not exist, adding the writing task of the electronic medical record corresponding to the first target time limit rule in the task list.

6. The task execution method based on electronic medical records according to claim 3, wherein the first target time limit rule includes classification information of the electronic medical records corresponding to the first target time limit rule, the trigger event, a start time and a cycle time.

7. The electronic medical record-based task execution method according to claim 1, wherein deleting the written task of the electronic medical record corresponding to the first target time limit rule from the task list according to the rule schedule configuration table comprises:

querying the rule scheduling configuration table by utilizing the first target time limit rule to determine whether a fifth target time limit rule with a dependency relationship with the first target time limit rule exists in the rule scheduling configuration table; the first target time limit rule and the fifth target time limit rule are two time limit rules corresponding to the same target patient in the same illness state;

if the fifth target time limit rule exists and the writing task of the electronic medical record corresponding to the fifth target time limit rule exists in the task list, deleting the writing task of the electronic medical record corresponding to the first target time limit rule and the writing task of the electronic medical record corresponding to the fifth target time limit rule from the task list;

And if the fifth target time limit rule does not exist, deleting the writing task of the electronic medical record corresponding to the first target time limit rule from the task list.

8. A storage medium having stored thereon a computer program which, when executed by a processor, performs the electronic medical record based task execution method of any of claims 1-7.