A method for simplifying the signing of an agreement process for insurance cases

Abstract

The application provides a method for simplifying the signing agreement process of insurance cases; the application calls a case management microservice to create a new case according to the claim submitted by a customer and stores basic information; an information extraction microservice uses a pre-trained NLP model to extract key information from the basic information; a template matching and filling microservice automatically fills the extracted key information into the corresponding variable position in the template to generate a preliminary agreement document; a format verification microservice processes the generated preliminary agreement document into an agreement document and verifies the format and content of the document; an online approval and signing microservice reminds the approval personnel to review the agreement, and after the approval personnel reviews and confirms that the agreement document is correct, a signing link is established for the customer, and the customer signs the agreement; an agreement circulation and automatic stamping microservice converts the signed agreement into an electronic signature version of the agreement, and asynchronously circulates it to a claim settlement system, and the claim settlement system uploads the cloud storage system after signing the agreement content; each microservice is cooperated 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 number of claims settlement cases has continued to grow in recent years, customers and investigators have to travel frequently back and forth between the counter and the customer's residence, resulting in a dramatic increase in workload and a long time span, which makes it easy for customers to regret and complain. At the same time, the process of 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 handling 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 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 application and seal application process for the agreement is complicated. The traditional case agreement signing 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 error. 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 agreement, comprising:

[0006] The customer submits a claim 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 basic information about the newly created case and uses a pre-trained NLP model to extract key information from the insurance policy or claim description.

[0008] After extracting the key information, the template matching and filling microservice obtains the key information and automatically fills the extracted key information into the corresponding variable positions in the template to generate 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, reminding him / her to review the agreement. After the approver reviews and confirms that the agreement document is correct, he / she creates a signing link for the customer, who then signs the agreement.

[0011] After the customer signs the agreement, the Agreement Flow and Automatic Seal Microservice converts the signed agreement into an electronically signed version and asynchronously transfers it to the claims system. The claims system then stamps the signed agreement and uploads it to the cloud storage system.

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

[0013] Furthermore, Spring Boot is used to build a case management microservice to implement case creation and management functions; basic case information is stored in a MySQL or PostgreSQL database, and data integrity and consistency 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, using 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 a 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 the API interface.

[0017] Furthermore, the online approval and signing microservice sends real-time notifications to the approver via WebSocket or SSE technology, reminding him / her to review the agreement. The approver then logs into the online platform, views the generated agreement document, reviews it, and confirms that it is correct.

[0018] After the reviewer has reviewed and confirmed the agreement document is correct, a signing link will be created for the customer. The customer can 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. Customers complete identity verification and online signing, and upload necessary image materials.

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

[0021] The agreement transfer and automatic seal microservice sends the generated electronically signed agreement to the claims settlement system through the message queue and microservice architecture, achieving asynchronous transfer.

[0022] In the claims settlement system, a corresponding electronic seal is generated based on the content of the signed agreement and embedded into the electronically signed 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] Further, the cooperation between the microservices through event driving includes: the case management microservice generates a "case creation" event; the information extraction microservice subscribes to the "case creation" event, and when receiving the "case creation" event, the information extraction microservice extracts case key information, 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 receiving the "case information extraction" event, the template matching and filling microservice generates a preliminary protocol document by using the key information, and after completing the generation of the preliminary protocol document, generates a "generate preliminary protocol" event; the format verification microservice subscribes to the "generate preliminary protocol" event, and when receiving the "generate preliminary protocol" event, the format verification microservice processes the preliminary protocol document to obtain a protocol document, and after completing the generation of the protocol document, generates a "generate protocol" event; the online approval and signing process microservice subscribes to the "generate protocol" event, and when receiving the "generate protocol" event, controls the approval and signing of the protocol, and after signing the protocol, generates a "protocol signing completion" event; the protocol circulation and automatic stamping microservice subscribes to the "protocol signing completion" event; the protocol circulation and automatic stamping microservice receives the subscription "protocol signing completion" event, processes the signed protocol into an electronic signature version of the protocol, and asynchronously circulates the electronic signature version of the protocol to the claim settlement system, the claim settlement system signs the protocol according to the signed protocol content, and after signing the protocol, generates a "protocol signing" event; after receiving the "protocol signing" event, the PDF generation and storage microservice processes the generated electronic signature version of the protocol into a PDF format and stores the PDF in a secure cloud storage system, and then generates a "protocol completion" event; after receiving the "protocol signing completion" event, the case management microservice changes the case state managed by the case management microservice according to the signing state; after receiving the "protocol signing" event, the case management microservice updates the case state managed by the case management microservice according to the signing state; and after receiving the "protocol completion" event, the case management microservice updates the case state managed by the case management microservice according to the protocol completion state.

