A cloud radiotherapy service management method and system based on process processing engine

Abstract

The present invention discloses a cloud radiotherapy service management method and system based on a process processing engine, and the method comprises the following steps: integrating a process processing engine into a project according to a project architecture, and generating a process processing engine class according to a process processing engine configuration class; establishing a process management model according to cloud radiotherapy core business operations, defining process nodes, and drawing cloud radiotherapy business processes according to process nodes and deploying the processes; and managing and operating instances of deployed cloud radiotherapy business processes by calling the process processing engine. This solution implements custom settings of processes and user tasks by adding a process processing engine, adopting unified process design, process modeling, process monitoring and standard process interfaces, and supporting different hospitals and different cancer types to configure different radiotherapy processes and process nodes, meeting the personalized needs of hospital radiotherapy departments, realizing business orchestration and integration, and improving the standardization and normalization of process management.

Description

Technical Field

[0001] The present invention belongs to the technical field of cloud radiotherapy, and specifically relates to a cloud radiotherapy service management method and system based on a process processing engine. Background Art

[0002] In order to realize the above-mentioned remote radiotherapy model, the common practice is mostly to introduce remote video conferencing to achieve collaboration between superiors and subordinates and conduct remote review and confirmation; or to customize the relevant table structure for a specific field. The process definition may be hardcoded or stored in a certain table to modify the process status and complete the process approval of the task.

[0003] However, there are many problems with the above solution. First, due to the differences in radiotherapy processes in different hospitals, the original solution cannot meet the diverse needs of hospital clinical business scenarios. Secondly, the above solution does not introduce a process processing engine, and it is necessary to define a large number of status codes and next-step responsible persons. Furthermore, if it is expanded in the future, and the next-step responsible person changes from a specific person to a group of specific organizations, a large amount of code needs to be modified. The codes are isolated, the business processes are not well reflected, the business processes that are too flexible are coded rigidly, and it is not easy to implement the corresponding processes.

[0004] At the same time, when the above remote radiotherapy service model is used in the normal workflow, the following problems are often encountered: lack of consideration when making demands, and continuous modification of processes after going online; organizational adjustments of the unit result in changes in business processes; business processes are relatively complex, with many states of use and prone to errors; responsible business processes require high logical thinking from the participants; the degree of workflow business coupling is too high and many scenarios are not applicable; the flow of each activity requires a rigid judgment of the next activity node and its operator; each operation requires maintenance of business data and process-related data; and there is a lack of data management, process monitoring and other functions. Summary of the invention

[0005] In view of the above-mentioned deficiencies in the prior art, the present invention provides a cloud radiotherapy service management method and system based on a process processing engine to solve the above-mentioned technical problems.

[0006] In order to solve the above technical problems or at least partially solve the above technical problems, the present invention adopts the following technical solutions:

[0007] A cloud radiotherapy service management method based on a process processing engine comprises the following steps:

[0008] S1: Integrate the process processing engine into the project according to the project architecture, and generate the process processing engine class according to the process processing engine configuration class;

[0009] S2: Establish a process management model based on the core business operations of cloud radiotherapy, define process nodes, draw cloud radiotherapy business processes based on process nodes, and deploy the processes;

[0010] S3: Manage the deployed cloud radiotherapy business process instances by calling the process processing engine.

[0011] In some embodiments, the process processing engine is a camunda process engine or an activiti process engine;

[0012] In some embodiments, the process processing engine also integrates a visual process design web page for drawing cloud radiotherapy business processes.

[0013] In some embodiments, the "generating a process processing engine class according to the process processing engine configuration class" in step S1 includes: using XML files for automatic configuration, automatically loading the process processing engine configuration class to initialize generation when the process processing engine starts; or manually calling an independent process processing engine configuration object in the process processing engine configuration.

[0014] In some embodiments, the process nodes include six nodes: target area delineation, delineation review, plan making, plan review, plan confirmation, and treatment completion.

[0015] In some embodiments, the “deployment” in step S2 includes the following steps:

[0016] S21: calling the deployment creation method in the operation process definition service in the process processing engine, obtaining the constructor deployed in the form of a file, and calling the deployment interface to obtain the unique identifier PRO_DEF_ID of the business process definition;

[0017] S22: Obtain process node information in the process through the business process keyword PROCESS_KEY;

[0018] S23: Create a process information table, a process processing engine information table, and a node information table in the project database to store process related information.

[0019] In some embodiments, the “managing operations on deployed cloud radiotherapy business process instances” in step S3 includes:

[0020] S31: Create a task information table in the project database to save detailed information of tasks associated with the current process node;

[0021] S32: Call the operation process instance service, obtain the process instance unique identifier in the task information table, and start the process instance;

[0022] S33: According to the unique identifier of the process node task instance, based on the defined process node and the drawn cloud radiotherapy business process, the current process node where the process node task instance is located is submitted, approved, rejected, returned or recalled.

[0023] In some embodiments, the submit operation in step S33 is applied after the target area delineation node and the plan making node, and is used to determine whether to update the task information to the next process node according to the exclusive gateway variable value;

[0024] The said operation acts on the outline review node and the plan review node, and is used to update the task information to the next process node;

[0025] The rejection, return or recall operation is used to update the task information to the specified process node.

[0026] In some embodiments, the specific process of the submission operation is to call the getVariables method in the operation process instance service, pass in the unique identifier of the process instance, obtain the global parameter variables of the current process instance, and update the exclusive gateway variable value; then call the complete method of the operation task service, pass in the unique identifier of the task instance and the global variables; use the @EventListener annotation method to listen to the current process node task information released by the process processing engine, and load the unique identifier of the "create" type task instance to the local task.

[0027] In some embodiments, the specific process of the operation is to call the complete method of the operation task service, pass in the unique identifier of the task instance, use the @EventListener annotated method to listen to the current process node task information released by the process processing engine, and load the unique identifier of the "create" type task instance to the local task.

[0028] In some embodiments, the specific process of the rejection, return or recall operation is to call the getActivityInstance method in the operation task service, pass in the process instance unique identifier, and obtain the process node instance object running in the current business process in the process processing engine; call the createHistoricActivityInstanceQuery interface in the query historical data service, pass in the current process instance unique identifier and the task type selected when drawing the process, query the list of historical process node instance objects, and find the specified process node unique identifier to be rejected, returned or recalled according to the process node sequence and completed historical data in the node information table, combined with the process instance global parameters; call the createProcessInstanceModification method in the operation process instance service, pass in the process instance unique identifier, obtain the process instance modification builder ProcessInstanceModificationBuilder, call the cancelActivityInstance method to cancel the process node task and pass in the taskDefinitionKey attribute of the activityInstance object, call the startBeforeActivity method, pass in the unique identifier of the process node to be started, and then call the execute method. At this time, the local method annotated with @EventListener will listen to the task information of the process node published by the process processing engine, and load the "create" type process node task unique identifier to the local task.

[0029] In a second aspect, the present disclosure also discloses a cloud radiotherapy service management system based on a process processing engine, including:

[0030] The engine integration module integrates the process processing engine into the project according to the project architecture, and generates the process processing engine class according to the process processing engine configuration class;

[0031] The process deployment module establishes a process management model based on the core business operations of cloud radiotherapy, defines process nodes, draws cloud radiotherapy business processes based on process nodes, and deploys the processes;

[0032] The process management module manages the instances of the deployed cloud radiotherapy business processes by calling the process processing engine.

[0033] In some embodiments, the process deployment module includes:

[0034] The deployment creation submodule is used to call the deployment creation method in the operation process definition service in the process processing engine, obtain the constructor deployed in the form of a file, and call the deployment interface to obtain the unique identifier PRO_DEF_ID of the business process definition;

[0035] The process node acquisition submodule is used to obtain the process node information in the process through the business process keyword PROCESS_KEY;

[0036] The information storage submodule is used to create a process information table, a process processing engine information table and a node information table in the project database to save process related information.

[0037] In some embodiments, the process management module includes:

[0038] The task information table creation submodule is used to create a task information table in the project database to save the task details associated with the current process node;

[0039] The process instance start submodule is used to call the process instance operation service, obtain the process instance unique identifier in the task information table, and start the process instance;

[0040] The operation submodule submits, approves, rejects, returns or recalls the current process node where the process node task instance is located according to the unique identifier of the process node task instance, based on the defined process node and the drawn cloud radiotherapy business process.

