CN114171168A - Business module management system, method, electronic device and storage medium - Google Patents
Business module management system, method, electronic device and storage medium Download PDFInfo
- Publication number
- CN114171168A CN114171168A CN202111528895.2A CN202111528895A CN114171168A CN 114171168 A CN114171168 A CN 114171168A CN 202111528895 A CN202111528895 A CN 202111528895A CN 114171168 A CN114171168 A CN 114171168A
- Authority
- CN
- China
- Prior art keywords
- function
- service module
- module
- interface
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0637—Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals
Abstract
The embodiment of the disclosure provides a service module management system, a service module management method, electronic equipment and a storage medium. The system comprises: the system comprises a plurality of service modules and a public module, wherein the public module is connected with the plurality of service modules through functional interfaces; the public module is used for receiving a first function request of the first service module through the first function interface; the first function request includes at least first function type information; the public module is also used for calling a second function interface and sending the first function request to the second service module through the second function interface so as to realize the first function request; the second function interface corresponds to the first function type information, and the first service module is different from the second service module. The system functions are split in a modularization mode, so that development, modification and reconstruction of each module can be realized quickly and efficiently, functions of other systems can be developed in a module mode and flexibly added or removed, maintenance cost and period are reduced, and the effect of quickly changing service requirements of users is met.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of electronic equipment, and in particular relates to a service module management system method, electronic equipment and a storage medium.
Background
With the development of medical science and technology and the electronic informatization of more and more medical institution areas, the current HIS system (hospital information system) is mainly applied to medical institutions such as hospitals, the business modules of the HIS system are coupled together, and the program needs to be recompiled when the systems with different functional versions are released.
Disclosure of Invention
In view of the foregoing problems in the prior art, embodiments of the present disclosure provide a service module management system method, an electronic device, and a storage medium, so as to solve the problems that modules are added, modified, and developed in a system, the maintenance cost is high, the period is long, and the service requirement of a client for quick change cannot be met.
In order to solve the above problems, the technical solution provided by the embodiments of the present disclosure is: a business module management system, the system comprising: the system comprises a plurality of service modules and a public module, wherein the public module is connected with the plurality of service modules through functional interfaces; the public module is used for receiving a first function request of the first service module through the first function interface; wherein the first function request includes at least first function type information; the public module is also used for calling a second function interface and sending the first function request to a second service module through the second function interface so as to realize the first function request; the second function interface corresponds to the first function type information, and the first service module is different from the second service module.
Further, the public module is further configured to, when the second function interface is called, determine whether the second function interface is associated with the second service module;
under the condition that the second function interface is associated with the second service module, the first function request is sent to the second service module through the second function interface so as to realize the first function request;
and sending default information to the first service module through the first functional interface under the condition that the second functional interface is not associated with the second service module.
Further, in a case that the association relationship between the second functional interface and the second service module is removed and the association relationship between the second functional interface and the third service module is newly added, the common module is further configured to send the first functional request to the third service module through the second functional interface to implement the first functional request;
wherein the third service module is different from the second service module.
Further, the association relationship between the second functional interface and the fourth service module is newly added, and when the priority of the fourth service module is higher than that of the second service module, the common module is further configured to send the first functional request to the fourth service module through the second functional interface to implement the first functional request;
wherein the fourth service module is different from the second service module; the fourth service module has a function of implementing the first function request.
Further, when the association relationship between the second function interface and the fifth service module is newly added, the common module is further configured to send a second function request to the fifth service module through the second function interface to implement the second function request;
the first function request is different from the second function request, and the second function interface corresponds to second function type information in the second function request.
Further, when an association relationship between a third function interface and a sixth service module is newly added, the common module is further configured to send a third function request to the sixth service module through the third function interface to implement the third function request;
the first function request is different from the third function request, and the third function interface corresponds to third function type information in the third function request.
Further, the common module is further specifically configured to receive feedback information of the second service module, and send the feedback information to the first service module through the first functional interface.
The embodiment of the present disclosure further provides a method for managing a service module of a system, where the method includes:
receiving a first function request of a first service module through a first function interface; wherein the first function request includes at least first function type information;
calling a second function interface, and sending the first function request to a second service module through the second function interface to realize the first function request;
the second function interface corresponds to the first function type information, and the first service module is different from the second service module.
An embodiment of the present disclosure further provides an electronic device, which at least includes a memory and a processor, where the memory stores a computer program, and the processor implements the steps of the service module management method of the above system when executing the computer program on the memory.
Embodiments of the present disclosure also provide a storage medium having a computer program stored thereon, where the computer program is executed by a processor to implement the steps of the service module management method of the above-mentioned system.
The method and the device have the advantages that the system functions are split in a modularization mode, so that the complexity of the interior of each module is reduced, the development, modification and reconfiguration of each module can be realized quickly and efficiently, the functions of other systems can be developed in a module mode and flexibly added or removed, the problem of repeatedly developing basic functions is solved, the maintenance cost and the maintenance period are reduced, and the effect of quickly changing service requirements of users is met.
Drawings
Fig. 1 is a block diagram of a service module management system according to a first embodiment of the present disclosure;
fig. 2 is a block diagram of a service module management system according to a second embodiment of the present disclosure;
fig. 3 is a block diagram of a service module management system according to a third embodiment of the present disclosure;
fig. 4 is a block diagram of a service module management system according to a fourth embodiment of the present disclosure;
fig. 5 is a block diagram of a service module management system according to a fifth embodiment of the present disclosure;
fig. 6 is a block diagram of a service module management system according to a sixth embodiment of the present disclosure;
FIG. 7 is a flow chart of a method for managing service modules of a system according to an embodiment of the present disclosure;
fig. 8 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present disclosure.
Detailed Description
Various aspects and features of the present application are described herein with reference to the drawings.
It will be understood that various modifications may be made to the embodiments of the present application. Accordingly, the foregoing description should not be construed as limiting, but merely as exemplifications of embodiments. Those skilled in the art will envision other modifications within the scope and spirit of the application.
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the application and, together with a general description of the application given above and the detailed description of the embodiments given below, serve to explain the principles of the application.
These and other characteristics of the present application will become apparent from the following description of preferred forms of embodiment, given as non-limiting examples, with reference to the attached drawings.
It is also to be understood that although the present application has been described with reference to some specific examples, those skilled in the art are able to ascertain many other equivalents to the practice of the present application.
The above and other aspects, features and advantages of the present application will become more apparent in view of the following detailed description when taken in conjunction with the accompanying drawings.
Specific embodiments of the present application are described hereinafter with reference to the accompanying drawings; however, it is to be understood that the disclosed embodiments are merely exemplary of the application, which can be embodied in various forms. Well-known and/or repeated functions and constructions are not described in detail to avoid obscuring the application of unnecessary or unnecessary detail. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present application in virtually any appropriately detailed structure.
The specification may use the phrases "in one embodiment," "in another embodiment," "in yet another embodiment," or "in other embodiments," which may each refer to one or more of the same or different embodiments in accordance with the application.
An embodiment of a first aspect of the present disclosure provides a business module management system.
Fig. 1 shows a block diagram of a service module management system according to a first embodiment of the present disclosure.
As shown in fig. 1, the system 10 includes: the system comprises a plurality of service modules and a common module 107, wherein the common module 107 is connected with the plurality of service modules through functional interfaces; the common module 107 is configured to receive a first function request sent by the first service module 101 through the first function interface 1011; wherein the first function request comprises at least first function type information;
the common module 107 is further configured to invoke a second function interface 1021 corresponding to the first function type information based on the first function type information included in the first function request, and send the first function request to the second service module 102 through the second function interface 1021 to implement the first function request. The second function interface 1021 corresponds to the first function type information, and the first service module 101 is different from the second service module 102.
In the embodiment of the present disclosure, as long as the module implementing the corresponding service function is associated with the corresponding interface set on the common module, when the function is added or removed from each module, since each module is connected to the common module through the functional interface, the added or removed module does not affect other modules, and the call relationship between all modules does not need to be adjusted, thereby saving the problem of repeatedly developing the basic function.
In some embodiments, the first function request mainly refers to a function request to be performed by the service module. Taking the outpatient service information management module as an example, the user wants to call the storage condition of the medicine through the outpatient service information management module, and the first function request refers to a request of calling the storage condition of the medicine sent by the outpatient service information management module; taking the hospitalization information management module as an example, the user wants to invoke the medication condition of the patient through the hospitalization information management module, and the first function request refers to a request of "invoking the medication condition of the patient" sent by the hospitalization information management module.
In some embodiments, the first function type information refers primarily to the specific function type of the function request, typically represented in a string or code. For example, when the function request is "call storage of medicine", the function type information corresponding to the function request may be represented as 001A (storage of medicine); if the function request is "call patient hospitalization", the function type information corresponding to the function request may be represented as 001B (patient hospitalization).
In some embodiments, the system 10 further includes a portal module, which may be a UI interface, and is specifically used for implementing operations such as human-computer interaction on the interface.
In some embodiments, portal module and common module 107 may be the base modules of the system in which the operator interface is essential in system 10.
In some embodiments, the service module type may be set according to actual situations, for example, the service module may further include a permission module, a report module, a timing task module, a log module, a picture module, and the like.
Taking an HIS system (hospital information system) as an example, the HIS system can be split into: the system comprises a basic configuration center module, an outpatient service information management module, a medicine information management module, a sanitary material information management module, an in-hospital management module, an electronic medical record module and the like. The specific service module can be split and set according to the actual situation.
In some embodiments, if the out-patient department where the user is located wants to call the drug a inventory condition, as shown in fig. 2, the first service module 101 is an out-patient information management module, and the second service module 102 is a drug information management module, the specific call process is as follows:
the public module 107 receives the function request of "calling inventory condition of drug a" sent by the outpatient service information management module 101 through the first function interface 1011, then the public module 107 calls the second function interface 1021 corresponding to the function type according to the function type of "inventory condition of drug" corresponding to the function, and sends the received function request of "calling inventory condition of drug a" to the drug information management module 102 through the second function interface 1021 to realize the function request of "calling inventory condition of drug a" and further call inventory condition of drug a.
In this embodiment, the first function request mainly refers to a function request of "call drug a stock situation", and the first function type information mainly refers to a function type of "drug stock situation". In the calling process, the second function interface 1021 corresponds to the first function type information, that is, the second function interface 1021 corresponds to the function type of "drug stock status".
In some embodiments, the common module 107 is further configured to determine whether the second function interface 1021 is associated with the second service module 102 to implement a function corresponding to the first function type information when the second function interface 1021 is called; under the condition that the second function interface 1021 is associated with the second service module 102, the first function request is sent to the second service module 102 through the second function interface 1021 to realize the first function request; in case the second functional interface 1021 is not associated with the second service module 102, default information is sent to the first service module 101 via the first functional interface 1011. For example, the default information may include error reporting information, blank messages, etc., which may be set according to actual situations.
In some embodiments, each business module has at least one functional interface corresponding thereto on a common module. For example, a service module a, where a function interface a corresponding to the module a exists on a common module, can implement the function request 1; and the service module B has function interfaces B1 and B2 corresponding to the module B on a common module, wherein the function interface B1 can realize the function request 1, and the function interface B2 can realize the function request 2.
Taking the case that the outpatient department where the user is located wants to call the inventory condition of the drug a as an example, as shown in fig. 2, the first service module 101 is an outpatient information management module, the second service module 102 is a drug information management module, and the specific call process is as follows:
after the public module 107 receives the function request of "calling the inventory status of drug a" sent by the outpatient service information management module 101 through the first functional interface 1011, when the public module 107 calls the corresponding second functional interface 1021 according to the function type of "inventory status of drug", it will be determined preferentially whether the second functional interface 1021 is associated with the drug information management module 102.
In the case where the drug information management module 102 is associated with the second function interface 1021, the common module 107 sends a function request of "call drug inventory condition" to the drug information management module 102 through the second function interface 1021 to implement the function request of "call drug a inventory condition".
In the event that the second functional interface 1021 is not associated with the drug information management module 102, the common module 107 sends default information to the clinic information management module via the first functional interface 1011.
In some embodiments, in the case that the association relationship between the second function interface 1021 and the second service module 102 is removed, and the association relationship between the second function interface 1021 and the third service module 103 is added, the common module 107 is further configured to send the first function request to the third service module 103 through the second function interface 1021 to implement the first function request; wherein the third service module 103 is different from the second service module 102.
In some embodiments, the third module 103 is different from the second service module 102, and the third module 103 may also implement the function of the second module, i.e. the third module 103 may implement the first function request.
In some embodiments, the third service module 103 may be a functional extension or functional split, etc., of the second module 102 service. For example, the second service module 102 splits a part of the request for implementing the first function to form a third service module; alternatively, the second service module 102 is merged with other modules, and so on.
Taking the case that the outpatient department where the user is located wants to call the inventory condition of the drug a as an example, referring to fig. 2 and fig. 3, the first service module 101 is an outpatient information management module, the second service module 102 is a drug information management module, and the third service module 103 is a warehouse information management module. The specific calling process is as follows:
in the system 10, when the drug information management module 102 is removed and the association relationship between the second function interface 1021 and the warehouse information management module 103 is newly added, after the public module 107 receives the function request of "call drug a stock condition" sent by the outpatient service information management module 101 through the first function interface 1011, the public module 107 sends the function request of "call drug stock condition" to the warehouse information management module 103 through the second function interface 1021 to realize the function request of "call drug a stock condition".
In the embodiment of the present disclosure, the removal or addition (replacement) of the service module can be flexibly implemented, as long as the module implementing the corresponding service function is associated with the corresponding interface set on the common module, and the adjustment of the call relationship between all modules when the function is added or removed is not required to be performed on the whole, so that the problem of repeatedly developing the basic function is solved, the maintenance cost and period are reduced, and the effect of quickly changing the service requirement of the user is satisfied.
In some embodiments, an association relationship between the second function interface 1021 and the fourth service module 104 is newly added in the system, and when the priority of the fourth service module 104 is greater than that of the second service module 104, the common module 107 is further configured to send the first function request to the fourth service module 104 through the second function interface 1021 to implement the first function request; wherein the fourth service module 104 is different from the second service module 102.
In some implementations, the fourth service module and the second service module may implement part of the same functional request. That is, the fourth service module and the second service module can implement the first function request.
Taking the case that the outpatient department where the user is located wants to call the drug a sales condition as an example, referring to fig. 2 and fig. 4, the first service module 101 is an outpatient information management module, the second service module 102 is a drug information management module, and the fourth service module 104 is a sales information management module. The specific calling process is as follows:
in the system 10, when an association relationship between the second function interface 1021 and the sales information management module 104 is added, that is, when the second function interface is associated with both the sales information management module 104 and the drug information management module 102, after the public module 107 receives a function request of "call drug a sales condition" sent by the outpatient service information management module 101 through the first function interface 1011, if the priority of the sales information management module 104 is greater than that of the drug information management module 102, the public module 107 sends the function request of "call drug a stock condition" to the sales information management module 104 through the second function interface 1021 to realize the function request of "call drug a sales condition"; if the priority of the drug information management module 102 is higher than that of the sales information management module 104, the common module 107 sends the function request of "call drug a stock condition" to the drug information management module 102 through the second function interface 1021 to implement the function request of "call drug a sales condition".
In the embodiment of the present disclosure, when the functions of the service modules are repeated, which service module to use can be determined by setting the priority of the service module, so that flexible operation of the service module is realized, and convenience is brought to users.
In some embodiments, in the system, in a case that an association relationship between the second function interface 1021 and the fifth service module 105 is newly added, the common module 107 is further configured to send a second function request to the fifth service module 105 through the second function interface 1021 to implement the second function request; the first function request is different from the second function request, and the second function interface 1021 corresponds to the second function type information in the second function request.
In some embodiments, the function interface may correspond to one function type information, may also correspond to a plurality of function type information, and may be set according to an actual situation.
Taking the out-patient department where the user is located to call the patient B hospitalization condition and the drug a inventory condition as an example, referring to fig. 2 and fig. 5, the first service module 101 is an out-patient information management module, the second service module 102 is a drug information management module, and the fifth service module 105 is an in-patient information management module. The specific calling process is as follows:
in the system 10, when an association relationship between the second function interface 1021 and the hospitalization information management module 105 is newly added, that is, when the second function interface 1021, the hospitalization information management module 105 and the drug information management module 102 are all associated, after the public module 107 receives a function request of "invoke patient B hospitalization condition" sent by the outpatient service information management module 101 through the first function interface 1011, the public module 107 sends the function request of "invoke patient B hospitalization condition" to the hospitalization information management module 105 through the second function interface to implement the function request of "invoke patient B hospitalization condition"; meanwhile, after the public module 107 receives the function request of "call drug a inventory condition" sent by the outpatient service information management module 101 through the first function interface 1011, the public module 107 sends the function request of "call drug a inventory condition" to the drug information management module 102 through the second function interface 1021 to realize the function request of "call drug a inventory condition", and further call the drug a inventory condition.
In this embodiment, the second function interface 1021 corresponds to a function type of "drug inventory condition" and a function type of "patient hospitalization condition".
In the embodiment of the disclosure, one functional interface is associated with a plurality of service modules, so that the complexity in each module is reduced, the problem of repeatedly calling the functional interface is solved, and the effects of reducing the maintenance cost and the maintenance period are achieved.
In some embodiments, in a case that an association relationship between the third function interface 1031 and the sixth service module 106 is newly added in the system, the common module 107 is further configured to send a third function request to the sixth service module 106 through the third function interface 1031 to implement the third function request; the first function request is different from the third function request, and the third function interface 1031 corresponds to the third function type information in the third function request.
Taking the case that the outpatient department where the user is located wants to call the cost of the patient C as an example, with reference to fig. 2 and fig. 6, the first service module 101 is an outpatient information management module, the second service module 102 is a drug information management module, and the sixth service module 106 is a charging information management module. The specific calling process is as follows:
in the system 10, when an association relationship between the third function interface 1031 and the billing information management module 106 is added, that is, when the third function interface 1031 has an association relationship with the billing information management module 106 and the second function interface 1021 has an association relationship with the drug information management module 102, after the public module 107 receives a function request of "call patient C fee condition" sent by the outpatient service information management module 101 through the first function interface 1011, the public module 107 sends the function request of "call patient C fee condition" to the billing information management module 106 through the third function interface 1031 to realize the function request of "call patient C fee condition".
In this embodiment, the third function request mainly refers to a function request of "invoke patient C fee condition", and the third function type information mainly refers to a function type of "patient fee condition".
In this embodiment, the third functional interface 1031 corresponds to the third function type information, i.e. the third functional interface 1031 corresponds to the function type "patient cost situation".
In some embodiments, the common module is further specifically configured to receive feedback information of the second service module, and send the feedback information to the first service module through the first functional interface.
Taking the case that the outpatient department where the user is located wants to call the inventory of the drug a as an example, referring to fig. 2, after the public module 107 sends the received first function request to the drug information management module 102 through the second function interface 1021 to realize the first function request, the public module 107 sends the inventory information of the drug a received and fed back by the drug information management module 102 to the outpatient information management module 101 through the first function interface 1011 for the user to use.
In some embodiments, the functional interfaces define only in-and out-references and give default implementations (all null implementations), these codes need to be placed in a common module, which is referenced by other business modules.
In some embodiments, the service module has different functional capabilities, and can be set according to the needs of the user, for example, the drug information management module can be split into a drug name management module, a drug code management module, and the like, and is not described herein again to avoid repetition.
In the embodiment of the disclosure, the system functions are split in a modularized manner, so that the complexity in each module is reduced, the development, modification and reconfiguration of each module can be realized quickly and efficiently, and the functions of other systems can be developed in a module manner and flexibly added or removed, so that the problem of repeatedly developing basic functions is solved, the maintenance cost and period are reduced, and the effect of quickly changing service requirements of users is met.
The embodiment of the second aspect of the disclosure provides a flow chart of a business module management method of a system.
Fig. 7 is a flowchart of a method for managing a service module in a system according to an embodiment of the present disclosure. As shown in fig. 7, the service module management method of the system includes:
s211, receiving a first function request of a first service module through a first function interface; wherein the first function request includes at least first function type information.
S212, a second function interface is called, and the first function request is sent to a second service module through the second function interface so as to realize the first function request.
The second function interface corresponds to the first function type information, and the first service module is different from the second service module.
Embodiments of a third aspect of the present disclosure provide an electronic device.
Fig. 8 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present disclosure, as shown in fig. 8, the electronic device at least includes a memory 302 and a processor 301, the memory 302 stores a computer program, and the processor 301 implements the method provided in any embodiment of the present disclosure when executing the computer program on the memory 302. Illustratively, the electronic device computer program steps are as follows S11-S12:
s11, receiving a first function request of a first service module through a first function interface; wherein the first function request includes at least first function type information.
S12, calling a second function interface, and sending the first function request to a second service module through the second function interface to realize the first function request.
The second function interface corresponds to the first function type information, and the first service module is different from the second service module.
When the processor executes the second function interface stored in the memory and calls the second function interface, and determines whether the second function interface is associated with the second service module, the processor specifically executes the following computer program:
under the condition that the second function interface is associated with the second service module, the first function request is sent to the second service module through the second function interface so as to realize the first function request;
and sending default information to the first service module through the first functional interface under the condition that the second functional interface is not associated with the second service module.
When the processor executes the association relationship between the second functional interface and the second service module, which is stored in the memory, and the association relationship between the second functional interface and the third service module is removed, and the association relationship between the second functional interface and the third service module is newly added, the processor specifically executes the following computer program:
sending the first function request to the third service module through the second function interface to realize the first function request;
wherein the third service module is different from the second service module.
In some embodiments, the electronic device further comprises: an input device 303 and an output device 304;
the processor 301, the memory 302, the input means 303 and the output means 304 in the electronic device may be connected by a bus or other means.
The memory 302 is a non-transitory computer-readable storage medium that can be used to store software programs, computer-executable programs. The processor 301 executes various functional applications of the server and data processing by running software programs and instructions stored in the memory 302, namely, implements the service module management method of the above-described method embodiment.
The memory 302 may include high speed random access memory and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device.
In some embodiments, memory 302 optionally includes memory located remotely from processor 301, which may be connected to a terminal device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 303 may include receiving input numeric or character information and generating key signal inputs related to user settings and function controls of the electronic device.
The output means 304 may comprise a display device such as a display screen.
Embodiments of the third aspect of the present disclosure provide a storage medium, which is specifically a computer-readable medium, storing a computer program, which when executed by a processor implements the method provided in any of the embodiments of the present disclosure, including the following steps S21 to S22:
s21, receiving a first function request of a first service module through a first function interface; wherein the first function request includes at least first function type information.
S22, calling a second function interface, and sending the first function request to a second service module through the second function interface to realize the first function request.
The second function interface corresponds to the first function type information, and the first service module is different from the second service module.
When the computer program is executed by the processor to call the second functional interface and determine whether the second functional interface is associated with the second service module, the computer program is specifically executed by the processor to perform the following steps:
under the condition that the second function interface is associated with the second service module, the first function request is sent to the second service module through the second function interface so as to realize the first function request;
and sending default information to the first service module through the first functional interface under the condition that the second functional interface is not associated with the second service module.
When the processor executes the computer program, and the incidence relation between the second functional interface and the second service module is removed, and the incidence relation between the second functional interface and the third service module is newly added, the processor specifically executes the following steps:
sending the first function request to the third service module through the second function interface to realize the first function request;
wherein the third service module is different from the second service module.
Optionally, the computer-executable instructions, when executed by the computer processor, may also be configured to implement a technical solution of the service module management method provided by any embodiment of the present disclosure.
In the embodiment of the disclosure, the system functions are split in a modularized manner, so that the complexity in each module is reduced, the development, modification and reconfiguration of each module can be realized quickly and efficiently, and the functions of other systems can be developed in a module manner and flexibly added or removed, so that the problem of repeatedly developing basic functions is solved, the maintenance cost and period are reduced, and the effect of quickly changing service requirements of users is met.
The device provided by the embodiment of the present disclosure can execute the processes and steps of the above method embodiments, and further has a functional module corresponding to the above method embodiments, which can execute corresponding operations, and has corresponding technical effects, and in order to avoid repetition, details are not repeated here.
The above embodiments are merely exemplary embodiments of the present disclosure, which is not intended to limit the present disclosure, and the scope of the present disclosure is defined by the claims. Various modifications and equivalents of the disclosure may occur to those skilled in the art within the spirit and scope of the disclosure, and such modifications and equivalents are considered to be within the scope of the disclosure.
Claims (10)
1. A business module management system, the system comprising: the system comprises a plurality of service modules and a public module, wherein the public module is connected with the plurality of service modules through functional interfaces;
the public module is used for receiving a first function request of the first service module through the first function interface; wherein the first function request includes at least first function type information;
the public module is also used for calling a second function interface and sending the first function request to a second service module through the second function interface so as to realize the first function request;
the second function interface corresponds to the first function type information, and the first service module is different from the second service module.
2. The service module management system according to claim 1, wherein said common module is further configured to, when said second function interface is called, determine whether said second function interface is associated with said second service module;
under the condition that the second function interface is associated with the second service module, the first function request is sent to the second service module through the second function interface so as to realize the first function request;
and sending default information to the first service module through the first functional interface under the condition that the second functional interface is not associated with the second service module.
3. The service module management system according to claim 2, wherein in a case that the association relationship between the second functional interface and the second service module is removed and the association relationship between the second functional interface and the third service module is newly added, the common module is further configured to send the first functional request to the third service module through the second functional interface to implement the first functional request;
wherein the third service module is different from the second service module.
4. The service module management system according to claim 1, wherein the association relationship between the second function interface and the fourth service module is newly added, and when the priority of the fourth service module is higher than that of the second service module, the common module is further configured to send the first function request to the fourth service module through the second function interface to implement the first function request;
wherein the fourth service module is different from the second service module; the fourth service module has a function of implementing the first function request.
5. The service module management system according to claim 1, wherein in case of newly adding an association relationship between a second function interface and a fifth service module, the common module is further configured to send a second function request to the fifth service module through the second function interface to implement the second function request;
the first function request is different from the second function request, and the second function interface corresponds to second function type information in the second function request.
6. The service module management system according to claim 1, wherein in a case that an association relationship between a third function interface and a sixth service module is newly added, the common module is further configured to send a third function request to the sixth service module through the third function interface to implement the third function request;
the first function request is different from the third function request, and the third function interface corresponds to third function type information in the third function request.
7. The service module management system according to claim 1, wherein the common module is further specifically configured to receive feedback information of the second service module, and send the feedback information to the first service module through the first functional interface.
8. A method for managing service modules of a system, the method comprising:
receiving a first function request of a first service module through a first function interface; wherein the first function request includes at least first function type information;
calling a second function interface, and sending the first function request to a second service module through the second function interface to realize the first function request;
the second function interface corresponds to the first function type information, and the first service module is different from the second service module.
9. An electronic device comprising at least a memory, a processor, a computer program stored on said memory, characterized in that said processor, when executing the computer program on said memory, implements the steps of the service module management method of the system of claim 8.
10. A storage medium storing a computer program, characterized in that the computer program, when being executed by a processor, carries out the steps of the service module management method of the system of claim 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111528895.2A CN114171168A (en) | 2021-12-14 | 2021-12-14 | Business module management system, method, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111528895.2A CN114171168A (en) | 2021-12-14 | 2021-12-14 | Business module management system, method, electronic device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114171168A true CN114171168A (en) | 2022-03-11 |
Family
ID=80486525
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111528895.2A Pending CN114171168A (en) | 2021-12-14 | 2021-12-14 | Business module management system, method, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114171168A (en) |
-
2021
- 2021-12-14 CN CN202111528895.2A patent/CN114171168A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110838071B (en) | Policy data processing method, device and server | |
| CN112867988A (en) | Implementing compliance settings by a mobile device to follow a configuration scenario | |
| CN109445841B (en) | Interface document management method, device, server and storage medium | |
| CN111371898B (en) | Message monitoring method, device, equipment and storage medium | |
| US20170147368A1 (en) | Dynamic Agent Delivery | |
| CN111240940B (en) | Real-time service monitoring method and device, electronic equipment and storage medium | |
| US20150319116A1 (en) | System and method for multi-channel delivery of transformed and augmented messages in real-time | |
| CN112860342A (en) | Method, device, equipment, system and storage medium for microservice configuration | |
| CN111338834A (en) | Data storage method and device | |
| CN114528517A (en) | View processing method and device, electronic equipment and computer readable medium | |
| US20030084062A1 (en) | Method and system for automated web reports | |
| CN112417042A (en) | Method and device for processing service request | |
| CN109445966B (en) | Event processing method, device, medium and computing equipment | |
| CN114171168A (en) | Business module management system, method, electronic device and storage medium | |
| US11301538B1 (en) | Data management in multi-application web pages | |
| CN111460020B (en) | Method, device, electronic equipment and medium for resolving message | |
| CN112202605A (en) | Service configuration method, device, equipment and storage medium | |
| CN113778560B (en) | Method, system, equipment and medium for custom development and execution of hospital treatment process | |
| CN112688863B (en) | Gateway data processing method and device and electronic equipment | |
| CN114253520B (en) | Interface code generation method and device | |
| CN111128334B (en) | Learning method and device of prescription generation system, electronic equipment and storage medium | |
| CN110727898B (en) | OTA website event assisted processing method, system, equipment and storage medium | |
| US20160248823A1 (en) | Messaging protocol | |
| JP4628551B2 (en) | Dynamic installation method and computer system | |
| CN114741251A (en) | Processing method and device for embedded point, electronic equipment and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |