Insurance data adjustment method and device and electronic equipment

Abstract

The invention provides an insurance data adjustment method and device and electronic equipment, and relates to the technical field of medical insurance, and the method comprises the steps: obtaining transaction information; determining an adjustment result based on the transaction information and the adjustment related information set; wherein the adjustment related information set comprises a rule information set and an adjustment information set; the adjustment information set comprises the adjustment quotas corresponding to the plurality of cycle types respectively. Therefore, the adjustment quotas respectively corresponding to the plurality of cycle types are merged and stored in one adjustment information set, and when the transaction information is adjusted, the called information records are less, the occupied computing resources are also less, and the adjustment efficiency is further improved.

Description

Technical Field

[0001] This application relates to the technical field of medical insurance, and in particular, to an insurance data calculation method, device, and electronic device. Background Art

[0002] In the related art, outpatient insurance is a type of commercial health insurance. After a user purchases the insurance, the user generally enjoys the right to claim compensation for outpatient services both online and offline. Among them, when claiming compensation online, the compensation amount can directly offset the order amount, and the user does not need to advance the payment first and then claim reimbursement. Because outpatient insurance claims generally involve a large number of data records such as compensation ratios, deductibles, compensation caps, and compensation times. For one transaction, multiple data records need to be operated, and the amount of data records to be processed is large, resulting in poor calculation efficiency. Summary of the Invention

[0003] An insurance data calculation method, device, and electronic device provided by an embodiment of this application can improve the efficiency of insurance data calculation.

[0004] The technical solution of this application is implemented as follows:

[0005] An embodiment of this application provides an insurance data calculation method, including:

[0006] Obtain transaction information;

[0007] Based on the transaction information and the calculation-related information set, determine the calculation result; where the calculation-related information set includes a rule information set and a calculation information set; the calculation information set includes: calculation amounts corresponding to multiple cycle types respectively.

[0008] In the above solution, the calculation information set includes: the used deductibles, compensation times, and compensation caps corresponding to multiple cycle types respectively.

[0009] In the above solution, the calculation information set includes: a first correspondence between each cycle of each cycle type and the used deductible, a second correspondence between each cycle of each cycle type and the compensation times, and a third correspondence between each cycle of each cycle type and the compensation cap;

[0010] The calculation information set further includes: a user amount identifier and the current data version.

[0011] In the above solution, the first correspondence, the second correspondence, and the third correspondence corresponding to each cycle type are stored in the storage order respectively;

[0012] Dynamically eliminate the earliest stored corresponding relationship based on the maximum storage quantities corresponding to the first corresponding relationship, the second corresponding relationship, and the third corresponding relationship for each of the cycle types.

[0013] In the above solution, the rule information set includes: a business rule information set and a user rule information set;

[0014] Among them, the business rule information set includes: a preset business type identifier and corresponding deductible amount, number of claim payments, claim payment limit, and claim payment ratio; the user rule information set includes: the preset business type identifier, user quota identifier, information set identifier, and business start and end times.

[0015] In the above solution, when the transaction information includes: a deduction amount and a first transaction time; determining the adjustment result based on the transaction information and the adjustment-related information set includes:

[0016] Verify the business start and end times in the transaction information and the rule information set to determine a first verification result;

[0017] When the first verification result indicates that the verification is passed, determine a first current transaction cycle corresponding to each of the multiple cycle types based on the first transaction time;

[0018] Based on the first current transaction cycle in the adjustment information set, determine the claim payment limit and the used deductible amount corresponding to each of the multiple cycle types;

[0019] Determine the adjustment result based on the claim payment limit, the used deductible amount, and the adjustment information set.

[0020] In the above solution, determining the adjustment result based on the claim payment limit, the used deductible amount, and the adjustment information set includes:

[0021] Determine the remaining amount based on the claim payment limit and the used non-claim payment;

[0022] Determine the minimum amount between the remaining amount and a preset direct payment amount as the direct payment amount; where the preset direct payment amount is determined based on the deduction amount and the claim payment ratio in the business rule information;

[0023] Determine the adjustment result based on the direct payment amount and the adjustment information set.

[0024] In the above solution, determining the adjustment result based on the direct payment amount and the adjustment information set includes:

[0025] Determine the out-of-pocket amount based on the direct payment amount and the deduction amount;

[0026] Based on the direct payment amount and the used deductible amounts of the first current transaction corresponding to multiple cycle types in the adjustment information set, determine the adjusted deductible amount and the deductible amount change for this time.

[0027] Based on the deduction amount, the direct payment amount, the out-of-pocket amount, the change data version, the adjusted deductible amount, the deductible amount change for this time, the used deductible amount, and a predetermined string, determine the adjustment result; wherein, the predetermined string is used to represent writing a transaction record for the transaction information.

[0028] In the above solution, the method further includes:

[0029] Based on the adjusted deductible amount, update the first corresponding relationships of the first current transaction cycles corresponding to multiple cycle types respectively, and update the claim times in the second corresponding relationships of the first current transaction cycles corresponding to multiple cycle types respectively.

[0030] In the above solution, before determining the adjustment result based on the direct payment amount and the adjustment information set, the method further includes:

[0031] If a single-transaction limit amount is set in the rule information set, determine the minimum amount between the preset direct payment amount and the single-transaction limit amount as the direct payment amount.

[0032] In the above solution, when the transaction information includes: a refund amount and a second transaction time; determining the adjustment result based on the transaction information and the adjustment-related information set includes:

[0033] Perform a verification on the transaction information to determine a second verification result;

[0034] When the second verification result indicates that the verification is passed, based on the second transaction time, determine the second current transaction cycles corresponding to multiple cycle types respectively;

[0035] Based on the refund amount and the used deductible amounts of the second current transaction cycles corresponding to multiple cycle types in the adjustment information set, determine the adjustment result.

[0036] In the above solution, the determining the adjustment result based on the refund amount and multiple second current transaction cycles in the adjustment information set includes:

[0037] Based on the refund amount and the used deductible amounts of the second current transaction cycles corresponding to multiple cycle types in the adjustment information set, determine the adjusted deductible amount and the deductible amount change for this time;

[0038] Determine the adjustment result based on the refund amount, the changed data version, the changed deductible, the current changed deductible, the used deductible, and a predetermined string; wherein, the predetermined string is used to indicate not writing a transaction record for the transaction information.

[0039] An embodiment of the present application further provides an insurance data adjustment device, including:

[0040] An information acquisition unit, configured to acquire transaction information;

