Configuration-Driven Insurance Data Processing Across Company Schemas

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in delivering cloud-based services that cater to multiple companies with varying database structures, as they often require burdensome data extraction from companies with similar but non-identical database configurations.

Innovation Solution

A central hosted component retrieves and processes both standard and custom data fields from client systems, using configuration files to define data retrieval and usage, enabling tailored applications and services for each company, with incremental data updates and historical data catch-up mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a service provider builds a single application to share among multiple companies, then service delivery efficiency is improved, but the ability to accommodate varying database structures and custom data needs deteriorates

Engineering Contradiction:
Improveservice delivery efficiencyVSAvoidaccommodation of varying database structures
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments data fields into standard fields and custom fields, allowing the application to handle multiple database structures through configuration files that define company-specific custom fields while sharing common standard fields across all companies

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically adapts to different company database structures by loading configuration files that specify custom data fields, enabling the application to adjust its behavior and data extraction processes based on each company's specific requirements

Inventive Principle:
Principle #15Dynamics

2Loss of information

If data extraction is performed from companies with similar but non-identical database structures, then information retrieval is achieved, but the process becomes burdensome and complex

Engineering Contradiction:
Improveinformation retrieval completenessVSAvoiddata extraction process complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent uses configuration files that are prepared in advance to define custom data fields, data types, and extraction rules for each company, allowing the system to automatically adapt to different database structures without requiring complex extraction logic

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Configuration files serve as an intermediary layer between the application and various company database structures, translating diverse database schemas into a unified format that the application can process without direct complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12444000B2Custom data
Publication Date: 2025.10.14 GUIDEWIRE SOFTWARE INC
  • US12444000B2 patent drawing
  • US12444000B2 patent drawing
  • US12444000B2 patent drawing

AI summary

A technique of processing insurance data collected from a plurality of companies includes obtaining a company defined configuration that specifies how to extract a set of company generated data records from a data store and how the set of company generated data records is used by an application. The data store includes common data elements shared by the plurality of companies and company-specific data elements specified by a company. It further includes obtaining from the data store the set of company generated data records based on the company defined configuration. It further includes executing the application to process the company generated data records according to how the set of company generated data records is used by the application as specified by the company defined configuration.