A medical insurance standard-oriented unified interface adaptation module

Abstract

The application discloses a medical insurance standard-oriented unified interface adaptation module, and belongs to the technical field of medical information, which is used to solve the problems of non-uniform interface standards, large development workload and difficult maintenance when the existing medical information system is connected with multi-region medical insurance platforms. The technical scheme comprises an interface configuration layer, a protocol conversion layer, a data mapping layer and a routing forwarding layer. The interface configuration layer provides a visual configuration interface, and is used to define access parameters and calling rules of the medical insurance interface. The protocol conversion layer supports mutual conversion of multiple communication protocols, including HTTP, HTTPS, WebService and Socket protocols. The data mapping layer is internally provided with multiple medical insurance data dictionaries, and is used to convert internal data formats of the medical information system into standard data formats of target medical insurance platforms. The routing forwarding layer forwards requests to target medical insurance interfaces according to configured medical insurance platform routing rules, and receives returned results. The application realizes quick connection and adaptation of the medical information system and multiple medical insurance platforms, and reduces development cost.

Description

Technical Field

[0001] This invention belongs to the field of medical information technology, specifically relating to a unified interface adaptation module oriented towards medical insurance standards, which is suitable for data connection and business interaction between medical information systems and medical security platforms in multiple regions. Background Technology

[0002] With the construction of the national medical security information platform and the differentiated implementation of medical insurance policies in various regions, medical information systems need to connect with medical insurance platforms at all levels to complete services such as registration, payment settlement, medical insurance reimbursement, and drug catalog lookup. Medical insurance platforms in different regions exhibit significant differences in interface protocols, data formats, communication methods, and security authentication: some use RESTful API interfaces with HTTP / HTTPS protocols, some use SOAP interfaces with WebService protocols, and some use Socket communication methods; in terms of data formats, the definitions of field names, data types, and value codes vary across platforms; and regarding security authentication, some use API keys, some use digital certificates, and some use the OAuth 2.0 protocol.

[0003] In existing technologies, healthcare information system developers need to independently develop an interface adapter program for each medical insurance platform to achieve interoperability with that specific platform. This point-to-point interoperability method has the following problems: First, the development workload is large, as each new medical insurance platform requires the development of a new adapter program, consuming a lot of manpower and time; second, maintenance is difficult, as each adapter program needs to be modified individually when the interface specifications of the medical insurance platform are upgraded, resulting in high maintenance costs; third, code reusability is low, with a large number of duplicate functions among the various adapter programs, leading to serious waste of resources; and fourth, there is a lack of unified monitoring and management methods, making it difficult to centrally manage and troubleshoot the interface calls of multiple medical insurance platforms. Summary of the Invention

[0004] This invention addresses the technical problems in existing technologies, such as large development workload, maintenance difficulties, low code reuse rate, and lack of unified monitoring and management, when interfacing medical information systems with multi-regional medical insurance platforms. It provides a unified interface adaptation module oriented towards medical insurance standards.

[0005] This invention can be achieved through the following technical solutions: A unified interface adaptation module oriented towards medical insurance standards includes an interface configuration layer, a protocol conversion layer, a data mapping layer, and a routing and forwarding layer. The interface configuration layer provides a visual configuration interface for defining access parameters and invocation rules for the medical insurance interface. The protocol conversion layer supports mutual conversion between multiple communication protocols, including HTTP, HTTPS, WebService, and Socket. The data mapping layer incorporates multiple medical insurance data dictionaries to convert the internal data format of the medical information system into the standard data format of the target medical insurance platform. The routing and forwarding layer forwards requests to the target medical insurance interface according to the configured routing rules of the medical insurance platform and receives the returned results.

