Page Generation Method, Apparatus, Electronic Device, and Storage Medium

Abstract

An embodiment of the present application provides a page generation method, device, electronic device, and storage medium, which relate to the field of computer technology. The method includes: obtaining an insurance application document; performing semantic analysis on the insurance application document to obtain key fields; performing semantic analysis on the insurance application document to determine a claim settlement scenario; the claim settlement scenario corresponds to one or more claim settlement page modules; determining available claim settlement page modules according to the key fields; selecting a target claim settlement page module that matches the claim settlement scenario from the available claim settlement page modules; generating a claim settlement page according to the target claim settlement page module. The method provided by the embodiment of the present application helps to improve the efficiency of page generation.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of computer technology, and in particular, to a method, apparatus, electronic device, and storage medium for generating a page. Background Art

[0002] According to the current requirements of insurance supervision, insurance products must have the ability to process claims online. That is to say, after purchasing an insurance product, users can process claims online, which requires insurance institutions to provide an online claims page for users to process claims online after an accident.

[0003] Currently, the claims page needs to be manually created by employees of insurance institutions and requires processes such as requirement submission, product evaluation, requirement document production, technical review, development, and testing, resulting in low efficiency. In particular, there are currently thousands of insurance product types. If manual creation of claims pages for a large number of insurance products is required, not only is the efficiency low, but also a large amount of enterprise resources are consumed. Summary of the Invention

[0004] Embodiments of the present application provide a method, apparatus, electronic device, and storage medium for generating a page, which helps to improve the efficiency of page generation.

[0005] In a first aspect, embodiments of the present application provide a method for generating a page, including:

[0006] Obtain an insurance application file;

[0007] Perform semantic analysis on the insurance application file to obtain key fields;

[0008] Perform semantic analysis on the insurance application file to determine a claims scenario; the claims scenario corresponds to one or more claims page modules;

[0009] Determine available claims page modules according to the key fields;

[0010] Select a target claims page module that matches the claims scenario from the available claims page modules;

[0011] Generate a claims page according to the target claims page module.

[0012] In embodiments of the present application, by performing semantic analysis on the insurance application file and automatically creating a claims page in a module matching manner, the traditional manual creation of claims pages can be transformed into automatic creation of claims pages, thereby improving the efficiency of creating claims pages.

[0013] In one possible implementation, before the step of selecting a target claims page module that matches the claims scenario from the available claims page modules, the method further includes:

[0014] Determine the complexity based on the number of the keyword fields and the number of the available claim settlement page modules;

[0015] Send a prompt message based on the complexity, where the prompt message is used to prompt the user to generate the complexity of the current claim settlement page.

[0016] In one possible implementation, the generating the claim settlement page according to the target claim settlement page module includes:

[0017] Fill the target claim settlement page module in the area of a preset layout to generate the claim settlement page.

[0018] In one possible implementation, the relationship and sequence between the areas of the preset layout correspond to the target claim settlement page modules.

[0019] In a second aspect, an embodiment of the present application provides a page generation device, including: one or more functional modules, where the one or more functional modules are used to execute the page generation method as described in the first aspect.

[0020] In a third aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory, where the memory is used to store a computer program; the processor is used to run the computer program to implement the page generation method as described in the first aspect.

[0021] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program runs on a computer, the computer is enabled to implement the page generation method as described in the first aspect. Description of the Drawings

[0022] Figure 1 It is a schematic flowchart of an embodiment of the page generation method provided by the present application;

[0023] Figure 2 It is a schematic diagram of an embodiment of the claim settlement page provided by the present application;

[0024] Figure 3 It is a schematic flowchart of another embodiment of the page generation method provided by the present application;

[0025] Figure 4 It is a schematic diagram of another embodiment of the claim settlement page provided by the present application;

[0026] Figure 5 It is a schematic structural diagram of the page generation device provided by the embodiment of the present application;

[0027] Figure 6 It is a schematic structural diagram of the electronic device provided by the embodiment of the present application. Detailed implementation manners

[0028] In the embodiments of the present application, unless otherwise specified, the character " / " indicates that the related objects before and after are in an "or" relationship. For example, A / B may represent A or B. "And / or" describes the related relationship of the related objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone, these three situations.

