A method and device for constructing a claim standardization model

Abstract

The present application relates to the field of information technology, and provides a method and device for constructing a claim standardization model. The purpose of the present application is to automatically establish the data specification problem between multiple independent systems and a claim system, that is, the data of multiple systems can be standardized and unified to the claim system without manual intervention, for subsequent calling of the claim system. The main scheme includes connecting each loan product system database, assembling an SQL execution statement according to a data mapping relationship, assigning values of corresponding fields of corresponding tables in the database of each loan system to corresponding fields of an input parameter table in the database of the claim system, and obtaining data that needs to be claimed from an insurance company due to overdue of a loaner; screening out insurance companies that meet the conditions; after screening out the insurance companies, interacting with an API interface of the insurance company to obtain claim permission by using the data information stored in the input parameter table, and if the claim permission is refused, continuing to route an alternative claim company for claim.

Description

Technical Field

[0001] This invention relates to the field of information technology, specifically a method and apparatus for constructing a standardized claims model. Background Technology

[0002] Business pressure

[0003] To achieve the goal of simultaneously developing internet transaction banking, supply chain finance banking, and small business (B2B and B2C) services, banks have launched various loan products, some of which involve joint lending models. As the business continues to grow, to protect the rights of investors and reduce financial losses from non-performing loans, a comprehensive compensation guarantee is needed to support the rapid development of the business.

[0004] System pressure

[0005] Currently, each product has its own set of claims business logic. As the business continues to develop, the system has undergone continuous patching and upgrades to support business development, resulting in a large amount of redundant and overlapping code, high maintenance costs, and high iteration implementation costs.

[0006] The urgency of restructuring

[0007] To protect the rights and interests of investors, an insurance company will be introduced to provide credit guarantee insurance for the promissory notes under the cooperation agreement. For promissory notes that meet the conditions for claim, our bank has the right to apply for compensation to reduce losses and lower non-performing loans. The goal is to automate the insurance claim function in the system, thereby protecting the project revenue of both our bank and the partner banks.

[0008] Therefore, a system capable of supporting different business models and quickly implementing claims processing functions by connecting to industry standard models has emerged. Reducing redundant code and standardizing development processes lays the foundation for lower implementation costs in the future.

[0009] Currently, the business data backends for various bank loan products are mostly separate. Due to differences in products and channels, and variations in the information tables for corporate and personal business transactions, data inconsistency arises. In an automated claims system, data retrieved from different tables in the database, unlike other business systems, needs to be standardized before it can be accessed by the automated claims system.

[0010] For example, in system A, the fields of table A in the database are "customer name", "phone number" and "ID number";

[0011] The data in system B may exist in table B or table D, and the field names in the corresponding tables may be "Account Name", "Mobile Number", or "ID Number".

[0012] If an automated claims system needs to retrieve relevant data from systems A and B, the existing traditional approach is to have a data table S in the automated claims system. Data table S has fields such as "customer name", "mobile phone number" and "ID card number". The mapping relationship between each field of table A in system A and table S in system S is hardcoded, such as table A.customer name → table S.customer name, table A.phone number → table S.mobile phone number, table A.ID card number → table S.ID card number.

[0013] The mapping relationship between each field of table B in system B and table S in system S: Table B. Account Name → Table S. Customer Name, Table B. Mobile Phone Number → Table S. Mobile Phone Number, Table B. ID Card Number → Table S. ID Card Number;

[0014] However, this method has the following drawbacks:

[0015] 1. If a new field M is added to table S in system S,

[0016] 1.1 Assuming that the field F that needs to be mapped to the M field exists in various systems, in this case, it is also necessary to rewrite the code and create a new mapping relationship between the F field in each system and the M field in table S. Since each system implements the mapping of the F field that the M field needs to be mapped, in this case, the mapping relationship of each system can be written in code at once.

[0017] 1.2 Suppose that the field F that the M field needs to map does not exist in some systems, and the field F that the M field needs to map needs to be added to the corresponding system later, then the code needs to be rewritten to establish the mapping relationship.

[0018] 2. If a new product system is added to the existing systems, the traditional approach would be to manually write code to configure the mapping relationship so that the claims system can obtain data later. Summary of the Invention

