Business operation process control method, terminal equipment and storage medium

Abstract

The invention relates to a business operation flow control method, terminal equipment and a storage medium, and the method comprises the steps: building message middleware through employing a Kafka and Zookeeper cluster, and connecting each business system with a producer interface and a consumer interface of the message middleware; defining and recording an event for each business operation generated by each business system; recording corresponding consumer interfaces and message formats at the same time; when the business system generates a service operation, sending the business operation to the message middleware through a producer interface of the message middleware; and enabling the message middleware to verify the received message, read the consumer interface corresponding to the event corresponding to the message when the verification succeeds, convert the message according to the message format corresponding to the consumer interface, and send the converted message to the corresponding business system through the read consumer interface. Based on the modular design concept, the event-driven architecture is adopted, cooperation between modules is completed by means of communication of event messages, and the purpose of module decoupling is achieved.

Description

technical field [0001] The invention relates to the field of flow control, in particular to a method for controlling a business operation flow, a terminal device and a storage medium. Background technique [0002] The hospital information system involves a lot of clinical business, and these clinical business are composed of events, such as doctor's order, nurse's proofreading, patient admission, etc., and there is a linkage relationship between events. From the perspective of software, these events correspond to function blocks or operation sets in the same or different modules. At the same time, there are many function modules, and there are a lot of correlations between the operations of the modules. If these events are processed using the traditional dependency injection method, it is bound to Causes a high degree of coupling between modules. For example, in the traditional admission operation, after the patient is successfully admitted, he needs to continue to perform ...

AI Technical Summary

Problems solved by technology

From the perspective of software, these events correspond to function blocks or operation sets in the same or different modules. At the same time, there are many function modules, and there are a lot of correlations between the operations of the modules. If these events are processed using the traditional dependency injection method, it is bound to Causes a high degree of coupling between modules

For example, in the traditional admission operation, after the patient is successfully admitted, he needs to continue to perform multiple logics such as writing medical records and admission evaluation within 8 hours of admission. If other operations need to be expanded later, the admission module must be modified. The shortcomings of the method are obviously tight coupling, no linkage, and poor expansion.

Images