[0006] Furthermore, the interface configuration layer includes an interface registration unit, a parameter definition unit, and a call rule configuration unit. The interface registration unit is used to input basic information about the medical insurance interface, including the interface name, interface version, interface address, authentication method, and timeout. The parameter definition unit is used to define the field names, field types, field lengths, and validation rules for the input and output parameters of the medical insurance interface. The call rule configuration unit is used to configure the call order, call frequency limits, and retry strategies for the medical insurance interface.

[0007] Furthermore, the visual configuration interface is either a web-based configuration interface or a desktop configuration interface, and it has a template import / export function, which is used to export the configured medical insurance interface parameters as a configuration file and quickly deploy them to other compatible module instances by importing them.

[0008] Furthermore, the protocol conversion layer includes a protocol identification unit, a protocol conversion engine, and a protocol adapter pool. The protocol identification unit parses request messages and identifies the communication protocol type they employ. The protocol conversion engine converts the request messages into messages in the target protocol format according to the protocol types supported by the target medical insurance platform. The protocol adapter pool includes HTTP protocol adapters, HTTPS protocol adapters, WebService protocol adapters, and Socket protocol adapters.

[0009] Furthermore, the data mapping layer includes a data dictionary library, a field mapping engine, and a value range conversion engine. The data dictionary library stores medical insurance data dictionaries for various medical insurance platforms, including data element identifiers, data element names, data types, data formats, and value ranges. The field mapping engine is used to map the internal fields of the medical information system to the standard fields of the medical insurance platform based on the target medical insurance platform's data dictionary. The value range conversion engine is used to convert the code values ​​of the medical information system into the standard code values ​​of the target medical insurance platform.

[0010] Furthermore, the data dictionary library supports online updates and automatically obtains the latest data dictionary version by connecting to the official data dictionary server of the medical insurance platform. The data dictionary library contains data from the three major medical insurance catalogs, including the drug catalog, the treatment item catalog, and the medical service facility catalog.

[0011] Furthermore, the routing and forwarding layer includes a routing rule storage unit, a request forwarding unit, and a response processing unit. The routing rule storage unit stores the routing rules for each medical insurance platform, including the target address, target port, request path, and load balancing strategy. The request forwarding unit forwards the request to the target medical insurance interface according to the routing rules. The response processing unit receives the result message returned by the medical insurance platform and performs format validation and exception handling.

[0012] Furthermore, it also includes a monitoring and auditing layer, comprising a logging unit, an anomaly alarm unit, and a statistical reporting unit. The logging unit records the request and response messages, call time, and call duration for each interface call. The anomaly alarm unit generates alarm information and notifies operations and maintenance personnel via email, SMS, or in-site messages when an interface call fails or a response times out. The statistical reporting unit provides statistics on the number of interface calls, success rate, average response time, and anomaly type distribution for each medical insurance platform, categorized by time dimension.

[0013] Furthermore, a security authentication layer is included, positioned between the interface configuration layer and the protocol conversion layer. This layer includes an identity authentication unit, a data encryption unit, and a signature verification unit. The identity authentication unit authenticates the user's identity in calls to the medical information system, supporting one or more of API key authentication, digital certificate authentication, and OAuth 2.0 authentication. The data encryption unit encrypts request and response messages for transmission, using symmetric and asymmetric encryption methods. The signature verification unit generates digital signatures for request messages and verifies signatures for response messages.

[0014] Furthermore, it also includes a configuration hot-loading unit, which is connected to the interface configuration layer and is used to load the updated medical insurance interface configuration parameters without stopping the system. The configuration hot-loading unit has a configuration version management function to record the modification history and version rollback of the configuration parameters.

[0015] Compared with the prior art, the present invention has the following advantages: 1. Through the collaborative work of the interface configuration layer, protocol conversion layer, data mapping layer and routing forwarding layer, unified access between medical information systems and multiple medical insurance platforms can be achieved. When adding a new medical insurance platform, only the configuration needs to be completed in the visual configuration interface to achieve the connection. There is no need to redevelop the adaptation program, which greatly reduces the development workload.