[0019] The purpose of this invention is to automatically establish data standardization between multiple independent systems and the claims system, that is, to standardize and unify the data of multiple systems into the claims system without manual intervention, so that the claims system can call it later.

[0020] To solve the above-mentioned technical problems, the present invention adopts the following technical solution, the specific implementation of which is as follows:

[0021] This invention provides a method for constructing a standardized claims model, specifically including the following steps:

[0022] Step 1: The claims system connects to each loan product system based on the database address, account, and password. It assembles SQL execution statements according to the data mapping relationship, assigns the values ​​of the corresponding fields in the corresponding tables of each loan system's database to the corresponding fields in the input parameter table of the claims system's database, and obtains the data that needs to be claimed from the insurance company due to the borrower's overdue payment.

[0023] Step 2: Based on the data information stored in the input parameter table, such as one or more of the following conditions: business type, channel type, claims mode, claims amount, overdue days, weight, and total number of claims customers, create a claims routing model. The model can then be used to route and filter eligible insurance companies to customers who meet the claims criteria.

[0024] Step 3: After filtering out the insurance companies, interact with the data information stored in the API parameter table of the insurance companies to obtain claim approval. If rejected, you can continue to route alternative claim companies.

[0025] Step 4: Determine whether the claim was successful based on the response from the insurance company's API interface. If successful, interact with the accounting microservice.

[0026] Step 5: The financial microservices uniformly process the early settlement of overdue on-balance-sheet transactions for borrowers, generating a set of accounting documents and related reports for early settlement;

[0027] Step 6: The loan microservice copies the borrower's original loan records for off-balance-sheet accounting, and provides customers with functions such as checking accounts, making repayments, and collecting debts.

[0028] Based on the above technical solution, the claims system connects to each loan product system according to the database address, account number, and password of each loan product system. It assembles SQL statements according to the data mapping relationship. When the corresponding data table or field in the corresponding data table cannot be found in the database of the loan product system, it executes the assembled SQL statement to automatically update the data.

[0029] Based on the above technical solution, before executing the automatic update operation using assembled SQL statements, it is necessary to establish mapping matching data in table L of the databases of various loan systems. The steps include:

[0030] Step a: In each loan system, a parameter table name identifier field is set in table L. The value of the parameter table name identifier field is set to the actual table name of the parameter table in the database.

[0031] Step b: Set one or more mapping matching data in table L of each loan system. In the mapping matching data, except for the input parameter table name identifier field which is the actual table name of the input parameter table, the values ​​of other fields in table L are the field names that need to be mapped to the input parameter table.

[0032] Based on the above technical solution, perform an automatic update operation by assembling SQL statements:

[0033] Step c: After the claims system connects to the database of each loan product system, it uses the actual table name of the input parameter table as the value to query the database of the corresponding loan product system to find the table name L containing the "actual table name of the input parameter table".

[0034] Step d: Then, take each field name in the input parameter table as a query condition and "the actual table name of the input parameter table" as a constraint condition to query the corresponding field name N in table L for each field name, and obtain the mapping relationship between each field in the input parameter table and each field in table L in each loan system.

[0035] Step e: Assemble the SQL execution statement according to the mapping relationship, update or insert the data in table L into the input parameter table, and obtain the data that needs to be claimed from the insurance company due to the borrower's overdue payment. The SQL execution statement is saved locally for easy access later.

[0036] Based on the above technical solution, in step 3, according to the different API interaction requirements of different insurance companies, the loan microservice completes the assembly of XML / TCP messages through the database, and the open platform completes the concatenation of external JSON messages by parses the XML messages in a loop. The open platform points to the API interface of different claims companies according to the messageType and messageCode values ​​in the header file of the API request.

[0037] The present invention also provides an apparatus for constructing a standardized claims model, specifically including the following steps:

[0038] The claims data acquisition module and claims system connect to each loan product system based on the database address, account, and password of each loan product system. Based on the data mapping relationship, they assemble SQL execution statements and assign the values ​​of the corresponding fields in the corresponding tables of each loan system's database to the corresponding fields in the input parameter table of the claims system's database to obtain the data that needs to be claimed from the insurance company due to the borrower's overdue payment.

