Insurance data review method, device, computer equipment and storage medium

Abstract

The present application relates to an insurance data review method, device, computer equipment and storage medium. The method comprises: receiving insurance data uploaded by a first terminal, the insurance data carrying key fields; using the key fields to filter multiple rule packages, and filtering out rule files corresponding to the insurance data from the rule packages; determining the execution order of the filtered multiple rule files according to the key fields; loading the filtered multiple rule files according to the execution order, and reviewing the insurance data according to the loaded rule files. The use of this method can improve the review efficiency of insurance policy data.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an insurance data review method, device, computer equipment and storage medium. Background Art

[0002] With the development of insurance business, in order to ensure the accuracy of automatic underwriting, it is usually necessary to execute hundreds or even thousands of underwriting rules compiled into different codes on the policies when reviewing policy data.

[0003] However, in the traditional way, all underwriting rules are generally uploaded to the rule engine in a disorderly manner, and the execution of the rules is controlled by the specific writing of the LHS (antecedent or left-hand-side) of the business rules. In this way, all underwriting rules need to be loaded every time the underwriting rules are executed, resulting in low underwriting efficiency. Summary of the invention

[0004] Based on this, it is necessary to provide an insurance data review method, device, computer equipment and storage medium that can improve underwriting efficiency in response to the above technical problems.

[0005] A method for reviewing insurance data, the method comprising:

[0006] Receiving insurance data uploaded by the first terminal, wherein the insurance data carries a key field;

[0007] Filtering multiple rule packages using the key fields, and filtering out rule files corresponding to the insurance data from the rule packages;

[0008] Determine the execution order of the multiple rule files selected according to the key fields;

[0009] The multiple rule files selected are loaded according to the execution order, and the insurance data is reviewed according to the loaded rule files.

[0010] In one embodiment, determining the execution order of the plurality of rule files selected according to the key field comprises:

[0011] Reading a configuration file, wherein the configuration file records the priority levels corresponding to the key fields;

[0012] The execution order of the rule files corresponding to the key fields is determined according to the priority levels corresponding to the key fields.

[0013] In one embodiment, the method further comprises:

[0014] Receiving a rule file update request uploaded by the second terminal, wherein the update request carries a key field and an updated rule file;

[0015] Obtain the rule file before updating according to the key field;

[0016] The updated rule file overwrites the rule file before updating.

[0017] In one embodiment, before the method uses the key field to filter multiple rule files, it also includes:

[0018] Determining whether the amount of insurance data reaches a preset threshold;

[0019] If yes, obtain key fields of multiple insurance data;

[0020] The insurance data is classified and processed according to the key fields.

[0021] In one embodiment, after classifying the insurance data according to the key fields, the method further includes:

[0022] Generate a workflow to be reviewed based on the insurance data;

[0023] Obtaining the current date and a pre-stored date table, wherein the date table carries multiple date identifiers;

[0024] Obtaining a date identifier corresponding to the current date according to the date table;

[0025] The workflow to be reviewed is captured according to the date identifier.

[0026] In one embodiment, the receiving of the insurance data uploaded by the first terminal includes:

[0027] Receiving a rule file uploaded by the first terminal, wherein the rule file carries a file identifier;

[0028] The rule files are classified and packaged according to the file identifiers to obtain multiple rule packages.

[0029] An insurance data review device, the device comprising:

[0030] A receiving module, used for receiving the insurance data uploaded by the first terminal, wherein the insurance data includes key fields;

[0031] A screening module, used to screen multiple rule packages using the key fields, and screen out rule files corresponding to the insurance data from the rule packages;

[0032] A determination module, used to determine the execution order of the multiple rule files selected according to the key fields;

[0033] The audit module is used to load the multiple rule files selected according to the execution order, and use the loaded rule files to audit the insurance data.

[0034] In one of the embodiments, the determination module is further used to read a configuration file, in which priority levels corresponding to key fields are recorded; and the execution order of the rule files corresponding to the key fields is determined according to the priority levels corresponding to the key fields.

[0035] A computer device comprises a memory and a processor, wherein the memory stores a computer program, and the processor implements any of the above-mentioned insurance data review methods when executing the computer program.

[0036] A computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements any one of the insurance data review methods.