[0041] An adjustment unit, configured to determine an adjustment result based on the transaction information and an adjustment-related information set; wherein, the adjustment-related information set includes a rule information set and an adjustment information set; the adjustment information set includes: adjustment amounts corresponding to multiple cycle types.

[0042] An embodiment of the present application further provides an electronic device, including a memory and a processor, the memory stores a computer program that can run on the processor, and when the processor executes the computer program, the steps in the above method are implemented.

[0043] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps in the above method are implemented.

[0044] An embodiment of the present application further provides a computer program product, including a computer program, and when the computer program is executed by a processor, the steps in the above method are implemented.

[0045] In an embodiment of the present application, by acquiring transaction information; determining an adjustment result based on the transaction information and an adjustment-related information set; wherein, the adjustment-related information set includes a rule information set and an adjustment information set; the adjustment information set includes: adjustment amounts respectively corresponding to multiple cycle types. In this way, the adjustment amounts respectively corresponding to multiple cycle types are combined and stored in an adjustment information set. When adjusting for transaction information, fewer information records are called, and less computing resources are occupied, thereby improving the adjustment efficiency. Description of the Drawings

[0046] Figure 1 It is an optional flowchart of the insurance data adjustment method provided by an embodiment of the present application;

[0047] Figure 2 It is an optional effect diagram of the insurance data adjustment method provided by an embodiment of the present application;

[0048] Figure 3 It is an optional flowchart of the insurance data adjustment method provided by an embodiment of the present application;

[0049] Figure 4An optional flowchart of the insurance data adjustment method provided by the embodiment of the present application;

[0050] Figure 5 An optional flowchart of the insurance data adjustment method provided by the embodiment of the present application;

[0051] Figure 6 An optional effect diagram of the insurance data adjustment method provided by the embodiment of the present application;

[0052] Figure 7 An optional flowchart of the insurance data adjustment method provided by the embodiment of the present application;

[0053] Figure 8 An optional flowchart of the insurance data adjustment method provided by the embodiment of the present application;

[0054] Figure 9 A structural diagram of the insurance data adjustment device provided by the embodiment of the present application;

[0055] Figure 10 A schematic diagram of a hardware entity of an electronic device provided by the embodiment of the present application. Detailed implementation manners

[0056] In order to make the objectives, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be further described in detail below with reference to the accompanying drawings and embodiments. The described embodiments should not be regarded as limitations on the present application. All other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of the present application.

[0057] In the following description, reference is made to "some embodiments", which describe a subset of all possible embodiments. However, it can be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments, and can be combined with each other without conflict.

[0058] If similar descriptions such as "first / second" appear in the application documents, the following description is added. In the following description, the terms "first\second\third" only distinguish similar objects and do not represent a specific order for the objects. It can be understood that "first\second\third" can be interchanged with a specific order or sequence when allowed, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0059] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the technical field to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0060] In the related art, since claims generally involve payout ratios, deductibles, payout caps, and the number of payouts. And deductibles, payout caps, and the number of payouts generally stack across different periods. For example, single - transaction limits, daily limits, monthly limits, and annual limits, and these periods can be stacked arbitrarily, and even all can be stacked. The single - transaction limit is a fixed value, while the daily, monthly, and annual limits are cumulative values. In theory, there are 3 * 3 * n = 9n (n represents the specific number of periods, such as a certain day, a certain month, a certain year) cumulative amount values. Therefore, at the system level, it is necessary to store and manage these amount values and perform corresponding calculations and changes when placing an order. Exemplarily, referring to Table 1: If the payout cap is configured, with a single - transaction limit of 10, a daily limit of 20, a monthly limit of 30, and an annual limit of 40.

[0061] Cycle key:

[0062]

[0063] Table 1

[0064] Among them, for one transaction, to locate the specific cycle key, 9 data records need to be operated on, plus 1 transaction record. In total, two data tables need to be read and written, and 10 records need to be operated on. There are performance problems and it is not suitable for high - traffic and high - concurrency scenarios. Also, for the daily limit, the cycle is short. Within one policy cycle (usually one year), there may be N or more data. And for historical data, as time goes by, it doesn't need to be concerned anymore, and this kind of storage will cause waste of database resources.

[0065] To solve the above - mentioned technical problems, an embodiment of the present application provides an insurance data adjustment method. Please refer to Figure 1 , which is an optional process schematic diagram of the adjustment method provided by the embodiment of the present application, and will be described in conjunction with Figure 1 the steps shown:

[0066] S101. Obtain transaction information.

[0067] In the embodiment of the present application, after the user performs a transaction operation on the client, the server obtains the transaction information formed for the transaction operation. Among them, the transaction information may include: the deducted amount and the first transaction time information. Or, the transaction information may also include: the refund amount and the second transaction time information.

[0068] In the embodiment of the present application, when the user places an order on the client, the server obtains the deducted amount and the first transaction time information. When the user cancels an order on the client, the server obtains the refund amount and the second transaction time information.

[0069] Exemplarily, in conjunction with Figure 2, after the user performs a transaction operation on the client, the server can obtain the user direct payment record form corresponding to this transaction. Among them, the direct payment record ID in the user direct payment record form can be used to determine the amount and transaction time corresponding to this transaction. The user direct payment card ID is used to represent the preset service type corresponding to the user. The adjustment ID is used to represent the quota corresponding to the user. The order ID represents the identifier of this transaction. User direct payment record form: The order data of the user direct payment card for completing the deduction transaction. It is used to record the relevant parameters of the transaction, such as the transaction time, amount, etc.

[0070] S102. Determine the adjustment result based on the transaction information and the adjustment-related information set; wherein, the adjustment-related information set includes a rule information set and an adjustment information set; the adjustment information set includes: the adjustment quotas corresponding to multiple cycle types.

[0071] In the embodiment of the present application, after the server obtains the transaction information, it can find the adjustment-related information set corresponding to the user through the transaction information. Among them, the adjustment-related information set includes a rule information set and an adjustment information set; the adjustment information set includes: the adjustment quotas corresponding to multiple cycle types. The server determines the adjustment result based on the amount and transaction time in the transaction information, as well as the rule information set and the adjustment information set.