[0041] In some embodiments, the operation submodule further includes:

[0042] A submission unit, used to act on the target area delineation node and the plan making node, and to determine whether to update the task information to the next process node according to the exclusive gateway variable value;

[0043] Through the unit, it is used to act on the outline review node and the plan review node, and to update the task information to the next process node;

[0044] The return unit is used to update the task information to the specified process node.

[0045] In a third aspect, an embodiment of the present disclosure provides a computer device, the computer device comprising:

[0046] A processor is used to implement the steps of any of the above methods when executing a computer program stored in a memory.

[0047] In a fourth aspect, an embodiment of the present disclosure further discloses a computer-readable storage medium on which computer instructions are stored, and when the computer instructions are executed by a processor, the steps of any of the above methods are implemented.

[0048] The technical solution provided by the embodiment of the present disclosure proposes a cloud radiotherapy service management method and system based on a process processing engine. The process processing engine can help sort out business logic and build a clearer approval process route. The visual process designer only needs simple configuration to easily implement the data flow process. After the business process is on the cloud, it is no longer trapped in the traditional approval model and can be approved anytime and anywhere. The role of the process engine is that users can independently build forms, configure / publish process approval nodes, without the need for development participation or providing advanced functions to development. It can quickly build complex forms and generate user-usable forms and workflows without the need for development from scratch, thereby achieving the purpose of quickly launching new processes and unifying process functions / styles / configurations. By introducing the process processing engine and modifying the EventListener event monitoring mechanism, the custom settings of the process and the tasks of participating users can be realized, and different radiotherapy processes and process nodes can be configured for different hospitals and different types of cancer to meet the personalized needs of the hospital radiotherapy department.

[0049] The above technical solution of the embodiment of the present disclosure, by adding a process processing engine (taking the camunda process engine as an example), adopts unified process design, process modeling, process monitoring and standard process interface, flexibly realizes the orchestration and integration of business, improves the standardization and normalization of process management, and has the following 4 advantages and 2 enhancements compared with previous solutions:

[0050] advantage:

[0051] 1. It will help to establish a regional or national radiotherapy service and quality control system;

[0052] 2. Establish a regional collaborative teleradiotherapy service system and formulate and promote clinical application standards;

[0053] 3. Break down information silos and realize information interconnection among radiotherapy units at different levels;

[0054] 4. Mining, analyzing and managing tumor big data, improving clinical diagnosis rates, and assisting in the reform of the national medical system.

[0055] Enhancements:

[0056] 1. It has a large number of custom extension interfaces, and provides reference REST APIs for process deployment, process instances, process node tasks, timers, operators (groups, permissions), forms, etc.;

[0057] 2. It has a complete process monitoring system, a web application for monitoring and operation, which provides access to deployed BPMN processes and DMN decisions, allows searching for running and ended instances and performing operations on them, and allows it to be extended through plug-ins. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 This is a flow chart of the cloud radiotherapy service management method based on the process processing engine of the present application.

[0059] Figure 2 This is a sub-flow chart of step S2 in this application.

[0060] Figure 3 This is a sub-flow chart of step S3 in this application.

[0061] Figure 4 This is the cloud radiotherapy flow chart drawn in this application.

[0062] Figure 5 This is the process node diagram of the cloud radiotherapy process in this application. DETAILED DESCRIPTION

[0063] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments described herein; on the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0064] Figure 1 This is a flow chart of the cloud radiotherapy service management method based on the process processing engine of this application, such as Figure 1 As shown: A cloud radiotherapy service management method based on a process processing engine includes the following steps:

[0065] S1: Integrate the process processing engine into the project according to the project architecture, and generate the process processing engine class according to the process processing engine configuration class;

[0066] Specifically, this application integrates the process processing engine, based on the spring event monitoring mechanism, to meet the diversified needs of clinical business scenarios in different hospitals, eliminate the barriers caused by the differentiation of radiotherapy processes between hospitals, and realizes the customized processing of cloud radiotherapy processes by introducing the camunda process engine or other process engines. Taking the camunda process engine as an example, the process processing engine configuration class represents the entire configuration of the camunda process engine, and the process processing engine configuration class is customized through an XML file, and its function is to build a series of services according to the XML file (including, obtaining the operation process instance service RuntimeService, the operation process definition service RepositoryService, the operation task service TaskService, the query history data service HistoryService, etc.); the process processing engine class is also constructed through the process processing engine configuration class, and its function is to obtain the above series of services.

