Method for simplifying insurance case signing agreement process

Abstract

The invention provides a method for simplifying an insurance case signing agreement process. The method comprises the following steps: calling a case management micro-service to create a new case and store basic information according to claim submitted by a client; the information extraction micro-service uses a pre-trained NLP model to extract key information from the basic information; the template matching and filling micro-service automatically fills the extracted key information into a corresponding variable position in a template to generate a preliminary protocol document; the format verification micro-service processes the generated preliminary protocol document into a protocol document and verifies the format and content of the document; the online examination and approval and signing micro-service reminds the examination and approval personnel to examine the agreement, after the examination and approval personnel examine and confirm that the agreement document is correct, a signing link is established for the client, and the client signs the agreement; the protocol circulation and automatic seal using micro-service converts the signed protocol into an electronic signature version protocol and asynchronously circulates the electronic signature version protocol to the claim checking system, and the claim checking system signs according to the signed protocol content and then uploads the signed protocol content to the cloud storage system; and the micro-services are matched through event driving.

Description

Technical Field

[0001] The present invention relates to the technical field of insurance agreement processing, and in particular to a method for simplifying the process of signing an insurance case agreement. Background Art

[0002] Given that the volume of claims settlement cases has continued to grow in recent years, customers and investigators have to frequently travel back and forth between the counter and the customer's place of residence, resulting in a dramatic increase in workload and a long time span, which makes it easy for customers to go back on their word and complain. At the same time, the process for applying for seals for the agreement is complicated, which can effectively improve efficiency, reduce costs and increase customer satisfaction.

[0003] With the rapid development of the insurance industry, insurance companies are facing more and more challenges, especially when dealing with difficult cases. Given the continuous growth in the number of claims settlement cases in recent years, customers and investigators have to frequently travel back and forth between the counter and the customer's place of residence, resulting in a sharp increase in workload and a long time span. It involves complex legal provisions, diverse customer needs, and multi-party negotiation processes, which are prone to customer regrets and complaints. At the same time, the process of applying for seals for agreements is complicated. The traditional case signing agreement process relies on manual review and negotiation, which is not only time-consuming and labor-intensive, but may also lead to legal and compliance risks due to human errors. In order to improve the efficiency of insurance claims processing, reduce the error rate, and ensure the accuracy and consistency of agreement signing, simplifying the process of signing agreements for difficult cases based on artificial intelligence has become an important research direction. Summary of the invention

[0004] In order to solve the above technical problem or at least partially solve the above technical problem, the present invention provides a method for simplifying the process of signing an insurance case agreement.

[0005] In a first aspect, the present invention provides a method for simplifying the process of signing an insurance case agreement, comprising:

[0006] The customer submits claim documents through the APP. The APP backend calls the case management microservice to create a new case and store basic information, including claim serial number, type, status, policy, and claim case description.

[0007] After a case is created, the information extraction microservice obtains the basic information of the newly created case and uses the pre-trained NLP model to extract key information from the insurance policy or claim case description;

[0008] After extracting the key information, the template matching and filling microservice obtains the key information, automatically fills the extracted key information into the corresponding variable position in the template, and generates a preliminary agreement document;

[0009] After the preliminary agreement document is generated, the format verification microservice processes the generated preliminary agreement document into a Word or PDF format agreement document and verifies the format and content of the document to ensure that the document complies with legal requirements;

[0010] After the agreement is generated, the online approval and signing microservice sends a real-time notification to the approver to remind him / her to review the agreement. After the approver reviews and confirms that the agreement document is correct, he / she will create a signing link for the customer, and the customer will sign the agreement.

[0011] After the customer signs the agreement, the agreement circulation and automatic seal microservice converts the signed agreement into an electronically signed agreement and asynchronously transfers it to the claims system. The claims system stamps the signed agreement according to its content and uploads it to the cloud storage system.

[0012] The microservices cooperate with each other through event-driven.

