WO2018233367A1 - Procédé et appareil d'enregistrement de cas, terminal et support de stockage lisible par ordinateur - Google Patents

Procédé et appareil d'enregistrement de cas, terminal et support de stockage lisible par ordinateur Download PDF

Info

Publication number
WO2018233367A1
WO2018233367A1 PCT/CN2018/083675 CN2018083675W WO2018233367A1 WO 2018233367 A1 WO2018233367 A1 WO 2018233367A1 CN 2018083675 W CN2018083675 W CN 2018083675W WO 2018233367 A1 WO2018233367 A1 WO 2018233367A1
Authority
WO
WIPO (PCT)
Prior art keywords
case
field
request
verification
filing
Prior art date
Application number
PCT/CN2018/083675
Other languages
English (en)
Chinese (zh)
Inventor
赵亮
刘金萍
黄建虎
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2018233367A1 publication Critical patent/WO2018233367A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/18—Legal services; Handling legal documents

Definitions

  • the present application relates to the field of computer technologies, and in particular, to a filing method, apparatus, terminal, and computer readable storage medium.
  • the main purpose of the present application is to provide a method, device, terminal and computer readable storage medium for solving the problem of the existing filing method, low filing efficiency and poor intelligence.
  • the present application provides a filing method, the filing method comprising:
  • the report entry is displayed in the preset interface of the claim system
  • Each verification case is used to review the corresponding cases.
  • the claim settlement plan is generated based on the amount of the compensation corresponding to the case.
  • the present application further provides a filing device, the filing device comprising:
  • a display module configured to display a report entry in a preset interface of the claims system when receiving the case import request
  • the comparison module is configured to extract corresponding data fields in each imported case, and compare the extracted data fields with the pre-stored mapping table to determine a verification rule corresponding to each data field;
  • the audit module is used to review each case by using each verification rule.
  • the claim scheme is generated based on the amount of the claim corresponding to the case.
  • the present application further provides a terminal, where the terminal includes a memory, a processor, and a filing program stored on the memory and operable on the processor, the filing program being The steps of the filing method as described above are implemented when the processor executes.
  • the present application further provides a computer readable storage medium, where the computer readable storage medium stores a filing program, and the filing program is executed by a processor to implement the filing method as described above. step.
  • the technical solution proposed by the present application first displays a report entry in a preset interface of the claims system when receiving the case import request, and then imports a batch case from the report entry, and extracts corresponding data from each imported case. Field, and compare each extracted data field with the pre-stored mapping table to determine the verification rule corresponding to each data field, and finally use each verification rule to review each case, and when the verification is correct, based on the case The corresponding compensation amount is generated to generate a claim plan.
  • this application examines the case through the verification rules of each case, and carries out subsequent filing, realizing the batch filing of the claims plan, without having to manually file each case separately, and improve the claims. The efficiency and intelligence of filing the case saves manpower.
  • FIG. 1 is a schematic structural diagram of a terminal in a hardware operating environment involved in a solution according to an embodiment of the present application
  • FIG. 2 is a schematic flow chart of a first embodiment of a method for filing a case according to the present application
  • FIG. 3 is a schematic flow chart of a second embodiment of a filing method of the present application.
  • the solution of the embodiment of the present application is mainly: when receiving the case import request, first displaying the report entry in the preset interface of the claim system, then importing the batch case from the report entry, and extracting from the imported cases. Corresponding data fields, and comparing the extracted data fields with the pre-stored mapping table to determine the verification rules corresponding to the respective data fields, and finally using the respective verification rules to review the corresponding cases, when the verification is correct A claim settlement plan is generated based on the amount of the claim corresponding to the case. In order to solve the problem of poor intelligence and low efficiency in the existing filing method.
  • FIG. 1 is a schematic structural diagram of a terminal in a hardware operating environment involved in an embodiment of the present application.
  • the device in the embodiment of the present application may be a PC, or may be a mobile terminal device having a display function, such as a smart phone, a tablet computer, an e-book reader, and a portable computer.
  • the device may include a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005.
  • the communication bus 1002 is used to implement connection communication between these components.
  • the user interface 1003 can include a display, an input unit such as a keyboard, and the optional user interface 1003 can also include a standard wired interface, a wireless interface.
  • the network interface 1004 can optionally include a standard wired interface, a wireless interface (such as a WI-FI interface).
  • the memory 1005 may be a high speed RAM memory or a stable memory (non-volatile) Memory), such as disk storage.
  • the memory 1005 can also optionally be a storage device independent of the aforementioned processor 1001.
  • the device may also include a camera, RF (Radio) Frequency, RF) circuits, sensors, audio circuits, WiFi modules, and more.
  • RF Radio
  • RF Radio Frequency
  • FIG. 1 does not constitute a limitation to the device, and may include more or less components than those illustrated, or a combination of certain components, or different component arrangements.
  • an operating system, a network communication module, a user interface module, and a filing program may be included in the memory 1005 as a computer readable storage medium.
  • the operating system is a program for managing and controlling terminal and software resources, and supports operation of a network communication module, a user interface module, a filing program, and other programs or software; a network communication module is used to manage and control the network interface 1002; and a user interface module is used.
  • the user interface 1003 is managed and controlled.
  • the network interface 1004 is mainly used to connect to the claims system platform, and performs data communication with the claims system platform;
  • the user interface 1003 is mainly used to connect the client (user end) and perform data communication with the client;
  • the terminal invokes the filing program stored in the memory 1005 by the processor 1001 and executes the steps of the filing method as described below.
  • FIG. 2 is a schematic flow chart of a preferred embodiment of the method for filing a case of the present application.
  • the filing method includes:
  • the filing method is applied to a terminal, and the terminal is a terminal as shown in FIG.
  • the terminal is provided with a claim system, and the claim system is used for reporting and filing.
  • step S10 when the case import request is received, the report entry is displayed in the preset interface of the claim system.
  • the triggering manner of the case import request includes:
  • the terminal displays a preset interface of the claim system, such as a main interface, when the user clicks a preset case import button in the main interface to trigger a case import request.
  • a preset interface of the claim system such as a main interface
  • the terminal receives the report request sent by the third party in the service interface of the claim system, performs risk check on the report request, and triggers the case import request based on the report request when the verification is successful. Specifically, receiving the report request sent by the third party, first identifying the parameter information of the report request, extracting the pre-stored judgment rule based on the parameter information, and verifying the parameter information according to the determination rule, if the parameter is detected The information matches the judgment rule, and the verification is determined to be successful. When the verification is successful, a case flag is added to the report request to trigger the case import request according to the added case flag.
  • the terminal Upon receiving the case import request, the terminal displays the report entry in the preset interface of the claim system, and the report entry can be imported into the batch case at one time.
  • the implementation manner of the step S10 includes:
  • the terminal when the terminal receives the request for importing the case in the preset interface of the claim system, the terminal directly displays the batch report entry in the current interface.
  • the user can import the case based on the batch report entry.
  • the third party can send a case to the report entry through the service interface of the claim system.
  • Step S20 importing a batch case from the report entry.
  • the terminal When the terminal receives the batch case from the report entry, the received batch case is imported into the claim system, and the imported batch case is cached in the cache area.
  • the case of batch import is mainly for the case that the insurance policy has a high frequency of occurrence and a small amount of risk in different policies under the same policy or the same insurance.
  • the terminal imports a batch case from the report entry, it is via CSV (Comma-Separated). Values, character-separated values) are imported.
  • the claim system in this embodiment supports an extensible import template, that is, the report entry is available for the operator to set and import the claim data, and can record and download the original data.
  • Step S30 extracting corresponding data fields in each imported case, and comparing the extracted data fields with the pre-stored mapping table to determine a verification rule corresponding to each data field;
  • the terminal After the terminal imports the batch case from the report entry, the terminal extracts the data field corresponding to each case in each imported case, and then compares the extracted fields with the mapping table prestored by the terminal.
  • the data storage field and the corresponding verification rule are stored in the pre-stored mapping table, where a data field corresponds to a verification rule, a data field corresponds to multiple verification rules, or A plurality of data fields correspond to a verification rule, which is specifically set according to actual conditions.
  • the verification rules corresponding to the respective data fields may be determined according to the mapping table.
  • step S40 each of the corresponding cases is reviewed by using each verification rule.
  • the claim settlement plan is generated based on the amount of the compensation corresponding to the case.
  • each verification rule can be used to review each case, that is, whether each data field in each case satisfies the corresponding verification rule.
  • each case in the comparison process between each data field and the verification rule, if the ratio of the number of data fields satisfying the verification rule to the total data field of the case reaches a preset threshold, the case is considered to be correct, and Determining the amount of the claim, in order to generate a corresponding claim plan according to the amount of the case, specifically: after the case is verified by using each check rule, the amount of the case is compensated according to the amount of compensation previously arranged in the case. Add to the case table to generate the corresponding claims plan.
  • the case in the claim system also has a query function, specifically:
  • the query condition corresponding to the query instruction is determined, and the query condition includes a batch number query, an import start and end time query (limited 7-day range), a batch status query, an organization query, and the like. Moreover, when the case is queried, the query can be performed in a preset order, such as in chronological order.
  • the technical solution proposed by the embodiment when receiving the case import request, first displays the report entry in the preset interface of the claim system, and then imports the batch case from the report entry, and extracts corresponding items from the imported cases. Data field, and compare each extracted data field with a pre-stored mapping table to determine a verification rule corresponding to each data field, and finally use each verification rule to review each case, and when the verification is correct, based on The amount of compensation corresponding to the case generates a claim settlement plan.
  • this application examines the case through the verification rules of each case, and carries out subsequent filing, realizing the batch filing of the claims plan, without having to manually file each case separately, and improve the claims.
  • the efficiency and intelligence of filing the case saves manpower.
  • the method further includes:
  • Step S50 after a case import failure occurs, obtaining a case that the import fails;
  • Step S60 storing the failed import case into the preset storage area, and generating a case list based on the case of the failed import, so as to download the corresponding case based on the case list.
  • the terminal imports the batch case from the report entry, if the case import fails, the terminal stores the failed import case in the preset storage area, and the terminal fails to import the case.
  • Obtaining identification information corresponding to the case where the identification information may be a case name or a case number, to generate a case list according to the obtained identification information, and subsequently, the corresponding case may be downloaded from the preset storage area based on the case list. To prevent the case from failing to import, the case could not be found.
  • the failed import case is stored, and the case that the import failed is found according to the case list for downloading and viewing.
  • the third embodiment of the method of filing is different from the first embodiment of the method of filing.
  • the method further includes:
  • Step A when receiving a call request of a third party in a service interface of the claim system, determining a call request sent by the third party;
  • Step B detecting a request type of the call request, and if the request type is one of preset types, receiving a report request of the third party;
  • Step C Perform a risk check on the report request, and after the verification succeeds, trigger the case import request based on the report request.
  • the terminal before the terminal displays the report entry in the preset interface of the claim system according to the case import request, the terminal first determines the trigger mode of the case import request, and if the trigger mode of the case import request is triggered by a third party, then The third party first calls the service interface of the terminal to establish the communication connection.
  • the third party refers to a partner and can be represented by other devices.
  • the method further includes: before the step A, the method further includes:
  • Step D registering a transaction code for the third party, so that the third party invokes the service interface through the transaction code.
  • the terminal needs to register a transaction code (tradecode) for the third party, and the transaction code is unique, and the third party interacts with the terminal's claim system through the transaction code to call The service interface of the claims system.
  • a transaction code tradecode
  • the existing third parties are different.
  • the service interface is preferably a restful interface. Through the restful interface, different types of third parties can call the service interface without setting different interfaces for different third parties, which improves the high availability of data calls.
  • the service data in the claim system in the present embodiment has a specific form of data in the json format, so that each third party can call and receive data.
  • the terminal When the terminal receives the call request of the third party in the service interface of the claim system, the terminal first determines the call request sent by the third party.
  • the call request sent by the third party is determined, which may be Determining the type of the request corresponding to the call request, specifically, determining the type identifier included in the call request to determine whether the request type of the call request is one of the preset types, and if it is one of the preset types, the third party is considered
  • the call request sent is reasonable, and the preset type is set according to the actual situation, and is not limited herein.
  • the terminal receives the report request of the third party.
  • the report request includes information such as the time of the case, the time of the insurance, the policy number, and the amount of the payment.
  • the terminal After receiving the report request sent by the third party, the terminal performs a risk check on the report request. After the verification succeeds, the case import request is triggered based on the report request, that is, the case flag is added in the report request. The case import request is triggered based on the added case flag.
  • the step of performing risk verification on the report request includes:
  • the terminal first identifies the parameter information carried in the report request, and the parameter information, such as the case time, the time of the insurance, the policy number, etc., after extracting the parameter information, extracts the judgment rule according to the parameter information, and then according to the parameter information.
  • the judgment rule verifies the parameter information.
  • the judgment rule is the existing policy number in the system, and the parameter information is verified according to the judgment rule, which is actually comparing the policy number with each existing policy number in the system. To determine whether the policy number exists, if the policy number exists, it is considered that the parameter information matches the judgment rule, and the verification is determined to be successful. Other parameter information and the verification method of the judgment rule are not described in detail.
  • the case import request may be triggered based on the report request, and the report entry is displayed in the preset interface of the claim system based on the case import request, and the subsequent entry is performed.
  • the operation process, the subsequent operation process has been detailed in the above, and will not be described here.
  • the service interface is first set in the claims system, and the transaction code is set to the third party, and the third party terminal that does not have the claim settlement capability can also be implemented by the third party through the service interface.
  • the fourth embodiment of the filing method is different from the first embodiment of the filing method in that, before the step A, the method further includes:
  • Step E extracting a data field in the preset claim application data, and comparing the extracted data field with the pre-stored field;
  • Step F when the data field matches the pre-stored field, determining that the data field is a basic field
  • Step G when the data field does not match the pre-stored field, determine that the data field is an extended field, and add the field to the system;
  • Step H mapping the basic field and the extended field under a transaction code to map a verification rule corresponding to the basic field and the extended field;
  • step I the basic field and the extended field are associated with the corresponding verification rule for subsequent review of the case.
  • the claim application data refers to the claim data having the public basis, and after obtaining the claim application data, the data field is extracted from the claim application data, such as the application time, the application for the claim partner, the application for the payment amount, etc., and then The extracted data field is compared with the pre-stored field.
  • the data field is considered to be a basic field, and when the data field does not match the pre-stored field, the data field is considered to be an extended field. And add this field to the system.
  • the base field and the extension field are mapped under the transaction code. Since the transaction code can uniquely represent the third party, the base field and the extension field are mapped under the transaction code, optionally Determining the current transaction code, configuring a verification rule for the base field of the transaction code, and configuring another verification rule for the extension field of the transaction code to map the verification corresponding to the base field and the extension field of the transaction code. The rule finally stores the base field and the extended field in association with the corresponding verification rule to obtain a mapping table for subsequent review of the case associated with the transaction code.
  • mapping table in the system before the terminal files the case in the claims system, so that the subsequent review of the case can be carried out through the mapping table, thereby realizing the automatic review of the case and improving the filing of the case. Convenience.
  • the verification rule Upon receiving the verification rule modification instruction, the verification rule is adjusted and/or added or deleted according to the verification rule modification instruction.
  • the filing device includes:
  • a display module configured to display a report entry in a preset interface of the claims system when receiving the case import request
  • the comparison module is configured to extract corresponding data fields in each imported case, and compare the extracted data fields with the pre-stored mapping table to determine a verification rule corresponding to each data field;
  • the audit module is used to review each case by using each verification rule.
  • the claim scheme is generated based on the amount of the claim corresponding to the case.
  • the filing device may be a terminal, and the terminal is a terminal as shown in FIG. 1 .
  • the terminal is provided with a claim system, and the claim system is used for reporting and filing.
  • the triggering manner of the case import request includes:
  • the terminal displays a preset interface of the claim system, such as a main interface, when the user clicks a preset case import button in the main interface to trigger a case import request.
  • a preset interface of the claim system such as a main interface
  • the terminal receives the report request sent by the third party in the service interface of the claim system, performs risk check on the report request, and triggers the case import request based on the report request when the verification is successful. Specifically, receiving the report request sent by the third party, first identifying the parameter information of the report request, extracting the pre-stored judgment rule based on the parameter information, and verifying the parameter information according to the determination rule, if the parameter is detected The information matches the judgment rule, and the verification is determined to be successful. When the verification is successful, a case flag is added to the report request to trigger the case import request according to the added case flag.
  • the terminal Upon receiving the case import request, the terminal displays the report entry in the preset interface of the claim system, and the report entry can be imported into the batch case at one time.
  • the implementation manner of the display module for displaying the report entry in the preset interface of the claim system when receiving the case import request includes:
  • the terminal when the terminal receives the request for importing the case in the preset interface of the claim system, the terminal directly displays the batch report entry in the current interface.
  • the user can import the case based on the batch report entry.
  • the third party can send a case to the report entry through the service interface of the claim system.
  • the terminal When the terminal receives the batch case from the report entry, the received batch case is imported into the claim system, and the imported batch case is cached in the cache area.
  • the case of batch import is mainly for the case that the insurance policy has a high frequency of occurrence and a small amount of risk in different policies under the same policy or the same insurance.
  • the terminal imports a batch case from the report entry, it is via CSV (Comma-Separated). Values, character-separated values) are imported.
  • the claim system in this embodiment supports an extensible import template, that is, the report entry is available for the operator to set and import the claim data, and can record and download the original data.
  • the terminal After the terminal imports the batch case from the report entry, the terminal extracts the data field corresponding to each case in each imported case, and then compares the extracted fields with the mapping table prestored by the terminal.
  • the data storage field and the corresponding verification rule are stored in the pre-stored mapping table, where a data field corresponds to a verification rule, a data field corresponds to multiple verification rules, or A plurality of data fields correspond to a verification rule, which is specifically set according to actual conditions.
  • the verification rules corresponding to the respective data fields may be determined according to the mapping table.
  • each verification rule can be used to review each case, that is, whether each data field in each case satisfies the corresponding verification rule.
  • each case in the comparison process between each data field and the verification rule, if the ratio of the number of data fields satisfying the verification rule to the total data field of the case reaches a preset threshold, the case is considered to be correct, and Determining the amount of the claim, in order to generate a corresponding claim plan according to the amount of the case, specifically: after the case is verified by using each check rule, the amount of the case is compensated according to the amount of compensation previously arranged in the case. Add to the case table to generate the corresponding claims plan.
  • the case in the claim system also has a query function, specifically:
  • the query condition corresponding to the query instruction is determined, and the query condition includes a batch number query, an import start and end time query (limited 7-day range), a batch status query, an organization query, and the like. Moreover, when the case is queried, the query can be performed in a preset order, such as in chronological order.
  • the technical solution proposed by the embodiment when receiving the case import request, first displays the report entry in the preset interface of the claim system, and then imports the batch case from the report entry, and extracts corresponding items from the imported cases. Data field, and compare each extracted data field with a pre-stored mapping table to determine a verification rule corresponding to each data field, and finally use each verification rule to review each case, and when the verification is correct, based on The amount of compensation corresponding to the case generates a claim settlement plan.
  • this application examines the case through the verification rules of each case, and carries out subsequent filing, realizing the batch filing of the claims plan, without having to manually file each case separately, and improve the claims.
  • the efficiency and intelligence of filing the case saves manpower.
  • the obtaining module is configured to obtain a case that the import failed after the case fails to be imported;
  • the first storage module is configured to store the failed import case into the preset storage area, and generate a case list based on the failed import case, so as to download the corresponding case based on the case list.
  • the terminal imports the batch case from the report entry, if the case import fails, the terminal stores the failed import case in the preset storage area, and the terminal fails to import the case.
  • Obtaining identification information corresponding to the case where the identification information may be a case name or a case number, to generate a case list according to the obtained identification information, and subsequently, the corresponding case may be downloaded from the preset storage area based on the case list. To prevent the case from failing to import, the case could not be found.
  • the failed import case is stored, and the case that the import failed is found according to the case list for downloading and viewing.
  • a judging module configured to determine, when the third party call request is received in the service interface of the claim system, the call request sent by the third party;
  • a detecting module configured to detect a request type of the calling request, and if the request type is one of preset types, receiving a report request of the third party;
  • the verification module is configured to perform a risk check on the report request, and after the verification succeeds, trigger the case import request based on the report request.
  • the terminal before the terminal displays the report entry in the preset interface of the claim system according to the case import request, the terminal first determines the trigger mode of the case import request, and if the trigger mode of the case import request is triggered by a third party, then The third party first calls the service interface of the terminal to establish the communication connection.
  • the third party refers to a partner and can be represented by other devices.
  • the device further comprises:
  • a registration module for registering a transaction code for the third party to cause the third party to invoke the service interface via a transaction code.
  • the terminal needs to register a transaction code (tradecode) for the third party, and the transaction code is unique, and the third party interacts with the terminal's claim system through the transaction code to call The service interface of the claims system.
  • a transaction code tradecode
  • the existing third parties are different.
  • the service interface is preferably a restful interface. Through the restful interface, different types of third parties can call the service interface without setting different interfaces for different third parties, which improves the high availability of data calls.
  • the service data in the claim system in the present embodiment has a specific form of data in the json format, so that each third party can call and receive data.
  • the terminal When the terminal receives the call request of the third party in the service interface of the claim system, the terminal first determines the call request sent by the third party.
  • the call request sent by the third party is determined, which may be Determining the type of the request corresponding to the call request, specifically, determining the type identifier included in the call request to determine whether the request type of the call request is one of the preset types, and if it is one of the preset types, the third party is considered
  • the call request sent is reasonable, and the preset type is set according to the actual situation, and is not limited herein.
  • the terminal receives the report request of the third party.
  • the report request includes information such as the time of the case, the time of the insurance, the policy number, and the amount of the payment.
  • the terminal After receiving the report request sent by the third party, the terminal performs a risk check on the report request. After the verification succeeds, the case import request is triggered based on the report request, that is, the case flag is added in the report request. The case import request is triggered based on the added case flag.
  • the verification module is further configured to identify parameter information of the report request, extract a pre-stored determination rule based on the parameter information, and verify the parameter information according to the determination rule; If the parameter information matches the determination rule, it is determined that the verification is successful.
  • the terminal first identifies the parameter information carried in the report request, and the parameter information, such as the case time, the time of the insurance, the policy number, etc., after extracting the parameter information, extracts the judgment rule according to the parameter information, and then according to the parameter information.
  • the judgment rule verifies the parameter information.
  • the judgment rule is the existing policy number in the system, and the parameter information is verified according to the judgment rule, which is actually comparing the policy number with each existing policy number in the system. To determine whether the policy number exists, if the policy number exists, it is considered that the parameter information matches the judgment rule, and the verification is determined to be successful. Other parameter information and the verification method of the judgment rule are not described in detail.
  • the case import request may be triggered based on the report request, and the report entry is displayed in the preset interface of the claim system based on the case import request, and the subsequent entry is performed.
  • the operation process, the subsequent operation process has been detailed in the above, and will not be described here.
  • the service interface is first set in the claims system, and the transaction code is set to the third party, and the third party terminal that does not have the claim settlement capability can also be implemented by the third party through the service interface.
  • the extracting module is configured to extract a data field in the preset claim application data, and compare the extracted data field with the pre-stored field;
  • a determining module configured to determine that the data field is a basic field when the data field matches the pre-stored field
  • the determining module is further configured to: when the data field does not match the pre-stored field, determine that the data field is an extended field, and add the field to the system;
  • mapping module configured to map the basic field and the extended field under a transaction code to map a verification rule corresponding to the basic field and the extended field;
  • the second storage module is configured to store the basic field and the extended field in association with the corresponding verification rule, so as to subsequently review the case.
  • the claim application data refers to the claim data having the public basis, and after obtaining the claim application data, the data field is extracted from the claim application data, such as the application time, the application for the claim partner, the application for the payment amount, etc., and then The extracted data field is compared with the pre-stored field.
  • the data field is considered to be a basic field, and when the data field does not match the pre-stored field, the data field is considered to be an extended field. And add this field to the system.
  • the base field and the extension field are mapped under the transaction code. Since the transaction code can uniquely represent the third party, the base field and the extension field are mapped under the transaction code, optionally Determining the current transaction code, configuring a verification rule for the base field of the transaction code, and configuring another verification rule for the extension field of the transaction code to map the verification corresponding to the base field and the extension field of the transaction code. The rule finally stores the base field and the extended field in association with the corresponding verification rule to obtain a mapping table for subsequent review of the case associated with the transaction code.
  • mapping table in the system before the terminal files the case in the claims system, so that the subsequent review of the case can be carried out through the mapping table, thereby realizing the automatic review of the case and improving the filing of the case. Convenience.
  • a modification module configured to: when the verification rule modification instruction is received, modify the verification rule according to the verification rule modification instruction, and/or add or delete the verification rule.
  • the embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium stores a filing program, and when the filing program is executed by the processor, the steps of the filing method as described above are implemented.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better.
  • Implementation Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