[0067] S2: Establish a process management model based on the core business operations of cloud radiotherapy, define process nodes, and draw and deploy cloud radiotherapy business processes based on process nodes;

[0068] Specifically, the process management model includes process nodes, process execution process and process permissions. Taking the core business operation process of cloud radiotherapy as an example, the process nodes in this embodiment include six nodes: target area delineation, delineation review, plan making, plan review, plan confirmation, and treatment completion. The process execution process is the task flow between the above six process nodes. The process permissions are to limit the operators. Only the operators with permissions can operate the corresponding process node task instances. For example, only operators with review permissions can pass the delineation review.

[0069] S3: Manage and operate the deployed cloud radiotherapy business process instances by calling the process processing engine;

[0070] Specifically, after completing the integration of the process processing engine and the deployment of the cloud radiotherapy business process, the process instance of the cloud radiotherapy business process can be managed by calling the process processing engine interface service.

[0071] In some embodiments, the "generating a process processing engine class according to the process processing engine configuration class" in step S1 includes: using XML files for automatic configuration, automatically loading the process processing engine configuration class to initialize generation when the process processing engine starts; or manually calling an independent process processing engine configuration object in the process processing engine configuration.

[0072] Specifically, before using the services provided by the process processing engine, it is necessary to generate the process processing engine class ProcessEngine according to the process processing engine configuration class ProcessEngineConfiguration. This embodiment can be implemented in two ways. One is to use XML files for automatic configuration. When the process processing engine is started, the process processing engine configuration class ProcessEngineConfiguration will be automatically loaded for initialization and generation. The other is to generate by manually calling the createStandaloneProcessEngineConfiguration method in the process processing engine configuration class ProcessEngineConfiguration.

[0073] In some embodiments, the process processing engine also integrates a visual process design web page for drawing cloud radiotherapy business processes.

[0074] Specifically, the process engine of this embodiment also integrates a visual process design Web page, which can draw a business process according to the designed process node flow.

[0075] In some embodiments, in combination Figure 4 That is, the cloud radiotherapy flow chart drawn in this application, the process nodes include six nodes: target area delineation, delineation review, plan making, plan review, plan confirmation, and completion of treatment.

[0076] Specifically, according to the cloud radiotherapy business operation, in this embodiment, the entire process is defined as six nodes: target area delineation, delineation review, plan making, plan review, plan confirmation, and treatment completion. Exclusive gateways, parallel gateways, and compatible gateways can be added between the nodes, and judgment conditions can be set on the connection line (the variables set here are global variables in the process instance) to implement special services. For example: the target area delineation node is for the purpose of delineating the target area for tumor radiotherapy for patients; the delineation review node requires the participation of physicians with review qualifications to review the target area delineation results, and if the review is passed, it enters the plan making node; the plan making node is to determine the target area for radiotherapy according to the patient's condition. The target area is delineated and a treatment plan is formulated for the patient. In the plan making node, the process engine will determine whether a senior physicist (a person who is qualified to make a treatment plan) is involved in the node. If yes, it means that the treatment plan does not need to be reviewed and can directly enter the plan confirmation node. If not, the treatment plan will be reviewed by entering the plan review node. After the treatment plan review is completed, the plan will enter the plan confirmation node. At this node, the opinions of the patient and his family will be considered and judged. If they agree to the treatment, the treatment will be completed. If not, the process will return to the plan making node and the treatment plan will be remade. The specific process of cloud radiotherapy is to start the treatment and determine whether the image contains the outline result and the result is issued by a hospital with the outline review qualification. If so, jump directly to the plan making node; if not, enter the target area outline node; enter the target area outline node and determine whether there is a physician with the outline review qualification participating in the node. If so, enter the plan making node after the target area outline node is completed; if not, enter the outline review node; after the outline review is completed, enter the plan making node and determine whether there is a physicist with the plan making role participating in the plan making node. If so, directly enter the plan confirmation node; if not, enter the plan review node, and enter the plan confirmation node after the plan review is completed; when the plan is confirmed, directly enter the treatment confirmation node and determine whether the patient and family members agree to the treatment. If so, enter the treatment completion node; if not, return to the plan making node to make the plan again.

