Decision-making method and system and storage medium

Abstract

The invention discloses a decision-making method and system and a storage medium. The method comprises the steps of obtaining a health service event; determining a corresponding health service product based on the health service event; and based on a matching rule table and business scene information corresponding to the health service event, determining a service provider corresponding to the health service product, the matching rule table being used for representing a corresponding relationship between the health service product and the service provider in different business scenes. According to the method, real service providers are dynamically managed, a code form is not needed any more, and supplier decision-making can be carried out on a complex business scene only by carrying out corresponding configuration, so that the business requirements are met.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a decision-making method, system and storage medium. Background Art

[0002] In the insurance industry, insurance companies often use health service products as a tool to acquire and retain customers, and often use them as value-added services for insurance policies. Therefore, insurance companies will sign contracts with multiple service providers for the same health service item / health service product.

[0003] The existing technology completes the demand by creating multiple identical health service products to assist in code logic judgment. The service items need to be defined multiple times, and the service products also need to be defined multiple times. Even if the customer sees the same health service products, once a new scenario appears, it is necessary to use code to determine which service item and service product to use, which leads to slow response speed and high maintenance costs. Therefore, in scenarios with different sales channels, different customer groups, and different time periods, how to flexibly match the most suitable supplier according to scenario requirements has become an urgent problem to be solved. Summary of the invention

[0004] Based on the above problems, the present application provides a decision-making method, system and storage medium.

[0005] The embodiments of the present application disclose the following technical solutions:

[0006] In a first aspect, an embodiment of the present application provides a decision-making method, including:

[0007] Get health service events;

[0008] Determining a corresponding health service product based on the health service event;

[0009] Based on the matching rule table and the business scenario information corresponding to the health service event, the service provider corresponding to the health service product is determined, and the matching rule table is used to characterize the corresponding relationship between the health service product and the service provider under different business scenarios.

[0010] In a possible implementation, obtaining a health service event includes:

[0011] Receive events from upstream systems;

[0012] The events received from the upstream system are filtered and converted into health service events based on the filtering results.

[0013] In a possible implementation, the method further includes:

[0014] Define health service items to obtain a service item definition table; define health service products to obtain a health service product definition table; the service item definition table is used to store relevant information of various health service items, and the service product definition table is used to store relevant information of service products;

[0015] The defined service item definition table and the health service product definition table are associated through a relationship table to obtain a product matching table, wherein the product matching table includes health service products.

[0016] In a possible implementation, determining a corresponding health service product based on the health service event includes:

[0017] Based on the health service event, a product matching table is queried to determine a health service product matching the health service event in the health service product definition table, wherein the product matching table is used to characterize the association relationship between service items and products.

[0018] In a possible implementation, the method further includes:

[0019] When the service provider corresponding to the health service product does not exist in the matching rule table, the main supplier in the service item definition table is used as the service provider.

[0020] In a possible implementation, the method further includes:

[0021] storing the health service event, the health service product and the service provider in association with each other in a rights and interests responsibility table;

[0022] In response to a customer exercise instruction, the connection is made through the principal supplier in the equity liability table.

[0023] In a possible implementation, the method determines the service provider corresponding to the health service product based on the matching rule table and the business scenario information corresponding to the health service event, including:

[0024] Based on the matching sequence numbers corresponding to the sequence fields in the matching rule table, the rules with smaller matching sequence numbers are preferentially used to determine the service provider corresponding to the health service product.

[0025] In a possible implementation, the method further includes:

[0026] Health service rights and interests information is generated based on the principal supplier and the rights and interests responsibility table.

[0027] In a second aspect, an embodiment of the present application provides a decision-making system, including:

[0028] An acquisition unit, used for acquiring health service events;

[0029] A first determining unit, configured to determine a corresponding health service product based on the health service event;

[0030] The second determination unit is used to determine the service provider corresponding to the health service product based on the matching rule table and the business scenario information corresponding to the health service event, wherein the matching rule table is used to characterize the corresponding relationship between the health service product and the service provider under different business scenarios.

[0031] In a third aspect, an embodiment of the present application provides a computer-readable storage medium, in which instructions are stored. When the instructions are executed on a terminal device, the terminal device executes the aforementioned decision-making method.

