A service bus for heterogeneous business information system and its implementation method

Abstract

The present invention provides a service bus for a heterogeneous business information system and an implementation method thereof, the method comprising: setting a unified call specification and a third-party service access specification for the bus; establishing a two-way service authentication channel for the bus; introducing a bus whitelist mechanism; providing an encryption function for the bus service; providing a message content conversion function for the bus; and providing a message structure conversion function for the bus. The present invention takes the business application scenario as the core, and through various technologies such as information exchange and integration, integrates the information of various dispersed and heterogeneous subsystems on an information sharing platform, thereby realizing a full-stack information-based, flexible customization, and sustainable expansion of the medical service bus system.

Description

Technical Field

[0001] The present invention relates to the technical field of service bus construction, and in particular to a method for realizing a service bus of a heterogeneous business information system. Background Art

[0002] With the continuous improvement of information construction, the same unit has more and more heterogeneous business information systems. For example, hospital platforms usually include electronic medical record systems (EMR), hospital information systems (HIS), clinical information systems (CIS), radiology information systems (RIS), physical examination information systems (PEIS), operating room information systems (ORIS), hospital appointment management systems, unified payment reconciliation platforms, and supply chain management systems (SPD). Due to the different development times and development teams, these systems often use different development languages. Their technical architecture differences, inconsistent data formats, incompatible protocols, and the phased, technical, economic, and human factors of information construction are the main causes of heterogeneity in business information systems. The various architectures, databases, data dictionary standards, and external interfaces of different business information systems make the management of business information exchange and sharing more and more complicated and difficult. The problem of "information islands" has become increasingly prominent, restricting the development of information integration.

[0003] If a service bus can be built, the integration of various business information systems can be effectively achieved, which will facilitate data exchange and sharing between heterogeneous business systems of such units and solve the problem of mutual recognition and sharing of business information. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a method for implementing a service bus for a heterogeneous business information system. Taking the business application scenario as the core, the information of the scattered and heterogeneous subsystems is integrated on an information sharing platform through various technologies such as information exchange and integration, thereby realizing a full-stack trusted, flexible, customizable, and sustainably expandable service bus system.

[0005] In a first aspect, the present invention provides a method for implementing a service bus of a heterogeneous business information system, comprising:

[0006] Set unified calling specifications and third-party service access specifications for the bus;

[0007] Establish a two-way service authentication channel for the bus, so that each business information system can configure the service list allowed to be called and the business information system list allowed to be called;

[0008] Introduce the bus whitelist mechanism to add trustworthy business information systems to the whitelist. The business information systems in the whitelist will obtain a persistent TOKEN for identity authentication and authorization in subsequent service calls; and provide a key for business information systems that are not in the whitelist, so that the business information systems can obtain a temporary TOKEN through the key to request services;

[0009] Provide encryption function for bus service, so as to facilitate encrypted transmission and communication between business information systems;

[0010] Provide message content conversion function for the bus, convert the content of messages passing through the bus, convert standardized data with non-standardized data, and provide mutual recognition and sharing for various business information systems;

[0011] Provides message structure conversion function for the bus, and converts the request message structure of one business information system into the request message structure required by another business information system through mapping.

[0012] In a second aspect, the present invention provides a service bus for a heterogeneous business information system, comprising:

[0013] A calling specification setting module is used to set a unified calling specification for the bus;

[0014] The access specification setting module is used to set a unified third-party service access specification for the bus;

[0015] The service authentication channel module is used to establish a two-way service authentication channel for the bus, so that each business information system can configure a list of services that can be called, and a list of business information systems that can be called;

[0016] The whitelist module is used to introduce the bus whitelist mechanism and add the trustworthy business information systems to the whitelist. The business information systems in the whitelist will obtain a persistent TOKEN for identity authentication and authorization in subsequent service calls; and provide a key for the business information systems that are not in the whitelist, so that the business information systems can obtain a temporary TOKEN through the key to request services;

[0017] The encryption module is used to provide encryption functions for bus services, so as to facilitate encrypted transmission and communication between business information systems;

[0018] The data mapping management module is used to provide the bus with a message content conversion function, convert the content of messages passing through the bus, and convert standardized data into non-standardized data for mutual recognition and sharing by various business information systems;

[0019] The message structure conversion module is used to provide a message structure conversion function for the bus, and converts the request message structure of a business information system into the request message structure required by another business information system through mapping.