[0037] In the above-mentioned insurance data review method, device, computer equipment and storage medium, the server first receives the insurance data uploaded by the first terminal, and the insurance data carries a key field. The key field is used to screen multiple rule packages, and the rule files corresponding to the insurance data are screened out from the rule packages. The execution order of the multiple rule files screened out is determined according to the key field, and the multiple rule files screened out are loaded according to the execution order, and the insurance data is reviewed according to the loaded rule files. The above-mentioned method uses the key field to screen out the rule files corresponding to it, and reviews the insurance policy data according to the execution order, thereby improving the review efficiency of the insurance policy data. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 An application environment diagram of an insurance data review method in an embodiment;

[0039] Figure 2 A schematic diagram of a process of an insurance data review method in one embodiment;

[0040] Figure 3 A schematic diagram of the execution order of a rule file in an embodiment;

[0041] Figure 4 A schematic diagram of a flow chart of the steps of screening multiple rule files according to key fields in one embodiment;

[0042] Figure 5 A flowchart of the steps before screening multiple rule files using key fields in one embodiment;

[0043] Figure 6 It is a structural block diagram of an insurance data review method device in one embodiment;

[0044] Figure 7 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0046] The insurance data review method provided in this application can be applied to Figure 1 In the application environment shown. Among them, the first terminal 102 and the second terminal 104 communicate with the server 106 through the network. Among them, the first terminal 102 and the second terminal 104 can be, but not limited to, various personal computers, laptops, smart phones, tablet computers and portable wearable devices, and the server 106 can be implemented by an independent server or a server cluster composed of multiple servers. The server 106 receives the insurance data uploaded by the first terminal 102, and the insurance data carries a key field. The server 106 uses the key field to filter multiple rule packages, and filters out the rule files corresponding to the insurance data from the rule package. The server 106 determines the execution order of the multiple rule files filtered out according to the key field, and loads the multiple rule files filtered out according to the execution order, and reviews the insurance data according to the loaded rule files. In addition, when the server 106 receives the rule file update request uploaded by the second terminal 104, the rule file is updated according to the key field and the updated rule file carried in the update request.

[0047] In one embodiment, Figure 2 As shown, a method for reviewing insurance data is provided, which is applied to Figure 1 The server in the example is used to illustrate the following steps:

[0048] S202, receiving insurance data uploaded by the first terminal, where the insurance data carries key fields.

[0049] S204, using key fields to filter multiple rule packages, and filter out rule files corresponding to the insurance data from the rule packages.

[0050] The insurance data includes the personal information of the insured user, the insurance information and the key fields corresponding to the insurance information, and the key fields include the file identifier and the data identifier. The rule package refers to a compressed package or folder for storing multiple rule files. The rule file refers to the code rules pre-written in the terminal for reviewing the insurance data. When the terminal writes different rule files, different file identifiers are added to different rule files, and the file identifier is used to identify which part of the insurance data the rule file is used to review. The completed rule file is sent to the server. When the server receives the rule file uploaded by the terminal, the file identifier of the rule file is obtained, and the rule file is classified and stored according to the file identifier. Different categories of rule files are packaged and put into different rule packages. When the server receives the insurance data uploaded by the first terminal, the insurance data carries the key fields. Among them, the key fields include the file identifier and the data identifier. The server uses the file identifier to determine the rule package where the rule file corresponding to the insurance data is located, and then uses the data identifier to filter the rule files in the rule package, and filters out the rule files corresponding to the insurance data from the multiple rule files in the rule package.

[0051] For example, the file identifier may include: general rule file, channel rule file, platform rule file, and product rule file. That is, the classification of rule files according to the above file identifiers can be divided into four types: general rule package, channel rule package, platform rule package, and product rule package. Each rule package stores a corresponding rule file. The general rule package stores a type of general rules and a type of general rules, the channel rule package stores online sales rules and telemarketing rules, the platform rule package stores Jin Guanjia rules, Taobao rules, Lufax rules, and Jingdong rules, and the product rule package stores 2000 product rules, 2002 product rules, 2004 product rules, and 2006 product rules. The above rule packages and the corresponding rule types stored in the rule packages are not limited to the above types, and can be set according to actual conditions. That is to say, the data identifiers in the key fields include but are not limited to the following: type one general, type two general, online sales, telemarketing, Taobao, Lufax, Jin Guanjia, Jingdong, 2000, 2002, 2004, and 2006. When the file identifier in the key field of the insurance data uploaded by the first terminal received by the server is a channel rule file, and the data identifier is telemarketing, the server screens all rule packages according to the channel rule file and obtains the channel rule package corresponding to the file identifier. Then, the data identifier telemarketing is used to screen out the telemarketing rules corresponding to the data identifier telemarketing from the channel rule package.