[0039] Insurance Company Matching Module: Based on the data information stored in the input parameter table, such as business type, channel type, claims mode, claims amount, overdue days, weight, total number of claims customers, etc., one or more of these conditions are used to create a claims routing model. The model can then be used to route and filter eligible insurance companies to customers who meet the claims criteria.

[0040] API Interaction Module: After filtering out insurance companies, the module interacts with the insurance company's API interface to obtain data information stored in the parameter table to obtain claim approval. If the claim is rejected, the module can continue to route alternative claim companies.

[0041] Claims result judgment module: Determines whether the claim is successful based on the response result of the insurance company's API interface, and interacts with the accounting microservice after success;

[0042] On-balance sheet business settlement module: The financial microservice uniformly processes the early settlement of overdue on-balance sheet business of borrowers, and generates a set of accounting documents and related reports for early settlement;

[0043] Off-balance sheet accounting module: The loan microservice copies the original loan documents of the borrower for off-balance sheet accounting, and provides customers with functions such as checking accounts, repayment, and collection.

[0044] Based on the above technical solution, the claims system connects to each loan product system according to the database address, account number, and password of each loan product system. It assembles SQL statements according to the data mapping relationship. When the corresponding data table or field in the corresponding data table cannot be found in the database of the loan product system, it executes the assembled SQL statement to automatically update the data.

[0045] Based on the above technical solution, before executing the automatic update operation using assembled SQL statements, it is necessary to establish mapping matching data in table L of the databases of various loan systems:

[0046] In each loan system, a parameter table name identifier field is set in table L. The value of the parameter table name identifier field is set to the actual table name of the parameter table in the database.

[0047] In each loan system, set one or more mapping matching data in table L. In the mapping matching data, except for the input parameter table name identifier field which is the actual table name of the input parameter table, the values ​​of other fields in table L are the field names that need to be mapped to the input parameter table.

[0048] Based on the above technical solution, perform an automatic update operation by assembling SQL statements:

[0049] After the claims system connects to the databases of various loan product systems, it uses the actual table name of the input parameter table as the value to query the databases of the corresponding loan product systems to find the table name L containing the "actual table name of the input parameter table".

[0050] Then, each field name in the input parameter table is used as a query condition, and the actual table name of the input parameter table is used as a constraint condition to query the corresponding field name N in table L, thus obtaining the mapping relationship between each field in the input parameter table and each field in table L in each loan system.

[0051] The SQL execution statement is assembled based on the mapping relationship. The data in table L is updated or inserted into the input parameter table to obtain the data that needs to be claimed from the insurance company due to the borrower's overdue payment. The SQL execution statement is saved locally for easy access later.

[0052] Based on the above technical solution, and considering the different API interaction requirements of various insurance companies, the loan microservice assembles XML / TCP messages through a database, while the open platform assembles external JSON messages by iteratively parsing the XML messages. The open platform then points to the API interfaces of different claims companies based on the messageType and messageCode values ​​in the API request header.

[0053] Because the present invention adopts the above-described technical solution, it has the following beneficial effects:

[0054] 1. This invention eliminates the need to create configuration tables. Simply add a row of mapping data to the corresponding data tables of each loan system. The claims system automatically establishes a mapping relationship between the input parameter table and each field in the data tables of each loan product system based on this mapping data. When a new field is added to the input parameter table, a new field is added to the data table of each loan product system, and the value of the newly added field in one or more corresponding mapping data rows in the table is set to the field name of the newly added field in the input parameter table. No manual coding to modify the field mapping relationships is required.

[0055] 2. Similarly, if you need to change the mapping relationship of fields in the tables of various loan product systems, you can directly modify the value of the field in one or more mapping matching data in the table. Attached Figure Description

[0056] Figure 1 System framework diagram; Detailed Implementation

[0057] The specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples. The following examples are for illustrative purposes only and are not intended to limit the scope of the invention.

[0058] This invention provides a method for constructing a standardized claims model, specifically including the following steps:

[0059] Step 1: The claims system connects to each loan product system based on the database address, account, and password. It assembles SQL execution statements according to the data mapping relationship, assigns the values ​​of the corresponding fields in the corresponding tables of each loan system's database to the corresponding fields in the input parameter table of the claims system's database, and obtains the data that needs to be claimed from the insurance company due to the borrower's overdue payment.

[0060] Step 2: Based on the data information stored in the input parameter table, such as one or more of the following conditions: business type, channel type, claims mode, claims amount, overdue days, weight, and total number of claims customers, create a claims routing model. The model can then be used to route and filter eligible insurance companies to customers who meet the claims criteria.

[0061] Step 3: After filtering out the insurance companies, interact with the data information stored in the API parameter table of the insurance companies to obtain claim approval. If rejected, you can continue to route alternative claim companies.

[0062] Step 4: Determine whether the claim was successful based on the response from the insurance company's API interface. If successful, interact with the accounting microservice.

[0063] Step 5: The financial microservices uniformly process the early settlement of overdue on-balance-sheet transactions for borrowers, generating a set of accounting documents and related reports for early settlement;

[0064] Step 6: The loan microservice copies the borrower's original loan records for off-balance-sheet accounting, and provides customers with functions such as checking accounts, making repayments, and collecting debts.

[0065] Based on the above technical solution, the claims system connects to each loan product system according to the database address, account number, and password of each loan product system. It assembles SQL statements according to the data mapping relationship. When the corresponding data table or field in the corresponding data table cannot be found in the database of the loan product system, it executes the assembled SQL statement to automatically update the data.

[0066] Based on the above technical solution, before executing the automatic update operation using assembled SQL statements, it is necessary to establish mapping matching data in table L of the databases of various loan systems. The steps include:

[0067] Step a: In each loan system, a parameter table name identifier field is set in table L. The value of the parameter table name identifier field is set to the actual table name of the parameter table in the database.

[0068] Step b: Set one or more mapping matching data in table L of each loan system. In the mapping matching data, except for the input parameter table name identifier field which is the actual table name of the input parameter table, the values ​​of other fields in table L are the field names that need to be mapped to the input parameter table.

[0069] Based on the above technical solution, perform an automatic update operation by assembling SQL statements:

[0070] Step c: After the claims system connects to the database of each loan product system, it uses the actual table name of the input parameter table as the value to query the database of the corresponding loan product system to find the table name L containing the "actual table name of the input parameter table".

[0071] Step d: Then, take each field name in the input parameter table as a query condition and "the actual table name of the input parameter table" as a constraint condition to query the corresponding field name N in table L for each field name, and obtain the mapping relationship between each field in the input parameter table and each field in table L in each loan system.

[0072] Step e: Assemble the SQL execution statement according to the mapping relationship, update or insert the data in table L into the input parameter table, and obtain the data that needs to be claimed from the insurance company due to the borrower's overdue payment. The SQL execution statement is saved locally for easy access later.

[0073] Based on the above technical solution, in step 3, according to the different API interaction requirements of different insurance companies, the loan microservice completes the assembly of XML / TCP messages through the database, and the open platform completes the concatenation of external JSON messages by parses the XML messages in a loop. The open platform points to the API interface of different claims companies according to the messageType and messageCode values ​​in the header file of the API request.

[0074] The present invention also provides an apparatus for constructing a standardized claims model, specifically including the following steps:

[0075] The claims data acquisition module and claims system connect to each loan product system based on the database address, account, and password of each loan product system. Based on the data mapping relationship, they assemble SQL execution statements and assign the values ​​of the corresponding fields in the corresponding tables of each loan system's database to the corresponding fields in the input parameter table of the claims system's database to obtain the data that needs to be claimed from the insurance company due to the borrower's overdue payment.

[0076] Insurance Company Matching Module: Based on the data information stored in the input parameter table, such as business type, channel type, claims mode, claims amount, overdue days, weight, total number of claims customers, etc., one or more of these conditions are used to create a claims routing model. The model can then be used to route and filter eligible insurance companies to customers who meet the claims criteria.

[0077] API Interaction Module: After filtering out insurance companies, the module interacts with the insurance company's API interface to obtain data information stored in the parameter table to obtain claim approval. If the claim is rejected, the module can continue to route alternative claim companies.

[0078] Claims result judgment module: Determines whether the claim is successful based on the response result of the insurance company's API interface, and interacts with the accounting microservice after success;

[0079] On-balance sheet business settlement module: The financial microservice uniformly processes the early settlement of overdue on-balance sheet business of borrowers, and generates a set of accounting documents and related reports for early settlement;

[0080] Off-balance sheet accounting module: The loan microservice copies the original loan documents of the borrower for off-balance sheet accounting, and provides customers with functions such as checking accounts, repayment, and collection.

[0081] Based on the above technical solution, the claims system connects to each loan product system according to the database address, account number, and password of each loan product system. It assembles SQL statements according to the data mapping relationship. When the corresponding data table or field in the corresponding data table cannot be found in the database of the loan product system, it executes the assembled SQL statement to automatically update the data.

[0082] Based on the above technical solution, before executing the automatic update operation using assembled SQL statements, it is necessary to establish mapping matching data in table L of the databases of various loan systems:

[0083] In each loan system, a parameter table name identifier field is set in table L. The value of the parameter table name identifier field is set to the actual table name of the parameter table in the database.

[0084] In each loan system, set one or more mapping matching data in table L. In the mapping matching data, except for the input parameter table name identifier field which is the actual table name of the input parameter table, the values ​​of other fields in table L are the field names that need to be mapped to the input parameter table.

[0085] Based on the above technical solution, perform an automatic update operation by assembling SQL statements:

[0086] After the claims system connects to the databases of various loan product systems, it uses the actual table name of the input parameter table as the value to query the databases of the corresponding loan product systems to find the table name L containing the "actual table name of the input parameter table".

[0087] Then, each field name in the input parameter table is used as a query condition, and the actual table name of the input parameter table is used as a constraint condition to query the corresponding field name N in table L, thus obtaining the mapping relationship between each field in the input parameter table and each field in table L in each loan system.

[0088] The SQL execution statement is assembled based on the mapping relationship. The data in table L is updated or inserted into the input parameter table to obtain the data that needs to be claimed from the insurance company due to the borrower's overdue payment. The SQL execution statement is saved locally for easy access later.

[0089] Based on the above technical solution, and considering the different API interaction requirements of various insurance companies, the loan microservice assembles XML / TCP messages through a database, while the open platform assembles external JSON messages by iteratively parsing the XML messages. The open platform then points to the API interfaces of different claims companies based on the messageType and messageCode values ​​in the API request header.

Claims

1. A method of building a claim standardization model, the method comprising: Specifically comprising the following steps: Step 1, the claim system connects each loan product system according to the database address, account number and password of each loan product system, assembles a SQL execution statement according to the data mapping relationship, assigns the values of the corresponding fields of the corresponding table in the database of each loan product system to the corresponding fields of the input parameter table in the database of the claim system, obtains the data that needs to be claimed to the insurance company due to the overdue of the lender, and executes the automatic updating operation of the assembled SQL statement when the corresponding data table or the field in the corresponding data table cannot be found in the loan product system database. Step 2: According to the data information stored in the input parameter table, create a claim routing model according to one or more conditions of business variety, channel type, claim mode, claim amount, overdue days, weight, and total number of claim customers, and filter out the insurance companies that meet the conditions according to the model. Step 3: After screening out the insurance companies, interact with the API interface of the insurance company to obtain the claim permission, and if it is refused, continue to route the alternative insurance company. Step 4: Determine whether the claim is successful according to the response result of the insurance company API interface, and interact with the account micro service after success. Step 5: The account micro service uniformly processes the early settlement of the overdue table business of the lender, generates a set of early settlement account files and related reports. Step 6: The loan micro service copies a set of original loan account books of the lender to do off-balance sheet accounting, and meets the functions of account checking, repayment and collection. Before executing the automatic updating operation of the assembled SQL statement, mapping matching data needs to be set in the table L in the database of each loan product system, and the steps include: Step a, setting an input parameter table name identification field in the table L of each loan product system, and setting the value of the input parameter table name identification field as the actual table name of the input parameter table in the database; Step b, setting one or more mapping matching data in the table L of each loan product system, wherein, in addition to the value of the input parameter table name identification field being the actual table name of the input parameter table, the values of other fields in the table L are the field names that need to be mapped to the input parameter table; Step c, the claim system connects to the database of each loan product system, and then queries the table name L of the table containing the actual table name of the input parameter table from the database of each loan product system according to the actual table name of the input parameter table as the value; Step d, then query the corresponding field name N of each field name in the table L from the table L by taking each field name in the input parameter table as a query condition and taking the actual table name of the input parameter table as a constraint condition, to obtain the mapping relationship between each field of the input parameter table and each field in the table L in each loan product system; Step e, assemble a SQL execution statement according to the mapping relationship, update or insert the data in the table L to the input parameter table, obtain the data that needs to be claimed to the insurance company due to the overdue of the lender, and save the SQL execution statement locally for subsequent direct calling. ​ 2. The method of claim 1, wherein, In step 3, according to different API interaction requirements of different insurance companies, the loan microservice assembles xml / tcp messages through the database, and the open platform parses the xml messages to complete the splicing of the external json message. The open platform points to the API interface of different insurance companies according to the messageType and messageCode values in the API request header file.