[0072] Exemplarily, in combination with Figure 2 , the adjustment result can be explained by the direct payment adjustment transaction record form. Among them, the adjustment result may include an adjustment transaction ID, and the adjustment transaction ID is used to represent the direct payment amount and the out-of-pocket amount of this transaction. It also includes an adjustment ID, a direct payment record ID, a change type (used to represent whether the local transaction is to deduct the amount or refund the amount), the adjustment quota JSON before the change, the adjustment quota JSON for the change, the adjustment quota JSON after the change, and the data version after the change (used as the basis for processing idempotency and the CAS (check and set) judgment for database operations). Direct payment adjustment transaction record form: It is used to record the specific transaction data of each quota change. It mainly includes the quota before the change, the quota for the change, and the quota after the change.

[0073] In the embodiment of the present application, the adjustment information set includes: the used deductible amounts, the number of claim settlements, and the claim settlement upper limits corresponding to multiple cycle types respectively.

[0074] Among them, multiple cycle types may include: daily cycle type, weekly cycle type, monthly cycle type, quarterly cycle type, and annual cycle type. In other embodiments, the cycle type may also include cycle types of other durations, and in the embodiment of the present application, no specific limitation is made.

[0075] In the embodiments of the present application, the adjustment information set includes: a first correspondence between each period corresponding to each period type and the deductible amount already used, a second correspondence between each period corresponding to each period type and the number of claim settlements, and a third correspondence between each period corresponding to each period type and the claim settlement limit;

[0076] The adjustment information set further includes: a user quota identifier and the current data version. Among them, the user quota identifier is used by the user to query and determine the quota corresponding to the user.

[0077] Among them, the first correspondence may include key-value pairs (key, value) in JSON format between each period and the corresponding deductible amount already used. The second correspondence may include key-value pairs in JSON format between each period and the corresponding number of claim settlements. The third correspondence may include key-value pairs in JSON format between each period and the claim settlement limit.

[0078] In the embodiments of the present application, the first correspondence, the second correspondence, and the third correspondence corresponding to each period type are stored in the storage order respectively; based on the maximum storage quantity corresponding to the first correspondence, the second correspondence, and the third correspondence corresponding to each period type respectively, the earliest stored correspondence is dynamically eliminated.

[0079] Among them, if the storage quantity of the correspondence in any period of any period type exceeds the maximum storage quantity corresponding to this period, the earliest stored correspondence in this period is deleted.

