A method, system and electronic device for centralized processing of insurance claim data
By monitoring changes in the underwriting claims database and transmitting data to Kafka and Elasticsearch, the inefficient query efficiency caused by data scattered storage in multiple provinces is solved, and efficient processing of insurance claims reporting and user experience are achieved.
Patent Information
- Application Number
- CN202310118210.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-02-03
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2043-02-03
AI Technical Summary
In the insurance claims system, the insured and claims data in multiple provinces are stored scattered, resulting in low data query efficiency. Customer service personnel need to maintain multiple database addresses, extending the reporting processing time and affecting the user experience.
By monitoring the changes in the underwriting claims database of different addresses in real time, transmitting data to Kafka, and storing insurance claim data to Elasticsearch, centralized query is realized and dependence on multiple database addresses is reduced.
It improves the efficiency of claim reporting, and customer service personnel do not need to enter query conditions and configure multiple database addresses, achieving rapid retrieval and efficient processing.
Smart Images

Figure CN116069814B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of insurance data processing, and in particular to a method, system and electronic equipment for centralized processing of insurance policy claim data. Background Art
[0002] Currently, the insurance underwriting and claims settlement systems are deployed on a provincial basis, and the underwriting and claims settlement data addresses of a single province are also different. In addition, auto insurance and non-auto insurance are divided at the insurance type level, resulting in a large number of related databases. When performing data queries, many data addresses need to be maintained.
[0003] The centralized reporting system is responsible for the reporting of claims. In order to simultaneously handle reports of general claims (where the insured location is inconsistent with the location of the accident), customer service specialists must have the authority to query national insurance policies and claims data. If you want to query the original database of underwriting and claims, you need to enter the query conditions of the underwriting agency and the case agency, and configure multiple database addresses. When the actual customer service receives the report, entering the query conditions will extend the processing time of the customer service staff, resulting in low reporting efficiency and affecting the user experience. Summary of the invention
[0004] The purpose of the present invention is to provide a method, system and electronic equipment for centralized processing of insurance policy claim data, which can improve the efficiency of insurance claim reporting.
[0005] To achieve the above object, the present invention provides the following solutions:
[0006] A method for centralized processing of insurance claim data, comprising:
[0007] Monitor in real time the changes of various underwriting and claims databases located at different addresses; the underwriting and claims database is used to store insurance policy claim data; the changes of the underwriting and claims database include adding new data, modifying data and deleting data;
[0008] When any underwriting and claims database changes, the corresponding change data is transmitted to the distributed publish-subscribe messaging system Kafka;
[0009] Store insurance claim data into Elasticsearch based on data in Kafka;
[0010] Report claims based on Elasticsearch.
[0011] Optionally, the insurance claims database is an informix database.
[0012] Optionally, the incremental data migration tool SinoRepl is used to monitor changes in each underwriting and claims database in real time.
[0013] Optionally, when any underwriting and claims database changes, the corresponding change data is transmitted to the distributed publish-subscribe messaging system Kafka in JSON format.
[0014] Optionally, each underwriting and claims database includes a business main table and a business sub-table;
[0015] The business master table is used to store the serial number, policy number, report number and actual processing location; the serial number is the primary key of the business master table; the actual processing location is the insurance location or the accident location;
[0016] The business sub-table is used to store serial numbers, business data of the insured place or business data of the accident place; the serial numbers in the business sub-table correspond to the serial numbers in the business main table;
[0017] The insurance policy claim data includes serial number, policy number, report number, actual processing location and business data; the business data is business data at the place of insurance or business data at the place of accident.
[0018] Optionally, when the change in the underwriting and claims database is the addition of new data, the corresponding change data is the newly added policy claim data; when the change in the underwriting and claims database is the modification of data, the corresponding change data is the modified policy claim data; when the change in the underwriting and claims database is the deletion of data, the corresponding change data is the serial number of the deleted policy claim data.
[0019] Optionally, storing the insurance claim data in Elasticsearch based on the data in Kafka specifically includes:
[0020] When the underwriting and claims database changes and the data of the business sub-table of the underwriting and claims database is transmitted to Kafka, query whether the data of the corresponding business main table is stored in Elasticsearch. If yes, store the data of the business sub-table in Elasticsearch; otherwise, store the data of the business sub-table in a temporary table;
[0021] When the data of the business main table of the underwriting and claims database is transmitted to Kafka, it is queried whether the data of the corresponding business sub-table is stored in the temporary table. If so, the data of the business main table and the corresponding business sub-table are stored in Elasticsearch. Otherwise, the data of the business main table is stored in Elasticsearch.
[0022] Optionally, the temporary table is a data table opened in advance in a PostgreSQL database.
[0023] To achieve the above object, the present invention also provides the following solution:
[0024] A centralized processing system for insurance claim data, comprising:
[0025] A monitoring unit, used for monitoring changes in various insurance claims databases located at different addresses in real time; the insurance claims database is used to store insurance policy claim data; changes in the insurance claims database include adding new data, modifying data and deleting data;
[0026] A transmission unit, connected to the monitoring unit, is used to transmit corresponding change data to the distributed publish-subscribe messaging system Kafka when any underwriting and claims database changes;
[0027] A storage unit, connected to the transmission unit, for storing the insurance policy claim data in Elasticsearch based on the data in Kafka;
[0028] A processing unit is connected to the storage unit and is used for making a claim report based on Elasticsearch.
[0029] To achieve the above object, the present invention also provides the following solution:
[0030] An electronic device includes a memory and a processor, wherein the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute the above-mentioned insurance policy claim data centralized processing method.
[0031] According to the specific embodiments provided by the present invention, the present invention discloses the following technical effects:
[0032] By monitoring changes in the underwriting and claims databases at different addresses, the change data is transmitted to Kafka, and then the policy claim data is stored in Elasticsearch based on the data in Kafka. Customer service specialists only need to make claims reports based on Elasticsearch, without having to enter underwriting agency query conditions, case agency query conditions, etc., and there is no need to configure multiple database addresses, which improves the efficiency of claims reporting. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0034] Figure 1 It is a flow chart of the centralized processing method of insurance policy claim data of the present invention;
[0035] Figure 2 This is a schematic diagram of the process of synchronizing the source data of the underwriting and claims database to the Elasticsearch database;
[0036] Figure 3 It is a module schematic diagram of the insurance policy claim data centralized processing system of the present invention.
[0037] Explanation of symbols:
[0038] Monitoring unit-1, transmission unit-2, storage unit-3, processing unit-4. DETAILED DESCRIPTION
[0039] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0040] The purpose of the present invention is to provide a method, system and electronic device for centralized processing of insurance policy claim data, which adopts a data centralized mode to synchronize the original library data of underwriting and claims to the ES (Elasticsearch) database. When querying, there is no need to enter the institutional information, and the efficient query characteristics of ES are utilized to realize the rapid retrieval of underwriting and claims data.
[0041] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.
[0042] Embodiment 1
[0043] like Figure 1 As shown, this embodiment provides a method for centralized processing of insurance claim data, including:
[0044] S1: Monitor the changes of various insurance claims databases located at different addresses in real time. In this embodiment, the incremental data migration tool SinoRepl is used to monitor the changes of various insurance claims databases in real time.
[0045] The insurance claim database is used to store insurance policy claim data. In this embodiment, the insurance claim database is an informix database.
[0046] Specifically, each underwriting and claims database includes a business main table and a business sub-table. The business main table is used to store the serial number (the primary key of the business main table, i.e., the unique identifier), policy number, report number, and actual processing location. The actual processing location is the processing identifier of the place of accident or the processing identifier of the place of insurance. The business sub-table is divided into two types: the place of insurance sub-table and the place of accident sub-table. Among them, the place of insurance sub-table is used to store the serial number and the business data of the place of insurance; the place of accident sub-table is used to store the serial number and the business data of the place of accident. The serial number in the business sub-table corresponds to the serial number in the business main table, that is, the business main table and the business sub-table are associated through the serial number. The serial number in the business sub-table is unique, but the serial number is not the primary key of the business sub-table.
[0047] The insurance claim data includes serial number, policy number, report number, actual processing location and business data. The business data is the business data of the insurance location or the business data of the accident location. Each claim has a unique report number and a unique processing location, i.e., the accident location or the insurance location. Both the business main table and the business subtable are data tables with pre-specified numbers in the source informix.
[0048] Specifically, a claim case corresponds to a record in the business master table. For any claim case, first determine whether the actual processing location of the corresponding serial number in the business master table is the insurance location or the accident location. If it is the insurance location, then find the corresponding insurance location business data in the insurance location business subtable, that is, a record with the same serial number in the insurance location business subtable and the business master table; if it is the accident location, then find the corresponding accident location business data in the accident location business subtable, that is, a record with the same serial number in the accident location business subtable and the business master table.
[0049] As another implementation, the insurance claim database includes an insurance database and a claim database. Both the insurance database and the claim database include a business main table and a business sub-table.
[0050] S2: When any underwriting and claims database changes, the corresponding change data is transmitted to the distributed publish-subscribe messaging system Kafka. Preferably, the change data is pushed to the distributed publish-subscribe messaging system Kafka in json format.
[0051] In this embodiment, the changes in the underwriting and claims database include adding new data, modifying data, and deleting data. When the change in the underwriting and claims database is adding new data, the corresponding changed data is the newly added insurance policy claim data. When the change in the underwriting and claims database is modifying data, the corresponding changed data is the modified insurance policy claim data. When the change in the underwriting and claims database is deleting data, the corresponding changed data is the serial number of the deleted insurance policy claim data. That is, when adding and modifying data, the entire row of data is pushed to Kafka, and when deleting data, only the serial number is pushed.
[0052] S3: Stores insurance claims data in Elasticsearch based on data in Kafka. Elasticsearch is the distributed search and analysis engine at the core of the ElasticStack.
[0053] Specifically, when the insurance and claims database changes and the data of the business sub-table of the insurance and claims database is transmitted to Kafka, it is queried whether the data of the corresponding business main table is stored in Elasticsearch. If yes, the data of the business sub-table is stored in Elasticsearch, otherwise, the data of the business sub-table is stored in a temporary table. The temporary table is a data table opened in advance in the PostgreSQL database.
[0054] When the data of the business main table of the underwriting and claims database is transmitted to Kafka, it is queried whether the data of the corresponding business sub-table is stored in the temporary table. If so, the data of the business main table and the corresponding business sub-table are stored in Elasticsearch. Otherwise, the data of the business main table is stored in Elasticsearch.
[0055] S4: Claim reporting based on Elasticsearch. The present invention utilizes ES's massive data search and analysis technology to perform real-time data analysis on massive data. In addition, the ES database synchronizes some useful data in the library source, not all data. Therefore, the efficiency of querying the ES library is higher than that of querying the library source. This improves processing efficiency.
[0056] In order to better understand the solution of the present invention, Figure 2 As shown, the following specifically describes the process of synchronizing the source data of the underwriting and claims database to the Elasticsearch database:
[0057] Data processing application A reads data from Kafka and processes it. The data pushed to Kafka by the monitoring tool during deletion is not the entire row of data, but only contains the sequence number, not the report number (the unique identifier of the claim). And due to the characteristics of general claims, when processing data, it is necessary to determine whether to take the data of the insured place or the data of the accident place. Therefore, it is necessary to ensure that the main business table of the source informix database is first put into ES, and then the sub-table is put into ES. Therefore, a temporary table of PG (PostgreSQL) library is opened to:
[0058] (1) When adding new data, the relationship between the serial number and the report number is stored in a temporary table. This is because SinoRepl only pushes the primary key when it detects data deletion in the source database (underwriting and claims database). When there is a deletion action in the source database, check this temporary table and obtain the report number corresponding to the deleted data through the serial number. After checking, mark it as deletable for subsequent clearing of the temporary table.
[0059] (2) Since the data source changes in Kafka, the change order of the business main table and the business sub-table cannot be guaranteed. Therefore, when the data of the business sub-table is first transmitted to Kafka, it is first checked whether the business main table has been stored in ES. If the business main table has not been stored in ES, the data of the business sub-table is stored in a temporary table. If the business main table has been stored in ES, the data of the business sub-table is transmitted to data processing application B.
[0060] After all the data in the business main table in Kafka is processed, the data in the business sub-table in the temporary table is stored in ES. Change the deletable flag of the temporary table for subsequent clearing.
[0061] Data processing application B performs secondary processing on the data processed by data processing application A, including:
[0062] (1) For a change in a piece of data, the change data of multiple business main tables and business sub-tables processed by data processing application A are organized into a wide table of data and stored in the centralized ES.
[0063] (2) Store values with different source and column attributes (e.g., extended warranty and non-auto insurance) but the same meaning in ES using the same key.
[0064] The data processing application A and the data processing application B of the present invention are processed separately, so that when the monitoring tool of the data source is changed, resulting in a different data format pushed to Kafka, only the data processing application A needs to be changed and adjusted to process the corresponding data format, and the data processing application B can remain unchanged for easy maintenance.
[0065] The present invention centralizes the data of insurance policies and claims, and can uniformly query data in a large range without locating the affiliated institutions, which is convenient for statistical analysis and improves the efficiency of customer service personnel. In addition, during the period of upgrading and maintenance of the underwriting and claims database source or service problems, the ES database can still be used normally for business processing, realizing decoupling from the underwriting and claims systems. It is only necessary to maintain the ES database information, and it is not necessary to configure all the database source addresses, which reduces the difficulty of operation and maintenance.
[0066] Embodiment 2
[0067] In order to execute the method corresponding to the above-mentioned embodiment 1 and realize the corresponding functions and technical effects, a system for centralized processing of insurance policy claim data is provided below.
[0068] like Figure 3 As shown, the insurance policy claim data centralized processing system provided in this embodiment includes: a monitoring unit 1, a transmission unit 2, a storage unit 3 and a processing unit 4.
[0069] The monitoring unit 1 is used to monitor the changes of the insurance claim databases located at different addresses in real time. The insurance claim database is used to store insurance policy claim data. The changes of the insurance claim database include adding new data, modifying data and deleting data.
[0070] The transmission unit 2 is connected to the monitoring unit 1, and the transmission unit 2 is used to transmit the corresponding change data to the distributed publish-subscribe message system Kafka when any underwriting and claims database changes.
[0071] The storage unit 3 is connected to the transmission unit 2, and the storage unit 3 is used to store the insurance policy claim data in Elasticsearch based on the data in Kafka.
[0072] The processing unit 4 is connected to the storage unit 3, and the processing unit 4 is used to make a claim report based on Elasticsearch.
[0073] Compared with the prior art, the insurance policy claim data centralized processing system provided in this embodiment has the same beneficial effects as the insurance policy claim data centralized processing method provided in Example 1, which will not be described in detail here.
[0074] Embodiment 3
[0075] This embodiment provides an electronic device, including a memory and a processor, wherein the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute the insurance policy claim data centralized processing method of the first embodiment.
[0076] Optionally, the above-mentioned electronic device may be a server.
[0077] In addition, an embodiment of the present invention further provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method for centralized processing of insurance policy claim data of embodiment 1.
[0078] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.
[0079] The principles and implementation methods of the present invention are described in this article using specific examples. The description of the above embodiments is only used to help understand the method and core idea of the present invention. At the same time, for those skilled in the art, according to the idea of the present invention, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting the present invention.
Claims
1. A method for centralized processing of insurance claim data, characterized in that: The method for centralized processing of insurance policy claims data includes: Monitor in real time the changes of various underwriting and claims databases located at different addresses; the underwriting and claims database is used to store insurance policy claim data; the changes of the underwriting and claims database include adding new data, modifying data and deleting data; Each underwriting and claims database includes a business main table and a business sub-table; the business main table is used to store the serial number, policy number, report number and actual processing location; the serial number is the primary key of the business main table; the actual processing location is the insurance location or the accident location; the business sub-table is used to store the serial number, insurance location business data or accident location business data; the serial number in the business sub-table corresponds to the serial number in the business main table; The insurance claim data includes serial number, policy number, report number, actual processing location and business data; the business data is business data of the insurance location or business data of the accident location; When any underwriting and claims database changes, the corresponding change data is transmitted to the distributed publish-subscribe messaging system Kafka; The insurance claim data is stored in Elasticsearch based on the data in Kafka, including: When the underwriting and claims database changes and the data of the business sub-table of the underwriting and claims database is transmitted to Kafka, query whether the data of the corresponding business main table is stored in Elasticsearch. If yes, store the data of the business sub-table in Elasticsearch; otherwise, store the data of the business sub-table in a temporary table; When the data of the business main table of the underwriting and claims database is transmitted to Kafka, it is queried whether the data of the corresponding business sub-table is stored in the temporary table. If yes, the data of the business main table and the data of the corresponding business sub-table are stored in Elasticsearch. Otherwise, the data of the business main table is stored in Elasticsearch. Report claims based on Elasticsearch.
2. The method for centralized processing of insurance claim data according to claim 1, characterized in that: The insurance claims database is an informix database.
3. The method for centralized processing of insurance claim data according to claim 1, characterized in that: The incremental data migration tool SinoRepl is used to monitor changes in each underwriting and claims database in real time.
4. The method for centralized processing of insurance claim data according to claim 1, characterized in that: When any underwriting and claims database changes, the corresponding change data will be transmitted to the distributed publish-subscribe messaging system Kafka in JSON format.
5. The method for centralized processing of insurance claim data according to claim 1, characterized in that: When the change in the insurance and claims database is the addition of new data, the corresponding change data is the newly added policy claim data; when the change in the insurance and claims database is the modification of data, the corresponding change data is the modified policy claim data; when the change in the insurance and claims database is the deletion of data, the corresponding change data is the serial number of the deleted policy claim data.
6. The method for centralized processing of insurance claim data according to claim 1, characterized in that: The temporary table is a data table opened in advance in the PostgreSQL database.
7. A centralized processing system for insurance claim data, characterized in that: The insurance policy claim data centralized processing system includes: A monitoring unit, used for monitoring changes in various insurance claims databases located at different addresses in real time; the insurance claims database is used to store insurance policy claim data; changes in the insurance claims database include adding new data, modifying data and deleting data; Each underwriting and claims database includes a business main table and a business sub-table; the business main table is used to store the serial number, policy number, report number and actual processing location; the serial number is the primary key of the business main table; the actual processing location is the insurance location or the accident location; the business sub-table is used to store the serial number, insurance location business data or accident location business data; the serial number in the business sub-table corresponds to the serial number in the business main table; The insurance claim data includes serial number, policy number, report number, actual processing location and business data; the business data is business data of the insurance location or business data of the accident location; A transmission unit, connected to the monitoring unit, is used to transmit corresponding change data to the distributed publish-subscribe messaging system Kafka when any underwriting and claims database changes; A storage unit connected to the transmission unit, and used to store the insurance policy claim data in Elasticsearch based on the data in Kafka, specifically including: when the insurance claim database changes and the data of the business sub-table of the insurance claim database is transmitted to Kafka, query whether the corresponding business main table data is stored in Elasticsearch, if yes, store the data of the business sub-table in Elasticsearch, otherwise, store the data of the business sub-table in a temporary table; when the data of the business main table of the insurance claim database is transmitted to Kafka, query whether the corresponding business sub-table data is stored in the temporary table, if yes, store the data of the business main table and the corresponding business sub-table in Elasticsearch, otherwise, store the data of the business main table in Elasticsearch; A processing unit is connected to the storage unit and is used for making a claim report based on Elasticsearch.
8. An electronic device, characterized in that: It comprises a memory and a processor, wherein the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute the method for centralized processing of insurance policy claim data as described in any one of claims 1 to 6.