[0025] In a second aspect, the present application provides a device for simplifying an insurance case signing protocol process, comprising: at least one processing unit, a bus unit interconnecting the processing unit and a storage unit, the storage unit storing a computer program, and the computer program being executed by the processing unit to implement the method for simplifying the insurance case signing protocol process.

[0026] In a third aspect, the present application provides a computer readable storage medium storing a computer program, and the computer program being executed by a processor to implement the method for simplifying the insurance case signing protocol process.

[0027] Compared with the prior art, the above technical solution provided by the embodiments of the present application has the following advantages:

[0028] Intelligent agreement generation and automatic information filling greatly simplify the claims agreement writing process, improving the efficiency of claims adjusters. Automatic filling and formatting through a microservice-based NLP model ensure the accuracy of agreement content and reduce the possibility of human error. Support for multiple signing methods meets the needs of different customers and improves the customer experience. Automatically generating electronic agreements and automatically applying seals automates the agreement signing process, reducing the time and cost of manual operations. Electronic signatures, identity recognition, and multi-factor authentication technologies ensure the security and legality of the signing process. The combination of an event-driven architecture and a microservices architecture ensures system scalability and high availability, supporting large-scale concurrent operations. 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 following briefly introduces the drawings required for use in the embodiments or the description of the prior art. 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 This is an architectural diagram of a simplified insurance case agreement signing process provided by an embodiment of the present invention;

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

[0034] Figure 4 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 an apparatus for simplifying the insurance case agreement signing process provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0036] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying 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 making creative efforts shall fall within the scope of protection of the present invention.

[0037] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0038] Example 1

[0039] The present invention implements a method for simplifying the insurance case agreement signing process. To achieve this, the present invention utilizes a microservices architecture combined with an event-driven architecture development model, which meets the system's requirements for high scalability, resilience, flexibility, and decoupling. Each microservice can act as an event producer, publishing events to an event bus when important business events occur. The event bus, acting as a central, highly scalable message queue or message broker, is responsible for event distribution and delivery. Other microservices can act as event consumers, subscribing to events of interest and executing corresponding business logic based on the event content. An event represents a fact that has occurred and does not contain any destination information. Messages convey event content, transferring event data from the source to a designated destination. The event source generates a message encapsulating the event data. When the message carrying the event data arrives at the destination, it triggers the subscribed microservice or action function. The message queue is asynchronous, allowing the recipient to retrieve the message some time after it is sent, without requiring the sender and recipient to interact with the message queue simultaneously. The event producer sends a message, and the event consumer asynchronously obtains the event through the message queue and executes the corresponding logic, reducing service response time and improving the user experience. Message queues reduce coupling between services. Different services communicate through message queues. When a business requires the joint implementation of multiple services, or a single message requires processing by multiple services, the message producer simply sends a message, and the consuming service consumes the message from the message queue to meet the business needs, reducing coupling between services. If there is a gap in processing capabilities between services, the message queue is stored until the service is able to handle it, and then distributed and processed. If system request traffic suddenly increases, the message queue will cache the requests and distribute them over a period of time, improving system stability and user experience.

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