[0052] S206, determining the execution order of the multiple rule files selected according to the key fields.

[0053] S208, loading the selected multiple rule files according to the execution order, and reviewing the insurance data according to the loaded rule files.

[0054] In one embodiment, determining the execution order of the multiple rule files selected according to the key fields includes: reading a configuration file that records the priority levels corresponding to the key fields; and determining the execution order of the rule files corresponding to the key fields according to the priority levels corresponding to the keywords.

[0055] The server pre-sets a configuration file, sets the corresponding priority level for the key fields of the insurance data, and records the priority levels corresponding to multiple key fields in the configuration file. After the server screens out the rule file corresponding to the policy data, it reads the configuration file and obtains the corresponding execution priority level according to the key fields corresponding to the rule file. Among them, since the key fields include file identifiers and data identifiers, and the file identifiers and data identifiers are corresponding, the configuration file can only record the priority level corresponding to the file identifier or the priority level corresponding to the data identifier. The priority level of the rule file can be determined by the priority level of any one of the file identifier and the data identifier. For example, if the configuration file sets the execution priority level of the file identifier, if the execution priority level of the general rule file is set to the first level, then the execution priority level of the general rule package is the first level, and the execution priority levels of the first class of general rules and the second class of general rules stored in the general rule package are all the first level. If the configuration file sets the execution priority level of the data identifier, if the first class of general rules is set to the first level, then the execution priority level of the general rule package corresponding to the first class of general rules is the first level, and the execution priority levels of the rule files stored in the general rule package are all the first level.

[0056] The execution order is sorted according to the priority level. The rule files with higher priority levels are executed first, and the rule files with lower priority levels are executed later. The set priority levels can be: first level, second level, third level, fourth level, and so on. And the level size relationship can be: the first level is higher than the second level, higher than the third level, higher than the fourth level, or the fourth level is higher than the third level, higher than the second level, higher than the first level. It can be set according to the actual situation. If the first level is higher than the second level, higher than the third level, higher than the fourth level, for example: the rule file with the first priority level is loaded and executed first, and then the rule file with the second priority level is loaded and executed, followed by the rule file with the third priority level, and finally the rule file with the fourth priority level is loaded and executed.

[0057] For example, Figure 3As shown, a schematic diagram of the execution sequence of rule files is provided. When the key fields carried by the insurance data received by the server include: the file identifier includes a general rule file, a channel rule file, a platform rule file and a product rule file, and the data identifier includes a general rule package, online sales, Golden Butler, 2000 and 2006. The server first determines that the rule packages involved in the insurance data include a general rule package, a channel rule package, a platform rule package and a product rule package through the file identifier, and then uses the data identifiers of a general rule, online sales, Taobao, 2000 and 2006 to filter out a general rule, online sales rules, Taobao rules, 2000 product rules and 2006 product rules from the general rule package, channel rule package, platform rule package and product rule package respectively. The server reads the configuration file, determines that a general rule is the first level, the online sales rule is the second level, the Golden Butler rule is the third level, the 2000 product rule and the 2006 product rule are the fourth level according to the priority level corresponding to the key fields recorded in the configuration file, and then loads the rule files according to the priority level to review the insurance data. Among them, the fourth-level product rule files include 2002 product rules and 2006 product rules. Since the same user may insure multiple insurance types, when the server selects multiple product rule files from the product rule package according to the key fields of the user's insurance data, it is possible that multiple product rule files are selected from the product rule package. Therefore, when multiple product rule files are selected according to the insurance data, the user's insurance information is obtained, and the primary and secondary relationship of the insurance types insured by the user is determined according to the insurance information, and the primary insurance products and secondary insurance products are selected, and the rule files of the primary insurance products are executed first. For example, if the 2002 product is the primary insurance product and the 2006 product is the secondary insurance product, the loading order is: first load a class of general rules to review the insurance data, then load the online sales rules to review the insurance data, then load the Taobao rules to review the insurance data, and finally load the 2002 product rule file to review the insurance data, and then load the 2006 product rule file to review the insurance data.