[0020] The one or more technical solutions provided by the present invention have at least the following technical effects or advantages: The present invention takes the business application scenario as the core, and realizes a full-stack trusted, flexible and customizable service bus system with sustainable expansion. The service bus provides the ability of data mutual recognition and sharing, and unified service reuse, which meets the interconnection and interoperability application requirements between the unit's heterogeneous business systems. By transforming the original one-to-many interfaces of each system into a one-to-one interface mode, the information islands of the heterogeneous business systems are eliminated, and services such as business process unification and data standardization are provided to realize platform-based service governance and data integration unification, thereby reducing the system's maintenance costs and management workload. Through the independently developed modular integration engine, message content encryption and interconversion between different protocols are realized, providing a more efficient and secure service integration solution under the trusted ecology. It is particularly suitable for interconnection and interoperability application requirements at the hospital level and medical community level, for example.

[0021] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.

[0023] Figure 1 is a flow chart of the method in Embodiment 1 of the present invention;

[0024] Figure 2 An example diagram of an authorization interface for a system call service in a two-way authentication according to an embodiment of the present invention;

[0025] Figure 3 This is an example diagram of the authorization interface of the system that is allowed to be called in the two-way authentication in the embodiment of the present invention;

[0026] Figure 4 A schematic diagram of a process flow when a non-whitelisted business information system requests a service in an embodiment of the present invention;

[0027] Figure 5 This is an example diagram of an interface for managing and maintaining a business dictionary of a requester's business information system in message content conversion according to an embodiment of the present invention;

[0028] Figure 6 An example diagram of an interface for configuring a mapping relationship between a business dictionary and a standard dictionary in message content conversion in an embodiment of the present invention;

[0029] Figure 7 An example diagram of a configuration interface for the relationship between a message message and a dictionary in message content conversion in an embodiment of the present invention;

[0030] Figure 8 This is an example diagram of a configuration interface for message body conversion mapping according to an embodiment of the present invention;

[0031] Fig. 9 This is an example diagram of a service rule list in accordance with the first embodiment of the present invention;

[0032] Fig.10 An example diagram of a configuration interface for service rules according to an embodiment of the present invention;

[0033] Fig.11 This is a schematic diagram of the structure of the service bus in the second embodiment of the present invention. DETAILED DESCRIPTION

[0034] The embodiment of the present application provides a method for implementing a service bus for a heterogeneous business information system. With business application scenarios as the core, the information of scattered and heterogeneous subsystems is integrated on an information sharing platform through various technologies such as information exchange and integration, thereby realizing a full-stack, flexibly customized, and sustainably expandable medical service bus system.

[0035] The technical solution in the embodiment of this application has the following general idea: taking the business application scenario as the core, setting a unified calling specification and third-party service access specification for the bus, establishing a two-way service authentication channel, introducing a bus whitelist mechanism, providing encryption function, message content conversion function, and message structure conversion function for the bus service; it also provides asynchronous return function, service routing, filtering function, and endpoint attention or merge return function. Thus, a full-stack trust creation, flexible customization, and sustainable expansion service bus system is realized to meet the interconnection and interoperability application requirements between the unit's heterogeneous business systems. By transforming the original one-to-many interfaces of each system into a one-to-one interface (all connected to the bus service) mode, the information islands of the heterogeneous business systems are eliminated, and services such as business process unification and data standardization are provided, which reduces the system's maintenance costs and management workload.

[0036] Embodiment 1

[0037] like Figure 1 As shown, this embodiment provides a method for implementing a service bus of a heterogeneous business information system, including:

[0038] Set unified calling specifications and third-party service access specifications for the bus;

[0039] The bus calling specifications are shown in the following table:

[0040]

[0041]

[0042] The third-party service interface is agreed upon as follows:

[0043]

[0044]

[0045] A two-way service authentication channel is established for the bus, so that each business information system can configure a list of services that can be called, as well as a list of business information systems that can be called; the services that can be called are the services that the system can call, such as Figure 2 As shown in the figure, the scope of services that each system can call, that is, the list of services allowed to be called, can be defined through configuration to ensure that only specific, authorized services can be accessed by the system. The list of business information systems allowed to be called is the list of systems that can call the service, such as Figure 3 As shown in Figure 1, by setting a list of systems that are allowed to be called, you can ensure that the service only responds to requests from trusted systems or services. The configuration of these two perspectives together constitutes a two-way authentication mechanism for service calls, which effectively intercepts illegal requests.