[0041] Case Management Microservice: When a customer submits a claim through the app and submits claim documents, the app backend calls the Case Management Microservice via an API to create a new case and store basic case information, including claim serial number, type, status, policy, and claim description. For each new claim, the Case Management Microservice, acting as an event producer, generates a "Case Created" event. In implementation, the Case Management Microservice is built using Spring Boot to implement case creation and management. Basic case information is stored in a MySQL or PostgreSQL database to ensure data integrity and consistency. A unified interface is provided through Spring Cloud Gateway or the Kong API Gateway, allowing other microservices to access basic case information from the Case Management Microservice. As an event consumer, the Case Management Microservice subscribes to the "Agreement Signed Completed" event. Upon receiving this event, it updates the status of the managed case based on the signing status. As an event consumer, the Case Management Microservice subscribes to the "Agreement Signed Completed" event. Upon receiving this event, it updates the status of the managed case based on the signing 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 person 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. Examples of NLP models include 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: Store and manage a library of protocol templates through a template engine, such as Freemarker, Thymeleaf, or Handlebars. Embed dynamic fillable variables in the templates to ensure uniform formatting. Based on the key information extracted by the information extraction microservice, automatically fill the extracted key information into the corresponding variable positions in the template to generate a preliminary protocol document. The template matching and filling microservice provides API interfaces through Spring Boot to facilitate other microservices to obtain the generated preliminary protocol document from the template matching and filling microservice. The template matching and filling microservice acts as an event consumer and 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 positions in the template to generate a preliminary protocol document. The template matching and filling microservice acts as an event producer and generates a "generate preliminary protocol" event after completing the generation of the preliminary protocol document.

[0044] Format verification microservice: The format verification microservice acts as an event consumer and subscribes to the "generate preliminary protocol" event. When the "generate preliminary protocol" event is received, the format verification microservice processes the generated preliminary protocol document into a Word or PDF format protocol document using Apache POI or iText. 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 with the front end and case management microservices through API interfaces. The format verification microservice acts as an event producer and generates a "generate protocol" event.

[0045] As shown in Figure 3 Online approval and signing process microservice: The online approval and signing process microservice acts as an event consumer and subscribes to the "generate protocol" event. When the "generate protocol" event is received, the online approval and signing microservice sends real-time notifications to the approval personnel through WebSocket or SSE technology, reminding them to review the protocol. The approval personnel logs in to the online platform, reviews the generated protocol document, and confirms that it is correct. After the approval personnel reviews and confirms that the protocol document is correct, a signing link is established for the client, and the client signs the protocol. The signing methods include: SMS signing link: The system calls the SMS service API and sends a SMS link containing verification code verification, identity recognition, and signature function to the client through a third-party SMS service provider (such as Twilio, Nexmo). APP signing link: Provide a signing link through the APP, and the client completes identity verification and online signing, and uploads necessary image data.

[0046] The online approval and signing process microservice acts as an event producer and generates a "protocol signing completion" event after the client signs the protocol.

[0047] Agreement Flow and Automatic Seal Microservice: The Agreement Flow and Automatic Seal Microservice acts as an event consumer and subscribes to the "Agreement Signing Completed" event. Figure 4 As shown, upon receiving the "Agreement Signing Completed" event, the Agreement Flow and Automatic Seal Microservice generates an electronically signed version of the signed agreement based on PDF generation libraries such as iText and PDFBox, and electronic signature technologies such as DocuSign and Adobe Sign. The Agreement Flow and Automatic Seal Microservice then sends the generated electronically signed version of the agreement to the claims settlement system via a message queue, such as Kafka or RabbitMQ, and the microservice architecture, enabling asynchronous flow. In the claims settlement system, a corresponding electronic seal is generated based on the signed agreement content and 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 acts as an event consumer and subscribes to the "Agreement Signature" event. Upon receiving the "Agreement Signature" 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. The microservice architecture manages the storage and retrieval of the agreement, ensuring data accessibility and security. The PDF Generation and Storage microservice acts as an event producer and generates the "Agreement Completed" event.