[0080] Exemplarily, in combination with Figure 2, the settlement information set can be described by the direct settlement form. The direct settlement form includes a settlement ID (used to represent the user's specific quota), the current data version (used for idempotency processing and is the basis for CAS judgment in database operations), and the settlement quota JSON, mainly including the deductible, the number of claims, the claim limit, which are respectively accumulated over daily, monthly, and annual cycles. There are a total of 9 fields. The type of each field is BoundedMap<K, V>. BoundedMap<K, V> mainly has two parameters, maxSize and LinkedHashMap<K, V>; maxSize is used to mark the maximum number of LinkedHashMap in the corresponding cycle. The LinkedHashMap type can ensure the order of insertion. BoundedMap provides a put method. When inserting elements into LinkedHashMap, it will be judged based on maxSize. If the size of LinkedHashMap has reached maxSize, the first inserted element will be removed. The specific implementation is because LinkedHashMap can guarantee the insertion order, and traversing the first one is the earliest inserted element. The key of LinkedHashMap is the specific quota cycle (example: daily cycle: 20240815, monthly cycle 20240815 - 20240914, annual cycle 20240815 - 20250814), and the value is the quota used in the current cycle. The quota types are divided into BigDecimal (amount type, deductible and claim limit) and Integer (number of claims type, number of claims); therefore, BoundedMap adopts a generic design method.

[0081] In the embodiments of the present application, the rule information set includes: a business rule information set and a user rule information set;

[0082] Among them, the business rule information set includes: a preset business type identifier and the corresponding deductible, number of claims, claim limit, and claim ratio; the user rule information set includes: the preset business type identifier, user quota identifier, information set identifier, and business start and end times.

[0083] Exemplarily, combined with Figure 2 , the business rule information set can be described by the direct payment card configuration form. The direct payment card configuration form: used to store business rule parameters, related to the limit control fee model, including deductible, number of claims, claim limit, claim ratio, etc.

[0084] Exemplarily, combined with Figure 2 , the user rule information set can be described by the user direct payment card table. The user direct payment card table: simply understood as a user account attribute table, related to the limit control fee model, including the settlement ID, and one settlement ID represents one quota data. One user direct payment card account is uniquely associated with one quota data.

[0085] In an embodiment of the present application, after the server obtains the transaction information, it can find the corresponding actuarial-related information set of the user through the transaction information. That is, the server can obtain the user direct payment record form corresponding to the transaction operation, and can determine the user direct payment card form (user rule information set) and the direct payment actuarial form (actuarial information set) through the actuarial ID in the user direct payment record form. Then, the corresponding direct payment card configuration form (business rule information set) is determined through the direct payment card configuration ID in the user direct payment card form.

[0086] In an embodiment of the present application, by obtaining transaction information; based on the transaction information and the actuarial-related information set, an actuarial result is determined; wherein, the actuarial-related information set includes a rule information set and an actuarial information set; the actuarial information set includes: actuarial amounts corresponding to multiple cycle types respectively. In this way, the actuarial amounts corresponding to multiple cycle types are combined and stored in one actuarial information set. When performing actuarial calculations for transaction information, fewer information records are called, and less computing resources are occupied, thereby improving the actuarial efficiency.

[0087] Please refer to Figure 3 , which is an optional process schematic diagram of the insurance data actuarial method provided by the embodiment of the present application, Figure 1 S102 shown can also be implemented through S201 to S204, and will be described in combination with the steps:

[0088] S201. Check the business start and end times in the transaction information and the rule information set to determine the first check result.

[0089] In an embodiment of the present application, the server first needs to check the deduction amount, the first transaction time in the transaction information, and the business start and end times in the rule information set to determine the first verification result used to represent whether the check passes.

[0090] In an embodiment of the present application, the server first needs to perform parameter verification, which includes basic parameter non-emptiness, legal verification of deduction amount > 0, and verification that the business start and end times and the first transaction time must be within the business start and end times. In the outpatient insurance scenario, the prescription validity period is 3 days, which restricts that the actuarial time cannot be < 10 days from the current time.

[0091] S202. When the first check result indicates that the check passes, based on the first transaction time, determine the first current transaction cycle corresponding to each of the multiple cycle types.

[0092] In the embodiments of the present application, when the deducted amount verified by the server is >0 and the first transaction time is between the start and end times of the business, the server determines the first verification result indicating successful verification. Based on the first transaction time, the server determines the first current transaction cycle corresponding to each of the multiple cycle types for the first transaction time.

[0093] In the embodiments of the present application, the server can determine the key of the first transaction cycle corresponding to each of the multiple cycle types for the first transaction time based on the cycle corresponding to the first transaction time in the start and end times of the business. Exemplarily, the determined key for the daily cycle can be: 20240815.

[0094] S203. Based on the first current transaction cycle, determine the compensation upper limit and the deductible amount already used corresponding to each of the multiple cycle types in the adjustment information set.

[0095] In the embodiments of the present application, the server queries in the adjustment information set based on the first current transaction cycle corresponding to each of the multiple cycle types, and determines the compensation upper limit and the deductible amount already used corresponding to each of the multiple cycle types.

[0096] In the embodiments of the present application, the server can query the corresponding value in the adjustment information set based on the key of the first current transaction cycle corresponding to each cycle type, and determine the compensation upper limit and the deductible amount already used corresponding to each of the multiple cycle types.

[0097] S204. Based on the compensation upper limit, the deductible amount already used, and the adjustment information set, determine the adjustment result.

[0098] In the embodiments of the present application, the server can determine the remaining amount based on the compensation upper limit and the deductible amount already used, then determine the direct payment amount, the out-of-pocket amount, the adjusted amount JSON, the changed amount JSON, and the pre-changed amount JSON based on the remaining amount, and then combine the changed data version to determine the adjustment result.

[0099] In the embodiments of the present application, verify the start and end times of the business in the transaction information and the rule information set to determine the first verification result; when the first verification result indicates successful verification, determine the first current transaction cycle corresponding to each of the multiple cycle types based on the first transaction time; based on the first current transaction cycle, determine the compensation upper limit and the deductible amount already used corresponding to each of the multiple cycle types in the adjustment information set; based on the compensation upper limit, the deductible amount already used, and the adjustment information set, determine the adjustment result. In this way, the compensation upper limit and the deductible amount already used can be directly determined in the adjustment information set, without calling a relatively large number of data record tables, saving computing resources, and compared with the solutions in the related art, the efficiency of determining the adjustment effect can be improved.

[0100] Please refer toFigure 4 , which is an optional process schematic diagram of the insurance data adjustment method provided by the embodiments of the present application. Figure 1 The S204 shown can also be implemented through S301 to S303, and will be described in combination with the steps:

[0101] S301. Determine the remaining amount based on the compensation limit and the deductible already used.

[0102] In the embodiments of the present application, the server determines the remaining amount by subtracting the deductible already used from the amount characterized by the compensation limit.

[0103] S302. Determine the minimum amount between the remaining amount and the preset direct payment amount as the direct payment amount; wherein, the preset direct payment amount is determined based on the deduction amount and the compensation ratio in the business rule information.

[0104] In the embodiments of the present application, the server can compare the remaining amount and the preset direct payment amount, and determine the minimum amount between the remaining amount and the preset direct payment amount as the direct payment amount. Wherein, the preset direct payment amount is determined based on the deduction amount and the compensation ratio in the business rule information.

[0105] In the embodiments of the present application, the server can use the deduction amount as the temporary direct payment amount, multiply it by the compensation ratio in the business rule information set, and determine the preset direct payment amount.

[0106] S303. Determine the adjustment result based on the direct payment amount and the adjustment information set.

[0107] In the embodiments of the present application, the server can determine the out-of-pocket amount based on the deduction amount minus the direct payment amount, then determine the adjusted deductible JSON, the current change in deductible JSON, and the deductible already used JSON corresponding to multiple cycle types respectively based on the direct payment amount and the deductible already used corresponding to multiple cycle types respectively, and then combine the adjusted data version to determine the adjustment result.

[0108] In the embodiments of the present application, the server determines the out-of-pocket amount based on the direct payment amount and the deduction amount; determines the adjusted deductible and the current change in deductible based on the direct payment amount and the deductible already used corresponding to multiple cycle types respectively in the adjustment information set; determines the adjustment result based on the deduction amount, the direct payment amount, the out-of-pocket amount, the adjusted data version, the adjusted deductible, the current change in deductible, the deductible already used, and a predetermined string; wherein, the predetermined string is used to represent whether to write a transaction record for the transaction information.

[0109] In the embodiments of the present application, the server may determine the changed deductible JSON and the current changed deductible JSON corresponding to multiple cycle types respectively based on the key of the first current transaction cycle corresponding to each cycle type, the corresponding changed deductible, and the current changed deductible for this time.

[0110] In the embodiments of the present application, if the server determines that there is no used deductible, or the number of claim payments, or the claim limit corresponding to the first current transaction cycle for any cycle type, that is, there is no corresponding relationship for the first current transaction cycle, the server determines a new corresponding relationship for the first current transaction cycle based on the key corresponding to the first current transaction cycle, stores the new corresponding relationship in the adjustment information set in sequence, and deletes the earliest stored corresponding relationship of this cycle type at the same time.

[0111] In the embodiments of the present application, the server updates the first corresponding relationship corresponding to the first current transaction cycle for multiple cycle types respectively based on the changed deductible, and updates the number of claim payments in the second corresponding relationship corresponding to the first current transaction cycle for multiple cycle types respectively.

[0112] Among them, the server may update the used deductible in the first corresponding relationship corresponding to the first current transaction cycle for multiple cycle types respectively based on the changed deductible corresponding to multiple cycle types.

[0113] Among them, the server may determine the second corresponding relationship corresponding to the first current transaction cycle for multiple cycle types respectively, and the server may also update the number of claim payments in multiple second corresponding relationships based on the current deduction amount transaction. That is, add 1 to the number of claim payments in the second corresponding relationship.

[0114] In the embodiments of the present application, when determining the direct payment amount for daily, monthly, and annual cycle types, first, based on the first transaction time and the business start and end times, obtain the key corresponding to the daily, monthly, and annual cycle types. Secondly, through the cycle key, from the data structure in the quota JSON of the adjustment information set, the used deductible and the claim limit corresponding to the daily, monthly, and annual cycle types respectively can be obtained. Then, based on the claim limit and the used deductible, the remaining quota for multiple cycle types can be calculated. Finally, compare the preset direct payment amount with the remaining quota, and take the smaller value as the direct payment amount. After determining the direct payment amount, it is also necessary to process the quota change, including the current changed deductible JSON and the changed deductible JSON. Here, based on the direct payment amount, the current changed deductible and the changed deductible for daily, monthly, and annual multiple cycle types are processed respectively. The processing logic is to first obtain the cycle key corresponding to multiple cycle types respectively, then read the used quota within the cycle, process the quota changed this time as the direct payment amount, and the changed quota is the used deductible corresponding to each cycle type plus the direct payment amount.

[0115] In the embodiment of the present application, based on the compensation upper limit and the used deductible, the remaining amount is determined; the minimum amount between the remaining amount and the preset direct payment amount is determined as the direct payment amount; wherein, the preset direct payment amount is determined based on the deduction amount and the compensation ratio in the business rule information; based on the direct payment amount and the set of adjustment information, the adjustment result is determined. In this way, the adjusted deductible and the current amount can be determined based on the used deductibles corresponding to multiple cycle types in the set of adjustment information, without calling a relatively large number of data record tables, saving computing resources. Compared with the solutions in the related art, the efficiency of determining the adjustment effect can be improved.

[0116] Before S303 shown, S401 may further be included, which will be described in combination with the steps:

[0117] S401. If a single - limit amount is set in the rule information set, determine the minimum amount between the preset direct payment amount and the single - limit amount as the direct payment amount.

[0118] In the embodiment of the present application, if a single - limit amount is set in the rule information set, the server determines the minimum amount between the preset direct payment amount and the single - limit amount as the direct payment amount. If a single - limit amount is set in the rule information set, the predetermined string in the adjustment result is used to indicate not writing a transaction record for the transaction information.

[0119] Please refer to Figure 5 , which is an optional process schematic diagram of the insurance data adjustment method provided by the embodiment of the present application. Figure 1 Before S102 shown, it may also be implemented by including S501 to S503, which will be described in combination with the steps:

[0120] S501. Verify the transaction information to determine a second verification result.

[0121] In the embodiment of the present application, when the transaction information includes: a refund amount and a second transaction time; the server verifies the refund amount in the transaction information to determine a second verification result.

[0122] In the embodiment of the present application, the server needs to perform parameter verification on the transaction information, that is, perform a legality verification of refund amount > 0.

[0123] S502. When the second verification result indicates that the verification is passed, based on the second transaction time, determine the second current transaction cycle corresponding to each of the multiple cycle types.

[0124] In an embodiment of the present application, when the server verifies that the refund amount > 0, it determines a second verification result indicating successful verification. Based on the second transaction time, the server determines the second current transaction cycles corresponding to multiple cycle types for the second transaction time.

[0125] In an embodiment of the present application, the server can determine the key of the second transaction cycles corresponding to multiple cycle types for the second transaction time based on the cycle corresponding to the second transaction time in the business start and end times.

[0126] S503. Determine the adjustment result based on the refund amount and the used deductibles corresponding to multiple second current transaction cycles in the adjustment information set.

[0127] In an embodiment of the present application, the server determines the adjusted deductible and the current change in deductible based on the refund amount and the used deductibles corresponding to multiple second current transaction cycles in the adjustment information set; determines the adjustment result based on the refund amount, the change data version, the adjusted deductible, the current change in deductible, the used deductible, and a predetermined string. Here, the predetermined string is used to indicate not writing a transaction record for the transaction information.

[0128] In an embodiment of the present application, the server can update the used deductible in the first correspondence of the second current transaction cycles corresponding to multiple cycle types based on the adjusted deductibles corresponding to multiple cycle types.

[0129] In an embodiment of the present application, the server can determine the second correspondence of the second current transaction cycles corresponding to multiple cycle types, and the server can also update the claim times in multiple second correspondences based on the current refund amount transaction. That is, subtract 1 from the claim times in the second correspondence.

[0130] In an embodiment of the present application, calculate the change in the claim amount. Here, it is similar to the positive deduction part, but in the refund scenario, there is no need to calculate. Just directly process the quota change based on the refund amount. Obtain the input refund amount and process the adjusted deductible and the current change in deductible for multiple cycle types of day, month, and year respectively. The processing logic is to first obtain the key of the second current transaction cycle, then read the used quota corresponding to the second current transaction cycle in multiple cycle types, process the quota change for this time as the refund amount, and the changed quota is the used quota within the cycle + the refund amount (the refund amount is negative).

[0131] In the embodiment of the present application, the transaction information is verified to determine a second verification result. When the second verification result indicates that the verification is passed, the second current transaction period corresponding to the plurality of period types is determined based on the second transaction time. The settlement result is determined based on the refund amount and the plurality of second current transaction periods in the settlement information set. In this way, the deductible after the change can be determined based on the second current transaction period corresponding to the plurality of period types in the settlement information set, without calling a relatively large number of data record tables, thus saving computing resources and improving the efficiency of determining the settlement effect compared to the solutions in the related art.

[0132] See also Figure 6 , which is a schematic diagram of the effect of the insurance data adjustment component provided in an embodiment of the present application.

[0133] The design of the calculation module is mainly divided into three parts: input parameters, output parameters and calculation components. The calculation component is positioned as a pure calculation operation. All the methods provided to the outside are static methods with the best performance.

[0134] Input parameters: JSON of the settlement amount used for calculation, data version; rule parameters used for calculation; policy start and end time (business start and end time), used to process the calculation of the cycle key. Settlement amount (deduction amount and refund amount), the amount to be calculated this time. Transaction time, used to process the cycle.

[0135] Adjustment component: There are four main methods. The logic of positive deduction and reverse refund is relatively complex and is equipped with a flow chart. Figure 7 and Figure 9 The process explanation in . Here is a brief explanation of the two methods of settlement verification and direct payment result verification. Settlement verification method: Applied to the pre-claim verification, mainly to verify whether there is any remaining amount that can be used for claims. The specific logic is to determine whether there is any remaining amount by comparing the used amount of the period to which the current settlement time belongs and the upper limit configured in the settlement rules. Method for verifying direct payment settlement results: The positioning is to prevent the inconsistency between the settlement results stored in the database and the initial calculation due to the modification of the settlement results by other codes after the settlement calculation is completed and when the database is actually written. This is mainly a safety bottom-up verification.

[0136] Output parameters: the result of this settlement, including the input parameters: settlement amount (deduction amount and refund amount), changed data version, direct payment amount, self-paid amount, whether to write transaction records (only for single transaction restriction scenario, no transaction records are required); the deductible amount of this change, the deductible amount after the change, and the deductible amount before the change.

[0137] See also Figure 7 , which is an optional flow chart of the insurance data adjustment method provided in the embodiment of the present application, will be described in combination with the steps:

[0138] S11. Parameter verification.

[0139] In the embodiments of the present application, parameter verification includes basic parameter non - emptiness, the legality verification that the amount > 0, as well as the verification of the start and end times of the insurance policy, and the verification that the adjustment time must be within the start and end times of the insurance policy. In the outpatient insurance scenario, the prescription validity period is 3 days, which restricts that the adjustment time cannot be < 10 days from the current time.

[0140] S12. Verify whether only a single - limit is set.

[0141] In the embodiments of the present application, verify whether the verification rule only sets a single - limit. For a single - limit, no amount accumulation processing is required. Therefore, no adjustment amount management and amount transaction flow are needed.

[0142] S13. Initialize the adjustment result.

[0143] In the embodiments of the present application, initializing the adjustment result means that the calculation of the adjustment amount goes through several processes. Initialization is just to temporarily store the result for subsequent calculation steps. By default, the initialized adjustment amount is the direct - payment amount, and the out - of - pocket amount is 0. If it is only a single - limit, mark it and do not process the amount and flow fields. The adjustment amount before change is the input adjustment amount. The comfortable change amount is an empty object.

[0144] S14. Calculate the deductible.

[0145] In the embodiments of the present application, for the specific steps, please refer to S16.

[0146] S15. Calculate the preset direct - payment amount.

[0147] In the embodiments of the present application, it can be obtained by multiplying the default direct - payment amount by the ratio.

[0148] S16. Calculate the claim amount limit.

[0149] In the embodiments of the present application, when calculating the claim amount limit, calculate the single - item limit, daily limit, monthly limit, and annual limit in sequence. There is no order among them. Adopting the "funnel thinking" and "barrel principle", take the minimum value to replace the direct payment amount. After the calculation is completed, the final direct payment amount can be obtained. Among them, for the single - item limit processing, directly compare the direct payment amount with the preset direct payment amount configured, and take the smaller value. For the daily, monthly, and annual limits, first, based on the first transaction time and the business start - end time, obtain the key corresponding to the first current transaction cycle. The key values for different cycles can refer to the examples in the flow chart. Secondly, through the cycle key, the used amount can be obtained from the data structure in the quota JSON. Then, based on the configured claim upper limit, the remaining amount for the first current transaction cycle can be calculated. Finally, compare the direct payment amount with the current remaining amount, take the smaller value, and replace the default direct payment amount. The direct payment amount can be used to handle the quota change in the first current transaction cycle, including the deductible JSON for this change and the changed deductible JSON. Here, when obtaining the direct payment amount, handle the deductible JSON for this change and the changed deductible JSON for the daily, monthly, and annual cases respectively. The processing logic is to first obtain the key of the first current transaction cycle, then read the used amount within the cycle, handle the changed amount as the direct payment amount, and the changed amount is the used amount within the cycle plus the direct payment amount.

[0150] S17. Calculate the claim times limit.

[0151] In the embodiments of the present application, based on the transaction time and the business start - end time, obtain the key corresponding to the first current transaction cycle. The key values for different cycles can refer to the examples in the flow chart. Secondly, determine the corresponding second correspondence from the data structure in the claim times JSON through the cycle key, and update the claim times in the second correspondence (claim times + 1).

[0152] Please refer to Figure 8 , which is an optional flow schematic diagram of the insurance data adjustment method provided by the embodiments of the present application, and will be described in combination with the steps:

[0153] S21. Parameter verification.

[0154] In the embodiments of the present application, here reuse the basic parameter verification of the forward deduction, including non - null and legality. For refunds, there is no need for legality verification related to the business start - end time.

[0155] S22. Verify whether only the single - item limit is set.

[0156] In the embodiments of the present application, verify whether only the single - item limit is set in the business rule information set. In the single - item limit scenario only, there is no need for quota and no need for refund.

[0157] S23. Initialize the refund adjustment result.

[0158] In the embodiment of the present application, the refund settlement result is initialized. Generally, it is similar to the forward deduction, but when it comes to reverse refund, the direct payment amount is processed as a negative number to facilitate subsequent calculation and processing. Since the quota stores the used quota within a cycle, the forward deduction is cumulative and the reverse refund is a deduction. By processing it as a negative number, all subsequent code calculations can be handled using the add operation, which is convenient for code reuse.

[0159] S24. Whether there is only a single - transaction limit.

[0160] In the embodiment of the present application, the server detects whether there is only a single - transaction limit set in the business rule information set. If it is set, the process ends. If there is no single - transaction limit set, then S25 is executed.

[0161] S25. Calculate the change in the deductible amount.

[0162] In the embodiment of the present application, first obtain the second current transaction cycle key, then read the used quota within the cycle, process the quota change for this time as the refund amount, and the changed quota is the used quota within the cycle + the refund amount.

[0163] S26. Calculate the change in the indemnity amount.

[0164] In the embodiment of the present application, calculate the change in the indemnity amount. Here, it is similar to the forward - deduction part, but in the refund scenario, there is no need to calculate. Just directly process the quota change based on the input refund amount. After obtaining the input refund amount, process the current change in the deductible amount and the changed deductible amount for multiple cycle types, namely daily, monthly, and yearly.

[0165] S27. Calculate the change in the number of indemnity claims.

[0166] In the embodiment of the present application, based on the transaction time and the start - end time of the business, obtain the corresponding second current transaction cycle key. The key values for different cycles can refer to the examples in the flowchart. Secondly, determine the corresponding second correspondence from the data structure in the indemnity - claim number JSON through the cycle key, and update the indemnity - claim number in the second correspondence (indemnity - claim number - 1).

[0167] Please refer to Figure 9 , which is the structural schematic diagram of the insurance data settlement device provided by the embodiment of the present application.

[0168] The embodiment of the present application further provides an insurance data settlement device 800, including: an information acquisition unit 801 and a settlement unit 802.

[0169] The information acquisition unit 801 is used to acquire transaction information;

[0170] An adjustment unit 802, configured to determine an adjustment result based on the transaction information and an adjustment-related information set; wherein, the adjustment-related information set includes a rule information set and an adjustment information set; the adjustment information set includes: adjustment amounts corresponding to multiple cycle types.

[0171] In an embodiment of the present application, the adjustment information set includes: used deductibles, claim numbers, and claim limits respectively corresponding to multiple cycle types.

[0172] In an embodiment of the present application, the adjustment information set includes: a first correspondence between each cycle corresponding to each cycle type and the used deductible, a second correspondence between each cycle corresponding to each cycle type and the claim number, and a third correspondence between each cycle corresponding to each cycle type and the claim limit;

[0173] The adjustment information set further includes: a user quota identifier and a current data version.

[0174] In an embodiment of the present application, the first correspondence, the second correspondence, and the third correspondence respectively corresponding to each cycle type are stored in the storage order; the adjustment unit 802 in the insurance data adjustment device 800 is configured to dynamically eliminate the earliest stored correspondence based on the maximum storage quantity respectively corresponding to the first correspondence, the second correspondence, and the third correspondence corresponding to each cycle type.

[0175] In an embodiment of the present application, the rule information set includes: a service rule information set and a user rule information set;

[0176] Wherein, the service rule information set includes: a preset service type identifier and corresponding deductible, claim number, claim limit, and claim ratio; the user rule information set includes: the preset service type identifier, user quota identifier, information set identifier, and service start and end times.

[0177] In an embodiment of the present application, when the transaction information includes: a deduction amount and a first transaction time; the adjustment unit 802 in the insurance data adjustment device 800 is configured to verify the first transaction time in the transaction information and the service start and end times in the rule information set to determine a first verification result;

[0178] When the first verification result indicates that the verification is passed, based on the first transaction time, determine a first current transaction cycle respectively corresponding to multiple cycle types;

[0179] Based on the first current transaction cycle in the adjustment information set, determine the claim limits and used deductibles respectively corresponding to multiple cycle types;

[0180] Determine the adjustment result based on the compensation limit, the used deductible, and the set of adjustment information.

[0181] In an embodiment of the present application, the adjustment unit 802 in the insurance data adjustment device 800 is configured to determine the remaining amount based on the compensation limit and the used non - compensation amount.

[0182] Determine the minimum amount between the remaining amount and the preset direct payment amount as the direct payment amount; wherein, the preset direct payment amount is determined based on the deducted amount and the compensation ratio in the business rule information.

[0183] Determine the adjustment result based on the direct payment amount and the set of adjustment information.

[0184] In an embodiment of the present application, the adjustment unit 802 in the insurance data adjustment device 800 is configured to determine the out - of - pocket amount based on the direct payment amount and the deducted amount.

[0185] Based on the direct payment amount and the used deductible of the first current transaction corresponding to multiple cycle types in the set of adjustment information, determine the adjusted deductible and the deductible change for this time.

[0186] Based on the deducted amount, the direct payment amount, the out - of - pocket amount, the change data version, the adjusted deductible, the deductible change for this time, the used deductible, and a predetermined string, determine the adjustment result; wherein, the predetermined string is used to represent writing a transaction record for the transaction information.

[0187] In an embodiment of the present application, the adjustment unit 802 in the insurance data adjustment device 800 is configured to update the first correspondence relationship of the first current transaction cycle corresponding to multiple cycle types based on the adjusted deductible, and update the claim times in the second correspondence relationship of the first current transaction cycle corresponding to multiple cycle types.

[0188] In an embodiment of the present application, the adjustment unit 802 in the insurance data adjustment device 800 is configured to, if a single - transaction limit amount is set in the rule information set, determine the minimum amount between the preset direct payment amount and the single - transaction limit amount as the direct payment amount.

[0189] In an embodiment of the present application, the adjustment unit 802 in the insurance data adjustment device 800 is configured to perform a verification on the transaction information to determine a second verification result.

[0190] In the case where the second verification result indicates that the verification is passed, based on the second transaction time, determine the second current transaction cycle corresponding to multiple cycle types.

[0191] Determine the adjustment result based on the refund amount and the used deductible amounts corresponding to multiple second current transaction cycles in the adjustment information set.

[0192] In the embodiments of the present application, the adjustment unit 802 in the insurance data adjustment device 800 is configured to determine the adjusted deductible amount and the current change in deductible amount based on the refund amount and the used deductible amounts corresponding to multiple second current transaction cycles in the adjustment information set;

[0193] Determine the adjustment result based on the refund amount, the change data version, the adjusted deductible amount, the current change in deductible amount, the used deductible amount, and a predetermined string; wherein the predetermined string is used to indicate not writing a transaction record for the transaction information.

[0194] It should be noted that in the embodiments of the present application, if the above-mentioned insurance data adjustment method is implemented in the form of software function modules and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of the present application essentially or the part that contributes to the related art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions to enable an adjustment device (which can be a personal computer, etc.) to execute all or part of the methods described in the embodiments of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROMs), magnetic disks, or optical discs that can store program codes. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0195] Correspondingly, the embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps in the insurance data adjustment method are implemented.