[0046] The bus whitelist mechanism is introduced to add trustworthy business information systems to the whitelist. The business information systems in the whitelist will obtain a persistent TOKEN for authentication and authorization in subsequent service calls. This mechanism simplifies the authentication process of the whitelist system and improves efficiency. For business information systems that are not included in the whitelist, a key is provided for the business information system to obtain a temporary TOKEN to request services; Figure 4 As shown in the figure, it is a service request process for a non-whitelist system. The validity period of the temporary TOKEN can be flexibly set to further control access rights and security.

[0047] Provide encryption function for bus service, so that each business information system can transmit encrypted messages between each other; the encryption algorithm used by the encryption function is RSA. When the business information system as the requester needs to send a message, the encryption SDK provided is used to encrypt the request message with the public key and then transmit it to the bus securely. After the bus receives it, it uses the corresponding private key to decrypt it, so as to restore the original request message. The core of the RSA algorithm is that it uses a pair of unique keys, public key and private key, to realize message encryption and decryption. The public key is public and used to encrypt messages, while the private key is confidential and is specifically used to decrypt messages encrypted by the public key. The encryption SDK plays a vital role in the entire encryption and decryption process. It not only simplifies the complex operations of encryption and decryption, but also ensures the safe management and use of keys. By adopting this advanced encryption technology and tools, we can provide users with a safe and efficient bus service, fully guaranteeing the security and privacy of their data.

[0048] Provide the bus with a message content conversion function, convert the content of messages passing through the bus, and convert standardized data into non-standardized data for mutual recognition and sharing by various business information systems; because some units, such as hospitals, have many internal business information systems, each business information system has its own business dictionary and corresponding patient identification, and there are often inconsistent data standards between different systems in data exchange, and the problem of mutual recognition is that in order to solve this problem, a data mapping management module can be built into the bus to convert the content of messages passing through the bus. The bus can convert standardized data into non-standardized data, which facilitates the business information system to receive and understand data, and can also convert non-standardized data into standardized data to achieve unified data processing, so as to achieve the purpose of mutual recognition and sharing. Among them, the data mapping management module provides the following three configuration functions:

[0049] like Figure 5 As shown, a business dictionary of a business information system for managing maintenance requests;

[0050] like Figure 6 As shown, a mapping relationship between the business dictionary and the standard dictionary is configured;

[0051] like Figure 7 As shown, the relationship between the request message node and the business dictionary is configured on the bus;

[0052] The data mapping management module realizes the standardization and commercialization of the dictionary through the above configuration.

[0053] Provides message structure conversion function for the bus, and converts the request message structure of one business information system into the request message structure required by another business information system through mapping, so as to reduce the interface modification between various systems. Figure 8 As shown, the realization of the message structure conversion function is: the business specifications of the domestic standard interconnection and intercommunication interactive service are built into the bus, and the message structure supporting the business specifications is converted into a custom structure through mapping configuration to connect with existing services and understand the connotation of message nodes. For example: HL7 is an international medical information communication standard, and its message structure has a certain complexity. The HL7 specification of the domestic standard interconnection and intercommunication interactive service can be built into the bus. Through mapping configuration, the conversion of the HL7 message structure into a custom structure is supported, which is convenient for connecting with existing services and understanding the connotation of message nodes.

[0054] As a more optimal solution of this embodiment, it may also include:

[0055] Provide asynchronous return function for the bus. When the business information system is the requester and does not care about the return content of the request, it can be configured to be asynchronous by starting the asynchronous return configuration function. Asynchronization means that after sending a message to the bus, a successful response is immediately returned to the requesting system, and the bus then distributes the message to different downstream systems.

[0056] Provide service routing and filtering functions for the bus, so that the bus can send messages to specific business information systems according to specific rules; Fig. 9 As shown, for example, for the new service of the test report information of the hospital business information system, when the ORG_CODE node in the request message is equal to 35042622, the message will be pushed to the FY-A100_Maternal and Child Health Information System Interaction Interface and the FY-250_Maternal and Child Health Information System Interaction Service Interface. The rule configuration interface can be as follows Fig.10 shown.

[0057] Provide the bus with endpoint attention or merge return functions. When a business information system requests a service and multiple business information systems receive it, you can set whether to pay attention to the return of only one receiving system or merge the returns of all receiving systems.