[0016] 2. The protocol conversion layer supports mutual conversion between multiple communication protocols such as HTTP, HTTPS, WebService and Socket. The data mapping layer realizes field mapping and value domain conversion through the built-in medical insurance data dictionary, which can adapt to the differences in communication protocols and data formats of different medical insurance platforms. It has strong universality and wide adaptability.

[0017] 3. The monitoring and auditing layer implements full-process logging and anomaly alarms for interface calls, and provides statistical reports on the interface call status of various medical insurance platforms, which facilitates centralized management and troubleshooting by operation and maintenance personnel; the configuration hot-loading unit supports online updates of configuration parameters, and can complete interface adaptation and adjustment without downtime, ensuring business continuity. Attached Figure Description

[0018] The invention will now be further described with reference to the accompanying drawings.

[0019] Figure 1 This is a block diagram of the overall architecture of the unified interface adaptation module for medical insurance standards in this invention.

[0020] Figure 2 This is a schematic diagram of the interface configuration layer in this invention.

[0021] Figure 3 This is a schematic diagram of the protocol conversion layer in this invention.

[0022] Figure 4 This is a schematic diagram of the data mapping layer in this invention.

[0023] Figure 5 This is a schematic diagram of the routing and forwarding layer in this invention.

[0024] Figure 6 This is a schematic diagram of the monitoring and auditing layer in this invention.

[0025] Figure 7 This is a schematic diagram of the security authentication layer in this invention.

[0026] Figure 8 This is a schematic diagram of the workflow of the present invention.

[0027] Figure 9 This is a schematic diagram of the configuration interface in one embodiment of the present invention.

[0028] Figure 10 This is a schematic diagram of the interface call monitoring interface in one embodiment of the present invention.

[0029] The meanings of the markings in the diagram are as follows: 100—Interface Configuration Layer; 110—Interface Registration Unit; 120—Parameter Definition Unit; 130—Call Rule Configuration Unit; 140—Visual Configuration Interface; 200—Protocol Conversion Layer; 210—Protocol Identification Unit; 220—Protocol Conversion Engine; 230—Protocol Adapter Pool; 300—Data Mapping Layer; 310—Data Dictionary; 320—Field Mapping Engine; 330—Value Domain Conversion Engine; 400—Route Forwarding Layer; 410—Route Rule Storage Unit; 420—Request Forwarding Unit; 430—Response Processing Unit; 500—Monitoring and Auditing Layer; 510—Log Recording Unit; 520—Anomaly Alarm Unit; 530—Statistical Report Unit; 600—Security Authentication Layer; 610—Identity Authentication Unit; 620—Data Encryption Unit; 630—Signature Verification Unit; 700—Configuration Hot Reloading Unit. Detailed Implementation

[0030] The present invention will be further described in detail below with reference to specific embodiments. These embodiments are intended to fully disclose the technical solutions of the present invention, enabling those skilled in the art to implement the present invention, and are not intended to limit the scope of protection of the present invention.

[0031] Example 1 like Figure 1 As shown, this embodiment of a unified interface adaptation module for medical insurance standards includes an interface configuration layer 100, a protocol conversion layer 200, a data mapping layer 300, a routing and forwarding layer 400, a monitoring and auditing layer 500, a security authentication layer 600, and a configuration hot-loading unit 700.

[0032] The interface configuration layer 100 provides a visual configuration interface 140 for defining the access parameters and calling rules of the medical insurance interface. For example... Figure 2 As shown, the interface configuration layer 100 includes an interface registration unit 110, a parameter definition unit 120, and a call rule configuration unit 130. The interface registration unit 110 is used to input basic information about the medical insurance interface, including the interface name, interface version, interface address, authentication method, and timeout. The parameter definition unit 120 is used to define the field names, field types, field lengths, and validation rules for the input and output parameters of the medical insurance interface. The call rule configuration unit 130 is used to configure the call order, call frequency limits, and retry strategies for the medical insurance interface. In this embodiment, the visual configuration interface 140 is a web-based configuration interface with template import / export functionality. It can export the configured medical insurance interface parameters as a JSON-formatted configuration file and quickly deploy it to other compatible module instances via import.