[0029] It should be noted that the terms "first", "second", etc. involved in the embodiments of the present application are only used for the purpose of distinguishing descriptions, and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of the indicated technical features, nor can they be understood as indicating or implying an order.

[0030] In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. In addition, "at least one (item)" or its similar expressions refer to any combination of these items, which can include any combination of single item (item) or plural items (items). For example, at least one (item) of A, B, or C may represent: A, B, C, A and B, A and C, B and C, or A, B, and C. Among them, each of A, B, and C itself can be an element or a set containing one or more elements.

[0031] In the embodiments of the present application, "exemplary", "in some embodiments", "in another embodiment", etc. are used to give examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly speaking, the use of the word "exemplary" is intended to present concepts in a specific manner.

[0032] In the embodiments of the present application, "(of)", "corresponding", and "corresponding" can sometimes be used interchangeably. It should be noted that when not emphasizing their differences, the meanings to be expressed are the same. In the embodiments of the present application, communication and transmission can sometimes be used interchangeably. It should be noted that when not emphasizing their differences, the meanings they express are the same. For example, transmission can include sending and / or receiving, and can be a noun or a verb.

[0033] In the embodiments of the present application, the equality involved can be used in combination with greater than, applicable to the technical solutions adopted when greater than, or can also be used in combination with less than, applicable to the technical solutions adopted when less than. It should be noted that when equality is used in combination with greater than, it cannot be used in combination with less than; when equality is used in combination with less than, it is not used in combination with greater than.

[0034] The current claims page needs to be manually created by the employees of insurance companies, and it requires processes such as requirement submission, product evaluation, requirement document production, technical review, development, and testing, resulting in low efficiency. In particular, there are currently a large number of insurance products, numbering in the thousands. Manually creating claims pages for a large number of insurance products not only has low efficiency but also consumes a large amount of enterprise resources. Among them, the claims page refers to the page where the insured needs to understand necessary information, submit necessary materials and information, and perform operations when applying for online claims. The claims page generally includes a claims description page, a claims information page, a material upload page, etc.

[0035] Based on the above problems, the embodiment of the present application proposes a page generation method, which automatically creates a claims page by semantic analysis of the insurance application file and in a module-matching manner. Thus, the traditional manual creation of the claims page can be transformed into an automatic creation, thereby improving the efficiency of creating the claims page.

[0036] Now in combination with Figures 1-4 the page generation method provided by the embodiment of the present application will be described.

[0037] As Figure 1 shown in the flowchart of an embodiment of the page generation method provided by the present application, it specifically includes the following steps:

[0038] Step 101, obtain the insurance application file.

[0039] Specifically, the insurance application file can be an insurance product developed by an insurance institution or can also be considered as an insurance product purchased by a user. The insurance application file contains content such as insurance liability and claims rules. Among them, the insurance liability can refer to the protection content in commercial insurance, generally including: medical expense expenditure, diagnosis of major diseases, loss of living ability, property and economic loss, etc. The claims rules can refer to the situation where the insured claims compensation from the insurer after suffering health or property losses, and the insurance institution reviews the compensation result and the specific amount according to the specified claims rules.

[0040] Step 102, perform semantic analysis on the insurance application file to obtain key fields.

[0041] Specifically, the specific way to perform semantic analysis on the insurance application document can be as follows: perform semantic analysis on the insurance application document through natural language processing (NLP) means. Among them, semantic analysis can be carried out based on keywords, and corresponding keyword fields can be obtained according to the keywords. Among them, the keywords can include scope of coverage, adjustment rules, exemption scenarios, material requirements, claim types, etc. It can be understood that the above are only examples and do not constitute a limitation on the embodiments of the present application. In some embodiments, there may be more or fewer keywords. Taking the keyword of material requirements as an example, after performing semantic analysis on the text in the insurance application document, the corresponding keyword fields that can be obtained can be admission records, first page of medical records, discharge records, expense lists, etc. It can be understood that the above are only examples and do not constitute a limitation on the embodiments of the present application. In some embodiments, there may be more or fewer keyword fields.

