A closed-loop management method, device, equipment and medium for hospital business processes

Abstract

The application provides a hospital business process closed-loop management method, device, equipment and medium, the method comprises the following steps: S1, establishing or importing the template of the standard closed-loop process of the hospital business process; S2, listening to the MQ message queue distributed by the integrated platform to consume the message sent by the business system, and when consuming, the corresponding message is parsed through the configuration field and stored in the process log; S3, the completion rate of the current standard closed-loop process is calculated according to the process log. The application is based on the integrated platform of hospital interconnection, integrates the key business processes in the hospital, thereby realizing the closed-loop management of the hospital business process, improving the service quality and operation efficiency, and improving the experience of patients.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, equipment, and medium for closed-loop management of hospital business processes. Background Technology

[0002] With the increasing demands for hospital management, it has become an urgent need to standardize the management of various processes within hospital operations. For example, the pre-diagnosis examination process involves multiple personnel, including doctors, nurses, patients, and their families. In particular, patients and their families cannot receive prior training on the process, and their educational levels vary. If the process guidance or management is inadequate, there is a risk of missing or omitted steps in the entire process, which not only greatly reduces the patient experience but also leads to a deterioration in the doctor-patient relationship.

[0003] It is evident that without standardized management of business processes, hospitals cannot fully expose existing problems, nor can they precisely improve their services by addressing these issues. Therefore, by integrating key business processes within hospitals based on interoperability and using an integrated platform to achieve closed-loop management of these processes, the aforementioned problems can be resolved.

[0004] The so-called interconnected integration platform refers to the platform that breaks down information barriers between various information systems within the hospital, enabling interconnection and interoperability among these systems. Summary of the Invention

[0005] The technical problem to be solved by the present invention is to provide a method, device, equipment and medium for closed-loop management of hospital business processes, which integrates key business processes within the hospital based on an interconnected hospital platform, thereby realizing closed-loop management of hospital business processes.

[0006] In a first aspect, the present invention provides a closed-loop management method for hospital business processes, executed in a closed-loop process management system, comprising the following steps:

[0007] S1. Establish or import a template for a standard closed-loop process for hospital business processes;

[0008] S2. Listen to the asynchronously distributed MQ message queue of the integration platform to consume messages sent by the business system, and parse the corresponding messages through configuration fields and store them in the process log during consumption;

[0009] S3. Display the standard closed-loop process based on the process log, and calculate the completion rate of the current standard closed-loop process;

[0010] The completion rate of the current standard closed-loop process = (effective nodes of the current standard closed-loop process / maximum level of the template of the current standard closed-loop process) × 100%.

[0011] Secondly, the present invention provides a closed-loop management device for hospital business processes, executed in a closed-loop process management system, comprising:

[0012] The template management module is used to create or import templates for standard closed-loop processes in hospital business processes and manage them.

[0013] The message listening module is used to listen to the asynchronously distributed MQ message queue of the integration platform to consume messages sent by the business system, and parse the corresponding messages through configuration fields and store them in the process log during consumption;

[0014] The display module is used to display the standard closed-loop process based on the process log and calculate the completion rate of the current standard closed-loop process.

[0015] Thirdly, the present invention provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method described in the first aspect.

[0016] Fourthly, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect.

[0017] The one or more technical solutions provided in the embodiments of this invention have at least the following technical effects or advantages: Based on zero modification to the business system, this invention, through interconnection and interoperability achieved by relying on an integration platform, asynchronously integrates previously scattered messages into specific processes, enabling each business process in the hospital to form a standard closed-loop process. This achieves closed-loop management of hospital business processes, helping hospitals better identify problems and gradually improve the quality of closed-loop processes, increase hospital operational efficiency, and enhance patient experience. Furthermore, since the closed-loop management of hospital business processes is also implemented based on the integration platform, each message contains transaction codes and node fields. These node fields include key fields, general fields, main index fields, trigger time fields, operator fields, institution fields, and hospital number fields. Therefore, it can not only accurately and efficiently parse each message to obtain process logs and store them under the corresponding nodes, but also retrieve the patient's relevant medical information from the patient's 360° holographic view (a holographic view of patients based on a clinical data center) through the patient's main index (the patient's unique identifier) ​​and hospital number.

[0018] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0019] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0020] Figure 1 This is a schematic diagram of the system framework of the present invention;