[0013] Furthermore, Spring Boot is used to build a case management microservice to implement case creation and management functions; the basic information of the case is stored in a MySQL or PostgreSQL database, and the integrity and consistency of the data are ensured; a unified interface is provided through Spring Cloud Gateway or Kong API gateway to facilitate other microservices to obtain basic case information from the case management microservice.

[0014] Furthermore, the information extraction microservice is implemented based on the NLP model, and uses a pre-trained NLP model to extract key information from the insurance policy or claim case description. The extracted key information includes: applicant name, insured person information, policy number, and claim amount; the information extraction microservice provides an API interface through Flask or FastAPI for other microservices to call key information.

[0015] Furthermore, the template matching and filling microservice stores and manages the protocol template library through the template engine, and dynamically fillable variables are embedded in the template to ensure a unified format; based on the key information extracted by the information extraction microservice, the extracted key information is automatically filled into the corresponding variable positions in the template to generate a preliminary protocol document; the template matching and filling microservice provides an API interface through Spring Boot, which facilitates other microservices to obtain and generate preliminary protocol documents from the template matching and filling microservice.

[0016] Furthermore, the format verification microservice uses Apache POI or iText to process the generated preliminary agreement document into an agreement document in Word or PDF format; verifies the format and content of the document through JSON Schema or XML Schema to ensure that the document complies with legal requirements; encapsulates the document generation and verification logic as a Java service, and integrates it with the front-end and case management microservices through an API interface.

[0017] Furthermore, the online approval and signing microservice sends real-time notifications to the approvers through WebSocket or SSE technology, reminding them to review the agreement; the approvers log in to the online platform, view the generated agreement document, review it and confirm that it is correct;

[0018] After the reviewer has reviewed and confirmed that the agreement document is correct, a signing link will be created for the customer, who will sign the agreement in the following ways: SMS signing link: The system calls the SMS service API and uses a third-party SMS service provider to send an SMS link with verification code verification, identity recognition and signature functions to the customer;

[0019] APP signing link: The signing link is provided through the APP. The customer completes identity verification and online signing, and uploads necessary image materials.

[0020] Furthermore, the agreement circulation and automatic seal microservice generates an electronic signature version of the signed agreement based on the PDF generation library and electronic signature technology;

[0021] The agreement circulation and automatic seal microservice sends the generated electronic signature version of the agreement to the claims system through the message queue and microservice architecture to achieve asynchronous circulation;

[0022] In the claims settlement system, a corresponding electronic seal is generated according to the content of the signed agreement, and the seal is embedded in the electronic signature version of the agreement to ensure the legal validity of the agreement;

[0023] The generated electronically signed agreement is stored in a secure cloud storage system, and the storage and retrieval of the agreement is managed through a microservice architecture to ensure data accessibility and security.

[0024] Furthermore, the event-driven cooperation between the microservices includes: the case management microservice generates a "case creation" event; the information extraction microservice subscribes to the "case creation" event, and when the "case creation" event is received, the information extraction microservice extracts the key information of the case, and after completing the extraction of the key information, a "case information extraction" event is generated; the template matching and filling microservice subscribes to the "case information extraction" event, and when the "case information extraction" event is received, the template matching and filling microservice uses the key information to generate a preliminary agreement document, and after completing the generation of the preliminary agreement document, a "generate preliminary agreement" event is generated; the format verification microservice subscribes to the "generate preliminary agreement" event, and when the "generate preliminary agreement" event is received, the format verification microservice processes the preliminary agreement document to obtain the agreement document, and after completing the generation of the agreement document, a "generate agreement" event is generated; the online approval and signing process microservice subscribes to the "generate agreement" event, and when the "generate agreement" event is received, it controls the approval and signing of the agreement, and after signing the agreement, a "agreement signing" event is generated. The Agreement Circulation and Automatic Seal Microservice subscribes to the "Agreement Signing Completed" event; The Agreement Circulation and Automatic Seal Microservice subscribes to the "Agreement Signing Completed" event. When receiving the "Agreement Signing Completed" event, the Agreement Circulation and Automatic Seal Microservice processes the signed agreement into an electronically signed agreement and asynchronously transfers it to the claims settlement system. The claims settlement system signs and seals the signed agreement according to the content of the signed agreement. After the agreement is signed, an "Agreement Signing Completed" event is generated; After the PDF Generation and Storage Microservice receives the "Agreement Signing Completed" event, the PDF Generation and Storage Microservice processes the generated electronically signed agreement into PDF format and stores it in a secure cloud storage system, and then generates an "Agreement Completed" event; After receiving the "Agreement Signing Completed" event, the Case Management Microservice changes the status of the managed case according to the signing status; After receiving the "Agreement Signing Completed" event, the Case Management Microservice updates the status of the managed case according to the signing status; After receiving the "Agreement Completed" event, the Case Management Microservice updates the status of the managed case according to the agreement completion status.