[0058] In the above-mentioned insurance data review method, the server first receives the insurance data uploaded by the first terminal, and the insurance data includes key fields. The key fields are used to screen multiple rule files, and the rule files corresponding to the insurance data are screened out. The execution order of the multiple rule files screened out is determined according to the key fields, and the multiple rule files screened out are loaded according to the execution order, and the insurance data is reviewed using the loaded rule files. The above-mentioned method uses the key fields to screen out the rule files corresponding to them, and reviews the insurance policy data according to the execution order, thereby improving the review efficiency of the insurance policy data.

[0059] In one embodiment, Figure 4 As shown, a rule file updating method is provided, comprising the following steps:

[0060] S402, receiving a rule file update request uploaded by the second terminal, where the update request carries a key field and an updated rule file.

[0061] S404, obtaining the rule file before updating according to the key field.

[0062] S406: Overwrite the rule file before updating with the updated rule file.

[0063] The rule file update request refers to an instruction for requesting to update the rule file sent by the business personnel to the server by operating the second terminal. When the rule file has an update requirement, the business personnel can rewrite the updated rule file in advance at the second terminal or first obtain the updated rule file from the server according to the key field of the rule file, and then supplement the updated rule file according to the requirement. If the updated rule file is rewritten, the rule file update request is sent to the server through the second terminal, and the key fields of the updated rule file and the updated old rule file are carried in the update file request. After the server receives the rule file update request uploaded by the second terminal, it screens multiple rule packages according to the file identifier in the key field, and screens out the rule package corresponding to the file identifier. According to the data identifier in the key field, the old rule file corresponding to the data identifier is screened from the rule package, that is, there is no rule file before the update. After obtaining the old rule file, the updated rule file is overwritten by the old rule file, that is, the updated rule file overwrites the rule file before the update. Among them, overwriting is to completely delete the rule file before the update, and store the updated rule file in the corresponding rule package to ensure the uniqueness of the rule file. If the rule file is an updated rule file obtained from the server, after the updated rule file is supplemented, the second terminal sends an update request to the server, and the update request carries the updated rule file. The server stores the updated rule file according to the original storage path.

[0064] In one embodiment, Figure 5 As shown, before using key fields to filter multiple rule files, the following steps are also included:

[0065] S502, determining whether the amount of insurance data reaches a preset threshold.

[0066] S504: If yes, obtain key fields of multiple insurance data.

[0067] S506, classify and process the insurance data according to key fields.

[0068] After the server receives the insurance data uploaded by the first terminal, it can screen and review the insurance data in real time, or store the insurance data for batch review, which can be set according to actual needs. When the server is set to review the insurance data in batches, the server regularly scans the amount of insurance data stored, and when the amount of insurance data reaches a preset threshold, multiple key fields of insurance data are obtained. Among them, the key fields corresponding to a specified number of insurance data can be obtained, and the key fields of all insurance data that have not yet been underwritten can also be obtained when the amount of insurance data reaches the threshold. The insurance data is classified according to the key fields, and the insurance data with the same key fields are classified into the same category. The key fields corresponding to the classified insurance data are used to screen the rule files, and the execution order of the rule files is determined according to the key fields, and multiple insurance data are reviewed at the same time according to the execution order. For example, when there are 100 users' insurance data files identified as general rule files, channel rule files, platform rule files and product rule files, and the data are identified as Class II, online sales, Taobao and 2002 products. The insurance data of the 100 users are packaged into one category, and after the rule file is determined according to the same key field, the insurance data of the 100 users are uniformly reviewed. In this implementation, when the insurance data reaches the threshold, the insurance data is classified according to the key field and the data is uniformly reviewed according to the key field. The efficiency of the review work is guaranteed by batch review of the policy data, and resources are saved.

[0069] In one embodiment, after classifying the insurance data according to key fields, it also includes: generating a workflow to be reviewed based on the insurance data; obtaining the current date and a pre-stored date table, wherein the date table carries multiple date identifiers; obtaining the date identifier corresponding to the current date according to the date table; and capturing the workflow to be reviewed according to the date identifier.