[0032] Compared with the prior art, this application has the following beneficial effects:

[0033] This application obtains health service events, and then quickly identifies and determines the health service products corresponding to the event. Based on the matching rule table and the business scenario information corresponding to the health service event, the service provider corresponding to the health service product is determined. That is, this application uses a matching rule table to establish the corresponding relationship between health service products and service providers. The matching rule table is a flexible and extensible data structure that allows the most suitable service provider to be dynamically selected according to different conditions. In this way, the rule table allows the selection logic of the supplier to be flexibly adjusted according to different business scenarios, and even in the face of complex and changing service scenarios, it can quickly respond to the supplier used for output. In addition, since it is no longer necessary to select service items and service products through code logic judgment, but to implement supplier decisions through a configured rule table, this greatly improves the response speed. When a new business scenario appears, it is only necessary to add the corresponding rules in the rule table without rewriting and deploying the code. As a result, the response speed and flexibility of the system are improved, and the maintenance cost is reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0035] Figure 1 This is a schematic diagram of the correspondence between health service products and health service rights;

[0036] Figure 2 A schematic diagram of a health service product solution provided in an embodiment of the present application;

[0037] Figure 3 A schematic diagram of a unified decision-making process provided for an embodiment of the present application;

[0038] Figure 4 A flowchart of a decision-making method provided in an embodiment of the present application;

[0039] Figure 5 A structural diagram of a decision-making system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0041] To facilitate understanding of the technical solutions provided by the embodiments of the present application, the professional terms involved in the embodiments of the present application will be explained below.

[0042] Health service items: refers to the health service items currently purchased by the insurance company, generally including dental services, green channel services, accompanying services, physical examination services, community accommodation rights, etc.

[0043] Health service responsibility: refers to the insurance company providing the health service items in the health service product to the customer, and the customer has the right to exercise the responsibility of using the health service.

[0044] Health service products: refers to assembling existing purchased service items into service product packages and providing them to customers in the form of products. Generally, there are dental service products, family cards including green channel service items and accompanying service items, physical examination service products, city center community products (only the right to stay in the city center community), etc.

[0045] Health service rights: refers to the fact that when an insurance company provides health service products to customers, the customers have the right to enjoy all the service items in the products.

[0046] Supplier: refers to the supplier who provides health service products / services. Subsequent code A / B Supplier

[0047] Insurance company business channels: In our pension insurance, different sales channels are divided into different business channels, and the subsequent code business is a / b channel.

[0048] To facilitate understanding of the technical solutions provided by the embodiments of the present application, the background technology involved in the embodiments of the present application will be described below.

[0049] The correspondence between health service products and health service rights can be found in Figure 1 , Figure 1 This is a diagram of the correspondence between health service products and health service rights. As shown in the figure, there are many ways for customers to obtain rights. It can be obtained by increasing the value of the insurance policy, participating in activities initiated by the account manager, and so on. From the perspective of the insurance company, the insurance company assembles different service items into different service products for use in different scenarios. Because many suppliers are signed for the same service item and the same product. Therefore, a certain service item will have different supplier requirements in different service products and scenarios. Because there is a need to change suppliers within a time period, in order to solve this supplier restriction and realize the need to change suppliers according to the scenario, this technical solution was generated. In order to quickly respond to business requirements for different suppliers of the same product, there is no need to repeatedly develop health service products, and the requirements can be met by simply using configuration.

[0050] In a possible implementation, the service item Green Channel has been signed with suppliers A, B, and C, the service item Accompanying Service has been signed with suppliers A, B, C, D, and E, and the service product (Green Channel + Accompanying Service) has been signed with supplier F. The insurer wants to package a series of health service products - the Fukang Card series, including the Fukang Card Basic version (only including Green Channel) and the Fukang Card Advanced version (Green Channel and Accompanying Service) for customers. The following scenarios all require the use of the Fukang series card.

[0051] That is, use the basic version of Fukang Card - provided by supplier A in the salesperson's customer acquisition activities. Use the basic version of Fukang Card - provided by supplier B in the customer service festival activities from September 10 to October 31. Sell risk001 insurance in channel a to increase the value of the policy. If the insured is a customer in Jiangsu Province, use the advanced version of Fukang Card - green channel supplier C + accompanying service supplier D. If it is for other customers, use the advanced version of Fukang Card - supplier F.

[0052] For the above example, the prior art completes the demand by creating multiple identical health service products to assist in code logic judgment, see Figure 2 , Figure 2Schematic diagram of the health service product solution provided for the embodiment of the present application. Among them, first, the customer behavior event is received and converted into rights and interests related input. Then determine whether the above conditions for using the Fukang series card are met, that is, determine whether it is a salesperson activity, determine whether it meets condition 1 (such as in the customer service festival activity from September 10 to October 31), and whether it meets condition 2 (such as whether channel a sells risk001 insurance). On the premise of judging that channel a sells risk001 insurance, determine whether condition 3 is met (the insured is a customer in Jiangsu Province). If so, execute Fukang Card Advanced Edition 1 to generate the rights and interests corresponding to the Fukang Card; otherwise, execute Fukang Card Advanced Edition 2 to generate the rights and interests corresponding to the Fukang Card.

[0053] As mentioned above, the existing technology completes the demand by creating multiple identical health service products to assist in code logic judgment. The service items need to be defined multiple times, and the service products also need to be defined multiple times. Even if the customer sees the same health service products, once a new scenario appears, it is necessary to use code to determine which service item or service product to use, which leads to slow response speed and high maintenance costs.

[0054] In order to solve the above problems, the embodiment of the present application defines the required products and the service items included in the product at this stage of defining the service item / service product stage, and establishes a relationship table between the service item and the product. This step provides basic data support for subsequent decision-making. In the stage of obtaining health service products, according to the events of the upstream system, it is converted into the health service events required by the health service system, and the corresponding health service products are obtained. This step ensures the accuracy and pertinence of subsequent decisions. In the supplier decision-making stage, according to the stored health service events, the supplier decision engine is entered. The engine selects suppliers according to multiple dimensions such as insurance code, insurance plan code, sales channel, business channel, and activity events through configured rules. This step is the core of the method and realizes the dynamic management and flexible configuration of suppliers. In the customer rights generation stage, the real supplier service results are stored in the rights and interests responsibility table. When the customer performs the exercise operation, it only needs to connect the service through the main supplier on the rights and interests responsibility. This step ensures the timely realization and effective protection of customer rights.

[0055] By implementing dynamic management of suppliers in a configurable manner, the supplier selection strategy can be quickly adjusted according to different scenarios and needs. This avoids the tediousness and complexity of traditional code logic judgment and improves the efficiency of business processing. With the development of business and the emergence of new needs, new rules and configurations can be easily added to meet the ever-changing market needs. Therefore, by introducing a unified supplier decision engine, the basic version and advanced version of Fukang Card only need to be defined once, and different suppliers and service scenarios can be determined by configuration rather than code logic. This means that all logic and judgment can be completed through the decision engine, greatly reducing duplication of work and maintenance costs.

[0056] like Figure 3 As shown, Figure 3 A schematic diagram of the unified decision-making process provided for an embodiment of the present application, wherein, after the start, it is converted into rights-related input parameters, and the service engine is obtained based on the event, and the execution of the Fukang Card Basic Edition or the Fukang Card Advanced Edition is selected, and then the supplier makes a unified decision to select the corresponding rights and interests of the Fukang Card, such as each Fukang Card Basic Rights and each Fukang Card Advanced Rights and Interests.

[0057] Therefore, for different scenarios and time periods, you only need to configure the corresponding rules in the decision engine to select suppliers without changing the definition of service products, which improves the flexibility and responsiveness of the system. Using this configuration-based approach, you can more flexibly respond to changes in business needs. For example, you can dynamically adjust suppliers according to specific time periods, customer groups, or other conditions, without having to modify the code level every time you make a change.

[0058] It should be noted that the decision-making method, system, device and medium provided in the present application can be applied to the field of computer technology. The above is only an example and does not limit the application field of the decision-making method, system, device and medium provided in the present application. In addition, the embodiments of the present application may not limit the execution subject of the decision. For example, the decision-making method of the embodiment of the present application can be applied to data processing devices such as terminal devices or servers. Among them, the terminal device can be an electronic device such as a computer, a personal digital assistant (PDA). The server can be a stand-alone server, a cloud server or a cluster server composed of multiple servers.

