CN112511591A - Method, device, equipment and medium for realizing hospital interface data interaction - Google Patents
Method, device, equipment and medium for realizing hospital interface data interaction Download PDFInfo
- Publication number
- CN112511591A CN112511591A CN202011194050.XA CN202011194050A CN112511591A CN 112511591 A CN112511591 A CN 112511591A CN 202011194050 A CN202011194050 A CN 202011194050A CN 112511591 A CN112511591 A CN 112511591A
- Authority
- CN
- China
- Prior art keywords
- service
- message
- dictionary
- interface
- conversion
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 153
- 230000003993 interaction Effects 0.000 title claims abstract description 21
- 238000006243 chemical reaction Methods 0.000 claims abstract description 135
- 238000013507 mapping Methods 0.000 claims abstract description 37
- 230000008569 process Effects 0.000 claims abstract description 21
- 230000010354 integration Effects 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 15
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 24
- 230000006870 function Effects 0.000 description 6
- 238000011161 development Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 238000009517 secondary packaging Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005538 encapsulation Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000007418 data mining Methods 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000005065 mining Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- 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
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/70—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for mining of medical data, e.g. analysing previous cases of other patients
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
Abstract
The invention provides a method, a device, equipment and a medium for hospital interface data interaction, wherein the method comprises a configuration process and a data conversion process, and the configuration process comprises the following steps: configuring an endpoint, proxy service and data conversion; the data conversion process comprises: when a request message of the proxy service of a service system is received, firstly analyzing a head parameter of the request message, and acquiring configuration information related to the requested proxy service and corresponding endpoint information; performing dictionary conversion on the request message according to configuration information related to the proxy service; and returning the message dictionary conversion result according to the corresponding endpoint information. According to the invention, each method of the interface is divided into the proxy services, then dictionary conversion configuration is carried out on each proxy service, and mapping of the service dictionary of the original data in the service system and the national standard dictionary is utilized, so that data interaction of the hospital cross-service system is realized, dynamic configuration is supported, the application scene is flexible, and the efficiency is high.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method, a device, equipment and a medium for realizing hospital interface data interaction.
Background
With the increasing popularization of big data technology and application, the mining of hospital information system data becomes an important foundation for medical technology improvement and national health construction.
For the data mining of hospital information systems, the most important point is that the data from each information system of the hospital has a uniform data standard. For the existing hospital information systems, due to different reasons and business requirements of developers, each information system is often provided with a specific data dictionary, and mutual recognition of business data among the hospital information systems is another difficulty.
At present, the data mutual-recognition solving mode in the market is mainly to realize data conversion between systems through dictionary mapping of each hospital information system, and the solution only solves the problem of data intercommunication between two parties needing data conversion at present. Taking the data interface as an example, when the dictionary data of the interface provider is changed, the dictionary mapping transformation is required to be performed by the interface receiver, so that the informatization cost of the hospital is increased, and extra workload is generated.
At present, the country provides an electronic medical record basic data set aiming at a national hospital information platform, and the data in the electronic medical record basic data set provides definition of standard data elements, wherein the definition of the standard data elements covers types, dictionaries, lengths and the like of the data elements. By means of a data set of national standards, when all service systems in the hospital information system provide interfaces, data are subjected to dictionary mapping facing to a national standard dictionary, so that the problem of service system data standardization can be solved, and meanwhile, data mutual recognition of the hospital-crossing information system can be realized according to secondary conversion of the dictionary (for example, data of an A service system is converted into standard data, and then the standard data is converted into data of a B service system).
At present, data conversion between service systems has two modes, one is to directly convert in a database, that is, periodically collect data in a service system database for conversion, so that the real-time performance is not high. The other method is to perform real-time conversion in an interface message mode, but one interface address supports a plurality of interface methods exposed to the outside, and for different interface methods, the content of the requested interface message is different, so the interface method needs to be split, the current splitting method writes all service codes in all the interface methods, each service corresponds to one set of codes, and the codes in the conversion process are also written, when the service changes the dictionary of the relevant service system, the codes need to be modified and re-distributed, which results in huge workload and is not beneficial to the improvement of efficiency.
Disclosure of Invention
The technical problem to be solved by the invention is to provide a method, a device, equipment and a medium for realizing hospital interface data interaction, each method of an interface is divided into proxy services, then dictionary conversion configuration is carried out on each proxy service, and mapping of a service dictionary of original data in a service system and a national standard dictionary is utilized, so that data interaction of a hospital cross-service system is realized, dynamic configuration is supported, application scenes are flexible, and efficiency is high.
In a first aspect, the invention provides a method for realizing hospital interface data interaction, which is used for an agent service integration platform and comprises a configuration process and a data conversion process;
the configuration process comprises:
s11, configuring the end point information including interface address, name space, attribution system and whether needing standard conversion;
s12, proxy service configuration for configuring proxy service information including home interface, method name, whether standardized conversion and method parameter are needed;
s13, data conversion configuration, which is used for configuring mapping configuration information of the service system dictionary and the standard dictionary of both data conversion parties and binding configuration information of the request message and the return message node data and the dictionary;
the data conversion process comprises:
s21, when a request message of the proxy service of a service system is received, the request message of the proxy service is a proxy service message, the header parameter of the request message is firstly analyzed, the requested proxy service information, the mapping configuration information of the dictionary and the standard dictionary of the service system of both data conversion parties and the binding configuration information of the request message and the return message node data and the dictionary, and the corresponding endpoint information are inquired and obtained according to the header parameter;
s22, according to the proxy service information, mapping configuration information of the service system dictionaries of both data conversion parties and the standard dictionary and binding configuration information of the node data of the request message and the returned message and the dictionary, performing dictionary conversion on the request message;
and S23, returning the message dictionary conversion result according to the corresponding endpoint information.
In a second aspect, the present invention provides a device for implementing data interaction of hospital interfaces, which is disposed on an agent service integration platform, and includes:
the endpoint configuration module is used for configuring endpoint information, including interface addresses, namespaces, attribution systems and whether standardized conversion is needed or not;
the proxy service configuration module is used for configuring proxy service information, including an attribution interface, a method name, whether standardized conversion and method parameters are needed or not for packaging a specific interface service method;
the data conversion configuration module is used for configuring mapping configuration information of the dictionaries of the business systems of the data conversion parties and the standard dictionary and binding configuration information of node data of the request message and the return message and the dictionaries;
a data converter: the data conversion method comprises the steps that when a request message of proxy service of a service system is received, wherein the request message of the proxy service is a proxy service message, a head parameter of the request message is analyzed, the requested proxy service information is inquired and obtained according to the head parameter, mapping configuration information of a dictionary and a standard dictionary of the service system of both data conversion sides, binding configuration information of node data and the dictionary of the request message and a return message, and corresponding endpoint information are obtained; performing dictionary conversion on the request message according to the proxy service information, mapping configuration information of a dictionary and a standard dictionary of the business system of both data conversion parties and binding configuration information of the node data and the dictionary of the request message and the return message; and returning the message dictionary conversion result according to the corresponding endpoint information.
In a third aspect, the present invention provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of the first aspect when executing the program.
In a fourth aspect, the invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the method of the first aspect.
The dictionary conversion of the interface message is essentially the conversion of the node content of the message of the interface, and the content of the request message is different for different interface methods, so that the invention splits and secondarily encapsulates each service method of the interface into the proxy service, and then performs the configuration of two layers for each proxy service and the dictionary conversion thereof, thereby having at least the following technical effects or advantages:
(1) the real-time conversion is carried out in an interface message mode, the real-time performance of data conversion is met, meanwhile, the specific certain interface service method is configured and packaged through the configuration agent service information, the split configuration of all the interface service methods in the interface is realized, the application of various interface service scenes can be met, a set of codes does not need to be written for each interface service method, and the workload is reduced;
(2) through the end point configuration and the data conversion configuration, the message conversion configuration and the realization of different request systems are supported for the same interface service method;
(3) the conversion of the node content of the interface message dictionary is realized by utilizing the binding mode of the node of the interface message and the dictionary in the data conversion configuration; and when the dictionaries of any party in the business systems of the two parties of data conversion change or need to be integrally replaced, the data conversion is realized only through dynamic configuration without modifying codes, and the workload is reduced.
(4) The proxy service is used for carrying out secondary packaging on the original interface message into a proxy service message with a standard fixed format, so that the standardization of the original service interface service is realized, and the development cost and time of the interface standardization are reduced.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
The invention will be further described with reference to the following examples with reference to the accompanying drawings.
FIG. 1 is a schematic diagram of a system framework in use of the present invention;
FIG. 2 is a flow chart of a method according to one embodiment of the present invention;
FIGS. 3 and 4 are schematic diagrams of an example of an endpoint (interface) configuration interface according to the present invention;
FIG. 5 is a schematic diagram of an example proxy service configuration interface according to the present invention;
FIG. 6 is a schematic diagram of an example of a proxy service packet node configuration interface according to the present invention;
FIG. 7 is a schematic diagram of an example of a selective agent service and request system configuration interface according to the present invention;
FIG. 8 is a diagram illustrating an example node dictionary configuration interface in accordance with the present invention;
FIG. 9 is a diagram illustrating an example of a message node configuration interface of the endpoint method of the present invention
FIG. 10 is a diagram illustrating an example of a dictionary binding configuration interface for selecting a corresponding endpoint method, requesting the endpoint method, and returning a message according to the present invention
FIG. 11 is a diagram illustrating an example of a mapping configuration interface between a service dictionary and a standard dictionary of each system according to the present invention
FIG. 12 is a diagram illustrating an example of a proxy service message according to the present invention;
FIG. 13 is a diagram illustrating a process of secondary packaging of original interface messages for the integrated proxy service platform according to the present invention
FIG. 14 is a diagram illustrating an example of an original request message according to the present invention;
FIG. 15 is a diagram illustrating an example of an interface for splitting a service method of an original interface and performing service agent configuration according to the present invention;
FIG. 16 is a schematic structural diagram of an apparatus according to a second embodiment of the present invention;
fig. 17 is a schematic structural diagram of an electronic device according to a third embodiment of the invention;
FIG. 18 is a schematic structural diagram of a medium according to a fourth embodiment of the present invention;
FIG. 19 is a flowchart illustrating the overall conversion process of a message dictionary between two service systems according to the present invention.
Detailed Description
The embodiment of the application provides a method, a device, equipment and a medium for realizing data interaction of a hospital interface, and the method, the device, the equipment and the medium realize data interaction of a hospital cross-service system by splitting each method of the interface into proxy services, then performing dictionary conversion configuration on each proxy service and utilizing mapping between a service dictionary of original data in a service system and a national standard dictionary, and support dynamic configuration, and have flexible application scenes and high efficiency.
The technical scheme in the embodiment of the application has the following general idea: the real-time conversion is still carried out in an interface message mode, each method of the interface is divided into proxy services, the proxy services can be configured, then dictionary conversion configuration is carried out on each proxy service, configuration of two layers is achieved, a set of codes do not need to be written for each interface service method, and when the dictionary of any party in the business systems of the two data conversion parties changes or needs to be replaced integrally, the dynamic configuration is achieved without modifying the codes, and the workload is reduced. For the same interface service method, the message conversion configuration and realization of different request systems are supported; for the message, the proxy service is used for carrying out secondary packaging on the original interface message into the proxy service message with the standard fixed format, so that the standardization of the original service interface service is realized, and the development cost and time of the interface standardization are reduced.
Before describing the specific embodiment, a use scenario of each embodiment of the present invention is described, as shown in fig. 1, each embodiment of the present invention is applied to an agent service integration platform, and when two business systems (which may belong to one hospital or different hospitals) need to perform data interaction, an agent service of the agent service integration platform may be requested, and the agent service integration platform completes a business dictionary conversion operation of the two business systems.
Example one
As shown in fig. 2, the embodiment provides an implementation method of hospital interface data interaction, which is used for a proxy service integration platform and includes a configuration process and a data conversion process;
the configuration process comprises:
s11, configuring the end point information including interface address, name space, attribution system and whether needing standard conversion;
as shown in fig. 3 and fig. 4, the interface address (i.e. the interface address to which the interface service method belongs), the endpoint namespace (i.e. the namespace parameter of the endpoint), whether the parameter contains the namespace (i.e. whether the parameter needs the namespace parameter of the endpoint as the prefix of the parameter node), the home system (the service system to which the endpoint belongs), whether the request is made to be a service (i.e. whether the request message is to be converted into the dictionary of the service to which the endpoint belongs), whether the return is standardized (i.e. whether the return message is to be converted into the standard dictionary), the node where the request message dictionary conversion is located, the node where the return message dictionary conversion is.
S12, proxy service configuration for configuring proxy service information including home interface, method name, whether standardized conversion and method parameter are needed;
as shown in fig. 5, the proxy service transaction code mainly includes a proxy service capability name (i.e., a service function name), whether to enable a service (i.e., whether to open a service), whether to standardize a request packet (i.e., whether to convert the request packet into a standardized packet), whether to convert a return packet into a service (whether to convert a packet returned to a request end into a dictionary of a request system), an interface method name corresponding to the proxy service, a bound end point, and a proxy service transaction code (a proxy service identification parameter in the request packet) generated after encapsulation.
S13, data conversion configuration, which is used for configuring mapping configuration information of the service system dictionary and the standard dictionary of both data conversion parties and binding configuration information of the request message and the return message node data and the dictionary; as a more preferred or specific implementation manner of this embodiment, the data conversion configuration further includes:
(1) proxy service message node service dictionary binding configuration, which is used for configuring service dictionary binding information of proxy service message nodes and comprises the steps of configuring a request message for proxy service and binding a dictionary of a corresponding request system by a node needing conversion in a return message;
during configuration, a request message node of the proxy service is configured, then a corresponding request system is selected, and then a dictionary of the corresponding system is bound for a node which needs to be converted in the message, wherein the node of the proxy service is configured as shown in fig. 6, the node of the proxy service and the request system is selected as shown in fig. 7, and the node dictionary is configured as shown in fig. 8.
(2) The binding configuration of the endpoint original interface message node service dictionary is used for configuring the service dictionary binding information of the endpoint original interface message node, and comprises the steps of configuring an original request for an endpoint and returning a dictionary of a node binding corresponding to a request system needing to be converted in the message;
as shown in fig. 9, a message node configuring an endpoint method selects a corresponding endpoint method, requests the endpoint method, and binds a dictionary of a returned message, as shown in fig. 10.
(3) Mapping configuration of each service system dictionary and the standard dictionary is used for configuring mapping relationship between the dictionary of each service system and the standard dictionary, and the configuration interface is shown in fig. 11.
As shown in fig. 2, the data conversion process includes:
s21, when a request message of the proxy service of a service system is received, the request message of the proxy service is a proxy service message, the header parameter of the request message is firstly analyzed, the requested proxy service information, the mapping configuration information of the dictionary and the standard dictionary of the service system of both data conversion parties and the binding configuration information of the request message and the return message node data and the dictionary, and the corresponding endpoint information are inquired and obtained according to the header parameter;
s22, according to the proxy service information, mapping configuration information of the service system dictionaries of both data conversion parties and the standard dictionary and binding configuration information of the node data of the request message and the returned message and the dictionary, performing dictionary conversion on the request message;
and S23, returning the message dictionary conversion result according to the corresponding endpoint information.
According to the method and the device, the proxy service is utilized to secondarily package the original interface message into the proxy service message with the standard fixed format, so that the standardization of the original service interface service is realized, and the development cost and time of the interface standardization are reduced. As shown in fig. 12, the proxy service packet has the following unified format:
the unified request address is positioned in an address bar of the request message and represents an interface address of the proxy service integration platform; because the request addresses are unified, no matter which service system sends the request to the interface of which service system, the requesting party only needs to request the unified address, thereby realizing standardization;
the unified method name is positioned at the method node of the request message, is determined by the interface definition of the proxy service and represents the name of the home interface method of the requested interface service method; the unified method name can ensure that an access party does not need to develop a set of codes aiming at different methods as a plurality of interfaces need to be docked when the original centralized management is not available;
the request system code is positioned at the head of the request message and represents the code of the service system sending the request message;
the service method transaction code is positioned at the head of the request message and represents the proxy service identification parameter of the current proxy service;
the request system identity code is positioned at the head of the request message and represents the authentication basis of the request system;
and the service parameter is positioned in the main body part of the request message and represents the service parameter of the requested interface service method. The dictionary conversion of the interface message is essentially the conversion of node contents of the message of the interface, and the contents of the request message are different for different interface methods, so that more interface service methods are subdivided by the service parameters in the interface methods.
As shown in fig. 13, when receiving a proxy service packet of a first service system as a requester, the proxy service integration platform performs standard dictionary conversion on node data of the proxy service packet, forms an original interface packet, and sends the original interface packet to a second service system as a receiver, and when the second service system returns the original interface packet, performs standard dictionary conversion on the node data of the returned original interface packet, forms a proxy service packet, and returns the proxy service packet to the first service system. As shown in fig. 14, the interface address of the original interface message requests the system to request the interface service methods of different systems, which often requires accessing different interface addresses and interface methods, and splicing different service method parameters, so that the caller may pay attention to the configuration of multiple parameters. After the service method of the original interface is split and the service agent is configured, as shown in fig. 15, only the transaction code and the service parameter of the corresponding service method need to be entered.
Based on the same inventive concept, the application also provides a device corresponding to the method in the first embodiment, which is detailed in the second embodiment.
Example two
As shown in fig. 16, in this embodiment, an apparatus for implementing data interaction of a hospital interface is provided, and is disposed on an agent service integration platform, and includes:
the endpoint configuration module is used for configuring endpoint information, including interface addresses, namespaces, attribution systems and whether standardized conversion is needed or not;
as shown in fig. 3 and fig. 4, the interface address (i.e. the interface address to which the interface service method belongs), the endpoint namespace (i.e. the namespace parameter of the endpoint), whether the parameter contains the namespace (i.e. whether the parameter needs the namespace parameter of the endpoint as the prefix of the parameter node), the home system (the service system to which the endpoint belongs), whether the request is made to be a service (i.e. whether the request message is to be converted into the dictionary of the service to which the endpoint belongs), whether the return is standardized (i.e. whether the return message is to be converted into the standard dictionary), the node where the request message dictionary conversion is located, the node where the return message dictionary conversion is.
The proxy service configuration module is used for configuring proxy service information, including an attribution interface, a method name, whether standardized conversion and method parameters are needed or not for packaging a specific interface service method;
as shown in fig. 5, the proxy service transaction code mainly includes a proxy service capability name (i.e., a service function name), whether to enable a service (i.e., whether to open a service), whether to standardize a request packet (i.e., whether to convert the request packet into a standardized packet), whether to convert a return packet into a service (whether to convert a packet returned to a request end into a dictionary of a request system), an interface method name corresponding to the proxy service, a bound end point, and a proxy service transaction code (a proxy service identification parameter in the request packet) generated after encapsulation.
The data conversion configuration module is used for configuring mapping configuration information of the dictionaries of the business systems of the data conversion parties and the standard dictionary and binding configuration information of node data of the request message and the return message and the dictionaries; the data conversion configuration module further comprises:
(1) the proxy service message node service dictionary binding configuration module is used for configuring service dictionary binding information of proxy service message nodes, and comprises a request message for proxy service and a dictionary binding corresponding to a request system by a node needing conversion in a return message;
during configuration, a request message node of the proxy service is configured, then a corresponding request system is selected, and then a dictionary of the corresponding system is bound for a node which needs to be converted in the message, wherein the node of the proxy service is configured as shown in fig. 6, the node of the proxy service and the request system is selected as shown in fig. 7, and the node dictionary is configured as shown in fig. 8.
(2) The system comprises an endpoint original interface message node service dictionary binding configuration module, a service dictionary binding configuration module and a service dictionary binding configuration module, wherein the service dictionary binding configuration module is used for configuring service dictionary binding information of an endpoint original interface message node, and comprises the steps of configuring an original request for an endpoint and binding a dictionary of a corresponding request system by a node needing to be converted in a return message;
as shown in fig. 9, a message node configuring an endpoint method selects a corresponding endpoint method, requests the endpoint method, and binds a dictionary of a returned message, as shown in fig. 10.
(3) And a mapping configuration module for each service system dictionary and standard dictionary, configured to configure mapping relationships between the dictionaries of each service system and the standard dictionaries, where a configuration interface is shown in fig. 11.
A data converter: the data conversion method comprises the steps that when a request message of proxy service of a service system is received, wherein the request message of the proxy service is a proxy service message, a head parameter of the request message is analyzed, the requested proxy service information is inquired and obtained according to the head parameter, mapping configuration information of a dictionary and a standard dictionary of the service system of both data conversion sides, binding configuration information of node data and the dictionary of the request message and a return message, and corresponding endpoint information are obtained; performing dictionary conversion on the request message according to the proxy service information, mapping configuration information of a dictionary and a standard dictionary of the business system of both data conversion parties and binding configuration information of the node data and the dictionary of the request message and the return message; and returning the message dictionary conversion result according to the corresponding endpoint information. The data converter is implemented by the following steps:
a. judging whether the request message and the return message need to carry out dictionary conversion or not;
b. if conversion is needed, whether the request message and the return message are standardized or business is judged.
c. If the conversion node is standardized, the corresponding conversion configuration and the service dictionary bound by each conversion node are found according to the request or the returned service system and the proxy service or the port method. And finding out corresponding dictionary mapping according to the service dictionary, and then converting the content of the current conversion node into a standard dictionary value through mapping.
d. If the service is the business, finding out the corresponding conversion configuration and the service dictionary bound by each conversion node according to the requested or returned service system and the proxy service or the port method. And finding out corresponding dictionary mapping according to the service dictionary, and then converting the content of the current conversion node into a dictionary value of the service dictionary through mapping.
According to the method and the device, the proxy service is utilized to secondarily package the original interface message into the proxy service message with the standard fixed format, so that the standardization of the original service interface service is realized, and the development cost and time of the interface standardization are reduced. As shown in fig. 12, the proxy service packet has the following unified format:
the unified request address is positioned in an address bar of the request message and represents an interface address of the proxy service integration platform; because the request addresses are unified, no matter which service system sends the request to the interface of which service system, the requesting party only needs to request the unified address, thereby realizing standardization;
the unified method name is positioned at the method node of the request message, is determined by the interface definition of the proxy service and represents the name of the home interface method of the requested interface service method; the unified method name can ensure that the access party does not need to develop a set of codes aiming at different methods as a plurality of interfaces need to be docked when the original centralized management is not available.
The request system code is positioned at the head of the request message and represents the code of the service system sending the request message;
the service method transaction code is positioned at the head of the request message and represents the proxy service identification parameter of the current proxy service;
the request system identity code is positioned at the head of the request message and represents the authentication basis of the request system;
and the service parameter is positioned in the main body part of the request message and represents the service parameter of the requested interface service method. The dictionary conversion of the interface message is essentially the conversion of node contents of the message of the interface, and the contents of the request message are different for different interface methods, so that more interface service methods are subdivided by the service parameters in the interface methods.
As shown in fig. 13, when receiving a proxy service packet of a first service system as a requester, the proxy service integration platform performs standard dictionary conversion on node data of the proxy service packet, forms an original interface packet, and sends the original interface packet to a second service system as a receiver, and when the second service system returns the original interface packet, performs standard dictionary conversion on the node data of the returned original interface packet, forms a proxy service packet, and returns the proxy service packet to the first service system. As shown in fig. 14, the interface address of the original interface message requests the system to request the interface service methods of different systems, which often requires accessing different interface addresses and interface methods, and splicing different service method parameters, so that the caller may pay attention to the configuration of multiple parameters. After the service method of the original interface is split and the service agent is configured, as shown in fig. 15, only the transaction code and the service parameter of the corresponding service method need to be entered.
Since the apparatus described in the second embodiment of the present invention is an apparatus used for implementing the method of the first embodiment of the present invention, based on the method described in the first embodiment of the present invention, a person skilled in the art can understand the specific structure and the deformation of the apparatus, and thus the details are not described herein. All the devices adopted in the method of the first embodiment of the present invention belong to the protection scope of the present invention.
Based on the same inventive concept, the application provides an electronic device embodiment corresponding to the first embodiment, which is detailed in the third embodiment.
EXAMPLE III
The present embodiment provides an electronic device, as shown in fig. 17, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, any one of the first embodiment modes may be implemented.
Since the electronic device described in this embodiment is a device used for implementing the method in the first embodiment of the present application, based on the method described in the first embodiment of the present application, a specific implementation of the electronic device in this embodiment and various variations thereof can be understood by those skilled in the art, and therefore, how to implement the method in the first embodiment of the present application by the electronic device is not described in detail herein. The equipment used by those skilled in the art to implement the methods in the embodiments of the present application is within the scope of the present application.
Based on the same inventive concept, the application provides a storage medium corresponding to the fourth embodiment, which is described in detail in the fourth embodiment.
Example four
The present embodiment provides a computer-readable storage medium, as shown in fig. 18, on which a computer program is stored, and when the computer program is executed by a processor, any one of the first embodiment can be implemented.
Finally, referring to fig. 1 and fig. 19, taking the data of the service system a requesting the service system B as an example, the message dictionary conversion process is as follows:
when the service system A sends a request message to the agent service integration platform, the agent service of the agent service integration platform can be requested;
the agent service integration platform analyzes the request message, routes the request message to the requested service and acquires a request source system, namely a service system A;
according to the service, obtaining message conversion configuration of the service, judging whether standard conversion is needed, if so, converting the request message, converting a dictionary of a service system A in the message into a standard dictionary, and if not, keeping the original request message; then acquiring an end point of an actual request according to the request service;
judging whether the service conversion is needed, if so, converting the request message into a dictionary of a system to which the end point belongs, namely a service system B, and if not, keeping the original request message; requesting the end point again and returning a response message;
judging whether the returned message is standardized, if so, converting the dictionary of the system to which the end point belongs, namely the service system B, in the message into a standard dictionary for returning, and if not, protecting the original returned message for returning;
judging whether the returned message needs service conversion, if so, converting the request message into a request system, namely a dictionary of the service system A, and if not, keeping the current returned message; and returning the response message to finish.
The technical scheme provided in the embodiment of the application at least has the following technical effects or advantages:
(1) the real-time conversion is carried out in an interface message mode, the real-time performance of data conversion is met, meanwhile, the specific certain interface service method is configured and packaged through the configuration agent service information, the split configuration of all the interface service methods in the interface is realized, the application of various interface service scenes can be met, a set of codes does not need to be written for each interface service method, and the workload is reduced;
(2) through the end point configuration and the data conversion configuration, the message conversion configuration and the realization of different request systems are supported for the same interface service method;
(3) the conversion of the node content of the interface message dictionary is realized by utilizing the binding mode of the node of the interface message and the dictionary in the data conversion configuration; and when the dictionaries of any party in the business systems of the two parties of data conversion change or need to be integrally replaced, the data conversion is realized only through dynamic configuration without modifying codes, and the workload is reduced.
(4) The proxy service is used for carrying out secondary packaging on the original interface message into a proxy service message with a standard fixed format, so that the standardization of the original service interface service is realized, and the development cost and time of the interface standardization are reduced.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus or system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Although specific embodiments of the invention have been described above, it will be understood by those skilled in the art that the specific embodiments described are illustrative only and are not limiting upon the scope of the invention, and that equivalent modifications and variations can be made by those skilled in the art without departing from the spirit of the invention, which is to be limited only by the appended claims.
Claims (10)
1. A method for realizing hospital interface data interaction is characterized in that: the proxy service integration platform comprises a configuration process and a data conversion process;
the configuration process comprises:
s11, configuring the end point information including interface address, name space, attribution system and whether needing standard conversion;
s12, proxy service configuration for configuring proxy service information including home interface, method name, whether standardized conversion and method parameter are needed;
s13, data conversion configuration, which is used for configuring mapping configuration information of the service system dictionary and the standard dictionary of both data conversion parties and binding configuration information of the request message and the return message node data and the dictionary;
the data conversion process comprises:
s21, when a request message of the proxy service of a service system is received, the request message of the proxy service is a proxy service message, the header parameter of the request message is firstly analyzed, the requested proxy service information, the mapping configuration information of the dictionary and the standard dictionary of the service system of both data conversion parties and the binding configuration information of the request message and the return message node data and the dictionary, and the corresponding endpoint information are inquired and obtained according to the header parameter;
s22, according to the proxy service information, mapping configuration information of the service system dictionaries of both data conversion parties and the standard dictionary and binding configuration information of the node data of the request message and the returned message and the dictionary, performing dictionary conversion on the request message;
and S23, returning the message dictionary conversion result according to the corresponding endpoint information.
2. The method for realizing hospital interface data interaction according to claim 1, wherein: the data conversion arrangement further comprises:
proxy service message node service dictionary binding configuration, which is used for configuring service dictionary binding information of proxy service message nodes and comprises the steps of configuring a request message for proxy service and binding a dictionary of a corresponding request system by a node needing conversion in a return message;
the binding configuration of the endpoint original interface message node service dictionary is used for configuring the service dictionary binding information of the endpoint original interface message node, and comprises the steps of configuring an original request for an endpoint and returning a dictionary of a node binding corresponding to a request system needing to be converted in the message;
and mapping and configuring the dictionary of each service system and the standard dictionary, and configuring the mapping relation between the dictionary of each service system and the standard dictionary.
3. The method for realizing hospital interface data interaction according to claim 1, wherein: the proxy service message has the following unified format:
the unified request address is positioned in an address bar of the request message and represents an interface address of the proxy service integration platform;
the unified method name is positioned at the method node of the request message, is determined by the interface definition of the proxy service and represents the name of the home interface method of the requested interface service method;
the request system code is positioned at the head of the request message and represents the code of the service system sending the request message;
the service method transaction code is positioned at the head of the request message and represents the proxy service identification parameter of the current proxy service;
the request system identity code is positioned at the head of the request message and represents the authentication basis of the request system;
and the service parameter is positioned in the main body part of the request message and represents the service parameter of the requested interface service method.
4. The method of claim 3, wherein the method comprises: when receiving an agent service message of a first service system as a requester, the agent service integration platform performs standard dictionary conversion on node data of the agent service message to form an original interface message and sends the original interface message to a second service system as a receiver, and when the second service system returns the original interface message, performs standard dictionary conversion on the node data of the returned original interface message to form an agent service message and returns the agent service message to the first service system.
5. The utility model provides a realization device of hospital interface data interaction which characterized in that: set up in agent service integration platform, include:
the endpoint configuration module is used for configuring endpoint information, including interface addresses, namespaces, attribution systems and whether standardized conversion is needed or not;
the proxy service configuration module is used for configuring proxy service information, including an attribution interface, a method name, whether standardized conversion and method parameters are needed or not for packaging a specific interface service method;
the data conversion configuration module is used for configuring mapping configuration information of the dictionaries of the business systems of the data conversion parties and the standard dictionary and binding configuration information of node data of the request message and the return message and the dictionaries;
a data converter: the data conversion method comprises the steps that when a request message of proxy service of a service system is received, wherein the request message of the proxy service is a proxy service message, a head parameter of the request message is analyzed, the requested proxy service information is inquired and obtained according to the head parameter, mapping configuration information of a dictionary and a standard dictionary of the service system of both data conversion sides, binding configuration information of node data and the dictionary of the request message and a return message, and corresponding endpoint information are obtained; performing dictionary conversion on the request message according to the proxy service information, mapping configuration information of a dictionary and a standard dictionary of the business system of both data conversion parties and binding configuration information of the node data and the dictionary of the request message and the return message; and returning the message dictionary conversion result according to the corresponding endpoint information.
6. The apparatus for realizing hospital interface data interaction according to claim 5, wherein: the data conversion configuration module further comprises:
the proxy service message node service dictionary binding configuration module is used for configuring service dictionary binding information of proxy service message nodes, and comprises a request message for proxy service and a dictionary binding corresponding to a request system by a node needing conversion in a return message;
the system comprises an endpoint original interface message node service dictionary binding configuration module, a service dictionary binding configuration module and a service dictionary binding configuration module, wherein the service dictionary binding configuration module is used for configuring service dictionary binding information of an endpoint original interface message node, and comprises the steps of configuring an original request for an endpoint and binding a dictionary of a corresponding request system by a node needing to be converted in a return message;
and the mapping configuration module of the dictionary and the standard dictionary of each service system is used for configuring the mapping relation between the dictionary and the standard dictionary of each service system.
7. The apparatus for realizing hospital interface data interaction according to claim 5, wherein: the proxy service message has the following unified format:
the unified request address is positioned in an address bar of the request message and represents an interface address of the proxy service integration platform;
the unified method name is positioned at the method node of the request message, is determined by the interface definition of the proxy service and represents the name of the home interface method of the requested interface service method;
the request system code is positioned at the head of the request message and represents the code of the service system sending the request message;
the service method transaction code is positioned at the head of the request message and represents the proxy service identification parameter of the current proxy service;
the request system identity code is positioned at the head of the request message and represents the authentication basis of the request system;
and the service parameter is positioned in the main body part of the request message and represents the service parameter of the requested interface service method.
8. The apparatus for realizing hospital interface data interaction according to claim 5, wherein: when receiving an agent service message of a first service system as a requester, the agent service integration platform performs standard dictionary conversion on node data of the agent service message to form an original interface message and sends the original interface message to a second service system as a receiver, and when the second service system returns the original interface message, performs standard dictionary conversion on the node data of the returned original interface message to form an agent service message and returns the agent service message to the first service system.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 4 when executing the program.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011194050.XA CN112511591B (en) | 2020-10-30 | 2020-10-30 | Method, device, equipment and medium for realizing hospital interface data interaction |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011194050.XA CN112511591B (en) | 2020-10-30 | 2020-10-30 | Method, device, equipment and medium for realizing hospital interface data interaction |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112511591A true CN112511591A (en) | 2021-03-16 |
| CN112511591B CN112511591B (en) | 2024-04-05 |
Family
ID=74954761
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011194050.XA Active CN112511591B (en) | 2020-10-30 | 2020-10-30 | Method, device, equipment and medium for realizing hospital interface data interaction |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112511591B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113270179A (en) * | 2021-05-25 | 2021-08-17 | 北京金山云网络技术有限公司 | Medical skill examination method, device and system and electronic equipment |
| CN113808723A (en) * | 2021-09-30 | 2021-12-17 | 北京蓝海医信科技有限公司 | Information integration platform of service system |
| CN113849562A (en) * | 2021-09-16 | 2021-12-28 | 支付宝(杭州)信息技术有限公司 | Method and device for accessing external service system |
| CN114281428A (en) * | 2021-12-28 | 2022-04-05 | 挂号网（杭州）科技有限公司 | Configuration method of service dictionary, electronic equipment and storage medium |
| CN117076163A (en) * | 2023-10-17 | 2023-11-17 | 建银工程咨询有限责任公司 | Communication method and system between multiple standard service systems |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020128861A1 (en) * | 2001-01-05 | 2002-09-12 | Lau Lee Min | Mapping clinical data with a health data dictionary |
| CN107766456A (en) * | 2017-09-27 | 2018-03-06 | 山东浪潮通软信息科技有限公司 | Data parsing converting system and method based on file interaction between supplementary pension system |
| CN109460912A (en) * | 2018-10-31 | 2019-03-12 | 泰康保险集团股份有限公司 | Data processing method, device, storage medium and electronic equipment |
| WO2020140679A1 (en) * | 2019-01-03 | 2020-07-09 | 深圳壹账通智能科技有限公司 | Interface docking method and apparatus, computer device and storage medium |
-
2020
- 2020-10-30 CN CN202011194050.XA patent/CN112511591B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020128861A1 (en) * | 2001-01-05 | 2002-09-12 | Lau Lee Min | Mapping clinical data with a health data dictionary |
| CN107766456A (en) * | 2017-09-27 | 2018-03-06 | 山东浪潮通软信息科技有限公司 | Data parsing converting system and method based on file interaction between supplementary pension system |
| CN109460912A (en) * | 2018-10-31 | 2019-03-12 | 泰康保险集团股份有限公司 | Data processing method, device, storage medium and electronic equipment |
| WO2020140679A1 (en) * | 2019-01-03 | 2020-07-09 | 深圳壹账通智能科技有限公司 | Interface docking method and apparatus, computer device and storage medium |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113270179A (en) * | 2021-05-25 | 2021-08-17 | 北京金山云网络技术有限公司 | Medical skill examination method, device and system and electronic equipment |
| CN113849562A (en) * | 2021-09-16 | 2021-12-28 | 支付宝(杭州)信息技术有限公司 | Method and device for accessing external service system |
| CN113808723A (en) * | 2021-09-30 | 2021-12-17 | 北京蓝海医信科技有限公司 | Information integration platform of service system |
| CN113808723B (en) * | 2021-09-30 | 2023-08-22 | 北京蓝海医信科技有限公司 | Service system information integration platform |
| CN114281428A (en) * | 2021-12-28 | 2022-04-05 | 挂号网（杭州）科技有限公司 | Configuration method of service dictionary, electronic equipment and storage medium |
| CN117076163A (en) * | 2023-10-17 | 2023-11-17 | 建银工程咨询有限责任公司 | Communication method and system between multiple standard service systems |
| CN117076163B (en) * | 2023-10-17 | 2024-01-12 | 建银工程咨询有限责任公司 | Communication method and system between multiple standard service systems |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112511591B (en) | 2024-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112511591A (en) | Method, device, equipment and medium for realizing hospital interface data interaction | |
| CN109246251B (en) | Micro-service calling method, device, system, equipment and readable storage medium | |
| KR100845234B1 (en) | Apparatus and method for parsing domain profile in software communication architecture | |
| CN101697139A (en) | Method, device and registry for remote procedure call | |
| CN111698205B (en) | Service calling method and related equipment | |
| CN109062906B (en) | Translation method and device for program language resources | |
| CN113225379A (en) | Method and device for sending HTTP request message | |
| US20090043864A1 (en) | Method and System for Generating Globally Unique Identifiers | |
| US9652309B2 (en) | Mediator with interleaved static and dynamic routing | |
| CN112417016B (en) | Data exchange method, system, equipment and storage medium | |
| CN114040032A (en) | Protocol conversion method, system, storage medium and electronic equipment | |
| CN101719069B (en) | Method and device of Web servitization of Java system | |
| CN112491943A (en) | Data request method, device, storage medium and electronic equipment | |
| CN113709177B (en) | Method for processing message and external call gateway | |
| CN114219643A (en) | Transaction calling method, device, equipment and storage medium | |
| CN113918245A (en) | Data calling method, device, equipment and computer readable storage medium | |
| CN114840718A (en) | Link data processing method, device, equipment, storage medium and program product | |
| CN110555042B (en) | Method, device and system for retrieving data in real time | |
| CN112714148A (en) | Interface configuration method, device, equipment and medium | |
| CN112650502A (en) | Batch processing task processing method and device, computer equipment and storage medium | |
| CN111309319A (en) | Inheritable office data dynamic page configuration method and device | |
| CN114844957B (en) | Link message conversion method, device, equipment, storage medium and program product | |
| CN114499759B (en) | Message generation method and device, electronic equipment and storage medium | |
| CN113285997B (en) | Data processing method, device, medium and product based on heterogeneous system | |
| CN114238466A (en) | Message pushing method and device, computer equipment and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |