Database Query Optimization for Retail Claim Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems face inefficiencies and overload due to the need for numerous database queries across disparate databases to retrieve and merge data, leading to slow system performance and potential failures.
Innovation Solution
A method and system that minimize database queries by receiving user application claim information, querying item and invoice databases to merge relevant data into a single record, and storing it in a claims database, thereby reducing the operational load and improving data retrieval speed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is retrieved from multiple disparate databases by running queries against all available data fields, then complete data retrieval is achieved, but system performance deteriorates and the system becomes overloaded
Solution Approach 1:
The patent extracts only the necessary data fields required for the specific task at hand, rather than retrieving all available data fields from databases. This selective extraction approach maintains data retrieval completeness for the required information while significantly reducing the processing load and improving system performance.
Solution Approach 2:
The system performs preliminary actions by pre-identifying and retrieving only the specific data fields needed for the task before processing begins. This preliminary selection of necessary data prevents unnecessary database scanning and merging operations, thereby maintaining reliability while improving productivity.
2Loss of information
If queries are structured to search all available data fields in databases, then data completeness is ensured, but the system runs slowly and becomes overloaded
Solution Approach 1:
The patent applies extraction by selectively retrieving only the specific data fields required for the task from the databases, rather than searching all available data fields. This ensures that all necessary information is obtained while minimizing the time spent on unnecessary data retrieval and processing operations.
Solution Approach 2:
The system performs partial action by retrieving exactly the necessary data fields needed for the task without going beyond what is required. This avoids the excessive action of searching all available data fields, thereby reducing query execution time while maintaining data completeness for the required information.
3Adaptability or versatility
If multiple database queries are run to retrieve and merge data from different locations, then data from disparate sources is obtained, but the number of queries increases system complexity and processing time
Solution Approach 1:
The patent extracts only the necessary data fields from each disparate database source required for the specific task. This selective extraction maintains the system's ability to integrate data from multiple sources while simplifying the query structure by eliminating unnecessary data retrieval and merging operations.
Solution Approach 2:
The system performs preliminary identification of necessary data fields from each database source before executing queries. This preliminary action enables efficient data retrieval from disparate sources with simplified query structures, as the system already knows exactly what data is needed from each location.
Data Source
AI summary
Retail stores may use the claim processing server to make a claim against a distribution center. Information about the claim may be entered into the store computer via an application and user interface. The claim processing server may use the information to process the claim and validate the related data. Using the information entered via the application the claim processing server may query the item database and the invoice database to retrieve to retrieve addition information from the database regarding the claim and the items. The information from the different databases may be merged together into a single database record which is then validated and stored the claim processing database. The information may also be checked and its accuracy verified. The user interfaces at the retail stores and distribution center may then be used to identify the claims for processing. The information for the item and invoice databases needed to process the claims are available from the claims processing database and the claim may be processed. The claims may be stored in the claims processing database for processing at a later time or for batch processing, for example during off-peak hours.