[0059] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0060] The following is an example to illustrate a decision-making method provided by the present application. Figure 4 ,Should Figure 4 A flowchart of a decision-making method provided in an embodiment of the present application, the method comprising:

[0061] S101. Obtain health service events.

[0062] This process occurs when the upstream system is connected to the health service system. When the user's behavior or certain events in the system are triggered, a health service event is generated. Health service events can be actively reported by users (such as appointments for physical examinations, disease consultations, etc.) or automatically detected by the system (such as abnormal physiological indicators monitored by wearable devices). These events need to be captured and converted into a format that the health service system can understand and process.

[0063] Health service events, including but not limited to insurance type codes, insurance plan codes, sales channels, business channels, event events and other information.

[0064] In a possible implementation, the process of obtaining a health service event may include:

[0065] Receive events from upstream systems; filter the events received from upstream systems, and convert them into health service events based on the filtering results.

[0066] Events from the upstream system may include customer behavior, business needs, system triggers, etc. These events are converted into health service events that can be recognized by the health service system. This conversion process may involve operations such as parsing, classification, and mapping of events. The corresponding health service products are obtained. The required fields include insurance type code, insurance plan code, sales channel, business channel, activity event, etc. These fields are used to accurately match and locate specific health service products.

[0067] S102: Determine a corresponding health service product based on the health service event.

[0068] For example, for the Fukang Card series of health service products, the following health service events and matched health service products are output. The health service event is that the customer participated in the customer acquisition activity through the salesperson channel and obtained the Fukang Card Basic Edition. Then, based on the above health service event, the health service product is determined to be the Fukang Card Basic Edition (product_code=P001). In another example, the health service event is that the customer purchased the insurance type risk001 through channel a, and the insured's address is in Jiangsu Province. The health service product is the Fukang Card Advanced Edition (product_code=P002).

[0069] S103: Determine a service provider corresponding to the health service product based on the matching rule table and the business scenario information corresponding to the health service event.

[0070] The matching rule table is used to characterize the correspondence between health service products and service providers in different business scenarios. In addition, the matching rule table includes configuration rules, such as using the basic version of Fukang Card-provided by A supplier in the salesperson's customer acquisition activities. Use the basic version of Fukang Card-provided by B supplier in the customer service festival activities from September 10 to October 31. Sell risk001 insurance in channel a to increase the value of the policy. If the insured is a customer in Jiangsu Province, use the advanced version of Fukang Card-Green Channel C supplier + accompanying service D supplier. If it is other customers, provide the advanced version of Fukang Card-F supplier.

[0071] When a health service event is triggered, according to the relevant information in the event (such as insurance code, sales channel, business channel, etc.), the matching rule table is searched for the qualified rule and the corresponding real service provider is determined. If there are multiple qualified rules in the matching rule table, the best rule is selected to determine the real service provider according to the order of the rules (such as the order_no field) and the priority of the conditional expression (such as the expression field). If there is no qualified rule in the matching rule table, the main supplier in the service item and product relationship table (such as the rel_product_duty table) is taken as the real service provider by default.

[0072] For example, when an upstream system triggers an event (such as a salesperson recommending the Fukang Card Basic Edition to a customer during a customer acquisition activity), the event will be converted into a health service event and matched to the corresponding health service product (Fukang Card Basic Edition, product_code=P001). Subsequently, this product will enter the supplier decision stage and select a suitable supplier (such as supplier A) based on preset rules and conditions. Finally, the selection result will be stored in the equity responsibility table to provide support for subsequent customer service.

[0073] Therefore, through the matching rule table, the corresponding relationship between health service products and service providers can be flexibly configured and adjusted without hard coding in the form of code. In complex business scenarios, through the quick search and condition judgment of the matching rule table, the real service provider can be efficiently determined to meet business requirements. The structure of the matching rule table is clear and easy to understand, which facilitates subsequent maintenance and expansion. At the same time, through the configuration method, the complexity and cost of technical implementation can be reduced.