[0025] In a second aspect, the present invention provides a device for simplifying the process of signing an agreement for an insurance case, comprising: at least one processing unit, the processing unit and a storage unit being interconnected via a bus unit, the storage unit storing a computer program, and when the computer program is executed by the processing unit, the method for simplifying the process of signing an agreement for an insurance case is implemented.

[0026] In a third aspect, the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method for simplifying the insurance case agreement signing process is implemented.

[0027] The above technical solution provided by the embodiment of the present invention has the following advantages compared with the prior art:

[0028] Through intelligent agreement generation and automatic filling of information, the writing process of claim agreements is greatly simplified, and the efficiency of claims personnel is improved. Through the automatic filling and format unification of the microservice NLP model, the accuracy of the agreement content is ensured, reducing the possibility of human error. Supporting multiple signing methods meets the needs of different customers and improves customer experience. By automatically generating electronic agreements and automatically using seals, the agreement signing process is automated, reducing the time and cost of manual operations. Through electronic signatures, identity recognition and multi-factor authentication technology, the security and legality of the signing process are ensured. Through the combination of event-driven architecture and microservice architecture, the scalability and high availability of the system are ensured, and large-scale concurrent operations are supported. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0030] In order to more clearly illustrate the embodiments of the present invention 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, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0031] Figure 1 A flowchart of a method for simplifying the insurance case agreement signing process provided by an embodiment of the present invention;

[0032] Figure 2 An architectural diagram of a simplified insurance case agreement signing process provided by an embodiment of the present invention;

[0033] Figure 3 A flowchart of the online approval and signing microservice implementation provided by an embodiment of the present invention;

[0034] Figure 4 A flowchart of the protocol transfer and automatic seal usage microservice implementation provided by an embodiment of the present invention;

[0035] Figure 5 A schematic diagram of a device for simplifying the insurance case agreement signing process provided by an embodiment of the present invention. DETAILED DESCRIPTION

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

[0037] It should be noted that, in this article, the terms "include", "comprises" or any other variations 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, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0038] Example 1

[0039] The technology of the present invention realizes a method for simplifying the process of signing an agreement for an insurance case. In order to realize the method for simplifying the process of signing an agreement for an insurance case, the present invention adopts a development mode of a microservice architecture combined with an event-driven architecture, and the development mode can meet the high scalability, elasticity, flexibility and decoupling requirements of the system. Each microservice can act as an event producer and publish events to the event bus when an important business event occurs. The event bus acts as a central, highly scalable message queue or message agent, responsible for the distribution and delivery of events. Other microservices can act as event consumers, subscribe to events of interest, and execute corresponding business logic according to the content of the event. An event represents a fact that has occurred and does not contain any destination-related information. The message can convey the event content and transmit the event data from the source to the specified destination. The event source generates a message encapsulating the event data. When the message carrying the event data arrives at the destination, the microservice or behavior function subscribed to the event will be triggered. The message queue is asynchronous, allowing the receiver to retrieve the message after a period of time after the message is sent, and the sender and receiver of the message do not need to interact with the message queue at the same time. The event producer sends a message, and the event consumer asynchronously obtains the time through the message queue and executes the corresponding logic, reducing the service response time and improving the user experience. Message queues reduce the coupling between services. Different services communicate through message queues. When a business needs to be implemented by multiple services together, or a message needs to be processed by multiple services, as long as the message producer sends a message and the consumer service consumes the message in the message queue, the business needs can be met and the coupling between services can be reduced. If there is a gap in processing capabilities between services, the message queue will be saved until it is capable of processing, and then distributed and processed. If the system request traffic increases suddenly, the message queue will cache the request and process it after a period of time, which improves the stability of the system and user experience.