Landscapes

  • Business, Economics & Management (AREA)
  • Tourism & Hospitality (AREA)
  • Engineering & Computer Science (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Technology Law (AREA)
  • Primary Health Care (AREA)
  • Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention concerne un procédé d'enregistrement de cas. Le procédé consiste : à afficher, lorsqu'une demande d'importation de cas est reçue, une entrée de rapport dans une interface prédéfinie d'un système de déclaration de sinistre ; à importer des fiches de cas provenant de l'entrée de rapport ; à extraire un champ de données correspondant de chaque cas importé, et comparer chaque champ de données extrait avec une table de mappage pré-stockée afin de déterminer une règle de vérification correspondant à chaque champ de données ; à examiner chaque cas correspondant par utilisation de chaque règle de vérification, et à générer, lorsque la vérification réussit, un schéma de déclaration de sinistre sur la base de la quantité de compensation correspondant au cas. La présente invention concerne également un appareil d'enregistrement de cas, un terminal et un support de stockage lisible par ordinateur. La présente invention améliore l'efficacité et l'intelligence de l'enregistrement de cas de déclaration de sinistre, et économise de la main d'œuvre.
PCT/CN2018/083675 2017-06-22 2018-04-19 Procédé et appareil d'enregistrement de cas, terminal et support de stockage lisible par ordinateur WO2018233367A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710483564.9A CN108335237B (zh) 2017-06-22 2017-06-22 立案方法、终端和计算机可读存储介质
CN201710483564.9 2017-06-22

Publications (1)

Publication Number Publication Date
WO2018233367A1 true WO2018233367A1 (fr) 2018-12-27

Family

ID=62922085

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/083675 WO2018233367A1 (fr) 2017-06-22 2018-04-19 Procédé et appareil d'enregistrement de cas, terminal et support de stockage lisible par ordinateur

Country Status (2)

Country Link
CN (1) CN108335237B (fr)
WO (1) WO2018233367A1 (fr)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108932612B (zh) * 2018-08-17 2022-07-12 中国建设银行股份有限公司 一种应用于企业年金的数据处理方法、装置及电子设备
CN109934722A (zh) * 2019-01-31 2019-06-25 德联易控科技(北京)有限公司 校验规则的调试方法、装置及电子设备
CN110517007A (zh) * 2019-06-14 2019-11-29 平安科技（深圳）有限公司 仲裁申请立案审核处理方法、装置和计算机设备
CN110377631B (zh) * 2019-06-17 2024-01-09 平安科技（深圳）有限公司 案件信息处理方法、装置、计算机设备和存储介质
CN110335180A (zh) * 2019-07-04 2019-10-15 北京市律典通科技有限公司 案件立案材料智能审查装置
CN110728593A (zh) * 2019-09-04 2020-01-24 杭州安存网络科技有限公司 案件的立案方法和装置、电子设备和存储介质
CN111178822B (zh) * 2019-11-13 2023-08-15 泰康保险集团股份有限公司 理赔链生成方法、装置及存储介质
CN111309672B (zh) * 2020-02-07 2023-11-17 重庆华谷科技有限公司 立案和预立案辅助管理系统及智慧法务辅助服务系统
CN111680693A (zh) * 2020-05-28 2020-09-18 泰康保险集团股份有限公司 理赔业务批量处理方法及装置
CN111640031B (zh) * 2020-05-29 2023-07-14 泰康保险集团股份有限公司 跨系统的理赔数据处理方法、装置及相关设备

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105405053A (zh) * 2015-10-28 2016-03-16 上海商保通健康科技有限公司 人工智能理算系统
CN105956667A (zh) * 2016-04-14 2016-09-21 平安科技（深圳）有限公司 车险定损理赔审核方法及系统
CN106228448A (zh) * 2016-07-29 2016-12-14 深圳市永兴元科技有限公司 基于移动通信网络的车险理赔方法及装置
CN106295151A (zh) * 2016-08-03 2017-01-04 合肥奇也信息科技有限公司 一种医疗保险在线理赔系统
CN106682987A (zh) * 2016-11-21 2017-05-17 中国平安财产保险股份有限公司 一种财产险理赔实现方法及实现系统
CN106875030A (zh) * 2016-12-14 2017-06-20 武汉默联股份有限公司 商业健康保险在线直赔智能推荐系统及方法
CN107705211A (zh) * 2017-11-10 2018-02-16 平安科技（深圳）有限公司 一种保险理赔案件的理算方法和装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002035363A1 (fr) * 2000-10-20 2002-05-02 Ge Financial Assurance Holdings, Inc. Procede et systeme de verification de prime d'assurance
US7904326B2 (en) * 2001-06-29 2011-03-08 Versata Development Group, Inc. Method and apparatus for performing collective validation of credential information
US7415471B1 (en) * 2001-11-30 2008-08-19 Midland Loan Services, Inc. Methods and systems for automated data collection and analysis for use in association with asset securitization
CN101673268A (zh) * 2008-09-11 2010-03-17 贵州创慧科技开发有限公司 人像组合识别系统
CN201733328U (zh) * 2010-07-09 2011-02-02 中国工商银行股份有限公司 基于银行系统的企业数据维护装置及系统
CN103198200A (zh) * 2012-01-09 2013-07-10 北京汉林信通信息技术有限公司 人案信息采集比对反馈设备及其用途
US20140114692A1 (en) * 2012-10-23 2014-04-24 InnovaPad, LP System for Integrating First Responder and Insurance Information
CN106709696A (zh) * 2016-11-21 2017-05-24 中国平安财产保险股份有限公司 一种自助理赔实现方法及实现系统

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105405053A (zh) * 2015-10-28 2016-03-16 上海商保通健康科技有限公司 人工智能理算系统
CN105956667A (zh) * 2016-04-14 2016-09-21 平安科技（深圳）有限公司 车险定损理赔审核方法及系统
CN106228448A (zh) * 2016-07-29 2016-12-14 深圳市永兴元科技有限公司 基于移动通信网络的车险理赔方法及装置
CN106295151A (zh) * 2016-08-03 2017-01-04 合肥奇也信息科技有限公司 一种医疗保险在线理赔系统
CN106682987A (zh) * 2016-11-21 2017-05-17 中国平安财产保险股份有限公司 一种财产险理赔实现方法及实现系统
CN106875030A (zh) * 2016-12-14 2017-06-20 武汉默联股份有限公司 商业健康保险在线直赔智能推荐系统及方法
CN107705211A (zh) * 2017-11-10 2018-02-16 平安科技（深圳）有限公司 一种保险理赔案件的理算方法和装置

Also Published As

Publication number Publication date
CN108335237A (zh) 2018-07-27
CN108335237B (zh) 2020-10-27

Similar Documents

Publication Publication Date Title
WO2018233367A1 (fr) Procédé et appareil d'enregistrement de cas, terminal et support de stockage lisible par ordinateur
WO2019019374A1 (fr) Procédé, appareil et système permettant de commander un appareil électroménager à l'aide d'un dispositif vocal intelligent
WO2019019378A1 (fr) Procédé et appareil de traitement de service, adaptateur et support de stockage lisible par ordinateur
WO2018120457A1 (fr) Procédé de traitement de données, appareil, dispositif et support de stockage lisible par ordinateur
WO2018058919A1 (fr) Procédé, appareil, dispositif de génération d'informations d'identification, et support de stockage lisible par ordinateur
WO2019019493A1 (fr) Procédé et dispositif de partage de données et support d'informations lisible par ordinateur
WO2018082482A1 (fr) Procédé de partage de réseau et procédé et système d'accès à un réseau
WO2019024336A1 (fr) Procédé et dispositif d'interrogation de données, et support de stockage lisible par ordinateur
WO2018166236A1 (fr) Procédé, appareil et dispositif de reconnaissance de facture de règlement de revendication, et support d'informations lisible par ordinateur
WO2017201899A1 (fr) Procédé et appareil de connexion à un dispositif bluetooth
WO2019051899A1 (fr) Procédé et dispositif de commande de terminaux, et support d'informations
WO2018227887A1 (fr) Procédé de distribution de publicité vidéo, procédé de génération de publicité vidéo, dispositif, serveur et support d'informations lisible
WO2019037395A1 (fr) Procédé de gestion de clé, dispositif et support de stockage lisible
WO2019051890A1 (fr) Procédé et dispositif de commande de terminal et support de stockage lisible par ordinateur
WO2018149191A1 (fr) Procédé, appareil et dispositif de souscription à des polices d'assurance, et support d'informations lisible par ordinateur
WO2019019376A1 (fr) Procédé, appareil et dispositif de gestion de processus de service, et support d'informations lisible par ordinateur
WO2018201696A1 (fr) Procédé, appareil et dispositif de paiement de prime de renouvellement de police de carte d'assurance sociale, et support d'informations
WO2019051866A1 (fr) Procédé, dispositif et appareil de gestion d'informations de droits et d'intérêts, et support d'informations lisible par ordinateur
WO2019056462A1 (fr) Procédé, appareil, et dispositif de distribution de liste nominative, et support de stockage lisible par ordinateur
WO2019100531A1 (fr) Procédé de génération de signature numérique et dispositif associé, procédé de vérification et dispositif associé, et support d'informations
WO2018000856A1 (fr) Procédé de mise en œuvre de transfert de message de réseau de recouvrement sdn, terminal, appareil et support d'informations lisible par ordinateur
WO2019071762A1 (fr) Procédé et système de positionnement au sol, serveur et support d'enregistrement lisible par ordinateur
WO2018176864A1 (fr) Procédé et système de gestion d'autorisation de base de données, dispositif, support d'informations lisible par ordinateur
WO2019051934A1 (fr) Procédé d'évaluation de personnel commercial, plateforme d'évaluation et support d'informations lisible par ordinateur
WO2019071771A1 (fr) Procédé et système de calibrage d'informations d'empreinte de signal sans fil, serveur, et support

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18821041

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18821041

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 18.03.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18821041

Country of ref document: EP

Kind code of ref document: A1