[0074] The following is an explanation of the establishment process and internal composition of each table in this application. The embodiment of this application is divided into four stages in the actual application process, the first stage is the stage of defining service items / service products, the second stage is the stage of obtaining health service products, the third stage is the stage of supplier decision-making, and the fourth stage is the stage of customer rights generation.

[0075] The first stage is used to define the required products and the services included in the products. Create a service item definition table and a health service product definition table to store the basic information of various health service items and service products, such as service item number, name, type, main supplier, etc. This information can be easily maintained and updated through the background management interface without changing any code.

[0076] In a possible implementation, health service items are defined to obtain a service item definition table; health service products are defined to obtain a service product definition table; the service item definition table is used to store relevant information of various health service items, and the service product definition table is used to store relevant information of service products; the defined service item definition table and the health service product definition table are associated through a relationship table to obtain a product matching table, and the product matching table includes health service products. Then, the product matching table can be queried based on the health service event to determine the health service product in the health service product definition table that matches the health service event, and the product matching table is used to characterize the association relationship between service items and products.

[0077] Among them, the health service item can be expressed as a health service item definition table product_duty. For example, Table 1 is a health service product definition table provided in an embodiment of the present application. The service product definition table can be expressed as a health service product definition table product. For example, Table 2 is a health service product definition table provided in an embodiment of the present application.

[0078] Table 1. Definition of health service items

[0079]

[0080]

[0081] Table 2. Health service product definition table product

[0082] product_code Product Code product_name Product Name nick_name Personalized product name begin_time Product effective date end_time Product expiration date type Product Type status Product status (for sale, on sale, discontinued) ... etc.

[0083] In the embodiment of the present application, two service items are further established, namely the green pass service item (product_duty_code=pd001) and the accompanying medical service item (product_duty_code=pd002). The two products, Fukang Card Basic Edition (product_code=P001) and Fukang Card Advanced Edition (product_code=P002), are defined by combining through the relationship table. The relationship between service items and products is associated using a relationship table. The product matching table can be expressed as a product-service item relationship table rel_product_duty. For example, Table 3 is a product-service item relationship table. The relationship table result is shown in Table 4 below, and Table 4 is a relationship table structure table. In this way, the relationship between service items and products is clarified, and the combination of different service items and service products can be easily managed and adjusted to adapt to various business scenarios.

[0084] Table 3. Product service item relationship table

[0085]

[0086] Table 4. Relationship table structure table

[0087]

[0088] The second stage is to obtain health service products and receive event information from the upstream system. Parse this information and extract necessary fields, such as insurance code, insurance plan code, sales channel, business channel, activity event, etc. Map the extracted information to the standard format used within the health service system. Generate records in the hipe_event_task table and fill in the corresponding fields. According to the information in the converted health service event, such as sales channel, business channel, insurance code, etc., query the health service product definition table product to find matching health service products. In the example, based on information such as sales channels and business activities, the basic version of Fukang Card (product_code=P001) or the advanced version of Fukang Card (product_code=P002) may be matched.

[0089] Table 5. Health service event table (hipe_evet_task table)

[0090]

[0091]

[0092] The third stage is the supplier decision-making stage. Based on the stored health service events, it enters the supplier decision-making engine. The core table of this decision-making engine is the main_supplier_gen_rule table, that is, the health service product - service item supplier rule table, which can also be expressed as the matching rule table. The main fields of this table include: id: rule ID, used to uniquely identify each rule. product_duty_code: health service item code, used to identify specific health service items. product_code: used to identify the health service product containing this service item.

[0093] During the decision-making process, the engine will match the information in the health service event (such as sales channel, business channel, risk code, etc.) with the rules in the main_supplier_gen_rule table. If an event meets the conditional expression in a certain rule (such as ins.address = "Jiangsu"), then the rule is successfully matched.

[0094] In a possible implementation, the rules are matched in the numerical order of the order_no field, and the rules with smaller serial numbers are matched first. If multiple rules meet the conditions, the rule with the smallest order_no will be selected.

[0095] If the stored health service events do not hit any rules, then the system will fallback to the main_supplier field in the relationship table, that is, the main supplier, as the actual service supplier. For example, in the requirement "if it is for other customers, provide the advanced version of Fukang Card - Supplier F", if this rule is not hit in the main_supplier_gen_rule table, then the system will use the main_supplier in the product_duty relationship table as the actual service supplier, that is, automatically select Supplier F as the actual service supplier.