[0040] See also Figure 1 and Figure 2 As shown, the present invention includes the following microservices and execution steps:

[0041] Case management microservice: Customers submit claims through the APP and submit claims documents. The APP backend calls the case management microservice through the API to create a new case and store the basic information of the new case, including the claim serial number, type, status, policy, and claim case description. When each new claim case is generated, the case management microservice generates a "case creation" event as an event producer. In the specific implementation process, Spring Boot is used to build the case management microservice to realize the case creation and management functions. The basic information of the case is stored in the MySQL or PostgreSQL database to ensure the integrity and consistency of the data. Through the Spring Cloud Gateway or Kong API gateway, a unified interface is provided to facilitate other microservices to obtain the basic information of the case from the case management microservice. As an event consumer, the case management microservice subscribes to the "agreement signing completed" event. After receiving the "agreement signing completed" event, the status of the managed case is changed according to the signing status. As an event consumer, the case management microservice subscribes to the "agreement signature" event. After receiving the "agreement signature" event, the status of the managed case is updated according to the signature status. The case management microservice subscribes to the "agreement completion" event as an event consumer. After receiving the "agreement completion" event, it updates the status of the managed case according to the agreement completion status.

[0042] Information extraction microservice: The information extraction microservice is implemented based on the NLP model. It uses a pre-trained NLP model to extract key information from the insurance policy or claim case description. The extracted key information includes: applicant name, insured information, policy number, and claim amount. During the specific implementation process, the information extraction microservice provides an API interface through Flask or FastAPI for other microservices to call key information. The NLP models described in the example are such as the BERT model and the GPT model. As an event consumer, the information extraction microservice subscribes to the "case creation" event. Once the "case creation" event is received, the information extraction microservice obtains the basic information of the newly created case and uses the pre-trained NLP model to extract key information from the insurance policy or claim case description. As an event producer, the information extraction microservice generates a "case information extraction" event after completing the extraction of key information.

[0043] Template matching and filling microservice: The agreement template library is stored and managed through the template engine. Exemplary template engines include Freemarker, Thymeleaf or Handlebars. Dynamically fillable variables are embedded in the template to ensure uniform format. According to the key information extracted by the information extraction microservice, the extracted key information is automatically filled into the corresponding variable position in the template to generate a preliminary agreement document. The template matching and filling microservice provides an API interface through Spring Boot to facilitate other microservices to obtain and generate preliminary agreement documents from the template matching and filling microservice. As an event consumer, the template matching and filling microservice subscribes to the "case information extraction" event. Once the "case information extraction" event is received, the template matching and filling microservice obtains the key information and automatically fills the extracted key information into the corresponding variable position in the template to generate a preliminary agreement document; as an event producer, the template matching and filling microservice generates a "generate preliminary agreement" event after completing the generation of the preliminary agreement document.

[0044] Format Verification Microservice: As an event consumer, the format verification microservice subscribes to the "Generate Preliminary Agreement" event. When receiving the "Generate Preliminary Agreement" event, the format verification microservice uses Apache POI or iText to process the generated preliminary agreement document into an agreement document in Word or PDF format. Verify the format and content of the document through JSON Schema or XML Schema to ensure that the document meets legal requirements. Encapsulate the document generation and verification logic as a Java service and integrate it with the front-end and case management microservices through the API interface. As an event producer, the format verification microservice generates the "Generate Agreement" event.

