A data interface integrated configuration method for facilitating connection with external systems
By configuring external standard interfaces and interface integration platforms, the complexity of data interface integration between third-party systems and external systems in hospital information system is solved, and efficient and secure interface management and unified interface docking is achieved, which is suitable for non-internal systems. External system docking.
Patent Information
- Application Number
- CN202111581893.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-22
- Publication Date
- 2024-12-17
- Estimated Expiration
- 2041-12-22
AI Technical Summary
The existing technology has diversity in the data interface integration between third-party systems and external systems in hospital information systems, which leads to time-consuming and labor-intensive development, lack of visual configuration and low security, and cannot be applied to external systems that are not internal. System docking.
By configuring external standard interfaces, building an interface integration platform, binding third-party systems, performing field mapping and verification, providing a unified standard interface, and connecting the external system call interface integration platform with third-party systems to realize interface effectiveness verification and authorization management .
It reduces inefficient interface docking work, avoids the third-party system providing interface call permissions separately, improves the unity and security of interface management, and facilitates external system docking.
Smart Images

Figure CN114281500B_ABST
Abstract
Description
Technical Field
[0001] The invention belongs to the field of computer technology, and in particular relates to a data interface integrated configuration method that is convenient for docking with an external system. Background Art
[0002] In the hospital information system, when the service provider's PACS (Picture Archiving and Communication Systems) system is interconnected with a third-party system, it is necessary to integrate the hospital's third-party system with the service provider's PACS through webservice. For example, the service provider's PACS is integrated with the hospital's HIS (Hospital Information System) system through webservice.
[0003] At present, the webservice integration between the service provider's PACS system and the hospital's third-party system is to reference the wsdl (Web Services Description Language) file provided by the third-party system and do customized development based on the different WebService interfaces of each hospital. However, due to the variety of definitions of the WebService interfaces of the hospital's third-party systems, such as the interface name, number of parameters, and what kind of values each parameter needs to pass in, it is a waste of time and manpower to integrate the data of each hospital's third-party HIS system with the service provider's PACS system through customized development of the WebService interface.
[0004] The Chinese patent with publication number CN112769975A discloses a data integration method, device, server and storage medium. Configure the interface address of at least one third-party system, generate a parameter list for accessing a remote call method and calling the method, so as to transmit data between the third-party system and the internal system, determine the method name corresponding to the interface address of the third-party system according to the interface address of the third-party system, and determine the method list corresponding to the method name by reflection calling, dynamically call the method list corresponding to the address according to the interface address, and establish a field mapping relationship according to the field name in the method list corresponding to the method name and the field name of the internal standard field obtained, so as to realize data integration between the internal system and the third-party system by only providing the interface address, interface name and method list, without customized development for each interface of the third-party system, improving the data integration efficiency of the internal system and the third-party system, and facilitating interface maintenance. However, the patent still has the following defects: first, its third-party system is limited to the hospital's internal system and is not applicable to other third-party systems that need to be integrated; second, the system call is limited to the webservice method, and the scope of application is narrow; third, there is no design for the visual configuration and visual verification process, and the efficiency is low; fourth, there is no configuration authorization function, and the system security is low; finally, since the third-party system is an internal system, it is generally not desired to provide the interface call permissions related to the external system separately.
[0005] Therefore, there is an urgent need to develop a data interface integration configuration method that is easy to connect with external systems, replacing the third-party system to provide a unified standard interface service to the outside world. Summary of the invention
[0006] The purpose of the present invention is to provide a data interface integrated configuration method that is convenient for docking with an external system in view of the problems existing in the prior art.
[0007] To achieve the above object, the technical solution adopted by the present invention is:
[0008] According to one aspect of the present invention, there is provided a data interface integration configuration method for facilitating connection with an external system, comprising the following steps:
[0009] S1, configure external standard interfaces and build an interface integration platform;
[0010] S2, configure the integration system and connect the third-party system with the interface integration platform;
[0011] S3, configure the field mapping between the third-party system and the interface integration platform;
[0012] S4, verify the interface integration platform, and connect it with the third-party system by calling the standard interface of the interface integration platform through the external system to verify the effectiveness of the interface integration platform.
[0013] Specifically, in step S1, configuring the external standard interface includes: defining keywords, names, input parameters and output parameters of the external standard interface.
[0014] Specifically, in step S2, the method for configuring the integrated system is: binding the system number and system name of the third-party system with the external standard interface in step S1, and the third-party system provides a unified external standard interface to the outside.
[0015] Specifically, in step S3, the method for configuring the field mapping between the third-party system and the interface integration platform is:
[0016] Define the mapping between the input parameters of the external standard interface and the input parameters of the third-party system;
[0017] Define the mapping between the outgoing parameters of the external standard interface and the outgoing parameters of the third-party system;
[0018] The fields of the mapping include:
[0019] The name and interface service address of the third-party system;
[0020] The name of the external standard interface, interface address, method name, interface type, input parameter type, authorization parameters, authorized IP, and interface request type.
[0021] Specifically, step S4 includes:
[0022] S41, obtaining standard input parameters of the external system through the external standard interface;
[0023] S42, converting the input parameters according to the field mapping between the third-party system and the interface integration platform;
[0024] S43, transferring the converted input parameters to a third-party system;
[0025] S44, obtaining the outgoing parameters returned by the third-party system through the external standard interface;
[0026] S45, converting the outgoing parameters according to the field mapping between the third-party system and the interface integration platform;
[0027] S46, returning the converted standard outgoing parameters to the external system.
[0028] Preferably, the interface integration configuration method further comprises the steps of:
[0029] S5, configure interface authorization, create an authorized user, and configure the authorized user's username, authorization key, and a list of callable external standard interfaces.
[0030] According to another aspect of the present invention, a computer-readable storage medium is provided, on which a computer program is stored, and when the program is executed by a processor, the steps of the above-mentioned interface integration configuration method are implemented.
[0031] Compared with the prior art, the beneficial effects of the present invention are as follows: the present invention constructs an interface integration platform by configuring external standard interfaces; configures an integration system to connect a third-party system with the interface integration platform; configures field mapping between the third-party system and the interface integration platform; and connects with the third-party system by calling the standard interface of the interface integration platform through the external system; through the interface integration configuration method of the present invention, it is avoided that the third-party system separately provides the relevant interface calling permissions to the external system, while reducing inefficient and repetitive interface connection work, and facilitating unified interface management. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] Figure 1 The present invention is a flowchart of a method for configuring a data interface integration that is convenient for docking with an external system.
[0033] Figure 2 The present invention is a flowchart showing a method for verifying an interface integration platform according to an embodiment of the present invention.
[0034] Figure 3 Schematic diagram of data transmission between the interface integration platform and external systems and third-party systems in an embodiment of the present invention.
[0035] Figure 4 This is a schematic diagram of configuring an external standard interface in an embodiment of the present invention.
[0036] Figure 5 A schematic diagram of configuring field mapping between a third-party system and an interface integration platform in an embodiment of the present invention.
[0037] Figure 6 It is a schematic diagram of the verification result of the interface integration platform in the embodiment of the present invention. DETAILED DESCRIPTION
[0038] The technical solution of the present invention will be described clearly and completely below in conjunction with the accompanying drawings of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0039] According to one aspect of the present invention, Figure 1As shown, this embodiment provides a data interface integration configuration method that is convenient for docking with an external system, including the following steps:
[0040] S1, configure external standard interfaces and build an interface integration platform;
[0041] S2, configure the integration system and connect the third-party system with the interface integration platform;
[0042] S3, configure the field mapping between the third-party system and the interface integration platform;
[0043] S4, verifying the interface integration platform, by calling the standard interface of the interface integration platform through the external system to connect with the third-party system, and verifying the effectiveness of the interface integration platform;
[0044] S5, configure interface authorization, create an authorized user, and configure the authorized user's username, authorization key, and a list of callable external standard interfaces.
[0045] Specifically, Figure 4 As shown, in step S1, configuring the external standard interface includes: defining the keywords, name, input parameters and output parameters of the external standard interface; wherein the input parameters and the output parameters support page configuration, and are finally saved in the database in json format, and support returning List format.
[0046] This embodiment takes a hospital department query as an example, and configures the transmission parameters and output parameters of the external standard interface as follows:
[0047] Pass in parameters:
[0048] {"hospitalId":"Medical institution number","deptCode":"Department number","deptType":"Department type","superiorDeptId":"Superior department number","orgId":"Organization code","orgName":"Organization name","requestType":"Request client type","operatorCode":"Operator number","hospAreaNo":"Hospital area Id","requestId":"Request source Id","operatorName":""}
[0049] Outgoing parameters:
[0050] {"code":"Return status code","msg":"Return description information","data":[{"deptCode":"Department code","deptName":"Department name","nickName":"Department alias","location":"Department location","deptLimit":"Department limit","deptDesc":"Department introduction","superiorDeptId":"Superior department Id","deptLevel":"Department level","deptFlag":"Department flag","hospitalId":"Medical institution number","hospAreaNo":"Hospital area Id","updateBy":"Modifier","updateDate":"Modification time"}]}
[0051] Specifically, in step S2, the method for configuring the integrated system is: binding the system number and system name of the third-party system with the external standard interface in step S1, and the third-party system provides a unified external standard interface to the outside.
[0052] Specifically, Figure 5 As shown, in step S3, the method for configuring the field mapping between the third-party system and the interface integration platform is:
[0053] Define the mapping between the input parameters of the external standard interface and the input parameters of the third-party system;
[0054] Define the mapping between the outgoing parameters of the external standard interface and the outgoing parameters of the third-party system;
[0055] The fields of the mapping include:
[0056] The name and interface service address of the third-party system;
[0057] The name of the external standard interface, interface address, method name, interface type, input parameter type, authorization parameters, authorized IP, and interface request type.
[0058] In this embodiment, the interface type supports two types: http and webservice; the input parameter supports three types: xml, json and string; the interface request type supports two types: get and post.
[0059] Specifically, Figure 2 As shown, step S4 specifically includes:
[0060] S41, obtaining standard input parameters of the external system through the external standard interface;
[0061] S42, converting the input parameters according to the field mapping between the third-party system and the interface integration platform;
[0062] S43, transferring the converted input parameters to a third-party system;
[0063] S44, obtaining the outgoing parameters returned by the third-party system through the external standard interface;
[0064] S45, converting the outgoing parameters according to the field mapping between the third-party system and the interface integration platform;
[0065] S46, returning the converted standard outgoing parameters to the external system.
[0066] Verification results are as follows Figure 6 As shown, according to the input standard incoming parameters (interface code inHospRechargeRecord, hospital number HOSPT021 and system number HIS), the outgoing parameters returned by the third-party system are no results yet, that is, no hospitalization prepayment recharge record was found according to the above-mentioned incoming parameters.
[0067] In this embodiment, the data transmission between the interface integration platform and the external system and the third-party system is as follows: Figure 3 As shown; the external system includes a client system, a workstation or a portable computer, etc.; the interface integration platform is used to provide a unified payment interface and a unified product list interface; the third-party system includes system A (the interface is a webservice that provides a payment interface), system B (the interface is an http-get method that provides a payment interface) and system C (the interface is an http-post method that provides a product list interface).
[0068] The method by which the interface integration platform of this embodiment provides a unified external standard interface for an external system is as follows: the external system inputs standard input parameters to the interface integration platform, and the interface integration platform calls the relevant interface of the third-party system based on the field mapping between the third-party system, converts the standard input parameters into input parameters that match the relevant interface of the third-party system and inputs them into the third-party system; the third-party system returns output parameters based on the input input parameters, and the interface integration platform converts the output parameters returned by the third-party system into standard output parameters that match the external system interface based on the field mapping between the third-party system and the third-party system, and returns the standard output parameters to the external system.
[0069] According to another aspect of the present specification, this embodiment provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of the above-mentioned interface integration configuration method are implemented.
[0070] Those skilled in the art should understand that many improvements in method flows can now be regarded as direct improvements in hardware circuit structures. In general, technicians obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit, that is, the improvement of the method flow can be implemented with a hardware entity module. For example, the logic function of integrated circuits such as programmable logic devices PLDs and field programmable gate arrays FPGAs is determined by the user programming the device. A digital system is integrated on a PLD by the technician himself programming without the need to design and manufacture a special integrated circuit chip. Those skilled in the art should also understand that the method flow can be logically programmed through a hardware description language and programmed into an integrated circuit to implement the hardware circuit of the logical method flow.
[0071] According to one aspect of the present invention, a computer-readable storage medium is provided, on which a computer program is stored, and when the program is executed by a processor, the steps of the method are implemented.
[0072] The processor may be implemented in any suitable manner. For example, the processor may take the form of, for example, a microprocessor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the microprocessor, logic gates, switches, application specific integrated circuits, programmable logic controllers, and embedded microcontrollers. The memory controller may also be implemented as part of the control logic of the memory.
[0073] Those skilled in the art also know that, in addition to implementing the processor in a purely computer-readable program code, the method steps can be logically programmed to enable the processor to implement the same function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a processor can be considered as a hardware component, and the devices for implementing various functions included therein can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules for implementing the method and structures within the hardware component.
[0074] The platform, system, terminal, module or unit described in the above embodiments may be implemented by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
[0075] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented 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.
[0076] The present invention is described with reference to flowcharts and / or block diagrams of methods, platforms (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0077] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.
[0078] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0079] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1In a typical configuration, a computer includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0080] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.
[0081] Computer readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0082] In the description of this specification, the description with reference to the terms "one embodiment", "certain embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.
[0083] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the technical solutions of the embodiments of the present invention.
Claims
1. A data interface integration configuration method for facilitating connection with an external system, characterized in that: The following steps are involved: S1, configure external standard interfaces and build an interface integration platform; Configuring the external standard interface includes: defining the keywords, names, incoming parameters and outgoing parameters of the external standard interface; S2, configure the integration system and connect the third-party system with the interface integration platform; The method for configuring the integrated system is: binding the system number and system name of the third-party system with the external standard interface in step S1, so that the third-party system provides a unified external standard interface to the outside world; S3, configure the field mapping between the third-party system and the interface integration platform; The method for configuring the field mapping between the third-party system and the interface integration platform is: Define the mapping between the input parameters of the external standard interface and the input parameters of the third-party system; Define the mapping between the outgoing parameters of the external standard interface and the outgoing parameters of the third-party system; The mapped fields include: the name and interface service address of the third-party system; the name, interface address, method name, interface type, input parameter type, authorization parameter, authorization IP and interface request type of the external standard interface; S4, verifying the interface integration platform, by calling the standard interface of the interface integration platform through the external system to connect with the third-party system, and verifying the effectiveness of the interface integration platform; S41, obtaining standard input parameters of the external system through the external standard interface; S42, converting the input parameters according to the field mapping between the third-party system and the interface integration platform; S43, transferring the converted input parameters to a third-party system; S44, obtaining outgoing parameters returned by the third-party system through an external standard interface; S45, converting the outgoing parameters according to the field mapping between the third-party system and the interface integration platform; S46, returning the converted standard outgoing parameters to the external system.
2. A data interface integrated configuration method for facilitating docking with an external system according to claim 1, characterized in that: Also includes the steps: S5, configure interface authorization, create an authorized user, and configure the authorized user's username, authorization key, and a list of callable external standard interfaces.
3. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the method according to any one of claims 1 to 2 are implemented.