[0021] Figure 2 This is a flowchart of the method in Embodiment 1 of the present invention;

[0022] Figure 3 This is a schematic diagram of an example of a standard closed-loop process in an embodiment of the present invention;

[0023] Figure 4 This is a schematic diagram illustrating the successful registration of a message type with the integration platform by a business system in an embodiment of the present invention.

[0024] Figure 5 This is an example of a platform invocation specification in an embodiment of the present invention;

[0025] Figure 6 This is a schematic diagram of a message structure in an embodiment of the present invention;

[0026] Figure 7 This is a schematic diagram of the transaction codes corresponding to different nodes in an embodiment of the present invention;

[0027] Figure 8 This is a schematic diagram of the loop node determination in an embodiment of the present invention;

[0028] Figure 9 This is a schematic diagram of the message consumption process in an embodiment of the present invention;

[0029] Figure 10 This is a schematic diagram of the maximum level of the template for the standard closed-loop process in an embodiment of the present invention;

[0030] Figure 11 This is a status diagram showing the calculation results of the completion rate of the current standard closed-loop process in this embodiment of the invention.

[0031] Figure 12 This is a schematic diagram of the daily summary results in an embodiment of the present invention;

[0032] Figure 13 This is a schematic diagram of the device in Embodiment 2 of the present invention;

[0033] Figure 14This is a schematic diagram of the electronic device in Embodiment 3 of the present invention;

[0034] Figure 15 This is a schematic diagram of the structure of the medium in Embodiment 4 of the present invention. Detailed Implementation

[0035] This application provides a method, apparatus, equipment, and medium for closed-loop management of hospital business processes. Based on an integrated platform for hospital interconnection, it integrates key business processes within the hospital to achieve closed-loop management of hospital business processes.

[0036] The overall concept of the technical solution in this application is as follows:

[0037] Before introducing specific embodiments, the hospital system framework corresponding to the method in this application embodiment will be introduced first, such as... Figure 1 As shown, the hospital system can be roughly divided into three parts:

[0038] Business systems are used to implement various business processes in a hospital. Generally, different business systems need to interact and cooperate to complete the same business process.

[0039] The integration platform is used to integrate the processes and data of numerous business systems within the hospital through a service bus, forming a data governance system including a patient master index and hospital master data, and building a complete and reliable data center (Clinical Data Center CDR, Operational Data Center ODR, and Research Data Center RDR); through a unified portal, it provides a real-time, aggregated, 360-degree visualized view of patient diagnosis and treatment information, enabling interconnection and interoperability of patient clinical information, exchange and sharing of clinical data, and retrieval and query functions for medical knowledge within the hospital.

[0040] The closed-loop management system, as researched in this invention, is based on an integrated platform for hospital interconnection and integrates key business processes within the hospital to achieve closed-loop management of these processes. It consumes messages from business systems by listening to asynchronously distributed MQ message queues on the integrated platform. During consumption, the system parses the corresponding messages using various process configurations, such as key fields and general fields, and stores them in the process log.

[0041] Example 1

[0042] like Figure 2 As shown, this embodiment provides a closed-loop management method for hospital business processes, executed in a closed-loop process management system, including the following steps:

[0043] S1. Establish or import a template for a standard closed-loop process for hospital business processes;

[0044] S2. Listen to the asynchronously distributed MQ message queue of the integration platform to consume messages sent by the business system, and parse the corresponding messages through configuration fields and store them in the process log during consumption;

[0045] S3. Display the standard closed-loop process based on the process log, and calculate the completion rate of the current standard closed-loop process.

[0046] The template for the standard closed-loop process is compiled based on the hospital's standard process specifications and interoperability documentation before being imported into the system. After importation, it can be adjusted according to actual needs; alternatively, it can be created directly within the system. For example... Figure 3 As shown, standard closed-loop processes include inpatient laboratory testing, inpatient surgery, inpatient examination, inpatient blood transfusion, medication use, outpatient examination, and outpatient laboratory testing. Each standard closed-loop process corresponds to a template, and schematic diagrams of each node in the inpatient laboratory testing closed-loop process are also displayed.