[0042] In specific implementation, a keyword field library can be set up in advance, and the keyword field library can include multiple keyword fields. When performing semantic analysis, the semantic analysis result can be matched with the keyword fields in the keyword field library to obtain the corresponding keyword fields. Taking a sentence in the insurance application document as an example, after performing semantic analysis on this sentence, this sentence can be segmented into several fragments. Among them, each fragment can be composed of word segmentation. Then, each fragment can be matched with the keyword fields in the keyword field library to obtain the corresponding keyword fields. Since the insurance application document is composed of paragraphs, and each paragraph is composed of one or more sentences, therefore, through semantic analysis sentence by sentence, the entire insurance application document can be semantically recognized, and thus the keyword fields corresponding to the insurance application document can be obtained.

[0043] It can be understood that the insurance application document in the present application refers to an electronic document. If a paper insurance application document is obtained, then the text of the paper insurance application document can be recognized through optical character recognition (OCR) means, and thus an electronic document can be obtained, and the recognized text is included in this electronic document.

[0044] Step 103, determine the target claim page module according to the keyword fields.

[0045] Specifically, after obtaining the keyword fields, the target claim page module can be determined according to the keyword fields.

[0046] In specific implementation, the mapping relationship between the claim settlement page module and the key fields can be preset. For example, one claim settlement page module can correspond to one or more key fields. Taking the key fields such as the admission record, the first page of the medical record, the discharge record, and the expense list identified as an example, if the material name module corresponds to the key fields such as the admission record, the first page of the medical record, the discharge record, and the expense list, then the key fields such as the admission record, the first page of the medical record, the discharge record, and the expense list can be corresponded to the material name module, and thus the material name module can be determined as the target claim settlement page module.

[0047] Step 104, generate a claim settlement page according to the target claim settlement page module.

[0048] Specifically, after the target claim settlement page module is determined, the determined target claim settlement page module can be built on a page, thereby generating a claim settlement page. Figure 2 It is a schematic diagram of an embodiment of the claim settlement page, as Figure 2 shown. The claim settlement page can include multiple claim settlement page modules. For example, module A, module B, and module C, etc. Each claim settlement page module can include one or more key fields. For example, key field A1, key field A2, key field B1, key field B2, key field B3, key field C1, etc.

[0049] In the embodiment of the present application, by semantic analysis of the insurance application document and automatically creating a claim settlement page in the way of module matching, the traditional manual creation of the claim settlement page can be transformed into automatic creation of the claim settlement page, thereby improving the efficiency of creating the claim settlement page.

[0050] Next, in combination with Figure 3 the page generation method provided by the embodiment of the present application will be further described.

[0051] Figure 3 It is a schematic flowchart of another embodiment of the page generation method provided by the present application, which specifically includes the following steps:

[0052] Step 301, obtain the insurance application document.

[0053] Specifically, the specific implementation manner of this step 301 can refer to the relevant description of step 101, which will not be elaborated here.

[0054] Step 302, perform semantic analysis on the insurance application document to determine the key fields and the claim settlement scenarios; the claim settlement scenarios correspond to one or more claim settlement page modules.

[0055] Specifically, the specific implementation manner of performing semantic analysis on the insurance application document to determine the key fields can refer to the relevant description of step 102, which will not be elaborated here.

[0056] In addition, semantic analysis can be performed on the insurance application documents to determine the claim scenarios. It can be understood that the claim scenarios can be regarded as the types of insurance, such as medical insurance, critical illness insurance, accident insurance, etc.

[0057] Step 303: Determine the available claim page modules based on the key fields.

[0058] Specifically, after determining the key fields, the available claim page modules corresponding to the key fields can be determined according to the determined key fields. Among them, the available claim page modules can be obtained by matching in a pre-set key field library.

