CN111212102A - Task push management method, device and system, storage medium and electronic equipment - Google Patents
Task push management method, device and system, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN111212102A CN111212102A CN201911205195.2A CN201911205195A CN111212102A CN 111212102 A CN111212102 A CN 111212102A CN 201911205195 A CN201911205195 A CN 201911205195A CN 111212102 A CN111212102 A CN 111212102A
- Authority
- CN
- China
- Prior art keywords
- task
- terminal
- information
- executed
- evaluation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 49
- 238000011156 evaluation Methods 0.000 claims abstract description 84
- 238000000034 method Methods 0.000 claims abstract description 31
- 238000012544 monitoring process Methods 0.000 claims abstract description 19
- 230000004044 response Effects 0.000 claims abstract description 9
- 238000012545 processing Methods 0.000 claims description 14
- 230000010365 information processing Effects 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 2
- 230000003252 repetitive effect Effects 0.000 abstract description 4
- 238000005516 engineering process Methods 0.000 abstract description 2
- 230000008569 process Effects 0.000 description 9
- 230000000737 periodic effect Effects 0.000 description 7
- 238000012790 confirmation Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000036541 health Effects 0.000 description 4
- 230000007774 longterm Effects 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000035479 physiological effects, processes and functions Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 230000005802 health problem Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000002045 lasting effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000474 nursing effect Effects 0.000 description 1
- 230000000149 penetrating effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 238000012502 risk assessment Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000007619 statistical method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Tourism & Hospitality (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Data Mining & Analysis (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The present disclosure relates to the field of computer technologies, and in particular, to a task push management method, a task push management device, a task push management system, a storage medium, and an electronic device. The method comprises the following steps: in response to a task creation request submitted by a first terminal, calling a rule engine to generate target task information; when the target task information is monitored, generating a task to be executed and pushing the task to a second terminal; when monitoring that the second terminal executes the task execution information generated after the task to be executed is executed, pushing the task execution information to the first terminal; and acquiring an evaluation task for the task execution information submitted by the first terminal, and pushing the evaluation task to a third terminal so that the third terminal can execute the evaluation task. The method disclosed by the invention can effectively reduce and avoid a large amount of repetitive labor and realize the automatic triggering of related tasks by the endogenous circulation.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a task push management method, a task push management device, a task push management system, a storage medium, and an electronic device.
Background
In the field of the aged-care community, a large amount of evaluation and statistics work needs to be carried out on residents when the residents live in the community and in the living process. Due to the complexity of the resident conditions of the aged-care community, the evaluation and statistics work is more in types and quantity. In the prior art, a manual mode is mostly adopted when evaluation management work is performed, and due to the working mode, the workload is huge, the error and leakage rate is high, and the problems of data errors and data leakage also exist in data transmission at different working stages.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The present disclosure is directed to a task push management method, a task push management apparatus, a task push management system, a storage medium, and an electronic device, which implement rule engine-based task push and management, and further overcome one or more problems due to limitations and disadvantages of the related art, at least to some extent.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.
According to a first aspect of the present disclosure, there is provided a task push management method, including:
in response to a task creation request submitted by a first terminal, calling a rule engine to generate target task information;
when the target task information is monitored, generating a task to be executed and pushing the task to a second terminal;
when monitoring that the second terminal executes the task execution information generated after the task to be executed is executed, pushing the task execution information to the first terminal;
and acquiring an evaluation task for the task execution information submitted by the first terminal, and pushing the evaluation task to a third terminal so that the third terminal can execute the evaluation task.
In an exemplary embodiment of the disclosure, the invoking a rule engine to generate target task information in response to a task creation request submitted by a first terminal includes:
receiving the task creation request generated by the first terminal according to user information;
calling a rule engine to configure target task information according to the user information; the target task information comprises at least one subtask, and trigger time and task configuration data corresponding to the subtask.
In an exemplary embodiment of the present disclosure, when the target task information is monitored, generating a task to be executed and pushing the task to a second terminal includes:
and acquiring the triggering time of the subtask, generating a task to be executed according to task configuration data corresponding to the subtask when the triggering time is monitored, and pushing the task to be executed to the second terminal.
In an exemplary embodiment of the present disclosure, the user information further includes abort execution information; the method further comprises the following steps:
and calling the rule engine to generate a abandoning record task according to the abandoning execution information, pushing the abandoning record task to the first terminal, and storing the abandoning record task to a target database.
In an exemplary embodiment of the present disclosure, when the task execution information generated after the second terminal executes the task to be executed is monitored, the pushing the task execution information to the first terminal includes:
and monitoring a target database, and calling a rule engine to push the task execution information to the first terminal when the task execution information uploaded by the second terminal is identified.
In an exemplary embodiment of the present disclosure, the method further comprises:
and responding to the update request of the first terminal to the target task information, and updating the task to be executed for the second terminal to execute the updated task to be executed.
According to a second aspect of the present disclosure, there is provided a data processing apparatus comprising:
the task creation request processing module is used for responding to a task creation request submitted by the first terminal and calling a rule engine to generate target task information;
the to-be-executed task generating module is used for generating a to-be-executed task and pushing the to-be-executed task to the second terminal when the target task information is monitored;
the task execution information processing module is used for pushing the task execution information to the first terminal when monitoring that the task execution information generated after the second terminal executes the task to be executed is monitored;
and the evaluation task generating module is used for acquiring the evaluation task for the task execution information submitted by the first terminal and pushing the evaluation task to a third terminal so that the third terminal can execute the evaluation task.
According to a third aspect of the present disclosure, there is provided a task push management system, including:
a server side;
the first terminal is used for creating a request according to a task generated by user information and submitting the request to the server so that the server calls a rule engine to generate target task information;
the second terminal is used for executing the task to be executed which is issued by the server and generated according to the target task information, and generating task execution information which is used for the server to push the task execution information to the first terminal;
and the third terminal is used for executing the evaluation task generated by the first terminal according to the task execution information.
According to a fourth aspect of the present disclosure, there is provided a storage medium having stored thereon a computer program which, when executed by a processor, implements the task push management method described above.
According to a fifth aspect of the present disclosure, there is provided an electronic device comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the above-mentioned task push management method via execution of the executable instructions.
In the task push management method provided by an embodiment of the disclosure, a rule engine is configured at a server side, and when a task creation request submitted by a first terminal is received, the rule engine is called to generate target task information; generating a task to be executed according to the local target task information and pushing the task to the second terminal; when monitoring that the second terminal executes the task execution information generated after the task to be executed is executed, pushing the task execution information to the first terminal; and acquiring an evaluation task for the task execution information submitted by the first terminal, and pushing the evaluation task to a third terminal so that the third terminal can execute the evaluation task. Therefore, after the first terminal triggers a task, the related task information can be automatically triggered and pushed to the second terminal and the third terminal. Therefore, a large amount of repetitive labor is effectively avoided, and the internal circulation automatic triggering related tasks are further realized.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.
Fig. 1 schematically illustrates a flowchart of a task push management method in an exemplary embodiment of the present disclosure;
FIG. 2 is a schematic diagram illustrating another task push management device according to an exemplary embodiment of the disclosure;
FIG. 3 is a schematic diagram illustrating a task push management system according to an exemplary embodiment of the disclosure;
FIG. 4 schematically illustrates a composition diagram of an electronic device in an exemplary embodiment of the disclosure;
FIG. 5 schematically illustrates a schematic diagram of a program product in an exemplary embodiment of the disclosure;
fig. 6 schematically illustrates a composition diagram of an old-age community service system in an exemplary embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
At present, endowment community carries out full life cycle's aassessment through comprehensive and lasting to endowment community resident, and understanding resident's that can be accurate health problem and demand gather resident omnidirectional health data, and these data summarize and have presented resident's full picture, help the service team to know the resident more, formulate more effective, individualized care scheme. Because the state of residents in the aged-care community is constantly changing, the health condition of the residents can be timely determined by timely evaluating the residents or adjusting the timed evaluation plan according to the evaluation result, and meanwhile, the care plan of the residents can be continuously adjusted according to the evaluation result of the residents to provide targeted care service. In the prior art, the complexity of the resident situations of the aged-care community and the correspondingly generated huge evaluation quantity bring heavy evaluation plan management work for community service personnel. The evaluation carried out at regular time needs to be carried out manually, and the planning of regular evaluation is also needed to be carried out manually according to the evaluation result, so that the working mode has huge workload and high error and leakage rate. For the current situation, a demand for an information rule management platform capable of providing evaluation trigger rule management is very urgent.
For the problems in the prior art, the present exemplary embodiment first provides a task push management method, which can be applied to triggering and managing tasks. Referring to fig. 1, the task push management method may include the following steps:
step S11, responding to the task creating request submitted by the first terminal, and calling a rule engine to generate target task information;
step S12, when the target task information is monitored, generating a task to be executed and pushing the task to the second terminal;
step S13, when monitoring that the task execution information generated after the second terminal executes the task to be executed, pushing the task execution information to the first terminal;
step S14, obtaining an evaluation task for the task execution information submitted by the first terminal, and pushing the evaluation task to a third terminal, so that the third terminal executes the evaluation task.
According to the task push management method provided by the embodiment of the invention, the rule engine is configured at the server side, and when a task creation request submitted by a first terminal is received, the rule engine is called to generate target task information; generating a task to be executed according to the local target task information and pushing the task to the second terminal; when monitoring that the second terminal executes the task execution information generated after the task to be executed is executed, pushing the task execution information to the first terminal; and acquiring an evaluation task for the task execution information submitted by the first terminal, and pushing the evaluation task to a third terminal so that the third terminal can execute the evaluation task. On one hand, after the first terminal triggers a task, the related task information can be automatically triggered and pushed to the second terminal and the third terminal; and further realizing the automatic triggering of related tasks by the internal circulation. On the other hand, a large amount of repetitive labor is effectively reduced and avoided, and the task management efficiency is improved.
Hereinafter, each step in the task push management method in the present exemplary embodiment will be described in more detail with reference to the drawings and the embodiments.
Step S11, in response to the task creation request submitted by the first terminal, calls the rules engine to generate target task information.
In this exemplary embodiment, the data processing method may be executed on a server side, and may be applied to pushing tasks automatically and normatively for key events of the aged-care community clients and comprehensive situations (including multidimensional factors such as physiology, psychology and social contact) obtained through evaluation.
In this exemplary embodiment, the first terminal may be an intelligent terminal device on the first user side in the senior citizen community, for example, the first user may be a life manager for managing residents, creating tasks, and the like. Specifically, the step S11 may include:
step S111, receiving the task creation request generated by the first terminal according to the user information;
step S112, calling a rule engine to configure target task information according to the user information; the target task information comprises at least one subtask, and trigger time and task configuration data corresponding to the subtask.
The user information may be basic information of a resident, for example. When a resident enters a community area, a life manager can submit a task creating request to a server end through a first terminal, and the task creating request can contain basic information of the resident and a physical examination task creating request aiming at the resident; the physical examination task creation request can also include physical examination configuration data, such as physical examination time, physical examination type, and the like. After receiving the task creation request, the server side can call a rule engine, and generate a corresponding target execution task based on the request. Further, the target execution task may be a plurality of subtasks for regular physical examination, including physical examination time, physical examination content, and the like of each of the physical examination subtasks.
Or, in other exemplary embodiments of the present disclosure, when the resident first enters the community or is converted from the "care state" to the "independent living state", and the housekeeper uploads the resident basic information to the server via the first terminal and submits the resident creation request, the server may call the rule engine according to the resident creation request, and feed back a task of "physical examination item confirmation" to the first terminal; and displaying the task content in the interactive interface of the first terminal. The life butler submits the data generation task creation request of the physical examination time, the physical examination type and the like of the user at the first terminal according to the task of physical examination item confirmation. After receiving the task penetrating request, the server side calls a rule engine to configure corresponding target task information according to the information and establishes at least one subtask.
Alternatively, in other exemplary embodiments of the present disclosure, the user information described above may further include the abort execution information. Specifically, the abandonment execution information may be abandonment physical examination execution information. The task creation request may be a discard task creation request generated by the life butler based on the to-be-discarded physical examination execution information. The server side can call the rule engine after receiving the request, identify the abandoning record task which is generated after the execution information is abandoned currently, send the abandoning record task to the first terminal, confirm the abandoning record task by the resident, and upload the confirmation information to the target database.
And step S12, when the target task information is monitored, generating a task to be executed and pushing the task to the second terminal.
In the present exemplary embodiment, for the above subtasks, specific task information may be added to a task list in the target database. The tasks are executed in sequence by reading the task list. The task information may include a trigger time of the subtask. The server side can monitor the task list, so that when the current time is monitored to reach the triggering time of a subtask, a task to be executed is generated according to task configuration data corresponding to the subtask and is pushed to the second terminal.
Step S13, when monitoring that the task execution information generated after the second terminal executes the task to be executed, pushing the task execution information to the first terminal.
In this exemplary embodiment, the second terminal may be a community doctor user who performs a physical examination task. After receiving a specific task to be executed, a community doctor user can perform physical examination on corresponding residents, collect a specific physical examination result and generate a physical examination record sheet as task execution information. Wherein, the physical examination record sheet can comprise: the physical examination time, the physical examination type, the physical examination information, the evaluation conclusion, the periodic evaluation suggestion and the like. And storing the information to a target database.
The server side can monitor the target database in real time and recognize the task execution information through user identification or keyword words. After the corresponding task execution information is identified, a rule engine is called, an 'evaluation judgment task' is generated according to a preset rule, and the 'evaluation judgment task' is fed back to a first terminal, namely a life manager user side, in the form of a task form.
Step S14, obtaining an evaluation task for the task execution information submitted by the first terminal, and pushing the evaluation task to a third terminal, so that the third terminal executes the evaluation task.
In this exemplary embodiment, for example, the above-mentioned "evaluation judgment task" may be an evaluation judgment task generated according to a "periodic evaluation suggestion" sent by the second terminal. For example, periodic evaluation is simplified, i.e., a timed evaluation task is generated, but the evaluation content is simplified and relatively less; complete periodic evaluation, namely generating a timing evaluation task, wherein the evaluation content is all selectable content; or for exempt evaluation, i.e., no evaluation task is generated.
After receiving the task, the first terminal can call the rule engine to determine a specific timing evaluation task according to the task execution information. When the timing evaluation task includes a plurality of timing subtasks, the plurality of timing subtasks may be saved in a task list of the target database. And sending the evaluation result to the third terminal at regular time so that the third terminal can execute the evaluation subtask at regular time and generate the evaluation result. The server side can store the evaluation result in the target database and is associated with the corresponding residents, so that the evaluation data can be conveniently retrieved and checked. For example, the assessment content may include a care level assessment, a fall risk assessment, an improved pap index (MBI) assessment, and the like.
Based on the above, in the present exemplary embodiment, the life steward user may also submit an update request of the target task information at the first terminal, for example, change a specific physical examination time, and correspondingly modify the sub-task trigger time, so that the server side may perform monitoring according to the updated time and trigger the task to be executed. For example, the planned medical examination time is delayed due to the residents going out.
In this exemplary embodiment, the trigger rule of each task may be defined in advance in the rule engine. For example, a trigger rule for a timing task is defined, and a trigger keyword for each task, a trigger for updating a task, and the like are defined.
In this example embodiment, for example, the life manager user may submit an event "check in independent living area" or "change state to independent living area" at the first terminal, so that the server triggers a task "physical examination communication record form" and sends the task to the first terminal. The life butler user triggers a task creation request after the first terminal completes the task of 'physical examination communication record sheet', and the server triggers a task to be executed for the physical examination of the physical examination doctor user when detecting the planned physical examination/physical examination time in the form, generates a task of 'physical examination task sheet' and sends the task to the second terminal. The medical examination doctor user finishes medical examination on residents, submits the medical examination task list to the server side after finishing the medical examination task list, and pushes a periodic evaluation confirmation table list to the first terminal. After the first terminal finishes the regular evaluation confirmation table, the life housekeeper user generates a corresponding evaluation task and regularly pushes the evaluation task to the third terminal, so that the evaluator user executes a specific evaluation task.
In this exemplary embodiment, the task pushing management method described above may be applied to automatic pushing and management of tasks among different users in the endowment community service system. The endowment community can make a planned and periodic service scheme according to the time when residents begin to receive services and the comprehensive condition of the residents, so that tasks can be automatically and standardly pushed according to key events corresponding to the residents by the service scheme and the comprehensive condition (including multi-dimensional factors such as physiology, psychology and social contact) obtained through evaluation. The condition triggering rules and the result triggering rules of each task can be set through a graphical user interface without setting through a command line interface, and the triggering rules are endowed with considerable freedom and flexibility to meet the requirements of services more fully, and the requirements of new increase and change are responded more quickly. Referring to fig. 6, the endowment community service system 60 may include: an archival data center 603, a long-term care system 601, and a task management push system 602. The archiving data center can be used for storing system related data such as statistical analysis data, business data, user information and the like; the long-term care system can be used for processing resident identity data, medical advice execution data, early warning data and the like; the task management push system may be configured to execute the task push management method described in the foregoing embodiment, and may also store data required to execute the method, such as rule classification data, rule package data, and rule file data in a rule engine, evaluation test question data, evaluation tool, and data integration data required for user testing; and term content data and term relationship data, etc. Moreover, the archiving data center, the long-term care system and the task push management system can perform mutual data and instruction transmission and exchange through a presentation layer State conversion open interface (Restful API). In addition, the endowment community service system can also be added with other business systems, such as an alarm system and the like.
In this exemplary embodiment, the system architecture of the task push management system described above may include a presentation layer, a service layer, and a data layer. Wherein, the data layer can comprise a data storage layer and a data access layer; the data store layer may use a MySQL database and a MongoDB database. Correspondingly, the Data access layer can adopt a mybatis framework and a Spring Data framework. The service layer can execute term management service, rule management service and rule engine service, can adopt a Spring Boot framework and a Drools rule engine, deploys the Drools Work Bench rule engine and uses a KIE Server engine to realize remote calling. In particular, the long-term care system may be interfaced using the HTTP REST API interface. The presentation layer may be based on a VUE framework that allows the user to manage the terms and rules.
In this example embodiment, the rules engine may include event class rules and form class rules. Specifically, the event class rules may include: events, current state of health, applicable care level, trigger node definition (event occurrence, timed trigger and initialization), trigger time interval, trigger result, task period, and whether egress is smooth, etc. The user can customize the service according to the service requirement or the actual requirement. For example, task triggering of both "check-in" and "transfer mode" events may be supported; and can select the applicable state of business and care grade; tasks (i.e., the frequency of tasks) may be triggered based on the time at which the event occurs and at regular intervals; the task period can be selected, and the sequential adjustment can be carried out according to the outgoing; for example, when a resident is out of the community, the task execution time or the push time may be held down.
In addition, the above form class rules may include form topics, such as: condition form name, condition form topic, condition form answer (content, number), trigger result, trigger frequency, trigger interval time, task period, and whether to go out for a certain time. Further, the form class rules may include: business state, care level, trigger result, trigger frequency, trigger time interval, task period, whether to go out for a certain time, relative start time (form submission time, conditional form subject selectable time). When the event occurs, the corresponding form can be triggered and generated, and the corresponding task pushing is carried out. And triggering the corresponding tasks by identifying the titles or contents of the forms, and pushing the tasks to the corresponding preset users.
For example, the form class rules may include two broad classes, "form topic trigger" and "non-form topic trigger". The non-form topic trigger can be used for selecting an applicable state and a nursing grade, and the trigger of another form can be completed according to the execution completion condition of the conditional form or the time class data in the conditional form. The "form topic trigger" may complete the triggering of one form based on the options/fill-in of the specified topic in another form. The form item trigger and the non-form item trigger can select frequency, task period and relative start time, and can be adjusted according to the sequence of going out.
The task pushing management method can achieve automatic triggering of the evaluation task according to the event condition, automatic generation of the periodic evaluation task and automatic triggering of the evaluation plan according to the evaluation result. The method can help the business department to generate automatic operation tasks effectively according to preset rules, avoids complex and complicated manual calculation, and relieves health professionals from repetitive labor. The system can automatically calculate the generation time of each task of each resident according to the rules, and compared with manual calculation, the system can remarkably reduce the error rate (including the problems of omission, mismatching and the like) and ensure the accuracy of task generation. Moreover, because the task generates the guarantee of the accuracy, a foundation is laid for the manager to accurately assess the execution rate; and when the task plan rule changes, the system can cooperate with the quick response, so that the changing difficulty is reduced.
It is to be noted that the above-mentioned figures are only schematic illustrations of the processes involved in the method according to an exemplary embodiment of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
Further, referring to fig. 2, in an embodiment of the present example, there is also provided a task push management apparatus 20, including: a task creation request processing module 201, a to-be-executed task generating module 202, a task execution information processing module 203, and a reply evaluation task generating module 204.
Wherein:
the task creation request processing module 201 may be configured to invoke a rule engine to generate target task information in response to a task creation request submitted by the first terminal.
The to-be-executed task generating module 202 may be configured to generate a to-be-executed task and push the to-be-executed task to the second terminal when the target task information is monitored.
The task execution information processing module 203 may be configured to, when it is monitored that the second terminal executes the task to be executed, generate task execution information, and push the task execution information to the first terminal.
The evaluation task generating module 204 may be configured to obtain an evaluation task for the task execution information, which is submitted by the first terminal, and push the evaluation task to a third terminal, so that the third terminal executes the evaluation task.
In the present exemplary embodiment, the task creation request processing module 201 may include: a task creation request unit and a task configuration unit. Wherein:
the task creation request unit may be configured to receive the task creation request generated by the first terminal according to user information.
The task configuration unit may be configured to invoke a rule engine to configure target task information according to the user information; the target task information comprises at least one subtask, and trigger time and task configuration data corresponding to the subtask.
In this exemplary embodiment, the to-be-executed task generating module 202 may include: and a task monitoring unit. Wherein,
the task monitoring unit may be configured to acquire a trigger time of the subtask, generate a task to be executed according to task configuration data corresponding to the subtask when the trigger time is reached through monitoring, and push the task to the second terminal.
In the present exemplary embodiment, the user information further includes discard execution information; the apparatus 20 further comprises: the execution unit is discarded.
The abandonment execution unit may be configured to invoke the rule engine to generate an abandonment recording task according to the abandonment execution information, push the abandonment recording task to the first terminal, and store the abandonment recording task in a target database.
In the present exemplary embodiment, the task execution information processing module 203 may include: and a task execution information monitoring unit.
The task execution information monitoring unit can be used for monitoring a target database, and when the task execution information uploaded by the second terminal is identified, a rule engine is called to push the task execution information to the first terminal.
In the present exemplary embodiment, the apparatus 20 may further include: and a data updating module.
The data updating module may be configured to update the task to be executed in response to an update request of the first terminal for the target task information, so that the second terminal executes the updated task to be executed.
Further, referring to fig. 3, in an embodiment of the present example, there is provided a task push management system 30, which may include:
the server side 301.
The first terminal 302 may be configured to create a task request according to the user information, and submit the task request to the server, so that the server invokes the rule engine to generate the target task information.
The second terminal 303 may be configured to execute a to-be-executed task generated according to target task information and issued by the server, and generate task execution information, so that the server pushes the task execution information to the first terminal.
The third terminal 304 may be configured to execute an evaluation task generated by the first terminal according to the task execution information.
In some of the disclosed exemplary embodiments, the first terminal 302, the second terminal 303, and the third terminal 304 in the task push management system 30 may be terminals that perform a type of task, and may specifically include a plurality of terminal devices, where the terminal devices may be intelligent terminal devices such as a computer, a tablet computer, or a mobile phone. Data transmission between each terminal and the server 301 can be performed via the network 305.
The details of each module in the task pushing management device 20 are already described in detail in the corresponding task pushing management method, and therefore are not described herein again.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 400 according to this embodiment of the invention is described below with reference to fig. 4. The electronic device 400 shown in fig. 4 is only an example and should not bring any limitation to the function and the scope of use of the embodiments of the present invention.
As shown in fig. 4, electronic device 400 is embodied in the form of a general purpose computing device. The components of electronic device 400 may include, but are not limited to: the at least one processing unit 410, the at least one memory unit 420, and a bus 430 that couples various system components including the memory unit 420 and the processing unit 410.
Wherein the storage unit stores program code that is executable by the processing unit 410 to cause the processing unit 410 to perform steps according to various exemplary embodiments of the present invention as described in the above section "exemplary methods" of the present specification. For example, the processing unit 410 may perform a method as shown in fig. 1.
The storage unit 420 may include readable media in the form of volatile storage units, such as a random access memory unit (RAM)4201 and/or a cache memory unit 4202, and may further include a read only memory unit (ROM) 4203.
The storage unit 420 may also include a program/utility 4204 having a set (at least one) of program modules 4205, such program modules 4205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The electronic device 400 may also communicate with one or more external devices 50 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 400, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 400 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 450. Also, the electronic device 400 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 460. As shown, the network adapter 460 communicates with the other modules of the electronic device 400 over the bus 430. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with electronic device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.
Referring to fig. 5, a program product 500 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is to be limited only by the terms of the appended claims.
Claims (10)
1. A task push management method is characterized by comprising the following steps:
in response to a task creation request submitted by a first terminal, calling a rule engine to generate target task information;
when the target task information is monitored, generating a task to be executed and pushing the task to a second terminal;
when monitoring that the second terminal executes the task execution information generated after the task to be executed is executed, pushing the task execution information to the first terminal;
and acquiring an evaluation task for the task execution information submitted by the first terminal, and pushing the evaluation task to a third terminal so that the third terminal can execute the evaluation task.
2. The method of claim 1, wherein invoking a rules engine to generate targeted task information in response to a task creation request submitted by the first terminal comprises:
receiving the task creation request generated by the first terminal according to user information;
calling a rule engine to configure target task information according to the user information; the target task information comprises at least one subtask, and trigger time and task configuration data corresponding to the subtask.
3. The method according to claim 2, wherein the generating a task to be executed and pushing the task to the second terminal when the target task information is monitored comprises:
and acquiring the triggering time of the subtask, generating a task to be executed according to task configuration data corresponding to the subtask when the triggering time is monitored, and pushing the task to be executed to the second terminal.
4. The method of claim 2, wherein the user information further comprises abort execution information; the method further comprises the following steps:
and calling the rule engine to generate a abandoning record task according to the abandoning execution information, pushing the abandoning record task to the first terminal, and storing the abandoning record task to a target database.
5. The method according to claim 1, wherein the pushing the task execution information to the first terminal when monitoring task execution information generated after the second terminal executes the task to be executed comprises:
and monitoring a target database, and calling a rule engine to push the task execution information to the first terminal when the task execution information uploaded by the second terminal is identified.
6. The method of claim 1, further comprising:
and responding to the update request of the first terminal to the target task information, and updating the task to be executed for the second terminal to execute the updated task to be executed.
7. A task push management system, comprising:
a server side;
the first terminal is used for creating a request according to a task generated by user information and submitting the request to the server so that the server calls a rule engine to generate target task information;
the second terminal is used for executing the task to be executed which is issued by the server and generated according to the target task information, and generating task execution information which is used for the server to push the task execution information to the first terminal;
and the third terminal is used for executing the evaluation task generated by the first terminal according to the task execution information.
8. A task push management device, comprising:
the task creation request processing module is used for responding to a task creation request submitted by the first terminal and calling a rule engine to generate target task information;
the to-be-executed task generating module is used for generating a to-be-executed task and pushing the to-be-executed task to the second terminal when the target task information is monitored;
the task execution information processing module is used for pushing the task execution information to the first terminal when monitoring that the task execution information generated after the second terminal executes the task to be executed is monitored;
and the evaluation task generating module is used for acquiring the evaluation task for the task execution information submitted by the first terminal and pushing the evaluation task to a third terminal so that the third terminal can execute the evaluation task.
9. A storage medium having stored thereon a computer program which, when executed by a processor, implements a task push management method according to any one of claims 1 to 6.
10. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the task push management method of any of claims 1 to 6 via execution of the executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911205195.2A CN111212102A (en) | 2019-11-29 | 2019-11-29 | Task push management method, device and system, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911205195.2A CN111212102A (en) | 2019-11-29 | 2019-11-29 | Task push management method, device and system, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111212102A true CN111212102A (en) | 2020-05-29 |
Family
ID=70787071
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911205195.2A Pending CN111212102A (en) | 2019-11-29 | 2019-11-29 | Task push management method, device and system, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111212102A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708625A (en) * | 2020-06-16 | 2020-09-25 | 中国建设银行股份有限公司 | Multi-user task execution method, device, equipment and storage medium |
| CN111782248A (en) * | 2020-07-10 | 2020-10-16 | 上海淇毓信息科技有限公司 | Terminal application updating method and device and electronic equipment |
| CN113283742A (en) * | 2021-05-21 | 2021-08-20 | 建信金融科技有限责任公司 | Task allocation method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070174716A1 (en) * | 2005-12-30 | 2007-07-26 | Uwe Erdtmann | Health check monitoring process |
| CN105761058A (en) * | 2016-03-02 | 2016-07-13 | 广州支点网络科技股份有限公司 | Multi-type task control method and device in plan management |
| CN109087030A (en) * | 2018-09-14 | 2018-12-25 | 山东大学 | Realize method, General Mobile crowdsourcing server and the system of the crowdsourcing of C2C General Mobile |
| CN110069335A (en) * | 2019-05-07 | 2019-07-30 | 江苏满运软件科技有限公司 | Task processing system, method, computer equipment and storage medium |
-
2019
- 2019-11-29 CN CN201911205195.2A patent/CN111212102A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070174716A1 (en) * | 2005-12-30 | 2007-07-26 | Uwe Erdtmann | Health check monitoring process |
| CN105761058A (en) * | 2016-03-02 | 2016-07-13 | 广州支点网络科技股份有限公司 | Multi-type task control method and device in plan management |
| CN109087030A (en) * | 2018-09-14 | 2018-12-25 | 山东大学 | Realize method, General Mobile crowdsourcing server and the system of the crowdsourcing of C2C General Mobile |
| CN110069335A (en) * | 2019-05-07 | 2019-07-30 | 江苏满运软件科技有限公司 | Task processing system, method, computer equipment and storage medium |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708625A (en) * | 2020-06-16 | 2020-09-25 | 中国建设银行股份有限公司 | Multi-user task execution method, device, equipment and storage medium |
| CN111782248A (en) * | 2020-07-10 | 2020-10-16 | 上海淇毓信息科技有限公司 | Terminal application updating method and device and electronic equipment |
| CN111782248B (en) * | 2020-07-10 | 2023-09-19 | 上海淇毓信息科技有限公司 | Updating method and device of terminal application and electronic equipment |
| CN113283742A (en) * | 2021-05-21 | 2021-08-20 | 建信金融科技有限责任公司 | Task allocation method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11675484B2 (en) | Integrated data authentication system with an interactive user interface | |
| Wewerka et al. | Robotic process automation-a systematic mapping study and classification framework | |
| US11055619B2 (en) | Systems and methods for energy expert collaboration features | |
| CN110290189A (en) | A kind of container cluster management method, apparatus and system | |
| CN111212102A (en) | Task push management method, device and system, storage medium and electronic equipment | |
| CN109478266A (en) | For the resource allocation of database supply | |
| US10264120B2 (en) | Automated data collection and analytics | |
| US20170032296A1 (en) | Ultrasound resource management system | |
| CN109154937A (en) | The dynamic of inquiry response is transmitted as a stream | |
| US20180349179A1 (en) | Centralized flexible deployment system | |
| US9940361B2 (en) | Intelligent presence server systems and methods | |
| CN113158090A (en) | State detection system, method, device, equipment and readable storage medium | |
| US20200321084A1 (en) | Device, system, and method for optimizing pathology workflows | |
| US20210256861A1 (en) | Electronic infrastructure for digital content delivery and/or online assessment management | |
| CN110648105B (en) | Recommendation method and device based on data processing, electronic equipment and storage medium | |
| US11775910B2 (en) | Applied computer technology for high efficiency value stream management and mapping and process tracking | |
| US20150006200A1 (en) | System and method for providing automated home-based health services | |
| US20120278125A1 (en) | Method and system for assessing process management tools | |
| JP2020181238A (en) | Information analysis device, information analysis method, and information analysis program | |
| WO2018134680A1 (en) | System and method for integrating disparate computer systems and applications | |
| Hoffmann et al. | Socio-Behavioral Elements in Data-Driven Requirements Engineering: The Case of Enterprise Cloud Software. | |
| US11803358B1 (en) | Adaptive issue type identification platform | |
| US11797374B2 (en) | Systems and methods for recording major incident response information | |
| JPWO2019187019A1 (en) | Customer support system and customer support method | |
| US20170171030A1 (en) | System and method for digital optimization of electronic discovery |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200529 |
|
| RJ01 | Rejection of invention patent application after publication |