[0047] Since the entire closed-loop management system relies on an integration platform, the definition of the closed-loop process needs to define a standard interface corresponding to the integration platform, i.e., message type. For example... Figure 4 As shown, when business system A registers an update service for a certain type of status information with the integration platform, after successful registration, the integration platform returns a transaction code and requires business system A to use the platform's call specifications to send messages. Figure 5 This is an example of a platform call specification. Therefore, subsequent status information updates from business system A will be sent according to the call specification, such as... Figure 6 The message shown is sent to the integration platform. The transaction code in the status information update message remains unchanged each time business system A checks. The integration platform will synchronously send the following message to the MQ queue, which will be consumed by the closed-loop management system.

[0048] Therefore, any of the aforementioned standard closed-loop processes has multiple nodes, each node corresponding to a message type, and each message type is identified by a transaction code; such as Figure 7 As shown, for example, an inspection process includes eight nodes: inspection application submission, inspection fee payment, application withdrawal, inspection registration, inspection refund, inspection completion, inspection report completion, and report review. These eight nodes correspond to eight message types, therefore each node has a different transaction code.

[0049] Each message contains a transaction code and node fields. The node fields include key fields, general fields, a main index field, a trigger time field, an operator field, an institution field, and a hospital number field. Specifically: the key fields are used to determine whether the business process has reached the corresponding node; different nodes have different key fields. The general fields are unique identifiers for the standard closed-loop process, used to connect the entire standard closed-loop process; therefore, in the same standard closed-loop process, the general fields of each node are the same. The main index field is a unique identifier for the patient.

[0050] In different messages at the same node within the same standard closed-loop process, the transaction code and the key field are identical. For example, when different patients execute the same standard closed-loop process (or the same patient executes the same standard closed-loop process sequentially), multiple closed loops are initiated. Before each node of these closed loops is completed, it is typically stored in memory. Each closed loop corresponds to the same message type at the same node, therefore the transaction code and key field are the same. However, since they belong to different closed loops, the common fields are different. Thus, the node can be determined based on the transaction code, and the closed loop can be determined by combining the common fields. Finally, the key field can be used to determine which node the closed loop is currently executing at.

[0051] Nodes can be divided into cyclic nodes and non-cyclic nodes, which can be set in the node's property configuration panel. A cyclic node has multiple messages, which are cyclic messages. Therefore, it is necessary to determine whether a message is a cyclic message. If it is, the process logs parsed from multiple cyclic messages of the same cyclic node should all be stored on that cyclic node.

[0052] The judgment of circular messages is as follows Figure 8 The diagram illustrates a partial node in a testing process. Assume a testing process has reached the specimen collection node. Suppose the testing system first sends a blood specimen collection message to the integration platform, and then sends a urine specimen collection message to the same platform (the integration platform will place both messages in a message queue for closed-loop management and consumption). Since both the first blood specimen collection message and the second urine specimen collection message belong to the same node in the same closed loop, then:

[0053] When the closed-loop management system consumes the first blood sample collection message, it first determines whether the previous barcode printing node is a loop node. Since the barcode printing node is not a loop node, it means that the current message is not a loop message. Then, it incrementally traverses the subsequent nodes of the closed loop. When it finds that it is a sample collection node, the process has reached the sample collection node. At this time, the process log obtained by parsing the message needs to be saved on the sample collection node.

[0054] When the closed-loop management system consumes the second urine sample collection message, it will determine whether the previous sample collection node is a loop node. Since the sample collection node has already been executed, when first determining whether the previous barcode printing node is a loop node, the previous node has already become a sample collection node. Since the sample collection node is a loop node, it will determine whether the current message is a loop message of the previous node based on the transaction code and key fields. Since the key fields indicate that the current message is still a message of the sample collection node, the message will be parsed and the process log will be stored in the previous sample collection node.

[0055] like Figure 9 As shown, the specific process of parsing the corresponding message and storing it in the process log by configuring fields includes:

[0056] S31. Retrieve the transaction code and common fields from the message;

[0057] S32. Match the corresponding nodes in each closed loop in the cache according to the transaction code and general fields. If the match fails, it is considered to be the starting node, and proceed to step 33; if the match succeeds, it is considered to be the intermediate node, and proceed to steps 34 to 35.

[0058] S33. Based on the transaction code, find the key fields in the node attribute configuration that belong to the start node, and match the specific closed loop to which it belongs based on the key fields.

[0059] If a match is successful, the transaction code and common fields are saved sequentially under all nodes in the corresponding closed loop, and the current node information is stored in the cache; the message is parsed and the process log is stored in the current node;