[0033] The security authentication layer 600 is located between the interface configuration layer 100 and the protocol conversion layer 200. For example... Figure 7As shown, the security authentication layer 600 includes an identity authentication unit 610, a data encryption unit 620, and a signature verification unit 630. The identity authentication unit 610 is used to authenticate the identity of requests to the medical information system; this embodiment supports both API key authentication and digital certificate authentication. The data encryption unit 620 is used to encrypt and transmit request and response messages; this embodiment uses a hybrid encryption method combining AES symmetric encryption and RSA asymmetric encryption. The signature verification unit 630 is used to generate digital signatures for request messages and verify signatures for response messages.

[0034] like Figure 3 As shown, the protocol conversion layer 200 includes a protocol identification unit 210, a protocol conversion engine 220, and a protocol adapter pool 230. The protocol identification unit 210 parses request messages and identifies the communication protocol type they employ. The protocol conversion engine 220 converts the request messages into messages in the target protocol format according to the protocol types supported by the target medical insurance platform. The protocol adapter pool 230 includes HTTP protocol adapters, HTTPS protocol adapters, WebService protocol adapters, and Socket protocol adapters.

[0035] like Figure 4 As shown, the data mapping layer 300 includes a data dictionary library 310, a field mapping engine 320, and a value domain conversion engine 330. The data dictionary library 310 stores medical insurance data dictionaries for various medical insurance platforms, including data element identifiers, data element names, data types, data formats, and value domain ranges. The data dictionary library 310 supports online updates, automatically obtaining the latest data dictionary version by connecting to the official data dictionary server of the medical insurance platform. It contains built-in data from the three major medical insurance catalogs (drug catalog, treatment item catalog, and medical service facility catalog). The field mapping engine 320 maps the internal fields of the medical information system to the standard fields of the medical insurance platform based on the target medical insurance platform's data dictionary. The value domain conversion engine 330 converts the code values ​​of the medical information system into the standard code values ​​of the target medical insurance platform.

[0036] like Figure 5 As shown, the routing and forwarding layer 400 includes a routing rule storage unit 410, a request forwarding unit 420, and a response processing unit 430. The routing rule storage unit 410 stores routing rules for each medical insurance platform, including the target address, target port, request path, and load balancing strategy. The request forwarding unit 420 forwards requests to the target medical insurance interface according to the routing rules. The response processing unit 430 receives the result messages returned by the medical insurance platform and performs format validation and exception handling.

[0037] like Figure 6As shown, the monitoring and auditing layer 500 includes a logging unit 510, an anomaly alarm unit 520, and a statistical reporting unit 530. The logging unit 510 records the request message, response message, call time, and call duration for each interface call. The anomaly alarm unit 520 generates alarm information and notifies operations and maintenance personnel via email when an interface call fails or a response times out. The statistical reporting unit 530 statistically analyzes the number of interface calls, success rate, average response time, and anomaly type distribution for each medical insurance platform over a time dimension.

[0038] The configuration hot loading unit 700 is connected to the interface configuration layer 100 and is used to load the updated medical insurance interface configuration parameters without stopping the system. The configuration hot loading unit 700 has a configuration version management function to record the modification history and version rollback of the configuration parameters.