[0077] In some embodiments, in combination Figure 2 That is, the sub-flow chart of step S2 in this application, the "deployment" in step S2 includes the following steps:

[0078] S21: calling the deployment creation method in the operation process definition service in the process processing engine, obtaining the constructor deployed in the form of a file, and calling the deployment interface to obtain the unique identifier PRO_DEF_ID of the business process definition;

[0079] S22: Obtain process node information in the process through the business process keyword PROCESS_KEY;

[0080] S23: Create a process information table, a process processing engine information table, and a node information table in the project database to store process related information.

[0081] Specifically, call the createDeployment method in the process definition service RepositoryService in the process processing engine, pass in the process name, BPMN file name, and BPMN file, obtain the constructor DeploymentBuilder deployed in the form of a file, then call the deploy method in the constructor to generate the deployment object Deployment, and call the getId method in Deployment to obtain the unique identifier proc_def_id of the process definition (the format is: process keyword: version number: serial number). At this point, the process drawn on the page has been deployed to the process processing engine. The deployed process information can be found in the database process processing engine data tables ACT_RE_DEPLOYMENT, ACT_GE_BYTEARRAY, and ACT_RE_PROCDEF. Among them, the business process information table WORKFLOW is created in the project database to save detailed information of the business process, mainly for the needs of radiotherapy business. For example, different radiotherapy processes can be configured for different hospitals; the process processing engine information table WORKFLOW_ENGINE is created to save the definition information of the process, because the unique identifier of the process definition is unique in both the radiotherapy business process and the process processing engine; the node information table WORKFLOW_ACT in the process is created to save the information of the process nodes in the process, mainly for handling the problem of continuous return task loop.

[0082] In some embodiments, in combination Figure 3 That is, the sub-flow chart of step S3 in the present application, wherein the "management operation on the instance of the deployed cloud radiotherapy business process" in step S3 includes:

[0083] S31: Create a task information table in the project database to save detailed information of tasks associated with the current process node;

[0084] Specifically, the task information table is mainly used to save the association between the patient, the unique identifier of the process instance, the process node and the unique identifier of the process node task instance. All the treatment processes of the patient can be found according to the patient's unique identifier, and all the process node treatment tasks and global parameters under the current process instance can be found according to the process instance unique identifier; in task management, all treatment tasks under the specified node can be found by switching the process node, and the specified task information can be found according to the process node task instance unique identifier, which is also the method parameter for realizing task flow.

[0085] S32: Call the operation process instance service, obtain the process instance unique identifier in the task information table, and start the process instance;

[0086] Specifically, when starting treatment, the startProcessInstanceById method in the operation process instance service RuntimeService is called, and the process definition unique identifier and process instance global parameters (locally create Map<String,Object> ) to obtain the unique identifier of the process instance processInstanceId of the process. At this time, the local method annotated with @EventListener will listen to the task information TaskEvent of the process node published by the process processing engine, load the unique identifier of the "create" type task instance to the local task, and when the condition for starting treatment meets "the image has delineation results and is not a lower-level hospital", the task listened to at this time is the task of making the plan node, otherwise it is the task of the target area delineation node

[0087] S33: According to the unique identifier of the process node task instance, based on the defined process node and the drawn cloud radiotherapy business process, submit, pass, reject, return or recall the current process node where the process node task instance is located;

[0088] Figure 5 This is the process node diagram of the cloud radiotherapy process in this application, combined with Figure 5 In some embodiments, the submit operation in step S33 acts after the target area delineation node and the plan making node, and is used to determine whether to update the task information to the next process node according to the exclusive gateway variable value;

[0089] The said operation acts on the outline review node and the plan review node, and is used to update the task information to the next process node;

[0090] The rejection, return or recall operation is used to update the task information to the specified process node.