[0059] Furthermore, after determining the available claim page modules, the complexity can also be determined based on the number of key fields and the number of available claim page modules. Here, the complexity refers to the complexity of creating the claim page. It can be understood that if there are too many key fields, the complexity of generating the claim page modules will increase; if there are too many claim page modules, the complexity of creating the claim page will increase. Therefore, when considering the complexity, it can be based on the number of key fields and the number of claim page modules. Exemplarily, if the total number of key fields and the total number of claim page modules exceed a preset threshold, a prompt message can be sent to prompt the user that the complexity of generating the current claim page is too high. At this time, the user can create it manually, thereby avoiding the waste of time and resources caused by the generated claim not meeting the requirements; if the total number of key fields and the total number of claim page modules do not exceed the preset threshold, the creation of the claim page can be further carried out, for example, execute Step 304.

[0060] Step 304: Select the target claim page module that matches the claim scenario from the available claim page modules.

[0061] Specifically, after obtaining the available claim page modules, the target claim page module that matches the claim scenario can be determined according to the claim scenario.

[0062] In the specific implementation, since there may be many available claim page modules determined according to the key fields, it is necessary to find the claim page modules related to the current claim scenario, and the irrelevant claim page modules can be ignored. Taking the claim scenario of medical insurance as an example, assume that the available claim page modules include Module A, Module B, Module C, Module D, etc. If Module A and Module B match the medical insurance, then Module A and Module B can be used as the target claim page modules, and Module C, Module D, etc. that do not match the medical insurance can be ignored.

[0063] Step 305: Generate a claim page according to the target claim page module.

[0064] Specifically, the target claim settlement page module can be filled in the area of a preset layout to generate a claim settlement page. The preset layout can be the layout corresponding to the claim settlement scenario.

[0065] In specific implementation, the mapping relationship between the claim settlement scenario and the preset layout can be set in advance. Exemplarily, claim settlement scenario 1 corresponds to preset layout 1, claim settlement scenario 2 corresponds to preset layout 2, claim settlement scenario 3 corresponds to preset layout 3, etc. Each preset layout has its own layout. Exemplarily, each layout can include multiple areas, each area corresponds to a determined claim settlement page module, and there are constraints on the relationship and order among the claim settlement page modules corresponding to each area. It can be understood that the claim settlement page is a page for filling in information. Therefore, for each claim settlement page module, there is a sequence and a subordinate relationship. Therefore, in the layout of the claim settlement page, the claim settlement page modules with a sequence can be placed in a front-back and up-down order, and the claim settlement page modules with a subordinate relationship can be placed in a containing relationship.

[0066] Figure 4 For a schematic diagram of another embodiment of the claim settlement page, as Figure 4 shown, assuming that the user should fill in module B before module A, then in the claim settlement page, module B can be placed above module A. In addition, assuming that module C contains module D, it can also be considered that module D is a sub-module of module C, then module C can be placed in a way that contains module D.

[0067] Figure 5 For a schematic structural diagram of an embodiment of the page generation device of the present application, as Figure 5 shown, the above page generation device 50 may include:; where

[0068] An obtaining module 51, configured to obtain an insurance application document;

[0069] An analysis module 52, configured to perform semantic analysis on the insurance application document to obtain key fields; perform semantic analysis on the insurance application document to determine a claim settlement scenario; the claim settlement scenario corresponds to one or more claim settlement page modules;

[0070] A determination module 53, configured to determine available claim settlement page modules according to the key fields; select target claim settlement page modules that match the claim settlement scenario from the available claim settlement page modules

[0071] A generation module 54, configured to generate a claim settlement page according to the target claim settlement page modules.

[0072] In one possible implementation manner, the above page generation device 50 further includes:

[0073] A hint module 55 for determining complexity based on the number of the keyword fields and the number of the available claim pages modules;

[0074] Sending a hint message based on the complexity, where the hint message is used to prompt a user to generate the complexity of a current claim page.

[0075] In one possible implementation, the above-mentioned generation module 54 is specifically configured to fill the target claim page module in an area of a preset layout to generate a claim page.

[0076] In one possible implementation, the area of the preset layout corresponds to the relationship and sequence among the target claim page modules.

[0077] Figure 6 The following is a schematic structural diagram of an electronic device 600 provided by an embodiment of the present application. The above-mentioned electronic device 600 may include: at least one processor; and at least one memory communicatively connected to the above-mentioned processor. The above-mentioned memory stores program instructions executable by the above-mentioned processor, and the processor can call the above-mentioned program instructions to execute the actions performed by the electronic device provided by the embodiment of the present application.

[0078] As Figure 6 shown, the electronic device 600 may be presented in the form of a general-purpose computing device. The components of the electronic device 600 may include, but are not limited to: one or more processors 610, a memory 620, a communication bus 640 connecting different system components (including the memory 620 and the processor 610), and a communication interface 630.

[0079] The communication bus 640 represents one or more of several types of bus structures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the multiple bus structures. For example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnection (PCI) bus.

[0080] The electronic device 600 typically includes a variety of computer system-readable media. These media can be any available media accessible by the electronic device 600, including volatile and non-volatile media, removable and non-removable media.

[0081] The memory 620 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) and / or cache memory. The electronic device 600 may further include other removable / non-removable, volatile / non-volatile computer system storage media. Although Figure 6 not shown in the figure, a disk drive for reading from and writing to a removable non-volatile magnetic disk (such as a "floppy disk"), and an optical disk drive for reading from and writing to a removable non-volatile optical disk (such as a compact disc read only memory (CD-ROM), a digital versatile disc read only memory (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to the communication bus 640 through one or more data media interfaces. The memory 620 may include at least one program product having a set (such as at least one) of program modules configured to perform the functions of the embodiments of the present application.

[0082] A program / utility having a set (at least one) of program modules may be stored in the memory 620. Such program modules include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Implementations of a network environment may be included in each or some combination of these examples. The program modules generally perform the functions and / or methods in the embodiments described in the present application.

[0083] The electronic device 600 may also communicate with one or more external devices (such as a keyboard, a pointing device, a display, etc.), and may also communicate with one or more devices that enable a user to interact with the electronic device 600, and / or communicate with any device that enables the electronic device 600 to communicate with one or more other computing devices (such as a network card, a modem, etc.). Such communication may be carried out through the communication interface 630. Moreover, the electronic device 600 may also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter ( Figure 6 not shown in the figure), and the above network adapter may communicate with other modules of the electronic device through the communication bus 640. It should be understood that although Figure 6Not shown in the figure, other hardware and / or software modules can be used in combination with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, redundant arrays of independent drives (RAID) systems, magnetic tape drives, and data backup storage systems, etc.

[0084] Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and conciseness of description, only the above division of each functional module is used as an example. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0085] In each embodiment of the embodiments of the present application, each functional unit can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0086] If the above integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk, or optical disk, etc., which can store program codes.

[0087] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A page generation method, characterized in that, The method includes: Obtaining an insurance application document; Performing semantic analysis on the insurance application document to obtain key fields; Performing semantic analysis on the insurance application document to determine a claim settlement scenario; the claim settlement scenario corresponds to one or more claim settlement page modules; Determining available claim settlement page modules according to the key fields; Selecting a target claim settlement page module that matches the claim settlement scenario from the available claim settlement page modules; Generating a claim settlement page according to the target claim settlement page module; The performing semantic analysis on the insurance application document to obtain key fields includes: Performing semantic analysis on the insurance application document based on one or more preset keywords to obtain key fields corresponding to the one or more preset keywords.

2. The method according to claim 1, characterized in that, Before the selecting a target claim settlement page module that corresponds to the claim settlement scenario from the available claim settlement page modules, the method further includes: Determining the complexity according to the number of the key fields and the number of the available claim settlement page modules; Sending a prompt message based on the complexity, where the prompt message is used to prompt the user about the complexity of generating the current claim settlement page.

3. The method according to claim 1 or 2, characterized in that, The generating a claim settlement page according to the target claim settlement page module includes: Filling the target claim settlement page module in an area of a preset layout to generate a claim settlement page.

4. The method according to claim 3, wherein The area of the preset layout corresponds to the relationship and sequence among the target claim settlement page modules.

5. A page generation device, characterized in that, Including: One or more functional modules, where the one or more functional modules are used to execute the page generation method according to any one of claims 1-4.

6. An electronic device, characterized in that, Including: A processor and a memory, where the memory is used to store a computer program; the processor is used to run the computer program to implement the page generation method according to any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, and when the computer program runs on a computer, it implements the page generation method according to any one of claims 1-4.

Images