[0039] The workflow of this embodiment is as follows: Figure 8 As shown: When a medical information system initiates a business request, the request first enters the interface configuration layer 100. The interface configuration layer 100 obtains the corresponding interface configuration information based on the business type and medical insurance platform identifier in the request. The request then enters the security authentication layer 600 for identity authentication, data decryption, and signature verification. After successful verification, it enters the protocol conversion layer 200. The protocol identification unit 210 identifies the request protocol type, and the protocol conversion engine 220 converts the request into a protocol format supported by the target medical insurance platform. Then, it enters the data mapping layer 300, where the field mapping engine 320 and value domain conversion engine 330 convert the data format into the standard format of the target medical insurance platform. The routing and forwarding layer 400 forwards the request to the target medical insurance interface according to routing rules and receives the returned result. The returned result is reverse-converted by the data mapping layer 300, encrypted and signed by the security authentication layer 600, and then returned to the medical information system. The monitoring and auditing layer 500 records the entire call log, and the anomaly alarm unit 520 triggers an alarm when an anomaly occurs.

[0040] Example 2 The difference between this embodiment and Embodiment 1 is that the visual configuration interface 140 is a desktop configuration interface, supporting offline configuration and suitable for medical insurance interface configuration in network isolation environments. The configuration hot-loading unit 700 supports gray-scale deployment of configurations, that is, the new configuration is first applied to a portion of requests for verification, and then applied to all requests after verification, reducing the risk of configuration changes. The data dictionary library 310 contains medical insurance data dictionaries from multiple provinces, and the field mapping engine 320 supports one-to-many and many-to-one field mapping relationships, that is, one source field can be mapped to multiple target fields, and multiple source fields can also be merged and mapped to one target field. The routing and forwarding layer 400 also supports request circuit breaking and degradation. When a medical insurance platform interface response times out or the exception rate reaches a threshold, it automatically breaks the circuit and returns a preset degradation result. The rest of the structure is the same as in Embodiment 1.

[0041] Example 3 The difference between this embodiment and Embodiment 1 is that: the security authentication layer 600 supports the OAuth2.0 authentication protocol, making it suitable for medical insurance platforms using OAuth2.0 authentication. The statistical reporting unit 530 of the monitoring and auditing layer 500 can generate a visual dashboard to display the real-time health status of interface calls for each medical insurance platform in chart form. The configuration version management function of the configuration hot-loading unit 700 supports configuration comparison and can intuitively display the differences between different version configurations. An MQTT protocol adapter has also been added to the protocol adapter pool 230, enabling the adaptation module to support medical insurance data interaction in IoT scenarios. The remaining structure is the same as in Embodiment 1.

[0042] In the description of this specification, references to terms such as "an embodiment," "example," "specific example," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0043] The above description is merely an example and illustration of the present invention. Those skilled in the art can make various modifications or additions to the specific embodiments described, or use similar methods to replace them, as long as they do not deviate from the invention or exceed the scope defined in the claims, all of which should fall within the protection scope of the present invention.

Claims

1. A unified interface adaptation module oriented towards medical insurance standards, characterized in that, include: The interface configuration layer provides a visual configuration interface for defining the access parameters and calling rules of the medical insurance interface; The protocol conversion layer supports mutual conversion between multiple communication protocols, including HTTP, HTTPS, WebService, and Socket protocols. The data mapping layer has multiple built-in medical insurance data dictionaries, which are used to convert the internal data format of the medical information system into the standard data format of the target medical insurance platform. The routing and forwarding layer forwards requests to the target medical insurance interface according to the configured medical insurance platform routing rules and receives the returned results. The interface configuration layer, protocol conversion layer, data mapping layer, and routing forwarding layer are connected in sequence. The output of the routing forwarding layer is connected to the external medical insurance platform, and the input of the interface configuration layer is connected to the medical information system.

2. The unified interface adaptation module for medical insurance standards according to claim 1, characterized in that, The interface configuration layer includes: The interface registration unit is used to enter the basic information of the medical insurance interface, including the interface name, interface version, interface address, authentication method, and timeout period. The parameter definition unit is used to define the field names, field types, field lengths, and validation rules of the input and output parameters of the medical insurance interface; The call rule configuration unit is used to configure the call order, call frequency limit and retry strategy of the medical insurance interface; The interface registration unit, parameter definition unit, and call rule configuration unit are interactively connected to the visual configuration interface.