[0070] After the server classifies the insurance data according to the key fields, it generates a workflow to be reviewed according to each type of insurance data, indicating that the insurance data of this category has not been reviewed yet. The server regularly obtains the current date and the pre-stored date table, and each date in the date table carries a date identifier. The date identifier of the current date is obtained by matching the date table with the current date. Among them, the date identifier includes working days and non-working days. The date identifiers from Monday to Friday in the date table can be pre-set as working days, and the date identifiers from Saturday to Sunday can be pre-set as non-working days. If the date identifier of the current date is a working day, the server does not capture the workflow to be reviewed. If the current date is a non-working day, the server randomly captures the workflow to be reviewed. After capturing the workflow to be reviewed, the insurance data corresponding to the workflow to be reviewed is obtained, the rule file is screened according to the key fields of the insurance data, and the execution order of the rule file is determined by the key fields. The rule file is loaded in sequence to review the insurance data corresponding to the workflow to be reviewed. In this embodiment, insurance data review is performed by presetting working day and non-working date identifiers, and non-working days are used to perform insurance review data work, so that resources are not occupied on working days for review work, and it is ensured that there are sufficient resources for data review work on non-working days.

[0071] In one embodiment, before receiving the insurance data uploaded by the first terminal, the method includes: receiving a rule file uploaded by the first terminal, the rule file carrying a file identifier; and classifying and packaging the rule file according to the file identifier to obtain multiple rule packages.

[0072] A rule file refers to a code file used to load and execute the review of insurance data. Before the server formally receives the insurance data for review, the rule file written by the business personnel is uploaded to the server for storage in advance. When the server performs the insurance data review, the corresponding rule file can be directly called. In addition, after the server receives the rule file uploaded by the business personnel through the first terminal, the rule file is classified and processed by the file identifier corresponding to the rule file, and the rule files of the same category are packaged and stored in a rule package to obtain multiple rule packages. Among them, when the business personnel write the rule file, different file identifiers are added to the rule file according to the different business types. The insurance information when the user takes out insurance generally includes the general type of the insurance policy insured by the user, the channel for the user to take out insurance, the platform for the user to take out insurance, and the insurance product insured by the user, etc. According to the user's insurance information, the rule file that the business personnel needs to write can be determined, that is, the rule file used to review the insurance data generally includes a rule file for reviewing the general type of insurance policy, a rule file for reviewing the insurance channel, a rule file for reviewing the insurance platform, and a rule file for reviewing the insurance product. Therefore, when business personnel write a rule file for reviewing insurance policy types, the file identifier added is a general rule file; when writing a rule file for reviewing insurance channels, the file identifier added is a channel rule file; when writing a rule file for reviewing insurance platforms, the file identifier added is a platform rule file; and when writing a rule file for reviewing insurance products, the file identifier added is a product rule file.

[0073] In one embodiment, the rule package includes: a general rule package, a channel rule package, a platform rule package and a product rule package.

[0074] After receiving the rule file uploaded by the business personnel through the first terminal, the server classifies and packages the rule file according to the file identifier carried by the rule file, and obtains multiple rule packages, including: general rule package, channel rule package, platform rule package and product rule package. For example, insurance policy types are generally divided into one general type and two general types. When writing one general rule and two general rules, the business personnel add the file identifier of the general rule file to the rule file. The server packages the one general rule and the two general rules into the general rule package according to the general rule file identifier. Similarly, insurance policy channels are divided into online sales and telemarketing. When writing online sales rules and telemarketing rules, the business personnel add the file identifier of the channel rule file to the rule file. The server packages the online sales rules and telemarketing rules into the channel rule package according to the channel rule file identifier. Insurance platforms generally include JD.com, Lufax, Taobao and Golden Butler. When business personnel compile JD.com platform rules, Lufax platform rules, Taobao platform rules and Golden Butler platform rules, they add the file identifier of the platform rule file to the above rule files. The server packages the JD.com platform rules, Lufax platform rules, Taobao platform rules and Golden Butler platform rules into the platform rule package according to the platform rule file identifier.

[0075] In this embodiment, traditionally, all rule files are usually stored in the server. When the server conducts insurance data review, it needs to load all rule files and select the corresponding rule file for review. However, this embodiment adds different file identifiers according to different rule files, and the server classifies the rule files according to the file identifiers. When the server conducts policy data review, it can obtain the corresponding rule package and rule file without loading all rule files, thereby improving the efficiency of the review work. It should be understood that although Figure 2 , 4 The steps in the flowcharts of and 5 are shown in sequence as indicated by arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2 , 4 At least part of the steps in 5 may include multiple sub-steps or multiple stages. These sub-steps or stages do not necessarily have to be executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages does not necessarily have to be sequentially, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0076] In one embodiment, Figure 6As shown, an insurance data review device is provided, including: a receiving module 602, a screening module 604, a determination module 606 and a review module 608, wherein:

[0077] The receiving module 602 is used to receive the insurance data uploaded by the first terminal, where the insurance data carries a key field;

[0078] The screening module 604 is used to screen multiple rule packages using key fields, and screen out rule files corresponding to the insurance data from the rule packages.

[0079] The determination module 606 is used to determine the execution order of the multiple rule files selected according to the key fields.

[0080] The audit module 608 is used to load the multiple filtered rule files according to the execution order, and audit the insurance data according to the loaded rule files.

[0081] In one embodiment, the determination module 606 is further used to read a configuration file, in which the priority levels corresponding to the key fields are recorded; and the execution order of the rule files corresponding to the key fields is determined according to the priority levels corresponding to the keywords.

[0082] In one embodiment, the insurance data review device also includes an update module for receiving a rule file update request uploaded by the second terminal, the update request carrying key fields and an updated rule file; obtaining the rule file before the update according to the key fields; and overwriting the rule file before the update according to the updated rule file.

[0083] In one embodiment, the receiving module 602 is also used to determine whether the amount of insurance data reaches a preset threshold; if so, obtain key fields of multiple insurance data; and classify the insurance data according to the key fields.

[0084] In one embodiment, the receiving module 602 is also used to generate a workflow to be reviewed based on the insurance data; obtain the current date and a pre-stored date table, the date table carrying multiple date identifiers; obtain the date identifier corresponding to the current date based on the date table; and capture the workflow to be reviewed based on the date identifier.

[0085] In one embodiment, the receiving module 602 is further configured to receive a rule file uploaded by the first terminal, the rule file carrying a file identifier; and classify and package the rule file according to the file identifier to obtain multiple rule packages.

[0086] The specific definition of the insurance data review device can be found in the definition of the insurance data review method above, which will not be repeated here. Each module in the above insurance data review device can be implemented in whole or in part by software, hardware and a combination thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0087] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 7 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store insurance data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for reviewing insurance data is implemented.

[0088] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0089] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0090] Receiving insurance data uploaded by the first terminal, the insurance data carrying key fields;

[0091] A plurality of rule packages are screened using key fields, and rule files corresponding to the insurance data are screened out from the rule packages.

[0092] The execution order of the multiple rule files selected is determined according to the key fields.

[0093] The multiple filtered rule files are loaded according to the execution order, and the insurance data is reviewed according to the loaded rule files.

[0094] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0095] Read the configuration file, which records the priority levels corresponding to the key fields;

[0096] The execution order of the rule files corresponding to the key fields is determined according to the priority levels corresponding to the key fields.

[0097] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0098] Receiving a rule file update request uploaded by the second terminal, the update request carrying key fields and an updated rule file;

[0099] Get the rule file before updating based on the key fields;

[0100] The updated rule file overwrites the rule file before updating.

[0101] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0102] Determine whether the amount of insurance data reaches a preset threshold;

[0103] If so, obtain key fields of multiple insurance data; and classify the insurance data according to the key fields.

[0104] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0105] Generate a workflow to be reviewed based on the insurance data; obtain the current date and a pre-stored date table, which carries multiple date identifiers; obtain the date identifier corresponding to the current date based on the date table; and capture the workflow to be reviewed based on the date identifier.

[0106] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0107] Receiving a rule file uploaded by the first terminal, the rule file carrying a file identifier;

[0108] The rule files are classified and packaged according to the file identifiers to obtain multiple rule packages.

[0109] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0110] Receiving insurance data uploaded by the first terminal, the insurance data carrying key fields;

[0111] Use key fields to filter multiple rule packages, and filter out rule files corresponding to insurance data from the rule packages.

[0112] The execution order of the multiple rule files selected is determined according to the key fields.

[0113] The multiple filtered rule files are loaded according to the execution order, and the insurance data is reviewed according to the loaded rule files.

[0114] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0115] Read the configuration file, which records the priority levels corresponding to the key fields;

[0116] The execution order of the rule files corresponding to the key fields is determined according to the priority levels corresponding to the key fields.

[0117] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0118] Receiving a rule file update request uploaded by the second terminal, the update request carrying key fields and an updated rule file;

[0119] Get the rule file before updating based on the key fields;

[0120] The updated rule file overwrites the rule file before updating.

[0121] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0122] Determine whether the amount of insurance data reaches a preset threshold;

[0123] If so, obtain key fields of multiple insurance data; and classify the insurance data according to the key fields.