3. An apparatus for building a claim standardization model, the apparatus comprising: Specifically, the following modules are included: A data acquisition module for claim settlement: The claim settlement system connects to each loan product system according to the database address, account, and password of each loan product system, assembles SQL execution statements according to the data mapping relationship, assigns the values of the corresponding fields of the corresponding tables in the database of each loan product system to the corresponding fields of the input parameter table in the database of the claim settlement system, obtains the data that needs to be claimed from the insurance company due to the overdue of the loaner, and updates the operation automatically when the assembled SQL statement cannot find the corresponding data table or the fields in the corresponding data table in the loan product system database. An insurance company matching module: According to the data information stored in the input parameter table, a claim settlement routing model is created according to one or more conditions such as business variety, channel type, claim settlement mode, claim settlement amount, overdue days, weight, and total number of claim settlement clients, and the insurance companies that meet the conditions are screened out according to the model. An API interaction module: After screening out the insurance companies, the data information stored in the input parameter table is interacted with the API interface of the insurance company to obtain claim settlement permission, and if it is refused, the alternative insurance company is continued to be routed. A claim settlement result judgment module: According to the response result of the insurance company API interface, it is judged whether the claim settlement is successful, and after the success, it is interacted with the account microservice. A table business settlement module: The account microservice uniformly handles the early settlement of the table business of the loaner, generates a set of early settlement account files and related reports. An off-table accounting module: The loan microservice copies a set of original loan documents of the loaner to do off-table accounting, and meets the functions of account checking, repayment, and collection. Before performing the automatic update operation of the assembled SQL statement, the mapping matching data needs to be set in the table L in the database of each loan product system: In the table L of each loan product system, there is an input parameter table name identification field, and the value of the input parameter table name identification field is set to the actual table name of the input parameter table in the database. In the table L of each loan product system, one or more mapping matching data are set, and in the mapping matching data, in addition to the input parameter table name identification field value being the actual table name of the input parameter table, the values of other fields in the table L are the field names that need to be mapped to the input parameter table. Performing the automatic update operation of the assembled SQL statement: After the claim settlement system connects to the database of each loan product system, the actual table name of the input parameter table is used as a value to query the table name L of the table containing the actual table name of the input parameter table in the database of each loan product system. Then, each field name in the input parameter table is taken as a query condition, and the actual table name of the input parameter table is taken as a value as a constraint condition to query each field name N corresponding to each field name in table L from table L, so as to obtain a mapping relationship between each field of the input parameter table and each field in table L in each loan product system; According to the mapping relationship, a SQL execution statement is assembled, data in table L is updated or inserted into the input parameter table, and data needing to be compensated to the insurance company due to the overdue of the lender is obtained, and the SQL execution statement is saved locally, so that it is convenient for subsequent direct calling.

4. The device for building a claim standardization model according to claim 3, characterized in that, According to different API interaction requirements of different insurance companies, the loan micro service completes xml / tcp message assembly through a database, and the open platform completes external json message splicing through cyclic xml message analysis. The open platform points to API interfaces of different insurance companies according to messageType and messageCode values in a header file of an API request.

Images