[0058] Embodiment 2

[0059] Based on the same inventive concept, the present application also provides a device corresponding to the method in Example 1, see Example 2 for details.

[0060] like Fig.11 As shown, in this embodiment, a service bus of a heterogeneous business information system is provided, including:

[0061] A calling specification setting module is used to set a unified calling specification for the bus;

[0062] The access specification setting module is used to set a unified third-party service access specification for the bus;

[0063] The service authentication channel module is used to establish a two-way service authentication channel for the bus, so that each business information system can configure a list of services that can be called, and a list of business information systems that can be called;

[0064] The whitelist module is used to introduce the bus whitelist mechanism and add the trustworthy business information systems to the whitelist. The business information systems in the whitelist will obtain a persistent TOKEN for identity authentication and authorization in subsequent service calls; and provide a key for the business information systems that are not in the whitelist, so that the business information systems can obtain a temporary TOKEN through the key to request services;

[0065] The encryption module is used to provide encryption functions for bus services, so as to facilitate encrypted transmission and communication between business information systems;

[0066] The data mapping management module is used to provide the bus with a message content conversion function, convert the content of messages passing through the bus, and convert standardized data into non-standardized data for mutual recognition and sharing by various business information systems;

[0067] The message structure conversion module is used to provide a message structure conversion function for the bus, and converts the request message structure of a business information system into the request message structure required by another business information system through mapping.

[0068] Furthermore, the encryption algorithm adopted by the encryption function is RSA. When the business information system as the requesting party needs to send a message, the provided encryption SDK is used to encrypt the request message with the public key and then securely transmit it to the bus. After being received by the bus, it is decrypted using the corresponding private key to restore the original request message.

[0069] The data mapping management module provides the following three configuration functions:

[0070] Business dictionary for the business information system that manages maintenance requests;

[0071] Configuring a mapping relationship between the business dictionary and the standard dictionary;

[0072] configuring a relationship between a request message node and the service dictionary on a bus;

[0073] The data mapping management module realizes the standardization and commercialization of the dictionary through the above configuration.

[0074] The message structure conversion module is a business specification of a domestic standard interconnection and intercommunication interactive service built into the bus. Through mapping configuration, the message structure supporting the business specification is converted into a custom structure to connect to existing services and understand the connotation of message nodes.

[0075] Furthermore, as a better solution of this embodiment, this embodiment may also include:

[0076] The asynchronous return module is used to provide the asynchronous return function for the bus. When the business information system is the requester and does not pay attention to the return content of the request, the asynchronous return configuration function is started to configure and realize the asynchronization;

[0077] Routing and filtering modules are used to provide service routing and filtering functions for the bus, so that the bus can send messages to specific business information systems according to specific rules;

[0078] The endpoint attention or merged return module is used to provide the bus with endpoint attention or merged return functions. When a business information system requests a service and multiple business information systems receive it, it is set whether to only pay attention to the return of one receiving system or merge the returns of all receiving systems.

[0079] Since the service bus introduced in the second embodiment of the present invention is a device obtained after implementing the method of the first embodiment of the present invention, those skilled in the art can understand the specific structure and deformation of the device based on the method introduced in the first embodiment of the present invention, so it is not described here in detail. All devices used in the method of the first embodiment of the present invention belong to the scope of protection of the present invention.

[0080] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A method for implementing a service bus of a heterogeneous business information system, characterized by: include: Set unified calling specifications and third-party service access specifications for the bus; Establish a two-way service authentication channel for the bus, so that each business information system can configure the service list allowed to be called and the business information system list allowed to be called; Introduce the bus whitelist mechanism to add trustworthy business information systems to the whitelist. The business information systems in the whitelist will obtain a persistent TOKEN for identity authentication and authorization in subsequent service calls. A key is provided to the business information system that is not included in the whitelist, so that the business information system can obtain a temporary TOKEN through the key to request services; Provide encryption function for bus service, so as to facilitate encrypted transmission and communication between business information systems; Provide message content conversion function for the bus, convert the content of messages passing through the bus, convert standardized data with non-standardized data, and provide mutual recognition and sharing for various business information systems; Provides message structure conversion function for the bus, and converts the request message structure of one business information system into the request message structure required by another business information system through mapping.