[0045] like Figure 3 As shown in the figure, the online approval and signing process microservice: As an event consumer, the online approval and signing process microservice subscribes to the "Generate Agreement" event. When receiving the "Generate Agreement" event, the online approval and signing microservice sends a real-time notification to the approver through WebSocket or SSE technology to remind him to review the agreement. The approver logs in to the online platform, views the generated agreement document, reviews it and confirms that it is correct. After the approver reviews and confirms that the agreement document is correct, he will establish a signing link for the customer, and the customer signs the agreement. The methods include: SMS signing link: The system calls the SMS service API and uses a third-party SMS service provider (such as Twilio, Nexmo) to send an SMS link with verification code verification, identity recognition and signature functions to the customer. APP signing link: The signing link is provided through the APP, and the customer completes identity authentication and online signing, and uploads the necessary image materials.

[0046] As an event producer, the online approval and signing process microservice generates an "agreement signing completed" event after the customer signs the agreement.

[0047] Agreement Flow and Automatic Seal Microservice: As an event consumer, the Agreement Flow and Automatic Seal Microservice subscribes to the "Agreement Signing Completed" event. Figure 4 As shown in the figure, when the "Agreement Signing Completed" event is received, the Agreement Flow and Automatic Seal Microservice will generate an electronically signed version of the agreement based on the PDF generation library, such as iText, PDFBox, and electronic signature technology, such as DocuSign, Adobe Sign. The Agreement Flow and Automatic Seal Microservice will send the generated electronically signed version of the agreement to the claims system through a message queue, such as Kafka, RabbitMQ, etc., and the microservice architecture to achieve asynchronous flow. In the claims system, the corresponding electronic seal is generated according to the content of the signed agreement, and the seal is embedded in the electronically signed version of the agreement to ensure the legal validity of the agreement. As an event producer, the Agreement Flow and Automatic Seal Microservice generates an "Agreement Signature" event after the agreement is signed.

[0048] The PDF Generation and Storage microservice subscribes to the "Agreement Signature" event as an event consumer. After receiving the "Agreement Signature" event, the PDF Generation and Storage microservice processes the generated electronic signature version of the agreement into PDF format and stores it in a secure cloud storage system. It also manages the storage and retrieval of the agreement through the microservice architecture to ensure data accessibility and security. The PDF Generation and Storage microservice, as an event producer, generates an "Agreement Completion" event.

[0049] The present invention adopts Python and Java as the main development languages, and the front end mainly adopts JavaScript and the front-end framework Vue.js to build the user interface to realize the visualization functions of case management and signing process. The front end uses Vue.js to build the claim case management interface, including the creation, viewing and updating functions of claim cases. The back end uses Spring Boot to build the case management microservice to realize case data storage and status management. At the same time, MySQL or PostgreSQL is used as a database to store basic case information and provide it to other microservices for calling through the API gateway. The information extraction microservice uses the NLP model to extract key information from the insurance policy and case description, and uses Flask or FastAPI to build the API interface of the information extraction microservice. The information extraction microservice returns the key information to the template matching and filling microservice in the form of structured data. The template matching and filling microservice uses a template engine to store and manage the agreement template library. According to the extracted key information, the agreement template is filled to generate a preliminary agreement document. The format verification microservice verifies the document format of the generated agreement document using JSON Schema or XML Schema to ensure that the document meets legal requirements. The generated agreement is passed to the online approval and signing microservice to initiate the approval and signing process. The online approval and signing microservice uses DocuSign or Adobe Sign to initiate the approval process and uses WebSocket or SSE to send the approval information to the claims personnel in real time. It uses Twilio SMS service to send the signing link or sends the signing link to the customer through the APP. The signing status is passed to the case management service to update the case status. The signing result is passed to the agreement circulation and automatic seal microservice. The agreement circulation and automatic seal microservice generates an electronically signed version of the agreement based on the PDF generation library and electronic signature technology. The agreement circulation and automatic seal microservice sends the generated electronically signed version of the agreement to the claims system through the message queue and microservice architecture to achieve asynchronous circulation. In the claims system, the corresponding electronic seal is generated according to the signed agreement content, and the seal is embedded in the electronically signed version of the agreement to ensure the legal validity of the agreement. The signature status is passed to the case management service to update the case status. The PDF generation and storage microservice generates the final PDF document and uploads it to the cloud storage system. The agreement completion status is passed to the case management service to update the case status.

[0050] Example 2

[0051] See also Figure 5As shown, an embodiment of the present invention provides a device for simplifying the process of signing an agreement for an insurance case, comprising: at least one processing unit, the processing unit and the storage unit are interconnected through a bus unit, and the storage unit is a computer-readable storage medium that can be used to store software programs, computer executable programs, and modules, such as the software programs, computer executable programs, and modules corresponding to a method for simplifying the process of signing an agreement for an insurance case in an embodiment of the present invention. The processing unit implements the above-mentioned method for simplifying the process of signing an agreement for an insurance case by running the software programs, computer executable programs, and modules stored in the storage unit, including:

[0052] The customer submits claim documents through the APP. The APP backend calls the case management microservice to create a new case and store basic information, including claim serial number, type, status, policy, and claim case description.

[0053] After a case is created, the information extraction microservice obtains the basic information of the newly created case and uses the pre-trained NLP model to extract key information from the insurance policy or claim case description;

[0054] After extracting the key information, the template matching and filling microservice obtains the key information, automatically fills the extracted key information into the corresponding variable position in the template, and generates a preliminary agreement document;

[0055] After the preliminary agreement document is generated, the format verification microservice processes the generated preliminary agreement document into a Word or PDF format agreement document and verifies the format and content of the document to ensure that the document complies with legal requirements;

[0056] After the agreement is generated, the online approval and signing microservice sends a real-time notification to the approver to remind him / her to review the agreement. After the approver reviews and confirms that the agreement document is correct, he / she will create a signing link for the customer, and the customer will sign the agreement.

[0057] After the customer signs the agreement, the agreement circulation and automatic sealing microservice will convert the signed agreement into an electronic signature version and asynchronously transfer it to the claims settlement system. The claims settlement system will sign and seal the signed agreement according to the content and upload it to the cloud storage system.

[0058] Microservices are event-driven. Each microservice can act as an event producer, publishing events to the event bus when important business events occur; the event bus acts as a central, highly scalable message queue or message agent, responsible for the distribution and delivery of events; other microservices can act as event consumers, subscribe to events of interest, and execute corresponding business logic based on the event content.

[0059] Of course, the computer program stored in the storage unit of the device for simplifying the insurance case agreement signing process provided by an embodiment of the present invention is not limited to the method operations described above, and can also execute related operations in the method for simplifying the insurance case agreement signing process provided by any embodiment of the present invention.

[0060] Example 3

[0061] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program. When the computer program is executed, the method for simplifying the insurance case agreement signing process is implemented, including:

[0062] The customer submits claim documents through the APP. The APP backend calls the case management microservice to create a new case and store basic information, including claim serial number, type, status, policy, and claim case description.

[0063] After a case is created, the information extraction microservice obtains the basic information of the newly created case and uses the pre-trained NLP model to extract key information from the insurance policy or claim case description;

[0064] After extracting the key information, the template matching and filling microservice obtains the key information, automatically fills the extracted key information into the corresponding variable position in the template, and generates a preliminary agreement document;

[0065] After the preliminary agreement document is generated, the format verification microservice processes the generated preliminary agreement document into a Word or PDF format agreement document and verifies the format and content of the document to ensure that the document complies with legal requirements;

[0066] After the agreement is generated, the online approval and signing microservice sends a real-time notification to the approver to remind him / her to review the agreement. After the approver reviews and confirms that the agreement document is correct, he / she will create a signing link for the customer, and the customer will sign the agreement.