[0060] If the match fails, the process ends.

[0061] S34. Based on the transaction code and general fields, find the previous node in the successfully matched closed loop and determine whether the previous node is a loop node;

[0062] If the previous node is a loop node, determine whether the current message is a loop message of the previous node based on the transaction code and key fields; if it is a loop message of the previous node, parse the message, store the process log to the previous node, and then proceed to step 35.

[0063] If the previous node is not a loop node, determine whether the current node is the next node of the previous node based on the transaction code and key fields; if so, parse the message and store the process log to the next node; if not, it means that there is a skipped node, so it iterates through the subsequent nodes of the closed loop until the corresponding node is matched, parses the message, and stores the process log to the corresponding node; at the same time, it fills in the error process log of the skipped node and determines whether the skipped node is a necessary node. If it is a necessary node, it pushes a notification message to the preset recipient.

[0064] 35. Determine whether the current node is the end node based on the node attributes. If it is, clear all caches in the current process and end; otherwise, end directly.

[0065] Regarding the calculation of the completion rate of the current standard closed-loop process; such as Figure 10 As shown, if a current standard closed-loop process includes 6 nodes, where the inspection application fee payment and application withdrawal nodes are parallel nodes belonging to the same level, and the barcode printing and inspection application refund nodes also belong to the same level, the maximum level of the current standard closed-loop process template is 4 levels. The valid node in the current standard closed-loop process is the completed node. Of course, only one node at the same level can be effectively executed during execution. Therefore, as... Figure 11 As shown, in the current standard closed-loop process with four levels, only the two nodes in the second level have not been executed, while nodes in the other three levels have been executed. Therefore:

[0066] The completion rate of the current standard closed-loop process = (effective nodes of the current standard closed-loop process / maximum level of the template of the current standard closed-loop process) × 100% = 3 / 4 × 100% = 70%.

[0067] Better, such as Figure 2 As shown, the closed-loop management method for hospital business processes in this embodiment further includes:

[0068] S4. Summarize and display the daily completion rate and number of standard closed-loop processes for each process. The results are as follows: Figure 12 As shown.

[0069] Based on the same inventive concept, this application also provides an apparatus corresponding to the method in Embodiment 1, as detailed in Embodiment 2.

[0070] Example 2

[0071] like Figure 13 As shown, this embodiment provides a closed-loop management device for hospital business processes, which is executed in a closed-loop process management system and includes:

[0072] The template management module is used to create or import templates for standard closed-loop processes in hospital business processes and manage them.

[0073] The message listening module is used to listen to the asynchronously distributed MQ message queue of the integration platform to consume messages sent by the business system, and parse the corresponding messages through configuration fields and store them in the process log during consumption;

[0074] The display module is used to display the standard closed-loop process based on the process log and calculate the completion rate of the current standard closed-loop process.

[0075] The template for the standard closed-loop process is compiled based on the hospital's standard process specifications and interoperability documentation before being imported into the system. After importation, it can be adjusted according to actual needs; alternatively, it can be created directly within the system. For example... Figure 3 As shown, standard closed-loop processes include inpatient laboratory testing, inpatient surgery, inpatient examination, inpatient blood transfusion, medication use, outpatient examination, and outpatient laboratory testing. Each standard closed-loop process corresponds to a template, and schematic diagrams of each node in the inpatient laboratory testing closed-loop process are also displayed.

[0076] Since the entire closed-loop management system relies on an integration platform, the definition of the closed-loop process needs to define a standard interface corresponding to the integration platform, i.e., message type. For example... Figure 4 As shown, when business system A registers an update service for a certain type of status information with the integration platform, after successful registration, the integration platform returns a transaction code and requires business system A to use the platform's call specifications to send messages. Figure 5 This is an example of a platform call specification. Therefore, subsequent status information updates from business system A will be sent according to the call specification, such as... Figure 6 The message shown is sent to the integration platform. The transaction code in the status information update message remains unchanged each time business system A checks. The integration platform will synchronously send the following message to the MQ queue, which will be consumed by the closed-loop management system.

[0077] Therefore, any of the aforementioned standard closed-loop processes has multiple nodes, each node corresponding to a message type, and each message type is identified by a transaction code; such as Figure 7 As shown, for example, an inspection process includes eight nodes: inspection application submission, inspection fee payment, application withdrawal, inspection registration, inspection refund, inspection completion, inspection report completion, and report review. These eight nodes correspond to eight message types, therefore each node has a different transaction code.