[0091] In some embodiments, the specific process of the submit operation is to call the getVariables method in the operation process instance service, pass in the process instance unique identifier, obtain the global parameter variables of the current process instance, and update the exclusive gateway variable value; then call the complete method of the operation task service, pass in the task instance unique identifier and global variables; use the @EventListener annotation method to listen to the current process node task information released by the process processing engine, and load the "create" type task instance unique identifier to the local task;

[0092] Specifically, take the target area delineation submission as an example (the same applies to the plan submission operation), call the getVariables method in the RuntimeService service of the operation process instance service, pass in the unique identifier of the process instance, and obtain the global parameter variables (Map<String,Object> ), update the exclusive gateway variable value; then call the complete method of the operation task service TaskService, pass in the unique identifier of the process node task instance and the global variable, at this time, the local method annotated with @EventListener will listen to the task information TaskEvent of the process node published by the process processing engine, load the unique identifier of the "create" type task instance to the local task, when the user who submits the target area delineation operation has the role of a senior doctor, what is listened at this time is the task of making the plan node, otherwise it is the task of delineating the review node.

[0093] In some embodiments, the specific process of the operation is to call the complete method of the operation task service, pass in the unique identifier of the task instance, use the @EventListener annotated method to listen to the current process node task information released by the process processing engine, and load the unique identifier of the "create" type task instance to the local task.

[0094] Specifically, taking the operation of passing the outline review node as an example (the same applies to the operation of passing the plan review node), call the complete method of the operation task service TaskService, and pass in the unique ID of the task instance. At this time, the local method annotated with @EventListener will listen to the production plan node task information TaskEvent published by the process processing engine, and load the unique ID of the "create" type task instance to the local task. At this time, the task node information appears in the production plan node.

[0095] In some embodiments, the specific process of the rejection, return or recall operation is to call the getActivityInstance method in the operation task service, pass in the process instance unique identifier, and obtain the process node instance object running in the current business process in the process processing engine; call the createHistoricActivityInstanceQuery interface in the query historical data service, pass in the current process instance unique identifier and the task type selected when drawing the process, query the list of historical process node instance objects, and find the specified process node unique identifier to be rejected, returned or recalled according to the process node sequence and completed historical data in the node information table, combined with the process instance global parameters; call the createProcessInstanceModification method in the operation process instance service, pass in the process instance unique identifier, obtain the process instance modification builder ProcessInstanceModificationBuilder, call the cancelActivityInstance method to cancel the process node task and pass in the taskDefinitionKey attribute of the activityInstance object, call the startBeforeActivity method, pass in the unique identifier of the process node to be started, and then call the execute method. At this time, the local method annotated with @EventListener will listen to the task information of the process node published by the process processing engine, and load the "create" type process node task unique identifier to the local task.

[0096] In a second aspect, the present application also provides a cloud radiotherapy service management system based on a process processing engine, including:

[0097] The engine integration module integrates the process processing engine into the project according to the project architecture, and generates the process processing engine class according to the process processing engine configuration class;

[0098] The process deployment module establishes a process management model based on the core business operations of cloud radiotherapy, defines process nodes, draws cloud radiotherapy business processes based on process nodes, and deploys the processes;

[0099] The process management module manages the instances of the deployed cloud radiotherapy business processes by calling the process processing engine.

[0100] In some embodiments, the process deployment module includes:

[0101] The deployment creation submodule is used to call the deployment creation method in the operation process definition service in the process processing engine, obtain the constructor deployed in the form of a file, and call the deployment interface to obtain the unique identifier PRO_DEF_ID of the business process definition;

[0102] The process node acquisition submodule is used to obtain the process node information in the process through the business process keyword PROCESS_KEY;

[0103] The information storage submodule is used to create a process information table, a process processing engine information table and a node information table in the project database to save process related information.

[0104] In some embodiments, the process management module includes:

[0105] The task information table creation submodule is used to create a task information table in the project database to save the task details associated with the current process node;

[0106] The process instance start submodule is used to call the process instance operation service, obtain the process instance unique identifier in the task information table, and start the process instance;

[0107] The operation submodule submits, approves, rejects, returns or recalls the current process node where the process node task instance is located according to the unique identifier of the process node task instance, based on the defined process node and the drawn cloud radiotherapy business process.

[0108] In some embodiments, the operation submodule further includes:

[0109] A submission unit, used to act on the target area delineation node and the plan making node, and to determine whether to update the task information to the next process node according to the exclusive gateway variable value;

[0110] Through the unit, it is used to act on the outline review node and the plan review node, and to update the task information to the next process node;

[0111] The return unit is used to update the task information to the specified process node.

[0112] In a third aspect, an embodiment of the present invention provides a computer device, the computer device comprising: a processor, the processor is used to implement the steps of the cloud radiotherapy service management method based on the process processing engine as described above when executing a computer program stored in a memory. The processor may be a central processing unit (CPU) or other forms of processing units with data processing capabilities and / or instruction execution capabilities, and may control other components in the computer to perform desired functions. The memory may include one or more computer program products, and the computer program products may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on a computer-readable storage medium, and the processor may run the program instructions to implement the method steps and / or other desired functions of the various embodiments of the present application described above.

[0113] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium having computer instructions stored thereon, which, when executed by a processor, implement the steps of the cloud radiotherapy service management method based on the process processing engine as described above.

[0114] In addition to the above-mentioned methods and apparatus, the embodiments of the present application may also be a computer program product, which includes computer program instructions. When the computer program instructions are executed by a processor, the processor executes the method steps of various embodiments of the present application.

[0115] The computer program product may be written in one or more programming languages ​​in any combination to write program code for performing the operations of the embodiments of the present invention, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0116] In addition, the embodiments of the present application can also be a computer-readable storage medium, on which computer program instructions are stored, and the computer program instructions make the processor perform the method steps of various embodiments of the present application when being run by the processor. The computer-readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples of readable storage media (non-exhaustive list) include: an electrical connection with 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0117] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the existence of other identical elements in the process, method, article or device including the elements. The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A cloud radiotherapy service management method based on a process processing engine, characterized in that: The following steps are involved: S1: Integrate the process processing engine into the project according to the project architecture, and generate the process processing engine class according to the process processing engine configuration class. The "generating the process processing engine class according to the process processing engine configuration class" in step S1 includes: using XML file automatic configuration, automatically loading the process processing engine configuration class to initialize the generation when the process processing engine is started; or manually calling the independent process processing engine configuration object in the process processing engine configuration; S2: Establish a process management model based on the core business operations of cloud radiotherapy, define process nodes, draw cloud radiotherapy business processes based on process nodes and deploy the processes. The process nodes include six nodes: target area delineation, delineation review, plan making, plan review, plan confirmation, and treatment completion. The "deployment" in step S2 includes the following steps: S21: Call the deployment creation method in the operation process definition service in the process processing engine, obtain the constructor deployed in the form of a file, and call the deployment interface to obtain the unique identifier of the business process definition PRO_DEF_ID; S22: Obtain process node information in the process through the business process keyword PROCESS_KEY; S23: Create a process information table, a process processing engine information table, and a node information table in the project database to store process related information; S3: By calling the process processing engine, manage the instance of the deployed cloud radiotherapy business process. The "manage the instance of the deployed cloud radiotherapy business process" in step S3 includes: S31: Create a task information table in the project database to save detailed information of tasks associated with the current process node; S32: Call the operation process instance service, obtain the process instance unique identifier in the task information table, and start the process instance; S33: According to the unique identifier of the process node task instance, based on the defined process node and the drawn cloud radiotherapy business process, the current process node where the process node task instance is located is submitted, approved, rejected, returned or recalled.

2. According to claim 1, a cloud radiotherapy service management method based on a process processing engine is characterized in that: The process processing engine is a camunda process engine or an activiti process engine.

3. The cloud radiotherapy service management method based on a process processing engine according to claim 1, characterized in that: The process processing engine also integrates a visual process design web page for drawing cloud radiotherapy business processes.

4. A cloud radiotherapy service management method based on a process processing engine according to claim 3, characterized in that: The submit operation in step S33 acts after the target area delineation node and the plan making node, and is used to determine whether to update the task information to the next process node according to the exclusive gateway variable value; The said operation acts on the outline review node and the plan review node, and is used to update the task information to the next process node; The rejection, return or recall operation is used to update the task information to the specified process node.