[0067] After the customer signs the agreement, the agreement circulation and automatic seal microservice converts the signed agreement into an electronically signed agreement and asynchronously transfers it to the claims system. The claims system stamps the signed agreement according to its content and uploads it to the cloud storage system.

[0068] Microservices are event-driven. Each microservice can act as an event producer, publishing events to the event bus when important business events occur; the event bus acts as a central, highly scalable message queue or message agent, responsible for the distribution and delivery of events; other microservices can act as event consumers, subscribe to events of interest, and execute corresponding business logic based on the event content.

[0069] A computer-readable storage medium provided in an embodiment of the present invention stores a computer program which is not limited to the method operations described above, but can also execute related operations in a method for simplifying the insurance case agreement signing process provided in any embodiment of the present invention.

[0070] In the embodiments provided by the present invention, it should be understood that the disclosed structures and methods can be implemented in other ways. For example, the structural embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, structures or units, which can be electrical, mechanical or other forms.

[0071] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0072] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0073] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. 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 invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for simplifying the process of signing an insurance case agreement, characterized in that: include: The customer submits claim documents through the APP. The APP backend calls the case management microservice to create a new case and store basic information, including claim serial number, type, status, policy, and claim case description. After a case is created, the information extraction microservice obtains the basic information of the newly created case and uses the pre-trained NLP model to extract key information from the insurance policy or claim case description; After extracting the key information, the template matching and filling microservice obtains the key information, automatically fills the extracted key information into the corresponding variable position in the template, and generates a preliminary agreement document; After the preliminary agreement document is generated, the format verification microservice processes the generated preliminary agreement document into a Word or PDF format agreement document and verifies the format and content of the document to ensure that the document complies with legal requirements; After the agreement is generated, the online approval and signing microservice sends a real-time notification to the approver to remind him / her to review the agreement. After the approver reviews and confirms that the agreement document is correct, he / she will create a signing link for the customer, and the customer will sign the agreement. After the customer signs the agreement, the Agreement Circulation and Automatic Seal Microservice converts the signed agreement into an electronically signed agreement and asynchronously transfers it to the claims system. The claims system signs and seals the signed agreement according to the content of the signed agreement. The signing status is passed to the case management microservice in real time. The case management microservice updates the case status and passes the signing result to the PDF generation and storage microservice. After the final PDF document is generated, it is uploaded to the cloud storage system. The microservices cooperate with each other through event-driven.

2. The method for simplifying the insurance case agreement signing process according to claim 1, characterized in that: Use SpringBoot to build a case management microservice to implement case creation and management functions; store the basic information of the case in a MySQL or PostgreSQL database, and ensure the integrity and consistency of the data; provide a unified interface through Spring Cloud Gateway or KongAPI gateway to facilitate other microservices to obtain basic case information from the case management microservice.

3. The method for simplifying the insurance case agreement signing process according to claim 1, characterized in that: The information extraction microservice is implemented based on the NLP model, and uses a pre-trained NLP model to extract key information from the insurance policy or claim case description. The extracted key information includes: applicant name, insured person information, policy number, and claim amount; the information extraction microservice provides an API interface through Flask or FastAPI for other microservices to call key information.

4. The method for simplifying the insurance case agreement signing process according to claim 1, characterized in that: The template matching and filling microservice stores and manages the protocol template library through the template engine, and dynamically fillable variables are embedded in the template to ensure a unified format; According to the key information extracted by the information extraction microservice, the extracted key information is automatically filled into the corresponding variable position in the template to generate a preliminary protocol document; the template matching and filling microservice provides an API interface through Spring Boot, which facilitates other microservices to obtain and generate preliminary protocol documents from the template matching and filling microservice.

5. The method for simplifying the insurance case agreement signing process according to claim 1, characterized in that: The format verification microservice uses Apache POI or iText to process the generated preliminary agreement document into an agreement document in Word or PDF format; verifies the format and content of the document through JSON Schema or XML Schema to ensure that the document complies with legal requirements; encapsulates the document generation and verification logic as a Java service, and integrates it with the front-end and case management microservices through the API interface.

