Insurance Data Configuration Layer for Multi-Company Custom Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems struggle to efficiently deliver cloud-based services to multiple companies with varying database structures, as they typically rely on consistent data types, making it burdensome to extract and integrate custom data from companies with unique database configurations.
Innovation Solution
A central hosted component retrieves and processes both standard and custom data fields from multiple companies, using configuration files to define how data is extracted and integrated into applications, allowing for tailored services and incremental updates to maintain data consistency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If consistent data types are used across all companies, then system simplicity is improved, but adaptability to company-specific database structures deteriorates
Solution Approach 1:
The patent segments data fields into standard fields (common to all companies) and custom fields (specific to individual companies). This segmentation allows the system to maintain a simple core structure while accommodating company-specific variations through configurable custom fields defined in company-specific configuration files.
Solution Approach 2:
The system dynamically adapts to different company database structures by reading company-specific configuration files that define custom data fields. This dynamic configuration approach allows the system to adjust its data extraction and processing behavior based on each company's specific requirements without compromising overall system simplicity.
2Adaptability or versatility
If custom data extraction is implemented for each company, then adaptability is improved, but operational burden deteriorates
Solution Approach 1:
The system implements self-service by automatically reading company-specific configuration files that contain definitions of custom data fields, their locations in company databases, and extraction parameters. This automation eliminates the need for manual configuration and reduces operational burden, as the system configures itself based on the provided configuration files.
Solution Approach 2:
The patent applies preliminary action by requiring companies to prepare their configuration files in advance, which define all custom data field specifications before the data extraction process begins. This preliminary configuration setup enables the system to automatically handle custom data extraction without requiring operational intervention during the extraction process.
3Adaptability or versatility
If company-specific configuration files are used, then customization capability is improved, but system complexity deteriorates
Solution Approach 1:
The patent introduces configuration files as an intermediary layer between the company's database and the central system. These configuration files serve as a mediator that translates company-specific database structures into a format the central system can process, enabling customization without directly complicating the core system architecture.
Solution Approach 2:
The system manages complexity by changing parameters (data field definitions, locations, and extraction rules) through configuration files rather than modifying the core system code. This parameter-based approach allows extensive customization while maintaining system simplicity, as changes are made through configuration rather than structural modification.
Data Source
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.