[0196] It should be pointed out here that: the descriptions of the above storage medium and device embodiments are similar to those of the above method embodiments and have similar beneficial effects to the method embodiments. For the technical details not disclosed in the storage medium and device embodiments of the present application, please refer to the descriptions of the method embodiments of the present application for understanding.

[0197] It should be noted that Figure 10 is a schematic diagram of a hardware entity of an electronic device provided in the embodiments of the present application. As Figure 10 shown, the embodiments of the present application provide an electronic device 900, including a memory 902 and a processor 901. The memory 902 stores a computer program that can run on the processor 901, and when the processor 901 executes the program, the steps in the above method are implemented, where;

[0198] The processor 901 generally controls the overall operation of the electronic device 900.

[0199] The memory 902 is configured to store instructions and applications executable by the processor 901, and can also cache data to be processed or already processed by the processor 901 and each module in the electronic device 900 (for example, image data, audio data, voice communication data, and video communication data), and can be implemented by flash memory (FLASH) or random access memory (Random Access Memory, RAM).

[0200] Correspondingly, an embodiment of the present application further provides a computer program product, including a computer program, which can be executed by the processor 901 of the electronic device 900 to complete the steps in the method on the side of the insurance data adjustment device 800.

[0201] It should be understood that the "one embodiment" or "an embodiment" mentioned throughout the specification means that the specific features, structures, or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the "in one embodiment" or "in an embodiment" that appears throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the sequence numbers of the above processes do not mean the order of execution is prior or subsequent. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. The sequence numbers of the embodiments of the present application above are only for description and do not represent the advantages or disadvantages of the embodiments.