[0124] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0125] Generate a workflow to be reviewed based on the insurance data; obtain the current date and a pre-stored date table, which carries multiple date identifiers; obtain the date identifier corresponding to the current date based on the date table; and capture the workflow to be reviewed based on the date identifier.

[0126] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0127] Receiving a rule file uploaded by the first terminal, the rule file carrying a file identifier;

[0128] The rule files are classified and packaged according to the file identifiers to obtain multiple rule packages.

[0129] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0130] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0131] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A method for reviewing insurance data, the method comprising: Receiving insurance data uploaded by the first terminal, wherein the insurance data carries a key field; The key fields include file identification and data identification; Determining whether the amount of the insurance data reaches a preset threshold; If yes, obtain key fields of multiple insurance data; Classify the insurance data according to the key fields, classify the insurance data with the same key fields into the same category, and obtain multiple insurance data categories; For each insurance data class, determine the target rule package where the rule file corresponding to the insurance data class is located using the file identifier in the key field corresponding to the insurance data class, filter the rule files in the target rule package using the data identifier in the key field corresponding to the insurance data class, and filter out multiple rule files corresponding to the insurance data class from multiple rule files in the target rule package; Reading a configuration file, wherein the configuration file records the priority levels corresponding to the key fields; Determine the execution order of the rule files corresponding to the key fields according to the priority levels corresponding to the key fields corresponding to the insurance data class; The multiple rule files selected are loaded according to the execution order, and all the insurance data in the insurance data class are uniformly reviewed according to the loaded rule files.

2. The method according to claim 1, characterized in that The method further comprises: Receiving a rule file update request uploaded by the second terminal, wherein the update request carries a key field and an updated rule file; Obtain the rule file before updating according to the key field; The updated rule file overwrites the rule file before updating.

3. The method according to claim 1, characterized in that After the insurance data is classified according to the key fields, the following further comprises: Generate a workflow to be reviewed based on the insurance data; Obtaining the current date and a pre-stored date table, wherein the date table carries multiple date identifiers; Obtaining a date identifier corresponding to the current date according to the date table; The workflow to be reviewed is captured according to the date identifier.

4. The method according to claim 1, characterized in that: The receiving of the insurance data uploaded by the first terminal includes: Receiving a rule file uploaded by the first terminal, wherein the rule file carries a file identifier; The rule files are classified and packaged according to the file identifiers to obtain multiple rule packages.

5. An insurance data review device, characterized in that: The device comprises: A receiving module, used for receiving the insurance data uploaded by the first terminal, wherein the insurance data carries a key field; the key field includes a file identifier and a data identifier; The receiving module is also used to determine whether the amount of insurance data reaches a preset threshold; if so, obtain key fields of multiple insurance data; classify the insurance data according to the key fields, classify the insurance data with the same key fields into the same category, and obtain multiple insurance data categories; A screening module, for each insurance data class, using the file identifier in the key field corresponding to the insurance data class to determine the target rule package where the rule file corresponding to the insurance data class is located, using the data identifier in the key field corresponding to the insurance data class to screen the rule files in the target rule package, and screening out multiple rule files corresponding to the insurance data class from multiple rule files in the target rule package; A determination module is used to read a configuration file, in which the priority levels corresponding to the key fields are recorded; and to determine the execution order of the rule files corresponding to the key fields according to the priority levels corresponding to the key fields corresponding to the insurance data class; The audit module is used to load the multiple rule files selected according to the execution order, and conduct a unified audit on all the insurance data in the insurance data class according to the loaded rule files.

6. The device according to claim 5, characterized in that The device also includes: an update module, which is used to: receive a rule file update request uploaded by the second terminal, the update request carrying a key field and an updated rule file; obtain the rule file before the update according to the key field; and overwrite the rule file before the update according to the updated rule file.

7. The device according to claim 5, characterized in that The receiving module is also used to generate a workflow to be reviewed based on the insurance data; obtain the current date and a pre-stored date table, the date table carrying multiple date identifiers; obtain the date identifier corresponding to the current date based on the date table; and capture the workflow to be reviewed based on the date identifier.

8. The device according to claim 5, characterized in that The receiving module is also used to receive a rule file uploaded by the first terminal, the rule file carrying a file identifier; and classify and package the rule file according to the file identifier to obtain multiple rule packages.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the insurance data review method described in any one of claims 1 to 4 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the insurance data review method described in any one of claims 1 to 4 are implemented.

Images