[0078] Each message contains a transaction code and node fields. The node fields include key fields, general fields, a main index field, a trigger time field, an operator field, an institution field, and a hospital number field. Specifically: the key fields are used to determine whether the business process has reached the corresponding node; different nodes have different key fields. The general fields are unique identifiers for the standard closed-loop process, used to connect the entire standard closed-loop process; therefore, in the same standard closed-loop process, the general fields of each node are the same. The main index field is a unique identifier for the patient.

[0079] In different messages at the same node within the same standard closed-loop process, the transaction code and the key field are identical. For example, when different patients execute the same standard closed-loop process (or the same patient executes the same standard closed-loop process sequentially), multiple closed loops are initiated. Before each node of these closed loops is completed, it is typically stored in memory. Each closed loop corresponds to the same message type at the same node, therefore the transaction code and key field are the same. However, since they belong to different closed loops, the common fields are different. Thus, the node can be determined based on the transaction code, and the closed loop can be determined by combining the common fields. Finally, the key field can be used to determine which node the closed loop is currently executing at.

[0080] Nodes can be divided into cyclic nodes and non-cyclic nodes, which can be set in the node's property configuration panel. A cyclic node has multiple messages, which are cyclic messages. Therefore, it is necessary to determine whether a message is a cyclic message. If it is, the process logs parsed from multiple cyclic messages of the same cyclic node should all be stored on that cyclic node.

[0081] The judgment of circular messages is as follows Figure 8 The diagram illustrates a partial node in a testing process. Assume a testing process has reached the specimen collection node. Suppose the testing system first sends a blood specimen collection message to the integration platform, and then sends a urine specimen collection message to the same platform (the integration platform will place both messages in a message queue for closed-loop management and consumption). Since both the first blood specimen collection message and the second urine specimen collection message belong to the same node in the same closed loop, then:

[0082] When the closed-loop management system consumes the first blood sample collection message, it first determines whether the previous barcode printing node is a loop node. Since the barcode printing node is not a loop node, it means that the current message is not a loop message. Then, it incrementally traverses the subsequent nodes of the closed loop. When it finds that it is a sample collection node, the process has reached the sample collection node. At this time, the process log obtained by parsing the message needs to be saved on the sample collection node.

[0083] When the closed-loop management system consumes the second urine sample collection message, it will determine whether the previous sample collection node is a loop node. Since the sample collection node has already been executed, when first determining whether the previous barcode printing node is a loop node, the previous node has already become a sample collection node. Since the sample collection node is a loop node, it will determine whether the current message is a loop message of the previous node based on the transaction code and key fields. Since the key fields indicate that the current message is still a message of the sample collection node, the message will be parsed and the process log will be stored in the previous sample collection node.

[0084] The specific process executed by the message listening module includes:

[0085] S31. Retrieve the transaction code and common fields from the message;

[0086] S32. Match the corresponding nodes in each closed loop in the cache according to the transaction code and general fields. If the match fails, it is considered to be the starting node, and proceed to step 33; if the match succeeds, it is considered to be the intermediate node, and proceed to steps 34 to 35.

[0087] S33. Based on the transaction code, find the key fields in the node attribute configuration that belong to the start node, and match the specific closed loop to which it belongs based on the key fields.

[0088] If a match is successful, the transaction code and common fields are saved sequentially under all nodes in the corresponding closed loop, and the current node information is stored in the cache; the message is parsed and the process log is stored in the current node;

[0089] If the match fails, the process ends.

[0090] S34. Based on the transaction code and general fields, find the previous node in the successfully matched closed loop and determine whether the previous node is a loop node;

[0091] If the previous node is a loop node, determine whether the current message is a loop message of the previous node based on the transaction code and key fields; if it is a loop message of the previous node, parse the message, store the process log to the previous node, and then proceed to step 35.

[0092] If the previous node is not a loop node, determine whether the current node is the next node of the previous node based on the transaction code and key fields; if so, parse the message and store the process log to the next node; if not, it means that there is a skipped node, so it iterates through the subsequent nodes of the closed loop until the corresponding node is matched, parses the message, and stores the process log to the corresponding node; at the same time, it fills in the error process log of the skipped node and determines whether the skipped node is a necessary node. If it is a necessary node, it pushes a notification message to the preset recipient.