2. The method for implementing a service bus of a heterogeneous business information system according to claim 1, characterized in that: The encryption algorithm used by the encryption function is RSA. When the business information system as the requesting party needs to send a message, the provided encryption SDK is used to encrypt the request message with the public key and then securely transmit it to the bus. After the bus receives it, it is decrypted using the corresponding private key to restore the original request message.

3. The method for implementing a service bus of a heterogeneous business information system according to claim 1, characterized in that: The message content conversion function is implemented through the built-in data mapping management module of the bus, and the data mapping management module provides the following three configuration functions: Business dictionary for the business information system that manages maintenance requests; Configuring a mapping relationship between the business dictionary and the standard dictionary; configuring the relationship between the request message node and the business dictionary on the bus; The data mapping management module realizes the standardization and commercialization of the dictionary through the above configuration.

4. The method for implementing a service bus of a heterogeneous business information system according to claim 1, characterized in that: The message structure conversion function is realized by: embedding the business specifications of domestic standard interconnection and intercommunication interactive services in the bus, and converting the message structure supporting the business specifications into a custom structure through mapping configuration to connect with existing services and understand the connotation of message nodes.

5. The method for implementing a service bus of a heterogeneous business information system according to claim 1, characterized in that: Also includes: Provide asynchronous return function for the bus. When the business information system is the requester and does not care about the return content of the request, it can be configured to achieve asynchronization by starting the asynchronous return configuration function. Provide service routing and filtering functions for the bus, so that the bus can send messages to specific business information systems according to specific rules; Provide the bus with endpoint attention or merge return functions. When a business information system requests a service and multiple business information systems receive it, you can set whether to pay attention to the return of only one receiving system or merge the returns of all receiving systems.

6. A service bus for a heterogeneous business information system, characterized by: include: A calling specification setting module is used to set a unified calling specification for the bus; The access specification setting module is used to set a unified third-party service access specification for the bus; The service authentication channel module is used to establish a two-way service authentication channel for the bus, so that each business information system can configure a list of services that can be called, and a list of business information systems that can be called; The whitelist module is used to introduce the bus whitelist mechanism and add trustworthy business information systems to the whitelist. The business information systems in the whitelist will obtain a persistent TOKEN for identity authentication and authorization in subsequent service calls; A key is provided to the business information system that is not included in the whitelist, so that the business information system can obtain a temporary TOKEN through the key to request services; The encryption module is used to provide encryption functions for bus services, so as to facilitate encrypted transmission and communication between business information systems; The data mapping management module is used to provide the bus with a message content conversion function, convert the content of messages passing through the bus, and convert standardized data into non-standardized data for mutual recognition and sharing by various business information systems; The message structure conversion module is used to provide a message structure conversion function for the bus, and converts the request message structure of a business information system into the request message structure required by another business information system through mapping.

7. The service bus of a heterogeneous business information system according to claim 6, characterized in that: The encryption algorithm used by the encryption function is RSA. When the business information system as the requesting party needs to send a message, the provided encryption SDK is used to encrypt the request message with the public key and then securely transmit it to the bus. After the bus receives it, it is decrypted using the corresponding private key to restore the original request message.

8. The service bus of a heterogeneous business information system according to claim 6, characterized in that: The data mapping management module provides the following three configuration functions: Business dictionary for the business information system that manages maintenance requests; Configuring a mapping relationship between the business dictionary and the standard dictionary; configuring the relationship between the request message node and the business dictionary on the bus; The data mapping management module realizes the standardization and commercialization of the dictionary through the above configuration.

9. The service bus of a heterogeneous business information system according to claim 6, characterized in that: The message structure conversion module is a business specification of a domestic standard interconnection and intercommunication interactive service built into the bus. Through mapping configuration, the message structure supporting the business specification is converted into a custom structure to connect to existing services and understand the connotation of message nodes.

10. The service bus of a heterogeneous business information system according to claim 6, characterized in that: Also includes: The asynchronous return module is used to provide the asynchronous return function for the bus. When the business information system is the requester and does not pay attention to the return content of the request, the asynchronous return configuration function is started to configure and realize the asynchronization; Routing and filtering modules are used to provide service routing and filtering functions for the bus, so that the bus can send messages to specific business information systems according to specific rules; The endpoint attention or merged return module is used to provide the bus with endpoint attention or merged return functions. When a business information system requests a service and multiple business information systems receive it, it is set whether to only pay attention to the return of one receiving system or merge the returns of all receiving systems.

Images