[0096] In a possible implementation, assume there is a health service event as follows:

[0097] product_code: pd002; sale_scene: Channel A; business_dept: A; risk_code: risk001; ins.address: "Jiangsu".

[0098] Since ins.address in the event is "Jiangsu", the rules with IDs 3 and 4 in the main_supplier_gen_rule table will be matched. However, due to the different order_no, the rule with a higher priority will be selected. In this example, the rule with ID 4 has a higher priority, so the actual_supplier finally matched will be Supplier D.

[0099] If ins.address in the same event is not "Jiangsu", then no rule will match successfully. In this case, the main_supplier in the product_duty relationship table, i.e., Supplier F, will be used as the actual service supplier.

[0100] The following is an example table (main_supplier_gen_rule) of the health service product - service item supplier rules provided by the embodiments of the present application.

[0101] Table 6. Health service product - service item supplier rule table (main_supplier_gen_rule)

[0102]

[0103] Based on the above content, the embodiments of the present application need to configure the following data in the actual application scenario:

[0104] Table 7. Data configuration table

[0105]

[0106]

[0107] The fourth stage is the customer rights and interests generation stage. Once the actual supplier is determined, this information needs to be stored in the rights and interests liability table so that customers can smoothly enjoy the corresponding services when they need to exercise their rights.

[0108] Table 8. Rights and interests liability table

[0109] rights_duty_no Equity Responsibility Number rights_no Equity Number product_duty_code Service item number rights_duty_nick_name Personalized name of rights and responsibilities main_supplier Main supplier main_supplier_contract_no Principal Supplier Contract Number scene Equity Responsibility Scenario Value business_dept Performance attribution channel buyer_id Purchaser ID owner_id Owner id bnf_id Beneficiary ID bnf_ids Beneficiary ID(s) bnf_messages Name of beneficiary(s) agent_no Salesman Code branch_code Institution Code show_code Display template encoding remark Remark ext_data_json Extending structures eff_begin_date Effective date of liability eff_end_date Effective expiration date of liability

[0110] Therefore, this application manages real service providers through configuration rules rather than hard coding. This allows business personnel to dynamically adjust supplier decision rules according to different business scenarios by simply modifying the configuration in the rule table. This greatly improves the flexibility of the system and enables the system to respond quickly to changes in business needs. There is no need to create multiple product auxiliary codes or logical judgments for each service scenario. It is only necessary to define product and service items once and implement supplier decisions through configuration rules, which simplifies the development process and system architecture. In addition, the modified rules can take effect immediately without waiting for the application to be redeployed, which speeds up the update of decision logic. The priority and expression of the configuration rules can accurately match complex business scenarios to achieve more efficient supplier decisions. At the same time, the configuration rules are also easy to maintain and update, reducing operating costs.

[0111] The above are some specific implementations of the decision-making method provided in the embodiment of the present application. Based on this, the present application also provides a corresponding decision-making system. The system provided in the embodiment of the present application will be introduced from the perspective of functional modularization. Figure 5 A structural diagram of a decision-making system provided in an embodiment of the present application.

[0112] The system comprises:

[0113] An acquisition unit 110 is used to acquire health service events;

[0114] A first determining unit 111 is used to determine a corresponding health service product based on the health service event;

[0115] The second determination unit 112 is used to determine the service provider corresponding to the health service product based on the matching rule table and the business scenario information corresponding to the health service event. The matching rule table is used to characterize the corresponding relationship between the health service product and the service provider in different business scenarios.

[0116] In a possible implementation manner, the acquiring unit is specifically configured to:

[0117] Receive events from upstream systems; filter the events received from upstream systems, and convert them into health service events based on the filtering results.

[0118] In a possible implementation, the system further includes:

[0119] A definition unit, used to define health service items and obtain a service item definition table; define health service products and obtain a health service product definition table; the service item definition table is used to store relevant information of various health service items, and the service product definition table is used to store relevant information of service products;

[0120] The association unit is used to associate the defined service item definition table and the health service product definition table through a relationship table to obtain a product matching table, wherein the product matching table includes health service products.