[0093] 35. Determine whether the current node is the end node based on the node attributes. If it is, clear all caches in the current process and end; otherwise, end directly.

[0094] Regarding the calculation of the completion rate of the current standard closed-loop process; such as Figure 10 As shown, if a current standard closed-loop process includes 6 nodes, where the inspection application fee payment and application withdrawal nodes are parallel nodes belonging to the same level, and the barcode printing and inspection application refund nodes also belong to the same level, the maximum level of the current standard closed-loop process template is 4 levels. The valid node in the current standard closed-loop process is the completed node. Of course, only one node at the same level can be effectively executed during execution. Therefore, as... Figure 11 As shown, in the current standard closed-loop process with four levels, only the two nodes in the second level have not been executed, while nodes in the other three levels have been executed. Therefore:

[0095] The completion rate of the current standard closed-loop process = (effective nodes of the current standard closed-loop process / maximum level of the template of the current standard closed-loop process) × 100% = 3 / 4 × 100% = 70%.

[0096] Better, such as Figure 13 As shown, the closed-loop management device for hospital business processes in this embodiment further includes:

[0097] The daily summary module summarizes and displays the daily completion rate and the number of standard closed-loop processes for each process. The results are shown below. Figure 12 As shown.

[0098] Since the apparatus described in Embodiment 2 of the present invention is an apparatus used to implement the method of Embodiment 1 of the present invention, those skilled in the art can understand the specific structure and variations of the apparatus based on the method described in Embodiment 1 of the present invention, and therefore will not be described again here. All apparatuses used in the method of Embodiment 1 of the present invention fall within the scope of protection of the present invention.

[0099] Based on the same inventive concept, this application provides an electronic device embodiment corresponding to Embodiment 1, as detailed in Embodiment 3.

[0100] Example 3

[0101] This embodiment provides an electronic device, such as... Figure 14 As shown, it includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it can implement any of the embodiments in Example 1.

[0102] Since the electronic device described in this embodiment is the device used to implement the method in Embodiment 1 of this application, those skilled in the art can understand the specific implementation method and various variations of the electronic device in this embodiment based on the method described in Embodiment 1 of this application. Therefore, how the electronic device implements the method in the embodiment of this application will not be described in detail here. Any device used by those skilled in the art to implement the method in the embodiment of this application falls within the scope of protection of this application.

[0103] Based on the same inventive concept, this application provides a storage medium corresponding to Embodiment 1, as detailed in Embodiment 4.

[0104] Example 4

[0105] This embodiment provides a computer-readable storage medium, such as... Figure 15 As shown, a computer program is stored thereon, which, when executed by a processor, can implement any of the embodiments in Example 1.

[0106] The technical solutions provided in the embodiments of this application have at least the following technical effects or advantages: the methods, apparatus, systems, equipment, and media provided in the embodiments of this application,

[0107] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0108] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0109] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0110] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0111] While specific embodiments of the present invention have been described above, those skilled in the art should understand that the specific embodiments described are merely illustrative and not intended to limit the scope of the present invention. Equivalent modifications and variations made by those skilled in the art in accordance with the spirit of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A closed-loop management method for hospital business processes, characterized in that: Execution in a closed-loop process management system includes the following steps: S1. Establish or import a template for a standard closed-loop process for hospital business processes; S2. Listen to the asynchronously distributed MQ message queue of the integration platform to consume messages sent by the business system, and parse the corresponding messages through configuration fields and store them in the process log during consumption; S3. Display the standard closed-loop process based on the process log, and calculate the completion rate of the current standard closed-loop process; Each of the aforementioned standard closed-loop processes has multiple nodes, each node corresponds to a message type, and each message type is identified by a transaction code; Each message contains a transaction code and node fields. The node fields include key fields, general fields, main index fields, trigger time fields, operator fields, institution fields, and hospital number fields. Among them: the key fields are used to determine whether the business process has reached the corresponding node; the general fields are unique identifiers of the standard closed-loop process and are used to connect the entire standard closed-loop process; the main index field is the unique identifier of the patient. The specific process of parsing the corresponding messages and storing them in the process log by configuring fields includes: S31. Retrieve the transaction code and common fields from the message; S32. Match the corresponding nodes in each closed loop in the cache according to the transaction code and general fields. If the match fails, it is considered to be the starting node, and then proceed to step S33; if the match succeeds, it is considered to be the intermediate node, and then proceed to steps S34 to S35. S33. Based on the transaction code, find the key fields in the node attribute configuration that belong to the start node, and match the specific closed loop to which it belongs based on the key fields. If a match is successful, the transaction code and common fields are saved sequentially under all nodes in the corresponding closed loop, and the current node information is stored in the cache; the message is parsed and the process log is stored in the current node; If the match fails, the process ends. S34. Based on the transaction code and general fields, find the previous node in the successfully matched closed loop and determine whether the previous node is a loop node; If the previous node is a loop node, determine whether the current message is a loop message of the previous node based on the transaction code and key fields; if it is a loop message of the previous node, parse the message, store the process log to the previous node, and then proceed to step S35. If the previous node is not a loop node, determine whether the current node is the next node of the previous node based on the transaction code and key fields; if so, parse the message and store the process log to the next node; if not, it means that there is a skipped node, so it iterates through the subsequent nodes of the closed loop until the corresponding node is matched, parses the message, and stores the process log to the corresponding node; at the same time, it fills in the error process log of the skipped node and determines whether the skipped node is a necessary node. If it is a necessary node, it pushes a notification message to the preset recipient. S35. Determine whether the current node is the end node based on the node attributes. If it is, clear all caches in the current process and end; otherwise, end directly.