[0049] This invention uses Python and Java as the primary development languages. JavaScript and the front-end framework Vue.js are primarily used to build the user interface for case management and document signing process visualization. Vue.js is used on the front end to build the claims case management interface, which includes the creation, viewing, and update functions for claims cases. Spring Boot is used on the back end to build the case management microservice for case data storage and status management. MySQL or PostgreSQL is also used as a database to store basic case information and make it available to other microservices via an API gateway. The information extraction microservice uses an NLP model to extract key information from the policy and case description. Flask or FastAPI is used to build the API interface for the information extraction microservice. The information extraction microservice returns this key information as structured data to the template matching and filling microservice. The template matching and filling microservice uses a template engine to store and manage a library of agreement templates. Based on the extracted key information, the agreement template is filled in to generate a preliminary agreement document. The format verification microservice verifies the format of the generated agreement document using JSON Schema or XML Schema to ensure compliance with legal requirements. The generated agreement is then 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 sends approval information to the claims adjuster in real time using WebSocket or SSE. The signing link is sent to the customer via Twilio SMS or the app. The signing status is communicated to the case management service, which updates the case status. The signing result is also passed to the agreement transfer and automatic seal microservice, which generates an electronically signed agreement based on a PDF generation library and electronic signature technology. The agreement transfer and automatic seal microservice sends the generated electronically signed agreement to the claims system via a message queue and microservice architecture, achieving asynchronous processing. The claims system generates a corresponding electronic seal based on the signed agreement content and embeds it into the electronically signed agreement to ensure the legal validity of the agreement. The signing status is communicated to the case management service, which updates the case status. The PDF generation and storage microservice generates the final PDF document and uploads it to a cloud storage system. The agreement completion status is communicated to the case management service, which updates the case status.

[0050] Example 2

[0051] See Figure 5As shown, an embodiment of the present invention provides an apparatus for simplifying the process of signing an insurance agreement, comprising: at least one processing unit, interconnected with a storage unit via a bus unit, the storage unit being a computer-readable storage medium capable of storing 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 insurance agreement in an embodiment of the present invention. The processing unit implements the method for simplifying the process of signing an insurance agreement by running the software programs, computer executable programs, and modules stored in the storage unit, including:

[0052] The customer submits a claim 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 basic information about the newly created case and uses a pre-trained NLP model to extract key information from the insurance policy or claim description.

[0054] After extracting the key information, the template matching and filling microservice obtains the key information and automatically fills the extracted key information into the corresponding variable positions in the template to generate 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, reminding him / her to review the agreement. After the approver reviews and confirms that the agreement document is correct, he / she creates a signing link for the customer, who then signs 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 driven by events. 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 broker, responsible for distributing and delivering events. Other microservices can act as event consumers, subscribing to events of interest and executing 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 storing 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 a claim 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 basic information about the newly created case and uses a pre-trained NLP model to extract key information from the insurance policy or claim description.

[0064] After extracting the key information, the template matching and filling microservice obtains the key information and automatically fills the extracted key information into the corresponding variable positions in the template to generate 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, reminding him / her to review the agreement. After the approver reviews and confirms that the agreement document is correct, he / she creates a signing link for the customer, who then signs the agreement.

[0067] After the customer signs the agreement, the Agreement Flow and Automatic Seal Microservice converts the signed agreement into an electronically signed version and asynchronously transfers it to the claims system. The claims system then stamps the signed agreement and uploads it to the cloud storage system.

[0068] Microservices are driven by events. 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 broker, responsible for distributing and delivering events. Other microservices can act as event consumers, subscribing to events of interest and executing corresponding business logic based on the event content.

[0069] A computer-readable storage medium provided by an embodiment of the present invention stores a computer program that 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 by 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 merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, structure or unit, which can be electrical, mechanical or other forms.

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