[0121] In a possible implementation manner, the first determining unit is specifically configured to:

[0122] Based on the health service event, a product matching table is queried to determine a health service product matching the health service event in the health service product definition table, wherein the product matching table is used to characterize the association relationship between service items and products.

[0123] In a possible implementation, the system further includes:

[0124] The third determining unit is configured to use the subject supplier in the service item definition table as the service supplier when the service supplier corresponding to the health service product does not exist in the matching rule table.

[0125] In a possible implementation, the system further includes:

[0126] storing the health service event, the health service product and the service provider in association with each other in a rights and interests responsibility table;

[0127] In response to a customer exercise instruction, the connection is made through the principal supplier in the equity liability table.

[0128] In a possible implementation manner, the second determining unit is specifically configured to:

[0129] Based on the matching sequence numbers corresponding to the sequence fields in the matching rule table, the rules with smaller matching sequence numbers are preferentially used to determine the service provider corresponding to the health service product.

[0130] In a possible implementation, the system further includes:

[0131] A generating unit is used to generate health service rights and interests information according to the subject supplier and the rights and interests responsibility table.

[0132] The embodiments of the present application also provide corresponding devices and computer storage media for implementing the test method solutions provided in the embodiments of the present application.

[0133] The device includes a memory and a processor, the memory is used to store instructions or codes, and the processor is used to execute the instructions or codes so that the device executes the test method described in any embodiment of the present application.

[0134] The computer storage medium stores codes, and when the codes are executed, a device executing the codes implements the test method described in any embodiment of the present application.

[0135] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other. For the system or device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0136] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0137] It should be understood that the terms "center", "longitudinal", "lateral", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside" and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the referred device or element must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present invention.

[0138] It should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected" and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0139] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0140] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0141] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A decision-making method, characterized in that: include: Get health service events; Determining a corresponding health service product based on the health service event; Based on the matching rule table and the business scenario information corresponding to the health service event, the service provider corresponding to the health service product is determined, and the matching rule table is used to characterize the corresponding relationship between the health service product and the service provider under different business scenarios.

2. The method according to claim 1, characterized in that The health service event acquisition includes: Receive events from upstream systems; The events received from the upstream system are filtered and converted into health service events based on the filtering results.

3. The method according to claim 1, characterized in that The method further comprises: Define health service items to obtain a service item definition table; define health service products to obtain a health service product definition table; the service item definition table is used to store relevant information of various health service items, and the service product definition table is used to store relevant information of service products; The defined service item definition table and the health service product definition table are associated through a relationship table to obtain a product matching table, wherein the product matching table includes health service products.

4. The method according to claim 3, characterized in that The determining a corresponding health service product based on the health service event includes: Based on the health service event, a product matching table is queried to determine a health service product matching the health service event in the health service product definition table, wherein the product matching table is used to characterize the association relationship between service items and products.

5. The method according to claim 1, characterized in that The method further comprises: When the service provider corresponding to the health service product does not exist in the matching rule table, the main supplier in the service item definition table is used as the service provider.

6. The method according to claim 1, characterized in that The method further comprises: storing the health service event, the health service product and the service provider in association with each other in a rights and interests responsibility table; In response to a customer exercise instruction, the connection is made through the principal supplier in the equity liability table.

7. The method according to claim 1, characterized in that The method determines the service provider corresponding to the health service product based on the matching rule table and the business scenario information corresponding to the health service event, including: Based on the matching sequence numbers corresponding to the sequence fields in the matching rule table, the rules with smaller matching sequence numbers are preferentially used to determine the service provider corresponding to the health service product.

8. The method according to claim 1, characterized in that The method further comprises: Health service rights and interests information is generated based on the principal supplier and the rights and interests responsibility table.

9. A decision-making system, characterized in that: include: An acquisition unit, used for acquiring health service events; A first determining unit, configured to determine a corresponding health service product based on the health service event; The second determination unit is used to determine the service provider corresponding to the health service product based on the matching rule table and the business scenario information corresponding to the health service event, wherein the matching rule table is used to characterize the corresponding relationship between the health service product and the service provider under different business scenarios.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on a terminal device, the terminal device executes the decision-making method according to any one of claims 1 to 8.

Images