2. The closed-loop management method for hospital business processes according to claim 1, characterized in that: Also includes: S4. Summarize and display the daily completion rate and number of standard closed-loop processes for each standard closed-loop process.

3. A closed-loop management device for hospital business processes, characterized in that: Executed in a closed-loop process management system, including: The template management module is used to create or import templates for standard closed-loop processes in hospital business processes and manage them. The message listening module is used to listen to the asynchronously distributed MQ message queue of the integration platform to consume messages sent by the business system, and parse the corresponding messages through configuration fields and store them in the process log during consumption; The display module is used to display the standard closed-loop process based on the process log and calculate the completion rate of the current standard closed-loop process. Each of the aforementioned standard closed-loop processes has multiple nodes, each node corresponds to a message type, and each message type is identified by a transaction code; Each message contains a transaction code and node fields. The node fields include key fields, general fields, main index fields, trigger time fields, operator fields, institution fields, and hospital number fields. Among them: the key fields are used to determine whether the business process has reached the corresponding node; the general fields are unique identifiers of the standard closed-loop process and are used to connect the entire standard closed-loop process; the main index field is the unique identifier of the patient. The specific process executed by the message listening module includes: S31. Retrieve the transaction code and common fields from the message; S32. Match the corresponding nodes in each closed loop in the cache according to the transaction code and general fields. If the match fails, it is considered to be the starting node, and then proceed to step S33; if the match succeeds, it is considered to be the intermediate node, and then proceed to steps S34 to S35. S33. Based on the transaction code, find the key fields in the node attribute configuration that belong to the start node, and match the specific closed loop to which it belongs based on the key fields. If a match is successful, the transaction code and common fields are saved sequentially under all nodes in the corresponding closed loop, and the current node information is stored in the cache; the message is parsed and the process log is stored in the current node; If the match fails, the process ends. S34. Based on the transaction code and general fields, find the previous node in the successfully matched closed loop and determine whether the previous node is a loop node; If the previous node is a loop node, determine whether the current message is a loop message of the previous node based on the transaction code and key fields; if it is a loop message of the previous node, parse the message, store the process log to the previous node, and then proceed to step S35. If the previous node is not a loop node, determine whether the current node is the next node of the previous node based on the transaction code and key fields; if so, parse the message and store the process log to the next node; if not, it means that there is a skipped node, so it iterates through the subsequent nodes of the closed loop until the corresponding node is matched, parses the message, and stores the process log to the corresponding node; at the same time, it fills in the error process log of the skipped node and determines whether the skipped node is a necessary node. If it is a necessary node, it pushes a notification message to the preset recipient. S35. Determine whether the current node is the end node based on the node attributes. If it is, clear all caches in the current process and end; otherwise, end directly.

4. The closed-loop management device for hospital business processes according to claim 3, characterized in that: Also includes: The daily summary module summarizes and displays the daily completion rate and the number of standard closed-loop processes for each process.

5. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method as described in claim 1 or 2.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in claim 1 or 2.

Images