[0072] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0073] The foregoing description is intended only to provide specific embodiments of the present invention, which will enable those skilled in the art to understand and implement the present invention. Various modifications to these embodiments will be readily 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 is not intended to be limited to the embodiments shown herein, but is intended to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for simplifying the process of signing an insurance agreement, characterized in that: include: The customer submits a claim 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 basic information about the newly created case and uses a pre-trained NLP model to extract key information from the insurance policy or claim description. After extracting the key information, the template matching and filling microservice obtains the key information and automatically fills the extracted key information into the corresponding variable positions in the template to generate 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, reminding him / her to review the agreement. After the approver reviews and confirms that the agreement document is correct, he / she creates a signing link for the customer, who then signs the agreement. After the customer signs the agreement, the Agreement Flow and Automatic Seal Microservice converts the signed agreement into an electronically signed version and asynchronously transfers it to the claims settlement system, which then stamps the agreement based on the content. The system then transmits the signing status to the Case Management Microservice in real time, which updates the case status and passes the signing result to the PDF Generation and Storage Microservice, which generates the final PDF document and uploads it to the cloud storage system. The microservices cooperate with each other through event-driven operation.

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 basic case information in a MySQL or PostgreSQL database, and ensure data integrity and consistency; 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 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 embeds dynamically fillable variables 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 agreement document; the template matching and filling microservice provides an API interface through Spring Boot, which facilitates other microservices to obtain and generate preliminary agreement 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 approver via WebSocket or SSE technology, reminding him / her to review the agreement. The approver logs into the online platform, views the generated agreement document, reviews it, and confirms that it is correct. After the reviewer has reviewed and confirmed the agreement document is correct, a signing link will be created for the customer. The customer can 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. Customers complete identity verification and online signing, and upload 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 will generate an electronic signature version of the signed agreement based on the PDF generation library and electronic signature technology; The agreement transfer and automatic seal microservice sends the generated electronically signed agreement to the claims settlement system through the message queue and microservice architecture, achieving asynchronous transfer. In the claims settlement system, a corresponding electronic seal is generated based on the content of the signed agreement and embedded into the electronically signed 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 coordination 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 it receives the "case creation" event, the information extraction microservice extracts the key information of the case, and after completing the extraction of the key information, it generates a "case information extraction" event; the template matching and filling microservice subscribes to the "case information extraction" event, and when it receives the "case information extraction" event, 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, it generates a "generate preliminary agreement" event; the format verification microservice subscribes to the "generate preliminary agreement" event, and when it receives the "generate preliminary agreement" event, the format verification microservice processes the preliminary agreement document to obtain the agreement document, and after completing the generation of the agreement document, it generates a "generate agreement" event; the online approval and signing process microservice subscribes to the "generate agreement" event, and when it receives the "generate agreement" event, it controls the approval and signing of the agreement, and after signing the agreement, it generates an "agreement signing completed" event. " event; the Agreement Flow and Automatic Seal Microservice subscribes to the "Agreement Signing Completed" event; the Agreement Flow and Automatic Seal Microservice subscribes to the "Agreement Signing Completed" event. When receiving the "Agreement Signing Completed" event, the Agreement Flow and Automatic Seal Microservice processes the signed agreement into an electronically signed version of the agreement and asynchronously transfers it to the claims settlement system. The claims settlement system signs and seals the agreement according to the content of the signed agreement. After the agreement is signed, an "Agreement Signed" event is generated; after the PDF Generation and Storage Microservice receives the "Agreement Signed" event, the PDF Generation and Storage Microservice processes the generated electronically signed version of the 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 Signed" 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 agreement, characterized in that: include: At least one processing unit, interconnecting the processing unit and the storage unit through a bus unit, wherein 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 agreement signing 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, it implements the method for simplifying the insurance case agreement signing process as described in any one of claims 1 to 8.

Images