[0202] It should be noted that in this article, the term "including", "comprising", or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article, or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article, or device. Without further limitation, the element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article, or device including the element.

[0203] In several embodiments provided by the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined, or can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed with each other can be through some interfaces. The indirect coupling or communication connection of the devices or units can be electrical, mechanical, or other forms.

[0204] The units described above as separate components may or may not be physically separated. The components shown as units may or may not be physical units; they can be located in one place or distributed to multiple network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0205] In addition, each functional unit in the embodiments of the present application can be all integrated in a processing unit, or each unit can be separately used as a unit, or two or more units can be integrated in a unit; the above integrated unit can be implemented in the form of hardware, or in the form of a combination of hardware and software functional units.

[0206] Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions. The foregoing program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps including the above method embodiments; and the foregoing storage medium includes: removable storage devices, read-only memory (ROM), magnetic disks, or optical disks, etc., which can store program codes.

[0207] Alternatively, if the above integrated unit of the present application is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiments of the present application essentially or the part that contributes to the related technology can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in the embodiments of the present application. And the foregoing storage medium includes: removable storage devices, ROM, magnetic disks, or optical disks, etc., which can store program codes.

[0208] As described above, it is only the implementation mode of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application.

Claims

1. An insurance data adjustment method, characterized in that, Including: Obtain transaction information; Based on the transaction information and the set of adjustment-related information, determine the adjustment result; wherein, the set of adjustment-related information includes a set of rule information and a set of adjustment information; the set of adjustment information includes: adjustment amounts corresponding to multiple cycle types.