6. The method for simplifying the insurance case agreement signing process according to claim 1, characterized in that: The online approval and signing microservice sends real-time notifications to the approvers through WebSocket or SSE technology, reminding them to review the agreement. The approvers log in to the online platform, view the generated agreement document, review it and confirm that it is correct. After the reviewer has reviewed and confirmed that the agreement document is correct, a signing link will be created for the customer, who will sign the agreement in the following ways: SMS signing link: The system calls the SMS service API and uses a third-party SMS service provider to send an SMS link with verification code verification, identity recognition and signature functions to the customer; APP signing link: The signing link is provided through the APP. The customer completes identity verification and online signing, and uploads necessary image materials.

7. The method for simplifying the insurance case agreement signing process according to claim 1, characterized in that: The agreement circulation and automatic seal microservice generates an electronic signature version of the signed agreement based on the PDF generation library and electronic signature technology; The agreement circulation and automatic seal microservice sends the generated electronic signature version of the agreement to the claims system through the message queue and microservice architecture to achieve asynchronous circulation; In the claims settlement system, a corresponding electronic seal is generated according to the content of the signed agreement, and the seal is embedded in the electronic signature version of the agreement to ensure the legal validity of the agreement; The generated electronically signed agreement is stored in a secure cloud storage system, and the storage and retrieval of the agreement is managed through a microservice architecture to ensure data accessibility and security.

8. The method for simplifying the insurance case agreement signing process according to claim 1, characterized in that: The event-driven cooperation between the microservices includes: the case management microservice generates a "case creation" event; the information extraction microservice subscribes to the "case creation" event, and when the "case creation" event is received, the information extraction microservice extracts the key information of the case, and after completing the extraction of the key information, generates a "case information extraction" event; the template matching and filling microservice subscribes to the "case information extraction" event, and when the "case information extraction" event is received, the template matching and filling microservice uses the key information to generate a preliminary agreement document, and after completing the generation of the preliminary agreement document, generates a "generate preliminary agreement" event; the format verification microservice subscribes to the "generate preliminary agreement" event, and when the "generate preliminary agreement" event is received, the format verification microservice processes the preliminary agreement document to obtain the agreement document, and after completing the generation of the agreement document, generates a "generate agreement" event; the online approval and signing process microservice subscribes to the "generate agreement" event, and when the "generate agreement" event is received, controls the approval and signing of the agreement, and after signing the agreement, generates an "agreement signing completed" event. "Event; The Agreement Circulation and Automatic Seal Microservice subscribes to the "Agreement Signing Completed" event; The Agreement Circulation and Automatic Seal Microservice subscribes to the "Agreement Signing Completed" event. When receiving the "Agreement Signing Completed" event, the Agreement Circulation and Automatic Seal Microservice processes the signed agreement into an electronically signed agreement and asynchronously transfers it to the claims system. The claims system signs and seals the signed agreement according to the content of the signed agreement. After the agreement is signed, an "Agreement Signing" event is generated; After the PDF Generation and Storage Microservice receives the "Agreement Signing" event, the PDF Generation and Storage Microservice processes the generated electronically signed agreement into PDF format and stores it in a secure cloud storage system, and then generates an "Agreement Completed" event; After receiving the "Agreement Signing Completed" event, the Case Management Microservice changes the status of the managed case according to the signing status; After receiving the "Agreement Signing" event, the Case Management Microservice updates the status of the managed case according to the signing status; After receiving the "Agreement Completed" event, the Case Management Microservice updates the status of the managed case according to the agreement completion status.

9. A device for simplifying the process of signing an insurance case agreement, characterized in that: include: At least one processing unit, the processing unit and the storage unit are interconnected through a bus unit, the storage unit stores a computer program, and when the computer program is executed by the processing unit, the method for simplifying the insurance case signing agreement process as described in any one of claims 1-8 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method for simplifying the insurance case agreement signing process as described in any one of claims 1-8 is implemented.

Images