5. A cloud radiotherapy service management method based on a process processing engine according to claim 4, characterized in that: The specific process of the submission operation is to call the getVariables method in the operation process instance service, pass in the unique identifier of the process instance, obtain the global parameter variables of the current process instance, and update the exclusive gateway variable value; then call the complete method of the operation task service, pass in the unique identifier of the task instance and the global variables; use the @EventListener annotation method to listen to the current process node task information released by the process processing engine, and load the unique identifier of the "create" type task instance to the local task.

6. A cloud radiotherapy service management method based on a process processing engine according to claim 5, characterized in that: The specific process of the operation is to call the complete method of the operation task service, pass in the unique identifier of the task instance, use the @EventListener annotated method to listen to the current process node task information released by the process processing engine, and load the unique identifier of the "create" type task instance to the local task.

7. A cloud radiotherapy service management method based on a process processing engine according to claim 6, characterized in that: The specific process of the rejection, return or recall operation is to call the getActivityInstance method in the operation task service, pass in the unique identifier of the process instance, and obtain the process node instance object running in the current business process in the process processing engine; Call the createHistoricActivityInstanceQuery interface in the historical data query service, pass in the current process instance unique ID and the task type selected when drawing the process, query the list of historical process node instance objects, and find the unique ID of the specified process node to be rejected, returned or recalled based on the process node sequence and completed historical data in the node information table and the process instance global parameters; Call the createProcessInstanceModification method in the operation process instance service, pass in the unique identifier of the process instance, obtain the process instance modification builder ProcessInstanceModificationBuilder, call the cancelActivityInstance method to cancel the process node task and pass in the taskDefinitionKey attribute of the activityInstance object, call the startBeforeActivity method, pass in the unique identifier of the process node to be started, and then call the execute method. At this time, the local method annotated with @EventListener will listen to the task information of the process node published by the process processing engine, and load the unique identifier of the "create" type process node task to the local task.

8. A cloud radiotherapy service management system based on a process processing engine, characterized in that: include: The engine integration module is used to generate a process processing engine class according to the process processing engine configuration class, and integrate the process processing engine into the project according to the project architecture, including: using XML files for automatic configuration, automatically loading the process processing engine configuration class for initialization generation when the process processing engine is started; or manually calling the independent process processing engine configuration object in the process processing engine configuration; The process deployment module is used to establish a process management model based on the core business operations of cloud radiotherapy, define process nodes, and draw and deploy cloud radiotherapy business processes based on the process nodes. The process nodes include six nodes: target area delineation, delineation review, plan making, plan review, plan confirmation, and treatment completion. The process deployment module includes: The deployment creation submodule is used to call the deployment creation method in the operation process definition service in the process processing engine, obtain the constructor deployed in the form of a file, and call the deployment interface to obtain the unique identifier PRO_DEF_ID of the business process definition; The process node acquisition submodule is used to obtain the process node information in the process through the business process keyword PROCESS_KEY; The information storage submodule is used to create a process information table, a process processing engine information table, and a node information table in the project database to store process related information The process management module is used to manage and operate the deployed cloud radiotherapy business process instance by calling the process processing engine. The process management module includes: The task information table creation submodule is used to create a task information table in the project database to save the task details associated with the current process node; The process instance start submodule is used to call the process instance operation service, obtain the process instance unique identifier in the task information table, and start the process instance; The operation submodule submits, approves, rejects, returns or recalls the current process node where the process node task instance is located according to the unique identifier of the process node task instance, based on the defined process node and the drawn cloud radiotherapy business process.

9. A cloud radiotherapy service management system based on a process processing engine according to claim 8, characterized in that: The operation submodule also includes: A submission unit, used to act on the target area delineation node and the plan making node, and to determine whether to update the task information to the next process node according to the exclusive gateway variable value; Through the unit, it is used to act on the outline review node and the plan review node, and is used to update the task information to the next process node; The return unit is used to update the task information to the specified process node.

10. A computer device, characterized in that: The computer device comprises: A processor, wherein the processor is configured to implement the steps of the method according to any one of claims 1 to 7 when executing a computer program stored in a memory.

11. A computer-readable storage medium having computer instructions stored thereon, characterized in that: When the computer instructions are executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images