2. The insurance data adjustment method according to claim 1, wherein, The set of adjustment information includes: used deductibles, claim frequencies, and claim limits corresponding to multiple cycle types respectively.

3. The insurance data adjustment method according to claim 2, wherein, The set of adjustment information includes: a first correspondence relationship between each cycle corresponding to each cycle type and the used deductible, a second correspondence relationship between each cycle corresponding to each cycle type and the claim frequency, and a third correspondence relationship between each cycle corresponding to each cycle type and the claim limit; The set of adjustment information further includes: a user quota identifier and the current data version.

4. The insurance data adjustment method according to claim 3, wherein The first correspondence relationship, the second correspondence relationship, and the third correspondence relationship corresponding to each cycle type are stored in the storage order respectively; the method further includes: Based on the maximum storage quantities corresponding to the first correspondence relationship, the second correspondence relationship, and the third correspondence relationship corresponding to each cycle type respectively, dynamically eliminate the earliest stored correspondence relationship.

5. The insurance data adjustment method according to claim 1, characterized in that The set of rule information includes: a set of business rule information and a set of user rule information; Wherein, the set of business rule information includes: a preset business type identifier and the corresponding deductible, claim frequency, claim limit, and claim ratio; the set of user rule information includes: the preset business type identifier, user quota identifier, information set identifier, and business start and end times.