3. The unified interface adaptation module for medical insurance standards according to claim 2, characterized in that, The visual configuration interface can be a web-based configuration interface or a desktop configuration interface. The visual configuration interface has a template import and export function, which is used to export the configured medical insurance interface parameters into a configuration file and quickly deploy it to other compatible module instances by importing it.

4. The unified interface adaptation module for medical insurance standards according to claim 1, characterized in that, The protocol conversion layer includes: The protocol identification unit is used to parse the request message and identify the type of communication protocol it uses; The protocol conversion engine converts the request message into a message in the target protocol format based on the protocol types supported by the target medical insurance platform. The protocol adapter pool includes HTTP protocol adapters, HTTPS protocol adapters, WebService protocol adapters, and Socket protocol adapters; The input of the protocol identification unit is connected to the output of the interface configuration layer, the output of the protocol identification unit is connected to the input of the protocol conversion engine, and the output of the protocol conversion engine is connected to the input of the protocol adapter pool.

5. The unified interface adaptation module for medical insurance standards according to claim 1, characterized in that, The data mapping layer includes: The data dictionary library stores medical insurance data dictionaries from various medical insurance platforms. The medical insurance data dictionary includes data element identifiers, data element names, data types, data formats, and value ranges. The field mapping engine is used to map the internal fields of the medical information system to the standard fields of the medical insurance platform based on the data dictionary of the target medical insurance platform. Value domain conversion engine is used to convert the code values ​​of the medical information system into the standard code values ​​of the target medical insurance platform; The field mapping engine and the value range conversion engine are respectively connected to the data dictionary database.

6. The unified interface adaptation module for medical insurance standards according to claim 5, characterized in that, The data dictionary library supports online updates and automatically obtains the latest data dictionary version by connecting to the official data dictionary server of the medical insurance platform. The data dictionary library contains data from the three major medical insurance catalogs, namely the drug catalog, the treatment item catalog, and the medical service facility catalog.

7. The unified interface adaptation module for medical insurance standards according to claim 1, characterized in that, The routing and forwarding layer includes: A routing rule storage unit is used to store the routing rules of each medical insurance platform. The routing rules include the target address, target port, request path, and load balancing strategy. The request forwarding unit forwards the request to the target medical insurance interface according to the routing rules; The response processing unit is used to receive the result messages returned by the medical insurance platform and perform format verification and exception handling. The output of the routing rule storage unit is connected to the input of the request forwarding unit, and the output of the request forwarding unit is connected to the input of the response processing unit.

8. The unified interface adaptation module for medical insurance standards according to claim 1, characterized in that, It also includes a monitoring and auditing layer, which includes: The log recording unit is used to record the request message, response message, call time, and call duration for each interface call; The anomaly alarm unit is used to generate alarm information and notify operation and maintenance personnel via email, SMS or in-site message when the interface call fails or the response times out. The statistical reporting unit is used to statistically analyze the number of API calls, success rate, average response time, and distribution of exception types for each medical insurance platform over a time period.

9. The unified interface adaptation module for medical insurance standards according to claim 1, characterized in that, It also includes a security authentication layer, which is located between the interface configuration layer and the protocol conversion layer, and includes: The identity authentication unit is used to authenticate the call request to the medical information system. The identity authentication supports any one or more of API key authentication, digital certificate authentication, and OAuth2.0 authentication. A data encryption unit is used to encrypt and transmit request and response messages, wherein the encryption methods include symmetric encryption and asymmetric encryption; The signature verification unit is used to generate digital signatures for request messages and verify signatures for response messages.

10. The unified interface adaptation module for medical insurance standards according to claim 1, characterized in that, It also includes a configuration hot-loading unit, which is connected to the interface configuration layer and is used to load the updated medical insurance interface configuration parameters without stopping the system. The configuration hot-loading unit has a configuration version management function to record the modification history and version rollback of the configuration parameters.

Images