6. The insurance data adjustment method according to any one of claims 1 to 5, characterized in that, When the transaction information includes: a deduction amount and a first transaction time; the determining the adjustment result based on the transaction information and the set of adjustment-related information includes: Perform a verification on the business start and end times in the transaction information and the set of rule information to determine a first verification result; When the first verification result indicates that the verification is passed, based on the first transaction time, determine the first current transaction cycle corresponding to multiple cycle types respectively; Based on the first current transaction cycle in the set of adjustment information, determine the claim limits and used deductibles corresponding to multiple cycle types respectively; Based on the claim limit, the used deductible, and the set of adjustment information, determine the adjustment result.

7. The insurance data adjustment method according to claim 6, wherein The determining the adjustment result based on the claim limit, the used deductible, and the set of adjustment information includes: Based on the claim limit and the used deductible, determine the remaining amount; Determine the minimum amount between the remaining amount and a preset direct payment amount as the direct payment amount; wherein, the preset direct payment amount is determined based on the deduction amount and the claim ratio in the business rule information; Based on the direct payment amount and the set of adjustment information, determine the adjustment result.

8. The insurance data adjustment method according to claim 7, wherein The determining the adjustment result based on the direct payment amount and the set of adjustment information includes: Based on the direct payment amount and the deduction amount, determine the out-of-pocket amount; Based on the direct payment amount and the used deductibles of the first current transaction corresponding to multiple cycle types in the set of adjustment information, determine the adjusted deductible and the deductible change for this time; Determine the adjustment result based on the deduction amount, the direct payment amount, the out-of-pocket amount, the change data version, the adjusted deductible, the current change in deductible, the used deductible, and a predetermined string; wherein the predetermined string is used to represent writing a transaction record for the transaction information.

9. The insurance data adjustment method according to claim 7, wherein The method further includes: Update the first correspondence relationships respectively corresponding to the first current transaction cycles of multiple cycle types based on the adjusted deductible, and update the claim times in the second correspondence relationships respectively corresponding to the first current transaction cycles of multiple cycle types.

10. The insurance data adjustment method according to claim 7, wherein Before determining the adjustment result based on the direct payment amount and the adjustment information set, the method further includes: If a single-transaction limit amount is set in the rule information set, determine the minimum amount between the preset direct payment amount and the single-transaction limit amount as the direct payment amount.

11. The insurance data adjustment method according to any one of claims 1 to 5, characterized in that, When the transaction information includes: a refund amount and a second transaction time; determining the adjustment result based on the transaction information and the adjustment-related information set includes: Perform a verification on the transaction information to determine a second verification result; When the second verification result indicates that the verification is passed, determine the second current transaction cycles respectively corresponding to multiple cycle types based on the second transaction time; Determine the adjustment result based on the refund amount and the used deductibles respectively corresponding to multiple second current transaction cycles in the adjustment information set.

12. The adjustment method according to claim 11, wherein The determining the adjustment result based on the refund amount and the used deductibles respectively corresponding to multiple second current transaction cycles in the adjustment information set includes: Determine the adjusted deductible and the current change in deductible based on the refund amount and the used deductibles respectively corresponding to multiple second current transaction cycles in the adjustment information set; Determine the adjustment result based on the refund amount, the change data version, the adjusted deductible, the current change in deductible, the used deductible, and a predetermined string; wherein the predetermined string is used to represent not writing a transaction record for the transaction information.

13. An insurance data adjustment device, characterized in that, It includes: An information acquisition unit, configured to acquire transaction information; An adjustment unit, configured to determine an adjustment result based on the transaction information and an adjustment-related information set; wherein the adjustment-related information set includes a rule information set and an adjustment information set; the adjustment information set includes: adjustment amounts corresponding to multiple cycle types.

14. An electronic device, characterized in that, It includes a memory and a processor, the memory stores a computer program that can run on the processor, and when the processor executes the computer program, it implements the steps in the method according to any one of claims 1 to 12.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps in the method according to any one of claims 1 to 12.

16. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps in the method according to any one of claims 1 to 12.

Images